System Management Guide

Appendix A. System Messages

This appendix lists system messages in three sections:

Online messages that you see when you use the installation verification program (IVP) - see "IVP Messages".
Other online messages that you see whan using the administration subsystem - see "Online Messages".
Messages that are logged to the CallPath/CICS message log - see "Messages Logged in the CallPath/CICS Message Log".

The messages are listed, within each section, in numerical order by message number. Each message is explained and you are advised as to what action to take when you see the message.

A message identifier precedes the text of each message. The identifier consists of:

The prefix EQZ
A four-digit message number
A single character indicating the message type. The character can be either I (Information), W (Warning), or A (Action). An action message advises you what action you need to take.

IVP Messages

You may see the following messages displayed on your terminal when you use the IVP.

EQZ0450A CICS SEND MAP command failed

Explanation: The IVP issued a CICS SEND MAP command to display a panel, but the command failed.
System Action: The IVP ends.
User Response: Ensure that the terminal size is large enough for the map. There must be at least 24 rows and 80 columns. If the terminal size is already large enough, contact your service representative.

EQZ0451A CICS RECEIVE MAP command failed

Explanation: The IVP issued a CICS RECEIVE MAP command to receive data from a panel, but the command failed.
System Action: The IVP ends.
User Response: Ensure that the terminal size is large enough for the map. There must be at least 24 rows and 80 columns. If the terminal size is already large enough, contact your service representative.

EQZ0452A Press a valid key

Explanation: You pressed the wrong key.
System Action: None.
User Response: Press a valid key. A list of valid function keys is displayed at the bottom of the panel.

EQZ0453A Type a number between 1 and 3

Explanation: You need to type an option number in the range of 1 to 3 inclusive.
System Action: None
User Response: Type a valid option number. Then press Enter.

EQZ0455A The system configuration table is not configured correctly

Explanation: The SCT does not contain the expected information. The problem may have one of the following causes:

When the macro EQZTSCT was assembled, the VTAM APPLIDs for the CICS regions that are to use CallPath/CICS were not specified
The VTAM APPLID for the CICS region in which the IVP is currently running is not specified in the SCT
The load module EQZTSCT does not contain copyright information in the expected position.

System Action: The IVP continues.
User Response:

Reassemble macro EQZTSCT specifying the VTAM APPLIDs for all the CICS regions containing CallPath/CICS modules. Remember to specify the VTAM APPLID of the current CICS region if you want CallPath/CICS to use it.
If the problem persists and you are sure that you have assembled macro EQZTSCT correctly, contact your service representative.

EQZ0456I EQZTSCT not found. IVP runs as if in primary region.

Explanation: The SCT load module EQZTSCT cannot be found. CallPath/CICS cannot operate without this module.
System Action: The IVP continues to perform the checks that it makes when it runs in the primary CallPath/CICS region. The IVP cannot determine whether or not it is running in the primary CallPath/CICS region, as this information is held in the SCT.
User Response: Ensure that the load module EQZTSCT is placed in one of the libraries assigned to DFHRPL in the CICS JCL.

EQZ0457I VTAM APPLID not in list. Will run as if in primary region.

Explanation: The ACB by which this CICS system is known to VTAM could not be found in the list of VTAM APPLIDs that were defined to CallPath/CICS during the creation of the System Configuration Table, module EQZTSCT, at installation time.
System Action: The IVP continues to perform the checks that it makes when it runs in the primary CallPath/CICS region.
User Response: Re-assemble the module EQZTSCT after adding the VTAM APPLID for this CICS system to the list. See "Task 6: Creating the System Configuration Table (SCT)" for details.

EQZ0458A mmmmmmmm Transaction disabled

Explanation: The transaction associated with module mmmmmmmm is currently disabled and cannot be used.
System Action: The IVP continues.
User Response: Use the CICS transaction CEMT to enable the transaction.

EQZ0459A fffff CICS OPEN command failed

Explanation: The CICS OPEN command to open file fffff ready for use has failed with an IOERR condition.
System Action: The IVP continues.
User Response: Refer to your CICS documentation for an explanation of response codes for this command.

EQZ0460I Link checking available from remote region only

Explanation: The option to verify remote region support links for MRO operation was selected from the Installation Verification Menu, but the transaction EQIV was initiated from a primary CallPath/CICS region.
System Action: The IVP does not perform this check.
User Response: To check MRO communication links, use transaction EQIV in each remote CallPath/CICS region.

EQZ0461A aaaaaaaa MRO connection name not found

Explanation: No MRO connection name is defined with the same name as the SUBSYSID parameter associated with the displayed VTAM APPLID in the System Configuration Table.
System Action: The IVP cannot continue to test communication links.
User Response: Ensure that the SUBSYSID specified in the SCT is correct. Then define a MRO connection with the same name.

EQZ0462I Top of scrolling area reached

Explanation: You cannot scroll up any further.
System Action: None
User Response: None

EQZ0463I Bottom of scrolling area reached

Explanation: You cannot scroll down any further.
System Action: None
User Response: None

EQZ0464A Select an option. Then press Enter.

Explanation: You need to type an option number before you press Enter.
System Action: None
User Response: Type either 1, 2, or 3. Then press Enter.

EQZ0465A CICS DELETEQ command failed

Explanation: A DELETEQ TS command to delete a temporary storage queue has failed. The queue is used for internal processing. The name of the queue is formed by concatenating the terminal ID and task number.
System Action: The IVP ends.
User Response: Exit IVP and start again by re-invoking transaction EQIV. If the problem persists, contact your service representative.

EQZ0467A CICS READQ command failed

Explanation: A READQ TS command to read a temporary storage queue failed. The queue is used for internal processing. The name of the queue is formed by concatenating the terminal ID and task number.
System Action: The IVP ends.
User Response: Exit IVP and start again by re-invoking transaction EQIV. If the problem persists, contact your service representative.

EQZ0468A fffffff File not found

Explanation: This file is not defined to CICS.
System Action: The IVP continues.
User Response: Ensure that you define to your CICS system all the files used by CallPath/CICS.

EQZ0469A fffffff Not authorized to read file

Explanation: The person using the transaction EQIV is not authorized to access file fffffff.
System Action: The IVP continues.
User Response: Ensure that the person using the IVP is authorized to access all CallPath/CICS files.

EQZ0470A fffffff File is not defined as VSAM

Explanation: File fffffff has not been set up with VSAM as the global access method.
System Action: The IVP continues.
User Response: Redefine the FCT entry for this file. Specify the access method to be VSAM. See the supplied FCT entries for the correct values.

EQZ0471A fffffff File is not enabled

Explanation: File fffffff is not available for application programs to access.
System Action: The IVP continues.
User Response: Enable the file using the transaction CEMT.

EQZ0472A fffffff VSAM file is not ESDS or KSDS

Explanation: File fffffff is not defined with the correct TYPE option that defines the type of dataset that corresponds to the file. CallPath/CICS uses only ESDS and KSDS files.
System Action: The IVP continues.
User Response: Redefine the FCT entry for this file, specifying the correct TYPE. See the supplied FCT entries for the correct values.

EQZ0473A Incorrect READ, UPDATE, BROWSE, ADD, or DELETE parameters

Explanation: The file was defined with an invalid combination of values for the above parameters. The parameters indicate which operations application programs can perform on a file.
System Action: The IVP continues.
User Response: Redefine the FCT entry for this file. Specify the correct combination of parameters. See the supplied FCT entries for the correct values.

EQZ0474A fffffff Help file is empty

Explanation: The help control file fffffff is empty. No online help is available until you correct the problem.
System Action: The IVP continues.
User Response: Ensure that the installation process to define and initialize the VSAM files used by CallPath/CICS worked successfully.

EQZ0475A aaaaaaaa Network name incorrect in system configuration table

Explanation: The application ID of the remote CallPath/CICS region to which the connection name points does not correspond to the value specified in the SCT.
System Action: The IVP cannot continue testing communication links.
User Response: Ensure that the CICS connection definition points to the correct remote region in the SCT.

