Customizing the started task procedure CFZCIM
You can start the CIM server via started task procedure CFZCIM.
A sample of CFZCIM is shipped with the default PROCLIB.
To customize CFZCIM,
- _ Include CFZCIM in your PROCLIB concatenation.
- _ When you use the default installation directory /usr/lpp/wbem, you need not modify CFZCIM or cimserver.env.
Else, you need to customize the procedure in the DD statements and
also update the cimserver.env file installed in /etc/wbem to match the correct installation paths
for the CIM server.
- _ The DDNAMEs STDOUT and STDERR in path /var/wbem/logs are used to redirect the output
from the console into the UNIX file
system files cimserver.out and cimserver.err. When
the started task is ended, job steps two and three copy the console
output to the JCL job log.
- _ The DDNAME STDENV points to the hierarchical file system
file containing environment variables required to run the CIM server.
For running the CIM server as a started task, the environment variables
are set in file cimserver.env located in the /etc/wbem hierarchical file system directory.
See Setting the CIM server environment variables for details on how to set environment variables
for the z/OS CIM server.
- _ To run the CIM server with a user ID for which the security setup
has been completed, either set up the STARTED class or use the started
procedures table (ICHRIN03).
For further
details refer to z/OS Security Server RACF Security Administrator’s Guide, topic "Assigning RACF® User
IDs to Started Procedures".
Example of the RACF commands required to set up the CIM server for
the STARTED class:
Example:
SETROPTS RACLIST(STARTED)
RDEFINE STARTED CFZCIM.* STDATA(USER(CFZSRV) GROUP(CFZSRVGP))
SETROPTS RACLIST(STARTED) REFRESH
|