gtpm5m0zMessages (Online)

CQAI-CSMP

CQAI0080ECTKI RETRIEVAL ERROR - UNABLE TO CHECK FOR STR EXTERNAL INTERRUPT

Explanation: Keypoint I (CTKI) could not be retrieved from disk while processing the Sysplex Timer (STR) external interrupt routine.

For Sysplex Timer Attachment Facility-1 (STAF-1), the external interrupt polling routine could not determine if an STR external interrupt occurred since the last time the polling routine was processed.

For Sysplex Timer Attachment Facility-2 (STAF-2), an STR Alert external interrupt occurred, but it is not possible to determine whether the interrupt was caused by a service request or a time adjustment.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON).

System Action: For STAF-1, the polling routine is scheduled to be processed again.

For STAF-2, the external interrupt is not logged for the Environmental Error Record Editing and Printing (EREP) program.

User Response: Do the following:

  1. Determine why CTKI could not be retrieved from disk.
  2. Correct the error.

For STAF-2, report the external interrupt to your IBM service representative.

CQAI0081EERROR READING STR DATA -- UNABLE TO CHECK FOR STR EXTERNAL INTERRUPT

Explanation: A required data word could not be obtained from the Sysplex Timer (STR) while processing the STR external interrupt routine. As a result, for Sysplex Timer Attachment Facility-1 (STAF- 1), the polling routine could not determine whether an STR external interrupt had occurred since the last time the polling routine was processed.

For Sysplex Timer Attachment Facility-2 (STAF-2), it is known that an STR Alert external interrupt occurred but it is not possible to determine whether the interrupt was caused by a service request or a time adjustment.

For STAF-1, there may be a problem with the processor controller.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON).

System Action: For STAF-1, the polling routine is scheduled to be processed again.

For STAF-2, the external interrupt is not logged for the Environmental Error Record Editing and Printing (EREP) program.

User Response: See your IBM service representative.

CQAI0082WSTR SERVICE IS REQUESTED

Explanation: A Sysplex Timer (STR) external interrupt occurred indicating that service may be required on the STR. The purpose of this request depends upon the STR and is published in Maintenance Information for the 9037 Sysplex Timer.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON).

System Action: The request is logged for the Environmental Error Record Editing and Printing (EREP) program.

User Response: See your IBM service representative.

See the console for the Sysplex Timer (STR) for more information.

CQAI0083WSTR TIME OFFSET CHANGES HAVE OCCURRED

Explanation: A Sysplex Timer (STR) external interrupt was received indicating one of the following:

The local time offset given by the Sysplex Timer is not used by the TPF system to set the clock.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON).

System Action: The condition is logged for the Environmental Error Record Editing and Printing (EREP) program.

User Response: When you enter a ZATIM command to set the time-of-day (TOD) clock, the new leap second offset is used. Follow your local practice for daylight savings time adjustment.

See the console for the Sysplex Timer (STR) for more information.

CQAI0084WPORT portnum AVAILABILITY CHANGE OCCURRED

Where:

portnum
The CPC port number.

Explanation: The CPC port connected to the Sysplex Timer (STR) has gone from operational to not operational or vice versa. If the primary port and the alternate port started out in synchronization and one of these ports is still operational, then the CPC synchronization is maintained. If none of the ports are operational, CPC synchronization is lost and appropriate error processing occurs.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (Enterprise Systems Connection).

System Action: STR information is gathered for each of the CPC ports. This information is logged for the Environmental Error Record Editing and Printing (EREP) program.

User Response: Seee your IBM service representative.

CQAI0085ISTR LINK TUNING CHANGE HAS OCCURRED

Explanation: A change in the tuning status of the ports connected to the Sysplex Timer (STR) occurred.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON).

System Action: STR information is gathered for each of the CPC ports. This information is logged for the Environmental Error Record Editing and Printing (EREP) program.

User Response: See your IBM service representative. The CPC may need to be resynchronized by entering the ZATIM command if synchronization is lost within the complex.

See the console for the Sysplex Timer (STR) for more information.

CRD90010IHCT INITIALIZATION SUCCESSFUL ENTRIES INITIALIZED -- entries

Where:

entries
The number of hot conversation table (HCT) entries. that were initialized.

Explanation: The TPF Application Requester (TPFAR) hot conversation (HCT) was initialized successfully during restart processing.

System Action: None.

User Response: None.

See the TPF Application Requester User's Guide for more information.

CRD90012WHCT NOT INITIALIZED, NO ENTRIES ALLOCATED