EQZ0476A qqqq Transient data queue not defined as remote

Explanation: The transient data queue qqqq is not defined as remote in the DCT of the remote CallPath/CICS region.
System Action: The IVP continues.
User Response: Redefine the DCT entry for this transient data queue. Specify TYPE=REMOTE. See the supplied DCT entries for the correct options.

EQZ0477A No more information to display

Explanation: You pressed a function key to scroll backward or forward, but there is no more information to display.
System Action: The current panel is displayed again.
User Response: None.

EQZ0487A mmmmmmmm Load module not found

Explanation: Load module mmmmmmmm could not be found in any of the libraries assigned to the DFHRPL DD statement in the CICS JCL.
System Action: The IVP continues.
User Response: Ensure that the CallPath/CICS load library SEQZLOAD is assigned to the DFHRPL DD statement. If it is already assigned, ensure that it contains the specified load module. If it does not contain the load module, contact your service representative.

EQZ0488A mmmmmmmm You are not authorized to use load module

Explanation: The person using transaction EQIV is not authorized to access load module mmmmmmmm. The IVP performs CICS LOAD commands to verify that the load modules exist. The modules are subsequently released.
System Action: The IVP continues.
User Response: Ensure that the person using the IVP has authority to LOAD and RELEASE all CallPath/CICS programs and maps.

EQZ0489A Error on CICS call. EIBFN=xxxx EIBRESP=y

Explanation: An error occurred while the CICS command identified by the EIBFN value xxxx in the EXEC Interface Block (EIB) was being executed. The CICS response code was y.
System Action: The IVP continues.
User Response: Refer to your CICS documentation for an explanation of response codes for this command. If the explanation suggests a problem in the CallPath/CICS software, contact your service representative.

EQZ0490A Installation Verification Program ended abnormally

Explanation: The IVP ended abnormally. Another message is displayed that tells you the reason for the abnormal end. The probable cause is that the IVP could not send or receive a map.
System Action: The IVP ends.
User Response: Contact your service representative.

EQZ0491I No installation errors found

Explanation: The IVP found no errors in the installation of CallPath/CICS in this CICS region.
System Action: None
User Response: None

EQZ0492I xxx messages produced. Maximum condition code = y

Explanation: The IVP has completed its checks. It found xxx problems. The maximum condition code y indicates the severity of the problems:

0: No errors were detected
4: Information messages only
8: Severe errors were detected

System Action: None
User Response: If the maximum condition code is 8, you must correct the problems before CallPath/CICS can operate successfully.

EQZ0493A mmmmmmmm Load module not defined in PPT

Explanation: The IVP issued a CICS INQUIRE command on program or map name mmmmmmmm. The response code indicates that there is no entry for the module in the PPT.
System Action: The IVP continues.
User Response: Add an entry for this program or map to the PPT. See the supplied PPT entries for the correct options.

EQZ0494A tttt Transaction not defined in PCT

Explanation: The IVP issued a CICS INQUIRE command on transaction tttt. The response code indicates that there is no entry for the transaction in the PCT.
System Action: The IVP continues.
User Response: Add an entry for this transaction in the PCT. See the supplied PCT entries for the correct options.

EQZ0495A mmmmmmmm Load module disabled

Explanation: The program or map is not available for use because its status is disabled.
System Action: The IVP continues.
User Response: Enable the program or map using the transaction CEMT.

EQZ0496A Transient data queue not defined in DCT

Explanation: The IVP called the CICS-supplied program CEMT to determine whether the transient data queues are defined to CICS in the DCT. Queue qqqq is not defined.
System Action: The IVP continues.
User Response: Add an entry for this transient data queue in the DCT. See the supplied DCT entries for the correct options.

EQZ0497A tttt You are not authorized to use this transaction

Explanation: The person using the transaction EQIV is not authorized to use transaction tttt.
System Action: The IVP continues.
User Response: Ensure that the person using the IVP has authority to use all CallPath/CICS transactions, and re-run IVP.

EQZ0498A tttt Invalid program name defined for transaction

Explanation: The wrong program is defined to this transaction in the PCT.
System Action: The IVP continues.
User Response: Correct the PCT entry for this transaction. See the supplied PCT entries for the correct program name to associate with this transaction.

EQZ0499A qqqq Transient data queue disabled

Explanation: Transient data queue qqqq is not available for use because its status is disabled.
System Action: The IVP continues.
User Response: Enable the transient data queue using the transaction CEMT.

Online Messages

You may see the following messages displayed on your terminal when you use the administration subsystem.

EQZ0201A Press a valid key

Explanation: The key pressed is not supported by the displayed panel.

System Action: The panel is not processed.
User Response: Press a valid key. A list of function keys supported by the panel are displayed at the bottom of the panel.

EQZ0202I Top of scrolling area reached

Explanation: The top of the scrolling area is currently displayed.
System Action: The function key F7 has no effect.
User Response: None.

EQZ0203I Bottom of scrolling area reached

Explanation: The bottom of the scrolling area is currently displayed.
System Action: The function key F8 has no effect.
User Response: None.

EQZ0204W System error. Help information cannot be found.

Explanation: There is no help information available for this panel.
System Action: The current panel is redisplayed.
User Response: None.

EQZ0205A CICS error reading help file

Explanation: A CICS error has occurred when attempting to read the help file EQZHELP.
System Action: The current panel is redisplayed.
User Response: Check that file EQZHELP has been defined to CICS, and that it is open and enabled.

EQZ0206I No more information to display

Explanation: A scrolling function key has been pressed but there is no more information to be displayed.
System Action: The current panel is redisplayed.
User Response: None.

EQZ0207A Select the traffic type you require

Explanation: Enter has been pressed with no traffic type selected.
System Action: The Message Traffic Statistics panel is re-presented.
User Response: Enter one of the valid traffic types indicated on the panel.

EQZ0208A Type 1, 2, or 3 to select the traffic type

Explanation: An invalid traffic type number has been entered.
System Action: None.
User Response: Enter a valid traffic type number.

EQZ0209A SEND MAP FAILURE

Parameters: mmmmmmm, resp
Explanation: A CICS SEND MAP command failed to display map mmmmmmm. The response code was resp.
System Action: The module ends and returns control to CICS.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0210A RECEIVE MAP FAILURE

Parameters: mmmmmmm, resp
Explanation: A CICS RECEIVE MAP command failed to receive data from map mmmmmmm. The response code was resp.
System Action: The module ends and returns control to CICS.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0211I Your subsystem start request has been issued

Explanation: The request to start the Administration Subsystem has been issued successfully. This does not imply that the Subsystem is now active. Check the system status information.
System Action: The panel is redisplayed.
User Response: None.

EQZ0212A Your subsystem start request was not issued
rc

Explanation: The request to start the Administration Subsystem has failed.
System Action: The panel is redisplayed, and the Subsystem will not have started.
User Response: Place the cursor on the message and press F1 for help information. This will give the CICS response code for the start request.

EQZ0213I The subsystem is already shut down

Explanation: The request to shutdown the Administration Subsystem has been rejected because the Subsystem is not currently active.
System Action: The panel is redisplayed.
User Response: None.

EQZ0214I Your subsystem shutdown request is cancelled

Explanation: The request to shutdown the Administration Subsystem has not been confirmed, so the request is not submitted.
System Action: None.
User Response: None.

EQZ0215I Your subsystem shutdown request has been issued

Explanation: The request to shutdown the Administration Subsystem has been confirmed, and the request has been sent to the Subsystem.
System Action: The Administration Subsystem will request the shutdown of all switch communication links, and when this has been completed, it will terminate.
User Response: None.

EQZ0216A CICS error in help request. See the message log.

Explanation: Help has been requested but the application has failed to link to the help module EQZ3HELP.
System Action: The current panel is redisplayed.
User Response: Contact your service representative. EQZ3TRAF EQZ3TRON EQZ3PTRC

EQZ0217A CICS error in status request

Explanation: A request to display the system status information has failed to link to the status module EQZ3STAT.
System Action: The current panel is redisplayed.
User Response: Contact your service representative.

