Page 1¶

SINTRAN III¶

System Supervisor¶

ND-30.003.007 EN

Norsk Data Logo

Norsk Data

Page 2¶

SINTRAN III¶

System Supervisor

ND–30.003.007 EN

Page 3¶

PREFACE¶

The product¶

SINTRAN III is a general purpose operating system for ND-100 and ND-500 computers. This manual describes the Operator and System Supervisor functions for the following products.

Product	Version	Code
SINTRAN III VSE	version K	ND-210174
SINTRAN III VSX	version K	ND-210575
SINTRAN III VSX-500	version K	ND-210576
COSMOS Basic Module	version D	ND-210374

VSE and VSX are used on ND-100 computers, while VSX-500 is used on the ND-500 computers. The VSE-500 has now been now phased out (the last version was I).

VSE and VSX are abbreviations for Virtual Storage EXtended. VSE is for ND-100 standard CPUs, while VSX is for ND-100/CX CPUs (Commercially eXtended instruction set). In addition to the ND-100 part of SINTRAN, the VSX-500 contains the ND-500 MONITOR.

The VSE uses 4 page tables, while the VSX now uses 16 page tables. VSX requires Memory Management System II (MMS II), or the new fast ND-110/CX CPU.

The reader¶

This manual is intended for System Supervisors and Operators of computers using any of the versions of SINTRAN listed above.

Prerequisite knowledge¶

Many of the tasks described can be carried out without any basic knowledge of software or ND equipment, though knowledge of SINTRAN as an ordinary user is an advantage. New operators and supervisors of ND computers are advised to take the special courses offered by ND.

Sections marked "ADVANCED" are written for experienced operators or supervisors. Some of these sections may prove difficult for people who do not have much knowledge of data processing.

Norsk Data ND-30.003.7 EN

Page 4¶

The manual¶

Chapters 1 to 4 contain material of importance to all readers in the above groups.

Operators of ND-500 installations need knowledge of some operations that are exclusive to the ND-500. These operations are described in separate sections.

Documentation for all configurations:¶

Document	Number
SINTRAN III Introduction	ND-60.125
Timesharing Guide	ND-30.132
Release Information K-version	ND-60.230
Commands Reference Manual	ND-60.128
How to order it	ND-30.053
Utilities Manual	ND-60.151
Backup User Guide	ND-60.250
Tuning Guide	ND-30.049
Software Security Handbook	ND-30.048
Quick Reference Card	ND-60.174 (RC)
User Environment Reference Manual	ND-60.194
ND-100 Operator's Communication Survey	ND-99.016 (RC)

Documentation on specific types of computer:¶

Document	Number
ND-100 Compact Operator Guide	ND-30.031
ND-100 Satellite Operator Guide	ND-30.041
How To Use Operator Panel ND-323163	ND-99.030 (RC)

Data communication:¶

Document	Number
COSMOS Options Operator's Guide	ND-30.034
SNA Supervisor	ND-30.054
SNA RJE Operator Manual	ND-30.058

(RC means reference card)

Databases and applications using them:¶

Document	Number
SIBAS Operator's manual	ND-30.009
UNIQUE-II Installation Instructions	ND-60.217
ND TPS System Supervisor's manual	ND-30.006
ACCESS DBA Manual	ND-30.022
TRUE Operator Guide	ND-30.042
NOTIS-DS Supervisor Guide	ND-30.059

Norsk Data ND-30.003.7 EN

Page 5¶

Documentation	Code
SINTRAN III Monitor Call Guide	ND-60.228
Real Time Guide	ND-60.133
System Documentation	ND-60.062
NORD File System Documentation	ND-60.122
FTX Operator Manual	ND-30.051
NDIX Operator Guide	ND-30.055
TELEFIX Reference Manual	ND-30.040
ND-100 Hardware Maintenance Manual	ND-30.008
ND-500 Hardware Maintenance	ND-30.014

Notation used in this manual¶

SINTRAN prints the character @ as prompt when it is ready to accept a command. Commands and parameters specified can be abbreviated as long as they do not become ambiguous. SINTRAN and many subsystems have a HELP command to list the commands available.

EXAMPLE: @W-I-O is legal for "WHO-IS-ON".

The character "*" can be used to denote arbitrary characters in commands and parameters.

EXAMPLE: @***** is equal to @DATCL.

EXAMPLE: @LIST-FILES .*SEG will list files with matching file types such as :PSEG and :DSEG.

Parameters omitted in an input string are asked for. Each input line must be terminated by CR (Carriage Return). This character is invisible.

Spaces and commas are used to separate parameters. Examples in this manual make use of both conventions.

EXAMPLE: @HELP CREATE TERMINAL is equal to @HELP,CREATE,TERMINAL

Lowercase letters are considered equal to the corresponding uppercase letters in an input line. SINTRAN uses mainly uppercase letters in output to the terminal.

EXAMPLE: @terminal-status is equal to @TERMINAL-STATUS.

Norsk Data ND-30.003.7 EN

Page 6¶

Number Systems¶

Numbers can be specified in two number systems. The radix (number base) specifiers are:

Specifier	System	Example
B	octal	Example: 313B
D	decimal	Example: 203D

The radix specifier is added after the last digit in the number. SINTRAN usually uses decimal, while the SINTRAN Service Program mainly uses octal numbers. The ND-500 Monitor accepts also hexadecimal numbers.

EXAMPLE: 203D is the same as 313B.

In the text in this manual, octal numbers are indicated by the radix specifier 8 or B.

K stands for "binary K" (1024 decimal). In the same way, M stands for "binary M" (1024*1024=1048576 decimal).

EXAMPLE: 64K is the same as 64₁₀ * 1024₁₀ = 65536₁₀.

Word Length¶

A word has a length of 16 bits unless otherwise stated. This is in general valid for the ND-100 computer and SINTRAN, while the ND-500 CPU has a word-length of 32 bits.

Line-Editing Features¶

Line-editing features are activated by control characters. See SINTRAN Commands Reference Manual.

Command Syntax Conventions¶

The following conventions are used throughout this manual in explanations of COMMAND syntax. When typing commands on the terminal, THESE CHARACTERS MUST NOT BE TYPED:

Character	Description
< >	parameter name within angular brackets
( )	the enclosed parameter has a default value
[ ]	the enclosed parameter is optional
/	use one of the alternatives values/expressions either to left or right of the slant.
?	the parameter is a question to be answered by "Y" or "N"

Norsk Data ND-30.003.7 EN

Page 7¶

Examples of Different Parameter Types¶

Parameter	Description
`<file name>`	has no default value,
`<output file>`	has a default value.
`[unit]`	is an optional parameter.
`<input/output>`	is a parameter with two alternatives.
`(<image?>)`	is a question with default value "N"

In examples of interactive communication, two types of commands are shown:

commands with prompted parameters
commands fully specified on a line.

For the sake of clarity, user input is underlined except in the case of "CR", which is omitted. In examples illustrating mode jobs, nothing is underlined.

Control characters are shown as follows: CTRL-A .

Control characters are typed by pressing the CONTROL-key "CTRL" and holding it down while pressing the other key.

The three most-used functions on the computer's operator panel are illustrated as follows:


STOP	MACL	LOAD
	(MAster CLear)

The activation of these functions depends on the operator-panel type.

Changes from Previous Version¶

The manual has been completely rewritten and reorganized to reflect SINTRAN III version K.

For an overview of the differences between versions J and K, see SINTRAN Release Information K-version, ND-60.230.2

The Operator functions of the COSMOS Basic Module are also now documented in this manual. This replaces the parts of the COSMOS Operator Manual (ND-30.031) that described these functions.

Norsk Data ND-30.003.7 EN

Page 8¶

Contents¶

Appendices¶

Appendix	Title	Page
A	SYSTEM NAME	A-1

Index	Topic	Page

List of Code Words¶

Code	Meaning
CODE1	Description1
CODE2	Description2

Norsk Data ND-30.003.7 EN

Page 9¶

TABLE OF CONTENTS¶

Section	Page
1 SYSTEM SUPERVISION OVERVIEW	1
1.1 Job description for the System Operator	1
1.2 Job description for the System Supervisor	1
1.3 Categories of user area	3
1.4 Software versions required for running SINTRAN III K	5

| 2 HARDWARE OPERATIONS | 7 | | 2.1 Using the operator panel | 7 | | 2.1.1 ND-100 and ND-500 operator panels until 1984 | 9 | | 2.1.2 All ND computers from 1985 | 13 | | 2.1.3 OPCOM reference section (ADVANCED) | 16 | | 2.2 Using disks | 21 | | 2.2.1 The SMD disks | 22 | | 2.2.2 The MMD disk | 25 | | 2.2.3 The FSD and RSD disks | 26 | | 2.3 Using the streamer magnetic tape | 29 | | 2.3.1 The 8 inch streamer | 29 | | 2.3.2 The 5 1/4 inch streamer | 30 | | 2.3.3 Write-protecting the cartridge | 31 | | 2.4 Switching on the installation | 32 | | 2.4.1 The ND-100 and ND-500 computers in large cabinet | 33 | | 2.4.2 The Compact computers | 35 | | 2.4.3 The Satellite computers | 36 | | 2.4.4 The OMNI hardcopy console terminal | 37 | | 2.4.5 The Tandberg TDV 2200/9 terminal | 38 | | 2.4.6 The FACIT 4440 - TWIST terminal | 39 | | 2.4.7 The EPSON RX/80 printer | 40 |

| 3 STOPPING, STARTING AND LOADING SINTRAN III | 43 | | 3.1 Controlled stop | 46 | | 3.1.1 More about stopping different processes | 48 | | 3.1.2 Stopping ND-500 CPU without stopping the ND-100 | 58 | | 3.2 Warn start | 61 | | 3.2.1 SINTRAN memory, image and save-area | 64 | | 3.2.2 Initial commands | 66 | | 3.2.3 More about the LOAD-MODE file | 69 | | 3.2.4 More about starting different processes | 71 | | 3.2.5 Starting the ND-500 CPU | 75 | | 3.2.6 Starting the ND-500 Multi-CPU (ND-580/CX) | 80 | | 3.3 Cold start | 86 | | 3.3.1 Cold start with SINTRAN running | 86 | | 3.3.2 More about the HENT-MODE file | 91 | | 3.3.3 Maintaining the segment files (ADVANCED) | 92 |

Norsk Data ND-30.003.7 EN

Page 10¶

Section¶

Section	Page
3.3.4	Initializing background programs
3.3.5	Initializing the MAIL system
3.3.6	Reentrant subsystems
3.3.7	The ND500-HENT file
3.3.8	Ordinary domains and standard domains
3.3.9	ND-500 Swap files (ADVANCED)
3.4	Loading SINTRAN from floppy diskettes
3.5	Configuration program
3.5.1	The utility commands
3.5.2	The selection commands
3.5.3	The DISPLAY command
3.6	Initial loading of SINTRAN (ADVANCED)
3.7	Example of initial loading (ADVANCED)
3.8	Space requirements for K version

4 FILE SYSTEM SUPERVISION¶

Section	Page
4.1	Files
4.1.1	Creating indexed files
4.1.2	Shrinking, renaming and deleting files
4.1.3	Retrieving information about files
4.2	Directories
4.2.1	Creating a directory
4.2.2	Formatting a disk or floppy diskette
4.2.3	Entering and releasing directories
4.2.4	Retrieving information about directories
4.3	Administrating user areas and disk space
4.3.1	Creating and deleting user areas
4.3.2	Defining file access and the number of files that can be created
4.3.3	Scratch files
4.3.4	Passwords
4.4	Efficient directory and file organization (ADVANCED)
4.4.1	Two examples of directory organization

5 COSMOS BASIC MODULE OPERATIONS¶

Section	Page
5.1	Survey
5.1.1	Prerequisites to use the COSMOS BM
5.1.2	Defining the network routing
5.2	The Connect-To Service program and TADs
5.2.1	The SINTRAN TAD commands
5.2.2	The Connect-To Service program
5.3	The script facility of Connect-To
5.3.1	SCRIPT syntax
5.3.2	How to start and end a SCRIPT
5.3.3	The SCRIPT body
5.3.4	Error messages
5.3.5	Some additional SCRIPT examples
5.4	The File Server Administrator
5.4.1	Overview of Remote File Access
5.4.2	The FS Administrator program

Norsk Data ND-30.003.7 EN

Page 11¶

Section¶

Section	Page
5.5	Advanced part of File-Transfer
5.5.1	Checking the network connections
5.5.2	Defining transfer conditions
5.5.3	Other advanced commands
5.6	COSMOS Spooling
5.6.1	COSMOS Spooling Service program
5.6.2	Maintaining definitions of printers
5.6.3	Some other commands

6 PERIPHERALS AND SPOOLING SUPERVISION¶

Section
6.1	Peripherals as seen from the file system	229
6.1.1	File access for peripheral files	231
6.2	Spooling system	231
6.2.1	Preparing a printer for spooling	233
6.2.2	Administering spooling pages	235
6.2.3	Starting and stopping spooling	237
6.2.4	Spooling headers, conditions and forms	237
6.2.5	Printing documents or files	241
6.2.6	Controlling the spooling queue	243
6.2.7	Controlling the file currently being printed	246
6.2.8	Spooling using COSMOS Remote File Access	248
6.3	Commands for handling mass-storage devices	250
6.4	Some important commands and variables for terminals	251
6.4.1	Terminal type	251
6.4.2	The ESCAPE function (ESC)	253
6.4.3	Background Allocation System	254
6.4.4	Some variables in the terminal datafield	258
6.4.5	Security primitives	265

7 TAKING BACKUP¶

Section
7.1	Why and how often you should take backup	267
7.2	SINTRAN commands for taking backup	269
7.3	Using the Backup System	270
7.3.1	Device copy	271
7.3.2	Commands for selective copying of files	273
7.3.3	Modifying the copying mode	283
7.4	Running stand-alone programs for taking backup	284
7.4.1	Example of running Filesystem Investigator	285
7.4.2	DISC-TEMA	286
7.4.3	DIR-BACKUP	287

8 MAIL SUBSYSTEM¶

Section	Page
8	MAIL SUBSYSTEM

Norsk Data ND-30.003.7 EN

Page 12¶

9 ACCOUNTING (ADVANCED)¶

Section	Title	Page
9.1	Installation	293
9.2	Initializing, starting and stopping ACCOUNTING	294
9.3	ACCOUNTING Service Program	296
9.3.1	Creating and deleting background projects	297
9.3.2	Creating and deleting RT projects	298
9.3.3	Dumping and inspecting ACCOUNTING information	299
9.3.4	Deleting ACCOUNTING information	303

10 PREVENTIVE MAINTENANCE AND TEST PROGRAMS¶

Section	Title	Page
10.1	Environmental requirements	305
10.2	TPE Monitor and ND-100 test program overview (ADVANCED)	307
10.2.1	Example of running CONFIGURATION	310
10.3	TEMICS for the ND-500/2 CPUs (ADVANCED)	312
10.4	The File System Investigator (ADVANCED)	316
10.4.1	Directory consistency check	316
10.4.2	Correcting errors	317
10.4.3	More hints about correcting errors	323

11 ERROR SUPERVISING¶

Section	Title	Page
11.1	The main types of serious errors	325
11.2	Error logging	326
11.3	Overview of SINTRAN error messages	327
11.3.1	Format of error messages related to RT-programs	327
11.3.2	Format of the tables describing the error messages	328
11.3.3	SINTRAN run-time error messages	329
11.3.4	Some SINTRAN file system error messages	335
11.4	Using MENTO (ADVANCED)	344
11.5	RT-program hang (ADVANCED)	346
11.6	Stuck terminals	347
11.7	TELEFIX	349

12 PATCHING¶

Section	Title	Page
12.1	Patching when loading SINTRAN from floppy diskettes	351
12.2	Patching with SINTRAN commands	352
12.3	Patching with DMAC and FMAC	353

Norsk Data ND-30.003.7 EN

Page 13¶

Appendices¶

Section	Title	Page
A	CONFIGURATION-DEPENDENT INFORMATION	355
B	BINARY, OCTAL AND HEXADECIMAL NUMBERS	357
C	MASS STORAGE DEVICE NAMES	361
D	SINTRAN K-VERSION, LAYOUT ON DISK (ADVANCED)	365
E	SINTRAN K-VERSION, PHYSICAL LAYOUT IN COMPUTER (ADVANCED)	369
F	FILE SYSTEM LAYOUT ON DISK (ADVANCED)	379
G	PHYSICAL CHARACTERISTICS OF DISKS (ADVANCED)	387
H	FILES USED TO STOP AND START THE SYSTEM	391
I	EXAMPLE OF INFORMATION FOUND IN CSI	403
J	EXAMPLE OF PRODUCT DESCRIPTION (PD) SHEETS	405
K	SWITCH SETTINGS (ADVANCED)	409

Index ------------------------------------------------------------------------ 424

Norsk Data ND-30.003.7 EN

Page 14¶

I'm unable to convert the document directly as it appears to be blank with only a page number and document identifier at the bottom. If there is another page with content, please share it for conversion.

Page 15¶

LIST OF FIGURES¶

Title	Page
1. The operator panel (until 1984)	9
2. The display panel (until 1984)	11
3. Operator panel (from 1985)	13
4. The display panel (from 1985)	16
5. Operator panel on the SMD disks	22
6. Removing a SMD disk pack	23
7. Locking the SMD disk heads	24
8. Operator panel on the MMD disk	25
9. The File store cabinets	26
10. Front panel of the RSD disk	27
11. Removing a RSD disk pack	28
12. Inserting cartridge tape into an 8 inch streamer	29
13. Inserting cartridge tape into a 5 1/4 inch streamer	30
14. Write-protecting the streamer cartridge	31
15. The ND-100 and ND-500 circuit breakers	33
16. The ND-100 and ND-500 battery switches	34
17. The Compact circuit breaker	35
18. The Satellite mains switch	36
19. The hardcopy console terminal	37
20. The Tandberg TDV 2200/9 terminal	38
21. The FACIT 4440 - TWIST terminal	39
22. The EPSON RX-80 printer	41
23. SINTRAN memory, image and save-area	65
24. ND-500 physical memory configuration	79
25. ND-500 actual memory configuration	80
26. Overview of the ND-500 Multi-CPU	81
27. How a domain is organized on files	103
28. Execution of a ND-500 domain (as seen from ND-500)	107
29. The configuration program and the parts of SINTRAN affected	120
30. Example of an indexed file	142
31. Example of a contiguous file	143
32. Example of directory structure (simplified)	148
33. Example of directory structure	152
34. A small network using HDLC or Megalink	181
35. A small Ethernet network	182
36. Example of interconnection in the Connect-To system	184
37. Example of interconnection using COSMOS remote file access	205
38. Example of interconnection using COSMOS File-Transfer	216
39. Example of interconnection using COSMOS Spooling	221
40. The spooling system	232
41. Simplified model of user dialogue with an application	259
42. Several generations of a complete backup	268
43. Example of incremental backup using several directories	279
44. SINTRAN VSX - Physical memory layout	369
45. SINTRAN VSX - Page Index Table layout	371
46. SINTRAN VSX - Interrupt level usage	373
47. SINTRAN VSE - Physical memory layout	374
48. SINTRAN VSE - Page Index Table layout	377

Norsk Data ND-30.003.7 EN

Page 16¶

Title¶

	Title	Page
49	SINTRAN VSE - Interrupt level usage	378
50	File system overview	379
51	Master block	380
52	Bit-file	381
53	User file	382
54	User entry	383
55	Object file block	384
56	Object entry	385
57	Indexed and contiguous file organization	386
58	Disk pack	387
59	ND-100 and ND-110 CPU cards	409
60	The Telefix switches on the operator panel	412
61	Terminal interfaces	414
62	The OMNI hardcopy console	417
63	EPSON LX-80 printer connected to Tandberg terminal	420

Norsk Data ND-30.003.7 EN

Page 17¶

List of Tables¶

Title	Page
1. Categories of SINTRAN user area	3
2. ND product groups requiring separate start and stop handling	45
3. System-included RT-programs and COSMOS	56
4. Values for default memory allocation	80
5. Standard SINTRAN user areas	131
6. System files	132
7. Formula for calculating disk space for SINTRAN VSX - K	139
8. Example of different file types	141
9. Example of main and default directories	150
10. File access codes	166
11. Example of directory organization of a small system	174
12. Example of directory organization of a large system	177
13. SCRIPT identifiers in Connect-To	193
14. Installation of COSMOS RFA	205
15. Installation of COSMOS CFT	216
16. Installation of COSMOS Spooling	222
17. File access codes for peripherals	231
18. Standard ND terminal types	252
19. Values to select terminal transmission speed	260
20. The Backup System commands	270
21. ND-100 test programs	309
22. TEMICS main tests	313
23. Commands in the Filesystem Investigator	317
24. SINTRAN run-time error messages	331
25. Some error codes from floppy and magtape controller	341
26. Binary, octal, and hexadecimal numbers	357
27. Mass storage device names	363
28. Physical characteristics of various disk types	390
29. The ALD setting on the CPU card	410
30. Console transmission speed	411
31. Console and modem transmission speed when using Telefix	413
32. Terminal transmission speed	414
33. Terminal numbers and device numbers	416
34. Some ND-relevant OMNI configuration parameters	418

Norsk Data ND-30.003.7 EN

Page 18¶

Norsk Data ND–30.003.7 EN

Page 19¶

SINTRAN III SYSTEM SUPERVISOR¶

SYSTEM SUPERVISION OVERVIEW¶

An ND-100 or ND-500 computer installation needs to be supervised by a trained technician. This person is usually referred to as the System Supervisor or Operator.

1.1 Job description for the System Operator¶

A System Operator is responsible for the day-to-day operation of the computer:

defining user areas and user privileges in SINTRAN and application programs
starting and stopping SINTRAN and application programs
taking backup
installing disk packs
maintaining peripheral equipment (e.g. printers, terminals)
helping users (trouble shooting, training, information)
installing new application software
calling ND Service for help if needed
keeping informed about news from ND (new products and manuals)

1.2 Job description for the System Supervisor¶

The System Supervisor's job may include all of the above functions. In addition, he is responsible for:

loading new SINTRAN versions and corrections (patches)
maintaining the accounting system (if used)
optimizing performance (tuning)

Page 20¶

SINTRAN III SYSTEM SUPERVISOR¶

SYSTEM SUPERVISION OVERVIEW¶

making patches
running test programs
planning the company's future computer-needs

Generally speaking, a System Supervisor needs to have more basic computer knowledge than is usually required of an Operator. The way either of these jobs is defined, however, depends on the size and complexity of the system. In the case of small systems with a small number of applications, the above functions might all be carried out by the same person. Large installations with many computers often employ many technicians with specialised duties.

When a company wishes to make use of Norsk Data's service facilities a service contract is drawn up, setting out the specific requirements of the company concerned. This contract states:

How much operating/supervising assistance is to be provided by ND.
How fast the company is guaranteed to receive service

Please ensure that all staff involved in using or operating the system have the documentation and the training they need. ND offers a wide range of product-oriented courses, which can be tailored to your specific requirements.

Norsk Data's monthly publication, Customer Support Information, contains news about products and documentation as well as technical hints. It also contains information about modifications and corrections needed for existing software products. This publication is sent free of charge to all ND customers.

The preface to this manual includes a list of current manuals of use to System Supervisors and Operators.

Norsk Data ND-30.003.7 EN

Page 21¶

SINTRAN III SYSTEM SUPERVISOR¶

SYSTEM SUPERVISION OVERVIEW¶

1.3 Categories of user area¶

SINTRAN has three different categories of user area, each with its own privileges:

User category	SINTRAN III privileges
"public"	public commands
RT	public and RT commands
SYSTEM	all commands

Table 1. Categories of SINTRAN user area

NOTE! In earlier versions of this manual, the term user has often been used synonymously with user area. In order to avoid confusion, we have chosen now to reserve the term user for the human user, except in compounds such as user SYSTEM and user RT, where user is still used to mean user area.

All categories of SINTRAN user area have the following in common:

They are accessed via a terminal, or by submitting batch jobs to a batch processor.

They are identified when logging in, or as the first command in a batch job, by specifying the SINTRAN user name.

Many users can simultaneously be logged in on the same user area.

Every user has the freedom to decide whether or not to protect the SINTRAN user area with a password. The privileged user areas SYSTEM and RT should always have PASSWORDS. Otherwise unauthorized persons will be able to log in and damage files or gain access to confidential information. If you are able to log in as user SYSTEM or RT, you are capable of accessing all the information stored in the computer. Passwords should also be changed regularly (for example once a week, month or half year). The command for changing a password is simply:

@CHANGE-PASSWORD

Norsk Data ND-30.003.7 EN

Page 22¶

SINTRAN III SYSTEM SUPERVISOR¶

SYSTEM SUPERVISION OVERVIEW¶

Make a habit of logging out when leaving the terminal for longer periods, and never leave the terminal when logged in as user SYSTEM or RT!

User SYSTEM is a standard SINTRAN user area intended for use by Operators and System Supervisors. Many special commands are available in addition to those for the public and RT user areas. Some of the special commands activate SINTRAN subsystems: The SINTRAN Service Program and the RT-Loader (the latter also available for user RT).

User RT is also a standard SINTRAN user area. It exists on all ND computers and is mainly used for controlling RT programs. RT programs execute closer to the kernel of the operating system and are able to carry out privileged tasks.

Many ND products have special commands related to the operating of the computer. To be able to execute the commands, you must be logged on as user SYSTEM. Examples are the XMSG command program and some of the commands in the MAIL subsystem.

You are strongly advised NOT to experiment with system commands if you do not know what the result will be. The result may be days or weeks of lost work! No user without a thorough knowledge of SINTRAN should be given access to the SYSTEM password.

The shared resources of the installation - hardware devices (such as floppy diskettes and printers) and shared programs (such as compilers and editors) - are all owned by user SYSTEM. The resources are associated with files. In the case of peripheral devices, these are called peripheral files. User SYSTEM is automatically searched for files when another user refers to files not found in her/his own user area.

In addition to such supervisor programs/program parts, you must use the console terminal (terminal number 1) for some of the basic operations, for example loading SINTRAN and operating ND-100. See chapters 2 and 3. When the command @SET-UNAVAILABLE has been given, it is only possible to log in from the console terminal. The system is made available again by giving the command @SET-AVAILABLE. Both commands are restricted to user SYSTEM.

The product USER-ENVIRONMENT (UE) is delivered as a standard software package with new computers. The intention of this program is to make it easier for people who are not computer experts to use the ND computers. USER-ENVIRONMENT also increases the degree of security on ND systems, helping to prevent unauthorized persons from accessing SINTRAN user areas and stealing data. Data security is very important if your computer is part of a data network. It is possible to select which terminals UE shall be enabled for. It is a good idea to make UE obligatory for all terminals that are accessible via the network.

The "visible part" of UE consists of menus handling logging in and out, accessing SINTRAN, starting programs etc. In this way UE can be regarded as a user-interface outside SINTRAN.

Norsk Data ND-30.003.7 EN

Page 23¶

SINTRAN III SYSTEM SUPERVISOR¶

SYSTEM SUPERVISION OVERVIEW¶

UE has its own user category: UE-users. A UE-user is not the same as a SINTRAN user area. A UE-user has a name which can be different from all SINTRAN user names. All UE-users MUST have UE-passwords. This comes in addition to any SINTRAN password. If UE is enabled for the terminal you are working on, you must log in to UE before you can do any work on the computer.

A UE-user can access one or more user areas. UE-users are defined by an authorized UE-user through the UE profile manager (UE-PMAN).

1.4 Software versions required for running SINTRAN III K¶

SINTRAN III version K requires the following versions of different subsystems. You should check that you have the correct versions after SINTRAN has been installed. The version identification is part of the file name of all files containing subsystems. For the subsystems with a user interface (for example ND-500 MONITOR), the identification is also displayed as a part of the program heading when activating it.

Subsystem	Version Requirement
ND-500 MONITOR	Only the H version of the ND-500 background Monitor (ND-210333) can be used.
ND-500 SWAPPER	Only the H version of the ND-500 Swapper (ND-211034) can be used.
XMSG	Only the K version of XMSG (ND-210373) can be used.
COSMOS BASIC MODULE	The D version of COSMOS Basic Module (ND-210374) must be used together with XMSG version K.
BACKUP SYSTEM	The H version of the Backup system (ND-210337) is required to handle more than 256 files per user.
FILE MANAGER	Version C of the File Manager (part of ND-210518) handles 4096 files per user.
FILE SYSTEM INVESTIGATOR	The O version of the File System Investigator is required to handle more than 256 files per user.
LINKAGE LOADER	The H version of the Linkage Loader (ND-210319) is modified to handle communication with RT programs due to changed RTFIL format.
SYMBOLIC DEBUGGER	The F version of the Symbolic Debugger (ND-210336) may be used for debugging RT programs.

Norsk Data ND-30.003.7 EN

Page 24¶

SINTRAN III SYSTEM SUPERVISOR¶

SYSTEM SUPERVISION OVERVIEW¶


TELEFIX-LOCAL	Version C of Telefix-Local (ND-210775) is required.
USER ENVIRONMENT	The C version of User Environment (ND-210518) offers a highly improved performance when used together with version K of SINTRAN.

Norsk Data ND-30.003.7 EN

Page 25¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

CHAPTER 2¶

HARDWARE OPERATIONS¶

This chapter explains the principal hardware operations carried out by system supervisors and operators:

using the operator panel
changing removable disk packs
using streamer tape for backup on configurations with fixed disk drives (for example Satellite and Compact)
powering on and off the installation

See the manual ND Backup User Guide (ND-60.250) for the use of magnetic tapes and floppy diskettes.

2.1 Using the operator panel¶

Two main types of operator panel are used on the ND-100 and ND-500 computers. There are separate sets of operating instructions for each panel. The most important operator functions are as follows:

| STOP |¶

Hardware stop of the ND-100 computer:

The ND-100 CPU is forced to give up execution of instructions. Program execution can be resumed without loss of information. The ND-100 CPU enters OPCOM mode.

| MCL |¶

Hardware initialization of the ND-100 CPU and interface parts:

Vital information in registers, etc. is cleared. The program execution is stopped and OPCOM mode is entered. The computer becomes ready to be restarted. Program execution cannot be resumed. The contents of the memory remains unchanged (restart without loading possible).

| LOAD |¶

The ND-100 CPU is instructed to load a program (either SINTRAN or a stand-alone program) from a peripheral device into ND-100 memory. The ND-CPU starts program execution automatically when the loading is finished. The ND-100 CPU leaves OPCOM mode.

Norsk Data ND-30.003.7 EN

Page 26¶

SINTRAN III System Supervisor Hardware Operations¶

Mode. You decide which device to load from by setting a switch on the ND-100 CPU card (ALD switch). The switch setting is described in Appendix K.

Put the ND-100 CPU into OPCOM mode. When in OPCOM mode, you are able to communicate with the ND-100 CPU from the console terminal (and from this terminal only). OPCOM is either used for activating basic operations or for debugging of ND-100.

If your operator panel has a key switch, it has three settings:

Setting	Description
LOCKED	The operator panel is locked; the panel buttons activate the panel functions. All power supplies are on. This is the normal operating mode.
ON	The operator panel is unlocked, the panel buttons can be used to activate the panel functions. All power supplies are on.
-	The power supplies are turned off. Standby power from a separate battery is still present in some cabinets.
OFF	All power to the computer is turned off. The computer is "dead". Old memory and register contents are lost.
STANDBY	The main power supply is turned off. Standby power is present if you turn the key from "ON" to "STANDBY", and memory and registers remain unchanged.

The standby power feeds energy to the parts of the computer that are vital for preserving the state of execution, in particular the main memory. The energy comes from a separate rechargeable battery. The computer is not able to run in this state. No vital information is lost as long as the battery has energy (guaranteed for at least twelve minutes).

CAUTION! When the computer is working, the key switch should always be turned to "LOCK" to prevent undesired use of the panel functions, and to ensure that power-fail handling works! You are also strongly advised to remove the key from the operator panel (but keep in mind where you store it).

Norsk Data ND-30.003.7 EN

Page 27¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

