· web viewall other disc addresses are in negative form within the active file header. the type...

NIROS

NIXDORFCustomer Service COMPUTER

Table of Contents

1. Introduction ......................................... 11.1 System Components .................................... 11.2 Controller and Configuration Components .............. 11.3 System Operation ..................................... 21.4 Resources ............................................ 2

2 Bootstrap ............................................ 32.1 Functional Sequence .................................. 32.2 Error Handling ....................................... 42.3 Assignment of Memory Space ........................... 42.4 Flow Chart ........................................... 5

3 BZUPNEW .............................................. 73.1 Functional Sequence .................................. 73.2 Error Handling ....................................... 73.3 Block Structure ...................................... 8

4 System Loader (XVSYLAR) .............................. 94.1 General .............................................. 94.2 Block Structure ...................................... 94.3 XVSYLAR Function ..................................... 104.4 Processor Loader (LOAD) .............................. 104.5 Service Module (XVSYLAR) ............................. 11

5 Initial Program Load (IPL) ........................... 115.1 General .............................................. 115.2 Process .............................................. 125.3 Flow Cart “Power On – Start IPL” ..................... 135.4 Error Messages during IPL ............................ 145.5 Memory Address Allocation in Release 3.3 for SIR ..... 18

6 CONFIG ............................................... 196.1 General .............................................. 196.2 CONFIG File Structure ................................ 196.3 INFO Table ........................................... 22

7 INDEX ................................................ 257.1 INDEX Printout ....................................... 257.2 Removal of the Entry from Address 650 ................ 25

8 ACCOUNTS ............................................. 278.1 General .............................................. 278.2 ACCOUNT Data ......................................... 27

Copying of this document and giving it to others and the use or communication of the contents thereof are forbidden without express authority. Offenders are liable to the payment of damages. All rights are reserved in the event of the grant of a patent or the registration of a utility model or design.

10.79 Copying of this document and giving it to others and the use or communication of the contents thereof are forbidden without express authority. Offenders are liable to the payment of damages. All rights are reserved in the event of the grant of a patent or the registration of a utility model or design.

1

NIROS


9 DMAP .................................................. 299.1 General ............................................... 299.2 Cartridge Printout (Example) .......................... 299.2.1 Storage Module Printout (Example) ..................... 30

10 Formatter ............................................. 3110.1 Management of Trail Replacement ....................... 3110.1.1 Physical Pack Structure ............................... 32

11 Port Control Block (PCB) .............................. 3311.1 FLW Word in Port Control Block ........................ 34

12 Channel Control Block (CCB) ........................... 35

13 Printer Control Block (PRCB) .......................... 37

14 Data File Table (DFT) ................................. 39

15 Partition Control Block (PCT) .......................... 41

16 Logical Unit Variable Information Table (LUVAR) ........ 41

17 Logical Unit Fixed Information Table (LUFIX) ........... 43

18 Processor .............................................. 4518.1 BYE .................................................... 4518.2 INSTALL ................................................ 4518.3 DRIVER ................................................. 4518.4 SCOPE .................................................. 4618.5 REMOVE ................................................. 4618.6 DSP .................................................... 4618.7 Synopsis ............................................... 4618.8 Disc Service Processor (DSP) Handling .................. 47

19 NIROS (REX) ............................................ 5119.1 Device Files in NIROS .................................. 5119.1.1 NO LOAD FLAGs .......................................... 5219.2 System Files in NIROS .................................. 5319.3 Processor Files in NIROS ............................... 5419.4 Standalone Files in NIROS .............................. 5419.5 REX .................................................... 5519.6 Memory Start Address for Various NIROS Components ...... 5619.7 Memory Assignment ...................................... 5819.7.1 Memory Assignment Description .......................... 5919.8 Page Zero Address Content .............................. 6119.8.1 Processor Page Zero Address Content .................... 6319.9 Memory Printout Release 3.3 ............................ 64



2

NIROS


19.10 Time-Sharing ............................................ 6519.11 Active File ............................................. 6719.12 SWAP IN ................................................. 6719.13 SWAP OUT ................................................ 6819.14 INPUT/OUTPUT ............................................ 7019.15 Data Access ............................................. 71

20 IOCS .................................................... 7520.1 Channelling Concept ..................................... 7520.2 Task .................................................... 7620.3 Entries in the Waiting Queue ............................. 7720.4 Partial Printout of a Task Queue ........................ 7820.5 Removing an Entry from the Waiting Queue ................. 7920.6 Task Priorities ......................................... 79

21 Interrupt Handling ...................................... 8121.1 Parity and Time Error Interrupts ........................ 8121.2 System Time Interrupt ................................... 81 21.3 Power Failure Interrupt ................................. 8221.4 Power Start Routine ..................................... 8221.5 E/A Interrupt ........................................... 82

22 NIROS Block Diagram ..................................... 8322.1 Flow Chart .............................................. 8422.1.1 IDLE .................................................... 8422.1.2 ESCAPE for LOG ON ....................................... 8522.1.3 LOG ON .................................................. 8622.1.4 Program Selection ....................................... 8722.1.5 BUMP .................................................... 89

23 File Label (File Header) ................................. 91

24 DISCSUB .................................................. 9924.1 General .................................................. 9924.2 Structure of a DISCSUB ................................... 10024.3 DISCSUB MAPPING .......................................... 10224.3.1 Introduction ............................................ 10224.3.2 SYSMOD Selection ........................................ 10324.3.3 SYSMOD Memory Assignment List ........................... 10424.3.4 Memory Assignment with DISCSUB MAPPING .................. 10524.3.5 Setting Up DISCSUBS ..................................... 10624.3.6 Calling DISCSUBS ........................................ 10724.3.7 Further Modifications ................................... 108



3

NIROS


25 File Organisation Methods ............................... 10925.1 Sequential Files ........................................ 10925.2 Formatted Files ......................................... 10925.3 Relative Files .......................................... 11225.4 Index Files ............................................. 11225.5 Text Files .............................................. 11625.6 File Definition ......................................... 11625.7 File Name ............................................... 11625.8 The Concept of Logical Units ............................ 11725.9 Record Pointers ......................................... 117

26 Data Security ........................................... 119

27 TAMOS ................................................... 12127.1 Selectors ............................................... 12127.2 Data Backup ............................................. 12227.3 System Monitoring ....................................... 12327.4 Control Files ........................................... 12327.5 Spooling ................................................ 12527.5.1 Supervisor Selector ..................................... 12627.5.2 System Maintenance ...................................... 12627.5.3 Setting Up a Selector ................................... 12627.5.4 Updating a Selector ..................................... 12727.5.5 Removing a Selector ..................................... 12727.5.6 Printing a Selector ..................................... 12727.5.7 Notice Maintenance ...................................... 12727.5.8 Text Maintenance ........................................ 12727.5.9 Program List ............................................ 12827.6 Service Routines ........................................ 12827.6.1 Start of Day ............................................ 12827.6.2 End of Day .............................................. 128 27.6.3 Data Backup ............................................. 12927.6.4 Reconstruction 2nd Generation ............................ 12927.6.5 Reconstruction 3rd Generation ............................ 12927.6.6 Setting Up Drives ....................................... 13027.6.7 Exchanging Drives ....................................... 13027.6.8 File Print Log .......................................... 13027.6.9 Formatting .............................................. 13027.6.10 Setting System Time ..................................... 13027.6.11 Setting Up Users ........................................ 13127.6.12 Shutting Down the System ................................ 13227.7 Spooling ................................................ 13227.7.1 Displaying Spool File ................................... 13227.7.2 Starting Spooling ....................................... 13227.7.3 Cancelling Spooling ..................................... 132 27.7.4 Displaying Log File ..................................... 132



4

NIROS


27.8 System Programs ......................................... 13327.8.1 Printing Archive Files .................................. 13327.8.2 Displaying Archive Files ................................ 13327.8.3 Printing Assignment ..................................... 13327.8.4 System Security ......................................... 13327.8.5 System Reconstruction ................................... 13327.8.6 System Commands ......................................... 133

28 Description of SYSMOD ................................... 13528.1 Calling SYSMOD .......................................... 13528.2 Main Selectors .......................................... 13628.3 Change Hardware Specifications .......................... 13628.3.1 Address MAP Registers ................................... 13628.3.2 Core Size ............................................... 13728.3.3 Disc Characteristics .................................... 13728.3.4 No. of ALM Controllers ................................... 13828.3.5 Channel Port Connection ................................. 13828.4 Change Software Specifications .......................... 13928.4.1 Active File Size ........................................ 13928.4.2 Drivers ................................................. 14028.4.3 Size of the Mag Tape Buffer ............................. 14128.4.4 Port Characteristics .................................... 14128.4.5 Data Files .............................................. 14228.4.6 Partitions .............................................. 14328.4.7 Core Resident DISCSUBS .................................. 14428.4.8 Queues .................................................. 14528.4.9 Time Slice .............................................. 14628.4.10 Decimal Sign ............................................ 14628.4.11 NCL Buffer Size ......................................... 14628.5 Core Allocation MAP ..................................... 14728.6 EXIT .................................................... 15128.7 DISCSUB List ............................................ 15128.8 Driver List ............................................. 15528.9 Swapping/Partitioning ................................... 15628.10 Memory Assignment ....................................... 15828.11 Time Slice Size ......................................... 159



5

NIROS


1 Introduction

The following system components describe the functional process of the NIROS in its natural order.

1.1 System Components

Bootstrap

- Performs a memory test- Determines the system unit- Loads the system loader- Displays an error report on the computer’s LED

System Loader

- Establishes ZE-Master communication - Loads master board- Determines and loads the REX and SIR (NIROS) components- Jumps to the preparation of the system (SIR)

SIR

- Evaluates the INFO and CONFIG configuration tables- Correspondingly assigns memory to system components- Generates buffers and tables- Creates the disc map- Jumps to REX

1.2 Controller and Configuration Components

System Files

- Config File- Index File- Accounts File- Disc Map

Standard Processors

- BYE- SCOPE- DSP

Tables



6

NIROS


- Port Control Block (PCB)- Channel Control Block (CCB)- Partition Control Table (PCT)- Disc Address Table (DAT)- Starting Address Table (SAT)- Data File Table (DFT)- Info- Printer Control Block (PRCB)- Mapped Address Table (MAT)

1.3 System Operation

REX

- Handles interrupts- Manages time slices- Manages time - Manages partitions- Calls resources (drivers, discsubs)

Position Management

- Sets position indicators- Transmits Signal - Manages the I/O Buffer - Handles special characters

Cartridge or Storage Module Drivers

- Runs disc applications- Processes disc errors

1.4 Resources

Discsubs

- Subprograms for SIR, REX, processors and drivers

Driver

- Interface programs between peripherals and the user2 Bootstrap



7

NIROS


A bootstrap is a 1 KB PROM located in 1517.01 computers on the J7 and J8 IC-sockets.

The bootstrap is loaded into the memory address 0 in the following situations.

Situations: Power failure signal (main switch off) Computer clearing signal Emergency power supply clearing signal Adapter removal

2.1 Functional Sequence

The bootstrap routines are performed in the following order:

1. Placing the general interrupt lock and releasing the locks corresponding to time errors, parity errors and power failure.

2. Performing a memory test by writing and reading random memory addresses until 64KB. Moreover, all addresses will also be indicated by a shut down value (400).

3. Determining the magnetic disc drive type The partitions of the drive types are Cartridge = 0, 40MB Storage Module = 1, 80MB Storage Module = 2, Phoenix Drive = 4 and the bootstrap is located at 20.

4. Processing a 10 seconds long time warp.

5. Determining the system unit starting from unit 0-7 for the Cartridge, unit 0-1 for the 40 MB Storage Module, unit 0-3 for the 80 MB and unit 0-5 for the Phoenix Drive.

6. Loading BZUPNEW from RDA 0 from the determined drive type and writing memory addresses starting from address 26000.

7. Comparing the identification, the first word of the BZUPNEW must be a 403. In case of an error, the bootstrap error routine is called.

A checksum is formed through the BZUPNEW and compared to the 2nd word of the BZUPNEW. If the comparison has a negative result, the bootstrap error routine is called. In case of a positive result, which means that both tests have been positive, the jump to BZUPNEW (address 26000) occurs.

2.2 Error Handling



8

NIROS


The next unit (x = x+1) will attempt to be loaded in case of magnetic disc failure, incorrect identification or false checksums.

If all tests are negative, the system will try to load unit 0 once again with consequential error reports on the computer’s LED. It then jumps to the start of the bootstrap routine.

2.3 Assignment of Memory Space

Memory test KBInterrupt processing stageSearch BZUPNEWLoad BZUPNEWJump to BZUPNEWDriver: Cartridge Storage Module Phoenix DriveDisc error report: Cartridge Storage Module Phoenix Drive

3 BZUPNEW



9

Address 0

254

457

777

NIROS


The Block Zero Utility Package (BZUP), located on block 0 of each disc (LU), is loaded by the bootstrap into memory. BZUPNEW is not a file per say because it has no header and is not listed in any INDEX.

The first 3 words from the BZUPNEW have the following meaning:

Word 0: an identification is listed here = 403Word 1: check digit for BZUPNEWWord 2: number of words that build the checksum.

The E/As of various files are recorded in words 26, 26 and 30:

Word 26: RDA of the XVSYLAR or XVSYLAD headerWord 27: RDA of the NIROSR or NIROSD headerWord 30: RDA of the DISCSUBS headerWords 360-377 are reserved for position loader programs.

3.1 Functional Sequence

1. Determining the ALM flags for RAP or DAP ALM flag = 0 RAP ALM ALM flag = 1 DAP ALM

2. If the ALM flag = 0, the XVSYLAR file is searched through Find File, if the file is not found or a MP error occurs, an error handling occurs through the BZUPNEW.

3. Loading the XVSYLAR files into memory. The header is saved starting from address 27400 and the XVSYLAR file itself starting from address 30000.

4. If all blocks are in the memory (5), the checksum is built from word 4 until the end of the file, and compared to the content of address 30001. If the comparison is negative, an error handling occurs through BZUPNEW.

5. The Cartridge, Storage Module and Phoenix drivers, as well as the bootstrap error routine (address 252 until 773), are pushed to address 32000 in the memory.

3.2 Error Handling

The system returns to the bootstrap (next unit) in case of disc errors. If the checksum is incorrect or the XSYSLAR file is not found, an error report shows up on the computer’s LED.3.3 Block Structure



10

NIROS


Word 0 : Identification 1 : Check digit 2 : Number of words 26 : XVSYLAR RDA 27 : NIROSR RDA 30 : DISCSUBS

360 – 377 : Position loader programs

4 System Loader (XVSYLAR)



11

NIROS


4.1 General

The system loader is saved on five 512 blocks on the magnetic disc.

The last block of the system loader contains the parity and time error handling routines and is loaded into memory in case of a parity or time error. The system loader ensures that the master indicator and operating system are loaded.

The position programs that can be loaded are identified by XB00-XB49 and are only found in 3 XB programs.

The diagnosis segment, which is loaded first, is named XBOA.

4.2 Block Structure

HEADER

Master indicatorSystem unit definition

Find operating systemLoad operating system

LoadStandalone file

Service moduleZE-RAP procedure

Parity and time error handling routines

Only blocks 0-3 are resident in the memory during the system loader.



12

Block 0

1

2

3

4

NIROS


4.3 XVSYLAR Function

The master indicator is polled until a loader wish is recognized. The loader wish is created by switching the indicator on.

The diagnosis segment is loaded by the system disc determined by the bootstrap.

The master indicator is polled once again. The second loader wish is created by entering the program no. If the program no. has already been specified through the SYSMOD, just press the “CR” key.

The position program is now loaded.

If the system loader was unequally loaded by unit 0, the master indicator will reveal the “LOADED FROM UNIT X” text. If it was only loaded by unit 0, “INIT” appears.

The system disc is newly defined through the “CR” confirmation resp. through the entry of the unit no. and the “CR” key. The system loader looks for the DISCSUBS RDA and for the NIROSR header in this entered unit no.

The XVSYLAR header is set at address 26, the NIROSR header at address 27 and that of DISCSUBS at address 30 in block 0 (BZUPNEW).

After the operating system is loaded, the system loader branches out to the system initialization routine (SIR).

4.4 Processor Loader (LOAD)

The master indicator is loaded by the system loader during the system initialization. All other positions must be loaded separately during time-sharing. The configured positions are polled starting from the execution of the time-sharing algorithm. Switching on the position creates a loader wish. The indicator controller of the operating system thereby queues a processor loader task. The XBOA diagnosis segment is transferred to the position. The workplace indicates the text “CR!”. The confirmation through the CR key sets a new loader wish and the



13

NIROS


process loader is once more added to the queue. The processor loader transfers the position program configured for the corresponding channel. The configured position program number is set starting from address 360 in block 0 for each channel. SIR adds a further PCB with a I/O buffer to the processor loader. Therefore, only one position may be loaded at a time. If the position program is not present, an error report will be issued on keyboard (s. RAP control program).

4.5 Service Module (XVSYLAR)

The service module from XVSYLAR performs the following functions:

Transferring of the calling program parameter in the Channel Control Block (CCB).

The address of the corresponding CCB must be contained in register 2 when calling the service module.

Sending the block to the selected channel of the ALM.

Receiving the acknowledgement block of the position.

Determining the received blocks and data assignment.

Returning to the calling program.

5 Initial Program Load (IPL)

5.1 General

The system initialization (Initial Program Load) of the 8870 system consists of 4 stages.

Stage 1: Loading the bootstrap and memory test, determining the drive type, loading the BZUPNEW from RDA 0.

Stage 2: Loading BZUPNEW, establishing the workplace alternative RAP or DAP, loading the system loader.

Stage 3: Loading the system loader, position programs and operating system. In the case of DAP, the position programs are loaded.

Stage 4: SIR, operating system initialization.

Stages 1, 2 and 3 have already been described, while the description of stage 4 follows.



14

NIROS


5.2 Process

An Initial Program Load (IPL) must be performed at restart, a system crash or after the system has run in standalone mode.

The first step of the IPL is loading the BZUPNEW from disc block 0 into memory starting from address LBZUP (26000).

IPL brings a new REX (operating system core) and SIR file, contained in the REX file, into the memory and performs all necessary initialization functions. This occurs through the disc driver within BZUPNEW.

SIR evaluates the CONFIG file in order to load the necessary disc driver routine into memory. The LUFIX and LUVAR tables are generated for each disc.

SIR continues by examining the DISCSUB file in order to build the DAT (disc address table) and the SAT (start address table) containing the absolute disc address resp. the memory address. SIR transfers the SISCSUB corresponding to the flag into memory.

The SCOPE, DSP, DISCSUBS, MESSAGES and BYE files are evaluated in order to enter the disc addresses in the INFO table.

The Port Control Block of each port, the data files table and the input/output buffer are created.

INDEX continues to be evaluated in order to build the DMAP. Moreover, an active file is attached to each port.

The REX start routine initializes the interrupt system.

Only the power failure, parity and time error interrupts are released until you are prompted to HIT ESC.



15

NIROS


5.4 Error Messages during IPL

Error Messages

Message SIR RoutineNo. Message Number1 NO CONFIG FILE 72 x DISC ADDRESS DOESN’T MATCH INDEX ENTRY 123 x FILENAME DOESN’T MATCH INDEX ENTRY 124 x “Filename” HAS WRONG NUMBER OF DISC ADDRESS 125 x “Filename” USES DISC BLOCK ALREADY MARKED 126 x “Filename” IS NOT VALID DEVICE FILE 13



16

1 2

Error evaluation through bootstrap or BZUPNEW

XB 01 selectionXB 02 transferXB 03

INITdisplay

UNIT #input

START INITIALPROGRAM LOAD

NIROS


7 x “Filename” REFERS TO AN IN USE DEVICE ADDRESS 138 PLEASE WAIT ... 12, 149 NOTE: PORT A (XY)’s ACTIVE FILE IS NOT OPTIMIZED 1510 ONLY (x) FREE NODES (OCTAL) 1611 TIME RUNS BACKWARDS 17

