gtpm5m0jMessages (Online)

CCTL - CDSI

CCTL0001E 

Explanation: Refer to the CSIO line error messages for any message with a CTL header.

System Action: None.

User Response: None.

CDBG0001WNOT ENOUGH STORAGE TO SATISFY REQUEST FROM module, DEBUGGER MAY ABEND

Where:

module
The module that is making the storage request.

Explanation: Additional entry control block (ECB) heap storage was requested, but there was not any more storage available.

System Action: The debugger tries to continue, but will most likely fail.

User Response: Do the following:

  1. Enter the ZCTKA ALTER command to increase the size of ECB heap storage.
  2. Perform an initial program load (IPL) of the TPF system.
  3. Run the ECB again.

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

CDBG0002EC RUN-TIME ENVIRONMENT FAILED TO INITIALIZE

Explanation: A call to the C environment initialization routine returned with a nonzero return code during TPF C Debugger for VisualAge Client initialization.

System Action: The TPF C Debugger for VisualAge Client initialization ends and the entry control block (ECB) runs without the debugger.

User Response: Do the following:

  1. Verify that the CDB2 segment is loaded to your TPF system or subsystem.
  2. Correct the problem that caused the C environment initialization to fail.
  3. Run the ECB again.

CDBP0001EAN ERROR OCCURRED DURING DEBUG SETUP PROCESSING. ERROR ON socket_call API, RETURN CODE rtcode.

Where:

socket_call
The socket call that received an error return code.

rtcode
The return code to the socket call in decimal format.

Explanation: The ZDBUG command with the START parameter specified was entered to start the VisualAge TPF debug server, but the debug setup request processor found a Transmission Control Protocol/Internet Protocol (TCP/IP) error while processing a request from a client.

System Action: The debug request from the debug setup client program was not processed. The VisualAge TPF debug server continues to run.

User Response: Do the following:

  1. Determine the cause of the TCP/IP IP error and correct it.
  2. Enter ZCLAW DISPLAY ALL to ensure that a Common Link Access to Workstation (CLAW) connection is marked as active.
  3. Ensure that the TPF system is in NORM state.

See TPF Operations for more information about the ZDBUG and ZCLAW DISPLAY commands.

CDBP0002EVISUALAGE TPF DEBUG SERVER RECEIVED A REQUEST IT CANNOT PROCESS. BAD REQUEST LENGTH.

Explanation: The debug setup request processor received a request that is smaller or larger than it can handle.

System Action: The VisualAge TPF debug server continues to run, but this debug setup request is discarded.

User Response: Ensure that the client is at a level that this VisualAge TPF debug server can process.

See the TPF Migration Guide: Program Update Tapes for more information about software requirements for the VisualAge TPF debug server.

CDBP0003EVISUALAGE TPF DEBUG SERVER RECEIVED A REQUEST IT CANNOT PROCESS. UNKNOWN ACTION CODE.

Explanation: The debug setup request processor received a request it could not handle because of an unknown action code.

System Action: The VisualAge TPF debug server continues to run, but this debug setup request is discarded.

User Response: Ensure that the client is at a level that this VisualAge TPF debug server can process.

See the TPF Migration Guide: Program Update Tapes for more information about software requirements for the VisualAge TPF debug server.

CDBS0001IVISUALAGE TPF DEBUG SERVER STARTED FOR HOST: ipaddr (wrkstname) ON PORT port

Where:

ipaddr
The Internet Protocol (IP) address of the VisualAge TPF debug server.

wrkstname
The workstation name of the VisualAge TPF debug server.

port
The port number, in decimal format, of the VisualAge TPF debug server.

Explanation: The ZDBUG command with the START parameter specified was entered to start the VisualAge TPF debug server. The VisualAge TPF debug server has started. You can now use the TPF debug registration client to identify programs to debug.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDBUG command.

CDBS0002IVISUALAGE TPF DEBUG SERVER STARTED FOR HOST: ipaddr ON PORT port

Where:

