Step 9: Configure the System Logger

SysOps	ProcOps
*

Although this step is optional, it is, however, recommended. The automation manager writes history information to the z/OS system logger and the automation agents read from it.

If you do not perform this step, users will not get any output from the INGHIST commands.

Notes:

The LOGSTREAM parameter in the HSAPRMxx parmlib member is set to YES by default. The automation manager connects to the logger address space at initialization.
If you set the LOGSTREAM parameter to NO, no access is established to the system logger. Step 9: Configure the System Logger is then unnecessary.
If you set the LOGSTREAM parameter to GRPID, the automation manager connects to the logger address space at initialization time. However, the log streams to which the automation manager connects depend on the value of the GRPID parameter. For more information, see Syntax for HSAPRM00.

To exploit the system logger, the following must be fulfilled:

Systems in a sysplex must run in XCF mode and the following must be defined in SYS1.PARMLIB(IEASYSxx):
```
PLEXCFG=MULTISYSTEM
```
For standalone systems the following must be defined in SYS1.PARMLIB(IEASYSxx):
```
PLEXCFG=MONOPLEX
```

Next, the LOGR couple data sets must be formatted, if this has not already been done. For this task you can use the sample JCL provided in the HSAJFCDS member of the sample library.

Use the following sample JCLs to define the log stream in different environments:

For a single system environment, use the sample JCL provided in member HSAJDLGM (for the automation manager)
For a sysplex, use the sample JCL provided in member HSAJDLGS (for the automation manager)

In both cases you may want to adapt the HLQ parameter in the LOGR policy according to your environment. The default is IXGLOGR. Use the corresponding HSAJDxxx members as input and make the changes accordingly.

Note: Do not change the provided MAXBUFSIZE values in the HSAJDxxx job. The provided values match the size of the expected data.

For a sysplex environment, you must additionally add the log structures to the CFRM policy:

STRUCTURE   NAME(HSA_LOG)
            SIZE(17408)
            FULLTHRESHOLD(0)
            PREFLIST(cfname,cfname)

In this CFRM policy, you have to adapt the PREFLIST for structure HSA_LOG, if you are setting up the system logger. Also adapt the SIZE parameter to a recommended minimum of 17408 K (17M). If the size specified was not large enough, you may see message IXL015I STRUCTURE ALLOCATION INFORMATION. Since System Logger manages the space of the structure, there is no need for additional monitoring. The parameter FULLTHRESHOLD(0) disables XES monitoring and potential IXC585E messages.

The system logger must be authorized. If it is not yet assigned either privileged or trusted RACF® status, or both, refer to chapter Planning for System Logger Applications in z/OS MVS Setting Up a Sysplex for more information about how to define authorization to system logger resources. The names of the system logger resources used by SA z/OS are HSA.MESSAGE.LOG and HSA.WORKITEM.HISTORY.

The address spaces of the NetView agents and automation manager need to be authorized to access the log streams. They need update access for the following:

RESOURCE(logstream_name)
CLASS(LOGSTRM)

Where logstream_name stands for HSA.MESSAGE.LOG and HSA.WORKITEM.HISTORY.

For further information see section Define Authorization to System Logger Resources in z/OS MVS Setting Up a Sysplex.

Now activate the couple data sets via the console commands:

     SETXCF COUPLE,TYPE=LOGR,PCOUPLE=(primary_couple_data_set)
     SETXCF COUPLE,TYPE=LOGR,ACOUPLE=(alternate_couple_data_set)

For a sysplex, after defining the new structure in the CFRM policy, activate the CFRM policy via:

SETXCF START,POLICY,TYPE=CFRM,POLNAME=policy_name