gtpm4m1s | Messages (System Error and Offline) |
TLDR0200T | ERROR DURING OPEN OF TAPEOUT |
Explanation: The offline portion of TLDR was unable to open the file specified with the TAPEOUT DDNAME. TAPEOUT is a work file used by TLDR. TLDR must be able to first write, then read 4095-byte records from TAPEOUT.
System Action: TLDR ends processing abnormally.
User Response: Do the following:
TLDR0201T | ERROR DURING WRITE TO TAPEOUT |
Explanation: The offline portion of TLDR was unable to write to the file specified with the TAPEOUT DDNAME.
System Action: TLDR ends processing abnormally.
User Response: Do the following:
TLDR0202T | ERROR DURING READ OF TAPEOUT |
Explanation: The offline portion of TLDR was unable to read from the file specified with the TAPEOUT DDNAME.
System Action: TLDR ends processing abnormally.
User Response: Do the following:
TLDR0210T | ERROR DURING OPEN OF TLDROUT |
Explanation: The offline portion of TLDR was unable to open the file specified with the TLDROUT DDNAME. TLDROUT is the output file that will contain the program objects found in the load deck. TLDR must be able to write 4095-byte records to TLDROUT.
System Action: TLDR ends processing abnormally.
User Response: Do the following:
TLDR0211T | ERROR DURING WRITE TO TLDROUT |
Explanation: The offline portion of TLDR was unable to write to the file specified with the TLDROUT DDNAME.
System Action: TLDR ends processing abnormally.
User Response: Do the following:
TLDR0402T | ERROR DURING BLDL FOR ADATAIN |
Explanation: An error occurred when the offline portion of auxiliary loader (TLDR) attempted to call the BLDL service for the ADATAIN data definition name.
System Action: TLDR processing ends abnormally.
User Response: Do one of the following:
See TPF System Installation Support Reference for more information about TLDR and the ADATAIN DD card.
TPFL0002W | TLDR ALREADY SPECIFIED |
Explanation: In the EXEC PGM line of the loader JCL, ALDR, or OLDR was specified after TLDR had already been specified. You can specify only 1 loader.
System Action: The program ignores the parameter and processing continues.
User Response: Correct the JCL.
TPFL0003W | ALDR ALREADY SPECIFIED |
Explanation: In the EXEC PGM line of the loader JCL, TLDR, or OLDR was specified after ALDR had already been specified. You can specify only 1 loader.
System Action: The program ignores the parameter and processing continues.
User Response: Correct the JCL.
TPFL0004W | OLDR ALREADY SPECIFIED |
Explanation: In the EXEC PGM line of the loader JCL, ALDR, or TLDR was specified after OLDR had already been specified. You can specify only 1 loader.
System Action: The program ignores the parameter and processing continues.
User Response: Correct the JCL.
TPFL0005W | TRACE SUBPARAMETER NOT VALID - TRACE(OFF) ASSUMED |
Explanation: The TRACE parameter on the LOAD card of the offline loader (TPFLDR) job was specified incorrectly.
System Action: The TRACE parameter is ignored. No trace data will be generated.
User Response: If you want trace data for your TPFLDR job, do the following:
See TPF System Installation Support Reference for information about loaders.
TPFL0006W | PATH NAME pathname CANNOT BE DEFINED - FORMAT IS NOT VALID |
Where:
Explanation: The Path card contained a syntax error.
System Action: No action is taken. If the specified path name is referenced by a Load FCTB card, message TPFL2003T is issued.
User Response: Do the following:
See TPF System Installation Support Reference for more information about TPFLDR and the Path card.
TPFL0007W | PATH NAME pathname CANNOT BE REDEFINED - EARLIER DEFINITION WILL BE USED |
Where:
Explanation: The path name was already defined.
System Action: The Path card is ignored.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the Path card.
TPFL0008W | PATH NAME pathname CANNOT BE DEFINED - TOO MANY PATH CARDS SPECIFIED |
Where:
Explanation: There are too many input cards specifying the search path following the Path card.
System Action: No action is taken. If the specified path name is referenced by a Load FCTB card, message TPFL2003T is issued.
User Response: Reduce the number of input cards, specifying the search path for the specified Path card.
See TPF System Installation Support Reference for more information about the Path card.
TPFL0010E | ERROR OPENING LDRTRACE |
Explanation: TRACE(ON) was specified as a parameter and the offline loader (TPFLDR) attempted to open LDRTRACE to generate trace data. LDRTRACE could not be opened.
System Action: The TRACE parameter is ignored. No trace data will be generated.
User Response: If you want trace data for your TPFLDR job, do the following:
See TPF System Installation Support Reference for information about loaders.
TPFL1001I | DDNAME ADATAIN COULD NOT BE OPENED - ADATA WILL NOT BE LOADED |
Explanation: The offline loader was unable to open the ADATAIN data definition name, which specifies data sets that contain ADATA files.
System Action: ADATA files will not be loaded for real-time programs.
User Response: Do one of the following:
See TPF System Installation Support Reference for more information about the ADATAIN data definition card.
TPFL2001T | UNABLE TO OBTAIN STORAGE FOR PROCESSING FCTB AS A PROGRAM OBJECT |
Explanation: An error occurred when the offline loader (TPFLDR) attempted to obtain storage for processing the FACE table (FCTB) as a program object.
System Action: TPFLDR processing ends abnormally.
User Response: Do the following:
See TPF System Installation Support Reference for more information about TPFLDR.
TPFL2002T | ERROR PROCESSING FCTB AS A PROGRAM OBJECT IEWBIND FUNCTION-funcval RETCODE-rc RSNCODE-reasoncde |
Where:
Explanation: The IEWBIND macro returned an error code to TPFLDR while processing the FACE table (FCTB) as a program object.
System Action: TPFLDR processing ends abnormally.
User Response: See OS/390 DFSMS Program Management for more information about return code and reason code values. See your system programmer for additional help.
TPFL2003T | PATH NAME pathname NOT DEFINED - UNABLE TO LOAD FCTB |
Where:
Explanation: A Load FCTB card specified a search path name that was not previously defined by a Path card in the load deck.
System Action: Offline loader (TPFLDR) processing ends abnormally.
User Response: Do the following:
See TPF System Installation Support Reference for more information about TPFLDR.
TPFL2004T | FCTB vv NOT FOUND IN PATH NAME pathname - UNABLE TO LOAD FCTB |
Where:
Explanation: The FCTB could not be found in the hierarchical file system (HFS) search path specified by the path name in the Load FCTB card.
System Action: Offline loader (TPFLDR) processing ends abnormally.
User Response: Do the following:
See TPF System Installation Support Reference for more information about TPFLDR.
TPFL2005T | FCTB vv IN PATH NAME pathname EXCEEDS BUFFER SIZE - UNABLE TO LOAD FCTB |
Where:
Explanation: The FCTB is larger than the buffer allocated by the offline loader (TPFLDR).
System Action: TPFLDR processing ends abnormally.
User Response: Do the following:
See TPF System Installation Support Reference for more information about TPFLDR.