gtpm4m1w | Messages (System Error and Offline) |
000000000 | zzzz nnnn ttt cuu CCx CCW--cc CSW--yyyyyyyy yyyyyyyy SNS-ssssssss ssssssss ssssssss ssssssss ssssssss ssssssss ssssssss ssssssss |
Where:
Explanation: This is the format of a tape control program hardware error message.
System Action: None.
User Response: None.
See TPF Operations for more information about the
tape support commands. See 3480 Magnetic Tape
Subsystem Operator's Guide and 3490 Magnetic
Tape Subsystem Operator's Guide for more information about the
meanings of and
Where:
Severity: 12
Explanation: The record ID cannot be a virtual file access (VFA) candidate.
System Action: None.
User Response: Noe.000000000 recordid CANNOT BE A VFA CANDIDATE
000000000 | nnnn CHAIN OVERLAYING mmmm |
Where:
Explanation: The core image restart area (CIMR) chain for the chain type referenced in the message overlays the type of CIMR referenced in the message.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | nnnnvv CONTAINS TOO MANY XTRNS, PROG NOT LOADED |
Where:
Explanation: The program contained more than the maximum number of external references.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program, the maximum number of external references, and the linkage editor (LEDT).
000000000 | xxxxxx FIND/FILE ERROR |
Where:
Explanation: This is a T type message that is sent to the printer and the console devices.
System Action: A system error dump is issued.
User Response: None.
See TPF Operations for more information about the unit record commands.
000000000 | xx,yy ILLEGAL IA. MSG EXCLUDED FROM TEST |
Where:
Explanation: An IA,LA from a message using an ILT address was not found in the appropriate table.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information about the program test vehicle (PTV).
000000000 | xx,yy INACTIVE LINE |
Where:
Explanation: The program test vehicle (PTV) intercepted a SEND-type macro from an ILT terminal address to an inactive line number.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information about the program test vehicle (PTV).
000000000 | xx,yy INACTIVE TERMINAL |
Where:
Explanation: The program test vehicle (PTV) intercepted a SEND-type macro from an ILT terminal address to an inactive terminal address.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information about the program test vehicle (PTV).
000000000 | nnnn INVALID PROGRAM LENGTH -- CARD IGNORED |
Where:
Explanation: The absolute length of the program indicated exceeds 4096.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the system allocator (SAL).
000000000 | nnnn IS A DUPLICATE ENTRY -- CARD IGNORED |
Where:
Explanation: A duplicate entry was found in the input cards of the program referenced in the message.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the system allocator (SAL).
000000000 | xxxx IS NOT IN TABLE |
Where:
Explanation: An attempt was made to fall back a program that was not in the OLD directory tables.
System Action: The fallback function request is ended.
User Response: Enter the fallback request again and specify the proper program name.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | nnnnvv IS SHOWN AS TRANSFER VECTOR IN SALTABLE -- PROGRAM NOT LOADED |
Where:
Explanation: The user specified a name in the call program card that is defined as a transfer vector to another program within the system allocator (SAL) table. The loader successfully found a module with that name in the object library. A module can only be loaded when requested by its primary (transfer vector 0) name.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | nnnnvv IS SPECIFIED AS A DUMMY PROG WITHIN THE SALTABLE -- PROGRAM IS IGNORED |
Where:
Explanation: The program is called in error or the system allocator (SAL) table is wrong.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | xxxxxxxx MEMBER NOT FOUND |
Where:
Explanation: The member referenced in the message, which was specified through a LIST option, was not found within the PDS data definition.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about variable cross referencing.
000000000 | nnnnvv NOT ON-LINE PROG....IT WAS NOT LOADED |
Where:
Explanation: The program being loaded is a batch (offline) segment. A program is considered as a batch program when it contains a V-type adcon that may not be used by the online programs. If the specified CLMSIZE is 0, ALDR processes the program as BAL or TARGET(TPF), even though the program is a C load module.
System Action: If CLMSIZE is set to 0, the offline loader skips LOADMOD DSN.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | nnnnvv OBJECT MODULE IS CORRUPTED -- MUST BE REASSEMBLED, PROGRAM LOAD IS IGNORED |
Where:
Explanation: When building the program in main storage from the object module, the loader encountered a data address that is not valid in one of the TXT cards.
System Action: None.
User Response: Reassemble the program as instructed in the error message.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | xx,yy ON LINE IA,LA. MSG EXCLUDED FROM TEST. |
Where:
Explanation: An IA,LA from a message using an ILT address is currently online.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for
more information about the program test vehicle (PTV).
Where:
Severity: 0
Explanation: The previous messages specify the number of each type of record generated in
the Phase 1 run. This is an informational message.
System Action: None.
User Response: None.
Where:
Severity: 0
Explanation: None.
System Action: None.
User Response: None.
Where:
Severity: 0
Explanation: None.
System Action: None.
User Response: None.000000000 xx PDUMP RECORDS GENERATED
000000000 xx PKST RECORDS GENERATED
000000000 xx SCK RECORDS GENERATED
000000000 | ABORT-COMPRESS RTN ERROR |
Explanation: A corrupted object deck has been encountered in the object library.
System Action: The job is abended.
User Response: Determine the last member read from the object library and create it again. You will need to reassemble or recompile the program to recreate it.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | ABORT-ERROR TRYING TO READ/WRITE A 4K RECORD -- TRACK FORMAT INVALID |
Explanation: While trying to read or write a 4 K record, the record size on the track was found to be other than 4 K.
System Action: The load ends abnormally.
User Response: Check the formatting of the loader general file (LGF).
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | ABORT-ERROR TRYING TO READ/WRITE IMAGE CONTROL RECORD -- TRA FORMAT INVALID |
Explanation: While trying to read or write the image control record (ICR), the record size on the track was found to be greater than 1 K.
System Action: The load ends abnormally.
User Response: Reformat track 1 on the loader general file (LGF) as 1 K records.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | ABORT-LOAD NOT POSSIBLE -- CTKX MISSING ON LGF |
Explanation: CTKX was not found in the loader general file (LGF) and was not specified in the load deck.
System Action: The load ends abnormally.
User Response: Run ALDR again and specify a load of CTKX in the load deck.
See TPF System Installation Support Reference for more information about loaders.
000000000 | ABORT -- TIMESTAMP MISMATCH DETECTED FOR PAT / SALTBL |
Explanation: The time stamp in the system allocator (SAL) table (SALTBL) does not match the time stamp of the program allocation table (PAT) on the loader general file (LGF) (or the PAT being loaded, if it was included in the load deck).
System Action: The load ends abnormally.
User Response: Ensure that the time stamp of the PAT and SALTBL match by doing one of the following:
See TPF System Installation Support Reference for more information about loaders.
000000000 | ACP CPUID INVALID -- PROCS xxxxxx ALLOWED |
Where:
Explanation: The CPU ID specified is not valid. The only valid processor names are those referenced in this message.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about loaders.
000000000 | A DATA FILE WAS UNSUCCESSFULLY OPENED |
Explanation: An error in opening an input or output data set, with the exception of the data specified by the ddname ERR statement, occurred. This message is sent to a printer.
System Action: If the data set specified by the ddname ERR statement cannot be opened, then the job is ended by an abend. The primary result of this ABEND is a user return code of 9, which indicates that the data set to record error messages could not be opened. Additionally a dump of the virtual storage areas pertaining to this job may be included in the output generated when a SYSABEND, SYSMDUMP, or SYSUDUMP DD statement is coded in the JCL to process the dispatch control records (DCRs).
User Response: None.
00000000 | ALL ADDRESSES PREVIOUSLY IN A DEACTIVATED STATUS HAVE BEEN RETURNED TO POOL |
Explanation: This is a warning that SYCON previously contained deactivation parameters but no longer does. Any addresses that were deactivated are returned to the online system during the next online pool directory update. However, make sure that this is what you requested before running the online pool directory update.
System Action: None.
User Response: None.
See TPF Database Reference for more information about offline pool maintenance and pool directory update.
000000000 | ALL INPUT CARDS HAVE BEEN PROCESSED -- END OF SUCCESSFUL EXECUTION |
Explanation: None.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the system allocator (SAL).
000000000 | ALL INPUT CARDS HAVE BEEN PROCESSED - ERRORS DETECTED |
Explanation: None.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the system allocator (SAL).
000000000 | ALLOCATED SIZE DOES NOT AGREE WITH RECORD LENGTH -- RECORD (NOT) FILED |
Explanation: If the record being loaded is allocated as small (381) and its length is greater than 381, the record is ignored. Small length records (381) can be filed when the allocation is large (1055).
System Action: Your are notified that a small record was filed in the larger allocated record.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | ALL RCP ITEMS DO NOT HAVE SAME TIME STAMP |
Explanation: The RCP items should all have the same time stamp and do not. The discrepancy is probably because an incorrect or old RCP tape was used.
System Action: The job is ended.
User Response: Do the following:
000000000 | A MESSAGE HAS BEEN DELETED FROM THE ABOVE TEST UNIT BECAUSE NO LN/IA/TA WAS IN THE MESSAGE |
Explanation: You did not include a line number, interchange address, and terminal address (LNIATA) for the output message.
System Action: This message is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | A MESSAGE HAS BEEN DELETED FROM THE ABOVE TEST BECAUSE NO RID WAS FOUND |
Explanation: For a SNA-type message no resource identifier (RID) was placed in the message.
System Action: The message is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | A MESSAGE HAS BEEN DELETED FROM THE ABOVE TEST UNIT DUE TO AN INVALID CHARACTER COUNT HAVING BEEN ENTERED INTO THE MESSAGE |
Explanation: The system test compiler (STC) will not accept character counts that are less than 12 or greater than 1170.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | AN RCP TAPE MUST BE PROCESSED IN PHASE 2 OF RECOUP |
Explanation: The operator told the TPF system that there were no input tapes to process. However, recoup phase 2 is meaningless without a routing control parameter list (RCP) tape.
System Action: None.
User Response: Do one of the following:
See TPF Database Reference for more information about offline pool maintenance.
000000000 | AP CHAIN OVERLAYING PTV |
Explanation: The core image restart area (CIMR) chain for the main storage resident E-type programs overlays the beginning of ICDF.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about loaders.
000000000 | ASMP ERROR REPORT ------ NOT FOUND ON LISTAPE |
Explanation: The program identified was requested through the LIST option but not found during a search of the LISTAPE input.
System Action: None.
User Response: Verify the program name from the output of the multiple assembly (MASM) program.
See TPF System Installation Support Reference for more information about the multiple assembly and compilation print program.
000000000 | ATTENTION - APRG CLEAR CARD INPUT, ADATA FILES WILL BE CLEARED |
Explanation: The LOADER APRG CLEAR card was specified in the auxiliary loader (TLDR) load deck. When the output from this job is loaded to the online TPF system, all ADATA files on the target image will be cleared.
System Action: None.
User Response: If the LOADER APRG CLEAR card was intentionally included in the load deck, do nothing. Otherwise, remove the LOADER APRG CLEAR card from the load deck and run TPFLDR again.
See TPF System Installation Support Reference for more information about TLDR and the LOADER APRG CLEAR card.
000000000 | ATTENTION - BUFFER ERROR READING ADATA |
Explanation: Auxiliary loader (TLDR) ran out of storage while attempting to load an ADATA file for a 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 TLDR and the ADATASIZE parameter.
000000000 | ATTENTION - CONTAINS NO LINK MAP DATA |
Explanation: You ran the offline auxiliary loader (TLDR) 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:
See TPF Application Programming for information about CBLD and TPF System Installation Support Reference for information about TLDR.
000000000 | ATTENTION - I/O ERROR READING ADATA |
Explanation: An I/O error occurred when auxiliary loader (TLDR) attempted to read an ADATA file for a 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 TLDR.
000000000 | ATTRIBUTE BITS DO NOT MATCH TABLE FOR MAP--xxxx--FIELD NAMED--yyyy--DEFAULT SET |
Where:
Explanation: This is a Type E error. The DDATA statement referenced in the message in the map referenced in the message contains unknown attribute options or attribute options that are not valid.
System Action: None.
User Response: None.
See TPF Database Reference for more information about mapping support installation.
000000000 | AUTO TYPE--xx FOR FIELD --yyyy-- INVALID FOR MAP--zzzz, TERMINATED |
Where:
Explanation: This is a Type E error. The map referenced in the message was not generated because the TYPE= operand for the field referenced in the message is inconsistent for the map designation; for example, an input-only map has a TYPE=CO field. This type is only valid for output maps.
System Action: None.
User Response: None.
See TPF Database Reference for more information about mapping support installation.
000000000 | AUTO TYPE-CL CODED FOR FIELD --yyyy-- BUT SYSMAP=YES NOT CODED FOR MAP--xxxx--, TERMINATED |
Where:
Explanation: This is a Type E error. The DDATA statement reference in the message defines this field as a control line. This designation is reserved for system-type maps and must have the SYSMAP=YES option coded in the DPANL statement.
System Action: The map referenced in the message is not generated.
User Response: None.
See TPF Database Reference for more information about mapping support installation.
000000000 | BAD DIRECTORY RECORD |
Explanation: Data that is not valid was found in the directory record. The TPF system error macros are issued for these cases, which causes a dump to the real-time tape.
System Action: None.
User Response: Do the following:
In addition, the operator is informed of the error and processing is stopped. The operator, then, should enter an abort message to carry out housekeeping procedures.
000000000 | BAD LOAD CARD OR BAD PATCH CARD |
Explanation: The load card does not match the load card in the name table of the TLDR segment. The CPU ID may be in the wrong column or there may be an error in the REP card patch address.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | BAD TAPE |
Explanation: The recoup phase 2-created tape contains a record type that is not valid.
System Action: None.
User Response: Do the following:
In addition, the operator is informed of the error and processing is stopped. The operator, then, should enter an abort message to carry out housekeeping procedures.
000000000 | BASE ORDINAL NUMBER nnnn IS TOO LARGE FOR TPF 3.1 FIELD - FALLBACK WILL NOT BE POSSIBLE |
Where:
Explanation: This is a warning that the base ordinal number exceeds the maximum value that is allowed in the TPF system. Therefore, the TPF 3.1 field cannot be filled in and the directory cannot be used in the TPF system.
System Action: Processing continues.
User Response: The TPF 4.1 system provides the capability to code more directories than was possible with the TPF system. However, to do so, you must be sure that you no longer need to fall back from the TPF 4.1 system to the TPF system.
If you still require the capability to fall back from the TPF 4.1 system to the TPF 3.1 system, recode the pool layout.
If you no longer require the capability to fall back from the TPF
4.1 system to the TPF 3.1 system, you do not need to make any
changes at this time.
Severity: 0
Explanation: None.
System Action: None.
User Response: None.
Severity: 0
Explanation: None.
System Action: None.
User Response: None.
Severity: 4
Explanation: The first subparameter of the BCODE parameter was defaulted to EBCDIC but
EBCDIC support was not included in the system initialization program (SIP)
generation.
System Action: None.
User Response: Do one of the following:
Severity: 4
Explanation: The first subparameter of the BCODE parameter is EBCDIC but EBCDIC support was
not included in the system initialization program (SIP) generation.
System Action: None.
User Response: Do one of the following:
Severity: 4
Explanation: The first subparameter of the BCODE parameter is not EBCDIC or UASCII.
System Action: None.
User Response: Do the following:
Severity: 4
Explanation: The BCODE parameter specifies UASCII code for this BSC line but UASCII code
support was not included in the system initialization program (SIP)
generation.
System Action: None.
User Response: Do one of the following:
Severity: 4
Explanation: The second subparameter of the BCODE parameter is not YTRAN or NTRAN.
System Action: None.
User Response: Do the following:
Severity: 4
Explanation: The third subparameter of the BCODE parameter is not YRCPL or NRCPL.
System Action: None.
User Response: Do the following:
000000000 BCODE HAS MORE THAN ONE USACII SUBPARAMETER EXCESS IGNORED
000000000 BCODE HAS MORE THAN THREE SUBPARAMETERS EXCESS PARAMETERS IGNORED
000000000 BCODE(1) DEFAULTED TO EBCDIC BUT NO EBCDIC SUPPORT IN GEN
000000000 BCODE(1) PARAMETER IS EBCDIC BUT EBCDIC SUPPORT NOT INCLUDED IN GEN
000000000 BCODE(1) PARAMETER IS NOT VALID
000000000 BCODE(1) VALUE IS UASCII BUT UASCII SUPPORT NOT INCLUDED IN GEN
000000000 BCODE(2) PARAMETER NOT VALID
000000000 BCODE(3) PARAMETER NOT VALID
000000000 | BEYOND ALLOC LGTH - PATCH NOT APPLIED |
Explanation: A patch for a program or a keypoint extends beyond the allocated length of the program or keypoint.
System Action: The load is aborted for a keypoint. The patch is ignored for a program and the load is continued.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | BEYOND ALLOC RANGE |
Explanation: None.
System Action: None.
User Response: None.
000000000 | BEYOND END STATEMENT |
Explanation: The patch address is beyond the end statement of the main storage-resident program.
System Action: The patch is still applied.
User Response: None.
See TPF System Installation Support Reference for
more information about the loaders program.
Severity: 0
Explanation: The line is defined as a BSC point to point line. Only BST00 is
valid.
System Action: If other BST parameters are specified, they will not be processed.
User Response: None.
Severity: 0
Explanation: The station is defined as a tributary station on a multipoint line.
Only BST00 is valid.
System Action: If other BST parameters are specified, they will not be processed.
User Response: None.
Where:
Severity: 4
Explanation: The BST parameter does not have two subparameters.
System Action: None.
User Response: Do the following:
Where:
Severity: 4
Explanation: BST was not specified but an entry was found in the SNCT table for this line
with the station number referenced in the message. Since no POL and SEL
characters were specified, the pointer into the BSAT table could not be
determined.
System Action: None.
User Response: Do the following:
Where:
Severity: 4
Explanation: The BST parameter does not have a polch subparameter.
System Action: None.
User Response: Do the following:
Where:
Severity: 4
Explanation: The BST parameter does not have a selch subparameter.
System Action: None.
User Response: Do the following:
Where:
Severity: 4
Explanation: The BST parameter was specified for a BSC line but no matching entry was found
in the SNCT table. This condition is valid only if the line is
specified as using EBCDIC, YTRAN, and YRCPL (BCODE=(EBCDIC, YTRAN,
YRCPL)). The line does not have one of these required
parameters.
System Action: None.
User Response: Do the following:
Where:
Severity: 4
Explanation: The BST parameters must be specified using consecutive numbers. The BST
parameter was not specified (for example, skipped).
System Action: None.
User Response: Do the following:
Where:
Severity: 0
Explanation: The BST parameter was not specified and the SNCT table did not contain a entry
for this line with the station number referenced in the message but there was
a entry with a higher station number.
System Action: None.
User Response: The condition described by the message may be valid. If it is not
valid, correct the input and rerun Phase 1.
Where:
Severity: 0
Explanation: An entry was found in the SNCT table for this line with the station number
referenced in the message but the BST parameter was not specified.
System Action: None.
User Response: The condition described by the message may be valid. If it is not
valid, correct the input and rerun Phase 1.
Where:
Severity: 4
Explanation: No match was found when comparing the POL and SEL subparameters of the BST
parameter with the BSAT table specified in the system initialization program
(SIP) generation using BBSAT macros.
System Action: None.
User Response: The error occurred on the SKLNG macro or on a BBSAT (SIP) macro.
Do one of the following:
Where:
Severity: 4
Explanation: The POL subparameter of the BST parameter has a maximum length of 7
characters.
System Action: None.
User Response: Do the following:
Where:
Severity: 4
Explanation: The SEL subparameter of the BST parameter has a maximum length of 7
characters.
System Action: None.
User Response: Do the following:
Where:
Severity: 0
Explanation: BST parameter was specified but there is no entry in the SNCT table for this
line with the station number referenced in the message.
System Action: None.
User Response: The condition described by the message may be valid. If it is not
valid, correct the input and rerun Phase 1.
Severity: 4
Explanation: The station is defined as a tributary station so the BSTOV value cannot be
zero.
System Action: None.
User Response: Do the following:
Severity: 4
Explanation: The line is defined in the BTYPE parameter as a point-to-point line so BSTOV
parameter is not needed.
System Action: None.
User Response: None.
Severity: 4
Explanation: None.
System Action: None.
User Response: Do the following:
Severity: 0
Explanation: None.
System Action: No TITB table is generated for the line.
User Response: None.
Severity: 0
Explanation: None.
System Action: None.
User Response: None.
Severity: 4
Explanation: The BTYPE parameter must specify either point to point (BSPP) or multipoint
(BSMP) for each BSC line.
System Action: None.
User Response: Do one of the following:
Severity: 4
Explanation: The line is a BSC line but the BTYPE parameter was not specified.
System Action: None.
User Response: Do the following:
Severity: 4
Explanation: The line is defined as a BSC point to point line but point to point line
support was not included in the system initialization program (SIP)
generation.
System Action: None.
User Response: Do one of the following:
Severity: 4
Explanation: The line is defined as a BSC multipoint line but multipoint line support was
not included in the system initialization program (SIP) generation.
System Action: None.
User Response: Do one of the following:
Severity: 4
Explanation: The station is being defined as a master station on a BSC multipoint line but
master station support was not included in the system initialization program
(SIP) generation.
System Action: None.
User Response: Do one of the following:
Severity: 4
Explanation: The station is being defined as a tributary station on a BSC multipoint line
but tributary station support was not included in the system initialization
program (SIP) generation.
System Action: None.
User Response: Do one of the following:
Severity: 4
Explanation: The second subparameter of the BTYPE parameter is not a valid value.
System Action: None.
User Response: Do the following:
Severity: 4
Explanation: The third subparameter of the BTYPE parameter is not valid.
System Action: None.
User Response: Do the following:
000000000 BSC POINT TO POINT LINE, ONLY BST00 PROCESSED
000000000 BSC TRIBUTARY STATION ON A MULTIPOINT LINE ONLY BST00 PROCESSED
000000000 BSTnn DOES NOT HAVE TWO SUBPARAMETERS
000000000 BSTnn ERROR UNABLE TO DEVELOP BSAT POINTER
000000000 BSTnn HAS MISSING POL SUBPARAMETER
000000000 BSTnn HAS MISSING SEL SUBPARAMETER
000000000 BSTnn IN ORDER TO OMIT AN SNCT ENTRY THE LINE MUST USE EBCDIC,
YTRAN AND YRCPL
000000000 BSTnn NOT SPECIFIED
000000000 BSTnn NOT SPECIFIED AND NOT IN SNCT TABLE BUT HIGHER ENTRY
IN TABLE
000000000 BSTnn NOT SPECIFIED BUT ENTRY WAS FOUND IN SNCT TABLE
000000000 BSTnn POL AND SEL SUBPARAMETERS NOT FOUND IN BSAT TABLE
000000000 BSTnn POL SUBPARAMETER HAS TOO MANY CHARACTERS
000000000 BSTnn SEL SUBPARAMETER HAS TOO MANY CHARACTERS
000000000 BSTnn SPECIFIED BUT NO MATCHING ENTRY FOUND IN SNCT TABLE
000000000 BSTOV CAN NOT BE ZERO FOR TRIB STATION
000000000 BSTOV SPECIFIED FOR BTYPE(1) AS BSPP PARAMETER IGNORED
000000000 BSTOV VALUE LESS THAN 0 OR GREATER THAN 255
000000000 BST00 NOT SPECIFIED FOR BSC POINT TO POINT LINE
000000000 BTYPE HAS MORE THAN THREE SUBPARAMETERS EXCESS PARAMETERS ARE IGNORED
000000000 BTYPE PARAMETER IS NOT BSPP OR BSMP
000000000 BTYPE PARAMETER NOT SPECIFIED FOR BSC LINE
000000000 BTYPE PARAMETER SPECIFIES BSPP BUT NO POINT TO POINT SUPPORT IN GEN
000000000 BTYPE(1) PARAMETER SPECIFIES BSMP BUT NO MULTIPOINT SUPPORT IN GEN
000000000 BTYPE(2) PARAMETER IS MAST BUT MASTER SUPPORT IS NOT INCLUDED IN
GEN
000000000 BTYPE(2) PARAMETER IS TRIB BUT TRIB SUPPORT IS NOT INCLUDED IN GEN
000000000 BTYPE(2) PARAMETER NOT VALID
000000000 BTYPE(3) PARAMETER IS NOT VALID
000000000 | BUFFER NOT AVAILABLE FOR xxxxxxxx |
Where:
Explanation: An O/S GETBUF macro instruction returned an error code for the specified data set.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about variable cross referencing.
000000000 | BYPASSED -- KEYPOINT HAS NO VALID PATCHES |
Explanation: There were no valid patches for this KEYPOINT PATCH card so no action is taken.
System Action: None.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CALLED PROGRAM GREATER THAN 1055 BYTES -- IGNORED |
Explanation: The system test compiler (STC) will not place any programs larger than 1055 bytes on the test unit tape.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | CANNOT FIND ONE OF THE FOLLOWING PROGRAMS IN NAME TABLE: CP, FCTB, ICDF, ACPL, IPLB, RIAT, SIGT, IPLA, IPAT, USR1, or USR2. |
Explanation: One of these programs was not found in the name table of the TLDR segment.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CANNOT FIND PROC NAME OF THIS LOAD CARD |
Explanation: The processor ID for this load card does not match any processor ID that was TPF system generated.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CANNOT FIND REQUESTED PROG ON RTOL |
Explanation: The requested program is not in object library.
System Action: The call is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | CAPACITY OF THE SDMU HAS BEEN EXCEEDED. A NEW LIBRARY TAPE HAS BEEN CREATED WITH REFLECTS INPUT CARDS PROCESSED TO THIS POINT |
Explanation: It is probable that more work area is needed on the unit test disk.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | CARD FORMAT IN ERROR |
Explanation: One of the following errors occurred:
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CARD HAS ILLEGAL HEX DATA |
Explanation: The REP card address or data fields have data that is not 0 through 9 or A through F.
System Action: If the REP card is for a keypoint, the load is aborted.
If the REP card is for a program, he patch is ignored and the load is continued.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CARD OUT OF SEQUENCE |
Explanation: The control card or REP card is in the wrong sequence.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CARD UNIDENTIFIABLE BY DATA GENERATION ROUTINE |
Explanation: The card cannot be identified by the data generation routine.
System Action: This card is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | CHECK LOAD CARDS FOR THIS SEGMENT |
Explanation: The load cards for this segment might be incorrect. This error occurs while trying to use:
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | CHKSUM ERROR--DETECTED AT yyyyyy xxxx |
Where:
Explanation: Checksum entered into the program test vehicle (PTV) checksum table upon first entry to a program under a unit test ECB. Every time that program issues a macro, checksum is calculated and composed (for internal modifications). If an error is found, control transfers to the next sequential instruction and a new checksum total is entered into the PTV checksum table. Upon EXITC of a unit test ECB, the PTV checksum table is cleared and the process started again for the next ECB generated by a unit test.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | CHKSUM--PROGRAM nnnn NOT CHECKSUMMED--CHKSUM TABLE FULL |
Where:
Explanation: None.
System Action: This program segment is not checksummed. Control is transferred to the ENTER routine.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | CMD NOT CODED CORRECTLY |
Explanation: This is a Type E error. The user map has a DPANL CMD= option coded that is not valid or is misspelled.
System Action: The map is not created.
User Response: Do the following:
See TPF Database Reference for more information about mapping support installation.
000000000 | COMMANDS OUT OF SEQUENCE RESET PTV |
Explanation: None.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | COMPLETE -- ERROR FOUND |
Explanation: None.
System Action: None.
User Response: None.
000000000 | CON LEN > THE FIELD LEN MAP--xxxx--TERMINATED |
Where:
Explanation: This is a Type E error. The user output map named in the message has a DDATA statement with a CON= operand coded in which the constant data is greater than the length specified in the LENGTH= operand.
System Action: This map is not created.
User Response: Do the following:
See TPF Database Reference for more information about mapping support installation.
000000000 | CONTINUATION CNTRL CARD MISSING |
Explanation: Continuation control card expected but not found.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about variable cross referencing.
000000000 | CONTROL UNIT STATUS REINITIALIZED (SEGMENT CCL1) |
Explanation: None.
System Action: None.
User Response: None.
000000000 | COPY REQUESTED FOR MEMBER xxxxxxxx IN MEMBER yyyyyyyy IS A NESTED REQUEST/IGNORED |
Where:
Explanation: See the JCL SYSLIB data definition.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about variable cross referencing.
000000000 | COPY REQUESTED FOR MEMBER xxxxxxxx IN MEMBER yyyyyyyy NOT FOUND, IGNORED |
Where:
Explanation: The copy member referenced in the message, which was requested by the PDS member referenced in the message, was not found in the SYSLIB data set.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about variable cross referencing.
000000000 | CORE SIZE = xxxx, ALLOCATED SIZE = yyyy, PGM = nnnnvv |
Where:
Explanation: None.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | COULD NOT CONVERT NODE NAME TEST UNIT IGNORED |
Explanation: The user-specified node name for an SNA message was not found on the node name to resource identifier (RID) conversion file.
System Action: This test unit is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | CP CAN ONLY BE LOADED IN A BSS SYSTEM -- JOB ABORTED |
Explanation: The control program (CP) can only be loaded in the basic subsystem (BSS).
System Action: None.
User Response: Do one of the following:
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CP CSECT TBL EXCEEDS ALLOC LGTH, RUN WILL CONTINUE WITHOUT ONLINE CP PATCH CAPABILITY |
Explanation: The size of the CP CSECT names module (CPLKMP) is too small to contain the names of all the CP CSECTS.
System Action: None.
User Response: No CP CSECT module may be patched. This problem can be fixed by correcting the CPLKMP module.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CP IN CORE EXCEEDS BUFSIZ PARM -- JOB ABORTED |
Explanation: The size of the control program (CP) is larger than the BUFSIZ parameter when running offline TLDR.
The BUFSIZE parameter needs to be larger than any single component that is included in the load deck.
System Action: The load is ended.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CP IN CORE EXCEEDS CK1ECP |
Explanation: The general file loader build area is too small to contain the control program and what was loaded before it.
System Action: None.
User Response: Increase the size of CK1ECP.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CP LOAD OUT OF SEQ |
Explanation: The control program (CP) load is out of sequence.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CP ON LMOD DIFF FROM LEN AND/OR LOC PER KPT A |
Explanation: The length of the control program (CP) does not agree with keypoint A.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CP VERSION NOT FOUND |
Explanation: The control program (CP) version was not found.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CP VERSION NOT FOUND -- JOB ABORTED |
Explanation: The requested control program (CP) was not found.
System Action: None.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CRITICAL CARD OUT OF SEQUENCE |
Explanation: A loader image clear card or a loader load CTKX card was encountered that is out of sequence.
System Action: None.
User Response: Do the following:
000000000 | CRITICAL PROG nnnnvv NOT FOUND OR COULD NOT BE LOADED |
Where:
Explanation: A program that is critical to the loading operation was not found (for example, ACPL) or could not be loaded because of some other errors.
System Action: The run is ended. Application program errors will not cause the run to abend but are noted on the load list.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CTKx G.FILE CONFIG FROM G.FILE |
Where:
Explanation: For this execution of ALDR, the keypoint values referenced in the message for the general file configuration are being taken from the general file keypoint area.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CTKx G.FILE CONFIG FROM LIBRARY |
Where:
Explanation: For this execution of ALDR, the keypoint values referenced in the message for the general file configuration are being taken from the object library.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CTKx NOT CALLED ON G.FILE CONFIG CARD-JOB ABORTED |
Where:
Explanation: The configuration card is not valid.
System Action: None.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | CTRL. -- CARD IN ERROR, CARD IGNORED |
Explanation: The control card after the load AP card is not a call program card, a load card, a REP card, or an LDT card.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for
more information about the loaders program.
Severity: 4
Explanation: The PKST macros should be coded in ascending order by control unit number so
that the generation macros can check that a PKST is generated for every
control unit.
System Action: None.
User Response: Check that a PKST was generated for every control unit in the TPF
system.000000000 CU NUMBER OUT OF SEQUENCE - CHECK ALL PKSTs INITIALIZED
000000000 | CURRENT TA T2 NOT EQUAL TO LAST ACTIVE TA T1 |
Explanation: The program test vehicle (PTV) intercepted a SEND-type macro from an ILT terminal address, which is in Tete-a-Tete mode, and the terminal address (T2) does not agree with the original terminal address (T1).
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | CYL PORTION OF MCHR FILE ADDR IS GREATER THAN 255 |
Explanation: The file address for a record that was to be written using the special MCHR format was calculated and the cylinder portion of the file address was greater than 255.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | DATA GENERATION -- BAD DELIMITER -- REST OF CD IGNORED |
Explanation: The proper delimiter for this field of four decimal digits was not found.
System Action: The remainder of this card is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- BSTA02 NO LONGER A VALID ENTRY |
Explanation: The system test compiler (STC) will only accept BSTA06 and BSTA08 entries.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- BSTA04 NO LONGER A VALID ENTRY |
Explanation: The system test compiler (STC) will only accept BSTA06 and BSTA08 entries.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- CARD IGNORED |
Explanation: A detail data generation card or a TPF system generated card was not preceded by a valid GSTAR card.
System Action: The card is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- CARD REFERENCES LABEL NOT IN DRIL |
Explanation: The label on the card cannot be found in the DRIL library.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- CARD REFERENCES LABEL NOT IN DRIL |
Explanation: The label in the card does not correspond to any label in the DRIL record currently being used.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- CARD REFERENCES RECORD NOT IN SDMF |
Explanation: A record was called from the standard data/message file (SDMF) that was not available.
System Action: The records were created without using a model from SDMT.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- CC1-15 BLANK -- IGNORED |
Explanation: CC1-15 of this card is blank. However, the last card did not specify a continuation.
System Action: This card is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- DATA ENTERED IN UNUSED FIELD |
Explanation: Data was entered into a field defined as a spare field.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- DRIL NOT AVAILABLE -- ENTRY IGNORED |
Explanation: The label on the card references a record not available on the DRIL library.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- ENTRY POSITION >RCD SIZE< IGN |
Explanation: The requested entry exceeds the size of the record.
System Action: The card is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- FIELD TOO LONG TRUNCATED ON LEFT |
Explanation: Data to be entered into a field was too long for this field. Truncation has occurred on the left and the maximum field length was entered.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- GROUP RECORD NOT AVAILABLE |
Explanation: The GROUP record being called is not in the standard data/message file (SDMF).
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- GSTAR--FORMAT ERROR--1 REC. ASSUMED |
Explanation: In the GSTAR card, a period was not found delimiting the number of records to four digits or less. The number of records desired is assumed to be one.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION GSTAR--NO REC.NUMBER--1 ASSUMED |
Explanation: The number of records to be created was not entered in the GSTAR word.
System Action: The data generation routine will create one record.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- GSTAR--REC. # HI -- USED |
Explanation: The data generation routine does not have the main storage available to create the desired number of records. As many records as possible will be created and the number indicated in message.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- INVALID ALPHA DATA ENTERED |
Explanation: A nonalphabetic character was entered into a field defined to be alphabetic only.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- INVALID CONT. CD READ AGAIN |
Explanation: Since the card is still in the read-in area, the data generation routine will reprocess it as a noncontinuation card. Since the card is still in the DGR card read-in area, DGR will reprocess it as a noncontinuation card.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- INVALID CONTROL TYPE IN DRIL -- IGN |
Explanation: CC63. of the DRIL record was defined incorrectly.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- INVALID FLD. TYPE IN DRIL -- CD. IGNORED |
Explanation: CC69. of the DRIL record was defined incorrectly.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- INVALID NUMERIC DATA ENTERED |
Explanation: A character that is not valid was entered into a field defined to be numeric only.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- LENGTH CONFLICT -- CED LENGTH USED |
Explanation: The length of a record indicated on the GSTAR card is not equal to the length of a record on the standard data/message file (SDMF).
System Action: The length given on the card is assumed to be correct and used.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- MODEL RECORD NOT AVAILABLE |
Explanation: A record was called from the standard data/message file (SDMF) that was not available.
System Action: The records were created without using a model from SDMF.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- NO DELIMITER LAST ENTRY IGNORED |
Explanation: No delimiter found at the end of a field to be entered.
System Action: This field was not entered into the record.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- NO GEND CARD FOUND -- ANY RECORDS TO BE GENERATED FROM LAST GSTAR CARD UP TO THIS POINT HAVE BEEN DELETED |
Explanation: None.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- NON DEC. CHAR -- OR BAD DELIMITER IGND |
Explanation: A non-numeric character was found in a field of 4 decimal digits or no delimiter was found.
System Action: The remainder of this card is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- NON-HEX CHAR.--REST OF CD. IGNORED |
Explanation: A field that must be coded in hexadecimal contains a character other than 0 through 9 or A through F.
System Action: The field set is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- SDMU ID TOO SHORT -- SDMU IGNORED |
Explanation: The ID used in a GSTAR card was less than 12 characters.
System Action: No record was called from the standard data/message file (SDMF).
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- SDMU ID TOO LONG -- SDMU IGNORED |
Explanation: The ID used in a GSTAR card was greater than 12 characters.
System Action: No record was called from the standard data/message file (SDMF).
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- THIS FIELD IS NOT CONTINUOUS |
Explanation: A continuous field card was used for a field that is not greater than 56 characters long.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- UNUSUAL CONDITION ON DISK -- IGNORED |
Explanation: Either this label is not available in DRIL or DRIL was not outputted to disk.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA GENERATION -- ZERO LN. FIELD -- CD. IGNORED |
Explanation: A field of zero length was found. It cannot be entered into the record.
System Action: The rest of the card is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | DATA RECORD NOT AVAILABLE -- ENTRY IGNORED |
Explanation: The requested ID is not available on the standard data/message file (SDMF).
System Action: None.
User Response: None.
See TPF Program Development Support Reference for
more information.
Severity: 12
Explanation: The logical device parameter for this parameter must be A,B,C, D (for devices
A-D), or R (for ratio dispensing).
System Action: None.
User Response: None.000000000 "DEV" IS INVALID FOR xxxxx PARAMETER
000000000 | DIRECTORY NUMBER nnnn IS TOO LARGE FOR TPF 3.1 FIELD - FALLBACK WILL NOT BE POSSIBLE |
Where:
Explanation: This is a warning that the pool directory ordinal number exceeds the maximum value that can fit in the TPF 3.1 field. Therefore, the TPF 3.1 field cannot be filled in and the directory cannot be used in the TPF system.
System Action: Processing continues.
User Response: The TPF 4.1 system provides the capability to code more directories than was possible with the TPF 3.1 system. However, to do so, you must be sure that you no longer need to fall back from the TPF 4.1 system to the TPF 3.1 system.
If you still require the capability to fall back from the TPF 4.1 system to the TPF 3.1 system, then recode the pool layout.
If you no longer require the capability to fall back from the TPF 4.1 system to the TPF 3.1 system, you do not need to make any changes at this time.
000000000 | DIRECTORY RCDS ON DGF HAVE NOT BEEN PROCESSED ON-LINE. REPLY 'C' TO CONTINUE OR 'T' TO TERMINATE |
Explanation: Directory records created by a previous offline pool maintenance run were not processed by the online system. This can happen even when the previous run did not go to the end-of-job.
System Action: None.
User Response: See your system programmer for more information. If told to run the job, then reply with the character C. Otherwise, reply with the character T.
See TPF Database Reference for more information about offline pool maintenance.
000000000 | DUPLICATE -- LOAD CARD -- JOB ABORTED |
Explanation: This program was already loaded. This message appears to the right of the card that caused the error.
System Action: None.
User Response: Do the following:
See TPF System Installation Support Reference for
more information about the loaders program.
Severity: 12
Explanation: The same ID (displayed in hex, character, and decimal formats) was coded more
than once.
System Action: None.
User Response: None.000000000 DUPLICATE USER RECORD ID(x"xxxx",
C"cc", D"ddd")
THIS RUN
000000000 | DURING-RECOUP TAPES CANNOT BE CORRECTLY PROCESSED. RUN MAY BE INVALID |
Explanation: The number in the recoup keypoint record denoting the last during-recoup primary real-time tape (RTA) is not greater than the number denoting the last pre-recoup RTA. This indicates a wraparound situation on the tape sequence number written in the dump formatter record at the beginning of each RTA. As this could be expected to happen only about once in a billion times (the number ranges from 0 to 4,294,967,295), it was probably caused by a system error.
System Action: None.
User Response: Remove any RTAs known to have been created during recoup. The run should then be correct except for addresses released during recoup.
See TPF Database Reference for more information about offline pool maintenance.
000000000 | END OF CARD REACHED - VALUE OR KEYWORD INVALID |
Explanation: Column 72 of the card was reached while scanning an entry on a control card and a delimiter was not found.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the multiple assembly and compilation program.
000000000 | END OF CARD REACHED/VALUE OR KEYWORD INVALID |
Explanation: This message is printed when column 72 of the control card is reached on a scan without finding a delimiter for the keyword or keyword value being scanned.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about variable cross referencing.
000000000 | END OF FILE ERROR -- JOB TERMINATED |
Explanation: None.
System Action: None.
User Response: None.
000000000 | END OF FILE FOUND AFTER RECORD NO. xx |
Where:
Explanation: Reduction is processing and the end of the RTC tape occurred before the CE or DE record was found. The data read up to that point was processed.
System Action: None.
User Response: None.
000000000 | END OF FILE FOUND AFTER RECORD NO xx REDUCTION IS PROCESSING INFORMATION GATHERED TO THIS POINT |
Where:
Explanation: If the end of the RTC tape occurs before the DE record, this message will be printed and the reduction will contain already read data.
System Action: None.
User Response: None.
000000000 | END OF JOB |
Explanation: This is the normal completion of the formatter.
System Action: None.
User Response: None.
See TPF Database Reference for more information about the real-time disk formatter.
000000000 | END OF MAP RECORD CREATE RUN |
Explanation: This is a Type C error.
System Action: The program has completed.
User Response: None.
See TPF Database Reference for more information about mapping support installation.
000000000 | END STC |
Explanation: The END STC card on the test unit tape (TUT) is found. It indicates that the completion of the system test vehicle (STV) or the last unit/package test unit on the TUT.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | END TEST UNIT |
Explanation: This message indicates the end of output for either a unit or a package test unit.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | ENTRY IN CONTROL CARD LIST EXCEEDS 8 CHARACTERS |
Explanation: None.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the multiple assembly and compilation print program.
000000000 | EOD RETURNED WHEN ATTEMPTING TO RETRIEVE PROGRAM nnnnvv -- LOAD IS IGNORED |
Where:
Explanation: The end-of-data (EOD) set condition was encountered when ALDR tried to read the object module referenced in the message from an object library.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | EOV MOUNT NEXT TAPE. NEWTAPE=Y, EOF=N |
Explanation: The program encountered an EOV condition.
System Action: None.
User Response: If there are more tapes to process, reply Y. Otherwise, reply N and the program gives a summary print of data processed.
See TPF Database Reference for more information about offline pool maintenance.
000000000 | ERROR DURING BLDL -- JOB TERMINATED ENTRY NOT FOUND |
Explanation: An error occurred while accessing the program directory record (PDR).
System Action: The job is ended.
User Response: None.
000000000 | ERROR DURING BLDL -- JOB TERMINATED PERM I/O ERROR |
Explanation: An error occurred while accessing the program directory record (PDR).
System Action: The job is ended.
User Response: None.
000000000 | ERROR FINDING ID nn ADDRESS nnnnnnnn SSU nnnn -- I--S nn |
Where:
Explanation: A main storage allocator record or global record cannot be found with the ID, ordinal number, and address provided.
System Action: None.
User Response: None.
000000000 | ERROR FINDING SAL TABLE -- NOTIFY SUPPORT |
Explanation: An error was encountered retrieving the system allocator (SAL) table (SALTBL).
System Action: None.
User Response: Make sure you are referencing the proper SALTBL. If not, correct the deck and submit the job again. If yes, verify the content of the SALTBL.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | ERROR -- ILLEGAL CARD OR SEQUENCE - THIS CARD IGNORED |
Explanation: This card is not valid because it is out of sequence.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | ERROR IN PARAMETER OF CALL CARD |
Explanation: The card in error is printed.
System Action: The job is ended.
User Response: None.
000000000 | ERROR IN PATCH CARD |
Explanation: The REP card does not have blanks in the correct location or the 001 in the correct location.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | ERROR IN PATCH ROUTINE |
Explanation: A patch card that is valid for ALDR was submitted.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | ERROR -- PROGR. nnnnvv, CORE ADDR. OUT OF RANGE, PROGR IGNORED |
Where:
Explanation: The main storage resident program address referenced in the message does not fall within the allocated range of main storage resident E-type programs.
System Action: The load is aborted. The values of the allocated range are contained in the CK1SAP and CK1EAP fields in keypoint A.
User Response: Make sure that you are using the proper system allocator (SAL) table (SALTBL) and the proper keypoint A. Perhaps CK1EAP in keypoint A needs to be increased.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | ERROR READING BLOCK FOR SEGMENT -- nnnn |
Where:
Explanation: An error occurred while reading the block for the segment name referenced in the message occurred. This message is sent to a printer.
System Action: The job is ended.
User Response: None.
000000000 | ERROR READING CARD |
Explanation: This message is caused by one of these errors:
In either case, the message is issued to a printer, along with the card image and segment name.
System Action: None.
User Response: None.
000000000 | ERROR READING FCTB VERSION=xx -- NOTIFY SUPPORT |
Where:
Explanation: An error was encountered while reading the file address compute program (FACE) table version referenced in the message.
System Action: None.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | ERROR READING OBJ CODE -- NOTIFY SUPPORT |
Explanation: A read error was encountered while doing input/output (I/O) on the object code.
System Action: None.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | ERROR OCCURRED IN READING THE DIRECTORY. JOB TERMINATED. |
Explanation: An error reading the directory block occurred. This message is sent to a printer.
System Action: The job is ended.
User Response: None.
000000000 | EXCEEDS ALLOCATED LNGTH, PROG NOT LOADED |
Explanation: None.
User Response: None.
System Action: None.
See TPF System Installation Support Reference for
more information about the loaders program.
Severity: 12
Explanation: The only two valid options for this parameter are XCP=YES or XCP=NO.
System Action: None.
User Response: None.000000000 EXCEPTION RECORDING PARAMETER INVALID
000000000 | FILE ADDR EXCEEDS LIMIT OF GEN FILE |
Explanation: The file address exceeds the limit for the general file.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | FILE ADDRESS PARA. LABEL NOT FOUND IN DRIL DELETED |
Explanation: The file addresses indicated in the header cannot be found within the DRIL entry.
System Action: This file address was deleted.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | FIND ERROR ON PARS LIST |
Explanation: The programmer airlines reservation system (PARs) list specified on the PARSvv card could not be found.
System Action: None.
User Response: Make sure PARSvv is on the object library specified in the load. If not, put it on the object library and submit the load again.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | FOLLOWING DATA NOT FILED |
Explanation: There is an error in the data record header in the pilot system or individual record.
System Action: The record is not loaded. The header is written to the real-time tape.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | FOLLOWING LOADER CARD INVALID |
Explanation: Either this card was not an END, LDT, or LOADER card, or the modules specified on the LOADER card is not valid.
System Action: None.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | FOLLOWING LOADER LOAD CARD OUT OF SEQUENCE: |
Explanation: The LOADER card printed after this message is out of sequence.
System Action: None.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | GENERAL FILE IS ON AN UNSUPPORTED DEVICE TYPE |
Explanation: The loader general file (LGF) is not on a supported direct access storage device.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program. See TPF System Generation for more information about the devices that are supported.
000000000 | G.FILE CONFIG CARD NOT GIVEN -- JOB ABORTED |
Explanation: The configuration card was not included in the load deck.
System Action: None.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | HARDWARE ERROR IN FILE ADDRESS -- PROGRAM FOLLOWS |
Explanation: The CE1SUG error indicator is set following the FINWC macro for the original (a base system) program. The test program from the TUT is written to the real-time tape after the message.
System Action: The program is not loaded.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | HARDWARE ERROR -- SELD UNABLE TO RETRIEVE THIS RECORD |
Explanation: A hardware error occurred so SELD was unable to retrieve the record.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | HDR PATCHING NOT ALLOWED -- CARD IGNORED |
Explanation: REP card address is in the program header area.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | IERxxxx |
Where:
Explanation: None.
System Action: None.
User Response: None.
See OS Sort/Merge System Information: System Generation/Installation library.
000000000 | IGNORED - UNKNOWN CARD TYPE |
Explanation: This card is unrecognizable by the loader.
System Action: None.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | ILLEGAL FORMAT IN PREVIOUS MESSAGE |
Explanation: The program test vehicle (PTV) intercepted a SEND-type macro from an ILT terminal address and the message contains illegal control characters.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | IMPROPER SEQUENCE OF LOAD ADDRESS CARDS JOB TERMINATED |
Explanation: The load address card that contains the first set of 1055 byte addresses did not contain a 1 in CC41.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information about the system test compiler (STC).
000000000 | INCORRECT CSECT NAME OR FORMAT ERROR |
Explanation: The CP REP card contains an incorrect CP CSECT name.
System Action: The card is ignored.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | INPUT RCP TAPE IS IN 3.1 FORMAT |
Explanation: The primary real-time tape (RTC) was produced by the TPF 3.1 system in a format that is not recognized by later versions of the TPF system. The tape cannot be read.
System Action: None.
User Response: Provide a tape formatted for the current system.
See TPF Database Reference for more information about offline pool maintenance.
000000000 | INPUT RECORD TYPE TO FACE IS INVALID/INPUT ORDINAL NUMBER TO FACE OUTSIDE ALLOWABLE RANGE |
Explanation: An error returned from the file address compute program (FACE) indicates a record type that is not valid or an ordinal number that is not valid. The first 44 bytes of the record header are written to the real-time tape.
System Action: The record is skipped.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | INPUT TAPE IS AFTER RECOUP. PROCESS IN NEXT OFFLINE UPDATE |
Explanation: The primary real-time tape (RTA), which is mounted as SYSIN, was created after running recoup phase 3. Processing this tape would distort the error analysis performed by recoup phase 4 of recoup (Run Type 4).
System Action: None.
User Response: Save the RTA as an unprocessed RTA.
See TPF Database Reference for more information about offline pool maintenance.
000000000 | INSUFFICIENT CORE -- INCREASE REGION SIZE |
Explanation: The program issued a GETMAIN request for core to build a list from the control cards. The GETMAIN was unsuccessful. The program should be run with a larger region or partition size.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the multiple assembly and compilation print program.
000000000 | INTERVENTION PARAMETERS NOT VALID - RUN ABORTED |
Explanation: The characters specified for the parameter are not valid.
System Action: None.
User Response: Specify the correct parameter and submit the job again.
See TPF Database Reference for more information about valid parameters for offline pool maintenance.
000000000 | INVAL BKSPC OVER PRIME ACT. CODE |
Explanation: Condition causing the backspace character tried to delete the error: Primary Action Code.
System Action: None.
User Response: None.
Severity: 4
Explanation: One or more of the parameters in the BASE operand is not valid.
System Action: None.
User Response: Do the following:
Severity: 4
Explanation: For a BSC line, the SL parameter in the SKLNG macro was omitted or outside the
range 1 through 256.
System Action: None.
User Response: If the default value is not acceptable, update the input and rerun Phase 1 or
patch the generated record at the byte following the SLCFnn tag.000000000 INVALID BASE STATUS DEFAULTED TO OFF-LINE
000000000 INVALID BSC SEND LEVEL - DEFAULT=1
000000000 | INVALID BYTE COUNT ON DRIL -- RECORD DELETED |
Explanation: This message indicates that the record was deleted from the library for this run.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information about the system test compiler (STC).
000000000 | INVALID BYTE OR RECORD NUMBER -- REST OF CARD IGNORED |
Explanation: An ORD card was encountered with a byte count that is not valid or a record number that is greater than the number created.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | INVALID CARD FORMAT -- REST OF CARD IGNORED |
Explanation: The ORD card format is incorrect.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | INVALID CODE IN RECORD HEADER |
Explanation: The data record header does not contain valid address code (X'09' for absolute, X'07' for ordinal number and record type). The first 44 bytes of the record header are written to the real-time tape.
System Action: The record is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | INVALID COMMUNICATION WITH LINKER |
Explanation: A return code that is not valid was received from the linkage editor (LEDT) while a program is being link edited.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | INVALID CONTROL TYPE ON DRIL -- RECORD DELETED |
Explanation: This message indicates that the record was deleted from the library for this run.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for
more information about the system test compiler (STC).
Severity: 4
Explanation: The control unit number specified is greater than maximum control unit number
as calculated by the system initialization program (SIP).
System Action: None.
User Response: Do the following:
000000000 INVALID CONTROL UNIT IN PATH PARAMETER - DEFAULTED TO VOID
PATH
000000000 | INVALID CONVERSION TYPE ON DRIL -- RECORD DELETED |
Explanation: CC69 of the DRIL record is in error. This message indicates that the record was deleted from the library for this run.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for
more information about the system test compiler (STC).
Severity: 8
Explanation: The control unit number specified was not:
System Action: None.
User Response: Do the following:
Severity: 4
Explanation: The CUSTAT operand is not valid.
System Action: None.
User Response: If default is not acceptable, correct the input and rerun Phase 1.
Alternatively, the generated PKST can be patched at the XSTAnn
tag.
Severity: 4
Explanation: The DEVICE parameter of the first SENDG macro was not coded with the proper
device type.
System Action: None.
User Response: If the default is not acceptable, correct the input and rerun Phase
1.000000000 INVALID CU NUMBER - PKST GENERATION SUPPRESSED
000000000 INVALID CU STATUS - DEFAULT TO OFF-LINE
000000000 INVALID DEVICE TYPE CODED 3350 DEFAULT SUBSTITUTED
000000000 | INVALID DGF KEYPOINT RECORD n--RUN ABORTED |
Explanation: The disk pack mounted as DGF does not have a valid pool maintenance keypoint record where one should be. The relative position of the record within the data set is indicated by the value provided in the message. Either the wrong disk pack was mounted or the pool maintenance general file was destroyed.
System Action: None.
User Response: None.
See TPF Database Reference for more information
about offline pool maintenance.
Where:
Severity: 4
Explanation: An END operand was specified that is not valid.
System Action: None.
User Response: The operand is assumed to be END so no action is necessary unless this message
is generated by a SENDG that was not suppose to have an END
operand.000000000 INVALID END OPERAND SPECIFIED - xxx
000000000 | INVALID FIELD TYPE ON DRIL - RECORD DELETED |
Explanation: CC68 of the DRIL record is in error. This message indicates that the record was deleted from the library for this run.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information about the system test compiler (STC).
000000000 | INVALID FILE ADDR -- SELD UNABLE TO RETRIEVE THIS RECORD |
Explanation: None.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | INVALID FORMAT MSG IGNORED |
Explanation: A program test vehicle (PTV) ZSTVS command was entered incorrectly.
System Action: None.
User Response: Enter the command again.
See TPF Program Development Support Reference for more information.
000000000 | INVALID --FROM-- OPTION, EXPECTING FOLLOWING --TO-- |
Explanation: A FROM keyword and value was found without a corresponding TO option.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the multiple assembly and compilation program.
000000000 | INVALID HEADER BIT CONTROL INDICATOR IN DRIL--DELT |
Explanation: CC71 of the DRIL record is in error.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information about the system test compiler (STC).
000000000 | INVALID KEYWORD ON CONTROL CARD |
Explanation: A keyword on a control card is not LIST, FROM, TO, or SUFFIX.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about variable cross referencing and the multiple and assembly compilation program.
000000000 | INVALID LABEL FOUND |
Explanation: The card image, the program name, and the label that is not valid are provided.
System Action: None.
User Response: None.
000000000 | INVALID LENGTH ON DRIL HDR - RECORD DELETED |
Explanation: This message indicates that the record was deleted from the library for this run.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for
more information about the system test compiler (STC).
Severity: 4
Explanation: The line type specified in the first parameter of a QI operand is not
valid.
System Action: None.
User Response: Do the following:
Severity: 4
Explanation: The physical line number specified in a PATH parameter was not a valid
hexadecimal number or was greater than 3EF.
Path definitions begin at the STIMnn tag and the dummy paths are
initialized to 6 bytes of zeros.
System Action: None.
User Response: Do the following:
Severity: 8
Explanation: The value specified in LNSY parameter is not a valid hexadecimal or the line
number specified is greater than the maximum symbolic line number as generated
by the system initialization program (SIP).
System Action: None.
User Response: Do the following:
Severity: 8
Explanation: The physical line number specified in the LINE parameter was not defined in
the PATH parameter of the preceding SKLNG macro as a remote path.
System Action: None.
User Response: Do the following:
000000000 INVALID LINE DISCIPLINE ATTACHED TO QI
000000000 INVALID LINE IN PATH PARAMETER - DEFAULTED TO VOID PATH
000000000 INVALID LINE NUMBER - SCK GENERATION SUPPRESSED
000000000 INVALID LINE SPECIFIED - REMOTE TABLE GENERATION SUPPRESSED
000000000 | INVALID LINKER RTN CODE DURING SALTBL LOAD |
Explanation: A return code that is not valid was received from the linkage editor (LEDT) for the system allocator (SAL) table (SALTBL) load.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for
more information about the loaders program.
Severity: 4
Explanation: The LOAD parameter did not contain YES or NO.
System Action: None.
User Response: If the default is not acceptable, correct the input and rerun Phase
I.000000000 INVALID LOAD SPECIFIED 'NO' DEFAULT SUBSTITUTED
000000000 | INVALID/MISSING PARM FIELD, CHECK PARM STMNT |
Explanation: This is a Type E error. A parameter field was not coded with the words CREATE, MODIFY or the parameter field was omitted from the EXEC JCL card.
System Action: The run is ended.
User Response: Do the following:
See TPF Database Reference for more information about mapping support installation.
000000000 | INVALID MODE PARAMETERS |
Explanation: The mode parameter (STV mode) of the program test vehicle (PTV) ZSTVS START RUNID XY command was not in the valid range. Parameter X can only be A or B. Parameter Y can be a numeral from 1 through 9.
System Action: None.
User Response: Enter the command again.
See TPF Program Development Support Reference for
more information.
Severity: 4
Explanation: The PID parameter did not contain a valid single alphabetic character.
System Action: None.
User Response: If the default is not acceptable, correct the input and rerun Phase
I.000000000 INVALID NON ALPHABETIC CHARACTER USED FOR PID DEFAULT 'A'
SUBSTITUTED
000000000 | INVALID NUMBER OF MESSAGES, DEFAULTED TO ONE |
Explanation: The number of messages specified on the RUNID must be between 1 and 9.
System Action: None.
User Response: None.
000000000 | INVALID OPERAND FOUND |
Explanation: The card image, the program name, and the operand that are not valid are given.
System Action: None.
User Response: None.
000000000 | INVALID OPERATOR FOUND |
Explanation: The card image, the program name, and the operation code that is not valid are given.
System Action: None.
User Response: None.
000000000 | INVALID ORD NO. LENGTH ON DRIL -- RECORD DELETED |
Explanation: A number that is not valid was used for the length. This message indicates that the record was deleted from the library for this run.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | INVALID ORD NUMBER |
Explanation: None.
System Action: None.
User Response: None.
See TPF Operations for more information about online file recoup.
000000000 | INVALID ORG CARD IN DRIL -- RECORD DELETED |
Explanation: Parameters that are not valid were found on the origin card.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | INVALID PARAMETER IN TYPE LIST |
Explanation: The line type in the list is not within range of valid line types defined in the TPF system.
System Action: None.
User Response: None.
000000000 | INVALID PATCH CARD |
Explanation: The patch card is not valid.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for
more information about loaders.
Severity: 4
Explanation: One of the following errors occurred:
System Action: None.
User Response: Do the following:
000000000 INVALID PATH INDICATOR - MA ASSUMED
000000000 | INVALID PHASE I MACRO INTERRUPT CODE yyyyyy xxxx |
Where:
Explanation: An illegal SVC code was issued. Control is transferred to the DENDT macro.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | INVALID POOL MAINTENANCE INPUT TAPE |
Explanation: The first record of the primary real-time tape (RTA) is not a dump formatter record or a record on an RCP tape is not a recoup logging record. The tape is therefore considered not valid.
System Action: None.
User Response: Do the following:
See TPF Database Reference for more information about offline pool maintenance.
000000000 | INVALID PROC ID IN KEYPT CALL - JOB ABORTED |
Explanation: The processor ID is not valid.
System Action: None.
User Response: Do the following:
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | INVALID RECORD FOUND ON INPUT RCP TAPE. |
Explanation: The program found a primary real-time tape (RCP) that is not valid. The CY6PGM field did not contain the correct subsystem user ID in a MDBF system.
System Action: None.
User Response: Do the following:
See TPF Database Reference for more information about offline pool maintenance.
000000000 | INVALID RECOUP KEYPOINT RECORD--RUN ABORTED |
Explanation: The disk pack mounted as RGF does not contain a valid recoup keypoint record. Either the wrong disk pack was mounted or recoup phase 3 must be rerun.
System Action: None.
User Response: Do one of the following:
See TPF Database Reference for more information about offline pool maintenance.
000000000 | INVALID REC TYPE |
Explanation: None.
System Action: None.
User Response: None.
See TPF Operations for more information about online file recoup.
000000000 | INVALID REQ MADE DURING SALTBL LOAD |
Explanation: None.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about loaders.
000000000 | INVALID REQUEST MSG IGNORED |
Explanation: A program test vehicle (PTV) service request was issued in the wrong operating state.
System Action: None.
User Response: Do the following:
See TPF Program Development Support Reference for more information.
000000000 | INVALID RETURN CODE FROM LEDT, JOB ABORTED |
Explanation: TLDR called the linkage editor (LEDT) to perform link editing and received an unknown return code.
System Action: The load is ended.
User Response: See your system support personnel for help resolving the error.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | INVALID SET COUNT ON DRIL -- RECORD DELETED |
Explanation: This message indicates this record was deleted from the library for this run.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information about the system test compiler (STC).
000000000 | INVALID SLOT DISPLACEMENT ON DRIL -- RECORD DELETED |
Explanation: A character that is not valid was used for displacement. This message indicates this record was deleted from the library for this run.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for
more information.
Severity: 4
Explanation: One or both of the subchannel addresses specified in PHADR parameter is not
valid.
System Action: None.
User Response: Do the following:
000000000 INVALID SUBCHANNEL RANGE
000000000 | INVALID SYNTAX IN CONTROL CARD |
Explanation: The syntax in the control card is not valid.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the multiple assembly and compilation print program.
000000000 | INVALID SYNTAX ON CNTRL CARD |
Explanation: The syntax on the control card does not correspond to the rules specified.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about variable cross referencing.
000000000 | INVALID TAPE -- NO DX RECORD ON TAPE |
Explanation: The tape being post processed does not contain a dump label (DX) record before the second tape mark on the tape. The STPP post processor expects one tape mark between the header labels and data, and a second tape mark between the data and trailer labels. If a DX record is not contained between the two tape marks, the tape is considered not to be valid.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | INVALID TRAC OPTION CARD |
Explanation: The program test vehicle received an RTT UNABLE message from real-time trace (RTT) caused by a TRAC option. PTV constructs and sends the ZTRAC 00F+ command to RTT.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information about the RTT utility. See TPF Operations for more information about the ZTRAC command.
000000000 | INVALID TRAP OF A PHASE I MACRO -- TRPMT yyyyyy |
Where:
Explanation: Control is transferred to the next sequential instruction in the driver program.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | INVALID TRCE OPTION CARD |
Explanation: The program test vehicle received a SFDP UNABLE response from SFDP caused by a TRCE option.
System Action: The SFT option is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | INVALID UNTRAP OF A PHASE I MACRO -- STPMT yyyyyy |
Explanation: Control is transferred to the next sequential instruction in the driver program.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | I/O ERROR DURING BLDL MACRO |
Explanation: None.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about loaders.
000000000 | I/O ERROR OCCURRED IN READING THE DIRECTORY. JOB TERMINATED |
Explanation: An error occurred while reading the directory block.
System Action: Processing is ended.
User Response: None.
See TPF System Installation Support Reference for more information about macro cross referencing.
000000000 | I/O ERROR ON GEN FILE AT CCHHR cccchhhhrr |
Where:
Explanation: This error message is issued out of ALDR relatively early in the load process. Other messages may or may not accompany this message. It is a severe problem caused by one of the following:
System Action: None.
User Response: Do the following:
If the input/output (I/O) error persists, have the pack checked.
See TPF System Installation Support Reference for more information about loaders.
000000000 | I/O ERROR ON GENERAL FILE AT CYLINDER xxx HEAD xxx RECORD xxx--RUN ABORTED |
Where:
Explanation: The program was unable to read or write the general file (DGF or RGF) at the indicated address.
System Action: None.
User Response: None.
See TPF Database Reference for more information about offline pool maintenance.
000000000 | I/O ERROR ON OBJLIB |
Explanation: None.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about loaders.
000000000 | I/O ERROR READING nnnnvv |
Where:
Explanation: There was an input/output (I/O) error while reading the program name and version number referenced in the message.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about loaders.
000000000 | I/O ERROR READING CP |
Explanation: An input/output (I/O) error occurred while reading the control program (CP).
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about loaders.
000000000 | I/O ERROR READING CP -- JOB ABORTED |
Explanation: An input/output (I/O) error occurred while reading the control program from the load library.
System Action: None.
User Response: Run the job again. If the problem continues, check the pack.
See TPF System Installation Support Reference for more information about macro cross referencing.
000000000 | JCD TAPE RECORD xxx HAS yy FOR AN ID. THIS IS UNACCEPTABLE. |
Where:
Explanation: An unidentifiable record identification character causes this message and stops the reduction run.
System Action: None.
User Response: None.
See TPF Operations for more information about system performance.
000000000 | JCD TAPE RECORD xxx IS OUT OF ORDER. REDUCTION WILL PROCESS INFORMATION GATHERED TO THIS POINT AND TERMINATE. |
Where:
Explanation: The JRA1, JRA2, JRM1, and JRF1 offline segments print this message when a record is written to the JCD tape in the wrong order. The record number is equivalent to the value in DCOUNT.
System Action: None.
User Response: Review the record on the tape with that corresponding number to diagnose the problem.
See TPF Operations for more information about system performance.
000000000 | JOB ABORTED -- FIX LOAD ADDRESS CARD AND RESTART JOB |
Explanation: The format of the load address card is incorrect.
System Action: None.
User Response: Check the card for valid addresses in the correct card columns.
See TPF Program Development Support Reference for more information.
000000000 | KEYPOINT CTKxvv IS TOO LARGE -- JOB ABORTED |
Where:
Explanation: The keypoint exceeds its maximum size.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | KEYPOINT READ ERROR |
Explanation: A keypoint read error occurred.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about loaders.
000000000 | KEYPOINTS ALLOCATION ON GF CONTAINS INSUFFICIENT ROOM FOR GF, RT, AND ONLINE KPT PATCH AREA |
Explanation: None.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about loaders.
000000000 | KEYPT nnnnvv, INCORRECT NAME |
Where:
Explanation: The name on a general file or on a call keypoint card is not valid.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about loaders.
000000000 | KEYPT OR AP NAME CANNOT BE FOUND IN NAMETBL |
Explanation: One of the keypoints or AP programs was not found in the name table of TLDR.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | KEYWORD ON CONTROL CARD IS NOT --LIST-- |
Explanation: A control card has been read on which the keyword is not LIST.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for
more information about the multiple assembly and compilation print
program.
Severity: 4
Explanation: The LNSY parameter for LC type lines were not specified consecutively on the
SKLNG macros.
System Action: None.
User Response: Do the following:
000000000 LC LINE NUMBERS NOT CONSECUTIVE
000000000 | LDCR READ ERROR |
Explanation: An error occurred reading the general file loader control record.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about loaders.
000000000 | LENGTH OF FROM/TO VALUE GREATER THAN 8 CHARACTERS |
Explanation: A value assigned to a FROM or TO keyword exceeds eight characters.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the multiple assembly and compilation print program.
000000000 | LINE LENGTH FOR TYPE T OR FD EXCEEDED FOR THIS DEV. TYPE. --zz-- MAP NAMED xxxx TERMINATED |
Where:
Explanation: This is a Type E error. A DDATA statement with a TYPE= T or FD has a CON== parameter coded. This constant data exceeds the line size for the device type referenced in the message.
System Action: The map referenced in the message is not generated.
User Response: None.
See TPF Database Reference for more information
about mapping support installation.
Severity: 4
Explanation: SCK macros should be coded in ascending line number order, so that the
generation macros can check that all SCKS have been initialized. This
message would also be output if line numbers 0 or 1 were coded or any number
between the maximum HS and the minimum LS line number.
System Action: None.
User Response: Check that an SCK was created for every line in the TPF system.000000000 LINE NUMBER OUT OF SEQUENCE - CHECK ALL SCKS INITIALIZED
000000000 | LIVE TEST ACTIVATE LINES |
Explanation: Lines will be activated as stated in the procedures found in TPF Operations for control programs.
System Action: None.
User Response: None.
See TPF Operations for more information about the program test vehicle (PTV).
000000000 | LIVE TEST ACTIVE -- INVALID REQUEST -- RESET ONLY VALID |
Explanation: The program test vehicle (PTV) was requested to operate in Live mode only through the ZSTVS TEST LIVE command. The only PTV request that can now be serviced is the PTV reset command. Any other PTV service request will cause the previous message to be generated.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | LNS zz aaa |
Where:
Explanation: This formatted message is sent to the computer room agent set (CRAS) console that requested the single processor display.
System Action: None.
User Response: None.
000000000 | LOADER CONTROL CARD ERROR |
Explanation: A loader control card error occurred.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about loaders.
000000000 | LOADER CTRL CARD OUT OF SEQ |
Explanation: The call keypoint card is out of sequence.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about loaders.
000000000 | LOADER COMPLETE |
Explanation: This message is sent to SYSLOG at the completion of the general file load. At this time the general file should be IPLed, if there were no input errors. If no errors occurred, an IPLable module to be used as input to the TPF general file loader online segment is now available. It contains programs, keypoints, and online keypoint patches to be loaded to the online files, as specified in the general file loader control record.
A listing of all the programs and patches loaded was generated by ALDR with an indication of errors and warnings of suspected errors.
System Action: None.
User Response: None.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | LOADER COMPLETE INPUT ERROR CHECK PRINTER FOR DETAILS |
Explanation: See the explanation for LOADER COMPLETE for more information.
System Action: See the system action for LOADER COMPLETE for more information.
User Response: See the user response for LOADER COMPLETE for more information.
See TPF System Installation Support Reference for more information about the loaders program.
000000000 | LOADING DATA FROM TEST UNIT |
Explanation: This message indicates that data is being loaded from the test unit.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | LOADING PILOT SYSTEM |
Explanation: The program test vehicle (PTV) loaded the PILOT system requested in the RUNID option.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | LOADING PROGRAMS FROM TEST UNIT |
Explanation: This message indicates that the programs are being loaded from the test unit.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | LOAD MAY BE INCOMPLETE, xxxx WAS NOT LOADED |
Where:
Explanation: One or more components not loaded were marked as required for one of the following reasons:
If this load is for the basic subsystem (BSS), any specified components must be loaded. Otherwise, this message can be ignored for subsystem shared components.
System Action: None.
User Response: If the specified component is required by the subsystem, run ALDR again and include the component in the load deck.
See TPF System Installation Support Reference for
more information about the loaders program.
Severity: 12
Explanation: The only valid options for this parameter are LOCKF=DASD and
LOCKF=PROC.
System Action: None.
User Response: None.
Severity: 12
Explanation: The only valid options for this parameter are LOCKP=DASD and
LOCKP=PROC.
System Action: None.
User Response: None.
Severity: 12
Explanation: The only two valid options for this parameter are LOG=YES or LOG=NO.
System Action: None.
User Response: None.
Severity: 4
Explanation: It is possible to generate PKSTs without previously generating the
SCKs. In this case, this message will be generated on the first PKSTG
macro but it can be ignored. If SCKs are being created in this run, the
first PKSTG should follow a SENDG macro.
System Action: None.
User Response: Do the following:
Severity: 4
Explanation: None.
System Action: None.
User Response: Do the following:
Severity: 4
Explanation: None.
System Action: None.
User Response: Do the following:
Severity: 8
Explanation: One of the following occurred:
System Action: None.
User Response: Do the following:
Severity: 8
Explanation: See the SKLNG macro errors.
System Action: None.
User Response: Do the following:
000000000 LOCK FIXED PARAMETER INVALID
000000000 LOCK POOL PARAMETER INVALID
000000000 LOGGING PARAMETER INVALID
000000000 MACRO SEQUENCE ERROR - MUST FOLLOW SENDG MACRO
000000000 MACRO SEQUENCE ERROR - MUST FOLLOW SENDG MACRO - ALL
MACROS SINCE LAST SENDG IGNORED
000000000 MACRO SEQUENCE ERROR - MUST FOLLOW SENDG MACRO - ALL
MACROS SINCE LAST SENDG IGNORED
000000000 MACRO SEQUENCE ERROR - SENDG WITH END PARAMETER FOUND -
MACRO IGNORED
000000000 MACRO SEQUENCE ERROR - SENDG WITH END PARAMETER FOUND -
MACRO IGNORED
000000000 | MAP-xxxx-FOR DEV. TYPE -zz- GENERATED SUCCESSFULLY |
Where:
Explanation: This is a Type C error.
System Action: None.
User Response: None.
See TPF Database Reference for more information about mapping support installation.
000000000 | MAP--xxxx--HAS NO SEQUENCE #, TERMINATED |
Where:
Explanation: This is a Type E message. The user map specified in the message is not coded with a SEQNO operand or the sequence number (1 through 9999) is not valid.
System Action: None.
User Response: Do the following:
See TPF Database Reference for more information about mapping support installation.
000000000 | MAP NAMED--xxxx FOR ADD/REPLACE NOT FOUND |
Where:
Explanation: This is a Type E error. The map name on the ADD/REPLACE statement does not match a map statement in the user's map source library.
System Action: This statement is ignored and the next ADD/REPLACE statement, if there is any, is read.
User Response: None.
See TPF Database Reference for more information about mapping support installation.
000000000 | MAP NAME MISSING FROM DPANL STMNT, MAP TERMINATED DIR NAME=xxxx |
Where:
Explanation: This is a Type E error. The source member read from the user's map library does not contain a four character map name.
System Action: This map is not created.
User Response: None.
See TPF Database Reference for more information about mapping support installation.
000000000 | MAX (nnn) NO OF ALLOWED VARIABLES EXCEEDED INCREASE &VBLS AND REAS |
Where:
Explanation: The number of global variables allowed for the program, which are specified in the message, is less than the number occurring in the member being processed when the message is issued.
System Action: None.
User Response: Do the following:
See TPF System Installation Support Reference for more information about variable cross references.
000000000 | MAX (nnn) NO. OF CONTINUATION CARDS EXCEEDED/INCREASE &CONTCRD REASSEMBLE |
Where:
Explanation: The program allows for the amount of continuation cards specified in the message in a statement. A statement has more than this number of continuation cards when this message is issued.
System Action: None.
User Response: Do the following:
See TPF System Installation Support Reference for more information about variable cross references.
000000000 | MAX (n) NO OF ENTRIES ALLOWED IN CONTROL CARD LIST EXCEEDED - INCREASE VARIABLE &LISTMEM AND REASSEMBLE |
Where:
Explanation: The program can print a list of up to the value specified in the message. The list, which is input to the program, exceeds this number of entries.
System Action: None.
User Response: Do the following:
If you prefer, you can run the program more than once with a smaller control card list.
See TPF System Installation Support Reference for more information about the multiple assembly/compilation print program.
000000000 | MAX (nnn) NO. OF MEMBERS FOR LIST EXCEEDED/INCREASE &LISTMEM A REASSEMBLE |
Where:
Explanation: The LIST option was used to specify a list of members to be cross referenced. The program can only handle the number of members specified in the message.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the variable cross reference.
000000000 | MAXIMUM (n) NO. OF MEMBERS FOR LIST EXCEEDED |
Where:
Explanation: Only the number of members specified in the message are allowed in a list. The list supplied on a control card exceeds this number.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference
for more information about the multiple assembly/compilation
program.
Severity: 4
Explanation: The SKLNG macro will allow at most 16 Local 3270(LC) control units in the
gen.
System Action: None.
User Response: Increase the size of the table XACUTAB in the SKLNG macro.000000000 MAXIMUM NUMBER OF LC CU EXCEEDED
000000000 | MESSAGE TOO LARGE, REJECTED |
Explanation: The length of the old format message was greater than 768 or the length of the new format message was greater than the &SAM3270 system initialization program (SIP) variable.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | MESSAGE TOO SMALL, REJECTED |
Explanation: The input message from the test unit tape (TUT) had a count of less than four (the line number, interchange address, and terminal address (LNIATA) plus one character).
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | MISSING RIGHT PAREN IN LIST -- ASSUMED ), CONTINUE |
Explanation: A list of members on a list control card was not ended by a right parenthesis.
System Action: A right parenthesis is assumed.
User Response: None.
See the TPF System Installation Support Reference for more information about the multiple assembly/compilation program.
000000000 | MODIFY STATEMENT -- INVALID OPTION IN COL 1 CARD IGNORED |
Explanation: This is a Type E error. The modify statement displayed with this error message does not have A, D, M or A in column 1.
System Action: This statement is ignored and the next statement is read.
User Response: None.
See the TPF Database Reference for more information about mapping support installation.
000000000 | MORE THAN 10 ORD NUMBERS--MSG REJECTED |
Explanation: None.
System Action: None.
User Response: None.
See TPF Operations for more information about online file recoup.
000000000 | MOUNT CORRECT DISK PACK AND RESTART JOB |
Explanation: The system test compiler (STC) encountered a NO RECORD FOUND or a READ ERROR on the unit test disk or the object library disk.
System Action: STC cannot continue.
User Response: Try another unit test disk.
See TPF Program Development Support Reference for more information.
000000000 | MPIF FILE SEQUENCE ERROR. OUTPUT REPORT MAY BE INCORRECT |
Explanation: When reading Multi-Processor Interconnect Facility (MPIF) path plot and distribution data from the sorted file MDWKOUT, a problem with the amount of data was found. Since the plots and distribution reports were already printed, it should be noted that they may contain incorrect data.
System Action: None.
User Response: None.
See TPF Operations for more information about system performance.
000000000 | MPIF PATH ENTRY SEQUENCE ERROR X. PREVIOUSLY ACCUMULATED DATA CLEARED |
Explanation: This message indicates that an incongruity was found in the order of the Multi-Processor Interconnect Facility (MPIF) path entries within the MD records read from the RTC tape.
System Action: The path data accumulated up to this point may be incorrect and is therefore cleared out so that an attempt to accumulate new, valid path data can begin from the remaining MD records. The resulting report will not be representative of the entire sampling period.
User Response: None.
See TPF Operations for more information about system performance.
000000000 | NEGATIVE RESPONSE TO POLLING (ICBIS = X'0B') -- R TNK00 |
Explanation: None.
System Action: None.
User Response: None.
000000000 | NO ASSIGNED FILE STORAGE AREAS REMAINING CORE DUMP FOLLOWS RUN DISCONTINUED |
Explanation: All of the disk areas assigned to the system test compiler (STC) loader by the load address cards were used.
System Action: The run is started again.
User Response: Do the following:
See TPF Program Development Support Reference for
more information.
Severity: 0
Explanation: None.
System Action: None.
User Response: None.000000000 NO BST PARAMETERS SPECIFIED FOR BSC LINE
000000000 | NO BKD TAPE LABEL MASK INFORMATION |
Explanation: None.
System Action: None.
User Response: None.
See TPF Operations for more information about online file recoup.
000000000 | NO CORE BLK AVAILABLE FOR PTV MESSAGE |
Explanation: This error condition occurs while trying to add a message to the input list during system test or package test, or for LOMET processing during unit test.
System Action: The message is ignored.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | NO CORE FOR LIST -- INCREASE REGION SIZE |
Explanation: A LIST option was found on a control card and a GETMAIN macro issued to obtain core to build this list.
System Action: The requested core is not available.
User Response: Increase the region size.
See the TPF System Installation Support Reference
for more information about the multiple assembly/compilation
program.
Severity: 8
Explanation: The CUNO parameter must be specified.
System Action: None.
User Response: Do the following:
000000000 NO CU NUMBER - PKST GENERATION SUPPRESSED
000000000 | NO DUPLICATE RECORDS ALLOWED. A DUPLICATE HAS BEEN FOUND IN THIS RUN -- THE RUN WILL BE TERMINATED WITH NO NEW LIBRARY |
Explanation: Two records with the same ID were created in this run. If no records were created or updated during this run, the message will also appear.
System Action: None.
User Response: Do the following:
See the TPF Program Development Support Reference for more information.
000000000 | NO DUPLICATE RECORDS ARE ALLOWED. THE OLD RECORD WILL BE PUT ON THE LIBRARY WITH THE NEWLY CREATED RECORD TO BE DUMPED |
Explanation: A record was created with the same ID as one already on the library. The old record will remain on the library.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | NO (DE) RECORD ON TAPE xx |
Where:
Explanation: This message is printed when no DE record is found on any of the RTC files being merged.
System Action: JRC1 processing is continued.
User Response: None.
000000000 | NO ERRONEOUSLY AVAILABLE ADDRESSES APPEAR ON THE TAPE(S) USED IN THIS RUN |
Explanation: Tests are made for the start of an erroneously available address message and the end of a recoup seld message. The finding of either of these messages will cause the processed lost addresses to be summarized and printed. In addition, if it was the end of a recoup seld message that was found, the NO ERRONEOUSLY AVAILABLE ADDRESSES APPEAR ON THE TAPE(S) USED IN THIS RUN message is printed.
If the start of an erroneously available address message was found first, erroneously available addresses would be processed and when the end of recoup seld message was found, these processed addresses would be summarized, printed and the job ended.
System Action: None.
User Response: None.
See the TPF Database Reference for more information about offline pool maintenance.
000000000 | NO GF CONF CRD |
Explanation: The general file configuration card is missing.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about loaders.
000000000 | NO GLOBAL VARIABLES USED IN MEMBERS SEARCHED |
Explanation: The members searched (PDS data definition as modified by LIST option) did not contain any global variable definitions.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference
for more information about variable cross references.
Severity: 8
Explanation: The LNSY parameter was omitted in the SKLNG macro call.
System Action: None.
User Response: Do the following:
000000000 NO LINE ENTRY - SCK GENERATION SUPPRESSED
000000000 | NO MESSAGE DATA FOR LU STREAM REPORT |
Explanation: This message is printed in place of the requested logical unit message.
System Action: None.
User Response: None.
See TPF Operations for more information about system performance.
000000000 | NO MESSAGE DATA FOR STREAM REPORT |
Explanation: This message is printed in place of the requested message stream report when no records exist in the file name starting with MS.
System Action: None.
User Response: None.
See TPF Operations for more information about system performance.
000000000 | NO MESSAGE DATA FOR THOSE CITIES REQUESTED FOR TERMINAL ACTIVITY |
Explanation: This message is printed in place of the requested terminal activity reports when no MI/MO records exist in the file name starting with MT.
System Action: None.
User Response: None.
See TPF Operations for more information about system performance.
000000000 | NO MESSAGE DATA FOR THOSE NODES REQUESTED FOR LU ACTIVITY REPORT |
Explanation: This message is printed in place of the requested logical unit activity reports when no NI/NO records exist in the file name starting with MT.
System Action: None.
User Response: None.
See TPF Operations for more information about system performance.
000000000 | NO PARS LISTS FOUND -- RUN WILL CONTINUE WITHOUT IN-CORE DIRECT |
Explanation: None.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference
for more information about the loaders program.
Severity: 4
Explanation: One of the following errors occurred:
System Action: None.
User Response: Do the following:
000000000 NO PRIME PATH - DEFAULTED TO FIRST NONVOID
000000000 | NO RCPL CARD -- RCPL SET TO HEX 00 IN CREATED MESSAGE |
Explanation: When creating a SNA-type message using the AM0SG/AM1SG/AM2SG DRIL record, the user failed to specify a routing control parameter list (RCPL).
System Action: The RCPL in the created message was set to a X'00'.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | NO REPORTS PRINTED DUE TO LACK OF INPUT MESSAGES |
Explanation: This message is printed in place of the requested message reports if there were no high-speed input messages recorded on the RTC tape by the message collector.
System Action: None.
User Response: None.
See TPF Operations for more information about
system performance.
Severity: 8
Explanation: Generation of the SCK record was suppressed due to one of the errors listed
previously.
System Action: None.
User Response: Do the following:
000000000 NO SCK RECORD GENERATION
000000000 | NO TIME VALUE ENTERED IN RUNID, PTV WILL DEFAULT TO 30S FOR PHASE I |
Explanation: The maximum run time for a phase I test unit was not specified on the RUNID. If this is a phase I test unit, 30 seconds will be the default set.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | NO TUT ASSIGNED PROCESSING STOPPED |
Explanation: A resume test (system test vehicle (STV) mode) ZSTVS START POSIT command was entered but the test unit tape was not assigned in the tape table.
System Action: None.
User Response: Do the following:
See TPF Program Development Support Reference for more information.
000000000 | NOT A CONTROL CARD -- CARD IGNORED |
Explanation: SDMU is looking for a control card at this time and this card is not a control card.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | NOT APPLIED -- INVALID DELIMITER ON REP CRD |
Explanation: Commas do not separate every two bytes of patch data on the REP card.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT APPLIED -- INVALID HEX DATA ON REP CARD |
Explanation: One of the following errors occurred:
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT APPLIED -- NAME NOT EQUAL TO PGM CALLED |
Explanation: The name on the patch card does not match the program or keypoint name on the LOADER CALL card.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT APPLIED -- PATCH ADDR BEYOND PGM LIMITS |
Explanation: The patch address on the REP card is greater than the allocated size.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT APPLIED -- PATCH ADDR NOT HALFWORD BDWY |
Explanation: The patch address on the REP card is not a half-word boundary.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT APPLIED -- PATCH CARD FORMAT ERROR |
Explanation: The format of this REP card is incorrect.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT APPLIED -- PATCH NAME NOT IN PARS LIST |
Explanation: There was no corresponding name found in the programmer airlines reservation system (PARS) list for this patch name.
System Action: None.
User Response: Do one of the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT APPLIED -- PGM BYPASSED |
Explanation: This REP card belongs to a program that has a later call superseding it. Therefore, the program and this REP card are ignored.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT ENOUGH CORE ALLOCATED FOR PGM TABLE -- JOB ABORTED |
Explanation: The minimum of 4000 bytes of storage cannot be allocated for the program table in BPR0. Alternatively, the requested core for the program table was not allocated.
System Action: None.
User Response: Do the following:
See the TPF Database Reference for more information about offline pool maintenance.
000000000 | NOT ENOUGH ROOM FOR SALTBL |
Explanation: There is not enough room for the system allocator (SAL) table (SALTBL).
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about loaders.
000000000 | NOT FIRST RTL TAPE JOB CANCELLED. MOUNT FIRST TAPE AND RESTART JOB. |
Explanation: For a multi-volume data set, the sequence for mounting the tape was incorrect.
System Action: None.
User Response: Do the following:
See the TPF Database Reference for more information about offline pool maintenance.
000000000 | NOT HWD BDRY |
Explanation: The REP card address field is not on a half-word boundary.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about loaders.
000000000 | NOT LOADED -- BAD CARD IN OBJECT MODULE |
Explanation: There is something is wrong with this program's object module.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- DUMMY PROGRAM |
Explanation: The program that the TPF system tried to load is defined in the allocator table as a dummy program.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- END CARD NOT FOUND IN OBJECT MODULE |
Explanation: There is no END card in this program's object module.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- I/O ERROR ON DIRECTORY SEARCH |
Explanation: An unrecognizable input/output (I/O) error was encountered while trying to locate the program in the PDS object library.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- KYPT NAME REFERENCE INVALID |
Explanation: A keypoint name that is not valid was found on the call keypoint card.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- LOAD MODULE LARGER THAN CLMSIZE |
Explanation: The auxiliary loader (TLDR) 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 the TPF System Installation Support Reference for more information.
000000000 | NOT LOADED -- PGM CAN ONLY BE LOADED IN THE BSS |
Explanation: TLDR verifies that IPLB, ICDF, ACPL, and the ISO-C libraries (TPF API, TPFDF, and standard C) are not loaded on a subsystem other than the basic subsystem (BSS) (SYSID=BSS).
System Action: None.
User Response: Do one of the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- PGM HAS TOO MANY EXTRNS |
Explanation: This program has too many external references (ESDs) entries in the object module.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- PGM NAME IS A TRANSFER VECTOR |
Explanation: The program name specified is a transfer vector in the system allocator (SAL) table.
System Action: This program is not loaded.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- PGM NAME UNEQUAL TO BEGIN HEADER |
Explanation: The application program name (loader call program card columns 21 through 24 or the programmed airlines reservation system (PARS) list entry) does not match the Z4 VCON name found in its BEGIN expansion while processing TLDR.
System Action: The program is not loaded.
User Response: Check the object module's source code to ensure that the NAME parameter on the BEGIN macro matches that segment name.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- PGM NOT FOUND IN LIBRARY |
Explanation: This program is not found in the load module libraries specified by the LOADMOD DD name or the object module libraries specified by the OBJDD DD name.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- PGM NOT REAL TIME |
Explanation: The loader has found an object module in the libraries specified by the OBJDD DD name, but the program object module has external reference (ESD) types that are unrecognizable by the TPF linkage editor (LEDT).
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- PGM SIZE TOO LARGE |
Explanation: The program size for a file-resident program is greater than the allocated size.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- PGM SUPERCEDED BY LATER CALL |
Explanation: The program is called later in the load deck. This message is informational only.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- PROGRAM NOT ALLOCATED |
Explanation: This program has no entry in the allocator table specified by the SALVERS card.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- THIS AP PGM RECORD NOT ALLOWED |
Explanation: An auxiliary loader critical program module cannot be loaded by the auxiliary loader. Some such modules are the auxiliary loader segments (CTLx) and OLD1.
System Action: None.
User Response: If these modules must be reloaded, then use the general file loader to load them.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NOT LOADED -- UNKNOWN ERROR DURING LINK |
Explanation: A bad error code was returned from the TPF linkage editor (LEDT).
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | NPx NOT FOUND IN INPUT STREAM -- NPx SET TO A HEX 6C |
Where:
Explanation: When creating either 3270 or SNA messages using the AM0SG/AM1SG/AM2SG DRIL records, the user did not specify NP1 or NP2 data. The NP1 and NP2 fields were set to X'6C' in the output message.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for more information.
000000000 | NUMBER OF EXTERNS IS GREATER THAN ALLOWABLE |
Explanation: The linkage program could not handle the EXTERNS.
System Action: None.
User Response: None.
See TPF Program Development Support Reference for
more information.
Severity: 4
Explanation: The number of paths specified must not be greater than the number specified in
the NPATH parameter of the SIP NETWK macro.
System Action: None.
User Response: None.000000000 NUMBER OF PATHS SPECIFIED GREATER THAN MAX SPECIFIED IN SIP
000000000 | OBJECT MODULE IS CORRUPTED, MUST BE RE-ASSEMBLED. PROGRAM LOAD IS IGNORED |
Explanation: An address in one of the text cards in the object module is not within the address limits of the program.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | OLD FORMAT TAPES ARE NOT SUPPORTED -- RUN ABORTED |
Explanation: The primary real-time tape (RTC) was produced by the TPF 3.1 system in a format not recognized by later versions of the TPF system.
System Action: The tape cannot be read.
User Response: Provide a tape formatted for the current system.
See the TPF Database Reference for more information about offline pool maintenance.
000000000 | OLD TAPE EOF ENCOUNTERED - # RECORDS READ = 0 - LOAD ENDED |
Explanation: An end-of-file (EOF) condition occurred before reading the first record during an online program load for one of the following reasons:
System Action: The load ECB is exited. If the tape was dismounted prior to the load ECB exiting, then a CTL-53 is issued.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the E-type loader routines. See TPF Operations for more information about the ZOLDR commands.
000000000 | OM BLOCK CHAINED TO ITSELF |
Explanation: None.
System Action: None.
User Response: None.
000000000 | OS/VS SORT PGM ERROR CAUSED FILE REDUCTION PGM TERMINATION OF: name |
Where:
Explanation: See the appropriate publication in the OS/VS library for the associated sort program diagnostics that will have occurred. File names that begin with SORT are those used by the sort program for these options.
System Action: None.
User Response: None.
See TPF Operations for more information about system performance.
000000000 | OVER 19 UNRSLVD XTRNS FOUND |
Explanation: Twenty or more unresolved externs were found. Only the first twenty unresolved externs are listed.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | OVER 50 PROGRAMS IN THIS TEST UNIT -- REMAINING PROGRAMS NOT LOADED |
Explanation: A maximum of 50 file-resident programs may be loaded from a test unit.
System Action: A surplus will be ignored.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | OVERLAPPING SON RANGES FOR DEVICES xxxx AND yyyy--RUN ABORTED |
Where:
Explanation: The base file address for the device referenced in the message, when combined with the number of modules for that device produces a file address range that overlaps the file address range for the other device referenced in the message.
System Action: None.
User Response: Do the following:
See the TPF Database Reference for more
information about offline pool maintenance.
Severity: 4
Explanation: OVFL and RTP1 are equivalent parameters. If the SIP RIATA macro coded
with the OVFL parameter is from a previous release, it can remain the
same; otherwise, RTP1 should be coded in its place.
RIAT is still generated but the OVFL parameter is not
used.
System Action: None.
User Response: None.000000000 OVFL IS EXTRANEOUS WHEN RTP1 IS CODED, OVFL IS IGNORED
000000000 | PARM ERROR |
Explanation: Either the PGMNBR or the PTCHNBR parameter did not have a valid value or the parameter specified was not valid.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PARS CARD EXPECTED .. JOB ABORTED |
Explanation: The card following the loader load OPL card is not a PARSvv card.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PARS LIST xx HAS NO ENTRIES -- RUN WILL CONTINUE |
Where:
Explanation: The OPL list was found but no items were in it.
System Action: The list is ignored and the load is continued.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PARS LIST vv NOT AVAILABLE ... IF IT IS REQ D FOR LOAD OPL, END RUN, TYPE Y=GO, N=EOJ |
Where:
Explanation: ALDR could not find the OPL list for the parameter version referenced in the message (specified in the loader CC card) for use in building in-core directories. This error will not cause a problem with the load but, if the same version is used during the load OPL phase, the loader will abend when the OPL LIST is not found.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PARS LIST vv NOT AVAILABLE - LOAD ENDS |
Where:
Explanation: ALDR could not find the OPL list for the parameter version referenced in the message (specified in the loader CC card) for use in building in-core directories.
System Action: The load ends.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PARS LIST ENTRIES EXCEED 4000 -- DIRECTORY BUILT WILL NOT BE COMPLETE |
Explanation: None.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PAT ORDINAL NUMBER FOR xxxx HIGHER THAN SALCOUNT, JOB ABORTED |
Where:
Explanation: The program allocation table (PAT) entry ordinal number for the program specified in the message returned by the TPF linkage editor (LEDT) is greater than the maximum ordinal number during offline TLDR process.
System Action: The program named in the message is not loaded.
User Response: Have your system programmer review the IPAT and SALTBL entry for the program named in the message.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PATCH CARD OUT OF SEQ |
Explanation: Either a REP card was read before the call program card or the program name on the REP card is incorrect.
System Action: None.
User Response: Do one of the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PATCH CARD OUT OF SEQUENCE |
Explanation: A REP card was read before a call program card.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information.
000000000 | PATCHING BEYOND CSECT END |
Explanation: A patch for a CP CSECT, ACPL, ICDF, SIGT, IPLB, FCTB, or record attribute table (RIAT) extends beyond the end of the CSECT.
System Action: The load is aborted.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PATCHING MORE THAN ONE VER. OF PGM DURING OPL LOAD -- CARD IGNORED |
Explanation: More than one version of the same program is being patched during an OPL load.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PERMANENT READ ERROR ON POOL MAINTENANCE INPUT TAPE--EOF ASSUMED |
Explanation: An irrecoverable read error was encountered while processing SYSIN. It is treated as an end-of-file indication since one of the possible causes is failure to write a tape mark on the real-time tape.
System Action: None.
User Response: None.
See the TPF Database Reference for more information about offline pool maintenance.
000000000 | PGM nnnnvv CORE SIZE xxxx EXCEEDS ALLOCATED SIZE yyyy, LOAD NO GOOD -- CORRECT AND RERUN |
Where:
Explanation: None.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PGM CALL NAME xxxxxx DOES NOT MATCH ITS BEGIN NAME yyyy -- PGM NOT LOADED. |
Where:
Explanation: The application program name (loader call program card columns 21 through 24 or the programmed airlines reservation system (PARS) list entry) does not match the Z4 VCON name found in its BEGIN expansion during processing of ALDR.
System Action: The program is not loaded.
User Response: Check the source code for the object model to ensure that the NAME parameter on the BEGIN macro matches that segment name.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PGM CAN ONLY BE LOADED IN LC -- NOT LOADED |
Explanation: SIGT can only be loaded in a loosely coupled system.
System Action: This program is not loaded.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PGM CAN ONLY BE LOADED IN MDBF - NOT LOADED |
Explanation: The program can only be loaded in a multiple database function (MDBF) system.
System Action: This program is not loaded.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PHASE I MACRO NOT ISSUED IN DRIVER yyyyyy xxxx |
Where:
Explanation: There was an illegal use of the program test vehicle (PTV) macro by a program other than the drive program.
System Action: Control is transferred to the next sequential instruction in the issuing program.
User Response: None.
See the TPF Program Development Support Reference
for more information.
Severity: 12
Explanation: The pool duration coded for this parameter is not ST (short term), LT (long
term, nonduplicated), or LD (long term, duplicated).
System Action: None.
User Response: None.
Severity: 4
Explanation: The pool specified for yyyy was not defined in the FACE table with
the SIP RAMFIL macro. The RIAT is still generated, but the use of
this pool type may cause errors online.
System Action: None.
User Response: None.000000000 "POOL" IS INVALID FOR xxxxx PARAMETER
000000000 POOL TYPE xxxx CODED FOR yyyy HAS NOT BEEN DEFINED
IN THE FACE TABLE
000000000 | POS. DISK IO ERR |
Explanation: There has been a possible disk error. A dump should be retained for verification of the error.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference
for more information.
Severity: 12
Explanation: The only two valid positional parameters for the RIATA macro are START and
FINISH.
System Action: None.
User Response: None.000000000 POSITIONAL PARAMETER NOT "START" OR "FINISH"
000000000 | POS. VALUE -- LAST LINE OF NOT VALID SCREEN REQUESTED |
Explanation: This is a type E error. A user defined a field in a DDATA statement with the POS operand coded for the last line of a 3270 CRT. This line is reserved for system messages.
System Action: None.
User Response: None.
See the TPF Database Reference for more information about mapping support installation.
000000000 | PREVIOUS PROGRAM ALREADY CALLED -- THIS PROG CALL IGNORED |
Explanation: The program being called was already called in this test unit.
System Action: The system test compiler (STC) ignores the current call.
User Response: None.
See the TPF Program Development Support Reference
for more information.
Severity: 4
Explanation: PRIME and RTP0 are equivalent parameters. If the RIATA macro coded with
the PRIME parameter is from a previous release, it can remain the same;
otherwise, RTP0 should be coded in its place.
RIAT is still generated but the PRIME parameter is not
used.
System Action: Nne.
User Response: None.000000000 PRIME IS EXTRANEOUS WHEN RTP0 IS CODED, PRIME IS IGNORED
000000000 | PRGM NOT LOADED, CORE ADDR INVALID, PROGRAM FOLLOWS |
Explanation: The main storage address for a main storage resident program is outside the boundaries specified in keypoint A. The test program from the TUT is written to the real-time tape (RTL) after the message.
System Action: The program is not loaded.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | PRIME DIRECTORY NOT FOUND -- RELOAD DISK |
Explanation: The system test compiler (STC) cannot find the SDMF/DRIL directory on the unit test disk.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | PROCESSOR NUMBER MISMATCH |
Explanation: While trying to patch a segment, this processor ordinal number was not found.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PROG nnnnvv ADDRESS NOT RESOLVED |
Where:
Explanation: The file address for the program specified in the message is not resolved in the system allocator (SAL) table.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PROG nnnnvv CNTNS CODE BEF BEGIN, PROG IGNORED |
Where:
Explanation: Program specified in the message contains code that ORGs back to a point before the end of the BEGIN statement.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PROG nnnnvv NOT ALLOCATED, PROG NOT LOADED |
Where:
Explanation: The program specified in the message was not found in the system allocator (SAL) table.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program and the system allocator.
000000000 | PROG nnnnvv NOT AVAILABLE FOR LOAD |
Where:
Explanation: A find request on the program specified in the message resulted in an error.
System Action: If the find request was for the programmed airlines reservation system (PARS) list, a keypoint or one of the core image restart area components then the load is aborted. Otherwise the load continues.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PROGRAM progname ALREADY PROCESSED -- PREVIOUS VERSION REMOVED |
Where:
Explanation: The program was already loaded in the TPF system. The new version of the program replaced the previous version.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about loading programs in the TPF system.
000000000 | PROGRAM nnnnvv LARGER THAN ALLOCATED SIZE -- PROG NOT LOADED |
Where:
Explanation: The object module for the program specified in the message is larger than the size allocated in the system allocator (SAL) table.
System Action: The program is not loaded.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | PROGRAM ALLOCATED AS A TRANSFER VECTOR -- PROGRAM CALL IGNORED |
Explanation: An error was encountered while trying to link-edit the object module, because the program name called is actually a transfer vector.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | PROGRAM NOT IN TRAP TABLE -- STPPT yyyyyy |
Where:
Explanation: There was a stop program trap of program not in trapped status.
System Action: Control is transferred to the next sequential instruction of the driver program.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | PROGRAM NOT REALTIME -- PROGRAM CALL IGNORED |
Explanation: All real-time programs must start with a BEGIN macro.
System Action: None.
User Response: Check the status of the requested program.
See the TPF Program Development Support Reference for more information.
000000000 | PROGRAM TABLE FULL - THIS PROGRAM CALL IGNORED |
Explanation: The program table already contains 64 program IDs, which is the maximum allowable number.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | PROGRAM TRAP TABLE FULL -- TRPPT yyyyyy |
Where:
Explanation: The program tried to trap more than ten programs.
System Action: Control is transferred to the next sequential instruction of the driver program. The requested program is not trapped.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | RCP ITEMS OUT OF SEQUENCE |
Explanation: The RCP items are either not in sequence or the gap is too big because of missing tapes.
System Action: The job is ended.
User Response: Use the correct RCP tapes and have them mounted in the correct order.
000000000 | RCP SEQUENCE NUMBER: nnnnnnnn IS IN ERROR - RUN ABORTE |
Where:
Explanation: The RCP items are either not in sequence or the gap is too big because of missing tapes.
System Action: The job is ended.
User Response: Use the correct RCP tapes and have them mounted in the correct order.
If this error message continues, there is probably a loss of critical data on the tapes. This loss probably occurred during recoup Phase 1. You will need to run recoup Phase 1 again.
000000000 | RCP SEQUENCE NUMBER ERROR--RUN ABORTED |
Explanation: The recoup logging records were not in correct sequence. Since the run depends on the integrity of these records, the job was canceled.
System Action: None.
User Response: None.
See the TPF Database Reference for more information about offline pool maintenance.
000000000 | RCPL INDICATES FMH -- LENGTH IS INVALID -- MESSAGE IGNORED |
Explanation: When specifying the routing control parameter list (RCPL), the user set bit 7 on, which indicates the FMH is included in the message text. However, the first character of the message text was not a valid FMH length (X'01 through 0F').
System Action: This message is ignored.
User Response: None.
See the TPF Program Development Support Reference
for more information.
Severity: 12
Explanation: The only valid options for this parameter are RCSF=RET, RCSF=CFWS, RCSF=CFWD,
RCSF=DFW, and RCSF=NO.
System Action: None.
User Response: None.
Severity: 12
Explanation: The only valid options for this parameter are RCSP=RET, RCSP=CFWS, RCSP=CFWD,
RCSP=DFW, and RCSP=NO.
System Action: None.
User Response: None.000000000 RCS FIXED PARAMETER INVALID
000000000 RCS POOL PARAMETER INVALID
000000000 | REAL-TIME TAPE HAS ALREADY BEEN PROCESSED. REPLY 'P' TO PROCESS OR 'I' TO IGNORE. |
Explanation: A tape was already processed having the same tape mount sequence number as this tape. Reprocessing the same tape can cause the same pool address to be used for more than one purpose at the same time.
System Action: None.
User Response: Reply P only when absolutely sure that the tape should be processed; for example, when the job is being rerun. Otherwise, reply I.
See the TPF Database Reference for more information about offline pool maintenance.
000000000 | RECORD AND/OR PROGRAM ID'S EXCEED MAXIMUM. THE FOLLOWING ID'S ARE NOT INCLUDED IN THE SUMMARY |
Explanation: The record ID table overflows when an attempt is made to enter more than 100 IDs. Program table overflow is detected by a compare of the address in the next available program table location counter with the end of core addresses each time an entry into the program table is made. If the end of core address is lower an overflow routine is entered.
The same overflow routine is used for both tables. Prior to any summarized data output this message is printed. Following this is a list of both the record IDs and program names, regardless of which table overflowed, is printed out.
System Action: None.
User Response: None.
See the TPF Database Reference for more
information about offline pool maintenance.
Severity: 12
Explanation: A RIATA call was coded without a START, FINISH, or ID parameter.
System Action: None.
User Response: None.
Severity: 12
Explanation: The record ID coded on the ID parameter is not correctly coded in hex, binary,
character, or decimal format.
System Action: None.
User Response: None.
Severity: 12
Explanation: The record ID coded (displayed in hex, character and decimal formats) is not
in the range 1-65535.
System Action: None.
User Response: None.000000000 RECORD ID PARAMETER MISSING
000000000 RECORD ID NOT SELF DEFINING TERM
000000000 RECORD ID(X"xxxx",
C"cc",D"ddd") OUT OF RANGE
(1-65535)
000000000 | REC/ORD FACE ERROR--NOT LOADED |
Explanation: None.
System Action: None.
User Response: None.
See TPF Operations for more information about online file recoup.
000000000 | RECORD ID IS ZERO |
Explanation: The record ID is not valid. The first 44 bytes of the record header are written to the real-time tape (RTL).
System Action: The record is ignored.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | RECORD NO. OR SLOT NO. REQUESTED TOO HI-ENTRY IGND |
Explanation: The slot number requested does not exist in the record or the record number requested is greater than the number of records being created.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | RECORD READ FROM THE RECOUP LOGGING TAPE HAS INVALID ID IGNORE=I ABORT RUN=A |
Explanation: An error occurred because a record ID is not valid on the RCP tape.
System Action: None.
User Response: Do one of the following:
000000000 | RECOUP GENERAL FILE RCD. NO. nnn IS INVALID |
Where:
Explanation: A directory record that is not valid was encountered while processing the recoup general file. The relative position of the record within the data set is referenced in the message.
System Action: The run continues but the error analysis will not be valid for addresses contained within that directory.
User Response: None.
See the TPF Database Reference for more information about offline pool maintenance.
000000000 | RECOUP LOGGING RECORD OUT OF SEQUENCE |
Explanation: The RCP items are either not in sequence or the gap is too big because of missing tapes.
System Action: The job continues to run normally because this message is only a warning.
User Response: Mount the correct RCP tapes in the correct order.
000000000 | RECOUP PHASE 2 HASH TABLE OVERFLOW -- RUN ABORTED |
Explanation: DYOPM uses a record ID hash table to generate recoup phase 2 output. An overflow resulted because the number of unique pool record ID and subsystem user ID combinations, which are kept in the record ID hash table, is greater than the number of entries allocated for the table.
System Action: None.
User Response: Do the following:
See the TPF Database Reference for more information about the size of the record ID hash table.
000000000 | RECOUP SELF-START OF ERRONEOUSLY AVAILABLE ADDRESSES |
Explanation: If erroneously available addresses are also on the tape, this message will indicate the end of lost addresses and the start of erroneously available addresses. The END OF RECOUP SELD message indicates the end of all recoup selective file dump records that appear on the real-time tape (RTL).
System Action: None.
User Response: None.
See the TPF Database Reference for more information about offline pool maintenance.
000000000 | REPLY 'Y' IF AN INPUT TAPE IS TO BE PROCESSED; ELSE REPLY 'N' |
Explanation: The program wants to know whether SYSIN should be opened. This message appears before processing the first input tape and again each time that End of File is raised for SYSIN.
System Action: None.
User Response: If there is a primary real-time tape (RTA) or RCP tape to be processed (or any more to be processed), then reply Y. Otherwise, reply N.
See the TPF Database Reference for more information about offline pool maintenance.
000000000 | REQUESTED PILOT SYSTEM NOT FOUND ON PILOT TAPE |
Explanation: The pilot system specified on RUNID was not found on the mounted pilot tape.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference
for more information.
Severity: 12
Explanation: The only two valid options for this parameter are RESTORE=YES or
RESTORE=NO.
System Action: None.
Severity: None.000000000 RESTORE PARAMETER INVALID
000000000 | RETRIEVAL ERROR OF A DUMP BLOCK |
Explanation: SERRC 0001E5 was issued unless a dump already given as the error is due to hardware. If the error was on the retrieval of a dump header block then a 3705-DUMP **** LOST DUE TO FILE RETRIEVAL ERROR message is sent to the originating terminal.
System Action: None.
User Response: None.
000000000 | RETURN CODE INVALID -- NOTIFY SUPPORT |
Explanation: The return code from the TPF linkage editor (LEDT) was not valid.
System Action: None.
User Response: Do the following:
If this problem continues, see your system support personnel for additional help.
See the TPF System Installation Support Reference
for more information about the loaders program.
Severity: 12
Explanation: A RIATA FINISH was already coded or was not preceded by a RIATA START.
System Action: None.
User Response: None.
Severity: 12
Explanation: A START or FINISH was already coded.
System Action: None.
User Response: None.000000000 RIATA "FINISH" OUT OF SEQUENCE
000000000 RIATA "START" OUT OF SEQUENCE
000000000 | RIGHT ('S MISSING ON CNTRL CARD/ ASSUMED |
Explanation: None.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about variable cross references.
000000000 | RUN ABORTED, RCP INPUT HAD INCORRECT TIME STAMP |
Explanation: The time stamps for all the RCP tapes are not the same. This discrepancy is probably because the RCP tapes are from different recoup runs.
System Action: The job is ended.
User Response: Do the following:
000000000 | SAL TABLE VERSION NOT GIVEN -- JOB ABORTED |
Explanation: When using the E-type loader, the version number of the system allocator (SAL) table (SALTBL) to be used was not given on the first input card. Alternatively, when using the auxiliary loader, the second card in the deck was not a SALVERS card.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | SALTBL/IPAT TIME STAMP DOES NOT MATCH, JOB ABORTED. |
Explanation: The TLDR offline program detects the time stamp on the offline system allocator (SAL) table (SALTBL) and the online IPAT that is to be loaded does not match.
System Action: The TLDR offline program is aborted with a return code of 12.
User Response: Correct the load deck to use the compatible SALTBL and IPAT version.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | SALTBL NOT FOUND ON LIBRARY |
Explanation: The system allocator (SAL) table (SALTBL) was not found on the library.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about loaders.
000000000 | SDMU CREATE CARD FOUND IN UPDATE RUN -- IGNORED |
Explanation: None.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference
for more information.
Severity: 4
Explanation: The SKLNG macros for the line for a particular LC control unit where not
specified on consecutive macros.
System Action: None.
User Response: Do the following:
Severity: 12
Explanation: The size coded for this parameter is not S (small), L (large), or 4
(4K).
System Action: None.
User Response: None.
Severity: 0
Explanation: No remote paths were specified in the preceding SKLNG macro.
System Action: The STRMG macro is ignored.
User Response: None.
Severity: 4
Explanation: None.
System Action: None.
User Response: Do the following:
Severity: 4
Explanation: None.
System Action: None.
User Response: Do the following:
000000000 SKLNG MACRO FOR LC CONTROL UNIT NOT CONSECUTIVE
000000000 "SIZE" IS INVALID FOR xxxxx PARAMETER
000000000 SLING MACRO NOT REQUIRED FOR LINE TYPE
000000000 SL PARAMETER IS OUT OF ALLOWABLE RANGE
000000000 SL PARAMETER NOT SPECIFIED FOR BSC LINE
000000000 | SOFTWARE ERROR IN FILE ADDRESS -- PROGRAM FOLLOWS |
Explanation: None.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | SOME PARS LIST ENTRIES NOT FOUND -- RUN WILL CONTINUE |
Explanation: The OPL list versions specified in the CC card contain programs that the MVS BLDL macro was unable to find. This will not hurt processing of the load.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | SORT UNSUCCESSFUL. LU ACTIVITY REPORT WILL NOT BE PRINTED |
Explanation: This message is printed in place of the requested logical unit activity report. File names starting with MA are those used by sort for this option.
System Action: None.
User Response: None.
See TPF Operations for more information about system performance.
000000000 | SORT UNSUCCESSFUL. LU MESSAGE STREAM NOT PRINTED. |
Explanation: This message is printed in place of the requested logical unit message stream report. File names starting with MT are those used by sort for this option.
System Action: None.
User Response: None.
See TPF Operations for more information about system performance.
000000000 | SORT UNSUCCESSFUL. TERMINAL ACTIVITY -- REPORT WILL NOT BE PRINTED |
Explanation: This message is printed in place of the requested terminal activity reports. File names starting with MT are those used by sort for this option.
System Action: None.
User Response: None.
See TPF Operations for more information about system performance.
000000000 | SORT UNSUCCESSFUL. MESSAGE STREAM NOT PRINTED. |
Explanation: This message is printed in place of the requested message stream report. File names starting with MS are those used by sort for this option.
System Action: None.
User Response: None.
See TPF Operations for more information about system performance.
000000000 | SORT UNSUCCESSFUL. OUTPUT MESSAGE DATA NOT INCLUDED IN ACTION CODE SUMMARIES |
Explanation: This message, applicable only for continuous mode reductions, is printed after the last message report. The action code summaries will still be reported. However, the two columns of output message data will be omitted. File names starting with MA are those used by sort for this option.
System Action: None.
User Response: None.
See TPF Operations for more information about system performance.
000000000 | SORT VALUE NOT SIP TYP GLB |
Explanation: The sort parameter contained an unknown keyword. BPR0 is designed to process recoup selective file dump (SFD) records from the RTL tape. The start of these records is indicated on the RTL tape by the START OF RECOUP SELD-LOST ADDRESSES FIRST message.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference
for more information about variable cross referencing. See the TPF Database Reference for more information about offline
pool maintenance.
Severity: 4
Explanation: The STATUS operand specified in the SLING macro was not one of the
following:
System Action: None.
User Response: If the default is not acceptable, correct the input and rerun Phase 1 or patch
the generated SCK record at the LCFnn tag.000000000 STATUS OPERAND INVALID - DEFAULTED TO STATUS DOWN
000000000 | STCC GLOBAL LOAD MODE INVALID FOR PHASE I OR III, NO DEFAULTS WILL BE TAKEN |
Explanation: The mode of the global core load must be specified as a single numeral (1 through 9).
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | STV CURRENTLY ACTIVE |
Explanation: A program test vehicle (PTV) start request (system test vehicle (STV) mode) was entered. PTV was 20.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | STV NOT ACTIVE |
Explanation: A request for the program test vehicle (PTV) to perform a function was entered.
System Action: PTV was not started (system test vehicle (STV) mode).
User Response: Do the following:
See the TPF Program Development Support Reference for more information.
000000000 | SUFFIX GREATER THAN 6 CHARACTERS |
Explanation: A suffix was provided through a control card that exceeds six characters.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the multiple assembly and compilation program.
000000000 | SUFFIX + MEMBER NAME GREATER THAN 8 CHAR |
Explanation: When the suffix was added to the input library member name the resultant name exceeds eight characters.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the multiple assembly and compilation program.
000000000 | SYSID MUST BE FIRST CARD -- JOB ABORTED |
Explanation: The SYSID card is not the first card in the load deck.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | SYSTEM KEYPTS PREVIOUSLY LOADED -- CARD IGNORED |
Explanation: More than one load keypoint card was encountered.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference
for more information about the loaders program.
Severity: 8
Explanation: This message follows any of the preceding severe error messages.
System Action: None.
User Response: Do the following:
000000000 TABLE GENERATION SUPPRESSED
000000000 | TAPE OUT OF SEQUENCE -- RUN DISCONTINUED |
Explanation: The current input tape to the STC loader is not in the expected sequence. The offending tape should be sorted or recreated and STC rerun completely.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | TAPE WRITE ERROR |
Explanation: The dump currently being processed is deleted from the CDM tape contents display, the tape switch is activated internally, and the dump is reprocessed as the first on the new CDM tape.
System Action: None.
User Response: None.
000000000 | TEXT SIZE OF PGM xxxxxx TOO BIG -- NOTIFY SUPPORT. |
Where:
Explanation: The size of the program referenced in the message is greater than the build area allotted.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference
for more information about loaders.
Severity: 8
Explanation: The PATH parameter in the SKLNG macro call is not valid or omitted.
System Action: None.
User Response: Do the following:
000000000 THERE IS NO PATH IN SCK GENERATION
000000000 | THE RTC TAPE DOES NOT HAVE A xx RECORD FOR THIS FILE |
Explanation: The RTC tape is missing all or part of the required data collection record referenced in the message. The tape may not be a data collection tape. If it is, the LABEL field in the RTC file definition card, which indicates which file on the tape is being read, may need to be changed for this particular reel before the job can be rerun.
System Action: None.
User Response: None.
See TPF Operations for more information about system performance.
000000000 | THE RTC TAPE DOES NOT HAVE A DB RECORD FOR THIS FILE |
Explanation: If the first or second record on the RTC tape is not a DB record this message is printed and the reduction run is stopped.
System Action: None.
User Response: None.
000000000 | THIS FIELD IS TOO LONG -- REST OF CARD IGNORED |
Explanation: One of the parameters on an ENTER card was too long.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | THIS FIELD TOO SHORT -- REST OF CARD IGNORED |
Explanation: The record ID is less than 1.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference
for more information.
Severity: 12
Explanation: All three subparameters -- size, pool, and device -- were not coded
for this parameter.
System Action: None.
User Response: None.000000000 THREE ENTRIES NOT SPECIFIED IN xxxx PARAMETER
000000000 | TIME INTERVAL NOT S OR M IN RUNID, SET TO S |
Explanation: The RUNID does not specify whether the maximum time parameter is for a phase I test unit is to be measured in seconds or minutes. The default will be seconds.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | TIME VALUE GT 99 IN RUNID, SET TO BLANKS, PTV WILL DEFAULT TO 30S FOR PHASE I |
Explanation: A maximum run time that is not valid was specified on a phase I RUNID.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | TIME VALUE LT 01 IN RUNID, SET TO BLANKS -- PTV WILL DEFAULT TO 30S FOR PHASE I |
Explanation: A maximum run time that is not valid was specified on a phase I RUNID.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | TOO MANY KEYPOINTS ARE BEING LOADED |
Explanation: More than the maximum number of unique keypoints are being loaded.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about loaders.
000000000 | TOO MANY NAME TABLE ENTRIES -- INCREASE PGMNBR -- JOB ABORTED |
Explanation: The number of name table entries for the load deck exceeds the default or the number specified on the PGMNBR parameter.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | TOO MANY RECORDS HAVE BEEN GENERATED AND CANNOT FIT IN CORE ADDRESS. THIS PART OF JOB HAS BEEN ABORTED AND NOT RECORDS OUTPUTTED |
Explanation: During an SDMU run, the main storage table can handle only 100 new records at a time. If more than 100 records are given, SDMU cannot handle them.
System Action: No new library is created because of this condition.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | TOO MANY REP CARDS -- INCREASE MAX NUMBER OF PATCHES. |
Explanation: The number of REP cards in the load deck exceeds the default or the number specified on the PTCHNBR parameter.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | TOO MANY UNRESOLVED VCONS -- JOB ABORTED |
Explanation: The unresolved V-Constants (V-Cons) Table (UNRESAD) is too small to maintain all of the unresolved V-con information for this load deck.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | TOTAL NUMBER OF GENERATED MAP FIELDS NOT EQUAL TO THE NUMBER CODED IN MAXFLDS MAP--xxxx--TERMINATED |
Where:
Explanation: This is a type E error. This error occurs when you code the MAXFLDS parameter but the total number of input fields for the map specified does not equal that number coded.
System Action: The user map referenced in the message is not generated.
User Response: None.
See the TPF Database Reference for more information about mapping support installation.
000000000 | TRAP ADDRESS NOT WITHIN DRIVER -- TRPMT yyyyyy |
Where:
Explanation: The P2 parameter has a displacement greater than 1055.
System Action: Control is transferred to the next sequential instruction in the drive program.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | TUT NOT RESERVED |
Explanation: A start test (system test vehicle (STV) mode) ZSTVS START RUNID command was entered but the test unit tape was not reserved in the TPF system. The message and the card involved are printed on the same line.
System Action: None.
User Response: Do the following:
See the TPF Program Development Support Reference for more information.
000000000 | UNABLE |
Explanation: This message is issued by selective file dump (SFD) processing while forward chaining with an S type file address format record. The file address compute program (FACE) returns a code that is not valid.
System Action: The entry is exited.
User Response: Review the system error dump to determine why FACE returned a return code that is not valid.
See the TPF Program Development Support Reference for more information.
000000000 | UNABLE -- ANOTHER IS ACTIVE |
Explanation: An attempt to start a second selective file dump (SFT) was tried before a prior trace ended.
System Action: The entry is exited.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | UNABLE -- CHECK MESSAGE FORMAT |
Explanation: There is an error in the command format.
System Action: The entry is exited.
User Response: Do the following:
See the TPF Program Development Support Reference for more information.
000000000 | UNABLE -- INVALID ORDINAL RANGE |
Explanation: The user specified a negative ordinal range with an N or S type file address format.
System Action: The entry is exited.
User Response: Enter the command again and specify the proper ordinal range.
See the TPF Program Development Support Reference for more information.
000000000 | UNABLE -- INVALID RECORD TYPE |
Explanation: The record type is not recognized by the file address compute program (FACE) and, therefore, is not valid for the user.
System Action: The entry is exited.
User Response: Do the following:
See the TPF Program Development Support Reference for more information.
000000000 | UNABLE -- NUMBER OF RECORDS REQUESTED EXCEEDS MAXIMUM |
Explanation: The number of records may not exceed 82 for A type address format and 420 for the N or S type address format. The number of records in the input message exceeded the maximum.
System Action: The entry is exited.
User Response: Enter the command again and specify the valid number of records.
See the TPF Program Development Support Reference for more information.
000000000 | UNABLE -- ORD RANGE EXCEEDED FOR SPECIFIED REC TYPE |
Explanation: The specified ordinal range is greater than that available for the record type.
System Action: The entry is exited.
User Response: Enter the command again and specify the valid ordinal range for the record type.
See the TPF Program Development Support Reference for more information.
000000000 | UNABLE -- SFT NOW INACTIVE |
Explanation: The selective file trace (SFT) halt message is issued when SFT is not active.
System Action: The entry is exited.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | UNABLE TO IDENTIFY INPUT FOR OBJECT MODULE |
Explanation: An object card that is not valid was encountered.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | UNABLE TO PROCESS, NOT FILED -- SEQ # DEVICE TYPE |
Explanation: There was a retrieval error on an existing file record.
System Action: None.
User Response: Do the following:
See the TPF Database Reference for more information about mapping support installation.
000000000 | UNABLE TO READ POINTER TO CTKX |
Explanation: An error occurred because the TPF system is unable to read the pointer to CTKX.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about loaders.
000000000 | UNABLE TO RESOLVE VCONS -- PROGRAM CALL IGNORED |
Explanation: The called program used V-constants (V-cons) that could not be resolved. The allocator table must be updated.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | UNABLE TO RETRIEVE THESE RECORDS: xxxxxxxx Hardware Error yyyyyyyy Invalid File Address |
Where:
Explanation: The file retrieval errors occurred because of a hardware error or a file address that is not valid. The message contains a series of sub messages containing the file address followed by the reason these records are not able to be retrieved.
System Action: Selective file dump (SFDT) processing is continued to completion, dumping the records that can be retrieved.
User Response: Do the following:
See the TPF Program Development Support Reference for more information.
000000000 | UNABLE TO WRITE POINTER TO CTKX |
Explanation: An error occurred because the system is unable to writer the pointer to CTKX.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about loaders.
000000000 | UNABLE -- USERID DID NOT INITIATE SFT |
Explanation: The user ID trying to halt selective file trace (SFT) does not match the user ID that initiated SFT.
System Action: The entry is exited.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | UNDEFINED CARD TYPE OR SEQ ERR. CD. IGNORED |
Explanation: This card is unidentifiable by SDMU.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | UNDEFINED CARD TYPE OR SEQUENCE ERROR FOLLOWING CARD IGNORED |
Explanation: None.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
000000000 | UNKNOWN CARDS FOUND..SEE FULL LOAD LIST |
Explanation: Extraneous cards were found in the load deck.
System Action: None.
User Response: Do the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | UNKNOWN ERROR ON FIND - NOTIFY SUPPORT |
Explanation: FIND returned an unexpected return code.
System Action: None.
User Response: Run the job again. If the error continues, see your system support personnel for additional help.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | UNUSUAL CONDITION ON DISK -- ENTRY IGNORED |
Explanation: Either the record is not available on disk or the disk was not loaded properly.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference
for more information.
Severity: 12
Explanation: The only two valid options for this parameter are UEXIT=YES or
UEXIT=NO.
System Action: None.
User Response: None.000000000 USER EXIT PARAMETER INVALID
000000000 | VALUE OF KEYWORD MISSING |
Explanation: One of the following keywords was found without any value indicated:
System Action: None.
User Response: None.
See the TPF System Installation Support Reference
for more information about the multiple assembly and compilation
program.
Severity: 12
Explanation: The only valid options for this parameter are VFAF=DELAY, VFAF=IMMED, and
VFAF=NO.
System Action: None.
User Response: None.
Severity: 12
Explanation: The VFAF=SIMMED or VFAF=SDELAY parameters that were coded on the RIATA
macro indicate virtual file access (VFA) synchronization was requested.
VFA synchronization is not compatible with processor locking and requires
control unit locking (LOCKF=DASD).
System Action: None.
User Response: None.
Severity: 12
Explanation: The only valid options for this parameter are VFAP=DELAY, VFAP=IMMED, and
VFAP=NO.
System Action: None.
User Response: None.
Severity: 12
Explanation: The VFAP=SIMMED or VFAP=SDELAY parameters that were coded on the RIATA
macro indicate virtual file access (VFA) synchronization was requested.
VFA synchronization is not compatible with processor locking and requires
control unit locking (LOCKP=DASD).
System Action: None.
User Response: None.000000000 VFA FIXED PARAMETER INVALID
000000000 VFAF SYNC AND LOCKF=PROC ARE INCOMPATIBLE
000000000 VFA POOL PARAMETER INVALID
000000000 VFAP SYNC AND LOCKP=PROC ARE INCOMPATIBLE
000000000 | WARNING -- nnnnvv WAS LOADED WITH UNRESOLVED XTRNS |
Where:
Explanation: The program name and the unresolved external references (up to 20) referenced in the message will be listed below the error message.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | WARNING -- CSECT TBL > ALLOC LNG -- NO CP PATCH |
Explanation: The size of the CP CSECT names module (CPLKMP) is too small to contain the names of all the CP CSECTs.
System Action: None.
User Response: No CP CSECT module may be patched. This problem can be corrected by correcting the CPLKMP module.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | WARNING - DUPLICATE IATA/TIADDR ENCOUNTERED - CHECK LISTING |
Explanation: Duplicate node names must be resolved to allow correct system operation. Every node name in a TPF SNA network must be unique.
A few messages appear on both the macro listing and the operator console. These messages indicate irrecoverable conditions and are followed by an abort message.
System Action: None.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation program (OSTG) error messages.
000000000 | WARNING - ELDR CLEAR CARD NOT INCLUDED, ELDR STRUCTURES REMAIN UNCHANGED |
Explanation: The ELDR clear card is not included in the TLDR load deck. All E-type loader structures remain unchanged when the the TLDR output data set is loaded.
System Action: None.
User Response: Add the loader load ELDR clear card to the load deck if the E-type loader structures need to be cleared.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | WARNING -- G.FILE CONFIG CARD NOT SUPPORTED, IGNORED |
Explanation: The G.FILE CONFIG card is not required in the TLDR load deck.
System Action: The card is ignored.
User Response: Remove the G.FILE CONFIG card from the TLDR load deck.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | WARNING GF MISSING CP ACPL CR PROG FCTB, RIAT SEGMENTS |
Explanation: The general file is missing one or more of the following:
System Action: None.
User Response: Load the general file again with the missing segments.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | WARNING GF MISSING KEYPT xxxx |
Where:
Explanation: For the basic subsystem (BSS), the general file must be reloaded with the missing keypoint. For a non-BSS subsystem, the general file must be reloaded with the missing keypoint if the keypoint is defined as a subsystem-unique kyepoint. The subsystem-unique keypoints are defined in CTKX (see CX0IN1).
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | WARNING -- IMAGE CLEAR CARD NOT SUPPORTED, IGNORED |
Explanation: The image clear card is not supported by TLDR.
System Action: The card is ignored.
User Response: Remove the image clear card from the TLDR load deck.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | WARNING NO LDT CARD FOUND |
Explanation: There was no LDT card in the load deck. Load may not be complete.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | WARNING -- PGM HAS UNRESOLVED V-CONS |
Explanation: This program contains external references and enters to other programs that are not contained in the system allocator (SAL) table.
System Action: None.
User Response: Do one of the following:
See the TPF System Installation Support Reference for more information about the loaders program.
000000000 | WARNING--PROG-MOD-BASE CLEAR CARD INPUT, PROGRAM MODULE BASE WILL BE CLEARED |
Explanation: The offline loader set an indicator that will cause the #XPRGn directory to be initialized when the online portion of this load is run.
System Action: None.
User Response: Do one of the following:
See the TPF System Installation Support Reference for more information about the LOADER PROG-MOD-BASE CLEAR card.
000000000 | WARNING -- REP CARD NOT SUPPORTED FOR PROGRAM MODULE |
Explanation: The offline loader encountered a REP card for an ISO-C program.
System Action: The REP card is ignored and processing continues.
User Response: Do the following:
000000000 | WCC NOT CODED CORRECTLY, MAP--xxxx--TERMINATED |
Where:
Explanation: This is a type E error. The user map referenced in the message with the DPANL WCC operand options was not coded according to specifications or the option is misspelled.
System Action: The map is not created.
User Response: Do the following:
See the TPF Database Reference for more information about mapping support installation.
000000000 | WRITE TAPEMARK ERROR |
Explanation: The tape switch is activated immediately.
System Action: None.
User Response: None.
See the TPF Database Reference for more information about the 3705 communications controller.
000000000 | WRONG VERSION NO.--CARD IGNORED |
Explanation: A REP card for ICDF, ACPL, FCTB, IPLB, SIGT, or RIAT was found but the version on the REP card did not match the version on the loader load card.
System Action: None.
User Response: None.
See the TPF System Installation Support Reference
for more information about the loaders program.
Severity: 4
Explanation: The BCODE subparameters are not a valid combination. If YRCPL is
specified, then EBCDIC and YTRAN must be specified or defaulted to.
System Action: None.
User Response: Do the following:
000000000 YRCPL IS SPECIFIED BUT EBCDIC AND/OR YTRAN WERE NOT SPECIFIED
OR DEFAULTED
000000000 | ZSTOP UNABLE RTT INITIATED BY CRAS xxxxxxxx |
Where:
Explanation: The ZSTOP command was not entered from the same computer room agent set (CRAS) console.
System Action: The entry is exited.
User Response: Enter the ZSTOP command from the issuer of the start message.
See the TPF Program Development Support Reference for more information about the real-time trace (RTT) utility. See TPF Operations for more information about the ZSTOP command.
000000000 | ZSTOP UNABLE USER--ID DID NOT INITIATE RTT |
Explanation: The subsystem ID of the user did not match that of the real-time tape (RTT) initiator.
System Action: The entry is exited.
User Response: None.
See the TPF Program Development Support Reference for more information about the real-time trace (RTT) utility. See TPF Operations for more information about the RTT commands.
000000000 | 1055-BYTE AREA TABLE FULL FOLLOWING CARD IGNORED |
Explanation: The table in the system test compiler (STC) loader used to accumulate 1055 or 381 byte addresses as they are read in is full.
System Action: None.
User Response: None.
See the TPF Program Development Support Reference for more information.
*E101* | NODENAME MISSING |
Explanation: The symbolic name on an RSC input definition statement is not specified.
System Action: Processing is continued with the next input definition statement.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E103* | INVALID CONTINUATION.STMNT FLUSHED. |
Explanation: A continuation card that is not valid was detected.
System Action: Processing is continued with the next input definition statement.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E104* | OPCODE MISSING ON 1ST CARD.STMNT FLUSHED. |
Explanation: The offline ACF/SNA table generation (OSTG) program requires that the OPCODE for an input definition statement be on the first or only card.
System Action: Processing is continued with the next input definition statement.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the OSTG program.
*E105* | SYNTAX ERROR |
Explanation: The input definition statement could not be parsed correctly.
System Action: Processing is continued with the next input definition statement.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E110* | STATEMENT OUT OF LOGICAL SEQUENCE |
Explanation: The input definition statement is not in logical sequence.
System Action: Processing is continued with the next input definition statement.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E112* | MAXIMUM STATEMENT LENGTH EXCEEDED. STMNT FLUSHED. |
Explanation: While reading an input definition statement, the buffer used to concatenate the parameters became full. This error is normally caused by incorrect continuation cards.
System Action: Processing is continued with the next input definition statement.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E113* | OPCODE UNDEFINED. |
Explanation: The OPCODE of an input definition statement is not known to the offline ACF/SNA table generation (OSTG) program.
System Action: Processing is continued with the next input definition statement.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the OSTG program.
*E114* | NAME GREATER THAN 8. STMNT FLUSHED. |
Explanation: The symbolic name on an input definition statement exceeded 8 characters in length.
System Action: Processing is continued with the next input definition statement.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E115* | OPCODE INVALID - NO PU_5 SUPPORT GENERATED |
Explanation: A CDRM, NCP, or CTC input definition statement was found but PU_5 support was not requested for this TPF system.
System Action: Processing is continued with the next input definition statement.
User Response: Do one of the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E116* | LOCAL CP ALREADY DEFINED |
Explanation: In the OSTG deck a second ANTNME statement has been found with the LOCP keyword. Only 1 local APPN control point (CP) can be defined to the TPF system.
System Action: The entry to define a second local APPN CP is ignored by OSTG.
User Response: In SIP check the MSGRTA macros (which produce the ANTNME statements) to ensure that only 1 local APPN CP is defined in your OSTG deck.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program. See TPF System Generation for more information about the MSGRTA macro.
*E201* | xxxxxxxx VALUE INVALID |
Where:
Explanation: The value specified for the parameter is not valid.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E202* | xxxxxxxx IS AN INVALID USAGE OF RESERVED NODENAME |
Where:
Explanation: A statement contains a TPF reserved node name whose usage is not valid.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E203* | SYMBOL NAME AND LUTYPE ARE INCOMPATIBLE |
Explanation: A TPF reserved name specified in the RSC input definition statement is not valid with the value specified for the LUTYPE parameter.
The value of the LUTYPE parameter must be:
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E204* | xxxxxxxx INVALID OR LOWER CASE CHARACTER IS USED |
Where:
Explanation: The node name specified contains one of the following:
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E205* | SUBAREA VALUE PREVIOUSLY DEFINED |
Explanation: The subarea address specified by the SUBAREA parameter in the NCP and CTC statements is a duplicate of a subarea address specified on an earlier SUBAREA parameter.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E206* | VRILTO GREATER THAN MAXIMUM ALLOWED |
Explanation: The virtual route input list time-out (VRILTO) value specified by the VRILTO parameter is larger than the maximum value allowed. The maximum value allowed is 255.
System Action: Processing is continued with the value defaulted to zero (0).
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E207* | WINDOW SIZE GREATER THAN MAXIMUM OR LESS THAN ONE |
Explanation: The window size specified is greater than 255.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E208* | SDA GREATER THAN MAXIMUM ALLOWED |
Explanation: The symbolic device address (SDA) defined on the TG2SDA parameter is not valid. A valid range for the SDA is from X'0001' to X'7FFF'.
System Action: Processing is continued.
User Response: Do not code the TG2SDA parameter on the CTC statement because this parameter is no longer supported.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E209* | VRTO GREATER THAN MAXIMUM ALLOWED |
Explanation: The virtual route time-out (VRTO) value specified by the VRTO parameter is larger than the maximum allowed. The maximum allowed is 65 535.
System Action: Processing is continued with the value defaulted to 0.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E210* | SUBAREA VALUE NOT CDRM|SSCP SUBAREA |
Explanation: The subarea address defined on the CTC statement was not defined as a host subarea.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E211* | MAXIMUM NAMES ALLOWED FOR ANT EXCEEDED |
Explanation: The maximum of 255 application program names for the ANT deck was exceeded.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program and the ANT deck. See TPF System Generation for more information about system generation and the MSGRTA statements that are used to create the ANT deck.
*E213* | RECVRY AND PSV KEYWORDS ARE MUTUALLY EXCLUSIVE |
Explanation: Both the RECVRY and PSV parameters were specified in the RSC input definition statement. Only one of these parameters can be specified in the RSC input definition statement.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E214* | SUBAREA VALUE NOT PREVIOUSLY DEFINED IN CDRM STATEMENT |
Explanation: The subarea address defined in the CTC statement was not defined previously in the CDRM statement. A link to an undefined subarea is not valid.
System Action: Processing is continued.
User Response: Do one of the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E215* | LEID LENGTH ERROR |
Explanation: The logical endpoint identifier (LEID) length is one of the following:
System Action: Processing is continued.
User Response: Ensure the correct length is specified for LEID.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E216* | IATA AND LEID KEYWORDS ARE MUTUALLY EXCLUSIVE |
Explanation: The interchange address/terminal address (IATA) and the logical endpoint identifier (LEID) parameters were specified in the RSC input definition statement. Only one of these parameters can be specified in the RSC input definition statement.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E220* | MAX NUMBER OF CTC-LINKS TO THIS SUBAREA EXCEEDED |
Explanation: A maximum of 2 CTC links can be defined for a subarea.
System Action: Processing is continued.
User Response: Ensure that only 2 CTC links are defined for the subarea.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E227* | LU INCOMPATIBLE WITH CCTYPE VALUE |
Explanation: The values specified for the LUTYPE and CCTYPE parameters are not compatible with each other.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E229* | CCTYPE REQUIRED FOR THIS RSC |
Explanation: The CCTYPE parameter is required for this type of RSC definition.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E230* | IATA NOT VALID ON RSCSET STATEMENT |
Explanation: The IATA parameter is not valid in the RSCSET statement because each interchange address/terminal address (IATA) defined must be unique.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E231* | LEID NOT VALID ON RSCSET STATEMENT |
Explanation: The LEID parameter is not valid in the RSCSET statement.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E232* | LUMOD FOR LUTYPE NOT SUPPORTED |
Explanation: The model number specified for the logical unit (LU) type is not supported.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E233* | SCSBUF FOR LUTYPE NOT SUPPORTED |
Explanation: The buffer size specified for the logical unit (LU) type is not supported.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E234* | USER SPECIFIED PSV NAME EXCEEDS 96 ENTRIES |
Explanation: More than 96 user-defined process selection vector (PSV) names were specified in the RSC input definition statement. A maximum of 96 user-defined PSV names can be specified in an RSC input definition statement.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E235* | LEID DOES NOT EXCEED THE HIGHEST SYMBOLIC LINE NUMBER |
Explanation: The logical endpoint identifier (LEID) must be greater than the highest symbolic line number defined in the TPF system.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E250* | IBM RESERVED PSV NAME EXCEEDS 32 ENTRIES |
Explanation: A maximum of 32 IBM-reserved process section vector (PSV) names are allowed in the RSC input definition statement. The number of PSV names specified exceeds this maximum.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E266* | TPF APPL NAME MUST BE 4 CHARACTERS |
Explanation: An application name with secondary logical units (SLUs) defined must be 4 characters long.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program and the ANT deck. See TPF System Generation for more information about system generation and the MSGRTA statements that are used to create the ANT deck.
*E280* | CDRMNAME INCORRECT FOR TPF CPU |
Explanation: The CDRM name specified for a TPF CPU must be TPFc where c is the TPF CPU ID.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E281* | SUBAREA FOR GENNING TPF HOST INCORRECT |
Explanation: The subarea specified for this TPF host system is inconsistent with a previous subarea definition.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E290* | xxxxxxxx INVALID KEYWORD THIS STMNT |
Where:
Explanation: The parameter referenced in the message is not valid for this type of input definition statement.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E291* | BOTH CLU AND QN KEYWORDS ARE REQUIRED IF EITHER IS SPECIFIED |
Explanation: Either the CLU parameter or the QN parameter was specified in the CTC statement, but not both.
If TPF/APPC sessions with VTAM application programs will be activated across a channel-to-channel (CTC) connection, both a control point logical unit (CLU) and a qualifier number (QN) are required. The CLU is needed for a control session with Logon Manager and the QN is needed with the CPU ID to create an alias name for the TPF/APPC logical unit (LU).
System Action: Processing is continued; however, the CTC definition is ignored and the OSTG run is unsuccessful.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E292* | xxxxxxxx REQUIRED KEYWORD MISSING |
Where:
Explanation: The parameter referred to in the message is required for this type of input definition statement.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E293* | ALSNAME MISSING |
Explanation: The symbolic name was not specified on the ALS input definition statement. Each ALS name must be unique.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E294* | NCPNAME MISSING |
Explanation: The symbolic name was not specified on the NCP input definition statement. Each NCP name must be unique.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E295* | CDRMNAME MISSING |
Explanation: The symbolic name was not specified on the CDRM input definition statement. Each CDRM name must be unique.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E296* | CTC NAME MISSING |
Explanation: The symbolic name was not specified in the CTC input definition statement. Every CTC link must have a unique name.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E800* | DUPLICATE NODENAME(S) FOUND - CHECK LISTING |
Explanation: Duplicate node names were found after processing all the input definition statements.
Every resource defined to the TPF system must have a unique name with NET IDs. The OSTG listing identifies the duplicate names found.
System Action: The OSTG run is canceled.
User Response: do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*E801* | DUPLICATE LEID(S) FOUND, CHECK LISTING |
Explanation: Duplicate logical endpoint identifiers (LEIDs) were found after processing all the input definition statements.
Each LEID must be unique to the TPF system. The OSTG listing identifies the duplicate LEIDs found.
System Action: The OSTG run is canceled.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I401* | 3614 SPECIFIED, VALUES IMPOSED ARE |
Explanation: LUTYPE=3614 was specified in the RSC input definition statement. As a result, the offline ACF/SNA table generation (OSTG) program imposes values for some of the other parameters.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values override all other specifications for the parameters. Any additional parameters that were specified, but are not relevant to this RSC type, are ignored.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the OSTG program.
*I403* | BATCH SPECIFIED, VALUES IMPOSED ARE |
Explanation: LUTYPE=BATCH was specified in the RSC input definition statement. As a result, the offline ACF/SNA table generation (OSTG) program imposes values for some of the other parameters.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values override all other specifications for the parameters. Any additional parameters that were specified, but that are not relevant to this RSC type, are ignored.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the OSTG program.
*I404* | 3271 SPECIFIED, VALUES IMPOSED ARE |
Explanation: CCTYPE=3271 was specified in the RSC input definition statement. As a result, the offline ACF/SNA table generation (OSTG) program imposes values for some of the other parameters.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values override all other specifications for the parameters. Any additional parameters that were specified, but are not relevant to this RSC type, are ignored.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the OSTG program.
*I405* | 3274/3276 SPECIFIED, VALUES IMPOSED ARE |
Explanation: CCTYPE=3274 or CCTYPE=3276 was specified in the RSC input definition statement. As a result, the offline ACF/SNA table generation (OSTG) program imposes values for some of the other parameters.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values override all other specifications for the parameters. Any additional parameters that were specified, but are not relevant to this RSC type, are ignored.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the OSTG program.
*I406* | 360X SPECIFIED, VALUES IMPOSED ARE |
Explanation: LUTYPE=360X was specified in the RSC input definition statement. As a result, the offline ACF/SNA table generation (OSTG) program imposes values for some of the other parameters.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values override all other specifications for the parameters. Any additional parameters that were specified, but are not relevant to this RSC type, are ignored.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the OSTG program.
*I453* | RECVRY=YES |
Explanation: The resource being defined by this input definition statement will be generated with the RECVRY=YES value imposed regardless of the defaults or the explicit specification of any other option for this parameter.
This message is preceded by another severity I message based on the logical unit (LU) type.
System Action: The imposed values are used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I454* | RECVRY=NO |
Explanation: The resource being defined by this input definition statement will be generated with the RECVRY=NO valued imposed regardless of the defaults or the explicit specification of any other option for this parameter.
This message is preceded by another severity I message based on the logical unit (LU) type.
System Action: The imposed values are used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I455* | THREAD=SINGLE |
Explanation: The resource being defined by this input definition statement will be generated with the THREAD=SINGLE value imposed regardless of the defaults or explicit specification of any other option for this parameter.
This message is preceded by another severity I message based on the logical unit (LU) type.
System Action: The imposed value is used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I456* | THREAD=MULTI |
Explanation: The resource being defined by this input definition statement will be generated with the THREAD=MULTI value imposed regardless of defaults or explicit specification or any other option for this parameter.
This message is preceded by another severity I message based on the logical unit (LU) type.
System Action: The imposed value is used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I461* | DEFAULT VALUE OF 0 USED ON VRTO |
Explanation: The resource being defined by this input definition statement will be generated with the value of the VRTO parameter set to 0.
System Action: A 0 value is used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I462* | DEFAULT VALUE OF 0 USED ON VRILTO |
Explanation: The resource being defined by this input definition statement is generated with the value of the VRILTO parameter set to 0.
System Action: A 0 value is used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I463* | CHAIN=NO |
Explanation: The CHAIN=YES value is allowed only for multichannel links and virtual circuits. The CHAIN=NO value is imposed for all other X.25 resources.
System Action: The imposed values are used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I478* | LU62 SPECIFIED, VALUES IMPOSED ARE |
Explanation: The resource being defined by this input definition statement will be generated as an LU 6.2 resource because the value of the LUTYPE parameter is L6PLU, L6SLU, or REMCP. The values for some other parameters will be imposed regardless of their defaults or explicit specification of those parameters.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values override all other specifications for the parameters. Any additional parameters that were specified, but are not relevant to this RSC type, are ignored.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the OSTG program.
*I480* | LUTYPE=3277 |
Explanation: The resource being defined by this input definition statement will be generated with the LUTYPE=3277 value imposed regardless of the defaults or explicit specification of any other option for this parameter.
This message is preceded by another severity I message based on CCTYPE.
System Action: The imposed values are used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I481* | LUTYPE=3284/86/88 |
Explanation: The resource being defined by this input definition statement will be generated with the LUTYPE=3284/3286/3288 value imposed regardless of the defaults or explicit specification of any other option for this keyword.
This message is preceded by another severity I message based on CCTYPE.
System Action: The imposed values are used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I485* | NO PSV ENTRY |
Explanation: The resource being defined by this input statement will be generated with no process selection vector (PSV) entry, regardless of the default or explicit specification of any other option for this parameter.
System Action: No PSV name is used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I488* | LUMOD=2 |
Explanation: The resource being defined by this input definition statement will be generated with the LUMOD=2 value imposed regardless of the defaults or explicit specification of any other option for this parameter.
This message is preceded by another severity I message based on LUTYPE/CCTYPE.
System Action: The imposed values are used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I489* | AX001 SPECIFIED, VALUES IMPOSED ARE |
Explanation: The resource being defined by this input definition statement will be generated with the LUTYPE=AX0001 value imposed regardless of the defaults or explicit specification of any other option for this parameter.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values are used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I490* | AX002 SPECIFIED, VALUES IMPOSED ARE |
Explanation: The resource being defined by this input definition statement will be generated with the LUTYPE=AX002 value imposed regardless of the defaults or explicit specification of any other option for this parameter.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values are used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I491* | MCHLU SPECIFIED, VALUES IMPOSED ARE |
Explanation: The resource being defined by this input definition statement will be generated with the LUTYPE=MCHLU value imposed regardless of the defaults or explicit specification of any other option for this parameter.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values are used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I492* | VCLU SPECIFIED, VALUES IMPOSED ARE |
Explanation: The resource being defined by this input definition statement will be generated with the LUTYPE=VCLU value imposed regardless of the defaults or explicit specification of any other option for this parameter.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values are used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I493* | FMMR SPECIFIED, VALUES IMPOSED ARE |
Explanation: The resource being defined by this input definition statement will be generated with the LUTYPE=FMMR value imposed regardless of the defaults or explicit specification of any other option for this parameter.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values are used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I494* | NEF SPECIFIED, VALUES IMPOSED ARE |
Explanation: The resource being defined by this input definition statement will be generated with the LUTYPE=NEF value imposed regardless of the defaults or explicit specification of any other option for this parameter.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values are used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I495* | FTPI SPECIFIED, VALUES IMPOSED ARE |
Explanation: The resource being defined by this input definition statement will be generated with the LUTYPE=FTPI value imposed regardless of the defaults or explicit specification of any other option for this parameter.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values are used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I496* | XALCI SPECIFIED, VALUES IMPOSED ARE |
Explanation: The resource being defined by this input definition statement will be generated with the LUTYPE=XALCI value imposed regardless of the defaults or explicit specification of any other option for this parameter.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values are used when creating the RRT entry for this resource.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I703* | THE FOLLOWING APPLICATIONS GENERATED: |
Explanation: Based on the CPU IDs detected on the ANTDEF, ANTNME, and CDRM input definition statements, certain system application logical units (LUs) are generated by the offline ACF/SNA table generation (OSTG) program.
System Action: The names of the system application LUs generated automatically by the OSTG program are listed immediately following this message.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the OSTG program.
*I705* | THIS CPU IS PART OF SDPS GENERATION |
Explanation: This message identifies the host CPU ID as a TPF host system that is part of the loosely coupled complex.
System Action: None.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*I901* | NO STATEMENTS FLAGGED |
Explanation: This message is printed on the OSTG report file if no severity S message or severity E message was issued by the offline ACF/SNA table generation (OSTG) program. A similar message is sent to the operator.
System Action: None.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the OSTG program.
*I902* | xxxxxxxx STATEMENTS FLAGGED |
Where:
Explanation: This message shows the count of the severity S messages and the severity E messages that were issued by the offline ACF/SNA table generation (OSTG) program.
System Action: None.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the OSTG program.
*I903* | OSTG RUN COMPLETE |
Explanation: This is the OSTG end-of-job message that is printed on the OSTG report file. A similar message is sent to the operator.
System Action: Control is returned to the operating system.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S001* | OSTG CANCELLED DUE TO PARM ERROR |
Explanation: The PARM parameter in the EXEC statement was not specified correctly. See the messages on the OSTG report for the specific error.
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S002* | OSTG CANCELLED DUE TO OPEN ERROR |
Explanation: The OPEN of an OSTG data set failed.
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S003* | OSTG CANCELLED DUE TO INPUT STATEMENT ERROR |
Explanation: A severe error was detected while processing the input definition statements.
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S004* | OSTG CANCELLED DUE TO SORT ERROR |
Explanation: The OS/VS SORT program returned an error code to the offline ACF/SNA table generation (OSTG) program.
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the OSTG program.
*S005* | OSTG CANCELLED DUE TO EXCESSIVE ERRORS |
Explanation: The offline ACF/SNA table generation (OSTG) program run is canceled when more than 100 errors with severity E messages are encountered in the input.
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the OSTG program.
*S021* | EXEC PARM CPUID INVALID |
Explanation: The CPUID value specified on the PARM parameter in the EXEC statement of the JCL used to run the offline ACF/SNA table generation (OSTG) program is not alphanumeric (A to Z or 0 through 9).
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S022* | EXEC PARM CPUID FORMAT ERROR |
Explanation: The value of CPUID specified for the PARM parameter in the EXEC statement of the JCL used to run the offline ACF/SNA table generation (OSTG) program can only be specified as 1 character.
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S031* | EXEC PARM SDPSID CPUID INVALID |
Explanation: One of the values specified for CPUID and SDPSID on the PARM parameter in the EXEC statement of the JCL used to run the offline ACF/SNA table generation (OSTG) program is not alphanumeric (A to Z or 0 through 9).
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S032* | EXEC PARM SDPSID FORMAT ERROR |
Explanation: The value of SDPSID specified on the PARM parameter in the EXEC statement of the JCL used to run the offline ACF/SNA table generation (OSTG) program is not coded correctly.
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S041* | EXEC PARM PILOTID INVALID/FORMAT ERROR |
Explanation: The value of PILOTID specified on the PARM parameter in the EXEC statement of the JCL used to run the offline ACF/SNA table generation (OSTG) program is not valid. The value specified must be 1 alphanumeric character.
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S051* | EXEC PARM GENTYPE INVALID/FORMAT ERR |
Explanation: The value specified for GENTYPE on the PARM parameter in the EXEC statement of the JCL used to run the offline ACF/SNA table generation (OSTG) program is not one of the following:
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S061* | EXEC PARM SUBAREA INVALID |
Explanation: The value specified for SUBAREA on the PARM parameter in the EXEC statement of the JCL used to run the offline ACF/SNA table generation (OSTG) program is not valid. The value specified:
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S091* | EXEC PARM CPUID MISSING |
Explanation: The value of CPUID specified for the PARM parameter in the EXEC statement of the JCL used to run the offline ACF/SNA table generation (OSTG) program was not found.
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S092* | EXEC PARM PILOTID MISSING |
Explanation: The value of PILOTID specified for the PARM parameter in the EXEC statement of the JCL used to run the offline ACF/SNA table generation (OSTG) program was not found.
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S095* | EXEC PARM CPUID NOT = 1ST SDPSID CPU |
Explanation: The first CPU ID specified for the SDPSID value for the PARM parameter in the EXEC statement of the JCL used to run the offline ACF/SNA table generation (OSTG) program is not equal to the CPUID value specified for the PARM parameter in the same EXEC statement.
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S098* | xxxxxxxx INVALID KEYWORD FOUND |
Where:
Explanation: A value that is not valid was found on the PARM parameter in the EXEC statement of the JCL used to run the offline ACF/SNA table generation (OSTG) program.
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S099* | EXEC PARM SYNTAX ERROR FOUND |
Explanation: The PARM parameter in the EXEC statement of the JCL used to run the offline ACF/SNA table generation (OSTG) program could not be parsed correctly.
System Action: The table generation process is ended.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S111* | PREMATURE END OF FILE |
Explanation: The end-of-file condition was raised on the OSTG input data set before a valid NCP, CTC, or ALS statement was found.
The NCP or ALS statement must be the last statement processed.
System Action: The OSTG run is canceled.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*S297* | CPUID ON ANTDEF NOT = EXEC PARM CPUID |
Explanation: The value specified for the CPUID parameter on the ANTDEF input definition statement is not the same as the CPUID value specified for the PARM parameter in the EXEC statement of the JCL used to run the offline ACF/SNA table generation (OSTG) program.
System Action: The OSTG run is canceled.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program and the ANT deck. See TPF System Generation for more information about system generation and the MSGRTA statements that are used to create the ANT deck.
*S298* | INCONSISTENT USE OF SDPSID |
Explanation: The SDPSID value must be either specified or omitted for both the ANTDEF input definition statement and on the PARM parameter in the EXEC statement of the JCL used to run the offline ACF/SNA table generation (OSTG) program.
System Action: The OSTG run is canceled.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program and the ANT deck. See TPF System Generation for more information about system generation and the MSGRTA statements that are used to create the ANT deck.
*S299* | INCONSISTENT USE OF CPUID |
Explanation: The CPUID value must be specified for both the ANTDEF input definition statement and on the PARM parameter in the EXEC statement of the JCL used by the offline ACF/SNA table generation (OSTG) program.
System Action: The OSTG run is canceled.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program and the ANT deck. See TPF System Generation for more information about system generation and the MSGRTA statements that are used to create the ANT deck.
*W402* | xxxxxxxx TPF APPL NAME STARTS WITH NUMERIC |
Explanation: The first character specified in the NAME keyword of the ANTNME macro starts with a numeric character of 0 through 9. This TPF application program name cannot be used in a SNA network because SNA names cannot begin with a numeric character.
However, this application program can be used in a TPF-TPF routing environment by using the FMMR protocol because the application program name is used only in the private TPF protocol and is not externalized in the SNA network.
System Action: Processing is continued.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program. See TPF System Generation for more information about the MSGRTA macro.
*W407* | CLU MISSING: REQUIRED KEYWORD FOR PRIMARY ALS |
Explanation: The CLU parameter is required when defining the primary adjacent link station (ALS). The CLU parameter is not required for a backup ALS in a 37x5 multiple central control unit.
System Action: Processing is continued.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*W408* | LUTYPE=ANY - ADDITIONAL KEYWORDS IGNORED |
Explanation: LUTYPE=ANY was specified on the RSC input definition statement. The other keywords on this RSC input definition statement are ignored.
System Action: The unrelated keywords are ignored.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*W409* | LUTYPE=NEF - ADDITIONAL KEYWORDS IGNORED |
Explanation: LUTYPE=NEF was specified on the RSC input definition statement. The other keywords on this RSC input definition statement are ignored.
System Action: The unrelated keywords are ignored.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*W410* | APPLICATION LU SPECIFIED, VALUES DEFAULTED TO |
Explanation: LUTYPE=APPLU or LUTYPE=APSLU was specified on the RSC input definition statement. As a result, the offline ACF/SNA table generation (OSTG) program imposes values for some of the other parameters.
Additional severity I messages follow this message. The additional messages show the actual imposed values.
System Action: The imposed values override all other specifications for the parameters. Any additional parameters that were specified, but are not relevant to this RSC type, are ignored.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the OSTG program.
*W412* | xxxxxxxx INVALID KEYWORD THIS STMNT, IGNORED |
Where:
Explanation: The parameter referred to in the message is not valid for this type of input definition statement.
System Action: The parameter specified is ignored.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*W500* | RECVRY AND PSV KEYWORDS ARE MUTUALLY EXCLUSIVE |
Explanation: Both the RECVRY and PSV parameters were specified in the RSC input definition statement.
System Action: Processing is continued.
User Response: None.
See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.
*W700* | UNKNOWN SUBAREA FOR FOLLOWING LU |
Explanation: During the update phase of the offline ACF/SNA table generation (OSTG) program, a resource was found that refers to a TPF CPU for which no subarea value was defined.
System Action: Processing is continued. The resource is identified immediately after this message.
User Response: This may be an error based on the network configuration, so do one of the following:
See TPF ACF/SNA Network Generation for more information about the OSTG program.