EQZ0218A Select an action. Then press Enter.

Explanation: The Enter key has been pressed but an action has not been selected.
System Action: The panel is not processed.
User Response: Enter a valid action number and press Enter.

EQZ0219A Type a valid action code

Explanation: The Enter key has been pressed with an invalid action code typed in the choice entry field.
System Action: The panel is not processed.
User Response: Enter a valid action code and press Enter.

EQZ0220I The subsystem is already started

Explanation: A request to start the Subsystem has been made but the Subsystem is already processing.
System Action: The start request is not processed.
User Response: None.

EQZ0221A System error during status processing

Parameters: rc
Explanation: An EXEC CICS LOAD command on program EQZTSTAT failed with a return code of rc
System Action: No further processing can be done from this panel.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0222I The screen has been refreshed

Explanation: The information on the screen has been refreshed to reflect the current system status.
System Action: None
User Response: None

EQZ0223A CICS error processing your request

Explanation: An attempt to transfer control to another program has failed.
System Action: None
User Response: Contact your service representative. EQZ3TRON EQZ3PTRC EQZ4SLCO

EQZ0224A Type a number between 1 and 9

Explanation: The user has typed an invalid option number, which must be in the range 1 to 9 inclusive.
System Action: None
User Response: Type a valid option number and press Enter.

EQZ0225A Select an option. Then press Enter.

Explanation: The user has pressed the Enter key without typing an option number in the choice entry field.
System Action: None.
User Response: Type a valid option number and press Enter, or select a function key.

EQZ0226A Type / to select an item

Explanation: The user has typed an invalid selection character against an item in the selection list. This character should be /.
System Action: None.
User Response: Type / against the item in the list on which the action is to be performed. Then press Enter.

EQZ0227I Tracing is on for the modules that are selected

Explanation: Tracing has been switched on for the modules selected.
System Action: Trace records will be generated by the selected modules and written to the subsystem for logging.
User Response: None.

EQZ0228A Select a module for which you want to switch on tracing

Explanation: The user has pressed Enter without selecting any modules for tracing.
System Action: None.
User Response: Type / against the modules for which tracing is required, and press Enter. Otherwise, select a valid function key.

EQZ0229I All tracing is switched off

Explanation: The user action has resulted in tracing being turned off for all modules.
System Action: No more trace records are generated.
User Response: None.

EQZ0230A Type action codes next to the switches

Explanation: The user has pressed Enter without typing any actions against the switch list.
System Action: None.
User Response: Type valid action codes against the switch list and press Enter to process them. Otherwise, press a valid function key.

EQZ0231I All actions have been processed

Explanation: All the actions selected by the user have been processed successfully.
System Action: None.
User Response: None.

EQZ0232A System error in delete queue processing

Parameters: rc
Explanation: The module has failed to delete a temporary storage queue used for processing. The CICS response code from the delete command is rc.
System Action: No further processing can be performed on this panel.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0233A CICS error. Failed to write to temporary storage queue.

Parameters: rc
Explanation: An attempt to write a record to a temporary storage queue used for processing has failed with a CICS response code of rc.
System Action: No further processing can be performed on this panel.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0234A CICS error reading switch file

Parameters: rc
Explanation: Whilst browsing the VSAM file EQZSWCH, a CICS READNEXT command failed with a CICS response code of rc.
System Action: No further processing can be performed from this panel.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0235W There are no switches to display

Explanation: There are no switch description records defined to the VSAM file EQZSWCH.
System Action: None.
User Response: Add a switch description record to EQZSWCH.

EQZ0236A CICS error while processing request

Parameters: rc
Explanation: An attempt to read a record from a temporary storage queue failed with a CICS response code of rc.
System Action: No further processing can be performed from this panel.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0237A CICS error while processing request

Parameters: rc
Explanation: An attempt to rewrite a record to a temporary storage queue failed with a CICS response code of rc.
System Action: No further processing can be performed from this panel.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0238A Your start switch communications request was not issued

Parameters: rc
Explanation: A CICS start command for transaction EQRH (Request Handler) failed with a response code of rc..
System Action: None.
User Response: Contact your service representative.

EQZ0239I Help panel nesting limit has been reached

Explanation: A request to display another level of help has been turned down because the nesting limit of 10 help panels has been reached.
System Action: None
User Response: Press F12 to back out one help panel at a time, or press F3 to end help.

EQZ0240I The switch is already in use

Explanation: A request to start communications with a switch has been rejected because communications with this switch has already been established.
System Action: None.
User Response: None.

EQZ0241A Select a switch

Explanation: The Enter key has been pressed with no switch selected
System Action: None
User Response: Select a switch and press Enter.

EQZ0242I The switch is already shut down

Explanation: A request to shut down communications with a switch has been rejected because communications are not established with this switch.
System Action: None
User Response: None.

EQZ0243A The response type must be 1 or 2

Explanation: The response type must be 1 or 2.
System Action: None
User Response: Type a valid response type and press Enter.

EQZ0244W Diagnostic tracing is switched on. It may affect performance.

Explanation: A warning message to indicate that diagnostic tracing is turned on for some modules which may affect the performance information if performance tracing is switched on.
System Action: None
User Response: None

EQZ0245A CICS error reading log control file

Parameters: rc
Explanation: An attempt to read the VSAM file EQZCLOG failed with a CICS response code of rc.
System Action: No further processing can be performed from this panel.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0246W Log swapping in progress. Try again.

Explanation: A request to view or print the system messages log file has been rejected because the logs are currently being swapped.
System Action: None
User Response: Try again.

EQZ0247I No messages found for the criteria you specified

Explanation: No messages in the systems messages log file meet the search criteria specified by the user.
System Action: None.
User Response: Change the search criteria and press Enter.

EQZ0248A Type / to select a log type

Explanation: The Enter key has been pressed with no selections made.
System Action: None
User Response: Type / beside the required log type.

EQZ0249I Your request to swap log files has been issued

Explanation: Requests to swap logs have been sent to the subsystem.
System Action: None.
User Response: None.

EQZ0250A The start date and time must be before the end date and time

Explanation: The start date and time must be less than the end date and time.
System Action: None.
User Response: Enter a start date and time that is less than the end date and time.

EQZ0251A CICS error in print request

Parameters: rc
Explanation: An EXEC CICS OPEN command on the message log file failed with a response code of rc.
System Action:
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0252A CICS error in print request

Parameters: rc
Explanation: An EXEC CICS INQUIRE on the message log file to ascertain the dataset name for printing has failed with a response code of rc.
System Action: None.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0254A The print facility is not available

Parameters: rc
Explanation: An EXEC CICS STARTBR command failed on the print file with a response code of rc.
System Action: Module processing ends.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0255A CICS error in print request

Parameters: rc
Explanation: An EXEC CICS WRITEQ TD command failed when attempting to write to EQRD, with a response code of rc.
System Action: Module processing ends.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0256I Print request submitted successfully

Explanation: Print request has successfully completed.
System Action: None.
User Response: None.

EQZ0257A CICS error in print request

Parameters: rc
Explanation: An EXEC CICS READNEXT command failed on the print file with a response code of rc.
System Action: Module processing ends.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0258A CICS error reading message log file

Parameters: rc
Explanation: An EXEC CICS STARTBR command failed on the message log file with a response code of rc.
System Action: Module processing ends.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0259A CICS error reading message log file

Parameters: rc
Explanation: An EXEC CICS READNEXT command failed on the message log file with a response code of rc.
System Action: Module processing ends.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0260A CICS error reading message log file

Parameters: rc
Explanation: An EXEC CICS ENDBR command failed on the message log file with a response code of rc.
System Action: Module processing ends.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0261A CICS error in print request

Parameters: rc
Explanation: A CICS ENQUEUE command on resource EQZREADER failed with a response code of rc.
System Action: Module processing ends.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0262A Type 1 or 2 to select a switch communication startup method

Explanation: You must select a switch communications startup mode.
System Action: None
User Response: None

EQZ0263A Type 1 or 2 to select an output destination

