Various job control examples are also provided with the installation.
xxSADUMP Process transfer to HORIZONT
xxSJCUST Create SQL for filling DB2 table CUSTOM_DATA
xxSJDELD Deleting temporary process files
xxSJFCNT Create SQL for filling DB2 table FORMCONT
xxSJVSFL Create VSAM Check file for JCL rules
ProcMan zOS activities usually generate temporary files. After ProcMan has read these files, they can be deleted. The attached batch job deletes the data using IWSz control. As soon as a certain creation date is reached, these files are deleted.
Note! A backup, of these files, is not required.
If problems occur in the SmartJCL part of ProcMan, it can be very helpful to pull all zOS files used by this ProcMan step and send them to HORIZONT via JIRA ticket.
The XMIT file must be transferred binary and added to the JIRA ticket.
The DB2 table CUSTOM_DATA can be filled using SQL statements. These can be generated with the PRCICUS batch program. Program can read data in CSV format or a FLAT file structure. The input data is described with DD EDEFCMDS. Furthermore, it must be described which data is stored in which column of the DB2 table.
DB2 Structure of CUSTOM_DATA
Job-Control
The EXEC parameter ‘DO’ is used to specify the target table and the parameter ‘MC’ is used to specify the COMMIT frequency.
EDEFCMDS Example CSV
IMPORT_FILE Name of Input file and Member name. Only PO datasets are supported.
IMPORT_FILE_LRECL Record length of Input file. Following LRECL are supported. LRECL 80, 100, 120, 150, 200, 250, 300, 350, 400
IMPORT_TYP CSV or FLAT Typ of IMPORT_FILE
IGNORE_FIRST_LINE TRUE or FALSE If the 1st line contains headings.
SQL_TYP INSERT or DELETE Which type of SQL should be written.
CSV_DELIMITER Each 1 digit character. E.g. ; or , or !
CSV_COLUMNS_n Column number of CSV source data and the target column in CUSTOM_DATA
CSV_KEY Column number of CSV source data which must be unique. In the case of duplicate values, only the 1 entry is used.
Note! Each definition block must be terminated with END1BLOCK.
EDEFCMDS Example FLAT
IMPORT_FILE Name of Input file and Member name. Only PO datasets are supported.- IMPORT_FILE_LRECL Record length of Input file. Following LRECL are supported. LRECL 80, 100, 120, 150, 200, 250, 300, 350, 400
IMPORT_TYP CSV or FLAT Typ of IMPORT_FILE
IGNORE_FIRST_LINE TRUE or FALSE If the 1st line contains headings
SQL_TYP INSERT or DELETE Which type of SQL should be written.
FLAT_COLUMNS_n Column number of FLAT source data and the target column in CUSTOM_DATA
FLAT_KEY Column number of FLAT source data which must be unique. In the case of nn duplicate values, only the 1 entry is used.
FLAT_FILTER Column number of FLAT source data and search value.
The ProcMan JCL rule set offers the option of using check tables. These check tables are saved in a VSAM file. This VSAM file is recreated cyclically so that the latest data is saved. This usually happens every 24 hours when the online ProcMan is no longer being used.
Job-Control
EDEFCMDS description
Parameter 1 Name of the check table
Parameter 2 Name of the Input file (Only PO datasets are supported)
Parameter 3 Name of the Input member name.
Parameter 4 Record length of Input file. Following LRECL are supported. LRECL 80, 100, 120, 150, ZZ 200, 250, 300, 350, 400
Parameter 5 Record format e.g. FB
Parameter 6 LABEL Which data for the label. E.g.
1; 1. Column of input data
1,2; 1. and 2. Column of input data
(1:30); Start in position 1 with length of 30
(1:15;24:3) Start in position 1 with length of 15 and start in position 24 with length of 3
Parameter 7 VALUE Which data for the value. E.g. -1,4,3,2
1. Column of input data for VSAM DATA1
4. Column of input data for VSAM DATA2
3. Column of input data for VSAM DATA3
2. Column of input data for VSAM DATA4
1(53:3),2(48:4),3(57:48);
position 53 length of 3 of input data for VSAM DATA1
position 48 length of 4 of input data for VSAM DATA2
position 57 length of 48 of input data for VSAM DATA3
EDEFTITL description (new title will be shown with the ISPF dialog)
Parameter 1 Name of the check table
Parameter 2 Column number of check table
Parameter 3 New title of column ( instead DATA1, DATA2…..)
The DB2 table FORMCONT can be filled using SQL statements. These can be generated with the PRCIFRM batch program. The input data is described with DD EDEFCMDS.
DB2 Structure of FORMCONT
Job-Control
The EXEC parameter ‘DO’ is used to specify the target table and the parameter ‘MC’ is used to specify the COMMIT frequency.
EDEFCMDS Example
Parameter 1 Name of the Input file (Only PO datasets are supported)
Parameter 2 Name of the Input member name.
Parameter 3 Record length of Input file. Following LRECL are supported. LRECL 80, 100, 120, 150, 200, 250, 300, 350, 400
Parameter 4 Record format e.g. FB
Parameter 5 Statement Typ. E.g. JOB, EXEC or DD
Parameter 6 Name of the Web Form Field
Parameter 7 Name of the Web Form
Parameter 8 Label start position in the input data
Parameter 9 Label length in the input data
Parameter 10 Value start position in the input data
Parameter 11 Value length in the input data
Parameter 12 User start position in the input data (Optional)
Parameter 13 User length in the input data (Optional)