Reason:
The LISTER= option was invalid.
Action:
Correct the LISTER= option and resubmit your job stream.
Reason:
The CUTPRINT= option was invalid.
Action:
Correct the CUTPRINT= option and resubmit your job stream.
Reason:
The NOPURGE option was specified on the parameter statement.
Action:
None.
Reason:
An option was specified on the parameter statement was not recognizable.
Action:
Correct the parameter statement and resubmit your job stream.
Reason:
This identifies the LISTER option specified.
Action:
None.
Reason:
This identifies the CUTPRINT option specified.
Action:
None.
Reason:
No parameter statement was found.
Action:
Correct the parameter statement and resubmit your job stream.
Reason:
The CA InterTest for CICS Symbolic File has exceeded the maximum number of program entries.
Action:
Delete some programs for your file and resubmit your job stream. (The symbolic file capacity was greatly increased in Release 5.4.) Or, define a new CA InterTest for CICS Symbolic File and then resubmit your job stream using the new file. Refer to the SYMFIL= parameter in the CA InterTest for CICS Installation Guide for an explanation of how to handle multiple Symbolic files.
Reason:
Program XXXXXXXX is being processed and its output will reside on the CA InterTest for CICS Symbolic File.
Action:
None.
Reason:
This is an internal verification check error.
Action:
Contact CA technical support.
Reason:
This is an internal verification check error.
Action:
Contact CA technical support.
Reason:
A VSAM request, QQQQ, has resulted in an error. CA InterTest for CICS has reached the maximum number of program entries. This normally indicates a corrupted file.
Action:
Contact CA technical support.
Reason:
The CA InterTest for CICS Symbolic File has exceeded the maximum number records.
Action:
Either delete some programs for your file or increase the size of your symbolic file. (The symbolic file capacity was greatly increased in Release 5.4). Then resubmit your job stream. Or, define a new CA InterTest for CICS Symbolic File and then resubmit your job stream using the new file. Refer to the SYMFIL= parameter in the CA InterTest for CICS Installation Guide for an explanation of how to handle multiple symbolic files.
Reason:
In MVS, the DD JCL statement for the CA InterTest for CICS Symbolic File could not be found.
Action:
Correct the JCL and resubmit the job stream.
Reason:
In VSE, an error occurred when an SVC 63 (ENQ) was issued. This is normally caused by a NOT FOUND condition for the CA InterTest for CICS Symbolic file.
Action:
Check the JCL and correct. Contact CA technical support if the JCL is correct.
Reason:
The CA InterTest for CICS batch utility program was processing the Symbolic file at the same time that the post‑processor step was running.
Action:
First ensure that the last UTILITY run was successful. To turn off this indicator, run a UTILITY job with a REPORT function.
Reason:
A GETMAIN (MVS) or GETVIS (VSE) request has failed due to insufficient storage.
Action:
Resubmit the job stream with a larger region size.
Reason:
A condition has occurred that required a termination with a dump.
Action:
Contact CA technical support.
Reason:
The post‑processor has ended successfully and the program has been added to the CA InterTest for CICS Symbolic File.
Action:
None.
Reason:
On a successful completion, the number of source statements, XXXXXXX, displays.
Action:
None.
Reason:
On a successful completion, the total number of records added to the CA InterTest for CICS Symbolic File, YYYY, displays.
Action:
None.
Reason:
The CA InterTest for CICS post‑processor program has ended.
Action:
None.
Reason:
The CA InterTest for CICS post‑processor program has read all of the data passed to it in the INPUT data set.
Action:
None.
Reason:
The procedure names cross‑reference output area was not found.
Action:
Without this area, CA InterTest for CICS will be unable to process any requests using a PARAGRAPH NAME. If PARAGRAPH NAMES are needed, correct the COBOL options and resubmit the job stream.
Reason:
The data set specified by the INPUT JCL statement was empty.
Action:
Correct and resubmit the job stream.
Reason:
The required CA Optimizer (CAPEX) option MLIST was not specified.
Action:
Correct and resubmit the job stream.
Reason:
Area XXXXX could not be found in the COBOL listing. For Working Storage, at least one data item must be declared.
Action:
Correct COBOL compiler options or add a Working Storage data item to produce the required area and resubmit the job stream.
Reason:
The required COBOL II option, XXXXX, was not specified.
Action:
Correct and resubmit the job stream.
Reason:
After examining the entire Assembler listing, no labeled CSECT could be found.
Action:
Correct and resubmit the job stream.
Reason:
The input passed to the CA InterTest for CICS post‑processor program was generated by the CICS command translator and not by the compiler or Assembler.
Action:
Correct the procedure so that the passed output is from the compiler/Assembler.
Reason:
The INPUT file could not be opened. Check the printed output for additional error messages that may have been produced by the operating system.
Action:
Correct the JCL and resubmit the job stream.
Reason:
The OUTPUT file could not be opened. Check the printed output for additional error messages that may have been produced by the operating system.
Action:
Correct the JCL and resubmit the job stream.
Reason:
The CARDS file could not be opened. Check the printed output for additional error messages that may have been produced by the operating system.
Action:
Correct the JCL and resubmit the job stream.
Reason:
The Cross‑Reference area could not be found in the Assembler listing. Without this area, Symbolic names cannot be resolved.
Action:
Resubmit the job stream with either the XREF (SHORT) or XREF (FULL) Assembler parameter.
Reason:
The next group of printed lines is an echo of all the parameter statements read by the post‑processor.
Action:
None.
Reason:
The IN25LINK program has added XXX linkage‑editor records to an existing Symbolic entry.
Action:
None.
Reason:
The link‑name, XXXXXXXX, specified on an IN25LINK post‑processor control card could not be found in the output produced by the linkage‑editor.
Action:
You can do one of the following:
Reason:
The list of options following this message was not specified. Without these options, some CA InterTest for CICS facilities may not function.
Action:
Correct the JCL and resubmit the job stream.
Reason:
The post‑processor program could not find the data needed to process the statement information.
The following are some of the conditions that may cause this error:
Action:
Determine why the required area was suppressed. Correct and resubmit the job stream.
Reason:
In a VSE Assembler, a CSECT statement named XXXXXXX was found, but that name could not be found in the ESD list.
Action:
Correct the JCL and resubmit the job stream.
Reason:
The data passed to the IN25LINK post‑processor via the INPUT JCL statement did not contain the output produced by the linkage‑editor step or the linkage ‑ editor PARM=MAP is not in effect.
Action:
Correct the JCL and resubmit the job stream.
Reason:
The POWER= parameter was specified incorrectly.
Action:
Correct the parameter card and resubmit the job stream.
Reason:
The POWER LST class specified on the parameter card was not an alphabetic character.
Action:
Correct the parameter card and resubmit the job stream.
Reason:
The name specified in the POWER= parameter is invalid.
Action:
Correct the parameter card and resubmit the job stream.
Reason:
The CA InterTest for CICS module, IN25PWRI, was not found in the load library specified in the JCL. This module is required when using the VSE/POWER LST queue.
Action:
You may do one of the following:
Reason:
The CA InterTest for CICS module, IN25OPTS, was not found in the load library specified in the JCL.
Action:
If the default POWER options can be used (for a detailed description, see the CA InterTest for CICS Installation Guide), no action is required. However, it is recommended that the correct IN25OPTS module be added to the load library.
Reason:
The POWER= parameter was specified incorrectly.
Action:
Correct the parameter card and resubmit the job stream.
Reason:
A syntax error was found in the Realia Workbench Host Option parameter.
Action:
Correct the parameter card and resubmit the job stream.
Reason:
An error was found in the Realia Workbench Host Option parameter.
Action:
Correct the parameter card and resubmit the job stream.
Reason:
An error was found in the Realia Workbench Host Option parameter.
Action:
Correct the parameter and resubmit the job stream.
Reason:
The LISTER option was not specified in the Realia Workbench HostOption parameter.
Action:
The LISTER=ALL option is set by default.
Reason:
The Realia Workbench Host Option Interface Module was not linked.
Action:
Correct and resubmit the job.
Reason:
The License Management Program definition does not contain a license for PL1.
Action:
Ensure that you have the proper level of software installed. Contact CA technical support.
Reason:
CSECT name is greater than 8 bytes.
Action:
Correct and resubmit the job.
Reason:
HLASM option "LIST(133|MAX) is not supported.
Action:
Correct the option. Use "LIST(121)".
Reason:
The NOTHREAD option is not supported.
Action:
Correct the option. Use the THREAD option (IBM Default).
The following error messages are produced by a special checkout procedure. This procedure looks for conditions that corrupt the CA InterTest for CICS Symbolic File, PROTSYM. If any of the conditions is found, one of the following messages is issued and the batch processor program abends.
Contact CA technical support for help in handling these errors.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|