ipaddr
The Internet Protocol (IP) address of the VisualAge TPF debug server.

port
The port number, in decimal format, of the VisualAge TPF debug server.

Explanation: The ZDBUG command with the START parameter specified was entered to start the VisualAge TPF debug server. The VisualAge TPF debug server has started. You can now use the TPF debug registration client to identify programs to debug.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDBUG command.

CDBS0003IVISUALAGE TPF DEBUG SERVER STOPPED. ONE CLIENT WAS ACTIVATED.

Explanation: The VisualAge TPF debug server was stopped by doing one of the following:

You can no longer use the TPF debug registration client to identify programs to debug.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZCLAW INACTIVATE and ZDBUG commands.

CDBS0004IVISUALAGE TPF DEBUG SERVER STOPPED. clientnum CLIENTS WERE ACTIVATED.

Where:

clientnum
The number of debug setup clients that made contact with the VisualAge TPF debug server.

Explanation: The VisualAge TPF debug server was stopped by doing one of the following:

You can no longer use the TPF debug registration client to identify programs to debug.

System Action: None.

User Response: None.

See TPF Operations for more information about stopping the VisualAge TPF debug server.

CDBS0005EVISUALAGE TPF DEBUG SERVER FAILED TO START. ERROR ON socket_call API, RETURN CODE rtcode.

Where:

socket_call
The socket call that received an error return code.

rtcode
The return code to the socket call in decimal format.

Explanation: The ZDBUG command with the START parameter specified was entered to start the VisualAge TPF debug server, but a Transmission Control Protocol/Internet Protocol (TCP/IP) error occurred. You cannot debug programs using the VisualAge TPF debug server at this time.

System Action: The VisualAge TPF debug server is not started.

User Response: Do the following:

  1. Enter ZCLAW DISPLAY ALL to check that a Common Link Access to Workstation (CLAW) connection is marked as active.
  2. Ensure that the TPF system is in NORM state.
  3. Enter ZDBUG START to start the VisualAge TPF debug server.

See TPF Operations for more information about the ZDBUG andZCLAW DISPLAY commands.

CDBS0006EVISUALAGE TPF DEBUG SERVER FAILED TO START. ERROR ON socket_call API, RETURN CODE rtcode

Where:

socket_call
The socket call that received an error return code.

rtcode
The return code to the socket call in decimal format.

Explanation: A Transmission Control Protocol/Internet Protocol (TCP/IP) error occurred while the VisualAge TPF debug server tried to start the CDBP program.

System Action: The debug request from the debug setup client program was not processed. The VisualAge TPF debug server continues to run.

User Response: Do the following:

  1. Determine the cause of the TCP/IP error and correct it.
  2. Enter ZCLAW DISPLAY ALL to ensure that a Common Link Access to Workstation (CLAW) connection is marked as active.
  3. Ensure that the TPF system is in NORM state.

See TPF Operations for more information about the ZDBUG and ZCLAW DISPLAY commands.

CDBS0008ECOULD NOT FIND A MATCH FOR IP ADDRESS ENTERED

Explanation: The ZDBUG command was entered with the CLEAR and IP-ipaddr parameters specified to clear an Internet Protocol (IP) entry in the trace-by-program or trace-by-terminal table.

System Action: The entry is not cleared from the table.

User Response: Enter the ZDBUG command again and specify the correct IP address for the CLEAR IP-ipaddr parameter.

See TPF Operations for more information about the ZDBUG command.

CDBS0009IALL VISUALAGE TPF DEBUG TRACE ENTRIES HAVE BEEN REMOVED

Explanation: The ZDBUG command with the CLEAR parameter specified was entered to clear all trace entries from the TPF debug registration client.

System Action: Processing is completed successfully with all trace entries removed from the tables.

User Response: To begin tracing your programs, use the TPF Debug Registration window to add debug trace entries.

See TPF Operations for more information about the ZDBUG command. See the VisualAge TPF Online Help for more information about the VisualAge TPF debug server, the TPF Debug Registration window, and how to add debug trace entries.

