gtpm4m1oMessages (System Error and Offline)

OLDR-ONL0

OLDR0001TCOLR_OPEN_ERROR: UNABLE TO OPEN dataset -- JOB ABORTED

Where:

dataset
The name of the data set or member.

Explanation: The data set or member could not be opened.

System Action: The E-type loader offline job is aborted and the C language run-time library issues a message to indicate the reason for the error.

User Response: Do the following:

  1. Refer to the message that was issued by the C language run-time library for information about the error.
  2. If the problem continues, check for a JCL error or a hardware problem.

See TPF System Installation Support Reference for more information.

OLDR0002TCOLR_READ_ERROR: UNABLE TO READ/SEEK dataset -- JOB ABORTED

Where:

dataset
The name of the data set or member.

Explanation: A critical input/output (I/O) error was encountered while trying to read or seek the data set or member.

System Action: The E-type loader offline job is aborted and the C language run-time library issues a message to indicate the reason for the error.

User Response: Do the following:

  1. Refer to the message that was issued by the C language run-time library for information about the error.
  2. If the problem continues, check for a hardware problem.

See TPF System Installation Support Reference for more information.

OLDR0003TCOLR_WRITE_ERROR: UNABLE TO WRITE dataset -- JOB ABORTED

Where:

dataset
The name of the data set or member.

Explanation: A critical input/output (I/O) error was encountered while trying to write to the data set or member.

System Action: The E-type loader offline job is aborted and the C language run-time library issues a message to indicate the reason for the error.

User Response: Do the following:

  1. Refer to the message that was issued by the C language run-time library for information about the error.
  2. If the problem continues, check for a hardware problem.

See TPF System Installation Support Reference for more information.

OLDR0004TCOLR_OBJECT_ERROR: READ ERROR -- OBJECT MODULE modname -- JOB ABORTED

Where:

modname
The name of the object module.

Explanation: A critical input/output (I/O) error was encountered while trying to read the object module that is currently being processed.

System Action: The E-type loader offline job is aborted and the C language run-time library issues a message to indicate the reason for the error.

User Response: Do the following:

  1. Refer to the message that was issued by the C language run-time library for information about the error.
  2. If the problem continues, check for a hardware problem.

See TPF System Installation Support Reference for more information.

OLDR0004ECOLR_OBJECT_ERROR: READ ERROR -- OBJECT MODULE modname -- LOADSET IGNORED

Where:

modname
The name of the object module.

Explanation: A critical input/output (I/O) error was encountered while trying to read the object module that is currently being processed.

System Action: The loadset that is currently being processed by the E-type loader offline job is rejected.

User Response: Do the following:

  1. Determine the cause of the error for the object module.
  2. Correct the error.

See TPF System Installation Support Reference for more information.

OLDR0005TCOLR_OBJECT_ERROR: PREMATURE EOF IN modname -- JOB ABORTED

Where:

modname
The name of the object module.

Explanation: A premature end-of-file (EOF) was encountered in the object module that is currently being processed.

System Action: The E-type loader offline job is aborted and the C language run-time library issues a message to indicate the reason for the error.

User Response: Do the following:

  1. Run the system allocator offline utility (SALO) again to generate a new program allocation table (PAT) and a new system allocator (SAL) table.
  2. Refer to the message that was issued by the C language run-time library for information about the error.

See TPF System Installation Support Reference for more information.

OLDR0005ECOLR_OBJECT_ERROR: PREMATURE EOF IN modname -- LOADSET IGNORED

Where:

modname
The name of the object module.

Explanation: A premature end-of-file (EOF) was encountered in the object module that is currently being processed.

System Action: The loadset that is currently being processed by the E-type loader offline job is rejected.

User Response: Do the following:

  1. Determine the cause of the error for the object module.
  2. Correct the error.
  3. Generate that object module again if necessary.

See TPF System Installation Support Reference for more information.

OLDR0006TCOLR_OBJECT_ERROR: OBJECT MODULE modname IS GREATER THAN ITS MAXIMUM PERMITTED SIZE -- JOB ABORTED

Where:

modname
The name of the object module.

Explanation: The machine language text of the object module currently being processed exceeds the maximum length allowed for that object module.

System Action: The E-type loader offline job is aborted and the C language run-time library issues a message to indicate the reason for the error.

User Response: Do the following:

  1. Run the system allocator offline utility (SALO) again to generate a new program allocation table (PAT) and a new system allocator (SAL) table.
  2. Refer to the message that was issued by the C language run-time library for information about the error.

See TPF System Installation Support Reference for more information.

OLDR0006ECOLR_OBJECT_ERROR: OBJECT MODULE modname IS GREATER THAN ITS MAXIMUM PERMITTED SIZE -- LOADSET IGNORED

Where:

modname
The name of the object module.

Explanation: The machine language text of the object module currently being processed exceeds the maximum length allowed for that object module.

System Action: The loadset that is currently being processed by the E-type loader offline job is rejected.

