6.5 System Automation for OS390 | ASP.NET for Web Designers

< Day Day Up >

6.5 System Automation for OS/390

The following describe the log streams used by System Automation for OS/390 and their characteristics.

6.5.1 Functional description

The Automation Manager optionally uses two log streams: the History log stream where it writes the work items that have been processed and the Message log stream where application message are written from the Automation Manager itself and the Netview Agents.

In addition to these two log streams, APAR OW56107 introduced a third log stream, the health checker. The SYSOPS function, on interval base, performs checks in the systems and writes the results on this log stream for later retrieval.

These log streams are funnel type log stream where System Automation for OS/390 doesn't perform any trimming on the data but relies on the logger function to remove old records from the log stream. For this reason, you should use RETPD and AUTODELETE keyword on the log stream definition to avoid these log stream from growing unlimited.

Criticality/persistence of data

System Automation for OS/390 uses these log streams to accumulate messages and information on the behavior of the systems to potentially trigger some event or reactions. They are funnel-type log streams, where System Automation writes and the agents can retrieve the data to understand what's happening. System Automation does not manage the records within the log streams: for this reason, you should use a combination of AUTODELETE and RETPD to manage these log streams and let logger delete the records after the period of time you decide you might need to keep the data for your installation.

In a multi systems sysplex, it is preferred to have these log streams defined as coupling facility based log streams because it is possible to record data and to view data for each system anywhere in the sysplex. In a monoplex or in a single system sysplex, DASD-only log stream can be a good alternative configuration.

Log stream sizing

The initial recommendation on how to size the System Automation for OS/390 interim storage is that you can start with two structures, each with a size of about 8MB in a Coupling Facility or a 2000 block if you are using DASD-only log stream and use SMF88 to verify how accurate this configuration is for your installation.

One structure should be shared between the History log stream and the Message log and the other dedicated to the Health Checker log stream. If you are not contraint, you can also dedicate a coupling facility structure to each log stream.

6.5.2 Definition

Subsystem definitions

There are no definition at subsystem levels since the name of the log streams are fixed. When System Automation for OS/390 initializes, it connects to these log streams.

The names of the log streams are:

HSA.MESSAGE.LOG, HSA.WORKITEM.HISTORY and ING.HEALTH.CHECKER.HISTORY

Structure definition in the CFRM Policy for the SAFO for OS/390

Example 6-39: Structure definitions sample

 //SAFOLOG JOB CLASS=A,MSGCLASS=A //POLICY EXEC PGM=IXCMIAPU //SYSPRINT DD SYSOUT=A //SYSIN DD *    DATA TYPE(CFRM)    STRUCTURE NAME(HSA_LOG)       SIZE(16384)       INITSIZE(8192)       FULLTHRESHOLD(0)       PREFLIST(FACIL02, FACIL01)    STRUCTURE NAME(ING_HIST)       SIZE(16384)       INITSIZE(8192)       FULLTHRESHOLD(0)       PREFLIST(FACIL02, FACIL01)

Logger definitions

Example 6-40 shows how to define the log streams in the LOGR policy.

Example 6-40: System Automation for OS/390 log stream sample

 //SAFOLOG JOB CLASS=A,MSGCLASS=A //POLICY EXEC PGM=IXCMIAPU //SYSPRINT DD SYSOUT=A //SYSIN DD *    DATA TYPE(LOGR) DEFINE STRUCTURE NAME(HSA_LOG)        LOGSNUM(2)        MAXBUFSIZE(65532)        AVGBUFSIZE(1024) DEFINE STRUCTURE NAME(ING_HIST)        LOGSNUM(1)        MAXBUFSIZE(65532)        AVGBUFSIZE(1024)    DEFINE LOGSTREAM NAME(HSA.MESSAGE.LOG)       STRUCTNAME(HSA_LOG)       LS_DATACLAS(LOGR24K)       HLQ(IXGLOGR)       LS_SIZE(1024)       LOWOFFLOAD(0)       HIGHOFFLOAD(80)       STG_DUPLEX(NO)       RETPD(7)       AUTODELETE(YES)       OFFLOADRECALL(YES)       DASDONLY(NO)    DEFINE LOGSTREAM NAME(HSA.WORKITEM.HISTORY)       STRUCTNAME(HSA_LOG)       LS_DATACLAS(LOGR24K)       HLQ(IXGLOGR)       LS_SIZE(1024)       LOWOFFLOAD(0)       HIGHOFFLOAD(80)       STG_DUPLEX(NO)       RETPD(7)       AUTODELETE(YES)       OFFLOADRECALL(YES)    DEFINE LOGSTREAM NAME(ING.HEALTH.CHECKER.HISTORY)       STRUCTNAME(ING_HIST)       STG_DUPLEX(NO)       LS_DATACLAS(LOGR24K)       LS_SIZE(4096)       AUTODELETE(YES)       RETPD(365)       HLQ(IXGLOGR)       HIGHOFFLOAD(80)       LOWOFFLOAD(0)       DIAG(YES)

