Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Please see Setting up TLS Communication
With the ProcMan zOS installation, an administration dialog is also installed. With this dialog, the ProcMan VSAM databases can be viewed and changed, as well as a syntax check of the Rules can be performed. For Rule syntax check, the included Edit macro "RULE" can be used.
In the installed CLIST / REXX library, execute the member PRCX with "EX" (execute).
The following dialog appears:
Rule syntax checking, checks the correct spelling of Rule parameters, setting commas and setting semicolon at the end of the Rule. Furthermore, the Rules numbering is displayed with “ISPF NOTE” lines.
After entering “S”, the dialog for entering the library and the member is displayed.
After entering Rule library name and member name have been specified, the member will be displayed in ISPF-Editor.
If Rules using the table function, the corresponding data must be loaded into a VSAM file with a management job. The contents of this VSAM file can be displayed with the dialog.
After entering “C”, the dialog for entering the name of the VSAM dataset is displayed.
After entering the file name and ENTER an overview of loaded tables is displayed.
By entering “S” the data can be displayed in more detail
Each data has the length of 50 bytes. There are 7 data fields. To see the data in full length, enter a “S” in front of the line.
DTDAT1 to DTDAT7 is not a clear header. With administration run new header, for each column can be set.
If you are using ProcMan Job-Control module then HORIZONT’s SmartJCL must be installed first.
If HORILST is used for communication, SmartJCL Remote Check must also be installed.
Since ProcMan z/OS part version 5.1, TLS is mandatory. Please see Setting up TLS Communication
Unpack the installation file on Windows and transfer to z/OS
Adjust template jobs for JCL analysis / generation
Post installation: define basic JCL Rules
The Job-Control which is used by ProcMan Web-Dialog was stored in library HLQ.PROCMAN.SKELS. After installation, you will find all members for sample client HORIZONT. For a new client all example members must be copied with a new name. These new members must be modified according to your company's requirements.
It has proven itself to use the first two characters in member names as client abbreviation. You will be asked for that during the installation dialog. E.g. HO = HORIZONT
HOJADHOC
ADHOC IWS process reformat
HOJAPPT
DSN copy process
HOJAPPV
DSN copy process
HOJCHKC
Verify JCL with Handover type CHANGE
HOJCHKN
Verify JCL with handover type NEW
HOJCPY
Copy members into target library.
HOJDEL
Delete datasets or member
HOJDSNF
Get dataset list
HOJEDT
Jcl Check with “JCL-Check” button. Without Rules.
HOJEDTA
Verify JCL after edit at approve
HOJEDTF
The final JCL check
HOJGDGL
Get list GDG entries
HOJGTYP
Get DSN attributes
HOJJCKT
JCL check with previous IWS variable substitution
HOJOD933
IWS process variable substitution
HOJOSJ
JCL check with TWS variable substitution
HOJPAR1
Used by „Change by Parameters“ function
HOJPAR2
Used by „Change by Parameters“ function
HOJREF
Reformat JCL
HOJREND
HOJUNI
Example job for universal process
HOMEDOW
Fast TSO Export
HOMEUPL
Fast TSO Import
HOOJJCK
IWS process. JCL check with previous IWS variable substitution
HOOJJCKF
IWS process. Final JCL check with previous IWS variable substitution
HOPJCK
Verify procedure IWS variable substitution PO
HOPJCKF
Verify procedure IWS variable substitution fast
HOPCHKC
Verify procedure with handover type CHANGE
HOPCHKN
Verify procedure with handover type NEW
HOPEDT
Check procedure with “JCL-Check” button. Without Rules.
HOPEDTA
Verify procedure after edit at approve
HOPEDTF
The final procedure check
HOPREF
Reformat procedure
The members are skeleton JCL for the ProcMan programs. The dataset names and member names must also be defined in configuration files on ProcMan windows server.
Below you will see an example skeleton.
Variables that are replaced by ProcMan are limited with ‘##’ at the beginning and at the end of a variable. Do not modify or delete these variables.
There are example member with Rules and parameter stored in library HLQ.PROCMAN.RULES. These members must be adapted to your Requirements. The importance of the members and the parameters are described in the following chapters.
xxSANA01
Will be used for JCL analysis and for definition of form attributes
PRXPRG
xxSGEN01
Will be used for JCL generation. Depending on the Rules the user is forced later on to make entries in the ProcMan web dialog.
PRCPRG
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
Copy PRXINST.ZIP to a temporary Windows directory and unzip it. The following files will be created:
PRXINST.BIN
The unzipped file must be transmitted to the HOST by file transfer.
PREFIX.XMITINST
RECFM=FB,LRECL=80,BLKSIZE=3120,SPACE=(TRK,100,100),DSORG=PS
With a file transfer program, you must send the following PC files to the HOST.
PMZBINST.BIN
PREFIX.XMITINST
Transfer mode must be binary.
The options ASCII and CLRF are not allowed.
RECEIVE INDSNAME(‘PREFIX.XMITINST’)
PREFIX.XMITINST
‘HLQ.PROCMAN.VxRxFIX.XMIT.INSTALL’
HLQ.PROCMAN.VxRxFIX.INSTALL(PMJFXnn).
The following files will be created:
HLQ.PROCMAN.CHECK.VSAM
User
Batch Job
HLQ.PROCMAN.CHECK.ISPF
User
ISPF Dialog
HLQ.PROCMAN.EMAC
Administrator
Edit Macro
HLQ.PROCMAN.EXAMPLE.CNTL
Administrator
Batch Job
HLQ.PROCMAN.MACRO.HOSXIN
Administrator
Edit Macro
HLQ.PROCMAN.LOG
User
ISPF Dialog
HLQ.PROCMAN.TABLES
User
ISPF Dialog
HLQ.PROCMAN.JCL
User
Batch Job
HLQ.PROCMAN.LOAD
Administrator
Batch Job
HLQ.PROCMAN.LOAD.REXX
Administrator
ISPF Dialog
HLQ.PROCMAN.MESSAGE
Administrator
ISPF Dialog
HLQ.PROCMAN.JCL.MESSAGE
User
Batch Job
HLQ.PROCMAN.PANELS
Administrator
ISPF Dialog
HLQ.PROCMAN.PARM
User
Batch Job + ISPF Dialog
HLQ.PROCMAN.REXX
Administrator
Batch Job + ISPF Dialog
HLQ.PROCMAN.RULES
USER
Batch Job
HLQ.PROCMAN.SKELS
USER
Batch Job
HLQ.PROCMAN.SYSIN
USER
Batch Job
HLQ.PROCMAN.TEMP.CNTL
Administrator
Temp. for installation
Copy PRXINST.ZIP to a temporary Windows directory and unzip it. The following files will be created:
PRXINST.BIN
The unzipped file must be transmitted to the HOST by file transfer.
With a file transfer program, you must send the following PC files to the HOST.
Transfer mode must be binary.
The ASCII and CLRF options must not be used.
RECEIVE INDSNAME(‘PREFIX.XMITINST’)
Start the installation by executing the following member with line command=EX HLQ.PROCMAN.VxRx.INSTALL(PMIXINST).
It displays the menu where you select the components you want to install. The following screenshots describe the installation dialogs for all components.
ProcMan zOS installation with IWS variable substitution If SmartJCL jobs will be started with IWS variable substitution some IWS parameter must be entered.
Enter the dataset name of your transfer dataset. Normally the name is inserted automatically.
The names of the ISPF Libraries are automatically determined. If the fields are empty you have to type the correct dataset names manually. In some system environments is an automatic determination not possible.
SMARTJCL must be installed first. Enter the name of the SMARTJCL parameter library where member JCKXPARM exists. This member is analysed in order to obtain the required parameter.
Enter the dataset names for your installation. HLQ is a placeholder and the dataset names are just a suggestion.
You can customize the names according to your Requirements.
Enter the dataset names for your installation. HLQ is a placeholder and the dataset names are just a suggestion.
You can customize the names according to your Requirements.
In a typical installation software product libraries and user libraries are separated by dataset qualifier and permission. It is called user datasets because the software user has maintained these datasets and not the person who made the installation.
If you are using ProcMan with IWS handover you have to type the IWS datasets too. Within IWS processes can also job control actions are invoked. The entered parameter will be used for IWS JCL templates.
ProcMan JCL Web dialog will submit SmartJCL jobs. These jobs will be stored as templates at zOS. To generate these templates, you need to specify certain parameters.
DB2 parameter are used for an administration batch job. This job will fill DB2 table FORMCONT. This table will be used for checks with web dialog.
Please enter the Job Control parameter for installation job. After job was generate it will be shown with ISPF edit.
If you press ENTER the program generates all template jobs a temporary library. Copying to the destination library will be done by the installation job.
After the members have been generated, you will see the installation job in Edit-Modus. Enter “SUBMIT” to start the Job. The Job should end with Severity Code 0. The two generated jobs are also stored in the installation library. Member names are INSJOB1 and INSJOB2.
The update files can be downloaded from
The installation files can be downloaded from
PREFIX.XMITINST
RECFM=FB,LRECL=80,BLKSIZE=3120,SPACE=(TRK,100,100),DSORG=PS
PRXINST.BIN
PREFIX.XMITINST
PREFIX.XMITINST
‘HLQ.PROCMAN.VxRx.XMIT.INSTALL’
The description of the syntax and the help function are now in a separate PDF manual. The reason for this is that this PDF manual is created directly from the windows online help.
The file "ProcMan - JCL Rules.PDF" and "ProcMan -JCL Rules.chm" are included in the delivery.
The online help is new and did not exist before.
It makes searching for specific content extremely easy and offers practical examples for many functions. These are constantly being added to.
The online help file is a compiled HTML file. Often there are problems with the display of subtopics in the browser program. For this reason, the online help file should be saved locally.
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.
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.
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)
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 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.