x These notifications end with the following message:PRESS SPACE KEY TO DELETE FILE



17

I

Read config fileTransfer INFO tables parameter and disc buffer parameter from CONFIG

Build the DISC map scheme and DISC ADDRESS and STARTING ADDRESS tables once again

Logical unit tableDriver tableSetup LUVAR table (disc driver tables)

Read memory-resident discsubs(list located in block 3 of the config file)

Check if the processor configuration meets the minimum requirementsEnter the SCOPE, ACCOUNTS, BYE, MESSAGES, CONFIG, RDA

HOUSECLEANINGSystem disc reorganization

II

Routine7

8

9

10

11

12

Message 1

TRAP101

TRAP104

TRAP101105123

TRAP106107110

Message23458

NIROS




18

Routine13

14

15

16

17

18

II

Load the system and peripheral drivers in the memory and initialize them

Initialize PCB (Port Control Block)

Create active files on the disc (1 file per port)

Create character queueBuild interrupt stackCreate free nodes (memory area)

Display output: HIT, ESC

End of system initializationStart of time-sharing

MESSAGE67

MESSAGE68

TRAP101102MESSAGE9

MESSAGE10

MESSAGE11

NIROS


5.5 Memory Address Allocation in Release 3.3 for SIR

SIR Routine Label Memory Address 3.3

1 START SIR 120002 SIR 130013 INMAS 157764 SKSM 120125 DADS + 2 131376 DSAT 164567 132058 133569 SIR 1 1341410 SCRES 1367311 SIR 1 C 1407112 HOUS X 1245113 SRDEV 1455514 SIRB 1596715 STRA + 2 1671716 SIRZ 1551017 SIRT 1570418 SMOV (RAP) 14453



19

NIROS


6 CONFIG

6.1 General

The CONFIG file contains configuration parameters that may be changed through SYSMOD. An IPL must be run after each update in order to load the newly configured system into memory.

The following table shows the various pieces of information included in the CONFIG file:

6.2 CONFIG File Structure

System History(not used)

General Information

Memory-resident discsub list

Disc Driver Table

Alternate discsub list

Disc driver

Partition Control Table



20

Block No.1

2

3

4

5

6

7

NIROS


The following parameters of the INFO table or the CONFIG file have the following meaning:

Address Label Parameter600 SDAT Date of system creation (no. of hours since 1.1.1973).

Do not modify!601 SPED Average command speed per ms.

Computer 1513/1517 Speed (octal) 653

602 MILU Maximal number of initialized log. units. This entry should be equal to the number of log. partitions.

603 NDCH Number of data channels per terminal. Each data channel occupies 8 memory words for a dialog terminal. NDCH is usually saved on 8 (octal).

604 PLCA Address of the Port Control Area (PCB for port 0). This address is automatically set for SIR if a driver attribute table indicates a PCB address and must lie in the LBSA + 2000 + ABUF = LBCA = TOPW + 1 – TNAP x 40 range.

605 TNAP Total reports of the dialog terminal; the value is automatically increased by SIR if it is lower than the dialog terminal number indicated by the driver attribute table.

606 AFHA This active file header area cell should be located in the CONFIG file 0 if no special buffer is reserved in the memory for the modification of active file headers. In this case, SIR sets an indicator of the HBA at this memory address. If the AFHA is not equal to zero, SIR reserves 256 words of memory after ABA and places an indicator on on this area in the memory assigned to AFHA.

607 DMR DISCSUBS will be mapped in the system if the contentof the DMR word is not equal to zero. The value present in the DMR word at that time becomes the first page number of the DISCSUB map range. DMR is a 2K large memory block between SSA and ABA.

610 TOPW Last usable word from the memory. NIROS will ignore memory areas beyond this address.



21

NIROS


The value of TOPW is 77776 octal. The TOPW is changed in Release 3.3. It has no constant value, but depends on the generated system.

Address Label Parameter611 ABUF Size of the auxiliary buffer area (help buffer

measured in words). This area must be at least 1004 words (octal) if index-sequential data is used.

612 TBUF Magnetic tape buffer area. As long as the system contains no magnetic disc, the content of this cell is zero. If, however, a magnetic disc exists, it should indicate the buffer size of the largest bandwidth.

613 NCQN Number of additional character queue indicators. SIR reserves two character queues plus the number of additional character queues for each dialog terminal. Additional character queues are required in order to reach maximal entry speed especially in the case of intensive character handling. Each queue is assigned two words in the memory; the lowest value is 2.

614 NNOD Lowest number of unoccupied character queues desired for the use of task chains in the memory. This value is the only limit of the number of concurrent tasks in the system. Each character queue occupies 10 words (decimal) of memory. The value from this memory address shows available free space in order to make DISCSUBS memory-resident etc. because the remaining memory area at the end of an IPL is reserved for open character queues.

615 NSIG Length of buffer chains for the signal. This is the greatest total value of signals that may await reception. Each queue occupies 4 words in the memory.

616 NSUB Maximum number of DISCSUB subprograms. This value does not need any modifications as long as no disc- resident subprograms that could increase the total number of the NSUB value are added. NSUB x 2 memory words are occupied for the use of indication tables.

617 KTSL This word delivers coefficients in order to determine a new task start priority and the priority increase and two coefficients for the calculation of the time slice length assigned to each user.

620 NPAR Number of partitions621 SAF Size of the active file



22

NIROS


622 CDPF Flag for comma

6.3 INFO Table

Address Label Meaning

600 SDAT SYSTEM CREATION DATA601 SPED AVERAGE CPU SPEED602 MILU MAXIMUM = INSTALLED LOGICAL UNITS603 NDCH NUMBER OF DATA CHANNELS PER PORT604 LPCA LOCATION OF PORT CONTROL AREA605 TNAP TOTAL NUMBER OF ACTIVE PORTS606 AFHA ACTIVE FILE HEADER AREA607 DMR DISCSUB MAP RANGE610 TOPW TOP WORD OF CORE611 ABUF AUXILIARY BUFFER SIZE (NO. OF WORDS)612 TBUF MAG TAPE BUFFER SIZE (NO. OF WORDS)613 NCOW NUMBER OF EXTRA CHARACTER QUEUE MODES614 NWOB MINIMUM NUMBER OF FREE MODES615 NSIG NUMBER OF SIGNAL BUFFER MODES616 NSUB MINUMUM NUMBER OF DISCSUB617 KTSL COEFFICIENTS FOR I/O DONE PER TIME SLICE620 NPAR NUMBER OF PARTITIONS EXCEPT THE MAIN ONE621 SAF SIZE OF THE ACTIVE FILE622 CDPF FLAG FOR COMMA623 TSA TEMPORARY STORAGE “A” POINTER (6 WORDS)624 TSB TEMPORARY STORAGE “B” POINTER (6 WORDS)625 TSQ TEMPORARY STORAGE “Q” (6 WORDS)626 TSZ TEMPORARY STORAGE “Z” POINTER (6 WORDS)627 TSC TEMPORARY STORAGE “C” POINTER (6 WORDS)630 HRS CPU TIME HOURS SINCE631 TSC PART OF HOUR IN TENTH-SECONDS632 CPLU CURRENT PROCESSOR LOGICAL UNIT633 CPDA CURRENT PROCESSOR DISC ADDRESS634 CPTN CURRENT PROCESSOR TYPE NUMBER635 SDFT SIZE OF EACH PORT’S DATA FILE TABLE636 DSCO DISC ADDRESS OF “SCOPE”637 DBYE DISC ADDRESS OF “BYE”640 DDSP DISC ADDRESS OF “DSP”641 DSUB DISC ADDRESS OF “DISCSUBS”642 DMSG DISC ADDRESS OF “MESSAGE”



23

NIROS


643 DSYH DISC ADDRESS OF “SYSTEM HISTORY BLOCK”644 RFLG RECOVER INHIBIT FLAG645 MASK INITIAL INTERRUPT MASK646 STK POINTER TO “CALL” STACK POINTER647 RGS POINTER TO REGISTER BUFFER FOR “CALL”650 ASQ POINTER TO “CALL” STACK POINTER651 DBS POINTER TO (BLOCK IN HSA) CELL652 RCV POINTER TO RECOVER ROUTINE


653 LUT POINTER TO LOGICAL UNIT TABLE654 TBA POINTER TO MAGNETIC TAPE BUFFER AREA655 ELB POINTER TO END OF LAST DISC BUFFER656 INT POINTER TO INTERRUPT HANDLER TABLE657 NLCB LINE CONTROLLER BUFFER PTR.660 DKMR LOC, FOR FLAG661 RWRTC POINTER TO READ-WRITE RETRY-COUNTER662 CARE POINTER TO COMMON AREA663 DRUN DISC ADDRESS OF RUN664 ISFF INTERRUPT SERVICE FAULT FLAG665 PFRF POWER FAIL RECOVER FLAG666 BPSP BEGIN PATCH SPACE (AFTER LAST PATCH TO REX)667 ENDP END OF PATCH SPACE (SET BY STR)670 JCBRR POINTER TO AN ICB IN REX (9 WORDS) MAY BE USED BY

DISCSUBS671 ASBL DISC ADDRESS OF “PRINTER ASSIGNMENT BLOCK”672 STIF START INPUT RETURN FLAG673 DLOA DISC ADDRESS OF “LOAD”674 MPRI BASIS SLICE OF PRIORITY675 DCOP PRINTER TO DIAGNOSTIC CONTROL BUFFER676 POC DISC DRIVER COUNT AREA677 ENCC POINTER TO ENTRY OF COUNTER CODE (DIAG)700 RWRF READ/WRITE DISC RETRY FLAG701 DDFL DISC DRIVER FLAG702 ERDC2 ERROR DISC CONTROLLER ROW 2703 ERDC3 ERROR DISC CONTROLLER ROW 3704 ERDC4 ERROR DISC CONTROLLER ROW 4705 DIWF DIAG WRITE FLAG706 GERR ADDRESS OF “GENERATE ERROR RECORD”707 CRRF CONTROL READ RETRY FLAG



24

NIROS


7 INDEX

Each logical disc data has its own index file. This file contains all file names and the direct addresses to these disc files (as well as the header block address).

An entry in the index file looks like this:

7 words File name1 word Header block address

The DMAP update is performed according to the entries in the index file.

7.1. INDEX Printout

0: 140703 141717 152716 152323 0 0 0 310: 140706 127320 140722 140715 130260 130400 0 120620: 140703 141717 152716 152314 144723 152000 0 732130: 122306 142000 0 0 0 0 0 702740: 140723 141711 144656 142702 141704 144703 0 60650: 140723 141711 144670 127301 151703 144711 133400 61060: 140723 141711 144667 127301 151703 144711 134000 61270: 140723 141711 144720 152716 141710 152301 151314 620100: 122301 142703 0 0 0 0 0 7032110: 122322 152303 0 0 0 0 0 7066120: 140723 141711 144722 142701 142324 140702 146305 622

7.2 Removal of the Entry from Address 650

610: 122322 150322 132000 0 0 0 0 7305620: 122322 150322 132400 0 0 0 0 7307630: 122322 150322 133000 0 0 0 0 7311640: 122322 150322 133400 0 0 0 0 7313650: 0 147304 142730 0 0 0 0 525660: 0 0 0 0 0 0 0 0670: 0 0 0 0 0 0 0 0



25

NIROS


8 ACCOUNTS

8.1 General

All the user’s accesses of the operating system are recorded in the ACCOUNT file. A so-called account is created for each user in this file. The use of disc blocks is managed dynamically which means that the account of a user will only be altered if he creates, removes or extends files. The values of the used CPU and connection time, as well as the maximum number of disc blocks, are updated by the “BYE” processor during the during the log in process. The value of this data is determined independently of the user’s privilege level.

8.2 ACCOUNT File

The entries of the ACCOUNT file have the following structure:

Word Content

1-6 Account identification (name)7 Assigned priority8 Assigned logical unit9 Account number (privilege, group and username)10 Remaining connection time in minutes (x)11 Remaining CPU time in seconds (x)12 Number of max. permitted disc blocks (xx)13 Number of used disc blocks 14 Top use of disc blocks15-16 Cost of file use

x The values of the remaining connection and CPU time must both be positive or 100000 (octal), which means that they must not be limited. These values are updated when the user logs out. The user cannot log in anymore if the time has expired.

xx The number of max. permitted disc blocks is not reserved on disc but may not be surpassed by the user.



26

NIROS


9 DMAP

9.1 General

Each logical disc unit has its own DMAP. The recent block assignment list of the magnetic disc is stored in this file, which means that the DMAP will be updated at each IPL.

Each entry of the DMAP consists of 4 words which have the following structure:

1st word = cylinder address

2nd word = number of available blocks per cylinder (max. 24)

3rd word = block assignments bit by bit page 0Bit = 0 = available blockBit = 1 = occupied block

4th word = block assignments bit by bit page 1Bit = 0 = available blockBit = 1 = occupied block

Block assignment is therefore described bit by bit from right to left.

Since only 12 blocks (sectors) are available for each trail in terms of hardware, the upper 4 bits are set to 1.

9.2 Cartridge Printout (Example)

0: 0 0 177777 177777 40 0 177777 17777710: 100 0 177777 177777 140 0 177777 17777720: 200 0 177777 177777 240 0 177777 17777730: 300 0 177777 177777 340 0 177777 17777740: 400 0 177777 177777 440 0 177777 17777750: 500 5 177777 177063 540 0 177777 17777760: 600 0 177777 177777 640 0 177777 17777770: 700 0 177777 177777 740 0 177777 177777



27

NIROS


100: 1000 0 177777 177777 1040 0 177777 1777779.2.1 Storage Module Printout (Example)

0: 0 0 177777 177777 177777 177777 177777 1777710: 177777 177777 177777 177777 240 0 177777 1777720: 177777 177777 177777 177777 177777 177777 177777 17777730: 500 0 177777 177777 177777 177777 177777 17777740: 177777 177777 177777 177777 740 0 177777 17777750: 177777 177777 177777 177777 177777 177777 177777 17777760: 1200 0 177777 177777 177777 177777 177777 17777770: 177777 177777 177777 177777 1440 0 177777 177777100: 177777 177777 177777 177777 177777 177777 177777 177777110: 1700 0 177777 177777 177777 177777 177777 177777120: 177777 177777 177777 177777 2140 0 177777 177777130: 177777 177777 177777 177777 177777 177777 177777 177777140: 2400 0 177777 177777 177777 177777 177777 177777150: 177777 177777 177777 177777 2640 0 177777 177777160: 177777 177777 177777 177777 177777 177777 177777 177777170: 3100 0 177777 177777 177777 177777 177777 177777200: 177777 177777 177777 177777 3340 0 177777 177777210: 177777 177777 177777 177777 177777 177777 177777 177777220: 3600 0 177777 177777 177777 177777 177777 177777230: 177777 177777 177777 177777 4040 0 177777 177777240: 177777 177777 177777 177777 177777 177777 177777 177777250: 4300 0 177777 177777 177777 177777 177777 177777

This is the same representation as by Cartridge, the only difference being that 32 sectors are available per trail and head. The number of heads increases to 5.



28

NIROS


10 FORMATTER

The new formatter places max. 30 trails for the management of trail replacement. This format takes a total of 22 minutes.

A multiple read follows the writing which means that a sector must be read flawlessly 5 times. If this is not the case, the trail will be rejected.

A 6DB6 will be written as master and read 5 times. Afterwards, the bit pattern will be shifted and the process repeated.

Bit pattern 33333 is the last one from the pack.

10.1 Management of Trail Replacement

The defective trails are entered in the DMAP header starting from word 70. Entries are performed per word.

Word 70 = defective trailWord 71 = replacement trailWord 72 = defective trailWord 73 = replacement trailetc.

This means that every defective trail and its corresponding replacement trail need 2 words altogether.

Definition of defective replacement trails

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0



29

Cylinder

Head

NIROS


10.1.1 Physical Pack Structure

33 MB = 411 cylinders

0 – 402 correspond to 403 cylinders with 5 trails each, an available address space of 64480 blocks of 512 bytes each.


21 MB = 262 cylinders



The number of cylinders for the 33 MB system is 403 and for the 21 MB one = 256.

The max. number of replacement trails is 30, depending on the number of FMAP cells in the DMAP header.



30

NIROS


11 Port Control Block (PCB)

Each active port has a Port Control Block that contains various pieces of information about its status and owner. The current user pointer (RUP: Regnant User Pointer) on page 0 shows the user’s PCB, his currently saved processor in memory and the current task pointer (RTP), which indicates the PCB or TCB (Task Control Block) of the main task at a specified time. The exact description and relative addresses of all PCB elements are to be taken from the following list. All PCBs are summarised in the Port Control Area (PCA) where the PCBs are sorted increasingly in regards to their port numbers. Thus, the PCA in REX’s page zero points to the PCB of port 0.


0 ALI. ALM information on row 0 1 ALA. ALM address0 CCB. Address of the Channel Control Block1 EKY. Termination code2 FBA. First byte address in the I/O buffer – 13 LBA. Last byte address in the I/O buffer4 IBP. Byte input pointer5 OBP. Byte output pointer6 PCT. Pointer to the Partition Control Table7 SIN. Bit 0-7 PORT PRIOR.10 TIB. Temporary buffer for character input11 TOB. Temporary buffer for character output12 FLW. Word status13 ULU. LU number of the user14 URA. Return address of the user15 ORA. All return addresses16 CTU. Computer time (left byte = hours)17 CTL. Computer time (right byte = /10 seconds)20 ACT. Account number, privilege level21 TON. Computer time after LOG ON in minutes22 PRI. User priority23 SWF. Swap flag24 DQT. DE queue time in /10 seconds25 DFT. Pointer to Data File Table26 PDC. Pause Delay Counter in /10 seconds27 AHA. Active file header disc address30 PDA. Program’s disc address31 TIL. Row length (number of characters)32 SND. Pointer to driver’s send routine33 OCC. Column counter readout34 ODC Delay counter readout



31

NIROS



35 SZE. Program size 36 CEN. ENQ counter (only for RAP systems)36 BP1. Buffer pointer (SD 1)37 BP2. Buffer pointer (SD 2)37 PRC. Printer Control Block Address

11.1 FLW Word in Port Control Block

The FLW bits have the following meaning (bit 15 is the bit of the highest value).

Bit Meaning of the individual bit in the FLW

15 CR pressed (buffer pointer), only for DAPPrinter is active, only for RAP

14 Binary readout mode (no parity)Switch off STI mode, only for RAP

13 DSP breakpoint activated

12 DSP is active on this port

11 A signal is activated by break

10 Break has been identified

9 Return was eliminated from RUN

8 A processor task is in the queue

7 Output is active

6 Input is active

5 Ending the interrupt causes an “AUTO LOG OFF”

4 Ignore XOFF and XON

3 Ignore CTRLO

2 Eliminate XOFF and XONSwitch off STI, RAP only

1 Buffer pointer readoutSTI sends, RAP only

0 Echo input character



32

NIROS


12 Channel Control Block (CCB)

Each physical ALM channel is assigned a so-called Channel Control Block in the RAP system. The total size of this Channel Control Block is 18 words. The management of the master model, slave model and an eventual connected remote printer is made possible through the CCB.

The meaning of each of the 18 words is explained in the following list.


0 PCM. Master’s PCB address1 ACB. Current PCB address2 ALR. ALM address (device address)3 ALC. ALM channel address4 TIN. Sender interrupt output5 RIN. Receiver interrupt output6 CLK. Clock7 CDR. Reception request10 CT1. Counter11 CDS. Sender request12 ENQ. Last ENQ command13 ACK. Last ACK14 LPC. LPC character15 PCS. Slave’s PCB address16 NBL. Next block 0 = master, 1 = slave, 2 – printer17 NBT. Number of bytes corresponding to the printer



33

NIROS


13 Printer Control Block (PRCB)