User Response: Do the following:

  1. Determine the cause of the error for the object module.
  2. Correct the error.
  3. Generate that object module again if necessary.

See TPF System Installation Support Reference for more information.

OLDR0007TCOLR_OBJECT_ERROR: INVALID CARD FOUND IN modname -- JOB ABORTED

Where:

modname
The name of the object module.

Explanation: An incorrect card was detected in the object module that is currently being processed.

System Action: The E-type loader offline job is aborted and the C language run-time library issues a message to indicate the reason for the error.

User Response: Do the following:

  1. Run the system allocator offline utility (SALO) again to generate a new program allocation table (PAT) and a new system allocator (SAL) table.
  2. Refer to the message that was issued by the C language run-time library for information about the error.

See TPF System Installation Support Reference for more information.

OLDR0007ECOLR_OBJECT_ERROR: INVALID CARD FOUND IN modname -- LOADSET IGNORED

Where:

modname
The name of the object module.

Explanation: An incorrect card was detected in the object module that is currently being processed.

System Action: The loadset that is currently being processed by the E-type loader offline job is rejected.

User Response: Do the following:

  1. Determine the cause of the error for the object module.
  2. Correct the error.
  3. Generate that object module again if necessary.

See TPF System Installation Support Reference for more information.

OLDR0008TOLDR_ERASE_FOM: FINAL OUTPUT MEDIA HAS NO VALID LOADSETS AND HAS NO COMPACTED PAT -- MEDIA DELETED

Explanation: The E-type loader offline job determined that the final output media would not contain a compacted program allocation table (PAT) or any programs or loadsets.

System Action: The final output media is deleted to prevent it from being used during an online load.

User Response: Do the following:

  1. Refer to the output report to determine which loadsets caused the error and correct the problem.
  2. Correct any errors in the input load deck.

See TPF System Installation Support Reference for more information.

OLDR0009TCOLR_NO_MEMORY: UNABLE TO ALLOCATE nnnnnn BYTES STORAGE -- JOB ABORTED

Where:

nnnnnn
The number of bytes of storage that were requested.

Explanation: The requested storage could not be allocated.

System Action: The E-type loader offline job is aborted.

User Response: Do the following:

  1. Increase the region size of the job in the JCL.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0010TCOLR_EXTRACT_SSID: INVALID SYSID= CARD -- JOB ENDED

Explanation: The syntax of the subsystem ID card is not correct. The subsystem ID can contain between 1 and 4 uppercase alphanumeric characters.

System Action: The E-type loader offline job is ended.

User Response: Do the following:

  1. Correct the syntax of the subsystem ID card.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0011TOLDR_VERIFY_CARD_SEQUENCE: 1ST CARD READ NOT SYSID=XXXX CARD -- JOB ENDED

Explanation: The first card in the input load deck is not the subsystem ID card.

System Action: The E-type loader offline job is ended.

User Response: Do the following:

  1. Place the subsystem ID card first in the input load deck.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0012TCOLR_OBTAIN_PAT_VERSION: INVALID PATVERS= CARD -- JOB ENDED

Explanation: The syntax of the program allocator table (PAT) card is not correct. The program version can contain 1 or 2 uppercase alphanumeric characters.

System Action: The E-type loader offline job is ended.

User Response: Do the following:

  1. Correct the syntax of the PAT card.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0014TCOLR_LOAD_SAL_TABLE: INVALID SALVERS= CARD -- JOB ENDED

Explanation: The syntax of the system allocator (SAL) card is not correct.

System Action: The E-type loader offline job is ended.

User Response: Do the following:

  1. Correct the syntax of the SAL card.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0015TCOLR_LOAD_SAL_TABLE: CORE ALLOCATION EXCEEDED FOR SALTBL READ -- JOB ABORTED

Explanation: The TPF linkage editor (LEDT) could not allocate the storage for the system allocator (SAL) table.

System Action: The E-type loader offline job is aborted and a dump is generated.

User Response: Do the following:

  1. Refer to the dump to determine the cause of the error.
  2. Increase the region size of the job.
  3. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0016TCOLR-LOAD_SAL_TABLE: INVALID RET CODE OF code FROM LEDT -- JOB ABORTED

Where:

code
The condition code.

Explanation: An unknown condition code was returned from the TPF linkage editor (LEDT).

System Action: The E-type loader offline job is aborted and a dump is generated.

User Response: Refer to the dump to determine the cause of the error.

See TPF System Installation Support Reference for more information.

OLDR0017TOLDR_VERIFY_CARD_SEQUENCE: 3RD CARD READ NOT SALVERS=XX CARD -- JOB ENDED

Explanation: The third card in the input load deck is not the system allocator (SAL) card.

System Action: The E-type loader offline job is ended.

User Response: Do the following:

  1. Place the SAL card third in the input load deck.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0018TOLDR_CALL_LOAD_SAL_TABLE: SALTBL AND PAT TIMESTAMPS DO NOT MATCH, IMPROPER VERSION BEING USED -- JOB ENDED