NOTE! See section 2.4 for powering on the computer. It is NOT SUFFICIENT to turn the key to "ON".

2.1.1 ND-100 and ND-500 operator panels until 1984¶

![Operating buttons and key switch illustration]

Figure 1. The operator panel (until 1984)

OPERATING¶

Turn key switch to "ON".
Select function by pressing one of the following buttons:

Turn key switch to "LOCKED" after use.

IF ND-500 WITH 2 CABINETS¶

If you have a two-cabinet model of ND-500, you also have an operator panel on the ND-500 cabinet. The only operation available from this panel is hardware initialization of the ND-500 CPU. The ND-500 must be software-stopped from ND-100 before you carry out this operation.

Turn ND-500 key switch to "ON" and press MCL.

Norsk Data ND-30.003.7 EN

Page 28¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

The ND-500 is started by software running in the ND-100: the ND-500 MONITOR. The ND-500 CPU is normally initialized from this monitor.

LIGHT INDICATORS¶

"POWER" The main power is present.
"RUN" The ND-100 CPU is running.
"STOP" The ND-100 CPU has stopped (opposite of "RUN").
"OPCOM" OPCOM mode is active.

IF ND-500 WITH 2 CABINETS¶

There are two light indicators:

"RUN" The ND-500 CPU is running.

When the ND-500 is working, this light flashes. The length of the flashes indicates the degree of utilization: the more the ND-500 is being utilized, the longer each flash will be.

"POWER" This light is always on when the main power is on in the ND-500 cabinet.

The display panel gives information about what is going on inside the ND-100. Some of the displayed information relates to the hardware (you don't need to understand all of it to be able to make use of it). The information displayed sometimes changes when using OPCOM.

Norsk Data ND-30.003.7 EN

Page 29¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

Display Panel

Figure 2. The display panel (until 1984)

UTIL (UTILISATION)¶

An indication of how much time the ND-100 is idle. The amount of idle time is indicated by the number of black segments shown. Usually only a few segments are black.

HIT (CACHE HIT RATE)¶

The ND-100 CPU has a small, fast, primary memory where the most recent instructions and data are stored. This is the cache memory. When the ND-100 CPU finds the desired information in cache (hit in cache), the program execution becomes faster. The more black segments, the better. Usually almost all segments are black. Cache memory is optional.

(PROTECT) RING¶

The ND-100 (and SINTRAN) has a ring protection system. The ring protection is used to separate RT programs into four categories with different privileges. The ring protection is only used when the paging system (MMS) is active (paging on). The ring usage is:

0 Background RT programs (lowest privileges)
1 RT programs allowed to access RTCOMMON
2 SINTRAN and RT programs using privileged instructions
3 SINTRAN segment administration

Norsk Data ND-30.003.7 EN

Page 30¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

A program executing on a ring cannot access pages belonging to a lower ring. The active ring changes rapidly when running SINTRAN.

The different rings are symbolized as follows:


Paging off	Ring 0	Ring 1

MODE
When paging is on, "P" is displayed. "I" is displayed when the interrupt system is on.

SINTRAN K VSX always runs with "P" on, while the "I" is turned off for short intervals.

ACTIVE (INTERRUPT) LEVEL
This display shows the most recent interrupt levels used. The interrupt levels are in reality active for imperceptibly short periods at a time. The black segments therefore stay black for longer, in order to be visible to the human eye.

Different software parts run on different levels. The 16 interrupt levels are numbered from 0 to 15. See appendix E for interrupt level usage.

The large number of interrupt levels makes it possible to use external interrupts to activate small program routines directly (drivers handling external devices), or to activate software for specific purposes (direct task).

Norsk Data ND-30.003.7 EN

Page 31¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.1.2 All ND computers from 1985¶

Diagram

Figure 3. Operator panel (from 1985)

The operator panel can operate in three different modes:

Normal
Advanced
TELEFIX

The functions that can be affected within an operating mode are lit up on the operator panel. The operating mode field shows the state of the control panel.

To be able to use the operator panel:

Turn key switch to "ON" (if present).

You now enter the normal mode of operation.

SINTRAN FROM NORMAL MODE¶

To start SINTRAN, press the field START

(This corresponds to MCL and LOAD)

The operating mode field goes from "OPERATING" to "RUNNING".

Norsk Data ND–30.003.7 EN

Page 32¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

To stop ND-100 CPU, press STOP field.
The operating mode field goes from "RUNNING" to "OPERATING".

ENTERING THE ADVANCED MODE¶

Turn key switch to "ON" (if present).

Press the rightmost field (1) and keep pressed while pressing the leftmost field "STOP" (2).

STOP  |   |   |   |   |   |   
      |   |   |   |   |   |   
 2 ▲  |   |   |   |   | 1 ▲

The operator functions STOP MCL LOAD OPCOM are directly available in the advanced mode.

RETURN TO NORMAL MODE¶

To go from advanced to normal mode, press the same buttons in the same sequence as for entering the advanced mode.

The control panel also returns to normal mode if no function is selected within approximately 7 minutes.

IF ND-500 CONFIGURATION¶

When the ND-500 CPU is running, the operating mode field "OPERATING" flashes. The more the ND-500 CPU is being utilized, the longer each flash will be.

TELEFIX MODE¶

The TELEFIX mode is only used for remote service diagnosis from the ND Service Centre. The console line into the CPU is connected to a modem when the TELEFIX mode is active (the modem is not an integral part of the the computer).

The Telefix mode is only entered when the number is dialled (the modem receives a carrier). The operator panel can respond in two different ways when this happens, depending on the setting of a switch on the back of the operator panel. See appendix K.

Norsk Data ND-30.003.7 EN

Page 33¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

LISTEN ON/OFF¶

LISTEN ON means that the ND Service Centre gets a copy of all information sent to the console terminal.

LISTEN OFF means that no output goes to the ND Service Centre.

REMOTE/LOCAL¶

REMOTE means that the ND Service Centre controls the input to the console line.

LOCAL means that you control the input to the console line via the console terminal.

The mode LOCAL/LISTEN OFF corresponds to the normal operating mode (as TELEFIX is not used).

You can control the operating mode of the TELEFIX after your modem is dialled:

Turn key switch to "ON" (if present).

Select the desired TELEFIX operating mode by using the two rightmost function fields on the operator panel. Each field controls one of the two TELEFIX mode descriptors. Pressing one of them causes the opposite mode descriptor to appear.

TELEFIX
LOCAL
(□)
REM
(□)

LISTEN ON
(□)
LISTEN OFF
(□)

CAUTION!¶

Make sure that nobody can dial your computer and get control of it under normal working conditions! Either set the default TELEFIX mode to LOCAL/LISTEN OFF or disconnect the modem.

Norsk Data ND-30.003.7 EN

Page 34¶

DISPLAY PANEL¶

The layout of the information displayed on the display panel differs from that on the panel used until 1984. Since there have been no changes in the architecture of the ND-100, the meaning of the information is the same as before. See section 2.1.1 for description.

UTILIZATION	CACHE HIT RATE	PROTECT RING	INTERRUPT	PAGING
0	0	-2	ON	OFF
DAY: 16	TIME: 21:32:40
ACTIVE LEVEL	[15][14][13][12]	[11][10][9]	[8][7][6][5]	[4][3][2][1][0]

Figure 4. The display panel (from 1985)

2.1.3 OPCOM Reference Section (ADVANCED)¶

OPCOM is an acronym for OPerator's COMmunication. It is a small micro program inside the ND-100 CPU. It can only be used from the console terminal. It is mainly of interest for debugging and service purposes. Some of the commands are also relevant for supervisors and operators.

Entering OPCOM mode does not affect the operating mode of the CPU. If it is running, it continues to run. If you run a program from the console and enter OPCOM, input from the keyboard goes to the ND-100 CPU, while output from the program is unaffected. While in the OPCOM mode, it is not possible for you to use the console to communicate with SINTRAN. When you leave OPCOM, you resume normal communication with your program.

OPCOM accepts only uppercase letters. Some commands must not be terminated by CR. All characters that you must type (both visible and invisible) are therefore shown in this reference section. In both input and output, OPCOM uses only octal numbers (use of radix specifier is not possible).

Norsk Data ND-30.003.7 EN

Page 35¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

How to activate the most important operator functions via OPCOM:¶

ENTER OPCOM
Use the command @OPCOM from user SYSTEM or activate OPCOM from the operator panel.

The prompt # appears on the console terminal to indicate that OPCOM is activated and ready to accept commands.

You can give these commands either by pressing a button on the operator panel or by typing the command on the console keyboard:

Command	Action
STOP	#STOP↵
MCL	#MCL↵

NOTE: You are advised to use the MCL button on the operator panel if you have an ND-110/CX CPU. (in order to renew the micro-program).

When initializing is finished, two number signs are displayed: ##

MAKE SURE THAT BOTH NUMBER SIGNS ARE DISPLAYED BEFORE GIVING THE LOAD COMMAND.

Command	Action
LOAD	#&

This load is performed in accordance with the setting of the Automatic Load Descriptor (ALD switch). See appendix K for switch setting.

LOADING FROM FLOPPY

1560&¶

This command loads from FLOPPY-DISC-1, unit 0. Loading from floppy is mainly used for running stand-alone programs (backup or test programs) or loading a new copy of SINTRAN. When there are two floppy units, this unit is usually placed at the left-hand side.

Norsk Data ND-30.003.7 EN

Page 36¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

To load from FLOPPY-DISC-2, unit 0, use:

1570&¶

This floppy unit is seldom present. It is not possible to select any other floppy drive than unit 0.

ALD VERIFY¶

You examine the setting of the ALD switch by:

112/xxxxxx¶

where xxxxxx is the switch setting. The most often used values for xxxxxx are:

	Description
21540	ECC/SMD disk controller 1, unit 0.
20500	ST-506 "winchester" disk controller 1, unit 0.

The corresponding SINTRAN disk names are: DISC--1, unit 0. See appendix C for a list of legal names.

It is not possible to select any other disk drive than unit 0 in connection with the ALD descriptor (see appendix K). Loading from disk is always done from disk unit 0.

LOAD FROM DISK CONTROLLER 2¶

If you have to load from disk controller 2, you must give one of the following commands in OPCOM:

	Description
21550	ECC/SMD disk controller 2, unit 0.
20510	ST-506 disk controller 2, unit 0.

The corresponding SINTRAN disk names are: DISC--2, unit 0

LEAVE OPCOM¶

OPCOM is left automatically when the load is completed and the ND-100 is running, but you can also do this manually.

Norsk Data ND-30.003.7 EN

Page 37¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

Using OPCOM sometimes affects the display panel information. To restore the normal display when leaving OPCOM, give the following commands:

#ACT/

Key	Description
ESC	(It is only possible to leave OPCOM if the ND-100 is running)

PROGRAM CONTROL¶

Make ND-100 continue program execution from current instruction:

#! (This is of interest if the STOP function has been used by accident.)

Restart of SINTRAN if MACM is loaded (cold start):

#22!

Simulated powerfail restart of SINTRAN:

STOP followed by #20!

Start a program from location xxxxxx:

#xxxxxx!

USER REGISTER¶

The U register is also accessible from programs. DISC TEMA (for taking backup) uses this register to indicate how fast the backup is taking place, by recording the number of the disk cylinder currently being copied:

U/xxxxxx

This number is displayed on the operator display.

The following OPCOM functions are mainly for debugging purposes:¶

MEMORY EXAMINE¶

The memory contents can be displayed both with the CPU running and stopped. It is possible to make both virtual (paging on) and physical examine (paging off) of the memory:

PHYSICAL EXAMINE¶

Select physical examine by: E↓

Norsk Data ND-30.003.7 EN

Page 38¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

VIRTUAL EXAMINE¶

Select virtual examine via page table x (0 to 17B).
See appendix E for page table usage.

Calculate input to OPCOM:

a) ND-100 with MMS II: y = x / 4,
z = y * 10B + (x - y*4B)
(y is always a whole number, obtained by ignoring any numbers after the decimal point)

b) ND-110/CX: z = x

Input to OPCOM: zE↓

Examine the contents of a memory location xxxxxx (0 ≤ xxxxxx ≤ 177777):

xxxxxx/yyyyyy     (yyyyyy is the contents)

Examine and change the contents of a memory location (only allowed when CPU is in STOP mode):

xxxxxx/yyyyyy zzzzzz↓ (zzzzzz is the NEW contents)

Examine the contents of the memory area from xxxxxx to yyyyyy:

xxxxxx<yyyyyy↓

REGISTER DUMP¶

If SINTRAN stops unexpectedly (system crash), you should perform a register dump in combination with a dump of memory contents (by the stand-alone program MEMTOF). The output from the dump is used by ND Service for fault finding. See also chapter 11 for how to do this.

The registers that are the most relevant to examine are those that are used by user programs and by SINTRAN: the register block; and those that are used only by SINTRAN: internal registers.

REGISTER BLOCK¶

To dump the register block (that is the registers S D P P B L A T X on all interrupt levels):

0Q17RD↓

INTERNAL REGISTERS¶

To dump the internal registers:

IRD↓

Norsk Data ND-30.003.7 EN

Page 39¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.2 Using disks¶

It is only possible to change disk packs on a disk drive with a removable pack. Such disk drives are always placed in external cabinets outside the computer. They must also be switched on/off manually.

Internal disk drives (as in Compact and Satellite) are of the fixed disk pack type. You cannot change disk packs on these. They are switched on/off automatically when the computer is powered on/off.

The current types of removable disk pack delivered with ND computers are the SMD (Storage Module Drive) and RSD (Removable Storage Drive) families.

The FSD (Fixed Storage Drive) and MMD (Mini Module Drive) disks are fixed. The FSD and RSD disks are placed in File Store cabinets.

CAUTION!
If you suspect a disk pack to have been subjected to a head-crashed drive, DO NOT MOVE IT TO ANOTHER DRIVE. The result may be another ruined disk drive. Also, DO NOT INSTALL ANY OTHER DISK PACK IN THE SUSPECTED DRIVE.

CAUTION!
Keep disk packs containing valuable data stored in a safe place (fireproof, smokeless, dustfree, no static electricity, no strong magnetic fields). NEVER DROP OR SHOCK A DISK PACK.

Norsk Data ND-30.003.7 EN

Page 40¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.2.1 The SMD disks¶

SMD OPERATOR PANEL¶

The SMD disk packs are delivered in two sizes with the different storage capacities 75 and 288 MB. They are mounted in disk drives which are similar to operate.

READY	START	FAULT	PROTECT
•	•	•	•

Unit No. plug

Figure 5. Operator panel on the SMD disks

START SMD DISK DRIVE¶

Install disk pack.
Push the "START" button. The "START" light should come on.
Wait for the "READY" light to come on.

The "READY" light flashes until the rotational speed of the disk is correct. Then it stays on without flashing to indicate that the disk is accessible from the computer.

STOP SMD DISK DRIVE¶

Push the "START" button. The "READY" light begins flashing.
Wait for the "READY" light to go off.

UNIT NO. PLUG¶

The unit number plug is used to give a disk drive a fixed unit number on the disk controller inside the computer.

WRITE PROTECT¶

Push the "PROTECT" button if you want to protect the disk pack from being accidentally overwritten by other data. The "PROTECT" light comes on automatically when protection is turned on. It is now only possible to READ from the disk. Push the "PROTECT" button again to allow writing on the disk pack.

Norsk Data ND-30.003.7 EN

Page 41¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

FAULT¶

The "FAULT" light comes on if errors occur during read or write. If the light goes off when you press the "FAULT" button, this means that the error was not serious. If it does not go off, call ND Hardware Service.

REMOVING DISK PACK¶

After the disk drive has stopped rotating:

Step	Description
1	To open the lid, push the lid release as shown (use both hands if necessary).
2	Place the blue, transparent cover over the disk pack as shown.
3	Turn the locking bar counter-clockwise until you hear a series of clicks.
4	Lift the disk pack out and place it on the tray, while at the same time pressing the two small bars underneath the tray together.
5	When you release the two bars, the tray is locked onto the disk pack.

Figure 6. Removing a SMD disk pack

Norsk Data ND-30.003.7 EN

Page 42¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

Installing a new disk pack is done in exactly the opposite way as removing it.

CAUTION! Place the disk on the tray AT ONCE to avoid damage from dust, shocks and static electricity!

LOCKING THE DISK HEADS¶

CAUTION! You must ensure that the disk heads are locked before the disk drive is moved. If not, they will be damaged!

Turn the power off.
Lift the top cover as shown.
Insert the disk head locking pins in these three holes.

Figure 7. Locking the SMD disk heads

Norsk Data ND-30.003.7 EN

Page 43¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.2.2 The MMD disk¶

MMD OPERATOR PANEL¶

READY	FAULT CLEAR	WRITE PROTECT

Light indicators are placed inside the operating buttons.

Figure 8. Operator panel on the MMD disk

START MMD DISK DRIVE
- Push the "READY" button.
- Wait for the "READY" light to come on.

The "READY" light comes on when the disk is rotating at the correct speed and is accessible from the computer.

STOP DISK DRIVE
- Push the "READY" button. The "READY" light goes off.

FAULT CLEAR AND WRITE PROTECT
- See corresponding description for the SMD disks.

NOTE! The disk heads are automatically locked when the power is turned off. No locking needed before moving the disk.

Norsk Data ND-30.003.7 EN

Page 44¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.2.3 The FSD and RSD disks¶

FSD and RSD disk drives are often placed in the same File Store cabinet. The large File Store cabinet is used in ordinary ND-100 and ND-500 configurations, while the small cabinet is used in ND-100 Compact configurations.

Figure 9. The File store cabinets

Norsk Data ND-30.003.7 EN

Page 45¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

The FSD and RSD operator panels are identical in layout and use.

Front panel of the RSD disk

Figure 10. Front panel of the RSD disk

START DISK DRIVE¶

If RSD disk, install disk pack.
Push the "START" button.
Wait for the "START" light to come on.

The "START" light flashes until the disk rotates at the correct speed. The light then stays on without flashing and you hear a click. The door is now locked and the disk is accessible from the computer.

STOP DISK DRIVE¶

Push the "START" button.
The "START" light begins flashing.
Wait until the "READY" light goes off and a click is heard (door unlocked).

Norsk Data ND-30.003.7 EN

Page 46¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

UNIT SELECTED INDICATOR¶

The indicator light comes on when the disk drive is selected by the computer.

FAULT CLEAR AND WRITE PROTECT¶

See corresponding description for the SMD disks.

REMOVING AN RSD DISK PACK¶

After the disk drive has stopped:

Pull the door handle to open the door.
Pull the disk pack carefully out of the disk drive.

Keep the door fully opened while doing this to release the disk pack completely from the drive.

The RSD disk pack has also a write protection mechanism, so you can choose between this and write-protecting on the disk drive.

Removing a RSD disk pack

Figure 11. Removing a RSD disk pack

When installing a disk pack, the procedure you follow is the exact reverse of the procedure followed when removing a disk pack.

| NOTE! The disk heads are automatically locked when the power is turned off (and the disk pack removed). The door is locked when the power is turned off. |

Norsk Data ND-30.003.7 EN

Page 47¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.3 Using the streamer magnetic tape¶

Two different streamer drives are used on ND computers: an 8 inch drive (Archive) and a 5 1/4 inch drive (Tandberg). Both use the same cartridge tapes.

When the streamer drive is in use the indicator light on its front panel comes on.

2.3.1 The 8 inch streamer¶

Slide the cartridge into the streamer until it stops.

This streamer drive has no door and no possibility for locking the streamer cartridge in the drive.

Inserting cartridge tape into an 8 inch streamer

Figure 12. Inserting cartridge tape into an 8 inch streamer

Norsk Data ND-30.003.7 EN

Page 48¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.3.2 The 5 1/4 inch streamer¶

Open the streamer door by pushing the knob (springy mechanism).

Slide the cartridge into the streamer until it stops.

Close the door (you hear a click when it locks).

Inserting cartridge tape into a 5 1/4 inch streamer

Figure 13. Inserting cartridge tape into a 5 1/4 inch streamer

Norsk Data ND-30.003.7 EN

Page 49¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.3.3 Write-protecting the cartridge¶

You can protect data on a cartridge from accidental overwrite by turning the write-protect plug to the position marked "SAFE". You are now only able to READ from the cartridge. You should do this for all valuable backups you have taken from disk(s) to the streamer.

Write-protecting the streamer cartridge

Figure 14. Write-protecting the streamer cartridge

Norsk Data ND-30.003.7 EN

Page 50¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.4 Switching on the installation¶

This section describes how to switch on the various types of computer and some of the most common peripheral equipment.

The computer and its peripheral equipment shall normally be left in operational condition (powered on) after the computer has stopped running. If for some reason you must stop the installation totally (for example for moving or hardware service), this should be done in the following sequence:

software-stop the computer (see chapter 3).
power off printers.
power off the computer.
stop and power off external disks (not present for Satellite and most Compacts).
power off the terminals and remaining peripherals.

| CAUTION! Remove streamer tape and floppy diskettes from the drives before the computer is switched off. If this is not done, they may be damaged by electric shock. |

See also separate vendor manuals for your particular peripheral equipment.

SINTRAN "hangs" if you try to start the ND-100 computer with a system disk that is not ready (not rotating at the correct speed). By "hangs" we mean that SINTRAN repeatedly attempts to communicate with the disk, but fails to do so. The system disk cannot be removed while SINTRAN is running. REMEMBER ALWAYS TO RELEASE THE DIRECTORIES BEFORE DISKS OR FLOPPY DISKETTES ARE REMOVED FROM THE DRIVES.

Norsk Data ND-30.003.7 EN

Page 51¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.4.1 The ND-100 and ND-500 computers in large cabinet¶

This procedure is valid for all ND-100/ND-500 computers placed in large cabinets. Make sure that your service contract allows you to do this.

Do the following for each computer cabinet in your configuration:

FROM THE FRONT - Remove the front panel to access the circuit breakers. - Switch the circuit breakers S1 - S9 on by placing the circuit-breaker handles in the upper position marked "1". Start with S1 and continue in ascending order.

S8 and S9 are the main circuit breakers.

Front Cover Removed
220V AC LINE


S9	S8	S7	S6	S5	S4	S3	S2	S1

Figure 15. The ND-100 and ND-500 circuit breakers

Norsk Data ND-30.003.7 EN

Page 52¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

FROM THE REAR¶

Remove the rear panel of each cabinet to access the power supply.

Set the battery switches located under the power control panel to "ON".

This enables the standby battery to be used in the case of power failure.

CAUTION!¶

In the case of some configurations, the "STANDBY" light on the power control panel comes on after the mains is switched off.

IN THESE CASES, THE BATTERY SWITCHES MUST ALSO BE TURNED OFF WHEN POWERING OFF THE COMPUTER.

This prevents the standby battery from being completely discharged and thereby permanently damaged!

Figure 16. The ND-100 and ND-500 battery switches

Replace the front and rear panels. Turn the key switch on the operator panel to "ON". The computer is now ready to be software-started (see chapter 3).

Norsk Data ND-30.003.7 EN

Page 53¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.4.2 The Compact Computers¶

This procedure is valid for all Compact computers and the small File Store cabinet (same cabinet type):

If present, turn the key switch to "ON".

Figure 17. The Compact circuit breaker

The computer is now ready to be software-started (see chapter 3).

Norsk Data ND-30.003.7 EN

Page 54¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.4.3 The Satellite computers¶