CDBS0011ITPF DEBUG SERVER HAS BEEN DISABLED

Explanation: The ZDBUG command was entered with the STOP parameter specified to stop the TPF debug server.

System Action: The TPF debug server is disabled.

User Response: None.

See TPF Operations for more information about the ZDBUG command.

CDBS0012ITRACE ENTRY HAS BEEN REMOVED FOR: ipaddr

Where:

ipaddr
The Internet Protocol (IP) address of the TPF debug server.

Explanation: The ZDBUG command was entered with the CLEAR and IP-ipaddr parameters specified to clear the trace entry.

System Action: Processing is completed successfully with a single trace entry removed from the table.

User Response: To begin tracing your programs, use the TPF Debug Registration window to add debug trace entries.

See TPF Operations for more information about the ZDBUG command.

CDBS0013ISTART OF DEBUGGER REGISTRATION INFORMATION

Explanation: The ZDBUG command was entered with the DISPLAY and ALL parameters specified to display all registration information.

System Action: Processing is completed successfully with registration information displayed.

User Response: None.

See TPF Operations for more information about the ZDBUG command.

CDBS0014ISTART OF DEBUGGER PROGRAM REGISTRATION INFORMATION

Explanation: The ZDBUG command was entered with the DISPLAY and PROGRAM parameters specified to display program registration information.

System Action: Processing is completed successfully with program registration information displayed.

User Response: None.

See TPF Operations for more information about the ZDBUG command.

CDBS0015ISTART OF DEBUGGER TERMINAL REGISTRATION INFORMATION

Explanation: The ZDBUG command was entered with the DISPLAY and TERMINAL parameters specified to display terminal registration information.

System Action: Processing is completed successfully with terminal registration information displayed.

User Response: None.

See TPF Operations for more information about the ZDBUG command.

CDBS0016ISTART OF DEBUGGER ACTIVE REGISTRATION INFORMATION

Explanation: The ZDBUG command was entered with the DISPLAY and ACTIVE parameters specified to display information about active entries in the trace-by-program and trace-by-terminal tables.

System Action: Processing is completed successfully with registration information displayed.

User Response: None.

See TPF Operations for more information about the ZDBUG command.

CDBS0017ISTART OF DEBUGGER NONACTIVE REGISTRATION INFORMATION

Explanation: The ZDBUG command with the DISPLAY and NONACTIVE parameters specified was entered to display information about entries in the trace-by-program and trace-by-terminal tables that are not active.

System Action: Processing is completed successfully with registration information displayed.

User Response: None.

See TPF Operations for more information about the ZDBUG command.

CDBS0018WIP ADDRESS ipaddr CLEARED WHILE ENTRY WAS ACTIVE

Where:

ipaddr
The Internet Protocol (IP) address of the TPF debug server.

Explanation: The ZDBUG command was entered with the CLEAR and IP-ipaddr parameters specified to clear an entry in the trace-by-program and trace-by-terminal tables when the entry was already active.

System Action: The trace entry is cleared.

User Response: None.

See TPF Operations for more information about the ZDBUG command.

CDBS0019IAN ACTIVE TRACE ENTRY WAS FOUND. TPF DEBUGGER WAS NOT DISABLED. ALL NONACTIVE TRACE ENTRIES WERE REMOVED.

Explanation: The ZDBUG command was entered with the CLEAR and IP-ipaddr parameters specified to clear an entry in the trace-by-program and trace-by-terminal tables when the entry was already active.

System Action: The debugger is not disabled because an active trace entry was found. However, all nonactive trace entries were removed.

User Response: None.

See TPF Operations for more information about the ZDBUG command.

CDBS0020EVISUALAGE TPF DEBUG SERVER STOPPED. ERROR OCCURRED ON socket_call API, RETURN CODE rtcode.

Where:

socket_call
The socket call that received an error return code.

rtcode
The return code to the socket call in decimal format.

Explanation: The ZDBUG command was entered with the START parameter specified to start the VisualAge TPF debug server, but a network error occurred.