Explanation: The headers of the system allocator (SAL) table and the program allocation table (PAT) contain different time stamps. This indicates that the SAL table and the PAT were created by different system allocator offline utility (SALO) jobs.

System Action: The E-type loader offline job is ended.

User Response: Run the job again by using the correct versions of the SAL and the PAT.

See TPF System Installation Support Reference for more information.

OLDR0019TCOLR_READ_PAT_INTO_CORE: modname TXT LENGTH IS GREATER THAN ESD LENGTH -- JOB ABORTED

Where:

modname
The name of the object module.

Explanation: The machine language text of the object module currently being processed is greater than the module length attribute specified on the first external symbol dictionary (ESD) card that was submitted for the object module.

System Action: The E-type loader offline job is aborted.

User Response: Do the following:

  1. Refer to the dump to determine the cause of the error.
  2. Correct the error.
  3. Run the system allocator offline utility (SALO) again to create a new system allocator (SAL) table and a new program allocation table (PAT).

See TPF System Installation Support Reference for more information.

OLDR0020EOLDR_VALIDATE_LOADSET_CARD: lsname IS NOT A VALID LOADSET NAME -- LOADSET IGNORED

Where:

lsname
The name of the loadset.

Explanation: The loadset name specified on the loadset card contains characters that are not valid, or the loadset card does not contain a blank character in the proper columns.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Correct the loadset card.
  2. Run the job again.

See TPF System Installation Support Reference for more information.

OLDR0021EOLDR_VALIDATE_LOADSET_CARD: lsname EXCEEDS 8 CHARACTERS -- LOADSET IGNORED

Where:

lsname
The name of the loadset.

Explanation: The loadset name specified on the loadset card contains more than 8 characters.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Ensure that the loadset name specified on the Loadset card contains between 5 and 8 alphanumeric characters.
  2. Run the job again.

See TPF System Installation Support Reference for more information.

OLDR0022EOLDR_VALIDATE_LOADSET_CARD: lsname IS LESS THAN 5 CHARACTERS -- LOADSET IGNORED

Where:

lsname
The name of the loadset.

Explanation: The loadset name specified on the loadset card contains less than 5 characters.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Ensure that the loadset name specified on the Loadset card contains between 5 and 8 alphanumeric characters.
  2. Run the job again.

See TPF System Installation Support Reference for more information.

OLDR0023EOLDR_CHECK_FOR_DUP_LOADSET: DUPLICATE OF LOADSET lsname ALREADY EXISTS -- PRIOR LOADSET IGNORED

Where:

lsname
The name of the loadset.

Explanation: The loadset currently being processed by the E-type loader offline job was previously processed by the E-type loader offline job.

System Action: The loadset that was previously processed by the E-type loader offline job is deleted and is replaced with a loadset that is currently being processed by the E-type loader offline job.

User Response: Do the following:

  1. Determine the cause of the error.
  2. Correct the loadset card.
  3. Submit the job again if necessary.

See TPF System Installation Support Reference for more information.

OLDR0024EOLDR_CHECK_FOR_EMPTY_LOADSET: LOADSET lsname IS EMPTY -- LOADSET IGNORED

Where:

lsname
The name of the loadset.

Explanation: The Loadset card that was previously processed by the E-type loader offline job was not followed by any call program cards.

System Action: The previous loadset is rejected.

User Response: Do the following:

  1. Correct the input cards in the input load deck.
  2. Submit the job again, if necessary.

See TPF System Installation Support Reference for more information.

OLDR0030ECOLR_PROCESS_PROGRAM: progname_version KEYPOINT CANNOT BE LOADED -- LOADSET IGNORED

Where:

progname_version
The name and version of the program.

Explanation: The program currently being processed by the E-type loader offline job is actually a keypoint and cannot be loaded by the E-type loader.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Remove the call program card of the keypoint from the input load deck.
  2. Submit the job again.
  3. Use the auxiliary loader to load the keypoint.

See TPF System Installation Support Reference for more information.

OLDR0031ECOLR_PROCESS_PROGRAM: progname_version IS A DRIVER PROGRAM, CANNOT BE LOADED -- LOADSET IGNORED

Where:

progname_version
The name and version of the program.

Explanation: The program currently being processed by the E-type loader offline job is a driver program or a program test vehicle (PTV) program and cannot be loaded by the E-type loader.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Remove the call program card of the program from the input load deck.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0032ECOLR_VALIDATE_PROGRAM_CARD: INVALID CARD SYNTAX -- LOADSET IGNORED

Explanation: The current call program card does not contain a blank character in the proper column.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Correct the call program card.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0033ECOLR_VALIDATE_PROGRAM_CARD: progname_version CONTAINS ILLEGAL CHARACTERS -- LOADSET IGNORED

Where:

progname_version
The name and version of the program.

Explanation: The program name and version specified on the current call program card is not valid for one or more of the following reasons:

