This chapter discusses the Common Component error messages.
This section contains the following topics:
Reason:
The CICS Cross Memory online interface must be executed on a system that runs MVS/XA or higher.
Action:
Run the Cross Memory task on a MVS/XA system or higher.
Reason:
The DFHPPT or RDO definition for the EC1CIEND program is wrong. The comment indicates the specific error. You are possibly not using Version 4.1 or a later version of CICS. EC1CEND requires Version 4.1 or a later version of CICS to work.
Action:
Correct the EC1CIEND definition.
Reason:
The EC1XSTSK has not shut down after waiting 10 seconds. The termination program stops with this error.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The subtask termination program has requested that the MVS subtask terminate; this occurs when CICS is being shut down and the PLTSD program is executed, or when a terminal operator requests that the subtask be shut down through the operator interface (CICS OP20 transaction).
Action:
None. This message is informational.
Reason:
EC1CIEND has terminated the subtask for EC1XSTSK.
Action:
None. This message is informational.
Reason:
The CICS Cross Memory online interface must be executed on a system that runs MVS/XA or higher.
Action:
Run the Cross Memory task on an MVS/XA system or higher.
Reason:
The DFHPPT or RDO definition for the EC1CINIT program is wrong. The comment indicates what specifically is found to be in error. You are possibly not using Version 4.1 or a later version of CICS. EC1CINIT requires Version 4.1 or a later version of CICS to work.
Action:
Correct the EC1CIEND definition.
Reason:
EC1CINIT could not get enough storage to initialize. The MAXUSER parameter in EC1XMCTR is used to determine the initial storage requirements.
Action:
Reduce the value that is assigned to MAXUSER or increase the storage available above the 31-bit line in the region.
Reason:
EC1CINIT could not start the service transaction defined in the EC1XMCTR table. This transaction is required. The subtask is terminated.
Action:
Try to execute EC1CINIT again.
Reason:
EC1CINIT could not start the EC1XSTSK subtask. The system cannot be initialized.
Action:
Try to execute EC1CINIT again.
Reason:
The subtask is active when EC1CINIT was executed. The control table was reloaded and no other changes were made. Some initialization options (MAXUSER, MSGLVL) are ignored.
Action:
None. This message is informational.
Reason:
EC1CINIT requires more storage above the 24-bit line to be initialized.
Action:
Increase the line storage by increasing the region size of CICS or TSO.
Reason:
EC1CINIT could not find the correct version of the CICS release-dependent program.
Action:
Review the Installation Guide and see http://ca.com/support for the most latest requirements for CICS.
Reason:
The EC1CINIT program has checked and found one or more required programs cannot be loaded from the STEPLIB or DFHRPL.
Action:
Review the CICS JOBLOG for EBCCIN10 or EBCCIN11 error messages indicating the specific programs that are not found. Copy the required programs to the STEPLIB/DFHRPL and restart the initialization process.
Reason:
The listed program is not found in the STEPLIB and is required for normal operation.
Action:
Move the program to the CICS STEPLIB.
Note: This program cannot be loaded from the CICS DFHRPL libraries.
Reason:
The listed program is not found in the DFHRPL and is required for normal operation.
Action:
Move the program to the CICS DFHRPL.
Note: The progam cannot be loaded from the CICS STEPLIB or linklist.
Reason:
EC1CINIT finished initializing without error.
Action:
None. This message is informational.
Reason:
You are not using MVS/ESA. EC1CISRV requires MVS/ESA to work.
Action:
Use MVS/ESA, and then try again.
Reason:
The DFHPPT or RDO definition for the EC1CISRV program is wrong. The comment indicates what specifically was in the error. You are possibly not using Version 4.1 or a later version of CICS. EC1CISRV requires Version 4.1 or a later version.
Action:
Correct the EC1CISRV definition.
Reason:
The EC1XSTSK program is not executing. EC1CISRV requires the EC1XSTSK to work. EC1CISRV ends. EC1CINIT, which starts the subtask, was not executing. The subtask stopped.
Action:
See your operations administrator for more information.
Reason:
An internal error occurred in EC1CISRV.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
EC1CISRV is not designed to be attached to a terminal. EC1CISRV ends.
Action:
Refrain from executing EC1CISRV from a terminal.
Reason:
The service program has abended and shut down.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
This is an informational message response that is written to the terminal.
Action:
Review the associated message text for further information. Also review error messages that are displayed before this about the cause. For assistance, contact Technical Support at http://ca.com/support if necessary.
Reason:
The EC1CISRV service transaction has been stopped.
Action:
Review the error messages that are displayed before this message about the cause. For assistance, contact Technical Support at http://ca.com/support if necessary.
Reason:
VIEW received a CICS LENGERR condition when doing a screen send to a terminal where 'x' indicates the CICS release level being used and 4 = CICS Release 4 or above.
Action:
Retry VIEW command. For assistance, contact Technical Support at http://ca.com/support.
Reason:
An allocation error, access error, or I/O error occurred with the CA View database as described by the text of the message where:
database
Identifies the high-level prefix of the database.
dccb
Represents a hexadecimal string identifying the data set, relative cylinder, and relative block in the database.
Function
Identifies the type of catalog function that failed for a RENAME.
ccc
Indicates the internal control block being accessed (SFB, IFB, or XFB).
eeee
Identifies the internal error code of the logical I/O error.
Kkkkkkkkkkkkkkkk
Specifies the key of the record in hex (if the key is longer than 16 bytes, only the first 16 bytes are shown).
nnn
Represents a number to identify a data set number, number of blocks, return code, or error code.
xxxx
or xxxxxxxxRepresents a hexadecimal number for an error code, information code, or reason code.
Action:
Correct the problem with the database. This can require copying the database with the SARDBASE utility or, in the extreme case, recovering the database.
Note: For more information about database utilities, see the chapters "Database Utilities" and "Backing Up and Recovering the Database" in the Reference Guide.
Reason:
The software release level does not match the database release level.
Action:
Verify that you are using the correct steplib (loadlib). If it is correct, run the SARDBASE utility to version the database to the correct level.
Reason:
A report was deleted from the disk while it was being viewed.
Action:
Verify that the report is no longer on the disk, and then reload it back to disk.
Reason:
A report was compressed and archived to disk using MVS Compression Services, but your current operating system does not support MVS Compression Services.
Action:
If the report is archived to tape, delete the disk copy and reload the report from tape. If the report is not archived to tape, access the report from the same machine that archived it.
Reason:
During XMS initialization CA View provides information on the databases in use. The Dbase-name indicates the database name. The 'action' field shows ADDED or RESET. The 'id' field indicates the relative database # in the EBCXMCTR table for XMS. The 'status' field shows AVAILABLE or SUSPENDED.
Action:
None. This message is informational.
Reason:
During XMS initialization, CA View clears the use counts and allocation flag bit for each table listed in the EBCXMCTR table. The EBCDBL02 message is displayed after this process is completed.
Action:
None. This message is informational.
Reason:
A CA View program has terminated, and a dump was generated. In this message blk specifies the control block CA View expected but did not receive (usually IFB, SFB, XFB, or DBB). It is suffixed with a number indicating which test point in the program detected the problem.
Action:
Send the dump to CA Technical Support. Restart the program that was terminated. If the problem recurs, run SARDBASE VERIFY on the database. For assistance, contact Technical Support at http://ca.com/support.
Reason:
The EBCDRV00 message is informational and displays both the parameters in the SYSIN dataset and in the execute statement PARM Field.
Action:
None
Reason:
The operator communication subtask has attached and is ready to accept operator commands. This message has a MSGLVL of NORM.
Action:
None.
Reason:
The cross-memory login subtask has attached and is ready to except cross-memory logon requests. This message has a MSGLVL of NORM.
Action:
None.
Reason:
The VTAM login subtask has attached to open the VTAM ACB and attach VTAM exits. This message has a MSGLVL of NORM.
Action:
Correct the input parameters, and then restart the region.
Reason:
Initialization has detected incompatible input parameters. These parameters cannot be used together. For example, LGNFMT= cannot be specified when SARVTDB= is used because LGNFMT= specifies the FORMAT of the VTAM logon data. And SARVTDB= indicates that the specific qualifier replaces the logon data. You cannot do both at the same time.
Action:
Correct the input parameters, and then restart the region.
Reason:
Initialization has detected that an input parameter requires a missing input parameter. For instance SARAPPL= must be specified when SARVTDB= is used. SARAPPL= specifies that the VTAM interface is used, and SARVTDB= is only valid when VTAM is initialized.
Action:
Correct the input parameters, and then restart the region.
Reason:
Initialization has detected that an input parameter that specifies the VTAM logon processing occurs, but none of the VTAM interfaces (SARAPPL=, RMOAPPL= INBAPPL=) were specified.
Action:
Correct the input parameters, and then restart the region.
Reason:
Initialization has detected that an input parameter that specifies how a VTAM logon processing occurs, but none of the VTAM interfaces (SARAPPL=, RMOAPPL= INBAPPL=) were specified.
Action:
Correct the input parameters, and then restart the region.
Reason:
Initialization has detected that an input parameter that specifies how a VTAM logon processing occurs, but none of the VTAM interfaces (SARAPPL=, RMOAPPL= INBAPPL=) were specified.
Action:
Correct the input parameters, and then restart the region.
Reason:
EBCDRV06, EBCDRV07, EBCDRV08 was issued previously. This message indicates that SARAPPL=, RMOAPPL=, or INBAPPL= can be used to initialize the VTAM interface.
Action:
Correct the input parameters, and then restart the region.
Reason:
The displayed PC call routine has been loaded into the CSA at the address shown. The release, assembly date, and time are also shown. This message has a MSGLVL of INFO.
Action:
None.
Reason:
The PC call function is now available to allow cross-memory communication to take place. The EC1XMSGN routine must start before cross‑memory login can process. This message has a MSGLVL of NORM.
Action:
None.
Reason:
Initialization has detected that an input parameter that requires a missing input parameter. For instance SARAPPL= must be specified when SARVTDB= is used. This is because SARAPPL= specifies that the VTAM interface is used, and SARVTDB= is only valid when VTAM is initialized.
Action:
Correct the input parameters; then restart the region.
Reason:
The operator communication subtask has detached and is no longer available. If any login subtasks are still attached, they are forced off and the region finishes terminating. This message has a MSGLVL of CRIT.
Action:
None.
Reason:
The cross-memory login subtask has detached and is no longer available. This message has a MSGLVL of CRIT.
Action:
None.
Reason:
The VTAM login subtask has detached and is no longer available. This message has a MSGLVL of CRIT.
Action:
None.
Reason:
The SYSPRINT writer subtask has stopped. This normally occurs when the region is shut down. It also occurs when the SYSPRINT log writer did not find a SYSPRINT DDCARD or the SYSPRINT log writer has abended for some reason.
Action:
If the SYSLOG writer abended. For assistance, contact Technical Support at http://ca.com/support; otherwise, no action must be taken.
Reason:
The operator subtask terminated and this subtask was still active. CA View has forced the subtask to shut down. This message has a MSGLVL of CRIT.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The SYSPRINT message queue was allocated in storage.
Action:
None.
Reason:
This message is issued when the cross-memory region started. The size and location of the pool of user control blocks that are received at the system startup are displayed. This message has a MSGLVL of NORM.
Action:
The USERMAX initialization parameter sets the maximum number of user control blocks to allocate in the region. To increase the USERMAX initialization parameter, shut down and restart the region.
Reason:
The cross-memory region is terminating, but some subtasks are still active.
Action:
Wait for all subtasks to end.
EBCDRV99 text for invalid startup parameter
Reason:
The OVERRIDE parameter is not valid in the SYSIN data set, or if coded in the execute statement PARM field, cannot contain sub parameter values.
The input parameter that is shown is unknown or invalid. The region abends. This message has a MSGLVL of CRIT.
Action:
Remove the OVERRIDE parameter from the SYSIN dataset or remove the sub parameter from the OVERRIDE parameter coded in the execute statement PARM field. Correct the invalid parameter and restart the task.
Reason:
This message is issued when the EBCERRWL task is initialized.
Action:
It is an informational message, no action is required.
Reason:
This message is issued when the EBCERRWL task terminates.
Action:
It is an informational message, no action is required.
Reason:
The logon request queue has been damaged. XMS stops accepting logons. This is accompanied with a U0005 abend.
Action:
Save the dump that is associated with this message. For assistance, contact Technical Support at http://ca.com/support.
Reason:
A CA View program has terminated, and a dump was generated. In this message, blk specifies the control block that CA View expected but did not receive (usually IFB, SFB, XFB, or DBB). It is suffixed with a number indicating which test point in the program detected the problem.
Action:
Send the dump to CA Technical Support. Restart the program that terminated. If the problem recurs, run SARDBASE VERIFY on the database. For assistance, contact Technical Support at http://ca.com/support.
Reason:
The CLOSE operator command is attempting to close the VTAM interface ACB. The possible programs are SARVTAM, INBVTAM, and RMOVTAM. This message has a MSGLVL of OPER.
Action:
The text indicates whether there was an error. For assistance, contact Technical Support at http://ca.com/support.
Reason:
The CLOSE operator command has been issued, but the VTAM interface ACB is not open. The possible programs are INBVTAM and RMOVTAM. This message has a MSGLVL of OPER.
Action:
Verify that the specified ACB is open.
Reason:
The operator command operand must be either YES or NO. This message has a MSGLVL of OPER.
Action:
Reissue the command with a valid operand.
Reason:
The operator command operand must not specify more than one value. This message has a MSGLVL of OPER.
Action:
Reissue the command with a valid operand.
Reason:
The operator command operand is limited to 10 values. This message has a MSGLVL of OPER.
Action:
Reissue the command with a valid operand.
Reason:
The operator command operand must be a number. This message has a MSGLVL of OPER.
Action:
Reissue the command with a valid operand.
Reason:
The operator command operand cannot be assigned a value. This message has a MSGLVL of OPER.
Action:
Reissue the command with a valid operand.
Reason:
The operator command could not locate this user on the system. This message has a MSGLVL of OPER.
Action:
Reissue the command with a valid connect ID of the user.
Reason:
The displayed operator command was entered. This command processes now. This message has a MSGLVL of OPER.
Action:
None.
Reason:
The displayed operator command is not valid for cross-memory. This message has a MSGLVL of OPER.
Action:
Reenter a valid cross-memory operator command.
Reason:
The operator command operand is not valid. This message has a MSGLVL of OPER.
Action:
Reenter the cross-memory operator command with a valid operand.
Reason:
The operand is not valid for this operator command. This message has a MSGLVL of OPER.
Action:
Reissue the command with a valid operand.
Reason:
The operator command operand did not specify a value. This message has a MSGLVL of OPER.
Action:
Reissue the command with a value.
Reason:
The operator command operand must end with a quote mark if it begins with a quote mark. This message has a MSGLVL of OPER.
Action:
Reissue the command with balanced quote marks.
Reason:
The operator command operand must not specify a character string. This message has a MSGLVL of OPER.
Action:
Reissue the command with a valid operand.
Reason:
The operator command operand must not be more than n characters. This message has a MSGLVL of OPER.
Action:
Reissue the command with a valid operand length.
Reason:
There was an internal error in the operator routine. This message has a MSGLVL of OPER.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The CANCEL command has abended the requested user subtask. This message has a MSGLVL of OPER.
Action:
None.
Reason:
The CANCEL command did not indicate which user to cancel. This message has a MSGLVL of OPER.
Action:
Reissue the CANCEL command with a user connect ID.
Reason:
The CANCEL command did not find any users in this region. This message has a MSGLVL of OPER.
Action:
None.
Reason:
The CANCEL command had an internal error. This message has a MSGLVL of OPER.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
A LIST STATUS,ALL command was entered.
The meaning of the items displayed:
Action:
This message is informational.
Reason:
A LIST USERS,ALL command was entered.
The meaning of the items displayed:
These fields are followed by two unnamed fields:
The high water mark displayed in EBCOLS10 is greater than the high water mark displayed in EBCOLST2. This is because inactive entries that are displayed in EBCOLS11 are not candidates for immediate reuse. This can cause a new logon to use a new entry rather than reusing an old entry.
Action:
This message is informational.
Reason:
The operator list command is processing a LIST USER,ALL and found a pending login queue with active control blocks.
Action:
None.
Reason:
The operator list command is processing a LIST S,TABLE. The message displays the contents of the EC1XMCTR table that is in use.
Action:
None.
Reason:
A LIST USERS, ALL command was entered. The meaning of the items displayed:
These fields are followed by two unnamed fields:
Action:
This message is informational.
Reason:
A LIST STATUS,ALL command was entered.
The meaning of the items displayed:
Action:
This message is informational.
Reason:
The LIST command did not indicate what users to list. This message has a MSGLVL of OPER.
Action:
Reissue the command, specifying user connect-IDs.
Reason:
The operands that are specified with the STATUS LIST command are not valid STATUS operands. This message has a MSGLVL of OPER.
Action:
Reissue the command with valid operands.
Reason:
The LIST command did not find any users in this region. This message has a MSGLVL of OPER.
Action:
None.
Reason:
The LIST command had an internal error. This message has a MSGLVL of OPER.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The LIST command had an internal error. This message has a MSGLVL of OPER.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The LIST command had an internal error. This message has a MSGLVL of OPER.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
This is the LIST command display of database status.
Action:
None.
Reason:
This is the LIST command display of XMSSUB task status.
Action:
None.
Reason:
The CHANGE command has altered the USERMAX parameter. This message has a MSGLVL of OPER.
Action:
None.
Reason:
The CHANGE command has altered the LONGWAIT parameter. This message has a MSGLVL of OPER.
Action:
None.
Reason:
The CHANGE command has altered the CANCEL parameter. This message has a MSGLVL of OPER.
Action:
None.
Reason:
The CHANGE command has altered the VTAMPASS parameter. This message has a MSGLVL of OPER.
Action:
None.
Reason:
The CHANGE command has altered the USERMAX parameter. This message has a MSGLVL of OPER.
Action:
None.
Reason:
The CHANGE command had an internal error. This message has a MSGLVL of OPER.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The CHANGE command has found a value not in range. This message has a MSGLVL of OPER.
Action:
Reissue the command with a valid operand.
Reason:
The OPEN command attempted to open the SARVTAM ACB, the text indicates whether the request was successful. This message has a MSGLVL of OPER.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The OPEN command has attempted to open the SARVTAM ACB, the message indicates if the request was successful or not. This message has a MSGLVL of OPER.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The operator routine is loaded at the address indicated. This message has a MSGLVL of INFO.
Action:
None.
Reason:
The operator routine was entered and there was no MODIFY or STOP command to process. This message has a MSGLVL of CRIT.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The OPEN command has attempted to open the SARVTAM ACB, the message indicates whether the request was successful. This message has a MSGLVL of CRIT.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The QUIESCE command has attempted to QUIESCE the SARVTAM ACB, the message indicates whether the request was successful. This message has a MSGLVL of OPER.
Action:
Your action depends on the actual message. Correct and reissue the command if the request was not successful.
Reason:
The QUIESCE command has attempted to QUIESCE the SARVTAM ACB, the message indicates whether the request was successful. This message has a MSGLVL of OPER.
Action:
Your action depends on the actual message. Correct and reissue the command if the request was not successful.
Reason:
The QUIESCE command has attempted to QUIESCE the RMOVTAM ACB, the message indicates whether the request was successful. This message has a MSGLVL of OPER.
Action:
Your action depends on the actual message. Correct and reissue the command if the request was not successful.
Reason:
The RESUME command has attempted to RESUME the SARVTAM ACB, the message indicates whether the request was successful. This message has a MSGLVL of OPER.
Action:
Your action depends on the actual message. Correct and reissue the command if the request was not successful.
Reason:
The RESUME command has attempted to RESUME the SARVTAM ACB, the message indicates whether the request was successful. This message has a MSGLVL of OPER.
Action:
Your action depends on the actual message. Correct and reissue the command if the request was not successful.
Reason:
The RESUME command has attempted to RESUME the RMOVTAM ACB, the message indicates whether the request was successful. This message has a MSGLVL of OPER.
Action:
Your action depends on the actual message. Correct and reissue the command if the request was not successful.
Reason:
The SUSPEND command has attempted to SUSPEND the SARVTAM ACB, the message indicates whether the request was successful. This message has a MSGLVL of OPER.
Action:
Your action depends on the actual message. Correct and reissue the command if the request was not successful.
Reason:
The SUSPEND command has attempted to SUSPEND the SARVTAM ACB, the message indicates whether the request was successful. This message has a MSGLVL of OPER.
Action:
Your action depends on the actual message. Correct and reissue the command if the request was not successful.
Reason:
The SUSPEND command has attempted to SUSPEND the RMOVTAM ACB, the message indicates if the request was successful or not. This message has a MSGLVL of OPER.
Action:
Your action depends on the actual message. Correct and reissue the command if the request was not successful.
Reason:
The SHUTDOWN command has attempted to SHUTDOWN the SARVTAM ACB, the message indicates whether the request was successful. This message has a MSGLVL of OPER.
Action:
Your action depends on the actual message. Correct and reissue the command if the request was not successful.
Reason:
The SHUTDOWN command has attempted to SHUTDOWN the SARVTAM ACB, the message indicates whether the request was successful. This message has a MSGLVL of OPER.
Action:
Your action depends on the actual message. Correct and reissue the command if the request was not successful.
Reason:
The SHUTDOWN command has attempted to SHUTDOWN the RMOVTAM ACB, the text indicates whether the request was successful or not. This message has a MSGLVL of OPER.
Action:
Your action depends on the actual message. Correct and reissue the command if the request was not successful.
Reason:
A CA View program has terminated, and a dump was generated. In this message, blk specifies the control block that CA View expected but did not receive (usually IFB, SFB, XFB, or DBB). It could be suffixed with a number indicating which test point in the program detected the problem.
Action:
Send the dump to CA Technical Support. Restart whatever program was terminated. If the problem recurs, run SARDBASE VERIFY on the database. For assistance, contact Technical Support at http://ca.com/support.
Reason:
A CA View program has terminated, and a dump was generated. In this message, blk specifies the control block that CA View expected but did not receive (usually IFB, SFB, XFB, or DBB). It could be suffixed with a number indicating which test point in the program detected the problem.
Action:
Send the dump to CA Technical Support. Restart whatever program was terminated. If the problem recurs, run SARDBASE VERIFY on the database. For assistance, contact Technical Support at http://ca.com/support.
Reason:
You are not using MVS/XA or MVS/ESA. EC1XMCIC requires MVS/XA or MVS/ESA to work.
Action:
Use MVS/XA or MVS/ESA, and then try again.
Reason:
The DFHPPT or RDO definition for the EC1XMCIC program is wrong. The comment indicates what specifically is found to be in error. You are possibly not using Version 4.1 or a later version of CICS. EC1XMCIC requires Version 4.1 or a later version of CICS to work.
Action:
Correct the EC1XMCIC definition.
Reason:
The EC1XSTSK program is not executing. EC1XMCIC requires the EC1XSTSK to work. EC1XMCIC ends. EC1CINIT, which starts the subtask, was not executing, or the subtask was stopped.
Action:
See your operations administrator for more information.
Reason:
An internal error occurred in EC1XMCIC.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
EC1XMCIC is designed to execute attached to a terminal. EC1XMCIC ends.
Action:
Execute EC1XMCIC from a terminal.
Reason:
An internal error occurred in EC1XMCIC.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in EC1XMCIC.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in EC1XMCIC.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
EC1XMCIC cannot find the EC1CICUX program. EC1XMCIC requires the EC1CICUX to work. EC1XMCIC ends.
Action:
Define EC1CICUX for CICS RDO (Resource Definition Online), and then try again.
Reason:
An internal error occurred in EC1XMCIC.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
A CICS transaction has timed out and the session in EC1XMCIC is ended. The first message is the normal message issued. The second message is issued when XMC11= is specified on the EBCXMOPT MACRO where XXXX is the XMC11= value.
Action:
Restart the transaction.
Reason:
An internal error occurred in EC1XMCIC.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in EC1XMCIC.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
Parameter data larger than 102 bytes is passed to EC1XMCIC.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
EC1XMCIC timed out waiting for the cross-memory region to respond.
Action:
If this condition occurs frequently, extend the parameter TIMEOUT in the EC1XMCTR table, if possible.
Reason:
EC1XMCIC found that EC1XSTSK is shut down. EC1XMCIC ends. EC1CINIT, which starts the subtask, was not executing, or the subtask was stopped or failed.
Action:
For more information, see your operations administrator.
Reason:
Cross-memory region terminated the session because the XMS session exceeded the value of LONGWAIT in the cross-memory region.
Action:
If this condition occurs frequently, increase the value of LONGWAIT in the cross-memory region start-up file.
Reason:
EC1XMCIC found that the cross-memory region was terminated. EC1XMCIC ends.
Action:
Start the cross-memory region, and then try again.
Reason:
The maximum number of users, which are specified by the USERMAX parameter of the EC1XMCTR macro EBCXMOPT has been reached, and no more sessions are allowed.
Action:
Make sure that CICS performance monitor software, such as TMON or Omegamon, is not configured to purge CA View CICS transactions. AKC3 abend messages in the CICS log are an indication that a transaction has been purged. This abend must never occur for a View transaction and issue the EBCXMC19 message. Otherwise, try to log on later or increase the USERMAX value and restart CICS region.
Reason:
The maximum number of logons, which is specified in the EC1XMCTR macro EBCXMOPT, has been reached.
Action:
Try to log on later, or increase the value and restart the CICS region.
Reason:
Informational message indicating that a transaction is starting.
Action:
None. This message is provided for reference only.
Reason:
Informational message indicating transaction input.
Action:
None. This message is provided for reference only.
Reason:
The EC1XMCIC application program has abended.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
Informational message indicating control has returned to CICS for a transaction and waits for further input.
Action:
None. This message is provided for reference only.
Reason:
Informational message indicating control has returned to CICS after a transaction has ended.
Action:
None. This message is provided for reference only.
Reason:
The previous operation is successfully completed.
Action:
None. This message is provided for reference only.
Reason:
An internal error occurred in the cross-memory region.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
Your session has been lost. This condition occurs when the time specified for LONGWAIT is exceeded in the cross-memory region, the cross-memory region is shut down or abnormally ends, or an operator cancels your session.
Action:
Restart your session.
Reason:
You have ended your session, and the cross-memory session is completed without errors.
Action:
None. This message is provided for reference only.
Reason:
Your session was terminated. The cross-memory session failed.
Action:
Check the job log of the cross-memory region. Restart your session.
Reason:
All cross-memory regions are at the maximum user limit.
Action:
To enable more users start more cross-memory regions.
Reason:
Someone suspended the cross-memory region.
Action:
Review the cross-memory log to identify who suspended the region. Have that person release the cross-memory region.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The cross-memory region is being terminated and logons are no longer accepted.
Action:
Review the cross-memory log to identify who terminated the cross‑memory region. Start the cross-memory region.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The cross-memory region has not finished initializing.
Action:
Wait for cross-memory to finish initializing, and then retry your request.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The last request exceeded the time-out value in the EC1XMCTR table entry for this transaction.
Action:
If too many of these failures occur, review and extend the TIMEOUT parameter.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The connect identifier you that specified is already in use.
Action:
Ensure that ExxCICUX is generating a unique connect identifier for each user.
Reason:
To log in, an XMS region must be active.
Action:
Start an XMS region, and then try to log on again.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
A request to log in XMSSUB has been received.
Action:
None, the logon is being processed.
Reason:
An input request has been received from the terminal.
Action:
None, the request is being processed.
Reason:
The EC1XSTSK program is not executing. XMSSUB=YES is required in the cross-memory address space, or the cross-memory region is not active.
Action:
Verify that XMSSUB=YES, and that the cross-memory region is active.
Reason:
An internal error occurred in EC1XMCIC.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The terminal type is invalid.
Action:
Verify that the terminal type is 3270, or a PC emulator.
Reason:
An internal error occurred.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The specified user connection exit was not found.
Action:
Place the user exit in the LOADLIB.
Reason:
An internal error occurred in EC1XMCIC.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
EC1XMCIC cannot find the user connection to continue the session. EC1XMCIC ends.
Action:
Restart the transaction.
Reason:
An internal error occurred in EC1XMCIC.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in EC1XMCIC.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
Parameter data larger than 102 bytes is passed to EC1XMCIC.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
A time-out occurred waiting for the cross-memory region to respond.
Action:
If this condition occurs frequently, increase the parameter TIMEOUT in the EC1XMCTR table, if appropriate.
Reason:
EC1XMCIC found that EC1XSTSK is shut down. EC1XMCIC ends. EC1CINIT, which starts the subtask was not executing, or was stopped or failed.
Action:
For more information, see your operations administrator.
Reason:
Cross-memory terminated the session because the XMS session exceeded the value of LONGWAIT in the cross-memory region.
Action:
If this condition occurs frequently, increase the value of LONGWAIT in the cross-memory startup file.
Reason:
EC1XMCIC found that the cross-memory region was terminated. EC1XMCIC ends.
Action:
Start the cross-memory region, and then try again.
Reason:
The region control block was invalid, or at the incorrect release level for this user connection.
Action:
Check the status of the cross-memory regions, they could have terminated.
Reason:
Active cross-memory region was not available.
Action:
Start up a cross-memory region. It must have the default SUBSYS= value, and must specify XMSSUB=YES. For details, see the Installation Guide.
Reason:
The USERMAX value was exceeded.
Action:
If possible, increase the parameter value.
Reason:
No cross-memory region with the default SUBSYS= value has been started.
Action:
Start up a cross-memory region with the default SUBSYS= value.
Reason:
No cross-memory region with XMSSUB=YES value is active.
Action:
Start up a cross-memory region with XMSSUB=YES.
Reason:
A cross-memory region with XMSSUB=YES has terminated, or the subtask has failed.
Action:
Start up a cross-memory region with XMSSUB=YES.
Reason:
The application interface must be in 31-bit mode.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The application interface must be in 31-bit mode.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
All user logon blocks are in use. The system has problems logging on a user and all the logon blocks are full. Try again later.
Action:
None.
Reason:
The cross-memory region failed.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error has occurred.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The operand of the IMS/DC transaction does not specify a valid terminal type.
Action:
Reenter the transaction with a proper operand.
Reason:
The operand of the IMS/DC transaction does not specify a valid terminal option.
Action:
Reenter the transaction with a proper operand.
Reason:
An unexpected return code from IMS/DC was received.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The EC1XMTSO program has checked and found that one or more required programs cannot be loaded from the STEPLIB. The EBCXMT44 message displays indicating the missing programs that must be available.
Action:
Copy the required programs to the STEPLIB, then restart the initialization process.
Reason:
A nonzero return code from the user connection exit was received.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The indicated IMS/DC function call failed with IMSIO_STAT set to the given return code. Check the appropriate IMS guide for function and return code meanings.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The EC1XMTSO program has checked and found one or more required programs that cannot be loaded from the STEPLIB.
Action:
Copy the required programs to the STEPLIB, then restart the initialization process.
Reason:
This error message is displayed for debugging purposes.
In this message, #, 1st, size, free, xsctl, xsuser, and pcsgpr represent additional parameter values that are provided for further reference.
Action:
None. This message is informational.
Reason:
EC1XSTSK abnormally ended. In this message, n represents an additional parameter value that is provided for further reference.
Action:
None. EC1XSTSK attempts to restart itself automatically.
Reason:
EC1XSTSK abnormally ended. In this message, #A, #B, #C, #D, and #E represent additional parameter values that are provided for further reference.
Action:
None. EC1XSTSK attempts to restart itself automatically.
Reason:
EC1XSTSK abnormally ended. In this message, #A, #B, #C, and #D represent additional parameter values that are provided for further reference.
Action:
None. EC1XSTSK attempts to restart itself automatically.
Reason:
This error message is displayed for debugging purposes.
In this message, # represents an actual address. M, D, and Y represent the month, day, and year, respectively. H and M represent the hour and minutes.
Action:
None. This message is provided for reference only.
Reason:
The user is being logged on to the cross-memory address space.
Action:
None.
Reason:
The user has timed out; the session undergoes clean-up processing.
Action:
None.
Reason:
The EC1XSOPR (CICS operator subtask) has been attached to provide the CICS OPERATOR interface.
Action:
None.
Reason:
The EC1XSOPR (CICS operator subtask) has been detached. This normally occurs only when the subtask is shutting down.
Action:
None.
Reason:
The EC1XSOPR (CICS operator subtask) has failed to stop. This operator subtask previously failed.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
You tried to log in to a subsystem on which a cross-memory region is not initialized and active. In this message, name represents the name that is assigned to the subsystem.
Action:
Initialize a cross-memory region on the subsystem, and then try to log on again.
Reason:
Not enough memory is allocated to cross-memory, or the USERMAX parameter is set too high.
Action:
Allocate more memory to cross-memory and reduce the number of users that are assigned to the USERMAX parameter.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The connection identifier that is modified by the EC1CICUX user exit is incorrect or invalid.
Action:
Verify that the connection identifier that is modified by the EC1CICUX user exit is valid.
Reason:
Your session ended with no errors.
Action:
None. This message is provided for reference only.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
Your EC1XMCTR table contains zero entries.
Action:
Rebuild the EC1XMCTR table with at least one transaction definition.
Reason:
An internal error occurred in cross-memory.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The cross-memory region is terminated.
Action:
None. This message is provided for reference only.
Reason:
The entry for this transaction does not have a valid database name.
Action:
Check the entry for the transaction to ensure that the database name is correct. Correct the database name if necessary, and then try again. For assistance, contact Technical Support at http://ca.com/support.
Reason:
The cross-memory session that you are trying to initiate exceeds the maximum number allowed in the EC1MCTR table. You cannot initiate new sessions.
Action:
Terminate cross-memory sessions, and then try again.
Reason:
The EC1XMCTR table does not contain the database index name that you specified, and so you are denied access to the table.
Action:
Add an entry to the EC1XMCTR table for the database you want to specify.
Reason:
EC1XMCTR is assembled with the SARXMTRN macro from a previous release of a CA product.
Action:
Assemble the table again with the current macro library.
Reason:
An error occurred in cross-memory.
Action:
Review the error message that is displayed after this error message for more information about the cause. Review the contents of the second error message and act accordingly.
Reason:
An error occurred in cross-memory.
Action:
Review the error message that is displayed after this error message for more information about the cause. Review the contents of the second error message and act accordingly.
Reason:
An error occurred in cross-memory.
Action:
Review the error message that is displayed after this error message for more information about the cause. Review the contents of the second error message and act accordingly.
Reason:
An error occurred in cross-memory.
Action:
Review the error message that is displayed after this error message for more information about the cause. Review the contents of the second error message and act accordingly.
Reason:
An error occurred in cross-memory.
Action:
Review the error message that is displayed after this error message for more information about the cause. Review the contents of the second error message and act accordingly.
Reason:
An error occurred in cross-memory.
Action:
Review the error message that is displayed after this error message for more information about the cause. Review the contents of the second error message and act accordingly.
Reason:
This error message is a trace message to the indicated logic flow. In this message, #A and #B represent parameter values that are provided for further reference.
Note: This message appears only if trace messages are requested.
Action:
None. This message is provided for reference only.
|
Copyright © 2013 CA.
All rights reserved.
|
|