Turn the mains switch on (located at the rear of the terminal
Turn the key switch to "ON".

Figure 18. The Satellite mains switch

The computer is now ready to be software-started (see chapter 3).

Norsk Data ND-30.003.7 EN

Page 55¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.4.4 The OMNI hardcopy console terminal¶

This terminal (Texas Instruments OMNI 825) was the standard console terminal until 1985. All communication with the computer is written on paper. When this console terminal is used, it is also usually the error device. Such a line-oriented terminal must use screen-oriented programs (such as the NOTIS series) in line mode (terminal type 2).

Switching on the terminal:

Turn the power switch on (located at the rear of the terminal).
Set the LOCAL/LINE switch to "LINE".

See appendix K for switch settings.

Hardcopy console terminal

Figure 19. The hardcopy console terminal

Norsk Data ND-30.003.7 EN

Page 56¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.4.5 The Tandberg TDV 2200/9 terminal¶

This screen terminal is used as an all-round terminal, both for the ordinary user and as the standard console terminal for the operator (from 1985).

Turn the power switch on (located at the left side of the terminal).

Here you will also find dials to control light intensity and contrast.

The terminal should be in ON-line mode. If this is the case, the indicator light marked "LINE" will be on. If this light is not on, press the LOCAL key.

Tandberg TDV 2200/9 terminal

Figure 20. The Tandberg TDV 2200/9 terminal

Norsk Data ND-30.003.7 EN

Page 57¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.4.6 The FACIT 4440 - TWIST terminal¶

Turn the power switch on (at the bottom right-hand side of the terminal).

All other control functions are software-controlled by setup menus.

To set the terminal in ON-line mode:

Strike the SET-UP key (top left-hand corner of the keyboard)

The words "SET-UP A" are displayed in the upper, left-hand corner of the screen. You have now entered menu A.

Strike the 4 key until the word "ON LINE" appears in the upper, right-hand corner of the screen. Strike the SET UP key again to leave the menu system.

For more information on switch setting, see Appendix K.

FACIT 4440 - TWIST terminal illustration

Figure 21. The FACIT 4440 - TWIST terminal

Norsk Data ND-30.003.7 EN

Page 58¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

2.4.7 The EPSON RX/80 printer¶

This printer is now used as the standard error device. Together with a screen terminal, this device replaces the former OMNI hardcopy terminal. The error device receives all special error messages reported from SINTRAN and some application programs.

To tell the computer which output device is the error device, give the command:

@SET-ERROR-DEVICE

You find the terminal number of the error device by giving the command:

@GET-ERROR-DEVICE

To switch the printer on:

Turn the power switch on (at the bottom right-hand side of the printer).

Press the "ON LINE" button. The "ON LINE" indicator light comes on.

If the indicator "PAPER OUT" is lit, you must change the paper.

To feed the paper, set the printer in LOCAL mode by pressing the "ON LINE" button before using FF (Form Feed) or LF (Line Feed).

See appendix K for installation hints.

Norsk Data ND-30.003.7 EN

Page 59¶

SINTRAN III SYSTEM SUPERVISOR¶

HARDWARE OPERATIONS¶

Epson RX-80 Printer

Figure 22. The EPSON RX-80 printer

NOTE: The error device must always be on-line. If not, this results in reduced performance in SINTRAN, as an error program will use much of the CPU resources trying to output unprinted messages.

Norsk Data ND-30.003.7 EN

Page 60¶

I'm sorry, the page appears to be blank. If there's specific content you want to extract, please let me know!

Page 61¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

CHAPTER 3¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Except for time needed for backup and maintenance, the computer should normally run 24 hours a day, 7 days a week. As a general rule this applies also to peripheral equipment such as disks, printers and terminals.

CONTROLLED STOP¶

In some cases, however, such as when running a test program, taking backup, or modifying the system, you will need to stop and start SINTRAN. In order to be able to do this, you must first log in as user SYSTEM.

Before you stop the system, you must make sure that nobody is logged in on the computer. Otherwise valuable work could be lost. See section 3.1.

The amount of work required to do this, depends on your configuration. For example, a Satellite running just a few applications requires less supervision than an ND-500 carrying many applications.

CAUTION!	When SINTRAN is started, the user programs are aborted and all users are logged off the computer.

There are two different ways of starting/restarting SINTRAN:

WARM START¶

A warm start reloads minor parts of SINTRAN, restarts it, and initializes some parts of the system information. Currently-executing programs cease executing after the warm start is completed.

During normal operation of the system, you use warm start mainly for restarting the system after backup. It is also useful for correcting small error situations occurring in SINTRAN. In this manual warm start refers to the warm start procedure described in section 3.2.

Norsk Data ND-30.003.7 EN

Page 62¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

COLD START¶

A cold start reloads a complete copy of SINTRAN, and performs a warm start.

During normal operation of the system, you use cold start only after reconfigurations. Cold start can also be used to rectify some problems which cannot always be cured by a warm start. It should, however, not be used unnecessarily as most error information is lost by a cold start. This makes failures more difficult to diagnose for the Service people. The procedure is described in section 3.3.

Cold start also involves other procedures, depending on the method used for loading SINTRAN:

LOADING SINTRAN FROM FLOPPY¶

New versions of SINTRAN and revisions (patch files) are loaded from diskettes.

In the event of an unsuccessful cold start when correcting errors in SINTRAN, you can reload SINTRAN from a diskette.

A disk crash can also necessitate loading SINTRAN from a diskette.

When SINTRAN is running within your configuration, it is tailored to run this configuration. If you want to make changes in your configuration (for example more terminals or printers), it might be necessary to install a new copy of SINTRAN.

If you run a generated version of SINTRAN, you must order a new copy of SINTRAN from ND to be able to make changes in your configuration.

You may have SINTRAN III VSX as a standard system able to support many configurations. You use the configuration program to manipulate configuration parameters, then you do a cold start. Section 3.5 describes the configuration program.

See section 3.4 for how to load SINTRAN from floppy diskettes.

Norsk Data ND-30.003.7 EN

Page 63¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

INITIAL LOAD¶

Initial loading means loading SINTRAN into a brand new system disk. It implies somewhat more than a load of SINTRAN because some definitions about users, files and system information for SINTRAN must be made.

The initial loading of SINTRAN is normally done at ND when new computers are ordered. The procedure is described in section 3.6. It may also be necessary to do an initial load after a disk crash of the system disk.

Some of the applications programs running under SINTRAN require additional, separate procedures when stopping and starting the computer. See table 2 for which main product groups require such procedures. It is beyond the scope of this manual to give the procedures here. It is also good practice to read the PD-sheets that accompany the software products to find out what procedures are required. If you have applications programs not developed by ND, be sure that you also have the information needed to make such decisions about these products.

Note that XMSG and User Environment are part of the standard software package delivered by ND. These products are so closely integrated with SINTRAN that some information about them is included in this manual. The operator functions of the COSMOS Basic Module are described in chapter 5.

Operating system environment:
User Environment (UE)
NDIX
Fault Tolerance EXtension (FTX)

Data communication:	Databases and related tools:
XMSG	SIBAS
COSMOS Basic Module	UNIQUE
COSMOS options	TPS
SNA	TRUE
X.21/X.25/X.29	ISAM
	NOTIS-DS
	NOTIS-ID
	ACCESS

Table 2. ND product groups requiring separate start and stop handling

Norsk Data ND-30.003.7 EN

Page 64¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

3.1 Controlled stop¶

Before you stop the system, you should request all users to log out. You must also stop all active batch processors and all printers. XMSG, ND-500, UE and some special RT-programs must also be stopped. The special RT-programs to be stopped, are in general those which have RT open files, for example SIBAS, NOTIS-DS and UE. See also table 2.

It is useful to have a mode file for stopping all activity in the system. Appendix H.1 gives an example.

Before stopping the system, the following must be carried out:

Set the system unavailable to make it impossible for new users to log in (except from the console terminal).

Broadcast a message via the mail system requesting all users to log out.

Fetch the system information about activity in the system.

Give the users a chance to terminate their jobs before stopping the remaining activity.

Norsk Data ND-30.003.7 EN

Page 65¶

SINTRAN III System Supervisor¶

Stopping, Starting, and Loading SINTRAN III¶

Example of checking a system for activity¶

SET-UNAVAILABLE
TEXT: REGULAR BACKUP
@MAIL
DIRECT-BROADCAST
TYPE YOUR MESSAGE, TERMINATED BY CONTROL L:

***********************************
* BACKUP STARTS IN 15 MINUTES.    *
* ESTIMATED DURATION 1/2 HOUR.    *
* PLEASE LOG OUT!                 *
***********************************

Put a frame around the informative text. End it by typing CTRL+L.

EXIT

A few minutes later.

@TERMINAL-STATUS,,¶

LOG.NO	USER	MODE	CPU-MIN	OUT OF	LAST COMMAND
1	SYSTEM	COMMAND	1	6	TERMINAL-STATUS,,

@LIST-BATCH-PROCESS¶

1 IDLE, NO USER LOGGED IN

@ABORT-BATCH 1¶

@LIST-SPOOLING-QUEUE LINE-PRINTER,,¶

QUEUE IS EMPTY

@STOP-SPOOLING LINE-PRINTER¶

@LIST-RTOPEN-FILES,,¶

Check that no files are RT-open.

@LIST-RT-PROGRAMS,,¶

NAME	STATUS
DUMMY	READY
STSIN	PASSIVE

Check that there are no active RT-programs, and that no files are open.

@LIST-OPEN-FILES,,¶

@STOP-SYSTEM¶

The line printer with spooling is an option in this example.

Norsk Data ND-30.003.7 EN

Page 66¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

3.1.1 More about stopping different processes¶

If you for some reason need to set the system available again (making it possible for users to log in) before restarting the system, the command to use is:

@SET-AVAILABLE

Terminals¶

If it becomes necessary to log out users after having used @TERMINAL-STATUS, the command is:

@STOP-TERMINAL <terminal number>

| CAUTION! All activity on the terminal is aborted immediately. |
| ————————————————————————————————————————— |
| The users have NO chance of saving their work. |
| Therefore, BE CAREFUL! |

The command TERMINAL-STATUS <terminal number> <interval> gives information about the following processes:

Users logged in on terminals directly connected to the computer. Terminal numbers are 1, 36, 37 .. 63, 544, 545 .. 575.
Users logged in via the communication network COSMOS. These terminals are called TADs (Terminal Access Device). Terminal numbers are 768, 769 .. 863.
Started batch processors. Terminal numbers are 670, 672 ... 686 (in steps of two).

The field "Last command" is a copy of the command input line in SINTRAN. Many application programs developed by ND use this line to tell what the user is doing.

Although it is possible to stop batch processors by giving the @STOP-TERMINAL command, we advise that this method should only be used for stopping terminals belonging to groups 1 and 2 above.

Norsk Data ND-30.003.7 EN

Page 67¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Example of stopping a terminal¶

@TERMINAL-STATUS,.

LOG.NO	USER	MODE	CPU-MIN OUT OF	LAST COMMAND
1	SYSTEM	COMMAND	1	20 TERMINAL-STATUS.
38	MICKY	COMMAND	1	100 CC WP L eng 500
768	DAVE	COMMAND	0	7 DATCL

User MICKY is running NOTIS-WP. He may have files that need to be written back. Ask him!

@STOP-TERMINAL 768

You logged DAVE off the computer. On terminal 768 this message appears:

*** ABORTED BY SYSTEM ***

TADs¶

If you want to know about the activity on COSMOS TADs, there is also a dedicated command in SINTRAN for this:

@TADADM

TADADM is an acronym for TAD ADMINISTRATOR. It gives information about all TADs in the system, both passive and active. Note that there are also some COSMOS applications (servers) that make use of the TADs. In the following example, you see a server called FS Administrator. This server is used for remote file access, which enables you to read and write files on remote computers. If somebody is using the File Server at the moment you stop the TAD, this operation is aborted.

See chapter 5 for how to stop COSMOS activities.

Norsk Data ND-30.003.7 EN

Page 68¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Example of using TADADM¶

@TADADM

-------------------------------------------------------------------
TADADM Version K.    System: SPINX
-------------------------------------------------------------------
TAD/TYP  RESERV  ESCAP  PORTNO - PORTNO  TERMNO  USER                  SYSTEM
768/0      No    Enab   Discon
769/0      No    Enab   Discon
770/255    No    Enab     7       -        6     FS Administrator
771/0    BAK26   Enab    12      12       58     COSMOS-FACTORY EAGLE
-------------------------------------------------------------------
                    | 
                    | Terminal number, user name and network name
                    | of the computer. All referring to the remote
                    | computer.
                    |
Name of the reserving background program.

TAD number (same as found by @TERMINAL-STATUS).

Batch processors¶

The command to stop a batch processor is

@ABORT-BATCH

This command should be used for batch processors which are not passive. The commands @LIST-BATCH-PROCESS and @LIST-BATCH-QUEUE list information about activity on the batch processors. Be careful not to stop any important batch job! The job currently being processed is not included in the queue information. You can remove it by the command @ABORT-JOB.

All jobs in a batch processor queue are removed by the command @CLEAR-BATCH-QUEUE. This queue is also automatically cleared when the system is restarted. This means that all the jobs in the queue will need to be appended manually afterwards if they are to be processed.

Norsk Data ND-30.003.7 EN

Page 69¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Some applications make use of the batch processors, for example the ADP product ACCESS. If user DATA-DICTIONARY is logged on a batch processor, make sure that nobody is using the ACCESS application before you abort the batch job.

Example of stopping batch processors¶

@LIST-BATCH-PROCESS


1	ACTIVE, USER MADAME-MARIE LOGGED IN
2	ACTIVE, USER DATA-DICTIONARY LOGGED IN

You must ascertain that MADAME-MARIE's job is not important, and that no-one is using ACCESS.

@LIST-BATCH-QUEUE 1


1	(ELENORE)BATCH-JOB (ELENORE)BATCH-LIST

This job may need to be appended after system restart so that user ELENORE does not lose important work.

@ABORT-BATCH 1

@ABORT-BATCH 2

@LIST-BATCH-PROCESS,,


1	PASSIVE
2	PASSIVE

Printers and spooling¶

If you find out that some printers are active after having used the command @LIST-SPOOLING-QUEUE {peripheral file name},({output file}), the command to stop a printer is:

@STOP-PRINT {peripheral file name}

The printer is temporarily disabled.

Norsk Data ND-30.003.7 EN

Page 70¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

The command

@ABORT-PRINT

skips the file currently in print and advances to the first entry in the spooling queue.

In addition, the spooling process for the printer has to be stopped:

@STOP-SPOOLING

The file currently being printed is lost in a warm start. A cold start normally empties the spooling files. You can change this if you like.

Example of stopping a printer¶

@LIST-SPOOLING-QUEUE PHILIPS::

FILE CURRENTLY BEING PRINTED ON: PHILIPS::1
PHILIPS::2
LAST USED BY DAHL
LAST COPY. APPROX. 7168 BYTES LEFT TO PRINT

QUEUE IS EMPTY

There are only a few pages left to print, so you wait for the printer to finish its work before you stop it.

@STOP-PRINT PHILIPS

@STOP-SPOOLING PHILIPS

Norsk Data ND-30.003.7 EN

Page 71¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

User Environment¶

If UE is running, it should be stopped:

Stopping UE¶

Command	Note
@UE-FUNC STOP-PROFILE-MANAGER	This is for the English version.

Specify the whole "command" on one line. UE-FUNC is NOT a SINTRAN command, but an ADP program.

XMSG¶

All programs using XMSG (for example COSMOS and UE) should have been stopped before stopping XMSG itself. XMSG is stopped as follows in the SINTRAN-SERVICE program:

Stopping XMSG¶

Command	Result
@SINTRAN-SERVICE-PROGRAM
*STOP-XMSG	OK: XMSG terminated.
*EXIT

Norsk Data ND-30.003.7 EN

Page 72¶

ND-500¶

If an ND-500 CPU is present, it must be stopped. In the following example it is assumed that all processes running on ND-500 are already stopped (i.e. that all users are logged out and that all applications are stopped).

Example of stopping the ND-500¶

@ND-500-MONITOR

ND-500 MONITOR Version H .......
N500: WHO-IS-ON

===>   1 USED BY SYSTEM   ON TERMINAL   1

You are now the only user of ND-500.

N500: STOP-ND-500

You return directly to SINTRAN after having stopped ND-500.

RT-programs and open files¶

Before the system is stopped, take a look to see if there are any files that have been opened by RT-programs. If so, the RT-programs which have opened the files should be aborted, and the opened files closed. If there are other user-written RT-programs which are NOT passive, they should also be aborted. This is not necessary for the system-included RT-programs, which are more or less parts of SINTRAN. The command to list RT-programs is:

@LIST-RT-PROGRAMS (<output file>)

When you list RT-programs, the system-included RT-programs are written out first, followed by RT-programs used by application programs and the ones written by users.

Norsk Data ND-30.003.7 EN

Page 73¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

The command to abort a RT-program is:

@ABORT <RT-program name>

The commands to list and close RT-opened files are:

@LIST-RTOPEN-FILES (<output file>)

@RTCLOSE-FILE <file number>

If the procedure for stopping has been followed until now, it is not necessary to stop system-included RT-programs. Table 3 lists all the system-included RT-programs. See PD sheets and manuals for the other applications you run which can have separate RT-programs.

All open files should now be closed. The scratch files for the background processes are closed when the terminals, TADs and batch processors are stopped. An exception is your own terminal, which you have used for stopping the processes. Therefore, make sure that all your open files are also closed:

Example of closing a user's files¶

@LIST-OPEN-FILES

FILE NUMBER	DESCRIPTION
000100	{PACK-ONE:SCRATCH}SCRATCH01:DATA;1
000101	{PACK-ONE:SYSTEM}ANOTHER-FILE:SYMB;1

@CLOSE -2

CLOSE has as parameter <open file number>, which is the number output in front of the file name from LIST-OPEN-FILES. -1 closes all the user's files except scratch file. -2 closes all.

Norsk Data ND-30.003.7 EN

Page 74¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Name	Belongs to - used for/comments
1SWAP	SINTRAN kernel - used for queuing swapping requests.
5SWAP	ND-500 MONITOR kernel - used for swapping ND-500 programs.
ACCRT	SINTRAN kernel - used for RT accounting.
BAKxxx	Background process no. xx. Stopped by separate command.
BKxxx	-- " --
BCHxxx	Batch processor no. xx. Stopped by separate command.
BPTIMP	SINTRAN kernel - used for handling timeouts of background programs in configurations where background allocation is used.
COSPO	COSMOS spooling server. Stopped by separate program.
DUMM2	Dummy program used by the spooling system.
DUMMY	SINTRAN kernel - used as idle process in execution queue.
FDRTx	SINTRAN kernel - data transfer for floppy controller no. x.
FIXRT	SINTRAN kernel - handles fixing of ND-100 segments in memory.
FSART	COSMOS File Server Administrator. Stopped by separate program.
RTDIL	SINTRAN kernel - logging activity for DISC-ACCESS-LOG facility.
RTERR	SINTRAN kernel - prints error messages on error device.
RTRFA	COSMOS remote file access server.
RTSLI	SINTRAN kernel - time-slices background processes (by changing priority in the executing queue).
RWRTxx	SINTRAN kernel - block-oriented external and internal devices.
SPRTx	Spooling processor no. x. Stopped by separate command.
STSIN	SINTRAN initialization. Starts system-included RT-programs.
TADxx	Terminal Access Device no. xx. Stopped by separate commands.
TADAD	COSMOS TAD Administrator. Need not to be aborted.
TERMP	SINTRAN kernel - does user-defined termination handling of RT programs.
TIMRT	SINTRAN kernel - used for timeout on peripheral devices.
XROUT	XMSG - Management of computer names and network routing. Used by COSMOS. Stopped by separate command.

Table 3. System-included RT-programs and COSMOS

CAUTION!
"SINTRAN kernel" means that the program belongs to the inner parts of the operating system. It should not be stopped!

Norsk Data ND-30.003.7 EN

Page 75¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III

Example of stopping a user-written RT-program¶

@LIST-RTOPEN-FILES,1

FILE NUMBER 00100 : (PACK-ONE:KNUTH)ALGORITHMS:DATA::1

@LIST-RT-PROGRAMS,1

NAME	RT-DESC	STATUS
DUMMY	56730B	READY
STSIN	56756B	PASSIVE

These are system-included RT-programs. They shall not be stopped.

These belong to XMSG.

| UEXPS | 61426B | PASSIVE |

This belongs to UE.

| KNUTH | | RTWAIT |

Here you have a user-written RT-program.

You assume that the RT opened file belongs to the RT-program KNUTH, because of the name conformity. You decide to abort the RT-program because it is NOT PASSIVE.

Example continued¶

@ABORT KNUTH

@RTCLOSE-FILE 100

@LIST-RT-PROGRAMS,1

The file number is used as parameter when closing a file.

You list the RT-programs another time to ascertain yourself that KNUTH has become passive.

Norsk Data ND-30.003.7 EN

Page 76¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

At this point, all the activity in the system should be stopped. You can now stop SINTRAN itself. The command to use is:

@STOP-SYSTEM

The command cannot be abbreviated. After the command has been given, the computer enters stop mode, and stops executing instructions. OPCOM is activated (described in chapter 2) and prints out its prompt # on the console terminal.

The STOP-SYSTEM commands cause SINTRAN to save all working registers in the ND-100 CPU before stopping. Then it forces the CPU to enter stop mode. This means that the ND-100 CPU is no longer executing any SINTRAN code in memory.

The saving of the CPU's registers makes it possible to resume (continue) processing of SINTRAN and programs that were running at the moment the command @STOP-SYSTEM was executed. So, if you regret that you stopped the system, the command to use in OPCOM is:

20!

This simulates a power fail restart. If this does not work, you must carry out a warm start.

The STOP function on the operator panel does NOT have the same effect as the @STOP-SYSTEM command (see also chapter 2). It just makes the ND-100 CPU stop execution of instructions without SINTRAN being able to carry out a controlled stop by itself.

3.1.2 Stopping ND-500 CPU without stopping the ND-100¶

The ND-500 CPU can be stopped separately without stopping the ND-100. If you for example need hardware service on the ND-500 CPU, the users still have access to the ND-100. Stopping ND-100 without stopping the ND-500 CPU is impossible, as the kernel of the operating system runs in the ND-100.

Norsk Data ND-30.003.7 EN

Page 77¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

A typical example of stopping the ND-500 CPU is shown in the following:

Example of stopping ND-500 separately¶

@ND-500-MONITOR

ND-500 MONITOR Version H.......

N500: SET-ND-500-UNAVAILABLE

You make it impossible for others to enter ND-500.

You check who is using the ND-500 at the moment.

N500: PROCESS-STATUS

PROC. NO.	TERM. NO.	USER	STATUS	ND-500 CPU
1	38	SWEDISH-EXPERT	ACTIVE	5.0 S
2	39	FLOPPY-USER	ACTIVE	32.6 S
3	1	SYSTEM	IDLE	0.0 S

| Information similar to that found by @WHO-IS-ON. | Status for each user logged on (using) the ND-500 CPU. | How much time each user has got from the ND-500 CPU. |

You have logged in as user SYSTEM from the console. You see from the status above that there are two active users (running programs) on the ND-500 CPU. Your ND-500 status is IDLE because you have only entered the ND-500 MONITOR.

You request the active users to terminate their jobs, then you check the process status another time. If you exit from the ND-500-MONITOR, be aware that users are allowed to log in!

Norsk Data ND-30.003.7 EN

Page 78¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Example continued¶

FLOPPY-USER did NOT respond to your request. You decide to log him off the ND-500 CPU!

Command	Description
N500: LOGOUT-PROCESS 2	The parameter "2" is the process number found in the leftmost column from PROCESS-STATUS.
	You are now the only user of ND-500.
N500: STOP-ND-500
@	You return directly to SINTRAN.
@ND-500-MONITOR	The ND-500 CPU is restarted.
N500: START-SWAPPER

Norsk Data ND-30.003.7 EN

Page 79¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

3.2 Warm start¶

You perform a warm start from the console terminal (as user SYSTEM) or by using the computer's operator panel. Chapter 2 describes how the operator functions are activated by the different operator panel types.

The procedure for warm start is as follows:

Make a controlled stop of the computer (see section 3.1), if SINTRAN is running.
The ND-100 CPU should now have entered OPCOM mode.
Press the STOP and MCL buttons on the operator panel:

STOP	MCL

Wait a few seconds for the prompt # to be displayed on the console, then load SINTRAN by pressing the LOAD button on the operator panel:

LOAD

After you have done this, the warm start itself is carried out by SINTRAN. When a fresh copy is loaded into the computer, and the SINTRAN started, the message

"SINTRAN III RUNNING"

is displayed on the console. All users can now log in and continue working on the computer.

If you do NOT get this message at all, repeat the warm start procedure.

Make sure that OPCOM is activated before you repeat.

OPCOM is activated after the command @STOP-SYSTEM to SINTRAN is executed. There is also a separate command for activating OPCOM from SINTRAN:

@OPCOM

Norsk Data ND-30.003.7 EN

Page 80¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

OPCOM is a small operator program residing in the ND-100 CPU. It can only be used from the console terminal. When OPCOM is activated, the prompt # will appear on the screen. While OPCOM is active, the console terminal can only be used to communicate with this program. It is impossible to reach SINTRAN before you leave OPCOM. When SINTRAN is restarted, the ND-100 CPU leaves the OPCOM mode. If you want to leave OPCOM manually, press the "ESC" key on the console.

There is another way of performing a warm start that is even shorter:

After taking all necessary precautions (see section 3.1), stop all activity on the system.

Release all directories except the MAIN directory (containing SINTRAN). This is not absolutely necessary, but it ensures that you have the minimum number of open files.

If you are not logged in on the console terminal, use the command @SET-ERROR-DEVICE (terminal number) to switch all system messages to your terminal.

Type the command @RESTART-SYSTEM unabbreviated from user SYSTEM.

The command:

@RESTART-SYSTEM

has the same effect as pressing STOP and LOAD.

If this procedure does NOT work, carry out a warm start as described in the first procedure.

Norsk Data ND-30.003.7 EN

Page 81¶

Example of Warm Start Based on the Command @RESTART-SYSTEM¶

All users except SYSTEM are logged off the computer, and programs are stopped.

@LIST-DIRECTORIES-ENTERED¶

DIR INDEX	DISC-70MB-1 UNIT	PACK
0	0	PACK-ONE
1	1	PACK-TWO
2	2	PACK-SPECIAL

You must release all directories except the main. If you do not know which is the main one, you must check.

@DIRECTORY-STATISTICS PACK-ONE¶

DIR INDEX	DISC-70-MB-1 UNIT	PACK
0	0	PACK-ONE

(Main and Default Directory)

Here is the main directory!

@RELEASE-DIRECTORY PACK-TWO¶

@RELEASE-DIRECTORY PACK-SPECIAL¶

If you get the error message "FILES OPEN ON THIS DIRECTORY" you must find out which files are open, and close them.

You are logged in as user SYSTEM on terminal 39 far away from the computer room.

@SET-ERROR-DEVICE 39¶

@RESTART-SYSTEM¶

If you want future error messages to come on the console, use @SET-ERROR-DEVICE 1 afterwards.

Norsk Data ND-30.003.7 EN

Page 82¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III

3.2.1 SINTRAN Memory, Image and Save-area¶

In this section, you will find an account of the main things that the computer and SINTRAN do in a warm start. This will give you a better understanding of what kinds of error situations you can correct by carrying out a warm start, and what kind of event you can manipulate during the warm start.

The parts of SINTRAN that play an important role during warm and cold starts are located on three different areas:

memory, that is in physical ND-100 memory.
image, on the system disk.
save-area, also on the system disk.

These three areas constitute a small part of SINTRAN located on the files SINTRAN:DATA, MACM-AREA:DATA, and SEGFILE:DATA. These files are the first three files found on user SYSTEM. Each of the areas contains a separate copy of the same part of SINTRAN.

The three files contain:

The MONITOR kernel, including code to handle MONITOR calls. This make it possible to have a time-shared operating system.
Page tables to make a virtual storage concept for user programs.
Code and system information for administrating the different processes running (RT-programs).
Code to handle data transfers to and from peripheral equipment.
Configuration-dependent system information.
Code for start and restart of SINTRAN.

The save-area is not used for anything in a warm start, but is important in a cold start. The remaining parts of SINTRAN (for example code for executing commands and using the file system) are located on the files MACM-AREA:DATA and SEGFILE:DATA. The SEGFILE is divided into parts called segments. The ones belonging to SINTRAN, or closely related products, are called system-included segments.

Norsk Data ND-30.003.7 EN

Page 83¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III

Disk Page 0¶

SYSTEM DISK (MAIN DIRECTORY)¶

BOOTSTRAP AND DIRECTORY ENTRY
SINTRAN SAVE-AREA
END OF SAVE-AREA
SINTRAN IMAGE AREA

The file
SINTRAN:DATA

A small part of the file
MACM-AREA:DATA
(only SINTRAN III VSX)

A part of the file
SEGFILO:DATA

Physical Memory Page 0¶

SINTRAN MEMORY AREA
swapping area etc

Figure 23. SINTRAN memory, image and save-area

Norsk Data ND-30.003.7 EN

Page 84¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

See appendix D for details of SINTRAN layout on disk, and appendix E for layout in physical memory.

After you have performed the operator functions to carry out a warm start, the following things happen:

The bootstrap is read into physical memory by the ND-100 CPU, and is started. This is then the only executing program.

The bootstrap program copies the SINTRAN IMAGE AREA to the MEMORY AREA.

SINTRAN starts.

Some rather important predefined SINTRAN commands residing in a buffer on the SINTRAN IMAGE AREA are executed. They are called initial commands.

3.2.2 Initial commands¶

You control the warm-start procedure by defining the initial commands. The definition of the initial commands is found in the mode file usually called HENT-MODE:MODE, used in a cold start. More details of this are given in the description of the cold start (section 3.3).

You must normally use the initial commands to carry out the following:

Enter the main directory, because no disk is entered and ready to be used by SINTRAN just after a warm start.

Start a batch processor, and append to it a batch job that starts different processes and applications in your configuration.

The file appended to the batch processor is usually called LOAD-MODE, and this name is used throughout this manual. This file should start the software you had to stop when carrying out a controlled stop.

The definition of the very first initial command is made by giving the command:

@INITIAL-COMMAND <command and parameters>

The next initial commands are defined by repeating the command:

@NEXT-INITIAL-COMMAND <command and parameters>

Norsk Data ND-30.003.7 EN

Page 85¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

The parameter <command> must be specified on one line, and it shall NOT be preceded by a @ as when making mode jobs. It may be necessary to abbreviate the commands, if you must have many of them. The buffer they are stored in is limited to a total of 256 characters for all these commands together. If your software configuration is large, you may need to move more of what is normally associated with initial commands into mode files.

If you need to make any changes in the initial commands, you must rewrite the whole list. The @INITIAL-COMMAND clears the buffer, and there is no command to remove and insert a single command.

You can see what initial commands are defined by giving the command:

@LIST-INITIAL-COMMANDS ()

Example of Initial Commands¶

Command
@LIST-INITIAL-COMMANDS,
ENTER-DIRECTORY PACK-ONE DISC-45MB-1 0
BATCH 1
CONNECT-FILE SYSTEM-OUTPUT-1 105 W
CLOSE 105
APPEND-BATCH 1 LOAD-MODE:BATCH SYSTEM-OUTPUT-1

It would be normal to include these initial commands in most configurations, but the parameters in ENTER-DIRECTORY vary considerably from one configuration to another.

If the batch job is aborted due to commands that could not be accepted by SINTRAN, you can read SYSTEM-OUTPUT into an editor and take a look at what has happened.

Norsk Data ND-30.003.7 EN

Page 86¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Warn start missing initial commands¶

If you accidentally carry out a warm start without having any initial commands, you can log in as user SYSTEM and give them manually as shown in the following example.

Warn start missing initial commands¶

Step	Description
You have carried out the warm-start procedure, and logged in as SYSTEM.
ESC
ENTER SYSTEM
PASSWORD:
NO MAIN DIRECTORY OK	This error message indicates that no initial commands have been executed.
@ENTER-DIRECTORY	Enter the main directory.
DIRECTORY-NAME: PACK-ONE
DEVICE-NAME: DISC-45MB-1
DEVICE-UNIT: 0
@LOGOUT
ESC
ENTER SYSTEM	SINTRAN still thinks that no users are entered. Correct this by logging out and logging in again as user SYSTEM.
PASSWORD:
OK
@BATCH	Start the first batch processor, and run the batch job LOAD-MODE.
BATCH NUMBER = 1
@APPEND-BATCH 1 LOAD-MODE:BATCH SYS-OUTPUT-1	Correct the initial commands.

Norsk Data ND-30.003.7 EN

Page 87¶

User RT has space on a directory different from system directory¶

If user RT has a different default directory than the system directory, two initial commands must be added:

Changes to LOAD-MODE file
ENTER-DIRECTORY
....
ENTER-DIRECTORY
SET-DEFAULT-DIRECTORY
....
APPEND-BATCH 1 LOAD-MODE:BATC SYSTEM-OUTPUT-1

The command RTENTER must be included as one of the first commands in LOAD MODE. The reason is that user RT's default directory is set equal to the system directory when the initial commands are executed.

3.2.3 More about the LOAD-MODE file¶

The file LOAD-MODE must be tailored to suit each configuration. In configurations running many applications, many commands can be needed to start things, while smaller configurations require fewer. An example of such a file is given in appendix H.2.

It is, of course, possible to give the commands found in the LOAD-MODE file manually, but it is practical to make it start all applications that are used more or less daily.

The standard part of the LOAD-MODE file should do the following (see also appendix H.2):

Enter all directories not entered by the initial commands.
Define the entered directories as default.
Define the floppy disk drives in the directory table.
Set the system available for the users.
Inform the users that they can log in and start working.

Norsk Data ND-30.003.7 EN

Page 88¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Setting the system available is the last thing to do. It is normal to use the LOAD-MODE file to start the following:

Batch processors not started by the initial commands.
Spooling processes.
Communication, for example XMSG and COSMOS.
User Environment.
ND-500.

It is not necessary to give any commands to start the terminals. All files are closed after the warm start. RT-programs are passive - apart from any included by SYSTEM or started by commands in mode files.

Please note that you cannot use any arbitrary sequence when starting up the software. Some products require that others are already running before they can be started up. For example: starting COSMOS requires that XMSG is already running.

Some applications, such as COSMOS, need a lot of commands and information to start them. These applications are started with the help of separate mode files. All that needs to be in the LOAD-MODE file is then reduced to mode commands that start execution of the related mode files. Such mode files are delivered with the product from ND.

When making changes in the LOAD-MODE file or other important files needed for operating the system, it is good practice to:

Read and follow the installation description (PD sheets) or other information accompanying the product.
Write comments in the mode file about why the command(s) are there and what they are intended for!
Test that the commands have the desired effect. Give the commands manually the first time (avoid surprises later on), or test your changes as a separate mode job.
The first command in a batch job run from SYSTEM must be the ENTER SYSTEM () () (). When you change the password on user SYSTEM, remember also to change it in the LOAD-MODE file. The public file access for files containing batch jobs should be NONE to prevent other users from reading the password (data security).
Remember that a batch job must be terminated by the control character CTRL+ESC twice. In PED (or NOTIS-WP) you make this character by typing: CTRL+O followed by CTRL+ESC.

Norsk Data ND-30.003.7 EN

Page 89¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III

If you are editing a mode file or batch job in NOTIS-WP, make sure that you store the file in the 7-bits format. This is the ASCII character set. SINTRAN will not accept 16-bits or the newer standard (S) format produced by the NOTIS products. The actual format qualifier is written in left-hand corner of the status line on the screen in NOTIS-WP. PED handles only 7-bits format.

Commands in SINTRAN-SERVICE-PROGRAM and MAIL must be preceded by a @, instead of the * which is used by these programs as prompt when used interactively.

3.2.4 More about starting different processes¶

All processes that can be started more or less automatically in the warm start can also be started as separate processes. This section gives some short examples of how the most common processes are started (those that were stopped in section 3.1.1).

Batch processor¶

A batch processor is started, and made ready to receive batch jobs, by giving the command:

@BATCH [<batch number>]

If the parameter <batch number> is not given, the first passive batch processor is started.

Example of starting a batch processor
`@BATCH 2`
BATCH NUMBER = 2
This answer means that you succeed!

Norsk Data ND-30.003.7 EN

Page 90¶

Printers with Spooling¶

A printer with spooling is started by the command:

@START-SPOOLING <peripheral file name>

If there are already some files in the spooling queue that are not empty, the printer starts printing these. Users can now append files to the spooling queue.

Example of starting a printer
@START-SPOOLING LINE-PRINTER

XMSG¶

XMSG should be started before the applications using it. The procedure is:

Starting XMSG
@SINTRAN-SERVICE-PROGRAM
*START-XMSG
OK: XMSG started
*EXIT

If you are using a network with several computers, routing definitions have also to be done. See chapter 5.

Norsk Data ND-30.003.7 EN

Page 91¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III

User Environment¶

The UE is started by:

Starting UE
@UE-FUNC START-PROFILE-MANAGER

Before you give this command, you can decide which terminals UE shall control. The users on these terminals must then log in as UE users before they can do any work. The command for controlling this is:

@UE-AUTOMATIC-LOGIN <all terminals?> <enable=1/disable=0> [<terminal number>]

This can be useful if you or some of your users do not want to use UE.

Example of disabling UE on some terminals¶

Suppose that you want to disable UE on terminals 1 and 51.

@UE-AUTOMATIC-LOGIN
ALL TERMINALS ? N
ENABLE=1/DISABLE=0:0
TERMINAL NUMBER: 1

If you want to disable all terminals, type Y.

@UE-AUTOMATIC-LOGIN
ALL TERMINALS ? N
ENABLE=1/DISABLE=0:0
TERMINAL NUMBER: 51

Repeat the command for each terminal to disable or enable.

Norsk Data ND-30.003.7 EN

Page 92¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

RT-programs¶

The commands that start COSMOS in the LOAD-MODE file are described in chapter 5. RT-programs that you stopped (aborted) manually when stopping the installation, can be activated by the command:

@RT <RT-program name>

The legal RT-program names in your configuration are found by the command @LIST-RT-PROGRAMS. You cannot abbreviate the name of the RT-program in any of these commands, so exact match is required.

The only RT-programs that you normally need to start explicitly are those made by users. RT-programs belonging to any of your applications are in general started by separate service programs or by mode files included automatically in the warm start.

An alternatively way of starting UE¶

@LIST-RT-DESCRIPTION UEXPS
PASSIVE


The state of the RT-program is PASSIVE, so UE has not been started yet (UEXPS = UE Profile Server).

@RT UEXPS
@LIST-RT-DESCRIPTION UEXPS
IN TIME QUEUE, TIME LEFT:


The program has moved from PASSIVE state into a queue. That means it is started.

The example does exactly the same as the use of the UE-FUNC in the example showing start of UE.

Norsk Data ND-30.003.7 EN

Page 93¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

3.2.5 Starting the ND-500 CPU¶

The ND-500 CPU is normally started automatically during the warm start. This section explains the different ways of starting it manually.

The ND-500 CPU can be both stopped and started while the ND-100 (and SINTRAN) is running. But the ND-500 cannot run without the ND-100. This is because SINTRAN runs on the ND-100.

The operating system part of the ND-500 is called the ND-500 MONITOR. You use this for control of the ND-500. If you have read the previous sections, you have already seen this monitor used in both procedures and examples.

Normally, the start of ND-500 should be this simple:

Simple start of ND-500
@ND-500-MONITOR
ND-500 MONITOR Version H
%500: START-SWAPPER
Some system information is displayed.
%500: EXIT

If you do NOT intend to carry out ADVANCED OPERATIONS on the ND-500 CPU, you need not read the remainder of this section.

After the START-SWAPPER command is given, the ND-500 MONITOR carries out the necessary functions to start ND-500. This is done by using default values for important system parameters:

The ND-500 hardware is initialized. This has the same effect as Master Clear.

The ND-500 instruction set is loaded into the CPU. This is because the instructions themselves consist of software (the micro-programming principle). This software disappears when the power is turned off. The micro-program is supplied in different versions for different models of ND-500.

When started in this way, the micro-program is loaded from the file (SYSTEM)CONTROL-STORE:DATA. The ND-500 MONITOR expects this file name and contents.

Norsk Data ND-30.003.7 EN

Page 94¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

The ND-100 starts the micro-program in ND-500, and thereby enables the ND-500 CPU to run programs.

The swapper process is loaded into physical memory and started. The ND-500 MONITOR expects that the swapper process is on files placed under user SYSTEM with file names SWAPPER. The swapper is a vital part of the operating system that make it possible to run many programs timeshared.

The next example shows how you can control the loading of the micro-program version and starting the swapper.

You must now specify the default values of the parameters in the simple start procedure. The control store version you wish to load must be present on a data file.

Norsk Data ND-30.003.7 EN

Page 95¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Advanced start of ND-500¶

@ND-500-MONITOR¶

ND-500 MONITOR Version H

N500: MASTER-CLEAR¶

| Initialization of control store and registers. |

N500: LOAD-CONTROL-STORE (SYSTEM)CONTROL-STORE:DATA¶

| Here you load the standard micro-program, but the file name could be changed to the name of another version, or your own! |

N500: MICRO-START 0¶

| The micro-program starts running. The parameter is the start address in the control store. |

N500: LOAD-SWAPPER¶

File name: (SYSTEM)SWAP

| Load the swapper process into the physical Multiport memory. If you use a separate command to load, you can change the name of the swapping process file as well. |

N500: START-SWAPPER¶

| Start the swapper process. Process number is 0. |

N500: GIVE-N500-PAGES 1000B¶

| This gives ND-500 a swapping area corresponding to 1 MB. |

When the command LOAD-SWAPPER is used, there is no default memory allocation for ND-500 (no swapping area for user processes is reserved in ND-500). Some pages must therefore be given to the ND-500.

N500: EXIT¶

Norsk Data ND-30.003.7 EN

Page 96¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

When SINTRAN is started, the memory configuration in the system is defined. There are two different kinds of memory:

ND-100 local memory. This is for the exclusive use of ND-100 programs (including the ND-500 Monitor).

Shared Multiport memory. This memory is accessible for both ND-100 and ND-500 programs.

When the computer is warm-started, the memory configuration is initialized. This is usually done automatically by default values if the command DEFINE-MEMORY-CONFIGURATION is not given. The default values correspond to the physical memory configuration.

An example of defining the memory configuration manually:

@ND-500-MONITOR

ND-500 MONITOR Version H

N500: DEFINE-MEMORY-CONFIGURATION

N100 PAGE NO FOR PHYS. ADR. ZERO: 1000B

000001.MEMORY PART  
SIZE (IN 2K BYTES): 2000B  
ND-100 ACCESS: YES  
ND-500 PROGRAM ACCESS: YES  
ND-500 DATA ACCESS: YES  
LAST MEMORY PART DEFINED: YES

This configuration has 1 MB local memory, and 2 MB shared. 1 MB = 1000B pages. It is possible to define different memory parts with different access rights, but this is seldom done.

N500: START-SWAPPER

| | Start the ND-500 CPU. |

Norsk Data ND–30.003.7 EN

Page 97¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Memory Configuration¶

┌─────────────────────────────┐
│ Local ND-100   │ Shared Multiport memory    │
│ memory        │ (MPM)                       │
└─────────────────────────────┘

A: ND-100 page no. for ND-500 physical address zero
B: 1 memory part size

Figure 24. ND-500 physical memory configuration

If you have many ND-100 "user" processes, it is a good idea to extend the swapping area for use by the ND-100 CPU. This is done by taking some pages from the ND-500 CPU and giving them to the ND-100.

If for example you have only 1 MB of local ND-100 memory and several MBs in the Multiport you can give the ND-100 another half MB. You should be aware, though, that the access to Multiport memory is slower than for the local memory.

Example of giving the ND-100 extra swapping pages¶

┌──────────────────────────────────────────────┐
│ @ND-500-MONITOR                             │
│                                              │
│ ND-500 MONITOR Version H ........            │
│ N500: TAKE-N500-PAGES                        │
│ NUMBER OF PAGES: 400B             │ This corresponds to half a MB. │
│                                              │
│ NUMBER OF PAGES AVAILABLE FOR ND-500 PROCESSES: ........ 1088 │
│ NUMBER OF PAGES USED BY THE SWAPPER PROCESS: ........... 104 │
│ NUMBER OF PAGES USED FOR MAILBOXES AND DATA BUFFERS: ..... 60 │
│ NUMBER OF PAGES AVAILABLE FOR SWAPPING IN SINTRAN III: .... 483 │
│                                              │
│ These important parameters have been affected. GIVE-N500-PAGES │
│ command has the opposite effect. The physical configuration │
│ in this example is 3 MB shared and 1 MB local memory.       │
└──────────────────────────────────────────────┘

Norsk Data ND-30.003.7 EN

Page 98¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

ND-500 Actual Memory Configuration¶

| Local ND-100 memory | Shared Multiport memory |
|---------------------|------------------------|
| SIII memory         | proc. 0 GIVE           | TAKE |
| ND-100 swapping area| Swapping area shared between the CPUs |

Figure 25. ND-500 actual memory configuration

Note that the minimum local ND-100 swapping area is the one given by the local ND-100 memory.

The default memory allocation is as follows (N is total number of pages for swapping, local + shared memory):

Swapping areas	ND-100	ND-500
N < 2 MB	N/2 MB	N/2 MB
2 MB ≤ N < 4 MB	1 MB	N - 1 MB
4 MB ≤ N < 8 MB	1.5 MB	N - 1.5 MB
8 MB ≤ N	2 MB	N - 2 MB

Table 4. Values for default memory allocation

3.2.6 Starting the ND-500 Multi-CPU (ND-580/CX)¶

The ND-500 Multi-CPU configuration runs from two to four ND-570 CPUs under SINTRAN VSX-500 version K. The ND-570 CPUs support the need of scientific and technical users for more computing power than is available in a single ND-570 CPU system. The Multi-CPU configurations use a special swapper and micro program version.

Norsk Data ND-30.003.7 EN

Page 99¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Overview of the ND-500 Multi-CPU configuration¶

The operating software in the ND-500 Multi-CPU configuration is shown in the diagram below.

ND-500 MONITOR
      |
ND-210697       SWAPPER PROCESS       SWAP FILE(S)
"MULTISWAPPER"      .......       .......
      |                     |
      |                     |
ND-500 CPU no 1        ND-500 CPU no 4
MICRO PROGRAM IN       MICRO PROGRAM IN
CONTROL STORE 1        CONTROL STORE 4

                    ND-210701
                    "ND-500/2 CX
                     MULTI CPU
                     MICRO-PROGRAM"

Figure 26. Overview of the ND-500 Multi-CPU

The operating software outlined in the diagram above performs these main functions:

The ND-500 Monitor and swapper process is common to all parts of the configuration.
The swapper process handles the administration of the physical, shared MPM-5 memory between the CPUs. There is no change in the use of the swap file(s).
Each ND-570 CPU has its own control store.

Norsk Data ND-30.003.7 EN

Page 100¶

Installation¶

Run the additional Multi-CPU patch-file after SINTRAN has been loaded from floppy. IT MUST BE RUN AFTER THE STANDARD PATCH FILE, BUT BEFORE ANY COLD START!
```
@MODE (ND:SYSTEM)START-MULTIPATCH:MODE.,. (separate floppy)
```
Copy the new software onto the system disk.

The floppy ND-210697 contains the swapper files:
```
MULTISWAPPER-xx:PSEG and MULTISWAPPER-xx:DSEG
```
The floppy ND-210701 contains the file CONT-STORE-151xx

xx means version and revision level.
Make the ND-500 MONITOR use the correct versions of the swapper and the control store files.

There are several ways of doing this, but the two most common ways are here described as alternatives A and B.

### Alternative A:

In many single ND-500 CPU configurations, the starting of the ND-500 is done as follows (or in a similar way) when making a warm start:
```
@ND-500-MONITOR
ND-500 MONITOR
N500: START-SWAPPER
```
```
Loading of control store and swapper by default values.
```
```
N500: EXIT
```
The default values in alternative A are:
- CONTROL-STORE:DATA
- SWAPPER:PSEG
- SWAPPER:DSEG
You transfer the new software by copying to these default files.

Norsk Data ND-30.003.7 EN

Page 101¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

@COPY-FILE SWAPPER:PSEG,MULTISWAPPER:PSEG

@COPY-FILE SWAPPER:DSEG,MULTISWAPPER:DSEG

@COPY-FILE CONTROL-STORE:DATA,CONT-STORE-151:DATA

Alternative B:¶

If you are an advanced user, running different instruction sets, you are accustomed to giving commands to load the control store. Therefore, as an advanced user you only need to make the ND-500 use the default swapper process. Do the copying:

@COPY-FILE SWAPPER:PSEG,MULTISWAPPER:PSEG

@COPY-FILE SWAPPER:DSEG,MULTISWAPPER:DSEG

4. Make a controlled stop of the ND-500 CPUs (stop all active ND-500 processes).¶

5. Update the LOAD-MODE file.¶

The old procedure for starting one ND-500 CPU is here replaced with a new procedure for starting several ND-500 CPUs.

If you used alternative A in step 3, make these changes in the LOAD-MODE file:

@CC START THE ND-500 MULTI-CPU CONFIGURATION
@CC
@CC START THE ND-500 CPU NO 1 AND SWAPPER BY DEFAULTS
@CC
@ND-500-MONITOR 1
START-SWAPPER
EXIT

@CC REPEAT THE FOLLOWING FOR EACH ADDITIONAL ND-500 CPU

@CC
@ND-500-MONITOR 2    | The logical ND-500 CPU number.
MASTER-CLEAR
LOAD-CONTROL-STORE,...
MICRO-START 0
EXIT

Norsk Data ND-30.003.7 EN

Page 102¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

You add the logical ND-500 CPU number when entering the ND-500-MONITOR to select a specific ND-500 CPU on which to operate. Two ND-500 CPUs were started in the previous example.

If you, as an advanced user, selected alternative B in step 3, then your LOAD-MODE should be made similar to the following:

@CC START THE ND-500 MULTI-CPU CONFIGURATION
@CC
@CC START THE ND-500 CPU NO 1 AND SWAPPER
@CC
@CC
@ND-500-MONITOR 1
MASTER-CLEAR
LOAD-CONTROL-STORE (SYSTEM)CONT-STORE-151:DATA,...
MICRO-START 0
START-SWAPPER
EXIT

@CC REPEAT THE FOLLOWING FOR EACH ADDITIONAL ND-500 CPU
@CC
@CC
@CC
@ND-500-MONITOR 2 [The logical ND-500 CPU number.]
@CC
MASTER-CLEAR
LOAD-CONTROL-STORE (SYSTEM)CONT-STORE-151:DATA
MICRO-START 0
EXIT

6. Do a warm start.¶

After the warm start has been completed, all your ND-500 CPUs should be ready to run programs. The swapper process is common to all ND-500 CPUs, and runs on the ND-500 CPU that it is serving at any given time. Thus, the load of the swapper is shared equally between the ND-500 CPUs.

If you suspect that the loaded micro program may not be the correct one, you can use the following procedure to verify the version:

@ND-500-MONITOR 1
N500: VERSION

| SUBSYSTEM PART: | <date of generation> |
| SYSTEM PART:    | <revision status>    |
| SWAPPER:        | <date of generation> |
| MICRO PROGRAM:  | 151xx [Micro program version.] |

Norsk Data ND-30.003.7 EN

Page 103¶

Running processes on the ND-500 Multi-CPUs¶

A user does not need to know which physical ND-500 CPU his/her application is running on. Applications are therefore started in just the same way as before. This also applies to standard domains.

Example of running PED-500¶


@ND-500-MONITOR
ND-500-MONITOR
N500: PED-500

A process is started on the ND-500 CPU that has the fewest processes in the execution queue. Assignment of the CPU that a process shall run on is done by the time slicer each time it is active. Thus, the ND-500 CPUs will automatically share the total workload. A process not being time-sliced will continue to run on the CPU where it was started.

You may also force any process always to run on the same ND-500 CPU. You do this by specifying the logical CPU number when entering the ND-500 Monitor.

Example of running PED-500 on CPU no. 3¶


@ND-500-MONITOR 3	The logical ND-500 CPU number.
ND-500-MONITOR
N500: PED-500

Norsk Data ND-30.003.7 EN

Page 104¶

3.3 Cold start¶

A cold start must be carried out after a reconfiguration of the system, i.e. after running the configuration program (section 3.5).

A cold start is also useful to clear up error situations where a warm start is not sufficient. Such error situations occur when the segment file(s) has become erroneous (SEGFILE:DATA).

The main tasks of the cold start are to load a new copy of SINTRAN from save-area and to rebuild the segment file(s) with a fresh copy of code and data.

3.3.1 Cold start with SINTRAN running¶

If SINTRAN is running, you can carry out the cold start as follows:

Stop all activity in the system (see section 3.1).

Give the command @COLD-START [<terminal number>] unabbreviated from user SYSTEM. The optional parameter is the terminal to be used for the rest of the cold start procedure. Default is the console.

Log in as user SYSTEM when SINTRAN starts.

Enter the system directory containing SINTRAN (usually the main directory).

Log out and in again as user SYSTEM.

Run the file HENT-MODE as a mode job. This file is very configuration-dependent.

Carry out a warm start (see section 3.2.)

Update the software clock if necessary (@UPDAT or @CLADJ).

The next page gives an example of such a cold start.

During the cold start the following things happen (see also figure 23):

SINTRAN save-area is copied to the SINTRAN image-area. The system-included segments on the files SINTRAN:DATA and MACM-area are copied to SEGFILE:DATA (among other things, this includes the RT-Loader, spooling RT-programs, SINTRAN Service program, MAIL, XMSG and ND-500 System Monitor).

Norsk Data ND-30.003.7 EN

Page 105¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

SINTRAN image-area is copied to the SINTRAN memory area and SINTRAN starts itself. This is quite similar to a warm start.
You must run the HENT-MODE file because a lot of information is still missing and the segment file(s) must be rebuilt. Some of the commands in this mode file are system dependent, while others are always present.

Example of cold start with SINTRAN running¶

Stop all activity.	Wait a minute or two.

@COLD-START

| NUMBER OF PAGES THE SYSTEM WILL USE ON THE SEGMENT FILE(S): | 15070B | | FIRST SYSTEM SEGMENT STARTS ON PAGE: | 2765B | | NUMBER OF BACKGROUND PROCESSES | 39 | | EACH BACKGROUND PROCESS NEEDS <pages>: | 205B |

The displayed information is useful for calculating the size of the segment file(s).

09.13.44    17. MAY 1986
SINTRAN III - VSX/500 K REVISION 0B
CPU (SYSTEM NUMBER): 6586
GENERATED: 16.39.00   15 MAY 1986

SINTRAN III RUNNING -

PAGES FOR SWAPPING: 14033B

This is the amount of swapping pages shared between the ND-100 and ND-500 CPUs.

ESC	Ordinary logging in.
ENTER ⏎ PASSWORD: ⏎	Just give CR when SINTRAN asks for user name and password. This error message is correct in this case. No mass storage units are entered at the moment.

@ENTER-DIRECTORY

| DIRECTORY-NAME: PACK-ONE | Enter the main directory. The different parameters must be in accordance with your disk configuration. | | DEVICE-UNIT: 0 | |

Norsk Data ND-30.003.7 EN

Page 106¶

SINTRAN III System Supervisor¶

Stopping, Starting and Loading SINTRAN III¶

Example Continued¶

@LOGOUT - ESC: SINTRAN still thinks that no users are entered. Log in again.

ENTER SYSTEM
PASSWORD: _

OK

@MODE HENT-MODE:MODE,... - Run the HENT-MODE file to rebuild the segment file(s) and initialize some parts of SINTRAN.

@UPDAT 58 16 30 6 1986 - Format Min Hour, Day Month Year.

The HENT-MODE should end by appending LOAD-MODE to a batch processor.

Automatic Cold Start Procedure¶

There is also an automatic way of making a cold start if SINTRAN is running. It is based on letting SINTRAN enter the main directory and then starting the HENT-MODE job after SINTRAN is loaded.

Stop the activity in the system, but do NOT stop SINTRAN (see section 3.1).

Use the command *SET-COLDSTART-MODE-FILE in the Sintran Service PROGRAM to specify that the HENT-MODE file shall be run automatically in the cold start.

Give the command COLD-START unabbreviated from user SYSTEM.

Be careful when specifying the parameters in the command *SET-COLDSTART-MODE-FILE. They are not checked for legality before the cold start is performed. The definition survives both warm and cold starts. If you want to do an ordinary manual cold start after the mode file has been specified, use the command *RESET-COLDSTART-MODE-FILE.

Norsk Data ND-30.003.7 EN

Page 107¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Example of cold start with automatic run of HENT-MODE¶

Stop all activity.

@SINTRAN-SERVICE-PROGRAM

*SET-COLDSTART-MODE-FILE
PARAMETERS TO THE ENTER-DIRECTORY COMMAND
WHEN ENTERING THE MAIN DIRECTORY: PACK-ONE,DISC-70MB-1,0
COLDSTART INPUT FILE: HENT-MODE:MODE
COLDSTART OUTPUT FILE: TERMINAL
*EXIT
@COLD-START 1

The cold start is now performed from the console terminal's background program. The output is displayed on this terminal due to the specification of the cold start output file.


ⓔ	The mode job is finished. LOAD-MODE should be running on a batch processor.

CAUTION! Do NOT press the ESC button on the console terminal before the cold start is finished! Otherwise you abort the HENT-MODE job!

Cold start with SINTRAN NOT running¶

If SINTRAN is not running, you must use the SINTRAN floppy diskette containing MACM to load SINTRAN.

Norsk Data ND-30.003.7 EN

Page 108¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Example of Cold Start with SINTRAN Not Running¶

Suppose you have a COMPACT computer with a 45MB internal disk.

Insert the SINTRAN floppy diskette 1 in the floppy drive, unit 0.

#1560&
MACM is loaded from floppy into memory.

MACM-1718-0
APR 25, 1986

GIVE DISK TYPE AS ONE OF THE FOLLOWING NUMBERS:¶

Number	Disk Type
0	DISC-14MB
1	DISC-21MB
7	DISC-45MB
20	DISC-450MB

See your SINTRAN order form to find your disk type. In this example it is 7.

DISC TYPE: 7!

TYPE ANY MACM COMMAND:

)HENTJ
Fetch SINTRAN from save-area.