Explanation: You must select an output destination.
System Action: None
User Response: None

EQZ0264I This switch description record no longer exists

Explanation: A request to update or delete this record has been rejected because it no longer exists.
System Action: None
User Response: None

EQZ0265A CICS error reading switch file

Parameters: rc
Explanation: An EXEC CICS READ for UPDATE command has failed with a response code of rc.
System Action: None.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0266A CICS error updating switch file

Parameters: rc
Explanation: An EXEC CICS REWRITE command has failed with a response code of rc.
System Action: Module processing ends.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0267A CICS error deleting switch file record

Parameters: rc
Explanation: An EXEC CICS DELETE command has failed with a response code of rc.
System Action: Module processing ends.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0268I No traffic statistics have yet been logged in this session

Explanation: No message traffic statistics have been collected for the current session.
System Action: None.
User Response: None.

EQZ0269A You can only select one switch

Explanation: The user has selected more than one switch.
System Action: None.
User Response: Select only one switch and press Enter.

EQZ0270I There is no extra data for the selected message

Explanation: From the Message Listing panel, the F2 function key has been pressed while the cursor is on a message for which there is no associated variable data.
System Action: None.
User Response: None.

EQZ0271A CICS error in traffic request

Explanation: A CICS LOAD request for program EQZTTRFC failed with a response code of rc.
System Action: Module processing ends.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0272A This switch record has changed during your update request

Explanation: During an update process for the switch description record, the record has been altered by another user while you have been doing your changes.
System Action: Your update request is terminated.
User Response: Re-enter the required switch record changes.

EQZ0273I Your update request has been processed

Explanation:
System Action: None.
User Response: None.

EQZ0274A Error loading module EQZTSWMT. Run transaction EQIV to verify.

Parameters: rc
Explanation: An EXEC CICS LOAD command on program EQZTSWMT failed with a return code of rc
System Action: No further processing can be done from this panel.
User Response: Run IVP.

EQZ0275A Enter a date

Explanation: The date and time formatting module has been passed a date to edit which is blank.
System Action: The date is rejected.
User Response: Enter a valid date.

EQZ0276A Enter a time

Explanation: The date and time formatting module has been passed a time to edit which is blank.
System Action: The time is rejected.
User Response: Enter a valid time.

EQZ0277A System error during date and time validation

Explanation: The date format value held in the System Configuration Table EQZTSCT is invalid. It must be in the range 1 to 8 inclusive.
System Action: The date and time are rejected.
User Response: Reconfigure the System Configuration Table.

EQZ0278A Incorrect date format. Press F5 for default dates and times.

Explanation: The format of the date entered does not match the format selected at installation time, specified in the System Configuration Table. The valid formats (without the selectable separator) are:

DDMMYY
DDMMYYYY
MMDDYY
MMDDYYYY
YYMMDD
YYYYMMDD
YYDDMM
YYYYDDMM

System Action: The date is rejected.
User Response: Enter the date in the valid format. Press F5 to display the current date in the expected format.

EQZ0279A Incorrect time format. Press F5 for default dates and times.

Explanation: The format of the time entered does not match the format expected.
System Action: The time is rejected.
User Response: Enter the time in the valid format. Press F5 to display the current time in the expected format.

EQZ0280A Month number must be in the range 1 to 12 inclusive

Explanation: The month number entered is invalid. It must be in the range 1 to 12 inclusive.
System Action: The date is rejected.
User Response: Correct the month number.

EQZ0281A Enter a valid day number for the chosen month

Explanation: The day of the month number is invalid for the month specified.
System Action: The date is rejected.
User Response: Correct the day of the month number.

EQZ0282A Hours must be in the range 0 to 23 inclusive

Explanation: The hour number is invalid. It must be in the range 1 to 23 inclusive.
System Action: The time is rejected.
User Response: Correct the hour number.

EQZ0283A Minutes must be in the range 0 to 59 inclusive

Explanation: The minutes number is invalid. It must be in the range 0 to 59 inclusive.
System Action: The time is rejected.
User Response: Correct the minutes number.

EQZ0284A CICS ERROR LINKING TO PROGRAM

Parameters: resp, pppppppp
Explanation: An EXEC CICS LINK command to program pppppppp failed. The response code was resp.
System Action: The module ends and returns control to CICS.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0285A CICS ERROR TRANSFERRING CONTROL TO PROGRAM

Parameters: resp, pppppppp
Explanation: An EXEC CICS XCTL command to program pppppppp failed with a response code of resp.
System Action: The module ends and returns control to CICS.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0286A You must start the subsystem first

Explanation: A request to start communications with a switch or to swap logs has been rejected because the subsystem is not started.
System Action: None.
User Response: Start the subsystem.

EQZ0287W No more switches can be started. System limit reached.

Explanation: A request to start communications with a switch has been rejected because the system limit of 36 active conversations has been reached.
System Action: None
User Response: Consider creating another Callpath CICS region to which another 36 Switches can be defined.

EQZ0288A System error loading control table

Explanation: There was an error loading the SCT.
System Action: Control table processing ends.
User Response: Contact your systems programming representative.

EQZ0289A You must be in the same CICS region as the subsystem

Explanation: You may have a Sysid defined that is not valid.
System Action: Control table processing ends.
User Response: Check your SCT configuration to ensure you have the correct applids defined.

EQZ0290A System error sending request

Explanation: A request to the subsystem to swap log files has failed.
System Action: System log swap processing ends.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0291A System error sending request

Explanation: Error writing to Request Handler transient data queue.
System Action: The module continues processing.
User Response: None.

EQZ0292A CICS error reading message log file

Parameters: rc
Explanation: An EXEC CICS READ command failed on the message log file with a response code of rc.
System Action: The module ends and returns control to CICS.
User Response: Refer to your CICS documentation for an explanation of the response code for this command.

EQZ0293A Place the cursor on the required message and press F2

Explanation: Key F2 was pressed, but the cursor was not placed on a line on the screen containing a message.
System Action: The screen is returned.
User Response: Place the cursor on a line containing a message and press F2.

EQZ0294A Type 1 or 2 to select message listing sequence

Explanation: You must select a message listing sequence.
System Action: None
User Response: None

EQZ0295A CICS error reading message log file

Parameters: rc
Explanation: An EXEC CICS READPREV command failed on the message log file with a response code of rc.
System Action: The module ends.
User Response: Refer to your CICS documentation for an explanation of response codes for this command. If the explanation suggests an error in the CallPath/CICS software, contact your service representative.

EQZ0296A EQZnnnnA

Explanation: Error message not found in message file.
System Action: None.
User Response: Contact your systems programming representative.

EQZ0297A EQZnnnnA

Explanation: CICS error encountered reading message file.
System Action: None.
User Response: Refer to your CICS documentation for an explanation of response codes for this command. If the explanation suggests an error in the CallPath/CICS software, contact your service representative.

EQZ0298A Seconds must be in the range 0 to 59 inclusive

Explanation: The seconds number is invalid. It must be in the range 0 to 59 inclusive.
System Action: The time is rejected.
User Response: Correct the seconds number.

EQZ0299A The log file has been swapped. Refresh your search criteria.

Explanation: The current log file has been swapped whilst the user has been using the System Messages panels. Only the current log file can be browsed.
System Action: None.
User Response: Refresh the search criteria.

EQZ0400I No simulated switches are currently active

Explanation: The panel cannot display any information as there are no simulated switches currently active.
System Action: The panel is not processed.
User Response: Either start a switch in simulation mode, or investigate why the switch you had started is no longer active.

EQZ0409A Failed to process Switch_Status message. See message log.

Explanation: The Switch_Status message being processed requires the internal switch table to be reset, but the call to module EQZ2SETT has failed.
System Action: The internal switch dependent tables are not reset.
User Response: Check the message log for an associated message for this problem, with EQZ2SETT as the source module. This message will contain further action instructions.

EQZ0412A Failed to distribute Switch_Status message. See message log.