Explanation: There were no TPF Application Requester (TPFAR) hot conversation table (HCT) entries defined in keypoint 2. Therefore, the table was not initialized.

System Action: None.

User Response: If you want to initialize the HCT, do one of the following:

See TPF Operations for more information about the ZNKEY command. Also see the TPF Application Requester User's Guide for more information.

CRD90020ISDD INITIALIZATION SUCCESSFUL ALLOCATED -- xxxxx, COPIED -- yyyyy

Where:

xxxxx
The number of structured query language (SQL) database directory (SDD) entries allocated by Keypoint 2 (CK2SDDN).

yyyyy
The number of SQL SDD entries filled in with the SQL database directory entry information on file.

Explanation: The TPF Application Requester (TPFAR) initialization of the SQL SDD completed successfully.

System Action: None.

User Response: None.

See the TPF Application Requester User's Guide for more information.

CRD90021IMIGRATION OF CORE COPY OF SDD SUCCESSFUL MIGRATION OF FILE COPY AT NEXT UPDATE

Explanation: The TPF Application Requester (TPFAR) migration of the structured query language (SQL) database directory (SDD) completed successfully. The migration of the file copy takes place only after the ZSQLD command with the ADD or MODIFY parameter was entered. The migration may have changed the size of the entries and the type of record.

System Action: None.

User Response: None.

See the TPF Application Requester User's Guide for more information.

CRD90022WSDD NOT INITIALIZED, NO ENTRIES ALLOCATED

Explanation: There were no structured query language (SQL) database directory (SDD) entries allocated or initialized, because there were no entries defined in keypoint 2 (CK2SDDN).

System Action: Processing is continued.

User Response: If you want to allocate the SDD entries in the TPF system, do one of the following:

See TPF Operations for more information about the ZNKEY command. Also see the TPF Application Requester User's Guide for more information.

CRD90024WHOT CONVERSATIONS REQUESTED BY SDD EXCEED HCT ENTRIES ALLOCATED ALLOCATED -xxxxx, REQUESTED -yyyyy

Where:

xxxxx
The number of hot conversation table entries provided by keypoint 2 (CK2HCTN).

yyyyy
The number of hot conversations requested for all the structured query language (SQL) database directory (SDD) entries.

Explanation: The number of hot conversations required for all the structured query language (SQL) database directory (SDD) entries exceeds the number of hot conversation table entries provided by keypoint 2 (CK2HCTN).

System Action: The maximum number of hot conversation table entries are allocated starting from the top of the structured query language (SQL) database directory (SDD).

User Response: Do one of the following:

See TPF Operations for more information about the ZNKEY and ZSQLD commands. Also see the TPF Application Requester User's Guide for more information.

CRD90026ESDD NOT INITIALIZED, ERROR ON FIRST FIND. FIND ERROR ADDR --address

Where:

address
The structured query language (SQL) database directory (SDD) record file address.

Explanation: An error occurred accessing the first structured query language (SQL) database directory (SDD) record at the file address specified in the message.

System Action: Processing is continued.

User Response: Initialize the SDD record using the Initialize option on the ZSQLD command.

See TPF Operations for more information about the ZSQLD command. Also see the TPF Application Requester User's Guide for more information.

CRD90028ESDD NOT INITIALIZED, FACS ERROR.

Explanation: An file address compute program (FACE) error occurred when accessing the structured query language (SQL) database directory (SDD).

System Action: Processing is continued.

User Response: Verify the SDD record type allocation.

See the TPF Application Requester User's Guide for more information.

CRDH0010WTPFAR SQLH ERROR, RESOURCE LIMIT AT APPL SERVER, RETRY. SQLCODE code, SQLSTATE state

Where:

code
The structured query language (SQL) code returned to the application program.

state
The SQL state returned to the application program.

Explanation: TPF Application Requester (TPFAR) processing failed because of insufficient application server resources that are non-relational-database (RDB) resources. This failure has no effect on subsequent SQL commands and requests.

System Action: The SQLCODE and SQLSTATE are returned to the application program.

User Response: Because a problem occurred in the application server due to insufficient non-RDB resources, you should try the SQL statement again.

See the TPF Application Requester User's Guide for more information.

CRDH0012WTPFAR SQLH ERROR, RESOURCE LIMIT AT APPL SERVER, NO RETRY. SQLCODE code, SQLSTATE state

Where:

code
The structured query language (SQL) code returned to the application program.