22!
Start SINTRAN.

SINTRAN III Running¶

Log in using "CR" for user name and password.

NO MAIN DIRECTORY
OK

@ENTER-DIRECTORY PACK-ONEJ
DEVICE-NAME: DISC-45MB-1J
DEVICE-UNIT: 0J

You must enter the main directory.

Log out and in again as user SYSTEM. Use password this time.

@MODE HENT-MODE:MODE,,,J

Run HENT-MODE file to rebuild the segment file(s) etc.

Norsk Data ND-30.003.7 EN

Page 109¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III

3.3.2 More about the HENT-MODE file¶

The HENT-MODE must also be tailored separately for each configuration. An example of such a file is given in appendix H.3.

The standard part of the HENT-MODE file should do the following:

Define the initial commands because these are cleared during the cold start.
Enter all directories required to perform the cold start and set them default. These are the directories containing files referred to by different mode files run via HENT-MODE.
Define SEGFIL0 as the first segment file in SINTRAN Service program.
Execute the command @INITIALIZE-BACKGROUND-PROGRAMS
Execute the command @RTENTER to allow RT-programs access files. User RT is associated with the owner of RT-programs.
Load DMAC to segment 7. DMAC is used for patching of segments.
Initialize the ND-500 CPU if it is included in the configuration.

The following configuration-dependent operations are normally carried out by the HENT-MODE file:

Initialize the SINTRAN mail system.
Empty spooling files.
Load configuration-dependent software which make use of segments (XMSG, COSMOS, UE and so on).
Install reentrant ND-100 programs.
Initialize the ND-500 configuration and define standard domains.

Some of the tasks mentioned are usually performed by separate mode files. Having separate mode files for dedicated tasks improves the structure of the mode files. See appendix H.3 to H.6 for an example of all mode file necessary to perform a cold start. See your PD sheets for instructions about what to put into the mode files.

Norsk Data ND-30.003.7 EN

Page 110¶

3.3.3 Maintaining the Segment Files (ADVANCED)¶

If you load a new version of SINTRAN that requires more space, you can risk the segment file not having sufficient extra space to contain the new version. The space required for SINTRAN is printed out on the error device in the cold start. The PD sheet for each product specifies how much space it needs on the segment file. In this case, SINTRAN gives the error message "NOT ENOUGH SPACE ON THE SEGMENT FILE(S)" during the cold start. There are two main solutions to this problem:

A: Expand the existing segment file.
B: Create a new, additional segment file.

The cold-start procedure must be repeated after this problem has been solved.

A: Example of Expanding SEGFILE0:DATA¶

@EXPAND-FILE SEGFILE0:DATA
NUMBER OF PAGES: 500

The number 500 was chosen arbitrarily (trial and error method). If the error message "SPACE ALREADY ALLOCATED" appears, it is impossible to expand the segment file. Use the other solution.

Example Continued¶

Delete and redefine the segment file in SINTRAN Service Program.

@SINTRAN-SERVICE-PROGRAM
*DELETE-SEGMENT-FILE Y Y
SEGMENT FILE NUMBER (OCT): 0

*DEFINE-SEGMENT-FILE Y Y
SEGMENT FILE NUMBER (OCT): 0

Page 111¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

If it is impossible to expand the segment file, create a new segment file.

Example of defining a new segment file¶

@CREATE-FILE SEGFIL1:DATA
NUMBER OF PAGES: 500

The segment files should by convention be named SEGFILx, where x is in the range 0 - 3. The segment file can be placed on any directory, although it is normal to place it on the main directory. If it is not placed on the main directory, you must include an additional command in the beginning of the HENT-MODE file to enter this directory.

Example continued¶

@SINTRAN-SERVICE-PROGRAM
*DEFINE-SEGMENT-FILE Y Y
SEGMENT FILE NUMBER (OCT): 1
SEGMENT FILE NAME: SEGFIL1:DATA

You will now have two segment files (SEGFIL0 and SEGFIL1).

You are also advised to include this command in the HENT-MODE file, although it is only really needed after loading SINTRAN from a diskette. SEGFIL0 is automatically defined by SINTRAN.

The command SET-SEGMENT-FILE must be given in the RT-Loader to ensure loading on the desired file. The definition becomes permanent, as the RT-Loader saves it on the RTFIL. Your HENT-MODE should be modified as shown in the following example:

Modifying HENT-MODE to load onto two segment files¶

@CC ALL DIRECTORIES ARE NOW ENTERED AND SET DEFAULT

@RT-LOADER
@SET-SEGMENT-FILE 0
....
@RT-LOADER
@SET-SEGMENT-FILE 1

Load onto SEGFIL0 until it becomes full. Then switch to SEGFIL1.

Norsk Data ND-30.003.7 EN

Page 112¶

Sintran III System Supervisor¶

Stopping, Starting and Loading Sintran III¶

Note: If you already have four segment files that are not possible to expand, the files on the disk must be reorganized.

3.3.4 Initializing Background Programs¶

Each terminal, batch processor and TAD is controlled by a background process. The background programs are system-included RT-programs. The command

@INITIALIZE-BACKGROUND-PROGRAMS

allocates space on the segment file for the background programs. The command must be executed before terminals, batch processors and TADs can be used. The only exception is the console terminal which always has a background program present.

Each background program consists of a data segment and a system segment. The system segment is usually 5K words big. It keeps user-dependent information for each SINTRAN user (e.g. open-file table and local variables for program routines). The SINTRAN-SERVICE command

INITIALIZE-SYSTEM-SEGMENT <segment name/number>

copies a new system segment from the SINTRAN save-area onto an existing system segment. This can be useful for clearing up a system segment without performing a cold start.

The data segment is by default 128K words big, but this can be changed if necessary. This is done by the command

@CHANGE-BACKGROUND-SEGMENT-SIZE <segment name/number>

During execution of a background program (ordinary program), the data segment contains a copy of the user's program. Only a very small part of the program is at any time present in physical memory. The size of the data segment determines the size of programs that can be run on a background process. 128K words corresponds to a 2-bank program, and 64K words to a 1-bank program (a bank corresponds to the logical address range of the ND-100 CPU). You should only change the size of the background segment size from 2-bank to 1-bank if you have special reasons for saving space on the segment file. ND software applications consist today of a mixture of 1-bank and 2-bank programs.

Norsk Data ND-30.003.7 EN

Page 113¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

The following procedure is used to find the segments of an active background process belonging to a particular terminal:

Finding the segments used by a terminal¶

@LIST-DEVICE 51.0	Get the terminal number by giving the @WHO command. BAK03 has reserved this terminal.
RESERVED BY: BAK03

@LIST-RT-DESCRIPTION BAK03
BACKGROUND PROGRAM
ACTIVE I/O WAIT

SEGMENTS 1 AND 2	REENT	NPIT	APIT	RING	PRIORITY
INITIAL	3B	1374B	11B	7B	2
ACTUAL	1375B	1374B	5B	7B	2

The initial segments for the background process are the segments used by the background process when it is activated. Segment 1 is the terminal's data segment when an ND-100 program is run, and segment 2 is always the system segment. When a SINTRAN command is given, the data segment is exchanged with segment number 3, the SINTRAN command segment. If the file system is called from the background program, the data segment is exchanged with segment number 6; the SINTRAN file system segment.

Example continued¶

@RT-LOADER	The RT-Loader can be used for checking that you have found the correct segments.

REAL TIME LOADER, SINTRAN III VSX - K

*WRITE-SEGMENT 1374,,

| SEG. NO. | SEG. NAME | LOWER ADDR. | UPPER ADDR. |  |
|----------|-----------|-------------|-------------|--|
| 1374     | 130000    | 141777      |             | This address range corresponds to 5 pages. It is the system segment. |

*WRITE-SEGMENT 1375,,

| SEG. NO. | SEG. NAME | LOWER ADDR. | UPPER ADDR. |  |
|----------|-----------|-------------|-------------|--|
| 1375     | 000000    | 377777      |             | This address range corresponds to 128 pages. It is the data segment. |

Norsk Data ND-30.003.7 EN

Page 114¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

If the SINTRAN feature Background Allocation is used in your configuration, there is no fixed connection between a background program and a terminal. Background allocation means that the first free background program is allocated for the user at the time of logging in. When logging out, the background program is released. You must therefore change the background segment size for all background programs if you have decided to change the size for a particular terminal.

3.3.5 Initializing the MAIL system¶

The SINTRAN mail system is initialized by the command:

*INITIALIZE <max. no of messages>

The parameter is the maximum number of unread messages that can be stored in the mailbox file. When the INITIALIZE command is given, all existing messages are lost. A maximum of 10 or 20 messages should in most cases be sufficient.

After the INITIALIZE command is given, the MAIL system is started by the command

*RUN-MAIL-SYSTEM*

The file (SYSTEM)MAILBOX:DATA contains the unread messages. It should not be inspected by the editors PED or NOTIS-WP but only by the commands in the MAIL system.

3.3.6 Reentrant subsystems¶

Reentrant subsystems are normal programs (file types :PROG or :BPUN) that are loaded "permanently" onto the segment file.

If an ordinary ND-100 program is started, the file containing the program is copied onto the background data segment of the terminal demanding the program. If another user starts the same program, s/he also gets a new copy of the same program. The result is more than one copy of the same program on the segment file.

The advantage of a reentrant subsystem is the fact that it is always present on a segment. No copying onto the background program is needed before starting it. It is therefore started rapidly.

Norsk Data ND-30.003.7 EN

Page 115¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

The reentrant segment is not owned by a particular user but is a common resource for everybody. All users share the program code of the reentrant subsystem. Thus, reentrant subsystems save pages in memory when more than one user runs the program at the same time. You are therefore strongly advised to make reentrant subsystems of the programs that are frequently used by many users simultaneously. The maximum number of reentrant subsystems in a system is 75.

The following command establishes an ordinary ND-100 program (file type :PROG) as a reentrant subsystem:

@DUMP-PROGRAM-REENTRANT <name> <file name> [<segment name/number>]

The name is used later on to identify the reentrant subsystem. A reentrant subsystem is started by simply giving this name or an unambiguous abbreviation of it to SINTRAN. If the name is also a legal abbreviation of a command name, it must be started by the command @RECOVER.

After an arbitrary text string is given to SINTRAN, the search strategy is:

command table
reentrant subsystem table
files with file type :PROG on the user's default directory
files with file type :PROG on user SYSTEM's default directory

If the text string contains user name specifications in parentheses, the search is limited to this user's files with file type :PROG.

User SYSTEM must have read access to the file at the moment it is dumped. The program is dumped onto the first unused segment on the segment file. The RT-Loader is activated after the command is given to SINTRAN.

Making a reentrant subsystem out of an ordinary program¶

Command	Description
`@DUMP-PROGRAM-REENTRANT PLANC,(UTILITY)PLANC-100::PROG`
`@PLANC`	The simplest way of starting the subsystem.
- ND-100 PLANC COMPILER	...
`@RECOVER PLANC`	Another way to start the subsystem.
- ND-100 PLANC COMPILER	...

Norsk Data ND-30.003.7 EN

Page 116¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

If the program to be dumped is in BPUN format (file type :BPUN - Binary PUNched), another command must be used to make a reentrant subsystem out of it:

@DUMP-REENTRANT <name> (<start address>) (<restart address>) 
<file name> [<segment name/number>]

You should find the start and restart addresses documented on the PD sheets delivered with the ND software products. If the command @CONTINUE is used, the subsystem is executed from the restart address. See also appendix H.4 for a relevant example.

Making a reentrant subsystem out of a program in BPUN format¶

@DUMP-REENTRANT ASSEMBLER,,(BPUN-FILES)ASSEMBLER-500:BPUN

| The user BPUN-FILES is usually created in all systems to keep the files in BPUN format. |

@ASSEMBLER
ND-500 ASSEMBLER ...

The following command removes a reentrant subsystem from the reentrant subsystem table and clears the reentrant segment on the segment file:

@DELETE-REENTRANT <name>

Deleting a reentrant subsystem¶

@DELETE-REENTRANT ASSEMBLER

| Deleting the subsystem. |

@ASSEMBLER
"ASSEMBLER"
NO SUCH FILE NAME

| It is no longer available. |

Norsk Data ND-30.003.7 EN

Page 117¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Some of the application programs developed by ND (e.g. COSMOS) make use of another SINTRAN feature:

@DEFINE-REENTRANT-PROGRAM `<name>` `<start address>` `<segment name/number>` `<restart address>`¶

When the command is given, the reentrant subsystem must already have been loaded onto a segment by the RT-Loader. This is an alternative way of making a reentrant subsystem. This command can be used to define more than one subsystem (with different entry points) at the same segment.

Example of how COSMOS uses the @DEFINE-REENTRANT-PROGRAM¶

Command
@DUMP-PROGRAM-REENTRANT CONNECT-TO (UTILITY)COS-CONN-TO:PROG CCT
@DEFINE-REENTRANT-PROGRAM LIST-SYSTEMS 2 3 CCT

The segment called CCT is defined and loaded by the RT-Loader by the first command. The second command defines the name "LIST-SYSTEMS" as an alias for the same segment. Owing to the different start addresses for the two reentrant systems, the subsystem LIST-SYSTEMS is only a command within the CONNECT-TO program.

The command

@LIST-REENTRANT `<subsystem name>`¶

is used for listing available subsystems. This command is available for all users.

3.3.7 The ND500-HENT file¶

The ND500-HENT mode file is normally included from the HENT-MODE file. An example of such a file is given in appendix H.5. These standard tasks are performed by the mode file:

Define the ND-500 Monitor as a reentrant subsystem.
Defining standard domains. The number of standard domains to be defined and which to select depends on the configuration.
Defining swap file(s).

Norsk Data ND-30.003.7 EN

Page 118¶

3.3.8 Ordinary domains and standard domains¶

An executable program on ND-500 is called a domain. A domain is made up of logical segments. These segments are placed on files under the users who have created them. An ordinary ND-500 program can only be started via the ND-500 Monitor.

Example of starting an ordinary domain¶

@ND-500-MONITOR

This is how to start the ND-500 Monitor after it has been defined as a reentrant subsystem.

N500: LIST-DOMAIN

DOMAIN NAME: (DOMAINS)

Domain no.	Domain Name
0	SCRATCH-DOMAIN
1	LINKAGE-LOADER
2	PED-500-EN
3	FORTRAN-500

The domains available under DOMAINS.

N500: (DOMAINS)PED

Starting a domain that belongs to DOMAINS.

