gtpm5m10Messages (Online)

CSNA-CTIN

CSNA0011EREQUIRED BLANK MISSING AFTER ACTION CODE

Explanation: A SNA command was entered that requires a blank following the five-character action code, for example, after ZNETW. The required blank is missing.

System Action: None.

User Response: Enter the command again with the required blank between the action code and the following message parameters.

See TPF Operations for more information about the SNA communication commands.

CSNA0012EILLEGAL FUNCTION -- NO LINKAGE FOUND

Explanation: A command that is not valid was entered beginning with ZN.

System Action: None.

User Response: Do the following:

  1. Verify the spelling of the action code.
  2. Enter the command again with the correct action code.

See TPF Operations for more information about the SNA communication commands.

CSNA0013EI/O HARDWARE ERROR DURING CSN0 SNA MESSAGE TABLE RETRIEVAL

Explanation: A SNA command was entered but an input/output (I/O) error occurred when the SNA command editor CSNA attempted to retrieve the SNA command table (CSN0). The SNA command cannot be processed.

System Action: A file error message is sent to the prime computer room agent set (CRAS) console and CSNA is exited.

User Response: Do the following:

  1. Inform the operator of the prime CRAS console so the operator can check for the file error message.
  2. When the hardware problem is corrected, you may enter the command again.

See TPF Operations for more information about the SNA communication commands.

CSNB0001ECURRENT NCB DIRECTORY RECORD, ORDINAL ordnum IS FULL

Where:

ordnum
The ordinal number of the current node control block (NCB) directory record.

Explanation: An NCB record cannot be created for the resource because the specified current NCB directory record is full.

System Action: None.

User Response: Enter the ZNNCB REORG command to increase the number of NCB directory records in the TPF system.

See TPF Operations for more information about the ZNNCB REORG command.

CSNB0002ICURRENT NCB DIRECTORY RECORD, ORDINAL ordnum IS 90 PERCENT FULL

Where:

ordnum
The ordinal number of the current node control block (NCB) directory record.

Explanation: The TPF system determined that the specified current NCB directory record is becoming full.

System Action: The TPF system starts the NCB reconciliation function for the specified current NCB directory record to reclaim the entries that are no longer being used.

User Response: Determine if you should reorganize the NCB directory records at this time.

See TPF ACF/SNA Data Communications Reference for more information about the NCB reconciliation and NCB reorganization functions.

CSNB0003ESTAGED NCB DIRECTORY RECORD, ORDINAL ordnum IS FULL

Where:

ordnum
The ordinal number of the staged node control block (NCB) directory record.

Explanation: The TPF system tried to create a new NCB record for a resource while the NCB reorganization function was running. However, the NCB record cannot be created for the resource because the specified staged NCB directory record is full.

System Action: The NCB reorganization function ends.

User Response: Do the following:

  1. Increase the number of staged NCB directory records in the TPF system.
  2. Enter the ZNNCB REORG command to start the NCB reorganization function again.

See TPF ACF/SNA Data Communications Reference for more information about the staged NCB directory records and the NCB reorganization function. See TPF Operations for more information about the ZNNCB REORG command.

CSNB0004ISTAGED NCB DIRECTORY RECORD, ORDINAL ordnum IS 90 PERCENT FULL

Where:

ordnum
The ordinal number of the staged node control block (NCB) directory record.

Explanation: The TPF system created a new NCB record for a resource while the NCB reorganization function was running and determined that the specified staged NCB directory record is becoming full.

System Action: None.

User Response: See your system administrator for more information.

See TPF ACF/SNA Data Communications Reference for more information about the NCB reconciliation and NCB reorganization functions.

CSNB0005INCB DATABASE SWITCHED IN THIS PROCESSOR

Explanation: This processor updated the node control block (NCB) database information in its resource name hash control table (RNHCT) because it detected that the NCB database was switched on another processor in the loosely coupled TPF system.

System Action: None.

User Response: None.

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

CSON0002IFARF ADDRESS IS address

Where:

address
The 16-digit hexadecimal file address.

Explanation: This is the normal response to the ZCSON command. The module, cylinder, head and record (MCHR) address specified in the command is converted and displayed as a file address reference format (FARF) address.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZCSON command.

CSON0052EMCHR OUTSIDE SYSTEM LIMITS

Explanation: The ZCSON command was entered, but the module, cylinder, head and record (MCHR) address specified was not converted to a valid file address reference format (FARF) address because it exceeds the defined database range.