If remote printers are connected to the RAP, a Printer Control Block will be generated for each printer. The start address of the PRCB is word 37 of the Port Control Block. All parameters needed by the printer are included in this PRCB. The size of the PRCB is 44 words.

The meaning of each parameter is explained in the following list.

Address Label Description

0 PDFT. Data File Table1 PBPO. Start position (must be 1)2 PEPO. End position (must be 2)3 PNIG. Form level (must be 3)4 PBPS. Standard start position5 PEPS. Standard end position6 PHIS. Standard form level7 PCHA. Channel no. (0 – 7)10 PDRI. Driver no. (0 = RPL, 1 = RPR, 2 = RPF)11 PRUP. Driver user (set by OPEN)12 PPRT. PCB address of the channel (set by OPEN)13 PRCL. PRCB address from S LPTL (set by OPEN)14 PCPO. Current position15 PAPO. Current start position16 PFBK. Blank flag17 PBLK. Blank counter20 PMLF. Current row counter21 PANZ. Current number22 PFRM. Form flag23 PLIN. Line counter26 PZBP. Current input pointer27 PERR. Error memory30 PFBA First buffer address31 PLBA. Last buffer address32 PIBP. Current input pointer33 POBP. Current output pointer34 PFLW. Flag word35 PRTL.36 PRTR. PRCB address, set by OPEN, removed by CLOSE37 PRTF.40 PCBP. Current pointer41 PHBP. Pointer42 PWT1. Waiting flag43 PWT2. Waiting flag



34

NIROS


14 Data File Table (DFT)

Each active port has its own table of data files. It can be found through a pointer in the corresponding Port Control Block.

Each DFT has 8 words with the following meaning.

Address Label Description

0 FLU LU number of the filecomplementary to the device

1 FDA File header disc address2 CBN Current block number3 STS Channel status4 FSZ File size (number of contiguous blocks)

(number of sentences at formatting)5 WPR Number of words per sentence6 FRR First available record number in the index file

column counter in case of devices7 PDP Parameter for peripheral device

Meaning of the STS channel status word

Bit 15 Sentence is lockedBit 14 File is read-onlyBit 13 File is contiguousBit 12 File is not formattedBit 11 Peripheral deviceBit 10 File is indexedBit 9 Index file with a two-word pointer



35

NIROS


15 Partition Control Block (PCB)

A Partition Control Table is generated for each existing partition. Its size is 61 octal per partition.


0 FLG. Flag word1 PSZ. Partition size (number of blocks)2 PNM. Program name (7 words)11 FLU. Logical unit no. of file12 FDA. File disc address13 PCB. Pointer to PCB14 CPC. Ongoing program counter15 FTU. First time used16 NOA. Number of attempts17 SOD. Flag for out done

Words 20-60 contains the page address of the corresponding partition.

Flag word in the PCT

Bit 0 Partition was usedBit 1 Partition is usedBit 2 Swap inhibit

ReservedBit 15

16 Logical Unit Variable Information Table (LUVAR)

Word Label Meaning

0 NCYL Number of cylinders1 PART Partition information3 MNCYL Max. number of cylinders4 AVBC Available blocks5 MINB Min. number of cylinders for creating a new file6 OCYL Current cylinder (head position)7 FUDA First unused RDA10 ERRC Data check error counter

Address checkLate data channel



36

NIROS


17 Logical Unit Fixed Information Table (LUFIX)

Label Meaning

DSIZ Driver size incl. LUFIXDNAT Number of alternate tracks corresponding to the disc typeFSBIV FORMATTER: buffer size + inverted valueFNPAT FORMATTER: number of patternsFDLPF Difference between the first logical and physical unused ROADMSK Disc Controller mask bitsINIT Init track routine inputDINT Interrupt handler pointerDMSK Disc Controller mask bitsPDRD Power fail restartEMSK Error status masks

Read-only maskNo such disc maskLate data channel maskAddress check error maskIllegal disc address mask

IDRV “Initialize driver” subroutine jumpSLUR “Skip if LU ready” subroutine jumpSKNB “Skip if not busy” subroutine jumpREDS “Read status” subroutine jumpSEEK “Seek or recalibrate” subroutine jumpNSCT Number of sectors (per trail)NTRK Number of trails per cylinderLRTC Logical to real track conversion factorLRCC Logical to real cylinder conversion factorDFLG Disc flag word

List of possible DFLG words

Bit 15 Flag exchange packBit 14 Fixed head discBit 13 UnusedBit 12 UnusedBit 11 Sector exchange between track and cylinderBit 10 The same sector in the next trackBit 9 Next sector, next trackBit 8 Next sector, same trackBit 7 No transfer for sequential sectorsBit 6 Sequential sectorsBit 5-0 Device address



37

NIROS


18 Processor

18.1 BYE

If the BYE processor is called by a user, that user will be logged out of the system. This processor simultaneously manages both the CPU and connection time for the individual user and updates the user’s account in the ACCOUNT file after the call. The user may see his use of system resources on the screen. A new login of the user is possible through an ESC key confirmation on the alpha-numeric keyboard. Parts of the BYE processor will also run during the user’s login to the system (e.g. the user’s account is being opened).

18.2 INSTALL

The Logical Installation Processor generates the mapping between logical and physical disc units (login). During the IPL, the system disc is automatically assigned the logical unit 0 of the physical unit which has started the system.

All other logical units must be declared through INSTALL. One must pay attention that this process is performed for all logical units.

The logical unit is declared through the INSTALL AND CLEAR function, however, all entries from INDEX are simultaneously removed, which means that the disc is empty for the current user.

The INSTALL FORMAT function clears the disc as well, but does not declare this unit.

18.3 DRIVER

If we were to speak about a driver in regards to the system (attention: the file name mainly begins with a dollar sign), we are speaking either about a system driver or three different channel programs for devices.

These devices are defined as:

- An interactive user space where the user may run processors and user programs.

- a peripheral device that may be used by a user by READING or WRITING an in/output on the device, just like data files.

- a logical unit with its own index, which enables the user to access data through the READ or WRITE functions, remove or update them.



38

NIROS


18.4 SCOPE

The System Command Processor, SCOPE for short, enables system-user communication. This processor allows the user to use the system for:

- Programming,- Saving and maintaining files and- Desktop and general system management.

Communication is made possible through the command line, in which each command represents an individual software processor or a BASIC program. If the user is in SCOPE, the first column on his screen shows a number sign (#).

18.5 REMOVE

The Logical Unit Removing Processor must be chosen before changing the magnetic disc and clears the corresponding logical unit. An orderly process requires all files on the chosen logical unit to be closed.

18.6 DSP

The Disc Service Processor (DSP) is required for the tests and updates of the system and files. DSP can be called from every active workplace of the system (see privilege levels) during the normal performance of the system.

DSP may be chosen from SCOPE (number sign on screen) if the user is logged in the system.

18.7 Synopsis

The description of all above listed operating system components is mandatory, however, all other processors are optional no matter the use case, because they are not directly required by the system.



39

NIROS


18.8 Disc Service Processor (DSP) Handling

In order to call DSP, one must log in to the terminal and input the DSP command “CR”.

To end a misuse, close the DSP (always with the X command) and logout in order to leave the terminal through the log. OFF command.

The following commands enabled after DSP has been called.

The input of a command is terminated through the “Return” key. All commands work either with absolute memory addresses or with the file or disc block, indicated by the last F, G or H command.

Command Meaning

AX Attaches the block that contains the X memory address to the file chosen by the last F command. The first memory address and attached block disc address are outputted.

BX Enters a breakpoint in address X. This command only makes sense when the specified file is a processor. If it is usedin this terminal and the breakpoint is reached, Register and Carry are outputted. The breakpoint is removed through the F, G, H or X command.

C command The inputted command is regarded as a system command by SCOPE. It works like pressing CTRLC and inputting the same command, however, a program name may not be inputted withouta processor name in this case, which means that the processor is not chosen automatically.

DC Octal dump on address X. 8 words are outputted per row, the address of the 1st word of the line is also outputted at the beginning. The listing may be stopped through an ESC key stroke.

EX Symbolic or octal input starting from address X. Each input must be terminated by a “return”. ESC terminates the input mode. Machine instructions may be inputted in a symbolic form but device addresses must be inputted in an octal form (this means 601 instead of DISC). Labels may not be inputted but absolute addresses are converted in their relative form if possible.



40

NIROS


Command Meaning

X : V Places value V in address X. Value v may be either an octal number or a symbolic instruction. Very useful at inputting to a single memory address.

F (file name) Selects the file (filename) in order to work with other instructions in regard to it. Logical unit 0 isthe default value if no filename is entered.

F . Selects the active file of this port in order to work with it.

F Selects the memory in order to work with it. Addressesin the area of the processor are pointed out in this mode if they are error-free (this means 100 367 instead of 367).

GU/X Selects the disc block from the X disc address of the logical unit U. Only address 400 is accepted in this mode. Logical unit 0 is considered if U is missing.

H Selects the header block of the selected file. Only addresses <400 are accepted.

IX: (text) Input of a random symbol chain starting at address X.It has the same effect as a pseudo-assembler instruction. CTRLZ is considered “return” code in the symbol chain.

J+ Byte by byte expressionKX, Y, Z Saves the octal constant Z starting from address X and

up to and including Y.LX Listing as symbolic instruction up to address X.

Termination through ESC.MX, Y, Z Transports the contents from address X up to and

including Y to the addresses starting with Z. The initial and end field may overlap.

NX, Y, Z This command, as well as N, X, Y, Z, M have the same effect as the corresponding S commands, the only difference being that the contents of a cell is outputted if the comparison has a negative result.

OX Output of an ASCII symbol chain starting from address X. The output is terminated at the occurrence of byte <200 octal or through an ESC keystroke. A CTRLE code is outputted as “:”.

PX, Y Outputs the tape between addresses X and Y in binary format. If a hole punch is missing (no $ PTP driver), DSP will try to use the master terminal. Warning: The Y command has lead priority in the first

PXs.



41

NIROS


Command MeaningCommand Meaning

PX Punches a termination block with the start address X.X may not be null. The next blocks are punched afterwards. A PX or an Y command is a prerequisite tothis process.

P Like PX, but without a start address.QX Queries a cell continuously. Its content is constantly

outputted (octal), a swap being permitted after eachoutput. The command may be used to supervise updatesof a cell on the terminal (in the memory or on disc) while tasks run on a different terminal and alter itscontent. Termination with ESC.

R Reads the tape in binary format through a rapid strip reader in the file or memory, selected by the last Fcommand.

Each sentence composed of tapes (approx. 4 inches) isread in the buffer and generates a checksum prior tosaving the data. The first 21 words (octal) of the last breakpoint will be lost because the same buffer area is used.

RX Like R, with the difference that all address that originate in a tape are pushed so that the first wordis placed on address X. X may not be null.

SX, Y, Z Searches the constant Z between addresses X and Y. If found, its address and contents will be outputted as asymbolic instruction.

SX, X, Z, M Like SX, Y, Z, only that the content of each cell willbe masked by M (log. AND) before it is compared to constant Z.

For example: S 400, 1120, 53, 101777

Evaluates addresses 400 up to 1120 in order to obtain an indication that points to a direct reference ofaddress 53.

T $ LPT Listen on NNDUX Provides an extract of the PMAP cells to the active

file, cells that have been filled after the last breakpoint.

The output begins (in octal dump format) at address X with Y X Y + 100 with Y as start address, set by the last Y command.

Warning: The addresses are incorrect if another Y command is inputted after the breakpoint



42

NIROS


recognition. Command Meaning

V Checks the content for tapes. This command and the VX command have the same effect, just like the corresponding R commands, however, the information is not saved, but compared to the content of the selected file (or memory). If a difference is found, the address and content of the memory are outputted.

WU/X Writes the disc block selected by the last G or H command on the absolute disc address X of the logicalunit U.

WX This command is rejected if the disc address is incorrect or if a disc block has not been selected. If U is missing, logical unit null is considered.

X Termination of DSP. Existing file selections and breakpoints are removed and a new DSP selection must be performed through CR.

YX Sets the first address of 101 (octal) words from the memory area, which will be transferred to the FMAP cells of the active file header as “memory extract”if a breakpoint is identified.

ZX Searches for a relative reference. The 256 words of address X are searched based on memory reference instructions using address X as a relative address. All found instructions will be outputted in asymbolic form.

; Comment. If a row begins with a semicolon, it will be ignored by DSP. This is mainly used in order to add comments to corrected tapes.



43

NIROS


19.1.1 NO LOAD FLAGs

Device Driver

The NO LOAD FLAG will be updated during the maintenance procedure.

Bit 15 from header word 33 is now the “NO LOAD FLAG” and not the entire word anymore. This applies to all drivers besides $ RTC.

Bit 14 of the $ RTC driver has an additional meaning, if set, itindicates that the driver must be constantly loaded.

Bit 15 = NO LOADBit 14 = ALWAYS LOAD only S RTC

Index File (disc index)

Only bit 15 is now set as OP INDEX.

Bit 14 is the “INSTALL SYSTEM” function flag. If this functionis selected, bit 14 = 1. The bit returns to its prior value if“REMOVE SYSTEM” is selected.



44

NIROS


19.5 REX

REX (Real Time Executive) is loaded right after the system is switched on by the system disc. A part of this processor remains resident in the memory during its entire life cycle. The following functions are contained in the memory-resident part of the REX processor:

- Routines for selection and reservation- Subprograms of the system- INFO- Swap in / Swap out- Call handling- TRAP handling- Channel operating (peripheral control)- Processor task management- Subprograms for byte handling, move, multiplication, division- Queue management- Interrupt handling- Escape task- Character processor- Queue processor task- 10Hz task- Address conversion- Bit manipulation- Disc attempts- Keyboard routines etc.



45

NIROS


19.6 Memory Start Address for Various NIROS Components

Address Meaning

0 Page zero NIROS200 Page zero processor600 INFO table704 Select the optimal partition1010 The routine is a DISCSUB1223 Hardware or software error1301 Channel operation1466 Memory-resident subroutine table1632 Find open file1766 Start input2040 Start output2064 Output waiting not active2100 Swap out regnant user2130 Bump to task queue2255 Task activates a processor2514 Transfer next input byte2522 Transfer next string byte2527 Transfer byte2536 Save output byte2560 Save byte in A02575 Convert PCB pointer to port number2625 Move word to memory2734 Binary multiplication2747 Binary division3031 Initialize disc driver3127 Power failure3265 Time error3271 Parity error3440 Add task to queue3552 Remove task from queue3574 Release or transfer FREE MODE3676 Character management4062 ESC from the current task



46

NIROS


Address Meaning

4147 Processor ESC task4221 Queue processor task4633 Interrupt handler5102 Read/write a file5343 Read a block5506 Write a block5762 Disc error handler6066 Master port handling7640 SMD channel program10200 Processor area20000 User area36000 Block swap area36400 Header block area37000 Header expansion area37400 Subroutine swap area40000 DMR42000 ABA43323 Task queue43610 Interrupt stack43641 Character queue43711 Data File Table45531 Signal Mode Queue45551 I/O buffer47151 Channel Control Block47231 Channel program (driver)62447 Partition Control Area62447 Memory-resident DISCSUB73745 Additional LU area74454 Disc and Start Address Table75054 Call stack75077 Port Control Area75377 Common area77776 Top word of corefrom 10000 Additionally created partitions

The here indicated addresses are start addresses of various memory areas.



47

NIROS


19.7 Memory Assignment

NIROS + page zero processorINFO tableCALL routineChannel operationSubprograms of the systemBUMPProcessor activation (PROCT)QUEUE taskDQUEUE taskCharacter processingQUEUE processor taskInterrupt handlerRead/write blockSMD/CA driverBPSBUSBSA – ABATask QUEUEI/O bufferDriversCore-resident DISCSUBSPort Control AreaTop word of COREAdditional partition area up to physical memory termination



48

0600766130114662130225534403552373142214633534376401020020000360005070452634540726415075553777776

NIROS


19.7.1 Memory Assignment Description

NIROS page zero Constants and subprogram addresses required by the operating system are saved in this memory area.

Processor page zero Texts and subprogram addresses used by the processors are saved in this memory area.

INFO table System information table; this table containsessential system information for the IPL.

CALL routine DISCSUBS resp. REX routines are called throughthe CALL routine.

CHANNEL operation Various OPEN functions are performed through the CHANNEL operation, e.g. OPEN DEVICE.

SYSTEM subprograms List of the core-resident subprograms.BUMP This routine is a jump in the task queue and is

performed through JSR, CALL WONA or STI.PROCESSOR activation This routine activates a processor within the

task.QUEUE task This routine adds a task to the queue.DQUEUE task Remove a task from the queue through these

routines.CHARACTER processing The character queue is processed through this

routine.QUEUE processor task A processor task is added to the queue through

this routine.INTERRUPT table Interrupt Handler TableREAD/WRITE block Disc blocks are written on the disc or read

through these routines.SMD/CA driver These routines are channel programs for the

storage module or Cartridge.BPS Processor sectionBUS Active file within the 64 K (main partition)BSA Block Swap Area; blocks are swapped within this

memory area.



49

NIROS


HBA Header Block Area; file headers are read in thismemory area.

HXA Header Extended Area; if a second header is required, it will be found in this area.

SSA Subroutine Swap Area; subroutines are swapped within this area.

DMR DISCSUBS resident in the BASE CORE are residentin this area.

ABA Auxiliary Buffer Area; this memory area is usedfor index files.

TASK queue Task entries are saved in this memory area, 9 words per task.

I/O buffer The input/output buffers are stored in this memory area.

Drivers Channel programs are found in this memory area.

Core-resident Memory-resident DISCSUBS corresponding to the DISCSUBS list are stored in this memory area.

PORT CONTROL Port Control Blocks of active parts are foundArea in this memory area.

TOPW Top word of core; last address occupied by NIROSwithin the 64 K.



50

NIROS


19.8 Page Zero Address Content

Address Meaning

0 Indirect jump to error routine1 Start address of the interrupt address table2 Idle location3 Constant4 Parameters for NND (is set in RUN state by OPEN)5 Currently active user pointer6 Currently active task pointer7 Start of BSA10 Start of HSA11 Start of HXA These 5 addresses are set by SIR.12 Start of SSA13 Start of ABA14 Address of the Partition Control Table (SET BY SIR)15 Regnant partition pointer1617 Start address for DEBUG and DSP, now available20 Power fail restart21-41 Constants42 Mask bits for file types43 Size of Port Control Blocks44-66 Constants67 Digit mask bits70 Byte mask bits71 Port Control Area (set by SIR)72 Start of processor storage73 System Information Table74 Escape flag75 Run time limiter76 BSA changed flag77 Error flag100 Call to the system subroutine101 Check or another flag102 Symbol processing103 Add task to queue104 Reset task within queue105 Perform a channel operation106 Transfer or release available memory area107 Error stop110 COBOL DEC. EXTENSION111 Reserved partition112 Clear pointers and flags113 Byte attempt114 Attempt to input byte



51

NIROS


Address Meaning

115 String byte attempt116 Binary division117 Binary multiplication120 Swap task queue121 Decimal operation122 Error in SIR123 Decimal operation124 Decimal operation125 Find logical unit table126 Is it a digit?127 Is it a letter?130 Interrupt in interrupt131 Decimal arithmetic132 Message to I/O buffer133 Output registry content134 Read disc block135 SKIP RETURN (NORMAL)136 Save byte to registry 0137 Decimal operation140 Start input141 Start output142 Save output byte143 Start IPL144 Write disc block145 Symbol queue processing146 Save help registry to stack147 Reset and decrease stack pointer150151 Physical disc address152 Read file153 Constant 30154 Core-size flag for page registry155 Disc address of C dump156 DSP breakpoint157 Changed to falt 0 in SIR160-173 Decimal buffer174-177

The content of the address corresponding to the SUBROUTINE start address is saved starting from address 100-156

The only exception is address 151, here is the physical address of the logical unit null.



52

NIROS


19.8.1 Processor Page Zero Address Content

Address Meaning

200-245 Page zero for program load260-332 Page zero for SYSL and SIR260261 Reserved for INSTALL262 Load MBA file to a memory address263 Convert RDA to a logical ADR264 Generate DMAP scheme265 Disc block symbol in MAP266 LUVAR pointer267 LUFIX pointer270 Start address of housecleaning subroutine271 Logical unit number272273274 Config file275276277300301 Start system initialization302303 Write block during SYSL304 Search pointer305 Start address of the bad block routine306 Start address of the INMAS routine307 Memory assignment start address310 Active file assignment start address311 Start address of the build disc address and system address

tables routine312 LBZUP313 LPCA = Port Control Area address314315 DEBUG address316 Number of blocks (DISCSUBS)317320 SIR start location minus 400321-331 Constants332 LSIR333-374 Unoccupied375 Start address of the CALL routine376377-404 File history405-440 Write a message441-504 Erroneous text504-577 Unoccupied



53

NIROS


500: 111206 111211 11347 111473 11527 1112100 114107 12163510: 12251 12256 12313 12333 12337 157000 35777 165120520: 125220 44224 175122 414 30741 146414 6267 24224530: 34740 166415 406 126400 34217 45413 403 6265540: 34217 41403 24051 2224 14400 30005 102400 24027550: 30774 2144 54224 30771 24007 146400 44216 34005560: 25427 102400 6134 2224 177400 177400 177400 177400570: 177400 177400 177400 177400 177400 177400 177400 177400600: 52660 653 15 16 75537 4 41004 0610: 77776 1004 0 12 663 4562 200 22003620: 0 34 177776 62467 63475 62503 62511 62517630: 156061 77661 0 7103 1 230 402 7006640: 7103 151 366 405 0 1777760 1164 1155650: 3571 5465 3072 75045 177777 41404 4633 0660: 0 6032 75777 444 0 0 7602 0670: 7436 13026 0 7162 177400 177400 177400 177400700: 61 0 0 0 54777 30014 34005 21435

19.10 Time Sharing

The procedure sequence of the process operation is as follows:

1. A numeric symbol is inputted through SCOPE as a character.

The user inputs a command that includes the processor file name and additional information such as program or text file name or other data required by the processor. SCOPE processes this information in some cases (independent of type). SCOPE constantly searches and selects the desired processor and loads the address of BPS + 4 in the URA (User Return Address) cell of the user’s PCB.

2. The system loads the selected processor during the next time slice if it is not present in the memory, adds a breakpoint jump if a DSP breakpoint has already been set for this processor in this port and generates a JSR in the SWAP-IN routine indicated by the BPS pointer. The SWAP-IN routine performs all initialization requirements (see SWAP IN) and returns to the system, which jumps to the content of the URA address. The initial entry, meaning the first input of the command, is saved in BPS + 4, set by SCOPE. Later entries continue their operation (after JSR for SWAP IN) at the point where the processor performance has been interrupted by the time slice.

3. The processor runs until its time slice is terminated due to one of the following reasons:

a) Start input (JSR@ .STI)



