|
DataMuseum.dkPresents historical artifacts from the history of: RegneCentralen RC850 |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about RegneCentralen RC850 Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 35328 (0x8a00)
Types: RcTekst
Names: »43G12165.WP«
└─⟦975e936c7⟧ Bits:30005865 Manualer - tekstfiler 43-GL afdelingen
└─⟦this⟧ »43G12165.WP«
╱04002d4e0a0006000000000201413140000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱
i↲
↲
┆b0┆┆a1┆TABLE OF CONTENTS ┆05┆PAGE↲
↲
┆b0┆1. INTRODUCTION ┆f0┆........................................... 1↲
↲
┆b0┆2. DESCRIPTION OF THE CENTERNET SOFTWARE SYSTEM┆f0┆ ........... 2↲
2.1 Logical Division of the Software System ........... 2↲
2.2 Organization on the RC8000 Disc ................... 3↲
2.2.1 Base Organization at RC Computer ........... 4↲
2.2.2 Base Organization at a Customer ............ 4↲
↲
┆b0┆3. CONFIGURATION OF THE CENTERNET SOFTWARE SYSTEM ┆f0┆......... 6↲
3.1 On CENTERNET System Configuration ................. 6↲
3.2 Configuration of the Individual Modules ........... 7↲
3.2.1 The SMT Module ............................. 8↲
3.2.2 The HI Module .............................. 8↲
3.2.3 The SC Module .............................. 9↲
3.2.4 The TS Module .............................. 9↲
3.2.5 The DTE Module ............................. 11↲
3.2.6 The CNADAM Module .......................... 11↲
↲
┆b0┆4. GENERATION OF THE CENTERNET SOFTWARE SYSTEM ┆f0┆............ 12↲
4.1 Console Log during Generation ..................... 12↲
↲
┆b0┆5. INSTALLATION OF THE CENTERNET SOFTWARE SYSTEM ┆f0┆.......... 14 ↲
5.1 Resource Requirements during Load ................. 14↲
5.2 Console Log during Load ........................... 15↲
↲
↲
┆b0┆APPENDICES:↲
↲
┆b0┆A. REFERENCES ┆f0┆............................................ 17↲
↲
┆b0┆┆b0┆B. LOOKUPS ON THE CENTERNET SOFTWARE SYSTEM┆f0┆ .............. 18↲
↲
┆b0┆C. CONFIGURATION FILES ┆f0┆...................................↲
C.1 Standard Configuration File CRPARMENV ............↲
C.2 Example of a Special Configuration File ..........↲
↲
════════════════════════════════════════════════════════════════════════
↓
ii ↲
════════════════════════════════════════════════════════════════════════
↓
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆ ┆0b┆↲
↲
┆b0┆┆a1┆1. INTRODUCTION↲
↲
┆84┆This manual is directed towards three groups of readers, ↓
┆19┆┆89┆┄┄namely↲
↲
1) ┆84┆Those, who want to get a brief overview of the ↓
┆19┆┆8c┆┄┄CENTERNET software system in terms of the various ↓
┆19┆┆8c┆┄┄files, which constitute the system and to get an idea ↓
┆19┆┆8c┆┄┄of the contents of these file and so on. Those ↓
┆19┆┆8c┆┄┄readers are recommended to read chapter 2 and ↓
┆19┆┆8c┆┄┄appendix B.↲
↲
2) ┆84┆Those, who want to see, how the system generation ↓
┆19┆┆8c┆┄┄and/or system installation is carried out. This group ↓
┆19┆┆8c┆┄┄of readers is referred to chapter 4 and 5.↲
↲
3) ┆84┆Those, who want to learn about system configuration - ↓
┆19┆┆8c┆┄┄i.e. how the software configuration parameters are ↓
┆19┆┆8c┆┄┄adjusted to fit a specific installation ↓
┆19┆┆8c┆┄┄(customization). This is described in chapter 3.↲
↲
┆84┆It is not the intention to go into every detail because ↓
┆19┆┆89┆┄┄it is felt that ↲
↲
- ┆84┆readers with little experience in the CENTERNET ↓
┆19┆┆8b┆┄┄software system might very well be overwhelmed.↲
↲
- ┆84┆a lot of the details are of very little importance - ↓
┆19┆┆8b┆┄┄this includes details about customization too. Almost ↓
┆19┆┆8b┆┄┄only systems programmers at RC Computer may have the ↓
┆19┆┆8b┆┄┄need for all the details, which may be found in the ↓
┆19┆┆8b┆┄┄reference manuals listed in appendix A and referred to ↓
┆19┆┆8b┆┄┄from elsewhere in this manual.↲
↲
┆84┆Part of the PAXNET software system is contained in the ↓
┆19┆┆89┆┄┄CENTERNET software system. This manual tells nothing ↓
┆19┆┆89┆┄┄about how to configurate or otherwise manipulate that ↓
┆19┆┆89┆┄┄part of the CENTERNET software system - instead some ↓
┆19┆┆89┆┄┄relevant documentation is referred later on.↲
↲
┆84┆Readers not familiar with CENTERNET is recommended to ↓
┆19┆┆89┆┄┄get a system overview in ref. (1), chapter 1 through 4.↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆2. DESCRIPTION OF THE CENTERNET SOFTWARE SYSTEM↲
↲
┆84┆The CENTERNET Software System comprises quite a lot of ↓
┆19┆┆89┆┄┄files and at a first glance it may seem difficult to ↓
┆19┆┆89┆┄┄survey the system. However, the total set of files may ↓
┆19┆┆89┆┄┄logically be divided in 3 subsets, which in turn may be ↓
┆19┆┆89┆┄┄divided in smaller subsets, which comprise the files ↓
┆19┆┆89┆┄┄concerning a single module. The term "module" is ↓
┆19┆┆89┆┄┄somewhat vague, but in this context a precise definition ↓
┆19┆┆89┆┄┄is impossible, however - the TS (┆a1┆T┆e1┆ransport ┆a1┆S┆e1┆tation), ↓
┆19┆┆89┆┄┄which implement the OSI layer 4, may serve as an example ↓
┆19┆┆89┆┄┄of a module.↲
↲
┆84┆The next section gives a short description of this ↓
┆19┆┆89┆┄┄logical division, while a complete catalogue containing ↓
┆19┆┆89┆┄┄all the modules, their files and the contents of ↓
┆19┆┆89┆┄┄possible library files can be found in appendix B.↲
↲
↲
┆b0┆┆a1┆2.1 Logical Division of the Software System↲
↲
┆84┆The CENTERNET System Software includes both modules ↓
┆19┆┆89┆┄┄intended for RC8000 as well as modules intended for ↓
┆19┆┆89┆┄┄RC3502.↲
↲
┆84┆The latter ones may in turn be grouped, when it is ↓
┆19┆┆89┆┄┄remembered that some of them only run in such ↓
┆19┆┆89┆┄┄combinations that RC3502 operates as a terminal ↓
┆19┆┆89┆┄┄concentrator (possibly including a host interface ↓
┆19┆┆89┆┄┄module, which connects the RC3502 in question to e.g. an ↓
┆19┆┆89┆┄┄RC8000 host computer) while other modules participate ↓
┆19┆┆89┆┄┄only in combinations making RC3502 operate as a network ↓
┆19┆┆89┆┄┄node. (For the sake of completeness it is mentioned that ↓
┆19┆┆89┆┄┄especially the TS (┆b0┆┆f0┆┆a1┆T┆e1┆ransport ┆a1┆S┆e1┆tation) module appears ↓
┆19┆┆89┆┆81┆┄in both combinations). A terminal concentrator is ↓
┆19┆┆89┆┆81┆┄normally denoted a TC for short, while a network mode is ↓
┆19┆┆89┆┆81┆┄called a PAXNET node as most of the modules running here ↓
┆19┆┆89┆┆81┆┄has been developed in the well known PAXNET project.↲
↲
┆84┆These remarks may now be summarized as follows: The ↓
┆19┆┆89┆┄┄CENTERNET Software System is constituted by 3 subsets:↲
↲
1) RC8000 modules.↲
2) TC modules.↲
3) PAXNET modules.↲
↲
┆84┆The modules themselves comprises various number of ↓
┆19┆┆89┆┄┄files, which in nearly all cases belong to one of the ↓
┆19┆┆89┆┄┄following four types:↲
↲
1) ┆84┆Text files, which usually either contain a (program) ↓
┆19┆┆8c┆┄┄source text or is a job file comprising FP commands ↓
┆19┆┆8c┆┄┄(compiler invocation etc.).↲
↲
2) ┆84┆Binary files containing either a program for RC8000 ↓
┆19┆┆8c┆┄┄or a load file for RC3502.↲
↲
════════════════════════════════════════════════════════════════════════
↓
3) ┆84┆LIB files - i.e. files containing other files. Such a ↓
┆19┆┆8c┆┄┄library may be manipulated by means of the LIB ↓
┆19┆┆8c┆┄┄utility program. Manipulation may for instance be ↓
┆19┆┆8c┆┄┄insertion or extraction of one of the files in the ↓
┆19┆┆8c┆┄┄library. Source texts and job files concerning a ↓
┆19┆┆8c┆┄┄single TC module are often collected in a few ↓
┆19┆┆8c┆┄┄(possibly only one) LIB files.↲
↲
4) ┆84┆PLIB files, which are RTP (┆a1┆R┆e1┆eal ┆a1┆T┆e1┆ime ┆a1┆P┆e1┆ascal) ↓
┆19┆┆8c┆┄┄libraries containing one or more compiled modules or ↓
┆19┆┆8c┆┄┄procedures (note that a PLIB file ┆a1┆cannot┆e1┆ be loaded ↓
┆19┆┆8c┆┄┄directly into RC3502). This type of library may be ↓
┆19┆┆8c┆┄┄manipulated by for instance the utility programs ↓
┆19┆┆8c┆┄┄PLIBINSERT, PLIBEXTRACT, CRC16 or CROSSLINK.↲
↲
┆84┆This division of the software system is to a large ↓
┆19┆┆89┆┄┄extend reflected in the listings in appendix B.↲
↲
┆b0┆┆84┆NOTE┆f0┆: Some files not mentioned here are necessary to ↓
┆19┆┆89┆┆81┆┄get the system operating. These files has to be ↓
┆19┆┆89┆┆81┆┄installed when the CENTERNET software system is ↓
┆19┆┆89┆┆81┆┄installed for the very first time, but they are not part ↓
┆19┆┆89┆┆81┆┄of what is otherwise called the CENTERNET software ↓
┆19┆┆89┆┆81┆┄system. The experienced reader knows these files as ↓
┆19┆┆89┆┆81┆┄COMFILE, COMFILEPRINT and so on. These Files are oftenly ↓
┆19┆┆89┆┆81┆┄called NC (┆a1┆N┆e1┆etwork ┆a1┆C┆e1┆ontrol) Files.↲
↲
↲
┆b0┆┆a1┆2.2 Organization on the RC8000 Disc↲
↲
┆84┆All of the CENTERNET software system is normally stored ↓
┆19┆┆89┆┄┄on a single RC8000 disc. Yet - the real key to ↓
┆19┆┆89┆┄┄understand the various possibilities that exist when ↓
┆19┆┆89┆┄┄system generation and installation takes place lies in ↓
┆19┆┆89┆┄┄knowledge about the base organization in the disc ↓
┆19┆┆89┆┄┄catalogue - i.e. how the files are grouped.↲
↲
┆84┆The first thing to remember in this connection is that ↓
┆19┆┆89┆┄┄the RC3502 computer exists in two models, namely model 1 ↓
┆19┆┆89┆┄┄and model 2. The two models differ in a way that ↓
┆19┆┆89┆┄┄requires the RTP compiler to exist in two matching ↓
┆19┆┆89┆┄┄versions that work with the same source texts as input, ↓
┆19┆┆89┆┄┄but produce different binary code output. As a given ↓
┆19┆┆89┆┄┄customer is expected to have either model 1 machines ↓
┆19┆┆89┆┄┄only or model 2 machines only, he needs only to have ↓
┆19┆┆89┆┄┄software appropiate for the model in question. On the ↓
┆19┆┆89┆┄┄other hand RC Computer itself has of course to be able ↓
┆19┆┆89┆┄┄to maintain and generate software systems appropriate ↓
┆19┆┆89┆┄┄for either model and therefore the base organization at ↓
┆19┆┆89┆┄┄RC Computer itself differs slightly from the one ↓
┆19┆┆89┆┄┄recommended to be used by a customer.↲
↲
┆84┆In the following subsections the terms "binary model 1" ↓
┆19┆┆89┆┄┄and "binary model 2" are used. They cover the PLIB files ↓
┆19┆┆89┆┄┄and those binary files (see section 2.1), which contain ↓
┆19┆┆89┆┄┄RTP binary code and loadfiles for RC3502 (either it is ↓
┆19┆┆89┆┄┄acting as a TC or as a PAXNET node).↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆2.2.1 Base Organization at RC Computer↲
↲
┆84┆This section describes how the CENTERNET software system ↓
┆19┆┆89┆┄┄is organized as regards to the bases belonging to the ↓
┆19┆┆89┆┄┄file descriptions in the RC8000 disc catalogue↲
↲
-8388607 0 99900 99999 ┆05┆8388605╞ ↲
┆a1┆ ┆e1┆ ┆a1┆ ┆e1┆ ┆a1┆ ┆a1┆ ┆e1┆ ┆a1┆┆05┆↲
CENTERNET software system ↲
↲
┆84┆The following sets of files have the interval 0 - 99999 ↓
┆19┆┆89┆┄┄as their base:↲
↲
- ┆84┆All source texts concerning RC8000, TC and PAXNET ↓
┆19┆┆8b┆┄┄modules.↲
↲
- ┆84┆All FP job files and binary RC8000 modules.↲
↲
- All binary model 1 files.↲
↲
With base 99900 - 99999:↲
↲
- All binary model 2 files.↲
↲
┆84┆The SMM (┆a1┆S┆e1┆croll ┆a1┆M┆e1┆ode ┆a1┆M┆e1┆apping module) is the only module, ↓
┆19┆┆89┆┄┄which for special reasons has its binary program file ↓
┆19┆┆89┆┄┄placed on the bases -8388607 - 8388605 (oftenly called ↓
┆19┆┆89┆┄┄system bases).↲
↲
┆84┆The NC (┆a1┆N┆e1┆etwork ┆a1┆C┆e1┆ontrol) files, such as DESFILE, ↓
┆19┆┆89┆┄┄NCTLOGFILE and so on, are placed on the bases 0-9999. ↓
┆19┆┆89┆┄┄(Not part of the CENTERNET software system).↲
↲
┆84┆Besides the interval 0 - 99999 contains on smaller bases ↓
┆19┆┆89┆┄┄(e.g. 0 - 10, ..., 80 - 90, ...) a variety of files, ↓
┆19┆┆89┆┄┄which are ┆a1┆not part┆e1┆ of the CENTERNET software system, but ↓
┆19┆┆89┆┄┄are used for maintenance and operating purposes.↲
↲
┆84┆From the preceding it is seen that generating a tape ↓
┆19┆┆89┆┄┄containing the CENTERNET software system including ↓
┆19┆┆89┆┄┄binary model 1 files as well as binary model 2 files can ↓
┆19┆┆89┆┄┄be performed quite easily.↲
↲
↲
┆b0┆┆a1┆2.2.2 Base Organization at a Customer↲
↲
┆84┆Here it is described how the CENTERNET software system ↓
┆19┆┆89┆┄┄is recommended to be organized at a customers site as ↓
┆19┆┆89┆┄┄regards to the bases belonging to the file descriptions ↓
┆19┆┆89┆┄┄in the RC8000 disc catalogue.↲
↲
-8388607 0 99999 ┆05┆8388605↲
┆a1┆ ┆e1┆ ┆a1┆ ┆e1┆ ┆a1┆┆05┆↲
CENTERNET software system ↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆84┆The following sets of files have the interval 0 - 99999 ↓
┆19┆┆89┆┄┄as their base:↲
↲
- ┆84┆All source texts concerning RC8000, TC and PAXNET ↓
┆19┆┆8b┆┄┄modules↲
↲
- ┆84┆All binary model 1 files ┆a1┆or┆e1┆ all binary model 2 files ↓
┆19┆┆8b┆┄┄depending on the equipment in question (which is ↓
┆19┆┆8b┆┄┄supposed to be ┆a1┆either┆e1┆ model 1 ┆a1┆or┆e1┆ model 2 ).↲
↲
┆84┆The SMM (┆a1┆S┆e1┆croll ┆a1┆M┆e1┆ode ┆a1┆M┆e1┆apping module) is the only module, ↓
┆19┆┆89┆┄┄which for special reasons has its binary program file ↓
┆19┆┆89┆┄┄placed on the bases -8388607 - 8388605 (oftenly called ↓
┆19┆┆89┆┄┄system bases).↲
↲
┆84┆Operation of the system does not strictly demand the ↓
┆19┆┆89┆┄┄bases 0 - 99999 to be selected, even though a system ↓
┆19┆┆89┆┄┄tape delivered by RC Computer contains an installation ↓
┆19┆┆89┆┄┄job, which places the software system on these bases ↓
┆19┆┆89┆┄┄unless other bases should be selected for test purposes ↓
┆19┆┆89┆┄┄at installation time. ┆a1┆BUT BE CAREFUL┆e1┆ and contact RC ↓
┆19┆┆89┆┄┄Computer if in any doubt.↲
↲
┆84┆Furthermore it is recommended that the NC (┆a1┆N┆e1┆etwork ↓
┆19┆┆89┆┄┄┆a1┆C┆e1┆ontrol) files, such as DESFILE, NCTLOGFILE and so on, ↓
┆19┆┆89┆┄┄are placed on a set of bases below 0-99999, e.g. on the ↓
┆19┆┆89┆┄┄bases 0-9999.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆3. CONFIGURATION OF THE CENTERNET SOFTWARE SYSTEM↲
↲
┆84┆This chapter deals with the set up of the parameters ↓
┆19┆┆89┆┄┄inhered in the CENTERNET software system. First, section ↓
┆19┆┆89┆┄┄3.1 introduces some basic considerations, which the ↓
┆19┆┆89┆┄┄reader should know about before moving into the art of ↓
┆19┆┆89┆┄┄CENTERNET software system configuration. Next, section ↓
┆19┆┆89┆┄┄3.2 gives some general information about TC configura- ↓
┆19┆┆89┆┄┄tion and the following subsections contain the details ↓
┆19┆┆89┆┄┄about the important configuration parameters concerning ↓
┆19┆┆89┆┄┄the individual modules. Section 3.3 outlines the overall ↓
┆19┆┆89┆┄┄TC configuration, while two configuration examples are ↓
┆19┆┆89┆┄┄found in appendix B.↲
↲
┆b0┆┆84┆NOTE:┆f0┆ This chapter does not cover configuration of the ↓
┆19┆┆89┆┆81┆┄PAXNET part of the CENTERNET software system - instead ↓
┆19┆┆89┆┆81┆┄the reader should consult ref. (2).↲
↲
↲
┆b0┆┆a1┆3.1 On CENTERNET System Configuration↲
↲
┆84┆What does CENTERNET software configuration mean, one may ↓
┆19┆┆89┆┄┄ask. A concise answer to this question can hardly be ↓
┆19┆┆89┆┄┄given, but in this context the following approach has ↓
┆19┆┆89┆┄┄been chosen: At configuration time the starting point is ↓
┆19┆┆89┆┄┄a ┆a1┆hardware configuration┆e1┆ that is fixed as regards to ↓
┆19┆┆89┆┄┄topology and connections for terminals and host ↓
┆19┆┆89┆┄┄computers. This means that except for the number of ↓
┆19┆┆89┆┄┄memory boards in the RC3502 computers, all the hardware ↓
┆19┆┆89┆┄┄including HDLC connections is laid down, when the ↓
┆19┆┆89┆┄┄software configuration starts. (Note that calculation of ↓
┆19┆┆89┆┄┄the memory claim for RC3502 is not part of this manual).↲
↲
┆84┆The configuration is then carried out according to a ↓
┆19┆┆89┆┄┄top-down approach, meaning that the upper layers ↓
┆19┆┆89┆┄┄(modules) (in the OSI sense) are configured first.↲
↲
┆84┆The very first thing to understand is that even though ↓
┆19┆┆89┆┄┄nearly all modules contain quite a lot of configuration ↓
┆19┆┆89┆┄┄parameters, then many of these are of minor importance ↓
┆19┆┆89┆┄┄in the sense that different set ups only causes slightly ↓
┆19┆┆89┆┄┄different memory claims (1 kbyte of memory is considered ↓
┆19┆┆89┆┄┄to be of minor importance here). As a consequence these ↓
┆19┆┆89┆┄┄unessential parameters are in a standard configurated ↓
┆19┆┆89┆┄┄CENTERNET software system assigned such values that ↓
┆19┆┆89┆┄┄changes should be needed only seldomly. Therefore these ↓
┆19┆┆89┆┄┄parameters are not mentioned in the following.↲
↲
┆84┆The next thing to know about is the existence of two ↓
┆19┆┆89┆┄┄types of parameters:↲
↲
1) ┆84┆"Hard" parameters - i.e. parameters, which can be ↓
┆19┆┆8c┆┄┄changed only in the source texts concerning the ↓
┆19┆┆8c┆┄┄relevant modules.↲
↲
════════════════════════════════════════════════════════════════════════
↓
2) ┆84┆"Soft" parameters - i.e. parameters, which are handed ↓
┆19┆┆8c┆┄┄over to the individual modules (processes) at start-↓
┆19┆┆8c┆┄┄up time (create parameters).↲
↲
┆84┆These parameters are changed in the source text ↓
┆19┆┆89┆┄┄concerning a single module - namely CNADAM, which is the ↓
┆19┆┆89┆┄┄father process of the other processes being of interest ↓
┆19┆┆89┆┄┄in this connection - meaning that the latter ones are ↓
┆19┆┆89┆┄┄created and started by CNADAM, which therefore sets up ↓
┆19┆┆89┆┄┄and hands over these parameters.↲
↲
┆84┆Furthermore, by means of LCP operations to CNADAM most ↓
┆19┆┆89┆┄┄of the "soft" parameters may be assigned new values, ↓
┆19┆┆89┆┄┄which are put into operation by a restart of the TC in ↓
┆19┆┆89┆┄┄question (but at a ┆a1┆reload┆e1┆ of the TC the parameters are ↓
┆19┆┆89┆┄┄of course always assigned their original configured ↓
┆19┆┆89┆┄┄values).↲
↲
┆84┆When the configuration is carried out, some knowledge ↓
┆19┆┆89┆┄┄about the CNADAM module is necessary. It is found in ↓
┆19┆┆89┆┄┄ref. (3), while the less important information about the ↓
┆19┆┆89┆┄┄LCP operations just mentioned is found in ref. (4).↲
↲
┆84┆In the rest of this chapter only the "soft" parameters ↓
┆19┆┆89┆┄┄are mentioned because↲
↲
- ┆84┆Nearly all important (i.e. memory consuming) ↓
┆19┆┆8b┆┄┄parameters are "soft".↲
↲
- ┆84┆Configuration of "hard" parameters is - in practice - ↓
┆19┆┆8b┆┄┄believed to require co-operation from the RC Computer ↓
┆19┆┆8b┆┄┄staff.↲
↲
┆84┆Finally it should be noted that even though the software ↓
┆19┆┆89┆┄┄configuration has a fixed hardware configuration as its ↓
┆19┆┆89┆┄┄starting point, then the software configuration is ┆a1┆per ↓
┆19┆┆89┆┄┆84┆TC┆e1┆ ┆e1┆- i.e. the SC module in one TC may very well be ↓
┆19┆┆89┆┄┄configured different from the SC running in another TC. ↓
┆19┆┆89┆┄┄Accordingly, there shall exist a special configuration ↓
┆19┆┆89┆┄┄file for each TC - cf. app. C.2. The configuration of a ↓
┆19┆┆89┆┄┄single TC now turns out to proceed in 3 steps:↲
↲
1) ┆84┆Write the wanted configuration parameters in a ↓
┆19┆┆8c┆┄┄special configuration file (a normal text file).↲
↲
2) ┆84┆Compile CNADAM.↲
↲
3) ┆84┆Use CRC16 to create the bootfile for RC3502.↲
↲
↲
┆b0┆┆a1┆3.2 Configuration of the Individual Modules↲
↲
┆84┆The following subsections describe the configuration ↓
┆19┆┆89┆┄┄parameters concerning the individual modules in such a ↓
┆19┆┆89┆┄┄way that firstly the superior parameters are discussed, ↓
┆19┆┆89┆┄┄after which follow those, which are either less ↓
┆19┆┆89┆┄┄important or depend on the foregoing ones.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆84┆The parameters are denoted by their names as found in ↓
┆19┆┆89┆┄┄CRPARMENV (app. C), which is the part of the CNADAM ↓
┆19┆┆89┆┄┄source text that defines all the "soft" parameters in a ↓
┆19┆┆89┆┄┄standard configurated CENTERNET software system. The ↓
┆19┆┆89┆┄┄default values stated by CRPARMENV are mentioned too.↲
↲
┆84┆For further information about all the configuration ↓
┆19┆┆89┆┄┄parameters, "soft" as well as "hard", please consult the ↓
┆19┆┆89┆┄┄relevant manuals, in ref. (5) through (10).↲
↲
↲
┆b0┆┆a1┆3.2.1 The SMT Module↲
↲
┆84┆def_max_t_port = 16;↲
↲
┆84┆Defines the maximum number of terminal ports (AMX ↓
┆19┆┆89┆┄┄ports). Should equal the number of physical terminal ↓
┆19┆┆89┆┄┄ports.↲
↲
def_max_na_ports = 3;↲
↲
┆84┆Defines the maximum number of special network artificial ↓
┆19┆┆89┆┄┄traffic ports. Terminal ports may be used for artificial ↓
┆19┆┆89┆┄┄traffic, whereas the reverse does not apply - i.e. at ↓
┆19┆┆89┆┄┄least 'def_max_na_ports' are at the disposal of ↓
┆19┆┆89┆┄┄artificial traffic. The default setting is considered to ↓
┆19┆┆89┆┄┄be reasonable in the most cases. ↲
↲
↲
┆b0┆┆a1┆3.2.2 The HI Module↲
↲
def_hi_ports = 11;↲
↲
┆84┆Defines the maximum number of host ports. Should be ↓
┆19┆┆89┆┄┄decided upon after an analysis of the requirements due ↓
┆19┆┆89┆┄┄to the host applications and the users. One user (e.g. ↓
┆19┆┆89┆┄┄terminal) occupies one host port.↲
↲
def_hi_midi = 300;↲
↲
┆84┆Defines the size (in bytes) of a number of buffers ↓
┆19┆┆89┆┄┄defined by↲
↲
def_no_midi = 43;↲
↲
┆84┆Defines the maximum value of the accumulated credit, ↓
┆19┆┆89┆┄┄which the HI can support to the current number of open ↓
┆19┆┆89┆┄┄ports having requested a buffer size of 'def_hi_midi' ↓
┆19┆┆89┆┄┄bytes or less.↲
↲
def_hi_max = 2001;↲
↲
┆84┆Defines the size (in bytes) of a number of buffers ↓
┆19┆┆89┆┄┄defined by↲
↲
def_no_max = 5;↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆84┆Defines the maximum value of the accumulated credit, ↓
┆19┆┆89┆┄┄which the HI can support to the current number of open ↓
┆19┆┆89┆┄┄ports having requested a buffer size of 'def_hi_max' ↓
┆19┆┆89┆┄┄bytes or less (but greater than 'def_hi_midi').↲
↲
↲
┆b0┆┆a1┆3.2.3 The SC Module↲
↲
def_max_portno = 25;↲
↲
┆84┆Defines the maximum accumulated number of SC ports, ↓
┆19┆┆89┆┄┄which the SC users may open. Should equal the sum of the ↓
┆19┆┆89┆┄┄number of ports, which the individual SC users are ↓
┆19┆┆89┆┄┄expected to open - i.e. ↲
↲
def_max_portno = def_max_t_port↲
+ def_max_na_port↲
+ def_hi_ports↲
+ ports concerning possible other users.↲
↲
def_max_lg_ports = 6;↲
↲
┆84┆Defines the maximum accumulated number of LG (┆a1┆L┆e1┆etter ↓
┆19┆┆89┆┄┄┆a1┆G┆a1┆┆a1┆┆e1┆ram) ports, which the SC users may open. NCP always ↓
┆19┆┆89┆┄┄opens a LG port, while the NC system and the SCAT module ↓
┆19┆┆89┆┄┄also use LG ports, if they are running on the TC in ↓
┆19┆┆89┆┄┄question.↲
↲
def_max_lg_con = 6;↲
↲
┆84┆Defines the maximum accumulated number of connections, ↓
┆19┆┆89┆┄┄which the SC users may initiate on the LG ports (one ↓
┆19┆┆89┆┄┄connection per remote DTE + two, if local connection is ↓
┆19┆┆89┆┄┄used).↲
↲
↲
┆b0┆┆a1┆3.2.4 The TS Module↲
↲
def_ts_conf = ts_conf_type(↲
2, 21, 31, 31,↲
┆84┆def_dte_max_chan + 1, def_dte_max_chan, 0, ↓
┆19┆┆89┆┄┄def_dte_max_chan + 2, ↲
2, 10, 3, 2,↲
def_dte_max_chan + 2, 0, 10, 3, ↲
1, ... 19 unessential parameters);↲
↲
┆84┆In the following those parameters, which are candidates ↓
┆19┆┆89┆┄┄for varying configuration values, are depicted by ↓
┆19┆┆89┆┄┄their series number in 'ts_conf_type', named according ↓
┆19┆┆89┆┄┄to ref. (8) and then explained.↲
↲
2: 'tcep_id_max'↲
┆84┆Maximum number of transport connections per TSAP. ↓
┆19┆┆8c┆┄┄Should equal the largest of the SC parameters ↓
┆19┆┆8c┆┄┄'def_max_portno' and 'def_max_lg_con'.↲
↲
════════════════════════════════════════════════════════════════════════
↓
3: 'pool_no_max'↲
┆84┆Should equal 'tcep_id_max'.↲
↲
4: 'tc_max'↲
┆84┆Maximum number of transport connections. Should equal ↓
┆19┆┆8c┆┄┄the sum of the SC parameters 'def_max_portno' and ↓
┆19┆┆8c┆┄┄'def_max_lg_con'. ↲
↲
5: 'nc_max'↲
┆84┆Maximum number of network connections - not to be ↓
┆19┆┆8c┆┄┄confused with transport connections. This is a subtle ↓
┆19┆┆8c┆┄┄parameter, which must be decided upon after a careful ↓
┆19┆┆8c┆┄┄analysis taking the following considerations into ↓
┆19┆┆8c┆┄┄account:↲
↲
1) ┆84┆The maximum number of remote DTE's with which the ↓
┆19┆┆8f┆┄┄local DTE is expected to communicate ↓
┆19┆┆8f┆┄┄simultaneously. At least one network connection is ↓
┆19┆┆8f┆┄┄required per DTE.↲
↲
2) ┆84┆The degree of multiplexing. The transport ↓
┆19┆┆8f┆┄┄connections are multiplexed onto network ↓
┆19┆┆8f┆┄┄connections according to:↲
↲
a) ┆84┆The TS parameters 15, 16 and 17. Terminals are ↓
┆19┆┆92┆┄┄normally put into the low throughput class - ↓
┆19┆┆92┆┄┄see parameter 14.↲
↲
b) ┆84┆The multiplexing of a number of transport ↓
┆19┆┆92┆┄┄connections onto the same network connection ↓
┆19┆┆92┆┄┄requires 1) same remote DTE address (endpoint) ↓
┆19┆┆92┆┄┄and 2) same throughput class.↲
↲
3) ┆84┆Local network connections (transport connections ↓
┆19┆┆8f┆┄┄looping in the TS) should be taken into account in ↓
┆19┆┆8f┆┄┄exactly the same way as remote network ↓
┆19┆┆8f┆┄┄connections.↲
↲
┆84┆No reasonable value for 'nc_max' can be forecasted.↲
↲
6: 'xdte_maxstream'↲
┆84┆Maximum number of external network connections, ↓
┆19┆┆8c┆┄┄'nc_max - 1' is normally a reasonable value (implying ↓
┆19┆┆8c┆┄┄one local connection).↲
↲
15: 't_low_no_tc_pr_nc'↲
┆84┆Maximum number of transport connections with ↓
┆19┆┆8c┆┄┄throughput class equal to low that can be multiplexed ↓
┆19┆┆8c┆┄┄onto the same network connections. 10-20 should be ↓
┆19┆┆8c┆┄┄reasonable values.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆3.2.5 The DTE Module↲
↲
┆84┆def_dte_max_chan = 5;↲
↲
┆84┆Defines the maximum number of simultaneous virtual ↓
┆19┆┆89┆┄┄calls. Should equal the TS parameter 6: ↓
┆19┆┆89┆┄┄'xdte_maxstream'.↲
↲
def_dte_conf_rec = dte_cp_type (......);↲
↲
┆84┆The set up of these parameters are very much dependent ↓
┆19┆┆89┆┄┄on the requirements due to the transportation network. ↓
┆19┆┆89┆┄┄For the time being the default values are reasonable and ↓
┆19┆┆89┆┄┄in case of changes in the requirements, ref. (9) is ↓
┆19┆┆89┆┄┄recommended.↲
↲
↲
┆b0┆┆a1┆3.2.6 The CNADAM Module↲
↲
┆84┆Configuration of CNADAM itself does not concern the ↓
┆19┆┆89┆┄┄maximum number of ports or the like - instead the task ↓
┆19┆┆89┆┄┄here is to tell CNADAM, which processes are to be linked ↓
┆19┆┆89┆┄┄and created automatically, the DTE address of the TC ↓
┆19┆┆89┆┄┄('tc_adr') and so on. The best understanding of the ↓
┆19┆┆89┆┄┄CNADAM configuration is obtained from a study of app. C ↓
┆19┆┆89┆┄┄and ref. (2) and thus no further explanation is given ↓
┆19┆┆89┆┄┄here.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆e1┆┆b0┆┆a1┆4. GENERATION OF THE CENTERNET SOFTWARE SYSTEM↲
↲
┆84┆All the commands needed to generate a standard system ↓
┆19┆┆89┆┄┄tape (where 'standard' refers to the set of files ↓
┆19┆┆89┆┄┄included on the tape - not to be confused with a ↓
┆19┆┆89┆┄┄┆a1┆standard configurated┆e1┆ system, (cf. chapter 3) are ↓
┆19┆┆89┆┄┄collected in a single file (job file), which is ┆a1┆not ↓
┆19┆┆89┆┄┆84┆part┆e1┆ of the CENTERNET software system and this file is ↓
┆19┆┆89┆┄┄therefore not found at the customers site and ↓
┆19┆┆89┆┄┄consequently system tape generation here is not ↓
┆19┆┆89┆┄┄possible. A consequence of this approach is that the ↓
┆19┆┆89┆┄┄system generation is accomplished essentially by the ↓
┆19┆┆89┆┄┄invocation of a single 's' command. The tape applied ↓
┆19┆┆89┆┄┄should be able to hold some 25000 segments and 350 ↓
┆19┆┆89┆┄┄entries. (20 Mbytes which is for instance 2400 ft/1600 ↓
┆19┆┆89┆┄┄bpi. For a description of the tape format, please cf. ↓
┆19┆┆89┆┄┄chapter 5.↲
↲
↲
┆b0┆┆a1┆4.1 Console Log during Generation↲
↲
┆84┆Immediately after start-up of the system generation the ↓
┆19┆┆89┆┄┄operator is prompted for a few informations (tapename ↓
┆19┆┆89┆┄┄etc.) and is requested to mount the tape (if not done ↓
┆19┆┆89┆┄┄already). During system generation a great deal of ↓
┆19┆┆89┆┄┄information is written on the system printer. This ↓
┆19┆┆89┆┄┄information comprises various lookups on files etc. and ↓
┆19┆┆89┆┄┄part of the printouts is found in appendix B.↲
↲
┆84┆The console log written during system generation is, of ↓
┆19┆┆89┆┄┄course, of great importance and an example of the log ↓
┆19┆┆89┆┄┄including prompts and operator supplied information is ↓
┆19┆┆89┆┄┄found in the following. The input supplied by the ↓
┆19┆┆89┆┄┄operator is printed in bold-faced types.↲
↲
┆b0┆ATT S↲
┆b0┆CALL 10 MTCN2401 READ CNSYSSAVE↲
READY↲
↲
FROM CNNETSYS↲
********** CENTERNET SYSTEM SAVE **********↲
TYPE TAPENAME: MTCN....↲
┆b0┆MTCN2401╞ ↲
TYPE INSTALLATION NAME:↲
┆b0┆RECAU↲
TYPE YES/NO FOR RC BACKUP TAPE↲
┆b0┆NO↲
TYPE DATE OF LAST RELEASE PLUS ONE↲
ON THE FORM YYMMDD↲
┆b0┆831110↲
*NEXTFILE T↲
*T=COPY CNNETINFO↲
CNNETINFO SEGM. 5 3474/172567↲
*NEXTFILE T↲
*I T2↲
*T=COPY LOADRECAU↲
LOADRECAU SEGM. 16 11848/796282↲
*O CNSAVEUD↲
↲
════════════════════════════════════════════════════════════════════════
↓
FROM S↲
MESSAGE CNNETSYS RELEASE MTCN2401↲
↲
FROM CNNETSYS↲
*MODE LIST.NO↲
********** CENTERNET SYSTEM SAVE **********↲
CHECKLOAD OF TAPE MTCN2401↲
↲
FOR INSTALLATION RECAU↲
↲
FROM S↲
MESSAGE CNNETSYS RELEASE MTCN2401↲
MESSAGE CNNETSYS RELEASE MTCN2401↲
↲
FROM CNNETSYS↲
CHECKLOAD OF CN SYSTEMTAPE OK↲
↲
FROM S↲
PAUSE CNNETSYS FINIS FP↲
↲
┆84┆┆b0┆NOTE:┆f0┆ The CENTERNET system tape is ┆a1┆not┆e1┆ automatically ↓
┆19┆┆89┆┆81┆┄checked for consistency. This has to be done manually.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆5. INSTALLATION OF THE CENTERNET SOFTWARE SYSTEM↲
↲
┆84┆The CENTERNET software system is delivered on a single ↓
┆19┆┆89┆┄┄magnetic tape, where the tape for the time being is ↓
┆19┆┆89┆┄┄organized as follows:↲
↲
file 1: release description↲
file 2: load job↲
file 3: CENTERNET software system↲
- source texts↲
- binary RC8000 modules↲
- binary model 1 files↲
file 4: binary model 2 files↲
↲
┆84┆where file 1 and 2 are in text format (copy/move), while ↓
┆19┆┆89┆┄┄the files 3 and 4 are in save/load format.↲
↲
┆84┆From this organization it is seen that a customer with ↓
┆19┆┆89┆┄┄RC3502 model 1 machines should ┆a1┆not┆e1┆ load file 4, while ↓
┆19┆┆89┆┄┄customers with RC3502 model 2 machines should load this ↓
┆19┆┆89┆┄┄file, thereby overwriting the binary model 1 files with ↓
┆19┆┆89┆┄┄the matching binary model 2 files (file 3 from the tape ↓
┆19┆┆89┆┄┄is loaded prior to file 4, of course). Luckily the load ↓
┆19┆┆89┆┄┄job prompts the operator (cf. section 5.2) for ↓
┆19┆┆89┆┄┄information about the model in question and then takes ↓
┆19┆┆89┆┄┄care of loading the correct files.↲
↲
┆84┆The contents and organization of the tape are candidates ↓
┆19┆┆89┆┄┄for changes and therefore no exact load description is ↓
┆19┆┆89┆┄┄given here - instead every tape delivery is accompanied ↓
┆19┆┆89┆┄┄by a precise load description including a listing of the ↓
┆19┆┆89┆┄┄actual contents of the tape.↲
↲
┆84┆In the succeeding subsections some remarks concerning ↓
┆19┆┆89┆┄┄resource requirements are given and the console log from ↓
┆19┆┆89┆┄┄a tape load is listed.↲
↲
┆84┆┆b0┆NOTE: ┆f0┆If the CENTERNET software system is to be loaded ↓
┆19┆┆89┆┆81┆┄for the very first time, some files not found on the ↓
┆19┆┆89┆┆81┆┄system tape are needed. (COMFILE, DESFILE etc.). If this ↓
┆19┆┆89┆┆81┆┄is the case, please contact RC Computer.↲
↲
┆b0┆↲
┆b0┆┆a1┆5.1 Resource Requirements during Load↲
↲
┆84┆The CENTERNET system tape contains some 25000 segments ↓
┆19┆┆89┆┄┄(approximately 20 Mbytes) and 350 entries, which ↓
┆19┆┆89┆┄┄therefore are the upper limits for the resource demands ↓
┆19┆┆89┆┄┄on the disc in question (which must be a single logical ↓
┆19┆┆89┆┄┄disc), but if the load files overwrite currently ↓
┆19┆┆89┆┄┄existing files the resource demands are of course ↓
┆19┆┆89┆┄┄correspondingly less.↲
↲
┆84┆The maximum core demand during load is 30000 hw.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆84┆To avoid unhappy interference it is strongly recommended ↓
┆19┆┆89┆┄┄that no other processes exist on RC8000 during load, and ↓
┆19┆┆89┆┄┄especially the NC (┆a1┆N┆e1┆etwork ┆a1┆C┆e1┆ontrol) system, the NPM, the ↓
┆19┆┆89┆┄┄SMM and the FTU should be closed down prior to CENTERNET ↓
┆19┆┆89┆┄┄system installation.↲
↲
↲
┆b0┆┆a1┆5.2 Console Log during Load↲
╞ ╞ ↲
┆84┆In the following a console log from a load of a ↓
┆19┆┆89┆┄┄CENTERNET system tape is listed. Note that the operator ↓
┆19┆┆89┆┄┄is requested to answer a few questions. The operator ↓
┆19┆┆89┆┄┄supplied information is printed in bold-face types.↲
↲
┆84┆Beside the console log also the system printer is used ↓
┆19┆┆89┆┄┄for printing various information telling which files are ↓
┆19┆┆89┆┄┄loaded, output from certain jobs executed during the ↓
┆19┆┆89┆┄┄installation and so on.↲
↲
┆b0┆ATT S↲
┆b0┆ALL ME RUN CALL 10 MTCN2401↲
READY↲
↲
TO ME↲
┆b0┆CNTAPE = SET MTO NTCN2401 0 2↲
┆b0┆I CNTAPE↲
****************************************↲
****************************************↲
********** **********↲
********** CENTERNET **********↲
********** LOADJOB GENERATION **********↲
********** **********↲
****************************************↲
****************************************↲
↲
CNTAPE = SET MTO MTCN2401 0 2 0 0 0 ; TEMP↲
; 0 16 0 -8388607 8388605↲
↲
NORMAL INSTALLATION ................ TYPE YES↲
TEST INSTALLATION (ONLY TAPE LOAD) . TYPE NO↲
┆b0┆YES↲
FROM S↲
PAUSE ME FINISSCNSYSINST↲
READY↲
↲
FROM CNTAPELOAD↲
*******************************************↲
********** **********↲
********** CENTERNET SYSTEM LOAD **********↲
********** **********↲
*******************************************↲
↲
TYPE DISC NAME FOR CN SYSTEM LOAD↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆DISC↲
RC3502 MODEL 2 SYSTEM? TYPE YES OR NO ↲
┆b0┆NO↲
DELETED ENTRIES: 0↲
↲
FROM S↲
MESSAGE CNTAPELOAD RELEASE MTCN2401↲
↲
FROM CNTAPELOAD↲
↲
FROM S↲
PAUSE CNTAPELOAD FINISSMAINFTU↲
READY↲
↲
FROM FTU9↲
FTUJOBS =SET 9 DISC D.820401.1556 0 0 0 0 ; ***↲
; 886 124 3 0 99999↲
↲
FROM S↲
PAUSE FTU9 FINISSCNDELETE↲
READY↲
↲
FROM CNDELETE↲
*******************************************↲
** **↲
** CENTERNET SYSTEM **↲
** READY FOR INITIALIZATION **↲
** **↲
*******************************************↲
↲
FROM S ↲
PAUSE CNDELETE FINIS FP↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆A. REFERENCES↲
↲
(1) RCSL No. 43-GL12224↲
┆a1┆CENTERNET, System Specifications↲
Per Høgh (ed.), December 1983.↲
↲
(2) PAXNET↲
┆a1┆Software Installation Guide↲
┆a1┆Reference Manaul↲
┆a1┆Revision 1.00↲
Claus Houlberg Hansen, March 1983↲
↲
(3) RCSL No. 43-GL12166↲
┆a1┆CENTERNET, CNADAM↲
┆a1┆Reference Manual, Ref. 2.00↲
Peter Holm, December 1983.↲
↲
(4) RCSL No. 43-GL12157↲
┆a1┆CENTERNET, Network Control↲
┆a1┆CNADAM LCP Specification Sheets, Ref. 2.0↲
Peter Holm, November 1983↲
↲
(5) RCSL No. 43-GL12086↲
┆a1┆┆84┆CENTERNET, X.28 Scroll Mode Terminal Module (X.28-↓
┆19┆┆8e┆┄┆84┆SMT) Reference Manual↲
Inger Marie Toft Hansen, September 1983.↲
↲
(6) RCSL No. 43-GL11426↲
┆a1┆CENTERNET, Host Port Module - HPM↲
┆a1┆Reference Manual↲
Karsten Kynde, October 1981.↲
↲
(7) RCSL No. 43-GL11739↲
┆a1┆CENTERNET, Session Control Module (SC)↲
┆a1┆Reference Manual↲
Viggo Lomborg, Peter Holm, November 1983.↲
↲
(8) RCSL No. 43-GL11958↲
┆a1┆RC3502 ECMA Transport Station↲
┆a1┆Reference Manual, Rev. 1.00↲
Per Holager, Jørgen Breinholt Frandsen, ↲
October 1983.↲
↲
(9) RCSL No. 43-GL11738↲
┆a1┆CENTERNET, DTE Module↲
┆a1┆Reference Manual↲
Per Høgh, July 1984.↲
↲
↓
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆B. LOOKUPS ON THE CENTERNET SOFTWARE SYSTEM↲
↲
┆84┆The following listings consists of lookups by means of ↓
┆19┆┆89┆┄┄the following utility programs:↲
↲
- LOOKUP↲
- LIB↲
- PLIBLOOKUP↲
↲
┆84┆According to the rules outlined in chapter 2, the ↓
┆19┆┆89┆┄┄listings are separated by explanatory head lines. It is ↓
┆19┆┆89┆┄┄seen that the listings show lookups on binary model 1 ↓
┆19┆┆89┆┄┄files as well as binary model 2 files, which is due to ↓
┆19┆┆89┆┄┄the fact that RC Computer maintains the software ↓
┆19┆┆89┆┄┄appropriate for both models of the RC3502 computer.↲
↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆C. CONFIGURATION FILES↲
↲
┆84┆Section C.1 lists the standard configuration file ↓
┆19┆┆89┆┄┄CRPARMENV, while C.2 lists a configuration file as it ↓
┆19┆┆89┆┄┄might look for a certain TC.↲
↲
↲
┆b0┆┆a1┆C.1 Standard Configuration File CRPARMENV↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆C.2 Example of a Special Configuration File↲
↲
┆84┆The example given here concerns a TC with 64 SMT ports ↓
┆19┆┆89┆┄┄and which from CRPARMENV furthermore is configured with ↓
┆19┆┆89┆┄┄a HI (┆a1┆H┆e1┆ost ┆a1┆I┆e1┆nterface) module (for communication with an ↓
┆19┆┆89┆┄┄RC8000 computer) equipped with 8 SMM ports, 2 FTP ports ↓
┆19┆┆89┆┄┄and a port for NC (┆a1┆N┆e1┆etwork ┆a1┆C┆e1┆ontrol) communication adding ↓
┆19┆┆89┆┄┄up to a total of 11 HI ports.↲
════════════════════════════════════════════════════════════════════════
↓
┆1a┆┆1a┆**********************↲
↲
FROM S ↲