System Action: The command is rejected.

User Response: Enter the ZCSON command again and specify a valid MCHR address.

See TPF Operations for more information about the ZCSON command.

CSON0053EINPUT MCHR IS NOT 7-BYTES IN LENGTH

Explanation: A ZCSON command was entered with a module, cylinder, head, and record (MCHR) address specified that was not 14 digits (7 bytes) in length.

System Action: The command is rejected.

User Response: Enter the ZCSON command again and specify a 14-digit MCHR address.

See TPF Operations for more information about the ZCSON command.

CSON0054EINPUT RECORD TYPE IS NOT VALID

Explanation: A ZCSON command was entered with a record type value specified that was not F (for fixed) or P (for pool).

System Action: The command is rejected.

User Response: Enter the ZCSON command again and specify either F or P for the record type value.

See TPF Operations for more information about the ZCSON command.

CSS00001IRCS RESTART STARTED

Explanation: The TPF restart scheduler performed an ENTRC to the record caching subsystem restart program.

System Action: The record cache subsystem (RCS) restart program begins processing.

User Response: None.

CSS00002IRCS RESTART COMPLETED

Explanation: The record caching subsystem (RCS) restart program performed a BACKC to the TPF restart scheduler.

System Action: TPF restart is continued.

User Response: None.

CSS00020AISSUE ZBUFC ALLOCATE INIT MESSAGE TO RE-ESTABLISH CURRENT RECORD SLOT ALLOCATION RATIOS

Explanation: The record slot allocations for the record cache subsystems (RCSs) in the complex were lost. These values are used to verify that the RCSs are initialized properly.

System Action: The TPF system waits for you to specify the proper record slot allocations for the RCSs. After you provide the valid allocations, RCS restart processing is continued.

User Response: Enter the ZBUFC ALLOCATE command to respecify record slot allocation ratios for the RCSs in the complex.

See TPF Operations for more information about the ZBUFC ALLOCATE command.

CSS00040WRCS SSST HEADER RETRIEVAL ERROR-- POTENTIAL DATA LOSS CONDITIONS FOR THIS IPL CAN NOT BE REPORTED

Explanation: The record cache subsystem (RCS) restart program detected a record ID failure while trying to retrieve the subsystem status table (SSST) header record from file. This indicates that:

Note:
This occurs for the first processor in the complex.

System Action: the CSS020A message is issued and waits for you to provide the proper record slot allocations for the RCSs in the complex through the ZBUFC ALLOCATE INIT command. The remainder of the SSST is reconstructed using current hardware status.

User Response: None.

CSS00041WFAST WRITE DISABLE REQUESTED FOR RCS COMPLEX DUE TO ZBUFC FILE ALL REQUEST -- ISSUE ZBUFC ENABLE ALL TO RE-ENABLE

Explanation: A ZBUFC FILE command was entered to destage the record cache subsystem (RCS) cache memories prior to this IPL.

System Action: RCS restart processing is continued.

User Response: Enter the ZBUFC ENABLE command to re-enable the RCS complex caching operations.

See TPF Operations for more information about the ZBUFC commands.

CSS00042WZBUFC FILE DID NOT COMPLETE ON THIS PROCESSOR

Explanation: An outage occurred on this processor while a ZBUFC FILE command was being processed.

System Action: Record cache subsystem (RCS) restart processing is continued.

User Response: Enter the ZBUFC FILE command again.

See TPF Operations for more information about the ZBUFC FILE command.

CSS00043WZBUFC ALLOCATE IMPLEMNT RCS DID NOT COMPLETE ON THIS PROCESSOR

Explanation: An outage occurred on this processor while a ZBUFC ALLOCATE IMPLEMNT command was being processed.

System Action: Record cache subsystem (RCS) restart processing is continued.

User Response: Enter the ZBUFC ALLOCATE IMPLEMNT command again.

See TPF Operations for more information about the ZBUFC ALLOCATE IMPLEMNT command.

CSS00044WZBUFC ENABLE DID NOT COMPLETE ON THIS PROCESSOR

Explanation: An outage occurred on this processor while a ZBUFC ENABLE command was being processed.

System Action: Record cache subsystem (RCS) restart processing is continued.

User Response: Enter the ZBUFC ENABLE command again.

See TPF Operations for more information about the ZBUFC ENABLE command.

CSS00045WZBUFC FILE FUNCTION PENDING

Explanation: One of the other processors in the loosely coupled complex is processing a ZBUFC FILE command.