54

NIROS


b) If data must be outputted and an output is currently running (CALL WONA)c) End of time slice (JSR @ .BUMP where RTL = 0)d) The user hits ESC or CTRLCe) The processor is ready and has terminated its task (CALL EXIT)f) The processor or a subprogram discovers a hardware or software error (JSR @ .FALT)g) a DSP breakpoint is reached.

Each of the first 3 statements requires saving the return address as a RE-entry in the URA during the next time slice. Each of the 3 statements causes this to be the last time slice for the current processor. SCOPE is selected through statement e) or f), statement g) selects the DSP and causes a registry save, bit carriage and a KSP 65 word area in the DSPS cells of the active file header in order to output them through the U command of the DSP.

The activities in regard to the ESC and CTRLC keys are independent of the current processor status.

a) If the processor is loaded onto the core memory for this user and ESC or CTRLC is hit, all outputs will be terminated and the interruption flag will be set (ESCF in REX page zero). The processor periodically checks ESCF: if (ESCF) is different from 0, the processor clears it and performs the desired action. If the ESC flag is ignored by the processor, the input for the next time slices is set as an ESC input.

b) If the processor is not loaded onto the core memory for this user, the system action consists of saving the URA address to the ORA (Old Return Address) and setting URA for the next time slice (after JSP SWAP-IN) so that the BPS + 2 or BPS + 3 pointer for ESC and CTRLC skips the processor control.

c) After the termination of the time slices reasons is reached due to the above (except JSR @ .FALT or DSP breakpoint), a JSR on the SWAP-IN routine of the processor is performed through the BPS + 1 pointer. The SWAP-OUT routine is responsible for saving the desired information for the next time slice (see SWAP-OUT).

19.11 Active File

The active file is a special file reserved on the system disc in order to temporarily save the processor data during a certain time slice.



55

NIROS


There is an active file for each dialog port. The size of each active file is normally determined by the size of the sections between the end of RUN (basic interpreter) and BSA – plus a block for its header.

REX allows the possibility to read from and write an active file, however, the SWAP-OUT routine of the processor must define the length of the written content. The processor may not use the active file if it only has little or no temporary memory for saves between SWAPs. If the processor has no temporary save requirements, it has pointers to the JMPO and 3 requirements in the BPS cells and BPS+1. If the processor requires 1018 or less cells as temporary memory, cells PMAP up to PMAP + 1008 of the active file header may be used to this purpose. The processor must read the active file header in HSA or APHA, copy its temporary memory and write the header on disc if this method is chosen.

The real disc address of the active file address is included in the AHA of the user’s actual PCB.

If the processor has to save more than 1018 words between swaps, the active file must be used.

19.12 SWAP IN

Whenever a user time slice begins, BUP points to the user PCB, the selected processor is loaded onto the core memory (unless already in the core memory) and the system performs a subprogram jump through its SWAP-IN routine to the BPS address. If the active file and/or its header is required for saves during the time slices, the SWAP-IN routine must read it in the core memory and perform all initializations. A LOAD USER subroutine is included in REX and may be called through the CALL LUSR command. LUSR reads the active file header in AFHA (or HBA, is AFHA is not assigned) and if its type (5 bits of low value of word type) matches the processor, the active file is also read in the memory and returned by SKIP. LUSR also saves the 6 DA (Decimal Accumulator) cells and every save area specified by the AFSETUP during the last SWAP-OUT (see SWAP-OUT). LUSR returns without using SKIP if their types don’t match.

The SWAP-IN routine may mandatorily also read the active file header or another file or header in its core memory, or perform a simple 0,3 JMP if no initialization is required. The INFO table contains a pointer to AFHA; this cell indicates HBA if AFHA is not assigned.



56

NIROS


In some cases, the SWAP-IN routine must know if the 1st or a consequent time slice is influenced. This may occur by comparing the value from BPS + 4 with the address in URA. An equality indicates that it is the 1st entry (initial entry).

19.13 SWAP-OUT

After the reasonable termination of all time slices (see TIME-SHARING – due to errors or breakpoints), the system generates a JSR for the SWAP-OUT routine of the processor as indicated by the BPS + 1 pointer. If no WRAP-UP is necessary, BPS + 1 may point to the JMP 0,3 instruction, otherwise the SWAP-OUT routine must save all necessary information for the next time slice. The SWAP routine will either:

a) Copy a temporary memory area to page 0 of the PMAP up to PMAP + 100 rows of the active file header

and/or

b) generate a KSP address list and call AFSETUP in order to read the active file header and establish its disc address, so that the system may write the active file onto disc.

A SKIP return to the system from the SWAP-OUT routine of the processor causes the system to output the active file. If the active file header suffices for the temporary save, the SWAP-OUT subroutine must output it and perform a return without SKIP.

The active file usually contains DSAF blocks, including headers, where DSAF (Default Size of Active File) is defined as an interactive port driver in the attribute table and may be altered by DSP. The active file header contains the real file addresses of these blocks, but a different processor may leave them behind, scattered within the last 200 words of the header. Each cell located in the last half of the header is “linked” to a memory header in regards to CORA. Moreover, each disc address, that is negatively described in the active file header, shows that it is intuitive (the block is not transported in or outside of the core memory). The AFSETUP routine is required in order to generate the active file header.

CALL AFSETUP must therefore be called, while registry A2 contains a pointer to the KSP address list. This list consists of word pairs, where each pair points to the 1st and last word of the KSP area that must be swapped. The termination of the list is indicated by the



57

NIROS


1xxxxx8 value. Each pointer within the list must be greater in value than the previous one. If the lower 15 bits of the termination word are not equal to null, they will be used as start address of a core memory area of up to 1008 words, where PMAP cells of the active file header will be saved and the next word from the list shows the size of the save area (words – 1). The start address and the size are saved in DASA + 6 and DASA + 7 of the header or, if DASA + 6 it set to null, the save area does not exist. In each case, the decimal accu (DA) is saved in the first 6 DASA cells. ALLOCATE is called by FSETUP if the active file is too small for accepting a save area.

AFSETUP performs a return without SKIP if the active file is too small and if there are not enough available disc blocks in order to assign it via system ACCOUNT. In this case, AFSETUP jumps to JSR a .FALT (error no. 13).

AFSETUP sets CORA to the first KSP address of the active file area in the KSP and positions the disc addresses in the header so that active disc addresses exist for transporting blocks. All other disc addresses are in negative form within the active file header. The TYPE word of the active file header is set to the processor type.

19.14 INPUT/OUTPUT

All I/Os each have an online buffer for each channel. The pointer located in each PCB of a word determines the location of the buffer and



58

NIROS


the next character position. It is forbidden for a processor to query or alter an I/O character placement. System subroutines exist for all I/O function requirements.

Start input is called through the JSR@ .STI instruction. The user is superseded and the input is made possible. The processor is called (SWAP-IN) and control returns to the last instruction, terminated by the user through the RETURN key in order to terminate the input. The processor may change the current RETURN key as EOM key to a desired code by placing the code in the lower half of the PCB RDE cell.

An attempt of input onto byte is performed by JSR@ .ACIB in order to attempt input to each byte. The byte is written in A2, where the upper bit of the ASCII code is set to “1” and nulls are located in the upper half of the registry. Blanks (2408) are ignored. The EOM code (usually RETURN), 2158,shows the termination of the input.

An attempt on character bytes is performed by JSR@ .ASCB. It works in the same way as ACIB, only that characters are ignored. Each character inputted by the user is passed on to the processor. If A0 = null, so when ASCB has been called, the byte pointer is not increased and will attempt to reach the same byte during the next use of ACIB or ACSB.

Wait until the output is ready, called by CALL WONA. This call must be made before one of the following output routines if the data has not yet been proven to be inactive (e.g. following an initial entry or a START INPUT). WONA interrupts the user if he is running an output. This allows the proceedings determined by the processor, however, if an output is running, it prevents a second output from overlapping with the already processed output.

Save byte output through the call of the JSR@ .STOB instruction, where the bytes from the lower half of the A2 registry are saved in the user’s I/O buffer. The byte is written in A0 and the word’s upper half is set to null. Once the buffer is full, STOB overlaps the last byte of the buffer instead of increasing the pointer and thereby setting it at the end of the I/O buffer.

The output of text messages is called by JSR@ .MSG followed by TXTF, a “text” pseudo-instruction. The specified “text” string is copied in the user I/O buffer and the return is performed on the next instruction following the text. Neither STOB, nor MSG,



59

NIROS


increase the output byte pointer if the byte that must be saved is null.

“Fixed” text outputs deliver all available “fixed” messages as long as their number is contained in the A1 registry.

A conversion from integer to ASCII is called by CALL CIA, the integer being thereby located in A1. Registry A0 contains the basis to which to convert and A2 must contain a minimal number of desired digit positions. Nulls located at the start are ignored, the result being filled with blank spaces at the start until the sum of the (A2) characters is reached. If (A2) = 0, no blanks will be added at the beginning. Letters are used according to their value if the basis is 10, e.g. A = 10, B = 11 etc.

An output start is called by JSR@ .STO after the above routines have been used in any desired combination in order to save ASCII code in the user I/O buffer. The ASCII character chain must be terminated with a null byte (clear A2) and must be preceded by JSR@ .STOB. Only then may the output be started. (This is necessary when the last output has been generated by a JSR@ .MSG or a CALL MESSAGE.)

All above routines destroy all registry contents if not mentioned otherwise.

19.15 Data Access

Data file transports are performed by processors through system subprograms. These subprograms enable the opening of present files, the creation of new files and their removal. Processors may access data files and update them through system calls or directly access data through READ and WRITE block subprograms. Almost all data accesses are performed through channels. Channels allow the system to guarantee that the files will not be deleted by a user while another one accesses them. The I/O channel allows devices to be considered data files by the processor. Therefore, no updates of the user software are necessary when adding a device to the system. A file may be opened in 4 ways by a channel.

CHANNEL OPEN opens a file on the channel. If the file is not the current one of the user but an account for it exists, the current user will be afflicted. If the file is read-only, the information will be stored in KSP and the user will receive an error when trying to write



60

NIROS


to this file. The LDAT cell will be set to the current system time value and cell NTAC will be increased.

CHANNEL OPEN REFERENCE opens the file but only as a reference. The current user will not be afflicted; cells LOAT and NTAC will not be altered and the channel will be set to read-only.

CHANNEL OPEN UPDATE has the same effect as OPEN apart from the fact that it runs even if it presents errors pointing to the read-only characteristic of the file.

CHANNEL OPEN LOCK has the same effect as OPEN apart from the fact that all other users are blocked access to this file, but an error will be outputted in case that another user has already opened the file.

A new file may be created through the CHANNEL BUILD system call. The FILENAME data will be built for the required channel. Errors occur for incorrect file names, locations outside of the disc area etc. If the file name is correct, BUILD marks the old file as replaced. If the new name matches the FILENAME! pattern and if both types and ACCOUNT numbers are equal, the present file will not be replaced. The new file remains marked according to the BUILD call until it is closed (CLOSED). A newly created file must be closed by the processor through a CHANNEL CLOSE instruction before the process of returning to the system is terminated. If a channel has been exitted with CLEAR instead of CLOSE, the created file is lost and if a new file should have replaced the old one, the old one is once more saved in normal status mode.

Each channel may be cleared by the CHANNEL CLEAR call (loss of content). All channels may be reset by the CALL ALL CLEAR system command.

ALL CLEAR is rarely used by means of the processor since the system clears all channels after the termination of the processor.

If the processor desires to delete a file, it calls the CALL DELETE system routine. DELETE checks if the file is open for any users. If not, DELETE gives notice to the user account and returns the corresponding disc blocks to the system. If the file is in use, it is marked for removal once the last user CLOSES or CLEARS the channel where it was open.

Data may be transferred to a file in 2 ways: a “high” structure means that data is transferred from and to the file through CHANNEL READ ITEM and WRITE ITEM. You may read (write) from (to) an individual file to (from) a file address from (to) a specified memory address. If a device



61

NIROS


was opened on a channel, the system automatically transports the information onto the device, so that the processor must not differentiate between the device and file system anymore. For quick access, the processor may specify the data block of a file directly through the file header and afterwards use RBLK or WBLK for the transport of 25610 words from or to the file.

A processor may use the FOFI and FOFC (Find Open File Initialize and Find Open File Continue) in order to establish if a specified file is opened by any users. A processor may establish if any file is opened on a logical unit, since the disc address is set to null if FOFI is called.

20 IOCS

The operating system supports all user in/output operations through the Input Output Control System, IOCS for short.



62

NIROS


The user is offered no support by IOCS during the processing of desktops, because the in/output data of the desktop is not organised as a file system.

Neither does IOCS offer support during magnetic tape processing. The user has to program the magnetic tape physically (through CALL) and obtain the data carrier and data this way.

The logical IOCS assumes the management of databases for magnetic discs, printers and punchcards. Moreover, all file organisation methods described in the previous chapter are also supported. What does this mean for the user? He may work with the information inside his files from a logical, and not from a physical, point of view. A list of instructions regarding file processing is available to the user in the form of a BASIC manual.

20.1 Channelling Concept

Data channels control the processing of files. 14 channels (0 up to 13) are made available to every participant.

Only one file may be opened per channel. Disc files may be opened simultaneously on different channels (file-sharing), no matter if the file is opened by several programs (participants) or inside one program on multiple channels.

In contrast to this, printer and punchcard files may only be opened a single time, because these peripheral devices can only be used by a participant at a time.

Feature: Data channels 0 and 1 are mainly occupied when working with TAMOS.

20.2 Task

A task is created (added to the waiting queue) by performing the following instructions:



63

NIROS


QueueTaskTCB PointerStart priorityPriority incrementA3 Registry

Here is “Task” either the name of a system task specified in the software definitions or the memory address of a task entry point. The TCB pointer word may be null if the task uses no Task Control Block or -1 if the general task pointer (RTP) should be used. The Task Control Block is normally the Port Control Block. If the start priority is null, the effective priority (EFP) of the concerning TCP is used.

The carry bit and registers A0, A1, A2 and A3 are saved in task nodes and may be used for transferring parameters to the task. After the return from queue, registry A2 will point to the new waiting queue node.

Whenever a user is swapped, the system tasks within the queue are reordered in order to yet again place the user task in correct order, if necessary. The new order is based on searching within the task waiting queue for a PRIL entry unequal to null. The priority increase value (PRIL’s upper 6 bits) is added to the temporary priority value (FLAP’s lower 10 bits); thereby, the priority limit (PRIL’s lower 19 bits) may not be exceeded. The priority limit may not be higher than the highest priority value of the user tasks.

The new task priority is then compared to the current priority of the other entries in the queue and the entries are ordered in such a way that the task with the highest priority (apart from the user which has just been swapped) be first.

ATTENTION: The start priority of a task that must be ordered within a waiting queue may not exceed the current priority of the task calling the queue. An interrupt handler may add a new task to the order if its start priority is lower than 1777 (octal).

20.3 Entries in the Waiting Queue



64

NIROS


Accumulator 2

Accumulator 1Accumulator 0Accumulator 3Address, carry bitFlag, priorityTask pointerTSB pointerChain pointer

Registry A2 points to the entry with the next higher priority (or to TASKQ if A2 has the highest priority). The pointer points to cell 0 of the entry. LINK points to the entry with the next lower priority. The pointer of the task with the lowest priority points to the fix, unused entry with priority null.

Cell Meaning

0 – 3 Are used to transfer parameters to the task if they are created for saving the registry when the task isinterrupted.

4 Contains the start address of the task once it is created and is used as return address if the task isinterrupted. The address is shifted 1 bit to the leftand the carry bit is saved in bit 0 of the cell.

5 (FLAP) Bits 0 to 9 contain the current priority of the task.The upper 6 bits are used as flags as follows:Bit Meaning15 Possible task conflict14 Task is a processor13121110



65

01234FLAP = 5TASK = 6TCBP = 7LINK = 8

NIROS


6 (TASK) Points to the start address of the task. The task attribute lies prior of the entry point.

Cell Meaning

7 (TCBP) Points to the Task Control Block (TCB) of the userfor whom the task works or is equal to null for a system task.

8 (LINK) Points to the task entry with the next lower priority.This cell is equal to null if the task is unused, indicating the end of the waiting queue.

20.4 Partial Printout of a Task Queue

53400: 53357 0 0 0 0 0 0 053410: 0 53370 0 0 0 0 0 053420: 0 0 53401 0 0 0 0 053430: 0 0 0 53412 0 0 0 053440: 0 0 0 0 53423 0 0 053450: 0 0 0 0 0 53434 0 053460: 0 0 0 0 0 0 53445 053470: 0 0 0 0 0 0 0 5346553500: 0 0 0 0 0 0 0 053510: 53467 0 0 0 0 0 0 053520: 0 53500 473 10020 20 7777 4534 14020053530: 2256 75577 53511 75577 200 10401 60006 453453540: 140200 2256 75577 4723 75577 40 0 1020453550: 10762 1600 4371 75577 53522 0 0 253560: 0 4 0 0 0 0 0 053570: 0 0 0 0 0 0 0 0