System Action: The VisualAge TPF debug server is stopped.

User Response: Do the following:

  1. See the socket.h header file for more information about the return code for the failing socket API.
  2. Ensure that the TPF system is in NORM state.
  3. Enter the ZDBUG command with the START parameter specified to start the VisualAge TPF debug server.

See TPF Operations for more information about the ZDBUG command.

CDCO0002IRDB-rdb - CONTINUOUS DATA COLLECTION HAS BEEN STARTED

Where:

rdb
The remote relational database (RDB) that contains the continuous data collection (CDC) table.

Explanation: This is the normal response to the ZCDCO command with the START and RDB parameters specified.

System Action: CDC begins.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDCO0003IRDB-rdb - CONTINUOUS DATA COLLECTION HAS BEEN STOPPED

Where:

rdb
The remote relational database (RDB) that contains the continuous data collection (CDC) table.

Explanation: This is the normal response to the ZCDCO command with the STOP and RDB parameters specified.

System Action: CDC ends.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDCO0004WRDB-rdb - CONTINUOUS DATA COLLECTION ALREADY STOPPED

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the STOP and RDB parameters specified; however, CDC is not running.

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDCO0005WRDB-rdb - CONTINUOUS DATA COLLECTION ALREADY STARTED

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the START and RDB parameters specified; however, CDC is already running.

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDCO0006IRDB-rdb - CLEARED ALL CONTINUOUS DATA COLLECTION RECORDS FROM THE REMOTE DATABASE

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: This is the normal response to the ZCDCO command with the CLEAR and RDB parameters specified.

System Action: All CDC records are removed from the CDC table on the specified remote relational database.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDCO0007IRDB-rdb - CREATED CONTINUOUS DATA COLLECTION TABLE ON THE REMOTE DATABASE

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: This is the normal response to the ZCDCO command with the CREATE and RDB parameters specified.

System Action: The CDC table is created in the specified remote relational database and an entry is created in the list of remote relational databases.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDCO0008ERDB-rdb - INCORRECTLY SPECIFIED OR UNAVAILABLE REMOTE DATABASE WHILE ATTEMPTING TO CREATE A CONTINUOUS DATA COLLECTION TABLE

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the CREATE and RDB parameters specified; however, the remote relational database is incorrect or unavailable.

System Action: The command is rejected.

User Response: Do the following:

  1. Verify that the remote relational database is available and defined to the TPF Application Requester (TPFAR) feature.
  2. Enter the ZCDCO command again and specify the CREATE parameter and a valid remote relational database for the RDB parameter.
See TPF Operations for more information about the ZCDCO and ZSQLD commands.

CDCO0009ERDB-rdb - UNAVAILABLE REMOTE DATABASE WHILE ATTEMPTING TO CLEAR THE CONTINUOUS DATA COLLECTION TABLE

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the CLEAR and RDB parameters specified; however, the specified remote relational database is unavailable.

System Action: The command is rejected and the entry is removed from the list of remote relational databases.

User Response: Do the following:

  1. Verify that the remote relational database is available and defined to the TPF Application Requester (TPFAR) feature.
  2. Enter the ZCDCO command again and specify the CLEAR parameter and a valid remote relational database for the RDB parameter.
See TPF Operations for more information about the ZCDCO and ZSQLD commands.

CDCO0010ERDB-rdb - UNAVAILABLE TABLE WHILE ATTEMPTING TO CLEAR THE CONTINUOUS DATA COLLECTION TABLE

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the CLEAR and RDB parameters specified; however, the CDC table in the specified remote relational database is unavailable.

System Action: The command is rejected.

User Response: Do the following:

  1. Verify that the CDC table is defined or has an alias on the specified remote relational database by entering the ZCDCO command with the DISPLAY parameter specified.
  2. Enter the ZCDCO command again and specify the CLEAR parameter and the correct remote relational database for the RDB parameter.

See TPF Operations for more information about the ZCDCO command.

