Skip to content

Page 1

ND Software Library Diskette

Directory Name:
25036CL02-XX-01D

Page 1

Containing

SINTRAN III/VSX Patch file
Patch level 003100 for L-version

User Name: SYSTEM

No File Name Type T Public Friend Own Pages Bytes
0 NEW-SYSTEM PROG I R RWACD RWACD 21 40960
1 START-PATCH-FILE MODE I R RWACD RWACD 3 1667
2 PATCH-FILE MODE I R RWACD RWACD 4 4200
3 SYMBOLS FADM I R RWACD RWACD 2 16
4 PATCHES PATC I R RWACD RWACD 45 38106
5 REFERENCE FADM I R RWACD RWACD 3 3578
6 PF-LIBR-MARK FADM I R RWACD RWACD 3 2155
7 COS-7ZAJ05R BPUN I R RWACD RWACD 5 7470
8 LOAD-SERVERS MODE I R RWACD RWACD 2 1749
9 NKNME-C04 BPUN I R RWACD RWACD 65 129400
10 MXSERV-C04 BPUN I R RWACD RWACD 54 104824
11 PSA-PROGRAM-C04 BPUN I R RWACD RWACD 53 104822
12 ER-S3WD-CODE-C02 BPUN I R RWACD RWACD 31 61022
13 ER-S3WD-DATA-C02 BPUN I R RWACD RWACD 58 115252
14 ER-S3WD-DESC-C02 EDAT I R RWACD RWACD 38 75467
15 ER-S3WD-LOG-C02 PROG I R RWACD RWACD 2 28624

16 files using 416 pages. 600 pages reserved out of 610 pages.

ND-895230.1A EN

Scanned by Jonny Oddene for Sintran Data © 2024

Page 2

The page is blank, with only a footer stating:

Scanned by Jonny Oddene for Sintran Data © 2024

Page 3

Introduction

To avoid the problems involved with running extra mode files when customer-specific modification patches are needed, we are introducing a new way of handling such patches.

From now on these patches will be referred to as SM reports. (SM is short for Special Modification). The new system for handling SM reports will be used from patch file 3000 and onwards.

The SM reports will be stored on the patch file diskette, but they will not be installed when running the patch file, unless specified. Each SM report is identified by a special symbol called a library mark. The library mark consists of the letters PN and the report number.

If you want to install SM reports on a system the first time patch file 3500 is run, the file PF-MODIF-L:FADM must have already been created under user area SYSTEM. The library marks for the SM reports wanted must be written to the file before running the patch file.

Example

  1. You want to install SM reports SSR-119 and SSR-154 together with the patch file.

  2. @CREATE-FILE PF-MODIF-L:FADM 0

  3. The file PF-MODIF-L:FADM should look like this (REMEMBER 7 BITS FORMAT):

PN119
PN154
@
  1. Install SINTRAN from diskette and run the patch file.

If you don't want any SM reports, install SINTRAN and run the patch file as usual. The only difference from before is that a file called PF-MODIF-L:FADM is created under user area SYSTEM. This file will only contain the @ character and should be kept for future use.

When a SM report is wanted later on, the library mark for the corresponding SM report has to be written to the file PF-MODIF-L:FADM before SINTRAN is installed from diskette together with the patch file.

Another Example

  1. Edit the file PF-MODIF-L:FADM so it contains the library mark for the wanted SM-report.

  2. Install SINTRAN from diskette, and run the patch file.

Page 4

Software System Reports

Software System Reports Included

Report No. Program Subject Symptom
186 A VSX/500 The most significant byte in 5FUNC is set when addressing FUNC5 table. System stops in errfatal on level 14, with page fault on level 5.
160 A VSX Error in MON IOMTY : Function 12 to set 8 bits unmodified input and output. Not possible to set 8 bits unmodified when connected on TAC.
159 A ALL MON PERFORMANCE - prim. 66. Error in measurements on 100 histograms split on RT-Program and segments. Any activity on level 1 was measured, not only the selected RT-program and segment.
158 A VSX Error in Monitor Call MSYSU (MON 331) for SINTRAN generated without disk mirroring (Library mark BCIM1). Servers (ERS3W0, MTSERV ...) and all RT-programs using this monitor will be looping with P-register = 000000.
151 A ND-100 STOP-SYSTEM command for system generated only for ND-100 (without library mark BN500). System hangs on level 2.
147 A ALL No restrictions towards Nucleus when logging into Sintran via User Environment (UE). A process logged into Sintran via UE did always get access towards Nucleus.
146 A ALL Error when using Performance monitor on old ND-100 CPU. (Part nos. 322602, 322663) System stops on level 14 with page fault on level 11.