Security definitions

You can protect your log streams defining them as resources in the Security Access Facility (SAF) LOGSTRM class. The NetView® agents as well as the automation manager address spaces need UPDATE access to the log streams.

Example 6-41: Sample log streams security definitions

 RDEFINE LOGSTRM ING.HEALTH.CHECKER.HISTORY UACC(READ) RDEFINE LOGSTRM HSA.WORKITEM.HISTORY UACC(READ) RDEFINE LOGSTRM HSA.MESSAGE.LOG UACC(READ) PERMIT ING.HEALTH.CHECK.LOG CLASS(LOGSTRM) ID(Automatin_Manager_userid) ACCESS(UPDATE) PERMIT HSA.WORKITEM.HISTORY CLASS(LOGSTRM) ID(Automation_Manager_userid) ACCESS(UPDATE) PERMIT HSA.MESSAGE.LOG CLASS(LOGSTRM) ID(Automation_Manager_userid) ACCESS(UPDATE) PERMIT ING.HEALTH.CHECK.LOG CLASS(LOGSTRM) ID(Netwiew_Agent_userid) ACCESS(UPDATE) PERMIT HSA.WORKITEM.HISTORY CLASS(LOGSTRM) ID(Netwiew_Agent_userid) ACCESS(UPDATE) PERMIT HSA.MESSAGE.LOG CLASS(LOGSTRM) ID(Netwiew_Agent_userid) ACCESS(UPDATE)

6.5.3 Operational considerations

Start up problem

If System Automation for OS/390 log streams are not defined or are defined not correctly in the logger policy, you can expect the following message at start up time. SA/390 will initialize but the functions that will need the log streams to operate will not be functional:

Example 6-42: MSOPS start up messages

 IXG231I IXGCONN REQUEST=CONNECT TO LOG STREAM ING.HEALTH.CHECKER.HISTORY DID NOT SUCCEED FOR JOB MSOPS1. RETURN CODE: 00000008  REASON CODE: 0000080B  DIAG1: 00000008  DIAG2: 0000F801  DIAG3: 05030004  DIAG4: 05020010 HSAM5403I STREAM ING.HEALTH.CHECKER.HISTORY IS NOT DEFINED IN THE LOGR POLICY. IXG231I IXGCONN REQUEST=CONNECT TO LOG STREAM HSA.MESSAGE.LOG DID NOT SUCCEED FOR JOB MSOPS1.  RETURN CODE: 00000008  REASON CODE: 0000080B DIAG1: 00000008  DIAG2: 0000F801  DIAG3: 05030004  DIAG4: 05020010 HSAM5403I STREAM HSA.MESSAGE.LOG IS NOT DEFINED IN THE LOGR POLICY. IXG231I IXGCONN REQUEST=CONNECT TO LOG STREAM HSA.WORKITEM.HISTORY DID NOT SUCCEED FOR JOB MSOPS1.  RETURN CODE: 00000008  REASON CODE: 0000080B  DIAG1: 00000008  DIAG2: 0000F801  DIAG3: 05030004  DIAG4: 05020010 HSAM5403I STREAM HSA.WORKITEM.HISTORY IS NOT DEFINED IN THE LOGR POLICY

6.5.4 Recovery

Data gap in log streams

When System Automation for OS/390 detects a gap in the sequence of logger records, it logically deletes all the data following this gap regardless of the retention period. For example, this can happen when an user manually deletes some logger data sets or offload data sets are allocated with incorrect shareoptions.

6.5.5 Performance

Usually these log streams do not present many concerns from a performance perspective toward the System Automation for OS/390 log stream. After your initial log stream allocation, performance data is produced in a number of forms that can be useful to determine if any adjustments is necessary to your installation:

SMF 88 data produced by the MVS System Logger
SMF 70–78 data produced by various MVS components

There are several tools which aide in the analysis of log stream performance problems.

IXGRPT1 formats and reports the SMF 88 data produced by the MVS System Logger
ERBRMFPP reports on the data captured in the SMF 70 -78 records

Refer to 8.6.4, "IXGRPT1 Field Summary and IXGSMF88 Cross Reference" on page 283 on how to use the IXGRPT1 output.

< Day Day Up >