The task entries start with the highest address within the memory address reserved for the task queue. In this case it is address 53554.

Address Meaning

53554 Chain pointer (link)53553 Task Control Block = Port Control Block53552 Task pointer e.g. 4371 = 10 Hz task53551 Priority e.g. 1600 = ESC task53550 Task start address within the processor53547 Accumulator 353546 Accumulator 0



66

NIROS


53545 Accumulator 153544 Accumulator 2

20.5 Removing an Entry from the Waiting Queue

Once a task is done, it must be removed from the waiting queue by performing the instruction

D QUEUE

There is no returning from the DQUEUE instruction. The concerned task entry will be extracted from the task and added to the chain of free entries. The program process will be continued with the next task within the waiting queue.

20.6 Task Priorities

2021 Power failure interrupt handler

2020 – 2001 Device interrupts

2000 Character processing (in REX)

1777 – 1602 System tasks that make no attempts to the disc mayeach have these priorities.

1601 Task of reorganising the waiting queue

1600 Processor Escape Task

1577 – 1400 System tasks that make attempts to the disc, mayeach have these priorities.

1377 – 0001 Area for user tasks and dynamic priorities (with apriority increase value different from null).Tasks having a priority lower than 400 are regarded as background tasks.

0000 The used task has the null priority.



67

NIROS


21 Interrupt Handling

Interrupt Handling is continuously supported by computer hardware. The computer handles the interrupt number at the time of an interrupt instruction and adds the start address of the “Interrupt Handler Table” (memory address 1) to it. The computer reads the address of the corresponding interrupt routine from the table and directly ramifies there. Registry 4 and the instruction counter, together with the carry bit, will be stored in the hardware stack beforehand.

Each interrupt routine must return to address “INTS” (IMP @ INTR). The prior states of the registry and the instruction counter will be restored here and the program will continue running from the point where it was interrupted.

An interrupt on multiple levels is possible. The system’s PUSH and POP subprograms have been created for this purpose. PUSH stores the hardware stack in a software stack, sets the INTSS flag, releases the interrupt again and returns. POP must be performed after the interruptible interrupt routine. This program resets the software stack and continues running the normal program. The stack will be stored in SIR and its length will depend on the number of drivers having different “mask bits”.

“Character Processing” (PC) is also interruptible. The computer stack will be saved in a TASK QUEUE NODE here and the “PCR” flag will be set.

21.1 Parity and Time Error Interrupts

The parity and time error interrupts are not available in NIROS anymore, but in the XVSLAR and XVSLAD service modules. NIROS now contains only the computer’s LED manager.

The computer checks all data in its rear panel for uneven byte parity, which means 2 bytes per word. When it identifies an even parity, it will trigger a parity error interrupt.

A time error interrupt will be triggered if an addressed unit, memory or controller does not send a strobe or exit signal after 10 µs.

The error notification occurs in the following way:



68

NIROS


P – T – ERROR (CORE) or (PERIPHERAL)

Error registry Return address

Registry 0 Registry 1Registry 2 Registry 3

21.2 System Time Interrupt

A system time interrupt is generated by the computer interface. The system time frequency and the start of time are set after the start of time-sharing. The 10 Hz task is called through a 400 in the character queue (interrupt task).

21.3 Power Failure Interrupt

The processing routine sees a power failure during the IPL (Initial Program Load) and a power failure during the start of the time-sharing executive differently. Cell 0 is used as flag. After REX is started, a subprogram jump to the FAULT routine will be contained in the cell; as opposed to this, the cell content = 0 in the IPL phase. A power failure during the IPL routine causes the computer to shut down and with it, a delay of the initial program loader. In case of a power failure in REX, the current interrupt state is saved in NAINZ and the power failure interrupt is released. Afterwards, the program sets the general interrupt lock (IP) and the help registries are stored in the stack. The address of the power failure routine is set after address 20 and the emergency power supply is activated. After the termination of this process, the computer is shut down. An exception is power failure during power start. The IP will not be set and the help registries will not be saved in the stack in this case.

21.4 Power Start Routine

The power start routine will turn on the emergency power supply and release the power failure interrupt, so that the power failure is recognized during the power start. The system clock is afterwards started. The output on screen will indicated “P-FAIL”, meaning that a power failure has taken place. The power failure routine is continued by hitting a random key as confirmation. If the disc drives are READY, all peripheral drivers will be restarted. At termination, the previous interrupt state is rebuilt and a subprogram jump to the FAULT routine in address 0 is saved. The stack pointer is decreased and the system continues working in time-sharing mode.

21.5 E/A Interrupt



69

NIROS


SIR loads the address of its interrupt routine in the Interrupt Handler Table when the drivers are loaded. The program is saved during an E/A interrupt directly onto this address. The interrupt routine must be terminated with a jump to INTS (JMP @ INTR) or started resp. terminated with PUSH and POP.

23 File Label (File Header)

The file label contains all information required by the operating system for the processing of certain information. It has the following structure:

WordAddr.(octal)

Length in words

Abr. Content/Structure Represen-tation

0 – 6 7 Name File name ASCII7 1 ACNT Account

|15,14|13,12,11,10,9,8,7,6|5,4,3,2,1,0| bit

Account user number

Account Group Number

Privilege area10 1 TYPE File type / File protection

|15|14,13,12|11,10,9|8|7|6|5|4,3,2,1,0| bit

15 – available14 – read-protected13 – read-only12 – copy-protected11 – read-protected10 – read-only9 – copy-protected8 – executable processor7 – load active data if processed6 - start input of the first storage (SWAP in)5 – available4,3,2,1,0 – data type 1

Bit 9 – 11 for users in the same privilege areaBit 12-14 for users in a lower privilege area

binary



70

NIROS


WordAddr.(octal)

Length in words


11 1 NBLK Number of disc blocks (sectors) incl. labels currently assigned to files

binary

12 1 STAT File status

|15|14|13|12|11|10|9,8,7,6,5,4,3,2,1|0| bit

15 – file is being created, not terminated yet14 – a file replacing the current one is being created13 – file is being deleted as soon as it is closed12 – formatted file11 – available10 – file cannot be deleted9,8,7,6,5,4,3,2,1 – available0 – expanded file (formatted)

binary

13 1 NITM Number of file words per data sentence (only at formatted files).

binary

14 1 LRCD Length of file sentences expressed in words (all data files).

binary

15 1 NRPB Number of sentences per block (only formatted files, else = 0).

binary

16 1 NCRDup to 3.2

Number of assigned sentences for linked files, highest written sentence number at formatted files, number of data-occupied blocks (sectors) at text files.

binary

17 1 COST File cost = the sum charged to another user when he opens this file. The number is a multiple of 10, so that the maximum sum remains DM 999,90.

BCDwithoutVZ



71

NIROS


WordAddr.(octal)

Length in words


20 – 21 2 CHGS The (cumulated) charged sum of other users for access to this file. The highest value can be DM 99.999.90 before the lowest index is ignored since the sum representation is limited to 6 digits.

BCDFloating point

22 – 23 2 LDAT Date of last access. Is replaced at each “open”.Format:1st word = hours since 1.1.19732nd word = time until the next full hours in tenths of a second

binary

24 – 25 2 CDAT Creation date of the file. Is set at the creation of the file.Format: as LDAT.

binary

26 1 NTAC Access counter; is incremented with “1” at each file opening.

binary

27 1 CATR Catalogue sentence number30 2 CLAS Catalogue class31 1 DSID Disc ID32 1 NLF. Load flag (only for drivers)33 1 SINH Swap inhibit (index header optimized = -1) binary34 1 SIZE Number of assigned sentence lengths binary35 1 HASH Checksum36 2 NRCD Number of sentences per file40 10 DASA Decimal Accumulator Saver Area binary50 20 DSPS Memory for DSP64 2 FFDR First available data sentence (index file)66 2 NOFRC Number of available sentences by CHAIN (only

index files)70 101 FMAP Data file format 272 1 FRDR First available data sentence (only index

files) 2



72

NIROS


WordAddr.(octal)

Length in words


171 1 HTEM Reserved for temporary saves, for the allocate, deallocate and account-look-up system subprograms.

binary

172 1 STAD For files in machine code (autonomous or executable) = start addr. of the program. If bit 15 is set, no start address has been assigned.

At a peripheral driver file = real memory address of the entry point of the initialising routine.

At a system driver file = memory address of the routine for ease of troubleshooting, bit 15=1.

In case of any other files are all bits STAD = 1.

binary

173 1 DREP If a file is replaced by another file with the same name, this word is placed onto disc address 3 of the replacing file header.

binary

174 1 DSAF Standard length of active files. Is only used for active files in order to indicate the length of active files (number of blocks), pointed out in the attribute table of the port driver. This number of blocks is determined by the active file during the initial program load and, whenever a user logs off, the length of the active file will be restored to this value.

binary

175 1 CORA This is the core memory address of the first data block, and all further data blocks start at intervals of 400 words (octal) from the first data block. If a proper block of the core memory address remains available, no disc address will be assigned to it and the corresponding cell of the disc address list (starting at 200 octal) is = 0. In case of text files and random linked files CORA is always 0.

binary



73

NIROS


WordAddr.(octal)

Length in words


176 1 UNIT Number of log. devices (logical unit) saved in the file.

binary

177 1 DHDR Real disc address of the file header (3 for the indicated log. device).

binary

200 – 377 128 Disc Address List (disc address list)Cells 200 to 377 contain the real disc addresses (of the log. devices indicated by UNIT) of each data block of the file, except if the file is expanded or linked. In case of linked files, this disc address does not point to data blocks but to header extender blocks, each containing up to 256 disc addresses of data blocks.

The first address in this list points to the expansion of the first 256 data blocks etc.A linked file has no disc address list; all NBLK-1 data blocks are located on consecutive disc addresses after the termination of the header.

binary



74

NIROS


1) Structure of File Types

File types are stored in 5 bits as follows:

Value (octal) File type Abbr.03 Standalone processor or program A02 Basic processor or program B32 Linked or indexed data files C31 Formatted data files F00 Permanent system files P01 System processor or file S30 Text file T36 Peripheral Driver Crossed S05 Z 80 assembler O

2) Structure/content of FMAP a) Formatted data files

Each word in the FMAP indicates the format and the relative address of the concerning data element from the sentence.

Word 0 from the FMAP defines element 0 from the sentence, word 1 from the FMAP defines element 1 etc.

Structure of the FMAP word:

|15,14,13,12,11,10,9|8,7,6,5,4,3,2,1,0| bit

15,14,13,12,11,10,9 – format of the data element.

8,7,6,5,4,3,2,1,0 – relative address of the data element (number of words from the beginning of the sentence to the beginning of the data element).



75

NIROS


The format of data elements is as follows:

Value (octal) Format000 Termination of format build004 Floating point – binary number005 Decimal number (BCD)011 ASCII character chain012 Binary number without sign077 File label

b) Indexed data files

The following information about the indexes is contained in the FMAP:

Addr. (octal) Content70 Number of indexes (max. 15)71 Number of current data sentences located in the

chain of available sentences.72 Sentence number of the first data sentence in the

chain of available sentences.73 Number of the first real data sentence.74 Label of the field, number of OBs/blocks and

length of the OB for index 1.

|15|14,13,12,11,10,9|8,7,6,5,4,3,2,1,0| bit

15 – label: 0 = main or large field 1 = discrete field

14,13,12,11,10,9 – OBs/block8,7,6,5,4,3,2,1,0 – length of OB

75 Start of index 1 of the discrete field76 First available block in index 1 of the large

field77 First available block in index 1 of the discrete

field78 – 167 4 words for each of the indexes from 2 to 15,

with the same structure as the words from addresses 74 up to 77.



76

NIROS


170 Available

24 DISCSUB

24.1 General

A DISCSUB file exists on each system disc and contains all system subprograms. These subprograms are used as a whole by the operating system and in part by the user. The BASIC (see BASIC manual) contains CALLs which perform the subprogram jumps to corresponding subprograms.

These system subprograms either have a size of 256 words (1 disc block) or a size of 512 words. In order to increase the system’s throughput and to save constant loads of subprograms, certain DISCSUBS must be kept resident in the memory.

If the subprogram has a maximal size of 256 words, it will be loaded after SSA; if it is an extended subprogram, the first block after HXA and the second block after SSA will be loaded. A maximal nesting level of 8 subprogram calls may be programmed in case of subprogram calls.

If a DISCSUB calls another DISCSUB, SSA will be written on disc in order to save all temporary memory cells.

If an extended DISCSUB is called, only SSA will be saved. After the call of an extended subroutine, one must make sure that no further extended subroutines are called and that the first block of the first extended subroutine is not used further.

Disc-resident subprograms are relatively slow, since they require at least one disc access in order to load a subprogram onto memory.

A subprogram call nesting requires 3 disc accesses in order to:- write the calling subprogram onto disc,- load the called subprogram onto memory and- load the calling subprogram once more when the called program is terminated.



77

NIROS


Address 0 = DISCSUB numberAddress 1 = Start address of the first DISCSUB (4467)Address 2 = DISCSUB number (13) of the second DISCSUBAddress 3 = Start address of the second DISCSUB (117) within the blockAddress 4 = DISCSUB number (47) of the third DISCSUBAddress 5 = Start address of the third DISCSUB (227) within the blockAddress 6 = Length of the DISCSUB complementAddress 7 = Begin loading the first DISCSUB, including address 7, onto

memory

If other numbers are located before the DISCSUB number, they will have the following meaning:

2xxx = basecore-resident only1xxxx = DISC-resident only2xxxx = load onto memory linked4xxxx = DISCSUB is extended (larger than a block)4xxx = alternate version for core residency

Determine, at which memory address the DISCSUB has been loaded. Determine the DAT start address with the SYSMOD processor. Add to this start address the number of the DISCSUB.

The result is the memory address starting from which the DISCSUB is loaded. The content of the corresponding DISCSUB is located at this address, for example, address 7.

Example: SAT start address 75254 DISCSUB no. + 7 Memory address 75263

The content of the memory address is 4467.

One must work with the DSP processor after determining the memory address.



78

NIROS


24.3 DISCSUB MAPPING

24.3.1 Introduction

Operating systems (NIROS) up to release 3.3 version 5 saved the core-resident DISCSUBS in a directly addressable memory area (64 KB).

In order to overcome the idea of working directly with the memory through directly addressable memory areas, core-resident DISCSUBS have been saved in the memory extension since release 3.3 version 6.

The DAT (DISC ADDRESS TABLE) and SAT (START ADDRESS TABLE) tables indicate the absolute disc address, as well as its start address in the SSA, if the DISCSUB is disc-resident. If the DISCSUB is core-resident, the RDAs will be represented inverted in the DAT and the SAT will contain the start addresses of this DISCSUB in the memory.

Memory assignment up to release 3.3, version 5

I---------------------------IPAGE ZERO

I---------------------------INIROS

I---------------------------IPROCESSOR PARTITION

I---------------------------IBSA UP TO ABA

I---------------------------ITABLES, DRIVERS, FREENODES, PCT, PCB ...

I---------------------------ICore-resident DISCSUBS

I---------------------------IDAT, SAT

I---------------------------I

I---------------------------ITOPW

I---------------------------I



79

NIROS


24.3.2 SYSMOD Selection

The decision, whether DISCSUBS should be mapped and with it organised a new, linked, structure of the memory area, is taken under SYSMOD.

If the physical memory size is equal to 64 KB, which means there is no ADDRESS MAP REGISTER, no DISCSUBS may be mapped.

SYSMOD . 3.3CHANGE HARDWARE SPECIFICATIONS ........................ 0CHANGE SOFTWARE SPECIFICATIONS ........................ 1CORE ALLOCATION MAP ................................... 2EXIT .................................................. 3 USER: 1

SYSMOD . 3.3ACTIVE FILE SIZE ...................................... 0DRIVER ................................................ 1SIZE OF MAGTAPE BUFFER ................................ 2PORT CHARACTERISTICS .................................. 3DATA FILES ............................................ 4PARTITIONS ............................................ 5CORE RESIDENT DISCSUBS ................................ 6QUEUES ................................................ 7TIME SLICE ............................................ 8DECIMAL SIGN .......................................... 9COMMUNICATIONS ........................................ 10DIAGNOSTIC FILE ....................................... 11 USER: 6

SYSMOD . 3.3DISPLAY CORE-RESIDENT DISCSUB LIST .................... 0INSERT A = IN CORE-RESIDENT DISCSUBS LIST ............. 1REMOVE A = FROM CORE-RESIDENT DISCSUBS LIST ........... 2MAPPED DISCSUBS ....................................... 3 USER: 3 .CURRENT VALUE: NMAP DISCSUBS IN EXTENSION IF AVAILABLE (Y OR N): USER: Y

The CORE-RESIDENT DISCSUBS rows always indicate a value different from 0, since not all DISCSUBS may be stored (e.g. REQUEUE).



80

NIROS


The SYSMOD list indicates how many KB are occupied by DISCSUBS in the larger than TOPW memory area for memory assignment purposes.

24.3.3 SYSMOD Memory Assignment List

CORE SIZE IN KB ............................. 96 140UNUSED CORE IN EXTENSION IN KB .............. 0 0 140MAPPED DISCSUBS ............................. 9 11 127AREA OF PARTITIONS IN EXTENSION ............. 28 34 73TOPWORD OF CORE ............................. 72776COMMON AREA ................................. 1024 2000 70777PORT CONTROL AREA ........................... 160 240 70537CALL STACK .................................. 26 32 70505DISCSUBS ADDRESS TABLES ..................... 384 600 67705AREA DEPENDING ON LU’S ...................... 359 547 67136PARTITION CONTROL AREA ...................... 148 224 66712CORE-RESIDENT DISCSUBS ...................... 688 1260 65432DRIVERS ..................................... 5028 11644 53566ALM CHANNEL CONTROL BLOCKS .................. 32 40 53526I/O BUFFER SIZE ............................. 640 1200 52326SIGNAL NODE QUEUE ........................... 40 50 52256DATA FILE TABLES ............................ 760 1370 40666CHARACTER QUEUE ............................. 36 44 50622INTERRUPT STACK ............................. 25 31 50571TASK QUEUE .................................. 145 221 50350UNUSED CORE ................................. 2203 4233 44114BLOCK BUFFER AREA (ADDR. IS .BSA) ........... 3148 5114 36000BASIC USER AREA (ACTIVE FILE SIZE) .......... 7168 16000 20000

24.3.5 Setting Up DISCSUBS

In the case of MAPPED DISCSUBS, a DMR buffer of 2 KB will be created between SSA and ABA at the system initialisation (SIR).

The information of the 1st KB page of the DMR will be stored in word 7 (address 607) of the info table. The content of this address is 0 if no MAPPING has been generated.

“C2MD” will be the first available page, indicated by TOPWORD OF CORE, in word 7 (address 407) of the 2nd CONFIG block.



81

NIROS


Setting up core-resident DISCSUBS through SIR is a process performed in the order that the DISCSUB numbers are entered in the CONFIG block.

The process of transferring DISCSUBS onto start addresses is performed for each DISCSUB in the CONFIG block 3 list. If the available area is too small, the DISCSUB will be transferred to the DMD area. If partitions exist, DMD will be located over the additional RUN PARTITIONS.

Each DISCSUB will be entered in the DAT of the RDA.

The start addresses will be saved onto memory during the SAT.

If the DISCSUB is disc-resident, the corresponding entry from the SAT will contain SSA’s start address.

If the DISCSUB is core-resident and may not be saved onto expanded memory (core-resident flag = 2000), the corresponding entry from the SAT will contain its start address from the memory.

If the DISCSUB must be saved onto expanded memory, the corresponding entry from the SAT will contain a start address located in the DMR.

The pages for MAPPED DISCSUBS will be entered in the MAT table.

24.3.6 Calling DISCSUBS

The DISCSUB is checked for core-residency through the entry in the MAT (x) during the DISCSUB call (x). MAT continues to deliver a page number (P) if DISCSUB (x) is MAPPED, which means it is located in the DMD or DMR area.

