Reason:
You have specified more than one area to be displayed.
Action:
On the CORE=Bkpt for Assembler programs menu enter data in the special element fields or the Assembler base and Label fields or the Assembler base and Label fields or the Register # field or the Argument # field.
On the CORE=Bkpt for COBOL programs menu enter data in the COBOL name field or the special element field.
On the CORE=Bkpt for PL/I programs menu enter data in the PL/I data name field or the Special element field.
On the CORE=Syst menu enter data in the CICS AREA field or the ADDRESS field or the one of the CICS TABLE entry fields.
Reason:
One of the listed PF keys was not entered.
Action:
Choose one of the listed PF keys.
Reason:
Characters other than 0 ‑ 9 have been entered in a numeric field.
Action:
Enter valid numeric characters 0 ‑ 9.
Reason:
Data was entered in one but not both of the fields on the CORE=Bkpt menu for Assembler programs.
Action:
Enter data in both fields.
Reason:
Both the Task AREA and the GET STORAGE size fields have data entered on the CORE=TASK Menu.
Action:
Remove the data from one of the fields.
Reason:
An invalid keyword has been entered in either the CICS area field of the CORE=Syst Menu, the Task AREA of the CORE=Task Menu or the special element field of the CORE=BKPT Menu.
Action:
Press PF1 to obtain the list of all valid keywords.
Reason:
Only one of the above two fields has data entered.
Action:
Enter data in both fields.
Reason:
The new data field starts with something other than the valid letters in the message.
Action:
Correct, and enter data.
Reason:
Either no field has data entered on the CORE=Bkpt Menu for COBOL programs or only a SCAN, an existing data field or a new data field, has data entered.
Action:
Enter data in the COBOL name, special element, or MOVE fields.
Reason:
A request was made to load or delete without entering a program name.
Action:
Enter a program name.
Reason:
A request was made to scan backwards without entering data in the Scan value and Scan range fields.
Action:
Enter data in both fields.
Reason:
No data was entered on the CORE=Syst menu.
Action:
Enter data or Clear to exit.
Reason:
A request was made to GET STORAGE but only the class and/or the Initial value fields had data entered.
Action:
Enter a number in the Size field.
Reason:
Data was entered in the Optional Offset field that did not start with the ,+,‑, or % special character.
Action:
Begin the data with one of the special characters.
Reason:
A non‑numeric task number has been entered.
Action:
Enter a task number that consists of numbers.
Reason:
The existing data field must be either a hexadecimal, or character or combination of the two.
Action:
Enter the data in the correct format.
Reason:
The data entered in the Scan range field is neither a valid hexadecimal nor decimal number.
Action:
Enter a number in the range of 0 ‑ F.
Reason:
The special keyword BMSG was requested when there was no breakpointed task waiting at the user's terminal.
Action:
Select another special keyword.
Reason:
Data was entered for a location on either the CORE=Bkpt Menus or the CORE=Task Menu without a task number.
Action:
Enter a valid decimal number in the Task number field.
Reason:
The special keyword selected is not one of the valid keywords.
Action:
Press PF1 to obtain a list of all valid keywords.
Reason:
Data was entered in either the move from or move to fields of the CORE=Bkpt Menu for COBOL programs.
Action:
Enter data in both fields.
Reason:
Data has been entered in some other field than the Move From or Move To fields on the CORE=Bkpt Menu for COBOL programs.
Action:
Erase data from other fields on the menu.
Reason:
The Optional offset and/or the Scan value and/or VERIFY and/or CHANGE fields have been entered without entering a location or special element.
Action:
Enter a location or a special element.
Reason:
Data was entered on the CORE=Syst Menu without selecting data in the CICS AREA, ADDRESS, OR CICS TABLE entry fields.
Action:
Enter data in one of the fields.
Reason:
A procedure name followed by a colon was entered in the PL/I data name field on the CORE=Bkpt Menu for PL/I programs without following it with a data name.
Action:
Add a data name after the colon.
Reason:
The total number of characters entered in the fields of the Complex Cobol Data Names Menu is greater than 58.
Action:
Reduce the total number of characters to 58 or less.
Reason:
Data was not entered in the Data name field of the Complex Cobol Data Names Menu.
Action:
Enter the name of the field you wish to display.
Reason:
The CORE menus have generated an invalid message number.
Action:
Contact CA technical support with the exact information of the data entered.
Reason:
The named resource failed a resource level security check.
Action:
Either use a different resource or obtain the proper authority for the named resource.
Reason:
You pressed Clear to exit the menu.
Action:
None.
Reason:
There was not enough storage available to complete this problem.
Action:
When storage becomes available, re‑enter your request.
Reason:
The top of the data in a structured display has been reached.
Action:
None.
Reason:
The bottom of the data in a structured display has been reached.
Action:
None.
Reason:
You are using Composite Support, but no monitor names match the PPT names of the module.
Action:
Recompile the main module of the program, and add an entry to the Symbolic File that matches the PPT entry.
Reason:
Comments have been generated for this display. Review them and press PF5 to continue.
Action:
None.
Reason:
When you completed the menu for composite support, you pressed ENTER instead of PF5.
Action:
To set composite support, press PF5.
Reason:
A plus sign (+) may be used only to treat multi‑CSECT Assembler subroutines as one program. The plus sign must not be used on the first CSECT name of the subroutine, but may be used on any that follow.
Action:
Remove the plus sign.
Reason:
A character other than a plus sign (+) or slash (/) was entered to the left of a link name on the Composite Menu.
Action:
Enter either a plus sign or slash.
Reason:
A subroutine was assigned a monitor name that has a PPT entry.
Action:
Recompile the subroutine into the PROTSYM File, and assign it a name that is not in the PPT.
Reason:
The offset entered has at least one character not in the range from 0 to 9 or A to F.
Action:
Correct the data and re‑enter your request.
Reason:
A link name, monitor name length or language was not entered, but the offset field is blank.
Action:
Specify a valid offset.
Reason:
An invalid length was entered.
Action:
Specify only characters from 0 to 9 and A to F.
Reason:
A link name, monitor name, offset or language was entered, but the length field was left blank.
Action:
Specify a valid length.
Reason:
A language was specified that is not COBOL (COB), COBOL II (COB2), Assembler (ASM) or PL/I.
Action:
Specify a valid language.
Reason:
An invalid character was entered to the left of a link name on the Composite Menu.
Action:
Specify a plus sign (+) or a slash (/).
Reason:
A plus sign (+) was entered to the left of link name, but the monitor name field contains a name.
Action:
Delete the name in the monitor name field.
Reason:
An invalid character was entered in the link name field.
Action:
Specify the only the following characters in the link name: A‑Z, 0‑9, $, @, #.
Reason:
A monitor name, offset, or language was entered, but the link name is missing.
Action:
Specify a valid link name.
Reason:
The same link name was entered more than once.
Action:
Specify a different link name where necessary.
Reason:
The same monitor name was entered more than once.
Action:
Specify a different monitor name where necessary.
Reason:
The offset entered does not end with 0 or 8.
Action:
Specify an offset that ends with 0 or 8.
Reason:
Composite support has previously been established for a PPT entry that uses the same monitor name for at least one of the monitor names currently displayed.
Action:
Either change the monitor names online, or recompile or reassemble the subroutines specifying a different name in the CA InterTest Batch Post Processor step.
Reason:
You entered a PF key that is not available with this screen.
Action:
Enter a valid PF key.
Reason:
The named resource failed a resource level security check.
Action:
Select a different resource with the proper authority, or obtain the necessary authority for the named resource.
Reason:
The input message is invalid.
Action:
Correct the input and re‑enter the request.
Reason:
CA InterTest for CICS ignored your request.
Action:
Check to see if your request is valid. Correct and resubmit.
Reason:
The target area is beyond the permitted storage area, which caused an I/O error during the read/write to temporary storage.
Action:
None.
Reason:
The terminal that was supposed to receive the breakpoint is out of service or was not found in the Terminal Control Table (TCT).
Action:
Check the TCT to find out the status of the terminal.
Reason:
This error occurs when a transient data write operation is requested and a length of zero is specified.
Action:
Check the input length and respecify if necessary.
Reason:
The task requested could not be found at the specified breakpoint.
Action:
None.
Reason:
A request was made for symbolic support for a function that does not support symbolic requests, or program symbolics were not found in the Symbolic file of CA InterTest for CICS.
Action:
Check the Symbolic File.
Reason:
A storage chain has been broken.
Action:
None.
Reason:
An illegal or failed GETMAIN has been terminated.
Action:
Retry the transaction. If the error persists, contact CA technical support.
Reason:
An internal logic error has occurred.
Action:
Contact CA technical support.
Reason:
The menu processing has ended normally.
Action:
None.
Reason:
The transaction is not authorized to access the program name.
Action:
Correct the authorization settings of the CA InterTest for CICS transactions.
Reason:
An illegal or failed GETMAIN has been detected, which caused the transaction to be terminated.
Action:
Retry the transaction. If the error persists, contact CA technical support.
Reason:
The menu processing has ended.
Action:
None.
Reason:
An internal logic error occurred.
Action:
Contact CA technical support.
Reason:
A non‑authorized condition was detected.
Action:
Check the condition.
Reason:
The only symbolic data that was found for the requested program was in update mode. This may happen when the program is being compiled or assembled or the CA InterTest for CICS post‑processor failed to run successfully.
Action:
Re‑compile/assemble your application program.
Reason:
While processing a request, a bad sequence number was found. A sequence number is an internal reference for processing. This error indicates a corrupted CA InterTest for CICS Symbolic File.
Action:
For assistance, contact CA technical support.
Reason:
The data entered in the Stmt # field was found to contain one or more non‑numeric characters, that is, not within the range of 0 through 9.
Action:
Correct the data and resubmit request.
Reason:
The data entered in the Margin= field was invalid. Valid entries are 1 to 50.
Action:
Correct and resubmit request.
Reason:
The data entered in the Displacement= field contained one or more non‑hexadecimal characters. Valid hexadecimal characters are all numbers from 0 through 9 and all characters from A through F.
Action:
Correct and resubmit request.
Reason:
The data entered in the Option # field was invalid.
Action:
After returning from the HELP facility, press PF4 to display the Lister Profile screen. The two lines, starting at the one labeled OPTS, describes the valid options.
Reason:
A search request, options 9 or 10, has been made without having any data entered in the Label/Search Arg= field.
Action:
Enter the search data and retry the request.
Reason:
More than one request was entered, such as a statement number and a displacement request.
Action:
Correct and resubmit request.
Reason:
The area requested in the Option # field does not exist in the saved listing. This may occur when the CA InterTest for CICS post‑processor was run with a LISTER=REF and OPTION # 6 (cross‑reference) is requested. This error also occurs when Option # 5 (Clist/Pmap) is requested for a COBOL program that was compiled with the CAPEX optimizer. Another reason for this error message is when a Search request, Options 9 or 10, is made for an argument that was not found.
Action:
None.
Reason:
A terminal control key, which does not has an assigned function, has been entered. Examples of this would be, pressing PF10 (single step) when a program is not at a breakpoint or pressing the PA1 key.
Action:
None.
Reason:
A program must be held at a CA InterTest for CICS breakpoint to use a GOTO request.
Action:
None.
Reason:
The name entered in the Program= field could not be found in any the CA InterTest for CICS symbolic files that are known to this CICS region. Either the program name is not in any of the CA InterTest for CICS symbolic files, or one or more symbolic files are inaccessible because they are disabled or not open.
Action:
Check the status of your CA InterTest for CICS symbolic file by using option 03 of the VRPT transaction. If all the symbolic files are accessible, compile/assemble the missing program with a procedure that contains a CA InterTest for CICS post‑processor step.
Note: You can find the return and reason codes for the Dynamic Protsym load feature in Appendix C.
Reason:
A program name was missing from the Program= field when an ENTER or PF key was pressed.
Action:
Enter the program name and retry request.
Reason:
A display request for the assembler data item, xxxxxxxx, was rejected because of its data type, yyyy. For example, a request to display the data name CSAX21, when used in the instruction TM CSAOPREL,CSAX21, would be rejected with the message ' CSAX21 is defined as a MASK '.
Action:
None.
Reason:
When processing a display request from the lister screen for a PL/I program, the cursor was found placed within a comment.
Action:
Retry request with the cursor positioned under a data name.
Reason:
The name entered in the Terminal ID = field, from the Profile, could not be found in the Terminal Control Table (TCT).
Action:
Correct the data and resubmit.
Reason:
The LISTER facility was entered from a breakpoint and a request to set a breakpoint was made for the displayed program. However, the program was not being monitored at a program level.
Action:
None.
Reason:
The location, indicated by xxxx , may not be used for a CORE display or move request. This error may occur if a TIOA compression package is installed in the system. You may also receive the CAIN2919 and CAIN2954 messages.
Action:
Ensure that all CA InterTest for CICS transactions are not affected by any TIOA compression packages.
Reason:
CA InterTest options - breakpoints, may not be set at the location XXXXX. This error may occur if a TIOA compression package is active in system. You may also receive the CAIN2918 and CAIN2954 messages.
Action:
Ensure that all of the CA InterTest for CICS transactions are not affected by any TIOA compression packages.
Reason:
The location, indicated by xxxxx, is not a valid location for a GOTO request. This error occurs when the request is made at a data names definition.
Action:
Retry the GOTO request at a valid location.
Reason:
The composite command has completed successfully, and the current composite load module has been established. The current composite load module is used as a qualifier when setting breakpoint options on composite subroutines.
Action:
None.
Reason:
The list facility has detected an attempt to list a subroutine that is part of a composite load module. This message is simply informational. If the same subroutine is defined to more than one composite load module and you wish to refer to a subroutine belonging to a load module other than the one in the message, use the COMPOSITE command to set it.
Action:
None.
Reason:
A VSAM request, for the CA InterTest for CICS Symbolic File has failed. The message provides you with the VSAM ERROR CODE (in hex) and the VSAM RETURN CODE (in hex).
Action:
Look up the VSAM ERROR and RETURN CODE in your VSAM manual and then take the recommended action. Note: The lister transaction terminates on any input after this message is displayed.
Reason:
A request to display data has been entered along with other types of requests. For example, a display request is entered on one line and a request to set a breakpoint is entered on another line.
Action:
You may either remove the display requests and process or remove the other requests and process.
Reason:
More than one GOTO request, G, has been entered on the source display.
Action:
Remove all of the GOTO except for the one that is required and press the ENTER key to process.
Reason:
The LISTER= option was not specified when doing the CA InterTest Batch post‑processor step for this program.
Action:
Recompile or reassemble the application program with the CA InterTest Batch post‑processor step that has the LISTER+ option specified.
Reason:
More than one request to set a conditional breakpoint, C, was found after examining the screen input.
Action:
After returning from the help facility, remove all but one of the conditional breakpoint requests and press the ENTER key. After that request has been processed, you may make the next conditional breakpoint request.
Reason:
A character was entered at the beginning of a displayed line of source that has no function. Valid characters are B C D M U X + ‑ @ %.
Action:
Remove or change any invalid characters that were entered on the screen and retry request.
Reason:
CA InterTest for CICS detected an abend in the program.
Action:
Call CA technical support.
Reason:
An abend request has been made with an abend code that starts with the letter A. Abend codes that start with the letter A are restricted to IBM usage.
Action:
Request the abend with a different abend code.
Reason:
The data entered did not contain one of the following values:
Display with titles
Display without titles
Display registers instead of titles
Action:
Correct data and retry request.
Reason:
The data entered was found to contain one or more non‑numeric characters.
Action:
Correct the data and retry request.
Reason:
The data entered was not one of the following:
Scroll forward or backward a full page
Scroll forward or backward a half page
Scroll to the next or previous breakpoint location number ‑ scroll forward or backward by this amount
Action:
Correct data and retry.
Reason:
The data entered was not one of the following:
Use the source listing breakpoint display
Use the detailed breakpoint display
Action:
Correct and retry request.
Reason:
The program has encountered an unusual condition and will be terminated by the next input command.
Action:
None.
Reason:
The contents of one of the displayed registers contained one or more non‑hexadecimal characters.
Action:
Correct the contents of the register and retry request.
Reason:
The data entered from the lister screen contained one or more MOVE requests along with other request types.
Action:
Remove the other requests and process only the MOVE requests.
Reason:
A lister service request was made which uses the cursor position to determine the data name that it applies to. However, the cursor was not found under any part of a data name.
Action:
Reposition the cursor so that it is under any part of the data name and retry the request.
Reason:
The program statement number for the requested label was not found.
Action:
None.
Reason:
A bypass error request, B, was entered on the lister screen. However, it was not used on the statement that had the error.
Action:
Remove the B from its current location and enter it at the correct location.
Reason:
A display request was made on an assembler instruction that does not contain any fields that can be displayed; for example, SVCs.
Action:
None.
Reason:
An assembler data name display request was made at an instruction that uses Register 0 as a base register.
Action:
None.
Reason:
MOVE requests cannot be used on an assembler program.
Action:
None.
Reason:
The CNTL option entered in the Option # field did not contain a known option.
Action:
Pressing PF2 from the lister screen displays the CNTL menu. The option numbers displayed on this screen are the only valid entries.
Reason:
The character that follows the CNTL menu request was not an S (set) or R (remove). This character indicates if the requested options are to be set or removed for the monitored program.
Action:
Correct and resubmit the request.
Reason:
An invalid request was entered for a data name.
Action:
Enter a valid request and retry or remove the invalid request.
Reason:
An invalid request was entered for a Procedure name or label.
Action:
Correct and resubmit.
Reason:
The usage of the System‑Wide options selection menu, =32, or CNTL one‑ line commands that request system‑wide functions are not permitted when requested from the ZIST facility. System‑wide functions include: START, END, RESTART, GLOG, CKPT, and PURGE.
Action:
Exit the lister facility. Then enter the CNTL menus directly or enter the one‑line command from a clear screen.
Reason:
A scroll request, which has STOP set for the amount, was made for a program that does not have any breakpoints.
Action:
Press PF4 to view the lister profile, change the PF7/8 amount field and retry the scroll request.
Reason:
A scroll backward request, which has STOP set for the amount, was made from a screen that is currently showing the first breakpoint set in the program.
Action:
None.
Reason:
A forward scroll request, which has STOP set for the amount, was made from a screen that is currently showing the last breakpoint set for the program.
Action:
None.
Reason:
A display request, for an assembler data name, cannot be done from the displayed dsect because of the margin value.
Action:
Reset the margin value to 34 or less, and then try the display request.
Reason:
When trying to process a screen request, the saved TIOA was found to contain data from software that compresses TIOAs. Some examples of these packages are CTOP and 3270 SUPER OPTIMZER.
Action:
Exclude all CA InterTest for CICS transactions from the TIOA compression software package.
Reason:
When changing data, by over-typing, in the keep window, invalid data or an invalid numeric value was entered for the data type. This occurs when entering data that does not match the data type or a numeric value that is too large for the data type. For example, the maximum value an S9(4) COMP field can hold is +32767.
Action:
Correct the data or press ENTER to redisplay screen.
Reason:
Certain requests, like abending the task, are not allowed when the ZIST facility is entered from the SymDump facility.
Action:
None.
Reason:
An invalid number has been entered in the Wait amount = field.
Action:
Correct and retry.
Reason:
The CA InterTest for CICS help facility does not contain any information about the abend that has occurred in your program.
Action:
For diagnostic information related to this abend, see the IBM CICS Messages and Codes for your version of the CICS transaction server for z/OS.
Reason:
The location chosen for the setting of a MON or NOM option is invalid.
Action:
Review the restrictions for the setting of these options, then retry the request.
Reason:
The data entered for this field did not contain one of the following values:
To activate the auto‑stepping facility
To deactivate the auto‑stepping facility
Action:
Correct and retry.
Reason:
The data entered in this field was not one of the following: CALL ‑ to stop auto‑stepping at Commands, Macros, or UEXI calls number ‑ the number of steps to perform before stopping
Action:
Correct the data and retry.
Reason:
The data entered on the Command= line did not start with a CA InterTest for CICS transaction code.
Action:
Correct and retry.
Reason:
A CA InterTest for CICS dispatch command was requested for a program that is not currently stopped at a breakpoint. A dispatch command has either a CNTL*... or a CNTL=GO,.. syntax.
Action:
None.
Reason:
The character entered at left of the KEEP element was invalid. The following are valid options:
To display a KEEP element
To generate a MOVE request for a KEEP element
To remove a KEEP element
To keep a dynamic KEEP element (AutoKeep feature only)
Action:
Change the option and retry or press ENTER to re‑display the screen.
Reason:
A MOVE (M) request was made for a KEEP element that was not defined as a COBOL or PL/I data name.
Action:
Over‑type the data that is displayed in the KEEP window or type a "D" at the left of the KEEP element that needs to be changed, then change data from within the CORE facility.
Reason:
The CA InterTest for CICS security program was found to be unusable when an attempt was made to verify the CORE password.
Action:
Report the problem to the person within your organization who is responsible for the CA InterTest for CICS product.
Reason:
The hexadecimal data displayed for a KEEP element was overtyped with non‑hexadecimal data. Valid hexadecimal data consists of the numbers 0 through 9 and the characters A through F.
Action:
Correct the data and retry the request.
Reason:
An attempt is being made to modify data that is not owned by this task, by overtyping the data shown in a KEEP window. The KEEP element that is in error is displayed with this message.
Action:
Enter the same password that is generated in your system for the CA InterTest for CICS CORE facility in the area "‑‑‑‑". The change to the data is ignored if the correct password is not entered.
Reason:
The password entered in the CAIN2969 message was incorrect.
Action:
Retry the password just in case it was mistyped.
Reason:
The CNTL command entered on the LISTER command line, for example CNTL=NEW,..., is not permitted.
Action:
Exit the LISTER facility and re‑issue the command.
Reason:
An attempt was made to change the character portion of a KEEP window, which contains lowercase characters.
Action:
Either enter the changes in the hexadecimal portion of the KEEP window or type a D at the right of the keep item and then make the changes on the CORE screen.
Reason:
The data displayed in the KEEP window for xxxxx is store‑protected and may not be changed.
Action:
The change request is ignored and the original data is displayed.
Reason:
A + or ‑ character was entered at the beginning of a displayed line of source code. These characters request the MON or NOM options, respectively. However, MON/NOM support has not been enabled at your installation.
Action:
Remove or change the + or ‑ characters and retry your request. To enable MON/NOM, contact your systems programmer.
Reason:
A V line command was entered at the beginning of a displayed line of source code. This character represents establishing a variable change breakpoint, which is not supported for PL/I language programs.
Action:
Remove or change the V character and retry your request.
Reason:
The character entered does not match either the default or alternate national language defined by the LANG1= and LANG2= CA InterTest for CICS customization parameters.
Action:
Enter one of the language characters displayed in the profile screen.
Reason:
The CA InterTest for CICS LISTER function was terminated.
Action:
None.
Reason:
The SOURCE BACKTRACE function could not find a valid backtrace table entry. There is an internal CA InterTest for CICS problem or the backtrace table storage has been damaged.
Action:
Request a transaction dump, and contact CA technical support.
Reason:
The master index records cannot be found in the Symbolic file. The SOURCE BACKTRACE function cannot display the Backtrace Summary Menu. This is an internal CA InterTest for CICS problem or a critical control block has been damaged.
Action:
Request a transaction dump and contact CA technical support.
Reason:
An internal error occurred scanning the Symbolic File records The SOURCE BACKTRACE function cannot display the Backtrace Summary Menu. This is an internal CA InterTest for CICS problem or a critical control block has been damaged.
Action:
Request a transaction dump, and contact CA technical support.
Reason:
The Source Listing's date and time stamps are not equal to the program's load module's post processing data and time.
Action:
Check the source and load dates and times. If they do not match, recompile to PROTSYM File.
Reason:
You specified 'S' next to more than one Backtrace Statement Block, and you specified a duplicate or a numeric bookmark. Only one 'S' is allowed, and bookmarks must be unique and contain at least one non‑numeric character.
Action:
Correct the error and try again.
Reason:
You specified 'S' next to more than one Backtrace Statement Block or you specified a character in the 'S' column that is not an 'S'.
Action:
Correct the error and try again.
Reason:
You specified a duplicate or a numeric bookmark. Only one 'S' is allowed, and bookmarks must be unique and contain at least one non‑numeric character.
Action:
Correct the error and try again.
Reason:
You specified an invalid key or entered invalid data on the Backtrace Summary screen.
Action:
Correct the error and try again.
Reason:
You are positioned at the first (or oldest) entry in the internal backtrace table.
Action:
None.
Reason:
You are positioned at the last (or newest) entry in the internal backtrace table. The last entry reflects where the current breakpoint is positioned.
Action:
None.
Reason:
The Backtrace Summary screen displays the first (or oldest) and last (or newest) entries in the internal backtrace table.
Action:
None.
Reason:
The numeric value specified in the 'From' field on the Backtrace Summary menu cannot be greater than the 'Of' value. The 'Of' value is the maximum number of internal backtrace table entries currently active for this program. You can also specify a valid 'bmrk' value in the 'From' field to re‑position the Backtrace Summary screen.
Action:
Correct the error and try again.
Reason:
The 'bmrk' value specified in the 'From' field was not a valid bookmark. You either specified an incorrect bookmark or the internal backtrace entry associated with the previously defined bookmark had been deleted.
Action:
Specify the correct bookmark.
Reason:
Option 12 must be used with one or more 'U' or 'C' type breakpoints. This option is used to select additional breakpoints options such as the first 'Indirect Command' to be executed when this breakpoint is encountered.
Action:
Only use Option 12 with one or more 'U' or 'C' breakpoints
Reason:
Option 11 was specified for an ASSEMBLER program and INDIRECT COMMANDS are not supported for ASSEMBLER type programs.
Action:
Do not specify option 11 for ASSEMBLER type programs.
Reason:
The data‑name specified by the cursor position on a D, K, M, or V line command could not be found in the programs XREF.
Action:
Ensure that you used the proper COBOL II or COBOL/370 compile options when the program was compiled.
Reason:
The CA InterTest for CICS program specified is not defined to your CICS region or cannot be loaded.
Action:
Ensure that the program is available in the DFHRPL concatenation.
Reason:
The data entered was not one of the following:
Use the AutoKeep display feature
Do not use the AutoKeep display feature
Action:
Correct and retry request.
Reason:
The AutoKeep display feature is not available under this programming language or under this version of a language's compiler.
Action:
Review the documentation provided with the latest release and genlevel of CA InterTest for CICS to verify which languages and compilers support the AutoKeep display feature.
Reason:
The AutoKeep display feature cannot be activated until monitoring has been requested for the program.
Action:
Initiate monitoring by either hitting PF5 or setting a breakpoint request within the program before activating the AutoKeep display feature.
Reason:
The data entered was not one of the following:
Start the Code Coverage feature
Stop the Code Coverage feature
Action:
Correct and retry request.
Reason:
The Code Coverage feature cannot be activated until monitoring has been requested for the program.
Action:
Initiate monitoring by either hitting PF5 or setting a breakpoint request within the program before activating the Code Coverage feature.
Reason:
The Code Coverage feature can only be activated for a single user at a specific "From" terminal.
Action:
No action can be taken until the user at the "From" terminal stops their Code Coverage session.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|