user's guide -...

Communications

Bull DPS 7000User's Guide

Network User's Guide

47 A2 94UC Rev06

47 A2 94UC Rev06

Communications

Bull DPS 7000User's Guide


Subject: This manual describes the commands used by and themessages output to the network operator/administrator. It alsotreats the load and dump functions of CNP 7 and variousDatanet models, or MainWay 2600LE. It describes operationand administration of communications processor 7.

Special Instructions:

Software Supported: GCOS 7-V10 TS9920

Software/Hardware required:

Date: February 2005

Bull CEDOC357 Avenue PattonBP 2084549008 ANGERS Cedex 01FRANCE

47 A2 94UC Rev06

Copyright © Bull S.A., 1992-2005

Bull acknowledges the rights of proprietors of trademarks mentioned herein.

Your suggestions and criticisms concerning the form, contents and presentation of this manual are invited.A form is provided at the end of this manual for this purpose.

No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by anymeans, electronic, mechanical or otherwise without the prior written permission of the publisher.

Bull disclaims the implied warranties of merchantability and fitness for a particular purpose and makes noexpress warranties except as may be stated in its written agreement with and for its customer. In no event is Bullliable to anyone for any indirect, special, or consequential damages.The information and specifications in this document are subject to change without notice.Consult your Bull Marketing Representative for product or service availability.

47 A2 94UC iii

Preface

This manual describes all the procedures involved in operating a DPS 7000network. It lists the GCOS 7 commands for managing and controlling the networkresources. It treats the administrative functions for configuring and managing thefront-end processors. The manual also treats the maintenance functions forproviding traces in the communications servers.

The manual is intended for the System Administrator and the Console (networkcontrol) Operator, and for all users with an interest in operating and managing theresources of the network configured to the DPS 7000 host.

Section 1 introduces the environment of the network and the procedures foroperating the network.

Sections 2 and 3 of this document is a list of GCL commands used for networkoperations.

Section 4 describes the management functions performed by FECM for generatingthe software (SYSGEN), loading and dumping the Datanet, CNP 7 or MainWay2600LE.

Section 5 discusses OCS Front Ends (all Front Ends managed by OCS) and theirassociated communications server OCS (Open Communications Subsystem). Italso discusses scenarios for these OCS Front Ends.

Section 6 gives the list of messages issued to the network control operator.

Section 7 discusses the correspondence between GCOS 7 administrativecommands and AEP commands.

Section 8 gives the record format of GCOS 7 unsolicited messages.

Section 9 describes BNSE (Basic Network Session Exerciser). BNSE can be usedto provide a controlled environment for establishing a session and transferring data.

Section 10 describes the maintainability and trace aspects of network operation.

Appendix A lists FECM service messages which are written to the SYSOUT andthe JOR.

Scope andObjectives

IntendedReaders

Structure


iv 47 A2 94UC

Appendix B describes the use of CPDS and gives the syntax of CPDS commands.

Appendix C gives the scenarios delivered with the standard network generation forthe CNP 7 and the Datanet.

Appendix D discusses GCOS 7 communications installation.

Appendix E lists communications error codes.

The following publications complement the information given in this manual:

For defining and implementing DSA networking:

DSA Concepts ........................................................................................... 39 A4 9725DSA Network Configuration Guide .......................................................... 39 A2 8932DSA Network Administration Guide......................................................... 39 A2 8849

For managing terminals configured to the CNP 7:

Terminal Management ............................................................................ 39 A2 43DM

For managing terminals configured to the MainWay:

Terminal Management .............................................................................. 39 A2 9820

For CNS 7 network directives and CNP 7 system generation:

CNS 7 System Generation ...................................................................... 39 A2 40DM

For DNS network directives and Datanet system generation:

DNS V4 System Generation .....................................................................39 A2 22DNDNS V4 NGL Reference Manual .............................................................39 A2 23DN

MainWay and MainWay 2600LE:

MainWay Overview.................................................................................. 39 A2 14EBMainWay 2600LE User's Guide .............................................................. 39 A2 60AEMainWay 2600LE HW, SW & Maintenance Guide.................................. 39 A2 61AEMainWay 2600 Site Preparation Guide.................................................. 39 A1 82 RADNS-E System Generation Guide.......................................................... 39 A2 09 EBNGL Reference Manual ......................................................................... 39 A1 10 EB

Bibliography

Preface

47 A2 94UC v

For configuring the front-end system generation using FPG 7:

Simple Generation Guide using FPG 7.................................................. 39 A2 46DM

For the following details on DPS 7/7000 networks:

• implementation of ISO/DSA concepts

• generating the DPS 7/7000 networking environment using NETGEN

• standard network generation and FECM scenarios

Network Overview and Concepts ............................................................47 A4 92UCNetwork Generation ................................................................................47 A2 93UC

For details of the CPDS utility used for editing DNS and CNS 7 dumps:

CPDS User's Guide .................................................................................47 A2 36UC

For the administration and control of the DPS 7000 network:

DSAC User's Guide .................................................................................47 A2 75UC

For programming administrative utilities on the DPS 7000:

AUPI User's Guide ..................................................................................47 A2 76UC

For programming communications applications using MAM/QMON:

MCS User's Guide ...................................................................................47 A2 32UC

For details concerning the role of the MAIN operator:

System Operator Guide .......................................................................... 47 A2 60UU

For details of the various console and other messages that may be generatedby GCOS 7:

Console Messages Manual ..................................................................... 47 A2 61UUMessages and Return Codes Directory ....................................................47 A2 10UJ


vi 47 A2 94UC

For details of the system messages and return codes that may be generated bythe DSA network:

DSA Network System Messages and Return Codes ................................ 39 A2 26DM

DPS 7000 to XTA Evolution Guide:

V7000 Operator's Guide.......................................................................... 47 A2 74USV7000 Configuration and Maintenance Guide......................................... 77A2 77USV7000 Software Installation and Activation Guide ................................ 77 A2 88USGCOS7 - System Installation Configuration and Updating Guide ......... 47 A2 23USGCOS7-V10 System Operator's Guide................................................... 47 A2 53 USDPS 7000/XTA Interop 7 User's Guide ................................................... 47 A2 91USGCOS 7 Console Messages Directory.................................................... 47 A2 61UUGCOS 7 Messages and Return Codes Directory ......................................47 A2 10UJ

For more information about V7000 operations:

V7000 Operator’s Guide..........................................................................47 A2 74UC

For more detailed information on the VCAM-ISO trace facility:

VCAM-ISO User's Guide.........................................................................47 A2 60UC

VCAM-ISO Reference Manual, Volume 1................................................47 A2 61UCVCAM-ISO Reference Manual, Volume 2................................................47 A2 62UC

The following notation conventions are used in this manual when describing thesyntax of commands:

UPPERCASE The keyword item must be coded exactly as shown.

Lowercase Indicates a user-supplied parameter value. The symbolic namedigitsn is used to represent a string of decimal digits ofmaximum length n.

[item] An item within square brackets is optional.

{item 1}{item 2}{item 3}

A column of items within braces means that one value must beselected if the associated parameter is specified. The defaultvalue (if any) is underlined.

( ) Parentheses must be coded if they enclose more than one item.

. . . An ellipsis indicates that the preceding item may be repeatedone or more times.

SyntaxNotation

Preface

47 A2 94UC vii

GCOS 7 Documentation

The complete GCOS 7 document set is available on one CD-ROM. This product isknown as CD-DOC. It is delivered with each system or software update, it isupdated for each new GCOS 7 release. A WEB site is available to downloaddocuments which have been updated between 2 CD-ROM versions, its URL isindicated as a link on the CD-ROM itself.


viii 47 A2 94UC

47 A2 94UC ix

Table of Contents

1. Introduction

1.1 Scope and Purpose ........................................................................................................ 1-1

1.2 Network Operation Management.................................................................................... 1-2

1.3 Network Operation Functions ......................................................................................... 1-2

2. ISO/DSA Commands (CRAL to EDD)

2.1 CREATE Command........................................................................................................ 2-6

2.1.1 CRAL .......................................................................................................... 2-6

2.1.2 CRRB .......................................................................................................... 2-8

2.2 DBSVR (DEBUG_SERVER)......................................................................................... 2-10

2.3 DELETE Command ...................................................................................................... 2-11

2.3.1 DLAL ........................................................................................................ 2-11

2.3.2 DLRB ........................................................................................................ 2-12

2.4 DMBX ........................................................................................................ 2-13

2.5 DNET (DISPLAY_NETWORK) ..................................................................................... 2-14

2.5.1 DNET AC ........................................................................................................ 2-18

2.5.2 DNET AF ........................................................................................................ 2-20

2.5.3 DNET AG ........................................................................................................ 2-22

2.5.4 DNET AL ........................................................................................................ 2-24

2.5.5 DNET CB ........................................................................................................ 2-26

2.5.6 DNET CC ........................................................................................................ 2-28

2.5.7 DNET CH ........................................................................................................ 2-31

2.5.8 DNET CT ........................................................................................................ 2-33

2.5.9 DNET FL ........................................................................................................ 2-38

2.5.10 DNET ID 2-41

2.5.11 DNET IS 2-43

2.5.12 DNET LC 2-46

2.5.13 DNET LG 2-49


x 47 A2 94UC

2.5.14 DNET MB 2-51

2.5.15 DNET NK 2-53

2.5.16 DNET NR 2-55

2.5.17 DNET OP 2-57

2.5.18 DNET PC 2-59

2.5.19 DNET PL 2-62

2.5.20 DNET QD 2-67

2.5.21 DNET RB 2-74

2.5.22 DNET SA 2-76

2.5.23 DNET SB 2-78

2.5.24 DNET SC 2-80

2.5.25 DNET SP 2-84

2.5.26 DNET SR 2-86

2.5.27 DNET SS 2-89

2.5.28 DNET SY 2-92

2.5.29 DNET TC 2-96

2.5.30 DNET TS 2-101

2.6 DNR (DISPLAY_NETWORK_REPORTING).............................................................. 2-107

2.7 DTL (DISPLAY_TEST_IN_LINE)................................................................................ 2-108

2.8 DTSVR (DISPLAY_TELECOM_SERVER)................................................................. 2-110

2.9 DVTR (DISPLAY_VCAM_TRACE)............................................................................. 2-114

2.10 EDD (ENTER_DSA_DIALOG).................................................................................... 2-115

3. ISO/DSA Commands (LNET to TVTR)

3.1 LNET (LIST_NETWORK) ............................................................................................... 3-2

3.1.1 LNET AC .......................................................................................................... 3-5

3.1.2 LNET AF .......................................................................................................... 3-7

3.1.3 LNET AG .......................................................................................................... 3-9

3.1.4 LNET AL ........................................................................................................ 3-11

3.1.5 LNET CB ........................................................................................................ 3-13

3.1.6 LNET CC ........................................................................................................ 3-14

3.1.7 LNET CH ........................................................................................................ 3-16

3.1.8 LNET CT ........................................................................................................ 3-18

3.1.9 LNET FL ........................................................................................................ 3-21

3.1.10 LNET ID 3-23

3.1.11 LNET IS 3-24

3.1.12 LNET LC 3-26

3.1.13 LNET LG 3-28

3.1.14 LNET MB 3-29

47 A2 94UC xi

3.1.15 LNET NK 3-31

3.1.16 LNET NR 3-33

3.1.17 LNET OP 3-34

3.1.18 LNET PL 3-35

3.1.19 LNET QD 3-38

3.1.20 LNET RB 3-40

3.1.21 LNET SA 3-42

3.1.22 LNET SB 3-44

3.1.23 LNET SC 3-46

3.1.24 LNET SP 3-49

3.1.25 LNET SR 3-50

3.1.26 LNET SS 3-52

3.1.27 LNET SY 3-54

3.1.28 LNET TC 3-57

3.1.29 LNET TS 3-59

3.1.30 LNET WS 3-64

3.2 MDNET (MODIFY_NETWORK) ................................................................................... 3-65

3.2.1 MDNET AC...................................................................................................... 3-68

3.2.2 MDNET AF ...................................................................................................... 3-70

3.2.3 MDNET AG...................................................................................................... 3-72

3.2.4 MDNET AL....................................................................................................... 3-74

3.2.5 MDNET CH...................................................................................................... 3-75

3.2.6 MDNET CT ...................................................................................................... 3-77

3.2.7 MDNET FL....................................................................................................... 3-80

3.2.8 MDNET LG ...................................................................................................... 3-86

3.2.9 MDNET OP...................................................................................................... 3-88

3.2.10 MDNET PL ...................................................................................................... 3-90

3.2.11 MDNET QD...................................................................................................... 3-92

3.2.12 MDNET RB...................................................................................................... 3-97

3.2.13 MDNET SA ...................................................................................................... 3-99

3.2.14 MDNET SB .................................................................................................... 3-101

3.2.15 MDNET SR.................................................................................................... 3-103

3.2.16 MDNET TS .................................................................................................... 3-105

3.3 MDTL (MODIFY_TEST_IN_LINE).............................................................................. 3-109

3.4 MDTSVR (MODIFY_TELECOM_SERVER) ............................................................... 3-111

3.5 PRTTR (PRINT_TELECOM_TRACE) ........................................................................ 3-114

3.6 SCNVTR (SCAN_VCAM_TRACE) ............................................................................. 3-117

3.7 SNDQ (SEND_QUEUE) ............................................................................................. 3-118

3.8 SNR (START_NETWORK_REPORTING) ................................................................. 3-120


xii 47 A2 94UC

3.9 STL (START_TEST_IN_LINE) ................................................................................... 3-125

3.10 STSVR (START_TELECOM_SERVER) .................................................................... 3-128

3.11 STTR (START_TELECOM_TRACE).......................................................................... 3-132

3.12 SVTR (START_VCAM_TRACE)................................................................................. 3-134

3.13 TNR (TERMINATE_NETWORK_REPORTING) ........................................................ 3-135

3.14 TTL (TERMINATE_TEST_IN_LINE) .......................................................................... 3-136

3.15 TTSVR (TERMINATE_TELECOM_SERVER)............................................................ 3-137

3.16 TTTR (TERMINATE_TELECOM_TRACE)................................................................. 3-140

3.17 TVTR (TERMINATE_VCAM_TRACE)........................................................................ 3-142

4. FECM Functions

4.1 Overview .......................................................................................................... 4-2

4.1.1 INTRODUCTION ............................................................................................... 4-2

4.1.2 DATANET MANAGEMENT............................................................................... 4-3

4.1.3 CNP 7 AND LCT MANAGEMENT..................................................................... 4-4

4.1.4 MAINWAY 2600LE MANAGEMENT ................................................................. 4-5

4.1.5 MULTIVERSION MANAGEMENT..................................................................... 4-6

4.1.6 FILES AND SCENARIOS.................................................................................. 4-7

4.2 Startup and Automatic Mode .......................................................................................... 4-8

4.2.1 DATANET.......................................................................................................... 4-84.2.1.1 STARTUP OF FECM ........................................................................ 4-84.2.1.2 STARTUP OF FEPS ......................................................................... 4-9

4.2.2 CNP 7 .......................................................................................................... 4-9

4.2.3 MAINWAY 2600LE .......................................................................................... 4-10

4.2.4 DPS 7000 ISL CONTROLLER ........................................................................ 4-10

4.3 Description of Files and Subfiles................................................................................... 4-11

4.3.1 SYS.DSABLIB ................................................................................................. 4-12

4.3.2 SYS.DSACONF............................................................................................... 4-14

4.3.3 SYS.DSACORE............................................................................................... 4-16

4.3.4 SYS.DSADUMP............................................................................................... 4-17

4.3.5 SYS.DSASLIB ................................................................................................. 4-18

4.3.6 SYS.HUBG ...................................................................................................... 4-20

4.4 Description of Scenarios ............................................................................................... 4-21

4.4.1 SOFTWARE VERSION NUMBER .................................................................. 4-22

4.4.2 GENERAL RULES FOR THE SCENARIO...................................................... 4-23

4.4.3 SYNTAX OF THE SCENARIO ........................................................................ 4-244.4.3.1 VERSION ORDER .......................................................................... 4-254.4.3.2 NODE ORDER................................................................................ 4-25

47 A2 94UC xiii

4.4.3.3 SCEN ORDER ................................................................................ 4-274.4.3.4 DUMP ORDER................................................................................ 4-274.4.3.5 LOAD ORDER................................................................................. 4-274.4.3.6 GO ORDER..................................................................................... 4-284.4.3.7 COMMENT...................................................................................... 4-28

4.5 Administrative Functions............................................................................................... 4-29

4.5.1 FILE NAMES ................................................................................................... 4-29

4.5.2 FRONT-END PROCESSOR GENERATION: SYSGEN ................................. 4-304.5.2.1 DATANET SYSTEM GENERATION............................................... 4-304.5.2.2 CNP 7 SYSTEM GENERATION..................................................... 4-364.5.2.3 MAINWAY 2600LE SYSTEM GENERATION................................ 4-43

4.5.3 FRONT-END PROCESSOR: LOAD................................................................ 4-504.5.3.1 DATANET LOAD............................................................................. 4-504.5.3.2 CNP 7 LOAD................................................................................... 4-534.5.3.3 MAINWAY 2600LE LOAD............................................................... 4-57

4.5.4 FRONT-END PROCESSOR DUMP................................................................ 4-604.5.4.1 DATANET OR CNP7 DUMP........................................................... 4-604.5.4.2 MAINWAY 2600LE DUMP.............................................................. 4-64

4.5.5 CONTROLLER FUNCTIONS.......................................................................... 4-674.5.5.1 LOAD FUNCTION........................................................................... 4-674.5.5.2 DUMP FUNCTION .......................................................................... 4-67

4.6 DSA Administrative Storage Facility ............................................................................. 4-68

4.6.1 INTRODUCTION ............................................................................................. 4-68

4.6.2 ASF HANDLER STARTUP AND EXECUTION............................................... 4-68

4.6.3 FILES SUPPORTED ....................................................................................... 4-69

4.6.4 VERSION NUMBER........................................................................................ 4-69

4.6.5 USE OF THE ASF FUNCTION ....................................................................... 4-71

4.6.6 OPERATOR INTERFACE ............................................................................... 4-71

4.6.7 PREREQUISITES............................................................................................ 4-72

4.6.8 RUNNING THE TEST ..................................................................................... 4-73

4.6.9 EXAMPLE OF REMOTE LOADING................................................................ 4-74

5. OCS Server Functions

5.1 Overview .......................................................................................................... 5-1

5.1.1 OSI/DIWS ADMINISTRATION .......................................................................... 5-1

5.1.2 IPS ADMINISTRATION ..................................................................................... 5-25.1.2.1 BASIC TCP/IP ADMINISTRATIVE COMMANDS............................. 5-25.1.2.2 SNMP AGENT................................................................................... 5-25.1.2.3 SNMP MANAGER............................................................................. 5-3

5.2 Startup and Automatic Mode .......................................................................................... 5-3

5.2.1 STARTING OCS................................................................................................ 5-3

5.2.2 STARTING AN INCREMENTAL CONFIGURATION ........................................ 5-45.2.2.1 AUTOMATIC LAUNCH ..................................................................... 5-4


xiv 47 A2 94UC

5.2.2.2 OPERATOR LAUNCH ...................................................................... 5-4

5.2.3 STOPPING OCS ............................................................................................... 5-4

5.3 Description of Files and Subfiles..................................................................................... 5-5

5.3.1 SYS.DSABLIB ................................................................................................... 5-5

5.3.2 SYS.DSACONF................................................................................................. 5-5

5.3.3 SYS.DSASLIB ................................................................................................... 5-7

5.3.4 SYS.DSADUMP................................................................................................. 5-7

5.3.5 SYS.DSATRC_<LCT NAME>_N....................................................................... 5-7

5.3.6 SYS.DSATRCIDX_<LCT NAME> ..................................................................... 5-8

5.3.7 SYS.DSATRCIDT_<VERSION> ....................................................................... 5-8

5.3.8 SUBFILES USED FOR IPS............................................................................... 5-8

5.4 Description of OCS Front End Scenarios ....................................................................... 5-9

5.5 Orders for OCS Scenarios ............................................................................................ 5-13

5.5.1 NODE ORDER ................................................................................................ 5-13

5.5.2 SCEN ORDER................................................................................................. 5-14

5.5.3 DUMP ORDER ................................................................................................ 5-15

5.5.4 LOAD ORDER................................................................................................. 5-16

5.5.5 GO ORDER ..................................................................................................... 5-17

5.6 IPS Administration Commands..................................................................................... 5-20

5.6.1 ARP COMMAND ............................................................................................. 5-20

5.6.2 ENDNETST COMMAND ................................................................................. 5-27

5.6.3 ENDPING COMMAND .................................................................................... 5-28

5.6.4 IFCONFIG COMMAND ................................................................................... 5-29

5.6.5 NETSTAT COMMAND .................................................................................... 5-34

5.6.6 PING COMMAND............................................................................................ 5-40

5.6.7 ROUTE COMMAND ........................................................................................ 5-42

5.7 SNMP Manager Commands......................................................................................... 5-48

5.7.1 REQUEST COMMANDS................................................................................. 5-48

5.7.2 STOP COMMANDS ........................................................................................ 5-48

5.7.3 DOCUMENTATION COMMANDS .................................................................. 5-49

5.7.4 COMMON PARAMETERS .............................................................................. 5-49

5.7.5 CRSNMPDOC COMMAND ............................................................................. 5-51

5.7.6 ENDGETAR COMMAND................................................................................. 5-56

5.7.7 ENDGETCN COMMAND ................................................................................ 5-57

5.7.8 ENDGETNT COMMAND................................................................................. 5-58

5.7.9 ENDGETRT COMMAND................................................................................. 5-59

5.7.10 ENDGETUD COMMAND ................................................................................ 5-60

5.7.11 ENDSNMP COMMAND................................................................................... 5-61

5.7.12 ENDSNMPG COMMAND................................................................................ 5-62

47 A2 94UC xv

5.7.13 ENDSNMPN COMMAND ................................................................................ 5-63

5.7.14 ENDSNMPS COMMAND ................................................................................ 5-64

5.7.15 GETARP COMMAND...................................................................................... 5-65

5.7.16 GETNET COMMAND ...................................................................................... 5-67

5.7.17 GETROUTE COMMAND................................................................................. 5-69

5.7.18 GETTCPCN COMMAND................................................................................. 5-71

5.7.19 GETUDP COMMAND...................................................................................... 5-73

5.7.20 SNMPDOC COMMAND .................................................................................. 5-75

5.7.21 SNMPGET COMMAND................................................................................... 5-76

5.7.22 SNMPNEXT COMMAND................................................................................. 5-78

5.7.23 SNMPSET COMMAND ................................................................................... 5-80

5.8 OSI/DIWS Extended Set of Commands ....................................................................... 5-82

5.8.1 ATTACH_FCP_IVMO COMMAND.................................................................. 5-83

5.8.2 CREATE_FCP_TCIVMO COMMAND............................................................. 5-85

5.8.3 DISPLAY_FCP_TCIVMO COMMAND ............................................................ 5-87

5.8.4 DISPLAY_IVMO_LINK COMMAND ................................................................ 5-89

5.8.5 FCP_EXTENDED_GA_TC COMMAND.......................................................... 5-91

5.8.6 LIST_FCP_TCIVMO COMMAND.................................................................... 5-93

5.8.7 MODIFY_FCP_TCIVMO COMMAND ............................................................. 5-94

5.8.8 UPGRADE_FCP_CONFIG COMMAND ......................................................... 5-96

6. Messages

6.1 CA Messages .......................................................................................................... 6-3

6.2 CC Messages ........................................................................................................ 6-16

6.3 CD Messages ........................................................................................................ 6-17

6.4 FE Messages ........................................................................................................ 6-18

6.5 FR Messages ........................................................................................................ 6-35

6.6 NA Messages ........................................................................................................ 6-45

6.7 NC Messages ........................................................................................................ 6-56

6.8 NG Messages ...................................................................................................... 6-147

6.9 QC Messages ...................................................................................................... 6-157

6.10 TF Messages ...................................................................................................... 6-162

6.11 TP Messages ...................................................................................................... 6-170

7. GCOS 7 Command Support


xvi 47 A2 94UC

8. GCOS 7 Unsolicited Messages

8.1 Introduction .......................................................................................................... 8-1

8.2 CC : Unsolicited Messages for Channel Connections.................................................... 8-5

8.2.1 CHANNEL CONNECTION OPEN..................................................................... 8-5

8.2.2 CHANNEL CONNECTION OPEN FAIL ............................................................ 8-6

8.2.3 CHANNEL CONNECTION CLOSE................................................................... 8-7

8.2.4 CHANNEL CONNECTION ERROR .................................................................. 8-8

8.2.5 CHANNEL CONNECTION HISTORY REPORT............................................... 8-9

8.3 CH : Unsolicited Messages for Channel ....................................................................... 8-10

8.4 CT : Unsolicited Messages for Controller ..................................................................... 8-11

8.5 EX : Unsolicited Messages for Executive ..................................................................... 8-12

8.6 FT : Unsolicited Messages for File Transfers ............................................................... 8-14

8.6.1 FILE TRANSFER OPEN ................................................................................. 8-14

8.6.2 FILE TRANSFER OPEN FAIL......................................................................... 8-16

8.6.3 FILE TRANSFER FILE CREATE .................................................................... 8-19

8.6.4 FILE TRANSFER FILE DELETE..................................................................... 8-22

8.6.5 FILE TRANSFER FILE RENAME.................................................................... 8-24

8.6.6 FILE TRANSFER CLOSE ............................................................................... 8-26

8.6.7 FILE TRANSFER HISTORY REPORT............................................................ 8-29

8.6.8 FILE TRANSFER ERROR............................................................................... 8-31

8.7 FX: Unsolicited Messages for AF Connections ............................................................ 8-33

8.7.1 AF CONNECTION OPEN................................................................................ 8-33

8.7.2 AF CONNECTION OPEN FAIL ....................................................................... 8-34

8.7.3 AF CONNECTION CLOSE.............................................................................. 8-35

8.7.4 AF CONNECTION ERROR............................................................................. 8-36

8.8 IS : Unsolicited Messages for ISO Sessions ................................................................ 8-37

8.8.1 ISO SESSION CONNECTION OPEN............................................................. 8-37

8.8.2 ISO SESSION CONNECTION OPEN FAIL .................................................... 8-39

8.8.3 ISO SESSION CONNECTION CLOSE........................................................... 8-41

8.8.4 ISO SESSION CONNECTION HISTORY REPORT....................................... 8-43

8.9 LC : Unsolicited Messages for Logical Connections..................................................... 8-44

8.9.1 LOGICAL CONNECTION OPEN..................................................................... 8-44

8.9.2 LOGICAL CONNECTION OPEN FAIL............................................................ 8-45

8.9.3 LOGICAL CONNECTION CLOSE................................................................... 8-46

8.9.4 LOGICAL CONNECTION HISTORY REPORT............................................... 8-47

47 A2 94UC xvii

8.10 LG : Unsolicited Messages for Administrative Logs ..................................................... 8-49

8.10.1 ADMINISTRATIVE LOGFILE OPEN............................................................... 8-49

8.10.2 ADMINISTRATIVE LOGFILE OPEN FAIL ...................................................... 8-50

8.10.3 ADMINISTRATIVE LOGFILE CLOSE............................................................. 8-51

8.11 NA : Unsolicited Messages for NAD ............................................................................. 8-52

8.12 NK : Unsolicited Messages for Internet Network Activity.............................................. 8-53

8.12.1 INTERNET NETWORK ACTIVITY HISTORY REPORT................................. 8-53

8.13 SS : Unsolicited Messages for Sessions ...................................................................... 8-54

8.13.1 SESSION OPEN.............................................................................................. 8-54

8.13.2 SESSION OPEN FAIL..................................................................................... 8-55

8.13.3 SESSION CLOSE............................................................................................ 8-56

8.13.4 SESSION HISTORY REPORT........................................................................ 8-57

8.14 SU : Unsolicited Messages for System Startup ............................................................ 8-59

8.15 TC : Unsolicited Messages for Transport Connections ................................................ 8-60

8.15.1 TRANSPORT CONNECTION OPEN.............................................................. 8-60

8.15.2 TRANSPORT CONNECTION OPEN FAIL ..................................................... 8-62

8.15.3 TRANSPORT CONNECTION CLOSE............................................................ 8-64

8.15.4 TRANSPORT CONNECTION ERROR ........................................................... 8-66

8.15.5 TRANSPORT CONNECTION HISTORY REPORT........................................ 8-67

8.16 Tl : Unsolicited Messages for Tests.............................................................................. 8-69

8.16.1 TEST ROUTINE EXECUTE ............................................................................ 8-69

8.16.2 TEST ROUTINE CLOSE ................................................................................. 8-70

8.16.3 TEST ROUTINE HISTORY REPORT ............................................................. 8-71

8.16.4 TEST ROUTINE ERROR ................................................................................ 8-72

8.17 TS : Unsolicited Messages for Transport Station ......................................................... 8-73

8.17.1 TRANSPORT STATION ERROR.................................................................... 8-73

9. Basic Network Session Exerciser (BNSE)

9.1 Purpose and General Description of BNSE.................................................................... 9-1

9.2 Configurations in the Primary Network ........................................................................... 9-2

9.3 SIDE Option .......................................................................................................... 9-3

9.3.1 ACCEPTOR SIDE ............................................................................................. 9-3

9.3.2 INITIATOR SIDE................................................................................................ 9-4

9.4 How to Start a BNSE Test .............................................................................................. 9-5

9.5 Outputs of a BNSE Test.................................................................................................. 9-5


xviii 47 A2 94UC

10. Maintainability

10.1 Passthrough for Dialog with the FEP............................................................................ 10-1

10.1.1 ACTIVATION AND DEACTIVATION............................................................... 10-2

10.1.2 CONNECTION AND DISCONNECTION ........................................................ 10-3

10.1.3 DEFAULT VALUES ......................................................................................... 10-4

10.1.4 DIALOG ...................................................................................................... 10-4

10.1.5 INTERRUPT .................................................................................................... 10-5

10.1.6 DISPLAY CONNECTIONS.............................................................................. 10-5

10.1.7 OUTPUTS ON CONSOLE AND SYSOUT...................................................... 10-6

10.2 Passthrough for Dialog with the MainWay 2600LE ...................................................... 10-8

10.3 Trace Facilities ...................................................................................................... 10-13

10.3.1 VCAM TRACE ............................................................................................... 10-1310.3.1.1 SVTR (START_VCAM_TRACE)................................................... 10-1410.3.1.2 SCNVTR (SCAN_VCAM_TRACE) ............................................... 10-1610.3.1.3 DESCRIPTION OF THE VCAM TRACE SCANNER DISPLAY.... 10-17

10.3.2 TNS, OCS AND FEPS FILE TRACE............................................................. 10-22

10.3.3 OCS TRACE FACILITY................................................................................. 10-28

10.3.4 UFT SERVER TRACE................................................................................... 10-29

10.3.5 DEBUGGING APPLICATIONS ..................................................................... 10-29

10.3.6 DBSVR (DEBUG_SERVER) ......................................................................... 10-30

10.3.7 ISL CONTROLLER........................................................................................ 10-35

10.3.8 OCS FRONT END TRACE FACILITY........................................................... 10-3610.3.8.1 OCS FRONT END TRACE OVERVIEW....................................... 10-3610.3.8.2 <DIR>.DSATRC_<LCT NAME>_I FILES ..................................... 10-3710.3.8.3 <DIR>.DSATRCIDX_<LCT NAME> FILE..................................... 10-3810.3.8.4 <DIR>.DSATRCIDT_<VERSION> FILE ....................................... 10-3810.3.8.5 OSI STACK TRACEABLE ENTITIES ........................................... 10-3810.3.8.6 IPS STACK TRACEABLE ENTITIES............................................ 10-3910.3.8.7 OTHER DRIVER TRACEABLE ENTITIES ................................... 10-3910.3.8.8 DEFINITION OF TRACE LEVELS................................................ 10-39

10.3.9 OCS FRONT END TRACE MANAGEMENT COMMANDS .......................... 10-4110.3.9.1 TRACE COMMAND ...................................................................... 10-4110.3.9.2 NOTRACE COMMAND................................................................. 10-4410.3.9.3 SEETRACE COMMAND............................................................... 10-4610.3.9.4 FCP_TRACE_TPDU COMMAND................................................. 10-5010.3.9.5 FCP_NOTRACE_TPDU COMMAND ........................................... 10-5310.3.9.6 FCP_SEETRACE_TPDU COMMAND.......................................... 10-5510.3.9.7 SEQUENCE OF TRCTPDU, STRCTPDU, TRACE, SEETRACE,

NOTRACE COMMANDS .............................................................. 10-5710.3.9.8 EDTRACE COMMAND ................................................................. 10-5910.3.9.9 OCS FRONT END TRACE OUTPUT FORMAT........................... 10-63

10.3.10 OCS FRONT END XID/TEST/ECHO SERVICES......................................... 10-6510.3.10.1 OVERVIEW................................................................................... 10-6510.3.10.2 XID COMMAND ............................................................................ 10-66

47 A2 94UC xix

10.3.10.3 TEST COMMAND ......................................................................... 10-6810.3.10.4 ENDTEST COMMAND ................................................................. 10-7010.3.10.5 SEND_ECHO_REQUEST COMMAND ........................................ 10-7110.3.10.6 FCP_END_ECHO_SENDING COMMAND .................................. 10-74

10.3.11 MISCELLANEOUS COMMANDS.................................................................. 10-7510.3.11.1 DISPLAY_FCP_ACTIVITY COMMAND ....................................... 10-7510.3.11.2 END_DISP_FCP_ACTIVITY COMMAND..................................... 10-7710.3.11.3 DISPLAY_FCP_MAC_ADDR COMMAND ................................... 10-7810.3.11.4 RESTART_FCP_ADMIN COMMAND .......................................... 10-79

A. FECM Service Messages

A.1 FECM Service Messages ...............................................................................................A-1

B. Scanning CNP 7 and Datanet Dumps

B.1 Scanning CNP 7 and Datanet Dumps ............................................................................B-1

B.1.1 CPU (CNS PROCESS UNIT ALIAS MEMORY UNIT) ......................................B-2

B.1.2 DESC (DESCRIPTORS) ...................................................................................B-3

B.1.3 DISP (DISPLACE) .............................................................................................B-4

B.1.4 EC (ECHO) ........................................................................................................B-5

B.1.5 GOTO (ALTER_INPUT) ....................................................................................B-6

B.1.6 MAP (MAP)........................................................................................................B-7

B.1.7 MAPF (MAPFAMILY) ........................................................................................B-8

B.1.8 MAPT (MAPTYPE) ............................................................................................B-9

B.1.9 NODISP (NODISPLACE) ................................................................................B-10

B.1.10 PITCB (PRINT INTERNAL TASK CONTROL BLOCK)...................................B-11

B.1.11 POFF (PRINTER OFF)....................................................................................B-12

B.1.12 PON (PRINTER ON) .......................................................................................B-13

B.1.13 PR (PRINT)......................................................................................................B-14

B.1.14 PRINTALL (ALL)..............................................................................................B-15

B.1.15 PST (PRINT STACK) ......................................................................................B-16

B.1.16 PSYSER (PRINT SYSTEM ERROR)..............................................................B-17

B.1.17 Q (QUIT) B-18

B.2 Explanation of Acronyms and Abbreviations ................................................................B-19

C. Standard FECM Scenarios

C.1 Standard FECM Scenarios .............................................................................................C-1

C.1.1 CNP 7 FOR DPS 7000 SYSTEMS....................................................................C-2

C.1.2 DPS 7000 SYSTEMS WITH DATANET AND CNP 7........................................C-6

C.1.3 DPS 7000/XTA WITH MAINWAY 2600LE ........................................................C-8


xx 47 A2 94UC

D. Communications Installation

D.1 Standard Network Configurations and FECM Scenarios ...............................................D-1

D.1.1 STANDARD BASIC NETWORK CONFIGURATION ........................................D-1

D.1.2 STANDARD FECM SCENARIOS .....................................................................D-1

D.2 DPS 7000 Series A .........................................................................................................D-2

D.2.1 STANDARD BASIC NETWORK CONFIGURATION ........................................D-2

D.2.2 STANDARD FECM SCENARIOS .....................................................................D-5

D.3 DPS 7000 Series: (200, 300, 500 and 700)....................................................................D-9

D.3.1 STANDARD NETWORK CONFIGURATION ....................................................D-9D.3.1.1 STANDARD NETWORK CONFIGURATION WITH ONLY ONE

CNP 7................................................................................................D-9D.3.1.2 STANDARD NETWORK CONFIGURATION WITH ONLY

DATANET........................................................................................D-11

D.3.2 STANDARD FECM SCENARIOS ...................................................................D-12

D.4 Models for Standard Network Configurations and Scenarios.......................................D-14

E. Specific Error Codes

Glossary

Index

47 A2 94UC xxi

Table of Graphics

7-1. GCOS 7 GCL Command/AEP Command Correspondence........................................... 7-27-2. Command/Object Matrix ................................................................................................. 7-3

Tables


xxii 47 A2 94UC

47 A2 94UC 1-1

1. Introduction

1.1 Scope and Purpose

This manual describes how a DPS 7000 network operating under GCOS 7 ismanaged and controlled by the network operator.

In the GCOS 7 communications environment a front-end processor can be used:

• to manage terminals of both the local network and the TRANSPAC secondarynetwork,

• to enable the DPS 7000 to access nodes (systems) of the primary network.

For DPS 7000, three kinds of FEP are avaibles:

• the integrated or extended CNP 7,

• the stand-alone Datanet,

• the stand-alone Mainway.

For DPS 7000/XTA, two types of MainWay are availables:

• MainWay 2600

• MainWay 2600LE

Terminals are always declared in the System Generation of the front-end processorand not in the Network Generation of the DPS 7000.

The GCOS 7 communications environment is assured by four networkmanagement components depending on the network, namely:

• TNS for all connections through an ISL controller,

• a separate FEPS occurrence for each Datanet connected to the DPS 7 over a PSIchannel,

• OCS for all connections through an OCS Front End acting on a FDDI for DSP7000.

• OCS Front End acting on an high performance Ethernet cable for DSP7000/XTA.


1-2 47 A2 94UC

1.2 Network Operation Management

When starting a GCOS session, the system console operator has implicit access tothe network operation functions. It is the system console operator who can firstissue the STSVR command to start a communications server.

Once the TNS server, an FEPS occurrence (which is also a server), or OCS serveris started, an operator logging on to IOF under the project specified with the MAINattribute can operate the network.

For details concerning the role of a main operator, refer to the System Operator'sGuide.

Network operation commands are GCL commands available only in GCL mode,not in OCL mode. A block mode terminal allows the operator the facility offormatted GCL menus, prompts and help texts. At the system console, thecommand can only be submitted in line mode.

1.3 Network Operation Functions

Network operation includes:

• managing communications servers: startup, shutdown and display status,

• managing the primary network over the Ethernet or the FDDI link cable: list,display and modify objects,

• managing the IPS stack (OCS only),

• managing the network by sending commands (list, display, modify) to a remoteDSA NAD (CNP 7, Datanet, Mainway, remote DPS 7000, etc.),

• monitoring network behavior using the Network Reporting function,

• analysing unsolicited messages sent by nodes,

• managing DSAC objects in the DPS 7000: list, display and modify,

• managing MCS queues: list, display and modify status and editing parameters,

• and starting inline tests, see STL command.

NOTE:It is also possible to operate the CNP 7 or Datanet, or MainWay 2600LE byconnecting to its NOI function using the passthrough mechanism (activated bythe EDD command).

47 A2 94UC 2-1

2. ISO/DSA Commands (CRAL to EDD)

Because of a limit on the size of a Section (in this manual), the commands listed inSection 2 and Section 3 cannot be contained in a single Section. The commandsare listed in alphabetical order. The split of commands between Section 2 andSection 3 was done to roughly balance the sizes of the Sections; there is no otherreason for the split.

Commands Described in this Section

The following GCL commands are described in this Section:

CRAL CReate_ALCRRB CReate_RBDBSVR DeBug_SerVeRDLAL DeLete_ALDLRB DeLete_RBDMBX Display_MailBoxDNET Display_NETworkDNR Display_Network_ReportingDTL Display_Test_in_LineDTSVR Display_Telecom_SerVeRDVTR Display_Vcam_TRaceEDD Enter_DSA_Dialog

NOTES:1. All these commands are available to MAIN operators except for DNET for

classes ID, IS, MB, QD, SC, SS and SY which are available to both MAINoperators and end-user operators.

2. The following are reserved for Maintenance purposes:- TRACE parameter of EDD command- $DEBUG application parameter of EDD command- DBSVR command.

3. The commands CRAL, CRRB, DLAL and DLRB are GCOS 7 commands(not DSAC commands).


2-2 47 A2 94UC

Objects

The use of the object is described by the following acronyms:

DSAC Distributed Systems Administration and Control.See the DSAC User's Guide.

NTGN Network Generation (NETGEN) utility for configuringthe network on the DPS 7000. See the manualNetwork Generation.

TRSP Object created dynamically by the communicationlayer (FEPS, TNS, or OCS). Used also by DSAC.

VCAM Virtual Communication Access Method.

FCPCONF OCS Front End Configuration.

The following list indicates which objects can be modified by operator commands.

Object Use Meaning and Effect of Network OperationsAC DSAC Administrative Correspondent ModifiableAF DSAC Administrative Function ModifiableAG DSAC Administrative Group ModifiableAL DSAC Addressing List ModifiableCB NTGN Cable Not ModifiableCC TRSP Channel Connection Not ModifiableCH NTGN Channel ModifiableCT NTGN Controller

LCT Local Controller ModifiableRCT Remote Controller ModifiableLCT Local Controller Not Modifiable

FL DSAC Filter ModifiableID NTGN ISO Session Descriptor Not ModifiableIS VCAM ISO Session Connection Not ModifiableLC VCAM Logical Connection Not ModifiableLCT NTGN Local Controller See CTLG DSAC Log ModifiableLPL NTGN Local Physical Link See PLLSC NTGN Local Session Control See SCLSYS NTGN Local System See SYLTS NTGN Local Transport Station See TS

ISO/DSA Commands (CRAL to EDD)

47 A2 94UC 2-3

Object Use Meaning and Effect of Network OperationsMB VCAM Mailbox Not ModifiableNR NTGN Network Route Not ModifiableNK TRSP Internet activity Not ModifiableOP DSAC Operator ModifiablePC TRSP Physical Connection Not ModifiablePL NTGN Physical Link

LPL Local Physical Link ModifiableRPL Remote Physical Link Not Modifiable

LPL FCPCONF Physical LinkLPL Local Physical Link Not Modifiable

QD NTGN Queue ModifiableRCT NTGN Remote Controller see CTRB DSAC Routing Base ModifiableRPL NTGN Remote Physical Link see PLRSC NTGN Remote Session Control see SCRSYS NTGN Remote System see SYRTS NTGN Remote Transport Station see TSSA NTGN Subdomain (GCOS specific) ModifiableSB DSAC Statistics Block ModifiableSC NTGN Session Control

LSC Local Session Control Not ModifiableRSC Remote Session Control Not Modifiable

SP VCAM Session Access Point address Not ModifiableSR NTGN Session Route ModifiableSS VCAM Session Not ModifiableSY NTGN System

LSYS Local System Not ModifiableRSYS Remote System Not Modifiable

TC TRSP Transport Connection Not ModifiableTS NTGN Transport Station

LTS Local Transport Station Not ModifiableRTS Remote TransportStation

Modifiable

LTS FCPCONF Transport StationLTS Local Transport Station Modifiable

WS VCAM Workstation Not Modifiable


2-4 47 A2 94UC

Scope of GCOS 7 Networks Commands

The scope of GCOS 7 network commands is shown below.

The codes in the table are:

o = implemented on GCOS 7 onlyx = implemented on GCOS 7 and other DSA systems (can be sent from GCOS 7 to any DSA system supporting them)

A = when used on GCOS 7, applicable to administrative functionsD = when used on GCOS 7, applicable to DSA (or ISO/DSA) session and common to TNS, FEPS, and OCSF = when used on GCOS 7, applicable to OCSI = when used on GCOS 7, applicable to ISO session and common to TNS, FEPS, and OCSM = specific to MCSP = when used on GCOS 7, applicable to FEPS/PSIT = when used on GCOS 7, applicable to TNS/ISL


47 A2 94UC 2-5

COMMANDSObject DNET LNET MDNET CR DL

AF xA xA xAAG xA xA xAAL xF xF xF oF oFCB xT xTCC xPT xPTCH xP xP xPCT xFPT xFPT xPTFL xA xA xAID xI xI xIIS xI xILC xD xDLG xA xA xAMB xD xDNK xF xFNR xT xTOP xA xA xAPC xFT xTPL xFT xFT xTQD oM oM oMRB xF xF xF oF oFSA xI xI xISB xA xA xASC xD xDSP xI xISR xD xDSS xD xDSY xD xDTC xFT xFTTS xFT xFT xFTSV the commands DTSVR, STSVR, TTSVR, and MDTSVR

are specific to GCOS 7 and apply to all servers (that is, toTNS, FEPS, FECM, and OCS)


2-6 47 A2 94UC

2.1 CREATE Command

Purpose

Creates or adds an AL (Address List) or an RB (Route information Base) object.There are two commands: CREATE_AL and CREATE_RB. These commands areapplicable only to an OCS server.

The commands are available only if the OSI/DIWS stack has been loaded in theOCS Front End.

2.1.1 CRAL

Purpose

Creates or adds a local NSAP represented by an AL (Address List) object.

Syntax

{ CRAL }{ }{ CREATE_AL }

,NAME = ( name-8 )

,NSAP = NSAP_address

,NCC = <OCS server name>

Parameters

NAME name-8: the name of the AL object to be created.

NSAP NSAP address: a code for the local Network ServiceAccess Point (from 0 to 40 digits).

NCC OCS server name.


47 A2 94UC 2-7

EXAMPLE:

S:CRAL NAME=AL01 NSAP=1234567890 NCC=OCS1;

CRAL hh:mm:ss COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-8 47 A2 94UC

2.1.2 CRRB

Purpose

Creates or adds a remote NSAP represented by an RB (Route information Base)object.

Syntax

{ CRRB }{ }{ CREATE_RB }

,IDENT = name-8

,NSAP = NSAP_address

[,NSAP_MASK = NSAP_mask ]

{ SNPA = SNPA_string }{ SNPAMASK = SNPAM_string }{ SNPANET = NET_string }

,IVMO = name-8

,NCC = <OCS server-name>

Parameters

IDENT defines a symbolic name for the RIB entry as a 8character string.

NSAP gives the address of the remote Network ServiceAccess Point to be reached.

NSAP_MASK gives a mask to be applied to the NSAP address, todefine an equivalent class.

SNPA, SNPAMASK defines the SubNetwork Physical Address of the nexthop.

SNPANET either directly (via SNPA_string), or as a mask (viaSNPAM_string) to be applied to the NSAP address, oras a Network Entity Title (NET_string).


47 A2 94UC 2-9

IVMO string of up to 8 bytes, giving the IVMO name relatedto this NSAP. An IVMO is defined using theTCIVMO (Transport Connection Initial ValueManagement Object) CONFIGURATION command orthe CRIVMO command. If no TCIVMO command isused, IVMO_DF is name of the default IVMO.

NCC OCS server name.

EXAMPLE:

CRRB IDENT = RB01 NSAP = xxxx SNPA = yyyy IVMO = IVM1 NCC = OCS1

CRRB hh:mm:ss COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-10 47 A2 94UC

2.2 DBSVR (DEBUG_SERVER)

Purpose

Displays and/or modifies trace parameters and contexts.

The DBSVR command is intended for maintenance purposes only and is reservedfor the Service Center. However, the operator may be requested by the ServiceCenter to enter this command.

For the syntax and parameter description of the DBSVR command, see paragraph10.2.6 DBSVR (DEBUG_SERVER).


47 A2 94UC 2-11

2.3 DELETE Command

Purpose

Deletes or removes an AL (Address List) or an RB (Route information Base)object. There are two commands: DELETE_AL and DELETE_RB. Thesecommands are applicable only to an OCS server.

The commands are available only if the OSI/DIWS stack has been loaded in theOCS Front End.

2.3.1 DLAL

Purpose

Deletes or removes a local NSAP represented by an AL (Address List) object.

Syntax

{ DLAL }{ }{ DELETE_AL }

,NAME1 = name-8

Parameter

NAME1 name-8: the name of the AL object to delete. See theCRAL command.

EXAMPLE:

S:DLAL NAME1=AL01;

DLAL hh:mm:ss COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-12 47 A2 94UC

2.3.2 DLRB

Purpose

Deletes or removes a remote NSAP represented by an RB (Route informationBase) object.

Syntax

{ DLRB }{ }{ DELETE_RB }

,IDENT = name-8

Parameter

See CRRB command.

EXAMPLE:

DLRB IDENT = RB01

DLRB hh:mm:ss COMMAND COMPLETED. 1 OBJECT SELECTEDDMBX Display_MailBox❑


47 A2 94UC 2-13

2.4 DMBX

Purpose

Displays:- a list of users connected to the selected mailbox, and- the server used for each connection.

Syntax

{ DMBX }{ }{ DISPLAY_MAILBOX }

MAILBOX = name-8

Parameter

MAILBOX Mailbox name

EXAMPLE:

S: DMBX $NASF SC48 $NASF MB DYN ON CNCT:0/255 WAITING:0/0

S: DMBX IOF SC48 IOF MB DYN ON CNCT:4/255 WAITING:0/0 BY27 /GUELOU CONNECTED TNS /SIOUX CONNECTED TNS /HORNEBECK CONNECTED TNS /OPPH CONNECTED❑


2-14 47 A2 94UC

2.5 DNET (DISPLAY_NETWORK)

Purpose

Displays the status of selected network objects.

General Syntax

{ DNET }{ }{ DISPLAY_NETWORK }

CLASS = class

[, OBJECT = ( obj-identifier1 [, obj-identifier2 ] ) ]

[, CODE = { SHORT | LONG | HISTORY } ]

[, STATE = { ENBL | LOCK | USED | DOWN | DSBL | SHUT | TEST } ]

[, TYPE = type ]

[, MAP = ( class:obj-identifier1 [, class:obj-identifier2 ] ) ]

[, SYSTEM = { #WSYS | system } ]

[ MORE = { 0 | 1 } ]

[, class-specific parameters ]

NOTE:Detailed syntax for each class is given separately.


47 A2 94UC 2-15

Parameters:

CLASS name taken from a network configuration directive orderived from parameters defined by a networkconfiguration directive.

For the DPS 7, the network is configured byNETGEN.For the CNP 7, the network is configured by CNS 7SYSGEN.For the Datanet, the network is configured by DNSSYSGEN.For OCS Front End, the network is configured usingNETGEN and OCS configuration subfiles ofSYS.DSACONF.For other systems, refer to the appropriate networkingdocumentation.

OBJECT the name of the object uniquely identified within theclass.

Syntax Rules

DNET...OBJECT=name: selects one object

DNET...OBJECT=(name1,name2): selects all objectsfrom name1 up to name2

DNET...OBJECT=(name,*): selects all objects startingfrom name

DNET...OBJECT=(*,name): selects all objects frombeginning up to name

DNET...OBJECT=* or omitted: selects all objectswithin class

CODE determines the information displayed.SHORT: displays the name and principal attributes ofall objects in the class satisfying the selection criteria.LONG: displays detailed attributes of all objects in theclass satisfying the selection criteria.HISTORY: displays statistics of all objects in the classsatisfying the selection criteria.


2-16 47 A2 94UC

STATE describes the state of the objectENBL: object is availableLOCK: object is unavailableUSED: object is being usedDOWN: object has failedDSBL: object inoperable due to lower level failuresSHUT: object taken out of configurationTEST: object under test

TYPE describes the type of object appropriate to its class.

MAP maps the object to a class to which it is associated.

SYSTEM defines the system to which the command is addressed.

MORE 0:default1:display new screen for class-specific parameters ofheterogeneous systems.

class-specific parameters

See the appropriate DNET commands.

NOTE:When the command is sent to a remote system supporting a standard DSACNAD, care must be taken to ensure that this system is able to support thecommand and its corresponding parameters.

The general syntax of the command allows specifying common parameters.MORE allows prompting class-specific parameters which are not described inGCOS 7 commands, if these parameters are needed for a given class.


47 A2 94UC 2-17

The chart below associates GCOS 7 commands and parameters with those of DNSand CNS 7.

GCOS 7Command Parameter

DNET code=SHORT

DNET CODE=LONG

DNET CODE=HISTORY

DNS/CNS 7Command Parameter

UP

OBJECT=name1

OBJECT=(name1,name2)

STATE=state

TYPE=type

MAP=(map1[,map2])

name1

name1/name2

-OS state

-OT type

-OM map1[map2]

For detailed information on DNS and CNS 7 commands and parameters:

• For the Datanet, DNS System Operations,

• For the CNP 7, CNS 7 System Operations.


2-18 47 A2 94UC

2.5.1 DNET AC

Purpose

Displays the status of selected AC (administrative correspondent) objects.

Syntax


CLASS = AC

[, OBJECT = ( name-8 [, name-8 ] ) ]

[, CODE = { SHORT | LONG } ]

[, STATE = { ENBL | LOCK | USED } ]

[, TYPE = { ASF | AUT | MUX | NAD | NCC | NOI } ]

[, MAP = AG : name-8 ]

[, SYSTEM = { #WSYS | name-4 } ]

Parameters: (See DNET Command)

TYPE describes the type of object appropriate to the AC.

ASF: administrative storage facilityAUT: administrative utilityMUX: multiplexorNAD: node administratorNCC: network control centerNOI: network operator interface

MAP maps the AC to its associated AG.


47 A2 94UC 2-19

Response

* SHORT name state type mapping1 :AG ag_name

* LONG name state type mapping1 :AG ag_name max_lgth :maximum length of record code :ASCII or EBCDIC cor_mbx :initiator correspondent mailbox prim_bac :primary or backup correspondent

EXAMPLE:

S: DNET AC; DAAC 13:57:32 --> NAME:LDSALOG STATE:ENBL TYPE:NAD AG:_LDSALOG COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET AC LDSALOG CODE=LONG; GAAC 13:57:55 --> NAME:LDSALOG STATE:ENBL TYPE:NAD AG:_LDSALOG MAX_LGTH:3072 CODE:EBCDIC PRIM_BAC:PRIMARY COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-20 47 A2 94UC

2.5.2 DNET AF

Purpose

Displays the status of selected AF (administrative function) objects.

Syntax


CLASS = AF

[, OBJECT = ( name-8 [, name-8 ] ) ]







TYPE describes the type of object appropriate to the AF.

ASF: administrative storage facilityAUT: administrative utilityMUX: multiplexorNAD: node administratorNCC: network control centerNOI: network operator interface

MAP maps the AF to its AG correspondent.


47 A2 94UC 2-21

Response

* SHORT name state type

* LONG name state type

EXAMPLE:

S: DNET AF; DAAF 13:58:07 --> NAME:LNOI STATE:ENBL TYPE:MUX --> NAME:DSALOG STATE:LOCK TYPE:ASF --> NAME:LNAD STATE:ENBL TYPE:NAD COMMAND COMPLETED. 3 OBJECTS SELECTED

S: DNET AF CODE=LONG; GAAF 13:58:19 --> NAME:LNOI STATE:ENBL TYPE:MUX --> NAME:DSALOG STATE:LOCK TYPE:ASF --> NAME:LNAD STATE:ENBL TYPE:NAD COMMAND COMPLETED. 3 OBJECTS SELECTED❑


2-22 47 A2 94UC

2.5.3 DNET AG

Purpose

Displays the status of selected AG (administrative group) objects.

Syntax


CLASS = AG

[, OBJECT = ( name-8 [, name-8 ] ) ]



[, TYPE = { ASF | AUT | MUX | NAD | NCC | NOI | OP } ]

[, MAP = AF : name-8 ]



TYPE describes the type of object appropriate to the AG:

ASF: administrative storage facilityAUT: administrative utilityMUX: multiplexorNAD: node administratorNCC: network control centerNOI: network operator interfaceOP : operator

MAP maps the AG to its AF correspondent.


47 A2 94UC 2-23

Response

* SHORT name state type mapping1 :AF af_name

* LONG name state type mapping1 :AF af_name initiate :initiator, acceptor or both maxsess :maximum nb of sessions on AG

EXAMPLE:

S: DNET AG; DAAG 13:58:40 --> NAME:LNOI STATE:ENBL TYPE:OP AF:LNOI --> NAME:RMUX STATE:ENBL TYPE:MUX AF:LNOI --> NAME:RLNOI STATE:ENBL TYPE:NAD AF:LNOI --> NAME:_LDSALOG STATE:ENBL TYPE:NAD AF:DSALOG --> NAME:RDSALOG STATE:ENBL TYPE:NAD AF:DSALOG 13:58:40 NAME:RLNAD STATE:ENBL TYPE:AUT AF:LNAD COMMAND COMPLETED. 6 OBJECTS SELECTED

S:DNET AG CODE=LONG; GAAG 13:58:55 --> NAME:LNOI STATE:ENBL TYPE:OP AF:LNOI MAX_SESS:16 --> NAME:RMUX STATE:ENBL TYPE:MUX AF:LNOI INITIATE:BOTH MAX_SESS:32 --> NAME:RLNOI STATE:ENBL TYPE:NAD AF:LNOI INITIATE:BOTH MAX_SESS:32 --> NAME:_LDSALOG STATE:ENBL TYPE:NAD AF:DSALOG MAX_SESS:1 --> NAME:RDSALOG STATE:ENBL TYPE:NAD AF:DSALOG INITIATE:INITIATOR MAX_SESS:32 13:58:40 NAME:RLNAD STATE:ENBL TYPE:AUT AF:LNAD INITIATE:INITIATOR MAX_SESS:32 COMMAND COMPLETED. 6 OBJECTS SELECTED❑


2-24 47 A2 94UC

2.5.4 DNET AL

Purpose

Displays the attributes of selected AL (Address List) objects.

Syntax


CLASS = AL[,OBJECT = ( name-8 [,name-8] )]

[,CODE = { SHORT | LONG } ]

[,NSAP = NSAP_address ]

[,SYSTEM = { #WSYS | name-4 } ]

Parameters (See DNET Command)

NSAP_address a code for the local Network Service Access Point(from 0 to 40 digits).

Response

* SHORT

name : name of the Address List object (up to 8 characters)state: ENBLtype : LOCNSAP : a code for the local Network Service Access Point (from 0 to 40 digits)

* LONG

name : name of the Address List object (up to 8 characters)state: ENBLtype : LOCNSAP : a code for the local Network Service Access Point (from 0 to 40 digits)

Note that the state is always ENBL.


47 A2 94UC 2-25

EXAMPLE:

DNET AL OBJECT=(xxxx,yyyy);

DAAL hh:mm:ss ---> NAME= xxxx STATE:ENBL TYPE:LOC NSAP:xxxxxxxxxxxxxx ---> NAME= yyyy STATE:ENBL TYPE:LOC NSAP:yyyyyyyyyyyyyy COMMAND COMPLETED. 2 OBJECTS SELECTED

DNET AL;

DAAL 17:19:22 ---> NAME= AL02 STATE:ENBL TYPE:LOC NSAP:123456789B ---> NAME= AL04 STATE:ENBL TYPE:LOC NSAP:123456789D ---> NAME= AL06 STATE:ENBL TYPE:LOC NSAP:123456789F ---> NAME= AL01 STATE:ENBL TYPE:LOC NSAP:123456789A ---> NAME= AL03 STATE:ENBL TYPE:LOC NSAP:123456789C COMMAND COMPLETED. 5 OBJECTS SELECTED❑


2-26 47 A2 94UC

2.5.5 DNET CB

Purpose

Displays the status of selected CB (cable) objects.

Syntax


CLASS = { CB | CBL }

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = LAN1 ]

[, MAP = ( PL:name-8 [, PL:name-8 ] ) ]



TYPE LAN1: local area network for the ISL transceiver(applicable to DPS 7000 systems).

MAP maps the CB to its associated remote or local PL(physical link).

Response

* SHORT name type

* LONG name type


47 A2 94UC 2-27

EXAMPLE:

S: DNET CB; DACB 11:25:28 --> NAME:CBL_00 TYPE:LAN1 COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET CB CODE=LONG; GACB 11:25:38 --> NAME:CBL_00 TYPE:LAN1 COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-28 47 A2 94UC

2.5.6 DNET CC

Purpose

Displays the status of selected CC (channel connection) objects.

Syntax


CLASS = CC

[, OBJECT = ( dec-5 [, dec-5 ] ) ]


[, STATE = { ENBL | USED } ]

[, TYPE = { PSI | ISL } ]

[, MAP = ( { CC|CH|LC|SV }:name-8 [, { CC|CH|LC|SV }:name-8 ] ) ]



OBJECT identifies the connection number(s).

TYPE describes the type of object appropriate to the CC.

PSI : peripheral subsystem interface for DatanetISL : internal system link for CNP 7

MAP maps the CC to its associated class.

CC : channel connection (cc index of DNS or CNS 7)CH : channelLC : logical connectionSV : server


47 A2 94UC 2-29

Response

* SHORT index state type mapping1 :CH channel_name (if type = PSI) mapping2 :SV server_name mapping3 :LC index of logical connection

* LONG index state type mapping1 :CH channel_name (if type = PSI) mapping2 :SV server_name mapping3 :LC index of logical connection lcplug :local plug number rmplug :remote plug number in_or_ac :IN (initiator) ; AC (acceptor) cc_dns :CC index of DNS or CNS 7 rmendpnt :remote end point name lcsc :local session control name (PSI) rmsc :remote session control name (PSI)

* HISTORY index rmendpnt :remote endpoint name mapping3 :CC index of channel connection mapping4 :LC index of logical connection in_or_ac :IN (initiator) ; AC (acceptor) rmplug :remote plug number elt :number of letters sent rlt :number of letters received eda :number of data bytes sent rda :number of data bytes received eltx :number of expedited letters sent rltx :number of expedited letters received edax :number of expedited data bytes sent rdax :number of expedited data bytes received


2-30 47 A2 94UC

EXAMPLE:

S: DNET CC OBJECT=(8,53); DACC 14:20:08 --> INDEX:8 STATE:USED TYPE:PSI CH:CC00 SV:BP16 LC:9216 --> INDEX:10 STATE:USED TYPE:PSI CH:CC00 SV:BP16 LC:11264 --> INDEX:35 STATE:USED TYPE:PSI CH:CC00 SV:BP16 LC:5122 --> INDEX:40 STATE:USED TYPE:PSI CH:CC00 SV:BP16 LC:12290 --> INDEX:53 STATE:USED TYPE:PSI CH:CC00 SV:BP16 LC:11268 COMMAND COMPLETED. 5 OBJECTS SELECTED

S: DNET CC OBJECT=40 CODE=LONG; GACC 14:20:24 --> INDEX:40 STATE:USED TYPE:PSI CH:CC00 SV:BP16 CC:0 LC:12290 LCPLUG:40 RMPLUG:1287 IN_OR_AC:AC CC_DNS:51201 RMENDPNT:BPA6 LCSC:BPEA RMSC:BPA6 COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET CC OBJECT=40 CODE=HISTORY; GHCC 14:20:40 --> INDEX:40 RMENDPNT:BPA6 CC:51201 LC:12290 IN_OR_AC:AC RMPLUG:1287 ELT:5 RLT:1 EDA:796 RDA:212 ELTX:0 RLTX:0 EDAX:0 RDAX:0 COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 2-31

2.5.7 DNET CH

Purpose

Displays the status of selected CH (channel) objects.

Syntax


CLASS = CH

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, STATE = { ENBL | LOCK | USED | DOWN | DSBL } ]

[, TYPE = PSI ]

[, MAP=( {CC|CT|SC|SR|SV}:name-8 [, {CC|CT|SC|SR|SV}:name-8 ] ) ]



TYPE PSI for the connection to the Datanet.

MAP maps the CH to its associated class.

CC : channel connectionCT : controllerSC : session controlSR : session routeSV : server


2-32 47 A2 94UC

Response

* SHORT name state type mapping2 :CT controller_name server :server_name

* LONG name state type mapping2 :CT controller_name watch :watchdog delay survey :ON|OFF watchdog efficiency maxcn :maximum number of connections cnx_nb :current number of connections maxch :maximum number of logical channels maxinch :maximum number of input channels server :server_name

EXAMPLE:

S: DNET CH; DACH 14:21:05 --> NAME:CC00 STATE:USED TYPE:PSI CT:CC00 SERVER:BP16 COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET CH CODE=LONG; GACH 14:21:14 --> NAME:CC00 STATE:USED TYPE:PSI CT:CC00 WATCH:0 SURVEY:ON MAXCN:2000 CNX_NB:12 MAXCH:16 MAXINCH:8 SERVER:BP16 COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 2-33

2.5.8 DNET CT

Purpose

Displays the status of selected CT (controller) objects.

CT is the addition of LCT and RCT.

Syntax for LCT (Local Controller)


CLASS = { LCT | CT }

[, OBJECT = ( name-8 [, name-8 ] ) ]



[ { TYPE=ISL [,MAP=({ PL|SV }:name-8 [,{ PL|SV }:name-8 ] ) ] } ][,{ TYPE=PSI [,MAP=({ CH|SV }:name-8 [,{ CH|SV }:name-8 ] ) ] } ][ { TYPE=FCP [,MAP={ PL:name-8 | SV:name-8 }]

[, VENUE = PR ]



TYPE ISL for ISL connection: mapping to PL or SVPSI for Datanet connection: mapping to CH or SVFCP for OCS connection

MAP maps the LCT to its associated class.

CH: channel for PSI typePL: physical link for ISL or FCP typeSV: server for ISL, PSI, and FCP types


2-34 47 A2 94UC

VENUE specifies that the selected object is proper (PR)meaning local as opposed to image meaning remote.

DNET CLASS=LCT ...

is equivalent to

DNET CLASS=CT VENUE=PR ...

Response for LCT (type ISL)

* SHORT name state type open_md :open mode (manual or automatic)

* LONG name state type rmlsap :remote lsap isolsap :iso lsap open_md :open mode (manual or automatic) loopmode :loop mode rminit :remote initialization lcload :local loading reset :remote reset

Response for LCT (type PSI)


* LONG name state type loopmode :loop mode rminit :remote initialization lcload :local loading maxcn :maximum number of connections maxch :maximum number of logical channels maxinch :maximum number of input channels watch :watchdog delay


47 A2 94UC 2-35

Response for LCT (type FCP)

* SHORT

name state type

* LONG name state type maxcn watch (in milliseconds)

EXAMPLE:

S: DNET LCT; DACT 13:22:01 --> NAME:EA01 STATE:ENBL TYPE:ISL OPEN_MD:AUTOMATIC 13:22:01 NAME:CC01 STATE:USED TYPE:PSI --> NAME:CC02 STATE:DSBL TYPE:PSI COMMAND COMPLETED. 3 OBJECTS SELECTED

S:DNET LCT CODE=LONG; GACT 13:22:13 --> NAME:EA01 STATE:ENBL TYPE:ISL ISOLSAP:I:L:20 OPEN_MD:AUTOMATIC LOOPMODE:LOOP2 RMINIT:1 LCLOAD:ON RESET:OFF 13:22:13 NAME:CC01 STATE:USED TYPE:PSI LOOPMODE:LOOP2 RMINIT:1 LCLOAD:ON MAXCN:2000 MAXCH:16 MAXINCH:8 WATCH:0 --> NAME:CC02 STATE:DSBL TYPE:PSI LOOPMODE:LOOP2 RMINIT:1 LCLOAD:ON MAXCN:2000 MAXCH:16 MAXINCH:8 WATCH:0 COMMAND COMPLETED. 3 OBJECTS SELECTED

S: dnet ct ea51 type=fcp code=long GACT 15:07:56 --> NAME:EA51 STATE:ENBL TYPE:FCP MAXCN:2000 WATCH:10176 COMMAND COMPLETED. 1 OBJECT SELECTEDS: dnet ct ea51 type=fcp DACT 15:08:19 --> NAME:EA51 STATE:ENBL TYPE:FCP COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-36 47 A2 94UC

Syntax for RCT (Remote Controller)


CLASS = { RCT | CT }

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = ISL ]

[, MAP = ( PL : name-8 ) ]

[, VENUE = IM ]



TYPE ISL for the connection to the CNP 7.

MAP maps the RCT to its PL (physical link).

VENUE specifies that the selected object is image (IM)meaning remote as opposed to proper meaning local.

DNET CLASS=RCT ...

is equivalent to

DNET CLASS=CT VENUE=IM ...


47 A2 94UC 2-37

Response

* SHORT name state type rmload :remote loading capability

* LONG name state type rmload :remote load capability loopmode :loop mode

EXAMPLE:

S: DNET RCT; DACT 13:22:43 --> NAME:CT_BL05 STATE:ENBL TYPE:ISL RMLOAD:ON --> NAME:CT_BL04 STATE:ENBL TYPE:ISL RMLOAD:ON --> NAME:RCT1MATH STATE:ENBL TYPE:ISL RMLOAD:ON --> NAME:CT_BL17 STATE:ENBL TYPE:ISL RMLOAD:ON --> NAME:CT_BL36 STATE:ENBL TYPE:ISL RMLOAD:ON --> NAME:CT_BL37 STATE:ENBL TYPE:ISL RMLOAD:ON --> NAME:CT_BL38 STATE:ENBL TYPE:ISL RMLOAD:ON --> NAME:CT_BL13 STATE:ENBL TYPE:ISL RMLOAD:ON --> NAME:CT_DSA5 STATE:ENBL TYPE:ISL RMLOAD:ON COMMAND COMPLETED. 9 OBJECTS SELECTED

S: DNET CT OBJECT=CT_BL37 CODE=LONG VENUE=IM; GACT 13:24:53 --> NAME:CT_BL37 STATE:ENBL TYPE:ISL RMLOAD:ON LOOPMODE:NONE RESET:ON COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-38 47 A2 94UC

2.5.9 DNET FL

Purpose

Displays the status of selected FL (filter) objects.

Syntax


CLASS = FL

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, STATE = { ENBL | LOCK } ]

[, TYPE = { IN | OUT } ]

[ { AF : name-8 [, { AC | AG } : name-8 ] } ][, MAP = ( { } ) ][ { AC | AG | LG | OP } : name-8 [, AF : name-8 } ]

[, LOGIC = { INCL | EXCL | OBLI } ]



TYPE IN for input, OUT for output.

LOGIC INCL: inclusive (select if criteria match)EXCL: exclusive (reject if criteria match)OBLI: obligatory (reject if criteria do not match)

MAP maps the FL to its associated class.

AC : administrative correspondentAF : administrative functionAG : administrative groupLG : administrative logOP : operator


47 A2 94UC 2-39

Response

* SHORT name state type :IN or OUT mapping1 :AC or AG or LG or OP mapping2 :AC or AG or LG or OP logic :INCLUSIVE or EXCLUSIVE or OBLIGATORY

* LONG name state type :IN or OUT mapping1 :AC or AG or LG or OP mapping2 :AC or AG or LG or OP logic :INCLUSIVE or EXCLUSIVE or OBLIGATORY l_domain :low domain; if no value is specified, 256 is displayed for exclusive filters 0 for inclusive and obligatory filters h_domain :high domain; if no value is specified, 256 is displayed for exclusive filters 4 for inclusive and obligatory filters l_power :low power; if no value is specified, 256 is displayed for exclusive filters 0 for inclusive and obligatory filters h_power :high power; if no value is specified, 256 is displayed for exclusive filters 3 for inclusive and obligatory filters l_class :low class; if no value is specified, 256 is displayed for exclusive filters 1 for inclusive and obligatory filters h_class :high class; if no value is specified, 256 is displayed for exclusive filters 255 for inclusive and obligatory filters l_code :low code; if no value is specified, 256 is displayed for exclusive filters 1 for inclusive and obligatory filters h_code :high code; if no value is specified, 256 is displayed for exclusive filters 255 for inclusive and obligatory filters l_level :low level; if no value is specified, 256 is displayed for exclusive filters 0 for inclusive and obligatory filters h_level :high level; if no value is specified, 256 is displayed for exclusive filters 255 for inclusive and obligatory filters


2-40 47 A2 94UC

EXAMPLE:

S: DNET FL FLLOG000; DAFL 14:21:59 --> NAME:FLLOG000 STATE:ENBL TYPE:OU LG:DSALOG LOGIC:INCLUSIVE COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET FL FLLOG000 CODE=LONG; GAFL 14:22:10 --> NAME:FLLOG000 STATE:ENBL TYPE:OU LG:DSALOG LOGIC:INCLUSIVE L_DOMAIN:0 H_DOMAIN:4 L_POWER:0 H_POWER:3 L_CLASS:1 H_CLASS:255 L_CODE:1 H_CODE:255 L_LEVEL:0 H_LEVEL:255 COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 2-41

2.5.10 DNET ID

Purpose

Displays the status of selected ID (iso session control) objects.

Syntax


CLASS = ID

[, OBJECT = ( name-4 [, name-4 ] ) ]




OBJECT If two object values are specified, they must beidentical.


2-42 47 A2 94UC

Response

* SHORT name state :used or enabled fc_unit :functional units supported prtc_ver :protocol version sendsegm :sending segmentation supported smaxseg :sending max TSDU size if segmented smaxunsg :sending max TSDU size if not segmented recvsegm :receiving segmentation supported rmaxseg :receiving max TSDU size if segmented rmaxunsg :receiving max TSDU size if not segmented e_concat :extended concatenation supported max_sc :max number of session connections

* LONG name state :used or enabled fc_unit :functional units supported prtc_ver :protocol version sendsegm :sending segmentation supported smaxseg :sending max TSDU size if segmented smaxunsg :sending max TSDU size if not segmented recvsegm :receiving segmentation supported rmaxseg :receiving max TSDU size if segmented rmaxunsg :receiving max TSDU size if not segmented e_concat :extended concatenation supported max_sc :max number of session connections

EXAMPLE:

S: DNET ID; DAID 11:28:15 --> NAME:BL03 STATE:ENBL FC_UNIT:07FF PRTC_VER:1 SENDSEGM:YES SMAXSEG:4096 SMAXUNSG:0 RECVSEGM:YES RMAXSEG:4096 RMAXUNSG:0 E_CONCAT:YES MAX_SC:5000 COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET ID CODE=LONG; GAID 11:28:15 --> NAME:BL03 STATE:ENBL FC_UNIT:07FF PRTC_VER:1 SENDSEGM:YES SMAXSEG:4096 SMAXUNSG:0 RECVSEGM:YES RMAXSEG:4096 RMAXUNSG:0 E_CONCAT:YES MAX_SC:5000 COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 2-43

2.5.11 DNET IS

Purpose

Displays the status of selected IS (iso session connection) objects.

Syntax


CLASS = IS

[, OBJECT = ( dec-5 [, dec-5 ] ) ]


[, STATE = { ENBL | LOCK | USED | DOWN } ]

[, TYPE = { INT | EXT } ]

[, MAP =( { CC | ID | TC }:name-8 [,{ CC | ID | TC }:name-8 ] ) ]

[, ENDS = { 1 | 2 } ]



TYPE INT : internal, EXT : external


CC : channel connection, only if remoteID : iso session controlTC : transport connection, only if remote

ENDS 1: default, selects only the initiator's end of the localconnection.2: selects both ends of the local connection.


2-44 47 A2 94UC

Response

* SHORT and * LONG index type :internal or external mapping1 :ID mapping3 :CC or TC (only if remote) initresp :initiator or responder of connection fct_unit :functional units on the connection prtc_ver :protocol version sendsegm :sending segmentation selected smaxtsdu :maximum size of TSDU sent recvsegm :receive segmentation selected rmaxtsdu :maximum size of TSDU received e_concat :extended concatenation selected prv_prty :private priority pair_idx :index of opposite end (local connection) calling :calling session selector called :called session selector data_tok :data token assignment rels_tok :release token assignment minor_tk :minor token assignment major_tk :major token assignment

* HISTORY index ss_ctrl :iso session control mapping3 :CC or TC (only if remote) initresp :initiator or responder of connection pair_idx :index of opposite end (local connection) edu :number of SPDUs sent rdu :number of SPDUs received edo :number of bytes sent rdo :number of bytes received


47 A2 94UC 2-45

EXAMPLE:

S: DNET IS OBJECT=25600; DAIS 10:07:53 --> INDEX:25600 TYPE:EXT ID:BPC6 CC:10 INITRESP:RESPONDER FCT_UNIT:0002 PRTC_VER:1 SENDSEGM:YES SMAXTSDU:2992 RECVSEGM:YES RMAXTSDU:2992 E_CONCAT:NO PRV_PRTY:000E CALLING:49495341 CALLED:41495341 DATA_TOK:0 RELS_TOK:0 MINOR_TK:0 MAJOR_TK:0 AUTO_STA:713 COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET IS 25600 CODE=LONG; GAIS 10:08:26 --> INDEX:25600 TYPE:EXT ID:BPC6 CC:10 INITRESP:RESPONDER FCT_UNIT:0002 PRTC_VER:1 SENDSEGM:YES SMAXTSDU:2992 RECVSEGM:YES RMAXTSDU:2992 E_CONCAT:NO PRV_PRTY:000E CALLING:49495341 CALLED:41495341 DATA_TOK:0 RELS_TOK:0 MINOR_TK:0 MAJOR_TK:0 AUTO_STA:713 COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET IS 25600 CODE=HISTORY; GHIS 10:15:18 --> INDEX:25600 SS_CTRL:BPC6 CC:3 INITRESP:INITIATOR EDU:0 RDU:1 EDO:0 RDO:0 COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-46 47 A2 94UC

2.5.12 DNET LC

Purpose

Displays the status of selected LC (logical connection) objects.

Syntax


CLASS = LC

[, OBJECT = ( dec-5 [, dec-5 ] ) ]




[, MAP =( {CC|LM|RM|SS|TC}:name-8 [,{CC|LM|RM|SS|TC}:name-8 ] ) ]

[, ENDS = { 1 | 2 } ]





CC : channel connection (if remote LC)LM : local mailboxRM : remote mailboxSS : sessionTC : transport connection (if remote LC)

ENDS 1: default, selects only the initiator's end of the localconnection.2: selects both ends of the local connection.


47 A2 94UC 2-47

Response

* SHORT index state type :internal or external mapping1:LMB (local mailbox) mapping2:RMB (remote mailbox) mapping3:CC or TC (only for remote LC) pair_idx:index of opposite end (local connection)

* LONG index state type :internal or external mapping1:LMB (local mailbox) mapping2:RMB (remote mailbox) mapping3:CC or TC (only for remote LC) pair_idx:index of opposite end (local connection) lc_id :dialog protocol logical connection identifier m_subch :maximum number of subchannels s_ltsize:maximum size of sent letters r_ltsize:maximum size of received letters m_unrsru:maximum unreleased SRU mode :TWA, TWS or 1WAY recover :recovery capability resync :resynchronization capability telegram:telegram capability re_subch:release subchannels in_or_ac:initiator or acceptor of connection i_block :input blocking capability

* HISTORY index local_mb:LMB (local mailbox) rmt_mb :RMB (remote mailbox) mapping3:CC or TC (only for remote LC) ss_id :supported session in_or_ac:initiator or acceptor of connection lc_id :dialog protocol logical connection identifier eda :number of application data characters sent esy :number of system characters sent ers :number of record segments sent erc :number of records sent elt :number of letters sent rda :number of application data characters recd rsy :number of system characters received rrs :number of record segments received rrc :number of records received rlt :number of letters received


2-48 47 A2 94UC

EXAMPLE:

S: DNET LC OBJECT=(15364,*); DALC 14:24:49 --> INDEX:15364 STATE:USED TYPE:EXT LMB:BPA6IOF RMB:BP03V272 CC:57 --> INDEX:16388 STATE:USED TYPE:EXT LMB:BPA6IOF RMB:BP03V272 CC:57 --> INDEX:17413 STATE:USED TYPE:EXT LMB:BPA6IOF RMB:BP05V672 CC:77 COMMAND COMPLETED. 3 OBJECTS SELECTED

S: DNET LC OBJECT=(15364,*) CODE=LONG; GALC 14:25:10 --> INDEX:15364 STATE:USED TYPE:EXT LMB:BPA6IOF RMB:BP03V272 CC:57 LC_ID:1006895105 M_SUBCH:1 S_LTSIZE:2992 R_LTSIZE:2992 M_UNRSRU:0 MODE:TWA RECOVER:NO RESYNC:NO TELEGRAM:YES RE_SUBCH:NO IN_OR_AC:AC I_BLOCK:NO --> INDEX:16388 STATE:USED TYPE:EXT LMB:BPA6IOF RMB:BP07VB43 CC:76 LC_ID:1074003969 M_SUBCH:1 S_LTSIZE:2992 R_LTSIZE:2992 M_UNRSRU:0 MODE:TWA RECOVER:NO RESYNC:NO TELEGRAM:YES RE_SUBCH:NO IN_OR_AC:AC I_BLOCK:NO --> INDEX:17413 STATE:USED TYPE:EXT LMB:BPA6IOF RMB:BP05V672 CC:77 LC_ID:1141178369 M_SUBCH:1 S_LTSIZE:2992 R_LTSIZE:2992 M_UNRSRU:0 MODE:TWA RECOVER:NO RESYNC:NO TELEGRAM:YES RE_SUBCH:NO IN_OR_AC:AC I_BLOCK:NO COMMAND COMPLETED. 3 OBJECTS SELECTED

S: DNET LC OBJECT=(15364,*) CODE=HISTORY; GHLC 14:25:37 --> INDEX:15364 LMB:BPA6IOF RMB:BP03V272 CC:57 SS:15364 IN_OR_AC:AC LC_ID:1006895105 EDA:10497 ESY:574 ERS:74 ERC:74 ELT:75 RDA:627 RSY:442 RRS:51 RRC:51 RLT:55 --> INDEX:16388 LMB:BPA6IOF RMB:BP07VB43 CC:76 SS:16388 IN_OR_AC:AC LC_ID:1074003969 EDA:2291 ESY:280 ERS:25 ERC:25 ELT:26 RDA:159 RSY:238 RRS:18 RRC:18 RLT:19 --> INDEX:17413 LMB:BPA6IOF RMB:BP05V672 CC:77 SS:17413 IN_OR_AC:AC LC_ID:1141178369 EDA:41098 ESY:976 ERS:141 ERC:141 ELT:142 RDA:203 RSY:408 RRS:46 RRC:46 RLT:48 COMMAND COMPLETED. 3 OBJECTS SELECTED❑


47 A2 94UC 2-49

2.5.13 DNET LG

Purpose

Displays the status of selected LG (administrative log) objects.

Syntax


CLASS = LG

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, STATE = { ENBL | LOCK | DOWN } ]

[, MAP = AF : DSALOG ]



MAP AF DSALOG


2-50 47 A2 94UC

Response

* SHORT name state mapping1 :AF

* LONG name state mapping1 :AF cur_file :current file name nxt_file :next file name max_rec :maximum number of records max_oct :maximum number of bytes

EXAMPLE:

S: DNET LG; DALG 14:27:34 --> NAME:DSALOG STATE:ENBL AF:DSALOG COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET LG CODE=LONG; GALG 14:27:47 --> NAME:DSALOG STATE:ENBL AF:DSALOG CUR_FILE:SYS.DSALOG2 NXT_FILE:SYS.DSALOG1 MAX_REC:5004 MAX_OCT:1000800 COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 2-51

2.5.14 DNET MB

Purpose

Displays the status of selected MB (mailbox) objects.

Syntax


CLASS = MB

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, STATE = { ENBL | USED | SHUT | DSBL } ]

[, MAP = ( { LC | WS } : name-8 [, { LC | WS } : name-8 ] ) ]

[, VENUE = { PR | IM } ]



MAP maps the MB to its associated class:

LC: logical connectionWS: workstation

VENUE specifies that only proper (PR) meaning local or image(IM) meaning remote, mailboxes are to be selected.


2-52 47 A2 94UC

Response

* SHORT name state mapping1 :WS workstation_name

* LONG name state mapping1 :WS workstation_name max_lc :maximum number of logical connections user_nb :number of users on the mailbox

EXAMPLE:

S: DNET MB OBJECT=IOF; DAMB 14:28:51 --> NAME:IOF STATE:USED WS:IOF COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET MB IOF CODE=LONG; GAMB 14:29:02 --> NAME:IOF STATE:USED WS:IOF MAX_LC:255 USER_NB:14 COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 2-53

2.5.15 DNET NK

Purpose

Displays the attributes of selected NK (Internet Network Activity) objects.

Syntax


CLASS = NK

[, OBJECT = ( dec-5 [,dec-5] )]


[, STATE = USED ]

[, TYPE = IP ]

[, MAP = TS : name_8]

[, SYSTEM = { #WSYS | name-4 }]


TYPE = IP (Internet Protocol)


2-54 47 A2 94UC

Response

* SHORT

indexstate : USEDtype : IPmapping1 : TS transport station name

* LONGindexstate : USEDtype : IPmapping1 : TS transport station name

* HISTORY

indexmapping1 : TS transport station nameETU: number of PDUs data requests emitted by transportRTU: number of PDUs data indications received by transportFSU: number of subnetwork data indications forwardedRDI: number of data units discarded due to congestionREA: number of address error class report PDUs receivedRES: number of source routing class error report PDUs receivedREL: number of lifetime class error report PDUs receivedRED: number of PDUs discard class error reports receivedRER: number of re-assembly class error reports received

EXAMPLE:

DNET NK OBJECT=2;

DANK hh:mm:ss---> INDEX: 2 STATE:USED TYPE:IP TS:NCC2COMMAND COMPLETED. 1 OBJECT SELECTED

DNET NK OBJECT=2 CODE=LONG;

GANK hh:mm:ss---> INDEX: 2 STATE:USED TYPE:IP TS:NCC2COMMAND COMPLETED. 1 OBJECT SELECTED

DNET NK CODE=HISTORY;

GHNK 17:25:28---> INDEX: 2 TS:NCC2 ETU:10042 RTU:3175 FSU:0 RDI:0 REA:0 RES:0 REL:0 RED:0 RER:0COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 2-55

2.5.16 DNET NR

Purpose

Displays the status of selected NR (network route) objects.

Syntax


CLASS = NR

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, STATE = { ENBL | DSBL } ]

[, TYPE = PTPT ]

[, MAP = ( { PL | TS } : name-8 [, { PL | TS } : name-8 ] ) ]



TYPE PTPT

MAP maps the NR to its associated class:

PL: physical linkTS: transport station


2-56 47 A2 94UC

Response

* SHORT name state type mapping1 :TS rts_name

* LONG name state type mapping1 :TS rts_name rel_prty :nr relative priority tc_nb :number of transport connections

EXAMPLE:

S: DNET NR; DANR 11:29:46 --> NAME:BL05 STATE:ENBL TYPE:PTPT TS:BL05 --> NAME:BL04 STATE:ENBL TYPE:PTPT TS:BL04 --> NAME:BL17 STATE:ENBL TYPE:PTPT TS:BL17 --> NAME:BL36 STATE:ENBL TYPE:PTPT TS:BL36 --> NAME:BL37 STATE:ENBL TYPE:PTPT TS:BL37 --> NAME:BL38 STATE:ENBL TYPE:PTPT TS:BL38 --> NAME:BL13 STATE:ENBL TYPE:PTPT TS:BL13 --> NAME:DSA5 STATE:ENBL TYPE:PTPT TS:DSA5 COMMAND COMPLETED. 8 OBJECTS SELECTED

S: DNET NR OBJECT=BL37 CODE=LONG; GANR 11:36:01 --> NAME:BL37 STATE:ENBL TYPE:PTPT TS:BL37 COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 2-57

2.5.17 DNET OP

Purpose

Displays the status of selected OP (operator) objects.

Syntax


CLASS = OP

[, OBJECT = ( name-8 [, name-8 ] ) ]



[, TYPE = OP ]

[, MAP = ( AG : name-8 , [ AG : name-8 ] ) ]



TYPE OP

MAP maps the OP to its associated AG correspondent.

Response

* SHORT and * LONG name state type mapping1 :AG administrative correspondent name ron_vl :run occurrence number


2-58 47 A2 94UC

EXAMPLE:

S: DNET OP; DAOP 15:53:56 --> NAME:OPERATOR STATE:LOCK TYPE:OP AG:LNOI RON_VL:13 --> NAME:OPER1 STATE:USED TYPE:OP AG:LNOI RON_VL:24 COMMAND COMPLETED. 2 OBJECTS SELECTED

S: DNET OP CODE=LONG; GAOP 15:54:31 --> NAME:OPERATOR STATE:LOCK TYPE:OP AG:LNOI RON_VL:13 --> NAME:OPER1 STATE:USED TYPE:OP AG:LNOI RON_VL:24 COMMAND COMPLETED. 2 OBJECTS SELECTED❑


47 A2 94UC 2-59

2.5.18 DNET PC

Purpose

Displays the attributes of selected PC (physical connection) objects.

If it is an RPL on the ISL, the command issues a status request on the cable to theRPL and displays the answer to the request. If it is an RPL of the CNP 7, thecommand issues a hardware configuration request and displays the answer.

Syntax


CLASS = PC

CODE = HISTORY

MAP = PL : name-8



MAP maps the PC to its associated local or remote PL(physical link).With OCS there is only one PL which is always a localPL.

The old TYPE parameter is obsolete.


2-60 47 A2 94UC

Response

* HISTORY (if mapped to an LPL on Ethernet)lcendpnt :PL local pl nameepd :number of PDUs correctly senteda :number of bytes sentrpd :number of PDUs correctly receivedrda :number of bytes receivedxhw :number of hardware faults signalled by controllerrer :number of PDUs received incorrectlyeer :number of PDUs sent incorrectlyeby :number of transmits deferred due to medium busyebt :accumulated time of transmits deferred in tenths of a secondral :number of misaligned PDUs discardedrcl :number of collisions interfering with receptionecf :number of PDUs transmitted resulting in collisionrln :number of received PDUs discarded due to length errorrls :number of frames lost on receiveech :number of link frames receivedsy_ident :system internal identificationsy_state :system internal status

* HISTORY (if mapped to an RPL on Ethernet)rmendpnt :PL remote pl nameepd :number of PDUs correctly sentrpd :number of PDUs correctly receivedrer :number of PDUs received incorrectlyral :number of misaligned PDUs discardedrcl :number of collisions interfering with receptionech :number of link frames receivedsy_ident :system internal identificationsy_state :system internal statuscnp_dial :cnp 7 dialog in progresslcload :local loading in progresscnp_lan :cnp 7 lan dialog in progress


47 A2 94UC 2-61

* HISTORY (if mapped to an LPL on FDDI)

index :lcendpnt : PL local nameEPD : Number of frames sent without errorEDA : Number of bytes sent without errorRPD : Number of frames received without errorRDA : Number of bytes received without errorROR : Number of aborted framesRFC : Number of frames received with FCS errorXHW : Number of hardware errorEER : Number of lost frames in transmit modeRSC : Number of lost frames in receive modeRLN : Number of frames received with a length > 4500 bytesNUT : Number of times where the ring became operationalPCFNF : Number of frames seen on the networkPCFLF : Number of lost frames on the networkPCFFE : Number of frames in error on the network

EXAMPLE:

S: DNET PC CODE=HISTORY MAP=PL:BL37; GHPC 11:38:50 --> PL:BL37 EPD:0 RPD:0 RDA:0 RER:0 RAL:0 RCL:0 RLS:0 ECH:0 SY_IDENT:0 SY_STATE:OPER STATE CNP_DIAL:NO LCLOAD:NO CNP_LAN:NO COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET PC TYPE = FDDI CODE = HISTORY MAP = PL:EA82;

GHPC 15:53:36 ---> INDEX:2 PL:EA82 EPD:236136 EDA:56454411 RPD:236608 RDA:12147555 ROR:0 RFC:0 XHW:0 EER:0 RSC:0 RLN:0 NUT:1 PCFNF:486296 PCFLF:0 PCFFE:0 COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-62 47 A2 94UC

2.5.19 DNET PL

Purpose

Displays the status of selected PL (physical link) objects.

PL is the addition of LPL and RPL.

RPL is a TNS object only. If TNS exists but has not been started, the commandcannot be executed on PL.

Syntax for LPL (Local Physical Link)


CLASS = { LPL | PL }

[, OBJECT = ( name-8 [, name-8 ] ) ]



[ = {CSMA [,MAP =({CB|CT|NR}:name-8 [,{CB|CT|NR}:name-8])]}][, TYPE = { }][ = {FDDI [,MAP = CT:name-8 ] }]

[, VENUE = PR ]



TYPE CSMA or FDDI

MAP maps the LPL to its associated class.

CB : cableCT : local controller (LCT)NR : network route


47 A2 94UC 2-63

VENUE specifies that the selected object is proper meaninglocal as opposed to image (IM) meaning remote.

DNET CLASS=LPL ...

is equivalent to

DNET CLASS=PL VENUE=PR ...

Response for LPL (type CSMA)

* SHORT name state type :CSMA mapping1:CT controller_name mapping2:CB cable_name venue :proper (local) open_md :open mode (automatic or operator) access :I/O (input and output) or IN or OU

* LONG name state type :CSMA mapping1:CT controller_name mapping2:CB cable_name venue :proper (local) open_md :open mode (automatic or operator) access :I/O (input and output) or IN or OU iaddr :individual ethernet address raddr1 :remote individual ethernet address raddr2 . . raddr12 maddr1 :multicast ethernet address maddr2 . . maddr8 foreign :0 or 1 foreign frame acceptance faddr1 :foreign multicast ethernet address faddr2 . . faddr10


2-64 47 A2 94UC

Response for LPL (type FDDI)

* SHORT

namestatetype : FDDImapping1 : CT controller_namevenue : proper (local)

* LONG

namestatetype : FDDImapping1 : CT controller_namevenue : proper (local)iaddr : individual Ethernet addressmaddr1 : multicast Ethernet addressmaddr2 : multicast Ethernet address ... : .....maddr8 : multicast Ethernet address

EXAMPLE:

S: DNET PL VENUE=PR; DAPL 15:29:46 --> NAME:PL503C03 STATE:ENBL TYPE:CSMA CT:EA01 CB:CBL_00 VENUE:PROPER OPEN_MD:AUTOMATIC ACCESS:I/O COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET LPL CODE=LONG; GAPL 15:29:59 --> NAME:PL503C03 STATE:ENBL TYPE:CSMA CT:EA01 CB:CBL_00 VENUE:PROPER IADDR:G:O8-00-38-50-3C-03 OPEN_MD:AUTOMATIC ACCESS:I/O RADDR1:08-00-38-50-00-00:08-00-38-6F-FF-FF MADDR1:G:09-00-38-10-00-00 MADDR2:G:09-00-38-20-00-00 COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET PL TYPE=FDDI;

DAPL hh:mm:ss--> NAME:EA01 STATE:ENBL TYPE:FDDI CT:EA01 VENUE : PROPERCOMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 2-65

Syntax for RPL (Remote Physical Link)


CLASS = { RPL | PL }

[, OBJECT = ( name-8 [, name-8 ] ) ]



[, TYPE = CSMA ]

[, MAP = ( { CB | CT | NR }:name8 [,{ CB | CT | NR }:name8 ] ) ]

[, VENUE = IM ]



TYPE CSMA

MAP maps the RPL to its associated class.CB : cableCT : remote controller (RCT)NR : network route


DNET CLASS=RPL ...

is equivalent to

DNET CLASS=PL VENUE=IM ...


2-66 47 A2 94UC

Response for RPL

* SHORT name state type :CSMA mapping1 :CT controller_name mapping2 :CB cable_name venue :image (remote)

* LONG name state type :CSMA mapping1 :CT controller_name mapping2 :CB cable_name venue :image (remote) access :I/O (input and output) or IN or OU iaddr :individual ethernet address

EXAMPLE:

S: DNET RPL OBJECT=(BL17,*); DAPL 15:51:13 --> NAME:BL17 STATE:ENBL TYPE:CSMA CT:CT_BL17 CB:CBL_00 VENUE:IMAGE 15:51:13 NAME:BL36 STATE:ENBL TYPE:CSMA CT:CT_BL36 CB:CBL_00 VENUE:IMAGE 15:51:13 NAME:BL37 STATE:ENBL TYPE:CSMA CT:CT_BL37 CB:CBL_00 VENUE:IMAGE 15:51:13 NAME:BL38 STATE:ENBL TYPE:CSMA CT:CT_BL38 CB:CBL_00 VENUE:IMAGE 15:51:13 NAME:BL13 STATE:ENBL TYPE:CSMA CT:CT_BL13 CB:CBL_00 VENUE:IMAGE 15:51:13 NAME:DSA5 STATE:ENBL TYPE:CSMA CT:CT_DSA5 CB:CBL_00 VENUE:IMAGE COMMAND COMPLETED. 6 OBJECTS SELECTED

S: DNET RPL BL37 LONG; GAPL 15:51:32 --> NAME:BL37 STATE:ENBL TYPE:CSMA CT:CT_BL37 CB:CBL_00 VENUE:IMAGE IADDR:G:08-00-38-50-3C-37 COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 2-67

2.5.20 DNET QD

Purpose

Displays the status of selected QD (queue) objects.

Syntax


CLASS = QD

[ { prog-q-char-8 } [ { prog-q-char-8 } ] ][ { } [ { } ] ][, OBJECT = ( { user-q-char-12 } [, { user-q-char-12 } ] ) ][ { } [ { } ] ][ { dsa-q-char-12 } [ { dsa-q-char-12 } ] ]


[, STATE = { ENBL | DSBL | USED } ]

[, TYPE = { PROG | USER | DSA } ]

[, MAP = MB : name-8 ]



2-68 47 A2 94UC


OBJECT the maximum number of alphanumeric charactersdepends on the TYPE of queue.

DSA-terminal-queue used to send messages to anapplication over either a secondary network or aprimary network connecting DSA remote systems.Since the total string including, is limited to 12alphanumeric characters, the following restrictions areimposed:

either rsys-name (name-4) is reduced to 3alphanumeric characters if mailbox-name occupies themaximum of 8 alphanumeric characters.

or, mailbox-name (name-8) is reduced to 7alphanumeric characters rsys-name occupies themaximum of 4 alphanumeric characters.

TYPE PROG for program queue.USER for userid queue.DSA for a DSA queue in a primary network.

MAP maps the program-queue to its associated MB(mailbox).


47 A2 94UC 2-69

Response for QD of PROG Type

* SHORT name state :ENBL or USED or DSBL type :PROGRAM mapping1:MB mailbox_name nb_msg :number of messages free :percentage of free space in the queue

* LONG name state :ENBL or USED or DSBL type :PROGRAM mapping1:MB mailbox_name nb_msg :number of messages free :percentage of free space in the queue int_type:internal queue type (MEMORY or DISK) qmaint :YES or NO break :YES or NO share :YES or NO protocol:TWA or TWS initjcl :name of application for automatic startup


2-70 47 A2 94UC

Response for QD of DSA or USER Type

* SHORT name state :ENBL or USED or DSBL type :USERID or DSA nb_msg :number of messages free :percentage of free space in the queue

* LONG name state :ENBL or USED or DSBL type :USERID or DSA nb_msg :number of messages free :percentage of free space in the queue int_type:internal queue type (MEMORY or DISK) qmaint :YES or NO inmode :NORMAL or MARKED or UNEDITED outmode :NORMAL or UNEDITED blocking:YES or NO nblines :maximum number of lines which can be sent linelg :logical line length index :index of program queue associated to terminal queue trspt :YES or NO kbco :KCO or BCO control code (BSC2780 protocol) bscack :YES or NO cnx_stat:0 or 1 or 2 or 3 or 4


47 A2 94UC 2-71

EXAMPLE:

S: DNET QD; DAQD 14:49:36 --> NAME:QUEUE1 STATE:ENBL TYPE:PROGRAM MB:QUEUE1 NB_MSG:0 FREE:100 --> NAME:QUEUE2 STATE:ENBL TYPE:PROGRAM MB:QUEUE2 NB_MSG:0 FREE:100 --> NAME:QUEUE3 STATE:ENBL TYPE:PROGRAM MB:QUEUE3 NB_MSG:0 FREE:100 --> NAME:QUEUE4 STATE:ENBL TYPE:PROGRAM MB:QUEUE4 NB_MSG:0 FREE:100 --> NAME:QUEUE5 STATE:ENBL TYPE:PROGRAM MB:QUEUE5 NB_MSG:0 FREE:100 --> NAME:BC1A.QUEUE6 STATE:ENBL TYPE:DSA NB_MSG:0 FREE:100 --> NAME:QUEUE7 STATE:ENBL TYPE:USERID NB_MSG:0 FREE:100 --> NAME:BC1A.QUEUE8 STATE:ENBL TYPE:DSA NB_MSG:0 FREE:100 --> NAME:BC1A.QUEUE9 STATE:ENBL TYPE:DSA NB_MSG:0 FREE:100 COMMAND COMPLETED. 9 OBJECTS SELECTED

S: DNET QD TYPE=USER CODE=LONG; GAQD 14:52:51 --> NAME:QUEUE7 STATE:ENBL TYPE:USERID NB_MSG:0 FREE:100 INT_TYPE:MEMORY QMAINT:NO INMODE:NORMAL OUTMODE:NORMAL BLOCKING:NO NBLINES:20 LINELG:80 INDEX:0 TRSPT:NO KBCO:NO BSC_ACK:NO CNX_STAT:0 COMMAND. 1 OBJECT SELECTED

S: DNET QD QUEUE2 CODE=LONG; GAQD 15:00:56 --> NAME:QUEUE2 STATE:ENBL TYPE:PROGRAM MB:QUEUE2 NB_MSG:2 FREE:100 INT_TYPE:MEMORY QMAINT:NO BREAK:NO SHARE:NO PROTOCOL:TWS NBLINES:0 LINELG:0 INDEX:0 CNX_STAT:0 COMMAND. 1 OBJECT SELECTED❑


2-72 47 A2 94UC

Explanation of Parameters in Response

NB_MSG the current number of messages in the queue.

FREE the percentage free space in the queue.

INT_TYPE the internal type of queue:

MEM : memory queueDISK : disk queue

QMAINT YES : QMAINT is the application using the queue.BREAK meaningful only for TYPE=PROG, event notification

as follows:

YES : application using the queue should be notifiedof asynchronous events such as BREAK and RVI

NO : application is not notified of asynchronousevents.

SHARE meaningful only for TYPE=PROG, as follows:

YES : MCS applications can share the same queue.NO : no sharing.

PROTOCOL meaningful only for TYPE=PROG, defining thecommunication mode between application andterminal:

TWA : two-way alternateTWS : two way simultaneous

INITJCL meaningful only for TYPE=PROG, specifying thename of the application for automatic restart.

INMODE meaningful only for TYPE=DSA or USER, definingthe input data exchanged from terminal to application:

NL : normalMK : markedUN : unedited

OUTMODE meaningful only for TYPE=DSA or USER, definingthe format of output data from application to terminal:

NL : normalUN : unedited


47 A2 94UC 2-73

BLOCKING meaningful only for TYPE=DSA or USER.

YES : MAM blocks messages sent by application toterminal by line throw and carriage return.

NBLINES meaningful only for TYPE=DSA or USER, specifyingthe maximum number of logical lines to be sent.

LINELG meaningful only for TYPE=DSA or USER, specifyingthe logical line length on terminal for automaticediting.

INDEX meaningful only for TYPE=DSA or USER, specifyingthe index of the associated program queue.Meaningless if 0.

TRSPT meaningful only for TYPE=DSA or USER.

YES : transparent mode editing for BSC lineprocedure.

KBCO meaningful only for TYPE=DSA or USER.

YES : KCO BCO used by BSC2780.

BSCACK meaningful only for TYPE=DSA or USER.

YES : end-to-end acknowledgement used forBSC2780.

CNX_STAT meaningful only for TYPE=DSA or USER, indicatingconnection status:

− no connection− connection set up on input− connection running on output− connection set up on output− connection shutdown running


2-74 47 A2 94UC

2.5.21 DNET RB

Purpose

Displays the status or attributes of selected RB (Route information Base) objects.

Syntax


CLASS = RB


[, STATE ={ ENBL | LOCK }]

[, TYPE = CLNS ]

[, NSAP_ID = name-8]

[, NSAP = NSAP_address]

[, NSAP_MASK = NSAP_mask ]

[, SNPA = SNPA_string]



TYPE CLNS

NSAP_ID An identifier name for the Network Service AccessPoint.

NSAP a code for the remote Network Service Access Point(from 0 to 40 digits).

NSAP_MASK a string of bits, representing the mask, left justified, foran equivalent class (optional).

SNPA a string of 12 hexadecimal digits giving the MACaddress of the next hop.


47 A2 94UC 2-75

Response (See DNET parameters)

* SHORT

state : ENBL or LOCKtype : CLNSNSAP_ID : identifier of the NSAPNSAP address : up to 40 digits corresponding to the NSAP valueMASK : maskSNPA : up to 40 digits corresponding to the SNPA valuetype_entry : 2 characters DY: dynamic entry ST: static entry

* LONG

state : ENBL or LOCKtype : CLNSNSAP_ID : identifier of the NSAPNSAP address : up to 40 digits corresponding to the NSAP valueMASK : maskSNPA : up to 40 digits corresponding to the SNPA valuetype_entry : 2 characters DY: dynamic entry ST: static entry

EXAMPLE:

DNET RB

DARB hh:mm:ss ---> STATE = ENBL TYPE = CLNS NSAP_ID = RB01 NSAP = yyyy....y NSAPMASK = FFFFFFFF SNPA = zzzz....z TYPE_ENT:ST ---> STATE = ENBL TYPE = CLNS NSAP_ID = RB02 NSAP = yyyy....y NSAPMASK = FFFFFFFF SNPA = zzzz....z TYPE_ENTRY:ST COMMAND COMPLETED. 2 OBJECTS SELECTED❑


2-76 47 A2 94UC

2.5.22 DNET SA

Purpose

Displays the status of selected SA (subdomain) objects.

Syntax


CLASS = SA

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = ISO ]

[, MAP = ( { SV | CT }: name-8 ) ]

[, NSAP = addr-40 ]



TYPE ISO

MAP selects the subdomain on its associated passthroughsystem.

NSAP specifies the upper part of the NSAP address inhexadecimal. When specified, all subdomains whoseNSAP prefixes contain this string are selected.NSAP and OBJECT are mutually exclusive.


47 A2 94UC 2-77

Response for each SA selected

* SHORT name type :ISO nsap :NSAP mask

* LONG name type :ISO nsap :NSAP mask system :passthrough system serving subdomain sy_state :state of passthrough system ENBL or DOWN or LOCK cos :class-of-service offered by passthrough system

EXAMPLE:

S: DNET SA; DASA 11:04:31 --> NAME:SDOM10 TYPE:ISO NSAP:123456789ABCF0123456 --> NAME:SDOM5 TYPE:ISO NSAP:012345 --> NAME:SDOM4 TYPE:ISO NSAP:01234 --> NAME:SDOM3 TYPE:ISO NSAP:0123 --> NAME:SDOM2 TYPE:ISO NSAP:012 --> NAME:SDOM1 TYPE:ISO NSAP:01 COMMAND COMPLETED. 6 OBJECTS SELECTED

S: DNET SA OBJECT=SDOM10 CODE=LONG; GASA 15:44:29 --> NAME:SDOM10 TYPE:ISO NSAP:123456789ABCF0123456 SYSTEM:BP10 SY_STATE:ENBL COS:0:7 --> NAME:SDOM10 TYPE:ISO NSAP:123456789ABCF0123456 SYSTEM:BP11 SY_STATE:ENBL COS:0:7 --> NAME:SDOM10 TYPE:ISO NSAP:123456789ABCF0123456 SYSTEM:BPD8 SY_STATE:ENBL COS:0:7 COMMAND COMPLETED. 3 OBJECTS SELECTED❑


2-78 47 A2 94UC

2.5.23 DNET SB

Purpose

Displays the status of selected SB (statistics block) objects.

Syntax


CLASS = SB


[, OBJECT = ( name-8 [, name-8 ] ) ]

[, TYPE = SMPL ]


[, MAP = { CC | IS | LC | PC | SS | TC | NK} : dec-5 ]



TYPE SMPL

MAP maps the connection object to the SB object.

CC : channel connection (cc index of DNS or CNS 7)IS : iso session connectionLC : logical connectionPC : physical connectionSS : sessionTC : transport connectionNK : internet network activity


47 A2 94UC 2-79

Response


* LONG name state type obj1_cc :first cc monitored obj2_cc :last cc monitored obj1_is :first is monitored obj2_is :last is monitored obj1_lc :first lc monitored obj2_lc :last lc monitored obj1_pc :first pc monitored obj2_pc :last pc monitored obj1_ss :first ss monitored obj2_ss :last ss monitored obj1_tc :first tc monitored obj2_tc :last tc monitored objstate :monitored object state obj_type :monitored object type mapping1 :monitored object mapping mapping2 :monitored object mapping interval :reporting interval

EXAMPLE:

S: DNET SB MAP=CC:0; DASB 14:15:56 --> NAME:_SBCC2 STATE:LOCK TYPE:SMPL --> NAME:_SBCC1 STATE:LOCK TYPE:SMPL --> NAME:_SBCC0 STATE:LOCK TYPE:SMPL COMMAND COMPLETED. 3 OBJECTS SELECTED

S:DNET SB OBJECT=_SBCC0 CODE=LONG; GASB 14:16:15 --> NAME:_SBCC0 STATE:LOCK TYPE:SMPL OBJ1_CC:0 OBJ2_CC:65535 OBJSTATE:USED MAP1_SV:BP16 INTERVAL:00:05:00 COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-80 47 A2 94UC

2.5.24 DNET SC

Purpose

Displays the status of selected SC (session control) objects.

SC is the addition of LSC and RSC.

Syntax for LSC (Local Session Control)


CLASS = { LSC | SC }

[, OBJECT = ( name-8 [, name-8 ] ) ]



[, TYPE = DSA ]

[, VENUE = PR ]



TYPE DSA


DNET CLASS=LSC ...

is equivalent to

DNET CLASS=SC VENUE=PR ...


47 A2 94UC 2-81

Response

* SHORT name state type :DSA venue :proper (local)

* LONG name state type :DSA venue :proper (local) tsap :transport service access point scid :session control identifier

EXAMPLE:

S: DNET LSC; DASC 16:11:57 --> NAME:BL03 STATE:ENBL TYPE:DSA VENUE:PROPER COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET SC CODE=LONG VENUE=PR; GASC 16:12:08 --> NAME:BL03 STATE:ENBL TYPE:DSA VENUE:PROPER TSAP:BL03 SCID:60:3 . COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-82 47 A2 94UC

Syntax for RSC (Remote Session Control)


CLASS = { RSC | SC }

[, OBJECT = ( name-8 [, name-8 ] ) ]



[, TYPE = DSA ]

[, MAP = ( SR : name-8 [, SR : name-8 ] ) ]

[, VENUE = IM ]



TYPE DSA

MAP maps the RSC to its associated SR (session route).


DNET CLASS=RSC ...

is equivalent to

DNET CLASS=SC VENUE=IM ...


47 A2 94UC 2-83

Response

* SHORT name state type :DSA mapping1 :SR session route name venue :image (remote)

* LONG name state type :DSA mapping1 :SR session route name venue :image (remote) tsap :transport service access point scid :session control identifier

EXAMPLE:

S: DNET SC OBJECT=(BC00,BC05) VENUE=IM; DASC 16:13:57 --> NAME:BC00 STATE:ENBL TYPE:DSA VENUE:IMAGE --> NAME:BC01 STATE:ENBL TYPE:DSA VENUE:IMAGE --> NAME:BC02 STATE:ENBL TYPE:DSA VENUE:IMAGE --> NAME:BC15 STATE:ENBL TYPE:DSA VENUE:IMAGE --> NAME:BC17 STATE:ENBL TYPE:DSA VENUE:IMAGE --> NAME:BC07 STATE:ENBL TYPE:DSA VENUE:IMAGE --> NAME:BC19 STATE:ENBL TYPE:DSA VENUE:IMAGE --> NAME:BC05 STATE:ENBL TYPE:DSA VENUE:IMAGE COMMAND COMPLETED. 8 OBJECTS SELECTED

S: DNET RSC BC02 CODE=LONG; GASC 16:15:17 --> NAME:BC02 STATE:ENBL TYPE:DSA VENUE:IMAGE TSAP:BC02 SCID:65:2 COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-84 47 A2 94UC

2.5.25 DNET SP

Purpose

Displays the status of selected SP objects (SAP addresses).

Syntax


CLASS = SP

[, OBJECT = ( dec-5 [, dec-5 ] ) ]


[, TYPE = SSAP ]

[, MAP = ID : name-4 ]



TYPE describes the type of object appropriate to the SP.

SSAP: session service access point

MAP maps the SP to its associated ID.


47 A2 94UC 2-85

Response

* SHORT index state : ENBL, USED or DSBL type : SSAP mapping1 : ID mapping2 : SC s-sel : session selector t-sel : transport selector

* LONG index state : ENBL, USED or DSBL type : SSAP mapping1 : ID mapping2 : SC s-sel : session selector t-sel : transport selector nsap : network access point maxcnx : total number of connections curcnx : current number of connections ext-name : external entity name (application name)

EXAMPLE:

S: DNET SP; DASP 09:31:52 --> INDEX:18434 STATE:USED TYPE:SSAP ID:BPC6 SC:BPC6 S_SEL:83518434 T_SEL:84842504336 NSAP:781639250F0800385046C6 COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET SP OBJECT=18434 CODE=LONG; GASP 09:32:00 --> INDEX:18434 STATE:USED TYPE:SSAP ID:BPC6 SC:BPC6 S_SEL:83518434 T_SEL:84842504336 NSAP:781639250F0800385046C6 MAXCNX:3 CURCNX:1 EXT_NAME:AJ30 COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-86 47 A2 94UC

2.5.26 DNET SR

Purpose

Displays the status of selected SR (session route) objects.

Syntax


CLASS = SR

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, STATE = { ENBL | LOCK | DSBL | DOWN | USED } ]

[, TYPE = { ISO | GC64 } ]

[, MAP=( { CH | SC | TS }:name-8 [, { CH | SC | TS }:name-8 ] ) ]



TYPE describes the type of SR:

ISO : ISO networkGC64 : PSI channel for DPS 7000 or link betweenDPS 7000 and FCP 7

MAP maps the SR to its associated class:

CH : channel (available for TYPE=GC64 but PSIchannel only)SC : session controlTS : transport station (available for TYPE=ISO only)


47 A2 94UC 2-87

Response

* SHORT name state type :ISO or GC64 mapping1:SC session control name mapping2:CH PSI channel name on TYPE=GC64 :TS transport station on TYPE=ISO

* LONG namex state type :ISO or GC64 mapping1:SC session control name mapping2:CH PSI channel name on TYPE=GC64 :TS transport station on TYPE=ISO server :SV server name quota :quota of sr connections cnct_nb :current connection number

EXAMPLE:

S: DNET SR OBJECT=(BC000001,BC050001); DASR 14:33:14 --> NAME:BC000001 STATE:ENBL TYPE:GC64 SC:BC00 CH:CC00 --> NAME:BC010001 STATE:ENBL TYPE:GC64 SC:BC01 CH:CC00 --> NAME:BC020001 STATE:ENBL TYPE:GC64 SC:BC02 CH:CC00 --> NAME:BC030001 STATE:ENBL TYPE:GC64 SC:BC03 CH:CC00 --> NAME:BC040001 STATE:ENBL TYPE:GC64 SC:BC04 CH:CC00 --> NAME:BC050001 STATE:ENBL TYPE:GC64 SC:BC05 CH:CC00 COMMAND COMPLETED. 6 OBJECTS SELECTED

S: DNET SR BC020001 CODE=LONG; GASR 14:33:41 --> NAME:BC020001 STATE:ENBL TYPE:GC64 SC:BC02 CH:CC00 SV:BP16 QUOTA:0 CNCT_NB:0 COMMAND COMPLETED. 1 OBJECT SELECTED


2-88 47 A2 94UC

S: DNET SR; DASR 15:48:06 --> NAME:BC980001 STATE:ENBL TYPE:GC64 SC:BC98 CH:CC03 15:48:06 NAME:MP900001 STATE:ENBL TYPE:ISO SC:MP90 TS:RTS_MP90 15:48:06 NAME:BCB60001 STATE:ENBL TYPE:GC64 SC:BCB6 --> NAME:BCB70001 STATE:ENBL TYPE:GC64 SC:BCB7 --> NAME:BCB80001 STATE:USED TYPE:GC64 SC:BCB8 --> NAME:BRA50001 STATE:ENBL TYPE:GC64 SC:BRA5 --> NAME:BRA70001 STATE:ENBL TYPE:GC64 SC:BRA7 CH:CC03 --> NAME:BRA40001 STATE:ENBL TYPE:GC64 SC:BRA4 CH:CC03 --> NAME:BRA90001 STATE:USED TYPE:GC64 SC:BRA9 --> NAME:BCA60001 STATE:USED TYPE:GC64 SC:BCA6 --> NAME:BCA40001 STATE:ENBL TYPE:GC64 SC:BCA4 --> NAME:BRA10001 STATE:ENBL TYPE:GC64 SC:BRA1 15:48:06 NAME:BRA20001 STATE:ENBL TYPE:GC64 SC:BRA2 --> NAME:BRA30001 STATE:ENBL TYPE:GC64 SC:BRA3 --> NAME:BYA00001 STATE:DSBL TYPE:GC64 SC:BYA0 CH:CC03 --> NAME:BCAA0001 STATE:ENBL TYPE:GC64 SC:BCAA CH:CC03 --> NAME:CONF0001 STATE:ENBL TYPE:GC64 SC:CONF COMMAND COMPLETED. 17 OBJECTS SELECTED❑


47 A2 94UC 2-89

2.5.27 DNET SS

Purpose

Displays the status of selected SS (session) objects.

Syntax


CLASS = SS

[, OBJECT = ( dec-5 [, dec-5 ] ) ]




[, MAP = LC : name-8 ]

[, ENDS = { 1 | 2 } ]




MAP maps the object to its associated LC (logicalconnection).

ENDS 1 : default, selects only the initiator's end of the localconnection

2 : selects both ends of the local connection


2-90 47 A2 94UC

Response

* SHORT and * LONG index state type :internal or external mapping2:LC logical connection index pair_idx:index of opposite end (local connection) sub_ch :subchannel ss_nb :session number person :user identifier project :project identifier billing :billing identifier

* HISTORY index local_mb:LMB (local mailbox) rmt_mb :RMB (remote mailbox) mapping3:LC supporting logical connection in_or_ac:initiator or acceptor of connection lc_id :dialog protocol logical connection identifier sub_ch :number of the subchannel ss_nb :session number on the subchannel eda :number of application data characters sent esy :number of system characters sent ers :number of record segments sent erc :number of records sent elt :number of letters sent rda :number of application data characters received rsy :number of system characters received rrs :number of record segments received rrc :number of records received rlt :number of letters received


47 A2 94UC 2-91

EXAMPLE:

S: DNET SS OBJECT=(15364,*); DASS 14:26:34 --> INDEX:15364 STATE:USED TYPE:EXTERNAL LC:15364 PAIR_IDX:0 SUB_CH:1 SS_NB:1 PERSON:GAETAN PROJECT:QBSA BILLING:QBSAV --> INDEX:16388 STATE:USED TYPE:EXTERNAL LC:16388 PAIR_IDX:0 SUB_CH:1 SS_NB:1 PERSON:REOLON PROJECT:OTI BILLING:OTI-OUTI --> INDEX:17413 STATE:USED TYPE:EXTERNAL LC:17413 PAIR_IDX:0 SUB_CH:1 SS_NB:1 PERSON:OPERATOR PROJECT:OPERATOR BILLING:INSTALL COMMAND COMPLETED. 3 OBJECTS SELECTED

S: DNET SS OBJECT=(15364,*) CODE=LONG; DASS 14:26:57 --> INDEX:15364 STATE:USED TYPE:EXTERNAL LC:15364 PAIR_IDX:0 SUB_CH:1 SS_NB:1 PERSON:GAETAN PROJECT:QBSA BILLING:QBSAV --> INDEX:16388 STATE:USED TYPE:EXTERNAL LC:16388 PAIR_IDX:0 SUB_CH:1 SS_NB:1 PERSON:REOLON PROJECT:OTI BILLING:OTI-OUTI --> INDEX:17413 STATE:USED TYPE:EXTERNAL LC:17413 PAIR_IDX:0 SUB_CH:1 SS_NB:1 PERSON:OPERATOR PROJECT:OPERATOR BILLING:INSTALL COMMAND COMPLETED. 3 OBJECTS SELECTED

S: DNET SS OBJECT=(15364,*) CODE=HISTORY; GASS 14:27:15 --> INDEX:15364 LMB:BPA6IOF RMB:BP03V272 LC:15364 IN_OR_AC:AC LC_ID:1006895105 SUB_CH:1 SS_NB:1 EDA:13897 ESY:652 ERS:87 ERC:87 ELT:88 RDA:635 RSY:466 RRS:55 RRC:55 RLT:59 --> INDEX:16388 LMB:BPA6IOF RMB:BP07VB43 LC:16388 IN_OR_AC:AC LC_ID:1074003969 SUB_CH:1 SS_NB:1 EDA:2748 ESY:298 ERS:28 ERC:28 ELT:29 RDA:165 RSY:250 RRS:20 RRC:20 RLT:21 --> INDEX:17413 LMB:BPA6IOF RMB:BP05V672 LC:17413 IN_OR_AC:AC LC_ID:1141178369 SUB_CH:1 SS_NB:1 EDA:43968 ESY:1036 ERS:151 ERC:151 ELT:152 RDA:210 RSY:426 RRS:49 RRC:49 RLT:51 COMMAND COMPLETED. 3 OBJECTS SELECTED❑


2-92 47 A2 94UC

2.5.28 DNET SY

Purpose

Displays the status of selected SY (system) objects.

Syntax for LSYS (Local System)


CLASS = LSYS

[, OBJECT = name-4 [, name-4 ] ]


[, STATE = USED ]

[, VENUE = PR ]




DNET CLASS=LSYS ...

is equivalent to

DNET CLASS=SY VENUE=PR ...


47 A2 94UC 2-93

Response

* SHORT name state :USED

* LONG name state :USED profile :system profile net_time :network time on local system tsel :default iso transport selector nsap :network service access point

EXAMPLE:

S: DNET LSYS; DASY 16:55:19 --> NAME:BL03 STATE:USED COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET LSYS CODE=LONG; GASY 16:55:30 --> NAME:BL03 STATE:USED PROFILE=DPS7/GCOS-7/V9 NET_TIME:JAN 09, 1991 16:55:30 TSEL:424C3033 COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET SY CODE=LONG VENUE=PR; GASY 15:42:52 --> NAME:BPA0 STATE:USED PROFILE=DPS7/GCOS-7/V9 NET_TIME:MAR 01, 1991 15:42:51 LOC_TIME:OCT 17, 2002 18:23:26 TSEL:123456789012345678 ->901245678901234567890123456789012345678901234 NSAP:1 --> NAME:BPA0 STATE:USED PROFILE=DPS7/GCOS-7/V9 NET_TIME:MAR 01, 1991 15:42:51 LOC_TIME:OCT 17, 2002 18:23:26 TSEL:123456789012345678 ->901245678901234567890123456789012345678901234 NSAP:2 --> NAME:BPA0 STATE:USED PROFILE=DPS7/GCOS-7/V9 NET_TIME:MAR 01, 1991 15:42:51 LOC_TIME:OCT 17, 2002 18:23:26 TSEL:123456789012345678 ->901245678901234567890123456789012345678901234 NSAP:3 COMMAND COMPLETED. 3 OBJECTS SELECTED❑


2-94 47 A2 94UC

Syntax for RSYS (Remote System)


CLASS = RSYS

[, OBJECT = ( name-4 [, name-4 ] ) ]


[, STATE = USED ]

[, MAP = SA : name-8 ]

[, VENUE = IM ]


Parameters (See DNET Command):

MAP displays the RSYS associated to the given subdomain.


DNET CLASS=RSYS ...

is equivalent to

DNET CLASS=SY VENUE=IM ...

Response

* SHORT name state :USED

* LONG name state :USED profile :system profile


47 A2 94UC 2-95

EXAMPLE:

S: DNET SY (BC05,BC00) VENUE=IM; DASY 14:34:37 --> NAME:BC05 STATE:USED --> NAME:BC04 STATE:USED --> NAME:BC03 STATE:USED --> NAME:BC02 STATE:USED --> NAME:BC01 STATE:USED --> NAME:BC00 STATE:USED COMMAND COMPLETED. 6 OBJECTS SELECTED

S: DNET RSYS BC02 CODE=LONG; GASY 14:34:53 --> NAME:BC02 STATE:USED PROFILE:DPS7/GCOS-7/V9 COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-96 47 A2 94UC

2.5.29 DNET TC

Purpose

Displays the status of selected TC (transport connection) objects.

Syntax


CLASS = TC

[, OBJECT = ( dec-5 [, dec-5 ] ) ]



[ { ISO [,MAP = ({ LC|TS }:name-8 [,{ LC|TS }:name-8])]}][, TYPE = { DIWS [,MAP = TS:name-8 ]}][ { CLNS [,MAP = TS:name-8 ]}][ { INET [,MAP = TS:name-8 ]}]



TYPE ISO, for TC via ISL.DIWS, for TC using the ISO stack with Null Internetof the OCS Front End.CLNS, for TC using the ISO stack with Full Internet ofthe OCS Front End.INET, for TC using ISO over the TCP/IP stack of theOCS Front End.


47 A2 94UC 2-97

Response (for TYPE = ISO)

* SHORT index state type :ISO mapping1:TS local transport station name mapping2:TS remote transport station name mapping4:LC logical connection index

* LONG index state type :ISO mapping1:TS local transport station name mapping2:TS remote transport station name mapping4:LC logical connection index lcplug :local plug number rmplug :remote plug number maxtusz :maximum transport unit size for connection maxcrdts:maximum credit allocated for outgoing data maxcrdtr:maximum credit allocated for incoming data mils :maximum input letter size

* HISTORY index lcendpnt:local transport station name rmendpnt:remote transport station name in_or_ac:initiator or acceptor rmplug :remote plug number epd :number of data fragments sent & acknowledged epc :number of command fragments sent eto :number of acknowledgement timeouts edu :number of data fragments retransmitted ewc :number of times window closed ewt :time window remained closed esd :number of letters received from session control for transmission over transport connection rpd :number of data fragments received correctly rpc :number of command fragments received rdu :number of duplicate fragments received rsd :number of letters received over transport connection and passed to session control exd :number of expedited data fragments sent rxd :number of expedited data fragments received


2-98 47 A2 94UC

Response (for TYPE = DIWS or CLNS)

* SHORT

indexstate : USEDtype : DIWS or CLNSmapping1 : TS transport station name

* LONG

indexstate : USEDtype : DIWS or CLNSmapping1 : TS transport station nameLCPLUG : local plugRMPLUG : remote plugMAXTUSZ : maximum transport unit sizeMAXCRDTS : maximum credit allocated for emissionMAXCRDTR : maximum credit allocated for reception

* HISTORY

indexlocal end point: local transport station nameRMPLUG: remote plugEPD : number of data fragments sent and acknowledgedETO : number of acknowledgement timeoutsERJ : number of REJects received provoking re-transmissionEDU : number of data fragments re-transmittedEWC : number of times window closedESD : number of letters received from session for transmissionRPD : number of data fragments received correctlyRSD : number of letters received and passed to sessionEXD : number of expedited data fragments sentRXD : number of expedited data fragments receivedEDA : number of data bytes sent (and acknowledged) in TSDUsRDA : number of data bytes received (and accepted) in TSDUsRAS : number of times reassignment occurred


47 A2 94UC 2-99

Response (for TYPE = INET)

* SHORT

indexstate : USEDtype : INETmapping1 : INET TS Transport Station name

* LONG

indexstate : USEDtype : INETmapping1 : INET TS Transport Station nameLCPLUG : local plugRMPLUG : remote plugprot_option : CLS0 (transport class 0)MAXTUSZ : maximum transport unit sizecalling NSAPcalled NSAP

* HISTORY

indexlocal_end_point: local Transport Station nameRMPLUG: remote plugEPD : number of data fragments sent and acknowledgedESD : number of letters received from session for transmissionRPD : number of data fragments received correctlyRSD : number of letters received and passed to sessionEXD : number of expedited data fragments sentRXD : number of expedited data fragments receivedEDA : number of data bytes sent (and acknowledged) in TSDUsRDA : number of data bytes received (and accepted) in TSDUs


2-100 47 A2 94UC

EXAMPLE:

S: DNET TC OBJECT=(1,4); DATC 09:57:39 --> INDEX:1 STATE:ENBL TYPE:ISO TS:TNS TS:BL05 LC:13312 --> INDEX:2 STATE:ENBL TYPE:ISO TS:TNS TS:BL36 LC:34830 --> INDEX:3 STATE:ENBL TYPE:ISO TS:TNS TS:BL36 LC:35854 --> INDEX:4 STATE:ENBL TYPE:ISO TS:TNS TS:BL36 LC:36878 COMMAND COMPLETED. 4 OBJECTS SELECTED

S: DNET TC OBJECT=1 CODE=LONG; GATC 09:58:17 --> INDEX:1 STATE:ENBL TYPE:ISO TS:TNS TS:BL05 LC:13312 LCPLUG:1 RMPLUG:1693 MAXTUSZ:1024 MAXCRDT:4 MAXCRDTR:4 MILS:3057 COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET TC OBJECT=1 CODE=HISTORY; GHTC 09:58:32 --> INDEX:1 LCENDPNT:TNS RMENDPNT:BL05 IN_OR_AC:AC RMPLUG:1693 EPD:12 EPC:10 ETO:0 EDU:0 EWC:0 EWT:0 ESD:13 RPD:9 RPC:18 RDU:0 RSD:9 EXD:0 RXD:0 COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET TC OBJECT=10758;

DATC hh:mm:ss---> INDEX: 10758 STATE:USED TYPE:DIWS TS:NCC1COMMAND COMPLETED. 1 OBJECT SELECTED

DNET TC CODE=HISTORY;

GHTC 16:07:18---> INDEX: 10758 LCENDPNT:NCC1 RMPLUG:6206 EPD:33 ETO:8 ERJ:0 EDU:9 EWC:0 ESD:14 RPD:19 RSD:8 EXD:0 RXD:0 EDA:3042 RDA:364 RAS:0COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 2-101

2.5.30 DNET TS

Purpose

Displays the status of selected TS (transport station) objects.

TS is the addition of LTS and RTS.

Syntax for LTS (Local Transport Station)


CLASS = { LTS | TS }

[, OBJECT = ( name-8 [, name-8 ] ) ]



[, TYPE = ISO ]

[, MAP = ( { NR|SC|SR|TC }:name-8 [, { NR|SC|SR|TC }:name-8 ] ) ]

[, VENUE = PR ]



2-102 47 A2 94UC


TYPE ISO

MAP maps the LTS to its associated class:

NR : network routeSC : session controlSR : session routeTC : transport connection


DNET CLASS=LTS ...

is equivalent to

DNET CLASS=TS VENUE=PR ...

Response

* SHORT and * LONG name state type :ISO venue :proper (local)

EXAMPLE:

S: DNET LTS; DATS 10:17:43 --> NAME:TNS STATE:ENBL TYPE:ISO VENUE:PROPER COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET TS CODE=LONG VENUE=PR; GATS 10:17:51 --> NAME:TNS STATE:ENBL TYPE:ISO VENUE:PROPER COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 2-103

Syntax for RTS (Remote Transport Station)


CLASS = { RTS | TS }

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, STATE = { ENBL | LOCK | USED | DSBL | DOWN } ]

[, TYPE = ISO ]


[, VENUE = IM ]



TYPE ISO

MAP maps the RTS to its associated class:



DNET CLASS=RTS ...

is equivalent to

DNET CLASS=TS VENUE=IM ...


2-104 47 A2 94UC

Response

* SHORT name state type :ISO venue :image (remote)

* LONG name state type :ISO venue :remote option1 :NO option2 :NO option3 :NO option4 :YES credit :maximum transport output credit maxtusz :maximum transport unit size timer_1 :acknowledgement timeout in milliseconds timer_2 :inactivity timeout in milliseconds count_n1:maximum number of retries maxpaths:maximum number of NRs maxtc :maximum number of TCs

EXAMPLE:

S: DNET TS BL37 VENUE=IM; DATS 10:18:34 --> NAME:BL37 STATE:ENBL TYPE:ISO VENUE:IMAGE COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET RTS BL37 CODE=LONG; GATS 10:18:34 --> NAME:BL37 STATE:ENBL TYPE:ISO VENUE:IMAGE OPTION1:NO OPTION2:NO OPTION3:NO OPTION4:YES CREDIT:3 MAXTUSZ:2048 TIMER_1:10 TIMER_2:60 COUNT_N1:3 MAXPATHS:1 MAXTC:2200 COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 2-105

Syntax (for OCS)


CLASS = TS

[, OBJECT = ( name-8 [,name-8] )]


[, STATE = ENBL | LOCK | USED | DOWN | DSBL ]

[, TYPE = { COTP | INET } ]



TYPE COTP/INET

Response

* SHORT

name: name of the Transport Station object (up to 8 characters)statetype: COTP/INET

* LONG

name: name of the Transport Station object (up to 8 characters)statetype: COTP/INET

option1 :prot_opt_1 : NOoption2 :prot_opt_2 : NOoption3 :prot_opt_3 : NOoption4 :prot_opt_4 : YESmaxtc :


2-106 47 A2 94UC

EXAMPLE:

DNET TS BL38;

DATS hh:mm:ss ---> NAME:BL38 STATE=ENBL TYPE=COTP COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET TS;

DATS 17:20:44 ---> NAME:TSBCB1 STATE:ENBL TYPE:ISO VENUE:IMAGE ---> NAME:TSBCC4 STATE:ENBL TYPE:ISO VENUE:IMAGE ---> NAME:BCC1 STATE:ENBL TYPE:ISO VENUE:PROPER ---> NAME:NCC1 STATE:ENBL TYPE:COTP COMMAND COMPLETED. 4 OBJECTS SELECTED❑


47 A2 94UC 2-107

2.6 DNR (DISPLAY_NETWORK_REPORTING)

Purpose

Displays the names of active main and subprofiles entered in the SNR command.

Syntax

{ DNR }{ }{ DISPLAY_NETWORK_REPORTING }

Parameter Description

The DNR command does not take any parameters.

EXAMPLE:

S: DNR; ***************************************************** * DNR 11:08:28 * * ACTIVE PROFILES FOR OPERATOR * * MAIN = SURVEY * * SUB = NONE * * FROM_SYSTEM = ANY * *****************************************************❑


2-108 47 A2 94UC

2.7 DTL (DISPLAY_TEST_IN_LINE)

Purpose

Displays attributes, options and statistics for a given test.

Syntax

{ DTL }{ }{ DISPLAY_TEST_IN_LINE }

TEST = BNSE ID = dec-5 [ SYSTEM = { #WSYS | name-4 } ]

[ { SHORT } ][ CODE = { LONG } ] [, MORE = { 0 | 1 } ][ { HISTORY } ]


ID The identifier of the test returned by the STLTEST=BNSE command.

SYSTEM The name of the system on which the command is tobe executed.

CODE Specifies the kind of display required, as follows:

SHORT (default): brief displayLONG: detailed displayHISTORY: display accumulated counters and statistics

MORE Specifies a lower screen level.


47 A2 94UC 2-109

EXAMPLE:

S: DTL BNSE ID=2; DATL 09:32:02 --> ID:2 NAME:BNSE SUB_NAME:ECHO OBJECT:BL05$NSE ELAPSE:00:00:00 ITER:1000 DELAY:00:00:01 ERR_REP:R TRACE:NT ERR_ACT:HE AUX_OBJ:BCLE$NSE COMMAND COMPLETED. 1 OBJECT SELECTED

S: DTL BNSE ID=2 CODE=LONG; GATL 09:32:18 --> ID:2 NAME:BNSE SUB_NAME:ECHO OBJECT:BL05$NSE ELAPSE:00:00:00 ITER:1000 DELAY:00:00:01 ERR_REP:R TRACE:NT ERR_ACT:HE AUX_OBJ:BCLE$NSE DATA_NB:500 COMMAND COMPLETED. 1 OBJECT SELECTED

S: DTL BNSE ID=2 CODE=HISTORY; GHTL 09:32:39 --> ID:2 NAME:BNSE SUB_NAME:ECHO OBJECT:BL05$NSE ELAPSE:00:00:00 ITER:1000 START_T:APR 23,1991 09:31:40 STOP_T:00:00:00 S_BYTES:15624 R_BYTES:15624 S_RECORD:252 R_RECORD:252 COMMAND COMPLETED. 1 OBJECT SELECTED❑


2-110 47 A2 94UC

2.8 DTSVR (DISPLAY_TELECOM_SERVER)

Purpose

Displays the status of a communications server.

Syntax

{ DTSVR }{ }{ DISPLAY_TELECOM_SERVER }

[ { { * } } ] [ { * } ][ { { TNS } } ] [, STATE = { USED } ][ { { FEPS } } ] [ { ENBL } ][ { TYPE = { FECM } } ][ { { QMON } } ] [ { SHORT } ][ { { RAEH } } ] [ { LONG } ][ { { OCS } } ] [, CODE = { } ][ { } ] [ { LIST } ][ { NAME = name-8 } ] [ { NUMBER } ][ { } ][ { } ][ { RSYS = name-4 } ]


TYPE TYPE is mutually exclusive with NAME.

The type of server to be displayed. If neither TYPEnor NAME nor RSYS is specified, TYPE = * isassumed.

NAME NAME is mutually exclusive with TYPE and RSYS.

The name of the server occurrence to be displayed. IfTYPE is TNS, the server name is also TNS.


47 A2 94UC 2-111

RSYS RSYS is mutually exclusive with NAME.

The name of the remote system or the front-endprocessor to be administered by the server. In the caseof OCS, RSYS is used to give the name of the OCSserver.

STATE Specifies the state of servers to be displayed :

* groups all servers both USED and ENBL

ENBL means servers that are configured in networkbut not started.

USED means servers that are started.

CODE Specifies the level of detail requested in the display.

EXAMPLE:

S: DTSVR; DASV 11:47:54 --> SV:TNS STATE:USED TYPE:TNS --> SV:BL05 STATE:USED TYPE:FEPS 11:47:54 SV:BL1A STATE:ENBL TYPE:FEPS --> SV:QMON STATE:ENBL TYPE:QMON --> SV:RAEH STATE:ENBL TYPE:RAEH COMMAND COMPLETED. 5 OBJECTS SELECTED

S: DTSVR TNS CODE=LONG; GASV 11:48:05 --> SV:TNS STATE:USED TYPE:TNS TRACE:0 NAUTO:1 REPEAT:3 BUFSZ:128 BUF_MIN:15872 BUF_MAX:15872 EXTENS:80 NBCNCT:0 COMMAND COMPLETED. 1 OBJECT SELECTED

S: DTSVR FEPS CODE=LONG; GASV 11:48:15 --> SV:BL05 STATE:USED TYPE:FEPS TRACE:0 NODE:BL05 NAUTO:0 REPEAT:7 BUFSZ:128 BUF_MIN:512 BUF_MAX:2048 EXTENS:80 NBCNCT:1 LCT:CC01 11:48:15 SV:BL1A STATE:ENBL TYPE:FEPS NODE:BL1A COMMAND COMPLETED. 2 OBJECTS SELECTED


2-112 47 A2 94UC

S: DTSVR; DASV 17:01:33 --> SV:TNS STATE:USED TYPE:TNS --> SV:NCC1 STATE:USED TYPE:OCS 17:01:34 SV:RAEH STATE:ENBL TYPE:RAEH --> SV:NCC2 STATE:ENBL TYPE:OCS COMMAND COMPLETED. 4 OBJECTS SELECTED

S: DTSVR OCS NCC2 CODE=LONG; GASV 15:55:21 --> SV:NCC2 STATE:USED TYPE:OCS TRACE:0 NAUTO:1 REPEAT:0 BUFSZ:128 BUF_MIN:4096 BUF_MAX:8192 EXTENS:80 NBCNCT:244 LCT:EA82 COMMAND COMPLETED. 1 OBJECT SELECTED❑

where:

SV: Server name.

STATE: Server state.

TYPE: Server type.

TRACE: Trace level. Meaningful only when TYPE is RAEH orFECM.

ACTION: Label name in the scenario actually executed.

NODE: Name of the front-end processor, CNP 7, or Datanet.

VERS.: DNS/CNP 7/OCS Front End version.

SCENARIO: Scenario name.

NEXT: Label name in the scenario, to which control will bepassed in case of a subsequent automatic startup ofFECM or OCS, if automatic mode is enabled.

NAUTO: 0 means automatic mode is enabled.1 means automatic mode is disabled.

REPEAT: Maximum number of times that the server is to berestarted automatically.


47 A2 94UC 2-113

BUFSZ: Size of the buffer unit.

BUF_MIN: Minimum number of buffer units to be allocated at theserver startup.

BUF_MAX: Maximum number of buffer units after dynamicallocation.

EXTENS: Percentage of total buffer units used, beyond which anextension of the buffer pool is attempted until thenumber allocated reaches the maximum number.

NBCNCT: Number of connections.

LCT: Controller name.


2-114 47 A2 94UC

2.9 DVTR (DISPLAY_VCAM_TRACE)

Purpose

Displays the activity of the VCAM trace collector with respect to the logfile andobjects selected with their corresponding levels.

Syntax

{ DVTR }{ }{ DISPLAY_VCAM_TRACE }


The DVTR command does not take any parameters.


47 A2 94UC 2-115

2.10 EDD (ENTER_DSA_DIALOG)

PurposeDialogs with a DSA system, being

• the Datanet or CNP 7 for DPS 7000 ;

• the MainWay 2600LE for DPS 7000/XTA.

For more details, see the paragraph " Passthrough for Dialog with the FEP " or

" Passthrough for Dialog with the MainWay 2600LE " in Chapter 10.

Syntax

{ EDD }{ }{ ENTER_DSA_DIALOG }

[ ] [ {APPL } {$NOI } ] [ ][, RSYS = name-4 ] [,{ } = { } ] [,SETDFLT ][ ] [ {APPLICATION} {$DEBUG} ] [ ]

{ [ { ST | START } ] }{ [ { } ] }{ [ { TT | TERMINATE } ] }{ }{ [ { CN | CONNECT } [ { PSSW | PASSWORD } = char-12 ] } ] }{ [ { } ] }{ [ { DIS | DISCONNECT } ] }{ }{ [ { CD | COMMAND } = char-128 ] }{ }{ [ { DC | DISPLAY } ] }{ }{ [ { HO | HOMSG } ] }{ [ { } ] }{ [ { RO | ROMSG } ] }{ }{ [ { HM | HMSG } ] }{ [ { } ] }{ [ { RM | RMSG } ] }{ }{ [ { IT | ITCMD } ] }{ }{ [ TRACE = dec-3 ] }

[ { PR | PRTLIB } = char-8 ]


2-116 47 A2 94UC


RSYS Specifies the name of the remote system (Datanet orCNP 7) to dialog with, see SETDFLT.

RSYS is optional with START, TERMINATE,DISPLAY and TRACE. RSYS is mandatory (eitherexplicit or default) with all other parameters.

APPLICATION Specifies the name of the application to dialog with.

Default value is $NOI. See SETDFLT.

APPL is optional with START, TERMINATE,DISPLAY and TRACE. APPL is mandatory (explicitor default) with all other parameters.

NOTE: The $DEBUG application can be specified formaintenance purposes and is reserved for use by theService Center.

SETDFLT (Set Default value) Specifies that the names specifiedin RSYS and/or APPLICATION parameters becomedefault values for any further EDD command.

Before any specification of this parameter, the defaultvalues for RSYS and APPLICATION are the nameswhich were specified in the previous EDD command.

NOTE:The following parameters are all mutually exclusive.

START Specifies that FECM server is to be started to enterDSA dialog.

TERMINATE Specifies that FECM server which was executing toprocess DSA dialog is to be terminated.

CONNECT Specifies that a connection is to be established with thespecified application on the given system.

PASSWORD can only be specified with CONNECT.

DISCONNECT Specifies that the connection previously establishedwith the specified application on the given system is tobe terminated.


47 A2 94UC 2-117

COMMAND Specifies the command to be executed by theapplication on the given system.

DISPLAY Displays all the active connections of FECM server forDSA dialog with their state.

HOMSG (Hold Output Messages) Specifies that the messagesfrom the application are no longer printed onSYSOUT.

ROMSG (Release Output Messages) Specifies that the messagesfrom the application are printed on SYSOUT.

HMSG (Hold Messages) Specifies that the messages from theapplication are no longer printed on the console.

RMSG (Release Messages) Specifies that the messages fromthe application are printed on console.

ITCMD (Interrupt Command) Specifies that the previouscommand executed by the application on the givensystem is to be interrupted and remaining messages arelost.

TRACE Trace level of the server, for maintenance purposes.

PRTLIB Specifies that the report produced by the commandsthat follow is to be placed in a member of the librarySYS.DSACONF. You specify the name in the formCONFxxxx, where CONF refers to SYS.DSACONF,and xxxx (up to 4 characters) is the name of themember.


2-118 47 A2 94UC

❑

47 A2 94UC 3-1

3. ISO/DSA Commands (LNET to TVTR)

Because of a limit on the size of a Section (in this manual), the commands listed inSection 2 and Section 3 cannot be contained in a single Section. The commandsare listed in alphabetical order. The split of commands between Section 2 andSection 3 was done to roughly balance the sizes of the Sections (there is no otherreason for the split).

The following GCL commands are described in this Section:

LNET List_NETworkMDNET MoDify_NETworkMDTL MoDify_Test_in_lineMDTSVR MoDify_Telecom_ServerPRTTR PRint_Telecom_TRaceSCNVTR SCaN_Vcam_TRaceSNDQ SeND_QueueSNR Start_Network ReportingSTL Start_Test_in_lineSTSVR Start_Telecom_SerVeRSTTR Start_Telecom_TRaceSVTR Start_Vcam_TRaceTNR Terminate_Network_ReportingTTL Terminate_Test_in_LineTTSVR Terminate_Telecom_SerVeRTTTR Terminate_Telecom_TRaceTVTR Terminate_Vcam_TRace

NOTES:1. All these commands are available to MAIN operators except for LNET for

all classes which are accessible in the IOF domain.

2. The following are reserved for Maintenance purposes:- TRACE parameter of STSVR commands- SVTR and SCNVTR commands for VCAM_TRACE.


3-2 47 A2 94UC

3.1 LNET (LIST_NETWORK)

Purpose

Lists the names of selected network objects.

General Syntax

{ LNET }{ }{ LIST_NETWORK }

CLASS = class


[, STATE = { ENBL | LOCK | USED | DOWN | DSBL | SHUT | TEST } ]

[, TYPE = type ]


[, NUMBER = { 0 | 1 } ]


[, MORE { 0 | 1 } ]


NOTE:Detailed syntax for each class is given separately.

ISO/DSA Commands (LNET to TVTR)

47 A2 94UC 3-3

Parameters


For the DPS 7, the network is configured byNETGEN.For the CNP 7, the network is configured by CNS 7SYSGEN.For the Datanet, the network is configured by DNSSYSGEN.For other systems, refer to the appropriate networkingdocumentation.


Syntax Rules

LNET...OBJECT=name: selects one object

LNET...OBJECT=(name1,name2): selects all objectsfrom name1 up to name2

LNET...OBJECT=(name,*): selects all objects startingfrom name

LNET...OBJECT=(*,name): selects all objects frombeginning up to name

LNET...OBJECT=* or omitted: selects all objectswithin class

STATE describes the state of the objectENBL : object is availableLOCK : object is unavailableUSED : object is being usedDOWN : object has failedDSBL : object inoperable due to lower level failuresSHUT : object taken out of configurationTEST : object under test



NUMBER 0 : default, lists the network objects selected1 : gives the number of network objects selected.


3-4 47 A2 94UC


MORE 0 : default1 : displays new screen for class-specific parameters ofheterogeneous systems.

class-specific parameters See the appropriate LNET commands.

NOTE:When the command is sent to a remote system supporting a standard DSACNAD, care must be taken to ensure that this system is able to support thecommand and its corresponding parameters.

The general syntax of the command allows specifying common parameters. MOREallows prompting class-specific parameters which are not described in GCOS 7commands, if these parameters are needed for a given class.



LNET NUMBER=1

LNET NUMBER=0


NB

LSOBJECT=name1OBJECT=(name1,name2)STATE=stateTYPE=typeMAP=(map1[,map2])

name1name1/name2-OS state-OT type-OM map1[map2] |


• For the Datanet, DNS System Operations



47 A2 94UC 3-5

3.1.1 LNET AC

Purpose

Lists the names of selected AC (administrative correspondent) objects.

Syntax


CLASS = AC

[, OBJECT = ( name-8 [, name-8 ] ) ]




[, NUMBER = { 0 | 1 } ]


Parameters: (See LNET Command)

TYPE describes the type of object appropriate to the AC.ASF : administrative storage facilityAUT : administrative utilityMUX : multiplexorNAD : node administratorNCC : network control centerNOI : network operator interface



3-6 47 A2 94UC

EXAMPLES:

S: LNET AC NUMBER=1; NBAC 09:31:06 AC:1 COMMAND COMPLETED.

S: LNET AC; LSAC 09:31:13 LDSALOG COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 3-7

3.1.2 LNET AF

Purpose

Lists the names of selected AF (administrative function) objects.

Syntax


CLASS = AF

[, OBJECT = ( name-8 [, name-8 ] ) ]




[, NUMBER = { 0 | 1 } ]



TYPE describes the type of object appropriate to the AF.ASF : administrative storage facilityAUT : administrative utilityMUX : multiplexorNAD : node administratorNCC : network control centerNOI : network operator interface

MAP maps the AF to its AG correspondent.


3-8 47 A2 94UC

EXAMPLES:

S: LNET AF NUMBER=1; NBAF 09:31:22 AF:3 COMMAND COMPLETED.

S: LNET AF; LSAF 09:31:28 LNOI DSALOG LNAD COMMAND COMPLETED. 3 OBJECTS SELECTED❑


47 A2 94UC 3-9

3.1.3 LNET AG

Purpose

Lists the names of selected AG (administrative group) objects.

Syntax


CLASS = AG

[, OBJECT = ( name-8 [, name-8 ] ) ]




[, NUMBER = { 0 | 1 } ]



TYPE describes the type of object appropriate to the AG:ASF : administrative storage facilityAUT : administrative utilityMUX : multiplexorNAD : node administratorNCC : network control centerNOI : network operator interfaceOP : operator

MAP maps the AG to its AF correspondent.


3-10 47 A2 94UC

EXAMPLES:

S: LNET AG NUMBER=1; NBAG 09:31:40 AG:6 COMMAND COMPLETED.

S: LNET AG; LSAG 09:31:47 LNOI RMUX RLNOI _LDSALOG RDSALOG 09:31:47 RLNAD COMMAND COMPLETED. 6 OBJECTS SELECTED❑


47 A2 94UC 3-11

3.1.4 LNET AL

Purpose

Lists the names of selected AL (Address List) objects.

Syntax


CLASS = AL

[, OBJECT = ( name-8 [,name-8] )]

[, NSAP = NSAP_address ]

[, NUMBER = { 0 | 1 }]



NSAP a code for the local Network Service Access Point(from 0 to 40 digits).

NOTE:If NUMBER = 1 and several OCS servers are started, each server answers to thecommand. For example:

LNET AL NUMBER=1;

NBAL hh:mm:ss AL : 1 hh:mm:ss AL : 2 COMMAND COMPLETED


3-12 47 A2 94UC

EXAMPLES:

LNET AL;

LSAL hh:mm:ss AL01 AL02 COMMAND COMPLETED 2 OBJECTS SELECTED

LNET AL NUMBER=1;

NBAL hh:mm:ss AL=2 COMMAND COMPLETED.❑


47 A2 94UC 3-13

3.1.5 LNET CB

Purpose

Lists the names of selected CB (cable) objects.

Syntax


CLASS = { CB | CBL }

[, OBJECT = ( name-8 [, name-8 ] ) ]

[, TYPE = LAN1 ]

[, MAP = ( PL:name-8 [, PL:name-8 ] ) ]

[, NUMBER = { 0 | 1 } ]



TYPE LAN1: local area network for the ISL transceiver(applicable to DPS 7000 systems).

MAP maps the CB to its associated remote or local PL(physical link).

EXAMPLES:

S: LNET CB NUMBER=1; NBCB 11:25:14 CB:1 COMMAND COMPLETED.

S: LNET CB; LSCB 11:25:21 CBL_00 COMMAND COMPLETED. 1 OBJECT SELECTED❑


3-14 47 A2 94UC

3.1.6 LNET CC

Purpose

Lists the names of selected CC (channel connection) objects.

Syntax


CLASS = CC

[, OBJECT = ( dec-5 [, dec-5 ] ) ]


[, TYPE = { PSI | ISL } ]

[, MAP = ( { CC|CH|LC|SV }:name-8 [, { CC|CH|LC|SV }:name-8 ] ) ]

[, NUMBER = { 0 | 1 } ]



OBJECT identifies the connection number(s).

TYPE describes the type of object appropriate to the CC.PSI : peripheral subsystem interface for DatanetISL : internal system link for CNP 7

MAP maps the CC to its associated class.CC : channel connection (cc index of DNS or CNS7)CH : channelLC : logical connectionSV : server


47 A2 94UC 3-15

EXAMPLES:

S: LNET CC NUMBER=1; NBCC 09:48:31 CC:9 COMMAND COMPLETED.

S: LNET CC MAP=CH:CC00; LSCC 09:48:44 3 6 8 16 18 20 25 28 29 COMMAND COMPLETED. 9 OBJECTS SELECTED❑


3-16 47 A2 94UC

3.1.7 LNET CH

Purpose

Lists the names of selected CH (channel) objects.

Syntax


CLASS = CH

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = PSI ]

[, MAP=( {CC|CT|SC|SR|SV}:name-8 [, {CC|CT|SC|SR|SV}:name-8 ] ) ]

[, NUMBER = { 0 | 1 } ]




MAP maps the CH to its associated class.CC : channel connectionCT : controllerSC : session controlSR : session routeSV : server


47 A2 94UC 3-17

EXAMPLES:

S: LNET CH NUMBER=1; NBCH 09:48:53 CH:1 COMMAND COMPLETED.

S: LNET CH; LSCH 09:48:59 CC00 COMMAND COMPLETED. 1 OBJECT SELECTED❑


3-18 47 A2 94UC

3.1.8 LNET CT

Purpose

Lists the names of selected CT (controller) objects.

CT is the addition of LCT and RCT.




[, OBJECT = ( name-8 [, name-8 ] ) ]


[ { TYPE = ISL [,MAP=({ PL|SV }:name-8 [,{ PL|SV }:name-8 ] )] } ][,{ TYPE = PSI [,MAP=({ CH|SV }:name-8 [,{ CH|SV }:name-8 ] )] } ][ { TYPE = FCP [,MAP={ PL:name_8 | SV:name-8 }]]

[, VENUE = PR ]

[, NUMBER = { 0 | 1 } ]



TYPE ISL for ISL connection: mapping to PL or SVPSI for Datanet connection: mapping to CH or SVFCP for OCS Front End connection (in this case,STATE=DSBL does not apply)

MAP maps the LCT to its associated class.CH : channel for PSI typePL : physical link for ISL and FCP typesSV : server for ISL, FCP, and PSI types


47 A2 94UC 3-19


LNET CLASS=LCT ...

is equivalent to

LNET CLASS=CT VENUE=PR ...

EXAMPLES:

S: LNET LCT NUMBER=1; NBCT 13:21:45 CT:3 COMMAND COMPLETED.

S: LNET CT VENUE=PR; LSCT 13:21:55 EA01 CC01 CC02 COMMAND COMPLETED. 3 OBJECTS SELECTED❑



CLASS = RCT

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = ISL ]

[, MAP = ( PL : name-8 ) ]

[, VENUE = IM ]

[, NUMBER = { 0 | 1 } ]



3-20 47 A2 94UC





LNET CLASS=RCT ...

is equivalent to

LNET CLASS=CT VENUE=IM ...

EXAMPLES:

S: LNET RCT NUMBER=1; NBCT 13:22:28 CT:9 COMMAND COMPLETED.

S: LNET RCT; LSCT 13:22:34 CT_BL05 CT_BL04 RCT1MATH CT_BL17 CT_BL36 CT_BL37 CT_BL38 CT_BL13 CT_DSA5 COMMAND COMPLETED. 9 OBJECTS SELECTED❑


47 A2 94UC 3-21

3.1.9 LNET FL

Purpose

Lists the names of selected FL (filter) objects.

Syntax


CLASS = FL

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = { IN | OUT } ]

[ { AF : name-8 [, { AC | AG } : name-8 ] } ][, MAP = ( { } ) ][ { AC | AG | LG | OP } : name-8 [, AF : name-8 } ]


[, NUMBER = { 0 | 1 } ]




LOGIC INCL : inclusive (select if criteria match)EXCL : exclusive (reject if criteria match)OBLI : obligatory (reject if criteria do not match)

MAP maps the FL to its associated class.AC : administrative correspondentAF : administrative functionAG : administrative groupLG : administrative logOP : operator


3-22 47 A2 94UC

EXAMPLES:

S: LNET FL NUMBER=1; NBFL 09:49:17 FL:8 COMMAND COMPLETED.

S:LNET FL; LSFL 09:49:25 FLLOG000 FLAUT001 FLAUT002 FLAUT003 FLAUT004 FLNAD005 FLNAD006 FLNAD007 COMMAND COMPLETED. 8 OBJECTS SELECTED❑


47 A2 94UC 3-23

3.1.10 LNET ID

Purpose

Lists the names of selected ID (iso session control) objects.

Syntax


CLASS = ID

[, OBJECT = ( name-4 [, name-4 ] ) ]

[, NUMBER = 0 ]



OBJECT If two object values are specified, they must beidentical.

EXAMPLE:

S: LNET ID; LSID 11:28:02 BL03 COMMAND COMPLETED. 1 OBJECT SELECTED❑


3-24 47 A2 94UC

3.1.11 LNET IS

Purpose

Lists the names of selected IS (iso session connection) objects.

Syntax


CLASS = IS

[, OBJECT = ( dec-5 [, dec-5 ] ) ]



[, MAP =( { CC | ID | TC }:name-8 [,{ CC | ID | TC }:name-8 ] ) ]

[, ENDS = { 1 | 2 } ]

[, NUMBER = { 0 | 1 } ]




MAP maps the object to a class to which it is associated.CC : channel connection, only if remoteID : iso session controlTC : transport connection, only if remote

ENDS 1 : default, selects only the initiator's end of the localconnection2 : selects both ends of the local connection


47 A2 94UC 3-25

EXAMPLES:

S: LNET IS NUMBER=1; NBIS 10:14:48 IS:8 COMMAND COMPLETED

S: LNET IS; LSIS 10:15:05 18434 19456 20480 21504 22528 23552 24576 25600 COMMAND COMPLETED. 8 OBJECTS SELECTED.❑


3-26 47 A2 94UC

3.1.12 LNET LC

Purpose

Lists the names of selected LC (logical connection) objects.

Syntax


CLASS = LC

[, OBJECT = ( dec-5 [, dec-5 ] ) ]



[, MAP =( {CC|LM|RM|SS|TC}:name-8 [,{CC|LM|RM|SS|TC}:name-8 ] ) ]

[, ENDS = { 1 | 2 } ] [, NUMBER = { 0 | 1 } ]




MAP maps the object to a class to which it is associated.CC : channel connection (if remote LC)LM : local mailboxRM : remote mailboxSS : sessionTC : transport connection (if remote LC)



47 A2 94UC 3-27

EXAMPLES:

S: LNET LC NUMBER=1; NBLC 14:24:27 LC:14 COMMAND COMPLETED.

S: LNET LC; LSLC 14:24:31 8 1029 5122 9216 10241 11264 11268 11269 12290 13317 14:24:31 14341 15364 16388 17413 COMMAND COMPLETED. 14 OBJECTS SELECTED❑


3-28 47 A2 94UC

3.1.13 LNET LG

Purpose

Lists the names of selected LG (administrative log) objects.

Syntax


CLASS = LG

[, OBJECT = ( name-8 [, name-8 ] ) ]



[, NUMBER = { 0 | 1 } ]



MAP AF DSALOG

EXAMPLES:

S: LNET LG NUMBER=1; NBLG 09:50:29 LG:1 COMMAND COMPLETED.

S: LNET LG; LSLG 09:50:36 DSALOG COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 3-29

3.1.14 LNET MB

Purpose

Lists the names of selected MB (mailbox) objects.

Syntax


CLASS = MB

[, OBJECT = ( name-8 [, name-8 ] ) ]

[, STATE = { ENBL | USED | SHUT | DSBL } ]

[, MAP = ( { LC | WS } : name-8 [, { LC | WS } : name-8 ] ) ]

[, VENUE = { PR | IM } ]

[, NUMBER = { 0 | 1 } ]



MAP maps the MB to its associated class:LC : logical connectionWS : workstation

VENUE specifies that only proper (PR) meaning localmailboxes or image (IM) meaning remote mailboxesare selected.


3-30 47 A2 94UC

EXAMPLES:

S: LNET MB NUMBER=1; NBMB 09:51:38 MB:13 COMMAND COMPLETED.

S: LNET MB; LSMB 09:51:45 $LOGFILE $MUX $NAD $NASF BIA FILETRAN FILR IOF MML MML_____ 09:51:45 RBF READER TILS COMMAND COMPLETED. 13 OBJECTS SELECTED❑


47 A2 94UC 3-31

3.1.15 LNET NK

Purpose

Lists the names of selected NK (Internet Network Activity).

Syntax


CLASS = NK

[, OBJECT = ( dec-5 [,dec-5 ] ) ]

[, STATE = USED ]

[, TYPE = IP ]

[, NUMBER = { 0 | 1 }]



TYPE IP: Internet Protocol

NOTE:If NUMBER = 1 and several OCS servers are started, each server answers to thecommand. For example:

LNET NK NUMBER=1;

NBNK hh:mm:ss NK : 1 hh:mm:ss NK : 1 COMMAND COMPLETED


3-32 47 A2 94UC

EXAMPLES:

LNET NK ;

LSNK hh:mm:ss 2 COMMAND COMPLETED. 1 OBJECT SELECTED

LNET NK NUMBER=1;

NBNK hh:mm:ss NK:1 COMMAND COMPLETED.❑


47 A2 94UC 3-33

3.1.16 LNET NR

Purpose

Lists the names of selected NR (network route) objects.

Syntax


CLASS = NR

[, OBJECT = ( name-8 [, name-8 ] ) ]

[, STATE = { ENBL | DSBL } ]

[, TYPE = PTPT ]

[, MAP = ( { PL | TS } : name-8 [, { PL | TS } : name-8 ] ) ]

[, NUMBER = { 0 | 1 } ]



TYPE PTPT

MAP maps the NR to its associated class:PL : physical linkTS : transport station

EXAMPLES:

S: LNET NR NUMBER=1; NBNR 13:45:15 NR:8 COMMAND COMPLETED.

S: LNET NR; LSNR 13:45:19 BL05 BL04 BL17 BL36 BL37 BL38 BL13 DSA5 COMMAND COMPLETED. 8 OBJECTS SELECTED❑


3-34 47 A2 94UC

3.1.17 LNET OP

Purpose

Lists the names of selected OP (operator) objects.

Syntax


CLASS = OP

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = OP ]


[, NUMBER = { 0 | 1 } ]



TYPE OP


EXAMPLES:

S: LNET OP NUMBER=1; NBOP 15:53:40 OP:2 COMMAND COMPLETED.

S: LNET OP; LSOP 15:53:45 OPERATOR OPER1 COMMAND COMPLETED. 2 OBJECTS SELECTED❑


47 A2 94UC 3-35

3.1.18 LNET PL

Purpose

Lists the names of selected PL (physical link) objects.

PL is the addition of LPL and RPL.

RPL is a TNS object only. If TNS exists but has not been started, the commandcannot be executed on PL.




[, OBJECT = ( name-8 [, name-8 ] ) ]


[, VENUE = PR ]

[, NUMBER = { 0 | 1 } ]



MAP maps the LPL to its associated class.CB : cableCT : local controller (LCT)NR : network route


3-36 47 A2 94UC


LNET CLASS=LPL ...

is equivalent to

LNET CLASS=PL VENUE=PR ...

The old TYPE parameter is obsolete.

EXAMPLES:

S: LNET LPL NUMBER=1; NBPL 15:29:35 PL:1 COMMAND COMPLETED.

S: LNET LPL; LSPL 15:29:41 PL503C03 COMMAND COMPLETED. 1 OBJECT SELECTED❑

Syntax for RPL (Remote Physical Link)


CLASS = RPL

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = CSMA ]

[, MAP = ({ CB | CT | NR }:name-8 [,{ CT | CB | NR }:name-8])]

[, VENUE = IM ]

[, NUMBER = { 0 | 1 } ]



47 A2 94UC 3-37


TYPE CSMA or FDDI(if TYPE=FDDI, then CLASS=LPL and VENUE=PR)

MAP maps the RPL to its associated class.CB : cableCT : remote controller (RCT)NR : network route


LNET CLASS=RPL ...

is equivalent to

LNET CLASS=PL VENUE=IM ...

EXAMPLES:

S: LNET RPL NUMBER=1; NBPL 15:44:28 PL:9 COMMAND COMPLETED.

S: LNET RPL; LSPL 15:45:10 BL05 BL04 RPL1MATH BL17 BL36 BL37 BL38 BL13 DSA5 COMMAND COMPLETED. 9 OBJECTS SELECTED❑


3-38 47 A2 94UC

3.1.19 LNET QD

Purpose

Lists the names of selected QD (queue) objects.

Syntax


CLASS = QD


[, STATE = { ENBL | DSBL | USED } ]

[, TYPE = { PROG | USER | DSA } ]


[, NUMBER = { 0 | 1 } ]



47 A2 94UC 3-39


OBJECT the maximum number of alphanumeric charactersdepends on the TYPE of queue.

DSA-terminal-queue used to send messages to anapplication over either a secondary network or aprimary network connecting DSA remote systems.

Since the total string including . is limited to 12alphanumeric characters, the following restrictions areimposed:

− either rsys-name (name-4) is reduced to 3 alphanumericcharacters, if mailbox-name occupies the maximumof 8 alphanumeric characters

− or mailbox-name (name-8) is reduced to 7alphanumeric characters, where rsys-name occupiesthe maximum of 4 alphanumeric characters.



EXAMPLES:

S: LNET QD NUMBER; NBQD 14:50:09 QD:9 COMMAND COMPLETED.

S: LNET QD; LSQD 14:49:53 QUEUE1 QUEUE2 QUEUE3 QUEUE4 QUEUE5 BC1A.QUEUE6 QUEUE7 BC1A.QUEUE8 BC1A.QUEUE9 COMMAND COMPLETED. 9 OBJECTS SELECTED❑


3-40 47 A2 94UC

3.1.20 LNET RB

Purpose

Lists the names of selected RB (Route information Base) objects.

Syntax


CLASS = RB


[, TYPE = CLNS ]


[, NSAP = NSAP_address ]

[, NSAP_MASK = NSAP_mask ]

[, SNPA = SNPA_string ]

,NUMBER = 1



TYPE CLNS

NSAP_ID An identifier name for the Network Service AccessPoint.

NSAP a code for the remote Network Service Access Point(from 0 to 40 digits).

NSAP_MASK a string of bits, representing the mask, left justified, foran equivalent class (optional, from 0 to 40 digits).


47 A2 94UC 3-41

SNPA a string of from 0 to 40 digits giving the SNPA(SubNetwork Physical Address).

NOTE:Several OCS servers can answer to the command. For example:

LNET RB NUMBER=1;

NBRB hh:mm:ss RB : 10 hh:mm:ss RB : 20 COMMAND COMPLETED

EXAMPLE:

LNET RB NUMBER=1;

NBRB hh:mm:ss RB:10 COMMAND COMPLETED❑


3-42 47 A2 94UC

3.1.21 LNET SA

Purpose

Lists the names of selected SA (subdomain) objects.

Syntax


CLASS = SA

[, OBJECT = ( name-8 [, name-8 ] ) ]

[, TYPE = ISO ]

[, MAP = { CT | SY }: name-8 ]

[, NSAP = addr-40 ]

[, NUMBER = { 0 | 1 } ]



TYPE ISO




47 A2 94UC 3-43

EXAMPLES:

S: LNET SA NUMBER=1; NBSA 11:46:11 SA:6 COMMAND COMPLETED.

S: LNET SA; LSSA 11:46:15 SDOM10 SDOM5 SDOM4 SDOM3 SDOM2 SDOM1 COMMAND COMPLETED. 6 OBJECTS SELECTED❑


3-44 47 A2 94UC

3.1.22 LNET SB

Purpose

Lists the names of selected SB (statistics block) objects.

Syntax


CLASS = SB

[, OBJECT = ( name-8 [, name-8 ] ) ]

[, STATE = { ENBL | LOCK ]

[, TYPE = SMPL ]

[, MAP = { CC | IS | LC | PC | SS | TC | NK } : dec-5 ]

[, NUMBER = { 0 | 1 } ]



TYPE SMPL

MAP maps the connection object to the SB object:CC : channel connection (cc index of DNS or CNS7)IS : iso session connectionLC : logical connectionPC : physical connectionSS : sessionTC : transport connectionNK : internet network activity


47 A2 94UC 3-45

EXAMPLES:

S: LNET SB NUMBER=1; NBSB 14:14:41 SB:193 COMMAND COMPLETED.

S: LNET SB MAP=CC:0; LSSB 14:14:52 _SBCC2 _SBCC1 _SBCC0 COMMAND COMPLETED. 3 OBJECTS SELECTED❑


3-46 47 A2 94UC

3.1.23 LNET SC

Purpose

Lists the names of selected SC (session control) objects.

SC is the addition of LSC and RSC.

Syntax for LSC (Local Session Control)


CLASS = { LSC | SC }

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = DSA ]

[, VENUE = PR ]

[, NUMBER = { 0 | 1 } ]



TYPE DSA


LNET CLASS=LSC ...

is equivalent to

LNET CLASS=SC VENUE=PR ...


47 A2 94UC 3-47

EXAMPLES:

S: LNET LSC NUMBER=1; NBSC 16:11:08 SC:1 COMMAND COMPLETED.S: LNET LSC; LSSC 16:11:36 BL03 COMMAND COMPLETED. 1 OBJECT SELECTED❑

Syntax for RSC (Remote Session Control)


CLASS = { RSC | SC }

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = DSA ]

[, MAP = ( SR : name-8 [, SR : name-8 ] ) ]

[, VENUE = IM ]

[, NUMBER = { 0 | 1 } ]



3-48 47 A2 94UC


TYPE DSA

MAP maps the RSC to its associated SR (session route).


LNET CLASS=RSC ...

is equivalent to

LNET CLASS=SC VENUE=IM ...

EXAMPLES:

S: LNET RSC NUMBER=1; NBSC 16:12:31 SC:309 COMMAND COMPLETED.

S: LNET RSC OBJECT=(BC00,BC05); LSSC 16:14:29 BC00 BC01 BC02 BC15 BC17 BC07 BC19 BC05 COMMAND COMPLETED. 8 OBJECTS SELECTED❑


47 A2 94UC 3-49

3.1.24 LNET SP

Purpose

Lists the names of selected SP objects (SAP addresses).

Syntax


CLASS = SP

[, OBJECT = ( dec-5 [, dec-5 ] ) ]

[, TYPE = SSAP ]

[, MAP = ID : name-4 ]

[, NUMBER = { 0 | 1 } ]



TYPE describes the type of object appropriate to the SP.

SSAP : session service access point

MAP maps the SP to its associated ID.

EXAMPLES:

S: LNET SP NUMBER=1; NBSP 09:31:06 SP:1 COMMAND COMPLETED.

S: LNET SP; LSSP 09:31:13 18434 COMMAND COMPLETED. 1 OBJECT SELECTED❑


3-50 47 A2 94UC

3.1.25 LNET SR

Purpose

Lists the names of selected SR (session route) objects.

Syntax


CLASS = SR

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = { ISO | GC64 } ]


[, NUMBER = { 0 | 1 } ]




ISO : ISO networkGC64 : PSI channel for DPS 7000 or link betweenDPS 7000 and FCP7




47 A2 94UC 3-51

EXAMPLES:

S: LNET SR NUMBER=1; NBSR 14:57:34 SR:52 COMMAND COMPLETED.

S: LNET SR OBJECT=(BC000001,BC050001); LSSR 14:58:08 BC000001 BC010001 BC020001 BC030001 BC040001 BC050001 COMMAND COMPLETED. 6 OBJECTS SELECTED❑


3-52 47 A2 94UC

3.1.26 LNET SS

Purpose

Lists the names of selected SS (session) objects.

Syntax


CLASS = SS

[, OBJECT = ( dec-5 [, dec-5 ] ) ]



[, MAP = LC : name-8 ]

[, ENDS = { 1 | 2 } ]

[, NUMBER = { 0 | 1 } ]




MAP maps the object to its associated LC (logicalconnection).



47 A2 94UC 3-53

EXAMPLES:

S: LNET SS NUMBER=1; NBSS 14:26:12 SS:15 COMMAND COMPLETED.

S: LNET SS; LSSS 14:26:17 8 1029 1030 5122 9216 10241 11264 11268 11269 12290 14:26:17 13317 14341 15364 16388 17413 COMMAND COMPLETED. 15 OBJECTS SELECTED❑


3-54 47 A2 94UC

3.1.27 LNET SY

Purpose

Lists the names of selected SY (system) objects.

Syntax for LSYS (Local System)


CLASS = { LSYS | SY }

[, OBJECT = ( name-4 [, name-4 ] ) ]

[, STATE = USED ]

[, VENUE = PR ]

[, NUMBER = { 0 | 1 } ]


Parameters: (See LNET command)


LNET CLASS=LSYS ...

is equivalent to

LNET CLASS=SY VENUE=PR ...


47 A2 94UC 3-55

EXAMPLES:

S: LNET LSYS NUMBER=1; NBSY 16:55:03 SY:1 COMMAND COMPLETED.

S: LNET SY VENUE=PR; LSSY 16:55:11 BL03 COMMAND COMPLETED. 1 OBJECT SELECTED❑

Syntax for RSYS (Remote System)


CLASS = { RSYS | SY }

[, OBJECT = ( name-4 [, name-4 ] ) ]

[, STATE = USED ]

[, MAP = SA : name-8 ]

[, VENUE = IM ]

[, NUMBER = { 0 | 1 } ]



MAP displays the RSYS associated to the given subdomain.


LNET CLASS=RSYS ...

is equivalent to

LNET CLASS=SY VENUE=IM ...


3-56 47 A2 94UC

EXAMPLES:

S: LNET SY NUMBER=1 VENUE=IM; NBSY 09:56:24 SY:32 COMMAND COMPLETED.

S:LNET RSYS; LSSY 09:56:29 09:56:29 BC1B BC1A BC19 BC18 BC17 BC16 BC15 BC14 BC13 BC12 BC11 BC10 BC0F BC0E BC0D BC0C BC0B BC0A BC09 BC08 BC07 BC06 BC05 BC04 BC03 BC02 BC01 BC00 BR12 BR10 BF12 BF11 COMMAND COMPLETED. 32 OBJECTS SELECTED❑


47 A2 94UC 3-57

3.1.28 LNET TC

Purpose

Lists the names of selected TC (transport connection) objects.

Syntax


CLASS = TC

[, OBJECT = ( dec-5 [, dec-5 ] ) ]


[ { ISO [,MAP = ({ LC|TS }:name-8 [,{ LC|TS }:name-8])]}][, TYPE = { DIWS [,MAP = TS:name-8 ]}][ { CLNS [,MAP = TS:name-8 ]}][ { INET [,MAP = TS:name-8 ]}]

[, NUMBER = { 0 | 1 } ]



TYPE ISO for TC via ISLDIWS for TC using the ISO stack with Null Internet ofthe OCS Front End (in this case, STATE=ENBL doesnot apply).CLNS for TC using the ISO stack with Full Internet ofthe OCS Front End (in this case, STATE=ENBL doesnot apply).INET for TC using OSI/DIWS over the top of theTCP/IP layers of OCS Front End.

MAP maps the TC to its associated class:

LC : logical connectionTS : transport station


3-58 47 A2 94UC

NOTE:If NUMBER = 1 and several servers (TNS, OCS) are started, each serveranswers to the command. For example:

LNET TC NUMBER=1;

NBTC hh:mm:ss TC : 5 hh:mm:ss TC : 7 COMMAND COMPLETED

EXAMPLES:

S: LNET TC NUMBER=1; NBTC 09:57:12 TC:27 COMMAND COMPLETED.

S: LNET TC; LSTC 09:57:18 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 COMMAND COMPLETED. 27 OBJECTS SELECTED

S: LNET TC; LSTC 09:57:18 84 COMMAND COMPLETED. 1 OBJECT SELECTED

S: LNET TC NUMBER=1; LSTC 09:57:18 TC:1 COMMAND COMPLETED.❑


47 A2 94UC 3-59

3.1.29 LNET TS

Purpose

Lists the names of selected TS (transport station) objects.

TS is the addition of LTS and RTS.

Syntax for LTS (Local Transport Station)


CLASS = { LTS | TS }

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = ISO ]


[, VENUE = PR ]

[, NUMBER = { 0 | 1 } ]



TYPE ISO

MAP maps the LTS to its associated class:



3-60 47 A2 94UC


LNET CLASS=LTS ...

is equivalent to

LNET CLASS=TS VENUE=PR ...

NOTE:If NUMBER = 1 and several servers (TNS, OCS) are started, each serveranswers to the command. For example:

LNET TS NUMBER=1;

NBTS hh:mm:ss TS : 1 hh:mm:ss TS : 1 COMMAND COMPLETED

EXAMPLES:

S: LNET LTS NUMBER=1; NBTS 10:17:33 TS:1 COMMAND COMPLETED.

S: LNET TS VENUE=PR; LSTS 10:17:38 TNS COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 3-61




[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = ISO ]


[, VENUE = IM ]

[, NUMBER = { 0 | 1 } ]



TYPE ISO.




LNET CLASS=RTS ...

is equivalent to:

LNET CLASS=TS VENUE=IM ...


3-62 47 A2 94UC

EXAMPLES:

S: LNET TS NUMBER=1 VENUE=IM; NBTS 10:18:17 TS:8 COMMAND COMPLETED.

S: LNET RTS; LSTS 10:18:23 BL05 BL04 BL13 BL17 BL36 BL37 BL38 DSA5 COMMAND COMPLETED. 8 OBJECTS SELECTED

S: LNET TS NUMBER = 1 NBTS hh:mm:ss TS = 2 COMMAND COMPLETED

S: LNET TS LSTS hh:mm:ss TNS BL38 COMMAND COMPLETED. 2 OBJECTS SELECTED❑

Syntax for OCS


CLASS = TS

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = { COTP | INET }]

[, NUMBER = { 0 | 1 } ]



47 A2 94UC 3-63


TYPE COTP/INET.

EXAMPLE:

S: LNET TS NUMBER = 1

NBTS hh:mm:ss TS = 2 COMMAND COMPLETED❑


3-64 47 A2 94UC

3.1.30 LNET WS

Purpose

Lists the names of WS (workstation) objects.

Syntax


CLASS = WS

[, OBJECT = ( name-8 [, name-8 ] ) ]


[, NUMBER = { 0 | 1 } ]



MAP maps the WS to its associated MB (mailbox).

EXAMPLES:

S: LNET WS NUMBER=1; NBWS 13:54:16 WS:11 COMMAND COMPLETED.

S: LNET WS; LSWS 13:53:21 ASFWKS BIA IOF IQSUFN21 LOGWKS MML NADWKS1 RBF READER SPAW 13:54:21 UFTWS COMMAND COMPLETED. 11 OBJECTS SELECTED❑


47 A2 94UC 3-65

3.2 MDNET (MODIFY_NETWORK)

Purpose

Modifies the state and/or attributes of selected network objects.

General Syntax

{ MDNET }{ }{ MODIFY_NETWORK }

CLASS = class


[, NEW_STATE = { ENBL | LOCK } ]

[, STATE = { ENBL | LOCK | USED | DOWN | DSBL | SHUT | TEST }

[, TYPE = type ]



[, MORE = { 0 | 1 } ]


NOTES:1. Detailed syntax for each class is given separately.

2. Within each class, the modification parameters are separate from theselection parameters. For a given MDNET command, one and only onemodification parameter may be specified.


3-66 47 A2 94UC

Parameters


For the DPS 7, the network is configured byNETGEN.For the CNP 7, the network is configured by CNS 7SYSGEN.For the Datanet, the network is configured by DNSSYSGEN.For other systems, refer to the appropriate networkingdocumentation.


Syntax Rules

MDNET...OBJECT=name:selects one objectMDNET...OBJECT=(name1,name2):selects all objectsfrom name1 up to name2MDNET...OBJECT=(name,*):selects all objectsstarting from nameMDNET...OBJECT=(*,name):selects all objects frombeginning up to nameMDNET...OBJECT=* or omitted:selects all objectswithin class

NEW_STATE state to which the object selected is to be set.The effects of NEW_STATE for each object is treatedin the appropriate command. See also STATE.

STATE describes the state of the objectENBL : object is availableLOCK : object is unavailableUSED : object is being usedDOWN : object has failedDSBL : object inoperable due to lower level failuresSHUT : object taken out of configurationTEST : object under test





47 A2 94UC 3-67

MORE 0: default1: displays new screen for class-specific parameters ofheterogeneous systems. Default is set to 1 if nomodification parameter has been specified.

class-specific parameters See the appropriate MDNET commands.

NOTE:The description of the command given separately for each class is availablefrom GCOS 7 release V6. When the command is sent to a remote systemsupporting a standard DSAC NAD, care must be taken to ensure that thissystem is able to support the command and its corresponding parameters.

The general syntax of the command allows specifying common parameters.MORE allows prompting class-specific parameters which are not described inGCOS 7 commands, if these parameters are needed for a given class.



MDNET


UPOBJECT=name1OBJECT=(name1,name2)STATE=stateTYPE=typeMAP=(map1[map2])NEW_STATE=state

name1name1/name2-OS state-OT type-OM map1[map2]-ST state


• For the Datanet, DNS System Operations



3-68 47 A2 94UC

3.2.1 MDNET AC

Purpose

Modifies the state of selected AC (administrative correspondent) objects.

Syntax


CLASS = AC

[, OBJECT = ( name-8 [, name-8 ] ) ]

, NEW_STATE = { ENBL | LOCK }





Parameters: (See MDNET Command)

TYPE describes the type of object appropriate to the ACs.ASF : administrative storage facilityAUT : administrative utilityMUX : multiplexorNAD : node administratorNCC : network control centerNOI : network operator interface



47 A2 94UC 3-69

Modification Parameter

NEW_STATE=LOCK:− close session on selected AC(s)− release dynamic AC(s) from administrative tables.

EXAMPLE:

S: MDNET AC LDSALOG NEW_STATE=LOCK; UPAC 14:47:27 --> NAME:LDSALOG OLD_STATE:ENBL NEW_STATE:LOCK COMMAND COMPLETED. 1 OBJECT SELECTED❑


3-70 47 A2 94UC

3.2.2 MDNET AF

Purpose

Modifies the state of selected AF (administrative function) objects.

Syntax


CLASS = AF

[, OBJECT = ( name-8 [, name-8 ] ) ]







TYPE describes the type of object appropriate to the AF.

ASF : administrative storage facilityAUT : administrative utilityMUX : multiplexorNAD : node administratorNCC : network control centerNOI : network operator interface

MAP maps the AF to its associated AG.


47 A2 94UC 3-71


NEW_STATE=LOCK:− close session on AC(s) established with selected

AF(s)− release dynamic AC(s) from administrative tables.

EXAMPLE:

S: MDNET AF DSALOG NEW_STATE=LOCK; UPAF 14:48:30 --> NAME:DSALOG OLD_STATE:ENBL NEW_STATE:LOCK COMMAND COMPLETED. 1 OBJECT SELECTED❑


3-72 47 A2 94UC

3.2.3 MDNET AG

Purpose

Modifies the state of selected AG (administrative group) objects.

Syntax


CLASS = AG

[, OBJECT = ( name-8 [, name-8 ] ) ]

NEW_STATE = { ENBL | LOCK }






TYPE describes the type of object appropriate to the AG:

ASF : administrative storage facilityAUT : administrative utilityMUX : multiplexorNAD : node administratorNCC : network control centerNOI : network operator interfaceOP : operator

MAP maps the AG to its associated AF.


47 A2 94UC 3-73


NEW_STATE=LOCK: close session established on AC(s) belonging toselected AG(s),release dynamic AC(s) from administrative tables.

EXAMPLE:

S: MDNET AG RLNAD NEW_STATE=LOCK; UPAG 14:57:36 --> NAME:RLNAD OLD_STATE:LOCK NEW_STATE:ENBL COMMAND COMPLETED. 1 OBJECT SELECTED❑


3-74 47 A2 94UC

3.2.4 MDNET AL

Purpose

Modifies a local NSAP represented by an AL (Address List) object.

Syntax


CLASS = AL

[, OBJECT = ( name-8 )]

NEW_NSAP = NSAP_address


Parameters

See MDNET Command

Modification Parameters:

NEW_NSAP NSAP address: a code for the local Network ServiceAccess Point (from 0 to 40 digits).

EXAMPLE:

S:MDNET AL OBJECT=AL01 NEW_NSAP=1234567890;

UPAL hh:mm:ss ---> NAME: AL01 OLD_NSAP=ABCDEF NEW_NSAP=1234567890 COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 3-75

3.2.5 MDNET CH

Purpose

Modifies the state and/or attributes of selected CH (channel) objects.

Syntax

{ MDNET }{ }{ MODIFY_NETWORK }CLASS = CH[, OBJECT = ( name-8 [, name-8 ] ) ]



[, TYPE = PSI ]

[, MAP=( {CC|CT|SC|SR|SV}:name-8 [,{CC|CT|SC|SR|SV }:name-8 ] ) ]

[, SURVEY = { 0 | 1 } ]




MAP maps the CH to its associated class:

CC : channel connectionCT : controllerSC : session controlSR : session routeSV : server


3-76 47 A2 94UC


NEW_STATE: ENBL : channel availableLOCK : channel closed

SURVEY: watchdog efficiency0 : watchdog off1 : watchdog on

EXAMPLE:

S: MDNET CH CC04 NEW_STATE=ENBL; UPCH 15:19:11 --> NAME:CC04 OLD_STATE:DSBL NEW_STATE:ENBL COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 3-77

3.2.6 MDNET CT

Purpose

Modifies the state and/or attributes of selected CT (controller) objects.




[, OBJECT = ( name-8 [, name-8 ] ) ]



[ { TYPE=ISL [,MAP=({ PL|SV }:name-8 [,{ PL|SV }:name-8 ] ) ] } ][,{ } ][ { TYPE=PSI [,MAP=({ CH|SV }:name-8 [,{ CH|SV }:name-8 ] ) ] } ]

[, VENUE = PR ]



TYPE ISL for CNP 7 connection : mapping to PL or SVPSI for Datanet connection : mapping to CH or SV

MAP maps the LCT to its associated class.CH : channel for PSI typePL : physical link for ISL typeSV : server for both ISL and PSI types


MDNET CLASS=LCT ...

is equivalent to:

MDNET CLASS=CT VENUE=PR ...


3-78 47 A2 94UC

Modification Parameter:

NEW_STATE: ENBL : controller availableLOCK : controller closed

EXAMPLE:

S: MDNET CT NEW_STATE=LOCK; UPCT 15:20:01 --> NAME:EA01 OLD_STATE:ENBL NEW_STATE:LOCK --> NAME:CC01 OLD_STATE:USED NEW_STATE:LOCK --> NAME:CC02 OLD_STATE:DSBL NEW_STATE:LOCK COMMAND COMPLETED. 3 OBJECTS SELECTED❑



CLASS = { RCT | CT }

[, OBJECT = ( name-8 [, name-8 ] ) ]

[, TYPE = ISL ]

[, MAP = ( PL : name-8 ) ]

[, VENUE = IM ]

, RMLOAD = { 0 | 1 }



47 A2 94UC 3-79





MDNET CLASS=RCT ...

is equivalent to

MDNET CLASS=CT VENUE=IM ...


RMLOAD: remote loading capability of RCT0: disable1: enable

EXAMPLE:

S: MDNET CLASS=CT CT_BL37 VENUE=IM RMLOAD=0; UPCT 15:22:46 --> NAME:CT_BL37 OLD_RMLOAD:1 NEW_RMLOAD:0 COMMAND COMPLETED. 1 OBJECT SELECTED❑


3-80 47 A2 94UC

3.2.7 MDNET FL

Purpose

Modifies the state and/or attributes of selected FL (filter) objects.

Syntax


CLASS = FL

[, OBJECT = ( name-8 [, name-8 ] ) ]



[, TYPE = { IN | OUT } ]

[ { AF : name-8 [, { AC | AG } : name-8 ] } ][, MAP = ( { } ) ][ { {AC | AG | LG | OP } : name-8 [, AF : name-8 ] } ]


[, NEW_TYPE = { IN | OUT } ]

[, NEW_LOGIC = { INCL | EXCL | OBLI } ]

[, L_DOMAIN = dec-1 ] [, H_DOMAIN = dec-1 ]

[, L_POWER = dec-1 ] [, H_POWER = dec-1 ]

[, L_CLASS = dec-3 ] [, H_CLASS = dec-3 ]

[, L_CODE = dec-3 ] [, H_CODE = dec-3 ]

[, L_LEVEL = dec-3 ] [, H_LEVEL = dec-3 ]

[, SYSTEM1 = name-4 ] [, SYSTEM2 = name-4 ]



47 A2 94UC 3-81



LOGIC INCL : inclusive (select if criteria match)EXCL : exclusive (reject if criteria match)OBLI : obligatory (reject if criteria do not match)

MAP maps the FL to its associated class.AC : administrative correspondentAF : administrative functionAG : administrative groupLG : administrative logOP : operator


NEW_STATE ENBL: filter is availableLOCK: filter is closed

the following parameters are allowed only if one filter is selected.

NEW_TYPE IN : inputOUT : output

NEW_LOGIC INCL: inclusive (select if criteria match)EXCL: exclusive (reject if criteria match)OBLI: obligatory (reject if criteria do not match)

L_DOMAIN, H_DOMAIN low_domain must be less than or equal tohigh_domain0: DSA or OSI communications1: Administration of local system2: Application administration3: Control of administration4: Security administration

L_POWER, H_POWER low_power must be less than or equal to high_power0: Message reporting event1: Information display command2: Test and maintenance command3: Control and modification command


3-82 47 A2 94UC

L_CLASS, H_CLASS low_class must be less than or equal to high_class1: XC cross network monitoring2: XN cross network transfers3: SU system startup control4: PL physical line5: LL logical line6: NS network subscription7: NR network route (path)8: VC virtual circuit9: TS transport station10: MB mailbox11: SS session12: LC logical connection13: CT communications controller14: DV terminal device15: AF administrative function18: FX administrative function connection19: RS executive (remote subsystem)19: EX executive (local OS)20: SY system21: TC transport connection22: WS workstation23: NC network connection24: SD session type descriptor25: CH intersystem channel26: SN station (terminal)27: CL terminal cluster28: LK link connection29: PC physical connection30: SC session control31: CC channel connection34: FL output filter management (in NAD)35: SB statistic block36: NA additional control of NAD itself38: MU mailbox user43: AC administrative correspondent44: SR session route45: LD logical terminal device48: OP operator49: LG log control


47 A2 94UC 3-83

51: TL diagnostic application control53: DF user application control54: FT file transfer56: AG administrative group57: CO correspondent58: PS physical subscription59: SG subscription group60: SX station connection61: LX logical device connection62: DX device connection63: UD user descriptor64: LN login descriptor65: CD connection descriptor66: TX terminal mailbox extension68: DP device pool69: WM welcome message70: TU terminal unit71: MD terminal model74: SW software module75: NU network user86: AD osi address87: ET osi layer entity title88: SP sap address90: CB cable91: AI address information95: AL address list96: AP application97: AX application connection98: UT user of transport100: VH vehicle (system type specific)101: UA user agent102: AS association105: IS iso session connection106: ID iso session descriptor110: RQ dsas request (gcos-8 specific)111: RB rib - routing information base112: ML multlink113: MK multilink connection114: IK internet activity115: NK network internet activity120: FR ftam regime121: FS ftam file selection regime122: FE ftam file exchange (access and transfer regime)


3-84 47 A2 94UC

123: FM ftam file management130: PA printer server agent140: MA message transfer server agent141: MQ message queue of ma142: MM mailbox of ma143: MI mail item150: FA document file server agent151: FF file of document file server agent152: FD folder of a file of ff160: DA directory server agent201 - 255: reserved for user-defined objects

L_CODE, H_CODE low_code must be less than or equal to high_code

1 - 49: general commands and events

1: NB report NUMBER of objects2: LS LIST objects3: DA DISPLAY common attributes of objects4: HR report HISTORY (statistics) of objects4: GH get HISTORY (statistics) of objects5: UP UPDATE object state or attributes6: MP alter MAPPING of objects to other objects7: CR CREATE object7: OP object OPEN report7: EX EXECUTE8: DL DELETE object8: CL object CLOSE report12: GA GET all ATTRIBUTES of an object14: ER ERROR events report15: TH THRESHOLD violation report17: OF OPEN FAILURE event report

50 - 149: class-specific events and error reports

50: TX text broadcast50: SU submission51: SF submission failed51: RL reload system51: DS dissociation51: SW swap52: DE delivery52: LD load system52: AS association52: RI neighbor requests initialization53: DF delivery failed53 DP dump system54: RE reception


47 A2 94UC 3-85

54: ST start system55: TR transmission56: TF transmission failed57: DI discard60: CS completed startup100: FC file creation101: FD file deletion102: FN file rename103: AC attribute change150 - 255: implemention specific events and error reports150: EM executive % use (per cpu on multi-cpu machine)160: DR diverting

L_LEVEL, H_LEVEL low_level must be less than or equal to high_level0: Response to NUMBER or LIST command2: Response to ATTRIBUTE or HISTORY reporting commands4: unimportant errors not usually user-visible6: answer to modification command8: impossible answer by NAD and rejected10: standard events and probe points12: important events14: inline test messages to operators16 and above: important errors22 and above: operator intervention suggested24 and above: operator intervention required26 and above: part of distributed system failed or shutdown32 and above: fatal errors

SYSTEM1: name of a system for filtering

SYSTEM2: only one system name is allowed

EXAMPLE:

S: MDNET FL FLLOG000 NEW_STATE=LOCK; UPFL 15:36:21 --> NAME:FLLOG000 OLD_STATE:ENBL NEW_STATE:LOCK COMMAND COMPLETED. 1 OBJECT SELECTED❑


3-86 47 A2 94UC

3.2.8 MDNET LG

Purpose

Modifies the state of selected LG (administrative log) objects.

NOTE:No modification is performed if STATE=DOWN and OBJECT=DSALOG.

Syntax


CLASS = LG

[, OBJECT = ( name-8 [, name-8 ] ) ]






NEW_STATE no modification is performed if STATE=DOWN.

OBJECT no modification is performed if OBJECT=DSALOG.

MAP AF DSALOG


NEW_STATE ENBL: the logfile is availableLOCK: the logfile is closed


47 A2 94UC 3-87

EXAMPLE:

S: MDNET LG USERLOG NEW_STATE=LOCK; UPLG 15:43:24 --> NAME:USERLOG OLD_STATE:ENBL NEW_STATE:LOCK COMMAND COMPLETED. 1 OBJECT SELECTED❑


3-88 47 A2 94UC

3.2.9 MDNET OP

Purpose

Modifies the state of selected OP (operator) objects.

Syntax


CLASS = OP

[, OBJECT = ( name-8 [, name-8 ] ) ]



[, TYPE = OP ]




TYPE OP



NEW_STATE: setting of network reportingENBL: the OP is enabledLOCK: the OP is locked


47 A2 94UC 3-89

EXAMPLE:

S: MDNET OP OPERATOR NEW_STATE=ENBL; UPOP 15:55:22 --> NAME:OPERATOR OLD_STATE:LOCK NEW_STATE:ENBL COMMAND COMPLETED. 1 OBJECT SELECTED❑


3-90 47 A2 94UC

3.2.10 MDNET PL

Purpose

Modifies the state of selected PL (physical link) objects.


{ MDNET }{ MODIFY_NETWORK }


[, OBJECT = ( name-8 [, name-8 ] ) ]



[, TYPE = CSMA ]

[, MAP =( { CB | CT | NR }:name-8 [,{ CB | CT | NR }:name-8 ] ) ]

[, VENUE = PR ]



TYPE CSMA

MAP maps the LPL to its associated class.

CB : cableCT : local controller (LCT)NR : network route


MDNET CLASS=LPL ...is equivalent to:

MDNET CLASS=PL VENUE=PR ...


47 A2 94UC 3-91


NEW_STATE ENBLLOCK

EXAMPLE:

S: MDNET LPL PL503C03 NEW_STATE=ENBL; UPPL 09:19:29 --> NAME:PL503C03 OLD_STATE:LOCK NEW_STATE:ENBL COMMAND COMPLETED. 1 OBJECT SELECTED❑


3-92 47 A2 94UC

3.2.11 MDNET QD

Purpose

Modifies the state and/or attributes of data formats in an MCS queue. The queuemust not be involved in a connection with a terminal.

Syntax


CLASS = QD


[,NEW_STATE = { ENBL | DSBL }]

[,STATE = { ENBL | DSBL | USED }]

[,TYPE = { PROG | USER | DSA } ]

[,MAP = MB : name-8 ]

[,{ IM | INMODE } = { NL | MK | UN } ]

[,{ OM | OUTMODE } = { NL | UN } ]

[,BLOCKING = { YS | NO } ] [,NBLINES = dec-4 ] [,LINELG = dec-4 ]

[,SYSTEM = { #WSYS | name-4 } ]


47 A2 94UC 3-93


OBJECT The maximum number of alphanumeric charactersdepends on the TYPE of queue.

DSA-terminal-queue used to send messages to anapplication over either a secondary network or aprimary network connecting DSA remote systems.

Since the total string including . is limited to 12alphanumeric characters, the following restrictions areimposed:

− either rsys-name (name-4) is reduced to 3alphanumeric characters, if mailbox-name occupiesthe maximum of 8 alphanumeric characters

− or mailbox-name (name-8) is reduced to 7alphanumeric characters, where rsys-name occupiesthe maximum of 4 alphanumeric characters.




NEW_STATE ENBLLOCK

The following parameters are applicable only if the queue is USER or DSA.

INMODE | IM Specifies the format of messages passed from theterminal to the MCS application.

MK : MARK

denotes input mark mode and corresponds to theIM=MARK option in the QD (QUEUE) directive atnetwork generation whereby

− headers are passed as marks of the format><U03abc

− all hexadecimal control codes are translated intotheir corresponding mark formats


3-94 47 A2 94UC

− character encoding and repeat formats are translated

− other characters including control codes in markformat are passed without translation.

UN : UNEDITED

denotes input unedited mode and corresponds to theIM=UNEDITED option in the QD (QUEUE) directiveat network generation whereby

− headers are passed as marks of the format><U03abc

− other characters, including control codes in markformat, character encoding and repeat formats, arepassed without translation.

NL : NORMAL

denotes input normal mode and corresponds to theIM=NORMAL option in the QD (QUEUE) directive atnetwork generation whereby

− headers and control codes, except HT and ESC, arenot passed


− other characters, including control codes in markformat are passed without translation.

OUTMODE | OM Specifies the format of messages passed from the MCSapplication to the terminal

UN : UNEDITED

denotes output unedited mode and corresponds to theOM=UNEDITED option in the QD (QUEUE)directive at network generation whereby

− the user can provide VIP-headers in the mark format><U03abc

− other characters, including control codes in markformat, character encoding and repeat formats, arepassed without translation.


47 A2 94UC 3-95

NL : NORMAL

denotes output normal mode and corresponds to theOM=NORMAL option in the QD (QUEUE) directiveat network generation whereby

− the user can provide VIP-headers in the mark format><U03abc


− unreserved codes and inapplicable hexadecimalcontrol codes are translated into character encodingformat ><Cab

− control codes in mark format specific to the terminalare translated into hexadecimal values

− all other characters, including applicablehexadecimal control codes, are passed withouttranslation.

BLOCKING When set to 1, MAM performs blocking on currentlydefined LINELG and NBLINES.When set to 0, blocking is not performed.

LINELG Applies only if BLOCKING option is selected. Itdefines the logical line length for automatic editing.

NBLINES Represents the maximum number of lines per message.This parameter is meaningful only with messageblocking and is used to alter:

− either the NBLOCKS value as specified originallyin the QD (QUEUE) directive at network generation

− or a subsequent NBLINES value specified in theMDQED network control command previouslyissued during the course of the currentcommunications session.


3-96 47 A2 94UC

The length of the message transmitted is defined by thealgorithm:

LINELG x NBLINES = maximum message lengthAny part of a message exceeding the maximummessage length will be truncated. In order to avoidthis situation occurring, the operator can, during thecourse of the current communications session,dynamically alter either or both of these values of anyof the terminal-queues as defined under OBJECT.

EXAMPLE:

S: MDNET QD QUEUE1 NEW_STATE=DSBL; UPQD 14:54:16 --> NAME:QUEUE1 OLD_STATE:ENBL NEW_STATE:DSBL COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 3-97

3.2.12 MDNET RB

Purpose

Modifies a selected RB (Route information Base) object.

It is not possible to modify the dynamic RB which is created by the ES-IS protocoland whose name begins with the character "$".

Syntax


CLASS = RB

{ NEW_STATE ={ ENBL | LOCK }}

{ NEW_SNPA = SNPA_string }


[, TYPE = CLNS ]


[, NSAP = NSAP_address]

[, NSAP_MASK = NSAP_mask]

[, SNPA = SNPA_string]



3-98 47 A2 94UC


TYPE CLNS


NEW_STATE ENBLLOCK

NEW_SNPA a string of 12 hexadecimal digits giving the MACaddress of the next hop.

EXAMPLE:

MDNET RB NSAP_ID=xxxx NEW_STATE = LOCK

UPRB hh:mm:ss ---> OLD_STATE = ENBL NEW_STATE = LOCK COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 3-99

3.2.13 MDNET SA

Purpose

Modifies the state of a passthrough system associated to the selected SA(subdomain) objects.

Syntax


CLASS = SA

[, OBJECT = ( name-8 [, name-8 ] ) ]

[, TYPE = ISO ]

[ MAP = { CT | SY }: name-8 ]

[, NSAP = addr-40 ]

SY_STATE = { ENBL | LOCK }



TYPE ISO




3-100 47 A2 94UC


SY_STATE specifies the state of the SY (passthrough system)associated with SA.

EXAMPLES:

S: DNET SA SDOM1 CODE=LONG; GASA 13:59:03 --> NAME:SDOM1 TYPE:ISO NSAP:01 SYSTEM:BP10 SY_STATE:ENBL COS:0:7 COMMAND COMPLETED. 1 OBJECT SELECTED

S: MDNET SA SDOM1 MAP=SY:BP10 SY_STATE=LOCK; UPSA 13:59:46 --> NAME:SDOM1 OLD_SY_STATE:ENBL NEW_SY_STATE:LOCK COMMAND COMPLETED. 1 OBJECT SELECTED

S: DNET SA SDOM1 CODE=LONG; GASA 13:59:58 --> NAME:SDOM1 TYPE:ISO NSAP:01 SYSTEM:BP10 SY_STATE:LOCK COS:0:7 COMMAND COMPLETED. 1 OBJECT SELECTED

BCA2: crivmo ea81 ivmo_a NC54 command : CRIVMO response from EA81 NC58 IVMO# : 07 IVMO_NAME : IVMO_A NC54 command : CRIVMO command complete

BCA2: crivmo ea81 ivmo_a NC54 command : CRIVMO response from EA81 NC54 command : CRIVMO ERROR : IVMO already exists NC54 command : CRIVMO command terminated❑


47 A2 94UC 3-101

3.2.14 MDNET SB

Purpose

Modifies the state and/or attributes of selected SB (statistics block) objects.

Syntax


CLASS = SB

[, OBJECT = ( name-8 [, name-8 ] ) ]



[, TYPE = SMPL ]

[, MAP = { CC | IS | LC | PC | SS | TC | NK } : dec-5 ]

[, INTERVAL = dec-9 ]



TYPE SMPL

MAP maps the connection object to the SB object:CC : channel connection (cc index of DNS or CNS7)IS : iso session connectionLC : logical connectionPC : physical connectionSS : sessionTC : transport connectionNK : internet network activity


3-102 47 A2 94UC


NEW_STATE ENBLLOCK

INTERVAL frequency of message emission in seconds up to amaximum of 999999 seconds.

EXAMPLE:

S: MDNET SB OBJECT=_SBCC0 NEW_STATE=ENBL; UPSB 14:18:12 --> NAME:_SBCC0 OLD_STATE:LOCK NEW_STATE:ENBL COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 3-103

3.2.15 MDNET SR

Purpose

Modifies the state and/or attributes of selected SR (session route) objects.

Syntax


CLASS = SR

[, OBJECT = ( name-8 [, name-8 ] ) ]



[, TYPE = { ISO | GC64 } ]


[, QUOTA = dec-3 ]




ISO :ISO networkGC64: PSI channel for DPS 7000 or link betweenDPS 7000 and FCP7




3-104 47 A2 94UC


NEW_STATE ENBLLOCK

QUOTA new quota for allocation of connections over sessionroutes.0 <= quota <= 32

EXAMPLE:

S: MDNET SR BC020001 NEW_STATE=LOCK; UPSR 09:56:24 --> NAME:BC020001 OLD_STATE:ENBL NEW_STATE:LOCK COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 3-105

3.2.16 MDNET TS

Purpose

Modifies the attributes of selected TS (transport station) objects.




[, OBJECT = ( name-8 [, name-8 ] ) ]


[, TYPE = ISO ]


[, VENUE = IM ]

[, TIMER_1 = dec-3 ] [, TIMER_2 = dec-3 ]

[, COUNT_N1 = dec-2 ] [, MAXTUSZ = dec-4 ]

[, MAXTC = dec-4 ] [, CREDIT = dec-2 ]



3-106 47 A2 94UC


TYPE ISO


NR : network routeSC : session controlSR : session controlTC : transport connection


MDNET CLASS=RTS ...

is equivalent to

MDNET CLASS=TS VENUE=IM ...


TIMER_1 acknowledgment timeout in seconds1 <= timer_1 <= 30 seconds

TIMER_2 inactivity timeout in seconds1 <= timer_2 <= 600 seconds

COUNT_N1 retransmission count1 <= count_n1 <= 10

MAXTUSZ transport unit size128 <= maxtusz <= 2048 (powers of 2)

MAXTC maximum number of transport connections1 <= maxtc <=2200

CREDIT input and output credit1 <= credit <= 15


47 A2 94UC 3-107

EXAMPLES:

S: MDNET RTS BL37 TIMER_1=20; UPTS 08:47:37 --> NAME:BL37 OLD_TIMER_1:10 NEW_TIMER_1:20 COMMAND COMPLETED. 1 OBJECT SELECTED

S: MDNET TS BL37 VENUE=IM CREDIT=6; UPTS 08:47:55 --> NAME:BL37 OLD_CREDIT:3 NEW_CREDIT:6 COMMAND COMPLETED. 1 OBJECT SELECTED❑

Syntax (for OCS)


CLASS = TS

[, OBJECT = ( name-8 )]

{ NEW_STATE = { ENBL | LOCK } }{ MAXTC = dec-5 }

[, STATE = ENBL | LOCK | USED | DOWN | DSBL ]

[, TYPE = { COTP | INET } ]


Parameters

See MDNET Command.


NEW_STATE ENBLLOCK

MAXTC number of possible connections opened. Must be< 5000.


3-108 47 A2 94UC

EXAMPLE:

MDNET TS BL38 MAXTC = 600

UPTS hh:mm:ss --->NAME = BL38 OLD_MAXTC = 2000 NEW_MAXTC = 600 COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 3-109

3.3 MDTL (MODIFY_TEST_IN_LINE)

Purpose

Modifies attributes of a given inline test.

Syntax

{ MDTL }{ }{ MODIFY_TEST_IN_LINE }

TEST = BNSE ID = dec-5 [, SYSTEM = { #WSYS | name-4 } ]

[, ELAPSE = dec-5 ] [, ITER = dec-5 ] [, DELAY = dec-5 ]

[, TRACE = { 0 | 1 } ] [, CONTINUE = { 0 | 1 } ]

[, ERROR_REPORT = { R | S | N | D } ] [, MORE = { 0 | 1 } ]


ID Specifies the identifier of the test as returned in theSTL TEST=BNSE command.

SYSTEM The name of the system on which the command is tobe executed.

NOTE:The following parameters are mutually exclusive.

ELAPSE Specifies the time in minutes beyond which the test isnot allowed to exceed.The maximum value is 65535 minutes.

ITER Specifies the maximum number of times the test is tobe repeated.The maximum value is 65535 times.

DELAY Specifies the time in seconds between consecutiveiterations of the test.The maximum value is 65535 seconds.


3-110 47 A2 94UC

TRACE Specifies if a trace is to be produced (TRACE orTRACE=1) or not (TRACE=0).

CONTINUE Specifies if, in the case of an error, the test is tocontinue (CONTINUE or CONTINUE = 1) or toterminate (CONTINUE = 0).

ERROR_REPORT Specifies the level of reporting.

MORE Requests further information on a lower-level screen(MORE or MORE=1).

EXAMPLES:

S: MDTL BNSE ID=2 ELAPSE=10; UPTL 09:33:20 --> ID:2 OLD_ELAPSE:00:00:00 NEW_ELAPSE:00:10:00 COMMAND COMPLETED. 1 OBJECT SELECTED

S: MDTL BNSE ID=2 ITER=20; UPTL 09:33:43 --> ID:2 OLD_ITER:1000 NEW_ITER:20 COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 3-111

3.4 MDTSVR (MODIFY_TELECOM_SERVER)

Purpose

Modifies the parameters of a communications server.

Syntax Format 1

{ MDTSVR }{ }{ MODIFY_TELECOM_SERVER }

{ TNS [, UNKNOWN_RPL = {0 | 1} ] } { }TYPE = { QMON } [, REPEAT = dec-3 ] { } { RAEH [, TRACE = dec-3 ] }

Syntax Format 2

{ MDTSVR }{ }{ MODIFY_TELECOM_SERVER }

{ FEPS [,READY = { 0 | 1 } ] }TYPE={ OCS } RSYS=name-4 { FECM [,RIM = { 0 | 1 } ] [,TRACE = dec-3 ] }

[ { STD_SCEN } ] [ { NO } ][, SCENARIO = { } ] [, AUTO = { } ][ { subfile-name } ] [ { name-8 } ]

[, VERSION = name-4 ] [, REPEAT = dec-3 ]


3-112 47 A2 94UC


TYPE Specifies the type of server to be started:

TNSFEPSFECMQMONRAEHOCS

RSYS mandatory for TYPE = FEPS, FECM or OCS.Specifies the name of the front-end processor, CNP 7or Datanet, to be administered by the server. In thecase of OCS Front End, specifies the name of the OCSserver.

SCENARIO meaningful only for TYPE=FEPS, TYPE=FECM, orTYPE=OCS.Specifies the name of the subfile in SYS.DSACONFlibrary containing the scenario to be executed by nextactivations of FECM or future restarts of OCS.

TYPE=FEPS means the subsequent automatic startupof FECM should the FEPS server fail.

VERSION meaningful only when TYPE=FEPS, or TYPE=OCS.DNS/OCS Front End version to be used for nextautomatic startup of FECM or next restarts of OCS.

AUTO Specifies a label name in the scenario designated bythe SCENARIO parameter, to which control will bepassed in case of a subsequent automatic startup ofFECM or OCS.If not specified, the default label is provided.AUTO=NO means that the automatic mode isdisabled.

TRACE meaningful only when TYPE=RAEH orTYPE=FECM.

Trace level of future activations of the serverconcerned for maintenance purposes.

RIM Specifies if the DNS RIM (request initialization mode)signal coming from the Datanet is to be processedwhen FEPS is inactive.If RIM=1, the RIM is not processed and the FECMoccurrence is not started.


47 A2 94UC 3-113

READY Specifies if the DNS READY signal coming from theDatanet is to be processed when FEPS is inactive.If READY=1, the READY signal is not processed andthe FEPS occurrence on the remote system is notactivated.

REPEAT Specifies the maximum number of attempts at startingthe server.

UNKNOWN_RPL UNKNOWN_RPL = 1 means that the addresses ofremote systems not configured (in NETGEN) whichsend frames via the ISL are displayed on the operatorconsole (TP05 message). UNKNOWN_RPL = 0means that such addresses are not displayed.UNKNOWN_RPL is meaningful only if TYPE = TNS.

EXAMPLES:

S: MDTSVR FECM BL05 RIM=0; CA28 MDTSVR BL05 COMPLETED.

S: MDTSVR FECM BL05 SCENARIO=MY_SCEN; CA28 MDTSVR BL05 COMPLETED.❑


3-114 47 A2 94UC

3.5 PRTTR (PRINT_TELECOM_TRACE)

Purpose

Edits and prints a trace file whose name appears at the startup of the trace and at itstermination.

Syntax

{ PRTTR }{ }{ PRTTRF }{ }{ PRINT_TELECOM_TRACE }

FILE = name-44

[ { * } ][, PROCESS = { } ][ { ( x [ x [ x ] ... ] ) } ]

where, x = { 0 | 1 | 2 | 3 | 4 } for FEPS and TNSand x = { 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 } for OCS

[ { DL } { 1 } ] [ { PRT132 } ][, { } = { } ] [, PRT_W = { } ][ { DELETE } { 0 } ] [ { PRT120 } ]

[ { 0 } ][, TIME = { } ] where 1 = GMT time and 0 = local time (default)[ { 1 } ]


47 A2 94UC 3-115


FILE Up to 44 a/n characters identifying the trace file to beedited. The name of the trace file of the format:file-name[:media[:device]]

The file can be resident or non-resident, cataloged ornon-cataloged.

Allocation of the Trace File

− File Resident but UncatalogedThe name of the trace file according to the server, is:

TRC_FEPS_server-name for FEPS,TRC_TNS_TNS for TNS,TRC_OCS_server-name for OCS.

− Cataloged FileSuch a file can be cataloged in either SYS.CATALOGor a private catalog. FILE must be specified and thename of the file must be prefixed by the name of thecatalog as follows:

SYS.file-name for SYS.CATALOG,MYCAT.file-name for a private catalog.

− File Non-resident and UncatalogedSuch a file must be defined in the full format:file-name:media:device, for example:

FILE=TRC1:SVLT8B:MS/D500.

PROCESS List of process numbers to be printed. The defaultvalue * means that all processes are to be printed.For OCS, the relevant process numbers are 0 to 8(9 values).

DELETE Specifies if the file is to be deleted after printing. Thedefault is to delete to avoid proliferating trace files.

PRT_W Allows when it is possible using the maximum printerwidth. Default is PRT132.

TIME Specifies the time with respect to either local time (0)or GMT time (1). 0 is the default.


3-116 47 A2 94UC

EXAMPLES:

PRTTR RST.TRC1$CAT;Prints all the processes of the file RST.TRC1 catalogedin RST.CATALOG and deallocates the file.

PRTTR TRC1:SVLT8B:MS/D500 PROCESS=0 PRT_W=PRT120;Prints only process 0 of the file TRC1 on the mediaspecified on a printer of 120 characters and deallocatesthe file.

PRTTR TRC_FEPS_UNCP TIME=0 PROCESS=*;Prints all processes of the file for the server UNCPbeing an FEPS occurrence showing GMT time anddeallocates the file.

PRTTR TRC_TNS_TNS PROCESS=3 DL=0;Prints only process 3 of the file for the TNS server butdoes not deallocate the file.

PRTTRF TRC_OCS_NCC1;Prints the trace file for the OCS server named NCC1.

❑


47 A2 94UC 3-117

3.6 SCNVTR (SCAN_VCAM_TRACE)

Purpose

Scans the logfile created through the SVTR command.

The SCNVTR command is a specialized command used for maintenance purposes.It is not normally intended for the operator.

For the syntax and parameter description of the SCNVTR command, see paragraph10.2.1.2 SCNVTR (SCAN_VCAM_TRACE).


3-118 47 A2 94UC

3.7 SNDQ (SEND_QUEUE)

Purpose

Sends a message to a program queue.

Syntax

{ SNDQ }{ } QUEUE = char-8{ SEND_QUEUE }

{ MSSG }{ } = char-128{ MESSAGE }


QUEUE The name of the program-queue used by MCSapplications to receive messages.

MESSAGE A string of up to 128 alphanumeric characters. Themessage is queued after other system or data messagesalready present in the queue.

Response

NAME : queue-nameREASON : reason code if the command is not executed

EXAMPLE:

S: SEND_QUEUE QUEUE2 MESSAGE='FILE TRANSFER ON JOB OUTPUT DONE' TXQD 14:59:50 --> NAME:QUEUE2 COMMAND COMPLETED. 1 OBJECT SELECTED CC03 SNDQ COMPLETED❑


47 A2 94UC 3-119

Reason Codes

AA/00 command done AA/01 selection parameter not supported AA/02 modification parameter not supported

AA/03 selection parameter mandatory AA/04 TYPE not supported AA/05 mandatory modification parameter missing

AA/06 already exists AA/07 retry later AA/08 no network generation available

AA/09 queue unknown AA/0A selection parameter not allowed AA/0B no modification allowed, queue is disabled

AA/0C no modification nor selection allowed AA/0D no modification allowed, queue is in use AA/0E no modification allowed on PROGRAM queue

AA/0F no modification allowed on DSA/USERID queue AA/10 illegal parameter value AA/11 no queue declared in network generation

AA/12 command management error AA/13 MCS internal error AA/14 QMON not started


3-120 47 A2 94UC

3.8 SNR (START_NETWORK_REPORTING)

Purpose

Reports network messages in realtime for any operator cataloged with MAINaccess rights. Profiles functioning as filters, select the messages to be reported.

Syntax

{ SNR }{ }{ START_NETWORK_REPORTING }

[,{ FROM_SYSTEM | FROM } = ( name_4 , name_4 [ , name_4 ... ] ) ]

Main Profiles [ { SURVEY = { 0 | 1 } } ] [ { } ] [ { { EVENTS | EV } = { 0 | 1 } } ] [ { } ] [ { { ERROR_EVENTS | ERREV | EREV } = { 0 | 1 } } ] [ { } ] [ { { STATISTIC_EVENTS | STATEV } = { 0 | 1 } } ] [ { } ] [ { { MODIF_COMMANDS | MDCMD } = { 0 | 1 } } ] [ { } ]

Sub Profiles [ { ALL = { 0 | 1 } } ] [ { } ] [ { { ERRORS | ERR | ER } = { 0 | 1 } } ] [ { } ] [ { { CHANGES | CH } = { 0 | 1 } } ] [ { } ] [ { { STATISTICS | STAT } = { 0 | 1 } } ] [ { } ] [ { { ADMINISTRATION | ADM } = { 0 | 1 } } ] [ { } ] [ { { APPLICATIONS | APPLI } = { 0 | 1 } } ] [ { } ] [ { TESTS = { 0 | 1 } } ] [ { } ] [ { { DSA_OSI_DOMAIN | DSA_OSI } = { 0 | 1 } } ] [ { } ] [ { { SESSION | SESS } = { 0 | 1 } } ] [ { } ] [ { { TRANSPORT | TR } = { 0 | 1 } } ] [ { } ] [ { { LOW_LAYERS | LOW } = { 0 | 1 } } ] [ { } ]


47 A2 94UC 3-121


FROM_SYSTEM limits the selection of records issued from the systemsspecified. When the record is a response to acommand, the system responder only is concerned.

Up to 5 systems may be specified.

Parameter Description of Main Profiles

SURVEY Selects any important or error unsolicited message orany response to an UPDATE or MAP commandreceived to be logged by DSAC from the local orremote systems. SURVEY behaves as thoughERRORS and CHANGES are active at the same time.

SURVEY is the default profile if no main or subprofileis specified.

When other subprofiles are active with SURVEY, theirselected records are also reported.

EVENTS Selects any unsolicited message received to be loggedby DSAC from the local or remote systems.

When other subprofiles are active with EVENTS, therecords selected by EVENTS are further subjected forselection by these subprofiles.

ERROR_EVENTS Selects any important or error unsolicited messagereceived to be logged by DSAC from the local orremote systems.

When other subprofiles are active withERROR_EVENTS, the records selected byERROR_EVENTS are further subjected for selectionby these subprofiles.

STATISTIC_EVENT Selects any History Report unsolicited messagereceived by DSAC to be logged by DSAC from thelocal or remote systems.

When other subprofiles are active withSTATISTIC_EVENTS, the records selected bySTATISTIC_EVENTS are further subjected forselection by these subprofiles.


3-122 47 A2 94UC

MODIF_COMMANDS Selects any Modification command and its responsereceived to be logged by DSAC from the local orremote systems. Modification commands may beUPDATE, MAP, CREATE or DELETE or commandsspecific to SY and EX objects.

When other subprofiles are active withMODIF_COMMANDS, the records selected byMODIF_COMMANDS are further subjected forselection by these subprofiles.

Parameter Description of Subprofiles

ALL Selects any unsolicited message or response to acommand received by DSAC from the local or remotesystems.

ALL is the default subprofile when SURVEY=0 andno other subprofile has been specified.

When ALL is active, other subprofiles are not effectivesince the record is always selected.

ERRORS Selects any important or error unsolicited messagereceived by DSAC from the local or remote systems.

ERRORS may not be active withMODIF_COMMANDS or SURVEY main profiles.

CHANGES Selects any response to an UPDATE or MAPcommand received to be logged by DSAC from thelocal or remote systems. CHANGES may not beactive with EVENTS, ERROR_EVENTS,STATISTIC_EVENTS or SURVEY main profiles.

STATISTICS Selects any History Report unsolicited message or anyresponse to a Get History command received to belogged by DSAC from the local or remote systems.


47 A2 94UC 3-123

ADMINISTRATION Selects any unsolicited message or response to acommand received to be logged by DSAC from thelocal or remote systems and related to theadministration of DSAC and the local system.

Objects related to DSAC administration may beadministrative connections, administrative objects,logfiles, filters, operators and statistics blocks.

Objects related to the administration of the localsystem may be system, executive subsystem andvehicle objects.

APPLICATIONS Selects any unsolicited message received to be loggedby DSAC from the local or remote systems and relatedto applications such as file transfers, workstations andmessage queues.

TESTS Selects any unsolicited message or response to acommand received to be logged by DSAC from thelocal or remote systems and related to tests.

DSA_OSI_DOMAIN Selects any unsolicited message or response to acommand received to be logged by DSAC from thelocal or remote systems and related to communicationsobjects in layers 5 to 1 of the DSA and OSI referencemodels.

DSA_OSI_DOMAIN includes the SESSION,TRANSPORT and LOW_LAYERS subprofiles.

SESSION Selects any unsolicited message or response to acommand received to be logged by DSAC from thelocal or remote systems and related either toaddressing objects of the session layer or to connectionobjects.

Addressing objects of the session layer may bemailbox, session control, session route or address list.Connection objects may be session or logicalconnections.


3-124 47 A2 94UC

TRANSPORT Selects any unsolicited message or response to acommand received to be logged by DSAC from thelocal or remote systems and related either to transportaddressing objects or to connection objects.

Transport addressing objects may be transport stationsor channels.

Connection objects may be transport connections,network connections or channel connections.

LOW_LAYERS Selects any unsolicited message or response to acommand received to be logged by DSAC from thelocal or remote systems and related to addressing andconnection objects in layers 3 to 1 of the DSAreference model.

EXAMPLE:

S: SNR; CRFL 11:08:02 --> COMMAND COMPLETED. 1 OBJECT SELECTED CRFL 11:08:03 --> COMMAND COMPLETED. 1 OBJECT SELECTED UPOP 11:08:04 --> NAME:SNR_8264 OLD_STATE:LOCK NEW_STATE:ENBL COMMAND COMPLETED. 1 OBJECT SELECTED ****************************************************** * SNR 1:08:04 * * NETWORK REPORTING STARTED FOR OPERATOR * * OP NAME IS SNR_8264 (SNR_RON) * ******************************************************❑


47 A2 94UC 3-125

3.9 STL (START_TEST_IN_LINE)

Purpose

Starts the BNSE session exerciser or the LNA link-level echo frame over anEthernet Network.

Syntax For BNSE

{ STL } [ { ECHO } ]{ } TEST = BNSE [, SUBTEST = { } ]{ START_TEST_IN_LINE } [ { DROP } ]

{ ACCEPTOR } { }SIDE = { [ { $NSE } ] } { INITIATOR, RSYS = name-4 [, RMBX = { } ] } { [ { char-8 } ] }

[ { $NSE } ] [ { 500 } ][, LMBX = { } ] [, EXCHANGES = { } ][ { char-8 } ] [ { dec-5 } ]

[, SYSTEM = { #WSYS | name-4 } ] [, MORE = { 0 | 1 } ]

[ { 0 } ] [ { 1 } ] [ { 0 } ][,ELAPSE = { } ] [,ITER = { } ] [,DELAY = { } ][ { dec-5 } ] [ { dec-5 } ] [ { dec-5 } ]

[, TRACE = { 0 | 1 } ] [, CONTINUE = { 0 | 1 } ]

[, ERROR_REPORT = { R | S | N | D | } ]


3-126 47 A2 94UC

Syntax For LNA

{ STL }{ } TEST = LNA OBJECT = char-8{ START_TEST_IN_LINE }

[ { 1 } ][, SYSTEM = name-4 ] [, MORE = { 0 | 1 } ] [,ITER = { } ] [ { dec-5 } ]

[ { 126 } ][, DATA_SIZE = { } ] [, DATA_VALUE = char-128 ][ { dec-3 } ]


SUBTEST Specifies how the message is to be processed.ECHO: default, checks that the message sent is echoedDROP: the message sent requires no response

SYSTEM The name of the system on which the test is to beexecuted.

ELAPSE Specific to BNSE, defining the time in minutes beyondwhich the test is not allowed to exceed.

If ELAPSE is not specified, the duration of the test isnot controlled.

The value must not exceed 65535 minutes.

ITER Specifies the maximum number of times the test is tobe repeated.

The value must not exceed 65535 times.

DELAY Specific to BNSE, defining the time in secondsbetween consecutive iterations of the test.

The value must not exceed 65535 seconds.

TRACE Specific to BNSE, defining if a trace is to be produced(TRACE or TRACE=1) or not (TRACE=0 default).

CONTINUE Specific to BNSE, defining if, in the case of error, thetest is to continue (CONTINUE or CONTINUE=1) orto terminate (CONTINUE=0 default).


47 A2 94UC 3-127

DATA_SIZE Specific to LNA, defining the data part of the echoframe size ranging from 1 through 126 (default) bytes.

DATA_VALUE Specific to LNA, defining the pattern of the frame.

ERROR_REPORT Specific to BNSE, defining the level of reporting.

EXCHANGES Specific to BNSE, defining the number of messagessent by the initiator side or received by the acceptorside during one iteration.The default is 500 messages.

LMBX Specific to BNSE, defining the local mailbox.The default name is $NSE.

MORE Requests further information on a lower-level screen(MORE or MORE=1).

OBJECT Specific to LNA, defining the name of the remotephysical link to which the ECHO frame is sent.

RMBX Specific to BNSE, defining the remote mailbox and ismeaningful only if SIDE=INITIATOR.The default name is $NSE.

RSYS Specific to BNSE, defining the name of the remotesystem running the corresponding acceptor test.Meaningful only if SIDE=INITIATOR.The default name is $NSE.

SIDE Specific to BNSE, defining how the test is to execute.

EXAMPLES:

S: STL BNSE SIDE=ACCEPTOR; EXTL 09:31:07 --> ID:1 NAME:BNSE SUB_NAME:ECHO OBJECT:BL05$NSE COMMAND COMPLETED. 1 OBJECT SELECTED

S: STL BNSE SIDE=INITIATOR RSYS=B ITER=1000 DELAY=1; EXTL 09:31:45 --> ID:2 NAME:BNSE SUB_NAME:ECHO OBJECT:BL05$NSE COMMAND COMPLETED. 1 OBJECT SELECTED❑


3-128 47 A2 94UC

3.10 STSVR (START_TELECOM_SERVER)

Purpose

Starts a communications server. See also "LNA Trace".

Contrary to Datanet or CNP7 front-end processors, the software of the FCP7controller is loaded each time that its related OCS server is started.

Syntax Format 1 (for TNS, RAEH, and QMON)

{ STSVR }{ }{ START_TELECOM_SERVER }

{ TNS [, LOG = { 0 | 1 } ] [, REPEAT = dec-1 ] }TYPE = { QMON } { RAEH [, TRACE = dec-3 ] [, REPEAT = dec-1 ] }

Syntax Format 2 (for FEPS and FECM)

{ STSVR }{ }{ START_TELECOM_SERVER }

{FEPS [, LOG = { 0 | 1 } ] }TYPE={ } RSYS=name-4 {FECM [,ACTION = name-8 ] [,TRACE = dec-3 ]}

[ { STD_SCEN } ] [ { NO } ][, SCENARIO = { } ] [, AUTO = { } ][ { subfile-name } ] [ { name-8 } ]

[, VERSION = name-4 ] [, REPEAT = dec-1 ]


47 A2 94UC 3-129

Syntax Format 3 (for OCS)

STSVR TYPE = OCS

RSYS = <name_8>

[LOG = {0 | 1}]

[SCENARIO = {STD_SCEN | <subfile_name>}]

[ACTION = <name_8>]

[VERSION = <name_4>]

[AUTO = NO | name-8]

[REPEAT = dec-1]


TYPE Specifies the type of server to be started:

TNSFEPSFECMQMONRAEHOCS

RSYS mandatory for TYPE=FEPS, TYPE=FECM, orTYPE=OCS.Specifies the name of the front-end processor, CNP 7or Datanet, to be administered by the server, or thename of the OCS server that will administer the OCScontroller.

SCENARIO meaningful only for TYPE=FEPS, FECM, or OCS.It specifies the name of the subfile (in the librarySYS.DSACONF) which contains the scenario to beexecuted by FECM or OCS. Default name isSTD_SCEN.TYPE = FEPS means the subsequent automatic startupof FECM should the FEPS server fail.


3-130 47 A2 94UC

ACTION meaningful only for TYPE=FECM or OCS.Specifies a label name in the scenario designated bythe SCENARIO parameter, to which control is passedon FECM or OCS startup. If not specified, the defaultlabel in the scenario is taken.

AUTO meaningful only for TYPE=FECM (for Datanet only),TYPE=FEPS, or TYPE=OCS.Specifies a label name in the scenario designated bythe SCENARIO parameter, to which control will bepassed in case of a subsequent automatic startup ofFECM or OCS.If not specified, the default label is provided.AUTO=NO means that the automatic sequence ofFECM-FEPS-FECM... (in whichever order the serverconcerned fails to start) is disabled. In the case ofOCS, the automatic restart of OCS is also disabled.

TRACE meaningful only when TYPE = RAEH or TYPE= FECM.Trace level of the server concerned for maintenancepurposes.

LOG meaningful only when TYPE = TNS, FEPS, or OCS.Specifies that the memory trace is to be logged on afile.

VERSION meaningful only when TYPE = FEPS, FECM, or OCS.For FEPS/FECM, it specifies the DNS/CNS 7 versionto be used for present and future activations of FECM.For OCS, it specifies the OCS Front End softwareversion to be used.

REPEAT specifies the maximum number of times that the serveris to be restarted automatically (after an abort), onlywhen AUTO=NO is not specified. REPEAT=0 meansthat no restart is processed.


47 A2 94UC 3-131

EXAMPLES:

S: STSVR FEPS BL05; CA20 BL05 LAUNCHED BY OPERATOR COMMAND CA21 BL05 STARTED

S: STSVR RAEH; CA20 RAEH LAUNCHED BY OPERATOR COMMAND CA21 RAEH STARTED NA10 JOURNAL STARTED ON SYS.DSALOG1

S: STSVR OCS NCC1 VERSION=NA07 AUTO=NO; CA20 NCC1 LAUNCHED BY OPERATOR COMMAND 17.04 X1432 STARTED OCS OPERATOR S JB08 X1432.1 STEP H_NCCD7 XPR=0 PGID=124 NCC1 LOAD STARTED FROM VERSION:NA07 NCC1 LOAD COMPLETED NC01 FROM SERVER NCC1 : CONFIGURATION WARNINGS OR ERRORS: SEE REPORT FILE NC01 FROM SERVER NCC1 : ISO/DIWS + IPS PROTOCOLS AVAILABLE CA21 NCC1 STARTED NC01 FROM SERVER NCC1 : CONNECTED TO NETWORK❑


3-132 47 A2 94UC

3.11 STTR (START_TELECOM_TRACE)

Purpose

Starts the trace on the objects selected for the server. The value for the TRACEparameter, if not specified, is taken from the last TTTR command entered for theserver concerned.

See also the paragraph 10.2.7 "LNA Trace".

Syntax

{ STTR }{ }{ START_TELECOM_TRACE }

{ [ { value set at TTTR } ] } { [ { } ] } { [ { ALL } ] }{ SVR } { { TNS } [ { TR } { } ] }{ }={ { ocs-name } [ { }={ DATA } ] }{ SERVER } { { feps-name } [ { TRACE } { } ] } { [ { DATASEMM } ] } { [ { } ] } { [ { RESET } ] } { } { UFT }

[ {MB1 } ][,{MB }={char-8} ][ {MBX1 } ]

[ {MB2 } ][,{MB }={char-8} ][ {MBX2 } ]

[ {MB3 } ][,{MB }={char-8} ][ {MBX3 } ]


47 A2 94UC 3-133


SERVER keywords TNS and UFT or up to 8 alphanumericcharacters for ocs-name (the name of the OCS server)or feps-name.

TRACE specifies the set of objects in the server to be traced asfollows:

ALL: select all objectsDATA: select only the data exchangedDATASEMM: select only data and semaphoremessagesRESET: set trace mode at initial value

MB1, MB2, MB3 For selective telecommunication trace:

Names(s) of the local or remote mailbox(es) for whicha telecommunication trace is requested.Only the first connection for each mailbox is selected.Not significant for an UFT user.When these parameters are used, TRACE=DATA orTRACE=DATASEMM is mandatory.When MB2 is used, MB1 is mandatory.When MB3 is used, MB2 is mandatory.

EXAMPLES:

STTR SVR=TNS TR=ALLThe information on all objects for TNS are traced inTRC_TNS_TNS.

STTR SVR=UNCP TR=DATAOnly data in the form of DSA letters and ISO SPDUsexchanged by the FEPS or OCS occurrence namedUNCP are traced in TRC_FEPS_UNCP orTRC_OCS_UNCP. Data exchanged by the applicationusing the FEPS occurrence are included.

STTR SVR=UFT The trace on the phases of the file transfer are sentdirectly in the JOR or SYSOUT report of the transfer.

STTR SVR=UNCP TR=RESETThe trace filters for the FEPS or OCS occurrencenamed UNCP are set to their initial state to allow forthe minimum of traffic. Only short events which arenot time-consuming are allowed.

❑


3-134 47 A2 94UC

3.12 SVTR (START_VCAM_TRACE)

Purpose

Starts the VCAM trace collector.

The SVTR command is not intended for normal operations.

For the syntax and parameter description of the SVTR command, see 10.2.1.1SVTR (START_VCAM_TRACE).

Other commands relating to the VCAM trace collector are the DVTR and TVTRcommands.


47 A2 94UC 3-135

3.13 TNR (TERMINATE_NETWORK_REPORTING)

Purpose

Deactivates all profiles and stops Network Reporting to the operator. TNR issymmetric to SNR.

Syntax

{ TNR }{ }{ TERMINATE_NETWORK_REPORTING


The TNR command does not take any parameters.

EXAMPLE:

S: TNR; DLFL 11:08:41 --> NAME:PF1_FL1 --> NAME:PF1_FL2 COMMAND COMPLETED. 2 OBJECTS SELECTED ***************************************************** * TNR 11:08:41 * * NETWORK REPORTING TERMINATED FOR OPERATOR * *****************************************************❑


3-136 47 A2 94UC

3.14 TTL (TERMINATE_TEST_IN_LINE)

Purpose

Terminates the inline test.

Syntax

{ TTL }{ }{ TERMINATE_TEST_IN_LINE }

{ BNSE ID = dec-5 }TEST = { } { LNA OBJECT = char-8 }

[, SYSTEM = { #WSYS | name-4 } ] [, MORE = { 0 | 1 } ]


ID Specific to BNSE, defining the identifier of the testreturned by the STL TEST=BNSE command.

OBJECT Specific to LNA, defining the name of the remotephysical link.

SYSTEM The name of the system on which the test is to beterminated.

MORE Specifies a lower screen level.

EXAMPLE:

S: TTL BNSE ID=2; CLTL 09:34:10 --> ID:2 NAME:BNSE SUB_NAME:ECHO OBJECT:BL05$NSE COMMAND COMPLETED. 1 OBJECT SELECTED❑


47 A2 94UC 3-137

3.15 TTSVR (TERMINATE_TELECOM_SERVER)

Purpose

Terminates a communications server. See also 10.2.7 "LNA Trace".

Syntax

{ TTSVR }{ }{ TERMINATE_TELECOM_SERVER }

{ { TNS } } { { } } { { QMON } } { { } }TYPE = { { RAEH } } { } { } { { FEPS } { RSYS = name-4 } } { { OCS } { } } { { FECM } { NAME = name-8 } }

[ { WEAK } ][ { } ][, CODE = { STRONG } ][ { } ][ { ABORT } ][ { } ][ { ABTPG } ]


TYPE The type of communications server to be terminated.If TYPE=FEPS or TYPE=FECM, either RSYS orNAME must be specified. If TYPE=OCS, RSYS mustbe specified.

RSYS mutually exclusive to NAME.Identifies the FEPS or FECM server occurrence to beterminated by the name of the system it administers.For OCS Front End, you give the name of the OCSserver.


3-138 47 A2 94UC

NAME mutually exclusive to RSYS and applicable only whenTYPE=FEPS or TYPE=FECM. Identifies the FEPS orFECM to be terminated as follows:

− for FEPS, the name of the server is that given atNETGEN.

− for FECM, the name of the server is dynamicallybuilt when the server is started and is given in theCA20 or CA21 messages, or by the DTSVRcommand, e.g. ADM_rsys-name or ASF_rsys-name.

CODE Specifies the kind of termination that is requested.

− WEAK: option processed by the server. Terminatethe server at the end of normal processing of currentsessions. No more new sessions can be started.

− STRONG: option processed by the server. Breakimmediately current sessions then terminate theserver.

− ABORT: option processed by system services.Abort only the server named.

− ABTPG: option processed by job management.Abort the entire process group of the OCS driver.Consequently, all started OCS servers are aborted.ABTPG is only applicable if TYPE=OCS. TheABTPG option should only be used if a previousABORT option was not effective. After usingABTPG, LT and UC resource availablity must bechecked and, if necessary, restored (for exampleby RDV command).

The ABORT or ABTPG options can cause one ormore user process dumps to be stored in theSYS.SPDUMP file.


47 A2 94UC 3-139

EXAMPLES:

S: TTSVR FEPS BL05; CA21 BL05 COMPLETED

S: TTSVR RAEH; CA21 RAEH COMPLETED

S: TTSVR OCS NCC2; NC01 FROM SERVER NCC2 : FRONT END STOPPING NC01 FROM SERVER NCC2 : IPS TRAFFIC STOPPED CA21 NCC2 COMPLETED 10.53 X142.1 COMPLETED OCS OPERATOR

S: TTSVR OCS NCC1 CODE=ABTPG; CA21 NCC1 COMPLETED 17.02 X1431.1 ABORTED OCS OPERATOR S SEV3❑


3-140 47 A2 94UC

3.16 TTTR (TERMINATE_TELECOM_TRACE)

Purpose

Stops the trace on the objects selected for the server. The value for the TRACEparameter, if not specified, is taken from the last STTR command entered for theserver concerned.

See also paragraph 10.2.7 "LNA Trace".

Syntax

{ TTTR }{ }{ TERMINATE_TELECOM_TRACE }

{ [ { value set at STTR } ] } { [ { } ] } { [ { ALL } ] }{ SVR } { { TNS } [ { TR } { } ] }{ }={ { ocs-name } [ { }={ DATA } ] }{ SERVER } { { feps-name } [ { TRACE } { } ] } { [ { DATASEMM } ] } { [ { } ] } { [ { RESET } ] } { } { UFT }


SERVER keywords TNS and UFT or up to 8 alphanumericcharacters for ocs-name (the name of the OCS server)or feps-name.

TRACE specifies the set of objects in the server to be traced asfollows:

ALL: select all objectsDATA: select only the data exchangedDATASEMM: select only data and semaphoremessagesRESET: set trace mode at initial value


47 A2 94UC 3-141

EXAMPLES:

TTTR SVR=TNS TR=ALL TThe file TRC_TNS_TNS is closed. The TRACE levelis set at ALL for a subsequent STTR TNS command.

TTTR SVR=UNCP TR=DATAThe file TRC_FEPS_UNCP is closed. The TRACElevel is set to DATA for a subsequent STTR UNCPcommand.

TTTR SVR=UFT The trace on the phases of the file transfer no longerappear in the JOR or SYSOUT report of the transfer.

TTTR SVR=UNCP TR=RESETThe file TRC_FEPS_UNCP is closed. The TRACElevel for the filters is RESET to their initial state toallow for the minimum of traffic. Only short eventswhich are not time-consuming are allowed.

❑


3-142 47 A2 94UC

3.17 TVTR (TERMINATE_VCAM_TRACE)

Purpose

Terminates the VCAM trace collector previously started by the SVTR command.

Syntax

{ TVTR }{ }{ TERMINATE_VCAM_TRACE }


The TVTR command does not take any parameters.

47 A2 94UC 4-1

4. FECM Functions

This Section describes the administrative functions of FECM, these being:

For DPS 7000:

• providing the support of FEP software generation (DNS for the Datanet andCNS 7 for the CNP 7):

• loading the FEP with its appropriate software

• and dumping the software image of the FEP concerned.

It applies to the following hardware and connections to the DPS 7000:

• the Datanet connected over the PSI

• CNP 7 (integrated FEP) over the ISL

• and the LCT or the ISL controller of the DPS 7000.

This Section also describes the support for the ASF function standard for DSA.

For DPS 7000/XTA:

• providing the support of MainWay 2600LE software generation

• loading the MainWay 2600LE with its appropriate software

• and dumping the software image of the MainWay 2600LE concerned.

The OCS Front Ends integrated controller have their own communicationsdriver/servers named OCS (Open Communications Subsystem). OCS Front Endsand OCS are discussed in Section 5.


4-2 47 A2 94UC

4.1 Overview

4.1.1 Introduction

For DPS 7000:

The FEPs supported by GCOS 7 are:

• stand-alone Datanets connected over PSIs

• and/or several integrated CNP 7s connected to the SPA over the ISL.

Throughout the text, the term Datanet includes all models of DN71xx. The termFEP applies to both the Datanet and the CNP 7. The terms Datanet and CNP 7 areonly mentioned if the operation is specific to the FEP concerned.

For DPS 7000/XTA:

The MainWay 2600LE is supported by GCOS 7.The MainWay 2600LE is administrated by DPS 7000/XTA.

FEPs or MainWay 2600LE are managed through GCL commands entered at themain operator terminal.

One service job: FECM (Front End Control and Management) is started for eachfunction required, system generation, load or dump. This service job can be startedautomatically according to the parameters specified by the user in the STSVR orMDNET commands.

This job is responsible for administration dialog between GCOS 7 and the FEP, aswell as for providing file access facilities for DSAC logging. It runs in thescheduling class S with a high dispatching priority in order to meet time constraintsimposed on either the PSI or ISL dialog.

There are as many occurrences of FECM jobs as there are concurrentadministrations of different front-end systems or LNA controllers.

FECM Functions

47 A2 94UC 4-3

4.1.2 Datanet Management

The Datanet is managed by two communications servers, FECM and FEPS.

FECM is in charge of performing administrative functions while FEPS performstransport functions.

There are as many occurrences of FECM or FEPS as there are active Datanets.

Datanet

FECMor

FEPS

DPS 7000HOST

PSI

A Datanet at power-up or after a system incident (SYSER DNS) must be loaded tobe operational. The memory image to load the Datanet must contain both DNSsoftware as well as the Datanet network configuration. The Datanet has the abilityto request loading from its neighbors through the communications support or toautoload from its own diskettes.

The request from the Datanet for loading from its neighbor is performed as followsdepending on the neighbor:

• over a PSI if the neighbor is a DPS 7000, in which case

− FEPS, if active, terminates

− FECM starts automatically if the PSI is ready and uses the default scenario.

• over an HDLC line if the neighbor is a Datanet, in which case, teleloadingoccurs where

− the neighbor searches the Datanet loading files in the DPS 7000

− FECM then starts at the same time as the file server to load the Datanet.


4-4 47 A2 94UC

• over an ISL, where the neighbor can be either a DPS 7000 or a Datanet, in whichcase, the GCOS 7 operator loads the Datanet by starting up FECM through theSTSVR TYPE=FECM command.

In the case of a bi-PSI Datanet configured as such in the DPS 7000 networkgeneration, the request for loading sent over both its PSIs will result in the startupof FECM even if one PSI is HELD.

4.1.3 CNP 7 and LCT Management

The CNP 7 and the LCT are managed by two communications servers, FECM andTNS.

FECM is in charge of performing administrative functions while TNS performsdata transfer over the ISL or through the LCT.

Although there are as many occurrences of FECM as there are CNP 7s or ISL localcontrollers (hardware entity: Local Network Adaptor) for which administrativefunctions are executing, there can be only one occurrence of TNS whatever thenumber of active CNP 7s.

CNP7

LCT

LNASPA

PSI

DPS 7000HOST

FECM

VCAM

TNS

ISL

TNS must first have been started before it is able to process any administrativefunction requested either by the equipment concerned or by operator command.

FECM Functions

47 A2 94UC 4-5

The loading of a CNP 7 may be performed automatically upon its request (RIM)broadcast over the ISL.

The loading of an LCT is automatically performed when necessary, each time itsstate passes to ENBL.

Any failure or initialization request from CNP 7 or its SPA is handled withoutoperator intervention.

One FECM job is started to process the necessary administrative functions(dumping and/or loading the CNP 7 or LNA).

4.1.4 MainWay 2600LE Management

For DPS 7000/XTA:

The MainWay 2600LE is managed by three communications servers, FECM, TNSand OCS.

FECM is in charge of performing administrative functions while TNS and OCSperforms data transfer over the ISL or through the LCT.

TNS server is used during sysgen, load and dump of MainWay 2600LE(ADMfunction of FECM).

OCS server is only used during second step of MainWay 2600LE(ASF function ofFECM).

MainWayLE

DPS7000/XTA

ISL

(ADM) FECM (ASF)

LCT

TNS OCS

LCT


4-6 47 A2 94UC

TNS must first have been started before it is able to process any administrativefunction requested either by the MainWay 2600LE or by operator command.

The loading of a MainWay 2600LE may be performed automatically upon itsrequest (RIM) broadcast over the ISL.

Any failure or initialization request from MainWay 2600LE is handled withoutoperator intervention. One FECM job is started to process the necessaryadministrative functions (dumping and/or loading the MainWay 2600LE).

4.1.5 Multiversion Management

In order to facilitate the evolution of technical releases of the FEPs (Datanet andCNP 7) and to allow them to be administered together, a multiversion managementfunctionality is available on GCOS 7.

This functionality allows having different software releases which may be used ondifferent FEPs, or different software releases which may be used alternatively onthe same FEP.

It may be used, for example, to run the current FEP release during production, andwhen the FEP is no longer active, to test a new software release on the same FEP.

On a given DPS 7000, a default version is provided for all FEPs. This defaultversion may be changed either for all the FEPs, or for only one FEP.

FECM Functions

47 A2 94UC 4-7

4.1.6 Files and Scenarios

The files that are required for executing administrative functions on the FEPs andthe LNA controllers are cataloged system files. These files are created by theTAILOR function at System Installation. See System Installation, Configurationand Updating Guide.

These files fall into two categories:

• those that are system-configured and therefore cannot be modified

• and those whose system-supplied defaults can be modified by the user.

All the FEP files or MainWay 2600LE files are described in paragraph 4.3.

The administrative functions (sysgen, load, dump) and the files which are used, aredefined in a scenario.

A standard scenario where administrative functions execute with defaultparameters, is supplied with each front-end processor when the system is firstinstalled. This FECM scenario corresponds to the standard network generation(NETGEN) delivered with GCOS 7.

The scenario may be either modified to be readapted to the network configurationor used to create a new user-defined scenario. For further details of the standardscenarios for the CNP 7 and Datanet, or MainWay 2600LE see Appendix C.

The use of the scenario and the detailed syntax are described in paragraph 4.4.


4-8 47 A2 94UC

4.2 Startup and Automatic Mode

For DPS 7000:

The STSVR command starts FECM to process administrative functions, and FEPS(Datanet) and/or TNS (CNP 7) for the appropriate transport connection.

For DPS 7000/XTA:

The STSVR command starts OCS, TNS and FECM servers to processadministrative functions for MainWay 2600LE.

The TTSVR command stops a server.

The STSVR and TTSVR commands are described in Section 3.

The automatic mode for FECM is enabled when the STSVR command is firstentered, unless otherwise specified.

4.2.1 Datanet

4.2.1.1 Startup of FECM

A RIM attention signal received from the Datanet before FEPS is started, causesGCOS 7 to simulate the command:

STSVR FECM rsys-name (with default values).

The subsequent sequence in starting up the servers is (FECM-FEPS...) which isidentical to starting up FEPS in automatic mode.

FECM Functions

47 A2 94UC 4-9

4.2.1.2 Startup of FEPS

If the STSVR command for starting FECM or FEPS does not specify AUTO=NO,the automatic mode is enabled. This means that when FECM successfullyterminates, FEPS is automatically initialized. If FEPS fails to be initialized, FECMis automatically restarted to reload the Datanet.

The scenario used for automatic reload of the Datanet is specified in the STSVRcommand. The default scenario is STD_SCEN. The action defined in the scenariocan be overridden by the argument specified in the AUTO parameter of the STSVRand MDTSVR commands.

This automatic mode (FECM-FEPS-FECM-FEPS...) continues until a TTSVRcommand is issued. The automatic mode can be invalidated by explicitlyspecifying -NAUTO in the NODE directive of the scenario. In this case, when aRIM attention signal is received from the Datanet, only FECM is started up withoutFEPS. The operator must then start up the FEPS occurrence by entering theSTSVR command.

The automatic mode can be invalidated by the MDTSVR command.

4.2.2 CNP 7

The automatic mode is different from that of the Datanet because TNS must bepresent and active before any administrative function on the CNP 7 can beperformed.

On receiving an initialization request from the CNP 7 over the ISL, TNS notifiesthe Server Manager which then starts FECM to reload the CNP 7. This action isautomatic since it requires no operator intervention.

The scenario used for this automatic reload is STD_SCEN. The action defined inthis scenario is the default and takes the name of the CNP 7.

To disable the automatic reload of the CNP 7, the user enters the command:

MDNET CLASS=RCT OBJECT=cnp7_name RMLOAD=0.

To subsequently reload the CNP 7, the user then enters the command STSVRTYPE=FECM RSYS=cnp7_name.

The command MDNET CLASS=RCT OBJECT=cnp7_name RMLOAD=1subsequently entered is only effective when the CNP 7 retransmits an initializationrequest. Until then, nothing happens.


4-10 47 A2 94UC

4.2.3 MainWay 2600LE

For DPS 7000/XTA:

TNS server must be present and active before any administrative function on theMainWay 2600LE can be performed through FECM server.

On receiving a RIM (Request Initialization Mode) request from the MainWay2600LE over the ISL, TNS notifies the Server Manager which then starts FECM todump and/or reload the MainWay 2600LE.

This action is automatic since it requires no operator intervention.

The scenario used for this automatic reload is STD_SCEN, and the action used inthis scenario is the default).

To disable the automatic reload of the MainWay 2600LE, the user enters thecommand:

MDNET CLASS=RCT OBJECT=MainWay 2600LE_name RMLOAD=0

To subsequently reload the MainWay 2600LE, the user then enters the command:

STSVR TYPE=FECM RSYS= MainWay 2600LE _name

The following command:

MDNET CLASS=RCT OBJECT= MainWay 2600LE _name RMLOAD=1

subsequently entered, is only effective when the MainWay 2600LE retransmits aRIM request. Until then, nothing happens.

4.2.4 DPS 7000 ISL Controller

The ISL controller (LNA or LNM depending on the DPS 7000 model) isautomatically loaded when the state of the LCT passes to ENBL. FECM is startedif a more recent memory image exists than that already in the ISL controller.

FECM Functions

47 A2 94UC 4-11

4.3 Description of Files and Subfiles

Throughout the text, all system libraries used for the administration and control ofFEPs and MainWay 2600LE are prefixed by SYS.

For DPS 7000:

Six files, two source and four binary libraries, are used by FECM. The two sourcelibraries are named SYS.DSASLIB and SYS.DSACONF. The four binary librariesare named SYS.DSABLIB, SYS.DSACORE, SYS.DSADUMP and SYS.HUBG.

For DPS 7000 /XTA:

Five files, two source and three binary libraries, are used by FECM.

The two source libraries are named SYS.DSASLIB and SYS.DSACONF.The three binary libraries are named SYS.DSABLIB, SYS.DSACORE andSYS.DSADUMP.

Three of these libraries, SYS.DSACONF, SYS.DSACORE and SYS.DSADUMP,can be modified by the user to contain user-specific information.

Within these libraries, subfile names must conform to the standard conventionsdefined for LIBMAINT. A subfile name is composed of a string of letters(A-Z, a-z) numerics (0-9) and special characters.

The only special characters allowed are the underscore (_) and the minus (-),otherwise known as the hyphen.

The first character of the subfile name must be either a letter or a numeric; it cannotbe a special character. The maximum length is 31 characters. As LIBMAINT doesnot allow creating or processing a subfile name in small letters, any small letterscontained in the subfile name are first converted by FECM to capitals, beforeFECM processes the subfile.


4-12 47 A2 94UC

4.3.1 SYS.DSABLIB

It is a binary library which is not modifiable and serves only for managing theDatanet and CNP 7 or MainWay 2600LE.

All the names of the subfiles belonging to this library are prefixed automaticallywith the software version number corresponding to the DNS or CNS 7 release, orthe MainWay 2600LE software release: V3U4.

For DPS 7000:

Subfile Name Contents and UsageYTABLE Contains the directory of the Datanet and CNP 7

software image to be used as input during theirrespective software generations.

bound-units Contains the bound units of Datanet and CNP 7software images to be used as input during theirrespective software generations.

The subfiles containing the image of the bootstrap for Datanet |or CNP 7 systemsoftware to be used as input during their respective software generations are asfollows:

IMAEXC DNS system software for the DatanetSYSGEN,SYSGEN1 CNS 7 system software for the CNP 7.test-name Contains inline, online and offline tests started either

automatically by the Datanet or CNP 7, by theirrespective operators.

NOTE:

This method of calling the test from the DPS 7000enables inline testing of the Datanet or CNP 7.The Datanet or the CNP 7 need not stop normaloperations to load and execute the appropriate test.Instead, the appropriate task is called from theDPS 7000 and multitasked with the normal operationalfunction of the Datanet or CNP 7.

FECM Functions

47 A2 94UC 4-13

For DPS 7000/XTA:

Subfile Name Contents and Usage

YTABLE Contains the directory of the MainWay 2600LE softwareimage to be used as input during its software generation.

bound-units Contains the bound units of MainWay 2600LE softwareimage to be used as input during its software generation.

SYSGEN,SYSGEN1Contain the image of the bootstrap for MainWay2600LE system software to be used as input during itssoftware generation


4-14 47 A2 94UC

4.3.2 SYS.DSACONF

It is a source library. It is empty at creation.

It contains the user's own subfiles: STD_SCEN which is moved fromSYS.HSLLIB by the user and TSLIST which is created by the user.

The names of the subfiles are never prefixed with the software version number.

For DPS 7000:


STD_SCEN Contains the default scenario describing administrativefunctions to perform in automatic mode or when noscenario was specified in STSVR command for Datanetand CNP 7 administrative functions.

TSLIST Optional: Contains the default software version number,scenario and system generation input command subfilesused for the DNS or CNS 7 release when no version isspecified.

subfile-name Optional: Contains the scenario where theadministrative functions are defined with thecorresponding parameters and file-names for Datanetand CNP 7 administration.

subfile-name Contains the source generation commands to be used asinput during Datanet/CNP 7 software generation togenerate the image in the SYS.DSACORE library. Thesize of the records in the subfile must not exceed174 characters including trailing spaces for a Datanetgeneration.

subfile-name Optional: Contains the messages and/or keywords ofDatanet or CNP 7 software release modified by the userfrom the corresponding subfiles (DLCKW, DLCMSFand DLCMSG) in the SYS.DSASLIB library. The sizeof the records in the subfile must not exceed 174characters including trailing spaces for a Datanetgeneration.

FECM Functions

47 A2 94UC 4-15

For DPS 7000/XTA:


STD_SCEN

Contains the default scenario describing administrativefunctions to perform in automatic mode or when noscenario was specified in STSVR command forMainWay 2600LE administrative functions.

TSLIST

Optional: Contains the default software version number,scenario and system generation input command subfilesused for the MainWay 2600LE software release whenno version is specified.

subfile1

Optional: Contains the scenario where theadministrative functions are defined with thecorresponding parameters and file-names for MainWay2600LE administration.

subfile2Contains the source generation commands to be used asinput during MainWay 2600LE software generation togenerate the image in the SYS.DSACORE library.

subfile3

Optional: Contains the messages and/or keywords ofMainWay 2600LE software release modified by theuser from the corresponding subfiles (DLCKW,DLCMSF and DLCMSG) in the SYS.DSASLIB library.


4-16 47 A2 94UC

4.3.3 SYS.DSACORE

It is a binary library. It is empty at creation time.

It is accessed only for Datanet, CNP 7, or MainWay 2600LE management duringa SYSGEN or a LOAD function. It contains the memory image for the Datanet,CNP 7 or MainWay 2600LE created during a system generation and used forloading. The objects in this library are in the IMA (Image Memory Address)format. The subfile names are those defined in the system generation.

All the names of the subfiles are prefixed automatically with the software versionnumber corresponding to the DNS or CNS 7 or MainWay 2600LE release andmust not be prefixed in the commands.

For DPS 7000:


subfile-name Contains the generated image of Datanet and CNP 7software:- Output during their respective software generations- Input when loading them, respectively.A second subfile suffixed by 1 contains the secondimage required by the CNP 7 to load its secondarynetwork adaptors.

For DPS 7000/XTA:


subfile, subfile1 The first subfile contains the generated image ofMainWay 2600LE software:- Output during its software generation- Input when loading it.The second subfile, suffixed by 1, contains the secondimage required by the MainWay 2600LE to load itssecondary network adaptors.

FECM Functions

47 A2 94UC 4-17

4.3.4 SYS.DSADUMP

It is a binary library. It is empty at creation time.

It is accessed during a DUMP function of the Datanet, CNP 7, LNA or MainWay2600LE. It contains a dump of the remote system or controller. The subfile namesare those defined in the scenario suffixed with 1 or 2. The oldest version of thedump is replaced by the new dump.

The names of the subfiles are never prefixed with the software version number.

For DPS 7000:

Subfile Name Contents and Usagend-name1 and nd-name2

Contains the last 2 images of the Datanet, CNP 7 orLNA memory dumps. The latest version of the previousdump 1 or 2 is replaced with the new dump.

For DPS 7000/XTA:

Subfile Name Contents and Usagename1,name2

Contains the last 2 images of the MainWay 2600LEmemory dumps. The oldest version of the previousdump1 or 2 is replaced with the new dump.

Dxx_yyMWname1,Dxx_yyMWname2

Contains the last 2 images of an adapter dumps.• xx is the rank of the rack.

• yy is the rank of the adapter in the rack.

The oldest version of the previous dump1or 2 isreplaced with the new dump.


4-18 47 A2 94UC

4.3.5 SYS.DSASLIB

An unmodifiable source library for managing both Datanet, CNP 7 or MainWay2600LE. All subfile names except TSLIST, are automatically prefixed with theDNS or CNP 7, or MainWay 2600LE software version number.

For DPS 7000:

Subfile Name Contents and UsageSYSGEN Contains the configuration file for SYSGEN,

SYSGEN1 in SYS.DSABLIB.CHXMOD Contains the list of BLIB-modules to be used as input

during Datanet or CNP 7 software generation.PATCH0 Contains patches for IMAEXC in SYS.DSABLIB, to be

used as input during DNS software generation.This subfile is not used by the CNP 7.

PATCH1 Contains patches to Datanet or CNP 7 bound-units to beused as input during software generation.

PATCH2 Contains the patches for the image of Datanet or CNP 7software in memory, used for dynamic input:- during their respective software generations- when loading them, respectively.

TSLIST Contains the list of software versions available on theDPS 7000 for DNS and CNS 7 releases. It is unique fora site and is never prefixed.

DLCKW Contains the list of all keywords used as input duringDatanet or CNP 7 software generation.

DLCMSF Contains the list of all messages in French for inputduring DNS or CNS 7 software generation.

DLCMSG Contains the list of all messages in English for inputduring DNS or CNS 7 software generation.

UNCP1C Contains an example of input for system generation.This member is to be moved in SYS.DSACONF libraryby the user (and may be renamed). It can then bemodified to suit the needs of the user.

FECM Functions

47 A2 94UC 4-19

For DPS 7000/XTA:

Subfile Name Contents and UsageSYSGENCHXMOD

Contains the configuration file for SYSGEN,SYSGEN1 in SYS.DSABLIB.

Contains the list of BLIB-modules to be used as inputduring MainWay 2600LE software generation.

PATCH0

PATCH1

PATCH2

No longer used

Contains patches to MainWay 2600LE bound-units tobe used as input during software generation.

Contains the patches for the image of MainWay 2600LEsoftware in memory, used for dynamic input:- during software generation- during load.

TSLIST Contains the list of software versions available on theDPS 7000/XTA for MainWay 2600LE releases. It isunique for a site and is never prefixed.

DLCKW

DLCMSF

DLCMSG

Contains the list of all keywords used as input duringMainWay 2600LE software generation.

Contains the list of all messages in French for inputduring MainWay 2600LE software generation.

Contains the list of all messages in English for inputduring MainWay 2600LE software generation.


4-20 47 A2 94UC

4.3.6 SYS.HUBG

It is a binary library which is accessed only for managing the LCT of type ISL.This library cannot be modified.

The library consists of a subfile containing the memory image of the LNA (localnetwork adaptor) board of the SPA. The name of the subfile is never prefixed.

Subfile Name Contents and UsageLNRA0xx Contains the memory image which is loaded and

executed in the LNA board instead of the PROM image.xx are two hexadecimal characters representing thefirmware release of the LNA. The greater the value ofxx, the more recent is the release.

FECM Functions

47 A2 94UC 4-21

4.4 Description of Scenarios

The scenario defines the administrative functions to be performed on the Datanet ,the CNP 7 for DPS 7000, or the MainWay 2600LE for DPS 7000/XTA.

Scenarios for the OCS Front End integrated controller are discussed in Section 5.

The scenario is a subfile of the SYS.DSACONF library.

A standard scenario is delivered with the DNS or CNS 7 release. The scenariocontains the orders for the different administrative functions with default valuessupplied for file names and parameters. This scenario is created in a subfileSTD_SCEN in the SYS.HSLLIB library.

When the SCENARIO parameter of the STSVR command is not specified, thedefault STD_SCEN scenario is used.

The user can use one of two methods to define a specific scenario:

• either to create a new scenario to incorporate the necessary modifications

• or to move and modify the STD_SCEN scenario in the SYS.HSLLIB library.

In the first case of a new scenario, the subfile name of the scenario must bespecified in the SCENARIO parameter of the STSVR command.

However, the new scenario will not be taken into account during automaticprocessing when the front-end processor is powered up and initialized.

This method is therefore suitable for testing a new scenario without the risk ofaltering the STD_SCEN scenario used for production.

A new scenario is tested for either or both of the following reasons:

• either for new or modified administrative functions

• or for a new DNS or CNS 7 Release.

• or for a MainWay 2600LE Release.

In the second and the third case of modifying an existing STD_SCEN scenario, thesubfile name need not be specified in the STSVR command.

When the front-end processor is powered up and initialized, it will be automaticallyloaded in accordance with the STD_SCEN scenario.

This method should be used after the scenario has been tested and proved tofunction as expected.


4-22 47 A2 94UC

4.4.1 Software Version Number

To make the scenario as independent as possible of the DNS, CNS 7 release orDNS-E release, the software version number is never specified in the file namesdefined for the scenario. The version number is specified in the VERSIONparameter of the STSVR command.

It may also be specified in the scenario either for all the front-end processors whoseadministrative functions are described in the scenario or for just one specific front-end processor.

A default version number may be installed on the DPS 7000 or DPS 7000/XTA,which makes use of the current release during automatic mode. This feature saveskeying in the VERSION parameter in the STSVR command. To install the defaultversion number, a subfile named TSLIST is created in the SYS.DSACONF library.The TSLIST subfile need contain only one record for either the version numbersuch as V4U1, V3U4 or NONE if no version is applicable.

If such a subfile does not exist in SYS.DSACONF and the VERSION parameter ofthe STSVR command was not specified, the default version number is taken fromthe first record of the subfile TSLIST in SYS.DSASLIB.

For DPS 7000, this subfile is created by the DIUF utility and contains the list of theversion numbers on the site.

For DPS 7000/XTA, the subfile TSLIST needs to contain only one record: V3U4which is the version number of MainWay 2600LE.

Any version number specified in the VERSION parameter of the STSVRcommand, or in the scenario, or in the TSLIST subfile of SYS.DSACONF mustexist in the list of version numbers available.

FECM Functions

47 A2 94UC 4-23

4.4.2 General Rules for the Scenario

The scenario defines administrative functions for one or several front-endprocessors. Each NODE order describes one system and is unique for that system.If several NODE orders bear the same name, only the first NODE order will betaken into consideration, the rest being ignored. Subsequent NODE orders withdifferent names will be considered.

For DPS 7000: The system is a FEP.

For DPS 7000/XTA: The system is a MainWay 2600LE.

EXAMPLE:

NODE SYS1 : administrative functions for SYS1 : : NODE SYS2 : administrative functions for SYS2 : : NODE SYS3 : :❑

The name of the NODE order (SYS1, SYS2, SYS3...) is that given to the front-endprocessor at NETGEN and is the same as the argument of the RSYS parameter inthe STSVR command when starting up FECM. Within the part of the scenariodefined by the NODE order, the different administrative functions that are requiredfor execution are defined by the SCEN order.


4-24 47 A2 94UC

EXAMPLE:

NODE SYS1 SCEN LOAD : administrative functions : : SCEN SYSGEN : administrative functions : : SCEN DUMP : :❑

The parameter of the SCEN order (LOAD, SYSGEN and DUMP) corresponds tothe argument specified for the ACTION parameter in the STSVR command.

Each administrative function is defined in its entirety by the part of the scenariobelonging to the SCEN order.

The principal functions for managing the front-end processor are systemgeneration, load (LOAD and GO) and dump.

4.4.3 Syntax of the Scenario

In the orders for the scenario, all items are separated by a blank and each orderstarts at column one.

A keyword or parameter value cannot be split over 2 lines.

"&" appearing as the last character of a line indicates that the line is continued onthe next line.

For DPS 7000:

The syntax of the scenario is compatible with the syntax of the scenarios used bythe DNS or CNS 7 release with the exceptions that the following do not exist forDNS or CNS 7, namely

• the VERSION order

• and the -VERSION option of the NODE order.

FECM Functions

47 A2 94UC 4-25

4.4.3.1 VERSION order

VERSION version

version Default version number of the software to be used forthe front-end processors following the VERSIONorder and for which the -VERSION option of theNODE order is not specified.

This version number is not taken into account if theVERSION parameter has been specified in the STSVRcommand.

It must not exceed 4 characters.

The MainWay 2600LE default version number of thesoftware is V3U4.

The VERSION order must be the first order of the scenario and must precede anyNODE order to which it applies.

4.4.3.2 NODE order

NODE name [scen] [-VERSION version] [-NAUTO ]

name name of the front-end processor to be managed asdeclared in the RSYS directive.


scen name of the scenario defined by the SCEN order usedin automatic mode. When the ACTION parameter ofthe STSVR command is not specified, the part of thescenario defined by the corresponding SCEN order isused.

If this name is not specified, the first scenario definedby the SCEN order is used.


version version number of the software to be used for thatgiven front-end processor when the VERSIONparameter was not specified in STSVR command or inautomatic mode.



4-26 47 A2 94UC

This parameter must not be used to select a node in thescenario subfile. If more than one version applies for anode, there must be as many scenario subfiles inSYS.DSACONF as versions.

EXAMPLE:

For DPS 7000:

2 versions C1U6 and V4U1 apply for node FEP1. To distinguish theadministrative functions for the 2 versions, 2 scenarios must be written.

- In scenario STD_SCEN, the NODE order would be: NODE FEP1 -VERSION C1U6

- In scenario FEP1V4U1, the NODE order would be: NODE FEP1 -VERSION V4U1

For DPS 7000/XTA:

One version V3U4 apply for MainWay 2600LE. To distinguish the administrativefunctions for this version, one scenario must be written.

- In scenario STD_SCEN, the NODE order would be:NODE SYS1 -VERSION V3U4

❑

NAUTO applies only to the Datanet. Indicates that theautomatic mode is not to be activated when theDatanet is automatically reloaded by a RIM attentionsignal. In this case, only FECM is started up toexecute the scenario defined for the automatic reloadof the Datanet; no startup of FEPS occurs.

The NAUTO parameter of the NODE order isoverridden if a subsequent STSVR command to startFECM specifies auto, that is, either AUTO=name-8 orits default. In this case, auto of the STSVR commandis taken into account resulting in FEPS being startedup after FECM terminates.

FECM Functions

47 A2 94UC 4-27

4.4.3.3 SCEN order

SCEN name

name name of a scenario defined in the following orders,describing the management functions on the front-endprocessor. This name corresponds to the namespecified in the ACTION parameter of the STSVRcommand.


4.4.3.4 DUMP order

DUMP [file]

file defines the file in which the dump is written. Seeparagraph 4.5.4. If this file name is not specified, adefault name is provided with the node name.

The DUMP order may be followed only by a LOAD order.

4.4.3.5 LOAD order

LOAD file1 [MAP file2]

file1 defines the file to be loaded on the front-end processorduring load or generation. See paragraphs 4.5.2and 4.5.3.

file2 defines the file in which the MAP (the report list fromthe Datanet, CNP 7 or MainWay 2600LE) will bewritten during load or generation. See paragraph 4.5.2.

The LOAD order must be followed by a GO order.


4-28 47 A2 94UC

4.4.3.6 GO order

GO parameters

parameters parameters those parameters defined by the DNS, CNS7 or DNS-E release.

The complete description of the GO order is treated in the following manuals:

• for the Datanet, DNS NGL Reference Manual

• for the CNP 7, CNS 7 NGL Reference Manual.

• for the MainWay 2600LE, DNS-E NGL Reference Manual.

The maximum size of a GO order with its parameters is limited

• by the Datanet to 160 characters

• and, by the CNP 7 to 980 characters.

If a greater value is needed to specify all the parameters, the -GOFILE parametersof the GO order must be used. The GO order must follow the LOAD order.

4.4.3.7 Comment

* comment

comment any character string

Continuation Line

& appearing as the last character of a line indicates that the line is continued on thenext line.

A keyword or parameter value cannot be split over 2 lines.

FECM Functions

47 A2 94UC 4-29

4.5 Administrative Functions

Each administrative function has its own files associated with a given scenario.The following manuals give details on the SYSGEN parameters and sourceconfiguration input:

• for the Datanet, DNS NGL Reference Manual

• for the CNP 7, CNS 7 NGL Reference Manual.

Administration for the OCS Front End integrated controller are discussed inSection 5.

4.5.1 File Names

All the files specified in the scenario or referenced in the Datanet or CNP 7commands are interpreted in the GCOS 7 environment as follows:

• The first 4 characters of the file name are prefixed by SYS.DSA to form aGCOS 7 file name.

The following are examples of equivalent references: BLIB references the file SYS.DSABLIB CONF SYS.DSACONF CORE SYS.DSACORE DUMP SYS.DSADUMP SLIB SYS.DSASLIB

• the remainder of the file name string is interpreted as the name of the subfilewithin the specified GCOS 7 library concatenated to the end of the -characterstring software version of the Datanet or CNP 7 system, it exists.

EXAMPLES:

The PATCH1 function in the configuration command file PATCH1 SLIBPATCH1 isinterpreted by GCOS 7 as:

• Library SYS.DSALIB

• Subfile in this library being− either C1U6PATCH1 if the software version is C1U6− or V4U1PATCH1 if the software version is V4U1.


4-30 47 A2 94UC

The END function in the configuration command file END -SAVE COREDN20-START is interpreted by GCOS 7 as:

• Library SYS.DSACORE

• Subfile in this library being− either C1U6DN20 if the software version is C1U6− or V4U1DN20 if the software version is V4U1.

The DIR function in the configuration command file DIR BLIB is interpreted byGCOS 7 as:

• Library SYS.DSABLIB

• without any subfile reference.

❑

4.5.2 Front-end Processor Generation: SYSGEN

The SYSGEN function specifies that the Datanet or CNP 7 is to generate itssoftware image. SYSGEN error messages appear on the console.

4.5.2.1 Datanet System Generation

Generation Description

The generation proceeds in the following sequence:

• the system software in the IMAEXC subfile of SYS.DSABLIB is bootstrappedinto the Datanet

• the patches in the PATCH0 subfile of SYS.DSASLIB corresponding to thisversion of software are then applied to it

• the source configuration input subfile containing the directives for the systemgeneration is read in from SYS.DSACONF to be loaded in the Datanet by meansof GO in the scenario

• if specified in the source configuration, the messages and the keywords are readin from SYS.DSASLIB or SYS.DSACONF if these were previously modifiedby the user

• the commands used optionally to link the DNS modules, depend on theconfiguration functions loaded from the CHXMOD subfile in SYS.DSASLIB

• the subfile YTABLE and the bound-units (equivalent to GCOS 7 compile units)are loaded from SYS.DSABLIB to generate the memory image of the Datanet

FECM Functions

47 A2 94UC 4-31

• this memory image is patched if the PATCH1 option is specified in the sourceconfiguration (PATCH1 subfile in SYS.DSASLIB)

• the memory image generated is now saved in a subfile of SYS.DSACORE, itsname being specified in:END -SAVE COREsubfile for the source configuration inputandGO CONFsubfile1 -SVPAT2 COREsubfile2 for the scenario subfileafter PATCH2 patches have been applied to the memory image(-PAT2 SLIBPATCH2 parameter of GO).

The previous memory image (the same subfile and the same software version) isdeleted and replaced with the new memory image when it has been successfullycreated. If any abnormal termination occurs, the previous memory image isretained.

The following considerations for generating the Datanet software must be taken:

• If START is specified in END of the source configuration input, the systemgeneration starts executing.

An STSVR command for loading the Datanet after such a SYSGEN is notnecessary.

• A subsequent load of this memory image must specify the same subfilecontaining the memory image in SYS.DSACORE as that specified for

− either END -SAVE in the configuration input− or GO -SVPAT2 in the scenario.

Applying the patches in PATCH2 depends on the following conditions:

• If the memory image was saved before PATCH2 is applied in END -SAVE, GOof the load function must specify -PAT2 to apply the patches at loading.

• If the memory image was saved after PATCH2 has been applied in GO -SVPAT2,GO of the load function must specify -NOPAT2 so that the patches are notapplied again.

NOTE:All the subfile names in SYS.DSABLIB, SYS.DSASLIB and SYS.DSACORElibraries are automatically prefixed by FECM with the software version numberof the DNS release.


4-32 47 A2 94UC

Scenario Description

The SYSGEN function is described in the scenario by a LOAD order followed by aGO order. Their syntax is described as follows:


file1 defines the file in which the bootstrap of the DNSsystem software is fetched. It must be of the formBLIBIMAEXC, where:

− BLIB corresponds to SYS.DSABLIB library

− IMAEXC corresponds to the subfile containing thesystem bootstrap to be loaded on the front-endprocessor. The real name of this subfile is prefixedby the software version number (if it exists). Theversion number is automatically added by FECMand need not be specified.

MAP specifies that the lists produced during SYSGEN are to be written on a filedefined by the user.

file2 is of the format:

CONFsubfile

where:

• CONF corresponds to SYS.DSACONF library• subfile is the user-defined file in which the listings are produced.

If MAP is not specified, an implicit file2 will be created in SYS.DSACONF libraryby the name node-nameH, where node-name is the name of the Datanet performingthe SYSGEN.

FECM Functions

47 A2 94UC 4-33

The GO order must follow the LOAD order in the scenario.

GO file1 [ { -PATCH } ] [ { } file2 ] [ { -P0 } ]

[ { { -P2 | -PAT2 } file3 } ] [ { } ] [ { { -NP | -NOPAT2 } } ]

[ { -SVPAT2 } ] [ { } file4 ] [ { -SV } ]

[ { -LCPAT2 } ] [ { } file5 ] [ { -LC } ]

[ dns-parameters ]

file1 defines the file containing the source configurationinput. It must be of the format CONFsubfile where:

− CONF corresponds to SYS.DSACONF library

− subfile corresponds to the subfile name containingthe source configuration input

-P0 or -PATCH specifies that patches for updating the bootstrap are to be applied.

file2 defines the file in which the patches are located. Itmust take the name SLIBPATCH0, where:

− SLIB corresponds to SYS.DSASLIB library

− PATCH0 is the subfile containing the patches. Thereal name of this subfile is prefixed by FECM withthe software version number.


4-34 47 A2 94UC

-P2 or PAT2 specifies that patches for updating the generated DNS image are to beapplied.

file3 defines the file in which the patches are located. Itmust take the name SLIBPATCH2 where:


− PATCH2 is the subfile containing the patches. Thereal name of this subfile is prefixed by FECM withthe software version number.

-SV or SVPAT2 specifies that the memory image is to be saved after the patches inPATCH2 have been applied.

file4 defines the file in which the memory image is savedfor a further load function. It must take the formatCOREsubfile where:

− CORE corresponds to SYS.DSACORE library

− subfile is where the memory image is saved. Thereal name of this subfile is prefixed by FECM withthe software version number.

-LC or LCPAT2 specifies that the memory image is to be saved on the local diskafter the patches in PATCH2 have been applied.

file5 defines the file in the local disk in which the memoryimage is saved.

dns-parameters are specific parameters processed by the Datanet.

DN7500 versions of the Datanet which are configured with a local disk and whichrun on DNS V4U1 can perform a local SYSGEN without going through theDPS 7000. To do this the LOAD order in the SCENARIO must specify:

LOAD subfile -LC

where

• subfile is the name of the file to bootstrap the Datanet• and -LC specifies that the file is located on the local disk.

The GO order must then follow the LOAD order in the scenario. The files file1,file2, file3, and file4 can be saved either on the local disk or on the DPS 7000 ifthey are prefixed with H:. The rules defined above apply for these files.

file5 now defines the name of the file on the local disk. It cannot be prefixedby H:.

FECM Functions

47 A2 94UC 4-35

EXAMPLE OF EXECUTION

S: STSVR FECM BP22 ACTION=SYSGEN CA20 ADM_BP22 LAUNCHED BY OPERATOR COMMAND 12.19 X32 STARTED FECM OPERATOR S CA21 ADM_BP22 STARTED FE01 BP22 SYSGEN STARTED FROM SCENARIO STD_SCEN VERSION V4U1 FE04 BP22 YTABLE :1991/01/15 FE04 BP22 SYSGEN STILL RUNNING FE04 BP22 ALL MODULES ARE LINKED FE04 BP22 ******* SYSGEN IS COMPLETED ******* FE04 BP22 **** INSERT ZONE 03435/ 02504 ***** FE04 BP22 ***** INSERT # 011/127 ***** FE04 BP22 DNS_DATE: 1987/11/4 12:19:15 FE04 BP22 *** LOAD TIME : 1987/11/4 12:29:15 FE02 BP22 SYSGEN COMPLETED CA21 ADM_BP22 COMPLETED 12.29 X32.1 COMPLETED FECM OPERATOR S❑

EXAMPLE OF SCENARIO

10 NODE BP22 LOAD 20 * 30 SCEN LOAD 40 LOAD COREBP22I 50 GO 60 * 70 SCEN DUMP 80 DUMP DUMPBP22 90 *100 --->SCEN SYSGEN110 --->LOAD BLIBIMAEXC120 --->GO CONFBP22C -PAT2 SLIBPATCH2 -SVPAT2 COREBP22I &130 ---> -PATCH SLIBPATCH0 -MOD 500 -SYMB 5000140 --->*❑


4-36 47 A2 94UC

4.5.2.2 CNP 7 System Generation


Two FECM jobs are started up by the command STSVR TYPE=FECMACTION=sysgen RSYS=cnp7_name.

The first FECM job bootstraps the CNS 7 system software in the two subfiles,SYSGEN and SYSGEN1, of SYS.DSABLIB into the CNP 7. The job then passescontrol to the CNP 7 and terminates. The CNP 7 requests connection to the$NASF mailbox in the DPS 7000.

The second FECM job then starts the ASF function, and the generation proceeds inthe following sequence:

• the source configuration input subfile containing the directives for the systemgeneration is read in from SYS.DSACONF to be loaded in the CNP 7 by meansof GO in the scenario

• if specified in the source configuration, the messages and the keywords are readin from SYS.DSASLIB or SYS.DSACONF if these were previously modifiedby the user

• the commands used optionally to link the CNS 7 modules, depend on theconfiguration functions loaded from the CHXMOD subfile in SYS.DSASLIB

• the subfile YTABLE and the bound-units (GCOS 7 compile-unit equivalents) areloaded from SYS.DSABLIB to generate the memory image of the CNP 7

• this memory image is patched if the PATCH1 option is specified in the sourceconfiguration (PATCH1 subfile in SYS.DSASLIB)

• the memory image generated is now saved in a subfile of SYS.DSACORE, itsname being specified in:END -SAVE COREsubfile for the source configuration input.

The 2 subfiles created by SAVE are subfile and subfile1, where subfile is auser-defined name.


Once SYSGEN has terminated, the user verifies if the execution is normal. If so,the user then issues the command

STSVR FECM RSYS=cnp7-name

to load the CNP 7.

FECM Functions

47 A2 94UC 4-37

The subfile used to load the memory image must be that specified in END -SAVEof the configuration input.

Applying PATCH2 proceeds as follows:

1. For a new SYSGEN, if PATCH2 was specified in the source configuration, theresulting SYSGEN will contain the patches of PATCH2.

2. To modify an existing system, PATCH2 is applied as follows: GO -SYSGEN "OLD=ocore, NEW=ncore, P1=SLIBPATCH1:SLIBPATCH2, HIST=hconf"

where

− ocore is the pathname of the file containing the memory image of theprevious sysgen (this file is often referred to IMAMEM)

− ncore is the pathname of the file containing the updated memory in whichthe patches have been applied

− hconf is the pathname of the file containing the report of the CNS 7generation of the format CONFsubfile.

For both (1) and (2), the GO order at loading must specify -NL and -NP.

3. If at sysgen, PATCH2 is not applied either by means of (1) or (2), the patchesin PATCH2 must be applied at loading by the order GO -P2 SLIBPATCH2.

NOTE:All the subfile names in SYS.DSABLIB, SYS.DSASLIB and SYS.DSACOREare automatically prefixed by FECM with the software version number of theCNS 7 release.


The SYSGEN function is described in the scenario by a LOAD order followed by aGO order.


file1 defines the file in which the bootstrap of the CNS 7system software is fetched. It must take the nameBLIBSYSGEN, where:


− SYSGEN corresponds to the subfile containing thesystem bootstrap to be loaded in the CNP 7. Thereal name of this subfile is prefixed by FECM withthe software version number.


4-38 47 A2 94UC

MAP specifies that the lists produced during sysgen are written to file2, where:

file2 defines the file in which the lists are produced. It musttake the format CONFsubfile, where:


− subfile is the file in which listings are produced. Noprefix is added to this subfile name.

NOTE:MAP only applies to the first FECM job. For the second FECM job, HIST ofthe GO order defines the listing of the CNP 7 generation.


GO -SYSGEN "CONF=file1, HIST=file2"

[ { CNP7 02:00 0800385F0200 } ][ -SITE { } ][ { scid dsa-address ethernet-address } ]

[ { DPS7 01:00 0800385F0100 } ][ -REMOTE { } ][ { scid dsa-address ethernet-address } ][ { SLIBPATCH2 } ][ -P2 { } ] -NL cns-parameters[ { file3 } ]

file1 defines the file containing the source configurationinput. It must take the format CONFsubfile, where:


− subfile holds the source configuration input.

file2 defines the file to contain the report of the CNS 7generation. It must take the format CONFsubfile,where:


− subfile holds the CNS 7 generation.

FECM Functions

47 A2 94UC 4-39

file3 defines the file in which the patches are located. Thedefault name is SLIBPATCH2, where:


− PATCH2 corresponds to the subfile name containingthe patches. The real name of this subfile isprefixed by FECM with the software versionnumber.

-NL indicates that the applications of the patch2 file are not to appear at theDPS 7000 console.

cns-parameters are specific parameters processed by the CNP 7.


S: STSVR FECM BL02 SYSGEN CA20 ADM_BL02 LAUNCHED BY OPERATOR COMMAND 16.16 X111 STARTED FECM OPERATOR S CA21 ADM_BL02 STARTED FE01 BL02 SYSGEN STARTED FROM SCENARIO STD_SCEN VERSION A0U2 FE04 BL02 FE04 BL02 ***CNS *RLS:AOU2 *PTS:0000/PTL:0000 *SYS:SYSGEN*GEN:1987/11/4 17:31:37*** FE04 BL02 FE04 BL02 Initial patches are installed on DEA 1 : 0 error(s) FE04 BL02 FE04 BL02 Loading of DEA 1 , CNP7 , is completed FE04 BL02 FE04 BL02 Initial patches are installed on DEA 2 : 0 error(s) FE04 BL02 FE04 BL02 Loading of DEA 2 , DCA2 , is completed FE04 BL02 FE04 BL02 *** LOAD TIME 1987/11/4 16:17:33 *** FE02 BL02 SYSGEN COMPLETED CA21 ADM_BL02 COMPLETED 16.19 X111.1 COMPLETED FECM OPERATOR S CA20 ASF_BL02 LAUNCHED FOR ASF SERVICE 16.19 X112 STARTED FECM OPERATOR S CA21 ASF_BL02 STARTED FE01 BL02 ASF STARTED FE02 BL02 ASF COMPLETED 16.39 X112.1 COMPLETED FECM OPERATOR S❑


4-40 47 A2 94UC

EXAMPLE OF SCENARIO

10 NODE BL02 RELOAD -VERSION AOU2 20 * 30 SCEN LOAD 40 LOAD COREBL02I 50 GO -P2 SLIBPATCH2 60 * 70 SCEN RELOAD 80 DUMP DUMPBL02 90 LOAD COREBL02I100 GO -P2 SLIBPATCH2 -NL110 *120 SCEN DUMP130 DUMP DUMPBL02140 *150 --->SCEN SYSGEN160 --->LOAD BLIBSYSGEN170 --->GO -NL -PAT2 SLIBPATCH2 -SITE BL02 60:02 080038503C02 &180 ---> -REMOTE BL17 60:23 080038503C17 &190 ---> -SYSGEN "CONF=CONFBL02C,HIST=CONFBL02L"200 --->*❑

FECM Functions

47 A2 94UC 4-41

MAP listscenario listsource-configurationpatch list

scenariosource-configuration

memory imageCHXMODPATCH0PATCH1PATCH2

IMAEXC(DNS) orSYSGEN andSYSGEN1 (CNS 7)

YTABLEbound-units

<node>FRONT-END PROCESSOR

DPS 7000 HOST STSVR FECM<node>

SYS.OUT SYS.DSACONF SYS.DSACORE SYS.DSABLIBSYS.DSASLIB

FECM

SYSGEN


4-42 47 A2 94UC

Cross Reference of GCOS Files to Source Configuration Commands

Source Configuration Commands

DNS/CNS 7 CommandGCOS File

Library SubfileLANG... SYS.DSABLIB DLCKW

DLCMSF or DLCMSGTMP TEMP (for CNP7 only) gcos7-defined cns7-definedDIR BLIB SYS.DSABLIBLKFL SLIBCHXMOD SYS.DSASLIB CHXMODPATCH1 SLIBPATCH1 SYS.DSASLIB PATCH1PATCH2 SLIBPATCH2(DNS only) SYS.DSASLIB PATCH2END -SAVE COREsubfile SYS.DSACORE user-defined

"GO" Order in Scenario for Datanet

Go OrderGCOS File

Library SubfileGO CONFsubfile SYS.DSACONF user-defined-PATCH SLIBPATCH0 SYS.DSASLIB PATCH0-PAT2 SLIBPATCH2 SYS.DSASLIB PATCH2-SVPAT2 COREsubfile SYS.DSACORE user-defined

GO Order in Scenario for CNP 7GO Order GCOS File

Library SubfileGO -SYSGEN "CONF=file1, SYS.DSACONF user-defined HIST=file2" SYS.DSACONF user-defined -P2 file3 SYS.DSASLIB PATCH2

Note that FECM prefixes all GCOS subfile names with the software versionnumber unless otherwise specified.

A user-defined subfile can take any name.

FECM Functions

47 A2 94UC 4-43

4.5.2.3 MainWay 2600LE System Generation


Two FECM jobs are started up by the command:

STSVR TYPE=FECM ACTION=sysgen RSYS=MainWay 2600LE_name

The first FECM job (ADM function) bootstraps the MainWay 2600LE systemsoftware in the two subfiles, SYSGEN and SYSGEN1, of SYS.DSABLIB into theMainWay 2600LE. FECM dialogs with MainWay 2600LE through TNS serverduring this first step. The FECM job then passes control to the MainWay 2600LEand terminates.

The MainWay 2600LE then requests connection to the $NASF mailbox in the DPS7000/XTA, through OCS server.

The second FECM job then starts the ASF function and dialogs with MainWay2600LE through OCS server during this second step.The generation proceeds in the following sequence:

• the source configuration input subfile containing the directives for the systemgeneration is read in from SYS.DSACONF to be loaded in the MainWay2600LE, by means of GO command in the scenario

• if specified in the source configuration, the messages and the keywords are readin from SYS.DSASLIB or SYS.DSACONF if these were previously modifiedby the user.

• the commands optionally used to link the MainWay 2600LE modules, depend onthe configuration functions loaded from the CHXMOD subfile inSYS.DSASLIB.

• the subfile YTABLE and the bound-units are loaded from SYS.DSABLIB togenerate the memory image of the MainWay 2600LE.

• this memory image is automatically patched with PATCH1 if no PATCHcommands is specified in the source configuration.Otherwise,it is patched with patch file list given in PATCH command describedin the source configuration.

• the memory image generated is now saved in a subfile of SYS.DSACORE, itsname being specified in: END -SAVE COREsubfile for the source configurationinput.The 2 subfiles created by SAVE are subfile and subfile1, where subfile is a user-defined name.A map file named subfileM is automatically produced by the MainWay 2600LEin the SYS.DSACONF library.


4-44 47 A2 94UC


Once SYSGEN has terminated, the user verifies if the execution is normal.If so, the user then issues the following command:

STSVR FECM RSYS=MainWay 2600LE_name ACTION=LOAD

to load the MainWay 2600LE.

The subfile used to load the memory image must be that specified in END –SAVEof the configuration input.

Applying PATCH2 on image created during sysgen proceeds as follows:

• If PATCH2 is specified in the source configuration:PATCH SLIBPATCH1 SLIBPATCH2the resulting image will contain the patches of PATCH2.

• If at sysgen, PATCH2 is not specified in the source configuration:PATCH SLIBPATCH1the patches in PATCH2 must be applied at loading by the order:GO -PT SLIBPATCH2

NOTE:All the subfile names in SYS.DSABLIB, SYS.DSASLIB and SYS.DSACOREare automatically prefixed by FECM with the software version number of theMainWay 2600LE release: V3U4.

FECM Functions

47 A2 94UC 4-45


The SYSGEN function is described in the scenario by a LOAD order followed by aGO order.


file1 defines the file in which the bootstrap of the MainWay2600LE system software is fetched. It must take thename BLIBSYSGEN, where:


− SYSGEN corresponds to the subfile containing thesystem bootstrap to be loaded in the MainWay2600LE. The real name of this subfile is prefixed byFECM with the software version number.

MAP specifies that the lists produced during sysgenare written to file2, where:

file2 defines the file in which the lists are produced. It musttake the format CONFsubfile, where:


− subfile is the file in which listings are produced.No prefix is added to this subfile name.

NOTE:MAP only applies to the first FECM job, launched by STSVR command(FECM ADM). For the second FECM job, automatically launched onMainWay 2600LE request (FECM ASF), HIST of the GO order defines thelisting of the MainWay 2600LE generation.


GO –SYSGEN CONF=file1,HIST=file2 –PT SLIBPATCH2 –SITE name1 –REMOTE name2 scid ethaddress


4-46 47 A2 94UC

file1 defines the file containing the source configurationinput. It must take the format CONFsubfile, where:− CONF corresponds to SYS.DSACONF library− subfile holds the source configuration input.

file2 defines the file to contain the report of the MainWay2600LE generation report.It must take the format CONFsubfile, where:− CONF corresponds to SYS.DSACONF library− subfile holds the MainWay 2600LE generation.

-PT option is mandatory to apply PATCH2 file on delivered memory image ofsysgen (PATCH1 is already applied at SYSGEN time of that delivered image).

This subfile is located in SYS.DSASLIB. The real name of this subfile is prefixedby FECM with the software version number.

-SITE option is necessary for substitution in delivered memory image of sysgen,

name1 name of the MainWay 2600LE to be managed, asdeclared in the RSYS directive of NETGEN.

-REMOTE option is necessary for substitution in delivered memory image ofsysgen.

name2 name of the local DPS 7000/XTA system, as declaredin the LSYS directive of NETGEN.

scid Session Control Identifier of the local DPS 7000/XTAsystem, as declared in the LSC directive of NETGEN.

ethadress MAC address of the local controller of one of the OCSservers of the DPS 7000/XTA, as declared in the LCTdirective of NETGEN.

FECM Functions

47 A2 94UC 4-47


S: STSVR FECM BC86 SYSGENCA20 ADM_BC86 LAUNCHED BY OPERATOR COMMAND 13.35 X118 STARTED FECM OPERATOR S CA21 ADM_BC86 STARTED FE01 BC86 SYSGEN STARTED FROM SCENARIO STD_SCEN VERSION V3U4 FE04 BC86 SYSER: rrst 01/09/04 11:36 AD:60106F28 CPU: 8IMA: COREBC86 VS: V3U4 FE04 BC86 FE04 BC86 *DNS-E V3U4.000 P1.002 P2.008 P3.000*IMA:BLIBSYSG2001/05/1811:35* FE04 BC86 FE04 BC86 FE04 BC86 *** LOAD TIME 2001/09/04 13:35:58 *** FE02 BC86 SYSGEN COMPLETED CA21 ADM_BC86 COMPLETED 13.36 X118.1 COMPLETED FECM OPERATOR S CA20 ASF_BC86 LAUNCHED FOR ASF SERVICE 13.36 X119 STARTED FECM OPERATOR S CA21 ASF_BC86 STARTED FE01 BC86 ASF STARTED FE04 BC86 ******** START OF SYSGEN OPERATION FE04 BC86 ******** READING CONFIGURATION FILE FE04 BC86 ******** GETTING THE USEFUL SUBSET OF YTABLE FE04 BC86 ******** MAPPING RESOLUTION FE04 BC86 ******** LOCAL DIALOG TREATMENT FE04 BC86 ******** IMA BUILDING PHASE FE04 BC86 ******** END OF THE OBJECT TABLE GENERATION FE04 BC86 ******** SYSGEN ERROR NUMBER : 0000 FE04 BC86 ******** START LINKER FE04 BC86 ******** START LINKER PHASE 1 FE04 BC86 ******** START LINKER PHASE 2 FE04 BC86 ******** START TO LINK CPU: CT80 FE04 BC86 ******** START TO LINK CPU: 06-03-01 FE04 BC86 ******** LINK TERMINATED OF COREBC86 FE04 BC86 ******** LINKER ERROR NUMBER : 0000 FE04 BC86 ******** START PATCH PROCESSING FE04 BC86 ******** END OF GENERATION FE04 BC86 ******** SYSGEN ERROR NUMBER : 0000 FE04 BC86 ******** LINKER ERROR NUMBER : 0000 FE04 BC86 ******** DEBUG ERROR NUMBER : 0000 FE04 BC86 ******** TOTAL ERROR NUMBER : 0000 FE02 BC86 ASF COMPLETED 13.41 X119.1 COMPLETED FECM OPERATOR S

❑


4-48 47 A2 94UC

EXAMPLE OF SCENARIO

NODE BC86 SYSGEN -VERSION V3U4*SCEN SYSGENLOAD BLIBSYSGEN MAP CONFBC86LSGO -SYSGEN CONF=CONFBC86C,HIST=CONFBC86H &

-PT SLIBPATCH2 & -SITE BC86 & -REMOTE BC05 065:005 009027FC16F2*❑

Libraries and files used for sysgen

SYS.OUT SYS.DSACONF SYS.DSACORE SYS.DSASLIB SYS.DSABLIB

memory imagescenario

source config

CHXMOD

PATCH1

PATCH2

SYSGEN

SYSGEN1

YTABLE

bound units

FECM

MainWay-LE

DPS7000/XTA

scenario listing

report listing

STSVR FECM <node> SYSGEN

FECM Functions

47 A2 94UC 4-49

Cross reference of GCOS 7 Files to Source Configuration Commands

Source Configuration Commands

GCOS FileMainWay 2600LE commandLibrary Subfile

LANG …PATCH SLIBPATCH1END –SAVE COREsubfile

SYS.DSABLIBSYS.DSASLIBSYS.DSACORE

DLCKW, DLCMSFor DLCMSGPATCH1user-defined

GO order in scenario

GCOS FileGO orderLibrary Subfile

GO –SYSGEN CONF=file1,HIST=file2 –PT file3

SYS.DSACONFSYS.DSASLIB

user-definedPATCH file

Note that FECM prefixes all GCOS subfile names - in SYS.DSASLIB,SYS.DSABLIB and SYS.DSACORE libraries - with the software version numberunless otherwise specified.

A user-defined subfile can take any name.


4-50 47 A2 94UC

4.5.3 Front-end Processor: Load

The LOAD function specifies that the DNS, CNS 7 or DNS-E image is to beloaded in the Datanet, CNP 7 or MainWay 2600LE memory, respectively.

4.5.3.1 Datanet Load


The LOAD function is described in the scenario by LOAD followed by GO. Thesyntax is:

LOAD COREsubfile [MAP file2]

where subfile is the file containing the memory image in SYS.DSACORE to beloaded in the Datanet. The memory image was previously created at SYSGEN.

Since FECM prefixes the name of the subfile by the software version number if itexists, the user need not specify this number.

MAP specifies that the lists produced during LOAD are written to a file.

file2 defines the file in which the lists are produced. It mustbe of the format CONFsubfile where:

− CONF corresponds to SYS.DSACONF

− subfile corresponds to the name of the subfile inwhich the lists are produced. No prefix is added tothis subfile name.

GO must then follow LOAD in the scenario.

GO [ { { -P2 | -PAT2 } file } ] [ { } ] -NL [ { { -NP | -NOPAT2 } } ]

[ dns-parameters ]

-NP specifies that no patches are applied to the memory image.

-P2 specifies that patches for updating the generated DNS memory image are to beapplied.

FECM Functions

47 A2 94UC 4-51

file is identified by the keyword SLIBPATCH2. Thismeans that the subfile is PATCH2 of SYS.DSASLIB.FECM automatically prefixes the file-name by thesoftware version number, if it exists. The user neednot specify this number.

dns-parameters are specific parameters processed by the Datanet.

-NL only service and error messages are to appear.

DN7500 versions of the Datanet which are configured with a local disk and whichrun on DNS V4U1 can perform a local LOAD instead of going through theDPS 7000. To do this, the LOAD order in the SCENARIO must specify:

LOAD subfile -LC

where

• subfile is the name of the file containing the memory image to be loaded intothe Datanet

• and -LC specifies that the file is located on the local disk.

The GO order must then follow the LOAD order in the scenario. The file can beeither on the local disk or on the DPS 7000 if it is prefixed with H:. The rulesdefined above then apply to the file.

Automatic Mode for Datanet Management

When the automatic mode has been validated (either explicitly in the STSVRcommand, or implicitly), the FEPS occurrence is started up synchronously after theDatanet is loaded to provide the transport service. If the Datanet fails, twosuccessive events occur:

• its associated FEPS occurrence, if active, terminates

• then FECM is automatically started up to load the Datanet.

The scenario specified for AUTO mode is invoked to perform this loading. Onceloading is completed, transport is again started up. Refer to paragraph Datanet in4.2 for a complete description of the automatic mode processing.


4-52 47 A2 94UC


S: STSVR FECM BP22 ACTION=LOAD CA20 ADM_BP22 LAUNCHED BY OPERATOR COMMAND 12.16 X30 STARTED FECM OPERATOR S CA21 ADM_BP22 STARTED FE01 BP22 LOAD STARTED FROM SCENARIO STD_SCEN VERSION C1U4 FE04 BP22 **** INSERT ZONE 03435/ 02504 ***** FE04 BP22 ***** INSERT # 011/127 ***** FE04 BP22 DNS_DATE: 1987/10/15 15:47:01 FE04 BP22 *** LOAD TIME : 1987/11/4 12:17:08 FE04 BP22 LOAD COMPLETED CA21 ADM_BP22 COMPLETED 12.17 X30.1 COMPLETED FECM OPERATOR S❑

EXAMPLE OF SCENARIO

10 NODE BP22 LOAD 20 * 30 --->SCEN LOAD 40 --->LOAD COREBP22I 50 --->GO 60 --->* 70 SCEN DUMP 80 DUMP DUMPBP22 90 *100 SCEN SYSGEN110 LOAD BLIBIMAEXC120 GO CONFBP22C -PAT2 SLIBPATCH2 -SVPAT2 COREBP22I &130 -PATCH SLIBPATCH0 -MOD 500 -SYMP 5000140 *❑

FECM Functions

47 A2 94UC 4-53

4.5.3.2 CNP 7 Load


The LOAD function is described in the scenario by LOAD followed by GO. Thesyntax is:

LOAD COREsubfile [ MAP file2]

subfile is the file containing the memory image onSYS.DSACORE to be loaded in the CNP 7. Thememory image was previously created at SYSGEN.

subfile1 is the second memory image created at SYSGEN andloaded automatically with subfile by the CNP 7.

MAP specifies that the lists produced during LOAD are written to a file.

file2 defines the file in which the lists are produced. It mustbe of the format CONFsubfile where:

− CONF corresponds to SYS.DSACONF

− subfile corresponds to the name of the subfile inwhich the lists are produced. This subfile name isnot prefixed.


[ { -P2 patch2-name-list } ]GO [ { } ] -NL [ { -NP } ]

-NP specifies that no patches are to be applied to the memory image

-P2 specifies that the patches for updating the generated CNS 7 memory image areto be applied from file.

patch2-name-list lists all the patch2 file(s) to be applied. If no file isspecified, the default file SLIBPATCH2 is used.FECM prefixes the file-name with the softwareversion.


4-54 47 A2 94UC

-NL only service and error messages are to appear.

NOTE:In the case of TOL (test-online), the arguments for -P2 are as follows:-P2 SLIBPATCH2 SLIBPATCH3

Automatic Mode for CNP 7 Management

After TNS is started through the STSVR command, FECM is automatically startedon the default scenario.


S: STSVR FECM BL02 ACTION=LOAD CA02 ADM BL02 LAUNCHED BY OPERATOR COMMAND 17.04 X118 STARTED FECM OPERATOR S CA21 ADM_BL02 STARTED FE01 BL02 LOAD STARTED FROM SCENARIO STD_SCEN VERSION A0U2 FE04 BL02 FE04 BL02 ***CNS *RLS:A0U2 *PTS:0000/PTL:0000 *SYS:BL02C*GEN:1987/10/15 16:52:35*** FE04 BL02 FE04 BL02 Initial patches are installed on DEA 1 : 0 error(s) FE04 BL02 FE04 BL02 Loading of DEA 1 , CTRL , is completed ! FE04 BL02 FE04 BL02 Initial patches are installed on DEA 2 : 0 error(s) FE04 BL02 FE04 BL02 Loading of DEA 2 , CT02 , is completed ! FE04 BL02 FE04 BL02 *** LOAD TIME 1987/11/4 17:07:32 *** FE02 BL02 LOAD COMPLETED CA21 ADM_BL02 COMPLETED 17.09 X118.1 COMPLETED FECM OPERATOR S❑

FECM Functions

47 A2 94UC 4-55

EXAMPLE OF SCENARIO

10 NODE BL02 RELOAD -VERSION AOU2 20 * 30 --->SCEN LOAD 40 --->LOAD COREBL02I 50 --->GO -P2 SLIBPATCH2 60 --->* 70 SCEN RELOAD 80 DUMP DUMPBL02 90 LOAD COREBL02I100 GO -P2 SLIBPATCH2 -NL110 *120 SCEN DUMP130 DUMP DUMPBL02140 *150 SCEN SYSGEN160 LOAD BLIBSYSGEN170 GO -NL -PAT2 SLIBPATCH2 -SITE BL02 60:02 080038503C02 &180 -REMOTE BL17 60:23 080038503C17 &190 -SYSGEN "CONF=CONFBL02C,HIST=CONFBL02L"200 *❑


4-56 47 A2 94UC

FE C M

memory image

<node>

FRONT_END PROCESSOR


SYS.OUT SYS.DSACONF SYS.DSACORE

scenarioscenario listpatch list

PATCH2

SYS.DSABLIB

LOAD with PATCH2

FECM Functions

47 A2 94UC 4-57

4.5.3.3 MainWay 2600LE Load

The LOAD function specifies that the MainWay 2600LE memory image is to beloaded in the MainWay 2600LE.

Scenario description

The LOAD function is described in the scenario by LOAD followed by GO.

The syntax is:

LOAD COREfile1 [ MAP file2]

file1 defines the file containing the memory image inSYS.DSACORE library, to be loaded in the MainWay2600LE. The memory image was previously created atSYSGEN time.

The second memory image named subfile1 created atSYSGEN time is automatically loaded with subfile bythe MainWay 2600LE.

MAP specifies that the lists produced during application of patches on softwareimage loaded are written to a file.

file2 defines the file, in SYS.DSACONF library, in whichthe lists are produced.This subfile name is not prefixed.


GO [{-PT|-PATCH} SLIBfile1 [SLIBfile2 […]] [-NL] | {-NP|-NPATCH}} [-SITE name1] [-REMOTE name2 scid ethaddress]

-PT option is only necessary if PATCH2 file was not previously applied duringgeneration of memory image (refer to source configuration command namedPATCH), and/or if a PATCH3 member must be applied on created image for apatch test purpose. If all patchs are applied, -NP option will be used.

file1 file2 define the patch files, in SYS.DSACONF library, forupdating the generated MainWay 2600LE memoryimage.FECM prefixes the patch file names with the softwareversion.

-NL (No List): The patch application report will not beprinted as the PATCH2 and/or PATCH3 patchs areapplied during a system Load.


4-58 47 A2 94UC

-NP or -NPATCH (No Patch): No patch file will be applied duringsystem load.

-SITE option is only necessary for substitution, if MainWay 2600LE name isreferred as "$FEP" in source configuration file.

name1 name of the MainWay 2600LE to be managed, asdeclared in the RSYS directive of NETGEN.

-REMOTE option is only necessary for substitution, if DPS7000/XTA name usedfor loading is referred as "$SP" in source configuration file.

name2 name of the local DPS 7000/XTA system, as declaredin the LSYS directive of NETGEN.

scid Session Control Identifier of the local DPS 7000/XTAsystem, as declared in the LSC directive of NETGEN.

ethaddress MAC address of one of the OCS server localcontrollers of the DPS 7000/XTA, as declared in theLCT directive of NETGEN.


S: STSVR FECM BC86 LOAD 15.29 X126 STARTED FECM OPERATOR S CA20 ADM_BC86 LAUNCHED BY OPERATOR COMMAND CA21 ADM_BC86 STARTED FE01 BC86 LOAD STARTED FROM SCENARIO STD_SCEN VERSION V3U4 FE04 BC86 SYSER: rrst 01/09/04 15:29 AD:60106F28 CPU: 8IMA:BLIBSYSGEN VS:V3U4 FE04 BC86 FE04 BC86 *DNS-E V3U4.300 P1.002 P2.008 P3.000*IMA:COREBC862001/09/04 13:37* FE04 BC86 FE04 BC86 FE04 BC86 *** LOAD TIME 2001/09/04 15:29:50 *** FE02 BC86 LOAD COMPLETED CA21 ADM_BC86 COMPLETED 15.29 X126.1 COMPLETED FECM OPERATOR S❑

FECM Functions

47 A2 94UC 4-59

EXAMPLE OF SCENARIO

NODE BC86 LOAD -VERSION V3U4*SCEN LOADLOAD COREBC86 MAP CONFBC86LCGO -PT SLIBPATCH3 & -SITE BC86 & -REMOTE BC05 065:005 009027FC16F2*

❑

Libraries and files used for load

SYS.OUT SYS.DSACONF SYS.DSACORE SYS.DSASLIB

memory imagescenarioPATCH1

PATCH2

FECM

MainWay-LE

DPS7000/XTA

scenario listing

report listing

STSVR FECM <node> LOAD


4-60 47 A2 94UC

4.5.4 Front-end Processor Dump

The DUMP function specifies that the Datanet, the CNP 7 or the MainWay2600LE is forced to take a dump. As soon as the FEP or the MainWay 2600LEreceives the DUMP command, its CPU is stopped before its core image is dumped.

4.5.4.1 Datanet or CNP7 Dump


The DUMP function is described in the scenario by the DUMP order of thefollowing syntax:

DUMP [ DUMPsubfile ]

where subfile defines the file in SYS.DSADUMP, in which the dump of the DNSor CNS 7 memory image is to be written.

Two versions of dump for the same subfile are kept; they are version1 andversion2, respectively subfile1 and subfile2.

When writing a new dump for a given subfile, the oldest existing subfile is erasedbefore the new dump is written.

In order to manage the various dump versions of a given FEP, it is recommended tospecify subfile as the node name. If subfile is not specified, the default name isDUMPnode.

The size of the SYS.DSADUMP library should be large enough to accommodatetwo dumps for each front-end processor configured.

DN7500 versions of the Datanet which are configured with a local disk and whichrun on DNS V4U1 can take a local dump instead of going through the DPS 7000.To do this, the DUMP order in the SCENARIO must specify:

DUMP subfile -LC

where

• subfile is the name of the file to contain the dump• and -LC specifies that the file is located on the local disk.

If -LC is specified for Datanet versions that do not support the local disk, theDUMP order will result in:

• a dump being taken in the SYS.DSADUMP library in a file node-name, wherenode-name is the name of the Datanet

• and the following message appearing on the console and in the output listing:

FECM Functions

47 A2 94UC 4-61

FE21 sitenm DNS VERSION NOT AVAILABLE FOR LOCAL DUMP: version

DNS and CNS 7 dumps can be edited by the CPDS utility. See the CPDS User'sGuide.

EXAMPLE 1:

Successful dump of Datanet BP22 to member BP221 in SYS.DSADUMP library.

Execution

S: STSVR FECM BP22 ACTION=DUMP CA20 ADM_BP22 LAUNCHED BY OPERATOR COMMAND 12.36 X39 STARTED FECM OPERATOR S CA21 ADM_BP22 STARTED FE01 BP22 DUMP STARTED FROM SCENARIO STD_SCEN VERSION C1U4 FE17 BP22 DUMP BEGINS IN SUBFILE: BP221 FE18 BP22 DUMP AVAILABLE IN SUBFILE: BP221 FE02 BP22 DUMP COMPLETED CA21 ADM_BP22 COMPLETED 12.37 X39.1 COMPLETED FECM OPERATOR S

Scenario

10 NODE BP22 LOAD 20 * 30 SCEN LOAD 40 LOAD COREBP22I 50 GO 60 * 70 --->SCEN DUMP 80 --->DUMP DUMPBP22 90 --->*100 SCEN SYSGEN110 LOAD BLIBIMAEXC120 GO CONFBP22C -PAT2 SLIBPATCH2 -SVPAT2 COREBP22I &130 -PATCH SLIBPATCH0 -MOD 500 -SYMB 5000140 *❑


4-62 47 A2 94UC

EXAMPLE 2:

Unsuccessful dump to member BP222 since SYS.DSADUMP library is not largeenough.

Execution

S: STSVR FECM BP22 ACTION=DUMP CA20 ADM_BP22 LAUNCHED BY OPERATOR COMMAND 12.36 X40 STARTED FROM OPERATOR S CA21 ADM_BP22 STARTED FE01 BP22 DUMP STARTED FROM SCENARIO STD_SCEN VERSION C1U4 FE17 BP22 DUMP BEGINS IN SUBFILE: BP222 FE18 BP22 DUMP FILE: SYS.DSADUMP IS FULL FE02 BP22 DUMP ABNORMALLY TERMINATED CA21 ADM_BP22 COMPLETED 12.37 X40.1 ABORTED FECM OPERATOR S SEV3

Scenario

10 NODE BP22 LOAD 20 * 30 SCEN LOAD 40 LOAD COREBP22I 50 GO 60 * 70 --->SCEN DUMP 80 --->DUMP DUMPBP22 90 --->*100 SCEN SYSGEN110 LOAD BLIBIMAEXC120 GO CONFBP22C -PAT2 SLIBPATCH2 -SVPAT2 COREBP22I &130 -PATCH SLIBPATCH0 -MOD 500 -SYMB 5000140 *❑

FECM Functions

47 A2 94UC 4-63

<node>

FRONT_END PROCESSOR


SYS.OUT SYS.DSACONF

scenarioscenario list subfile1

subfile2

command

SYS.DSADUMP

FECM

DUMP


4-64 47 A2 94UC

4.5.4.2 MainWay 2600LE Dump

At the end of dump phases, the MainWay 2600LE sends a RIM to be automaticallyreloaded.

Scenario description

The DUMP function is described in the scenario by the DUMP order of thefollowing syntax:

DUMP [ DUMPsubfile ]

subfile defines the file in SYS.DSADUMP, in which the dumpof the MainWay 2600LE memory image is to bewritten.

Two versions of dump for the same subfile are kept; they are version1 andversion2, respectively subfile1 and subfile2.

When writing a new dump for a given subfile, the oldest existing subfile is erasedbefore the new dump is written.

In order to manage the various dump versions of a given MainWay 2600LE, it isrecommended to specify subfile as the node name.If subfile is not specified, the default name is DUMPnode.

The size of the SYS.DSADUMP library should be large enough to accommodatetwo dumps for the MainWay 2600LE.


S: STSVR FECM BC86 DUMP 10.54 X240 STARTED FECM SIOUX S CA20 ADM_BC86 LAUNCHED BY OPERATOR COMMAND CA21 ADM_BC86 STARTED FE01 BC86 DUMP STARTED FROM SCENARIO STD_SCEN VERSION V3U4 FE04 BC86 SYSER: rrst 01/09/20 10:54 AD:60106F28 CPU: 8IMA: COREBC86 VS: V3U4 FE17 BC86 DUMP BEGINS IN SUBFILE: BC862 FE18 BC86 DUMP AVAILABLE IN SUBFILE: BC862 FE02 BC86 DUMP COMPLETED CA21 ADM_BC86 COMPLETED 11.05 X240.1 COMPLETED FECM SIOUX S❑

FECM Functions

47 A2 94UC 4-65

At the end of dump phases, a RIM is sent by the MainWay 2600LE.

If the RIM is accepted by TNS server, the default action in standard scenario(STD_SCEN) is executed (e.g. LOAD):

CA20 ADM_BC86 LAUNCHED BY SERVER: TNS 11.05 X242 STARTED FECM OPERATOR S CA21 ADM_BC86 STARTED FE01 BC86 LOAD STARTED FROM SCENARIO STD_SCEN VERSION V3U4 FE04 BC86 SYSER: rrst 01/09/20 10:54 AD:60106F28 CPU: 8IMA: COREBC86 VS: V3U4 FE04 BC86 FE04 BC86 *DNS-E V3U4.300 P1.002 P2.008 P3.000*IMA:COREBC862001/09/18 13:15* FE04 BC86 FE04 BC86 FE04 BC86 *** LOAD TIME 2001/09/20 11:06:16 *** FE02 BC86 LOAD COMPLETED CA21 ADM_BC86 COMPLETED 11.06 X242.1 COMPLETED FECM OPERATOR S❑

EXAMPLE OF SCENARIO

NODE BC86 LOAD -VERSION V3U4*SCEN LOADLOAD COREBC86 MAP CONFBC86LCGO -PT SLIBPATCH3 & -SITE BC86 & -REMOTE BC05 065:005 009027FC16F2*SCEN DUMPDUMP DUMPBC86*❑


4-66 47 A2 94UC

Libraries and files used for dump

SYS.OUT SYS.DSACONF SYS.DSADUMP

scenario subfile1

subfile2

FECM

MainWay-LE

DPS7000/XTA

scenario listing

report listing

STSVR FECM <node> DUMP

FECM Functions

47 A2 94UC 4-67

4.5.5 Controller Functions

The administrative functions needed to manage an ISL LCT are automaticallymanaged by GCOS without any user intervention.

Administrative controller functions are reserved for the Service Center and areactivated through the STSVR command.

The functions to be performed are defined in a scenario for managing the Datanetor CNP 7. The only difference is that the NODE order is replaced by a CT order.The result is described for each function.

4.5.5.1 LOAD Function

The LOAD function specifies that the LNRA memory image is to be loaded in theRAM of the LNA board of the SPA or MPC or LNM.

LOAD must be followed by GO with no accompanying parameters.

4.5.5.2 DUMP Function

The DUMP function specifies that the ISL controller is forced to take a dump.

See paragraph 4.5.4 for a complete description of the DUMP order.


4-68 47 A2 94UC

4.6 DSA Administrative Storage Facility

4.6.1 Introduction

The Administrative Storage Facility enables the system:

• to receive incoming administrative sessions from correspondents on the standard$NASF mailbox

• and to transmit information between administrative correspondents of thenetwork.

4.6.2 ASF Handler Startup and Execution

The ASF facility is enabled by GCOS once the communications session is startedup through the STSVR command.

The ASF handler is packaged with the FECM server and is started up each time anetwork connection is established towards the $NASF mailbox.

One ASF handler job is started at the first connection request to the $NASFmailbox from a remote correspondent. Further connection requests from a remoteAC already connected to the $NASF mailbox will open up new sessions with theASF handler which is executing for that remote AC.

There can potentially be several ASF handlers concurrently active since there canbe as many different remote systems as concurrent administrative sessions openedtowards the $NASF mailbox.

Since the remote AC can open up to 10 simultaneous sessions on the same ASFhandler, the AC can access up to 10 files simultaneously. Each session can accessany of these files consecutively.

FECM Functions

47 A2 94UC 4-69

4.6.3 Files Supported

The files supported by ASF are:

• SYS.DSAxxxx libraries• SYS.OUT• one temporary library (TEMP.BINLIB)

The maximum record length depends on the file accessed.

Files are transmitted sequentially record by record, in input or output mode, namely

• SYS.OUT in WRITE mode (output from the ASF handler)

• any subfile belonging to the libraries named SYS.DSAxxxx in either WRITE orREAD mode

• any subfile in the temporary library which must first be created in WRITE modebefore READ.

This library is available only during the job execution.

4.6.4 Version Number

As the connection request is initiated by an administrative correspondent, it is theAC's responsibility to provide the software version number of the DNS or CNS 7release as is applicable.

For the CNP 7, each time a file is opened, CNS 7 systematically sends the softwareversion number.

For the Datanet, however, if no version number is supplied by the AC, ASFprovides a default version to access its subfiles all of which are prefixed by it.

This default version number is found in a way similar to that during Datanetadministration in the following sequence:

• first in the -VERSION parameter of the NODE order corresponding to the FEPin the STD_SCEN scenario of SYS.DSACONF

• then in the VERSION order in the STD_SCEN scenario of SYS.DSACONF

• then in the first record of the TSLIST subfile of the SYS.DSACONF library

• lastly, in the first record of the TSLIST subfile of the SYS.DSASLIB library.


4-70 47 A2 94UC

NADNAD

ASF handlerFECM

ASF handlerFECM

Remote System Remote System

NETWORK

DPS 7000 HOST

SYS.DSAxxxx or SYS.OUT

$NASF

FECM Functions

47 A2 94UC 4-71

4.6.5 Use of the ASF Function

• Online test load of the Datanet or CNP 7 from a library on the DPS 7000.

• Remote LOAD/DUMP/SYSGEN support of the Datanet and/or CNP 7. Forremote load, the Datanet or CNP 7 reads the image and the patches to be applied,then sends output deliveries to files on the DPS 7000. For remote dump, thecore image of the Datanet or CNP 7 is written away. The scenario files used forremote load/dump must be created in subfiles of SYS.DSACONF.

• CNP 7 software generation.

4.6.6 Operator Interface

DNET MB $NASF LONG gives the number of NADs currently connected to the$NASF mailbox. This number corresponds to the number of ASF handlers activeon the DPS 7000.

S: DNET MB $NASF LONG GAMB 14:29:25 --> NAME:$NASF STATE=USED WS:ASFWKS MAX_LC:255 USER_NB:2 COMMAND COMPLETED. 1 OBJECT SELECTED

The message indicates that two NADs are connected to the $NASF handler. Thismeans that there are two active ASF handlers.

Example: Datanet Online Test Loading from a DPS 7000 Library.

This function is supported on the Datanet as from Release DNS C1.

SYS.DSABLIB DPS 7000 HD20 DATANET DN04


4-72 47 A2 94UC

4.6.7 Prerequisites

On the DPS 7000

The SYS.DSABLIB library contains as many subfiles as there are tests to bestarted, namely:

- Asynchronous Lines: .LASY00 . LASY01 . . . . LASYnn- HDLC Lines: . LHDL00 . LHDL01 . . . . LHDLnn- Other Lines

On the Datanet

Configuration of a test-type administrative function.

BLIB$NASFHD20$NADDN04

DPS 7000 name

mailbox name on DPS 7000

TL -MBR -DIRL

Test Library Nameon DPS 7000syntax : [SYS.DSA]BLIB

Datanet name

Datanet local mailbox name

AFT1 TL -MBL

FECM Functions

47 A2 94UC 4-73

4.6.8 Running the Test

Launching LASYnn from the Datanet console tests the line specified in the EX TLcommand.

1. Test Launch on the Datanet Console after connecting to the NOI: ??EX TL LASY00 LN01

The Datanet Administrative Module opens a session on the $NASF mailboxon HD20 to retrieve the corresponding test. The file requested is:

BLIBLASY00

where BLIB is from the AF, and LASY00 is from the EX TL command. Thiswill be interpreted on the DPS 7000 as:

− Library SYS.DSABLIB− Member LASY00

2. An FECM job (ASF handler) is spawned on the DPS 7000 to transfer thecorresponding subfile. Once the subfile is transferred, the job terminates.

NODE=DN04 TIME=:15:52:18:1991:2:28 MW-TEST TL: LASY EXTL ACCEPTEDSOFTWARE COMPATIBILITY

HARDWARE COMPATIBILITY BMLC001B-008 (FW 000C)BMLF 10 18-001ASYNCHRONOUS LINE TEST: NUMBER OF PROG. = 1 : NUMBER OF ROUT. = 2 : ROUT1 =SHORT MESSAGE : ROUT2 = LONG MESSAGE

RULES TO EXECUTE THIS TEST TYPE ADAPTOR 2 108 2118 1. CHOOSE LOOP BACK MODE: A = AUTOMATIC (INTERNAL LOOPBACK) B = BRANCH CABLE (EXTERNAL LOOPBACK) C = COMMUTATION LOCAL OR REMOTE MODEMIF SKEY OPTION = 0001 NO RELEASE CONTROL

NODE=DN04 TIME=15:52:3:1991:3:28 NW_TEST TL: TYPE=1 CODE=20END 0 OF LASY: OK


4-74 47 A2 94UC

4.6.9 Example of Remote Loading

The Datanet functioning as an FEP or neighbor of the DPS 7000 runs on releasesfrom DNS C onwards. The DPS 7000 standard ASF handler fetches and returnsthe following components, namely

• the commands in the scenario files to be executed by the Datanet Loader

• the IMA to load the remote Datanet

• the source configuration, bound-units and patches needed to generate theneighbor

• the IMA generated after SYSGEN or the IMA patched after a load

• the job error report listing errors, if any, delivered when the operation iscomplete.

HD20 DN20 DN04

DPS 7000Host

Datanet Neighbor(FEP or Remote) HDLCPoint-to-point

Site to beLoaded orDumped orGenerated

LoaderSite

Site SupportingASF Functions

The following example is only a part of teleload. For a full description of teleloadprocessing, see DNS NGL Reference Manual.

Before attempting teleload processing, verify with the installation personnel thatthe BPF of the MMPO board is correct and that the switches on this board arecorrectly set.

FECM Functions

47 A2 94UC 4-75

Loader Configuration: Administrative Function TLD (Teleload)

& *************************************************************DN7100 V24DN20C-EOS%5PFEL5ZGB8$TDBB8$#QW3%UC$TIL_8EISLH5#IFBN88& *************************************************************DIR BLIBLKFL SLIBCHXMODTBFL BLIBYTABLEPATCH1 SLIBPATCH1PATCH2 SLIBPATCH2& *************************************************************

& ********************** LOCAL SITE ***************************ND DN20 LOC -ADDR 1:131 . .AF NOI1 NOIPSSW UNCPAF AFAD NADAF AFT1 ASF -LG LG01AF TLLD TLD -TLDND DN04 -NSFND HD20 -LL HDL1 -FILE CONFV24SDN04 -MAIL $NASF -AUT . . .LINK -FOR DEBUGEND -START -SAVE COREV24DN20

Example of Scenario Executed by the Loader Site

This scenario comes from the scenario subfile introduced by anAF ... TLD command on the site supporting ASF functions.

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

+--------+C: PRINT |V24SDN04| +--------+ 10 NODE DN04 B 20 SCEN BLoad 30 LOAD COREVTESTSVPAT2 MAP SYS.OUT 40 GO -NOLIST

Dump 50 SCEN A 60 DUMP DUMPDN04

Sysgen 70 SCEN C 80 LOAD BLIBIMAEXC MAP SYS.OUT 90 GO CONFVTESTDN04 -PATCH SLIBPATCH0 -SVPAT2 COREVTESTSVPAT2❑


4-76 47 A2 94UC

Example of Remote Site to be Loaded and Generated

& ************************************************** DN7100 TEST04C -EOS RJB9DV%QV1ZFW1 IEUKC5*ZM3*%RQJN4RK47RKXB238 & ************************************************** & D I R E C T I V E S & ************************************************** DIR BLIB LKFL SLIBCHXMOD TBFL BLIBYTABLE PATCH1 SLIBPATCH1 PATCH2 SLIBPATCH2 & **************************************************

& *************** LOCAL SITE *************** ND DN04 LOC -ADDR 1:138 . . . AF NOI1 NOI AF AFAD NAD AF AFT1 ASF -LG LG01 AF TLLD TLD -NSFND HD20 -TLDND DN20 -AUT -LL HDL3 -FILE CONFSCEN2TEST . . . LINK -FOR DEBUG END -START -SAVE COREVTESTDN04 ------------- : : : :--------VTESTDN04: Memory image before PATCH : processing : :---VTESTSVPAT2: Memory image after PATCH2 : : processingMEMBERS : : -----CREATED---------MODIFIED-----MOD--TYPEV4U1DN04 : : 10/25/90 10:57 10/25/90 10:57 00 IMAV4U1DN20 : : 10/18/90 10:06 10/18/90 10:06 00 IMAV4U1VTESTDN04<-+ : 10/25/90 09:54 10/25/90 09:54 00 IMAV4U1VTESTSVPAT2<--+ 10/25/90 09:57 10/25/90 09:57 00 IMAV4U1V24DN04 10/24/90 17:36 10/24/90 17:36 00 IMAV4U1V24DN20 10/24/90 07:46 10/24/90 07:46 00 IMA

NUMBER OF MEMBERS: 6❑

47 A2 94UC 5-1

5. OCS Server Functions

5.1 Overview

OCS (Open Communications Subsystem) is a GCOS 7 job (process group). TheOCS job can manage up to 4 Front End servers. Each Front Ends has its ownserver running under OCS. The Front End server is known as a server of OCStype. When the last Front End server has stopped, the OCS job stops as well.

Once the server starts, the scenario is executed. The scenario gives the name(s) ofthe subfile(s) containing the configuration(s). If both OSI/DIWS and IPS are beingconfigured, each one has its own configuration subfile.

When the OCS server starts (STSVR command), it loads the OCS Front Endsoftware (you can specify the version number of the OCS Front End software to beloaded).

According to the hardware, the OCS Front End trafic is send to a FDDI ring or toan high performance Ethernet cable.

5.1.1 OSI/DIWS Administration

The OSI/DIWS stack is administered using the following commands common toall servers:

• DNET• LNET• MDNETThese commands are described in Sections 2 and 3.

The OCS server has an extended set of commands to:

• perform IVMO management: MDIVMO, LSIVMO, DPLKIVMO, ATTIVMO,DPIVMO, and CRIVMO commands.

• launch an OCS Front End incremental configuration: UPGRADECF command.• get extended attributes of an OCS Front End Transport connection objects:

XGATC command.These commands are described in paragraph 5.8.


5-2 47 A2 94UC

5.1.2 IPS Administration

On DPS 7000 based on Bull processor, the OCS server provides the capability to:

• administer its own IPS stack by submitting basic TCP/IP administrativecommands such as IFCONFIG, ROUTE, ARP, ...

• administer its own TCP/IP stacks or remote TCP/IP stacks by using the SNMPmanager set of commands.

The IPS stack of an OCS server may be:

• administered locally by its own OCS server through the basic TCP/IPadministrative commands such as IFCONFIG, ROUTE, ARP, ...

• administered by an SNMP manager (remote or its own) via the SNMP agent ofthe OCS server.

5.1.2.1 Basic TCP/IP Administrative Commands

There are 7 commands described later in this chapter:

• ARP• ENDNETST• ENDPING• IFCONFIG• NETSTAT• PING• ROUTE

These commands can only be submitted to the local TCP/IP stack(s).

5.1.2.2 SNMP Agent

(On DPS 7000 based on Bull processor only).

Attached to each OCS server running a TCP/IP stack, there is an SNMP agentwhich is compliant with the SNMP-V1 protocol. It allows the management ofadministrative objects related to the TCP/IP stack, FDDI management, and FCPkernel administrative management. It replies to local or remote requests.

OCS Server Functions

47 A2 94UC 5-3

5.1.2.3 SNMP Manager

(On DPS 7000 based on Bull processor only).

This is available when an OCS server runs a TCP/IP stack. It provides a set ofcommands allowing individual or grouped object management. It sends requests tolocal or remote SNMP agents. See paragraph 5.7.

5.2 Startup and Automatic Mode

5.2.1 Starting OCS

An OCS server is started using a STSVR command. The OCS job is started whenthe first OCS server is started. This STSVR command is described in Section 3.

Unless you specify AUTO = NO or REPEAT = 0 in the STSVR or MDTSVRcommand, OCS server restart in automatic mode. Automatic mode means thisOCS server will restart automatically after an abort. Once started in automaticmode, OCS server remains in automatic mode until a TTSVR command isexecuted or until the value of REPEAT is reached. In STSVR the parameter"ACTION" gives the name of the action to be performed in scenario at the firstlaunching and the parameter "AUTO" gives the action to be performed at eachsubsequent automatic restart.

At OCS server start or re-start, the following processes are performed:

1. DUMP and/or LOAD orders are executed in accordance with the appropriateaction in scenario (default scenario subfile is STD_SCEN), enclosed in therelevant NODE order.

2. OCS Front End stacks are configured using the configuration subfiles (andsecondary subfiles).

3. If at least one transport level is configured successfully (no fatal error), theassociated communication services are activated.


5-4 47 A2 94UC

5.2.2 Starting an Incremental Configuration

5.2.2.1 Automatic launch

During the start of the OCS server, at the end of the successful analysis of the mainOSI/DIWS configuration subfile of the OCS Front End, an incrementalconfiguration step is launched.

In that case an incremental configuration subfile is analysed. This subfile islocated in the SYS.DSACONF library and its name is EAxx_ISOCONF_INCR(a fixed name except that EAxx is replaced by the actual OCS Front End name).

The result of the analysis is appended to the EAxx_CONF_RPRT report subfile.

5.2.2.2 Operator launch

The operator can launch an incremental configuration at any time while the OCSserver attached to the OCS Front End is running an OSI/DIWS configuration.

The UPGRADE_FCP_CONFIG operator command is used to submit anincremental configuration to the current OCS Front End configuration. In thatcase, subfile name and library name are freely chosen.

The result of the analysis is appended to the EAxx_CONF_RPRT report subfile(in SYS.DSACONF library).

Submitting two (or more) times the same incremental subfile without change leadsto ignore the second (and next) attempt and a warning message is written in thereport subfile.

5.2.3 Stopping OCS

An OCS server is stopped using a TTSVR command. This command is describedin Section 3.

The OCS job stops when the last OCS server is stopped.


47 A2 94UC 5-5

5.3 Description of Files and Subfiles

5.3.1 SYS.DSABLIB

SYS.DSABLIB is a non-modifiable binary library. It contains the software whichmust be loaded in OCS Front End.


<Nxyy>IMA_DEA (optional) Contains the first memory image whichmust be loaded and executed in the OCS Front End.This subfile contains the memory image which mustbe loaded and executed in the DEA component insteadof the PROM image.

<Nxyy>IMA_DMAT (optional) Contains the second memory image whichmust be loaded and executed in the OCS Front End.This subfile contains the memory image which mustbe loaded and executed in the DMAT componentinstead of the PROM image.

<Version>IMA_PPA (mandatory for Nxyy, optional for Dxyy) Contains thethird memory image which must be loaded andexecuted in the OCS Front End. This subfile containsthe memory image which must be loaded and executedat the transport level. Version is a string in the formNxyy or Dxyy.

5.3.2 SYS.DSACONF

SYS.DSACONF is a modifiable source library. It is empty at system installation.It contains the user's own subfiles necessary for OCS Front End configuration.


ETC_HOSTS Optional. It is the GCOS 7 equivalent to the UNIX/etc/hosts.

ETC_NETWORKS Optional (useful when IPS used). It is the GCOS 7equivalent to the UNIX /etc/networks.

STD_SCEN The default scenario subfile describing administrativefunctions which must be performed when processingthe STSVR command.

EAxx_ISOCONF_INCR Optional subfile. When present, it containsincremental configuration directives automaticallylaunched at OCS server startup.


5-6 47 A2 94UC

subfile_name Optional subfile. The scenario subfile describing theadministrative functions which must be performedwhen this scenario subfile is specified in the STSVRcommand (SCENARIO keyword).

subfile_name Optional subfile for the configuration of OCS FrontEnd OSI stack. This name is derived from the GOorder (see section 5.5.5.).

subfile_name Optional subfile for the configuration of OCS FrontEnd IPS stack. This name is derived from the GOorder (see section 5.5.5.).

<LCT_name>_CONF_RPRTSubfile made of the OCS Front End configurationreport.

<LCT_name>_SNMP_CONFOptional (useful when IPS used) subfile for theconfiguration of SNMP agent. Only with Bullprocessor.

<LCT_name>_SNMP_COMMOptional (useful when IPS used) subfile for theconfiguration of SNMP agent. Only with Bullprocessor.

<LCT_name>_SNMP_TRAPOptional (useful when IPS used) subfile for theconfiguration of SNMP agent. Only with Bullprocessor.

<LCT_name>_SNMP_AUTHOptional (useful when IPS used) subfile for theconfiguration of SNMP agent. Only with Bullprocessor.

TSLNCC contains the name of the default OCS Front Endsoftware version to be used (optional for Nxyy,mandatory for Dxyy).

SMGR_COMMPORT Mandatory subfile for the configuration of the SNMPManager of OCS. Only with Bull processor.

SNMP_MGR_MIB Optional subfile for the SNMP Manager of OCS. Onlywith Bull processor.


47 A2 94UC 5-7

5.3.3 SYS.DSASLIB

SYS.DSASLIB is a modifiable source library. It contains the subfiles created byDIUF.

The following subfiles are mandatory only on DPS 7000 based on Bull processor.


TSLNCC contains the list of installed OCS Front End softwareversions.

NCC_MG_DOCFILES optional subfile (useful when IPS is used) for theSNMP Manager of OCS.

NCC_MG_RFC1213 optional subfile (useful when IPS is used) for theSNMP Manager of OCS.

NCC_MG_RFC1285 optional subfile (useful when IPS is used) for theSNMP Manager of OCS.

NCC_MG_FCP_MIB optional subfile (useful when IPS is used) for theSNMP Manager of OCS.

5.3.4 SYS.DSADUMP

SYS.DSADUMP a binary library. It is empty at system installation. It containsdumps of front end processors including controller. There are two dump subfiletypes:

• one for transport level dump: <LCT name>_PPA• one for adapter dump: <LCT name>_DEA (optional).The dumps of PPA and DEA components are always taken simultaneously. Adump always overwrites the previous one (of the same type of the same OCS FrontEnd).

Both dumps are made by executing a unique DUMP order in the scenario section.


<LCT_name>_PPA Contains the last transport level memory dump.<LCT_name>_DEA Contains the last adapter memory dump. (optional).

5.3.5 SYS.DSATRC_<LCT name>_n

These are sequential files for recording OCS Front End transport level traces.

There are up to 9 (1 <= n <= 9) such files.

These files are created by DIUF.


5-8 47 A2 94UC

5.3.6 SYS.DSATRCIDX_<LCT name>

This is a sequential file used for OCS Front End trace management.

This file is created by the OCS server.

5.3.7 SYS.DSATRCIDT_<Version>

This is an indexed sequential file used for OCS Front End trace management.

This file is delivered in the OCS Front End software package (via DIUF). It canalso be delivered, in SYS.HSLLIB, by GCOS 7 software package.

5.3.8 Subfiles Used for IPS

On DPS 7000 based on Bull processor only.

The System Subfiles used for IPS Administration are the same as those used forconfiguration (see the manual Network Generation) except the IPS configurationsubfile and the ARPCO_name subfiles.

There is an additional administrative ARP subfile type which can be referred to bythe ARP -f command described below. This subfile contains a list of ARP entrycreation commands (which can be common to several OCS Front Ends).

The name of such a subfile is ARPAD_name,

where:

ARPAD_ is a mandatory string used as a prefix.

name is any string that can be chosen to complete the subfilename.

Structure of the ARPAD Subfile

This subfile is in the library SYS.DSACONF.

The subfile contains a list of ARP commands. These commands are exactlystructured as the ARP -s described below except that the ARP command name andthe -s option are omitted in each command line. Command lines are separatedfrom each other by means of the new line character.


47 A2 94UC 5-9

5.4 Description of OCS Front End Scenarios

A scenario subfile defines the administrative functions for one or several front endprocessors including controllers. Each NODE order describes one FEP and isunique to that FEP. If several NODE orders have the same name, only the firstNODE order will be taken into consideration.

EXAMPLE OF STRUCTURE

NODE FEP1 :administrative orders for FEP1 : :NODE FEP2 : :administrative orders for FEP2 : :NODE FEP3 :❑

When the front-end processor is a OCS one, the name of the NODE order (FEP1,FEP2, FEP3, ...) is the one given to NAME parameter in the LCT directive (NG).

The part of the scenario defined by the NODE order contains a set SCEN orders. Aset of administrative orders is associated with each SCEN order.

EXAMPLE: (OCS controller name = EA01)

NODE EA01

SCEN START :administrative orders for start :

SCEN RESTART :administrative orders for restart after an abort :SCEN DUMP :administrative order for dump :❑


5-10 47 A2 94UC

The name of the SCEN order (for instance START, RESTART or DUMP)corresponds to the argument parameter specified for the ACTION parameter of theSTSVR command.

The administrative orders are:

DUMP to dump the OCS Front End elements for debuggingLOAD to check the executable images related to this OCS

Front End (without loading)GO to load and start the OCS Front End software images

File and Subfile Names

All the subfiles names specified in the orders must be interpreted in the GCOS 7environment as follows: <aaaa><subfile name>

The first four characters must be prefixed by SYS.DSA to form a GCOS 7 libraryname.

The only authorized <aaaa> values are:

BLIBCONF

So are the equivalent references:

BLIB references the file SYS.DSABLIB

CONF references the file SYS.DSACONF

The other characters of the subfile name give the name of the member of thelibrary.

EXAMPLE:

The CONFNCC1_OSICONF value of OSI keyword in the order:

"GO -OSI CONFNCC1_OSICONF"

is interpreted by GCOS 7 as:

• library SYS.DSACONF;

• subfile in this library being NCC1_OSICONF.

❑


47 A2 94UC 5-11

OCS Front End Software Version

The software version is a 4 character string in the form Nxyy or Dxyy with:

N or D according to OCS Front End software type

x: an alphanumeric character identifying the software version [0..9 A..Z]

yy: two decimal character identifying the software revision

For a given OCS server, the same version number applies simultaneously to thefollowing 4 entities:

• DEA software image (optional)

• DMAT software image(optional)

• PPA software image (transport level)

• TRACE_IDT file

However, different OCS servers on the same machine may simultaneously rundifferent version numbers (each one).

Specifying the Software Version

The OCS Front End software version to be used can be given at first level inSTSVR operator command through VERSION keyword.

When omitted in the STSVR command, the version to be used can be given via theVERSION keyword of the NODE order in the scenario subfile. This ismeaningless if STSVR VERSION keyword has been specified.

When omitted in STSVR command or NODE order, the OCS Front End softwareversion to be used is the first one read in the TSLNCC member of SYS.DSACONFlibrary. This member is mandatory for Dxyy versions.

For Nxyy only, when ommited in the STSVR command or NODE order and whenthe optional TSLNCC subfile is not created, the version defined in the first recordof the TSLNCC subfile in the SYS.DSASLIB library becomes the OCS Front Endlast default version to be used.

Setting of the Default Software Version by Customer

The TSLNCC subfile of SYS.DSACONF contains the default value of the OCSFront End software version to be used when an explicit version is not given in theSTSVR command or NODE order.

You must create this subfile for Dxyy versions. It is optional for Nxyy versions.The only first record is used. This record must only contain a "Nxyy" or "Dxyy" 4characters string.


5-12 47 A2 94UC

List of Software Versions

The TSLNCC subfile of SYS.DSASLIB is created by DIUF utility at OCS FrontEnd subdomain installation. This subfile contains a list of the earlier OCS FrontEnd software versions which have been installed on the host.

When a new version is installed, DIUF appends it after the first record whichcontains the current last default version.

Each record contains a character string of the form "Nxyy" or "Dxyy". The versioncontained in the first record will be the last default version.

If the VERSION keyword is in the STSVR operator command or NODE scenarioorder or if the first record of the optional TLSNCC subfile in the SYS.DSACONFlibrary gives an explicit Nxyy version name to be loaded, the presence of this Nxyyname in a record of the TLSNCC subfile in the SYS.DSASLIB library is alwayschecked.


47 A2 94UC 5-13

5.5 Orders for OCS Scenarios

5.5.1 NODE Order

Purpose

Starts the description of the administrative orders relating to the <name> FEP. Itcan also define a default action and a default OCS Front End software version forthis FEP.

Syntax

NODE <name>

[<action>]

[-VERSION <version>]

Parameter Descriptions

<name> Name of OCS controller. It is the name given in theLCT directive. It must be of the EAnn format.

<action> Name of the default action defined by the SCEN orderwhich must be used when the ACTION parameter isnot specified in the STSVR command.If this name is not specified, the action defined by thefirst SCEN order is used.It must not exceed 8 characters.

<version> Default version identification of OCS Front Endsoftware to be used when the VERSION parameter isnot specified in STSVR command (see paragraph3.10).


5-14 47 A2 94UC

5.5.2 SCEN Order

NOTE:The keyword "SCEN" has been kept for historical reasons. In the followingsections, to clarify matters, the word "Action" is used instead.

Purpose

This order corresponds to the ACTION parameter of the STSVR command. Itdefines one action instance, in the NODE order, in the scenario subfile, combiningthe following administrative orders. These action administrative orders start fromjust after this SCEN order and continue up to the next SCEN or NODE order (orthe end of the subfile). These action administrative orders can only be "DUMP"and / or "LOAD" followed by "GO" orders.

Syntax

SCEN <action-name>

Parameter

<action-name> Name of the action defined by the followingadministrative orders.This name corresponds to the name specified in theACTION parameter of the STSVR command. It mustnot exceed 8 characters.


47 A2 94UC 5-15

5.5.3 DUMP Order

Purpose

Part of an action which specifies that the OCS Front End memories dumps must betaken and saved.

The memories of PPA and DEA in some cases are dumped in the SYS.DSADUMPlibrary with the respective names:

<LCT name>_DEA

<LCT name>_PPA

Only one such subfile is created by the related server per OCS Front End. Itoverrides the previous ones.

When used, the DUMP order must be the first order of the action.

The DUMP order may only be followed by LOAD and GO orders (in order torestart the OCS Front End controller); there must be no more orders in this action(SCEN) paragraph.

Syntax

DUMP

Parameters

None.


5-16 47 A2 94UC

5.5.4 LOAD Order

Purpose

Part of an action which specifies that the OCS Front End software must be verified(before loading).

Three software components can be loaded into the OCS Front End from theSYS.DSABLIB with respectively the subfile names:

• <version>IMA_PPA (contains the PPA memory image)

• <version>IMA_DEA (contains the DEA memory image)

• <version>IMA_DMAT (contains the DMAT memory image)

<version> specified by (refer to section 5.4.): VERSION keyword of the STSVRcommand, or by default byVERSION keyword of the NODE order in the scenario,or by default bythe only record of the optional subfile TSLNCC in theSYS.DSACONF library, or by default bythe first record of the mandatory TSLNCCsubfile in the SYS.DSASLIB.

For OCS, the LOAD order must always be followed by a GO order.

Syntax

LOAD

Parameters

None.


47 A2 94UC 5-17

5.5.5 GO Order

Purpose

Part of an ACTION that load and activates the OCS Front End softwarecomponents and defines the subfiles containing the configuration.

Syntax

GO [-OSI <subfile1>] [-IPS <subfile2>]

This order format is special for OCS Front End.

The GO order must always follow the LOAD order.

Parameters

<subfile1> Defines the subfile containing the OCS configurationfor the OSI/DIWS telecommunication stack. Thisparameter must be of the form CONF<subfile> where:CONF corresponds to the SYS.DSACONF library,and <subfile> is the name of the subfile containingthe OCS Front End configuration for the OSI/DIWStelecommunication stack.If <subfile1> is not found or if a fatal error occursabout one of its commands, the OSI/DIWS stack is notconfigured.

<subfile2> Defines the subfile containing the OCS configurationfor the IPS telecommunication stack. This parametermust be of the form CONF<subfile> where:CONF corresponds to the SYS.DSACONF library,and <subfile> is the name of the subfile containing theOCS Front End configuration for the IPStelecommunication stack.If <subfile2> is not found or if a fatal error occursabout one of its commands, the IPS stack is notconfigured.If neither the OSI/DIWS stack nor the IPS stack issuccessfully configured, the STSVR command isterminated.


5-18 47 A2 94UC

EXAMPLE FOR OCS FRONT END SCENARIO

The following example describes the content of the scenario subfile STD_SCENfor a OCS Front End named EA01. It contains three action (or SCEN) labels:

START to start the OCS Front End.

RESTART to take a memory dump of the OCS Front End and(re)start it.

DUMP to take a memory dump of the OCS Front End.

❑

Scenario

NODE EA01

*SCEN RESTARTDUMPLOADGO -OSI CONFEA01_OSI -IPS CONFEA01_IPS

*SCEN STARTLOADGO -OSI CONFEA01_OSI -IPS CONFEA01_IPS

*SCEN DUMPDUMP*


47 A2 94UC 5-19

Execution

STSVR OCS EA01(scenario executed: SCEN RESTART, as the first SCEN, is thedefault for the missing <action> in the NODE order which itself isa default for the missing ACTION keyword in the STSVRcommand)

STSVR OCS EA01 ACTION = START(action executed: SCEN START)

If, once started, the server EA01 is stopped by error (not by a TTSVR command), itis restarted with the RESTART action because:

• AUTO=NO was not specified in the STSVR command.• no action was specified in the AUTO parameter of the STSVR command.• no action is specified in the relevant NODE order.• SCEN RESTART is the first SCEN order after the NODE order corresponding to

EA01.STSVR OCS EA01 ACTION = DUMP AUTO=NO(action executed: SCEN DUMP)

"AUTO=NO" is specified to prevent the EA01 from being automatically restartedafter this STSVR is performed, as for the above execution for ACTION=START


5-20 47 A2 94UC

5.6 IPS Administration Commands

NOTE:The commands described in this section cannot be executed in GCL batch modenor via the statement EXDIR.

5.6.1 ARP Command

Purpose

During administration, this command is used in several ways (depending on theARP command options).

The possibilities offered are:

• Individual creation of an ARP table entry each time an ARP command issubmitted for execution by the operator. Note that the ARP table is limited to255 entries.

• Global creation of entries by means of a subfile containing several ARPcommands.

• Individual deletion of an ARP entry.

• Individual display of an ARP entry.

• Global display of the ARP table.

Syntax (for individual ARP entry creation)

ARP EAnn

-s

host_name | host_ipadd

mac_add

[published]

[trailers]

[temp]


47 A2 94UC 5-21


EAnn a 4 characters string (the LCT name) which identifiesthe OCS Front End that the command applies to.

-s a positional string which indicates that the ARPcommand is being used to create an entry in the ARPtable.

host_name symbolic name of the host. It is used to look for thecorresponding Internet address in the ETC_HOSTSsubfile. This Internet address is equivalent tohost_ipadd described below.Host_name or host_ipadd (whichever one you choose)is a positional parameter. Host name is a string madeof up to 15 printable characters except blank, dot and"#" characters.

host_ipadd host IP address, when directly provided by thecommand.Host IP address is expressed in dot notation as a fourparts address. Host_ipadd or host_name (whicheverone you choose) is a positional parameter.

mac_add physical address which is associated to the host_ipadd.

mac_add is expressed in MAC address notation as asix hexadecimal parts address. It is a positionalargument.

published makes the created ARP information to be known byanother host. This is a SIV parameter with no defaultvalue.

trailers requires the trailers encapsulation (see IFCONFIGcommand). This is a SIV parameter with no defaultvalue.

temp This qualifies the ARP entry to be a temporary entry.If temp is specified and the ARP table becomes full, atemporary entry which has not been used for 6 secondswill be deleted (to free an entry for reuse). Themaximum size of the ARP table is 255 entries. temp isa SIV parameter. If temp is omitted, the entry createdwill be a permanent entry.


5-22 47 A2 94UC

Command Execution

• The command line is analyzed and arguments are checked for validity. If a hostname is provided by the command, an access to the ETC_HOSTS subfile is doneto get the corresponding IP address.

• A record is built according to arguments and options of the command and it issent to the OCS Front End concerned.

• The incoming response is checked and processing resumes if no error isdetected.

• If temp parameter is missing, the entry created will be a permanent entry.

Error Detection

• A syntactical or a semantic error is found during command analysis.

• host_name is not found while scanning the ETC_HOSTS subfile.

• No response is provided within a required time.

• The response indicates an error.

• All errors detected are displayed on the operator console.

Syntax (for global ARP entries creation)

ARP EAnn

-f

INLIB = { SYS.DSACONF | library-name }

MEMBER = member-name

VOLUME = volume-name


47 A2 94UC 5-23


EAnn 4 character string (LCT name) which identifies theOCS Front End the command applies to.

-f positional 2 character string. This identifier indicatesthat the subfile MEMBER is to be accessed to performthe command.

INLIB name of the SL library containing the subfile whichcontains the ARP entry creation commands.

MEMBER name of the subfile which contains the ARP entrycreation commands. The subfile name must start withthe characters ARPAD_ (as a prefix). The subfile iscontained in the SL library specified by INLIB.

VOLUME name of the volume on which the SL library (INLIB)resides.

Command Execution

• ARP commands are taken one by one from the subfile.

• Each time a command is taken from the subfile, a command record is sent to theOCS Front End concerned and the corresponding response is checked.

• If no error is detected, processing continues until all commands are processed.

Error Detection

If an error is detected, it is displayed (on the operator console) and processingstops.

The following are possible errors:

• A command argument is missing.

• The subfile cannot be opened.

• The subfile contains an erroneous command.

• The OCS Front End response indicates an error or there is no response from theOCS Front End.


5-24 47 A2 94UC

Syntax (for individual ARP entry deletion)

ARP EAnn

-d

{ host_name | host_ipadd }


EAnn 4 characters string (LCT name) which identifies theOCS Front End the command applies to.

-d positional 2 character string which indicates that thehost_name entry in the ARP table is to be deleted.

host_name either the symbolic name of the host,

host_ipadd or the IP address of the host.

Command Execution

• The command line is checked.

• If a symbolic name is provided, the ETC_HOSTS subfile (of SYS.DSACONF)is accessed to get the IP address of the host. Otherwise, the IP address is takenfrom the command line.

• A command record is built and sent to the OCS Front End concerned.

• The expected response from the OCS Front End is checked.

Error Detection


Possible errors are:

• A command argument is missing.

• host_name is not found in the ETC_HOSTS subfile (of SYS.DSACONF).

• The response sent by the OCS Front End indicates an error.


47 A2 94UC 5-25

Syntax (for individual display of an ARP entry)

ARP EAnn

host_name


EAnn 4 character string (LCT name) which identifies theOCS Front End that the command applies to.

host_name either the symbolic name of the host or its IP address.

Command Execution

• The command line is checked.

• If a symbolic name is provided, the ETC_HOSTS subfile (of SYS.DSACONF)is accessed to get the IP address of the host. Otherwise, the IP address is takenfrom the command line.

• A command record is built and sent to the OCS Front End concerned.

• The response from the OCS Front End is checked and the items are displayed asfollows: host_name (host_ipadd) at eth_add, where:

− host_name is the symbolic name of the host.

− host_ipadd is the IP address of this host expressed in dot notation.

− eth_add is the Ethernet address of this host expressed in MAC notation.

− and with the fields separated by a blank character.

• An example of a display is:

- bach (129.182.51.40) at 8:0:38:20:e2:2a

Error Detection


Possible errors are:

• host_name is not found in the ETC_HOSTS subfile (of SYS.DSACONF).

• The response sent by the OCS Front End indicates an error.


5-26 47 A2 94UC

Syntax (for global display of ARP table)

ARP EAnn

-a



-a command option which requests that the wholecontents of the ARP table (of the OCS Front Endconcerned) be displayed.

Command Execution

• A command record requesting for the ARP table contents is sent to the OCSFront End.

• The OCS Front End response is analyzed.

• In the OCS Front End response, one ARP entry at a time is displayed. Thedisplay is the same as that described under the "ARP EAnn -a" version of thecommand above (for the "individual display of an ARP entry").

Error Detection

If the response sent by the OCS Front End indicates an error, or if there is noresponse within a required time, an error message is displayed (on the operatorconsole) and processing stops.


47 A2 94UC 5-27

5.6.2 ENDNETST Command

Purpose

During administration, this command terminates the execution of a NETSTATcommand which is currently in progress.

Syntax

ENDNETST EAnn




5-28 47 A2 94UC

5.6.3 ENDPING Command

Purpose

During administration, this command terminates a previous PING command whoseexecution is in progress.

Syntax

ENDPING EAnn



Command Execution

• The PING command currently in progress is terminated.

• A summary is displayed as shown below: ----<host_name> PING Statistics nn packets transmitted, mm packets received, vv% packets lost round-trip (ms) min/avg/max = tt/uu/vv


47 A2 94UC 5-29

5.6.4 IFCONFIG Command

Purpose

During administration, this command is used to:

• To set some network parameters.• To display the state of an interface.

Syntax (to set network parameters)

IFCONFIG EAnn

interface_name

address_family

{ IPADDR | IPDSTAD } = dest_add

[parameters]

The following can appear within [parameters]:

BROADCAST broadcast_addNETMASK mask{arp | noarp}{trailers | notrailers}{down | up}


EAnn a 4 character string (i.e. the LCT name) whichidentifies the OCS Front End that the IFCONFIGcommand applies to.

Interface_name is a 3 characters positional argument which indicatesthe name of the interface the command applies to.

Interface_name must have the following values:

− fd0 for the FDDI or high performance Ethernetinterface.

− lo0 for the loopback interface LOOP.


5-30 47 A2 94UC

address_family is a positional argument identifying the protocol thecommand applies to. Address_family will always berepresented as a string equal to INET.

IPADDR or IPDSTAD is a keyword argument which allows to identify thefollowing statement as being the dest_add definition.

dest_add is the internet address of the OCS Front End interface.It is expressed as a four part internet address.

BROADCAST is a keyword which precedes the broadcast_adddefinition.BROADCAST is not allowed with the lo0 interface.

broadcast_add is an IP address expressed in dot notation. It specifiesthe address to use when it is expected that severalsystems on the network receive the same message. Itis made of the host part of the address set to 1s.

NETMASK is a keyword which precedes the mask definition.

mask is a string of 8 hexadecimal digits. It is used tosubdivide the host part of an internet address intosubnetworks. This is expressed by a bit mask using 1sfor the bits associated with network and subnet numberand 0s for the bits used to address hosts on the subnet.

arp enables the use of the address resolution protocol todynamically map between Internet and Ethernetaddress and to cache the mapping. This is a SIVparameter; arp is the default value.Note that arp is not allowed with the lo0 interface.

noarp disables the address resolution protocol. It is usedwhen a host on the network does not implement theprotocol or if it is expected not to dynamically modifythe cache namely when it is manually configured(see ARP command).This is a SIV parameter.


47 A2 94UC 5-31

trailers requires the use of a link level encapsulation whensending messages to facilitate memory management atreceiving host level. That is to say variable parts inlength of a data header are moved at the end of the datato insure page alignment in a page mapped virtualmemory management.Trailers is a SIV parameter.Trailers is the default value.Trailers is not presently used by OCS Front End. It isreserved for future use. Nevertheless, the trailers valueis not allowed for lo0 interface and generates an error(if used).

notrailers disables the use of the trailers encapsulation.Notrailers is not presently used by OCS Front End. Itis reserved for future use.

{down | up} these parameters are SIV parameters.

down marks an interface down. When an interface is markeddown, the local system will not attempt to transmitmessages through that interface. This action does notautomatically disable the route using this interface.

up marks an interface up. This automatically happenswhen setting the address of the interface. Up can beused after down to re-enable the interface.

Command Execution

• The command line is analyzed. Arguments are checked for type range andvalue.

• If an error is detected, it is noted and processing continues or stops according ofthe error severity (warning or fatal error).

• Else a command record is built according to the arguments and parameters of thecommand and it is sent from the local DPS 7000 host to the OCS Front Endconcerned. Processing waits for the response it is expected to get.

• The response is analyzed and processing resumes or it is aborted depending ofthe result indicated by the response.

• If neither down nor up is specified, the state of the interface remains unchanged.


5-32 47 A2 94UC

Error Detection

• A syntactical or a semantic error is found during command analysis.

• No response occurs within a required time.

• The response indicates the OCS Front End concerned has detected an errorduring execution of the command.

• The response is not the expected one. That is because some items inside theresponse does not correspond to those of the request (request id, OCS Front Endid, function).

• All error messages are displayed on the operator console.

Syntax (to display interface state)

IFCONFIG EAnn

interface_name


EAnn is a string of 4 characters (that is, the LCT name)which identifies the OCS Front End that the commandapplies to.

Interface_name is a mandatory string of 3 characters which indicatesthe interface the command applies. It should have thefollowing form:

− fd0 for the FDDI or high performance Ethernetinterface.

− lo0 for the LOOP interface.

Command Execution

A command record is sent to the OCS Front End concerned and processing waitsfor a response.

The incoming response, which provides the state and values of the interfaceparameters, is analyzed and are displayed as shown below.


47 A2 94UC 5-33

For example:

fd0: flags=101<UP,NOTRAILERS,NOARP>

inet 129.182.51.10 netmask=fffffe00

broadcast 129.182.51.255 ether 08:00:38:20:d0:98

where:

• fd0 is the name of the physical interface.

• 101 is the decimal sum of values assigned to each one of the parameter nameslisted between < > characters. It indicates the "flags" value for this interface.

The parameter names and the items displayed are those previously set by anIFCONFIG command except for the Ethernet address which has been assigned tothe interface at OCS Front End bootloading time.

Error Detection

If an error is detected during command analysis or if the issued response indicatesan error, the error is displayed (on the operator console).


5-34 47 A2 94UC

5.6.5 NETSTAT Command

Purpose

During administration, the NETSTAT command is used to do the following:

• continuously display information about message traffic on a configured interfaceor take a snapshot of the statistics of all the interfaces.

• Display the routing table contents.

Syntax (to display interface statistics)

NETSTAT EAnn

[-n]-i

[INTERFACE = interface_name [,INTERVAL = {0 | interval}]]



-n optional positional 2 character string. When present,network will be represented as a number instead of itscorresponding symbolic name.

-i positional 2 character string which indicates that thecommand is to display interface statistics.

INTERFACE 3 character string which identifies the interface that thecommand applies to, that is either lo0 or fd0 or its IPaddress. When omitted, the command applies to allinterfaces.

INTERVAL a string of up to 9 decimal digits.Statistics of an interface are got every "interval" periodof time in seconds.If interval is omitted, a value of 0 second is assumedand statistics are asked for just once.


47 A2 94UC 5-35

Command Execution

• The command is checked for validity.

• If no interface is specified, a command record asking for the statistics of all theinterfaces is built and sent to the OCS Front End concerned.

• If an interface name is specified, a command record requesting for the statisticsof this interface is sent to the OCS Front End concerned every "interval" periodof time until interrupted (via the console). The request is done once if "interval"is 0 or missing.

• Each time a response is received, it is analyzed and items provided by theresponse are displayed.

• The display depends on whether or not the INTERVAL parameter is present. Ifthe INTERFACE parameter is omitted, the display is as follows:

Name Mtu Network Address lo0 2048 loopback localhost fd0 1500 129.182.50 bach

continued: Ipkts Ierrs Opkts Oerrs 132 0 132 0 10000 0 12000 0

• The display consists of an identification line followed by up to 2 value lines eachone tied to an interface.

• Each column in the display is identified by a name in the identification linewhose meaning is given hereafter and contains the corresponding value providedby the response:

• Name is the name of the interface.

• Mtu is the Maximum Transmission Unit. It defines the largest size in bytes thetransmitted datagram will have on this interface.

• Network is the IP address of the network tied to the interface or itscorresponding symbolic name.

• Address is the IP address associated with the interface or its correspondingsymbolic name.

• Other items are input or output statistics related to the number of transmittedpackets (up to 100 million minus 1) and the number of errors detected (up to 10million minus 1).

• When an interface name is specified, only the identification line followed by thevalue line corresponding to the interface specified are displayed.


5-36 47 A2 94UC

• If the -n option is specified, IP addresses are represented as a number in dotnotation instead of symbolic names. For example, in the above display,"localhost" is replaced by 127.0.0.1 (and so on).

• The fields above are displayed at screen positions: 1, 6, 12, 24, 40, 49, 57, 66(respectively).

• If the INTERVAL parameter is present, the display is as follows:

− First, a banner: input (interface) output input (Total) output packets errs packets errs packets errs packets errs

− Second, a display line giving statistics counters at sampling time. Forexample:

1567 0 1567 0 4885 0 1567 0

which means:

1567 packets have been received by the selected interface, this interface hassent 1567 packets. No packets (received or sent) were in error for thisinterface.

4885 packets have been received and 1567 packets have been transmitted bythe whole interface. No packets (received or sent) were in error.

− When INTERVAL is not 0, up to 20 display lines giving the evolution ofthe statistics counters since the previous sampling. For example:

19 0 19 0 20 0 19 0

which means (since the previous sampling):

19 packets have been received by the selected interface, this interface has sent19 packets. No packets (received or sent) were in error for this interface.

20 packets have been received and 19 packets have been transmitted by thewhole interface. No packets (received or sent) were in error.

In this case, the sequence banner, partial-statistics, global-statistics is repeateduntil an ENDNETST command is entered.

Error Detection

If a response indicates an error or if there is no response, an error message isdisplayed on the operator console.


47 A2 94UC 5-37

EXAMPLES:

S: NETSTAT EA92 -N-I LO0 0

NC74 NETSTAT RESPONSE FROM EA92

input (lo0) output input (Total) output packets errs packets errs packets errs packets errs 0 0 0 0 0 0 0 0

S: NETSTAT EA92 -N-I INTERVAL = 0


Name Mtu Network Address Ipkts Ierrs Opkts Oerrsfd0 4352 129 129.183.53.35 0 0 0 0


lo0 2048 127 127.0.0.1 0 0 0 0❑

Syntax (to display routing table)

NETSTAT EAnn

[-n]-r



-n optional positional 2 character string. When present,network address will be represented as a numberinstead of its corresponding symbolic name.

-r positional 2 character string which indicates that thecommand is to display the routing table contents.


5-38 47 A2 94UC

Command Execution

• The command is checked for validity.• A command record (which asks for the routing table contents) is built and sent to

the OCS Front End concerned.• The incoming responses are analyzed and the items provided are displayed.

These items are related to the available routes and their status. For example,they are displayed as follows:

Destination Gateway Flags localhost localhost UH 129.182.50 bach U

continued: Refcnt Use Interface 0 0 lo0 48 4002 fd0

where:

The 1st line is an item identification line followed by an item value line each ofthem describing a route.

Each column in the display is identified by a name in the identification line whosemeaning is given hereafter and contains the corresponding value provided by theresponse:

destination is the address of the destination host or network toreach expressed either as a name or its correspondingIP address depending on the -n option. For example, ifthe -n option is given, 127.0.0.1 will be displayedinstead of localhost.

gateway is the address of the gateway to use to reachdestination expressed either as a name or itscorresponding IP address depending on the -noption as shown above.

flags is a set of flags indicating if the route is U (up) or G(to a gateway) or H (to a Host) or D when the route hasbeen dynamically added through an ICMP redirectmessage.


47 A2 94UC 5-39

Refcnt is the number of users of the route.

Use is the number of packets transmitted using this route.

Interface is the name of the interface that connects to thenetwork.

The above fields are displayed at screen positions: 1, 17, 33, 39, 46, 55(respectively).

Error Detection

If a response indicates an error or if there is no response, an error message isdisplayed on the operator console.


5-40 47 A2 94UC

5.6.6 PING Command

Purpose

During administration, this command is used for network testing and faultisolation. The commands sends an Internet Control Message Protocol ICMPecho_request packet to elicit an ICMP echo_response packet.

Syntax

PING EAnn

[-v]

host_name | host_ipadd

[SIZE = { 64 | packet_size }]

[COUNT = { 1 | count }]



-v optional positional 2 character string which specifiesICMP packets received other than echo_responsepackets will be listed.

host_name | host_ipaddthis mandatory argument is either the symbolic nameof the host to which the echo_request packet is sent orits corresponding IP address.

SIZE indicates the size the echo_request packet will have.The maximum value is 4096, so the maximum userdata part size of the echo_request packet will belimited to 4068 bytes.The default value is 64.


47 A2 94UC 5-41

COUNT indicates the number of echo_request packets to besent. This optional parameter is a string of up to8 decimal digits. The default is COUNT = 1.If COUNT = 0 is specified, the ICMP echo_requestpacket is sent repeatedly until terminated by anENDPING command.

Command Execution

• The command is checked for validity.

• A command record (which requests the sending of an ICMP echo_requestpacket) is built and it is sent to the OCS Front End concerned:

• if the COUNT parameter is omitted or if it is equal to 1, the request is sent once,

• otherwise, the request is sent once per second and the count value isdecremented each time a packet is sent, until the count value is exhausted.

• Each time an echo response is received, the following message is displayed:

ww bytes from 129.182.51.10 icmp_seq=xx time=yy mswhere:

• ww indicates the size of the packet received.

• xx indicates the packet number.

• yy indicates the round trip time for the packet in milliseconds.

• When the command completes, or if a processing time out occurs because nomore responses arrive, a summary is displayed as shown below. This summarygives the number of packets sent, received, and lost plus a statistic concerningthe round trip time, as follows:

----<host_name> PING Statistics nn packets transmitted, mm packets received, vv% packets lost roundtrip (ms) min/avg/max = tt/uu/vv

Error Detection

If a response indicates an error or if all the expected responses do not occur withina predetermined period of time, an error message is displayed (on the operatorconsole).

NOTE:If a PING command is requested from an OCS server towards OPEN 7 or vice-versa and the OCS Front Ends share the same OCS controller, the destinationdeclaration must have been made in the corresponding ARP tables (either atconfiguration, or subsequently by an ARP operator commnad).


5-42 47 A2 94UC

5.6.7 ROUTE Command

Purpose

During administration, this command is used to manage the OCS Front End routingtables.

It is used:

• To define and add a route in the routing table. There is no limit to the number ofroutes created in the routing table.

• To cancel a route in the routing table.

• To flush all the gateways entries in the routing table, that is useful to isolate anetwork from the other ones.

Syntax (to add a route)

ROUTE EAnn

add

NET | HOST

name | ip_add

gateway_name | gateway_ipadd

metric



add This 3 character string indicates that the ROUTEcommand is used to add a route into the IPS stackrouting table. It is a positional argument.


47 A2 94UC 5-43

NET | HOST These two positional keywords indicates how the nextpart (name or ip_add) of the address parameter is to beinterpreted.

If NET, the next part of the address parameter isinterpreted as a network address.

If HOST, the next part of the address parameter isinterpreted as a host address.

name | ip_add This parameter is either the symbolic name of thedestination to reach or its IP Internet address.

If a symbolic name is provided, the corresponding IPaddress is taken either from the ETC_NETWORKS orfrom the ETC_HOSTS subfile depending on whetherthe preceding parameter NET or HOST (respectively).Otherwise, the IP address is directly taken from thecommand line.

Name is a string of up to 15 printable characters.String should neither contain nor blank, nor dot nor"#" characters.

A host address is expressed as a four decimal parts dotnotation address when up to four parts are used toexpress a network address, missing parts being filledwith 0s on the right during command processing.


This parameter is either the symbolic name of thegateway or its IP address.

If a name is provided, the corresponding IP address isfetched from the ETC_HOSTS subfile else it isdirectly taken from the command line.

Name is a up to 15 printable characters string. Stringshould neither contain nor blank, nor dot nor"#" characters.In every case, the IP address is expressed as a fourdecimal parts dot notation address.

metric This mandatory parameter indicates the number ofhops to the destination.It is expressed as an up to ninedecimal digits.


5-44 47 A2 94UC

Syntax (to cancel a route)

ROUTE EAnn

delete

NET | HOST

name | ip_add




delete positional string which indicates that the routecorresponding to the following parameters is to beremoved from the routing table.

NET | HOST These two positional keywords indicates how the nextpart (name or ip_add) of the address parameter is to beinterpreted.

If NET, the next part of the address parameter isinterpreted as a network address.

If HOST, the next part of the address parameter isinterpreted as a host address.


47 A2 94UC 5-45

name | ip_add This parameter is either the symbolic name of thedestination to reach or its IP Internet address.

If a symbolic name is provided, the corresponding IPaddress is taken either from the ETC_NETWORKS orfrom the ETC_HOSTS subfile depending on whetherthe preceding parameter NET or HOST (respectively).Otherwise, the IP address is directly taken from thecommand line.

Name is a string of up to 15 printable characters.String should neither contain nor blank, nor dot nor"#" characters.

A host address is expressed as a four decimal parts dotnotation address when up to four parts are used toexpress a network address, missing parts being filledwith 0s on the right during command processing.

When the value DEFAULT is given to this parameter,this indicates a default route declaration. This routewill be used for outgoing packets when no entrymatches in the OCS Front End IP routing table (usefulwith the NET parameter). DEFAULT does not need tobe declared in the ETC_HOSTS orETC_NETWORKS subfiles.


This parameter is either the symbolic name of thegateway or its IP address.

If a name is provided, the corresponding IP address isfetched from the ETC_HOSTS subfile else it isdirectly taken from the command line.

Name is a up to 15 printable characters string. Stringshould neither contain nor blank, nor dot nor"#" characters.In every case, the IP address is expressed as a fourdecimal parts dot notation address.


5-46 47 A2 94UC

Command Execution

• The command line is checked and parameters are processed (as for the ROUTEcommand in the manual Network Generation).

• A command record requesting for a deletion is sent to the OCS Front Endconcerned.

• The incoming response (from the OCS Front End) is checked.

Error Detection

• The response indicates an error because the entry to be deleted does not exist inthe table.

• A syntactic or a semantic error is found during command analysis.

• The host name or the gateway name is not found while looking up in theETC_HOSTS subfile.

• The network name is not found while looking up in the ETC_NETWORKSsubfile.

• No response is provided within a required time.

• The response coming from the OCS Front End indicates an error.

• All errors detected are displayed on the operator console.

Syntax (to flush gateways entries)

ROUTE EAnn -f



-f 2 character string which indicates this ROUTEcommand is to flush the gateways entries in the routingtable.


47 A2 94UC 5-47

Command Execution

• a command record requesting the flushing of the routing table is sent to the OCSFront End concerned.

• the incoming response (from the OCS Front End) is analyzed to check the resultof the operation.

Error Detection

If the response indicates an error, an error message is displayed (on the operatorconsole).


5-48 47 A2 94UC

5.7 SNMP Manager Commands

NOTE:The commands described in this section are available only on the DPS 7000based on Bull processor.

These commands cannot be executed in GCL batch mode nor via the statementEXDIR.

There are 3 types of SNMP Manager commands:

• Request Commands,• Stop Commands,• Documentation Commands.

5.7.1 Request Commands

The following request commands are available:

• GETARP• GETNET• GETROUTE• GETUDP• GETTCPCN• SNMPGET• SNMPNEXT• SNMPSET

These commands are used to display/modify the values of MIB objects in therequested SNMP agent.

5.7.2 Stop Commands

The following stop commands are available:

• ENDGETAR• ENDGETCN• ENDGETNT• ENDGETRT• ENDGETUD• ENDSNMP• ENDSNMPG• ENDSNMPN• ENDSNMPS

These commands are used to stop an earlier request command.


47 A2 94UC 5-49

5.7.3 Documentation Commands

The following documentation commands are available:

• CRSNMPDOC• SNMPDOC

5.7.4 Common Parameters

The following parameters are common to several SNMP Manager commands:

file

This is the name of the subfile to which a copy of the response (to the request) iswritten. It must be a member of an SL library. If the subfile specified does notexist (before the request is issued), it is created. If the subfile exists, the result ofthe request is appended to its existing contents. The first line written gives the dateand time of the response.

For example:

file = my.snmp.rprt..traces

host

This represents the destination host (whose agent is the target of the command). Itis expressed as an IP address or as a symbolic name. The host name must be thefirst field of a line in the SYS.DSACONF..SMGR_COMMPORT subfile (the otherfields are port# and community). If the host is given as a symbolic name, then thisname must exist in SYS.DSACONF..ETC_HOSTS subfile. The maximum lengthof the field is 15 characters.

For example:

host = bcc1-ncc1host = 129.183.53.100

retry

This is the number of retry attempts made if a timeout occurs. It is a number from0 to 9. The default is 3.

For example:

retry = 2


5-50 47 A2 94UC

timeout

This is the time that the manager waits for a response before retrying or abortingthe request. It is expressed in seconds (from 1 to 99). The default is 30 seconds.

For example:

timeout = 10

The SNMP Manager Commands are described below. For ease of reference, theyare presented in alphabetical order.


47 A2 94UC 5-51

5.7.5 CRSNMPDOC Command

Purpose

This command helps you create on-line documentation. It displays a form that youfill in to create the documentation about an object (also given in the form). Thiscommand is not destined to a specific host.

Syntax

CRSNMPDOC

[FILE = library..subfile]


FILE See "Common Parameters" in paragraph 5.7.4. Thefile specified is known as the documentation file.

Form Used to Create Object Documentation

Each item you enter in the form becomes part of the on-line documentation. Thecommand embeds the data (in the form) with syntax elements before writing it tothe documentation file. The form contains the following fields:

OBJECT This is mandatory. It is the object to be documented.This field describes either:(i) a node name in the MIB subtree (if EQUALS is theonly other field entered), or(ii) a managed object (if SYNTAX and other fields arealso entered).

In the first case, the following single line is written tothe documentation file:

objectName OBJECT IDENTIFIER ::= {equalsName number}

where "objectName" is the value you enter in theOBJECT field, and "equalsName number" is the valueyou enter in the EQUALS field.


5-52 47 A2 94UC

In the second case, several lines are written to thedocumentation file. The first line is:

objectName OBJECT-TYPE

where "objectName" is the value you enter in theOBJECT field. The other lines are written from theSYNTAX and other fields.

SYNTAX This is optional. If SYNTAX is specified, thefollowing line is written to the documentation file:

SYNTAX syntaxName

where "syntaxName" is the value you enter in theSYNTAX field. You may use the followingabbreviations:

I for INTEGER,OI for OBJECT IDENTIFIER,IPA for IP Address,C for Counter,G for Guage,T for TimeTicks,or OS for Object String.

ACCESS This is optional. If ACCESS is specified, thefollowing line is written to the documentation file:

ACCESS accessName

where "accessName" is the value you enter in theACCESS field. You use the following abbreviations:

ro for read-only,wo for write-only,rw for read-write,na for not-accessible.

STATUS This is optional. If STATUS is specified, the followingline is written to the documentation file:

STATUS statusName

where "statusName" is the value you enter in theSTATUS field. You use the following abbreviations:

m for mandatory,o for optional,d for deprecated (not recommended).


47 A2 94UC 5-53

DESCRIPTION This is optional. This is 1 to 16 lines of free text. Itspurpose is to describe the object semantics. The textentered must not contain double-quotes ("), becausethe text will be embedded in double-quotes in thedocumentation file. When the form is displayed, only4 lines are actually displayed for the DESCRIPTIONparameter. If you want to enter more than 4 lines, youenter a plus sign (+) in the last line (being displayed).

Note that four fields (SYNTAX, ACCESS, STATUS,DESCRIPTION) are optional. However, if you enterone of them, you must enter all four of them.

INDEX This is optional. This is one or more object names(separated by commas). If INDEX is specified, thefollowing line is written to the documentation file:

INDEX {object1, object2, ..., objectn}

where "objectn" are the object names. There is not anexplicit limit on the number of objects you can enter.However, the total length of the string entered(object names, commas, spaces, etc.) must not exceed64 characters.

INDEX may be specified only if SYNTAX is alsospecified.

EQUALS This is mandatory. You must enter 2 items: an objectname, and an object number. The object name is thename of the parent object in the MIB tree. The objectnumber is the rank of the object in the parent objectsubTree. The following line is written to thedocumentation file:

::={objectParent 4}

where "objectParent" and "4" are the values you enter.


5-54 47 A2 94UC

SEQUENCE This is optional. You can enter 0 to 16 lines of text.Each line is composed of 2 subfields: an object name,and an object type. If you enter:

object1 INTEGER (0..127) object2 OCTETSTRING

then, the following lines are written to thedocumentation file:

objectName::= SEQUENCE{ object1 INTEGER (0..127), object2 OCTETSTRING }

where "objectName" is the value entered in theOBJECT parameter.When the form is displayed, only 4 lines are actuallydisplayed for the SEQUENCE parameter. If you wantto enter more than 4 lines, you enter a plus sign (+) inthe last line (being displayed).

SEQUENCE may be specified only if SYNTAX is alsospecified.

SEQUENCE_CONT This is optional. Its purpose is to provide acontinuation for the SEQUENCE parameter (if there isnot enough space in the SEQUENCE field). So,SEQUENCE_CONT may be specified only ifSEQUENCE is also specified. You can enter 0 to 16lines of text. Each line is as described above forSEQUENCE.When the form is displayed, only 4 lines are actuallydisplayed for the SEQUENCE_CONT parameter. Ifyou want to enter more than 4 lines, you enter a plussign (+) in the last line (being displayed).


47 A2 94UC 5-55

QUIT This is mandatory. You specify Y to quit and N not toquit.

Consult RFC1065 for the template syntax of on-line documentation.

Modifying Object Documentation

To modify or correct documentation already entered, you must use a text editor tochange the contents of the documentation file. Be careful not to introduce errors inthe syntax elements of the documentation file.


5-56 47 A2 94UC

5.7.6 ENDGETAR Command

Purpose

This command stops a GETARP command (before its normal completion).

Syntax

{ ENDGETAR }{ ENDGETARP }{ STOP_SNMP_GET_ARP }


None.

EXAMPLE:

endgetar❑


47 A2 94UC 5-57

5.7.7 ENDGETCN Command

Purpose

This command stops a GETTCPCN command (before its normal completion).

Syntax

{ ENDGETCN }{ ENDGETTCPCONN }{ STOP_SNMP_GET_CONNECT }


None.

EXAMPLE:

endgetcn❑


5-58 47 A2 94UC

5.7.8 ENDGETNT Command

Purpose

This command stops a GETNET command (before its normal completion).

Syntax

{ ENDGETNT }{ ENDGETNET }{ STOP_SNMP_GET_NET }


None.

EXAMPLE:

endgetnt❑


47 A2 94UC 5-59

5.7.9 ENDGETRT Command

Purpose

This command stops a GETROUTE command (before its normal completion).

Syntax

{ ENDGETRT }{ ENDGETROUTE }{ STOP_GET_ROUTE }


None.

EXAMPLE:

endgetrt❑


5-60 47 A2 94UC

5.7.10 ENDGETUD Command

Purpose

This command stops a GETUDP command (before its normal completion).

Syntax

{ ENDGETUD }{ ENDGETUDP }{ STOP_SNMP_GET_UDP }


None.

EXAMPLE:

endgetud❑


47 A2 94UC 5-61

5.7.11 ENDSNMP Command

Purpose

This command stops any request command (before normal completion of therequest command).

Syntax

{ ENDSNMP }{ }{ STOP_SNMP_REQ }


None.

EXAMPLE:

endsnmp❑


5-62 47 A2 94UC

5.7.12 ENDSNMPG Command

Purpose

This command stops an SNMPGET command (before its normal completion).

Syntax

{ ENDSNMPG }{ ENDSNMPGET }{ STOP_SNMP_GET }


None.

EXAMPLE:

endsnmpg❑


47 A2 94UC 5-63

5.7.13 ENDSNMPN Command

Purpose

This command stops an SNMPNEXT command (before its normal completion).

Syntax

{ ENDSNMPN }{ ENDSNMPNEXT }{ STOP_SNMP_NEXT }


None.

EXAMPLE:

endsnmpn❑


5-64 47 A2 94UC

5.7.14 ENDSNMPS Command

Purpose

This command stops an SNMPSET command (before its normal completion).

Syntax

{ ENDSNMPS }{ ENDSNMPSET }{ STOP_SNMP_SET }


None.

EXAMPLE:

endsnmps❑


47 A2 94UC 5-65

5.7.15 GETARP Command

Purpose

This command displays information contained in the ipNetToMediaTable. This isthe IP Address Translation table used to map an IP address to a physical address.

The name of the corresponding stop command is ENDGETAR.

Syntax

{ GETARP }{ }{ GET_ARP }

HOST=hostId

[FILE = library..subfile] [TIMEOUT = number] [RETRY = number]


HOST See "Common Parameters" in paragraph 5.7.4.

FILE See "Common Parameters" in paragraph 5.7.4.

TIMEOUT See "Common Parameters" in paragraph 5.7.4.

RETRY See "Common Parameters" in paragraph 5.7.4.


5-66 47 A2 94UC

Format of Response

Each line represents one entry of ipNetToMediaTable and contains the following4 fields:

• ipNetToMediaIfIndexSymbolic name of the interface (field Int). 3 characters.

• ipNetToMediaPhysAddressPhysical Address Mask (field PhysAddress). 17 characters.

• ipNetToMediaNetAddrIP Address (field NetAddr). 15 characters.

• ipNetToMediaTypeMnemonic (field Type), 5 characters. The meaning of the mnemonic can beobtained by executing an SNMPDOC command on the ipNetToMediaTypeobject. The values of type are: OTHER, STATiC, INVALid, DYNAMic.

EXAMPLES:

getarp bcaf-ncc9

may give the following response:

NC51 getarp to BCAF-NCC9:COMMAND LAUNCHEDNC53 Int PhysAddress---- NetAddr--------- TypeNC53 fd 08:00:38:10:00:0E 129.183.53.36 otherNC53 fd 08:00:38:10:00:0F 129.183.53.37 statcNC51 getarp to BCAF-NCC9:COMMAND COMPLETED❑


47 A2 94UC 5-67

5.7.16 GETNET Command

Purpose

This command displays information contained in the IP address table. This tablecontains addressing information relevant to the host's IP address.

The name of the corresponding stop command is ENDGETNET.

Syntax

{ GETNET }{ }{ GET_NET }

HOST=hostId








5-68 47 A2 94UC

Format of Response

Each line represents one entry of ipAddrTable and contains the following 5 fields:

• ipAdEntAddrIP Address (field Addr). 15 characters.

• ipAdEntIfIndexSymbolic name of the interface (field Int). 3 characters.

• ipAdEntNetMaskIP Address Mask (field NetMask). 15 characters.

• ipAdEntBcastAddrIP Broadcast Address (field Broadcast Addr). 15 characters.

• ipAdEntReasmMaxSizeSize of the largest IP datagram (incoming from the interface) that can bereassembled (field MxSiz). 5 characters.

EXAMPLES:

getnet bcc1-ncc1


NC51 getnet to BCC1-NCC1:COMMAND LAUNCHEDNC53 Addr--------- Int NetMask------- Broadcast Addr- MxSizNC53 127.0.0.1 l0 255.0.0.0 65535NC53 199.182.57.36 fd 255.255.255.0 199.182.57.255 65535NC51 getnet to BCC1-NCC1:COMMAND COMPLETED❑


47 A2 94UC 5-69

5.7.17 GETROUTE Command

Purpose

This command displays information contained in the IP Routing table.

The name of the corresponding stop command is ENDGETRT.

Syntax

{ GETROUTE }{ }{ GET_ROUTE }

HOST=hostId








5-70 47 A2 94UC

Format of Response

Each line represents one route (one entry of ipRouteTable) and contains thefollowing 11 fields:

• ipRouteDestIP address of destination (field Dest). 15 characters.

• ipRouteNextHopIP Address of next hop (field Nexthop). 15 characters.

• ipRouteTypeMnemonic (field Type), 5 characters. The values are: OTHER, INVALid,DIReCT, INDIRect.

• ipRouteProtoMnemonic (field Proto), 5 characters. The values are: OTHER, LOCAL,NETMGmt, ICMP, EGP, GGP, HELLO, RIP, IS-IS, ES-IS, CISCOigrp,BBNSPfigp, OSPF, BGP.

• ipRouteMaskIP Address Mask (field Mask). 15 characters.

• ipRouteIfIndexSymbolic name of the interface (field Int). 3 characters.

• ipRouteMetric1 to ipRouteMetric5Route metric (fields M1, M2, M3, M4, M5). 5 x 2 digits.

EXAMPLES

getroute bcc1-ncc1


NC51 getroute to BCC1-NCC1:COMMAND LAUNCHED NC53 Dest-----------NextHop--------Type- Proto MaskHexa Int M1 M2 M3 M4 M5 NC53 0.0.0.0 199.182.57.19 indir rip FFFFFF00 fd 1 -1 -1 -1 0 NC53 127.0.0.1 127.0.0.1 dirct local FF000000 l0 0 -1 -1 -1 0 NC53 129.182.56.36 199.182.57.19 indir rip FFFFFF00 fd 1 -1 -1 -1 0 NC53 199.182.57.0 199.182.57.36 dirct local FFFFFF00 fd 0 -1 -1 -1 0 NC51 getroute to BCC1-NCC1:COMMAND COMPLETED

❑


47 A2 94UC 5-71

5.7.18 GETTCPCN Command

Purpose

This command displays TCP connection-specific information contained in thetcpConnTable.

The name of the corresponding stop command is ENDGETCN.

Syntax

{ GETTCPCN }{ GETTCPCONN }{ GET_TCP_CONNECTION }

HOST=hostId








5-72 47 A2 94UC

Format of Response

Each line represents one entry of tcpConnTable and contains the following 5 fields:

• tcpConnLocalAddressLocal IP Address Mask (field LocalAddr). 15 characters.

• tcpConnLocalPortLocal port number (field LPort). 5 digits.

• tcpConnRemAddressRemote IP Address Mask (field RemoteAddr). 15 characters.

• tcpConnRemPortRemote port number (field RPort). 5 digits.

• tcpConnStateMnemonic (field State), 5 characters. The values of state are: CLOSeD,LISTeN, SYNSenT, SYNReCeived, ESTABlished, FINWait1, FINWait2,CLoSeWaiT, LaSTAcK, CLoSiNG, TIMeWaiT, DeLeteTCB.

EXAMPLES:

gettcpcn bcc1-ncc1


NC51 gettcpconn to BCC1-NCC1:COMMAND LAUNCHEDNC53 LocalAddr---- LPort RemoteAddr---- RPort StateNC53 0.0.0.0 22018 0.0.0.0 00000 synRcNC53 127.0.0.1 22017 127.0.0.1 22018 finW2NC53 127.0.0.1 22018 127.0.0.1 22017 finW2NC51 gettcpconn to BCC1-NCC1:COMMAND COMPLETED❑


47 A2 94UC 5-73

5.7.19 GETUDP Command

Purpose

This command displays UDP listener information (about end-points on which alocal application is currently accepting datagrams) contained in the udpTable.

The name of the corresponding stop command is ENDGETUD.

Syntax

{ GETUDP }{ }{ GET_UDP }

HOST=hostId







Format of Response

Each line represents one entry of udpTable and contains the following 2 fields:

• udpLocalAddressLocal IP Address Mask (field LocalAddr). 15 characters.

• udpLocalPortLocal port number (field LPort). 5 digits.


5-74 47 A2 94UC

EXAMPLES:

getudp bcc1-ncc1


NC51 getudp to BCC1-NCC1:COMMAND LAUNCHEDNC53 LocalAddr---- LPortNC53 0.0.0.0 00161NC53 0.0.0.0 01043NC51 getudp to BCC1-NCC1:COMMAND COMPLETED❑


47 A2 94UC 5-75

5.7.20 SNMPDOC Command

Purpose

This command displays documentation about a symbolic object (given via aparameter). This command is not destined to a specific host.

Syntax

SNMPDOC

OBJECT=ObjectName



OBJECT A symbolic object name (for example, interfaces,ipRouteDest).


EXAMPLE:

snmpdc ipRouteEntry❑


5-76 47 A2 94UC

5.7.21 SNMPGET Command

Purpose

This command displays the value of one or more specific object instances.

The name of the corresponding stop command is ENDSNMPG.

Syntax

{SNMPGET }{ }{SNMP_GET}

HOST=hostId

OBJECTS=(ObjectInstance1 [ObjectInstance2 ...])


[TIMEOUT=number]

[RETRY=number]



OBJECTS This field contains from 1 to 10 object instance names.Each name must be given in simple dot notation(for example, 1.3.6.1.2.1.2.2.1.5.1), or partially inmnemonic form (for example, ifSpeed.1). Note that itis not possible to give a pure mnemonic name(for example, ifSpeed); if you do, you get an"UNKNOWN OBJECT" error message. If more thanone object instance is given, then the each one must beon a separate line (request submitted through a form),or be embedded in parentheses (request submittedthrough an operator command).

For example:

OBJECTS = ifMtu.1OBJECTS = (ifSpeed.1 ifMtu.1 ifMtu.2)


47 A2 94UC 5-77




EXAMPLES:

snmpget bcc1-ncc1 ifSpeed.1


NC51 snmpget to BCC1-NCC1:COMMAND LAUNCHEDNC53 Name------------------------ Value -------------NC53 ifSpeed.1 0NC51 snmpGet to BCC1-NCC1:COMMAND COMPLETED❑


5-78 47 A2 94UC

5.7.22 SNMPNEXT Command

Purpose

This command displays the value of one or more successor object instances from apoint in the MIB tree. This point may be an object (for example, ifMtu), an objectinstance (for example, ifMtu.1), or an upper point in the MIB tree (for example,1.3.6.1.2).

The name of the corresponding stop command is ENDSNMPN.

Syntax

{SNMPNEXT }{ }{SNMP_NEXT}

HOST=hostId

OBJECTS=(ObjectInstance1 [ObjectInstance2 ...])


[TIMEOUT=number]

[RETRY=number]



OBJECTS This field contains from 1 to 10 object instance names.Each name must be given in simple dot notation(for example, 1.3.6.1.2.1.2.2.1.5.1), or partially inmnemonic form (for example, ifSpeed.1). Note that itis possible to give an instance name (for example,ifSpeed.1) or an object name (for example, ifSpeed).If more than one object instance is given, then eachone must be on a separate line (request submittedthrough a form), or be embedded in parentheses(request submitted through an operator command).


47 A2 94UC 5-79

For example:

OBJECTS = ifSpeedOBJECTS = (ifSpeed.1 ifMtu.1 ifMtu.2)




Requests Against the Whole MIB

To display the whole MIB of an agent (like the local agent), you specify thefollowing objects:

• mibTo display all the RFC1213 (mib-2) and RFC1285 (fddi) objects, you specify:

snmpnext bcc1-ncc1 mib

• bull or bullFcpTo display all specific FCP objects, you specify:

snmpnext bcc1-ncc1 bullFcp

EXAMPLES:

snmpnext bcc1-ncc1 ifMtu


NC51 snmpnext to BCC1-NCC1:COMMAND LAUNCHEDNC53 Name------------------------ Value -------------NC53 ifMtu.1 4352NC53 ifMtu.2 2048NC51 snmpNext to BCC1-NCC1:COMMAND COMPLETED❑


5-80 47 A2 94UC

5.7.23 SNMPSET Command

Purpose

This command modifies the value of one or more specific object instances. Theinstance must be writeable and the agent must have given the right to modify to themanager (see the agent community file).

The name of the corresponding stop command is ENDSNMPS.

Syntax

{ SNMPSET }{ }{ SET_SNMP_VALUE }

HOST=hostId

OBJ1=(ObjectInstance1 Value1 [Type1])

[OBJ2=(ObjectInstance2 Value2 [Type2]) ... ]


[TIMEOUT=number]

[RETRY=number]



OBJ1, OBJ2, OBJ3, You may modify up to 5 object instances in onecommand.

OBJ4, OBJ5 Three items are given for each object instance. Theleftmost item is the name of the object instance(for example, snmpEnableAuthTraps.0). The middleitem is the value to be applied (for example, 1). Therightmost item (optional) is the data type as:INTEGER, OCTETSTRING, IPADDRESS,OBJECTID. If the type is omitted, the defaultis INTEGER.At least OBJ1 must be specified.


47 A2 94UC 5-81

Each object instance name must be given in simple dotnotation (for example, 1.3.6.1.2.1.2.2.1.5.1), orpartially in mnemonic form (for example, ifSpeed.1).Note that it is not possible to give a pure mnemonicname (for example, ifSpeed); if you do, you get an"UNKNOWN OBJECT" error message.The snmpset command is atomic, i.e., if one objectcannot be set (for any reason), the whole command isrejected.




EXAMPLES:

snmpset bcc1-ncc1 (snmpEnableAuthTraps.0 2 integer)

may give the following response (if the modification is accepted):

NC51 snmpset to BCC1-NCC1:COMMAND LAUNCHEDNC53 Name------------------------ Value -------------NC53 snmpEnableAuthTraps.0 2NC51 snmpset to BCC1-NCC1:COMMAND COMPLETED❑


5-82 47 A2 94UC

5.8 OSI/DIWS Extended Set of Commands

NOTE:The commands described in this section cannot be executed in GCL batch modenor via the statement EXDIR.

The following extended commands are described below:

• ATTACH_FCP_IVMO• CREATE_FCP_TCIVMO• DISPLAY_FCP_TCIVMO• DISPLAY_IVMO_LINK• FCP_EXTENDED_GA_TC• LIST_FCP_TCIVMO• MODIFY_FCP_TCIVMO• UPGRADE_FCP_CONFIG

For ease of reference, they are presented in alphabetical order.


47 A2 94UC 5-83

5.8.1 ATTACH_FCP_IVMO Command

Purpose

This command attaches an RTS (Remote Transport Station) or an RNAP to a newlycreated IVMO. The command can also be used to change the IVMO attached to anRTS or an RNSAP.

Syntax

{ ATTACH_FCP_IVMO }{ }{ ATTIVMO }

FCP_NAME = char4

IVMO = char8

{RTS = char8 } { } {RNSAP = char8}


FCP_NAME This identifies the OCS Front End to which thecommand applies. It is a 4 character string giving theLCT name identifying the OCS Front End in theNETGEN configuration. FCP_NAME must beginwith the two characters EA.

IVMO This identifies the IVMO to which the commandapplies. It is an 8 character giving the name of theIVMO.

RTS This 8 character string identifies the RTS to which theIVMO is to be attached. RTS and RNSAP aremutually exclusive.

RNSAP This 8 character string identifies the Remote NSAP towhich the IVMO is to be attached. RNSAP and RTSare mutually exclusive.


5-84 47 A2 94UC

EXAMPLE:

ATTIVMO FCP_NAME=EA92 IVMO = ivmo_df RTS = BCA2NCC9;

displays:

NC54 command : ATTIVMO command completed

ATTIVMO FCP_NAME=EA92 IVMO = ivmo_df RTS = toto;

displays:

NC54 command : ATTIVMO response from EA92NC54 command : ATTIVMO : UNKNOWN NRTSNC54 command : ATTIVMO command completed❑


47 A2 94UC 5-85

5.8.2 CREATE_FCP_TCIVMO Command

Purpose

This command dynamically adds a Transport Connection IVMO to the OCS FrontEnd configuration.

Syntax

{ CREATE_FCP_TCIVMO }{ }{ CRIVMO }

FCP_NAME = EAxx

IVMO_NAME = char_8

[MAXRCRDT = {dec_3 | 7}]

[MAXSCRDT = {dec_3 | 7 }]

[MAXRETRY = {dec_1 | 3}]

[T1TIME = {dec_6 | 10000}]

[WTIME = {dec_6 | 60000}]

[ITIME = {dec_6 | 180000}]

[ACKTIME = { dec_2 | 5000}]

[TPUSIZE = {dec_4 | 1024}]

[T_CHECKSUM = {Y | N}]

[EXTMODE = {Y | N}]


5-86 47 A2 94UC


FCP_NAME This identifies the OCS Front End to which thecommand applies. It is a 4 character string giving theLCT name identifying the OCS Front End in theNETGEN configuration.

IVMO_NAME This identifies the IVMO to which the commandapplies. It is a string of 8 characters giving thesymbolic name of the IVMO.

other parameters Refer to the description of the TCIVMO directive inthe manual GCOS 7 Network Generation.

EXAMPLE:

CRIVMO ea81 ivmo_a

displays:

NC54 command : CRIVMO response from EA81NC58 IVMO# : 07 IVMO_NAME: IVMO_ANC54 command : CRIVMO command completed

Subsequently,

CRIVMO ea81 ivmo_a

displays:

NC54 command : CRIVMO response from EA81NC54 command : CRIVMO ERROR : IVMO already declaredNC54 command : CRIVMO command terminated❑


47 A2 94UC 5-87

5.8.3 DISPLAY_FCP_TCIVMO Command

Purpose

This command displays the attributes of a Transport Connection IVMO of the OCSFront End selected. The IVMO can be selected either by its symbolic name or itsinternal number (if necessary, use an LIST_FCP_TCIVMO command to retrievethis information).

Refer to the manual GCOS 7 Network Generation for a complete description of theattributes displayed.

Syntax

{ DISPLAY_FCP_TCIVMO }{ }{ DPIVMO }

FCP_NAME = EAxx

{IVMO_NUMBER = dec_8} { } {IVMO_NAME = char_8 }



IVMO_NUMBER This identifies the IVMO to which the commandapplies. It is a decimal number (8 digits) giving theinternal number of the IVMO. IVMO_NUMBER andIVMO_NAME are mutually exclusive.

IVMO_NAME This identifies the IVMO to which the commandapplies. It is a string of 8 characters giving thesymbolic name of the IVMO. IVMO_NAME andIVMO_NUMBER are mutually exclusive.


5-88 47 A2 94UC

EXAMPLE:

DPIVMO FCP_NAME=EA92 IVMO_NUMBER = 02;

displays:

NC54 command : DPIVMO response from EA92NC59 IVMO#=02 IVMO_NAME=IVMO_DF MAXRCRDT=7 MAXSCRDT=7 MAXRETRY=3 T1TIME=10000 WTIME=60000 ITIME=180000 ACKTIME=5000 TPUSIZE=2048 EXTMODE=N T_CHECKSUM=YNC54 command : DPIVMO command completed❑


47 A2 94UC 5-89

5.8.4 DISPLAY_IVMO_LINK Command

Purpose

This command displays the link between an IVMO and an NRTS or RNSAP.

It displays:

• which IVMO is attached to a given NRTS or RNSAP,

• which NRTS or RNSAP is attached to a given IVMO.

Syntax

{ DISPLAY_IVMO_LINK }{ }{ DPLKIVMO }

FCP_NAME = EAxx

{RTS = char8 } {IVMO = char8 } {RNSAP = char8}



RTS This identifies the RTS whose attached IVMO is to bedisplayed. It is a string of 8 characters. RTS, IVMO,and RNSAP are mutually exclusive.

IVMO This identifies the IVMO whose links are to bedisplayed. It is an 8 character giving the name of theIVMO. IVMO, RTS, and RNSAP are mutuallyexclusive.

RNSAP This identifies the Remote NSAP whose attachedIVMO is to be displayed. It is a string of 8 characters.RNSAP, IVMO, and RTS are mutually exclusive.


5-90 47 A2 94UC

EXAMPLES:

DPLKIVMO FCP_NAME=EA92 IVMO = IVMO_DF;

displays:

NC54 command : DPLKIVMO response from EA92NC58 RTS BCA2NCC9 IVMO : IVMO_DF RTS BCA2NCC8 IVMO : IVMO_DF RNSAP BCC1 IVMO : IVMO_DFNC54 command : DPLKIVMO command completed

DPLKIVMO FCP_NAME=EA92 RTS=BCA2NCC9;

displays:

NC54 command : DPLKIVMO response from EA92NC58 RTS BCA2NCC9 IVMO : IVMO_DFNC54 command : DPLKIVMO command completed

DPLKIVMO FCP_NAME=EA92 IVMO=IVMO1;

displays:

NC54 command : DPLKIVMO response from EA92NC54 command : DPLKIVMO IVMO : IVMO1 not linkedNC54 command : DPLKIVMO command completed❑


47 A2 94UC 5-91

5.8.5 FCP_EXTENDED_GA_TC Command

Purpose

This command displays attributes of TC (Transport Connection) objects which arenot retrieved by a DNET TC command. Only TCs of type CLNS and DIWSattached to the OCS servers are addressed by the command.

Syntax

{ FCP_EXTENDED_GA_TC }{ }{ XGATC }

TCREF = dec_5


TCREF This identifies the TC reference to which the commandapplies. It corresponds to the DSAC TC index.

EXAMPLE:

BCA2: xgatc 10249

displays:

NC54 command : XGATC response from EA81NC62 extended attributes of OCS Transport Connection : 10249 IVMO_MAME= IVMO4 STATUS= OPEN MAXRETRY = 3 NUMBF = N T1TIME = 10000 WTIME= 60000 ITIME= 180000 ACKTIME= 5000NC54 command : XGATC command completed

where,

EAxx identifies the OCS Front End on which the connection was established.

❑


5-92 47 A2 94UC

STATUS is the detailed status of the TC as follows:

CLOSEOPENCLOSING Release in progress.WFNC Wait for network connection.WFCC Wait for CC TPDU.WFR Wait for T_CONNECT response.WBCL Wait before releasing (wait for CC TPDU before

sending DR).WFNC_R Wait for network connection and re-assignment in

progress.WFCC_R Wait for CC TPDU and re-assignment in progress.WBCL_R Wait before releasing and re-assignment in progress.OPEN_R Open and re-assignment in progress.OPEN_WR Open and wait for re-assignment.CLOSING_R Release in progress and re-assignment in progress.CLOSING_W Release in progress and wait for re-assignment.WFR_WR Wait for T_CONNECT response and wait for re-

assignment.WBCL_WR Wait before releasing and wait for re-assignment.WBOC Wait before open complete (CC is unacknowledged).WBOC_WR Wait before open complete and wait for re-assignment.CLOSING_BOC Wait before open complete and release in progress.CLOSING_BOC_WR As for CLOSING_BOC plus wait for re-assignment.FREEAKWAIT Waiting for acknowledgement of CC TPDU.REFWAIT Waiting for frozen reference time.

Other parameters

Refer to the description of the TCIVMO directive in the manual GCOS 7 NetworkGeneration .


47 A2 94UC 5-93

5.8.6 LIST_FCP_TCIVMO Command

Purpose

This command lists by name and by number the IVMO declared for the OCS FrontEnd selected.

Each line of the display gives:

• the IVMO name (useful in administration and configuration commands),

• the IVMO internal number (useful in trace and connnection processing).

Syntax

{ LIST_FCP_TCIVMO }{ }{ LSIVMO }

FCP_NAME = EAxx



EXAMPLES:

LSIVMO FCP_NAME=EA92;

displays:

NC54 command : LSIVMO response from EA92NC58 IVMO# : 02 IVMO_NAME : IVMO_DF IVMO# : 04 IVMO_NAME : TO_DNS IVMO# : 03 IVMO_NAME : TO_FCPNC54 command : LSIVMO command completed❑


5-94 47 A2 94UC

5.8.7 MODIFY_FCP_TCIVMO Command

Purpose

This command modifies one or more attributes of an IVMO identified either by itsname or its internal number (as given via a LIST_FCP_TCIVMO command).

Syntax

{ MODIFY_FCP_TCIVMO }{ }{ MDIVMO }

FCP_NAME = EAxx

{IVMO_NUMBER = dec_8} { } {IVMO_NAME = char_8 }

[MAXRCRDT = dec_3]

[MAXSCRDT = dec_3]

[MAXRETRY = dec_1]

[T1TIME = dec_6]

[WTIME = dec_6]

[ITIME = dec_6]

[ACKTIME = dec_2]

[TPUSIZE = dec_4]

[EXTMODE = {Y | N}]


47 A2 94UC 5-95



IVMO_NUMBER This identifies the IVMO to which the commandapplies. It is a decimal number (8 digits) giving theinternal number of the IVMO. IVMO_NUMBER andIVMO_NAME are mutually exclusive.

IVMO_NAME This identifies the IVMO to which the commandapplies. It is a string of 8 characters giving thesymbolic name of the IVMO. IVMO_NAME andIVMO_NUMBER are mutually exclusive.

other parameters Refer to the description of the TCIVMO directive inthe manual GCOS 7 Network Generation.

EXAMPLE:

MDIVMO FCP_NAME=EA92 IVMO = IVMO_DF MAXRCRDT =10;

displays:

NC54 command : MDIVMO response from EA92NC54 command : MDIVMO command completed❑


5-96 47 A2 94UC

5.8.8 UPGRADE_FCP_CONFIG Command

Purpose

This command starts an OCS Front End incremental configuration. This enablesyou to add new remote systems and new routes to reach them without stopping/re-starting the OCS.

Refer to the description of OCS Front End configuration in the manual GCOS 7Network Generation.

Syntax

{ UPGRADE_FCP_CONFIG }{ }{ UPGRADECF }

FCP_NAME = EAxx

LIB=library-name

SUBFILE=subfile-name



LIB This identifies the cataloged SL library containingSUBFILE.

SUBFILE This identifies the subfile containing the incrementalconfiguration.


47 A2 94UC 5-97

EXAMPLES:

UPGRADE_FCP_CONFIG FCP_NAME=EA92 NB7.IPS.SL FILEOK;

displays:

NC54 command : UPGRADECF command launchedNC54 upgrade of EA92 configuration successful

UPGRADE_FCP_CONFIG FCP=EA92 NB7.IPS.SL FILEKO;

displays:

NC54 command : UPGRADECF command launchedNC60 upgrade of EA92 configuration unsuccessfulNC60 refer to report file SYS.DSACONF..EA92_CONF_RPRT❑


5-98 47 A2 94UC

❑

47 A2 94UC 6-1

6. Messages

Messages issued to the network control terminal can be:

• either network messages which appear under the following conditions:

− either as a result of commands entered by the operator

− or as requests to the operator for actions required

• or messages which are automatically redirected to the network control operator.

Messages are classified according to their type which determines the degree ofoperator intervention namely,

• information which is an acknowledgement either that the command has beenexecuted or that a normal event has occurred

• normal operation, which is a request to the operator for a specific action requiredto be done to continue operating the communications session

• error, which can be:

− either an exception condition for which operator intervention is necessary andwhich is considered recoverable

− or a system error, affecting either the hardware or software, for which a call tothe Service Center is necessary and which is considered irrecoverable.

The categories of messages appearing in the order documented, are

• time-prefixed messages, which are information and which require no operatoraction

• key-prefixed messages, the keys being a two character alphabetic identifier,followed by a code consisting of two numerics.

Where the gr4 return-code is not treated in the text of the message, refer to theMessages and Return Codes Directory.

Where the key of the message is not treated in this Section, refer to the ConsoleMessages Manual.


6-2 47 A2 94UC

The messages are classified in key ascending order, grouped by key prefix:

CA (CSA) Communication server administration

CC Communication Control

CD (CDH) Communication directory handler

FE (FECM) Front-end and controller management

FR (FEPS) Front-end processor subsystem

NA (NAD) Network administration

NC OCS driver

NG (NG) Network generation

QC Communication queue control

TF TNS/FEPS Transport and front-end subsystems

TP (TNS) Transport and network subsystem

These messages complement GCOS system messages which are described in themanual Console Messages.

Messages

47 A2 94UC 6-3

6.1 CA Messages

CA01 STSVR svrnm REJECTED: . NETWORK CONFIGURATION NOT AVAILABLE RUN NETWORK GENERATION UTILITY (01) . COMMUNICATION SHUTDOWN RUNNING RETRY COMMAND LATER (02)

Meaning

Follows a STSVR command.

(01) The network configuration for the specified server is not available.

(02 The last server is in its termination phase.

Action

(01) Run the NETGEN utility to provide the network configuration for thespecified server.

(02) Re-enter the command later. If the STSVR command is still rejected callthe Service Center.


6-4 47 A2 94UC

CA02 STSVR svrnm REJECTED: . UNKNOWN SERVER NAME svrnm (01) . INVALID NODE NAME ndnm (02) . INVALID CONTROLLER NAME ctlnm (03)

Meaning

Follows an STSVR command.

(01) The server specified in the STSVR command has not been configured bythe previous Network Generation.

(02) The Node specified in the STSVR command has not been configured bythe previous Network Generation.

(03) The Controller specified in the STSVR command has not beenconfigured by the previous Network Generation.

Action

(01 - 03) Re-enter the STSVR command specifying the correctname for a configured server, controller or node.

CA03 STSVR svrnm PROCESSING FAILED: gr4

Meaning

Follows a STSVR command. The STSVR command cannot be processed due to afailure in GCOS system services.

Action

If the same problem persists, Initialize System Load at the Console or rerun theNETGEN utility. If unsuccessful, call the Service Center.

Messages

47 A2 94UC 6-5

CA04 GCOS ERROR; INVALID SERVER STATE

Meaning

A GCOS System internal error has occurred during the processing of CSA.

Action


CA05 WARNING: ACTIVATING ASF FAILED: gr4

Meaning

Follows the startup of the first communications server. The failure in GCOSsystem services has prevented ASF being activated for:

a) Datanet or CNP 7 in-line test from a library on DPS 7000

b) Datanet Remote load/Dump/SYSGEN support

c) CNS 7 system generation.

Action

So long as the ASF Service is not required for the Datanet or CNP 7, CSA can stillcontinue to function but in degraded mode.

To resolve the problem:

a) terminate all communications servers, then restart them

b) if unsuccessful, Initialize System Load at the console or run theNETGEN utility.

If the problem still persists, call the Service Center.


6-6 47 A2 94UC

CA06 SERVER svrnm SEMAPHORE { COUNT | LINK } OVERFLOW

Meaning

Follows a TTSVR command. Because of a lack of resources, the specified servercannot be notified of the TTSVR command whether OPTION=WEAK orOPTION=STRONG.

Action

First terminate the server through OPTION=ABORT and start again. Ifunsuccessful, Initialize System Load at the Console or run the NETGEN utility. Ifthe same problem still persists, call the Service Center.

CA07 VIRTUAL PROCESS SEMAPHORE { COUNT | LINK } OVERFLOW

Meaning

Follows a STSVR, TTSVR command or the termination of a communicationsserver. Because of a lack of resources, CSA cannot execute the command orterminate the server.

Action

Initialize System Load at the Console or run the NETGEN utility. If unsuccessful,call the Service Center.

CA08 VIRTUAL PROCESS NOTIFICATION TO IOF, RBF OR SYSIN FAILED

Meaning

Follows the startup of the first communications server. Because of a lack ofresources, the GCOS services, as indicated in the message, cannot be started.

Action

Terminate all communications servers, then restart them. If the problem persists,Initialize System Load at the Console or run the NETGEN utility. If unsuccessful,call the Service Center.

Messages

47 A2 94UC 6-7

CA09 ADMINISTRATIVE COMMUNICATION SERVER TABLE OVERFLOW

Meaning

Follows a STSVR command. Because of a lack of resources, CSA cannot start thespecified server.

Action

Initialize System Load at the Console or run the NETGEN utility. If unsuccessful,call the Service Center.

CA10 LAUNCHING svrnm . BY OPERATOR COMMAND FAILED : gr4 (01) . BY FRONT_END REQUEST FAILED : gr4 (02) . FOR ASF SERVICE FAILED : gr4 (03) . IN AUTOMATIC MODE FAILED : gr4 (04) . IN RESTART MODE FAILED : gr4 (05) . BY SYSTEM INIT REQUEST FAILED : gr4 (06) . BY TNS SERVER FAILED : gr4 (07)

Meaning

The command syntax and semantics have been successfully validated, but thespecified server cannot be started because of a failure in GCOS System Services.

(01) Follows a STSVR command.

(02) Follows a RIM from the Datanet.

(03) Follows a request for GCOS ASF Service from the Datanet or CNP 7.

(04) Follows the termination of FECM and the subsequent startup of FEPS,and vice versa.

(05) Follows the termination and the restart of FEPS.

(06) Follows a start server request during System Initialisation.

(07) Follows a request from TNS to start FECM for managing the LCT (LNA)or RCT (CNP 7).

Action

Restart the Server. If the problem recurs, Initialize System Load at the Console orrun the NETGEN Utility. If unsuccessful, call the Service Center.


6-8 47 A2 94UC

CA11 svrnm CANNOT BE STARTED. . SERVER ALREADY ACTIVE (01) . NODE:ndnm BUSY BY OTHER SERVER (02) . SERVER: svrnm1 NOT STARTED; START svrnm2 (03) . SERVER JOB CLASS:jclass NOT STARTED;START JOB CLASS (04) . CONTROLLER: ctlrnm HELD; RELEASE CONTROLLER (05) . SERVER svrnm3 TERMINATING (06)

Meaning

Follows an STSVR command.

(01) The specified server is already started and active.

(02) An FEPS or FECM occurrence is already executing for the specifiednode.

(03 FECM cannot be started to administer the LCT (LNA) or RCT (CNP 7)because TNS has yet to be started.

(04) The communications server jobclass is not started.

(05) FECM cannot be started to administer the Datanet because the PSI(CCnn) is HELD.

(06) A prior occurrence of the specified server in its termination phase.

Action

(01) No action.

(02) Terminate the other server if required.

(03) Start TNS.

(04) Start communications server jobclass S (GCL: SLD CLASS=S)

(05) Release the PSI (CCnn) for the Datanet. (GCL : RDV psi_ctrl_name)

(06) Re-enter the STSVR command later.

Messages

47 A2 94UC 6-9

CA12 svrnm . CANNOT BE TERMINATED; SERVER NOT STARTED (01) . CANNOT BE TERMINATED; SERVER svrnm TERMINATING (02) . TERMINATION ALREADY REQUESTED (03)

Meaning

(01) The specified server is not started.

(02) The specified server is in its termination phase, that is, somecorrespondents have yet to close down their sessions.

(03) The termination of the specified server (with same OPTION) has alreadybeen requested.

Action

(01) No action.

(02) Try to close the active sessions. If the problem persists, Initialize SystemLoad at the console. If still unsuccessful, call the Service Center.

(03) Re-enter a TTSVR command with OPTION={STRONG|ABORT} ifrequired.

CA13 exception in TASKM jnb . pnb AT ADDRESS address

Meaning

An exception has occurred during CSA processing.

Action

If the same problem recurs, Initialize System Load at the Console or rerun theNETGEN utility. If unsuccessful, call the Service Center.


6-10 47 A2 94UC

CA14 GCOS ERROR; INVALID SEMAPHORE MESSAGE: semaphore

Meaning

An invalid service request has been addressed to CSA.

Action

If the problem recurs, call the Service Center.

CA15 NO SERVER CAN BE LAUNCHED: NETWORK CONFIGURATION NOT AVAILABLE.RUN NETWORK GENERATION UTILITY

Meaning

A RIM from the Datanet cannot be processed because the Network Configurationis not available for starting up FECM.

Action

Run the NETGEN Utility to provide the network configuration required for FECM.

CA16 LAUNCHING SERVER FAILED: gr4

Meaning

Follows a request to start a server. The request cannot be processed because of afailure in GCOS system services.

Action

If the problem recurs, Initialize System Load at the Console or run the NETGENutility. If unsuccessful, call the Service Center.

Messages

47 A2 94UC 6-11

CA17 TERMINATING svrnm FAILED: gr4

Meaning

Follows a TTSVR command. A TTSVR command cannot be processed because ofa failure in GCOS System Services.

Action

If the problem recurs, Initialize System Load at the Console or run the NETGENUtility. If unsuccessful, call the Service Center.

CA18 TERMINATING SERVER FAILED: gr4

Meaning

Follows a TTSVR command. A TTSVR command cannot be processed because ofa failure in GCOS System Services.

Action

If the same problem recurs, Initialize System Load or rerun the NETGEN utility. Ifunsuccessful, call the Service Center.

CA19 TTSVR svrnm REJECTED: . NETWORK CONFIGURATION NOT AVAILABLE RUN NETWORK GENERATION UTILITY (01) . COMMUNICATION SHUTDOWN RUNNING RETRY COMMAND LATER (02)

Meaning

Follows a TTSVR command.

(01) The Network Configuration for the specified server is not available.

(02) The last communications server is in its termination phase.

Action

(01) Run the NETGEN Utility to provide the network configuration for thespecified server.

(02) Re-enter the command later. If the problem recurs, call the ServiceCenter.


6-12 47 A2 94UC

CA20 svrnm LAUNCHED . BY { FRONT-END | SYSTEM INIT } REQUEST . BY OPERATOR COMMAND . BY SERVER: svrnm1 . FOR ASF SERVICE . IN { AUTOMATIC | RESTART } MODE

Meaning

The specified server has been successfully started up by the GCOS JobManagement Service.

Action

None.

CA21 svrnm . STARTED (01) . COMPLETED (02)

Meaning

(01) The specified server is now started and active.

(02) The specified server has now completed and can be restarted.

Action

None.

Messages

47 A2 94UC 6-13

CA22 TTSVR svrnm REJECTED : . UNKNOWN SERVER NAME svrnm1 (01) . INVALID NODE NAME ndnm (02) . INVALID CONTROLLER NAME ctnm (03)

Meaning

Follows a TTSVR command.

(01) The specified server has not been configured in a previous NetworkGeneration.

(02) The specified Node has not been configured in a previous NetworkGeneration.

(03) The specified Controller has not been configured in a previous NetworkGeneration.

Action

Re-enter the TTSVR command correctly, specifying a valid (configured) server,node or controller.

CA23 TTSVR svrnm PROCESSING FAILED: gr4

Meaning

Follows a TTSVR command. The TTSVR command cannot be processed becauseof a failure in GCOS System Services.

Action

If the same problem recurs, Initialize System load at the Console or rerun theNETGEN Utility. If unsuccessful, call the Service Center.


6-14 47 A2 94UC

CA24 MDTSVR svrnm REJECTED: . NETWORK CONFIGURATION NOT AVAILABLE RUN NETWORK GENERATION UTILITY (01) . COMMUNICATION SHUTDOWN RUNNING RETRY COMMAND LATER (02)

Meaning

Follows a MDTSVR command.

(01) The network configuration for the specified server is not available.

(02) The last server is in its termination phase.

Action

(01) Run the NETGEN utility to provide the network configuration for thespecified server.

(02) Re-enter the command later. If the MDTSVR command is still rejectedcall the Service Center.

CA25 MDTSVR svrnm REJECTED: . UNKNOWN SERVER NAME svrnm (01) . INVALID NODE NAME ndnm (02) . INVALID CONTROLLER NAME ctlnm (03)

Meaning

Follows an MDTSVR command.

(01) The server specified in the MDTSVR command has not been configuredby the previous Network Generation.

(02) The node specified in the MDTSVR command has not been configuredby the previous Network Generation.

(03) The controller specified in the MDTSVR command has not beenconfigured by the previous Network Generation.

Action

(01 - 03) Re-enter the MDTSVR command specifying thecorrect name for a configured server, controller ornode.

Messages

47 A2 94UC 6-15

CA26 MDTSVR svrnm PROCESSING FAILED: gr4

Meaning

Follows a MDTSVR command. The MDTSVR command cannot be processed dueto a failure in GCOS system services.

Action


CA27 DTSVR REJECTED: NETWORK CONFIGURATION NOT AVAILABLE RUN NETWORK GENERATION UTILITY

Meaning

Follows a DTSVR command. The network configuration for the specified server isnot available.

Action

Run the NETGEN utility to provide the network configuration for the specifiedserver.

CA28 MDTSVR svrnm COMPLETED

Meaning

The specified server has been modified successfully.

Action

None.


6-16 47 A2 94UC

6.2 CC Messages

CC03 message . RETRY LATER (01) . COMPLETED (02)

Meaning

(01) A previous command from a user application to the QMON server is stillbe acted upon.

(02) The command from a user application to the QMON server has beenexecuted successfully.

Action

(01) Wait for the current command to execute before resubmitting thecommand.

(02) None.

Messages

47 A2 94UC 6-17

6.3 CD Messages

CD01 exception IN TASKM jnb pnb AT ADDRESS address

Meaning

A fatal incident has occurred in Communication Directory Handler services.

Address is the instruction address within CommunicationDirectory Handler services where the incidentoccurred.

jnb and pnb are the process numbers of the caller which made arequest to Communication Directory Handler.

Action

Call the Service Center.


6-18 47 A2 94UC

6.4 FE Messages

FE01 sitenm action STARTED FROM SCENARIO scenario VERSION version

Meaning

Indicates that an FECM server is started to manage a Datanet, a CNP7, a MainWay2600LE or an LCT (ISL) defined by sitenm. The administrative functions aredescribed in the part of scenario defined by action.

For the LCT, no scenario exists and the action itself defines the administrativefunctions required.

For a Datanet, a CNP 7 or a MainWay 2600LE, version indicates the softwarerelease of sitenm.

Action

None.

FE02 sitenm action COMPLETED

Meaning

The FECM server which was running to process administrative functions describedin action for a Datanet, a CNP7, a MainWay 2600LE or an LCT (ISL) hascompleted successfully.

Action

None.

FE03 sitenm action ABNORMALLY TERMINATED

Meaning

The FECM occurrence which was executing to administer either the Datanet,CNP7 or MainWay 2600LE or the LCT (ISL) did not complete successfully.

Action

Messages

47 A2 94UC 6-19

Check other FE messages issued before this FE03 message concerning the samesitenm and check in the report listing.

FE04 sitenm site_text

Meaning

Site_text is a report issued by the sitenm concerning the administration of aDatanet, a CNP 7 or a MainWay 2600LE.

Action

None if the message is for information only. Refer to Datanet, CNP 7 or MainWay2600LE documentation for error messages.

FE05 sitenm VERSION NOT AVAILABLE: version

Meaning

The DNS or CNS 7 software release specified by the version number is invalid ordoes not exist on the site.

Action

Modify the version either in STSVR command, or in scenario subfile or TSLISTsubfile of SYS.DSACONF library.

FE06 sitenm . UNKNOWN SCENARIO: scenario (01) . NODE NOT FOUND IN SCENARIO: scenario (02) . ACTION NOT FOUND IN SCENARIO: scenario (03) . ERRORS DETECTED IN SCENARIO: scenario (04)

Meaning

(01) The scenario specified in STSVR command does not exist orSTD_SCEN has not been created.

(02) The NODE order corresponding to sitenm does not exist in the scenariospecified.

(03) The SCEN clause for the action corresponding to sitenm does not exist inthe scenario specified.


6-20 47 A2 94UC

(04) Either the part of the scenario corresponding to sitenm is incorrect or theelements referencing the scenario such as file, subfile and system namecannot be found.

Action

'01) Check if the scenario specified in the STSVR command is correct orcreate the scenario in SYS.DSACONF library.

(02) Check if the node specified for RSYS in the STSVR command is corrector modify the scenario in SYS.DSACONF library.

(03) Check if the action specified for ACTION in the STSVR command iscorrect or modify the scenario in SYS.DSACONF library.

(04) The action depends on the text given in the FECM FS39 message, seeAppendix A. Correct either the appropriate part of the scenario in theSYS.DSACONF library or the references to the scenario issued in theSTSVR command.

FE08 sitenm FILE: efn IS FULL

Meaning

Indicates that the file whose name is efn is full and cannot contain other member.

Action

Delete unwanted members in the corresponding library.

FE09 sitenm FILE PROCESSING ERROR; REFER TO LISTING gr4

Meaning

An incident occurred when processing a file during sitenm administration. gr4defines the incident.

Action

Refer to listing for a more detailed description of the problem.

Messages

47 A2 94UC 6-21

FE10 sitenm UNABLE OR NOT ALLOWED TO ACCESS file: efn

Meaning

The file specified by efn does not exist or cannot be accessed by the FECMoccurrence.

Action

Refer to listing for more information.

FE11 sitenm . UNABLE TO RESET THE CONTROLLER (01) . UNABLE TO INITIALIZE THE CONTROLLER (02)

Meaning

(01) The controller sitenm cannot be RESET before loading.

(02) The controller sitenm cannot be INITIALIZED before loading.

Action


FE12 sitenm SYSTEM ERROR gr4

Meaning

A fatal incident (indicated in gr4) has occurred during the administration of sitenmDatanet, CNP 7, MainWay 2600LE or LCT.

Action

The action depends on the value of gr4.


6-22 47 A2 94UC

FE13 sitenm . FECM ERROR PLEASE CONTACT YOUR SUPPLIER (01) . IMPLEMENTATION RESTRICTION PLEASE CONTACT YOUR SUPPLIER (02)

Meaning

(01) A fatal incident has occurred in the FECM processor.

(02) A restriction in the FECM processor has been reached

Action

Refer to listing for more information. If the incident cannot be resolved, call theService Center.

FE14 sitenm PROTOCOL . ERROR: REFER TO LISTING (01) . DENIED: REFER TO LISTING (02) . TIME OUT: REFER TO LISTING (03) . ERROR, TOO LARGE RECORD: REFER TO LISTING (04)

Meaning

(01) A error occurred during communication protocol between FECM and thesitenm.

(02) Communication dialog was not acknowledged successfully by thesitenm.

(03) A timeout has occurred because the sitenm no longer maintains dialog.

(04) A record from a GCOS 7 file is too large or the file name which wasspecified is wrong; or a record from a remote system is too large.

Messages

47 A2 94UC 6-23

Action

Refer to listing for more information.

(01)-(03)If the protocol incident cannot be bypassed, call the Service Center.

(04) If the record belongs to a file created or modified by the user, split therecord into smaller records.

If the file specified was incorrect, change the file name.If the incident recurs, call the Service Center.If the record comes from a remote system, call the Service Center.

FE15 sitenm . UNABLE TO ESTABLISH CONNECTION WITH MAILBOX: mbxnm (01) . CONNECTION INTERRUPTED WITH MAILBOX: mbxnm (02) . ERROR DURING CONNECTION WITH MAILBOX: mbxnm (03)

Meaning

(01) The connection with mailbox mbxnm cannot be established for sitenmadministration.

(02) The dialog with mailbox mbxnm has been interrupted during sitenmadministration.

(03) A fatal incident has occurred during sitenm administration.

Action

Refer to listing for more information. The action depends on the error messagesprinted in the listing.


6-24 47 A2 94UC

FE16 sitenm UNABLE TO ALLOCATE PSI: . CL { HELD OR ALLOCATED | NOT CONNECTED IN SRST } . LACK OF CL IN SRST . LCT HELD OR ALLOCATED . LCT { NOT CONNECTED | UNKNOWN } IN SRST . NO CL IN SRST

Meaning

The PSI of the sitenm Datanet cannot be allocated to FECM for sitenmadministration.

Action

The action depends on the reason of allocation rejection specified in the secondpart of the message.

FE17 sitenm DUMP BEGINS IN SUBFILE: sfn

Meaning

A dump of the memory image of sitenm Datanet, CNP 7, MainWay 2600LE orLCT is being taken in the sfn member of SYS.DSADUMP library.

Action

None.

FE18 sitenm DUMP AVAILABLE IN SUBFILE : sfn

Meaning

A dump of the memory image of sitenm Datanet, CNP 7, MainWay 2600LE orLCT has completed successfully in the sfn member of SYS.DSADUMP library.

Action

None.

Messages

47 A2 94UC 6-25

FE19 sitenm PROCESSING INTERRUPTED . BY TNS SERVER (01) . BY FRONT-END REQUEST (02)

Meaning

(01) TNS server has detected an incident and requests that the FECMprocessor terminates current processing.

(02) An error has occurred on the Datanet (possibly a SYSERR) duringadministration.

Action

(01) Refer to the messages previously issued by TNS server to check thecause of the abnormal termination.

(02) Refer to the SYSERR issued by the Datanet to check the cause of theabnormal termination.

Reload the Datanet memory image.

FE20 CONNECTION CANNOT BE ESTABLISHED : text

Meaning

The connection cannot be established to:

• either TNS for the administration of a CNP 7 or an LCT• or a $NOI or $DEBUG application of the Datanet, CNP 7 or MainWay 2600LE.

NOTE:$DEBUG is reserved for maintenance purposes only, see the EDD command.

Action

The text in the message indicates the intervention required.


6-26 47 A2 94UC

FE21 sitenm DNS VERSION NOT AVAILABLE FOR LOCAL DUMP : version

Meaning

The local DNS dump is not supported:

• either because the Datanet model is not configured with the local disk (diskette)• and/or the DNS version is not DNS V4U0.

NOTE:This message is for information only. The dump of the Datanet concerned willbe taken in the SYS.DSADUMP library in a file whose name contains the node-name of the Datanet.

Action

None for the operator. To avoid recurrence of the same message, thenetwork/system administrator should remove the -LC parameter from the DUMPorder in the SCENARIO of the Datanet concerned.

FE30 sitenm mbxnm CONNECTION REJECTED, TOO MANY ACTIVE CONNECTIONS; DISCONNECT UNUSED CONNECTIONS

Meaning

Too many connections to $NOI and $DEBUG are active on the FECM server forpassthrough processing.


Action

Display the state of all connections with EDD DISPLAY command, and thendisconnect unused connections with EDD DISCONNECT command.

Messages

47 A2 94UC 6-27

FE31 sitenm mbxnm UNKNOWN PARAMETER verb IN COMMAND; THE COMMAND IS IGNORED

Meaning

A discrepancy exists between the EDD command and the FECM server forpassthrough processing.

Action

Do not use the parameter of the EDD command which leads to an error. Call theService Center.

FE32 sitenm mbxnm IS NOT CONNECTED; THE COMMAND IS IGNORED

Meaning

The connection to the sitenm $NOI or $DEBUG application was not yetestablished before the command was sent.


Action

To connect to sitenm mailbox, issue EDD CONNECT PASSWORD=xxxx.


6-28 47 A2 94UC

FE33 sitenm mbxnm CONNECTION IN PROGRESS; RETRY COMMAND LATER

Meaning

The connection to sitenm $NOI or $DEBUG application is not yet completed.


Action

Wait for the completion of the connection before reissuing the command.

FE34 sitenm mbxnm DISCONNECTION IN PROGRESS; THE COMMAND IS IGNORED

Meaning

Disconnection from sitenm $NOI or $DEBUG application has been requested.


Action

Wait for the disconnection to complete before reconnecting.

Messages

47 A2 94UC 6-29

FE35 sitenm mbxnm ALREADY CONNECTED; THE COMMAND IS IGNORED

Meaning

An attempt was made to connect to sitenm $NOI or $DEBUG application althoughthe connection is already established.


Action

None.

FE36 sitenm mbxnm IS BUSY BY PREVIOUS COMMAND; RETRY COMMAND LATER

Meaning

The previous command issued to sitenm $NOI or $DEBUG application has not yetcompleted.


Action

Wait for completion of the previous command before reissuing the currentcommand.


6-30 47 A2 94UC

FE37 FECM SERVER IS ALREADY ACTIVE FOR EDD PROCESSING; THE COMMAND IS REJECTED

Meaning

An EDD START command was issued to start FECM to process passthroughalthough FECM is already active.

Action

None.

FE38 sitenm mbxnm IS DISCONNECTED BY SITE REQUEST

Meaning

The connection to sitenm $NOI or $DEBUG application has been deactivated bythe sitenm Datanet, CNP 7 or MainWay 2600LE.


Action

Check the state of the site.

FE39 NO ACTIVE CONNECTION

Meaning

Response to EDD DISPLAY command. FECM for passthrough processing isinactive because all connections to it have terminated or no request has beenissued.

Action

None.

Messages

47 A2 94UC 6-31

FE40 sitenm mbxnm . BUSY BY COMMAND IN PROGRESS . { CONNECTED | CONNECTION IN PROGRESS } . DISCONNECTION IN PROGRESS . NOT CONNECTED

Meaning

Response to EDD DISPLAY command giving the state of each sitenm $NOI or$DEBUG application.


Action

None.

FE41 FECM STARTED FOR ENTER_DSA_DIALOG

Meaning

FECM has been activated by EDD command to process passthrough.

Action

None.

FE42 FECM COMPLETED FOR ENTER_DSA_DIALOG

Meaning

FECM has completed processing passthrough.

Action

None.


6-32 47 A2 94UC

FE43 NO MORE DIALOG WITH ENTER_DSA_DIALOG FECM IS STOPPED

Meaning

Since FECM has not processed passthrough for at least an hour, it is inactive andtherefore, has terminated.

Action

None.

FE44 sitenm mbxnm

Meaning

Beginning of a response from sitenm $NOI or $DEBUG application.

The response itself immediately follows this message and is edited as a group oflines which are not interspersed with other messages. The response can containmore than one such message with text following.


Action

None.

Messages

47 A2 94UC 6-33

FE45 sitenm mbxnm CONNECTION IS ESTABLISHED

Meaning

The connection to sitenm $NOI or $DEBUG application in either the Datanet,CNP 7 or MainWay 2600LE, requested by an EDD CONNECT command, hassuccessfully completed.


Action

None.

FE46 sitenm mbxnm CONNECTION CANNOT BE ESTABLISHED: BYTE2="byte2"X, BYTE3="byte3"X

Meaning

The connection to sitenm $NOI or $DEBUG application in either the Datanet,CNP 7 or MainWay 2600LE, requested by an EDD CONNECT command, hasfailed. The reasons for rejection are specified in byte2 and byte3 of the message.


Action

Refer to corresponding Datanet, CNP 7 or MainWay 2600LE documentation tofind the meaning of byte2 and byte3 rejection reasons.


6-34 47 A2 94UC

FE47 sitenm mbxnm IS DISCONNECT

Meaning

The disconnection from sitenm $NOI or $DEBUG application in either theDatanet, CNP 7 or MainWay 2600LE, requested by an EDD DISCONNECTcommand, has completed successfully.


Action

None.

FE48 "free text"

Meaning

This is the last message of a group of messages like that described in the FE44message above.

Action

None.

Messages

47 A2 94UC 6-35

6.5 FR Messages

FR01 FROM SERVER feps-name : . I/O ERROR - HARDWARE CHECK - PARITY ERROR ON { NML | PSI } - OPERATIONAL CHECK - UNKNOWN ERROR . UNKNOWN ERROR { CAUSING PROGRAM CHECK | ON PSI } . UNKNOWN I/O ERROR [ CAUSING DATER ]

Meaning

A failure probably hardware has induced an I/O error.

Action

Release all the devices (CCnn and associated CLii) which have become HELD.Restart FEPS. Run the job PRLOG (SYS.RO.SLLIB) and call the Service Center.

If FEPS does not restart, analyze the new message. If the message is the same,hold the CCnn, power off/on the Datanet, release the CCnn and retry. If theproblem persists, call the Service Center.

FR01 FROM SERVER feps-name : LOGICAL CHANNELS DIFFERENTLY CONFIGURED ON DN AND DPS 7

Meaning

The parameter(s) MAXCH and/or MAXINCH in the NETGEN LCT directive arenot consistent with the values for DNS.

If these parameters are inconsistent, either rerun the NETGEN utility or correct theDNS version. If these parameters are correct and consistent, call the ServiceCenter.


6-36 47 A2 94UC

FR01 FROM SERVER feps-name : I/O ERROR - DATANET I/O STOP RECEIVED

Meaning

DNS has decided to stop using the PSI since the survey timer in the Datanet hasgone down.

Action

The timer in the NETGEN LCT directive must be consistent with the equivalentassociated DNS parameter.

Check the units of the parameters in the LCT and TS (DNS) directives.

Correct either the NETGEN value or the DNS value. If the values are consistent,call the Service Center.

FR01 FROM SERVER feps-name : I/O ERROR . ERRONEOUS COMMAND FROM { DPS 7 | DATANET } . INVALID MEMORY ADDRESS ON DATANET . IOCAN FROM DPS 7 . READ BUFFER TOO SHORT ON DPS 7

Meaning

(01) If the message mentions DPS 7, the most probable cause is an error inFEPS or GCOS.

(02) If the message contains the mention DATANET, the most probable causeis an error in DNS.

Action

Perform the following:

• run the job PRLOG (SYS.RO.SLLIB)• take a dump of FEPS (01) or the Datanet (02), as appropriate• then contact the Service Center.

Messages

47 A2 94UC 6-37

FR02 FROM SERVER feps-name : . NO LOGICAL CHANNEL CONFIGURED IN SRST . NOT ENOUGH LOGICAL CHANNELS CONFIGURED IN SRST . PSI CONTROLLER NOT CONFIGURED IN SRST

Meaning

• Either the CCnn identifying the LCT does not exist in the firmware generation• Or insufficient CLiis have been declared for the named LCT at firmware

generation.

Action

Confirm the message by the following:

• Either enter the command DC CCnn to display the network resourceconfiguration

• or/and run the job LSRST to check the devices declared in the firmwaregeneration.

The MAXCH value in the NETGEN LCT directive must be less than or equal to 1+ the total number of CCiis configured.

Correct MAXCH and rerun the NETGEN utility or, if the problem is the firmwaregeneration, call the Service Center.


6-38 47 A2 94UC

FR02 FROM SERVER feps-name : { LOGICAL CHANNEL | PSI CONTROLLER } . HELD OR ALREADY ALLOCATED (01) . NOT CONNECTED IN SRST (02)

Meaning

(01) One of the following conditions has occurred:- either a CCnn or CLii is HELD (verify with DC CCnn or DC Cli command)- or the CCn or CLii is allocated to another activity.

(02) One of the following reasons applies:- at firmware generation, a CCn or a CLii has been declared NOT CONNECTED (status represented by C in the job LSRST)- or at DPS 7000 hardware initialization, the CCnn was powered down- or the PSI cable has developed a malfunction.

Action

(01) Try and release the component with the command RDV CCn or CLii. Ifunsuccessful, wait for the activity using the resource to terminate beforeproceeding.

(02) If the Datanet was not powered up at INIT, switch it on and enter theRDV CCnn command.

If unsuccessful, Initialize System Load the DPS 7000.

Messages

47 A2 94UC 6-39

FR02 FROM SERVER feps-name : . ERROR ON - ALLOCATE DEVICE - CPDEF PRIMITIVE - DEALLOCATE DEVICE - GDLDN - GET SRST - GISRST - I/O PRIMITIVE - TIMER PRIMITIVE . FEPS BUFFER POOL ERROR

Meaning

A device management system primitive has sent an unexpected return code toFEPS due to either of the following messages being ignored at Initialize SystemLoad:

• REQUESTING NEW INIT because of a new firmware generation• REQUESTING TO PERFORM CONFIG because of a new SRST.

Action

If unable to perform either corrective action and to restart FEPS, call the ServiceCenter.

FR02 FROM SERVER feps-name : . FAULT BUFFER ID FROM ASAM . ILLEGAL ACTION CODE IN FEPS . QUEUEING PROCESSOR ERROR . UNKNOWN EVENT RECEIVED

Meaning

A unrecoverable error has occurred and has been identified.

Action

Take a dump of the Datanet and keep the JOR with the operator log. Call theService Center.


6-40 47 A2 94UC

FR02 FROM SERVER feps-name : DATANET FAILED

Meaning

One of either events has occurred after FEPS has been started:

• either the Datanet did not respond to a START command sent by FEPS• or the watchdog timer declared for the Datanet (T3 of CH directive) is

inconsistent with that declared for the DPS 7000 (WATCH of LCT or DEFdirective).

Action

Check if the Datanet is still functional to connect to the $NOI application anddisplay the state of the CT mapped on the PSI. If the Datanet is usable, performeither of the following :

• If the CT is DOWN or LOCK, set its state to ENBL• If the CT has failed, take a dump of the Datanet and reload it• If the PSI watchdog timer values are inconsistent, correct one of the values, as

applicable.

FR02 FROM SERVER feps-name : ILLEGAL COMMAND . ON DO . RECEIVED ON DI

Meaning

As in message text

Action

Take a dump of the Datanet and reload it. Call the Service Center.

Messages

47 A2 94UC 6-41

FR02 FROM SERVER feps-name : . INCONSISTENT CONFIGURATION ON DI/DO IN DPS 7 AND DN . LOGICAL CHANNELS WRONGLY ASSIGNED

Meaning

An inconsistency has occurred between the parameters in the NETGEN LCTdirective and the equivalent associated DNS parameters.

Action

The parameter values for NETGEN and DNS must be consistent. If not, correctone or both configurations, as required.

FR03 FROM SERVER feps-name : . ERROR ON - A MODIFY_RESUME PRIMITIVE - A RESUME PRIMITIVE - ACTIVATE WORKSTATION - BUFFER POOL OPENING - CPEXEC PRIMITIVE - CQST PRIMITIVE - EATTN PRIMITIVE - FILE OPENING - H_TIME PRIMITIVE - IOCAN PRIMITIVE - SETOPT PRIMITIVE - TSTART PRIMITIVE . ERROR WHEN - CREATING { P0 | P1 | P2 } SEMAPHORE - EXECUTING { DSAC | SYSTEM | TRACE } PRIMITIVE - OPENING QUEUE PROCESSOR - READING J NUMBER - STARTING PROCESS { P1 | P2 } - USING LOGICAL CHANNEL . NO START JOB OPTIONS GIVEN BY CSA

Meaning

As in message text.

Action



6-42 47 A2 94UC

FR03 FROM SERVER feps-name : DATANET IN SYSERR OR NOT LOADED

Meaning

A RIM notification has been received by FEPS from the Datanet. The Datanetsends a RIM when requesting to be loaded either when first powered up or when aSYSERR has occurred.

Action

None.

However, the operator must ensure that all files needed to load the Datanet arepresent and online. FECM is started without operator intervention and whencompleted, FEPS is restarted.

FR03 FROM SERVER feps-name : ILLEGAL COUPLE STATE EVENT

Meaning

A irrecoverable protocol error has occurred.

Action

Take a dump of the Datanet, and keep the JOR and operator log. Call the ServiceCenter.

FR03 FROM SERVER feps-name : NO PSI AVAILABLE

Meaning

All the PSIs in the LCT list declared in the NETGEN SVR directive are notfunctional.

Action

Use the DC command to display the devices. If HELD, use the RDV command torelease them. If successful, restart FEPS.

Messages

47 A2 94UC 6-43

FR03 FROM SERVER feps-name : READY ATTENTION RECEIVED

Meaning

The Datanet has notified FEPS that it is operational.

Action

None.

FR04 FROM SERVER feps-name : STOP RECEIVED FROM DN

Meaning

The Datanet has notified FEPS that it is no longer operational.

Action



6-44 47 A2 94UC

FR05 FROM SERVER feps-name:. WATCHDOG TIMERS ARE DIFFERENT IN DPS7 AND DN ON CH lcendpt (01). INCOHERENT CONFIGURATIONS ON DI/DO IN DPS7 AND DN ON CH lcendpt (02). I/O COMPLETION CODE iocc IS RECEIVED ON CH lcendpt (03). A PROBLEM HAS APPEARED AT ADDRESS: address :DUMP AND TRACE COULD BE GENERATED (04). CT/CH lcendpt IS NOT IN AN AVAILABLE STATE (05). CT/CH lcendpt,lcendpt2 ARE NOT IN AN AVAILABLE STATE (06). MUTUAL SURVEY IS SUSPENDED ON CH lcendpt (07). STOP SURVEY IS NOT ALLOWED FOR DNS RELEASE PREVIOUS TO V4 ON CH lcendpt (08)

Meaning

(01 - 02) The configuration parameters in the DPS 7000 andDatanet generations do not match.

(03) I/O error received on the PSI(04) irrecoverable software error(05 - 06) The PSI is not available.(07) Survey is suspended between FEPS and the Datanet.(08) Survey cannot be suspended for this DNS release.

Action

(01 - 02) Check and correct the WATCH and MAXINCHparameter values of the LCT directive in the DPS 7000NETGEN.

(03 - 04) Call the Service Center.(05 - 06) Enter the command: MDNET LCT lcendpt

NEW_STATE=ENBL.(07 - 08) none; these messages are for information only.

Messages

47 A2 94UC 6-45

6.6 NA Messages

NA10 JOURNAL STARTED ON SYS.lgnmi

Meaning

lgnm is the name of the NETGEN LG directive defining the mandatory DSALOGset of logfiles or the optional user-defined set of logfiles and i is a decimal digit.

AF ASF has started journalizing on the named logfile as a result of one of thefollowing events:

• RAEH startup through the STSVR command• switching from the previous logfile to the current logfile whose name appears in

the message• the MDNET AF DSALOG NEW_STATE=ENBL command, if AF DSALOG was

previously locked• the MDNET LG lgnm NEW_STATE=ENBL command, if LG lgnm was

previously locked, lgnm being the user-defined logfile.

Action

None.

NA11 JOURNAL SYS.lgnmi IS FULL

Meaning

lgnm is the name of the NETGEN LG directive defining the mandatory DSALOGset of logfiles or the optional user-defined logfile set and i is a decimal digit.

AF ASF has filled the named logfile and will switch to the next logfile.

Action

None.

Each time a logfile is switched, the DSALG job is automatically started up byGCOS to perform a specific task on it. No operator action is required to identifythe logfile since AF ASF passes lgnmi to the ASSIGN statement of DSALG. If theuser has not specified a job for DSALG, no system action is taken.


6-46 47 A2 94UC

NA12 SYS.lgnmi LOGFILE UNAVAILABLE gr4

Meaning

lgnm is the name of the NETGEN LG directive defining the mandatory DSALOGset of logfiles or the optional user-defined logfile set and i is a decimal digit.

AF ASF considers the named logfile unavailable and has set it to an invalid state.Journalization, however, continues on the remaining logfiles.

Action

Check the disk drive on which the volume containing the named logfile ismounted:

• if the drive is not functioning normally, remove the volume and mount it onanother drive; no further action is necessary

• if the drive is functioning normally, deallocate, then preallocate the namedlogfile. At the next RAEH session, the file will be put in a valid state and will betaken into account.

If the same message recurs in the next RAEH session, call the Service Center.

NA20 NAD INITIALIZATION FAILED gr4

Meaning

At RAEH startup, the AF NAD cannot be initialized due to an unrecoverable errordefined by the gr4 return code.

Action


NOTE:Although DSAC services are unavailable, the LNET, DNET and MDNETcommands addressing DSAC objects can be submitted and executed on thelocal system.

Messages

47 A2 94UC 6-47

NA21 LOG INITIALIZATION FAILED gr4

Meaning

At RAEH startup, the AF ASF cannot be initialized due to an irrecoverable error inthe logfile handler

Action

Call the Service Center

NOTE:Although DSAC services are not available, the LNET, DNET and MDNETcommands addressing DSAC objects can be submitted and executed on thelocal system.

NA22 NAD INTERNAL ERROR FROM aftype : reason , gr4

Meaning

An unrecoverable error has occurred during DSAC processing, where

• aftype is the name of the DSAC function, being NAD, LOG, MUX or NER• reason is a numeric value being the code of the error• gr4 defines the error return code.

Action


NOTE:Although DSAC services are not available, the LNET, DNET and MDNETcommands addressing DSAC objects can be submitted and executed on thelocal system.


6-48 47 A2 94UC

NA24 NAD SESSION ERROR : STATUS=vcam_status AF=afname REMOTE SITE=system gr4

Meaning

An irrecoverable error has occurred in the VCAM session layer either whenestablishing a connection or during the dialog:

• vcam_status gives the condition status of VCAM

• afnm is the name of the AF, being LNAD, DSALOG or LNOI

• system identifies the remote site at which the correspondent of the AF is located

• gr4 defines the error return code.

Action


Messages

47 A2 94UC 6-49

NA25 NAD OVERFLOW : ERNB=reason AF=afnm REMOTE SITE=system gr4

Meaning

An overflow has occurred for the reason given by ERNB:

• reason see Action• afnm is the name of the AF, being LNAD, DSALOG or LNOI• system identifies the remote site at which the correspondent of the AF is located• gr4 defines the error return code

Action

According to the values of ERNB, modify the values of the parameters concernedin the AG or AC network generation directives, as follows:

• ERNB=N_AGSESSOVFThe current limit for static ACs + dynamic ACs is 420. The sum of MAXSESSvalues of AGs must not exceed this limit.

• ERNB=N_ACQOVF− Check the values of the following queues:

ACs of AG RMUX : output queue=MAXCMD ACs of AG RLNOI: output queue=(2 * MAXCMD) + MAXEV input queue=MAXCMD (awaiting response) ACs of ASF type: output queue=MAXEV other ACs : output queue=MAXCMD + MAXEV

− and increase the MAXCMD or MAXEV values for this AC

• ERNB=N_REQBUFOVFThe request block pool size = current output queue + current input queue of eachAC (static and dynamic). The maximum size is 256,000. Modify theMAXCMD and MAXEV values of the AGs and ACs.

• ERNB=N_CMDOUTOVFThe MAXCMD value of the AC or its associated AG is not sufficient.

NOTE:The default values of the AGs are passed on to their associated ACs. Thesevalues can then be overridden by values explicitly declared in the AC directives.


6-50 47 A2 94UC

NA30 nnnn LOST MESSAGES DUE TO { SYSQM OVERFLOW } { NETWORK REPORTING OVERFLOW }

Meaning

An overflow has occurred in the PMOS message queue or the DSAC queue duringnetwork reporting resulting in the loss of the number of message indicated.

Action

• Either limit the flow of reported messages through the selection of the OP filters• Or set the OP state to LOCK to terminate network reporting.

NA50 LOCAL JOURNALIZATION SUSPENDED

Meaning

AF ASF cannot cope with the throughput of local administrative traffic generatedby LDSALOG (local AC NAD). The overflow of this administrative traffic is lost.

Action

If the message recurs for the session and over a number of sessions, perform thefollowing at the termination of the current session:

• restrict the throughput of administrative traffic by selective filter settings onLDSALOG

• and rerun the NETGEN utility.

If the overflow condition persists despite the new configuration, call the ServiceCenter.

NOTE:Administrative traffic is lost before it is filtered, whatever its importance(LEVEL).

AF ASF will resume local journalization without operator intervention.

Messages

47 A2 94UC 6-51

NA51 LOCAL JOURNALIZATION RESTARTED nnn RECORDS LOST

Meaning

nnn is a decimal value indicating the number of records that have been lost. AFASF has now resumed local journalization.

Action

None.

NOTE:The following 2 messages generated by LDSALOG (local AC NAD) are sent tothe logfile(s) and all remote ACs - NCC, NOI and AC ASF:

AF CONNECTION ERROR with LOSS_CNTindicating the number of records potentially lost sincethey are lost before they can be filtered; thecorrespondents mandatorily receive this message as awarning that the filtering mechanism has beenbypassed

NAD ERROR with REASONgiving the value 06/F2; the correspondents optionallyreceive this message according to their filter settings.

NA53 CONFIGURED lognm LOG FILES NOT PRESENT

Meaning

lognm is the name of the NETGEN LG directive defining the mandatory DSALOGset of logfiles or the optional user-defined logfile set.

The names logfile set has been declared in the NETGEN configuration but theassociated logfiles have not been preallocated before RAEH startup.

Action

Run the DSALOGFILE job to preallocate the missing logfile set using lognm asthe argument of the NAME parameter in the VALUES statement.


6-52 47 A2 94UC

NA54 REMOTE JOURNALIZATION SUSPENDED

Meaning

DSAC cannot cope with the remote logging of administrative traffic to the remoteACs - NCC, NOI and AC ASF, resulting in potential loss of traffic.

Action

If the message recurs for the session and over a number of sessions, call the ServiceCenter.

NA55 REMOTE JOURNALIZATION RESTARTED nnn RECORDS LOST

Meaning

nnn is a decimal value indicating the number of records that have been lost. DSAChas resumed remote journalization.

Action

None.

NOTE:The following 2 messages generated by LDSALOG (local AC NAD) are sent tothe logfile(s) and all remote ACs - NCC, NOI and AC ASF:

AF CONNECTION ERRORthe correspondents mandatorily receive this messageas warning that the filtering mechanism has beenbypassed

NAD ERROR with REASONgiving the value 06/F4: the correspondents optionallyreceive this message according to their filter settings.

Messages

47 A2 94UC 6-53

NA56 nnn RECORDS LOST FOR AC:acnm

Meaning

acnm is the name of the NETGEN AC directive identifying the NCC, NOI or ACASF.

The named remote AC cannot cope with the throughput of administrative trafficsent by the AF NAD resulting in the potential loss of traffic due to overflow fromits associated queue.

Action

If the message recurs for the session and over a number of sessions, perform thefollowing at the termination of the current session:

• increase the value of MAXEV in the AC directive concerned,• and, rerun the NETGEN utility.

If the overflow condition persists despite the new configuration, call the ServiceCenter.

NOTE:The following message generated by LDSALOG (local AC NAD) is sent to thelogfile(s) and the named remote AC:

AF CONNECTION ERROR with LOSS_CNTindicating the number of lost records; thecorrespondents mandatorily receive this message as awarning that the filtering mechanism has beenbypassed.


6-54 47 A2 94UC

NA57 REMOTE JOURNALIZATION DOWN

Meaning

DSAC has repeatedly failed to cope with remote journalization resulting in itspermanent suspension until the next DSAC session.

Action

If the message often recurs, call the Service Center.

NOTE:The following message generated by LDSALOG (local AC NAD) is sent to thelogfile(s) and all remote ACs - NCC, NOI and AC ASF:

NAD ERROR with REASONgiving the value 06/F5 : the correspondents optionallyreceive this message according to their filter settings.

Messages

47 A2 94UC 6-55

NA59 lognm LOG DOWN

Meaning

lognm is the name of the NETGEN LG directive defining the mandatory DSALOGlogfiles or the optional user-defined logfile set. The set of logfiles namesSYS.lognmi, i defining the entire range of logfiles declared, is unavailable for theduration of the current session.

Action

Terminate RAEH. Then run the DSALOGFILE job to preallocate the failed logfileset using lognm as the argument of the NAME parameter in the VALUESstatement.

NOTE:On the detection of each failed logfile of the set concerned, LDSALOG (localAC NAD) generates the following message:

- either ADMINISTRATIVE LOGFILE OPEN FAILURE

- or ADMINISTRATIVE LOGFILE CLOSE.

In either message, the REASON and SYSINFO parameters give non-zerovalues explaining the cause of the file failure.


6-56 47 A2 94UC

6.7 NC Messages

OCS Driver Messages

NC10 OCS: NO AVAILABLE NCC CONTROLLER FOUND

Meaning

No OCS Front End is currently declared in the NETGEN configuration.

Action

Include OCS Front End in the NETGEN configuration (controller of NCC type)..

NC10 OCS SERVER DISABLED

Meaning

A OCS Server has aborted. Its traffic is lost.

Action

If it is in automatic mode (that is, not AUTO = NO) , wait for it to re-startautomatically. Otherwise, re-start it manually.

NC10 OCS ALREADY STOPPING

Meaning

You have issued a TTSVR command for an OCS Server which is already stopping.This TTSVR command is ignored.

Action

Wait for the OCS Front End concerned to stop.

Messages

47 A2 94UC 6-57

NC10 OCS ISO/DSAC LOCAL ADMINISTRATION DISABLED, MAY BE ENABLED BY NEXT OCS STSVR

Meaning

The ISO/DSAC local administration process has aborted.

Action

Issue a STSVR command on an OCS Server (for an OCS Front End with anISO/DIWS configuration). This will re-start the ISO/DSAC local administrationprocess.

If the stop of the OCS Server is not desired, issue an RSTADM command.

NC10 OCS IPS LOCAL ADMINISTRATION DISABLED, MAY BE ENABLED BY NEXT OCS STSVR

Meaning

The IPS local administration process has aborted.

Action

Issue a STSVR command on an OCS Server (for an OCS Front End with an IPSconfiguration). This will re-start the IPS local administration process.

If the stop of the OCS Server is not desired, issue an RSTADM command.

NC10 OCS INIT LCT FAILURE

Meaning

There is a major error during the initialization of the LT management table. Thereis an error in the SRST and/or in the NETGEN declaration for the OCS Front End.

Action

Correct the error and then re-start the OCS server.


6-58 47 A2 94UC

NC10 OCS DRIVER SHORT OF SEMAPHORE RESOURCES

Meaning

There is not enough semaphore segment space available. The site's resources areoverloaded.

Action

Make more resources available and then re-start the OCS server.

NC10 OCS DRIVER CANNOT ACTIVATE THE PROCESS tsk_name

Meaning

The driver process "tsk-name" cannot be activated. There is a shortage of TaskManagement resources or a bad driver load-module file.

Action

Make more resources available (or correct the error) and then re-start the OCSserver.

NC10 MARKETING IDENTIFIER NOT VALID

Meaning

This site is not authorized to use the OCS Driver facility.

Action

Ask your Bull Service Center to install the necessary MI (Marketing Identifier).Then re-start the OCS server.

Messages

47 A2 94UC 6-59

NC10 OCS IPS SERVER DISABLED

Meaning

The IPS Server has failed. The OCS cannot handle any more IPS traffic.

Action

Issue a STSVR command for an OCS Front End with an IPS configuration. Thiswill re-start the IPS traffic.

OCS Server Messages

NC01 FROM SERVER svr_name : FRONT END INIT PHASE ENDED

Meaning

A fatal error occurred in the OCS Front End INIT phase. This attempt to executethe STSVR command is abandoned.

Action

Correct the error and then re-execute the STSVR command.

NC01 FROM SERVER svr_name : SERVER NOT STARTED

Meaning

Even though an OCS Server has been dumped and/or loaded correctly, it cannot beactivated. It may have a bad status, be in hardware error, or have been loaded witha bad IMA file(s). This attempt to execute the STSVR command is abandoned.

Action



6-60 47 A2 94UC

NC01 FROM SERVER svr_name : FRONT END DUMP AND/OR LOAD PHASE ENDED

Meaning

A fatal error occurred in the OCS Front End dump or load phase. This attempt toexecute the STSVR command is abandoned.

Action


NC01 FROM SERVER svr_name : NO NCC FOUND IN SRST

Meaning

There is an error in the current site SRST declarations. This attempt to execute theSTSVR command is abandoned.

Action


NC01 FROM SERVER svr_name : CANNOT ACTIVATE IO INTERFACE (SERVICE LT)

Meaning

Service Logical Terminator cannot be activated. This OCS Front End may be held,or in a bad status, or in hardware error. This attempt to execute the STSVRcommand is abandoned.

Action


Messages

47 A2 94UC 6-61

NC01 FROM SERVER svr_name : DUMP AND/OR LOAD PROCESSING NOT COMPLETED

Meaning

An I/O or a file declaration error occurred in the OCS Front End dump or loadphase. This attempt to execute the STSVR command is abandoned.

Action


NC01 FROM SERVER svr_name : IO INTERFACE FAILURE (SERVICE LT)

Meaning

An error occurred on the Service Logical Terminator. No more traffic can go viathis server. All sessions through this server are broken.

Action

If you want to re-start this server, you must correct the error and re-execute theSTSVR command. To correct the error HDV and RDV commands on relativeUCxx or LTxx are often efficient.

NC01 FROM SERVER svr_name : CANNOT ACTIVATE IO INTERFACE (ISOlikeLT)

Meaning

The ISO/DIWS traffic Logical Terminator cannot be activated. This OCS FrontEnd may be held, or in a bad status, or in hardware error. This attempt to executethe STSVR command is abandoned.

Action



6-62 47 A2 94UC

NC01 FROM SERVER svr_name : NO AVAILABLE PROTOCOLS AFTER FRONT END CONFIGURATION

Meaning

Due to severe error(s) in ISO/DIWS and/or IPS configuration file(s), no protocolsare available. This attempt to execute the STSVR command is abandoned.

Action

Read the configuration report file named <LCT name>_CONF_RPRT inSYS.DSACONF library to correct the error(s) and then re-execute the STSVRcommand.

NC01 FROM SERVER svr_name : UNAVAILABLE IPS TRAFFIC SERVER

Meaning

Even though there is a correct IPS configuration, the server handling IPS traffic hasfailed. No IPS traffic can be handled (on any OCS Front End).

Action

Correct the error and then re-execute an STSVR command on an OCS server withan IPS configuration.

NC01 FROM SERVER svr_name : FAILING ACTNOI gr4

Meaning

GCOS 7 does not accept this OCS server administrative management. The reasonis given by "gr4". This attempt to execute the STSVR command is abandoned.

Action


Messages

47 A2 94UC 6-63

NC01 FROM SERVER svr_name : IPS TRAFFIC STOPPED

Meaning

The IPS Server stops normally or abnormally its services for this OCS Front End.No new IPS traffic can go through this OCS Front End until the next STSVRcommand is issued for this OCS Front End with an IPS configuration.

Action

None.

NC01 FROM SERVER svr_name : FRONT END STOPPING

Meaning

A severe error has occurred or a TTSVR command is being executed on this OCS.No more new traffic can go via this server.

Action

None.

NC01 FROM SERVER svr_name : NO MORE TRAFFIC

Meaning

A severe error has occurred or a TTSVR command was completed for this OCS. Itis returned to enable status.

Action

None.


6-64 47 A2 94UC

NC01 FROM SERVER svr_name : UNAVAILABLE SNMP ADMINISTRATION

Meaning

Even though there is a correct IPS configuration, the SNMP administration processhas failed. No IPS SNMP administration can be done as a result of this STSVRcommand.

Action

If you want the SNMP process to restart, stop this OCS (TTSVR command) andthen execute a new STSVR command, or submit an RSTADM command if theserver stop is not desired.

NC01 FROM SERVER svr_name : WATCHDOG DELAY EXCEEDED (NG LCT WATCH)

Meaning

No response from the OCS Front End associated with this server. This may be dueto deadlock, a bad status, or a hardware error. This OCS Front End session isdropped.

Action


NC01 FROM SERVER svr_name : IO INTERFACE FAILURE (SNMP LT)

Meaning

An I/O error occurred on the SNMP Logical Terminator. No further IPS SNMPadministration can be done for this OCS Front End.

Action

If you want the SNMP process to restart, stop this OCS (TTSVR command) andthen execute a new STSVR command.

Messages

47 A2 94UC 6-65

NC01 FROM SERVER svr_name : SNMP AGENT WARNING FAILURE

Meaning

The SNMP process has detected an error leading to its abort. No further IPSSNMP administration can be done for this OCS Front End.

Action

If you want the SNMP process to restart, stop this OCS (TTSVR command) andthen execute a new STSVR command, or enter an RSTADM command.

NC01 FROM SERVER svr_name : SNMP AGENT WILL BE RECOVERED ON NEXT STSVR

Meaning

After an error, the SNMP agent process can be restarted.

Action

If you want the SNMP agent process to restart, stop this OCS (TTSVR command)and then execute a new STSVR command, or enter an RSTADM command (if theserver stop is not desired).

NC01 FROM SERVER svr_name : IO INTERFACE FAILURE (TRACE LT)

Meaning

An I/O error occurred on the stack trace Logical Terminator. No further stack traceprocessing can be done by this OCS Front End.

Action

If you want the stack trace to restart, execute a STSVR command.


6-66 47 A2 94UC

NC01 FROM SERVER svr_name : SERVER TRACE WARNING FAILURE

Meaning

The stack trace process has detected an error leading to its abort. No further stacktrace processing can be done for this OCS Front End.

Action

If you want the stack trace to restart, execute a STSVR command, or enter anRSTADM command (if the OCS server stop is not desired).

NC01 FROM SERVER svr_name : SERVER TRACE WILL BE RECOVERED ON NEXT STSVR

Meaning

The stack trace process has detected marginal conditions which prevent it fromworking.

Action

If you want the stack trace to restart, execute a STSVR command, or enter anRSTADM command (if the server stop is not desired).

NC01 FROM SERVER svr_name : ISO TRACE WARNING FAILURE

Meaning

An error occurred on the ISO/DSA trace process. No further ISO/DSA traceprocessing can be done for this OCS Front End.

Action

If you want the ISO/DSA trace process to restart, execute a STSVR command.

Messages

47 A2 94UC 6-67

NC01 FROM SERVER svr_name : ISO TRACE WILL BE RECOVERED ON NEXT STSVR

Meaning

After an error, the ISO/DSA trace process can be restarted.

Action

If you want the ISO/DSA trace process to restart, execute a STSVR command.

NC01 FROM SERVER svr_name : NETWORK CANNOT BE REACHED OR IS BROKEN DOWN

Meaning

The network is non-operational, or is becoming non-operational, or it cannot bereached by the DEvice Adaptor. This attempt to execute the STSVR command isabandoned, or this current OCS Front End session is dropped.

Action


NC01 FROM SERVER svr_name : CONNECTED TO NETWORK

Meaning

From now on, this Server (and this OCS Front End session) can handle inward andoutward traffic.

Action

None.


6-68 47 A2 94UC

NC01 FROM SERVER svr_name : WAITING FOR NETWORK

Meaning

The network is not operational at the OCS server initialization phase. The OCSserver waits for the network (to become operational).

This message can mainly appear with an FDDI access to the network.

Action

Make the network operational, or terminate the server (TTSVR command).

NC01 FROM SERVER svr_name : CONFIGURATION WARNINGS OR ERRORS: SEE REPORT FILE

Meaning

The OCS Front End configuration has resulted in one or more warning and/or errormessages. To see these messages, consult the report subfile. The report subfile isthe member named <lctname>_CONF_RPRT in the library namedSYS.DSACONF.

Action

Correct the configuration (to eliminate the errors).

NC01 FROM SERVER svr_name : ISO/DIWS PROTOCOLS AVAILABLE

Meaning

Self explanatory.

Action

None.

Messages

47 A2 94UC 6-69

NC01 FROM SERVER svr_name : IPS PROTOCOLS AVAILABLE

Meaning

Self explanatory.

Action

None.

NC01 FROM SERVER svr_name : ISO/DIWS+IPS PROTOCOLS AVAILABLE

Meaning

Self explanatory.

Action

None.

NC01 FROM SERVER svr_name : IO FAILED BY CHANNEL EXCEPTION

Meaning

Self explanatory.

Action

See the other messages that follow. Call your support.


6-70 47 A2 94UC

NC01 FROM SERVER svr_name : SHORT OF BUFFER RESOURCES. RISK OF OCS DEADLOCK OR ABORT!

Meaning

Self explanatory.

Action

Increase Buffer Resources (Size and/or Number of Buffers).

NC01 FROM SERVER svr_name : MISMATCH OR WRONG FRONT END VERSION NAME

Meaning

The given front end version is not valid on this site.

Action

Start the front end with a name of a fully installed version.

NC01 FROM SERVER svr_name : FRONT END DOES NOT START

Meaning

Lack of ressource or anomaly when starting a valid Dxyy version name on a frontend.

Action

Fix the local problem and submit again the STSVR.

NC05 FROM SERVER svr_name LOAD COMPLETED

Meaning

Self explanatory.

Action

None.

Messages

47 A2 94UC 6-71

NC05 FROM SERVER svr_name DUMP STARTED

Meaning

Self explanatory.

Action

None.

NC05 FROM SERVER svr_name DUMP COMPLETED

Meaning

Self explanatory.

Action

None.

NC05 FROM SERVER svr_name -OSI OR -IPS MUST BE GIVEN IN GO ORDER

Meaning

Self explanatory.

Action

See the scenario subfile STD_SCEN.

NC05 FROM SERVER svr_name DUMP/LOAD SEGMENT NOT AVAILABLE

Meaning

The data segment to receive the subfile record for the Load action is not available.

Action

Analyze the return codes in the message that follows.


6-72 47 A2 94UC

NC05 FROM SERVER svr_name NO MORE ENTRY IS AVAILABLE

Meaning

This subfile is already open.

Action

None.

NC05 FROM SERVER svr_name FIRST SL RECORD IS NOT A CR101

Meaning

Self explanatory.

Action

Move the SARF member to an SSF member.

NC05 FROM SERVER svr_name ILLEGAL PARAMETER WITH ADMINISTRATIVE LT

Meaning

Impossible dump or load action.

Action

Submit a STAR.

Messages

47 A2 94UC 6-73

NC05 FROM SERVER svr_name ERROR ON ADMINISTRATIVE LT

Meaning

Self explanatory.

Action

Submit a STAR.

NC05 FROM SERVER svr_name ERROR WHEN DELETE DUMP/LOAD BUFFER SEGMENT

Meaning

Mismatch in segment management.

Action

Submit a STAR.

NC05 FROM SERVER svr_name NO CONTINUATION LINE EXISTS

Meaning

The continuation line is empty (return code = DATALIM).

Action

Correct the scenario subfile STD_SCEN.


6-74 47 A2 94UC

NC05 FROM SERVER svr_name NO NAME FOUND AFTER SCEN ORDER

Meaning

Self explanatory.

Action

The name specified in the ACTION parameter of the STSVR command is not inSTD_SCEN.

NC05 FROM SERVER svr_name VERSION NUMBER MISSING/INVALID IN NODE ORDER

Meaning

Self explanatory.

Action

The version must be a 4 character string in the Nxyy or Dxyy format.

NC05 FROM SERVER svr_name INVALID (TOO LARGE?) ACTION NAME

Meaning

This name exceeds 8 characters.

Action

See the description of the STSVR command in Chapter 3.

Messages

47 A2 94UC 6-75

NC05 FROM SERVER svr_name GO ORDER NOT FOUND JUST AFTER LOAD ORDER

Meaning

GO order is not found after the LOAD order.

Action

Correct the scenario subfile STD_SCEN.

NC05 FROM SERVER svr_name VERSION NUMBER NOT FOUND IN SYS.DSACONF..TSLNCC

Meaning

The version has not been specified in the STSVR command and the TSLNCCsubfile of SYS.DSACONF is missing.

Action

You must create the TSLNCC subfile of SYS.DSACONF, at least, with just onerecord whose contents is a 4 character string in the form Nxyy or Dxyy.

NC05 FROM SERVER svr_name VERSION NUMBER NOT FOUND IN SYS.DSASLIB..TSLNCC

Meaning

Self explanatory.

Action

The TSLNCC subfile of SYS.DSASLIB must contain a list of front ends softwareversions (which have been installed on the host).


6-76 47 A2 94UC

NC05 FROM SERVER svr_name NAME MISSING AFTER KEYWORD IN SCENARIO GO ORDER

Meaning

In the GO order, the parameter -OSI<subfile1> or -IPS<subfile2> is missing orincomplete.

Action

Correct the scenario subfile.

NC06 FROM SERVER svr_name LOAD STARTED FROM VERSION: version

Meaning

Gives the version of the server software being loaded.

Action

None.

NC06 FROM SERVER svr_name UNREACHABLE FILE: file_name

Meaning

The file was not found in the list of allowed files.

Action

Correct the error.

Messages

47 A2 94UC 6-77

NC06 FROM SERVER svr_name STRUCT FILE NOT INIT: file_name

Meaning

The structure (VALID_FILE) file was not initialized (software error: file numbererror or a hardware error).

Action

Correct the error.

NC06 FROM SERVER svr_name UNKNOWN SCENARIO subfile_name

Meaning

The scenario subfile does not exist in the SYS.DSACONF library.

Action

Create the scenario subfile that defines the administrative functions for one or morefront-end processors including the OCS Front End controllers.

NC06 FROM SERVER svr_name NO NAME AFTER NODE IN: file_name

Meaning

No name parameter found after NODE order.

Action

The NODE order must contain an OCS Front End controller name. This is thename given in the LCT directive.


6-78 47 A2 94UC

NC06 FROM SERVER svr_name INVALID TYPE FOR FILE: file_name

Meaning

The file type is not SL or BIN.

Action

Check the validity of the file.

NC06 FROM SERVER svr_name NOT BIN RECORD IN: subfile_name

Meaning

The record is not a BIN control record.

Action

Correct the subfile record.

NC06 FROM SERVER svr_name INVALID BIN TYPE REC: subfile_name

Meaning

Invalid subfile type in control record.

Action

Make an SSF BIN subfile.

Messages

47 A2 94UC 6-79

NC06 FROM SERVER svr_name VERB SIZE ERROR: subfile_name

Meaning

The size of a parameter specified after an order is not correct.

Action

Correct the parameter in the scenario subfile.

NC06 FROM SERVER svr_name NODE NOT FOUND IN: file_name

Meaning

Self explanatory.

Action

Analyze the scenario subfile.

NC06 FROM SERVER svr_name ACTION NOT FOUND IN: subfile_name

Meaning

Self explanatory.

Action

Analyze the scenario subfile (STD_SCEN). The part of the scenario defined by theNODE order must contain a set of action orders.


6-80 47 A2 94UC

NC06 FROM SERVER svr_name SUBFILE NAME NOT REQUIRED subfile_name

Meaning

The parameters in the DUMP or LOAD order in the scenario subfile are notrequired.

Action


NC06 FROM SERVER svr_name INVALID NAME FOR DUMP subfile_name

Meaning

The RSYS parameter in the STSVR command does not exist or is inconsistent.The dump subfile is not created.

Action

Correct the erroneous parameter.

NC06 FROM SERVER svr_name MULTI DUMP NOT ALLOWED subfile_name

Meaning

There are several administrative DUMP orders in the same SCEN order in thescenario subfile.

Action


Messages

47 A2 94UC 6-81

NC06 FROM SERVER svr_name SCENARIO NOT AVAILABLE subfile_name

Meaning

The command (for example, GO) following the DUMP order in the scenariosubfile is inconsistent.

Action

Correct the verb (NODE, SCEN, DUMP, LOAD, or GO, for OCS Front Endscenarios) in the scenario subfile.

NC06 FROM SERVER svr_name SUBFILE NOT FOUND IN SYS.DSACONF subfile_name

Meaning

The OSI or IPS subfile containing the OCS Front End configuration for theOSI/DIWS and IPS telecommunication stack does not exist.

Action

Analyze the SYS.DSACONF library. It must contain the user subfiles for the OCSFront End configuration.

Or, correct the scenario subfile.


6-82 47 A2 94UC

NC06 FROM SERVER svr_name INVALID SL TYPE REC file_name

Meaning

Incorrect subfile type.

In the GO order, the name of the subfile must be of the form CONF<subfile>,where CONF corresponds to the SYS.DSACONF library.

Or, an error in the open subfile function. There is an incorrect subfile type inCR101.

Action

If the GO order is the cause, correct the scenario subfile.

If the subfile type is incorrect, correct it.

NC06 FROM SERVER svr_name TOO LONG VERB subfile_name

Meaning

The maximum size of a verb in the scenario subfile is exceeded.

Action

Correct the verb in the scenario subfile.

NC06 FROM SERVER svr_name HARDWARE CANNOT RUN IMA VERSION version

Meaning

Given OCS Front End software version does not fit the front end hardwareenvironment.

Action

Give a correct version name in scenario or in STSVR command

Messages

47 A2 94UC 6-83

NC07 FROM SERVER svr_name OPEN SUBFILE ERROR gr4

Meaning

An error occurred in the H_OPENS primitive.

Action

Analyze the abnormal return code gr4.

NC07 FROM SERVER svr_name CLOSE SUBFILE ERROR gr4

Meaning

An error occurred in the H_CLOSES primitive.

Action


NC07 FROM SERVER svr_name BUILD SUBFILE ERROR gr4

Meaning

An error occurred in the H_BUILD primitive during a function which checks if agiven subfile exists in the library.

Action


NC07 FROM SERVER svr_name GET DATA RECORD ERROR gr4

Meaning

An error occurred in the H_GET primitive during a get data function.

Action



6-84 47 A2 94UC

NC07 FROM SERVER svr_name GET OPEN SUBFILE ERROR gr4

Meaning

An error occurred in the H_GET primitive after an open subfile function to check asubfile type in input.

Action


NC07 FROM SERVER svr_name PUT CONTROL RECORD ERROR gr4

Meaning

An error occurred in the H_PUT primitive after a function that creates a BIN or SLcontrol record (depending on the file type).

Action


NC07 FROM SERVER svr_name PUT DATA RECORD ERROR gr4

Meaning

An error occurred in the H_PUT primitive while writing a data record in a givenfile or subfile.

Action


Messages

47 A2 94UC 6-85

NC07 FROM SERVER svr_name OPEN FILE ERROR gr4

Meaning

An error occurred in an H_OPEN file primitive.

Action


NC07 FROM SERVER svr_name POINT OPEN SUBFILE ERROR gr4

Meaning

An error occurred in the H_POINT primitive after an open subfile operation.

Action


NC07 FROM SERVER svr_name SGCR LOAD ERROR gr4

Meaning

An error occurred in the H_SGCR primitive (segment creation) during a loadfunction.

Action



6-86 47 A2 94UC

NC07 FROM SERVER svr_name SGCR DUMP ERROR gr4

Meaning

An error occurred in the H_SGCR primitive (segment creation) during a dumpfunction.

Action


NC07 FROM SERVER svr_name CRFD OPEN FILE ERROR gr4

Meaning

An error occurred in an H_CRFD primitive (create file declaration).

Action


NC07 FROM SERVER svr_name DFLASG OPEN FILE ERROR gr4

Meaning

An error occurred in an H_DFLASG primitive (dynamic file assignment).

Action


Messages

47 A2 94UC 6-87

NC08 FROM SERVER svr_name subfile_name NOT FOUND IN file_name

Meaning

The subfile does not exist in the file_name.

Action

If the subfile is TSLNCC of SYS.DSASLIB, there is an error in the OCS Front Endsubdomain installation. This subfile must contain a list of the earlier OCS FrontEnd software versions (which have been installed on the host).

If the subfile is <Version>IMA_PPA of SYS.DSASLIB, there is an error in theOCS Front End subdomain installation. This subfile must contain the memoryimage to be loaded and executed in the PPA board.

NC48 FROM SERVER <srvr>: AT LEAST SYS.DSATRC_<lct_name>_i IS MISSING <srvr> SERVER IS WAITING FOR FILE(S) CREATION

Meaning

The message was issued by the server named <srvr>.

The name of the OCS Front End associated with the server is <lct_name>.

The name of the missing file is SYS.DSATRC_<lct_name>_i (where i = 1 or 2).

At least one of the 2 sequential files needed by the OCS Front End tracemechanism is missing. During this error the OCS Front End trace mechanism isnot available (for this OCS Front End).

Action

Check that the file named SYS.DSATRC_<lct_name>_1 and the file namedSYS.DSATRC_<lct_name>_2 are present.

Create the missing file(s). Refer to section 10.2.8.2, <DIR>.DSATRC_<LCTname>_i files in this manual.

The server will start using the newly created file within a minute (of its creation).


6-88 47 A2 94UC

NC48 FROM SERVER <srvr>: UNRECOVERABLE ERROR ON SYS.DSATRC<name> IS MISSING REPAIR IT BEFORE NEXT <srvr> RESTART

Meaning


The full path name of the file concerned is SYS.DSATRC<name>.

An irrecoverable error occurred while accessing this file (the file may be missing).

Action

Check the status of the named file.

If the file has a bad status, delete it and then re-create it.

If the file is missing, create it. Refer to section 10.2.8, OCS Front End TraceFacility in this manual.

The server will use the newly created file after the next server restart, or after thesubmission of an RSTADM command.

NC48 FROM SERVER <srvr>: SYS.DSATRCIDX_<lct_name> CREATION PREVIOUS LOGGED TRACE MESSAGES MAY BE LOST

Meaning



The full path name of the file concerned is SYS.DSATRCIDX_<lct_name>.

The server concerned has created or re-created this file. This is normal behaviorwhen the server starts for the first time.

This is abnormal behavior on subsequent starts of the server (it means that the filewas deleted). Previously logged trace messages may have been lost. Subsequenttraces will start from the file SYS.DSATRC_<lct_name>_1.

Action

None.

Messages

47 A2 94UC 6-89

NC48 FROM SERVER <srvr>:SYS.DSATRC_<lct_name>_i OPEN FAILURE <srvr> IS WORKING IN REDUCED TRACE MODE

Meaning



The full path name of the file concerned is SYS.DSATRC_<lct_name>_i (where 3<= i <= 9).

The server concerned has not been able to open this file. This is because the filehas been deleted (since the last successful access to it). Consequently, the OCSFront End trace mechanism will work using only the filesSYS.DSATRC_<lct_name>_1 through SYS.DSATRC_<lct_name>_i-1.

Action

If you want to increase the number of files available for OCS Front End tracing, re-create the file SYS.DSATRC_<lct_name>_i. Refer to section 10.2.8.2,<DIR>.DSATRC_<LCT name>_i files in this manual.

NC48 FROM SERVER <srvr>: ACCESS TO FILE SYS.DSATRCIDX_<lct_name>FAILED.

Meaning



The server cannot access to file SYS.DSATRCIDX_<lct_name>

1. This is because the project Operator does not have the right to access thedirectory SYS. In general, an Access Right Violation has occurred, if . Operatordoes not have the right PROXY.

2. This is because the incoherence between entry catalog and the file.

The full path name of the file concerned is SYS.DSATRCIDX_<lct_name> (wherelct_name is EAxx, 0 <= x <= 9).


6-90 47 A2 94UC

Action

1. CHECK ACCESS RIGHT OF OPERATOR : Use MODIFY_ACL commandby System Administrator. The right of project Operator must be set to PROXY.

2. CHECK COHERENCE BETWEEN ENTRY CATALOG AND THE FILE:Verify entry catalog by command LSDIR and verify the file by LSF. Delete it ifit isn't coherent.

Start server OCS by operator.

NC49 FROM SERVER <srvr>: <lct_name>_SNMP_COMM IS MISSING

Meaning



The subfile named <lct_name>_SNMP_COMM is missing from theSYS.DSACONF library. This subfile is essential for SNMP administration.Consequently, SNMP administration is no longer available.

Action

Create the subfile named <lct_name>_SNMP_COMM in the SYS.DSACONFlibrary.

The server will start using the newly created subfile within 5 minutes (of itscreation).

Messages

47 A2 94UC 6-91

NC49 FROM SERVER <srvr>: <lct_name>_SNMP_COMM : NO COMMUNITY MEMBER DECLARED

Meaning


The name of the FCP 7 associated with the server is <lct_name>.

The subfile named <lct_name>_SNMP_COMM is empty or contains onlycomment lines. No community member is declared. Community declaration isessential for remote SNMP administration. Consequently, remote SNMPadministration is not possible.

Action

Modify the subfile named <lct_name>_SNMP_COMM in the SYS.DSACONFlibrary by declaring community member(s).

The server take account of the subfile modifications within 5 minutes.

NC50 FCP DRIVER NOT AVAILABLE

Meaning

No OCS server has been started.

Action

Start an OCS server (STSVR command).

NC50 CANNOT GET PMOS COMMAND

Meaning

An error occurred while the OCS server was getting the PMOS command.

Action

None.


6-92 47 A2 94UC

NC50 IPS STACK NOT IN RIGHT FCP

Meaning

You submitted an IPS administrative command on an OCS Front End which is notrunning TCP/UDP communications.

Action

Re-submit the command on the OCS Front End on which the IPS stack isconfigured.

NC50 IPS ADMINISTRATION FAILS

Meaning

Self explanatory.

Action

Submit an RSTADM command to restart it.

NC50 REJECTED COMMAND: NETSTAT IS RUNNING

Meaning

Self explanatory.

Action

None.

Messages

47 A2 94UC 6-93

NC50 REJECTED COMMAND: PING IS RUNNING

Meaning

Self explanatory.

Action

None.

NC50 REJECTED COMMAND: TEST IS RUNNING

Meaning

Self-explanatory.

Action

None.

NC50 rejected command: UPGRADECF is running

Meaning

You submitted an iterative command (such as: PING, XID, TEST, ...) while anUPGRADECF command was still running on the same OCS Front End.

Action

Re-submit the command later (after the UPGRADECF command has completed).


6-94 47 A2 94UC

NC50 rejected command: XID is running

Meaning

You submitted an iterative command (such as: PING, NETSTAT, TEST, ...) whilean XID command was still running on the same OCS Front End.

Action

Re-submit the command later (after the XID command has completed).

NC50 rejected command: DACTFCP is running

Meaning

You submitted an iterative command (such as: PING, XID, ECHO, ...) while aDACTFCP command was still running on the same OCS Front End.

Action

Re-submit the command later (after the DACTFCP command has completed).

NC50 try later: a command is still running

Meaning

You submitted an iterative command (such as: PING, XID, ECHO, ...) while acommand was still running on the same OCS Front End.

Action

Re-submit the iterative command later (after the command has completed).

Messages

47 A2 94UC 6-95

NC51 FCP DRIVER NOT AVAILABLE

Meaning

The OCS driver or the manager process has not been launched.

Action

Start the OCS driver with an STSVR command.

NC51 command TO host: UNEXPECTED RESPONSE TYPE

Meaning

There is an incompatibility between the agent and the manager (so the managercannot interpret the agent response).

Action

Set the FCP trace on and submit the trace to your support.

NC51 command TO host: OBJECT object NOT TRANSLATABLE IN DOT NOTATION

Meaning

The object is neither in the user MIB (the subfileSYS.DSACONF..SNMP_MGR_MIB) nor in the default MIB.

Action

Correct the symbolic name of the object in the command, or add the symbolicname (and its dot notation value) to the user MIB (the subfileSYS.DSACONF..SNMP_MGR_MIB).


6-96 47 A2 94UC

NC51 command1 TO host: COMMAND command2 ALREADY LAUNCHED

Meaning

You may issue only one request command at a time.

Action

You must either stop command2 (for example, via an ENDSNMP command) orwait for command2 to complete before submitting another command.

NC51 command1 TO host: COMMAND command2 NOT LAUNCHED

Meaning

You issued command1 to terminate command2, but command2 has either not beensubmitted or has already completed.

Action

You may enter any request command (but not an ENDxxxx command).

NC51 command1 TO host: COMMAND command2 TERMINATED

Meaning

Command1 has successfully terminated command2.

Action


Messages

47 A2 94UC 6-97

NC51 command TO host: COMMAND COMPLETED

Meaning

A request command has successfully completed. This message is the last one forthis command.

Action


NC51 command TO host: UNREACHABLE HOST (TIMEOUT OR COMMUNITY REJECTED)

Meaning

The SNMP agent of the host did not respond.

Either:

• the requested agent is not running,

• or, the host is not reachable.

• or, the community in the SGMR_COMMPORT subfile does not correspond tothe one authorized by the requested agent.

Action

Verify that the IP address or the host identifier is declared in theSGMR_COMMPORT file. If the community name is erroneous or has NONE asright, the agent does not respond even if it is running.


6-98 47 A2 94UC

NC51 command TO host: UNKNOWN HOST

Meaning

The host identifier given as a command parameter has no corresponding IP Addressin the SYS.DSACONF..ETC_HOSTS subfile.

Action

Correct the host identifier or the IP Address in the command, or in theSYS.DSACONF..SGMR_COMMPORT subfile, or in theSYS.DSACONF..ETC_HOSTS subfile.

NC51 command TO host: MANAGER CONFIGURATION FILE IS MISSING

Meaning

The SYS.DSACONF..SGMR_COMMPORT subfile is missing.

Action

Create a SYS.DSACONF..SGMR_COMMPORT subfile.

NC51 command TO host: MANAGER CONFIGURATION FILE IS EMPTY (NO VALID ENTRY)

Meaning

There is no valid entry in the SYS.DSACONF..SGMR_COMMPORT subfile.

Action

Create a valid entry in the SYS.DSACONF..SGMR_COMMPORT subfile.

Messages

47 A2 94UC 6-99

NC51 command TO host: INTERNAL ERROR text

Meaning

The SNMP manager has detected an internal error while processing the command.

Action

Transmit the text to your support.

NC51 command TO host: COMMAND LAUNCHED

Meaning

This is a normal message indicating that the command has been transmittedcorrectly to the agent.

Action

None.

NC51 snmpdoc TO host: NO INFORMATION FOR THIS OBJECT

Meaning

The SNMP manager has either not found the object in the documentation files orhas not found the documentation files.

Action

Verify that the object's symbolic name is correct and that the documentation filesexist in the SYS.DSASLIB library.


6-100 47 A2 94UC

NC51 command TO host: RETRYING

Meaning

A response has not been received to the request command before the timeout.

Action

Either, continue to wait for the response, or terminate the request command (bysubmitting an ENDSNMP command).

NC51 manager not started

Meaning

The request command arrived too early (before the driver has completely started).

Action

Re-submit the command after you receive the "CONNECTED TO NETWORK"message.

NC51 transport provider not responding

Meaning

The request cannot be processed because the IP Stack (IPS) is not running.

Action

If necessary, re-start the OCS server with the IPS protocols available.

Messages

47 A2 94UC 6-101

NC52 command RESPONSE FROM host: UNKNOWN object OBJECT

Meaning

The object is not known to the SNMP agent of the host.

Action

Verify the object identification.

NC52 command RESPONSE FROM host: value ILLEGAL VALUE

Meaning

The value has been verified by the agent (for an SNMPSET command) and isincompatible with the object.

Action

Refer to the object documentation.

NC52 command RESPONSE FROM host: object IS READ-ONLY

Meaning

The object is declared non-modifiable in the agent. The SNMPSET command isrejected.

Action

None.


6-102 47 A2 94UC

NC53 Name------------------------------ Value --------------NC53 <objectid> <value>

Meaning

This is the banner and the display line resulting from an operation (SNMPGET,SNMPGETNEXT, SNMPSET) on an object.

Action

None.

NC53 Addr-------- Int NetMask------- Broadcast. Addr- MxSizNC53 <@IP> ... ....... ........... .....

Meaning

This is the banner and the display line resulting from a GETNET command.

Action

None.

NC53 Dest----- NextHop---- Type- Proto MaskHexa Int M1 M2 M3 M4 M5NC53 <@IP> <@IP> ... ... ........ ... . . . . .

Meaning

This is the banner and the display line resulting from a GETROUTE command.

Action

None.

Messages

47 A2 94UC 6-103

NC53 LocalAddr---- LPort RemoteAddr--- RPort StateNC53 <@IP> ..... <@IP> ..... .....

Meaning

This is the banner and the display line resulting from a GETTCPCN command.

Action

None.

NC53 LocalAddr---- LPortNC53 <@IP> .....

Meaning

This is the banner and the display line resulting from a GETUDP command.

Action

None.

NC53 Int PhysAddress------ NetAddr------- Type-NC53 fd ..:..:..:..:..:.. <@IP> ....

Meaning

This is the banner and the display line resulting from a GETARP command.

Action

None.


6-104 47 A2 94UC

NC54 command : <name> command completed

Meaning

This indicates the successful completion of the command whose name is <name>.

Action

None.

NC54 command : <name> command launched

Meaning

This indicates the successful submission of the command whose name is <name>.

Action

None.

NC54 command : <name> response from <EAxx>

Meaning

This indicates that the command whose name is <name> has been submitted to theOCS Front End controller identified by <EAxx>. The next message displayed willbe the response or non-response.

Action

None.

Messages

47 A2 94UC 6-105

NC54 command : <name> timeout on <EAxx> response

Meaning

There is a timeout on the response from the OCS controller identified by <EAxx>to the command whose name is <name>.

Action

Check the OCS Front End state.

NC54 command : <name> terminated

Meaning

The command whose name is <name> has terminated:

• abnormally, due to an error during its processing (for example, timeout, ...),

• or normally, in response to an ENDxxxx command (for example, a DACTFCPcommand terminated by an ENDACTFCP command).

Action

In case of error, refer to the associated error message.

NC54 command : <name> no OCS server started for <EAxx>

Meaning

The OCS server handling the OCS controller identified by <EAxx> has notcompletely started.

Action

Start the OCS server related to the OCS Front End concerned.

Once the OCS server has started, retry the command later.


6-106 47 A2 94UC

NC54 command : <name> no IVMO declared

Meaning

No OSI/DIWS configuration has been done.

Action

None, if this is normal.

Otherwise, perform an OSI/DIWS configuration.

NC54 command : <name> unknown IVMO

Meaning

The IVMO given in the IVMO management command (for example, DPLKIVMO,ATTIVMO) has not been declared.

Action

If necessary, create the IVMO by configuration or by a CRIVMO command.

NC54 command : <name> unknown NRTS

Meaning

The NRTS given in the IVMO management command (for example, DPLKIVMO,ATTIVMO, TRCTPDU) does not exist.

Action

Check the OSI/DIWS configuration subfile of the OCS Front End concerned.

Messages

47 A2 94UC 6-107

NC54 command : <name> unknown RNSAP

Meaning

The RNSAP given in the IVMO management command (for example,DPLKIVMO, ATTIVMO does not exist.

Action

Check the OSI/DIWS configuration subfile of the OCS Front End concerned.

NC54 command : DPLKIVMO IVMO : <ivmo_name> not linked

Meaning

Self explanatory.

Action

None.

NC54 command : <name> not allowed for NRTS of INET type

Meaning

You attempted to attach an IVMO to a NRTS of type INET (also known asRFC1006) via an ATTIVMO command.

Action

None.


6-108 47 A2 94UC

NC54 command : XGATC ERROR : not allowed for TC of INET type

Meaning

You attempted to retrieve the extended attributes of a TC (Transport Connection) oftype INET via an XGATC command. Only OCS TC objects of type COTP andDIWS can be addressed by an XGATC command.

Action

None.

NC54 command : <name> ERROR : OSI/DIWS protocols not available

Meaning

You attempted to submit a command (CRIVMO, ECHO) while the OSI/DIWSprotocols of the OCS Front End concerned have not been configured. Refer to themessages displayed when the OCS server concerned was started.

Action

None.

NC54 command : <name> ERROR : IVMO already declared

Meaning

You attempted to submit a CRIVMO command, but the IVMO already exists in theOSI/DIWS configuration.

Action

Correct the IVMO name or use the MDIVMO command to modify the parametervalues of an existing IVMO.

Messages

47 A2 94UC 6-109

NC54 command : <name> ERROR : .......................

Meaning

An internal error has been detected during command processing. The textfollowing the word ERROR gives the reason.

Action

Start the trace for the OCS server (of the front end in error) using an STTRcommand. Re-enter the command which gave the error, and contact your support.

NC54 command : IFCONFIG ERROR : Illegal parameter value for NETMASK

Meaning

Self explanatory.

Action

Change the NETMASK value.

NC54 command : <command> ERROR : inconsistent IPS table

Meaning

The IPS routing tables, located in GCOS 7 and in the OCS Front End software, arenot coherent. These tables are altered by submitting an IFCONFIG or ROUTEcommand.

Action

Restart the OCS server using an STSVR command.


6-110 47 A2 94UC

NC54 command : <name> ERROR : TCP/IP protocol not available thru GXTI

Meaning

The PING command cannot be processed because the ICMP protocol (protocol ofthe IPS) is not accessible via GXTI. The most likely reason is that the IPS stackhas not been explicitly configured (refer to the NC01 message displayed at the endof the OCS configuration). Another reason may be that there is no link operationalbetween GXTI and the IPS stack (status of LT resource).

Action

Check the IPS configuration report (if it exists) in the SYS.DSACONF library.

Check the status of the LT resources.

NC54 command : <name> ERROR : selection of a local address

Meaning

The host name (or NSAP, or IP address, or ...) given to identify a remote element infact identifies a local element of the OCS Front End controller to which thecommand (ECHO, TRCTPDU) applies.

Action

Check the subfile ETC_HOSTS in the SYS.DSACONF library.

NC54 OCS local IPS administration restarted

Meaning

A RESTART_FCP_ADM command has been executed. A previously failed localadministrative component (here, the local IPS administration) has been restarted.

Action

None.

Messages

47 A2 94UC 6-111

NC54 OCS OSI/DSAC administration restarted

Meaning

A RESTART_FCP_ADM command has been executed. A previously failed localadministrative component (here, the local OSI/DSAC administration) has beenrestarted.

Action

None.

NC54 from server <name> : server TRACE restarted

Meaning

A RESTART_FCP_ADM command has been executed. A previously failed localadministrative component of the server (whose name is <name>) has beenrestarted. In this case, the component is the FCP trace collector.

Action

None.

NC54 from server <name> : SNMP restarted

Meaning

A RESTART_FCP_ADM command has been executed. A previously failed localadministrative component of the server (whose name is <name>) has beenrestarted. In this case, the component is the SNMP agent.

Action

None.


6-112 47 A2 94UC

NC55 <dest> is responding

Meaning

Self-explanatory.

Action

None.

NC55 command ECHO Request Route recording : PARTIAL/TOTAL/NONE

Meaning

Indicates whether or not the route recording contains the addresses of all nodesused to route the ECHO request to the remote node.

If TOTAL, all node addresses have been recorded.

If PARTIAL, some nodes have not recorded their addresses, or the list of addressesis too long.

If NONE, the remote node is on the same network as the issuer of the ECHOcommand.

Action

None.

Messages

47 A2 94UC 6-113

NC55 command ECHO Response Route recording : PARTIAL/TOTAL/NONE

Meaning

Indicates whether or not the route recording contains the addresses of all nodesused to route the ECHO response.

If TOTAL, all node adresses have been recorded.

If PARTIAL, some nodes have not recorded their addresses, or the list of addressesis too long.

If NONE, the remote node is on the same network as the issuer of the ECHOcommand.

Action

None.

NC55 NETitle : <nsap>

Meaning

Indicates the address of an intermediate node used to route the ECHO request.

Action

None.

NC55 command : ECHO Node: <name> is unknown

Meaning

The node identified by <name> is not declared in the ETC_HOSTS subfile of theSYS.DSACONF library.

Action

Update the ETC_HOSTS subfile.


6-114 47 A2 94UC

NC55 command : <command> Multiple NSAP for <node>

Meaning

The node identified by <node> is not declared in the ETC_HOSTS subfile of theSYS.DSACONF library.

Action

Update the ETC_HOSTS subfile.

NC55 command : <command> Multiple IP addresses for <node>

Meaning

The node identified by <node> is associated with several IP addresses in theETC_HOSTS subfile of the SYS.DSACONF library. The command does not knowwhich address to select.

Action

Select the node by its IP address instead of its name (or update the ETC_HOSTSsubfile).

NC56 FCP = EAyy MACADD = xx:xx:xx:xx:xx:xx

Meaning

Response to a DISPLAY_FCP_MACADD command from the OCS Front Endidentified by EAyy.

Action

None.

Messages

47 A2 94UC 6-115

NC57 <fcp><hour> LOAD = ..% TOTAL = ... USED = ... FREE = ...KB

Meaning

Display of OCS Front End activity in response to a DISPLAY_FCP_ACTIVITYcommand. The OCS Front End is identified by <fcp> and the host time ofsampling by <hour>.

Action

None.

NC58 IVMO#: ..... IVMO_NAME : .....

Meaning

Line of response to a DISPLAY_FCP_IVMO command.

Action

None.

NC58 RTS: ..... IVMO: .....

Meaning

Line of response to a DISPLAY_LINK_IVMO command.

Action

None.


6-116 47 A2 94UC

NC58 RNSAP: ..... IVMO: .....

Meaning

Line of response to a DISPLAY_LINK_IVMO command.

Action

None.

NC59 IVMO#=xxx IVMO_NAME: xxxxxxxx MAXRCRDT=xxx MACSCRDT=x MAXRETRY=x T1TIME=xxxxxxx WTIME=xxxx ITIME=xxx ACKTIME=xx TPUSIZE=xxx EXTMODE=Y/N T_CHECKSUM=Y/N

Meaning

Response displayed by normal execution of a DPIVMO command.

Action

None.

NC60 UPGRADE OF EAxx CONFIGURATION SUCCESSFUL

Meaning

No errors, no warnings, were detected while processing the incrementalconfiguration of the OCS Front End identified by EAxx.

Action

None.

Messages

47 A2 94UC 6-117

NC60 UPGRADE OF EAxx CONFIGURATION UNSUCCESSFULNC60 refer to report file SYS.DSACONF..EAxx_CONF_RPRT

Meaning

At least one error or warning was detected while processing the incrementalconfiguration of the OCS Front End identified by EAxx.

Action

Consult the report file. If necessary, re-submit a corrected incrementalconfiguration.

NC60 from server <name> : configuration unsuccessfulNC60 open failure of SYS.DSACONF..EAxx_CONF_RPRT file

Meaning

Self explanatory.

These are issued during the start of the OCS server identified by <name>. TheOCS Front End being configured is identified by EAxx.

Action

Check the status of the SYS.DSACONF library (access, space available, ...).

NC60 from server <name> : configuration unsuccessfulNC60 write error on SYS.DSACONF..EAxx_CONF_RPRT file

Meaning

Self explanatory.

These are issued during the start of the OCS server identified by <name>. TheOCS Front End being configured is identified by EAxx.

Action

Check the status of the SYS.DSACONF library (access, space available, ...).


6-118 47 A2 94UC

NC62 extended attributes of OCS Transport Connection : <tcref> IVMO_NAME=<ivmo-name> STATUS=<status> MAXRETRY=xxx NUMBF=<y/n> T1TIME=xxx WTIME=xxx ITIME=xxx ACKTIME=xxxxx

Meaning

Result of an FCP_EXTENDED_GA_TC (alias XGATC) command applied to theTransport Connection <tcref>. For more details, refer to the description of thiscommand.

Action

None.

NC62 OCS Transport Connection : <tcref> does not or no more exist

Meaning

Self-explanatory.

Action

None.

NC62 command : <name> cannot be processed. Restart OCS administration

Meaning

The command identified by <name> was submitted while the local administrationof the OCS server was not operational (failed, or not yet started).

Action

If a message indicating that local IPS administration has failed has also beendisplayed, and/or the OCS server is running, submit an RSTADM command torestart the local IPS administration.

If the OCS server is in the process of starting, re-submit the command later (oncethe OCS server has started).

Messages

47 A2 94UC 6-119

NC63 driver : <name> ipaddr:<@IP> node:<node_name>

Meaning

This is the message returned by a STRCTPDU or a TRCTPDU command. If<name> is UDP or TCP, then @IP is the IP address of the remote node. Thisaddress is used to select the traces of TPDUs.

<node_name> is the name retrieved from the ETC_HOSTS subfile using the @IPvalue (or UNKNOWN if the retrieve fails).

Action

None.

NC63 driver : TP1006 ipaddr:<@IP> port:xxx node:<node_name>

Meaning

This is the message returned by a STRCTPDU or a TRCTPDU command executedwith the TP1006 driver selected. @IP is the IP address of the RFC1006 node usedto select the traces of TPDUs. Port is the TCP listening port of the RFC1006 node.

<node_name> is the name retrieved from the ETC_HOSTS subfile using the @IPvalue (or UNKNOWN if the retrieve fails).

Action

None.


6-120 47 A2 94UC

NC63 driver : COTP macaddr:<mac_address> rts:<rts_name>

Meaning

This is the message returned by a STRCTPDU or a TRCTPDU command executedwith the COTP driver and RTS selected. <mac_address> is the physical address ofthe remote Transport Station whose name is given by <rts_name>. The<mac_address> is used as a selection criterion for the trace.

Action

None.

NC63 driver : COTP nsap:xxxxxxxx node:<node_name>

Meaning

This is the message returned by a STRCTPDU or a TRCTPDU command executedwith the COTP driver and NSAP selected. Nsap is the network address of theremote node. Name is the node name retrieved from the ETC_HOSTS subfile (orUNKNOWN if it cannot be retrieved). The nsap is used as a selection criterion forthe trace.

Action

None.

NC63 command:<name>RTS:<rts_name> not accessible through <driver> transport

Meaning

Self-explanatory.

Action

Retry the command <name> changing the driver selected.

Messages

47 A2 94UC 6-121

NC63 command:<name>NSAP:<nsap> not accessible through <driver> transport

Meaning

Self-explanatory.

Action


NC63 driver:<name> sel:xxxxxxxxxxxx

Meaning

This is the message returned when a TRCTPDU command completes normally.For the driver <name>, it gives the address on which the real selection is set.

Action

None.

NC63 command:<name> node:<node_name> not accessible through <driver> transport

Meaning

Self-explanatory.

Action



6-122 47 A2 94UC

NC65 IFCONFIG SUCCESSFUL FOR <node>

Meaning

Self explanatory.

Action

None.

NC65 IFCONFIG SERVER NOT STARTED FOR <node>

Meaning

The DCS server identified by <node> is not started.

Action

Start the related DCS server.

NC65 IFCONFIG UNSUCCESSFUL FOR <node> ERROR <code> INDEX <value>

Meaning

The OCS Front End has detected an error: inconsistent command message, illegalcommand parameters, or a command which is inconsistent with the state of thecommunications stack.

Action

Correct the error.

Messages

47 A2 94UC 6-123

NC66 IFCONFIG RESPONSE FROM <node> <interface> :flags=<value><...,...,...> INET <ipaddress> netmask=<mask> broadcast=<ipadress> ether <ethernet_address>

Meaning

The IFCONFIG command execution has completed.

Action

None.

NC68 ARP SUCCESSFUL FOR <node>

Meaning

Self explanatory.

Action

None.

NC68 ARP CANNOT HAVE ACCESS TO <node> ERROR 00000002NC68 ARP SERVER NOT STARTED FOR <node>

Meaning

The OCS server identified by <node> is not started.

Action

Start the OCS server attached to <node>.


6-124 47 A2 94UC

NC68 ARP CANNOT HAVE ACCESS TO <node> ERROR 0000000E

Meaning

There is an illegal command line in the ARPAD_ type subfile.

Action

Correct the command line in the subfile.

NC68 ARP CANNOT HAVE ACCESS TO <node> ERROR <code> [ <text of line in error> ]

Meaning

Administrative connection between OCS and the OCS Front End cannot beestablished. If the command has been taken from an ARPAD_ type subfile, thecommand line (from the subfile) in error is displayed in the message.

Action

Correct the erroneous command.

NC68 ARP CANNOT BE PROCESSED FOR <node> ERROR <code> [ <text of line in error> ]

Meaning

An internal OCS fatal error has been detected while processing an ARP command.If the command has been taken from an ARPAD_ type subfile, the command line(from the subfile) in error is displayed in the message.

Action

Correct the erroneous command.

Messages

47 A2 94UC 6-125

NC68 ARP UNSUCCESSFUL FOR <node> ERROR 00000019 INDEX 00000000

Meaning

The related ARP entry does not exist or has already been deleted.

Action

None.

NC68 ARP UNSUCCESSFUL FOR <node> ERROR 0000001E INDEX 00000001

Meaning

There is an illegal IP address (not on the same network).

Action

Modify the IP address given in the ARP command.

NC68 ARP UNSUCCESSFUL FOR <node> ERROR <code> INDEX <value> [ <text of line in error> ]

Meaning

The FCP 7 has detected an error: inconsistent command message, illegal commandparameters, or a command which is inconsistent with the state of thecommunications stack. If the command has been taken from an ARPAD_ typesubfile, the command line (from the subfile) in error is displayed in the message.

Action

Correct the error.


6-126 47 A2 94UC

NC68 ARP UNSUCCESSFUL FOR <node> - HOST/NET NAME NOT FOUND

Meaning

The host name or the network name given in a parameter of the ARP command isnot present in the ETC_HOSTS or in the ETC_NETWORKS subfile.

Action

Correct the ARP command parameter or update the ETC_HOSTS or theETC_NETWORKS subfile.

NC68 ARP UNSUCCESSFUL FOR <node> - CANNOT HAVE ACCESS TO FILE

Meaning

The subfile named in the ARP -f command cannot be accessed or does not exist.

Action

Correct the subfile name in the ARP -f command, or create/modify the subfileconcerned.

NC69 ARP RESPONSE FROM <node><host>(<host_IPaddress) at <Ethernet address>

Meaning

Self explanatory.

Action

None.

Messages

47 A2 94UC 6-127

NC69 ARP RESPONSE FROM <node><host>(host_ipadd)--no entry

Meaning

The ARP address table is empty or all its entries have been deleted.

Action

Create entries in the ARP address table.

NC72 ROUTE SUCCESSFUL FOR <node>

Meaning

Self explanatory.

Action

None.

NC72 ROUTE UNSUCCESSFUL FOR <node> ERROR 00000019 INDEX 00000000

Meaning

There was an attempt to create a route which is already created, or to delete a routewhich has already been deleted, or to delete a non-existing route.

Action

None.


6-128 47 A2 94UC

NC72 ROUTE UNSUCCESSFUL FOR <node> ERROR <code> INDEX <value>

Meaning


Action

Correct the error.

NC72 ROUTE CANNOT HAVE ACCESS ACCESS TO <node> ERROR 00000002NC72 ROUTE SERVER NOT STARTED FOR <node>

Meaning

The OCS server attached to <node> is not started.

Action

Start the OCS server.

NC72 ROUTE CANNOT HAVE ACCESS TO <node> ERROR <code>

Meaning

Administrative connection between OCS and the Front End cannot be established.

Action

Correct the error.

Messages

47 A2 94UC 6-129

NC72 ROUTE CANNOT BE PROCESSED FOR <node> ERROR FFFFFFFF

Meaning

There is an illegal gateway address.

Action

Modify the gateway address and re-submit the command.

NC72 ROUTE CANNOT BE PROCESSED FOR <node> ERROR <code>

Meaning

The OCS server has received an inconsistent command message from PMOS.

Action

None.

NC72 ROUTE UNSUCCESSFUL FOR <node> -HOST/NET NAME NOT FOUND

Meaning

The host name or the network name given in a parameter of the ROUTE commandis not present in the ETC_HOSTS or in the ETC_NETWORKS subfile.

Action

Correct the ROUTE command parameter or update the ETC_HOSTS or theETC_NETWORKS subfile.


6-130 47 A2 94UC

NC74 NETSTAT RESPONSE FROM <node> -- no route

Meaning

Self explanatory.

Action

None.

NC74 NETSTAT CANNOT HAVE ACCESS TO <node> ERROR 00000002NC74 NETSTAT SERVER NOT STARTED FOR <node>

Meaning


Action

Start the OCS server concerned.

NC74 NETSTAT CANNOT HAVE ACCESS TO <node> ERROR <code>

Meaning


Action

Correct the error.

Messages

47 A2 94UC 6-131

NC74 NETSTAT CANNOT BE PROCESSED FOR <node> ERROR <code>

Meaning


Action

None.

NC74 ROUTE UNSUCCESSFUL FOR <node> ERROR <code> INDEX <value>

Meaning

The FCP 7 has detected an error: inconsistent command message, illegal commandparameters, or a command which is inconsistent with the state of thecommunications stack.

Action

Correct the error.

NC74 NETSTAT RESPONSE FROM <node> Destination Gateway Flags Refcnt Use Interface <addr/name> <addr/name> <...> <value> <value> <name>

Meaning

Self explanatory.

Action

None.


6-132 47 A2 94UC

NC74 NETSTAT RESPONSE FROM <node> input (<name>) output input (Total) output packets errs packets errs packets errs packets errs <value> <value> <value> <value> <value> <value> <value> <value>

Meaning

Self explanatory.

Action

None.

NC74 NETSTAT RESPONSE FROM <node> Name Mtu Network Address Ipkts Ierrs Opkts Oerrs<name> <size> <name> <IPaddress> <value> <value> <value> <value>

Meaning

Self explanatory.

Action

None.

NC78 PING UNSUCCESSFUL FOR <node> PING <IPaddress><size> data bytes - HOST UNREACHABLE

Meaning

Target host cannot be reached or does not respond to PING request.

Action

None.

Messages

47 A2 94UC 6-133

NC78 PING CANNOT HAVE ACCESS TO <node> ERROR 00000002NC78 PING SERVER NOT STARTED FOR <node>

Meaning


Action


NC78 PING CANNOT BE PROCESSED FOR <node> ERROR <code>

Meaning


Action

None.

NC78 PING UNSUCCESSFUL FOR <node> - HOST/NET NAME NOT FOUND

Meaning

The host name given in a PING command is not present in the ETC_HOSTSsubfile.

Action

Correct the PING command parameter or update the ETC_HOSTS subfile.


6-134 47 A2 94UC

NC78 PING RESPONSE FROM <node>

PING <IPaddress><size> data bytes* <size> bytes from <IP address>:icmp_seq=<i>.time=<t>.ms

[---<IP address>PING Statistics---

<n> packets transmitted, <m> packets received, <x>% packets loss

round trip (ms) min/avg/max = <j>/<k>/l> ]

Meaning

This is the output from a normal execution of a PING command.

Action

None.

NC78 PING RESPONSE FROM <node>

PING <IP address><size> data bytes

<size> bytes from <IP address>:icmp_type=<x>.(type message>)

[---<IP address>PING Statistics---


round trip (ms) min/avg/max = <j>/<k>/l> ]

Meaning

An ICMP message other than a PING reply has been received during a PINGcommand with the verbose (-v) option. The text of this ICMP message is displayedin the NC78 message.

Action

None.

Messages

47 A2 94UC 6-135

NC81 TEST RESPONSE FROM EA92 ETH <Ethernet address> TEST COMMAND NUMBER: <i> ... TEST OPERATION COMPLETED

Meaning

Self explanatory.

Action

None.

NC81 TEST NO RESPONSE FROM <node>.ETH<Ethernet address> ...

Meaning

Self explanatory.

Action

None.

NC81 TEST UNSUCCESSFUL FOR <node> ERROR <code> INDEX <value>

Meaning


Action

Correct the error.


6-136 47 A2 94UC

NC81 TEST CANNOT HAVE ACCESS TO <node> ERROR 00000002NC81 TEST SERVER NOT STARTED FOR <node>

Meaning


Action


NC81 TEST CANNOT HAVE ACCESS TO <node> ERROR <code>

Meaning

Administrative connection between OCS and the OCS Front End cannot beestablished.

Action

Correct the error.

NC81 TEST CANNOT BE PROCESSED FOR <node> ERROR <code>

Meaning


Action

None.

Messages

47 A2 94UC 6-137

NC84 XID RESPONSE FROM <node>

ETH <Ethernet address> IS RESPONDING ...[ XID RESPONSE FROM <node>.BROADCAST OPERATION BROADCAST OPERATION COMPLETED ]

Meaning

Self-explanatory.

Action

None.

NC84 XID NO RESPONSE FROM <node>.ETH<Ethernet address>

Meaning

Self-explanatory.

Action

None.

NC84 XID UNSUCCESSFUL FOR <node> ERROR <code> INDEX <value>

Meaning


Action

Correct the error.


6-138 47 A2 94UC

NC84 XID CANNOT HAVE ACCESS TO <node> ERROR 00000002NC84 XID SERVER NOT STARTED FOR <node>

Meaning


Action


NC84 XID CANNOT HAVE ACCESS TO <node> ERROR <code>

Meaning


Action

Correct the error.

NC84 XID CANNOT BE PROCESSED FOR <node> ERROR <code>

Meaning


Action

None.

Messages

47 A2 94UC 6-139

NC87 SEETRACE RESPONSE FROM <node>

ENTITY ----- TRACE LEVEL NUMBER : ON = X. 1 2 3 4 5 6 7 8 etc until 16<name> <x> <x> <x> <x> <x> <x> <x> <x> <x>

17 18 19 20 21 22 23 24 etc until 32<name> <x> <x> <x> <x> <x> <x> <x> <x> <x>

Meaning

Self explanatory.

Action

None.

NC87 SEETRACE XID UNSUCCESSFUL FOR <node> ERROR <node> INDEX <value>

Meaning


Action

None.

NC87 SEETRACE CANNOT HAVE ACCESS TO <node> ERROR 00000002NC87 SEETRACE SERVER NOT STARTED FOR <node>

Meaning


Action



6-140 47 A2 94UC

NC87 SEETRACE CANNOT HAVE ACCESS TO <node> ERROR <node>

Meaning


Action

Correct the error.

NC87 SEETRACE CANNOT BE PROCESSED FOR <node> ERROR <node>

Meaning


Action

None.

NC90 TRACE SUCCESSFUL FOR <node>

Meaning

Self explanatory.

Action

None.

Messages

47 A2 94UC 6-141

NC90 TRACE UNSUCCESSFUL FOR <node> ERROR <code> INDEX <value>

Meaning


Action

Correct the error.

NC90 TRACE UNSUCCESSFUL FOR <node> - ERROR ON LEVEL

Meaning

Entity does not support the trace level needed.

Action

Correct the error.

NC90 TRACE CANNOT HAVE ACCESS TO <node> ERROR 00000002NC90 TRACE SERVER NOT STARTED FOR <node>

Meaning


Action

Start the OCS server.


6-142 47 A2 94UC

NC90 TRACE CANNOT HAVE ACCESS TO <node> ERROR <node>

Meaning


Action

Correct the error.

NC90 TRACE CANNOT BE PROCESSED FOR <node> ERROR <node>

Meaning


Action

None.

NC92 NOTRACE UNSUCCESSFUL FOR <node>

Meaning

Self explanatory.

Action

None.

Messages

47 A2 94UC 6-143

NC92 NOTRACE UNSUCCESSFUL FOR <node> ERROR <code> INDEX <value>

Meaning


Action

Correct the error.

NC92 NOTRACE CANNOT HAVE ACCESS TO <node> ERROR 00000002NC92 NOTRACE SERVER NOT STARTED FOR <node>

Meaning


Action


NC92 NOTRACE CANNOT HAVE ACCESS TO <node> ERROR <node>

Meaning


Action

Correct the error.


6-144 47 A2 94UC

NC92 NOTRACE CANNOT BE PROCESSED FOR <node> ERROR <node>

Meaning


Action

None.

NC94 ENDNETST SUCCESSFUL FOR <node>

Meaning

Self explanatory.

Action

None.

NC94 ENDNETST CANNOT HAVE ACCESS TO <node> ERROR <node>

Meaning


Action

Correct the error.

Messages

47 A2 94UC 6-145

NC96 ENDPING CANNOT HAVE ACCESS TO <node> ERROR <node>

Meaning


Action

Correct the error.

C96 ENDPING SUCCESSFUL FOR <node>

---<IP address>PING Statistics---


round trip (ms) min/avg/max = <j>/<k>/l>

Meaning

This is the output from a normal execution of an ENDPING command.

Action

None.

NC98 ENDTEST SUCCESSFUL FOR <node> TEST COMMAND COMPLETED

Meaning

Self-explanatory.

Action

None.


6-146 47 A2 94UC

NC98 ENDTEST UNSUCCESSFUL FOR <node> ERROR <code> INDEX <value>

Meaning


Action

Correct the error.

NC98 TRACE CANNOT HAVE ACCESS TO <node> ERROR <node>

Meaning


Action

Correct the error.

Messages

47 A2 94UC 6-147

6.8 NG Messages

NG01 WARNING: GCOS SYSTEM AND NETWORK CONFIGURATIONS MAY MISMATCH

Meaning

The current system configuration index is different from that contained in thenetwork configurations being enabled.

Action

If the changes in the system configuration affect communications processing, runthe NETGEN utility.

NG02 NETWORK CONFIGURATION . MISMATCH BETWEEN PREVIOUS AND NEW VERSION gr4 (01) . VMF FILE NOT FOUND gr4 (02) . RETRIEVED CONFIGURATION IS NOT VALID gr4 (04) . NOT AVAILABLE - gr4 (02) - ENABLE INTERNAL ERROR gr4 (03) - SEGMENT OVERFLOW gr4 (04) . ERROR WHEN - ACCESSING WORKSPACE gr4 (06) - ABNORMAL VMF ACCESS gr4 (06) - ABNORMAL SEGMENT EXTENSION gr4 (06) - INITIALIZING SERVER SEMAPHORE LINK * ABNORMAL SERVER SEMAPHORE LINK INIT gr4 (06) * ABNORMAL SERVER SEMAPHORE LINK DELETE gr4 (06) - INITIALIZING SERVER TRACE SEGMENT * ABNORMAL SERVER TRACE SEGMENT INIT gr4 (07) * ABNORMAL SERVER TRACE SEGMENT DELETE gr4 (07) - LOADING SYSTEM TABLE gr4 (08) - LOADING TERMINAL TABLE gr4 (09) - LOCKING/UNLOCKING SEGMENT * ABNORMAL SEGMENT LOCKING gr4 (10) - OBSOLETE * BAD ENBL ARGUMENTS gr4 (11) * UNEXPECTED CALL KEY gr4 (11) - TEMPORARY gr4 (12) . NOT FOUND - BINARY LIBRARY SUBFILE NOT FOUND FOR NETWORK gr4 (13) - IN WORKSPACE gr4 (14) . NOT VALID


6-148 47 A2 94UC

Meaning

All these messages specify that the Network Configuration cannot be enabled forthe reason explained in each submessage.

(01) Not ISL visible.(02) Unused(03) Internal error.(04) Sizing of some type 0 segment has failed.(05) Workspace contents not accessible.(06 - 07) TNS semaphore or type 0 initialization has failed.(08) Enabling of system tables has failed.(09) Enabling of terminal table has failed.(10) Semaphore segment locking has failed.(11) Retrieved configurations were built under

incompatible GCOS release.(12) Retrieved configurations were built with

TEMPORARY option.(13) Basic network configuration does not exist in specified

binlib.(14) Basic network configuration is absent from current

workspace. Loading from binlib may have failed.(15) Due to an error at generation time, the retrieved basic

network configuration is not operable.

Action

(01 - 02) None.(03 - 04) Call the Service Center.(05) Do a clean restart. If the same problem persists, call

the Service Center.(06 - 07) Call the Service Center.(08 - 09) Run NETGEN. If the same problem persists, call the

Service Center.(10) Call the Service Center.(11) Recreate the configurations using NETGEN under the

current V6 release.(12) Recreate the configurations using NETGEN without

the TEMPORARY option.(13) Check the binlib name, otherwise see (14)(14 - 15) Run NETGEN to build the configuration required.

Messages

47 A2 94UC 6-149

NG03 DO YOU WANT TO LOAD PREVIOUSLY SAVED TELECOMMUNICATION CONFIGURATIONS? (Y,N), DEFAULT=Y

Meaning

Allows the search of the network generation from the SYS.DSACORE library ifthe members NETGEN_CORR, NETGEN_TRMN and NETGEN_CTMN arepresent.

Action

The answer depends on whether a new Technical Status is introduced for GCOS 7:

• After an update for a new Technical Status followed by CLEAN restart, answerN (no). Then resubmit the network generation at GCOS READY.

• Otherwise, the default Y (yes) applies.

NG04 GCOS ERROR; REPLY NOT AVAILABLE . YES (LOAD) IS ASSUMED gr4 (01) . NO (MAM OPTIONS) IS ASSUMED gr4 (02)

Meaning

(01) No answer given to message NG03 or expiry of timeout delay.

(02) No answer given to message QC15 or expiry of timeout delay.

Action

None.

NG05 GCOS ERROR WHEN FORMATTING MAM QUEUES gr4

Meaning

An error has occurred during the formatting and initialization of the queue file.

Action

Correct the allocation attributes of the queue file.


6-150 47 A2 94UC

NG06 GCOS ERROR WHEN ACCESSING WORKSPACE gr4

Meaning

Internal error.

Action

None.

If no other NETGEN error message appears, the network generation should beoperable.

NG07 GCOS ERROR WHEN INITIALIZING . CSA TABLE: ABNORMAL TABLE RESET gr4 . DICTIONARY gr4 . SYSTEM TABLE gr4

Meaning

Internal errors.

Action

Do a clean restart and/or rerun the NETGEN utility. If the same problem persists,call the Service Center.

NG08 RUN NETWORK GENERATION UTILITY IF NECESSARY

Meaning

It is a generic message issued in addition to a NETGEN error message each timethe enabled configuration is not operable.

Action

Rerun NETGEN if the configuration is no longer operable.

Messages

47 A2 94UC 6-151

NG09 exception WHEN ENABLING NETWORK CONFIGURATION

Meaning

A system exception has occurred when enabling the network configurations.

Action


NG10 TERMINAL CONFIGURATION . NOT FOUND - BINARY LIBRARY SUBFILE IS NOT FOUND FOR TERMINALS gr4 (01) - VMF FILE CTMN NOT FOUND gr4 (01) . OBSOLETE gr4 (02) . TEMPORARY gr4 (03) . NOT COHERENT WITH BASIC CONFIGURATION gr4 (04) . INTERNAL ERROR (05)

Meaning

(01) Terminal configuration does not exist in specified binlib.

(02) Terminal configuration built under an incompatible GCOS release.

(03) Terminal configuration built with TEMPORARY option.

(04) Terminal configuration not built by the same NETGEN run as the basicconfiguration.

(05) GCOS 7 internal error.

Action

(01) Check binlib name or rerun the NETGEN utility to rebuild theconfigurations.

(02) Rerun the NETGEN utility to rebuild the configurations.

(03) Rerun the NETGEN utility without the TEMPORARY option.

(04) as for (01)

(05) Call the Service Center.


6-152 47 A2 94UC

NG11 GCOS ERROR WHEN EXTENDING SEGMENT gr4

Meaning

An unrecoverable GCOS error has occurred when enabling the networkconfiguration.

Action


NG13 SOME TELECOMMUNICATION OBJECTS ARE STILL ACTIVE GENERATION IS ABORTED.

Meaning

This message at the start of the network generation informs the user that theconfiguration being generated cannot be enabled because some communicationsobjects involving connections to either VCAM or servers are still active.

Action

• Either run the NETGEN utility with SAVE but without ENABLE (deferredenabling)

• Or close down GCOS communications before rerunning the NETGEN utilityusing the same parameters.

Messages

47 A2 94UC 6-153

NG14 GCOS ERROR WHEN HANDLING DIRECTORY WORKSPACE: . OPEN FUNCTION (01) . READ FUNCTION (02) . CLOSE FUNCTION (03) . LENGTH MISMATCH (04)

Meaning

This message signals a failure while handling the temporary or permanentworkspaces concerning the directory configuration. The submessage indicates theaction processed.

Action

(01 - 03) Rerun the NETGEN utility. If the workspace istemporary, the error condition may not appear.However, if the workspace is permanent, perform aclean restart before rerunning NETGEN.

(04) Rerun the NETGEN utility. If the same error persists,call the Service Center.

NG15 GCOS ERROR WHEN HANDLING DIRECTORY: . INITIALIZATION FUNCTION (01) . LOAD FUNCTION (02) . INTERNAL ERROR (03)

Meaning

This message signals a failure during the processing of the directory configuration.The submessage specifies the action in progress at the time of the error.

Action

(01 - 02) Rerun the NETGEN utility. If the same error persists,call the Service Center.



6-154 47 A2 94UC

NG16 WARNING: NO VALID CONFIGURATION RUNNING. INCREMENTAL GENERATION IS ABORTED.

Meaning

An incremental generation has been attempted but no valid communicationsconfiguration has been currently installed.

Action

Run the NETGEN utility to enable a valid basic network configuration beforeretrying the incremental generation.

NG17 DIRECTORY CONFIGURATION . BINARY LIBRARY SUBFILE NOT FOUND FOR DIRECTORY gr4 (01) . OBSOLETE gr4 (02) . TEMPORARY gr4 (03) . NOT CONSISTENT WITH BASIC CONFIGURATION gr4 (04) . INTERNAL ERROR gr4 (05)

Meaning

(01) The directory configuration searched for is not in the specified binlib.

(02) The directory configuration concerned has been built under anincompatible GCOS release.

(03) The directory configuration concerned has been built with theTEMPORARY option.

(04) The directory configuration concerned has not been built in the sameNETGEN run as the basic network configuration

(05) GCOS internal error.

Action

(01) Check the name of binlib and rerun the NETGEN utility.

(02) Rerun the NETGEN utility to rebuild the configuration.

(03) Rerun the NETGEN utility without the TEMPORARY option.

'04) Rerun the NETGEN utility to recreate a full consistent set ofconfigurations.


Messages

47 A2 94UC 6-155

NG18 PREVIOUSLY RUNNING CONFIGURATION NOT ACCESSIBLE IN WORKSPACE DO YOU WANT TO LOAD A SAVED ONE? (NO,SYS,LIB..MB) DEFAULT=SYS

Meaning

After a GCOS restart (COLD or WARM), some of the permanent communicationsworkspaces which were active during the previous GCOS session are no longeravailable.

Action

NO No valid communications configuration will beinstalled at GCOS system ready. The NETGEN utilitymust be rerun to regenerate new configurations.

SYS The configurations stored in NETGEN_CORR,NETGEN_CTMN and NETGEN_TRMN of theSYS.DSACORE binary library will be enabled.LIB..MB represents binary_library..subfile: Theconfigurations stored in subfile_CORR, subfileCTMNand subfile_TRMN of binary_library will be enabled.

NG19 WARNING: NO VALID CONFIGURATION RUNNING. OBJLIST "PREVIOUS" IS ABORTED.

Meaning

A dump of the communications tables currently active has been requested using theNETGEN utility but no valid communications configuration has been installed.

Action

Run the NETGEN utility to enable a valid communications configuration beforerequesting a dump of the tables concerned.


6-156 47 A2 94UC

NG20 NETWORK SECURITY REQUESTED BY GCOS BUT NOT CONFIGURED BY NETGEN

Meaning

NETSEC=YES was specified in the SECOPT directive of the GCOS 7configuration but security support is not provided in the basic networkconfiguration selected to be enabled.

Action

Run the NETGEN utility after either adding the appropriate information to thebasic network configuration or choosing another configuration to enable.

Messages

47 A2 94UC 6-157

6.9 QC Messages

QC06 TELECOM WARNING: QUEUE FILE OVERFLOW PENDING

Meaning

The disk queue file is almost full.

Action

Operator

• issue DNET CLASS=QD command to monitor the percentage occupancy of allMCS queues each time the message appears.

• retain the console listing for the systems analyst.

Systems Analyst

• examine the occupancy of the queues according to their function such as input,output or pooled

• rerun the MCS application

• repeat this process until the GCOS message no longer appears.

QC08 process-name UNABLE TO START USER PROCESS gr4

Meaning

The process-name identifies the user process that cannot be started. The gr4 givesthe error return code.

Action

Operator

• Retry the multiprocess MCS application whose process cannot be started

• If the same condition recurs, retain the console listing for the systems analyst.

Systems Analyst

• Correct the MCS application as necessary, according to the return code

• Resubmit the job

• If the same condition recurs, call the Service Center.


6-158 47 A2 94UC

QC13 ron TASK USER process-number ABORTED gr4

Meaning

ron identifies the multiprocess MCS application whose process indicated byprocess-number has aborted. The gr4 gives the error return code.

Action

Operator

• Retry the multiprocess MCS application whose process has aborted

• If the same condition occurs, retain the console listing for the systems analyst.

Systems Analyst

• Correct the MCS application, as necessary, according to gr4

• Resubmit the job

• If the same condition occurs, call the Service Center.

QC15 GCOS: MAM OPTIONS (NO, YES, REFORMAT) ? DEFAULT = NO

Meaning

Formatting request for disk queue files.

Action

YES or REFORMAT for formatting.

NO (default) for no formatting.

Messages

47 A2 94UC 6-159

QC30 QMON INITIALIZATION FAILED gr4

Meaning

System error defined by gr4.

Action


QC32 QMON FATAL ERROR gr4

Meaning

(01) I/O error on the drive on which the volume containing the disk queue fileis mounted.

(02) No more space available on disk queue file.

Action

(01) Check the state of the disk drive and if not operational, mount the volumeon another disk drive, and retry.

(02) If the disk drive is operational, rerun NETGEN to allocate a larger extenton the disk queue file.

QC33 QMON ABORTS

Meaning

System error.

Action



6-160 47 A2 94UC

QC34 QUEUE SEND ERROR ON QUEUE mbxnm gr4

Meaning

An I/O error has occurred during a send from QMON to the mailbox queue.

Action

According to the gr4 error return code, as follows:

BUFNAV Message could not be written to disk because of MCSdisk buffer overload. Call the Service Center.

IOFAIL Message could not be written to disk because of MCSdisk I/O failure. Check the status of the disk queuefile.

MSGOV Message written to disk has been truncated because itis too long. Check disk drive used for data entry.

NOTALL The designated queue is full. Try creating a largerextent.

SPACENAV Message could not be written to disk since the diskqueue file is full. Try creating a larger extent.

For all other return codes, call the Service Center.

QC35 QUEUE RECEIVE ERROR ON QUEUE mbxnm gr4

Meaning

An I/O error has occurred during a receive by QMON from the mailbox queue.

Action


BUFNAV Message could not be read from disk because of MCSdisk buffer overload. Check with Service Center.

IOFAIL Message could not be read from disk because of MCSdisk I/O failure. Check the status of the disk queuefile.


Messages

47 A2 94UC 6-161

QC36 QMON TABLES OVERFLOW

Meaning

Condition has resulted because of too large a traffic or too many connections.

Action


QC42 MCS NOT AVAILABLE: ERROR ON SYSTEM RESTART WHEN PROCESSING DISK QUEUE FILE gr4

Meaning

An incident has occurred when accessing the disk queue file on system restart.

Action


IOFAIL Check the status of the disk queue file.

MEDNAV The disk volume containing the queue file has not beenmounted.


NOTE:If MCS is to be used for a subsequent session, perform ISL after the disk queuefile incident has been corrected.


6-162 47 A2 94UC

6.10 TF Messages

TF01 SERVER svrnm WEAK SHUTDOWN RUNNING: number CONNECTIONS STILL USED

Meaning

Response to TTSVR svrnm command when at least one remaining connection wasstill active. The server concerned will terminate when its last connectionterminates.

Action

To force the server to terminate all its current connections, re-enter the samecommand specifying OPTION=STRONG.

TF03 RST . FATAL ERROR SERVER svrnm ABORT IN PROGRESS (01) . literal IN TASK j-number p-number AT ADDRESS literal (02)

Meaning

An irrecoverable incident has occurred, followed by details given in the secondmessage.

Action

Perform the following

• retain the JOR• take a dump of the server identified in the first message• take a dump of the application, if any• and contact the Service Center.

Messages

47 A2 94UC 6-163

TF04 RST literal IN TASK j-number p-number AT ADDRESS literal

Meaning

An irrecoverable incident has occurred when activating a server.

Action

Contact the Service Center.

TF05 LOG OF SERVER svr-name ALREADY ACTIVE EFN : efn (01)TF05 START LOG BY SERVER . ON ABORT EFN : efn (02) . ON OPERATOR REQUEST EFN : efn (03) . ON SEVERITY EFN : efn (04)

Meaning

(01) response to operator command DBSVR svr-name MDLOG when log trace on the server is already active.

(02 - 04) server has started logging its memory trace on theevent as indicated in the message.

Action

None.


6-164 47 A2 94UC

TF06 LOG OF SERVER svr-nm ALREADY INACTIVE. LAST EFN (IF ANY):efn (01)TF06 LOG TERMINATED BY SERVER svr-name . ON ITS TERMINATION EFN : efn (02) . ON OPERATOR REQUEST - EFN : efn (03)

Meaning

(01) response to operator command DBSVR svr-name MD LOG=0 whenlogging has already been terminated.

(02) logging has terminated since the server itself has terminated.

(03) response to operator command DBSVR svr-name MD LOG=0 toterminate the current log session.

Action

Take a listing of the log trace by using the PRTTRF command. The listing is to beretained for Service Center personnel.

NOTE:For the attention of Maintenance Personnel. The commands LSFST andDLFST can be used to list and to delete several file traces, respectively.

Messages

47 A2 94UC 6-165

TF07 TRACE WARNING (error-code) FOR SERVER svr-name return-code . FILE MANAGEMENT INCIDENT (01) . INCONSISTENT TRACE USE. SERVER NOT DAMAGED PLEASE CALL YOUR FIELD ENGINEER (02) . MEMORY MANAGEMENT INCIDENT (03) . UNEXPECTED INCIDENT. SERVER NOT DAMAGED PLEASE CALL YOUR FIELD ENGINEER (04)

Meaning

(01 and 03) problem with GCOS software(02 and 04) an anomaly has been detected during the trace session

Action

(01 and 03) depends on the return-code in the message, see themanual Messages and Return Codes MessageDirectory.

(02 and 04) if the message appears repetitively during the GCOSsession, report the symptom to the Service Center.


6-166 47 A2 94UC

TF50 DBSVR svr-name MD . COMPLETED (01) . IS THE COMMAND TO USE. UNKNOWN REQUESTED {ACTION|TARGET} (02) . IMPOSSIBLE (NO TABLES): SERVER NEVER STARTED (03) . LOG IMPOSSIBLE: SERVER NOT ACTIVE (03) . MAY BE PERFORMED. PLEASE CHECK WITH DBSVR...[D]... (04) . NO { DOMAIN | OBJECT | SUBDOMAIN } SELECTED (05) . REFUSED FOR AT LEAST ONE OBJECT: POS + VAL > LENGTH (06) . UNKNOWN SERVER (07)

Meaning

(01) Normal termination of command.

(02) Either an OCL command has been entered or there is a bug in theDBSVR command.

(03) Server has not been started since ISL or last NETGEN load.

(04) Option MD does not apply with other parameters in DBSVR.

(05) Name specified does not match any in the network generation.

(06) Position and value specified for object lead to a comparison out-of-bounds.

(07) Server name does not match TNS or an FEPS occurrence name.

Action

(01) none.

(02) contact the Service Center.

(03) enter STSVR svr-name to start the server concerned.

(04) check MD and D options with the rest of DBSVR parameters.

(05) enter DBSVR svr-name D { DOMAIN | OBJECT | SUBDOMAIN }=* toobtain list of names configured.

(06) enter DBSVR svr-name D OBJECT=object-name to get the definedmaximum length for the object; if maximum length is 0, position andvalue are not allowed.

(07) enter DTSVR to display the names of servers configured.

Messages

47 A2 94UC 6-167

TF51 DBSVR svr-name D . COMPLETED (01) . COMPLETED WITH ERROR (02) . IS THE COMMAND TO USE. UNKNOWN REQUESTED {ACTION|TARGET} (03) . IMPOSSIBLE (NO TABLES): SERVER NEVER STARTED (04) . LOG IMPOSSIBLE: SERVER NOT ACTIVE (04) . NO { DOMAIN | OBJECT | SUBDOMAIN } SELECTED (05) . UNKNOWN SERVER (06) . WARNING FOR AT LEAST ONE OBJECT: POS + VAL > LENGTH (07)

Meaning

(01) normal termination of command.(02) DBSVR command has executed but with inconsistent

results.(03) either an OCL command has been entered or there is a

bug in the DBSVR command.(04) server has not been started since ISL or last NETGEN

load.(05) name specified does not match any in the network

generation.(06) server name does not match TNS or an FEPS

occurrence name.(07) position and value specified for object lead to a

comparison out-of-bounds.

Action

(01) none(02 - 03) contact the Service Center.(04) enter STSVR svr-name to start the server concerned.(05) enter DBSVR svr-name D { DOMAIN | OBJECT |

SUBDOMAIN }=* to obtain list of names configured.(06) enter DTSVR to display the names of servers

configured.(07) contact the Service Center.


6-168 47 A2 94UC

TF52 LOG ACTIVE . EFN : efn . (ON ABORT) EFN : efn . (ON SEVERITY) EFN : efnTF52 LOG INACTIVE. LAST EFN (IF ANY): efn

Meaning

Response to operator command DBSVR svr-name D LOG=1, see TF05.

Action

None.

TF53 OBJECT ID LENGTH FILTER ADDRESS POSITION VALUETF54 object id length { ADDR | AND | OFF | ON | OR | POSVAL } address position value

Meaning

ID is the internal object identifier.

Response to DBSVR svr-name D OBJECT=object-name where object concerns thememory trace.

Action

If filter is a numeric value, report the symptom to the Service Center.

TF55 SUBDOM IN DOM ID SICID LVL SEV TOL SW0 SW1 SW2TF56 subdom IN dom id sicid lvl sev tol sw0 sw1 sw2

Meaning

ID is the internal subdomain identifier.

Response to DBSVR svr-name D SUBDOMAIN=subdomain-name.

Action

None.

Messages

47 A2 94UC 6-169

TF57 DOMAIN ID DEBUGTF58 domain id { 0 | 1 }

Meaning

ID is the internal domain identifier.

Response to DBSVR svr-name D DOMAIN=domain.

Action

None.

However, if DEBUG is a value other than 0 or 1, report the symptom to the ServiceCenter.


6-170 47 A2 94UC

6.11 TP Messages

TP01 SERVER TNS INITIALIZATION FAILURE return code . ERROR DURING DRIVER INITIALIZATION . ERROR ON TABLE INITIALIZATION ( {GNA | PLG | WA} ) TABLE see Note under Action for further details . ERROR ON ACK BUFFER POOL OPENING . ERROR ON TELECOM - BUFFER POOL OPENING - (CSA) PRIMITIVE : ACTIVATE LOAD MODULE - DICTIONARY PRIMITIVE - TRACE PRIMITIVE . ERROR WHILE ACTIVATING - { P#1 | P#2 } WORKSTATION - P#2 { MAILBOX | MESSAGE PATH DESCRIPTOR } . ERROR WHILE INITIATION TNS { P#1 | P#2 | P#3 } TASK . ERROR WHILE SETTING TELECOM INTERVAL TIMER . MISMATCH BETWEEN TELECOM SWITCHES (BTNS CONFIGURED)

Meaning

An incident has occurred when allocating a resource.

Action

If the abnormal return code does not indicate the reason for corrective action to betaken, contact the Service Center.

NOTE:Another TP01 error message follows specifying another return codeaccompanied by the appropriate explanation:

GNA: ret code ERROR ON SERVER - INTERNAL STATE (ALREADY STARTED)

PLG: ret code ERROR DURING DRIVER INITIALIZATION

WA : ret code SERVER SEMAPHORES NOT ALLOCATED

Refer to the Messages and Return Codes Directory.

Messages

47 A2 94UC 6-171

TP01 SERVER TNS INITIALIZATION FAILURE return code TNS TABLES CRUSHED BY LAST NG SAVE : LOAD NG

Meaning

The network generation has been specified with SAVE=SYS. The NETGEN utilitywill use the file containing the image of the current generation and not that whichhas just been created. The new network generation must first be reloaded beforeTNS can be restarted.

Action

Perform the following:

• terminate all servers• load the new network generation• and then restart the servers.

To avoid the message appearing in subsequent sessions, specify a private save, seethe manual Network Generation.

TP02 FROM SERVER TNS : { LCT | LPL } object-name newstate

Meaning

Notification that the object indicated has changed state due to one of the following:

• an MDNET STATE={LOCK|ENBL} command• automatic activation as follows• for LCT, an STSVR TNS command• for LPL, when its associated LCT is activated• an I/O error occurring.

Action

Except for I/O error, this message is only for information. If no command has beenentered, an I/O error has occurred.

Run the ERLOG job (SYS.HSLLIB) to detail the I/O error and contact the ServiceCenter.


6-172 47 A2 94UC

TP03 FROM SERVER TNS : IN ADMINISTRATION MODULE . DATA TRANSFER ERROR - DISCONNECT COMMAND {SENT|RECEIVED} (01) . ERROR STARTING ADMINISTRATION SERVER (02) . LPL HARDWARE OR CABLE CONNECTION FAILURE [ DETECTED ON LCT RESET ] (03) . MEMORY OVERFLOW - BUFFER ERROR (04) . NO RESPONSE FROM REMOTE TO { RESET | SIM } COMMAND (05)

Meaning

(01) HDLC link between the local and remote modules has beendisconnected.

(02) Irrecoverable software error

(03) The LCT has reported a malfunctioning hardware status

(04) Irrecoverable software error

(05) Either the remote module is not online (powered off or unplugged) or itsaddress does not match the address configured in the network generation.

Action

(01) check the status of the remote module and the LCT. If both arefunctioning normally, retry.


(03) none if the LPL and LCT are in ENABLE; otherwise run the appropriateT&D to test the LCT.


(05) see TP52.

Messages

47 A2 94UC 6-173

TP04 FROM SERVER TNS : ERROR ON VCAM PRIMITIVE DURING ADMINISTRATIVE FUNCTION CODE = error-code

Meaning

Error in VCAM during dialog between FECM and TNS.

Action

Contact the Service Center.

TP05 . OUT OF PROTOCOL INFORMATION RECEIVED FROM RPL : { dte-address | rplnm } (01) . RPL WITH ADDRESS : dte-address NOT CONFIGURED (02)

Meaning

(01) unknown administrative frame received

(02) an administrative frame received with a sender address which does notmatch an RPL of the network generation.

Action

Add the absent RPL or correct the address parameter in the RPL directive and rerunthe NETGEN utility.


6-174 47 A2 94UC

TP06 . LCT literal-name - HAS NOT ENOUGH LT IN FIRMWARE GENERATION (01) - INITIALIZATION IMPOSSIBLE : UNABLE TO ALLOCATE MEMORY (02) - UNKNOWN IN FIRMWARE GENERATION (SRST TABLE) (03) . LCT DRIVER WARNING hh IF INCIDENT CALL YOUR FIELD ENGINEER (04) . LT ltnm lctnm - HELD OR ALREADY ALLOCATED : RELEASE IT (05) - NEW FIRMWARE GENERATION BUT OLD SYSTEM CONFIG: RUN CONFIG (06)

Meaning

As in text.

Action

(01) run LSRST to check LCT status

(02) check available memory space

(03) run LSRST to check LCT status

(04) warning at Initialize System Load may have been issued but subsequentlyignored

(05) check the state of the hardware concerned

(06) call the Service Center if the error is irrecoverable

TP06 TNS ERROR . OBJECT TYPE : object . ORIGINATOR : originator . REASON : reason code

Meaning

The message only appears for debugging purposes.

Action

None.

Messages

47 A2 94UC 6-175

TP52 ECHO . NOT RECEIVED RPL : rpl (01) . NOT SENT RPL : rpl (02) . { RECEIVED | SENT } RPL : rpl (03)

Meaning

(01) after a lapse of 5 seconds,the ECHO frame has not returned from theRPL.

(02) the ECHO frame cannot be sent since probably the LPL is not enabled toaccess the RPL.

(03) the ECHO frame has been transmitted successfully.

Action

(01) Check that the RPL is powered up and that the ISL is functioningcorrectly. If the hardware is in proper order, check the addressconfiguration of the network generation as follows:- the ISL (DTE) address of the configured RPL matches its address declared- and the LPL address has been correctly declared.If the address declared is in error, correct the network generation.

(02) Set the LCT or LPL to ENBL, if LOCK.

(03) none

TP53 CONFIG RESPONSE FROM RPL rpl-name

Meaning

Response to the DNET RPL cnp 7-name command.

Action

None.


6-176 47 A2 94UC

TP54 STATUS . RESPONSE NOT RECEIVED RPL : rpl (01) . REQUEST NOT SENT RPL : rpl (02) . { RESPONSE RECEIVED | REQUEST SENT } RPL : rpl (03)

Meaning

Response to the DNET RPL rpl-name LONG command.

Action

See corresponding actions as for TP52.

47 A2 94UC 7-1

7. GCOS 7 Command Support

The following tables give the correspondence between GCOS 7 GCL commandsand AEP commands, and the objects to which the commands apply.

NOTE:These commands can be locally submitted for execution even when RAEH isnot activated.


7-2 47 A2 94UC

Table 7-1. GCOS 7 GCL Command/AEP Command Correspondence

GCOS 7 Command Meaning of Command AEP Command

LNET class NUMBER

LNET class [name]

DNET class [name]

DNET class [name] LONG

DNET class [name] HISTORY

MDNET class [name]

DTL

MDTL modify test inline

STL start test inline

TTL terminate test inline

List

List

Display

Display

Display @Statistics

Modify/Update

Create

Delete

Display Test Inline

Update Test Inline

Execute Test Inline

Close Test Inline

NB

LS

DA

GA

GH

UP

CB

DL

DA

UP

EX

CL

NOTE:These commands can be locally submitted for execution even when RAEH isnot activated.

GCOS 7 Command Support

47 A2 94UC 7-3

Table 7-2. Command/Object Matrix

Commands and Response Codes

Object Class CL CR DA DL EX GA GH LS NB UP

xx

xx xx

xx

xx

xx

xx

xxxx

xx

xx

xxxx

xx

xx

xx

xx

xxxxxx

xxxxxx

xx

xxxxxx

xxxx

xx

xxxx

xx

xxxxxx

xxxxxx

xx

xx

xxxx

xx

xxxxxx

xxxx

xx

xxxx

xxxx

xxxxxx

xxxxxx

xx

xx

xxxx

xx

xxxx xx xx xx

xxxxxxxx

xxxx

xxxxxx

xxxx

xxxxxx

xxxx

xxxx

xx

xxxxxxxx

xx

xxxxxxxx

xxxx

xxxxxx

xxxx

xxxxxx

xxxx

xxxx

xx xx

xxxxxx

xx

xx

xx

xx xx xx xx

xx xx

xx xx xx xxxxxxxx xx xxxx xx xx xx

xx xx xx xxxxxx xx

xx xx xxxx

xxxxxx xxxx

xx xx xxxx xx xxxxxxxx xx

ACAFAGAL

CBCC

CHCTFL

IDIS

LCLGMB

NKNROP

PCPLQD

RB

SASBSCSPSRSSSTSVSY

TCTLTSTTTXWS


7-4 47 A2 94UC

❑

47 A2 94UC 8-1

8. GCOS 7 Unsolicited Messages

8.1 Introduction

This section describes the unsolicited messages produced by GCOS 7 systemsusing system journalization.

The terminology used in the record description conforms to that for AUPI, see theAUPI User's Guide.

Each unsolicited message comprises one REGION, the "response" region. ThisREGION has one ITEM and several FIELDs.

There are four field formats:

• C: character

• N: numeric

• O: object

• B: both character and numeric The unsolicited message is described in terms ofeach field, its format (C,N,O or B), and its definition.

Optional parameters are also treated.


8-2 47 A2 94UC

GCOS 7 Unsolicited Events

Object Class

xx

xx xx

xx

xx

xx

xx

xx

xxxx

xxxx

xx

Unsolicited Event Codes

CL

xx

xx

xx

xx

xx

xx

xx

xx

xx

xx

xx

xx

xx

xx

xx

xx

xx

xx

xx

xx

xx xx

xx

xx

xx xxxx

xx

xxxx

xx

xx

xx

xx

xx xx

xx

CS ER EX FC FD FN HR OF OP

CC

CH

CT

EX

FT

FX

IS

LC

LG

NA

NK

PC

SS

SU

TC

TL

TS

Code Abbreviation-Code Name expanded------------------------------------CL-CLOSE EX-EXECUTE FN-FILE RENAMECS-COMPLETED STARTUP FC-FILE CREATE HR-HISTORY REPORTER-ERROR FD-FILE DELETE OF-OPEN FAILURE OP-OPEN

GCOS 7 Unsolicited Messages

47 A2 94UC 8-3

Summary of GCOS 7 Unsolicited Messages

The numbers correspond to AEP parameter numbers generated by GCOS 7.

CC OPEN 1->7,15,16 OPEN FAIL 1->7,10,11,15,16 CLOSE 1->7,10,11,15,16 ERROR 1->9 HISTORY REPORT 1->11

CH ERROR 1,2,7,8

CT ERROR 1,2,7,8

EX HISTORY REPORT 1

FT OPEN 1->13,17 OPEN FAIL 1->13,15->17 CREATE 1->8,15->17 DELETE 1,2,4->8,15->17 RENAME 1->8,15->17 CLOSE 1->13,15->17 ERROR 1->10,15->17 HISTORY REPORT 1->11,16->20

FX AF OPEN 1->6 AF OPEN FAIL 1->8 AF CLOSE 1->8 AF ERROR 1->9

IS OPEN 1,2,4,6,8->18 OPEN FAIL 1,2,4,6,8->20 CLOSE 1,2,4,6->18,[19],[20] HISTORY REPORT 1,2,4,6->10,16

LC OPEN 1->7,10->12 OPEN FAIL 1->7,10->13 CLOSE 1->7,10->13 HISTORY REPORT 1->7,10->13,16->20,23

LG OPEN 1->3 OPEN FAIL 1->3,5,6 CLOSE 1->4,[5],[6]

NA ERROR 1,2,7,8

NK HISTORY REPORT 1,2,8->11,13->17


8-4 47 A2 94UC

SS OPEN 1->4,6->9,13->15 OPEN FAIL 1->4,6->9,12->15 CLOSE 1->4,6->9,12->15 HISTORY REPORT 1->4,6->13,16->20,23

SU STARTUP COMPLETED 1,2TC OPEN 1->3,6,7,11,12,14 OPEN FAIL 1->3,6,7,11->14 CLOSE 1->3,6,7,11->14 ERROR 1,2,7,8 HISTORY REPORT 1->3,6->10,12->19,26,27

TL EXECUTION 1->3,6,7 CLOSE 1->3,5,6 HISTORY REPORT 1->3,5->13 ERROR 1->3,5->11,14

TS ERROR 1,7

NOTE:The symbol -> includes all values within the range denoted. TL applies only toBNSE, see Section 9.


47 A2 94UC 8-5

8.2 CC : Unsolicited Messages for Channel Connections

8.2.1 Channel Connection Open

The CC (Channel Connection) has been successfully established.

FUNCTION: 0,0

CLASS : 31 (CC channel connection)

CODE : 7 (OP open)

PARAM 1 : B INDEX channel connection index assigned by GCOS 7

PARAM 2 : O LCENDPNT name of CH establishing the connection

PARAM 3 : O RMENDPNT name of image CH mapping the connection

PARAM 4 : O CC lower level supporting connection on which : O LC the CH is multiplexed. : O SS Note : GCOS 7 currently supports only CC. : O TC

PARAM 5 : O CC higher level supported connection using : O LC the CH. : O SS Note : GCOS 7 currently supports only LC.

PARAM 6 : C IN_OR_AC initiator or acceptor

PARAM 7 : B RMPLUG remote plug number

PARAM 8 : B EVENT_MS time of event in milliseconds

PARAM 9 : B DELAY delay

PARAM12 : B LCPLUG local plug number identifying the channel connectionPARAM15 : C LCSC local session control name

PARAM16 : C RMCS remote session control name


8-6 47 A2 94UC

8.2.2 Channel Connection Open Fail

An attempt to establish the CC has failed.

FUNCTION: 0,0


CODE : 17 (OP open failure)










PARAM10 : B REASON identification of error

PARAM11 : C SYSINFO system-specific error or status information

PARAM12 : B LCPLUG local plug number identifying the channel connectionPARAM15 : C LCSC local session control name



47 A2 94UC 8-7

8.2.3 Channel Connection Close

The CC has been closed normally.

FUNCTION: 0,0


CODE : 8 (CL close)





PARAM 5 : O CC higher level supported connection using : O LC the CH. : O SS Note: GCOS 7 currently supports only LC.





PARAM10 : B REASON identification of error

PARAM11 : C SYSINFO system-specific error or status information

PARAM12 : B LCPLUG local plug number identifying the channel connection

PARAM15 : C LCSC local session control name



8-8 47 A2 94UC

8.2.4 Channel Connection Error

An error has been detected on an inter-system channel.

FUNCTION: 0,0


CODE : 14 (ER error)





PARAM 5 : O CC higher level supported connection using : O LC the CH. : O SS Note: GCOS 7 currently supports only LC.



PARAM 8 : B REASON identification of error

PARAM 9 : C SYSINFO system-specific error or status information


47 A2 94UC 8-9

8.2.5 Channel Connection History Report

GCOS 7 reports an incremental history of the Channel Connection triggered by aperiodic timer or on termination of the connection.

FUNCTION: 0,0


CODE : 4 (HR history report)








PARAM 8 : B ELT number of letters sent over the CC

PARAM 9 : B RLT number of letters received over the CC

PARAM10 : B EDA number of bytes sent over the CC

PARAM11 : B RDA number of bytes received over the CC


8-10 47 A2 94UC

8.3 CH : Unsolicited Messages for Channel

Channel Error

An error has been detected on an inter-system channel.

FUNCTION: 0,0

CLASS : 25 (CH channel)


PARAM 1 : C NAME identifies the channel

PARAM 2 : B STATE state of channel at time of error

PARAM 3 : C HW_ADDR hardware address of channel


PARAM 8 : C SYSINFO I/O completion code resulting from error


47 A2 94UC 8-11

8.4 CT : Unsolicited Messages for Controller

Controller Error

An error has been detected on a controller.

FUNCTION: 0,0

CLASS : 13 (CT controller)


PARAM 1 : C NAME identifies the controller

PARAM 2 : B STATE state of controller at time of error

PARAM 3 : C HW_ADDR hardware address of controller


PARAM 8 : C SYSINFO I/O completion code resulting from error


8-12 47 A2 94UC

8.5 EX : Unsolicited Messages for Executive

Executive History Report

GCOS 7 reports statistics on the local DPS 7 periodically, every 3 minutes bydefault.

FUNCTION: 0,0

CLASS : 19 (EX executive GCOS)


PARAM 1 : B INTERVAL interval in seconds covered by report

PARAM 2 : B USED_CAP percentage of used CPU during interval

PARAM 3 : B MEAN_MEM mean free memory available for non-executive use during interval

PARAM 4 : B MIN_MEM minimum free memory available for non-executive use during interval

PARAM 5 : B MAX_MEM maximum free memory available for non-executive use during interval

PARAM 6 : B IOS number of I/Os

PARAM 7 : B_MAX_WKSP maximum workspace available to system

PARAM 8 : B ACT_WKSP actual workspace available to system

PARAM 9 : B PC_NB number of physical connections

PARAM10 : B LK_NB number of link connections


47 A2 94UC 8-13

PARAM11 : B VC_NB number of virtual circuits

PARAM12 : B TC_NB number of transport connections

PARAM13 : B LC_NB number of logical connections

PARAM14 : B SS_NB number of sessions

PARAM15 : B DX_NB number of device connections

PARAM16 : B LX_NB number of logical device connections

PARAM17 : B SX_NB number of station connections

PARAM18 : B BUF_SIZE size of memory unit


8-14 47 A2 94UC

8.6 FT : Unsolicited Messages for File Transfers

NOTE:In the text describing the parameter functions, the term "known to the reportingsystem" has the following meanings:

If the system creating the AEP record is the REQUESTOR, the files at both theREQUESTOR and SERVER sites are known.

Otherwise, if the system creating the AEP record is the SERVER, only the file atthe SERVER site is known.

8.6.1 File Transfer Open

A transfer to or from a file in an external system has been acknowledged andsuccessfully opened.

Initiator: The initiator has received an ACK to "Open RemoteFile".

Acceptor: The acceptor has sent an ACK to "Open Remote File".

FUNCTION: 2,0

CLASS : 54 (FT file transfer)

CODE : 7 (OP open)

PARAM 1 : B INDEX local file transfer index assigned by GCOS 7

PARAM 2 : C RMT_SCID remote system session control

PARAM 3 : C ORIGFILE name of origin file if known to reporting system

PARAM 4 : C DESTFILE name of destination file if known to reporting system

PARAM 5 : C USER user identifier of requestor

PARAM 6 : C PROJECT project identifier of requestor

PARAM 7 : C BILLING billing identifier of requestor


47 A2 94UC 8-15

PARAM 8 : C FILE_TYP file organization and format char(4) : file organization, values as follows - SEQ sequential REL relative IND indexed EIND extended indexed GIND general indexed RAND random UNST unstructured LINQ link queued IDS2 ids-2 L6R2 l6 r2 fixed relative L6R5 l6 r5 fixed relative BYST byte stream char(1) : [/] char(m) : file format, values as follows - GFRC 66 BFAS 64 UFAS 6/66 UFAS 36-bit UFAS 64 UFAS/ANS/ASCII UFAS EBCDIC non-UFAS 6 IBM non-VSAM IBM VSAM foreign

PARAM 9 : C TRANSFER transfer direction SD for sender; RC for receiverPARAM10 : C ACTIV_ID uft file transfer request identifier

PARAM11 : B FIRSTREC first record number to transfer

PARAM12 : C COMPRESS data compression indicator CM for compression; NC for no compression

PARAM13 : C CHECKPNT checkpoint indicator CK for checkpoint; NK for no checkpoint

PARAM14 : B DELAY duration request was held in seconds before processing began

PARAM17 : C RQ_OR_SV role of uft RQ for requestor; SV for server


8-16 47 A2 94UC

8.6.2 File Transfer Open Fail

An attempt to open a transfer to or from a file in an external system has terminatedabnormally.

The initiator receives a NACK to an Open Remote File.

FUNCTION: 2,0


CODE : 17 (OF open failure)









47 A2 94UC 8-17


PARAM 9 : C TRANSFER transfer direction SD for sender; RC for receiver

PARAM10 : C ACTIV_ID uft file transfer request identifierPARAM11 : B FIRSTREC first record number to transfer





8-18 47 A2 94UC

PARAM15 : B REASON reason for failure hex-4 values as follows - x'2200' normal termination x'2201' immediate shutdown x'2202' unsupported message x'2203' message out of sequence x'2204' illegal message contents x'2205' illegal turn handling x'2206' unsupported session usage x'2207' timeout x'22FF' abnormal termination at requestor x'23FF' abnormal termination at server

PARAM16 : C SYSINFO system-specific information char(1) : uft-severity, possible values are 0, 1 or 2 char(1) : uft-class, values as follows - 0 ftp 1 session 2 presentation 3 file/data management 4 system 5 higher level application 6 other char(4) : uft reason code char(n) : message text



47 A2 94UC 8-19

8.6.3 File Transfer File Create

File management reports on the action to create a file for use in a file transfer.

FUNCTION: 2,0


CODE : 100 (FC file creation)



PARAM 3 : C OLD_FILE model or old file name if known to reporting system

PARAM 4 : C NEW_FILE new or deleted file name if known to reporting system





8-20 47 A2 94UC


PARAM15 : B REASON hex-4 values as follows - x'2200' normal termination x'2201' immediate shutdown x'2202' unsupported message x'2203' message out of sequence x'2204' illegal message contents x'2205' illegal turn handling x'2206' unsupported session usage x'2207' timeout x'22FF' abnormal termination at requestor x'23FF' abnormal termination at server


47 A2 94UC 8-21




8-22 47 A2 94UC

8.6.4 File Transfer File Delete

File management reports on the action to delete a file.

FUNCTION: 2,0


CODE : 101 (FD file deletion)









47 A2 94UC 8-23





8-24 47 A2 94UC

8.6.5 File Transfer File Rename

File management reports on the action to rename a file.

FUNCTION: 2,0


CODE : 102 (FN file rename)



PARAM 3 : C OLD_FILE model or old file name if known to reporting system







47 A2 94UC 8-25





8-26 47 A2 94UC

8.6.6 File Transfer Close

A transfer to/from a file in an external system has terminated.

Initiator: The initiator has received an ACK to Close RemoteFile.

Acceptor: The acceptor has sent an ACK to a Close Remote Filefrom the initiator.

FUNCTION: 2,0


CODE : 8 (CL close)









47 A2 94UC 8-27


PARAM 9 : C TRANSFER transfer direction SD for sender; RC for receiverPARAM10 : C ACTIV_ID uft file transfer request identifier

PARAM11 : B FIRSTREC first record number to transfer





8-28 47 A2 94UC

PARAM15 : B REASON reason for termination hex-4 values as follows - x'2200' normal termination x'2201' immediate shutdown x'2202' unsupported message x'2203' message out of sequence x'2204' illegal message contents x'2205' illegal turn handling x'2206' unsupported session usage x'2207' timeout x'22FF' abnormal termination at requestor x'23FF' abnormal termination at server




47 A2 94UC 8-29

8.6.7 File Transfer History Report

The GCOS executive reports statistics on the file transfer after the transfer hasterminated.

FUNCTION: 2,0












8-30 47 A2 94UC


PARAM10 : C ACTIV_ID uft file transfer request identifierPARAM11 : C RQ_OR_SV role of uft RQ for requestor; SV for server

PARAM16 : B EPD number of data records sent

PARAM17 : B EDA number of data bytes sent

PARAM18 : B RPD number of records received

PARAM19 : B RDA number of data bytes received

PARAM20 : B CHP number of checkpoints


47 A2 94UC 8-31

8.6.8 File Transfer Error

An error has occurred during a transfer to or from a file in an external system, butdoes not affect the file transfer itself.

FUNCTION: 2,0












8-32 47 A2 94UC


PARAM10 : C ACTIV_ID uft file transfer request identifierPARAM15 : B REASON reason for error hex-4 values as follows - x'2200' normal termination x'2201' immediate shutdown x'2202' unsupported message x'2203' message out of sequence x'2204' illegal message contents x'2205' illegal turn handling x'2206' unsupported session usage x'2207' timeout x'22FF' abnormal termination at requestor x'23FF' abnormal termination at server




47 A2 94UC 8-33

8.7 FX: Unsolicited Messages for AF Connections

8.7.1 AF Connection Open

The AF has successfully established a connection with an AC, independently ofwhich correspondent is the initiator or acceptor of the connection.

FUNCTION: 3,0

CLASS : 18 (FX administrative function connection)

CODE : 7 (OP open)

PARAM 1 : C LCAF_MBX local AF mailbox name

PARAM 2 : C LCAFTYPE local AF type

PARAM 3 : C RMSC remote session control name

PARAM 4 : C RMAF_MBX remote AF mailbox name

PARAM 5 : C RMAFTYPE remote AF type

PARAM 6 : C IN_OR_AC local AF initiator or acceptor IN for initiator; AC for acceptor


8-34 47 A2 94UC

8.7.2 AF Connection Open Fail

The AF NAD has unsuccessfully attempted a connection with an AC,independently of which correspondent is the initiator or acceptor of the connection.

FUNCTION: 3,0









PARAM 7 : B REASON reason for the failure

PARAM 8 : C SYSINFO system-specific information


47 A2 94UC 8-35

8.7.3 AF Connection Close

The AF NAD has terminated the connection with one of its ACs.

FUNCTION: 3,0


CODE : 8 (CL close)







PARAM 7 : B REASON reason for the termination



8-36 47 A2 94UC

8.7.4 AF Connection Error

The AF NAD has discarded UMs destined for any of the correspondents. Eachcorrespondent connected to the AF NAD receives this "event" UM, indicating thenumber of records potentially lost.

FUNCTION: 3,0









PARAM 7 : B REASON reason for the error


PARAM 9 : B LOSS_CNT number of aep records lost


47 A2 94UC 8-37

8.8 IS : Unsolicited Messages for ISO Sessions

8.8.1 ISO Session Connection Open

An ISO session connection system has been acknowledged and successfullyopened.

Initiator: The initiator has received an S-CONNECT confirmpositive (AC) after sending an S-CONNECT request(CN).

Responder: The responder has sent an S-CONNECT responsepositive (AC) after receiving an S-CONNECTindication (CN).

FUNCTION: 0,0

CLASS : 105 (IS ISO session connection)CODE : 7 (OP open)

PARAM 1 : B INDEX session index assigned by GCOS 7

PARAM 2 : C SS_CTRL iso session control

PARAM 4 : O TC lower-level connection supporting iso : O CC session, either tc or cc

PARAM 6 : C INITRESP initiator or responder IN for initiator; RE for responder

PARAM 8 : B FCT_UNIT functional units over the connection, see ISO8327

PARAM 9 : B PRTC_VER protocol version

PARAM10 : C SENDSEGM sending segmentation YS for segmentation; NO for no segmentation

PARAM11 : B SMAXTSDU maximum size in bytes of TSDU sent

PARAM12 : C RECVSEGM receiving segmentation YS for segmentation; NO for no segmentation

PARAM13 : B RMAXTSDU maximum size in bytes of TSDU received 0 = no limit


8-38 47 A2 94UC

PARAM14 : C E_CONCAT extended concatenation reception YS for concatenation;NO for no concatenation

PARAM15 : B PRV_PRTY private priority

PARAM16 : B PAIR_IDX index of opposite end of internal connection

PARAM17 : C CALLING calling selector

PARAM18 : C CALLED called selector


47 A2 94UC 8-39

8.8.2 ISO Session Connection Open Fail

An attempt to open an ISO session connection has terminated abnormally.

Initiator: The initiator has received an S-CONNECT confirmnegative (RF) after sending an S-CONNECT request(CN).

Responder: The responder has sent an S-CONNECT responsenegative (RF) after receiving an S-CONNECTindication (CN).

FUNCTION: 0,0

CLASS : 105 (IS ISO session connection)






PARAM 8 : N FCT_UNIT functional units over the connection, see ISO8327

PARAM 9 : N PRTC_VER protocol version







PARAM16 : B PAIR_IDX pair index


8-40 47 A2 94UC


PARAM18 : C CALLED called selectorPARAM19 : N REASON reason code : values in first byte are 0 : rejection by called SS; reason not specified 1 : rejection by called SS-user due to congestion 2 : rejection by called SS-user; up to 512 bytes following first byte may contain user data 128 + 1 : session selector unknown 128 + 2 : SS-user not attached to SSAP 128 + 3 : SPM congestion at connect time 128 + 4 : protocol versions not supported 128 + 5 : rejection by SPM; reason not specified

PARAM20 : C SYSINFO complementary code


47 A2 94UC 8-41

8.8.3 ISO Session Connection Close

The ISO session connection has terminated for the following reasons :

1. RE release

2. UA user abort

3. PA provider abort

RE Requestor:The requestor has received an S-RELEASE confirmpositive (DN) after sending an S-RELEASE request(FN).Acceptor:The acceptor has sent an S-RELEASE responsepositive (DN) after sending or receiving an S-RELEASE indication (FN).

UA Requestor:The requestor has sent an S-UABORT request (AB).Acceptor:The acceptor has received an S-UABORT indication(AB).

PA On the one side:The local (or remote) service provider has sent an S-PABORT request.On the other side:The remote (or local) service provider has received anS-PABORT request.

FUNCTION: 0,0


CODE : 8 (CL close)





PARAM 7 : C CL_ORIGN close origin


8-42 47 A2 94UC

PARAM 8 : B FCT_UNIT functional units over the connection, see ISO8327PARAM 9 : B PRTC_VER protocol version









PARAM18 : C CALLED called selector

PARAM19 : B REASON reason code : values of bits in first byte bit 1=0 : transport connection retained =1 : transport connection released bit 2=1 : user abort bit 3=1 : protocol abort bit 4=1 : no reason bits 5-8 : reserved

PARAM20 : C SYSINFO complementary code


47 A2 94UC 8-43

8.8.4 ISO Session Connection History Report

The GCOS executive reports statistics on the ISO session after the connection hasterminated.

FUNCTION: 0,0







PARAM 7 : B EDU number of SPDUs sent

PARAM 8 : B RDU number of SPDUs received

PARAM 9 : B EDO number of data bytes sent

PARAM10 : B RDO number of data bytes received



8-44 47 A2 94UC

8.9 LC : Unsolicited Messages for Logical Connections

8.9.1 Logical Connection Open

The logical connection with an external system has been successfully opened.

Initiator: The initiator has received an ILCAL with zero"reason" after it has sent an ILCRL to the acceptor.

Acceptor: The acceptor has sent an ILCAL with zero "reason"after it has received an ILCRL from the initiator.

FUNCTION: 0,0

CLASS : 12 (LC logical connection)

CODE : 7 (OP open)

PARAM 1 : B INDEX logical connection index assigned by GCOS 7

PARAM 2 : O LMB name of local mailbox

PARAM 3 : O RMB name of correspondent mailbox

PARAM 4 : O TC lower-level supporting connection, : O CC either tc or cc

PARAM 5 : O SS higher-level supported connection

PARAM 6 : C IN_OR_AC initiator or acceptor IN for initiator; AC for acceptor

PARAM 7 : B LC_ID dialog protocol identifier of connection



PARAM10 : B M_SUBCH maximum number of subchannels

PARAM11 : B S_LTSIZE maximum size of letter sent in bytes

PARAM12 : B R_LTSIZE maximum size of letter received in bytes


47 A2 94UC 8-45

8.9.2 Logical Connection Open Fail

An attempt to open a logical connection with an external system has terminatedabnormally.

An ILCAL has been built with a non-zero "reason" explaining the failure to openthis connection.

FUNCTION: 0,0















PARAM13 : B REASON reason for failure, either GCOS 7 reason or reported from lower layers (DNS or CNS7)

PARAM14 : C SYSINFO system-specific information


8-46 47 A2 94UC

8.9.3 Logical Connection Close

The logical connection with an external system has terminated.A TLCL has been built with a non-zero "reason" explaining if termination is due toa request from the correspondent or as the result of a timeout.

Initiator: The initiator has received a TLCL after sending thesame or on timeout.

Acceptor: The acceptor has sent a TLCL after receiving the same.

FUNCTION: 0,0


CODE : 8 (CL close)













PARAM13 : B REASON reason for termination, either GCOS 7 reason or reported from lower layers (DNS or CNS7)

PARAM14 : C SYSINFO system-specific information


47 A2 94UC 8-47

8.9.4 Logical Connection History Report

GCOS 7 reports the incremental statistical history of a logical connection triggeredeither by a periodic timer or on termination of the logical connection.

FUNCTION: 0,0










PARAM10 : B EDA number of application data characters sent

PARAM11 : B ESY number of system data characters sent

PARAM12 : B ERS number of record segments sent

PARAM13 : B ERC number of records sent

PARAM14 : B ERU number of sru's sent

PARAM15 : B ERL number of release sru's sent

PARAM16 : B ELT number of letters sent

PARAM17 : B RDA number of application data characters recd

PARAM18 : B RSY number of system data characters received

PARAM19 : B RRS number of record segments received

PARAM20 : B RRC number of records received

PARAM21 : B RRU number of sru's received


8-48 47 A2 94UC

PARAM22 : B RRL number of release sru's received

PARAM23 : B RLT number of letters received

PARAM24 : B EQU number of quarantine units sent

PARAM25 : B RQU number of quarantine units received

PARAM26 : B XRU number of recovery units

PARAM27 : B XIU number of interaction units


47 A2 94UC 8-49

8.10 LG : Unsolicited Messages for Administrative Logs

8.10.1 Administrative Logfile Open

The AF ASF has opened a logfile of the SYS.DSALOGi set or the SYS.<lg-name>iset to journalize records.

FUNCTION: 3,0

CLASS : 49 (LG administrative log)

CODE : 7 (OP open)

PARAM 1 : C NAME name of LG : DSALOG or <lg-name>

PARAM 2 : C CUR_FILE name of current file

PARAM 3 : C PRV_FILE name of previous file


8-50 47 A2 94UC

8.10.2 Administrative Logfile Open Fail

The AF ASF has detected a system error when opening a logfile.

FUNCTION: 3,0





PARAM 3 : C PRV_FILE name of previous file

PARAM 5 : N REASON reason for failure, see Section 8



47 A2 94UC 8-51

8.10.3 Administrative Logfile Close

The AF ASF has closed a logfile of the SYS.DSALOGi set or the SYS.<lg-name>iset after having journalized records on it.

FUNCTION: 3,0


CODE : 8 (CL close)



PARAM 3 : C NXT_FILE name of next file

PARAM 4 : B TIME_OP time the file was opened

PARAM 5 : B REASON reason for close



8-52 47 A2 94UC

8.11 NA : Unsolicited Messages for NAD

NAD Error

An error has occurred in the AF NAD or AF MUX.

FUNCTION: 0,0

CLASS : 36 (NA nad)


PARAM 1 : C NAME name of the AF NAD : LNAD

PARAM 2 : C STATE resulting state

PARAM 7 : B REASON reason for error



47 A2 94UC 8-53

8.12 NK : Unsolicited Messages for Internet Network Activity

These are the GCOS executive report statistics on Internet network activity.

8.12.1 Internet Network Activity History Report

FUNCTION: 0,0

CLASS : 115 (NK Internet Network Activity)


PARAM 1 : B INDEX NK index assigned by GCOS 7

PARAM 2 : O LCENDPT name of local transport station

PARAM 8 : B NKETU number of data requests emitted

PARAM 9 : B NKRTU number of data indications received

PARAM10 : B NKFSU number of subnetwork data indications forwarded

PARAM11 : B NKRDI number of data units discarded due to congestion

PARAM13 : B NKREA number of address error class report PDUs received

PARAM14 : B NKRES number of service routing class error report PDUs received

PARAM15 : B NKREL number of lifetime class error report PDUs received

PARAM16 : B NKRED number of PDU discard class error reports received

PARAM17 : B NKRER number of re-assembly class error reports received


8-54 47 A2 94UC

8.13 SS : Unsolicited Messages for Sessions

8.13.1 Session Open

A session with an external system has been successfully opened.

Initiator: The initiator has received an ILCAL with zero"reason" after it has sent an ILCRL to the acceptor.

Acceptor: The acceptor has sent an ILCAL with zero "reason"after it has received an ILCRL from the initiator.

FUNCTION: 0,0

CLASS : 11 (SS session)

CODE : 7 (OP open)

PARAM 1 : B INDEX session index

PARAM 2 : O LMU name of local mailbox. : O LMB Note : GCOS 7 currently supports only MB. : O LTX

PARAM 3 : O RMU name of remote mailbox. : O RMB Note : GCOS 7 currently supports only MB. : O RTX

PARAM 4 : O LC lower-level supporting connection on which : O CC the SS is multiplexed. : O TC Note : GCOS 7 currently supports only LC.

PARAM 5 : O SX station connection index


PARAM 7 : B LC_ID logical connection identifier

PARAM 8 : B SUB_CH subchannel number

PARAM 9 : B SS_NB session number on subchannel

PARAM10 : B EVENT_MS time of event in milliseconds

PARAM11 : B DELAY delay

PARAM13 : C PERSON user identifier

PARAM14 : C PROJECT project identifier

PARAM15 : C BILLING account identifier


47 A2 94UC 8-55

8.13.2 Session Open Fail

An attempt to open a session with an external system has terminated abnormally.An ILCAL has been built with a non-zero "reason" explaining the failure to openthis session.

FUNCTION: 0,0














PARAM12 : B REASON reason for failure, either GCOS 7 reason or reported from lower layers (DNS or CNS7)





8-56 47 A2 94UC

8.13.3 Session Close

The session with an external system has terminated.

Initiator: The initiator has received a Terminate-Session recordafter sending the same or on timeout.

Acceptor: The acceptor has sent a Terminate-Session record afterreceiving the same.

FUNCTION: 0,0


CODE : 8 (CL close)












PARAM12 : B REASON reason for termination, either GCOS 7 reason or reported from lower layers (DNS or CNS7)





47 A2 94UC 8-57

8.13.4 Session History Report

GCOS 7 reports the incremental history of a session either triggered by a periodictimer or on termination of the session.

FUNCTION: 0,0












PARAM10 : B EDA number of application data characters sent

PARAM11 : B ESY number of system data characters sent

PARAM12 : B ERS number of record segments sent

PARAM13 : B ERC number of records sent

PARAM14 : B ERU nb of terminate session recovery units sent

PARAM15 : B ERL nb of release session recovery units sent

PARAM16 : B ELT number of letters sent


8-58 47 A2 94UC

PARAM17 : B RDA number of application data characters recd

PARAM18 : B RSY number of system data characters received

PARAM19 : B RRS number of record segments received

PARAM20 : B RRC number of records received

PARAM21 : B RRU nb of terminate session recovery units recd

PARAM22 : B RRL nb of release session recovery units recd

PARAM23 : B RLT number of letters received

PARAM24 : B EQU number of quarantine units sent

PARAM25 : B RQU number of quarantine units received

PARAM26 : B XRU number of session recovery units

PARAM27 : B XIU number of interaction units


47 A2 94UC 8-59

8.14 SU : Unsolicited Messages for System Startup

System Startup Completed

GCOS 7 reports its restart or reload. This message is sent only once to eachadministrative correspondent.

FUNCTION: 0,0

CLASS : 3 (SU system startup)

CODE : 60 (CS completed startup)

PARAM 1 : C IDENT system identification

PARAM 2 : C MOT message of the day


8-60 47 A2 94UC

8.15 TC : Unsolicited Messages for Transport Connections

8.15.1 Transport Connection Open

The transport connection with an external system has been successfully opened.

Initiator: The initiator has received an FL-CC after it has sent anFL-CT to the acceptor.

Acceptor: The acceptor has sent an FL-CC after it has receivedan FL-CT from the initiator.

FUNCTION: 0,0

CLASS : 21 (TC transport connection)

CODE : 7 (OP open)

PARAM 1 : B INDEX transport connection index assigned by GCOS 7


PARAM 3 : O RMENDPT name of remote transport station

PARAM 4 : O NC lower-level supporting connection on which : O NK the TC is multiplexed. : O PC : O VC

PARAM 5 : O CC higher-level supported connection using the : O IS TC. : O LC : O SS : O TC





PARAM10 : C OPTION transport protocol used for connection

PARAM11 : B MAXCRDTR maximum credit the receiver can process


47 A2 94UC 8-61

PARAM12 : B FRAGLGT maximum negotiated fragment length

PARAM14 : B LCPLUG local plug number

PARAM15 : C LCSC_ID origin session control identifier

PARAM16 : C RMSC_ID destination session control identifier

PARAM27 : C ALT_PRTC alternative protocol class

PARAM28 : B VC_FAIL number of vc failures

PARAM29 : B QOS_PRTY priority of quality_of_service

PARAM30 : C CLG_NSAP calling nsap address

PARAM31 : C CLD_NSAP called nsap address

PARAM32 : C CLG_TSEL calling t-selector

PARAM33 : C CLD_TSEL called t-selector

PARAM34 : B QOS_THPT quality_of_service throughput

PARAM35 : B QOS_MIN minimum qos throughput acceptable

PARAM36 : B QOSDELAY qos transit delay

PARAM37 : B QOSDLMAX maximum qos delay acceptable


8-62 47 A2 94UC

8.15.2 Transport Connection Open Fail

An attempt to open a transport connection with an external system has terminatedabnormally.

Initiator: The initiator has received an FL-DC or FL-DT aftersending an FL-DT or on timeout.

Acceptor: The acceptor has sent an FL-DC or FL-DT.

FUNCTION: 0,0















PARAM13 : B REASON identification of failure


47 A2 94UC 8-63




PARAM17 : N specific error (CLNS, DIWS, INET only). See Appendix F.










PARAM36 : B QOSDELAY quality_of_service transit delay



8-64 47 A2 94UC

8.15.3 Transport Connection Close

The transport connection with an external system has terminated.

Initiator: The initiator has received a Terminate-TC record aftersending the same or on timeout.

Acceptor: The acceptor has sent a Terminate-TC record afterreceiving the same.

FUNCTION: 0,0


CODE : 8 (CL close)













PARAM13 : B REASON identification of termination



47 A2 94UC 8-65



PARAM17 : N specific error (CLNS, DIWS, INET only). See Appendix F.










PARAM36 : B QOSDELAY quality_of_service transit delay



8-66 47 A2 94UC

8.15.4 Transport Connection Error

An error has been detected on a transport connection.

FUNCTION: 0,0





PARAM 6 : C IN_OR_AC initiator or acceptor (INET only) IN:initiator AC:acceptor See Appendix F.



PARAM 9 : N specific error (CLNS, DIWS, INET only). See Appendix F.


47 A2 94UC 8-67

8.15.5 Transport Connection History Report

The GCOS executive reports statistics on the transport connection after theconnection has terminated.

FUNCTION: 0,0










PARAM 8 : B EPD nb of data fragments sent and acknowledged

PARAM 9 : B EPC number of command fragments sent

PARAM10 : B ETO number of acknowledgement timeouts

PARAM11 : B ERJ nb of rejects recd requiring re-transmission

PARAM12 : B EDU number of fragments re-transmitted

PARAM13 : B EWC number of times window closed

PARAM14 : B EWT time window closed

PARAM15 : B ESD nb of letters recd from session control for re-transmission on the transport connection


8-68 47 A2 94UC

PARAM16 : B RPD number of data fragments correctly received

PARAM17 : B RPC number of command fragments received

PARAM18 : B RDU number of duplicate fragments received

PARAM19 : B RSD number of letters received on the transport connection and passed to session control

PARAM20 : B RCR mean credit sent in acknowledgement to this connection

PARAM21 : B EWS mean window size sent in acknowledgement to this connection

PARAM22 : B EOF number of fragments emitted and awaiting acknowledgement

PARAM23 : B RTT total roundtrip time

PARAM24 : B NSAM number of samples

PARAM25 : B NNL nominal losses

PARAM26 : B EXD number of expedited data fragments sent

PARAM27 : B RXD number of expedited data fragments received

PARAM28 : B EDA number of data bytes sent in tsdu

PARAM29 : B RDA number of data bytes received and accepted in tsduPARAM30 : B RSY number of times re-synchronization occurred

PARAM31 : B RAS number of times re-assignment occurred


47 A2 94UC 8-69

8.16 Tl : Unsolicited Messages for Tests

8.16.1 Test Routine Execute

GCOS 7 reports the initiation of a BNSE test.

FUNCTION: 0,0

CLASS : 51 (TL test routine)

CODE : 7 (EX execute)

PARAM 1 : B ID test identifier assigned by GCOS 7

PARAM 2 : C NAME name of the test

PARAM 3 : C SUB_NAME name of the subtest

PARAM 6 : O OBJECT name of object under test

PARAM 7 : B REASON reason code


8-70 47 A2 94UC

8.16.2 Test Routine Close

GCOS 7 reports that a BNSE test has terminated.

FUNCTION: 0,0


CODE : 8 (CL close)



PARAM 3 : C SUB_TEST name of the subtest


PARAM 6 : B REASON reason code


47 A2 94UC 8-71

8.16.3 Test Routine History Report

BNSE reports statistics on the test, once the test has completed.

FUNCTION: 0,0






PARAM 4 : B ROUTINE routine identifier


PARAM 6 : B ELAPSE duration of test in seconds

PARAM 7 : B ITER number of iterations of test

PARAM 8 : B START_T time when test was started

PARAM 9 : B STOP_T time when test was terminated

PARAM10 : B S_BYTES number of bytes sent

PARAM11 : B R_BYTES number of bytes received

PARAM12 : B S_RECORD number of records sent

PARAM13 : B R_RECORD number of records received


8-72 47 A2 94UC

8.16.4 Test Routine Error

BNSE has detected an error during the execution of a test.

FUNCTION: 0,0






PARAM 4 : B ROUTINE routine identifier


PARAM 6 : B ELAPSE duration of test in seconds

PARAM 7 : B ITER number of iterations of test

PARAM 8 : B REASON reason for the error

PARAM 9 : C ERR_TEXT text of error

PARAM10 : B B_SOURCE source of error

PARAM11 : B B_REASON error code

PARAM12 : C S_MESS message sent

PARAM13 : C R_MESS message received

PARAM14 : B ERR_POS position of error


47 A2 94UC 8-73

8.17 TS : Unsolicited Messages for Transport Station

8.17.1 Transport Station Error

An error has been detected on a transport station.

FUNCTION: 0,0

CLASS : 9 (TS transport station)

PARAM 1 : C NAME identifies the transport station

PARAM 2 : C STATUS state of the named TS



8-74 47 A2 94UC

❑

47 A2 94UC 9-1

9. Basic Network Session Exerciser (BNSE)

9.1 Purpose and General Description of BNSE

The purpose of BNSE is to confirm that between 2 systems

• the session is established

• and, data transfer at application level is operational.

BNSE is a tool which provides a controlled environment for establishing sessionsand transferring data over those sessions. This tool operates online and does notdisrupt normal network traffic.

The operation of BNSE is based on an initiator and an acceptor. This techniquerequires the presence of certain exerciser components at the two systems under test.

The purpose of the BNSE test is

• to initiate or accept a session with another BNSE test

• to confirm that a session can be established between their respective mailboxes

• to submit the session to a specified load test

• and, to trace and report errors in the execution of session control interfacecommands.

There are two BNSE tests active during any test session. One assumes the role ofinitiator while the other, normally located in another system, assumes the role ofacceptor.


9-2 47 A2 94UC

9.2 Configurations in the Primary Network

BNSE is a standard exerciser for all DSA systems. It is designed and implementedto test connection with another DPS 7000.

VCAM

TNS

FEPS

CNP7

Datanet

primary network

initiator mbx:$NSE BNSEI

acceptor BNSEAmbx:$NSE

remote system

remote system

initiatorBNSEI

mbx:$NSE

BNSE

mbx:$NSE

BNSEAacceptor

local DPS 7000

The diagram shows the local DPS 7000 connected to 2 separate DPS 7000s, eachacting respectively as initiator and acceptor. The local DPS 7000 fulfils thefunction of both initiator and acceptor of the separate BNSE sessions.

The mailbox names shown are the defaults. In order to distinguish initiator andacceptor, the suffixes I and A are respectively used.

Basic Network Session Exerciser (BNSE)

47 A2 94UC 9-3

9.3 SIDE Option

The SIDE option allows BNSE to function either as initiator or acceptor.

Each side can operate in either ECHO or DROP according to the execution options.

9.3.1 Acceptor Side

The purpose of the acceptor side is to dialog with the initiator side which definesthe parameters of the test.

The acceptor side waits a maximum lapse-time of 20 minutes for the session to beestablished. If the connection is not established within that period, the test stopswith a TIMEOUT error.

When the connection is established, the test is executed by the acceptor sidethrough parameters sent by the initiator side, namely

if the test is ECHO, the message received from the initiator side is echoed back

• if the test is DROP, the message received from the initiator side is checkedagainst the reference message and is then ignored

• when all test messages are sent, the session terminates.

When the current session terminates, the acceptor side analyzes the iterationnumber to find out if another session must be opened in the same test. As manysessions as specified by the iteration number are opened, and then, the last sessionterminates. The iteration number is one of the parameters defined by the initiatorside.


9-4 47 A2 94UC

9.3.2 Initiator Side

The initiator side defines the parameters of the test. It requests sessionestablishment and waits a maximum lapse-time of 20 minutes for the acceptor toacknowledge the request to open the session. If the connection cannot beestablished within that period, the test stops with a TIMEOUT error.

When the connection is established, the test is executed according to theparameters selected :

• if the test is ECHO, it sends a message, then on receiving it back, checks thatboth messages are identical

• if the test is DROP, it sends a message to which no response is required

• when the required number of messages have been sent, it terminates the session.

When the session terminates, the initiator side analyzes the iteration number andthe elapse time (if specified) to know if another session has to be opened for thesame test. When the number of iterations or the elapse time is exhausted, the testsession terminates.

Basic Network Session Exerciser (BNSE)

47 A2 94UC 9-5

9.4 How to Start a BNSE Test

Both initiator and acceptor test activities are managed through specific TL mainoperator commands:

• STL (Start_Test_inLine)

• TTL (Terminate_Test_inLine)

• DTL ( Display_Test_inLine)

• MDTL (MoDify_Test_inLine)

• the maximum number of STL commands processed in parallel is set at 100

• one and only one BNSE job processes all currently active TL commands

• refer to the Network Operations Manual for further information on the use ofvarious commands.

9.5 Outputs of a BNSE Test

There is no implicit USER and CLASS for the JOB (the user is usually theOPERATOR).

The results of a BNSE test are unsolicited messages which report the testexecution, test history, test close and test error.

When the test executes normally, no output listing is produced.

If the test detects a critical error, a sysout listing is produced as follows :

• the Job Occurrence Report

• the report of execution (error reporting optional)

• and, possibly a dump.

When an error is detected during the test, a brief error message (NA99) is printedin the report of execution which explains the reason of the abnormal termination.This error reporting completes the trace of unsolicited messages.


9-6 47 A2 94UC

❑

47 A2 94UC 10-1

10. Maintainability

A GCOS 7 operator can send commands to a remote NAD by specifying the nameof the remote node (via the SYSTEM parameter) in the command (DNET, LNET,and MDNET). However, he/she can also use the passthrough facility via the EDDcommand.

10.1 Passthrough for Dialog with the FEP

Passthrough allows the DPS 7000 main operator to connect to and dialog with theDatanet or CNP 7.

To do this, the operator connects to the $NOI mailbox. At the request of theService Center, the operator may connect to the $DEBUG mailbox.

In this section, although only $NOI is mentioned, $DEBUG is an alternative whichcan be used instead for maintenance purposes only.

Using passthrough, the operator can issue commands to $NOI and receiveresponses, while still remaining connected to, and operating GCOS. There is noneed to disconnect.

Passthrough is invoked by the EDD command which activates an FECMoccurrence.


10-2 47 A2 94UC

10.1.1 Activation and Deactivation

Prior to any command, the FECM server must first be started up to provide accessto the passthrough. This server executes in an operator's job: ADM_EDD.

The ADM_EDD job is started up by the command:

EDD START

When FECM is started and is ready to process operator commands, the followingprompt appears on all operator consoles:


Since only one occurrence of FECM can be active on a given DPS 7000, anotherEDD START command is rejected. However, FECM is ready to process any otherEDD command. FECM is inactive if no command is issued to it or if it does notreceive a response from the Datanet or CNP 7. If FECM remains inactive for anhour, it is terminated by GCOS.

The user can also terminate FECM by the command:

EDD TERMINATE

When the FECM occurrence terminates, a prompt appears on all operator consoles:


However, if FECM was not previously activated by the EDD START command,the following error message appears:

*** ILLEGAL STATEMENT NAME: FECM

Maintainability

47 A2 94UC 10-3

10.1.2 Connection and Disconnection

Once FECM starts, connection to the $NOI is established by entering thecommand:

EDD RSYS=rsys-name APPL=$NOI CONNECT PASSWORD=password

If the connection is successful, the operator receives the response:

FE45 rsys-name $NOI CONNECTION IS ESTABLISHED

When the connection request fails, the operator is informed with the response:

FE46 rsys-name $NOI CONNECTION CANNOT BE ESTABLISHED

and the reason codes for the reject are printed. The meaning of the reason codesfor rejections are described in the DSA Network System Messages and ReturnCodes.

NOTE:Before any connection to $DEBUG, the state of the mailbox must be set toENBL by the $NOI command:

UP MB $DEBUG -ST ENBL.

Up to 20 connections can be simultaneously active.

Any user can operate a connection. Two operators dialoging through a passthroughcan share the same connection. In this case, no checks are made concerning theinitiator of the connection. Commands can then be issued alternately by eachoperator in turn. Should such a situation occur, both operators must ensure thatneither disconnects without the other knowing. When dialog terminates,disconnection from the mailbox is through the following command:

EDD RSYS=rsys-name APPL=$NOI DISCONNECT

The response to this command appears on the operator's console:

FE47 rsys-name $NOI IS DISCONNECTED

No further dialog with the application concerned can be activated until anotherconnection is established.


10-4 47 A2 94UC

10.1.3 Default Values

$NOI is the default for APPL.

Where the EDD command applies to only one application executing in one system,the arguments for RSYS and APPL can be specified as defaults by the followingcommand:

EDD RSYS=rsys-name APPL=$NOI SETDFLT

These are the values that will be provided for RSYS and/or APPL in a subsequentEDD command if the corresponding parameter is not specified.

These remain defaults until another subsequent EDD command with SETDFLT isissued.

However, an EDD command can be issued to another RSYS for another APPL,without affecting the default values.

SETDFLT enables the RSYS and APPL arguments to be retained and used as thevalue to be taken if a subsequent EDD command does not specify thecorresponding parameter.

10.1.4 Dialog

Once a connection is established with $NOI, dialog can be activated by theoperator.

The operator issues a DNS or CNS 7 command to obtain a response from theDatanet or CNP 7.

To send a command to the Datanet or CNP 7, key in the entry:

EDD COMMAND='{ dns-command|cns7-command }'RSYS=rsys-name APPL=$NOI

If the RSYS and APPL already have default values through a previous EDDcommand specifying SETDFLT, they can be omitted.

NOTE:If the DNS or CNS 7 command contains an apostrophe, an additionalapostrophe must be used to conform to GCL syntax rules.

Maintainability

47 A2 94UC 10-5

10.1.5 Interrupt

When a response from $NOI is too long and the remaining messages are notneeded, it may be interrupted by the command:

EDD RSYS=rsys-name APPL=$NOI ITCMD

Nothing will be sent from $NOI until another command towards this mailbox isissued.

10.1.6 Display Connections

As only one FECM occurrence is active to handle many passthrough connectionswhich may have been activated by more than one operator, the EDD DISPLAYcommand enables listing all connections and their states.

The states may be:

• NOT CONNECTED• CONNECTION IN PROGRESS• CONNECTED• BUSY BY COMMAND IN PROGRESS• DISCONNECTION IN PROGRESS

A command to $NOI is accepted only when its state is CONNECTED.


10-6 47 A2 94UC

10.1.7 Outputs on Console and SYSOUT

The response from the Datanet or CNP 7 appears on the same console at which thecommand is issued.

If the response is not to be printed on the console, it can be held by the command:

EDD RSYS=rsys-name APPL=$NOI HMSG

The corresponding responses will no longer be printed until an EDD commandwith the RMSG parameter is issued to release the messages.

In addition to the console, the commands and the responses are printed onSYSOUT or placed in a member of SYS.DSACONF to keep a trace of the activityduring passthrough processing.

If the responses do not need to be printed on SYSOUT or placed in a member ofSYS.DSACONF, the operator can hold output messages by the command:

EDD RSYS=rsys-name APPL=$NOI HOMSG

The corresponding responses will no longer be printed on SYSOUT until an EDDcommand with the ROMSG parameter is issued to release output messages.

The commands and responses can be placed in a member of the SYS.DSACONFlibrary as follows:

EDD PRTLIB = CONFxxxx

where CONF represents SYS.DSACONF and xxxx (up to 4 characters) is the nameof the member.

Maintainability

47 A2 94UC 10-7

EXAMPLE:

S: EDD START 09.19 X3541 IN EDD DTSOPER P SPR=6 MAIN 09.18 X3541 STARTED EDD DTSOPER P JB08 X3541.1 STEP H_FECM DPR=6 J=15 FE41 FECM STARTED FOR ENTER_DSA_DIALOGS: EDD RSYS=BP3B APPL=$NOI SETDLFTS: EDD CONNECT PASSWORD=BP47 FE45 BP3B $NOI CONNECTION IS ESTABLISHEDS: EDD CD='DA MB $DEBUG' 09.21 BP3B $NOI DNS BP3B :09:21:39 MB NAME STAT TYPE MAP1 MAP2 $DEBUG LOCK USER : SC:BP3BS: EDD CD='UP MB $DEBUG -ST ENBL' 09.22 BP3B $NOI DNS BP3B :09:22:22 MB NAME OATT NATT RPRT $DEBUG LOCK ENBLS: EDD APPL=$DEBUG CONNECT PASSWORD=UNCP FE46 BP3B $DEBUG CONNECTION CANNOT BE ESTABLISHED: BYTE2="00"X, BYTE3="1A"XS: EDD COMMAND='DA SR CNP 7' 09.24 BP3B $NOI DNS BP3B :09:24:29 SR NAME STAT TYPE MAP1 MAP2 CNP 7 ENBL ISO SC:BP47 TS:CNP 7S: EDD APPL=$DEBUG CONNECT PASSWORD=BUG FE45 BP3B $DEBUG CONNECTION IS ESTABLISHEDS: EDD DISPLAY FE40 BP3B $NOI CONNECTED FE40 BP3B $DEBUG CONNECTEDS: EDD APPL=$DEBUG CD='PO' 09.32 BP3B $DEBUG CNT LV ITCB CDID IR R1 R2 R3 R4 R5 R6 R7 B1 B2 B3 B4 B5 B6 B7 09.32 BP3B $DEBUG THAT'S ALL FOLKS ... THE TRACE COUNT IS NOW 000S: EDD DISCONNECT APPL=$DEBUG FE47 BP3B $DEBUG IS DISCONNECTEDS: EDD DISCONNECT FE47 BP3B $NOI IS DISCONNECTEDS: EDD DISPLAY FE39 NO ACTIVE CONNECTIONS: EDD TT FE42 FECM COMPLETED FOR ENTER_DSA_DIALOG❑


10-8 47 A2 94UC

10.2 Passthrough for Dialog with the MainWay 2600LE

A GCOS 7 operator can send commands to a MainWay 2600LE by using thepassthrough facility via the EDD command.

Passthrough allows the DPS 7000 main operator to connect to and dialog with theMainWay 2600LE.

To do this, the operator connects to the $NOI mailbox.

Using passthrough, the operator can issue commands to $NOI and receiveresponses, while still remaining connected to, and operating GCOS.There is no need to disconnect.

Passthrough is invoked by the EDD command which activates an FECMoccurrence.

Activation and Deactivation

Prior to any command, the FECM server must first be started up to provide accessto the passthrough. This server executes in an operator's job: ADM_EDD.

The ADM_EDD job is started up by the command:

EDD START

When FECM is started and is ready to process operator commands, the followingprompt appears on all operator consoles:


Since only one occurrence of FECM can be active on a given DPS 7000/XTA,another EDD START command is rejected. However, FECM is ready to processany other EDD command. FECM is inactive if no command is issued to it or if itdoes not receive a response from the MainWay 2600LE. If FECM remains inactivefor an hour, it is terminated by GCOS.

The user can also terminate FECM by the command:

EDD TERMINATE

When the FECM occurrence terminates, a prompt appears on all operator consoles:


However, if FECM was not previously activated by the EDD START command, thefollowing error message appears:

*** ILLEGAL STATEMENT NAME: FECM

Maintainability

47 A2 94UC 10-9

Connection and Disconnection

Once FECM starts, connection to the $NOI is established by entering thecommand:

EDD RSYS=rsys-name APPL=$NOI CONNECT PASSWORD=password

If the connection is successful, the operator receives the response:

FE45 rsys-name $NOI CONNECTION IS ESTABLISHED

When the connection request fails, the operator is informed with the response:

FE46 rsys-name $NOI CONNECTION CANNOT BE ESTABLISHED

and the reason codes for the reject are printed. The meaning of the reason codes forrejections are described in the DSA Network System Messages and Return Codes.

Up to 20 connections can be simultaneously active.

Any user can operate a connection. Two operators dialoging through a passthroughcan share the same connection. In this case, no checks are made concerning theinitiator of the connection. Commands can then be issued alternately by eachoperator in turn. Should such a situation occur, both operators must ensure thatneither disconnects without the other knowing. When dialog terminates,disconnection from the mailbox is through the following command:

EDD RSYS=rsys-name APPL=$NOI DISCONNECT

The response to this command appears on the operator's console:

FE47 rsys-name $NOI IS DISCONNECTED

No further dialog with the application concerned can be activated until anotherconnection is established.


10-10 47 A2 94UC

Default Values

$NOI is the default for APPL.

When the EDD commands apply to only one application executing in one system,the arguments for RSYS and APPL can be specified as defaults by the followingcommand:

EDD RSYS=rsys-name APPL=$NOI SETDFLT

These are the values that will be provided for RSYS and/or APPL in a subsequentEDD command if the corresponding parameter is not specified.

These remain defaults until another subsequent EDD command with SETDFLT isissued.

However, an EDD command can be issued to another RSYS for another APPL,without affecting the default values.

SETDFLT enables the RSYS and APPL arguments to be retained and used as thevalue to be taken if a subsequent EDD command does not specify thecorresponding parameter.

Dialog

Once a connection is established with $NOI, dialog can be activated by theoperator.

The operator issues a MainWay 2600LE command to obtain a response from it.

To send a command to the MainWay 2600LE, key in the entry:

EDD COMMAND='{ MainWay 2600LE command }' RSYS=rsys-name APPL=$NOI

If the RSYS and APPL already have default values through a previous EDDcommand specifying SETDFLT, they can be omitted.

NOTE:If the MainWay 2600LE command contains an apostrophe, an additionalapostrophe must be used to conform to GCL syntax rules.

Maintainability

47 A2 94UC 10-11

Interrupt

When a response from $NOI is too long and the remaining messages are notneeded, it may be interrupted by the command:

EDD RSYS=rsys-name APPL=$NOI ITCMD

Nothing will be sent from $NOI until another command towards this mailbox isissued.

Display Connections

As only one FECM occurrence is active to handle many passthrough connectionswhich may have been activated by more than one operator, the EDD DISPLAYcommand enables listing all connections and their states.

The states may be:

• NOT CONNECTED

• CONNECTION IN PROGRESS

• CONNECTED

• BUSY BY COMMAND IN PROGRESS

• DISCONNECTION IN PROGRESS

A command to $NOI is accepted only when its state is CONNECTED.

Outputs on Console and SYSOUT

The response from the MainWay 2600LE appears on the same console at which thecommand is issued.

If the response is not to be printed on the console, it can be held by the command:

EDD RSYS=rsys-name APPL=$NOI HMSG

The corresponding responses will no longer be printed until an EDD commandwith the RMSG parameter is issued to release the messages.

In addition to the console, the commands and the responses are printed onSYSOUT or placed in a member of SYS.DSACONF to keep a trace of the activityduring passthrough processing.

If the responses do not need to be printed on SYSOUT or placed in a member ofSYS.DSACONF, the operator can hold output messages by the command:

EDD RSYS=rsys-name APPL=$NOI HOMSG


10-12 47 A2 94UC

The corresponding responses will no longer be printed on SYSOUT until anEDD command with the ROMSG parameter is issued to release output messages.

The commands and responses can be placed in a member of the SYS.DSACONFlibrary as follows:

EDD PRTLIB = CONFxxxx

where CONF represents SYS.DSACONF and xxxx (up to 4 characters) is the nameof the member.

EXAMPLE

S: EDD START 13.18 X243 IN ADM_EDD USER=SIOUX CLASS=P SPR=7 STATION=BC05 13.18 X243 STARTED ADM_EDD SIOUX P FE41 FECM STARTED FOR ENTER_DSA_DIALOG

S: EDD RSYS=BC86 APPL=$NOI SETDFLT

S: EDD CONNECT PASSWORD=XXXX FE45 BC86 $NOI CONNECTION IS ESTABLISHED

S: EDD DISPLAY FE40 BC86 $NOI CONNECTED

S: EDD CD='DA MB $NOI' 13.38 BC86 $NOI DNS-E BC86 :13:38:56 MB NAME STAT TYPE MAP1 MAP2 $NOI USED ADM : SC:BC86

S: EDD DISCONNECT FE47 BC86 $NOI IS DISCONNECTED

S: EDD DISPLAY FE39 NO ACTIVE CONNECTION

BC05: EDD TT FE42 FECM COMPLETED FOR ENTER_DSA_DIALOG 13.41 X245.1 COMPLETED ADM_EDD SIOUX P❑

Maintainability

47 A2 94UC 10-13

10.3 Trace Facilities

Trace facilities can be used on TNS, FEPS, VCAM, and OCS Front End to obtaininformation on their functioning and performance in case of difficulty. This sectiongives an overview of these facilities.

10.3.1 VCAM Trace

The VCAM trace facility records events relating to the session layer, either ISO forVCAM-ISO or DSA for VCAM-DSA.

It is activated by the SVTR command and terminated by the TVTR command. Theactivity of the trace is monitored through the DVTR command.

When the VCAM trace is activated, the VCAM events are logged either in the fileTRC_VCAM_#userid (default) or a user-defined file on a resident or catalogedvolume. When the trace is terminated, the logfile created is scanned using theSCNVTR command.

This manual only treats the syntax of the commands concerned. For more detailedinformation on the VCAM-ISO trace facility, refer to:

• VCAM-ISO User's Guide

• VCAM-ISO Reference Manual, Volumes 1 and 2.

Information on the VCAM-DSA trace only deals with the trace collector phase.Analysis of the VCAM-DSA trace is provided by Technical Support from theprintout of the trace.


10-14 47 A2 94UC

10.3.1.1 SVTR (START_VCAM_TRACE)

Purpose

Starts the VCAM trace collector.

Syntax

{ SVTR }{ }{ START_VCAM_TRACE }

[ { { TRC_VCAM_#userid } ][ { FILE = { } ][ { { char10 [.char8] [:dvc:md] [$RES | $CAT] } ]

[ DYNALC = { CAT | UNCAT } ]

RON = { * | (ron,[ron...]) }

{ { ILVL | ILEV | VITLV } }{ { } = { 1 | ... | 15 } }{ { ISO_TRACE_LEVEL } }{ }{ }{ { DLVL | DLEV | VDTLV } }{ { } = { 1 | ... | 15 } }{ { DSA_TRACE_LEVEL } }

Maintainability

47 A2 94UC 10-15


FILE external logfile name allocated for the trace.The explicit filename must not exceed 44 characters(file_44).#userid is the name of the submitter of the SVTRcommand.

DYNALC logfile to be dynamically allocated by the VCAM tracecollector.

RON mandatory parameter specifying at least onerun_occurrence_number.

ISO_TRACE_LEVEL abbr. ILVL or ILEV or VITLVmutually exclusive to DSA_TRACE_LEVEL rangingfrom 1 (minimum) through 15 (maximum), definingthe level of VCAM-ISO trace required.

DSA_TRACE_LEVEL abbr. DLVL or DLEV or VDTLVmutually exclusive to ISO_TRACE_LEVEL rangingfrom 1 (minimum) through 15 (maximum), definingthe level of VCAM-DSA trace required.


10-16 47 A2 94UC

10.3.1.2 SCNVTR (SCAN_VCAM_TRACE)

Purpose

Scans the logfile containing the VCAM trace.

Syntax

{ SCNVTR }{ }{ SCAN_VCAM_TRACE }

[ { { TRC_VCAM_#userid } ][ { TRC_FILE = { } ][ { { char10 [.char8] [:dvc:md] [$RES | $CAT] } ]


TRC_FILE external logfile name allocated for the trace in theSVTR command. The explicit filename must notexceed 44 characters (file_44). #userid is the name ofthe submitter of the SVTR command.

NOTE:VCAM Trace Scanner Commands appear in the Menu Facility.

B (BACK) { [ 1 (default) | times ] }Returns the number of times specified from son tofather in decreasing current levels.

D (DUMP) [line] [indication] Specifies the line and number ofcharacters of the dump required.Example: DUMP 3 '.A#x32' dumps at line 3, a stringof 32 hexadecimal characters starting at A.

F (FORWARD) [line] Selects the line determining the rank in the list ofsons.

L (LOCATE) [line] Positions on the line required.

N (NEXT) [times] Skips the number of subsequent pagesspecified.

Maintainability

47 A2 94UC 10-17

MLP (MODIFY_LOCAL_PROFILE) [AUTO_DISPLAY]Enables (MLP AUTO_DISPLAY) or disables (MLP)the automatic display of the current list of sons afterexecution of each command.

P (PREVIOUS) [times] Skips the number of previous pages specifiedby times.

W (WORKSPACE) { 0 | 1 | 2 | 3 }Switches to the workspace specified.

10.3.1.3 Description of the VCAM Trace Scanner Display

Each display is divided in 3 parts:

• on the top of the display is the name of the son and its fathers, with the numberof sons also given

• the main display gives the list of sons for one father.

These sons are numbered from 0. This number is followed by an identifier whichdescribes the type of son, its structure is the record of the VCAM user traceassociated with one primitive either VCAM-ISO or VCAM-DSA. The last part ofthe line contains information on the son structure.

The T: prompt appears on the bottom line. Scanner commands can then be entered.

The level of the trace depends on the version of VCAM, as follows:

• VCAM-ISO has 2 and more levels of structures

• VCAM-DSA has only one level structure.


10-18 47 A2 94UC

VCAM-ISO TRACE

Description of First Level Structure

The following example shows a display of trace records concerning a remoteconnection that has failed at the level of the Datanet or CNP 7. The example wasproduced by specifying an NSAP which was not described in the front-endprocessor.

ROOT..VCAM_TRACE================================================= 1:15 ========== 1 SISO_OPN_SSAP B 8. 0 UA:1 2 SISO_OPN_SSAP B 7. 0 UA:1 3 SISO_CONREQ 7. 0 4 SISO_CLG_UREF 7. 0 5 SISO_CONMONRE 7. 0 6 SISO_ADDREF 7. 0 ==> 7 SISO_CONREQ A:DONE 7. 0 US:1 VS:0 8 TISO_TCONREQ A:DONE 1. 16 VS:0 9 TISO_LTSAPAD 1. 16 10 TISO_TDCNIND A:DONE 1. 16 VS:0 11 PISO_ERROR 1. 16 12 PISO_ERROR 1. 16 13 PISO_NOTIF 1. 16 US:1 VS:0 14 SISO_PABIND B 7. 0 US:1 VS:0 15 SISO_PABIND A:DONE 7. 0 US:1 VS:0=================================================================

T:

The root of the tree is a VCAM_TRACE. At this level, enter the F (FORWARD)command.

Description of Second Level Structures

These structures are associated with VCAM-ISO primitives. Each GPL primitivecalled results in a structure built by the concatenation of the explicit GPL primitiveparameters, each keyword of the GPL primitive having its own field. Thisstructure may be followed by others corresponding to indirectly related parametersexchanged through a pointer to a structure such as user data, called references andTSDUs.

Maintainability

47 A2 94UC 10-19

The 3 types of structures are denoted by the following prefixes:

• SISO_xxxx:

These are structures corresponding to the VCAM-ISO primitives. Their namesare built by concatenating SISO_ to the root of the primitive. The root of theprimitive is the name of the primitive stripped of its H_SI_ prefix. The resultingstring can be affixed with the TYPE value if it exists.

Example: SISO_CONIND for H_SI_CON TYPE=IND...;

Some structures result in only one field. In this case, their names are built byconcatenating SISO_ to the name of the parameter.

Example: SISO_COMMONREF

• TISO_xxxx:

These are structures corresponding to the interface between the session providerand the transport provider. The naming convention is the same as that forSISO_xxxx.

TISO_DATA is the name of the structure containing the TSDU. It can bedivided into SPDU, PGI and PI by the F (FORWARD) command.

• PISO_xxxx:

These are structures associated with events internal to the SS-provider whichimpact on the SS-user, namely:

PISO_ABORT:the SS-provider has decided to close the session.

PISO_ERROR:the SS-provider has detected an error. This structure resembles that ofH_DC_SI_ERROR.

PISO_NOTIF:the SS-provider has decided to notify the user or transport provider. Thisstructure contains the notifying message.

The name of the first structure associated with a VCAM-ISO primitive provides thetitle to the following information:

• Column 1 A (after) or B (before) denoting whether the VCAM primitive hasbeen executed or not, respectively. Return-code appears with A.

• Column 2 J (job) and P (process) identifies the system process group executingthe primitive.


10-20 47 A2 94UC

• Column 3 US (user) or UA (ssap) identifies the user session connection or theuser SSAP.

• Column 4 VS (vcam session) or VA (vcam ssap) identifies the VCAM sessionconnection or the VCAM SSAP.

Description Of Structures With Level Exceeding 2

These levels apply only for TSDUs exchanged between the transport provider andthe session provider. The name of the structure is TISO_DATA.

The F (FORWARD) command divides the TSDU into its descending componentsSPDU, then PGI, then PI. The names of the PGI and PI components are providedby the encoding rules of the ISO session protocol.

VCAM-DSA TRACE

Description of Single Level Structure

The following example shows a display of trace records concerning a remoteconnection with either the Datanet or CNP 7.

ROOT..VCAM_TRACE================================================= 1:230========== 46 SDSA_OPMG_UWS A:DONE 8. 0 VW:1024 47 SDSA_OPMG_UMB A:DONE 8. 0 VM:1024 48 SDSA_OPMG_MPD A:DONE 8. 0 49 TDSA_TCONREQ_TCON B 5. 0 50 TDSA_TCONREQ_LTSAPAD B 5. 0 51 TDSA_TCONREQ_RTSAPAD B 5. 0 ==> 52 TDSA_TCONREQ_QOS B 5. 0 53 TDSA_TCONREQ_USERDAT B 5. 0 54 TDSA_TCONREQ_TCON A:DONE 5. 0 VS:2 55 TDSA_TCONREQ_LTSAPAD A:DONE 5. 0 56 TDSA_TCONREQ_RTSAPAD A:DONE 5. 0 57 TDSA_TCONIND_TCON B 5. 0 58 TDSA_TCONIND_LTSAPAD B 5. 0 59 TDSA_TCONIND_RTSAPAD B 5. 0 60 TDSA_TCONIND_TCON A:DONE 5. 0 VS:1024 61 TDSA_TCONIND_LTSAPAD A:DONE 5. 0 62 TDSA_TCONIND_RTSAPAD A:DONE 5. 0 63 PDSA_NOTIF A:DONE 5. 0 64 TDSA_TCONRSP_TCON B 5. O VS:1024=================================================================

T:

Maintainability

47 A2 94UC 10-21

The F (FORWARD) command is only used to select the VCAM trace after theSCNVTR command has been entered for DSA sessions. There are no more levelstructures.

The 3 types of structures are denoted by the following prefixes:

• SDSA_xxxx:

These are structures corresponding to the VCAM-DSA primitives. Their namesare built by concatenating SDSA_ to the root of the primitive and the parameterabbreviation. The root of the primitive is the name of the primitive stripped ofits H_prefix.

Example: SDSA_OPMG_UWS

for H_OPMG on UWS (User WorkStation)

• TDSA_xxxx:

These are structures corresponding to the interface between the session providerand the transport provider. The naming convention is the same as that forSDSA_xxxx with the concatenation of the parameter name.

Example: TDSA_TCONIND_LTSAPAD

TDSA_xxxx_DATA is the name of the structure containing user data.

• PDSA_xxxx:

These are structures associated with events internal to the SS-provider whichimpact on the SS-user, namely:

PDSA_ERROR:the SS-provider has detected an error.PDSA_NOTIF:the SS-provider has decided to notify the user or transport provider. Thisstructure contains the notifying message.


10-22 47 A2 94UC

The name of the first structure associated with a VCAM-DSA primitive providesthe title to the following information:

• Column 1 A (after) or B (before) denoting whether the VCAM primitive hasbeen executed or not, respectively. Return-code appears with A.

• Column 2 J (job) and P (process) identifies the system process group executingthe primitive.

• Column 3:− US (user) identifies the user session connection− UM identifies the user mailbox− UW identifies the user workstation.

• Column 4:− VS (vcam) identifies the VCAM session connection− VM identifies the VCAM mailbox− VW identifies the VCAM workstation.

10.3.2 TNS, OCS and FEPS File Trace

TNS and FEPS file traces are activated by the operator through the STTRcommand. A more detailed trace of these servers can be obtained through theDBSVR command but only at the request of the Service Center. For TNS, theevents are logged in the file TRC_TNS_TNS. For the FEPS occurrence, events arelogged in TRC_FEPS_feps-name.

The trace file is dynamically allocated if it does not exist. It is a UFAS file of1Megabytes on the resident disk. A file of a different size, at least 128K bytes, canbe pre-allocated for the TNS/FEPS trace mechanism to use.

The trace file may be allocated on another media through the DBSVR command, asshown in the following examples:

Examples for Handling User-defined Trace Files

• To open a trace file RST.TRC1 cataloged in RST.CATALOG: DBSVR TNS MD TRACE_FILE=RST.TRC1$CAT;

or DBSVR TNS MD TRACE_FILE=RST.TRC1 FILESTAT=CAT;

• To open a trace file TRC1 on the media specified: DBSVR TNS MD TRACE_FILE=TRC1:SVLT8B:MS/D500;

• To return to the default options resident, uncataloged and file name: DBSVR TNS MD FILESTAT=DEFAULT;

For the syntax of the DBSVR command, see paragraph 10.2.6.

Maintainability

47 A2 94UC 10-23

When TNS, FEPS or OCS abort, a file trace is automatically activated to logthe last server events present in memory. The names of these files arerespectively TRC_TNS_TNS_Xron, TRC_FEPS_feps-name_Xron andTRC-OCS_ocs_name_Xron. The size of each file is 128 Kbytes rounded upto the nearest cylinder.

When the trace file is closed through the TTTR command (or DBSVRTRACE=OFF), it must be printed out using the PRTTR command.For each process of the server, the events are traced in a set of memory pagesbelonging to a trace context whose number is identical to the process number.The distributed buffer pool is traced in the context 4.

To trace the coding in the LM memory space, a dedicated context must be allocatedfor each distributed function which manages its own access conflicts.

There is one context for each server process. There are 3 processes in FEPS(from 0 to 2), 4 processes in TNS (from 0 to 3) and 9 processes for each OCS.There is another context for the buffer management named context 4 for FEPS andTNS and named context 9 for OCS.

The DBSVR command can optionally be used to provide the trace for UFT,see paragraph 10.2.4 "UFT TRACE".

Header Banner for TNS Trace

********************************************************************* GCOS7 TRACE ******** VERSION: 10.00 DATED: DEC 15, 1991 *********TRC_TNS_TNS_X2406******************************************* +---------------- | | | +-> caption identifies the TNS trace

****** OPTIONS ****** >> FILE=TRC_TNS_TNS_X2406,PROCESS=*,PRT132 +--------------------- | +-> file name of TNS trace as in caption


10-24 47 A2 94UC

Header Banner for FEPS Trace

********************************************************************* GCOS7 TRACE ******** VERSION: 10.00 DATED: DEC 15, 1991 *********TRC_FEPS_UNCP_X305****************************************** +---------------- | | | +-> caption identifies the trace of FEPS occurrence UNCP

****** OPTIONS ****** >> FILE=TRC_FEPS_UNCP_X305,PROCESS=*,PRT132 +--------------------- | +->file name of FEPS trace as in caption

Header Banner for OCS Trace

********************************************************************* GCOS7 TRACE ******** VERSION: 11.00 DATED: OCT 26, 1993 *********TRC_OCS_NCC1************************************************ +---------------- | | +-> caption identifies the trace of OCS occurrence NCC1

TRACE FILE (FICH_RST ) = TRC_OCS_NCC1 CAT = NO RES = YESMD:DVC = TIME = LOCALDELETE = Y SERVER = TYPE: OCS NAME: NCC1START LOG = 12:58:37.067 FEB 14, 1994 TDEV = 00:00

Maintainability

47 A2 94UC 10-25

Titles in First Printout Page (OCS)

--------------------------------------- XRON PGID CONTEXT 156 000E 0--------------------------------------- | | | | | |+-> domain of the trace (0 - 8) | | | |+-> defines the Process Group from which the | trace has been taken: | +-> RON of the OCS servers job

Titles in First Printout Page (FEPS and TNS)

-------------------------- XRON J CONTEXT 2406 04 4 +--- +- +- | | +-> defines the LM process or the SM context from | | which the trace has been taken : | | FEPS process : 0, 1 and 2 | | TNS process : 0, 1, 2 and 3 | | XBF context : 4 | | | +-> job number of the product code | +-> corresponds to xron appearing in the caption and OPTIONS file--------------------------

Titles heading Data (FEPS, TNS, OCS)

The titles in the heading of the long format are stacked in 2 levels because of thelack of space on the page. For the actual printout, the titles of the long formatappear in a single line header followed by another header giving the titles of theshort format.


10-26 47 A2 94UC

Titles heading Data in Long Format (FEPS, TNS, OCS)

Read the titles starting at LID and ending at TOTL-->LONG as follows:

LID OBJ SUB TIME_DAY.TOD_FT/LT S CTX DP LGTH INDX ADDR.TOTL->LONG

LID SUB_NAME S DP INDX TOTL-->LONG+-- ---v---- - -+ --v- ---+ ---+|OBJ_NAME |TIME_OF_DAY.---TOD_FT/LT |CTX |LGTH |ADDRESS. | ||+------- |+----------------------- |--+ |---+ |------+ | ||| || | | | | | | | ||| ||severity or trace level<+ | | | | | | ||| || | | | | | | ||| || context (process number)<-+ | | | | | ||| || | | | | | ||| || displacement from Level 1<-+ | | | | ||| || | | | | ||| || length of data traced<-+ | | | ||| || | | | ||| || index (array subscript) optional<-+ | | ||| || | | ||| || address of level 1 trace<-+ | ||| || | ||| || cumulative total of lgth's<-+ ||| || ||| || long data format<-+|| |||| |+->time of day (FT:first time / LT:last time)|| | (1) hh:mm:ss.milliseconds|| | (2) hexadecimal|| | data entries for FT and LT appear vertically stacked|| ||| +->SUBDOMAIN entry point of procedure|||+->OBJECT|+->line identifier, trace point in procedure

Maintainability

47 A2 94UC 10-27

Titles heading Data in Short Format (FEPS, TNS, OCS)

LID OBJ_NAME SUB_NAME TIME_OF_DAY.-----TOD---- S CTX DATA-->SHORT+--------------------------------------------------- ---+ ----+| | || | || | |+->see long format for definition except for TOD entry: | | TOD for short format appears as a single entry | | | | | | hexadecimal printout of trace<-+ | | | short data format<-+


10-28 47 A2 94UC

10.3.3 OCS Trace Facility

Trace Overview

OCS traces are activated via the STTR command.

A more detailed trace of this server can be obtained via the DBSVR command.You should execute the DBSVR command only at the request of your ServiceCenter.

OCS events are logged in the file TRC_OCS_<server-name>. If this file does notexist, it is created dynamically.

In case of OCS abort, a file trace is automatically activated to log the last serverevents present in memory. The name of this file is TRC_OCS_<OCS-server-name>_Xron.

Once the trace file is closed (via a TTTR or DBSVR TRACE = OFF command), itmust be printed using a PRTTRF command.

For each process of the server, the events are traced in a set of memory pagesbelonging to a trace context.

Trace Contexts

For OCS, the following 10 contexts (from 0 to 9) are defined:

PPAS context #0TSI context #1SNMP context #2 SNMP agentTRACE context #3RST-trace context #4IPSS context #5CONF context #6ADMA context #7LIPS context #8SNMP context #9 SNMP manager

The distributed buffer pool is traced in context #8.

Maintainability

47 A2 94UC 10-29

10.3.4 UFT Server Trace

The UFT trace is activated by the operator through the STTR command. A moredetailed UFT trace can be obtained through the DBSVR command but only at therequest of the Service Center.

UFT events are not logged in a file, unlike TNS or occurrences of FEPS. Instead,UFT events appear either at the end of the file transfer in the JOR or with the filetransfer in the resulting SYSOUT report.

10.3.5 Debugging Applications

The main purpose of the DBSVR facility is to analyze the behavior of the TNS andFEPS servers through the protocol layers from 1 to 4.

However, a set of DBSVR commands adapted for debugging applicationsconnected either through TNS or occurrences of FEPS is available in the librarySYS.HSLLIB. By using this facility, the user can trace the connections through theserver concerned at the moment that the application was debugged.

The procedure for using this set of commands is given for each server.

To debug an application connected through TNS:

1. To start logging:AI S_DBSVR_TNS LIB=SYS.HSLLIB

2. To terminate logging:AI T_DBSVR_TNS LIB=SYS.HSLLIB

3. To print the trace log:PRTTRF TNS PROCESS=0

To debug an application connected through an FEPS occurrence, first copy thefollowing system members in a user-defined library denoted your-library under auser-defined file name of the FEPS occurrence denoted feps-name:

• SYS.HSLLIB..S_DBSVR_FEPS to your-library..S_DBSVR_feps-name• SYS.HSLLIB..T_DBSVR_FEPS to your-library..T_DBSVR_feps-nameProceed as follow:

1. To start logging:AI S_DBSVR_feps-name LIB=your-library

2. To terminate logging:AI T_DBSVR_feps-name LIB=your-library

3. To print the trace log:PRTTRF feps-name PROCESS=0


10-30 47 A2 94UC

10.3.6 DBSVR (DEBUG_SERVER)

The DBSVR command is intended for maintenance purposes only and is reservedfor the Service Center. However, the operator may be requested by the ServiceCenter to enter this command.

Purpose

Displays and/or modifies trace parameters and contexts. The DBSVR commandcan also be used to select a media for the trace file. See Examples.

Syntax

{ { TNS } } { SVR } { { ocs-name } }DBSVR { } = { { feps-name } } { SERVER } { } { UFT }

[ { D } ] [ { { 0 } } ] [ { 0 } ][ { } ] [ { LOG = { } } ] [,SUFFIX = { } ][,ACTION = { MD } ] [ { { 1 } } ] [ { 1 } ][ { } ] [,{ } ][ { BOTH } ] [ { { 0 } } ] [ { NEWLOG = { } } ] [ { { 1 } } ]

[ { DOM } { * } ] [ { DB } { 0 } ][, { } = { } ] [, { } = { } ][ { DOMAIN } { name-14 } ] [ { DEBUG } { 1 } ]

[ {SDOM } {* }] [ {LVL } ] [ {SEV } ][, { }={ }] [, { }=dec-2] [, { }=dec-2][ {SUBDOMAIN} {name-8}] [ {LEVEL} ] [ {SEVERITY} ]

[ { * } ][, OBJECT = { } ][ { name-8 } ]

[ { ON | OFF } ][ { } ][, TRACE = { ADDR ,ADDRESS = hexa-8 } ][ { } ][ { POSVAL ,POSITION = hexa-6 ,VALUE = hexa-8 } ]

Maintainability

47 A2 94UC 10-31

[ { DEFAULT } ][, FILESTAT = { } ][ { { CAT | UNCAT } [ TRACE_FILE = name-44 ] } ]

[ {MB1 } ][,{MB }={char-8} ][ {MBX1 } ]

[ {MB2 } ][,{MB }={char-8} ][ {MBX2 } ]

[ {MB3 } ][,{MB }={char-8} ][ {MBX3 } ]


SERVER up to 8 alphanumeric characters, identifying the serverconcerned.

ACTION Specifies the action to be taken:

D: Display (default), not applicable for UFTMD: Modify, applicable for all serversBOTH: Display and Modify, not applicable for UFT

LOG mutually exclusive to NEWLOG.

Concerns the state of the file trace:LOG=1: Start the file traceLOG=0: Stop the file traceAbsent: Log left in preceding state unchanged.

The following parameters apply only to FEPS occurrences and TNS.

NEWLOG mutually exclusive to LOG.

Determines the state of the current file trace:

NEWLOG=1: Stops the current file trace and starts anew one with SUFFIX

NEWLOG=0: Meaningless

Absent: Log remains in previous state as-is.


10-32 47 A2 94UC

SUFFIX Specifies the suffix of the file trace name:

SUFFIX=1: Suffix name with _XRON_i, where i startsat 0 and is incremented by 1 on each entry of theDBSVR LOG=1 command over the same SVR andXRON.

SUFFIX=0: No suffix.

DOMAIN A set of SUBDOMAINs having similar functions.

To list all the DOMAINS, enter:

DBSVR svr-name [D] DOMAIN=*

To modify the DEBUG attributes of a DOMAIN,enter:DBSVR svr-name {MD|BOTH} DOMAIN={*|name}DEBUG={0|1}

DEBUG Specifies the values for the SUBDOMAIN traceparameters of a given DOMAIN:

DEBUG=0: The trace mechanism ignores the actualvalues of the subdomains. All subdomains areconsidered as having the attributes LVL=0 andSEV=15.

DEBUG=1: The actual values of the subdomains areonly taken into consideration when DEBUG=1.

SUBDOMAIN Corresponds to a procedure or an entry point into aprocedure. The subdomain-name and the line-idappearing in the edited trace uniquely identify a pointin the trace.Each SUBDOMAIN has its own attributes, LEVELand SEVERITY, and its own debugging maintenanceparameters available to the Service Center.

LEVEL Specifies the trace depth by subdomain. It ismeaningless when DEBUG=0. Values are 0(minimum) to 15 (maximum).

SEVERITY Specifies the gravity of an incident at and above whichthe trace is to be automatically started. Values are 0(not significant) to 15 (serious).

Maintainability

47 A2 94UC 10-33

OBJECT Specifies the object concerned in ACTION.

The following attributes apply to an identified object.

TRACE specifies the trace criteria.ADDRESS, POSITION and VALUES are maintenanceparameters which provide complementary information.

TRACE Specifies how the trace session is handled:

TRACE=ON: Write the information on the object inmemoryTRACE=OFF: No information is to be written (notrace)TRACE=ADDR: Trace on ADDRESS givenTRACE=POSVAL: Trace on POSITION andVALUES given

ADDRESS Level 1 address of the data trace.ADDRESS is valid only with TRACE=ADDR.

POSITION Displacement from Level 1 of the data trace.POSITION must be specified with VALUES.POSITION and VALUES are valid only withTRACE=POSVAL.

VALUES String of up to 16 paired hexadecimal digits split overseveral fields. When the value specified matches theposition defined by ADDRESS and POSITION, a traceis taken.

VALUES must be specified with POSITION.POSITION and VALUES are valid only withTRACE=POSVAL.

FILESTAT Status of the trace file.

DEFAULT: file is Resident but Uncataloged;TRACE_FILE is not required. For name of the tracefile, see TRACE_FILE 1 File Resident butUncataloged

CAT: cataloged; TRACE_FILE must be specified. Forname of the trace file, see TRACE_FILE 2 CatalogedFile

UNCAT: uncataloged; TRACE_FILE must bespecified. For name of the trace file, seeTRACE_FILE 3 File Non-resident and Uncataloged


10-34 47 A2 94UC

TRACE_FILE Up to 44 alphanumeric characters being the name ofthe trace file of the format: file-name[:media[:device]]

Allocation of the Trace File1 File Resident but UncatalogedBy default TRACE_FILE is omitted and the name ofthe trace file according to the server, is: TRC_FEPS_server-name for FEPS TRC_TNS_TNS for TNS.

2 Cataloged FileSuch a file can be cataloged in either SYS.CATALOGor a private catalog. TRACE_FILE must be specifiedand the name of the file must be prefixed by the nameof the catalog as follows:SYS.file-name for SYS.CATALOGMYCAT.file-name for a private catalog.

3 File Non-resident and UncatalogedSuch a file must be defined in the full format:file-name:media:device

Example: TRACE_FILE=TRC1:SVLT8B:MS/D500.

MB1, MB2, MB3 For selective telecommunication trace:

Name(s) of the local or remote mailbox(es) for which atelecommunication trace is requested.Only the first connection for each mailbox is selected.Not significant for an UFT user.When these parameters are used, LOG=1 orNEWLOG=1 is mandatory.When MB2 is used, MB1 is mandatory.When MB3 is used, MB2 is mandatory.

EXAMPLES:

1. To open a trace file RST.TRC1 cataloged in RST.CATALOG, either commandformat can be used:

DBSVR TNS MD TRACE_FILE=RST.TRC1$CAT DBSVR TNS MD TRACE_FILE=RST.TRC1 FILESTAT=CAT

2. To open a trace file TRC1 on the media specified: DBSVR TNS MD TRACE_FILE=TRC1:SVLT8B:MS/D500

3. To return to the default FILESTAT option (resident but uncataloged) and thedefault trace_file name:

DBSVR TNS MD FILESTAT=DEFAULT❑

Maintainability

47 A2 94UC 10-35

10.3.7 ISL Controller

The ISL controller of the DPS 7000 is declared at network generation (NETGEN)by the LCT directive. The LNA (or LNM depending on the DPS 7000 model) isattached to the ISL which relays all network connections to the compact DPS 7000system. The LNA (or LNM) being an LCT of type ISL is serviced by TNS. EachLNA (or LNM) is identified by its Ethernet Address (EAdd).

Putting the ISL controller in trace mode is done through the STTR commandspecifying:

• the SERVER as TNS

• and the TRACE level as LNA.

The decision to do so is not the operator's responsibility but only at the expressrequest of the Service Center.

The trace involves not only the STTR and TTTR commands, but also the STSVRand TTSVR commands.

The sequence of the commands given below gives their syntax for the trace.

S: STSVR TYPE=TNS;S: MDNET LCT EAdd NEW_STATE=LOCK;S: STTR SVR=TNS TR=LNA;S: MDNET LCT EAdd NEW_STATE=ENBL; . . .S: TTTR SVR=TNS TR=RESET; (see Note 1)

[ S: TTSVR TYPE=TNS; ]

S: STSVR TYPE=FECM CT=EAdd SCENARIO=SCEN_EAdd; (see Note 2)

NOTES:1. The operator must explicitly and systematically RESET the TRACE level

of the TNS server on the termination of the trace.Such a measure ensures that a subsequent STTR TNS command does notinadvertently restart the trace.

2. The trace is to be kept for analysis by the representative of the ServiceCenter.


10-36 47 A2 94UC

10.3.8 OCS Front End Trace Facility

10.3.8.1 OCS Front End Trace Overview

The OCS Front End Trace Facility consists in:

1. collecting information from OCS Front End IPS/ISO/DIWS stack entities(layers plus drivers), located in the controller,

2. recording the information in GCOS 7 logging files on disk. This is done by alocal DPS 7000 host listener. There is a separate set of GCOS 7 disk files foreach OCS Front End being logged.

3. displaying and analysing the information logged.

The contents of the GCOS 7 logging files can be processed immediately or later.There is a trace tool editor (see the EDTRACE command) to display and assist inthe analysis of the information logged.

The network administrator can decide which information is to be logged and whichis not to be logged.

The following 7 commands are used to manage the OCS Front End trace facility:

• TRACE• NOTRACE• SEETRACE• EDTRACE• TRCTPDU• NTRCTPDU• STRCTPDU

These commands are described below.

Trace files are sequential files organized as loops (that is, while one file is beingconsulted the others are still being used for recording).

OCS Front End traces are activated/de-activated through the administrativecommands (TRACE, NOTRACE). These commands are addressed to OCS FrontEnd stream drivers and set/reset trace levels. Up to 33 trace levels can be activatedin each driver. Trace level 0 is always activated (it cannot be de-activated); it is thedefault trace level after OCS Front End software launching. (Trace level 0 isrelated to protocols and system errors and warnings.)

Each trace level can be individually altered.

Only level 0 implementation is mandatory in a stream driver. No error is returnedwhen a not implemented trace level alteration is requested.

Maintainability

47 A2 94UC 10-37

TRCTPDU, NTRCTPDU, and STRCTPDU are special versions of the TRACE,NOTRACE, and SEETRACE commands where you want the trace mechanism toaffect only TPDU (Transport Protocol Data Units) exchanged with a selectedremote node.

The name of the logging files are:

• SYS.DSATRC_<LCT name>_i• DSATRCIDX_<LCT name> file• DSATRCIDT_<Version> file

Each of these file is discussed below.

10.3.8.2 <DIR>.DSATRC_<LCT name>_i files

Each OCS Front End has its own set of files (the number goes from 2 up to 9). Thefile allocation (number and size) is performed at GCOS 7 communicationinstallation time (DIUF). At any time, an operator can modify the number of thefile or the size of each of them by using the BUILD_FILE and DELETE_FILEcommands.

The syntax of the file name must be: <DIR>.DSATRC_<LCT name>_i

<DIR> is the directory where the files are allocated. On therecording machine, DIR must be SYS. On amaintenance machine the working directory DIR canbe chosen freely.

<LCT name> identifies the OCS Front End (that the files belong to).

i (1 up to 9) is the file index.

The only file creation constraints are:

• status: CAT• type: SEQ• recform:F (fixed)• recsize:4104• cisize: 25088

For each OCS Front End, the files are organized as a loop. The loop begins at thefile whose index is 1 and ends at either:

• the file whose index is 9,• or, at the first failure to open a file.

In a file, the trace buffers are recorded sequentially until the end of file. Eachrecord is 4104 bytes long.


10-38 47 A2 94UC

10.3.8.3 <DIR>.DSATRCIDX_<LCT name> file

This file is a UFAS sequential file. It can be located either under the SYS directoryon recording machine for an immediate analysis, or under a freely chosen workingdirectory name on a maintenance machine for a deferred analysis.

There is one such file per OCS Front End. It is automatically created by the OCSserver starting on the recording machine.

Its role is to save the following information:

• to resume recording after the previous one, in cases where the OCS server hasbeen stopped and re-started,

• to inform the trace editor where the trace begins and ends.

This file contains a <Version> field which is a 4 characters string identifying theversion of the front end software. This field allows to trace editor to know whichDSATRCIDT_<Version> file to use when translating the IDENT field of tracemessage.

10.3.8.4 <DIR>.DSATRCIDT_<Version> file

This file is a sequential indexed file. It is used to translate (numeric/explanation)the IDENT field of the OCS Front End trace frame.

This file is built from the DSATRCIDT_<Version> file which is delivered in thefront end software package.

Version is formatted as Nxyy or Dxyy.

xyy is a 3 digits string which identifies the PPA software version.

For Dxyy version the equivalent file is an IOF$TEMPRY file build by theEDTRACE command from a SYS.HSLLIB member delivered in the GCOS 7software package.

10.3.8.5 OSI Stack Traceable Entities

These are:

• COTP

• CLNP

• DLPI

• TP1006 (RFC1006 layer)

Maintainability

47 A2 94UC 10-39

10.3.8.6 IPS Stack Traceable Entities

These are:

• IP• ICMP• TCP• UDP• ARP• RIP (not yet implemented)• IAM IPS administrative Module

10.3.8.7 Other Driver Traceable Entities

These are:

• IM Information Management Driver

• HINT Host Interface Driver

• CTRL Controller Driver

NOTE:The CTRL driver cannot be used on a host platform based on Bull processors.It has its own level definitions. It is able to dynamically modify itself its owntrace level setting without any warnings.

10.3.8.8 Definition of Trace Levels

- For all drivers but the CTRL one.• level 0: Trace of protocol and system errors,• level 1: Trace of PDUs that are sent by the layers,• level 2: Trace of PDUs received by the layers,• level 3 to level 9: Trace of the system adherence calls with the following

assignment:− level 3: stream message sending.− level 4: stream queue management.− level 5: stream memory management.− level 6: stream mask management.− level 7: system timer management.− level 8: system memory management.− level 9: system lock management.

• level 10: Trace of state transitions in automates.


10-40 47 A2 94UC

• level 11 to level 14: Trace for performance measurement with the followingassignment:

− level 11: (reserved for APIs).− level 12: Timer handlers instrumentation.− level 13: Stream message handling (ingoing/outgoing message

instrumentation).− level 14: Stream service interface procedures instrumentation.

• level 15: Configuration trace level. Trace of commands applied to object'sattributes during configuration process.

• level 16: Management trace level. Same as above for administration process.

• level 17: to level 18: (reserved for APIs).

• level 19: Trace of SDU and stream messages sent by the lower part of astream/driver module.

• level 20: Trace of SDU and stream messages received by the lower part of astream/driver module.

• level 21: Trace of SDU and stream messages sent by the upper part of astream/driver module.

• level 22: Trace of SDU and stream messages received by the upper part of astream/driver module.

• level 23: Internal functions, parameters trace level, trace the input and outputparameters of the functions at the beginning and at the end these functions.

• level 24: Internal functions, buffers trace level, trace the contents of buffersassociated to pointer parameters at the beginning and at the end of the functions.

• level 25: Trace of service procedure entry points in stack entities (input andoutput parameters at the beginning and at the end of the functions, return codeand addresses of buffers parameters).

• level 26: Trace and debug of internal automates.

• level 27 to 32: Development and debugging trace levels.

− For CTRL driver.

• Level 1 to 5: setting of OCS Front End internal trace level.

• Other levels are Dxyy version-dependent.

Maintainability

47 A2 94UC 10-41

10.3.9 OCS Front End Trace Management Commands

10.3.9.1 TRACE Command

Purpose

• This command is used to enable tracing of stack or driver entities. Several tracelevels can be positioned in each of them.

• 32 trace levels can be selected from trace level 1 up to trace level 32. Anadditional trace level 0 is always selected by default and cannot be disabled.

• The administrator may select any combination of above trace levels in eachentity (0 excepted) to obtain a global level of trace.

Syntax

TRACE EAnn

[name]

level = { (n[,m]...[,p]) | * }


EAnn system identification of targeted OCS Front End.

name the name of the entity the command applies to. This isa positional argument of up to 8 EBCDIC characters.If omitted, the command applies to all the driversexcept the CTRL one.Name should be one of the names returned when youexecute a SEETRACE command.Trace command on CTRL driver must always useexplicit name "CTRL".

level a positional keyword argument that precedes the tracelevel number list.If * is not specified, n, m, and p are the trace levelnumbers. Each one is up to 2 decimal digits and theyare separated by commas. The level list can containfrom 1 up to 32 level numbers. It is mandatory toindicate at least one level number.


10-42 47 A2 94UC

* means all trace levels.* is meaningless for CTRL driver. Trace command onCTRL driver must always specify explicit levelnumber (s) to be set.According to its own processing management, CTRLdriver can dynamically modify itself its own tracelevel settings without any warnings.

Command Execution

• The command line is analyzed. Arguments are checked for type range andvalue. Missing arguments or presence of not permitted parameters cause anerror to be detected.

• If an error is detected, it is displayed (on the operator console) and processingstops.

• Else a record is built according to the arguments and parameters of the commandand it is sent from the local GCOS 7 host to the front end concerned. Processingwaits for the expected response.

• The response is analyzed and an error message is displayed (on the operatorconsole) if it indicates an error.

Error Detection

• A syntactic or a semantic error is found during command analysis.


• The response indicates if the OCS Front End that is concerned has detected anerror during execution of the command.

• The response is not the expected one. That is because some items inside theresponse do not correspond to those of the request (request id, OCS Front Endid, function).

• If the entity does not support a trace level that is selected by the command, anerror message is displayed as follows:

• entity_name levelnn not supported

• with entity_name equal to the name of the entity the command applied and nnthe number of the trace level that entity does not support.

Maintainability

47 A2 94UC 10-43

EXAMPLES:

S: TRACE EA92 HINT LEVEL = 22 NC90 TRACE SUCCESSFUL FOR EA92

This enables HINT trace at level 22.

S: TRACE EA92 HINT LEVEL = * NC90 TRACE SUCCESSFUL FOR EA92

This enables HINT trace at all levels.

❑


10-44 47 A2 94UC

10.3.9.2 NOTRACE Command

Purpose

• This command is used to disable tracing of stack entities or drivers. Severaltrace levels can be cancelled in each of them.

• 32 trace levels can be selected from trace level 1 up to trace level 32. Anadditional trace level 0 is always selected by default and cannot be disabled.

• The administrator may select any combination of above trace levels in eachentity or driver (0 excepted) to obtain a global level of trace deletion.

• If * is specified for level, all trace levels (except 0) are disabled.

Syntax

NOTRACE EAnn

[name]

level = {(n[,m]...[,p]) | * }


EAnn system identification of the targeted OCS Front End.

name the name of the entity or driver the command appliesto. This is a positional argument up to 8 EBCDICcharacters. If omitted, the command applies to alldrivers, except to the CTRL one.Name should be one of the names returned when youexecute the SEETRACE command.

NOTRACE command on CTRL driver must alwaysuse explicit name CTRL.

Maintainability

47 A2 94UC 10-45

level a positional keyword argument that precedes the tracelevel number list.If * is not specified, n, m, and p are the trace levelnumbers. Each one is up to 2 decimal digits and theyare separated by commas. The level list can containfrom 1 up to 32 level numbers.If a list is provided, you must to indicate at least onelevel number.

* disables all trace levels except level 0.* can be used on CTRL driver (explicitly named).According to its own processing management, CTRLdriver can dynamically modify itself its own tracelevel settings without any warnings.

Command Execution and Error Detection

These are the same as for the TRACE command.

EXAMPLES:

S: NOTRACE EA92 HINT LEVEL = 22 NC92 NOTRACE SUCCESSFUL FOR EA92

This disables HINT trace at level 22.

S: NOTRACE EA92 HINT LEVEL = * NC92 NOTRACE SUCCESSFUL FOR EA92

This disables HINT trace at all levels.

❑


10-46 47 A2 94UC

10.3.9.3 SEETRACE Command

Purpose

This command is used to display the current trace levels of the OCS drivers.

• When no specific name is provided, the command applies to all drivers. So youcan use this command to get the list of all the OCS Front End traceable entitiesand their level of trace. Names will be those used when the administrator wantsto modify an entity trace level (see TRACE and NOTRACE commands).

• If a name is specified, SEETRACE allows you to get the trace level of the onlycorresponding entity.

Syntax

SEETRACE EAnn

[name]


EAnn system identification of the targeted OCS Front End(LCT name).

name the name of the entity that the command applies to.This is an optional argument of up to 8 EBCDICcharacters.Name should be one of the names returned when youexecute the SEETRACE command.

Command Execution

• The command line is analyzed and a command record is built according to it.The command record is sent from the GCOS 7 local host to the OCS Front Endconcerned and processing waits for the expected response(s):

• one response if a name was provided by the command.

• as many responses as there are traceable entities when no name is specified.

• The response is analyzed and an error message is displayed (on the operatorconsole) if the response indicates an error.

Maintainability

47 A2 94UC 10-47

• Entity names and their trace levels are displayed as shown below:

ENTITY trace level number on = x

1 2 3 4 5 6 7 etc until 16 HINT x x x x

17 18 19 20 21 22 23 etc until 32 x x x x

The 1st line is the SEETRACE banner line.

The 2nd and the 4th lines are level number ident lines.

The 3rd and the 5th lines are level number state lines with x showing the tracelevel is on and blank otherwise.

The name of the entity is indicated at the beginning of the 3rd line.

Each time a trace level of another entity is to be displayed, a new set of 4 lines isappended to the display.

Error Detection


• The response indicates if the OCS Front End concerned has detected an errorduring execution of the command.

• The response is not the expected one. That is because some items inside theresponse do not correspond to those of the request (request id, OCS Front Endid, function).


10-48 47 A2 94UC

EXAMPLES:

S: SEETRACE EA92

NC87 SEETRACE RESPONSE FROM EA92 ENTITY ----- TRACE LEVEL NUMBER : ON = X 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 ... COTP 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 ...

NC87 SEETRACE RESPONSE FROM EA92 ENTITY ----- TRACE LEVEL NUMBER : ON = X 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 ... CLNP x 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 ... x x

NC87 SEETRACE RESPONSE FROM EA92 ENTITY ----- TRACE LEVEL NUMBER : ON = X 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 ... ICMP 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 ...

NC87 SEETRACE RESPONSE FROM EA92 ENTITY ----- TRACE LEVEL NUMBER : ON = X 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 ... TCP 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 ...

NC87 SEETRACE RESPONSE FROM EA92 ENTITY ----- TRACE LEVEL NUMBER : ON = X 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 ... UDP 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 ...

Maintainability

47 A2 94UC 10-49

S: TRACE EA92 HINT LEVEL = 22 NC90 TRACE SUCCESSFUL FOR EA92S: SEETRACE EA92 HINT

NC87 SEETRACE RESPONSE FROM EA92 ENTITY ----- TRACE LEVEL NUMBER : ON = X 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 ... HINT x 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 ... x

S: NOTRACE EA92 HINT LEVEL = * NC92 NOTRACE SUCCESSFUL FOR EA92S: SEETRACE EA92 HINT

NC87 SEETRACE RESPONSE FROM EA92 ENTITY ----- TRACE LEVEL NUMBER : ON = X 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 ... HINT 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 ...

❑


10-50 47 A2 94UC

10.3.9.4 FCP_TRACE_TPDU Command

Purpose

This command activates the level 1 and 2 traces (these levels are related to thetrace of incoming and outward TPDUs) of an FCP Transport layer identified by adriver name. A TCP, UDP, COTP, or TP1006 transport can be chosen. OnlyTPDUs exchanged with a selected remote node are traced.

The remote node can be identified by:

• its name (which must be declared in the ETC_HOSTS member of theSYS.DSACONF library), for all transport types, or

• an IP address for TCP and UDP drivers, or

• a Remote NSAP for COTP and TP1006 drivers.

According to the addressing rules of the Transport type, the selected address usedto identify the remote node can be the remote address itself or the address of thefirst hop used to reach it. The real selected address will be displayed at normalcommand completion.

The remote selection remains in effect while either level 1 or level 2 (or both) isset. So, TRACE and/or NOTRACE commands submitted to the same driver andaltering the levels 1 and/or 2, can cancel the remote selection made by a TRCPDUcommand.

There can be only one selection for a driver at any time. Consequently, asubsequent TRCTPDU command for the same driver, replaces the previousselection.

Syntax

{FCP_TRACE_TPDU}{TRACETPDU }{TRCTPDU }

FCP = EAnn

DRIVER = (COTP | UDP | TCP | TP1006}

{NAME = <host_name> /* TCP,UDP,COTP,TP1006 */} {IPADDR = <host_address> /* TCP,UDP */} {RTS = <remote_TS_name> /* COTP,TP1006 */} {RNSAP = <remote_NSAP> /* COTP,TP1006 */}

Maintainability

47 A2 94UC 10-51


EAnn 4 characters string which identifies the OCS Front Endcontroller (LCT name) to which the command issubmitted. It must be in the form EAnn.

DRIVER name of the driver selected (a string of up to8 characters).

Only the following driver names are accepted:

− COTP− TCP− TP1006− UDP

Refer to the paragraph "OCS Front End Trace Facility"in this chapter.

NAME A name, up to 15 characters, identifying the remotenode by its name. This can be used with any DRIVERvalue. The name must be declared in theETC_HOSTS member of the SYS.DSACONF library.The selected address will be retrieved from theconfiguration (depending on the driver type). IfNAME is specified, then IPADDR, RTS, and RNSAPmust be omitted.

IPADDR An IP address, in decimal dot notation, identifying theremote node by its IP address. This can be used onlywith DRIVER = TCP or UDP. If IPADDR is specified,then NAME, RTS, and RNSAP must be omitted.

RTS A name, up to 8 characters, identifying the remotenode by its RTS name. This can be used only withDRIVER = COTP or TP1006. If RTS is specified,then NAME, IPADDR, and RNSAP must be omitted.

RNSAP A remote NSAP, up to 40 hexadecimal digits,identifying the remote node by its NSAP address. Thiscan be used only with DRIVER = COTP or TP1006.If RNSAP is specified, then NAME, IPADDR, andRTS must be omitted.


10-52 47 A2 94UC

EXAMPLES:

TRCTPDU FCP=EA92 DRIVER=TCP NAME=lautrec;NC54 command TRCTPDU response from EA92NC63 driver=TCP sel=129.192.52.17NC54 command TRCTPDU command completed

TRCTPDU FCP=EA92 DRIVER=TP1006 NSAP=49350017;NC54 command TRCTPDU response from EA92NC63 driver=TP1006 sel=540072872203129182051131001020NC54 command TRCTPDU command completed

TRCTPDU FCP=EA92 DRIVER=COTP RTS=TSBCC6;NC54 command TRCTPDU response from EA92NC63 driver=COTP sel=080038100004NC54 command TRCTPDU command completed❑

Maintainability

47 A2 94UC 10-53

10.3.9.5 FCP_NOTRACE_TPDU Command

Purpose

This command de-activates the trace levels on TPDUs for given OCS Front Endand driver.

It also cancels the selection of a remote node.

Syntax

{FCP_NOTRACE_TPDU}{NOTRACETPDU }{NTRCTPDU }

FCP = EAnn

DRIVER = (COTP | UDP | TCP | TP1006}


EAnn 4 characters string which identifies the OCS controller(LCT name) to which the command is submitted. Itmust be in the form EAnn.

DRIVER name of the driver selected (a string of up to8 characters).

Only the following driver names are accepted:

− COTP− TCP− TP1006− UDP

Refer to the paragraph "OCS Front End Trace Facility"in this chapter.


10-54 47 A2 94UC

EXAMPLES:

- Normal Execution

NOTRACE_TPDU FCP=EA01 DRIVER=TP1006;NC54 command NTRCTPDU command completed

- Abnormal Execution (internal error)

NOTRACE_TPDU FCP=EA01 DRIVER=COTP;NC54 command NTRCTPDU response from EA01NC54 command NTRCTPDU ERROR : cannot allocate spaceNC54 command NTRCTPDU command terminated❑

Maintainability

47 A2 94UC 10-55

10.3.9.6 FCP_SEETRACE_TPDU Command

Purpose

This command displays information about drivers handling TPDU traces.

For TCP and UDP drivers, the following are displayed:

• the driver name,

• the IP address of the remote node,

• if possible, the name of the remote node.

For TP1006 drivers, the following are displayed:

• the driver name,

• the IP address (and if possible, the name) of the RFC1006 gateway used to reachthe remote node,

• the RFC1006 listening port.

For COTP drivers (and the remote node is OSI), the following are displayed:

• the MAC address of the first gateway (used to reach the remote node),

• the RTS name of the first gateway (used to reach the remote node).

For COTP drivers (and the remote node is DIWS), the following are displayed:

• the NSAP address of the first gateway (used to reach the remote node),

• if possible, the name of the first gateway (used to reach the remote node).

Syntax

{FCP_SEETRACE_TPDU}{SEETRACETPDU }{STRCTPDU }

FCP = EAnn


10-56 47 A2 94UC


EAnn 4 characters string which identifies the OCS controller(LCT name) to which the command is submitted. Itmust be in the form EAnn.

EXAMPLES:

SEETRACETPDU FCP=EA92;NC54 command STRCTPDU response from EA92NC63 driver: TCP sel: 129.192.52.17 node: unknownNC63 driver: UDP sel: 129.192.52.18 node: BC06NC63 driver: TP1006 sel: 129.192.52.18 port: 0102 node:BCC4NC63 driver: COTP macaddr: 080038100004 rts : TSBCC4NC54 command STRCTPDU command completed

SEETRACETPDU FCP=EA92;NC54 command STRCTPDU response from EA92NC63 command STRCTPDU: no selecton activatedNC54 command STRCTPDU command completed

SEETRACETPDU FCP=EA92;NC54 command STRCTPDU response from EA92NC63 driver = COTP nsap: 195644778809 node : BCC1EA84NC54 command STRCTPDU command completed❑

Maintainability

47 A2 94UC 10-57

10.3.9.7 Sequence of TRCTPDU, STRCTPDU, TRACE, SEETRACE, NOTRACECommands

EXAMPLES:

S:trctpdu ea92 cotp bcc1;NC54 command: TRCTPDU response from EA92NC63 driver: COTP sel=39250F08003810000ENC54 command: TRCTPDU command completed

S: strctpdu EA92;NC54 command: STRCTPDU response from EA92NC63 driver: COTP nsap : 39250F08003810000E NODE:BCC1NC54 command: STRCTPDU command completed

S: trace ea92 cotp level=(3,4);NC90 TRACE SUCCESSFUL FOR EA92

S: strctpdu ea92;NC54 command: STRCTPDU response from EA92NC63 driver: COTP nsap : 39250F08003810000E NODE:BCC1NC54 command: STRCTPDU command completed

S: notrace ea92 cotp level=1;NC92 NOTRACE SUCCESSFUL FOR EA92

S: strctpdu ea92;NC54 command STRCTPDU response from EA92NC63 driver: COTP nsap : 39250F08003810000E NODE:BCC1NC54 command: STRCTPDU command completed

S: seetrace ea92 cotp;NC87 SEETRACE RESPONSE FROM EA92ENTITY --- TRACE LEVEL NUMBER : ON = X. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 ... COTP x x x 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 ...

S: notrace ea92 cotp level=2;NC92 NOTRACE SUCCESSFUL FOR EA92


10-58 47 A2 94UC

S: strctpdu ea92;NC54 command: STRCTPDU response from EA92NC54 command: STRCTPDU : no selection activatedNC54 command: STRCTPDU command terminated

S: trace ea92 cotp level=1;NC90 TRACE SUCCESSFUL FOR EA92

S: strctpdu ea92;NC54 command: STRCTPDU response from EA92NC54 command: STRCTPDU : no selection activatedNC54 command: STRCTPDU command terminated

S: trace ea92 cotp level=2;NC90 TRACE SUCCESSFUL FOR EA92

S: strctpdu ea92;NC54 command: STRCTPDU response from EA92NC54 command: STRCTPDU : no selection activatedNC54 command: STRCTPDU command terminated❑

Maintainability

47 A2 94UC 10-59

10.3.9.8 EDTRACE Command

Purpose

This command enables you to display information from the trace files (while OCSFront End is running it places the information in the trace files). The informationcan be displayed on the console, placed in a subfile, or sent directly to a printer.EDTRACE can be used either while OCS Front End is running or later on amaintenance machine. In the first case, one file may be held by the OCS driver andthis prevents EDTRACE from processing the most recent traces.

EDTRACE has been extended to enable you to select one "connection" with aremote node, to complement the possibility to trace only the TPDUs exchangedwith a selected remote node (refer to the TRCTPDU command). Depending on theTransport type (specified via the DRIVER parameter), a "connection" will beidentified by a remote port (+ local port) for TCP and UDP, or by a TransportConnection reference for COTP and TP1006. This extended use of EDTRACE isavailable only on TCP/UDP/COTP/TP1006 drivers and on the level 1 and/or level2 trace.

Note that the LOC_REF parameter is a TC reference retrieved from the LCPLUGfield returned by a DNET TC CODE=LONG command.

Syntax

EDTRACE EAnn

[DIR = (SYS | working directory)]

[DRIVER = (driver_name | ALL)]

[LEVEL = level-value]

[IDENT = ident-value]

[DATE_BEGIN = (date | 0000.00.00)]

[HOUR_BEGIN = (time | 00.00.00)]

[DATE_END = (date | 0000.00.00)]

[HOUR_END = (time | 00.00.00)]

[MAX = (value | 0)]


10-60 47 A2 94UC

[CONSOLE = (0 | 1)]

[SYSOUT = (0 | 1)]

[FILE_NAME = file_name]

[{REM_PORT = dec-5 [, LOC_PORT = dec_5]}] [{ }] [{LOC_REF = hexa-8 }]


EAnn 4 characters string which identifies the OCSconcerned.

DIR master directory where the OCS Front End trace files(<dir>.DSATRC_EAnn_i) are located. Default isSYS.

DRIVER name of the selected driver (Default value is ALL).

Driver names are:

− HINT (host Interface)− LLC1− COTP− CLNP− ESIS− IAM (IPS Administrative Module)− FIFO (GPU2A/PPA FIFO management)− IM (Information Management)− ARP− ICMP− IP− RIP (not yet implemented)− TCP− TP1006− UDP

CTRL driver traces cannot be displayed.

Level trace level to be selected (0 up 32). If omitted, all tracelevels are selected.

Maintainability

47 A2 94UC 10-61

Ident an 8 hexadecimal character string which identifies thetrace message. If missing, all idents will be selected.A range of value is allocated to each sender. Identranges are as following:

000nnnnn COMS (communication services)014nnnnn CLNP (for RIB)02nnnnnn TP1006038nnnnn ESIS04nnnnnn COTP1nnnnnnn HINT2nnnnnnn FIFO3nnnnnnn IM4nnnnnnn LLC15nnnnnnn IP6nnnnnnn TCP7nnnnnnn UDP8nnnnnnn ICMP9nnnnnnn ARPAnnnnnnn RIP (not implemented)Bnnnnnnn IAMEnnnnnnn LME (Layer Management entity)Fnnnnnnn CLNP

nnnnnnn: 7 hexadecimal digitsDATE_BEGIN date (expressed in yyyy.mm.dd format) from which the

search will begin. If omitted, the default value is thedate of the oldest trace message of the trace.

HOUR_BEGIN hour (expressed in hh.mm.ss format) from which thesearch will begin. If omitted, the default value is thehour of oldest record.

DATE_END date (expressed in yyyy.mm.dd format) at which thesearch will end. If omitted, the default value is thecurrent date.

HOUR_END hour (expressed in hh.mm.ss format) at which thesearch will end. If omitted, the default value is thecurrent time.

MAX maximum number of selected trace records to bedisplayed. Default value 0 means no limit.(1 <=MAX<=99999)

CONSOLE result will be displayed on the terminal.

SYSOUT result will be printed.


10-62 47 A2 94UC

FILE_NAME Full path name of a subfile (of a cataloged library)where the result will be stored.

REM_PORT TCP or UDP remote port. If REM_PORT is specified,then DRIVER must be set to TCP or UDP, and LEVELmust be 1 or 2. If REM_PORT is specified, LOC_REFmust be omitted.

LOC_PORT TCP or UDP local port. If LOC_PORT is specified,then DRIVER must be set to TCP or UDP, and LEVELmust be 1 or 2. If LOC_PORT is specified,REM_PORT must also be specified and LOC_REFmust be omitted.

LOC_REF TC reference of the OSI/DIWS transport connection.If LOC_REF is specified, then DRIVER must be set toCOTP or TP1006, and LEVEL must be 1 or 2. IfLOC_REF is specified, REM_PORT and LOC_PORTmust be omitted.

Maintainability

47 A2 94UC 10-63

10.3.9.9 OCS Front End Trace Output Format

A PPA trace is displayed in 2 parts:

• a common fixed part regardless the type of trace,

• a variable part depending on the type.

TRACE_MSG : stream messageTRACE_DUMP : memory dumpTRACE_LONG : 5 long variablesTRACE_STR : noneTRACE_EMERGENCY : fatal error message

Fields explanation

DT: recording DaTeHR: recording HouRHL: PPA Local Hour (expressed in 10ms).DR: PPA driver nameLV: trace LeVelID: message IDentIF: InFo fieldaaaaaa: ASCII fieldxxxxxx: Hexadecimal fielddd: decimal field

Fixed Part

DT: YY/MM/DD HR: HH/MM/SS HL: xxxxxxxxDR: abcdefgh LV: dd ID: xxxxxxxx IF: xxxxxxxx< explanation of IDENT >


10-64 47 A2 94UC

Specific Part

type TRACE_STR:NODATA

type TRACE_LONG:V1: xxxxxxxx V2:xxxxxxxx V3: xxxxxxxx V4: xxxxxxxx V5: xxxxxxxx

type TRACE_DUMP:DUMP:00: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx aaaaaaaaaaaaaaaa10: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx aaaaaaaaaaaaaaaa20: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx aaaaaaaaaaaaaaaa..X0: xxxxxxxx .........type TRACE_MSGMSG:00: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx aaaaaaaaaaaaaaaa10: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx aaaaaaaaaaaaaaaa20: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx aaaaaaaaaaaaaaaa..X0: xxxxxxxx .........

type TRACE_EMERGENCYPANIC:00: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx aaaaaaaaaaaaaaaa10: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx aaaaaaaaaaaaaaaa20: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx aaaaaaaaaaaaaaaa..X0: xxxxxxxx .........

Maintainability

47 A2 94UC 10-65

10.3.10 OCS Front End XID/TEST/ECHO Services

10.3.10.1 Overview

These services allow:

• a search for the identification of OSI/DSA operational hosts attached to thenetwork,

• or, a check of the integrity of a transmission when communicating with them.

Five commands exist:

• XID: search the identification of a remote host

• TEST: check the communication link with a remote host (on the same network)

• ENDTEST: stop a previous TEST command

• ECHO: check the communication link with a remote host (on the same or onanother network)

• ENDECHO: stop a previous ECHO command

NOTE:The PING command of the IPS administration works in a similar way as TESTin TCP/IP world.


10-66 47 A2 94UC

10.3.10.2 XID Command

Purpose

The XID (eXchange IDent) command is used to verify the presence of host(s)attached to the network, which are operational. This is done by sending a XIDcommand to elicit XID response(s) from the operational host(s).

This exchange designates the LLC that is associated with the underlying MACservice access point address, it does not allow to identify any other service accesspoint.

Syntax

XID EAnn

dest_MACad | BROADCAST


EAnn system identification of the targeted OCS controller(LCT name).

dest_MACad individual Ethernet address of the host from which aXID response is expected. It is expressed in MACaddress notation as a six part hexadecimal address.When the BROADCAST keyword is provided instead,it indicates that a global ethernet address is sent toelicit responses from all hosts that are attached to thenetwork.

Maintainability

47 A2 94UC 10-67

Command Execution

• The command line is checked and a command record built according tocommand argument is sent from the DPS 7000 local host to the OCS Front Endthat is concerned.

• The expected incoming response (corresponding to XID confirm and to LLCdestination service application point) is analyzed and displayed (on the operatorconsole) as indicated below, for instance:

eth 08:00:38:20:e0:13 is responding.

• and so on for the subsequent ones when the BROADCAST argument wasspecified.

• If no response occurs within a period of time equal to 20 seconds, responses thatcame (if any) are displayed together with a completed operation notificationmessage in case of BROADCAST operation.

• If no response occurs in case of individual address, the following error messageis displayed, for instance:

no response from eth 08:00:38:20:e0:13.

Error Detection

• If the command line is illegal or if a response indicates an error, processing stopsand an error message is displayed (on the operator console).

• In case of no response, a message is displayed as explained above.


10-68 47 A2 94UC

10.3.10.3 TEST Command

Purpose

The TEST command is used to communicate with a particular host in order toverify communication integrity and to observe network behavior.

As for XID, TEST command is performed only at LLC service level access point.

Syntax

TEST EAnn

dest_MACad

[packets=number]

[interval=time]



dest_MACad individual Ethernet address of the host the TESTcommand is addressed to. It is expressed in MACaddress notation as a six part hexadecimal address.

packets is a keyword that precedes the "number" definition.Number is a 6 EBCDIC decimal digits string thatindicates the number of times the TEST command is tobe sent. If packets = number is omitted, only oneTEST command is sent. If packets=number is set to 0,TEST commands are repeated until an ENDTESTcommand is executed.

interval is a keyword that precedes the time definition.Time is a string of 6 EBCDIC decimal digits thatdefines the elapsed time in seconds between sendingsubsequent TEST commands. If interval = time isomitted or set to 0, TEST commands are sent every 1second.

Maintainability

47 A2 94UC 10-69

Command Execution

• The command line is checked and a command record built according to thecommand argument(s). This record is sent from the DPS 7000 local host to theOCS Front End that is concerned. If packets=number is specified, the record issent at every interval period of time, until packet number is exhausted or until anENDTEST command is executed. This causes a packet having a total length of1518 bytes and made of alphanumeric characters to be sent on the network.

• Each time a TEST command is sent, processing waits for the expected response.

• The incoming response is checked. If an error is detected by the OCS Front Endwhile performing the command, an error message is displayed (on the operatorconsole). That is, when the data provided by the TEST response does notcorrespond to that just sent.

• If there is no error, an acknowledgment message containing the TEST commandnumber is displayed. For example:

eth 08:00:38:20:e0:13 -TEST cmd # : .

• When the test sequence is over because number of packets is exhausted or theENDTEST command is submitted, the additional information "TEST commandcompleted" is displayed too.

Error Detection

If the command line is illegal, or if the response indicates an error (as explainedabove), or if there is no response within a predetermined period of time, processingstops and an error message is displayed (on the operator console).


10-70 47 A2 94UC

10.3.10.4 ENDTEST Command

Purpose

The ENDTEST command is used to terminate a TEST command which is currentlyexecuting.

Syntax

ENDTEST EAnn



Maintainability

47 A2 94UC 10-71

10.3.10.5 SEND_ECHO_REQUEST Command

Purpose

This command is used to send an echo request message to an OSI remote node anddisplay the NSAPs of the gateways used to route the request and response message.The number of requests to be sent and the interval between them are specified viaparameters.

Syntax

{SEND_ECHO_REQUEST}{ }{ECHO }

FCP = EAnn

{NAME = char_15} { } {NSAP = hexa_40}

[SIZE = {user_data_length | 64}]

[INTERVAL = {time_in_seconds | 5}]

[COUNT = {count | 1}]


EAnn 4 character string (LCT name identifying the OCSFront End in the NETGEN configuration) specifyingthe OCS controller to which the command applies.

NAME a string, up to 15 characters, identifying the remotenode. This name must be declared in theETC_HOSTS subfile of the SYS.DSACONF library.NAME and NSAP are mutually exclusive.

NSAP an NSAP address, up to 40 hexadecimal digits,identifying the remote node. NSAP and NAME aremutually exclusive.

SIZE the length, expressed in bytes, of the user data in theECHO request message. The default value is 64 bytes.


10-72 47 A2 94UC

INTERVAL a string, of up to 5 decimal digits, that defines theelapsed time in seconds between the sending of 2consecutive ECHO messages. The minimum is 1 andthe default is 5.

COUNT a string that defines the number of times the ECHOmessage is to be sent. COUNT = 0 means that there isno limit (in fact, the message will be sent repeatedlyuntil an ENDECHO command is executed). In allcases, ECHO can be terminated via an ENDECHOcommand. The default is 1. The value entered mustnot exceed 2**31.

Messages in Response to the Command

The following suite of messages are displayed if the command executes normally.Except for the header and trailer messages, the other messages are repeated eachtime the ECHO messsage is sent (until COUNT is reached or the command isterminated by an ENDECHO command).

NC54 command ECHO command launchedNC54 command ECHO response from EAnnNC55 <dest> is respondingNC55 Request Route Recording : {PARTIAL | TOTAL | NONE}[NC55NETitle : NSAP][NC55NETitle : NSAP]NC55 Response Route Recording : {PARTIAL | TOTAL | NONE}[NC55NETitle : NSAP][NCNETitle : NSAP]

NC54 command ECHO response from EAnnNC55 <dest> is respondingNC55 Request Route Recording : {PARTIAL | TOTAL | NONE}[NC55NETitle : NSAP][NC55NETitle : NSAP]NC55 Response Route Recording : {PARTIAL | TOTAL | NONE}[NC55NETitle : NSAP][NCNETitle : NSAP]

NC54 command ECHO command completed

Dest is the identification of the remote node (name or NSAP).

Maintainability

47 A2 94UC 10-73

The "Request or Response Route Recording: {PARTIAL | TOTAL | NONE}"message indicates whether or not the following list of NSAPs contains all theaddresses of the nodes used to route the request and response. If NONE, it meansthat no gateway has been passed.

The ordered NETtitle list gives the suite of node addresses recorded during therouting.

EXAMPLES:

S: echo ea92 name=BCAF;NC54 command : ECHO response from EA92NC54 command : ECHO ERROR : selection of a local addressNC54 command : ECHO command terminated

S: echo ea92 name=BCC1;NC54 command : ECHO command launchedNC54 command : ECHO response from EA92NC55 BCC1 is respondingNC55 command : ECHO Request Route Recording : NONENC55 command : ECHO Response Route Recording : NONENC54 command : ECHO command completed

S: echo ea92 name=TOTO;NC54 command : ECHO response from EA92NC55 command : ECHO Node : TOTO is unknownNC54 command : ECHO command terminated❑


10-74 47 A2 94UC

10.3.10.6 FCP_END_ECHO_SENDING Command

Purpose

This command is used to terminate an ECHO command (currently in progress).

Syntax

{FCP_END_ECHO_SENDING}{ }{ENDECHO }

FCP = EAnn


EAnn 4 character string (LCT name identifying the OCSFront End in the NETGEN configuration) specifyingthe OCS controller to which the command applies.

EXAMPLES:

No ECHO Command in Progress

S: ENDECHO EA92;NC54 command : ENDECHO command completed

An ECHO Command in Progress

S: ENDECHO FCP=EA92;NC54 command : ENDECHO command completedNC54 command : ECHO command terminated❑

Maintainability

47 A2 94UC 10-75

10.3.11 Miscellaneous Commands

10.3.11.1 DISPLAY_FCP_ACTIVITY Command

Purpose

This command displays the activity of OCS Front End communication processingin terms of:

• processor loading rate (LOAD field),

• memory occupancy in Kbytes (TOTAL, USED, FREE fields),

• host time when the activity was measured (TIME field).

Syntax

{DISPLAY_FCP_ACTIVITY}{ }{DACTFCP }

FCP_NAME = EAnn

[COUNT = {count | 1}]

[INTERVAL = {time_in_seconds | 5}]


FCP_NAME 4 character string (LCT name identifying the OCSFront End in the NETGEN configuration) specifyingthe OCS controller to which the command applies.

COUNT a string, of up to 8 decimal digits, that defines thenumber of times the activity is to be measured.COUNT = 0 means that there is no limit (in fact, themeasures will be repeated until an ENDDACTcommand is executed). In all cases, DACTFCP can beterminated via an ENDDACT command. The defaultis 1.


10-76 47 A2 94UC

INTERVAL a string, of up to 5 decimal digits, that defines theelapsed time in seconds between 2 consecutivemeasures. The default is 5 seconds.

EXAMPLES:

S: DACTFCP EA92;NC54 command : DACTFCP command launchedNC57 EA92 10:34:52 LOAD=02% TOTAL=18120 USED=528 FREE=17592KBNC54 command : DACTFCP command completed

S: DISPLAY_FCP_ACTIVITY FCP_NAME=EA92 INTERVAL=2 COUNT=3;NC54 command : DACTFCP command launchedNC57 EA92 10:34:52 LOAD=02% TOTAL=18120 USED=528 FREE=17592KBNC57 EA92 10:34:54 LOAD=02% TOTAL=18120 USED=528 FREE=17592KBNC57 EA92 10:34:56 LOAD=02% TOTAL=18120 USED=528 FREE=17592KBNC54 command : DACTFCP command completed❑

Maintainability

47 A2 94UC 10-77

10.3.11.2 END_DISP_FCP_ACTIVITY Command

Purpose

This command terminates a DISPLAY_FCP_ACTIVITY command (currently inprogress).

Syntax

{END_DISP_FCP_ACTIVITY}{ }{ENDDACT }

FCP_NAME = EAnn


FCP_NAME 4 character string (LCT name identifying the OCSFront End in the NETGEN configuration) specifyingthe OCS to which the command applies.

EXAMPLES:

No DISPLAY_FCP_ACTIVITY Command in Progress

S: END_DISP_FCP_ACTIVITY EA92;NC54 command : ENDDACT command completed

A DISPLAY_FCP_ACTIVITY Command in Progress

S: ENDDACT FCP_NAME=EA92;NC54 command : ENDDACT command completedNC54 command : DACTFCP command terminated❑


10-78 47 A2 94UC

10.3.11.3 DISPLAY_FCP_MAC_ADDR Command

Purpose

This command displays the MAC address (also called the physical address) of anOCS Front End.

All OCS Front Ends or a specific one can be selected.

Syntax

{DISPLAY_FCP_MAC_ADDR}{FCPMACADDR }{DMAC }

[FCP_NAME = {EAnn | ALL | *}]


FCP_NAME EAnn is 4 character string (LCT name identifying theOCS Front End in the NETGEN configuration)specifying the OCS Front End to which the commandapplies.ALL (the default value) or * means all running OCSFront Ends (that is, whose servers are running) areselected.

EXAMPLES:

S: DMAC EA92;NC54 command : FCPMACADDR command launchedNC56 FCP : EA92 MACADD =08:00:38:52:41:afNC54 command : FCPMACADDR command completed

S: FCPMACADDR FCP_NAME=ALL;NC54 command : FCPMACADDR command launchedNC56 FCP : EA92 MACADD =08:00:38:52:41:afNC56 FCP : EA82 MACADD =08:00:38:67:41:c1NC54 command : FCPMACADDR command completed❑

Maintainability

47 A2 94UC 10-79

10.3.11.4 RESTART_FCP_ADMIN Command

Purpose

This command restarts all failed components of OCS servers withoutstopping/restarting OCS itself. It applies to all running OCS servers and addresseslocal IPS administration, SNMP components, OSI/DSAC administration, and OCSFront End trace management.

RSTADM is used after corrective actions such as file creation, file modification,etc.

Syntax

{RESTART_FCP_ADMIN}{ }{RSTADM }


None.

EXAMPLES:

S: RESTART_FCP_ADMIN;NC54 command : RSTADM command launchedNC54 local IPS administration restartedNC54 from server OCS1 : SNMP restartedNC54 command : RSTADM command completed

S: RSTADM;NC54 command : RSTADM command launchedNC54 from server OCS2 : server TRACE restartedNC54 command : RSTADM command completed❑


10-80 47 A2 94UC

❑

47 A2 94UC A-1

A. FECM Service Messages

A.1 FECM Service Messages

This appendix lists the messages issued by FECM when the error, as indicated inthe message text, is detected during execution.

Errors are caused either by the user in the scenario provided or when an abnormalsystem condition occurs.

These error messages are written to the SYSOUT and the JOR. For each messageor group of messages, an additional error message prefixed with FE is sent to theoperator's console. The accompanying FE message provides further details into thecause of the error. See Section 6 "Messages" for the meaning of the FE messageand the action to be taken.

The prefix FS indicates FECM as the originator of the message.

FS01 ERROR DURING "functionnm" PROCESSING. gr4

FS02 UNABLE TO reason [SUBFILE "sfn" IN] FILE "efn". where reason is one of the following: - ALLOCATE SPACE FOR - ASSIGN - CHANGE NAME OF - CLOSE - CREATE FD FOR - DELETE - FIND - OPEN - POINT TO BEGINNING OF - READ - WRITE [ CONTROL RECORD IN ]


A-2 47 A2 94UC

FS03 INVALID TYPE "type" FOR FILE "efn".

FS04 INVALID CONTROL RECORD OF SUBTYPE "sfn" IN FILE "efn".

FS05 WRONG SUBFILE "sfn" IN FILE "efn": TYPE "type" IS INVALID.

FS07 VERSION "versionnb" IS NOT AVAILABLE ON YOUR SITE.

FS08 UNABLE TO LOAD SPA. MEMORY IMAGE NOT FOUND IN FILE SYS.HUBG.

FS10 EFN NOT FOUND IN ALLOWED FILES <external-file-name>

FS11 "GO" INSTRUCTION IN SCENARIO MUST NOT EXCEED nn CHARACTERS. literal-128

FS12 UNABLE TO RESET THE CONTROLLER.

FS13 UNABLE TO INITIALIZE THE CONTROLLER.

FS14 TIMEOUT OCCURRED DURING PROCESSING.

FS15 SCENARIO "sfn" NOT FOUND IN FILE "efn".

FS16 UNABLE TO ALLOCATE PSI: - CL { HELD OR ALLOCATED | NOT CONNECTED IN SRST } - LACK OF CL IN SRST - LCT HELD OR ALLOCATED - LCT { NOT CONNECTED | UNKNOWN } IN SRST - NO CL IN SRST

FS17 ERROR DURING "functionnm" PROCESSING: - UNKNOWN STATUS: "code_01"X - text

FS18 SESSION CANNOT BE OPENED: text

FS19 SESSION WAS INTERRUPTED BY : { TNS SERVER , REASON = "hh" X } { UNKNOWN REASON : "code_01" X } { text } where "hh" depends on local or remote administration : a) local administration for LNA "23" : CNP protocol error "24" : abnormal termination on end_load CCE "25" : abnormal termination on abort_dump CCE "26" : abnormal termination on start_node CCE "27" : abnormal termination on read_dump CCE "28" : abnormal termination on write_load CCE "29" : buffer not available "2A" : abnormal termination on reset CCE

FECM Service Messages

47 A2 94UC A-3

b) remote administration for CNP 7 "24" : disconnect frame from remote controller "25" : DM frame simulated by local controller "26" : DM frame sent by remote controller "27" : timeout on reset frame (30 seconds) "28" : timeout on SIM frames ( 5 * 5 seconds) "29" : buffer not available "2A" : abnormal termination on write CCE

FS20 RECORD IS TOO LARGE OR WRONG SUBFILE "sfn" IN FILE "efn"; RECORD MUST NOT EXCEED nn BYTES.

FS21 PROCESSING WAS INTERRUPTED BY AN INITIALIZATION REQUEST FROM FRONT-END.

FS29 NO SCENARIO MATCHING, SCENARIO FILE IS DISCARDED.

FS30 NAME IS MISSING AFTER "{ NODE | SCEN }" CLAUSE.

FS31 {NODE | ACTION} NOT FOUND IN THE SCENARIO

FS32 message text as follows: - CLAUSE "literal-32" IS TOO LARGE. THE LINE IS IGNORED. - NAME "literal-32" IS TOO LARGE. ONLY 8 CHARACTERS ARE - CONSIDERED. - TOO LONG STRING IN THE LINE.

FS33 NO CLAUSE WAS SPECIFIED.

FS34 INVALID ORDER OF CLAUSES IN THE PRESENT CONTEXT.

FS35 FILE NAME IS MISSING - AFTER { "LOAD" ORDER | "MAP" OPTION } - OR INVALID

FS36 "GO" CLAUSE IS MISSING AFTER "LOAD" CLAUSE.

FS37 CONTINUATION LINE IS MISSING.

FS38 VERSION NUMBER IS MISSING OR INVALID.

FS39 INVALID FILE NAME "literal-32". - FILE NAME MUST BE - "{ CONF | CORE | DUMP | SLIB | CORE... "OR" BLIB }..." - SUBFILE NOT { FOUND | SPECIFIED }.

FS41 INVALID FILE NAME "literal-32". - SUBFILE NAME EXCEEDS 31 CHARACTERS. - SYNTAX ERROR IN SUBFILE NAME.FS42 WARNING : SUBFILE "sfn" DOES NOT EXIST IN FILE "efn".


A-4 47 A2 94UC

FS47 IMPLEMENTATION RETSRICTION. NO MORE ENTRY IS AVAILABLE FOR A NEW ASF SESSION (MAXIMUM IS nn).

FS48 IMPLEMENTATION RESTRICTION. NO ROOM ENOUGH TO HOLD SCENARIO INSTRUCTIONS.

FS49 IMPLEMENTATION RESTRICTION. NO MORE ENTRY IS AVAILABLE FOR A NEW SUBFILE (MAXIMUM IS nn).

FS50 INTERNAL ERROR. INPUT OR OUTPUT BUFFER IS TOO SMALL. (SHOULD BE nn)

FS51 INTERNAL ERROR. FILE STRUCTURE FOR FILE NUMBER nn IS INVALID

FS52 INTERNAL ERROR. UNKNOWN SEMAPHORE MESSAGE.

FS53 INTERNAL ERROR. INVALID OPTION STRING: - PREVIOUS VERSION NOT SUPPORTED. - TOO SHORT. - UNKNOWN CONTROLLER TYPE. - UNKNOWN FUNCTION (NOT ADM OR ASF).

FS54 INTERNAL ERROR. SAVE AREA FOR EDD PROCESSING IS TOO SMALL.

FS55 INTERNAL ERROR. SUBFILE "sfn" IS OPENED WHEN CLOSING FILE "efn".

FS59 CROSS-NET PROTOCOL ERROR. RECORD RECEIVED IS TOO LARGE; RECORD MUST NOR EXCEED nn BYTES.

FS60 CROSS-NET PROTOCOL ERROR. INVALID RECORD RECEIVED WHEN { WRITING | SENDING } A RECORD

FS61 CROSS-NET PROTOCOL ERROR. INVALID SEMAPHORE MESSAGE opcode DURING primitive PROCESSING.

FS62 CROSS-NET PROTOCOL ERROR. INVALID FILE PROCESSING MODE.

FS63 CROSS-NET PROTOCOL ERROR. INVALID RESPONSE FORMAT.

FS64 CROSS-NET PROTOCOL ERROR. END-OF-FILE WAS NOT ACKNOWLEDGED.

FS65 CROSS-NET PROTOCOL ERROR. UNEXPECTED END-OF-FILE RECORD.

FECM Service Messages

47 A2 94UC A-5

FS66 CROSS-NET PROTOCOL ERROR. reason RECORD IS INVALID IN THE PRESENT CONTEXT. reason is one of the following: - DATA TRANSFER - { DUMP | EXECUTE | LOAD | START-NODE } ACK - TRANSFER INITIALIZATION OR TERMINATION

FS67 CROSS-NET PROTOCOL ERROR. NEGATIVE ACKNOWLEDGEMENT OF END-OF-FILE.

FS68 CROSS-NET PROTOCOL ERROR. NEGATIVE ACKNOWLEDGEMENT: text

FS69 CROSS-NET PROTOCOL ERROR. INVALID NEGOTIATION SIZE IS TOO { LARGE | SMALL }.


A-6 47 A2 94UC

❑

47 A2 94UC B-1

B. Scanning CNP 7 and Datanet Dumps

B.1 Scanning CNP 7 and Datanet Dumps

The Communications Processor Dump Scanner (CPDS) allows the user to scan thememory dump of either the CNP 7 or the Datanet in order to select portions of thedump which are useful in finding where an anomaly in the front-end processor hasoccurred. CPDS is an interactive utility for which the menu facility is available.

Further information on CPDS is treated in the CPDS User's Guide.

The following steps show how CPDS is started.

1) S: CPDS . . The menu for the workfile allocation is displayed . Complete the mandatory parameters ORIGIN, WORK and CMD . Pressing Transmit is equivalent to Step 2 .

2) S: CPDS WORK=dumpfile, where dumpfile has been specified for WORK in the menu above . . listing of the dump context of the fep appears .

3) T: cpds-command . . see Syntax of Commands following .


B-2 47 A2 94UC

B.1.1 CPU (CNS Process Unit alias Memory Unit)

Purpose

Defines all the memory units or a particular memory unit of the CNP 7 to whichsubsequent CPDS commands are to apply. The default is all memory units.

NOTE:The CNP 7 has up to 6 memory units, each memory unit being a couplerexecuting its own CNS7 software. The main memory of the CNP 7 is numbered8 (the listing displays 80). Supplementary memory units are numbered 0, 1, 2,3 and 4 (the listing displays 00, 01, 02, 03 and 04).

Syntax

[ { all memory_units } ]CPU [ { ---------------- } ] ; [ { memory_unit-number } ]

Parameters

See "Explanation of Acronyms and Abbreviations" below.

Scanning CNP 7 and Datanet Dumps

47 A2 94UC B-3

B.1.2 DESC (DESCRIPTORS)

Purpose

Displays the start and end addresses of all the sections within the memory unit, foreither a particular memory unit or all memory units.

Syntax

{ DESCRIPTORS }{ }{ DESC } ;{ }{ DES }

Parameters

None.


B-4 47 A2 94UC

B.1.3 DISP (DISPLACE)

Purpose

Positions the pointers either at an absolute address or at an address relative to aknown location in the dump file.

Syntax

{ DISPLACE } { { hexadecimal-address } }{ } { { } }{ DISP } { { $ { + | - } hexadecimal-displacement } }{ } { }{ DI } { { [C*] | D* } md-nm-rls [ ] } { -- [ { } ] } ; { F*family-2 [ { + } ] } { [ { } hexa-disp ] } { T*fftype-4 [ { - } ] } { [ { } ] } { O*ffobject-8 [ ] }

Parameters



47 A2 94UC B-5

B.1.4 EC (ECHO)

Purpose

Directs the results of the dump scanner either to be displayed on the screen or to bewritten to a file or to be printed in the SYSOUT report.

Syntax

{ ECHO } { ON }{ } { -- } ;{ EC } { OFF }

Parameters

• ON Default: displays results at the submitter terminal.

• OFF Writes results to a user file or SYS.OUT.

Before issuing ECHO OFF, enter PON (printer on) to activate the printer. If theprinter is not activated, ECHO OFF will be rejected.


B-6 47 A2 94UC

B.1.5 GOTO (alter_input)

Purpose

The GOTO command is reserved for maintenance. The operator enters thiscommand only at the request of the Service Center.

Switches the input from the current dump file to the file designated.

Syntax

GOTO efn ;

Parameters



47 A2 94UC B-7

B.1.6 MAP (MAP)

Purpose

Positions the pointers either at an absolute address or at an address relative to aknown location in the dump file.

Syntax

MAP [ { { ALL | A } } ] [ { --- - } ] [ { [ { cpu } ] } ] [ { { MOD | M } [,md-nm-rls-label] [,{ --- } ] } ] [ { [ { cpu-number } ] } ] [ { } ] ; [ { { FAM | F } [ ,family-label ] } ] [ { } ] [ { { TYP | T } [ ,type-label ] } ] [ { } ] [ { { OBJ | O } [ ,object-label ] } ]

Parameters



B-8 47 A2 94UC

B.1.7 MAPF (MAPFAMILY)

Purpose

Lists the names, addresses, types and indexes of objects for a given family or agroup of families specified with the asterisk convention.

Syntax

{ MAPFAMILY } [ ]{ } [ family-label ] ;{ MAPF } [ ]

Parameters



47 A2 94UC B-9

B.1.8 MAPT (MAPTYPE)

Purpose

Lists the names, addresses, families, types and indexes of objects for a given typeor a group of types specified with the asterisk convention.

Syntax

{ MAPTYPE } [ ]{ } [ type-label ] ;{ MAPT } [ ]

Parameters



B-10 47 A2 94UC

B.1.9 NODISP (NODISPLACE)

Purpose

Enables (OFF) or disables (ON) the automatic displace function.

Automatic displace is ON when NODISP OFF is entered. Lines giving thedisplacement status of the module are displayed or printed.

Automatic display is OFF when NODISP or NODISP ON is entered. Lines givingthe displacement status of the module do not appear thereby allowing the screen todisplay the maximum amount of information.

Syntax

{ NODISPLACE } { ON }{ } { -- } ;{ NODISP } { OFF }

Parameters

• ON Default: disables the automatic displace function.The message AUTOMATIC DISPLACE IS OFF is returned.

• OFF Enables the automatic displace function.The message AUTOMATIC DISPLACE IS ON is returned.

Automatic displacement is enabled with PRINT and PSTACK commands.


47 A2 94UC B-11

B.1.10 PITCB (Print Internal Task Control Block)

Purpose

Lists information concerning the tasks accessed within a given memory unit of theCNP 7. The CNP 7 memory unit is either selected by specifying a value in thecommand or taken by default as the current memory unit, if no value is specified.

Syntax

{ PI }{ } [ { cpu } ]{ PIT } [ { --- } ] ;{ } [ { cpu-number } ]{ PITCB }

Parameters



B-12 47 A2 94UC

B.1.11 POFF (Printer Off)

Purpose

Suspends the output to either the workfile specified when invoking CPDS or theSYSOUT of the current session, by default. POFF is symmetric to PON.

Syntax

POFF;

Parameters

None.


47 A2 94UC B-13

B.1.12 PON (Printer On)

Purpose

Writes the output of the dump scan to either the workfile specified when invokingCPDS or the SYSOUT of the current session, by default. PON is symmetric toPOFF.

Syntax

PON;

Parameters

None.


B-14 47 A2 94UC

B.1.13 PR (PRINT)

Purpose

Prints an area in a given memory unit of the CNP 7. The memory unit is eitherspecified in the command or taken as default. The default is either the valueentered for a previous CPU command or, if no CPU command has been issued, allCNP 7 memory units.

Automatic displacement is enabled with PRINT. See NODISPLACE.

Syntax

{ PRINT } [ { cpu } ]{ } [ { --- } ]{ PR } [ { cpu-number } ]

[ { current-address } ] [ { --------------- } ] [ { hexadecimal-address } ] [ { } ] [ { $ { + | - } hexadecimal-displacement } ] [ { } ] [ { { [C*] | D* } md-nm-rls [ ] } ] [ { -- [ { } ] } ] [ { F*family-2 [ { + } ] } ] [ { [ { } hexa-disp ] } ] [ { T*fftype-4 [ { - } ] } ] [ { [ { } ] } ] [ { O*ffobject-8 [ ] } ]

[ { address (as in preceding) } ] [ { } ] [ , { { L= } } ] ; [ { { } hexadecimal-length } ] [ { { , } } ]

Parameters



47 A2 94UC B-15

B.1.14 PRINTALL (ALL)

Purpose

The ALL or PRINTALL command is reserved for maintenance only.

Prints all zones for the set of memory descriptors.

Syntax

{ PRINTALL }{ } ;{ ALL }

Parameters

None.


B-16 47 A2 94UC

B.1.15 PST (Print Stack)

Purpose

Prints the stack of a given memory unit of the CNP 7. The stack is defined as thearea between the start stack address to the BSTK flag. In absence of the BSTKflag, the stack is 2000 bytes from the start stack address. The start stack addressmust be specified with the memory unit concerned.

PSTACK can only be specified without arguments if the SYSER zone has beencreated. In this case, it is equivalent to the PSYSER command.

Automatic displacement is enabled with PSTACK. See NODISPLACE.

Syntax

{ PSTACK } [ { cpu }{ } [ { --- }{ PST } [ { cpu-number }

[ { syser-zone-address } ] [ { ------------------ } ] [ { hexadecimal-address } ] [ { } ] [ { $ { + | - } hexadecimal-displacement } ] [ { } ] [,{ { [C*] | D* } md-nm-rls [ ] } ] ; [ { -- [ { } ] } ] [ { F*family-2 [ { + } ] } ] [ { [ { } hexa-disp ] } ] [ { T*fftype-4 [ { - } ] } ] [ { [ { } ] } ] [ { O*ffobject-8 [ ] } ]

Parameters



47 A2 94UC B-17

B.1.16 PSYSER (Print System Error)

Purpose

Prints all the information in the SYSER zone.

PSYSER is equivalent to PSTACK without arguments.

Syntax

{ PSY } { } { PSYS } ; { } { PSYSER }

Parameters

None.


B-18 47 A2 94UC

B.1.17 Q (QUIT)

Purpose

Leaves the CPDS session at T: level to return to the GCOS 7 session at S: level.

Syntax

{ Q }{ } ;{ QUIT }

Parameters

None.


47 A2 94UC B-19

B.2 Explanation of Acronyms and Abbreviations

asterisk convention The asterisk convention is a means of grouping itemstogether whose names have a common root. A part orparts of the label can be used, the rest being filled in byan * (asterisk).Example: Object names - TXT7801, PC7800,VIP7801 can be regrouped under *780*

cpu controller process unit refers to the memory card of theCNP 7 which has several memories.All CPDS commands specifying the CPU parameterdo not apply to the Datanet because the Datanet onlyhas one single contiguous memory.The option <cpu> appearing in CPDS commandsmeans the last value, explicit or default, keyed in for aprevious CPU command.The alias for memory unit is 'CNS Process Unit' forwhich the abbreviation CPU applies only in thecontext of CPDS. In all other GCOS 7 documentation,the term 'CPU' stands for the 'Central Processor Unit'being the mainframe of the DPS 7/7000 system.

cpu-number the number of the controller process unit in the CNP 7ranging from 1 through 8. The parameter is notapplicable to the Datanet since the Datanet memory,being contiguous, is not divided up into CPUs.The CNP 7 has up to 6 memory units, each memoryunit being a coupler executing its own CNS 7software. The main memory of the CNP 7 isnumbered 8 (the listing displays 80). Supplementarymemory units are numbered 0, 1, 2, 3 and 4 (the listingdisplays 00, 01, 02, 03 and 04). The CNP 7 isconfigured with its main memory and variouspermissible combinations of memory units. Forexample, main memory can be configured withmemory units 1, 2 and 3 without units 0 and 4.

C*md-nm-rls defines the Code portion of the module_name_rls.Example: C*A_VECTOR0_20

current-address the location in the memory dump addressed by thecurrent pointers.


B-20 47 A2 94UC

D*md-nm-rls defines the Data portion of the module_name_rls.Example: D*A_VECTORD0_20

efn external file name referring to a GCOS subfile. Thedefault library is SLLIB.

family-label the name or a family or the names of families forwhich the asterisk convention can be used to groupthem under a single heading.

family-2 2-alpha characters denoted as "ff" in the syntax todefine the family and is the argument (ff) of F*(family), T* (type) and O* (object).Example: SC

F*family-2 Defines the family.Example: F*SC

hexadecimal-address the absolute address in hexadecimal giving the exactlocation in the dump. The address can be modified byadding or substracting a displacement.

hexadecimal-displacementthe displacement in hexadecimal being either thenumber of bytes for the CNP 7 or the number of 2-bytewords for the Datanet, from (+) or to (-) the locationreferenced either by the current address ($) or by aname. The resulting effective address must not exceedthe limits of the dump.

hexadecimal-length the portion of the dump from a given address to beprinted. For the CNP 7, this portion is expressed in thenumber of bytes. For the Datanet, this portion isexpressed in the number of 2-byte words.

label string of a/n characters identifying a specific Module(md-nm-rls), Family, Type or Object or being acommon name using the asterisk convention to groupmodules, families, types and objects, respectivelyunder a single heading.

md-nm-rls module_name_rls, a label appearing in the listing as aresult of the MAP command. Each md-nm-rls isdenoted with the sizes and start-addresses of its Code(C) and Data (D) portions.Example: A_VECTORD0_20

md-nm-rls-label an md-nm-rls name or the names of md-nm-rls's forwhich the asterisk convention can be used to groupthem.


47 A2 94UC B-21

memory_unit see CPU.

memory_unit-number main memory : 8 or 08 or 80memory unit : 0 or 00 1 or 01 2 or 02 3 or 03 4 or 04

object-8 8 a/n characters defining the object.Example: TTU8126A

object-label an object name or the names of objects for which theasterisk convention can be used to group them under asingle heading.

O*ffobject-8 Defines the Object specified by object-8 that belongsto Family ff.Example: O*MDTTU8126A, whereMD is the Family ffTTU8126A is the Object

syser-zone-address optional zone for complementary information on thesystem error detected. If this zone has not beencreated, the PSTACK command will be rejected.

type-4 4-alpha characters defining the type.Example: SYSG

type-label a type name or the names of types for which theasterisk convention can be used to group them under asingle heading.

T*fftype-4 Defines the Type specified by type-4 belonging tofamily ff.Example: T*AFSYSG, whereAF is the Family ffSYSG is the Type


B-22 47 A2 94UC

❑

47 A2 94UC C-1

C. Standard FECM Scenarios

C.1 Standard FECM Scenarios

This appendix describes the standard FECM scenarios delivered with thecorresponding standard network generation NETGEN for the installationconcerned.

The installation can be

• either the DPS 7000/x0 configured with the CNP 7 or the Datanet• or the DPS 7/1x07/10x7 configured with the Datanet only.

The standard FECM scenarios are administration files used by FECM to managefunctions required on the CNP 7 and the Datanet, namely sysgen, load and dump.

The scenarios are located in the STD_SCEN subfile of the SYS.DSACONF library.For further information on the standard network generation corresponding to theFECM scenario, refer to the manual Network Generation.


C-2 47 A2 94UC

C.1.1 CNP 7 for DPS 7000 Systems

There are as many CNP 7 standard scenarios delivered for an installation as thenumber of CNP 7s configured to the DPS 7000.

Each CNP 7 has its own implicit name and takes a unique scid, dsa-address andethernet-address. The implicit name defined for the CNP 7s depends on how manythere are configured as shown in the following table.

1 CNP7 : name CNP02 CNP7s : names CNP0, CNP1 or CNP0, CNP23 CNP7s : names CNP0, CNP1, CNP2 or CNP0, CNP2, CNP34 CNP7s : names CNP0, CNP1, CNP2, CNP3

The name of the FECM scenario, whatever the number of CNP 7s, is STD_SCEN.The following listing gives the scenarios for all 4 CNP 7s.

The scenario for each CNP 7 applicable for a given installation is identified by thename of the CNP 7 in the NODE order.

*---------------------------------------------------------------** STANDARD ADMINISTRATION SCENARIO FILES ** FOR CNP0, 1, 2, 3 IN ARES 3 USED BY FECM SERVER ** (THE STD_SCEN SUBFILE IN SYS.DSACONF LIBRARY). **---------------------------------------------------------------***** STANDARD SCENARIO FOR MICROFRONTAL CNP0*NODE CNP0 -VERSION #CNSTSSCEN RELOADDUMPLOAD CORECNP0IGO -NOPAT2 -NL*SCEN DUMPDUMP*SCEN LOADLOAD CORECNP0IGO -NOPAT2 -NL*

Standard FECM Scenarios

47 A2 94UC C-3

SCEN INSTALLLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP0 02:00 080038Y0Y0Y0 & -REMOTE DPS7 01:00 080038XXXXXX*SCEN SYSGENLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP0 02:00 080038Y0Y0Y0 & -REMOTE DPS7 01:00 080038XXXXXX & -SYSGEN CONF=CONFCNP0C HIST=CONFCNP0H*SCEN TOLDUMPLOAD BLIBTOLGO -PAT2 SLIBPATCH2 -NL** STANDARD SCENARIO FOR MICROFRONTAL CNP1

*NODE CNP1 -VERSION #CNSTSSCEN RELOADDUMPLOAD CORECNP1IGO -NOPAT2 -NL*SCEN DUMPDUMP*SCEN LOADLOAD CORECNP1IGO -NOPAT2 -NL*SCEN INSTALLLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP1 02:01 080038Y1Y1Y1 & -REMOTE DPS7 01:00 080038XXXXXX*SCEN SYSGENLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP1 02:01 080038Y1Y1Y1 & -REMOTE DPS7 01:00 080038XXXXXX & -SYSGEN CONF=CONFCNP1C HIST=CONFCNP1H*SCEN TOLDUMPLOAD BLIBTOLGO -PAT2 SLIBPATCH2 -NL** STANDARD SCENARIO FOR MICROFRONTAL CNP2*


C-4 47 A2 94UC

NODE CNP2 -VERSION #CNSTSSCEN RELOADDUMPLOAD CORECNP2IGO -NOPAT2 -NL*SCEN DUMPDUMP*SCEN LOADLOAD CORECNP2IGO -NOPAT2 -NL*SCEN INSTALLLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP2 02:02 080038Y2Y2Y2 & -REMOTE DPS7 01:00 080038XXXXXX

*SCEN SYSGENLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP2 02:02 080038Y2Y2Y2 & -REMOTE DPS7 01:00 080038XXXXXX & -SYSGEN CONF=CONFCNP2C HIST=CONFCNP2H*SCEN TOLDUMPLOAD BLIBTOLGO -PAT2 SLIBPATCH2 -NL** STANDARD SCENARIO FOR MICROFRONTAL CNP3*NODE CNP3 -VERSION #CNSTSSCEN RELOADDUMPLOAD CORECNP3IGO -NOPAT2 -NL*SCEN DUMPDUMP*SCEN LOADLOAD CORECNP3IGO -NOPAT2 -NL*SCEN INSTALLLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP3 02:03 080038Y3Y3Y3 & -REMOTE DPS7 01:00 080038XXXXXX*


47 A2 94UC C-5

SCEN SYSGENLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP3 02:03 080038Y3Y3Y3 & -REMOTE DPS7 01:00 080038XXXXXX & -SYSGEN CONF=CONFCNP3C HIST=CONFCNP3H*SCEN TOLDUMPLOAD BLIBTOLGO -PAT2 SLIBPATCH2 -NL


C-6 47 A2 94UC

C.1.2 DPS 7000 Systems with Datanet and CNP 7

An alternative FECM scenario is for a Datanet and CNP 7. The name of thescenario is STD_SCEN.

If the installation is configured with more than one Datanet, the user can generatestandard scenarios for the other Datanets. Similarly, for other CNP 7s, the user cangenerate standard scenarios making sure that the Ethernet addresses and the sessioncontrol identifiers for each CNP 7 are different.

In both cases of additional Datanets and CNP 7, the name of the NODE must beunique. The members used for the various administrative functions must also bechanged.

For example, if DN7X in the first NODE order is modified to DN71, all themembers used to service the Datanet named DN71 must be altered toCOREDN71I, COREDN71H, CONFDN71C, BLIBDN71D and BLIBDN71M.

*---------------------------------------------------------------** STANDARD ADMINISTRATION SCENARIO FILES ** FOR CNP 7 AND DN7X USED BY FECM SERVER ** (THE STD_SCEN SUBFILE IN SYS.DSACONF LIBRARY). **---------------------------------------------------------------***** STANDARD SCENARIO FOR MICROFRONTAL CNP 7*NODE CNP7 -VERSION #CNSTSSCEN RELOADDUMPLOAD CORECNP7IGO -NOPAT2 -NL*SCEN DUMPDUMP*SCEN LOADLOAD CORECNP7IGO -NOPAT2 -NL*SCEN INSTALLLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP7 02:00 0800385F0200 & -REMOTE DPS7 01:00 0800385F0100

*


47 A2 94UC C-7

SCEN SYSGENLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP7 02:00 0800385F0200 & -REMOTE DPS7 01:00 0800385F0100 & -SYSGEN CONF=CONFCNP7C HIST=CONFCNP7H*SCEN TOLDUMPLOAD BLIBTOLGO -PAT2 SLIBPATCH2 -NL***** STANDARD SCENARIO FOR DATANET DN7X*NODE DN7X -VERSION #DNSTSSCEN RELOADDUMPLOAD COREDN7XIGO -NOPAT2*SCEN DUMPDUMP*SCEN LOADLOAD COREDN7XIGO -NOPAT2*SCEN SYSGENLOAD BLIBIMAEXC MAP CONFDN7XHGO CONFDN7XC -PATCH SLIBPATCH0 -PAT2 SLIBPATCH2 -SVPAT & COREDN7XI** Datanet Loading for FPG7 running : Direct Lines*SCEN LOADDLOAD BLIBDN7XDGO -NOPAT2** Datanet Loading for FPG7 running : Lines with Modem*SCEN LOADMLOAD BLIBDN7XMGO -NOPAT2


C-8 47 A2 94UC

C.1.3 DPS 7000/XTA with MainWay 2600LE

The name of the FECM scenario for MainWay 2600LE is STD_SCEN.

If the installation is configured with more than one MainWay 2600LE, the user cangenerate standard scenarios for the other MainWay 2600LE.

In cases of additional MainWay 2600LE, the name of the NODE must be unique.

For example, if the NODE order is BC86, all the members used to service theMainWay 2600LE must be associated with his name and be altered toCONFBC86C, CONFBC86H, CONFBC86LC, CONFBC86LS.

EXAMPLE OF SCENARIO

****************************** OCS4 ******************************NODE EA41 START -VERSION D000*SCEN STARTLOADGO -OSI CONFISO_EA41*SCEN DUMPDUMPGO -OSI CONFISO_EA41****************************** MW-LE BC86 ******************************NODE BC86 RELOAD -VERSION V3U4*SCEN SYSGENLOAD BLIBSYSGEN MAP CONFBC86LSGO -SYSGEN CONF=CONFBC86C,HIST=CONFBC86H & -PT SLIBPATCH2 & -SITE BC86 & -REMOTE BC05 065:005 009027FC16F2*SCEN LOADLOAD COREBC86 MAP CONFBC86LCGO -PT SLIBPATCH3 & -SITE BC86 & -REMOTE BC05 065:005 009027FC16F2*SCEN DUMPDUMP DUMPBC86*SCEN RELOAD


47 A2 94UC C-9

DUMP DUMPBC86LOAD COREBC86 MAP CONFBC86LCGO -PT SLIBPATCH3 & -SITE BC86 & -REMOTE BC05 065:005 009027FC16F2*SCEN INSTALLLOAD BLIBSYSGEN MAP CONFBC86LSGO -PT SLIBPATCH2 & -SITE BC86 & -REMOTE BC05 065:005 009027FC16F2*SCEN TOLDUMP DUMPBC86LOAD BLIBTOL MAP CONFBC86LTGO -PT SLIBPATCH2 & -SITE BC86 & -REMOTE BC05 065:005 009027FC16F2****************************** TNS LOCAL CONTROLLER ******************************CT EAD1*SCEN DUMPDUMP DUMPEAD1*❑


C-10 47 A2 94UC

❑

47 A2 94UC D-1

D. Communications Installation

D.1 Standard Network Configurations and FECM Scenarios

This Appendix is abort only the communications software.

The standard basic network configuration represents the NETGEN versiondescribing the minimum communications resources of a DPS 7000 installation.These resources are the DPS 7000 host and its front-end processors.

If the user is not concerned with remote systems of the primary network, thisconfiguration is enough to operate communications sessions.

D.1.1 Standard Basic Network Configuration

Two or three standard source members of network configuration DPS 7000 mustbe in the SYS.DSACONF source library.

These files contain a standard basic network configuration description whichinclude the host itself and the dedicated front-end processors which can be aDatanet DN71xx , up to four CNP 7s or MainWay.

Such a minimum configuration provides the communications capability of theDPS 7000 host. The basic network description includes add-on systems to allowfor future extensions of the network configuration.

D.1.2 Standard FECM Scenarios

A set of standard FECM scenarios associated with the standard basic networkconfiguration description, is in the member STD_SCEN of the SYS.DSACONFsource library.


D-2 47 A2 94UC

D.2 DPS 7000 Series A

D.2.1 Standard Basic Network Configuration

The configuration of this type of host can include up to four CNP 7s, named CNP0to CNP3, as shown in the following table:

Base Cabinet Extension Cabinet Number of

CNP 7spresent

yes

yes

yesyes

yes

yesyesyesyesyes yes

yes

122334

--

- ----

-

-

-

-

-

Basic CNP 7CNP0

TWIN CNP 7CNP0+CNP1

1st CNP 7CNP2

2nd CNP 7CNP3

NOTES:1. In the base cabinet the basic CNP 7 and the TWIN CNP 7 (equivalent to

two CNP 7s) are mutually exclusive.

2. In the above configurations CNP0 is always present.

The standard basic network configuration description in high-level SYSTEMdirectives within a source member NG_CNP7 of the SYS.DSACONF sourcelibrary conforms always with the actual number of CNP7 and add-on systems. Forexample, the following schematic diagram and NG_CNP7 describes the mostcomplete standard basic network configuration with 4 CNP 7s and 2 add-onsystems.

Communications Installation

47 A2 94UC D-3

Schematic Diagram:

y1-y1-y1EA01

ISL xx-xx-xx

y2-y2-y2

Extension cabinet

y3-y3-y3 7f-ff-ff 7f-ff-fe

host DPS 7000 fep1 CNP 7 fep2 CNP 7

CNP0 02:00 CNP1 02:01DPS 7 01:00

Base cabinet

y0-y0-y0

fep3 CNP 7 fep4 CNP 7 add-on DPS 7000 add-on CNP 7

CNP2 02:02 CNP3 02:03 DPSX ff:ff CNPX ff:fe

High Level Directives (SOURCE)

NETWORK DPS7;COMM '********************************************';COMM '** L O C A L S Y S T E M **';COMM '********************************************';SYSTEM DPS7 PF=LSYS SCID=01:00 ISL=(XX-XX-XX EA01);

COMM '********************************************';COMM '** CNP7 REMOTE SYSTEMS **';COMM '********************************************';SYSTEM CNP0 PF=CNP7 SCID=02:00 ISL=(Y0-Y0-Y0);SYSTEM CNP1 PF=CNP7 SCID=02:01 ISL=(Y1-Y1-Y1);SYSTEM CNP2 PF=CNP7 SCID=02:02 ISL=(Y2-Y2-Y2);SYSTEM CNP3 PF=CNP7 SCID=02:03 ISL=(Y3-Y3-Y3);

COMM '********************************************';COMM '** ADD-ON REMOTE SYSTEMS **';COMM '********************************************';SYSTEM DPSX PF=DPS7 SCID=99:255 ISL=(7F-FF-FF);SYSTEM CNPX PF=CNP7 SCID=99:254 ISL=(7F-FF-FE);ENDNETWORK;


D-4 47 A2 94UC

NOTES:1. The generic values (xx-xx-xx, y0-y0-y0, y1-y1-y1, y2-y2-y2, y3-y3-y3)

shown in the diagram are replaced by the actual allocated Ethernetaddresses during the factory processing before being moved into theSYS.DSACONF library.

2. Factory processing includes a compilation by NETGEN of the NG_CNP7source member. The executable network configuration is then stored asSYSTEM in the SYS.DSACORE binary library. See CRNETGENSAVE=SYSTEM in the manual Network Generation.


47 A2 94UC D-5


Together with the basic network configuration described in the NG_CNP7 sourcemember, a set of FECM scenarios is also supplied in the member STD_SCEN ofthe same SYS.DSACONF source library.

The contents of the STD_SCEN member conforms to the basic networkconfiguration described in the paragraph 8.2.1, the complete set comprising 4CNP 7 scenarios.

*-------------------------------------------------** STANDARD ADMINISTRATION SCENARIO FILES ** FOR CNP0, 1, 2, 3 IN ARES 3 USED BY FECM SERVER** (THE STD_SCEN SUBFILE IN SYS.DSACONF LIBRARY). **-------------------------------------------------***** STANDARD SCENARIO FOR MICROFRONTAL CNP0*NODE CNP0 -VERSION #CNSTSSCEN RELOADDUMPLOAD CORECNP0IGO -NOPAT2 -NL*SCEN DUMPDUMP*SCEN LOADLOAD CORECNP0IGO -NOPAT2 -NL*SCEN INSTALLLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP0 02:00 080038Y0Y0Y0 & -REMOTE DPS7 01:00 080038XXXXXX*SCEN SYSGENLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP0 02:00 080038Y0Y0Y0 & -REMOTE DPS7 01:00 080038XXXXXX & -SYSGEN CONF=CONFCNP0C,HIST=CONFCNP0H*SCEN TOLDUMPLOAD BLIBTOLGO -PAT2 SLIBPATCH2 -NL**


D-6 47 A2 94UC

*** STANDARD SCENARIO FOR MICROFRONTAL CNP1*NODE CNP1 -VERSION #CNSTSSCEN RELOADDUMPLOAD CORECNP1IGO -NOPAT2 -NL*SCEN DUMPDUMP*SCEN LOADLOAD CORECNP1IGO -NOPAT2 -NL*SCEN INSTALLLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP1 02:01 080038Y1Y1Y1 & -REMOTE DPS7 01:00 080038XXXXXX*SCEN SYSGENLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP1 02:01 080038Y1Y1Y1 & -REMOTE DPS7 01:00 080038XXXXXX & -SYSGEN CONF=CONFCNP1C,HIST=CONFCNP1H*SCEN TOLDUMPLOAD BLIBTOLGO -PAT2 SLIBPATCH2 -NL***** STANDARD SCENARIO FOR MICROFRONTAL CNP2*NODE CNP2 -VERSION #CNSTSSCEN RELOADDUMPLOAD CORECNP2IGO -NOPAT2 -NL*SCEN DUMPDUMP*SCEN LOADLOAD CORECNP2IGO -NOPAT2 -NL*


47 A2 94UC D-7

SCEN INSTALLLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP2 02:02 080038Y2Y2Y2 & -REMOTE DPS7 01:00 080038XXXXXX*SCEN SYSGENLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP2 02:02 080038Y2Y2Y2 & -REMOTE DPS7 01:00 080038XXXXXX & -SYSGEN CONF=CONFCNP2C,HIST=CONFCNP2H*SCEN TOLDUMPLOAD BLIBTOLGO -PAT2 SLIBPATCH2 -NL***** STANDARD SCENARIO FOR MICROFRONTAL CNP3*NODE CNP3 -VERSION #CNSTSSCEN RELOADDUMPLOAD CORECNP3IGO -NOPAT2 -NL*SCEN DUMPDUMP*SCEN LOADLOAD CORECNP3IGO -NOPAT2 -NL*SCEN INSTALLLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP3 02:03 080038Y3Y3Y3 & -REMOTE DPS7 01:00 080038XXXXXX*SCEN SYSGENLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP3 02:03 080038Y3Y3Y3 & -REMOTE DPS7 01:00 080038XXXXXX & -SYSGEN CONF=CONFCNP3C,HIST=CONFCNP3H*SCEN TOLDUMPLOAD BLIBTOLGO -PAT2 SLIBPATCH2 -NL


D-8 47 A2 94UC

NOTES:1. The generic values represented by XXXXXX, Y0Y0Y0, Y1Y1Y1,

Y2Y2Y2 and Y3Y3Y3 are replaced by the real allocated Ethernetaddresses during the factory processing before being moved into theSYS.DSACONF library. Similarly the term #CNSTS in the first NODEorder is replaced by the real CNS 7 version before being moved into theSYS.DSACONF library.

2. The scenarios located in the STD_SCEN member of the SYS.DSACONFsource library are implicitly taken into account by FECM when no otherscenario member is specified or when FECM is internally started by FEPS.

3. For further details, see Network Operations Reference Manual.


47 A2 94UC D-9

D.3 DPS 7000 SERIES: (200, 300, 500 and 700)

D.3.1 Standard Network Configuration

The network configuration for this type of host can comprise either one or moreDatanet DN71xxs, or one or more CNP 7s, or a combination of Datanets andCNP 7s.

Two members are supplied in the SYS.DSACONF source library which can beused and eventually extended for describing the network configuration actuallydelivered:

• TCOM_NG_CNP7 a standard basic network configuration with only oneCNP 7

• TCOM_NG_DN7X a standard basic network configuration with only oneDatanet.

The standard network configuration source must be extended to include thesystems which are not described.

D.3.1.1 Standard Network Configuration with only one CNP 7

Schematic Diagram:

EA01ISL 5F-01-00

7f-ff-ff 7f-ff-fe

host DPS 7000 fep1 CNP 7

CNP0 02:00DPS 7 01:00

add-on DPS 7000 add-on CNP 7

DPSX ff:ff CNPX ff:fe

5F-02-00

Base cabinet


D-10 47 A2 94UC

High-Level Directives (SOURCE)

NETWORK DPS7;

COMM '********************************************';COMM '** L O C A L S Y S T E M **';COMM '********************************************';SYSTEM DPS7 PF=LSYS SCID=01:00 ISL=(5F-01-00 EA01);

COMM '********************************************';COMM '** C N P 7 R E M O T E S Y S T E M **';COMM '********************************************';SYSTEM CNP7 PF=CNP7 SCID=02:00 ISL=(5F-02-00);

COMM '********************************************';COMM '** ADD-ON REMOTE SYSTEMS **';COMM '********************************************';SYSTEM DPSX PF=DPS7 SCID=99:255 ISL=(7F-FF-FF);SYSTEM CNPX PF=CNP7 SCID=99:254 ISL=(7F-FF-FE);

ENDNETWORK;

NOTES:1. The generic terms 5F0100 and 5F0200 are replaced by the actually

allocated Ethernet addresses during the factory processing.

2. Factory processing includes an NETGEN compilation of this member. Theexecutable configuration is saved as SYSTEM in the SYS.DSACOREbinary library. See CRNETGEN SAVE=SYSTEM in the manual NetworkGeneration.


47 A2 94UC D-11

D.3.1.2 Standard Network Configuration with only Datanet

Schematic Diagram

PSI

host DPS 7000 fep DN71xxDN7X03:00

DPS 701:00

High-Level Directives (SOURCE)

NETWORK DPS7;

COMM '********************************************';COMM '** L O C A L S Y S T E M **';COMM '********************************************';SYSTEM DPS7 PF=LSYS SCID=01:00;

COMM '********************************************';COMM '** D N 7 X R E M O T E S Y S T E M **';COMM '********************************************';SYSTEM DN7X PF=DN7100 SCID=03:00 PSI=CC01;

ENDNETWORK DPS7;

NOTE:This basic network configuration is never compiled during the factoryprocessing. So there is no executable configuration corresponding to it in the theSYS.DSACORE binary library.


D-12 47 A2 94UC


Accompanying the standard network configurations in NG_CNP7 andTCOM_NG_DN7X of the SYS.DSACONF source library, a set of standard FECMscenarios for the Datanet DN7X and for the CNP 7 is also provided in the memberSTD_SCEN of the same library.

*-------------------------------------------------** STANDARD ADMINISTRATION SCENARIO FILES ** FOR CNP7 AND DN7X USED BY FECM SERVER. ** (THE STD_SCEN SUBFILE IN SYS.DSACONF LIBRARY) **-------------------------------------------------**** STANDARD SCENARIO FOR MICROFRONTAL CNP7*NODE CNP7 -VERSION #CNSTSSCEN RELOADDUMPLOAD CORECNP7IGO -NOPAT2 -NL*SCEN DUMPDUMP*SCEN LOADLOAD CORECNP7IGO -NOPAT2 -NL*SCEN INSTALLLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP7 02:00 0800385F0200 & -REMOTE DPS7 01:00 0800385F0100

*SCEN SYSGENLOAD BLIBSYSGENGO -PAT2 SLIBPATCH2 -NL -SITE CNP7 02:00 0800385F0200 & -REMOTE DPS7 01:00 0800385F0100 & -SYSGEN CONF=CONFCNP7C,HIST=CONFCNP7H*SCEN TOLDUMPLOAD BLIBTOLGO -PAT2 SLIBPATCH2 -NL***


47 A2 94UC D-13

** STANDARD SCENARIO FOR DATANET DN7X*NODE DN7X -VERSION #DNSTSSCEN RELOADDUMPLOAD COREDN7XIGO -NOPAT2*SCEN DUMPDUMP*SCEN LOADLOAD COREDN7XIGO -NOPAT2*SCEN SYSGENLOAD BLIBIMAEXC MAP CONFDN7XHGO CONFDN7XC -PATCH SLIBPATCH0 -PAT2 SLIBPATCH2 -SVPAT2 COREDN7XI** DATANET LOADING FOR FPG7 RUNNING : DIRECT LINESSCEN LOADDLOAD BLIBDN7XDGO -NOPAT2** DATANET LOADING FOR FPG7 RUNNING : LINES WITH MODEMSCEN LOADMLOAD BLIBDN7XMGO -NOPAT2


D-14 47 A2 94UC

D.4 Models for Standard Network Configurations and Scenarios

The contents of TCOM_NG_CNP7, TCOM_NG_DN7X and STD_SCEN are theresult of selective extractions from standard members located in the SYS.HSLLIBsource library according to the hardware configuration of the DPS 7000 model:

1. Models for DPS 7000 serie A:

TCOM_NG_CNP7: H_FABNG_A3_NG_CNP0 H_FABNG_A3_NG_CNP01 H_FABNG_A3_NG_CNP012 H_FABNG_A3_NG_CNP0123 H_FABNG_A3_NG_CNP02 H_FABNG_A3_NG_CNP023

STD_SCEN: H_FABNG_A3_STD_SCEN0 H_FABNG_A3_STD_SCEN01 H_FABNG_A3_STD_SCEN012 H_FABNG_A3_STD_SCEN0123 H_FABNG_A3_STD_SCEN02 H_FABNG_A3_STD_SCEN023

2. Models for DPS 7000 series 200, 300, 500 and 700. TCOM_NG_CNP7: TCOM_NG_CNP7

TCOM_NG_DN7X: TCOM_NG_DN7X

STD_SCEN: STD_SCEN

47 A2 94UC E-1

E. Specific Error Codes

This appendix lists the values of the field "Specific Error" in the unsolicitedmessages related to TC objects (type INET, DIWS and CLNS).

0000 /* ADM NO EVENT */

0001 /* Received CR TPDU too short to be decoded, ignore */

0002 /* Received CR TPDU with user data too long */

0003 /* Shutdown State - Cnx Refused */

0004 /* Received CR TPDU with DST-REF not null */

0005 /* Received CR TPDU with Src-Ref not null */

0006 /* Received CR TPDU with bad class (!=4) */

0007 /* Received CR TPDU with bad OPTION (bit 3 or 4 not null) */

0008 /* Received CR TPDU with bad checksum */

0009 /* Received CR TPDU having a bad length */

000A /* Received CR TPDU with bad Calling TSAP-ID parameter length */

000B /* Received CR TPDU having a bad length */

000C /* Received CR TPDU with bad Called TSAP-ID parameter length */

000D /* Received CR TPDU having a bad length */

000E /* Received CR TPDU with bad DSA57 parameter length */

000F /* Received CR TPDU having a bad length */

0010 /* Received CR TPDU with bad TPDU size parameter length */

0011 /* Received CR TPDU with bad TPDU size parameter value */


0013 /* Received CR TPDU with bad Preferred maximum TPDU size parameter length */

0014 /* Received CR TPDU with bad Preferred maximum TPDU size parameter value */


0016 /* Received CR TPDU with bad version parameter length */


0018 /* Received CR TPDU with bad Additional option parameter length */


001A /* Received CR TPDU with bad Alternative Class parameter length */

001B /* unknown parameter: Received CR TPDU having a bad length */

001C /* No session Entity waiting */

001D /* Parameter with bad value in CR */

001E /* No Reference Available */

001F /* Max Retrans Nb has been reached */

0020 /* Received DR TPDU with bad SRC-REF */

0021 /* Received CC TPDU with bad class (!=4) */

0022 /* Received CC TPDU having a bad length */


E-2 47 A2 94UC

0023 /* Received CC TPDU with user data too long */

0024 /* Received ER TPDU too short */

0025 /* Received ER TPDU with bad LI */

0026 /* Received ER TPDU with bad reject cause */

0027 /* Received ER TPDU with bad checksum */

0028 /* Received ER TPDU with bad Invalid TPDU parameter */

0029 /* Received ER TPDU with bad parameter */

002A /* ER TPDU Received */

002B /* Received DR TPDU too short */

002C /* Received DR TPDU with bad LI */

002D /* Received DR TPDU with user data too long */

002E /* Received DR TPDU with bad checksum */

002F /* Received DR TPDU with bad addl info param */

0030 /* Received DR TPDU with bad parameter */

0031 /* Received EA TPDU duplicated or erroneous */

0032 /* Received EA TPDU with bad LI */

0033 /* Received EA TPDU with bad YR-EDTU-NR */

0034 /* Received EA TPDU with bad checksum */

0035 /* Received DT TPDU having a bad length */

0036 /* Received DT TPDU with bad LI */

0037 /* Received DT TPDU with bad ROA (byte 2) */

0038 /* Received DT TPDU with bad checksum */

0039 /* Received DT TPDU out of reference */

003A /* Duplicated Received DT TPDU */

003B /* Received AK TPDU too short to be decoded */

003C /* Received AK TPDU with bad LI */

003D /* Received AK TPDU with YR-TU-RN out of transmit window */

003E /* Received AK TPDU with bad checksum */

003F /* Received AK TPDU with bad variable part length */

0040 /* Received AK TPDU with bad variable part length */

0041 /* Received AK TPDU with bad FCC (lower window edge Bit 8 byte 1 != 0) */

0042 /* Received AK TPDU with bad variable part length */

0043 /* Received AK TPDU with bad parameter */

0044 /* Received AK TPDU with bad Subsequence number */

0045 /* Received AK TPDU with bad Subsequence number */

0046 /* No Expdited were negociated */

0047 /* Received ED TPDU with bad LI */

0048 /* Received ED TPDU too short */

0049 /* Received ED TPDU with user data too long */

004A /* Received ED TPDU with bad EOT (byte 5) */

004B /* Received ED TPDU with bad TPDU-NR (byte 5) */

004C /* Received ED TPDU with bad checksum parameter */

004D /* Received CC TPDU with bad OPTION (bit 3 or 4 not null) */

004E /* Received CC TPDU with bad OPTION (extended format) */

004F /* Received CC TPDU with bad checksum */


0051 /* Received CC TPDU with bad Calling TSAP-ID parameter length */


0053 /* Received CC TPDU with bad Called TSAP-ID parameter length */


0055 /* Received CC TPDU with bad DSA57 parameter length */

Specific Error Codes

47 A2 94UC E-3

0056 /* Received CC TPDU with both TPDU size and Preferred maximum TPDU size parameters */


0058 /* Received CC TPDU with bad TPDU size parameter length */

0059 /* Received CC TPDU with bad TPDU size parameter value */

005A /* Received CC TPDU with unexpected Preferred maximum TPDU size parameter */

005B /* Received CC TPDU with both TPDU size and Preferred maximum TPDU size parameters */

005C /* Received CC TPDU having a bad length */

005D /* Received CC TPDU with bad Preferred maximum TPDU size parameter length */

005E /* Received CC TPDU with bad Preferred maximum TPDU size parameter value */

005F /* Received CC TPDU having a bad length */

0060 /* Received CC TPDU with bad Additional option parameter length */

0061 /* Received CC TPDU with bad Additional option parameter value */


0063 /* Received CC TPDU with bad parameter */

0064 /* Received CC TPDU with incoherence between checksum and Additional options */

0065 /* Received CC TPDU : the references are not matching */

0066 /* Already Received ED TPDU (byte 5) */

0067 /* Received DC TPDU having a bad length */

0068 /* Received DC TPDU with bad LI */

0069 /* TPI Internal ERROR bad sequence number */

006A /* T_CONN_RES on stream with outstanding connections */

006B /* No entry left in CotpNsapTable */

006C /* No entry left in TSAP Table */

006D /* No entry left in TSEL Table */

006E /* Tpi Internal error */

006F /* Protocol error between TPI and TRANSPORT */

0070 /* TPI internal error */

0071 /* Tpi internal error */

0072 /* TPI: T_ALLOPT invalid option for setting */

0073 /* TPI: Option with Null Length */

0074 /* TPI: option unknown */

0075 /* TPI: T_ALLOPT invalid option for setting */

0076 /* TPI: invalid TCO_PRIORITY */

0077 /* TPI: invalid TCO_EXPD */

0078 /* TPI: invalid TCO_LTPDU */

0079 /* TPI: invalid TCO_PREFCLASS */

007A /* TPI: invalid TCO_PRIORITY */

007B /* TPI: invalid TCO_ALTCLASS2 */

007C /* TPI: invalid TCO_ALTCLASS3 */

007D /* TPI: invalid TCO_ALTCLASS4 */

007E /* TPI: invalid TCO_EXTFORM */

007F /* TPI: invalid TCO_FLOWCTRL */

0080 /* TPI: invalid TCO_CHECKSUM */

0081 /* TPI: invalid TCO_ACKTIME */

0082 /* TPI: invalid TCO_RCV_CRDT */

0083 /* TPI: invalid TCO_SND_CRDT */

0084 /* TPI: invalid TCO_RETRY_NB */

0085 /* TPI: invalid TCO_T1_TMR */

0086 /* TPI: invalid TCO_I_TMR */

0087 /* TPI: invalid TCO_W_TMR */

0088 /* TPI: invalid TCO_L_TMR */


E-4 47 A2 94UC

0089 /* TPI: invalid TCO_TTR_TMR */

008A /* TPI: invalid TCO_TWR_TMR */

008B /* TPI: invalid TCO_TS1_TMR */

008C /* TPI: invalid TCO_TS2_TMR */

008D /* TPI: invalid TCO_IVMO */

008E /* TPI: invalid TCO_NETSRV */

008F /* TPI: invalid TCO_X25FAC */

0090 /* TPI: invalid TCO_X25CALLDT */

0091 /* TPI: invalid TCO_MUX */

0092 /* TPI: invalid TCO_DSA57_SIZE */

0093 /* TPI: invalid credit for extended TPDU */

0094 /* TPI: bad send credit with no extended format credit */

0095 /* TPI: No control flow asked with expedited TPDU in class 2 */

0096 /* TPI: Extended or expedited or control flow asked in class 0 */

0097 /* TPI: Invalid flow control flow according to class asked */

0098 /* TPI: asked TPDU size too long in class 0 */

0099 /* TPI: invalid class (preferred 0, 1, 2, 3, 4) ordering */

009A /* TPI: Checksum asked with class other than 4 */

009B /* TPI: asked TPDU too long on LAN with TCO_NETSRV=NULLCLNP */

009C /* TPI: TCO_NETSRV must be NULLCLNP when NSAP is NULL */

009D /* Tpi internal error */

009E /* Tpi internal error */

009F /* TPI: TCO_PRIORITY negotiation failed */

00A0 /* TPI: TCO_EXPD negotiation failed */

00A1 /* TPI: TCO_LTPDU negotiation failed */

00A2 /* TPI: TCO_EXTFORM negotiation failed */

00A3 /* TPI: TCO_FLOWCTRL negotiation failed */

00A4 /* TPI: TCO_CHECKSUM negotiation failed */

00A5 /* TPI: TCO_NETSRV negotiation failed */

00A6 /* TPI: TCO_MUX negotiation failed */

00A7 /* TPI: T_BIND_REQ invalid message */

00A8 /* TPI: T_BIND_REQ invalid address offset */

00A9 /* TPI: T_BIND_REQ invalid address size */

00AA /* TPI: T_BIND_REQ invalid TSEL Length */

00AB /* TPI: T_BIND_REQ invalid LSAP Length */

00AC /* TPI: T_BIND_REQ invalid NSAP Length */

00AD /* TPI: T_BIND_REQ invalid address format */

00AE /* TPI: T_BIND_REQ address already used for listen */

00AF /* TPI: T_OPTMGMT_REQ invalid MGMT_flags */

00B0 /* TPI: T_OPTMGMT_REQ invalid size */

00B1 /* TPI: T_OPTMGMT_REQ invalid offset option */

00B2 /* TPI: T_OPTMGMT_REQ invalid option size */

00B3 /* TPI: T_CONN_RES queue not IDLE */

00B4 /* TPI: T_CONN_REQ invalid size */

00B5 /* TPI: T_CONN_REQ invalid associated data size */

00B6 /* TPI: T_CONN_REQ invalid option offset */

00B7 /* TPI: T_CONN_REQ invalid option size */

00B8 /* TPI: T_CONN_REQ invalid address format */

00B9 /* TPI: T_CONN_REQ invalid TSEL format */

00BA /* TPI: T_CONN_REQ invalid LSAP format */

00BB /* TPI: T_CONN_REQ invalid NSAP format */

Specific Error Codes

47 A2 94UC E-5

00BC /* TPI: T_CONN_REQ invalid address format */

00BD /* TPI: T_CONN_REQ missing TSEL NSAP or LSAP */

00BE /* TPI: T_CONN_RES invalid size */

00BF /* TPI: T_CONN_RES invalid option offset */

00C0 /* TPI: T_CONN_RES invalid option length */

00C1 /* TPI: T_CONN_RES invalid associated data size */

00C2 /* TPI: T_DISCON_REQ invalid size */

00C3 /* TPI: T_DISCON_REQ invalid associated data size */

00C4 /* TPI: T_DISCON_REQ invalid SeqNum */

00C5 /* TPI: T_DATA_REQ: NULL data size but MORE_flag set */

00C6 /* TPI: T_DATA_REQ: NULL data size but MORE_flag set */

00C7 /* T_EXDATA_REQ exceeds ETSDU size or NULL size */

00C8 /* T_EXDATA_REQ exceeds ETSDU size or NULL size */

00C9 /* M_DATA: data size exceeds Max TSDU size */

00CA /* TPI:T_BIND_REQ: (NSAP LSAP) not available */

00CB /* Inactivity Timer expired */

00CC /* Receive CC in Invalid State */

00CD /* Receive DR in CLOSED or CLOSING State */

00CE /* Received TPDU out of state */

00CF /* Remote Transport Asked for Deconnection */

00D0 /* TPI: T_CONN_RES: Invalid Queue (fd) specified */

00D1 /* TPI: T_CONN_REQ: No NSAP available on the machine */

00D2 /* Received CC TPDU with Src-Ref null */

00D3 /* Received CC TPDU asking for use of Expd when CR did not */

00D4 /* Received DR TPDU with Invalid Reason Code */

00D5 /* Not enough memory to accept this connection */


E-6 47 A2 94UC

❑

47 A2 94UC g-1

Glossary

The following table lists acronyms common to the text of this manual and themanual Network Overview.

For the abbreviations of network commands and the objects on which they operate,see Sections 2 and 3.

A

ACAdministrative Correspondent (ADMCOR)

AFAdministrative Function (ADMFUNC)

AGAdministrative Group (ADMGROUP)

ARPAddress Resolution Protocol

ASCIIAmerican Standard Code for Information Interchange

ATSApplicative Transport Service

AUPIAdministrative Utilities Programmatic Interface


g-2 47 A2 94UC

C

CBCable

CCChannel Connection

CCnnCommunications Controller for PSI of Datanet (CPNET)

CHChannel

CLnnCommunications Link (SRST entry for CCLINK PSI)

CLNPConnection Less Network Protocol

CMDCommand, DSAC concept

CNP7Communications Network Processor integrated on the DPS 7000 host

CNS7Communications Network Software (CNP 7 software)

COTPConnection Oriented Transport Protocol

CRNETGENCreate_Network_Generation alias NETGEN

CSACommunications Server Administration

CTController

Glossary

47 A2 94UC g-3

D

DIWSDSA-ISO Work Station

DNDatanet

DNSDistributed Network Supervisor (Datanet software)

DSADistributed Systems Architecture

DSACDistributed Systems Administration and Control

E

EAnnEthernet Adaptor for ISL

EBCDICExtended Binary Coded Decimal Interchange Code

EDDEnter_DSA_Dialog

F

FCP7FDDI Communications Processor 7

FCSFrame Check Sequence

FDDIFiber Distributed Data Interface

FECMFront End Control Management, communications server

FEPFront End Processor

FEPSFront End Processor Support, communications server


g-4 47 A2 94UC

FLAdministrative Filter (ADMFILTER)

FPG7Front-end Processor Generation, DPS 7 utility

G

GKSGraphics Kernel System

H

HDLCHigh-level Data Link Control

HNAPHost to Network controller Administration Protocol

I

ICMPInternet Control Message Protocol

IEEEInstitute of Electrical and Electronic Engineers

IOFInteractive Operator Facility

IPINTERNET Protocol (operates in conjunction with TCP)

IPSInternet Protocol Suite (UDP-TCP/IP)

ISLInter System Link, connection applicable for DPS 7000

ISOInternational Standards Organization

Glossary

47 A2 94UC g-5

L

LANLocal Area Network

LCLogical Connection

LCTLocal Controller (LOCCTLR) identified as EAn or CCnn

LGAdministrative Log (ADMLOG)

LLCLogical Link Control

LNALocal Network Adaptor

LNMLocal Network Manager

LPLLocal Physical Link (LPLINK)

LSAPLink Service Access Point

LSCLocal Session Control (LOCSESS)

LSYSLocal System (LOCSYSTEM)

LTLogical Terminator (LTERMINATOR)

LTSLocal Transport Station, addressed by TSAP


g-6 47 A2 94UC

M

MACMedia Access Control (sublayer)

MAMMessage Access Method

MBMailbox

MCSMessage Control System

MPCMultiplexed Peripheral Controller (DPS 7/1x07/10x7)

N

NCCNetwork Control Center

NGalias NETGEN, synonymous with CRNETGEN

NOINetwork Operator Interface

NPDUNetwork Protocol Data Unit

NRNetwork Route (NETROUTE)

NSAPNetwork Service Access Point

O

OCSOpen Communication Subsystem

OSIOpen Systems Interconnection

Glossary

47 A2 94UC g-7

P

PCPhysical Connection

PDNPublic Data Network

PDUProtocol Data Unit

PLPhysical Line

PPAProtocol Processing Attachment (OCS) to run transport level.

PSIPeripheral Subsystem Interface

Q

QDQueue Directive

QMONQueue Monitor

R

RCTRemote Controller (RMTCTLR)

RFARemote File Access, DSA file transfer (UFT) protocol

RIMRequest Initialization Mode

RIPRouting Information Protocol

RPLRemote Physical Link (RMTPLINK)

RSCRemote Session Control (RMTSESS)


g-8 47 A2 94UC

RSPResponse, DSAC concept

RSYSRemote System (RMTSYSTEM)

RTSRemote Transport Station (RMTTRANSPORT)

S

SBStatistics Block

SCSession Control

SCIDSession Control Identifier

SIMSet Initialization Mode

SNMPSimple Network Management Protocol

SPSAP (Service Access Point)

SPAService Processor Ares, applicable to DPS 7000

SPDUSession Protocol Data Unit

SRSession Route (SESSROUTE)

SRSTSystem Resource and Status Table

SSSession

SSAPSession Service Access Point

SVRServer

SYSGENSystem Generation for DNS and CNS7

Glossary

47 A2 94UC g-9

TTC

Transport Connection

TCPTransmission Control Protocol (operates with IP)

TDSTransactional Driven Subsystem

TMTerminal Manager

TNSTransport and Network Subsystem, comms. server

TPTransport Protocol (TPROTOCOL)

TPDUTransport Protocol Data Unit

TSTransport Station

TSAPTransport Service Access Point

U

UDPUser Datagram Protocol

UFTUnified File Transfer using DSA (RFA) protocol

UMUnsolicited Message, DSAC concept

V

VCAMVirtual Communications Access Method


g-10 47 A2 94UC

X

XCPExtended Communications Protocol: versions XCP1, XCP2

XTA eXtended Twin Architecture

W

WANWide Area Network

WSWorkstation

47 A2 94UC i-1

Index

AACTION

param of DBSVR ............................... 10-31param of STSVR ................................ 3-130

ADDRESS param of DBSVR ................. 10-33ADMINISTRATION param of SNR....... 3-123administrative DSA storage facility .......... 4-68AEP-GCL command correspondence ......... 7-2ALL param of SNR ................................. 3-122APPLICATION param of EDD................2-116APPLICATIONS param of SNR............. 3-123ARP command........................................... 5-20ARPAD subfile............................................ 5-8ASF

administrative storage facility .............. 4-68example of remote loading................... 4-75files....................................................... 4-69operator interface ................................. 4-71prerequisites ......................................... 4-72remote loading by Datanet ................... 4-74running session test on $NASF ............ 4-73startup and execution............................ 4-68using ..................................................... 4-71

asterisk convention in CPDS.....................B-19ATTACH_FCP_IVMO command ............. 5-83ATTIVMO command ................................ 5-83AUTO

param of MDTSVR.............................3-112param of STSVR ................................ 3-130

BBACK command VCAM trace scanner... 10-16BLOCKING param of MDNET QD.......... 3-95BNSE

basic network session exerciser .............. 9-1purpose and function .............................. 9-1SIDE option ............................................ 9-3

CC*md-nm-rls param of CPDS................... B-19CA01 messages............................................ 6-3CA02 messages............................................ 6-4CA03 messages............................................ 6-4CA04 messages............................................ 6-5CA05 messages............................................ 6-5CA06 messages............................................ 6-6CA07 messages............................................ 6-6CA08 messages............................................ 6-6CA09 messages............................................ 6-7CA10 messages............................................ 6-7CA11 messages............................................ 6-8CA12 messages............................................ 6-9CA13 messages............................................ 6-9CA14 messages.......................................... 6-10CA15 messages.......................................... 6-10CA16 messages.......................................... 6-10CA17 messages.......................................... 6-11CA18 messages.......................................... 6-11CA19 messages.......................................... 6-11CA20 messages.......................................... 6-12CA21 messages.......................................... 6-12CA22 messages.......................................... 6-13


i-2 47 A2 94UC

CA23 messages ......................................... 6-13CA24 messages ......................................... 6-14CA25 messages ......................................... 6-14CA26 messages ......................................... 6-15CA27 messages ......................................... 6-15CA28 messages ......................................... 6-15CC03 messages ......................................... 6-16CD01 messages ......................................... 6-17CHANGES param of SNR...................... 3-122CLASS

param of DNET.................................... 2-15param of LNET ...................................... 3-3param of MDNET ................................ 3-66param of MDNET FL........................... 3-82

CLNS error codes........................................ E-1CNP 7

automatic LOAD management............. 4-54description of DUMP scenario ............. 4-60description of LOAD scenario ............. 4-53description of SYSGEN scenario......... 4-37example of LOAD execution ............... 4-54example of LOAD scenario.................. 4-55example of SYSGEN execution........... 4-39example of SYSGEN scenario ............. 4-40loading.................................................... 4-5management ........................................... 4-4scanning dumps......................................B-1startup of FECM in automatic mode ...... 4-9SYSGEN function................................ 4-36

CNS Process Unit........................................B-2CODE

param of DNET.................................... 2-15param of DTL..................................... 2-108param of DTSVR ................................2-111param of MDNET FL........................... 3-84param of TTSVR................................ 3-138

commandobject matrix........................................... 7-3

COMMANDparam of EDD .....................................2-117

comment syntax in scenario ...................... 4-28Common parameters

SNMP commands................................. 5-49CONF literal (CNP 7 SYSGEN) ............... 4-38CONF_RPRT subfile................................... 5-6CONNECT param of EDD.......................2-116

CONTINUEparam of MDTL.................................. 3-110param of STL...................................... 3-126

controller functions.................................... 4-67CORE

param for CNP 7 LOAD....................... 4-53param for Datanet LOAD ..................... 4-50

COUNT_N1RTS mod param of MDNET TS ......... 3-106

CPDSCPU command....................................... B-2DESC command .................................... B-3description ............................................. B-1DISPLACE command ........................... B-4ECHO command.................................... B-5GOTO command ................................... B-6MAP command...................................... B-7MAPFAMILY command ....................... B-8MAPTYPE command............................ B-9NODISPLACE command.................... B-10parameter descriptions......................... B-19PITCB command ..................................B-11POFF command................................... B-12PON command .................................... B-13PRINT command................................. B-14PRINTALL command.......................... B-15PSTACK command ............................. B-16PSYSER command.............................. B-17QUIT command................................... B-18

CPU command (CPDS) .............................. B-2CRAL command .......................................... 2-6CREATE_FCP_IVMO command.............. 5-85CREDIT

RTS mod param of MDNET TS ......... 3-106CRIVMO command................................... 5-85CRRB command.......................................... 2-8CRSNMPDOC command.......................... 5-51

DDACTFCP command............................... 10-75Datanet

automatic LOAD management ............. 4-51description of DUMP............................ 4-60description of LOAD............................ 4-50description of SYSGEN........................ 4-32

Index

47 A2 94UC i-3

example of DUMP ............................... 4-62example of LOAD................................ 4-52example of SYSGEN ........................... 4-35management ........................................... 4-3remote loading...................................... 4-74scanning dumps......................................B-1startup in automatic mode ...................... 4-9startup of FECM..................................... 4-8startup of FEPS ...................................... 4-9SYSGEN function................................ 4-30

DBSVR command.......................... 2-10, 10-30DEA subfile 5-7DEBUG param of DBSVR...................... 10-32DEBUG_SERVER command ................. 10-30debugging applications............................ 10-29DELAY

param of MDTL ................................. 3-109param of STL ..................................... 3-126

DELETE param of PRTTR ......................3-115DESC command (CPDS) ............................B-3DIR example ............................................. 4-30DISCONNECT param of EDD ................2-116DISPLACE command (CPDS) ...................B-4DISPLAY param of EDD .........................2-117DISPLAY_FCP_ACTIVITY command.. 10-75DISPLAY_FCP_MAC_ADDR command10-

78DISPLAY_FCP_TCIVMO command....... 5-87DISPLAY_IVMO_LINK command.......... 5-89DLAL command.........................................2-11DLRB command .............................. 2-12, 2-13DMAC command .................................... 10-78DNET command

AC ........................................................ 2-18AF......................................................... 2-20AG........................................................ 2-22AL ........................................................ 2-24CB ........................................................ 2-26CC ........................................................ 2-28CH ........................................................ 2-31CT......................................................... 2-33FL ......................................................... 2-38general syntax....................................... 2-14ID ......................................................... 2-41IS .......................................................... 2-43LC......................................................... 2-46

LCT of CT ............................................ 2-33LG......................................................... 2-49LPL of PL ............................................. 2-62LSC of SC............................................. 2-80LSYS of SY.......................................... 2-92LTS of TS ........................................... 2-101MB........................................................ 2-51NK ........................................................ 2-53NR......................................................... 2-55OP......................................................... 2-57PC ......................................................... 2-59PL ......................................................... 2-62QD ........................................................ 2-67RB......................................................... 2-74RCT of CT ............................................ 2-36RPL of PL............................................. 2-65RSC of SC ............................................ 2-82RSYS of SY.......................................... 2-94RTS of TS ........................................... 2-103SA......................................................... 2-76SC ......................................................... 2-80SP.......................................................... 2-84SR ......................................................... 2-86SS.......................................................... 2-89SY......................................................... 2-92TC......................................................... 2-96TS ....................................................... 2-101

DNET CommandSB ......................................................... 2-78

DNR command ........................................ 2-107Documentation commands ........................ 5-49DOMAIN

param of DBSVR................................ 10-32param of MDNET FL ........................... 3-81

DPIVMO command................................... 5-87DPLKIVMO command ............................. 5-89DSA_OSI_DOMAIN param of SNR ...... 3-123DSA_TRACE_LEVEL param of SVTR . 10-15DTL Command ........................................ 2-108DTSVR command ................................... 2-110DUMP

FEP dump ............................................. 4-60on LNM ................................................ 4-67on MPC................................................. 4-67on SPA .................................................. 4-67order for CNP 7 .................................... 4-60


i-4 47 A2 94UC

order for Datanet .................................. 4-60order in FCP7 scenario......................... 5-15syntax in scenario................................. 4-27VCAM trace scanner command ......... 10-16

DUMP order .............................................. 5-10DVTR command ......................................2-114DYNALC param of SVTR...................... 10-15

EECHO command ..................................... 10-71ECHO command (CPDS)............................B-5EDD command.........................................2-115EDTRACE command.............................. 10-59ELAPSE

param of MDTL ................................. 3-109param of STL ..................................... 3-126

END example ............................................ 4-30END_DISP_FCP_ACTIVITY command 10-77ENDDACT command ............................. 10-77ENDECHO command ............................. 10-74ENDGETAR command ............................. 5-56ENDGETARP command........................... 5-56ENDGETCN command............................. 5-57ENDGETCONN command....................... 5-57ENDGETNET command .......................... 5-58ENDGETNT command............................. 5-58ENDGETROUTE command..................... 5-59ENDGETRT command ............................. 5-59ENDGETUD command ............................ 5-60ENDGETUDP command .......................... 5-60ENDNETST command.............................. 5-27ENDPING command................................. 5-28ENDS

param of DNET IS ............................... 2-43param of DNET LC.............................. 2-46param of DNET SS .............................. 2-89param of LNET IS................................ 3-24param of LNET LC .............................. 3-26param of LNET SS............................... 3-52

ENDSNMP command ............................... 5-61ENDSNMPG command ............................ 5-62ENDSNMPGET command ....................... 5-62ENDSNMPN command ............................ 5-63ENDSNMPNEXT command..................... 5-63ENDSNMPS command............................. 5-64

ENDSNMPSET command ........................ 5-64ENDTEST command............................... 10-70ERROR_EVENTS param of SNR........... 3-121ERROR_REPORT

param of MDTL.................................. 3-110param of STL...................................... 3-127

ERRORS param of SNR.......................... 3-122ETC_HOSTS subfile ................................... 5-5ETC_NETWORKS subfile.......................... 5-5EVENTS param of SNR.......................... 3-121EXCHANGES param of STL.................. 3-127

FFCP 7

DACTFCP command.......................... 10-75DISPLAY_FCP_ACTIVITY command10-75DISPLAY_FCP_MAC_ADDR command............................................................ 10-78DMAC command ............................... 10-78ECHO command................................. 10-71EDTRACE command ......................... 10-59END_DISP_FCP_ACTIVITY command10-77END_ECHO_SENDING command... 10-74ENDDACT command ........................ 10-77ENDECHO command ........................ 10-74ENDTEST command.......................... 10-70FCP_NOTRACE_TPDU command ... 10-53FCP_SEETRACE_TPDU command.. 10-55FCP_TRACE_TPDU command......... 10-50FCPMACADDR command................ 10-78NOTRACE command..............10-44, 10-57NOTRACETPDU command .............. 10-53NTRCTPDU command ...................... 10-53RESTART_FCP_ADMIN command.. 10-79RSTADM command ........................... 10-79SEETRACE command ............10-46, 10-57SEETRACE_TPDU command........... 10-55SEETRACETPDU command............. 10-55SEND_ECHO_REQUEST command 10-71STRCTPDU command ............10-55, 10-57TEST command.................................. 10-68trace .................................................... 10-36TRACE command ...................10-41, 10-57

Index

47 A2 94UC i-5

TRACETPDU command ................... 10-50TRCTPDU command.............. 10-50, 10-57XID command.................................... 10-66

FCP_EXTENDED_GET_ATT_TC command.............................................. 5-91

FCP_NOTRACE_TPDU command........ 10-53FCP_SEETRACE_TPDU command ...... 10-55FCP_TRACE_TPDU command.............. 10-50FCP7

driver messages .................................... 6-56incremental configuration .................... 5-96scenarios................................................. 5-9server messages.................................... 6-59software version ....................................5-11

FCPMACADDR command..................... 10-78FE01 messages .......................................... 6-18FE02 messages .......................................... 6-18FE03 messages .......................................... 6-18FE04 messages .......................................... 6-19FE05 messages .......................................... 6-19FE06 messages .......................................... 6-19FE08 messages .......................................... 6-20FE09 messages .......................................... 6-20FE10 messages .......................................... 6-21FE11 messages .......................................... 6-21FE12 messages .......................................... 6-21FE13 messages .......................................... 6-22FE14 messages .......................................... 6-22FE15 messages .......................................... 6-23FE16 messages .......................................... 6-24FE17 messages .......................................... 6-24FE18 messages .......................................... 6-24FE19 messages .......................................... 6-25FE20 messages .......................................... 6-25FE21 messages .......................................... 6-26FE30 messages .......................................... 6-26FE31 messages ............................... 6-27, 6-135FE32 messages .......................................... 6-27FE33 messages .......................................... 6-28FE34 messages .......................................... 6-28FE35 messages .......................................... 6-29FE36 messages .......................................... 6-29FE37 messages .......................................... 6-30FE38 messages .......................................... 6-30FE39 messages .......................................... 6-30FE40 messages .......................................... 6-31

FE41 messages........................................... 6-31FE42 messages........................................... 6-31FE43 messages........................................... 6-32FE44 messages........................................... 6-32FE45 messages........................................... 6-33FE46 messages........................................... 6-33FE47 messages........................................... 6-34FE48 messages........................................... 6-34FECM

functions ................................................. 4-1operability............................................... 4-2scenario for administrative functions...... 4-7service messages.................................... A-1standard scenario ................................... D-1standard scenarios.................................. C-1std scenario for CNP 7 ................. C-2, D-12std scenario for Datanet ............... C-2, D-12std scenario for DPS 7000/CNP 7.......... C-2std scenario for first CNP 7............ C-2, D-5std scenario for fourth CNP 7 ........ C-2, D-5std scenario for second CNP 7....... C-2, D-5std scenario for third CNP 7 .......... C-2, D-5

FEPadministrative functions ......................... 4-7definition................................................. 4-2DUMP function .................................... 4-60libraries for administration and control 4-11LOAD function..................................... 4-50SYSGEN function ................................ 4-30

FEPS file trace ......................................... 10-22FILE

param of PRTTR................................. 3-115param of SVTR................................... 10-15

file naming convention .............................. 4-29file parameter

SNMP commands ................................. 5-49files used by OCS ........................................ 5-5FILESTAT param of DBSVR .................. 10-33FORWARD command (VCAM trace) ..... 10-16FR01 messages .......................................... 6-35FR02 messages .......................................... 6-37FR03 messages .......................................... 6-41FR04 messages .......................................... 6-43FR05 messages .......................................... 6-44FROM_SYSTEM param of SNR ............ 3-121


i-6 47 A2 94UC

GGCL-AEP command correspondence ......... 7-2GET_ARP command................................. 5-65GET_NET command................................. 5-67GET_ROUTE command ........................... 5-69GET_TCP_CONNECTION command ..... 5-71GET_UDP command................................. 5-73GETARP command ................................... 5-65GETNET command................................... 5-67GETROUTE command ............................. 5-69GETTCPCONN command........................ 5-71GETTCPTN command.............................. 5-71GETUDP command................................... 5-73GO

for Datanet LOAD................................ 4-50for Datanet SYSGEN ........................... 4-33general syntax....................................... 4-28order for CNP 7 LOAD........................ 4-53order for CNP 7 SYSGEN.................... 4-38order in FCP7 scenario......................... 5-17

GO order 5-10GOTO command (CPDS)............................B-6

HHIST

literal in CNP 7 SYSGEN .................... 4-38param for CNP 7 SYSGEN.................. 4-37

HMSG param of EDD..............................2-117HOMSG param of EDD...........................2-117host parameter

SNMP commands................................. 5-49

IID

param of DTL..................................... 2-108param of MDTL ................................. 3-109param of TTL ..................................... 3-136

IFCONFIG command................................ 5-29incremental configuration (FCP7)............. 5-96INET error codes ......................................... E-1INMODE param of MDNET QD.............. 3-93INTERVAL param of MDNET SB.......... 3-102

ISL controllertrace .................................................... 10-35

ISO_TRACE_LEVEL param of SVTR... 10-15ITCMD param of EDD............................ 2-117ITER

param of MDTL.................................. 3-109param of STL...................................... 3-126

LLC

param for Datanet local DUMP............ 4-60param for Datanet local LOAD ............ 4-51param for Datanet local SYSGEN........ 4-34param for Datanet SYSGEN................. 4-34

LCPAT2 param for Datanet SYSGEN....... 4-34LCT 4-4LEVEL

param of DBSVR................................ 10-32param of MDNET FL ........................... 3-85

LINELG param of MDNET QD................ 3-95LIST_FCP_TCIVMO command ............... 5-93LMBX param of STL .............................. 3-127LNA

startup of FECM in automatic mode .... 4-10trace .................................................... 10-35

LNET commandAC........................................................... 3-5AF........................................................... 3-7AG .......................................................... 3-9AL......................................................... 3-11CB......................................................... 3-13CC......................................................... 3-14CH......................................................... 3-16CT......................................................... 3-18FL ......................................................... 3-21general syntax ......................................... 3-2ID.......................................................... 3-23IS........................................................... 3-24LC......................................................... 3-26LCT of CT ............................................ 3-18LG......................................................... 3-28LPL of PL ............................................. 3-35LSC of SC............................................. 3-46LSYS of SY.......................................... 3-54LTS of TS ............................................. 3-59

Index

47 A2 94UC i-7

MB ....................................................... 3-29NK........................................................ 3-31NR ........................................................ 3-33OP......................................................... 3-34PL ......................................................... 3-35QD........................................................ 3-38RB ........................................................ 3-40RCT of CT............................................ 3-19RPL of PL............................................. 3-36RSC of SC............................................ 3-47RSYS of SY ......................................... 3-55RTS of TS............................................. 3-61SA......................................................... 3-42SB......................................................... 3-44SC......................................................... 3-46SP ......................................................... 3-49SR......................................................... 3-50SS ......................................................... 3-52SY......................................................... 3-54TC......................................................... 3-57TS ......................................................... 3-59WS........................................................ 3-64

LOADFEP load ............................................... 4-50on LMN................................................ 4-67on MPC ................................................ 4-67on SPA.................................................. 4-67order in FCP7 scenario......................... 5-16syntax for CNP 7 .................................. 4-53syntax for CNP 7 SYSGEN.................. 4-37syntax for Datanet ................................ 4-50syntax for Datanet local SYSGEN....... 4-34syntax for Datanet SYSGEN................ 4-32syntax for local LOAD on Datanet ...... 4-51syntax of in scenario............................. 4-27

LOAD order5-10LOCATE command (VCAM trace)......... 10-16LOG

param of DBSVR ............................... 10-31param of STSVR ................................ 3-130

LOGICparam of DNET FL .............................. 2-38param of LNET FL............................... 3-21param of MDNET FL........................... 3-81

LOW_LAYERS param of SNR............... 3-124LSIVMO command................................... 5-93

MMAP

LCT param of DNET CT...................... 2-33LCT param of LNET CT ...................... 3-18LCT param of MDNET CT .................. 3-77LPL param of DNET PL....................... 2-62LPL param of LNET PL ....................... 3-35LPL param of MDNET PL ................... 3-90LTS param of DNET TS..................... 2-102LTS param of LNET TS ....................... 3-59param for CNP 7 LOAD....................... 4-53param for CNP 7 SYSGEN .................. 4-38param for Datanet SYSGEN........4-32, 4-50param of DNET .................................... 2-16param of DNET AC.............................. 2-18param of DNET AF .............................. 2-20param of DNET AG.............................. 2-22param of DNET CB.............................. 2-26param of DNET CC.............................. 2-28param of DNET CH.............................. 2-31param of DNET FL............................... 2-38param of DNET IS................................ 2-43param of DNET LC .............................. 2-46param of DNET LG.............................. 2-49param of DNET MB ............................. 2-51param of DNET NR.............................. 2-55param of DNET OP .............................. 2-57param of DNET PC .............................. 2-59param of DNET QD.............................. 2-68param of DNET SA .............................. 2-76param of DNET SB .............................. 2-78param of DNET SP............................... 2-84param of DNET SR .............................. 2-86param of DNET SS............................... 2-89param of LNET....................................... 3-3param of LNET AC ................................ 3-5param of LNET AF................................. 3-7param of LNET AG ................................ 3-9param of LNET CB .............................. 3-13param of LNET CC .............................. 3-14param of LNET CH .............................. 3-16param of LNET FL ............................... 3-21param of LNET IS ................................ 3-24param of LNET LC............................... 3-26param of LNET LG .............................. 3-28


i-8 47 A2 94UC

param of LNET MB ............................. 3-29param of LNET NR.............................. 3-33param of LNET OP .............................. 3-34param of LNET QD.............................. 3-39param of LNET SA .............................. 3-42param of LNET SB .............................. 3-44param of LNET SP............................... 3-49param of LNET SR .............................. 3-50param of LNET SS............................... 3-52param of LNET TC .............................. 3-57param of LNET WS ............................. 3-64param of MDNET ................................ 3-66param of MDNET AC .......................... 3-68param of MDNET AF .......................... 3-70param of MDNET AG.......................... 3-72param of MDNET CH.......................... 3-75param of MDNET FL........................... 3-81param of MDNET LG.......................... 3-86param of MDNET OP .......................... 3-88param of MDNET QD.......................... 3-93param of MDNET SA .......................... 3-99param of MDNET SB ........................ 3-101param of MDNET SR ........................ 3-103RCT param of DNET CT ..................... 2-36RCT param of LNET CT...................... 3-20RCT param of MDNET CT.................. 3-79RPL param of DNET PL ...................... 2-65RPL param of LNET PL ...................... 3-37RSC param of DNET SC ..................... 2-82RSC param of LNET SC...................... 3-48RSYS param of DNET SY................... 2-94RSYS param of LNET SY ................... 3-55RTS param of DNET TS .................... 2-103RTS param of LNET TS....................... 3-61RTS param of MDNET TS................. 3-106

MAP command (CPDS) ..............................B-7MAPFAMILY command (CPDS) ...............B-8MAPTYPE command (CPDS)....................B-9MAXTC

RTS mod param of MDNET TS......... 3-106MAXTUSZ

RTS mod param of MDNET TS......... 3-106MBx

param of DBSVR ............................... 10-34param of STTR................................... 3-133

MDIVMO command ................................. 5-94

MDNET commandAC......................................................... 3-68AF......................................................... 3-70AG ........................................................ 3-72AL......................................................... 3-74CH......................................................... 3-75CT......................................................... 3-77FL ......................................................... 3-80general syntax ....................................... 3-65LCT of CT ............................................ 3-77LG......................................................... 3-86LPL of PL ............................................. 3-90OP......................................................... 3-88PL ......................................................... 3-90QD ........................................................ 3-92RB......................................................... 3-97RCT of CT ............................................ 3-78RTS of TS ........................................... 3-105SA......................................................... 3-99SB ....................................................... 3-101SR ....................................................... 3-103TS ....................................................... 3-105

MDTL command ..................................... 3-109MDTSVR command................................ 3-111MESSAGE param of SNDQ.................... 3-118messages

CA type................................................... 6-3categories ................................................ 6-1CC close.................................................. 8-7CC error .................................................. 8-8CC history report .................................... 8-9CC open ...........................................8-5, 8-6CC type................................................. 6-16CD type................................................. 6-17CH error................................................ 8-10composition of unsolicited...................... 8-1CT error ................................................ 8-11EX history report .................................. 8-12FE type.................................................. 6-18FR type ................................................. 6-35FT close ................................................ 8-26FT error................................................. 8-31FT file delete......................................... 8-22FT file rename ...................................... 8-24FT history report ................................... 8-29FT open................................................. 8-14

Index

47 A2 94UC i-9

FT open fail .......................................... 8-16FTX file create ..................................... 8-19FX close ............................................... 8-35FX error unsolicited ............................. 8-36FX open................................................ 8-33FX open fail.......................................... 8-34IS close ................................................. 8-41IS history report.................................... 8-43IS open ................................................. 8-37IS open fail ........................................... 8-39LC close ............................................... 8-46LC history report .................................. 8-47LC open................................................ 8-44LC open fail.......................................... 8-45LG close ............................................... 8-51LG open................................................ 8-49LG open fail ......................................... 8-50NA error ............................................... 8-52NA type ................................................ 6-45NC type ................................................ 6-56NG type .............................................. 6-147NK........................................................ 8-53QC type .............................................. 6-157SS close ................................................ 8-56SS history report................................... 8-57SS open ................................................ 8-54SS open fail .......................................... 8-55SU completed ....................................... 8-59summary................................................. 8-3TC close ............................................... 8-64TC error................................................ 8-66TC history report .................................. 8-67TC open................................................ 8-60TF type ............................................... 6-162TL close................................................ 8-70TL error ................................................ 8-72TL execute............................................ 8-69TL history report .................................. 8-71TP type ............................................... 6-170TS error ................................................ 8-73

MODIF_COMMANDS param of SNR... 3-122MODIFY_FCP_IVMO command............. 5-94MODIFY_LOCAL_PROFILE command

(VCAM trace) ..................... 10-17MORE

param of DNET.................................... 2-16

param of DTL ..................................... 2-108param of LNET....................................... 3-4param of MDNET................................. 3-67param of MDTL.................................. 3-110param of STL...................................... 3-127param of TTL...................................... 3-136

multiversion releases ................................... 4-6

NNA10 messages ......................................... 6-45NA11 messages.......................................... 6-45NA12 messages ......................................... 6-46NA20 messages ......................................... 6-46NA21 messages ......................................... 6-47NA22 messages ......................................... 6-47NA24 messages ......................................... 6-48NA25 messages ......................................... 6-49NA30 messages ......................................... 6-50NA50 messages ......................................... 6-50NA51 messages ......................................... 6-51NA53 messages ......................................... 6-51NA54 messages ......................................... 6-52NA55 messages ......................................... 6-52NA56 messages ......................................... 6-53NA57 messages ......................................... 6-54NA59 messages ......................................... 6-55NAME

param of DTSVR................................ 2-110param of SNDQ.................................. 3-118param of TTSVR ................................ 3-138

NAUTO param of NODE in scenario........ 4-26NBLINES param of MDNET QD ............. 3-95NC01 messages.......................................... 6-59NC05 messages.......................................... 6-70NC06 messages.......................................... 6-76NC07 messages.......................................... 6-83NC08 messages.......................................... 6-87NC10 messages.......................................... 6-56NC48 messages.......................................... 6-87NC49 messages.......................................... 6-90NC50 messages.......................................... 6-91NC51 messages.......................................... 6-95NC52 messages........................................ 6-101NC53 messages........................................ 6-102NC54 messages........................................ 6-104


i-10 47 A2 94UC

NC55 messages ........................................6-112NC56 messages ........................................6-114NC57 messages ........................................6-115NC58 messages ........................................6-115NC59 messages ........................................6-116NC60 messages ........................................6-116NC62 messages ........................................6-118NC63 messages ........................................6-119NC65 messages ....................................... 6-122NC66 messages ....................................... 6-123NC68 messages ....................................... 6-123NC69 messages ....................................... 6-126NC72 messages ....................................... 6-127NC74 messages ....................................... 6-130NC78 messages ....................................... 6-132NC84 messages ....................................... 6-137NC87 messages ....................................... 6-139NC90 messages ....................................... 6-140NC92 messages ....................................... 6-142NC94 messages ....................................... 6-144NC96 messages ....................................... 6-145NC98 messages ....................................... 6-145NCC_MG_DOCFILES subfile ................... 5-7NCC_MG_FCP_MIB subfile...................... 5-7NCC_MG_RFC1213 subfile....................... 5-7NCC_MG_RFC1285 subfile....................... 5-7NETSTAT command ................................. 5-34network

std basic configuration .......... D-1, D-2, D-9std config (high-level directives)............D-3

network management .................................. 1-2network operations ...................................... 1-2NEW param for CNP 7 SYSGEN ............. 4-37NEW_LOGIC param of MDNET FL........ 3-81NEW_NSAP param of MDNET AL ......... 3-74NEW_STATE

LCT param of MDNET CT.................. 3-78LPL param of MDNET PL................... 3-91param of MDNET ................................ 3-66param of MDNET AC .......................... 3-69param of MDNET AF .......................... 3-71param of MDNET AG.......................... 3-73param of MDNET CH.......................... 3-76param of MDNET FL........................... 3-81param of MDNET LG.......................... 3-86param of MDNET OP .......................... 3-88

param of MDNET QD.......................... 3-93param of MDNET SB......................... 3-102param of MDNET SR......................... 3-104

NEW_TYPE param of MDNET FL .......... 3-81NEWLOG param of DBSVR .................. 10-31NEXT command (VCAM trace).............. 10-16NG01 messages ....................................... 6-147NG02 messages ....................................... 6-147NG03 messages ....................................... 6-149NG04 messages ....................................... 6-149NG05 messages ....................................... 6-149NG06 messages ....................................... 6-150NG07 messages ....................................... 6-150NG08 messages ....................................... 6-150NG09 messages ....................................... 6-151NG10 messages ....................................... 6-151NG11 messages........................................ 6-152NG13 messages ....................................... 6-152NG14 messages ....................................... 6-153NG15 messages ....................................... 6-153NG16 messages ....................................... 6-154NG17 messages ....................................... 6-154NG18 messages ....................................... 6-155NG19 messages ....................................... 6-155NG20 messages ....................................... 6-156NL

param for CNP 7 LOAD....................... 4-54param for CNP 7 SYSGEN .................. 4-39param for Datanet LOAD ..................... 4-51

NODEexamples ......................................4-23, 4-24order in FCP7 scenario ......................... 5-13syntax in scenario ................................. 4-25

NODISPLACE command (CPDS) ........... B-10NOPAT2 param for Datanet LOAD........... 4-50NOTRACE command...................10-44, 10-57NOTRACETPDU command ................... 10-53NP

param for CNP 7 LOAD....................... 4-53param for Datanet LOAD ..................... 4-50

NSAPparam of DNET SA .............................. 2-76param of LNET AL............................... 3-11param of LNET RB .............................. 3-40param of LNET SA............................... 3-42param of MDNET SA........................... 3-99

Index

47 A2 94UC i-11

NSAP_ID param of LNET RB.................. 3-40NSAP_MASK param of LNET RB .......... 3-40NTRCTPDU command ........................... 10-53NUMBER param of LNET ......................... 3-3

Oobject

command matrix..................................... 7-3OBJECT

param of DBSVR ............................... 10-33param of DNET.................................... 2-15param of DNET CC.............................. 2-28param of DNET ID............................... 2-41param of DNET QD ............................. 2-68param of LNET ...................................... 3-3param of LNET CC.............................. 3-14param of LNET ID ............................... 3-23param of LNET QD.............................. 3-39param of MDNET ................................ 3-66param of MDNET LG.......................... 3-86param of MDNET QD.......................... 3-93param of STL ..................................... 3-127param of TTL ..................................... 3-136

object class unsolicited events..................... 8-2OCS

adding a TCIVMO ............................... 5-85ARP command ..................................... 5-20attaching RTS or RNSAP to IVMO5-83, 5-89CRAL command .................................... 2-6CRRB command .................................... 2-8displaying attributes of TC objects....... 5-91displaying IVMO attributes.................. 5-87DLAL command ...................................2-11DLRB command ......................... 2-12, 2-13DNET AL command ............................ 2-24DNET NK command............................ 2-53DNET RB command ............................ 2-74DNET TS............................................ 2-105DTSVR command...............................2-110ENDNETST command ........................ 5-27ENDPING command ........................... 5-28FCP7 incremental configuration .......... 5-96IFCONFIG command........................... 5-29IPS administration.................................. 5-2

listing IVMOs....................................... 5-93LNET AL command ............................. 3-11LNET NK command............................. 3-31MDNET AL command ......................... 3-74MDNET TS ........................................ 3-107modifying IVMO attributes .................. 5-94NETSTAT command............................. 5-34PING command .................................... 5-40ROUTE command ................................ 5-42starting .................................................... 5-3stopping .................................................. 5-4STSVR command ............................... 3-128trace .................................................... 10-28TTSVR command............................... 3-137

OCS LNET RB command ......................... 3-40OLD param for CNP 7 SYSGEN .............. 4-37OUTMODE param of MDNET QD .......... 3-94

PP0 param for Datanet SYSGEN................. 4-33P2

param for CNP 7 LOAD....................... 4-53param for CNP 7 SYSGEN .................. 4-39param for Datanet LOAD ..................... 4-50param for Datanet SYSGEN................. 4-34

passthroughactivating and deactivating ................... 10-2display connection ................................ 10-5example of console listing .................... 10-7for maintenance .................................... 10-1output to console and SYSOUT ........... 10-6

PAT2param for Datanet LOAD ..................... 4-50param for Datanet SYSGEN................. 4-34

PATCH param for Datanet SYSGEN......... 4-33PATCH1 example....................................... 4-29PING command ......................................... 5-40PITCB command (CPDS)..........................B-11POFF command (CPDS) .......................... B-12PON command (CPDS) ............................ B-13POSITION param of DBSVR.................. 10-33POWER param of MDNET FL ................. 3-81PPA subfile 5-7PREVIOUS command (VCAM trace)..... 10-17PRINT command (CPDS) ........................ B-14


i-12 47 A2 94UC

PRINTALL command (CPDS)..................B-15PROCESS param of PRTTR ....................3-115PRT_W param of PRTTR.........................3-115PRTLIB

param of EDD .....................................2-117PRTTR command.....................................3-114PSTACK command (CPDS)......................B-16PSYSER command (CPDS)......................B-17

QQC06 messages ....................................... 6-157QC08 messages ....................................... 6-157QC13 messages ....................................... 6-158QC15 messages ....................................... 6-158QC30 messages ....................................... 6-159QC32 messages ....................................... 6-159QC33 messages ....................................... 6-159QC34 messages ....................................... 6-160QC36 messages ....................................... 6-161QC42 messages ....................................... 6-161QUIT command (CPDS) ...........................B-18QUOTA param of MDNET SR ............... 3-104

RREADY param of MDTSVR ...................3-113REPEAT param of MDTSVR ..................3-113Request commands.................................... 5-48response

LONG for RTS of DNET TS ............. 2-104SHORT for RTS of DNET TS............ 2-104

responsesHISTORY for DNET CC ..................... 2-29HISTORY for DNET IS ....................... 2-44HISTORY for DNET LC...................... 2-47HISTORY for DNET PC (LPL) ........... 2-60HISTORY for DNET PC (RPL)........... 2-60HISTORY for DNET SS ...................... 2-90HISTORY for DNET TC...................... 2-97LONG for DNET AC ........................... 2-19LONG for DNET AF............................ 2-21LONG for DNET AG........................... 2-23LONG for DNET CC ........................... 2-29LONG for DNET CH........................... 2-32

LONG for DNET FL ............................ 2-39LONG for DNET ID............................. 2-42LONG for DNET IS ............................. 2-44LONG for DNET LC............................ 2-47LONG for DNET LG............................ 2-50LONG for DNET MB........................... 2-52LONG for DNET NR ........................... 2-56LONG for DNET OP............................ 2-57LONG for DNET QD (DSA or USER) 2-70LONG for DNET QD (PROG)............. 2-69LONG for DNET SA............................ 2-77LONG for DNET SB............................ 2-79LONG for DNET SP ............................ 2-85LONG for DNET SR............................ 2-87LONG for DNET SS ............................ 2-90LONG for DNET TC............................ 2-97LONG for LCT (ISL) of DNET CT ..... 2-34LONG for LCT (PSI) of DNET CT...... 2-34LONG for LPL of DNET PL................ 2-63LONG for LSC of DNET SC ............... 2-81LONG for LSYS of DNET SY............. 2-93LONG for LTS of DNET TS .............. 2-102LONG for RCT of DNET CT............... 2-37LONG for RPL of DNET PL................ 2-66LONG for RSC of DNET SC ............... 2-83LONG for RSYS of DNET SY ............ 2-94SHORT for DNET AC.......................... 2-19SHORT for DNET AF .......................... 2-21SHORT for DNET AG.......................... 2-23SHORT for DNET CB.......................... 2-26SHORT for DNET CC.......................... 2-29SHORT for DNET CH.......................... 2-32SHORT for DNET FL .......................... 2-39SHORT for DNET ID........................... 2-42SHORT for DNET IS............................ 2-44SHORT for DNET LC .......................... 2-47SHORT for DNET LG.......................... 2-50SHORT for DNET MB......................... 2-52SHORT for DNET NR.......................... 2-56SHORT for DNET OP .......................... 2-57SHORT for DNET QD (DSA or USER)2-70SHORT for DNET QD (PROG) ........... 2-69SHORT for DNET SA .......................... 2-77SHORT for DNET SB .......................... 2-79SHORT for DNET SP........................... 2-85

Index

47 A2 94UC i-13

SHORT for DNET SR.......................... 2-87SHORT for DNET SS .......................... 2-90SHORT for DNET TC.......................... 2-97SHORT for LCT (ISL) of DNET CT ... 2-34SHORT for LCT (PSI) of DNET CT ... 2-34SHORT for LPL of DNET PL.............. 2-63SHORT for LSC of DNET SC ............. 2-81SHORT for LSYS of DNET SY........... 2-93SHORT for LTS of DNET TS ............ 2-102SHORT for RCT of DNET CT............. 2-37SHORT for RPL of DNET PL.............. 2-66SHORT for RSC of DNET SC ............. 2-83SHORT for RSYS of DNET SY .......... 2-94

RESTART_FCP_ADMIN command ...... 10-79retry parameter

SNMP commands................................. 5-49RFC1213 subfile ......................................... 5-7RFC1285 subfile ......................................... 5-7RIM param of MDTSVR .........................3-112RMBX param of STL.............................. 3-127RMLOAD param of MDNET CT ............. 3-79RMSG param of EDD ..............................2-117ROMSG param of EDD ...........................2-117RON param of SVTR.............................. 10-15ROUTE command..................................... 5-42RSTADM command................................ 10-79RSYS

param of DTSVR ................................2-111param of EDD .....................................2-116param of MDTSVR.............................3-112param of STL ..................................... 3-127param of STSVR ................................ 3-129param of TTSVR................................ 3-137

SSCAN_VCAM_TRACE command ........ 10-16SCEN

order in FCP7 scenario......................... 5-14syntax in scenario................................. 4-27

scenariodescription ............................................ 4-21description for Datanet ......................... 4-32description of LOAD for CNP 7 .......... 4-53description of LOAD for Datanet......... 4-50description of SYSGEN for CNP 7...... 4-37

FCP7 ....................................................... 5-9FECM administrative functions.............. 4-7FEP software release............................. 4-22file naming convention ......................... 4-29general rules.......................................... 4-23syntax.................................................... 4-24

SCENARIOparam of MDTSVR ............................ 3-112param of STSVR ................................ 3-129

SCNVTR command......................3-117, 10-16SEETRACE command .................10-46, 10-57SEETRACE_TPDU command ................ 10-55SEETRACETPDU command .................. 10-55SEND_ECHO_REQUEST command ..... 10-71SEND_ECHO_SENDING command...... 10-74SERVER

param of DBSVR................................ 10-31param of STTR ................................... 3-133param of TTTR................................... 3-140

SESSION param of SNR ......................... 3-123SET_SNMP_VALUE command................ 5-80SETDFLT param of EDD ........................ 2-116SEVERITY param of DBSVR................. 10-32SIDE

BNSE option........................................... 9-3param of STL...................................... 3-127

SMGR_COMMPORT subfile...................... 5-6SNDQ command...................................... 3-118SNMP

agent ....................................................... 5-2displaying next object ........................... 5-78displaying values5-65, 5-67, 5-69, 5-71, 5-73documentation commands ...........5-51, 5-75getting values........................................ 5-76manager .................................................. 5-3modifying values .................................. 5-80stop request command5-56, 5-57, 5-58, 5-59, 5-60, 5-61, 5-62, 5-63, 5-64

SNMP_AUTH subfile ................................. 5-6SNMP_COMM subfile ................................ 5-6SNMP_CONF subfile .................................. 5-6SNMP_MGR_MIB subfile .......................... 5-6SNMP_TRAP subfile................................... 5-6SNMPDOC command ............................... 5-75SNMPGET command ................................ 5-76


i-14 47 A2 94UC

SNMPNEXT command............................. 5-78SNMPSET command ................................ 5-80SNPA param of LNET RB......................... 3-41SNR command ........................................ 3-120software version number

CNS 7.......................................... 4-22, 4-69DNS............................................. 4-22, 4-69FCP7....................................... 5-6, 5-7, 5-11

specific error codes...................................... E-1standard basic network configuration..........D-1START param of EDD .............................2-116START_VCAM_TRACE Command ...... 10-14starting OCS ................................................ 5-3STATE

param of DNET.................................... 2-16param of DTSVR ................................2-111param of LNET ...................................... 3-3param of MDNET ................................ 3-66

STATISTIC_EVENT param of SNR....... 3-121STATISTICS param of SNR ................... 3-122STD_SCEN subfile ..................................... 5-5STL command ......................................... 3-125

BNSE test ........................................... 3-125LNA test ............................................. 3-126

Stop commands ......................................... 5-48STOP_GET_ROUTE command ............... 5-59STOP_SNMP_GET command.................. 5-62STOP_SNMP_GET_ARP command ........ 5-56STOP_SNMP_GET_CONNECT command5-

57STOP_SNMP_GET_NET command ........ 5-58STOP_SNMP_GET_UDP command ........ 5-60STOP_SNMP_NEXT command ............... 5-63STOP_SNMP_REQ command.................. 5-61STOP_SNMP_SET command................... 5-64stopping OCS .............................................. 5-4storage facility (DSA admin)..................... 4-68STRCTPDU command................. 10-55, 10-57STSVR command.................................... 3-128STTR command ...................................... 3-132SUBDOMAIN param of DBSVR ........... 10-32SUBTEST param of STL ........................ 3-126SUFFIX param of DBSVR...................... 10-32SURVEY

param of MDNET CH.......................... 3-76param of SNR..................................... 3-121

SV param for Datanet SYSGEN................ 4-34SVPAT2 param for Datanet SYSGEN....... 4-34SVTR command ...................................... 3-134SVTR Command ..................................... 10-14SY_STATE param of MDNET SA .......... 3-100SYS.DSABLIB

description ............................................ 4-12use by OCS ............................................. 5-5

SYS.DSACONF use by OCS ...................... 5-5SYS.DSADUMP use by OCS...................... 5-7SYS.DSASLIB

description ............................................ 4-18use by OCS ............................................. 5-7

SYS.DSATRC use by OCS.......................... 5-7SYS.DSATRCIDT use by OCS ................... 5-8SYS.DSATRCIDX use by OCS................... 5-8SYS.HUBG library .................................... 4-20SYSGEN

Datanet.................................................. 4-30FEP generation...................................... 4-30on CNP 7 .............................................. 4-36

SYSTEMparam of DNET .................................... 2-16param of DTL ..................................... 2-108param of LNET....................................... 3-4param of MDNET................................. 3-66param of MDTL.................................. 3-109param of STL...................................... 3-126param of TTL...................................... 3-136

system subfiles in IPS administration.......... 5-8SYSTEM1 param of MDNET FL.............. 3-85SYSTEM2 param of MDNET FL.............. 3-85

TTC objects

error codes ..............................................E-1TCP/IP administrative commands ............... 5-2teleload 4-74TERMINATE param of EDD .................. 2-116TEST command ....................................... 10-68TESTS param of SNR ............................. 3-123TF01 messages......................................... 6-162TF03 messages......................................... 6-162TF04 messages......................................... 6-163TF05 messages......................................... 6-163

Index

47 A2 94UC i-15

TF06 messages ........................................ 6-164TF07 messages ........................................ 6-165TF50 messages ........................................ 6-166TF51 messages ........................................ 6-167TF52 messages ........................................ 6-168TF53 messages ........................................ 6-168TF54 messages ........................................ 6-168TF55 messages ........................................ 6-168TF56 messages ........................................ 6-168TF57 messages ........................................ 6-169TF58 messages ........................................ 6-169TIME param of PRTTR............................3-115timeout parameter

SNMP commands................................. 5-50TIMER_1

RTS mod param of MDNET TS......... 3-106TIMER_2

RTS mod param of MDNET TS......... 3-106TNR command ........................................ 3-135TNS

arg for TYPE of STSVR .................... 3-129file trace.............................................. 10-22

TP01 messages ........................................ 6-170TP02 messages ........................................ 6-171TP03 messages ........................................ 6-172TP04 messages ........................................ 6-173TP05 messages ........................................ 6-173TP06 messages ........................................ 6-174TP52 messages ........................................ 6-175TP53 messages ........................................ 6-175TP54 messages ........................................ 6-176trace

FCP 7.................................................. 10-36levels of FCP 7 ................................... 10-39OCS.................................................... 10-28VCAM................................................ 10-13

TRACEparam of DBSVR ............................... 10-33param of EDD .....................................2-117param of MDTL ..................................3-110param of MDTSVR.............................3-112param of STL ..................................... 3-126param of STSVR ................................ 3-130param of STTR................................... 3-133param of TTTR................................... 3-140

TRACE command ........................ 10-41, 10-57

trace scannerexample of VCAM-DSA .................... 10-21example of VCAM-ISO...................... 10-19

TRACE_FILE param of DBSVR ............ 10-34TRACETPDU command ......................... 10-50TRANSPORT param of SNR .................. 3-124TRC_FILE param of SCNVTR ............... 10-16TRCTPDU command ...................10-50, 10-57TSLNCC subfile ..........................5-6, 5-7, 5-11TTL command ......................................... 3-136TTSVR command.................................... 3-137TTTR command....................................... 3-140TVTR command ...................................... 3-142TYPE

LCT param of DNET CT...................... 2-33LCT param of LNET CT ...................... 3-18LCT param of MDNET CT .................. 3-77LPL param of DNET PL....................... 2-62LPL param of LNET PL ....................... 3-35LPL param of MDNET PL ................... 3-90LSC param of DNET SC ...................... 2-80LSC param of LNET SC....................... 3-46LTS param of DNET TS..................... 2-102LTS param of LNET TS ....................... 3-59param of DNET .................................... 2-16param of DNET AC.............................. 2-18param of DNET AF .............................. 2-20param of DNET AG.............................. 2-22param of DNET CB.............................. 2-26param of DNET CC.............................. 2-28param of DNET CH.............................. 2-31param of DNET FL............................... 2-38param of DNET IS................................ 2-43param of DNET LC .............................. 2-46param of DNET NR.............................. 2-55param of DNET OP .............................. 2-57param of DNET PC .............................. 2-59param of DNET QD.............................. 2-68param of DNET SA .............................. 2-76param of DNET SB .............................. 2-78param of DNET SP............................... 2-84param of DNET SR .............................. 2-86param of DNET SS............................... 2-89param of DNET TC .............................. 2-96param of DTSVR................................ 2-110param of LNET....................................... 3-3


i-16 47 A2 94UC

param of LNET AC................................ 3-5param of LNET AF ................................ 3-7param of LNET AG................................ 3-9param of LNET CB.............................. 3-13param of LNET CC.............................. 3-14param of LNET CH.............................. 3-16param of LNET FL............................... 3-21param of LNET IS................................ 3-24param of LNET LC .............................. 3-26param of LNET NK.............................. 3-31param of LNET NR.............................. 3-33param of LNET OP .............................. 3-34param of LNET QD.............................. 3-39param of LNET RB.............................. 3-40param of LNET SA .............................. 3-42param of LNET SB .............................. 3-44param of LNET SP............................... 3-49param of LNET SR .............................. 3-50param of LNET SS............................... 3-52param of LNET TC .............................. 3-57param of MDNET ................................ 3-66param of MDNET AC .......................... 3-68param of MDNET AF .......................... 3-70param of MDNET AG.......................... 3-72param of MDNET CH.......................... 3-75param of MDNET FL........................... 3-81param of MDNET OP .......................... 3-88param of MDNET QD.......................... 3-93param of MDNET RB .......................... 3-98param of MDNET SA .......................... 3-99param of MDNET SB ........................ 3-101param of MDNET SR ........................ 3-103param of MDTSVR.............................3-112param of STSVR ................................ 3-129param of TTSVR................................ 3-137RCT param of DNET CT ..................... 2-36RCT param of LNET CT...................... 3-20RCT param of MDNET CT.................. 3-79RPL param of DNET PL ...................... 2-65RPL param of LNET PL ...................... 3-37RSC param of DNET SC ..................... 2-82RSC param of LNET SC...................... 3-48RTS param of DNET TS .................... 2-103RTS param of LNET TS....................... 3-61RTS param of MDNET TS................. 3-106

UUFT server trace ...................................... 10-29UNKNOWN_RPL param of MDTSVR .. 3-113unsolicited error codes .................................E-1unsolicited events......................................... 8-2unsolicited messages

composition ............................................ 8-1summary ................................................. 8-3

UPGRADE_FCP_CONFIG command...... 5-96UPGRADECF command........................... 5-96

VVALUES param of DBSVR .................... 10-33VCAM trace scanner ............................... 10-17VCAM-ISO trace

example............................................... 10-19first level display ................................ 10-18second level display............................ 10-18

VENUELCT param of DNET CT...................... 2-34LCT param of LNET CT ...................... 3-19LCT param of MDNET CT .................. 3-77LPL param of DNET PL....................... 2-63LPL param of LNET PL ....................... 3-36LPL param of MDNET PL ................... 3-90LSC param of DNET SC ...................... 2-80LSC param of LNET SC....................... 3-46LSYS param of DNET SY ................... 2-92LSYS param of LNET SY.................... 3-54LTS param of DNET TS..................... 2-102LTS param of LNET TS ....................... 3-60param of DNET MB ............................. 2-51param of LNET MB.............................. 3-29RCT param of DNET CT...................... 2-36RCT param of LNET CT...................... 3-20RCT param of MDNET CT.................. 3-79RPL param of DNET PL ...................... 2-65RPL param of LNET PL....................... 3-37RSC param of DNET SC...................... 2-82RSC param of LNET SC ...................... 3-48RSYS param of DNET SY ................... 2-94RSYS param of LNET SY.................... 3-55RTS param of DNET TS..................... 2-103RTS param of LNET TS ....................... 3-61

Index

47 A2 94UC i-17

RTS param of MDNET TS................. 3-106VERSION

param of MDTSVR.............................3-112param of NODE in scenario ................. 4-25param of STSVR ................................ 3-130syntax in scenario................................. 4-25

version of FCP7 software ...........................5-11

WWORKSPACE command (VCAM trace) 10-17

XXGATC command ..................................... 5-91XID command ......................................... 10-66


i-18 47 A2 94UC

Vos remarques sur ce document / Technical publications remarks form

Titre / Title : Network User's Guide

N° Référence / Reference No. : 47 A2 94UC Rev06 Date / Dated : February 2005

ERREURS DETECTEES / ERRORS IN PUBLICATION

AMELIORATIONS SUGGEREES / SUGGESTIONS FOR IMPROVEMENT TO PUBLICATION

Vos remarques et suggestions seront attentivement examinées. Si vous désirez une réponse écrite,veuillez indiquer ci-après votre adresse postale complète.Your comments will be promptly investigated by qualified personnel and action will be taken asrequired. If you require a written reply, furnish your complete mailing address below.

NOM / NAME : DATE :

SOCIETE / COMPANY :

ADRESSE / ADDRESS :

Remettez cet imprimé à un responsable Bull S.A. ou envoyez-le directement à :Please give this technical publications remarks form to your Bull S.A. representative or mail to:

Bull CEDOC357 Avenue PattonBP 2084549008 ANGERS Cedex 01FRANCE

user's guide -...

Documents