Temporary backup of REPs

All REP records are temporarily backed up in the SYS.NSI.SAVEREP file and are logged in REPLOG. If a current REPLOG file (see "REPLOG") is not available, the SAVEREP file is saved by SLED and may be converted with DAMP.

SAVEREP (system initialization for BS2000)

Each REP record that has actually modified the system is marked with a number in column 72; the other REP records are assigned letters. where:

1 or A: REP from disk

4 or D: REP from console

The loader code is written to the BS2000 LOADER record. The loader code is generated as a function of all REP records (not the SYSIPL REPs) and serves to identify the REP file. It is derived from the sum of the REP addresses and the parity digits of all existing REP records.

For each REP medium, when a save is made, two START and two END records are entered, containing the date, time, component and the full file name to give an unambiguous identification.
REPs for any other HSI than the current one are not logged in SAVEREP (and therefore also not in REPLOG) and are also not counted in the message referring to the processing of IPL REPs.

These records are entered in the following format:

START <object> yyyy-mm-tt,hh:mm:ss
START <file or input device>
:
<REP and comment records>
:
END <object> yyyy-mm-tt,hh:mm:ss
END <file or input device>

The following values can be used for <object>:

SYSIPL: REPs for SYSIPL
SYSSTART: REPs for SYSSTART
BS2000-CL1: REPs for class 1 exec
BS2000-CL2: REPs for class 2 exec (no date or time)
VM2000: REPs for VM2000 hypervisor (SUs /390)

<file> contains the complete file name of the REP file, made up of the catalog ID, user ID and file name sections.

The following values can be used for <input device>:

IPL path: for SYSIPL REPs

*CONSOLE: for REPs which are input from the console

An additional record is inserted after the last END record for BS2000 class 2 REPs (END BS2000 record); this contains information about the number of REPs which have been processed and the number replaced:

END BS2000: LOADER VERSION Z, mmmmm PROCESSED REPS, nnnnn REPLACED REPS

During the course of system initialization the SYS.NSI.SAVEREP file is copied to the logging file $SYSAUDIT.SYS.REPLOG.<date>.<session-no>.01. The correction data for BS2000 and all dynamically loaded subsystems is logged there.

REPLOG

The correction data for SYSIPL, SYSSTART, BS2000 and all dynamically loaded subsystems and all corrections made with ROSI in the active system are logged in logging file $SYSAUDIT.SYS.REPLOG.<date>.<sessno.>.01.

In addition to the corrections made in BS2000 and in the dynamically loaded system parts or subsystems, the old information replaced by the correction (REP before-image) is also logged in memory. This makes it possible to reliably and consistently remove corrections from the system while it is in session.

The system parameter SECSTART can be used by systems support to specify whether the actual correction status of the loaded BS2000 should be logged over several sessions. If SECSTART=N applies, any existing REPLOG files are deleted.
If SECSTART=Y applies, the REPLOG files are retained, and corrections can be traced over several sessions.

The SET-REPLOG-READ-MARK command can be used by systems support to briefly close the REPLOG file of the current session. In this way it is possible to copy and analyze all the data so far logged in a session.

Command	Meaning
SET-REPLOG-READ-MARK	Permits read access to the REPLOG file