Post Installation tasks and customization at z/OS

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

Member	Description
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.

//##JOBNAME##   JOB  'DEFAULT','PROCMAN JOB', MSGCLASS=H,CLASS=A          
//* RESOLVED FROM SCELETON HOSJCHKC                    
//JOBLIB   DD  DISP=SHR,DSN=MYDATA.SMARTJCL.V3R0.LOAD        
//         DD  DISP=SHR,DSN=USER.PM.LOAD                      
//DEL      EXEC PGM=IDCAMS                             
//SYSPRINT DD  DUMMY                                   
//SYSIN    DD  *                                       
 DELETE ##HOSXOUT##                                    
 DELETE ##SYSPRINT##                                   
 DELETE ##SYSTSPRT##                                   
 DELETE ##JCKSUMO##                                    
 DELETE ##JCKDTLO##                                    
 IF MAXCC=8 THEN SET MAXCC = 0                         
/*                                                     
//RFMT     EXEC PGM=JCKIRFMT,REGION=0M                          
//SYSIN    DD  DISP=SHR,DSN=SYS1.SMARTJCL.V3R0.PARM(JCKKPARM)  
//         DD  *                                       
    USE-SRI=N                                          
    USE-HOS=N                                          
//##JUPJINAME-R## DD DISP=SHR,DSN=##JUPJIDSN-R##               
………………………………..          

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.

Member	Description	Used DD
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