System Action: Record cache subsystem (RCS) restart processing is continued.

User Response: None.

See TPF Operations for more information about the ZBUFC FILE command.

CSS00046WZBUFC ALLOCATE IMPLEMNT RCS FUNCTION PENDING

Explanation: One of the other processors in the loosely coupled complex is processing a ZBUFC ALLOCATE IMPLEMNT command.

System Action: Record cache subsystem (RCS) restart processing is continued.

User Response: None.

See TPF Operations for more information about the ZBUFC ALLOCATE IMPLEMNT command.

CSS00047WZBUFC ENABLE FUNCTION PENDING

Explanation: One of the other processors in the loosely coupled complex is processing a ZBUFC ENABLE command.

System Action: Record cache subsystem (RCS) restart processing is continued.

User Response: None.

See TPF Operations for more information about the ZBUFC ENABLE command.

CSS00080TERROR RETRIEVING RCS SSST -- RESTART ABORTED

Explanation: A hardware error or logic error was found while trying to retrieve the subsystem status table (SSST) header record from file.

Note:
This error occurs on all processors except the first one in the complex.

System Action: The TPF restart scheduler is exited.

User Response: See your IBM service representative.

CSS00081TERROR FILING RCS SSST -- RESTART ABORTED

Explanation: A hardware error or logic error was found while trying to write the subsystem status table (SSST) header record to file.

System Action: The TPF restart scheduler is exited.

User Response: See your IBM service representative.

CSS00084TFIND ERROR RETRIEVING KEYPOINT 0 -- RESTART ABORTED

Explanation: A hardware error or logic error was found while trying to retrieve keypoint 0 from file.

System Action: The TPF restart scheduler is exited.

User Response: See your IBM service representative.

CSS10048WNO DASD CONFIGURED ON RCS SSID ssss -- SUBSYSTEM HAS BEEN REMOVED FROM THE COMPLEX

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: No modules in the MFST were found to be attached to the specified record cache subsystem (RCS)

System Action: The subsystem status table (SSST) entry for the specified subsystem is deleted.

User Response: None.

CSS10049WFILE SSST ENTRY CONFLICT DETECTED FOR RCS SSID ssss --

Where:

ssss
Represents a 3990 record cache subsystem (RCS) subsystem ID (SSID).

Explanation: An SSID entry was created prior to RCS restart that used a memory subsystem status table (SSST) entry position different than the file copy of the SSST. Symmetry must be maintained between the file and memory copies of the SSST for RCS support to correctly report potential data loss conditions due to configuration changes between IPLs of the TPF system. RCS restart accommodates the configuration change and rebuilds the file SSST at the completion of processing.

System Action: The SSST is rebuilt at the end of RCS restart to reflect the configuration change. Potential data loss condition reporting is ended for this IPL.

User Response: None.

CSS10080TERROR RETRIEVING RCS SSST - RESTART ABORTED

Explanation: A hardware error or logic error was found while trying to retrieve one of the subsystem status table (SSST) records from file.

System Action: The TPF restart scheduler is exited.

User Response: See your IBM service representative.

CSS20003IRCS SSID ssss HAS BEEN ADDED TO THE COMPLEX

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: During construction of the subsystem status table (SSST), a new RCS SSID was returned in response to a sense subsystem status command.

System Action: An entry for this RCS is added to the SSST.

User Response: None.

CSS30050WFOLLOWING MODS HAVE POTENTIAL DATA LOSS FROM CACHE FOR SS tpf-ss

Where:

tpf-ss
Represents a TPF subsystem name.

Explanation: The record cache subsystem (RCS) returned from the sense subsystem status command does not agree with the SSID maintained in the MFST entry for one or more DASD attached to the specified record cache subsystems (RCSs) This indicates that a configuration change took place, that is, a group of DASD previously attached to a given RCS was switched to another RCS or another non-RCS controller.

The cache storage for the old RCS may not have been completely destaged before the substitution occurred. Therefore, data in the old subsystem cache may have been lost.

System Action: The TPF system issues the RSTT0004A message requesting your permission to write the updated version of the module verification table (MVT) with the updated SSID value for the specified DASD modules.

User Response: None.

CSS30051WPOSSIBLE CACHE FAST WRITE DATA LOSS FOR RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the cache fast-write ID (CFWID) in the specified RCS subsystem was incremented since the last IPL. This means that any cache fast-write data not written to disk at the time the CFWID was changed may have been lost.