state
The SQL state returned to the application program.

Explanation: TPF Application Requester (TPFAR) processing failed because of insufficient application server resources that are non-relational-database (RDB) resources. This failure affects subsequent SQL statements.

System Action: The SQLCODE and SQLSTATE are returned to the application program.

User Response: Because a problem occurred in the application state due to insufficient non-RDB resources, you should not try the SQL statement again.

See the TPF Application Requester User's Guide for more information.

CRDH0020WTPFAR SQLH ERROR, REMOTE RDB AUTHORIZATION FAILURE. SQLCODE code, SQLSTATE state

Where:

code
The structured query language (SQL) code returned to the application program.

state
The SQL state returned to the application program.

Explanation: An unauthorized user tried to access the requested relational database (RDB).

System Action: The SQLCODE and SQLSTATE are returned to the application program.

User Response: Verify the authorization for this RDB and, if necessary, correct the authorization.

See the TPF Application Requester User's Guide for more information.

CRDH0022WTPFAR SQLH ERROR, RDB NOT FOUND. SQLCODE code, SQLSTATE state

Where:

code
The structured query language (SQL) code returned to the application program.

state
The SQL state returned to the application program.

Explanation: You tried to access a relational database (RDB) that could not be found.

System Action: The SQLCODE and SQLSTATE are returned to the application program.

User Response: Validate the RDB requested in the command and take the appropriate action.

See the TPF Application Requester User's Guide for more information.

CRDH0024WTPFAR SQLH ERROR, IMPLIED ROLLBACK OCCURRED. SQLCODE code, SQLSTATE state

Where:

code
The structured query language (SQL) code returned to the application program.

state
The SQL state returned to the application program.

Explanation: TPF Application Requester (TPFAR) detected an error caused by an implied rollback.

System Action: An implied rollback is issued and the entry control block (ECB) is exited.

User Response: Investigate the cause of the implied rollback.

See the TPF Application Requester User's Guide for more information.

CRDW0001WNO SQL TRACE TABLE DEFINED FOR THE SYSTEM

Explanation: The structured query language (SQL) trace table was not defined for the TPF system.

System Action: None.

User Response: Do one of the following:

See TPF Operations for more information about the ZNKEY command. Also see the TPF Application Requester User's Guide for more information.

CRDW0002WNO SQL TRACE TABLE ENTRIES

Explanation: The structured query language (SQL) trace table does not contain any entries for the I-stream requested. No SQL commands were processed by any application programs on that I-stream.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZSTTD command. Also see the TPF Application Requester User's Guide for more information.

CRDW0004ISQL TRACE TABLE FOR I-STREAM nn

Where:

nn
The I-stream (displayed as a decimal number) that was specified in the ZSTTD command. The default is 1.

Explanation: This is the first line of the normal response to a request to display the structured query language (SQL) trace table. It is followed by a display of the trace table. The entries in the table for the specified I-stream are displayed when they meet the specified selection criteria. The displayed trace table entries reflect the subsystem where the ZSTTD command was entered.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZSTTD command. Also see the TPF Application Requester User's Guide for more information.

CRDW0005EI-STREAM SUPPLIED IS INVALID

Explanation: The I-steam supplied with the optional IS parameter is not currently active. Therefore, there is no structured query language (SQL) trace table associated with the I-stream.

System Action: None.

User Response: Determine the correct active I-stream that contains the SQL trace information and supply it with the IS parameter.

See TPF Operations for more information about the ZSTTD command. Also see the TPF Application Requester User's Guide for more information.

CRT00001IRIAT INITIALIZATION COMPLETE FOR VFADEF RECORD

Explanation: The virtual file access (VFA) data that was entered previously via the ZRTDM command was loaded from the VFA definition record on file into the correct slots in the in-core record ID attribute table (RIAT).

System Action: None.

User Response: None.

CRT00050EERROR TRYING TO RETRIEVE VFA DEFINITION RECORD FROM DASD

Explanation: An error occurred during a FINWC macro, while trying to retrieve the virtual file access (VFA) definition record, in the CRT0 segment.

System Action: The segment will BACKC to the CTKO restart scheduler.

User Response: See your system programmer for more information.

CRT00051EERROR DURING FACS PROCESSING FOR RECORD TYPE #VFARD -- RIAT INITIALIZATION ABORTED

Explanation: An error occurred during a call FACS while processing the virtual file access (VFA) definition record in the CRT0 segment.

System Action: The segment will BACKC to the CTKO restart scheduler.

