2.2 System Logger installation and setup tasks

---

2.2 System Logger installation and setup tasks

There are a number of requirements that must be taken into account when planning for System Logger and any applications that exploit it. Table 2-1 on page 10 illustrates the steps required to set up System Logger. If you plan on just using DASD-only log streams, only the common setup activities (those on the left side of the table) are necessary; CF-Structure based log stream users will need to complete all the steps listed. These requirements will be discussed further throughout this chapter. For more information about System Logger installation requirements, see z/OS MVS Setting Up a Sysplex, SA22-7625.

Table 2-1: System Logger installation tasks

Common Setup Activities	Additional CF-Structure log stream steps
Sysplex Environment
Need to be in a sysplex environment (PLEXCFG keyword in IEASYSxx) Set up sysplex and LOGR Couple Data Sets and System Logger policy Tailor Parmlib members - IEASYSxx, COUPLExx, IEFSSNxx	Need to be in a Parallel Sysplex environment Need a CF Set up CFRM Couple Data Sets and policy
Log Stream Configuration
Identify types of log streams you will use How many log streams are needed Plan for log stream recovery	Plan structure placement - which log streams will reside in each structure Determine structure sizes Plan for peer connector recovery
Naming Conventions
Log stream names Log stream DASD data set names Add log stream DASD data set names to GRSRNLxx inclusion list	CF structure names
DASD Space
Estimate log stream staging and offload data set sizes Allow for DASD expansion - specify additional DSEXTENTs Plan use of retention period for log streams Set up SMS classes for offload and staging data sets If multisystem sysplex: Need shared catalog(s) Access to DASD volumes Serialization mechanism SHAREOPTIONS(3,3)	Select duplexing method for log stream data dataspace or staging data sets
Security Authorization
IXGLOGR address space needs access to log streams Administrator of LOGR CDS Exploiters of log streams	CFRM CDSs and structures For System Logger address space Administrator of CFRM CDS Exploiters of log stream structures
Activate SMS
Activate System Logger
Establish SMF88 reporting

Important: 

• System Logger requires that the System Managed Storage (SMS) subsystem be active on any system using System Logger. This is true even if you do not use SMS to manage offload or staging data sets, since System Logger uses SMS services to allocate them. If SMS is not active when you attempt to use System Logger, System Logger will issue messages indicating allocation errors and the application will not be able to use the logging function. If you do not use SMS to manage offload or staging data sets, you can set up a minimal configuration to provide an environment for SMS. However, we recommend using SMS to manage System Logger offload and staging data sets, as it allows greater control over how System Logger uses your DASD storage. For more information on SMS, see z/OS DFSMS: Implementing System-Managed Storage, SC26-7407.

• If you have multiple systems in the sysplex, it is normal for System Logger to require access to offload data sets and staging data sets from multiple systems; for this reason, you must specify SHAREOPTIONS(3,3) for those data sets. Incorrect SHAREOPTIONS is a common problem among users of System Logger. If you have the PTF for APAR OW56438 installed, look for messages IXG267I and IXG268I which indicate incorrect SHAREOPTIONS; if you are running without the OW56438 PTF, look for IEC161I and System Logger exploiter messages.

---