System Action: The file-resident subsystem status table (SSST) entry is refreshed with the new CFWID.

User Response: See your IBM service representative.

CSS40085TFACE ERROR RETRIEVING RCS SSST DATA BLOCK -- RESTART ABORTED

Explanation: A file address compute program (FACE) error was found during an attempt to retrieve the first subsystem status table (SSST) data block from file for the purpose of rebuilding it.

System Action: The TPF restart scheduler is exited.

User Response: See your IBM service representative.

CSS60028WNONVOLATILE STORAGE BATTERY DEFECTIVE ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS cannot be fully enabled due to a defective nonvolatile storage battery.

System Action: RCS restart processing is continued with RCS queue thresholding active for the affected subsystem.

User Response: See your IBM service representative.

CSS60029ACACHING TERMINATED ON RCS SSID ssss DUE TO SUBSYSTEM STORAGE MALFUNCTION

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS cannot be fully enabled due to an internal subsystem error condition.

System Action: RCS restart processing is continued with RCS queue thresholding active for the affected subsystem.

User Response: See your IBM service representative.

CSS60030ADASD FAST WRITE TERMINATED ON RCS SSID ssss DUE TO NONVOLATILE STORAGE MALFUNCTION

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS cannot be fully enabled due to an internal nonvolatile storage error condition.

System Action: RCS restart processing is continued with RCS queue thresholding active for the affected subsystem.

User Response: See your IBM service representative.

CSS60052WSUBSYSTEM STATUS CONFLICT ON RCS SSID ssss -- SUBSYSTEM NOT DISABLED FOR FAST WRITE FUNCTIONS

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A conflict exists between the hardware status for a particular RCS and the software status in the subsystem status table (SSST) entry for the subsystem. The software status indicates that the subsystem was destaged through a previous ZBUFC FILE request. However, the hardware status indicates that fast-write functions are still active.

System Action: None.

User Response: Enter the ZBUFC FILE command again, if required.

See TPF Operations for more information about the ZBUFC FILE command.

CSS60053WCACHING DEACTIVATED ON RCS SSID ssss DUE TO EXPLICIT HOST REQUEST

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS is not fully enabled due to a host request to end caching.

System Action: RCS restart processing is continued with RCS queue thresholding active for the affected subsystem.

User Response: Enter the ZBUFC ENABLE command to re-enable the RCS subsystem for caching, if required.

See TPF Operations for more informationa bout the ZBUFC ENABLE command.

CSS60054WCACHE FAST WRITE DEACTIVATED ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS is not fully enabled due to termination of the cache fast-write function.

System Action: RCS restart processing is continued with RCS queue thresholding active for the affected subsystem.

User Response: Enter the ZBUFC ENABLE command to re-enable the RCS subsystem for cache fast-write functions, if required.

See TPF Operations for more information about the ZBUFC ENABLE command.

CSS60055WNONVOLATILE STORAGE DEACTIVATED ON RCS SSID ssss DUE TO EXPLICIT HOST REQUEST

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS is not fully enabled due to a host request to end use of nonvolatile cache capability.

System Action: RCS restart processing is continued with RCS queue thresholding active for the affected subsystem.

User Response: Enter the ZBUFC ENABLE command to re-enable the RCS subsystem for DASD fast-write capability, if required.

See TPF Operations for more information about the ZBUFC ENABLE command.

CSS60056WALLOCATION RATIOS NOT CURRENT FOR RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The record slot allocation ratios for the specified RCS do not match those designated for the RCS complex in the subsystem status table (SSST) header. This message is generated by the RCS restart program if the executing processor is not the first processor in the loosely coupled configuration.

System Action: None.

User Response: Enter the ZBUFC ALLOCATE command with the IMPLEMNT parameter specified to reset the allocation ratios to the desired values.

See TPF Operations for more information about the ZBUFC ALLOCATE command.

CSS60057WFAST WRITE DISABLE REQUESTED FOR RCS SSID ssss DUE TO ZBUFC FILE REQUEST -- ISSUE ZBUFC ENABLE TO RE-ENABLE

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A ZBUFC FILE command was entered to destage the specified record cache subsystem (RCS) prior to this IPL.

System Action: RCS restart processing is continued.

User Response: Enter the ZBUFC ENABLE command to re-enable caching operations, if desired.

See TPF Operations for more information about the ZBUFC ENABLE command.

CSS60058WCACHING DEACTIVATED FOR DEVICE dddd RCS SSID ssss