Explanation: The Switch_Status message being processed could not be distributed to applications monitoring the switch, due to a problem in module EQZ2TELL.
System Action: The switch status message is not distributed.
User Response: Check the message log for an associated message for this problem, with EQZ2TELL as the source module. This message will contain further action instructions.

EQZ0413A More than one selection has been made

Explanation: Self-explanatory.
System Action: Screen is redisplayed.
User Response: Remove invalid selections.

EQZ0414I Default response modified successfully

Explanation: Self-explanatory.
System Action: None.
User Response: None.

EQZ0419A Make a selection.

Explanation: The Enter key has been pressed without a selection being made.
System Action: None.
User Response: Contact your service representative.

EQZ0420A Invalid input data

Explanation: One or more input fields have invalid data in them.
System Action: None.
User Response: Re-enter data correctly.

EQZ0424A You must select ONE feature type

Explanation: Data for more than feature has been entered on the screen.
System Action: Screen redisplayed
User Response: Remove all but one feature

EQZ0425I Event file updated successfully

Explanation: The requested action has been performed on the event message.
System Action: Simulator processing continues.
User Response: None.

EQZ0426A Event file not updated - record already exists

Explanation: The add failed because a duplicate record was found.
System Action: The input screen is re-presented.
User Response: Change key fields or delete existing record.

EQZ0427A CICS error writing to event file

Explanation: An attempt to WRITE to the Event file has failed. The response code was resp.
System Action: Confirmation module processing ends.
User Response: Refer to your CICS documentation for an explanation of response codes for this command. If the explanation suggests that an error exists in the CallPath/CICS software, contact your service representative.

EQZ0428A CICS error rewriting EQZEVNT file

Explanation: Attempt to UPDATE a record has failed. The response code was resp.
System Action: Update processing ends.
User Response: Refer to your CICS documentation for an explanation of response codes for this command. If the explanation suggests that an error exists in the CallPath/CICS software, contact your service representative.

EQZ0429I Event not found for update

Explanation: The required record was not found on the Event file. The response code was resp.
System Action: Processing ends.
User Response: Refer to your CICS documentation for an explanation of response codes for this command. If the explanation suggests that an error exists in the CallPath/CICS software, contact your service representative.

EQZ0430A CICS error reading file EQZEVNT

Explanation: A serious CICS error occurred whilst reading the Event file. The response code was resp.
System Action: Processing ends.
User Response: Refer to your CICS documentation for an explanation of response codes for this command. If the explanation suggests that an error exists in the CallPath/CICS software, contact your service representative.

EQZ0431A CICS error when unlocking event file EQZEVNT

Explanation: An attempt to UNLOCK the Event file failed. The response code was resp.
System Action: Processing ends.
User Response: Refer to your CICS documentation for an explanation of response codes for this command. If the explanation suggests that an error exists in the CallPath/CICS software, contact your service representative.

EQZ0432I Event deletion successful

Explanation: The requested record was deleted from the Event file.
System Action: None.
User Response: None.

EQZ0433A CICS error when deleting from Event file

Explanation: An attempt to DELETE a record from the Event file failed. The response code was resp.
System Action: Processing ends.
User Response: Refer to your CICS documentation for an explanation of response codes for this command. If the explanation suggests that an error exists in the CallPath/CICS software, contact your service representative.

EQZ0434W Record not found for deletion

Explanation: A record selected for deletion could not be found on the Event file.
System Action: Processing ends. The response code was resp.
User Response: Refer to your CICS documentation for an explanation of response codes for this command. If the explanation suggests that an error exists in the CallPath/CICS software, contact your service representative.

EQZ0435A Required event key information not entered

Explanation: Event message record key fields were not entered.
System Action: module processing continues.
User Response: Refer to your CICS documentation for an explanation of response codes for this command. If the explanation suggests that an error exists in the CallPath/CICS software, contact your service representative.

EQZ0436A Duplicate event record on file

Explanation: A duplicate record exists on the Event file. The response code was resp.
System Action: Processing ends.
User Response: Refer to your CICS documentation for an explanation of response codes for this command. If the explanation suggests that an error exists in the CallPath/CICS software, contact your service representative.

EQZ0437A Type action codes next to the events

Explanation: No action code was entered.
System Action: None.
User Response: Type a valid action code beside the required event.

EQZ0438A Only one event type may be selected

Explanation: '/' has been entered beside more than one event.
System Action: None.
User Response: Select only one event message.

EQZ0441A Required feature data not entered

Explanation: Required Feature Invoked data has not been entered.
System Action: None.
User Response: Enter the required information.

EQZ0442W REQUEST_INSTRUCTION EVENT DATA NOT FOUND

Parameters: mmmmmmm, kkkkkkkkkkkkkkkkkk
Explanation: The extract messages module within the switch simulator could not find the trigger_event_data associated with a Request_Instruction event.

mmmmmmm is the panel ID of the
'Extract Messages' screen.
kkkkkkkkkkkkkkkkkk is the key of the
Request_Instruction event
that produced this warning message.

System Action: The Request_Instruction message is ignored and processing continues. When processing is complete, the warning message EQZ0606W is displayed.
User Response: Look at the key for the trigger_event_data that is specified on the Request_Instruction event that you have loaded. If no record has this key, correct the key or add the required record. If there is already a record with this key, a problem exists in the CallPath/CICS software. Contact your service representative.

EQZ0443A The number entered must be 1 or 2

Explanation: The value entered was not valid.
System Action: None.
User Response: Enter a value of 1 (single step) or 2 (multi step).

EQZ0444A Unable to place message onto application message queue

Explanation: Due to an error in an internal module the simulator was unable to place the message onto the application message queue specified by the program name entered on the screen.
System Action: Screen is redisplayed. No messages are processed.
User Response: Check the system log for further messages describing the cause of the problem with the internal EQZ2FANO module.

EQZ0445A Type a number between 1 and 4

Explanation: The user has typed an invalid option number, which must be in the range 1 to 4 inclusive.
System Action: None
User Response: Type a valid option number and press Enter.

EQZ0446A Last 5 characters of sequence number must be numeric

Explanation: The user has typed an invalid sequence number. The last 5 characters must be numeric. (The first 5 can be alphanumeric.)
System Action: None
User Response: Type a valid sequence number and press Enter.

EQZ0447A First 5 characters of sequence number must be alphanumeric

Explanation: The user has typed an invalid sequence number. The first 5 characters must be alphanumeric. (The last 5 must be numeric.)
System Action: None
User Response: Type a valid sequence number and press Enter.

EQZ0448A End Sequence Number must be greater than start Sequence Number

Explanation: Self-explanatory.
System Action: None
User Response: Type a valid sequence number and press Enter.

EQZ0449A A CICS error has occurred whilst reading the Message file

Explanation: Self-explanatory.
System Action: None
User Response: Refer to the CICS documentation

EQZ0557W Request ignored. Automatic communications recovery in progress.

Explanation: Communications with this switch have failed and the automatic communications recovery module has been invoked. You cannot start the switch manually while the automatic recovery module is running.

System Action: None.
User Response: If required, the switch can be manually stopped and then restarted. You may have to pause after stopping the switch to allow the automatic recovery module to terminate -- this can take up to a minute to complete.

EQZ0559A System error accessing internal table

Explanation: An attempt to access an internal table failed.

System Action: None.
User Response: None.

EQZ0560I Program Name entered cannot be found on internal table

Explanation: Self-explanatory.
System Action: None.
User Response: None.

EQZ0561I No records were found within the range specified

Explanation: Self-explanatory.
System Action: None.
User Response: None.

EQZ0562W Maximum start sequence number reached

Explanation: Self-explanatory.
System Action: None.
User Response: None.

EQZ0600I This message is currently being updated by another user

Parameters: rc
Explanation: Another user is currently in the process of updating or deleting this record. Each message can only be updated by one user at a time.
User Response: Wait for the message to be freed by the other user.

EQZ0601I This record no longer exists. Press F5 to refresh the screen.

Parameters: rc
Explanation: The record you requested has been deleted by another user since the list was first displayed on the screen.
User Response: Press F5 to obtain a fresh copy of the list of available messages.