@ND-500-MONITOR (DOMAINS)PED

This is an alternative way of starting the same domain from SINTRAN mode. The ND-500 Monitor becomes more or less invisible, and you return to SINTRAN after program execution. This can often be abbreviated to @END <domain name>.

It is possible to define ordinary domains as standard domains. A standard domain is a domain that is known to SINTRAN. This means you do not need to enter the ND-500 Monitor to start such a domain. The names of the standard domains are placed in the reentrant subsystem table. The start-up time for a standard domain is about the same as for an ordinary domain for the first user who starts it. The second user who starts the same domain saves some initialization time. The number of standard domains is limited to 64.

Norsk Data ND-30.003.7 EN

Page 119¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Example of defining a standard domain¶

@ND-500-MONITOR

N500: DEFINE-STANDARD-DOMAIN

STANDARD DOMAIN NAME: MY-PED

DOMAIN NAME: (DOMAINS)PED-500

N500: EXIT

The name becomes an alias for PED-500.

User name and domain name for the owner of the domain.

@LIST-REENTRANT

START RESTART SEGMENT NAME

0B 0B 114B PERFORM

ND-500 STANDARD DOMAIN: MY-PED

Both reentrant ND-100 programs and ND-500 standard domains are listed.

@MY-PED

The program is now started directly from SINTRAN.

The ND-500 Monitor command LIST-STANDARD-DOMAINS can also be used to find the standard domains. In addition, it gives information about related file names referred to by the domain.

The command DELETE-STANDARD-DOMAIN <domain name> removes the definitions of a standard domain. The SINTRAN command @DELETE-REENTRANT cannot be used because it is necessary to delete more than the domain from the reentrant subsystem table.

Ordinary end-users do not often need know about the ND-500 Monitor at all. If they use only a small number of ND-500 programs these can be defined as standard domains.

The user DOMAINS is normally present in an ND-500 configuration to keep the ND-supported application programs for ND-500. See appendix H.6 for an example of a mode file used for defining the standard domains in a cold start.

The standard-domain feature also makes it easier to control which domains public users are allowed to run. If public users are not allowed to enter the ND-500 MONITOR, they are only able to run standard domains. In the SINTRAN Service program, it is possible to set the command protection both for commands and programs defined in the reentrant subsystem table.

Norsk Data ND-30.003.7 EN

Page 120¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

How to make the ND-500 Monitor inaccessible for public use¶

@SINTRAN-SERVICE-PROGRAM

*SET-COMMAND-PROTECTION  
COMMAND: ND-500-MONITOR  
PROTECTION (SYSTEM, RT OR PUBLIC): RT  
MEMORY? Y  
SAVE-AREA? Y  

This definition survives a cold start.  
*EXIT

The reentrant subsystem ND-500 Monitor is now only accessible from user RT and SYSTEM. The error message "PROTECTED COMMAND" is the result if any public user tries to run the domain.

When deleting ND-500 domains or copying them to another user, they must be handled somewhat differently from ND-100 programs. To help you to understand why this is, a short explanation of domains follows.

A domain can consist of up to 32 program segments and 32 data segments. Each program or data segment is stored on a separate file of file type :PSEG or :DSEG, respectively.

A program segment consists of pure code (machine executable instructions) and a data segment of data and variables.

Information about how these segments are linked together is stored on the file with name <domain name>:LINK. There is one file for each domain.

The information about where the different files associated with a domain are stored, is found in the DESCRIPTION-FILE:DESC. There is one such file for each user owning domains. All domains owned by the user are described in this file. Figure 27 gives an overview of the files that a domain consists of.

Norsk Data ND-30.003.7 EN

Page 121¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Domain information : MY-DOMAIN¶

(a part of the description file)

Link information : MY-DOMAIN:LINK¶

File type	Program segment	Data segment	File type
:PSEG	Program segment x	Data segment x	:DSEG
	Program segment y	Data segment y
	Program segment z	Data segment z

Figure 27. How a domain is organized on files

Standard domains have the same type of information as found in the description file stored on a system-included segment on SEGFILE0 (segment number 20B).

A domain's files should never be deleted by the SINTRAN command @DELETE-FILE. If one of these files is deleted, it is no longer possible to run the domain, and it has to be reloaded. Instead, the Linkage-Loader is used for loading and maintaining ND-500 programs. When a domain is deleted or moved to another user, the DESCRIPTION-FILE:DESC has to be updated. This is why dedicated commands in the Linkage-Loader should be used for deleting and copying domains. If the DESCRIPTION-FILE for a user is deleted, none of the user's domains can be run.

Norsk Data ND-30.003.7 EN

Page 122¶

How to delete a domain¶

Command	Description
N500: LINKAGE-LOADER	ND-Linkage-Loader
N11: LIST-DOMAIN
Domain no. 0	SCRATCH-DOMAIN
Domain no. 1	MY-OLD-PROGRAM
N11: DELETE-DOMAIN	The domain's files are deleted and the description file updated.
Domain-name: MY-OLD-DOMAIN

How to copy a domain from user A to user B¶

This procedure should be used if the user receiving the copy already has a DESCRIPTION-FILE:DESC. It is good practice to log in as the user receiving the domain. This user must have read-access to all domain files to be copied.

Command	Description
@END LINKAGE-LOADER
N11: COPY-DOMAIN
Source domain: (A)TEST-DOMAIN	The domain is created by appending double quotes to the domain name.
Destination domain: "TEST-DOMAIN"

If you are copying domains between computers, e.g. new applications from a floppy diskette, you should copy to a user with no domains.

How domains can be copied to a user without domains¶

Command	Description
N500: LIST-DOMAINS	Use this command to find a user with no domains.
N500: EXIT

Copy the files by @COPY-FILE, BACKUP-SYSTEM or the COSMOS program TRANSFER-FILE. Copy all the domain files and the description file. The description file still contains the definitions valid for the user the domain is copied from. This must be corrected.

Norsk Data ND-30.003.7 EN

Page 123¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Example continued¶

@ND_LINKAGE-LOADER

N1: RENAME-DEFAULT-DIRECTORY-AND-USER
(New-directory;new-user): (PACK-ONE:B)

Give the directory name and user name in full. The parentheses must not be omitted.

Now, the command N500: COPY-DOMAIN should be used for copying to the user who is to own the domain, i.e. DOMAINS.

3.3.9 ND-500 Swap files (ADVANCED)¶

When ND-500 domains are executed, they need, like the ND-100 programs, room on a disk to which they can be swapped. The disk-swapping files should conventionally be called SWAP-FILE-0:SWAP ... SWAP-FILE-3:SWAP. This makes it possible to have 4 swapping files. The files must occupy contiguous areas on the disk (similar to ND-100 segment files). They can belong to any user on any directory, but user SYSTEM must have read and write access to these files. This means they need not be placed on the system disk.

It is difficult to estimate how many pages the swapping files should have. This always depends on the number of users simultaneously using the ND-500 and on the amount of space used by the domains they run. You must also consider how much disk space you can afford, taking the disk size into account. It is normal to use between 5000 and 10000 disk pages for swapping in a medium-sized ND-500 system with about 20 to 30 simultaneous users. This corresponds to approximately 10-20 MB swapping-pages.

Norsk Data ND-30.003.7 EN

Page 124¶

How to create a ND-500 swapping file¶

@CREATE-FILE SWAP-FILE-1:SWAP
NUMBER OF PAGES: 2000

This is the second swapping file. The first exists already. This file becomes contiguous.

@ND-500-MONITOR
N500: DEFINE-SWAP-FILE
File name: SWAP-FILE-1
N500: LIST-SWAP-FILE-INFO
Swap file number: 1

To ensure yourself that everything is correct.


SWAP-FILE-NUMBER:	1
SWAP-FILE-NAME:	(PACK-ONE:SYSTEM)SWAP-FILE-1:SWAP
SIZE IN PAGES:	2000

The ND-500 must be restarted to make the swapper use the new swapping file. Never delete a swapping file that is currently being used by ND-500.

Only a small part of an ND-500 segment using its total address range can be placed in physical memory at any time. The addressing range for a segment is 27 bits, which corresponds to 64K pages (more than 130 MB!). In addition, a domain can refer up to 32 program segments and 32 data segments altogether.

The ND-500 CPU has its own swapper process, which always runs as process 0 under the ND-500 Monitor. Its pages are resident in memory. They are never swapped out! When the computer is warm-started, the swapper process is copied from the files (SYSTEM)SWAPPER:PSEG and (SYSTEM)SWAPPER:DSEG to physical memory.

The swapping strategy of the ND-500 is different from the one SINTRAN uses. The hardware architecture guarantees that the program and data is always separated on different segments, and the main swapping strategy is determined at load time.

Norsk Data ND-30.003.7 EN

Page 125¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

 ------------------------------- 
|            DISK FILES:        |
|                               |     
|         ____________          |
|        | SWAP-FILE-1:SWAP |   |
|        | ----------------- |  |
|        | SWAP-FILE-2:SWAP |   |
|        | ----------------- |  |  
|         -------------------   |  
|                               |  
|         MY-DOMAIN:PSEG        |  
|         MY-DOMAIN:DSEG        |  
 -------------------------------

--------------------------------   
| PHYSICAL MULTIPORT MEMORY:   |    
|  __________________________  |     
| | ND-500 Swapper           | |  
| | (process 0)              | |     
| | ------------------------ | |  
| | Other system info.       | |   
| | ------------------------ | |   
| | Memory area to shared    | |   
| | between simultaneously   | |  
| | running processes.       | |  
|  --------------------------  |  
--------------------------------

Figure 28. Execution of a ND-500 domain (as seen from ND-500)

A domain cannot contain any local data that can change contents. The program segments of a domain need therefore never be written back when a program page in memory is to be exchanged with another. There will only be one copy of the same program segment page in memory, even if more than one user at a time refers to it.

By specifying different segment attributes at load time, the swapping of the data segment takes place either on the system-defined swapping file or on the original data segment itself. Default is the system-defined swapping file, and this is also widely used by application programs supported by ND. Most domains consist of only one program segment and one data segment. User-developed domains usually have one or more library segments.

As the domains can take up quite a lot of room, swapping-files defined by the system must be allocated several swapping-pages. If two or more users run the same domain, each has a separate copy of the domain's data segment on the swapping file.

Norsk Data ND-30.003.7 EN

Page 126¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III

An example of how to find out how much swapping space a domain uses

@LINKAGE-LOADER
The Linkage-Loader can be used to find information about segments.

Nil: LIST-SEGMENT
Domain-name: PED-500
Segment-name: (DOMAINS)

Give only the domain name as 1st parameter the 2nd can contain directory and user name identification.

Domain no.	Segment no.
9:PED-500-ENG-K	1: (PACK-ONE:DOMAINS)PED-500-ENG-K xxxxP 144770D WC

:PSEG address range	:DSEG address range
segment attributes	segment attributes

Segment attributes:

W = Write is allowed into the data segment (default)
R = Read but NOT write is allowed into data segment
C = Copying onto system defined swapping file (default)
O = Original data segment is used as swapping file

Nil: EXIT

@FILE-STATISTICS (DOMAINS)PED-500:DSEG
26 PAGES , 51705 BYTES IN FILE

In this example, each user who runs PED-500, occupies 26 pages on the system-defined swapping file.

Norsk Data ND-30.003.7 EN

Page 127¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

3.4 Loading SINTRAN from floppy diskettes¶

If a new SINTRAN version or a new patch file is delivered, you will need to load SINTRAN into your system from floppy diskettes.

The patch file contains updates (corrections and enhancements) of SINTRAN. It is necessary to install the patches on a fresh copy of SINTRAN. The patch file should always be run to make sure your system has the latest updates.

If you have a standard configuration of SINTRAN VSX, you must remember to run the S3-Configuration program after loading (see section 3.5).

The next pages describe the VSE- and VSX-dependent part of the load procedure.

Loading SINTRAN III version K from floppy (both VSB and VSX)


Stop the processes in your system. Find out the device name of your main directory (containing SINTRAN.)

©DIRECTORY-STATISTICS.

DIR INDEX 0 : DISC-70MB-1 UNIT 0 : PACK-ONE 
(MAIN AND DEFAULT DIRECTORY)             Here is your system disk!
...

DIR INDEX 40: FLOPPY-DISC-1 UNIT 0: MY-FLOPPY

You must also know the CPU number of your system. Take a look at your confirmed SINTRAN order from ND, or use the SINTRAN command @LIST-TITLE. All ND computers have a unique CPU number assigned by ND. It is also called system number.

Norsk Data ND-30.003.7 EN

Page 128¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Example Continued¶

@LIST-TITLE	@LIST-TITLE
SINTRAN III - VSX/500 K	SINTRAN III - VSE K
ND-570/CX - SAMBA	ND-100/VSE - MAMBA
REVISION:	REVISION:
OB	OB
CPU (SYSTEM NUMBER):	CPU (SYSTEM NUMBER):
6586	755

Your CPU number.

NOTE! If you make any mistake during the loading of SINTRAN, start again from this point!

Example Continued¶

@STOP-SYSTEM

OPCOM is entered. You should have a # on the console terminal. Do the operator functions (refer chapter 2):

STOP MCL

Wait a few seconds for the second # to be displayed.

Insert the SINTRAN floppy diskette 1 (N--I) into the floppy disk drive, unit 0 (FLOPPY-DISC-1).

NOTE! In the following, all characters that shall be TYPED by you are shown, including "CR".

NOTE! VSE EXAMPLE CONTINUES ON PAGE 116.

Norsk Data ND-30.003.7 EN

Page 129¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III

Example continued for SINTRAN VSX¶

#1560&


MACM-1718-0	MACM is now loaded from the floppy disk.

APR 25, 1986

GIVE DISK TYPE AS ONE OF THE FOLLOWING OCTAL NUMBERS:¶

For some disk types, alternative disk types are given in parentheses. The alternatives differ only in disk storage capacity.

Number	Type	Alternative
0	DISC-14MB
1	DISC-21MB
2	DISC-23MB
3	DISC-28MB
4	DISC-30MB	(DISC-60MB/DISC-90MB)
5	DISC-33MB
6	DISC-38MB
7	DISC-45MB
10	DISC-66MB
11	DISC-70MB	This is the device name used for this example, it is the main directory.
12	DISC-74MB
13	DISC-75MB
14	DISC-140MB	(DISC-2-70MB)
15	DISC-2-75MB
16	DISC-288MB-R	(DISC-225MB-R/DISC-3-75MB/DISC-4-70MB-R)
17	DISC-288MB-F	(DISC-4-70MB-F)
20	DISC-450MB	(DISC-2-225MB/DISC-6-70MB-F)

If you specify the wrong disk type, this can sometimes be redefined. Disk type 11, for instance, can be redefined to type 6 or 13.

DISK TYPE: 11¶

INITIALIZED FOR:
DISC-38MB-1, DISC-70MB-1, DISC-75MB-1

REMEMBER THE MACM COMMANDS:¶

)REDEF => REDEFINE DISC TYPE
)HENT => GET SINTRAN FROM SAVE-AREA
22↑ => START SINTRAN
10.0S => LOAD SINTRAN FROM DISKETTE

TYPE ANY MACM COMMAND:¶

10.0S
Loading SINTRAN from a floppy diskette.

%============================================================%
%== SINTRAN-III/VSX VERSION K LOAD SINTRAN-DISKETTE-I ==%
%============================================================%

A list of available patch macros is displayed.

Norsk Data ND-30.003.7 EN

Page 130¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

If you have a SINTRAN system delivered on single side/single density floppies, repeat this procedure for SINTRAN floppies II, III and IV:

Replace the inserted SINTRAN floppy diskette with the next one when asked for by the MACM program.
Give the command 10,0$. Some of the information below is related to our example with only 2 SINTRAN floppy diskettes.

Example continued for VSX¶

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%
%% THE SINTRAN III SYSTEM MAY NOW BE STARTED BY TYPING: 22!
%%
%% LATER COLD STARTS MAY BE DONE EITHER BY LOADING MACM FROM
%% SINTRAN DISKETTE I, TYPE: )HENT (CR), WAIT FOR LINE FED AND
%% TYPE: 22!, OR BY PERFORMING THE SINTRAN COMMAND: COLD-START
%%
%% THIS DISKETTE ALSO CONTAINS A PROGRAM CALLED NEW-SYSTEM. THIS
%% PROGRAM SHOULD BE STARTED AS SOON AS THE THE MAIN DIRECTORY HAS
%% BEEN ENTERED. THE PROGRAM WILL GUIDE YOU THROUGH SOME OF THE
%% PROCEDURES THAT HAVE TO BE PERFORMED AFTER LOADING A NEW SYSTEM.
%%
%% DISKETTE II CONTAINS THE SYMBOL-LISTS FOR YOUR SYSTEM.
%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

LINE
* 000000 DIAGNOSTICS *	If you do not get 000000 diagnostics, try again from the NOTE!
22!	SINTRAN will now be started in a minute or two!

The same system information as shown for the cold start will be displayed.

Norsk Data ND-30.003.7 EN

Page 131¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Example continued for VSX¶

SINTRAN III RUNNING¶

ESC
- Ordinary logging in.

ENTER ↓ PASSWORD: ↓
- Just give CR when SINTRAN asks for user name and password.

NO MAIN DIRECTORY OK

@ENTER-DIRECTORY↓

DIRECTORY-NAME: PACK-ONE↓
DEVICE-NAME: DISC-70MB-1↓
DEVICE-UNIT: 0↓

Enter the main directory. The parameters are the same as what you noted in the beginning of the procedure.

Log out and in again as user SYSTEM. Use password this time.

If you have only two SINTRAN floppy diskettes, insert number II in the floppy drive. Otherwise insert number V.

Example continued for VSX¶

@ENTER-DIRECTORY, FLOPPY-DISC-1,0↓

@Ⓔ(N:SYSTEM)NEW-SYSTEM↓
- Start the NEW-SYSTEM program.

SINTRAN-III K-version VSX installation MAY 12, 1986¶

Parameter	Value
CPU number	5000
Computer	ND-100 with 32 bit floating point arithmetic
Instruction set	Commercial extended with "micro segadm" (CX)
Operating system	SINTRAN-III VSX-500 K-version
Revision level	000000
Generated	86. 5.15

Time according to SINTRAN: 23.53.28 2 JUNE - Do you want to update the clock (def=NO)? N↓

This is not so very important at the moment!

Norsk Data ND-30.003.7 EN

Page 132¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III

Example continued¶

Creating files for symbol-lists/tadadm/fmac/dmac...
Copying files from SINTRAN floppy(ies) to user SYSTEM...
Copying...FILSYS-SYMBOLS:SYMB
Copying...RTLO-SYMBOLS:SYMB
Copying...FMAC-1920C:PROG
Copying...DMAC-1915F:BPUN
Copying...COS-TADADM:BPUN
Copying...SYMBOL-1-LIST:SYMB
Copying...SYMBOL-2-LIST:SYMB
Copying...LIBAARY-MARKS:SYMB
Copying...N500-SYMBOLS:SYMB

Note
	If you have 6 SINTRAN floppies, you are asked to change floppy diskette before continuing here!
	Only needed if this is an ND-500 computer.

The copied files are very important to be able to run SINTRAN. They assign values to symbolic constants used in the different SINTRAN parts. FMAC and DMAC are special versions of MAC.

Example continued for VSX¶

Checking CPU number ... Wait ...

Give CPU number (in decimal): 6586
--- OK
Checking CPU type ... Wait ...
Give CPU type (in decimal):
--- OK

Note
	The correct CPU number for SAMBA! You can also change the CPU number (if you need to for any reason).

If ND has given you a CPU type (see your SINTRAN order), then you must give this as input here! The CR given above means that no CPU type was assigned for SAMBA!

Do you want to run the patch-file (def=Y)? Y
Defining SEGFILE and loading DMAC (def=Y)? Y

It is strongly recommended that you now run the patch file after SINTRAN has been loaded (to correct all known errors and add modifications.

Norsk Data ND-30.003.7 EN

Page 133¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

NOTE! If any errors have been diagnosed after running the patch file, you should try to load SINTRAN once more!

NOTE! If you have additional patches to the system, they should be added now! Appendix H.7 gives an example of such a file. It defines important terminal parameters.

If you have a standard version of VSX, you may now change the configuration of your system by using the S3-Configuration program. If you have not already copied the program onto your disk, install the floppy diskette containing it, and give the following commands:

Example continued for VSX
@ENTER-DIRECTORY 211024_FLOPPY-DISC-1_0J
@COPY-FILE "S3-CONFIGURATION:PROG" (211024:):S3-CONFIG:PROG\|

Turn to section 3.5 for information on how to use this program. You should at least adjust the number of background processes, spooling programs and ND-500 processes, and define spooling device numbers.

Do an ordinary cold start (i.e. @COLD-START followed by run of HENT-MODE.) If you get disk space problems, you have probably loaded a more space-consuming SINTRAN configuration or forgotten to define the necessary segment files.

Norsk Data ND-30.003.7 EN

Page 134¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Example continued for VSE¶

Insert the SINTRAN floppy diskette 1 (N--1) into the floppy disk drive, unit 0 (FLOPPY-DISC-1).

#1560& MACM is now loaded from the floppy diskette.

MACM-1718-0

APR 25, 1986

INITIALIZED FOR:

DISC-38MB-1	DISC-70MB-1	DISC-75MB-1

REMEMBER THE MACM COMMANDS:

)REDEF => REDEFINE DISC TYPE
)HENT => GET SINTRAN FROM SAVE-AREA
22↑ => START SINTRAN
10,0$ => LOAD SINTRAN FROM DISKETTE

Legal MACM commands.

TYPE ANY MACM COMMAND:

10,0$ Loading SINTRAN from floppy diskette.

%%==================================================================
%% SINTRAN-III/VSE VERSION K LOAD SINTRAN-DISKETTE-1
%%==================================================================

A list of available patch macros is displayed.

If you have a SINTRAN system delivered on single-sided/single-density floppies, repeat this procedure for SINTRAN floppy diskettes II, III, and IV:

Replace the inserted SINTRAN floppy diskette with the next one when asked for by the MACM program.

Give the command 10,0$. Some of the information below is related to the example with only 2 SINTRAN floppy diskettes.

Norsk Data ND-30.003.7 EN

Page 135¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Example continued for VSE¶

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%                                             %
%  THE SINTRAN III SYSTEM MAY NOW BE STARTED  %
%  BY TYPING: 221                             % 
%                                             %
%  LATER COLD STARTS MAY BE DONE EITHER BY    %
%  LOADING MACM FROM SINTRAN DISKETTE I,      %
%  TYPE: }I;ENT (CR), WAIT FOR LINE FEED AND  %
%  TYPE: 221, OR BY PERFORMING THE SINTRAN    %
%  COMMAND: COLD-START                        %
%                                             %
%  THIS DISKETTE ALSO CONTAINS A PROGRAM      %
%  CALLED NEW-SYSTEM. THIS PROGRAM SHOULD BE  %
%  STARTED AS SOON AS THE MAIN DIRECTORY HAS  %
%  BEEN ENTERED. THE PROGRAM WILL GUIDE YOU   %
%  THROUGH SOME OF THE PROCEDURES THAT HAVE   %
%  TO BE PERFORMED AFTER LOADING A NEW SYSTEM.%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

LINE¶

* 000000 DIAGNOSTICS *	If you do not get .000000 diagnostics, try again from the NOTE!

221¶

SINTRAN will now be started in a minute or two!

The same system information as shown in the cold start is displayed.

SINTRAN III RUNNING¶

ESC	Ordinary logging in.

| ENTER ʞ
PASSWORD: ʞ
NO MAIN DIRECTORY
OK | Just give CR when SINTRAN asks for user name and password. |

| @ENTER-DIRECTORY;
DIRECTORY-NAME: PACK-ONE;
DEVICE-NAME: DISC-70MB-1;
DEVICE-UNIT: 0; | Enter the main directory. The parameters are the same as you noted in the beginning of the procedure. |

Logout and in again as user SYSTEM. Use password this time.

If you have only two SINTRAN floppy diskettes, insert number II in the floppy drive. Otherwise insert number V.

Norsk Data ND-30.003.7 EN

Page 136¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Example continued for VSE

@ENTER-DIRECTORY, FLOPPY-DISC-1.0#
@(N:SYSTEM)NEW-SYSTEM#


CPU number	755
Computer	ND-100
Instruction set	SINTRAN VSE
Operating system	SINTRAN-III VSE K-version
Revision level	000000
Generated	86. 6. 6

Start the NEW-SYSTEM program.

SINTRAN-III K-version VSE installation MAY 12, 1986

MAMBA has been generated with the same CPU number as before.

Time according to SINTRAN: 24.50.20 2 JUNE
Do you want to update the clock (def=NO)? N

This is not so very important at the moment!

Creating files for symbol-lists/tadadm/fmac/dmac

Copying files from SINTRAN floppy(ies) to user SYSTEM...

Copying... FILSYS-SYMBOLS:SYMB
Copying... RTLO-SYMBOLS:SYMB
Copying... FMAC-1920C:PROG
Copying... DMAC-1915F:BPUN
Copying... COS-TADADM:BPUN
Copying... SYMBOL-1-LIST:SYMB
Copying... SYMBOL-2-LIST:SYMB
Copying... LIBRARY-MARKS:SYMB

If you have 6 SINTRAN floppies, you are asked to change floppy diskette before continuing here!

Do you want to run the patch-file (def=Y)? Y

Defining SEGFILE and loading DMAC (def=Y)? Y

It is strongly recommended that the patch-file is run after SINTRAN has been loaded, to correct all known errors and make all relevant modifications for this SINTRAN version.

NOTE! If any errors have been diagnosed after running the patch file, you should try to load SINTRAN once more!

NOTE! If you have additional patches to the system, they should be added now! Appendix H.7 gives an example of such a file. It defines important terminal parameters.

Norsk Data ND-30.003.7 EN

Page 137¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III

You must now carry out an ordinary cold start (@COLD-START). If you get disk space problems on the segment file SEGFILE0 you have probably ordered a configuration that takes up more space on the disk.

3.5 Configuration program¶

The SINTRAN III Configuration Program (ND-211024) is available to make changes in important system parameters in a generated system of SINTRAN III/VSX version K. The program is installed together with SINTRAN and is started by the @RECOVER command: ES3-CONFIGURATION in just the same way as other programs.

Use of the program is restricted to user SYSTEM only. The configuration program is a screen-oriented program, but may also be run on a hard-copy terminal. The program requires that the file DDBTABLES:VTM containing terminal-dependent definitions is present on user SYSTEM.

The program has 9 commands. There are 4 commands for selecting a menu of configuration parameters which may be changed:

BACKGROUND
IO-COMM
LAMU
VARIOUS

There is a command to display the value of parameters which may not be changed:

DISPLAY

In addition, there are 4 utility commands:

PRINT
prints a report of the current configuration.

GENERATE
saves the changed configuration.

HELP
displays help information on the screen.

EXIT
exits back to SINTRAN.

Norsk Data ND-30.003.7 EN

Page 138¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