System Action: The loadset is rejected.

User Response: Do the following:

  1. Correct the call program card.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0034ECOLR_VALIDATE_PROGRAM_CARD: progname_version NOT 6 CHARACTERS LONG -- LOADSET IGNORED

Where:

progname_version
The name and version of the program.

Explanation: The program name and version specified on the current call program card cannot contain more than six alphanumeric characters.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Correct the call program card.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0035ECOLR_VALIDATE_PROGRAM_CARD: progname NOT ALLOWED TO BE LOADED -- LOADSET IGNORED

Where:

progname
The name of the program.

Explanation: The program specified on the current call program card cannot be loaded by the E-type loader.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Remove the call program card of the program from the input load deck.
  2. Submit the job again.
  3. Use the auxiliary loader or the general file loader to load the program.

See TPF System Installation Support Reference for more information.

OLDR0036ECOLR_PROCESS_PROGRAM_OBJMOD: progname_version OBJECT MODULE NOT FOUND OR COULD NOT BE OPENED -- LOADSET IGNORED

Where:

progname_version
The name and version of the program.

Explanation: One of the following errors occurred:

System Action: The loadset is rejected.

User Response: Do the following:

  1. Assemble the program again.
  2. Submit the job again.
  3. Check for a hardware error if the problem continues.

See TPF System Installation Support Reference for more information.

OLDR0037ECOLR_PROCESS_PROGRAM_OBJMOD: progname_version IS GREATER THAN 4K -- LOADSET IGNORED

Where:

progname_version
The name and version of the program.

Explanation: The length of the program currently being processed by the E-type loader offline job is too big to fit in the program buffer. The size of the buffer is 4 K bytes plus 24 bytes. The extra 24 bytes takes into account the header in C language programs and pre-4.1 assembler language programs.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Change the size of the program to be less than 4 K bytes.
  2. Assemble the program again.
  3. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0038ECOLR_PROCESS_PROGRAM_OBJMOD: modname TXT LENGTH IS GREATER THAN ESD LENGTH -- LOADSET IGNORED

Where:

modname
The name of the object module.

Explanation: The machine language text of the object module currently being processed is greater than the module length attribute specified on the first external symbol dictionary (ESD) card.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Determine the cause of the error.
  2. Assemble the program again.
  3. Run the job again.

See TPF System Installation Support Reference for more information.

OLDR0039ECOLR_LINK_EDIT_PROGRAM: INVALID REQUEST TO LEDT -- LOADSET IGNORED

Explanation: The request indicator used to call the TPF linkage editor (LEDT) was not valid.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Ensure that the proper versions of LEDT, OLDR, and COLR were link edited together.
  2. If the problem continues, see your IBM service representative.

See TPF System Installation Support Reference for more information.

OLDR0040WCOLR_LINK_EDIT_sPROGRAM: progname NOT FOUND IN THE SAL TABLE -- PROGRAM LOADED ANYWAY

Where:

progname
The name of the program.

Explanation: The TPF linkage editor (LEDT) determined that the program currently being processed by the E-type loader offline job was not allocated.

System Action: The unallocated program is loaded.

User Response: Do the following:

  1. Determine whether or not the program should be allocated.
  2. If the program should be allocated, allocate the program and then run the system allocator offline utility (SALO) again.

See TPF System Installation Support Reference for more information.

OLDR0041WCOLR_LINK_EDIT_PROGRAM: progname_version CONTAINS UNRESOLVED VCONS: vcon vcon vcon ... vcon -- PROGRAM LOADED ANYWAY

Where:

progname_version
The name and version of the program.

vcon
An unresolved V-type constant.

Explanation: The TPF linkage editor (LEDT) determined that the program currently being processed by the E-type loader offline job contains unresolved V-type constants.

System Action: The program is loaded.

User Response: Determine whether the V-type constants should be resolved.

See TPF System Installation Support Reference for more information.

OLDR0042ECOLR_LINK_EDIT_PROGRAM: progname_version MAXIMUM # OF VCONS EXCEEDED -- LOADSET IGNORED

Where:

progname_version
The name and version of the program.

Explanation: The program currently being processed by the E-type loader offline job contains more V-type constants than the TPF linkage editor (LEDT) is able to process.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Determine the cause of the unresolved V-type constants.
  2. Take the appropriate action to correct the error.

See TPF System Installation Support Reference for more information.

OLDR0043ECOLR_LINK_EDIT_PROGRAM: progname_version IS NOT AN E-TYPE PROGRAM -- LOADSET IGNORED

Where:

progname_version
The name and version of the program.

Explanation: The TPF linkage editor (LEDT) determined that the program currently being processed by the E-type loader offline job cannot be loaded by the E-type loader because it is not an E-type program.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Remove the call program card of the program from the input load deck.
  2. Submit the job again.
  3. Use the auxiliary loader or the general file loader to load the program.

See TPF System Installation Support Reference for more information.