EQZ0602A Message updated by another user. Changes have been cancelled.

Parameters: rc
Explanation: The message that you were using has been updated by another user in the time that you were making your changes. The changes that you entered have not been saved.
User Response: Re-enter your changes.

EQZ0603I The record has not been deleted

Parameters: rc
Explanation: Your request to delete the message has been cancelled.
User Response: None.

EQZ0604A Enter timestamp in correct format. Press F1 for help.

Explanation: The timestamp must be in the format YYYYMMDDHHMMSS.TTT.
User Response: Correct the format.

EQZ0605A This is a mandatory field - it cannot be left blank

Explanation: The highlighted field has not had a value entered in it but it is a mandatory field. A valid value must therefore be entered.
User Response: Correct the format.

EQZ0606W Some records were not processed. See message log.

Explanation: Not all the records within the specified range were processed. See the message log for error details.

EQZ0607W Request_Instruction event data not found

Explanation: The simulator message extractor could not find the trigger_event_data associated with a Request_Instruction event.
System Action: None
User Response: Check the key for the trigger_event_data that is specified on the Request_Instruction event that you have loaded. Does a record exist with such a key? If no, then correct the key or add the required record.
If yes, there is an error in Call Management Control System software. Contact your service representative.

EQZ0608I Simulator message on file references a non-simulated switch

Explanation: The switch name on a message to be sent back to waiting applications is not in simulation mode, so cannot be processed by the simulator.

System Action: None.
User Response: None.

EQZ0609W Request_Instruction event data is not valid

Explanation: The Trigger_event_data in the Request_Instruction event contains an invalid event. It should be either a Call_Routed or a Setep.
System Action: None
User Response: Amend the key for the trigger_event_data contained in the Request_Instruction event so that it specifies an event type of either Call_Routed or Setup.

EQZ0612A CICS spooling error in print request

Explanation: An EXEC CICS SPOOLxxxxx command has failed when trying to write the print request to the batch reader queue.
System Action: The print request is not submitted.
User Response: Check system messages log for more details.

EQZ0615I A new CLONE switch has been added. Press PF5 to refresh the list.

Explanation: A CLONE switch has been added. To display it press PF5 to refresh.
System Action: None.
User Response: Hit PF5 to refresh the Switch list.

EQZ0730A Type a number between 1 and 4

Explanation: The user has typed an invalid option number, which must be in the range 1 to 4 inclusive.
System Action: None.
User Response: Type in a valid option number and press Enter.

EQZ0731I No records on Application Name table

Explanation: No Program_names are currently in use.
System Action: None.
User Response: None.

EQZ0732I Enter Program_name in correct format

Explanation: The Program_name must be in upper-case alphanumeric with no embedded blanks.
System Action: None.
User Response: Correct the format.

EQZ0733I Program_name not found

Explanation: The Program_name is not on the Application Name Table.
System Action: None.
User Response: None.

EQZ0734A Enter Call_profile_ID in correct format

Explanation: The Call_profile_ID must be in the format EQZnnnnn, where nnnnn is numeric.
User Response: Correct the format.

EQZ0735I No Call Profiles to display

Explanation: No Call Profiles are currently in use by the Program_name.
System Action: None.
User Response: None.

EQZ0736I Call_profile_ID not found

Explanation: Selected Call_profile_ID not on Call Profile table.
System Action: None.
User Response: None.

EQZ0737I No Message Queue records to display

Explanation: Application message queue for the Program_name contains no records.
System Action: None.
User Response: None.

EQZ0738I Selected Program_name has been released

Explanation: The Program_name has been deleted from the Application Name Table since the last screen display.
System Action: None.
User Response: None.

EQZ0739I Screen refreshed because of deleted records

Explanation: The list has been redisplayed from the first record because of records being deleted.
System Action: None.
User Response: None.

EQZ0740A You can select only one Call Profile

Explanation: The user has selected more than one Call Profile.
System Action: None.
User Response: Correct selection and press Enter.

EQZ0741A Call_profile_ID/Program_name mismatched

Explanation: The user has entered a Program_name and a Call_profile_ID, but the Call Profile does not belong to the Program_name.
System Action: None.
User Response: Delete one of the selections and press Enter.

EQZ0742A You can select only one Program_name

Explanation: The user has selected more than one Program_name.
System Action: None.
User Response: Correct selection and press Enter.

EQZ0743A Type a number between 1 and 3

Explanation: The user has typed an invalid option number, which must be in the range 1 to 3 inclusive.
System Action: None.
User Response: Type a valid option number and press Enter.

EQZ0745I Call Profile has been deleted

Explanation: The Call Profile has been deleted from the table since the last screen display.
System Action: None.
User Response: None.

EQZ0746A Error loading module EQZTDTAB. Run transaction EQIV to verify.

Parameters: rc
Explanation: An EXEC CICS LOAD command on program EQZTDTAB failed with a return code of rc.
System Action: No further processing can be done from this panel.
User Response: Run IVP. Consult your local systems programmer.

EQZ0747I More than 100 messages on queue

Explanation: The application's message queue contains more than 100 records.
System Action: Only the first 100 will be listed.
User Response: None. @@@

Messages Logged in the CallPath/CICS Message Log

The following messages are logged to the message log while your system is running. Position the cursor on the online message display and press F2 to view the associated parameters, if available.

EQZ0001A INTERNAL FUNCTION PARAMETER IS NOT VALID

Parameters: x
Explanation: An internal problem has occurred in CallPath/CICS. The function parameter x passed on an internal call is not valid.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0002A MESSAGE NOT LOGGED. INTERNAL PARAMETER IS NOT VALID.

Parameters: aaaaaaaa, bbbb
Explanation: An internal problem has occurred in CallPath/CICS. A system message cannot be logged. Module aaaaaaaa cannot log message number EQZbbbb because one or more input parameters are not valid.
System Action: The module ends without logging the message. See the system action for message EQZbbbb to find out if any part of the system can no longer function.
User Response: Follow the procedure suggested for message EQZbbbbb.

Contact your service representative.

EQZ0003W TRACING SWITCHED OFF. MODULE NAME IS NOT VALID.

Parameters: aaaaaaaa
Explanation: An internal problem has occurred in CallPath/CICS. The module name parameter aaaaaaaa passed on an internal call is not valid.
System Action: The program that invoked the trace module has switched off tracing. Application programs will continue to run without tracing.
User Response: Contact your service representative.

EQZ0004W TRACING SWITCHED OFF. RECORD TYPE IS NOT VALID.

Parameters: aaaaaaaa, bb
Explanation: An internal problem has occurred in CallPath/CICS. The record type parameter bb passed to the trace module is not valid. The calling module is aaaaaaaa.
System Action: The program that invoked the trace module has switched off tracing. Application programs will continue to run without tracing.
User Response: Contact your service representative.

EQZ0005W TRACING SWITCHED OFF. NO POINT OF CALL SPECIFIED.

Parameters: aaaaaaaa, bb
Explanation: An internal problem has occurred in CallPath/CICS. No point of call code bb was passed to the trace module to identify the location in the source code where the trace record is being requested. The calling module is aaaaaaaa.
System Action: The program that invoked the trace module has switched off tracing. Application programs will continue to run without tracing.
User Response: Contact your service representative.

EQZ0006A DIRECTORY NUMBER LENGTH NOT IN RANGE 1 TO 32 INCLUSIVE

Parameters: nn
Explanation: An internal problem has occurred in CallPath/CICS. The directory number length nn is not in the range of 1 to 32 inclusive.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0007A DIRECTORY NUMBER IS NOT ALPHANUMERIC

Parameters: aaaaaa
Explanation: An internal problem has occurred in CallPath/CICS. Directory number aaaaaa must consist of characters in the character set 01134 (numbers and uppercase letters) or the special characters '&star.' and '&'.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0011A UNSUCCESSFUL CALL TO MODULE EQZXEQSQ