Page 5

SINTRAN III Version L/VSX

Patch File 003100

Software System Reports Included

Report No: 145 A

  • Program: VSX
  • Subject: Error on system generated for SIBAS process 20, 21, 22, or 23
  • Symptom: Impossible to start SIBAS process no: 20, 21, 22, or 23

Report No: 144 A

  • Program: All
  • Subject: File system error messages cannot be logged on batch output file or mode output mass storage file.
  • Symptom: Several, in worst case system crash.

Report No: 142 A

  • Program: All
  • Subject: Error in SCSI magtape functions 50 and 51.
  • Symptom: System may stop in errfatal. Different records may be read to the same memory address.

Report No: 141 A

  • Program: VSX
  • Subject: Error on parallel Line Printer
  • Symptom: Several symptoms: Page fault on level 2. Rubbish on output etc.

Report No: 140 A

  • Program: VSX/500
  • Subject: Power fail ND-500(0), nowait and multi-CPU timing.
  • Symptom:
    1. Sometimes multi-CPU systems didn’t recover properly after a power fail.
    2. One process only - in nowait - will not initiate ND-500(0) when restarted from this state.

Report No: 139 A

  • Program: All
  • Subject: Avoid deadlock between a program reserving the swap semaphore and a program doing MON 61.
  • Symptom: Deadlock, for instance between the DMA server and the Telnet server.

Report No: 138 A

  • Program: All
  • Subject: Avoid non-valid Sintran error messages when doing compare on SCSI disks.
  • Symptom: Sintran runtime error messages may be given when a recoverable error is encountered during a compare function done by backup system or backup manager.

Scanned by Jonny Oddene for Sintran Data © 2024

Page 6

Software System Reports Included

Report no: 137 A

  • Program: all
  • Subject: Error in STC magtape driver (SMAGT) when write-EOF is done and EOT detected. EOT status is not returned to caller.
  • Symptom: One symptom may be that the backup system will delete the second last file on a tape before switching to a new tape.

Report no: 135 A

  • Program: VSX
  • Subject: Resetting XOFF on terminal input clearing the terminal input channel when logging out.
  • Symptom: Terminals hang waiting for XON character.

Report no: 134 A

  • Program: VSX
  • Subject: Power fail on FUJITSU disk 140Mbytes
  • Symptom: System hangs waiting for disk to get ready.

Report no: 133 A

  • Program: VSX/500
  • Subject: RESIDENT-PLACE on ND-500(0) didn't work.
  • Symptom: Permit violation when executing command.

Report no: 131 A

  • Program: VSX
  • Subject: COPY-FILE command will leave the destination file or/and the source file opened.
  • Symptom: Error message on the terminal e.g. NOT MASS STORAGE FILE etc., but the files are not closed.

Report no: 130 A

  • Program: ALL
  • Subject: Login with TAD type 377B.
  • Symptom: It is possible to bypass UE login when using TAD type 377B when connecting to remote machine.

Report no: 129 A

  • Program: VSX/500
  • Subject: Error in MON PERFORMANCE - prim. 32 option 113.114.
  • Symptom: Physical log buffer is erroneously addressed, which may lead to overwriting in the same memory bank as these buffers reside. Different symptoms.

[Scanned by Jonny Oddene for Sintran Data © 2024]

Page 7

Software System Reports Included

Report no: 128 A

  • Program: VSX
  • Subject: Wrong definition of DISK-SCSI-<8-14> datafields in the table for logical device number.
  • Symptom: "NO SUCH DEVICE NAME" when trying to access the devices: DISK-SCSI-8 to DISK-SCSI-14.

Report no: 127 A

  • Program: ALL
  • Subject: MON 256 (DEABF, FullFileName)
  • Symptom: The monitor call does not accept '*' as part of the file name to be de-abbreviated.

Report no: 126 A

  • Program: ALL
  • Subject: Error in monitor calls 257 (Find open file number) and 2d (Find object index).
  • Symptom: System crash if the specified file name contains an illegal character.

Report no: 125 A

  • Program: ALL
  • Subject: Set 'lastport' in Nucleus message in Nucleus function mkSer.
  • Symptom: 'Lastport' was set in Nucleus message when receiving port was closed.

Report no: 124 A

  • Program: ALL
  • Subject: Powerfail do not work on Micropolis SCSI disk.
  • Symptom: Disk transfer error or hang after powerfail.