The page number (P) is written in CALL stack, otherwise, null is written.



82

NIROS


Afterwards, the PCT addressed by RPP is modified in such a way that both entries corresponding to DMR are replaced by page numbers (P) and P + 1 and loaded onto ATT.

During the return from a DISCSUB, ATT will be reset according to the stack information if the calling routine has been a MAPPED DISCSUB.

Pointers, flags and tables

A table, flags and pointers have been generated for the DISCSUB MAPPING.I----------------I----------------------------------------------------II INFO and DMR I Page number is the first page of the DMR. II (Word 7 of the I It is 0 if no DISCSUB MAPPING is available. II info table) I II----------------I----------------------------------------------------II C2DMD I This address contains the page number of II CONFIG block I the DMD. II----------------I----------------------------------------------------II DAT I The entries for core-resident DISCSUBS are II I not complemented anymore. II----------------I----------------------------------------------------II MAT I MAP ADDRESS TABLE per DISCSUB entry (page no.) II I Bit 15 = 0 DISCSUB is disc-resident II I 15 = 1 DISCSUB is core-resident II I 14 – 0 = N N unequal to 0, where N is the page II I no. of the MAPPED DISCSUB. II I If N is equal to 0, the DISCSUB is II I core-resident, but not MAPPED. II----------------I----------------------------------------------------II B (2000) I BASE CORE ONLY II I A DISCSUB represented by such a number may II I not be stored. II----------------I----------------------------------------------------I

RIP = Regnant Partition Pointer

24.3.7 Further Modifications

Incorrect HW-parameters: If PARTITIONING or MAPPED DISCSUB is activated and the phys. memory size is smaller than allowed by the configuration,a minimal configuration is loaded after the PARTITIONING SWITCHED OFF INCORRECT CONFI-GURATION SPECIFICATION message.

Only the master port will remain active.



83

NIROS


Only PARTITIONING has been deactivated until now.

Buffer overflow: A minimal configuration is loaded for traps 111 and 121 so that the master port may establish a new configuration through SYSMOD.

TRAPs: The address of CALL for the disc and memoryaddress has been outputted for core-resident DISCSUBS until now during TRAPS in deactivated DISCSUBS.

The FAULT DISCSUB has been modified in such a way that, instead of the address, the DISCSUB number is outputted.

25 File Organisation Methods

IOCS (Input Output Control System) is a part of the NIROS operating system that controls and monitors data access. Disc files may be processed properly through time-sharing.

Following data organisation methods are supported by IOCS:

- sequential files,- formatted files,



84

NIROS


- relative files,- index files and- text files

25.1 Sequential Files

The sequential file organisation method is mainly used for storage devices that do not allow data access.

These are: Files on magnetic tapes andPrinter files

Since this organisation method allows minimal access time, it may also be used by disc files if these must be processed sequentially.

25.2 Formatted Files

The “formatted” organisation method is generally only usable for files on magnetic discs. Each record in the formatted file has the same format, as defined in the header block of the FMAP words (see structure of header blocks). The data type and addressing of each element within the record is defined in this format map (FMAP). If a formatted file is assigned through the format processor, only 64 field descriptions may be entered for the record structure. The length of a data record may be from 1 up to 256 words, where only an integer record number may exist in a block. This means that no records may surpass the block limits. Usually only the header block is written when assigning formatted data. The physical data blocks on the disc will be dynamically assigned in case of formatted files, so that a file will always occupy as little space as necessary. The data blocks require no predefined, terminated disc area, but are assigned through a list of available disc sectors.

We can now differentiate between the following methods based on header structure and full capacity of the file:

- formatted files or- expanded formatted files

Headers of formatted files will occupy 127 words and the remaining 128 words will contain the direct addresses of max. 128 data blocks. This file form significantly reduces its capacity, however, it requires only 2 disc attempts in order to read the corresponding data block.



85

NIROS


schematic representation

Attempt Disc Block

1.

For extended formatted files, the header itself occupies 128 words. The remaining 128 contain no data block address, but max. 128 header-extended block addresses. 256 data block addresses are contained in these 128 header-extended block addresses. This organisation form has a 256 times extended capacity, but requires three disc attempts for it.

schematic representation

Attempt Disc Block



86

Header (128 words)

max. 128 data blockaddresses

Header block(256 words)

max. 64 fields

2.

Data block (max.256 words)

Header (128 words)

max. 128 header-extendedblock addresses

Header block(256 words)

1.

NIROS


The logical record number of the data record and the logical field number of the field within the record are to be entered in the user program for data access purposes. Based on the information in the FMAP, a plausibility control of the field to process will be taken from IOCS.

25.3 Relative Files

The “relative” organisation method is generally only applied for files stored on magnetic discs.

A relative file consists of a file header block and data blocks for the storage of data records. There is no format map (FMAP) and no list of data block addresses as by formatted files. If the user performs an area assignment for a relative file through FORMAT, this file will occupy a terminated area of the disc in regards to the size specified by the user through the record length and the max. number of expected records. Since the records are concisely linked together, the block limit will be surpassed in the case of this organisation method. The



87

max. 256 datablock addresses

max. 64 fields

2.

3.

Header-extended block(256 words)

Data block(max. 256 words)

NIROS


size of this relative file is only limited by the capacity of the logical unit.

The relative record number and the record length suffice for the IOCS to determine the address of the sector to access within the memory (no disc address) for placing the desired record. Usually, only a single disc access is required per record, except if the record exceeds the sector limit. A great disadvantage of this organisation form is that the file is not dynamically assigned, so it disposes very often of blank spaces within the disc.

The logical record number of the data record, the first position of the desired field within the record and the field length must be defined in the user program for file access. Since no logical record format description is available for formatted files, IOCS performs no plausibility control. This requirement must be completed by the user program.

25.4 Index Files

The “index” organisation method is usually only used for files stored on magnetic discs.

An index file occupies a limited area of the magnetic disc. A number of blocks at the beginning of the file contain an address list. Apart from this list, it is also possible to add 14 further record key lists. As opposed to relative files, index files use no logical record numbers for identifying a certain data record, but the concept of ordering, so a certain data record must be placed in order at a time. Up to 15 different criteria of order may be defined for a data record and placed in the record key lists, whereby the key can only point to a single location. The list file is opened and removed without affecting the data records.

Each key list of an index file consists of 3 levels:

- master level (main index)- coarse level (coarse index)- fine level (fine index)

The main index (master level) is usually a block (256 words). The size of the coarse and fine indexes does not depend on the maximal number of records of the file. IOCS occupies two words from each block of a key list and each key within the list has a two word long pointer.

The number of keys for each list block is the integer value of:



88

NIROS


254 / (L + 1),

where L is the key length expressed in words.

The sector address of the corresponding block within the coarse level is linked to each key of the master level; and the sector address of the corresponding block within the fine level is linked to each key of the coarse level. Each key of the master or coarse level is identical to the greatest (highest value) key of the block from the next lower level, pointed out by the corresponding sector address. The blocks within each level are ordered in a scattered way, however, the keys within each block are sorted in alpha numeric ascending order.

IOCS addresses a specified key by evaluating the first key with an equal or greater value from the master level. That is how a block from the coarse level is selected. The corresponding block from the fine level may be found in the same way, by performing a comparison with the specified key. Each key from the fine level addresses a data record through a relative record sum. This means that a data record may only be read at the 4th access. In order to avoid this, IOCS occupies four buffer areas, so that it can work with the next key in case of consequent disc transports.

In order to establish an approximate number of blocks needed for the list, the following formula may be used:

- SB = 254 / (L + 1)- GF = AD * 2 / SB + 1- GC = GF / SB – 1

GS = GF + GC + 1

This formula only determines an approximate value. The number of blocks in the coarse level may not exceed the number of keys per block, otherwise, the master level would exceed its block limit.

Abbreviations:

SB = Number of keys per blockL = Key length expressed in wordsGF = Size of the fine level expressed in blocksAD = Number of data blocksGC = Size of the coarse level expressed in blocksGS = Size of the list expressed in blocks

This formula only determines an approximate value. The number of blocks in the coarse level may not exceed the number of keys per block, otherwise, the master level would exceed its block limit.



89

NIROS


Schematic representation of an index file with 2 key lists:

Header block of fileMaster level 1Master level 2Coarse level 1Fine level 1

Coarse level 2Fine level 2Data blocks

Each level block of an index file has the following structure:

F; N; L

D

P 1

K 1

P 2

K 2



90

F = Flag of the fine level

0 = master and coarse level

1 = fine level

N = number of keys; maximal number of keys per block within the master level, number of active keys per block within the coarse and fine levels.

L = length of key expressed in words

D = sector address of the next block from this level and from this index ( 0 = last block from this level)

K = key word

P = sector address of the block of the next lower level in the master and coarse levels or the relative record number of the data block in the fine level

Up to L words may remain unused at the end of each level block.

NIROS


P 3

K 3

P n

K n

25.5 Text Files

The “text” organisation method is usually only used for files stored on magnetic discs.

A text file is not formatted and contains a single chain of characters which can be as long as the available disc capacity. All characters are saved in 7 bit ASCII code, whereby the eighth bit is always set to 1. The text is built from text rows, separated only by RETURN codes from each other, as well as text pages, which are separated by FORM codes from each other. Each data block from the disc can store 512 characters, where each block, except for the first one, may be filled by the file. The chain of characters is terminated by one or more null bytes. For random accesses, a hypothetical data record length of 512 bytes (256 words) is assumed, so that the access method of text files will correspond to that of relative files.



91

NIROS


25.6 File Definition File definitions (record length, organisation method etc.) are not required when programming with Business-Basic.

- The IOCS required data for processing is transferred from file labels for disc files.

- All standard values are used for punchcard files.

- The compulsory parameters from the open no. record are transferred to the IOCS (optional) or standard values are replaced for printer files.

25.7 File Name

In the case of files on magnetic discs, the file name consists of 1 to 14 letters and/or digits. Only the special character “.” is allowed. The first character of the file name must be a letter.

As opposed to file names for magnetic discs, file names for printer and punchcard files are set up by the system because a single file may be opened by a peripheral device. The file name will be the name of the corresponding channel program.

25.8 The Concept of Logical Units

While processing files on magnetic discs, especially at the termination of multiple sessions and the processing of multiple simultaneous issues, it becomes of advantage if the disc packs are not stored on the same physical drive.

This is achieved by assigning logical unit numbers (LU numbers). The LU numbers are assigned by the “INSTALL” processor. At the same time, the operating system learns which physical unit corresponds to which logical unit. The system disc will always correspond to logical unit number 0.

25.9 Record Pointers



92

NIROS


IOCS generates a record pointer as soon as a file is opened for magnetic discs and printer files. If several participants try to access the same file simultaneously, an individual pointer is created for each participant.

The record pointer represents the momentary access position of the file, which is the relative record number of recently processed data records within the file.

The record number of recent data blocs (sectors) and the byte position within this block pointing to the most recent processed character are generated for text files.

26 Data Security

The operating system contains a series of data security systems that prevent unpermitted access to files, processors and user programs.

Three methods of data security systems may be differentiated.

Password Security

Password security is used in order to prevent unauthorised access to processors, programs and files. Passwords are only known by the user who is authorised to access the processors.

Privilege Security



93

NIROS


Privilege security prevents access to data assigned to a higher privilege level than the one of the user. Four privilege levels are managed by the operating system, organised in the following way, starting with the highest priority:

- system level

This privilege level is only available to NCAG specialists and has no system limits.

- manager level

The manager privilege is the highest participant level and allows access to all commands, instructions and functions used for system control. Some commands, depending on the system, may only be performed from the master workstation.

- user level 1

This privilege level allows access to the programs shared by the manager and a subset of available system commands.

- user level 2

This privilege level allows access to the programs shared by the manager and a subset of available system commands.

Functional access security

The functional access security represents an expansion of the privilege levels since each file may be protected by a combination of the following: read-only, read-protected and copy-protected.

This security can also be applied to equal and lower privilege levels. There is no security measure for higher privilege levels.



94

NIROS


27 TAMOS

The TAMOS (Terminal Auto-Operating and Monitoring System) operating system was created as an expansion to the existing operating system, easing the following tasks of the system user.

- data carrier processing,- data security and reconstruction,- program structuring and program selection,- processing and controlling the process of tasks and- diverse processing functions.

Moreover, the system user is led through the entire disk drive of “his” system by dialog support.



95

NIROS


27.1 Selectors

TAMOS offers program structuring in the form of selectors organised in a three-level tree-view. A supervisor selector is offered by TAMOS for this system manager, containing all programs that will help TAMOS reach its aim.

The selector has the following structure:

Supervisor Selector

Level 1

Level 2

System maintenance Utility programs Spooling System subprograms

Level 3

- set up selector - day start - set up spool file

- print archive file

- update selector - day termination - start spooler

- show archive file

- remove selector - data security - cancel spooler

- printer assignment

- print selector - reconstruction 2nd gen.

- show log file

- system security

- message maintenance

- reconstruction 2nd gen.

- system reconstruction

- text maintenance- program list

- disc setup- print log file- format- set up clock- show participant- turn off system

- system commands

New selectors may be set up through the supervisor selector. These will be assigned a privilege level of 0. Max. 15 selectors may be created for level 1. 15 level 2 selectors may be created for each selector from level 1 and 15 level 3 selectors may be created for each selector from level 2. In theory, 3375 different programs are made available to each participant in his program sector.

The system manager therefore has the following tasks:set up participant constants,assign passwords anddefine the corresponding program selectors.

27.2 Data Backup



96

NIROS


Data Backup is completed automatically at the end of each work session based on three generator principles. The system manager is required to copy and backup all data carriages where a content update has taken place.

TAMOS allows setting up and processing max. 17 logical disc units, each containing three packs.

These three packs have the following functions:- work pack 1st generation- backup pack 1 2nd generation- backup pack 2 3rd generationThe backup packs are always used when the 1st generation ones prove to be erroneous.

Each logical unit is defined by the following unit number:0 = system pack1 = user packs2 = user packs..16 = user packsFor the identification of a pack an additional archive label of two characters has been added to the logical unit number.

The archive control file, located on the system disc and managed by TAMOS, contains three packs, each assigned to this system disc.

TAMOS allows the access of several system discs within the setup configuration.

In case of defective works, sources or aim packs, a reconstruction is required by TAMOS in order to establish that all three generation principles have been maintained.27.3 System Monitoring

All essential system events during the logical day cycle are recorded by TAMOS in a log file and may be called and analysed if needed.

If program interruptions (e.g. power failure) occur during the day cycle, TAMOS continues performance from the point where it was interrupted after establishing the cause and the system manager is notified of the event.

Before a user program may start, TAMOS checks if:

- the manager of today’s cycle has been released (start of day),- the manager has registered all necessary data carriages (disc registration),



97

NIROS


- a standalone processor is active,- the program may run, for example, only at the master workstation,- the correct (if required) password has been entered,- the previous program has been terminated correctly or if a 1st generation reconstruction of the backup generations is required.

27.4 Control Files

TAMOS requires for its operation, data security and reconstruction measures, as well as performance control of tasks, several control files on the system disc.

Log file

All essential system events during the logical cycle of the day are stored in this file.

Message file

This file contains all messages that TAMOS shows the user on screen.

Archive file

Contains archive names (is not checked), logical unit numbers and archive label for all logical disc units created by TAMOS on this system disc.

Participant and program control file

This file contains a control record for spooling and one for each dialog workstation by setting up a required control parameter from the program selector or from the task waiting queue for monitoring the program performance. Moreover, it serves to controlling and monitoring the required cycles e.g. new formatting or reconstruction of data carriages.

Spool file

This file contains the waiting queue for tasks running in the background partition. It contains an entry for each task with its name and a task description.



98

NIROS


Program selector file

The participant has been assigned a selector file for each created account, containing the messages on screen, shown as text on screen, and the parameters required for the programs running.

27.5 Spooling

A so-called “phantom port” may be created for each configuration, which will run on the background partition. This “phantom port” disposes neither of the keyboard, nor of the screen. This means that no program interventions may be made by the user through the keyboard and he may not be informed through the screen.

Spooling represents a part of TAMOS that controls the processing of programs and printer processes.

The spooler starts the task contained in the spool file. The processing control is transferred to the task starting, which will then run on the background partition. Once a job ends, whether correctly or not , the processing control returns to the spooler.



99

NIROS


Each task within the spool file has a label informing about its present state.

WAITING The task waits for its execution.BLOCKED The execution of a task has been blocked by a user.ERROR The execution of a task has been interrupted due to an

error.ACTIVE The task is being executed at the moment.STOP The execution of the task has been interrupted due to an

error and the spooler stopped.

If a task has been executed and terminated correctly it will be removed by the spooler from the spooler file. The spooler will afterwards look for the first task at the beginning of the spool file having the “WAITING” status and will try to execute it. If this does not work, because, for example, a disc unit is not available for access, this task will receive the “ERROR” status. The spooler will then check its task description (specified by the programmer), if it contains the word “stop” or if it can start the execution of the next task. If the spooler must be stopped, the task will receive the “stop” status and will await an intervention from the user.

If a task that enables the printing of a text file is found within the spool file, this process will also run according to the above scheme, whereby TAMOS will transfer the processing control from the spooler to the standard printing program.

This program checks prior to the actual printing of the text file with which paper format the printing should take place (contained in the task description). If the format corresponds to the format of the previous task, the printing task will be started directly.

During a format change, the printer is given a new format label and the first page of text is printed as a test.

The system manager may carry out the interventions of the supervisor selector over the spool file and request the printing of the log file.

27.5.1 Supervisor Selector

If the user logs in password-protected as manager, he will dispose of the following options concerning the system control through an area selector:

- system maintenance- utility programs



100

NIROS


- spooling- system programs

Explanations to these options may be found in the user manual.

27.5.2 System Maintenance

This option allows the manager to process selectors and match system texts to corresponding languages.

27.5.3 Setting Up a Selector

The manager may set up program selectors through this option and create user accounts within the system for new participants. This user account is required by the operating system in order to perform the management and interruptions of participant sessions. The username corresponding to the account identifies the program selector of the participant. The entire program selector is organised and specifications in regards to data security are defined (executable only in standalone mode).

27.5.4 Updating a Selector

This instruction allows specific corrections and expansions of the program selector of a certain user. It is recommended to first print the corresponding selector (executable only in standalone mode).

27.5.5 Removing a Selector

The corresponding user account and the program selector assigned to it will be removed. The participant will not be recognized by the system any more. All user-specific files should already be removed up to this point, since these will not be removed automatically (executable only in standalone mode).



101

NIROS


27.5.6 Printing a Selector

This instruction prints the desired selector on the system printer while taking into account the selector structure.

27.5.7 Notice Maintenance

Messages to be outputted in TAMOS, normally offered in German and English, may be attached to the corresponding language through this instruction.

27.5.8 Text Maintenance

Like the “notice maintenance” instruction, this instruction allows matching the texts used by TAMOS to their corresponding language.

27.5.9 Program List

A program saved on the magnetic disc may be listed through this command.

The listing occurs in the following way:

- program area (instructions),- cross-reference variables,- cross-reference row numbers.

Before a logical day cycle may begin, the manager must select “day start”. It will be checked if all required data backups have been performed and if formatting resp. reconstruction processes are not



102

NIROS


necessary. The manager will learn about the state of the magnetic discs through the disc archive print (executable only in standalone mode).

27.6 Service Routines

This group must be called by the manager within the logical day cycle, otherwise it wouldn’t be a logical day cycle.

27.6.1 Start of Day

Before a logical day cycle may begin, the manager must select “day start”. It will be checked if all required data protections have been performed and if formatting resp. reconstruction processes are not necessary. The manager will learn about the state of the magnetic discs through the disc archive print (executable only in standalone mode).

27.6.2 End of Day

This instruction will be performed by the manager at termination of each work session (logical end of day) in order to perform the necessary data backup. Prior to the data backup, the manager will be informed of essential events of the day through the log file printout.

