gtpm4m08 | Messages (System Error and Offline) |
Program: CCTAPE(CEFT)
Error Message: NO W/A AVAILABLE FOR CCW BUILD
Explanation: Excessive tape device medium errors have exhausted the CCW work area allocation and the tape I/O error recovery routines are unable to construct a CCW set for repositioning a tape prior to retrying an I/O operation.
System Action: A catastrophic system error is issued.
User Response: Review the system error dump to determine the device address.
As soon as possible take the device in question offline and see your IBM service representative.
Program: CCTAPE(CEFE)
Error Message: TAPE tapename NOT IN TSTB
Where:
Explanation: A TASNC macro was issued but the tape macro service routines can find no entry for the tape in the tape status table.
System Action: The entry control block (ECB) is ended.
User Response: Review the system error dump to determine which program issued the TASNC macro.
Application programs must not issue the TASNC macro for a tape that has not already been opened through a TOPNC, as the TOPNC processing will ensure that the tape is mounted.
Program: CCTAPE(CEFE)
Error Message: TASNC ISSUED BUT TAPE NOT OPEN
Explanation: A TASNC macro was issued but the tape macro service routines found that the tape is not indicated as open in the tape status table.
System Action: The entry control block (ECB) is ended.
User Response: Review the system error dump to determine which program issued the TASNC macro.
Application programs must not issue the TASNC macro for a tape that has not already been opened through TOPNC.
Program: CCTAPE(CEFE)
Error Message: TAPE tapename NOT HELD
Where:
Explanation: A tape macro was issued but the tape macro service routine found that the specified tape is not indicated as being assigned (through a TOPNC or TASNC) to the ECB.
System Action: The ECB is ended.
User Response: Probable application program error, but may be the result of operator intervention, for example, the ZTOFF command was entered for the tape in question.
Ensure that the problem is not the result of operator intervention by checking that the tape has an entry in the tape status table.
The following macros must not be used by application programs unless the specified tape was assigned to the ECB through a TOPNC or TASNC:
Program: CCTAPE(CEFE)
Error Message: TAPE tapename ALREADY OPEN
Where:
Explanation: A TOPNC macro was issued but the tape macro service routines found that the specified tape is already indicated as open in the tape status table.
System Action: The ECB is ended.
User Response: Probable application program error, but may be the result of operator intervention, for example, the operator initiated an application program requiring a tape that is already in use.
Ensure that the problem is not the result of operator intervention. If not so caused, then correct the application program. Application programs must not issue TOPNC macros for tapes that are already opened.
Program: CCTAPE(CEFE)
Error Message: TASNC ISSUED - TAPE NOT AVAILABLE
Explanation: A TASNC macro was issued but the tape macro service routine find that the specified tape is already assigned to the ECB.
System Action: The entry control block (ECB) is ended.
User Response: Review the system error dump to determine which program issued the TASNC macro.
Application programs must not issue TASNC for tapes that are already assigned to the ECB.
Program: CCTAPE(CEFE)
Error Message: INVALID PARAMETERS FOR TPINC
Explanation: A TPINC macro was issued with parameters that are not valid.
System Action: The entry control block (ECB) is ended.
User Response: Review the system error dump.
Program: CCTAPE(CEFE)
Error Message: TOPNC PARMS NON COMPAT WITH TSTB
Explanation: A TOPNC macro was issued but the tape macro service routines find that the usage (input or output) indicated in the tape status table does not agree with the TOPNC parameter.
System Action: The ECB is ended.
User Response: Probable operational error. General tapes must be mounted in accordance with the requirements of the application package which will use them. Review the operational procedures.
Program: CCTAPE(CEFE)
Error Message: TPRDC ISSUED - C/B ALREADY HELD
Explanation: A TPRDC macro was issued but the tape macro service routines find that a main storage block is already attached at the specified level.
System Action: The ECB (ECB) is ended.
User Response: Review the system error dump to determine which program issued the TPRDC macro.
If a main storage block is attached on a main storage level which is to be used for a TPRDC macro, then it is essential to release the level, through a RELCC or CRUSA macro, before issuing the TPRDC macro.
Program: CCTAPE(CEFE)
Error Message: NO BLK ATTACHED FOR TWRTC/TOURC
Explanation: A TWRTC/TOURC macro was issued but the tape macro service routines find that there is no main storage block attached a specified level.
System Action: The entry control block (ECB) is ended.
User Response: Review the system error dump to determine which program issued the TWRTC/TOURC macro.
This error can occur because of, for example, a retrieval error on a previous FINWC macro.
Program: CCTAPE(CEFT)
Error Message: TAPE I/O ERROR NO RECOVERY/AMSS
Appended Message: None.
Explanation: A tape I/O error occurred for which the control program tape routines have no recovery procedure defined and for which AMSS recording is not performed.
System Action: Control returned to the entry control block (ECB) with the appropriate error flag set.
User Response: This error condition can cause the loss of critical system records on the tape. It is essential that all such errors be checked for possible impact of this type.
Causes of this error include:
A message sent to the prime computer room agent set (CRAS) console and this message can be used to determine whether the error was caused by a hardware failure (for example, device not operational), or a software error (for example, a CCW op code that is not valid).
See the control program information in TPF Operations for more information.
Program: CCTAPE(CEFE)
Error Message: TAPE I/O ERROR NO RECOVERY/AMSS
Appended Message: SIOSC LOGIC ERROR OR QUEUE CORRUPTION
Explanation: There are two possible causes for this message:
System Action: A catastrophic system error is issued.
User Response: Review the system error dump. Queue corruption is indicated when the contents of the location pointed to by R4 and the contents of R1 do not agree. Corruption of TSTB section 2 is probable.
If queue corruption is not indicated, then a SIOSC error has occurred. Condition code 1 indicates a CIO logic error, while condition code 2 indicates that CCTAPE is attempting to initiate an I/O request that is already active. Possible causes of these conditions are:
Program: CCTAPE(CEFE)
Error Message: CE1IOC ALREADY ZERO AT OP END
Explanation: The post interrupt processing routine for a tape I/O macro finds that the entry control block (ECB) I/O counter was already set to zero.
System Action: ECB processing is continued.
User Response: Review the system error dump. It is possible that the main storage is corrupted.
Application programs must not modify the ECB I/O counter (CE1IOC).
Program: Displayed on the console and in the dump.
Error Message: TAPE MACRO USED PRIOR TO TAPE RESTART COMPLETION
Explanation: An attempt was made to use one of the following tape macros before tape restart completed:
System Action: The ECB is exited.
User Response: Modify the program that is trying to use the macro such that the macro waits for tape restart to complete before issuing the macro.
Program: CCTAPE(CEFE)
Error Message: ECB TAPE CHAIN CORRUPTED
Explanation: A tape macro was issued but the tape macro service routines find that the ECP tape chain (CE1TAP or CPMTDP) does not contain a valid tape module number.
System Action: The entry control block (ECB) is ended.
User Response: Review the system error dump.
Where the special tape name is used, the correct tape module number must be saved in CE1TAP prior to issuing the macro. Where the special tape name is not used, the application program must not modify CE1TAP. An application program must not modify the tape chain field (CPMTDP) of any entry in the tape status table.
Program: CCTAPE(CEFT, CEFS)
Error Message: UNRECOVERABLE TAPE I/O ERROR
Explanation: An unrecoverable tape I/O error for which AMSS error recording is required occurred.
System Action: Control returns to the entry control block (ECB) with the appropriate error flags set.
User Response: This error condition can cause the loss of critical system records on the tape. It is essential that all such errors be checked for possible impact of this type.
Refer to the message that is sent to prime computer room agent set (CRAS) console for details about the error. See TPF Operations for more information about tape support.
Program: CCTAPE(CEFE)
Error Message: INVALID TAPE NAME SPECIFIED
Explanation: An application program coded a tape macro that uses the name parameter to point to the tape name. The tape name indicated is not valid.
System Action: The application program ends.
User Response: Review the contents of R14 to find the error. Bytes 1 through 3 of R14 contain the invalid tape name pointed to. To be valid, the tape name must be assigned a three-character tape name.
See TPF Operations for more information about valid character tape names.
Program: CCENBK(CCEB)
Error Message: ECB EXCEEDED MAXIMUM PROGRAM NESTING
Explanation: The TPF system has been defined to limit the number of program nesting levels to the number that can fit in the entry control block (ECB). You can use the ZCTKA DISPLAY command to display the number of program nesting levels that can fit in the entry control block (ECB).
The number of program enters with return (ENTRCs) and the number of programs that were locked in main storage (GETPCs) during processing of the entry has exceeded the number of program nesting levels that can fit in the ECB. The dump displays the program nesting levels in the ECB.
System Action: The ECB ends. If an entry was activated from an online console, notification is sent to the operator.
User Response: Do one of the following:
See TPF Operations for more information about the ZCKTA DISPLAY and ZCTKA ALTER commands.
Program: CCENBK(CCEB, CCED)
Error Message: BACKC ISSUED WITH NO PROGRAM NESTED
Appended Message: ERROR RETURNING TO CALLING PROGRAM
Explanation: An operational program issued a BACKC macro but there is no program to go back to.
System Action: The ECB is ended. If entry was activated from an online console, notification is sent to the operator.
User Response: Check the program issuing the BACKC macro. Determine whether the program should end with EXITC or exit(), or whether the program should have been called with an ENTRC.
Program: CLE9
Error Message: CORE RESIDENT PROGRAM AREA IS CORRUPTED
Explanation: When program CLE9 is invoked to release a core resident program block to the core resident program area's (CRPA) free chain, it detects an error condition. The error condition is that the starting address of the program block (kept in PATCA) is within the valid range of CRPA but the ending address is not; for example, the program length field of the program header is corrupted.
System Action: This dump will be issued and control returns to the calling program with an error code.
User Response: See your system programmer to check the error condition.
Program: CCENBK(CCEB, CCEF)
Error Message: PROGRAM NAME MISMATCH OR ID NOT 00FF -- PROGRAM NAME MAY BE IN R1
Appended Message: NAME MISMATCH OR RECORD ID NOT X'OOFF'
Explanation: Either the program or load module name in the program allocation table (PAT) entry:
This error indicates that the program or load module was not loaded to file or that the file copy was corrupted. The SNAP dump displays the header and PAT entry of the retrieved record.
System Action: The ECB ends. If the entry was activated from an online console, notification is sent to the operator.
User Response: Do the following:
Program: CCENBK(CCEB, CCEF)
Error Message: HARDWARE ERROR WHEN RETRIEVING PROGRAM RECORD
Error Message: HARDWARE ERROR RETRIEVING PROGRAM RECORD
Explanation: A disk hardware error occurred while attempting to retrieve a program or load module from file.
System Action: The ECB is ended. If entry was activated from an online console, notification is sent to the operator.
User Response: None.
Program: CCENBK(CCEB)
Error Message: INVALID PROGRAM RECORD FILE ADDRESS
Explanation: A file address that is not valid was detected while attempting to retrieve a program from file.
System Action: The ECB is ended. If entry was activated from an online console, notification is sent to the operator.
User Response: None.
Program: CCENBK(CCEC)
Error Message: GETPC ISSUED FOR PRIVATE PROGRAM
Error Message: GETPC ISSUED FOR DUMMY ALLOCATED PROGRAM
Error Message: RELPC ISSUED FOR DUMMY ALLOCATED PROGRAM
Explanation: A GETPC or RELPC macro was issued for a PRIVATE or DUMMY allocated program and the calling program did not specify the error return parameter.
System Action: The ECB is ended. If entry was activated from an online console, notification is sent to the operator.
User Response: Check the program issuing the GETPC macro or the RELPC macro to determine the action to be taken.
Program: CCENBK(CCEB)
Error Message: UNDEFINED ERROR RETURNED DURING PROGRAM RETRIEVAL
Explanation: A return code that is not valid was detected while attempting to retrieve a program from file. The return code was other than a hardware error or a file address that is not valid.
System Action: The ECB is ended. If entry was activated from an online console, notification is sent to the operator.
User Response: Check the dump to determine what type of error occurred. Check the program in error.
Program: CCENBK(CCEB)
Error Message: INVALID PROGRAM TYPE
Explanation: The program type defined in the program allocation table (PAT) entry of the program is not valid.
System Action: The ECB is ended. If the entry was activated from an online console, notification is sent to the operator. The SNAP dump displays the PAT entry in error.
User Response: Review the system error dump to determine whether the PAT is corrupted.
Program: CCENBK(CCEB)
Error Message: ECB EXITING ON WRONG I-STREAM
Explanation: The I-stream number in the ECB was not equal to the number in the prefix page during EXITC processing. Either the ECB was corrupted or processing incorrectly switched to another I-stream.
System Action: The I-stream number in the ECB is corrected and processing continues.
User Response: None.
Program: CCENBK(CCEB, CCEC)
Error Message: INVALID PROGRAM NAME OR INDEX
Explanation: The program allocation table (PAT) entry for the supplied program could not be found or the supplied PAT displacement index was not valid.
System Action: The ECB is ended. If entry was activated from an online console, notification is sent to the operator. The SNAP dump displays the program data, name or displacement index, used to locate the PAT entry.
User Response: Check the dump to determine if storage corruption occurred or if an attempt was made to enter an unallocated program.
Program: CCENBK(CCEB)
Error Message: ATTEMPTED TO ENTER DUMMY ALLOCATED PROGRAM
Explanation: An attempt was made to enter a program that has a dummy allocation.
System Action: The ECB is ended. If entry was activated from an online console, notification is sent to the operator.
User Response: Investigation the problem to determine why the requested program was allocated as a dummy.
Program: CCENBK(CCEB)
Error Message: ATTEMPTED TO ENTER SPARE ALLOCATED PROGRAM
Explanation: An attempt was made to enter a program that was allocated as a spare program.
System Action: The ECB is ended. If entry was activated from an online console, notification is sent to the operator. The SNAP dump displays the program allocation table (PAT) entry of the spare program.
User Response: Check the problem to determine why the spare program is being entered. If necessary, change the program's allocation and load it to its online file location.
Program: Displayed in the console
Error Message: INVALID ACTIVATION NUMBER DETECTED
Explanation: One of the following errors occurred:
This condition is detected while performing the following functions:
System Action: The ECB is exited. The SNAP dump displays the ECB activation number and the EAT entry.
User Response: See your IBM service representative to report the problem.
Program: Displayed in the console and in the dump.
Error Message: ERROR IN GRAMMAR A POSITIONAL PARAMETER WAS FOUND AFTER A KEYWORD PARAMETER
Error Message: GRAMMAR ERROR AN UPPERCASE LETTER CANNOT FOLLOW A LOWER CASE LETTER
Error Message: GRAMMAR TOO LARGE
Error Message: ILLEGAL CHARACTER FOLLOWING WILDCARD
Error Message: ILLEGAL CHARACTER FOLLOWING PARENTHESIS
Error Message: ILLEGAL KEYWORD DELIMITER
Error Message: ILLEGAL USE OF TOKEN IN LIST PARAMETER
Error Message: ILLEGAL WILD CARD CHARACTER IN LIST
Error Message: INVALID CHARACTER IN GRAMMAR
Error Message: INVALID LIST VALUE IN GRAMMAR
Error Message: TOO MANY CHARACTERS IN MANDATORY PARAMETER LIST
Error Message: UNEVEN BALANCE OF LEFT BRACES IN THE GRAMMAR
Error Message: UNEVEN BALANCE OF LEFT BRACKETS IN THE GRAMMAR
Error Message: UNMATCHED PARENTHESIS IN GRAMMAR
Explanation: The grammar is in error. The messages are self-explanatory.
System Action: The ECB is ended.
User Response: Correct the grammar.
See the TPF C/C++ Language Support User's Guide for more information about the IBM C message parser and defining grammar.
Error Message: INVALID PARAMETER VALUE FOR BLDPRSTR
Explanation: One or more of the size parameters (parse_out_size, parm_size, or value_size) passed to IPRSE_bldprstr is a non-positive integer.
System Action: The ECB is ended.
User Response: Change the parameters that are not valid to the appropriate values
See the TPF C/C++ Language Support User's Guide for more information.
Program: Displayed on the console and in the dump.
Error Message: 'C' LANGUAGE SUPPORT DISABLED
Appended Message: REQUEST FOR 'C' STATIC/STACK FRAME REJECTED
Explanation: This message occurs during the static exception routine or the stack exception routine, and is generated by CL02 in CCLANG. This means that a C program segment was called, but the IBM C language support is not active. The IBM C language support is not active because:
System Action: The ECB is ended.
User Response: Check to see if the the IBM C language support is installed. If the support is present, the C programs may have been activated too early during restart stage and therefore the IBM C language support initialization is not complete yet.
Program: CCLANG(CL02)
Error Message: 'C' STATIC STORAGE REQUEST ERROR
Appended Message: C STATIC FRAME EXCEEDS MAXIMUM ALLOWED
Explanation: The static frame size exceeds maximum size.
System Action: The ECB is ended.
User Response: Reduce the number of static variables used by the C function.
Program: CCLANG(CL02)
Error Message: 'C' STACK FRAME REQUEST ERROR
Appended Message: SIZE OF REQUESTED 'C' STACK FRAME EXCEEDS MAXIMUM ALLOWED
Explanation: The stack frame size exceeds the maximum frame size.
System Action: The ECB is ended.
User Response: Reduce the number of automatic variables used by the C function.
Program: CCLANG(CL02)
Error Message: 'C' SET LOCALE REQUEST ERROR
Appended Message: INVALID LOCALE NAME SPECIFIED BY STACK EXCEPTION USER EXIT
Explanation: A locale name that is not valid was specified by the stack exception user exit.
System Action: The ECB is ended.
User Response: Request a valid locale name.
See the TPF C/C++ Language Support User's Guide for more information about specifying locales.
Program: Displayed on the console and in the dump.
Error Message: INVALID ARG PASSED TO API FUNCTION
Appended Message: (varies)
Explanation: A argument that is not valid was passed to a TPF API function. The appended message identifies the function name and the parameter that caused the error.
System Action: The ECB is ended.
User Response: Correct error in function call.
See the TPF C/C++ Language Support User's Guide for detailed descriptions about these functions and their parameters.
Error Message: INVALID GLOBAL AREA SPECIFIED
Explanation: A global area that is not valid was specified.
System Action: The ECB is ended.
User Response: Specify a valid global area.
Error Message: INVALID CRETC TIME VALUE SPECIFIED
Explanation: The TPF system issues this message when a negative time value parameter is coded in the CRETC macro.
System Action: None.
User Response: None.
Error Message: INCOMPATIBLE JMPBUF PASSED TO LONGJMP FUNCTION
Explanation: A jmpbuf that is not valid was specified.
System Action: The ECB is ended.
User Response: Correct error in function call.
Appended Message: SIPCC-LIST-PTR MISSING OR NOT VALID
Explanation: A sipcc_list_ptr parameter was required but not specified or the parameter value was NULL for a sipcc function call.
System Action: The entry control block (ECB) ends.
User Response: Determine why the sipcc_list_ptr parameter was missing or specified a null value and correct the error in the function call.
See the TPF C/C++ Language Support User's Guide for more information about the sipcc function.
Program: Displayed on the console and in the dump.
Error Message: CORRUPTION DETECTED IN HEAP AT addr ADDRESS
Where:
Explanation: A program wrote over node control data (for example, header and uplink addresses) surrounding allocated storage. The approximate address of the corruption is contained in R1.
System Action: The ECB is ended.
User Response: Look for the cause of the corruption at the address contained in R1 or higher. The control data may have been corrupted at any time prior to the error being detected.
Program: Displayed on the console and in the dump.
Error Message: PROGRAM LOAD EVENT HAS TIMED OUT
Explanation: The event used to ensure all the core resident programs are in the core resident program area by 1052 state has timed out.
System Action: None.
User Response: Do one of the following:
See TPF Operations for more information about the ZIDOT command.
Program: CLIB
Error Message: ERROR LOCKING PROGRAM IN CORE
Explanation: An ISO-C library that was allocated as preload could not be fetched. The SNAP dump displays the program allocation table (PAT) entry. The PAT entry contains the name of the ISO-C library that could not be fetched.
System Action: Restart processing continues.
User Response: Do the following:
Program: CCEB
Error Message: ENTERED DEACTIVATED PROGRAM - ECB EXITED
Explanation: The entry control block (ECB) entered a program in a loadset that was deactivated when a ZOLDR DEACT command with the SERRC parameter specified was entered.
System Action: The ECB is exited.
User Response: None.
See TPF Operations for more information about the ZOLDR DEACT command.
Program: CIMU CILG
Error Message: INVALID MESSAGE NUMBER
Explanation: An operational program entered CIMU or CILG to issue an output message with a message number that is not valid. The message number that is not valid was saved in the ECB work area starting at EBX000.
System Action: Control returns to the operational program.
User Response: Check the program that issued the message.
Program: CIMN
Error Message: INVALID MACRO/RECORD TYPE ENCOUNTERED
Explanation: An operational program entered CIMN to request a macro service. CIMN issues this system error if any macro service type or record type that is not valid is found. The following parameter values were saved in the ECB work area starting at EBX000:
System Action: Control returns to the operational program.
User Response: Check the program that requested the macro service.
Program: CRFH
Error Message: HEAP STORAGE EXHAUSTED
Explanation: The parser is unable to allocate sufficient heap storage to complete its processing.
System Action: The ECB is ended.
User Response: Determine why the ECB heap storage was depleted.
Program: CILA
Error Message: ERROR IN INPUT FILE FOR ZTPLD
Explanation: The auxiliary loader did not find an expected data item within the input file. It is possible that TLDR's output was corrupted or truncated. During ZTPLD processing, one of the following error messages was issued:
After the error message was issued, this system dump was issued to facilitate problem diagnosis in case more information is needed to determine what is wrong with the TLDR output file.
System Action: Control returns to the operational program, and the load processing is ended.
User Response: Do the following:
If you are unable to determine what is wrong with the TLDR output file after trying the steps previously listed, review the system error dump to determine why the input file was rejected by ZTPLD. If processing was ended after a data record was read from tape or GDS, then that record will be found on data level 5. In addition, the auxiliary loader parameter block (which is described in the ztpld.h header file) will be found in an IBM C language stack block (the one chained directly from the initial block).
This information can be used to diagnose why the input file was not acceptable for ZTPLD processing. Some possible reasons for this error are:
Program: Displayed on the console and in the dump.
Error Message: AUTO STORAGE BLOCK RELEASE ERROR
Explanation: Attempts to release automatic storage blocks during BACKC, ENTNC, ENTDC, or EXITC processing failed. This message follows either a 0006DA system error that indicates a block release error or a 0006D9 system error that indicates a double release of a storage block.
System Action: The entry control block (ECB) ends and the TPF system issues a system error dump of the general registers. No other auto storage blocks attached to this ECB are released. Therefore, those blocks can no longer be used by the TPF system. Immediately prior to the system error routine, register 1 is set up to contain the address of the block that cannot be released.
User Response: A failure to release automatic storage blocks is usually the result of block corruption. Review the system error dump of the ECB and working storage generated from the 0006D9 system error dump or 0006DA system error dump.
Program: Displayed on the console and in the dump.
Error Message: C LANGUAGE STACK BLOCK RELEASE ERROR
Explanation: Attempts to release the IBM C language stack blocks during SWISC, ENTDC, or EXITC processing failed. This message will follow a 0006DA system error, which indicates a block release error.
System Action: The ECB is ended and a dump of the ECB and working storage is generated. No other IBM C language stack blocks attached to this ECB are released, therefore those blocks can no longer be used by the TPF system. Immediately prior to the system error routine, register 1 is set up to contain the address of the block that could not be released.
User Response: A failure to release IBM C language stack blocks is usually the result of block corruption. Determine the cause of the error.
Program: Displayed on the console and in the dump.
Error Message: C LANGUAGE STATIC BLOCK RELEASE ERROR
Explanation: Attempts to release IBM C language static blocks during SWISC, ENTDC, or EXITC processing failed. This message will follow a 0006DA system error, which indicates a block release error.
System Action: The entry control block (ECB) is ended and a dump of the ECB and working storage is generated. No other IBM C language static blocks attached to this ECB are released. Therefore those blocks can no longer be used by the TPF system. Immediately prior to the system error routine, R1 is set up to contain the address of the block that could not be released.
User Response: A failure to release IBM C language static blocks is usually the result of block corruption. Determine the cause of the error.
Program: CEDI(CCNUCL)
Error Message: WTOPC DETECTED BAD ADDRESS IN PARM LIST
Explanation: The WTOPC service routine detected a bad address passed on the TEXTA, BUFFA, or level pointed to by the LEVEL parameter. The base address of the WTOPC parameter list may also be bad.
System Action: The dump is issued. If the WTOPC call is from CP code, control returns to the caller, otherwise the E-type program is exited.
User Response: The program should be inspected to verify that addresses passed to the TEXTA, BUFFA, LEVEL, and SUB parameters are set up correctly. If the base address of the WTOPC parameter list is bad, the code immediately preceding the WTOPC SVC should be inspected for possible corruption.
Program: Displayed on the console and in the dump.
Error Message: BSC LMT ERROR
Explanation: While trying to read an overflow record from file, the message router had an error. This error can occur only on long messages that are to be transmitted on a binary synchronous communication (BSC) line.
System Action: The message is discarded.
User Response: Review the system error dump to determine whether the file address was valid. If not, the problem was probably caused by an application program issuing the ROUTC macro for a message block that is not valid. The routing control parameter list (RCPL) saved in the prime message block contains the name of the originating application program.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A SENDL macro was issued with the data level holding a 1055-byte or 4K block.
System Action: Return to calling program
User Response: Modify the program to use correct SEND interface.
Program: CCCCP1(CLXE)
Error Message: None.
Explanation: A SEND was issued but a message block is not being held.
System Action: The ECB is ended. If entry was activated from an online console, notification is sent to the operator.
User Response: Modify the program to use correct SEND interface.
Program: CCCCP1(CLXE)
Error Message: None.
Explanation: The communication line number referenced in the SENDC or ROUTC macro is outside the allowable range and is not a pseudo Network Extension Facility (NEF) line number or an AX.25 Logical End Point Identifier (LEID).
System Action: The entry control block (ECB) is ended. The entry was activated from an online console, the TPF system notifies the operator.
User Response: None.
Program: CCCCP1(CLXE)
Error Message: None.
Explanation: A SENDA or SENDC macro was issued to an EP line that was invalidated or is in hold status.
System Action: Return to the calling program.
User Response: None.
Program: CCCCP1(CLXD)
Error Message: None.
Explanation: A SENDA or SENDC was issued on an ALC line but there was no end of message character at the end of the message.
System Action: The ECB is ended. If entry was activated from an online console, notification is sent to the operator.
User Response: Have your system programmer determine the segment that issued the SENDA or SENDC and check for the byte count.
Program: CCCCP1(CLYC)
Error Message: MPX CHAN/PROG ERROR ON SUBCHANNEL subchannel
Where:
Explanation: A multiplex channel program error was detected for subchannel shown in the message (SDA 00 subchannel). The error was a program check, protection exception, or chaining check.
System Action: Machine stops.
User Response: Restart or reload. Have your system programmer review the system error dump to determine the cause of the channel program error.
Program: Displayed on the console and in the dump.
Error Message: INCORRECT FIXED BITS IN LSTB
Explanation: The LSTB fixed bits are not valid.
System Action: None.
User Response: None.
Program: CCCCP1(CLXE)
Error Message: None.
Explanation: The message byte count either exceeds the block size or is less than the actual length.
System Action: The ECB is ended. If entry was activated from an online console, notification is sent to the operator.
User Response: Modify the program or the data.
Program: COBU
Error Message: None.
Explanation: The requested process selection vector (PSV) is reserved and not in use.
System Action: The entry control block (ECB) is ended and the message is lost.
User Response: Have your system programmer review the system error dump to determine why a reserved PSV was requested.
Program: COBT
Error Message: None.
Explanation: The requested process selection vector (PSV) was not found in COBU.
System Action: The entry control block (ECB) is ended. The SNA session, if any, is ended.
User Response: Have your system programmer review the dump and load a new version of COBU if necessary.
Program: CCCCP1(CLUK), CCCCP1(CLVK)
Error Message: None.
Explanation: An attempt was made to initiate an I/O on a communication line but the control information was determined not to be valid. This is a catastrophic system error.
System Action: The machine is stopped.
User Response: Restart or reload.
Program: CCCCP1(CLUK)
Error Message: None.
Explanation: During a post interrupt routine, control information was discovered to be wrong. This is a catastrophic programming error.
System Action: The machine is stopped.
User Response: Restart or reload.
Program: CCCCP1(CLYC)
Error Message: None.
Explanation: No core blocks were available for a read operation on a low-speed line.
System Action: Processing is ended.
User Response: None.
Program: CLUE
Error Message: SLN sln FR ALL CCP MSG NOS IN USE
Where:
Explanation: This message is reserved for World Trade use.
System Action: None.
User Response: None.
Program: CCCCP1(CLVK)
Error Message: None.
Explanation: A CIOUC macro was issued for a line number that is outside the valid range for the function requested.
System Action: A SERRC macro is issued and the entry control block (ECB) is exited.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Program: CIJP, CVAJ, CVQJ, CVQG, CIJA, CRM0, CML2
Error Message: POSSIBLE DUPLICATE SUBCHANNEL
Explanation: During line validation, the slot in the internal line table (ITLT) is nonzero for this line. The ITLT contains 255 1-byte slots and it is indexed by subchannel address. The internal line number for the line is stored in the corresponding ITLT slot when the line is validated. If the slot is nonzero, a possible duplicate subchannel is defined in the line status table (LSTB).
System Action: None.
User Response: Review the line status table to determine whether a subchannel was associated with more than one line. The LSTB can be located in the dump by using dump tag LNS.
Error Message: COMMON I/O MOUNT ERROR
Explanation: The line being validated is not attached to the TPF system.
System Action: Return to the calling program.
User Response: Attach the line to the TPF system.