ncar data communications

NCAR/TN-222 + IANCAR TECHNICAL NOTE

4 X ' -

April 1985

NCAR DATA COMMUNICATIONS

TBM'(Mass Storage)

CRAY, CI CRAYCA

1/2" TAPES [ 8

O // NCARI LOCAL 'j^\ NETWORK

IBM 4341's

I- - - -

I IRSCS -

L-TFFFTELEPHONE

LINES

TELEPHONELINES

SCIENTIFIC COMPUTING DIVISION

NATIONAL CENTER FOR ATMOSPHERIC RESEARCHBOULDER, COLORADO

1/2" TAPES

0 0 E

I

PREEAE

This updated User's Guide is designed to provide you with information andassistance regarding access to the Scientific Computing Division's computersfrom your remote location. In addition to the chapters covering specificaccess gateways such as the PACX port selection device, the UNINET nationalpacket switching network, and the IBM Remote Spooling Communications Subsystem(RSCS), a new chapter on "Special Features" has been added covering newfeatures, products and procedures.

This version of the data cammunications guide contains no reference to theMODCOMP system since this computer is being phased out. MODCOMP users arebeing directed to the IBM batch facility (RSCS). Current MODCOMP users shouldretain the previous edition of the data ccmmunications manual for reference.Besides correcting errors in the old manual, this manual contains items con-cerning updates to the RSCS command language, new UNINET PAD parameters,graphics metacode file transmission, asynchronous file transfer features, newtelephone numbers, and full screen interactive facilities.

At the end of this guide you will find a "Reader Response Form" designed toprovide our editor and author with feedback on the effectiveness of thisguide. We hope you will avail yourself of the opportunity to let us know ifthis guide meets your needs. You may also use this form to forward recommen-dations or suggestions on how the data communications facilities could beimproved or enhanced.

ACKNOWLEDGMENTS

Don Morris was the principal author of this manual; Robert Nicol was theeditor. The author and editor wish to thank both Greg MacArthur and DaveFulker for their work on an earlier edition of this manual. We also wish toacknowledge the efforts of Ann Cowley, Buck Frye, Barb Horner, Bill Ragin,Steve Storm and Marie Working for their careful reading of draft versions ofthis guide. They greatly assisted the author and editor in pointing outtechnical discrepancies which otherwise would have escaped into print. Also,thanks go to those users Who have taken the time to point out errors andinconsistencies that escaped initial scrutiny in the earlier edition.

NCAR Data Communications

Table of Contents

CHAPTER 1: INT mDUCTION

Remote Computing at NCAR ... ........................................ 1-1Telephone Entry Points..................................... ......... 1-2F PPACXuu Plans · · · · · · · · · · · · · · · · · · · ·....... 1-2UNINE T............... 1-2RSCS ......... ..... ..... ..... .... ..... ..... ..... ..... .... 1-2

Logical Path Connections. .... ............................... 1-2Hardware/Software Requirements for Dial-up Remote Access .............. 1-4Features of Remote Access Systems................................... 1-5Optimal Remote Use of SCD Facilities.................................. 1-6RJE Policies ........... 0...a................................ 1-6Future Plans.................... ...................... 1-7Consultation and Troubleshooting Services............................. 1-8

CBAPTER 2: THE PACX SYSTEM

Introduction .. ...................................................... 2-1

How to Establish a Communications Link................................ 2-1Logging onto the IBM 4341 Computers ... .. .... ................. 2-4

Line Mode Logon....................................... 2-5Full-Screen Logon....................................... 2-5

CHAPTER 3: TIE UNINET NE1WOIR

Introduction Pi..................... ..................................... .... 3-1

Access Procedures........................................... 3-3

Reporting Problems and Getting Help ................................ 3-6Network Infom ation........... ............................. 3-6Usage Notes......................................... 3-7

Line Editing ......................................... 3-7Flow Control.............................................. 3-7

Control of PAD Functioning..................... ................... ..... 3-8An Example of PAD Parameter Modification............................ 3-10PAD Parameter Definitions and Values .................. .......... .. 3-11

PAD Ccnmands. ....................................... 3-15

Table of Contents .April 1985 1

CHAPTER 4: SPECIAL FETRES

Introduction.................... � .................................... . 4-1Full Screen Emulation - SIM3278..... ...... ............... 4-1

SIMPC/AZPC2 - The IBM PC Package .................................... 4-1How to Enter SIM3278........................o ..... ....... ....... 4-5Graphics and SIM3278 ....... o ............ 4-6

Keystroke Definitions For ASCII Terminals ..... ... o.....0 0 ........ 4-6More on SIMPC/AZPC2 ...................... eo eo...o oo...e... 4-7

Accessing SIM3278 Through UNINET0 .................................. 4-7

PC-TALK......................................... ................ 4-7PC-TALK Through UNINET.............. . 4-8PC-TALK: PC to NCAR File Transfer ............ .............. . 4-8PC-TALK: NCAR to PC file Transfer...... .......................... 4-10

YTERIM..·.··..· ... ·.... .. . .. .. . .. ....... @ e @ @ aaa4-11File Transfers: Uploading and Downloading ............. .............. 44-11

Graphics File Transfer. ........................... ........... 4-12

Ccnmunications Between Two Personal Ccmputers. ................... 4-13

CHPTIER 5: RSCS: TE REMY SPOOdLIG C MMNICATI SBSYShE

Introduction................ ...... o..... ........ .. ... 5-1

Supported Protocols and Line Speeds............................... 5-1Permission to Use RSCS..................... 5-2

RSCS Conmand Language ... ................... 5-2Making the Connection.. ....................... .... .. 5-2Signing onto RSCS............................. ... ...... o..o......... 5-3

SIGNON Optional Parameters..5 ........... . . .. e... ........... 5-3

STINM................ ............ e.. ..... .......... 5-3

....... ................................ o.... . ............ 5-3.P120.............. ................................ . ... ...... 5-3

CMPR....... ...... 5-3

CMPR51S................................ . 5-4

SIGNON Re8cord for HASP. 5-4

SION Record for2780/3780............................................................. 5-4SIGNON RA5............................................ ............. 5-4PSubmitting a Job to The CRAY- Caputers and Getting It B.a ......... 5-4Disposing Job CH............. 5-4TRS.........................SY . ... 5-4

TRSN····························· · .5-4

SIGNON Record for 2780/3780 5-4SIGNON Record for UT200........................................... 5-4Submitting a Job to The CRAY-1 Computers and Getting It Back......... 5-5Disposing Job Output.................... o...o.......... 5-6

Disposing to the Local NCAR Printer for Mailing..... o ............. 5-6Disposing to the Output Queue of Your Remote Site.................. 5-6Disposing to Your Virtual Machine.. 5-7Disposing to Any Virtual Machine .. 5-7

Table of Contents April 19852

Disposing Metacode Plot Files................................... 5-7Making an Error in the DISPOSE Record................ 5-7

Sending Files to a Virtual Machine...................................5-8Sending Messages Fron RSCS ................................. 5.. ...... -8Receiving Messages from the Operator ......... .5-9Using a Virtual Machine with RSCS....................................5-9

Interrogating RSCS About Its Status..5-9Sending A Message To A Signed-on RSCS Site.........................5-10Routing Files Frm Your Virtual Machine............................ 5-10

CHAPTER 6: RSCS COMMND LANGOAGE

Minimal Command Set.......................................... 6-1RSCS Command Summary. . .............. .. 6-2

Notational Conventions ... . . ................ 6-4Command Responses .............. ...... 6-6Description of Terms .. . . .6-6NCAR-Added Commands.................... . .6-6

DIS,Cx. ........................ .... .. .............................. 6-7DIS,NEW ........................................................... 6-8DISHEL............................................................ 6-8DISSIT............................................................. 6-8

WFRIPRI.............................6-9REWPRI..............................6-9

6-10RDY .................. 6-10