Report no: 123 B

  • Program: MIAD
  • Subject: Mail to MIAD terminals when they are in XOFF modus.
  • Symptom: Process sending the mail is hanging until XON is received.

Report no: 117 A

  • Program: ALL
  • Subject: Error in displaying warnings when timeout on MIADs.
  • Symptom: No warning appears before logout.

Page 8

SINTRAN III Version L/VSX

Patch File 003100

Software System Reports Included (General Modification)

Report No Program Subject
157 A VSX/500 Extended functionality in MON 440 function 3 for SIBAS malloc scattered.
149 A ALL MON CLOSE from ND-500(Q) with Sintran-III open file number.
148 A ALL Patch to force BD10 to use half block size.
143 A SINTRAN First INITIAL-COMMAND had to be ENTER-DIRECTORY.
120 A ALL Error messages on error device from SCSI streamer driver. The same functionality as in the SCSI magtape driver.

Scanned by Jonny Oddene for Sintran Data © 2024

Page 9

SINTRAN III version L/VSX

Patch File 003100

Software System Reports Included (Special Modification)

Report no 171 A
Program all
Subject Patch to remove the form feed after the spooling trailer.
Report no 170 A
Program all
Subject Patch to remove the form feed at the end of the spooling print if the spooling trailer is present.
Report no 169 A
Program all
Subject Patch to remove the form at the start of the spooling print if the spooling header is present.
Report no 168 A
Program all
Subject Patch to remove the form feed after the spooling header.
Report no 156 A
Program all
Subject Patch to treat empty spooling form as normal string.
Report no 154 A
Program ALL
Subject Spooling header with rotating alphabetic characters (instead of *) gives more even wear on character set.
Report no 82 B
Program All
Subject Cold-start after online Sintran installation.

Scanned by Jonny Oddene for Sintran Data © 2024

Page 10

SINTRAN III Version L/VSX

Patch File 003100

Listed below are changes since Patch File 002200

Report no: 101 B

  • Program: IOMTY
  • Subject:
    • New function in monitorcall IOMTY (336), Function 26b
    • (Modification patch)
  • Symptom: Not possible to get MTA0 connection id from 500(0)

Report no: 79 B

  • Program: ALL
  • Subject: @CREATE-DIRECTORY on floppy disk.
  • Symptom:
    1. Not all bad pages are reserved and reported as bad.
    2. The command is also made faster if there are no bad spots on the diskette. (From approx. 2 mins. to 40 secs.)

Report no: 32 B

  • Program: XON/XOFF
  • Subject: Error in routine CTRIN when DFLAG=101000.
  • Symptom: IOX errors sometimes occurs, or hanging terminals.

Report no: 11 C

  • Program: All
  • Subject: Error in Nucleus function NkGetInfo for RT-programs.
  • Symptom: Page fault occurred in IOF.

Page 11

SINTRAN III Version L/VSX

Patch File 003100

Cross Reference List

  • X-origin: Patch File
  • Y-origin: Software System Report (SSR)
  • >: SSR-revision
  • *: Preliminary SSP
1 2 3
3 2 1
0 0 0
0 0 0
2 A A A
3 A A A
4 A A A
5 A A A
6 A A A
7 A A A
8 A A A
9 A A A
10 A A A
11 A >B >C
12 A A A
13 A A A
14 A A A
15 A A A
16 A A A
17 A A A
18 A A A
19 A A A
20 A A A
22 A A A
23 A A A
24 A A A
25 A A A
26 A A A
27 A A A
28 A A A
29 A A A
30 A A A
31 A A A

Page 12

SINTRAN III Version L/VSX

Patch File 003100

1 2 3
0 0 0 0

| 32 | A | A | B | | 33 | A | B | B | | 34 | A | A | A | | 35 | A | A | A | | 36 | A | A | A | | 37 | A | A | A | | 39 | A | A | A | | 40 | A | A | A | | 41 | A | A | A | | 42 | B | B | B | | 43 | A | A | A | | 44 | A | A | A | | 45 | A | B | B | | 46 | A | A | A | | 47 | A | A | A | | 48 | A | A | A | | 49 | A | A | A | | 50 | A | A | A | | 51 | A | A | A | | 52 | A | A | A | | 53 | A | A | A | | 54 | A | A | A | | 55 | A | A | A | | 56 | A | C | C | | 57 | B | B | B | | 58 | A | A | A | | 59 | A | A | A | | 60 | B | B | B | | 61 | A | A | A | | 62 | A | A | A | | 63 | A | A | A | | 64 | A | A | A | | 65 | A | A | A | | 66 | A | B | B | | 67 | A | A | A | | 68 | A | A | A |

