Reason:
Code Coverage is in use by another task attached to the "From" terminal. Due to this fact, the Counts Table is in use and cannot be removed.
Action:
No action can be taken until the other task ceases use of the Counts Table.
Reason:
The PREV or ADV command was specified but the Statement Trace facility is not active.
Action:
Specify the TRACE command to activate the Statement Trace facility.
Reason:
The PREV command was specified but the Statement Trace Table is already positioned at the first entry OR the ADV command was specified but the Statement Trace Table is already positioned at the last entry.
Action:
None.
Reason:
An internal error occurred while retrieving past data values for the DATAMON option.
Action:
Call CA technical support.
Reason:
There are no current channels active.
Action:
No action can be taken.
Reason:
A non‑authorized condition was detected.
Action:
Check the condition.
Reason:
The CA InterTest for CICS release that you are running is not compatible with the release of CICS that is running.
Action:
Install the correct release of CA InterTest for CICS.
Reason:
CA InterTest for CICS could not find a map in the PPT, or the PPT entry is disabled.
Action:
Check to see it the PPT entry is present, and ensure that it is enabled.
Reason:
A BMS abend has been intercepted by CA InterTest for CICS. The abend code appears as (*).
Action:
Check the BMS map and the requested input.
Reason:
Informational message.
Action:
None.
Reason:
The map is too large for display on terminal code=(*).
Action:
None.
Reason:
The request you made is invalid.
Action:
Correct your request and resubmit.
Reason:
An I/O error occurred while you were trying to access temporary storage.
Action:
Correct the temporary storage I/O error, and retry the transaction.
Reason:
The CORE=MAP command received an IGREQCD condition when sending the map to an LUTYPE4 logical unit.
Action:
Determine the reason that the terminal could not receive the map, and resubmit the request.
Reason:
An IGREQCD condition was received during a send map request.
Action:
Ensure that your LUTYPE4 Terminal is defined correctly in CICS.
Reason:
An I/O error was detected while loading a BMS map.
Action:
None.
Reason:
The CORE=MAP command was entered for an entry that is not defined as a map to CICS.
Action:
Correct the program definition, and resubmit the request.
Reason:
An internal logic error has occurred.
Action:
Contact CA technical support.
Reason:
The option or command entered is not valid for this function.
Action:
Correct the option or command and resubmit.
Reason:
The transaction specified has ended.
Action:
None.
Reason:
There was a processing error in the specified transaction.
Action:
If a dump was taken, contact CA technical support. Review the commands and processing for completeness. Resubmit if necessary.
Reason:
No entries were found to match the selection criteria specified.
Action:
Correct the selection criteria and resubmit.
Reason:
There was not enough storage available to complete the request.
Action:
Contact your systems programmer for assistance.
Reason:
The requested entry could not be found.
Action:
Verify and correct the selection criteria and resubmit.
Reason:
The requested file is not available because it is either unenabled or disabled.
Action:
Make the file enabled and try again.
Reason:
The file needs to be open to complete the request.
Action:
Open the file and try again.
Reason:
A character other than "S" was used to make a selection.
Action:
Use "S" to make the selection and resubmit.
Reason:
The command entered is currently inactive in this release of the product.
Action:
None.
Reason:
There was a problem reading the file.
Action:
Contact your systems programmer for assistance.
Reason:
One of the parameters required by this command was either invalid or missing.
Action:
Check the command syntax, correct, and try again.
Reason:
A value other than a valid scroll amount was specified.
Action:
Review the valid scroll values listed above and try again.
Reason:
The requested selection is invalid.
Action:
Choose a valid selection and try again.
Reason:
The selection character used is invalid for this function.
Action:
Review the valid selection characters and try again.
Reason:
A required input data field is missing
Action:
Fill in the highlighted field and resubmit.
Reason:
The data entered is not valid or a program, transaction, or terminal was specified that is not defined to the CICS region.
Action:
Correct the data and try again.
Reason:
This option is not valid for generic programs, .ALL, or .OPTIONS.
Action:
Specify a specific program and try again.
Reason:
This option is only available for COBOL and PL/I programs.
Action:
Check the program name and language and try again.
Reason:
The selected entry does not allow use of the requested function.
Action:
Verify the entry and request and try again.
Reason:
The option requested is restricted from use.
Action:
Either do not use this option, or obtain security access to the option from your systems programmer.
Reason:
The value specified is outside the range of valid values.
Action:
Correct the value and try again.
Reason:
The requested option is not installed at this site.
Action:
Contact your systems programmer for assistance.
Reason:
The requested action is not available during breakpoint processing or while in dump analysis.
Action:
Try again the request when not at a breakpoint or in dump analysis.
Reason:
The requested record was successfully added.
Action:
None.
Reason:
The requested record already exists on the file; therefore, it cannot be added.
Action:
None.
Reason:
The requested record was successfully updated.
Action:
None.
Reason:
The requested record was successfully deleted.
Action:
None.
Reason:
The requested record was not found on the file; therefore, it cannot be displayed.
Action:
None.
Reason:
The requested record could not be added. Use the information in the EIBRESP and EIBRESP2 to determine the problem.
Action:
Correct the problem and retry.
Reason:
The requested record could not be updated. Use the information in the EIBRESP and EIBRESP2 to determine the problem.
Action:
Correct the problem and retry.
Reason:
The requested record could not be deleted. Use the information in the EIBRESP and EIBRESP2 to determine the problem.
Action:
Correct the problem and retry.
Reason:
The file needed for this activity was not found.
Action:
Contact your systems programmer.
Reason:
The file needed for this activity was not authorized.
Action:
Contact your systems programmer.
Reason:
You have elected to browse files but have entered a file name that contains more than 8 characters.
Action:
Check the file name and shorten it to be less than or equal to 8 characters.
Reason:
You have elected to browse transient data queues but have entered a TDQueue name that contains more than 4 characters.
Action:
Check the TDQueue name and shorten it to be less than or equal to 4 characters.
Reason:
The leading and trailing crumple zones of the indicated storage do not match.
Action:
This is the result of a storage violation. Check the application responsible for the storage for references for possible access beyond the end of the storage area. It may also be necessary to check applications for use of storage areas that have been FREEd.
Reason:
Data displays in Structure Display Format.
Action:
None.
Reason:
A duplicate subroutine has been declared for monitoring. The LIST facility or transaction must be used to set/remove options on a duplicate subroutine. The COMPOSITE command must be used in the LIST facility to declare the subprogram's owning load module.
Action:
Use the COMPOSITE command in the LIST facility.
Reason:
The task was abended by CA InterTest for CICS.
Action:
None.
Reason:
The task was abended by CA InterTest for CICS.
Action:
None.
Reason:
The terminal is released from the control of CA InterTest.
Action:
None.
Reason:
The monitored program has encountered an automatic breakpoint.
Action:
You can use the CA InterTest for CICS Help facility to determine the cause of the error and to correct it.
Reason:
The monitored program has encountered an unconditional breakpoint.
Action:
Use the CA InterTest for CICS Help facility to find out more about breakpoints.
Reason:
The monitored program has encountered a conditional breakpoint.
Action:
Use the CA InterTest for CICS Help facility to find out more about breakpoints.
Reason:
The monitored program has encountered a single‑step breakpoint.
Action:
Use the CA InterTest for CICS Help facility to find out more about breakpoints.
Reason:
The monitored program has encountered an auto‑step breakpoint.
Action:
Use the CA InterTest for CICS Help facility to find out more about breakpoints.
Reason:
The monitored program issued a programmed breakpoint.
Action:
Use the CA InterTest for CICS Help facility to find out more about breakpoints.
Reason:
The monitored program has encountered a request breakpoint.
Action:
Use the CA InterTest for CICS Help facility to find out more about breakpoints.
Reason:
You cannot continue from a breakpoint unless you are on the terminal that received the original breakpoint.
Action:
Log in to the terminal that received the previous breakpoint, and continue your test session.
Reason:
Informational message.
Action:
None.
Reason:
Informational message.
Action:
Press Clear.
Reason:
A non‑CA InterTest for CICS transaction was requested from a detailed breakpoint screen. Only CA InterTest for CICS transactions are allowed.
Action:
Press Clear, and specify a CA InterTest for CICS transaction.
Reason:
Your request to abend the task at a breakpoint may leave work started in remote CICS regions pending.
Action:
None.
Reason:
An abend of a task at a breakpoint has been requested.
Action:
If you still wish to abend the task, press PF3. If you want to cancel the abend, press Clear.
Reason:
You have requested an abend of a breakpointed task with no dump.
Action:
If you want a dump, request the abend again, and specify an abend code other than "XXXX".
Reason:
The task that you are trying to disconnect was started without a terminal facility, and cannot be disconnected.
Action:
Press Clear.
Reason:
CEDF has been requested for this transaction.
Action:
CEDF is now activated.
Reason:
Informational
Action:
None.
Reason:
Your CNTL=DISC request has been successfully completed.
Action:
Clear your screen and continue.
Reason:
Your CNTL=DISC request has been processed. The breakpoint task is suspended at the breakpoint until you reconnect.
Action:
Clear your screen and continue.
Reason:
Your CNTL=DISC request has been processed for a remote terminal.
Action:
Press Enter to complete the disconnection, or press Clear to cancel the disconnection.
Reason:
An abend request for the breakpointed task has been requested without a dump, and Handle Abend Exits will be canceled.
Action:
None.
Reason:
There is no program entry in the CA InterTest for CICS PROTSYM file.
Action:
Ensure that the proper CA InterTest for CICS Symbolic File is specified in your CICS region.
Reason:
Informational message.
Action:
None.
Reason:
Symbolic program information was requested, but it is not in the CA InterTest for CICS Symbolic File.
Action:
Ensure that the proper CA InterTest for CICS Symbolic File is specified in your CICS region.
Reason:
The CA InterTest for CICS PLT start‑up module was executed and will issue the CA InterTest for CICS Start command.
Action:
None.
Reason:
The CA InterTest for CICS programs are not defined in your CICS region or are defined with improper security.
Action:
Ensure that CA InterTest for CICS is properly installed.
Reason:
The CA InterTest for CICS programs are not defined in your CICS region or are defined with improper security.
Action:
Ensure that CA InterTest for CICS is properly installed.
Reason:
CA InterTest for CICS could not be started during PLT initialization.
Action:
Check previous messages for additional errors that were encountered.
Reason:
The CA InterTest for CICS PLT shutdown module has executed the CA InterTest for CICS terminate command.
Action:
None.
Reason:
The CA InterTest for CICS PLT shutdown module could not load the CA InterTest for CICS program.
Action:
Ensure that CA InterTest for CICS was properly installed, or that your CICS PPT table was not corrupted.
Reason:
The CA InterTest for CICS CNTL transaction could not be started during PLT shutdown.
Action:
Ensure that CA InterTest for CICS has been installed properly.
Reason:
The CA InterTest for CICS PLT shutdown module terminated abnormally.
Action:
Review any previous messages for additional error information.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|