gtpm4m1kMessages (System Error and Offline)

IOD0-IPTS

IOD004xxxx ADDRESS INVALID FOR yyyy

Where:

xxxx
The keyword that contains the address that is not valid.

yyyy
The device type.

Severity: 5

Explanation: The keyword referenced in the message contains an address that is not valid for the device type indicated. The last digit must be 0 or 8.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

IOD006NUMBER OF 37X5S PLUS THE NUMBER OF SCTCS EXCEEDS TABLE SIZE OF xxx - ENTRY IGNORED

Where:

xxx
The number of entries.

Severity: 5

Explanation: The system initialization program (SIP) contains a table of 37x5 and SCTC addresses with space for the number entries indicated in the message. The table is full.

System Action: None.

User Response: Do the following:

  1. Reduce the number of 37x5 or SCTC addresses by reducing the number of IODEV macro calls for the 37x5s and SCTCs.
  2. Rerun SIP stage I.

IOD008IOADR PARAMETER INVALID FOR DVTYP = xxxx.

Where:

xxxx
The device type.

Severity: 5

Explanation: The address specified for the device type coded on the DVTYP parameter is not within the valid range.

System Action: None.

User Response: Do the following:

  1. Correct the IODEV macro that is in error.
  2. Rerun SIP stage I.

IOD015DUPLICATE IOADR=xx - IODEV IGNORED

Where:

xx
The value of IOADR.

Severity: 5

Explanation: An IODEV was already coded with IOADR=xx.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

IOD016WHEN DVTYP=xxxx - IOADR SHOULD BE y HEXADECIMAL DIGITS.

Where:

xxxx
The value for DVTYP.

y
The number of hexadecimal digits.

Severity: 5

Explanation: The number of digits specified for the device address is incorrect for this device type:

 DEVICE 
# OF DIGITS IN ADDRESS

 (xxxx) 
(y)

 TAPE 
2

 37X5 
4

 SCTC 
4

 DASD 
4

System Action: None.

User Response: Do the following:

  1. Correct the IODEV macro that is in error.
  2. Rerun SIP stage I.

IOD017A MAXIMUM OF xxxx IODEV MACROS DEFINING DASD IS ALLOWED

Where:

xxxx
The maximum number of DASD strings allowed.

Severity: 5

Explanation: The TPF system allows the maximum number of DASD strings indicated in the message to be coded.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

IOD018THE dev ADDRESS yyyy WILL DUPLICATE THE PREVIOUSLY DEFINED ADDRESS zzzz

Where:

dev
The device type that was coded on the DVTYP parameter.

yyyy
The starting address that was coded on the IOADR parameter.

zzzz
The address.

Severity: 5

Explanation: If all the devices on the string starting at yyyy were defined, then they would overlay the address of zzzz, which was defined by a prior IODEV macro. All IODEV device addresses must be unique. Therefore, the current IODEV macro was ignored.

Notes:

  1. For tape, the IOADR parameter defines a string of 16 tape addresses.

  2. For DASD, the IOADR parameter defines a string of eight DASD addresses.

  3. For 37x5, the IOADR parameter defines one 37x5 control unit.

  4. For SCTC, the IOADR parameter defines one SNA channel-to-channel connection.

System Action: None.

User Response: Do the following:

  1. Eliminate the address overlaps among the IODEV macros.
  2. Rerun SIP stage I.

IOD019THE RCSSID PARAMETER IS VALID ONLY WHEN DVTYP=DASD; PARAMETER WAS IGNORED

Severity: 0

Explanation: The DVTYP parameter specifies the type of device for which the range of addresses is intended. The Record Cache Subsystem SSID (RCSSID) parameter is used only for a 3990 Record Cache Subsystem attached DASD. Therefore, no other device can be specified.

System Action: None.

User Response: None. The RCSSID coded on the current IODEV macro is ignored and has no effect on system generation. However, if a completely clean assembly is desired, then remove the RCSSID parameter and rerun SIP stage I.

IPE00001IINVALID CARD -- IGNORED

Explanation: The input card (FMT, size, or dup field) is not valid. This message is sent to a printer.

System Action: An abnormal termination occurs with the abend code of U0001.

User Response: Do the following:

  1. Check to see whether FMT, S, L, N, D, 4, or 2 are missing.
  2. Correct the card.
  3. Start the job again.

See TPF Operations for more information about the real-time disk formatter.

IPE00002IFIRST TRACK SHOULD NOT BE FORMATTED

Explanation: An attempt to format cylinder 0 track 0 was made. This message is sent to a printer.

System Action: An abnormal termination occurs with the abend code of U0002.

User Response: Do the following:

  1. Correct the card.
  2. Start the job again.

See TPF Database Reference for more information about the real-time disk formatter.

IPE00003ITRIED TO FORMAT PAST CYLINDER LIMIT

Explanation: An attempt to format past the cylinder limit was made. This message is sent to a printer.

System Action: An abnormal termination occurs with the abend code of U0003.

User Response: Do the following:

  1. Correct the card.
  2. Start the job again.

See TPF Database Reference for more information about the real-time disk formatter.

IPE00004WEOF READER -- NO END CARD

Explanation: There was an EOF on the reader. There is no end card. This message is sent to a printer.

System Action: An abnormal termination occurs with the abend code of U0004.

User Response: Do the following:

  1. Insert the FMT END card.
  2. Start the job again.

See TPF Database Reference for more information about the real-time disk formatter.

IPE00005INO DASD SPECIFIED

Explanation: The type of device to be formatted was not specified. This message is sent to a printer.

System Action: An abnormal termination occurs with the abend code of U0008.

User Response: Do the following:

  1. Correct the card.
  2. Start the job again.

See TPF Database Reference for more information about the real-time disk formatter.

IPE00006IADDRESS NOT DECIMAL

Explanation: The disk address on the input card is not valid. This message is sent to a printer.

System Action: An abnormal termination occurs with the abend code of U0006.

User Response: None.

See TPF Operations for more information about the real-time disk formatter.

IPE00007IERROR IN ECB STATUS

Explanation: There was a programming error while testing the ECB. This message is sent to a printer.

System Action: An abnormal termination occurs with the abend code of U0007.

User Response: None.

IPE00009IADDRESSES SWITCHED

Explanation: The beginning address is larger than the ending address. This message is sent to a printer.

System Action: An abnormal termination occurs with the abend code of U0009.

User Response: None.

IPE00010IUNRECOVERABLE I/O ERROR.

Explanation: The completion code of this MVS event control block (ECB) is X'41'. The cylinder and head address are also shown.

System Action: None.

User Response: None.

IPE00011IDA EXTENT VIOLATED

Explanation: The completion code of this MVS event control block (ECB) is X'42'. The cylinder and head address are also shown.

System Action: None.

User Response: None.

IPE00012IPREVIOUS PERMANENT ERROR

Explanation: The completion code of this MVS event control block (ECB) is X'44'. The cylinder and head address are also shown.

System Action: None.

User Response: None.

IPE00013IAVAILABLE AFTER PURGE

Explanation: The completion code of this MVS event control block (ECB) is X'48'. The cylinder and head address are also shown.

System Action: None.

User Response: None.

IPE00014IERROR RECOVERY UNABLE TO READ HA OR R0

Explanation: The completion code of this MVS event control block (ECB) is X'4F'. The cylinder and head address are also shown.

System Action: None.

User Response: None.

IPE00015IDASD FORMAT REPORT TABLE OVERFLOW -- MORE THAN 1000 AREAS DEFINED

Explanation: The DASD has more than 1000 formatted areas. The internal table used to report each formatted area has overflowed.

System Action: An abnormal termination occurs with the abend code of U0011.

User Response: None.

See TPF Database Reference for more information about the real-time disk formatter.

IPE00016IINVALID TRACK ADDRESS SPECIFIED

Explanation: A track address that is not valid for the device was specified on the input parameter card for either the starting or ending address.

System Action: An abnormal termination occurs with the abend code of U0016.

User Response: None.

See TPF Database Reference for more information about the real-time disk formatter.

IPE00030IVTOC TRACK DO NOT FORMAT

Explanation: An attempt to format a track on which the VTOC is located was made.

System Action: This track address is ignored and job is continued.

User Response: None.

See TPF Database Reference for more information about the real-time disk formatter.

IPE00031ITHIS TRACK HAS NOT BEEN ALLOCATED -- REALLOCATE SPACE AND RERUN PROGRAM

Explanation: An error occurred while trying to format tracks that are not allocated. This message is sent to a printer.

System Action: An abnormal termination occurs with the abend code of U0010.

User Response: None.

IPTS0000IPROCESSED numrec FILE RECORDS, SELECTED numentry TRACE ENTRIES

Where:

numrec
The total number of Internet Protocol (IP) trace records on the real-time tape.

numentry
The number of trace entries selected.

Explanation: This is the normal message that is printed at the end of each successful report generated by the IPTPRT utility.

System Action: None.

User Response: None.

See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.

IPTS0001EERROR OPENING FILE filename

Where:

filename
The name of the file.

Explanation: An error occurred when the IPTPRT utility attempted to open a file.

System Action: The postprocessor request is rejected.

User Response: Do the following:

  1. Check the file name specified on the DD statement in the job control language (JCL) for the IPTPRT utility.
  2. Do one of the following:
  3. Run the JCL for the IPTPRT utility again.

See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.

IPTS0002EERROR READING FILE filename

Where:

filename
The name of the file.

Explanation: An error occurred when the IPTPRT utility attempted to read a file.

System Action: The postprocessor request is rejected.

User Response: Do the following:

  1. Check the file name specified on the DD statement in the job control language (JCL) for the IPTPRT utility.
  2. Do one of the following:
  3. Run the JCL for the IPTPRT utility again.

See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.

IPTS0003EERROR CLOSING FILE filename

Where:

filename
The name of the file.

Explanation: An error occurred when the IPTPRT utility attempted to close a file.

System Action: The postprocessor request is rejected.

User Response: Do the following:

  1. Check the file name specified on the DD statement in the job control language (JCL) for the IPTPRT utility.
  2. Do one of the following:
  3. Run the JCL for the IPTPRT utility again.

See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.

IPTS0004EINVALID PARAMETER: parameter

Where:

parameter
The specified parameter.

Explanation: The value specified for the PARM parameter in the job control language (JCL) for the IPTPRT utility is not a valid input parameter.

System Action: The postprocessor request is rejected.

User Response: Do the following:

  1. Update the EXEC statement in the JCL for the IPTPRT utility, and specify a valid parameter for the PARM parameter.
  2. Run the JCL again.

See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.

IPTS0005EINVALID VALUE parmvalue, DATE EXPECTED IN MMMDD FORMAT

Where:

parmvalue
The specified parameter value.

Explanation: The value specified for the DATE parameter in the job control language (JCL) for the IPTPRT utility is not valid.

System Action: The postprocessor request is rejected.

User Response: Do the following:

  1. Update the EXEC statement in the JCL for the IPTPRT utility, and specify a valid value for the DATE parameter. Ensure the value specified is in the form mmmdd, where mmm is the month and dd is the day.
  2. Run the JCL again.

See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.

IPTS0006EINVALID VALUE parmvalue, DECIMAL EXPECTED

Where:

parmvalue
The specified parameter value.

Explanation: The value specified for the DPORT, SPORT, or ICCW parameter in the job control language (JCL) for the IPTPRT utility is not valid. These parameters require a decimal value.

System Action: The postprocessor request is rejected.

User Response: Do the following:

  1. Update the EXEC statement in the JCL for the IPTPRT utility, and specify a valid decimal value for the DPORT, SPORT, or ICCW parameter.
  2. Run the JCL again.

See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.

IPTS0007EINVALID VALUE parmvalue, HEXADECIMAL EXPECTED

Where:

parmvalue
The specified parameter value.

Explanation: The value specified for the TOD parameter in the job control language (JCL) for the IPTPRT utility is not valid. This parameter requires a hexadecimal value.

System Action: The postprocessor request is rejected.

User Response: Do the following:

  1. Update the EXEC statement in the JCL for the IPTPRT utility, and specify a valid hexadecimal value for the TOD parameter.
  2. Run the JCL again.

See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.

IPTS0008EINVALID VALUE parmvalue, IP ADDRESS EXPECTED

Where:

parmvalue
The specified parameter value.

Explanation: The value specified for the DIP or SIP parameter in the job control language (JCL) for the IPTPRT utility is not valid. These parameters require an Internet Protocol (IP) address in dotted decimal form.

System Action: The postprocessor request is rejected.

User Response: Do the following:

  1. Update the EXEC statement in the JCL for the IPTPRT utility, and specify a valid IP address for the DIP or SIP parameter.
  2. Run the JCL again.

See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.

IPTS0009EINVALID VALUE parmvalue, TCP FLAG EXPECTED

Where:

parmvalue
The specified parameter value.

Explanation: The value specified for the FLAG parameter in the job control language (JCL) for the IPTPRT utility is not valid. This parameter requires a valid TCP flag.

System Action: The postprocessor request is rejected.

User Response: Do the following:

  1. Update the EXEC statement in the JCL for the IPTPRT utility, and specify a valid TCP flag for the FLAG parameter.
  2. Run the JCL again.

See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.

IPTS0010EINVALID VALUE parmvalue, PROTOCOL EXPECTED, USE TCP, UDP, OR ICMP

Where:

parmvalue
The specified parameter value.

Explanation: The value specified for the PROT parameter in the job control language (JCL) for the IPTPRT utilitiy is not valid. This value must be TCP, UDP, or ICMP.

System Action: The postprocessor request is rejected.

User Response: Do the following:

  1. Update the EXEC statement in the JCL for the IPTPRT utility, and specify TCP, UDP, or ICMP for the PROT parameter.
  2. Run the JCL again.

See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.

IPTS0011EINVALID VALUE parmvalue, TIME EXPECTED IN HH:MM:SS FORMAT

Where:

parmvalue
The specified parameter value.

Explanation: The value specified for the TIME parameter in the job control language (JCL) for the IPTPRT utility is not valid.

System Action: The postprocessor request is rejected.

User Response: Do the following:

  1. Update the EXEC statement in the JCL for the IPTPRT utility, and specify a valid value for the TIME parameter. Ensure the value specified is in the form HH:MM:SS.
  2. Run the JCL again.

See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.