User Response: See your system programmer for more information.

CRZ10007ECHAIN CHASE - INVALID FILE ADDRESS

Explanation: An error occurred when entering the ZCHCH command with the FILEADDR parameter specified. The file address specified is not valid.

System Action: The ZCHCH command is rejected.

User Response: Do the following:

  1. Determine the correct format of the ZCHCH command.
  2. Enter the command again using the correct format.

See TPF Operations for more information about the ZCHCH command.

CRZ10008ECHAIN CHASE - INCORRECT COUNT FIELD

Explanation: The ZCHCH command was entered with an incorrect value specified for the maximum number of chained records to be chased. The value specified must be from 1 to 999.

System Action: The command is rejected.

User Response: Enter the ZCHCH command again specifying a valid value for the maximum number of chained records to be chased.

See TPF Operations for more information about the ZCHCH command.

CRZ10010EMESSAGE addr WITH DISP loc IS OUT OF RANGE

Where:

addr
The chain address.

loc
The 3-byte hexadecimal displacement.

Explanation: The ZCHCH command was entered with a displacement (location) value specified that is not valid; it exceeds the record size range. The value specified must be a 3-byte hexadecimal displacement (location) in the chain chase where the file pool addresses of the next record in that chain chase is found.

System Action: The command is rejected.

User Response: Enter the ZCHCH command again specifying a valid displacement (location) value that is within the record size chain.

See TPF Operations for more information about the ZCHCH command.

CRZ10011ICHAIN CHASE-BACKWARD

Explanation: This is the normal response to the ZCHCH command with the B parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZCHCH command and for an example of the informational display.

CRZ10012ICHAIN CHASE-DISPL.loc

Where:

loc
The location in the chain chase at which the file pool address of the next record in that chain chase is found.

Explanation: This is the normal response to the ZCHCH command with the U parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZCHCH command and for an example of the informational display.

CRZ10013ECHAIN CHASE - INPUT HDR VALUE IS INCORRECT

Explanation: The ZCHCH command was entered with an incorrect value specified for the HDR parameter. The value must be either 4 or 8.

System Action: The command is rejected.

User Response: Enter the ZCHCH command again and specify a valid value for the HDR parameter.

See TPF Operations for more information about the ZCHCH command.

CRZ10014ECHAIN CHASE - INCONSISTENT FILE ADDRESS AND HDR VALUE INPUT

Explanation: The ZCHCH command was entered with a file address and a value for the HDR parameter that do not coexist. If you specify a value of 4 for the HDR parameter, the specified file address must be a 4-byte file address or an 8-byte file address in 4x4 format. If you specify a value of 8 for the HDR parameter, the specified file address must be an 8-byte FARF6 address or an 8-byte file address in 4x4 format.

System Action: The command is rejected.

User Response: Enter the ZCHCH command again and specify a valid file address and HDR parameter value combination.

See TPF Operations for more information about the ZCHCH command.

CRZ10015ICHAIN CHASE-FORWARD

Explanation: This is the normal response to the ZCHCH command with the F parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZCHCH command and for an example of the informational display.

CSAV0000IOPERATION COMPLETE

Explanation: The ZDEBB command was entered and the requested function has been completed successfully.

System Action: None.

User Response: None.

CSAV0001EI/O ERROR -- OPERATION ABORTED

Explanation: The ZDEBB command was entered to do one of the following:

However, an input/output (I/O) error occurred.

System Action: The tape is positioned following the record that received the I/O error (or before the record if the operation was to shift the blocked tape backward).

User Response: None.

See TPF Operationsfor more information about the ZDEBB command.

CSAV0002ITAPEMARK DETECTED

Explanation: The ZDEBB command was entered to do one of the following:

However, the request was ended because a tapemark was detected.

System Action: The tape is positioned following the tapemark (or before the tapemark if the operation was to shift the blocked tape backward).

User Response: None.

See TPF Operations for more information about the ZDEBB command.

CSAV0003EINVALID ID

Explanation: The format of the ZDEBB command is not correct.

System Action: The ZDEBB command is rejected.

User Response: Do the following:

  1. Determine the correct format of the ZDEBB command.
  2. Enter the command again using the correct format.

See TPF Operations for more information about the ZDEBB command.

CSAV0004EINVALID FORMAT OR INPUT DATA

Explanation: The format of the ZDEBB command is not correct.

System Action: The ZDEBB command is rejected.

User Response: Do the following:

  1. Determine the correct format of the ZDEBB command.
  2. Enter the command again using the correct format.

