Xerox Control Program-Five (CP·V)
Xerox 560 and Sigma 6/7/9 Computers
Remote Processing Reference Manual
90 30 28C
@lXerox Corporation, 1974., 1975
Xerox Control Program-Five (CP-VJ
Xerox 560 and Sigma 6/7/9 Computers
Remote Processing Reference Manual
903026C
December 1975
XEROX
Printed in U.S.A.
NOTICE
This publication documents the 000 version of Control Program-Five (CP-V). The publication is a revision to the B edition of this manual (9030 26A, dated February 1974) and the revision packages 9030 26B-1(9/74) and 90 30 26B-2(4/75). Vertical lines in the outer margin of pages indicated changes that reflect the 000 version of CP-V.
RELATED PUBLICATIONS
Title
Xerox Sigma 6 Computer/Reference Manual Xerox Sigma 7 Computer/Ref~rence Manual Xerox Sigma 9 Computer/Referenc~ Manual Xerox 560 Computer/Reference Manaul
Xerox Control Program-Five (CP-V)/OPS Reference Manual Xerox Control Program-Five (CP-V)/SM Reference Manual Xerox Control Program-Five (CP-V)/SP Reference Manual Xerox Control Program-Five (CP-V)/BP Reference Manual Xerox Control Program-Five (CP-V)/TS Reference Manual Xerox Control Program-Five (CP-V)/TS User's Guide Xerox Control Program-Five (CP-V)/TP Reference Manual Xerox Control Program-Five (CP-V)/Common Index Xerox EASY/LN,OPS Reference Manual
Xerox BASIC/L N, 0 PS Reference Manua I Xerox FLAG/Reference Manual
Xerox Meta-Syrnbol/LN,OPS Reference Manual CP-V Assembly Program/Reference Manual
Xerox Extended FORTRAN IV /LN Reference Manual Xerox Extended FORTRAN IV lOPS Reference Manual Xerox FORTRAN Debug Package (FDP)/Reference Manual Xerox ANS COBOL/LN Reference Manual
Xerox ANS COBOL/OPS Reference Manual Xerox APL/LN, OPS Reference Manual Xerox Manage/Reference Manual Xerox Sort-Merge/Reference Manual
Xerox Functional Mathematical Programming System (FMPS)/Reference Manual Xerox SL-1/Reference Manual
CIRC-AC/Reference Manual and User's Guide CIRC-DC/Reference Manual and User's Guide CIRC- TR/Reference Manual and User's Guide Xerox 1400 Series Simulator/Reference Manual
Publication No.
90 17 13 900950 90 1733 903076 90 1675 90 1674 9031 13 90 1764 900907 90 1692 90 31 12 903080 90 1873 90 1546 90 1654 900952 903000 900956 90 11 43 90 1677 90 1500 90 1501 90 1931 90 16 10 90 11 99 90 : 1,09 90 1676 90 1698 90 1697 90 17 86 90 15 02
Manual Content Codes: BP - batch processing, LN - language, OPS - operations, RP - remote processing, RT - real time, SM - system management, SP - system programming, TP - transaction processing, TS - time-sharing, UT - utilities.
The specifications of the software system described in this publication are subject to change without notice, The availability or performance of some feat
d d 'f' f' . f . ures
may e~en on a spec' IC con Iguratlon 0 equipment such as additional tape units or larger memory. Customers should consult their Xerox sales representative for details.
ii
CONTIENTS
PREFACE v Device Commands 19
Suspend Command 19
COMMAND SYNTAX NOTATION vi RBSUSPEND 19
Restart Commands 19
GLOSSARY vii RBCONTINUE 19
RBREPRINT 19
1. INTRODUCTIOr" RBABORT 20
RBSAVE 20
Definition of CP'-V 1 RBALIGN 20
Remote Processing 1 Other Device Commands 20
Remote Terminals 1 RBLOCK 20
Hardware Connection of Remote Terminals_ 2 RBUNLOCK 20
Workstation - 3 RBFORM 20
Scope of the Manua I 4 RBSIZE 20
RBCTL 20
Changing Forms 21
Entering a Noncontrol Input Fi Ie 21
2. LOCAL AND REMOTE USERS 5 2780 RBT Error Recovery 21
Remote Processing Messages 21
LDEV Command. 5
Using LDEV tiQ Receive Input 8
4.
CENTRAL SITE OPERA TOR 25Using LDEV tiQ Send Output 9
Examples of LDEV Usage 9 5. SYSTEM MANAGER 27
L DEV Processor 10
JOB Command 11 Establishing Remote Processing at SYSGEN _ _ _ 27
The ISCL Processor 12 :DEVICE Command 27
The ISCL Commands 12 :SDEVICE Command 27
Copy a File from a Remote CP-V System_ 13 :MON Command 27
SEND_ 13 :FECP Command 28
Send a Fi Ie to a Remote CP-V System _ _ 13 Defining Workstations 28
SEND _ 13 WORKSTATION Command 29
Delete a File at a RemotEl CP-V System __ 13 Device Selection 33
DELETE 13 Genera I Examples 34
List a File at a Remote CP-V System _ _ _ 13 Defining a Master Computer System as a
LIST 13 Workstation in a Slave CP-V 35
Record Size Restrictions 14 Defining Workstations for CP-V to
Vertical Format Control at Remc)te Printers _ _ 15 CP-V Communication 35
7670 RBT Printers 15 X Command 40
IRBT Printers _ 15 ISCL/RATLER Management 40
2780 RBT Prin'ters 16 ISCL Standing Orders 40
INDEX 59
3. REMOTE OPERA TO R 17
Remote Processin!~ Control Commands 17
APPENDIX'ES
Genera I Commands 17
RBID 17 A. CONNECTING REMOTE SITE AND CENTRAL
RBDISC 17 SITE TELEPHONE LINES 41
RBXXX 17
RBMSG 17 Full-Duplex Configuration 41
RBDEV 17 Ha If-Duplex Configuration 42
RBINFO 18
File Handling Commands _ , 18 B. OPERATION OF IRBTS AND 2780S 43
RBPRIO 18
RBHOLD 18 Preparing for Connection to CP-V 43
RBRETRIEVE 18 Logging onto CP-V 43
RBDELETE . 18 FIN Command 44
RBSTATUS, 19 Interruptions in Phone Connection 44
RBSWITCH 19 Device Control Commands 44
iii
C. OPERATION OF THE XEROX 7670 REMOTE 8. Defini tion of an ISCL/RATLER
BA TC H T ERMI NAL 45 Workstation 40
Prepari ng an RBT for Connection to the A-l. Connecting a Remote Site to the System 41
System 45
Logging On 45 C-l. Xerox 7670 Remote Batch Terminal 46
Enteri ng Job Streams 45
Receiving Punched Output 47 C-2. Xerox 7670 RBT Control Panel 46
Suspending an Output Symbiont 47
Logging Off 47 C-3. Xerox 7670 RBT Maintenance Panel 47
Disconnecting an RBT from the System 47
Handl ing Errors 47 D-l. Typical Multileaving Data Transmission Block_ 50
D. MULTILEAVING 49
TABLES
String Control Byte (SCB) 49
Record Control Byte (RCB) 51 l. LDEV Command Options 5
Subrecord Control Byte (SRCB) 51
Block Control Byte (BCB) 51 2. ISCL Error Messages 14
Function Control Sequence (FCS) 52
3. MAILBOX Messages 15
E. OPERA TING CP-V AS SLAVE IRBT TO IBM
HASP SYSTEM 53 4. Remote Processing Messages 22
SYSGEN Considerations 53 5. ISCL/RATLER Messages to the Remote
SYSGEN Options 53 Operator 24
Defining the Workstation 53
Operating Considerations 53 6. Central Site Operator Key-Ins 25
Logging On 53
System or Line Fai lures 54 7. Central Site Messages 26
F. ERROR LOG RECORD 55 8. General Options of the WORKSTATION
Command 29
FIGURES
9. Device Options of the WORKSTATIONCommand 31
1. CP-V Remote Processing Complex 2
10. Standard IRBT Device Option Values 33
2. CP-V Remote Processing Hardware 3
D-l. Text Control Characters Used In
3. WORKSTATION Command Options 33 Multileaving 49
4. Sample Definition of a Master System as a F-l. Xerox 7670 RBT - RP1, RP3, RP4 __ 55
Workstation in CP-V 36
F-2. Xerox 7670 RBT - RP2 56
5. Definition of Workstation CPV A in
Computer A 37 F-3. IBM 2780 RBT - RPl and RP4 56
6. Definition of Workstation CPVA in F-4. IBM 2780 RBT - RP2 and RP3 57
Computer B 38
F-5. IRBT - RPl and RP4 57
7. Communication Paths between CPVA
and CPVB 39 F-6. IRBT - RP2 and RP3 58
iv
PREFACE
This manual is the principal source of information about the remote processing features of CP-V. All information about remote processing for all computer personnel (remote and local users, system managers, remote site operators, and central site operators) is included in the manual.
Manuals describing other featurEls of CP-V are outl ined below.
• Thd CP-V Time-Sharin!~ Reference Manual, 90 09 07, is the principal source of information for the time- sharing features of CP-V. The purpose of the manual is to define the ru les for using the Terminal Executive
Language and other on··1 i ne processors.
• The CP-V Time-Sharin~~ User's Guide, 90 16 92, d(~scribes how to use the various time-sharing features.
It presents an introductory subset of the features in a format that allows the user to learn the material by using the features at a terminal as he reads through the document.
• The CP-V Batch Proces:sing Reference Manual, 90 1764, is the principal source of reference information for the batch processinfJ features of CP-V (i .e., job control commands, system procedures,
I/o
procedures, program loading and execution, debugging aids, and service processors).• The CP-V System Progrclmming Reference Manual, 90 31 13, describes the CP-V features that are designed to aid the system progrclmmer in the development, maintenance, and modification of the CP-V system.
• The CP-V System Management Reference Manual, 90 16 74, is the principal source of reference information for the system management features of C P-V. It defines the rules for generating a C P-V system (SYSGEN), authorizing users, maintaining user accounting records, maintaining the file system, monitoring system per- formance, and other related functions.
• The C P-V Operations Reference Manual, 90 16 75, is the principal source of reference information for CP-V computer operators. It defines the rules for operator communication (i .e., key-ins and messages), system stclrt-up and initialization, job and system control, peripheral device handling, recovery and file preservation.
• The C P-V Transaction Arocessing Reference Manual, 90 31 12, provides information about dynamically mod- ifying and querying a c,entral database in a transaction processing environment. The manual is addressed to system managers, database administrators, applications programmers, and computer operators.
• The C P-V Common Index, 90 30 80, is an index to all of the above C P-V ma"nuals.
Information for the language and application processors that ()perate under C P-V is also described in separate man- uals. These manuals are listed 011 the Related Publications page of this manual.
v
vi
COMMAND SYNTAX NOTATION
Notation conventions used in command specifications and examples throughout this manual are listed below.
Notation lowercase letters
CAPITAL LETTERS
[]
{ }
Numbers and special characters
Subscripts
Superscripts
Underscore
Description
Lowercase letters identify an element that must be replaced·with a user- selected value.
CRndd could be entered as CRA03.
Capital letters must be entered as shown for input, and will be printed as shown in output.
DPndd means "enter DP followed by the values for ndd".
An element inside brackets is optional. Several elements placed one under the other inside a pair of brackets means that the user may select anyone or none of those elements.
[KEYM] means the term II KEYM II may be entered.
Elements placed one under the other inside a pair of braces identify a re- quired choice.
{~}
means that either the letter A or the value of id must be entered.The horizontal ell ipsis indicates that a previous bracketed element may be repeated, or that elements have been omitted.
name [,name]. .. means that one or more name values may be entered, with a comma inserted between each name value.
The vertical ell ipsis indicates that commands or instructions have been omitted.
MASK2 DATA,2 X1l EFI BYT E DA T A,3 BA( L( 59))
means that there are one or more statements omitted between the two DATA directives.
Numbers that appear on the line (i .e., not subscripts), special symbols, and punctuation marks other than dotted I ines, brackets, braces, and under! ines appear as shown in output messages and must be entered as shown when input.
(value) means that the proper value must be entered enclosed in parentheses; e. g., (234).
Subscripts indicate a first, second, etc., representation of a parameter that has a different value for each occurrence.
sysid 1 ,sysid2,sysid3 means that three successive va lues for sysid should be entered, separated by commas.
Superscripts indicate shift keys to be used in combination with terminal keys.
c is control shift, and s is case shift.
L cs means press the control and case shift (CONTROL and SHIFT) and the L key.
All terminal output is underscored; terminal input is not.
lRUN means that the exclamation point was sent to the terminal, but RU N was typed by the terminal user.
These symbols indicate that an ESC (0), carriage return (@), or line feed (@) character has been sent.
lEDIT @means that, after typing EDIT, a carriage return character has been sent.
GLOSSARY
butch job a job that is submitted to the batch job stream through the central site card relClder, through an on-line terrninal (using the Batch processor), or through a re- mote terminal.
ghosl· job a job that is neither a batch nor an on-line program. It is initiated and 109ged on by the monitor, the operator, or another job and consists of a single job step. When the ghost progrram ex its, the ghost is logged off.
held fi Ie an output fi Ie ready for transmission to a remote site but not being transmitted because either the desti- nation remote sae is not logged on or the remote site operator has specifically requested "held"status. Files that are to be output on local devices cannot be held.
Message fi les (see below) are never held.
job stream a set of input records consi sti ng of one or more jobs and/or remote control commands and end- ing with a FIN control commond. A FIN command by itself is not a job stream <Jnd is ignored. The FIN command is. not used if the stream is input from an IRBT; instead, its equivalent is entered automati- cally by the IRBT.
logical device stream an informCition stream that may be used when performing input from or output to a symbiont device. At SYSGEN,up to 15 logical device streams are defined. Eoch logical device stream is given a name (e.g., L1, P1, C1), each is assigned to a default physical device, ond each is given default attributes.
The user may perform
I/o
through a logi cal devi ce stream wi th the default physi cal devi ce and attributes or he may change the physi cal devi ce and/or attributes to satisfy the requirements of hi"s job.message fi I e a symbiont pri nt fi I e containing informa- tion for a remote site identified by a given workstation name. It includes all remote control commands trans- mitted by the remote operator, error messages, operator messages, etc. A message file is transmitted to the remote site at lo!~-on, upon receipt of a job stream, in reply to operator commands, and when the central site operator directs 0 message to the workstation.
on·-line job a sessiion at an on-line terminal that begins with the log-on cmd ends with j'he log-off.
protocol a set of control codes, data forrr ts, Clnd ';ton- dardi zed response procedures that r"gu lal c th( tran';- mission of data between two communicatinq sy..,tcms in a predetermined manner.
remote control command (RBCC) a system coni 1"01 com- mand that is unique to the remote processing system.
remote site the locati on of a remote terminal.
remote user any user utilizingCP-V viathe remote pro- cessing system.
short block control character (EM) a special character for cards that allows shorter images to be punched and read by a Xerox 7670 Remote Batch Term i na I, thus i n- creasing throughput. The EM character appears as an 11-9-8-1 punch in the first column after the last non- b lank column of a card. All columns after an EM character are ignored by the remote batch terminal.
The user may supply EM characters on input decks.
The remote processing system automatically suppl ie:.
EM characters for 7670 output decks unless the user specifies that EM characters are not to be punched.
Cards with EM characters cannot be used as input at the central site.
suspended file a remote site symbiont output file for which output in progress was interrupted (but not aborted) by manual intervention by the remote site operator to allow the input of a job stream N by the RBSUSPEND command.
symbiont a monitor routine that transfers information be- tween di sk storage and a peri pheral devi ce independent of and concurrent with job processing.
symbiont retry point a point within an output symbiont file that is currently being output. The point dy- namically changes and is always several pages behind that whi ch is currently being output. If the current output point is within three pages of the beginning of the output file, the symbiont retry point is the be- ginning of the file.
sysid a unique number used to identi fy a job submitted to the CP-V system. It is assigned sequentially at job input time.
vii
1. INTRODUCTION
DEANITION OF (:P-V
Control Program-Five (CP-V) is a c:omprehensive operating system designed for use with Xerox 560 and Sigma 6/7/9 computers together with a wide variety of peripheral de- vices. The CP-V system provides for five concurrent modes of operation.
•
Time-sharing•
Batch processin~}•
Real-time processing•
Remote processing•
Transaction processingThe time-sharing and batch modes ,are complementary, yet compatible, modes elf operation thut provide the user with fi Ie management and program compi lation, execution, and debugging services. CP-V time-sharing allows up to
128 terminal lines tOI be connected to the central computer at one time. The CP-V multibatch system is designed to maximize uti lizationl of the system's resources whi Ie pre- venting conflicts in resource use. Batch jobs may be sub- mitted to the batch job stream thro.ugh the central site card reader, from an on-line terminal, or from a remote site via the remote processinH system.
Real-time processin~, involves reacting to external events (including clock pulses) within microseconds. Selected external events are ell lowed to interrupt the real-time user's program so that they can be processed at the ti me they occur. After an i nt1errupt has been processed, control may then return to the interrupted program or may be di rected elsewhere. Real-time facilities are available t'o both the on-line and batch u~;er (and also tel a ghost user), provided the user has a sufficiient privilege level.
The transaction proc4~ssing feature of C P-V is an efficient and economical approach to centralized information pro- cessing and is a gene!ralized packa!~e that is designed to meet the requiremenh of a variety of business applications.
Transaction processing faci lities provide an envi ronment in which several users at remote terminals may enter business transactions, simultaneously utilizing a common database.
The transactions are processed imm~~diately, as they are re- ceived, by application programs written especially for the particular installation.
REMOTE PROCESSING
The purpose of the remote processing system is to provide for flexible communication between C P-V and a variety of remote terminals. Remote terminals can range from a simple card reader and line printer combination to another large-sca Ie computer system wi th an assortment of peri phera I
devi ces. Important features of the remote processi ng system include
• Support of a wide variety of peripherals at the remote site. Through monitor and user interfaces, virtually any type of device (e.g., tape, disk, plotter) may be accessed wi th remote processi ng.
• Computer-to-computer communication. A remote site may be another large-scale computer, and fi les of data may be transferred between user programs at the centra I and remote computers.
• Slave/master status. A C P-V system may act as the central site to some remote terminals and as a remote terminal to other computers, simultaneously. This fea- ture encourages the construction of communications networks.
• Complete user interface. Any user (batch, on-line, ghost) of a C P-V system can communicate with any number of devices atone or several remote sites. When data is being sent by a user program to a remote si te, the remote site need not be connected since C P-V automatically buffers on RAD or disk for deferred transmission.
• Processing of jobs from remote sites at the central site.
Jobs are sent from the remote site to the central site, are processed there, and may direct output to the orig- inating remote site, a central site device, or another re- mote site as specified by the remote site user.
• Dynamic definition of remote stations. Remote stations can be added, deleted, or modified during system op- eration. The definition of remote stations is not SYSGEN-dependent.
Basically, CP-Vremote processing is a machine-to-machine communi cation mechanism that allows output fi les for pseudo devices called streams to be combined into transmission blocks and transmitted over communications lines. Blocks received over these lines are deblocked into symbiont input fi les for logi ca I device streams (or rea I devi ces) at the centra I or remote si te.
REMOTE TERMINALS
Two basic types of remote terminals are supported by CP-V:
Remote Batch Terminals (RBTs) and Intelligent Remote Termi na Is (I RBTs).
An RBT is a card reader, card punch, and line printer com- bination whi ch is used primari Iy to allow batch processi ng I/O functions to be performed at remote sites. That is, a job is input to the system from the remote site card reader, the job is processed at the central site, and the output is sent to the remote site line printer or card punch. The out- put may optionally be directed to the central site or to an- other remote site. The Xerox 7670 RBT or any computer that exactly emulates it (Univac DCT 2000 compatible) is supported by CP-V. Operation of the 7670 is described in Appendix C.
Introduction
The IBM 2780 RBTor :1780 RBT, or any computer that exactly emulates them, is sut'ported by CP-V given the following factors:
• EBCDIC transmis!don code.
• Nontransparent I ine protocol.
• Single record blocks or multirecord blocks of 400 bytes for 2780 RBTs and 512 bytes for 3780 RBTs.
• Support for multidrop I ines is not provided.
An IRBT can be eithm a mini-computer system for which the primary function is to control the operation of peripheral equipment (e. g., COPE 1200) or another large-scale com- puter system (e. g., another CP-V system). Any computer system that supports the IBM HAS P Multileaving protocol t may act as an IRBT to CP-V.
The remote processing system is designed so that the CP-V system may act as the central site to a set of remote ter- minal while simultaneously acting as a remote terminal to one or more other systems. A system that is acting as the central site is referred to as the "master" system and a sys- tem that is acting as a remote terminal is referred to as a IIslavell system.
To the CP-V system, the role of master and slave manifests itself only at log-on time. After the data-set to data-set communication path is established, the slave logs onto the master. (The master cannot log onto the slave.) Once the
log-on is complete, th~ communication path between the
tThis and all other reference to "HASplI and "Multi leaving"
in this document refer to the HASP Multileaving protocol as described i~ HASP Version 2.3 program documentation and not to the IBM HAS P operati ng system, except where IBM HASP is specifically noted.
IBM 2780
master and slave is symmetrical - simply streams of data flowing in both directions over the communication path.
When is is intended that the CP-V system act as a slave terminal on a particular line, the uperator must use the RBLOG key-in (described in Chapter 4) to establish the workstation name of the master on that line since the master does not identify itself to the slave.
F, ur fundamental modes of remote processing are
1. A CP-V master system connected to one or more slave Xerox 7670 and/or IBM 2780 RBTs. . 2. A CP-V master system connected to one or more slave
mini-computer IRBTs.
3. A CP-V system communicating with another CP-V system.
4. A CP-V system acting as a slave IRBT connected to another computer system acting as the master computer.
These four modes may be combined to provide a large va- riety of communications networks. An example of such a network is given in Figure 1. (The arrows point to the RBTs and slave IRBTs.)
HARDWARE CONNECTION OF REMOTE TERMINALS A remote terminal is connected to the central site over a communication line that is either a hardwired line or a switched line.
If the connection is over a hardwired line, the remote site must be physically near the central site.
CP-V
Other large- sca I e computer system.
Figure 1. CP-V Remote Processing Complex
2 Remote Processing
If the connection is by switched line, two data sets (modems) are required. The data sets provid4~ interfaces between the line and the remote terminal and between the line and a data set controller (described below) at the central site.
The data sets convert device signals to telephone tones and telephone tones to d,evice signals. Connecting the remote site to the central site with a telephone line and data sets is described in Appendix A.
All remote terminals require a date] set controller (DSC) for interface with the central site. A virtually unlimited number of RBTs and IRBTs may be c:onnected to the com- puter via a particular DSC, but on:ly one may be connected at a time. Therefore the maximum number of remote sites that may be connected concurrent Iy is determined, not by the number of remote terminals, but by the number of DSCs at the central site. CP-V supports up to 30 DSCs of the following types:
Xerox 7601, which may be used only with a Xerox 7670 RBT.
Xerox 7605, which may be used with any RBT or IRBT.
Options that may be added to either of the above DSCs are Xerox 7602, which provides full-duplex operations.
Xerox 7604, which provides for local connection.
Figure 2 depicts the relationship between the central site, remote sites, data sets, and data set controllers.
WORKSTATION
A workstation ~S) is a collection of information that defines both the identity and hardware characteristics of a remote site at a particular time. A workstation may represent a particular remote site, a particular group of users at one remote site, or a group of users utilizing several different remote sites. The definition of a workstation specifies items su ch as
• Name of the workstation.
• Type of terminal to be used (RBT or IRBT).
CP-]
[
7605 DSCData Set
IRBTOI~
Peripheral
I
Devic:es
MIOP 7605
DSC
Data Set
IRBT or RBT
Peripheral Devices Figure 2. CP-V Remote Processing Hardware
Remote Processing 3
• Whether or not jobs to be run in the :SYS account may be submitted from the workstation.
• Maximum priority for jobs submitted from the workstation.
• Whether the workstation wi II be a slave computer or the master computer (if the type is IRBT).
• Remote peripheral devices to be associated as part of the workstation (if it is an IRBT).
• Attributes of devices defined for the workstation.
Each workstation is given a one- to eight-alphanumeri c character workstation name (WSN). Local devices at a CP-V system have the workstation name LOCAL.
A workstation is not, as the name might imply, limited to one physical location. A user may log on as a given work- station at any remote site that has the appropriate hardware characteristics. Each remote site may have several work- stations defined for it, but only one workstation may be active on a gi ven line at a given time. If the remote site has more than one line (which could only be true if it were a large-scale computer), then more than one workstation may be logged on currently from that site.
Workstations may be defined dynamically any time during system operati on usi ng the system management processor Super. The attributes of workstations may alsobe changed and workstations may be deleted using Super during system operation.
4 Scope of the Manua I
SCOPE OF THE MANUAL
This manual is the central source of information about the remote processing system. It describes a II externa I aspects of remote processing and contains sections for system users, system operators, and system managers. The remaining chapters in the manual are
Chapter 2 - Remote and Loca I Users Chapter 3 - Remote Operator Chapter 4 - Central Site Operator Chapter 5 - System Manager
In each chapter, the information required by the personnel type indicated by the chapter title is documented. How- ever, there is some overlap. Specifically,
• Many remote users will find Chapter 3 helpful.
• CP-V operators at CP-V systems that are acting as slave remote termina Is shou Id read both Chapters 3 and 4.
• The system manager will find useful information in all of the chapters. .
Much of the material in this manual is repeated in other CP-V manuals. Cf particular importance, all of the infor~
mation for the C ;-Itra I site operator is repeated in the CP-V/OP5 Reference Manual, 90 1675.
2. LOCAL AN[J REMOTE USERS
This chapter discusses remote processing from the point of view of both central site and rEtmote site users. When the remote site is another CP-V system, the ISCL processor fa- cil itates manipulation of CP-V managed fil es for both local and remote users. The ISCL proc:essor is described I ater in th is chapter.
Two commands, LDEV and JOB, are the other primary methods that local and remote users can use t'o take advant- age of remote processing capabil ities.
These are the two CP-V commclnds that have options that allow a user at one site to direct a file to another site. The LDEV command aillows users to direct any file of informa- tion almost anywhere within thE! reaches of remote pro- cessing - to a symbiont device a~ the central site or to any device at a specific remote works,tation. The JOB command, with a more limitEtd application~o remote processing, pro- vides a means of directing the print and punch ou'tput of the job to a specified workstation or to the central site.
Before discussing t'hese commands, it is important to note that the remote user may subm it jobs to the central site that make full use of the LDEV and JOB command remote pro- cessing features provided that tne central site is a CP-V system. Because ()f the on-I ine/batch compatibil ity of CP-V, the operations described in this chapter may be used by both on-I ine and batch users. In cases where the master computer is a system other than C:P-V, the remote user must be famil iar with the remote procossing commands and capa- bil ities of the particular master system.
At the conclusion of this chapt1er, two other topics of interest to local and remote users are discussed.
1. Record size restrictions.
2. Vertical format control for rlemote devices.
LDEV COMMAND
A logical device stream is an information stream which may be attached to any symbiont device that the user specifies.
(Symbiont devices include devices such as the I ine printer, card reader, card punch, and plotter at the central site and all devices at remote workstations.) At SYSGEN, up to 15 logical device streams may be defined. Each is given a name (e.g., Cl, L 1, Pl), each is assigned to a default phys- ical device, and attributes are defined for the physical de- vice. Three logical device streams - C 1, L 1, and Pl - are always defined and are given default attributes at SYSGEN.
The user may perform I/O through a logical device stream with the default physical device and attributes or he may change the physical device assignment and/or attributes to satisfy the requirements of h is job. He makes any necessary changes through use of the LDEV command. The informa- tion about the logical device stream is stored in a coopera- tive context block, providing for central ized information about the physical device even though I/O to that device may arise through more than one DCB within a job.
The LDEV command is available in both the on-I ine and batch modes. The format of the command is
LDEV stream-id[, (option)] ...
where
stream-id specifies the two-character name of the stream to be referenced. Th is must be the name of one of the logical device streams defined during S YS GE N (e. g ., C 1, L 1, P 1 ).
options are as defined in Table 1. The options may appear in any order.
Table 1. LDEV Command Options Option
AINIT
AREL
-
Description
Specifies that the atl'ributes for the stream are to be initialized with the attributes DEV command and that system defau Its are to be suppl ied specified on this L
wherever an attrib a previous LDEV c ASAVE, and AREL
utE! is not specified. Any attributes specified for the stream on ommand are to be ignored. AINIT is the default for the AINIT,
options.
Specifies that the s ystem table containing the attributes of this stream (which may e result of previous LDEV commands) is to be released and that ot,to be reinitialized. Any other options specified (except have been set as th
the attributes are n
DELETE) in this co mmand will be ignored.
Loca I and Remote Users 5
Table 1. LDEV Command Options (cont.)
---O-p-t-io-n---.--D-e-s-c-ri-p-t-io-n---·---.. --·---~I
ASAVE
CONCURR
COPIES,value
COUNT,tab
DELETE
DEV,type
DRC
FFORM,name
FORM,name
Specifies that the current attributes for the stream are to be changed only by options explicitly specified on this LDEV command. Other LDEV-specifiable attributes (which may have been set as the result of previous LDEV commands) are not to be changed.
Places the symbiont output stream in concurrent output mode, a mode in which out- put is broken into groups ~"chunks") and released to the symbiont stream for output.
Once this stream has been selected by the symbiont for printing or punching, then the particular device is held until all output produced by the job has been processed, except as otherwise directed by an operator key-in. If CONCURR is not the only option specified, then already prepared outp~ will be packaged for printing in its entirety and a newl y bannered stream will be created for subsequent output. The COPIES option may not be specified when CONCURR is specified.
Specifies the number of times the file is to be processed to produce multiple copies.
The range of values that may be specified is 1-255. The default value is 1.
Specifies that page counting is to be done and specifies the column in which the most significant digit of the page count is to be listed. The value of "tab" must be appropriate for the particular physical device. (Note that if COUNT is speci- fied for the LO device and a TITLE control command is also specified, the page count wi II be superimposed on the title line.) The default is no page counting.
Specifies that if output currently exists for this stream but has not yet been dis- patched for processing, it is to be deleted. (If such a stream exists and DELETE is not specified, the output forthe stream isdispatched for processing.) Ifinputis cur- rently being accessed through this stream, any part of the stream that has not been read wi II automatically be deleted whether or not DELETE is specified.
Specifies the device type, where type is the two-character mnemonic of the device to be associated with the stream. Valid mnemonics are resource mnemonics either of the central site or of a remote workstation. Central site mnemonics are those defined for symbiont devices during SYSGEN (e.g., CR, LP). Remote mnemonics are those specified when defining a workstation with Super (e.g., OC, CR).
Requests that monitor logical record formatting implied by the DEV option not be performed. Any record formatting necessary wi II be suppli ed by the user. If DRC is not specified, the monitor will perform logical record formatting.
Specifies the future form name (as below, with FORM)of the form to be used when the form change procedure (M:DEVICE(FORM/FNAME)) is specified in the program for the stream. When M:DEVICE(FORM/FNAME)) is encountered, the stream will be dispatched for processing and restarted with 'name' as the stream form. The de- fault is none.
Specifies the one- to four-character name of an installation-determined paper form or card stock and is used in outputscheduling for the device. Thedefault is to have no special scheduling (i.e., the operator wi II determine whi ch form to use). If used on input, name specifies the one- to four-character name of a noncontrol input fi Ie.
(FORM and NAME may be used interchangeably. )
1 - - - + - - - _ . _ - - - -_ _ --I
FPC, name
JDE, value
6 LDEV Command
Specifies the one- to four-character name of an installation-determined form over- lay and is used in output scheduling for the Xerox 1200 or a similar device. The default is to have no special scheduling (i.e., the operator will determine which overlay to use if any).
Specifies the direction of the stream. The defau It is OUT.
Specifies the job descriptor entry to be used in output scheduling for the device.
The value must be in the range 0-89 and specifies an installation defined procedure describing printer setup attributes (e.g., ._V_F_C __ ta~pe--')'--. _ _ _ _ _ _ _ _ _ _ _ _ _ _ ....J
Option LINES,value
NAME,name
NOVFC OUT
sEaL
id]S PACE,value[, top]
SRCB
{VFC } NOVFC
Table 1. LDEV Command Options (cont.) Description
Specifies the number of printable lines per logical page. A maximum of 32,767 lines per page may be specified. The default is determined at SYSGEN.
Specifies the one- 1'0 four-character name of a noncontrol input file (see below,
II Noncontrol Input FlIes"). If used on output, name specifies the one- to four- character name of an in"tallation-determined paper form or card stock and is used in output schedul ing for the device. (NAME and FORM may be used interchangeably. ) See VFC below.
See IN above.
Specifies that punchE~d output is to have decimal sequencing in columns 72-80. If a user-defined id is specified, it will be punched in columns 73-76 of each card.
Sequencing begins with 0000.
Specifies the spacing between lines (value) and between the top of each page and the first line printed (top). A value of 1 indicates that lines are to be single spaced.
The greatest value that may be specified for value and top is 15.
Applies to remote pmcessing and is only valid when the WSN option is specified.
It specifies that the lJIser will supply a device-dependent control byte as the first byte of each record if this is an output stream, or that he wishes to receive it as the first byte of records if the stream is input. The following conditions appl y:
For remote devices for which the SRCB option of the WORKSTATION command W(lS set to U, the SRCB option of the LDEV command must be specified.
2 The LDEV SRCB option may not be specified for remote input devices unless the SRCB option of the WORKSTATION command was set to U.
3 The LDEV SIRCB option is legal for any output device.
Specifies whether or not vertical format control characters are to be used. (These two options are only ~egal for I ine printers.) VFC requests that a default vertical format control character be added to all records. NOVFC requests that the format character be stripped from the record if present. The default is VFC.
Specifies the workstal'ion name of the remote device that is to receive the stream, where name can be from one to eight alphanumeric characters. The default is local output. If a dollar sign ($) is specified, the name of the workstation on the JOB command (if onel is specified) effectively replaces the dollar sign. If no workstation name was specified on the JOB command or if no JOB command was used, the name of the workstation from which the job was submitted effectively replaces the dollar si~~n. (The dollar sign option allows a job to be run from more than one workstation without necessitating respecification of the workstation name on the LDEV command.)
_ - L -_ _ ,
LDEV Command 7
Examples:
1. The following command requests association of stream L 1 with the local I ine printer named LP and specifies that I ines per page is to be 60. All other attributes are to be suppl ied by default.
! LDEV L 1,(DEV,LP),(LINES,60)
2. The following command requests association of stream L5 with the I ine printer named LL at remote workstation LAX. All other cttributes are to be suppl ied by default.
! LDEV L5,(DEV,LL),(WS N,LAX)
If an LDEV command specifies DEV=LP or CP and no WSN, the stream is LDEVed to the system I isting or system punch device respectively (if it exists) at the workstation of ori- gin. The workstation of origin is the one from wh ich the job was subm itted or one on the JOB command wh ich overrides it. If the appropriate device is not present, the output is sent to the LOCAL device.
For example:
!JOB X, Y, 7, WSN1
! LDEV L2, (DEV, LP) is identical to:
IJOB X, Y,7
! LDEV L2, (DEV, L P), (WS N, WS N 1 )
USING LDEV TO RECEIVE INPUT
The LDEV command can be used to receive input transmitted via remote processing only if the receiving site is a CP-V system {either master or slave}.
Two types of input devices may be defined for IRBTs and the central site:
1. CTL devices - control devices from which system control commands such as the JOB command or remote control commands may be transmitted. (The card reader at an IRBT is usually a CTL device.)
2. NCTL devices - noncontrol devices from which files of data may be transmitted; i. e., files from NCTL de- vices are not scanned for system control commands (except EOD and FIN).
8 LDEV Command
Input from CTL devices is always scanned (unless otherwise requested) by the receiving operating system for system con- trol commands which tell the system what is to be done with the input (e.g., run it as a job).
When input is from an NCTL device, a user job at the re- ceiving site may access the input via the LDEV command.
Jobs are not allowed to access input that was sent from a CTL device unl ess that input was preceded by the command
! ! NCTL [name]
where name specifies the one- to four-character name of the noncontrol input stream.
The! ! NCTL command specifies that the input that immedi- ately follows is to be treated as though it had arrived from an NCTL device - it is not to be scanned for system control commands. This feature provides, among other things, a means of transmitting jobs that are to be run ata later time.
It is important to note that jobs at the receiving site can never access the actual physical input device at the sending site. They can only access the input from the device once it has arrived. The input is not restricted to being received by a job submitted by a user at the receiving site. For ex- ample, a us~r at a remote site may submit a job to the cen- tral site for tne specific purpose of reading a noncontrol file from a device at the same remote site.
To read a file that has been input via remote processing, the user assigns one of the logical device streams to the device and the WS N of the fi I e and then reads that stream. For example, the command
! LDEV C2,(WS N,ST A6),(DEV,CR)
assigns logical device stream C2 to the first available coop- erative input file from device CR at workstation STA6. The file may then be read by a series of commands such as
!PCLt
COpy C2 TO FILE END
provided that either CR is a noncontrol device or that the file was preceded by a !! NCTL command.
t The Peripheral Conversion Language (PCL) is described in the CP-V
IBP
Reference Manual, 90 17 64, and in the CP-VI
TS Reference Manual, 90 09 07.
In this example, the input wi II be copied to a standard CP-V consecutive fi Ie called FIl.E. Cooperative input fi les are deleted as they are read, so it is good practice to copy them to standard fi les befor1e accessing the data.
The above example obtains the first available (first to enter the system) cooperative fi Ie that has no name from the de- vice to which C2 i's assigned. To access a particu lor named cooperative input file, the lDEV command could be mod- ified as fol lows:
! lDEV C2,(WSN,STA6),(DEV,CR),(IN),(NAME,ABCD) This command connects cooperative stream C2 to the input cooperative file frc)m workstation STA6 and device CR with the name ABCD.
The lDEV command can be used t'o receive input sent by a central site to a slC:lVe CP-V IRBT because the central site (llways has a workstation name defined for it for use by jobs at the slave CP-V. (Actually, the central site is defined
CIS a workstation by' the slave CP-V through use of the Super processor. )
The SRCB option of the lDEV command is useful for devices with nonstandard rE~cord control properties. SRCB may be specified if, and only if, it was specified at the time the workstation was defined, that the user's program would be prepared to receive the control byte at the beginning of each record transmitted by this dE!vice as the first charac- ter of the data. The user's program may, for example, contain special routines to process the nonstandard control bytes.
I
USING LDEV TO SEN .. OUTPUT
Output to a device may be sent from a CP-V system to a remote site using the lDEV commcmd. The receiving site may be any type of remote proces:§ing terminal. A user may send remote processing output to CI device at a site regard-
less of whether the site is currently connected. If the site is not connected, the output is queued and is sent when the site becomes connected.
To send output to another site, a logical device stream must be di rected to an c:>utput device at the other site. For example,
IlDEV ll,(WSN,BBB),(DEV,LP)
The above command directs logiccd device stream L1 to device lP at the site with workstation name BBB. The file that is to be output may then be written to logical device stream 11 with commands such as
IPCl
COpy FILE TO L 1 END
This example assum~~s that the output resides in the fi Ie called FILE.
The logical file will not actually be queued for output until one of the following occurs:
1. The job exits.
2. The user issues a !PRINT command (available only to on-line users).
3. The logical device stream" is modified using the lDEV command. Actually, the user may issue another LDEV command for whi ch the sole purpose is to di spatch the cooperative file for output. The simplest such com- mand would be
! lDEV L1
which retums the logical device stream II to the de- fault attributes defined at SYSGEN, thereby redefining the attributes of II and dispatching the current coop- erati ve fi I e for output.
All of the standard LDEVoptions may be used when assigning output to a remote device if they are legal for the particu lar device. For example, if the following lDEV command is used
I LDEV 11 ,(WSN,BBB),(DEV,lP),(FORM, WXYZ) this cooperative file will not be output until the form WXYZ is mounted on the device lP at workstation BBB.
The SRCB option on the LDEV command shou Id only be used when the fil e to be output conta ins user-supp lied contro I bytes at the beginning of each record. User-suppl ied control bytes are appropriate only when the programmer wishes to supply control bytes that are different from those supplied by CP-V.
EXAMPLES OF LDEV USAGE
In these examples, Rl is used as the logical device stream name on the lDEV command.
1. Writing to a device:
Assume that a workstation named USA has been defined with a printer named lP. To assign Rl to this device, the LDEV command is
! lDEV Rl ,(WSN,USA),(DEV, lP)
If the user wishes to run a program called WOWIE, which prints through M:Ll, he might, for example, issue the following commands:
!ASSIGN M:Ll,(DEVICE,Rl)
!RUN (LMN,WOWIE) or
lSET M:LL Rl
8
lSTART WOWIE8 IPRINT@)
(batch)
(on-line)
The printed output from WOWIE would be sent to the printer lP at workstation USA.
LDEV Command 9
2. Submitting a job from a CP-V system acting asa slave IRBT:
Assume that a CP-V system is slave to another operating system that uses the HASP Mu Iti leaving protocol. The master system is known in the slave CP-V system as workstation narne MASTER and its card reader is known as device JE (br "job entry"). If a job to be run at the master system has been stored in a file called JOBFIlE at the slave sy~tem, the job can be submitted to the master system with the following commands:
! lDEV R1 ,(WS N,MASTER),(DEV,JE)
!PCl
COpy JOBFIlE TO R1 END
Note: The file is not actually read by the card reader JE. However, it is transmitted via remote processing as though it had been read by such a card reader.
The fi Ie in JOBFI lE should contain job control language that is appropriate for the master system so that the job can be executed correctly.
Another set of commands that can be used to submit a job from a CP-V IRBT to a master system is I isted below.
This set of commands can only be used if the job to be input resides 011 cards, the master system is not a CP-V system, and no command within the job being submitted contains a ! in the first column. The entire set of com- mands must be submitted from the card reader at the CP-V IRBT.
! JOB SUBMIT,REMOTE,7
! LIMIT (CORE,8),(TIME,2)
! lDEV R1 ,(WS N,MASTER),(DEV,JE)
!PCl
COpy CR TO R1
IlpROG
JOB (28741,SMK=CC),JOHN.SMITH,II
MSGlEVEl = 1II
EXEC PGM =PLlCOMPIISYSPRINT DD SYSOUT =A
IlcOMPOUT
DD UNIT = SYSDA,II
DISP = (NEW,PASS), SPACE = (80,250) IISYSIN DD*
1*
lEaD lEaD END
[source statements]
3. Passing fi les between CP-V systems:
'vVhen two CP-V systems are connected together it is possible to pass unstructured data between users at the two sites. Such files are limited to a maximum of 140 bytes per record (a symbiont restriction) and no struc- ture is maintained for keyed files. Therefore, if the user wishes to maintain a keyed structure or if records
10 lDEV Command
longer than 140 bytes exist, the file must be processed by a user-written program to prepare it for transm ission.
In the example below, the file COMFIlE is assumed to be a consecutive file with recc·rds that do not exceed 140 bytes in length.
Assume that there are two CP-V systems, A and B. (It is not important which is the master and which is the slave.) B is defined in A as workstation CPVB and has a device named FO (for "fi les out"). A is defined in B as workstation CPVA and has a device named FI (for
"fi les in ") which matches the FO device.
Note: FI and FO probably are not actual physical de- vices. They are more likely to be pseudo devices for wh i ch attributes were defi ned when worksta- tion CPVA was defined in B and when worksta- tion CPVB was defined in A. The only important factor is that the two devices, whether pseudo or actual, have matching attributes.
If a user in A wishes to pass the file COMFIlE to a user in B, he might use the following commands:
! lDEV R1,(WSN,CPVB),(DEV,FO),(NAME,XXX)
!PCl
COpy COMFIlE TO R1 END
XXX is the name that the file carries while it is being passed from one machi ne to the other. It is not requ ired but allows the user in B to access the file by name.
After the two machines have been connected and the fi Ie transm i tted between them, a user in B can copy the fi Ie to his own version of COMFIlE (or to any fi Ie) as follows:
! lDEV R1 ,(WSN,CPVA),(DEV,FI),( NAME,XXX)
!PCl
COpy R1 TO COMFIlE END
The transfer of the fi Ie is now complete.
LDEV PROCESSOR
The lDEV command is available to all on-line and batch users. An M:lDEV program procedure that is almost identical to the lDEV command ex ists; however, it can only be used for remote processing purposes (i
.e.,
to assign logical de- vice streams to remote devices) by shared processors. (The M:lDEV procedure is described in the CP-V/BP Reference Manual, 90 17 64.) The following discussion is for those users who wish to assign logical device streams to remote devices within the program rather than by use of the lDEV control command.Any program that has been loaded with the load processor may call the lDEV processor through use of the M:L1NK
procedure. The LDEV processor can then be used to perform the following:
1. Assign a logical device stream to a remote device.
2. Assign a form name to the stream if desired.
3. Spec ify whE~ther or not thEl user wi" supply record contro I bytE~s.
The user who wishes to use this facility should follow the steps outlined below ..
1. Obtain a common page. This may be done using the M:GCP procedure.
M:GCP
(This should be f'he only common page currently owned by the program.)
2. Store the following FPT into the first seven words of the page obtained. (The M:GCP procedure returns the start address of I'he page in register 9.)
o
31Error wOlrd
0 0
1
Stream idWSN - -
0 01
DeviceSRCB Form name
where
Error word may be set to any va lue by the user.
If the LDEV is successful, this field will be set to zero on return from the link. If it is set to any other va lue, an error occurred.
Stream id specifies, in text format, the name of one of the SYSGEN-defined logical device streams (e.g., Ll, PI).
WSN specifies the workstation name in text format, left- justified and blank fj lied.
Device specifies one of the devices defined for the workstation in te;<t format.
SRCB specifies, if set to zero, that the system should supply record control bytes. If non- zero, it specifies thclt the user will supply record control bytes.
Form name specifies the form name for the stream. The form name may be one to four characters in text format, left-justified and blank fi lied. If the field is set to zero, no form name wi II be associated with the stream.
3. Link to the LDEV processor by using the M:LINK procedure.
M:LINK 'LDEV',':SYS '
LDEVwill return to the instruction following the M:LINK procedure using the M: LDTRC procedure. If the first word of the FPT is zero, the LDEV was successfu I. If an error occurred, the first word of the FPT will be non- zero and LDEVwill printan error message through M:LL.
Example:
The following Meta-Symbol code assigns logical device stream Ll to device LP at workstation ST AnON. The sys- tem is to supply record control bytes and the standard form is to be used.
M:GCP GET COMMON PAGE
BCS ,8 NOPAGE NONE AVA ILABLE
STW,9 SAVEPAGE SAVE ADDRESS
LI,l 6
LW,2 FPT,l MOVE FPT
STW,2 *SAVEPAGE,l
BDR,l $ -2
M:LINK I LDEV I , I : SYS I CALL LDEV
LW,9 ~'<SAVEPAGE SUCCESS?
BNEZ ERROR
FPT EQU $-1 SKIP ERROR WORD
DATA C ' L11 ZEROS AND STREAM ID TEXT I STATTON I WORKSTATION NAME
DATA C'LP' ZEROS AND DEVICE
DATA 0,0 NO SRCB,NO FORM NAME
JOB COMMAND
The JOB command is described in complete detail in the CP-V/BP Reference Manual, 90 17 64. Only that por- tion of the command that applies to remote processing, the wsn option, is described here. The format of the JOB command is
JOB account,name[(ext. acctg.)] [, priority] [,wsn ] where wsn may specify either a workstation name or the term LOCAL which specifies lithe site at which the job is run". Although the effect of the wsn field on the JOB command is rather complex, the general effect is simple:
the job IS print and punch output is directed to the named workstation.
JO B Command 11
If a workstation name is specified and is valid, the following steps are taken:
1. If a system I isting device is defined for the specified workstation, logical cooperative stream L1 is assigned to that device. In effect, it is exactly as though the user had issued the command
! LDEV L 1,(WSN,wsn),(DEV,xx)
where wsn specified the workstation name that is on the JOB command and xx specified the name assigned to the system list i ng dev i ce •
The user may change the device assignment for L 1 within his job using LDEVand thereby nullify the effect of the wsn on the JOB command for print output.
If a system listing device is not defined for the work- station, L 1 maintclins its default assignment that was determ ined at SYSGEN unless the assignment is ex- plicitly changed within the job by the LDEV command.
For RBTs, the printer is automatically designated as the system iisting device. For IRBTs, a listing device may be selected to be the system listing device when the workstation is defined using Super.
2. If a system punch device is defined for the specified workstation, logical cooperative stream Pl is assigned to that device. In effect, it is exactly as though the user had issued the command
! LDEV Pl,(WSN,wsn),(DEV,xx)
where wsn specified the workstation name that is on the JOB command and xx specified the name assigned to the system punch device.
The user may change the device assignment for Pl with in his job using LDEV and thereby nullify the effect of the wsn on the JOB command for punch output.
If a system punch device is not defined for the worksta- tion, PI maintains its default assignment that was de- termined at SYSGEN unless the assignment is explicitly changed within the job by the LDEV command.
For RBTs, the punch is automatically designated as the system punch device. For IRBTs, a punch device may be selected to be the system punch device when the workstation is defined using Super.
If the term LOCAL is specified in the wsn field of the JOB command, the job's origin is ignored and L land Pl maintain their default assignments established at SYSGEN unless they are explicitly changed within the job using
LDEV.
If a workstation name is specified but is not valid, the diagnostic output is sent to the submitting site and the job is aborted.
12 The ISCL Processor
If there is no wsn specified on the JOB command and the job originated at the central site, Ll and Pl maintain their default assignments established at SYSGEN unless they are expl icitly changed within the job using LDEV.
If there is no wsn specification on the JOB command and the job originated at a remote site, then print and punch output are to be returned to the originating remote site and, in effect, it is exactly as though the user had specified his
0\' n wsn on the JOB command.
THE ISCL PROCESSOR
The ISCL processor provides the on-I ine or batch user with the ability to copy, create, list, or delete files in another CP-V system via an IRBT connection. The processor inter- prets the user ISCL command and packages it for transmission to the remote CP-V system, where the action is performed asynchronously. Notification of completion of service (or cause of failure if a failure occurs) and return of informa- tion requested occurs in the user MAILBOX file through messages placed there by RA TLER, a system ghost job. When the user requests that a local file be sent to a remote fil e, the local portion of the service is performed immediately by the ISCL processor. When the file is built in the remote CP-V system, a message indicating addition of a file to the remote account is placed in the MAILBOX file of the re- mote account.
To use the ISCL processor, the user must be authorized at the remote site as well as the local site. The ISCL processor is call ed v ia the command:
!ISCL
User requests may be of the following types:
• Copy a file from a file at a remote CP-V system.
• Send a file to a file at a remote CP-V system.
• Delete a file at a remote CP-V system.
• List file(s} which are at a remote CP-V system.
ISCL COMMANDS
ISCL commands have the following general structure:
commond-verb Hd-I ist [{~€EJ fid-I is]
The command-verbs are described below. Some of the com- mands allow the preposition specification, but it is never requ ired. The general format of a fid-I ist is:
fid [, fid] .•. [@W~n ]