Scanned by Jonny Oddene for Sintran Data © 2024

Page 13

SINTRAN III Version L/VSX

Patch File 003100

  : 1 : 2 : 3 :
  : 3 : 2 : 1 :
  : 0 : 0 : 0 :
  : 0 : 0 : 0 :
Line Column 1 Column 2 Column 3
69 A A A
70 B B B
71 D D
72 A A A
73 A A A
74 A A
75 A A
76 A A
78 A A
79 A >B
80 A A
81 A A
82 A >B
83 A A
84 C C C
85 A A
87 A A
88 A A
89 A A
90 A A
91 A A
92 A A
94 A A
95 A A
96 A A
97 A A
98 A A
100 C C C
101 A >B
104 A A
107 A A
108 A A
109 A A
110 A A
111 B B
112 A A

Page 14

SINTRAN III Version L/VSX

Patch File 003100

  : 1 : 2 : 3 :
  : 3 : 2 : 1 :
  : 0 : 0 : 0 :
  : 0 : 0 : 0 :

-------------------
| 113 :   : A : A |
| 114 :   : A : A |
| 117 :   :   :   |
| 119 :   : A : A |
| 120 :   :   : A |
| 123 :   :   : B |
| 124 :   :   : A |
| 125 :   :   : A |
| 126 :   :   : A |
| 127 :   :   : A |
| 128 :   :   : A |
| 129 :   :   : A |
| 130 :   :   : A |
| 131 :   :   : A |
| 133 :   :   : A |
| 134 :   :   : A |
| 135 :   :   : A |
| 137 :   :   : A |
| 138 :   :   : A |
| 139 :   :   : A |
| 140 :   :   : A |
| 141 :   :   : A |
| 142 :   :   : A |
| 143 :   :   : A |
| 144 :   :   : A |
| 145 :   :   : A |
| 146 :   :   : A |
| 147 :   :   : A |
| 148 :   :   : A |
| 149 :   :   : A |
| 151 :   :   : A |
| 154 :   :   : A |
| 156 :   :   : A |
| 157 :   :   : A |
| 158 :   :   : A |
| 159 :   :   : A |
-------------------

Scanned by Jonny Oddene for Sintran Data © 2024

Page 15

SINTRAN III Version L/VSX

Patch File 003100

1 2 3
3 2 1
0 0 0
0 0 0
A
160 A
168 A
169 A
170 A
171 A
186 A

Scanned by Jonny Oddene for Sintran Data © 2024

Page 16

It seems the page is blank or lacks visible content.

Page 17

ERS SINTRAN III Watchdog Description. Version C.

This report describes two programs:

The first is the ERS/SINTRAN III Watchdog (henceforth called ERS3WD), which is an RT-program to handle SINTRAN III error messages.

The second program is the Error Log Lister, which formats the log file produced by ERS3WD.

The installation procedure is found in the last paragraph.

Central Concepts

SSI
Subsystem Identification, a number uniquely identifying a product.

EC
Event Code (or Error Code), a number identifying an event in a product.

SEC
Standard Event Code (16 bits), the SSI and the EC combined. The SEC identifies both the (failing) product and the event which has occurred.

Example:

SSI = 1061B 'FTX - Disk Mirroring'
EC  =  15B 'Page outside limits'
SEC = 106115B

ERS3WD

The RT-program ERS3WD is a process which handles error reports sent via or by SINTRAN III. ERS3WD receives these reports from SINTRAN on the internal device with logical device number 2765. The SEC parameter in every report specifies which system module has issued the report and which error has occurred.

A received report is in numeric format. ERS3WD converts the report to text format and writes it to the error device.

To do this conversion ERS3WD needs some formatting information, the so-called "report descriptors". This information is already contained in ERS3WD's data segment at installation. The report descriptors are also supplied as the file ER-S3WD-DESC-Cxx:EDAT to make it possible to update the descriptors more frequently than ERS3WD is revised. If this file exists on the user areas ND-OPERATIONS or SYSTEM, ERS3WD will substitute this file's descriptors for its own descriptors at startup.

ERS3WD also writes the numerically formatted report to its own log file. This is the file (SYSTEM)ER-S3WD-LOG:DATA, which is created by ERS3WD at startup if it does not already exist. The log file is created as a contiguous 11-page file and ERS3WD treats it as a ring file. This means that ERS3WD will start writing at the beginning of the file again after reaching the end.