See TPF Operations for more information about the ZDEBB command.

CSAV0005ESYSTEM CYCLING TO 1052 STATE OR GFS NOT ACTIVE

Explanation: An error occurred because the ZDEBB command was entered with the TD or TP parameter specified when the get file storage (GFS) facility was not active or before the TPF system was in 1052 state.

System Action: The command is rejected.

User Response: Do the following:

  1. Wait for the TPF system to cycle down.
  2. Cycle up the TPF system to or past computer room agent set (CRAS) state.
  3. Enter the ZDEBB command again and specify the TD or TP parameter.

See TPF Operations for more information about the ZDEBB command.

CSAV0006ETAPE NOT MOUNTED

Explanation: An error occurred while entering the ZDEBB command because the DBL tape was not mounted.

System Action: The ZDEBB command is rejected.

User Response: Do the following:

  1. Enter the ZTMNT command to mount the DBL tape.
  2. Enter the ZDEBB command again.

See TPF Operations for more information about the ZDEBB and ZTMNT commands.

CSAV0007ETAPE IS IN USE BY ANOTHER ENTRY

Explanation: An error occurred while entering the ZDEBB command. The requested function cannot be performed on the specified device because the tape routines are already using that device.

System Action: The ZDEBB command is rejected.

User Response: Do the following:

  1. Wait for the routines that are currently using the specified device to complete processing.
  2. Enter the ZDTAP command to determine if you have to enter the ZDEBB command.
  3. Enter the ZDEBB command again and specify the same device or a different device.

See TPF Operations for more information about the ZDEBB and ZDTAP commands.

CSAV0007ETAPE NOT BLOCKED

Explanation: An error occurred while entering the ZDEBB command because the tape is not blocked.

System Action: The ZDEBB command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZDEBB and ZDEBE commands.

CSAW0000Ixxxxxxxxxx

Where:

xxxxxxxxxx
The record being displayed.

Explanation: This is the normal response to the ZDEBB command with one of the display and print tape block parameters specified.

System Action: The record is displayed.

User Response: None.

See TPF Operations for more information about the ZDEBB command.

CSD40001Wxx ADDITIONAL comd COMMAND(S) WERE REJECTED WITH code FOLLOWING ARE THE NAU NAMES: nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau

Where:

xx
The number of additional commands that generated the same negative response.

comd
The command that generated the negative response.

code
The negative response.

nau
The name of the network addressable unit (NAU) that received this negative response.

Explanation: The TPF system received the same command and negative response more than one time as specified in the message. The first time this pair (the command and negative response) is received, a message is sent to the terminal, dump, or both. The time between that and when this message is issued depends on the value set in the SNSETO field of keypoint 2.

System Action: The NAUs that received this negative response are processed normally.

User Response: If the cause of the negative response is unknown, you should determine the cause of the error.

See TPF ACF/SNA Network Generation for more information.

CSD40002Wxx ADDITIONAL comd COMMAND(S) WERE RECEIVED FOLLOWING ARE THE NAU NAMES: nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau nau

Where:

xx
The number of additional commands received.

comd
The command.

nau
The name of the network addressable unit (NAU) that received this command.

Explanation: The TPF system received the same command more than one as specified in the message. This message is issued only for commands that end a process or function. The first time this command is received, a message is sent to the terminal, dump, or both. The time between that and when this message is issued depends on the value set in the SNSETO field of keypoint 2.

System Action: The NAUs that received this negative response are processed normally.

User Response: If the cause of the negative command is unknown, you should determine the cause of the error.

See TPF ACF/SNA Network Generation for more information.

CSG00000IFRESH LOAD OF SNA TABLES COMPLETED

Explanation: Initialization of the SNA core records completed. Tables were built and filed.

System Action: None.

User Response: None.

CSG00001ESRT LOAD FAILURE - RVT2/SRT RESYNC. BEGUN

Explanation: It was discovered during a non-fresh load of the SNA tables that the system recovery table (SRT):

System Action: The SRT is rebuilt and the SRT indicators are removed from the RVT2.

User Response: None.

CSG00002IDYNAMIC LOAD OF SNA TABLES COMPLETED

Explanation: The SNA core records were updated dynamically to the current RRT definitions.

System Action: None.

User Response: None.

CSG00003INON-FRESH LOAD OF SNA TABLES COMPLETED

Explanation: SNA core records were determined to be current or were reloaded from the keypointed copy.

System Action: None.

User Response: None.