SIN m ................ 6-10MULO .......... ............................................ 6-11RSSNOTRAndard Cc....... d................................. ......... 6-11CTRASE. (ForNC...R.......perat..r . ................................ 6-11

.NOHDR...............6-11

EHDR.. .................. ............. 6-12END..*...* . .. ..... . .... 6-12REARDR ................................... 6-12DRDRDR ...................................... ...................... 6-12

6-12RSCS Standard CommandsC p a ry............................. .6-13BACKSPAC......................................6-13

CHANGE........................................... ...... 6-13CLOSE (For NCAR RSCS Operator Only) ................................*. 6-15

DRAIN......................................6-16FLUSH......................................6-16

FREE ........ .. . .. . ...........****..**** . .***.* **..*6-17-FWDSPACE..ooooo... .................................. ... ... . 00.....6-17

MSG. ........................ *..........*.*.**...***..******.******. 6-18ORDER, *.. ... **.** ..***.* ..** O..**** 00.**** *************6-19PURGE O a ....................................... . ... ......O . .. . 6-19QUERY .................................. **.*... *. *.*.. 6-20STAR .......................................... . . ....... 6-27

TRANSFER (For NCAR RSCS Operator Only)...............................6-27

Table of ContentsApril 1985 3

CEAP'IER 1: INTEUIXX2TIO I

RETE CCMPIUTING The National Center for Atmospheric Research (NCAR) pro-AT NCAR vides remote users of Scientific Computing Division (SCD)

computing systems with several methods of access to batchand interactive computing through both the dial-up tele-phone system and through leased telephone lines.

Batch access refers to the direct submission of job filesand the receiving of output without significant user in-teraction during the course of processing. Batch accesstypically involves the use of a remote work station (orcomputer) that is the logical equivalent of a card readerand printer. Data communications between such a remotesystem and an NCAR system are often on a high-speed lineusing one of several synchronous protocols.

Interactive access refers to a processing mode duringwhich the user engages in a dialogue with a computer sys-tem, even though that dialogue may be for the purpose ofpreparing a job for batch submission to a second comput-er. Interactive access merely requires a "dumb" termi-nal. The associated data communications occur at a lowspeed via the universally accepted asynchronous ASCIIprotocol.

Batch computing is provided on the two CRAY-1 computers,

referred to throughout this guide as the CRAY,C1 andCRAY,CA machines. The IBM 4341 computers, accessible via

the IBM 3705 and the IBM 7171 controllers, provide an in-

teractive environment for code development, job prepara-tion, and job output perusal for programs run on theseCRAY-1' s.

This guide deals with the methods used to gain access to

these computers and does not address the procedures forrunning jobs on the CRAY-1 machines or working in the in-teractive environment of the IBM 4341 system. The manu-als listed below contain detailed information on everyaspect of the SCD c mputing environment.

- THE CRAY-1 SUPERCOMPUTERS: A Guide to Supercomputingat NCAR (NCAR/TN-226+IA) provides information aboutbatch computing on the CRAY-1 computers Sections onCRAY-1 Job Control Language (JCL) commands and spe-

cial- IBM 4341 directives are included when needed to

describe the routing of your computer jobs or filesthrough the system.

Introduction1-1April 1985

- The NCAR IBM 4341 Gateway Computers (NCAR/TN-234+IA)provides information on the interactive computingenvironment.

- MANAGING DATASETS AND PROGRAMS AT NCAR: The MassStorage Subsystem (NCAR/TN-218+IA) describes themanagement of large amounts of data at NCAR.

- The NCAR Local-Network (NCAR/TN-228+IA) provides in-formation on NCAR's local area network.

Copies of these guides are available in the User Area andthe Computing Library at the Mesa Laboratory; personalcopies may also be obtained from the Documentation Spe-cialist (see Table 1.4).

TEP E ENTfRPOINTS

The PACX

Depending upon your needs and equipment, there areseveral points or "gateways" through which the remoteuser may enter the NCAR system via telephone. Althoughnot all logically equivalent, they are referred to as thePACX, UNINET, and RSCS.

The Private Automatic Computer exchange (PACX) is a portselection device that the remote user dials directly togain interactive access to the IBM 4341 machines.

UNINET UNINET is a national packet switching network service towhich NCAR subscribes to provide interactive access tothe IBM 4341 computers.

RSCS RSCS (Remote Spooling Canunications Subsystem) is a ccm-ponent of the IBM 4341 operating system that handlesremote batch entry.

The procedures for using each of these gateways are ex-plained in subsequent chapters of this guide.

WIXGIC~AL PATIH Figure 1.1 shows the logical path connections through thevarious access gateways. The following points should benoted in regard to this diagram: since UNINET is routedthrough the IBM 3705 controller, line mode is the defaultmode of operation; however, a psuedo-screen-mode facilityimplemented by software is available. Furthermore, thecurrent UNINET routing access is restricted to the IBM4341 CMS operating system. Dialing through the PACX al-lows routing through the IBM 7171 which in turn permitsful--screen mode for a certain set of terminal types.RSCS is intended for batch job submission and is notaccessible through the UNINET packet switching network.Subsequent chapters contain detailed information on theseand other features.

Introduction 1-2 av-ril 1985

Figure -. 1Logical Path Connecticns

CRAY, CIPHONE RSCS ORLINES CRAY, CA

PHONELINES

PHONELINES

April 1985 Introduction1-3-

EmlR iEgfaS FORDIAL-UP REEMTE

ACCESS

You must have a suitable terminal or computer with aprotocol emulator, as well as a modem that is compatiblewith one of the protocols and modems at NCAR. The proto-cols, modem types and speeds currently supported by NCARfor dial access are listed in Table 1.2.

Features of the

PROTOCOL PROCESSING

Table 1.2Rerote Telephone Access System

MODEM TYPE SPEED

CDC UT200

IBM 2780/3 780

IBM HASP

batch (RSCS)

batch (RSCS)

batch (RSCS)

AsynchronousASCII TrY

interactive(UNINET or PACX)

any asynchronous <2400 bps

* Available upon MDDCOMP phase-out.

Introduction

201A201C208B

201A201C208B

200024004800

BellBellBell

BellBellBell

BellBellBellBell

**

200024004800

bpsbpsbps

bpsbpsbps

bpsbpsbps

201A201C208B

200024004800

_ __

1-4 Av-% i 198 5

FEATURES OF REM3rEACCESS SYSTES

Table 1.3 briefly ccmpares sane of the features availableon the three remote job access systems via the telephonesystem.

Table 1.3Access System

Feature

InteractiveCanputing

RSCS

No

UNINET

Yes

PACX

Yes

Transparency/GraphicsMetacode

Yes-exceptUT200

Protocol(s) CDC UT2002780/3780IBM HASP

Async ASCII Async ASCII

Leased Lines

SynchronousLine Speeds(in bitsper second)

AsynchronousLine Speeds(in bitsper second)

200024004800leasedup to 56K

none

Introduction

Yes Yes

Yes No Yes

none

<2400

none

3001200

_ _

A-rril 1985 1-5

OPTIML REM TE E For those of you with both interactive and batch termi-OF SCD FACILITIES nals, a combination of interactive and batch access may

prove to be advantageous. The following scenario depictssuch a comnbination:

You perform most of the programming functions interac-tively on the NCAR/SCD IBM 4341 machines, including:

® job preparation and submission to one of the CRAY-1computers

@ observation of job progress

@ correction of program errors and re-submission ofprograms

0 perusal of job results

0 final editing of printed and graphical output

This type of interactive computing is efficient becauseof the access available through the UNINET packet switch-ing network. Finally, bulk transmission (most likely forlarge printouts or for transferring graphics files) isperformed through the RSCS gateway, preferably duringhours when the telephone rates are low.

The advantage of this scenario is that your output is nottransmitted (at expensive phone rates) until it has beenexamined interactively, at which time its value and in-tegrity can be ascertained. Furthermore, you can easilyroute your output to the RSCS gateway for subsequenthigh-speed transmission to your site.

REMDTE AdCESS There are several policies that specifically affect youPCLICIES as a remote user. The principal ones are based on the

fact that there are no classes of users who receive spe-cial service. All who may use computer resources haveequal access to the NCAR/SCD system. The following poli-cies were developed with this assumption in mind:

1. No differentiation in treatment is made between re-motely and locally submitted jobs on the CRAY-1 com-puters. All jobs entering the machine use the samescheduling algorithm which does not contain anyparameters governing "remoteness".

2. All costs for the equipment at the remote site, in-cluding the remote terminal and modem, are borne bythe user. Telephone calls directly to NCAR are paidby the user. If the user accesses NCAR via UNINET,the user also pays the cost (if any) for the call tothe nearest UNINET node.

Introduction 1-6 April 1985

3. The normal method of carnunication fron the remotesite is over the dial-up phone system. When totalconnect time from a site reaches more than 80 hoursa month, a leased line may prove more cost-effective. Requests for a leased line and the asso-ciated dedicated port on an NCAR/SCD gateway comnput-er are processed by the Ccmputer CommunicationsPlanning Group. All costs and maintenance for theleased lines and for modems at both ends will beborne by the user.

4. Any output produced at NCAR is mailed to the siteautomatically. Printing of large output listings atNCAR is discouraged. Output is mailed once a day.Microfilm, microfiche, and printer output of lessthan 50 pages are mailed first class. Printer out-put exceeding 50 pages is mailed parcel post.

5. When job output is ready for transmission to a re-mote site, the output will be available for printingat a terminal for a specified time period, currentlyset to seven days for output in an IBM 4341 virtualreader or in the RSCS output queue. If it is notrequested within the time period, output in a virtu-al reader or in the RSCS queue is purged by the sys-tem and lost to the user.

UTURE PIANS The Scientific Computing Division is constantly strivingto upgrade its data communication and related services.To this end the Division welcomes your recommendations.As a result of user input, the following features areplanned for implementation in the future or are beingconsidered.

0 UNIX operating system support on the IBM 4341 com-puters with user access through UNINET.

0 An error correcting protocol system for UNINET usersat certain locations.

0 2400 bps asynchronous line speed available at cer-tain UNINET locations.

0 Expanded file transfer support for mini and microcomputers.

- Internetwork electronic mail facilities.

IntroductionApril 1985 1-7

The Scientific Ccmputing Division maintains telephoneconsultation service on a regular schedule to help withany problems that you may encounter and will advise youon available services. See An Overview of the ScientificComputing Division (NCAR/TN-240+IA) for advisory servicesor consult The Record, SCD's monthly newsletter, for themost recent listing of people to contact and their tele-phone numbers.

Table 1.4 lists the contacts at the Scientific ComputingDivision for specific data communication services. Allphone numbers can be called direct by dialing (303)-497-xxxx where "xxxx" is the extension listed. FTS usersshould dial 320-xxxx. Users currently accessing the IBM4341 system can also send electronic mail addressed tothe userid listed in the table.

Table 1.4Consulting Service Contacts

Contact Ext.IBM 4341userid

Policy Information

Troubleshooting

RSCS Signon Assignment

Documentation Distribution

General -Liaison

UNINET Information

IBM 4341 VM Assignment

Mailing List Changes

Site Mailings

Remote Hardware/SoftwareCanpatability Questions

Questions about informationin this guide

Joe Choy

Consulting OfficeDon MorrisBill Ragin

Bill Ragin

Sal Farfan

Joe Choy

Don Morris

Rosemary Mitchell

Rosemary Mitchel

Sue Long

Don MorrisConsulting Office

Bill Ragin

Introduction

CONSULTAMSEItN AND

Service

1222

127812821258

1258

1292

1222

1282

1235

1235

1245

12821278

1258

CHOY

CONSULT1MDRRISBILLR

BILLR

SAL

CHOY

MORRIS

ROSEMARY

ROSEMRY

SUELONG

M3RRISCONSULT1

BILLR

__

Av-% i 198 51-8

CHPER 2: THE PACX SYST

IN I'lA xrrIC t The GANDALF Corporation s PACX (Private Autcmatic Camput-er exchange) is NCAR's port selection device. Users ac-cessing the IBM 4341 computers by a direct phone call toNCAR are routed through the IBM 3705 or the IBM 7171routing omnputers via the PACX. The PACX automaticallyassigns you to an available port or access channel on therouting computer that you select. You must first in-teract with the PACX before logging on to the IBM 4341machines. After the establishment of a communicationslink between your terminal and the routing computer, ccm-munication through the PACX is transparent to you.

In what follows, an important distinction between linemode and full-screen mode must be noted: whereas almostany terminal can communicate with the IBM 4341 computersin line mode, only certain terminals, as noted in Table2.4, can communicate in full-screen mode. However, userswith certain terminal types can log on in line mode andthen run in a simulated full-screen mode by invokingsoftware described in Chapter 4.

HOW TO ESTABLISH AOOCMMICA5TINS

LINK

Depending upon the access route you are using (see Table2.2), the following parity settings are necessary to per-mit you to establish a communications link to the IBM4341 computers through the PACX:

The PACX System

Entry Class Parity

i3705 M\RK parity (7 data bits, 8th bit always 1)io, i3705 SPACE parity (7 data bits, 8th bit always 0)

Av-ril 1985 2-1

If there is no space parity setting on your terminal youshould try setting your terminal to seven data bits withno parity or eight data bits with no parity. A connec-tion with the PACX may then be initiated by dialing oneof the numbers listed in the Table 2.1.

Table 2.1PACX Telephone List

All phone numbers transfer data at 300 or 1200 bits per secondare compatible with Bell 103, 212, and Vadic 3400 modems. Thecode is (303). There are two rotary banks. Dialing the firstof a rotary bank causes the first non-busy modem to answer.

NumberNumber

1 of 8494-0472

494-0486494-0490494-0539494-0473494-0488494-0528494-0551494-1946494-1947494-2267494-6444

After dialing the selected number, press the <RETURN> key(smaetimes labeled <ENTER>) o

The PACX will respond with:

enter class

The PACX System

Rotary

1 of 12

ofofofofofofofofofofof

1212121212121212121212

23456789

101112

499-7482

499-7503499-7504499-7506499-7507499-7512499-7514499-7515

Rotary

2345678

ofofofofofofof

8888888

area

Am ri 198 52-2

The response should be one of the class codes listed inTable 2.2, followed by <RETURN>.

Table 2.2Entry Class Codes for the PACX

Class Code

i3705

io

Device

IBM 3705

IBM7171

Description

Permits access to an IBM4341 machine, with linemode editing. Full-screensimulation possiblewith scme terminals.

Permits access to one of theIBM 4341 machiness with full-screen editing capabilities.

The PACX System

Half

Full

__

Av-ril 1985 2-3

The PACX will return one of the following responses:

System Response

CLASS xxx START

CLASS xxx UNASSIGNEDENTER CLASS

CLASS xxx UNAVAILABLEENTER CLASS

CLASS xxx RESTRICTEDENTER CLASS

Table 2.3

Table 2.3PACX System Response to Entry Class Code

Meaning

You are connected (xxx is the class entered).NOTE: A CONNECTION IS AUTOMATICALLY BROKENAFTER A TEN MINUTE IDLE PERIOD!

No ports are assigned in that class.Select another class.

This class is temporarily unavailable.Select another class.

Access to that class is restricted.Select another class.

CLASS xxx BUSYQUEUE SIZE xxxx DO YOU WISH TO QUEUE?

All ports of thatclass are busy, butyou may queue. EnterY[es-] to queue, N[o]to select a new class.

NOTE: Queued terminals receive periodic queue positionreports. When service is available, the START messagewill be received. Should service of that class fail orbecome unavailable while you are on the queue, you willreceive an appropriate message and will be prcmpted toselect a new class.

LOGGING OT THEIBM 4341 ODMPUTERS Once you have received the message:

CLASS xxx STARr-. I...

you are ready to log on to the IBM 4341 machines.

The PACX System 2-4 APril 1985

If you are accessing the IBM 4341 cacputers through theIBM 7171 machine you will have full-screen editing capa-bilities. If your access is through the IBM 3705machine, you may be using the equivalent of a teletype(TTY) terminal and have line editing capabilities only.The logon procedure looks quite different depending onthe available mode of access.

Line Mode Logon If "i3705" is the CLASS CODE you enter, access4341 machines is through the IBM 3705 and youmode. The PACX will respond:

to the IBMare in line

CLASS i3705 START

followed by the logon prompt.

WARNING: U.S. GOVERNNT PROPERTY, UNAUTHORIZED USE ....

I

If just "WARNING: U.S. GOVERNNT ... " appears, press

<RETURN> (in some cases pressing <BREAK> is necessary).This response should bring up the "!" and "." prompts,after which you can log onto the IBM 4341 computers. Ifyou have one of a certain class of ASCII terminals, or anIBM PC or a micro computer that emulates one of a certainclass of ASCII terminals, you may enter a software systembefore you log on that permits you to run in a simulatedfull-screen mode. Details regarding this feature aredescribed in Chapter 4.

Full-Screen Logon If you have entered CLASS CODE io you are put into full-screen node, and you will be queried for your terminal-type by the message

ENTR TERMINAL TYPE

One of the terminal-type codes listedbe entered. If you type <RETURN> thewill be displayed for your reference.

in Table 2.4 mustterminal-type codes

The PACX System2-5'Av-ril 1985

Table 2.4 below gives a list of all terminals currentlyacceptable for entry to the IBM 4341 computers throughthe IBM 7171. If your terminal is not on this chart oris not compatible with one on the chart, you cannot usethe full-screen mode and must enter the IBM 4341 machinesthrough the IBM 3705 in line mode.

After you have entered your terminal-type code, the NCARlogo will appear. To initiate the logon sequence, press<RETURN>. This will clear the NCAR logo from the screenand place you in the ControlNProgram (CP) environment.You may then log onto the IBM 4341 computers.

Table 2.4Terminal Chart for Full-Screen Mode

IBM 7171 Terminal-Types Terminal- Code

Perkin-Elmer 1100 Fox PE1100

Hewlitt-Packard 2648A HP2648A

IBM 3101 IBM3101

IBM 31ALT IBM31ALT

Digital Equipment VT100 VT100

Digital.Equipment VT100N VT100N

Lear-Seigler ADM 3A ADM3A

Soroc IQ 120 SOROC

IBM Personal-Ccmputer IBMPC(with YTERM software)

T 2-6The PACX System April 1985

CuHAPIER 3: 1THE tINET NETWORK

II ON One of the easiest ways to access the NCAR/SCD computersis through UNINET, a nationwide packet switching network.If you have an ASCII terminal, or a personal computerthat can emulate an ASCII terminal, and a standard modem,the UNINET network provides interactive computing on thetwo IBM 4341 systems. This chapter offers both introduc-tory and advanced information on the use of UNINET.

PELIMIRIES UNINET, part of United Telecommunications, Inc., is apublic packet switching network available in most citiesvia a local telephone call. Access is gained by callingthe nearest UNINET Packet Assembler/Disassembler (PAD)computer, each of which is configured to converse withconventional ASCII terminals using common modems. ThesePADs are interconnected with one another and with NCARvia high-speed lines utilizing the standard X.25 protocolof the Consultative Committee on InternationalNTelegraphyand Telephony (CCITT). This network offers inexpensive,relatively error-free, nationwide access to interactivecomputing on the NCAR/SCD IBM 4341 system. Access toNCAR from other countries is also possible via UNINETlinks to foreign networks.

Before accessing UNINET, you should understand the natureof the service provided and have the proper equipment formaking the local connection to UNINET. You should takeparticular note of the following points:

* At present, UNINET is configured to provide interac-tive service for ASCII terminals only (or computersthat emulate such terminals). Users of the IBM RSCSremote batch systems (2780/3780, HASP and UT200 pro-tocols) must place direct-dial phone calls to NCARfor access.

* Users of UNINET will have access to the IBM 4341computers through their common 3705 communicationscontroller in line mode. In the jargon of IBM manu-als, a UNINET user's terminal (also called a virtualconsole) is designated as a TrY, typewriter, or 3101terminal, but NOT a display, screen, full-screen, or327n terminal. Users of display mode through theIBM 7171 must place direct-dial phone calls to ac-cess these systems as outlined in Chapter 2. Howev-er, full-screen mode is available for a wide rangeof terminals and personal computers as detailed inChapter 4.

* The various UNINET access locations (PADs) are con-figured to support the most common data rates and

The UNINET NetworkApril 1985 3-1

modem types. Data rates from 110 to 1200 bits persecond (bps) are supported at all locations and 2400at selected locations, the most common being 300baud (30 characters per second) and 1200 baud (120characters per second). Your modem must be compati-ble with one of the Bell System 103 modems for 300bps transmission rates or compatible with a Bell212A modem or with the Vadic 3400 series modem for1200 bps data rates. 2400 bps rates requires amodem conforming to the CCITT V.22 bis standard.Certain UNINET PADS have modems that support an er-ror correcting protocol between the PAD and theuser's terminal. This facility requires you to havea MICROCOM modem with the Microcom Network Protocolfeature.

* The UNINET PADs are configured to support user ter-minals with the coanon asynchronous protocols andthe ASCII character set. Each character datum isassumed to comprise seven bits of information, withvarious parity and stop bit configurations handledautomatically by UNINET. The seven information bitsrepresent characters according to the American Stan-dard Code for Information Interchange (ASCII). Mostasynchronous terminals in use today are compatiblewith this protocol.

* The UNINET PAD echoes each character back to theuser s terminal as it is typed. There is no facili-ty for the host IBM 4341 to echo characters. Ifnecessary, "local-echo" mode (also called "half-duplex" or "no echo-plex" mode), in which the PADdoes not echo the characters back but instead thecharacters are echoed by the terminal, is obtainableby modifying a PAD parameter which is set by theuser. (See later sections on PAD parameters.)

* International users of UNINET typically gain accessfrom some other network in the country of origin(for example, the Canadian packet switching networkcalled Datapac). Thus, the characteristics of thelocal PAD will vary from network to network, and arenot under the control of UNINET. For the same rea-sons, access procedures will also vary, so pleasecontact the UNINET Information Consultant listed inTable 1.4 of this guide. Because international con-nections often involve International Record Carriers(IRCs) and other packet switching networks, there

may be additional costs borne by you.

The UNINET Network 3-2 April 1985

AmXIE5S pIEyEIX1rE~ The procedures for accessing the IBM 4341 computers viaUNINET are quite simple. First, you must determine thetelephone number of the nearest UNINET PAD. This phonenumber can be obtained by calling the UNINET toll-freecustomer service center number: 800-821-5340 (in Mis-souri, call 800-892-5915 ). A current list of UNINET ac-cess numbers can also be obtained on-line frcm a database accessible fran UNINET and described in the NetworkInformation section below. Once a telephone connectionhas been established with the local PAD (as indicated bya standard modem tone or whistle), you should begin datatransmission through the modem.

At this time, a few characters such as "1?" should appearon the terminal, but they may be garbled because the net-work requires scme input to become fully matched to yourterminal. The first data you transmit should be: a car-riage return, followed by a period, followed by a car-riage return. For example:

<RE"UN> . < >ETUiN>

Having received these data, UNINET will respond with somenetwork identifiers:

uninet pad XXXX port YY

and a service prompt:

service :

to which you are expected to respond. If this fails forsanome reason (such as phone line noise), you should makerepeated attempts of the form:

<BREAK> <RETURN> . <RETURN>

until the service prompt is received. It is possible atthis point to enter commands affecting the behavior ofthe PAD, but most commonly, you would initiate a connec-tion to NCAR by entering:

NCR <RETURN> (upper or lower case)

where NCR identifies the intended host computer location.

The UNINET NetworkA-mril 1985 3-3

Once the service request has been entered, UNINET shouldrespond with:

*uOO1 000 connected to 30300007

and the designated host IBM 4341 should respond:

WARNING: U.S. GOVERNMENT PROPERTY, UNAUTHORIZED USE ...

which indicates readiness for log on. If you should failto get the "." prompt, try entering <RETURN> or pressingthe <BREAK> key.

At the end of an interactive session, the CP commandsLOGOFF or DISCONNECT will cause UNINET to respond:

*u013 XXX disconnected by host

service :

at which point you simply hang up the telephone.

P1BLEMS ANDEROLRS

There are a variety oftablish a connection.most common symptoms:

possible causes for failure to es-The following examples contain the

* Fast busy signal.telephone circuits.

UsuallyTry again.

indicates overloaded

The UNINET Network 3-4 0 A-rril 1985

* Slow bus signal. The UNINET access number is busy.Try again. If this occurs with regularity, reportthe problem to the UNINET Customer Service Center(see below). UNINET is under contract to provideenough lines so that busy signals are encountered nomore than once per 100 calls.

* Modem carrier detected, but it is unable to ccamuni-cate. Possibly a mismatch between the terminal andmodem speeds. Be sure that the data rate for theterminal is set to that of the modem (300 or 1200bits per second). Also check power switches and ca-ble connections.

* Unable to obtain the "service" prompt, even with re-peated attempts of the <BREAK> <RETURN> . <RETURN>sequence. Mismatch of equipment (see above) or PADmalfunction. Call the UNINET Service Center for as-sistance (see below).

* Random data errors. This is generally caused bynoisy telephone lines. Try re-dialing. If thisproblem occurs with regularity, report it to theUNINET Service Center (see below). UNINET workswith the local telephone operating company to main-tain satisfactory line quality. NOTE: Such errorsoccur almost exclusively on the connection betweenthe terminal and the PAD. Communications withinUNINET sustain error rates of less than one errorper billion characters transferred.

Ring but no answer. Problems with the PAD or tele-phone rotaries. Try re-dialing and report the prob-lem to the UNINET Service Center (see below).

* Connection established but unexpectedly disconnect-ed. Typically caused by problems with the PAD orlocal telephone service. Try re-dialing and reportthe problem if recurrent.

* UNINET responds: "*uOlO XXX not obtainable." This isusually a misspelled NCR or other accessibilityproblems. If the corrected spelling does not solvethe problem, report it.

UNINET responds: "*u005 XXX network congestion" or"*uO33 000 route unavailable." The network is unableto estabETsh or maintain a route to NCAR. Wait andtry again.. Report the problem if it persists (seebelow). UNINET is under contract to provide enoughroutes so that route failures occur less than onceper 100 attempts.

The UNINET Network3-5April 1985

* UNINET responds: "*uOll XXX out of order." Theleased line between NCAR and UNINET is down (ino-perative) or the IBM 3705 canmunications processorat NCkR is down.

* UNINET responds: "*u004 XXX host busy." The connec-tion at NCAR is configured to support a maximum of32 simultaneous UNINET users, and all 32 positionsare occupied. Wait and try again.

* UNINET responds: "*u009 XXX remote procedure error."The host system at NCAR is down or malfunctioning.

* UNINET responds: "*u033 XXX route unavailable." Thenode in Denver through which all NCAR traffic mustpass is down or malfunctioning.

* The IBM 3705 responds: "NCAR IO IS DOWN (or BUSY)"or "NCAR IA IS DOWN (or BUSY)." The IBM 4341 systemyou selected is unavailable. Try again later.

* UNINET responds: "*u012 XXX disconnected at requestof host" or "*u013 XXX disconnected b host." Thehost system at NCAR has terminated the connection.This occurs normally when you log off. Other oc-currences probably indicate host malfunction.

REPiR[NG' P1BI 6 UNINET maintains a Customer Service Center, accessibleAND CrIMG HEM via a MTS number, that provides assistance and solves

network problems 24 hours per day. For network-relatedproblem reporting, information, and assistance, call thefollowing toll-free number:

800-821-5340 - in Missouri: 800-892-5915

at any hour. For UNINET problems that appear related tothe NCAR ccnputers, or if the UNINET customer assistanceis not completely satisfactory, call the RJE troub-leshooting consultant listed in Table 1.4.

NTWO)RK A data base of information about access phone numbers,IN)iRMTITON international connections, logging on, trouble reporting,