Error Log Lister

The Error Log Lister is a background program that takes the log file produced by ERS3WD and formats it into text messages.

Contrary to ERS3WD, the Error Log Lister program depends on finding and reading the descriptor file ER-S3WD-DESC-Cxx:EDAT, either on the user area ND-OPERATIONS or the user area SYSTEM.

Page 18

ERS3WD Log File Handling

ERS3WD writes to the file {SYSTEM}ER-S3WD-LOG:DATA, and this is the default input file to the Error Log Lister. Output can be directed to a file or to the terminal, default output is the file ER-S3WD-LOG:OUT.

It is possible to clear the log file when reading it, but this is not necessary as the log file is circular as explained above.

The program is started by typing: ER-S3WD-LOG

Data Flow

flowchart TB
    A(Event report from system module)
    A --> B(SINTRAN III)
    B --> C1(Internal device 276B)
    C1 --> D1(( ))
    D1 --> D(ERS3WD)
    D --> |3)| E(SINTRAN logical Error Device)
    D --> |4)| F(Terminal or file)
    F --> |4]| G(Error Log Lister)
    D --> | | H(Circular log file)
    D --> | | I(S3WD descriptor data)
    I --> |2)| J(S3WD numeric descriptor file)

Notes

  1. ERS3WD does not depend on finding the descriptor file.
  2. Error Log Lister depends on finding the descriptor file.
  3. Numeric format event reports.

  4. Text format event reports.

  5. If in a period reports are produced faster than they are read, it may happen that the internal device gets filled up by unread reports. Before SINTRAN writes a new report, it checks whether the device is almost full. Should this be the case, then a report with SEC: 1666B is written instead. The text format version of this report includes the event text:

    Internal device for error messages is full.

SINTRAN will ignore event reports arriving after the 1666B report until sufficient free space is again available in the device. The ignored reports are lost.

Page 19

Text Format

This is the layout of a report written to the error device:

<severity> * SSI.EC * YYYY-MM-DD HH:MM:SS * <RTprog>.<P-reg> * <sysname>.<sysno>

<product name>
<event text>
<parameter description><parameter>
<parameter description><parameter>

Components

Component Description
<severity> This tells the severity of the event that has been reported. (FATAL, ERROR, WARNING, INFORMATION)
SSI This is the SSI of the reported event. It is written as an octal number.
EC This is the Event Code of the reported event. It is also written as an octal number.
YYYY-MM-DD The date when the event was read by ERS3WD.
HH:MM:SS The time when the event was read by ERS3WD.
<RTprog> The RT-program name (if possible, or RT-program description address).
<P-reg> The P-register contents of the RT-program.
<sysname> The system name as defined in XMSG, if it is accessible.
<sysno> The system number as defined in XMSG, if it is accessible.
<product name> The product name.
<event text> A text which describes the nature of the event.
<parameter description> An explanation of what the following parameter value is.
<parameter> A parameter value.

Suppression

When a process reporting to ERS3WT "goes wild" and sends a stream of identical error messages, it is desirable that "excess" messages will be suppressed.

If the same event report appears more than 20 times in succession, the following identical event reports will be suppressed until a different event arrives or the time between the last and previous event exceeds 10 seconds.

When the suppression starts, a message about this will be given. When the logging of event reports is resumed, ERS3WD reports the number of reports that have been suppressed, and then the new report.

Page 20

ERS3WD Messages

ERS3WD indicates a few situations by writing messages both to the error device and the log file. The messages are:

1170B.01B ERS/Watchdog has started

1170B.02B ERS/Watchdog has stopped

1170B.03B Cannot reserve internal device

The internal device 276B could not be reserved.

1170B.04B Descriptor file was not found on SYSTEM or ND-OPERATIONS

The descriptor file could not be found or accessed.
The file was searched for on both the user areas ND-OPERATIONS and SYSTEM.
ERS3WD continues and will use its initial descriptors.

1170B.05B Cannot read descriptor file. Corrupt file

The descriptor file named ER-S3WD-DESC-C:EDAT is empty or contains corrupted data.

1170B.06B Log file could not be opened/created

The log file named (SYSTEM)ER-S3WD-LOG:DATA could not be created or opened. Is it possible to reserve at least 11 contiguous pages for user SYSTEM?

1170B.07B Further copies of this event will be suppressed