Where:

dddd
Represents a 3990 Record Cache Subsystem (RCS) device address.

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS is not fully enabled because caching functions for the device specified in the message were ended.

System Action: RCS restart processing is continued with RCS queue thresholding active for the affected subsystem.

User Response: Enter the ZBUFC ENABLE command to re-enable the device for caching functions, if required.

See TPF Operations for more information about the ZBUFC ENABLE command.

CSS60059WDASD FAST WRITE DEACTIVATED FOR DEVICE dddd RCS SSID ssss

Where:

dddd
Represents a 3990 Record Cache Subsystem (RCS) device address.

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS is not fully enabled because DASD fast-write functions for the device specified in the message were ended.

System Action: RCS restart processing is continued with RCS queue thresholding active for the affected subsystem.

User Response: Enter the ZBUFC ENABLE command to re-enable the device for DASD fast-write capability, if required.

See TPF Operations for more information about the ZBUFC ENABLE command.

CSS60060WRECORD MODE DISALLOWED FOR DEVICE dddd RCS SSID ssss

Where:

dddd
Represents a 3990 Record Cache Subsystem (RCS) device address.

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS is not fully enabled since the device specified in the message is not allowed to perform record mode operations.

System Action: RCS restart processing is continued with RCS queue thresholding active for the affected subsystem.

User Response: Enter the ZBUFC ENABLE command to re-enable the device for record mode operations, if required.

See TPF Operations for more information about the ZBUFC ENABLE command.

CSS60061WCACHING DEACTIVATION FAILURE ON RCS SSID ssss -- DESTAGE FAILED

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS could not be fully enabled since a prior deactivation request failed. Pinned fast-write data may be present in the subsystem.

System Action: RCS restart processing is continued with RCS queue thresholding active for the affected subsystem.

User Response: Do the following:

  1. Perform the necessary steps to clear any pinned data conditions.
  2. Request the deactivation again, if required.

CSS60062WSUBSYSTEM STORAGE DISABLED FOR MAINTENANCE ON SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS cannot be fully enabled.

System Action: None.

User Response: See your IBM service representative.

CSS60063WIML DEVICE NOT AVAILABLE ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the initial machine load (IML) device is not available on the specified record cache subsystem (RCS).

System Action: None.

User Response: See your IBM service representative.

CSS60064WNONVOLATILE STORAGE DISABLED FOR MAINTENANCE ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS cannot be fully enabled.

System Action: None.

User Response: See your IBM service representative.

CSS60065WNONVOLATILE STORAGE DEACTIVATION FAILURE ON RCS SSID ssss -- DESTAGE FAILED

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS cannot be fully enabled since a prior deactivation request failed. Pinned fast-write data may be present in the subsystem.

System Action: RCS restart processing is continued with RCS queue thresholding active for the affected subsystem.

User Response: Perform steps necessary to clear any pinned data conditions and request deactivation again if required.

CSS60066WDEACTIVATE PENDING FOR DEVICE dddd RCS SSID ssss UNABLE TO TRANSFER MODIFIED DATA TO DISK

Where:

dddd
Represents a 3990 Record Cache Subsystem (RCS) device address.

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS could not be fully enabled since a prior deactivation request failed. Pinned fast-write data may be present in the subsystem.

System Action: RCS restart processing is continued with RCS queue thresholding active for the affected subsystem.

User Response: Do the following:

  1. Perform the necessary steps to clear any pinned data conditions.
  2. Request the deactivation again, if required.

CSS60067WDASD FAST WRITE DEACTIVATE PENDING FOR DEVICE dddd RCS SSID ssss UNABLE TO TRANSFER MODIFIED DATA TO DISK

Where:

dddd
Represents a 3990 Record Cache Subsystem (RCS) device address.

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS could not be fully enabled since a prior deactivation request failed. Pinned fast-write data may be present in the subsystem.

System Action: RCS restart processing is continued with RCS queue thresholding active for the affected subsystem.

User Response: Do the following:

  1. Perform the necessary steps to clear any pinned data conditions.
  2. Request the deactivation again, if required.

CSS60068WFAST WRITE FUNCTIONS SUSPENDED ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The RCS restart program determined that the specified RCS is not fully enabled because fast-write functions are suspended in the subsystem.

System Action: RCS restart processing is continued with RCS queue thresholding active for the affected subsystem.

User Response: Enter the ZBUFC ENABLE command to the affected RCS subsystem to resume fast-write operations.