CDCO0011WRDB-rdb - UNABLE TO CREATE DATABASE - TOO MANY CONTINUOUS DATA COLLECTION DATABASES ON THE SYSTEM

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the CREATE and RDB parameters specified; however, the maximum number of remote relational databases has already been created.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZCDCO command.

CDCO0012ITHE REMOTE DATABASE LIST HAS BEEN INITIALIZED

Explanation: This is the normal response to the ZCDCO command with the INIT parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDCO0013WRDB-rdb - TABLE ALREADY DEFINED ON REMOTE DATABASE - MARKING AS CREATED

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the CREATE parameter specified; however, the remote relational database specified already has a CDC table.

System Action: The remote relational database is marked as having been created and is added to the remote relational database list.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDCO0014ERDB-rdb - INCORRECT VALUE FOR FREQ

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the START, FREQ, and RDB parameters specified; however, the value for the FREQ parameter is incorrect.

System Action: The command is rejected.

User Response: Enter the ZCDCO command again and specify the START and RDB parameters and a valid value for the FREQ parameter.

See TPF Operations for more information about the ZCDCO command.

CDCO0015ERDB-rdb - INCORRECT VALUE FOR TIME

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the START, RDB, and TIME parameters specified; however, the value for the TIME parameter was incorrect.

System Action: The command is rejected.

User Response: Enter the ZCDCO command again and specify the START and RDB parameters and a valid value for the TIME parameter.

See TPF Operations for more information about the ZCDCO command.

CDCO0016IDISPLAYING RUNNING CONTINUOUS DATA COLLECTORS

Explanation: This is the normal response to the ZCDCO command with the DISPLAY and COLLECTORS parameters specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDCO0017ERDB-rdb - UNAVAILABLE TABLE WHILE ATTEMPTING TO DELETE CONTINUOUS DATA COLLECTION TABLE

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the DELETE and RDB parameters specified; however, the CDC table was not available.

System Action: The command is rejected and the entry is removed from the remote relational database list.

User Response: See your database administrator.

See TPF Operations for more information about the ZCDCO command.

CDCO0018ERDB-rdb - UNAVAILABLE REMOTE DATABASE WHILE ATTEMPTING TO DELETE THE CONTINUOUS DATA COLLECTION TABLE

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the DELETE and RDB parameters specified; however, the remote RDB specified is not available.

System Action: The command is rejected.

User Response: Do the following:

  1. Verify that the remote relational database is available and defined to the TPF Application Requester (TPFAR) feature.
  2. Enter the ZCDCO command again and specify the DELETE parameter and the correct remote relational database for the RDB parameter.
See TPF Operations for more information about the ZCDCO and ZSQLD commands.

CDCO0019IRDB-rdb - CONTINUOUS DATA COLLECTION TABLE DELETED FROM THE REMOTE DATABASE

Where:

rdb
The remote relational database (RDB) that contains the continuous data collection (CDC) table.

Explanation: This is the normal response to the ZCDCO command with the DELETE and RDB parameters specified.

System Action: The specified CDC table is deleted from the remote relational database and the remote relational database list.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDCO0020IDISPLAYING CREATED CONTINUOUS DATA COLLECTION TABLES

Explanation: This is the normal response to the ZCDCO command with the DISPLAY and DATABASES parameters specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDCO0021ERDB-rdb - CONTINUOUS DATA COLLECTION TABLE MUST BE PREVIOUSLY DEFINED

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the DELETE, CLEAR, or START parameter specified with the RDB parameter; however, the specified remote relational database that contains the CDC table was not defined previously to the TPF system.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZCDCO command with the DISPLAY parameter specified to verify that the remote RDB and CDC table names are correct.
  2. Enter the ZCDCO command again and specify the CREATE parameter, using the correct remote RDB and CDC table parameters to define the table in the TPF system.

See TPF Operations for more information about the ZCDCO command.

