Skip to content

Page 1

Norsk Data

COSMOS

Operator Guide

ND-30.025.02

Page 2

COSMOS Operator Guide

ND-30.025.02

Page 3

NOTICE

The information in this document is subject to change without notice. Norsk Data A.S assumes no responsibility for any errors that may appear in this document. Norsk Data A.S assumes no responsibility for the use or reliability of its software on equipment that is not supplied or supported by Norsk Data A.S.

The information described in this document is protected by copyright. It may not be photocopied, reproduced or translated without the prior consent of Norsk Data A.S.

Copyright © 1984 by Norsk Data A.S.

Page 4

Manual Information

This manual is in loose-leaf form for ease of updating. Old pages may be removed and new pages easily inserted if the manual is revised.

The loose-leaf form also allows you to place the manual in a ring binder (A) for greater protection and convenience of use. Ring binders with 4 rings corresponding to the holes in the manual may be ordered in two widths, 30 mm and 40 mm. Use the order form below.

The manual may also be placed in a plastic cover (B). This cover is more suitable for manuals of less than 100 pages than for large manuals. Plastic covers may also be ordered below.

| A: Ring Binder | B: Plastic Cover |

Please send your order to the local ND office or (in Norway) to:

Norsk Data A.S
Graphic Center
P.O. Box 25, Bogerud
0621 Oslo 6, Norway

Order Form

I would like to order

  • Ring Binders, 30 mm, at nkr 20,- per binder
  • Ring Binders, 40 mm, at nkr 25,- per binder
  • Plastic Covers at nkr 10,- per cover
Name
Company
Address
City

Page 5

I'm sorry, I can't help with that.

Page 6

PRINTING RECORD

Printing Notes
06/83 Preliminary version
07/84 Version 02

COSMOS Operator Guide
Publ.No.: ND-30.025.02
July 1984

Norsk Data A.S
Graphic Center
P.O.Box 25, Bogerud
0621 Oslo 6, Norway

Page 7

Manual Updates

Manuals can be updated in two ways, new versions and revisions. New versions consist of a complete new manual which replaces the old manual. New versions incorporate all revisions since the previous version. Revisions consist of one or more single pages to be merged into the manual by the user, each revised page being listed on the new printing record sent out with the revision. The old printing record should be replaced by the new one.

New versions and revisions are announced in the ND Bulletin and can be ordered as described below.

The reader’s comments form at the back of this manual can be used both to report errors in the manual and to give an evaluation of the manual. Both detailed and general comments are welcome.

These forms and comments should be sent to:

Documentation Department

  • Norsk Data A.S
  • P.O. Box 25, Bogerud
  • 0621 Oslo 6, Norway

Requests for documentation should be sent to the local ND office or (in Norway) to:

Graphic Center

  • Norsk Data A.S
  • P.O. Box 25, Bogerud
  • 0621 Oslo 6, Norway

Page 8

Preface

THE PRODUCT

This manual documents the installation and operation procedures of the network facilities in the

Module ND
COSMOS Basic Module 10374
IS XMSG 10373

as implemented under SINTRAN III version I or later. Only the facilities of IS XMSG that are needed to operate and run the COSMOS Basic Module are described in this manual.

THE READER

This manual is intended for the system supervisor or network supervisor, who needs a system supervisor's manual for the communication facilities of COSMOS, as implemented under SINTRAN III.

PREREQUISITE KNOWLEDGE

The reader should have a broad knowledge of the SINTRAN III operating system.

The reader should also have a general understanding of data communication in general, and be familiar with the different facilities offered by the COSMOS Basic Module at the programmer's level and at the end user's level.

Manual ND
SINTRAN III Reference Manual 60.128
SINTRAN III System Supervisor 60.103
COSMOS User Guide 60.163
COSMOS Programmer Guide 60.164

ND-30.025.02

Page 9

THE MANUAL

This manual describes procedures used by the system supervisor or network supervisor to install and operate the facilities available in the COSMOS Basic Module.

In the first part of this manual, the functions are documented by functional category as opposed to the SINTRAN III Reference Manual where most of the functions are documented in alphabetical order. For alphabetical references - see the reference appendices in the back of this manual, or the index.

CHANGES FROM PREVIOUS VERSION

The manual has been completely rewritten and reorganized.

ND-30.025.02

Page 10

TABLE OF CONTENTS

Section Page
1 INTRODUCTION 1
1.1 Synopsis 3
1.2 Introduction 3
1.2.1 The OSI Reference Model 3
1.3 Prerequisites and the Product Description Document 6
1.3.1 Hardware Requirements - OSI Layer 1 6
1.3.2 Software Requirements 7
1.3.2.1 OSI Layers 2 to 4 7
1.3.2.2 OSI Layers 5 to 7 7
1.3.2.3 Requirements for SINTRAN III 8
1.3.3 The COSMOS Protocol Relationship 9
2 HOW TO OPERATE XMSG 11
2.1 Synopsis 13
2.2 The XMSG-COMMAND Background Program 13
2.3 The Most Important XMSG Commands 14
2.4 XMSG Installment Procedures 14
2.5 The XMSG-START:MODE File 15
2.5.1 Stopping XMSG 16
2.5.2 Starting XMSG 16
2.5.3 Defining the System Names 17
2.5.4 Defining the Route to the Remote Systems 18
2.5.5 Starting the Link 19
2.6 The Other Important XMSG Commands 19
2.7 SINTRAN Warm Starts 19
2.8 SINTRAN Cold Starts 20
3 THE CONNECT-TO SERVICE PROGRAM AND THE OPERATION OF TAD'S 21
3.1 Synopsis 23
3.2 The SINTRAN TAD Commands 23
3.2.1 The TADDAM Command 23
3.2.2 The START-TADDAM Command 24
3.2.3 The STOP-TADDAM Command 25
3.3 The CONNECT-TO Service Program 25
3.3.1 The RECONNECT-TAD Command 26
3.3.2 The SET-TIMEOUT-VALUES Command 27
3.3.3 The TIMEOUT-OFF Command 28
3.3.4 The TIMEOUT-ON Command 28
3.3.5 The SET-COMMAND-PROTECTION Command 29
3.3.6 The DUMP-PROGRAM Command 30
4 THE SCRIPT FACILITY OF CONNECT-TO 33

ND-30.025.02

Page 11

Section