See TPF Operations for more information about the ZBUFC ENABLE command.

CSS60083WUNRECOGNIZED ALLOCATIONS FOR RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: The record slot allocation ratios for the specified RCS do not match those designated for the RCS complex in the subsystem status table (SSST) header.

System Action: None.

User Response: Enter the ZBUFC ALLOCATE command with the IMPLEMNT parameter specified to reset the slot allocation ratios to the desired values.

See TPF Operations for more information about the ZBUFC ALLOCATE command.

CS060001WPIU TRACE QUESCING. MAXIMUM TAPE QUEUE DEPTH EXCEEDED.

Explanation: The number of items currently in the real-time tape queue exceeds the value allowed for the path information unit (PIU) trace facility. This value is set through the PIUTAPEQ parameter in the SNAKEY macro and is displayed by entering the ZNKEY command.

The maximum tape queue value is 255.

System Action: The path information unit (PIU) trace facility temporarily stops writing to tape.

User Response: Do the following:

  1. Determine why the real-time tape queue is full. For example, another utility may be writing to the real-time tape or a dump may have occurred.
  2. Do one of the following:

See TPF Operations for more information about the ZNKEY command. See TPF ACF/SNA Data Communications Reference for more information.

CTIN0004EPROGRAM CHECK IN INITIALIZATION -- ABORTED

Explanation: A program check occurred in CCCTIN. An attempt is made to display the contents of the general registers and program old PSW.

System Action: The TPF system is put into disabled wait state immediately.

If the program check occurred in either the dump routine or the system console write routine, no attempt is made to issue an error message or to display the registers and program old PSW.

User Response: Do the following:

  1. Determine why the program check occurred.
  2. Correct the error.
  3. IPL the TPF system again.

CTIN0008E--INVALID CPU ID -- CTIN ABORTED

Explanation: This may be a hardware error. The CPU model number read from the machine could not be found in the CPU ID table. A loop timing adjustment factor is adjusted depending on the CPU model. After entering this error message, the content of the general registers are displayed along with the program old PSW.

The CPU information is required for the TPF system to run.

System Action: The TPF system is put into disabled wait state immediately.

User Response: Do the following:

  1. Ensure the CPU model number is in the CPU ID table.
  2. Correct the error.
  3. IPL the TPF system again.

CTIN0010ECCCPSE STORAGE NOT VEQR -- CTIN ABORTED

Explanation: Due to TPF system changes, a hardware page in low memory is not mapped V=R.

System Action: The initializer ends. CCCPSE must reside in V=R storage.

User Response: Do the following:

  1. Determine the cause of the hardware failure.
  2. Correct the error.

CTIN0012ICT00 INIT STARTED

Explanation: The CT00 copy member completed successfully. The global areas were carved out and the pointers to the global areas were set up. The CINFC tables were carved out and several CINFC slots were filled in. The following information was moved to their permanent core location:

The message counter areas for data collection were carved out.

System Action: Initialization is continued.

User Response: None.

CTIN0013ISTIMER TABLE INIT DONE / CPU TIMER STARTED

Explanation: The system timer table was carved and initialized. The CPU timer is now active.

System Action: Initialization is continued.

User Response: None.

CTIN0014ICT01 TAPE TABLES ALLOCATED AND TSTB INIT

Explanation: the CT01 copy member CT01 completed successfully.

The CREATE macro controls were initialized. Several PSWs were set up. The start of working storage was determined. Keypoint B, keypoint 9, and keypoint M were moved to their permanent core locations. The tape status table was initialized. The tape control unit cross reference table was carved out. The general file volume serial number (VSN) table was moved to its permanent core location.

System Action: Initialization is continued.

User Response: None.

CTIN0015IINTERNAL EVENT FACILITY TABLE INIT DONE

Explanation: A call was made to the CP CCCIEF segment to carve out and initialize the internal event facility table.

System Action: The call completed successfully.

User Response: None.

CTIN0016ICT05 SON MFST & RCS TABLE INIT DONE

Explanation: The CT05 copy member completed successfully. The DASD control tables were initialized and table address pointers setup. These tables include:

System Action: Initialization is continued.

User Response: None.

CTIN0017EKEYPOINT ADDRESS ERROR -- CTIN ABORTED

Explanation: A file address compute program (FACE) error occurred while generating keypoint addresses.

System Action: CTIN is aborted.

User Response: To IPL this image, a new FACE table, a new CTKX record, or both should be loaded.

See TPF Main Supervisor Reference for more information.