CDCO0022WRDB-rdb - UNAVAILABLE TABLE OR DATABASE WHILE ATTEMPTING TO WRITE CONTINUOUS DATA COLLECTION RECORDS - WILL TRY AGAIN AT NEXT COLLECTION INTERVAL

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: CDC is running but records cannot be written to the CDC table. If multiple errors occur within 60 seconds of each other, only the first error will be displayed.

System Action: None.

User Response: Do the following:

  1. Verify that the remote relational database is available and defined to the TPF Application Requester (TPFAR) feature.
  2. Enter the ZCDCO command with the DISPLAY parameter specified to verify that the CDC table and the remote relational database exist.

See TPF Operations for more information about the ZCDCO and ZSQLD commands.

CDCO0023WRDB-rdb - CONTINUOUS DATA COLLECTION TABLE ALREADY CREATED ON THE REMOTE DATABASE

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the CREATE parameter specified; however, the remote relational database specified has been created already.

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDCO0024ERDB-rdb - SQL EXECUTION ERROR - SQLCODE- sqlcode, SQLSTATE- sqlstate

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

sqlcode
The signed integer value representing the disposition of the Structured Query language (SQL) statement.

sqlstate
The corresponding state to the signed integer value that represents the disposition of the SQL statement.

Explanation: The ZCDCO command was entered and encountered a problem running the SQL statement.

System Action: The command is rejected.

User Response: See your database administrator.

See TPF Application Requester User's Guide for more information about SQLCODES and SQLSTATES. See TPF Operations for more information about the ZCDCO command.

CDCO0025EFILE COPY OF REMOTE DATABASE LIST NOT LOADED FOR CONTINUOUS DATA COLLECTION - FACS ERROR

Explanation: The ZCDCO command was entered; however, a FACS error occurred during initialization of a continuous data collection (CDC) table.

System Action: The command is rejected.

User Response: Do the following:

  1. Verify that IBMMP4 ordinal 18 is defined to FACS.
  2. Enter the ZCDCO command again.

See TPF Operations for more information about the ZCDCO command. See TPF System Generation for more information about FACS.

CDCO0026E REQUEST FAILED - UNABLE TO ATTACH SHARED MEMORY SEGMENT

Explanation: The ZCDCO command was entered; however, storage allocation for a continuous data collection (CDC) table could not be completed.

System Action: The command is rejected.

User Response: Do the following:

  1. Verify that the TPF system is in NORM state.
  2. Enter the ZCDCO command again.

See TPF Operations for more information about the ZCDCO command.

CDCO0028WUNEXPECTED VERSION CODE - CLEARING ALL ENTRIES FROM REMOTE DATABASE LIST

Explanation: The ZCDCO command was entered, but an incorrect version of the remote relational database list was found.

System Action: The remote relational database list is reinitialized to match the correct version.

User Response: Enter the ZCDCO command again and specify the CREATE parameter to create all defined remote relational databases for continuous data collection (CDC).

See TPF Operations for more information about the ZCDCO command.

CDCO0029EUNEXPECTED VERSION CODE - COLLECTOR ENDING ABNORMALLY

Explanation: Continuous data collection (CDC) was running when an incorrect version of the remote relational database list was found.

System Action: The continuous data collector stopped.

User Response: Enter the ZCDCO command again and specify the START parameter to start CDC.

See TPF Operations for more information about the ZCDCO command.

CDCO0030IRDB-rdb - CONTINUOUS DATA COLLECTION COMPLETED

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: Continuous data collection (CDC) reached the end of the processing time that had been set previously with the ZCDCO command with the START, TIME, and RDB parameters specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDCO0031ERDB-rdb - CONTINUOUS DATA COLLECTION TABLE CANNOT BE DELETED WHILE ACTIVE

Where:

rdb
The remote relational database that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the DELETE and RDB parameters specified; however, the CDC table cannot be deleted because a collector was active.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZCDCO command with the STOP and RDB parameters specified to stop the collector.
  2. Enter the ZCDCO command with the DELETE and RDB parameters specified to delete the CDC table.

See TPF Operations for more information about the ZCDCO command.

CDCO0032IRDB-rdb - CONTINUOUS DATA COLLECTION TABLE MIGRATED SUCCESSFULLY

