gtpm4m1l | Messages (System Error and Offline) |
LIBI0801E | INVALID LIBFUN PARAMETER @LIBFUN(plist) |
Where:
Explanation: The keyword in a library interface instruction is coded with a parameter that is not valid.
System Action: The library interface instruction is ignored and processing continues.
User Response: Correct the keyword parameter.
LIBI0802E | REQUIRED PARAMETER IS MISSING FROM @LIBFUN(plist) |
Where:
Explanation: A required parameter is omitted in the coding of a library interface instruction keyword.
System Action: The library interface instruction is ignored and processing continues.
User Response: Add the required parameter values.
LIBI0810E | INVALID LIBRARY INTERFACE INSTRUCTION |
Explanation: A library interface instruction that cannot be parsed as either a comment or a keyword instruction is processed by the library interface tool.
System Action: The library interface instruction is ignored and processing continues.
User Response: Correct or delete the library interface instruction that is not valid
LIBI0815E | DUPLICATE INTERNAL FUNCTION NAME intfunction |
Where:
Explanation: The library interface script being processed contains more than 1 valid @libfun library interface instruction that specifies the same internal function name.
System Action: The library interface instruction is ignored and processing continues.
User Response: Do the following:
LIBI0820E | DUPLICATE EXTERNAL FUNCTION NAME extfunction |
Where:
Explanation: The library interface script being processed contains more than 1 valid @libfun library interface instruction that specifies the same external function name.
System Action: The library interface instruction is ignored and processing continues.
User Response: Delete the excess @libfun instructions.
LIBI0821E | INVALID EXTERNAL FUNCTION NAME extfunction |
Where:
Explanation: The external function name specified by a @libfun library interface instruction is not a valid C identifier.
System Action: The @libfun instruction is ignored and processing continues.
User Response: Correct the external function name.
LIBI0822E | INVALID INTERNAL FUNCTION NAME intfunction |
Where:
Explanation: The internal function name specified by a @libfun library interface instruction is not a valid C identifier.
System Action: The @libfun instruction is ignored and processing continues.
User Response: Correct the internal function name.
LIBI0823E | FUNCTION ORDINAL NUMBER fordinal IS ALREADY ASSIGNED TO extfunction |
Where:
Explanation: The library interface script being processed contains more than 1 valid @libfun library interface instruction that specifies the same function ordinal number.
System Action: The library interface is not created.
User Response: Correct the library ordinal numbers.
LIBI0824E | INVALID FUNCTION ORDINAL NUMBER fordinal |
Where:
Explanation: The function ordinal number specified by a @libfun library interface instruction is not a number or is not in the 0-1023 range.
System Action: The @libfun instruction is ignored and processing continues.
User Response: Correct the function ordinal number.
LIBI1201T | SYSXV DATASET CANNOT BE OPENED FOR OUTPUT |
Explanation: The SYSXV output data set could not be opened for writing. Additional diagnostics may precede this message.
System Action: The library interface tool stops running.
User Response: Correct the SYSXV DD specification used when calling the library interface tool.
LIBI1202T | SYSCLS DATASET CANNOT BE OPENED FOR OUTPUT |
Explanation: The SYSCLS output data set could not be opened for writing. Additional diagnostics may precede this message.
System Action: The library interface tool stops running.
User Response: Correct the SYSCLS DD specification used when invoking the library interface tool.
LIBI1212T | WRITE ERROR ON SYSXV |
Explanation: An error occurred when attempting to write to SYSXV. Additional diagnostics may precede this message.
System Action: The library interface tool stops running.
User Response: Do the following:
LIBI1213T | WRITE ERROR ON SYSCLS |
Explanation: An error occurred when attempting to write to SYSCLS. Additional diagnostics may precede this message.
System Action: The library interface tool stops running.
User Response: Do the following:
LIBI1215T | FCLOSE ERROR ON SYSXV |
Explanation: An error occurred while trying to close SYSXV (LIBVEC file). The partitioned data set (PDS) or the disk may be out of space.
System Action: The library interface tool stops running. The LIBVEC file is not written to file.
User Response: Do the following:
LIBI1216T | FCLOSE ERROR ON SYSCLS |
Explanation: An error occurred while trying to close SYSCLS, which is one of the dynamic load module (DLM) stub files. The partitioned data set (PDS) or the disk may be out of space.
System Action: The library interface tool stops running and no additional DLM stubs are generated.
User Response: Do the following:
LIBI1250T | NO LIBRARY INSTRUCTION ID IS SPECIFIED |
Explanation: The library interface script being processed does not contain a @libid library interface instruction.
System Action: The input file is processed but the library interface is not created and the library interface tool stops running.
User Response: Add the correct @libid library interface instruction.
LIBI1251T | MORE THAN ONE VALID LIBRARY ID INSTRUCTION IS SPECIFIED |
Explanation: The library interface script being processed contains more than 1 valid @libid library interface instruction.
System Action: The input file is processed but the library interface is not created.
User Response: Delete the extra @libid library interface instructions.
LIBI1252T | INVALID LIBRARY ORDINAL NUMBER ordinal |
Where:
Explanation: The library ordinal number specified by the @libid library interface instruction is not a number or is not in the 0-1023 range.
System Action: The input file is processed but the library interface is not created.
User Response: Correct the library ordinal number.
LIBI1253T | REQUIRED LIBRARY ID PARAMETER IS MISSING |
Explanation: The library interface script being processed does not contain the library ordinal number, or does not contain the library ordinal name.
System Action: The input file is processed but the library interface is not created and the library interface tool stops running.
User Response: Add the correct library ordinal number or name.
LIBI1254T | INVALID LIBRARY NAME name |
Where:
Explanation: Valid library names are 4 characters long. The first character must be a letter; the other 3 characters can be letters or numbers.
System Action: The input file is processed but the library interface is not created and the library interface tool stops running.
User Response: Correct the library name.
LIBI1260T | NO FUNCTIONS ARE SPECIFIED |
Explanation: The library interface script that is being processed does not contain a valid @libfun library interface instruction.
System Action: The library interface is not created and the library interface tool stops running.
User Response: Add the correct @libfun library interface instructions.
Severity: 5
Explanation: The multipoint (MP) parameter was included in the BSCOP parameter list, but
either the CT parameter (the TPF system as control station) or the TR
parameter (the TPF system as tributary station) was not specified.
System Action: None.
User Response: Do the following:
Severity: 0
Explanation: The BSCOP keyword was coded, but BSC was not included in the TPF
system.
System Action: The BSCOP keyword is ignored.
User Response: Do the following:
Where:
Severity: 0
Explanation: The number of BSC lines specified is greater than the number of BSC drops
defined.
System Action: None.
User Response: Do the following
Severity: 5
Explanation: You specified the BSCOP keyword and did not specify any keyword parameters in
the parameter list.
System Action: None.
User Response: Do the following:
Where:
Severity: 0
Explanation: The parameter referenced in the message is not valid in the BSCOP parameter
list.
System Action: None.
User Response: None.
Where:
Severity: 0
Explanation: The parameter referenced in the message was entered more than once in the
BSCOP parameter list.
System Action: None.
User Response: None.
Severity: 5
Explanation: The CT (the TPF system as control station) parameter was included in the BSCOP
parameter list, but the multipoint (MP) parameter was not specified.
System Action: None.
User Response: Do the following:
Severity: 5
Explanation: At least one LOGTAPE must be specified.
System Action: None.
User Response: Do the following:
Severity: 5
Explanation: More than one tape was assigned to cover the same module.
System Action: None.
User Response: Do the following:
Where:
Severity: 5
Explanation: The tape device type parameter referenced in the message specifies a device
type that is not valid.
System Action: None.
User Response: Do the following:
Where:
Severity: 5
Explanation: The operand referenced in the message is in error.
System Action: None.
User Response: Do the following:
LIN002 TPF MUST BE EITHER A TRIBUTARY OR A CONTROL STATION FOR MULTIPOINT
LIN003 TPF MUST CONTAIN BSC TO SPECIFY BSC OPTIONS--IGNORED
LIN006 # of BSC DROPS DEFINED BY xxx LESS THAN #
of BSC LINES - DEFAULT SET
LIN007 AT LEAST 1 PARAMETER REQUIRED FOR BSCOP
LIN008 INVALID PARAMETER IN BSCOP -- xx PARAMETER IGNORED
LIN009 DUPLICATE PARAMETER IN BSCOP -- xx PARAMETER IGNORED
LIN010 BSC MUST BE MULTIPOINT FOR TPF TO BE A CONTROL STATION
LOG001 NO LOG TAPES SPECIFIED
LOG002 TAPE MODULE NUMBERS OVERLAP
LOG003 xxxx, yyyy PARAMETER INVALID DEVICE TYPE
LOG004 OPERAND xxxx ENDING MOD LESS THAN STARTING MOD