Communications_Control_Program_Ver_3_Ref_Man_60471400G_May81 Communications Control Program Ver 3 Ref Man 60471400G May81
User Manual: Pdf Communications_Control_Program_Ver_3_Ref_Man_60471400G_May81
Open the PDF directly: View PDF .
Page Count: 160
Download | ![]() |
Open PDF In Browser | View PDF |
60471400 CONTRPL DATA CORPORATION NETWORK PRODUCTS COMMUNICATIONS CONTROL PROGRAM VERSION 3 REFERENCE MANUAL CDC® COMPUTER SYSTEMS: 255X SERIES NETWORK PROCESSING UNIT 0gv&®*\ REVISION RECORD Revision Description A (11/10/76) Initial release under NOS lj level 438. B (04/28/78) C (12/01/78) ?!fXisi?? e?,!?CP i'lf Cycle 34 plus °Ptioi»al minitape corrective code: PSRs 755, 718A, 729, 757, 773, 784, 828, 834, 835. Revised to include corrective code release, cycles 35, 36, 37; PSRs 257, 275, 710, 726, Ion' l*Z\ ?oLth^,76^ 7?3' 779' 784' 792' 800' 801» 803» 804> 807 thru 810, 813, 818, 891 921 853 thrU 855' 858' 862' 865' 869' 87°' 8?2' 8?8 thrU 88i' 883' D (06/30/79) Revised to CCP 3.2 PSR level 497. This revision obsoletes all previous editions. E (05/22/80) Revised to reflect PSR level 518. F (10/09/80) Revised for CCP release level 3.3, PSR level 528. G (05/29/81) Revised for CCP release level 3.4, PSR level 541. Includes PRU interface with Binary Synchronous Communications TIP and 2780/3780 terminal support. This is a complete reprint. /•sSis ^f£$S. REVISION LETTERS I, 0, Q, AND X ARE NOT USED ©COPYRIGHT CONTROL DATA CORPORATION 1976, 1978, 1979, 1980, 1981 All Rights Reserved Printed in the United States of America Address comments concerning this manual to: CONTROL DATA CORPORATION Publications and Graphics Division 215 MOFFETT PARK DRIVE SUNNYVALE, CALIFORNIA 94086 <*=weS!V or use Comment Sheet in the back of this manual 60471400 G LIST OF EFFECTIVE PAGES New features, as well as changes, deletions, and additions to information in this manual are indicated by bars in the margins or by a dot near the page number if the entire page is affected. A bar by the page number indicates pagination rather than content has changed. Page Revision Front Cover Title Page i i iii/iv v vi vii viii 1-1 1-2 1-3 1-4 1-5 thru 1-20 2-1 thru 2-37 3-1 3-2 3-3 3-4 thru 3-7 4-1 A - l t h r u A-41 B-l B-2 B-3 B-4 B-5 B-6 B-7 B-8 B-9 B-10 B-ll B-12 C - l t h r u C-9 D - l t h r u D-3 E-l F-l G - l t h r u G-4 H - l t h r u H-3 Index-1 Index-2 Comment !Sheet Mailer Back Cover 60471400 G iii/iv y^^K <# PREFACE This manual is intended to provide overview information concerning the role of the CDC® Communications Control Program Version 3.4 (CCP) in network processing, and to describe the functions which CCP provides for the network. [ ] Square brackets enclose entities that are optional; if omission of any entity causes the use of a default entity, the default is underlined. { } Braces enclose entities from which one must be chosen. CONVENTIONS USED Throughout this manual, the following conventions are used in the presentation of statement formats, operator type-ins, and diagnostic messages: ALN Uppercase letters indicate words, acronyms, or mnemonics either required by the network software as input to it, or produced as output. aln Lowercase letters identify variables for which values are supplied by NAM or the terminal user, or by the network software as output. Ellipsis indicates that the omitted entities repeat the form and function of the entity last given. Unless otherwise specified, all references to numbers are to decimal values; all references to bytes are to 8-bit bytes; all references to characters are to 8-bit ASCII coded characters. RELATED MANUALS The manuals listed below contain additional information on both the hardware and software elements of the CONTROL DATA® 255x Series Computer Systems and the CCP and related software. The Software Publications Release History serves as a guide in determining which revision level of software documentation corresponds to the Programming Systems Report (PSR) level of installed site software. Publication Publication Number Host Manuals Network Products Communications Control Program Version 3 System Programmer's Reference Manual 60474500 Network Products Interactive Facility Version 1 Reference Manual 60455250 Network Products Network Access Methods Version 1 Reference Manual 60499500 Network Products Network Access Methods Version 1 Network Definition Language Reference Manual 60480000 Network Products Remote Batch Facility Version 1 Reference Manual 60499600 Network Products Stimulator Version 1 Reference Manual 60480500 Network Products Transaction Facility Version 1 Reference Manual 60455340 NOS Version 1 Operator's Guide 60435600 NOS Version 1 Reference Manual, Volume 1 of 2 60435400 NOS Version 1 Reference Manual, Volume 2 of 2 60445300 Software Publications Release History 60481000 Avx^S. 60471400 G V • Language Manuals CYBER Cross System Version 1 Build Utilities Reference Manual 60471200 yX^rtWf^f. CYBER Cross System Version 1 Macro Assembler Reference Manual 96836500 CYBER Cross System Version 1 Micro Assembler Reference Manual 96836400 CYBER Cross System Version 1 PASCAL Compiler Reference Manual 96836100 State Programming Language Reference Manual 60472200 Update Version 1 Reference Manual 60449900 NPU Manuals MSMP Diagnostic Reference Manual 96700000 Network Processing Unit (NPU) Hardware Reference Manual 60472800 Operational Diagnostic System (ODS) Version 2 Reference Manual 96768410 CDC manuals can be ordered from Control Data Corporation, Literature and Distribution Services, 308 North Dale Street, St. Paul, Minnesota 55103. This product is intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. • vi 60471400 G CONTENTS i. INTRODUCTION TO CCP AND NETWORK CONCEPTS 1-1 Network Concepts Communications Network Overview Computer Network Overview Computer Network Products Network Host Products Network Access Method Network Definition Network Supervision NAM Applications Programs Communications Network Products 255X Series NPU Communications Control Program CCP Coding Languages Message Movement in a Network Simplified Input Message Processing Simplified Output Message Processing CCP Role in Network Processing Multiplexing Operation Base System Software Block Interface Package (BIP) Host Interface Package Link Interface Package Terminal Interface Packages CCP Software Languages 255X Hardware Communications Processor Multiplex Subsystem Communications Console 2558-3 Channel Coupler Communications Line Adapters 2560 Series Synchronous Communications Line Adapters Sample Configurations Terminals Supported 1-1 1-1 1-1 1-2 1-2 1-2 1-3 1-4 1-4 1-6 1-6 1-7 1-7 1-7 1-7 1-8 1-9 1-10 1-10 1-11 1-11 1-12 1-13 1-15 1-17 1-17 1-18 1-19 1-19 1-19 2. OVERVIEW OF CCP FUNCTIONS 2-1 Multiplexing, Switching and Data Conversion Interfaces Transmission Media Initialization Base System Software System Monitor Buffer Handling Worklist Services Queuing Mechanisms Direct Program Calls (Switching Services) Interrupt Handling Timing Services Globals Control Block Services Directory Maintenance Standard Subroutines Multiplex Subsystem Operation Input Multiplexing Output Multiplexing Trunk Multiplexing Demultiplexing Block Interface Package (BIP) Block Routing Service Module Interactive Virtual Terminal Commands 2-1 2-3 2-3 2-4 2-5 2-5 2-5 2-5 2-6 2-6 2-6 2-6 2-7 2-7 2-7 2-7 2-7 2-7 2-7 2-7 2-8 2-8 2-9 2-9 2-9 1-19 1-19 1-19 Batch Terminal PRU Commands Routing Block Acknowledgment and Data Flow Control Processing Special Characters and IVT Commands Processing Autoinput Common TIP Subroutines Failure and Recovery Host Failure NPU Failure Logical Link Failure Trunk Failure Line Failure Terminal Failure Diagnostics Interface Packages Hardware Used by Interface Packages Software Used by Interface Packages Host Interface Package Micromemory Start and Stop Commands Control Word Transfers Status Word Transfers Data Transfers Link Interface Package Loading/Dumping of Remote NPU Trunk Transmission Priorities and Regulation Transmission Assurance Terminal Interface Packages Async TIP Input Processing Output Processing User Interface MODE 4 TIP Mode 4 Autorecognition Mode 4 Data Handling Host Interface IVT Interface Card Reader Interface Printer Interface Binary Synchronous Communications (BSC) TIP Terminal Device Selection Batch Input Characteristics of 2780 and 3780 Terminals Batch Output Characteristics of 2780 and 3780 Terminals Interactive Input and Output Mode Autorecognition IVT Commands HASP Multileaving TIP Summary of HASP Protocol Protocol Operation Control Blocks Data Blocks Error Handling Data Conversion HASP Input Batch Data HASP Printer Output Data HASP Card Punch Output Data HASP Plotter Output Data HASP Error Recovery Procedures HASP Terminal Start-up and Termination X.25 TIP/PAD SubTIP X.25 Input Sequence X.25 Output Sequence Supported Terminal Classes 2-9 2-9 2-9 2-9 2-9 2-9 2-10 2-10 2-10 2-10 2-10 2-10 2-10 2-10 2-10 2-11 2-11 2-11 2-12 2-12 2-18 2-18 2-18 2-19 2-19 2-19 2-19 2-20 2-20 2-21 2-21 2-21 2-22 2-22 2-22 2-22 2-23 2-24 2-24 2-24 2-25 2-25 2-26 2-27 2-27 2-27 2-27 2-28 2-28 2-28 2-28 2-28 2-28 2-29 2-30 2-30 2-30 2-30 2-30 2-31 2-31 2-32 /#^v 60471400 G vu • Transparent Mode Autoinput Parity Typeahead Input from the Terminal Block Mode Backspacing from the Terminal Cancel Input Break Key Processing Formatting on Output IVT Commands Build-Time Selections Message Priorities and Input Regulation Message Priorities Input Regulation Host Interface Regulation Trunk Interface Regulation Terminal Interface Regulation Logical Link Regulation Upline Data Downline Data 2-32 2-32 2-32 2-32 2-32 2-32 2-33 2-33 2-33 2-33 2-33 2-33 2-33 2-35 2-35 2-35 2-35 2-36 2-36 2-37 FG I 1-1 1-2 1-3 1-4 1-5 1-6 1-7 1-8 2-1 2-2 2-3 2-4 2-5 2-6 3. INITIALIZING THE NPU 3-1 2-7 Load/Dump Phases for Local NPUs Local NPU Loading Load File Format Local NPU Dumping, 2551 NPU Remote NPU Loading Remote NPU Dumping Configuring NPUs 3-1 3-1 3-1 3-2 3-2 3-6 3-7 3-1 3-2 3-3 4. FAILURE, RECOVERY, AND DIAGNOSTICS 4-1 APPENDIXES A Coded Character Data Input, Output, and Central Memory Representation B Diagnostics C Glossary D CCP Mnemonics E Sample Main Memory Map for NPU F CCP Naming Conventions G Terminal Commands and Messages H NPU Operating Instructions A-l B-l C-l D-l E-l F-l G-l H-l /^^v INI CYBER Network, Overview of Functions 1-2 Network Host Products 1-3 Network Supervisor Functions 1-5 Communications Supervisor Functions 1-6 Simplified Input Message Processing 1-8 Simplified Output Message Processing 1-9 CCP Software Levels l-n Sample NPU/Peripheral Hardware C o n fi g u r a t i o n s 1-20 Simplified NPU Buffered Transfers 2-1 Base Elements of the Multiplex Subsystem 2-8 Functions of a LIP 2 - 11 Functions of a TIP (not X.25 TIP) 2-12 Comparison of TIP/LIP and X.25 TIP Functions 2-12 Sample Logical Link Connections (Shown for Local and Remote NPUs) 2-37 Buffer Availability Threshold Levels for Regulation 2-37 Load File Format 3-3 Format of 2551 Dump 3-4 Format of Words in Dumps 3-4 TAB 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10 2-11 3-1 Buffer Assignment/Release in NPU 2-2 Interface/Protocol Relationships 2-3 Hardware Used by Interface Packages 2-13 Interface Package Software Characteristics 2-14 Mode 4 Components 2-21 Mode 4 Te r m i n o l o g y 2-21 X.25/PAD TIP and PDN Transfer Characteristics 2-31 X.25/PAD SubTIP Terminal Classes 2-32 Parity Actions 2-32 CCITT PAD Parameters and Recommended Settings 2-34 Regulation 2-36 Load/Dump Phases 3-1 /£^!^V • viii 60471400 G INTRODUCTION TO CCP AND NETWORK CONCEPTS The Communications Control Program (CCP) provides the software necessary to process data (messages) through the network communications portion of a Control Data Net work. As will be described later in greater detail, the network communications function allows an applications program in the main computer (a CYBER 70/170, called the host computer in a network) to process data as if the program were attached directly to a virtual terminal connected directly to a CYBER port. Since virtual terminals can be of only two types, interactive or batch, the host processing becomes essentially independent of terminal type. Minimizing terminal type dependency, as well as removing many of the terminal switching operations from the host, frees the CYBER computer to process data efficiently in the manner in which it was designed: as a high-speed, highpowered processor. As a result of this division of labor, the host can accommodate many more terminals, terminal types, and applications programs. Naturally, the host also processes applications programs more rapidly and with greater flexibility since it is not burdened with I/O functions that are better performed elsewhere. The network communications function, thus removed from the CYBER computer, is made resident in the Network Processing Unit (NPU). The NPU is a minicomputer system resident in a 255x Host Communications Processor and its associated multiplexing and coupling hardware. The types of operations performed by the NPU are: • multiplexing data to/from the numerous terminals • demultiplexing data and storing it in buffers for buffered high-speed transfers to/from the host computer • converting the numerous terminal protocols into either an interactive or a batch virtual terminal protocol; the converse operation is performed for output operations to terminals • regulation of the volume of traffic handled Communications network processing not only relieves the host computer of most I/O overhead; it also relieves applications programmers of the need to concern themselves with terminal characteristics other than the characteristics of the virtual terminals. Since it is necessary to know the basic concepts of network message processing to understand the structure of the CCP software, this introduction includes a description of the network and the distribution of network tasks between the host and the NPUs. The CCP is itself functionally divided into three software groups: 60471400 G • base system software which includes the NPU operating system: monitor, timing and interrupt services, initialization, space allocation, and other general service routines; the multiplexing sub system is also a part of the base system software • block interface package (BIP) software: block formation (PRU or IVT), routing, control and status processing, hardware configuration control • other interface packages: the host interface, the link interface to a remote NPU (if one exists in the network), and the standard terminal interfaces (ASYNC, BSC, HASP, Mode 4, X.25 with PAD subTIP) NETWORK CONCEPTS Network products provide effective data-processing services to terminal users. These services consist primarily of applications programs written to perform specific functions. The applications programs are executed in the host computer. Network products are designed to achieve functional separa tion between the host system services to terminal users, and the communications equipment software required to inter connect the host computer and its terminals. This has led to the concept of viewing the complete network as consisting of two separate networks, a communications network and a computer network, with well-defined hardware and software boundaries between them as shown in figure 1-1. COMMUNICATIONS NETWORK OVERVIEW The communications network includes a set of Network Processing Units (NPUs) interconnected by communications lines. Its purpose is to transport blocks of data between the host computer and terminals. To perform this function, the NPU presents an interface (represented by a set of proto cols) to the host computer on the one side and to each terminal on the other side. Messages are carried in buffers of data and are transferred to/from the host at channel speeds. At the terminal interface, messages are transferred one character at a time at communications line speeds. The host interface is insensitive to the detailed topology of the communications network, so that the network may be either a simple network with a single local NPU or a network with one local NPU and one or more remote NPUs. COMPUTER NETWORK OVERVIEW The computer network includes host computers and termi nals, the host software associated with network communica tions, and the applications programs providing services to 1-1 COMPUTER NETWORK y HOST COMMUNICATIONS NETWORK LOCAL PROCESSOR NODE I "N TERMINALS USERS Figure 1-1. CYBER Network, Overview of Functions the terminal users. The software in each host computer meets the interface presented by the communications network on the one side, and in turn presents a standard interface to applications programs written to use the network on the other side. In this way, the communications network is isolated from the applications programs so that it may be changed without disturbing the applications-level software. COMPUTER NETWORK PRODUCTS The computer network uses the communications network along with host computer software and possibly terminal software to interface between terminal users and appli cations programs in a host computer system. The major network host product is the Network Access Method (NAM). Other network host products which execute as applications to NAM provide standard support of time sharing, remote batch handling, and transaction processing for the terminal user. The remaining network host products execute as network applications programs in the host; all use NAM to commu nicate with the communications network and with each other. The network and communications supervisors are responsible for the network coordination and control-oriented activities of the CYBER host computer. Standard NAM applications programs are provided to support various user applications environments such as timesharing, remote batch and transaction processing. User-provided applications may be added to meet special requirements. Network Access Method The Network Access Method (NAM) provides a generalized method for CYBER applications programs to access the communications network. Figure 1-2 illustrates this relationship. NETWORK HOST PRODUCTS The CYBER Network Operating System (NOS) provides the operational environment and control for the computer network software. The Network Access Method (NAM) provides a standard interface between the communications network and the applications programs executing in the host. 1-2 NAM provides a centralized queuing mechanism for accessing the communications network and a subroutine package that resides in each network applications program's field length. This subroutine package allows the appli cations to interface to NAM with CALL/ENTER-type procedure statements. 60471400 B HOST NETWORK OPERATING SYSTEM NS* • UA • UA APPLICATIONS CS* RBF* IAF« TVF» TAF» MCS* NAM* •STANDARD NETWORK APPLICATIONS NS CS RBF IAF TAF TVF UA NAM MCS NPU NETWORK SUPERVISOR COMMUNICATIONS SUPERVISOR REMOTE BATCH FACILITY INTERACTIVE FACILITY TRANSACTION FACILITY TERMINAL VERIFICATION FACILITY USER APPLICATION PROGRAM NETWORK ACCESS METHOD MESSAGE CONTROL SYSTEM Figure 1-2. Network Host Products Procedure statements are provided so that the applications program can connect to and disconnect from NAM, and can perform functions for applications programs similar to the LOGIN and LOGOUT procedures provided for users at terminals. They allow the installation to control the access to the communications network for programs executing in the host computer. Procedure statements also control the data exchange between the applications program and NAM buffers. Each applications program may have a number of logical connections. Each logical connection is associated with a single terminal or with another applications program. For each logical connection, NAM maintains a set of control tables and buffers. These allow NAM to queue data between the connected terminal and the associated applications program. NAM itself actually performs the physical I/O with the communications network. This use of supervisory messages between NAM and the applications program obviates the necessity for a defined table structure in the applications program's field length. NAM allows the applications program to use the table structure that is most efficient for it. Additionally, NAM does not limit the kind of buffering used by the applications program. The applications program may provide a buffer for each logical connection; alternatively, it may perform all its I/O from a single buffer. This allows the applications programmer maximum flexibility in the design of his program. NAM is described in detail in the NAM Reference Manual. As various events occur in the network, supervisory mes sages are passed to the applications program. They may, for example, inform the applications program of a new logical connection for a terminal which desires service from it, or of the fact that some failure has occurred. In the same way, the applications program uses supervisory messages to communicate with NAM. For example, an applications program may wish to disassociate itself from some terminal with whch it has a logical connection. The CYBER 170 Network Products define the complete network: 60471400 G Network Definition • The communications network is defined in terms of hosts and nodes and the physical/logical links between them. The computer network is defined in terms of applications programs, lines and terminals. 1-3 Network definition is provided by a language called the network definition language (NDL) which consists of a series of statements that describe the network. These statements generate a network configuration file (NCF), a local configuration file (LCF) and a printed output. NCF and LCF are used by the network host products in establishing, initiating, operating and controlling the network. The printed output provides documentation of the network configuration. NDL is described in detail in the NDL Reference Manual. Network Supervision The following paragraphs describe the network supervisor and the communications supervisor. NETWORK SUPERVISOR The network supervisor (NS) coordinates the activities of the various network processing units (NPUs) in the communi cations network. The network supervisor functions are as follows (see figure 1-3): • NS is responsible for loading software into the NPUs. • NS superimposes a logical network structure on the physical structure of the communications network. Logical links are established between the host and each NPU with which it is allowed to communicate. Note, however, that the host communicates with remote NPUs only through the local NPU. This minimizes the number of host programs that are aware of the physical structure of the network. The host can treat the entire communications network as a set of front-end NPUs; only NS tracks the actual physical topology of the network. By this means, the functions of the computer network and the communications network are effectively separated. • NS also receives reports from the NPUs on the status of the network. The supervisor takes corrective action as required. NS operates from a data base established by the individual responsible for managing the communications network, the network operator. This person prepares two files for use by NS. One contains copies of the software for each NPU in the network. The second contains a description of the configuration of the network. This latter file is prepared using network definition language. NS also allows the network operator (NOP) to control and to take the status of the communications network, either from a terminal in the network or from the CYBER 170 network operator's console. NS is described in detail in the NOS Operator's Guide. configuration table created by the NDL contains terminal information which allows CS to establish the physical configuration and characteristics of the terminals for which its host is responsible. CS also allows the local operator to control and to take the status of his portion of the computer network, either from a terminal in the network or from the LOP's console. The primary function of CS is to isolate the applications programs from the physical configuration of the terminals in the network. As applications programs make themselves known to NAM and as terminals connect to the network, CS establishes logical connections between terminal and pro gram as shown in figure 1-4. Applications programs communicate with terminals using simple connection numbers irrespective of the location of the terminals in the network. Logical connections may also exist between different applications programs. The network definition language (NDL) allows various options on the establishment of logical connections. • A terminal may be automatically connected to a given application. • The user at the terminal may be allowed to select the application he requires. • The user may be required to log-in before he is allowed to access the host computer. CS use is described in detail in the NOS Operator's Guide. NAM Applications Programs NAM applications programs provide users with communi cations access to host-system resources that satisfy a variety of processing needs. REMOTE BATCH FACILITY The remote batch facility (RBF) provides the capability to transfer data between files on a CYBER 170 host-computer and batch peripherals on terminals in the network. RBF interfaces to the Network Access Method (NAM) in order to communicate with its terminals. RBF is described in detail in the RBF Reference Manual. INTERACTIVE FACILITY The interactive facility (IAF) provides the terminal user with a range of timesharing capabilities. The facility provides the illusion to the user that he is the only user of the system. IAF also maintains control of files created by the user. Files are presumed private to the user who created them but can be declared to be common so other users may access them. Programs may be debugged interactively by use of IAF. The IAF Reference Manual gives a detailed description of IAF capabilities. COMMUNICATIONS SUPERVISOR The communications supervisor (CS) coordinates network-oriented activities of the host computer. the CS operates from a data base established by the individual responsible for managing the host's use of the communi cations network, the local operator (LOP). The local 1-4 TRANSACTION FACILITY The transaction facility (TAF) enables the terminal user to request a host system to perform a series of pre-defined tasks, such as checking a customer's credit and recording a sale, or making a reservation, or recording a deposit/with drawal/loan payment at a bank. When a transaction has 60471400 B / CCP s/w I NETWORK OPERATOR r NDL COMMUNICATIONS NETWORK NS - NETWORK SUPERVISOR NDL - NETWORK DEFINITION LANGUAGE Figure 1-3. Network Supervisor Functions been processed, information (such as status, acknowledg ment, or verification) is returned to the originator. Each subscriber has a private data base. The subsystem can contain a specialized data manager for use by the tasks or the total extended data base management system can be used. TAF is described in detail in the TAF Reference Manual. TERMINAL VERIFICATION FACILITY The terminal verification facility (TVF) provides the user with an active confidence test (diagnostic) to verify the correct operation of his terminal. This is accomplished by sending data to or from the terminal in either a user-defined or TVF-selected format. Three tests are provided: • A loopback test sends data entered by the user back to the terminal. * NETWORK VALIDATION FACILITY • A line test sends one full line of data to the user. The network validation facility (NVF) protects user applica tions, and such applications as RBF, IAF, TVF, or TAF, against unauthorized access by terminal users. NVF validates each user before granting access to the computer system or any of its resources. • A screen test sends one full screen of data to the user. TVF is described in detail in the NAM Reference Manual. MESSAGE CONTROL SYSTEM Validation is based on access permissions defined in a protected file. Statistical information and thresholds for illegal conditions pertaining to log-on and application requests are maintained, logged and reported for accounting and security (that is, penetration-detection) purposes. 60471400 G The message control system (MCS) allows the user to queue, route, and journal messages between COBOL programs and terminals. By using the Application Definition Language, an MCS application can be tailored to fit a user's needs. The terminal can be switched from MCS to NVF. 1-5 /r^S, y^sv NOL-NETWORK DEFINITION LANGUAGE CS -COMMUNICATIONS SUPERVISOR RBF-REMOTE BATCH FACILITY IAF - INTERACTIVE FACILITY Figure 1-4. Communications Supervisor Functions COMMUNICATIONS NETWORK PRODUCTS 255x SERIES NPU The communications network allows terminals to access the host computer via communications lines. The network products used to implement this access are: The hardware portion of the communications network consists of: • 255x series Network Processing Unit (NPU) hard ware which provides for physical connection between host and terminal. In CCP two varia tions are possible: local NPUs or local and remote NPUs. • Communications Control Program (CCP) which is the software system in the 255x series NPU I • Cross System software which supports the installation, maintenance and modification of CCP via the CYBER host computer. This is a batch-oriented compiler/run-time system. • A microprogrammable, 16-bit processor (mini computer). Main memory contains all the space necessary to execute programs and to provide buffers for network data. External (mass) memory is not used. • A CYBER channel coupler which provides the high speed interface between the minicomputer and the host's Peripheral Processing Unit (PPU). Transfers over this channel are buffered. Channel buffers within the NPU provide enough space to handle an entire message transfer in a single operation. ^&S\ 1-6 60471400 G NOTE The host/NPU coupler interface passes data upline to the host in one of three formats: interactive virtual terminal for interactive devices, physical record unit (PRU) for batch devices, or transparent. Blocks are received from the host in the same formats. J^s A multiplex subsystem consisting of: A Multiplex Loop Interface Adapter (MLIA) which controls the input and output multiplex loops Individual loop multiplexers (LMs) which attach to the input and output multiplex loop on one side and to individual Communications Line Adapters (CLAs) on the other. The CLAs provide line-by-line interface compatibility with the modems attached to terminals or to remote NPUs. NOTE yams At the interface of the NPU to the lines, data passes to/from the terminals in a format (protocol) compatible to the ter minal. A remote NPU is treated as a special type of terminal. Link interface package (LIP) supports the local/remote NPU transfers. The remote NPU collects data from its terminals and formats it prior to passing the data upline to a local NPU. This interface uses the CDC Communications Procedure (CDCCP) protocol. Terminal interface packages (TIPs). Five standard TIPs handle transfers for terminals using interactive modes (ASYNC or X25 with PAD subTIP), or both batch and interactive modes (Mode 4, BSC, and HASP). CCP Coding Languages For ease in programming the NPU, the programmer can code his source language routines in PASCAL, an ALGOL-like language. The Cross system programs are run on the host, and the principal output is an NPU machine language load file which resides in host mass storage. This load file contains all of the CCP modules in NPU image format (including overlays). This file is used to load the NPU (remote or local) following an NPU or host failure. The Cross system is described at the end of this section. A few common programs are coded in the macro assembler language. A.special subset of this language, called state programs, uses a set of specially-defined macrocommands to process messages on the microprocessing level. Each TIP contains message conversion programs written in the state programming language. All programs, regardless of source language, are included in the host's load file. COMMUNICATIONS CONTROL PROGRAM The three major parts of the Communications Control Program (CCP) are: • The base system which includes the OPS-monitor, interrupt handlers, multiplex subsystem, software and firmware, timing services, initialization (the NPU is downline-loaded from the host), space allocation, program-to-program calls and data transfers, standard subroutines, text processing, and error checking. • Block interface package (BIP) software, which provides block formation (PRU or IVT), routing, control and status processing, and hardware configuration controL NOTE Inline diagnostics are provided as part of CCP. If the customer elects to purchase a CDC maintenance contract, on-line diagnostics are provided. Also provided in the maintenance program are some hostbased applications programs which simpl ify the use of inline diagnostics. Interface software. Three standard types of interfaces are provided: Host interface package (HIP) supports the high-speed, buffered channel interface to the host computer. Data is assumed to be in IVT or PRU format. 60471400 G Message Movement in a Network The basic procedures for upline and downline message movement are discussed next. Note that the procedures given are highly summarized. Acknowledgment procedures are also highly summarized. It is assumed that terminals are connected through a single NPU. Simplified Input Message Processing Figure 1-5 shows the movement of a message from a terminal to the host applications program. Solid lines indicate message (and acknowledgment message) pathways, dashed lines indicate principal control functions. The major features of the upline message processing are: • Some synchronous terminals are polled to find if the terminal has data ready to send; an asynchronous terminal sends data when it is ready • Setting up of multiplex subsystem and buffers when terminal indicates it has data to send upline • Collecting all data from this (and all other active terminals) in a circular input buffer (CIB) • Demultiplexing data and converting it to a host compatible format (IVT or PRU). Demultiplexed data is collected in a block which uses one or more chained buffers and is called a line-related input buffer. If code conversion is necessary (such as EBCDIC to ASCII for interactive data or EBCDIC to display code for batch data), this is also accomplished. • When input buffer is full (that is, the message is complete), message is validated. 1-7 [terminal I—t* MUX CONTROL. MUX LOOP. AND MLIA INPUT DATA PROCESSOR HOP) © i BLOCK INTER FACE PROCESSOR (BIP) I © © © SETS UP INPUT TRANSFER RAW INPUT MESSAGE MULTIPLEXED INPUT MESSAGE IS PLACED IN CIRCULAR INPUT BUFFER (7) PROCESSES CHARACTERS v-x ANO DETECTS END OF MESSAGE. DEMUX AND CONVERT TO VIRTUAL TERMINAL OR PRU FORMAT; TRANSLATES TERMINAL CODE IF NECESSARY LINE-ORIENTED INPUT BUFFER (MAY BE CHAINED BLOCKS) (&) VALIDATES MESSAGE AND PASSES IT TO BIP © SETS UP TRANSFER TO PPU. (a) INPUT STATUS BUFFERS, ^-^ RELEASES WHEN COUPLER DETERMINES ROUTING WITH HELP OF DIRECTORY. REQUEUES MESSAGE FOR COUPLER. CONTROL TO HIP SHOWS THAT TRANSMISSION IS COMPLETE Figure 1-5. Simplified Input Message Processing Message routing is determined and message is queued to the host coupler. Statistics (a type of status information that includes both successful and failure information) are generated for the transfer. The coupler transmits the message to the host PPU and unqueues the message from the coupler. The host receives the message and connects it to the applications program. The NPU finishes input processing by releasing the message buffer. Simplified Output Message Processing Figure 1-6 shows the movement of a message from a host application program to a terminal (downline messages). Conventions for solid and dashed lines are the same as for the input message diagram. The major features of the downline message processing are: • Interrupt from the host indicates a buffer of data (message or file) is ready for transmission. The data is in PRU, IVT, or transparent format at this point. • If the NPU is not already saturated with other, higher priority tasks (note that output takes prece dence over input), the host interface package (HIP) sets up the coupler to receive the message and assigns a buffer (or chained buffers) of space to be used as an output buffer for the block. The message is sent by a buffered transfer from the PPU through the coupler to the assigned buffers. The coupler causes the transmission complete interrupt to the HIP when all of the message has been received. The text processor converts the message from IVT or PRU format to the destination terminal's format (transmission blocks). The transmission block is queued to a terminal control block where the terminal interface package (TIP) detects that data is available. • If the terminal is able to output data, the TIP directs the multiplexer subsystem to output the message. • When the terminal has detected the end of mes sage, it sends an acknowledgment message. Upon receiving acknowledgment that the message was received, the NPU terminates the output operation by sending an acknowledgment to the host and by releasing the output buffers. Most of the operations mentioned in the input are described in more detail later in this section. Since most of these operations are CCP functions, they are also discussed in general terms, by individual functions, in section 2. >«!tasjx 1-8 60471400 G BIP. TIP AND TEXT PROCESSOR /^^v ©! ®; ©;© © MUX CONTROL. MUX LOOP, AND MLIA OUTPUT BUFFERS ©/'©I ©' ®[©T I L _j © SET BOTH PPU ANO HIP COUPLER TO RECEIVE MESSAGE (Ia) SETS UPMESSAGE 8UFFERS FOR N-' OUTPUT © COUPLER SENDS INTERRUPT WHEN ALL OF MESSAGE IS RECEIVED (2A)ANOTIFIES BIP BY V^ WORKLIST f2Cj THAT BIP NOTIFIES TIP V"^ THERE IS THAT MESSAGE IS IN BUFFER (2B)0UEUES MESSAGE ^^ TO TERMINAL USING TCB A MESSAGE IN THE QUEUE (IF NECESSARY) (7) MESSAGE CHECKS TCB FOR V-' READY TO TRANSMIT CONVERTS TO PROPER FORMAT FOR THIS TERMINAL DIRECTS MESSAGE TRANSMISSION WHEN TERMINAL RESPONDS IT IS READY WHEN ACKNOWLEDGE MESSAGE IS RECEIVED. THIS INFORMATION IS PASSED UPLINE TO HOST; BUFFER IS RELEASED Figure 1-6. Simplified Output Message Processing CCP Role in Network Processing The CCP must provide the following functions for the network system. • Host interface compatibility: Data is transferred (upline and downline) in high-speed buffered transfers. The data is in PRU, IVT, or transparent format. The host interface package (HIP) monitors this operation. • Transfers may be regulated; that is, if the NPU is busy with output (downline) processing or has many upline messages already started, new upline trans fers may be refused. The rejected transfers will be made at a later time when the NPU is less busy. • NPU must pass an acknowledgment message to the host after a terminal has received a downline message. • NPU must prepare the coupler for upline and downline transfers. & • Conversion: Non-transparent upline messages are converted from terminal format to IVT format (if the message originated from an interactive terminal) or to PRU format (if the message originated from a batch device). Non-transparent downline messages are converted to the format of the destination terminal. The TIPs contain transform tables for code conversion and some format conversion. The BIP is responsible for some of the format conversion between terminal and IVT or PRU format. 60471400 G The CCP must supply memory space in the form of chained input and output buffers. Supervision of the multiplex subsystem. On output, supervision consists of preparing the multiplex subsystem to output data from the output buffer. Actual transmission is done on demand from the communications line adapter (CLA). On input this consists of preparing the CLA to receive data. After the data has been placed on the input loop, the multiplex loop interface adapter (MLIA) trans fers the data to the circular input buffer (CIB). From the CIB, data must be individually demulti plexed to the line-oriented input buffers. If this system has a remote NPU as well as a local NPU, the remote NPU must have a link interface package (LIP) which collects the data and the local NPU must have a LIP for receiving the data. In the remote unit (for upline messages) the data is collected and converted by the appropriate TIP into PRU or IVT format (transparent data is I permitted). The completed message is then divided | into subblocks of a size suitable for transmitting over the trunk. In the local NPU the subblocks are reconstituted into a message buffer. This data—after validation—is passed to the HIP to be transferred to the host. The output operation is the converse of the above I procedure: that is, blocks of PRU, IVT, or I transparent data are broken into subblocks (if | necessary), and multiplexed prior to transferring the message over the trunk. Conversion to terminal format takes place in the remote NPU. 1-9 Physical placement of the CLA in the NPU cabinet determines the frequency with which the line has access to the multiplex loop. CLAs for lines assigned to trunks are placed in the first slot (or slots) so that these lines have first chance to use the multiplex loop. Terminal interface packages (TIPs) are responsible for setting up the messages so that the terminal protocols for starting, stopping, acknowledging, and message formatting are satisfied. The TIP also converts data from host codes (ASCII for IVT; ASCII or display code for PRU) to the terminal's internal code, if necessary. Multiplexing Operation The multiplex subsystem has two major functions, both of them hardware related: • Physical line characteristics vary for the different types of lines. To relieve the TIPs of having to process each line type according to that line's special physical characteristics, the multiplex sub system handles the characteristics by translating logical line commands/status into physical line command/status. This makes most physical line characteristics transparent to the TIP. • The high-speed host works most efficiently if given a full block of data to process. A terminal, on the other hand, is often low-speed, and data is trans ferred to/from the terminal one character at a time. The multiplex subsystem interfaces the high speed characteristics of the host/NPU with the "low-speed characteristics of the lines/terminals. The multiplex interface to the TIPs is described in the System Programmer's Reference Manual. INPUT MULTIPLEXING Each line has a communciations line adapter (CLA). The CLA for each active line is sampled in sequence. If a character is ready, it is placed on the input multiplex loop together with information identifying the source (line) and, in some cases, control information. All input multiplex loop data is routed to a circular input buffer (CIB). The demultiplexing operation picks data from this buffer, recon stitutes the messages in data buffers, and passes these buffers to the appropriate processor for this terminal (line). TRUNK MULTIPLEXING If a remote NPU is included in the network, transmissions between the local NPU and the remote NPU take place over a trunk. A trunk is a communications line. In the local NPU, a link interface package (LIP) sets up the output buffer. In the remote NPU, the downline messages are treated similarly to upline messages in a local NPU; that is, the message goes through the CIB and is then demultiplexed for the TIP. After the TIP converts the code to terminal format, the message is treated as an output message in a local NPU; that is, the message is transmitted through the multiplex subsystem. Input messages (upline traffic) are reformatted from terminal to IVT or PRU format as in a local NPU, but are then sent by the LIP through the remote NPU's multiplex subsystem, received by the local NPU's multiplex subsystem, and reconstructed into complete messages in the local NPU by that NPU's LIP. DEMULTIPLEXING The multiplex subsystem is responsible for picking data from the CIB as well as putting it into that buffer. When the message reception starts, the multiplex subsystem firmware reserves a data buffer for the message. The data words for that line are picked from the CIB and are packed into the reserved buffer. Control and tag information is discarded. If a buffer is filled before the message is complete, another buffer is assigned and is chained to the first. When the end of text is detected, the TIP which is appropriate for the terminal type is called to continue the processing. The demultiplexing of a downline transfer is a terminal function; that is, the message is reconstituted in a buffer for the screen, printer, or other output device. Base System Software The base system software, which includes the multiplex subsystem, is a basic, relatively invariant, set of CCP programs. As figure 1-7 shows, CCP software belongs to one of three levels: • base system software OUTPUT MULTIPLEXING • network communications software After the NPU has received a full message from the host and the appropriate terminal interface package (TIP) has converted the code to real terminal format, the multiplex subsystem can output the message. The multiplex subsystem picks the characters from the line's output message buffer in response to an output data demand (ODD) generated by the CLA. The ODD signal is the CLA's indication that it is ready to transmit another character. The outgoing characters are placed on the output multiplex loop, along with such control characters as are needed and an address that will be recognized by the CLA connected to that terminal. The CLA for the line picks the data from the output loop via the loop multiplexer. When the contents of the entire output buffer for the line have been transmitted successfully, the message buffers are released. Many output data buffers can be serviced at the same time. • interface packages (TIPs, LIP, HIP) 1-10 A ^ S The primary functions supplied by the base system are: • basic operating system functions such as interrupt handling, calling program (queuing requests), allo cating space (buffers) to requesting programs, handling the passing of parameters from the calling to the called program (worklist processing), timing services, common areas, and control block services • some initialization processing • multiplex subsystem including the command driver which interfaces between the multiplex subsystem (software and hardware) and the TIPs or LIP 60471400 G jiSSS. INTERFACE PACKAGES (APPLICATIONS) • • • • 1 1 Host Interface Package (HIP) Block Interface Package (BIP) Link Interface Package (LIP) Terminal Interface Packages (TIPs): • Mode 4 TIP • Async TIP • HASP TIP • X.25 TIP with PAD subTIP 1 • BSC TIP • User Generated TIPs NETWORK COMMUNICATIONS SOFTWARE • • • • • Routing Service message handling Virtual terminal transformation Diagnostics Common TIP subroutines BASE SYSTEM • • • • • • Conversion to and from IVT or PRU format is done by the BIP and the TIPs. By this means, host applications need expect only three data formats: IVT from any interactive terminal; PRU from any batch device, or transparent data from any terminal so long as either the terminal or the application has specified that the next transmission will be in transparent format. An option allows data to be passed to/from the host applications program in terminal format. (This is called transparent mode.) Although the converted data is placed in a new buffer, the block identity is not lost; data blocks remain logically invariant regardless of the number of conversions that occur. Since the block format itself provides only a limited set of commands, one type of block called a CMD block is dedicated to handling the large number of specific commands needed to set up the connections of the network and to handling data flow over these connections. If the information carried by these command blocks is primarily to establish, change, or delete connections (a process known as configuring the network), the message is called a service message and is handled by the service module. Service messages are used to: • configure logical links, trunks, lines, and terminals Operating system (space allocation, calls, interrupt handling) Multiplexer subsystem • command loading or dumping of the NPU Interprogram communications (worklist) • command on-line or inline diagnostics or debugging, or carry information about such processes Timing services Standard subroutines Internal processor maintenance Figure 1-7. CCP Software Levels • carry status concerning failure and recovery • command that a message be broadcast to one terminal or several terminals (including sending a message from a terminal to the network operator's (NOP) or local operator's (LOP) terminal) Host Interface Package • common subroutines such as those for code conversion Most base subroutines are written in PASCAL language; a few are written in CYBER 18 macro assembler language. The host interface package (HIP) handles the protocol governing transmissions between the host and the NPU. The route of all such transmissions is through the coupler hardware. Three coupler registers hold status or command information; one register contains the NPU address of the data to be transferred, and one set of lines connects the host PPU buffer to the direct memory access buffer register of the NPU. This set of lines handles all data transfers. Block Interface Package (BIP) The next level of CCP software is concerned with handling network communications. It provides block switching so that the data block can ultimately be routed downline to the proper terminal, or upline to the host. Data traveling in either direction is tagged with the terminal ID. A group of directories is used to route the block to the next program that must process the block. Transfer of information (messages or files) through the host/NPU part of the network is accomplished by transmitting the data in blocks (this is called block protocol throughout this manual). A number of block types are defined. Two block types are dedicated to data transfer; the remaining block types contain control information such as acknowledging messages, controlling data flow on a connection, or starting and stopping transmissions. 60471400 G In all cases the format of the byte in the host PPU is 12 bits and the associated half-word (byte) in the NPU is 8 bits. Adjustment is made so that the receiving unit (host or NPU) has an input only as large as its input word or byte size. Usually, the NPU memory address register is set up by the NPU for upline or downline data transfer. When dumping the contents of the NPU to the host the PPU sets up the register to supply the memory to be dumped. Four principal functions are performed across the interface. MICROMEMORY START AND STOP Micromemory start and stop commands are issued by the host. The micromemory must be started at location zero. 1-11 CONTROL WORD TRANSFERS The NPU sets function commands to the coupler, allowing the coupler to chain buffers of data during transfer, to clear the coupler registers, to read the other status registers, to ready the PPU to read the status registers, and to set the memory address register prior to starting a data transfer. The PPU sets functions to clear the coupler or NPU, to start or stop the NPU, to input or output a program during the load/dump phase of NPU initialization, to load the memory address for dump operations, and to set or read the other two status-type registers. STATUS WORDS One status word is used for regulation. There are four regulation levels: (1) to transmit all messages to the NPU, (2) to transmit all but messages for batch-type devices, (3) to transmit only service messages, and (4) to transmit no messages. Regulation is a function of the availability of NPU buffers to receive input messages. DATA TRANSFERS For downline transfers, the NPU assigns the next data buffer, sets up buffer chaining, if necessary, and switches the block to the proper internal handling or terminal/line/TIP. For upline transfers, when the full message is ready, the NPU makes the address of the first buffer in the chain available. When one buffer is transferred, the starting address of the next chained buffer is provided by the coupler hardware. This continues until the full message is transmitted. Since the DMA/PPU buffer channel is half-duplex (data can be sent in only one direction at a time), contention for channel use is normally resolved in favor of outputting blocks from the PPU. However, following this transfer, the protocol provides a short period during which the NPU can request channel use without the PPU contending for channel use. No attempt is made to retransmit data in anything less than a full block. When a bad block is rejected, the entire message is rejected and must be retransmitted in its entirety. Link Interface Package Since the link interface package (LIP) handles transmission and reception on both ends of a trunk, a copy of the LIP is required in both the local and the remote NPU. Two major types of operations are handled by the LIP: loading/dumping the remote NPU, and processing data transmissions over the trunk. Data message transmissions across the trunk use a unit called a trunk transmission frame (TTF or frame). There are three types of frames: • unnumbered frames which establish the basic trans mission states between the two nodes (such as initialization, disconnect, command rejected) • supervisory frames that establish whether trans mission/reception is currently possible (ready for data/not ready for data/rejected last data sent) 1-12 • information frames used to transmit message data; this class of frames includes frames that are carrying service messages Both frame size and data block size are customization time selections. The information frames themselves are com posed of one or more subblocks. Each subblock is a buffer of information related to a single message so that the frame may be considered as a packet of information subblocks contaning one or more message parts for one or more terminals. Either end of the link may initiate data transmission when conditions warrant. Once the interfacing LIPs have established the normal mode, data transmission can begin. A remote NPU has no coupler to the host, and therefore no HIP. Terminal data passes through the multiplex subsystem of the remote NPU twice: once as it passes between the terminal and the NPU, and once as it passes between local and remote NPUs. Upline data in the remote NPU is demultiplexed and passed to the appropriate TIP for conversion. Completed, converted messages are passed to the LIP for framing and then passed through the multiplex subsystem, over the trunk to the local NPU. Trunk transmission rate is up to 19.2 Kbps. In the local NPU, upline data from the trunk is received by the LIP and reconstructed into a message in data buffers. Then it is passed to the HIP for transmission to the host. Downline data is taken from a message data buffer, assembled into frame format by the LIP, and sent to the remote NPU. Once it is demultiplexed by the LlP/multiplex subsystem, it is ready to be passed to the appropriate TIP for conversion to terminal format. LOADING/DUMPING OF REMOTE NPU The local NPU processes the load/dump operation in its overlay area. The program information is transmitted to/from the local NPU overlay area in block form. The local LIP passes the programs (downline) and receives the dumped main memory contents (upline) in frame format. The remote NPU LIP is responsible for stripping the frame information from the downline subblocks and loading these subblocks (parts of programs) at the location indicated by the host. For dumping, the LIP is responsible for placing the main memory contents (starting at the address indicated by the host) into frames and sending the frames to the local NPU. Configuring the remote NPU is handled by service messages, as in the case of configuring a local NPU. The service messages are transmitted across the trunk in the same manner as any other message data. TRUNK TRANSMISSION PRIORITIES AND REGULATION A high or a low priority is assigned to each subblock. High priority is associated with interactive terminals and low priority is associated with batch terminals. Each time a new frame can be transmitted the LIP scans the high and low priority queues. If high priority data is waiting, it is always transmitted ahead of low priority data. On input (in either the local or the remote NPU), data can be rejected if the number of available buffers has dropped to the threshold level. First low-priority traffic is rejected, then high-priority traffic. Supervisory frames are not included in this priority scheme. These frames contain some command/status information, but do not include most service message instructions which are treated as high 60471400 G ^ s priority. Thus, during regulation, some command/status information can be rejected while other command/status information passes over the trunk. TRANSMISSION ASSURANCE The CDCCP protocol requires that each frame be acknowledged. Since several frames may have been transmitted before a negative acknowledgment for a given frame is generated, all frames up to and including the last properly acknowledged frame are retransmitted. No frame is released from the sending NPU until it is properly acknowledged. Frame checking is provided by a cyclic redundancy checksum (CRC) which is generated by the sending CLA and included at the end of each frame. Terminal Interface Packages A terminal interface package (TIP) interfaces the terminal data (messages) to the network. The terminal interface is processed through the multiplex subsystem; the system interface is processed through the line control blocks (LCBs) and terminal control blocks (TCBs). Five standard TIPs can be included in a system: ASYNCHRONOUS TIP The asynchronous TIP supports dedicated and dial-up asyn chronous lines. The TIP provides software support for most teletypewriter-like terminals. The interface format between the host and the TIP is handled by the interactive virtual terminal and user interface. The asynchronous TIP supports a terminal-to-virtual trans form for eight types of terminals. To expand the usefulness of this TIP, a method is provided for the user at a terminal or a connected application to vary parameters and operating modes for any of the eight terminal types. This provides service for terminals which may differ from the eight terminal types. Line types supported are: • An async (asynchronous) TIP either in normal or extended format. This handles only interactive data. • dedicated or dial-up • A binary synchronous communication (BSC) TIP that handles both batch and interactive data. • full-duplex • A synchronous TIP for HASP workstations that handles both batch and interactive data. • A Mode 4 (synchronous) TIP which processes data from both batch and interactive devices. • An X.25 (synchronous) TIP with a packet handling (PAD) subTIP. This handles only interactive data that arrives through a public data network. Each TIP handles the protocol level for its terminal type. Specialized additional information for the connection is contained in the LCB, the logical channel control block (LCCB), and the TCB. The software portion of a TIP is written on several levels: • One or more OPS-levels control message transfer, including major error (transmission failures) processing, transfer setup, and transfer completion. Code and format translation are controlled by an OPS-level. 4 A mux-2 level is occasionally used for error processing. 3 Several OPS-levels: The X.25 TIP uses one OPS-level to supervise protocol/terminals, another to control packet flow (related to connections between host applications and terminals), a third to control frame flow (related to the connection between the CDC network or the X.25 public data network), and a fourth (called a sub-TIP) to handle the format conversions. • One or more microprocessing (firmware) levels perform upline/downline text processing and demultiplex upline messages. A number of OPS-levels exist; standard TIPs are written on: • A single OPS-level: The async TIP uses one OPS-level to control message flow, error checking, and code/format translation. • Two OPS-levels: The Mode 4, HASP, and BSC TIPs use one OPS level to control code/format conversion of blocks. Another OPS-level controls message flow. 60471400 G • two or four-wire The TIP is prepared to receive input at all times and attempts to deliver output whenever available, unless input is currently active. When input is detected during output, the TIP suspends output. This output is sent later. All input and output is converted between the terminal and virtual terminal characteristics. The TIP provides an auto-recognition feature for each line. The result of this feature is a service message from the TIP informing the host of the line speed. For the 2741 terminal, the TIP provides code recognition. Several parity options are provided, and paper tape input/output is supported. MODE 4 TIP The Mode 4 TIP interfaces with devices using Mode 4A or 4C protocols. A typical Mode 4 device would be the card reader, printer, keyboard, and CRT of a CDC 200 user terminal (UT). Interactive data is exchanged with a host application in IVT format; batch data is exchanged in PRU block (PRUB) format. The TIP is insensitive to line speeds; it supports synchronous lines operating at rates up to 9600 baud. Lines may be dedicated (with or without a transceiver) or switched (dialup) with a modem. All lines are considered to be halfduplex. Each line may have more than one cluster of equipment and each equipment cluster may have more than one terminal. Lines with multiple clusters must be dedicated. The TIP performs auto-recognition when requested by the host. Auto-recognition causes the TIP to return a service message to the host which contains information on terminal type, cluster address, terminal address, and device type. Multi-cluster auto-recognition is not supported. 1-13 The Mode 4 TIP supports remote batch terminals as separate but dependent devices. The TIP polls the terminal to determine when data should be sent. The TIP performs recovery for line or terminal errors. Any error from which an immediate recovery is not possible is reported to the host. The Mode 4 TIP counts all lines of batch output data sent to a terminal and all card images of batch data sent to the host. When a batch file or device connection is terminated, this data (called accounting data) is fowarded to the host to be merged with host usage accounting data. BINARY SYNCHRONOUS COMMUNICATIONS (BSC) TIP The BSC TIP provides data interchange between a host application program and a remote IBM 2780, 3780 or compatible batch terminal. The TIP provides batch and interactive capabilities. The interactive console is simulated by accepting input from the card reader and sending output to the line printer. Exchange of information between the NPU and a terminal uses the point-to-point binary synchronous communications protocol with contention resolution. Batch devices communicate with host applications using PRUB format; interactive data uses IVT blocks. The normal code of a 2780/3780 is EBCDIC; transparent mode is permitted. BSC terminals can be attached to an NPU through dedicatee or dial-in synchronous lines operating at speeds up to 19200 bps. A terminal consists of a required card reader, a required line printer, and an optional card punch. BSC input devices have precedence over output devices and interactive devices have precedence over batch devices. For non-transparent line printer output, the TIP supplies appropriate carriage control transformations (format effector processing). The host can supply preprint or postprint format effectors; BSC terminals support only postprint carriage controls. A print message (PM) in the output stream to a printer stops the batch output and allows the host to send an interactive output message to the printer. Autorecognition allows the terminal to report its own type, cluster address, and terminal address. The terminal address is used for the optional card punch. HASP MULTILEAVING TIP The TIP provides network interfacing to a HASP multileaving-type of terminal which may contain both interactive and batch devices. These terminals have computer-like functions. The term multileaving describes the computer-to-computer communciations technique used by a HASP terminal. The system uses fully-synchronized, pseudo-simultaneous, bidirectional transmission of a variable number of data streams between two computers and requires binary syn chronous communications facilities. In this configuration, the multileaving capability is used only in the upline direction. 1-14 The basic element of multileaving transmission is a character string which is embedded in a data (message) block. One or more character strings are formed from the smallest external element of transmission—the physical record. The transmitting program segments the data to be trans mitted into an optimum number of character strings. The receiving program reconstructs the original record for processing. Multiple physical records of various types can be grouped together in a single transmission block. Multileaving allows for two computers to exchange transmission blocks containing multiple data streams in an interleaved fashion. For optimum use of this capability, the system controls the flow of one data stream while continuing normal transmission of others. To meter the flow of individual data streams, a function control sequence (FCS) is added to each block. Error detection and correction information are also provided. Protocol Operation - After the communications line is initialized and the terminal is signed on, the NPU and the terminal transmit idle blocks until a function is desired. The process initiating the function transmits a request to initiate; the receiving process transmits permission to initiate. The requesting process then transmits data until an EOF is encountered. To transmit more data, the request to initiate must be repeated. ,^!SS£\ Data blocks are transmitted one block at a time. Before another block can be transmitted, the receiving process must transmit a positive response. Console functions (operator messages/commands) do not follow the request-to-initiate/permission-to-initiate sequence. A console function may be initiated at almost any time. /^ss. The following errors are recognized: cyclic redundancy check (CRC) errors, illegal block format, unknown responses, timeouts over the line, and a break in the sequence of transmitted blocks. For bad downline data, the TIP attempts to retransmit the block three times. On the fourth failure, the TIP forces a line inoperative status on the terminal. For upline data, the NPU attempts to receive a bad block four times. On the fourth failure, the TIP forces a line inoperative status on the terminal. Data Conversion and Compression - HASP terminals normally use EBCDIC code. Interactive data is exchanged with application programs in the host which use ASCn code in IVT format. Batch data is exchanged with applications programs which use display code in PRU format. In either case, the TIP makes the required format and code conversions. Transparent data is allowed in batch mode. Data compression is allowed in both transparent and non-transparent modes. HASP Console - The HASP console data is handled by the IVT. Auto-input is permitted. The HASP TIP accounts for all batch data exchanged with a terminal, including data sent in transparent mode to the plotters. When a batch file or device connection is terminated, this accounting data is fowarded to the host to be merged with other host usage accounting data. 60471400 G 259 so the frame is closed and transmitted with 166 bytes. The next frame will contain the second half of the 256-byte message and the other 32-byte message. Since no other messages are waiting to be transmitted, this frame is also closed and sent. NOTE This simplified example ignores such factors as checking frames on the receiving side, acknowledg ing them, and requiring retransmission of all frames since the last acknowledged good frame in the event that a frame transmission fails. As soon as the frame is stripped off in the receiving NPU, the various messages are reassembled into data blocks and all traces of frames disappear. 2-4 INITIALIZATION Since the terminals connected through the NPU must be configured to match the host's image of the network configuration, and since the NPU has no mass memory, the NPU image is kept on host mass storage and the NPU is downline-loaded from the host. After the baseline system is loaded, the host directs the NPU to configure its links, lines, and terminals by means of a series of service messages. The three steps of the initialization are: • (optional) dump the NPU so that contents can be used for later analysis to determine cause of failure • load the NPU from the host with the baseline program • configure the NPU by establishing the parameters of the logical links, lines and terminals connected to this NPU Differences in the initialization cycle result from hardware differences. The two formats required are for: • 2551 local NPUs • 2551 remote NPUs The host normally attempts to load/dump an NPU only if the NPU fails or if the network operator specifically requests a load. If the host itself fails, the NPU must also be reloaded when the host comes back on-line. In the case of an NPU failure, the host (optionally) first dumps the NPU contents. The NPU is then loaded. If the first attempt to load the NPU fails, another dump is taken. On subsequent consecutive attempts to load, dumping is inhib ited. After a set number of times, the NPU is marked down. Failure of a local NPU is detected by the host PPU channel. NPUs that are local to the host are loaded and dumped via the CYBER Coupler under the control of the PPU. The remote NPU requires an overlay process in the local NPU. When a remote NPU fails, the deadman timer is activated. A bootstrap load/dump program is read into the NPU from the system autostart module cassette, and that bootstrap program starts execution. The remote NPU then establishes contact with the local NPU. The local NPU communicates with the remote NPU using a restricted set of the communications protocol during this load/dump procedure. From this point forward, the load/dump procedure is controlled by the host, using an overlay in the local NPU. After the NPU is loaded, the host configures the unit by establishing all logical links and logical connections for that NPU. A logical connection is the association of two elements made by the assignment of a network logical address. The network logical address is a set of three numbers: two node IDs followed by a connection number. These three numbers are used together to trace through a set of increasingly specific directories: the destination node directory, the source node directory, and the connection directory. This process ultimately points to a terminal control block (TCB). The directories also have information concerning the logical link control block (LLCB), the line control block (LCB), and the logical channel control block (LCCB). It is these three control blocks that are the subject of the NPU configuration process. 60471400 G y^BSv The network supervisor (NS) program and the communica tions supervisor (CS) program in the host are responsible for the control of logical links and connections, respectively, in the network. All logical links and connections are explicitly configured, reconfigured and deleted by NS/CS using service messages (SM). Configuration proceeds in three stages: • establishing logical links • configuring lines • connecting terminal over the lines NS establishes all logical links which the current state of the network permits. NS notifies CS of each logical link to be established and the initial regulation level for the logical link. CS configures the lines and attempts to connect each terminal on the line. To connect the terminal, the line must be enabled. The terminal is connected by the NPU building the terminal control block (TCB) for the terminal. When the configure or reconfigure action has been performed, the block protocol is initiated and the connection is in use. BASE SYSTEM SOFTWARE The base system software consists of most of those portions of the CCP that are normally associated with a comprehensive operating system together with the associated standard utilities. The base system, plus the block interface package (BIP), and the other interface packages (HIP, UP, and all TIPs) constitute the standard CCP software. Initialization and configuration was desc ibed previously. The major features of the base system are: system monitor buffer handling worklist services queuing mechanisms direct program calls (switching services) interrupt handling timing services globals control block services directory maintenance standard subroutines for code translation, and special arithmetic functions multiplex subsystem operation the operations monitor (OPS) level. Programs on the OPS level communicate with one another using worklists. Para meters for the requested task are stored in a worklist and the worklist is placed in a first-in/first-out queue for the program to be called. The monitor scans the list of all programs capable of having worklist queues. If the monitor scan discovers a program with one or more worklists in its queue, control is passed to the program, together with the worklist which defines the parameters for the task. It is possible to pass control to a program for execution of more than one worklist, if that program is designated as being allowed to process more than one task before releasing control. In this case, the maximum number of queued tasks (worklists) are executed by the program before the program returns control to the monitor. When the task or tasks are completed, control returns to the monitor which resumes the scan at the next program on the list. Each time a program completes, a timer is advanced. This timer is checked by the interrupt level timer routine at specific system-defined intervals. If the timer expires, it indicates that some OPS-level program has been abnormally delayed. Monitor execution is then terminated and the NPU is stopped. BUFFER HANDLING The buffer handler allocates the four types of buffers and recovers buffers for the four free buffer pools when users are finished with them. Buffers are potentially available in six sizes: 4, 8, 16, 32, 64, and 128 words. At installation time, the user chooses any four contiguous sizes; for instance, 8, 16, 32, and 64 words. The largest size is designated as the data buffer size. Buffers are assigned one at a time; buffers can be released singly or in a chain of buffers. In conjunction with testing buffer availability to assure a minimum threshold number, buffer maintenance periodically attempts to adjust distribution of buffer sizes by using buffer mating or buffer splitting to replenish any buffer pool that is at threshold level. WORKLIST SERVICES Worklists provide a convenient method of handling communi cations between software modules that do not use direct calls. The list services function manipulates worklists by making worklist entries from any priority level (including OPS level). Characteristics of the queued worklists are: • first in, first out • one to six-word entries, but all entries in any one list of equal length SYSTEM MONITOR • lists exist in dynamically assigned space The NPU is a multiple interrupt level processor. Interrupts are serviced in a priority scheme in which all lower priority interrupts are disabled during execution of a program operating at a higher priority level. When no interrupt is in effect, the processor runs at its lowest priority, known as • No limit in the number of lists serviced 60471400 G If there is contention between priority interrupt levels when making an entry, this conflict is resolved by use of an intermediate worklist array. 2-5 QUEUING MECHANISMS I Several major queues are defined: • terminal control block (TCB) queue which controls input messages from the various terminals passed downline to the terminal I* TCB output queues which control messages to be • timing queue The input data processor (IDP) services the inter rupt produced when the MLIA places a data character or CLA status into the circular input buffer. The IDP (part of the multiplex subsystem) uses the designated input state program to process the character according to the requirements of the protocol and to transfer the characters to the lineoriented input buffer. The timing services firmware processes the 3.3millisecond clock interrupt which is used for the time base of all timed NPU functions. DIRECT PROGRAM CALLS (Switching Services) TIMING SERVICES Most OPS-level programs call other programs and subpro grams directly. One subroutine is provided for these direct calls. The same program also is the final step in the worklist calling sequence. It provides switching for pro grams on different main memory pages, timed and periodic calls, service message switching, and overlay execution, as well as actual passing of control for programs called by the monitor. Timing services provide the means for running those programs or functions which must be executed periodically or following a specific lapse of time. These timing services are available: INTERRUPT HANDLING The NPU can recognize 16 different macrointerrupts. Each has its own address to which control is transferred when the interrupt is acknowledged. When the computer is processing a particular interrupt, it is defined as being in the interrupt state (state 00 through 15). However, before the computer can recognize an interrupt, the corresponding mask bit in the interrupt mask register must be set and the interrupt system must be activated. Upon recognizing an interrupt, the hardware stores the appropriate program return address to ensure that the software can return to the interrupted program after interrupt processing. The interrupt handler that is activated also saves selected NPU registers for the interrupted program. The interrupt mask is then loaded with a mask to be used while in this interrupt state. The program then saves the current software priority level, sets the new software level, acti vates the interrupt system, and processes the interrupt. During interrupt processing, an interrupt request with a higher priority may interrupt this program. Such higher level interrupts also store return address links and registers to permit sequential interrupt processing according to priority level with eventual return to the main-stream computer program. The computer exits from an interrupt state when processing is completed. The handler inhibits interrupts, restores the registers, and retrieves the return address of the interrupted program. Control is transferred to the return address and the interrupt system is again activated. Three microinterrupts are also serviced: • The output data processor (ODP) services the output data demand (ODD) interrupt which each CLA generates to indicate that it is ready to output another character. The ODP (part of the multiplex subsystem) gets the next character from the appropriate line-oriented output buffer and puts the character on the output loop. The requesting CLA picks the character from the loop and transmits it. 2-6 /^^t\ • A firmware program handles the 3.3-millisecond microinterrupt to provide a 100-millisecond timing interval. • Every 100 milliseconds, a timing routine searches a x-«sv chain of time-lapse entries. If any entry's time ■ period has elapsed, that entry is deleted from the chain and a worklist entry is sent to the program for which the delayed call was requested. Timing services also handle adding delay requests to this delay request chain. • Every 500 milliseconds, a timing routine checks the deadman timer. The timer is reset and the monitor timeout routine is checked. If the monitor timer has expired, it indicates that the monitor has spent too long in one OPS-level program. The NPU is stopped. /^«k • Every 100 milliseconds, a timing routine scans the list of active line control blocks (LCBs) for ASYNC I TIP terminals. If a character has been received, | the timeout is reset for the next character. If the character has timed out (no character received within 100 milliseconds), the LCB is removed from the active list and the ASYNC TIP is notified. • A 500-millisecond program time has these principal functions: Every second, a timing routine checks all 1 active outputting lines to see if an output data demand (ODD) has been generated for the next character to output. If a second has expired with no new ODD interrupt, the multiplex event worklist processor is called to declare a hardware failure for the line. Every 500 milliseconds, a timing routine scans all active lines for periodic requests. If the period has elapsed, the TIP is called using a worklist. Input or output can be terminated for the line if this is requested. Inactive LCBs are unchained from the set of active LCBs. Timer services also provide the means of chaining LCBs to this list of LCBs requiring periodic action. A time-of-day routine is called every second. The time of day is incremented and, if necessary, recycled to start of day (00 hour, 00 minute, 00 second). 60471400 G 3 <*s^ GLOBALS PASCAL-coded programs can use global variables, tables, and constants. PASCAL globals are defined in the CYBER Cross PASCAL Compiler Reference Manual. The principal globals used by standard CCP programs are described in the CCP System Programmer's Reference Manual. CONTROL BLOCK SERVICES The line control blocks (LCBs) are a vital part of the configuration data. The blocks consist of a series of entries, one for each line. LCBs are chained together and are therefore handled as a series of active, chained blocks. Entries that are no longer active are flagged. If an entire block has no active entries, the block is unchained and released. New blocks are added as needed. The LCB space, however, is dedicated and cannot be used for other purposes. DIRECTORY MAINTENANCE This set of modules sets up and maintains the directories which are used for block routing. STANDARD SUBROUTINES controls modems and analyzes status • chains data buffers as necessary to create data blocks • processes commands issued by the communications system software • dynamically alters the input character processing characteristics as a function of the connected terminal Figure 2-2 shows the basic multiplex subsystem elements. Input Multiplexing Each line has a communications line adapter (CLA). The CLA for each active line is sampled in sequence and if a character is ready, it is placed on the input multiplexer loop together with information identifying the source (line) and, in some cases, the nature of the character (for instance, this type may contain control information rather than a charac ter of message data). All information on the input multiplex loop is routed to a circular input buffer (CIB) which is usually 512 words long. The demultiplexing operation picks data from this buffer and reconstitutes the messages on a line input basis. This group of subroutines provides handling to: convert and handle numbers handle interrupt masks maintain paging registers save/restore registers set/clear protect bits code conversions perform miscellaneous other tasks MULTIPLEX SUBSYSTEM OPERATION The multiplex subsystem has two principal tasks: • relieve the TIPs of having to process lines accord ing the the physical line characteristics (most line characteristics are invisible to the TIPs as a result of multiplex subsystem processing) • multiplex the data to match the low-speed charac teristics of individual terminals with the high-speed characteristics of the NPU and the host The principal multiplex subsystem functions are: • receives serial data from communications lines, places it in a circular input buffer, demultiplexes it and places it into line-oriented input buffers • transmits serial data to communications lines from line-oriented output buffers • detects and processes special characters • translates code on input • checks CRC • checks and generates character parity • detects breaks • assembles input data into blocks Output Multiplexing When the NPU has received a message block from the host and a TIP has transformed the code/format from IVT or PRU to terminal format, the TIP notifies the multiplex subsystem that the transmission block is ready for output. The multiplex subsystem picks the characters from the line's output message buffer one at a time, whenever a new output data demand (ODD) is generated by the CLA. (The ODD indicates the terminal is ready to receive another character.) The outgoing characters are placed on the output multiplex loop, along with such control characters as are needed, and an address that will be recognized by the active line for that terminal. The CLA for the line recognizes the address, picks that data from the output loop, and marks it as being sent. When the contents of the entire output buffer for the line have been transmitted, and the message has been acknowledged as received by the terminal, the multiplex subsystem notifies the TIP. The TIP releases the message buffers and notifies the host of a successful transmission. In some cases the TIP discards the output message even if it was not successfully transmitted. Trunk Multiplexing If a remote NPU is included in the network, transmissions between the local NPU (see previous subsection on 255x hardware) and the remote NPU take place over a trunk. In the local NPU, a link interface package (LIP) sets up the output buffer, and the message in that buffer remains in IVT or PRU format while being transmitted over the trunk. In the remote NPU, the downline messages are treated similarly to upline messages in a local NPU; that is, the message goes through the CIB and is then demultiplexed by the LIP for the TIP. After the TIP translates the code from virtual terminal format to terminal format, the message is treated as an output message in a local NPU; that is, the message is multiplexed for transmission, is sent, and is acknowledged. The acknowledgment must be for matted then as any other input message: remultiplexed, and sent upline through the local NPU to the host. ^ms 60471400 G 2-7 r^ms. INPUT LOOP <0L OUTPUT LOOP COMMUNICATIONS PROCESSOR tt v MULTIPLEX SUBSYSTEM MICROPRO GRAMS AND SOFTWARE INCLUDES COMMAND DRIVER, INPUT DATA PROCESSOR, AND OUTPUT DATA PROCESSOR LOOP MULTI PLEXER MULTIPLEX LOOP INTERFACE ADAPTER (MLIA) MULTIPLEX LOOPS I T nQiA4-*l LOOP MULTI PLEXER MEMORY BUFFERS I &v COMMUNI CATIONS LINES OR TRUNKS V| Vyl ( CLA W4—▶ "t ■MULTIPLEX SUBSYSTEM- CLA - COMMUNICATIONS LINE ADAPTER TIP - TERMINAL INTERFACE PROGRAM LIP - LINK INTERFACE PROGRAM Figure 2-2. Basic Elements of the Multiplex Subsystem Input messages (upline traffic) are reformatted from terminal to PRU or IVT format as in a local NPU, but are then sent by the LIP through the remote NPU multiplexer, received by the local NPU multiplexer, and reconstructed into complete messages in the local NPU by that NPU's LIP. It is apparent then, that through messages (non-control messages) are multiplexed twice in a remote NPU, once to/from the terminal and again from/to the local NPU. Demultiplexing For one-pass TIPs, the multiplex subsystem is responsible for picking data out of the CIB as well as for putting it into a line-oriented input buffer. When a message transmission starts, the multiplex subsystem reserves a data buffer for the message (data buffers are normally 64 words long, with 2 characters per word). The words in the CIB are identified by the line number, and are packed into a line-oriented input buffer. If a buffer is filled before the message is complete, another buffer is assigned and is chained to the first. ^3iS3K BLOCK INTERFACE PACKAGE (BIP) This CCP software handles network communications. The major BIP functions are: • Routing (switching) blocks for the CCP. • Providing routines to handle the block protocol on the host interface side of the TIPs. Bad blocks are discarded and good blocks are acknowledged. The host senses that a downline block has been discarded by failure to receive an acknowledgment. The terminal is notified with a message when a downline block is discarded due to no connection. Some PRU and IVT formatting is also done. • Handling failure and recovery, loading and dumping, and regulating input to the NPU. When the end of text (ETX or the equivalent) is detected, the TIP appropriate for the terminal type is called. It continues the processing by passing the message to the host interface package (HIP). The HIP will then pass the message through the coupler to the PPU of the host. • Providing system diagnostics. Routines send alarm messages to the network operator, and generate CE alarm messages and statistics for the host engineering file. Also, if the NPU stops, the diagnostics provide a reason code and other information concerning the stop. The demultiplexing of downline transfers is a terminal function; that is, the message is reconstituted in a buffer for the screen, printer, magnetic tape, etc. • Handling the service messages which configure the network. 2-8 60471400 G BLOCK ROUTING ROUTING A major portion of this processing provides block switching so that the data block can ultimately be routed downline to the proper terminal or upline to the host. Routing routines check the blocks for validity and queue the block to the TCBs if necessary. These routines also purge the data block queues when the network or a connection is reconfigured. Collectively some of the routing and queue maintenance routines are known as downline TIP services and upline TIP services. Data traveling in either direction is tagged by the terminal ID. A group of directories are provided which assures that the block control information (contained in a header) is decoded. The block is attached, through control blocks for that line/trunk and terminal, to the next program that must process the block. SERVICE MODULE The block format itself allows only a limited set of commands. Most of the large number of specific commands transmitted throughout the system are handled by the special type of command block called a service message. These messages are handled by the service module. There is a large variety of service messages (one type for each command, with a related normal response and a related error response): • Configuring logical links, trunks, lines, and terminals, as well as the basic load/dump NPU service messages, are described in the initiali zation section (section 3). These messages originate in the NS or CS modules of the host for normal configuration and reconfiguration. Mal functioning of a line or any component of the line may generate an upline service message indicating that the line or component is no longer usable. NS or CS will then reconfigure the network accord ingly. • Service messages regarding failure and recovery, and those that support diagnostics are discussed in section 4 (failure, recovery and diagnostics). • The remaining service messages provide com mands for such things as status, broadcasting a message to a terminal, or sending a message from a terminal to the network operator's (NOP) or local operator's (LOP) terminal. INTERACTIVE VIRTUAL TERMINAL COMMANDS Interactive virtual terminals are capable of changing some of their operating characteristics such as page width, page length, the character to be used for breaks, backspacing, aborts and other terminal features. These command messages can originate from the host or from the terminal The BIP supplies routines to validate the commands and to start implementation of the commands. BATCH TERMINAL PRU COMMANDS Batch device operating characteristics can also be changed. There are two types of changes: those which change device characteristics (page width or length, PRU block length, and sub device type) and those which change file characteristics (file type, file limit, carriage control, punch and lace card control). Both types are sent downline from the host; the code type (026/029 punch) and transparent/non-transparent mode can also be changed by BSC/HASP batch devices. The BIP supplies routines to validate the commands and to start the implementation of the commands. 60471400 G BLOCK ACKNOWLEDGMENT AND DATA FLOW CONTROL The BIP acknowledges downline blocks (examples: a BACK block is generated to inform the host that a message was successfully output to a terminal by the responsible TIP, or accounting data is sent for a PRU block indicating the block was successfully sent to the terminal). Accounting data is formatted for the host when an EOI occurs. PROCESSING SPECIAL CHARACTERS AND IVT COMMANDS The BIP provides routines to check special characters (cancels, breaks, interrupts) in an upline message. If such characters are found, the BIP takes the necessary action on the current message (such as discarding the current data). If IVT commands are found, the BIP calls the IVT processor to execute the command, to change the network configuration, and to notify the host if necessary. The programs also handle all the other kinds of control blocks except the CMD blocks which are handled by the service module. PROCESSING AUTOINPUT The BIP saves the first 20 characters of an autoinput message from the host so that these characters can be used to preface the autoinput reply from the terminal. COMMON TIP SUBROUTINES A number of common TIP subroutines are provided to: queue output blocks. The TIP is notified that output needs to be processed. Handle upline break signals from a terminal. Output operations are halted and the host is notified to stop sending output data on this line. Handle downline break from the host. The TIP will not send more input data to the host until the host is again ready to receive data for this line. Handle a request from the TIP to stop output data from the host for a given line. Handle requests from a TIP to escape to firmware processing. This is used for the text-processing operation. Find the number of characters to be processed. Save and restore TIP processing entry points so that a TIP can temporarily suspend processing while waiting for some external event to occur. The TIP may be simultaneously suspended for one output and one input operation. 2-9 Handle a common control relinquishing request. This assures that return of control to the OPSmonitor is complete and correct. FAILURE AND RECOVERY Several types of failure are possible, Each requires its own recovery or avoidance technique. Host Failure If a host fails, the NPU and its software must necessarily stop message processing. Host unavailability is communi cated to the other ends of all logical links. Also, the NPU sends an informative service message to all connected, interactive terminals (and to some other types of terminals) informing the terminal that the host is unavailable. After recovery, all logical links are reinitialized and new connec tions are made. The host recovers the existing configuration status by means of status requests to the NPU. Initialization requires the downline-loading technique described above, followed by complete reconfiguration using the status information recovered from the NPU. NPU Failure If an NPU fails, it must be reloaded and reconfigured from the host. Off-line diagnostic tests may be desirable during this period to help identify the cause of failure. Failure is detected by means of a 10-second timeout across the coupler. The NPU is forced to generate a request for load message. Recovery consists of a dump (optional), load, and recon figure operation. If the initial two load operations fail, the host does not request a dump after the second or any subsequent attempt to reload. After n successive attempts to load, the loading operation is aborted, and the NPU is ignored until manually reactivated. If the NPU is success fully loaded and initialized, NS and CS in the host set up all logical links, lines, and terminals for that NPU which the present state of the network allows. Line Failure Lines are disconnected and terminal control blocks (TCBs) associated with the lines are deleted. A line failure is detected by abnormal modem status or by line protocol failure. The change of status is reported to CS in the host. A line cannot recover spontaneously. CS (which owns the lines) deletes the supported TCBs. Then CS disables and reenables the line, using the appropriate service messages. When line status changes to operational and this is reported to CS, CS attempts to configure the supported terminals. Terminal Failure Terminal status is reported and messages are discarded. TCBs are not released. Once terminal failure has been detected, possible terminal recovery is monitored by a periodic status check or diagnostic poll made from the NPU to the terminal. Terminal recovery status is reported to CS. DIAGNOSTICS Three types of diagnostics are associated with the NPU: inline, on-line, and off-line. Only the inline diagnostics are a part of CCP. The on-line and off-line diagnostics are a part of the network maintenance package, which is optional. • Inline diagnostics include CE error and alarm messages, statistics messages concerning hardware performance, halt code messages that specify the reason for a NPU failure, and off-line dumps. • On-line diagnostics provide closed-loop testing of the circuits connecting the NPUs to the terminals. These tests are available for installations pur chasing a maintenance contract. ^&H^S • Off-line diagnostics are hardware tests for NPU circuits. They are described in detail in the Network Processor Unit Hardware Maintenance Manual. INTERFACE PACKAGES Logical Link Failure Host failure, one of the causes of link failure, was mentioned previously. Link protocol failure leads to higher and higher levels of regulation until message traffic ceases on the link. A logical link may recover spontaneously (regulation level drops), or may be reinitialized by the host. In the case of spontaneous recovery, the logical link protocol allows a restart without loss of data. Otherwise, all logical connec tions must be remade. Trunks connecting neighboring NPUs are a special class of links. Trunk recovery protocol is handled by the LIP. Trunk Failure A trunk failure (such as the trunk connecting the NOS network to the Public Data Network) is detected by a failure of the trunk protocol. All data queued for transmission on the trunk is discarded. The failure is reported to the host. The trunk protocol detects the trunk recovery. The logical link protocol determines when the trunk can again be used for data block transmissions. 2-10 CCP provides seven standard interface packages: .^Sejy • A host interface package (HIP) handles the host/NPU channel. This channel uses high-speed transfers to move 16 bits of data at a time between the PPU and NPU memories. These parallel data transfers do not use data assurance techniques since the channel's noise level is low. Data on this channel is in IVT/PRU format. The code is transparent to the HIP, except that an 8-bit byte is assumed. The interface requires a CYBER 70/170 host coupler hardware unit. • A LIP uses a high-speed link to move messages from any kind of a terminal between a local and a remote NPU. The functions of a LIP are shown in figure 2-3. • An ASYNC TIP services TTY-type asynchronous terminals connected to the network on low/ medium-speed voice-grade lines. Terminals must be asynchronous. The TIP supports ASCII, IBM extended BCD, APL, correspondence code, and variants of these. 60471400 G 00&Ss* MULTIPLEX SUBSYSTEM INTERFACES LOCAL NPU UPLINE HOST IVT/PRU BLOCKS REMOTE NPU BIP LIP SELECTS COUPLER (HIP) RECONSTITUTES LINE-RELATED IVT/PRU BLOCKS. OATA ASSURANCE FRAMES* LIP SUBBLOCKS, PRIORITY SELECTION. NON-LINE RELATED FRAMES _ ASYNC - MODE 4 HASP TIPS CONVERTS TO FIRST STAGE OF IVT/PRU FORMAT tc »Ul JL (H —JJKPJ ... NU T SHOWN) BIT-SERIAL. HIGH SPEED TRANSMISSIONS BIT-SERIAL. LOW/MEOIUM-SPEED TRANSMISSIONS • ALL INTERNAL OPERATIONS ARE WORD ORIENTED 'FINAL IVT/PRU CONVERSION IWORO-2 CHARACTERS) Figure 2-3. Functions of a LIP A Mode 4 TIP services Mode 4A and 4C terminals which connect to the network through a cluster controller (this may be physically incorporated into the terminal). The controller communicates with the NPU over a low/medium-speed voice-grade line. Transfers over a Mode 4 line are synchronous. The TIP supports ASCII and external BCD codes. The HASP TIP services any terminal or device connected to the network through a HASP workstation. The workstation communicates with the NPU over a low/medium-speed voice-grade line. Transfers over a HASP line are synchronous, using a variant of the BSC protocol. The TIP supports EBCDIC code. The Binary Synchronous Communications (BSC) TIP supports IBM 2780 and 3780 batch terminals. The terminals communicate with the NPU over a low/medium-speed voice-grade line. Transfers over a BSC line are synchronous. The TIP supports EBCDIC code. The functions of an ASYNC, Mode 4, BSC or HASP TIP are shown in figure 2-4. • An X.25 TIP together with a PAD subTIP services TTY-type asynchronous terminals connected to the network through an X.25 public data network (PDN). The PDN communicates to the NPU over a high-speed synchronous line; terminals commu nicate to the PDN over asynchronous low/ medium-speed voice-grade lines. On the terminal side, the PDN must provide a packet assembly/disassembly (PAD) access. The functions of the X.25 TIP are shown in figure 2-5. The TIP supports ASCII code. 60471400 G HARDWARE USED BY INTERFACE PACKAGES Table 2-3 summaries the hardware characteristics and functions of each of the interface packages. SOFTWARE USED BY INTERFACE PACKAGES Table 2-4 summarized the software characteristics and functions of each of the interface packages. HOST INTERFACE PACKAGE The host interface package (HIP) handles the protocol governing transmissions between the host and the NPU. The route of all such transmissions is through the coupler hardware. This hardware contains three registers which have status or command information, one register that contains the NPU address of the data to be transferred, and one set of lines connecting the host peripheral processing unit (PPU) buffer to the direct memory access (DMA) buffer register of the NPU. In all cases the format of the byte in the host is 12 bits, and the associated word (2 bytes) in the NPU is 16 bits. For address and data information the 12-bit host byte does not directly use the upper four bits, making the host interface effectively an 8-bit byte. Two bytes are needed to make the associated 16-bit NPU word. For the three status-type registers (coupler status, orderword commands, and NPU status), only the lower 12 bits are used. The NPU memory address register is set up by the NPU for upline or downline data transfer. The register is set up by the PPU when dumping the contents of the NPU to the host. In that case, the host uses the supplied address as the starting address of the next block of main memory to be dumped. 2-11 LOCAL NPU HOST IVT/PRU BLOCKS BIP TIPS FINAL CONVERSION TO IVT/PRU CONVERT CODE, FORMAT BUILD 1ST STAGE IVT/ PRU BLOCKS, HIGH-LEVEL ERROR HANDLING PASS BLOCKS TO TIP, ACKNOWLEDGE BLOCKS (HIP FUNCTIONS NOT SHOWN) MUX CONVERTS BIT-SERIAL TO/FROM BITPARALLEL (CHARACTERS), LOW-LEVEL LINE-ERROR HANDLING A^&^ts. in < z I UJ CONVERT CODE, FORMAT TO TERMINAL TYPE HIGHLEVEL ERROR HANDLING *— LOW/MEDIUM-SPEED BIT STREAM IN TERMINAL FORMAT INTERNAL OPERATIONS ARE WORD-ORIENTED (WORD=2 CHARACTERS) Figure 2-4. Functions of a TIP (not X.25 TIP) TIPl AND LIP LOCAL NPU BIP OPS LEVEL MUX LEVEL BLOCK SEPARATES CONVERTS INTERFACE MESSAGES INTO BETWEEN TO HOST LINE-RELATED FRAMED BIT BLOCKS STREAM AND LINE-RELATED COLLECTS BLOCKS BLOCKS FOR FRAMINC BIT SERIAL HIGH SPEED FRAMES MUX LEVEL COLLECTS IVT/PRU BLOCKS FOR FRAMING DISTRIBUTES IVT/PRU BLOCKS TO TIPl TASK ALLOCATION HIGH-LEVEL ERROR PROCESSING FORMAT/ COOE CONVERSION CONVERTS BETWEEN BIT-SERIAL AND WORDS (BLOCKS) X.2S TIP AND PUBLIC DATA NETWORK (PON) LOCAL NPU SUBTIP (PAD) TASK ALLOCATION TEXT ft FORMAT CONVERSION (PACKETINGI (TERMINAL TO/FROM IVT) LEVEL 1 PACKET PROTOCOL HANDLING FRAME FORMATION FRAME DISCARDING MULTI PLEXED INPUT AND OUTPUT PDN BIT SERIAL HIGHSPEEO FRAMES -LOW/MEDIUMSPEED BIT-SERIAL STREAM r38»y FRAME AND PACKET ASSEMBLY/ DISASSEMBLY CONVERT TO/FROM BIT-SERIAL Figure 2-5. Comparison of TIP/LIP and X.25 TIP Functions The four principal functions performed across the interface are: • The host issues NPU start and stop commands for the micromemory processor. • The host loads programs into the NPU to initialize it or to change its mode (overlay programs). Dumping the contents of the NPU is usually a part of downline loading from the host. • The host or NPU sends one-word function com mands to the coupler and checks status across the coupler. One of the status registers regulates transmission rate across the coupler by rejecting certain types of messages when the NPU is in danger of running low or running out of buffers. • Blocks of data (messages) are transferred both upline and downline. Service messages are a special type of control that uses block data transfer techniques. 2-12 MICROMEMORY START AND STOP COMMANDS The micromemory must be started at location zero. Both start and stop commands are a special form of service message. CONTROL WORD TRANSFERS The NPU sets function commands to the PPU in four hexadecimal bytes, using one of the status-type registers. This allows the NPU to check switch status, chain buffers of data during transfer, clear the coupler registers, read the other two status-type registers, ready the PPU to read the status-type registers, and to set the memory address register prior to starting a data transfer. The PPU uses a 3-bit octal code to transmit functions. These commands clear the coupler or NPU, start the NPU, input or output a program during the load/dump phase of NPU initialization, load the memory address for dump operations, and set or read the other two status-type registers. 60471400 G ^*3$tv TABLE 2-3. HARDWARE USED BY INTERFACE PACKAGES I n t erface IP Required by Line Type and Line Characteristics PPU on host Every local or frontend NPU Channel, 16 bits parallel data plus 18 bits of address plus control/status lines. Asynchronous transfers. Mux Mux Both ends of a trunk subsystem subsystem High-speed, bit-serial full-duplex, dedi cated 4-wire. Asynchronous requests, syn chronous transfers. CRC-16 frame check provided. Mux TTY terminals in classes 1, 2, 4-8 TTY type terminals not connected to a public data network Low/medium-speed, voice-grade, bit-serial, full-duplex, 2-wire, dedicated/dial-up, c o n s t a n t c a r r i e r. C h a r a c t e r - o r i e n t e d , asynchronous transfers. Codes: ASCII (variants), APL (variants), IBM extended BCD (variants), correspondence code (vari ants). Characters require start and stop bits. Character parity provided. Mode 4A or 4C device Any Mode 4 terminals in classes 10-13, 15 Low/medium/high-speed, voice-grade, bitserial, half-duplex, 2 or 4-wire, dedi cated/dial-up, constant and controlled c a r r i e r. Te r m i n a l s c a n b e c o n s o l e s , c a r d r e a d e r s o r p r i n t e r s . Te r m i n a l c l u s t e r s allowed. Block-oriented, synchronous transfers. Codes: external BCD and ASCII. Longitudinal parity check on blocks. 2780/3780 controller Any BSC device in terminal classes 16 or 17 Low/medium-speed, voice-grade, bit-serial, half-duplex, 4-wire, dedicated or dial-in, c o n s t a n t c a r r i e r. Te r m i n a l d e v i c e s o p e r a t e in batch mode. Terminal can have a simu lated interactive device. Block-oriented, synchronous transfers. Code: EBCDIC. CRC-16 check on blocks. HASP workstation Any device that can connect to a HASP workstation (terminal classes 9 or 14) Low/medium/high-speed, voice-grade, bitserial, full-duplex, 4-wire, dedicated, c o n s t a n t a n d c o n t r o l l e d c a r r i e r. Wo r k station must be an interactive device. Terminals can be consoles, card readers, printers, card punches or plotters. Blockoriented, synchronous transfers. Code: EBCDIC. CRC-16 check on blocks. Public data network de vices with PAD access Any TTY terminal in classes 1, 2, or 5-8 High-speed, bit-serial, full-duplex, 4w i r e , d e d i c a t e d , c o n s t a n t c a r r i e r. P u b l i c data network must support packet assembly/ disassembly. Frame-oriented, synchronous transfers using packetized data. Code: ASCII. Character parity can be carried in text, but is not checked. CRC-16 frame check provided. Device To HIP Coupler LIP Async TIP Mode 4 TIP subsystem Mux subsystem BSC TIP Mux HASP Mux TIP X.25 TIP 60471400 G subsystem subsystem Mux subsystem 2-13 • TABLE 2-4. INTERFACE PACKAGE SOFTWARE CHARACTERISTICS Characteristic Interface Package Description Transfer Format HIP Host blocks. Blocks are based on an 8-bit byte in network block format. Longest IVT data block is 2043 bytes. Full PRU blocks are 640, 1280, or 1920 display code charac ters, or 320, 640, or 960 ASCII characters. Blocks are in chained buffers (64 words each). All data is treated as transparent. LIP A variant of HDLC protocol using frames and subblocks. Maximum frame size is a buildtime selection, and is normally chosen to be 1024 bytes. Subblocks based on buffer sizes. All data is transparent. ASYNC TIP Several variants of TTY character-oriented protocol. Input characters are gathered into blocks on the basis of a line (character string ending with a carriage return). Code translation between ASCII and terminal's code. Paper tape/cassette transfers delimited by the device on/off signal. Transparent mode is available. Mode 4 TIP Subset of the Mode 4A/4C protocol. IVT block mode used for interactive transfers; PRUB mode used for batch transfers. Code translation between ASCII and the terminal's code. Transparent mode is available. BSC TIP Subset of the BSC protocol. IVT block mode used for interactive transfers; PRUB mode used for batch transfers. Code translation between EBCDIC and ASCII (IVT) or display code (PRU). Transparent mode is available. HASP TIP HASP protocol, a BSC protocol variant. HASP blocks with one or more records used for both batch and interactive transfers. Upline HASP blocks contain records from one or more devices. Downline HASP blocks contain records for one device. Code translation between ASCII and EBCDIC. Format conversion between HASP blocks and IVT or PRU blocks. Transparent mode is available. X.25 TIP X.25 protocol (TIP level 2) uses synchronous frames containing data packets. At the terminal side of the public data network (PDN), a PAD access governed by CCITT X.3 protocol transforms asynchronous character streams into data packets and the reverse. In NPU, level 3, subTIP, and BIP transform packets into IVT blocks and the reverse. Transparent data transfers (also packetized) permitted in 1200 character blocks. Control of Transfers HIP A hardware handshaking routine prepares transfers. Sending side puts control informa tion in status registers accessed by both sides; receiving side prepares for transfer on the basis of the status information. Logic is provided to resolve contention for channel use. LIP Asynchronous control frames prepare transfers. All frames contain control information; information frames contain data as well. Frames are sequenced and acknowledged. Logic provided to resolve contention for channel use. ASYNC TIP Input messages preferred. Typeahead mode saves interrupted output messages until the unsolicited input is completed and sent to the host. No acknowledgment in either d i r e c ti o n . S p e c i a l c h a r a c te r p r o c e s s i n g a v a i l a b l e o n i n p u t e x c e p t i n tr a n s p a r e n t data mode. Input characters echoed on the terminal display without TIP or host participation. Mode 4 TIP N P U i n i t i a t e s t r a n s f e r s , t e r m i n a l s r e s p o n d t h r o u g h c l u s t e r c o n t r o l l e r. I f t e r m i n a l h a s an upline message, it notifies the controller which then responds to requests from the NPU (polling) to read data. Terminals in clusters are handled on a strict rotation basis, except Mode 4A printers and card readers subordinated to console (interactive and batch devices cannot be active at the same time). Special character processing for interactive input data. Print messages (PMs) interrupt printer output; host is noti fied so that it can send an interactive message to the terminal before printer output resumes. • 2-14 60471400 G TABLE 2-4. INTERFACE PACKAGE SOFTWARE CHARACTERISTICS (Contd) Characteristic Interface Package Description Control of Transfers (Contd) BSC TIP Both ends of line bid for line use (logic is provided to resolve simultaneous requests). Set up and acknowledgment blocks sent in both directions. Input has precedence over output and can suspend output until input completes. Interactive transfers have precedence over batch transfers. Handles print messages as for Mode 4 TIP. HASP TIP Each terminal has its own data stream. Permission to use the stream is granted by the HASP workstation. Upline, HASP workstation determines device to be used. Set up and acknowledgment blocks sent in both directions. Special character processing for interactive input data. Idle blocks are exchanged when lines not sending data/control information. Handles print messages as for Mode 4 TIP. X.25 TIP (level 2) Asynchronous control frames prepare transfers. All frames contain control information; information frames contain data as well. Frames are sequenced and acknowledged. Logic provided to resolve contention for channel use. Data Movement HIP Direct-memory-access (DMA) data transfers through the host coupler, asynchronous. LIP Sending side puts data into subblocks and packs subblocks into frames. Frames are numbered. Receiving side unpacks frames and restores data to block format. Transfers are bidirectional and synchronous within the frames. ASYNC TIP Data is transferred one character at a time; parity is optional. TIP packs input char acters into a block. Block is sent upline when block delimiter is received. When a d o w n l i n e l i n e i s r e a d y f o r t r a n s f e r, e n t i r e l o g i c a l l i n e i s o u t p u t w i t h o u t i n t e r r u p t i o n unless unsolicited input occurs. Mode 4 TIP Data is transferred to/from Mode 4 controller in Mode 4 blocks. Controller routes data to/from terminals. TIP supplies downline formatting for interactive blocks, and con verts interactive input into IVT blocks. TIP breaks PRUBs into output blocks, and assembles input batch data into PRUBs. Trailing blank truncation for card input de vices. Accounting data for batch devices is generated both upline and downline. BSC TIP Data is transferred to/from BSC controller in blocks. BSC control function routes data to/from terminals. TIP supplies downline formatting for interactive blocks, converts upline interactive data to IVT blocks. TIP breaks PRUBs into output blocks, and assem bles input batch data into PRUBs. Accounting data for batch devices is generated both upline and downline. HASP TIP Data is transferred to/from the HASP workstation in HASP blocks. Upline, several ter minals can interleave records in a single HASP block. HASP TIP sorts upline records by connections. TIP moves an interactive record into an IVT block; TIP assembles batch records into full PRUBs (exception: partially full PRUBs contain end of input). Down line HASP blocks have a single record. PRUBs may be broken into several HASP blocks. In non-transparent mode, interactive data is translated between EBCDIC and ASCII in both directions, and batch data is translated between EBCDIC and display code in both directions. Downline data compression is supplied for batch devices; upline data expansion is performed on compressed data. Accounting data for batch devices is generated both upline and downline. X.25 TIP Downline, subTIP handles conversion from network blocks to packets. Packet level (3) provides groups of packets for level 2. Level 2 frames packets (packets from different channels are not mixed in one frame) and transmits to PDN. PDN/PAD access is responsi ble for dismantling frames and packets and moving data one character at a time to ter minals. Reverse process converts terminal data to IVT blocks. 60471400 G Transfers are 2-15 • TABLE 2-4. INTERFACE PACKAGE SOFTWARE CHARACTERISTICS (Contd) Characteristic Interface Package Description Error Handling HIP Keep-alive messages assure that channel is available. Recoverable errors are retried (data parity errors, hardware timeouts, abnormal termination of transfer) until host stops NPU and reloads. Irrecoverable errors (memory parity error, memory protect error, or broken chain of buffers) stop NPU. Host then reloads NPU. Block sequencing is provided by the agreement between host application and terminal. LIP An exchange of receive-ready messages assures that the channel is available. Frames are rejected for noise (bad CRC-16 check), for bad command/response format, for time outs, or for being out of sequence. In all cases, the bad frame and all succeeding frames are retransmitted. ASYNC TIP Input with bad parity marked but accepted. No retransmission in either direction. Mode 4 TIP TIP handles timeouts, protocol errors, bad commands, parity errors, and transmission errors reported by the receiving terminal. In all cases, retransmission is attempted. If this fails, message movement stops, but attempt is made to restart normal transfers. BSC TIP For upline data, the TIP recognizes timeouts, bad acknowledgments, and illegal formats. Bad blocks are reported to the sender by a NAK. For downline data, the TIP recognizes a transmission failure when it receives a NAK or detects a transmission timeout. Attempts to retransmit data are made unless an error threshold is exceeded. In that case, transmissions are aborted. Bad autorecognition data causes a message to be sent to the terminal. HASP TIP For upline data, the TIP recognizes timeouts, bad control commands, CRC-16 errors, and illegal HASP block formats. These are reported to the sender with a NAK block. For downline data, the TIP recognizes a transmission failure when it receives a NAK block. In all cases, an attempt is made to retransmit data. If this fails, line is marked inoperative and the host is informed. X.25 TIP At packet level, detecting a missing packet causes a channel reset. Packets traveling in the same direction are discarded; no action is taken for data traveling in the oppo site direction. At the frame level, frames are retained until acknowledged. Out-of-sequence errors cause all unacknowledged frames to be retransmitted. Other errors (bad commands/ responses, overlength frames, wrong sequence number) cause the link to reset. Follow ing resetting, all unacknowledged frames are retransmitted. In case the link is in an unknown state, it is disconnected and then reconnected. In this case, all frames are discarded at disconnect time. Flow Control and Regulation Host Input to host is controlled by host resource allocation. Host rejects long blocks (size greater than 256 bytes) first, then shorter blocks. HIP H o s t o u t p u t : C o n t r o l l e d b y a v a i l a b i l i t y o f N P U b u ff e r s . L o w p r i o r i t y t r a n s f e r s a r e r e g u l a t e d fi r s t , t h e n h i g h p r i o r i t y t r a n s f e r s , a n d fi n a l l y s e r v i c e m e s s a g e s . I n e x treme cases, all output from the host is rejected. LIP L o w p r i o r i t y t r a f fi c r e g u l a t e d fi r s t i f t h e r e i s a s h o r t a g e o f N P U b u ff e r s ; t h e n h i g h p r i o r i t y t r a f fi c r e g u l a t e d . S e n d i n g L I P r e s p o n d s t o r e c e i v i n g L I P ' s r e q u e s t s f o r regulation. ASYNC TIP I n p u t t r a f fi c i s r e j e c t e d i f t h e r e i s a s h o r t a g e o f b u ff e r s o r i f h o s t i s u n a v a i l a b l e . A canned message notifies the terminal user of regulation; another message indicates when the host is again available. • 2-16 60471400 G TABLE 2-4. INTERFACE PACKAGE SOFTWARE CHARACTERISTICS (Contd) Characteristic Interface Package Description Flow Control and Regulation (Contd) Mode 4 TIP I n p u t t r a f fi c : T I P s t o p s p o l l i n g f o r d a t a i f t h e r e i s a s h o r t a g e o f N P U b u ff e r s o r i f host is unavailable. Keyboard is locked when the send signal is entered from terminal so operator cannot attempt additional input. Terminals again polled for the data when regulation ends. O u t p u t t r a f fi c s e n t w i t h o u t r e g u l a t i o n . BSC TIP TIP stops input by sending WACK blocks (if the input has started when regulation condi tions start) or by sending an EOT (if regulation conditions exist when terminal starts input). HASP TIP TIP stops all input by sending a wait signal on every active data stream if shortage of NPU buffers or host is unavailable. If a terminal requests that no more data be sent on the data stream, NPU passes message to host. Other terminals continue to receive dat a. X.25 TIP Both input and output are controlled on three levels. I n p u t , s u b T I P l e v e l : r e g u l a t e d b y h o s t ' s a b i l i t y t o a c c e p t b l o c k s o r b y b u ff e r s h o r t age. SubTIP requests level 3 not to send additional packets. When shortage ends, sub TIP restarts the packet level. Input, level 3: stops acknowledging packets if requested to stop by subTIP. PDN stops sending packets when n packets are unacknowledged. I n p u t , l i n k l e v e l : i f b u ff e r s a r e u n a v a i l a b l e , l e v e l 2 d o e s n o t a c k n o w l e d g e frames. PDN ceases sending frames when n frames (n is a subscription option) are unacknowl edged; these unacknowledged frames are acknowledged when buffers are again available. Output, link level: level 2 ceases sending frames when n frames are unacknowledged; starts sending frames again when there are less than n unacknowledged frames. Requests are made to level 3 for information blocks (packets) when the level 2 output queue has room. Output, packet level: packet level flow is controlled by PDN failing to acknowledge packets. When the limit (n) is reached, level 3 ceases to send packets and does not request more data for the subTIP. Output, PAD access level: PAD subTIP sends data blocks on request from level 3. work blocks are acknowledged when data is sent to level 3. Net- Autorecognition ASYNC TIP Provided for terminals operating on lines up to 1200 baud. Includes line rate and code set. Mode 4 TIP Autorecognition is provided for cluster address, for code type, and for mode type (4A or 4C). BSC TIP Sign-on blocks (*/C0NFIG card) are used for autorecognition. HASP TIP Sign-on blocks (*/CONFIG card) are used for autorecognition. X.25 TIP Autorecognition does not apply. 60471400 G 2-17 • /tfG^^v TABLE 2-4. INTERFACE PACKAGE SOFTWARE CHARACTERISTICS (Contd) Characteristic Interface Package Description Autoinputt ASYNC TIP Supported Mode 4 TIP Supported BSC TIP Supported HASP TIP Supported X.25 TIP Supported •Saving the first 20 characters of the output message and appending the input response up to the length of a logical line. STATUS WORD TRANSFERS The control word is set indicating that one of the statustype registers has been loaded and can be accessed by the unit on the other side of the coupler. The unit interprets the control word, reads the status, and acts on the status information. The register used for regulation has three status values: transmit all messages to the NPU (buffer level is above threshold, so that buffers can be assigned to receive data as rapidly as the host can transmit data); do not transmit messages for batch-type devices (buffer availability is critical, so the heavy demands of chained buffers for batchtype messages pose a potential hazard of exhausting the NPU data buffer supply—which causes an unconditional NPU halt); and transmit-only service messages (neither batch nor interactive data transfers are allowed; the only transfers remaining are command/network coordination service mes sages—all service messages are short and can fit in a single data buffer of the largest size). Note that all messages use the direct memory access (DMA) channel of the NPU. DATA TRANSFERS For downline transfers, the NPU has assigned the next data buffer, set up buffer chaining (if necessary), and will receive sufficient information in the data block header to switch the block to the proper internal handling or terminal/line/TIP. For upline transfers, the full message (which may be in several chained blocks) is ready. The NPU makes the address of the first block in the chain available. As the blocks are transferred, the chaining bit is inspected. If set, when one block is transferred, the starting address of the buffer holding the next block is set in the address register. No attempt is made to resend transmissions of less than block length. A bad block is rejected in its entirety; with it, the message is rejected. For this reason an entire message is retransmitted regardless of the number of blocks com posing it. The message handlers on both sides of the coupler (that is, the NAM in the host and the HIP in the NPU) are responsible for retaining messages until they are acknowl edged as received. LINK INTERFACE PACKAGE The link interface package (LIP) module handles transmis sion and reception on both ends of a trunk; therefore, a copy of the LIP must exist in both the local and the remote NPU. The LIP implements a class of the Control Data Corporation Control Procedure (CDCCP) for information interchange. The specific protocol implemented is similar to ISO HDLC class: a symmetrical, asynchronous response mode (ACM), with basic numbering range having two-way simultaneous reject and initialization options (SAB, 2, 5). Two major types of operations are handled by the LIP: loading/dumping the remote NPU, and processing data transmissions over the trunk. Data message transmissions across the trunk use a unit called a trunk transmission frame (TTF or frame). There are three types of frames: • unnumbered frames which establish the basic trans mission states between the two nodes (such as utilization, disconnect, command rejected) Handling of the block protocol on both sides of the coupler will cause generation of acknowledgment service messages. This is not a HIP function on the NPU side. • supervisory frames that establish whether trans mission/reception is currently possible (ready for data, not ready for data, or rejected last data sent) • information frames used to transmit message data; this class of frames includes frames that are carrying service messages Since the DMA/PPU buffer channel is half-duplex (data can be sent in only one direction at a time), contention for channel use is normally resolved in favor of outputting blocks from the PPU. However, following this transfer, the protocol provides a 10-millisecond period during which the NPU can request channel use without the PPU contending for channel use. Both frame size and data block size are customization time selections. The information frames themselves are com posed of onerelated or moretosubblocks. Each subblock is the a buffer of information a single message so that frame may be considered as a pocket of information subblocks containing one or more message parts for one or more terminals. 2-18 60471400 G Use of overlay areas is controlled by the host, using information from the NPU. During normal processing, the NPU uses all of main memory. However, for rarely used operations such as initialization, a portion of the main memory which is normally reserved for assignable buffers is . instead reserved for special programs. These programs are temporarily overlaid in memory and are executed on-line. Terminal message data is always in virtual terminal format when it is placed in a frame; that is, upline data must be processed by a TIP in the remote NPU before it is sent over the trunk, and downline data is not processed by a TIP until after it is transmitted over the trunk. On input (in either the local or the remote NPU), data from the multiplex subsystem which services the trunk can be rejected if the number of available buffers has dropped to the threshold level. First low-priority traffic is rejected, then high-priority traffic. Supervisory frames are not included in this priority scheme. These frames contain some command/status information, but do not include most service message instructions which are treated as high priority. Thus, some service messages can be rejected while other command/status information still passes over the trunk. TRANSMISSION ASSURANCE Either end of the link may initiate data transmission when conditions warrant. Once the interfacing LIPs have estab lished the normal mode, data transmission can begin. To understand the LIP requirements for message processing, it must be remembered that a remote NPU has no coupler to the host, and therefore no HIP. Terminal data passes through the multiplexer twice: once in terminal format as it passes between the terminal and the NPU, and once in r/T or PRU as it passes between local and remote NPUs. Upline data in the remote NPU is demultiplexed and passed to the appropriate TIP for conversion to IVT or PRU format. Completed, converted messages are passed to the LIP for framing and then passed through the multiplex subsystem, over the trunk to the local NPU. Trunk transmission rate is up to 19200 bps. In this local NPU, upline data from the trunk is received by the LIP and reconstructed into a message in (chained) buffers. Then it is passed to the HIP for transmission to the host. Downline data is taken from a trunk message data buffer, assembled into frame format by the LLP and sent to the remote NPU. Once it is demultiplexed by the LIP/multiplex subsystem, it is in r/T or PRU format and is ready to be passed to the appropriate TIP for conversion to terminal format and processing. LOADING/DUMPING OF REMOTE NPU The local NPU must process the load/dump operation in its overlay area. The program information is transmitted to/from the local NPU overlay area in block form. The local LIP passes the programs (downline) and receives main memory contents (upline) in frame format. The remote NPU LIP is responsible for stripping the frame information from the downline subblocks and loading these subblocks (parts of programs) at the location indicated by the host. For dumping, the LIP is responsible for placing the main memory contents, starting at the address indicated by the host, into frames and sending the frames to the local NPU. Configuring the remote NPU is handled by service messages, as in the case of configuring a local NPU. The service messages are transmitted across the trunk in the same manner as any other message data. TRUNK TRANSMISSION PRIORITIES AND REGULATION A high or low priority is assigned to each frame. This is the same priority scheme discussed previously for NPU regula tion: high priority is associated with interactive terminals and low priority is associated with batch terminals. Each time a new frame can be transmitted the LIP scans the high and low priority queues. If high priority data is waiting, it is always transmitted ahead of low priority data. 60471400 G The CDCCP protocol requires that each frame be acknowl edged. Since several frames may have been transmitted before an acknowledgment for a given frame is generated, all frames up to and including the last properly acknowl edged frame are retransmitted. No frame is released from the sending NPU until it is properly acknowledged. Frame checking is provided by a cyclic redundancy checksum (CRC) which is generated by the sending LIP and included at the end of each frame. TERMINAL INTERFACE PACKAGES A terminal interface package (TIP) interfaces the terminal data (messages) to the network. The TIP's interface to the terminal or a controlling device is through the hardware, firmware, and software of the multiplex subsystem. The TIP's interface to the system is through line control blocks (LCBs) and terminal control blocks (TCBs). A user interface allows the terminal operator to change an interactive terminal's parameters (such as page width and length, cancel and break characters, and others). Each TIP has the general ability to handle the protocol for its terminal type. Specialized additional information for any real terminals that do not fit the basic TIP processing pattern is contained in the TCB for that terminal. This gives the standard TIPs sufficient flexibility to handle many terminal variations. A TIP includes both hardware and software elements. In interfacing with the communications network, the principal concerns of the TIP are mode control and error control with most of the software elements devoted to exception processing. Batch and interactive protocols are treated differently: • For interactive output in TIPs which support only interactive devices, TVT data is queued to the TIP which converts format and code and then passes the information directly to the terminal (ASYNC TIP) or to another network (X.25 TIP). • For other protocols, downline rVT blocks or PRUBs are transformed into terminal transmission blocks and are then returned to the BIP. The BIP requeues the blocks to the terminals in interactive or batch queues. The TIPs pass the blocks to the terminals through the multiplex subsystem. • One upline TIP (ASYNC) converts input data directly into IVT blocks and passes this to the host. Other TIPs have multistage upline processing. During the first stage, data is collected. During later stages data is formatted in PRUBs or IVT blocks as appropriate. At the same time, data on channels which service more than one device have the data segregated by connection number. 2-19 Methods are supplied for either the terminal user or the host to interrupt messages. ASYNC TIP The asynchronous TIP supports dedicated and dial-up asynchronous lines servicing teletypewriter-like terminals operating at standard rates in the range 110 to S600 baud. The TIP supports the following codes: ASCII, Tele typewriter-paired APL ASCII, Bit-paired APL ASCII, External BCD, External BCD APL, Correspondence, and Correspondence APL. Transparent mode is also available. The TIP provides software support for teletypewriters, for 2741 terminals, and for teletypewriter-compatible CRTs operating in an interactive mode with host applications programs. There is a build-time option that excludes support of the IBM 2741 terminals and terminals which use APL code. This option makes a considerable amount of additional NPU memory available for message processing. If the user attempts to use APL features that were not included in the build, a rejection message is generated by CCP. The interface between the host and the TIP is handled by the interactive virtual terminal. The TIP handles the interface to the terminal through the multiplex subsystem. The Async TIP supports a terminal-to-virtual transform for seven types of terminals. To expand the usefulness of this TIP, a method is provided for the user at a terminal or a connected application to vary parameters and operating modes for any of the seven terminal types. This provides terminals which differ in detail from the terminal types. The terminals explicitly supported by the Async TIP and the seven associated classes are: Terminal Class 1 2 4 5 6 7 8 Manufacturer Teletype CDC IBM Teletype Hazeltine CDC Tektronix Model Number M33, 35, 37, 38 713-10 2741 M40/2 2000 LIAT 751, 752, 756 4014 Line types supported are: • dedicated or dial-up • two- or four-wire • full-duplex The terminal type is supplied by the user at the terminal or by the host software, as are any further variable parameters or modes. The TIP is prepared to receive input at all times (type ahead mode); therefore, the TIP attempts to deliver output whenever available, unless input is currently active, a page-wait condition exists, or an auto-input block has been output and the reply information (which must be placed in the output block) has not been returned with the requested information. When input is detected during an output cycle, the TIP suspends output operation. Later, this output is sent from the beginning of the logical line, unless the input was one of the user break commands. 2-20 IBM 2741 keyboards are locked after each logical line is input and the TIP does not unlock the keyboard until one or more messages have been output. Therefore, if an operator at a 2741 terminal wishes to use the type ahead mode when the keyboard is locked, he must press the ATTN key to unlock the keyboard so that the type ahead data can be entered. Operators at all terminals have the responsibility for not using the type ahead feature if either auto-input or special edit mode (see appendix H) are currently being used. All input and output in the character mode is transformed between the terminal and virtual terminal characteristics (code conversions, format effectors, format effector delays, line delimiters, special character recognitions, etc.). The transparent mode is available to suppress this transform where desired. Autorecognition allows the TIP to determine both the terminal's transmission rate (if the rate is between 110 and 1200 baud) and the terminal's current code set. To activate the autorecognition function, the user at the terminal presses the carriage return key after the connection is established. This generates the appropriate character at the terminal, which is placed on the line at the terminal's normal line speed. The TIP samples the line at 800 baud. Depending on the speed of the line, one or more different characters will be sensed by the TIP. The TIP uses the received character to detect the true transmission speed of the terminal. After the TIP resets the communications line adapter to the correct baud rate, the TIP sends the terminal two line feeds to inform the operator that character set recognition can begin. The operator responds by pressing the ) key and then a carriage return (ASCII terminal operators have the option of pressing only the carriage return). If the TIP detects a terminal using a code set that is supported by the TIP but not available in the current variant, the terminal receives the message, "UNSUPPORTED CODE SET." This message is sent in the terminal's code set. After determining the code set, the TIP sends two more line feeds to the terminal to inform the operator that autorecognition is complete. At the same time, the TIP sends a line operational service message to the host. This message contains the line speed and terminal character set. See appendix C of the CCP System Programmer's Reference Manual. s^S. The user has one minute to enter each of the requested responses. If he fails to do so in this period, or if the code set is unsupported in the CCP variant, the line 4s disconnected. Any terminal operating at a speed greater than 1200 baud must be dialed into a port where the communications line adapter is designed to operate at that particular speed. Input Processing The basic input is the logical line (data followed by line feed/carriage return) or a physical line width of the device (number of characters in the line; for instance an 80-character line width on the CRT). Output is allowed only when input processing has a pause longer than 200 milliseconds following a line end. Output is interrupted if input starts during an output operation. 60471400 G 4&?Sk. J t ^ f fi n s Parity is checked and the parity bit is stripped from the data character. Certain other control characters are discarded from the date (e.g., nulls). The input data in whatever form is converted to 7-bit ASCII form unless transparent mode has been selected. Backspacing control is provided. Input characters within the current line which are corrected by subsequent backspacing are discarded. The operator can cancel the current line by entering the cancel character (see appendix H for definition of the character). The TIP discards the line and confirms the change by sending a *DEL* message to the operator. Note that if the terminal is in special edit mode (appendix H), backspace, linefeed, and cancel characters are sent to the host as data; the TIP does not perform the control action which these characters usually cause. /§ms Auto-input is provided. The output block is held while the terminal operator generates input data in response to output data. Then the first 20 characters of the output data are chained to the front of the input block and all of this data is returned to the host as the new input data stream. Further outputs are inhibited until the responsive input data is generated. The operator may stop the auto-input mode. MODE 4 TIP The Mode 4 TIP interfaces devices using Mode 4A or 4C protocols to the network. Not all features of the Mode 4 protocols nor all features of supported terminals are used. A typical Mode 4 device would be the card reader, printer, keyboard, and CRT display of a CDC 200 user terminal (UT). Mode 4 devices that have card readers and printers as optional devices are considered to be 200 UTs even though they may actually be CDC 731, 732, or 734 terminals. Table 2-5 shows the Mode 4 equipment supported by the TIP and the mode and associates each device with batch or interactive operation. Some variations exist in the terminology associated with Mode 4 devices. Table 2-6 presents the equivalent terms. TABLE 2-5. MODE 4 COMPONENTS Terminals Type 4A For keyboard inputs, the TIP provides logic to process line feed, carriage return, cancel, start of text, and upper/ lowercase shift. Paper tape input is supported. ID Type ID 200UT CRT & Keyboard Printer Card Reader Interactive Batch Batch 731 CRT & Keyboard Printer Card Reader Interactive Batch Batch 732 CRT & Keyboard Printer Card Reader Interactive Batch Batch 734 CRT & Keyboard Printer Card Reader Interactive Batch Batch 711 CRT & Keyboard Interactive 714 CRT & Keyboard Printer Interactive Batch Output Processing y^s A single data block may contain several logical lines. The TIP fills the lines with nulls as required. Paging format effectors (FEs) are supported, as are upper/lowercase shifts. The TIP converts the ASCII terminal code from the r/T character set to the character set of the terminal. A page-wait option feature for CRT output allows the user to view the display as long as he wishes. A page-over feature warns the viewer that there is more data in the message even though the current page is not full. Paper tape output is supported. 4C Devices User Interface The TIP supports the standard message input and output formats for TTY devices. The TIP also allows the operator at an interactive device to change some parameters during IVT processing. The commands and their effects are given in appendix H. The TIP is insensitive to line speeds; it supports synchronous lines operating at rates up to 19.2K bps. Lines may be dedicated (with or without a transceiver) or switched (dial-up) with a modem. Lines are considered to be half-duplex; that is, the TIP is either transmitting to the line or receiving from the line, but not both simultaneously. TABLE 2-6. MODE 4 TERMINOLOGY Nomenclature Used in this Manual Mode 4A Nomenclature Mode 4C Nomenclature NPU data source control station cluster address site address station address cluster controller equipment controller station terminal address station address device address 60471400 G 2-21 Each line can have more than one cluster of equipment and each equipment cluster can have more than one terminal. Lines with multiple clusters must be dedicated. Where multiple terminals are on a line, the TIP services each terminal in sequential order without priority. All Mode 4 terminals can have both interactive and batch devices attached. The Mode 4 TIP supports remote batch terminals as separate but dependent devices. The dependencies are reported to the host on demand when a conflict occurs. Mode 4 Autorecognition The TIP performs autorecognition when requested by the host. This procedure determines the code set of the terminal (ASCII or external BCD) and mode (Mode 4A or 4C). Autorecognition causes the TIP to return a service message to the host which contains the following information: terminal type cluster address terminal address device type Multicluster autorecognition is not supported. Autorecognition first determines the cluster address. A poll message allows the caller to hear an audible tone. The modem is allowed time to stabilize after the Modem Data switch is depressed. To complete autorecognition during dial-up procedures, the remote operator presses the SEND key on at least one of the displays in the cluster. This allows code set recognition through the use of an escape code in a read message. If the terminal uses BCD code, autorecognition is complete at this point. If the terminal uses ASCII code, the TIP sends a configuration poll. An error response or no response indicates the terminal is Mode 4A. A read response indicates the terminal is Mode 4C. A line status (operational) service message is sent to the host to complete autorecognition. Mode 4 Data Handling Interactive data is passed to/from the IVT interface; batch data is passed to/from the PRU interface. • Input data: the TIP polls the terminal to collect data that is ready to be input. The host requests polling, but the TIP controls the actual polling for data. A further throttling of input can occur if the NPU is regulating data input as a result of a low buffer availability condition. • Output data: the TIP delivers interactive output to the display and batch output to a printer. Output is delayed if the printer is not ready. • Error processing: the TIP performs recovery for line or terminal errors. If immediate recovery is not possible, the TIP reports the error to the host. 2-22 Host Interface rVT or PRU blocks are used at the host interface. The TIP processes each line as an independent data channel. Devices on a terminal are checked for data in the sequence the devices were configured. The card reader and printer of the 200 UT are treated as separate terminals, but the console must be configured before the card reader and printer can be configured. The terminal status of Mode 4C terminals is solicited before the TIP services devices on the terminal. The terminal returns the status of all the connected devices when requested. Console status indicates whether a read message is requested. Printer status indicates ready or busy condition. Status is saved in the TCB and is used to determine the action to be taken when subsequent events occur. IVT Interface The IVT interface to the Mode 4 TIP supports the CRT and keyboard which are collectively referenced as one device, the console. Selecting the Mode 4 Console Console activity is started by a start input command, console output data, or an input batch interrupt for the console. Console activity remains active and the TIP polls for input. Upon arrival of batch start or resume commands, console activity ceases and batch activity commences. When batch activity ceases due to normal processing of end of data and no further data is present, the TIP sends a clear write to the console and starts polling the console for input. For the Mode 4A terminals, using the console interrupts the card reader connection and the printer connection. The TIP inhibits any further batch input or output activity until it receives a resume type of command from the host. Mode 4 Interactive Input When a start input command is issued to a Mode 4A terminal, the cursor is moved to the left-most character position. This command also clears the terminal transmission buffer of any previous card or print block. Polling for input continues until the terminal is deleted from the system configuration, an error occurs, buffer regulation occurs, logical link regulation occurs, or a stop input command is received. A stop (STP) block is sent whenever a communication error is detected; a start (STRT) block is subsequently sent when the error condition disappears. The TIP polls the Mode 4C console for input only when a read request is indicated in the terminal's status. It is possible for parts of a message to repeat on a 711 terminal in certain types of error conditions. The operator can cancel part of a line by using the CN character (see appendix H). If this capability is used, the TIP confirms the cancellation by sending a *DEL* message to the interactive device. See appendix H for the alterations to the IVT interface which may be entered from a terminal. 60471400 G yaVuZOt^S Interactive input from the console can include multiple logical lines. The lines are separated by CRs. The TIP allows autoinput. The first 20 characters of the autoinput message from the host are saved and are prefixed to the reply from the console. The TIP supports transparent input, but this input applies only to the first message following transparent selection. The Mode 4 frame control characters are removed, but no other translation occurs. The cursor is not repositioned to the left margin following each input, and the keyboard is not unlocked. Since any further polling would result in retransmission of previous data, polling ceases. The host must request that polling resume by sending output or a start input command. The TIP removes any E2 or E3 codes from Mode 4A cluster transparent data. The data is processed without transforms. E-codes and MTIs for Mode 4 protocol are described in the CCP System Programmer's Reference Manual. An operator at a Mode 4 console can change the following r/T parameters for his terminal: • Terminal class • Page width and page length • The characters used for cancel, r/T control, and user breaks one and two • Input device for transparent mode (Mode 4C only) • Page wait feature The operator can also send a message to the NOP console. Each IVT command (including the message to the NOP console) is preceded by the control character and followed by a carriage return or an end of message. Multiple line inputs can have an IVT command only in the first line. If the IVT command in a multiline input is a request for transparent input, transparency will not be applied to the current set of input lines, but will be applied to the next message. Mode 4 Interactive Output The cursor is returned to the left margin following each output of a logical line. For a Mode 4A console, any ASCII control character is replaced with a blank, and lower case characters are folded into upper case. For a Mode 4C console, a full 128 ASCII character set is supported. The format effector transforms performed by the TIP for both interactive and batch devices is given in the CCP System Programmer's Reference Manual. The IVT transform is not performed on transparent output data. However, the Mode 4 frame control is added to the data, but no code or format effector conversion is performed. The parity bit for each character is also added before the data reaches the line. Autoinput and page wait are supported for transparent data. However, page wait occurs following each MSG block only. The console operator requests a message break by using either the user break one or two character. The page wait feature assures that output is delivered at a readable rate. Data from the host is displayed on the screen until the end of page is reached. Page turning is accomplished whenever the console operator responds with a request for the next data display. Card Reader Interface The Mode 4A card reader is activated by sending a command to the TIP to start accepting input. The TIP polls the card reader for data. Upline data is translated and trailing spaces are stripped to the first even character boundary following the last data character. The data is stored in buffers which are subsequently passed to the BIP. The BIP builds the PRUBs to be transmitted to the host. The TIP indicates end of card in standard host file format. If the last non-blank character is on an odd character boundary, one blank is inserted. Two to ten binary zeros are then added to insure that the host can decode end of card and also to insure that the data stream ends on a modulo ten character boundary. If the last data character of the card is a colon in the 64 character set, the TIP inserts one or two spaces. The TIP counts each card. Polling continues until an abort input occurs, a slipped card is detected, a console interrupt occurs, the card reader becomes not ready, or an EOI card is read (6, 7, 8, 9 punch in column 1 or /*EOI in columns 1-5). The TIP handles these events as follows: • Abort input: card reading stops and accounting data is sent to the host. If the printer is not active, the TIP polls the console. If the printer is active, the cluster remains in batch mode. Card reader input restarts upon receipt of a start input command from the host. • Slipped card: host is informed with an input stopped, card slip command. • Card reader not ready and last card read not an EOI card: the TIP stops polling and notifies the host. Polling resumes when the TIP receives another start input command from the host. • Console interrupt: the TIP reports that input is stopped and sends a batch interrupt to the host. Card reading resumes when the host sends a resume input command. • EOR card read: TIP checks columns 2/3 or 6/7 for level number and adds this information to the PRUB. Since an EOI or EOR card ends a PRUB, it is possible for a short PRUB to be sent to the host. • EOI card read: the current data, including accounting data (card count), is sent to the BIP. The BIP passes the data to the host in a PRUB and the TIP continues polling. If an EOI is read and the card reader is found to be not ready (empty), the TIP notifies the host that the card reader is at end of a data stream. To get more card data, the host sends another start input command to the TIP. jSv, 60471400 G 2-23 • Printer Interface Print Message The printer is activated by sending downline PRUB data to the BIP. The BIP passes the PRUB to the TIP. The TIP transforms the PRUB into transmission blocks (blocks of data that fit the particular printer buffer being addressed) and returns it to the BIP. The BIP adds the transmission blocks to the TIP's queue and, if necessary, notifies the TIP that data is ready for the printer. If a print message is received (TIP detects PM at the beginning of a print line), the TIP builds a separate PM message and sends it to the BIP, which in turn sends it to the host. This allows the host to send messages to the console before continuing the printed output. When the host sends an interrupt resume command, the TIP restarts printing with the print line following the PM line. As the TIP sends blocks to the printer, the BIP monitors the queue. When necessary, the BIP notifies the host. The host can send another PRUB if one is available. Mode 4 Error Handling When Mode 4A printing has completed and the accounting message has been generated, the TIP returns to polling of the console for inout if the card reader is not active. Otherwise, the terminal remains in batch mode. When the TIP detects a failure that cannot be corrected by a set number of retry attempts, the terminal is reported as failed and long-term error recovery begins. For Mode 4A terminals, failure of one device causes failure of all devices on the cluster. Skipping Printer Data Recovery attempts occur every 10 seconds during long-term error recovery. Interrupt commands from the host can cause the TIP to skip a specified portion of the printer data. The point in the data stream where the skip is to end is marked. After receiving the interrupt, the TIP continues to receive data, but discards all of it until the end skip marker is received. Then the TIP sends accounting data to the host. Printer Busy Busy status permits the operator to stop printing, to inspect the printed output, and to resume printing without console input. If a printer is ready but busy, the TIP holds data and periodically checks status. When the printer is again ready, the TIP resumes printing. The host is not notified. Since some Mode 4A printers do not always report printer not ready status, a different method is used. To interrupt printing or to generate a ready status, the operator presses the interrupt key. This toggles the printer between ready and busy status. Mode 4C printer status is determined by the terminal status request. Printer not ready condition is not reported to the host; printing automatically resumes when the printer becomes ready. In no case does the remote terminal operator receive a console message indicating that the printer is not ready. The printer should normally be left in the ready state to avoid unnecessary recovery processing. BINARY SYNCHRONOUS COMMUNICATIONS (BSC) TIP The BSC TIP provides data interchange between a host application program and a remote IBM 2780, 3780 or compatible batch terminal. In addition to the terminal's batch capabilities, BSC terminals simulate an interactive console device by sending interactive input from the card reader and receiving interactive output on the line printer. Exchange of information between the NPU and a terminal uses the point-to-point binary synchronous communications protocol with contention resolution (not all features of that protocol are supported). The NPU converts BSC batch data to/from PRUB format, and BSC interactive data to/from IVT blocks. The normal code of a 2780/3780 is EBCDIC. Provision is made for transmitting to or receiving from these terminals in transparent mode. 2780 and 3780 have unique subTIP types. For the purposes of the application interface, the 2780 and the 3780 terminals have exactly the same attributes as HASP terminals. BSC terminals can be attached to an NPU through dedicated or dial-up lines. The TIP is insensitive to line speeds; it supports synchronous lines operating at speeds up to 19200 bps. All lines are treated as half-duplex, that is, the TIP is either transmitting or receiving but not both simultaneously. Each BSC line is connected to one 2780 or 3780 terminal. A terminal consists of: Page Eject • A required card reader which sends interactive as well as batch input data Two types of Mode 4C printers are supported: impact and nonimpact. • A required line printer which receives interactive as well as batch output data The impact printer supports page eject and is controlled by vertical carriage control characters. • An optional card punch The nonimpact printer does not support page eject, so the TIP formats a virtual page image. The number of lines on the page is specified when the device is configured. Sixty lines is the default page length; six lines separate pages. Therefore, the TIP varies the number of line feeds it generates to support page eject. • 2-24 yzMgfigK Terminal Device Selection The following rules apply to terminal device selection: • Input has precedence over output • Interactive data has precedence over batch data 60471400 G y^S^V Batch card reader input is allowed if the simulated console input is not active. Batch output can be interrupted to accept card reader input; the interrupted output is resumed when input ends. Card reader input (either batch or interactive) is not interruptable. The 3780 non-transparent characteristics are the same as the 2780 non-transparent characteristics except: A new batch output can be started if no input is active and no simulated console data is queued. If the terminal user interrupts to send card reader input, the batch output is suspended. Batch output restarts when an upline end of transmission (EOT) is received, and continues until the end of job (EOJ) before any new batch output can be started. There is one exception: a print message (PM). Print messages are explained in the Mode 4 TIP description. • For multiple jobs, the last job must be input with the EOF toggle switch on. o Job cannot be terminated by an ETX in column 80 of last card. • Trailing blanks are truncated • Data can be compressed • Transmission block is limited by character count (usually 512) rather than record count <*\ CHARACTER SETS AND CODE SETS A character set differs from a code set. A character set is a set of graphic and/or control characters. A code set is a set of codes used to represent each character within a character set. Characters exist outside the computer system and communication network; codes are received, stored, retrieved, and transmitted within the computer system and network. GRAPHIC AND CONTROL CHARACTERS A graphic character can be displayed at a terminal or printed by a line printer. Examples of graphic characters are the characters A through Z, a blank, and the digits 0 through 9. A control character initiates, modifies, or stops a control operation. An example of a control character is the backspace character, which moves the terminal carriage or cursor back one space. Although a control character is not a graphic character, some terminals can produce a graphic representation when they receive a control character. CODED AND BINARY CHARACTER DATA Character codes can be interpreted as coded character data or as binary character data. Coded character data is converted from one code set representation to another as it enters or leaves the computer system; for example, data received from a terminal or sent to a magnetic tape unit is converted. Binary character data is not converted as it enters or leaves the system. Character codes are not converted when moved within the system; for example, data transferred to or from mass storage is not converted. /gfcjy The distinction between coded character data and binary character data is important when reading or punching cards and when reading or writing magnetic tape. Only coded character data can be properly reproduced as characters on a line printer. Only binary character data can properly represent characters on a punched card when the data cannot be stored as display code. 60471400 G The distinction between binary character data and characters represented by binary data (such as peripheral equipment instruction codes) is also important. Only such binary noncharacter data can properly reproduce characters on a plotter. FORMATTED AND UNFORMATTED CHARACTER DATA Character codes can be interpreted by a product as formatted character data or as unformatted character data. Formatted data can be stored or retrieved by a product in the form of the codes described for coded character data in the remainder of this appendix, or formatted data can be altered to another form during storage or retrieval; for example, 1 can be stored as a character code or as an integer value. Treatment of unformatted data by a product includes both coded character data and binary character data as described in this appendix. NETWORK OPERATING SYSTEM The Network Operating System (NOS) supports the following character sets: CDC graphic 64-character set CDC graphic 63-character set ASCII graphic 64-character set ASCII graphic 63-character set ASCII graphic 95-character set ASCII 128-character graphic and control set Each installation must select either a 64-character set or a 63-character set. The differences between the codes of a 63-character set and the codes of a 64-character set are described under Character Set Anomalies. Any reference in this appendix to a 64-character set implies either a 63or 64-character set unless otherwise stated. To represent its six listed character sets in central memory, NOS supports the following code sets: • 6-bit display code • 12-bit ASCII code • 6/12-bit display code The 6-bit display code is a set of 6-bit codes from OOg to 778. The 12-bit ASCII code is the ASCII 7-bit code (as defined by ANSI Standard X3.4-1977) right-justified in a 12-bit byte. Assuming that the bits are numbered from the right starting with 0, bits 0 through 6 contain the ASCII code, bits 7 through 10 contain zeros, and bit 11 distinguishes the 12-bit ASCII OOOOg code from the end-of-line byte. The 12-bit codes are OOOlg through 01778 and 40008. A-l • The 6/12-bit display code is a combination of 6-bit codes and 12-bit codes. The 6-bit codes are 008 through 77s, excluding 74g and 76g. (The interpretation of the OOg and 63g codes is described under Character Set Anomalies later in this appendix.) The 12-bit codes begin with either 74g or 76g and are followed by a 6-bit code. Thus, 74g and 76g are considered escape codes and are never used as 6-bit codes within the 6/12-bit display code set. The 12-bit codes are 7401g, 7402g, 7404g, 7407a, and 7601g through 7677g. All other 12-bit codes (74xx8 and 7600g) are undefined. CHARACTER SET ANOMALIES The operating system input/output software and some products interpret two codes differently when the installation selects a 63-character set rather than a 64-character set. If an installation uses a 63-character set, the colon graphic character is always represented by a 63g code, display code OOg is undefined (it has no associated graphic or punched card code), and the % graphic does not exist. If the installation uses a 64-character set, output of a 7404g 6/12-bit display code or a OOg display code produces a colon. A colon can be input only as a 7404g 6/12-bit display code. The use of undefined 6/12-bit display codes in output files produces unpredictable results and should be avoided. Two consecutive OOg codes can be confused with an end-of-line byte and should be avoided. CHARACTER SET TABLES The character set tables A-l and A-2 are designed so that the user can find the character represented by a code (such as in a dump) or find the code that represents a character. To find the character represented by a code, the user looks up the code in the column listing the appropriate code set and then finds the character on that line in the column listing the appropriate character set. To find the code that represents a character, the user looks up the character and then finds the code on the same line in the appropriate column. The IAF user can convert a 6/12-bit code file to a 12-bit ASCII code file using the NOS FCOPY control statement. The resulting 12-bit ASCII file can be routed to a line printer but cannot be output through IAF. IAF supports both character mode and transparent mode transmissions through the network. These transmission modes are described under Network Access Method Terminal Transmission Code Sets in this appendix. IAF treats character mode transmissions as coded character data; IAF converts these transmissions to or from either 6-bit or 6/12-bit display code. IAF treats transparent mode transmissions as binary character data; transparent mode communication between IAF and ASCII terminals using any parity setting occurs in the 12-bit ASCII code shown in table A-l. Local Batch Users Table A-2 lists the CDC graphic 64-character set, the ASCII graphic 64-character set, and the ASCII graphic 95-character set. This table also lists the code sets and card keypunch codes (026 and 029) that represent the characters. /*S^V The 64-character sets use display code as their code set; the 95-character set uses 12-bit ASCII code. The 95-character set is composed of all the characters in the ASCII 128-character set that can be printed at a line printer (refer to Line Printer Output). Only 12-bit ASCII code files can be printed using the ASCII graphic 95-character set. To print a 6/12-bit display code file (usually created in IAF ASCII mode), the user must convert the file to 12-bit ASCII code. To do this, the NOS FCOPY control statement must be issued. The 95-character set is represented by the 12-bit ASCII codes 0040g through 0176g. Line Printer Output The batch character set printed depends on the print train used on the line printer to which the file is sent. The following are the print trains corresponding to each of the batch character sets: Character Set Print Train CDC graphic 64-character set 596-1 Conversational Terminal Users ASCII graphic 64-character set 596-5 Table A-l shows the character sets and code sets available to an Interactive Facility (IAF) user at an ASCII code terminal using an ASCII character set. Table A-9 (later in this appendix) shows the octal and hexadecimal 7-bit ASCII code for each ASCII character, and can be used to convert codes from octal to hexadecimal. (Under NOS using network product software, certain Terminal Interface Program commands require specification of an ASCII code.) ASCII graphic 95-character set 596-6 IAF Usage When in normal time-sharing mode (specified by the IAF NORMAL command), IAF assumes the ASCII graphic 64-character set is used and translates all input and output to or from display code. When in ASCII time-sharing mode (specified by the IAF ASCII command), IAF assumes the ASCII 128-character set is used and translates all input and output to or from 6/12-bit display code. A-2 ,*SSv The characters of the default 596-1 print train are listed in the table A-2 column labeled CDC Graphic (64-Character); the 596-5 print train characters are listed in the table A-2 column labeled ASCII Graphic (64-Character); and the 596-6 print train characters are listed in the table A-2 column labeled ASCII Graphic (95-Character). If a transmission error occurs during the printing of a line, NOS prints the line again. The CDC graphic print train prints a concatenation symbol (r*) in the first printable column of a line containing errors. The ASCII print trains print an underline instead of the concatenation symbol. If an unprintable character exists in a line (that is, a 12-bit ASCII code outside of the range 0040g through 0176g), the number sign (#) appears in the first printable column of a print line and a space replaces the unprintable character. 60471400 G Punched Card Input and Output Under NOS, coded character data is exchanged with local batch card readers or card punches according to the translations shown in table A-2. As indicated in the table, additional card keypunch codes are available for input of the ASCII and CDC characters ]and[. The 95-character set cannot be read or punched as coded character data. Depending on an installation or deadstart option, NOS assumes an input deck has been punched either in 026 or 029 keypunch code (regardless of the character set in use). The alternate keypunch codes can be specified by a 26 or 29 punched in columns 79 and 80 of any 6/7/9 card or 7/8/9 card. The specified code translation remains in effect throughout the job unless it is reset by specification of the alternate code translation on a subsequent 6/7/9 card or 7/8/9 card. NOS keypunch code translation can also be changed by a card containing a 5/7/9 punch in column 1. A blank (no punch) in column 2 indicates 026 conversion mode; a 9 punch in column 2 indicates 029 conversion mode. The conversion change remains in effect until another change card is encountered or the job ends. The 5/7/9 card also allows literal input when 4/5/6/7/8/9 is punched in column 2. Literal input can be used to read 80-column binary character data within a punched card deck of coded character data. Literal cards are stored with each column in a 12-bit byte (a row 12 punch is represented by a 1 in bit 11, row 11 by bit 10, row 0 by bit 9, and rows 1 through 9 by bits 8 through 0 of the byte), 16 central memory words per card. Literal input cards are read until a card identical to the previous 5/7/9 card (4/5/6/7/8/9 in column 2) is read. The next card can specify a new conversion mode. ^ p \ Remote Batch Users When card decks are read from remote batch devices, the ability to select alternate keypunch code translations depends upon the remote terminal equipment. Remote batch terminal line printer, punched card, and plotter character set support is described under Input Deck Structure in the Remote Batch Facility (RBF) reference manual. RBF supports only character mode transmission to and from consoles through the network. Character mode is described under Network Access Method Terminal Transmission Code Sets in this appendix. Because only 63 characters can be represented in 7-track even parity, one of the 64 display codes is lost in conversion to and from external BCD code. Figure A-l shows the differences in conversion that depend on which character set (63 or 64) the system uses. The ASCII character for the specified character code is shown in parentheses. The output arrow shows how the display code changes when it is written on tape in external BCD. The input arrow shows how the external BCD code changes when the tape is read and converted to display code. 63-Character Set Display Code 00 33(0) 63(:> External BCD 16(%) Output 12(0) 12(0) Display Code Input 00 33(0) 33(0) 64-Character Set Display Code 00(:) 33(0) 63(%) External BCD 12(0) Output 12(0) 16{%) Display Code Input 33(0) 33(0) 63(%) Figure A-l. Magnetic Tape Code Conversions Tables A-3 and A-4 show the character set conversions for nine-track tapes. Table A-3 lists the conversions to and from 7-bit ASCII character code and 6-bit display code. Table A-4 lists the conversions between 8-bit EBCDIC character code and 6-bit display code. Table A-5 shows the character set conversions between 6-bit external BCD and 6-bit display code for seven-track tapes. If a lowercase ASCII or EBCDIC code is read from a 9-track coded tape, it is converted to its uppercase 6-bit display code equivalent. To read and write lowercase ASCII or EBCDIC characters, the user must assign the tape in binary mode and then convert the binary character data. During binary character data transfers to or from 9-track magnetic tape, the 7-bit ASCII codes shown in table A-3 are read or written unchanged; the 8-bit hexadecimal EBCDIC codes shown in table A-4 also can be read or written unchanged. ASCII and EBCDIC codes cannot be read or written to 7-track magnetic tape as binary character data. Magnetic Tape Users Tables A-6 and A-7 list the magnetic tape codes and their punch code equivalents on IBM host computers. Coded character data to be copied from mass storage to magnetic tape is assumed to be represented in display code. NOS converts the data to external BCD code when writing a coded 7-track tape and to ASCII or EBCDIC code (as specified on the tape assignment statement) when writing a coded 9-track tape. Two CDC utility products, FORM and the 8-Bit Subroutines, can be used to convert to and from EBCDIC data. Table A-7 contains the octal values of each EBCDIC code right-justified in a 12-bit byte with zero fill. This 12-bit EBCDIC code can also be produced using FORM and the 8-Bit Subroutines. 60471400 G A-3 • TABLE A-l. CONVERSATIONAL TERMINAL CHARACTER SETS ASCII Graphic (64-Char acter Set) ASCII Character (128-Character Set) A B C D E F G H I J K L M N 0 P Q R S T U V 01 02 03 04 05 06 07 10 11 12 13 14 15 16 u plus minus asterisk slash I. paren. r. p a r e n . dollar equal to X Y Z 0 1 2 3 4 5 6 7 8 9 + plus - minus * asterisk / slash (I. paren. ) r. paren. $ dollar = equal to space f comma . period tt number r I. bracket 3 r. b r a c k e t X percent tt " quote space , comma . period tt number r. I . b r a c k e t 3 r. b r a c k e t X percenttt " quote __ underline ! exclam. 8 ampersand 1 apostrophe _ underline ! exclam. S ampersand * ? question ? < less than < > g r t r. t h a n > Code Octal 6/12-Bit Display Codet Octal 12-Bit ASCII Code 01 02 03 04 05 06 07 10 11 0101 0102 0103 ASCII Graphic (64-Char acter Set) oott colon™ * / ( ) $ = Octal 6-Bit Display apostrophe question less than grtr. than 3 comI. at \ r e v. s l a n t •** circumflex \ rev. slant ; semicolon ; semicolon 3 coml. at **" circumflex 12 13 14 15 16 17 20 17 20 21 22 23 24 25 21 22 23 24 25 26 27 30 26 27 30 31 32 33 34 35 31 32 33 34 35 36 37 40 41 42 43 44 45 36 37 40 41 42 43 44 45 46 47 50 51 52 53 54 55 46 47 50 51 52 53 54 55 56 0104 0105 0106 0107 0110 0111 0112 0113 0114 0115 0116 0117 0120 0121 0122 0123 0124 0125 0126 0127 0130 0131 0132 0060 0061 0062 0063 0064 0065 V w X y z < | > " left brace vert, line right brace tilde NUL SOH 0071 0053 0055 0052 0057 0050 0051 0044 0075 0040 0054 0056 0043 0133 ETX EOT ENQ ACK BEL BS HT LF VT FF 57 60 62 62 63tt 64 65 63tt 64 65 66 67 70 66 67 70 71 72 73 74 75 71 72 73 0046 0047 0077 0074 0076 75 0134 77 7401 0073 0100 61 : colontt grave accent a b c d e f g h i j k I m n o P q r s t u 0066 0067 0070 56 57 60 61 76 77 ASCII Character (128-Character Set) 0135 0045 0042 0137 0041 STX C R S O SI DEL DLE DC1 DC2 DC3 DC4 NAK SYN ETB CAN EM SUB ESC FS GS RS US Octal 6-Bit Display Code Octal 6/12-Bit Display Codet Octal 12-Bit ASCII Code 7402 7404tt 7407 7601 7602 7603 7604 7605 7606 7607 7610 7611 7612 7613 7614 7615 7616 7617 7620 7621 7622 7623 7624 7625 7626 7627 7630 7631 7632 7633 7634 7635 7636 7640 7641 7642 7643 7644 7645 7646 7647 7650 7651 7652 7653 7654 7655 7656 7657 7637 7660 7661 7662 7663 7664 7665 7666 7667 7670 7671 7672 7673 7674 7675 7676 7677 0136 0072 0140 0141 0142 0143 0144 0145 0146 1047 0150 0151 0152 0153 0154 0155 0156 0157 0160 0161 0162 0163 0164 0165 0166 0167 0170 0171 0172 0173 0174 0175 0176 4000 0001 0002 0003 0004 0005 0006 0007 0010 0011 0012 0013 0014 0015 0016 0017 0177 0020 0021 0022 0023 0024 0025 0026 0027 0030 0031 0032 0033 0034 0035 0036 0037 tGenerally available only on NOS, or through BASIC on NOS/BE. ttThe interpretation of this character or code depends on its context. Refer to Character Set Anomalies in the text. ^VCE^v • A-4 60471400 G TABLE A-2. LOCAL BATCH DEVICE CHARACTER SETS Octal 6-Bit D i sp l a y Code Octal 6/12-Bit Display Codet Octal 12-Bit ASCII Code A B C D E F G 00 tt 01 02 03 04 05 06 07 01 02 03 04 05 06 07 H I J K L M N 0 H I J K L M N 0 10 11 12 13 14 15 16 17 P Q R S T U V P Q R S T U V P Q R S T U V X Y Z 0 1 2 3 4 CDC Graphic (64-Character Set) ASCII Graphic (64-Character Set) ASCII Graphic (95-Character Set) : colontt A B C D E F G : colontt A B C D E F G H I J K L M N 0 Card Keypunch Code 026 029 0101 0102 0103 0104 0105 0106 0107 8-2 12-1 12-2 12-3 12-4 12-5 12-6 12-7 8-2 12-1 12-2 12-3 12-4 12-5 12-6 12-7 10 11 12 13 14 15 16 17 0110 0111 0112 0113 0114 0115 0116 0117 12-8 12-9 11-1 11-2 11-3 11 - 4 11-5 11-6 12-8 12-9 11-1 11-2 11-3 11-4 11-5 11 - 6 u 20 21 22 23 24 25 26 27 20 21 22 23 24 25 26 27 0120 0121 0122 0123 0124 0125 0126 0127 11-7 11-8 11-9 0-2 0-3 0-4 0-5 0-6 11-7 11-8 11-9 0-2 0-3 0-4 0-5 0-6 X Y Z 0 1 2 3 4 X Y Z 0 1 2 3 4 30 31 32 33 34 35 36 37 30 31 32 33 34 35 36 37 0130 0131 0132 0060 0061 0062 0063 0064 0-7 0-8 0-9 0-7 0-8 0-9 5 6 7 8 9 + plus - minus * asterisk 5 6 7 8 9 + plus - minus * asterisk 5 6 7 8 9 + plus - minus * asterisk 40 41 42 43 44 45 46 47 40 41 42 43 44 45 46 47 0065 0066 0067 0070 0071 0053 0055 0052 12 11 11-8-4 12-8-6 11 11 - 8 - 4 / ( ) $ = slash left paren. right paren. dollar equal to space , comma . period / ( ) $ = slash left paren. right paren. dollar equal to space , comma . period / ( ) $ = slash left paren. right paren. dollar equal to space z comma . period 50 51 52 53 54 55 56 57 50 51 52 53 54 55 56 57 0057 0050 0051 0044 0075 0040 0054 0056 0-1 0-8-4 12-8-4 11-8-3 8-3 no punch 0-8-3 12-8-3 0-1 12-8-5 11-8-5 11-8-3 8-6 no punch 0-8-3 12-8-3 = equivalence C left bracket ft number C- left bracket ft number C I. bracket 60 61 60 61 0043 0133 0-8-6 8-7 3 right bracket 3 right bracket 3 r. bracket 62 62 0135 0-8-2 % percent™ X percent™ % percent™ 63 63 0045 8-6 w 60471400 G u 8-3 12-8-2 or 12-0nt 11-8-2 or 11-0™t 0-8-4 A-5 • TABLE A-2. LOCAL BATCH DEVICE CHARACTER SETS (Contd) CDC Graphic (64-Character Set) ASCII Graphic (64-Character Set) * not equal f*concat. V togical OR A logical AND t superscript i subscript " quote < less than > greater than < less/equal > greater/equal -i logical NOT __ underline ! exclamation 8 ampersand 1 apostrophe ? question < less than > greater than 3 commercial at \ reverse slant **• circumflex ; semicolon ; semicolon Octal 6/12-Bit Display Codet Octal 12-Bit ASCII Code 64 65 66 67 70 71 72 73 0042 0137 0041 0046 0047 0077 0074 0076 75 0134 a b 77 7401 7402 7404™ 7407 7601 7602 0073 0100 0136 0072 0140 0141 0142 c d e f g h i j 7603 7604 7605 7606 7607 7610 7611 7612 0143 0144 0145 0146 0147 0150 0151 0152 k I m n o P q r 7613 7614 7615 7616 7617 7620 7621 7622 0153 0154 0155 0156 0157 0160 0161 0162 s t u v w 7623 7624 7625 7626 7627 7630 7631 7632 0163 0164 0165 0166 0167 0170 0171 0172 7633 7634 7635 7636 0173 0174 0175 0176 ASCII Graphic (95-Character Set) " quote _ underline ! exclamation & ampersand 1 apostrophe ? question < less than > greater than \ rev. slant ; semicolon 3 comI. at **• circumflex : colon™ * grave accent X y z < | > " left brace vert, line right brace tilde Octal 6-Bit D i sp l a y Code 64 65 66 67 70 71 72 73 74 75 76 77 Card Keypunch Code 026 029 8-4 0-8-5 11-0 0-8-7 11-8-5 11-8-6 12-0 11-8-7 8-5 12-8-5 12-8-6 8-7 0-8-5 12-8-7 12 8-5 0-8-7 12-8-4 0-8-6 8-4 0-8-2 11-8-7 12-8-7 11-8-6 Generally available only on NOS, or through BASIC on NOS/BE. t tThe interpretation of this character or code depends on its context. Refer to Character Set Anomalies in the text. ttt Available for input only, on NOS. • A-6 60471400 G TABLE A-3. ASCII 9-TRACK CODED TAPE CONVERSION ASCII ASCII Display Code Conversiont Code (Hex) 20 21 22 23 24 25 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A Char space ii tt Codet™ Character and Code Conversion™ Code (Hex) 00 7D 02 03 04 05 05 06 07 08 09 0A 0B 0C 0D 0E OF 10 11 12 13 14 15 16 17 18 19 1A Code Conversiont Char ASCII Char Code (Octal) Code (Hex) NUL space 55 66 64 60 53 63 55 67 70 51 52 47 45 56 46 57 50 33 34 35 36 37 40 41 42 43 44 00 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F STX ETX EOT ENQ ENQ ACK BEL BS HT LF VT FF C R S O SI DLE DC1 DC2 DC3 DC4 NAK SYN ETB CAN EM SUB ft space Display code 00 is undefined at sites using the 63-character set. 3A 3B 3C 3D 3E 3F 1A 1B 7B 1D 1E 1F SUB ESC GS RS US 63 77 72 54 73 71 Char *. Character and Code Conversion™ Code (Hex) 60 61 62 63 64 65 66 67 68 69 6A 68 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 1C 7C 01 7E 7F Char Display Codettt ASCII Char FS *SOH DEL At. Code (Octal) 74 01 02 03 04 05 06 07 10 11 12 13 14 15 16 17 20 21 22 23 24 25 26 27 30 31 32 61 75 62 76 65 tyhen these characters are copied from or to a tape, the characters remain the same and the code changes from/to ASCII to/from display code. ™These characters do not exist in display code. When the characters are copied from a tape, each ASCII character is changed to an alternate display code character. The corresponding codes are also changed. Example: When the system copies a lowercase a, 61^, from tape, it writes an uppercase A, 01g. ™*A display code space always translates to an ASCII space. r 60471400 G A-7 TABLE A-4. EBCDIC 9-TRACK CODED TAPE CONVERSION EBCDIC Code Conversiont Code (Hex) Char EBCDIC Character and Code Conversion™ Code (Hex) Char Display Codettt ASCII Char Code (Octal) 40 00 NUL space space 55 4A t 1C IFS .r 61 4B 0E S O 57 < 4C C O C < 72 4D ( BS 16 ( 51 + 4E + 0B VT 45 I 4F DO > 66 50 & 2E ACK s 67 i 5A 01 SOH 62 5B $ 37 EOT $ 53 * 5C 25 LF * 47 5D ) 05 HT ) 52 5E 27 ESC 77 5F A1 76 60 0D C R 46 61 OF SI 50 6B OC FF 56 6C 2D ENQ % 63 6C 2D ENQ space 55 6D 07 DEL 65 6E 1E IRS 73 6F 1F IUS 71 7A | : 3F SUB 00 Display code 00 is undefi ned at sites using the 63-character set. I 7A 7B 7C 7D 7E 7F C1 C2 C3 C4 C5 3F 03 79 2F 1D 02 81 82 83 84 85 SUB ETX \ BEL IGS STX a b c d e 63 60 74 70 54 64 01 02 03 04 05 Code Conversiont Code (Hex) C6 C7 C8 C9 D1 D2 D3 D4 D5 D6 D7 D8 D9 E O E2 E3 E4 E5 E6 E7 E8 E9 FO F1 F2 F3 F4 F5 F6 F7 F8 F9 Char Character and Code Conversion™ Code Char (Hex) 86 87 88 89 91 92 93 94 95 96 97 98 99 6A A2 A3 A4 A5 A6 A7 A8 A9 10 11 12 13 3C 3D 32 26 18 19 Display Codettt ASCII Char f g h i j k I m n o P q r I s t u V w X y z DLE DC1 DC2 TM DC4 NAK SYN ETB CAN EM Code (Octal) 06 07 10 11 12 13 14 15 16 17 20 21 22 75 23 24 25 26 27 30 31 32 33 34 35 36 37 40 41 42 43 44 ALL EBCDIC codes not listed translate to display code 55g (space). A display code space always translates to an EBCDIC space. ™These characters do not exist in display code. When the characters are copied from a tape, each EBCDIC character is changed to an alternate display code character. The corresponding codes are also changed. Example: When the system copies a lowercase a, &li0, from tape, it writes an uppercase A, OI3. t t t'When these characters are copied from or to a tape, the characters remain the same (except EBCDIC codes ^16/ 4r"l6/ 5A«|6, and 5F-|0) and the code changes from/to EBCDIC to/from display code. • A-8 60471400 G TABLE A-5. 7-TRACK CODED TAPE CONVERSIONS External BCD 01 02 03 04 05 06 07 10 11 12* 13 14 15 16t 17 20 21 22 23 24 25 26 27 30 31 32 33 34 35 36 37 ASCII Character ■i space Octal Display Code External 34 35 36 37 40 41 42 43 44 33 54 64 74 63 61 55 50 23 24 25 26 27 30 31 32 62 56 51 65 60 67 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 60 61 62 63 64 65 66 67 70 71 72 73 74 75 76 77 BCD ASCII Character .A. Octal Display Code 46 12 13 14 15 16 17 20 21 22 66 53 47 70 71 73 45 01 02 03 04 05 06 07 10 11 72 57 52 75 76 77 TAs explained in the text of this appendix, convers ion of these codes depends on whether the tape is being read or written. 60471400 G A-9 • r u. U l i 8 7 ^ - - S£ CM I 25 78 7 4° ? 7 T CM CM 2 7 CM 7g !" 7 CM 7 CM CM " § 7 7 CM 72 p o 8 7 CM 1 i So fM eo 7 7 7 2 7 CM CM B O PS w H 5 So CM •-S CM o"" CM 7 7 7 7 CM u. es 7 CM CM 1 CM I t ? CM CM -8 7 7 CM CM CM 75 7 7 op™ ? ? ? ? CM CM CM CM CM CM ^o°~ 7 7 - CM °^ ? OS 5° *° •^3 CM Ow SI *§ o s W s - 5l " cut a. o*" C M o — a C M .0—JS O-O 1 * <—< 0,2a, u. u. CM 7 : 7 00: a** - q > tlr-tl O - O = CM 78 CT IA U. u. u. CO in CO in CM = C M o ui iT i» r»0B ? ?" 1 CM 1 CM 1 CM 7 * 7 7 70> 7W 7 7 U l 2 7 CM CM C T C T CM 7S 7 £ — £ <0 Ul Ul 7S 7 r»r«. 1 m i m 7 7 1 !«• 7 CM C M CM CM 7 CM CM 78 7 78 7 7 CM N O N 78 o2o i 2 i 7 8 CM 75 00 IL 0) U. u. (0 00 # o # «Su. 4 o> — imS —O T t Z X — 0 7S _jo>_i CM__ C T C T 1 01 7 C M J,tU CM CM C T C T ' o 1 a x t - x c -1 — -1 7 i - / mm 1cn 7S eSe CM e— c f u . m i n ap in ts s-s U l v2v 7 11 a 11 m1 m O Z t CM +— + III tog 7$ 7 CM O— 0 2§ 1, 7g 0 - 0 u. r^ tn 1 ui A2A -In 7 * 7 CO 1 2. 1 - 1 CM U ( j | U W T W OTC0OT U I O U I cn si? i 7 an —s r« 7 7 1 Otx2 cc-£ 7 S?2 Ul u. «»7w OT7w as «° ^2 u. U l CM l » s< Z SSo U l 7 ' 7 co oo as m CT*" 7 7 CMO o o o 01 J t T j t TC CM in CO CM° 1 u. (0 o O —UJ o O O o < 7 7 °? 5J.5 UJ o o J" CM 7 Sl7u ooooo v Z 9 z U. UJ CM i n l T C cn OS 7 7 CO m CO CM o 7 o zaU Ja?OtUzaI o ■■C O•■ 4 0 1 -7 8 SO Ul CM HCNtu i - u i UJ01UI o 0) i CM » to TC TC O cn in in 7 t o TC o 0) in v i in tn — t/i TC o 00 CO I ui cn 7 7 7s -cc —* op« CM >2> ? — 0) OS CM S3 CO 7 7 Set CM 7 C M /*S*?!\ CM C T 7 7 CM 7 U l 43 0)0 c.2 7 1 r» CM CM T00C T C x o x u. (0 i ^ C M mm o n 75 7 CM 00 cj" CM 0»— O) (0 (0 >—> i i n 78 O - O O - t - OenO tfSXX 2 p» sis s!5 A- 8~8 tests oo"° CM q S d uiSu. u.Su. T C V 7 C M ,£ T C 78 7 > 7i > >e coco CM CM UJ —UJ w 2" o w T (0 CM o • Q t - O T C CT1" > j CT7 IM 1". <0 to!? ing Ul I 0 O ?" ? CM Ul 00 00 C M CM i C M 00 CM mS ? 2§ 7 7 ? CM C M ^ o 1 CM CM •■o 7 7 < < I ? ? CM 7 7 7 CM 00 T C CM U. ct S 3 o"" aa es ? 7 ? CM 85 < 7 7 7 ? 7S 7 i r» 7 ? 7 < 7 IO Ul T. U . 1 oS)"- 7 t8 ? CM UJ ?I- >s J f3 7 CM CD o*" cyu. I I 7 2 7 7 I I 7i 0 n 1 T'0 4 ' 2« tf< Ul ? 7 7 ? too xfta u. U l U l Ul 7 7 I I CM UJ 7 7 7 7 CM 09 m f fl o 4 2 2 7 IM IU Ul CM 7° T8 7 7 It Sit KcmOC O - O 828 - 2 2§ 22 4 7 7° 7 0) rr 4 Ol — CM — W — OT 0 0 o o O .^-*^s 60471400 G 7S 5 - W O W -2. =2= >2> 5iS N O N X O ) 2 7C I u. 7 7 o« 7 s-s ss >S «s 0^S gg 4s £^ Og w< < eSe ._— ._ Jt — 4t 33 IO BB gg Q9 ' C O ' ..CO =*»=«= co. oo oo *curt 9 tax: A2A 4 cap rs < gg |8 & En tti IS 7* 7 vsv OT C W r< H i ? I z7 0.05 ZCMZ > M1 O> W -I- 3?3 OoiQ 5s° 22 U l * " Q Q m 4* I UJ —ui O - O COO CO 7 is8 ■ i k **8 4 x4x x 4 x 8S8 teste to it - 7 -im-) UITUI zU I7O UzI ul2tu l-CM»Ul —Ul 2=5 £st Siffi 3?«3 2?8 8= 17 Ss <^^V Octal 12-Bit EBCDIC Code 0101 thru 0111 0112 0113 0114 0115 0116 0117 0120 0121 thru 0131 0132 0133 0134 0135 0136 0137 0140 0141 0142 thru 0151 0152 0153 0154 0155 0156 0157 0160 thru 0170 0171 0172 0173 0174 0175 0176 0177 0200 0201 0202 0203 0204 0205 0206 0207 0210 0211 0212 thru 0220 0221 0222 0223 0224 0225 0226 0227 0230 0231 0232 thru 0240 EBCDIC Graphic Character1 EBCDIC Control Character u n d e fi n e d undefined - i undefined >" undefined •i undefined u n d e fi n e d undefined 60471400 G TABLE A-8. FULL EBCDIC CHARACTER SET (Contd) Hexa decimal EBCDIC Code Octal 12-Bit EBCDIC Code A1 A2 A3 A4 A5 A6 A7 A8 A9 AA 0241 0242 0243 0244 0245 0246 0247 0250 0251 0252 thru 0277 0300 0301 0302 0303 0304 0305 0306 0307 0310 0311 0312 0313 0314 0315 0316 0317 0320 0321 0322 0323 0324 0325 0326 thru BF CO C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB C C C D CE CF D O D1 D2 D3 D4 D5 D6 EBCDIC Graphic Character* EBCDIC Control Character Hexa decimal EBCDIC Code D7 D8 D9 DA thru undefined DF E O E1 E2 E3 E4 E5 E6 E7 E8 E9 EA EB EC ED thru undefined undefined P• undefined undefined EF FO F1 F2 F3 F4 F5 F6 F7 F8 F9 FA FB thru FF Octal 12-Bit EBCDIC Code 0327 0330 0331 0332 thru 0337 0340 0341 0342 0343 0344 0345 0346 0347 0350 0351 0352 0353 0354 0355 thru 0357 0360 0361 0362 0363 0364 0365 0366 0367 0370 0371 0372 0373 thru 0377 EBCDIC Graphic Character1 EBCDIC Control Character undefined undefined undefined undefined rl undefined undefined TGraphic characters sshown are those used on the IBM System/370 standard (PN) print train. Other devices support subsets or vv a r i a t i o n s o f t h is character graphic set. /g|ps\ 60471400 G A-13 • NETWORK ACCESS METHOD TERMINAL TRANSMISSION CODE SETS There are two modes in which coded character data can be exchanged with a network terminal console. These two modes, character mode and transparent mode, correspond to the type of character code editing and translation performed by the network software during input and output operations. The transmission mode used by the network software for input can be selected by the terminal operator, using a Terminal Interface Program command (sometimes referred to as a terminal definition command). The transmission mode used by the network software for output can be selected by the application program providing the terminal facility service. Character Mode Transmissions Character mode is the initial and default mode used for both input and output transmissions. When the network software services the terminal in character mode, it translates input characters from the transmission code used by the terminal into the ASCII code shown in table A-9. The translation of a specific transmission code to a specific ASCII code depends on the terminal class the network software associates with the terminal. In character mode input, the parity of the terminal transmission code is not preserved in the corresponding ASCII code; the ASCII code received by the terminal-servicing facility program always has its eighth bit set to zero. Character mode output is translated in a similar manner. The network software provides the parity bit setting appropriate for the terminal being serviced, even though translating from ASCII characters with zero parity bit settings. Tables A-10 through A-21 show the character mode translations performed for each terminal class. The parity shown in the terminal transmission codes is the parity used as a default for the terminal class. The parity setting actually used by a terminal can be identified to the network software through a TIP command. Tables A-10 through A-21 contain the graphic and control characters associated with the transmission codes used by the terminal because of the terminal class and code set in use. The network ASCII graphic and control characters shown are those of the standard ASCII character set associated with the ASCII transmission codes of table A-9. The general case for code translations of character mode data is summarized in the following paragraphs. This generalized description permits use of only table A-9 to explain all specific cases. The reader can logically extend this generalized description to allow use of tables A-l through A-8 as descriptions of character set mapping for various functions initiated from a terminal. Tables A-l through A-8 are provided for the reader's use while coding an application program to run under the operating system. They do not describe character transmissions between an application program and the network. • A-14 Table A-9 contains the ASCII 128-character set supported by the Network Access Method. A 96-character subset consists of the rightmost six columns and includes the 95-character graphic subset referenced previously in this appendix; the deletion character (DEL) is not a graphic character. A 64-character subset consists of the middle four columns. Note that 6-bit display code equivalents exist for the characters in this 64-character subset only. Although the network supports the 128-character set, some terminals restrict output to a smaller subset. This restriction is supported by replacing the control characters in columns 0 and 1 of table A-9 with blanks to produce the 96-character subset, and, additionally, replacing the characters in columns 6 and 7 with the corresponding characters from columns 4 and 5, respectively, to produce the 64-character subset. Similarly, input from a device may be limited to a smaller subset by the device itself because the device cannot produce the full 128-character set. A character input from a device using a character set other than ASCII is converted to an equivalent ASCII character; characters without ASCII character equivalents are replaced by the ASCII blank character. An application can also cause character replacement (as described previously for output) as well as character conversion, by requesting display-coded input from the network. The 7-bit hexadecimal code value for each character consists of the character's column number in the table, followed by its row number. For example, N is in row E of column 4, so its value is 4E1g. Transparent Mode Transmissions Transparent mode is selected separately for input and output transmissions. During transparent mode input, the parity bit is stripped from each terminal transmission code (unless the N parity option has been selected by a Terminal Interface Program command), and the transmission code is placed in an 8-bit byte without translation to 7-bit ASCII code. Line transmission protocol characters are deleted from a mode 4C terminal input stream. When the 8-bit bytes arrive in the host computer, a terminal servicing facility program such as the Interactive Facility can right-justify the bytes within a 12-bit byte. Upon transmission of 12-bit bytes from the host computer, the leftmost 4 bits (bits 11 through 8) are discarded. During transparent mode output, processing similar to that performed for input occurs. The code in each 8-bit byte received by the network software from the terminal servicing facility program is not translated. The parity bit appropriate for the terminal class being used is altered as indicated by the parity option in effect for the terminal. The codes are then output in transmission bytes appropriate for the codes associated with the terminal class being used. Line transmission protocol characters are inserted into a mode 4C terminal output stream. 60471400 G TABLE A-9. FULL ASCII CHARACTER SET ■128-Character Set•96-Character Subset■6 4 - C h a r a c t e r S u b s e t * * *■ Bits b^ bj b2 b,, t t t t o o o o Column NUL 000 DLE 020 SP 040 SOH 001 DC1 021 STX 002 11 0 060 100 120 140 160 1 061 A 101 Q 041 121 a 141 q 161 DC2 022 042 2 062 B 102 R 122 b 142 r 162 ETX 003 DC3 023 tt 043 3 063 C 103 S 123 c 143 s 163 EOT 004 DC4 024 $ 044 4 064 D 104 T 124 d 144 t 164 1 ENQ 005 NAK 025 X 045 5 065 E 105 U 125 e 145 u 165 0 11 0 ACK 006 SYN 026 & 046 6 066 F 106 V 126 f 146 v 166 0 111 BEL 007 ETB 027 047 7 067 G 107 W 127 9 147 w 167 0 0 0 0 0 0 0 0 10 0 1 10 10 i 0 0 0 BS 010 CAN 030 ( 050 8 070 H 11 0 X 130 h 150 x 170 0 0 1 HT 011 EM 031 ) 051 9 071 I 111 Y 131 i 151 y 171 0 1 0 LF 012 SUB 032 * 052 072 J 11 2 Z 132 j 152 z 172 VT 013 ESC 033 + 053 073 K 113 C 133 k 153 < 173 FF 014 FS 034 074 L 11 4 \ 054 134 I 154 174 CR 015 GS 035 055 075 M 115 : 135 m 155 > 175 S O 016 RS 036 > 076 N 056 11 6 136 n 156 176 SI 017 US 037 ? 077 0 117 137 o 157 DEL 177 0 1 1 1 1 1 0 0 1 1 1 0 1 0 1 < / 057 LEGEND: Numbers under characters are the octal values for the 7-bit character codes used within the network. 00m*_ 60471400 G A-15 • TABLE A-10. CHARACTER CODE TRANSLATIONS, CONSOLE TERMINAL CLASSES 9, 14, 16, AND 17 Terminal EBCDIC Octal Code Graphict 000 ETX PF HT LC 007 010 011 012 013 014 015 016 017 020 021 022 023 024 025 026 027 030 031 032 033 034 DEL undefined undefined m sm VT FF C R S O SI DLE DC1 DC2 T M RES NL B S IL CAN M E C C CU1 IFS IGS IRS 035 036 037 040 A-16 Control Character NUL SOH STX 001 002 003 004 005 006 041 042 043 044 045 046 047 050 051 052 053 054 055 056 057 060 061 062 063 064 065 066 067 070 071 072 073 074 075 076 077 100 Network ASCII IUS DS SOS FS undefined BYP LF ETB or EOB ESC or PRE undefined undefi ned M S CU2 undefined ENO ACK BEL undefined undefi ned SYN undefi ned P N RS U C EOT undefined undefined undefined CU3 DC4 NAK undefined space SUB Octal Codett Graphic 000 001 002 003 040 Oil 040 177 040 040 040 013 014 015 016 017 020 021 022 023 040 040 010 040 030 031 040 040 034 035 036 037 040 040 040 040 040 012 027 033 040 040 040 040 040 005 006 007 040 040 026 040 040 040 040 004 040 040 040 040 024 025 040 032 040 space space space space space space space space space space space space space space space space space space space space space space space space space space space space space space space Character Mode Use) Control Character null start of header start of text end of text horizontal tabulate delete vertical tabulate form feed carriage return shift out shift in data link escape device control 1 device control 2 device control 3 y^Kv backspace cancel end of medium file separator group separator record separator unit separator linefeed end of transmission block escape enquiry positive acknowledgment bell synchronous idle end of transmission device control 4 negative acknowledgement substitute space 60471400 G TABLE A-10. CHARACTER CODE TRANSLATIONS, CONSOLE TERMINAL CLASSES 9, 14,16, AND 17 (Contd) Network ASCII (Character Mode Use) Terminal EBCDIC Octal Code Graphic* 101 thru 111 112 113 114 115 116 117 120 121 Control Character Octal Codett Graphic undefined 040 space undefined 133 056 074 050 053 041 046 040 space undefined 135 044 052 051 073 136 055 057 040 space undefined 174 054 045 137 076 077 040 space thru 131 132 133 134 135 136 137 140 141 142 - i thru 151 152 153 154 155 156 157 160 thru 170 171 172 173 174 175 176 177 200 201 202 203 204 205 206 207 210 211 212 undefined 140 172 043 100 047 075 042 040 141 142 143 144 145 146 147 150 151 040 undefined 152 153 154 155 156 157 160 161 162 040 ii undefined thru 220 221 222 223 224 225 226 227 230 231 232 thru Control Character ii space .d space space 240 60471400 G A-17 • TABLE A-10. CHARACTER CODE TRANSLATIONS, CONSOLE TERMINAL CLASSES 9, 14, 16, AND 17 (Contd) Terminal EBCDIC Octal Code 241 242 243 244 245 246 247 250 251 252 thru 277 300 301 302 303 304 305 306 307 310 311 312 313 314 315 316 317 320 321 322 323 324 325 326 327 330 331 332 thru 337 340 341 342 343 344 345 346 347 350 351 352 353 354 355 thru 357 360 361 362 363 364 365 366 367 A-18 Graphic1 Network ASCII (Character Mode Use) Control Character undefined undefined undefined undefined undefined undefined undefined undefined undefined undefined Octal Codett Graphic 176 163 164 165 166 167 170 171 172 040 s t u v w x y z space 173 101 102 103 104 105 106 107 110 111 040 040 040 040 040 040 175 112 113 114 115 116 117 120 121 122 040 134 040 123 124 125 126 127 130 131 132 040 040 040 040 aZSS Control Character A B C D E F G H I space space space space space space A*%S J K L M N 0 P Q R space A ^ S \ space S T U V w X Y Z space space space space 060 061 062 063 064 065 066 067 60471400 G TABLE A-10. CHARACTER CODE TRANSLATIONS, CONSOLE TERMINAL CLASSES 9, 14, 16, AND 17 (Contd) Network ASCII (Character Mode Use) Terminal EBCDIC Octal Code 370 371 372 373 thru 377 Graphic1 Control Character Octal Codett Graphic undefined 070 071 040 040 space space Control Character tGraphic characters shown are those used on the IBM System/370 standard (PN) print train. Other devices support subsets or variations of this character graphic set. Shown with zero parity (eighth or uppermost bit is always zero). 0<$M^x\ y$f^\ 60471400 G A-19 TABLE A-ll. AMERICAN NATIONAL STANDARD CODE FOR INFORMATION INTERCHANGE (ASCH) WITH 029 PUNCHED CARD CODES AND EBCDIC TRANSLATION (BATCH OUTPUT DEVICES, TERMINAL CLASSES 9, 14, 16, AND 17) ASCII Bit h8 h7 b6 b5 ASCII Bit b5 b4 b3 b2 bx \ c o l RowN. 0 0 0 0 0 0 0 1 7 S b6 b4 b3 b2 bx \ C o l Row\ SP no punch SP 40 8-4 F0 9 7C 12-8-7 ! 4F 11-7 P 07 10 Fl 12-1 11-8 A Cl Q D8 10 10 F2 12-2 11 - 9 B C2 R D9 10 F3 12-3 0-2 C C3 S E2 F4 12-4 0-3 D C4 T E3 11 0 0-8-4 % 6C F5 12-5 E C5 0-4 U E4 11 0 12 & 12-6 F6 F C6 0-5 V E5 1 12-7 0-6 G C7 W E6 1 0 0 0 1 ii 0 0 10 0 0 0 0 0 11 10 10 0 1 11 0 111 8-3 # 8 F8 12-8 0-7 H C8 X E7 11-8-5 ) 5D 9 F9 12-9 0-8 I C9 Y E8 11-8-4 * 5C 8-2 : 7A 11-1 J Dl 12-8-6 + 4E 11-8-6 11-2 ; 5 E K D2 12-8-2 t 4A 6-8-3 6B 12-8-4 < 4C 11-3 L D3 0-8-2 \ E0 60 8-6 = 7E 11-4 M D4 11-8-2 ! 5A 4B 0-8-6 > 6E 11-5 N D5 11-8-7 -i 5F 61 0-8-7 ? 6F 11-6 0-8-5 0 D6 6D 10 8-7 7F 0 12-8-5 ( 4D 7B 11-8-3 $ 5B 50 10 (A) 11 0-9 Z E9 11 (B) 12 0 (C) 13 1 ii (D) 14 1 1 12-8-3 0 (E) 15 8-5 F7 7D 1 1 1 (F) 0-1 / LEGEND: ASCII Characte EBCDIC Characte I j i' 1 _ or EBCDIC Card / 11-8 - 2 5A ■—" * a rL* DIC tc B Code Code (Hexad ecimal) ■*^5?v A-20 60471400 G ft ft /!$W*P^S ft ft ft »! o°o - • ^^ m «■%» » * • m N ^ M -I 343 MOM »_ • - Ct < o -•\. • * • >2> K „ • • u5 oS MON 08 _<2.j as ■ a ••• 9 5v 2fc 2ft 2ft 2ft 2ft 28 "?8 Sft 2ft Sft 2ft 2ft 2ft 2fc 2ft 28 -R 2ft 2ft 04 <0 ^ 8 085 8* §3 <5 ^ • WZ QO «t a o°~ .:< 2ft .••" R J *!| ^ 85 « g» «»< 2ft 2ft ift 5ft i: i: i: 2ft =ft =ft n0 2& 2ft 2ft 2ft 2ft 2ft R i2ft 2ft f 8 8 8 8 8 8 8 8 2ft Itt IAAOI Sift sift -4 *2fc 8 = ft / rf5ft 2ft 2ft 2s 2s 2» 2ft 2ft 2ft 2ft 2ft 2ft i» M r\ »2. .2. .2. XX ift .-!L i . .1 i. ft A2A < 9 •»-•» Cft -R 4 .a 4 8 — - ..-.. r = < 8 i ♦^• V2v 2ft •»—— 8 . s. 8 8 8 p. i > 4 8 1]j i ! ! S 4R 8=fc 2ft 2ft ;r =» 2ft ?8 2ft «• i"=ft 2ft J" *1 4 8i i" J" 8i =& J8 4 R ? R ?■ 2ft 2 f t • •• ■•a ■• * a « 0 t4 sift cjift 1 * ;2ft £2ft ^ f t caoft ^ift .3 Lift ti 1 m. lil oft aft 3ft «8l I, •- » r 3ft loft 5? u a f t oaft zaft SSft 2ft Kaft eft uioftz> IS _•» o- 2ft «* _. • 1«»1 mm i« 2* ! ' !R 2ft 78 ft 6§ fH Q 1 0 S£ gS ,5 2R § | S Oj WO 2ft »Ss »£> » = * ■ Sx c < «s«» o" Q » 2ft - 2 * . 5 j E2s c 2 , « 2 o a2«. c/2o 2ft o§ 2ft f» 1 0* Ss Bo w£ 2ft „s ^ SB 2ft 78 R i .•• Sp 2ft Stl ..•• ?* ?8 ■5 SS ., tt ax r. <§ • rr J- 28 t« 7R 52fc £2ft 52ft y2ft a2ft • : u5 o9 w| = C S 3 ; o rr i i * ! • " A-21 • TABLE A-13. AMERICAN NATIONAL STANDARD CODE FOR INFORMATION INTERCHANGE (ASCII) WITH 026 PUNCHED CARD CODES AND EBCDIC TRANSLATION (BATCH OUTPUT DEVICES, TERMINAL CLASSES 9, 14, 16, AND 17) ASCII Bit ASCII Bit bb8 h7 b5 b4 b3 b2 bj b5 \ Col b4 b3 b2 bl Row\ 0 0 0 0 0 0 0 1 0 0 0 10 0 0 0 0 Fl A Cl Q D 8 11-8-3 $ 5B 1 8-6 11 0 0 i2-8-7 ! 4F 0-8-6 > 6E 0 10 F0 8-4 9 7C 11 10 SP no punch SP 40 7E 0-8-7 ? 6F 111 0-8-5 ) 5D 8-5 « 7D 11-7 P D7 1 0 0 12-1 11-8 1 0 0 F2 12-2 B C2 11-9 R D9 1 0 1 F3 12-3 C C3 0-2 S E2 1 0 1 F4 12-4 D C4 0-3 T E3 1 1 0 F5 12-5 E C5 0-4 U E4 1 1 0 F6 12-6 F C6 0-5 V E5 1 1 1 F7 12-7 G C7 0-6 W E6 1 1 1 LEGEND: C D C Chara( A EBCDI C Charac A jr 12-1 . 1 ULU \Col Row\ 0-8-4 % 6C 8 F8 12-8 H C8 0-7 X E7 12-8-4 < 4C 9 F9 12-9 I C9 0-8 Y E8 11-8-4 * 5C 8-2 : 7A 11-1 J Dl 0-9 Z E9 12 & 12-8-7 11-2 J 4 F K D2 8-7 " 7F 6B 12-0 { CO 11-3 L D3 12-8-5 ( 4D 60 8-3 11-4 # 7 B M D4 0-8-2 \ E0 11-8-7 11-5 - i 5 F N D5 12-8-6 + 4E 11-8-6 ; 5E £-8-5 6D 10 (A) 11 (B) 12 50 6-8-3 (C) 13 11 (D) 14 i2-8-3 4B (E) 15 (F) 0-1 / 61 11-6 0 D6 noc «w r BCDIC Card Code Ul L n — 1 cL.t3\,Ultr o r r t T r t,r ode I (Hexadecima 1) TABLE A-14. CHARACTER CODE TRANSLATIONS, CONSOLE TERMINAL CLASSES 1, 2, AND 5 THROUGH 8 Terminal ASCII (Transparent Mode Use) Octal Codet 000 003 005 006 011 012 014 017 • A-22 ASCII Graphic Control Character^ NUL or ® ETX or © ENQ or WRU or J) ACK or RU or © HT or 0 LF or NL or 1 or 0 FF or FORM or 0 SI or ® Network ASCII (Character Mode Use) Octal Codettt 000 003 005 006 Oil 012 014 017 ASCII Graphic Control Character null end of text enquiry positive acknowledgement horizontal tabulate linefeed formfeed shift in 60471400 G ygS&N. TABLE A-14. CHARACTER CODE TRANSLATIONS, CONSOLE TERMINAL CLASSES 1, 2, AND 5 THROUGH 8 (Contd) Network ASCII (Character Mode Use) Terminal ASCII (Transparent Mode Use) Octal Code 021 022 024 027 030 033 035 036 041 042 044 047 050 053 055 056 060 063 065 066 071 072 074 077 101 102 104 107 110 113 115 116 120 123 125 126 131 132 134 137 140 143 145 146 151 152 154 157 161 162 164 167 170 173 174 175 176 201 202 204 207 210 213 215 60471400 G ASCII Graphic Control Charactertt DC1 or X-ON or @ DC2 or TAPE or (ft DC4 or TAPE or Q ETB or © _ CAN or CLEAR or ® ESC or ESCAPE or 0 GS orQ RS or?A) •i _or— | ort or | Lor-i SOH or ® STX or © EOT or (P) BELL or or 7 P or p X or x G or g Control Character 045 or 116 or 126 or 105 or R0 or READER STOP NL or CR or RETURN LF or LINE FEED HT or TAB EOT IL or IDLE or NULL PRE or PREFIX DEL space _ or - 4 or ? + or & * or 8 Q or q Y or y H or h : or 4 M or m U or u D or d < K S B ) or 2 or k or s or b or 0 1 or 6 0 or o W or w F or f PN or PUNCH ON RES or RESTORE BY or BYPASS PF or PUNCH OFF undefined undefined undefined UCS or UPPERCASE BS or BACKSPACE EOB = or 1 J or j ? or / A or a ( or 9 R or r Z or z I or i Octal Codettt LCS or LOWERCASE 000 015 012 006 065 156 166 145 073 or 063 114 or 154 124 or 164 103 or 143 042 or 043 041 or 044 174 or 054 136 or 056 076 or 067 120 or 160 130 or 170 107 or 147 004 000 001 177 040 137 or 055 140 or 100 053 or 046 052 or 070 121 or 161 131 or 171 110 or 150 072 or 064 115 or 155 125 or 165 104 or 144 021 000 000 023 ASCII Graphic % or N or V or E or 5 n v e ; or 3 L or 1 T or t C or c " or # ! or $ i or , «*• or . > or 7 P or p X or x G or g Q or q Y or y H or h : or 4 M or m U or u D or d 062 153 163 142 060 < or 2 K or k S or s B or b ) or 0 041 or 117 or 127 or 106 or 066 157 167 146 ' or 6 0 or o W or w F or f 017 010 027 016 075 or 061 112 or 152 077 or 057 101 or 141 050 or 071 122 or 162 132 or 172 111 or 151 null carriage return line feed horizontal tabulate end of transmission' null . start of header5 delete space or * or @ + or & * or 8 074 or 113 or 123 or 102 or 051 or 000 000 000 Control Character = or J or ? or A or ( or R or Z or I or 1 j / a 9 r z i device control 1 (tape on) null null device control 3 (tape off) null null null shift in* backspace . end transmission block5 shift out§ A-31 TABLE A-18. ASCII CHARACTER CODE TRANSLATIONS, EBCD CONSOLE TERMINAL CLASS 4 (Contd) Terminal EBCD (Transparent Mode Use) Octal Codet 150 151 152 153 154 155 156 157 160 161 162 163 164 165 166 167 170 171 172 173 174 175 176 177 000 000 000 000 175 175 175 175 175 EBCD Graphic1"1" % or 5 N or n V or v E or e or 3 or 1 or t or c or # or $ or , —i or . > or 7 P or p X or x G or g space* spacej space* space5 Control Character R0 or READER STOP NL or CR or RETURN LF or LINE FEED HT or TAB EOT IL or IDLE or NULL PRE or PREFIX DEL IL or IDLE or NULLff IL or IDLE or NULL§§ IL or IDLE or NULL§§ IL or IDLE or NULLff IL or IDLE or NULL§§ Network ASCII (Character Mode Use) Octal Codettt 045 or 065 116 or 156 126 or 166 105 or 145 000 015 012 006 073 or 063 114 or 154 124 or 164 103 or 143 042 or 043 041 or 044 174 or 054 136 or 056 076 or 067 120 or 160 130 or 170 107 or 147 004 000 001 177 133 thru 135 140 173 175 or 176 002 003 005 007 013 or 014 175 175 175 IL or IDLE or NULLff IL or IDLE or NULL§§ IL or IDLE or NULL§§ 020 022 024 thru 026 175 IL or IDLE or NULL§§ 030 thru 037 ASCII Graphic % or 5 N or n V or v E or e or 3 or 1 or t or c or # or $ ! or , ^ or . > or 1 P or p X or x G or g [ or \ or ] or *~ Control Character null carriage return line feed horizontal tabulate end of transmission^ null start of header9 delete start of text end of text enquire bell vertical tabulate or form feed data link escape device control 2 device control 4, negative acknowledge, or synchronize cancel, end of media, substitute, escape, file separator, group separator, record separator, or unit separator TShown with odd and even parity; odd parity is the default for this terminal class, the application program receives the same code as in character mode.) (Unless PA=N, Each input line is assumed to begin in lowercase. Input characters are translated to lowercase ASCII characters unless prefixed by the UCS code. Once a case shift occurs, it remains in effect until another case shift code is received, the page width is reached, or the line is transmitted to the host computer. During output, case is preserved by insertion of case shift codes where needed. mShown with zero parity (eighth or uppermost bit is always zero). c sNot transmitted to the host computer after translation during input. ^Output translation only. s^ErS. A-32 60471400 G TABLE A-19. APL CHARACTER CODE TRANSLATIONS, EBCD CONSOLE TERMINAL CLASS 4 Terminal EBCD-APL (Transparent Mode Use) Octal Codet EBCD-APL 000 001 002 003 004 005 006 007 010 011 012 013 014 015 016 017 020 021 022 023 024 025 026 027 030 031 032 033 034 035 036 037 040 041 042 043 044 045 046 047 050 051 052 053 054 055 056 057 060 061 062 063 064 065 066 067 070 071 072 073 074 075 space _ —oror+ *- 60471400 G Graphictt Control Character - or 2 h or K undefined undefined undefined undefined i- or S 1 or B a or 0 > or 6 o or 0 w ~ or or W F undefined undefined undefined UCS or UPPERCASE BS or BACKSPACE E0B " or 1 LCS or LOWERCASE o or J \ or / oc or A v or 9 p or R = or Z \ or I = or 5 t or N U or V € or E < or 3 □ or L ~ or T n or C ) or ] ( or [ ; or , : or . > or 7 * or P => or X V or G Octal Codem 040 + or X * or 8 ? or Q t or Y A or H < or 4 1 or M \ or U u or D Network ASCII (Character Mode Use) 137 or 053 161 or 160 045 or 146 042 or 070 077 or 121 171 or 131 150 or 110 100 or 064 174 or 115 165 or 125 144 or 104 000 000 000 000 055 153 163 142 046 000 000 000 174 or 157 or - 167 or 136 or 066 117 127 106 017 010 027 016 042 or 061 152 or 112 134 or 057 141 or 101 041 or 071 162 or 122 172 or 132 151 or 111 075 or 065 156 or 116 166 or 126 145 or 105 undefined NL or CR or RETURN LF or LINE FEED HT or TAB 000 015 012 006 EOT 004 000 IL or IDLE or NULL or 062 or 113 or 123 or 102 or 060 074 or 063 154 or 114 164 or 124 143 or 103 051 or 135 050 or 133 073 or 054 072 or 056 076 or 067 052 or 120 170 or 130 147 or 107 ASCII-APL Graphic Control Character space _ or + -*■ or — + or X * or 8 ? or Q t or Y A or H < or 4 1 or M \ or U l or D - or 2 null null null null -i or K i- or S 1 or B a or 0 > or 6 o or 0 w —or orW F " or 1 null null null shift in§ backspace end transmission block§ shift out§ o or J \ or / oc or A v or 9 p or R c or Z \ or I = or 5 t or N U or V € or E < or 3 □ or L - or T n or C ) or ] ( or [ ; or , : or . > or 7 * or P = or X V or G null carriage return line feed horizontal tabulate end of transmission^ null A-33 • TABLE A-19. APL CHARACTER CODE TRANSLATIONS, EBCD CONSOLE TERMINAL CLASS 4 (Contd) Terminal EBCD-APL (Transparent Mode Use) Octal Codet 076 077 100 101 102 103 104 105 106 107 110 111 112 113 114 115 116 117 120 121 122 123 124 125 126 127 130 131 132 133 134 135 136 137 140 141 142 143 144 145 146 147 150 151 152 153 154 155 156 157 160 161 162 163 164 165 166 167 170 171 172 173 174 A-34 EBCD-APL Graphictt Control Character PRE or PREFIX DEL space _ or + -* or — + or X or 8 or Q or Y or H or 4 or M or U or D - or h or «- or l or ^ or 2 K ,S B 0 > or 6 o or 0 co — or or W F " or 1 0 or J \ or oc or •v or p or c or \ or I = or 5 t or N U or V € or E undefined undefined undefined undefined undefined undefined undefined UCS or UPPERCASE BS or BACKSPACE E0B LCS or LOWERCASE undefined NL or CR or RETURN LF or LINE FEED HT or TAB < or 3 D or L or T n or C ) or J ( or ( ; or , : or . > or 7 * or P = or X V or G EOT Network ASCII (Character Mode Use) Octal Codem 001 177 040 137 or 053 161 or 160 045 or 146 042 or 070 077 or 121 171 or 131 150 or 110 100 or 064 174 or 115 165 or 125 144 or 104 000 000 000 000 055 or 062 153 or 113 163 or 123 142 or 102 046 or 060 000 000 000 174 or 066 157 or 117 167 or 127 136 or 106 017 010 027 016 042 or 061 152 or 112 134 or 057 141 or 101 041 or 071 162 or 122 172 or 132 151 or 111 075 or 065 156 or 116 166 or 126 145 or 105 000 015 012 006 074 or 063 154 or 114 164 or 124 143 or 103 051 or 135 050 or 133 073 or 054 072 or 056 076 or 067 052 or 120 170 or 130 147 or 107 004 ASCII-APL Graphic Control Character start of header^ delete space _ or + -* or f + or X * or 8 ? or Q or Y or H or 4 or M or U or D - or 2 -i or K •- or S i or B a or 0 > o w ~ or 6 or 0 or or W F " or 1 ° or J \ or cc or v or p or <= or \ or I = or 5 t or N U or V e or E or 3 or L or T or C or 1 or [ or , or . or 7 or P or X or G null null null null null null null shift in§ backspace end transmission block§ shift out§ null carriage return line feed horizontal tabulate end of transmission^ 60471400 G TABLE A-19. APL CHARACTER CODE TRANSLATIONS, EBCD CONSOLE TERMINAL CLASS 4 (Contd) Network ASCII (Character Mode Use) Terminal EBCD-APL (Transparent Mode Use) Octal Code1 175 176 177 000 000 000 000 175 175 175 175 175 EBCD-APL Graphictt Control Character IL or IDLE or NULL PRE or PREFIX DEL space|§ space99 space9' space99 IL or IDLE or NULLff IL or IDLE or NULL99 IL or IDLE or NULL9| IL or IDLE or NULL!9 IL or IDLE or NULL99 175 IL or IDLE or NULL§§ 175 IL or IDLE or NULL§§ Octal Codem ASCII-APL Graphic Control Character null start of header* delete 000 001 177 047 140 173 175 002 003 005 007 start of text end of text enquire bell vertical tabulate or form feed data link escape, device control 1 thru device control 4, negative acknowledge, or synchronize cancel, end of media, substitute, escape, file separator, group separator, record separator, or unit separator 013 or 014 020 thru 026 030 thru 037 tShown with odd and even parity; odd parity i s the default for this terminal class. (Unless PA=N, the application program receives the same cod e as in character mode.) ttEach input line is assumed to begin in lowerc ase. Input characters are translated to lowercase ASCII characters unless prefixed by the UCS code. Once a case shift occurs, it remains in effect until another case shift code is received, the page width is reached, or the line is transmitted to the host computer. During output, case is preserved by insertion of case shift codes where needed. tttshown with zero parity (eighth or uppermost b it is always zero). §Not transmitted to the host computer after translation during input. §§0utput translation only. yg^s TABLE A-20. ASCII CHARACTER CODE TRANSLATIONS, CORRESPONDENCE CODE CONSOLE TERMINAL CLASS 4 Terminal Correspondence Code (Transparent Mode Use) Octal Codet Correspondence Code Graphictt 000 001 002 003 004 005 006 007 010 011 012 013 space h or h T or t J or j $ or 4 0 or o L or 1 ? or / % or 5 " or ' E or e P or p 60471400 G Control Character Network ASCII (Character Mode Use) Octal Codettt 040 137 or 135 124 or 164 112 or 152 044 or 064 117 or 157 114 or 154 077 or 057 045 or 065 042 or 041 105 or 145 120 or 160 ASCII Graphic Control Character space [ or ] T or t J or j $ or 4 0 or o L or 1 ? or / % or 5 •• or . E or e P or p A-35 • TABLE A-20. ASCH CHARACTER CODE TRANSLATIONS, CORRESPONDENCE CODE CONSOLE TERMINAL CLASS 4 (Contd) Terminal Correspondence Code (Transparent Mode Use) Octal Codet 014 015 016 017 020 021 022 023 024 025 026 027 030 031 032 033 034 035 036 037 040 041 042 043 044 045 046 047 050 051 052 053 054 055 056 057 060 061 062 063 064 065 066 067 070 071 072 073 074 075 076 077 100 101 102 103 104 105 106 107 110 111 \-36 Correspondence Code Graphic^ @ or 2 Control Character PN or PUNCH ON RES or RESTORE BY or BYPASS PF or PUNCH OFF i or I or K or Q or 6 i k q undefined undefined undefined UCS or UPPERCASE BS or BACKSPACE EOB ± or 1 M or m X or x G or g ) or 0 S or s H or h Y or y & or 7 R or r D or d : or ; # or 3 V or v U or u F or f ( or 9 W or w B or b or * or 8 A or a C or c LCS or LOWERCASE RO or READER STOP NL or CR or RETURN LF or LINE FEED HT or TAB 021 000 000 023 IL or IDLE or NULL PRE or PREFIX DEL ASCII Graphic 100 or 062 @ or 2 116 or 156 053 or 075 132 or 172 N or n + or = Z or z 000 000 000 041 or 066 111 or 151 113 or 153 121 or 161 017 010 027 016 174 or 061 115 or 155 130 or 170 107 or 147 051 or 060 123 or 163 110 or 150 131 or 171 046 or 067 122 or 162 104 or 144 072 or 073 000 015 012 006 043 or 063 126 or 166 125 or 165 106 or 146 050 or 071 127 or 167 102 or 142 137 or 055 052 or 070 101 or 141 103 or 143 EOT space h or h T or t J or j $ or 4 0 or o L or 1 ? or / % or 5 " or ' Octal Codettt 056 N or n + or = Z or z ,/*^s$. Network ASCII (Character Mode Use) 054 004 000 033 177 040 133 or 124 or 112 or 044 or 117 or 114 or 077 or 045 or 042 or ! or I or K or Q or 6 i k q I or 1 M or m X or x G or g ) or 0 S or s H or h Y or y & or 7 R or r D or d : or ; # or 3 V or v U or u F or f ( or 9 W or w B or b or w or 8 A or a C or c Control Character device control 1 (tape on) null null device control 3 (tape off) null null null shift in§ backspace end transmission block§ shift out8 null carriage return line feed horizontal tabulate end of transmission^ null escape delete 135 164 152 064 157 154 057 065 041 space I or ] T or t J or j $ or 4 0 or o L or 1 ? or / % or 5 .. or . 60471400 G TABLE A-20. ASCII CHARACTER CODE TRANSLATIONS, CORRESPONDENCE CODE CONSOLE TERMINAL CLASS 4 (Contd) Terminal Correspondence Code (Transparent Mode Use) Octal Codet Correspondence Code Graphictt 112 113 114 115 116 117 120 121 122 123 124 125 126 127 130 131 132 133 134 135 136 137 140 141 142 143 144 145 146 147 150 151 152 153 154 155 156 157 160 161 162 163 164 165 166 167 170 171 172 173 174 175 176 177 000 000 000 000 000 000 175 175 E or e P or p 60471400 G @ or 2 N or n + or = Z or z t or 6 I or i K or k Q or q Control Character PN or PUNCH ON RES or RESTORE BY or BYPASS PF or PUNCH OFF # or 3 V or v U or u F or f ( or 9 W or w B or b or * or 8 A or a C or c undefined undefined undefined ASCII Graphic 105 or 145 120 or 160 E or e P or p 100 or 062 @ or 2 116 or 156 053 or 075 132 or 172 N or n + or = Z or z 041 or 066 111 or 151 113 or 153 121 or 161 ! or 6 I or i K or k Q or q 174 or 061 115 or 155 130 or 170 107 or 147 051 or 060 123 or 163 110 or 150 131 or 171 046 or 067 122 or 162 104 or 144 072 or 073 ± or 1 M or m X or x G or g ) or 0 S or s H or h Y or y & or 7 R or r D or d : or ; 043 or 063 126 or 166 125 or 165 106 or 146 050 or 071 127 or 167 102 or 142 137 or 055 052 or 070 101 or 141 103 or 143 # or 3 V or v U or u F or f ( or 9 W or w B or b or * or 8 A or a C or c 021 000 000 023 000 000 000 LCS or LOWERCASE 017 010 027 016 RO or READER STOP NL or CR or RETURN LF or LINE FEED HT or TAB 000 015 012 006 UCS or UPPERCASE BS or BACKSPACE EOT IL or IDLE or NULL PRE or PREFIX space§§ space§§ space§§ space§§ space§§ space§§ Octal Codem 056 EOB ± or 1 M or m X or x G or g ) or 0 S or s H or h Y or y & or 7 R or r D or d : or ; Network ASCII 'Character Mode Use) DEL 054 004 000 033 177 047 134 136' IL or IDLE or NULLff IL or IDLE or NULL§§ 140 173 175 or 176 001 002 Control Character device control 1 (tape on) null null device control 3 (tape off) null null null shift in§ backspace end transmission block§ shift out§ null carriage return line feed horizontal tabulate end of transmission^ null escape delete a. } or ~ start of header start of text A-37 • TABLE A-20. ASCII CHARACTER CODE TRANSLATIONS, CORRESPONDENCE CODE CONSOLE TERMINAL CLASS 4 (Contd) Terminal Correspondence Code (Transparent Mode Use) Octal Codet Correspondence Code Graphictt Control Character Network ASCII (Character Mode Use) Octal Codettt 175 175 175 175 IL or IDLE or NULLff IL or IDLE or NULLff IL or IDLE or NULL98 IL or IDLE or NULL85 003 005 007 013 or 014 175 175 175 IL or IDLE or NULL88 IL or IDLE or NULL88 IL or IDLE or NULL88 020 022 024 thru 026 175 IL or IDLE or NULL88 030 thru 037 ASCII Graphic Control Character end of text enquire bell vertical tabulate or form feed data link escape device control 2 device control 4, negative acknowledge, or synchronize cancel, end of media, substitute, file separator, group separator, record separator, or unit separator tShown with odd and even parity; odd parity is the default for this terminal class. (Unless PA=N, the application program receives the same code as in character mode.) nEach input line is assumed to begin in lowercase. Input characters are translated to lowercase ASCII characters unless prefixed by the UCS code. Once a case shift occurs, it remains in effect until another case shift code is received, the page width is reached, or the line is transmitted to the host computer. During output, case is preserved by insertion of case shift codes where needed. mShown with zero parity (eighth or uppermost bit is always zero). 8Not transmitted to the host computer after translation during input. ^Output translation only. TABLE A-21. APL CHARACTER CODE TRANSLATIONS, CORRESPONDENCE CODE CONSOLE TERMINAL CLASS 4 Terminal Correspondence Code (Transparent Mode Use) Octal Codet Correspondence Code APL Graphictt 000 001 002 003 004 005 006 007 010 Oil 012 013 014 015 016 017 020 021 022 space -* or — - or T . or J < or 4 o or 0 □ or L \ or / = or 5 ) or ] € or E * or P • A-38 ~ or 2 : or . t or N Control Character undefined undefined undefined undefined Network ASCII (Character Mode Use) Octal Codettt 040 161 or 160 164 or 124 056 or 112 100 or 064 157 or 117 154 or 114 134 or 057 075 or 065 051 or 035 145 or 105 052 or 120 000 000 000 023 136 or 062 072 or 056 156 or 116 ASCII-APL Graphic Control Character space -♦ or *— or T . or J < or 4 o or 0 □ or L \ or / = or 5 ) or ] e or E * or P — or 2 : or . t or N null null null null 60471400 G TABLE A-21. APL CHARACTER CODE TRANSLATIONS, CORRESPONDENCE CODE CONSOLE TERMINAL CLASS 4 (Contd) Terminal Correspondence Code (Transparent Mode Use) Octal Codet Correspondence Code APL 023 024 025 026 027 030 031 032 033 034 035 036 037 040 041 042 043 044 045 046 047 050 051 052 053 054 055 056 057 060 061 062 063 064 065 066 067 070 071 072 073 074 075 076 077 100 101 102 103 104 105 106 107 110 111 112 113 114 115 116 117 120 + or X c or Z 0^S 60471400 G Control Character Graph icft > or 6 \ or I h or K ? or Q undefined undefined undefined UCS or UPPERCASE BS or BACKSPACE E0B " or 1 1 or M => or X V or G ^ or 0 r or S A or H t or Y > or 7 p or R L or D ( or [ < or 3 U or V \ or U _ or F v or 9 co or W l or B - or + ^ or8 oc or A n or C ; or , LCS or LOWERCASE undefined NL or CR or RETURN LF or LINE FEED HT or TAB EOT IL or IDLE or NULL PRE or PREFIX space — or — - or T . or J < or 4 DEL Octal Codettt D or L \ or / = or 5 ) or ] e or E * or P undefined undefined undefined undefined ASCII-APL Graphic 045 or 146 172 or 132 + or X <= or Z 174 151 153 077 > or 6 \ or I 000 000 000 or or or or 066 111 113 121 017 010 027 016 042 or 061 174 or 115 170 or 130 147 or 107 045 or 060 163 or 123 150 or 110 171 or 131 076 or 067 162 or 122 144 or 104 050 or 133 000 015 012 006 074 or 166 or 165 or 137 or 041 or 167 or 142 or 055 or 042 or 141 or 143 or 073 or 004 000 033 177 040 063 126 125 106 071 127 102 053 070 101 103 054 161 or 160 164 or 124 056 or 112 100 or 064 157 or 117 154 or 114 134 or 057 075 or 065 051 or 035 145 or 105 052 or 120 o or 0 "or 2 Network ASCII (Character Mode Use) 000 000 000 023 136 or 062 h or K ? or Q " or 1 I or M » or X V or G Control Character null null null shift in8 backspace end transmission bloc k8 shift out8 a or 0 r or S A or H t or Y > or 7 p or R L or D ( or [ < or 3 U or V \ or U _ or F ■^ or 9 co or W x or B - or + # or 8 cc or A n or C ; or , null carriage return line feed horizontal tabulate end of transmission8 null escape delete space -•• or — - or T . or J < or 4 o or 0 □ or L \= or or 5 / ) or ] e or E * or P — or 2 null null null null A-39 • TABLE A-21. APL CHARACTER CODE TRANSLATIONS, CORRESPONDENCE CODE CONSOLE TERMINAL CLASS 4 (Contd) Terminal Correspondence Code (Transparent Mode Use) Octal Codet Correspondence Code APL Graphictt 121 122 123 124 125 126 127 130 131 132 133 134 135 136 137 140 141 142 143 144 145 146 147 150 151 152 153 154 155 156 157 160 161 162 163 164 165 166 167 170 171 172 173 174 175 176 177 000 000 000 000 175 175 175 175 175 175 : or . t or N + or X <= or Z 175 175 > or 6 \ or I h or K ? or Q Control Character undefined undefined undefined UCS or UPPERCASE BS or BACKSPACE E0B " or 1 1 or M => or X V or G *• or 0 r or S A or H t or Y > or 7 p or R L or D ( or [ < or 3 U or V * or U _ or F v or9 co or W 1 or B - or + # or8 oc or A n or C ; or , LCS or LOWERCASE undefined NL or CR or RETURN LF or LINE FEED HT or TAB EOT IL or IDLE or NULL PRE or PREFIX DEL spaceff space|| space|| space88 IL or IL or IL or IL or IL or IL or IDLE or NULL88 IDLE or NULL88 IDLE or NULL88 IDLE or NULL88 IDLE or NULL88 IDLE or NULL88 IL or IDLE or NULL88 IL or IDLE or NULL88 a^^S Network ASCII (Character Mode Use) Octal Codettt 072 or 056 156 or 116 045 or 146 172 or 132 000 000 000 174 151 153 077 017 010 027 016 or 066 or 111 or 113 or 121 042 or 061 174 or 115 170 or 130 147 or 107 045 or 060 163 or 123 150 or 110 171 or 131 076 or 067 162 or 122 144 or 104 050 or 133 000 015 012 006 ASCII-APL Graphic : t + c or or or or . N X Z > or 6 \ or I n o r K ? or Q " or 1 1 or M = or X V or G ^ or 0 r or S A or H t or Y > or 7 p or R L or D ( or [ 074 or 063 166 or 126 165 or 125 137 or 106 041 or 071 167 or 127 142 or 102 055 or 053 042 or 070 141 or 101 143 or 103 073 or 054 < or 3 U or V \ or U _ or F v or9 co or W 1 or B - or + # or 8 oc or A n or C ; or , 175 or 176 I or r- 004 000 033 177 047 140 173 001 002 003 005 007 013 or 014 020 022 Control Character null null null shift in8 backspace end transmission block8 shift out8 null carriage return line feed horizontal tabulate r^^S end of transmission8 null escape delete start of header start of text end of text enquire bell vertical tabulate or form feed data link escape device control 2 A^^Su • A-40 60471400 G TABLE A-21. APL CHARACTER CODE TRANSLATIONS, CORRESPONDENCE CODE CONSOLE TERMINAL CLASS 4 (Contd) Terminal Correspondence Code (Transparent Mode Use) Octal Codet Correspondence Code APL Graphictt Network ASCII (Character Mode Use) Control Character Octal Codettt 175 IL or IDLE or NULL88 024 thru 026 175 IL or IDLE or NULL88 030 thru 037 ASCII-APL Graphic Control Character device control 4, negative acknowledge, or synchronize cancel, end of media, substitute, file separator, group separator, record separator, or unit separator tShown with odd and even parity; odd parity is the default for this terminal class. (Unless PA=N, the application program receives the same code as in character mode.) y/S^ ttEach input line is assumed to begin in lowercase. Input characters are translated to lowercase ASCII characters unless prefixed by the UCS code. Once a case shift occurs, it remains in effect until another case shift code is received, the page width is reached, or the line is transmitted to the host computer. During output, case is preserved by insertion of case shift codes where needed. tttshown with zero parity (eighth or uppermost bit is always zero). 8Not transmitted to the host computer after translation during input. SSOutput translation only. 60471400 G A-41 • DIAGNOSTICS Four types of in-line diagnostics are available for CCP. • Halt messages. These are delivered to the NPU console when the NPU stops. Normally the NPU contents are dumped to the host prior to restarting. These dumps are processed into a dump listing by the host's Network Dump Analyzer (NDA). • Alarm messages. These are delivered to the network operator's (NOP) console. These alarm messages alert the NOP to check the recent performance of the NPU and the NPU's controlled devices (including terminals). This performance is recorded on the host's engineering file by CE error messages and statistics messages. CE ERROR MESSAGES CE error messages can be divided into five categories as follows: Modem signal messages (error codes 01 through 03, OB and OC) CLA messages (error codes 04 through OA and OD through 10) MLIA messages (error code 11) Coupler messages (error codes 20 through 24 and 26 through 29) TIP or LIP related messages (2A through 37). All other codes are unused. These messages are described in tables B-2 and B-3. NOTE If the user has elected to purchase a network maintenance contract the contents of the engineering file can be easily analyzed by the Hardware Performance Analyzer (HPA). Otherwise the user must devise his own method for making the host's engineering file contents available. • CE error messages. These messages which reflect hardware errors are delivered to the host's engi neering file. The messages should be processed by the HPA or the user's analysis program. • Statistics messages. These messages which reflect hardware performance (normal or erroneous) are delivered to the host's engineering file. The messages should be processed by the HPA or the user's analysis program. STATISTICS MESSAGE Refer to table B-4 for statistics message text definition. HALT CODE MESSAGES AND DUMP INTERPRETATION When the CCP stops the NPU because of an unrecoverable condition caused by either hardware or software errors, the CCP delivers a halt message to the NOP console. See table B-5. This information is also included in the NPU dump. Format of the halt message is: HALT xxxxx yyyy wwww PORT zzzz BUFFER ADDR I I ALARM MESSAGES xxxxx is the address of the program in control I at the time when the halt condition occurred or information relating to the halt code. Alarm messages and the appropriate actions to take in responding to the messages are described in table B-l. yyyy is the halt code (hexadecimal format) NOTE If the user has not elected to purchase a mainte nance contract for CCP, the NOP should devise a system for dumping the engineering day file in the host, and for analyzing NPU error messages in that file. wwww appears only on CLA address out of | range (0005) and CLA status overflow (000D) codes zzzz appears only on buffer halt codes | (000A, 000B, 000C) TABLE B-l. ALARM MESSAGES 60471400 G Message Action From NPU ii/resident MAINTENANCE ALARM COUPLER Find coupler error codes in host day file From NPU ii/resident MAINTENANCE ALARM MLIA Find MLIA error codes in host day file From NPU ii/resident MAINTENANCE ALARM PORT jj Find CLA, modem messages in host day file B-l TABLE B-2. CE ERROR CODES Code (Hexadecimal) Significance Action 01 Not used None. 02 Abnormal data set ready (DSR) or clear to send (CTS) None. This is not an error. It occurs as part of the normal disconnect sequence on some lines. 03 Abnormal data carrier detect (DCD) If this occurs occasionally, ignore it. Otherwise, call a CE or analyst. 04 Unsolicited output data demand (ODD) Check for CLA duplicate address or CLA address switch set between two numbers. This error should not cause concern unless it occurs frequently; if it occurs frequently, call a CE or analyst. 05 C LA address out of range Same as code 04 06 Illegal mux loop cell format Same as code 03 07 Unsolicited input Same as code 04 08 Input mux loop error Same as code 03 09 Output mux loop error Same as code 03 OA TIP event receiver timeout for ODD Same as code 03 OB TIP event receiver timeout for DCD Same as code 03 OC Abnormal secondary data carrier detect (SDCD) This is normal for channels using reverse channel interrupts. For other channels, call a CE or analyst. 0D Excessive CLA status messages If this occurs frequently, call a CE or analyst. 0E Not used None. OF Next character not available (output) Put CLAs in proper priority positions so higher speed or high-use channels are serviced first. If this does not solve problem, call a CE or analyst. 10 Data transfer overrun (input) Same as code OF 11 MLIA error status Same as code 03 Not used None. The CE error code part of the CE mes sage is evidently garbled. 20 Deadman timeout None. This can occur normally due to the host locking out the 255x due to host processing higher priority batch tasks. 21 Spurious coupler interrupt This will occur occasionally. If frequent occur rence, call a CE or analyst. 22 Not used Same as code 12 12 thru IF -"filPv B-2 60471400 F TABLE B-2. CE ERROR CODES (Contd) Code (Hexadecimal) Action Significance 23 Coupler hardware timeout on input Same as code 03 24 Input data transfer terminated by PPU Same as code 03 25 Not used Same as code 12 26 Not used Same as code 12 27 Output data transfer terminated by PPU Same as code 03 28 Hardware timeout on output Same as code 03 29 End of operation (EOP) missing Same as code 03 2A HASP TIP: Too many NAKs received Same as code 03 2B HASP TIP: Bad BCB from HASP TIP Same as code 03 2C HASP TIP: Bad BCB from HASP work station Same as code 03 2D HASP TIP: Workstation restart Not an error if workstation is restarting. Other wise, call CE or analyst. 2E Mode 4 TIP: Card slip error Notify person responsible for maintaining the terminal. Call CE or analyst. 2F Mode 4 TIP: Auto recognition failed If port shows unusually low volume of traffic, someone may have called wrong number. Other wise, call CE or analyst. 30 Mode 4 TIP: No response from terminal Contact terminal operator; have him verify that terminal is properly configured with all switches in correct position. Then call CE or analyst. 31 Mode 4 TIP: Bad response (unexpected response) Same as code 30 32 Mode 4 TIP: Error response from terminal Same as code 30 33 LIP: Timeout on idle block Same as code 03 34 LIP: Protocol failure (no response to frame) Same as code 03 35 LIP: Remote NPU rejected command from local NPU Same as code 03 36 LIP: Bad frame detected by CRC An occasional bad frame is normal. If bad frames occur frequently, call CE or analyst. 37 ASYNC TIP: Parity errors Check for mismatch in parity between terminal and CCP. If not mismatch, check CLA. Call a CE or analyst. 60471400 C B-3 TABLE B-3. CE ERROR MESSAGE TEXT DEFINITIONS Error Codes (Hexadecimal) jtfaE^v Text Definition 01 00 Sl thru 10 S2 where: Port number (CLA address) CLA status byte 1 (logical format) Sl S2 CLA status byte 2 (logical format) SI and S2 not used for ECs 04-07, 0A, 0B, 10 CLA status bvte 1 bits CTS DSR DCP RI QM SQD ILE OLF PLA status bvte 2 bits DTO NCNA I Unused Unused where: 11 CTS DSR DCD RI QM SQD ILE OLE DTO NCNA ET ILE ET where: ILE LD AL LS 20 where: B-4 Clear to send Data Set readv Data carrier detect Ring indicator Qualitv monitor Signal quality detector Input loop error OutDut loop error Data transfer overrun Next character not available LD AL Error type (00 = Error condition restored 01 = Error counts given 02 = MLIA failure) Input loop error count ) , ,. . . ... _.- _, Lost data count "ft 1'sled ,fhf = 01 Alarm count ( <2 bV^ each) NS LS NS Last state Current state 60471400 F TABLE B-3. CE ERROR MESSAGE TEXT DEFINITIONS (Contd) Error Codes (Hexadecimal) Text Definition EH 21 thru 24 ST where: CP and ST Coupler status word 27 thru 29 | CP | ST | where: CP and ST Coupler status word 1P1ooI 2A thru 2D where: P 2E thru 32 00 where: 33 thru 36 Port number (CLA address) CA TA where: NID Port number (CLA address) Node ID of remote NPU NID 37 00 ERR Port number (CLA address) Cluster address Terminal address Device type Error count (not used on message number 37) CA TA DT ERR 00 DT CA TA where: DT TC Port number (CLA address) Cluster address Terminal address Device type Terminal class CA TA DT TC Coupler Status Word (CP and ST) 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Ll Alarm — Chain address zero Not used CYBER channel parity error ■ Hardware timeout NPU status accepted Order word loaded Memory parity error Memory protect fault L— NPU status register loaded •— Memory address register loaded L- External cabinet alarm •—Transmission complete ^■Transfer terminated by NPU ••Transfer terminated by PPU 60471400 D B-5 TABLE B-4. STATISTICS MESSAGE TEXT DEFINITIONS Secondary Function Code 01 Te x t D e fi n i t i o n NPU STATISTICS 1 where: 2 Word Word Word Word Word Word Word Word Word Word Word 10 1 2 Statistics Words 11 Service messages generated Service messages processed Bad service messages received Blocks discarded due to bad address Packets/blocks discarded due to bad format Times at no regulation Times at regulation Level 3 Times at regulation Level 2 Times at regulation Level 1 Times at regulation Level 0 Packet protocol timeouts 8 9 10 11 NOTE: Each word is composed of two bytes, 02 TRUNK/LINE STATISTICS p 00 HO where: Word 1 LRN Word 2 Word 3 Word 4 Port Host ordinal Link remote node - ID of NPU at opposite end of trunk (always 0 for lines) HO LRN ^s Trunk/line statistics words (2 bytes each) Word Word Word Word 03 1 2 3 4 Number Number Number Number of of of of blocks transmitted blocks received characters transmitted in good blocks characters received in good blocks TERMINAL STATISTICS p where: 00 K0 CA TA DT H O Word 1 Word 2 Word 3 P Port HO Host ordinal CA Cluster address TA Te r m i n a l a d d r e s s DT Device type (see below) Terminal statistics words (2 bytes each) Word 1 Number of good blocks transmitted Word 2 Number of good blocks received Word 3 Number of bad blocks bit DT = B-6 Device Terminal Class Device type - byte 13 60471400 C TABLE B-4. STATISTICS MESSAGE TEXT DEFINITIONS (Contd) Secondary Function Code 03 Te x t D e fi n i t i o n TERMINAL STATISTICS (Contd) Device 0 1 2 Console Card Reader Line Printer Card Punch Plotter HASP (postprint) 200UT HASP (postprint) 200UT 714X HASP (postprint) HASP (postprint) HASP (preprint) Class 1 2 4 5 6 7 8 9 10 11 12 13 14 jrGUP*^ 15 16 17 M33, etc. 713 2741 M40 H2000 751-1 T4014 HASP (postprint) 200UT 714X 711-10 714 714 HASP (preprint) HASP (preprint) HASP (preprint) HASP (preprint) 2780 3780 2780 3780 2780 3780 2780 3780 734 Device = 5 reserved for internal host/NPU use = 6 reserved for expansion = 7 reserved for installations Terminal Class = 18-27 reserved for expansion = 28-31 reserved for installations y^s When such a halt occurs, the host normally executes an upline dump of the NPU main memory, micromemory, and the file 1 registers. Thereafter, the host attempts to reload the NPU main memory. This is accomplished directly through the coupler for local NPUs; it is accomplished by use of overlays in the local NPU connected to the remote NPU in the case of a remote NPU. 60471400 G For the first two loading attempts, a dump is normally taken. Thereafter, dumps are suppressed. The NPU can be stopped locally by master clearing it using the MASTER CLEAR switch on the maintenance control panel. B-7 TABLE B-5. HALT CODES Code (Hexadecimal) Significance Action >C3tf??y 0001 Power failure Reapply power, reload CCP (for momentary failure). Call CE or analyst. 0002 Memory parity error Call CE or analyst. 0003 Program protect error Check that software breakpoint not accidently left set. Call CE or analyst. 0004 Interrupt count <0 Same as code 0002 0005 MLIA failure (reported by MLIA hardware status) Same as code 0002 0006 Overran CIB Same as code 0002 0007 Branch to zero detected Same as code 0002 0008 Invalid halt code Same as code 0002 0009 Ran out of buffers Check installation handbook to find if sufficient mem ory available to handle system configuration. Call CE or analyst. 000A Duplicate release of buffer Same as code 0002 000B Buffer chain error during buffer get Same as code 0002 000C Buffer out of range Same as code 0002 000D Coupler alarm condition Same as code 0002 000E Monitor stopped Same as code 0002 000F Too many worklists from one CLA Same as code 0002 0010 Force load service message received This is normal if a force load message was entered. Otherwise, take same action as code 0002. 0011 Bad MLIA initialization status Same as code 0002 0012 Invalid halt code Same as code 0002 0013 Chain address = 0 Same as code 0002 0014 Invalid halt code Same as code 0002 0015 Invalid coupler orderword Same as code 0002 0016 Invalid halt code Same as code 0002 0017 Invalid halt code Same as code 0002 /"aaiS\ A^S. A^tS /*^!K B-8 60471400 D In some cases, a halt code message is not generated. In these cases the dump listing, as generated from the host by the Network Dump Analyzer (NDA) program, must be consulted to find the cause of the failure. In all eases where the cause of stoppage is not apparent, the CE or analyst will probably want to consult the dump listing. The format of the listing is shown later in this section. HALT CODES Halt codes can be divided into three categories: 1) those primarily resulting from incorrect switch settings, 2) those caused by hardware malfunctions, and 3) those that can be either hardware or software problems. The first category includes detection of a duplicate CLA address (halt code 0012). This condition is usually caused by two CLA switches being set to the same address. Such a fault can normally be corrected by the operator resetting the switches. In the second category, the halt codes are the following: • power failures (code 0001) • memory parity error (code 0002) • memory protect bit error (code 0003) • bad MLIA initialization status (code 0011) Such conditions are usually caused by some type of hardware failure and normally must be repaired by a CE. The third category of halt codes (all those not already specified) are caused either by a hardware failure or by a software error. To correct this category of problems, the CE should normally first be called to check the hardware. If the hardware is functioning properly, a system analyst should be called. 60471400 F NOTE Have all upline dumps taken by the host available for the CE and/or the system analyst. DUMP INTERPRETATION WITHOUT HALT MESSAGE At most times when a halt occurs, halt codes are sent to the NOP console and dump interpretation is not needed. However, 1) if a halt occurs after loading but before com pletion of initialization, or 2) if the system becomes trapped in a looping condition during initialization (before the CCP header prints), dump interpretation may be neces sary to determine which halt has occurred, or in which subroutine of the initiation section the program is looping. INTERPRETATION INSTRUCTIONS When interpreting the upline dump printout to determine the cause of a halt or looping condition, first examine the contents of memory location 30^6 as reflected in the dump printout. If non-zero, a halt has occurred and the halt code value is contained in that location. If memory location 30ig equals zero, examine the address of the NPINTAB entry in the address table which begins at fixed memory address 150ie« (This is the table which is displayed at the end of a successful initialization. NPINTAB has a fixed address; it is the last non-zero entry in the address table.) Table B-6 lists the contents of the address table. Entry NPINTAB gives the starting address for the NPINTAB table, the format of which is illustrated in figure B-l. The NPISFL entry in the NPINTAB table contains the flags which mark the initialization subroutines that have completed running when the looping condition occurred. This information should be given to the system analyst along with the dump printouts. A sample dump, formatted by NDA, is shown in figure B-2. B-9 TABLE B-6. ADDRESS TABLE Location Address Title/Routine BYWLCB Worklist control block 1 JSWLADDR WL entry by LEVELNO 2 B1TCB Internal processing TCB 3 B1BUFF Internal processing block 4 JKMASK Interrupt masks 5 JKTMASK PBAMASK save area 6 CBTIMTBL TIMAL table 7 JACT PD controller table 8 BECTLBK Buffer control block (BCB) 9 BYSTAMP Buffer stamp area A CLBFSPACE Buffer space in number of small buffers B 0 C NAPORT Port D BQCIB Circular input buffer (CIB) E 0 F CGLCBS Line control blocks (LCB) 10 CHSUBLCB Sub line control blocks 11 CGTCBS Terminal control blocks (TBC) 12 BJTIPTYPT TIP type table 13 NJTECT Terminal characteristics table NPINTAB Initialization complete table 17 CCPVER CCP version address 18 CCPCYC CCP cycle address 19 CCPLEV CCP level address 15016 0 — Base table a**is ~~ Mux — sub system Lines — and TIPs 14 15 16 Initializa— tion Infor mation IA NOTE: Fix ed table begins at main me mory location 150.fi. Contents of table are displayed at end of 8i successful initialization. B-10 60471400 C 15 14 13 12 11 10 WORDO (NPSODD) 0 0 0 0 0 0 WORD 1 (NPISFL) B15 WORD 2 (NPBMLS) Y Y Y Y Y Y Y Y B7 B6 B5 B4 B3 B2 Bl BO Y Y Y Y Y Y Y Y NPSODD Duplicate CLA address, where XX... XX is the duplicated CLA address between 01 lg and FE1fi. 00._ indicates preset value (no duplicates), and FFlfi indicates no response. NPISFL Initialization completion sequence flags, where B15 and B7 through BO indicate start or completion of various tasks as follows: B15- All buffers initialized, system initialization completed B7 - Second phase of buffer initialization started/completed B6 - Initialization of fixed lines started/completed B5 - Initialization of MLIA started/completed B4 - Application initialization started/completed B3 - Miscellaneous NPU console initialization started/completed B2 - Initialization of worklist control blocks started/completed Bl - Initialization of buffers started/completed BO - Set up program protect bits started/completed NOTE A function is completed if the next higher bit is set, otherwise it was started but not completed. NPBMLS Bad MLIA initialization status, where any value for YY..YY other than 0009-fi indicates bad status. Call a Customer Engineer. Figure B-l. NPINTAB Table Starting Address Format n 60471400 D B-ll NPU DUMP = 0003 NDA (DN=03) CHANNEL 04 EQUIPMENT TIME DATE 07 00.14.05 NPU NAME NDA VER 1.1 header information Record 1 78/09/02 NODE2 BASE FILE 1 REGISTERS \DDRESS oooooo 000010 000020 000030 000040 000050 000060 000070 000080 000090 0000A0 0000B0 OOOOCO OOOODO 0000E0 0000F0 oooo 0560 007F AAD8 0001 0000 OEDA 1175 0F16 12B3 86C5 004D 0000 001F BDF8 0000 0508 0F00 0064 165E B720 0000 0000 0001 0014 0000 1F27 004D 0000 0000 0000 0000 0500 0000 0064 ACD8 0000 0200 36B2 0005 0000 B5B0 0018 0000 0000 BDCO 2C83 0000 COUPLER STATUS REGISTER NPU STATUS WORD ORDERWORD 0000 AEE0 0D00 0004 0001 0007 0000 0000 OOFE 0085 8000 0000 B723 . .. 0000 0006 401F 0050 B590 OOOO A180 0000 00F0 0000 0071 0000 0000 oooo 0000 BE85 0000 0000 0000 AEE3 00E0 000F 0001 0000 0000 OOOF OOOO B59F OOOO OOOO 7D08 OOOO OOOO OOOO OOOO F ~~ 3720 BABE 7D55 OOOO Micromemory dump 0801 Record 2 0304 — File 1 registers in groups of 16 2000 0008 words per line. Code is hexa OOOC decimal OOOO 00F8 OOOO OOOO OOOO OOOO AA2D _ 0000 "I oooo oooo J A A^S. For a 2552, both base and mux sides of main memory are dumped. The base side precedes the mux side. Identify a record by addresses MACROMEMORY ADDRESS 000000 OBOO 000010 0011 000020 0000 000030 0000 000040 oooo 000050 0001 000060 0001 000070 0002 000080 0001 000090 oooo 0000F0**0000 000100 oooo 000110 oooo 000120 F010 000130 oooo 000140 1400 000150 1125 000160 1518 000170 OOOO 000180 5400 OBOO 0807 OOOO OOOO 0044 OOOO 472C 0019 0001 OOOO OOOO 1400 1400 1400 1400 OOOO 11F5 1563 OOOO 4761 OBOO OOOO OOOO OOOO OOFE 0044 1263 0001 457A OOOO OOOO 1BA8 3715 1C4E 375D 1400 1064 15CA E8FD 12AF OBOO OBOO OOOO OOOO OOOO OOOO OOOO OOOO OOOO 0002 OOOO 0030 111F FFFE 0019 0001 0 0 0 1 . . . OOOO OOOO OOOO OOOO OOOO OOOO 1400 OOOO 1400 oooo 1400 oooo 1400 D108 1400 1065 OOOO 1699 AAD8 E600 OOOO 1071 CEF6 E 5400 0000 0000 0000 0001 0052 0091 0002 0000 0000 OOOO 1C0F 372D 3751 3781 3781 OOOO OOOO OOOO 6400 A9F6 OOOO OOOO OOOO 0001 OOOO 0001 0001 OOOO OOOO 0040 OOOO OOOO oooo oooo oooo oooo Main memory dump Record 3 If lines have identical information, lines after the first are omitted. New line with unique information is flagged with **. Sixteen words per line. Code is hexadecimal. AF21 oooo 12B3 Figure B-2. Sample NPU Dump B-12 60471400 D GLOSSARY Accounting Data Data collected by the TIP which counts the amount of I/O batch data passed to or received from a terminal. Examples: at the end of a card reader input job, the TIP informs the host of the number of cards read; at the end of a printer output, the TIP informs the host of the number of lines of text sent to the printer. Address A location of data (as in the main or micro NPU memory) or of a device (as a peripheral device or terminal). The NPU main memory is paged. APLA scientific programming language characterized by powerful operators defined as single keyboard symbols. jtf'wy&'^s Application Program A program resident in a host computer. The program provides an information storage, a retrieval, and/or processing service to a remote user via the data communications network and the Network Access Method. Async Protocol The protocol used by asynchronous, teletypewriter-like devices. For CCP, the protocol is actually the set of protocols for eight types of real terminals. The NPU/terminal interface is handled by the ASYNC TIP. Autoinput An output mode that appends the first 20 characters of the output message to the input reply. Autorecognition A capability offered to most terminals which allows the TIP to generate some device characteristics for the terminal, rather than having the terminal generate the information for itself. Bandwidth • For CCP, bandwidth indicates the transfer rate (in characters per second) between the NPU and the terminal. Base System Software The relatively invariant set of programs in CCP that supplies the monitor, timing, interrupt handling, and multiplexing functions for the NPU. Base software also includes common areas, diagnostics, and debugging utilities. Batch File Command A command from RBF in the host which alters the file characteristics of subsequent data transfers for a batch device. The characteristics which can be changed include: code type, suppressing carriage control on output, changing file limits (maximum size of a file in characters), and whether or not lace cards should be generated for a card punch. For HASP and BSC terminals, transparent mode and 026/029 card type can be changed from a terminal through a request to RBF. 60471400 G Binary Synchronous Communications (BSC) A communications protocol supported by the BSC TIP. This protocol connects IBM 2780 or 3780 terminals to the NPU using half-duplex synchronous transmissions in a point-to-point mode. The terminals have batch devices which use EBCDIC code. Transparent data exchanges are permitted. The terminals are structured to have a virtual console (interactive device). This is composed of a card reader for input and a printer for output. BIPBlock interface package. A group of modules that provide routing, service message handling, and some common TIP subroutines including assistance in IVT block and PRUB formation for upline messages. By making hold/queue decisions for downline batch messages, the BIP also has some batch data stream flow control capability. Block A unit of information used by networks. A block consists of one or more words (2 bytes/word) and contains sufficient information to identify the type of block, its origin, destination, and routing. Differing block protocols apply to the host/NPU and the NPU/terminal interfaces. Block Protocol The protocol governing block transfers of information between the host and the local NPU. Data is transferred in IVT blocks or PRU blocks (PRUBs). Break An element of a protocol indicating an interruption in the data stream. User breaks (a break normally entered by an operator at an interactive terminal) stops delivery of a message from the host. Broadcast Message A message generated by the system or by an operator using the system. The message is sent to one (broadcast one) or all (broadcast all) of the terminals in the system. Buffer A collection of data in contiguous words. CCP assigns two sizes of buffers for data and two other sizes of buffers for internal processing. A buffer usually has a header of one or more words. Data within a data buffer is delimited by pointers to the first and last characters (data buffers are character oriented). If the data cannot all fit into one buffer, an additional buffer is assigned and is chained to the current buffer. Buffer assignment continues until the entire message is contained in the chain of buffers. Buffers are chained together only to the forward direction. Buffering The process of collecting data together in buffers. Ordinarily, no action on the data is taken until the buffer is filled. Filled buffers include the case where data is terminated before the end of the buffer and the remaining space is filled with extraneous matter. C-l Buffer Threshold The minimum number of buffers available for assignment to new tasks. As the buffer level falls toward the threshold, new tasks are rejected (regulation). Contention The state that exists in a bidirectional transmission line when both ends of the line try to use the line for transmission at the same time. All protocols contain logic to resolve the contention situation. ByteA group of contiguous bits. For data handling within the NPU/host interface, a byte is 8 bits; IVT uses 7-bit ASCII characters with the eighth bit reserved for parity; PRU uses 6-bit display code right justified in the 8-bit space. Control Blocks (1) The types of blocks used to transmit control (as opposed to data) information; (2) Blocks assigned for special configuration/status purposes in the NPU. The major blocks are line control blocks (LCB), logical link control blocks (LLCB), logical channel control blocks (LCCB), terminal control blocks (TCB), queue control blocks (QCB), buffer maintenance control blocks (BCB), mux line control blocks (MLCB), text processing control blocks (TPCB), and diagnostics control blocks (DCB). Cassette The magnetic tape device in an NPU used for bootstrap loading of off-line diagnostics and (in remote NPUs) the bootstrap load/dump operation. CCPCommunications Control Program. This set of modules performs the tasks delegated to the NPU in the network message processing system. CE Error Message A diagnostic message sent upline to the host from the NPU. The message contains information concerning hardware and/or software malfunctions. Character A coded byte of data. Host applications processing interactive data expect ASCII characters; host applications processing batch data expect display code. Terminals expect a wide range of codes. The TIPs are responsible for translating between terminal codes and host codes. CIBCircular Input Buffer. This fixed buffer is used by the mux subsystem to collect all data passing upline from the multiplexer. The buffer is controlled by a put pointer for the multiplexer and a pick pointer used to demultiplex data to individual line-oriented data buffers. Command Driver The hardware driver that controls the mux subsystem. Common Area Areas of main memory dedicated to system and global data. These are usually below address 100016. Communications Supervisor (CS) A portion of the network software resident in the host. CS is written as an application program; the Communications Supervisor coordinates the networkoriented activities of the host computer and of the lines and terminals logically linked to it. Configuration See System Configuration. Connection Number (CN) A number specifying the path (line) used to connect the terminal through the NPU to the host. Console A terminal devoted to network control processing. Examples of consoles are the Network Operator's (NOP) terminal and the Local Operator's (LOP) terminal. A console attached to the NPU can be used for offline processing. C-2 Coupler The hardware interface between the local NPU and the host. Transmissions across the coupler use block protocol. CRCCyclic Redundancy Check. A check code transmitted with blocks/frames of data. It is used by several protocols including the HASP and CDCCP protocols. -«% Cross The software support system for CCP. These programs, which are run on the host, support source code programming in PASCAL, macroassembler, and microassembler languages. The compiled or assembled outputs of the Cross programs are in object code format on host computer files (source code is also kept in host files). The object code files are processed by other Cross programs and host installation programs into a downline load file for an NPU. DataInformation processed by the network or some components of the network. Data usually has the form of messages, but commands and status are frequently transmitted by using the same information packets as data (for instance, system messages). Data Compression The technique of transmitting a sequence of identical characters as a control character and a number representing the length of the sequence. HASP and BSC protocols support data compression. Data Set A hardware interface which transforms analog data to digital data and the converse. DDLTs Special diagnostic programs which use a highly structured table technique to aid the troubleshooter in isolating a problem. Debugging The process of running a program to rid it of anomalies. CCP supplies debugging aids for programs (TUP, PBTIPDG, and PBDEBUG) and for run-time PASCAL programs (QDEBUG and its associated programs). Diagnostics Software programs or combinations of programs or tables which aid the troubleshooter in isolating problems. 60471400 G ,'^^S. Direct Calls The method of passing control directly from one program to another. This is the usual transfer mode for CCP. Some CCP calls are indirect, through the monitor. Such OPS level indirect calls pass information to the called program through parameter areas called worklists. See Worklist. Directories Tables in CCP which contain information used to route blocks to the proper interface and line. There are directories for source and destination node and for connection number. A routed message is attached to the TCB for the line over which the message will pass. DMADirect Memory Access. The high-speed I/O channel to the NPU main memory. This channel is used for host/NPU buffered transfers. DNDestination Node. The network node to which a message is directed; for instance, the DN of an upline message may be the host process (CS) which passes the message to the application program responsible for processing the message. Downline The direction of output information flow, from host to I NPU to terminal. DumpThe process of transferring the contents of the NPU main memory, registers, and file 1 registers to the host. The dump can be processed by the Network Dump Analyzer in the host to produce a listing of the dumped hexadecimal information. EchoThe process of displaying a keystroke on a terminal's display. Echoing can be done from the TIP, from a modem, or from the terminal itself. FEFormat Effectors. See below. FileA unit of batch data. Files are transferred between application programs and terminals by using PRUBs on the NPU's host side and transmission blocks on the NPU's terminal side. A file contains one or more records. Example: a card reader job can consist of a file containing the card image records of all the cards in the job deck. File Registers The two sets of microregisters (file 1 and file 2) in the NPU. File 1 registers contain parameter information that is reloaded whenever the NPU is initialized. Microprograms using file 1 registers may also change values in them. File 2 registers are invariant firmware registers that come preprogrammed with the NPU. 60471400 G Format Effectors Characters in an output data stream that determine the appearance of data at the terminal. A format effector usually takes the form of a single character in the output message. For printers, the character is translated by the output side of the TIP into a combination of carriage returns, line feeds, or spaces. Similarly, FEs for displays can command new lines, screen clearing, or cursor positioning. Frame A medium for transmitting data across a high-speed link. Frames of different types are used by the LIP and by the X.25 TIP. A frame provides high data density in bit-serial format over data-grade lines. Data assurance is also provided. Frame (LIP) The basic communications unit used in trunk (NPU to NPU) communications. Frames are composed of control bytes, a CRC sum, and (in some cases) data bytes in sub-block sequence. A sub-block may be a block protocol block or a part of a block. Frames are transmitted as a sequence of bytes through the mux subsystem. Frame (MUX) The mux subsystem uses a hardware-controlled frame on the input and output mux loops. Full Duplex (FDX) A transmission mode allowing data transfer in both directions at the same time. An FDX system requires a dual set of data lines, each set dedicated to transmission in one direction only. Function Codes Codes used by the service module to designate the type of function (command or status) being transmitted. Two codes are defined: Primary Function Code (PFC) and Secondary Function Code (SFC). See Appendix C of the CCP System Programmer's Reference Manual for definitions of these codes. Global Variables PASCAL variables which are defined for use by any CCP program. Contrast global variables with local variables, which are identified only within a program. Halt Codes Codes generated by the NPU when it executes a soft-stop. These codes, which indicate the cause of the stoppage, are sent to the host's engineering file. I They are also contained in a CCP dump. | Half Duplex (HDX) A transmission mode allowing data transfer in one direction at a time. Normally a single set of data lines carry input, output, and part of the control information. Contention for use is possible in HDX mode and must be resolved by the protocol governing line transfers. C-3 HASPA protocol based on the BSC protocol; it is used by HASP workstations. A workstation has both interactive and batch devices. The standard code of all HASP devices is EBCDIC; however, transparent data exchanges with the host are also permitted. The HASP TIP converts interactive HASP data between EBCDIC transmission blocks and ASCn IVT blocks; it converts batch HASP data between EBCDIC transmission blocks and display code PRUBs. Header The portion or portions of a message holding information about the message source, destination, and type. During network movement, a message can acquire several headers. For example, during movement of a message from a terminal to the host over an X.25/NOS network, the message acquires the following headers: one at the terminal (also a trailer), one for the frame, one for the packet, and another for the host block. Headers are discarded by the appropriate stage of processing, so that in this example, the host sees only the host block header. Conversely, headers are generated and discarded as needed downline, so that the terminal sees only the terminal header (and trailer). High-Speed Synchronous Line A data transmission line operating at or above 19,200 baud. These lines are normally used for local LIP/remote LIP transfers and for PDN/NOS network transfers. Interrupts A set of hardware lines and software programs that allow external events to interrupt NPU processing. Interrupting programs allow preferential processing on a priority basis. The lowest priority level is processed by an OPS monitor. I V TInteractive Virtual Terminal. A block protocol format for interactive terminals. CCP TIPs convert all upline interactive messages to this format (exception: no transformations are made to transparent data except to put the messages into block format). By this method, application programs in the host need only to be able to process interactive data in IVT format rather than in the multiplicity of formats that real terminals use. Downline messages from the host to interactive terminals (including virtual consoles) are converted from IVT to real terminal format. IVT processing is controlled by the TIPs; the TIPs use some common IVT modules. IVT Commands A group of commands that aUow the operator at the terminal or a host application program to control some of the IVT transforms made by a TIP. These commands can (1) change the destination of the terminal characters for breaks and cancel signals, (2) select output page format (such as page width and length, number of padding characters after a line feed or carriage return), (3) designate parity type, terminal class, and other terminal-related features. HIPHost Interface Package. The CCP program which handles block transfers across the host/local NPU interface. The HIP transfers control blocks and data blocks (IVT blocks or PRUBs). LCBLine Control Block. A table assigned to each active line in the system. It contains configuration infor mation as well as current processing information. HostThe computer that controls the network and contains the applications programs that process network messages. LCCBLogical channel control block. A data structure holding information about logical channels. These are used by the X.25 TIP for terminals connected to the NOS network through a public data network. ID- LineA connection between an NPU and a terminal. Identifiers. Identifiers can refer to port/subport, nodes, lines, links, or terminals. Any hardware element or connection can have an ID, normally a sequentially assigned number. Initialization The process of loading an NPU and optionally dumping the NPU contents. After downline loading from the host, the NPU network-oriented tables are configured by the host so that all network processors have the same IDs for all network terminals, lines, trunks, etc. Input Buffer A data buffer reserved by CCP for receiving an upline message for the host. These buffers are assigned and released dynamically. Contrast with the CIB on the mux subsystem interface. Interface (NPU) The set of hardware and software that permits transfers between the NPU and an external device. There are three principal interfaces: to the host through a coupler (block protocol in IVT or PRU format handled by a HIP), to a neighbor NPU via the mux subsystem (CDCCP protocol handled by a LIP), and to the terminals (various protocols). Standard terminal protocols are handled by the ASYNC, BSC, MODE 4, HASP, and X.25 TIPs. C-4 Link A connection between two NPUs or an NPU and a host. In release 3.1, a line which connects NPUs is the same as a trunk. LIPLink Interface Package. The CCP program which handles frame transfers across a trunk; that is, across the connection between a local and a remote NPU. A LIP uses CDCCP protocol and interfaces on the local NPU side to the HIP. On the remote NPU side, the LIP interfaces with the appropriate TIP. In both local and remote NPUs, the LIP interfaces with the mux sub- system for transfer across the trunk. LLCBLogical Link Control Block. A table assigned to each logical link in the system which touches this NPU. The table contains configuration information as well as current processing information. Load The processing of moving programs downline from the host and storing them in the NPU main and micromemory. Loading of a remote NPU is accomplished by the host through the use of overlays in the local NPU. 60471400 G ^3s!v C-6 60471400 G Port (P) The physical connection in the NPU through which data is transferred to/from the NPU. Each port is numbered and supports a single line. Subports are possible but not used in this version of CCP. PPU (Peripheral Processing Unit) The part of the host dedicated to performing I/O transfers. The coupler connects the PPU directly to an NPU. Priority Level A set of 17 levels of processing in the NPU. Priority levels are interrupt driven. The OPS monitor processes at the lowest priority level; that is, at a level below any interrupt-driven level. Program A series of instructions which are executed by a computer to perform a task; usually synonymous with a module. A program can be composed of several subprograms. Protect System A method of prohibiting one set of programs (unprotected) from accessing another set of programs (protected) and their associated data. The system uses a protect bit in the main memory word. Protocol The complete set of rules used to transmit data between devices. This includes format of the data and commands, and the sequence of commands needed to prepare the devices to send and receive data. PRUPhysical record unit. A host batch file format. Batch data is exchanged with the host in PRU block (PRUB) format to minimize the amount of conversion a host performs to make network data compatible with host file handling capabilities. PRU Commands A set of commands from the host or a terminal that changes batch device or batch file characteristics, alters batch data stream flow, or transmits accounting data to the host. All batch file and batch device commands can come from the host. A few batch file commands can also come from the terminal. Some batch stream flow commands come from the host; others come from the terminals. Accounting data commands come only from the terminals. Queues Sequences of blocks, tables, messages, etc. Most NPU queues are maintained by leaving the queued elements in place and using tables of pointers to the next queued element. Most queues operate on a first-in-first-out basis. A series of worklist entries for a TIP is an example of an NPU queue. Record (1) A data unit defined for the host record manager (PRU); (2) a data unit defined for HASP workstations. In either case, a record contains space for at least one character of data and normally has a header associated with it. HASP records can be composed of subrecords. Regulation The process of making an NPU or a host progressively less available to accept various classes of input data. The host has one regulation scheme, the host and mux interfaces of a local NPU have another scheme, and the mux interface to a neighbor NPU has a third regulation scheme. Some types of terminals (for instance, HASP workstations) may also regulate data. Data classifications are usually based on batch, interactive, and control message criteria. Remote NPU An NPU connected only to other (local) NPUs. A remote NPU lacks a coupler; therefore it can have no direct connection to the host. Response Messages A subclass of service (network control) messages directed to the host that are normally generated to respond to a service message from the host. Response messages normally contain the requested information or indicate the requested task has been started/ performed. Error responses are sent when the NPU cannot deliver the information or start the task. A class of unsolicited response messages is generated by the NPU to report hardware failures. Routing The process of sending data/commands through the NPU to the internal NPU process or to an external device (for instance, a terminal). The network logical address (DN, SN, CN) is the primary criterion for routing. The NPU directories are used to accomplish the routing function. Service Channel The network logical link used for service message transmission. For this channel, CN=0. The channel is always configured, even at load time. PRUBPhysical record unit block. A block format for batch terminals that is compatible with the host's PRU (batch file) handling capabilities. CCP TIPs convert all upline batch messages to this format (exception: no transformations are made to transparent data except to put the messages into PRUBs). By this method, application programs in the host need only to be able to process batch data in PRU format rather than in the multiplicity of formats which real terminals use. Downline messages from the host to real batch devices are converted from PRUB to real terminal format. PRUB processing is controlled by the TIPs with the help of the BIP. SFCSubfunction code. See Function Codes. Public Data Network A network that supports the interface described in the CCITT protocol X.25. Source Node (SN) The network node originating a message or block of information. 60471400 G Service Message (SM) The network method of transmitting most command and status information to/from the NPU. Service messages use CMD blocks in the block protocol. Service Module (SVM) The set of NPU programs responsible for processing service messages. SVM is a part of the BIP. | C-7 State Programs Programs written in state programming language. These programs usually are part of a TIP (some are common to all TIPs), but do not operate on the OPS level. Instead they are reached by a call to the mux level or are operated automatically by the multiplex subsystem. State programs process modem signals, input data, and output data. Text processing is primarily performed by state programs. State Program Tables Tables used by the mux subsystem to locate the next state program to execute. Statistics Service Message A subclass of service messages that contain detailed information about the characteristics and history of a network element such as a line or a terminal. Status Information relating to the current state of a device, line, etc. Service messages are the principal carriers of status information. Statistics are a special subclass of status. String A unit of information transmission used by the HASP protocol. One or more strings compose a record. A string can be composed of different characters or contiguous identical characters. In the latter case, the string is normally compressed to a single character and a value indicating the number of times the character occurs. Subport One of several addresses in a port. In this CCP configuration, subport is always equal to 0. Subprogram A series of instructions which are executed by a computer to perform a task or part of a task. A subprogram may be called by several programs or may be unique to a single program. Subprograms are normally reached by a direct call from a program. Supervisory Message A message block in the host not directly involved with the transmission of data, but which provides information for establishing and maintaining an environment for the communications of data between the application program and NAM, then through the network to a destination or from a source. Supervisory messages may be transmitted to an NPU in the format of a service message. Switching The process of routing a message or block to the specified internal program or external destination. System Configuration The process of setting tables and variables throughout the network to assign lines, links, terminals, etc., so that all elements of the network recognize a uniform addressing scheme. After configuration, network elements accept all data commands directed to/through themselves and reject all other data and commands. C-8 Terminal An element connected to a network by means of a communications line. Terminals supply input messages to, and/or accept output messages from, an application program. A terminal can be a separately addressable device comprising a physical terminal or station, or the collection of all devices with a common address. Terminal Control Block (TCB) A control block containing configuration and status information for an active terminal. TCBs are dynamically assigned. Terminal Interface Packages (TIPs) NPU programs which provide the interface between real terminal format and IVT or PRU format. The standard TIPs are ASYNC, BSC, HASP, Mode 4, and X.25 with PAD subTIP. TIPs are responsible for data conversion and for some error processing. Timeout The process of setting a time for completion of an operation and entering an error processing condition if the operation has not finished in the allotted time. Timing Services The subset of base system programs which provide timeout processing and clock times for messages, status, etc. Timing services provide the drivers for the real-time clock. Trailer Control information appended to the end of a message unit. A trailer contains the end-of-data control signals. Trailers can be generated by the terminal or by an intermediate device such as a frame generator. Not all headers are matched with trailers, although some devices split their control information between a header and a trailer. The trailer usually contains a data assurance field such as a CRC-16 or a checksum. Like headers, trailers are generated and discarded at various stages along a message unit's path. Transparent Mode A data mode in which the TIP minimally formats the message and does no code translation. For most TIPs, transparency can occur on both upline and downline messages (files). If transparent mode is selected, the entire message/file must be in the receiving device's code and format (including all required header and trailer information). In some cases, transparent mode is specified by enclosing the message with transparent delimiting characters; in other cases, the mode of each file must be specified prior to beginning message transmission. TrunkA line connecting two NPUs or an NPU and a host. The host/NPU trunk uses block protocol; the NPU/NPU trunk uses trunk protocol. Trunk Protocol The protocol used for communicating between neighboring NPUs. It is a modified CDCCP protocol which uses the frame as the basic communications element. 60471400 G TUP (Test UtUity Program) A debugging utility that supports breakpoint debugging as well as other utility type operations such as loading and dumping. Typeahead (Terminal) The ability of a terminal to enter input data at all times without losing output data currently in progress. This requires suspending the output operation until the input message is finished, and then resuming the interrupted output. The ASYNC TIP supports typeahead; the X.25 TIP supports typeahead if it is provided by the PDN. Unsolicited Service Messages Service messages sent to the host which do not respond to a previous service message from the host. Unsolicited SMs report hardware or software failures to the host. Upline The direction of message travel from a terminal through an NPU to the host. Virtual Channel (X.25/PAD) A channel defined for moving data between a terminal and a host. Virtual channels are defined for the length of time that the terminal is connected to the PDN. WordThe basic storage and processing element of a computer. The NPU uses 16-bit word (main memory) and 32-bit word (internal to the microprocessor only). All interfaces are 16-bit word (DMA) or in character format (mux loop interface). Characters are stored in main memory two per word. Hosts (CYBER series) use 60-bit words but a 12-bit byte interface to the NPU. Characters at the host side of the NPU host interface are stored in bits 19 through 12 and 7 through 0 of a dual-12-bit type. Some terminals such as a HASP workstation can use any word size but must communicate to the NPU in character format. Therefore, workstation word size is transparent to the NPU. Worklists Packets of information containing the parameters for a task to be performed. Programs use worklists to request tasks of OPS level programs. Worklist entries are queued to the called program. Entries are one to six words long, and a given program always has entries of the same size. Worklist Processor The base system programs responsible for creating and queuing worklist entries. X.25 Protocol A CCITT protocol used by the public data network. It is characterized by high-speed, framed data transfers over links. A PDN requires a PAD access for attaching asynchronous terminals. X.25 TIP The CCP TIP that interfaces an NPU to a public data network. J0&&*. 60471400 G C-9 CCP MNEMONICS Acknowledge Block (BSC/HASP protocol) CMDR Command Reject (trunk protocol) ACN Application Connection Number CN Connection Number (for blocks/SVM) ACTL Assurance Control Block CND Connection Number Directory A Programming Language CR Carriage Return ARM Asynchronous Response Mode CRC Cyclic Redundancy Check ASCII American Standard Code for Information Interchange CRT Cathode Ray Tube CS ASYNC Asynchronous Communications Supervisor Program (in host) BACK Acknowledgment Block CTL Control Element (ASYNC protocol) BCB Block Control Byte (HASP protocol) DBC Data Block Clarifier (for blocks/SVM) Binary Coded Decimal DCB Diagnostics Control Block BFC Block Flow Control DDLT Diagnostic Decision Logic Table BFR Buffer DEL Delete Character Block Interface Package DM Disconnect Mode (trunk protocol) BLK Message Block DMA Direct Memory Access (in NPU) BN Block Number (overlay) DN Destination Node (for blocks/SVM) BRK Break Block DND Destination Node Directory Binary Synchronous Communication DSR Data Set Ready BSN Block Serial Number (for blocks/SVM) DT Device Type BT Block Type EBCDIC Extended Binary Coded Decimal Interchange Code User defined breaks for HASP (protocols and other) EC Error Code CA Cluster Address E-CODE Device Codes (MODE 4 protocol) CB Control Block ENQ Enquiry Block (BSC/HASP protocol) CCITT Comite Consultif International Telephonique et Telegraphique (an international com munications standards organization) EOF End of File EOI End of Information CDCCP CDC Communications Protocol (trunk protocol) EOJ End of Job EOM End of Message CDT Conversational Display Terminal End of Record (HASP protocol) Communications Control Program (in NPU) EOR CCP End of Transmission Block (HASP protocol) Customer Engineer ETB CE ETX End of Text CFS Configurator State (for SVM) FCD Circular Input Buffer First Character Displacement (in buffer) CIB Function Control Sequence (HASP protocol) Communications Line Adapter FCS CLA FD Command Block Forward Data (block protocol) CMD | ACK0/ACK1 1APL | BCD | BIP | BSC 1Bl, B2 60471400 G D-l FDX Full Duplex LLREG Logical Link Regulation FE Format Effector LM Loop Multiplex FF Forms Feed LOP Local Operator FN Field Number (for SVM) LP A series of TUP commands start with *LP FRQ Frame Retention Queue (trunk protocol) LRN Link Remote Node (for SVM) FS Forward Supervision (block protocol) LT Line Type FV Field Values (for SVM protocol) HASP Houston Automatic Spooling Protocol MLCB Mux Line Control Block HCP Host Communications Processor (alternate name for NPU) MLIA Mux Loop Interface Adapter HDLC MM Main Memory High Level Data Link Control HDX Half Duplex MPLINK The PASCAL Linking Editor HIP Host Interface Package MSG Message Block HL MTI High Level Message Type Indicators (MODE 4 protocol) HO Host Ordinal M4 MODE 4 IAF Interactive Facility Program (in host) NAK Negative Acknowledgment Block (BSC/ I HASP protocol) | 4^tWSS Mask Register 1 ICMD Interrupt Block NAM Network Access Method Program (in host) 1 ICMDR Interrupt Response Block NCF Network Configuration File (in host) (NS controlled) NDA Network Dump Analyzer (in host) NDLP Network Definition Language (for host) NHP Network Host Products NIP Network Interface Program NOP Network Operator NPINTAB NPU Table NPU Network Processing Unit NS Network Supervisor Program (in host) NVF Network Validation Facility (in host) ODD Output Data Demand (Mux subsystem) OPS Operational (OPS level = Monitor level programs) OPSMON Monitor ID Identifier (number of code) IDC Internal Data Channel (in NPU) I-FRAME Information Frame (for trunk protocol) INIT Initialization Block I/O Input/Output ISO International Standards Organization IVT Interactive Virtual Terminal Format LBN Last Block Number (overlay) LCB Line Control Block (in NPU) | LCCB Logical Channel Control Block (in NPU) LCD Last Character Displacement (LCD) LCF Local Configuration File (in host) (CS controlled) LD Load/Dump LF Line Feed LIDLE Idle Element (trunk protocol) UNIT Line Initialization Element (trunk protocol) LIP Link Interface Package (in NPU) LL Logical Link LLCB Logical Link Control Block (in NPU) D-2 >5^V Port PAD Packet Assembly/Disassembly PCB Program Control Block PDN Public PFC Primary Function Code (for SVM) PL Page Length (IVT) Data Network 60471400 G | PPU Peripheral Processing Unit (in host) SYNC Synchronizing Element (MODE 4 protocol) PRU Physical Record Unit TA Te r m i n a l A d d r e s s PRUB Physical Record Unit Block TA F Tr a n s a c t i o n F a c i l i t y ( i n h o s t ) PW Page Width (IVT or PRU) TC QCB Queue Control Block TCB Terminal Control Block (in NPU) QDEBUG PASCAL Debugging Package T D P Ti m e D e p e n d e n t P r o g r a m RAM Random Access Memory TIP Terminal Interface Package (in NPU) RBF Remote Batch Facility Program (in host) TIPTQ TIP Trunk Queues (trunk protocol) RC Reason Code (for SVM) (also called response code) TO RCB Record Control Byte (HASP protocol) RCV Receive State | REJ Reject (trunk or X.25 protocol) RIM Request Initialization Mode (trunk protocol) RL Regulation Level RM Response Message (SM) RNR Receive Not Ready (trunk or X.25 protocol) Te r m i n a l Class Timeout TOT Total Number of Trunks (SM) TPCB Text Processor Control Block TT Te r m i n a l Type T T F Tr u n k Tr a n s m i s s i o n F r a m e TTY Teletype (asynchronous device) T U P Te s t U t i l i t y P r o g r a m TVF Terminal Verification Facility (in host) RR Receive Ready (trunk or X.25 protocol) UA Unnumbered Acknowledgment (trunk or X.25 protocol) RS Reverse Supervision (block protocol) U-FRAME See UA and UI RST Reset Block UI Unnumbered Information Frame (trunk or X.25 protocol) RT Record Type RTS Ready to Send (trunk protocol) I S A R M S e t Aprotocol) synchronous Mode (trunk or X.25 SCB String Control Byte (HASP protocol) | S-FRAME Supervisory Frame (trunk or X.25 protocol) US Unit Separator UT User Te r m i n a l VA R PA S C A L Va r i a b l e WL Worklist WLCB Worklist Control Block SFC Secondary Function Code (for SVM) WLE SIM Set Initialization Mode (trunk protocol) WLP Worklist Processor SM Service Message X-OFF Stop Punch Character (ASYNC protocol) SN Source Node (for blocks/SVM) X-ON Start Punch Character (ASYNC protocol) SND Source Node Directory X P T Tr a n s p a r e n t B i t , p a p e r t a p e ( A S Y N C T I P ) SP X.25 CCITT Protocol for Public Data Network Support SRCB Subrecord Control Byte (HASP protocol) Worklist Entry X . 2 8 C C I T T P r o t o c o l f o r Te r m i n a l A c c e s s t o P D N / PA D STP Stop Data Block X . 2 9 C C I T T P r o t o c o l f o r h o s t a c c e s s t o P D N / PA D STRT Start Data Block STX Start of Text (ASYNC protocol) X . 3 C C I T T P r o t o c o l f o r A s y n c h r o n o u s Te r m i n a l Access to a PDN SVM Service Module for Processing Service Messages 60471400 G D-3 SAMPLE MAIN MEMORY MAP FOR NPU Figure E-l shows the locations of the principal CCP program groups in a 255x network processor unit with 96K words of memory. It is assumed that this is the smallest memory size that will be used with PRU, the HIP, a LIP, and at least one TIP. Note that the HIP, LIP, BIP, and all TIPs are paged. It is assumed that the standard build procedures described in the CYBER Cross Build Utilities Reference Manual and in the NOS Installation Handbook are being used. Therefore, the user need not be concerned with assigning modules to the various regions shown here. Autolink automatically optimizes the amount of memory left for message processing buffers. (Autolink is described in the CYBER Cross Build Utilities Reference Manual.) The example shown is an autolink generated load file for a local NPU (which requires a HIP and BIP) and three options: a LIP, the Mode 4 TIP, and the HASP TIP. Locations in Hexadecimal Program Name 0000 Jump to BEGINX ZEROX 0100 Interrupt trap locations PBINTRP 0140 Jump locations JUMPS 0150 Address table ADDRES 0DAOT PASCAL globals GLOBL$ ifaeT Some base routines 2000 BIP modules assigned to this area. HIP, LIP, TIP and other BIP modules assigned to pages above FFFF have their addresses imaged to this 2K (hex) page. 2K (hex) page of memory 4000 Base routines, mux routines, and routines asso ciated with paged applications above FFFF are loaded in this base area by Autolink. Parts of TIPs that must be in base are always loaded in this region. Base region 0*9*S 8B83t ID table - must be last base application (see Autolink directives) main$ \ Reserved by autolink for buffers D897T D8AF* FFFF 10000 PIDTBL Start of the initialization programs BEGINX Initialization routines Area released for use as buffers after initialization Mode 4 TIP 12000 HASP TIP 14000 LIP and HD? 16000 BIP There is some mixing of modules from one application on the page assigned to another application. See autolink directives in the CYBER Cross Build Utilities Reference Manual 'These addresses can fluctuate because of local mods, TIP selection differences, and PSR level. Figure E-l. Sample CCP Memory Map 60471400 G E-l« ■{*% CCP NAMING CONVENTIONS The following naming conventions for the CCP PASCAL programs should be regarded as guidelines rather than as strict requirements. Network Communications programs Packets The general format of a label is: TIPs, HIP, LIP PIRRRRSSS For types, variables, fields, etc. Where the usual length is six bytes, but additional bytes can be used. BA... P values are: A - 0 Global data BF... EL P Procedure or function DS... Q- W X -Z Local data NonC DC BW... BY... Uciklist CB(WLCB) Line CB (LCB) 1 -9 Transparent or not tied down Not a structure D... Service Module A - Z A structure J... Input/Output (I/O) JU... LD... TUP table M... MM... Mux subsystem Event interface N... Mux subsystem NC... Mux Line CB (MLCB) or Test Proce CB (TPCB) Mux command driver inputs For prccedures and functions: Assurance programs Base system or BIP programs Diagnostic programs Mux subsystem programs (part of the base system) NK... NZ... 60471400 G Logical Link Control Block (LLCB) Terminal CB(TCB) Intermediate array for Worklist BZ... I values are: P = P, I = Overlay Buffer Lojtd/dump Diagnostics CB (DCB) F-l '""^ !^% TERMINAL COMMANDS AND MESSAGES TERMINAL MESSAGES ^ j All interactive terminals controlled by the NPU receive Preformatted messages when the host becomes unavailable, and when the host is again available. A few output batch devices also receive these messages. The messages are: • Host unavailable message: HOST UNAVAILABLE Reply to a message sent upline to a host after the host unavailable message has been sent to the terminals: INPUT DISCARDED Host again available message: INPUT RESUMED TC 16 - 17 « PW < NNN> PL PA = CN = < SELECTED CHAR > BS = < SELECTED CHAR > CT » Cl = INTERACTIVE TERMINAL COMMANDS An interactive terminal has a limited ability to alter certain IVT processing parameters. A summary of these alterable parameters is shown in figure G-l. Ll = SE = DL - The general format of the command message that changes these parameters is: IN = CTL1 PARAMETER COMMAND CTL2 where CTL1 and CTL2 are the terminal's normal starting and ending characters to delimit messages. Each parameter command has the form of two characters followed by an equals sign followed by the selected value: xx = value If a TIP accepts the command, the TIP does not usually send a positive acknowledgment to the interactive device. However, if the TIP rejects the command (as in the case of a command that is invalid for the type of terminal being used), an error message is returned to the operator. The error message has the form: ERR... Table G-l shows the IVT commands that can be entered from each type of terminal. 60471400 G [i] OP => rcA-i L J l-CA-l L< NN >J [:] (X B1 < SELECTED CHAR > B2 MS Figure G-l. Summary of IVT Commands Entered From a Terminal G-l» TABLE G-l. TERMINAL PARAMETERS AS USED BY STANDARD TIPS Conmand TC P W PL PA CN BS CT CI LI SE DL IN OP C D EP PG AL Bl B2 MS A AR B C I Terminal Class Page Width Page Length Parity Cancel Input Line Chain Backspace Control Character CR Idle Count LF Idle Count Special Edit Mode Transparent Delimiter Input Mode Output Mode Character Set Detect Echoplex Mode Page Abort Output Line User Break 1 User Break 2 Message to Operator Other or Invalid Parameters MD4 BSC HASP ARtt AR AR ASYNC ARtt AR A/Bttt X.25 with PAD AR AR AR AR AR A . A/Bt A/I§§ A§ Take the comnanded action Take the commanded action and report to CS No action; send BRK block to host and ERR... message to terminal Valid only from user Ignore 'These commands are valid only for certain terminal classes. DL is not a valid command for terminal class 4 (IBM 2741). A BRK block will be sent to the application if any of these commands are received for a terminal in a class which does not support the command. '•An error will occur for any attempt to change mode between subTIPs. For ASYNC, terminal class 4 is not allowed if the extended ASYNC feature is not configured. TTlTransparent mode can be used only on mode 4C devices. 'The command is legal only if the NPU is configured to support the extended ASYNC feature. Otherwise, CCP sends BRK or ERR... message to the terminal. §SOnly the K, X, and KX options are allowed. PARAMETER COMMAND DEFINITIONS Terminal parameter definitions are: • Terminal Class (TC) TC establishes a class for the terminal with default values for all parameters as defined in table E-7. A TIP will not execute the command if the class is not supported. This change must be reported to CS in the host. • Page Width (PW) PW establishes the physical line width in charac ters for output. For non-transparent blocks, the TIP inserts the character sequence defined for the terminal class to move the carriage or cursor to the next line at the point where the number of characters to be transmitted equals the page width. The parameter NNN varies between 0 and 255; 0 means "new line" and is never inserted. This change must be reported to CS in the host. Page Length (PL) PL establishes the number of physical lines in a page for output. The TIP inserts the character sequence defined for the terminal class to advance the carriage or cursor to the next page length. Also, if the page wait feature is selected, the TIP will wait for an operator input before continuing. The parameter NN varies between 0 and 255; 0 means no paging. This change must be reported to CS in the host. NOTE None of the remaining IVT parameter changes need be reported to the host (CS). Parity Selection (PA) PA specifies the type of parity which the TIP expects on input and generates on output. See description of parity in the asynchronous TIP section of this manual. >«S5V • G-2 60471400 G • Cancel Character (CN) CN establishes the character which is used to delete the current logical input line. If special edit mode is engaged, the CN character is treated as data and is sent to the host; the delete action is not performed. • Backspace Character (BS) BS establishes the character which is used to delete the previous input character from the current input buffer. If special edit mode is engaged, the BS character is treated as data and is sent to the host; the backspace action is not performed. • Control Character (CT) CT establishes the character which is used to enter operational control messages. • Carriage Return Idle Count (CI) CI establishes the number of idle characters to be inserted in the output stream following carriage return (CR). The use of Cl-nn overrules the default value and CI-CA restores the default value. • Line Feed Idle Count (LI) LI establishes the number of idle characters to be inserted in the output stream following line feed (LF). The use of Ll-nn overrules the default value and LI-CA restores the default value. • Special Edit Mode (SE) A SE = Y selection places the terminal in special edit mode; an SE = N selection returns the terminal to the normal character edit mode. Special edit mode provides two types of special operations: (1) backspace (BS), linefeed (LF), and cancel input control symbols are not treated as control characters by the TIP; instead, they are sent upline as data. (2) a character delete sequence (one or more backspaces followed by a linefeed) causes the TIP to issue a caret prompt to the terminal, and then to continue with input processing. • Transparent Text Delimiter (DL) DL establishes the transparent text delimiter for input. The delimiter may be a character, a character count or a timeout of 300 ± 100 ms. One or more of the delimiters may be active simultaneously. • Input Device (EN) IN specifies the input device as a keyboard or paper tape reader in character or transparent mode. Note that paper tape input is allowed in keyboard mode, but that the TIP does not send the < X-ON> characters to start the paper tape reader. ym«s 60471400 G • Output Device (OP) OP specifies the output device as printer, CRT display, or paper tape punch. Printer and CRT display are functionally equivalent. The user may punch a paper tape in any mode, but the TIP provides the X-OFF character only if OP=PT and if data is not transparent. • Character Set Detect (CD) This restarts the character set recognition logic when changing a character set during a message exchange sequence. First, the terminal operator enters the IVT command: CD = A. Then the operator has 60 seconds to (1) physically change the terminal's code set (for instance, by changing the type element on a typewriter), and (2) activate the TIP's code set recognition sequence by pressing the carriage return key. • Echoplex Mode (EP) EP specifies where input character echoing will take place. EP=N implies the terminal is doing its own input echoing and EP=Y causes the TIP to set the CLA to provide character echoing. • Page Wait (PG) PG selects the page wait feature. It allows the user to control output by demanding each page explicitly after the previous page has been viewed for the desired period of time. • Abort Output Line Character (AL) AL selects the character which, when input followed by a carriage return, will result in the current output line being discarded. • User Break 1 (Bl) Bl selects the character which, when input followed by a carriage return, will cause the TIP to send an upline BRK block with reason code specifying "user break 1". Conventionally user break 1 is used to abort the queue. • User Break 2 (B2) B2 selects the character which, when input followed by a carriage return, will cause the TIP to send an upline BRK block reason code specifying "user break 2". Conventionally user break 2 is used to abort the job. NOTE At 2741 terminal, when an operator uses a break 1 or break 2 character, he must precede it by an ATTN character. • Message (MS) MS defines the character used to delimit messages to the LOP. G-3 • B AT C H T E R M I N A L F I L E ( t r a n s p a r e n t / n o n - t r a n s p a r e n t ) b y e n t e r i n g i n f o r m a t i o n i n / ^ S CHARACTERISTIC COMMANDS columns 79/80 of aJ'ob or E0R cardIn the current release only the BSC and HASP batch • 26 selects 026 mode terminals can send requests to the host remote batch facility (RBF) to change the operating charcteristics of • 29 selects 029 mode batch files. • TR selects transparent mode (used on EOR card A BSC/HASP card reader can change the card punching only; the terminal transparent switch must be on characteristics (026/029) or the device data mode when this card is read) /rf^^S • G"4 60471400 G NPU OPERATING INSTRUCTIONS Except for the diagnostics which are described elsewhere, the only operator actions that might be needed at the NPU concern loading the system. Even these actions are needed only in exceptional conditions, since once CCP has been successfully loaded, the host should control all subsequent load operations automatically. Nonetheless, following a failure, it may be desirable to check NPU control switch positions and initiate a CCP load manually. LOCAL NPU PROCEDURE To prepare for a downline load, the NPU operator should perform the following steps: 1. Verify that ports (CLA addresses) to the communications network are correct. yss 5. Stop the NPU at the maintenance panel by pressing the MASTER CLEAR switch (figure H-3). The host discovers that NPU has stopped and initiates the dump and reload sequence. Upon successful completion of the downline load operation by the host, the host is notified. The host then configures the NPU terminals and normal system operation begins. If the downline load is unsuccessful, the host initiates and receives a dump of the NPU memory, micromemory checksum, and file 1 registers. The initiation of another downline load attempt is under control of the host. REMOTE NPU PROCEDURE On loop multiplexer circuit card, set power (PWR) switch to ON. See figure H-l. The procedure for the remote NPU is the same as that for the local NPU except for the following: 3. On CLA circuit card, set CLA/OFF switches to CLA (on). See figure H-2. Only those cards that are configured are affected. • Check bootstrap load (SAM-C) tape equipment mounted on NPU cabinet door. The SAM-C tape cassette should be loaded and the ENABLE/ DISABLE switch should be set to ENABLE. 2. 4. Verify that local console is in normal ON condition. 60471400 G • The NPU is downline loaded via a local NPU. H-l • ! ;i CLA1 CLA 1 ON/OFF SWITCH OFF r ON > < 2 u POWER ON/OFF SWITCH i OFF PWR CLA 1 ADDRESS SWITCHES CLA 2 I■ N LCLKIO AT O £ RD A RTS TCLKjO f SD L RO A RTS r sd kDAllo rl LPCD V o - ¥ CLA 2 ON/OFF SWITCH CLA2 - <® §) OFF li! Figure H-l. Loop Multiplexer Circuit Card PWR ON/OFF Switch Location H-2 Figure H-2. CLA Circuit Card ON/OFF Switch Locations 60471400 G Uio h® 15 oo oo O □ «§ -8 -8 -1 © © © © © © © Q 0 © © 0 ® ® © 8 Z r J558 '*'.? t+ 8 Z z §> i * - liiiil?E - «=■««.--. UJ s | I ~ j < < ; . .' J s oo 10 010 0 1 0101 010 mo o 60471400 G H-3* INDEX Address table B-10 Alarm messages B-l ASCII A-l Async TIP 1-13, 2-20 Base system 1-7,1-10, 2-5 BIP 2-8 Block Interface Package (BIP) 2-8 PRU 2-2 Routing 2-2 Breakpoint 1-18 Buffers 2-1, 2-5 Card reader 2-21, 2-23, 2-24, 2-29 Cassette 1-18, 3-1 CCP 1-1, 1-6,1-7 CCP coding languages 1-7 CE error messages B-l Character sets A-l CLA 1-7,1-19 Common TIP subroutines 2-9 Communications Control Program (CCP) 1-1, 1-7 Network products 1-6 Processor (NPU) 1-17 Supervisor (CS) 1-4 Computer network 1-1 Configuration 1-19 Configure NPU 3-7 Control blocks 2-5 Control words 2-12 Coupler 1-19 CS 1-4 CYBER Cross Build Utilities 1-16 Data Block 2-28 Conversion 2-1, 2-23 Downline 2-37 Transfer 1-7, 2-18 Upline 2-36 Demultiplexing 2-7 Diagnostics 1-7, 2-10, 4-1, appendix B Direct program calls 2-6 Dump see Load/dump Errors 2-28 Failure Host 2-10 Line 2-10 Logical link 2-10 NPU 2-10 Terminal 2-10 Trunk 2-10 Globals 2-7 60471400 G HALT codes B-8 Hardware 1-6, 1-17, 2-4 HASP 2-27 HIP 1-11, 2-11 Host Failure 2-10 Interface 1-11, 2-11, 2-22 Regulation 2-35 IAF 1-4 Initialization 2-4, 3-1 Input Processing 1-7, 2-7, 2-20, 2-22, 2-25, 2-29, 2-31 Regulation 2-35 Interactive Facility (IAF) 1-4 Interface Packages 2-11 Hardware 2-11 Software 2-8, 2-10, 2-11 Interfaces 1-7, 2-3, 2-22 Internal processing 2-9 Interrupts 1-18, 2-6 IVT 1-9, 1-11, 2-19 Languages 1-7, 1-15 Line failure 2-10 LIP 1-9, 1-10, 1-12, 2-10, 3-6 Load/dump Dump format B-12 Local NPU 2-11, 3-1 Remote NPU 1-13, 2-11, 3-2, 3-6 Logical link failure 2-10 Logical link regulation 2-36 Loop multiplexer 1-18 Macro assembler 1-15, 1-17 Message Movement 1-7 Processing, input 1-7 Processing, output 1-8 Micromemory 1-11, 2-12 MLIA 1-18 Mode 4 1-13, 2-21 Monitor 2-5 Multiplex Loop Interface Adapter (MLIA) 1-18 Multiplex subsystem 1-18, 2-7 Multiplexing Input 1-10, 2-1, 2-7 Output 1-10, 2-1, 2-7 Trunk 1-10, 2-7 NAM 1-2 thru 1-5 NDL 1-4 Network Access Method (NAM) 1-2 Communications 1-1 Communications software 1-7, 2-8 Computer 1-2 Concepts 1-1 Definition Language (NDL) 1-4 Message movement 1-7 Index-1 • Operating System (NOS) 1-2 Processing 1-9 Supervisor (NS) 1-4 NPINTAB B-ll NPU Configuring 3-7 Description 1-1,1-6,1-12,1-17, 2-1 Failure 2-10, 4-1 Load/dump 2-18, 3-1, 3-6, B-12 Memory 1-6,1-11,1-17,1-18 Remote 1-12, 2-19 NS 1-4 Service module 2-9 Standard subroutines 2-7 State programs 1-17 Statistics message B-6 Status words 1-12, 2-18 Switching 2-1 System monitor 2-5 PASCAL 1-15 PPU 2-11 Printer 2-24, 2-26 Priorities 1-12, 2-33 Program protection 1-18 Protocol ASYNC 1-13,2-20 Block 2-9 BSC 1-13,2-24 HASP 1-14,2-27 Mode 4 1-13,2-21 X.25 1-15, 2-30 TAF 1-4 Terminal Commands H-l Failure 2-10 Interface Packages (TIP) 1-13, 2-19 Parameters H-l Regulation 2-35 Terminal Verification Facility (TVF) 1-5 Timing services 2-6 TIPs ASYNC 1-13, 2-20 BSC 1-13, 2-24 Functions 2-12, 2-13, 2-19 HASP 1-14, 2-27 MODE 4 1-13,2-21 Non-standard 1-15 Subroutine (common) 2-9 X.25 1-15, 2-30 Transaction Facility (TAF) 1-4 Transmission Assurance 2-18 Media 2-3 Trunk Regulation 1-12, 2-19 Transmission priorities 1-12, 2-19 TVF 1-5 Queuing 2-6 UPDATE 1-16 User interface 2-21 ODD 1-10 Operating procedures H-l OPS monitor 2-5 Output 1-18 Output processing 1-8, 2-7, 2-21, 2-23, 2-25, 2-29, 2-30 RBF 1-4 Recovery 2-10, 4-1 Regulation Host 2-35 Logical link 2-36 Terminal 2-35 Trunk 2-35 Remote Batch Facility (RBF) 1-4 Routing 2-9 • Index-2 Virtual terminals 2-9 Worklists 2-5 X.25 Input sequence 2-30 Output sequence 2-30 TIP with PAD subTIP 1-15, 2-30 60471400 G 00m\ I COMMENT SHEET MANUAL TITLE: Communications Control Program Version 3 Reference Manual PUBLICATION NO.: 60471400 REVISION: G NAME: COMPANY: STREET ADDRESS: CITY: S TAT E : zip CODE: Hit intended to. beanyused as an ^der blank. Control Corporation welcomes your below evaluation of this ™™J8 manual."piPlease indicate errors, suggested additions or Data deletions, or general comments (please include page number references). Please reply No reply necessary NO POSTAGE STAMP NECESSARY IF MAILED IN U.S.A. FOLD ON DOTTED LINES AND TAPE TAPE TAPE FOLD FOLD NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST CLASS PERMIT NO. 8241 MINNEAPOLIS, MINN. POSTAGE WILL BE PAID BY CONTROL DATA CORPORATION Publications and Graphics Division 215 Moffett Park Drive Sunnyvale, California 94086 FOLD FOLD
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.3 Linearized : No Page Count : 160 Creator : ScanSnap Manager Producer : Mac OS X 10.5.8 Quartz PDFContext Create Date : 2009:10:24 13:43:36Z Modify Date : 2009:10:24 13:43:36ZEXIF Metadata provided by EXIF.tools