If the same event report appears more than 20 times in succession, the following identical event reports will be suppressed until a different event arrives or the time between the last and previous event exceeds 10 seconds.

1170B.10B The previous message has been suppressed

This message is written at the end of a suppression period.

1170B.11B Descriptor file too big

The descriptor file named ER-S3WD-DESC-C:EDAT is larger than ERS3WD's data segment (about 114000 bytes).

1170B.12B Descriptor file too small

The descriptor file named ER-S3WD-DESC-C:EDAT is found to be too small. It must at least be 2 pages.

1170B.13B Error when reading descriptor file

A file system error occurred when reading the descriptor file ER-S3WD-DESC-C:EDAT.

Scanned by Jonny Oddene for Sintran Data © 2024

Page 21

1170B.14B Protocol Error on Internal Device

The byte string that was received on the internal device was not recognized by ERS3WD as a legal protocol. This error may cause one or more of the following reports to be slightly corrupted or totally wrong, or even make ERS3WD stop reporting. It is recommended that you abort ERS3WD, do @RTCLOSE on the log file, and then restart the ERS3WD RT-program if this error occurs. (See the next message.)

1170B.15B The Protocol Error is Corrected

This message appears if ERS3WD managed to find a correct protocol header on the internal device after the previously described situation. A restart is no longer necessary.

Reporters that are Recognised by ERS3WD

This list may be expanded by the installation of a newer revision of the descriptor file than ER-53WD-DESC-C02:EDAT.

SEC System Module
000000B - 000377B SINTRAN III File System
001000B - 001077B ND-500/5000 System Monitor
001500B - 001677B SINTRAN III Runtime System
002000B - 002177B ND-500/5000 Monitor Internal
002200B - 002277B ACCP/Microprogram
002300B - 002377B ND-500/5000 Monitor Internal
003200B - 003277B SINTRAN III File System
006000B - 006077B Domino Operating System
006200B - 006277B Domino Services
007600B - 007677B ND-500/5000 Traps
044500B - 044577B PO-LIB Service Point System
044600B - 044677B Ethernet Media Access
047200B - 047277B AIP - ARPA Internet Protocol
047300B - 047377B TCP/IP - Transmission Control Protocol / Internet Protocol
047400B - 047477B SLIB - Socket Library
047600B - 047677B Telnet Server
101000B - 101077B Nucleus
101100B - 101177B Nucleus Operations
101200B - 101277B MTAD Server
101400B - 101477B Octobus driver
101500B - 101577B MF-bus Controller
104000B - 104277B BDJ0 - Basic Disk I/O
104500B - 104577B SCSI domino driver
104600B - 104677B SCSI domino device level
104700B - 104777B SCSI domino tape access
105000B - 105077B PROMAN - Processor Manager
105300B - 105377B SCSI domino device level
106000B - 106277B FTX Disk Mirroring
107000B - 107077B ERS Watchdog
107100B - 107177B ERS Library
107200B - 107277B ERS Router
107300B - 107377B ERS Receiver
107400B - 107477B ERS Formatter
107500B - 107577B ERS Configuration Server
142200B - 142277B SIBAS Access Server

Page 22

Installation

ERS SINTRAN III Watchdog version C is delivered as part of the patch file 3000 for SINTRAN III version L.

ERS3WD version C is installed when you run the patch file, but the descriptor file ER-S3WD-DESC-C02:ED#T is not (and need not be) copied. ERS3WD is started when SINTRAN starts.

To be able to use the Error Log Lister, you must copy the file ER-S3WD-LOC-C02:PROC to the user area SYSTEM and the file ER-S3WD-DESC-C02:ED#T to the user area SYSTEM or ND-OPERATIONS. Create an output file for the Error Log Lister, e.g., ER-S3WD-LOG:OUT.

The operation of the log file (ring file) (SYSTEM)ER-S3WD-LOG:DATA is fully automatic. ERS3WD will create it as a 11-page contiguous file if it does not already exist. With this size the log file typically contains between 400 and 900 event reports when filled up. You may recreate this file with a new size to suit your demands, but it must be at least 2 pages in size, and it must be a contiguous file.

NOTE! ER-S3WD-LOG:DATA must not be closed for RT-program use (@RTCLOSE-FILE), deleted or otherwise tampered with while ERS3WD is active. - You must first do @ABORT ERS3WD, then @RTCLOSE on the log file. - To restart ERS3WD do @RT ERS3WD or @RESTART-SYSTEM.

The Error Log Lister may run while ERS3WD is active.