You use the arrow keys, (←) or (→), or the first letter of a command name to navigate between commands (similar to ND's screen-oriented editors).

If you select a command with variable parameters, use the CR key (↵) to enter the menu of parameters, and use the arrow keys, (↑) or (↓), to navigate. When finished, use the EXIT key, or the "Home" key (↖) to exit from the menu.

You are only allowed to navigate and alter the values in the column called "Input". Another column, "Max", shows the maximum values that can be used for this generated version of SINTRAN. The values you give are checked for validity. If more than the maximum value of a parameter is needed, you must order a new version of SINTRAN.

The HELP key may be used at all times to get information about the current configuration parameter, etc.

Figure 29 gives an overview of how the configuration program affects the different parts of SINTRAN. The current values are the current system values used by SINTRAN, the next values are the system values that will apply after the next cold start. It is a good idea to generate only slightly more than actually needed of different resources. Too many may be a costly waste of segment file space (for example the number of background programs).

S3-CONFIGURATION	SINTRAN memory-area
program	(the current active values are here.)
save changes

S3-CONFIGURATION:CNFG	SINTRAN image-area
(data for the configuration program)

generate new configuration	SINTRAN save-area
	(the values which become active after next cold start.)

Figure 29. The configuration program and the parts of SINTRAN affected

Norsk Data ND-30.003.7 EN

Page 139¶

SINTRAN III SYSTEM SUPERVISOR¶

Stopping, Starting and Loading SINTRAN III

NOTE! You must carry out a cold start after having reconfigured your system, in order to put the changes into effect!

3.5.1 The utility commands¶

The PRINT command will print the current configuration to a file. You will be asked for output file and this parameter has no default value. It is recommended that you do this after you have adapted the generation parameters to suit your needs. Make a paper copy of the output file by sending it to a printer. You can put the printout into appendix A if you like.

The GENERATE command will save the changes you have made to the current configuration of SINTRAN in the configuration file. This means that the values in the "input" column replace the values in the column "Next". The save-area of SINTRAN is also updated. You will be asked to confirm that you want to save the changes. Note that you must carry out a cold start to activate the changes because only the save-area is changed.

This command may be given as part of the @RECOVER command to run the configuration program:

@S3-CONFIGURATION GENERATE

This feature should be used to reconfigure SINTRAN in exactly the same way as before, after loading from diskettes, for example when installing a new patch file.

The EXIT command is used to exit from the configuration program. If you have made any changes in the configuration, and the changes have not been saved (by the GENERATE command), you will be asked if you want to save the changes.

The HELP command will give a brief explanation of the 4 commands used to select menus of configuration parameters which may be changed. You can also ask for help information for any field in the program by using the "HELP" key.

Norsk Data ND-30.003.7 EN

Page 140¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

3.5.2 The selection commands¶

The BACKGROUND command will display a menu of configuration parameters related to background processes. The menu may look like this:

	Current	Next	Max	(Input)
Number of TADs	6	6	50	6
Number of batch processors	3	3	10	3
Number of spooling programs	4	4	20	4
Number of background programs	32	32	151	32
Background allocation	Present
Number of symbolic debugger segments	8	8	32	8
Number of ND-500 processes	21	21	201	21
Number of remote file access segments	16	16	50	16
System segment size	5	5	5	5
Mon ADP	0	0	1	0

, or . return
or ? : field information

The configuration parameters listed in this menu are:

Number of TADs:

Number of terminals on remote systems able to use this system simultaneously (via COSMOS). Each file server needs also a TAD (described in chapter 5).

Number of batch processors:

Number of batch jobs to be run at a time.

Number of spooling programs:

Number of printers with spooling.

Number of background programs:

Number of terminals that can be used simultaneously, if background allocation is present. This should be set to the number of TADs + the number of terminals + the number of telefix devices.

Background allocation:

Indicates if the background allocation system is in use. This parameter cannot be changed.

Norsk Data ND-30.003.7 EN

Page 141¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III

Number of symbolic debugger segments:¶

Number of simultaneous users of the Symbolic Debugger. This is only needed when there are users who make programs.

Number of ND-500 processes:¶

Number of simultaneous users of the ND-500 part. Should normally be equal to "number of background programs" + 1.

Number of remote file access segments:¶

Number of simultaneous users of remote file access.

System segment size:¶

Size (in pages) of the system segment. This size will affect the number of open files for each user as follows: default size (5) provides 48 file buffers, each additional page (up to total max. of 8) provides 16 buffers. Each open file uses 2 buffers if sequential access, 1 if random access. Maximum number of open files are 64.

Mon ADP:¶

Indicates if MON ADP (MON 342) is to be available. (see PD-sheets for products requiring it)

NOTE! If the Background Allocation System is not present, the "Next" and "Input" fields of "Number of background programs" will not be used.

The Current value is the value currently used by SINTRAN, the Next value is the value which will apply after the next cold start and the Max value is the maximum generated for this version of SINTRAN.

Norsk Data ND-30.003.7 EN

Page 142¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

The IO-COMM command will display a menu of some configuration parameters. The menu may look like this:

	Current	Next	Max	(Input)
Number of HDLC connections		12
Number of synchronous modems on HDLC		6
Number of X.21 connections	0	0	2	0
Define spooling device numbers				x
Define HDLC interface as HDLC or modem				x
Define printer type				x

Type \<> or E to edit these tables
\<Exit>, \<Home> or : return
\<Help> or ? field information

The configuration parameters listed in this menu are:

Number of HDLC connections:¶

Number of HDLC connection generated for this system.

Number of synchronous modems on HDLC:¶

Number of HDLC connections which may be used for synchronous modems.

Number of X.21 connections:¶

Number of X.21 connections.

Define spooling device numbers¶

Define HDLC interface as HDLC or modem¶

Define printer type¶

Use the (\<>) key or E to enter sub-menus for these parameters. See below.

The Current value is the value currently used by SINTRAN, the Next value is the value which will apply after the next cold start and the Max value is the maximum generated for this version of SINTRAN.

The last three configuration parameters in the menu IO-COMM, contain tables of values. When you select one of these, a sub-menu is displayed on your terminal.

Norsk Data ND-30.003.7 EN

Page 143¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

The sub-menu for the parameter Define spooling device numbers may look like this:

Spooling	Current	Next	(Input)	Spooling	Current	Next	(Input)
1	5	5	5	2	59	59	59
3	0	0	0	4	0	0	0
5	0	0	0	6	0	0	0
7	0	0	0	8	0	0	0
9	0	0	0	10	0	0	0
11	0	0	0	12	0	0	0
13	0	0	0	14	0	0	0
15	0	0	0	16	0	0	0
17	0	0	0	18	0	0	0
19	0	0	0	20	0	0	0

<Exit>/<Home>/ : return <Help>/? : field information N : next

The Current value is the value currently used by SINTRAN, the Next value is the value which will apply after the next cold start.

If you need to set spooling device numbers for spooling processes 21-40 or 41-60, similar sub-menus will appear for these. Either navigate "past" 20 (40), or select next menu (N) key.

The sub-menu for the parameter Define HDLC interface as HDLC or modem may look like this:

HDLC	Current	Next	(Input)	HDLC	Current	Next	(Input)
1	1	1	1	2	1	1	1
3	1	1	1	4	1	1	1
5	1	1	1	6	1	1	1
7	0	0	0	8	0	0	0
9	0	0	0	10	0	0	0
11	0	0	0	12	0	0	0
13	0	0	0	14	0	0	0
15	0	0	0	16	0	0	0
17	0	0	0	18	0	0	0
19	0	0	0	20	0	0	0

0=Do not use this interface.
1=HDLC.
2=Synchronous modem.

<Exit>/<Home>/ : return <Help>/? : field information N : next

Norsk Data ND-30.003.7 EN

Page 144¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

The Current value is the value currently used by SINTRAN, the Next value is the value which will apply after the next cold start.

If you need to set status on HDLC connections 21-32, a similar sub-menu will appear for these. Either navigate "past" 20, or select next menu (N) key.

The sub-menu for the parameter Define printer type may look like this:

Define Printer Type¶

Printer	Current	Next	(Input)
1	1	1	1
2	0	0	0
3	0	0	0
4	0	0	0

Types: 0 - Do not use this printer
1 - DMA (Used for Fujitsu)
2 - Parallel (Used for CDC/DP)
3 - Serial

\/\ return \/? field information

The LAMU command will display a menu of some configuration parameters. The menu may look like this:

LAMU Configuration Parameters¶

	Current	Next	Max	(Input)
Mon MLAMU	Present
Max number of LAMUs	32	32	32	32
Max number of LAMUs per program	2	2	2	2
Max number of system LAMUs	16	16	16	16

\, \ or return \ or ? field information

Only the first line of the menu will be shown if Mon MLAMU is not present.

The configuration parameters listed in this menu are:

Mon MLAMU:¶

Indicates if MON MLAMU (MON 315) is to be present or not.

Norsk Data ND-30.003.7 EN

Page 145¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Max number of LAMUs:¶

Maximum number of LAMUs. A LAMU is a small, reserved part of the physical memory. It enables programs to have some data shared and fixed in memory (to speed-up program execution). The LAMUs is taken from the swapping area.

Max number of LAMUs per program:¶

Maximum number of LAMUs accessible from a single program.

Max number of system LAMUs:¶

Maximum number of system LAMUs (see PD sheets for products requiring LAMUs)

The Current value is the value currently used by SINTRAN, the Next value is the value which will apply after the next cold start.

The VARIOUS command will display a menu of some configuration parameters. The menu may look like this:

	Current	Next	Max	(Input)
Number of device buffers	64	64	64	64
First legal phys. page for device buffer	0	0	0	0
Spooling queue size in pages	4	4	4	4
Number of allocated areas	40	40	40	40
Number of fast UDMA programs	0	0	0	0

\<Exit>, \<Home> or . return \<Help> or ? : field information

The configuration parameters listed in this menu are:

Number of device buffers:¶

Number of device buffers (1K words). Device buffers are used for accessing internal block devices and DMA devices (e.g. disks, magnetic tape drives, and fast printers).

First legal phys. page for device buffer:¶

First physical page number in memory accessible from DMA devices.

Norsk Data ND-30.003.7 EN

Page 146¶

Spooling queue size in pages:¶

Size of each spooling queue - a queue size of 2 pages can contain 10 queue entries and each additional page will increase queue length by approximately 7 new entries.

Number of allocated areas:¶

Number of areas in memory reserved by the monitor call MON FIXC5 (MON 61). Should be larger than number of system LAMUs.

Number of fast UDMA programs:¶

Number of RT-programs to use fast UDMA.

The Current value is the value currently used by SINTRAN, the Next value is the value which will apply after the next cold start and the Max value is the maximum generated for this version of SINTRAN.

3.5.3 The DISPLAY command¶

The DISPLAY command will show the current values of some configuration parameters which are not changeable.

The screen picture may look like this:

	Current	Max
Number of user RT programs	128
Number of user segments	734
Number of terminals	25	128
Number of semaphores	50
Number of internal devices (total)	30
Number of internal devices (block)	2
Number of SIBAS processes	12
Number of open file entries	48
COSMOS spooling	Yes
Number of telefax devices	1
Work mode version	000100B
Standard system	Yes

Norsk Data ND-30.003.7 EN

Page 147¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

The configuration parameters listed in this command are:

Number of user RT programs:¶

Number of free RT-descriptions.

Number of user segments:¶

Number of free segments.

Number of terminals:¶

Number of terminals used.

Number of semaphores:¶

Number of semaphores generated.

Number of internal devices (total):¶

Total number of internal devices (generated value).

Number of internal devices (block):¶

Number of block-oriented internal devices (generated value).

Number of SIBAS processes:¶

Number of SIBAS processes generated.

Number of open file entries:¶

Number of files open simultaneously (generated value).

COSMOS spooling:¶

Indicates if COSMOS spooling is present.

Number of telefax devices:¶

Number of telefax devices (generated value).

Work mode version:¶

Version of work mode used when generating this SINTRAN system (for internal use by ND).

Standard system:¶

Indicates if this SINTRAN is a standard system.

The Max value appearing for the Number of terminals parameter means maximum number of terminals supported by this system (generated value).

Norsk Data ND–30.003.7 EN

Page 148¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III

3.6 Initial loading of SINTRAN (ADVANCED)¶

Initial loading is loading SINTRAN into a brand new computer system where no files or users exist. In most cases, the system is loaded by ND when it is delivered. Sometimes, for example if a new system disk has to be made after a disk crash, this is done by the system supervisor.

When the initial load takes place, the disk space available must be taken into consideration, especially in configurations with rather small disks.

Some standard user areas must be created and given disk space, and some files must also be created. SINTRAN and some special files (system files) must be placed on the main disk. This is called the system disk. The amount of space SINTRAN needs to occupy on the segment file(s) is discussed in section 3.8. The total number of pages needed by user SYSTEM depends on the configuration.

The main disk is also a main directory. SINTRAN file system requires that all existing users are defined (created) in a main directory, but only a few users need to be given disk space on the system disk.

The different categories of user are listed in table 5.

SINTRAN will not work without system files. Table 6 gives a list of the system files used in both ND-100 and ND-500 configurations.

Norsk Data ND-30.003.7 EN

Page 149¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

User name	Used for
ND-100 and ND-500 computers:
BPUN-FILES	ND software applications of type :BPUN
FLOPPY-USER	Copying files to/from floppy diskettes
PROGRAM-FILES	ND software applications of type :PROG
RT	Owner of RT-programs
SCRATCH	Scratch files for background programs
SYSTEM	SINTRAN and other important system files
UTILITY	Ordinary ND software applications and software closely integrated with SINTRAN
	Configuration-dependent user definitions (personal user areas)
ND-500 computers:
DOMAINS	ND-developed ND-500 application programs
N502-MICRO-TEST	ND-500 test programs (for use by ND Service)
	You can delete this user's files and user definition if you have little free disk space

Some large software applications developed by ND must be placed on dedicated users. Examples:

USER-ENVIRONMENT	See PD-sheets for the ND developed software applications you have.
NOTIS

Table 5. Standard SINTRAN user areas

Norsk Data ND-30.003.7 EN

Page 150¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Status	File name and type	Size (pages)	Organization	Directory
S	(UTILITY)DUMP-REENTRANT:MODE	Conf	Indexed	any
S	(UTILITY)STANDARD-DOMAINS:MODE	Conf	Indexed	any
		Conf	Indexed	default
5	CONTROL-STORE:DATA	72	Indexed	default
	COS-TADAM:BPUN	4	Indexed	any
	DBDTABLES:VTM	10-20	Indexed	system disk
	DMAC-1915:BPUN	19	Indexed	any
C	DUMMY:;1	Periph		default
	FILSYS-SYMBOLS:SYMB	21	Indexed	system disk
C	FLOPPY-x:;1 (x = 1..6)	Periph		default
	FMAC-1920C:PROG	15	Indexed	system disk
	LIBRARY-MARKS:SYMB	9	Indexed	system disk
S	LOAD-MODE:BATC	Conf	Indexed	system disk
C	MACM-AREA:DATA	64	Allocated	system disk
C	MAILBOX:DATA	10-20	Indexed	system disk
S	N500-SYMBOLS:SYMB	31	Indexed	system disk
S	ND500-HENT-MODE:MODE	Conf	Indexed	system disk
	PATCH-FILE:OUT	Conf	Indexed	system disk
	PATCHES:OUT	Conf	Indexed	system disk
	RTIL:DATA	64	Indexed	system disk
	RTLO-SYMBOLS	24	Indexed	system disk
	S3-CONFIGURATION:CNFG	2	Indexed	system disk
	S3-CONFIGURATION:PROG	62	Indexed	system disk
C	SEGFILE:DATA (x = 0..3)	Conf	Allocated	system disk
C	SINTRAN:DATA	63	Allocated	system disk
5	SWAPPER:DSEG	54	Indexed	default
5	SWAPPER:PSEG	11	Indexed	default
5C	SWAP-FILE-x:SWAP (x = 0..3)	Conf	Contiguous	any
	SYMBOL-1-LIST:SYMB	38	Indexed	system disk
	SYMBOL-2-LIST:SYMB	Conf	Indexed	system disk
C	SYSTEM-OUTPUT-1:SYMB	Temp	Indexed	system disk
C	TERMINAL:;1	Periph		default

Status: S means file created and maintained by the system supervisor.
C means file that only need to be created, contains initially no data.
5 Only for ND-500 computers.

No status letter means that the file is either copied manually or by dedicated installation programs (refer to PD sheets).

Conf : Configuration-dependent. The number of such files or the file size varies.
Temp : Temporary
Periph : Peripheral

Table 6. System files

Norsk Data ND-30.003.7 EN

Page 151¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

3.7 Example of initial loading (ADVANCED)¶

The following short example is intended to be a guide when carrying out an initial load in an ND-100 configuration. Configuration-dependent commands and parameters are commented on.

Example of initial loading of SINTRAN VSX¶

Load SINTRAN from floppy diskette as described in section 3.4 where you log in the first time.

See your SINTRAN order form for the device name of your system disk.


ENTER	Just give CR here.
PASSWORD:
NO MAIN DIRECTORY	OK
CREATE-DIRECTORY
DIRECTORY NAME: PACK-ONE
DEVICE-NAME: DISC-70MB-1
DEVICE-UNIT: 0
BIT FILE ADDRESS:	Must correspond to unit plug on disk drive.

The directory name is user-defined. The system disk is conventionally given the name PACK-ONE.

The bit-file is system information for the file system. Default value is in the middle of the disk. If you have a rather small disk, you may need to use another value. See chapter 4. A 70 MB disk corresponds to 512*70=35840 pages, but some of these are used by the file system for system information.

Norsk Data ND-30.003.7 EN

Page 152¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Example continued for VSX¶

Command	Description
`@ENTER-DIRECTORY`
`DIRECTORY-NAME: PACK-ONE`	The directory exists now, and must
`DEVICE-NAME: DISC-70-MB-1 0`	be entered before it is accessible.
`@CREAT-USER`
`USER NAME: SYSTEM`	The first user is created.
`@LOGOUT`
`-- EXIT --`
`ESC`
`ENTER SYSTEM:`	User identification in SINTRAN is done
`PASSWORD:`	when logging in. The first time you
	logged in, there were no users.
	Therefore log out and then log in as
	user SYSTEM.
`@CHANGE-PASSWORD`	An error message is displayed because SINTRAN tries to open a SCRATCH file. Ignore it! User SCRATCH does not exist yet.
`OLD PASSWORD:`	Users SYSTEM and RT should always
`NEW PASSWORD:`	be protected by passwords.
`@GIVE-USER-SPACE SYSTEM 15000`	To be used for the installation.

The space needed is very configuration-dependent. It is slightly more than 29MB. In a small system (Satellite/Compact) 5000 - 10000 pages should be sufficient. It is sensible to give user SYSTEM more pages than necessary before installation, and give some of the superfluous pages back afterwards.

Example continued for VSX¶

Command
`@SET-INITIAL-FILE-ACCESS R,RWA,RWAD`
`@SET-DEFAULT-FILE-ACCESS R,RWA,RWAD`

After giving the command @SET-INITIAL-FILE-ACCESS, all users created from now on will initially get this file access (the parameters are public, friend and own access). You must decide what data-security considerations the file access should be based upon.

The file access for one particular user is set when giving the command @SET-DEFAULT-FILE-ACCESS in this case user SYSTEM. This definition survives all loading of SINTRAN. Some system files must be given another access than this.

Norsk Data ND-30.003.7 EN

Page 153¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Allocate the important system files. Only the size of SEGFILE is configuration-dependent. If necessary, create the other segment files using @ALLOCATE-FILE or CREATE-FILE commands. If more than one directory must be used for the segment files; create, enter and give user SYSTEM disk space first.

Example continued for VSX

@ALLOCATE-FILE SINTRAN:DATA
PAGE ADDRESS (OCT): 1
NUMBER OF PAGES: 71B

@ALLOCATE-FILE MACM-AREA:DATA 100 100B

@ALLOCATE-FILE SEGFILE:DATA 200 10000D          Medium configuration.

It is advisable to have public and friend access NONE for the following system files:

@SET-FILE-ACCESS SINTRAN:DATA N N RWA
@SET-FILE-ACCESS MACM-AREA:DATA N N RWA

SEGFILE must be accessible from user RT (later created as friend):

@SET-FILE-ACCESS SEGFILE:DATA N RWA RWA

In addition, SEGFILE must be made accessible for SINTRAN:

@SINTRAN-SERVICE-PROGRAM
*DEFINE-SEGMENT-FILE
MEMORY? Y
SAVE-AREA? Y
SEGMENT FILE NUMBER (OCT): 0
SEGMENT FILE NAME: SEGFILE:DATA

The file MAILBOX is used by the MAIL system. Only user SYSTEM needs access to it.

@CREATE-FILE MAILBOX:DATA,

@SET-FILE-ACCESS MAILBOX:DATA N N RWA

Norsk Data ND-30.003.7 EN

Page 154¶

Example Continued for VSX¶

The file RTFIL is used by the RT-Loader.
Only SYSTEM and RT need access to it.

@CREATE-FILE RTFIL:DATA,,

@SET-FILE-ACCESS RTFIL:DATA N N RWA

Make a file associated with the users' terminals.
All users should be allowed to access it:

@SET-TERMINAL-FILE "TERMINAL"

@SET-FILE-ACCESS TERMINAL RWA RWA RWA

Create the file SYSTEM-OUTPUT-1, which will be used for output when running the batch job LOAD-MODE during warm start. The public file access should be NONE to prevent other users from discovering the SYSTEM password!

Example Continued for VSX¶

@SET-TEMPORARY-FILE "SYSTEM-OUTPUT-1:SYMB"

Create peripheral files for all peripheral devices (except from Streamer and disk drives). In this example the configuration has one floppy drive (FLOPPY-DISC-1 unit 0) and one line printer:

@SET-PERIPHERAL-FILE "FLOPPY-1"
DEVICE NUMBER (OCT): 1000B

@SET-FILE-ACCESS FLOPPY-1 RWA RWA RWA

@SET-PERIPHERAL-FILE "LINE-PRINTER" 5

See SINTRAN Commands Reference manual for legal device numbers.
Take also a look at section 3.6 and your SINTRAN order form.
If a printer has spooling, it must be given spooling pages.
The file access should also be as shown:

@SET-FILE-ACCESS LINE-PRINTER WA RWA RWA
@CREATE-NEW-VERSION LINE-PRINTER::10,1.

Nine spooling files are created for the Line Printer.

Norsk Data ND-30.003.7 EN

Page 155¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

Example continued¶

You can now create the standard SINTRAN users:

@CREATE-USER FLOPPY-USER
@CREATE-USER UTILITY
@CREATE-USER BPUN-FILES
@CREATE-USER SCRATCH
@CREATE-USER RT

User RT must be allowed to access the segment file and RTFIL:

@CREATE-FRIEND RT
@SET-FRIEND-ACCESS RT RWA

User BPUN-FILES must get some pages to keep copies of your application programs:

@GIVE-USER-SPACE PACK-ONE:BPUN-FILES 1000

User SCRATCH must be given some pages for the scratch files:

@GIVE-USER-SPACE PACK-ONE:SCRATCH 2500

This should normally be sufficient for 5-15 users working simultaneously with PED, NOTIS-WP or similar products. Log in as user SCRATCH and create necessary scratch files. There must be one for each terminal, batch processor and TAD.

Example continued for VSX¶

ENTER: SCRATCH	SINTRAN tries to open a non-existent scratch file - ignore the message.

@SET-DEFAULT-FILE-ACCESS RWA RWA RWA

This user's file access was initially only "R" for public use.

@CREATE-FILE SCRATCH01:DATA,,
...
@CREATE-FILE SCRATCH25:DATA,,

Norsk Data ND-30.003.7 EN

Page 156¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

You should now load an editor to be able to make mode files necessary for starting and stopping the system. If PED or NOTIS-WP is not included in your software packet from ND, you should at least have the modest QED. See appendix H for examples. You need at least the mode files LOAD-MODE, HENT-MODE and DUMP-REENTRANT. Remember to set the file access for such files to N for public.

Having the necessary mode files for loading, you are ready to continue installing SINTRAN. Continue from the point in section 3.4 where the program NEW-SYSTEM is to be run.

You should now load application software. Study the PD sheets. You are advised to load the BACKUP-SYSTEM as one of the first applications to make it easier to copy files (some of the PD sheets also assume that it is present.

If your computer is within a network, you may want to give it a name to identify it uniquely. It is possible to redefine the prompt string used by SINTRAN, and the heading that is displayed when logging in:

Example continued for VSX¶

@SINTRAN-SERVICE-PROGRAM

*DEFINE-PROMPT-STRING  
STRING: DOCOS'  
PROMPT STRING IN LOCAL MODE? Y  
MEMORY? Y  
SAVE-AREA? Y  

*DEFINE-TITLE  
TITLE: $--- BAHAMAS COMPANY'S DOCOS ---$'  
MEMORY? Y  
SAVE-AREA? Y  
*EXIT


The character ' must terminate the string.	The parameter "prompt string in local mode" means that users directly connected to the network
It is not printed out later.	(not via network) also get this prompt.
The character $ is replaced by CR at output.

Norsk Data ND-30.003.7 EN

Page 157¶

SINTRAN III SYSTEM SUPERVISOR¶

STOPPING, STARTING AND LOADING SINTRAN III¶

3.8 Space requirements for K version¶

On VSX systems, a standard system will require approximately 4358 pages of memory. This means that you should have at least 1 MB of memory available for ND-100.

The disk requirements for an VSX-system are calculated as follows:

Description	Pages required	Multiplied with
SINTRAN constant	1090	1
background program: (default)
● data segment	128
● system segment	5	--- " ---
MON ADP	63
ND-500 process	5
Symbolic Debugger segment on ND-100	8
Remote File Access segment	4
Spooling queue segment (default 4 pages)	2-12

Table 7. Formula for calculating disk space for SINTRAN VSX - K

Norsk Data ND-30.003.7 EN

Page 158¶

I'm sorry, but I can't process the image content directly. Could you please provide the text you'd like converted into Markdown?

Page 159¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION

CHAPTER 4¶

FILE SYSTEM SUPERVISION

This chapter describes the system supervisor's responsibilities in relation to files, user areas, and directories. Section 10.4 explains how to test the directory structure. The exact layout of the file system on a disk is described in appendix F.

4.1 Files¶

All kinds of information can be stored on mass storage files. A file is divided into pages of 1 Kwords. The pages of a file can be stored consecutively on the disk, or they can be scattered around with pointers to the pages used by the file. Some examples of information that can be stored in a file are:

Contents	File type
A formatted text document	:OUT
A set of commands (mode job)	:MODE ¹
A text document	:TEXT
An executable ND-100 program	:PROG
An executable ND-500 program	:PSEG
------ " ------	:LINK
------ " ------	:DSEG
General data	:DATA
The source of a program	:SYMB

¹) SINTRAN expects file type :SYMB when running a mode job.

Table 8. Example of different file types

A file is identified by a file name. This file name is used in commands to the file system. A complete file name has five parts as shown below, i.e. the directory it is found on, the user area it belongs to, the actual name given to it, the file type and the version number. If the file name is abbreviated, it should be unambiguous.

(DIRECTORY:USER NAME)FILE NAME:FILE TYPE;VERSION

Files are organized into directories containing files for one or more user areas. A directory can be thought of as a catalogue. When a file is asked for, the system looks it up in the directory to see where it is located. When a new file is created, a new entry is made in a directory. Each disk or floppy diskette in use has its own independent directory.

Norsk Data ND-30.003.7 EN

Page 160¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

Each file belongs to a user area. All user areas must be registered in a main directory. Only user areas defined in a main directory are known to SINTRAN. The directory contains information about the disk space available to each user.

A file type is used to designate the contents of the file. This file type can be set by the user as a maximum 4-character extension of the file name. It is separated from the file name by a colon. The file types shown in table 8 are commonly used as default in commands or subsystems.

ND has standardised many file types. Many application programs expect to find information on certain files with certain file types. It is therefore recommended that you to some extent follow these naming conventions when creating/renaming files (as described in this manual, other manuals and PD-sheets).

A file can exist in several versions. The version number is separated from the file type by a semicolon (;). The maximum number of file versions is 256. Version 1 is the most recent version of the file.

4.1.1 Creating indexed files¶

Indexed files can be created in two ways. The first is by directly giving the SINTRAN command:

@CREATE-FILE {file name} {number of pages}

When <number of pages> is given the value "0" the file will have no space to start with, but will take space as it is written into. Its pages are scattered around on the disk/floppy diskette. Initially, only a new entry in the directory is reserved for the file. The file becomes indexed the first time it is written into. Most files in a system are indexed.

Directory catalogue	dynamically expanding
first	page 0
next	page 1
last	page 2
MY-FILE (indexed)	Not used yet

Increasing page address on the directory

Figure 30. Example of an indexed file

Norsk Data ND-30.003.7 EN

Page 161¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

The file type should be specified according to what it is intended for. If no directory or user name is given, the file will be created in your user area on your default directory. Default directories are explained in the next section.

A new file can also be created by enclosing a file-name parameter in a command in double quotes "...". This procedure can be followed with all SINTRAN commands that have the parameter (). Application programs also have this possibility for creating new files via calls to SINTRAN. For example, a new letter written using NOTIS-WP will be stored under the name given in the store command, if this name is enclosed in double quotes.

Creating contiguous files¶

Contiguous files can also be created in two different ways. If the second parameter in the command @CREATE-FILE is greater than zero, the file becomes contiguous. A contiguous file occupies a contiguous area on the disk/floppy diskette. Normally, only special files, such as the system files mentioned in chapter 3, and databases are contiguous. When such a file is allocated on the disk, it is placed in the first free hole big enough to contain it.

Directory catalogue	first	page 0	page 1	page 2	...
MY-FILE (contiguous)
...	...

Number of pages

Increasing page address on the directory

Figure 31. Example of a contiguous file

A contiguous file cannot expand dynamically when written into. Instead, another command must be used:

EXPAND-FILE <file name> <number of pages>

Norsk Data ND-30.003.7 EN

Page 162¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

It is only possible to expand the file if sufficient subsequent space from the end of it is still free to be used. If not, the file must be moved to another area of the disk. If the file only contains temporary data, it can be deleted and then recreated. This method can for example be used if the contiguous ND-500 file SWAP-FILE-1:SWAP becomes too small. The file SEGFILE0:DATA cannot, however, be moved to another area, since SINTRAN requires that this file starts at a fixed start address. This restriction does not apply to the other segment files. Segment files contain temporary data in the sense that a cold start must be carried out to renew them. If it is impossible to create a contiguous file of a certain size, the whole directory must be reorganized. Necessary contiguous files should always be the first to be created in a directory.

In SINTRAN, there is also another special category of contiguous files, called allocated files. The command

@ALLOCATE-FILE <file name> <page address> <number of pages>

creates an allocated file. An allocated file is, in addition to being of a certain size, placed on a fixed area of the disk. <page address> is the place on the disk where the file starts. See section 3.6 for information about which SINTRAN system files must be allocated.

4.1.2 Shrinking, renaming and deleting files¶

Assume that a user has a large, indexed file. After parts of it have been deleted in an editor, e.g. NOTIS-WP or PED, the file will still occupy as many pages on mass storage as before. Deleting means here that the file is rewritten with fewer bytes than it previously consisted of. The file can effectively be shrunk by renaming it, copying it back to the original name and then deleting the renamed file (as shown in the following example). This makes the superfluous pages available for other files.

Norsk Data ND-30.003.7 EN

Page 163¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION

Example of shrinking a file¶

@FILE-STATISTICS PEDAGOGIC-EX:SYMB
FILE 98 : (PACK-ONE:SYSTEM)PEDAGOGIC-EX:SYMB
(INDEXED FILE)

10 PAGES, 10010 BYTES IN FILE

The file occupies 10 pages. The number of pages really needed is the number of bytes in the file divided by 2048. 10010/2048=4.88, rounded up to 5 pages. It makes sense to shrink this file.

@RENAME-FILE¶

FILE NAME	NEW FILE NAME AND TYPE
PEDAGOGIC-EX:SYMB	TEMPORARY:SYMB

The file to be shrunk is renamed to avoid name conflicts.

@COPY¶

TO DEVICE	FROM DEVICE
"PEDAGOGIC-EX:SYMB"	TEMPORARY:SYMB

A new file with the same name as the old one is created by using double quotes. This copy command copies the no. of bytes last written in the file.

@DELETE-FILE TEMPORARY:SYMB¶

Do not forget to do this!

This will not work for indexed files with holes in them. A hole is an unused, non-allocated page in an indexed file. One example of such files is program files. It is recommended that the @COPY command should be reserved for shrinking and for copying to peripheral files, as faster commands and programs are available for general copying.

As shown in the previous example, a single file can be deleted by the command:

@DELETE-FILE <file name>

Another command,

@DELETE-USERS-FILES (<file name>) [ [(<manual check?>)] ]

can be used to delete more than one file at a time. The command must be used with care. It is impossible to restore a deleted file! User-SYSTEM is always forced to use the manual check and confirm that each file that matches the <file name> parameter is to be deleted.

Norsk Data ND-30.003.7 EN

Page 164¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

4.1.3 Retrieving information about files¶

To find out data about a specific file the command:

@FILE-STATISTICS () ()

can be useful. This command, which is available to all users, lists useful information about file type, file access settings and file size.

For example, a file called PACKMAN:PROG is listed by the command:

Example of using the @FILE-STATISTICS command

@FILE-STATISTICS_PACKMAN
FILE 28 : (PACK-ONE:JOHNNY-PLAYER)PACKMAN:PROG;1	date created.
(INDEXED FILE)	last time read.
PUBLIC ACCESS : NONE	last time written.
FRIEND ACCESS : READ, WRITE, APPEND
OWN ACCESS : READ, WRITE, APPEND, DIRECTORY
OPENED 1986 TIMES
CREATED 01.10.55 JULY 4, 1980
OPENED FOR READ 16.28.58 JUNE 23, 1986
OPENED FOR WRITE 01.12.24 JULY 4, 1980
56 PAGES
112540 BYTES IN FILE

Another command @WHERE-IS-FILE, which is also available to all users, lists the following information about a file:

Whether or not it is free to be used (not opened).

If opened by a user, the user area's name and terminal number.

Whether or not it is reserved by an RT-program.

If it is a spooling file, whether or not it is currently in use.

This command is most useful for collecting information about peripheral files and printers with spooling. For instance, if you want to list information about free spooling files for a printer called ELPHO-20. (More information about peripherals is given in chapter 6).

Norsk Data ND-30.003.7 EN

Page 165¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

Example of finding free spooling files¶

WHERE-IS-FILE
FILE NAME: ELPHO-20
ELPHO-20:1	RESERVED BY RT-PROGRAM SPRTI
ELPHO-20:2	OPENED FOR RT-PROGRAM USE
ELPHO-20:3	SPOOLING FILE IN USE
ELPHO-20:4	SPOOLING FILE IN USE
ELPHO-20:5	FREE TO USE
ELPHO-20:6	FREE TO USE
ELPHO-20:7	FREE TO USE
ELPHO-20:8	FREE TO USE

The version no. 1 of the file is the peripheral file for the printer. "SPRTI" has always reserved the peripheral file, because this printer has spooling. "OPENED FOR RT-PROGRAM USE" means that this version is currently being printed or written into, while the versions with the text "SPOOLING FILE IN USE" are waiting for printing. The other versions are unused (empty) at the moment.

In addition to these SINTRAN commands, there is also an ADP product designed for manipulating files:

File Manager¶

Supervisors who spend a lot of time handling files are advised to use this product. It is a screen-oriented product that allows you to navigate on the screen between all files belonging to a given user-area, sort, delete and change attributes (to mention some of the many useful features). The program is usually started by typing @FILE-MANAGER or a legal abbreviation.

Norsk Data ND-30.003.7 EN

Page 166¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

4.2 Directories¶

A directory is a means of organizing the available space on a contiguous area of a disk or floppy diskette. It consists of descriptions of user areas and files as well as some administrative information for the file system. The description of a user area is called a user entry, while a single file description is called an object entry. The structure is explained in detail in appendix F.

dir.
index

0	PACK-ONE
1	PACK-TWO

corresponding structure as for PACK-ONE

Directory table

 _______________
|               |
|   PACK-ONE    |
|_______________|
     --> User descriptions
          ______      ______      ______
        |        |  |        |  |        |
        | SYSTEM |  |   RT   |  |  JOHN  |
        |________|  |________|  |________|

file system information

SINTRAN	MY-RT-PROGRAM	MY-MEMO
MACM-AREA	...	...
SEGFILE

Master block

________________
|                |
|                |
| Other file    |
| descriptions  |
|                |
|________________|

Figure 32. Example of directory structure (simplified)

The directory table is one of the main tables in the file system. It is organized sequentially. Each entry in the table contains a description of a directory and there is one entry for each directory in the system. The first word of each entry marks the directory as entered or released, as main or default, or as reserved or not reserved for special use. The directory table is located in physical memory. Some of these concepts are explained below.

A main directory provides a register of user names that can be found and used by the file system without requiring the user name to be defined on any other directory. All user areas must be defined in a main directory. The main directories are searched for matching user name and password when logging in.

Norsk Data ND-30.003.7 EN

Page 167¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

There is normally only one main directory in the system, capable of holding as many as 256 different user area definitions. A main directory cannot be created on a floppy diskette. This means that, if you want to access files on a floppy diskette with a user name that does not exist in a main directory, you must create the user area in a main directory first. This is one of the reasons why FLOPPY-USER is a standard user area on all ND computers.

A related, but not identical, concept is the user area's main directory. This concept is relevant for systems with more than one main directory. It is the first main directory (lowest directory index) where the user area is defined.

Main directories should not be entered or released when the system is running. If this is done, a user area's main directory can change. When a user logs in, the main directory for his or her user area is determined at that moment and stored on the terminal's system segment.

A default directory is a directory that is automatically searched whenever a file is referred to without specifying the directory name. A main directory is always a default directory.

The user area's default directory is the first default directory (lowest directory index) where a user area has disk space. The user area's default directory is searched when a user refers files omitting the directory name.

The search strategy used by the file system is as follows: If a user-name is supplied to the file system and the user area's main directory is to be determined, the file system starts with the lowest directory index. If it is a main directory, all user names are searched for a match. It then searches the next main directory and so on, until all main directories have been searched.

If an exact match occurs on a directory (i.e. an existing user name is identical to the user name supplied), the search need go no further. If only a partial match occurs (according to abbreviation rules), all main directories are searched to make sure that the supplied name is unambiguous. If no match is found at all, the user area does not exist.

When running mode or batch jobs, it speeds up the file searching if you supply the directory and user names. When working interactively, however, there is no point in doing this, since the time gained by the increased speed of execution is far less than that which is lost by the extra typing involved.

Norsk Data ND-30.003.7 EN

Page 168¶

Directories¶

Users	PACK-ONE	PACK-TWO	PACK-THREE
	Main and	Default	Not default
	default
SYSTEM	*	*
DORIS	-	*
HARRY	-	-

Symbols: * means user area is defined and given space
- means user area is only defined

All user areas have PACK-ONE as their main directory. User SYSTEM has default directory PACK-ONE, DORIS has PACK-TWO, while HARRY has none.

Table 9. Example of main and default directories

4.2.1 Creating a directory¶

A directory must be created on a disk/floppy diskette before any user-areas or files can be made on it. In addition, a brand new disk/floppy diskette must be formatted before user areas and files can be put on it. Formatting of disks and floppy diskettes is described in section 4.2.2.

A new directory on a disk/floppy diskette is created by the command:

@CREATE-DIRECTORY
[] [] [(bit-file address)]

You need to know more about the parameters in order to create the directory:

A user-defined name that is subsequently used to identify this particular directory. A maximum of 16 alphanumeric characters and hyphens (-) is allowed. Examples: PACK-ONE, PACK-TWO (these names are also used other places in this manual).

Norsk Data ND-30.003.7 EN

Page 169¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION

A logical name to uniquely identify for SINTRAN which disk controller the directory is connected to and the disk format. Examples: DISC-45MB-1, DISC-70MB-1 and FLOPPY-DISC-1.

If you do not already know the to use, see your SINTRAN order form or appendix C for a thorough description.

The disk/floppy diskette unit number to which the disk and directory is connected to. The number range for disks is 0-3, and 0-2 for floppy diskettes.

[(fixed=F/removable=R)]

Fixed or removable disk pack. Only a few old disks need this as a separate parameter. For most disks this is part of the device name (those ending with -R or -F in appendix C).

[]

A physical disk can be divided into one or more directories. Most disks have only one directory. The disks with more directories are in general large disks (several hundred MBs). A disk with more than one directory is called a sub-divided disk. The number range for sub-units is 0-5.

((bit-file address))

In order to keep track of which pages are free, The bit-file contains a map of the file system. A bit-file has one bit for each page on the directory. This means there is one new page in the bit-file for each 16,384 pages in the directory.

The parameter is the address of the first page of the bit-file. If the parameter is omitted, the file system will place the bit-file in the middle of the disk, or as near as possible to the middle, if bad pages occur there. A bad page is a page that cannot be used. It will be marked as used in the bit-file.

The parameter also affects the placement of the remainder of the system information, since this is placed near the bit-file.

For most systems the middle of the disk is the best place for the bit-file, and it is seldom necessary to use anything else than default value for a floppy diskette. If a contiguous file of size greater than about half of the directory size is wanted, the bit-file has to be placed somewhere else. The legal range for page numbers is given in appendix G.

Norsk Data ND-30.003.7 EN

Page 170¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

File System Structure¶

Disk Controller 1	Disk Controller 2
Device Unit 0	(other disk drives/packs)
(DISC-70MB-1)
PACK-ONE	Device Unit 1 (DISC-4-70MB-1) sub-unit
	PACK-TWO
	PACK-THREE
	PACK-FOUR
	PACK-FIVE

Device Unit 1 Sub-Units
0           => DISC-4-70MB-1, unit 1, sub-unit 1
1           => DISC-4-70MB-1, unit 1, sub-unit 1
2          
3

Figure 33. Example of directory structure

Example of creating a directory on a floppy diskette¶

To create a directory called FLOPPY-PACK on the floppy diskette controller 1, unit 1, you can type:

@CREATE-DIRECTORY
DIRECTORY NAME: FLOPPY-PACK
DEVICE NAME: FLOPPY-DISC-1
DEVICE UNIT: 1
BIT FILE ADDRESS:

Example of creating a directory on a disk¶

To create a directory called PACK-ONE on the 70MB FSD disk, controller 1, unit 0, you can type:

@CREATE-DIRECTORY PACK-ONE, DISC-70MB-1, 0

Figure references and notes

Norsk Data ND-30.003.7 EN

Page 171¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

Files should normally be placed on a directory in the following sequence:

allocated (contiguous) files
large contiguous files
indexed files

If a disk is to contain large contiguous files as well as indexed files, careful consideration should be given to where the files are placed. It is recommended that all indexed files (including spooling and temporary files) should be placed on the same area of the disk. The bit-file should be placed in the middle of this area, to minimize the access time needed for subsequent accesses within the file.

Norsk Data ND-30.003.7 EN

Page 172¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

Example of system with large, contiguous files¶

A system has one 75 MB disk pack giving 36,945 pages. The system must have contiguous system files with sizes:

File	Pages
Master block	1 page (this is not really a file!)
SINTRAN:DATA	63 pages
MACM-AREA:DATA	64 pages
SEGFILE:DATA	6,500 pages

Sum system files: 6,628 pages

The files above must follow the same order on the disk, starting from page 0.

The installation also runs a database with four contiguous files. These follow SEGFILE:DATA in the specified order:

File	Pages
ORDER-DB:DATA	1,600 pages
ORDER-SYS:DATA	6,000 pages
ORDER-DA-1:DATA	8,000 pages
ORDER-DA-2:DATA	8,000 pages

Sum database files: 23,600 pages

The bit-file and other files then have:

Description	Pages
Directory size	36,945 pages
System files	- 6,628 pages
Database files	-23,600 pages

Disk area left: 6,717 pages

Thus the bit-file should be placed at disk address:

\ + \/2 = 30,228 + 6,717/2 = 33,586 = 101462B

bit-file address

Page no.
0	30227	36945

Norsk Data ND-30.003.7 EN

Page 173¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

CAUTION! If a new directory is created on the same disk or floppy diskette, the old directory will be completely destroyed. Pointers to pages used by different files in the old directory will be overwritten. Pages previously used will be marked as free in the new bit-file. The data, however, still remains and can be retrieved with the help of the stand-alone program, FILE SYSTEM INVESTIGATOR. This cannot, however, be achieved without detailed knowledge of the file system.

CAUTION! If you specify wrong parameters to @CREATE-DIRECTORY and the parameters identify an existing disk type as seen from SINTRAN, the disk will enter fault state and the system will "hang".

4.2.2 Formatting a disk or floppy diskette¶

If you intend to put SINTRAN on a brand new disk, this must first be formatted. All new disks must be formatted before they can be used. Hard disks must be formatted by the system supervisor. All users, however, are allowed to format floppies.

The purpose of formatting is to determine the hardware layout on the disk: for each track, to decide how many sectors there should be; for each sector, to write disk address and reserve space for the data. Appendix G explains the physical disk layout.

CAUTION! Any data on a disk or floppy diskette is irretrievably lost when it is formatted.

Example of formatting a floppy diskette¶


@DEVICE-FUNCTION	The @DEVICE-FUNCTION command has several special functions for handling peripherals.
FILE NAME:	FLOPPY-1
FUNCTION:	SET-FLOPPY-FORMAT
FORMAT (OCT):	17

Norsk Data ND-30.003.7 EN

Page 174¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

The file name is the peripheral file name for FLOPPY-DISC-1, unit 0. Unit 1 should conventionally be called FLOPPY-2 and so on.

The floppy format is selected manually because the floppy diskette is not yet formatted. SINTRAN finds the floppy format itself on a formatted floppy diskette. ND uses these formats:

Format	Description	Pages
Format 0B	Single-Sided / Single-Density (SS/SD)	148
Format 17B	Double-Sided / Double-Density (DS/DD)	612

Example continued¶

@DEVICE-FUNCTION FLOPPY-1
FUNCTION: FORMAT-FLOPPY

Formatting takes a few minutes. If you get many bad-page reports (pages that cannot be used), do not use the floppy!

The stand-alone program DISC-TEMA is used for formatting (and backup) of disks. You find this program on the floppy diskette "Test programs for ND-100" (ND-210523). The following procedure gives an example of how one particular disk type is formatted. If you are going to format another disk type, you must know the SINTRAN disk name for it. See your confirmed SINTRAN order form.

If there are bad spots on a track, the whole track has to be reallocated (moved to another place on the disk). Initially the disk has some tracks in a spare pool. By default, each track is tested after formatting and reallocation is done automatically.

Some disks have a spare sector per track. If there is only one bad spot on a single sector of the track, the sector is reallocated.

If DISC-TEMA is not able to find the manufacturer's information about bad tracks at program start, you are asked to give this information manually. This list is enclosed with the disk media.

Norsk Data ND-30.003.7 EN

Page 175¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

Example of formatting a disk (ADVANCED)¶

Command/Step	Description
@STOP-SYSTEM	Make a controlled stop of the computer.
MCL	Install the floppy with DISC-TEMA in floppy drive 0. If you want to format a removable disk pack, install this in any disk drive unit. Write protect the others!
*#1560&
*HELP	The Floppy Monitor has been loaded (common for all test programs). The prompt * tells that it is ready to accept commands.
FLOPPY-MON-2010G
LIST-FILE
LOAD-FILE
PLACE-FILE
OPCOM
HELP

LIST-FILE DISC¶

FILE #: (ND-10523D: FLOPPY-USER) DISC-TEMA-H00: BPUN

LOAD-FILE DISC-TEMA¶

DISC-TEMA is loaded into memory and automatically started.

DISC TEST AND MAINTENANCE SYSTEM (DISC TEMA)¶

Program no.: 203134H00
Date issued: 12 January 1985

DISC NAME: ?¶

After the disk name is given, the disk controller is tested.
No such DISC NAME, HELP will give you a list of the legal answers.
DISC NAME: DISC-70-MB-1

Data way to disc system 1 tested.
Memory address register on disc system 1 tested.
Memory buffers initialized.
The command HELP gives you a list of the commands.

FORMAT¶

Unit (0-3 Oct.):	1
FORMAT	Make sure that the disk you want to format is placed in this unit.

The previous content will be destroyed on
DISC system: 1 Unit: 1

Do you still want to continue (Yes/No): Y

To give you a chance to cancel.

Norsk Data ND-30.003.7 EN

Page 176¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

Example continued¶

The tracks to be reallocated must be specified.
(According to the manufacturer's list.)

Input by Cylinder or Surface: CYLINDER

Cylinder	(0-822 Dec.): Finished

If you do not know about any tracks that need to be reallocated, press CR.

Table of reallocated tracks is empty.
Do you want to edit the table (Yes/No): N

No. of re-allocated tracks (dec.): 0
No tracks in the spare-track pool are used.
The pool will therefore be formatted with the standard format.

If a track fails later on you still have the whole spare track pool free, so a reformatting can be done.

The formatting takes about 5 - 6 seconds per MB, with 3 comparisons of data (default).

>OPCOM

MACL	LOAD
Carry out a warm start of the computer.

Norsk Data ND-30.003.7 EN

Page 177¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

4.2.3 Entering and releasing directories¶

When a disk pack or a floppy diskette is put on a disk unit, the directory on it must be entered. This is done by the command:

@ENTER-DIRECTORY (<directory name>) <device name> <device unit> [<fixed=F/removable=R>] [<sub-unit>]

The parameters have the same meaning as in the command @CREATE-DIRECTORY. The first directory entered automatically becomes a main and default directory. If the specified name matches the name found on the device, the directory is entered, otherwise an error message is given. The default directory name is the one found on the disk.

Example of entering a floppy diskette directory¶

@ENTER-DIRECTORY FLOPPY-PACK,FLOPPY-DISC-1,1

If you did not know the directory name, just type:

@ENTER-DIRECTORY,,FLOPPY-DISC-1,1

Use the following command to set an entered directory as default directory:

@SET-DEFAULT-DIRECTORY <directory name>

If a directory is not a default directory, the directory name must be given as a prefix, when accessing files on it. This is also the case if a user area has space in more than one default directory.

The command:

@SET-MAIN-DIRECTORY <directory name>

A system can have up to 16 main directories, each with a maximum of 256 user names. It is thus possible to have 4096 different user names in one system. All user areas must be defined in a main directory in order to access files on other directories where they are also defined. They need not have space in the main directory. A floppy diskette directory cannot be set as a main directory.

Norsk Data ND-30.003.7 EN

Page 178¶

Example of entering a main directory¶

To enter a directory called PACK-TWO on the 70MB FSD disk, and set it as main, you can type:

@ENTER-DIRECTORY PACK-TWO,DISC-70MB-1,1
@SET-MAIN-DIRECTORY PACK-TWO

The command @ENTER-DIRECTORY is one way to define a mass storage device in the directory table. Another way to define a mass storage device in the directory table is:

@DEFINE-MASS-STORAGE-UNIT <device name> <device unit> [<fixed=F/removable=R>] [<sub-unit>]

The parameters are as for the @ENTER-DIRECTORY command. On standard versions of SINTRAN VSK K, devices are not placed in the directory table when they are generated. Mass storage devices that are going to be accessed as volumes must be defined in the directory table before they can be used. It is recommended that this command be included in the warm-start procedure to take care of defining magnetic tape drives and floppy drives.

Example of defining a floppy unit in the directory table¶

@DEFINE-MASS-STORAGE-UNIT FLOPPY-DISC-1 1

A directory must be released before the disk pack or floppy diskette is removed from the disk drive. The directory can only be released if none of the files on it are opened, and no users are logged in with this directory as their main or default directory. The command to use is:

@RELEASE-DIRECTORY <directory name>

After the directory is released, it can be entered again, or another disk can be mounted on the disk drive. The directory can also be entered on another ND computer.

Users sometimes forget to release a directory on a floppy diskette, before taking it out. In such cases, install any other floppy diskette with a directory and give the @RELEASE-DIRECTORY command.

Norsk Data ND-30.003.7 EN

Page 179¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

The following command is used to rename an entered directory (the directory must be released before renaming it):

@RENAME-DIRECTORY ()
[] []

The effect of the following commands on the directory table is the reverse of that of the commands described earlier in this section:

@CLEAR-DEFAULT-DIRECTORY

@CLEAR-MAIN-DIRECTORY

@DELETE-MASS-STORAGE-UNIT
[] []

CAUTION!
If you enter a directory used from the K-version of SINTRAN to a computer running an older SINTRAN version, please note the following:
● All files with a file number greater than 255 become invisible, but they are still present on the disk. They reappear when you move them back to the K-version.
● The commands @REGENERATE-DIRECTORY and @TEST-DIRECTORY must not be used if any user area has files with a file number greater than 255.

4.2.4 Retrieving information about directories¶

Some commands are used to retrieve information about directories. The commands @LIST-DIRECTORIES-ENTERED () () and
@DIRECTORY-STATISTICS () ()
give information about directories. The first command lists the names of the entered directories matching the directory name parameter. Default is all directories. The second command lists more detailed information about the directories matching the name parameter. It

Norsk Data ND-30.003.7 EN

Page 180¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

takes some time to execute the command because it has to check several items of file-system information on the directory.

These command are, like other statistical commands, available to all users, but are of special interest to the system supervisor.

Example of retrieving information about a directory¶

@DIRECTORY-STATISTICS PACK-ONE,,

DIR INDEX 0 : DISC-70MB-1 UNIT 0 : PACK-ONE
(MAIN AND DEFAULT DIRECTORY)
2 PAGES UNRESERVED AND 3456 PAGES UNUSED OUT OF 34765 PAGES
MAXIMUM UNUSED CONTIGUOUS AREA ON DIRECTORY 131 PAGES

Index in directory table, device name etc, and directory name

The directory has only two pages that have not been given to any user-area. At least two pages must be left free in the directory for temporary use by the file system.

The maximum size of a contiguous file that can be created on this directory is 131 pages.

The command to list the mass storage devices already defined in the directory table is:

@LIST-MASS-STORAGE-UNITS (<output file>)

Example of directory table¶

@LIST-MASS-STORAGE-UNITS,,

DIR INDEX 0 : DISC-70MB-1 UNIT 0
DIR INDEX 1 : DISC-70MB-1 UNIT 1
DIR INDEX 40 : FLOPPY-DISC-1 UNIT 0

Floppy disk units are usually placed at the end of the table.

Norsk Data ND-30.003.7 EN

Page 181¶

4.3 Administering user areas and disk space¶

The System Supervisor is responsible for creating and deleting SINTRAN user areas and giving them disk space. Ordinary users are only allowed to do this on floppy diskettes. The number of pages available on a physical disk medium is limited. It is necessary to plan carefully when sharing these pages between user areas. The System Supervisor is also responsible for creating and maintaining User Environment users (see the User Environment Reference Manual (ND-60.194)).

4.3.1 Creating and deleting user areas¶

A new user area is created and given disk space by giving the commands:

@CREATE-USER <[directory:]user name>

@GIVE-USER-SPACE <[directory:]user name>

A user area must exist in the directory before it can be given any space. It must also exist in a main directory. If the directory name is omitted in the above command, the executing user's main directory is assumed. When a user area is created, it has no password. After the user area is created in the directory it can be included in the User Environment as an alternative user area.

The following example creates a new user area-named DOMINO. The user area is given 500 pages of user space in the directory PACK-TWO. PACK-TWO is not a main directory in this example. The only main directory is PACK-ONE.

Example of creating and giving a user area space
@CREATE-USER	Create the user area in the
USER NAME: DOMINO	main directory first.
@CREATE-USER
USER NAME: PACK-TWO:DOMINO
@GIVE-USER-SPACE	Do not forget to specify
USER NAME: PACK-TWO:DOMINO	which directory the user area
NUMBER OF PAGES: 500	shall be given space on.

Norsk Data ND-30.003.7 EN

Page 182¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

If a user area already has file space when the @GIVE-USER-SPACE command is entered, the file space will be increased by the number of pages given. If there are not enough unreserved pages in the directory, an error message is given.

To remove a user area from the directory, you use the following command:

@DELETE-USER <[directory name:]user name>

If you attempt to delete a user area with files in the specified directory, an error message is displayed and the user area is not removed.

Assume that the owner of user area DOMINO has created files in directory PACK-TWO and is moving to another computer, taking along the disk PACK-TWO. The user area can then be deleted in the main directory.

Example of deleting a user area that has no space in main directory¶

@DELETE-USER
USER NAME: DOMINO

User DOMINO must be created in a main directory on the other computer and the disk pack set as a main directory or the user name DOMINO renamed to one existing in the other computer. The following examples show the possibilities:

Example of moving a disk pack to another ND computer¶

Command	Description
@ENTER-DIRECTORY PACK-TWO DISC-70MB-1 1	Creating DOMINO in the main directory on the host computer.
@CREATE-USER PACK-ONE:DOMINO
or:
@ENTER-DIRECTORY PACK-TWO, DISC-70MB-1 1	Define the directory as a main directory.
@SET-MAIN-DIRECTORY PACK-TWO
or:
@ENTER-DIRECTORY PACK-TWO, DISC-70MB-1 1	Rename DOMINO to an existing user name on PACK-ONE.
@RENAME-USER PACK-TWO:DOMINO SOMETHING-ELSE

Norsk Data ND–30.003.7 EN

Page 183¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

Unused pages can be taken from a user area by giving the command:

@TAKE-USER-SPACE <[directory name:] user name>

The command assumes the specified user area's main directory, if no directory is specified. It is not possible to take away pages that are already in use by files. The files must first be deleted. If you are going to delete a whole user area with many files, you are advised to take a backup of it first (e.g. onto floppy diskettes). This ensures that valuable files are not lost unintentionally.

4.3.2 Defining file access and the number of files that can be created¶

When a user area is created, it gets a default file access to be used on files that are created. The default file access is specified by giving the command:

@SET-INITIAL-FILE-ACCESS

All file-access parameters in commands are specified by a combination of the codes: R W A C D or N - None (no access at all).

Norsk Data ND-30.003.7 EN

Page 184¶

File Access Codes¶

Access code	Explanation
R (Read)	The file can be opened for read by one or more users simultaneously.
W (Write)	The file can be opened for write by one user at a time. See also the code "C".
A (Append)	Only used as a qualifier to "W" for indexed files. The file is allowed to increase dynamically when necessary.
C (Common)	Only used as a qualifier to contiguous files with write access. Such a file can be opened for write by several users simultaneously.
D (Directory)	Attributes in the description of the file can be manipulated, i.e. the file can be renamed or deleted.
N (None)	No access rights at all. This is sufficient to perform statistical commands on your own files.

Table 10. File access codes

When a user area is created, it is also given friend access to be used by other user areas created by the command ©CREATE-FRIEND. Initial friend access is specified by giving the command:

A friend's access to any file is always the least common denominator of the friend-access and the file-access. A friend-access of RWA, for example, to a file with access RD would only give access R. It is therefore quite possible to have friends with less access rights to a file than public users without friend-access.

The commands for setting initial file access should be included in the HENT-MODE mode file because the commands must be repeated after each cold start. The default file access can be changed for each user area individually by the command ©SET-DEFAULT-FILE-ACCESS and ©SET-FRIEND-ACCESS. These are public commands that permit users to define the default file-access codes themselves. Information about user areas is retrieved by giving the command @USER-STATISTICS.

Norsk Data ND-30.003.7 EN

Page 185¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

Example of setting initial file-access codes¶

@SET-INITIAL-FILE-ACCESS R,RWA,RWAD

@SET-INITIAL-FRIEND-ACCESS RWAD

@CREATE-USER PACK-ONE:A-BRAND-NEW-USER

.. Logging in on the new user area ..

@CREATE-FRIEND SYSTEM

@USER-STATISTICS A-BRAND-NEW-USER,

USER 29 : PACK-ONE: A-BRAND-NEW-USER
    CREATED <date created>
    LAST DATE ENTERED <date logged in>
    DEFAULT PUBLIC ACCESS : READ
    DEFAULT FRIEND ACCESS : READ, WRITE, APPEND
    DEFAULT OWN ACCESS : READ, WRITE, APPEND, DIRECTORY

Affected by the command @SET-INITIAL-FILE-ACCESS

@LIST-FRIENDS,1

FRIEND 0 : SYSTEM
    ACCESS : READ, WRITE, APPEND

Affected by the command @SET-INITIAL-FRIEND-ACCESS

In previous versions of SINTRAN, no more than 256 files were allowed in each user area. In SINTRAN version K, it is possible to have as many as 4096. This is achieved by dividing the 4096 files into 16 object blocks of 256 objects (files) each. New object blocks can be allocated for the user area when needed.

In order to speed up file searching, the number of files each user is allowed to create is initially restricted to 256. If a user needs more files, use the command:

@GIVE-OBJECT-BLOCKS (<directory name:> user name)
<number of object blocks>

This command is restricted to user SYSTEM unless the directory resides on a floppy diskette. The number of object blocks is added to the object blocks already given to the user area (initially 1). The last line output from the @USER-STATISTICS command tells how many files a user area is allowed to have, for example:

MAXIMUM NUMBER OF FILES : 512

Norsk Data ND-30.003.7 EN

Page 186¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

All the versions of a file that are created must have file numbers within the same object block interval (e.g. 0..255, 256..511 and so on).

If you need to reduce the number of files a user is able to create, you use the following command:

@TAKE-OBJECT-BLOCKS <[directory name:] user name> <number of object blocks>

The first object block (file numbers 0..255) cannot be "taken". The object blocks to be removed must not contain any used file numbers. If for example a user allowed to have 512 files has created 257 files (file numbers 0..256) and later deletes all files except the one with file number 256, both object blocks will still be in use.

Example of increasing the number of files a user can have.
@CREATE-USER PACK-ONE;FILE-CONSUMER
@GIVE-OBJECT-BLOCKS PACK-ONE;FILE-CONSUMER 1
@USER-STATISTICS FILE-CONSUMER1:
....................................................................
MAXIMUM NUMBER OF FILES : 512

Norsk Data ND-30.003.7 EN

Page 187¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

4.3.3 Scratch files¶

Scratch files are temporary files, used to hold data while it is being processed. When, for example, you read a file into NOTIS-WP or PED, the whole file is copied onto the scratch file before the program continues (-WAIT- is displayed in the top right-hand corner of the screen). When you store a file, the opposite happens: the contents of the file are copied from the scratch file to the specified file. Many applications make use of scratch files. Each background program needs a scratch file (terminal, batch processor and TAD). All scratch files are "owned" by user SCRATCH.

SINTRAN opens the scratch file for you automatically when you log in. It always has the logical file number 1008. The scratch files are indexed and, as in the case of other indexed files, they are expanded dynamically when needed. The pages that are given to a scratch file are not released until you log out. Not all of the pages are released when you log out. Some of them remain in the file. The number of pages permanently allocated to the scratch file can be set by giving the SINTRAN Service command:

SET-CLOSED-SCRATCH-FILE-SIZE ()

The default value for this command is 64 pages. It is faster to copy to a scratch file with a large number of permanently allocated pages. However, it is a good policy to keep scratch files small, so that they do not occupy more pages than actually needed.

The number of background processes is printed when SINTRAN is started. You can also find this number by running the S3-Configuration program. A background process always uses the same scratch file. It is a good idea to create more scratch files than currently required, since this simplifies installation of new terminals.

It is difficult to calculate exactly the number of pages required by each scratch file. This always depends on the size of the files that a user works on. This can be anything from a single page to over a thousand pages. It is recommended that user SCRATCH should be given about two hundred pages for each active user (e.g. 10 users * 200 pages = 2000 pages).

Norsk Data ND-30.003.7 EN

Page 188¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

4.3.4 Passwords¶

Users create and change their own passwords by the @CHANGE-PASSWORD command. The password of any user area can be removed by user SYSTEM. To clear a password, use the command:

@CLEAR-PASSWORD <user name>

There is at least one reason why user SYSTEM might need to clear a user area's password: If a user has forgotten the password for his/her user area and give you permission to clear it.

If you need to clear a password without the knowledge of the owner of the user area, you must protect the user area by giving it a temporary password immediately. Do not forget to inform the user about what you have done.

NEVER leave a user area without a password!

If you must access files on other user areas protected by passwords, this is best solved by requesting the user to:

create user SYSTEM as a friend
set sufficient friend access codes for the files involved

Note that friends must have the same main directory!

The number of unsuccessful attempts to give a correct user name and password when logging in is counted and checked against a limit known as the maximum enter count. This enter count is used to protect the system from unauthorized users. If the number of attempts to log in exceeds the maximum enter count, the terminal will be disabled and the situation reported on the error device. You must correct this error in the SINTRAN Service Program before the terminal can be used again.

The SINTRAN Service Program command to enable a terminal for further use is:

*CLEAR-ENTER-COUNT <terminal number> (<memory?>)

The parameter () should always be answered by "Y" to clear the enter count.

Norsk Data ND-30.003.7 EN

Page 189¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

The command and parameters to define the maximum enter count are:

SET-MAX-ENTER-COUNT [()] () ()

The first parameter gives you the possibility of disabling the enter-count checking when logging in, but this is not recommended. The maximum enter count should be set high enough to allow users to make some typing errors. At the same time, it should be low enough to be of value to data security. A value between 5..20 should in most cases be reasonable.

Helping a user who gets "too many attempts to enter"¶

Suppose this happens on terminal 51:

| ENTER FINGER-TROUBLE | | PASSWORD: TYPING-ERRORS |

*** TOO MANY ATTEMPTS TO ENTER ***

| The user is unable to make any more attempts to log in. |

@SINTRAN-SERVICE-PROGRAM

CLEAR-ENTER-COUNT 51D Y

Norsk Data ND-30.003.7 EN

Page 190¶

SINTRAN III SYSTEM SUPERVISOR FILE SYSTEM SUPERVISION¶

4.4 Efficient Directory and File Organization (ADVANCED)¶

This section gives eight rules to be used when creating directories and user areas. Efficient use of the file system will improve the system performance. The first seven rules will help to speed up the searching for files and user descriptions. Some of this guidance applies only to large computer installations with several directories.

The eight SINTRAN III file system rules for good organization:

Do not have more main directories than you need.
Pack the user areas on the main directories so that successive object entries are used. This will improve the speed of searching for user areas.
Do not have more default directories than you need or can use.
Never define a user area in more than one main directory, unless it is absolutely unavoidable.
Change the order of the directory entries in the directory table so that directory index 0 is the main directory with users SYSTEM, SCRATCH, RT and others whose files are most frequently used.
The standard user areas BPUN-FILES and FLOPPY-USER are only used now and then, and they should therefore be the last ones to be created.

The command @DEFINE-MASS-STORAGE-UNIT reserves the first free entry in the directory table. You thereby control the order of the directory indexes. The command can only be used in standard systems of SINTRAN VSX. The SINTRAN Service Program command SWAP-DIRECTORY-ENTRIES can be used in other configurations for the same purpose.
Specify file names in full to speed up file searching (including directory name) when running mode or batch jobs.
Directory and file searching becomes faster. See also rule 6.
Do not give directory or user name when accessing files on your default directory.
Such information slows down the access time. This applies to all types of work.
Organize the users' files so that those accessed most frequently have the lowest file number.
The @FILE-STATISTICS command gives the number of times a file has been opened.
Only store files related to the operation of the computer on user SYSTEM.
Create personal user areas for other things.

Norsk Data ND-30.003.7 EN

Page 191¶

4.4.1 Two examples of directory organization¶

The first example is a company that has an ND-110/CX COMPACT computer with two internal 45 MB disks. The user areas and their disk-space requirements are as follows.

SYSTEM: 10000 pages.
SCRATCH: 2500 pages, RT: 100 pages, NOTIS: 600 pages, BPUH-FILES: 1700 pages, UTILITY: 1000 pages.
BASE, a user area for the database files: 5000 pages.
CLERK-1 .. CLERK-5, five clerks dealing with the accounting ledgers. No pages, only the database is used.
WAGES-1 .. WAGES-2, two wages clerks. No pages.
COSTING-1 .. COSTING-5, five clerks dealing with job costing. Each has 500 pages.
STOCKCONTROL-1 .. STOCKCONTROL-3, PRODUCTION-1 .. PRODUCTION-3, six more clerks dealing with stock control and production. No pages.
SECRETARY-1 .. SECRETARY-3, three secretaries, each using NOTIS-WP and some other ADP applications. They use the file system facilities frequently throughout the day. Each has 1500 pages of file space.
The source code of the database applications is kept under user SOURCE. These files are accessed about once per week and occupy 3000 pages.
A further three user areas, APPLIC-1, APPLIC-2 and APPLIC-3 have file space for developing application programs, documentation and general use of subsystems. They use the system nearly every day, but their use is not heavy. They each have 2000 pages of file space.
One manager uses ADP applications now and then for decision making and statistical purposes. The use is occasional and not heavy. She has 1000 pages of file space.

The two directories available, each with 22032 pages are organized as shown in table 11.

Page 192¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

Directory index	User index	User names	Number of pages	Notes
0	0	SYSTEM	10,000	Main and default directory.
	1	SCRATCH	2,500
	2	RT	100
	8	BASE	5,000
	3	COSTING-1	500
	4	COSTING-2	500
	5	COSTING-3	500	All user areas are defined here.
	6	COSTING-4	500
	7	COSTING-5	500
	9	CLERK-1	0
	10	CLERK-2	0
	11	CLERK-3	0
	12	CLERK-4	0
	13	CLERK-5	0
	14	WAGES-1	0
	10	WAGES-2	0
	11	STOCKCONTROL-1	0
	12	STOCKCONTROL-2	0
	13	STOCKCONTROL-3	0
	14	PRODUCTION-1	0
	15	PRODUCTION-2	0
	16	PRODUCTION-3	0
	17	PRODUCTION-3	0
	18	SECRETARY-1	0
	19	SECRETARY-2	0
	20	SECRETARY-3	0
	21	APPLICS-1	0
	22	APPLICS-2	0
	23	APPLICS-3	0
	24	DIRECTOR	0
	25	BPUN-FILES	0
	26	UTILITY	0
	27	NOTIS	0	In total: 20,100 pages

Directory index	User index	User names	Number of pages	Notes
1	0	SECRETARY-1	1,500	Default directory
	1	SECRETARY-2	1,500
	2	SECRETARY-3	1,500
	3	APPLICS-1	2,000
	4	APPLICS-2	2,000
	5	APPLICS-3	2,000
	6	DIRECTOR	1,000
	7	UTILITY	1,000
	8	NOTIS	600
	9	BPUN-FILES	1,700	In total: 14,800 pages
	10	FLOPPY-USER	0

Table 11. Example of directory organization of a small system

Norsk Data ND-30.003.7 EN

Page 193¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

The second example concerns a university that has an ND-570/CX computer with several directories; two sub-divided 4 x 70MB FSD disks (8 directories) and two 70MB RSD disks (2 directories). Altogether mounted in a filestore cabinet. The following user areas with the stated space requirements are arranged on the following 10 directories:

SYSTEM: 23,500 pages.
SCRATCH: 8000 pages, RT: 300 pages, UTILITY: 1000 pages, BPUN-FILES: 1000 pages for ND-100 programs.
DOMAINS: 5000 pages for ND-500 programs.
ANALYST-1 .. ANALYST-5: Five system analysts making constant use of the system, each requiring 1500 pages.
POSTGRAD-1 .. POSTGRAD-200: Two hundred postgraduate students, each requiring 500 pages.
STUDENT-3-1 .. STUDENT-3-200: Three hundred final year students, each requiring 300 pages.
STUDENT-1 .. STUDENT-500: Five hundred first and second-year students, each requiring 150 pages.

Apart from user SYSTEM, SCRATCH, and ANALYST-1 .. ANALYST-5, the other user areas will have roughly equal use. The only important point to note is that students in a class will sometimes be making intense use of the machine simultaneously, and it is thus advisable to group student classes so that all user area entries for students in a class lie on the same page.

The ten directories available, each with 34765 pages, should be organized as shown in table. 12.

Norsk Data ND-30.003.7 EN

Page 194¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

Directory index	User index	User names	Number of pages	Notes
0	0	SYSTEM	23,500	Main and default directory
	1	RT	300
	2	SCRATCH	8,000
	3	UTILITY	1,000	(DISC-70MB-1, UNIT 0)
	4	BPUN-FILES	1,000
	5	ANALYST-1	0
		. . . . . .	0
	9	ANALYST-5	0
	10	STUDENT-3-1
		. . . . . .
	209	STUDENT-3-200	0	In total:
				33,800 pages
1	0	POSTGRAD-1	500	Main and default directory
		. . . . . .
	39	POSTGRAD-40	500	(DISC-70MB-1, UNIT 1)
	40	POSTGRAD-41	0
		. . . . . .
	199	POSTGRAD-200	0
	200	ANALYST-1	1,500
		. . . . . .
	204	ANALYST-5	1,500	In total:
	205	DOMAINS	5,000	32,500 pages
2	0	STUDENT-1	150	Main and default directory
		. . . . . .		(DISC-4-70MB-1 UNIT 2, SUB 0)
	149	STUDENT-150	150
	150	STUDENT-151	0
		. . . . . .		In total:
	249	STUDENT-250	0	22,500 pages
3	0	STUDENT-251	150	Main and default directory
		. . . . . .		(DISC-4-70MB-1 UNIT 2, SUB 1)
	149	STUDENT-400	150
	150	STUDENT-401	0
		. . . . . .		In total:
	249	STUDENT-500	0	22,500 pages

Norsk Data ND-30.003.7 EN

Page 195¶

SINTRAN III SYSTEM SUPERVISOR¶

FILE SYSTEM SUPERVISION¶

Directory index	User index	User names	Number of pages	Notes
4	0	POSTGRAD-41	500	Default directory (DISC-4-70MB-1 UNIT 2, SUB 2) In total: 30,000 pages

	59	POSTGRAD-100	500

5	0	POSTGRAD-101	500	Default directory (DISC-4-70MB-1 UNIT 2, SUB 3) In total: 30,000 pages

	59	POSTGRAD-160	500
6	0	POSTGRAD-161	500	Main and default directory (DISC-4-70MB-1 UNIT 3, SUB 0) In total: 20,000 pages

	39	POSTGRAD-200	500
7	0	STUDENT-3-1	300	Default directory (DISC-4-70MB-1 UNIT 3, SUB 1) In total: 30,000 pages

	99	STUDENT-3-100	300
8	0	STUDENT-3-101	300	Default directory (DISC-4-70MB-1 UNIT 3, SUB 2) In total: 30,000 pages

	99	STUDENT-3-200	300
9	0	STUDENT-151	150	Default directory (DISC-4-70MB-1 UNIT 3, SUB 3) In total: 30,000 pages

	99	STUDENT-250	150
	100	STUDENT-401	150

	199	STUDENT-250	150

Table 12. Example of directory organization of a large system

Norsk Data ND-30.003.7 EN

Page 196¶

Page 197¶

Chapter 5: COSMOS Basic Module Operations¶

This chapter documents the installation and operation procedures of the network facilities in the COSMOS Basic Module (ND-210374) as implemented under SINTRAN III version K. You should already be familiar with the COSMOS concept from the end user's level. Such documentation is found in the manual COSMOS User Guide (ND-60.163).

The facilities of IS XMSG that are needed to operate and run the COSMOS Basic Module are only briefly described in this manual. The XMSG-COMMAND program is used for control and definition of network routing in XMSG. When the network routing is done, all computers are identified with a unique system name and system number.

5.1 Survey¶

COSMOS is ND's distributed data communications environment. It provides communication and application services to augment the user services provided by SINTRAN III.

The COSMOS Basic Module provides the services necessary to run a minimal local area network (LAN) with several systems (computers) interconnected. The basic services are CONNECT-TO, File Transfer, COSMOS Spooling and Remote File Access. Additional options can be added.

5.1.1 Prerequisites to use the COSMOS BM¶

The COSMOS BM can be run on all ND computers that have a ND-100 CPU.


HARDWARE	One or more communication interfaces of type HDLC or MEGALINK.
XMSG	The K version of XMSG IS.
COSMOS BM	The D version.
SINTRAN	The K version.

The installation of COSMOS BM requires 472 unused pages divided between 20 files.

Norsk Data ND-30.003.7 EN

Page 198¶

SINTRAN III SYSTEM SUPERVISOR¶

COSMOS BASIC MODULE OPERATIONS

You should read the PD-sheets for COSMOS BM before installing it. The examples of mode files used for start and stop of the system in appendix H include COSMOS BM. Remember that XMSG also must be present.

5.1.2 Defining the network routing¶

After XMSG has been started in a warm start, all network routing must be done. This is because tables containing network definitions are emptied when XMSG is stopped. The mode file XMSG-START (normally found on user UTILITY) must be tailored to handle the network routing.

Example of the XMSG-START file for HDLC and Megalink¶

Code Snippet	Description
@CC XMSG STARTUP MODE FILE FOR ND-6887
@SINTRAN-SERVICE
@STOP-XMSG
@EXIT
@&(UTILITY)XMSG-COMMAND	This program communicates with the kernel parts of XMSG.
DEFINE-REMOTE-NAME,MY-COMPUTER,6887
DEFINE-REMOTE-NAME,PARTNER-1,6888
DEFINE-REMOTE-NAME,PARTNER-2,6889	Names and routes for all computers accessible from this one (MY-COMPUTER).
DEFINE-REMOTE-NAME,NODE,6890
....
DEFINE-SYSTEM-ROUTE,PARTNER-1,NODE
DEFINE-SYSTEM-ROUTE,PARTNER-2,NODE
....
START-LINK,1360,...-1,
LIST-LINKS,...	Start software handling the hardware connections (HDLC or Megalink).
EXIT

Instead of referencing remote computers by system numbers, they are given a symbolic name to be stored in a name table. These names are used by both the users and the applications programs. It is very important that the system numbers are the correct ones (found by using the @LIST-TITLE command).

The next step is to define the routes to the different remote systems. The network architecture of the previous example is as shown in figure 34.

Norsk Data ND-30.003.7 EN

Page 199¶

SINTRAN III SYSTEM SUPERVISOR¶

COSMOS BASIC MODULE OPERATIONS¶


MY-COMPUTER	Local system
↓	(direct link to neighbour)
NODE	Neighbour remote system
........	........ (invisible part of network)
PARTNER-1	PARTNER-2 Remote systems

Figure 34. A small network using HDLC or Megalink

When defining the routes to remote systems, it is not necessary to define routes to the adjacent systems in the network. Only routes for the systems that shall be "visible" from the local systems need to be defined. By adjacent system is meant the system to which the local system has a direct link (physical connection). The command to be used for HDLC and Megalink routing is:

X-C: DEFINE-SYSTEM-ROUTE () ()

The first parameter is the name of the system the route shall be defined from. Default is your local system which you are currently working on. Parameter 2 is the name of the remote system that the local system shall have access to. The last parameter is the system name of the local system's neighbour which the remote system is accessed via. There must be a link between the local system and this neighbour system. Default is NONE, which means there is a direct link between the local and remote systems.

Norsk Data ND-30.003.7 EN

Page 200¶

Example of the XMSG-START file for Ethernet¶

@CC    ** XMSG STARTUP MODE FILE FOR ND-6887 ***

@SINTRAN-SERVICE
@STOP-XMSG
@EXIT

@<UTILITY>XMSG-COMMAND

DEFINE-REMOTE-NAME,.MY-COMPUTER,6887
DEFINE-REMOTE-NAME,.PARTNER-1,6888
DEFINE-REMOTE-NAME,.PARTNER-2,6889

Names for computers to be accessible from local system.

START-NETWORK-SERVER ENNSO,.,N
DEFINE-NETWORK-CONNECTION,.PARTNER-1,ENNSO
DEFINE-NETWORK-CONNECTION,.PARTNER-2,ENNSO

EXIT

Start network server for Ethernet. The server name is configuration dependent (see PD-sheets). Define connections to the remote systems accessible from this computer.

The network architecture when using Ethernet is as shown in figure 35.

+-------------+    +-----------+    +-----------+
| MY-COMPUTER |----| PARTNER-1 |----| PARTNER-2 |
+-------------+    +-----------+    +-----------+
   |               Ethernet cable             |

Figure 35. A small Ethernet network

Norsk Data ND-30.003.7 EN

Page 201¶

SINTRAN III SYSTEM SUPERVISOR¶

COSMOS BASIC MODULE OPERATIONS¶

5.2 The Connect-To Service program and TADs¶

The Connect-To program should be dumped reentrant in order to make it easy to start for the users.

5.2.1 The SINTRAN TAD commands¶

There are three SINTRAN TAD commands you need to know. They are:

@TADADM

@START-TADADM

@STOP-TADADM

The SINTRAN command @TADADM tells you the status of each Terminal Access Device (TAD):

Example of TAD information¶

MY-COMPUTER@TADADM

TAD/TYP	RESERV	ESCAP	PORTNO	- PORTNO	TERMTNO	USER	SYSTEM
768/ O	BAK14	Enab	14	13	42	UTILITY	SCHOLAR
769/ O	BAK03	Enab	10	-	This TAD has no corresponding PAD.
770/ 0	No	Enab	Discon	-
771/ 0	BAK05	Enab	12	9	50	SYSTEM	SOUTH
772/255	BAK08	Enab	7	6	FS Administrator
773/ 0	No	Disab	Discon	-

| Local system information. | Remote system information, except where is given. |

Norsk Data ND-30.003.7 EN

Page 202¶

SINTRAN III SYSTEM SUPERVISOR¶

COSMOS BASIC MODULE OPERATIONS¶

The information on the left is local-system information (the computer where you gave the TADADM command). The TADs are numbered from 768 and up, their type ("TYP") is 0. Each TAD being used needs a background program to be able to work. The background programs for the TADs are taken from the same pool as those used for the ordinary terminals.

TADs not in use should look like TAD 770 above, while each TAD being used for a File Server should look like 772 above. File Servers are controlled by the RT program TADAD on the local computer.

The column "ESCAP" tells you whether or not the escape function is enabled on the TADs. The command @ENABLE-ESCAPE-FUNCTION is used to enable the escape function for both terminals and TADs. This can be useful when it becomes impossible to disconnect from a remote system.

The column "PORTNO" tells you the XMSG port numbers in use, the local port numbers at the left side and the remote at the right side.

The remote system information includes also "TERMNO" (terminal number), "USER" (user name) and "SYSTEM" (computer name) for the system where the users are connected from, i.e. their local system.

MY-COMPUTER	SCHOLAR
(local system)	(remote system)
TAD administrator	User UTILITY

TAD 768	TERM 42
(virtual connection)
XMSG port 14	XMSG port 7

Figure 36. Example of interconnection in the Connect-To system

Note that in the TAD information example TAD 769 has no Peripheral Access Device (PAD):

Example of a hanging TAD
769/0 BAK03 Enab 10 - This TAD has no corresponding PAD.

Norsk Data ND-30.003.7 EN

Page 203¶

SINTRAN III SYSTEM SUPERVISOR¶

COSMOS BASIC MODULE OPERATIONS¶

Under certain circumstances this error situation occurs. When it happens, the TAD cannot be used until you correct the error by using the RECONNECT-TAD command (explained later).

The purpose of the START-TADADM command is to make the TAD service available, making it possible to log on a TAD from a remote system. The TAD Administrator is started. The command should normally be found in the SINTRAN LOAD-MODE file. Only user SYSTEM can give it.

Starting the TAD Administrator¶

Command
@START-TADADM

When the @STOP-TADADM command is executed, it will no longer be possible to log on any of the unused TADs. The operation of active TADs is not, however, affected. Only the TAD Administrator stops.

Users who try to log on a TAD when TADADM has been stopped, receive the error message, 'Remote terminal access not running on \<remote system name>'.

This can be used to improve the data security in your system. The TAD Administrator can for example be stopped during nights, weekends and holidays to prevent unauthorized persons from logging in.

Stopping the TAD Administrator¶

Command
@STOP-TADADM

5.2.2 The Connect-To Service program¶

The Service program of the Connect-To are described in this section. You select the Service program by typing:

Entering the Connect-To Service program¶

Command
@CONNECT-TO

COSMOS CONNECT-TO PROGRAM VERSION - D, JUNE 03, 1986
C-T: SERVICE-PROGRAM

CONNECT-TO service-program - Version D.
CT-SERV:

Norsk Data ND-30.003.7 EN

Page 204¶

SINTRAN III SYSTEM SUPERVISOR¶

COSMOS BASIC MODULE OPERATIONS¶

If you want to fix a TAD without a PAD (Peripheral Access Device) or connect to a specific TAD, use:

RECONNECT-TAD <TAD logical unit number> <system name> <password>

The command is only available for user SYSTEM. For example, you want to reserve the TAD 774 on the system SOUTH:

Example of reserving a TAD¶

CT-SERV: RECONNECT-TAD
TAD LOGICAL UNIT NO: 774
SYSTEM-NAME: SOUTH
Specify system-password for system: SOUTH please:
=== CONNECTION ESTABLISHED ===
TAD LOGICAL UNIT NO: 774
You have got the TAD.

ESC

SINTRAN III - VSX K SOUTH
ENTER SYSTEM
PASSWORD: {invisible}
OK
SOUTHE

You have now reconnected the TAD by using it yourself. This can be useful to correct a situation with a hanging TAD ("TAD without a PAD"), or when you need to recover a resource that has accidentally reserved a TAD.

The TAD type that is used when logging in on a remote computer is controlled by:

CHANGE-CONNECT-TYPE <new TAD type>

The TAD type is by default 0 for the Connect-To program. User RT and SYSTEM are allowed to use the command. Other parts of COSMOS that use TADs have different TAD types for identification. You are advised not to change the TAD type in the present version of Connect-To (future extension).

Norsk Data ND-30.003.7 EN

Page 205¶

SINTRAN III SYSTEM SUPERVISOR¶

COSMOS BASIC MODULE OPERATIONS

If you want to change timeout values concerning inactive use of TADs for your system, use:

SET-TIMEOUT-VALUES () ()

The <not logged in> value applies when you have connected to a remote system, but not yet logged in. The default value is one minute. The <not active> value you give determines how long you can remain inactive after having logged in on the remote system. Default here is 30 minutes. When a timeout occurs, COSMOS disconnects the inactive user from the network. Reasonable values should be selected.

Changing timeout values¶


CT-SERV: SET-TIMEOUT-VALUES
NOT LOGGED IN: 2	2 min. before logged in.
NOT ACTIVE: 10	10 min. inactive after logged in.

You can change these values for everyone on your system who uses Connect-To, but then you must also give the DUMP-PROGRAM command. An example of this is given later.

In addition to changing the timeout values, you can also disable them totally by giving the command:

TIMEOUT-OFF

The result of this command, which can only be used by user RT or user SYSTEM, is that, once you connect to a remote system, you will not be disconnected however long you are inactive. The DUMP-PROGRAM must be used to change this permanently for all users.

Disabling the timeout¶


CT-SERV: TIMEOUT-OFF
CT-SERV: EXIT
CT:: LIST-TIMEOUT-VALUES	You see whether timeout is on or off.
TIMEOUT OFF

This will prevent you from being disconnected due to either type of timeout.

Use this to restore your timeout values to the default values for your system:

TIMEOUT-ON command

Norsk Data ND-30.003.7 EN

Page 206¶

SINTRAN III SYSTEM SUPERVISOR¶

COSMOS BASIC MODULE OPERATIONS¶

The local character used for disconnecting from a remote computer can be redefined. The default local character is CTRL-@ (ASCII 0). Redefining the local character is done as follows:

Changing the local character¶

Command	Description
CT-SERV: CHANGE-LOCAL-CHARACTER
ASCII VALUE : 4B	This corresponds to CTRL-D.
CT-SERV: EXIT
CT: LIST-LOCAL-CHARACTER
OCTAL VALUE OF LOCAL CHARACTER: 4

The command DUMP-PROGRAM must be used to make the change permanent and for all users.

When you have connected to a remote system, you are not allowed to enter the Connect-To program there. If you then want to change the local character, use the SINTRAN command:

@DEFINE-LOCAL-CHARACTER (<terminal number>) (<value of local character>)

The default value is your own terminal with local character value 0 (CTRL-@). Only user SYSTEM is allowed to use this command.

The definitions of which categories of SINTRAN users are allowed to execute certain Connect-To commands are controlled by the following commands:

SET-COMMAND-PROTECTION <command> <protection: system/rt/public>

These commands can only be given from user SYSTEM. You can define who can use the different parts of the Connect-To command. For instance, suppose that you only want RT and SYSTEM to be able to dump script programs and you want to allow everyone to reconnect TAD's.

Example of changing the protection for commands¶

Command	Description
CT-SERV: SET-COMMAND-PROTECTION
COMMAND: INITIALIZE-SCRIPT
PROTECTION (SYSTEM, RT OR PUBLIC): RT
CT-SERV: SET-COMMAND-PROTECTION
COMMAND: RECONNECT-TAD
PROTECTION (SYSTEM, RT OR PUBLIC): PUBLIC

Norsk Data ND-30.003.7 EN

Page 207¶

SINTRAN III SYSTEM SUPERVISOR¶

COSMOS BASIC MODULE OPERATIONS¶

If they are to go into effect permanently, these changes must also be dumped. The command should be used with care as it influences data security.

When you use the command:

DUMP-PROGRAM \<program file>¶

you dump the Connect-To program you are currently running to another program file. All redefinitions of commands and parameters that you have made are included in the dumped program.

In this way, you are able to make a new version of Connect-To that reflects your changes. You are advised not to dump the program to the original file COS-CONNECT-TO:PROG unless you have a copy of the original program (e.g. on a floppy diskette).

Example of modifying and dumping a new version of Connect-To¶

@CONNECT-TO

COSMOS CONNECT-TO PROGRAM VERSION - D , JUNE 03, 1986  
C-T: SERVICE-PROGRAM  
CONNECT-TO service-program - Version D.

CT-SERV: SET-COMMAND-PROTECTION  
COMMAND: INITIALIZE-SCRIPT  
PROTECTION (SYSTEM, RT OR PUBLIC): RT

CT-SERV: SET-COMMAND-PROTECTION  
COMMAND: RECONNECT-TAD  
PROTECTION (SYSTEM, RT OR PUBLIC): PUBLIC

CT-SERV: SET-TIMEOUT-VALUES  
NOT LOGGED IN: 2  
NOT ACTIVE: 10

CT-SERV: DUMP-PROGRAM  
PROG-FILE: "NEW-CONNECT-TO"       | A brand new file name.

CT-SERV: EXIT  
C-T: EXIT

Norsk Data ND-30.003.7 EN

Page 208¶

SINTRAN III SYSTEM SUPERVISOR¶

COSMOS BASIC MODULE OPERATIONS

The next step is to make sure that nobody is using Connect-To. You can then give the following commands:

@DELETE-REENTRANT CONNECT-TO
@DUMP-PROGRAM-REENTRANT CONNECT-TO NEW-CONNECT-TO

When users on your system use Connect-To, it will reflect the changes made above. If you want the changes to be permanent, remember also to update the DUMP-REENTRANT file to make the correct version of the Connect-To reentrant. Make sure that the file access for the old version is set to none for public users.

The Connect-To service command DUMP-PROGRAM is also used for dumping script programs.

5.3 The script facility of Connect-To¶

SCRIPT is a feature of Connect-To that allows you to create your own version of Connect-To. For instance, if you often need to log in on a remote system and run a certain program there, you can create a special version of Connect-To that does this for you automatically.

As in the case of the ordinary Connect-To program, you are not allowed to use the CONNECT-TO command from a remote system. This restriction exists for purposes of data security.

We start this section by giving a simple example, and then go on to explain all the SCRIPT features in detail.

Let us suppose that you often need to run a program called QUICK-ACCOUNT on the remote system SCHOLAR. In this example this is done by a SCRIPT called GO-QUICK. By writing @GO-QUICK in SINTRAN, you will automatically be connected to and logged in on SCHOLAR. QUICK-ACCOUNT will be executed. Upon completion, you return to SINTRAN on the local system.

Use PED or another editor to create a document called GO-QUICK:SYMB (use only uppercase letters and 7-bits format!) containing the following lines:

Page 209¶

SINTRAN III SYSTEM SUPERVISOR¶

COSMOS BASIC MODULE OPERATIONS¶

Example of a simple script program¶

*SCRIPT: /SINGLE/ 
   *INPUT: CONNECT-TO SCHOLAR
   *MACRO: LOGIN-DEFAULT /MYSELF/,/FLOPPY-USER...
   *DISPLAY-ON: 
   *INPUT: QUICK-ACCOUNT
*ENDSCRIPT: /SINTRAN/

SCRIPT signals the beginning of a SCRIPT, and ENDSCRIPT marks the end.
The line indentation is just used to increase the readability. A file
can contain several SCRIPTs. /SINGLE/ means that this file only
contains one SCRIPT. /SINTRAN/ means that the user of the SCRIPT will
return to SINTRAN on the local system after the program QUICK-ACCOUNT
has been run.

The four lines starting with the line identifiers INPUT:, MACRO:,
DISPLAY-ON:, and INPUT: make up the SCRIPT body. All script
identifiers are preceded by an asterisk (*) and end with a colon (:).
Extra blanks between parameters etc. are ignored (stripped). The
maximum line length is 128 characters, including blanks.

To create a SCRIPT out of the QUICK-ACCOUNT file:

Initializing and dumping a script¶

MY-COMPUTERøCONNECT-TO

COSMOS CONNECT-TO PROGRAM VERSION - D, JUNE 03, 1986  
C-T: SERVICE-PROGRAM  

CONNECT-TO service-program version D  
CT-SERV: INITIALIZE-SCRIPT  
SCRIPT-FILE: GO-QUICK:SYMB  

   SCRIPT NAME .......... : /SINGLE/  
   CT info status ....... : CT INFO OFF (IN SCRIPT ONLY)  
   Remote command mode .. : NOT ALLOWED  
   Command mode return to : LOCAL COMMAND MODE  

CT-SERV: DUMP-PROGRAM  
PROG-FILE: "GO-QUICK"  
CT-SERV: EXIT  

MY-COMPUTERø

Norsk Data ND-30.003.7 EN

Page 210¶

SINTRAN III SYSTEM SUPERVISOR¶

COSMOS BASIC MODULE OPERATIONS¶

You now have a new file called GO-QUICK:PROG. To execute the SCRIPT, you type:

Starting a script program
MY-COMPUTER@GO-QUICK

You will automatically be connected to SCHOLAR. COSMOS then tries to log you in with the same user name and password as on the local computer. If that does not work, you will be logged in as FLOPPY-USER. Finally, your screen is turned on and the program called QUICK-ACCOUNT started. You return directly to your local computer when this program terminates.

If you merely want to test a SCRIPT program, do not use the DUMP-PROGRAM command because this takes some time; exit to SINTRAN instead. Then do the following:

Simple way of starting an initialized script program
@GOTO-USER 0
The program QUICK-ACCOUNT is run.

If the SCRIPT programs you write are going to be used quite often, you should dump them as reentrant programs.

You may want to include many SCRIPTs in the same SCRIPT program. This will reduce the number of :PROG files. For instance, the program MY-SCRIPTS:PROG could contain SCRIPTs for QUICK-ACCOUNT, FORTRAN-500, ND-500-MONITOR, etc. The user would then type:

Selecting a script in a multi-script program
MY-COMPUTER@MY-SCRIPTS ND-500-MONITOR

Choose short SCRIPT names because they cannot be abbreviated.

Norsk Data ND-30.003.7 EN

Page 211¶

5.3.1 SCRIPT syntax¶

The identifiers allowed in SCRIPTs are listed in table 13.

*SCRIPT:	/SINGLE/
*SCRIPT:	Previous SINTRAN Operations Documentation Next ND 30.049.1 EN SINTRAN III Tuning Guide Made with Material for MkDocs

Spooling	Current	Next	(Input)	Spooling	Current	Next	(Input)
1	5	5	5	2	59	59	59
3	0	0	0	4	0	0	0
5	0	0	0	6	0	0	0
7	0	0	0	8	0	0	0
9	0	0	0	10	0	0	0
11	0	0	0	12	0	0	0
13	0	0	0	14	0	0	0
15	0	0	0	16	0	0	0
17	0	0	0	18	0	0	0
19	0	0	0	20	0	0	0

HDLC	Current	Next	(Input)	HDLC	Current	Next	(Input)
1	1	1	1	2	1	1	1
3	1	1	1	4	1	1	1
5	1	1	1	6	1	1	1
7	0	0	0	8	0	0	0
9	0	0	0	10	0	0	0
11	0	0	0	12	0	0	0
13	0	0	0	14	0	0	0
15	0	0	0	16	0	0	0
17	0	0	0	18	0	0	0
19	0	0	0	20	0	0	0

Spooling	Current	Next	(Input)	Spooling	Current	Next	(Input)
1	5	5	5	2	59	59	59
3	0	0	0	4	0	0	0
5	0	0	0	6	0	0	0
7	0	0	0	8	0	0	0
9	0	0	0	10	0	0	0
11	0	0	0	12	0	0	0
13	0	0	0	14	0	0	0
15	0	0	0	16	0	0	0
17	0	0	0	18	0	0	0
19	0	0	0	20	0	0	0

HDLC	Current	Next	(Input)	HDLC	Current	Next	(Input)
1	1	1	1	2	1	1	1
3	1	1	1	4	1	1	1
5	1	1	1	6	1	1	1
7	0	0	0	8	0	0	0
9	0	0	0	10	0	0	0
11	0	0	0	12	0	0	0
13	0	0	0	14	0	0	0
15	0	0	0	16	0	0	0
17	0	0	0	18	0	0	0
19	0	0	0	20	0	0	0

Page 1¶

SINTRAN III¶

System Supervisor¶

Page 2¶

SINTRAN III¶

Page 3¶

PREFACE¶

The product¶

The reader¶

Prerequisite knowledge¶

Page 4¶

The manual¶

Related manuals¶

Documentation for all configurations:¶

Documentation on specific types of computer:¶

Data communication:¶

Databases and applications using them:¶

Page 5¶

Other documentation (related to SINTRAN or maintenance)¶

Notation used in this manual¶

Page 6¶

Number Systems¶

Word Length¶

Line-Editing Features¶

Command Syntax Conventions¶

Page 7¶

Examples of Different Parameter Types¶

Changes from Previous Version¶

Page 8¶

Contents¶

Appendices¶

List of Code Words¶

Page 9¶

TABLE OF CONTENTS¶

Page 10¶

Section¶

4 FILE SYSTEM SUPERVISION¶

5 COSMOS BASIC MODULE OPERATIONS¶

Page 11¶

Section¶

6 PERIPHERALS AND SPOOLING SUPERVISION¶

7 TAKING BACKUP¶

8 MAIL SUBSYSTEM¶

Page 12¶

9 ACCOUNTING (ADVANCED)¶

10 PREVENTIVE MAINTENANCE AND TEST PROGRAMS¶

11 ERROR SUPERVISING¶

12 PATCHING¶

Page 13¶

Appendices¶

Page 14¶

Page 15¶

LIST OF FIGURES¶

Page 16¶

Title¶

Page 17¶

List of Tables¶

Page 18¶

Page 19¶

SINTRAN III SYSTEM SUPERVISOR¶

SYSTEM SUPERVISION OVERVIEW¶

1.1 Job description for the System Operator¶

1.2 Job description for the System Supervisor¶

Page 20¶

SINTRAN III SYSTEM SUPERVISOR¶

SYSTEM SUPERVISION OVERVIEW¶

Page 21¶

SINTRAN III SYSTEM SUPERVISOR¶

SYSTEM SUPERVISION OVERVIEW¶

1.3 Categories of user area¶

Page 22¶

SINTRAN III SYSTEM SUPERVISOR¶

SYSTEM SUPERVISION OVERVIEW¶

Page 23¶

SINTRAN III SYSTEM SUPERVISOR¶

SYSTEM SUPERVISION OVERVIEW¶

1.4 Software versions required for running SINTRAN III K¶

Page 24¶

SINTRAN III SYSTEM SUPERVISOR¶

SYSTEM SUPERVISION OVERVIEW¶

Spooling	Current	Next	(Input)	Spooling	Current	Next	(Input)
1	5	5	5	2	59	59	59
3	0	0	0	4	0	0	0
5	0	0	0	6	0	0	0
7	0	0	0	8	0	0	0
9	0	0	0	10	0	0	0
11	0	0	0	12	0	0	0
13	0	0	0	14	0	0	0
15	0	0	0	16	0	0	0
17	0	0	0	18	0	0	0
19	0	0	0	20	0	0	0

HDLC	Current	Next	(Input)	HDLC	Current	Next	(Input)
1	1	1	1	2	1	1	1
3	1	1	1	4	1	1	1
5	1	1	1	6	1	1	1
7	0	0	0	8	0	0	0
9	0	0	0	10	0	0	0
11	0	0	0	12	0	0	0
13	0	0	0	14	0	0	0
15	0	0	0	16	0	0	0
17	0	0	0	18	0	0	0
19	0	0	0	20	0	0	0