Where:

rdb
The remote relational database (RDB) that contains the continuous data collection (CDC) table.

Explanation: This is the normal response to the ZCDCO command with the MIGRATE parameter specified.

System Action: The SYSTPF.TPF_DATA table on the specified remote RDB is migrated to the current level required by CDC.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDCO0033ERDB-rdb - CONTINUOUS DATA COLLECTION TABLE ALREADY MIGRATED

Where:

rdb
The remote relational database (RDB) that contains the continuous data collection (CDC) table.

Explanation: The ZCDCO command was entered with the MIGRATE parameter specified, but the SYSTPF.TPF_DATA table on the specified remote RDB is already migrated to the current level required by CDC.

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZCDCO command.

CDFT0001EINVALID INPUT INPUT FORMAT: ZDFCT nnnnn (1-5 DECIMAL CHARACTERS)

Where:

nnnnn
The decimal number (from 1 to 5 characters) of the record type to display.

Explanation: The record type specified with the ZDFCT command is not in decimal character format.

System Action: The command is rejected.

User Response: Do the following:

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

See TPF Operations for more information about the ZDFCT command.

CDFT0003EUNIQUE RECORD TYPE NOT ALLOWED

Explanation: A record type that is unique to some set of subsystem users, processors, or I-streams was specified with the ZDFCT command.

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZDFCT command.

CDFT0004EPOOL RECORDS NOT ALLOWED

Explanation: A pool record type was specified with the ZDFCT command. This function does not support pool record types.

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZDFCT command.

CDFT0005ETHE RECORD TYPE INDICATOR IS INVALID

Explanation: A record type that is not valid was specified with the ZDFCT command.

System Action: The command is rejected.

User Response: Enter the ZDFCT command again and specify a valid record type.

See TPF Operations for more information about the ZDFCT command.

CDFT0006ETHE REQUESTED RECORD TYPE IS NOT IN USE

Explanation: The record type specified with the ZDFCT command is not in use.

System Action: The command is rejected.

User Response: Enter the ZDFCT command again and specify a valid record type.

See TPF Operations for more information about the ZDFCT command.

CDFT0007ETHE RECORD TYPE IS NOT DEFINED OR EXCEEDS THE LIMIT

Explanation: The record type specified with the ZDFCT command is not defined or exceeds the record type limit.

System Action: The command is rejected.

User Response: Enter the ZDFCT command again and specify a valid record type.

See TPF Operations for more information about the ZDFCT command.

CDFT0009ETHE INPUT ORDINAL NUMBER IS OUTSIDE ALLOWABLE RANGE

Explanation: This error occurred because the maximum ordinal number for the requested record type is not within the allowable range.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDFCT command.

CDFT0012IDISPLAY FACE TABLE DATA

Explanation: This is the normal response to the ZDFCT command.

System Action: None.

User Response: None.

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

CDSI0001ISDA sda SCH# yyyy MOUNTED

Where:

sda
The symbolic device address (SDA) for an input/output (I/O) device.

yyyy
The subchannel number.

Explanation: This is the normal response to the ZDDSI command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDDSI command.

CDSI0002ISDA sda SCH# yyyy NOT DEFINED

Where:

sda
The symbolic device address (SDA) for an input/output (I/O) device.

yyyy
The subchannel number.

Explanation: This is the normal response to the ZDDSI command. The input/output (I/O) device specified is not currently defined to the TPF system.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDDSI command.

CDSI0003ISDA sda OUT OF RANGE. HIGHEST SDA is sda

Where:

sda
The symbolic device address (SDA) for an input/output (I/O) device.

Explanation: An error occurred because the SDA specified for an I/O device in the ZDDSI command is greater than the TPF system's currently defined highest SDA value.

System Action: The command is rejected.

User Response: Enter the ZDDSI command again, specifying a value for the SDA that is less than or equal to the current highest SDA value for the TPF system.

See TPF Operations for more information about the ZDDSI command.