and current UNINET messages may be accessed in the fol-lowing way:

Instead of responding to the "service" prompt with"ncr", enter:

nni <RETURN>

The network will then respond with four lines of hostconnect information followed by the prompt:


[ENTER YOUR 3 CHAR HOST ACCESS CODE]

You should then respond with:

ncr <RETURN>

You will then be directed by a series of prompts toobtain the desired information.

USAG(E NOES Users of the IBM 4341 computers through UNINET have ac-cess to certain features that are provided by the PADcomputer. Many of these features are somewhat complicat-ed and unlikely to be required, but a few of them arequite convenient. For example, smane of these featuresallow simple editing of the current line you are typing.(See below for detailed information concerning PAD param-eters 15, 16, 17, and 18.)

Line Editing The most useful line editing function is character dele-tion, whereby you can erase the most recently typed char-acters using <BACKSPACE> (or LEFT ARROW on some termi-nals). Similarly, the entire current line can be deletedusing <DEL>. (or <RUB> on some terminals). In either ofthese cases, the deleted character or line is nevertransmitted to the host. Typing <CTRL-E> (or <ALT-E> onsame terminals) will display the current line.

Flow Control Another very useful PAD feature is "flow control" whichpermits you to stop and re-start the flow of data fromthe PAD. For example, you can display a long listing onthe terminal and temporarily halt the display as desired.To stop the flow of data from the PAD, you must transmita special "Xoff" character to the PAD. The characterused is the ASCII DC3, obtained as:

<CTRL-S> or <ALT-S>

on most terminals. To resume the flow (exactly where itstopped) you must transmit a special "Xon" character tothe PAD. The character used is the ASCII DC1, obtainedas:

<CrRL-Q> OR <ALT-Q>

on most terminals.


There is another way to halt the flow of data from theIBM 4341 machines to your terminal. This is to actuallyinterrupt the IBM 4341 communications by depressing the<BREAK> key, causing the IBM 4341 system to cease outputand wait for your input. An advantage of this approachis that you can issue certain "immediate commands" thatare described in the CMS Command and Macro Referencemanual published by IBM. The most common immediate con-mands are the HT (Halt Typing) and HX (Halt execution)instructions. For example, during a TYPE operation:

<BREAK>

will cause the typing to halt, and:

HT <RETURN>

will terminate the process. The CMS prompt will appear.Alternatively, instead of using HT, a simple:

<RETURN>

will cause typing to resume. However, using this method,output data are usually lost, so the recommendations areas follows:

1. If the output is to be interrupted temporarily (forexamination), use the <CTRL-S>, <CTRL-Q> (Xoff, Xon)sequence.

2. If the output is to be terminated, use the <BREAK>HT (or HX), <RETURN> sequence.

CNxrL CIF PADF]NCfTIcING

You can control the functioning of the PAD by settingcertain parameters. The parameters are described inTable 3.1. These PAD parameters can be set while beingprompted for "service" by UNINET, and this can occur ei-ther at log on time (prior to connecting with NCAR), orduring a session. To obtain the service prompt duringthe course of a session, you must transmit a special sig-nal that is itself defined by a PAD parameter. The de-fault signal for this purpose is an ASCII control charac-ter, DLE, which is obtained as: <CTRL-P> or <ALT-P> onmost terminals. The PAD computer temporarily suspendsthe session with the host, and sets up an interactive ex-change with you, permitting the modification of the PADparameters. Simply typing <RETURN> will re-establish thehost session.


Functions most commonly modified by setting PAD parame-ters include echo-plex, flow control, character deletion,line deletion, and insertion of line feeds or fill (pad-ding) characters. Most users find the default PAD set-tings satisfactory, so the following information will beof the most value if you prefer to operate in local-echo(half-duplex) mode, if you wish the PAD to exercise flowcontrol against the terminal, or if you otherwise needspecial control over the functioning of the local PADsystem.

A typical sequence for setting the PAD parameters occursduring an interactive session as follows:

Type:

<CTRL-P>

which never arrives at NCAR because it is intercepted bythe PAD. This signal character cannot come from thehost; the PAD recognizes this form of signal characteronly frcm the terminal. Furthermore the signal characteritself can be modified by setting PAD parameter #1. Thedefault character is DLE, obtained as <CTRL-P> or <ALT-P>on most terminals. The PAD responds:

service :

to which you respond:

SETpp:nn <RETURN> (upper or lower case)

where pp represents the index of a particular (CCITTStandard X.3) PAD parameter, and nn represents the valueto which it is set. The host responds:

service :

to which you may respond with additional PAD control com-mands, or simply restore the interactive host session bytyping:

<RETURN>

All PAD control functions are entered in similar fashion,when the PAD is waiting for a response to the "service"


prompt. Subsequent sections provide details on the PADparameters, the meanings of their values, and the variousPAD control functions, such as the SET command describedabove.

An Example of PADParameter

Modification

You may prefer to operate your terminal in "local-echo"or "half-duplex" mode. In this mode the terminaldisplays its cwn characters as they are typed, so it isredundant for the PAD to echo these characters back toyou. In fact, each character typed will appear twice ifa half-duplex terminal is operated with UNINET s presetPAD parameters. For example, when responding to the ser-vice promapt with a request for connection to NCAR IO, youtype NCR;O but the following will appear on the terminal:

service :NNCCRR;;O00

To turn off the echoing of terminal input, PAD parameter#2 should be changed from 1 to 0. This can occur beforeattaching to NCAR (at the first service prompt), or itcan occur later in the session as illustrated below. Theparameter setting sequence is begun when you suspend hostinteraction by typing:

<CTRL-P>

The PAD responds:

service :

to which you respond:

SET2:0 <RETURN> (upper or lower case)

If the terminal is set for half-duplex operation, thiswill appear as:

service :SSEETT22: :00

Subsequently, the PAD responds:

service:

to which a simple <RETURN> will cause the host

The UNINET Network 3-10 A-^ril 1985

interaction to resume. Thus changed, the PAD will nolonger echo characters fran the terminal.

PAD ParameterDefinitions and

Values

Table 3.1 lists the PAD parameters implemented by UNINET.Most of these are frcm the CCITT standard X.3 protocol,so their meanings and the associated values are presentedin brief form. The table is organized by parameternumber. Those PAD parameters most cnmmonly changed bySCD users are marked with an asterisk (*). The "Preset"column indicates the parameter's initial default value.

NOTE: Whenever the value of a PAD parameter is used tospecify an ASCII character, the DECIMAL representationmust be used, not the octal or hexidecimal codes. Forexample, the values 0-31 represent control characters,and the values 32-126 represent graphical symbols. De-cimal tables of ASCII codes are given in Tables 3.2a and3.2b of this chapter. Table 3.2a lists the control char-acters, their names, and the keyboard sequences for theirinvocation. Table 3.2b lists the printable ASCII charac-ters. The hexadecimal equivalent of any character in thetables can be found by converting the decimal value forthe character to hexadecimal.

Table 3.1PAD Parameter Definitions and Values

# Parameter Description

1 What keystroke permits terminaloperator to escape data transfermode to set/inspect PAD params?

*2 Should the PAD echo typed char-acters back to the terminal?

3 Which characters should triggerthe PAD into sending a partiallyfull packet?

4 How fast should the PAD time outand send a partially full packet?

Allowable Values/Meanings

0=No escape permittedl=Escape via DLE <CONTIROL-P>17-126=ASCII char for escape

0=Nol=Yes

0=Only send full packets2=CR (Carriage Return)4=ESC,BEL, ENQ,ACK6=CR, ESC ,BEL, ENQ ,ACK8=DEL,CAN, DC216=ETX,ECT18=CR, BOT,ETX126=All control chars + DEL

0=No time out1-255=Time in 50 ms units

The UNINET Network

Preset

1

1

2

0

_ ___ _ __

Avpril 1985 3-11

Table 3.1 (cont.)


*5 Can the PAD assert flow controlagainst data frmn the terminal?(Often necessary if terminal is acomputer used to transmit files).

6 Is the PAD allowed to send ser-vice prompts and network messagesto the terminal?

7 What should the PAD do uponreceiving a <BREAK> signal fromthe terminal?

8 Should PAD discard output datafrom host or deliver it? (Usedin conjunction with parameter 7)

*9 How many fill characters shouldPAD append to CR sent to terminal?

*10 At what length should PAD foldoutput lines to terminal?

11 Terminal speed (automanaticallydetected by the PAD at the timeof the initial connect) in bitsper second.

12 Can the terminal assert flow con-trol against data from the PAD?

Allowable Values/Meanings

0=Nol=Yes (Xon/Xoff protocol)

O=Nol=Yes4=Yes5=Yes

(network messages only)(pranpts only)(prompts & messages)

0=Nothingl=Send interrupt to host2=Send reset to host8=Enter PAD command mode21=Discard current host out-

put & send interrupt

0=Normal delivery to terminall=Discard output fran host

0=None1-127=Number of (NUL) fillers

0=No line folding1-255=Number of chars in line

0=1102=3003=1200

4=6006=1507=1800

Preset

0

5

21

0

6

0

12=240013=4800

0=Nol=Yes (Xon/Xoff protocol)

*13 Should the PAD transmit linefeeds(LF) when carriage returns (CR)are encountered frman the terminalor from the host?

*14 How many fill characters shouldPAD append to LF sent to terminal?

0=No LF insertion1=LF appended to CR fran host4=LF echoed when CR fran term5=LF appended to CR fram host

and LF fran term echoed6=LF appended to CR frcn term

and LF fran term echoed7=combination of 5 and 6

0=None1-127=Number of (NUL) fillers

The UNINET Network

1

4

6

_ ___ _ __ __ _____ __ I

I

3-12 A-rp i 1 198 5

Table 3.1 (cont.)


*15 Should PAD provide line editingfeatures of params 16, 17, 18 &19?

16 Keystroke to delete a character(The default value is BACKSPACEor LEFT ARROW on most terminals).

*17 Keystroke to delete current line(The default value is DEL or RUBon most terminals).

*18 Keystroke to display current line(The default value is ENQ, ALT-Eor CONTROL-E on most terminals).

19 What response do you want to aDEL (line delete) and a BS(backspace) character?

20 What characters should be echoedback to the terminal?(In effect only if parameter 2is set to 1)

*200 What ASCII character can alsobe used for the <BREAK> keyfunction?

201 Should user be disconnected franthe network if the user dis-connects from the host?

254 Is parity for terminal determinedautomatically by PAD at logon?

255 What parity is used for datatransmitted to the host?

Allowable Values/Meanings Preset

0=No, params 16,17,18, & 19 1ignored

l=Yes

0-127=ASCII character code 8(see below)



l=Append XXX to line for DEL. 1Echo BS, do not erase char.

2=Erase line for DEL.

0=Echo all characters 0l=Alphanumeric characters2=CR4=ESC,BEL,ENQ,ACK8=DEL,CAN,DC216=ETX,EOT3 2=HT, LF,VT, FF64=All other CTRL characters128=All other characters

0=None 01-127 ASCII character code

0=No 0l=Yes

0=No, specified by host 1l=Yes, detected by PAD

40=As received fran terminal4=Space (parity bit zero)5=Mark (parity bit one)6=Even parity7=Odd parity

The UNINET Network

_ __

__

]Nvr i 198 5 3-13

Table 3.2aDecimal Table of Non-printable ASCII Control Characters

0 NUL Null <CTRL- @>1 SOH Start-of-Heading <CTEL- A>2 STX Start-of-Text <CTRL- B>3 ETX End-of-Text <CTRL- C>4 EOT End-of-Transmission <CTRL- D>5 ENQ Enquiry <CTRL- E>6 ACK Acknowledgement <CTRL- F>7 BEL Bell <CTRL- G>8 BS Backspace <CTRL- H>9 HT Horizontal Tabulation <CTRL- I>

10 LF Line Feed <CTRL- J>11 VT Vertical Tabulation <CTRL- K>12 FF Form Feed <CTRL- L>13 CR Carrige Return <CTRL- M>14 SO Shift Out <CTRL- N>15 SI Shift In <CTRL- 0>16 DLE Data Link Escape <CTRL- P>17 DC1 Device Control 1 (X-ON) <CTRL- Q>18 DC2 Device Control 2 <CTRL- R>19 D3X Device Control 3 (X-OFF) <CTRL- S>20 DC4 Device Control 4 <CTRL- T>21 NAK Negative Acknowledgement <CTRL- U>22 SYN Synchronous Idle <CTRL- V>23 E1B End of Transmission Block <CTRL- W>24 CAN Cancel <CTRL- X>25 EM End-of-Medium <CTL- Y>26 SUB Substitute <CTRL- Z>27 ESC Escape <CTRL- [>28 FS File Separator <CTRL- \>29 GS Group Separator <CTRL- ] >30 RS Record Separator <CTRL- ^>31 US Unit Separator <CTRL- _>

The UNINET Network

C I_ _I _ � __ ___

3-14 April 1985

PAD CDMMUS Whenever the UNINET PAD is awaiting your response to the"service" prompt, various ccmmands can be entered thatwill affect the behavior of the PAD. (During the courseof an interactive session, you can usually obtain the"service" prompt by typing <CTRL-P> or <ALT-P> as dis-cussed in previous sections). Each of the following com-mands may be entered either in upper or lower case:

1. Null command --

<RETURN>

If the response to the "service" prompt is null,i.e., a simple carriage return, the PAD will returnyou to the (suspended) interactive host session. Ifno host session is in progress (for example, beforea host connection has been established) a nullresponse is interpreted as a command error.

The UNINET Network

Table 3.2bDecimal Table of Printable ASCII Characters

32 space 56 8 80 P 104 h33 ! 57 9 81 Q 105 i34 " 58 : 82 R 106 j35 # 59 ; 83 S 107 k36 $ 60 < 84 T 108 137 % 61 = 85 U 109 m38 & 62 > 86 V 110 n39 63 ? 87 W 111 o40 ( 64 @ 88 X 112 p41 ) 65 A 89 Y 113 q42 * 66 B 90 Z 114 r43 + 67 C 91 [ 115 s44 , 68 D 92 \ 116 t45 -69 E 93 ] 117 u46 . 70 F 94 118 v47 / 71 G 95 119 w48 0 72 H 96 120 x49 1 73 I 97 a 121 y50 2 74 J 98 b 122 z51 3 75 K 99 c 123 {52 4 76 L 100 d 12453 5 77 M 101 e 125 }54 6 78 N 102 f 126~55 7 79 0 103 g 127 DEL

(non-printing), ~ .. . . ...

_ _ _

April 1985 3-15

2. Set parameter(s) -

SETpp: nn <RETURN>

or

SETpl:nl,p2:n2, ... <RETURN>

This command sets one or more PAD parameters tospecified values. The arguments pp, pl, p2, etc.are specific PAD parameter numbers, and the argu-ments nn, nl, n2, etc. are the (decimal integer)values to which the corresponding parameters are tobe set.

3. Set and read parameter(s) --

SET?pl:nl,p2:n2, ... <RETURN>

This cxonmand, in addition to setting one or moreparameters as above, also causes the PAD to displaythe (resultant) values of the referenced parameters.

4. Read parameter(s) --

PAR?pl, p2, ... <RETURN>

This cammand causes display of the current valuesfor one, several, or all of the PAD parameters. Thearguments pl, p2, etc. are specific PAD. parameternumbers. In the absence of arguments, the PAD willdisplay current settings for the entire set ofparameters.

5. Set parameter profile --

PRDFnn <RETURN>

This command sets all PAD parameters to one ofseveral pre-defined profiles, where the argument nnrefers to the desired profile. The available pro-files are listed below, but NCAR users will probablyfind profile 2 to be the most useful. The defaultsettings for the PAD parameters are those of pro-file 2.


6. Host disconnect --

BYE <RETURN>

This command causes UNINET to terminate your connec-tion with the host system. The effect is similar toissuing the CP command DISCONNECT on the IBM 4341system.

7. Host interrupt --

INT <RET:RN>

