Required authorizations

Local Windows administrator user to install the ProcMan programs on the Server.

DBADMIN to create ProcMan’s database.

To install additional HORIZONT products like SmartJCL: “z/OS system programmer rights” (to update proclibs, assign APF rights etc.) ProcMan requires a technical RACF user id to execute programs on z/OS. That user must have following rights:

• Select/Insert/Update/Delete on ProcMan’s DB2 tables.

• Run SmartJCL Jobs

• Read and write to ProcMan’s JCL libraries.

• Read XINFO DB2 tables (optional)

If IWSz handover are used

• Read IWSz VSAM Files AD, WS, LT

• Update IWSz AD/CP by PIF

If Control-M handover are used, the technical user needs:

• full access to read/update Folders in the Control-M Enterprise Manager

• permission to use the Automation API and Control-M Reports

ProcMan JCL Module creates job logs and needs to read these logs from spool on z/OS. Therefor a JES Hold Class must be provided with following parameters:

// OUTCLASS(T) BLNKTRNC=YES,        /* TRUNCATE TRAILING BLANKS          wnc*/
// OUTDISP=(HOLD,HOLD),             /* OUT disp                PRINT    ownc*/         
// OUTPUT=PRINT,                    /* Print Class             PRINT     wnc*/         
// TRKCELL=YES                      /* Track-Cell this Class   NOTRKCEL  wnc*/    

Required firewall authorizations

• Open port ProcMan Server database server (port 446)

• Open port ProcMan Server PC-Clients via https (port 443) or http (port 80)

• Open port ProcMan Server LDAP server (port 389) or Open port ProcMan Server LDAPS (SSL encrypted) server (port 636)

• Open port ProcMan Server and z/OS System(s) / HORILST (port 20000)

• Open port ProcMan Server and Control-M automation API

• Open port ProcMan Server SMTP server (port 25) orOpen port ProcMan Server SMTPS (SSL encrypted) server (port 465)

The ports mentioned above are the defaults. The ports can be changed to your needs.

The customer has to prepare/generate an X.509v3 certificate (and the key file) to setup https communication between the client PC and the ProcMan Server. In addition, the issuer's certificate (so-called CA certificate) must be installed on the client PCs.

Host-Mapping for the Windows Server (DNS names for the host IP Addresses).