Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

START-RESLOG-EVALUATION

&pagelevel(3)&pagelevel

Evaluate RESLOG file

Component:

RESLOG

Functional area:

Accounting system control

Domain:

ACCOUNTING

Privileges:

TSOS

SW-MONITOR-ADMINISTRATION

Function

The START-RESLOG-EVALUATION command starts the evaluation of RESLOG files. The caller can specify whether all the records or only the records relating to a specific period are to be evaluated. The result of the evaluation can be called in the form of a summary of the most important information or in detail with each ATTACH and DETACH operation. The output is written to SYSOUT but can alternatively be redirected to a file.

The RESLOG evaluation runs as a separate program that is loaded, started and terminated internally. Any previously loaded program is unloaded.

Format

START-RESLOG-EVALUATION                                                                                                                  

RESLOG-FILE = *CURRENT / *FROM-FILE(...) / <filename 1..54 without-gen-vers>


*FROM-FILE(...)



|

LIST-FILE-NAME = <filename 1..54 without-gen-vers>

,PERIOD = *INTERVAL(...)


*INTERVAL(...)



|

FROM = *FIRST-RECORD / <date>



|

,TO = *LAST-RECORD / <date>

,INFORMATION = *SUMMARY / *ALL

,OUTPUT = *SYSOUT / <filename 1..54 without-gen-vers>

Operands

RESLOG-FILE = *CURRENT / *FROM-FILE(...) / <filename 1..54 without-gen-vers>
Specifies one or more RESLOG files for evaluation.

RESLOG-FILE = *CURRENT
The current RESLOG file is evaluated.

RESLOG-FILE = <filename 1..54 without-gen-vers>
Path name of the RESLOG file that is to be evaluated. 

RESLOG-FILE = *FROM-FILE(...)
The path names of the RESLOG files that are to be evaluated are taken from a file name list. The file name list must be a SAM file with variable record length which possesses a fully qualified path name (maximum 54 characters) in capitals. Partially qualified spoecifications or specifications including wild cards are not permitted. The following conditions must be fulfilled for the specified RESLOG files:

  • They must all come from a single system (same server ID in the path name).

  • They must be specified in sequence from earliest to most recent.

The easiest and quickest way to generate a file name list is to use the
SHOW-FILE-ATTRIBUTES command. When this is done, all file selection possibilities are available (partial qualification, wildcards and selection criteria).


Example for the creation of a file name list

/SHOW-FILE-ATTRIBUTES FILE-NAME=:PVSX:$TSOS.SYS.RESLOG.<server-id>.,
     OUTPUT=<filelist>(FORM-NAME=FILE-NAME)

The fully qualified path names of all the already closed RESLOG files in the system specified by <server-id> are stored in the file <filelist> specified in the OUTPUT operand. The file <filelist> can be specified in the LIST-FILE-NAME operand.

LIST-FILE-NAME = <filename 1..54 without-gen-vers>
Path name of the file name list.

PERIOD = *INTERVAL(...)
Specifies the evaluation period.

FROM =
Specifies the start of the evaluation period.

FROM = *FIRST-RECORD
The evaluation period starts from the beginning of the specified RESLOG file or, in the case of a file name list, the beginning of the first log file in the list.

FROM = <date>
The evaluation period starts on the specified day.

TO =
Specifies the end of the evaluation period.

TO = *LAST-RECORD
The evaluation period terminates at the end of the specified RESLOG file or, in the case of a file name list, the end of the last log file in the list.

TO = <date>
The evaluation period ends on the specified day.

INFORMATION = *SUMMARY / *ALL
Specifies the level of detail of the evaluation.

INFORMATION = *SUMMARY
A summary of the most important information is output.

INFORMATION = *ALL
In addition to the summary information, outputs an overview listing each individual extra CPU ATTACH and DETACH operation. Also lists periods during which the RESLOG subsystem was not active.

OUTPUT = *SYSOUT / <filename 1..54 without-gen-vers>
Specifies where the information is output. The output can either be written to SYSOUT (default) or to the specified file.

