Reason:
No data has been entered on the menu screen.
Action:
Enter data or Clear to exit from menu.
Reason:
This was a restriction in CA InterTest for CICS version 2.3. These entries are ignored in CA InterTest for CICS version 2.4 and later.
Action:
Erase highlighted entries.
Reason:
Monitoring options can be specified to programs, transactions, or terminals.
Action:
Make separate entries for programs, transactions, and terminals.
Reason:
The entered function is blank or not A through L.
Action:
Enter function A through L or Clear to exit menu.
Reason:
A time interval was entered and neither PURGE nor CKPT was selected or, ABP terminal was entered with ABP.
Action:
Enter on/off for desired function.
Reason:
The keyword ON/OFF was not entered on the System‑Wide Options Menu.
Action:
Enter the keyword ON or OFF.
Reason:
Function A through H was entered on the function selection menu and no program, transaction or terminal identification was entered.
Action:
Enter at least one program or transaction or terminal identification.
Reason:
No entry was entered on the Function Selection Menu.
Action:
Enter Function A through N or Clear to exit menu.
Reason:
One of the listed PF keys was not entered.
Action:
Choose one of the listed PF keys.
Reason:
More than one format has data entered.
Action:
Enter data in only one format.
Reason:
Data was entered for one side of the condition and not the other on the Conditional Breakpoint Menu.
Action:
Enter data for the other side of the condition.
Reason:
Data was entered in the RESUME EXECUTION and the ABEND fields on the Resume Task Execution Menu.
Action:
Select one of these options.
Reason:
Data was entered in the SINGLE STEP and ABEND fields on the Resume Task Execution Menu.
Action:
Select one of these options.
Reason:
Data was entered in the DUMP and ABEND fields on the Resume Task Execution Menu.
Action:
Select one of these options.
Reason:
The generated command was incorrect.
Action:
Contact CA technical support.
Reason:
Data entered in only one side of the replace program name option on the Replacement Options Menu.
Action:
Enter data in both fields.
Reason:
Data was entered in only one side of the Replace file name option on the Replacement Options Menu.
Action:
Enter data in both fields.
Reason:
Data was entered in only one side of the Replace TD queue name option on the Replacement Options Menu.
Action:
Enter data in both fields.
Reason:
Data was entered in either the TS selection on TS replacement mask fields on the Replacement Options Menu.
Action:
Enter data in both fields.
Reason:
Data was entered in either the FROM or TO fields of the Bypass Storage Protection option on the Protection Options Menu.
Action:
Enter data in both the FROM and TO fields.
Reason:
Data was entered in either the Offset or Length fields of the unprotect CSA option or the CWA option on the Protect Options Menu.
Action:
Enter data in both the offset and length fields of the CSA or the CWA options.
Reason:
Data was entered in either the Address or Length fields of the unprotect main storage area option on the Protection Options Menu.
Action:
Enter data in both fields.
Reason:
Data was entered in either the Address or Length fields of the protect main storage area option on the Protection Options Menu.
Action:
Enter data in both fields.
Reason:
Data was entered in more than one field that is used for either the Left Side or the Right Side of the condition on the Conditional Breakpoint Menu.
Action:
Erase the data in all fields but one.
Reason:
One of the shown operators was not selected on the Conditional Breakpoint Menu.
Action:
Enter one of the six displayed operators.
Reason:
A packed decimal literal was entered in the literal field and no length was specified for the left‑side comparison on the Conditional Breakpoint Menu.
Action:
Specify the length for the left‑side condition.
Reason:
You did not enter a length for the right‑side comparison on the Conditional Breakpoint Menu.
Action:
Specify a length for the right‑side condition.
Reason:
The keyword 'ON' was entered in the PURGE and/or CHKPT fields without an interval specified on the System‑wide Options Menu.
Action:
Specify a time interval.
Reason:
Data was entered in the program name field for the NEW and/or SYM option, but no function was selected on the Utility Options menu.
Action:
Select the desired function.
Reason:
The SYM or NEW option was selected on the Utility Options Menu, but the associated program name field was left blank.
Action:
Specify a program name.
Reason:
Data was entered in the Optional Offset Field without the proper lead character on the Conditional Breakpoint Menu.
Action:
Start the data with one of the shown characters.
Reason:
The program name entered on the Function Selection Menu or on the Utility Options Menu does not have a PPT entry.
Action:
Enter the name of a valid program. Check the PPT Table.
Reason:
The transaction name entered on the Function Selection Menu does not have a PCT entry.
Action:
Enter the name of a valid transaction.
Reason:
The terminal identification entered on the Function Selection Menu or the System‑Wide Menu was not found in the TCT.
Action:
Enter a valid terminal identification.
Reason:
Undetermined.
Action:
Contact CA technical support.
Reason:
No data was entered on the Breakpoint Locations Menu.
Action:
Enter data or Clear to exit.
Reason:
Data was entered in one or more of the Identification # fields as well as in a location, loop control number, or terminal identification field on the Remove Breakpoint Menu.
Action:
If ID numbers are entered, they must be the only fields entered on this menu.
Reason:
No data was entered in the task number field of the Resume Task Execution Menu.
Action:
Enter a valid task number.
Reason:
More than nine locations were entered on the Breakpoint Locations Menu.
Action:
Enter a maximum of nine locations.
Reason:
Data entered started with a period on the Breakpoint Locations Menu.
Action:
Remove the leading period.
Reason:
Multiple program names were entered together with functions11 through 13 on the Function Selection Menu.
Action:
Specify only one program name.
Reason:
Breakpoints may only be set for a program on the Function Selection Menu.
Action:
Remove the transaction ID, and enter a program name.
Reason:
Breakpoints may only be set on the Function Selection Menu.
Action:
Remove the terminal ID, and enter a program name.
Reason:
A TD queue was chosen to receive a report from the Utility Options Menu, but no keyword was entered.
Action:
Specify LIST, SYM, or INQ in addition to the name of a TD queue.
Reason:
ALL is acceptable only when removing options specified on the Protection Options Menu.
Action:
Press PF8 to return to the Main Menu, then enter R to remove protection.
Reason:
Invalid data was entered for the Limit monitoring function on the Replacement Options or on the Protection Options Menu.
Action:
Enter a * or a valid terminal identification.
Reason:
A dump code beginning with the letter A was entered on the Resume Task Execution Menu.
Action:
Change the first letter.
Reason:
Both New and SWI functions were selected on the Utility Options Menu.
Action:
Select one or the other function.
Reason:
Both functions were selected on the System‑Wide Options Menu.
Action:
Select one or the other function.
Reason:
Invalid data was entered on the Breakpoint Locations Menu.
Action:
Enter valid data or press PF9.
Reason:
Function 10 through 22 was entered on the Function Selection Menu, but S (set) or R (remove) was not specified.
Action:
Specify either S or R with these functions.
Reason:
Breakpoints cannot be set on a global basis.
Action:
Enter a specific program name.
Reason:
Global options cannot be set with options for specific program names.
Action:
Set options either globally or for individual program names.
Reason:
More than 9 entries were specified on the Breakpoint Locations Menu.
Action:
Enter a maximum of 9 locations.
Reason:
Function 30 was requested on the Main Menu, but no program, transaction or terminal ID was entered.
Action:
Enter at least one program name, transaction code or terminal ID when you specify Function 30.
Reason:
A generic value was specified as the program name.
Action:
Enter a specific program name.
Reason:
From the Resume Task Menu, the task cannot be abended without specifying an abend code or "XXXX" to abend without a dump.
Action:
Specify either an abend code or 'X' to abend without a dump.
Reason:
This feature is not available with this release of CA InterTest for CICS, but is available with the specified release.
Action:
None.
Reason:
'R' was entered with Function 23 to remove monitoring from a composite program.
Action:
Use Function 10 to remove monitoring.
Reason:
A generic value was entered as the program name.
Action:
Enter a specific program name.
Reason:
Multiple program names were entered for Function 23.
Action:
Enter only one program name.
Reason:
The function selected also requires that a program name be specified.
Action:
Specify a program name.
Reason:
Composite support can only be set on a program.
Action:
Delete the transaction name and specify a program name.
Reason:
Composite support can only be set for a program.
Action:
Delete the terminal ID, and specify a program name.
Reason:
The name specified in the program name field is not the PPT name for the module.
Action:
Specify the PPT of the composite module.
Reason:
Request breakpoints and composite support are not available with this release of CICS.
Action:
None.
Reason:
The FOL= PPTname Option is not supported by this release of CICS.
Action:
Enter either 'ON' or 'NO PPT'.
Reason:
The wait amount does not contain a value from 1 through 59.
Action:
Specify the number of seconds from 1 to 59 for the wait amount.
Reason:
The stop value does not contain the word "CALL" or a numeric value of 1 through 9999.
Action:
Specify the word 'CALL' or enter a value from 1 to 9999.
Reason:
The data entered in the STDA value field is not in the range of 1 through 9999.
Action:
Specify a value of 1 through 9999.
Reason:
Either the wait value or the halt value was left blank.
Action:
Specify valid values for the wait field and the halt field.
Reason:
Either the wait value or the stop value is missing.
Action:
Specify a valid wait value and halt value.
Reason:
You attempted to set request breakpoints at both CALLs to DB2 and all IN25UEXI defined CALLs.
Action:
Specify either CALLs or DB2.
Reason:
Instructional message.
Action:
Press Enter to execute the displayed commands. Press Clear to exit from this display.
Reason:
Instructional message.
Action:
Press Enter to continue with the specified function. Press Clear to exit from the menu.
Reason:
You entered a PF key that is not available with this screen.
Action:
Specify a valid PF key.
Reason:
There was not enough storage available to complete this request.
Action:
When storage space becomes available, re‑enter your request.
Reason:
An internal error has occurred in CA InterTest for CICS.
Action:
Obtain a dump, and contact CA technical support.
Reason:
You pressed Clear to exit the menu.
Action:
None.
Reason:
An internal error has occurred in CA InterTest for CICS.
Action:
Obtain a dump and contact CA technical support.
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:
When ID numbers are entered, no other field may have data on the Remove Locations Menu.
Action:
Remove data from terminal identification fields.
Reason:
The Special Keyword Field contains invalid data on the Conditional Breakpoint Menu.
Action:
Press PF1 to obtain a list of valid keywords.
Reason:
Undetermined.
Action:
For assistance, contact CA technical support.
Reason:
Segmented monitoring cannot be set for a transaction or terminal ID. It can be set for a program only.
Action:
Specify a valid CICS program name.
Reason:
A specific terminal ID or user ID is required to enable data monitoring.
Action:
Specify a valid terminal ID or user ID.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|