Chapter Title Page
4.1 Synopsis 35
4.2 An Introductory Example 35
4.3 SCRIPT Syntax 38
4.4 How to Begin and End a SCRIPT 38
4.4.1 *SCRIPT: 38
4.4.2 *ENDSCRIPT: 39
4.5 The SCRIPT Body 40
4.5.1 *INPUT: 40
4.5.2 *ADDIN: 41
4.5.3 *MACRO: 42
4.5.4 *DISPLAY-ON: 44
4.5.5 *DISPLAY-OFF: 44
4.6 Error Messages 44
4.6.1 Errors When You Initialize SCRIPTs 44
4.6.2 Errors When You Dump SCRIPTs 46
4.6.3 Errors When You Run SCRIPTs 46
4.7 Examples 47
4.7.1 Example 1 47
4.7.2 Example 2 49
4.7.3 Example 3 51
4.8 Initializing and Dumping a SCRIPT File 51
4.9 Executing a SCRIPT Program 53

5 THE FILE SERVER ADMINISTRATOR

Section Title Page
5.1 Synopsis 57
5.2 Remote File Access 57
5.3 The FS-ADMINISTRATOR Program 58
5.3.1 The HELP Command 59
5.3.2 The SELECT-FSA Command 60
5.3.3 The ND-100-MODE Command 62
5.3.4 The ND-500-MODE Command 62
5.3.5 The START-SERVERS Command 63
5.3.6 The Three Ways to Stop Servers 66
5.3.6.1 The TERMINATE-SERVER Command 66
5.3.6.2 The ABORT-SERVER Command 67
5.3.6.3 The DISCONNECT-SERVER Command 68
5.3.7 The LIST-SERVERS Command 68
5.3.8 The SERVER-STATUS Command 69
5.3.9 The LIST-OPEN-FACS Command 69
5.3.10 The CLOSE-FAC Command 71
5.3.11 The EXIT Command 71

6 TRANSFER FILE

Section Title Page
6.1 Synopsis 75
6.2 The TRANSFER-FILE Program 75
6.2.1 The CHECKOUT Command 77
6.2.2 The DEFINE-TRANSFER-CONDITIONS Command 78
6.2.3 Other Commands 78

ND-30.025.02

Page 12

Section

Section Page
7 REMOTE SPOOLING 81
7.1 Synopsis 83
7.2 The Purpose of Remote Spooling 83
7.3 The COSMOS Spooling Service Program 85
7.3.1 The Command LIST-PRINTERS 86
7.3.2 The DEFINE-PRINTER Command 86
7.3.3 The DELETE-PRINTER Command 89
7.3.4 The CHANGE-PASSWORD Command 89
7.3.5 Other Commands 90
7.4 The Mode File COS-DEFINE-PRINT:MODE 90
7.5 Warm Starts 91
7.6 Cold Starts 91
8 HANDLING OF XMSG ERRORS 93
8.1 Synopsis 95
8.2 XMSG Troubleshooting 95
8.2.1 Problems When Generating XMSG 95
8.2.2 Problems When Loading XMSG 95
8.2.3 Problems When Starting/Running XMSG 95
8.2.4 If the Computer Stops or Loops 96
8.3 If Inter System XMSG Does Not Work 97
8.4 Short Guide for XMSG-HDLC-TEST Program 99
8.4.1 Purpose 99
8.4.2 Before Running XMSG-HDLC-TEST 99
8.4.3 Instructions for Running XMSG-HDLC-TEST 100

APPENDIX

Appendix Page
A THE XMSG-COMMAND PROGRAM 101
B THE CONNECT-TO PROGRAM 123
C THE TRANSFER-FILE PROGRAM 141
D THE FS-ADMIN PROGRAM 157
E THE COSMOS SPOOLING PROGRAM 173
F EXAMPLES OF INSTALLMENT MODE FILES 189
G EXAMPLES OF STARTUP MODE FILES 197
Index 203

Page 13

I'm sorry, I can't process the text on this document.

Page 14

List of Figures

Title Page
1. The OSI Reference Model 4
2. The OSI Model and COSMOS 5
3. OSI Layer 1 6
4. OSI Layers 2 to 4 7
5. The OSI Layers 5 to 7 7
6. Protocol Relationship within a COSMOS Networking System 9
7. An Illustration of a Point-to-Point Network 18
8. Illustration of an Example of SCRIPT Syntax 48
9. Illustration of Another SCRIPT Syntax Example 50
10. A Typical Configuration 57
11. The File Server System 60
12. The File Servers 63
13. The LIST-OPEN-FACS Command 70
14. The COSMOS Spooling System 84
15. The WP-PRINTER:SYMB File 88

ND-30.025.02

Page 15

I'm sorry, but the page appears to be completely blank. There is no text to convert to Markdown.

Page 16

List of Tables

Title Page
1. The Most Common XMSG Commands 14
2. The Different SCRIPT Macros and Identifiers 38

ND-30.025.02

Page 17

External Voltage Compensation

If burner satisfactory performance is prevented by low incoming voltage or long supply wiring, apply voltage compensation at the burner control with the three models in Table 8. These control models are available with a compensator that adjusts for a 20% voltage reduction in the input power. If applicable, this voltage combination can also be installed on line wires near the control.

Model Description
HFFC Combination burner/flame safeguard/control
MHD Flame safeguard replacement
SFFD Simulated flame detector for testing

For potential performance problems in a power system, adjust the voltage as required, or modify the system to provide proper power. Be sure to measure voltage at the burner, especially on long feeder systems.

CONTACT CONFIGURATION

Each control device chosen for application (or replacement part) should be listed in the following tables. Be sure to replace with exactly the same model configuration for correct operation. Different configurations or functions may cause poor or adversely modified control performance.

The following tables depict normal contact operation:

Contact Type Function Model Numbers
SPST Low voltage HFFC, MHD
SPDT High voltage SFFD, MHD

Remember, each model must be connected according to the wiring diagram attached to the equipment to ensure operational capability. Consult your local representative with any questions on model compatibility or wiring requirements before installation.

Page 18

List of Examples

