Running an invalid data detection scan

Edit online

The invalid data detection scan is a dynamic scan that looks at a specific COBOL batch application. This topic explains the input fields required to run the scan.

Invalid data detection report

Important: For the best results, ensure that your application is compiled with COBOL 6 with the following invalid data detection options enabled:

NUMCHECK
SSRANGE
PARMCHECK

Required input fields

COBOL program run JCL location

Name of the sequential file or PDS(E) member that contains the JCL to run the main COBOL program in your application.

COBOL program name

Name of the main COBOL program in your application that gets run directly from the JCL in JCLNAME.

Note: The application scan requires READ and EXECUTE access for the application. To learn more about these permissions and how to change them, refer to Protecting a data set. To learn more about universal access, refer to Universal access authority (UACC) for data sets

CBUINIT launcher program location

Data set name where CBUINIT is located. Contact your system programmer if you need more details.

Profiler data location

Data set name where the profiling report for your application will be generated.

You can allocate the data set using the recommended parameters listed in the following table:


Data set	Recommended allocation parameters
`hlq.CUAOUT.SYSPROFD`	Space units: CYLS Primary quantity: 5 Secondary quantity: 10 Directory blocks: 0 Record format: FB Record length: 80 Block size: 27920 Data set name type:

COBOL Upgrade Advisor install location

Data set name where the server component of CUAZ, CBUBE, is installed. Contact your system programmer if you need more details.

COBOL Upgrade Advisor output location

Data set name, including the member name, where the CUAZ output will be stored. The format is QUAL1.QUAL2.QUAL3(MEMBER).

You can allocate the data set using the recommended parameters listed in the following table:


Data set	Recommended allocation parameters
`hlq.CUAZOUT.OUTPUT`	Space units: CYLS Primary quantity: 5 Secondary quantity: 10 Directory blocks: 20 Record format: VB Record length: 32756 Block size: 32760 Data set name type: Library

Runtime message location

Data set name where the output of the runtime messages is stored.

You can allocate the data set using the recommended parameters listed in the following table:


Data set	Recommended allocation parameters
`hlq.CUAZOUT.RUNMSG`	Space units: CYLS Primary quantity: 10 Secondary quantity: 10 Directory blocks: 10 Record format: FB Record length: 133 Block size: 27930 Data set name type: Library

Advanced input fields

These input fields are automatically populated by CUAZ, and can be customized as necessary.

CUAZReportGenerator.py program path: The UNIX path to the CUAZReportGenerator.py Python program. The default SMP/E installed location is usr/lpp/IBM/cbu/v1r1/pytools. Contact your system programmer if you need more details.
Python install location: The location of the Python executable that runs the script. The default SMP/E installed location is /usr/lpp/IBM/cyp/v3rXX/pyz/bin/Python3, where XX is the Python 3 version. Contact your system programmer if you need more details.
Job name: Name of the job to be submitted by the launcher. The default is USERID, where CUAZ replaces this with the USERID detected with your current account ID. The job name can be changed to follow a different naming scheme.
HLQ: Name of a temporary data set high-level qualifier. The default is USERID, where CUAZ replaces this with the USERID detected with your current account ID. The HLQ can be changed to follow a different naming scheme.
Catalogued JCL procedure location: Name of the sequential file/library member containing the cataloged procedure that executes the PGMNAME program.

Application summary

Verify that the application specified for the scan is correct, and provide the output report name.

Optionally, select Edit JCL to modify the JCL before submitting the invalid data detection scan. Any changes that you make to the JCL apply only to the current scan.

Source location settings

These input fields are required to enable source code linking to your code or copybook.

Source file location: Data set name where the source location of the code is stored.
Listing location: Data set name where the listing of the code is stored.

Note:

If the checkbox for Use the same source file and listing locations for all programs is selected, COBOL Upgrade Advisor for z/OS® uses the same locations for any other source line that is opened.

If a source line is opened from another location, an error will display. To reopen the source location settings:

In the VS Code search bar, use the show and run command function to search for IBM COBOL Upgrade Advisor for z/OS: Reset Source Location.
Select IBM COBOL Upgrade Advisor for z/OS: Reset Source Location.
This reopens the source location settings.

If the checkbox is deselected, the next source line opened reopens the source location settings. Your last entered locations are automatically populated in the source file location and listing file location.