Creating and uploading data files
Some input parameters to the z/OS® source
code application require a data file. Data files must be created on the local workstation and copied
in binary format to a directory in z/OS
UNIX System Services.
For information about
creating specific types of data files, see the links at the end of this topic.
Types of data files
The Table 1 table shows the types of data
files and the input parameter for which each type of data file is needed. No
additional data files are needed for baseline analysis configurations. The code review application
for z/OS creates the baseline archive.
| Data file type | File extension | Description | Required | Parameter in the start procedure |
|---|---|---|---|---|
| Rule file | .dat |
Code review rules. | Yes. | RULES |
| CCR file | .ccr |
Definitions of custom code review rules. | If you use any custom code review rules. | CUSTRULE |
| z/OS File System Mapping file1 | .zip |
An archive of z/OS file system mappings. | If you use any nondefault z/OS file system mappings. | EXTMAP |
| Property group file2 | .xml |
SYSLIB entries for copybooks and include files. | If you use any copybooks or include files. | PROPERTY |
|
1You do not need a mapping file if you plan to use the LIST parameter when you run the code review application on z/OS. 2You do not need a property group file if you plan to use the SYSLIB parameter when you run the code review application on z/OS. |
||||
Uploading data files
After you create the data files, copy them in binary format to a directory or directories in z/OS UNIX. To use the data files as input parameters to the code review application, see the comments in the AKGCR procedure.