OLDR0044ECOLR_LINK_EDIT_PROGRAM: progname_version IS A NON-ZERO TRANSFER VECTOR -- LOADSET IGNORED

Where:

progname_version
The name and version of the program.

Explanation: The TPF linkage editor (LEDT) determined that the program currently being processed by the offline loader cannot not be loaded by the E-type loader because it is a transfer vector. Only the parent program can be loaded.

System Action: The loadset is rejected.

User Response: Do one of the following:

See TPF System Installation Support Reference for more information.

OLDR0045ECOLR_LINK_EDIT_PROGRAM: progname_version IS ALLOCATED AS DUMMY RESIDENT -- LOADSET IGNORED

Where:

progname_version
The name and version of the program.

Explanation: The TPF linkage editor (LEDT) determined that the program currently being processed by the E-type loader offline job is allocated as dummy resident. The program cannot be loaded by the E-type loader.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Remove the call program card of the program from the input load deck.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0046ECOLR_LINK_EDIT_PROGRAM: BEGIN HEADER DOES NOT MATCH progname -- LOADSET IGNORED

Where:

progname
The name of the program.

Explanation: The begin header of the program currently being processed by the E-type loader offline job is different from the name specified on the call program card.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Ensure that the begin header of the program is the same as the name specified on the call program card.
  2. Assemble the program again if necessary.
  3. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0047WCOLR_LINK_EDIT_PROGRAM: progname_version ILLEGAL Z1 VCON REFERENCE DETECTED -- PROGRAM LOADED ANYWAY

Where:

progname_version
The name and version of the program.

Explanation: The TPF linkage editor (LEDT) determined that the program currently being processed by the E-type loader offline job contains an illegal reference to a Z1 V-type constant.

System Action: The program is loaded.

User Response: Do the following:

  1. Remove from the program the code that calculates the file address of the program based on the Z1 V-type constant.
  2. Assemble the program again.
  3. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0048WCOLR_LINK_EDIT_PROGRAM: progname_version ILLEGAL Z1 VCON REFERENCE DETECTED AND UNRESOLVED VCONS WERE FOUND: vcon vcon vcon ... vcon -- PROGRAM LOADED ANYWAY

Where:

progname_version
The name and version of the program

vcon
An unresolved V-type constant.

Explanation: The TPF linkage editor (LEDT) determined that the program currently being processed by the E-type loader offline job contains an illegal reference to a Z1 V-type constant. The program also contains unresolved V-type constants.

System Action: The program is loaded.

User Response: Do the following:

  1. Remove from the program the code that calculates the file address of the program based on the Z1 V-type constant.
  2. Determine whether the V-type constants should be resolved.
  3. Assemble the program again.
  4. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0049ECOLR_LINK_EDIT_PROGRAM: code UNKNOWN LEDT ERROR OCCURRED -- LOADSET IGNORED

Where:

code
The condition code.

Explanation: An unknown condition code was returned from the TPF linkage editor (LEDT).

System Action: The loadset is rejected.

User Response: Do the following:

  1. Ensure that the proper versions of the LEDT, OLDR, and COLR were link edited together.
  2. If the problem continues, see your IBM service representative.

See TPF System Installation Support Reference for more information.

OLDR0050WCOLR_CHECK_FOR_DUP_PROGRAMS: progname HAS ALREADY BEEN PROCESSED -- PRIOR PROGRAM WILL BE REMOVED

Where:

progname
The name of the program.

Explanation: The program currently being processed by the E-type loader offline job was previously processed by the E-type loader offline job for this loadset.

System Action: The program that was previously processed by the E-type loader offline job is deleted and is replaced with the program that is currently being processed by the E-type loader offline job.

User Response: Do the following:

  1. Ensure that the proper version of the program is being loaded.
  2. Correct the call program cards in the input load deck if necessary.
  3. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0060ECOLR_VALIDATE_PATCH_CARD: INVALID PATCH CARD SYNTAX FOR progname_version -- LOADSET IGNORED

Where:

progname_version
The name and version of the program being patched.

Explanation: The patch card currently being processed by the E-type loader offline job does not contain a blank character in the proper columns, or the patch card does not contain the string 001 in the proper columns.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Correct the patch card.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0061ECOLR_VALIDATE_PATCH_CARD: PATCH CARD IS NOT APPLICABLE FOR progname_version -- LOADSET IGNORED

Where:

progname_version
The name and version of the program.

Explanation: The name of the patch card currently being processed by the E-type loader offline job does not match the name of the program currently being patched.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Correct the patch card.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0062ECOLR_VALIDATE_PATCH_CARD: PATCH FOR progname_version DATA FIELDS NOT HEX -- LOADSET IGNORED

Where:

progname_version
The name and version of the program being patched.

Explanation: The data on the patch card or the starting address fields on the patch card currently being processed by the E-type loader offline job are not specified in hexadecimal characters.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Correct the patch card.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0063ECOLR_PATCH_CARD: PATCH FOR progname_version NOT ON HALFWORD BOUNDARY -- LOADSET IGNORED

