Ca Optimizer/ii Message Reference Guide

Transcript

CA Optimizer®/II Message Reference Guide r8.5 Second Edition This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors. Copyright © 2010 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. CA Technologies Product References This document references the following CA Technologies products: ■ CA TestCoverage™ ■ CA Librarian® ■ CA Endevor® Change Manager ■ CA Common Services for z/OS ■ CA CICSORT™ ■ CA Netman® Contact CA Technologies Contact CA Support For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources: ■ Online and telephone contact information for technical assistance and customer services ■ Information about user communities and forums ■ Product and documentation downloads ■ CA Support policies and guidelines ■ Other helpful resources appropriate for your product Providing Feedback About Product Documentation If you have comments or questions about CA Technologies product documentation, you can send a message to [email protected]. To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs. Documentation Changes The following documentation updates have been made since the last release of this documentation: ■ CAPU013W—Added the new message and description. ■ CAPU014E—Changed the title from CAPU13E to CAPU14E. Contents Chapter 1: Introduction 7 Message Format ........................................................................................................................................................... 7 Chapter 2: Messages 9 CAPxyyyz Messages ...................................................................................................................................................... 9 CAPHCyyyz Messages ............................................................................................................................................... 198 Chapter 3: Abend Codes 201 Contents 5 Chapter 1: Introduction This guide defines all the errors, warnings, and informational messages specific to CA Optimizer/II. It serves as a debugging tool for all COBOL programmers using CA Optimizer/II in a z/OS environment. This section contains the following topics: Message Format (see page 7) Message Format All messages issued by CA Optimizer/II are in the format CAPxyyyz, where CAP is the message prefix for CA Optimizer/II and xyyyz are described in the following table: Code Description Value Description x Component issuing the message A Analyzer C Execution Monitor D Detector E Extended Detector H TSO facility I Repository Interface P Optimizer R Analyzer Reporter T Compile/optimize-time Run Executive U Utilities Z EOS yyy Message number 1-999 Message identifier z Action to be taken E An error has occurred. Processing will not continue. I This is an informational message, no action is required. W This is a warning message. Processing will continue, but there may be an impact on results. Chapter 1: Introduction 7 Message Format Three vertical dots between two messages mean that all message numbers falling between those two numbers produce the same message text and have the same Reason and Action text as the surrounding messages. Example CAPP310E . . . CAPP319E 8 Message Reference Guide Chapter 2: Messages This section contains CAPxyyyz error messages. This section contains the following topics: CAPxyyyz Messages (see page 9) CAPHCyyyz Messages (see page 198) CAPxyyyz Messages This section lists the CAPxyyyz messages where CAP is the message prefix for CA Optimizer/II. For more information about the message format for these messages, see Message Format (see page 7). CAPA201W USER PROGRAM HAS ACTIVE STIMER. TIMINGS TERMINATED. Reason: The execution step contains non-COBOL programs using the STIMER facility. Timing is terminated. The application program execution continues. Action: Check with your systems programmer to ensure task timing using STIMER is available. It must be available to ANALYZER for timings to be taken. CAPA202W ANALYZER UNABLE TO START TASK TIMER. TIMINGS TERMINATED. Reason: This usually occurs when STIMERM is not specified and another program is using STIMER. Action: Specify STIMERM ON as an override in your options file. Chapter 2: Messages 9 CAPxyyyz Messages CAPA203W STIMERM NOT SUPPORTED ON MVS/SP. TIMINGS TERMINATED. Reason: STIMERM has been specified (either at installation time or as an override in the options file) on an MVS/SP system. The STIMERM option is only supported on MVS/XA and above. Action: Specify STIMERM=NO in your execution time defaults (CAOUDFRX) or STIMERM OFF as an override in your options file. CAPA204W JOB STEP TIMING NOT ACTIVE. TIMINGS HAVE BEEN TERMINATED. Reason: The sampling function is not available in this environment with programs using the STIMER facility. Timing is terminated, but the application program execution continues. Action: Check that TIME=1440 was not specified for the Job Step. If TIME=1440 was specified, change it to a lower value. If the problem persists, contact CA Technical Support for assistance. CAPA298W MAXIMUM NUMBER OF SAMPLES EXCEEDED. EXCEED STOP SPECIFIED. Reason: The maximum number of samples was exceeded during sampling, and EXCEED STOP was specified. The application program execution is terminated. Action: If you want more samples, or if you do not want execution terminated before the application program completes, specify EXCEED NOSTOP in the options file, or increase the number of MSAMPLE. 10 Message Reference Guide CAPxyyyz Messages CAPA299W MAXIMUM SAMPLE TIME EXCEEDED. EXCEED STOP SPECIFIED. Reason: The maximum sample time was exceeded during time sampling, and EXCEED STOP was specified. The application program execution is terminated. Action: If you want more samples, or if you do not want execution terminated before the application program completes, specify EXCEED NOSTOP in the options file or increase the time specified on the MTIME option. CAPC011W NO INPUT DATA PRESENT -- INSTALLATION DEFAULTS USED. Reason: There were no records in the CAIOPTS data set. All the installation-specified option settings in the default CSECT module apply for this execution. Action: Ensure that default options are intended; see the Options in Effect section of the Execution Monitor Summary. Make any necessary corrections and rerun. CAPC012I INPUT OPTION DISPLAY COMPLETE. Reason: This message is printed on CAIPRINT to announce the end of input data in the CAIOPTS data set. Action: None. Chapter 2: Messages 11 CAPxyyyz Messages CAPC013I 'keyword' PARAMETER IGNORED DUE TO PREVIOUSLY DEFINED dddddddd STATEMENT. Reason: The SYMDSN or PRTLIB parameter was specified in the CAIOPTS data set, but the CAISYM or CAIPRTLB DD was already coded in the JCL. These parameters cannot be used to override DD statements in the JCL. Action: This is an informational message, no action is required. The parameter is ignored. However, to eliminate this error, remove the DD statement from your JCL or remove the parameter from CAIOPTS. CAPC014W KEYWORD CONFLICTS EXIST. ANALYZER KEYWORDS WERE FOUND BUT XREPORT IS NOT IN EFFECT. Reason: This message warns of a potentially unintended result. A scan of the keyword parameters present in the CAIOPTS data set has indicated the presence of valid keywords. These keywords are related to the output control of the Analyzer Reporter function. The Execution Monitor can give control to the Analyzer component prior to job-step termination, but only if XREPORT ON is specified or defaulted. Action: No action required. However, if you want to eliminate this error message, either remove the keywords related to Analyzer or add XREPORT ON for the next execution of the run. CAPC015I ANALYZER REPORTER WILL BE CALLED AUTOMATICALLY IF ANY PROGRAMS REQUEST COUNTS AND/OR TIMINGS. Reason: XREPORT ON was defaulted or specified. Prior to job-step termination, the Execution Monitor calls Analyzer for a reporting of the CAITIMSV file for the run. Action: None. 12 Message Reference Guide CAPxyyyz Messages CAPC016E A REQUIRED RTL MODULE COULD NOT BE LOADED. Reason: Execution of an Optimized program was attempted, but the runtime library could not be found. For example, compilation might be done on system A, but when execution is attempted on system B, the runtime library cannot be located. Execution is halted immediately with a user 1016 ABEND code. Action: Perform the following before calling CA Technical Support: 1. Check for the presence of the CA Optimizer/II runtime library in the TASKLIB/STEPLIB/JOBLIB allocation, or 2. Verify with your systems programming personnel that the runtime library is present in the system link library concatenation (LNKLSTxx). 3. Verify with your systems programming personnel that the CA Optimizer/II runtime was initialized at IPL time or by executing CAIRIM using the CAS9 procedure. 4. Resubmit the job. CAPC017W RUN TIME ENVIRONMENT IS NOT PROPERLY INITIALIZED FOR VS COBOL II SUPPORT. Reason: The CA Optimizer/II RTL has not been properly activated. Action: Review the procedure for RTL activation using CA Common Services in the Activate RTL and Extended Detector Support step in the Installation Guide. Chapter 2: Messages 13 CAPxyyyz Messages CAPC018E DYNAMIC ALLOCATION FAILED FOR DDNAME dddddddd, RC=nn, S99INFO=hhhh, S99ERROR=hhhh. Reason: An error occurred during an attempt to dynamically allocate the file specified by DDNAME. This could be a simple user error such as a misspelled data set name, or it could be a system problem. nn is the return code from SVC 99. hhhh gives various informational reason codes about the error encountered during SVC 99 processing. Depending on the error, the job step may be terminated. If the allocation was for a symbolic (PROTSYM or CSL) data set, execution continues. However, some symbolic information may not be available in your reports. Action: See one of the following IBM publications for an interpretation of these SVC 99 error codes, or retain all JCL and console log information and contact CA Technical Support for assistance. ■ GC28-1150-1 MVS/XA SPL: System Macros and Facilities Volume 1 ■ GC28-0627-2 OS/VS2 MVS SPL: Job Management, pages 27-31. CAPC019E THIS RUNTIME DOES NOT SUPPORT TESTCOVERAGE COBOL II PROGRAMS. Reason: The current runtime library does not support COBOL II programs that are compiled with the CA TestCoverage product. Action: Ensure that the STEPLIB DD statement includes the CA TestCoverage libraries. If your current runtime system is CA Optimizer/II, check that it is initialized correctly. Review the procedure for RTL activation using CA Common Services in the Activate RTL and Extended Detector Support step in the Installation Guide. 14 Message Reference Guide CAPxyyyz Messages CAPC020W 'string' IS NOT RECOGNIZED AND WILL BE IGNORED. Reason: An unrecognizable keyword has been located in the CAIOPTS DD and is ignored. Scanning resumes with the next token on the card image or the next record, and execution continues. Action: Correct the string on the CAIOPTS DD statement and resubmit the job. CAPC021I 'string' IS AN INVALID OPERAND FOR 'keyword'. KEYWORD REJECTED. Reason: An unrecognizable operand has been located in the 'keyword' option of the CAIOPTS DD statement that was specified; the operand is ignored. Scanning resumes with the next token on the card image or the next record, and execution continues. Action: Correct the string and resubmit the job. CAPC022I 'string' IS AN INVALID OPERAND FOR 'keyword'. NAME MUST NOT EXCEED 8 CHARACTERS. Reason: A valid keyword is followed by a token (option value) that is greater than 8 characters. The keyword is ignored. Scanning resumes with the next token on the card image or the next record, and execution continues. Action: Correct the token, make it fewer than 9 characters, and resubmit the job. Chapter 2: Messages 15 CAPxyyyz Messages CAPC023I 'string' IS AN INVALID OPERAND FOR 'keyword'. NAME CONTAINS AN INVALID CHARACTER. Reason: A valid 'keyword' is followed by a token (option value) that contains a non-alphanumeric character. The 'keyword' is ignored. Scanning resumes with the next token on the card image or the next record. Execution continues. Action: Correct the token, make it an alphanumeric character, and resubmit the job. CAPC024I 'string' IS AN INVALID OPERAND FOR 'keyword'. VALUE EXCEEDS MAXIMUM ALLOWABLE SIZE. Reason: A valid keyword contains an option value that exceeds the limit placed on the magnitude or size of that value. The value is set to the maximum. Action: No action required. However, to eliminate this informational message, correct the value of the option and resubmit the job. CAPC025I 'string' IS AN INVALID OPERAND FOR 'keyword'. VALUE MUST BE NUMERIC. Reason: A valid 'keyword' contains a non-numeric option value. The 'keyword' is ignored, and the default (if any) for this keyword is used. Scanning resumes with the next token on the card image or the next record, and execution continues. Action: No action required. However, to eliminate this informational message, correct the value of the option and resubmit the job. 16 Message Reference Guide CAPxyyyz Messages CAPC026I 'string' IS AN INVALID OPERAND FOR "PFLOW". VALUE LESS THAN MINIMUM. RESET TO MINIMUM (64). Reason: The minimum acceptable value for PFLOW is 64. The specified value for the PFLOW option was less than 64. It is set to the minimum of 64 for this run. Action: No action required. However, to eliminate this informational message, correct the PFLOW option value for the next run. CAPC027I 'string' IS AN INVALID OPERAND FOR "PFLOW". VALUE GREATER THAN MAXIMUM. RESET TO MAXIMUM (32768). Reason: The maximum value for the PFLOW option is 32768. The specified value for the PFLOW option is greater than 32 KB. It is set to the maximum for this run. Action: No action required. However, to eliminate this informational message, correct the PFLOW option value for the next run. CAPC028W 'PFLOW string' HAS BEEN MODIFIED AND ROUNDED UP TO NEAREST POWER OF 2 NOT EXCEEDING 32K. Reason: The PFLOW value specified was not a power of 2 and has been rounded up to the next power of 2 not to exceed 32768. ThE INTERNAL PFLOW algorithm makes the entries in the PFLOW buffer a power of 2 for efficiency reasons. Action: No action required. However, to eliminate this informational message, correct the PFLOW option value for the next run. Chapter 2: Messages 17 CAPxyyyz Messages CAPC029I PRINT FILE, NORMAL OUTPUT SUPPRESSED BY REQUEST. Reason: This message is written to the console (ROUTCDE=11) during initialization because of the detection of CPXRPTS=SUPPRESS in the default CSECT module, CAOUDFRX. All output which would normally be written to CAIPRINT is suppressed for this run. Action: No action is required. No override is possible with this setting in CAOUDFRX. CAPC030I CA Optimizer/II RTL INITIALIZATION REQUESTED. Reason: The RTL initialization program was invoked to initialize the CA Optimizer/II RTL. Action: None. CAPC031I CA Optimizer/II RTL INITIALIZATION COMPLETED. Reason: The CA Optimizer/II RTL was initialized successfully. Action: None. CAPC032E CA Optimizer/II RTL INITIALIZATION FAILED. Reason: An error was encountered while attempting to initialize the CA Optimizer/II RTL. Action: Save all output listings and Virtual Host Manager. 18 Message Reference Guide CAPxyyyz Messages CAPC033I CA Optimizer/II RTL REFRESH REQUESTED. Reason: The RTL initialization program was called but the CA Optimizer/II RTL was already initialized. A refresh will instead be attempted. Action: None. CAPC034I CA Optimizer/II RTL REFRESH COMPLETED. Reason: The CA Optimizer/II RTL was refreshed. Action: None. CAPC035E CA Optimizer/II RTL REFRESH FAILED. Reason: The CA Optimizer/II RTL was not refreshed because the DELETE function failed one or more modules. Action: Save all output listings and Virtual Host Manager. CAPC036E CA OPTIMIZER/II RTL REFRESH FAILED. Reason: The CA Optimizer/II RTL was not refreshed because the LOAD function failed for one or more modules. Action: Check to ensure that module CAOCBST2 resides in the same authorized library as RX70INIT. Chapter 2: Messages 19 CAPxyyyz Messages CAPC040I CA Optimizer/II RTL TERMINATION REQUESTED. Reason: The RTL termination program was invoked to terminate the CA Optimizer/II RTL. Action: None. CAPC041I CA Optimizer/II RTL TERMINATION COMPLETED. Reason: The CA Optimizer/II RTL was terminated successfully. Action: None. CAPC042E CA Optimizer/II RTL TERMINATION FAILED. Reason: The CA Optimizer/II RTL was not terminated because the DELETE function failed for one or more modules. Action: Save all output listings and Virtual Host Manager. CAPC043W CA Optimizer/II RTL IS NOT INITIALIZED. Reason: The CA Optimizer/II RTL was not terminated because it had not been previously initialized. Action: None. 20 Message Reference Guide CAPxyyyz Messages CAPC045W "XREPORT" TURNED OFF DUE TO ALLOCATION FAILURE. Reason: This message is issued if CA Optimizer/II is unable to dynamically allocate CAIPRNT1 or CAIPRNT2. The CAIPRNT1 and CAIPRNT2 files are required for the XREPORT option. Action: Execute Analyzer Reporter as a separate step using the CAIARII procedure, or add CAIPRNT1 and CAIPRNT2 DD statements to your JCL and resubmit the job. CAPC046W "XCOUNT" FEATURE DISABLED DUE TO OMITTED TIMSV DATA SET. Reason: The XCOUNT option was specified at execution-time, but a CAITIMSV DD statement was not included in the JCL. Counts and timings have been terminated for this job step. Action: If an Analyzer report is required, add a CAITIMSV DD statement to the JCL and retry. Otherwise, no action is necessary. CAPC072E "PGM" PARAMETER OMITTED. EXECUTION CANNOT PROCEED. Reason: The Execution Monitor was invoked directly as a job-step program using EXEC PGM=CAOCEM00 (alias CPXCEM), but there was no corresponding user program named which the Execution Monitor could LOAD and call. The job step terminates with a return code of 16. Action: Correct by supplying the PGM keyword with the name of the application program to be LOADed and called. (Syntax: PGM pppppppp, where pppppppp is the name of the load module). Then resubmit the JCL. Chapter 2: Messages 21 CAPxyyyz Messages CAPC074E INVALID CALL TO CPXCEMRU. NO RUN UNITS ARE ACTIVE. Reason: A user program intending an unconventional task termination has called CPXCEMRU to remove the COBOL run unit from monitoring control. However, the Execution Monitor found no active run units on its internal chains. This is a probable user error but could also be an internal error. The task is abended with a U1074 abend and a dump. Action: Retain the dump, all JCL and listings and contact CA Technical Support for assistance. CAPC076W xxxxxxxx WAS NEVER CORRECTLY EXITED. MODULE STILL MARKED ACTIVE AT TERMINATION. Reason: xxxxxxxx is the program-ID of a COBOL module whose entry was detected by the Execution Monitor. The Execution Monitor is in the process of terminating, and it has discovered that the program named xxxxxxxx has never terminated. This could be the result of intermixing with non-COBOL programs which fail to follow standard linkage conventions. For example, if A calls B, which calls C, C must return to B; it does not return directly to A. The message is written to CAIPRINT, and the remainder of the INTERNAL control blocks related to run unit chaining are examined. Orderly termination of the task proceeds; however, this message may be a prelude to more serious errors if the save area chains have been destroyed. Action: Review the source code of the named module for proper adherence to standard linkage conventions. 22 Message Reference Guide CAPxyyyz Messages CAPC077E ERROR ADDING FILE TO THE CAIPRINT REPOSITORY. Reason: An error occurred while adding a CAIPRINT report to the central VSAM repository. Action: Review the supplementary CAPC077E message that follows for more information about the nature of the error. Take appropriate steps to resolve the indicated error. A list of supplementary CAPC077E messages follows: ■ CAPC077E Invalid request ■ CAPC077E Unable to allocate ACB ■ CAPC077E Unable to allocate RPL ■ CAPC077E Unable to modify RPL ■ CAPC077E Unable to allocate repository ■ CAPC077E ENQUEUE failed ■ CAPC077E Unable to open repository ■ CAPC077E Unable to read repository record ■ CAPC077E Unable to read repository record for update ■ CAPC077E Unable to write repository ■ CAPC077E Unable to close repository ■ CAPC077E DEQUEUE failed ■ CAPC077E repository is full ■ CAPC077E Logic error, READ prior to OPEN ■ CAPC077E Invalid index id requested Verify the following: ■ The repository was correctly generated at installation time (see the Allocate CAIPRINT Repository Library step in the Installation Guide.) ■ The PRTLIB option in the default CSECT, CAOUDFRX, specifies the correct library. ■ The repository is not full. If it is full, use the utility program, CAOUPRTU, to delete or archive selected reports. If the error persists, save all output listings and Virtual Host Manager. Chapter 2: Messages 23 CAPxyyyz Messages CAPC078W FILE NOT ADDED TO THE CAIPRINT REPOSITORY Reason: Conditions prevented a CAIPRINT report from being written to the repository. Action: Review the supplementary CAPC078W message that follows for more information about what prevented the CAIPRINT report from being written to the repository. If needed, take appropriate steps to resolve the problem. A list of supplementary CAPC078W messages follows: ■ CAPC078W Report not found in repository ■ CAPC078W Report date mismatch ■ CAPC078W Report time mismatch ■ CAPC078W Lock error ■ CAPC078W Duplication limit exceeded ■ CAPC078W Repository is empty If you want to have CAIPRINT reports written to the central VSAM repository, verify the following: ■ The repository was correctly generated at installation time (see the Allocate CAIPRINT Repository Library step in the Installation Guide.) ■ The PRTLIB option in the default CSECT, CAOUDFRX, specifies the correct library. ■ The DUPLIM option in the default CSECT, CAOUDFRX is not set too low. The repository is not full. If it is full, use the utility program, CAOUPRTU, to delete or archive selected reports. If the problem persists, save all output listings and contact CA Technical Support. 24 Message Reference Guide CAPxyyyz Messages CAPC081E INVALID PROGRAM RETURN SEQUENCE. SEE USER GUIDE FOR CALL/ENTRY/RETURN REQUIREMENTS. Reason: The Execution Monitor is in the process of monitoring the exit of a given program. During save area chain validity checking, it is determined that a serious violation of save area linkage has occurred that makes further execution impossible. The Execution Monitor abends the task with a U1081 abend and a dump. Action: Review the source code of the named module for proper adherence to standard linkage conventions. If all appears reasonable, save all the documentation and Virtual Host Manager for assistance. CAPC082E OUT OF SPACE FOR INTERNAL CONTROL BLOCKS. INCREASE REGION SIZE. Reason: A conditional GETMAIN failed in an attempt to obtain more storage from subpool 0 (user storage). Execution is terminated immediately with a U1082 abend. Action: Increase the region size available to the job step and resubmit the job. CAPC084E INVALID ERROR CODE PASSED TO CAOCER00. Reason: Internal programming error. A module has called the error print module, CAOCER00, with an invalid error code in Register 0. Execution is terminated immediately with a U1084 abend. Action: This is a product error. Contact CA Technical Support for assistance. Chapter 2: Messages 25 CAPxyyyz Messages CAPC085E ATTEMPT TO FREE COUNT ACCUMULATION AREA WHICH IS NOT ASSIGNED. Reason: ProbablE INTERNAL error. A program which was Optimized with XCOUNT is in the process of terminating. An attempt to locate this program on an internal control block chain for the purpose of freeing the work area for XCOUNT has failed. The task abends with a U-1085 abend. Action: Save all the output and contact CA Technical Support for assistance. CAPC088E UNABLE TO LOAD MODULE CAODMAIN Reason: The Execution Monitor was unable to load Detector module, CAODMAIN. Execution terminates. Action: Verify that the library containing module CAODMAIN is available at execution-time in LINKLIST or LPA, or was specified in the JCL in STEPLIB or JOBLIB. CAPC089E INVALID CALL TO CPXCEM INTERNAL ENTRY POINT Reason: An error has occurred upon entry to the Execution Monitor. The task abends with a U-1089 abend. Action: Save all the output and Virtual Host Manager for assistance. 26 Message Reference Guide CAPxyyyz Messages CAPC091E INTERNAL ERROR. MTAP/XTAP CANNOT BE TRACED ACROSS THE RUN UNIT. Reason: Execution is terminated with a U1091 abend and a dump. Either Detector or MAPPER called the Execution Monitor to locate the first MTAP or XTAP associated with the run unit prior to the current one supplied as input. Action: Save all related documentation, including the dump, and Virtual Host Manager for assistance. CAPC092E OUT OF COUNT SPACE. EXCEED STOP SPECIFIED. Reason: During the initialization processing of a non-COBOL II program Optimized with XCOUNT, a conditional GETMAIN was attempted for a storage block to hold count values. If EXCEED STOP was specified, execution is terminated immediately with a U1092 abend and dump; otherwise, the XCOUNT routine associated with the current OS/VS COBOL program is disabled (no more counts are logged). Reporting of counts may be inaccurate. Action: Increase the region size to prevent this problem from occurring, or consider removing the EXCEED STOP specification to allow execution to continue. CAPC094E PRINT FILE HAS BEEN OMITTED AND CANNOT BE ALLOCATED. RUN TERMINATED. Reason: This message is issued after message CAPC018E is issued to the console and user log. The CAIPRINT file is required for execution, and the allocation failure causes immediate termination of the run with a U1094 abend code and dump. Action: CAPC018E should provide clues to the failure of dynamic allocation, or you can supply a DD statement of your own to identify the problem. Correct the error accordingly and resubmit the job. Chapter 2: Messages 27 CAPxyyyz Messages CAPC095E TIMSV COULD NOT BE DYNAMICALLY ALLOCATED. RUN TERMINATED. Reason: This message is issued after message CAPC018E is issued to the console and user log. The CAITIMSV file is required for execution, and the allocation failure causes immediate termination of the run with a U1095 abend code and dump. Action: CAPC018E should provide clues to the failure of dynamic allocation, or you can supply a DD statement of your own to identify the problem. Correct the error accordingly and resubmit the job. CAPC096I COUNTS AND TIMINGS TERMINATED. "XREPORT OFF" IN EFFECT WITHOUT TIMSV DD STATEMENT. Reason: The XREPORT ON option was specified at execution time, but a CAITIMSV DD statement was not included in the JCL. Counts and timings have been terminated for this job step and the XREPORT option has been turned off. Action: If an Analyzer report is required, add a CAITIMSV DD statement to the JCL and retry. Otherwise, no action is necessary. CAPC097E INTERNAL ERROR. DIAGNOSTIC PGM IN CONTROL. Reason: The error recovery mechanisms (for example, ESTAE exits) of the Optimizer runtime system have encountered an unexpected and unrecoverable abend. The most likely event is an unexpected 0Cx abend in the runtime system. This could be traceable to an invalid control block, product logic error, or user error. The runtime system captures a few data elements related to the abend and attempts to relate the abending PSW address to an offset within a named module. The abend code (e.g., 0C4) and the registers at abend, along with other pertinent information are written to CAIPRINT. The execution monitor then issues a user ABEND code of 1097 and an ABEND dump is produced. The difference in abend code reflects what process was in control at the time of the abend. 28 Message Reference Guide CAPxyyyz Messages This message is issued (abend code 1097) when a user diagnostic program was in control and did not return to its caller. The Installation Guide documents how a customer can create a reporting module for specific abend codes that are given control by Detector to report on the error. For example, assume that the runtime system has initially trapped a system 0C1. Normally, Detector calls the distributed module CAOD00C1 to produce the abend box (description, probable causes, etc.). If a 1097 abend appears, you should look for the presence of an entry for 0C1 in the user abend table module CAOCAB80. This customization process is discussed in the Installation Guide. Action: Contact CA Technical Support to report the problem after the dump is available. In the RTM2WA summary, abends are represented by a chain of SDWA control blocks displayed in chronological order from the oldest to the newest. Generally, diagnose the problem by finding the SWDA in the RTM2WA SUMMARY chain that matches the abend code and registers displayed on CAIPRINT. The unexpected and unrecoverable abend is documented as the SDWA that is queued just prior to the final user abend code 1097. CAPC098E INTERNAL ERROR. DETECTOR IN CONTROL. Reason: The error recovery mechanisms (for example, ESTAE exits) of the Optimizer runtime system have encountered an unexpected and unrecoverable abend. The most likely event is an unexpected 0Cx abend in the runtime system. This could be traceable to an invalid control block, product logic error, or user error. The runtime system captures a few data elements related to the abend and attempts to relate the abending PSW address to an offset within a named module. The abend code (for example, 0C4) and the registers at abend, along with other pertinent information, are written to CAIPRINT. The execution monitor then issues a user abend code of 1098 and an abend dump is produced. As the message text implies, the difference in abend code reflects what process was in control at the time of the abend. This message is issued when Detector (CAODxxxx) was in control and did not return to its caller. Action: Contact CA Technical Support to report the problem after the dump is available. In the RTM2WA summary, abends are represented by a chain of SDWA control blocks displayed in chronological order from the oldest to the newest. Generally, diagnose the problem by finding the SDWA in the RTM2WA SUMMARY chain that matches the abend code and registers displayed on CAIPRINT. The unexpected and unrecoverable abend is documented as the SDWA that is queued just prior to the final user abend code 1098. Chapter 2: Messages 29 CAPxyyyz Messages CAPC099E INTERNAL ERROR. EXECUTION MONITOR OR MAPPER IN CONTROL. Reason: The error recovery mechanisms (for example, ESTAE exits) of the Optimizer runtime system have encountered an unexpected and unrecoverable abend. The most likely event is an unexpected 0Cx abend in the runtime system. This could be traceable to an invalid control block, product logic error, or user error. The runtime system captures a few data elements related to the abend and attempts to relate the abending PSW address to an offset within a named module. The abend code (for example, 0C4) and the registers at abend, along with other pertinent information are written to CAIPRINT. The execution monitor then issues a user abend code of 1099 and an abend dump is produced. The difference in abend code reflects what process was in control at the time of the abend. If CAPC099E is issued (abend code 1099), the Execution Monitor itself (CAOCxxxx) or the Analyzer XTIME handler (CAOAxxxx) was in control. Action: Contact CA Technical Support to report the problem after the dump is available. In the RTM2WA summary, abends are represented by a chain of SDWA control blocks displayed in chronological order from the oldest to the newest. Generally, diagnose the problem by finding the SDWA in the RTM2WA SUMMARY chain that matches the abend code and registers displayed on CAIPRINT. The unexpected and unrecoverable abend is documented as the SDWA that is queued just prior to the final user abend code of 1099. CAPD101E PROGRAM INTERRUPT OCCURRED IN A PROGRAM WITHOUT THE DTECT FEATURE. Reason: This message only occurs if the INTERCEPTS feature is on, but DTECT was not specified for the program incurring the program interruption. Action: See the chapter "Using Detector" in the User Guide. 30 Message Reference Guide CAPxyyyz Messages CAPD102E MAXIMUM NUMBER OF PROGRAM INTERRUPTIONS HAS BEEN EXCEEDED. Reason: Program interruption exceeded the maximum number specified by the INTERCEPTS parameter. Processing terminates with the Detector Abend report. Action: Rerun job with a larger number specified for the INTERCEPTS parameter if further debugging is needed. CAPD103E IMPRECISE PROGRAM INTERRUPTION. Reason: When using the INTERCEPTS feature, Detector cannot tell exactly where the erring instruction is located; therefore, it can't adjust the data and continue. Also, when the application abends, Detector cannot determine the exact instruction which caused the abend. Detector processing continues and the normal Detector Abend report is generated. Action: None. CAPD105E PROGRAM INTERRUPTION IS NOT RECOVERABLE. Reason: The INTERCEPTS feature is specified, but the data for this interruption cannot be fixed. Processing continues. The normal Detector Abend report is generated. Action: None. Chapter 2: Messages 31 CAPxyyyz Messages CAPD106W MAXIMUM NUMBER OF PROGRAM SNAPSHOTS HAS BEEN EXCEEDED. Reason: Snapshots exceeded the maximum number specified by the SNAP parameter. No more snapshots are reported. Action: Rerun job with a larger number specified for the SNAP parameter if further debugging is needed. CAPD107E INSUFFICIENT MAIN STORAGE AVAILABLE. Reason: Detector ran out of memory. Action: Increase the region size. For details on how much storage is required by Detector, see the appendix "Performance Considerations" in the Installation Guide. CAPD108I THE PROGRAM WHICH HAS ABENDED CANNOT BE TRACED BACK TO A DETECTOR PROGRAM. Reason: This message is issued because of nonstandard linkage between the abending program and the latest active Detector COBOL program. The Detector Abend report skips back to the latest active Detector COBOL program. Action: None. 32 Message Reference Guide CAPxyyyz Messages CAPD109W SNAPSHOT CALL TURNED OFF. Reason: The region size is not large enough for operation of the SNAP feature. The feature is turned off and program processing continues. Action: Increase region size. For details, see the appendix "Performance Considerations" in the Installation Guide. CAPD110W SYMBOLIC FILE INITIALIZATION FAILED. Reason: An error was detected while trying to access a PROTSYM or CSL file. Detector reporting continues, but symbolic support will not be provided for this execution. Action: Verify that your PROTSYM and CSL data set names have been specified correctly and that the files are correctly defined. Rerun the job if necessary. If you cannot determine the cause of this message, contact CA Technical Support. CAPD112W NO SYMBOLIC INFORMATION FOUND FOR PROGRAM "xxxxxxxx". Reason: Detector is attempting to retrieve symbolic information for a program, but no information was found in any of the PROTSYM or CSL files available to Detector. Detector processing continues, but symbolic support is not provided for the program. Action: First, verify that the symbolic information has been written to a PROTSYM file or a CSL file. Then verify that the symbolic file is available to Detector using your installation defaults, your JCL, or a SYMDSN override. If you still cannot determine the cause of this message, Virtual Host Manager. Chapter 2: Messages 33 CAPxyyyz Messages CAPD113W SYMBOLIC MEMBER DATE/TIME DOES NOT MATCH CURRENT PROGRAM. Reason: Symbolic information was found for at least one version of your program in one of the available symbolic files, but the time stamp in the program does not exactly match the symbolic information. Action: First, verify that the symbolic information for the current version of your program has been written to a PROTSYM file or a CSL file. If the program has been recompiled and relinked, the symbolic file must be reloaded. This problem can also occur if your program has been recompiled and the symbolic file updated, but the program has not yet been relinked. If you have correctly loaded the latest symbolic information into a symbolic file, verify that the symbolic file is available to Detector using your installation defaults, your JCL, or a SYMDSN override. If you still cannot determine the cause of this message, Virtual Host Manager. CAPD114W SYMBOLIC FILE READ ERROR-SYMBOLIC INFORMATION MAY BE INCOMPLETE. Reason: An error was detected while attempting to read symbolic information from one of the available symbolic files. Detector processing continues, but symbolic information may be incomplete. Action: Verify that all of your available symbolic files are valid, and that their data set names are specified correctly in your installation defaults, JCL, or CAISYM override statements. Correct the error and rerun the job if necessary. If you still cannot determine the cause of this message, contact CA Technical Support. CAPD115W INTERRUPT OCCURRED IN REGION OR SYSTEM. NO CSECT DUMP WAS PRODUCED. Reason: An interrupt occurred outside of a user program or outside the user region. Processing continues. Action: None. 34 Message Reference Guide CAPxyyyz Messages CAPD116W CSECT LENGTH UNKNOWN, PROCEEDING TO DUMP ENTIRE LOAD MODULE. Reason: Detector was unable to determine the length of a control section, so the entire load module has been dumped instead using a standard "dump" format. Action: None. CAPD117W UNABLE TO LOCATE LOAD MODULE; LOAD MODULE DUMP SUPPRESSED. Reason: Detector was unable to relate an interrupt address with a load module name during a scan of system control blocks (CDE chain queued off the TCB). Processing continues. Action: None. CAPD118W PROCESSING TERMINATED DUE TO INSTALLATION REQUEST. Reason: An entry in the user table CAOCAB80 specified that DETECT equals OFF. A report will not be produced. Action: None. Chapter 2: Messages 35 CAPxyyyz Messages CAPD119W NUMBER OF PARAMETERS PASSED FROM CALLING PROGRAM "aaaaaaaa:nnnn" CONFLICTS WITH THAT EXPECTED BY CALLED PROGRAM "bbbbbbbb:mmmm". Reason: The PARMCHK facility has detected a conflict in the number of parameters being passed. The called program bbbbbbbb has been entered, and Detector has discovered that the program named aaaaaaaa has passed an incorrect number of parameters to bbbbbbbb. The actual PARM counts detected/expected are shown as values n and m. The application continues. After 16 occurrences, the PARMCHK mechanism is disabled. Action: None. CAPD120W PARAMETERS PASSED FROM "aaaaaaaa" TO "bbbbbbbb" CONTAIN INVALID ADDRESS VALUES. Reason: The Detector PARMCHK facility has analyzed the values found in the parameter list passed from aaaaaaaa to bbbbbbbb. Using the addressing mode of the called program, the Execution Monitor and Detector have determined that the address is inaccessible to the called program. The application continues. After 16 occurrences, the PARMCHK mechanism is disabled. Action: None. CAPD121W COBOL CALL STATEMENT FROM PROGRAM "aaaaaaaa" AT OFFSET hhhhhh. Reason: This is a supplemental message associated with the PARMCHK error described in message CAPD119W. If the calling program was COBOL and symbolic information was available to Detector, the CALL statement is displayed immediately following this message. Action: None. 36 Message Reference Guide CAPxyyyz Messages CAPD122W DISPLACEMENT FROM ENTRY POINT OF CALLER TO CALL LOCATION: hhhhhhhh. Reason: This is a supplemental message associated with the PARMCHK error described in CAPD119W. If the calling program was not COBOL, or if no symbolic information was available to Detector, this message is displayed instead of CAPD121W. Action: None. CAPD123I INSTRUCTION LOCATED PRIOR TO THE FIRST PROCEDURE STATEMENT. POSSIBLE ERROR COMPUTING THE SIZE OF A VARIABLE-LENGTH TABLE. Reason: The instruction which corresponds to the indicated program offset is located prior to the first Procedure Division statement in the program and does not correspond to a COBOL source statement. One possible reason for this is that an error occurred while computing the size of a variable-length table. Action: Verify that the DEPENDING ON variables for any variable-length tables are initialized before the tables are referenced. Alternatively, if a CAPD113W message was displayed, indicating that the symbolic file member does not exactly match the program in the executable load module, follow the action specified for that message. CAPD125E ABEND CAUSED BY AN INVALID SUBSCRIPT OR INDEX. Reason: The SUBRNGCK facility has examined the operation exception caused by the use of an invalid subscript. The Detector Abend report displays the INVALID dimension or subscript and the current values of the items associated with the statement causing the abnormal termination. Execution is terminated with a user abend code of U1125, and a complete Detector Abend report is produced. Action: Review the Detector Abend report, correct and recompile the source program, and rerun the job. Chapter 2: Messages 37 CAPxyyyz Messages CAPD128E ABEND CAUSED BY AN INVALID REFERENCE TO RECORD AREA OF DDNAME dddddddd. Reason: The FDCHECK facility has analyzed the base register(s) associated with an abend and determined that the cause of the abend was an invalid reference to the record area of a file defined by the ddname of dddddddd. Examples are attempts to move data into an area before the file is opened or after it is closed. Typically, the original abend is an S0C4. To narrow the possibilities involved in the debugging effort, the abend code is changed into a user abend code of U1128, and a complete Detector Abend report is produced. Action: Review the Detector Abend report, correct and recompile the source program, and rerun the job. CAPD135W INTERCEPTS PROCESSING CANCELLED BECAUSE ESTAE RB AND ABENDING RB DON'T MATCH. Reason: The retry failed in Intercepts processing because the intercepted instruction was not executing under the RB created by Optimizer's ESTAE. This error is most likely to occur when the intercepted instruction is in the input or output routine of an internal sort (and is therefore running under the sort RB). Action: None. CAPD137I CSECT DUMP SUPPRESSED DUE TO EXCLUSION CRITERIA. Reason: The abending CSECT was not displayed in the Detector because it was specifically excluded using the CAOUXMOD option of default options member, CAOUDFRX. Action: None. 38 Message Reference Guide CAPxyyyz Messages CAPD138I INTERRUPT OCCURRED IN REGION OR SYSTEM. DUMPING CSECT FOR CALLING PROGRAM. Reason: An interrupt occurred outside of a user program or outside of the user region. The CSECT dump will be generated for the previously active user program (as indicated in the save area chain). Action: None. CAPD140E INTERNAL ERROR DURING DB2 PROCESSING. DB2 PROCESSING HALTED. Reason: An error occurred in the Detector program which accesses the DB2 catalog. Processing is halted for the DB2 section of the report. Action: Rerun the job with the options DUMP ON and DB2TRACE ON specified in the CAIOPTS DD. Collect all output including JCL, log messages and dump. Contact CA Technical Support. CAPD141E ERROR PROCESSING SQLCODE. RETURN CODE FROM DSNTIAR=rc. Reason: An error occurred while trying to print the message associated with SQLCODE. The return code from DB2 module DSNTIAR is indicated in the message. Action: Rerun the job with the options DUMP ON and DB2TRACE ON specified in the CAIOPTS DD. Collect all output including JCL, log messages, and dump. Contact CA Technical Support. Chapter 2: Messages 39 CAPxyyyz Messages CAPD142W THE PARAMETER LIST FOR THE LAST SQL CALL WAS NOT FOUND. Reason: The parameter list for the last SQL call was not found in the DB2 control block. Action: If an SQL statement has been executed in the application, collect all output (including JCL, log messages, and dump) and Virtual Host Manager. Otherwise, no action is necessary. CAPD143W PROGRAM pppppppp HAS BEEN RECOMPILED SINCE IT WAS LAST BOUND. Reason: The indicated program has been recompiled since the last time that the package or plan containing the program was bound. Action: If you are using a product such as CA Unicenter Bind Analyzer, which allows programs to be changed without rebinding, no action is necessary. Otherwise, rebind the package or plan for the program. CAPD144W UNABLE TO FIND A UNIQUE SQL STATEMENT IN SECTION sssss FOR THE INDICATED STATEMENT TYPE. Reason: The SQL statement number could not be used to find the last SQL statement (because the program was recompiled since the last time it was bound or the statement number was greater than 32767, and was therefore saved in the catalog table as 0). When Detector tried to use the section number and statement type to find the last SQL statement, it found multiple statements of that type in the section. Action: None. 40 Message Reference Guide CAPxyyyz Messages CAPD145W SQL STATEMENT sssss WAS NOT FOUND IN THE DB2 CATALOG. Reason: The indicated SQL statement could not be found in DB2 catalog table SYSSTMT or SYSPACKSTMT. Action: Contact CA Technical Support. CAPD146W PLAN pppppppp WAS NOT FOUND IN THE DB2 CATALOG. Reason: The indicated plan could not be found in the DB2 catalog table SYSPLAN. Action: Collect all output including JCL, log messages, and dump. Contact CA Technical Support. CAPD147I NO OBJECT DEPENDENCIES WERE FOUND FOR PLAN pppppppp. Reason: No entries were found in the DB2 catalog table SYSPLANDEP for the indicated plan. Action: None. CAPD148I NO PACKAGE LIST WAS FOUND FOR PLAN pppppppp. Reason: No entries were found in the DB2 catalog table SYSPACKLIST for the indicated plan. Action: None. Chapter 2: Messages 41 CAPxyyyz Messages CAPD149I NO ACTIVE PACKAGES WERE FOUND FOR PLAN pppppppp. Reason: None of the entries found in the DB2 catalog table SYSPACKLIST for the indicated plan corresponded to programs that were active at the time of the report. Action: None. CAPD150I NO OBJECT DEPENDENCIES WERE FOUND FOR PACKAGE pppppppp. Reason: No entries were found in the DB2 catalog table SYSPACKDEP for the indicated package. Action: None. CAPD151I NO DBRMS WERE FOUND FOR PLAN pppppppp. Reason: No entries were found in the DB2 catalog table SYSDBRM for the indicated plan. Action: None. CAPD152I NO ACTIVE DBRMS WERE FOUND FOR PLAN pppppppp. Reason: None of the entries found in the DB2 catalog table SYSDBRM for the indicated plan corresponded to programs that were active at the time of the report. Action: None. 42 Message Reference Guide CAPxyyyz Messages CAPD153E CHARACTER CONVERSION FAILED: RC = nn, REASON = mm. Reason: An error occurred when converting a string from UTF-8 to EBCDIC. Action: Collect all output including JCL, log messages, and dump. Contact CA Technical Support. CAPD154W CAODSTKN – LOAD OF CAOUDIXR FAILED. Reason: Dynamic symbolic support encountered an error loading module CAOUDIXR. Dynamic symbolic support is not able to populate mismatched symbolic for the abending CSECTs. Action: Ensure that the CA Optimizer/II product load module libraries are correctly defined in your JCL or are defined in your installation's LNKLST. CAPD157W CAOFMAIN – LOAD OF CAODNDVR FAILED. Reason: Dynamic symbolic support encountered an error loading module CAODNDVR. Dynamic symbolic support will not be able to populate mismatched symbolic for the abending CSECTs. Action: Ensure that the CA Optimizer/II product load module libraries are correctly defined in your JCL or are defined in your installation's LNKLST. Chapter 2: Messages 43 CAPxyyyz Messages CAPD158W CAOFMAIN – LOAD OF CAOUDIXR FAILED. Reason: Dynamic symbolic support encountered an error loading module CAOUDIXR. Dynamic symbolic support will not be able to populate mismatched symbolic for the abending CSECTs. Action: Ensure that the CA Optimizer/II product load module libraries are correctly defined in your JCL or are defined in your installation's LNKLST. CAPE001E mmmmmmmm NOT FOUND - INITIALIZATION INCOMPLETE. Reason: An Extended Detector module was not available during initialization of Extended Detector. Action: Ensure that all Extended Detector modules from CAI.CAILIB are available when initializing Extended Detector. CAPE002E INTERCEPT FAILED - INITIALIZATION INCOMPLETE. Reason: The Extended Detector SVC hook could not be inserted. Action: Review all installation procedures. Rerun the job once more. If this message appears again, notify CA Technical Support. 44 Message Reference Guide CAPxyyyz Messages CAPE003I UNABLE TO OBTAIN LOCK. REFRESH WILL CONTINUE WITHOUT LOCK. Reason: Another job was using Extended Detector when an attempt was made to reinitialize. Extended Detector is reinitialized. Action: None. CAPE003W UNABLE TO OBTAIN LOCK. CONTINUE INITIALIZATION WITHOUT LOCK? Reason: Another job was using Extended Detector when an attempt was made to reinitialize. Action: If you reply Y or YES, Extended Detector reinitializes. If you reply N or NO, initialization is terminated. CAPE004I SQA TABLE RESIDES IN CORE AT ADDRESS nnnnnnnn. Reason: This message is for diagnostic purposes only. Action: None. CAPE005I INITIALIZATION COMPLETED. Reason: You have successfully initialized or refreshed the Extended Detector system. Action: None. Chapter 2: Messages 45 CAPxyyyz Messages CAPE006E INTERNAL ABEND ENCOUNTERED. Reason: This message is issued whenever Extended Detector has detected an internal error. Action: Collect all output including JCL, log messages, and dump. Contact CA Technical Support. CAPE007E INTERRUPT AT PSW xxxxxxxx EP=xxxxxxxx R0-R3 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx R4-R7 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx R8-RB xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx RC-RF xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx Reason: The Extended Detector ESTAE has intercepted an internal error. This message indicates the PSW and registers from the time of the error. Action: Collect all output including JCL, log messages, and dump. Contact CA Technical Support. CAPE008E REPORT TERMINATED BECAUSE XXXXXXXXXXXXXXX. Reason: A condition has occurred which has prevented the completion of the Extended Detector. Action: Collect all output including JCL, log messages, and dump. Contact CA Technical Support. 46 Message Reference Guide CAPxyyyz Messages CAPE009E REPORT WAS NOT PRODUCED BECAUSE NO PRB WAS FOUND. Reason: Extended Detector could not find a Program Request Block (PRB) on the RB chain. Action: None. CAPE010E UNABLE TO LOCATE RUNTIME MODULES. INITIALIZATION INCOMPLETE. Reason: A module required for initialization was not found. Action: Ensure that all CA Optimizer/II modules are available when initializing Extended Detector. CAPE011E EXCEPTION ENCOUNTERED IN CAOETSEL. Reason: This message is issued whenever Extended Detector has detected an internal error in module CAOETSEL while attempting to evaluate possible exclusion criteria. Action: Collect all output including JCL, log messages, and dump. Contact CA Technical Support. CAPE013I UNABLE TO OBTAIN LOCK. ABEND HANDLER WILL BE DISABLED WITHOUT LOCK. Reason: Another job was using Extended Detector when an attempt was made to disable it. Extended Detector will be disabled. Action: None. Chapter 2: Messages 47 CAPxyyyz Messages CAPE013W UNABLE TO OBTAIN LOCK. CONTINUE TO DISABLE ABEND HANDLER WITHOUT LOCK? Reason: Another job was using Extended Detector when an attempt was made to disable it. Action: If you reply Y or YES, Extended Detector will be disabled. If you reply N or NO, it will not. CAPE014I ABEND HANDLER IS NOT ACTIVE - NO ACTION WILL BE TAKEN. Reason: An attempt was made to disable Extended Detector support when it was already disabled. Extended Detector remains disabled. Action: None. CAPE015I ABEND HANDLER IS NOW DISABLED. Reason: Extended Detector has been successfully disabled. Action: None. CAPE016W OPTIONS NOT UPDATED BECAUSE MODULE CAOETABL IS NOT AVAILABLE. Reason: An attempt to update CAOETABL was made, but CAOETABL was not available. Action: The Extended Detector options table is not updated. Ensure that CAOETABL is available through STEPLIB, JOBLIB, LINKLIST or LPA and is APF authorized. 48 Message Reference Guide CAPxyyyz Messages CAPE017I ABEND HANDLER IS NOT CURRENTLY ACTIVE - NO ACTION WILL BE TAKEN. Reason: An attempt was made to update the Extended Detector options, but Extended Detector was not initialized on the system. Action: The options are not updated. Your options table will be loaded when you initialize Extended Detector. CAPE018I OPTIONS SUCCESSFULLY UPDATED. Reason: A successful update of CAOETABL has been completed. Action: None. CAPE019I UNABLE TO OBTAIN LOCK. OPTIONS WILL BE UPDATED WITHOUT LOCK. Reason: Another job was using Extended Detector when an attempt was made to update the options table. The Extended Detector options will be updated Action: None. CAPE019W UNABLE TO OBTAIN LOCK, SHOULD TABLE UPDATE CONTINUE WITHOUT LOCK? Reason: Another job was using Extended Detector when an attempt was made to update the options table. Action: If you reply Y or YES, Extended Detector will be updated. If you reply N or NO, it will not. Chapter 2: Messages 49 CAPxyyyz Messages CAPE021E REPORT WAS NOT PRODUCED BECAUSE A NECESSARY MODULE WAS MISSING. Reason: Extended Detector was unable to load CAOCEM00. Action: Ensure that the CA Optimizer/II RTL is available through STEPLIB, JOBLIB, LINKLIST or LPA. CAPE022I jjjjjjjj ssssssss ABENDED taaa IN PROGRAM pppppppp AT OFFSET +oooooo. Reason: Extended Detector has completed a report, but no symbolic information was available for the abending program. Action: Use your report to correct the application. CAPE023I jjjjjjjj pppppppp ABENDED taaa AT ssssssssssssssssssssssssss. Reason: Extended Detector has completed a report, and symbolic information was available for the abending program. Action: Use your report to correct the application. CAPE024E xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Reason: An invalid reply was entered by the operator. Action: Reply Y or N. 50 Message Reference Guide CAPxyyyz Messages CAPE025I jjjjjjjj ssssssss UNHANDLED CONDITION CEEnnnnx RAISED IN PROGRAM pppppppp AT OFFSET +oooooo. Reason: Extended Detector has completed an unhandled LE condition, but no symbolic information was available for the offending program. Action: Use your report to correct the application. CAPE026I jjjjjjjj pppppppp UNHANDLED COND CEEnnnnx AT ssssssssssssssssssssssssssssssssssssssssssssssss Reason: Extended Detector has completed an unhandled LE condition, and symbolic information was available for the offending program. Action: Use your report to correct the application. CAPE027I ABEND REPORT SUPPRESSED DUE TO STOPDD ddname Reason: The indicated DD name was specified in the JCL for the abending job step. The abend report is suppressed. Action: None Chapter 2: Messages 51 CAPxyyyz Messages CAPE028I ABEND REPORT NOT GENERATED DUE TO EXCLUSION CRITERION: keyword value Reason: The abending job step matched an exclusion criterion specified either in the CAOETXCL macro of default member CAOETABL, or in user exit CAOEUSR1. The message indicates the matching criterion. Action: None CAPE029I ABEND REPORT GENERATED REGARDLESS OF EXCLUSION CRITERIA DUE TO EXIT CAUEUSR1 Reason: The abending job step matched inclusion criteria specified in user exit CAOEUSR1. The abend report is generated regardless of whether it matched exclusion criteria specified in the CAOETXCL macro of default member CAOETABL. Action: None CAPE030W ALLOCATE FOR dddddddd FAILED. NETMAN INTERFACE NOT AVAILABLE. LOAD for mmmmmmmm FAILED. NETMAN INTERFACE NOT AVAILABLE. Reason: The specified module could not be loaded or the specified DDNAME could not be dynamically allocated. Action: Ensure that the instructions for using the CA Netman interface in the Installation Guide have been followed and that all installation defaults have been set up correctly. If so, Virtual Host Manager. 52 Message Reference Guide CAPxyyyz Messages CAPE031I RECORD HAS BEEN ADDED TO NETMAN FILE. Reason: A record was added by Extended Detector to the Unicenter CA-Netman database using the Machine Generated Problem Tracking system. Action: The record is now available for review by an authorized Unicenter CA-Netman user. CAPE032W NETMAN INTERFACE FAILED DURING UPDATE. Reason: An error has occurred while attempting to log a record to CA Netman for Machine Generated Problem Tracking. Action: Ensure that the instructions for using the CA Netman interface in the Installation Guide have been followed and that all installation defaults have been set up correctly. If so, Virtual Host Manager. CAPE033W CAOECEEI–LOAD OF CAOEGMSG FAILED. Reason: Language Environment Unhandled Condition support encountered an error loading module CAOEGMSG. LE Unhandled Condition messages will not be retrieved. Action: Ensure that the CA Optimizer/II product load module libraries are correctly defined in your JCL or are defined in your installation's LNKLST. Chapter 2: Messages 53 CAPxyyyz Messages CAPE034W CAOECEEI – CAOEGMSG FAILED. RC = nnnn. Reason: Retrieval of LE messages function failed, where nnnn is the severity code returned by CEEMGET, LE Callable Service. Action: Contact CA Technical Support for assistance. CAPH001I HELP IS NOT AVAILABLE FOR THAT WORD. Reason: COBOL II HELP is not available for the word you specified. Action: Check the spelling of the word, or enter another word. You can use the Reserved Word Locator (selection 1) to locate the word you want. CAPH002I ENTER A LETTER FROM A THROUGH E OR SCROLL THROUGH ALL PANELS. Reason: A character other than A, B, C, D, or E was entered. Action: Enter a valid character, or use the appropriate PF key to scroll through all panels. CAPH003I ENTER A DISPLAYED RESERVED WORD OR SCROLL THROUGH ALL PANELS. Reason: A word that is not displayed on the given panel was entered. Action: Enter a word that is displayed, or use the appropriate PF key to scroll through all panels. 54 Message Reference Guide CAPxyyyz Messages CAPH004I ENTER A LETTER FROM A THROUGH G. Reason: A character other than A, B, C, D, E, F, or G was entered. Action: Enter a valid character. CAPH005I ENTER A LETTER FROM A THROUGH K. Reason: A character was entered other than A, B, C, D, E, F, G, H, I, J, or K. Action: Enter a valid character. CAPH005I ENTER A LETTER FROM A THROUGH C OR SCROLL THROUGH ALL PANELS. Reason: A character other than A, B, or C was entered. Action: Enter a valid character, or use the appropriate PF key to scroll through all panels. CAPH007I ENTER EITHER A OR B. Reason: A character other than A or B was entered. Action: Enter a valid character. Chapter 2: Messages 55 CAPxyyyz Messages CAPH008I ENTER A LETTER FROM A THROUGH G OR SCROLL THROUGH ALL PANELS. Reason: A character other than A, B, C, D, E, F, or G was entered. Action: Enter a valid character, or use the appropriate PF key to scroll through all panels. CAPH009I ENTER A LETTER FROM A THROUGH D. Reason: A character other than A, B, C, or D was entered. Action: Enter a valid character. CAPH010I THE COMMUNICATION SECTION IS NOT SUPPORTED BY VS COBOL II. Reason: The Communication module of the ANS 74 standard is not supported by VS COBOL II. Therefore, HELP is not available for the specified word. Action: None. CAPH011I ENTER A LETTER FROM A THROUGH C. Reason: A character other than A, B, or C was entered. Action: Enter a valid character. 56 Message Reference Guide CAPxyyyz Messages CAPH012I ENTER A LETTER FROM A THROUGH F. Reason: A character other than A, B, C, D, E, or F was entered. Action: Enter a valid character. CAPH013I ENTER A LETTER FROM A THROUGH E. Reason: A character other than A, B, C, D, or E was entered. Action: Enter a valid character. CAPH014I ENTER A CODE DISPLAYED ON THIS PANEL. Reason: A code that is not displayed on this panel was entered. Action: Enter a code displayed on this panel. CAPH015I ENTER A LETTER FROM A THROUGH H. Reason: A character other than A, B, C, D, E, F, G, or H was entered. Action: Enter a valid character. Chapter 2: Messages 57 CAPxyyyz Messages CAPH016I ENTER A LETTER FROM A THROUGH I. Reason: A character was entered other than A, B, C, D, E, F, G, H, or I. Action: Enter a valid character. CAPH017I ENTER A LETTER FROM A THROUGH J. Reason: A character was entered other than A, B, C, D, E, F, G, H, I, or J. Action: Enter a valid character. CAPH018I ENTER A NUMBER FROM 1 THROUGH 3 OR SCROLL THROUGH ALL PANELS. Reason: A character was entered other than 1, 2, or 3. Action: Enter a valid character. CAPH019I INVALID REQUEST. Reason: An invalid request was entered. Action: Enter a valid request. 58 Message Reference Guide CAPxyyyz Messages CAPH020I THE REPORT WRITER IS NOT SUPPORTED BY VS COBOL II. Reason: The Report Writer module of the ANS 74 standard is not supported by VS COBOL II. HELP is not available for the specified word. Action: None. CAPH130I SPECIFY 'STRING' OR 'UNSTRING'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: STRING or UNSTRING. CAPH131I SPECIFY 'GO TO', 'OCCURS', OR 'RECORD CLAUSE OF FD OR SD'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: GO TO or OCCURS, or RECORD CLAUSE of FD or SD. CAPH140I SPECIFY 'AT END', 'DECLARATIVES', OR 'RERUN'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: AT END, DECLARATIVES, or RERUN. Chapter 2: Messages 59 CAPxyyyz Messages CAPH142I SPECIFY 'ON EXCEPTION' OR 'USE'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: ON EXCEPTION or USE. CAPH143I SPECIFY 'EXIT VERB' OR 'EXIT PROGRAM'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: EXIT VERB, or EXIT PROGRAM. CAPH150I SPECIFY 'CLOSE', 'INSPECT', OR 'SAME'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: CLOSE, INSPECT, or SAME. CAPH170I SPECIFY 'OPEN' OR 'USE'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: OPEN or USE. 60 Message Reference Guide CAPxyyyz Messages CAPH171I SPECIFY 'COPY' OR 'UNSTRING'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: COPY or UNSTRING. CAPH172I SPECIFY 'OCCURS' OR 'ORGANIZATION'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: OCCURS or ORGANIZATION. CAPH173I SPECIFY 'OPEN', 'SORT', OR 'USE'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: OPEN, SORT, or USE. CAPH200I SPECIFY 'LABEL RECORD', 'SERVICE LABEL', OR 'USE'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: LABEL RECORD, SERVICE LABEL, or USE. Chapter 2: Messages 61 CAPxyyyz Messages CAPH201I SPECIFY 'INSPECT' OR 'SIGN'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: INSPECT or SIGN. CAPH202I SPECIFY 'LINAGE' OR 'WRITE'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: LINAGE or WRITE. CAPH210I SPECIFY 'ACCESS MODE' 'RECORDING MODE', OR 'WITH DEBUGGING MODE'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: ACCESS MODE, RECORDING MODE, or WITH DEBUGGING MODE. CAPH220I SPECIFY 'IF', 'READ', OR 'SEARCH'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: IF, READ, or SEARCH. 62 Message Reference Guide CAPxyyyz Messages CAPH221I SPECIFY 'CLOSE', 'DISPLAY', OR 'OPEN'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: CLOSE, DISPLAY, or OPEN. CAPH222I SPECIFY 'ENTER THE LETTERS A THROUGH F'. Reason: A character other than A, B, C, D, E, or F was entered. Action: Enter one of the following: A, B, C, D, E, or F. CAPH223I SPECIFY 'MERGE', 'OPEN', 'SORT', OR 'USE'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: MERGE, OPEN, SORT, or USE. CAPH230I SPECIFY 'STRING', 'UNSTRING', OR 'USAGE'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: STRING, UNSTRING, or USAGE. Chapter 2: Messages 63 CAPxyyyz Messages CAPH231I PROCESSING MODE IS TREATED AS A COMMENT BY VS COBOL II. Reason: The PROCESSING MODE clause is treated as a comment by VS COBOL II. HELP is not available for this clause. Action: None. CAPH232I SPECIFY 'EXIT PROGRAM', 'PROGRAM COLLATING SEQUENCE' OR 'PROGRAM-ID'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: EXIT PROGRAM, PROGRAM COLLATING SEQUENCE, or PROGRAM-ID. CAPH240I READY TRACE IS TREATED AS A COMMENT IN VS COBOL II. Reason: The READY TRACE statement is treated as a comment in VS COBOL II. HELP is not available for this statement. Action: None. CAPH241I SPECIFY 'BLOCK CONTAINS', 'DATA RECORDS', OR 'RERUN'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: BLOCK CONTAINS, DATA RECORDS, or RERUN. 64 Message Reference Guide CAPxyyyz Messages CAPH242I SPECIFY 'CLOSE', 'RERUN', OR 'USE'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: CLOSE, RERUN, or USE. CAPH243I SPECIFY 'ACCESS MODE', 'ORGANIZATION', OR 'RELATIVE KEY'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: ACCESS MODE, ORGANIZATION, or RELATIVE KEY. CAPH244I SERVICE RELOAD IS NOT SUPPORTED BY VS COBOL II. Reason: The SERVICE RELOAD statement is not supported by VS COBOL II. HELP is not available for this statement. Action: None. CAPH245I SPECIFY 'COPY', 'INITIALIZE', OR 'INSPECT'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: COPY, INITIALIZE, or INSPECT. Chapter 2: Messages 65 CAPxyyyz Messages CAPH246I RESET TRACE IS TREATED AS A COMMENT IN VS COBOL II. Reason: The RESET TRACE statement is treated as a comment by VS COBOL II. HELP is not available for this statement. Action: None. CAPH247I SPECIFY 'CLOSE' OR 'OPEN'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: CLOSE or OPEN. CAPH248I SPECIFY 'JUSTIFIED (JUST)' OR 'SYNCHRONIZED (SYNC)'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: JUSTIFIED (JUST) or SYNCHRONIZED (SYNC). CAPH250I SPECIFY 'IF' OR 'SEARCH'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: IF or SEARCH. 66 Message Reference Guide CAPxyyyz Messages CAPH251I SPECIFY 'MERGE', 'PROGRAM COLLATING SEQUENCE', OR 'SORT'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: MERGE, PROGRAM COLLATING SEQUENCE, or SORT. CAPH252I SPECIFY 'ACCESS MODE' OR 'ORGANIZATION'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: ACCESS MODE or ORGANIZATION. CAPH253I SPECIFY 'MEMORY SIZE', 'ON SIZE ERROR', OR 'STRING'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: MEMORY SIZE, ON SIZE ERROR, or STRING. CAPH254I SPECIFY 'LABEL RECORD' OR 'USE'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: LABEL RECORD or USE. Chapter 2: Messages 67 CAPxyyyz Messages CAPH255I SPECIFY 'FILE STATUS' OR 'UPSI'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: FILE STATUS or UPSI. CAPH260I SPECIFY 'INSPECT' OR 'UNSTRING'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: INSPECT or UNSTRING. CAPH261I SPECIFY 'OCCURS' OR 'PERFORM'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: OCCURS or PERFORM. CAPH262I READY TRACE AND RESET TRACE ARE TREATED AS COMMENTS BY VS COBOL II. Reason: The READY TRACE and RESET TRACE statements are treated as comments by VS COBOL II. HELP is not available for these statements. Action: None. 68 Message Reference Guide CAPxyyyz Messages CAPH263I SPECIFY 'EVALUATE' OR 'SET'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: EVALUATE or SET. CAPH270I SPECIFY 'CLOSE', 'RERUN', OR 'USE'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: CLOSE, RERUN, or USE. CAPH280I SPECIFY 'PERFORM', RECORD CLAUSE OF FD OR SD, or 'SEARCH'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: PERFORM, RECORD CLAUSE OF FD or SD, or SEARCH. CAPH290I SPECIFY 'BLANK WHEN ZERO', 'EVALUATE', OR 'SEARCH'. Reason: The word you requested is used with the COBOL language elements listed in the message. A clearer indication of which use you want to see is required. Action: Enter one of the following: BLANK WHEN ZERO, EVALUATE, or SEARCH. Chapter 2: Messages 69 CAPxyyyz Messages CAPH300I ENTER A DISPLAYED LANGUAGE ELEMENT OR SCROLL THROUGH THE PANELS. Reason: A language element other than those displayed on the panel was entered. Action: Enter a valid language element or scroll through the panels. CAPH600W member NOT CONVERTED, ALREADY EXISTS ON OUTPUT. Reason: CAOHCNVT has determined that the CLIST being converted already exists in the output library. CAOHCNVT bypasses converting this member and attempts to convert the next member. The program ends with a Return Code of 4. Action: To convert this member, you either have to rename it in the source library (SYSUT1) data set, or rerun CAOHCNVT specifying PARM=REPLACE. CAPH601E member NOT CONVERTED, OUTPUT DIRECTORY FULL. Reason: During an attempt to update the directory of the output CLIST library, the directory became filled. Action: CAOHCNVT terminates processing and ends with a return code of 8. Either reallocate the output library (SYSUT2) with additional directory space, or scratch unused members. 70 Message Reference Guide CAPxyyyz Messages CAPH602E CONVERSION ABORTED, PERMANENT I/O ERROR HAS OCCURRED. Reason: During an attempt to update or read the directory of the output CLIST library, a permanent I/O error occurred. CAOHCNVT aborts with a U1602 abend. Action: Check the allocation of the output library and reallocate it on a different disk if necessary. Rerun the job. CAPH603E CONVERSION ABORTED, OUTPUT LIBRARY UNOPENED. Reason: During an attempt to update the directory of the output CLIST library, the STOW SVC ended with a return code indicating the CLIST library did not open. CAOHCNVT aborts with a U1603 abend. This should not occur since, if the output library does not open, an S0C1 should occur on the first WRITE. This indicates that there may be a probable IOS error. Action: Contact CA Technical Support. CAPH604E member NOT CONVERTED, INSUFFICIENT VIRTUAL STORAGE. Reason: During an attempt to process the directory of the output CLIST library (SYSUT2), the BLDL or STOW routine ended abnormally due to insufficient virtual storage availability. CAOHCNVT ends with a return code of 8. Action: Increase the REGION size on the EXEC or JOB card and resubmit the job. Chapter 2: Messages 71 CAPxyyyz Messages CAPH605I member HAS BEEN SUCCESSFULLY CONVERTED. Reason: CAOHCNVT has successfully converted the named input CLIST library member to variable format and stored it under the same name into the output CLIST library. CAOHCNVT attempts to process the next member (if any). Action: None. CAPH606E synadaf error message text. Reason: An I/O error has occurred while accessing either the input or output CLIST libraries causing the CAOHCNVT SYNAD routine to get control. CAOHCNVT invokes the SYNADAF facility to format an error message, after which it aborts with a U1606 abend. Action: Check the DCB attributes of the two libraries, correct the error, and resubmit the job. CAPI000E Internal error during initialization. Reason: An internal error was detected while attempting to initialize the repository viewer API. This typically indicates that an ISPF environment could not be established. Action: Verify that a valid ISPF environment exists. If you cannot determine the cause of this error, save any output or screen shots and Virtual Host Manager. 72 Message Reference Guide CAPxyyyz Messages CAPI002E is not a valid line command. Reason: A line command was entered that is not supported by the current selection list. Action: Return to the selection list from which this message was displayed, then press HELP to display the help text for the display. The valid line commands for the selection list will be listed in the help text. Enter a valid line command. If you believe that the line command that you entered was valid, Virtual Host Manager. CAPI004E is not a valid command for this screen. Reason: A command was entered on the command line that is not supported by the current display. Action: Return to the screen from which this message was displayed, then press HELP to display the help text for the screen. The valid commands for the screen will be listed in the help text. Enter a valid command. If you believe that the command that you entered was valid, Virtual Host Manager. CAPI005E is only valid while a report is loaded. Reason: A command was entered on the command line that is not supported unless a report has been selected for viewing. Action: Only the TAG (.label), LOCATE, and NOTES commands require an open report to be valid. Enter HELP command-name for more information about any of these commands. If you received this message after entering any other command, Virtual Host Manager. Chapter 2: Messages 73 CAPxyyyz Messages CAPI006E is not a valid command. Reason: An unrecognized command was entered on the command line. Action: Return to the screen from which this message was displayed, then press HELP to display the help text for the screen. The valid commands for the screen will be listed in the help text. Enter a valid command. If you believe that the command that you entered was valid, Virtual Host Manager. CAPI007E Command argument exceeds maximum length of 32 characters Reason: An argument specified for the command exceeds 32 characters. Action: Repeat the command with the correct arguments. If you are not sure about the required arguments for the command, enter HELP command-name for more information. CAPI010E Internal error. Reason: An internal error was detected while the repository viewer was attempting to locate a column header in the current display. Action: Contact CA Technical Support. 74 Message Reference Guide CAPxyyyz Messages CAPI011W No column specified. Reason: A command was entered that requires a column header as an argument, but no column header was provided. Action: Repeat the command with the correct arguments. If you are not sure about the required arguments for the command, enter HELP command-name for more information. CAPI012W Column does not exist. Reason: A command was entered that requires a column header as an argument, but the argument provided does not match any column header for the current display. Action: Repeat the command with the correct column header argument. If you are not sure about the required arguments for the command, enter HELP command-name for more information. CAPI015E Internal error. Reason: An internal error was detected while the repository viewer was attempting to interpret a d line command. Action: Contact CA Technical Support. Chapter 2: Messages 75 CAPxyyyz Messages CAPI016I Delete cancelled. Reason: A delete confirmation pop-up message was displayed in response to a d line command entered on the repository index selection list, and you responded by pressing END to cancel the request. Action: This is an informational message, no action is required. If you intended to delete the report from your repository, repeat the d line command and confirm the deletion by pressing Enter as described in the text of the pop-up message. For more information about confirming a deletion request, enter HELP DELETE or press HELP while the pop-up message is displayed. CAPI017E Error deleting report. Reason: You attempted to delete a report from your repository, but an error was detected and the report could not be deleted. Action: The report may have been deleted by another user after you had entered the viewer. Return to the repository index selection list, then enter REFRESH and press Enter to rebuild the list. If the report still appears in the list, Virtual Host Manager. CAPI018I Delete cancelled. Reason: A report was successfully deleted from your repository in response to a d line command from the repository index selection list. Action: This is an informational message, no action is required. 76 Message Reference Guide CAPxyyyz Messages CAPI021W No search argument specified. Reason: A FIND command was entered on the command line, but no search argument was provided. Action: Repeat the command with the correct arguments. If you are not sure about the required arguments for this command, enter HELP FIND for more information. CAPI022E Internal error. Reason: An internal error was detected while the repository viewer was attempting to execute a FIND request. Action: Contact CA Technical Support. CAPI023W Not found. Reason: A FIND command was entered on the command line, but the search argument was not found. Action: If the search was executed in the forward direction, enter RFIND to resume the search starting from the top of the display. If the search was executed in the backward direction, enter RFIND to resume the search starting from the bottom of the display. If you are not sure about the required arguments for this command, enter HELP FIND for more information. Chapter 2: Messages 77 CAPxyyyz Messages CAPI026W Sort invalid for this display. Reason: A SORT command was entered on the command line, but the current display does not support sorting. Action: Sorting is only allowed on the repository index selection list or a symbolic file member selection list. If you have entered a SORT command from one of these displays and this message appeared, Virtual Host Manager. CAPI027I Sort completed. Reason: This message is displayed in response to a successful SORT command. The current display has been sorted on the contents of the specified column and in the order requested. Action: This is an informational message, no action is required. Enter SORT * to restore the current display to its original order. CAPI030I SetIndex cancelled. Reason: You entered a SETINDEX command to change the name of your repository, but when prompted for a new data set name, you pressed END to cancel the request. Action: This is an informational message, no action is required. If you intended to change the repository data set name, repeat the SETINDEX command, enter a new name in the field provided, and press Enter to complete the command. Enter HELP SETINDEX for more information about this command, or press HELP when prompted for a new repository name. 78 Message Reference Guide CAPxyyyz Messages CAPI035W Cursor not on a data line. Reason: A KEEP command was entered but the cursor was not in a valid position. No change was made to your keep window. Action: If you are attempting to add a data line to your keep window, place the cursor on the data line and repeat the command. Only data lines located below the information and header lines can be added to the keep window. If you are attempting to remove a data line from your keep window, place the cursor on the line within the keep window that you would like to remove and repeat the command. Enter HELP KEEP for more information about this command. CAPI036I Keep window is enabled. Reason: This message is displayed in response to a KEEP ON command. The keep window is displayed, unless it is empty. Action: This is an informational message, no action is required. Enter KEEP OFF to disable the keep window, or enter HELP KEEP for more information about this command. CAPI037I Keep window is disabled. Reason: This message is displayed in response to a KEEP OFF command. The keep window is suppressed, even if it contains data. Action: This is an informational message, no action is required. Enter KEEP ON to enable the keep window, or enter HELP KEEP for more information about this command. Chapter 2: Messages 79 CAPxyyyz Messages CAPI040I Options updated. Reason: This message is displayed when you press END from the report options display to return to the repository index selection list. The repository is updated to reflect the options that you have selected for the report. Action: This is an informational message, no action is required. Use CANCEL instead of END to exit the report options screen without updating the report options in your repository. Enter HELP RPTOPTS or press HELP while the report options screen is displayed for more information about viewing and updating report options. CAPI041E Error updating options. Reason: An error was detected while attempting to update report options in your repository. Action: The report may have been deleted by another user after you had entered the viewer. Return to the repository index selection list, then enter REFRESH and press Enter to rebuild the list. If the report still appears in the list, Virtual Host Manager. CAPI042I Options update cancelled. Reason: You entered a CANCEL command from the report options screen to return to the repository index selection list. Any changes to your report options were discarded. Action: This is an informational message, no action is required. 80 Message Reference Guide CAPxyyyz Messages CAPI045I Notes request cancelled. Reason: You attempted to open the electronic notepad for a report by entering an n line command from the repository index selection list or by entering the NOTES command on the command line, but no existing notes were found in your profile for the report. Because your profile can only hold notes for a limited number of reports, a confirmation is required before a new notepad can be created. When prompted for a confirmation, you pressed END to cancel the request instead of pressing Enter to continue. The request is cancelled, and the notepad is not created. Action: This is an informational message, no action is required. CAPI049W Cursor is not on a valid data field. Reason: A cursor-sensitive command was entered on the command line without any argument, but the cursor was not located on a valid data field. The command fails because no argument can be determined. Action: Repeat the command by specifying a valid argument or position your cursor on a valid data line. CAPI052I Profile restored as of on . Reason: A report which you have already viewed at least once has been selected for viewing again. The viewing environment for this report, including the contents and status of the keep window, have been restored from your profile to its previous state. The time and date appearing in the message indicate the last time this report was exited by your userid. Action: This is an informational message, no action is required. Chapter 2: Messages 81 CAPxyyyz Messages CAPI055I Tag request cancelled. Reason: You entered a TAG or . command to create a bookmark in the current report, but you failed to specify a tag name. When prompted for a name, you responded by pressing END to cancel the request or by leaving the name field blank. The command is cancelled, no bookmark is created. Action: This is an informational message, no action is required. Enter HELP TAG for more information about this command, or repeat the command and press HELP while the pop-up prompt is displayed. CAPI056I Tag added for line number . Reason: This message is displayed in response to a successful TAG or .label command. The new tag name and corresponding line number are displayed in the text of the message. Action: This is an informational message, no action is required. Enter L label at any time in the current session to instantly position the viewer to the current line. Enter HELP TAG or HELP LOCATE for more information about setting and retrieving bookmarks. 82 Message Reference Guide CAPxyyyz Messages CAPI057I Tag replaced for line number . Reason: This message is displayed in response to a successful TAG or .label command, if the label you specified already existed from a previous TAG or .label command. The tag name and line number are displayed in the text of the message. Action: This is an informational message, no action is required. Enter L label at any time in the current session to instantly position the viewer to the current line. Enter HELP TAG or HELP LOCATE for more information about setting and retrieving bookmarks. CAPI058I Locate request cancelled. Reason: You entered a LOCATE command to position the viewer to a bookmark, but you failed to specify a tag name. When prompted for a name, you responded by pressing END to cancel the request or by leaving the name field blank. The command is cancelled, no repositioning is performed. Action: This is an informational message, no action is required. Enter HELP LOCATE for more information about this command, or repeat the command and press HELP while the pop-up prompt is displayed. Chapter 2: Messages 83 CAPxyyyz Messages CAPI059E Tag not found. Reason: You entered a LOCATE command to position the viewer to a bookmark, but the tag name you specified was not recognized. The command is cancelled, no repositioning is performed. Action: Check the spelling of your tag name, then repeat the command. Enter HELP LOCATE for more information about this command, or repeat the command and press HELP while the pop-up prompt is displayed. CAPI060I Print cancelled. Reason: You initiated a print request for one of the following: ■ The current display using a PRINT command. ■ An entire report using a p line command from the repository index selection list. ■ A symbolic listing using a p line command from a symbolic file member selection list. When prompted for specifications, you pressed END to cancel the request. No data was printed. Action: This is an informational message, no action is required. If you intended to complete the print request, repeat the command. When prompted for specifications, complete the fields on the pop-up screen and press Enter to print. For more information about the specifications, press HELP while the pop-up screen is displayed. 84 Message Reference Guide CAPxyyyz Messages CAPI061E Error printing member. Reason: An error occurred while attempting to print a listing from a symbolic (PROTSYM or CSL) file. The listing is not printed. Action: This is an internal error, Virtual Host Manager. CAPI062E Error printing report. Reason: An error occurred while attempting to print one of the following: ■ The current display using a PRINT command. ■ An entire report using a p line command from the repository index selection list. The listing is not printed. Action: This is an internal error, Virtual Host Manager. CAPI063I page(s) printed. Reason: This message is displayed in response to a successful PRINT request. indicates the number of pages printed from the current display. The number of pages is determined by the number of lines printed and the number of lines per page requested. Action: This is an informational message, no action is required. Chapter 2: Messages 85 CAPxyyyz Messages CAPI064I Print was successful. Reason: This message is displayed in response to a successful p line command. The selected report or symbolic listing was printed. Action: This is an informational message, no action is required. CAPI066I Profile updated. Reason: You have successfully completed a PROFILE command or option 5 of the SYM command: Dynamic Symbolic Support for CA Endevor SCM. Your profile variables have been updated. Action: This is an informational message, no action is required. CAPI067I Profile update cancelled. Reason: You pressed END to exit either the PROFILE dialog or the Dynamic Symbolic Support Options window (option 5 of the SYM command). Your profile variables were not updated. Action: This is an informational message, no action is required. If you intended to update the profile, repeat the command. When you have set all of the variables as desired, press Enter to exit the dialog and update your profile with the new settings. 86 Message Reference Guide CAPxyyyz Messages CAPI070W No program name specified. Reason: You entered a VIEW primary command but failed to specify which program name you wanted to view. Action: No listing is displayed for viewing. Enter HELP VIEW for more information about the VIEW command. CAPI071W Symbolic information not found in report. Reason: You entered a VIEW primary command but no symbolic information was found in the report for the specified program. Action: No listing is displayed for viewing. Check that the program name was spelled correctly, and that symbolic information was used for the program when the report was formatted. You may need to add the program listing to a symbolic file, or add the symbolic file to your global or supplemental symbolic file list. Enter HELP VIEW for more information about the VIEW command. CAPI074W Member not found. Reason: You entered a SELECT primary command but the member you selected was not found in the member list. Action: No listing is displayed for viewing. Check that the program name was spelled correctly, and that the member actually exists in the symbolic file. Chapter 2: Messages 87 CAPxyyyz Messages CAPI075W No program name specified Reason: You entered a SELECT primary command but did not specify the name of the program you would like to select for viewing. Action: No listing is displayed for viewing. Enter the command again with a valid program name argument. CAPI075W Dynalloc failed for , rc=, reason= Reason: A dynamic allocation failure occurred. The ddname and return codes from SVC 99 are displayed in the text of the message. Action: Evaluate the return codes from SVC 99 (dynalloc) to determine the cause of the failure. This error is often caused by a pre-existing allocation for the same ddname. If this is the case, free the allocation and try again. If you cannot determine the cause of this error, Virtual Host Manager. CAPI098E Error initializing repository API, rc=nnn. Reason: An internal error was detected while attempting to initialize the repository API. This may indicate one of the following conditions: ■ Insufficient storage was available to load the API modules. ■ One or more API modules could not be located. ■ The license management program was not available. Action: Verify that your session has a sufficient region size, that your product libraries have been made available by LIBDEF or through linklist, and that the CA Common Services for z/OS has been properly installed. If you are still unable to determine the cause of this error, Virtual Host Manager. 88 Message Reference Guide CAPxyyyz Messages CAPI099E Error initializing symbolic API, rc=nnn. Reason: An internal error was detected while attempting to initialize the symbolic API. This may indicate one of the following conditions: ■ Insufficient storage was available to load the API modules. ■ One or more API modules could not be located. Action: Verify that your session has a sufficient region size, and that your product libraries have been made available by LIBDEF or through linklist. If you are still unable to determine the cause of this error, Virtual Host Manager. CAPI100I Repository contains report(s). Reason: This message appears whenever the repository index selection list is initially displayed or updated. This occurs when you: ■ Start a new viewer session. ■ Use the REFRESH command to update the contents of the list. ■ Use the SETINDEX command to select a new repository. indicates the number of reports in the repository, each of which appears in the selection list, sorted in descending order by date. Action: This is an informational message, no action is required. Chapter 2: Messages 89 CAPxyyyz Messages CAPI101W Help file DD is not allocated. Reason: A HELP command was entered but the CAOIHELP DD statement is not properly allocated. Help cannot be displayed. Action: Allocate CAI.CARXHELP using DDNAME CAOIHELP and restart the viewer. CAPI102E Error reading help file. Reason: A HELP command was entered but the CAOIHELP DD statement does not point to the CAI.CARXHELP data set. Action: Free and reallocate CAOIHELP to point to CAI.CARXHELP, then restart the viewer. CAPI103W Help not available for . Reason: A HELP command was entered with an explicitly defined topic name, but no help member was found for that topic. Action: Try one of the following HELP topics: ■ HELP ALL lists all available help topics. ■ HELP MSG lists help topics for CA messages. ■ HELP SCREENS list help topics for viewer screens. ■ HELP COMMANDS list help topics for viewer commands. 90 Message Reference Guide CAPxyyyz Messages CAPI108W Selected entry cannot be . Reason: You have selected an item from the report tree selection list for an expand, collapse, toggle, or explode action. The item that you selected has no subordinate items, so the action cannot be performed. Items that can be expanded, collapsed, or exploded are indicated by + or - in the area between the line number and item description, as follows: ■ + indicates that an item has subordinate items which are not visible, and therefore the item can be expanded or exploded. Use + or / to expand the item or ! to explode it. ■ - indicates that an item has subordinate items which are already visible, and therefore the item can be collapsed. Use - or / to collapse it. Note: An expanded item indicated by - can also be exploded using ! if any of its subordinate items have the + indicator. Action: Select a different item or use a different line command. Chapter 2: Messages 91 CAPxyyyz Messages CAPI109W Selected entry is already . Reason: You have selected an item from the report tree selection list for an expand + or collapse - action. The item that you selected was already expanded or collapsed, so your action cannot be performed. Items which can be expanded, collapsed, or exploded are indicated by + or - in the area between the line number and item description, as follows: ■ + indicates that an item has subordinate items which are not visible, and therefore the item can be expanded or exploded. Use + or / to expand the item or ! to explode it. ■ - indicates that an item has subordinate items which are already visible, and therefore the item can be collapsed. Use - or / to collapse it. Note: An expanded item indicated by - can also be exploded using ! if any of its subordinate items have the + indicator. Action: Select a different item or use a different line command. CAPI111E Error deleting report. Reason: You attempted to delete a report from your repository, but an error was detected and the report could not be deleted. Action: The report may have been deleted by another user after you had entered the viewer. Return to the repository index selection list, then enter REFRESH and press Enter to rebuild the list. If the report still appears in the list, Virtual Host Manager. 92 Message Reference Guide CAPxyyyz Messages CAPI112W Report is locked and cannot be deleted. Reason: You attempted to delete a report from your repository, but the report has been locked and cannot be deleted. Action: The user owning the lock is displayed in the Lock field of the repository index selection list. Contact this user to determine if the report is still needed. If not, use the u line command to unlock the report. CAPI118E Access denied, request=, rc=. Reason: You attempted to access the contents of a repository, but access was denied by your system administrator. The request types are: ■ 5 - Open a report for viewing ■ 9 - Delete a report from the repository ■ 16 - Lock a report to prevent accidental deletion ■ 17 - Unlock a report to allow deletion ■ 21 - Update report options ■ 22 - Print a report The return codes are defined by your system administrator in the custom security exit. Action: Contact your system administrator. Chapter 2: Messages 93 CAPxyyyz Messages CAPI120W Report is already locked. Reason: You attempted to lock a report using an l line command, but the report was already locked. Action: The user owning the lock is displayed in the Lock field of the repository index selection list. Contact this user to determine if the lock is still needed. If not, ask the user to unlock the report, then try again. CAPI121E Lock error, rc=. Reason: An error occurred while you were attempting to lock a report. The report was not locked. Action: This usually indicates that the report was locked or deleted by another job or user after your repository index selection list was initially displayed. Use the REFRESH command to update the contents of the repository index selection list. If the report still appears in the list, and the report has not been locked by another user, this may indicate an internal error. Contact CA Technical Support. CAPI122I Report has been locked. Reason: A report was successfully locked in your repository in response to an l line command from the repository index selection list. Action: This is an informational message, no action is required. 94 Message Reference Guide CAPxyyyz Messages CAPI123W Report is not locked. Reason: You attempted to unlock a report using a u line command, but the report was not locked. Action: This is a user error, the report cannot be unlocked. CAPI124E Unlock error, rc=. Reason: An error occurred while you were attempting to unlock a report. The report was not unlocked. Action: This usually indicates that the report was unlocked or deleted by another job or user after your repository index selection list was initially displayed. Use the REFRESH command to update the contents of the repository index selection list. If the report still appears in the list, and the report is still locked, this may indicate an internal error. Contact CA Technical Support. CAPI125I Report has been unlocked. Reason: A report was successfully unlocked in your repository in response to a u line command from the repository index selection list. Action: This is an informational message, no action is required. Chapter 2: Messages 95 CAPxyyyz Messages CAPI140E Invalid value for , specify . Reason: You entered an invalid value for a report option. The name of the option for which the error was detected and the correct value type for that option are both identified in the text of the message. Action: Enter HELP RPTOPTS to list all of the options and their possible values. Correct the value for the option and press Enter to validate it. CAPI141E Internal Error. Reason: An internal error was detected while you were attempting to update report options. Action: Contact CA Technical Support. CAPI145E Dynalloc failed for , rc=, reason=. Reason: A dynamic allocation failure occurred while you were attempting to display your system installation options using an OPTIONS command. The ddname and return codes from SVC 99 are displayed in the text of the message. Action: Evaluate the return codes from SVC 99 (dynalloc) to determine the cause of the failure. This error is often caused by a pre-existing allocation for the same ddname. If this is the case, free the allocation and try again. If you cannot determine the cause of this error, Virtual Host Manager. 96 Message Reference Guide CAPxyyyz Messages CAPI146E Error writing report, rc=. Reason: An error occurred while you were attempting to display the system installation options. The return code from the options program CAOUOPTS is included in the text of the message. Action: For more information, execute CAOUOPTS in batch using the sample JCL provided in CAI.SAMPJCL or the following JCL model: // JOB //STEP1 //STEPLIB // //SYSPRINT EXEC PGM=CAOUOPTS DD DSN=CAI.CAILIB,DISP=SHR DD DSN=CAI.CAILPA,DISP=SHR DD SYSOUT=* If the return code in batch matches the return code from this message, review the job output for information related to the error. If you cannot determine the cause of this error, contact CA Technical Support. CAPI147E Error opening report. Reason: An error occurred while you were attempting to display the system installation options. The output from CAOUOPTS containing your installation options could not be opened. Action: This probably indicates an internal error. To view your options, execute CAOUOPTS in batch using the sample JCL provided in CAI.CARXJCL or the following JCL model: // JOB //STEP1 EXEC PGM=CAOUOPTS //STEPLIB DD DSN=CAI.CARXLOAD,DISP=SHR //SYSPRINT DD SYSOUT=* If this problem persists, Virtual Host Manager. Chapter 2: Messages 97 CAPxyyyz Messages CAPI199E License Management not installed. Reason: The license management component of CA Common Services for z/OS was not properly installed. Action: Contact CA Technical Support. CAPI201E Dynalloc failed for , rc=, reason=. Reason: A dynamic allocation failure occurred while you were executing the symbolic utilities using a SYM command. The ddname and return codes from SVC 99 are displayed in the text of the message. Action: Evaluate the return codes from SVC 99 (dynalloc) to determine the cause of the failure. This error is often caused by a pre-existing allocation for the same ddname. If this is the case, free the allocation and try again. If you cannot determine the cause of this error, Virtual Host Manager. CAPI202E Invalid symbolic file. Reason: The data set you have entered as a symbolic file is not a valid PROTSYM or CSL file. Action: Correct the data set name and try again. If you cannot determine the cause of this error, Virtual Host Manager. 98 Message Reference Guide CAPxyyyz Messages CAPI203E Symbolic API error, func=, rc=. Reason: An error occurred while attempting to execute a symbolic utility using a SYM command. The function name and return code are provided in the text of this message to assist CA Technical Support with the problem determination. Action: For some function types, this may be caused by an invalid symbolic file. Verify that your symbolic file name is correct. If you still cannot determine the cause of this error, Virtual Host Manager. CAPI204E Error retrieving CSL directory, rc=. Reason: An error occurred while attempting to display a list of members for a CSL file. The return code from program CAOUCSLD is included in the text of this message. Action: For more information, execute CAOUCSLD in batch using the sample JCL provided in CAI.SAMPJCL or the following JCL model: // JOB //STEP1 //STEPLIB // //CAISYM //SYSPRINT EXEC PGM=CAOUCSLD DD DSN=CAI.CAILIB,DISP=SHR DD DSN=CAI.CAILPA,DISP=SHR DD DSN=your.csl.dsn,DISP=SHR DD SYSOUT=* * Note that your installation may use an alternate name for CAISYM. If the return code in batch matches the return code from this message, review the job output for information related to the error. If you cannot determine the cause of this error, contact CA Technical Support. Chapter 2: Messages 99 CAPxyyyz Messages CAPI205E Open failed for . Reason: An error occurred while attempting to execute a symbolic utility using the SYM command. A file required by the utility could not be opened. The ddname identifying the file is included in the text of the message. Action: Contact CA Technical Support. CAPI206E Error printing CSL member, rc=. Reason: An error occurred while attempting to display a listing for a CSL member. The return code from program CAORMAIN is included in the text of this message. Action: For more information, execute CAORMAIN in batch using the sample JCL provided in CAI.SAMPJCL or the following JCL model: // JOB //STEP1 //STEPLIB // //CAISYM //CAIPRINT //CAIPRNT1 //CAIPRNT2 //CAIOPTS PRINTCSL /* EXEC PGM=CAORMAIN DD DSN=CAI.CAILIB,DISP=SHR DD DSN=CAI.CAILPA,DISP=SHR DD DSN=your.csl.dsn,DISP=SHR DD SYSOUT=* DD SYSOUT=* DD SYSOUT=* DD * member-name * Note that your installation may use alternate names for CAISYM, CAIPRINT, CAIPRNT1, CAIPRNT2, and CAIOPTS. If the return code in batch matches the return code from this message, review the job output for information related to the error. If you cannot determine the cause of this error, contact CA Technical Support. 100 Message Reference Guide CAPxyyyz Messages CAPI207I Member deleted from . Reason: This message is displayed in response to a successful deletion of a symbolic file member. The member name and symbolic file dsname are both identified in the text of the message. Action: This is an informational message, no action is required. CAPI208E Error deleting member. Reason: An error occurred while attempting to delete a symbolic file member. The member could not be deleted. Action: This problem can occur if the member was already deleted by another job or user after your member selection list was displayed. If you are deleting from a PROTSYM file, verify that the delete password was entered correctly. If you still cannot determine the cause of this error, Virtual Host Manager. CAPP050E I/O ERROR READING DSCB FOR dddddddd. RERUN JOB. Reason: A nonzero return code was encountered after an attempt to read the specified DSCB. The job is terminated. Action: Correct the DD statement and rerun the job. Chapter 2: Messages 101 CAPxyyyz Messages CAPP051E INSUFFICIENT MAIN STORAGE WITHIN REGION. INCREASE REGION SIZE BY nnnnK. Reason: There was not enough main storage available for optimization. The job is terminated. Action: Increase the region size, and rerun the job. CAPP052E INVALID DEVICE TYPE. Reason: An invalid device type was found (not DASD or tape). The job is terminated. Action: Correct the DD statement and rerun the job. CAPP053E FILE dddddddd BLKSIZE NOT MULTIPLE OF LRECL. Reason: The BLKSIZE for the specified file was not a multiple of LRECL. The job is terminated. Action: Correct the DD statement and rerun the job. CAPP054E SYSLIN DATA SET IS PARTITIONED BUT NO MEMBER NAME WAS SPECIFIED. Reason: The data set in the SYSLIN DD statement is partitioned and a member name is required. Action: The job step is terminated. Correct the JCL by specifying a member name or alternate SYSLIN data set and rerun the job. 102 Message Reference Guide CAPxyyyz Messages CAPP057W DEFAULT BLKSIZE FOR dddddddd (nnnnn) IS NOT A MULTIPLE OF LRECL (mmm). CORRECT YOUR INSTALLATION DEFAULT FOR sssssss. Reason: The default BLKSIZE for the specified DD is not a multiple of the LRECL. The BLKSIZE is set to the LRECL value for this run and processing continues. Action: None required. However, if you want to improve I/O performance for the specified file and prevent this message in the future, set the default BLKSIZE for parameter sssssss in options member CAOUDFOX to a multiple of the LRECL. CAPP060E dddddddd DD STATEMENT MISSING. Reason: The specified DD statement was not found. The job is terminated. Action: Correct the DD statement, and rerun the job. CAPP061E OPEN ERROR ON dddddddd. CHECK THE DD STATEMENT. Reason: Optimizer was unable to open the specified file. The job is terminated. Action: Correct the DD statement and rerun the job. CAPP062E INSUFFICIENT TABLE SPACE FOR tttttttt DURING PHASE pppppppp. INCREASE REGION SIZE BY nnnnK. Reason: There was insufficient main storage for optimization. The job is terminated. Action: Increase the region size and rerun the job. Chapter 2: Messages 103 CAPxyyyz Messages CAPP063E INSUFFICIENT BUFFER SPACE DURING PHASE pppppppp. INCREASE REGION SIZE BY nnnnK. Reason: There was insufficient storage for optimization. The job is terminated. Action: Increase the region size and rerun the job. CAPP064E GETMAIN ABOVE 16M LINE FAILED FOR TABLE tttttttt DURING PHASE pppppppp. RC=nnnn. Reason: There was insufficient storage above the 16M line for optimization. The job is terminated. Action: Increase the region size and rerun the job. If the problem persists, save all listings and JCL and contact CA Technical Support for assistance. CAPP066E A RECURSIVE ENTRY INTO DIAGNOSE HAS OCCURRED. ERROR 1 = nnn, ERROR 2 = mmm. Reason: The region specified is not large enough, or there is no SYSPRINT DD in the JCL. The job is terminated. Action: Verify that there is a large enough region specified. Specify a region of 2048K. If the region is large enough, verify that there is a SYSPRINT DD in the JCL. If problems continue, save all listings and JCL and contact CA Technical Support for assistance. 104 Message Reference Guide CAPxyyyz Messages CAPP077E DIAGNOSE SNAPSHOT REQUESTED. Reason: The Optimizer Phase Request Mask was incorrectly used. Action: If T= was specified on the EXEC statement at the request of CA Technical Support personnel, ignore this message. Otherwise, contact CA Technical Support for assistance. CAPP088E PROGRAM INTERRUPTION DURING PHASE pppppppp. DETAILED DESCRIPTION FOLLOWS. Reason: A program interruption was encountered during optimization. The job is terminated. Error diagnostics are displayed for use by CA Technical Support personnel. Action: Save all listings and JCL, and contact CA Technical Support for assistance. CAPP095W dddddddd HAS BEEN CLOSED. Reason: Probably an incorrect usage of the Optimizer Phase Request Mask. Action: If T= was specified on the PARMLIST at the request of CA Technical Support personnel, ignore this message. Otherwise, contact CA Technical Support for assistance. Chapter 2: Messages 105 CAPxyyyz Messages CAPP099E I/O ERROR ON FILE dddddddd DURING PHASE pppppppp --- DETAILED DESCRIPTION FOLLOWS. Reason: An error was encountered while reading from or writing to the specified file. The job is terminated. Error diagnostics are displayed for use by CA Technical Support personnel. Action: Save all listings and JCL and contact CA Technical Support for assistance. CAPP100E . . .CAPP105E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated. Error diagnostics are displayed for use by CA Technical Support personnel, and the job step is abended. Action: Save all listings and JCL and contact CA Technical Support for assistance. CAPP106W CXREF, MXREF, AND/OR LISTHAS BEEN TURNED OFF BECAUSE XREF WAS NOT PRODUCED BY THE COBOL COMPILER. Reason: CA Optimizer/II requires COBOL XREF to process these options. Optimization of the COBOL II program continues after this warning message is printed. Action: Specify XREF, MXREF, CXREF, and/or LIST on the parameter statement. CAPP107E 106 Message Reference Guide CAPxyyyz Messages CAPP108E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated. Error diagnostics are displayed for use by CA Technical Support personnel, and the job step abends. Action: Save all listings and JCL and contact CA Technical Support for assistance. CAPP109E "ENVIRONMENT DIVISION", "DATA DIVISION" OR "PROCEDURE DIVISION" NOT FOUND. Reason: One or more of these headers, ENVIRONMENT DIVISION, DATA DIVISION or PROCEDURE DIVISION, was not found in the COBOL source listing. Optimizer needs these headers to process the application. Optimization of the COBOL program is terminated. The job step is abended. Action: If COPY SUPPRESS was used to access the copybook containing these headers, remove the SUPPRESS option. If COPY SUPPRESS was not used, contact CA Technical Support for assistance. CAPP110E . . .CAPP114E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated. Error diagnostics are displayed for use by CA Technical Support personnel, and the job step is abended. Action: Save all listings and JCL and contact CA Technical Support for assistance. Chapter 2: Messages 107 CAPxyyyz Messages CAPP115E UNAUTHORIZED USE OF IGYCCAEN RESERVE WORD TABLE. Reason: WORD(CAEN) was specified for a program that is not the CA Optimizer/II demo program. Optimization of the COBOL program terminates. The job step abends. Action: Remove the WORD option or specify an alternate reserve word table. CAPP116E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated. Error diagnostics are displayed for use by CA Technical Support personnel, and the job step is abended. Action: Save all listings and JCL and contact CA Technical Support for assistance. CAPP117E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: Either the LIST offsets or the line numbers of the COBOL program were not in ascending sequence. Action: If the line numbers are out of sequence, either correct the line numbers, or use the compiler NONUMBER option. Retain all JCL and listings and contact CA Technical Support for assistance if the problem still persists. 108 Message Reference Guide CAPxyyyz Messages CAPP118E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated. Error diagnostics are displayed for use by CA Technical Support personnel, and the job step is abended. Action: Save all listings and JCL and contact CA Technical Support for assistance. CAPP119E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A serious internal error occurred during optimization of the COBOL program. Optimization of the COBOL program terminates. Diagnostic information (for use by CA Technical Support personnel) is displayed, and the job step abends. Action: Retain all JCL and listings and contact CA Technical Support for assistance. CAPP120E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: The default IBM VS COBOL II Compiler Options Module, IGYCDOPT, may not reside in the Modified LPA (MLPA) or in the Fixed LPA (FLPA) when CA Optimizer/II is used to optimize VS COBOL II programs. Action: Remove IGYCDOPT from MLPA or FLPA and retry. Chapter 2: Messages 109 CAPxyyyz Messages CAPP121E NO SYSUT5 DD STATEMENT IN JCL. Reason: The SYSUT5 DD statement is missing or incorrectly coded. CA Optimizer/II must have this statement. Optimization of the COBOL program is terminated. The job step is abended. Action: Correct the JCL and rerun the job. CAPP122E UNABLE TO OPTIMIZE PROGRAM. NO OBJECT DECK WAS PRODUCED BY THE COMPILER BECAUSE THE "NOCOMPILE" OPTION WAS SPECIFIED. Reason: The NOCOMPILE option was used, and the return code from the COBOL compiler indicates that no object deck was produced. Optimization of the COBOL program terminates, and the job step abends. Action: None. CAPP123W THIS PROGRAM WILL NOT EXECUTE UNDER THE CMS ENVIRONMENT BECAUSE XCOUNT AND/OR DTECT WAS SPECIFIED. Reason: The program is being compiled under CMS, and XCOUNT or DTECT are on. These options are currently not supported under CMS. However, this program runs under MVS. Optimization of the COBOL program continues without any change. Action: None. 110 Message Reference Guide CAPxyyyz Messages CAPP124W INVALID OR UNRECOGNIZABLE SPECIFICATION OF THE SELECT OPTION. SELECT REQUEST IGNORED. Reason: The Optimizer detected an incorrect or inconsistent SELECT option. The SELECT option is canceled. Optimization of the COBOL program continues. Action: No action required. However, you can find the correct coding of this option in the User Guide. CAPP125W SYM OPTION WAS TURNED OFF BECAUSE THE PROTSYM DD WAS MISSING. Reason: The SYM option was requested, but the PROTSYM DD statement was missing or did not point to a valid PROTSYM file. No symbolic information is saved. Action: Add or correct the PROTSYM DD statement and rerun the job. CAPP126I INCREASED REGION SIZE AND/OR BLOCKED SYSIN WILL IMPROVE PERFORMANCE. Reason: An increased region and/or a blocked SYSIN file decreases the amount of I/O required, thus improving compile and optimize time. Optimization of the COBOL program continues without any change. Action: None. Chapter 2: Messages 111 CAPxyyyz Messages CAPP127E UNSUPPORTED COMPILER RELEASE. Reason: The program was compiled with an unsupported compiler release. Action: Recompile the program with a supported compiler release. CAPP129E LANGUAGE(JAPANESE) NOT SUPPORTED. Reason: LANGUAGE(JA) was specified to the COBOL II compiler. Action: Specify LANGUAGE(UE) or LANGUAGE(EN) and rerun the job. CAPP130E . . .CAPP136E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A severe INTERNAL error has occurred during optimization. The job is terminated. Error diagnostics are displayed for use by CA Technical Support personnel. Action: Save all listings and JCL and contact CA Technical Support for assistance. CAPP139E SOURCE, MAP AND EITHER LIST OR OFFSET COBOL OPTIONS MUST BE SPECIFIED FOR THE POST PROCESSOR. Reason: The listing produced by the COBOL compiler did not include an option required by the COBOL postprocessor. Action: Recompile the program with the required options. 112 Message Reference Guide CAPxyyyz Messages CAPP140W CXREF AND MXREF HAVE BEEN TURNED OFF BECAUSE XREF WAS NOT PRODUCED BY THE COBOL COMPILER. Reason: The listing produced by the COBOL compiler did not include the XREF option. The CXREF and MXREF options have been turned off. Action: None required. If CXREF or MXREF output is needed, recompile the program with the XREF option. CAPP142E . . .CAPP201E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A severE INTERNAL error has occurred during optimization. The job is terminated. Error diagnostics are displayed for use by CA Technical Support personnel. Action: Save all listings and JCL and contact CA Technical Support for assistance. CAPP202ECAPP203E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: An invalid record was encountered while reading the COBOL II object module. The job is terminated. Error diagnostics are displayed for use by CA Technical Support personnel. Action: Save all listings and JCL and contact CA Technical Support for assistance. Chapter 2: Messages 113 CAPxyyyz Messages CAPP204E . . .CAPP210E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: A severE INTERNAL error has occurred during optimization. The job is terminated. Error diagnostics are displayed for use by CA Technical Support personnel. Action: Save all listings and JCL and contact CA Technical Support for assistance. CAPP211E . . .CAPP216E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: Insufficient main storage was available for optimization. The job is terminated. Action: Increase the region size and rerun the job. CAPP217E BATCH COMPILES ARE NOT SUPPORTED. Reason: You compiled your program with one or more other programs. CA Optimizer/II does not support this. Action: Compile your program alone and rerun the job. CAPP218E . . .CAPP220E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: Insufficient main storage was available for optimization. The job is terminated. Action: Increase the region size and rerun the job. 114 Message Reference Guide CAPxyyyz Messages CAPP221E PROGRAM MAXIMUM SEGMENTS EXCEEDED BY nnnn. Reason: Optimizer is unable to process this program because it is too large. The job is terminated. Error diagnostics are displayed for use by CA Technical Support personnel. Action: Save all listings and JCL and contact CA Technical Support for assistance. CAPP222E INSUFFICIENT STORAGE IN TABLE MGTROMWK FOR tttttttt. INCREASE REGION BY nnnnK. Reason: Insufficient storage is available for optimization. The job is terminated. Error diagnostics are displayed for use by CA Technical Support personnel. Action: Save all listings and JCL and contact CA Technical Support for assistance. CAPP230E . . .CAPP240E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: Insufficient storage is available for optimization. The job is terminated. Error diagnostics are displayed for use by CA Technical Support personnel. Action: Save all listings and JCL and contact CA Technical Support for assistance. Chapter 2: Messages 115 CAPxyyyz Messages CAPP241E MAXIMUM SEGMENTS EXCEEDED BY nnnn. Reason: The program is too large to be optimized. It contains more referenced base locators than the Optimizer component is capable of handling. The program, therefore, cannot be optimized by the current CA Optimizer/II product. Action: Contact CA Technical Support for assistance. CAPP242E . . .CAPP344E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated, and the job step is abended. Diagnostic information is displayed for use by CA Technical Support personnel. Action: Retain all JCL and listings and contact CA Technical Support for assistance. CAPP345E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: Not enough segments were allocated for the PROCEDURE DIVISION, or one or more of the segments has become larger than expected. Action: Add LOWER and reoptimize. Note that a problem report should be opened on any abend requiring LOWER. 116 Message Reference Guide CAPxyyyz Messages CAPP346E . . .CAPP350E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated, and the job step is abended. Diagnostic information is displayed for use by CA Technical Support personnel. Action: Retain all JCL and listings and contact CA Technical Support for assistance. CAPP351E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: Not enough segments were allocated for the PROCEDURE DIVISION, or one or more of the segments has become larger than expected. Action: Add LOWER and reoptimize. Note that a problem report should be opened on any abend requiring LOWER. CAPP352E . . .CAPP502E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated, and the job step is abended. Diagnostic information is displayed for use by CA Technical Support personnel. Action: Retain all JCL and listings and contact CA Technical Support for assistance. Chapter 2: Messages 117 CAPxyyyz Messages CAPP503E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: Not enough segments were allocated for the PROCEDURE DIVISION, or one or more of the segments has become larger than expected. Action: Add LOWER and reoptimize. Note that a problem report should be opened on any abend requiring LOWER. CAPP504E . . .CAPP590E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated, and the job step is abended. Diagnostic information is displayed for use by CA Technical Support personnel. Action: Retain all JCL and listings and contact CA Technical Support for assistance. CAPP591W TABLE OVERFLOW WAS ENCOUNTERED DURING PERFORM ANALYSIS. OPTIMIZATION CONTINUED WITH UNOPTIMIZED PERFORM LINKAGE. Reason: An internal table overflow occurred during the perform analysis phase of the CA Optimizer/II. Ordinarily, a table overflow of this type results in a U590 abend. However, because the LOWER option was specified at compile time, or the program ID was added to the LOWER table in the default CSECT, this message is produced rather than the U590 abend. Optimization continues with an unoptimized perform linkage. Action: In certain unusual cases, it is possible for the perform range analyzer to run out of table space. Contact CA Technical Support for an analysis of the problem. If the analysis indicates that the program is optimizeable, it can be recompiled/optimized by using the LOWER option at compile time, or by adding the program ID to the LOWER table in the default CSECT. Be careful when using this option; DO NOT, under any circumstances, use it without first consulting with CA Technical Support. 118 Message Reference Guide CAPxyyyz Messages CAPP592E . . .CAPP608E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated and the job step is abended. Diagnostic information is displayed for use by CA Technical Support personnel. Action: Retain all JCL and listings and contact CA Technical Support for assistance. CAPP609W *** WARNING *** SPECIFYING LOWER MAY CAUSE A REDUCTION IN OPTIMIZATION. Reason: LOWER was specified on the PARMLIST or in the compile time defaults. Optimization resumes but may lose efficiency. Action: None. CAPP610E . . .CAPP629E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated. Action: Diagnostic information is displayed for use by CA Technical Support personnel. The job step is abended. Retain all JCL and listings and contact CA Technical Support for assistance. Chapter 2: Messages 119 CAPxyyyz Messages CAPP630W PROGRAM CONTAINS MORE THAN 1024 UNCOND/UNEXEC STATEMENTS. DISPLAY IS TERMINATED. Reason: An overflow has occurred while attempting to add an entry to table MGTUNTBL because the program contained too many statements which were flagged as UNCOND or UNEXEC. Action: The report of UNCOND and UNEXEC statements will only contain as many entries as were in the table before the overflow occurred. Some statement numbers will not be displayed. CAPP631E . . .CAPP635E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated. Action: Diagnostic information is displayed for use by CA Technical Support personnel. The job step is abended. Retain all JCL and listings and contact CA Technical Support for assistance. CAPP636E TOO MANY SUBRNGCK LIMIT CELLS IN TGT. OPTIMIZATION TERMINATED. Reason: You exceeded an internal limit of the SUBRNGCK option. Your program cannot be Optimized with this option. Action: Remove SUBRNGCK from your options list and rerun the job. 120 Message Reference Guide CAPxyyyz Messages CAPP637W THE LIST OPTION WAS REQUESTED, BUT THE COBOL LIST WAS NOT FOUND. Reason: A COBOL procedure map listing (LIST) is required for the postprocessor to produce a LIST report. Action: If a LIST report is required, recompile the program with the COBOL LIST option. Otherwise, no response is necessary. CAPP638W THE OFFSET OPTION WAS REQUESTED, BUT THE COBOL OFFSET LISTING WAS NOT FOUND. Reason: A COBOL condensed procedure map listing (OFFSET) is required for the postprocessor to produce an OFFSET report. Action: If an OFFSET report is required, recompile the program with the COBOL OFFSET option. Otherwise, no response is necessary. CAPP639E . . .CAPP649E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated. Action: Diagnostic information is displayed for use by CA Technical Support personnel. The job step is abended. Retain all JCL and listings and contact CA Technical Support for assistance. Chapter 2: Messages 121 CAPxyyyz Messages CAPP650E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: CA Optimizer/II has not allocated enough segments for the PROCEDURE DIVISION, and one or more of the segments has become larger than expected. The abend usually occurs while processing an instruction where operand 1 is not addressable off its base register. Action: Add LOWER to the input options specified on the parmlist at compile time. CAPP651E . . .CAPP663E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated. Action: Diagnostic information is displayed for use by CA Technical Support personnel. The job step is abended. Retain all JCL and listings and contact CA Technical Support for assistance. CAPP664ECAPP665E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: CA Optimizer/II has not allocated enough segments for the PROCEDURE DIVISION, and one or more of the segments has become larger than expected. The abend usually occurs while processing an instruction where operand 1 is not addressable off its base register. Action: Add LOWER to the input options specified on the parmlist at compile time. 122 Message Reference Guide CAPxyyyz Messages CAPP666E . . .CAPP739E UNABLE TO CONTINUE PROCESSING PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated. Action: Diagnostic information is displayed for use by CA Technical Support personnel. The job step is abended. Retain all JCL and listings and contact CA Technical Support for assistance. CAPP740E "SERVICE LABEL" DOES NOT IMMEDIATELY FOLLOW A CALL VERB. Reason: The Optimizer found a SERVICE LABEL statement that does not immediately follow a CALL verb. The Optimizer does not allow any verbs or paragraph names between these two verbs. The application program execution is terminated. Action: For additional help, see the chapter "Special Usage Considerations" in the Installation Guide. CAPP741E . . .CAPP743E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated and the job step is abended. Action: Diagnostic information is displayed for use by CA Technical Support personnel. Retain all JCL and listings and contact CA Technical Support center for assistance. Chapter 2: Messages 123 CAPxyyyz Messages CAPP744E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: The compiler has used at least one of the registers 6 through 10 as a work register. Action: To optimize the program, add the compiler library and at least onE NON APF-authorized library to the compile time STEPLIB DD. or Add the following statements to the bottom of the program's Linkage Section: 01 LS-01 PIC X(01). 01 LS-02 PIC X(01). 01 LS-03 PIC X(01). Add the following statement immediately after any one STOP RUN or GOBACK in the Procedure Division: MOVE SPACES TO LS-01 LS-02 LS-03. If this problem is not corrected by the action listed above, retain all JCL and listings and contact CA Technical Support for assistance. CAPP745E . . .CAPP760E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated, and the job step is abended. Action: Diagnostic information is displayed for use by CA Technical Support personnel. Retain all JCL and listings and contact CA Technical Support for assistance. 124 Message Reference Guide CAPxyyyz Messages CAPP761E SEGMENTED COBOL PROGRAMS ARE NOT SUPPORTED. Reason: CA Optimizer/II does not support segmented COBOL programs. The program cannot be optimized. Action: Specify NOCOPT and rerun. CAPP762E . . .CAPP766E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated, and the job step is abended. Action: Diagnostic information is displayed for use by CA Technical Support personnel. Retain all JCL and listings and contact CA Technical Support for assistance. CAPP769E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A serious internal error has occurred during optimization of the COBOL program. Optimization of the COBOL program is terminated, and the job step is abended. Action: Diagnostic information is displayed for use by CA Technical Support personnel. Retain all JCL and listings and contact CA Technical Support for assistance. Chapter 2: Messages 125 CAPxyyyz Messages CAPP770W UNABLE TO OPEN STATISTICS FILE. CHECK THE STATS DD CARD. Reason: This message is issued if an error was encountered when trying to open the STATS data set. Processing continues, but the STATS file is not updated. Action: Check the CAISTATS DD statement in your JCL. Rerun the job, if necessary. CAPP771W STATISTICS INFORMATION FILE DAMAGED. FILE MUST BE REINITIALIZED. Reason: The statistics file has been damaged and must be rebuilt. Processing continues; however, the STATS file is not updated. Action: Rebuild or restore your STATS file. CAPP772W A PERMANENT I/O ERROR HAS OCCURRED ON THE STATS FILE. FILE MUST BE REINITIALIZED. Reason: An unrecoverable I/O error has occurred while attempting to write the STATS file. Processing continues, but the STATS file is not updated. Action: Rebuild or restore your STATS file. CAPP773I STATISTICS FILE HAS BEEN SUCCESSFULLY REFORMATTED. Reason: The statistics file has been successfully reformatted. Action: None. 126 Message Reference Guide CAPxyyyz Messages CAPP774I STATS DD STATEMENT MISSING. NO STATISTICS WERE RECORDED. Reason: The CAISTATS DD is not specified in the JCL. No optimization statistics were recorded for this compile. Action: None required. However, if you would like to have optimization statistics recorded, add a CAISTATS DD to your JCL and recompile. CAPP777W THE EOS compile time option is no longer supported and was ignored. Reason: You specified the EOS option at compile time when optimizing a program. The EOS compile time option is no longer supported. Programs previously compiled with the EOS option can continue to execute under the EOS run time, which is still supported in this release. Action: The EOS option is ignored. CAPP780I nnnnn BYTES SHOULD BE RESERVED DURING EXECUTION FOR COUNT TABLES. Reason: XCOUNT was specified on the PARMLIST or in CAOUDFOM. Action: Reserve the number of bytes indicated at execution time. Chapter 2: Messages 127 CAPxyyyz Messages CAPP781I SYMBOLIC POST-PROCESSING OUTPUT FOR PROGRAM FOLLOWS. Reason: The SYM option was specified when this program was compiled. Output from the symbolic postprocessor IN25COB2 follows this message. Action: None. CAPP782I RELEASE OR RETURN VERB FOUND. PERFORM RANGE TABLE MAY CONTAIN MISLEADING INFORMATION. Reason: If a program contains a release or return verb within the input or output procedure of a sort verb and an error occurs, control is passed back to the instruction immediately following the sort verb. (See VS COBOL II Application Programming Guide pp. 123-124.) During optimization, an implicit branch is generated to represent a possible transfer of control from the release/return verb back to the instruction following the sort. CA Optimizer/II sees this as illegally exiting a perform range. Starting with the destination of the implicit branch, all perform range exits which follow may be flagged as possible fall through. Consequently, recursive call from and branch out to conditions can occur. Action: None. CAPP800E . . .CAPP805E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A severE INTERNAL error has occurred during optimization. The job is terminated. Action: Error diagnostics are displayed for use by CA Technical Support personnel. Save all listings and JCL and contact CA Technical Support for assistance. 128 Message Reference Guide CAPxyyyz Messages CAPP807E . . .CAPP857E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A severE INTERNAL error has occurred during optimization. The job is terminated. Action: Error diagnostics are displayed for use by CA Technical Support personnel. Save all listings and JCL and contact CA Technical Support for assistance. CAPP858I ONE OR MORE "EXEC CICS" STATEMENTS REQUIRED "WORST-CASE" HANDLE PROCESSING.' Reason: CA Optimizer/II has reached a limit on processing one or more EXEC CICS statements. Worst-case HANDLE processing was used on these statements to prevent excessive CPU usage at optimize time. The list of CICS calls receiving the worst-case HANDLE processing appears at the end of the source program listing. Action: None. CAPP859E . . .CAPP889E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: A severE INTERNAL error has occurred during optimization. The job is terminated. Action: Error diagnostics are displayed for use by CA Technical Support personnel. Save all listings and JCL and contact CA Technical Support for assistance. Chapter 2: Messages 129 CAPxyyyz Messages CAPP890E UNABLE TO CONTINUE PROCESSING THIS PROGRAM. Reason: An overflow condition has occurred for an internal CA Optimizer/II table. Optimization of the COBOL program is terminated and the job step is abended. Action: Increase the region for the job step and rerun the job. CAPP999W INSUFFICIENT STORAGE AVAILABLE TO PRODUCE COMPILED LISTING. Reason: At the time that an error was detected by CA Optimizer/II, there was insufficient storage to continue with normal diagnostic displays. The unoptimized compiler listing was not produced. Action: This is a warning. The compiler diagnostics can still be examined if the TERM option was in effect. Correct the source errors and rerun the job. CAPR300W CSECT xxxxxxxx HAS NO COUNTS OR TIMINGS. Reason: Count or timing data is not available for CSECT xxxxxxxx. None of the Analyzer reports can be produced unless either counts or timings are available. Action: Check compile and execution steps. Ensure that XTIME and XCOUNT are specified. 130 Message Reference Guide CAPxyyyz Messages CAPR301W CSECT xxxxxxxx DOES NOT HAVE PROCDIV OR SOURCEMAP. IT CANNOT PRODUCE A CROSS-REFERENCE REPORT. Reason: PROCDIV or SOURCEMAP must be specified to produce an Execution Count Cross-Reference report. Action: Specify PROCDIV or SOURCEMAP for those programs for which the Execution Count Cross-Reference reports are requested. CAPR302W CSECT xxxxxxxx HAS NO COUNTS AND CANNOT PRODUCE A CROSS REFERENCE REPORT. Reason: Count measurement data is not available for CSECT xxxxxxxx. Action: Specify the XCOUNT parameter at both compile time and execution time to collect count measurement data. CAPR303W CSECT xxxxxxxx HAS NO TIMINGS AND CANNOT PRODUCE AN INSTRUCTION MAP. Reason: Timing data is not available for CSECT xxxxxxxx INSTRMAP report. Action: Check the execution step. The XTIME parameter must be specified at execution time to invoke timings. Chapter 2: Messages 131 CAPxyyyz Messages CAPR312W NO SYMBOLIC INFORMATION FOUND FOR PROGRAM "PPPPPPPP". Reason: Analyzer/Reporter is attempting to retrieve symbolic information for a program, but no information was found in any of the available PROTSYM or CSL files. Missing symbolic information usually results in termination of the requested report generation. Action: First, verify that the symbolic information has been written to a PROTSYM file or a CSL file. Then verify that the symbolic file is available to Analyzer/Reporter using your installation defaults, your JCL, or a SYMDSN override. If you still cannot determine the cause of this message, contact CA Technical Support. CAPR313E ERROR SEARCHING SYMBOLIC FILE DIRECTORY. Reason: PossiblE INTERNAL error. Action: Save all output materials and contact CA Technical Support. CAPR314E TIMSV DATA ABSENT. NO FURTHER ANALYZER PROCESSING WILL BE PERFORMED IN THIS RUN. Reason: CAITIMSV contains the count and timing measurement data. When this is not available, Analyzer processing cannot continue. The most likely cause of this problem is that no program in the application was compiled/optimized with XCOUNT or XTIME. Action: Check to ensure that there is a program in the application that was compiled/optimized with XCOUNT and/or XTIME. If this is not the case, contact CA Technical Support for assistance. 132 Message Reference Guide CAPxyyyz Messages CAPR315E TIMSV FILE COULD NOT BE OPENED. Reason: CAITIMSV file OPEN failed. Action: Check the CAITIMSV DD statement in the JCL. If the solution is not apparent, contact CA Technical Support for assistance. CAPR316E REGION SIZE IS TOO SMALL. ANALYZER UNABLE TO OBTAIN 25K WORK AREA. Reason: Analyzer was unable to obtain a 25K minimum work area. Processing cannot continue. Action: Rerun the job with a larger region size for the Analyzer Reporter. CAPR317E TIMSV FILE BLKSIZE nnnnn INVALID. Reason: BLKSIZE is not a multiple of 20. Action: Specify BLKSIZE as a multiple of 20 and rerun the job. CAPR318E ERROR READING SYMBOLIC INFORMATION FOR PROGRAM . Reason: Possible internal error. Action: Save all output materials and Virtual Host Manager. Chapter 2: Messages 133 CAPxyyyz Messages CAPR319W NO MATCHING SYMBOLIC INFORMATION FOR CSECT xxxxxxxx. SYMBOLIC DATE mmm dd, yyyy xx.xx.xx does not match TIMSV date mmm dd, yyyy xx.xx.xx. Reason: The TIMSV file contains data collected from an executable for which no matching symbolic information was available to Analyzer/Reporter. For SOURCEMAP reports, the newest symbolic information will be used, but no timings data will be merged onto the report. For INSTRMAP reports, the date and time from the latest executable version will be reported. Action: First, verify that the symbolic information for the current version of your program has been written to a PROTSYM file or a CSL file. If the program has been recompiled and relinked, the symbolic file must be reloaded. This problem can also occur if your program has been recompiled and the symbolic file updated, but the program has not yet been relinked. If you have correctly loaded the latest symbolic information into a symbolic file, verify that the symbolic file is available to Analyzer/Reporter using your installation defaults, your JCL, or a SYMDSN override. If you still cannot determine the cause of this message, contact CA Technical Support. CAPR320W CSECT xxxxxxxx SYMBOLIC DATE mmm dd,yyyy xx.xx.xx HAS NO TIMINGS FOR SOURCEMAP. Reason: A SOURCEMAP report was requested for CSECT xxxxxxxx, but the TIMSV file contains data collected from an executable for which no matching symbolic information was available to Analyzer/Reporter. The SOURCEMAP report does not contain any timings information. Action: First, verify that the symbolic information for the current version of your program has been written to a PROTSYM file or a CSL file. If the program has been recompiled and relinked, the symbolic file must be reloaded. This problem can also occur if your program has been recompiled and the symbolic file updated, but the program has not yet been relinked. If you have correctly loaded the latest symbolic information into a symbolic file, verify that the symbolic file is available to Analyzer/Reporter using your installation defaults, your JCL, or a SYMDSN override. If you still cannot determine the cause of this message, contact CA Technical Support. 134 Message Reference Guide CAPxyyyz Messages CAPR321E CSECT xxxxxxxx SYMBOLIC INFORMATION IS INCOMPLETE. Reason: The symbolic information for CSECT xxxxxxxx is incomplete. Action: Reload the program listing into the symbolic file. If the program was CA-optimized, recompile/optimize the program using the SYM option to update your PROTSYM file, then relink the program and ensure that the updated PROTSYM file is available. If the program was not CA-optimized, reload the listing using the appropriate postprocessor. If you still cannot determine the cause of this message, Virtual Host Manager. CAPR322E CSECT xxxxxxxx SYMBOLIC INFORMATION CONTAINS NO LISTING DATA. Reason: An unexpected end of file was detected while reading the symbolic information for CSECT xxxxxxxx. Action: Reload the program listing into the symbolic file. If the program was CA-optimized, recompile/optimize the program using the SYM option to update your PROTSYM file, then relink the program and ensure that the updated PROTSYM file is available. If the program was not CA-optimized, reload the listing using the appropriate postprocessor. If you still cannot determine the cause of this message, Virtual Host Manager. CAPR323E CSECT xxxxxxxx SYMBOLIC INFORMATION CONTAINS ERRORS. Reason: An error was detected while reading the symbolic information for CSECT xxxxxxxx. Action: Reload the program listing into the symbolic file. If the program was CA-optimized, recompile/optimize the program using the SYM option to update your PROTSYM file, then relink the program and ensure that the updated PROTSYM file is available. If the program was not CA-optimized, reload the listing using the appropriate postprocessor. If you still cannot determine the cause of this message, Virtual Host Manager. Chapter 2: Messages 135 CAPxyyyz Messages CAPR324W CSECT xxxxxxxx HAS NO TIMINGS FOR SOURCEMAP. Reason: No timings samples were taken for CSECT xxxxxxxx SOURCEMAP Report. Samples were taken for the load module containing this CSECT but none fell within this CSECT. Action: Check the execution step. CAPR325W CSECT xxxxxxxx HAS NO TIMING SAMPLES AND CANNOT PRODUCE AN INSTRMAP REPORT. Reason: Timings data is not available for CSECT xxxxxxxx INSTRMAP report. Action: Check the execution step. The XTIME parameter must be specified at execution time to invoke timings. CAPR326W CSECT xxxxxxxx HAS INSUFFICIENT SAMPLES TO PRODUCE INSTRMAP REPORT. Reason: For a single execution, the TOTAL SAMPLES value on the Run Summary report should be approximately 5000 samples. If the number of samples is much less, increase it to produce valid data for the INSTRMAP report. Action: Reduce the TIME option on the JOB card to match, more closely, the actual execution time of the job, or accumulate samples by executing multiple runs, and concatenate the information in the CAITIMSV file. Each of these will increase the number of samples in the CAITIMSV file. 136 Message Reference Guide CAPxyyyz Messages CAPR327W CSECT xxxxxxxx IS AN INVALID CSECT NAME AND HAS BEEN IGNORED. Reason: An invalid CSECT name was encountered during Analyzer Report processing. Action: Correct the invalid CSECT name and rerun the job. If you still cannot determine the cause of this message, contact CA Technical Support. CAPR329W CSECT xxxxxxxx SYMBOLIC DATE mmm dd,yyyy xx.xx.xx HAS NO COUNTS FOR SOURCEMAP. Reason: A SOURCEMAP report was requested for CSECT xxxxxxxx, but the TIMSV file contains data collected from an executable for which no matching symbolic information was available to Analyzer/Reporter. The SOURCEMAP report does not contain any counts information. Action: First, verify that the symbolic information for the current version of your program has been written to a PROTSYM file or a CSL file. If the program has been recompiled and relinked, the symbolic file must be reloaded. This problem can also occur if your program has been recompiled and the symbolic file updated, but the program has not yet been relinked. If you have correctly loaded the latest symbolic information into a symbolic file, verify that the symbolic file is available to Analyzer/Reporter using your installation defaults, your JCL, or a SYMDSN override. If you still cannot determine the cause of this message, contact CA Technical Support. Chapter 2: Messages 137 CAPxyyyz Messages CAPR330W NO MATCHING SYMBOLIC INFORMATION FOR CSECT xxxxxxxx. SYMBOLIC DATE mmm dd, yyyy xx.xx.xx does not match TIMSV date mmm dd, yyyy xx.xx.xx. Reason: The TIMSV file contains data collected from an executable for which no matching symbolic information was available to Analyzer/Reporter. For SOURCEMAP reports, the newest symbolic information will be used, but no counts data will be merged onto the report. For INSTRMAP reports, the date and time from the latest executable version will be reported. Action: First, verify that the symbolic information for the current version of your program has been written to a PROTSYM file or a CSL file. If the program has been recompiled and relinked, the symbolic file must be reloaded. This problem can also occur if your program has been recompiled and the symbolic file updated, but the program has not yet been relinked. If you have correctly loaded the latest symbolic information into a symbolic file, verify that the symbolic file is available to Analyzer/Reporter using your installation defaults, your JCL, or a SYMDSN override. If you still cannot determine the cause of this message, contact CA Technical Support. CAPR331W xxxxxxxx PROGRAM-ID NOT THE SAME AS CSECT NAME. Reason: The program ID does not match the CSECT name; these two items must match to produce Analyzer source reports. Action: Ensure that the names match. Otherwise, you get an Analyzer INSTRMAP report. CAPR332W CSECT xxxxxxxx DETAIL REPORTS WILL CONSOLIDATE DATA FROM DIFFERENT LOAD MODULES. Reason: This message alerts you that the report represents a consolidation of more than one execution. Action: None. 138 Message Reference Guide CAPxyyyz Messages CAPR333W TIMSV FILE FOR JOB xxxxxxxx IS INCOMPLETE. Reason: Not all of the expected timing measurement information appears in the CAITIMSV. Action: Check the execution step for any abnormal completions, and rerun the job. For assistance, contact Technical Support at http://ca.com/support. Chapter 2: Messages 139 CAPxyyyz Messages CAPR334E . . .CAPR338E INTERNAL ERROR CONDITION DETECTED. CONTACT CA. Reason: A serious internal error occurred during Analyzer reporter processing of the COBOL program. Analyzer processing of the COBOL program terminates. Diagnostic information for use by CA Technical Support personnel is displayed. The job step abends. Action: Retain all JCL and listings and contact CA Technical Support for assistance. CAPR339E MAXIMUM WORKSPACE EXCEEDED. CANNOT PROCESS REQUESTED QUANTITY OF INPUT/OUTPUT. Reason: The internal sort routine ran out of space. The allowable maximum working space has been exceeded. Action: Rerun the job with fewer report requests. CAPR340E WORKSPACE EXCEEDED. PLEASE INCREASE REGION BY UP TO xxxx K. Reason: The internal sort routine ran out of space. Action: Increase the region size, or reduce the number of reports requested. 140 Message Reference Guide CAPxyyyz Messages CAPR341E . . .CAPR436E INTERNAL ERROR CONDITION DETECTED. CONTACT CA. Reason: A serious internal error occurred during Analyzer reporter processing of the COBOL program. Analyzer processing of the COBOL program terminates. Diagnostic information to be used by CA Technical Support personnel is displayed. The job step abends. Action: Retain all JCL and listings and contact CA Technical Support for assistance. CAPR441W xxxxxxxx MUST PRECEDE yyyyyyyy, FOUND zzzzzzzz. yyyyyyyy IS IGNORED. Reason: An input statement was ignored because the expected xxxxxxxx was not found. Action: Review the edited input. Rerun the job with the correct input if necessary. CAPR442W xxxxxxxxxxxxxxxxxxx IS NOT RECOGNIZED AND WILL BE IGNORED. Reason: An input string was not recognized and will be ignored. Action: Review the edited input. Rerun the job with the correct input if necessary. CAPR443W OPTS FILE IS EMPTY OR OMITTED -- DEFAULT VALUES ASSUMED. Reason: The input parameter file has no data. The default values are used. Action: Review the default values. Rerun the job if necessary. Chapter 2: Messages 141 CAPxyyyz Messages CAPR444W BLANKS ARE ILLEGAL WITHIN A SUBLIST. SUBLIST HAS BEEN TERMINATED IN ERROR. Reason: A blank was found in a parentheses-enclosed list. The sublist was terminated by replacing the first blank with a right parenthesis. Any remaining data is ignored. Action: Review the edited input. Rerun the job with the correct input if necessary. CAPR445W CARD ENDED WITHOUT TERMINAL QUOTE. ONE IS ASSUMED. Reason: Character strings are not permitted to extend across statements. A beginning quote was found without a corresponding ending quote. An ending quote was supplied in column 73. Action: Review the edited input. Rerun the job with the correct input if necessary. CAPR446W RIGHT PARENTHESES ARE ILLEGAL EXCEPT TO TERMINATE A SUBLIST. Reason: A right parenthesis was found without a corresponding left parenthesis. The right parenthesis was ignored. Action: Review the edited input. Rerun the job with the correct input if necessary. CAPR447W LEFT PARENTHESES ARE ILLEGAL EXCEPT TO START A SUBLIST. Reason: A left parenthesis was found within a sublist. Multiple levels of parentheses are not allowed. The left parenthesis is ignored. Action: Review the edited input. Rerun the job with the correct input if necessary. 142 Message Reference Guide CAPxyyyz Messages CAPR448W IMPROPER USAGE OF RESERVED WORD xxxxxxxx, WILL BE REJECTED. Reason: xxxxxxxx is used in the wrong context or follows an error in a preceding keyword. xxxxxxxx is ignored. Action: Review the edited input. Rerun the job with the correct input if necessary. CAPR449W xxxxxxxx INVALID OPERAND FOR yyyyyyyy, KEYWORD REJECTED. Reason: xxxxxxxx is not a valid subparameter of keyword yyyyyyyy. The keyword is rejected. Action: Review the edited input. Rerun the job with the correct input if necessary. CAPR450W xxxxxxxx REQUIRES yyyyyyyy, FOUND zzzzzzzz. KEYWORD IGNORED. Reason: The keyword xxxxxxxx is ignored because the expected yyyyyyyy was not found. Action: Review the edited input. Rerun the job with the correct input if necessary. CAPR451W SUBLIST LIMIT OF kkkkkkkk (nnnn) HAS BEEN EXCEEDED. EXCESSIVE ENTRIES WILL BE IGNORED. Reason: Keyword kkkkkkkk has a maximum of nnn subparameters and that number was exceeded. Excess entries are ignored. Action: Review the edited input. Rerun the job with the correct input if necessary. Chapter 2: Messages 143 CAPxyyyz Messages CAPR452W xxxxxxxx TOO LONG FOR yyyyyyyy. KEYWORD REJECTED. Reason: xxxxxxxx is too long for keyword yyyyyyyy. The keyword is rejected. Action: Review the edited input. Rerun the job with the correct input if necessary. CAPR453W xxxxxxxx TOO LONG FOR yyyyyyyy. VALUE TRUNCATED. Reason: Value xxxxxxxx is too long for keyword yyyyyyyy. Value xxxxxxxx is truncated to the correct length. Action: Review the edited input. Rerun the job with the correct input if necessary. CAPR499E INTERNAL ERROR CONDITION DETECTED. CONTACT CA. Reason: A serious internal error occurred during Analyzer reporter processing of the COBOL program. Analyzer processing of the COBOL program terminates. Diagnostic information is displayed for CA Technical Support personnel. The job step abends. Action: Retain all JCL and listings and contact CA Technical Support for assistance. CAPT005W dddddddd WAS LEFT OPEN BY mmmmmmmm AND HAS BEEN CLOSED. Reason: A file was left open by the compiler and has been closed. Action: None. 144 Message Reference Guide CAPxyyyz Messages CAPT006E UNSUPPORTED COMPILER RELEASE. Reason: The compiler specified in the JCL is not supported. Action: Change the Compiler Library in the JCL and rerun the job. CAPT011E CAOTSCAN ABEND REQUESTED. Reason: A user specified PARM='SCAB' on the EXEC statement. The job terminates. Action: Eliminate this error by removing PARM='SCAB' from the EXEC statement. CAPT012E dddddddd DD STATEMENT MISSING. Reason: The specified DD statement was missing from the JCL. Action: Ad the DD statement to the JCL and rerun the job. CAPT013E INVALID SPECIFICATION OF THE "EXIT" OPTION. Reason: The EXIT option was specified incorrectly on the PARM card. Action: Correct EXIT option on the PARM card in the JCL and rerun the job. Chapter 2: Messages 145 CAPxyyyz Messages CAPT016E . . .CAPT018E MESSAGE ERROR: (FLAGS) nn (SEQ) xx (MSG) yyyy (RET) zzzzzzzz. Reason: Internal message options were erroneous. Action: Contact CA Technical Support after recording the four hexadecimal codes, nn, xx, yyyy, and zzzzzzzz. CAPT020I PROGRAM NOT OPTIMIZED DUE TO SOURCE ERRORS. PROCEEDING WITH UNOPTIMIZED SOURCE LISTING. Reason: The COBOL return code is greater than the COBCC value. The job terminates and an unoptimized source listing is supplied as requested. Action: Correct any COBOL source errors and rerun the job. CAPT024E UNABLE TO OPEN dddddddd FILE. CHECK THE DD STATEMENT. Reason: CA Optimizer/II is unable to open the SYSPRINT or SYSUT7 file. The job terminates. Action: Check the SYSPRINT and SYSUT7 DD statements and rerun the job. CAPU001E SYSPRINT DD STATEMENT MISSING OR INVALID. Reason: The SYSPRINT DD statement was not specified correctly. Action: Correct the SYSPRINT DD statement in the JCL and rerun the job. 146 Message Reference Guide CAPxyyyz Messages CAPU002E LIBRARY DD STATEMENT MISSING. Reason: The library DD statement was not specified. Action: Correct the library DD statement in the JCL and rerun the job. CAPU003E LIBRARY NOT DIRECT ACCESS. Reason: The library data set does not reside on direct access volume. The library cannot be processed by CAOUMRS. Action: Correct the data set name in the JCL or move this library to a direct access volume. CAPU004E LIBRARY DD STATEMENT INVALID. Reason: The library data set was not specified correctly. Action: Correct the library data set in the JCL and rerun the job. CAPU005E LIBRARY HAS AN INVALID VOLUME SEQUENCE NUMBER. Reason: The library data set resides on multiple volumes and cannot be processed by CAOUMRS. Action: Check the JCL to ensure it points to the correct library. Chapter 2: Messages 147 CAPxyyyz Messages CAPU006E LIBRARY NOT A PARTITIONED DATASET. Reason: The library is not a partitioned data set and cannot be processed by CAOUMRS. Action: Check the JCL to ensure it points to the correct library. CAPU007E LIBRARY DATASET HAS AN INVALID RECFM. Reason: The library data set is not a valid load library and cannot be processed by CAOUMRS. Action: Check the JCL to ensure it points at the correct library. CAPU008E UNABLE TO READ LIBRARY DICTIONARY. Reason: An I/O error occurred while attempting to read the library directory. The directory may be damaged. Action: Check the directory to ensure it contains valid data. Correct or restore the library and rerun the job. CAPU009E UNABLE TO READ LIBRARY MEMBER: XXXXXXXX. Reason: An I/O error occurred while attempting to read a library member. The member may be damaged. Action: Check the member to ensure it contains valid data. Correct or restore the library member and rerun the job. 148 Message Reference Guide CAPxyyyz Messages CAPU010E UNEXPECTED END OF FILE PROCESSING MEMBER: XXXXXXXX. Reason: The load module text information is incomplete. A member may be damaged. Action: Check the member to ensure it contains valid data. Correct or restore the member and rerun the job. CAPU011W MAXCSECT WAS EXCEEDED PROCESSING MEMBER XXXXXXXX. Reason: The load module being processed has more than 512 CSECTs. Action: Pass PARM='MAXCSECT=nnnn' on the exec card when invoking MRS to increase the value of MAXCSECT, where nnnn is the maximum number of CSECTs to be processed for a load module. CAPU012W BINDER ERROR PROCESSING xxxxxxxx FUNCTION. RC= xx REASON= xxxxxxxx Reason: The BINDER encountered an error during function xxxxxxxx. Action: Check to ensure that all members are bound/link-edited correctly. Processing continues. CAPU013W BINDER ERROR PROCESSING xxxxxxxx FUNCTION FOR MODULE xxxxxxxx. RC= xx REASON= xxxxxxxx Reason: The BINDER encountered an error during function xxxxxxxx. Action: Check to ensure that all members are bound/link-edited correctly. Processing continues. Chapter 2: Messages 149 CAPxyyyz Messages CAPU014E MAXIMUM SYSIN RECORDS EXCEEDED FOR CAOZAP Reason: Only 100 SYSIN records can be processed per run. Action: Limit the number of SYSIN records to a maximum of 100. CAPU100W QUOTE DELIMITER MISSING. RECORD REJECTED. Reason: To initialize the statistics data set, you must supply your company's name, location, and the installation date on the supply control statements. Action: Correct your control statements. Rerun the job if necessary. CAPU101W KEYWORD IN COLUMNS 1 THRU 8 NOT RECOGNIZED. CARD IGNORED. Reason: Columns 1-8 on your control statement must be one of these three keywords: CUSTNAME, CUSTLOCN, or INSTDATE. Action: Correct your control statements by specifying one of the three keywords. Rerun the job if necessary. CAPU102W CUSTOMER NAME TRUNCATED. MAXIMUM LENGTH = 40 CHARACTERS. Reason: The maximum length of customer name is 40 characters and will be truncated if this length is exceeded. Action: None. 150 Message Reference Guide CAPxyyyz Messages CAPU103W CUSTOMER LOCATION TRUNCATED. MAXIMUM LENGTH = 20 CHARACTERS. Reason: The maximum length of customer location is 20 characters and will be truncated if this length is exceeded. Action: None. CAPU104W INSTALLATION DATE MUST BE IN FORMAT (mm/dd/yy). CARD REJECTED. Reason: The installation date on user control statements was not in an expected format. Action: Correct the control statements so that the installation date is in the form mm/dd/yy and rerun the job. CAPU105E UNABLE TO OPEN SYSIN FILE. CHECK SYSIN DD STATEMENT. Reason: The SYSIN file contains the user supplied control statements. This message is issued if an error was encountered when trying to open the SYSIN file. Action: Check the SYSIN statement in your JCL to ensure it has the correct data set name and rerun the job. Chapter 2: Messages 151 CAPxyyyz Messages CAPU106E UNABLE TO OPEN STATS OUTPUT FILE. CHECK THE DD STATEMENT. Reason: This message is issued if an error was encountered when trying to open the STATS data set. Action: Check the CAISTATS DD statement in your JCL to ensure it has the correct data set name and rerun the job. CAPU107E UNRECOVERABLE ERRORS HAVE OCCURRED. REINITIALIZE THE STATS FILE. Reason: A serious error has occurred while attempting to write the STATS file. Action: Scratch and reallocate the STATS file and rerun the job. CAPU108I STATISTICS FILE HAS BEEN SUCCESSFULLY INITIALIZED. Reason: This message informs you that the STATS file has been successfully initialized. Action: None. CAPU109W MISSING CUSTOMER NAME. Reason: A customer name was not supplied on your control statements. Action: Check your control statements. Rerun the job if necessary. 152 Message Reference Guide CAPxyyyz Messages CAPU110W MISSING CUSTOMER LOCATION. Reason: A customer location was not supplied on your control statement. Action: Check your control statements. Rerun the job if necessary. CAPU111W MISSING INSTALLATION DATE. SYSTEM DATE WAS USED. Reason: An installation date was not supplied on your control statements. The initialization routine uses the system date as your installation date. Action: None. CAPU112E UNABLE TO OPEN STATIS FILE. CHECK THE DD STATEMENT. Reason: This message is displayed to the console if an error was encountered when trying to open the CAISTATS file. Action: Check the CAISTATS DD statement in your JCL to ensure it has the correct data set name. Rerun the job. CAPU113E STATISTICS FILE HAS BEEN DAMAGED. FILE MUST BE REBUILT. Reason: Your STATS file has been damaged and cannot be used. Action: Restore or reinitialize your STATS file. Chapter 2: Messages 153 CAPxyyyz Messages CAPU114E UNRECOVERABLE I/O ERROR HAS OCCURRED ON STATISTICS FILE. FILE MUST BE REBUILT. Reason: A serious error has occurred while attempting to write the STATS file. The STATS file probably has been damaged. Action: Check the CAISTATS DD statement. If the DD statement is incorrectly specified, correct and rerun the job. Otherwise, the statistics file in the DD statement has been damaged and must be reinitialized. CAPU115I OPTIMIZATION RESULTS UNAVAILABLE. ALL PROGRAMS HAVE BEEN OPTIMIZED WITH XCOUNT OPTION. Reason: This message is issued if you execute CAOMSRPT and all programs were compiled with XCOUNT. Action: None. CAPU116E UNABLE TO OPEN SYSPRINT FILE. CHECK DD CARD. Reason: This message is displayed to the console if an error was encountered when trying to open the SYSPRINT file. Action: Check the SYSPRINT DD card in your JCL to ensure it has the correct data set name. Rerun the job. 154 Message Reference Guide CAPxyyyz Messages CAPU117W INVALID SYSTEM DATE - ASSUME LAST DAY OF YEAR. Reason: The initialization routine tried to use the system date as the installation date, but the system date was invalid. The last day of the year will be used. Action: None. CAPU122E LICENSE MANAGEMENT PROGRAM NOT INSTALLED. Reason: The API for the License Management Program could not be found. Action: This error will not cause any immediate problems. Execution continues normally; however, this message will be repeated each time a CA Optimizer/II module is executed until the License Management Program is installed correctly. See your CA Common Services for z/OS documentation. CAPU301E CAIPRINT OPEN FAILED. Reason: An error occurred while attempting to open the CAIPRINT file. CAIPRINT formatting ends. No CAIPRINT output is generated. Action: Contact CA Technical Support. Chapter 2: Messages 155 CAPxyyyz Messages CAPU302E OPEN FAILED FOR CAIPRINT WORK FILE. Reason: An error occurred while attempting to open the CAIPRINT work file. CAIPRINT formatting ends. No CAIPRINT output is generated. Action: Contact CA Technical Support. CAPU303E OPEN FAILED FOR CAIPRINT REPOSITORY. Reason: An error occurred while attempting to open the CAIPRINT repository. CAIPRINT formatting ends. No CAIPRINT output is generated. Action: Contact CA Technical Support. CAPU304E MEMORY MANAGER INITIALIZATION FAILED. Reason: An internal error was detected while formatting an Abend report. Action: Save all materials and Virtual Host Manager. CAPU305E MEMORY MANAGER PUT FAILED. Reason: An internal error was detected while formatting an Abend report. Action: Save all materials and Virtual Host Manager. 156 Message Reference Guide CAPxyyyz Messages CAPU306E MEMORY MANAGER GET FAILED. Reason: An internal error was detected while formatting an Abend report. Action: Save all materials and Virtual Host Manager. CAPU308I SYMBOLIC INFORMATION AUTO POPULATED TO dsn. Reason: Symbolic information for the program name in the program box was automatically populated by the CA Endevor SCM dynamic symbolic support feature to the PROTSYM data set named dsn. Action: None. Informational only. CAPU309E SYMBOLIC FOR PROGRAM pgm NOT POPULATED. DYNAMIC SYMBOLIC SUPPORT ERROR. RC=xxxx, RSC=yyyy Reason: Symbolic information for the pgm named in the program box was NOT populated due to an error encountered by the CA Endevor SCM dynamic symbolic support feature. Return code from DSS is xxxx. Reason code from DSS is yyyy. The following table provides a list of possible return codes (RC) and reason codes (RSC) the API and various components may return. Note: Other numeric return codes and reason codes are also returned by CA Endevor SCM and z/OS binder services API (IEWBIND). For more information, see the respective guides. Function RC RSC Meaning API 00 0 Operations completed successfully. Chapter 2: Messages 157 CAPxyyyz Messages Function RC CA Endevor SCM 12 RSC Meaning 0 1. Incorrect C1DEFLTS used. 2. Listing data set referenced by the footprint is not cataloged. 3. For more information see the SYSOUT containing the CA Endevor SCM API execution report. CA Endevor SCM 32 15 CA Endevor SCM encountered critical error and cannot continue. Any function Any four digit code CCI The CA CCI component encountered an error communicating with the list server (INTNDVRx). See appropriate CCI documents for details. Any function Any four digit code CDRV One of the components (CA Testing and Fault Management) used by the list server interface encountered an error. Examine SYSOUT data sets from the started task INTNDVRx for appropriate component error logs and solutions. NDSB 04 NDSB Compressed footprint in IDRU invalid. API 02 NDVR GETMAIN failed. API 08 NDVR CA Endevor SCM server not activated. API 12 NDVR Invalid or missing parameter in NDVRCOMM. Listing data set not found. See CA Endevor SCM Message and Response file. API 16 NDVR Bad return code from CA Endevor SCM. See CA Endevor SCM documentation. API 20 NDVR Data set open failed. API 28 NDVR Allocation error. See SRVPRINT file. API 32 NDVR IN25DALC load failed. 158 Message Reference Guide CAPxyyyz Messages Function RC RSC Meaning API 36 NDVR ENA$NDVR load failed. API 40 NDVR CA Endevor SCM footprint not found for requested element. API 44 NDVR Requested CSECT not found. API 48 NDVR IN25CDRV load failed. NSRV 08 NSRV Listing server abort or failed. NIDR 02 XIDR GETMAIN failed. NIDR 08 XIDR PARM error. NIDR 20 XIDR CAOUXDSB load failed. NIDR 2C XIDR No IDRU found for CSECT in NDVR_NAM2 or NDVR_ELEM. CSVQ 30 XIDR CSECT from IDRU does not match CSECT in NDVR_NAM2. BINDER 44 XIDR Requested CSECT not found by binder. Action: Appropriate action should be taken based on the return and reason code. CAPU310W CAOFSYMP – LOAD OF CAODNDVR FAILED. Reason: Dynamic symbolic support encountered an error loading module CAODNDVR. Dynamic symbolic support will not be able to populate the symbolic file. Action: Ensure that the CA Optimizer/II product load module libraries are correctly defined in your JCL or are defined in your installation's LNKLST. Chapter 2: Messages 159 CAPxyyyz Messages CAPU311W NO FOOTPRINT WAS FOUND FOR PROGRAM XXXXXXXX.. Reason: Program XXXXXXXX does not have the required CA Endevor SCM footprint. Dynamic symbolic support is unable to populate the symbolic file for the indicated program. Action: Ensure that the indicated program is under CA Endevor SCM control and that the associated load modules were generated using the CA Endevor SCM Generate facility. For more information, see Dynamic Symbolic Support For CA Endevor SCM in the Installation Guide, r8. CAPU312I END OF DATA ENCOUNTERED BEFORE END OF MAP. SOME VARIABLES MAY NOT BE DISPLAYED. Reason: The storage associated with a data area is shorter than the map of the area in the symbolic file member. This can occur in the following instances: ■ The current record for a variable-length file is shorter than the maximum length defined in the File Section of a COBOL program. ■ The BLLMAX value is smaller than the length of an 01 item in the Linkage Section of a COBOL program. ■ The REGMAX value is smaller than the length of a DSECT definition for which there is an active USING in an Assembler program. ■ The symbolic file member does not exactly match the program in the executable load module, as indicated by a CAPD113W message. Any variables that map to data beyond the end of the available storage will not be displayed. Action: No action is required. However, the message may be eliminated if it was not caused by a short record in a variable-length file using one of the following methods: ■ 160 Message Reference Guide If the message is displayed because the BLLMAX value is smaller than the length of an 01 item in the Linkage Section of a COBOL program, specify a larger BLLMAX value and rerun the job. CAPxyyyz Messages ■ If the message is displayed because the REGMAX value is smaller than the length of a DSECT definition for which there is an active USING in an Assembler program, specify a larger REGMAX value and rerun the job. ■ If a CAPD113W message was displayed, indicating that the symbolic file member does not exactly match the program in the executable load module, follow the action specified for that message. CAPU313E OFFSET DOES NOT CORRESPOND TO A STATEMENT WITHIN THE PROGRAM. Reason: The indicated program offset does not correspond to a source statement in the program. A source statement could not be found. Action: If a CAPD113W message was displayed, indicating that the symbolic file member does not exactly match the program in the executable load module, follow the action specified for that message. Otherwise, Virtual Host Manager. CAPU399E INTERNAL ERROR. CAIPRINT FORMATTER IN CONTROL. Reason: The error recovery mechanisms (for example, ESTAE exits) of the CAIPRINT Formatter have encountered an unexpected and unrecoverable abend. The most likely event is an unexpected OCx abend. This could be traceable to an invalid control block, product logic error, or user error. A few data elements related to the abend are captured and an attempt is made to relate the abending PSW address to an offset within a named module. The abend code (for example, OC4) and the registers at abend, along with other pertinent information, are written to CAIPRINT and a dump is produced. Action: Contact CA Technical Support to report the problem after the dump is available. In the RTM2WA summary, abends are represented by a chain of SDWA control blocks displayed in chronological order from the oldest to the newest. Generally, diagnose the problem by finding the SDWA in the RTM2WA SUMMARY chain that matches the abend code and registers displayed on CAIPRINT. Chapter 2: Messages 161 CAPxyyyz Messages CAPU400I THE FOLLOWING EXPIRED REPORTS WILL BE DELETED: Reason: While adding an Abend report to the repository, one or more reports were found that exceeded the expiration limit established for your installation by the EXPDAYS option in CAOUDFRX. These reports were deleted. Action: No action is required. However, to prevent this message and the automatic deletion of abend reports from your repository, set the EXPDAYS option to zero. CAPU401I J=jjjjjjjj,S=ssssssss,P=pppppppp,O=oooooo,ccccc. Reason: This informational message appears once for each report that was automatically deleted due to expiration. The job name, system name, program name, offset, and completion code are used to identify the message. Action: No action is required. However, to prevent this message and the automatic deletion of abend reports from your repository, set the EXPDAYS option to zero. CAPU402I AUTO-MAINTENANCE COMPLETED. Reason: This message is written after all abend reports in your repository have been tested for expiration, only if reports were actually deleted during the process. Action: No action is required. 162 Message Reference Guide CAPxyyyz Messages CAPU501I COMPILE TIME DEFAULTS CSECT 'CAOUDFOX' NOT FOUND. REPORTING CONTINUES FOR RTL ONLY. Reason: The options reporting program was unable to find the compile time default options member, CAOUDFOX. Options reporting continues for the runtime default options. Action: If you have not installed the compile time component of CA Optimizer/II, no response is necessary. Otherwise, verify that the library containing the compile time options member, CAOUDFOX, is available to the options reporting program in LINKLIST or LPA, or was specified in the JCL in STEPLIB or JOBLIB. CAPU502E RUN TIME DEFAULTS CSECT 'CAOUDFRX' NOT FOUND. REPORTING TERMINATED. Reason: The options reporting program was unable to find the runtime default options member, CAOUDFRX. Options reporting was terminated. Action: Verify that the library containing the runtime options member, CAOUDFRX, is available to the options reporting program in LINKLIST or LPA, or was specified in the JCL in STEPLIB or JOBLIB. CAPZ001E A LOCAL DATA SPACE REQUEST EXCEEDED THE AMOUNT AVAILABLE. Reason: Upon entry to a CAOZxxxx module, the size of the local data required by that module exceeded the amount available. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. Chapter 2: Messages 163 CAPxyyyz Messages CAPZ002E THE EOS LOCK COULD NOT BE OBTAINED. Reason: EOS was unable to obtain its internal lock. Action: This is a severe EOS internal error. The transaction is abended and the EOS lock is forced opened. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ003E A COBOL EOS TRANSACTION WAS STARTED BUT EOS IS DISABLED. Reason: EOS was entered to initiate an EOS COBOL transaction but EOS was disabled. Action: The System Programmer has temporarily or permanently disabled EOS. Inflight transactions are allowed to continue but new EOS COBOL transactions are abended at transaction initiation. Wait until EOS has been reenabled before starting any new EOS COBOL transactions. CAPZ004E THE EOS MESSAGE WRITER SUFFERED AN INTERNAL FAILURE. Reason: EOS message writing facility has failed while attempting to write a message to the runtime message destination. Action: This is a severe EOS internal error. The transaction is abended. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. 164 Message Reference Guide CAPxyyyz Messages CAPZ005E A CONDITION WAS SET ON A RETURN COMMAND ISSUED BY EOS. Reason: Following an EXEC CICS RETURN issued by EOS, CICS returned to EOS with a condition set. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ006E AN UNDEFINED ROUTINE WAS INVOKED BY WAY OF THE CA COBVEC. Reason: An EOS COBOL program fetched an address from an undefined slot in the CA COBVEC and invoked the routine. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ007E AN UNSUPPORTED ROUTINE WAS INVOKED BY WAY OF THE CA COBVEC. Reason: An EOS COBOL program fetched an address from an unsupported slot in the CA COBVEC and invoked the routine. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. Chapter 2: Messages 165 CAPxyyyz Messages CAPZ008E AN UNEXPECTED LOGIC PATH WAS TAKEN WHILE HANDLING AN "EXIT PROGRAM". Reason: The EOS routine to handle STOP RUN or GOBACK was entered from an EOS COBOL program but the input parameter did not indicate either STOP RUN or GOBACK. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ009E EOS WAS UNABLE TO FREE STORAGE FOR AN EOS COBOL TRANSACTION. Reason: EOS attempted to free storage previously obtained on behalf of the transaction, but the FREEMAIN failed. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ010E EOS WAS UNABLE TO FREE SUFFICIENT UNUSED STORAGE FOR A COBOL TRANS. Reason: EOS could not free enough storage previously obtained on behalf of the transaction to satisfy its internal storage management parameters. Action: This is a severe EOS internal logic error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. 166 Message Reference Guide CAPxyyyz Messages CAPZ011E EOS WAS UNABLE TO LOCATE THE TGT FOR THE MAIN EOS COBOL PGM IN R.U. Reason: An internal EOS lookup routine to locate the TGT for the main EOS program in the run unit could not locate the main TGT. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ012E EOS WAS UNABLE TO LOCATE A TGT FOR AN EOS COBOL PGM IN THE RUN UNIT. Reason: An internal EOS lookup routine to locate a TGT for an EOS subprogram in the run unit could not locate a TGT. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ013E EOS WAS UNABLE TO OBTAIN STORAGE FOR AN EOS COBOL TRANSACTION. Reason: A GETMAIN to obtain storage for an EOS COBOL program's TGT and Working Storage failed. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. Chapter 2: Messages 167 CAPxyyyz Messages CAPZ014E AN EOS COBOL SUBPROGRAM WAS ABOUT TO BE ENTERED RECURSIVELY. Reason: A static CALL to an EOS COBOL program was made, but the program is already active in the Run Unit. Action: This is probably an application logic error. COBOL programs cannot be recursively entered. For example, if A CALLs B which CALLs C which CALLs B, at the point where C CALLs B, EOS will determine that B is already active and abend the transaction. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. The dump includes the EOS diagnostic report; see the chapter "Using EOS" in the User Guide for information on execution-time abends. CAPZ015E EOS WAS UNABLE TO LOCATE THE TGT FOR THE MAIN EOS COBOL PGM IN R.U. Reason: An internal EOS lookup routine to locate the TGT for the main EOS program in the run unit could not locate the main TGT. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ016E EOS WAS UNABLE TO LOCATE THE RUNCOM FOR AN IBM-CONTROLLED R.U. Reason: An internal EOS lookup routine to locate the RUNCOM for the current run unit owned by the COBOL II runtime system could not locate the RUNCOM. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. 168 Message Reference Guide CAPxyyyz Messages CAPZ017E RUNCOM FOR IGZ OR CEE-CONTROLLED R.U. DID NOT POINT TO A VALID TGT. Reason: The found RUNCOM for the current run unit owned by the COBOL II runtime system or LE/370 did not point to a valid non-EOS TGT. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ018E THE SIZE OF A DATA(24) EOS COBOL PGM'S TGT AND W. S. EXCEEDED 64K. Reason: An EOS COBOL program was compiled/optimized with DATA(24). The program's TGT and Working Storage at execution time exceeded 64 KB. Action: DATA(24) forces EOS to obtain storage below the 16 MB line. CICS does not allow a GETMAIN request below the line to exceed 64 KB. Specify DATA(31) and recompile/optimize. If that is not possible, make source changes to reduce the size of the program's Working Storage. An EOS diagnostic report is written to the runtime message destination, and a transaction dump is taken. The dump includes the EOS diagnostic report; see the chapter "Using EOS" in the User Guide for information on execution-time abends. Chapter 2: Messages 169 CAPxyyyz Messages CAPZ019E THE "HANDLE" STACK WAS EMPTY BEFORE THE "POP" COMMAND ISSUED BY EOS. Reason: Just before the return from a statically CALLed EOS COBOL program to its caller, EOS executed a POP HANDLE command. However, the HANDLE stack was already empty before the POP command was issued. Action: For a statically CALLed EOS COBOL program optimized with PUSHPOP, EOS performs a PUSH HANDLE just before program entry and a POP HANDLE just before program return. This is probably an application logic error. Verify that the CALLed program is not executing its own POP HANDLE prior to the return. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. The dump includes the EOS diagnostic report; see the chapter "Using EOS" in the User Guide for information on execution-time abends. CAPZ020E EOS WAS UNABLE TO COMPLETE IGZ OR CEE THREAD INITIALIZATION. Reason: EOS invoked either the COBOL II runtime system or LE/370 to perform non-EOS thread initialization, but the return code was not zero. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ021E EOS WAS UNABLE TO LOCATE THE CURRENT CEE RUN UNIT TOKEN. Reason: An internal EOS lookup routine to locate the LE/370 run unit token could not locate the token. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. 170 Message Reference Guide CAPxyyyz Messages CAPZ022E EOS WAS UNABLE TO COMPLETE CEE RUN UNIT INITIALIZATION. Reason: EOS invoked LE/370 to perform non-EOS run unit initialization but the return code was not zero. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ023E A FAILURE HAS OCCURED IN CAOZDTE; PLEASE REVIEW PRIOR MESSAGES. Reason: The EOS routine to handle a format 2 ACCEPT verb encountered an internal error. Action: This is a severe EOS internal error. One or more messages providing further explanation are written to the runtime message destination prior to the EOS diagnostic report. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ024E EOS WAS UNABLE TO OBTAIN USER24 STORAGE FOR CEE FOR THE RUN UNIT. Reason: A GETMAIN to obtain USER24 storage on behalf of LE/370 failed. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. Chapter 2: Messages 171 CAPxyyyz Messages CAPZ025E AN INVALID TAPS RECORD WAS PASSED TO CAOZTAPS. Reason: A parameter passed from an EOS COBOL program to an EOS routine is not recognizable. Action: Certain EOS routines are directly invoked from the EOS COBOL program to support particular COBOL language statements, for example, GOBACK. Probable causes include corrupted EOS COBOL program storage or a logic error in the invoked EOS routine. This is a severe error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ026E A COBOL PROGRAM HAS INVOKED SORT BUT CA-CICSORT IS NOT INSTALLED. Reason: An EOS COBOL program has invoked SORT but Unicenter CA-CICSORT is not installed in the CICS region. Action: If Unicenter CA-CICSORT is installed in your data center then the message means that it is not installed in the particular CICS region in which the transaction executed. Ensure that your CICS systems Programmer makes Unicenter CA-CICSORT available in that CICS region. If Unicenter CA-CICSORT is not installed in your data center then the optimize-time option, CASORT, should be set to NOCASORT and the program recompiled/optimized. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. The dump includes the EOS diagnostic report; see the chapter "Using EOS" in the User Guide for information on execution-time abends. 172 Message Reference Guide CAPxyyyz Messages CAPZ027E EOS MODULE CAOZECIC IS NOT LINK EDITED FOR THE LE/370 ENVIRONMENT. Reason: EOS is about to perform LE/370 run unit initialization but EOS is link-edited for the COBOL II runtime environment. Action: This is an EOS product installation problem. Most likely, when EOS was initially installed your data center was using the COBOL II runtime system. Since that time your data center has switched to LE/370 without relinking EOS for the LE/370 environment which your CICS systems Programmer must do. The transaction is abended. An EOS diagnostic report is written to the runtime message destination, and a transaction dump is taken. CAPZ028E CAOZMSG TERMINATED THE TRANSACTION. PLEASE REVIEW PREVIOUS MESSAGES. Reason: CAOZMSG terminated the transaction on behalf of the application after writing a message to the runtime message destination. The message previously written explains the reason for EOS having abended the transaction. Action: This normally indicates an application logic error that was detected by EOS. For example, message CAPZ028E would accompany EOS abend RX28 following message CAPZ153E, (fall through the bottom of the EOS COBOL program). An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. The dump includes the EOS diagnostic report; see the chapter "Using EOS" in the User Guide for information on execution-time abends. CAPZ029E CAOZMSG WAS UNABLE TO RECOGNIZE THE INPUT MESSAGE NUMBER. Reason: The message number passed from the EOS COBOL program to EOS routine CAOZMSG was not defined to CAOZMSG. Action: This is a severe EOS internal error. The transaction is abended. An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. Chapter 2: Messages 173 CAPxyyyz Messages CAPZ030E CAOZSSN TERMINATED THE TRANSACTION. PLEASE REVIEW PREVIOUS MESSAGES. Reason: CAOZSSN terminated the transaction on behalf of the application after writing a message to the runtime message destination. The message previously written explains the reason for EOS having abended the transaction. Action: This normally indicates an application logic error that was detected by EOS. For example, message CAPZ030E accompanies EOS abend RX30 following message CAPZ155E (invalid separate sign). An EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. The dump includes the EOS diagnostic report; see the chapter "Using EOS" in the User Guide for information on execution-time abends. CAPZ100I EOS INITIATION STARTED. Reason: This is an informative message that is always written at the beginning of the EOS initialization transaction, RXIN. Action: None. CAPZ101I EOS INITIATION ENDED. Reason: This is an informative message that is always written at the end of the EOS initialization transaction, RXIN. Action: None. This message is written regardless of the success of the initialization. Messages immediately preceding it indicate the success or the failure of the initialization. 174 Message Reference Guide CAPxyyyz Messages CAPZ102E EOS WAS UNABLE TO DETERMINE THE VERSION.RELEASE.MODLEVEL OF CICS. Reason: The version, release, and modification level of CICS was unknown to the EOS initialization transaction, RXIN. Action: This is a severe error and indicates that EOS initialization failed. The most probable cause is that the version, release, and modification level of CICS is less than or greater than the set of CICS releases currently supported by EOS. See the chapter "System Requirements" in the Installation Guide for information on supported releases. CAPZ103E NEITHER THE COBOL II RTL NOR LE/370 HAS BEEN INITIALIZED. Reason: The EOS initialization transaction, RXIN, determined that neither the COBOL II runtime system nor the runtime system for COBOL/370, LE/370, was initialized at CICS startup. Action: This is a severe error and indicates that EOS initialization failed. If EOS COBOL II transactions are to be run, either the COBOL II RTL or LE/370 have to be initialized at CICS startup. If EOS COBOL/370 transactions are to be run, LE/370 has to be initialized at CICS startup. CAPZ104W EOS IS ALREADY INITIATED AND ENABLED. Reason: An attempt to initialize and enable EOS by the EOS initialization transaction, RXIN, failed with a warning that EOS is already initialized and enabled. Action: This is a warning message. The execution of the RXIN transaction was effectively a no-op. The most likely cause of this message is that the RXIN transaction was inadvertently executed when EOS was already initiated and enabled. Chapter 2: Messages 175 CAPxyyyz Messages CAPZ105E EOS IS ALREADY LOADED BUT WAS NOT PREVIOUSLY INITIATED. Reason: The EOS initialization transaction, RXIN, determined that EOS was already loaded in the CICS region but was not in the initiated state. Action: The most likely cause of this problem is corruption of EOS module CAOZECIC. The CICS region must be recycled to recover from this error. Before doing so take a SNAP dump of the CICS region. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ106E EOS WAS UNABLE TO DELETE MODULE CAOZCOBP. Reason: The EOS initialization transaction, RXIN, was unable to DELETE or RELEASE EOS module CAOZCOBP prior to LOADing a fresh copy. Action: A condition was returned from the DELETE or RELEASE macro. This prevented the initialization transaction from LOADing a fresh copy of CAOZCOBP during EOS reinitialization. This is a severe error that indicates that EOS reinitialization failed. EOS remains in the disabled state. The CICS region must be recycled to recover from this error. Before doing so take a SNAP dump of the CICS region. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. 176 Message Reference Guide CAPxyyyz Messages CAPZ107E EOS WAS UNABLE TO LOAD THE DEFAULT CSECT, CAOZDFRX. Reason: The EOS initialization transaction, RXIN, was unable to LOAD the module containing the options for EOS. Action: A condition was returned from the LOAD macro. This prevented the initialization transaction from setting its options during initialization or reinitialization. This is a severe error and indicates that EOS initialization or reinitialization failed. Verify that CAOZDFRX has not been inadvertently deleted from the CAICICS PDS. The CICS region must be recycled to recover from this error. Before doing so take a SNAP dump of the CICS region. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ108E EOS WAS UNABLE TO LOAD CAOZCOBP. Reason: The EOS initialization transaction, RXIN, was unable to LOAD EOS module CAOZCOBP. Action: A condition was returned from the LOAD macro. This is a severe error and indicates that EOS initialization or reinitialization failed. Verify that CAOZCOBP has not been inadvertently deleted from the CAICICS PDS. The CICS region must be recycled to recover from this error. Before doing so take a SNAP dump of the CICS region. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. Chapter 2: Messages 177 CAPxyyyz Messages CAPZ109E EOS WAS UNABLE TO LOAD CAOZECIC. Reason: The EOS initialization transaction, RXIN, was unable to LOAD EOS module CAOZECIC. Action: A condition was returned from the LOAD macro. This is a severe error and indicates that EOS initialization or reinitialization failed. Verify that CAOZECIC has not been inadvertently deleted from the CAICICS PDS. The CICS region must be recycled to recover from this error. Before doing so take a SNAP dump of the CICS region. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ110E THE VERSION OF THE COBOL II RTL OR LE/370 IS NOT SUPPORTED BY EOS. Reason: The version of the COBOL II RTL or LE/370 was unknown to the EOS initialization transaction, RXIN. Action: This is a severe error and indicates that EOS initialization failed. The most probable cause is that the version, release, and modification level of the COBOL II RTL or LE/370 is less than or greater than the set of releases currently supported by EOS. See the chapter "System Requirements" in the Installation Guide for information on supported releases of the COBOL II RTL and LE/370. 178 Message Reference Guide CAPxyyyz Messages CAPZ111W EOS WAS UNABLE TO LOAD CASLZ001. INITIATION WILL CONTINUE. Reason: The EOS initialization transaction, RXIN, was unable to LOAD Unicenter CA-CICSORT module CASLZ001. Action: A condition was returned from the LOAD macro. This is a warning message. EOS initialization continues following the LOAD failure. If Unicenter CA-CICSORT is not installed in your data center then ignore this message. If Unicenter CA-CICSORT is installed, verify that Unicenter CA-CICSORT is defined in the RPL. If it is defined, take a SNAP dump of the CICS region. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. Following this execution of the EOS initialization transaction, any EOS COBOL program using SORT and compiled/optimized with the CASORT option will abend with an RX26 abend. CAPZ112I EOS HAS BEEN SUCCESSFULLY INITIATED AND ENABLED. Reason: The EOS initialization transaction, RXIN, has successfully completed initialization or reinitialization. Action: If, and only if, this message is produced then EOS has been enabled to run EOS COBOL transactions. This message will precede message CAPZ101I. CAPZ113I EOS TERMINATION STARTED. Reason: This is an informative message that is always written at the beginning of the EOS termination transaction, RXTR. Action: None. Chapter 2: Messages 179 CAPxyyyz Messages CAPZ114I EOS TERMINATION ENDED. Reason: This is an informative message that is always written at the end of the EOS termination transaction, RXTR. Action: None. This message is written regardless of the success of the termination processing. Messages immediately preceding it indicate the success or the failure of the termination. CAPZ115W COBOL II RTL OR LE/370 IS NOT INITIALIZED. EOS WAS NEVER INITIATED. Reason: The EOS termination transaction, RXTR, determined that neither the COBOL II runtime system nor the runtime system for COBOL/370, LE/370, was initialized at CICS startup. Therefore, EOS also could never have been initialized by the RXIN transaction. Action: This is a warning message. The execution of the RXTR transaction was effectively a no-op. If EOS COBOL II transactions are to be run then either the COBOL II RTL or LE/370 have to be initialized at CICS startup. If EOS COBOL/370 transactions are to be run then LE/370 has to be initialized at CICS startup. CAPZ116W EOS TERMINATION CANNOT BE PERFORMED BECAUSE EOS WAS NEVER INITIATED. Reason: The EOS termination transaction, RXTR, determined that the EOS initialization transaction, RXIN, was never run. Action: This is a warning message. The execution of the RXTR transaction was effectively a no-op. 180 Message Reference Guide CAPxyyyz Messages CAPZ117W EOS IS ALREADY DISABLED. Reason: An attempt to disable EOS by the EOS termination transaction, RXTR, failed with a warning that EOS is already disabled. Action: This is a warning message. The execution of the RXTR transaction was effectively a no-op. The most likely cause of this message is that the RXTR transaction was inadvertently executed when EOS was already disabled. CAPZ118I EOS HAS BEEN SUCCESSFULLY DISABLED. Reason: The EOS termination transaction, RXTR, has successfully completed the disabling of EOS. Action: If, and only if, this message is produced then EOS has been successfully disabled. This message will precede message CAPZ114I. CAPZ119I THE EOS TRACE FACILITY HAS BEEN STOPPED BY EOS TERMINATION. Reason: The EOS trace facility was enabled when the EOS termination transaction, RXTR, began executing. RXTR stopped the EOS trace facility. Action: The trace facility is stopped. The result is the same as if the EOS trace transaction, RXTC, were invoked to stop the EOS trace facility. The EOS trace table is dumped to the transaction dump data set under the transaction ID RXTR. Chapter 2: Messages 181 CAPxyyyz Messages CAPZ120E EOS LOCK COULD NOT BE OBTAINED. EOS PERFORMED A FORCED TERMINATION. Reason: During execution of the EOS termination transaction, RXTR, EOS was unable to obtain its internal lock. Action: This is a severe EOS internal error. The EOS lock is forced open and the transaction continues. If the EOS trace facility was on then it is stopped but no dump of the trace table is taken. Before proceeding further, take a SNAP dump of the CICS region. Verify that EOS is still operational by executing the EOS initialization transaction, RXIN followed by the EOS I.V.P. transaction, RXIV. If either fail then follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ121I EOS TRACE TRANSACTION STARTED. Reason: This is an informative message that is always written at the beginning of the EOS trace transaction, RXTC. Action: None. CAPZ122I EOS TRACE TRANSACTION ENDED. Reason: This is an informative message that is always written at the end of the EOS trace transaction, RXTC. Action: None. This message is written regardless of the success of the trace processing. Messages immediately preceding it indicate the success or the failure of the trace transaction. 182 Message Reference Guide CAPxyyyz Messages CAPZ123W EOS TRACE CANNOT BE PERFORMED BECAUSE EOS WAS NEVER INITIATED. Reason: The EOS trace transaction, RXTC, determined that the EOS initialization transaction, RXIN, was never run. Action: This is a warning message. The execution of the RXTC transaction was effectively a no-op. CAPZ124W EOS IS DISABLED. TRACE PROCESSING CANNOT BE PERFORMED. Reason: The EOS trace transaction, RXTC, determined that the EOS termination transaction, RXTR, has disabled EOS. Action: This is a warning message. The execution of the RXTC transaction was effectively a no-op. The EOS trace facility can be started or stopped only when EOS is initialized and enabled. The EOS initialization transaction, RXIN, must first be run to reenable EOS before running the RXTC transaction again. CAPZ125W THE EOS TRACE COMMAND WAS NOT RECOGNIZED. PLEASE RESPECIFY. Reason: The EOS trace transaction, RXTC, did not recognize the command string following the transaction ID, RXTC. Action: This is a warning message. The execution of the RXTC transaction was effectively a no-op. See the chapter "EOS Usage Considerations" in the Installation Guide for a description of the RXTC commands. Chapter 2: Messages 183 CAPxyyyz Messages CAPZ126E THE EOS LOCK COULD NOT BE OBTAINED. EOS FORCED TRACE OFF. Reason: During execution of the EOS trace transaction, RXTC, to stop trace processing, EOS was unable to obtain its internal lock. Action: This is a severe EOS internal error. The EOS lock is forced open and the transaction continues. The EOS trace facility is stopped but no dump of the trace table is taken. Before proceeding further, take a SNAP dump of the CICS region. Verify that EOS is still operational by executing the EOS I.V.P. transaction, RXIV. If it fails then follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ127I THE EOS TRACE FACILITY HAS BEEN SUCCESSFULLY STOPPED. Reason: The EOS trace transaction, RXTC, has successfully stopped the EOS trace facility. Action: If, and only if, this message is produced then the EOS trace facility has been successfully stopped. This message will precede message CAPZ122I. The EOS trace table is dumped to the transaction dump data set under the transaction ID RXTC. CAPZ128I THE EOS TRACE FACILITY IS ALREADY DISABLED. Reason: The EOS trace transaction, RXTC, has not honored the request to stop the trace facility because the trace facility has already been stopped. Action: The execution of the RXTC transaction was effectively a no-op. 184 Message Reference Guide CAPxyyyz Messages CAPZ129I THE EOS TRACE FACILITY IS ALREADY ENABLED. Reason: The EOS trace transaction, RXTC, has not honored the request to start the trace facility because the trace facility has already been started. Action: The execution of the RXTC transaction was effectively a no-op. CAPZ130E THE EOS LOCK COULD NOT BE OBTAINED. TRACE CANNOT BE STARTED. Reason: During execution of the EOS trace transaction, RXTC, to start trace processing, EOS was unable to obtain its internal lock. Action: This is a severe EOS internal error. The EOS lock is not forced open and the transaction is effectively a no-op. Before proceeding further, take a SNAP dump of the CICS region. Verify that EOS is still operational by executing the EOS termination transaction, RXTR, followed by the EOS initialization transaction, RXIN followed by the EOS I.V.P. transaction, RXIV. If any of the three fail, follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ131I THE EOS TRACE FACILITY HAS BEEN SUCCESSFULLY STARTED. Reason: The EOS trace transaction, RXTC, has successfully started the EOS trace facility. Action: If, and only if, this message is produced then the EOS trace facility has been successfully started. This message will precede message CAPZ122I. Chapter 2: Messages 185 CAPxyyyz Messages CAPZ132E FREEMAIN FOR THE EOS TRACE TABLE FAILED. PROCESSING WILL CONTINUE. Reason: During execution of the EOS trace transaction, RXTC, to either start or stop trace processing, EOS was unable to free storage for the trace table. Action: This is a severe EOS internal error. Additional messages will accompany this one prior to message CAPZ122I. Before proceeding further, take a SNAP dump of the CICS region. Verify that EOS is still operational by executing the EOS I.V.P. transaction, RXIV. If it fails, follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ133E GETMAIN FOR THE EOS TRACE TABLE FAILED. TRACE CANNOT BE STARTED. Reason: During execution of the EOS trace transaction, RXTC, to start trace processing, EOS was unable to obtain storage for the trace table. Action: This is a severe EOS internal error. The transaction is effectively a no-op. Before proceeding further, take a SNAP dump of the CICS region. Verify that the value of the TRACESZ EOS option has not been set to an unreasonably large value. For more information about the storage requirements for the EOS trace table, see the chapter "EOS Usage Considerations" in the Installation Guide. Verify that EOS is still operational by executing the EOS I.V.P. transaction, RXIV. If it fails, follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ134W EOS WAS UNABLE TO DELETE MODULE CAOZDFRX. PROCESSING WILL CONTINUE. Reason: The EOS initialization transaction, RXIN, was unable to DELETE or RELEASE EOS module CAOZDFRX at the end of EOS initialization processing. Action: A condition was returned from the DELETE or RELEASE macro. This is a warning message. EOS should be in the enabled state at the end of the RXIN transaction. You can verify that EOS is operational by executing the EOS I.V.P. transaction, RXIV. 186 Message Reference Guide CAPxyyyz Messages CAPZ135E EOS WAS UNABLE TO OBTAIN STORAGE AT TRANSACTION START. Reason: The initial storage request by EOS on behalf of the EOS COBOL transaction failed. Action: This is a severe EOS internal error. The transaction is abended with an ASRA (0C1). The PSW at abend points to the CAPZ135E message. An EOS diagnostic report may be written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ136W THE MAXIMUM NUMBER OF EOS MESSAGES FOR THE TRANS HAS BEEN REACHED. Reason: The maximum number of EOS messages written by EOS on behalf of the transaction to the runtime message destination has exceeded the value of the MSGMAX EOS option. Action: This is a warning message. No more EOS messages are written by EOS for the transaction but application transaction execution is allowed to continue. The MSGMAX option is controlled by your CICS systems programmer. This option is meant to prevent unnecessarily large volumes of messages from any one transaction. This can happen due to unanticipated application program loops which include an invocation from the compiled/optimized code of an EOS support module which writes n a message (usually a warning message) on behalf of the application. Examine the messages produced for symptoms of an unwanted loop in the application. If the value of MSGMAX must be made larger, consult your CICS systems programmer. Chapter 2: Messages 187 CAPxyyyz Messages CAPZ137E AN UNDEFINED FUNCTION CODE WAS PASSED TO THE EOS INTERFACE. Reason: EOS has received an undefined function code from CICS on behalf of a COBOL application. Action: This is a severe EOS internal error. The transaction is abended with an ASRA (0C1). The PSW at abend points to the CAPZ137E message. An EOS diagnostic report may be written to the runtime message destination and a transaction dump is taken. Follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ138E THE EOS CBL BOOTSTRAP WAS ENTERED BUT EOS HAS NOT BEEN INITIALIZED. Reason: The EOS COBOL bootstrap routine, CAOZEBST, has been entered but EOS has not been initialized in the CICS region. Action: This is a severe EOS internal error. The transaction is abended with an ASRA (0C1). The PSW at abend points to the CAPZ138E message. An EOS diagnostic report may be written to the runtime message destination and a transaction dump is taken. The most likely cause of this error is that the RXIN EOS initialization n transaction was never run. Consult your CICS systems programmer to verify this. 188 Message Reference Guide CAPxyyyz Messages CAPZ139E THE EOS CBL BOOTSTRAP WAS ENTERED BUT THE SUBSYSTEM IS NOT SUPPORTED. Reason: The EOS COBOL bootstrap routine, CAOZEBST, has been entered but the environment is not CICS. Action: This is a severe EOS internal error. The transaction (program) is abended with an ASRA (0C1). The PSW at abend points to the CAPZ139E message. A dump can be taken. The most likely cause of this error is that a non-CICS COBOL program was compiled/optimized with the EOS option and run in a non-CICS environment. If this is not the case, follow the guidelines for obtaining necessary supporting documentation in the appendix "Troubleshooting" in the User Guide and contact CA Technical Support for assistance. CAPZ140E A CROSS-PGM TRANSFER TO HANDLE LABEL IN PGM ???????? WAS ATTEMPTED. Reason: An abend in program x was about to cause control to pass from x to the HANDLE label in a different program in the run unit identified as program ????????. Action: CICS abends the task as if no HANDLE ABEND LABEL were active. This is probably an application logic error. For example, program A establishes a HANDLE ABEND LABEL and statically CALLs program B. B, which was optimized with the NOPUSHPOP option, executes a CICS command which happens to cause an error condition. Since HANDLE ABEND is still active in A, CICS attempts to transfer control from B to the label in A. This illegal cross-program transfer of control is detected by EOS. For the transaction abend, an EOS diagnostic report is written to the runtime message destination and a transaction dump is taken. The dump includes the EOS diagnostic report. For more information about execution-time abends, see the chapter "Using EOS" in the User Guide. Chapter 2: Messages 189 CAPxyyyz Messages CAPZ141E EOS HAS ABENDED. THE FOLLOWING REPORT SUMMARIZES THE ERROR. Reason: This message is written to the runtime message destination by the EOS diagnostic reporting routine as the first line of the report when EOS itself is the likely cause of the abend. Action: The message is followed by the rest of the diagnostic report. CAPZ142E AN EOS COBOL TRANS HAS ABENDED. THIS REPORT SUMMARIZES THE ERROR. Reason: This message is written to the runtime message destination by the EOS diagnostic reporting routine as the first line of the report when the EOS COBOL application itself is the likely cause of the abend. Action: The message is followed by the rest of the diagnostic report. CAPZ143I THE DIAGNOSTIC REPORT IS COMPLETE. Reason: This message is always written to the runtime message destination by the EOS diagnostic reporting routine as the last line of the report. Action: None. 190 Message Reference Guide CAPxyyyz Messages CAPZ144E CA COMMON SERVICES FOR Z/OS IS NOT INSTALLED. EOS CANNOT BE INITIALIZED. Reason: The EOS initialization transaction, RXIN, requires that CA Common Services for z/OS first be installed before EOS can perform its own initialization. Action: This is a severe error and indicates that EOS initialization failed. The transaction is effectively a no-op. No EOS modules have been loaded and no storage has been altered. Install CA Common Services for z/OS before rerunning the RXIN transaction. CAPZ145E THE RXNN ERROR CODE IS OUT OF RANGE. Reason: EOS has abended with a RXnn abend code but the nn is out range; there is no matching message for the abend code. Action: While this is a severe message the EOS diagnostic reporting routine continues with its report. CAPZ146E UNEXPECTED PARM LIST ENCOUNTERED. Reason: The EOS routine to handle a format 2 ACCEPT verb encountered an unrecognizable PARM list. Action: CAOZDTE is directly invoked from the EOS COBOL program to support format 2 ACCEPT. The PARM list passed to CAOZDTE from the generated EOS COBOL code was not valid. Probable causes include corrupted EOS COBOL program storage or a logic error in CAOZDTE. This is a severe error. This message is produced just before the transaction is abended with a RX23 abend. For more information, see CAPZ023E (see page 171). Chapter 2: Messages 191 CAPxyyyz Messages CAPZ147E NON ZERO RETURN CODE ENCOUNTERED FROM CAOZT1FT. Reason: The EOS routine to handle a format 2 ACCEPT verb received a nonzero return code from EOS routine CAOZT1FT. Action: CAOZDTE is directly invoked from the EOS COBOL program to support format 2 ACCEPT. CAOZDTE invoked EOS support routine CAOZT1FT which passed a nonzero return code to CAOZDTE. This is a severe error. This message is produced just before the transaction is abended with a RX23 abend. For more information, see CAPZ023E (see page 171). CAPZ150E RECURSIVE CALL WAS ATTEMPTED TO PROGRAM ???????? WHICH WAS ACTIVE. Reason: COBOL does not permit recursive entries into programs that have not terminated. Action: This is a severe user application error. The transaction is abended. This problem can occur when program A calls program B and program B calls program A. CAPZ151E INVALID SIGN CHARACTERS WAS DETECTED IN ???????? AT ??????. Reason: Function was attempted on data item defined with a separate sign, the value sign was neither (+) or (-). Action: This is a severe user application error. The transaction is abended. This problem can occur when using the redefine clause combined with a group move. The sign position may never have been initialized. 192 Message Reference Guide CAPxyyyz Messages CAPZ152W HIGH ORDER DIGIT TRUNC. IN PROGRAM ???????? ON LINE ??????. Reason: COBOL generated code has truncated an intermediate value in a arithmetic calculation to 30 digits. Action: This is a warning message. The message is logged and execution of the program continues. CAPZ153E FLOW OF CONTROL WENT BEYOND THE LAST LINE OF PROGRAM ????????. Reason: Control went through the last line of the program. Action: This is a severe user application error. The transaction is abended. Check the placement of the STOP, GOBACK, or EXIT verb. Flow of control may have fallen into to the last paragraph of the program. CAPZ154E INVALID OVERPUNCH SIGN WAS DETECTED IN ???????? ON LINE ?????? Reason: Function was attempted on a data item defined on a over-punch sign. Incorrect value was in the sign field. Action: This is a severe user application error. The transaction is abended. This problem can occur when using the redefine clause combined with a group move. The sign position may never have been initialized. Chapter 2: Messages 193 CAPxyyyz Messages CAPZ155E INVALID SEPARATE SIGN WAS DETECTED IN ???????? ON LINE ?????? Reason: Function was attempted on a data item defined with a separate sign. Incorrect value was in the sign field. Action: This is a severe user application error. The transaction is abended. This problem can occur when using the redefine clause combined with a group move. The sign position may never have been initialized. CAPZ156E OVERFLOW IN FP. CONV. IN PROGRAM ???????? AT DISP. ??????. Reason: A generated number was too large for floating point. Action: This is a severe user application error. The transaction is abended. Prepare the program for such numbers. CAPZ157W OVERFLOW IN FP. CONV. IN PROGRAM ???????? AT DISP. ?????? RESULT TRUNCATED. Reason: High-order truncation occurred in a conversion from floating point to fixed point. High-order digits were truncated. Action: This is a warning message, data may be truncated. 194 Message Reference Guide CAPxyyyz Messages CAPZ158W OVERFLOW IN FP. CONV. IN PROGRAM ???????? AT DISP. ?????? RESULT IS ZERO. Reason: High-order truncation occurred in a conversion from floating point to fixed point. High-order digits were truncated. Action: This is a warning message, data may be truncated. CAPZ159W EXPONENT GT. NINE DIGITS IN ???????? AT ?????? RESULT IS ZERO. Reason: Fixed Point Exponents can contain a maximum of nine digits. Action: This is a warning message, data may be truncated. CAPZ160E INVALID SIGN IN NUMERIC EDITED FIELD IN ???????? AT LINE ??????. Reason: A move was attempted from a signed numeric edited field to a signed numeric or numeric edited field when the sign position in the sending field was not valid. Action: This is a severe user application error. The transaction is abended. Ensure the data in the sending field is valid. CAPZ161E RECURSIVE CALL TO ACTIVE PROGRAM ???????? COMPILATION UNIT ????????. Reason: COBOL does not permit recursive entries into programs that have not terminated. Action: This is a severe user application error. The transaction is abended. This problem can occur when program A calls program B and program B calls program A. Chapter 2: Messages 195 CAPxyyyz Messages CAPZ162E CANCEL OF ACTIVE PROGRAM ???????? IN COMPILATION UNIT ????????. Reason: A cancel was attempted on a activE INTERNAL program. This will occur if program A call internal program B and program B calls program A. Action: This is a severe user application error. The transaction is abended. Check your logic to see where you are canceling an active program. CAPZ163E REF. MOD. OUTSIDE DATA ITEM, LINE ??????, REF VALUE ???????? Reason: The reference modification starting value was not within the bounds of the data item. Action: This is a severe user application error. The transaction is abended. Check the reference modification starting value. CAPZ164E NON POSITIVE REF. MOD. LENGTH ON LINE ?????? VALUE ??????. Reason: A zero or negative value was found in the reference modification length field. Action: This is a severe user application error. The transaction is abended. Check the reference modification length value. 196 Message Reference Guide CAPxyyyz Messages CAPZ165E REF. MOD. WAS MADE BEYOND RT. CHAR. ON LINE ??????. Reason: The reference modification start value along with the length value referenced an address beyond the data field. Action: This is a severe user application error. The transaction is abended. Check the reference modification length value plus start value. CAPZ166W INSPECT REPLACING BY FIELD GT. 1 IN ???????? AT LINE ??????. Reason: The field within the character phases of the replacing operand can only be one byte in length. The length value is assumed to be one. Action: Review the inspect verb and make the appropriate corrections. CAPZ167W INSPECT DATA ITEMS LENGTHS NOT EQUAL AT DISP. ??????. Reason: The data items for REPLACING or CONVERTING phrase in the inspect verb are not equal in length. The shorter length will be used. Action: Make the operands of equal length. CAPZ168E REF. MOD. OUTSIDE RESULT IN LINE ??????. Reason: The reference modification starting value was not within the bounds of the data item. Action: This is a severe user application error. The transaction is abended. Check the reference modification starting value. Chapter 2: Messages 197 CAPHCyyyz Messages CAPZ169E NON POSITIVE REF. MOD. LENGTH ON LINE ?????? Reason: A zero or negative value was found in the reference modification length field. Action: This is a severe user application error. The transaction is abended. Check the reference modification length value. CAPZ170E NON POSITIVE REF. MOD. LENGTH ON LINE ?????? Reason: The reference modification start value along with the length value referenced an address beyond the data field. Action: This is a severe user application error. The transaction is abended. Check the reference modification length value plus start value. CAPHCyyyz Messages This section lists the CAPHCyyyz messages where CAP is the message prefix for CA Optimizer/II. For more information about the message format for these messages, see Message Format (see page 7). CAPHC001I The CA Optimizer/II repository file prtlib.name is at nn.n% capacity. CA Optimizer/II is capable of capturing future abend reports to facilitate rapid problem diagnosis. This will help ensure normal business processes complete in a timely manner. Reason: The CA Optimizer/II health check program CAOCHCHK has performed a check on the PRTLIB file and has found the file to be within safe capacity levels. Action: No action is required. 198 Message Reference Guide CAPHCyyyz Messages CAPHC001W CA Optimizer/II repository file is nearing capacity. File prtlib.name is at nn.n% capacity. If the repository becomes full, future abend reports will not be captured. Reason: The index file has met or exceeded the capacity trigger set in the CAOUDFRX options table parameter PRTLHCT=. The CA Optimizer/II PRTLIB file is filling up and may not have the capacity to save future abend reports. Action: The CA Optimizer/II repository file must be maintained using utility program CAOUPRTU. Procedure CAIPRTU can be used to execute the utility to copy or delete dump reports from the repository file to free space for future abend reports. Chapter 2: Messages 199 Chapter 3: Abend Codes This chapter describes the abend codes issued by CA Optimizer/II. This section contains the following topics: Abend Codes (see page 201) U1090 (see page 201) Abend Codes All user abend codes issued by CA Optimizer/II (with the exception of those issued by EOS) range from 0001 to 2999. The codes 0001 to 0999 refer to compile/optimize-time components. The codes 1000 to 2999 refer to runtime components. For those components having abend codes from 1000 to 2999, the rightmost three digits form the yyy of the message number corresponding to the abend code. Every abend that causes a message to be produced is documented for use. The following abend code issued by CA Optimizer/II does not have a corresponding message: U1090 Reason: Insufficient storage available for this execution. Action: Run is terminated. If possible, rerun the job with a larger region. Chapter 3: Abend Codes 201