Parameters: rc
Explanation: An internal problem has occurred in CallPath/CICS. A call to the subsystem queue access module was unsuccessful. The return code was rc.
System Action: Processing stops for this module.
User Response: Look for an error message in the destination of the extrapartition transient data queue CSSL. If CallPath/CICS cannot write to its own message log, it writes messages to this queue. The messages have a JTYPE value of EQ.

Contact your service representative.

EQZ0012W TRACING SWITCHED OFF. UNSUCCESSFUL CALL TO MODULE EQZXTRCE.

Parameters: rc
Explanation: An internal problem has occurred in CallPath/CICS. A call to the trace module was unsuccessful. The return code was rc.
System Action: The program that started the trace module has switched off tracing. Application programs will continue to run without tracing.
User Response: Contact your service representative.

EQZ0013A AN INTERNAL REQUEST TAG TABLE HEADER IS CORRUPT

Parameters: s, literal
Explanation: An external program may have corrupted CallPath/CICS storage, or there may be an internal problem in the CallPath/CICS software.

The request tag table header does not contain the correct literal identifying the table. Instead, it contains the literal literal. The problem occurred when the switch entry with switch code s was processed.
System Action: Processing stops for this module and control returns to the initiating program. No more request tags can be allocated to requests to this switch. All program calls that require request tags will fail. Events will not be passed from the switch to application programs.
User Response: Shut down and then restart communications with the affected switch. If the problem persists and you are sure that your external programs are not corrupting CallPath/CICS storage, contact your service representative.

EQZ0014A INTERNAL RESPONSE TYPE PARAMETER IS NOT VALID

Parameters: r
Explanation: An internal problem has occurred in CallPath/CICS. The response type parameter r passed on an internal call is not valid.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0015A INTERNAL REQUEST TYPE PARAMETER IS NOT VALID

Parameters: r
Explanation: An internal problem has occurred in CallPath/CICS. The request type parameter r passed on an internal call is not valid.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0016A INTERNAL APPLICATION ID PARAMETER IS NOT VALID

Parameters: aaaaaaaa
Explanation: An internal problem has occurred in CallPath/CICS. The application ID parameter aaaaaaaa passed on an internal call is not valid.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0017A UNSUCCESSFUL CALL TO MODULE EQZXEQEH

Parameters: s, rc
Explanation: An internal problem has occurred in CallPath/CICS. A call to the event handler queue access module was unsuccessful. The return code was rc. Switch code s indicates the event handler queue for which the access attempt was made.
System Action: In most cases the calling module will end processing, but the Request Handler will attempt to continue processing if it gets this error.
User Response: Look at the other logged messages. Messages with the same task number are likely to be caused by the same problem. They will tell you if any part of the system can no longer function and may provide additional information to help diagnose the problem.

If the system messages do not reveal the problem, contact your service representative.

EQZ0018A UNSUCCESSFUL CALL TO MODULE EQZXSWDC

Parameters: rc
Explanation: An internal problem has occurred in CallPath/CICS. A call to the switch description access module was unsuccessful. The return code was rc.
System Action: Processing stops for this module.
User Response: Contact your service representative.

EQZ0019A REQUEST TAG TABLE ENTRY IS EMPTY

Parameters: s, nn
Explanation: An internal problem has occurred in CallPath/CICS. The request tag entry for tag number nn in the internal request tag table for switch code s contains no data.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0020A FREE SPACE IN AN INTERNAL REQUEST TAG TABLE IS CORRUPT

Parameters: s, nn
Explanation: An internal problem has occurred in CallPath/CICS software, or an external program has corrupted CallPath/CICS storage. The system could not use free space contained in an internal request tag table because the storage area was not initialized correctly.

The request tag table is identified by the switch code s, and the corrupted entry is for tag number nn.
System Action: Processing stops for this module and control returns to the initiating program. The system cannot allocate request tags to requests for this switch. All program calls to the switch that require request tags will fail.
User Response: Shut down and then restart communications with the affected switch. If the problem persists and you are sure that your external programs are not corrupting CallPath/CICS storage, contact your service representative.

EQZ0021A AN INTERNAL REQUEST TAG TABLE IS FULL

Parameters: s
Explanation: The internal request tag table for the switch identified by the code s is full. The following are possible causes:

CallPath/CICS storage limit reached
CICS storage limit reached
Request for more storage not yet processed
Request tag entries are not being freed.

System Action: Processing stops for this module and control returns to the initiating program. No more request tags can be allocated to requests for this switch, so all subsequent program calls that require request tags will fail.
User Response: Look at the other logged messages. Messages with the same task number are likely to be caused by the same problem. They will tell you if any part of the system can no longer function and may provide additional information to help diagnose the problem.

If the system messages do not reveal the problem:

Retry the program call. Storage may have become available.
If CICS has sufficient storage available, shut down the administration subsystem and increase the storage limit of CallPath/CICS.
If the problem persists, contact your service representative.

EQZ0022A INTERNAL TABLE NAME PARAMETER IS NOT VALID

Parameters: tttttttt
Explanation: An internal problem has occurred in CallPath/CICS. The table name parameter tttttttt passed on an internal call requesting more storage is not valid.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0023A SWITCH CODE NOT FOUND ON INTERNAL SWITCH TABLE

Parameters: s
Explanation: An internal problem has occurred in CallPath/CICS. Switch code s was not found on the internal switch description table.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0024A CICS GETMAIN COMMAND FAILED

Parameters: rc
Explanation: There may be insufficient CICS storage, or there may be an internal problem in CallPath/CICS software. A CICS GETMAIN command to obtain storage for an internal system table failed with a response code of rc.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Refer to your CICS documentation for an explanation of the response code for the command:

If the response code indicates no available storage, the CICS storage limit has been reached. Investigate how much storage is used by current active tasks. Allocate more storage if necessary.
If the response code indicates a length error in the CICS GETMAIN command, a problem exists in the CallPath/CICS software. Contact your service representative.

EQZ0025A CALLPATH CICS SCT STORAGE LIMIT REACHED

Parameters: tttttttt
Explanation: CallPath/CICS does not have enough storage available. An attempt to create or extend the internal table tttttttt was unsuccessful because the system storage limit specified in the SCT was reached.
System Action: Processing stops for this module and control returns to the initiating program.
User Response:

Look to see if any application programs are building up message queues without executing STLRCV. If so, ask your system administrator to run the Queue Clean program.
You may need more storage to support the activity of your system. Shut down CallPath/CICS and increase the storage limit that is specified in the SCT.

EQZ0026A CALLPATH CICS TABLE ALLOCATION TOO SMALL

Parameters: tttttttt
Explanation: Either there is an internal problem in the CallPath/CICS software, or the SCT has been corrupted. CallPath/CICS cannot create or extend the internal table tttttttt because insufficient storage is specified for the table in the SCT. (You cannot configure this quantity.)
System Action: CallPath/CICS cannot create or extend the internal table.
User Response:

Shut down and then restart CICS
If the problem persists, contact your service representative.

EQZ0027A TABLE NAME NOT KNOWN

Parameters: tttttttt
Explanation: An internal problem has occurred in CallPath/CICS. A system request to extend the internal table tttttttt was unsuccessful. The table name is not defined in the SCT.
System Action: Switch-dependent internal tables cannot be extended. Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0028A CICS FREEMAIN COMMAND FAILED

Parameters: resp
Explanation: A CICS FREEMAIN command to free CICS storage failed with a response code of resp.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Refer to your CICS documentation for an explanation of response codes for this command. If the response code indicates that a problem exists in the CallPath/CICS software, contact your service representative.

Look at the other logged messages. Messages with the same task number are likely to be caused by the same problem. They will tell you if any part of the system can no longer function and may provide additional information to help diagnose the problem.

EQZ0030I APPLICATION NAME TABLE ALREADY AT FULL SIZE

Explanation: A maximum of 999 applications can use CallPath/CICS at any time. A request to extend the application name table was unsuccessful because 999 entries are already available.
System Action: No more application name entries can be allocated.
User Response: Ensure that your application programs issue the STLREL program call when they finish using CallPath/CICS.