Where:

progname_version
The name and version of the program being patched.

Explanation: The relative starting address of the area to patch is not on a halfword boundary.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Correct the relative starting address on the patch card.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0064ECOLR_PATCH_CARD: PATCH FOR progname_version INSIDE PROGRAM HEADER -- LOADSET IGNORED

Where:

progname_version
The name and version of the program.

Explanation: The relative starting address of the area to patch is within the header of the program being patched.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Correct the relative starting address on the patch card.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0065ECOLR_PATCH_CARD: PATCH FOR progname_version BEYOND MAXIMUM LENGTH OF nnnn BYTES -- LOADSET IGNORED

Where:

progname_version
The name and version of the program being patched

nnnn
is the maximum size of the program.

Explanation: The relative starting address of the area to patch or the number of bytes to patch extends beyond the maximum size of the program.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Correct the relative starting address or the number of bytes to patch on the patch card.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0070WOLDR_VERIFY_CARD_SEQUENCE: CARD OUT OF SEQUENCE -- CARD IGNORED

Explanation: One of the following errors occurred:

System Action: The input card is ignored.

User Response: Do the following:

  1. Correct the input cards in the input load deck.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0071EOLDR_VERIFY_CARD_SEQUENCE: CARD OUT OF SEQUENCE -- LOADSET IGNORED

Explanation: One of the following situations occurred:

System Action: The loadset is rejected.

User Response: Do the following:

  1. Correct the input cards in the input load deck.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0075ICOLR_BUILD_COMPACTED_PAT: IPATversion SUCCESSFULLY PROCESSED AND COMPACTED PAT BUILT ON FILE

Where:

version
The version of the object module currently being processed.

Explanation: The program allocator table (PAT) card was processed successfully by the E-type loader offline job, and the compacted PAT was constructed in a temporary data set.

System Action: The E-type loader offline job continues to run.

User Response: None.

See TPF System Installation Support Reference for more information.

OLDR0076ECOLR_PROCESS_PROGRAM: progname_version IS GREATER THAN 4K -- LOADSET IGNORED

Where:

progname_version
The name and version of the program.

Explanation: The length of the program currently being processed by the E-type loader offline job is greater than 4 K bytes.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Change the size of the program to be less than 4 K bytes.
  2. Assemble the program again.
  3. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0077ICOLR_BLD_TIMESTAMP: TIMESTAMP RECORD WRITTEN TO FILE

Explanation: The E-type loader (OLDR) tried to get the amount of storage specified by the CLMSIZE parameter (or the default amount, if CLMSIZE was not specified) and was unable to obtain that storage.

System Action: Processing stops.

User Response: Reduce the amount of storage on the CLMSIZE parameter.

OLDR0078EOLDR_CALL_PROCESS_PATCH: xxxxxx IS AN ISOC LOAD MODULE PATCHES CANNOT BE APPLIED -- LOADSET IGNORED

Where:

xxxxxx
The name and version of the C load module.

Explanation: The offline loader found a REP card for a program that is a C load module.

System Action: The loadset is ignored and processing continues with the next loadset.

User Response: Check the load deck and move or remove the REP card that is not supported.

OLDR0079EOLDR_CALL_PROCESS_PATCH: MAX PATCHES EXCEEDED FOR PROGRAM xxxxxx -- LOADSET IGNORED

Where:

xxxxxx
The name and version of the program.

Explanation: More than 255 REP cards are present in the load deck for the specified program.

System Action: The loadset is rejected.

User Response: Create a new version of the program so that fewer patches have to be applied.

OLDR0080ECOLR_PROCESS_LOADMOD: UNABLE TO LOAD LIBRARY cccccc TO NON-BSS SUBSYSTEM -- LOADSET IGNORED

Where:

cccccc
The name and version of the library.

Explanation: The specified library was requested to be loaded to a nonbasic subsystem (non-BSS). Libraries are only allowed in the basic subsystem (BSS).

System Action: The loadset is rejected.

User Response: Load the library in the BSS.

OLDR0081TOLDR_OBTAIN_STORAGE_AND_START: UNABLE TO ALLOCATE STORAGE FOR CLMSIZE -- JOB ABORTED

Explanation: The E-type loader (OLDR) tried to get the amount of storage specified by the CLMSIZE parameter (or the default amount, if CLMSIZE was not specified) and was unable to obtain that storage.

System Action: Processing stops.

User Response: Reduce the amount of storage on the CLMSIZE parameter.

OLDR0082EOLDR_PROCESS_LM: PROGRAM LOAD MODULE xxxxxx I/O ERROR -- LOADSET IGNORED

Where:

xxxxxx
The name and version of the load module.

Explanation: The E-type loader (OLDR) tried to load a program. While attempting to read the program into storage, an I/O error occurred.

System Action: The program is not loaded and processing continues.

User Response: Do the following:

  1. Determine why the program was not created correctly.
  2. Build the program again.