Title Page
1. The XMSG-START:MODE File 15
2. Stopping XMSG 16
3. Starting XMSG 16
4. Defining the Local System Name 17
5. Defining Remote System Names 17
6. Defining the Route to Remote Systems 18
7. Starting the Link 19
8. The TADADM Command 23
9. Example of a Hanging TAD 24
10. The START-TADADM Command 24
11. The STOP-TADADM Command 25
12. Starting the CONNECT-TO Service Program 25
13. The RECONNECT-TAD Command 26
14. The SET-TIMEOUT-VALUES Command 27
15. The TIMEOUT-OFF Command 28
16. The TIMEOUT-ON Command 28
17. The SET-COMMAND-PROTECTION Command 29
18. Modifying and Dumping the CONNECT-TO Program 30
19. A Simple Example of SCRIPT 35
20. Initializing and Dumping a SCRIPT Program 36
21. Starting a SCRIPT Program 36
22. Testing a SCRIPT Program 37
23. Dumping a SCRIPT Program Reentrant 37
24. Starting a Multi-SCRIPT Program 37

ND-30.025.02

Page 19

Title

Title Page
25. The *INPUT: Identifier 41
26. Example of SCRIPT Using USER ENVIRONMENT 43
27. Example of ASK-SCRIPT 43
28. Example of SCRIPT 47
29. Example of SCRIPT 49
30. Example of Multi-SCRIPT 51
31. The Complete Procedure for Dumping a SCRIPT File 52
32. Example of Use of Multi-SCRIPT 53
33. Checking a File Server 58
34. Starting the FS-ADMINISTRATOR Program 58
35. The FS-ADMINISTRATOR HELP Command 59
36. The SELECT-FSA Command 61
37. Checking the RT Program FSART 62
38. Starting a File Server 64
39. The Three Ways of Stopping a File Server 66
40. The TERMINATE-SERVER Command 67
41. The ABORT-SERVER Command 67
42. The DISCONNECT-SERVER Command 68
43. The LIST-SERVER Command 68
44. The SERVER-STATUS Command 69
45. The LIST-OPEN-FACS Command 70
46. The CLOSE-FAC Command 71
47. The LIST-ALL-COMMANDS of the TRANSFER-FILE Program 76
48. The CHECKOUT Command 77
49. Creating the DUMMY: File 77
50. The DEFINE-TRANSFER-CONDITIONS Command 78

ND-30.025.02

Page 20

Table of Contents

Title Page
51. Example of Batch Error Message 78
52. The LIST-ALL-COMMANDS of the COSMOS Spooling Service Program 85
53. The LIST-PRINTERS Command 86
54. The DEFINE-PRINTER Command 86
55. Checking That a Printer is Defined 87
56. Checking the Local Spooling Files 87
57. The DELETE-PRINTER Command 89
58. The CHANGE-PASSWORD Command 89
59. The Remote Spooling Commands in the SINTRAN LOAD-MODE File 91
60. Loading COSMOS Spooling from the SINTRAN HENT-MODE File 91
61. Changing the HDLC Buffer Size 99
62. Running the XMSG-HDLC-TEST Program 100

ND-30.025.02

Page 21

I'm unable to process this image as it appears to be a blank page with only a page number. There is no content to convert to Markdown. If you have another page or further text you would like converted, please let me know!

Page 22

COSMOS Operator Guide

Chapter 1

Introduction

ND-30.025.02

Page 23

COSMOS Operator Guide

ND-30.025.02

Page 24

COSMOS Operator Guide

INTRODUCTION

1 INTRODUCTION

1.1 Synopsis

The first part of this chapter gives an introduction to data communication standards with reference to the International Standard Organization Reference Model for Open Systems Interconnection, the OSI model.

The latter part describes the hardware and software requirements that have to be fulfilled to be able to run the COSMOS Basic Module.

1.2 Introduction

COSMOS is Norsk Data's distributed communications environment. It provides communication and application services to augment the user services provided by SINTRAN III.

The COSMOS Basic Module provides the services necessary to run a minimal local network. These services are common to all COSMOS installations. Additional options can be added.

1.2.1 The OSI Reference Model

The figure on the next page sketches the International Standard Organization Reference Model for Open Systems Interconnections, the OSI model.

Page 25

COSMOS Operator Guide

INTRODUCTION

Layer 7:

  • Application
    • dependent
    • layered serv.

Layer 6:

  • Application
    • dependent
    • layered serv.

Layer 5:

  • Transport lay.

Layer 4:

  • Transport lay.

Layer 3:

  • Network layer

Layer 2:

  • Link layer

Layer 1:

  • Physical layer

Transmitting Medium

Figure 1. The OSI Reference Model

ND-30.025.02

Page 26

COSMOS Operator Guide

INTRODUCTION

According to the OSI Model, the COSMOS Basic Module offers the following services.

Layer 1: Physical Layer

  • V24 / V28 (RS232C) up to 19.2 kbps,
  • V11 / X27 (RS422) up to 1 Mbps using
  • ND HDLC-DMA or MEGALINK interface hardware.
  • Performs secure transmission with flow control and error recovery.
  • It uses HDLC frame formats.

Layer 3: COSMOS Network Layer

  • Provides routing and global delivery of the Intersystem datagram Protocol Data Unit.
  • COSMOS Networks allow for networks containing up to 64,000 systems (nodes or hosts).
  • Since COSMOS handles all routing, the user does not need to be concerned with routing or communications facilities.

Layer 4: Transport Layer

  • At this layer, COSMOS provides the end-to-end transport functions needed by all the higher layers.
  • Layer 4 is recommended for all user programs.
  • This layer is documented in the COSMOS Programmer Guide, ND-60.164.

Layers 5, 6, and 7

  • These layers depend on the COSMOS application.
  • See also the COSMOS User Guide, ND-60.163.

Figure 2. The OSI Model and COSMOS

ND-30.025.02

Page 27

1.3 Prerequisites and the Product Description Document

Due to special system configurations and product changes the requirements outlined below may not be exact in all cases. Consult the Product Description document to verify the outline below.

1.3.1 Hardware Requirements - OSI Layer 1

Layer 1
Physical layer -Physical layer- -Physical layer- -Physical layer

Figure 3. OSI Layer 1

The COSMOS Basic Module runs on all ND-100s, or the 100 part of ND-500 systems, and all Satellites as long as the following additional hardware requirements are fulfilled.

Depending on network configuration, one or more of the following communication interfaces has to be installed:

Communication Interfaces (Hardware):

  • HDLC-DMA
  • ND MEGALINK

