Important note: During the installation of ProcMan or HWM only the file hwm_db_config.php is created automatically and correctly filled. In all other configuration files, where the database connection, alias, DB user, password etc. appear, the values must be set manually.
So the next thing to do is to adjust the hos_db_config.php file e.g. located in c:/horizont/procman/etc/hos_db_config.php.
This configuration file is used to define the database connection from ProcMan to e.g. the DB2 database (in addition to hwm_db_config.php).
In the 'db' section at the very bottom, the correct "prefix", "alias" and "pwd"
(see in the hwm_db_config.php) must be set.
This is one of the most important configuration files in ProcMan!
In the next step, the file c:/horizont/procman/etc/hos_config2.php must be adjusted.
This is the most important file to start with, because in this file most of the configurations for a ProcMan installation come together. E.g., in this file it is defined which systems should be connected with ProcMan and also which environment variables should be used for the processes.
Important recommandation
To simplify long-term administration, it is strongly recommended to create a new file named pm_system_settings.php in the directory /procman/etc/ . This file serves as a central place to define variables that are used in the other configuration files. These variables have to be declared only once in this file and can be changed quickly if necessary, e.g. when deploying new processes from a DEV system to a PROD system.
If the pm_system_settings.php has been created, it must be included in every file in which you want to use the generic variables defined in the pm_system_settings.php file by using require_once.
How the configuration files are dependent on each other is shown in the "Configuration overview" article.
In the section system_mapping systems are defined in an array that should be connected with the ProcMan installation. In this section it is defined which IP is associated with which ID.
Important: Generally, the IP addresses have to be unique! This can be "bypassed" by assigning IP addresses to names in the c:/Windows/System32/drivers/etc/hosts file on the windows server. See the picture below.
For example, at HORIZONT, the z/OS with the IP 192.168.47.14 has to be defined in the section system_mapping. Therefore, we add a variable in the pm_system_settings.php file e.g. named $TEST_ip and assign the value 'TEST' to that variable. That means that the windows server now resolves 'TEST' to the IP 192.168.47.14 because this was set in the hosts file (as shown in the picture above).
In the following example (see picture below), we defined two systems in the hos_config2.php file. If you check the assigned variables' values in the pm_system_settings.php file, you can see that both systems are identical because they have equal IPs. The IP for the system DEV is directly defined in the hos_config2.php file, for the system DEMO the ip is resolved by windows through the c:/windows/system32/drivers/etc/hosts file.
In this section. it is defined which config files for environment definitions should be used. These hos_env_XXX.php files contain environment definitions for processes in ProcMan.
It is recommended to create a seperate hos_env_<module>.php file for every module which is used in an installation, e.g. one for the jcl_proccesses named hos_env_jcl.php, one for IWS/AD processes named hos_env_iws_ad.php, and one for IWS/CP processes named hos_env_iws_cp.php. These files must then be included in the hos_config2.php file.
Important: The definitions in those files need to start at the correct array-layer, make sure not to mess that up, otherwise this can break ProcMan.
The picture below shows an example of three env_config files placed in the directory /etc/env_configs/. One for the JCL module, one for the IWS/AD module and one for the IWS/CP module.
Please see the next article Environment filesof a description of these files.
In this section, it is defined which z/OS user is used for which system with which password. Here it is also highly recommended to use variables defined in the pm_system_settings.php file.
In the section rot_ini_file it is defined which system (see above section system_mapping) uses which .ini file for the communication to the z/OS systems.
Important: After a new installation most probably no .ini file was created. Therefore a new file with the name e.g. horcclnt.ini has to be created. Use the file /procman/etc/horcclnt.ini-dist to make a new copy for your system. If multiple z/OS systems are connected to ProcMan, create multiple files with different names like horcclnt_test.ini or horcclnt_prod.ini .
The example below illustrates two possible communications to a TEST and a PROD system.
The variables starting with $ are e.g. resolved from the pm_system_settings file as this:
The following adjustments have to be made in the .ini files. Row 14: Correct path Row 18: Correct path Row 26: Optional: Adjust log path Row 50: Set the correct host port from the installation of ProcMan z/OS part Row 54: Set the correct member from the installation of ProcMan z/OS part
In the section template_dsn_cntl it is defined, which dataset on the z/OS contains the skeletons for the ProcMan JCL Module.
In the section base_tmp_dsn it is defined, which dataset is used when the ProcMan JCL modules creates outputs. Those members are also defined in the installation of the z/OS part of ProcMan.
To be able to open ProcMan in the browser () the sections system_mapping, environment, zos_tech_user, rot_ini_file as well as base_tmp_dsn and template_dsn_cntl have to be adjusted.
As described in the article before, in the hos_config2.php files, multiple environment files are included.
These hos_env_<module>.php files contain environment settings that are relevant for the processes in ProcMan.
In most cases, there should also be a hos_env_general.php file. This environment file can be seen as a fallback and contains environment settings that should be used for all clients and processes if no other environment files have been defined.
For a detailed description of all the environment parameters of the hos_config2.php file, please see:
In most installations, processes require individual environment configurations.
See the code example below which shows an example of a hos_env_jcl.php file.
From line 3 to 51 a general environment config is set.
From line 58 to the end, the environment setting for a specific process with the name JCL_INIT_CO is set. This means that this config will "overwrite" the lines 3 to 51, because it is process specific.
