Reason:
Your CNTL command contains a syntax error.
Action:
Correct the command, and resubmit your request.
Reason:
The CNTL command was disregarded because of an error.
Action:
Review your command syntax and any previous error messages. Correct the command, and resubmit your request.
Reason:
Informational message.
Action:
Press Clear.
Reason:
A READ error occurred on the CA InterTest for CICS checkpoint file during a RESTART command.
Action:
Contact the person who installed CA InterTest for CICS.
Reason:
An error occurred during CNTL=RESTART.
Action:
Check your command syntax, and resubmit your request.
Reason:
CNTL=RESTART for the current date failed, because the last checkout was made on a different day.
Action:
A normal START occurs.
Reason:
CNTL=RESTART failed.
Action:
Review the errors and correct them.
Reason:
CNTL=NEW failed, because the program is in use by another task or was loaded with the HOLD option.
Action:
Check to see if other tasks are using the program. If there are none, issue CORE=DLTE=prgname and resubmit the request.
Reason:
NEW COPY failed. Refer to the accompanying messages.
Action:
None.
Reason:
The program specified in the request was either not found in the PPT or it was disabled.
Action:
Locate and determine the status of the program and resubmit the request.
Reason:
An attempt to NEW COPY a program failed, which caused the Monitoring Table entry to be removed.
Action:
See associated messages for the action to be taken.
Reason:
This is the normal CICS response when CNTL=NEW is executed for a program.
Action:
None.
Reason:
The request you made was not within the range.
Action:
Correct and resubmit you request.
Reason:
The program name specified could not be loaded.
Action:
Ensure that the program exists in the DFHRPL concatenation and in the installed program definitions.
Reason:
START failed. A normal CA InterTest for CICS START (CNTL=START) occurs. See accompanying messages.
Action:
Correct any errors.
Reason:
The CA90's License Management Program definitions do not contain a license for CA InterTest for CICS.
Action:
Ensure that you have the proper level of CA90's software installed. Contact CA technical support.
Reason:
A serious error occurred during initialization.
Action:
Review any error messages. Contact CA technical support if this is not an installation error.
Reason:
Program families have been defined.
Action:
None.
Reason:
There was no PPT entry found for the specified program, or the program's name is spelled incorrectly.
Action:
Place the program name in the PPT or correct the spelling of the program name.
Reason:
Informational message.
Action:
None.
Reason:
The family name that you specified has been successfully initialized.
Action:
None.
Reason:
CA InterTest for CICS is in the process of initializing in an ESA environment.
Action:
None.
Reason:
Informational message.
Action:
None.
Reason:
No security module was found.
Action:
CA InterTest for CICS security is disabled.
Reason:
The CA REALIA II HOST TEST option is not installed.
Action:
None.
Reason:
CA InterTest for CICS is not active at this time.
Action:
Start CA InterTest for CICS.
Reason:
The checkpoint facility is not active at this time.
Action:
You may start the checkpoint facility if you wish.
Reason:
A checkpoint could not be scheduled or canceled.
Action:
None.
Reason:
The checkpoint facility is already active.
Action:
None.
Reason:
You have requested an interval for the checkpoint facility that is below the 20‑minute minimum.
Action:
Respecify the command with a valid interval.
Reason:
Informational message.
Action:
None.
Reason:
The CA InterTest for CICS PURGE facility is not active.
Action:
Activate the PURGE facility.
Reason:
A request to stop the purge facility has failed.
Action:
None.
Reason:
The PURGE facility is already active.
Action:
None.
INTRVAL=HHMM 20 minutes or higher required.
Reason:
The interval that you specified is below the 20‑minute minimum.
Action:
Respecify the command with a valid interval.
Reason:
A request to stop the purge facility has failed.
Action:
None.
Reason:
The interval value specified is either too low or too high. The interval must be in the proper range.
Action:
Specify an appropriate value and resubmit the request.
Reason:
The PURGE command executes every time the specified time interval elapses.
Action:
None.
Reason:
This message indicates how many tasks were purged.
Action:
None.
Reason:
You have tried to exclude an item that is already in the exclusion table.
Action:
None.
Reason:
An attempt to remove an entry from the exclusion table has failed, because the entry was not found. The entry name specified in the INCL command must be an exact match to an entry that was added to the exclusion table by a previous EXCL command.
Action:
None.
Reason:
The entry specified already existed.
Action:
None.
Reason:
Informational message.
Action:
None.
Reason:
The program you specified was not found in the PPT. Your request was ignored.
Action:
None.
Reason:
You attempted to turn monitoring off for an entry that was not found.
Action:
Specify an appropriate entry and resubmit the request.
Reason:
Informational message.
Action:
None.
Reason:
A generic name was entered.
Action:
None.
Reason:
A generic name was entered, which causes CA InterTest for CICS to spend more time scanning its memory, which increases processing overhead.
Action:
None.
Reason:
Instructional message.
Action:
To process your command, press PF3. To cancel your request, press any other key.
Reason:
A generic name was entered when a fully qualified name was expected.
Action:
Specify a fully qualified name and resubmit the request.
Reason:
CA InterTest for CICS cannot be terminated while there are still active tasks at breakpoints.
Action:
Try again later.
Reason:
The system is quiescent. No new tasks will be automatically monitored.
Action:
None.
Reason:
During termination of CA InterTest for CICS, the global user exits were not properly disabled.
Action:
Refer to message CAIN4354.
Reason:
This is the reason that the global user exit enable/disable failed.
Action:
None.
Reason:
Termination of the CA Realia II Host Test option has failed. Refer to the accompanying messages.
Action:
Correct the error and resubmit the request.
Reason:
CA InterTest for CICS has been successfully terminated.
Action:
None.
Reason:
An internal logic error has occurred.
Action:
Contact CA technical support.
Reason:
See accompanying messages.
Action:
None.
Reason:
CA InterTest for CICS was not able to start.
Action:
Contact CA technical support with the code and offset.
Reason:
An internal logic error has occurred.
Action:
Contact CA technical support.
Reason:
All abends will be intercepted by CA InterTest for CICS, because the exclusion table IN25ABEN was not loaded.
Action:
None.
Reason:
The IN25ABEN Table was incorrectly assembled or link‑edited.
Action:
Correct the error and resubmit the request.
Reason:
During termination of CA InterTest for CICS, the global user exits were not successfully disabled.
Action:
None.
Reason:
This is the reason code that defines why the global user exit enable/disable failed.
Action:
None.
Reason:
Informational message.
Action:
Contact CA technical support.
Reason:
Enable of the global or task related user exit has failed.
Action:
Check the DFHRPL concatenation and the installed program definitions for modules IN25HOOK and IN25TRUE.
Reason:
The installation‑defined IN25UEXI module contains entries that are identical to the module entry code of CICS STUB modules.
Action:
Remove the entry from your IN25UEXI. Reassemble or link‑edit the module and restart CA InterTest for CICS.
Reason:
You did not link‑edit the entry correctly.
Action:
Follow the directions in the CA InterTest for CICS Installation Guide for link‑editing IN25UEXI.
Reason:
The installation defined IN25UEXI module contains entries that are identical to the module entry code of CICS STUB modules.
Action:
Remove the entry from your IN25UEXI. Reassemble or link‑edit the module and restart CA InterTest for CICS.
Reason:
Enable of CA InterTest for CICS Task related user exit has failed.
Action:
See accompanying messages for reason for the failure.
Reason:
The program IN25COBI is required for dynamic call monitoring but is currently unavailable.
Action:
Contact your systems programmer for assistance.
Reason:
The task number specified is invalid.
Action:
Correct the task number and resubmit.
Reason:
The program IN25IBMC is required for dynamic call monitoring but is currently unavailable.
Action:
Contact your systems programmer for assistance.
Reason:
CICSPlex communication failed with the reason indicated.
Action:
Contact your systems programmer.
Reason:
This message appears with other messages detailing the reason the transaction failed.
Action:
Contact your systems programmer.
Reason:
This message is produced in conjunction with another message. This message shows the contents of the above fields.
Action:
Contact your systems programmer.
Reason:
This message appears in conjunction with one or more other messages. Use the messages together to determine the problem.
Action:
Contact your systems programmer.
Reason:
This message appears with a second message.
Action:
None.
Reason:
This message identifies the CICSPlex family member with whom this member synchronizes its monitoring options.
Action:
None.
Reason:
CICSPlex=YES was specified, but this is the first member to start. Therefore, there are no other family members with whom to synchronize.
Action:
None.
Reason:
The CICSPlex environment has not been started, or has ended. Therefore, this CICSPlex member cannot resynchronize with other family members.
Action:
Contact your systems programmer.
Reason:
A syntax error was detected in the command.
Action:
Correct the command and resubmit it.
Reason:
The command was not processed.
Action:
None.
Reason:
The program has been successfully NEWCOPYed and all monitoring options have been reset.
Action:
None.
Reason:
The CNTL=RESTART command has been successfully completed. CA InterTest for CICS is ready for use.
Action:
None.
Reason:
A START or RESTART command was requested, but is already active.
Action:
None.
Reason:
The text specified on the CBP is longer than 254 bytes.
Action:
Shorten the text so it is less than or equal to 254 bytes and retry the command.
Reason:
The NEW COPY command could not be completed because the program is currently in use.
Action:
None.
Reason:
CNTL=NEW command cannot NEW COPY the program.
Action:
Refer to the accompanying messages to correct the error.
Reason:
The monitoring entry is in use for a task running in CICS. Future invocations of the program, transaction or terminal will not be monitored.
Action:
None.
Reason:
See accompanying messages.
Action:
Contact your system programmer.
Reason:
The command you specified has been processed successfully.
Action:
None.
Reason:
A CICS storage violation occurred. CA InterTest for CICS storage accounting control block was overlaid.
Action:
Contact CA technical support.
Reason:
The command to continue this task is incorrect or incomplete.
Action:
Restate the command correctly, and reenter it.
Reason:
Program execution continues, overriding an error detected during program monitoring.
Action:
None.
Reason:
Instructional message.
Action:
Press PF3 to proceed.
Reason:
Informational message.
Action:
None.
Reason:
A request was made to turn the TAL option off, but this option was never turned on.
Action:
The command is ignored.
Reason:
The option you entered was incorrect or could not be found.
Action:
Check the index for the proper command, and reenter it.
Reason:
The condition that you entered was disabled during a file transaction.
Action:
Check the FCT.
Reason:
A maximum of 9 items may be entered.
Action:
Enter 9 or fewer items.
Reason:
CA InterTest for CICS is not active in CICS.
Action:
Enter the following command to start CA InterTest for CICS: CNTL=INQ.
Reason:
The task you started has no breakpoints set at its location.
Action:
To check where breakpoints are set, enter the following command: CNTL=INQ.
Reason:
The function that you entered has either executed correctly or you must enter the correct command in order for the command to execute correctly.
Action:
If you entered the command incorrectly, reenter the correct command.
Reason:
Instructional message.
Action:
Press Clear to return to the original screen.
Reason:
You were trying to take CA InterTest for CICS off a program, or you were looking at an area that is outside the area in which CA InterTest for CICS is running.
Action:
On a clear screen, enter CNTL=INQ.
Reason:
Informational message. You used IN25COB2, COBOL II optimization.
Action:
None.
Reason:
You tried to set a breakpoint at a location that already contains a breakpoint.
Action:
Select another location for the breakpoint, or enter CNTL=INQ or CNTL=OFF,PROG=xxxxxxxx on a clear screen.
Reason:
Informational message. You used IN25COB2, COBOL II optimization.
Action:
None.
Reason:
CA InterTest for CICS is not active.
Action:
Press PF3 to start CA InterTest for CICS.
Reason:
The requested option is not valid with a generic program specification.
Action:
Do not use a generic specification for this option.
Reason:
An invalid keyword was entered.
Action:
Specify a valid keyword in the command and resubmit.
Reason:
CA InterTest for CICS only accepts requests to produce breakpoints with the same Relative Breakpoint.
Action:
See the CA InterTest for CICS User Guide for information on requesting breakpoints and the RBP option.
Reason:
A generic program request for UBP=All was converted to the equivalent command RBP=AllReg.
Action:
None.
Reason:
You are placing breakpoints at paragraph names, when you press PF3, more than 20 breakpoints are set in your program.
Action:
None.
Reason:
Use MON and NOM option with care.
Action:
None.
Reason:
If you continue, you may get unpredictable results or your system may break down.
Action:
None.
Reason:
Instructional message.
Action:
Press PF1 for HELP information, and press PF3 to execute.
Reason:
You have reached a system‑wide maximum of 255 MON/NOM options in your program.
Action:
Remove the MON/NOM breakpoints that are not being used, and resubmit your request.
Reason:
The offset specified plus the length exceeds the high boundary of the control block to be unprotected.
Action:
Correct the OFFSET and/or LENGTH parameter and retry.
Reason:
Informational message. If you change the terminal ID for a stopped task, you may cause a failure to occur.
Action:
Do not change the terminal ID for a stopped task.
Reason:
A CNTL=RECON command has been issued to reconnect the application program to its breakpoint on the terminal indicated by TRMB.
Action:
The breakpoint has been re‑established.
Reason:
The program is not in the Symbolic File, or the New Copy option has to be run.
Action:
Recompile the program, or run the New Copy option with the following command: CNTL=NEW,PROG=progname.
Reason:
The CNTL function you tried to use is invalid.
Action:
Refer to the CA InterTest for CICS User Guide for a list of valid CNTL functions.
Reason:
You tried to use a client‑specified terminal ID in a command that does not exist.
Action:
Enter the correct terminal ID. Enter CORE=TERM=x for a list of valid terminal IDs.
Reason:
The TO‑terminal that you specified is invalid.
Action:
Enter the correct terminal ID.
Reason:
You selected a PF key that abends the task without a dump.
Action:
Press PF3 to continue.
Reason:
If an MRO environment is being used, processing in a remote system will not complete.
Action:
Task will be abended.
Reason:
Informational message. A soft abend occurred, or you entered 'xxxx' so a dump will not take effect.
Action:
None.
Reason:
Instructional message.
Action:
Press PF3 to display the composite menu for the master program.
Reason:
Informational message. The release of CA InterTest for CICS that you are running is not compatible with the CICS release that is running.
Action:
See the CA InterTest for CICS Installation Guide. Contact CA technical support.
Reason:
The resource specified did not pass the authorization checks.
Action:
Contact the systems programmer.
Reason:
The JCL you used to load a table was successful.
Action:
None.
Reason:
The entry you made was not found in the Program Control Table or in the Task Control Area.
Action:
Check the program with PCT or TCT.
Reason:
The entry you made was not found in the Program Control Table or in the Task Control Area.
Action:
Check your program for PCT or TCT.
Reason:
Since the entry was already in the Exclusion Table, the entry you made was ignored by CA InterTest for CICS.
Action:
None.
Reason:
You were trying to turn off CA InterTest for CICS for a module that is not finished executing.
Action:
Complete the transaction, abend the task or delete it from the system.
Reason:
The facility requested is not installed.
Action:
Contact the systems programmer.
Reason:
The requested program was not found.
Action:
Check your program definitions and the DFHRPL data set concatenation.
Reason:
Valid machine instructions are always on even‑numbered addresses.
Action:
Correct the address and resubmit the command.
Reason:
There is no symbolic listing information for the saved program and Keep Windows are only valid with symbolic listing breakpoints.
Action:
The KEP option cannot be set for this program.
Reason:
The MON= option cannot be set on contiguous instructions. At least one machine instruction must exist between MON= settings.
Action:
None.
Reason:
The read‑only DSA is store‑protected and MON or NOM options cannot be specified for programs that reside there.
Action:
MON and NOM options cannot be set for this program.
Reason:
A CNTL=OFF command is issued for an entry that has no active KEP.
Action:
Correct the request and retry. The CNTL=INQ transaction may be used to display the active KEP options.
Reason:
KEP= options cannot be set for a terminal or a transaction.
Action:
None.
Reason:
The information that you entered contains too many characters.
Action:
Refer to the CA InterTest for CICS User Guide for information on the KEP option.
Reason:
The terminal ID you entered is invalid.
Action:
Specify a valid terminal ID, or bypass this function.
Reason:
The indicated option was disregarded.
Action:
Refer to the CA InterTest for CICS User Guide for information on using the option.
Reason:
The option you entered was executed successfully.
Action:
None.
Reason:
Global logging has been changed due to the command entered.
Action:
None.
Reason:
You tried to enter a breakpoint, but it was not generated.
Action:
Check the date and time of the load compared to the Symbolic File; there may be a mismatch. Recompile the program again, and ensure that all steps run successfully.
Reason:
You entered a 'GO TO' condition, and the program will now continue from the indicated point.
Action:
None.
Reason:
In response to CNTL=INQ, the following is a list of your breakpoints.
Action:
None.
Reason:
This is the automatic breakpoint terminal ID.
Action:
None.
Reason:
The terminal ID specified for the ABP command is defined in a Terminal Owning Region (TOR). The terminal ID in the TOR and the System ID of the TOR are listed in this message.
Action:
Informational.
Reason:
An error was detected in the CNTL command option identified by the option number.
Action:
Correct the command and resubmit.
Reason:
A generic monitoring entry was specified. See message CAIN4589 for more information.
Action:
None.
Reason:
Overhead for these tables could be increased due to the above condition (that is, +, ‑, . ).
Action:
Ensure that your table does not begin with a plus sign, minus sign or period.
Reason:
Instructional message.
Action:
Press PF3 to confirm what you did. Press any other key to reject what you did.
Reason:
A generic name was entered instead of a fully qualified name.
Action:
Specify a fully qualified name and resubmit.
Reason:
The program you entered was incorrectly defined to CICS and was ignored by CA InterTest for CICS, or the monitoring for a main composite program was not requested before a composite sub‑programs.
Action:
Ensure that the program is defined to CICS. Or, if the program is a composite sub‑program, you must start monitoring for the main composite program before starting monitoring its composite sub‑programs.
Reason:
The terminal ID was not found in the TCT.
Action:
Check the TCT for the correct terminal ID.
Reason:
The program you entered was not found in the PCT.
Action:
Check the PCT for the correct program.
Reason:
A CNTL command was issued for an invalid or remote program, and the request will be ignored.
Action:
Ensure that the program name is correct.
Reason:
A CA InterTest for CICS command has been entered for transaction (*). This transaction is a remote entry.
Action:
None.
Reason:
You have specified an address on an instruction that is not supported by CA InterTest for CICS.
Action:
Select an address for monitoring on a valid instruction.
Reason:
You have selected an address where MON has already been
Action:
Select an address that does not have monitoring assigned to it yet.
Reason:
You have selected a function that requires you to enter a password.
Action:
Enter the password.
Reason:
You have selected a function that requires you to enter a password.
Action:
Enter the password.
Reason:
The program name you specified cannot be found in any of the Symbolic Files.
Action:
Specify a valid program name.
Reason:
The specified program is not defined in the PPT or it has been disabled.
Action:
Specify a valid program name, or enable the program.
Reason:
The symbolic name that you specified is not a label or paragraph name.
Action:
Specify a valid label or paragraph name.
Reason:
The program that you specified is not in the PPT.
Action:
Specify a program that is defined to the PPT, or update the PPT with the program name.
Reason:
The CNTL=EDIT function is valid for option CMD only.
Action:
Correct the command and retry.
Reason:
The indirect commands defined for the program/terminal are currently either being edited or executed from another terminal. They cannot be accessed concurrently.
Action:
Wait until they are available and retry.
Reason:
An error occurred while attempting to execute indirect commands or access program IN25ICMD. The reason for the error follows in the succeeding message.
Action:
None.
Reason:
The program specified cannot be found or loaded.
Action:
Ensure that the program is defined in the PPT and can be loaded.
Reason:
CA InterTest for CICS storage chains have been damaged.
Action:
Get an SVC dump and contact CA technical support.
Reason:
The unprotect CWA option was requested in a CICS region which does not have a CWA generated.
Action:
You are either on the wrong CICS region or you must restart your CICS region with a CWA specified.
Reason:
The COBOL II runtime modules IGZCPCC and IGZCPAC cannot be defined as other than ASSEMBLER. Therefore, COBOL dynamic calls cannot be monitored.
Action:
Define IGZCPCC and IGZCPAC as ASSEMBLER or verify that AUTOINSTALL is not defining them as other than ASSEMBLER.
Reason:
The COBOL II runtime modules IGZCPCC and IGZCPAC cannot be defined as other than ASSEMBLER. Therefore, COBOL dynamic calls cannot be monitored.
Action:
Define IGZCPCC and IGZCPAC as ASSEMBLER or verify that AUTOINSTALL is not defining them as other than ASSEMBLER.
Reason:
The MON and NOM options cannot be set for a terminal or transaction monitoring entry.
Action:
Correct the request and retry.
Reason:
The PROG=.ALL can only be set by one user and it has already been set by the user specified.
Action:
None.
Reason:
The PROG=.OPTIONS can only be set by one user and it has already been set by the user specified.
Action:
None.
Reason:
The requested program was not available.
Action:
Contact your systems programmer.
Reason:
This message is produced in conjunction with another message. This message shows the contents of the above fields.
Action:
Contact your systems programmer.
Reason:
This message is produced in conjunction with one or more other messages which give information as to why the request failed.
Action:
Contact your systems programmer.
Reason:
CNTL=OFF,ALL syntax rules are:
Example:
CNTL=OFF,ALL,TTR=T001,FTR=T001
CNTL=OFF,ALL,USR=SMIJO01
Action:
Correct the command and resubmit.
Reason:
CNTL=OFF,ALL,... command did not find any breakpoints for the TTR/FTR=terminal or USR=userid.
Action:
Ensure that you specified the correct terminal or user id.
Reason:
The indicated option is only valid for COBOL programs.
Action:
Select a valid option.
Reason:
An INVALID request was made by one of the CA InterTest for CICS programs. This is an internal problem.
Action:
Perform the following steps:
Reason:
The CA InterTest for CICS Symbolic File was found to be in use by batch UTILITY program.
Action:
Perform the following steps:
Reason:
An internal error occurred while reading data from the CA InterTest for CICS Symbolic file.
Action:
Try recompiling the program and if the problem persists, call CA technical support.
Reason:
The specified statement number could not be found on the CA InterTest for CICS Symbolic File for the requested program.
Action:
If the program is PL1, this statement may have been removed due
Reason:
The PL1 variable was not defined as an array or the dimensions of the array could not be determined.
Action:
None.
Reason:
The program was not found on any symbolic file.
Action:
Specify a correct program name and retry the command.
Reason:
A request has been made which is not supported for the language, indicated xxxxx.
Action:
None.
Reason:
To view a data‑item, the program must be sitting at an CA InterTest for CICS breakpoint.
Action:
None.
Reason:
A STRUCTURE (PF12) request was made for a symbolic data item that was not contained in an Assembler DSECT or was COBOL data item that did not have a valid level number. For example: a COBOL paragraph name, a COBOL Index name, or an Assembler data item, which was defined within a CSECT.
Action:
None.
Reason:
A STRUCTURE (PF12) request was made for a symbolic data item which was defined in a PL/I program. At this time, STRUCTURE requests are invalid for PL/I programs.
Action:
None.
Reason:
The first argument for an ASSEMBLER data name was not found to be a register.
Action:
Correct the command and resubmit the request Syntax: 'register.dataname'
Specifies a symbolic reference for a register, like TIOABAR, or it may be specified as Rn, where n is the register number, like R15 for register 15.
Specifies a required delimiter.
Specifies the name of the data area which you wish to see.
Reason:
A symbolic request was made for an Assembler data item, with the register value (first argument) of 'Rn'. The 'Rn' name was NOT found in the Symbolic File, but an assumed value was used. For example: the value R15 was specified and not found, so register 15 was used.
Action:
Correct command and resubmit request if the assumed value was incorrect.
Reason:
A symbolic request was made for a COBOL data item with the following syntax: 'data‑item(x1,.,xn)' and the values specified for 'x1,.xn' were found to be a mixture of SUBSCRIPTS and INDEX names.
Action:
Change the command to specify all SUBSCRIPTS or INDEXES and resubmit the command.
Reason:
A symbolic request was made for a COBOL data item with the following syntax: 'data‑item(x1,.,xn)' and the number of exceeded the number of OCCURS clauses that could be used.
Action:
Change the command to specify the correct number of SUBSCRIPTS or INDEXES and resubmit command.
Reason:
The data item, indicated by xxxxxxx, was not found in the CA InterTest for CICS Symbolic File.
Action:
Check for the following conditions:
Reason:
The SUBSCRIPT or INDEX, specified by xxxxxxx, contained a NEGATIVE value.
Action:
Correct the value and resubmit the request.
Reason:
The SUBSCRIPT or INDEX, specified by xxxxxxx, did not contain a NUMERIC value.
Action:
Correct the value and resubmit the request.
Reason:
The SUBSCRIPT or INDEX, specified by xxxxxxx, was not defined with a NUMERIC PICTURE clause.
Action:
Change the command to specify a valid SUBSCRIPT/INDEX, or correct program.
Reason:
A symbolic request was made for a COBOL data item with the following syntax: 'data‑item‑2 OF data‑item‑1' and the value specified for 'data‑item‑1' was incorrectly specified. This could occur if its level number was greater than or equal to 'data‑item‑2' or it was an INDEX name.
Action:
Correct the command and resubmit request.
Reason:
A symbolic request for a COBOL II paragraph name or statement number resulted in more than one offset being found. This occurs because of the use of the COBOL II Optimize feature.
Action:
None.
Reason:
A PL1 label (xxxxxxxx) could not be found or the Procedure name block the label is defined in is not active.
Action:
Retry when the PL1 Block is active.
Reason:
Storage for the COBOL data‑name (xxxxxxxx) has not been allocated
Action:
Retry after the data‑name has been allocated.
Reason:
The PROC/BLOCK specified is not active.
Action:
Specify an active PROC/BLOCK.
Reason:
Specified program statement number is greater than the highest statement number in the program.
Action:
Ensure that the statement number you specified is defined in the program
Reason:
The printer was not set up for a BASED variable.
Action:
Supply a BASE pointer.
Reason:
The item selected is an INDEX set to (*).
Action:
None.
Reason:
No data names index was found.
Action:
Check your compiler options.
Reason:
The symbolic data found for the program specified was post‑ processed by an older release of CA InterTest for CICS.
Action:
Recompile the program and use the post‑processor from the current release.
Reason:
The data (*) was not found in the area that you specified.
Action:
Change the area that you are searching or change what you are searching for.
Reason:
The data item specified is indexed and CA InterTest for CICS is unable to calculate the number of times the data item occurs.
Action:
Specify a non-indexed data item.
Reason:
There is no source listing saved to the Symbolic File for this program.
Action:
Check your compile options.
Reason:
There is no cross‑reference section saved to the Symbolic File for this program.
Action:
Use LISTER=MAP or LISTER=ALL in your CA InterTest for CICS post compile processor parameters.
Reason:
The field indicated (*) was defined, but not referenced in the program.
Action:
None.
Reason:
There is no linkage‑editor map saved to the Symbolic File for this program.
Action:
CA InterTest for CICS was unable to save the linkage‑editor map. Check the linkage‑editor step for errors.
Reason:
The data item is defined as an '88' level, and it cannot be referenced by CA InterTest for CICS.
Action:
Do not reference data items defined as 88 level.
Reason:
You attempted to specify a qualified name for a non‑BASED variable.
Action:
Specify qualified names only for BASED variables.
Reason:
There were no paragraph names found for this program.
Action:
None.
Reason:
There were no labels found in this program.
Action:
None.
Reason:
The request you made is not a valid request for an index.
Action:
Specify a valid index request.
Reason:
You are not authorized to perform the requested task. Resource level security checking is in effect.
Action:
Contact the Security Administrator.
Reason:
No procedure names were found to match the specified criteria.
Action:
Check the selection criteria and try again.
Reason:
The PROTSYM file is corrupted so the requested record could not be found.
Action:
Contact your systems programmer for assistance.
Reason:
There was a syntax error in the command.
Action:
Correct the command syntax and try again.
Reason:
More indexes were specified than are allowed. COBOL and PL/I support 7 and 15 levels of subscripting, respectively.
Action:
Correct the request and resubmit.
Reason:
The language used in the specified program is not supported.
Action:
None.
Reason:
More than 15 qualifications were requested.
Action:
Correct the request and try again.
Reason:
A request was made for indexed qualified names but this is not supported.
Action:
None.
Reason:
The field specified contains too many numeric digits.
Action:
Correct the request and resubmit.
Reason:
The specified datatype is not supported for subscripting.
Action:
None.
Reason:
The values entered for the starting point and/or length reference a location that is greater than the data‑name's length.
Action:
Correct the erroneous fields and re‑enter the request.
Reason:
Either the starting position or the length field is not a positive number.
Action:
Correct the field and re‑enter the request.
Reason:
Your PL1 program needs to be recompiled and post processed with the latest PL1 Post‑Processor module IN25SYMP. This new version has enhanced support for displaying PL1 arrays.
Action:
Recompile your program using the newest PL1 post‑processor.
Reason:
The release of CA InterTest for CICS is not compatible with the release of CICS.
Action:
Install a compatible version of CA InterTest for CICS, or contact CA technical support.
Reason:
The transaction has ended.
Action:
None.
Reason:
CA InterTest for CICS has determined that an incorrect version of IN25OPTS is being used, and the values may be incorrect.
Action:
Regenerate IN25OPTS.
Reason:
IN25OPTS module was not found, and the defaults are displayed.
Action:
Generate an IN25OPTS module.
Reason:
An invalid option or command was entered.
Action:
Correct the request and retry.
Reason:
This message informs you of your site's current GENLEVEL of
CA InterTest for CICS.
Action:
None.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|