Troubleshooting
This section lists the different messages found in the JOBLOG and RTI profile of COBOL Upgrade Advisor for z/OS®.
Severity indicators can be any of the following: I, W, E, S, or U.
- I: Informational message (RC=0)
- W: Warning message (RC=4)
- E: Error message (RC=8)
- S: Severe error message (RC=12)
- U: Unrecoverable error message (RC=16)
Launcher messages in the JOBLOG
The COBOL Upgrade Advisor for z/OS launcher messages described in this section are written to the JOBLOG.
Each launcher message in this section has the form CBULnnnX where CBUL indicates that the message is a launcher message, nnn is the message number, and X is the severity indicator.
COBOL Upgrade Advisor for z/OS JCL launcher messages and their details in the JOBLOG
| Message code | Message text | Explanation | System action | User response | Return code |
|---|---|---|---|---|---|
| CBUL001E | Data set “&1” could not be found | One of the CBUINITJ input parameters (JCLNAME, CUAZ, PROF, JSON, or PROCNAME) specifies the nonexistent data set name &1. | The CBUINITJ initialization job fails. | Correct the data set name &1, then rerun the CBUINITJ job. | 8 |
| CBUL002E | Invalid data set “&1” | One of the CBUINITJ input parameters (JCLNAME, CUAZ, PROF, JSON, or PROCNAME) specifies the invalid data set name &1. | The CBUINITJ initialization job fails. | Correct the data set name &1, then rerun the CBUINITJ job. | 8 |
| CBUL003E | No DLM provided in CEEOPTS card | The DLM parameter specified in the source JCL CEEOPTS card has no value assigned. | The CBUINITJ initialization job fails. | Assign DLM value, then rerun the CBUINITJ job. | 8 |
| CBUL004E | No DSN provided in CEEOPTS card | The DSN parameter specified in the source JCL CEEOPTS card has no value assigned. | The CBUINITJ initialization job fails. | Assign DSN value, then rerun the CBUINITJ job. | 8 |
| CBUL005E | Program “&1” not in the step “&2” STEPLIB | The program &1 specified with the CBUINITJ input parameter PGMNAME is not found in any data set concatenated under the STEPLIB DD card of the step &2. However, the step &2 is expected to be the program &1 execution step accordingly with the EXEC card found in this step. | The CBUINITJ initialization job fails. | Ensure that JCL source provided by CBUINITJ input parameter JCLNAME or PROCNAME contains a correct JCL for the step &2 execution, then rerun the CBUINITJ job. | 8 |
| CBUL006E | No EXEC card provided in “&1” | The JCL source located in the data set &1 specified by the CBUINITJ input parameter JCLNAME or PROCNAME does not contain any JCL EXEC card. | The CBUINITJ initialization job fails. | Ensure that data set specified by the jobs CBUINITJ input parameter JCLNAME or PROCNAME is a correct JCL source location, then rerun the CBUINITJ job. | 8 |
| CBUL007E | No JOB card provided in “&1” | No JOB card found in the data set &1 specified as the JCL source location by the CBUINITJ input parameter JCLNAME. | The CBUINITJ initialization job fails. | Ensure that the data set specified by the CBUINITJ input parameter JCLNAME is a correct JCL source, then rerun the CBUINITJ job. | 8 |
| CBUL008E | No step with PGM=”&1” located in “&2” | The JCL source located in the data set &2 specified by the CBUINITJ input parameter JCLNAME or PROCNAME, does not contain any step with the program name &1 specified in the CBUINITJ input parameter PGMNAME. | The CBUINITJ initialization job fails. | Ensure that data set specified by the CBUINITJ input parameter JCLNAME or PROCNAME is a correct JCL source location, then rerun the CBUINITJ job. | 8 |
| CBUL009E | No STEPLIB provided for ”&1” step in “&2” | No STEPLIB card found for the step &1 in the JCL source located in the data set &2 specified by the CBUINITJ input parameter JCLNAME or PROCNAME. In this case, step &1 is expected to be the execution step of the program specified in the CBUINITJ input parameter PGMNAME. | The CBUINITJ initialization job fails. | Ensure that data set specified by the CBUINITJ input parameter JCLNAME or PROCNAME is a correct JCL source location, then rerun the CBUINITJ job. | 8 |
| CBUL010E | Missing parameter | Some of the input parameters have no value assigned. A default value is required at minimum. | The CBUINITJ initialization job fails. | Make sure all parameters have a value assigned. | 8 |
| CBUL011E | Invalid UNIX file path "&1" | The UNIX system file path to program &1 is invalid. | The CBUINITJ job fails. | Correct the file path for &1 and rerun the scan. | 8 |
| CBUL020E | RI buffer is empty, check program "&1" duration. | The RI buffer is empty. CUAZ cannot detect any COBOL programs. | The CBUINITJ job fails. | Increase the program or application runtime, and rerun the scan. Ideally, the application should run for more than CPU 10 seconds. If the issue persists, please contact IBM Support. | 8 |
RTI profile messages
The RTI Profiler messages described in this section are written to the JOBLOG.
Each RTI message in this section has the form CBURnnnX where CBUR indicates that the message is an RTI message, nnn is the message number, and X is the severity indicator.
RTI Profiler messages and their details in the JOBLOG.
| Message code | Message text | Explanation | System action | User response | Return code |
|---|---|---|---|---|---|
| CBUR002S | AUTH REQUEST FAILED (RC="&1",RSN="&2") | The current task has requested to be authorized for the RI facility through HISUSER REQUEST=AUTH with store key 0 to 15, but the request failed with return code &1 and reason code &2. | The RTI Profiler immediately terminates execution and returns to the operating system with a return code of ABEND=S000 U1130. | This message may be issued due to an earlier problem. Correct any problems reported in the JESMSGLG file and retry the RTI Profiler execution. If the problem persists, contact IBM support. | 12 |
| CBUR003S | ATTACHING CBURIDT FAILED (RC="&1") | The ATTACH macro request issued for the CBURIDT module failed with return code &1. | The RTI Profiler immediately terminates execution and returns to the operating system with an ABEND=S000 U1130. | If the return code in the message is 8, then this may be an indication of a transient environmental error and the RTI Profiler execution can be retried. If this does not resolve the problem, or for any other nonzero return code, contact IBM support. | 12 |
| CBUR004S | CORRUPTED RI BUFFER | The RICHK thread has discovered unrecoverable RI buffer corruption. | The RTI Profiler immediately terminates execution and returns to the operating system with an ABEND=S000 U1130. | It may be an indication of the environmental or machine check error, retry request. If the problem persists, contact IBM support. | 12 |
| CBUR005S | OPENING SYSPROFD FAILED | Opening of the file allocated under the SYSPROFD DD name failed. Possible reasons for this failure could be file corruption, or the file may be held exclusively by another task. | The RTI Profiler immediately terminates execution and returns to the operating system with an ABEND=S000 U1130. | Verify that your SYSPROFD file is correctly allocated and available, then retry RTI Profiler execution. If the problem persists, contact IBM support. | 12 |