Afterwards, TAMOS will require to backup all magnetic discs that have suffered content updates during the logical day cycle (executable only in standalone mode).

27.6.3 Data Backup

Data backup copies all content-wise updated data carriages (1st generation) on the oldest safety disc (3rd generation). The former 2nd generation – as after the copy during the end of day – and the 3rd generation, and the former 3rd and 2nd generations will be performed within the archive. The day’s work may be continued. The program allows additional data backup for large data amounts and high backup requirements (executable only in standalone mode).

27.6.4 Reconstruction 2nd Generation

Two options must be mentioned.



103

NIROS


- defective system disc

Most importantly, a new 1st generation will be created from the 2nd generation in the disc sets performed in the disc archive.

- non-defective system disc

First and foremost, a new 1st generation will be created from the 2nd generation in the disc archive as recently performed disc sets.

Hereby, even after the failure of the work disc, only the most recent data will be lost (executable only in standalone mode).

27.6.5 Reconstruction 3rd Generation

- defective system disc

Most importantly, a new 1st generation will be created from the 3rd generation in the disc sets performed in the disc archive.

- non-defective system disc

First and foremost, a new 1st generation will be created from the 3rd generation in the disc archive as recently performed disc sets.

The 3rd generation reconstruction must be performed by the user if the 2nd generation reconstruction has been terminated successfully (executable only in standalone mode).

27.6.6 Setting Up Drives

All work drives accessed until this point will be set up through this instruction and will hereby be available to the user. Afterwards, all unused magnetic discs will be rejected by the system. After setting up the work drives under their logical unit number, the correspondence between user programs and data files must be set up (executable only in standalone mode).

27.6.7 Exchanging Drives



104

NIROS


This instruction is used in order to copy the content of an exchange drive of the second performance disk drive to a random hard drive (not drive 0) (executable only in standalone mode).

27.6.8 File Print Log

All important system events from the log file will be outputted on the central system printer. This instruction is automatically performed at the “end of the day” (executable only in standalone mode).

27.6.9 Formatting

The “formatting” instruction is only used in order to physically check new or defective magnetic discs for availability. Either a new drive set, built from the work disc and one or two security generations, or a physically defective disc from an existing driver set is added. Moreover, a logical unit may be removed by removing it from the drive archive.

After the termination of formatting, a new drive archive is printed (executable only in standalone mode).

27.6.10 Setting System Time

An eventually required system time correction may be performed through this instruction. This may be necessary, for example, after a power failure, in order to correct the system time.

27.6.11 Managing Port Priorities

IntroductionPort priority management should improve the efficiency of the system. This is only performed through a new time slice algorithm.

Determining prioritiesIndividual port priorities are set up under TAMOS.Select function 2, “UTILITIES” from the system selector. Afterwards select function 12 “port priorities”.After selecting function 12, a display of the following mask will appear (example):



105

NIROS


PORT USER DESCRIPTION RUNMODE AGE STATUS PRIORITY0 0,1 PORT INQUIRY 71 0,0 LOGGED OFF 52 0,0 LOGGED OFF 43 0,0 LOGGED OFF 2

If the priority needs to be modified, insert the port number and then the new priority.

The mask will appear anew, so the priority for the corresponding port is already updated.

The value of the priority is set at word 7 of each Port Control Block. 0 up to 8 are possible entries. For priority 0, a “1” is set in PCB and for priority 8 an “11”.

Description of the algorithm

The time amounts of each port are independent of the sum of amounts for all active ports.

Example 1: All 3 ports are set up with priorities 1, 2, 3, so the performance within 6 time slices will be the following: Priority 3, priority 2, priority 3, priority 2, priority 3, priority 1.

The port with priority 3 will be used 3 times, priority 2 2 times and priority 1 only 1 time.

Example 2: 2 ports are set up with priorities 1 and 8, so the performance within 9 time slices will be the following: 8 times the port with priority 8 and 1 time priority 1.

27.6.12 Shutting Down the System

After the “end of the day” the manager shuts down the system through this instruction. All connected peripheral devices are also shut down.

The manager workstation is shut down by pressing the green button.

27.7 Spooling

The manager is allowed to affect the control of background processing.



106

NIROS


27.7.1 Displaying Spool File

All tasks that must be run in the background, including their description, are contained in this file. All task descriptions are displayed on screen through this instruction. The manager has the possibility to modify individual parameters within the task description or the position of tasks within the spool file, whereby he will also change the order in which they will be performed.

27.7.2 Starting Spooling

This instruction starts background processing. It can only be executed if the spooler has been properly set up under TAMOS. The tasks from the spooler file are performed sequentially.

27.7.3 Cancelling Spooling

Spooling may be cancelled either imperatively or after the execution of the current task through this instruction.

27.7.4 Displaying Log File

The log file will be displayed for the manager on screen, showing events liked to all jobs, both running in the background and those being processed. The log file will be analysed at the end of the entries from the background partition.

27.8 System ProgramsThis group of instructions allows the manager to perform certain operations of the system discs and to branch out from TAMOS to NIROS.

27.8.1 Printing Archive Files

The manager can inform himself at all times about the current status of the archive file through this instruction. This means that all logical units managed by TAMOS, ordered according to their generations, will be printed (including the status label).



107

NIROS


27.8.2 Displaying Archive Files

This instruction shows a part of the archive file on screen and allows the manager to mark for backup magnetic discs that have not been modified content-wise.

27.8.3 Printing Assignment

The assignment table for logical printer $LPT may either be created or updated. An entry may be void or only consist of a printer name within the assignment table.

27.8.4 System Security

This instruction may be executed only if “end of day” has been executed prior to it. The hard drive of the first disk drive of the 1st generation exchange pack is copied with the same archive number.

27.8.5 System Construction

The system exchange pack will be copied on the hard drive of the first disk drive.

27.8.6 System Commands

The manager may leave the TAMOS operating system through this instruction and branch out to the SCOPE NIROS command processor. Thereby, the user will have the option to execute all instructions offered by the operating system. These instructions are direct calls to the processor.

28 SYSMOD Description

The “SYSMOD” processor enables modifications of the hard and software specifications with desired parameters within the NIROS operating system. Parameters may be entered in the dialog box on the master workstation. The user may view all parameters that are available for modification.

Parameters are saved in several system files (e.g. CONFIG, NIROS, DRIVER). Parameters may be set no matter the SYSMOD configuration. The IPL procedure checks if the operating system identified by the parameters may or may not be installed.



108

NIROS


SYSMOD leads the user with the help of a multi-level function selector.

The input of a parameter is terminated by hitting the “CR” key. If the CURRENT VALUE is kept, “CR” will be hit without prior input. Hitting the “CR” key without prior input causes a return to the selector structure without altering the parameter.

Hitting the “ESC” key causes branching out to the main level.

A gapless protocol may be outputted on a random printer.

Similar tasks, performed on screen, may be terminated by hitting the spacebar.

The task is continued by hitting the “CR” key.

28.1 Calling SYSMOD

The processor runs only on the master workstation. The call is performed under SCOPE.

The processor displays the following text:

PRESS SPACE KEY TO STOP OUTPUT, CR TO CONTINUE

ENTER FILENAME OF YOUR PRINTER’S DRIVER,CR IF NO PRINTER IS AVAILABLE:

You may enter the name of the printer’s driver here. If a name is entered, a gapless protocol of the SYSMOD processor task will be printed on the specified printer. If the “CR” key is hit without a prior input, the tasks will only be performed on screen.

A printer protocol should be prepared for reconstructing parameter inputs in case of eventual issues that may arise.28.2 Main Selectors

The following main groups may be chosen:

CHANGE HARDWARE SPECIFICATIONS .............. 0CHANGE SOFTWARE SPECIFICATIONS .............. 1CORE ALLOCATION MAP ......................... 2EXIT ........................................ 3

28.3 CHANGE HARDWARE SPECIFICATIONS



109

NIROS


Here the user may set parameters for the hardware equipment of the system to install. E.g. he may enter requirements related to the deployed computer, the memory configuration and the type of the connected magnetic disc.

The following options are listed:

ADDRESS MAP REGISTERS ................ 0CORE SIZE ............................ 1DISC CHARACTERISTICS ................. 2NO OF ALM CONTROLLERS ................ 3CHANNEL – PORT COLLECTION ............ 4

28.3 ADDRESS MAP REGISTERS

This parameter determines if a new computer (module no. 1517) with basic registers or an old computer (module no. 1513) is installed. Computer 1517 allows partitioning.

After its selection, the current parameter is displayed:

CURRENT VALUE: X

and then the input of a parameter is required.

ADDRESS MAP REGISTERS AVAILABLE? (Y OR N):

Input: Y = computer 1517 will be usedN = computer 1513 will be used

If “N” is entered, a “Swapping System” will be installed because the computer (1513) allows no partitioning.

28.3.2 CORE SIZE

After its selection, the current parameter is displayed:

CURRENT VALUE: XXX

and then the input of a parameter is required.

CORE SIZE IN KB:

The memory configuration of the system, to which the BS will run, will be entered. The entered value will range from 64 to 256 KB. A memory



110

NIROS


expansion, independent of the available memory modules, is possible by 32 KB (e.g. 64, 96, 128, 160, 192, 224 or 256).

28.3.3 DISC CHARACTERISTICS

This parameter determines which type of disc drive has been connected.

After its selection, the following is displayed:

DISC CAPACITY .................................. 0

0 must be inputted here. Afterwards, the following will be outputted:

ENTER DRIVER NO:

Strictly “0” should be inputted here!

An entry unequal to “0” is only possible in the case of mixed SM and CA disc drives. In this case, “0” will mean storage module and “1” cartridge.

The number of cylinders will be entered as CURRENT VALUE, now configured for the current driver.

The number of cylinders must be entered. The following values are currently available:

403 = 33 million byte storage module256 = 21 million byte storage module408 = 5 million byte cartridge256 = 3 million byte cartridge128 = 1.5 million byte cartridge

The cylinder input of storage module systems is the number of cylinders without a track area. This area currently consists of 2 cylinders.

28.3.4 NO. OF ALM CONTROLLERS

Only permitted for RAP systems.

Input may be either “1” or “2”, depending on the number of insertions (module no. 1819).

Only the currently configured number of insertions (1819) is displayed as CURRENT VALUE.

28.3.5 CHANNEL PORT CONNECTION



111

NIROS


Only permitted for RAP systems.

The number of connected workstations is entered for each ALM channel here.

The input of the ALM channel number is required by the following instruction:

ALM CHANNEL NO

“Y” or “N” may be entered as CURRENT VALUE.

Y = 2 places (MASTER/SLAVE) for this channelN = 1 place (MASTER) for this channel

The entered channel number corresponds to the following physical ALM channels:

Input: 0 1 2 3 Input: 4 5 6 7 1st ALM: 1 2 3 4 2nd ALM: 1 2 3 4

Note: This input does not correspond to the logical port number.

After the channel number (-1) is entered, the question:

CHANNEL IS CONNECTED WITH TWO PORTS?

will require a “Y” or “N” answer.

Y = MASTER and SLAVE are connected to this ALM channel.N = only MASTER is connected to this channel.

28.4 CHANGE SOFTWARE SPECIFICATIONS

Software-specific parameters will be set here, mainly required during the IPL process in order to establish and determine an exact memory assignment.

The following options exist:

ACTIVE FILE SIZE ..................... 0DRIVERS .............................. 1SIZE OF MAGTAPE BUFFER ............... 2PORT CHARACTERISTICS ................. 3



112

NIROS


DATA FILES ........................... 4PARTITIONS ........................... 5CORE-RESIDENT DISCSUBS ............... 6QUEUES ............................... 7TIME SLICE ........................... 8DECIMAL SIGN ......................... 9NLC BUFFER SIZE ...................... 10

28.4.1 ACTIVE FILE SIZE

The current size of the ACTIVE FILE is provided as CURRENT VALUE.

Input is required by the:

ACTIVE FILE SIZE IN KB:

message.

The ACTIVE FILE must be sufficiently large to accept the largest program (incl. data area). 14 KB will be transferred from PM to master packs. The ACTIVE FILE may not be assigned a lower value than 12 KB, otherwise system components such as TAMOS and D2DUTIL will not be executable anymore.

The size of the ACTIVE FILE also determines the size of the main partition (see chapter 28.4.6).

28.4.2 DRIVERS


DISPLAY DRIVERS ........................... 0SELECT DRIVERS ............................ 1

DISPLAY DRIVERS

All drivers ($ files) located on the system disc are listed in the following form:



113

NIROS


NAME IGNORE DRIVER TYPE IN CORE: SIZE (10) SIZE (8)

NAME : Name of the driver

IGNORE DRIVER : Marks if the driver is made memory-resident during the IPL process or not. Y = driver is not made resident. N = driver is made resident.

TYPE : Type of driver – SYSTEM - PERIPHERAL

IN CORE SIZE (10) : Occupied memory space in words (decimal).

SIZE (8) : Occupied memory space in words (octal).

SELECT DRIVERS

Sets a loading label for random drives or removes them. This means that the driver that will be loaded onto memory during the IPL may be specified here.

Only memory-resident drivers may be used during runtime!

“Y” or “N” will be displayed as CURRENT VALUE.

Y = driver is ignored during IPL, which means it will not be loaded.N = driver is not ignored during IPL, which means it will be loaded.

“Y” or “N” will also be available as input, with the same significance.

28.4.3 Size of Magtape Buffer

The size of the magnetic tape buffer will be inputted in words for the magnetic tape connection. It must be as large as the largest band block to process. The maximal configurable buffer size is 8 KB (4096 words).

The $MTX driver must be activated during the MT connection (see chapter 28.4.2).

The current buffer size will be displayed as CURRENT VALUE.



114

NIROS


28.4.4 PORT CHARACTERISTICS


NO OF PORTS ................................. 0PORT NO OF FIRST PORT ....................... 1SET RWS PROGRAM ID .......................... 2

NO OF PORTS

Allows setting the number of spaces for the following drivers:- $AMLD (DAP system)- $PHAD (DAP system)- $AMLR (RAP system)- $PHAR (RAP system)For $ALMD and $ALMR, the number of connected workstations must be specified additionally to the master workstation.Example: Connecting 3 BA’s master ports + 2 additional ports.In the case of $PHAD resp. $PHAR, the real number of required “phantom ports” must be configured.ATTENTION: The configured number of ports for $PHAR resp. $PHAD

depends on: PORT NO OF FIRST PORT for both the $ALMRresp. $ALMD drivers.

PORT NO OF FIRST PORT

This function enables determining the port number of the first additional port connected to the master port for the $ALMD resp. $ALMR drivers. This number is specified as follows:

1 + number of configured ports of the corresponding phantom port drivers.

$ALMD = 1 + number of $PHAD ports$ALMR = 1 + number of $PHAR ports

The current port number of the first port is listed as CURRENT VALUE. The selection of the desired drives is performed by entering the corresponding driver name.

Attention: No gap may exist in the succession between the port number of the last configured phantom port and the number of the first additional workstation.

Example: The input of PORT NO OF FIRST PORT must be 2 for configured phantom ports.

If incorrect information was entered you will be



115

NIROS


notified by SYSMOD function 3 (EXIT).

If the entered port number is too low, the following message appears:

$ALMX TRIES TO ASSIGN MORE THAN ONCE PORT NO X

If the entered port number is too high, the following message appears:

“HOLE” BETWEEN PORT NUMBER X YWASTED CORE MORE THAN DECIMAL OCTAL: XXX YYY

SET RWS PROGRAM ID (only for RAP systems)

Allows the input of program number assignment for each port (XB file assignment). Only entry “01” is currently available.

28.4.5 Data Files

Here you may specify the number of data channels that may be opened simultaneously per BA.

The current amount is provided as CURRENT VALUE. Input is required by the message:

NO OF CHANNELS PER PORT

28.4.6 PARTITIONS

The user may divide the available main memory into program processing areas. After selecting this function, the current number of existing partitions and their size in KB will be listed.

NO OF PARTITIONS (EXCL. PROCESSOR): CURRENT VALUE: XPARTITION SIZE IN KB OF 1ST CURRENT VALUE: XXPARTITION SIZE IN KB OF 2ND CURRENT VALUE: XX...



116

NIROS


PARTITION SIZE IN KB OF NTH CURRENT VALUE: XX

The number of partitions and the size of existing partitions may be modified afterwards. If possible, as many partitions as the number of ports (see NUMBER OF PORTS), incl. master and phantom port, should be configured.

ATTENTION: The number of partitions specified is additional to the main partition! The main partition is always reserved. Thesize of the main partition always corresponds to the configured ACTIVE FILE SIZE.

If partitions with a size smaller in KB than the configured ACTIVE FILE are configured, these partitions will only be used for programs protected by the SAVE command.

28.4.7 CORE-RESIDENT DISCSUBS


DISPLAY CORE-RESIDENT DISCSUB LIST ............. 0INSERT A NO IN CORE-RESIDENT DISCSUB LIST ...... 1REMOVE A NO FROM CORE-RESIDENT DISCSUB LIST .... 2

DISPLAY CORE-RESIDENT DISCSUB LIST



117

NIROS


Displays the number of DISCSUBS (system subprograms) made memory-resident during the IPL.

INSERT A NO IN CORE-RESIDENT DISCSUB LIST

Allows the option of making a DISCSUB memory-resident.

Input is requested by the message:

DISCSUB NO

If the number of a DISCSUB contained in another DISCSUB is inputted, the message:

DISCSUB NO: XXX INCLUDED IN DISCSUB NO: YYY

will appear. DISCSUB XXX is automatically made resident if YYY is resident.

REMOVE A NO FROM CORE-RESIDENT DISCSUB LIST

Allows the option to remove a DISCSUB from the list of memory-resident DISCSUBS. This DISCSUB will not be memory-resident during a further IPL.

Input will be required by the message:

DISCSUB NO

28.4.8 QUEUES


CHARACTER QUEUE .................................. 0SIGNAL NODE QUEUE ................................ 1TASK QUEUE ....................................... 2

CHARACTER QUEUE



118

NIROS


The character queue allows saving CONTROL CODES (e.g. CTL, C-CTL, B-CR) and the ESC key. These will later on be processed within the next time slice caused by BA.

The currently configured value is listed as CURRENT VALUE.


NO OF CHARACTER QUEUE NODES ABOVE TWO PER PORT:

“10” should always be the value configured here. This value depends on the size of the TASK QUEUE for each port.

SIGNAL NODE QUEUE

All “signal 1” values are saved here. This entry must be at least “1”. The entry specifies the size of the SIGNAL NODE QUEUE of the entire system.



NO OF SIGNAL BUFFER NODES (MINIMUM IS ONE)

TASK QUEUE

Waiting queue for the time slice division. 3 entries are reserved for each task. Internally, each entry occupies 9 words.



NO OF FREE NODES

28.4.9 TIME SLICE

The size of the time slice is specified here. The size of the time slice is defined in tenths of a second (see chapter 27.11).

The current size of the time slice is listed as CURRENT VALUE.


TIME SLICE (BETWEEN 1 AND 64 TENTH OF A SEC.):



119

NIROS


28.4.10 DECIMAL SIGN

The decimal sign, “,” or “.” will be specified here.

The currently configured decimal sign (“,” or “.”) is listed as CURRENT VALUE.


ENTER DECIMAL SIGN (“.” OR “,”):

28.4.11 NCL BUFFER SIZE

The maximal size of a data transfer block is defined here in words.

The currently configured buffer size is listed as CURRENT VALUE.

Input of the block size is requested by the message:

ENTER NO OF WORDS FOR NCL BUFFER:

The buffer must be configured as large as the largest block that must be transferred.

28.5 CORE ALLOCATION MAP