Return codes

(SC2)

SC1

Maincode

Meaning                                                                            


0

CMD0001

No error

The codes returned in the event of an error (subcode 1 not equal to 0) cannot be guaranteed. However, automatic error processing is possible using the spin-off mechanism (corresponds to the default setting of the SET-PROCEDURE-OPTIONS command with ERROR-MECHANISM= *SPIN-OFF-COMPATIBLE).

Output information

Summary output of the current RESLOG file to SYSOUT

/START-RESLOG-EVALUATION [RESLOG-FILE=*CURRENT,INF=*SUMMARY,OUTPUT=*SYSOUT]

-----------------------------------------------------------------------------
                           RESLOG EVALUATION
-----------------------------------------------------------------------------
START DATE             : <date>              END DATE  : <date>
-----------------------------------------------------------------------------
BS2000 VERSION         : 21.0A00             SERVER-ID : 3002000188000000
RESLOG VERSION         : 21.0A00
-----------------------------------------------------------------------------
NUMBER EXTRA CPUS      :       1
NUMBER DAYS IN USE     :       1
-----------------------------------------------------------------------------
TIME WITHOUT DATA      :       1 (hours) (2%)
-----------------------------------------------------------------------------

Meaning of the output

START DATE

Start of the evaluation period

END DATE

End of the evaluation period

BS2000 VERSION

Operating system version at the start of the evaluation period

RESLOG VERSION

Version of the RESLOG file at the start of the evaluation period

SERVER-ID

Globally unique server ID of the system

NUMBER EXTRA CPUS

Number of extra CPUs at the start of the evaluation period

NUMBER DAYS IN USE

Number of days on which extra CPUs were used; each calendar day is counted on which each extra CPU was ATTACHED.

TIME WITHOUT DATA

Time in hours/days when RESLOG was inactive; the hours/days between the STOP and the following START records is counted. The time is also output as a percentage value relative to the overall evaluation period.

More detailed output of the current RESLOG file to the file PROT.EXTRA-CPU.002

/START-RESLOG-EVALUATION INFORMATION=*ALL, OUTPUT=PROT.EXTRA-CPU.002

.
.             Information as with INFORMATION=*SUMMARY
.
                DETAILED STATISTICS OF EXTRA-CPUS 
--------+-------------------------+-------------------------+----------------
 CPU NR !      ATTACH TIME        !      DETACH TIME        !     DURATION
--------+-------------------------+-------------------------+---------------
  02    !  <date>       <time>    !  <date>          <time> !      1 (days)
        !                         !                         !
  02    !  <date>       <time>    !  <date>          <time>*!      1 (days)
        !                         !                         !
NO DATA !  <date>       <time>    !  <date>          <time> !      1 (hours)
-----------------------------------------------------------------------------

Meaning of the output

CPU NR

CPU number of the extra CPU or – if RESLOG is not loaded – NO DATA

ATTACH TIME/
DETACH TIME

Date and time of the ATTACH or DETACH operation for an extra CPU (if a CPU number is specified under CPU NR) or
Date and time at the start of a period at which RESLOG was inactive (if the text NO DATA is specified under CPU NR)

DURATION

Period in hours or days relative to ATTACH/DETACH TIME

  • Output for extra CPU:
    The number of calendar days in the period between the ATTACH and DETACH operations for the extra CPU is output.

  • Output for NO DATA:
    The number of hours and days (rounded) in the period in which RESLOG was inactive is output

The times specified for ATTACH and DETACH TIME may be followed by an * (asterisk) which has the following meanings:

  • The precise time of the ATTACH operation is not known because the extra CPU was already ATTACHED when RESLOG was started.

  • The precise time of the DETACH operation is not known because the file was closed or changed or the subsystem was terminated abnormally while an extra CPU was ATTACHED.

  • The actual time of the ATTACH/DETACH operation is not output because the evaluation period starts after an ATTACH and/or ends before a DETACH.

  • The current file is evaluated and an extra CPU is ATTACHED. At DETACH-TIME, the date of the last alive or CPU record is written.