gtpm4m1lMessages (System Error and Offline)

LIBI-LOG0

LIBI0801EINVALID LIBFUN PARAMETER @LIBFUN(plist)

Where:

plist
The parameter list with the incorrect parameter.

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.

LIBI0802EREQUIRED PARAMETER IS MISSING FROM @LIBFUN(plist)

Where:

plist
The incomplete parameter list coded for the keyword.

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.

LIBI0810EINVALID 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

LIBI0815EDUPLICATE INTERNAL FUNCTION NAME intfunction

Where:

intfunction
The duplicated internal function name.

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:

  1. Determine if the internal function names are correct.
  2. Correct any internal function names that are incorrect.

LIBI0820EDUPLICATE EXTERNAL FUNCTION NAME extfunction

Where:

extfunction
The duplicated external function name.

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.

LIBI0821EINVALID EXTERNAL FUNCTION NAME extfunction

Where:

extfunction
The external function name that is not valid.

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.

LIBI0822EINVALID INTERNAL FUNCTION NAME intfunction

Where:

intfunction
The internal function name that is not valid.

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.

LIBI0823EFUNCTION ORDINAL NUMBER fordinal IS ALREADY ASSIGNED TO extfunction

Where:

fordinal
The multiple-assigned function ordinal number.

extfunction
The external name of the function to which the ordinal number was previously assigned.

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.

LIBI0824EINVALID FUNCTION ORDINAL NUMBER fordinal

Where:

fordinal
The function ordinal number that is not valid.

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.

LIBI1201TSYSXV 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.

LIBI1202TSYSCLS 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.

LIBI1212TWRITE 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:

  1. Determine why SYSXV could not be written.
  2. Correct the error.

LIBI1213TWRITE 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:

  1. Determine why SYSCLS could not be written.
  2. Correct the error.

LIBI1215TFCLOSE 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:

  1. Determine why the fclose function fails with SYSXV.
  2. Correct the error.
  3. Run the LIBI program again.

LIBI1216TFCLOSE 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:

  1. Determine why the fclose function fails with SYSCLS.
  2. Correct the error.
  3. Run the LIBI program again.

LIBI1250TNO 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.

LIBI1251TMORE 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.

LIBI1252TINVALID LIBRARY ORDINAL NUMBER ordinal

Where:

ordinal
The library ordinal number that is not valid.

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.

LIBI1253TREQUIRED 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.

LIBI1254TINVALID LIBRARY NAME name

Where:

name
The library name that is not valid.

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.

LIBI1260TNO 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.

LIN002TPF MUST BE EITHER A TRIBUTARY OR A CONTROL STATION FOR MULTIPOINT

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:

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

LIN003TPF MUST CONTAIN BSC TO SPECIFY BSC OPTIONS--IGNORED

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:

  1. Make the necessary corrections.
  2. Rerun SIP stage I if the assumption is not valid.

LIN006# of BSC DROPS DEFINED BY xxx LESS THAN # of BSC LINES - DEFAULT SET

Where:

xxx
The number of BSC lines defined.

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

  1. Make the necessary corrections.
  2. Rerun SIP stage I if the assumption is not valid.

LIN007AT LEAST 1 PARAMETER REQUIRED FOR BSCOP

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:

  1. Include the desired parameters in the parameter list or omit the BSCOP keyword.
  2. Rerun SIP stage I.

LIN008INVALID PARAMETER IN BSCOP -- xx PARAMETER IGNORED

Where:

xx
The name of the parameter.

Severity: 0

Explanation: The parameter referenced in the message is not valid in the BSCOP parameter list.

System Action: None.

User Response: None.

LIN009DUPLICATE PARAMETER IN BSCOP -- xx PARAMETER IGNORED

Where:

xx
The name of the parameter.

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.

LIN010BSC MUST BE MULTIPOINT FOR TPF TO BE A CONTROL STATION

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:

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

LOG001NO LOG TAPES SPECIFIED

Severity: 5

Explanation: At least one LOGTAPE must be specified.

System Action: None.

User Response: Do the following:

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

LOG002TAPE MODULE NUMBERS OVERLAP

Severity: 5

Explanation: More than one tape was assigned to cover the same module.

System Action: None.

User Response: Do the following:

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

LOG003xxxx, yyyy PARAMETER INVALID DEVICE TYPE

Where:

xxxx
The tape name.

yyyy
The device type parameter.

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:

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

LOG004OPERAND xxxx ENDING MOD LESS THAN STARTING MOD

Where:

xxxx
The name of the operand.

Severity: 5

Explanation: The operand referenced in the message is in error.

System Action: None.

User Response: Do the following:

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