The memory assignment list is outputted in the following form:NIROS ................................... SIZE(10) SIZE(80) ADRESS(8)CORE SIZE IN KB ......................... XXX XXXAREA OF PARTITIONS (ABOVE TOPW.) IN KB .. XXX XXX XXXXXXUNUSED CORE IN EXTENSION IN KB .......... XXX XXX XXXXXXTOPWORD OF CORE ......................... XXXXXXCOMMON AREA ............................. XXX XXX XXXXXXPORT CONTROL AREA ....................... XXX XXX XXXXXXCALL STACK .............................. XXX XXX XXXXXX



120

NIROS


DAT AND SAT ............................. XXX XXX XXXXXXAREA DEPENDING ON LU’S .................. XXX XXX XXXXXXCORE-RESIDENT DISCSUBS .................. XXX XXX XXXXXXPARTITION CONTROL AREA .................. XXX XXX XXXXXXDRIVERS ................................. XXX XXX XXXXXXALM CHANNEL CONTROL BLOCKS .............. XXX XXX XXXXXXI/O BUFFER SIZE ......................... XXX XXX XXXXXXSIGNAL NODE QUEUE ....................... XXX XXX XXXXXXDATA FILE TABLES ........................ XXX XXX XXXXXXCHARACTER QUEUE ......................... XXX XXX XXXXXXINTERRUPT STACK ......................... XXX XXX XXXXXXTASK QUEUE .............................. XXX XXX XXXXXXUNUSED CORE (ASSIGNED TO TASK QUEUE) .... XXX XXX XXXXXXBLOCK BUFFER AREA (ADDR. IS BSA) ........ XXX XXX XXXXXXBASIC USER AREA (ACTIVE FILE SIZE) ...... XXX XXX XXXXXX

Explanations to the CORE ALLOCATION MAP output:

The table head contains the name of the operating system and the internal version label.

Additional outputs mean:SIZE(10) = occupied memory in words, decimalSIZE(8) = occupied memory in words, octalADDRESS(8) = address, octal

CORE SIZE IN KBThe size of the configured memory is displayed in KB (see chapter 28.3.2).

AREA OF PARTITIONS (ABOVE TOPW.) IN KBThe size of the upper TOPW OF CORE memory area occupied by PARTITIONS.

“ADDRESS(8)” shows the address (word address) of the first partition in the upper “TOPW”.

UNUSED CORE IN EXTENSION IN KBThe size of the available memory area above “TOPW.” is listed in KB.

The start address of the available area is listed as address. If no available area smaller than 64 KB is found, this address is identical with the AREA OF PARTITIONS address.

TOPWORD OF COREThis address specifies the highest address occupied by the operating system. TOPWORD OF CORE’s largest possible value is



121

NIROS


77776 octal. TOPW. will only be pushed downwards if additional partitions exist and the reserved memory area is under 64 KB (see chapter 28.10).

COMMON AREASize and start address of common areas of all configured workstations. 256 words are reserved for each workstation (including phantom port). This area lies directly under TOPWORD OF CORE. Its size is expressed in words.

PORT CONTROL AREASize and start address of the PCB (control table for ports). A PCB of 32 words is reserved for each configured workstation. The area of the PCB lies directly under the COMMON AREA.

CALL STACKAn area used by the operating system to temporary save addresses and accu-content during levelled DISCSUB calls (e.g. a DISCSUB is called from another DISCSUB). This area lies directly under the PCB.

DAT AND SATAddress and control table for DISCSUBS in the memory and on the magnetic disc.

The following are set for each DISCSUB:

- start address in the memory for resident DISCSUBS- disc address for transient DISCSUBS.

The size of this area is expressed in words. The area for DAT AND SAT lies directly under CALL STACK.

AREA DEPENDING ON LU’SSize and start address of the LOGICAL UNIT TABLE (LUT). An entry with the following structure has been generated for each existing LU:

Word 1: Pointer to the LUFIX tableWord 2: Pointer to the LUVAR tableWord 3: LU number

This area lies directly under DAT AND SAT.

CORE-RESIDENT DISCSUBS



122

NIROS


Size and start address of the memory address where memory-resident DISCSUBS are loaded during the IPL. This area lies directly under AREA DEPENDING ON LU’S.

PARTITION CONTROLL AREASize and start address of the partition control area. 49 words are reserved per configured partition.

DRIVERSSize and start address of the memory address where active drivers ($ files) are loaded during the IPL. This area lies directly under PORT CONTROLL AREA.

ALM CHANNEL CONTROL BLOCKS (only for RAP systems)16 words are reserved for each additional RAP connected to the master.

I/O BUFFER SIZESize and start address of the I/O buffer. A buffer of 160 words is reserved for each configured port. This buffer is only used for interactive I/O’s (PRINT, INPUT). The area assigned to the I/O buffer lies directly under the ALM CHANNEL CONTROL BLOCKS.

SIGNAL NODE QUEUEArea of the “SIGNAL 1” values. Four words are reserved for each configured entry (see chapter 28.4.8). The SIGNAL NODE QUEUE lies directly under the I/O BUFFER area.

DATA FILE TABLESSize and start address of the DATA FILE TABLES. A DFT is created for each port, containing 8 entries for each configured channel. Additionally to the SYSMOD configured channels, each port occupies 5 channels which also reserve DFT entries. The DATA FILE TABLES lie directly under the SIGNAL NODE QUEUE.

CHARACTER QUEUE



123

NIROS


Size and start address of the CHARACTER QUEUE. This area enables saving CONTROL CODES and ESC. The CHARACTER QUEUE lies directly under the DATA FILE TABLES.

INTERRUPT STACKArea for the temporary save of interrupts. This area lies directly under the CHARACTER QUEUE.

TASK QUEUESize and start address of the waiting queue for the time slice division. The TASK QUEUE lies directly under the INTERRUPT STACK.

UNUSED CORE (ASSIGNED TO TASK QUEUE)Size and start address of the available memory area within the first 64 KB. This area is assigned to the TASK QUEUE.

BLOCK BUFFER AREA (ADDR. IS .BSA)Size and start address of the area enabling the buffer area of the system (BSA, HBA, SSA etc.).

BASIC USER AREA (ACTIVE FILE SIZE)Size and start address of the main partition. Its size matches the ACTIVE FILE SIZE.

28.6 EXIT

An exit of the SYSMOD processor is only possible by using this function.

In case of configuration alterations, eventual required entries are added that will affect the memory assignment list, driver list and memory-resident DISCSUBS. After the termination of their execution, the processor may be left.

The configured operating system is checked by SYSMOD. A notification will be displayed if configuration errors are found. In this case, SYSMOD will only be exited after the corresponding correction.



124

NIROS


If determined that the configured operating system may not be installed in the configured memory, the notification:

OVERFLOW! WORDS REQUIRED ................. XXXX XXXXXX

will be displayed.

The areas which have no available memory space are labelled by “*”.

In order to allow the configuration generated by SYSMOD to take effect, a configuration alteration will run the IPL right before its termination.

28.7 DISCSUB List

DSB No. Name Location XNDMR Function

0 FAULT 6000 D TRAP output, interrupt1 ALLOC 4400 R Occupy available disc block2 DALLC 4000 R Release occupied blocks3 FFILE 3400 R Search file in INDEX4 EXTEN 24000 Extend file on EXTENDED5 ALCON 24400 Assign relative file6 CDTA 26000 Conversion (only LKL 500)7 CIA 6400 Int to ASCII conversion10 CSTR 2400 R Compare strings11 PASSC 400 Compare password12 ERROR 12400 Basic error routine13 MESSA 6400 Error message in clear text14 BREAK 7000 Set DSP breakpoint15 ACNTL 5400 R ACCOUNT LOOKUP16 DELET 5000 N Delete file17 PDELE 5000 N Delete processor20 BUILD 1000 X Build fileDSB No. Name Location XNDMR Function

21 BILDD 1000 XN Build $ file22 OPEN 2000 N Open file/device23 OPENU 2000 N Open update24 OPENL 2000 N Open with lock25 OPENR 2000 N Open reference26 CLOSE 2400 CLOSE27 CLEAR 2400 Release channel30 GETRR 27400 X M Read record31 GETRW 27400 X M Write record32 IPRE 23000 X CALL 133 READI 400 M Read field (formatted)34 WRITI 400 N M Write field (formatted)



125

NIROS


35 WRITN 24000 Enter field in format list36 READC 25000 X M Read record (relative, text)37 WRITC 25000 XN M Write record (relative, text)40 CHARG 5000 XN M Calculate cost for access41 SYSCO 15000 CALL 9842 CNVDA 7400 Convert date in ASCII43 CNVAD 7000 Convert ASCII to DATE44 CNVDT 7400 CALL 9945 RDFHI 16000 CALL 9746 SPECI 13400 R SPC functions47 RECOV 6400 D Transfer to TRAP50 PATNF 120000 Arc tangent51 PLOGF 13000 Natural logarithm52 PSQRF 12000 Square root53 PEXPF 13400 X Exponential function54 PSINF 15000 X Sinus55 PCOSF 15000 XN Cosine56 PTANF 14400 Tangent57 IDIS 21000 CALL 160 DIREC 16400 X SEARCH module 061 BLDC 3000 BUILD expansion62 DELQU 62000 SEARCH module 663 INKEY 63400 M SEARCH module 464 DEKEY 64000 M SEARCH module 565 RELEA 34000 Release directory block66 REQUE 10000 X M TASK-QUEUE manager (***)67 AFSET 11000 M ACTIVE FILE processing for SWAP70 SIGPA 10000 M Signal or break71 MTFIL 32000 X CALL 71 (TAPE VTOC)72 GATHR 31000 CALL 7273 MPCHAR 34000 CALL 2674 CLC 33000 Compare bytes75 SORT 33000 X CALL 6576 SCATR 31000 N CALL 73(***) only for NIROS 3.3 with an initial system loader!DSB No. Name Location XNDMR Function

77 MTAPE 31000 X CALL 70100 FDALL 21400 X Floppy disc functions101 HAZL 16400 CALL 51102 PACK 30400 CALL 63103 UNPAC 30400 CALL 61104 EDITN 17000 CALL 62105 EDITA 17000 N CALL 63106 EDITD 17000 N CALL 64107 REOPT 20000 X REORG directory110 MTCAS 42400 CALL 82111112



126

NIROS


113114 DRCD 35000 Alter DRIVER code table115 CNDID 11400 CALL 25116117120 MVUP 17400 CALL 2121 MVDN 17400 N R CALL 3122 DGID 22400 CALL 4123 TRANS 43000 Data transmission124 ALBAS 17400 Assign basic file125 FFQU 36400 R Search file in resident index126127 ASSIGN 37400 Printer assignment130 BIMAN 35400 CALL 20131 FPBIN 35400 CALL 21132 BINFP 35400 CALL 22133 SUBSTR 36000 CALL 23134 ISRAEL 36000 CALL 24135136137140 ICHK 44000 X CALL 1141 FSGEN 45400 FIMAS/SORBAS142 FSNAC 46000 FIMAS/SORBAS143 FSIF 46400 X FIMAS/SORBAS144 FSDYN 47400 FIMAS/SORBAS145 FSCON 50000 X FIMAS/SORBAS146 FSRWC 51000 X FIMAS/SORBAS147 FSRWF 52000 X FIMAS/SORBAS150 FSDI 53000 X FIMAS/SORBAS151 FSDIM 54000 X FIMAS/SORBAS152 HDGET 43400 D Physical disc access (UT)153 BLGET 43400 D Physical disc access (UT)154 BLPUT 43400 ND Physical disc access (UT)155 STMAN 45000 CALL 90DSB No. Name Location XNDMR Function

156 FSDI 55000 X FIMAS/SORBAS157 FSEDI 65000 X FIMAS/SORBAS160 FSEDT 57000 FIMAS/SORBAS161 FSLET 57400 FIMAS/SORBAS162 FSINI 60000 FIMAS/SORBAS163 FSCHK 60000 FIMAS/SORBAS164 FSNED 60400 X FIMAS/SORBAS165 FSRWT 61400 FIMAS/SORBAS166167170171



127

NIROS


172173174175176 SEARCH 62400 X M SEARCH allocator177 INVST 40000 CALL 91

Explanation “XND”: X = expanded DISCSUB

N = DISCSUB uses routines of other DISCSUBS. This DISCSUB becomes memory-resident if memory- resident DISCSUBS use its routines.

D = DISCSUB may not be memory-resident.

R = If possible, should be made resident.

M = must be resident.

28.8 Driver List

T Filename GR Version M/K DAP RAP CommentS $ALMD 2 27400 M X BA control DAPS $ALMR 2 18430 M X BA control RAP$ $CAS 4 1841 M Cassette channel program$ $CRD 2 35067 K LKL 500 CRD/MIN channel program$ CRD1 3 37259 K LKL 90 CRD/MIN channel program$ $DEC 8 3430 M Floating point arithmetic$ $FD 3 50884 K Floppy disc channel program$ $JPTR 4 13562 K only Japan$ $SPTR 4 19638 K only Japan$ $LPT 5 25795 K NND channel program$ $LPT1 5 30334 K Record printer channel program$ $LPTR 4 60837 K NND channel program (with $LPT)



128

NIROS


$ LPTRS 4 61057 K 2nd NND channel program$ $LPTS 5 27127 K 2nd NND channel program (with

$LPTRS)$ $MTX 5 108 K Magnetic tape channel program$ $NLC 6 53686 K DFU channel program$ $ORDP 4 1354 K only USA$ $PHAD 2 35096 M X Phantom port control DAP$ $PHAR 2 33988 M X Phantom port control RAP$ $RPF0 2 27396 K X BA-ALM-KAN 0 FF channel program$ $RPF1 2 27398 K X BA-ALM-KAN 1 FF channel program$ $RPF2 2 27400 K X BA-ALM-KAN 2 FF channel program$ $RPF3 2 27402 K X BA-ALM-KAN 3 FF channel program$ $RPF4 2 27404 K X BA-ALM-KAN 4 FF channel program$ $RPF5 2 27406 K X BA-ALM-KAN 5 FF channel program$ $RPF6 2 27408 K X BA-ALM-KAN 6 FF channel program$ $RPF7 2 27410 K X BA-ALM-KAN 7 FF channel program$ RPL0 5 48357 K X BA-ALM-KAN 0 LL channel program$ RPL1 3 50685 K X BA-ALM-KAN 1 LL channel program$ $RPL2 3 50691 K X BA-ALM-KAN 2 LL channel program$ $RPL3 3 50697 K X BA-ALM-KAN 3 LL channel program$ $RPL4 3 50703 K X BA-ALM-KAN 4 LL channel program$ $RPL5 3 50709 K X BA-ALM-KAN 5 LL channel program$ $RPL6 3 50715 K X BA-ALM-KAN 6 LL channel program$ $RPL7 3 50721 K X BA-ALM-KAN 7 LL channel program$ $RPR0 2 28066 K X BA-ALM-KAN 0 RL channel program$ $RPR1 2 28068 K X BA-ALM-KAN 1 RL channel program$ $RPR2 2 28070 K X BA-ALM-KAN 2 RL channel program$ $RPR3 2 28072 K X BA-ALM-KAN 3 RL channel program$ $RPR4 2 28074 K X BA-ALM-KAN 4 RL channel program$ $RPR5 2 28076 K X BA-ALM-KAN 5 RL channel program$ $RPR6 2 28078 K X BA-ALM-KAN 6 RL channel program$ $RPR7 2 28080 K X BA-ALM-KAN 7 RL channel program$ $RTC 2 29059 M Data transfer for channel programs

28.9 SWAPPING/PARTITIONING

As recently confirmed, there is still uncertainty related to SWAPPING and PARTITIONING. That is why all aspects must be clearly explained and considered if a PARTITIONING SYSTEM is to be created. SWAPPING SYSTEMS should not be installed for systems with sufficient memory equipment.

concept definition

PARTITIONING: Division of available memory in program processing areas. As many tasks as created partitions may simultaneously be resident.

SWAPPING: Outsourcing and storing of partitions to/from the



129

NIROS


magnetic disc, if several tasks have to be run simultaneously when partitions are available.

If a single partition is available but several tasks have to run simultaneously, a SWAPPING SYSTEM should be installed.

If several partitions are available but a larger number of tasks than the one of partitions should be run, a mixed SWAPPING/PARTITIONS SYSTEM will be installed by NIROS.

Following must be noted when creating a system with SYSMOD in order to avoid SWAPPING:

CHANGE HARDWARE SPECIFICATIONS ............ 0

- is a computer configured with ADDRESS MAP REGISTER?

0. CURRENT VALUE: Y ADDRESS MAP REGISTERS AVAILABLE? Y OR N)

“Y” should mainly be entered here.

- Does the configured memory size match the installed memory?

1. CURRENT VALUE: XXX CORE SIZE IN KB

The entered value may not be greater than the capacity of the installed memory.

CHANGE SOFTWARE SPECIFICATIONS ............... 1

- How big is the ACTIVE FILE (main partition)

ACTIVE FILE SIZE .......... 0

Is entered in KB. Must be at least large enough to accept the largest program (incl. data area). The entry must not be smaller than 12 KB, or else the system components (e.g. TAMOS D2DUTIL) will not be executable anymore. This requirement determines the size of the main partition (see PARTITIONS).

- How many workstations exit?



130

NIROS


PORT CHARACTERISTICS ..... 3 NUMBER OF PORTS .......... 0

For the configured drivers ($ALMD or $ALMR)

$ALMD = number of workstations (DAP) minus 1 $PHAD = 1 $ALMR = number of workstations (RAP) minus 1 $PHAR = 1 $ALMR and $ALMD resp. $PHAR and $PHAD may not be activated simultaneously in the same system.

- How many partitions are configured and how large are the partitions configured?

PARTITIONS ................... 5

If possible, as many partitions are configured as the total “NUMBER OF PORTS” workstations (incl. phantom port).

If partitions are configured with a smaller size in KB than that of the configured ACTIVE FILE, these partitions will only be used by programs that have been appropriately protected with the SAVE command.

The SAVE command is described in the basic handbook and in the user handbook.

28.10 Memory Assignment

The following rules apply to the assignment of available memory:

a) The NIROS core, the processor area and the main partitions are assigned consecutively starting from address 0.

b) Variable NIROS components such as:

- DISCSUBS - PCB - DRIVERS

are assigned consecutively starting from TOPWORD OF CORE.



131

NIROS


c) Additional partitions are assigned consecutively starting from the highest possible memory address.

NIROS system core:- real time control system- time-sharing management- partitioning managementProcessor areaMain partitionIts size matches that of the ACTIVE FILEEventual available space within the first 64 KBVariable NIROS components:- memory-resident DISCSUBS- port control areas- file control tables- channel programs- port I/O buffer- partition management table- disc buffers (HBA, BSA, HXA etc.)- common areas

Additional partitions

28.11 Determination of a Time Slice Size

Two basic criteria apply to the determination of a time slice size.

a) The number of simultaneously running tasks.b) The types of the simultaneously running tasks.

Basically, there are two different types of tasks:

a) DIALOG TASK, which uses 50% of the time slice over a longer period of time.b) BATCH TASK, which normally uses 100% of the time slice.

The required response time per task should be one second. This means that each task should be refreshed one time per second.



132

ADR 0

ADR BPS

ADR BUS

TOPWORD OF CORESMALLER THAN 64 KB

NIROS


Due to the ranging use of time slices, DIALOG TASKS and BATCH TASKS are rated differently for the calculation of a time slice size.

a) BATCH TASK rating = 2b) DIALOG TASK rating = 1

The following formula is used for calculating the time slice size:

1,5 / SUM OF THE TASK RATINGS

Example: We are going to calculate the time slice size for a system with 3 screens + phantom port.

We will assume that the screen runs DIALOG TASKS and the phantom port a BATCH TASK.

Port 0: DIALOG TASK Rating = 1 Port 1: BATCH TASK Rating = 2 Port 2: DIALOG TASK Rating = 1 Port 3: DIALOG TASK Rating = 1

= 5

Calculation: 1,5 / 5 = 3

This means that the size of a time slice should be 300 ms.



133

· web viewall other disc addresses are in negative form within the active file header. the type...

Documents