This command causes UNINET to transmit a specialinterrupt package to the host system. Under defaultconditions (see parameter #7 in Table 3.1) this isequivalent to typing <BREAK> on your terminal.

The UNINET Network

Table 3.3Profile Numbers

Parameter # 1 2 3 4 5

1 * 0 1 1 1 12 0 1 1 0 13 0 2 2 2 24 20 0 0 0 05 0 0 0 1 06 0 5 5 5 57 21 21 21 21 218 0 0 0 0 09 0 6 0 6 6

10 0 0 0 0 011 auto auto auto auto auto12 0 1 1 1 113 0 4 4 4 014 0 6 0 0 615 0 1 1 1 116 0 8 8 8 817 0 127 127 24 12718 0 5 5 5 519 1 1 2 1 120 0 0 0 0 0

200 0 0 0 0 0201 0 0 0 0 0254 0 1 1 0 0255 0 4 4 6 6

_ _

3-17April 1985

8. Network status -

STAT <RETURN>

This command queries the current status of your con-nection on the network, including the PAD and thehost. The messages are similar to those receivedduring the initial access procedures.

9. Reset connection --

RESET <RETURN>

This coDmand re-initializes your connection with thehost system, clearing all data in transit, but notclearing the connection itself. This command isused only when a channel is blocked.


CSPER 4: SPCIAL EATRES

INTICCrTICN Making the physical connection from a remote site to NCARis only one part of successfully conducting a dialoguewith the interactive computer systems. Certain softwaretools have been implemented to help you use the systemefficiently. Although sane of the tools mentioned inthis chapter are mentioned in other guides, they are in-cluded here because they are of special importance to re-mote users. The features mentioned only apply to usersaccessing SCD computers through UNINET or through thePACX in the interactive access mode.

RFUN-SCEEN If you access the IBM 4341 system through UNINET orEM[EATON - through the PACX via class i3705, you do not automatical-

SIM3278 ly have the full-screen functionality provided by entrythrough class io. In fact, at a transmission rate of 300bits per second (bps), full-screen editing features are ahindrance, and some users find that even at 1200 bps,waiting while the video display screen is refreshed is anannoyance. Other full-screen features such as BROWSE,FLIST, and HELP are beneficial at any modem speed.

To provide such full-screen capabilities to users whoseNCAR access is through UNINET, or to users who must enterthrough the PACX class i3705 because their terminals donot permit access via the IBM 7171 through class io, aproduct called SIM3278 is provided.

SIM3278, a SIMqAE Inc. product, is a program running onthe IBM 4341 computers that allows ASCII video displayterminals and microcomputers emulating ASCII terminals tofunction as simulated IBM 3270-type terminals. SIM3278is refered to as a 3270 emulator or as an ASCII-to-3270protocol converter. This program allows you to enter anIBM 4341 ccmputer in line mode, yet still access "thefull-screen facilities. Most, but not all, ASCII termi-nals will function with SIM3278. A SIM3278 manual isavailable from the User Services Documentation Specialist(see Table 1.4). The SIM3278 documentation in this guideis sufficient to perform all full-screen tasks, providedthe user is familiar with the functionality of the PF andPA keys (see The NCAR IBM 4341 Gateway Computers,NCAR/TN-234+IA). Table 4.1 details the acceptable termi-nals and the identification code (ID) required whenentering the SIM3278 software.

SIPC/AZPC2 - The Users with IBM PCs also have the ability to perform fileIBM PC Package transfers to and from the host IBM 4341 machine with a

software package from SINAVRE, INC. called AZPC2 (the newversion is called SIMPC). More information onSIMPC/AZPC2 may be found later in this chapter.

Special FeaturesApril 1985 4-1

_ _ _ __ _I _ _ L _ Table 4.1

Table 4.1SIM3278 Identification Codes

Terminal Type SIM3278 ID

ADDS Viewpoint... . .......................... 31

ADDS Viewpoint 60...... ........................oooo 36

ADM - see Lear Siegler

Annarbor Ambassador.............................37

Beehive DM-5/5A*................................16

CCG Vuccm-4 (Bell Canada).......................12

Concept HDS AVT-100 ................. ............ 32

Control Data VIKING-721 ........................ 34

Cybernex MDL-S110. . .. .......................... 25#

Cybernex XL84.................10

Cybernex XL87-M ........ ........................ 21

Cybernex XM-3270 . .... .. ....................39

Datamedia 1520/21*. * .***... ..............2

Datamedia 3000/45................................1

Datamedia Excel 22see Digital VT100

Digital (DEC) VT52............................... 9#

# Full duplex terminal; requires diode switch or modem with "localecho" feature, unless used through UNINET.

## Manufacturer's enhancement required.

Special Features 4-2 April 1985

Table 4.1 (cont.)SIM3278 Identification Codes

Terminal Type SIM3278 ID

Digital (DEC) VT100 .............................. 8#

Digital (DEC) VT100 w/ VT640graphics by Digital Eng........................8#

GTE XT300.......................................43

Hazeltine 1420/1520.............................33#

Hazeltine ESPRIT IIIsee TeleVideo 950

Hewlett-Packard 2382A/2622A.....................30

Hewlett-Packard 2621A ........................... 14

IBM 3101 Model 20, BLOCK mode...................11

IBM 3101 Model 10/20, CHAR mode.................26#

IBM PC running AZPC2 software,available fron NCAR...........................38

Infotron 100 ................................... 28

Kimtron ABM-85..................................22

Lanpar VISION - see Digital VT100

Lear Siegler ALM3A . .... 17

Lear Siegler ADI3A+/AD5. ....................... 20

Lear Siegler AJD3A+/ADM5 w/ RG512graphics by Digital Eng ..... 20

# Full duplex terminal; requires diode switch or modem with "localecho" feature, unless used through UNINET.

## Manufacturer's enhancement required.

Special Features

__

IN-ril 1985 4-3

Table 4.1 (cont.)S1IM278 Identification Codes

Terminal-Type SIM3278 ID

Lear Siegler ADM42..............................15

Microterm ACT5A, native mode....................35

Northern Telecanom Displayphone,ANSI/VT100 mode.. ............................. 27

Northern Telecan Displayphone,IBM/3101 mode.................................13

Soroc Challenger 530............................44

Teleray 10M.....................................19

Teleray 16M*... *. *o....... .* . *....*.....eeo** 40

TeleVideo 910-Plus, 912/920 mode................18

TeleVideo 920....................................3

TeleVideo 925........ . . ..........................4

TeleVideo 925/950, Formatted....................23

TeleVideo 950..o.o.o.*.*.o.e. . .o.o.o.o.o.o.o.. 5

TeleVideo 970 4................ ..42

Tymshare SCANSET 415............................24

Visual 300......................................41

VT100 - see Digital

Volker-Craig VC404...............................6

Volker-Craig VC415......................... 7

Zenith Z19. ..................................... 45. . . .~~~~~~

Special Features 4-4 April 1985- _ _ . _ .. __

46 _____- -

How to EnterSIM3278

You may enter SIM3278 via UNINET or through PACX classi3705. If you enter through the PACX, your terminal mustbe set for half-duplex (or "local echo") and your termi-nal parity must be MARK or SPACE. For UNINET access setyour terminal to full duplex. Upon receiving the initialUNINET "service:" prompt enter

setl5:0

otherwise the XEDIT prefix area will not work with mostterminals. You may still use half-duplex or local-echowith UNINET, but to avoid every character that you enterfram appearing twice on your screen you must also enter"set2:0" while in the PAD ccnmand mode. The parity set-ting for UNINET is immaterial. However it is convienientand often necessary to have the ability to send a <BREAK>signal to the host. If your terminal does not have a<BREAK> key, or if the <BREAK> signal is not of thenecessary duration to be interpreted by UNINET, or if thesignal is not passed on to UNINET but causes some actionin your local terminal or PC, you can implement the<BREAK> signal through UNINET by a <CTRL-^> keystroke (orany other keystroke - see Chapter 3, PAD parameter 200)To do this, upon receiving the initial "service:" promptfromn UNINET, enter

set200:30 <RETURN>

Then signon to NCAR with the subsequent "service:"prompt. Upon receiving the proapt:

WARNING: U.S. GOVERNMENT PROPERY, UNAUTHORIZED USE...

respond with:

DIAL SIM3278 <RETURN>

If the response is "restart", press <RETURN> and re-enterthe DIAL ccnmand. You will then be prompted with themessage

Special FeaturesA-mril 1985

DIALED TO SINM3278S I M 3 2 7 8 V2.x LOO SIMMARE INC.PLEASE ENTER YOUR TERMINAL ID OR '?' (Q TO QUIT)

Now enter the ID associated with your terminal as listedin Table 4.1, followed by <RETURN>. If your terminal isnot listed in table 4.1, it may have been added afterthis guide was published. You may enter the single char-acter "?" and then <RETURN> to get a list of all sup-ported terminals and their IDs. If your terminal is notlisted, or you wish to escape from the SIM3278 mode,enter the single character "Q" then <RETURN> and you willreceive the message:

DROP FROM SIM3278 xxxWARNING: U.S. GOVERMENT PROPERTY .

at which time you can enter <RETURN>, or, if your accessis through UNINET, the <BREAK> signal that you havedefined by <CTRL-^> as described above. You will thenreceive the "." promapt that will allow you to log on inline mode.

Graphics and At this time, you are not able to view graphics outputSIM3278 while connected to SIM3278; however, viewing may be done

by entering another mode without breaking your telephoneor PACX connection. To do this, enter the comand

DISC HOLD <RETURN>

Then log back onto class i3705 in the line mode andretreive your graphics files. You may need the <CTRL-^>keystroke for the <BREAK> signal to get the "." promptthat allows you to enter the logon sequence. You mayreturn to SIM3278 by again issuing a DISC HOLD cammandand repeating the DIAL SIM3278 sequence.

Keystroke Each terminal listed above will have different keystrokeDefinitions For sequences to implement the PF, PA, and other control keysASCII Terminals that are used in the full-screen mode. You will need to

know these keystroke definitions before you make effi-cient use of SIM3278. To do this enter the SIM3278 comn-mand

#HELP <RETURN>

The needed keystroke sequences will be listed.


More cnSIMPC/AZPC2

Unless your IBM' PC can emulate cne of the ASCII terminalslisted in Table 4.1, you must use a software packagecalled AZPC2 (or SIMPC) which runs on an IBM PC with atleast 128K of memory. The floppy diskette and documenta-tion for AZPC2 or SIMPC is available for a ncminal feefracm the Documentation Specialist (see Table 1.4). Be-sides permitting your IBM PC to interface with SIM3278, amajor feature of this package is the inclusion of two IBM4341 caomands that permit easy file transfers between theIBM' PC and the IBM 4341 host system. The file transfersystem is not error correcting. There is also a facilityfor automatic dialing if you have a Hayes Smartmodem. Ifyou enter through UNINET, you should change the duplexsetting franom HALF to FULL when you are initially promptedwith a menu.

To utilize the file transfer features of SIMARE on yourIBM' PC you must access the SITMARE disk by invoking theIBM 4341 exec

GETDISK SIM3278 <RETURN>I... I ...

You will then receive a request for the read password.Respond with "READ".

Accessing SIM3278Through 1fT

Using SIM3278 with UNINET should pose no special prob-lems. SIMNARE was designed with public packet switchingnetworks in mind. When using an IBM' PC, control se-quences (keystrokes of the form <CTRL-x> and the PFkeys) are appended with carrige returns so that packetsare sent whenever these keys are struck. Other terminalsrequire carriage returns to terminate control sequences.Same minor performance degradation in features such ascharacter insertion while editing may occur and theresults will be delayed rather than immediate, sinceUNINET will not send a packet until -<RETURN> is entered.As mentioned earlier, when the the initial UNINET "ser-vice:" prompt is received, you should enter "set200:30"so that the keystroke <CTRL-^> acts as a <BREAK> signalto the IBM 4341. This is often a useful method of caus-ing the system to produce a "." prompt so that cnmands

.may be issued while still in the line mode.

PC-TALK PC-TALK is a public domain software package for the IBMPC that only works through PACX class i3705 or throughUNINET and supports file transfer to and fron the IBM4341 host. This file transfer system is not errorcorrecting. PC-TALK does have an error correcting filetransfer facility for use between two personal computersrunning PC-TALK. The floppy diskette and documentationfor PC-TALK are available from FREEWARE, P.O. Box 862,Tiburon, CA 94920, for a modest fee. However PC-TALK is

Special- Featuresav-,ril 15'85 4-7

not a licensed product and can be copied from anyone whohas the diskette. Special software to support filetransfers to and from the IBM 4341 system and an IBM PChave been implemented on the IBM 4341 computers; detailsare included below. If you already have the PC-TALKsoftware you should configure your canmunications tableas follows:

71MN017019127

Data BitsStop BitParityEchoStrippedStrippedStrippedPacing Character

PC-TALK ThroughUNIET

PC-TALK file transfers pose no problem through UNINET,but the default PAD profile should be changed so thatUNINET does not append null characters to carriage re-turns and line feeds sent by the IBM 4341. To change tothe proper profile, respond to the initial UNINET "ser-vice:" prompt with

prof3 <RETURN>

At the next "service:" pranpt you can sign on to NCAR.You may, of course, invoke this profile at any time byfirst entering the PAD command mode and then issuing theprof3 command.

PC-TALK: IBMPC to To move a file frcm your IBM PC to the IBM 4341 at NCARNCAR File Transfer while using the PC-TALK software, enter the coanmand

PCTALKUP <filename> <filetype> <filemode> <RETURN>

You will then be prompted by the message

ENTER ALT-T TO BEGIN TRANSMISSION (F FILEENTER 'ENTER' TWICE WHEN FILE IS DC(EDMSM7706I TERM INPUT-TYPE NULL LINE FOR END CF DATA

You should respond with

<ALT-T>

Special-Features 4-8 A-rril 1985

The system then replies with

== TRANSMIT A FTILE =specification:

to which you type

local-filename <RETURN>I~~~~...

where locatlfilename is the file on your IBM PC. Thelast line containing specification: local-filenane shouldthen reapear on your screen with the loca1filenameappended with the three characters "=p." indicating thatthe "." pacing character is in effect. If this does notappear you must change your program default parameters toinclude this pacing parameter. Then to start the actualdata transmission, enter

<RETURN>

The file transfer then takes place and upon cmpletionthe IBM PC replies with

=== END CF FILE ==

You should then type

<RETURN> <RETURN>

If you do not get the "." prompt to allow you to entercanmands to the IBM 4341, type

<CTRL-END>

Special Features'Avril 1985 4-9

PC-TALK: NCAR toIBM PC file

Transfer

To move a file from the IBM 4341 to your IBM PC whileing the PC-TALK software, issue the IBM 4341 ccamand

PCTALKDN <filename> <filetype> <filemode> <RETURN>

You will then be prompted by the message

ENTER ALT-R TO BEGIN RECEIVING THE FILE, THEN ENTERWHEN THE FILE HAS BEEN RECEIVED, ENTER ALT-R AND ENTER AGAIN

You should respond with

<ALT-R>

after which you will get the pranpt to enter the filename you want to call the down-loaded file on your IBM PCdisk:

==== RECEIVE A FILE ==Specification:

Respond with

local-filenae <RETURN>

You will then observe a short period of activity on yourdisk. Wait until the disk is no longer active; thenenter

<RETURN>

The file transfer will then take place and can beobserved on your screen. When the file is transfered theprcmpt R;T=... will appear. At that time terminate thetransmission by entering

<ALT-R>

Special Features

us-

4-10 Av-% i 198 5

You should then get the message

=== RECEIPT CF FILE local filename TERMINATED ===a ~ ~ . . . . . . .

NOTE: The file will contain the CMS prompt R;T=... asits last line. As usual, a <CTRL-END> will get you intothe CMS canmand mode.

!TE[RS YTERM is a software package for the IBM PC and its closeimitators that may be used to access the IBM 4341 onlythrough PACX class io. YTERM cannot be used throughUNINEr. YTERM may also be migrated to other 8088 or 8086based machines that run S-DOS or Single User CP/M-86operating systems, but knowledge of 8086 architecture andassembly language is required for a successful migration.Besides providing terminal emulation and "programmertools", YTERM provides full error-correcting filetransfers to and fron the IBM 4341. Since YTERM entry tothe IBM 4341 is through PACX class io, the terminal pari-ty must be set to SPACE.

Unlike the SIN4ARE and PC-TALK packages mentioned above,the NCAR Scientific Computing Division does not distri-bute YTERM. The YTERM software and documentation areavailable fracm the Yale University Ccmputer Center, 175Whitney Avenue, P.O. Box 2112, Yale Station, New Haven,CT 06520.

FILE TRANSFEIS:UPIDODING AND

DOWQADfIG

The AZPC2, SIMPC, PCTALK, and YTERM software systems men-tioned above all have support software on the IBM 4341that permit you to transfer files to and from the IBM4341 (known as uploading and downloading) with an IBM PC.However, it is possible for you to write communicationssoftware for your computer system that will upload yourlocal files to the IBM 4341 with no special supportsoftware on the -IBM 4341. This will usually require anintimate knowledge of the software on your cmnputer. Thekey to this process is the IBM 4341 line mode editorXEDIT. Since this editor accepts input only one line ata time (a line is a string of characters followed by acarriage return) and only after it has issued a "."prompt, the procedure that you would follow in construct-ing uploading software would be as follows:

1. Invoke XEDIT on the IBM 4341.

2. Enter the INPUT mode.

3. Send cne line of your file.

Special FeaturesAvpril 1985 4-11

4. Wait for the "." prompt. (Actually the promptstring consists of six characters, CR (carriage re-turn), LF (line feed), DC3 (device control 3), .(period),. DEL (delete), and lastly, DC1 (device con-trol 1). The decimal values for these charactersmay be found in Table 3.2).

5. Repeat the third and fourth step above until filetransfer is complete.

6. Issue the FILE cammand to close the file.

Since this process must use the line editor, entry mustbe through UNINET or the PACX class i3705.

Downloading can be acccmplished in line mode by issuingthe TYPE command and specifying the desired file. Thefile will then be sent to your terminal or computer.However, you must be aware that each line is prependedwith the string of four control characters CR (carriagereturn), LF (line feed), DC3 (device control 3), DEL(delete). Furthermore, if you are connected through

UNINET with the default profile, each carriage return andline feed sent to the terminal is followed by six nullcharacters (all zero bits).

GRPHICS FILE Graphics file transfer frcm NCAR to the local user's ter-TRA1'FER minal is possible through UNINET or through direct phone

connection through all PACX classes. Graphics filetransmission at this time is not possible while connectedthrough SIM3278. A wide class of graphics terminals willsoon be supported by NCAR for display of metacode plotfiles created on the NCAR mainframes. The metacode filetransfer is initiated through the PLT EXEC or the newPLTNEW EXEC. (See The NCAR IBM 4341 Gateway Ccmputers,NCAR/TN-234+IA and the April 1985 RECORD)

UNINET users receiving graphics metacode should set theirX.3 PAD parameters to guarantee transparent pass-throughof the metacode file. There are two ways to do this. Onreceiving the service: prnmpt on initial connection toUNINET, or after a <CTRL-P> sequence to get into the PADccanand mode (see Chapter 3), issue either

profl <RETURN>or,

set6:0,set9:0,setl4:0 <RETURN>

The first of these commands has the disadvantage that thelocal character echo frcm the PAD is disabled. It isalso impossible to return to the PAD cammand mode afterthis command has been issued.


CMMNICa)TIONS A data carnunications path can be established between twoBE'1N'ETWD personal computers using the PACX. The PACX thus per-

PESCZAL COUMPUTWE forms the function of a "null modem". The service is im-plemented by the PACX classes pcl, pc2, and pc3. Thefollowing requirements must be met in order to effect thecommunication:

* Both conputers must be connected to the same PACXclass pcx and the two connections must be madewithin ten minutes of each other to avoid the PACXtime-out feature.

* The terminal profiles of each computer must be thesame, i.e., the parity setting, the number of databits, baud rate, etc., must be identical.

* Both computers must have file transfer packages tocammunicate files.

WARNING: If two other users are trying to connect at thesame time to the same PACX class pcx as you and the oneyou are trying to communicate with, it is possible thatyou may make a connection with the wrong person. Forthis reason it is advisable for each party in a connec-tion to send a message of identification. Access to thisfeature through UNINET is not yet possible.

Special Features4-13April 1985

CPHI~ER .5: WAS: TMIE IXXLE SPOCLINI CrfUhNI@ATIC SLBSYS'TEM

INI'IEXXT IcIJ The Remote Spooling Communication Subsystem (RSCS) is asingle purpose operating system for a virtual machine onthe IBM 4341 computers that is dedicated to acceptingyour files and transferring them to the destination youspecify. Typical destinations include the CRAY,CA andCRAY,C1 computers or the reader of a virtual machine.

The most common use of RSCS is as a store-and-forwarddata communications system for remote batch job entry toone of the two NCAR CRAY-1 cnmputers. Combining the useof RSCS and a personal virtual machine on the IBM 4341system provides a powerful tool for interactive editing,job entry to a CRAY-1 computer, interactive perusal ofresults, and file routing to your remote printer.

SUPPORPEDPEIOTOiD5 AND LINE

SPEEDS

RSCS is a batch entry system that supports synchronousline transmission only. The dial-up line speeds and pro-tocols supported are shown in Table 5.1. In addition,leased-line connections of up to 56 kilobits per secondcan be supported with any of the protocols listed. RSCSis not accessible through UNINET.

Table 5.1SCS-Supported Line Speeds and Protocols

ProtocolUT200

2780/3780

HASP

Speed (bps)480048002000

48004800

4800480024002000

Area (303)494-6665494-6668499-6467

494-0636494-4022

494-0618494-6662494-6667494-6111

Note: UT200 refers to Control Data Corporation s User Terminal200 protocol described in CONTROL DATA 200 USER TERMINALPublication No. 82128100.

2780/3780 refers to IBM's bisynchronous protocols asdescribed in the IBM publications IBM Systems ReferenceLibrary: General- Information-Binary Synchronous Ccmurni-cations, GA27-3004-2; and Component Information for theIBM 3780 Data Ccmunication Terminal, GA27-3063-3.

April 1985

Line No.03A039038

02902D

02802B02A02C

5-1 RSCS

HASP refers to the IBM bisynch Multi-Leaving protocoldescribed in the. IBM publication IBM VM/370: RSCS Net-working Logic, LY24-5203.

PEIMISSICN TO UERSCS

Once it has been determined that you have the proper ter-minal hardware and software to use RSCS, you will need torequest an "RSCS signon" fraom SCD's Data CaimunicationsGroup. Contact Bill Ragin at (303) 497-1258 for helpo

You are then assigned an RSCS site identification, re-ferred to in this guide as a linkid, and a site profileis created that is tailored to your particular needs.

LANB a ,GE

P1IMKl THE

To assist you in routing jobs to and from your site andto allow you access to status information about jobs andnews items fran NCAR, RSCS has been modified by SCD toallow added commands. In addition to routing and statuscommands, other rcmmands described in the "NCAR ADDEDCOMMNDS" section of Chapter 6 in this guide are alsoavailable. Smane of the commands are specific to a par-ticular protocol and are noted as such. The standard IBMRSCS commands are also available and are described in thesection "RSCS STANDARD CDMMNDS" in Chapter 6. A de-tailed description of these IBM` RSCS commands along witha description of system messages is found in the IBM pub-lication: IBM Virtual Machine/System Product: RemoteSpooling Communications Subsystem Networking ProgramReference and Operations Manual, SH24-5005.

1. Check Table 5.1 for the proper telephone number foryour protocol and line speed.

2. After the carrier tone is detected, enter the properSIG(CN record for your protocol as described in theSI(GNC Record section below. RSCS will not promptyou for the SIGNON record unless you are configuredfor use of the UT200 protocol. The SIGNCN recordmust be the first record RSCS receives and must becorrect; otherwise you must hang up and re-dial.

3. When the SIGNCN record is accepted, RSCS will replywith the message:

DMTxxx905I SIGNON CF LINK linkid COMPLETE

4. The system is now ready to accept cmands.

April 19855-2

SIGNING CNTO RSCS Only dial-up users need to sign onto RSCS; users connect-ed by leased lines are "automatically" signed on. Signonprocedures vary slightly for each protocol. In the fol-lowing SIGNCN records, described in the SIGNON Recordsection below,

SIGNON or /* SIGNtON must begin in column 1.

linkid is your RSCS site id.

rscupd is your RSCS optional user password.

The SIGNON record allows you to control certain parame-ters that tailor your linkid to your particular needs.The SIGNCN parameters are specified in a site profilewhen the site linkid is created, but they can be overrid-den with the SIGNCN command. The parameters can also berespecified in the site profile by contacting the GeneralLiaison listed in Table 1.4. The current SIGNON parame-ter configuration can be determined by the DIS,SIT com-mand described below in the "NCAR ADDED COMMANDS" sec-tion. The optional parameters are defined below. In theSIGNON record, if a parameter has a default it is under-lined. The optional parameters must precede the PWDparameter in the SIGNON record.

SIGNON OptionalParameters

SINM Place remote station in single output mode. This causesall print output to be held until solicited with theWRI, PRI command.

MULM Place the terminal in multiple output mode. Any outputwill be immediately printed or queued for the printerupon receipt in the RSCS output queue.

P120 Width of print line is 120 columns.

P132 Width of print line is 132 columns.

CMPR Blank compression in effect for 3780 protocol.

CRT8 Dimensions of terminal display are 80 columns by 13lines.

CRT5 Dimensions of terminal display are 50 columns by 20lines.

HDRY Print a one page separator between output files

April 1985 5-3 RSCS

HDRN

TRA1

TRA5

PCHY

PCHN

TRSY

TRSN

Do not print a one page separator.

Print a one line trailer.

Print a five line trailer. If neither TRA1 or TRA5 isspecified, then no trailer is printed.

Configure linkid to contain a virtual punch unit.

No virtual punch unit included.

Transparent mode (binary data mode) active.

Transparent mode inactive.

SIGNQ Record For HASP

SIGNON Record For 2780/3780

SIGNON linkid [optional parameters] [PD=rscupwd]

optionatparameters[SINM [P120] [HDRY] [TRA1] [PCHY] [TRSY] [CMPR][MUL4M [P132] [HDRN] [TRA5] [PCHN] [TRSN]

SIGQXN Record For I71200

SIGNCON linkid [optional parameters] [PWD=rscupwd]

optional< parameters:[SINM] [P120] [CRI8] [HDRY] [TRA1] [PCHY][MULM] [P132] [CRT5] [HDRN] [TRA5] [PCHN]

April 1985

/*SIGNCN linkid [optional parameters] [PD=rscupwd]

optional parameters:[SINM] [HDRY] [TRA1][MULMI [HDRN] [TPA5]

5-4

SIBMETTIMG A JCBTO THE CAY-1COUT;ES AND

GETr' IT BACK

Job files submitted to one of the CRAY-1 canputers(CRAY,Cl or CRAY,CA) must contain a first record whichspecifies:

ClJOB or CAJOBI~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.

depending upon whether the job is to be run cn theCRAY,C1 or CRAY,CA machine.

Note: For UT200 protocol users, the REA, RDR command must pre-cede the job file and the job file must have *END as thelast record.

FOR UT200 USERS ONLY, once the job file has completed itsentry, RSCS responds with the message:

DMTUT2966I LINK linkid CARD FILE SENT TO NCARIO RSCSNET

After further processing by the IBM 4341 system, a mes-sage detailing the sequence number assigned to the jobfile is returned:

DMIxxxl71I FROM NCARIO RSCSNET:SEQUENCE NUMBER ASSIGNED IS IOnnnn

where "nnnn" is a four-digit number.

When the job file is successfully transferred to the tar-get CRAY-1, the following message is returned:

DMbxxxl71I FROM NCARIO RSCSNET:4341 JOBCON Cx WORKED.CODE 0. mm/dd/yy hh/mm/ss IOnnnn

where "x" is A or 1 for the CRAY,CA or CRAY,C1 machinesrespectively, and "mm/dd/yy hh/mrrss" is the date andtime and "nnnn" is the sequence number of the job.

Note: RSCS does not check the validity of the job file sent tothe CRAY-1 computers. In other words, RSCS does notcheck for a valid scientist number, project number, orvalid syntax in the JCB record. Any file following aC1JOB or CAJCB record is. sent to the designated CRAY-1machine without modification or error-checking. If theCRAY-1 computer finds a syntax error in the JCB record,the job will be rejected and the file will be lost.

April 1985 RSCS5-5

Job files must also contain a DISPOSE record directingthe job output back to an RSCS output queue, a virtualmachine, or sane other destination. The basic form of ajob file, then, is:

CxJOB is either C1JOB or CAJOB depending upon whether thefile is to be sent to the CRAY,Cl or the CRAY,CA com-puter.

Disposing JobOutput

Disposing to theLoci. NCAR Printer

for Mailing

The DISPOSE record specifies where you want the output ofthe job to go. Typical variations are described below.For more detailed information about the DISPOSE recordand other CRAY-1 JCL, refer to The CRAY-1 Computers: AGuide to Supercomputing at NCAR (NCAR/TN-226+lA).

Output disposed to the NCAR printer will automatically betagged with the site mailing code that is associated withthe scientist number of the job. This tag allows Opera-tions personnel to affix the proper shipping label to theoutput. If you change your work site and you want youroutput mailed to your new site, you must notify the Mail-ing List Change consultant (see Table 1.4, chapter 1 ofthis guide) to update your site mailing code. To haveyour output printed at NCAR and mailed to you, theDISPOSE record syntax should be:

DISPOSE,DN=$OUT, MF= IO, DC=PR, DEFER.

Disposing to the The DISPOSE record syntax is shown below. The TEXTOutput Queue of parameter directs CMS to send your file to the RSCS out-

Your Remote Site put queue associated with your (or sameone else's)linkid.

DISPOSE, DN=$OUT,MF=IO,DC=RS, DEFER, ^

TEXT=-'LOClinkid, [DIST=identifier] .

If the "DIST=-" parameter is included, identifier will bedisplayed when a DIS,SIT command is issued. This willassist you in uniquely identifying your output file fromothers in the output queue.

April 1985

CxJCBJOB, JN=jbnae, US=scitproj .DISPOSE,DN=$OUT,DEFER,MF=mf,DCdc, [TEX= . . .options'... ], [TID=tid].

.... Program File and other JCL .....

*END (for UT200 protocol cnly). ............

RSCS 5-6

Disposing to YourVirtual Machine

If in addition to having a batch terminal for entry toRSCS, you also have an interactive terminal for entry toCMS, you may want to have jobs disposed to your virtualmachine so that you may peruse, edit, or print them, orpossibly transfer them to the output queue of your RSCSlinkid. To dispose a job to your virtual machine, use:

DISPOSE,DN=$OUT,MF= IO,DEFER.

Disposing to Any You are not restricted to disposing output to your ownVirtual Machine virtual machine. Output can be directed to any virtual

machine userid using:

DISPOSE,DN=$OUT,DEFER,MF= IO, TEXT=- USER=userid' .

Disposing Metacode Metacode plot files cannot be disposed directly throughPlot Files RSCS as they are created by the CRAY-1 machines. The

1440 byte plot records must first be broken into 80 byterecords. This new 80 byte record file is known by thename $PLTC. The original $PLT file remains intact. Youmust concatenate the 80 byte records into 1440 byterecords to use your local metacode translator. The se-quence to split up and dispose the metacode file is:

PLTCONV.DISPOSE, DN=$PLTC ,MF--IO,DC=RS, DF=BI, DEFER, ^

TEXT=-LOC=linkid, [DIST=-identifier] '.

Note that the DISPOSE record syntax is similar to thatfor the $OUT file with the file name changed to $PLTC andthe data format, DF, changed to binary. The $PLTC fileis a PUNCH file. Since $PLTC files are binary they can-not be sent to a UT200 site. Also $PLTC files cannot berouted fram a virtual machine to RSCS.

Making an Error inthe DISPOSE Record

April 1985

If the CRAY-1 ccnputer finds a syntax error in theDISPOSE record containing the $OUT parameter, the entireDISPOSE record is rejected. Any information created inthe $OUT file is sent to the virtual reader of the virtu-al machine associated with the scit appearing in the JCBrecord. If there is no virtual machine associated withthe sci# the $OUT file is printed on the NCAR printer andmailed to you.

5-7 RSCS

SJDING FILES TO AVI MAL CHINE

Files can be sent from an RSCS remote site to the readerof a virtual machine on either IBM 4341. However, it isnot possible to append a file name or file type to atransferred file. Furthermore, a fixed length recordformat and a record length of 80 bytes will be assignedto the file by RSCS. The file to be sent must have asits first record:

ID NCARIx userid

where x is 0 or A and userid is the virtual machine idof the user to receive the file.

FOR UT200 USERS ONLY, successful transfer is indicated bythe following RSCS response:

DMTUT2966I LINK linkid CARD FILE SENT TO NCARIx userid

with no further messages.

For HASP users and those using 2780/3780 protocols, thereis no response. A failure mode elicits another messagewhose content depends on the type of failure.

Note: Files moved using the UT200 protocol must have as thelast record *END.

SEZ]DING MSSAGES Messages can be sent from RSCS to any virtual machineFECM'RSCS that is logged on. The message format is:

MSG NCARIO userid ... message text...

where userid is the virtual machine logon name of therecipient. CP1. is the userid for messages to the NCARoperations personnel. Messages sent with this commandwill be displayed immediately on the recipient½s termi-nal.

Messages using this command cannot be sent to a useridthat is not logged on. To send a message to a useridthat is not logged on, refer to the above section onsending files to a virtual machine.

There are no acknowledgements from RSCS about the successor failure of the message transfer.

April 1985RSCS 5-8

REEIVING ESSGESFROM THE ECPEAR

USING A VIcIrPLMAfINE WITH RSC

Interrogating RSCSAbout Its Status

On occasion the NC3R operator may need to send you a mes-sage informing you of an event that will affect you as anRSCS user. These messages will appear as spool files inyour RSCS output queue. You can identify a spool file asan NCAR operator message by the title OP1MESSG appearingin the file descriptor displayed when a DIS,SIT commandis issued (See Chapter 6 for command descriptions).

If, in addition to having an RSCS linkid, you also have avirtual machine userid, while you are logged onto thevirtual machine you can interrogate RSCS about its statusand the status of jobs in its queues, send messages toRSCS users, and route jobs from the virtual machine toRSCS, among other things.

To do this you must send a message to RSCS of the form:

SMSG RSCS ... message text ...

where the message text is itself a command to RSCS. TheQUERY ccnmand allows you to obtain RSCS status informa-tion. Particular variations of interest are as follows:

To determine the status of the RSCS ports:

SMVG RSCS QUERY SY A

To determine the status of your jobs in your RSCS outputqueue:

SM3G RSCS QUERY linkid Q

To determine the load in all the RSCS output queues

SMSG RSCS QUERY SY Q

Refer to the IBM RSCS command QUERY for further options.

April 1985 5-9

Sending A Message You may send a message to any RSCS linkid provided thatTo A Signed-on linkid is signed on. You may use the above SMSG RSCS

RSCS Site QUERY SY A command to determine if the linkid is signedon. The ocmmand format to send a message to an RSCSlinkid is:

SNSG RSCS MSG linkid ... message text...

Routing Files From The ROUTE EXEC gives you a wide range of options forYour Virtual routing jobs from your virtual reader or disk to RSCS, to

Machine another virtual reader, or to the printer.

The format of the ROUTE command is:

ROUTE [[FILE=] file_name] [[TYPE] file type] [[MDDE]=file mode][TO=]destination [[NAME=] id] [[SPOOLID=] spoolid][[HOLD=] hold_spool file]

'[ ]' indicates optional keywords and parameters.

Parameter Values,,

filename

file_type

file_mode

is either the file name of the CNSfileid to be routed or, if a readerspool file is to be routed, the newfile name assigned to a created CMSfile.

is either the file type of the CMSfileid to be routed or, if a readerspool file is to be routed, the newfile type assigned to a created CDSfile.

is either the file mode of the CMSfileid to be routed or, if a readerspool file is to be routed, the newfile mode assigned to a created CMSfile. If the file is to be routed,then any valid file mode letter or an"*" may be used (in which case, mini-disks are searched alphabetically). Ifthe file is to be created, then thedefault value is "A".

5-10 April 1985

destination

id

spoolid

hold spool file

is a required value specifying wherethe routed file is to be sent. Accept-able values are USER, SITE, DISK,PRINTER, or TERMINAL. If USER or SITEis specified, then "id" must be speci-fied. If DISK is specified, then"spoolid" must be specified. The DISKoption creates a CI3 file with a fileidof either "file name file_typefile_mode" (see above) or a form of thereader spool file fileid. If PRINTERor TERMINAL is specified, then either aCNS file or a reader spool file iseither printed or displayed on the ter-minal.

is the user ID of a user's VirtualMachine. If USER is specified for"destination", the file will be sent tothat user's virtual reader. If SITE isspecified, then "id" is the RSCS linkidwhere the file will be sent.

is the spoolid of a file in your vir-tual reader to be routed.

is an option to retain or not to retainthe spool file in your reader. Accept-able values are YES or NO. If thevalue is NO, the file will be deletedfran your spool file. The defaultvalue is YES.

Examples:

Send the CMS file MYJCB OUTPUT A to an RSCS linkid ofCOJEFF:

ROUTE MYJCB OUTPUT A SITE COJEFF

Print a reader spool file with SPOOLID of 1234 and do notretain it in your reader:

ROUTE TOPRINTER SPOOLID=1234 NO

April 1985 5-11

Send a reader spool file with SPOOLID of 1234 to the vir-tual reader with a user ID of M3RRIS:

ROUTE fO=USER M3RRIS 1234

Create a CS file with fileid of MYFILE MYTYPE A franreader spool file with SPOOLID 1234 and hold the file inyour reader:

ROUTE MYFITE MYTYPE TO=DISK SPOOLID=1234

Usage Notes:

You may determine if there have been any updates to theccammand by typing:

HELP ROUDE or ROUTE ?

which will also give you information on how to use thecaimand.

April 1985RSCS 5-12

cE1P'TER 6: 13SCS COXMND LANGUAGE

The RSCS command language allows you to control a varietyof functions frcm your terminal and obtain status infor-mation about your job and the RSCS system. NCAR's imple-mentation of RSCS contains additional locally definedcommands as well as the standard IBM RSCS commands. Sameof the NCAR-implemented commands are protocol-specificand are noted as such. For most users, the NCAR-implemented commands will suffice, since several of thesecommands invoke IBM RSCS commands. In fact, some of theIBM RSCS commands require advanced knowledge of IBM filestructure, so the NCAR cammands facilitate easy use ofRSCS.

Minimal CammandSet

Once you are able to sign onto RSCS, you can operate thesystem and perform the most basic functions of sendingand receiving a job file by using the following minimalcoainand set:

DIS,SIT

WRI, PRI

END

Display the RSCS output queue status toobtain spool file numbers needed to retrievejob file.

Initiate the transfer of a designated RSCSoutput spool file to the remote terminal.

Terminate an RSCS session.

Initiate the transfer of a file fromsite to NCAR (for UT200 users only -protocols simply send file without a

the remoteotherprologue).

RSCS CO1MNDS

REA,RDR

IN-ril 1985 6-1

SCS CoamandSummary

The following table summarizes the conands and theirfunctions. Detailed syntax information for these com-mands is included in the following sections.

Table 6.1RSCS Cmands Suminary

Function

Restart or reposition in a backwarddirection the file currently beingtransmitted

Alter one or more attributes of a file.

Requeue files in send or receive state(NCAR operator command only).

Display CRAY,C1 job status.

Display CRAY,CA job status.

Display IBM RSCS command HELP file.

Display current Daily Bulletin.

Display RSCS output queue status.

Stop file transfer and deactivate anactive ommunication link.

Interrupt file transfer to NCAR for UT200.

Terminate an RSCS session.

Discontinue processing of the currentlyactive file.

Resume transmission on a conmunicationlink previously in HOLD status.

Reposition in a forward direction thefile currently being transmitted.

RSCS COnMNDS

CommandNfame

BACKSPAC

CHANGE

CLOSE

DIS,C1

DIS,CA

DIS,HEL

DIS, NEW

DIS, SIT

DRAIN

DRO, RDR

END

FLUSH

FREE

FWDSPACE

CommnandOrigin

IBM

IBM

IBM

NCAR

NCAR

NCAR

NCAR

NCAR

IBM

NCAR

NCAR

IBM

IBM

IBM

�

_

6-2 avJr i 198 5

Tb 6. xn.

Table 6.1 (cont.)RSCS Comnands Sunmary

Function

Add a header file to output files.

Suspend file transmission withoutdeactivating the link.

Suspend receipt or transmission of files.

Send a message line to a user s console.

Request that files be transmitted on thelink when they arrive in the output queue.

Do not add a header file to output files.

Discontinue appending trailer records.

Reorder files in the output queue.

Remove and discard all or specifiedinactive files.

Request system information for a link,a file, or the system in general.

Activate receipt or transmission of files.

Initiate file transfer to NCAR for UT200.

Position file being transmitted tobeginning of file.

Require that output queue files besolicited for transmission.

Start file transmission for designatedclass of files.

Append trailer records to output files.

Mbve file from one RSCS linkid toanother (NCAR operator ccrmmand only).

Solicit transfer of an RSCS outputqueue file.

RSCS COMMANDS

CcimmandName

HDR

HO

HOL

MSG

MUL

NOHDR

NOTRA

ORDER

PURGE

QUERY

RDY

REA, RDR

REW,PRI

SIN

START

TRA

TRANSFER

WRI,PRI

CcnmandOrigin

NCAR

IBM

NCAR

IBM

NCAR

. NCAR

NCAR

IBM

IBM

IBM

NCAR

NCAR

NCAR

NCAR

NCAR

NCAR

IBM

NCAR

Av-ril 1985 6-3

~NC7ATIClL The following notation is used to define the command syn-VWENI(;CNS tax in this chapter:

1. Truncations and abbreviations of comands:

Where truncation of a camnand name is permitted, theshortest acceptable version of the comrand isrepresented by uppercase letters. Operands and op-tions are specified in the same manner. Where trun-cation is permitted, the shortest acceptable versionof the operand or option is represented by uppercaseletters in the ccrmand format box. If no minimumtruncation is noted, the entire word must be entered(indicated by all capital letters).

2. The following symbols define the command format andshould never be typed when the actual command is en-tered:

underscore brackets [ ]

braces { } ellipsis .

3. Uppercase letters and words, and the following sym-bols, should be entered as specified in the formatbox:

asterisk * parentheses ( )ccrna , periodhyphen - colon :equal sign =

4. Lowercase letters, words, and symbols in the camandformat box represent variables for which specificinformation should be substituted.

5. Choices are represented in the command format boxesby stacking:

ABC

RSCS COMMANDS 6-4 April 1985

6. An underscore indicates an assumed (default) option.If an underscored choice is selected, it need not bespecified when the conmand is entered. For example:

ABC

indicates that A, B, or C may be selected. If B isselected, it need not be specified. B is assumed ifnothing is specified.

7. The use of brackets denotes choices, one or more ofwhich may be selected. For example:

A[B][C]

indicates that you must specify A, and that you mayspecify either, both, or neither B nor C.

8. The use of braces with options denotes choices, oneof which must be selected. For example {AIBIC} or:

[A]<B>[C]

indicates that you must specify either A, or B, orC.

9. The use of brackets with options denotes choices,one of which may be selected. For example, [AIBIC]or:

[A][B][C]

indicates that you may enter A, B, or C, or you mayomit the field.

10. An ellipsis indicates that the preceding item orgroup of items may be repeated more than once insuccession. For example, (options ... ) indicatesthat more than one option may be coded within theparentheses.

ASCS CONMANDSApril 1985 6-5

DFS IIEIEI cr

TEllai

The terse forms of command responses are shown followingeach command. While these are usually sufficient to di-agnose problems, it may be necessary to refer to the ver-bose explanations of these comanands given in Appendix Bof IBM Virtual Machine/System Product: Remote SpoolingCoarmunications Subsystem Networking Program and Opera-tions Manual, SH24-5005. Portions of the following sec-tions have been taken fraom this document.

The following terms are used in the definitions of theccmmands in the following sections:

link The transmission path between the NCAR RSCS virtualmachine and a remote terminal system. A link is activewhen the remote terminal has signed on to RSCS.

active file

inactive file

A file being transmitted via the link.

A file queued for transmission via the link.

spoolid A four-digit number assigned to identify queued files.

userid A logon code for an interactive virtual machine.

line driver RSCS software that services a particular protocol.are three line driver identifiers:

for HASPfor UT200for 2780/3780

NCAR-AUCEDcommum

A description of the cmnmands that NCAR has added to RSCSfollows. Sane of these commands directly invoke IBM RSCSstandard cDmmands but have been added to the command re-pertoire to assist users who are converting to RSCS frmathe MDDCOMP.

ISCS COMMNDS

SMLUT2NPT

There

Av-~r i 198 56-6

DIS,Cx Where x is 1 or A. Display status of jobs or subset ofjobs on the CRAY,C1 or CRAY,CA.

DIS,<Cl> I| [ identifierl identifier2 ...[CA]

identifier specifies character string(s) that can beused to identify your job or jobs. This islimited to the sequence number assigned orthe logon name of the virtual machine asso-ciated with your scientist number (or ifyou do not have a virtual machine, the useridentification associated with your scien-tist number). When the optional parametersare used, only lines containing thesestrings are displayed. Omission of theparameters gives a display of all jobs onthe designated CRAY-1 computer.

Responses:

DMTxxx980IDMTxxx982IDMTxxx983 IDMTxxx984IDMTxxx981IDMTxxx204E

CRAYCxJCBIDENT

JOB STATUS FROM mmn/dd/yy hh: rrm:ssPGMR CPU JOBNAME LEFT 5EM PRI STATUS

seq name time memINVALID KEYWORD keyword

prior status text

Explanation:The variables of message DMTxxx981I are defined as fol-lows:

seq - the sequence number assigned to your job andreturned to you upon successful submission.

name - the logon ID of the virtual machine associatedwith your scientist number, or, if youhave no virtual machine, your user ID.

time - the CPU time remaining for the job, in seconds.mem - the number of 512K words of memory used.prior - the relative priority of the job.status text - description of the state the job

is in currently.

RSCS COMMANDS

- - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --~~···~·· ~

Av-% i 198 5 6-7

DIS,NEW Display the current Daily Bulletin.

DIS, NEW

Responses:

DMTxxx981I ... news file text...DMTxxx204E INVALID KEYWORD keyword

DIS,HEL Display a HELP file for the IBM RSCS conmand.

DIS,HEL [comnand]

canmand is the IBM RSCS command for which the HELP fileis requested. If this parameter is not given,the response is a list of all available IBMRSCS command HELP files.

Responses:

DMTxxx981I ...help file text...DMTxxx204E INVALID KEYWORD keyword

DIS,SIT Display the status and descriptors of files queued onyour linkid and number of files being transmitted. Seealso: IBM RSCS command "QUERY linkid QUEUE." You mayalso want other detailed information about your files.Refer to the IBM RSCS command "QUERY FILE."

DIS,SIT

Responses:

DMTxxx990I SITE linkid PORT nnn RDR {IDLE | ACTV } PRT MDDE{SIN I MUL} {HDRY I HDRN} {NTRA I TRA1 | TRA5} class

Refer to the IBM RSCS command "QUERY linkid Q" for formatof status display and other responses.

April 1985RSCS COMMANDS 6-8

Explanation:

nnn - three-character RSCS port code.IDLE - the transmission link f rcm the site

to NCAR is idle.ACIV - the transmission link fran the site

to NCAR is active.SIN - the output mode is set to single mode.MUL - the output mode is set to multiple mode.HDRY - header records are added to output files.HDRN - no header records added to output files.NTRA - no trailer records added to output files.TRA1 - one trailer record added.TRA5 - five trailer records added.class - printer class.

WRI,PRI Request transmission of file residing in your RSCS outputqueue. The file cannot be in HOLD status and its CLASSmust match the current printer class.

WRI,PRI spoolid

spoolid is the four-digit identifier for the file to betransmitted.

Responses:

DMTxxx970I LINK linkid MISSING PARAMETERDMTxxx526E EILE spoolid NOT DOUND - NO ACTION TAKENDMTxxx204E INVALID KEYWORD keyword

REW,PRI Restart the current file transmission fran your RSCS out-put queue at the beginning of the file. See also: theIBM RSCS command "BACKSPAC".

REW,PRI

Responses:

DMTxxx511E NO FILE ACTIVE CN LINK linkidDMTxxx510I FILE spoolid BACKSPACED

ASCS COO0NDSZ-1Avril 1985 6-9

HOL Suspend receipt or transmission of files fran the remotesite.

EHOL | { PRI | RDR }

PRI suspend receipt of files fran NCAR.

RDR suspend transmission of files to NCAR. RDR does notapply to the 2780/3780 protocol.

Responses:

DMTxxx963I LINK linkid READER HELDDMTxxx6llI LINK linkid FILE TRANSMISSICO SUSPENDEDDMrxxx6l2E LINK linkid ALREADY IN HOLD STATUSDMTxxx204E INVALID KEYWORD keyword

RDY Release previously suspended file activity that wasstopped by a "HOL" conmand.

RDY I {PRI RDR}

PRI re-activate receipt of files fran NCAR.

RDR reactivate transmission of files to NCAR. RDR doesnot apply to 2780/3780 protocol. See also: IBM RSCSconmand "FREE."

Responses:

DMTxxx511E NO FILES ACrIVE CN LINK linkidDMTxxx204E INVALID KEYWORD keywordDMTxxx590I LINK linkid RESUMING FILE TRANSFER

SIN Configure your linkid so that transmission of files inyour RSCS output queue must be solicited by the WRI,PRIcommand. See also: SINM parameter on SIGNON record.

SIN

Responses:

DMrxxx961I LINK linkid SINGLE OUiPUT MDDE SET

RSCS COMANDS Av-%r i 198 5* 6-10

MUL Configure your linkid so that files in your RSCS outputqueue are transmitted to your site as soon as they arrivein the queue. See also: MULM parameter on SIGNON record.

MUL

Responses:

DMTxxx962I LINK linkid MULTI OUTPUT MDDE SET

NO'T1A Discontinue the addition of trailer record (s) to filestransmitted fram your RSCS output queue.

NOTRA

Responses:

none - use DIS,SIT to validate.

TRA Add a one-line or five-line trailer record to filestransmitted frcm your RSCS output queue.

| TRA | n

n is either 1 or 5 depending upon whether a one-line trailer or five-line trailer is desired.

Responses:

DMTxxx204E INVALID KEYWORD keywordnote: use DIS,SIT to validate.

NCHER Discontinue the addition of a separator file and headerrecord to files sent franm your RSCS output queue.

NOHDR

Responses:

none - use DIS,SIT to validate.

ASCS 1CDO1NDSavpril 1985 6-11

HIER Add a separator file and header record to files sent fromyour RSCS output queue.

HDR

Responses:

none - issue DIS,SIT to validate.

END Logoff the remote RSCS session. If leased line, resetall parameters to default status. See also: IBM RSCSccmnand "DRAIN".

END

Responses:

DMTxxx570I LINK linkid NOW SET TO DEACrIVATE

REA,r Ready your "reader" to initiate the transfer of a filefrom your site to NCAR. Note: Applies to UT200 protocolonly.

REA,RDR

Responses:

DMTUr2965I LINK linkid READY THE CARD READERDMTxxx204E INVALID KEYWORD keyword

DB,RIJR Purge the current "reader" input file. Note: Applies toUT200 protocol only.

DRO, RDR

Responses:

DMTxxx511E NO FILES ACTIVE CN LINK linkid

RSCS OOMIANDS 6-12 ]%--%ri 198 5

LD~cS ShNIDAMRDcomNEm

BACKSPAC

A detailed description of IBM RSCS commands follows:

BACKSPAC causes the current file being transmitted to berestarted or repositioned backward.

File

nnn

Responses:

DMTCMY204EDMTxxx510 IDMTxxx511E

specifies that the file being transmitted isto be restarted frcm the beginning.is the number of. pages (or punch records) tobe backspaced. The file must contain pageejects.

INVALID KEYWORD keywordFILE spoolid BACKSPACEDNO FILE ACTIVE ON LINK linkid

CHANGE CHANGE alters one or more attributes of an inactive file.The link must not be transmitting the file.

spoolid is the four-digit identifier for thefile to be changed.

RSCS COMMANDS

CHange spoolid (options...*) [ NAme fn [ft] ]

* At least one of the followingoptions must be selected:

[ PRIority nn ][ CLass c ][ COpy [*]nnn ][ DIst identifier ][ HOld I NOHold ]

--

'A-mril 1985 6-13

PRIority nn

CLass c

COpy [*]nnn

DIst identifier

HOld

NOHold

NAme fn [ft]

Responses:

DMTCMX203EDMTCMX204EDMTCMX205EDMITCMX206EDMrCMX207EDMTCMX211EDMTAXM520 IDMIAXM5 21IDMTAXM522IDMTAXM523 IDMTAXM524E

designates the new transmission prior-ity for the file. nn is a decimalnumber frcm 0-99 with 0 signifying thehighest priority. The files in thequeue may be reordered to reflect thenew priority.

designates the new class for the file.c is a one-character alphameric fieldfrcm A to Z or fran 0-9.

alters the number of copies of thefile to be made. The maximum value ofnnn (number of copies) is 255. (TheWRI, and PRI, canmands will only printone of the copies).

changes the identification code of thespecified file. Identification is aone- to eight-character identificationto be associated with the file.

prevents the transmission of the fileuntil it is released by a CHANGE com-mand specifying NOHOLD.

releases the specified file that wasin HOLD status.

changes the file name. If specified,this operand must be the last entry inthe command line.

INVALID SPOOL ID spoolidINVALID KEYWORD keywordCONFLICTING KEYWORD keywordINVALID OPTION keyword optionCONFLICTING OPTION keyword optionINVALID OPTION keyword optionl option2FILE spoolid CHANGEDFILE spoolid HELD FOR LINK linkidFILE spoolid RELEASED FOR LINK linkidLINK linkid QUEUE REORDEREDFILE spoolid ACTIVE -- NO ACTION TAKEN

RSCS COMtNDS 6-14 av-%r i 198 5

crXSE (Ebr NCARiSCS Operator

Only)

This command is used when files are frozen in the send orreceive state. You cannot issue this command, but youmay request the NCAR RSCS Operator to do so (see below).CLOSE deactivates one or more active files on an inactivelink. Active input files are re-queued as inactivefiles, and later retransmission begins at the start ofeach input file. Active output files, which are normallyincomplete, are discarded.

linkid identifies the link on which the files tobe closed are queued. The specified linkmust be inactive when CLOSE is issued.

ALL

INput

OUTput

spoolid ...

specifies that all active input and outputfiles are to be deactivated. Active inputfiles are deactivated and re-queued.Active output files are deactivated andpurged.

specifies that all active input files forthe specified link are to be deactivatedand re-queued.

specifies that all active output files forthe specified link are to be deactivatedand purged.

specifies particular input file(s) to bedeactivated and re-queued.

Note: To make use of the CLOSE facility, you must con-tact the NCAR RSCS Operator and request that this commandbe issued fraom the system console. Specify the exacttext of the command in the request. The CLOSE commandmust be prefaced by SMSG RSCS. For example:

PLEASE ENTER "SMSG RSCS CLOSE linkid"

is a request to reset all the files on the specifiedlinkid to the queued, inactive state.

ESCS COMMNDS

Close | linkid [ALL][INput]

[spoolid]. . . .[OUput

]Nv-ril 1985 6-15

DRAIN DRAIN deactivates the link after the file currently beingtransmitted is completed. The link is deactivated im-mediately if no file is being transmitted when the DRAINcommand is issued. For a leased line link, DRAIN re-initializes the link to its default site profile parame-ters. If a START command is issued for the link beforefinal file transmission is completed, the link is notdeactivated and normal transmission is continued.

DRain |

Responses:

DMTxxx570I LINK linkid NOW SET TO DEACTIVATEDMTxxx571E LINK linkid ALREADY SET TO EEACTIVATE

FLSH FLUSH halts the transmission of a file. The file is ei-ther purged or held, and transmission continues with thenext file queued for transmission. If the file ispurged, all copies 'of the file are purged.

Flush < spoolid > [ ALL ][ * ] [ HOld]

spoolid is the four-digit identifier for the file to beflushed. This field is provided to assure thatthe wrong file is not inadvertently destroyedthrough a timing error.

* specifies that the file currently beingtransmitted is to be flushed.

ALL specifies that all copies of the file beingtransmitted are to be deleted. If this optionis not specified, only the current copy isdeleted and the next copy, if any, is transmit-ted.

HOld specifies that the file being transmitted isnot to be purged, but rather is to be saved andplaced in system hold status. Transmission ofthe file may be restarted after the file hasbeen taken out of hold status by a CHANGE com-mand.

IRSC COMMNEDS 6-16 April 1985

Responses:

DMTCMY203EDM2CMY204EDMTCMY205EDMTxxx580IDMTXXX581E

INVALID SPOOL ID spool idINVALID KEYWORD keywordCONFLICTING KEYWORD keywordFILE spoolid PROCESSING TERMINATEDFILE spool id NOT ACTIVE

FREE EREE resumes file transmission. The hold status for eachof the files queued is not affected. FREE has no effectfor file transmission which was not suspended by a HOLDcommand.

FRee |

Responses:

DMTxxx590I LINK linkid RESUMING FILE TRANSFERDMTxxx591E LINK linkid NOT IN HOLD STATUS

FMig ACE h EWDSPACE causes the file currently being transmitted tobe repositioned forward.

FWdspace I [nnn]

nnn is the number of pages (or punch records) to beforward spaced (if none is specified, a default of1 is assumed). If nnn is greater than the numberof pages (or punch records) remaining to betransmitted, FWDSPACE acts as a FLUSH command.The file must contain page ejects.

Responses:

DMfCYM204EDMTxxx511EDMTxxx600 I

INVALID KEYWORD keywordNO FILE ACTIVE CN LINK linkidFILE spoolid FORWRD SPACED

RSCS COMANDSAl-ril 1985 6-17

HO HO temporarily suspends file transmission without deac-tivating the link. Transmission is suspended when thecurrently active file is completed or, optionally, it maybe suspended immnediately, and later resumed fron thatpoint by a FREE command. The HO command does not affectthe hold status of any file queued for transmission.

HO i [IAED]

IMSED specifies that active file transmission, if any,is to be suspended immediately.

Responses:

DMTxxx2O E INVALID KEYWORD keywordDMTxxx610I LINK linkid TO SUSPEND FILE TRANSMISSICONDMTxxx611I LINK linkid FILE TRANSMISSION SUSPENDEDDMTxxx612E LINK linkid ALREADY IN HOLD STATUS

MSG BMG causes a line of arbitrary text to be presented to auser or operator as a message.

Msg | locid userid [msgtext]

locid is the location identifier of the user ID toreceive the specified text line. Valid loca-tion identifiers are NCARIO and NCARIA.

userid is the virtual machine identifier of a user atthat locid. The user ID for the operator isOP1.

msgtext is an arbitrary string of up to 120 alphamericcharacters composing the message to be sent.

Responses:

DMTCMX310E LOCATICN locid IS NOT DEFINED

RSCS COMMANDS 6-18 Av4r i 198 5

ORIER ORDER causes the output queue to be reordered as speci-fied. The effect of the command is to redefine the orderin which particular files are to be transmitted on thelink when the MULM parameter is in effect. The specifiedfiles are placed at the beginning of the queue in thespecified order, and the file priority attribute is au-tomnatically set to zero (top priority) for each specifiedfile.

ORDer | spoolidl [ spoolid2 ... ]

spoolid specifies the affected file(s), and definesthe new order in which they are to be queued.

Responses:

DMrCMX203E INVALID SPOOL ID spoolidDMICMX204E INVALID KEYWORD keywordDMTAXM523I LINK linkid QUEUE REORDEREDDMTAXM524E FILE spoolid ACTIVE - NO ACTICON TAKENDMTAXM526E FILE spoolid NOT EDUND -- NO ACTION TAKEN

PRGE PURGE causes specified files to be removed frcm the out-put queue. Any file may be purged, regardless of itsstatus, as long as it has not been selected for transmis-sion. All copies of the file are purged.

PURge < ALL >[ spoolidl spoolid2 ... ]

ALL

spoolid

specifies that the entire queue ofto be removed fram the system.specifies the particular file(s)removed franm the system.

files is

to be

DMTCMX203EDMTCMX204EDMTAXM524EDMTAXM526EDMrAXM640I

INVALID SPOOL ID spool idINVALID KEYWORD keywordFILE spoolid ACTIVE -- NO ACTINI TAKENFTILE spoolid NOT FOUND - NO ACTION TAKENnn FILE(S) PURGED ON LINK linkid

ASCS 9COMNDSZ-1Aril 1985 6-19

EY ERY displays linkid, file, or RSCS status information.The linkid does not have to be your own. Information forany linkid can be requested.

linkid Active

linkid Files

linkid Queue

requests information pertaining to the active filedescriptors for the link specified by linkid. Activityinformation includes the VW370 spool file ID, originat-ing VM/370 spool file ID, destination location and userID, spool file class, file transmission priority, numberof file records left to transmit, and total records, ofthe file currently being transmitted. (See the descrip-tions of messages DMTCMX656I and DM2CMX665I which fol-low) .

requests information pertaining to the file status of thelink specified by linkid. File information includes thenumber of files being transmitted, the number of filesbeing received, the number of files accepted and in thequeue, and the number of files pending. (See thedescription of message DMTCMX654I which follows).

requests a list of brief descriptions of each inactivefile queued for transmission, in the current queue order,on the link specified by linkid. Queue information in-cludes the number of files in the queue and the numberwaiting to be entered in the queue. In addition, foreach file currently in the queue, an additional responseis issued containing the spool file identificationnumber, origin location, destination location, destina-tion user ID (if any), spool file class, currenttransmission priority, the number of records in the file,user and operator form names, and the file HOLD status.

April 1985

Query[ Active ]

linkid < Files >[ Queue ][ Sum ]

[ STAT ]File spoolid [ RSCS ]

[ VM ]

SYstem [ Active ][ Links ][ Queue ]

Only one item (a linkid, a file, or the system)may be queried at any one time, and only onekeyword may be specified.

_ __

__ ___

IR~SCS COMMUMSD 6-20

(See the descriptions of messages DMICMX654I andDMlTCMX655I which follow).

linkid Sum

File spoolid STAT

File spoolid RSCS

File spoolid VM

SYstem Active

SYstem Links

SYstem Queue

requests summary information about the transaction anderror counters maintained by the line driver concerningactivity on the camnunications adapter. (See thedescription of message DMTxxxl49I which follows).

requests certain information pertaining to the particularfile specified by the numeric spoolid. Status informa-tion includes activity status and the linkid of the linkon which the file is queued or being transmitted.

requests a description of the RSCS control-related attri-butes and status of the file specified by spoolid. RSCS-related attributes include originating location and userID, originating VM/370 spoolid, date and time of crea-tion, time zone reference for time of day, and the desti-nation location and user ID. (See the descriptions ofmessages DMTCMX662I and DMTCMX664E which follow).

requests a description of the VM/370 spool system-relatedattributes of the file specified by spoolid. VM/370spool-related attributes include transmission priority,spool file class, number of copies requested, HOLDstatus, distribution code, filename and type, user andoperator form names, and dataset name. (See the descrip-tion of message DMrCMX663I which follows).

requests information pertaining only to active links.Active link information includes link identification,link status, line driver type, line address, and holdstatus, drain status, and trace status. (See thedescriptions of message DMTCMX670I which follows).

requests brief descriptions of each link currently de-fined in the system. Inactive link information includeslink identification, activity status, default line drivertype, and default line address. Active link informationincludes link identification, link status, line drivertype, line address, and hold status, drain status, andtrace status. (See the descriptions of messagesDMTCMX670I and DMICMX671I which follow).

requests that message DMTCMX654I be issued for each linkwith a non-zero queued or pending file count. Queue in-formation includes the number of files being transmittedand received, the files accepted and queued, and thefiles pending for each linkid with a non-zero queue.

RSCS COMANDSApril 1985 6-21

Responses:

QUERY linkid ACrIVE:DMrCMX656I FILE spoolid (orgid) locid userid CL FO uuuuuuuu

ffffffff a PR pp LEFT imnrurirrrn OF0 nnnnnnnnDMTCMX665I NO FILE ACTIVE

QUERY linkid FILES:DMrCMX654I LINK linkid S=s R=r Q=q P=p

QUERY linkid QUEUE:DMTCMX654I LINK linkid S=s R=r Q=q P=pDMTCMX655I FILE spoolid (orgid) locid identifier CL FO uuuuuuuu

ffffffff a PR pp REC nnnnnnnn tHOINOH}

QUERY linkid SUM:DMTCMX149I LINK linkid LINE ACTIVITY; TOT=-muMnmi; ERRS=nnnnnnnn;

TMDUTS=pppppppp

QUERY FILE spoolid STAT:DMTCMX660I FILE spoolid INACTIVE CN LINK linkidDMPCMX661I FILE spoolid ACTIVE CN LINK linkidDMTCMX664E FILE spoolid NOT FOUND

QUERY FILE spoolid RSCS:DMTCMX662I FIT. spoolid ORG locidl useridl ORGID orgid

mm/dd/yy hh:nmm:ss z.z.z. TO locid2 userid2DMI'CMX664E FILE spoolid NOT FOUND

QUERY FILE spoolid VM:DMTCMX663I FILE spoolid PR pp CL a FO uuuuuuuu ffffffff CO

[*]nnn {HOINOH} DI distcode, NA {fn ftldsname}DMrCMX664E FILE spoolid NOT FOUND

QUERY SYSTEM ACTIVE:DMTCMX670I LINK linkid CONNECT ACrIVE} - LINE vaddr

{HOINOH} {DRINOD} {NOTITRS TRLITSL}DMTCMX672I NO LINK ACTIVEDMTCMX673I NO LINK DEFINED

QUERY SYSTEM LINKS:DMCMX760I LINK linkid (CONNECTIACTIVE} - LINE vaddr

{HOINOH} {DR NOD} [NOlTnRSTRLI'TSL}DMrCMX761I LINK linkid INACTIVEDMTCMX763I NO LINK DEFINED

RSCS COMMANDS April 19856-22

QUERY SYSTEM QUEUE:DMICMX654I LINK linkid S=s R=r Q=q P=pDMTCMX674I NO FILES QUEUED

QUERY ... (general):DMTCMX202E INVALID LINK linkidDMTCMX203E INVALID SPOOL ID spoolidDMTCMX204E INVALID KEYWORD keywordDMTCMX206E INVALID CPTION keyword

DMTxxxl49I LINK linkid LINE ACTIVITY:ERRS=nnnnnnnn; TMDUTS=pppppppp

TOTf-r=nrmrrmrrn-

Explanation: This meis message is issued in response to aQUERY linkid SUM command.

mrummmmnimi - the total number of successful transactionsthat have taken place on the identified linksince the last similar message was issued, orsince the link was initially activated.

nnnnnnnn - the total number of transactions that haveended in error since the last similar messagewas issued, or since the link was initiallyactivated.

pppppppp - the total number of time-outs that haveoccurred while waiting for response from theremote station since the last similar messagewas issued, or since the link was initiallyactivated.

DMTCMX654I LINK linkid S=s R=r Q=q P=p

Explanation: This message is issued in response to aQUERY linkid QUEUE ccmmand, and is issued in response toa QUERY SYSTEM QU3EUE once for each link on which at leastone file is either queued or active. The status of thefile queue for the link identified by linkid isdescribed.

s - the number of files being actively transmitted (sent)on the link.

r - the number of files being actively received on thelink.

q - the number of files accepted and queued for transmis-sion on the link.

ASCS COOMMNDAy-% i 198 5 6-23

p - the number of files pending but not yet accepted forthe active link.

System Action: In response to a QUERY linkid QUEUE com-mand, an additional message (DMTCMX655I) is issued foreach file accepted and queued on the link, describing thestatus of each such file.

DMTCMX655I FILE spoolid {orgid} locid userid CL a FOSTANDARD STANIARD PR pp REC nnnnnnnn {HOINOH}

Explanation: A message of this form is issued for eachfile accepted and queued for transmission on the linkspecified by linkid in the preceding "QUERY linkid QUEUE"command.

spoolid - the VM/370 spool file ID for the file.

orgid - the originating VM/370 spool file ID (or theorigin job number) of the file.

locid - the destination location ID to which the fileis addressed.

userid - the destination user ID (if any) to which thefile is addressed.

a - the spool file class.

pp - the filers current transmission priority.

nnnnnnnn - the total number of records in the file.

HO - indicates that the file is in hold status.

NOR - indicates that the file is not in holdstatus.

DMTCMX656I FILE spoolid (orgid) locid identifier CL a FOSTANDARD STANDARD PR pp LEFT iiiiraniumu OEr 'nnnnnnn

Explanation: This message is issued in response to aQUERY linkid ACTIVE ccxmmand. The response describes thestate of the file that was being actively transmitted onthe link specified by linkid when the QUERY command wasexecuted.

spoolid - the VM/370 spool file ID for the activefile.

orgid - the originating VM/370 spool file ID (orthe origin job number) of the file.

April 1985FGSCS OO~lm'mimD 6-24

locid - the destination location ID to which thefile is addressed.

identifier - for file returned fran the CRAY-1, eitherthe value in the DIST parameter of theDISPOSE record or, if no DIST parameter,the scientist number fram the JOB record.Otherwise SYSTEM.

a - the spool file class.pp - the file's current transmission priority.rmmmrimniiumm - the number of records in the file which

remain to be transmitted.nnnnnnnn - the total number of records in the file.

DMTCMX662I FILE spoolid ORG locidl useridl ORGID orgidmm/dd/yy hh:mm:ss z.z.z. TO locid2 userid2

Explanation: This message is in response to the RSCS com-mand QUERY FILE spoolid RSCS. The RSCS control-relatedattributes of the file identified by spoolid aredescribed.

locidl - the location ID of the location at which thefile originated.

useridl - the user ID of the originator of the file.orgid - the originating VM/370 spoolid, or the origin

job number, of the file.mm/dd/yy - the file creation date.hh:mm:ss - the file creation time of day.z.z.z. - the time zone with reference to which the

time of day is expressed.locid2 - the destination location ID to which the file

is addressed.userid2 - the destination user ID (if any) to which the

file is addressed.

DMrCMX663I FILE spoolid PR pp CL a ED STANDARD STANDARD 00[*]nnn {HOINOH} DI distcode, NA {fn ftldsname}

Explanation: This message is issued in response to theRSCS crmmand "QUERY FILE spoolid VM". The VM/370 spoolsystem related attributes of the file identified byspoolid are described.

pp -

annnHONOH

distcode -

the file's priority.the file's spool file class.the file's copy count.indicates that the file is in hold status.indicates that the file is not in holdstatus.if the file is a job returned fran the CRAY-1, this is the value of the DIST parameter of

RSCS COMONDSAvpril 1985 6-25

the DISPOSE record or, if no DIST parameterthe scientist number fran the JCB record. Ifthe source is not the CRAY-1, this is thescientist number of the originator.

fn ft - the filers filename filetype.dsname - the file's dataset name.

DMTCMX670I LINK linkid {ONNECTrACrIVE} - type LINE vaddr{HO|NOH} {DR NOD} NOT

Explanation: This message is issued in response to aQUERY SYSTEM command, or to a QUERY SYSTEM ACTIVE com-mand. One such message is produced for each active linkin the RSCS facility at the time of command processing.The active link described by the message is identified bylinkid. The CCNNECT keyword indicates that the linedriver successfully received a satisfactory response fromthe remote station on the last attempted exchange. TheACTIVE keyword implies that the line driver s lastattempted exchange failed due to line or remote systemfailure, or that local telecomaunications equipment hasnot been dialed or is not properly set, or the link hasnot been started at the other end.

type - the name of the line driver in use by the activelink.

vaddr - the virtual device address of the line port inuse by the active link.

HO - indicates that the active link is in hold status.NO. - indicates that the active link is not in hold

status.DR - indicates that the active link is in the process

of draining, and will terminate when there is nomore line activity.

NOD - indicates that the active link is not in the pro-cess of draining.

DMTCMX671I LINK linkid INACTIVE DEFAULT type LINE vaddr

Explanation: This message is issued in response to aQUERY SYSTEM command. One such message is produced foreach inactive link in the RSCS facility at the time ofcommand processing. The inactive link is identified bylinkid; its default line driver type is identified by"type", and its default line port virtual address isidentified by "vaddr".

RSCS ODr-eN; 6-26 April 1985

S'MIR STRT causes an active link to begin transmitting filesof a specified set of classes.

STart | Class cl [ Class c2 ... ]

Class c specifies classes of files which may be processed afterexecution of the command. c can be either *, meaning allfile classes may be processed, or from one to fourclasses (single characters with no intervening blanks).If * is specified, no other classes may be specified. Ifmultiple classes are specified, files are processed inthe order that the classes are specified, and in priorityorder within each particular class. If * is specified,files are processed in priority sequence only.

Responses:

DMrxxx204E INVALID KEYWORD keywordDMTCMY751I LINK linkid ALREADY ACTIVE

-- NEW CLASS (ES)/FORM SET ASREQUESTED

T1B1SEER (Ebr NOCR TRANSFER moves inactive files specified by spoolid framRSS Operator one linkid to another or frcm a linkid to the virtual

Only) reader of a user. You cannot issue this command but canrequest the NCAR operator to do so by telephone or elec-tronic mail.

TRANsfer [ linkidl ] spoolidl [spoolid2 ... ] TO [ linkid2 ][ RSCS ] [ userid ]

linkidl

linkid2

spoolid

userid

is the link identifier of the link frcan whichfiles are to be transferred.

is the link identifier of the link that is toreceive the files.

specifies the particular file (s)transferred fran the specified link.

to be

is used when transfer is to be made to thereader of a virtual machine (used with useridparameter only).

is the user ID of the destination virtualmachine.

ASCS COMNSAl-%ri 1 -198 5 6-27

Note: If the file is to be transferred from a linkid toanother linkid, the operator must preface the TRANSFERcommand with SMSG RSCS. If the file is to be transferedfrcm a linkid to the reader of a virtual machine, theSM3G RSCS prefix is not allowed. To use this facility,you contact the operator and request that this command beissued fram the operator console. Specify the exact textof the cammand when you make the request. For example,the message text to the operator for a linkid-to-linkidmove request would be:

PLEASE ENTER "SMSG RSCS TRANSFER linkidl spoolid TO linkid2"

And, for a linkid-to-virtual machine reader transferrequest, the message would be:

PLEASE ENTER "TRANSFER RSCS spoolid TO userid"

To check that the operator has completed the request, usea QUERY linkid QUEUE comand for the destination linkid.If the requested transfer is to a virtual machine, youmay request a confirmation fran the operator that thecommand was completed.

RSCS COMMNDS April 19856-28

INEEX

Access Policies,Remote, 1-6

Access Procedures (UNINET), 3-3Access Systems,

Features of Remote, 1-5Accessing SIM3278 Through UNINET, 4-7Active,

Linkid, 6-20Active,

SYstem, 6-21Active File, 6-6Any Virtual Machine,

Disposing to, 5-7ASCII Terminals,

Keystroke Definitions For, 4-6BACKSPAC, 6-13CHANGE, 6-13Class c, 6-27'CLOSE (For NCAR RSCS

Operator Only), 6-15CMPR, 5-3Ccnmand Language,

RSCS, 5-2Coamand Language,

RSCS, 6-1Ccnmand Responses, 6-6Caonand Set,

Minimal, 6-1Ccanmand Summary,

RSCS, 6-2Commands,

PAD, 3-15Caomands,

RSCS Standard, 6-13Conmands,

Introduction (RSCS, 6-1Caimands,

NCAR-Added, 6-6Cammunications Between

Two Personal Computers, 4-13Communications Link, .

How to Establish a, 2-1Canmmunications Subsystem,

RSCS: The Remote Spooling, 5-1Computers,

Logging onto the IBM 4341, 2-4Computers,

Caommunications BetweenTwo Personal, 4-13

Computers and Getting It Back,Submitting a Jobto the CRAY-1, 5-5

Computing at NCAR,Remote, 1-1

Connection,Making the, 5-2

Connections,Logical Path, 1-2

Consultation andTroubleshooting Services, 1-8

Control,Flow, 3-7

Control of PAD Functioning, 3-8Conventions,

Notational, 6-4CRAY-1 Computers and

Getting it Back,Submitting a Job to the, 5-5

CRT5, 5-3CRI8, 5-3Definitions and Values,

PAD Parameter, 3-11Definitions For ASCII Terminals,

Keystroke, 4-6Description of Terms, 6-6Dial-up Remote Access,

Hardware/SoftwareRequirements for, 1-4

DIS,Cx, 6-7DIS,HEL, 6-8DIS,NEW, 6-8DISPOSE Record,

Making anError in the, 5-7

Disposing Job Output, 5-6Disposing Metacode

Plot Files, 5-7Disposing to

Any Virtual Machine, 5-7Disposing to the Local NCAR

Printer for Mailing, 5-6Disposing to the Output

Queue of Your Remote Site, 5-(Disposing to

Your Virtual Machine,DIS, SIT, 6-8Downloading,

File Transfers:Uploading and, 4-11

DRAIN, 6-16Driver,

Line, 6-6DRO,RDR, 6-12

5-7

April 1985

6

i Index

Editing,Line, 3-7

Emulation - SIM3278,Full-Screen, 4-1

END, 6-12Enter SIM3278,

How to, 4-5Entry Points,

Telephone, 1-2Error in the DISPOSE Record,

Making an, 5-7Errors,

Problems and, 3-4Establish a Cnmmunications Link,

How to, 2-1Example of PAD Parameter MDdification,

An, 3-10Facilities,

Optimal Remote Use of SCD, 1-6Features),

Introduction (Special, 4-1Features,

Special, 4-1Features of Remote Access Systems, 1-5File,

Active, 6-6File,

Inactive, 6-6File spoolid RSCS, 6-21File spoolid STAT, 6-21File spoolid VM, 6-21File Transfer,

PC-TALK: NCAR to IBM PC, 4-10File Transfer,

Graphics, 4-12File Transfer,

PC-TALK: IBM PC to NCAR, 4-8File Transfers: Uploading and

Downloading, 4-11Files,

Disposing Metacode Plot, 5-7Files,

Linkid, 6-20Files Fran Your Virtual Machine,

Routing, 5-10Files to a Virtual Machine,

Sending, 5-8Flow Control, 3-7FLUSH, 6-16For ASCII Terminals,

Keystroke Definitions, 4-6(For NCAR RSCS Operator Only),

CLOSE, 6-15(For NCAR RSCS Operator Only),

TRANSFER, 6-27

FREE, 6-17Full-Screen Emulation

- SIM3278, 4-1Full-Screen Logon, 2-5Functioning,

Control of PAD, 3-8Future Plans, 1-7FWDSPACE, 6-17Getting Help,

Reporting Problems and, 3-6Graphics and SIM3278, 4-6Graphics File Transfer, 4-12HASP,

SIGON Record for, 5-4HDR, 6-12HDRN, 5-4HDRY, 5-3Help,

Reporting Problemsand Getting, 3-6

HO, 6-18HOL, 6-10How to Enter SIM3278, 4-5How to Establish a

Ccmmunications Link, 2-1IBM 4341 Computers,

Logging onto the, 2-4IBM PC file Transfer,

PC-TALK: NCAR to, 4-10IBM PC Package,

SIMPC/AZPC2 - The, 4-1IBM PC to NCAR File Transfer,

PC-TALK:, 4-8Inactive File, 6-6Information,

Network, 3-6Interrogating RSCS

About Its Status, 5-9Introduction, 1-1Introduction (PACX), 2-1Introduction (RSCS), 5-1Introduction (RSCS Commands),Introduction

(Special Features), 4-1Introduction (UNINET), 3-1Job Output,

Disposing, 5-6Job to the CRAY-1 Computers

and Getting It Back,Submitting a, 5-5

Keystroke Definitions ForASCII Terminals, 4-6

Language,RSCS Canmand, 5-2

April 1985

6-1

Index ii

Language,RSCS Command, 6-1

Line Driver, 6-6Line Editing, 3-7Line Mode Logon, 2-5Line Speeds,

Supported Protocols and, 5-1Link,

How to Establish aCoammunications, 2-1

Link, 6-6Linkid Active, 6-20Linkid Files, 6-20Linkid Queue, 6-20Linkid Sum, 6-21Links,

SYstem, 6-21Local NCAR Printer for Mailing,

Disposing to the, 5-6Logging onto the

IBM 4341 Camputers, 2-4Logical Path Connections, 1-2Logon,

Full-Screen, 2-5Logon,

Line Mode, 2-5Machine,

Routing Files FranomYour Virtual, 5-10

Machine,Disposing to Any Virtual, 5-7

Machine,Disposing to Your Virtual, 5-7

Machine,Sending Files to a Virtual, 5-8

Machine with RSCS,Using a Virtual, 5-9

Mailing,Disposing to the LocalNCAR Printer for, 5-6

Making an Error in theDISPOSE Record, 5-7

Making the Connection, 5-2Message To A Signed-on RSCS Site,

Sending A, 5-10Messages from RSCS,

Sending, 5-8Messages from the Operator,

Receiving, 5-9Metacode Plot Files,

Disposing, 5-7Minimal Command Set, 6-1Mode Logon,

Line, 2-5

Modification,An Example of PAD Parameter, 3-10

More on SIMPC/AZPC2, 4-7MSG, 6-18MUL, 6-11MULM, 5-3NCAR,

Remote Computing at, 1-1NCAR File Transfer,

PC-TALK: IBM PC to, 4-8NCAR Printer for Mailing,

Disposing to the Local, 5-6NCAR RSCS Operator Only),

CLOSE (For, 6-15NCAR RSCS Operator Only),

TRANSFER (For, 6-27NCAR to IBM PC file Transfer,

PC-TALK:, 4-10NCAR-Added Commands, 6-6Network,

The UNINET, 3-1Network Information, 3-6NOHDR, 6-11Notational Convettions, 6-4Note:, 5-8Notes,

Usage, 3-7NOTRA, 6-11Operator,

Receiving Messagesfranom the, 5-9

Operator Only),CLOSE (For NCAR RSCS, 6-15

Operator Only),TRANSFER (For NCAR RSCS, 6-27

Optimal Remote Use ofSCD Facilities, 1-6

Optional- Parameters,SIGNON, 5-3

ORDER, 6-19Output,

Disposing Job, 5-6Output Queue of Your Remote Site,

Disposing to the, 5-6P120, 5-3P132, 5-3Package,

SIMPC/AZPC2 - The IBM PC, 4-1PACX,

The, 1-2(PACX),

Introduction, 2-1PACX System,

The, 2-1PAD Cnmmands, 3-15

April 1985 iii Index

PAD Functioning,Control of, 3-8

PAD Parameter Definitionsand Values, 3-11

PAD Parameter Modification,An Example of, 3-10

Parameter Definitions and Values,PAD, 3-11

Parameter Modification,An Example of PAD, 3-10

Parameters,SIGNON Optional, 5-3

Path Connections,Logical, 1-2

PC file Transfer,PC-TALK: NCAR to IBM, 4-10

PC Package,SIMPC/AZPC2 - The IBM, 4-1

PC to NCAR File Transfer,PC-TALK: IBM, 4-8

PCHN, 5-4PCHY, 5-4PC-TALK, 4-7PC-TALK: IBM PC to NCAR

File Transfer, 4-8PC-TALK: NCAR to IBM PC

File Transfer, 4-10PC-TALK Through UNINET, 4-8Permission to Use RSCS, 5-2Personal Ccmputers,

Canmunications Between Two, 4-13Plans,

Future, 1-7Plot Files,

Disposing Metacode, 5-7Points,

Telephone Entry, 1-2Policies,

Remote Access, 1-6Preliminaries, :3-1Printer for Mailing,

Disposing to the Local NCAR, 5-6Problems and Errors, 3-4Problems 'and Getting Help,

Reporting, 3-6Procedures (UNINET),

Access, 3-3Protocols and Line Speeds,

Supported, 5-1PURGE, 6-19QUERY, 6-20Queue,

Linkid, 6-20Queue,

SYstem, 6-21

Queue of Your Remote Site,Disposing to the Output, 5-6

RDY, 6-10REA, RDR, 6-12Receiving Messages from

the Operator, 5-9Record for HASP,

SIGNON, 5-4Record for UT200,

SIGNON, 5-4Record for 2780/3780,

SIGNON, 5-4Record,

Making an Error inthe DISPOSE, 5-7

Remote Access,Hardware/Sof twareRequirements for Dial-up, 1-4for the Dial-up, 1-4

Remote Access Policies, 1-6Remote Access Systems,

Features of, 1-5Remote Ccmputing at NCAR, 1-1Remote Site,

Disposing to theOutput Queue of Your, 5-6

Remote SpoolingCarmunications Subsystem,RSCS: The, 5-1

Remote Use of SCD Facilities,Optimal, 1-6

Reporting Problemsand Getting Help, 3-6

Requirements forDial-up Remote Access,Hardware/Software, 1-4

Responses,Conmand, 6-6

REWPRI, 6-9Routing Files Fran Your

Virtual Machine, 5-10RSCS, 1-2(RSCS),

Introduction, 5-1RSCS,

Permission to Use, 5-2RSCS,

Signing onto, 5-3RSCS,

Sending Messages frcm, 5-8RSCS,

Using a VirtualMachine with, 5-9

RSCS,File spoolid, 6-21

April 1985ivIndex

RSCS About Its Status,Interrogating, 5-9

RSCS Caomand Language, 5-2RSCS Ccmmand Language, 6-1RSCS Canmand Summary, 6-2(RSCS Canmands),

Introduction, 6-1RSCS Operator Only),

CLOSE (For NCAR, 6-15RSCS Operator Only),

TRANSFER (For NCAR, 6-27RSCS Site,

Sending A Message ToA Signed-on, 5-10

RSCS Standard Canmands, 6-13RSCS: The Remote Spooling

Ccnmunications Subsystem, 5-1SCD Facilities,

Optimal Remote Use of, 1-6Sending A Message To

A Signed-on RSCS Site, 5-10Sending Files to

a Virtual Machine, 5-8Sending Messages fracm RSCS, 5-8Services,

Consultation andTroubleshooting, 1-8

Set,Minimal Cammand, 6-1

Signed-on RSCS Site,Sending A Message To A, 5-10

Signing onto RSCS, 5-3SIGNCN Optional Parameters, 5-3SIGNON Record for HASP, 5-4SIGNON Record for UT200, 5-4SIGNON Record for 2780/3780, 5-4SIM3 278,

Full-Screen Emulation -, 4-1SIM3278,

How to Enter, 4-5SIM3 278,

Graphics and, 4-6SIM3278 Through UNINET,

Accessing, 4-7SIMPC/AZPC2 - The IBM PC Package, 4-1SIMPC/AZPC2,

More cn, 4-7SIN, 6-10SINM, 5-3Site,

Sending A Message ToA Signed-on RSCS, 5-10

Special Features, 4-1(Special Features),

Introduction, 4-1

Speeds,Supported Protocols and Line, 5-1

Spoolid, 6-6Spoolid RSCS,

File, 6-21Spoolid STAT,

File, 6-21Spoolid VM,

File, 6-21Spooling Carmmunications Subsystem,

RSCS: The Remote, 5-1Standard Caicmands,

RSCS, 6-13START, 6-27STAT,

File spoolid, 6-21Status,

Interrogating RSCSAbout Its, 5-9

Subsystem,RSCS: The Remote SpoolingCoarnunications, 5-1

Sum,Linkid, 6-21

Summary,RSCS Cammand, 6-2

Supported Protocolsand Line Speeds, 5-1

System,The PACX, 2-1

SYstem Active, 6-21SYstem Links, 6-21SYstem Queue, 6-21Systems,

Features ofRemote Access, 1-5

Telephone Entry Points, 1-2Terminals,

Keystroke DefinitionsFor ASCII, 4-6

Terms,Description of, 6-6

TRA, 6-11TRA1, 5-4TRA5, 5-4Transfer,

PC-TALK: NCAR toIBM PC file, 4-10

Transfer,Graphics File, 4-12

Transfer,PC-TALK: IBM PCto NCAR File, 4-8

April 1985 v Index

TRANSFER(For NCAR RSCSOperator Only), 6-27

Transfers: Uploadingand Downloading,File, 4-11

Troubleshooting Services,Consultation and, 1-8

TRSN, 5-4TRSY, 5-4Two Personal-Comnputers,

Cammunications Between, 4-13UNINET, 1-2(UNINET),

Introduction, 3-1(UNINET),

Access Procedures, 3-3UNINET,

Accessing SIM3278Through, 4-7

UNINET,PC-TALK Through, 4-8

UNINET Network,The, 3-1

Uploading and Downloading,File Transfers:, 4-11

Usage Notes, 3-7Use of SCD Facilities,

Optimal Remote, 1-6Use RSCS,

Permission to, 5-2Userid, 6-6Using a Virtual Machine

with RSCS, 5-9UT200,

SIGNON Record for, 5-4Values,

PAD ParameterDef initions and, 3-11

Virtual Machine,Routing Files Fran Your, 5-10

Virtual Machine,Disposing to Any, 5-7

Virtual Machine,Disposing to Your, 5-7

Virtual Machine,Sending Files to a, 5-8

Virtual Machine with RSCS,Using a, 5-9

VM,File spoolid, 6-21

YTERM, 4-112780/3780,

SIGNON Record for, 5-4

4341 Canputers,Logging onto the IBM, 2-4

April 1985viIndex

ncar data communications

Documents