CSG00051ERDLR CURRENT LOAD TYPE INVALID, SNA RESTART BYPASSED

Explanation: During an IPL, it could not be determined from the Root Dynamic Load Record (RDLR) whether a Dynamic or Fresh Load was to be performed.

System Action: SNA restart is bypassed and the IPL is continued.

User Response: None.

CSG40050ERESTART ABORTED STATE CHANGE DISABLED

Explanation: A serious error occurred during SNA restart.

System Action: The TPF system aborts cycling to 1052 state.

User Response: See the previous error message issued for more information.

CSG40052EINSUFFICIENT NON-LU SPACE FOR FRESH LOAD, NUMBER OF NON-LUS NOT BEING LOADED - xx

Where:

xx
The number non-LU resources not being loaded.

Explanation: The size of the non-LU section in the resource vector table (RVT) is not large enough to load all of the adjacent link station (ALS), cross-domain resource manager (CDRM), channel-to-channel (CTC), and network control program (NCP) resources during the fresh load.

System Action: Processing continues.

User Response: Increase the size of the non-LU section in the RVT by increasing the value assigned to the NUMALS parameter in the SNAKEY macro.

See TPF ACF/SNA Data Communications Reference for more information about the SNAKEY macro.

CSG40053EI/O ERROR OCCURRED ON RETRIEVING NCB CONTROL RECORD, NCB DATABASE NOT AVAILABLE FOR DYNAMIC LU

Explanation: The TPF system could not initialize the node control block (NCB) database because an error occurred while retrieving the NCB control record.

System Action: Dynamic LU support is not enabled in the TPF system; that is, LU resources cannot log on to the TPF system unless they are defined using the offline ACF/SNA table generation (OSTG) program.

User Response: See your system programmer for more information.

See TPF ACF/SNA Data Communications Reference for more information about dynamic LU support and the NCB control record.

CSG40054WFRESH LOAD FORCED DUE TO NUMALS BEING CHANGED

Explanation: A fresh load was performed because the value assigned to the NUMALS parameter in the SNAKEY macro was increased. Increasing the value assigned to the NUMALS parameter increases the size of the non-LU section in the resource vector table (RVT).

System Action: The TPF system performs a fresh load.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about fresh loads. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.

CSG40055EFACS ERROR OCCURRED ON NCBN4, THIS SYSTEM IS RUNNING WITHOUT DYNAMIC LU SUPPORT

Explanation: A file address retrieval program (FACS) error occurred while locating an NCBN4 record because no NCBN4 records were defined for the TPF system.

System Action: Dynamic LU support is not enabled in the TPF system; that is, LU resources cannot log on to the TPF system unless they are defined using the offline ACF/SNA table generation (OSTG) program.

User Response: See your system programmer for more information.

See TPF ACF/SNA Data Communications Reference for more information about dynamic LU support.

CSG50001IRVT1 CORE COPY REUSED

Explanation: It was determined that the content of the core copy of the RVT1 is still valid across the software IPL. The core copy will be used instead of refreshing it from file.

System Action: None.

User Response: None.

CSG50002IRVT1 RELOADED FROM FILE

Explanation: On a hardware IPL or an irrecoverable software IPL where the content of the core copy could not be validated, the RVT1 is reloaded from file.

System Action: None.

User Response: None.

CSG50003IRVT2 CORE COPY REUSED

Explanation: It was determined that the content of the core copy of the RVT2 is still valid across the software IPL. The core copy will be used instead of refreshing it from file.

System Action: None.

User Response: None.

CSG50004IRVT2 RELOADED FROM FILE

Explanation: On a hardware IPL or an irrecoverable software IPL where the content of the core copy could not be validated, the RVT2 is reloaded from file.

System Action: None.

User Response: None.

CSG50005ISAT CORE COPY REUSED

Explanation: It was determined that the content of the core copy of the subarea address table (SAT) is still valid across the software IPL. The core copy will be used instead of refreshing it from file.

System Action: None.

User Response: None.

CSG50006ISAT RELOADED FROM FILE

Explanation: On a hardware IPL or an irrecoverable software IPL where the content of the core copy could not be validated, the subarea address table (SAT) is reloaded from file.

System Action: None.

User Response: None.

CSG60007ISRT CORE COPY REUSED

Explanation: It was determined that the content of the core copy of the system recovery table (SRT) is still valid across the software IPL. The core copy will be used instead of refreshing it from file.

System Action: None.

User Response: None.

CSG60008ISRT RELOADED FROM FILE