EQZ0031I SUBSYSTEM IS NOT ACTIVE

Explanation: The CallPath/CICS Queue Clean program has been run. However, the administration subsystem is not currently active, so there are no internal tables to clean up.
System Action: The Queue Clean program ends normally.
User Response: None.

EQZ0032I THE APPLICATION NAME TABLE IS EMPTY

Explanation: The CallPath/CICS Queue Clean program has been run although no applications are currently using CallPath/CICS.
System Action: The Queue Clean program ends normally.
User Response: None.

EQZ0033A UNSUCCESSFUL CALL TO MODULE STLREL

Parameters: rc,nnnnnnnn
Explanation: The CallPath/CICS Queue Clean program did not run successfully. In processing CSA program name nnnnnnnn the STLREL program call produced a return code of rc.
System Action: The Queue Clean continues processing the next CSA program name.
User Response: Look up the return code rc in the CallPath/CICS for OS/390 Application Programming Guide to see the cause of the problem.

EQZ0034A NO DATE SUPPLIED FOR INTERNAL FORMATTING

Explanation: An internal problem has occurred in CallPath/CICS. The date and time formatting module has been called without passing a system date to be formatted.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0035A INPUT PARAMETER COMBINATION IS NOT VALID

Explanation: An internal problem has occurred in CallPath/CICS. Both CICS ABSTIME and ASN.1 date formats were passed to the date and time formatting module. Only one date format is required.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0036A ASN.1 DATE FORMAT IS NOT VALID

Explanation: An internal problem has occurred in CallPath/CICS. The ASN.1 date input parameter to the date and time formatting module is not valid. It must be a number with three decimal places.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0037A CICS ABSTIME DATE FORMAT IS NOT VALID

Explanation: An internal problem has occurred in CallPath/CICS. The CICS ABSTIME date input parameter to the date and time formatting module is not valid. It must be a number.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0038A WRITE TO A CICS TRANSIENT DATA QUEUE FAILED

Parameters: qqqqqqqq, resp
Explanation: The CICS command WRITEQ TD could not write to the transient data queue qqqqqqqq. The response code was resp.
System Action: Processing stops for this module and control returns to the initiating program.
User Response:

Refer to your CICS documentation for an explanation of response codes for this command.
Look at the other logged messages. Messages with the same task number are likely to be caused by the same problem. They will tell you if any part of the system can no longer function and may provide additional information to help diagnose the problem.

EQZ0040A SWITCH CODE PARAMETER IS NOT VALID

Parameters: s
Explanation: An internal problem has occurred in CallPath/CICS. The switch code parameter s passed on an internal call is not valid.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0041A SWITCH INFORMATION MISSING FROM INPUT

Explanation: An internal problem has occurred in CallPath/CICS. Both the switch code and the switch name parameters passed to an internal module are blank.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0042A MISLEADING SWITCH INFORMATION PASSED AS INPUT

Parameters: s, nnnnnnnn
Explanation: An internal problem has occurred in CallPath/CICS. Both switch code s and switch name nnnnnnnn have been passed to an internal module. Only one value is required.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0043A SWITCH NOT FOUND IN FULL SWITCH DESCRIPTION TABLE

Parameters: s, nnnnnnnn
Explanation: An internal problem has occurred in CallPath/CICS. The switch entry identified by switch code s and switch name nnnnnnnn cannot be found in the switch table. The switch table is full.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0044A THE INTERNAL SWITCH TABLE HEADER IS CORRUPT

Parameters: s, literal
Explanation: An external program may have corrupted CallPath/CICS storage, or there may be an internal problem in the CallPath/CICS software.

Literal literal, which identifies the table in the table header, is incorrect.

The system is currently processing the switch entry identified by switch code s.
System Action: Processing stops for this module and control returns to the initiating program.
User Response:

Look at the other logged messages. Messages with the same task number are likely to be caused by the same problem. They will tell you if any part of the system can no longer function and may provide additional information to help diagnose the problem.
Shut down and then restart communications with the affected switch. If the problem persists, contact your service representative.

EQZ0045A LENGTH OF TRANSACTION DATA EXCEEDED LIMIT

Parameters: nnn
Explanation: An internal problem has occurred in CallPath/CICS. The length nnn of the transaction passed as input to an internal module exceeds the maximum length allowed.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Look at the other logged messages. Messages with the same task number are likely to be caused by the same problem. They will tell you if any part of the system can no longer function and may provide additional information to help diagnose the problem.

Contact your service representative.

EQZ0046A CICS CANCEL COMMAND FAILED

Parameters: aaaaaaa, resp
Explanation: A CICS CANCEL command on request identifier aaaaaaa failed with a CICS response code of resp.
System Action: The call to the internal module is rejected.
User Response:

Look at the other logged messages. Messages with the same task number are likely to be caused by the same problem. They will tell you if any part of the system can no longer function and may provide additional information to help diagnose the problem.
Refer to your CICS documentation for an explanation of this response code for this command. If the response code indicates a problem exists in the CallPath/CICS software, contact your service representative.

EQZ0047A PROGRAM NAME INFORMATION MISSING FROM INPUT

Parameters: nnnnnnnn, iiiiiiii
Explanation: An internal problem has occurred in CallPath/CICS. Application name nnnnnnnn and application ID iiiiiiii were passed to an internal module as blanks.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0048A THE INTERNAL APPLICATION NAME TABLE HEADER IS CORRUPT

Explanation: An external program may have corrupted CallPath/CICS storage, or there may be an internal problem in the CallPath/CICS software.

The literal which identifies the table in the application name table header, is incorrect.
System Action: Processing stops for this module and control returns to the initiating program.
User Response:

Look at the other logged messages. Messages with the same task number are likely to be caused by the same problem. They will tell you if any part of the system can no longer function and may provide additional information to help diagnose the problem.
Shut down and then restart the administration subsystem. If the problem persists, contact your service representative.

EQZ0049A INVALID APPLICATION NAME INPUT PARAMETER

Parameters: nnnnnnnn
Explanation: An internal problem has occurred in CallPath/CICS. The first character of the application name nnnnnnnn input parameter was passed as blank.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0050A INVALID APPLICATION ID INPUT PARAMETER

Parameters: iiiiiiii,
Explanation: An internal problem has occurred in CallPath/CICS. The application ID parameter iiiiiiii passed on an internal call is not valid.
System Action: Processing stops for this module and control returns to the initiating program.
User Response: Contact your service representative.

EQZ0051A NO FREE SPACE AVAILABLE ON THE APPLICATION NAME TABLE

Explanation: The internal application name table cannot register your program name because it contains no free space.
System Action: The API program issues a return code of 12 (STL_RESOURCES_UNAVAILABLE) to the application program. No further program names can be identified to CallPath/CICS.
User Response: The Queue Clean program should be run by the system administrator to free up resources reserved for application programs that have not made a program call for longer than a predetermined period of time, which is defined in the system configuration table.

Ensure that applications issue the STLREL API call to free resources when they are no longer required.

EQZ0052A FREE SPACE IN THE INTERNAL APPLICATION NAME TABLE IS CORRUPT

Explanation: An external program may have corrupted CallPath/CICS storage, or there may be an internal problem in the CallPath/CICS software. An attempt to use free space in an internal application name table failed because the storage area is not initialized correctly. This indicates that the storage area has been corrupted.
System Action: Processing stops for this module and control returns to the initiating program. Program names cannot be identified to CallPath/CICS by the STLIDEN program call until the problem is resolved.
User Response: The Application Name Table load module needs to be refreshed which will cause the loss of all resources for currently assigned program names.

Shut down the administration subsystem
Ask your systems programmer to newcopy the Application Name Table load module EQZTANT
Restart the administration subsystem.

If the problem persists and you are sure that your external programs are not corrupting CallPath/CICS storage, contact your service representative.

EQZ0053A FAILED TO LOAD APPLICATION NAME TABLE

Parameters: tttttttt, resp
Explanation: The CICS LOAD command failed to load table tttttttt into main storage. The response code was resp.
System Action: Proc