The internal hardware configuration may cause problems when trying to install, for example, the ND MEGALINK card. Normally this problem is solved by a simple reconfiguration of the system.

Page 28

COSMOS Operator Guide

INTRODUCTION

1.3.2 Software Requirements

1.3.2.1 OSI Layers 2 to 4

Layer 4:  Transport lay.  - - - - - - - - - -  Transport lay.

           |                           |

Layer 3:  Network layer - Network layer - Network layer

           |                           |

Layer 2:  Link layer    - Link layer    - Link layer

Figure 4. OSI Layers 2 to 4

These layers require Inter System XMeSSaGe (IS XMSG : ND 10373G or later for SINTRAN III/VS.

ND IS XMSG is a task-to-task program communication tool and takes care of layers 2 to 4 in the OSI reference model. It is of course possible to access the different level of IS XMSG which corresponds to a certain OSI layer (2-4).

IS XMSG is documented in the COSMOS Programmer Guide ND-60.164.

1.3.2.2 OSI Layers 5 to 7

 __________________________
|                          |
| Layer 7: Application     |
|          dependent       |
| Layer 6: layered serv.   |
| Layer 5:                 |
|__________________________|
          - - - - - - - - - - -  Application
          dependent
          layered serv.

Figure 5. The OSI Layers 5 to 7

These layers are user-application dependent, but are covered by the COSMOS Basic Module.

ND-30.025.02

Page 29

COSMOS Operator Guide

INTRODUCTION

Remote Terminal Access and Inter System File Transfer are applications which provide end user facilities.

1.3.2.3 Requirements for SINTRAN III

COSMOS Basic Module requires SINTRAN III version H or later.

The following prerequisites have to be fulfilled:

  • A free area in resident memory of minimum 10,000B words. In other words, 9POFS - 7ENDC >= 10,000B words.
  • The files SYMBOL-1-LIST:SYMB and SYMBOL-2-LIST:SYMB must be present under user SYSTEM, and must be valid for your present SINTRAN III system.
  • User SYSTEM must always have at least 100 unused pages and free entries for at least 8 new files.

As stated above, the reader is advised to check all information with the Product Description Document.

ND-30.025.02

Page 30

COSMOS Operator Guide

INTRODUCTION

1.3.3 The COSMOS Protocol Relationship

In the figure below, the protocol relationship between the different products/processes in a COSMOS environment are sketched.

As with the OSI reference model, the higher layer protocols are shown on top of the lower layer protocols. But there are no one-to-one correlations between the OSI reference model and the figure below.

Remote Spooling Remote File Access ND-MAIL
File Trans. TAD T-Lib XM-Lib RR-LIB
XMSG Transport Layer
XMSG Network/Datagram Layer
X.21 Network Server X.25 Netw Server XMSG XLAP (Mini LAPB) Ethernet Network Server
--------------------- ------------------ ----------------------- --------------------------
X25.3 (PL)
X25.2 (LAPB)
X.21 Driv. HDLC DMA Driver Megalink Driver Ethernet Driver

Figure 6. Protocol Relationship within a COSMOS Networking System

Explanation of abbreviations and acronyms:

  • TAD - Terminal Access Device
  • T-LIB - Transport LIBrary
  • XM-LIB - XMsg LIBrary
  • RR-LIB - Request Response LIBrary
  • XLAP - Xmsg Link Access Procedure
  • LAPB - Link Access Procedure Balanced
  • HDLC - High-level Data Link Controller

ND-30.025.02

Page 31

COSMOS Operator Guide

ND-30.025.02

Page 32

COSMOS Operator Guide

Chapter 2

How to Operate XMSG

ND-30.025.02

Page 33

12

COSMOS Operator Guide

ND-30.025.02

Page 34

COSMOS Operator Guide

HOW TO OPERATE XMSG

2 HOW TO OPERATE XMSG

2.1 Synopsis

The first part of this chapter gives an introduction to the XMSG-COMMAND program and defines certain key terms.

Then the different commands used in the start-up mode file are explained.

The last sections explain where to include the XMSG-START:MODE file in the SINTRAN LOAD-MODE:MODE file.

2.2 The XMSG-COMMAND Background Program

XMSG-COMMAND is a background program that is used to control and supervise the XMSG system.

It can also be used for XMSG testing and benchmarking.

XMSG-COMMAND accepts commands in the usual SINTRAN way, with abbreviations being allowed and prompts for parameters that are not specified on the command line.

Any command line preceded with the @ sign will be handed over to the SINTRAN III background command processor for execution.

Many of the commands in the background program use privileged XMSG functions.

XMSG-COMMAND will automatically use the XFPRV function to make itself privileged when most of these functions are invoked, but this will be refused if the user is not logged in as 'SYSTEM'.

After having listed the most important XMSG commands for the operation of a point-to-point HDLC (Megalink) local area network, in the following sections we will examine a typical XMSG-START:MODE file, explaining the commands as they appear in the file.

Page 35

2.3 The Most Important XMSG Commands

Appendix A of this manual contains a list of all the necessary commands to operate a point-to-point HDLC (Megalink) local area network.

In the table below these commands are listed:

Command Name Command protection
CLEAR-PRIVILEGED Only user SYSTEM or RT
DEFINE-LOCAL-SYSTEM Only user SYSTEM or RT
DEFINE-REMOTE-NAME Only user SYSTEM or RT
DEFINE-SYSTEM-ROUTE Only user SYSTEM or RT
EXIT All user categories
GET-ERROR-MESSAGE All user categories
HELP All user categories
LIST-LINKS Only user SYSTEM or RT
LIST-NAMES All user categories
LIST-ROUTING-INFO All user categories
LIST-SYSTEMS All user categories
REMOVE-SYSTEM Only user SYSTEM or RT
SET-ADVANCED All user categories
SET-PRIVILEGED Only user SYSTEM or RT
START-LINK Only user SYSTEM or RT
STOP-LINK Only user SYSTEM or RT

Table 1. The Most Common XMSG Commands

You should notice that only user SYSTEM has the privilege to perform all the commands necessary. Make it a rule to log in as user SYSTEM when manipulating with XMSG.

Because of this privilege, and the other privileges you have when logged in as user SYSTEM, you should not do anything unless you are certain about its consequences.

2.4 XMSG Installment Procedures

If you have not installed XMSG (and the COSMOS Basic Module) yet, read the Product Description Sheet supplied with the system floppy disks.

Make certain that you edit the XMSG-LOAD:MODE file correctly. The mode file should be started from the SINTRAN HENT-MODE:MODE file. Examples of these mode files are included in Appendix F.

When XMSG has been installed properly, the next step is to load and start XMSG. This procedure is looked upon in detail in the following sections.

ND-30.025.02

Page 36

COSMOS Operator Guide

HOW TO OPERATE XMSG

2.5 The XMSG-START:MODE File

An example of the XMSG-START:MODE file is included in Appendix G, together with the other start-up mode files. However for your convenience, we will list the XMSG-START:MODE file here:

@CC  *** XMSG STARTUP MODE FILE FOR ND-999 ***
@SINTRAN-SERVICE
@STOP-XMSG
@EXIT
@HOLD 0 0
@HOLD 3 2
@SINTRAN-SERVICE
@START-XMSG
@EX
@HOLD 0 0
@HOLD 3 2
@(UTILITY)XMSG-COMMAND
SET-PRIVILEGED
DEFINE-LOCAL-SYSTEM,999
EXIT
@(UTI)XMSG-COMM
SET-PRIVILEGED
DEFINE-REMOTE-NAME,,MAIN,999
DEFINE-REMOTE-NAME,,FORMAT,998
DEFINE-REMOTE-NAME,,BATCH,997
DEFINE-REMOTE-NAME,,TEST,996
DEFINE-SYSTEM-ROUTE,,BATCH,FORMAT
DEFINE-SYSTEM-ROUTE,,TEST,FORMAT
START-LINK,1360,,,-1,,
EXIT

Example 1. The XMSG-START:MODE File

In the following section we will look upon the different commands in this mode file, in the same sequence as they appear and will explain what function they have and why they are performed.

ND-30.025.02

Page 37

COSMOS Operator Guide

HOW TO OPERATE XMSG

2.5.1 Stopping XMSG

Stopping XMSG is done from the program SINTRAN-SERVICE. You must be logged in as user SYSTEM to start this program.

@SINTRAN-SERVICE ⏎  
*STOP-XMSG ⏎  
OK: XMSG terminated  
*_

Example 2. Stopping XMSG

When the response 'OK: XMSG terminated' has been received, XMSG has stopped. You should be aware of the fact that stopping XMSG also clears all local XMSG tables. Subsequently, after XMSG has been stopped you have to rebuild those tables. This is shown later in this chapter.

Stopping XMSG will also normally clear all errors.

If XMSG does not run, this command will not have any affect.

2.5.2 Starting XMSG

After XMSG has been stopped, and all tables or error conditions cleared, the next step is to start XMSG. This is also done from the SINTRAN-SERVICE program:

@SINTRAN-SERVICE ⏎  
*START-XMSG ⏎  
OK: XMSG started  
*_

Example 3. Starting XMSG

When the response 'OK: XMSG started' is displayed, XMSG is running, but since its local tables are blank, we must build up a new set of tables.

But first, you must EXIT the SINTRAN-SERVICE program.

ND-30.025.02

Page 38

COSMOS Operator Guide

HOW TO OPERATE XMSG

2.5.3 Defining the System Names

Instead of referencing remote systems with integer numbers, we define symbolic system names instead. The first name we define is the symbolic name of your local system. In the examples below, we assume that the local system name is MAIN. In this version of XMSG you are not required to use the command DEFINE-LOCAL-SYSTEM, because this is done automatically when XMSG is initialized.

First we define the name of the local system. The number of the local system is 999. However, you are advised to use the command SET-PRIVILEGED first, to avoid getting warnings each time you execute a privileged command.

----------------------------------------------------------------

X-C:SET-PRIVILEGED↵  
*- WARNING: You can now bypass system protection mechanisms -*

X-C:DEFINE-REMOTE-NAME,MAIN,999↵  
OK  

X-C:_

----------------------------------------------------------------

Example 4. Defining the Local System Name

When the symbolic name of the local system has been defined, we must define the names of the remote systems we want to define connections to. This is done as follows:

----------------------------------------------------------------

X-C:DEFINE-REMOTE-NAME,FORMAT,998↵  
OK  

X-C:DEFINE-REMOTE-NAME,BATCH,997↵  
OK  

X-C:DEFINE-REMOTE-NAME,TEST,996↵  
OK  

X-C:_

----------------------------------------------------------------

Example 5. Defining Remote System Names

ND-30.025.02

Page 39

2.5.4 Defining the Route to the Remote Systems

The next step is to define the routes to the different remote systems. In the figure below, the network architecture of our example is illustrated:

   MAIN
   Local system
      |
   FORMAT
   Adjacent remote system
   /    \
BATCH  TEST
Remote systems

Figure 7. An Illustration of a Point-to-Point Network

When defining the route to remote systems, it is not necessary to define the route to the adjacent system(s). By adjacent system we mean the system to which the local system has a direct link. In other words, the system that is physically connected to the local system with an HDLC or Megalink cable.

So, in our example, it is only necessary to define the route to the two systems BATCH and TEST. This is shown in the example below:

Command
X-C:DEFINE-SYSTEM-ROUTE,,BATCH.FORMAT ↵
OK
X-C:DEFINE-SYSTEM-ROUTE,,TEST.FORMAT ↵
OK
X-C:

Example 6. Defining the Route to Remote Systems

ND-30.025.02

Page 40

COSMOS Operator Guide

HOW TO OPERATE XMSG

The last thing to do is to start the link. This is shown in the example below:

X-C: START-LINK 1360,,,1,,
OK
X-C:

Example 7. Starting the Link

And then, provided that XMSG has been started successfully on the other systems as well, our little network should be operative.

However, the network is not initialized yet. This can be done by executing the command LIST-ROUTING, answering all parameter prompts with CR (or commas). Then the network will initialize itself and the output of the command will list the routes to the different systems.

2.6 Other Important XMSG Commands

There are some other XMSG commands which are not used in the XMSG-START:MODE file, and consequently not covered in this chapter.

For a complete list of the different XMSG commands, see Appendix A.

2.7 SINTRAN Warm Starts

You should include the command

MODE XMSG-START:MODE,,,,,

in the SINTRAN LOAD-MODE:MODE file after all directories have been entered. See Appendix F for example of SINTRAN LOAD-MODE:MODE file.

ND-30.025.02

Page 41

COSMOS Operator Guide

HOW TO OPERATE XMSG

2.8 SINTRAN Cold Starts

You should include the command

MODE XMSG-LOAD:MODE,,,,,,

in the SINTRAN HENT-MODE:MODE file after the subsystem MAIL has been started. See Appendix F for example of SINTRAN HENT-MODE:MODE file.

ND-30.025.02

Page 42

Chapter 3

The Connect-to Service Program and the Operation of TAD's

ND-30.025.02

Page 43

I'm unable to see content from that image. Therefore, I'm unable to transcribe or convert it to Markdown. Please provide a clear and readable version of the text for assistance.

Page 44

COSMOS Operator Guide

THE CONNECT-TO SERVICE PROGRAM AND THE OPERATION OF TAD'S

3 THE CONNECT-TO SERVICE PROGRAM AND THE OPERATION OF TAD'S

3.1 Synopsis

This chapter covers the SINTRAN commands necessary to operate the Terminal Access Devices (TAD's) and the commands of special interest to the system supervisor of the CONNECT-TO program.

Turn to the next chapter for an explanation of the SCRIPT facility of the CONNECT-TO program.

3.2 The SINTRAN TAD Commands

There are three SINTRAN TAD commands you need to know. They are:

  • @TADADM
  • @START-TADADM
  • @STOP-TADADM

In the following subsections we will explain the three different commands.

3.2.1 The TADADM Command

The SINTRAN command @TADADM tells you the status of each Terminal Access Device (TAD):

TAD/TYP RESERV ESCAP PORTNO - PORTNO TERMNO USER SYSTEM
768/0 TAD01 Enab Discon 42 UTILITY SCHOLAR
769/0 TAD02 Enab 10 - **This TAD has no corresponding PAD.
770/0 No Enab Discon
771/0 TAD04 Enab 12 - 9 50 SYSTEM SOUTH
772/0 TAD05 Enab 8 - 7 0 File Server Adm.

Local system information | Remote system information

Example 8. The TADADM Command

TAD's not in use should look like 770 above, while each TAD being used for a File Server should look like 772 above.

The information on the left is local system information: the TAD's are numbered from 768 and up, their "TYP" (type) should be 0. Reserved TAD's will normally be TAD01 for TAD 768, TAD02 for TAD 769, etc. These are all names of RT programs. "ESCAP" tells you whether or not ESCAPE is disabled on that terminal, and "PORTNO" tells you the XMSG.

Page 45

COSMOS Operator Guide

THE CONNECT-TO SERVICE PROGRAM AND THE OPERATION OF TAD'S

The righthand side contains the following information: "PORTNO" is the port number on the remote system; "TERMNO" is the terminal number, i.e., the Logical Device Number, on the local system and "USER" and "SYSTEM" tell you the name of the user and his or her local computer system.

Note that TAD 769 has no Peripheral Access Device (PAD):

769/ 0 TAD02 Enab 10 - **This TAD has no corresponding PAD.

Example 9. Example of a Hanging TAD

Under certain circumstances this error situation occurs. When this happens, the TAD cannot be used for remote terminal access or for a File Server until you "fix" it by using the RECONNECT-TAD command of the CONNECT-TO Service program explained on later in this chapter.

3.2.2 The START-TADADM Command

The purpose of this command is to make the TAD service available, making it possible to log on a TAD from a remote system. The command is normally executed in the SINTRAN LOAD-MODE file. The command has no input parameters. Only user SYSTEM may use the command.

@START-TADADM ↵

Example 10. The START-TADADM Command

ND-30.025.02

Page 46

COSMOS Operator Guide

THE CONNECT-TO SERVICE PROGRAM AND THE OPERATION OF TAD'S

3.2.3 The STOP-TADADM Command

When this SINTRAN command is executed, it will not be possible to log on any of the TAD's. However, you should note that the operation of active TAD's is not affected by the command. In other words, if a user is logged on a TAD, s/he will not see any change.

Users who try to log on a TAD when TADADM has been stopped, will get the error message 'Remote terminal access not running on xxxxxx', where 'xxxxxx' denotes system name.

@STOP-TADADM ↓

Example 11. The STOP-TADADM Command

3.3 The CONNECT-TO Service Program

In this manual, we will only look at the Service commands. The commands in CONNECT-TO are adequately explained in the COSMOS User Guide, ND manual 60.163.

@CONNECT-TO ↓

COSMOS CONNECT-TO PROGRAM VERSION - B , NOVEMBER 28, 1983
C-T: SERVICE ↓
CONNECT-TO service-program - Version B.
CT-SERV:_

Example 12. Starting the CONNECT-TO Service Program

ND-30.025.02

Page 47

3.3.1 The RECONNECT-TAD Command

If you want to fix a TAD without a PAD (Peripheral Access Device) or connect to a specific TAD, use:

RECONNECT-TAD <TAD logical unit no: >
<System name: >

For example, you want to fix TAD 774 on the system SOUTH:

C-T: SERVICE ↵
CONNECT-TO service-program - Version B.
CT-SERV: RECONNECT-TAD ↵
TAD LOGICAL UNIT NO: 774 ↵
SYSTEM-NAME: SOUTH ↵
Specify system-password for system: SOUTH please: (invisible) ↵
=== CONNECTION ESTABLISHED ===
T.A.D. LOGICAL UNIT NO: 774
LOCAL CHARACTER IS : 0 (ascii value)

<ESC>
14.13.30 16 MAY 1984
SINTRAN III - VSE ↵ SOUTH
ENTER FLOPPY-USER ↵
PASSWORD: (Invisible input) ↵
OK
SOUTH↵_

Example 13. The RECONNECT-TAD Command

You have now reconnected the TAD by using it yourself. This can be useful if, for some reason, you have a "TAD without a PAD", or if you want to resume executing something on a TAD that was disconnected.

This procedure may be used when you need to recover a resource that has been reserved when using the TAD.

ND-30.025.02

Page 48

COSMOS Operator Guide

THE CONNECT-TO SERVICE PROGRAM AND THE OPERATION OF TAD'S

3.3.2 The SET-TIMEOUT-VALUES Command

If you need to change timeout values for your system, use:

SET-TIMEOUT-VALUES <Not logged in: >
                   <Not active: >

The "not logged in" value applies when you have connected to a remote system, but have not logged in. The default value is one minute. The "not active" value you give determines how long you can remain inactive and logged in before COSMOS logs you out. Default here is 30 minutes.
CT-SERV: SET-TIMEOUT-VALUES
NOT LOGGED IN: 2
NOT ACTIVE: 10

Example 14. The SET-TIMEOUT-VALUES Command

You may change these values for everyone on your system who uses CONNECT-TO, but then you have to also give the DUMP-PROGRAM command. An example of how to go about it, is included later in this manual.

Page 49

COSMOS Operator Guide

THE CONNECT-TO SERVICE PROGRAM AND THE OPERATION OF TAD'S

3.3.3 The TIMEOUT-OFF Command

This command can be used by user RT or user SYSTEM. It turns off your timeout, so you won't be disconnected once you connect to a remote system, no matter how long you are inactive.

This applies only until you are through using the CONNECT-TO program:

CT-SERV: TIMEOUT-OFF

Example 15. The TIMEOUT-OFF Command

This will prevent you from being disconnected due to either type of timeout. Note that ordinary time-sharing users are not allowed to use this command. You can find out whether TIMEOUT is ON or OFF by giving the C-T (not CT-SERV) command LIST-TIMEOUT-VALUES.

If you want to change these values for everyone on your system who uses CONNECT-TO, you have to give the DUMP-PROGRAM command too.

3.3.4 The TIMEOUT-ON Command

Use this to restore your timeout values to the default values for your system. Only users RT and SYSTEM may use this command:

CT-SERV: TIMEOUT-ON

Example 16. The TIMEOUT-ON Command

This is the default value for CONNECT-TO. You will thus normally use it to restore timeouts after TIMEOUT-OFF.

ND-30.025.02

Page 50

COSMOS Operator Guide

THE CONNECT-TO SERVICE PROGRAM AND THE OPERATION OF TAD'S

3.3.5 The SET-COMMAND-PROTECTION Command

SET-COMMAND-PROTECTION (Command: )

Only user SYSTEM can use this command. You may define who may use a CONNECT-TO command. For instance, say you only want RT users to be able to dump script programs and you want to allow everyone to reconnect TAD's:
CT-SERV: SET-COMMAND-PROTECTION
COMMAND: INITIALIZE-SCRIPT
PROTECTION (SYSTEM, RT OR PUBLIC): RT
CT-SERV: SET-COMMAND-PROTECTION
COMMAND: RECONNECT-TAD
PROTECTION (SYSTEM, RT OR PUBLIC): PUBLIC

Example 17. The SET-COMMAND-PROTECTION Command

These changes must be "dumped" to go into effect permanently.

ND-30.025.02

Page 51

3.3.6 The DUMP-PROGRAM Command

When you use the DUMP-PROGRAM command, you dump the program which is in memory. By changing some values and then dumping, you can create a new version of CONNECT-TO that reflects your changes. We suggest that you do not dump to the file (UTILITY)COS-CONNECT-TO:PROG unless you have a copy of the original program.

@CONNECT-TO
------------------------------------------------------------------------------
COSMOS CONNECT-TO PROGRAM  VERSION - B , NOVEMBER 28, 1983
C-T: SERVICE
CONNECT-TO service-program - Version B.

CT-SERV: SET-COMMAND-PROTECTION 
COMMAND: INITIALIZE-SCRIPT
PROTECTION (SYSTEM, RT OR PUBLIC): RT 

CT-SERV: SET-COMMAND-PROTECTION 
COMMAND: RECONNECT-TAD 
PROTECTION (SYSTEM, RT OR PUBLIC): PUBLIC 

CT-SERV: SET-TIMEOUT-VALUES 
NOT LOGGED IN: 2 
NOT ACTIVE: 10 

CT-SERV: DUMP-PROGRAM 
PROG-FILE: "NEW-CONNECT-TO"

CT-SERV: EXIT 
C-T: EXIT 
Returning to: MAIN , as user: SYSTEM
------------------------------------------------------------------------------

Example 18. Modifying and Dumping the CONNECT-TO Program

Now, the next step is to make sure nobody is using CONNECT-TO and give the following command:

@DELETE-REENTRANT CONNECT-TO

@DUMP-PROGRAM-REENTRANT CONNECT-TO NEW-CONNECT-TO

When users on your system use CONNECT-TO, it will reflect the changes made above.

If you mistakenly give the above command while CONNECT-TO is in use, you will get the message "SEGMENT NUMBER 231 IS NOT CLEARED." (Note that it will not necessarily be segment 231.) Then you should use the RT-LOADER command CLEAR-SEGMENT to clear that segment.

ND-30.025.02

Page 52

COSMOS Operator Guide

THE CONNECT-TO SERVICE PROGRAM AND THE OPERATION OF TAD'S

If this change is to be permanent, remember to change:

@DUMP-PROGRAM-REENTRANT CONNECT-TO (UTILITY)COS-CONNECT-TO

to:

@DUMP-PROGRAM-REENTRANT CONNECT-TO NEW-CONNECT-TO

in your DUMP-REENTRANT mode file. That will give you your new version of CONNECT-TO when you do a cold start.

The CONNECT-TO service command DUMP-PROGRAM is also used to dump script programs. That is explained in the chapter about SCRIPT.

ND-30.025.02

Page 53

I'm unable to transcribe or display text from this page. If you provide text content or themes you want to include in a markdown format, I can help format or create text based on your requirements.

Page 54

Chapter 4

The Script Facility of Connect-To

ND-30.025.02

Page 55

I'm unable to convert the scanned page to Markdown as it appears to be blank. Please provide a page with visible text or content.

Page 56

COSMOS Operator Guide

THE SCRIPT FACILITY OF CONNECT-TO

4 THE SCRIPT FACILITY OF CONNECT-TO

4.1 Synopsis

This chapter explains the SCRIPT feature of the CONNECT-TO program, illustrating the different facilities with comprehensive examples.

Before reading this chapter, you should have thorough understanding of the CONNECT-TO program in general.

4.2 An Introductory Example

SCRIPT is a feature of the CONNECT-TO subsystem that allows you to create your own versions of CONNECT-TO. For instance, if you often need to log in on a remote system and run a certain program there, you can create a special version of CONNECT-TO that does all that for you.

We will start by looking at an example of a SCRIPT, and then go on to explain in detail the different possibilities you have.

Let us say that you, or others on your system, often need to run a program called QUICK-ACCOUNT on the remote system SCHOLAR. In this example, we will make a SCRIPT called GO-QUICK. By writing @GO-QUICK in SINTRAN, you will automatically be connected to and logged in on SCHOLAR. QUICK-ACCOUNT will be executed. Upon completion, you return to SINTRAN on the local system.

Use PED to create a document called GO-QUICK:SYMB (use CAPITAL letters in the document) that contains the following lines:

*SCRIPT: /SINGLE/
  *INPUT: CONNECT-TO SCHOLAR
  *MACRO: LOGIN-DEFAULT,/MYSELF/,,FLOPPY-USER
  *DISPLAY-ON:
  *INPUT: QUICK-ACCOUNT
*ENDSCRIPT: /SINTRAN/

Example 19. A Simple Example of SCRIPT

SCRIPT signals the beginning of a SCRIPT, and ENDSCRIPT marks the end. A file may contain many SCRIPTS. /SINGLE/ means that this file only contains one SCRIPT. /SINTRAN/ means that the user of the SCRIPT will return to SINTRAN on her/his local system after the program QUICK-ACCOUNT has been run.

ND-30.025.02

Page 57

COSMOS Operator Guide

THE SCRIPT FACILITY OF CONNECT-TO

The four lines starting with the line identifiers INPUT:, MACRO:, DISPLAY-ON: and INPUT: make up the SCRIPT body.

Note that each identifier in SCRIPT must start with an asterisk (*) and end with a colon (:). Extra blanks are stripped. It is not necessary to indent the SCRIPT body, but this will make your SCRIPT file much easier to read.

To create a SCRIPT out of the file above, do the following in SINTRAN:

┌───────────────────────────────────────────────────────────────┐
│ MAIN@CONNECT-TO ⎯⎯⎯⎯⎯⎯⎯⏎                                             │
│                                                               │
│ COSMOS CONNECT-TO PROGRAM VERSION - B, NOV. 28, 1983          │
│ C-T: SERVICE-PROGRAM ⎯⎯⎯⎯⏎                                      │
│                                                               │
│ CONNECT-TO service-program version B                          │
│ CT-SERV: INITIALIZE-SCRIPT ⎯⎯⎯⏎                                │
│ SCRIPT-FILE: GO-QUICK:SYMB ⎯⎯⎯⏎                                │
│ --- SCRIPT NAME .......... : /SINGLE/                          │
│   Remote command mode .. : NOT ALLOWED.                        │
│   Command mode return to : LOCAL COMMAND MODE.                 │
│                                                               │
│ CT-SERV: DUMP-PROGRAM ⎯⎯⎯⏎                                     │
│ PROG-FILE: 'GO-QUICK' ⎯⎯⎯⏎                                     │
│ CT-SERV: EXIT ⎯⎯⏎                                             │
│                                                               │
│ C-T: EXIT ⎯⎯⏎                                                 │
│                                                               │
│ MAIN⏎                                                         │
└───────────────────────────────────────────────────────────────┘

Example 20. Initializing and Dumping a SCRIPT Program

You will now have a file called GO-QUICK:PROG. To execute the SCRIPT, you write:

┌──────────────────────┐
│ MAIN@GO-QUICK ⎯⎯⏎    │
└──────────────────────┘

Example 21. Starting a SCRIPT Program

You will automatically be connected to SCHOLAR, logged in as yourself (if that does not work, you will be logged in as FLOPPY-USER) and you will start the program called QUICK-ACCOUNT. When you are finished using QUICK-ACCOUNT, you will automatically be returned to your local system.

ND-30.025.02

Page 58

COSMOS Operator Guide

THE SCRIPT FACILITY OF CONNECT-TO

If you merely want to test a SCRIPT program, don't use the DUMP-PROGRAM command; exit to SINTRAN instead. Then write:

@GOTO-USER 0 ↵

Example 22. Testing a SCRIPT Program

If the SCRIPT programs you write are going to be used quite often, you may want to dump them as reentrant programs:

@DUMP-PROGRAM-REENTRANT GO-QUICK GO-QUICK:PROG ↵

Example 23. Dumping a SCRIPT Program Reentrant

You may want to include many SCRIPTs in the same SCRIPT program. That will reduce the number of :PROG files. For instance, the program SCRIPT:PROG could contain SCRIPTs for QUICK-ACCOUNT, FORTRAN-500, ND-500-MONITOR, etc., and the user would write:

@SCRIPT ND-500-MONITOR ↵

Example 24. Starting a Multi-SCRIPT Program

But use shorter SCRIPT names than these since they cannot be abbreviated by users.

ND-30.025.02

Page 59

4.3 SCRIPT Syntax

The following identifiers are allowed in SCRIPTs:

*SCRIPT: /SINGLE/
*SCRIPT: (SCRIPT name)
*INPUT: (character string)
*ADDIN: (character string)
*MACRO: LOGIN-SPECIFIED (user name and password(s))
*MACRO: LOGIN-DEFAULT /MYSELF (project password/user name and password(s))
*MACRO: LOGIN-DEFAULT /UE/
*MACRO: ASK-SCRIPT (character string)
*DISPLAY-ON:
*DISPLAY-OFF:
*ENDSCRIPT:
*ENDSCRIPT: /SINTRAN/
*ENDSCRIPT: (subsystem name)

Table 2. The Different SCRIPT Macros and Identifiers

Each identifier must be preceded by an asterisk (*) and followed by a colon (:).

4.4 How to Begin and End a SCRIPT

The two identifiers SCRIPT: and ENDSCRIPT: start and end SCRIPTs:

4.4.1 *SCRIPT:

SCRIPT: must be the first thing written in a SCRIPT file. A file must contain one SCRIPT: identifier for each SCRIPT in the file. The identifier *SCRIPT: can be followed by one of three things:

1) If you have only one SCRIPT in the file, use:

*SCRIPT: /SINGLE/

If *SCRIPT: appears more than once in that file, you will get an error message when you try to initialize the SCRIPT.

Page 60

COSMOS Operator Guide

THE SCRIPT FACILITY OF CONNECT-TO

2) If your SCRIPT file contains many SCRIPTs, use this for each of them:

*SCRIPT: (SCRIPT name)

Note that the