Explanation: On a hardware IPL or an irrecoverable software IPL where the content of the core copy could not be validated, the system recovery table (SRT) is reloaded from file.

System Action: None.

User Response: None.

CSG60009ENO AVAILABLE SRT SLOTS IN THE SYSTEM RECOVERY TABLE; RECOVERABLE MESSAGES WILL BE LOST; SRT AND RVT RE-SYNCHRONIZATION WILL BE INITIATED BY SNA RESTART

Explanation: On a hardware IPL, a software IPL or an irrecoverable software IPL, when it is determined that no system recovery table (SRT) slots are available on cycling the TPF system to NORM state, the SRT and resource vector table (RVT) are synchronized again.

System Action: The following information is lost:

This message is followed by a OPR-4A9 dump with the appended text of NO AVAILABLE SLOTS IN SR0RT.

User Response: Do one of the following:

CSG70001ENAT RID CONFLICT -- xxxx IN USE, yyyy SKIPPED

Where:

xxxx
The resource identifier (RID) of the network address table (NAT) entry in use.

yyyy
The RID of the resource to be added.

Explanation: When initializing the network address table (NAT), an attempt is made to add a network address that is already in use by another resource.

System Action: The resource to be added is skipped and processing is continued with the next resource.

User Response: Using the RIDs provided, the resource definitions should be reviewed to determine why the conflict occurred.

CSG70050ETHE PSV NAMES BELOW WERE GENNED BUT ARE NOT ONLINE psv psv psv psv psv psv psv psv psv psv psv psv psv psv psv psv psv psv psv psv psv psv psv psv psv psv psv psv

Where:

psv
The process selection vector (PSV) name. The display can contain a maximum of four lines with a maximum of seven names in each line.

Explanation: The PSV names generated by the offline ACF/SNA table generation (OSTG) were not defined in COBU.

System Action: None.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about the process selection vector (PSV).

CSGB0001ECIOSC MOUNT ERROR - SDA xxxx NOT DEFINED

Where:

xxxx
The symbolic device address (SDA).

Explanation: An attempt was made to mount an ALS/NCP that was indicated as active in the resource vector table (RVT) but the TPF system returned a SDA not defined indicator.

System Action: The current RVT entry is skipped and processing is continued with the next ALS/NCP.

User Response: Review the IOCP and the RVT entry to determine why the SDA conflict occurred.

CSGB0002IAUTOMATIC NETWORK SHUTDOWN OF xxxxxxxx COMPLETE

Where:

xxxxxxxx
The network control program (NCP) name.

Explanation: Following a hardware IPL, a DISCONNECT was issued to each active FID4 NCP.

System Action: An automatic network shutdown occurred.

User Response: Restart the network.

CSGC0001IXID ERROR. LOST TERMINAL CLEANUP INVOKED.

Explanation: An error was detected on completion of a non-activation exchange ID (XID) issued to restart an adjacent link station (ALS) by the CSGB segment. The CSEJ segment was entered to perform lost terminal cleanup processing.

System Action: None.

User Response: None.

CSGC0002INCP SENSE ERROR. LOST TERMINAL CLEANUP INVOKED.

Explanation: An error was detected on completion of a network control program (NCP) sense issued to restart an NCP by the CSGB segment. The CSEJ segment was entered to perform lost terminal cleanup processing.

System Action: None.

User Response: None.

CSGH0001IRTPCB BUILT AND FILED

Explanation: This message is displayed during Systems Network Architecture (SNA) restart after the rapid transport protocol control block (RTPCB) table is built and filed.

System Action: None.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about the RTPCB table.

CSGH0002IRTPCB CORE COPY REUSED

Explanation: This message is displayed when the core copy of the rapid transport protocol control block (RTPCB) table is valid and used again during a nonfresh load of the Systems Network Architecture (SNA) tables.

System Action: None.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about the RTPCB table.

CSGH0003IRTPCB RELOADED FROM FILE

Explanation: This message is displayed when the rapid transport protocol control block (RTPCB) table is loaded again from file during a nonfresh load of the Systems Network Architecture (SNA) tables.

System Action: None.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about the RTPCB table.

CSGI0001IDYNAMIC LOAD OF RVT1/RVT2 COMPLETE

Explanation: A dynamic load of RVT1/RVT2 completed during SNA restart.

System Action: None.

User Response: None.

CSGJ0001IHPRMT INITIALIZED

