This chapter contains all of the CallCoordinator messages in alphanumeric sequence with an explanation of each message and the action you should take.
The prefix of the message, CAM or EZP identifies it as a CallCoordinator message.
CallCoordinator sends three types of messages during the operation of the system. The suffix of the message number identifies the message type:
EZP0031E Year must be 00 - 99
EZP0017I Request has been processed
CAMS908W Request handler is busy; try later
Some of the messages printed in this section contain representations of variable data. When the message appears on panels or in logs, the correct information appears in the variable area. The following is an example of a message with variable information:
|
Message appears in this section in this format:
Return code <aaaa> during <bbbbbbbbbb>, pgmid <cccccccc>
Message appears on panel or in log in this format:
Return code 0027 during LINK, pgmid EZPACTLC
|
Appendix A contains tables that can assist you in interpreting table or program names.
Some messages contain references to CICS return codes. For the meanings of those return codes, refer to the Application Programmers' Reference, for your version of CICS. You also might need to refer to the CallPath CallCoordinator/CICS Application Programming Guide for return and reason codes returned from APIs.
| CAMA101E |
| Bal Pt1 equal to or greater than Bal Pt2 |
Explanation: Bal Pt1 is the number of calls that can be handled comfortably; Bal Pt2 is the maximum number of calls that can be handled. Bal Pt1 must be less than Bal Pt2, unless they both are 0.
Your response: Type valid Bal Pt1 and Bal Pt2 values.
| CAMA102I |
| CallCoordinator is already running |
Explanation: You made a request to start up CallCoordinator. CallCoordinator is already running.
Your response: None.
| CAMA103I |
| CallCoordinator is not running, no action taken |
Explanation: Shutdown was selected, but the Long Running Tasks are not active, so CallCoordinator is already shut down.
Your response: Investigate if the system is down because a shutdown was requested or due to some trouble in Long Running Tasks processing.
Your response: None.
| CAMA104E |
| Switch is already active |
Explanation: Switch activation was selected, but the switch is already active.
Your response: None.
| CAMA105E |
| Switch is not currently active |
Explanation: Switch de-activation was selected, but the switch is already active.
Your response: None.
| CAMA106E |
| Target COR is inactive |
Explanation: Switch cannot be activated in the selected COR because the COR is not active.
Your response: Start CallCoordinator in the selected COR using the Startup function from the COR Operations panel, or select an active COR in which to activate the switch.
| CAMA107E |
| Switch is already active in target COR |
Explanation: Switch activation was selected, but the switch is already active in the targeted COR.
Your response: None.
| CAMA108E |
| Type Screen Delay value between 1 - 180 |
Explanation: You typed a value outside the valid range of 1-180 seconds.
Your response: Type a value within the valid range.
| CAMA109E |
| Group is only required for Resource type 3 |
Explanation: The group field is only required to be entered if the resource type is 3.
Your response: Change the group field to blanks and continue.
| CAMA117E |
| CICS Journaling required , enter Id between 2 and 99 |
Explanation: This field must contain a number in the range 2 to 99, because the MIS Log File Suffix Field contains a 'J' , which indicate CICS User Journaling is to be used for MIS Log processing.
Your response: Change the Journal Id field to contain a valid journal Id ( 2 - 99 ) or change MIS Log File Suffix field to A or B or blank.
| CAMA118E |
| Invalid journal id - check JCT table and CICS JCL |
Explanation: There is no entry in the JCT table and/or there are no journal datasets defined in the JCL at CICS startup.
Your response: Check that the journal Id you use does exist and is defined to CICS. See the CICS Operations Guide for more information.
| CAMA119E |
| MIS Exit name must be provided for File Suffix of X |
Explanation: If you select MIS Log file suffix of X (process MIS Exit only) a MIS Exit name must be supplied.
Your response: Enter a MIS Exit name or enter a different MIS Log file suffix.
| CAMA125E |
| Switch ID is not in switch table or is not > |
Explanation: Switch ID entered is not defined in the Switches table, or the entry is not > for default.
Your response: Type a valid Switch ID or >.
| CAMA126E |
| From Switch same as To Switch |
Explanation: The From Switch ID is the same as the To Switch ID.
Your response: Type different From and To Switch IDs.
| CAMA127E |
| Function Backup Tel No entry required for default entry |
Explanation: A default entry requires a number in the Function Backup Tel No field.
Your response: Type a valid number in the Function Backup Tel No field.
| CAMA130E |
| Create a default entry for this ACD Group first. |
Explanation: You must create a default entry for each ACD Group.
Your response: Type > in the Function field for this ACD Group entry. Then type a number in the Function Backup Tel No field and press enter.
| CAMA132E |
| Delete of default entry not permitted |
Explanation: Delete of the default entry is not permitted while entries with the same key fields exist in the table. Key fields are those fields that serve as indexes for a record in the file.
Your response: Delete entries with the same key first.
| CAMA133E |
| Change of default entry key fields not permitted |
Explanation: Change of the default entry key fields is not permitted while entries with the same key fields exist in the table. Key fields are those fields that serve as indexes for a record in the file. Such fields cannot be changed.
Your response: Delete entries with the same key first.
| CAMA134E |
| Not a valid value - type value other than C |
Explanation: You typed a value of C. It is reserved for use by CallCoordinator components.
Your response: Type a value other than C.
| CAMA139E |
| Use API Verification Utility panel to access |
Explanation: You tried to access directly a menu transaction. Menu transactions can be accessed only from the menu.
Your response: Select this transaction from the API Verification Utility menu.
| CAMA140E |
| Insert action does not allow fields to be changed |
Explanation: You tried to change fields on an insert request.
Your response: Press F5 to refresh and get rid of changes and type 4 as action code.
| CAMA141E |
| Entry must be A-Z, 0-9, &&, *, or > |
Explanation: You can type only uppercase letters A through Z, the numerals 0 through 9, an ampersand (&), or an asterisk (*), if you are entering a target pilot number in this field.
If you are entering a default entry, you must enter the "greater than" sign (>) in the first position in this field. The > sign cannot be entered in combination with other characters.
Your response: Type the correct character.
| CAMA142E |
| Entry must be A-Z, 0-9, or > |
Explanation: You can type only uppercase letters A through Z or the numerals 0 through 9 for the function.
If you are entering a default entry, you must enter the "greater than" sign (>) in the first position in this field. The > sign cannot be entered in combination with other characters.
Your response: Type the correct character.
| CAMA150E |
| Entry must be 1 for non-Sysplex |
Explanation: This field must contain a value of "1" because your environment is defined as non-Sysplex.
Your response: Type a "1" in this field. If you wish to use a different value, you may change the Sysplex Indicator field on the System Configuration panel (VA30) and come back to this panel.
| CAMA151E |
| Entry must be blank for non-Sysplex |
Explanation: This field must contain a value of blank because your environment is defined as non-Sysplex.
Your response: Blank this field out. If you wish to use a different value, you may change the Sysplex Indicator field on the System Configuration panel (VA30) and come back to this panel.
| CAMA152E |
| Entry must be N for non-Sysplex |
Explanation: This field must contain a value of "N" because your environment is defined as non-Sysplex.
Your response: ype an "N" in this field. If you wish to use a different value, you may change the Sysplex Indicator field on the System Configuration panel (VA30) and come back to this panel.
| CAMA153E |
| SysID not defined on General Resource File |
Explanation: This field must contain a value of a COR defined in the General Resource file. CORs are defined on the System configuration panel (VA30)
Your response: Enter the name of a defined COR in this field. If your environment is non-Sysplex, then this field should be left blank.
| CAMA154E |
| Alternate SysID must not be the same as actual SysID |
Explanation: When choosing the recovery options the Alternate SysID has been set to the same as the actual Sysid.
Your response: Select a valid SysID that is different from the actual SysID.
| CAMA155E |
| Copy option available only for Sysplex Environment |
Explanation: You have selected option 5 on the configuration panel to copy a configuration to create a new COR description. This option is only valid in a Sysplex environment.
Your response: Choose a valid option or exit the configuration menu.
| CAMA160E |
| MIS and Trace Journal IDs must be unique |
Explanation: The MIS and Trace Journal IDs must not be the same.
Your response: Change the MIS Journal ID or the Trace Journal ID to another value to prevent MIS and Trace data from going to the same journal destination.
| CAMA200E |
| LOAD ERROR - TABLE <aaaaaaaa> LOADED ENTRIES <bbbb> VSAM FILE ENTRIES <cccc> |
Explanation: The table is not large enough to hold the number of entries on the VSAM file.
Your response: Contact the IBM Support Centre (ISC) for assistance.
| CAMA210E |
| SysID not defined in CAMTCORS TS Queue. |
Explanation: During the startup of CallCoordinator in a Sysplex environment, a SysID was passed that has not been defined to the system.
Your response: Ensure that all valid SysIDs are defined on the system configuration panel. In case of further difficulties contact the IBM Support Centre (ISC) for assistance.
| CAMA500I |
| BEGIN CALLCOORDINATOR TABLE LOAD AND START UP VIA - PLT - |
Explanation: CallCoordinator has been initialized through the CICS PLTPI startup process.
Your response: None. This message is for information only.
| CAMA501I |
| BEGIN CALLCOORDINATOR TABLE LOAD VIA - MENU - |
Explanation: CallCoordinator has been initialized through the System Administration Menu startup process.
Your response: None. This message is for information only.
| CAMA502I |
| STORAGE ACQUIRED FOR TABLE <aaaaaaaa> |
Explanation: CallCoordinator has acquired storage for the internal tables successfully.
Your response: None. This message is for information only.
| CAMA503I |
| TABLE <aaaaaaaa> LOADED, TABLE CONFIGURED FOR <bbbb> UTILIZATION AT START = <cccc> |
Explanation: CallCoordinator has loaded the internal table with the configured table size successfully.
Your response: None. This message is for information only.
| CAMA504I |
| <aaa> - LONG RUNNING TASK STARTED SUCCESSFULLY |
Explanation: CallCoordinator has started the long running tasks successfully.
Your response: None. This message is for information only.
| CAMA505I |
| END TABLE RELOAD |
Explanation: CallCoordinator has reloaded the internal tables successfully.
Your response: None. This message is for information only.
| CAMA506I |
| TABLE <aaaaaaaa> RELOADED, TABLE CONFIGURED FOR <bbbb> UTILIZATION AT START = <cccc> |
Explanation: CallCoordinator has reloaded the internal table with the configured table size successfully.
Your response: None. This message is for information only.
| CAMA507I |
| BEGIN CALLCOORDINATOR START UP VIA - MENU - |
Explanation: CallCoordinator has started the long running tasks requested from the CallCoordinator Start Up/Shut Down panel.
Your response: None. This message is for information only.
| CAMA508I |
| <aaaaaaaa> TABLE LOADED |
Explanation: CallCoordinator has loaded an internal table into CICS memory successfully.
Your response: None. This message is for information only.
| CAMA509I |
| END CALLCOORDINATOR TABLE LOAD |
Explanation: CallCoordinator has completed the table load and initialization functions successfully.
Your response: None. This message is for information only.
| CAMA510I |
| CALLCOORDINATOR START UP SUCCESSFUL |
Explanation: CallCoordinator has completed startup functions successfully.
Your response: None. This message is for information only.
| CAMA511E |
| RELEASE FOR TABLE <aaaaaaaa> FAILED |
Explanation: During the initialization process for CallCoordinator, CallCoordinator could not release the CallCoordinator tables from CICS memory.
Your response:
| CAMA512E |
| TABLE LOAD FOR <aaaaaaaa> FAILED |
Explanation: During the initialization process for CallCoordinator, CallCoordinator could not load the CallCoordinator tables into CICS memory.
Your response:
| CAMA513E |
| LINK TO CAMA821C PROGRAM FAILED |
Explanation: The host computer loaded the CallCoordinator program tables to memory, then linked to the data-load program to load the CallCoordinator configuration data from VSAM files into the CallCoordinator tables. This error message indicates that CallCoordinator could not link to the data-load program and, therefore, could not load the CallCoordinator configuration data.
Your response:
| CAMA514E |
| START FOR - <aaa> - FAILED |
Explanation: CallCoordinator could not start the long running task shown.
Your response:
| CAMA515E |
| UNAUTHORIZED ACCESS TO THIS PROGRAM |
Explanation: The CallCoordinator system initialization process started incorrectly. An unauthorized person probably tried to access the system program on the host computer.
Your response: Monitor the CICS system log. If the message appears again, ask the security group at your facility for advice.
| CAMA516E |
| NO INFORMATION ON CONFIGURED TABLES, CANNOT PROCEED |
Explanation: The CallCoordinator system initialization process could not proceed with the initialization function because no information was found on the configuration tables.
Your response: Monitor the CICS system log. If the message appears again, check the installation procedures or call System Support for advice.
| CAMA517E |
| MTS TABLE ''CAMSMTSL'' NOT AVAILABLE, CANNOT PROCEED |
Explanation: The CallCoordinator system initialization process could not proceed with the initialization function because the configuration table is not available.
Your response: Monitor the CICS system log. If the message appears again, check the installation procedures or call System Support for advice.
| CAMA518E |
| PROBLEM IN CAMA821C PROGRAM, CALLCOORDINATOR TABLE LOAD ABORTED |
Explanation: CallCoordinator found a problem while loading the VSAM configuration files for the CallPath tables.
Your response:
If the VSAM configuration file does not exist:
If CallCoordinator cannot read and write the CallCoordinator configuration data files because of a VSAM internal data structure problem:
| CAMA519E |
| RETURN CODE, <aaaa> - FROM <bbbbbbbb>, WHILE INITIALIZING TABLES WITH DATA |
Explanation: CallCoordinator found a problem while loading the VSAM configuration files for the CallPath tables.
Your response:
If the VSAM configuration file does not exist:
If CallCoordinator cannot read and write the CallCoordinator configuration data files because of a VSAM internal data structure problem:
| CAMA520E |
| RETURN CODE <aaaa> FROM PROGRAM ''CAMTACIN'', WHILE RELEASING STORAGE FOR <bbbbbbbb> |
Explanation: During the initialization process for CallCoordinator, CallCoordinator could not release the CallCoordinator tables from CICS memory.
Your response:
| CAMA521E |
| RETURN CODE <aaaa> FROM PROGRAM ''CAMTACIN'', WHILE ACQUIRING STORAGE FOR <bbbbbbbb> |
Explanation: The CallCoordinator system initialization process found errors in the table initialization program.
Your response: Monitor the CICS system log. If the message appears again, check for the installation procedures or call System Support for advice.
| CAMA522E |
| REQUEST FOR RELOAD REJECTED, CALLCOORDINATOR IS UP |
Explanation: Someone tried to reload the CallCoordinator system when it was already active. The CallCoordinator system must be shut down before it can be restarted.
Your response: Shut down the CallCoordinator system before reloading the system.
| CAMA524I |
| END CALLCOORDINATOR START UP |
Explanation: The CallCoordinator start up process has ended.
Your response: None. This is for information only.
| CAMA530I |
| BEGIN ''CALLCOORDINATOR STATUS MONITOR (CSM)'' |
Explanation: CallCoordinator has started the CallCoordinator Status Manager.
Your response: None. This message is for information only.
| CAMA531E |
| LONG RUNNING TASK -<aaa>- IS NOT ACTIVE, CALLCOORDINATOR IS SHUTTING DOWN. |
Explanation: The CallCoordinator long running task has not posted status information within the required time. CallCoordinator is therefore being shut down.
Your response:
| CAMA532E |
| LONG RUNNING TASK - <aaa> - HAS NOT POSTED TIME SINCE <bbbbbbbbbb> ON <cccccccccc> |
Explanation: The CallCoordinator long running task has not posted the status information since the time and date indicated.
Your response:
| CAMA533I |
| ''CALLCOORDINATOR STATUS MONITOR (CSM)'' LONG RUNNING TASK, V884, IS BEING RESTARTED |
Explanation: The CallCoordinator Status Manager is being restarted.
Your response: None. This message is for information only.
| CAMA534I |
| ENDING ''CALLCOORDINATOR STATUS MONITOR (CSM)'' PROCESS |
Explanation: CallCoordinator has ended the CallCoordinator Status Manager.
Your response: None. This message is for information only.
| CAMA535I |
| BEGIN TABLE RELOAD FUNCTION VIA CALLCOORDINATOR PROBLEM DETERMINATION PANEL |
Explanation: The table reload function has begun.
Your response: None. This is for information only.
| CAMA536E |
| CICS ERROR PROGRAM <aaaaaaaa> RETURN CODE <bbbb> |
Explanation: An error has occurred in program <aaaaaaaa> due to an unexpected return code from CICS.
Your response: Contact the IBM Support Centre.
| CAMA537E |
| ERROR IN PROGRAM <aaaaaaaa> FEEDBACK CODE <bbbb> |
Explanation: An unexpected error condition has occurred in program <aaaaaaaa).
Your response: Contact the IBM Support Centre.
| CAMA538I |
| CALLCOORDINATOR SHUTDOWN STARTED |
Explanation: The shutdown process for CallCoordinator has started.
Your response: None. This is for information only.
| CAMA539I |
| END CALLCOORDINATOR SHUTDOWN |
Explanation: The shutdown process for CallCoordinator has ended.
Your response: None. This is for information only.
| CAMA540E |
| MIS LRT HAS NOT POSTED SINCE <bbbbbbbbbb> ON <cccccccccc> - MIS PROCESSING DISABLED. |
Explanation: The CallCoordinator MIS long-running task has not posted status information within the required time. MIS processing has therefore been disabled. The likely cause of this problem is that the MIS long-running task is waiting on operator response for Journal archive.
Your response: After determining and correcting the source of the problem you should reset the MIS options flag on the Telephony Settings panel to reactivate MIS processing.
| CAMA541E |
| COR <aaaa> REGION FAILURE DETECTED - INITIATING RECOVERY |
Explanation: In a Sysplex environment CallCoordinator has detected that a COR has had a failure. The automatic recovery options set on the COR recovery policy panel will take effect.
Your response:
| CAMB003E |
| NO BACKUP NUMBER AVAILABLE, SWITCH <aaaaaaaa> FUNCTION <bbbbbbbbbb> |
Explanation: The system did not find a backup number in the Load Balancing Function table for the requesting switch. A backup number is necessary for every switch.
Your response:
| CAMB015W |
| NO INTER-SWITCH TRACKING NUMBER AVAILABLE FOR REQUESTED FUNCTION <aaaaaaaa> AND LEAST BUSY-ACD GROUP <bbbbbb> |
Explanation: This load-balancing error message indicates that an agent asked for a load-balanced number. However, no inter-switch tracking numbers are available because they are all in use (reserved).
Either the CallPath administrator did not configure enough inter-switch tracking numbers or agents are misusing the available reserve inter-switch tracking numbers by reserving the numbers and then not using them.
Your response: Monitor the MIS Log and resolve the problem by doing one or both of the following:
| CAMB016W |
| NO DEFAULT TGT ENTRY ON BAL PT TBL, SWITCH <aaaaaaaa> FUNCTION <bbbbbbbbbb> TGT <cccccccccc> |
Explanation: This load-balancing warning message indicates that the Balance Point table shows incorrect entries. The table lists each target number, with the Day and Time columns set to >, to get the defaults.
The Day and Time columns are probably not >.
Your response: Monitor the MIS Log and do the following:
Alternatively, you can list a target number more than once in the table. One entry must have Day and Time columns set to >, while the other entry can have exception times.
| CAMB023W |
| SWITCH NOT ON SWITCH TABLE, SWITCH <aaaaaaaa> |
Explanation: The switch in the Balance Point table does not have an entry in the Switches table.
Your response: This is a configuration error. Check the entries in the Switches table against the entries in the Transfer Load Balancing tables. Correct the entry or entries in error.
| CAMB024W |
| RETURN CODE <aaaa> FROM QUEUE COUNT UPDATE FOR ACD Group <bbbbbb> -- Target Pilot <cccccccccc> on Switch <dddddddd> |
Explanation: A request to update the queue count in the Transfer Load Balancing Balance Point table failed for the ACD Group listed. The Switch and Target Pilot number contained in the event message which indicates the need for a queue count update are also listed. The reason for the failure is identified by the return code
Your response: Take corrective action based on the return code:
| CAME001E |
| MESSAGE TOO LONG FOR EVENT QUEUE TABLE |
Explanation: An event or message was too long to fit into the Event Queue table.
Your response: Contact your IBM Software Support Center (ISC).
| CAME002E |
| MAXIMUM WAIT TIME EXCEEDED FOR QUEUE MANAGEMENT CTM DELAY |
Explanation: The maximum wait time of the Queue Management CTM Delay has been exceeded.
Your response:
| CAME003E |
| EVENT QUEUE CORRUPTED BEFORE WRITE |
Explanation: The event queue was corrupted before the event or message could be written to the queue.
Your response: Contact your IBM Software Support Center (ISC).
| CAME004E |
| EVENT QUEUE CORRUPTED AFTER WRITE |
Explanation: The event queue has been corrupted after the event or message was written to the queue.
Your response: Contact your IBM Software Support Center (ISC).
| CAMG003E |
| Use Agent Utility panel to access this transaction |
Explanation: You tried to directly access a menu transaction. Menu transactions can only be accessed from the menu.
Your response: Select this transaction from the Agent Utility menu.
| CAMG004I |
| Terminal has been disabled |
Explanation: The request to disable this terminal has been successfully completed. The terminal will not receive panels associated with incoming calls.
Your response: None.
| CAMG107I |
| Terminal has been enabled |
Explanation: The request to enable this terminal has been successfully completed. The terminal will now receive panels associated with incoming calls.
Your response: None.
| CAMG117E |
| Unable to perform screen copy |
Explanation: The screen copy was not successful.
Your response: Verify that the entry in the Ext ID field is correct, and try again.
| CAMM001E |
| CMCSGLBL ADDRESS LOAD ERROR FOR TABLE <aaaaaaaa> |
Explanation: An error occured while attempting to attain addressability for table <aaaaaaaa>.
Your response: Contact IBM support. If possible, provide a system dump of the CICS region affected.
| CAMM002I |
| BEGIN MIS LOG INTERFACE |
Explanation: CallCoordinator is loading the MIS Log module during a CallCoordinator startup.
Your response: None. This message is for information only.
| CAMM006I |
| END MIS LOG INTERFACE |
Explanation: The MIS Log module is stopping.
Your response: None. This message is for information only.
| CAMM007E |
| MIS MESSAGE QUEUE CORRUPTED |
Explanation: Writing to the MIS message queue caused a problem.
Your response:
| CAMM008E |
| BAD RESPONSE FROM EXEC CICS WAIT EVENT: <aaaa> |
Explanation: Executing the CICS WAIT EVENT command caused a problem. The CICS response code appears but the program continues.
Your response:
| CAMM009E |
| BAD RESPONSE FROM EXEC CICS WRITE: <aaaa> |
Explanation: Executing the CICS WRITE command caused a problem. The CICS response code appears but the program continues.
Your response:
| CAMM010E |
| BAD RESPONSE FROM EXEC CICS LINK: <aaaa> |
Explanation: Executing the CICS LINK command caused a problem. The CICS response code appears but the program continues.
Your response:
| CAMM011E |
| BAD RESPONSE FROM EXEC CICS SET ENABLED: <aaaa> |
Explanation: Executing the CICS SET ENABLED command caused a problem. The CICS response code appears and the program ends.
Your response:
| CAMM012E |
| BAD RESPONSE FROM EXEC CICS SET OPEN: <aaaa> |
Explanation: Executing the CICS SET OPEN command caused a problem. The CICS response code appears and the program ends.
Your response:
| CAMM013E |
| BAD RESPONSE FROM EXEC CICS START: <aaaa> |
Explanation: Executing the CICS START command caused a problem. The CICS response code appears and the program ends.
Your response: Check the response code in CICS Application Programmers' Reference. correct the error.
| CAMM028I |
| MIS MSG QUEUE WRITE CANNOT COMPLETE - CALLCOORDINATOR IS INACTIVE |
Explanation: An attempt was made to write to the MIS log while CallCoordinator was inactive. This could have been as a result of an MIS write from the MIS Write API, CAMI700C, or from a CallCoordinator module which tried to write to MIS during the shutdown phase.
Your response: If caused by API, check to see why API is being invoked while CallCoordinator is inactive. If caused by CallCoordinator, no response is necessary
| CAMM029E |
| MIS MSG QUEUE WRITE CORRUPTED |
Explanation: The message queue for the MIS Log contains incorrect data.
Your response: Call the IBM Software Support Center (ISC).
| CAMM030E |
| MIS MSG QUEUE WRITE POINTER IS OUT OF RANGE |
Explanation: The message queue write pointer for the MIS Log contains an incorrect non-numeric value.
Your response: Call the IBM Software Support Center (ISC).
| CAMM031E |
| MIS MSG QUEUE IS FULL, A MESSAGE HAS BEEN LOST |
Explanation: The message queue for the MIS Log overflowed.
Your response: Call the IBM Software Support Center (ISC).
| CAMM032E |
| BAD RESPONSE FROM EXEC CICS DELAY: <aaaaaaaa> |
Explanation: The system executive program gave an incorrect response.
Your response: Call the IBM Software Support Center (ISC).
| CAMM034E |
| INCORRECT TASK SEQUENCE ACTION REQUEST |
Explanation: An incorrect task sequencing action was requested. Valid actions are Request, Post, and Cancel.
Your response: Correct the action request and submit it again.
| CAMM035E |
| RETURN CODE <aaaa> FROM EXEC CICS JOURNAL: <bbbb> |
Explanation: A non-zero returned code was issued during a CICS WRITE JOURNAL command. The CICS return code appears in the message.
Your response: Check the response code in the CICS Applications Programmers Reference. The Journal number for the Write attempt is defined on the Telephony Settings screen, accessed through System Configuration option of the main Adiministrative menu (V800). Ensure that there is a JID entry for this Journal ID.
| CAMR001E |
| NO START DATA RECEIVED. RECOVERY MANAGER TERMINATING |
Explanation: The Recovery Manager transaction was not passed any input parameters by the calling program. The Recovery Manager transaction ends.
Your response: Contact IBM support. If possible, provide a system dump of the CICS region affected.
| CAMR002E |
| RECOVERY REASON <a> PASSED AS A PARAMETER <b> from <cccccccc> IS NOT VALID |
Explanation: The parameter value passed is not valid. The Recovery Manager transaction ends.
Your response: Contact IBM support. If possible, provide a system dump of the CICS region affected.
| CAMR003E |
| RETURN CODE cc READING <ffffffff> IN SYSID <ssss> |
Explanation: A READ of resource <ffffffff> failed in sysid <ssss> with a return code of cc. The Recovery Manager transaction ends.
Your response: Consult the relevant CICS documentation to determine the cause of the failure. Contact IBM support. If possible, provide a system dump of the CICS region affected.
| CAMR004E |
| RETURN CODE cc RECEIVED FROM <mmmmmmmm>. RECOVERY ATTEMPT FAILED |
Explanation: Recovery Manager received return code cc from called module <mmmmmmmm>. The Recovery Manager transaction ends.
Your response: Contact IBM support. If possible, provide a system dump of the CICS region affected.
| CAMR005E |
| RESTART ATTEMPT TO ALTERNATE COR <ssss> FAILED WITH RC=cc |
Explanation: An attempt to RESTART CallCoordinator in Alternate sysid <ssss> failed with return code cc. The Recovery Manager transaction ends.
Your response: Contact IBM support. If possible, provide a system dump of the CICS region affected.
| CAMR006I |
| RECOVERY OF CALLCOORDINATOR IN <ssss> HAS BEGUN |
Explanation: Recovery Manager is in the process of Recovering CallCoordinator in sysid <ssss>.
Your response: None.
| CAMR007I |
| RESTART OF CALLCOORDINATOR IN <ssss> HAS BEGUN |
Explanation: Recovery Manager is in the process of Restarting CallCoordinator in sysid <ssss>.
Your response: None.
| CAMR008I |
| RECOVERY MANAGER HAS SUCCESSFULLY RESTARTED SWITCH <nnnnnnnn> IN <ssss> |
Explanation: Recovery Manager has successfully restarted Switch <nnnnnnnn> in sysid <ssss>.
Your response: None.
| CAMR009I |
| RECOVERY MANAGER HAS SUCCESSFULLY RELOCATED SWITCHES FROM <ssss> TO <zzzz> |
Explanation: Recovery Manager has successfully relocated Switch <nnnnnnnn> in sysid <ssss>.
Your response: None.
| CAMR010I |
| RECOVERY/RESTART OF CALLCOORDINATOR IN <ssss> HAS COMPLETED SUCCESSFULLY |
Explanation: Recovery Manager has successfully recovered CallCoordinator in COR sysid <ssss>.
Your response: None
| CAMR011E |
| SWITCH NAME <aaaaaaaa> PASSED AS PARAMETER <x> FROM <bbbbbbbb> IS NOT VALID |
Explanation: The application program that invoked the Recovery Manager passed an incorrect switch name as an input parameter.
Your response: Make a note of the full text of the message and contact your Support Representative.
| CAMR012E |
| COR NAME <ssss> PASSED AS PARAMETER <x> FROM <bbbbbbbb> IS NOT VALID |
Explanation: The application program that invoked the Recovery Manager passed an incorrect COR name as an input parameter.
Your response: Make a note of the full text of the message and contact your Support Representative.
| CAMR013E |
| RETURN CODE <cccc> FROM CICS WTO COMMAND IN <ssss> |
Explanation: A CICS error occurred when the Recovery Manager issued a Write To Operator command.
Your response: Consult your CICS documentation to determine the full meaning of the error. If you determine that the error is not causedby a local problem contact your Support Representative.
| CAMR014E |
| RETURN CODE <cccc> FROM CICS WTOR COMMAND IN <ssss> |
Explanation: A CICS error occurred when the Recovery Manager issued a Write To Operator with Reply command.
Your response: Consult your CICS documentation to determine the full meaning of the error. If you determine that the error is not caused by a local problem contact your Support Representative.
| CAMR015I |
| RECOVERED SWITCH <aaaaaaaaaa> IN <ssss> HAD NO SIGNED ON AGENTS. |
Explanation: The switch that has been recovered in sysid <ssss> did not have any agents signed on.
Your response: This message is for information only. If you believe that agents would have been signed on to the switch before the problem that caused recovery:
| CAMR016I |
| AGENT SIGN ON TO RECOVERED SWITCH <aaaaaaaaaa> IN <ssss> IS COMPLETE |
Explanation: The Recovery Manager has completed the sign on of those agents that were previously registered.
Your response: None
| CAMR017I |
| RECOVERY IS SWITCHED OFF FOR SWITCH <aaaaaaaaaa>. IT WAS NOT RECOVERED. |
Explanation: Recovery Manager is attempting to recover all switches for a COR, however switch <aaaaaaaa> has had its recovery option set to no.
Your response: None
| CAMR018W |
| AGENT <aaaaaaaaaa> SIGN ON UNSUCCESSFUL DURING RECOVERY OF SWITCH <bbbbbbbb> |
Explanation: During the recovery or relocate of a switch, if the Recover Agents field on the COR Recovery Policy menu is set to 'Y', an attempt is made to sign on those agents that were previously signed on. In this instance agent <aaaaaaaaaa> could not be recovered.
Your response: None. The agent will need to sign on in the normal manner.
| CAMR019W |
| AGENT <aaaaaaaaaa> SIGN OFF UNSUCCESSFUL DURING RECOVERY OF SWITCH <bbbbbbbb> |
Explanation: During the recovery or relocation of a switch, if the Recover Agents field on the COR Recovery Policy menu is set to 'N', an attempt is made to sign off the agents from the original COR. In this instance agent <aaaaaaaaaa> could not be signed off.
Your response: None
| CAMR020I |
| AGENT <aaaaaaaaaa> SIGNED ON TO <bbbbbbbb> IN <ssss>. AGENT RECOVERY COMPLETE |
Explanation: During the recovery or relocate of a switch, if the Recover Agents field on the COR Recovery Policy menu is set to 'Y', an attempt is made to sign on those agents that were previously signed on. The agent shown has been signed on to switch <bbbbbbbb> in COR <ssss>.
Your response: None
| CAMR021I |
| AGENT <aaaaaaaaaa> SIGNED OFF FROM <bbbbbbbb> IN <ssss>. AGENT RECOVERY COMPLETE |
Explanation: During the recovery or relocate of a switch, if the Recover Agents field on the COR Recovery Policy menu is set to 'N', an attempt is made to sign off the agents from the original COR. The agent shown has been signed off switch <bbbbbbbb> in COR <ssss>.
Your response: None
| CAMR022I |
| SWITCH RELOCATION BEGINNING IN <aaaa> |
Explanation: A command has been issued to relocate a switch in COR <aaaa>.
Your response: None
| CAMR023I |
| SWITCH RELOCATION COMPLETED SUCCESSFULLY IN <aaaa> |
Explanation: A command has been issued to relocate a switch in COR <aaaa>, and has completed successfully.
Your response: None.
| CAMR024E |
| RETURN CODE <aaaa> RECEIVED FROM ENQ. RECOVERY MANAGER HAS ENDED |
Explanation: An EXEC CICS ENQ has been issued as part of the recovery process and has received the listed return code. Recovery manager can no longer function, so has ended.
Your response: Look up the return code in the appropriate CICS manual as a response to an EXEC CICS ENQ and take the recommended actions. If the problem persists, contact the IBM Support Centre (ISC) for assistance.
| CAMR025I |
| RECOVERY MANAGER INVOKED BY <aaaaaaaa> DUE TO FAILURE OF <bbbbbbbbbb> IN <cccc> |
Explanation: The Recovery Manager has been started by program <aaaaaaaa> due to the listed failure on COR <cccc>
Your response: Monitor the CICS message log to ensure that recovery is successful.
| CAMR026E |
| RETURN CODE <aaaa> FEEDBACK CODE <bbbb> RECEIVED FROM <cccccccc> |
Explanation: Recovery Manager received return code <aaaa> feedback code <bbbb> from called module <cccccccc>. The Recovery Manager transaction ends.
Your response: Contact IBM Support. If possible, provide a system dump of the CICS region affected.
| CAMR027I |
| ATTEMPT TO RECOVER SWITCH <aaaaaaaaaa> HAS ENDED DUE TO ERRORS. |
Explanation: This message should be preceeded by message CAMR026E and indicates the switch for which recovery was being attempted.
Your response: None
| CAMR028I |
| RECOVERY TURNED OFF FOR <aaaa>. NO ACTION TAKEN |
Explanation: For COR <aaaa> the recovery type has been set to 'no recovery' on the recovery policy menu for that COR, therefore no action has been taken.
Your response: Examine the CICS message log to determine the error that has occurred which would have resulted in action being taken by the recovery manager if the recovery type had been different.
| CAMR029I |
| SWITCH <aaaaaaaa> WAS SHUTDOWN MANUALLY. NO ACTION TAKEN |
Explanation: There are no recovery actions to take for the listed switch as it was shutdown manually
Your response: None
| CAMR030I |
| SUBSYSTEM WAS SHUTDOWN MANUALLY. NO ACTION TAKEN |
Explanation: There are no recovery actions to take for the CallPath subsystem as it was shutdown manually.
Your response: None
| CAMR031I |
| SWITCH <aaaaaaaa> WAS RECOVERED BY CALLPATH/CICS |
Explanation: The Recovery Manager has completed recovery of the listed switch.
Your response: None
| CAMR900E. |
| ATTEMPTS TO RECOVER CALLCOORDINATOR HAVE FAILED IN <ssss> |
Explanation: Recovery Manager has been unsuccessful in attempts to recover CallCoordinator in COR sysid <ssss>.
Your response: None
| CAMR901A |
| ENTER THE SYSID OF A RECOVERY TARGET OR ENTER CANCEL TO END RECOVERY |
Explanation: Recovery Manager is requesting input of a COR sysid as a target in which to recover CallCoordinator.
Your response: Enter the sysid of a target COR.
| CAMR902E |
| CALLPATH HAS FAILED IN <ssss>. SWITCHES CAN BE RELOCATED |
Explanation: CallPath has failed in sysid <ssss>. The Switches in the failing system can be relocated.
Your response: None
| CAMR903A |
| ENTER THE SYSID OF A RELOCATION TARGET OR ENTER CANCEL TO END RECOVERY |
Explanation: Input of a COR sysid as a target for Switch relocation is requested.
Your response: Enter the sysid of a target COR.
| CAMR904E |
| CICS REGION <ssss> HAS FAILED. RECOVERY CAN BE ATTEMPTED TO AN ALTERNATE COR |
Explanation: A CallCoordinator CICS region (COR) has failed. Recovery can be attempted in an alternate COR.
Your response: None
| CAMR905E |
| SWITCH <nnnnnnnn> IN <ssss> HAS FAILED TO ACTIVATE |
Explanation: A Switch <nnnnnnnn> in sysid <ssss> has failed to activate.
Your response: None
| CAMR906E |
| CALLCOORDINATOR HAS FAILED IN <ssss>. MANUAL RECOVERY IS SPECIFIED. |
Explanation: CallCoordinator has failed in sysid <ssss>. Manual recovery has been specified.
Your response: None
| CAMR907E |
| RETURN CODE <cccc> FROM WRITE OPERATOR COMMAND. RECOVERY ENDED IN <ssss> |
Explanation: A CICS error occurred when a Write Operator command was issued.
Your response: Consult your CICS documentation for the meaning of Return Code. If you determine that the problem is with the product, please contact your IBM Support Representative
| CAMR908E |
| RECOVERY HAS BEEN CANCELLED BY CONSOLE OPERATOR |
Explanation: A recovery attempt has been cancelled by the console operator in response to a WTOR message.
Your response: None.
| CAMR909A |
| ENTER GO TO RETRY OR CANCEL TO END RECOVERY |
Explanation: The Recovery Manager has not been able to contact the alternate COR.
Your response: Reply GO to retry or CANCEL to end the recovery attempt.
| CAMR910I |
| RESPONSE TO <aaaaaaaa> IS <bbbbbbbb> |
Explanation: The response to the previously issued WTOR <aaaaaaaa> is <bbbbbbbb>.
Your response: None
| CAMR911A |
| SYSID ENTERED IS NOT VALID. RE_ENTER OR ENTER CANCEL TO END RECOVERY |
Explanation: The SYSID entered from a previous WTOR has been checked and found invalid for recovery purposes.
Your response: Enter a valid SYSID for recovery or enter CANCEL to end the recovery attempt.
| CAMS002E |
| CANNOT RETRIEVE STARTED DATA |
Explanation: Executing the CICS RETRIEVE command caused a problem.
Your response:
| CAMS004E |
| SCREEN PRESENTATION CANNOT LINK TO PROGRAM <aaaaaaaa> RC <bbbb> |
Explanation: The System Settings table contains a program name that is not valid on the Exit Name field for Screen Presentation. If a program name is correct, there is a problem with the installation of the system tables.
Your response: Verify that the Exit Name field for Screen Presentation in the System Settings table contains a valid program name. If the program name is valid, contact your system programmer to check the installation of the system tables.
| CAMS005E |
| SPM PURGE DELAY TIME EXCEEDED, TO TERM <aaaaaaaa> UOW <bb> |
Explanation: The Screen Presentation Manager (SPM) threw away a screen before the system displayed the screen, because the display was delayed more than the user-defined default screen delay time. The screen delay in the System Settings table might be set too low.
This error can occur if an agent locks up a terminal by failing to press ENTER.
Your response:
| CAMS006E |
| COMMAREA ACI IS NOT NUMERIC OR IS NEGATIVE |
Explanation: An edit error occurred in the communication area between the Call Tracking Manager (CTM), and the Screen Presentation Manager (SPM). The CTM sent to the SPM an Application Connect Identifier (ACI) that was either negative or showed alphabetic characters.
Your response:
| CAMS007E |
| COMMAREA UNKNOWN ACTION-CODE <aa> |
Explanation: An edit error occurred in the communications area between the CTM and the SPM.
Your response:
| CAMS008E |
| COMMAREA MUST HAVE A TO OR FROM TERMINAL |
Explanation: An edit error occurred in the communications area between the Call Tracking Manager (CTM) and the Screen Presentation Manager (SPM). A terminal in the communications area between the CTM and the SPM must be identified as a to or from terminal.
Your response:
| CAMS009E |
| COMMAREA FROM TERMINAL MUST BE PRES. FOR THIS ACTION-CODE |
Explanation: An edit error occurred in the communications area between the CTM and the SPM.. The from designation is missing and a from terminal is necessary for the action code received from the CTM.
Your response:
| CAMS010E |
| COMMAREA TO TERMINAL MUST BE PRES. FOR THIS ACTION-CODE |
Explanation: An edit error occurred in the communications area between the Call Tracking Manager (CTM) and the Screen Presentation Manager (SPM). The to designation is missing and a to terminal is necessary for the action code received from the CTM.
Your response:
| CAMS011E |
| PROGRAM WAS NOT STARTED BY CALL TRACKING |
Explanation: An edit error occurred in the communications area between the CTM and the SPM. The to program identification code passed by the CTM to the SPM does not match the program identification code for the SPM, which is CAMS500C.
Your response:
| CAMS012E |
| ERROR IN STARTING TRANSACTION: <aaaaaaaa> |
Explanation: The Screen Presentation Manager (SPM) could not perform a CICS START command successfully.
Your response: If the transaction is a user-supplied transaction, check the transaction IDs in the System Settings table and Agent Sign On/Off panel. If the transaction IDs are correct, contact your system programmer to verify the installation of the system.
| CAMS013E |
| START V510 FOR SCREEN TRANSFER WAS NOT SUCCESSFUL |
Explanation: The Screen Presentation Manager (SPM) could not perform a CICS START command successfully.
Your response: Ask your system programmer to determine the cause of the error.
| CAMS014E |
| START V510 FOR SCREEN SAVE WAS NOT SUCCESSFUL |
Explanation: The Screen Presentation Manager (SPM) could not perform a CICS START command successfully.
Your response: Ask your system programmer to determine the cause of the error.
| CAMS015E |
| START V530 FOR SCREEN RESTORE WAS NOT SUCCESSFUL |
Explanation: The Screen Presentation Manager (SPM) could not perform a CICS START command successfully.
Your response: Ask your system programmer to determine the cause of the error.
| CAMS017E |
| CANNOT START USER-MODE TRANSACTION |
Explanation: The SPM indicates unsuccessful CICS commands.
Your response:
| CAMS018I |
| NOT ABLE TO SEND XFER/SAVE MESSAGE |
Explanation: The Screen Presentation Manager (SPM) could not perform a CICS SEND TEXT command successfully.
Your response: Ask your system programmer to determine the cause of the error.
| CAMS019E |
| RECEIVE BUFFER V510 / ACTION CODE = XFER / SAVE: |
Explanation: The Screen Presentation Manager (SPM) could not perform a CICS RECEIVE command successfully.
Your response: Ask your system programmer to determine the cause of the error.
| CAMS020E |
| CANNOT WRITE SCREEN BUFFER TO TS QUEUE |
Explanation: The Screen Presentation Manager (SPM) could not perform a CICS WRITE TS command successfully.
Your response: Ask your system programmer to determine the cause of the error.
| CAMS021E |
| CANNOT START CAMS520C/V520 ACTION-CODE = XFER |
Explanation: The Screen Presentation Manager (SPM) could not perform a CICS SEND command successfully.
Your response: Ask your system programmer to determine the cause of the error.
| CAMS024E |
| CANNOT SEND SAVED SCREEN |
Explanation: The 'saved screen image' length was zero and so no screen image could be restored on the transferred-to agent's terminal.
Your response: If this message occurs repeatedly, or is displayed consistently in particular circumstances, call the IBM Support Center.
| CAMS026E |
| CANNOT READ SCREEN BUFFER FROM TS QUEUE |
Explanation: The Screen Presentation Manager (SPM) cannot find the screen buffer in the temporary storage queue (TSQ). The system tried to read the TSQ before the write was complete.
Your response: If this message occurs repeatedly, or forms a pattern, call the IBM Software Support Center (ISC).
| CAMS027E |
| CANNOT DELETE SCREEN BUFFER FROM TS QUEUE |
Explanation: The Screen Presentation Manager (SPM) cannot find the screen buffer in the temporary storage queue (TSQ). The system probably tried to delete data from the TSQ before the write was complete.
Your response: If this message occurs repeatedly, or forms a pattern, call the IBM Software Support Center (ISC).
| CAMS028E |
| INQUIRE FOR CUSTOMER APPLICATION WAS NOT SUCCESSFUL |
Explanation: The Screen Presentation Manager (SPM) could not perform a CICS INQUIRE command successfully.
Your response: Ask your system programmer to determine the cause of the error.
| CAMS029E |
| ERROR ACCESSING CALL DATA TABLE IN ROUTINE = <aaaaaaaa> |
Explanation: CallCoordinator could not find a call data record for an agent, possibly due to a disconnect.
Your response: If this message occurs repeatedly, or forms a pattern, call the IBM Software Support Center (ISC).
| CAMS030E |
| USER APPLICATION COMMAREA EXCEEDS CALLPATH MAXIMUM OF 32763 |
Explanation: The user application Commarea exceeds maximum size for Commarea.
Your response: Contact your system programmer to reduce the application Commarea.
| CAMS031E |
| ERROR DURING CICS COMMAND, GETMAIN CANNOT OBTAIN NEEDED STORAGE |
Explanation: The Screen Presentation Manager (SPM) could not perform a CICS GETMAIN command successfully.
Your response: Ask your system programmer to determine the cause of the error.
| CAMS032E |
| ERROR DURING CICS COMMAND, READQ CANNOT READ DFHCOMMAREA FROM TS QUEUE |
Explanation: The Screen Presentation Manager (SPM) could not perform a CICS READQ command successfully.
Your response: Ask your system programmer to determine the cause of the error.
| CAMS033E |
| ERROR ACCESSING <aaaaaaaaaaaaaaaaaaaa> IN ROUTINE = <bbbbbbbb> |
Explanation: A non-zero return code has been obtained after trying to access one of three tables: Agents, Connection-ID, or Party Data. This occurred in ROUTINE = ... For the Agents table, the routine which can cause this msg to appear is EZPSEXTC. For the Conn ID table, it can be either CAMTIKTN or CAMTIKRN. For the Party Data table, it can be CAMTIKGN.
Your response: This error can be caused by many actions; the most common action would be not to have an agent signed on. If this message appears in the CICS system log, make sure there are agents signed on and verify that the actions performed prior to getting this error are valid. If this message continues to appear, call your IBM Software Support Center.
| CAMS034E |
| CANNOT SEND MSG TO TERMINAL |
Explanation: The Screen Presentation Manager (SPM) could not perform a CICS SEND command successfully.
Your response: Ask your system programmer to determine the cause of the error.
| CAMS035E |
| ERROR IN RETRIEVING TS-QUEUE LIST DATA, RETURN CODE = <aaaa> |
Explanation: The Screen Presentation Manager (SPM) could not perform a CICS RETRIEVE command successfully.
Your response: Ask your system programmer to determine the cause of the error.
| CAMS900I |
| Transfer from term <aaaaaaaa> to term <bbbbbbbb> successful |
Explanation: The transfer was successful.
Your response: None.
| CAMS901I |
| Transfer from terminal <aaaaaaaa> was saved |
Explanation: The transfer was saved.
Your response: None.
| CAMS902I |
| CallCoordinator is out of service. Press Enter. |
Explanation: CallCoordinator is out of service. The link to the host is down.
Your response: Press Enter to clear the message from the panel. Try again later.
| CAMS903I |
| CallCoordinator is available now. Press Enter. |
Explanation: CallCoordinator is back in service. The system is restarting.
Your response: Press Enter to clear the message from the panel.
| CAMS904I |
| CallCoordinator is available now. Press Enter. |
Explanation: CallCoordinator is in service, and the host link is up and running.
Your response: Press Enter to clear the message from the panel.
| CAMS905I |
| CallCoordinator is out of service. Press Enter. |
Explanation: CallCoordinator is out of service; the system is shut down.
Your response: Press Enter to clear the message from the panel.
| CAMS906W |
| Request not supported by switch |
Explanation: The function requested is not one that is supported by this switch.
Your response: Request another function, or review your request. If correct, contact the system administrator.
| CAMS907W |
| Communication with switch is unavailable |
Explanation: The switch is down.
Your response: Notify the system administrator.
| CAMS908W |
| Request handler is busy, try later |
Explanation: One of the telephony subsystems is busy.
Your response: Try the request later.
| CAMS909I |
| Switch service has been restored |
Explanation: Switch service had been down but is now restored.
Your response: None. This is for information only.
| CAMS910E |
| Transaction ID <aaaaaaaa> is not valid |
Explanation: The Initial Transaction ID defined on the signon panel is not defined for this CICS region.
Your response: Verify that you typed in the correct identifier. If the number is correct, contact your system administrator.
| CAMS911I |
| CallCoordinator is unavailable. Switch <aaaaaaaa> is down |
Explanation: Switch link is down.
Your response: Notify your system administrator.
| CAMS912I |
| CallPath/CICS is trying to restore link to Switch <aaaaaaaa> |
Explanation: Switch link is still down.
Your response: None
| CAMS913I |
| CallCoordinator now available. Switch <aaaaaaaa> restored |
Explanation: Switch link is back up.
Your response: None
| CAMS920W |
| Incorrect directory number |
Explanation: The directory number you entered does not exist on the switch.
Your response: Verify the number and try again, or try another number.
| CAMS921W |
| Number is busy/unavailable |
Explanation: The number is busy or is not receiving calls.
Your response: Try another number, or try this call later.
| CAMS922W |
| Call to this number is not allowed |
Explanation: This number is not receiving calls.
Your response: Try this call later, or try another number.
| CAMS923W |
| Telephony request rejected |
Explanation: The function you have requested is not available on the switch.
Your response: Notify your system administrator.
| CAMT003W |
| RESERVED PILOT NUMBER NOT RELEASED |
Explanation: CallCoordinator cannot find the reserved pilot number (used in load balancing) that released the call being processed by CallCoordinator. This warning message appears with load balancing. An error might exist in the CallCoordinator software.
Your response: Monitor the MIS Log, looking for frequent occurrences of the problem or for a pattern. If the problem persists, call the IBM Software Support Center (ISC).
| CAMT011W |
| SCREEN PRESENTATION RETURN WITH ERROR |
Explanation: CallCoordinator received a non-zero CICS response code from the Screen Presentation Manager (SPM) software. The wrong panel (or no panel) can appear on the terminal, as a symptom.
This might be caused by either CICS or the CallCoordinator software.
Your response: Monitor the CICS system log, looking for frequent occurrences of the problem or for a pattern. Call the IBM Software Support Center (ISC).
| CAMT013I |
| CMCT ENTRY DELETED BY CALL TRACKING |
Explanation: CallCoordinator cleared an entry out of the Call Management Control table (CMCT). The system administrator must decide how frequently CallCoordinator will clear the CMCT.
Your response: If the clearing occurs too frequently, monitor the system using the MIS Log and the CallCoordinator Trace Facility, as discussed in CallPath CallCoordinator/CICS Problem Determination. Take the recovery actions suggested by the error messages.
| CAMT014W |
| SWITCH RESTART OPTION OF INSTALLATION PARAMETER IS MISSING |
Explanation: The CallCoordinator global variables must show a CallCoordinator restart option that is set to YES or NO. This tells CallCoordinator what to do after receiving a message indicating that a switch restarted. If set to NO, CallCoordinator keeps on functioning as though nothing had happened. if set to YES, CallCoordinator logs the restart notification and all CMCT entries associated with the switch ID of the restarted switch. The CallPath administrator forgot to configure the restart option parameter.
Your response: Access the parameters configuration panel and select YES or NO as the restart option parameter.
| CAMT017I |
| SWITCH RESTART MESSAGE RECEIVED |
Explanation: CallCoordinator received a message indicating that the switch had started again.
Your response: None. This message is for information only.
| CAMT020E |
| CALL TRACKING MANAGER LOGIC ERROR |
Explanation: The application-connect identification code for the CTM is not valid. This warning message can occur with any type of call tracking message. An error might exist in the CallCoordinator software.
Your response: Monitor the MIS Log and perform the recovery actions indicated by any error messages found. Call the IBM Software Support Center (ISC).
| CAMT030E |
| CTM EVENT MESSAGE QUEUE IS EMPTY |
Explanation: The Call Tracking Manager (CTM) event message queue is empty. Error could be in the CallPath Services receiver.
Your response: Contact CICS system programmer.
| CAMT040E |
| CANNOT READ DATA FROM <aaaaaaaa> |
Explanation: The Call Tracking Manager (CTM) tried, and failed, to read the CallCoordinator configuration data from the VSAM file referenced by <ddnam>.
Your response: Contact CICS system programmer.
| CAMT050I |
| UNAUTHORIZED ACCESS, CONTACT SYSTEM SUPPORT |
Explanation: Someone tried to start the V200 module (call tracking) without going through the usual startup procedure.
Your response: None. This message is for information only.
| CAMT051I |
| BEGIN CALL TRACKING MANAGER (CTM) |
Explanation: CallCoordinator has begun a routine startup of CTM.
Your response: None. This message is for information only.
| CAMT052E |
| CTM START FAILED ERROR FOUND IN TABLE ADDRESSABILITY |
Explanation: The CTM detected table addressability error. An error exists in the host software (CICS or CallCoordinator or some other application).
Your response: Shut down and restart CallCoordinator. If the problem is not solved, call the IBM Software Support Center (ISC) to report the problem and the events leading to the error.
| CAMT053I |
| CALL TRACKING MANAGER IS ALREADY ACTIVE |
Explanation: Someone tried to start the Call Tracking Manager (CTM) without going through the standard startup procedure, and the CTM was already running.
Your response: None. This message is for information only.
| CAMT054I |
| END CALL TRACKING MANAGER (CTM) |
Explanation: CallCoordinator has ended CTM. This message appears during a routine shutdown.
Your response: None. This message is for information only.
| CAMT055I |
| CALL TRACKING SHUTDOWN REQUEST ACKNOWLEDGED |
Explanation: CallCoordinator has received the request for shutdown.
Your response: None. This message is for information only.
| CAMT056I |
| SHUTDOWN STATISTICS: MAXIMUM = <aaaa>, HIGH WATER = <bbbb> <ccccccccccccccc> |
Explanation: The usage for table <ccccccccccccccc> is such that the maximum entries configured is <aaaa> and the maximum entries used during this run CallCoordinator was <bbbb>. You can use this information to judge if your table size needs adjusting.
Your response: None. This message is for information only.
| CAMT057E |
| CALL MANAGEMENT CONTROL TABLE (CMCT) FULL |
Explanation: The Call Management Control table (CMCT) is full, and the CallCoordinator system cannot process more call event messages.
Your response: Increase the size of the CMCT, using the CallCoordinator Table Sizes panel. Then reload the tables, using the CallCoordinator Problem Determination panel.
| CAMT058I |
| CMCT TABLE FULL, HOUSEKEEPING STARTED |
Explanation: The CMCT is full, and the CallCoordinator system cannot process any more call event messages.
Either the CMCT size is not adequate or the CMCT housekeeping (cleanup) program was not configured correctly to clean out old CMCT entries.
Your response: Monitor the MIS Log. According to the indicated cause, do the following:
| CAMT060E |
| CANNOT READ DATA FROM THE SYSTEM SETTINGS FILE |
Explanation: The Call Tracking Manager (CTM) cannot read System Settings data from the System Settings file.
Your response: Contact CICS system programmer.
| CAMT061I |
| SWITCH HAS BEEN SUCCESSFULLY RESTARTED |
Explanation: The switch has successfully restarted.
Your response: None. This message is for information only.
| CAMT062I |
| HOST LINK IS DOWN |
Explanation: The link from the switch through the gateway to the host computer is not running. After a link shutdown, this message is written to the MIS log.
Your response: None. This message is for information only.
| CAMT063I |
| HOST LINK IS UP AND RUNNING |
Explanation: The host computer received a link alert indicating that the link from the switch through the gateway to the host computer is active.
Your response: None. This message is for information only.
| CAMT064I |
| CMCT CLEAN-UP STARTED. CMCT ENTRIES IN USE = <cccc> |
Explanation:
Your response:
| CAMT065I |
| CMCT CLEAN-UP COMPLETE. CMCT ENTRIES IN USE = <cccc> |
Explanation:
Your response:
| CAMT070E |
| CTM WAKES UP BY ITSELF, CALLPATH SERVICES RECEIVER IS OUT OF SERVICE |
Explanation: The Call Tracking Manager (CTM) (V200) wakes up by itself and is not awakened by the CallPath Services program.
Your response: Contact CICS system programmer.
| CAMT073E |
| CTM EVENT MESSAGE QUEUE CORRUPTED |
Explanation: The event message queue for Call Tracking Manager (CTM) contains incorrect data.
Your response: Contact CICS system programmer.
| CAMT075E |
| CALLPATH SERVICES RECEIVER ENCOUNTERS CICS PROBLEM : RC = <aaaa> |
Explanation: The CallPath Services receiver program (V220) has a CICS problem and no event is processed by the Call Tracking Manager (CTM).
Your response: Contact CICS system programmer.
| CAMT078E |
| CALLPATH SERVICES RECEIVER ENCOUNTERS CALLPATH SERVICES PROBLEM |
Explanation: The CallPath Services receiver program (V220) has a CallPath Services problem and no event is processed by the Call Tracking Manager (CTM)
Your response: Contact CICS system programmer.
| CAMT080E |
| INCORRECT SPM ACTION, FROM_AGENT STATUS = <a>, TO_AGENT STATUS = <b> |
Explanation: Call Tracking encountered an invalid combination of to- and from-agent status and was unable to invoke screen presentation as a result.
Your response: If this message occurs repeatedly, or is displayed consistently in particular circumstances, call the IBM Support Center.
| CAMT101E |
| MISSING DATA IN CALLPATH MESSAGE |
Explanation: A message was received from the CallPath/CICS for OS/390 subsystem that did not contain enough connection IDs for CallCoordinator to be able to process. This situation may occur if an undetected restart of a switch or gateway occurred, or as the result of an error in CallPath/CICS for OS/390.
Your response: Contact the system administrator for CallPath/CICS for OS/390 for problem determination.
| CAMT102W |
| CONFLICTING CALL DELETED |
Explanation: A message was received from the switch that implied that a connection was to a call that is not the same as a call already in the CMCT. The old call is deleted and this message written to the MIS log. This situation may occur if an undetected restart of a switch or gateway occurred, or as the result of an error in CallPath/CICS for OS/390.
Your response: Contact the system administrator for CallPath/CICS for OS/390 for problem determination.
| CAMT103E |
| EXISTING CALL NOT FOUND FOR CALL-TRANSFERRED MESSAGE |
Explanation: A Call_Transferred message contains data for the connections of the transferring party to two existing calls. One or more of the calls could not be found in the CMCT. This may be the result of lost messages from a link restart, or a CMCT full condition.
Your response: Examine the MIS log to see if it includes a link restart or CMCT-full message, If not, contact the system administrator for CallPath/CICS for OS/390 for problem determination.
| CAMT104E |
| EXISTING CALL NOT FOUND FOR CALL-ALTERNATED MESSAGE |
Explanation: A Call_Alternated message contains data for the connections of a party who is alternating between two existing calls. One or more of the calls could not be found in the CMCT. This may be the result of lost messages from a link restart, or a CMCT full condition.
Your response: Examine the MIS log to see if it includes a link restart or CMCT-full message, If not, contact the system administrator for CallPath/CICS for OS/390 for problem determination.
| CAMT105E |
| EXISTING CALL NOT FOUND FOR CALL-CONFERENCED MESSAGE |
Explanation: A Call_Conferenced message contains data for the connections of the party who joined two existing calls. One or more of the calls could not be found in the CMCT. This may be the result of lost messages from a link restart, or a CMCT full condition.
Your response: Examine the MIS log to see if it includes a link restart or CMCT-full message, If not, contact the system administrator for CallPath/CICS for OS/390 for problem determination.
| CAMT106E |
| CALLING PARTY ROLE CANNOT BE IDENTIFIED |
Explanation: A message contains data for the connections of one or more parties, but the calling-party role cannot be determined. This may be the result of lost messages from a link restart, or a CMCT full condition.
Your response: Examine the MIS log to see if it includes a link restart or CMCT-full message, If not, contact the system administrator for CallPath/CICS for OS/390 for problem determination.
| CAMT107E |
| CALLED PARTY ROLE CANNOT BE IDENTIFIED |
Explanation: A message contains data for the connections of one or more parties, but the called-party role cannot be determined. Call Tracking is unable to determine which agent controls, or should receive, the screen transaction. This may be the result of lost messages from a link restart, or a CMCT full condition.
Your response: Examine the MIS log to see if it includes a link restart or CMCT-full message. If not, contact the system administrator for CallPath/CICS for OS/390 for problem determination.
| CAMT108E |
| INCORRECT CALLPATH MESSAGE: CALL TYPE is STL_DATA |
Explanation: The Call Tracking Manager (CTM) receives an incorrect CallPath Services event call type.
Your response: Contact the system administrator for CallPath/CICS for OS/390 for problem determination.
| CAMT109E |
| CMCT TABLE ACCESS FAILED: FUNC = <aaaaaaaaaa> RC = <bbbb> |
Explanation: The Call Tracking Manager (CTM) detects error in the CMCT table access.
Your response: Call the IBM Software Support Center (ISC) to report the problem. Give time and location data to help the IBM Software Support Center (ISC) to find the problem in the CICS system log.
| CAMT110E |
| DISCONNECTING PARTY ROLE CANNOT BE IDENTIFIED |
Explanation: The Call Tracking Manager (CTM) cannot identify the party role for this Disconnect message.
Your response: Examine the MIS log to see if it includes a link restart or CMCT-full message. If not, contact the system administrator for CallPath/CICS for OS/390 for problem determination.
| CAMT111E |
| SWITCH ID <aaaaaaaa> CANNOT BE IDENTIFIED |
Explanation: The event message contains a switch that is not defined on the Switches table.
Your response: Define the switch on the Switches table.
| CAMT112E |
| EXISTING CALL NOT FOUND FOR DATA-COLLECTED MESSAGE |
Explanation: A Data_Collected event message was received from the CallPath subsystem but the connection_id contained in the message does not refer to any active telephone call known to CallCoordinator
Your response: This may be a timing issue in that the caller hung up before the data_collected event arrived. If this message occurs repeatedly, or is displayed consistently in particular circumstances, call the IBM Support Center.
| CAMT113E |
| CONNECTION ID NOT FOUND FOR DATA-COLLECTED MESSAGE |
Explanation: A Data_Collected event message was received from the CallPath subsystem but no connection_id was contained in the message.
Your response: This may signify a CallPath subsystem error. If this message occurs repeatedly, or is displayed consistently in particular circumstances, call the IBM Support Center.
| CAMT114E |
| DUPLICATE CONNECTION ID IN CALL HELD EVENT MSG, EVENT MSG IGNORED |
Explanation: A Call_Held event message was received from the CallPath subsystem and both the held_party and holding_party connection_ids were the same. The event message is treated as being invalid and is ignored.
Your response: This may signify a CallPath subsystem error. If this message occurs repeatedly, or is displayed consistently in particular circumstances, call the IBM Support Center.
| CAMT201E |
| MIS MSG QUEUE CORRUPTED |
Explanation: The message queue for the MIS Log contains incorrect data.
Your response:
| CAMT202E |
| MIS MSG QUEUE WRITE POINTER IS OUT OF RANGE |
Explanation: The message queue write pointer for the MIS Log contains an incorrect numeric value.
Your response:
| CAMT203E |
| MIS MSG QUEUE IS FULL, A MESSAGE HAS BEEN LOST |
Explanation: The message queue for the MIS Log overflowed. The MIS message queue is too small.
Your response:
| CAMT204E |
| MIS MSG QUEUE READ POINTER IS OUT OF RANGE |
Explanation: The message queue read pointer for the MIS Log contains an incorrect numeric value.
Your response:
| CAMT205E |
| MIS MSG QUEUE ERROR, BAD RETURN CODE |
Explanation: The MIS Log Queue write program returns with bad return code.
Your response:
| CAMT302E |
| INCORRECT MESSAGE CLASS |
Explanation: CallCoordinator received a message that was not valid. A major CallCoordinator system problem exists.
Your response:
| CAMT303E |
| INCORRECT PSEUDOEVENT MESSAGE CODE |
Explanation: CallCoordinator received incorrect data as a call event message.
Your response:
| CAMT304E |
| CALLPATH/CICS MESSAGE CODE NOT SUPPORTED |
Explanation:
Your response:
| CAMT305E |
| INCORRECT CALLPATH MESSAGE CODE |
Explanation: CallCoordinator received a message type that is not known to CallCoordinator. One of the following events caused a major CallCoordinator system problem:
Your response:
| CAMT310E |
| CALLPATH SERVICES SIGNON FAILED FOR <aaaaaaaa> <b> <cccccccccc> DURING <dddddddd> RC=<eeee> |
Explanation: CallCoordinator attempted to sign a resource on to CallPath Services and failed.
Your response: Either CallPath Services is down or the switch is down. Correct the problem, and CallCoordinator will automatically sign affected resources back on to CallPath Services when they are signed on to CallCoordinator.
| CAMT311E |
| CALLPATH SERVICES SIGNOFF FAILED FOR <aaaaaaaa> <b> <cccccccccc> DURING <dddddddd> RC=<eeee> |
Explanation: CallCoordinator attempted to sign a resource off of CallPath Services and the attempt failed.
Your response: Either CallPath Services is down or the switch is down. Correct the problem. No further action needs to be taken to sign the agent off of CallCoordinator.
| CAMT312E |
| CALLPATH SERVICES SIGNON FAILED; SWITCH <aaaaaaaa> NOT DEFINED TO CALLCOORDINATOR |
Explanation: The switch associated with the resource being signed on does not have an entry in the Switches table.
Your response: This is a configuration error. Check the entries in the Switches table against the entries in the Agents table and Load Balancing tables. Correct the entry or entries in error.
| CAMT313E |
| CALLPATH SERVICES SIGNOFF FAILED; SWITCH <aaaaaaaa> NOT DEFINED TO CALLCOORDINATOR |
Explanation: The switch associated with the resource being signed off does not have an entry in the Switches table.
Your response: This is a configuration error. Check the entries in the Switches table against the entries in the Agents table and Load Balancing tables. Correct the entry or entries in error.
| CAMT314I |
| BEGIN CALLPATH SERVICES RECEIVER |
Explanation: A routine startup of CallPath Services Receiver has begun.
Your response: None. This message is for information only.
| CAMT315I |
| END CALLPATH SERVICES RECEIVER |
Explanation: A routine shutdown of CallPath Services Receiver has occurred.
Your response: None. This message is for information only.
| CAMT316E |
| ABNORMAL TERMINATION CALLPATH SERVICES RECEIVER -- EVENT MSG QUEUE NOT INITIALIZED |
Explanation: CallCoordinator has detected an error in its internally managed storage.
Your response: Restart CTM. If the problem recurs, call the IBM Software Support Center (ISC).
| CAMT317E |
| CALLPATH SERVICES CALL FAILED: <aaaaaaaa> RC=<bbbb> |
Explanation: CallCoordinator detected an error during a routine call to CallPath Services.
Your response: Restart CTM. If the problem recurs, call the IBM Software Support Center (ISC).
| CAMT318E |
| EMQ TOO SMALL: MESSAGE LOST <aaa> <bbbbbbbbbb> <ccccccccccccccccccccccccc |
Explanation: CallCoordinator detected an error trying to write to its internal queue.
Your response: Call the IBM Software Support Center (ISC).
| CAMT319E |
| WAIT TIME EXCEEDED: MESSAGE LOST <aaa> <bbbbbbbbbb> <cccccccccccccccccccccccccccccc> |
Explanation: A message was lost because the maximum wait time allowed by CTM delay and CTM attempts has been exceeded.
Your response: Adjust the wait time by entering larger values in the CTM delay and CTM attempts fields on the CallCoordinator System Settings panel.
| CAMT320E |
| EMQ CORRUPTED BEFORE WRITE: MSG LOST <aaa> <bbbbbbbbbb> <cccccccccccccccccccccccccccccc> |
Explanation: CallCoordinator detected an error trying to write to its internal queue.
Your response: Call the IBM Software Support Center (ISC).
| CAMT321E |
| EMQ CORRUPTED AFTER WRITE: MSG LOST <aaa> <bbbbbbbbbb> <cccccccccccccccccccccccccccccc> |
Explanation: CallCoordinator detected an error trying to write to its internal queue.
Your response: Call the IBM Software Support Center (ISC).
| CAMT323I |
| COMMUNICATION ESTABLISHED WITH SWITCH <aaaaaaaa> |
Explanation: CallCoordinator has successfully established communication with the switch.
Your response: None. This is for information only.
| CAMT324E |
| COMMUNICATION FAILED WITH SWITCH <aaaaaaaa> |
Explanation: CallCoordinator has attempted to establish communication with a switch and failed.
Your response: Determine why the switch is out of service and correct the problem.
| CAMT325E |
| ABNORMAL TERMINATION CALLPATH SERVICES RECEIVER |
Explanation: CallCoordinator has detected a critical error and is unable to continue processing.
Your response: Contact the IBM Software Support Center (ISC).
| CAMT326I |
| CALLPATH SERVICES RECEIVER INITIALIZATION COMPLETE, COMMUNICATION ESTABLISHED |
Explanation: The link between CallCoordinator and CallPath/CICS for OS/390 is complete. CallCoordinator is ready to begin receiving messages.
Your response: None. This is for information only.
| CAMT327W |
| CALLPATH SERVICES RECEIVER HAS INITIATED RESTART PROCEDURE |
Explanation: The CallPath Services Receiver task (V220) has initiated a restart after losing communications with the CallPath subsystem.
Your response: If this message occurs repeatedly you should examine your CICS and CallPath/CICS logs to establish why contact is being lost. This may be indicative of a network problem that needs correction.
| CAMT328I |
| CALLPATH SERVICES RECEIVER RESTART COMPLETED, COMMUNICATION RE-ESTABLISHED |
Explanation: Communication has been established again with CallPath Services.
Your response: None. This is for information only.
| CAMT329E |
| CATASTROPHIC ERROR IN CALLPATH SERVICES RECEIVER. V220 IS TERMINATING |
Explanation: V220 issued a CallPath STLRCV and this API call failed with STL_RECEIVE_OUTSTANDING indicating a catastrophic error with the CallPath subsystem.
Your response: This may signify a CallPath subsystem error. If this message occurs repeatedly, or is displayed consistently in particular circumstances, call the IBM Support Centre.
| CAMT330I |
| BEGIN MONITOR PROCESS FOR SWITCH <aaaaaaaa> |
Explanation: The Monitor Process has begun.
Your response: None. This message is for information only.
| CAMT331I |
| END MONITOR PROCESS FOR SWITCH <aaaaaaaa> |
Explanation: The Monitor Process has ended.
Your response: None. This message is for information only.
| CAMT332I |
| BEGIN MONITOR PROCESS FOR ALL SWITCHES |
Explanation: The Monitor Process for all switches has begun.
Your response: None. This message is for information only.
| CAMT333I |
| END MONITOR PROCESS FOR ALL SWITCHES |
Explanation: The Monitor Process for all switches has ended.
Your response: None. This message is for information only.
| CAMT334E |
| RETURN CODE <aa> FROM EZPVBITC, SWITCH ID <aaaaaaaa> |
Explanation:
Your response:
| CAMT335E |
| UNABLE TO PROCESS SWITCH/LINK STATUS MESSAGE; SWITCH <aaaaaaaa> NOT DEFINED TO CALLCOORDINATOR |
Explanation: The switch is not defined to CallCoordinator, so the message cannot be processed.
Your response: Check switch names on CallCoordinator switch table and CallPath/CICS for OS/390 switch table. Correct any mismatches related to switch <aaaaaaaa>.
| CAMT336E |
| FEEDBACK CODE <cc> FROM <mmmmmmmm> FOR SWITCH <nnnnnnnn> |
Explanation: The Switch Activation/Deactivation modules have returned a feedback code of >cc< for switch <nnnnnnnn>.
Your response: Use the system administration switch operations panel to check the switch status.
| CAMT340E |
| Attempt to join call with itself |
Explanation:
Your response:
| CAMT341I |
| SWITCH <nnnnnnnn> IS NOW ACTIVE |
Explanation: Request to activate switch <nnnnnnnn> has been successfully completed.
Your response: None.
| CAMT342E |
| ERROR DURING CALLPATH API >tttttttt< FOR SWITCH <nnnnnnnn> |
Explanation: A CallPath STLSWCH API call of type >tttttttt< has failed for switch <nnnnnnnn>.
Your response: Use the system administration switch operations panel to check the switch status.
| CAMT343E |
| ERROR ISSUING MONITORS FOR SWITCH <nnnnnnnn> |
Explanation: The switch activation module experienced an error starting the monitor process.
Your response: Contact your systems programming representative
| CAMT344E |
| SWITCH <nnnnnnnn> FAILED TO ACTIVATE |
Explanation: Switch <nnnnnnnn> failed to activate in reasonable time.
Your response: Check the systems administration switch operations panel for the latest switch status. If still inactive attempt activation again.
| CAMT345I |
| SWITCH <nnnnnnnn> IS NOW INACTIVE |
Explanation: Switch <nnnnnnnn> is now inactive.
Your response: None.
| CAMX010E |
| Host Initiated Transfer API error return code <aaaa> |
Explanation: The Host Initiated Transfer API (CAMI775C) failed. The reason for failure is:
Your response: Once the error condition is corrected, try again.
| CAMX011E |
| Transfer Load Balancing API error return code <aaaa> |
Explanation: The Transfer Load Balancing API (CAMI705C) failed. The reason for failure is:
Your response: Once the error condition is corrected, try again.
| CAMX012E |
| Set Control Number API error return code <aaaa> |
Explanation: The Set Control Number API (CAMI730C) failed. The reason for failure is:
Your response: Once the error condition is corrected, try again.
| CAMX013E |
| Write MIS Record API error return code <aaaa> |
Explanation: The Write MIS Record API (CAMI700C) failed. The reason for failure is:
Your response: Once the error condition is corrected, try again.
| CAMX014E |
| Inquire Call Data API error return code <aaaa> |
Explanation: The Inquire Call Data API (CAMI726C) failed. The reason for failure is:
Your response: Once the error condition is corrected, try again.
| CAMX015E |
| Inquire Party Data API error return code <aaaa> |
Explanation: The Inquire Party Data API (CAMI727C) failed. The reason for failure is:
Your response: Once the error condition is corrected, try again.
| CAMX016E |
| Inquire Agents API error return <aaaa> reason <bbbb> |
Explanation: The Inquire Agents API (CAMI720C) failed. The reason for failure is:
The following reason codes further define the return codes that contain more than one error condition:
Your response: Once the error condition is corrected, try again.
| CAMX017E |
| Casual User Restore API error return code <aaaa> |
Explanation: The Casual User Restore API (CAMI760C) failed. The reason for failure is:
Your response: Once the error condition is corrected, try again.
| CAMX020E |
| Y in Start with Data field requires Init trans ID |
Explanation: The Start with Data field works with the Init trans ID field. If you type Y in the Start with Data field, you must make a valid entry in the Init trans ID field.
Your response: Type a valid entry in the Init trans ID field.
| CAMX021E |
| Agent mode must be Y, P, or I |
Explanation: You typed a value other than Y, P, or I in the Agent mode field.
Your response: Type a valid entry.
| CAMX032E |
| Type Y in User Control field |
Explanation: You typed an entry in the User Trans ID field. This requires the User control field to be set to Y.
Your response: Type Y in the User control field, or blank out the entry in the User Trans ID field.
| CAMX033E |
| Type Y or leave blank |
Explanation: You typed a value other than Y or Blank in the highlighted field.
Your response: Type Y or leave Blank.
| CAMX034E |
| User Trans ID is not defined |
Explanation: You typed Y in the User control field. This requires a valid entry in the User Trans ID field. If you do not type an entry in that field, the system administrator must define the User Trans ID on the CallCoordinator System Settings panel.
Your response: Type a valid entry in the User Trans ID field, or ask your system administrator to define that field on the CallCoordinator System Settings panel.
| CAMX038E |
| Cannot sign on; CallCoordinator is not running |
Explanation: An agent cannot sign on to CallCoordinator if it is not running.
Your response: Notify the system administrator that CallCoordinator is not running.
| CAMX040E |
| This terminal is not signed on |
Explanation: This request cannot be processed, because this terminal is not currently signed on.
Your response: Sign on terminal before trying this selection.
| CAMX041E |
| Time From is greater than Time To |
Explanation: Time From is after Time To.
Your response: Type a valid Time From/To entry.
| CAMX046E |
| Type Day 0 - 6 or > |
Explanation: You typed an incorrect code for a day. Valid codes are:
Your response: Type a valid code for the designated day of the week you want to use.
| CAMX048E |
| Valid range is 1 - 9 |
Explanation: You typed a value outside the valid range.
Your response: Type a valid value.
| CAMX049E |
| Valid range is 1 - 99 |
Explanation: You typed a value outside the valid range.
Your response: Type a valid value.
| CAMX052E |
| Type 0, 1, 2, or 3 |
Explanation: You typed an incorrect value.
Your response: Type a valid value:
| CAMX056E |
| Cannot change and delete together |
Explanation: You have changed a field, but typed in action code 3 to delete the entry.
Your response: If you meant to delete the entry, use F5 to refresh the panel, then type 3 in the Act field beside the entry.
If you meant to change the entry, leave the changed field at it is, and type 2 in the Act field beside the entry.
| CAMX057E |
| Overlapping times |
Explanation: The time range specified overlaps an existing time range definition for that day.
Your response: Verify time range required and make appropriate changes.
| CAMX063W |
| Sign on successful but CallPath/CICS for OS/390 is down |
Explanation: The sign on completed successfully, although CallPath/CICS for OS/390 is down, and is expected to recover automatically.
Your response: When CallPath/CICS for OS/390 does come up, you will see an information message and you will receive calls.
| CAMX064E |
| Sign on unsuccessful due to CallPath/CICS for OS/390 error |
Explanation: The sign on did not complete; CallPath/CICS for OS/390 is not expected to come up automatically.
Your response: Your system administrator can refer to the CICS system log for further information about the CallPath/CICS for OS/390 problem.
| CAMX066E |
| Request not permitted while CallCoordinator is running |
Explanation: This request can be processed only when CallCoordinator is not running.
Your response: Shut down CallCoordinator before making this request.
| CAMX068E |
| Agent is not signed on to terminal |
Explanation: The agent is not signed on to this terminal, so there is nothing to restore.
Your response: Select another option.
| CAMX069E |
| Casual user restore not allowed |
Explanation: Either you are not participating in an active call currently, or you are not the initiating party in this call, so there is nothing to restore.
Your response: Select another option.
| CAMX070E |
| Agent terminal is not permanently disabled |
Explanation: The agent's terminal is not set to permanently disabled (P), so there is nothing to restore.
Your response: Select another option.
| EZP0000I |
| 5655-B34 (C) Copyright IBM Corp. 1992, 1999. All rights reserved All rights reserved |
Explanation: Copyright notice.
Your response: None.
| EZP0001E |
| Function key <aaaaa> not valid, press F3 or F12 to exit |
Explanation: The only valid option after deleting an entry is to exit the detail panel.
Your response: Press F3 or F12 to exit this panel.
| EZP0002I |
| Entry not found |
Explanation: An entry matching your "Position to" field was not found. The panel appears again with the first entry whose key is prior to the "Position to" key that was entered. The "Position to" field remains with the field highlighted.
Your response: If you wish to process actions from the current panel, then you must first clear the "Position to" fields before typing an action. Or, you may correct the "Position to" field, and press Enter to try again.
| EZP0003I |
| Press Enter to confirm delete, or press F12 |
Explanation: You requested a delete action, which resulted in the detail panel appearing, so you can confirm the deletion.
Your response: Press Enter to confirm the delete request, or F12 to cancel the delete.
| EZP0004E |
| Function key <aaaaa> not valid, press Enter or F12 |
Explanation: You pressed a function key other than Enter or F12.
Your response: Press Enter to process the request, or F12 to cancel the request.
| EZP0005I |
| Request to exit has been canceled |
Explanation: You pressed the F12=Cancel key in response to a message asking if you want to process changes or cancel the request to exit. You must process the entries on the panel before you can move to another panel.
Your response: If you want to process the updates on the panel, press the Enter key. Then you see a message indicating the changes were processed, and you can use a function key to move to another panel. If you do not want to save the updates on the panel, press F5=Refresh to return the panel to its original state. Then you can use a function key to move to another panel.
| EZP0006I |
| Press Enter to process changes, or F12 to cancel |
Explanation: You typed an entry on the panel prior to pressing a function key to leave the panel. You must process that entry before you can move to another panel.
Your response: Press Enter to process the changes, or F12 to cancel the request to leave the panel.
| EZP0007E |
| Deleted entry may not be processed |
Explanation: You selected an action for an entry that has been deleted. The entry was deleted after it was initially displayed on this panel. It may have been deleted by you or another user.
Your response: Press F5 to refresh the panel, or select another action.
| EZP0008E |
| Function key <aaaaa> not available on this panel |
Explanation: You pressed a function key with no defined function on this panel.
Your response: Refer to the bottom of the panel to see the acceptable function keys, and press one of those keys.
| EZP0009E |
| Entry must be A-Z, 0-9, && or * |
Explanation: You can type only uppercase letters A through Z, the numerals 0 through 9 (character set 01134), an ampersand (&), or asterisk (*) in this field.
Your response: Type the correct characters.
| EZP0010E |
| Use System Admin menu to access transaction <aaaa> |
Explanation: You typed the CICS transaction <aaaa> for a program that must be accessed by a menu.
Your response: Refer to the Operations Guide for the correct method to access this panel.
| EZP0011E |
| Record has been updated by another user |
Explanation: The record to be accessed was just changed or deleted by another user.
Your response: Cancel the current panel, then reprocess your request.
| EZP0012E |
| Select one of the options available |
Explanation: The selection typed is not valid for this panel.
Your response: Choose one of the selection options listed on this panel.
| EZP0013E |
| You typed an unauthorized transaction |
Explanation: The CICS transaction ID that you typed is not authorized for your use.
Your response: Type another transaction ID.
| EZP0014E |
| Entry is not valid; view field help for details |
Explanation: You typed an incorrect value in this field.
Your response: Position the cursor on the entry field and press F1=Help to learn about the values that you can type in this field.
| EZP0015I |
| End of session |
Explanation: The CallCoordinator session has ended and you have returned to CICS.
Your response: Press the clear (ESC) key to clear the panel, then type a new CICS transaction ID.
| EZP0016I |
| Please wait; request is being processed |
Explanation: This message appears when a request has been made by the agent, such as next call, sign on, etc. A delay may result while the system is processing the request.
Your response: Wait for the system to complete the request. Do not perform any further functions until the request has been processed.
| EZP0017I |
| Request has been processed |
Explanation: The request that was selected has been processed.
Your response: None.
| EZP0018I |
| Request has been canceled |
Explanation: You pressed the F12=Cancel key in response to a confirmation message (i.e. EZP0410I).
Your response: Press F12 to return to the previous panel, or select another option from this panel.
| EZP0019E |
| Change action requires fields to be changed |
Explanation: You typed a code for change action,, but no other fields were changed on this line.
Your response: Change a field on this line, or remove the change action.
| EZP0020E |
| Duplicate record on file |
Explanation: An entry for the record to be added is already on file.
Your response: Verify the information for the record to be added. One of the key identifier fields is contained in another record. Correct the duplicate information.
| EZP0021I |
| Table has no entries in it |
Explanation: The table has no records currently defined.
Your response: None.
| EZP0022E |
| Type valid action code |
Explanation: You typed an action code that is not valid on this panel.
Your response: Type one of the action codes displayed on this panel.
| EZP0023E |
| Table is full; request is not processed |
Explanation: You attempted to add an entry to this file, which is already full.
Your response: Delete an unwanted entry to make room for this one. Or, the system administrator can enlarge this table by using the Table Sizes option on the System Administration menu. The new size will become effective when CICS is recycled, or the system administrator can use the CallCoordinator table reload option on the Problem Determination panel to reload the tables.
| EZP0024E |
| Agent ID not defined |
Explanation: The Agent ID typed is not defined in the Agents table.
Your response: Verify that the Agent ID is correct, or ensure that the Agent ID entry is added to the Agents table.
| EZP0025E |
| Not valid with F7,F8,F9,F10, or Action |
Explanation: You requested to be positioned to a specific entry. At the same time you requested an action to be performed or pressed a function key.
Your response: Remove the action request, and after the list is positioned, you then can request the action.
| EZP0026E |
| Type action code on the correct line |
Explanation: You typed an action code on a blank line.
Your response: You must type action codes on a line that has a valid entry.
| EZP0027I |
| Delete request has been canceled |
Explanation: The F12=Cancel key was pressed in response to a delete confirmation message, and the delete request was canceled.
Your response: None.
| EZP0028E |
| = is not valid for this field |
Explanation: You typed an equal sign (=) in a field to be copied from the entry above, but this field is not a field that can be copied.
Your response: Type in the correct value for this field.
| EZP0029E |
| = is not valid on the first line |
Explanation: You typed an equal sign (=) in a field on the first line. You can only type this character after a valid line with fields to be copied (line 2 or greater).
Your response: Type in the correct value for this field.
| EZP0030E |
| Date is not in the correct format |
Explanation: The entry in this field must match the format defined for date on the CallCoordinator System Settings panel. Your system administrator has defined one of the following formats:
Your response: Try another format, or see your system administrator to find the correct format to use.
| EZP0031E |
| Year must be 00 - 99 |
Explanation: The year must be a numeric value between 00 and 99.
Your response: Type a valid year.
| EZP0033E |
| Month must be 01 - 12 |
Explanation: The month must be between 01 (January) through 12 (December).
Your response: Type a valid month.
| EZP0034E |
| Day out of range |
Explanation: The day typed is not valid for the specified month.
Your response: Type a valid day 01 through n, where n equals:
| EZP0035E |
| The time entry is not in the correct format or is not > |
Explanation: The entry in this field must match the format defined for time on the CallCoordinator System Settings panel, or must be a > (greater than sign) if you are entering a default entry. Your system administrator has defined one of the following formats:
Your response: Try another format, or see your system administrator to find the correct format to use. If you are entering a default entry, use the >.
| EZP0036E |
| Hour must be 00 - 23 |
Explanation: The hour must be a numeric value between 00 and 23 when the 24-hour format has been selected by the system administrator on the CallCoordinator System Settings panel.
Your response: Type a valid hour value.
| EZP0037E |
| Hour must be 01 - 12 |
Explanation: The hour must be a numeric value between 01 and 12 when the 12-hour format has been selected by the system administrator on the CallCoordinator System Settings panel.
Your response: Type a valid hour value.
| EZP0039E |
| Minutes must be 00 - 59 |
Explanation: The minutes must be a numeric value between 00 and 59.
Your response: Type a valid minutes value.
| EZP0040E |
| AM or PM must be specified |
Explanation: The CallCoordinator General System Settings panel indicates that time fields must be specified as AM or PM for a 12-hour clock.
Your response: Type AM or PM after the time (for example, 02:00PM).
| EZP0041E |
| Enter a number greater than zero |
Explanation: The entry in this field cannot be zero or less than zero.
Your response: Type a valid value.
| EZP0042E |
| Seconds must be 00 - 59 |
Explanation: The seconds must be a numeric value from 00 to 59.
Your response: Type a valid seconds value.
| EZP0043E |
| Entry must be A or C |
Explanation: You typed an incorrect value.
Your response: Type an A or C.
| EZP0047E |
| Entry must be Y, N, I, R, or blank |
Explanation: You typed an incorrect value.
Your response: Type a Y, N, I, R, or blank.
| EZP0048E |
| Entry must be Y, N, I, or R |
Explanation: You typed an incorrect value.
Your response: Type a Y, N, I, or R.
| EZP0049E |
| Entry must be Y, N, or blank |
Explanation: You typed an incorrect value.
Your response: Type the correct value of Y, N, or blank.
| EZP0050E |
| Entry must be Y or N |
Explanation: You typed an incorrect value.
Your response: Type the correct value of Y or N.
| EZP0051E |
| Enter numbers in this field |
Explanation: This field must contain a combination of the numbers 0 thru 9.
Your response: Type the correct value.
| EZP0052E |
| Type / or other defined choice symbol |
Explanation: This field must contain the slash character (/), or the choice symbol that is defined on the CallCoordinator System Settings panel (EZPDS01).
Your response: Type either / (slash) or the correct choice symbol in this field.
| EZP0053E |
| Program ID does not exist |
Explanation: A system error has occurred.
Your response: Notify your system administrator. Note the ID and title of the panel where the request was made. Check the CICS system log for additional information.
| EZP0054E |
| Entry in this field is required |
Explanation: The field is highlighted and the cursor is positioned at the field where the entry must be typed.
Your response: Type the correct value for this field. Use F1=Help to find more information about the values.
| EZP0055E |
| Enter a valid language code |
Explanation: The language code entered on the panel is not a valid code for this installation.
Your response: Type a valid language code. See your system administrator to learn what languages are defined for your installation.
| EZP0056E |
| Language not installed |
Explanation: The code typed for the language is not defined for this installation.
Your response: Type a valid language code. See your system administrator to learn what languages are installed.
| EZP0057E |
| The Group entered has not been defined |
Explanation: The Group ID typed is not defined.
Your response: Verify that the Group ID is correct, or request correct Group ID from the system administrator.
| EZP0058E |
| Entry must be T or B |
Explanation: This field requires an entry of T or B, to indicate whether you want messages to display at the top or bottom of the panel.
Your response: Type a correct entry.
| EZP0059E |
| Entry must be A-Z or 0-9 |
Explanation: You can type only uppercase letters A through Z and the numerals 0-9 (character set 01134) in this field.
Your response: Type the correct character.
| EZP0060E |
| Time offset must be -11 thru +12 |
Explanation: You entered a time offset that was less than -11 or greater than +12.
Your response: Enter a number between -11 and +12.
| EZP0061E |
| The Switch entered has not been defined |
Explanation: The Switch ID typed is not defined in the Switches table.
Your response: Verify that the Switch ID is correct, or request correct Switch ID from the system administrator.
| EZP0063E |
| DBCS information is not valid |
Explanation: The DBCS edit has failed. This can be caused when there are unmatched shift out and shift in characters.
Your response: Make sure the field is formatted correctly.
| EZP0064E |
| Language not enabled |
Explanation: The language that was input is installed, but has not been translated for the particular audience (that is, Agent, Administrator, or CICS system log). For common language defaults on the CallCoordinator System Settings panel (EZPDS01), the language must be enabled for CallCoordinator.
Your response: Verify that the language that was entered has been installed for your audience type.
| EZP0070E |
| RETURN CODE <aaaa> FROM <bbbbbbbb>, TRAN <cccc>, TERMID <dddddddd>, LOC <eeee> |
Explanation: An unexpected return code was received from the module <bbbbbbbb>.
Your response: Call the IBM Software Support Center.
| EZP0071E |
| CICS error in executing program <aaaaaaaa> |
Explanation: An error condition was encountered while attempting a CICS function.
Your response: Contact your systems programmer for assistance.
| EZP0072E |
| System error in executing program <aaaaaaaa> |
Explanation: An error condition was encountered while attempting a CallCoordinator function.
Your response: Contact your systems programmer for assistance.
| EZP0081E |
| Field type <aaaaaaaa> not found in translate table |
Explanation: The system attempted to translate a variable to or from English using the in-core translate table but could not find the field type <aaaaaaaa>.
Your response: Contact your systems programmer. The systems programmer will need to check to see if all of the language decode tables have been properly installed. If all of the tables are properly installed, a storage violation must have occurred. If this is the case, fix the storage violation and recycle the region. If the problem persists, call the IBM Software Support Center. Refer to message EZP0082E.
| EZP0082E |
| FIELD TYPE <aaaaaaaa> NOT FOUND IN TRANSLATE TABLE, TRANID <bbbbbbbb>, TERMID <cccccccc> |
Explanation: System attempted to translate a variable to or from English using the in-core translate table but could not find the field type.
Your response: Check to see if all of the language decode tables have been properly installed. If all of the tables are properly installed, a storage violation must have occurred. If this is the case, fix the storage violation and recycle the region. If the problem persists, call the IBM Software Support Center.
| EZP0083E |
| RETURN CODE <aaaa> DURING <bbbbbbbbbb> QUEUE <cccccccc>, TRAN <dddddddd>, TERMID <eeeeeeee>, LOC <ffffffff> |
Explanation: A CICS return code occurred while performing the operation. The queue refers to the TS or TD queue involved. Transaction ID, Terminal ID and Procedure (LOC) are also provided.
Your response: The meanings of the CICS return codes can be found in the CICS Application Programmers' Reference. If the problem is an undefined TD queue, add the definition to the DCT and/or JCL stream. Otherwise a program error is indicated. If this is the case, call IBM Software Support Center.
| EZP0084E |
| RETURN CODE <aaaa> DURING <bbbbbbbbbb> PGMID <cccccccc>, TRAN <dddddddd>, TERMID <eeeeeeee>, LOC <ffff> |
Explanation: A CICS return code <aaaa> occurred while performing the operation <bbbbbbbbbb>. The program ID <cccccccc> refers to the program which is the object of the operation. Transaction ID, Terminal ID and Procedure (LOC) may also be provided.
Your response: The meanings of the CICS return codes can be found in the CICS Application Programmers' Reference. If the problem is an undefined or disabled program, add or fix the definition in the PPT. Otherwise a program error is indicated. If this is the case, call IBM Software Support Center.
| EZP0085E |
| RETURN CODE <aaaa> DURING <bbbbbbbbbb> FILE <cccccccc>, TRAN <dddddddd>, TERMID <eeeeeeee>, LOC <fffff> |
Explanation: A CICS return code occurred while performing the operation. The file refers to the file which is the object of the operation. Transaction ID, Terminal ID and Procedure (LOC) are also provided.
Your response: The meanings of the CICS return codes can be found in the CICS Application Programmers' Reference. If the problem is an undefined or disabled file, add or fix the definition in the FCT. Otherwise a program error is indicated. If this is the case, call IBM Software Support Center.
| EZP0086E |
| RETURN CODE <aaaa> DURING <bbbbbbbbbb> MAP <cccccccc>, TRAN <dddddddd>, TERMID <eeeeeeee>, LOC <ffff> |
Explanation: A CICS return code <aaaa> occurred while performing the operation. MAP refers to the BMS map which is the object of the operation. Transaction ID, Terminal ID and Procedure (LOC) are also provided.
Your response: The meanings of the CICS return codes can be found in the CICS Application Programmers' Reference. If the problem is an undefined or disabled program, add or fix the definition in the PPT. Otherwise a program error is indicated. If this is the case, call IBM Software Support Center.
| EZP0087E |
| RETURN CODE <aaaa> DURING <bbbbbbbbbb> TRNID <cccccccc>, TRAN <dddddddd>, TERMID <eeeeeeee>, LOC <ffff> |
Explanation: A CICS return code <aaaa> occurred while performing the operation. TRNID refers to the transaction which is the object of the operation. Transaction ID, Terminal ID and Procedure (LOC) are also provided.
Your response: The meanings of the CICS return codes can be found in the CICS Application Programmers' Reference. If the problem is an undefined or disabled transaction, add or fix the definition in the PPT. Otherwise a program error is indicated. If this is the case, call IBM Software Support Center.
| EZP0088E |
| RETURN CODE <aaaa> DURING <bbbbbbbbbb>, TRAN <cccccccc>, TERMID <dddddddd>, LOC <eeee> |
Explanation: A CICS return code occurred while performing the operation. Transaction ID, Terminal ID and Procedure (LOC) are also provided.
Your response: The meanings of the CICS return codes can be found in the CICS Application Programmers' Reference. Call IBM Software Support Center.
| EZP0089E |
| Return code <aaaa> during <bbbbbbbbbb>, queue <cccccccc> |
Explanation: A CICS return code <aaaa> occurred while performing the operation <bbbbbbbbbb>. <cccccccc> refers to the TS or TD queue involved.
Your response: Contact your systems programmer.
The systems programmer can find the meanings of the CICS return codes in the CICS Application Programmers' Reference. If the problem is an undefined TD queue, add the definition to the DCT and/or JCL stream. Otherwise a program error is indicated. If this is the case, call IBM Software Support Center. Refer to message EZP0083E.
| EZP0090E |
| Return code <aaaa> during <bbbbbbbbbb>, pgmid <cccccccc> |
Explanation: A CICS return code <aaaa> occurred while performing the operation <bbbbbbbbbb>. <cccccccc> refers to the program that was the object of the operation.
Your response: Contact your systems programmer. The systems programmer can find the meanings of the CICS return codes in the CICS Application Programmers' Reference. If the problem is an undefined or disabled program, add or fix the definition in the PPT. Otherwise a program error is indicated. If this is the case, call IBM Software Support Center. Refer to message EZP0084E.
| EZP0091E |
| Return code <aaaa> during <bbbbbbbbbb>, file <cccccccc> |
Explanation: A CICS return code <aaaa> occurred while performing the operation <bbbbbbbbbb>. <cccccccc> refers to the file that was the object of the operation.
Your response: Contact your systems programmer. The systems programmer can find the meanings of the CICS return codes in the CICS Application Programmers' Reference. If the problem is an undefined or disabled file, add or fix the definition in the FCT. Otherwise a program error is indicated. If this is the case, call IBM Software Support Center. Refer to message EZP0085E.
| EZP0092E |
| Return code <aaaa> during <bbbbbbbbbb>, map <cccccccc> |
Explanation: A CICS return code <aaaa> occurred while performing the operation <bbbbbbbbbb>. <cccccccc> refers to the map that was the object of the operation.
Your response: Contact your systems programmer. The systems programmer can find the meanings of the CICS return codes in the CICS Application Programmers' Reference. If the problem is an undefined or disabled program, add or fix the definition in the PPT. Otherwise a program error is indicated. If this is the case, call IBM Software Support Center. Refer to message EZP0086E.
| EZP0093E |
| Return code <aaaa> during <bbbbbbbbbb>, tranid <cccccccc> |
Explanation: A CICS return code <aaaa> occurred while performing the operation <bbbbbbbbbb>. <cccccccc> refers to the transaction that was the object of the operation.
Your response: Contact your systems programmer. The systems programmer can find the meanings of the CICS return codes in the CICS Application Programmers' Reference. If the problem is an undefined or disabled transaction, add or fix the definition in the PPT. Otherwise a program error is indicated. If this is the case, call IBM Software Support Center. Refer to message EZP0087E.
| EZP0094E |
| Return code <aaaa> during <bbbbbbbbbb> |
Explanation: A CICS return code <aaaa> occurred while performing the operation <bbbbbbbbbb>.
Your response: Contact your systems programmer. The systems programmer can find the meanings of the CICS return codes in the CICS Application Programmers' Reference. If the problem is an undefined or disabled program, add or fix the definition in the PPT. Otherwise a program error is indicated. If this is the case, call IBM Software Support Center. Refer to message EZP0084E.
| EZP0096E |
| Error in program <aaaaaaaa> RC <bbbb> |
Explanation: An unexpected return code <bbbb> was returned from the program <aaaaaaaa>.
Your response: Program error; contact the IBM Software Support Center.
| EZP0097E |
| SYSTEM ERROR <aaaa> IN <bbbbbbbb> |
Explanation: An unexpected return code <aaaa> was returned from the program <bbbbbbbb>.
Your response: Program error, contact IBM Software Support Center.
| EZP0098E |
| Please specify time in 24 hour format |
Explanation: The CallCoordinator System Settings panel indicates that time fields must be specified in 24 hour format (AM and PM are not specified).
Your response: Remove the AM or PM notation, and check that the hour is in 24 hour format.
| EZP0101E |
| From date/time - To date/time not valid |
Explanation: When specifying dates and time for when a client is called, the To date/time must be later than the From date/time and if one of the fields is specified, all four must be specified.
Your response: Correct the fields.
| EZP0102E |
| Field must be defined for this Agent ID |
Explanation: The field indicated is not defined for this Agent ID on the Agents table.
Your response: Verify that the field is correct, or add that entry for this Agent ID on the Agents table.
| EZP0103E |
| Agent is signed on; you cannot delete |
Explanation: The entry cannot be deleted from the Agents table when the agent is signed on to CallCoordinator.
Your response: Clear the action code, verify that this is the correct entry, and try again later.
| EZP0109E |
| Date separator must be ''/'', ''-'', or ''.'' |
Explanation: The date separator you typed is not valid.
Your response: Type a valid separator.
| EZP0110E |
| Time separator must be '':'', or ''.'' |
Explanation: The time separator you typed is not valid.
Your response: Type a valid separator.
| EZP0118I |
| Copy pending. Type fields, then press Enter |
Explanation: You requested a copy action, which resulted in the detail panel appearing, so you can complete the action.
Your response: Change the fields, then press Enter to add the entry.
| EZP0119I |
| Add pending. Type fields, then press Enter |
Explanation: You requested an add action, which resulted in the detail panel appearing, so you can complete the action.
Your response: Type the fields, then press Enter to add the entry.
| EZP0163I |
| CAMTCORS TSQ LOADED SUCCESSFULLY |
Explanation: The TSQ containing the list of CORs and their status has been loaded.
Your response: None.
| EZP0164I |
| CAMTSWIT TSQ LOADED SUCCESSFULLY |
Explanation: The TSQ containing the list of Switches and their status has been loaded.
| EZP0165E |
| CAMTCORS TSQ CREATE FAILED - RETURN CODE <aaaa> |
Explanation: A CICS command failed while creating the CAMTCORS TS Queue for CallCoordinator. This TS Queue contains entries for each COR within the system and stores information such as whether CallCoordinator is active in the specific COR. This message is preceded by one of the following messages: EZP0083E, EZP0084E, which specify which CICS command failed, the Return Code, and the resource(s) involved.
Your response:
Otherwise call the IBM Support Centre for assistance.
| EZP0203E |
| Sign on failed; Agent record is not active |
Explanation: The agent cannot sign on if agent's record status is not set to Y (active).
Your response: Contact your system administrator to change the Record status field to Y for your Agent ID on the Agents table.
| EZP0204I |
| Sign off is complete |
Explanation: The sign off request has been processed.
Your response: Select another CICS transaction, or log off from CICS.
| EZP0206I |
| Already signed on; view message help for details |
Explanation: This Agent ID is already signed on at another terminal.
Your response: Pressing Enter will sign this Agent ID off of the other terminal and complete the sign on to this terminal. Pressing F12 will cancel the sign on request here, and leave the other terminal sign on active.
| EZP0207I |
| Agent ID <aaaaaaaaaa> signed on here; view message help |
Explanation: The Agent ID shown is signed on to this terminal.
Your response: Pressing Enter will sign that agent off of the terminal and sign on your Agent ID to this terminal. Pressing F12 will cancel the sign on request here, and leave the other Agent ID signed on here.
| EZP0208E |
| You are not signed on to this feature |
Explanation: A sign off request cannot be processed because you are not signed on to CallCoordinator.
Your response: None.
| EZP0209E |
| Incomplete search fields |
Explanation: Additional fields must be selected.
Your response: Type Switch ID and Extension ID, or Agent ID.
| EZP0210E |
| Both Transfer msg and Clear screen are required |
Explanation: If either the Transfer msg or Clear screen fields are entered, the other field must also be entered, or both must be blank.
Your response: Enter both fields, or blank them out.
| EZP0211I |
| Agent ID <aaaaaaaaaa> signed on to Ext ID; view message help |
Explanation: The Agent ID (shown) is signed on to the Switch/Ext ID that is listed on this panel.
Your response: Pressing Enter will sign that agent off of the terminal and sign on your Agent ID to this terminal. Pressing F12 will cancel the sign on request here, and leave the other Agent ID signed on here.
| EZP0212I |
| Already signed on to <aaaaaaaa> <bbbbbbbbbb>; view message help |
Explanation: This Agent ID is already signed on at Switch <aaaaaaaa> Extension ID <bbbbbbbbbb>.
Your response: Pressing Enter will sign this Agent ID off of the other Switch/Ext ID and complete the sign on to this Switch/Ext ID. Pressing F12 will cancel the sign on request here, and leave the other Switch/Ext ID sign on active.
| EZP0213E |
| This field cannot be changed, press Enter |
Explanation: The field indicated cannot be changed. The original value has been restored. Key fields cannot be changed. An entry must be deleted and then added.
Your response: Press Enter to continue processing the panel. If you are not able to add entries, contact the system administrator.
| EZP0215I |
| Sign on complete |
Explanation: The sign on request has been processed successfully.
Your response: None.
| EZP0301E |
| Maximum number of CORs is 8 |
Explanation: The maximum number of CallPath-Owning Regions (CORs) allowed in a Sysplex is eight.
Your response: Do not try and define more than eight CORs.
| EZP0302E |
| New COR name required |
Explanation: When you copy a COR in order to define a new COR you must give it a name.
Your response: Enter a name for the new COR in the new COR name field.
| EZP0303E |
| New COR name must be unique |
Explanation: The name of a new COR must be unique.
Your response: Enter a unique COR name in the new COR name field.
| EZP0304E |
| Only one COR defined, cannot be deleted |
Explanation: You have attempted to delete a COR on the System Configuration panel, but at least one COR must be defined.
Your response: In a sysplex environment, use the copy function to add the CORs required and then delete those that are not required. In a single system environment, this option should not be required.
| EZP0400E |
| Interval exceeds Max Call Life |
Explanation: The entry you made in the Interval field is larger than the entry you made in the Max Call Life field.
Your response: Correct one of the entries.
| EZP0401I |
| Start up process has been initiated |
Explanation: The start up process has begun. This will take a few minutes to complete.
Your response: None.
| EZP0402I |
| Shut down process has been initiated |
Explanation: The shut down process has begun.
Your response: None.
| EZP0403E |
| Read failed for EZPACIV: Common table size record |
Explanation: An error occurred trying to read the Common table size record from the EZPACIV VSAM file.
Your response: Dump the EZPACIV VSAM file and check that the common table size record was initialized with this record.
| EZP0404E |
| Entry must be A, B, J, X, or Blank |
Explanation: The file suffix for the Log History file must be a J or X. If left blank, then no log records will be written. If J is selected then logs are written to a CICS User Journal and the Journal Id must be entered in the Journal ID field. If X is selected the MIS log record is passed to the MIS User Exit only. No records will be written.
Your response: Type the valid suffix, or clear the field with a blank.
| EZP0405W |
| Long running task(s) are active, try again |
Explanation: The reload could not be processed because one or more long running tasks are still active.
Your response: Wait a while (no more than a minute), and then try the request again.
| EZP0406E |
| Entry previously flagged for deletion |
Explanation:
Your response:
| EZP0407E |
| Too many "Position to" fields |
Explanation: The Agents table can be positioned by Agent ID, Switch ID, or a combination of Switch ID and Ext ID. The Agent ID cannot be used in combination with Switch ID or with Ext ID.
Your response: Determine which specification is required and which specifications can be omitted. Erase the specifications that can be omitted.
| EZP0408E |
| Field cannot be changed; agent is signed on |
Explanation: The Agent ID listed on this entry is currently signed on to CallCoordinator (refer to Signed on field). The fields that identify the Agent and telephone (Agent ID, Switch ID and Ext ID) cannot be changed.
Your response: The Agent ID that is signed on must first be signed off before you can change the fields.
| EZP0409E |
| Switch ID is defined on the Agents table |
Explanation: This Switch ID cannot be changed or deleted. The ID is currently defined for agents on the Agents table.
Your response: Clear the action code, verify that this is the correct entry. Entries must be changed on the Agents table before this switch ID can be deleted.
| EZP0410I |
| Shutdown requested; press Enter to process or press F12 |
Explanation: The shutdown option was requested. This is a confirmation message to inform you that the shutdown option was selected.
Your response: Press the Enter key to continue with the shutdown request or press F12=Cancel to cancel the shutdown request.
| EZP0413E |
| Reload cannot be processed; CallCoordinator is active |
Explanation: The option to reload CallCoordinator tables was not processed. The CallCoordinator long running tasks are currently active.
Your response: If shutdown was already selected, then wait until all tasks are inactive. If shutdown has not been requested, then shut down CallCoordinator from the CallCoordinator Start Up/Shut Down panel (CAM9901), then select the reload option again.
| EZP0414E |
| Fields cannot be changed when agents are signed on |
Explanation: The fields defined for this Switch ID cannot be changed now, because a CallCoordinator agent is signed on to this switch.
Your response: Cancel the change request. Wait until no agents are signed on to this switch and then make the changes.
| EZP0415E |
| Field can not be changed; Switch/Ext ID is signed on |
Explanation: The Switch/Ext ID listed on this entry is currently signed on to CallCoordinator. This entry can not be changed or deleted.
Your response: The agent that is signed to this Switch/Ext ID must first sign off before you can change the fields or delete the entry.
| EZP0416E |
| Duplicate Position ID for this switch |
Explanation: An attempt was made to add or change an entry with a Position ID that is already defined for this switch.
Your response: Either correct the Position ID, or determine if the other entry should be changed. You can use the "Position to" function to find the entry where this Position ID is defined.
| EZP0417E |
| Start up/Shut down in progress |
Explanation: A request to start up was made while a shutdown was in progress, or a shutdown was requested while a start up was in progress.
Your response: Wait until the current start up/shutdown is complete and then make this request.
| EZP0418E |
| Entry must be A or B |
Explanation: The suffix for the Trace (VSAM) file must be an A or B.
Your response: Type the valid suffix.
| EZP0419E |
| Entry must be Y or blank |
Explanation: You typed an incorrect value.
Your response: Type the correct value of Y or blank.
| EZP0420E |
| Exit name does not exist |
Explanation: You entered a program ID that is not defined for this CICS region.
Your response: Correct the program ID.
| EZP0421E |
| First 3 characters must be <aaa> |
Explanation: You entered a program name that does not begin with <aaa>. The CallPath Services Program Name must begin with the three characters that identify it for CallCoordinator (CAM).
Your response: Correct the program name.
| EZP0442E |
| Fields cannot be changed/deleted; In use by Transfer Load Balancing |
Explanation: You have attempted to delete or change a resource that is currently in use by Transfer Load Balancing.
Your response: The resource must be removed from Transfer Load Balancing first. This may involve removing the resource from the Load Balance Function menu, the Balance Point menu or the Inter-Switch Tracking Number menu.
| EZP0501E |
| Error in <aaaaaaaa>. Contact system support |
Explanation: An unexpected error was received by the current program from <aaaaaaaa>.
Your response: Program error has occurred. Contact your system support personnel.
| EZP0502E |
| RETURN CODE <aaaa> FROM <bbbbbbbb>, ITEM <cccccccccccccc> |
Explanation: An unexpected return code from program <bbbbbbbb> was received. The program that issued this message was passed the return code <aaaa>, but does not have logic that processes this return code. The item <cccccccccccccc> may provide information regarding the cause of this message.
Refer to the CallPath CallCoordinator/CICS Application Programming Guide or CallPath CallCoordinator/CICS Problem Determination books for more information.
Your response: If a system error, then contact the IBM Software Support Center.
| EZP0503I |
| BEGIN CALLCOORDINATOR TABLE LOAD VIA -<aaaa>- |
Explanation: The table load process has been started by transaction -<aaaa>-
Your response: None.
| EZP0504E |
| ADDRESSING ERROR IN - EZPACTLC - PROGRAM, END PROCESSING |
Explanation: There is a problem loading or addressing the CallCoordinator Common Information table.
Your response: Contact the IBM Software Support Center.
| EZP0505E |
| TABLE LOAD FAILED FOR <aaaaaaaa> - RETURN CODE <bbbb> |
Explanation: The assembler table program <aaaaaaaa> could not be loaded. Check that this program is defined in the PPT and in the LOADLIB.
Your response: Contact your system programmer.
| EZP0506W |
| RETURN CODE <aaaa> DURING ATTEMPT TO WRITE MESSAGE TDQ <bbbbbbbb>, SWITCHING TO CSMT |
Explanation: A write to a transient data queue used for CICS system log messages specified on the CallCoordinator CallCoordinator System Setting panel resulted in the return code. The name of the queue is identified in the message. The system switches to TDQ CSMT.
Your response: If the TDQ is a misspelling of the intended queue name, enter it again on the CallCoordinator CallCoordinator System Settings panel. The change takes place as soon as the record is updated. If the TDQ is the correct name, ensure that an entry has been defined in the DCT and the DDname is specified in the CICS startup JCL.
| EZP0507I |
| TABLE - <aaaaaaaa> - LOADED SUCCESSFULLY |
Explanation: Table <aaaaaaaa> has been loaded successfully.
Your response: None.
| EZP0508I |
| TABLE - <aaaaaaaa> - CONFIGURED FOR <bbbb>, PRESENT UTILIZATION <cccc> |
Explanation: Table <aaaaaaaa> has been loaded and initialized.
Your response: If the utilization is over 90 % consider reconfiguring the table size.
| EZP0509E |
| CALLCOORDINATOR LANGUAGE TABLE DOES NOT EXIST FOR <aaaaaaaa> |
Explanation: For a given language, the CallCoordinator common language table does not exist. For this language to be used, the common language table must be present, otherwise the language is not available.
Your response: Make sure that the common language table is defined in the PPT and the LOADLIB.
| EZP0510E |
| ONLY CALLCOORDINATOR LANGUAGE TABLE EXISTS FOR %1(08) |
Explanation:
Your response:
| EZP0511E |
| DUPLICATE TERMINAL ID <aaaaaaaa> -- SWITCH ID <bbbbbbbb> EXTENSION ID <cccccccccc> |
Explanation: A duplicate Terminal ID was found while loading the Agents table from the VSAM file EZPAAGV.
The duplicate terminal ID <aaaaaaaa> was set to blank in the VSAM file and in the CICS storage for the extension ID <cccccccccc>.
Your response: Determine how the duplicate ID got into the file (that is, a logic error in CallCoordinator, or the VSAM file loaded by a utility program). Correct the error.
| EZP0512E |
| DUPLICATE AGENT ID <aaaaaaaaaa> -- SWITCH ID <bbbbbbbb> EXTENSION ID <cccccccccc> |
Explanation: A duplicate Agent ID was found while loading the Agents table from the VSAM file EZPAAGV.
The duplicate Agent ID <aaaaaaaaaa> was set to blank in the VSAM file and in the CICS storage for the extension ID <cccccccccc>.
Your response: Determine how the duplicate ID go into the file (e.g. a logic error in CallCoordinator, or the VSAM file loaded by a utility program).
| EZP0513E |
| LOAD ERROR - TABLE <aaaaaaaa> LOADED ENTRIES <bbbb> VSAM FILE ENTRIES <cccc> |
Explanation: This message is written to the system log when there are more entries defined in the VSAM file than are configured for the table that will be loaded.
Your response: Increase the size of the table indicated.
| EZP0515I |
| END CALLCORDINATOR TABLE LOAD |
Explanation: The CallCordinator table load process has been completed.
Your response: None.
| EZP0516E |
| CANNOT LOCATE AVAILABLE LANGUAGE INFORMATION, END PROCESSING |
Explanation: This table must exist for CallCoordinator Common Table process to continue.
Your response: Verify that EZPSLNGL is defined in the PPT and LOADLIB.
| EZP0517I |
| STORAGE ACQUIRED FOR TABLE - <aaaaaaaa> |
Explanation: Storage for the referenced table has been acquired. The identifiers and table names are:
Your response: None.
| EZP0518E |
| TABLE SIZE INFORMATION MISSING, END PROCESSING |
Explanation: Table size information table must exist for the common table load to continue.
Your response: Verify that EZPSMTSL is defined in the PPT and LOADLIB.
| EZP0519E |
| TABLE LOAD TIMED OUT DUE TO ERROR IN PREVIOUS INVOCATION |
Explanation: A previous invocation of EZPACTLC set the table load indicator to "start", but never set it to "complete". The current invocation waited the maximum time for the previous invocation to finish. A message from the previous invocation appears on the CICS system log, indicating the reason for the failure.
Your response: Follow the directions for the error message written by the first invocation.
| EZP0520E |
| RETURN CODE <aaaa> REASON CODE <bbbb> FROM <cccccccc>, ITEM <dddddddddddddd |
Explanation: An unexpected return code <aaaa> and reason code <bbbb> from program <cccccccc> was received. The program that issued this message was passed the return code, but does not have logic that proccesses this return code. The item <dddddddddddddd> may provide information regarding the cause of this message.
Your response: If a system error, then contact the IBM Software Support Center.
| EZP7203I |
| TERMINAL ID <aaaaaaaa> AUTOMATICALLY SIGNED OFF CALLCOORDINATOR |
Explanation: This message is written to the CICS system log when the terminal <aaaaaaaa> is signed off from CallCoordinator. The following conditions can cause this to happen:
Your response: None
| EZP9101E |
| CONNECT TABLE ERROR, RC <aa> FROM <bbbbbbbb> |
Explanation: A CallCoordinator API could not load the MRO connect table via its front end processor <bbbbbbbb>. The return code <aa> explains the reason:
Your response: If return code 08, check to see that the program EZPSCCTL is defined in the CICS region and is available from the DFHRPL. If return code 12, check the Connect Table program EZPSCCTL to make sure that the correct CICS Application IDs were used to create it. Your systems programmer who installed CallPath CallCoordinator can check the output from the connect table generation JOB to check the connect table. If return code is 02, contact IBM support.
| EZP9201E |
| SYSLOG DESTINATION TO QUEUE <aaaaaaaa> NOT VALID |
Explanation: The transient data queue specified in the system parameters for Syslog messages was not found. Messages will be written to the CICS system log.
Your response: Define the transient data queue in the DCT (Destination Control Table), or change Syslog destination to CICS system log, by changing the entry to CSMT in the System log ID field on the CallCoordinator System Settings panel (EZPDS01).
| EZP9301E |
| Help is not available for this request |
Explanation: The help processing module did not find a match for the key passed by the calling program.
Your response: Program error has occurred. Contact your system support personnel.
| EZP9302I |
| No display fields on this panel |
Explanation: You pressed the F4=Display fields help function key, but this panel has no display only fields to describe.
Your response: Press F12=Cancel to return to the Help panel or F3=Exit to return to the application panel.
| EZP9303E |
| Help is not available for this program |
Explanation: There is no help function available for this program.
Your response: None