OLDR0083EOLDR_PROCESS_LM: INCORRECT RECORD IN PROGRAM LOAD MODULE xxxxxx -- LOADSET IGNORED

Where:

xxxxxx
The name and version of the load module.

Explanation: The E-type loader (OLDR) tried to load a program. While processing the program, a record was found that was either not valid or was unexpected.

System Action: The program is not loaded and processing continues.

User Response: Do the following:

  1. Determine why the program was not created correctly.
  2. Build the program again.

OLDR0084EOLDR_PROCESS_LM: DLM ENTRY POINT NOT FOUND IN PROGRAM xxxxxx -- LOADSET IGNORED

Where:

xxxxxx
The name and version of the load module.

Explanation: The E-type loader (OLDR) attempted to load a program that is a C load module. The program contained DLM startup code CSTRTD, but no entry point with the 4-character program name was found. A DLM must contain a function with the 4-character name of the program.

System Action: The loadset is rejected.

User Response: Make sure that the program was built correctly.

OLDR0085EOLDR_PROCESS_LM: STARTUP CODE MISSING FROM PROGRAM xxxxxx -- LOADSET IGNORED

Where:

xxxxxx
The name and version of the load module.

Explanation: The E-type loader (OLDR) tried to load a program that is a C load module, but the program did not contain the required startup code (CSTRTD or CSTRTL).

System Action: The program is not loaded and processing continues.

User Response: Make sure that the program was built correctly. One of the startup routines (CSTRTD or CSTRTL) was not linked into the program correctly.

OLDR0086EOLDR_PROCESS_LM: PROGRAM LOAD MODULE xxxxxx LARGER THAN CLMSIZE -- LOADSET IGNORED

Where:

xxxxxx
The name and version of the load module.

Explanation: The E-type loader (OLDR) tried to load a program, but there was not enough memory allocated to process the program.

System Action: The program is not loaded and processing continues.

User Response: Do one of the following:

See TPF System Installation Support Reference for more information.

OLDR0087WOLDR_CALL_PROCESS_PROGRAM: progname NOT FOUND IN THE SAL TABLE -- PROGRAM LOADED ANYWAY

Where:

progname
The name of the program.

Explanation: The TPF linkage editor (LEDT) determined that the program currently being processed by the E-type loader offline job was not allocated.

System Action: The unallocated program is loaded.

User Response: Do the following:

  1. Determine if the program should be allocated.
  2. If the program should be allocated, allocate the program and then run the system allocator offline utility (SALO) again.

See TPF System Installation Support Reference for more information.

OLDR0088EOLDR_CALL_PROCESS_PROGRAM: progname_version IS A NON-ZERO TRANSFER VECTOR -- LOADSET IGNORED

Where:

progname_version
The name and version of the program.

Explanation: The TPF linkage editor (LEDT) determined that the program currently being processed by the offline loader cannot be loaded by the E-type loader because it is a transfer vector. Only the parent program can be loaded.

System Action: The loadset is rejected.

User Response: Do one of the following:

See TPF System Installation Support Reference for more information.

OLDR0089EOLDR_CALL_PROCESS_PROGRAM: progname IS ALLOCATED AS DUMMY RESIDENT -- LOADSET IGNORED

Where:

progname
The name of the program.

Explanation: The TPF linkage editor (LEDT) determined that the program currently being processed by the E-type loader offline job is allocated as dummy resident. The program cannot be loaded by the E-type loader.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Remove the call program card of the program from the input load deck.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0090WOLDR_PROCESS_LM: C LOAD MODULE nnnnvv CONTAINS NO LINK MAP DATA - C LOAD MODULE LOADED ANYWAY

Where:

nnnnvv
The name and version of the C load module.

Explanation: You ran the offline E-type loader (OLDR) and specified a C load module that contains no link map data.

System Action: The C load module is loaded with no link map data.

User Response: If you want a link map for this C load module, do the following:

  1. Run the C load module build tool (CBLD) again.
  2. Run the offline E-type loader (OLDR) again to pick up the updated version of the C load module.

See TPF Application Programming for information about CBLD and TPF System Installation Support Reference for information about OLDR.

OLDR0091TOLDR_OBTAIN_STORAGE_AND_START: UNABLE TO ALLOCATE STORAGE FOR ADATASIZE - JOB ABORTED

Explanation: The E-type loader (OLDR) tried to get the amount of storage specified by the ADATASIZE parameter (or the default amount if the ADATASIZE parameter was not specified) and was unable to obtain that amount of storage.

System Action: Processing ends abnormally.

User Response: Do the following:

  1. Reduce the amount of storage specified for the ADATASIZE parameter.
  2. Run TPFLDR again.

See TPF System Installation Support Reference for more information about OLDR and the ADATASIZE parameter.

OLDR0092WCOLR_PROCESS_LOADMOD BUFFER ERROR OCCURRED READING ADATA FOR PROGRAM nnnnvv - PROGRAM LOADED ANYWAY