Explanation: This message is displayed during Systems Network Architecture (SNA) restart after the high-performance routing message table (HPRMT) is initialized.

System Action: None.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about the HPRMT.

CSGJ0002IHPRMT CORE COPY REUSED

Explanation: This message is displayed when the core copy of the high-performance routing message table (HPRMT) is valid and used again during a nonfresh load of the Systems Network Architecture (SNA) tables.

System Action: None.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about the HPRMT.

CSGJ0003IHPR OUTPUT MESSAGE DELIVERY NOT GUARANTEED

Explanation: The size of the high-performance routing message table (HPRMT) is 0; therefore, output messages for high-performance routing (HPR) LU-LU sessions will not be saved. If the TPF system is requested to retransmit a message, the rapid transport protocol (RTP) connection will be deactivated.

System Action: None.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about RTP connections and the HPRMT.

CSIO0001E 

Explanation: This explanation is for the messages with headers beginning with: CSIO, CINP, COUT, CCTL, CTRM, and CHIO.

Communication line error messages contain a header to indicate the type of operation as follows.

CSIO
An error on the SIO instruction.

CINP
An error detected at interrupt time on input operation.

COUT
An error detected at interrupt time on output operation.

CCTL
A control operation error.

CTRM
An external hardware error.

CHIO
An error on an HIO instruction.

Each header is followed by error information as the following describes.

HSxx
CTL SUBxx OPxx error-text

LSxx
FDX TIAxx error-text

ARxx
HXA TSCxx error-text

AIxx
HXN TAxx error-text

BSxx
SOA

LCxx
SON

 
SIA

 
SIN

The error text is one of the following:

CSWxxxxxxxx SNSxx CCx DOWN LOST DATA - DOWN REPEATED CHARACTER DOWN NEGATIVE ANSWR-BACK DOWN MAIN SIDE DOWN MONITOR SIDE DOWN SP UP POLL RCVD

Note:
Error data that is not available is printed as *; for example, SNS**.

Where:

HSxx
The high-speed symbolic line number.

LSxx
The low-speed symbolic line number (controlled and free-running).

ARxx
The ARINC symbolic line number.

AIxx
The synchronous Link symbolic line number.

BSxx
The binary synchronous communication (BSC) symbolic line number.

LCxx
The local 3270 Line Number.

CTL
The controlled line.

FDX
The full-duplex (free-running line).

HXA
The half-duplex with answerback (Free-running line).

HXN
The half-duplex (free-running line).

SOA
The simplex-out with answerback (free-running line).

SON
The simplex-out (free-running line).

SIA
The simplex-in with answerback (free-running line).

SIN
The simplex-in.

SUBxx
The subchannel number.

OPxx
The operation code in CCW.

TIAxx
The terminal interchange address.

TSC
The transmitter start code.

STAxx
The station identification.

CSWx..x
The eight bytes from CSW.

SNSxx
The sense data.

CCx
The condition code resulting from SIO.

DOWN
If a line, interchange, or terminal is shut down by the control program.

SP UP
If a terminal or interchange is reinstated to normal polling.
Example:
14.23.16 COUT HS05 CTL SUB63 OP01
CSW10049DD80E000005 SNS40 CC2 DOWN

System Action: None.

User Response: None.

CSMP0097ICPU-id SS-ssname SSU-ssuname IS-isnum

Where:

id
The CPU ID.

ssname
The subsystem name.

ssuname
The subsystem user (SSU) name.

isnum
The I-stream, which is displayed as a decimal number.

Explanation: This message precedes all messages in TPF systems that have prefix messaging generated in the TPF system. Prefix messaging is included in the TPF system by specifying YES in the PREMSG parameter to the SIP stage I CONFIG macro. The default is PREMSG=YES.

If the CSMP0097I message is generated on a base-only TPF system, then the subsystem name and SSU name are defined as the character string BASE.

System Action: None.

User Response: None.

CSMP0098IRESTRICTED MESSAGE ENTERED -- TERM. NOT AUTHORIZED

Explanation: The terminal that input the command is not authorized to perform that function.

System Action: None.

User Response: Do one of the following:

See TPF Operations for more information about the ZACRS command.

CSMP0099ILNIATA-CPU-ID command

Where:

ID
The central processing unit (CPU) ID.

command
The command entered.

Explanation: All input is echoed to the appropriate functional support consoles (FSCs), providing a contiguous account of system activity within functional areas.

Note:
If no loosely coupled TPF system is generated in the TPF system, the CPU ID is omitted.

System Action: None.

User Response: None.