CTIN0018ICT08 MPIF TABLE CREATION COMPLETE

Explanation: The Multi-Processor Interconnect Facility (MPIF) tables were carved out successfully. Pointers to the tables were stored into the Multi-Processor Interconnect Facility global table (MGT). (The DSECT name for the MGT is DCTMGT.)

System Action: CTIN processing is continued.

User Response: None.

CTIN0019ICT09 COMMIT/ROLLBACK ALLOCATION COMPLETE

Explanation: The CT09 copy member completed successfully. In addition, the areas required for TPF transaction services control tables and the recovery log buffer were allocated.

System Action: Initialization continues.

User Response: None.

CTIN0020ICT10 SON POOL CARVE COMPLETE

Explanation: The CT10 copy member completed successfully. The pool management global table and CINFC table pool entries were initialized and storage was allocated for the pool directory set control areas.

System Action: Initialization is continued.

User Response: None.

CTIN0024ICT15 SNA TABLE ALLOCATION COMPLETE

Explanation: The CT15 copy member completed successfully. In addition, the following occurred:

System Action: Initialization is continued.

User Response: None.

CTIN0025ICT15 WGTA ALLOCATION COMPLETE

Explanation: The CT15 copy member completed successfully. The WGTA was carved out.

System Action: Initialization is continued.

User Response: None.

CTIN0028ICT20 STORAGE RESERVED FOR CCP TABLES

Explanation: The CT20 copy member completed successfully. In addition, the following occurred:

System Action: Initialization is continued.

User Response: None.

CTIN0030ICT25/CT26 USER EXIT ACTIVATED

Explanation: The CT25 and CT26 copy members completed successfully. The CT25 copy member allows you to reserve storage for user tables or other unique structures that require reserved main storage. The CT26 copy member allocates storage for user storage resident tables through the use of the data supplied in the user storage allocation table (USAT) that is built by the CT25 copy member.

System Action: Initialization is continued.

User Response: None.

CTIN0036ICT40 CLH TABLES AND STORAGE BLOCKS BUILT

Explanation: The CT40 copy member completed successfully. The CT40 copy member carves out storage for the PNL table, the detached block table, all of the working storage blocks and their control structures, the ECB virtual memory (EVM) page and segment tables, the dispatch management table, the dispatch control record, and the dispatch control list.

If there is not enough working storage to satisfy all the block requests, the number of each type of block allocated is bumped down. A message warning you that there was not enough working storage is issued later in the IPL.

The maximum and minimum shutdown levels for the CPU loop are calculated, the Enter/Back nesting levels are determined, and the working storage protect keys are set.

System Action: Initialization is continued.

User Response: None.

CTIN0037ICT38 STACKS ALLOCATED

Explanation: The CT38 copy member completed successfully. The CT38 copy member carves out storage for:

The CT38 copy member also sets the storage protect keys from the end of the global area to the end of the SVM.

System Action: Initialization is continued.

User Response: None.

See TPF Main Supervisor Reference for more information about the system initializer (CCCTIN).

CTIN0038ICT41 MISCELLANEOUS TABLES BUILT

Explanation: The CT41 copy member completed successfully. The CT41 copy member accomplishes the following:

System Action: Initialization is continued.

User Response: None.

CTIN0040ICT50 VFA INIT DONE

Explanation: The CT50 copy member completed successfully. Pointers to virtual file access (VFA) areas were set up in the CINFC table, the dump formatter label table, and low core.

System Action: Initialization is continued.

User Response: None.

CTIN0044ICT60 CCP TABLE INIT DONE

Explanation: The CT60 copy member completed successfully. In addition, the following occurred:

System Action: Initialization is continued.

User Response: None.

CTIN0048ICT65 UNIT RECORD DEVICE TABLE INIT DONE

Explanation: The CT65 copy member completed successfully. If there are unit record devices in the TPF system, the unit record device status table is initialized from data in keypoint B. The entries in the branch vector table that correspond to unit record devices are initialized.

System Action: Initialization is continued.

User Response: None.

CTIN0052ICT66 3705 CONTROL TABLE INIT DONE

Explanation: The CT66 copy member completed successfully. The CCW pointer table was initialized for the IBM 3705.

System Action: Initialization is continued.

User Response: None.

CTIN0058ICT81 MACHINE CHECK INITIALIZATION COMPLETE

Explanation: The CT81 copy member completed successfully.

System Action: Initialization is continued.

User Response: None.