Where:

nnnnvv
The name and version of the C load module.

Explanation: The general file loader (ALDR) ran out of storage while attempting to load an ADATA file for the program being run.

System Action: The program was loaded without the ADATA file.

User Response: Do one of the following:

See TPF System Installation Support Reference for more information about ALDR and the ADATASIZE parameter.

OLDR0093WCOLR_PROCESS_LOADMOD: I/O ERROR OCCURRED READING ADATA FOR PROGRAM nnnnvv - PROGRAM LOADED ANYWAY

Where:

nnnnvv
The name and version of the C load module.

Explanation: An error occurred when the E-type loader (OLDR) attempted to read an ADATA file for the program being run.

System Action: The program was loaded without the ADATA file.

User Response: Do one of the following:

See TPF System Installation Support Reference for more information about OLDR.

OLDR0094WOLDR_CALL_PROCESS_PROGRAM: BUFFER ERROR OCCURRED READING ADATA FOR PROGRAM progname_version - PROGRAM LOADED ANYWAY

Where:

progname_version
The name and version of the program.

Explanation: The E-type loader (OLDR) ran out of storage while attempting to load an ADATA file for the program being run.

System Action: The program was loaded without the ADATA file.

User Response: Do one of the following:

See TPF System Installation Support Reference for more information about OLDR and the ADATASIZE parameter.

OLDR0095WOLDR_CALL_PROCESS_PROGRAM: I/O ERROR OCCURRED READING ADATA FOR PROGRAM progname_version - PROGRAM LOADED ANYWAY

Where:

progname_version
The name and version of the program.

Explanation: An error occurred when the E-type loader (OLDR) attempted to read an ADATA file for the program being run.

System Action: The program was loaded without the ADATA file.

User Response: Do one of the following:

See TPF System Installation Support Reference for more information about OLDR.

OLDR0099ECOLR_VALIDATE_PROGRAM_CARD: USER EXIT ERROR return_code ENCOUNTERED FOR PROGRAM progname_version -- LOADSET IGNORED

Where:

return_code
The return code from the E-type loader offline user exit

progname_version
The name and version of the program.

Explanation: The program currently being processed by the E-type loader offline job was flagged by the E-type loader offline user exit as being in error.

System Action: The loadset is rejected.

User Response: Do the following:

  1. Correct the error that was flagged by the E-type loader offline user exit.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

OLDR0099WCOLR_VALIDATE_PROGRAM_CARD: USER EXIT ERROR return_code ENCOUNTERED FOR PROGRAM progname_version -- PROGRAM LOADED ANYWAY

Where:

return_code
The return code from the E-type loader offline user exit

progname_version
The name and version of the program.

Explanation: The program currently being processed by the E-type loader offline job was flagged with a warning by the E-type loader offline user exit.

System Action: The program is loaded.

User Response: Do the following:

  1. Correct the error that was flagged by the E-type loader offline user exit.
  2. Submit the job again.

See TPF System Installation Support Reference for more information.

ONL002FULLY DUPLICATED OR SELECTIVELY DUPLICATED FILE LAYOUT SPECIFIED FOR xxxx WITH ODD NUMBER OF MODULES

Where:

xxxx
The keyword that specifies a fully duplicated or selectively duplicated layout.

Severity: 5

Explanation: The number of modules was found to be an odd number. It must be an even number.

System Action: None.

User Response: Do the following:

  1. Change the number of online modules to an even number for this device type or change DUPTYPx to a nonduplicated file layout.
  2. Rerun SIP stage I.

ONL003xxxx NO MODS FOR DEVICE TYPE

Where:

xxxx
The keyword

Severity: 5

Explanation: DEVICEx operand was specified but PERMx and EXTRAx were not found.

System Action: None.

User Response: Do the following:

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

ONL007INPUT DEVICE TYPES DO NOT FORM A CORRECT SERIES

Severity: 5

Explanation: When DASD devices are used they must form a complete series starting with the device type A. (In other words, if three device types are used, they must be A, B, and C.)

System Action: None.

User Response: Do the following:

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

ONL009NUMBER OF CYLINDERS (y...y) FOR DEVICEx IS NOT NUMERIC

Where:

y...y
A 1 to 5 digit number that represents the number of cylinders coded for the second subparameter of the DEVICEx parameter.

Severity: 5

Explanation: This error occurred because the number of cylinders coded for the second subparameter of the DEVICEx parameter is not a decimal number.

System Action: None.

User Response: Do the following:

  1. Change the value for y...y to a decimal number or allow the number of cylinders to default.
  2. Rerun SIP stage I.

ONL010KEYPOINTING MAY NOT OCCUR IF IPLABLE IS NOT GREATER THAN 1

Severity: 5

Explanation: This warning is issued if the number of online device A prime modules is greater than 1, yet IPLABLE is equal to 1. If this is the case then fallback module keypointing will not occur.

System Action: None.

User Response: Do one of the following: