gtpm4m1k | Messages (System Error and Offline) |
IOD004 | xxxx ADDRESS INVALID FOR yyyy |
Where:
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:
IOD006 | NUMBER OF 37X5S PLUS THE NUMBER OF SCTCS EXCEEDS TABLE SIZE OF xxx - ENTRY IGNORED |
Where:
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:
IOD008 | IOADR PARAMETER INVALID FOR DVTYP = xxxx. |
Where:
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:
IOD015 | DUPLICATE IOADR=xx - IODEV IGNORED |
Where:
Severity: 5
Explanation: An IODEV was already coded with IOADR=xx.
System Action: None.
User Response: Do the following:
IOD016 | WHEN DVTYP=xxxx - IOADR SHOULD BE y HEXADECIMAL DIGITS. |
Where:
Severity: 5
Explanation: The number of digits specified for the device address is incorrect for this device type:
System Action: None.
User Response: Do the following:
IOD017 | A MAXIMUM OF xxxx IODEV MACROS DEFINING DASD IS ALLOWED |
Where:
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:
IOD018 | THE dev ADDRESS yyyy WILL DUPLICATE THE PREVIOUSLY DEFINED ADDRESS zzzz |
Where:
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:
System Action: None.
User Response: Do the following:
IOD019 | THE 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.
IPE00001I | INVALID 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:
See TPF Operations for more information about the real-time disk formatter.
IPE00002I | FIRST 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:
See TPF Database Reference for more information about the real-time disk formatter.
IPE00003I | TRIED 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:
See TPF Database Reference for more information about the real-time disk formatter.
IPE00004W | EOF 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:
See TPF Database Reference for more information about the real-time disk formatter.
IPE00005I | NO 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:
See TPF Database Reference for more information about the real-time disk formatter.
IPE00006I | ADDRESS 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.
IPE00007I | ERROR 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.
IPE00009I | ADDRESSES 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.
IPE00010I | UNRECOVERABLE 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.
IPE00011I | DA 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.
IPE00012I | PREVIOUS 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.
IPE00013I | AVAILABLE 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.
IPE00014I | ERROR 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.
IPE00015I | DASD 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.
IPE00016I | INVALID 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.
IPE00030I | VTOC 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.
IPE00031I | THIS 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.
IPTS0000I | PROCESSED numrec FILE RECORDS, SELECTED numentry TRACE ENTRIES |
Where:
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.
IPTS0001E | ERROR OPENING FILE filename |
Where:
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:
See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.
IPTS0002E | ERROR READING FILE filename |
Where:
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:
See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.
IPTS0003E | ERROR CLOSING FILE filename |
Where:
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:
See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.
IPTS0004E | INVALID PARAMETER: parameter |
Where:
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:
See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.
IPTS0005E | INVALID VALUE parmvalue, DATE EXPECTED IN MMMDD FORMAT |
Where:
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:
See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.
IPTS0006E | INVALID VALUE parmvalue, DECIMAL EXPECTED |
Where:
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:
See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.
IPTS0007E | INVALID VALUE parmvalue, HEXADECIMAL EXPECTED |
Where:
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:
See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.
IPTS0008E | INVALID VALUE parmvalue, IP ADDRESS EXPECTED |
Where:
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:
See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.
IPTS0009E | INVALID VALUE parmvalue, TCP FLAG EXPECTED |
Where:
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:
See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.
IPTS0010E | INVALID VALUE parmvalue, PROTOCOL EXPECTED, USE TCP, UDP, OR ICMP |
Where:
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:
See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.
IPTS0011E | INVALID VALUE parmvalue, TIME EXPECTED IN HH:MM:SS FORMAT |
Where:
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:
See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.