CTIN0059ICT85 I-STREAM INITIALIZATION COMPLETE

Explanation: The CT85 copy member completed successfully.

System Action: Initialization is continued.

User Response: None.

CTIN0060IINIT COMPLETE -- CTIN CALLING ACPL

Explanation: This message is issued upon completion of CCCTIN when IPLing from a general file. Control is then passed to ACPL.

System Action: Initialization is continued.

User Response: None.

CTIN0064IINIT COMPLETE -- CTIN CALLING RESTART

Explanation: This message is issued upon completion of CCCTIN when IPLing from an online module. Control is then passed to the CTKS segment to begin restart.

System Action: Initialization is completed and restart is started.

User Response: None.

CTIN0068ECT00 SS KEYPOINTS OVERLAID -- CTIN ABORTED

Explanation: IPLB passes the core address of the beginning of the keypoints to CCCTIN. Upon return from the CT00, CT01, CT05, CT10, CT15, and CT20 copy members and also upon return from carving out the internal event facility table, a check is made to ensure that the keypoints are not overlaid. This error message indicates that one of those times it was discovered that the keypoints were overlaid.

After the error message is issued, the content of the general registers are displayed along with the program old PSW, followed by the TPF system entering disabled wait state.

System Action: The TPF system is put into disabled wait state immediately.

User Response: None.

CTIN0072ECT00 GLOBAL AREA TOO LARGE -- CTIN ABORTED

Explanation: There is too much global area reserved. The TPF system cannot run under that circumstance.

The CT00 global area sums up the number of 2K blocks requested for each of the global areas (Global 1 (A), Global 2, Global 3 (Y), and Global 4) given as input to the SIP GLOBAL macro, over all subsystem users (SSUs) for all subsystems.

This gives the total size of each of the global areas in terms of the number of 2K blocks. The number of 2K blocks for each of the global areas must be less than or equal to 255. If the number is greater than 255, this error message is issued. The error message is followed by a display of the general registers and the program old PSW.

System Action: The TPF system is put into disabled wait state immediately.

User Response: Do the following:

  1. Reallocate the global areas.
  2. Reload the corrected TPF system.
  3. IPL the TPF system again.

CTIN0082ECT00 INSUFFICIENT STORAGE FOR xxxx

Where:

xxxx
The name of the particular table requiring storage.

Explanation: While carving storage for the table specified in the message, insufficient storage was detected.

System Action: The TPF system is put into disabled wait state immediately except for the CRTB table. The first instance of this message indicates that there is not enough storage to allocate to the TPF transaction services table area. The CT09 segment will reduce the amount of storage to the minimum size and repeat the allocation request. If the second allocation request fails, the TPF system is put into disabled wait state immediately.

User Response: Do the following if the TPF system is put into disabled wait state:

  1. Define more storage or make some other tables smaller.
  2. IPL the TPF system again.

If the specified table is CRTB, the first instance of this message indicates that the TPF transaction services buffer allocation, which is defined in CTKA, is too large.

  1. Enter the ZCTKA ALTER command and specify the RLBUF parameter to modify the number of recovery log buffers allocated.
  2. IPL the TPF system again.

See TPF Operations for more information about the ZCTKA ALTER command.

CTIN0090ECT09 FACE ERROR ALLOCATION CRTB - CTIN ABORTED

Explanation: The CT09 copy member received an error return from the file address compute program (FACE) when retrieving information about the recovery log records.

System Action: Initialization ends abnormally.

User Response: Determine the reason for the FACE failure and correct it.

CTIN0092ECT38 FACE ERROR BUILDING PAT -- CTIN ABORTED

Explanation: While building the program allocation table (PAT), CTIN found a file address compute program (FACE) error. The registers at the return of the FACE call are displayed.

System Action: The TPF system needs the PAT table to run. The TPF system is put into a disabled wait state.

User Response: Do the following:

  1. Correct the FACE error.
  2. Load the new FACE table.
  3. Perform an initial program load (IPL) of the TPF system again.

CTIN0099ICT99 USER EXIT ACTIVATED

Explanation: The CT99 copy member completed successfully. The CT99 copy member allows you to key protect and initialize storage that was allocated using the CT25 and CT26 copy members. The CT99 copy member can also be used to initialize user-defined CINFC values.

System Action: Initialization is continued.

User Response: None.

See TPF Main Supervisor Reference for more information about the system initializer (CCCTIN). Also see TPF General Macros for more information about the CINFC macro.