Log Management

OpenFrame generates a number of log files during operation. These files are used to monitor the overall system robustness and reproduce problems for troubleshooting when a critical error occurs.

This appendix describes the types of logs generated by the OpenFrame system and the log contents.

1. Configuration

The locations of system log, operation log and data log files of OpenFrame can be specified in the VALUE item of: LOG_DIR in the DIRECTORY section of the ofsys subject; LOG_FILE_CREAT_MODE from the LOG section from OpenFrame Configuration.

For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide.

2. OpenFrame Logs

OpenFrame generates four types of log files: service, system, command, and data logs.

Log Description

Service Log

Records messages from the Tmax server that are produced by the OpenFrame engine.

System Log

Records important internal OpenFrame events.

Operational Log

Records shell or studio commands executed by OpenFrame users.

Data Log

Records clean data, which is used as input for other analysis tools.

2.1. Service Logs

Records messages from the Tmax server that are produced by the OpenFrame engine.

  • Log directory

    ${TMAX_DIR}/log/ulog

  • Log file name

    $(SVR)$(DATE).out, $(SVR)$(DATE).err

Service log directory is the same as the directory specified in "${TMAXDIR}/log/ulog".

Service logs are recorded in the following format:

  • Log format

    [YYYY-MM-DDTHH:MM:SS.ffffff] [SERVICE-NAME(PID)] [M] [MSGCODE] MESSAGE-CONTENTS
    Item Description

    [YYYY-MM-DDTHH:MM:SS.ffffff]

    Message output time.

    [SERVICE-NAME]

    Name of the executed service.

    [PID]

    TMAX server PID where the service has been executed.

    [M]

    Message type.

    • M: Message

    • E: Error

    • W: Warning

    • D: Debug

    [MSGCODE]

    Eight-character message code.

The following is an example of service log.

[2019-11-28T17:55:40.096148] [OFRUISVRPROFILE(15569)  ] [M] [SVR0100M] service starts.
    fkey = 469762750, fname = FB_USER, type = string, value = ROOT
    fkey = 469762149, fname = FB_COMMAND, type = string, value = 1

2.2. System Logs

Records important internal OpenFrame events.

  • Log directory

    (LOG_DIR)/sys

  • Log file name

    ${MODULE_NAME}_YYYYMMDD.log

System logs are recorded in the following format:

  • Log format

    [YYYY-MM-DDTHH:MM:SS.ffffff] [EXECUTED-MODULE] [CODE] [MSGCODE] EVENT FREE-FORMAT-CONTENTS
    Item Description

    [YYYY-MM-DDTHH:MM:SS.ffffff]

    Message output time.

    [EXECUTED-MODULE]

    The module where the event has been executed. The job ID (job name) or server (PID) is recorded.

    [CODE]

    Message type with a single-digit. In general, the last character of [MSGCODE] is recorded.

    [MSGCODE]

    8-character message code.

The following is an example of system log.

[2019-12-03T14:58:28.745867] [ofrsmlog(15570)         ] [N] [ALC5005N] OPERATE=DISPOSE,HANDLE=2,DDNAME=_NULLDDN,CCOUNT=1,COND=NORMAL,TERM=KEEP,JOBID=,STEPSEQ=0,RCODE=0
[2019-12-03T14:58:28.813007] [ofrsmlog(15570)         ] [N] [ALC5006N] OPERATE=UNALLOCATE,HANDLE=2,DDNAME=,CCOUNT=0,COND=NORMAL,REFCNT=0,JOBID=,STEPSEQ=0,RCODE=0

2.3. Operational Logs

Records shell or studio commands executed by OpenFrame users.

  • Log directory

    (LOG_DIR)/cmd

  • Log file name

    ${MODULE_NAME}_YYYYMMDD.log

Operational logs are recorded in the following format:

  • Log format

    [YYYY-MM-DDTHH:MM:SS.ffffff] [EXECUTED-MODULE] [CODE] [MSGCODE] EVENT FREE-FORMAT-CONTENTS
    Item Description

    [YYYY-MM-DDTHH:MM:SS.ffffff]

    Message output time.

    [EXECUTED-MODULE]

    The module where the event has been executed. The job ID (job name) or server (PID) is recorded.

    [CODE]

    Message type with a single-digit. In general, the last character of [MSGCODE] is recorded.

    [MSGCODE]

    8-character message code.

The following is a sample operational log entry.

[2019-11-15T13:21:47.310244] [tjesmgr(29290)    ] [M] [BLG0060M] OPERATE=COMMAND,STATUS=S,CMD=boot,RCODE=0
[2019-11-15T13:21:51.528051] [tjesmgr(29366)    ] [M] [BLG0060M] OPERATE=COMMAND,STATUS=S,CMD=ps,RCODE=0
[2019-11-15T13:22:13.844243] [tjesmgr(29431)    ] [M] [BLG0060M] OPERATE=COMMAND,STATUS=S,CMD=r /home/arena/oframe_71_fix3/volume_100000/SYS1.JCLLIB/IEBSTR,RCODE=0

2.4. Data Logs

Records clean data, which is used as input for other analysis tools.

  • Log directory

    (LOG_DIR)/data

  • Log file name

    ${MODULE_NAME}_YYYYMMDD.log

3. Base System Logs

Base system generates the following log files:

  • Service logs

    Log Description

    ofrcmsvr$(DATE).out,

    ofrcmsvr$(DATE).err

    Service log for the ofrcmsvr server.

    ofrdmsvr$(DATE).out,

    ofrdmsvr$(DATE).err

    Service log for the ofrdmsvr server.

    ofrdsedt$(DATE).out,

    ofrdsedt$(DATE).err

    Service log for the ofrdsedt server.

    ofrlhsvr$(DATE).out,

    ofrlhsvr$(DATE).err

    Service log for the ofrlhsvr server.

    ofruisvr$(DATE).out,

    ofruisvr$(DATE).err

    Service log for the ofruisvr server.

    ofrsmlog$(DATE).out,

    ofrsmlog$(DATE).err

    Service log for the ofrsmlog server.

    ofrsasvr$(DATE).out,

    ofrsasvr$(DATE).err

    Service log for the ofrsasvr server.

  • System logs

    Log Description

    ams_YYYYMMDD.log

    System log for catalog management.

    dsalc_YYYYMMDD.log

    System log for data set allocation.

    saf_YYYYMMDD.log

    System log for system security.

  • Command log

    Log Description

    dstool_YYYYMMDD.log

    Command log for data set management.

  • Data log

    Log Description

    console_YYYYMMDD.log

    Data log for console messages.