\setu~
\setb@
\seth^
\folio=CONTROL DATA PRIVATE
\blank
\skip15
\center,b=SCFS/VE
\center=Protocol Specification
\center=January 25, 1991
\page1
\autosec
\tablcon
\title1=Status and Control Facility Server PS
\block,j1,i4
\ n.0 PREFACE
 This protocol specification documents the I/O processing required of the Status
and Control Facility Server on NOS/VE. SCFS/VE runs as part of the C180 host
software portion of the batch device support service.
SCFS/VE
also provides status and control services for Network Transfer Facility
(NTF) remote systems and associated batch streams.
The protocol specification
provides a specification for the work request messages received/transmitted
by SCFS/VE, the protocol required to control work request/reply messages,
as well as the necessary information needed to establish a connection with
SCFS/VE.
\ n.n notes
\item,j1,n.
 . The conventions below are followed for names used as parameters on the work
request messages:

\+flowtab;1,3

 ;-;~I/O^Station^Name~:^^The name of an I/O station.

 ;-;~Directly^Connected^Remote^System^Name~:^^The name of a remote system
directly connected to a Device Interface.

 ;-;~Accessible^Remote^System^Name~:^^The name of a remote system which is
accessible via a directly connected remote system.

 ;-;~Remote^System^Name~:^^The name of a directly connected or accessible remote
system.

 ;-;~Station^Name~:^^The name of an I/O station, a directly connected or
accessible remote system

 ;-;~Stream^Name~:^^The name of a batch stream associated with a remote
system.

 ;-;~Device^Name~:^^The name of a device associated with an I/O station or
the name of a batch stream associated with a remote system.
\-

 . Future plans will support expansion of the user identity to three
parameters (community, family, user). The full design of the community facility
is not complete, and this feature will not be implemented in the first
release of batch device support. As a result of this no community parameters
have been included in this document. Once the community facility specifications
are completed this document will be updated to include the required
parameters.
\ n.n references
\item,j1,N.
 . CDCNET Batch Device Support DAP (ARH6250)
 . NOS/VE Batch Device Support DDD
 . CDCNET Status and Control Facility/DI ERS
 . CDCNET Terminal Support ERS (ARH6408)
 . CDCNET Standalone Printer Support DAP (SVL5134)
 . Network Transfer Facility (NTF) DAP (ARH7454)
\block,j1,i4
\ n.0 WORK REQUEST MESSAGE DESCRIPTIONS
\ n.n Messages between SCFS/VE and SCF/DI
\ n.n.n.n BTFS/DI Status
 This message is received from SCF/DI to inform SCFS that the BTFS/DI service
is available and the network address or title (or both) used to access that
service.  The use of "advanced features" may also be conveyed.  The status
message is normally sent after a new connection is established between SCFS and
SCF/DI.  The status message may also be used to inform SCFS that the service
has failed (status "down").

\+block
 Message received from SCF/DI

 Required parameter

\+item
 - Status Code
\-

 Optional Parameters

\+
 - BTFS/DI Network Address
 - BTFS/DI Title
 - BTFS/DI Advanced Features
\--
\ n.n.n.n Add I/O Station
 Request to define a new I/O station under control of this SCFS/VE copy. The I/O
station name supplied is checked against all current I/O station definitions.
The I/O station name supplied is also checked against
existing remote system names.  If the I/O station name supplied does not
currently exist,
the definition is done, if the name already
exists a test is done on the "check I/O station unique" parameter. If
this parameter is TRUE the definition is rejected. If this parameter
is FALSE the definition is accepted if an existing definition is found
identical and the current definition also has "check I/O station unique"
set to FALSE.

\+
 Message received from SCF/DI

 Required parameters

\+item
 - I/O Station Name
 - Station Usage
 - File Acknowledgement
 - Check I/O Station Unique
 - Auto Operator Control
 - Default Job Destination
 - Destination Unavailable Action
 - PM Message Action
\-

 Optional Parameters

\+
 - I/O station Alias 1
 - I/O station Alias 2
 - I/O station Alias 3
 - Required Operator Device Name
\--
\ n.n.n.n Add I/O Station Response
 Response message to SCF/DI giving the result of the definition.

\+
 Message sent to SCF/DI

 Required parameters

\+
 - I/O Station Name
 - Response Code
\--
\ n.n.n.n Add Remote System
 Request to define a new remote system under control of this SCFS/VE
copy.  The remote system name supplied is checked against all current
remote system and I/O station definitions.  If the new remote system
name does not currently exist, the definition is accepted.  If the
remote system name already exists and the new logical line number
matches an existing logical line number, the new definition is
rejected.  If the remote system name already exists and the existing
definition is identical to the new definition (except for Logical Line
Number, Line Speed, Line Name and Terminal User Procedure) the new
definition is accepted.  If the remote system name already exists and
the existing definition is not identical to the new definition, the new
definition is rejected.

\+
 Message received from SCF/DI

 Required parameters

\+item
 - Directly Connected Remote System Name
 - Remote System Protocol
 - Authority Level
 - Logical Line Number
 - Line Speed
 - Line Name
 - Terminal User Procedure
 - Wait-a-bit
 - Inactivity Timer
 - Positive Acknowledge
 - Default Job Destination
 - Default File Destination
 - Store and Forward Destination
 - Remote System Type
 - Route Back Position
 - Request Permission Retry
 - Local System Name
\--
\ n.n.n.n Add Accessible Remote System
 Request to define a new accessible remote system under control of this
SCFS/VE copy.  The accessible remote system name supplied is checked
against all current remote system (directly connected and accessible)
and I/O station definitions.  If the new accessible remote system name
does not currently exist, the definition is accepted.  If the new
accessible remote system name does not currently exist for the
specified directly connected remote system, the definition is accepted.
If the accessible remote system name is already defined for the
specified directly connected remote system and the Authority Level
specified is identical to the existing definition, the new definition
is accepted.  If the accessible remote system name is already defined
for the specified directly connected remote system and the Authority
Level specified is not identical to the existing definition, the new
definition is rejected.

\+
 Message received from SCF/DI

 Required parameters

\+item
 - Directly Connected Remote System Name
 - Logical Line number
 - Accessible Remote System Name
 - Authority Level of Accessible Remote System
 - Accessible Remote System Type
 - Route Back Position
\--
\ n.n.n.n Add Remote System Response
 Response message to SCF/DI giving the result of the Add Remote System
definition.

\+
 Message sent to SCF/DI

 Required parameters

\+
 - Directly Connected Remote System Name
 - Logical Line Number
 - Response Code
\--
\ n.n.n.n Add Accessible Remote System Response
 Response message to SCF/DI giving the result of the Add Accessible Remote
System definition.

\+
 Message sent to SCF/DI

 Required parameters

\+
 - Directly Connected Remote System Name
 - Logical Line Number
 - Accessible Remote System Name
 - Response Code
\--
\ n.n.n.n Delete I/O Station
 Request to delete access to the I/O station for the specified SCF/DI
connection.  Any batch devices defined for the requesting DI, that are
defined for the I/O station are deleted.  When all SCF/DI connections
are deleted the complete I/O station is deleted.

\+
 Message received from SCF/DI

 Required parameters

\+
 - I/O Station Name
\--
\ n.n.n.n Delete I/O Station Response
 Response message to SCF/DI giving the result of the deletion.

\+
 Message sent to SCF/DI

 Required parameters

\+
 - I/O Station Name
 - Response Code
\--
\ n.n.n.n Delete Remote System
 Request to delete access to the remote system for the
specified SCF/DI connection.  Any batch streams associated with the remote
system for this DI connection are deleted.  When all SCF/DI connections
are deleted the complete remote system is deleted.
If accessible remote systems can only be reached via the deleted directly
connected remote system, then those accessible remote systems are also deleted.

\+
 Message received from SCF/DI

 Required parameters

\+item
 - Directly Connected Remote System Name
 - Logical Line Number
\--
\ n.n.n.n Delete Remote System Response
 Response message to SCF/DI giving the result of the deletion.

\+
 Message sent to SCF/DI

 Required parameters

\+item
 - Directly Connected Remote System Name
 - Response Code
 - Logical Line Number
\--
\ n.n.n.n Start I/O Station
 Inform SCF/DI that an operator has now been assigned to this I/O station.
This message is sent for all I/O stations but is required to activate
the batch devices for I/O stations which have the "check I/O station
unique" attribute set to TRUE.

\+
 Message sent to SCF/DI

 Required parameters

\+
 - I/O Station Name
 - User Identity (user and family names)
\--
\ n.n.n.n Stop I/O Station
 Inform SCF/DI that the operator for this station is no longer assigned.
This message is sent for all I/O stations but causes the batch devices
to be deactivated at the end of the current file if the "check I/O
station unique" attribute  is set to TRUE.

\+
 Message sent to SCF/DI

 Required parameters

\+
 - I/O Station Name
\--
\ n.n.n.n Switch Control
 Command to cause SCF/DI to delete an I/O station or remote system from one
control facility SCFS and to re-establish the I/O station and the
associated devices or remote system and the associated batch streams to
another control facility.
\+

 Message sent to SCF/DI

 Required parameters

\+
 - Station Name
 - Control Facility
\--
\ n.n.n.n Add Batch Device
 Request to define a new batch device within an existing I/O station.
The device name must be unique within the I/O station.
 This message is also used for a request to define a new batch stream
within an existing remote system.  The batch stream name must be unique within
the remote system.

\+
 Message received from SCF/DI

 Required parameters

\+
 - Station Name
 - Device Name
 - Device Status
 - File Transfer Status
 - Device Type
 - Tip Type
 - File Acknowledgement
 - Transmission Block Size
 - Maximum File Size
 - Page Width
 - Page Length (ignored at NOSVE R1.2.2)
 - Banner Page Count
 - Banner Highlight Field
 - Carriage Control Action
 - Forms Code 1
 - External Device Characteristics 1
 - Suppress Carriage Control
 - Code Set
 - Vertical Print Density
 - Forms Size
 - Undefined Format Effector Action
 - Unsupported Format Effector Action
 - Maximum Page Length
 - Control Code Replacement
 - Data Parity
\-

 Required parameter for NTF

\+
 - Logical Line Number
 - Transparent Mode
\-

 Optional Parameters

\+
 - Device Alias (1 - 3)
 - Terminal Model
 - Forms Code (2 -4)
 - External Device Characteristics (2 -4)
 - VFU Load Procedure
 - VFU Load Option
 - Site-defined Code Set
\-

 Optional Parameter for NTF

\+
 - Skip Punch Count
\--
\ n.n.n.n Add Batch Device Response
 Response message to SCF/DI giving the result of the definition.

\+
 Message sent to SCF/DI

 Required parameters

\+
 - Station Name
 - Device Name
 - Response Code
\--
\ n.n.n.n Delete Batch Device
 Request to delete the definition of an existing batch device within an
existing I/O station.
 This message is also used for a request to delete the definition of an
existing batch stream within an existing remote system.

\+
 Message received from SCF/DI

 Required parameters

\+
 - Station Name
 - Device Name
\--
\ n.n.n.n Delete Batch Device Response
 Response message to SCF/DI giving the result of the deletion.

\+
 Message sent to SCF/DI

 Required parameters

\+
 - Station Name
 - Device Name
 - Response Code
\--
\ n.n.n.n Batch Device Status
 This message is received from SCF/DI whenever the status of a batch device
or batch stream changes.

\+
 Message received from SCF/DI

 Required parameters

\+
 - Station Name
 - Device Name
 - Device Status
 - File Transfer Status
\--
\ n.n.n.n File Status
 This message is received from SCF/DI when a status change occurs in
the "file transfer status" (e.g. start and end of file transfer) at
a batch device or batch stream.

\+
 Message received from SCF/DI

 Required parameters

\+
 - Station Name
 - Device Name
 - Device Status
 - File Transfer Status

\-
 Required for input files.

\+
 - User Job Name
 - Actual Destination

\-
 Optional for input files

\+
\nojust
 - Requested Destination (if different from actual destination)
 - System Job Name       (if file transfer complete)
 - Input Bytes Transferred
\just

\-
 Required for output files.

\+
 - System File Name
 - System Identifier (family)
 - User File Name
 - File Position
\--
\ n.n.n.n Terminate Transfer
 Command to terminate the transfer of a job/file from/to a batch device or
batch stream.  The batch device or batch stream remains active for the
transfer of subsequent jobs/files.  The only permissible file disposition
option for an input device or receive type batch stream is DROP.  The
allowable file disposition options for an output device or transmit type
batch stream are:^REQUEUE, DROP, and HOLD.

\+
 Message sent to SCF/DI

 Required parameters

\+
 - Station Name
 - Device Name
 - File Disposition (REQUEUE/DROP/HOLD)
\--
\ n.n.n.n Terminate Transfer Response
 Response to the Terminate Transfer command above.

\+
 Message from SCF/DI

 Required parameters

\+
 - Station Name
 - Device Name
 - Response Code
\--
\ n.n.n.n Stop Batch Device
 Command to take a batch device or batch stream out of service.  The device
or batch stream is removed from service immediately for file dispositions
= SUSPEND, REQUEUE, DROP or HOLD and is removed from service at the end of
the current job/file for file disposition = FINISH.

\+
 Message sent to SCF/DI

 Required parameters

\+
 - Station Name
 - Device Name
 - File Disposition (REQUEUE/DROP/HOLD/FINISH/SUSPEND)
\--
\ n.n.n.n Stop Batch Device Response
 Response to the Stop Batch Device Command above.

\+
 Message from SCF/DI

 Required parameters

\+
 - Station Name
 - Device Name
 - Response Code
\--
\ n.n.n.n Start Batch Device
 Command to make a batch device or batch stream available for file transfer
following a Stop Batch Device Command.  A suspended, file being sent to an
I/O station, will restart at it's suspended position (unless
re-positioned) when the device was stopped.  A suspended file, being sent
to a remote system will restart from the beginning.

\+
 Message sent to SCF/DI

 Required parameters

\+
 - Station Name
 - Device Name
\--
\ n.n.n.n Start Batch Device Response
 Response to the Start Batch Device command above.

\+
 Message from SCF/DI

 Required parameters

\+
 - Station Name
 - Device Name
 - Response Code
\--
\ n.n.n.n Suppress Carriage Control
 Command to suppress carriage control or remove suppress carriage
control for a specific batch output device.

\+
 Message sent to SCF/DI

 Required parameters

\+
 - I/O Station Name
 - Device Name
 - Suppress Format Control
\--
\ n.n.n.n Suppress Carriage Control Response
 Response message to Suppress Carriage Control command above.

\+
 Message from SCF/DI

 Required parameters

\+
 - I/O Station Name
 - Device Name
 - Response Code
\--
\ n.n.n.n Change Batch Device Attributes
 Command to change the attributes defined for a specific batch device or batch
stream.  This message is generated in response to a
change_batch_device_attributes I/O station operator command or
change_batch_stream_attributes NTF operator command.

\+
 Message sent to SCF/DI

 Required parameters

\+
 - Station Name
 - Device Name
\-

 Optional parameters

\+
 - Device Alias 1
 - Device Alias 2
 - Device Alias 3
 - File Acknowledgement
 - Terminal Model
 - Transmission Block Size
 - Maximum File Size
 - Page Width
 - Page Length (ignored at NOSVE R1.2.2 and later systems)
 - Banner Page Count
 - Banner Highlight Field
 - Carriage Control Action
 - Forms Code (1 - 4)
 - External Device Characteristics (1 - 4)
 - Code Set
 - Vertical Print Density
 - VFU Load Procedure
 - Forms Size
 - Undefined Format Effector Action
 - Unsupported Format Effector Action
 - Skip Punch Count
 - Control Code Replacement
 - Data Parity
 - Site-defined Code Set
\--
\ n.n.n.n Change Batch Device Attributes Response
 Response message to the Change Batch Device Attributes command above.

\+
 Message from SCF/DI

 Required parameters

\+
 - Station Name
 - Device Name
 - Response Code
\-

 Optional parameters

\+
 - Device Alias 1
 - Device Alias 2
 - Device Alias 3
 - Terminal Model
 - File Acknowledgement
 - Transmission Block Size
 - Maximum File Size
 - Page Width
 - Page Length (ignored at NOSVE R1.2.2)
 - Banner Page Count
 - Banner Highlight Field
 - Carriage Control Action
 - Forms Code (1 - 4)
 - External Device Characteristics (1 - 4)
 - Code Set
 - Vertical Print Density
 - VFU Load Procedure
 - Forms Size
 - Undefined Format Effector Action
 - Unsupported Format Effector Action
 - Invalid Attribute (parameter # with validation error)
 - Skip Punch Count
 - Control Code Replacement
 - Data Parity
 - Site-defined Code Set
\--
\ n.n.n.n Position File Transfer
 Request to re-position an output file transfer that is currently active on
an output device. The request is sent in response to a position file
operator command. The information is forwarded to SCF/DI for processing
and the device is suspended.  The request is forwarded to BTF/VE, via BTFS/DI,
for processing.
\+

 Message sent to SCF/DI

 Required parameters

\+
 - I/O Station Name
 - Device Name
 - Parameters passed to BTF/VE as received
\--
\ n.n.n.n Position File Transfer Response
 Response to the Position File Transfer command above.

\+
 Message from SCF/DI

 Required parameters

\+
 - I/O Station Name
 - Device Name
 - Response Code
\--
\ n.n.n.n Operator Message
 Request to send a message to the I/O station
operator. This message is expected to originate in a print file "PM"
entry, upon detection of an error condition or to contain preview data for
file positioning.

\+
 Message received from SCF/DI

 Required parameters

\+
 - I/O Station Name
 - Device Name
 - text
\--
\ n.n.n.n Send Remote Command
 Request to transmit a command or message to a remote system.

\+
 Message sent to SCF/DI

 Required parameters

\+item
 - Remote System Name
 - Stream Name
 - Logical Line Number
 - Command Type (Command, Message, Signon, Signoff, TDP)
 - Command Text
\--
\ n.n.n.n Send Remote Command Response
 Response to the Send Remote Command command above.

\+
 Message received from SCF/DI

 Required parameters

\+item
 - Remote System Name
 - Stream Name
 - Command Type
 - Signon Status
 - Response Code
\--
\page
\ n.n Messages between SCFS/VE and SCF/VE or SCFS/VE and NTF/VE
 The following commands are exchanged between SCFS/VE and SCF/VE to assign
output files to batch devices.  These commands are also exchanged between
SCFS/VE and NTF/VE to assign transmit files to batch streams.
\ n.n.n.n Add File Availability
 Request to add a file entry in the transmit file
scheduling queue(s).

\+
 Message received from SCF/VE or NTF/VE

 Required parameters

\+
 - Station Name (public ios or NTF)
 - User Identity (user name + family name) (private ios)
 - Station Usage
 - System File Name
 - System Job Name
 - User File Name
 - User Job Name
 - User Name
 - User Family
 - Copies
 - Device Name
 - Device Type
 - External Device Characteristics
 - File Size
 - Forms Code
 - Output Data Mode
 - Output Initial Priority
 - Output Maximum Priority
 - Output Priority Factor
 - Output State
\-

 Required if print file

\+
 - Page Format
 - Page Length
 - Page Width
 - Vertical Print Density
 - VFU Load Procedure
\--
\ n.n.n.n Modify File Availability
 Request to modify a file entry in the transmit file
scheduling queue(s).

\+
 Message received from SCF/VE or NTF/VE

 Required parameters

\+
 - Station Name (public ios or NTF)
 - User Identity (user name + family name) (private ios)
 - Station Usage
 - System File Name
 - System Job Name
 - User File Name
 - User Job Name
\-

 Optional parameters

\+
 - Copies
 - Device Name
 - External Device Characteristics
 - Forms Code
 - Output Initial Priority
 - VFU Load Procedure
 - Vertical Print Density
\--
\page
\ n.n.n.n Delete File Availability
 Request to delete a file entry in the transmit file
scheduling queue(s).

\+
 Message received from SCF/VE or NTF/VE

 Required parameters

\+
 - Station Name (public ios or NTF)
 - User Identity (user name + family name) (private ios)
 - Station Usage
 - System File Name
 - System Job Name
 - User File Name
 - User Job Name
 - File Requeued
\-

 Optional parameters

\+
 - File held by output filter (SCF/VE only)
\--
\ n.n.n.n File Assignment
 This message is sent to SCF/VE or NTF/VE upon assignment of a transmit file to
an output device or batch stream.

\+
 Message sent to SCF/VE  or NTF/VE

 Required parameters

\+
 - Station Name
 - Device Name
 - Device Type
 - System File Name
 - Requested Destination Name
 - Requested Device Name
 - Operator Name
 - Operator Family
 - Station Usage
 - Copies
 - External Characteristics
 - Forms Code
 - Output Initial Priority
 - VFU Load Procedure
 - Vertical Print Density
\-

 Required parameters for SCF (Device Attributes)

\+

 - Banner highlight field
 - Banner page count
 - Carriage control support
 - Code set
 - File acknowledgement
 - Forms size
 - Maximum file size
 - Page width
 - Tip type
 - Transmission block size
 - Undefined FE action
 - Unsupported FE action
 - Vertical print density
 - VFU load option
\-

 Optional parameters for SCF (Device Attributes supplied if non-blank)

\+
 - Device alias 1
 - Device alias 2
 - Device alias 3
 - External characteristics 1
 - External characteristics 2
 - External characteristics 3
 - External characteristics 4
 - Forms code 1
 - Forms code 2
 - Forms code 3
 - Forms code 4
 - Terminal model
 - VFU load procedure
\-

 Optional parameters

\+
 - BTFS/DI Network Address **
 - BTFS/DI Title **

 ** One and only one of these parameters must appear
\-

 Required parameters for NTF

\+
 - Remote System Protocol
 - Remote System Type
 - Route Back Position
\--
\ n.n.n.n File Assignment Response
 This message is sent in response to the File Assignment message. If the
message is rejected by SCF/VE or NTF/VE, then SCFS/VE should remove the file
assignment and attempt to assign a different file to the batch device or
batch stream.

\+
 Message received from SCF/VE or NTF/VE

 Required parameters

\+
 - Station Name
 - Device Name
 - System File Name
 - Response Code
\--
\ n.n.n.n Delete Destination
 This message is sent to SCF/VE by SCFS/VE when an I/O station or alias has been
deleted from the control facility.  SCF/VE should wait for the destination to
return before sending file availability messages to the control facility.

\+
 Message received from SCFS/VE

 Required parameters

\+
 - Destination Name
 - Control Facility Name
\--
\ n.n.n.n BTF/VE Status
 This message is sent to SCFS/VE by SCF/VE or NTF/VE to convey the protocol
stacks supported by the NOS/VE system where the BTF/VE resides.  This message
is normally sent before any File Availability messages.

\+
 Message received from SCF/VE or NTF/VE

 Required parameter

\+
 - BTF/VE Protocol Stacks
\--
\ n.n.n.n Terminate Queued Output
 Request to delete a file from the station's output queue before it gets
transferred.

\+
 Message sent by OPERATE_STATION utility to SCFS and by SCFS/VE to SCF/VE

 Required Parameters

\+
 - I/O Station Name
 - System File Name or User File Name
\--
\ n.n.n.n Terminate Queued Output Response
 Response to Terminate Queued Output command above.

\+
 Message sent by SCF/VE to SCFS/VE and by SCFS to OPERATE_STATION utility

 Required Parameters

\+
 - I/O Station Name
 - System File Name or User File Name
 - Response Code (Status of file termination)
\--
\page
\ n.n Messages between SCFS/VE and operator utilities
 The following commands may be exchanged between SCFS/VE and the OPERATE_STATION
utility (OPES) or between SCFS/VE and the OPERATE_NTF utility (OPENTF).
\ n.n.n.n Add User
 Request to register a new user as an I/O station operator. For the first
parameter, if the I/O station is a private dynamic station then the control
facility name is used, otherwise the I/O station name is used.
 This message is also used by OPENTF to request control of a remote system
by a new NTF operator. The request may also specify whether unsolicited
messages are to be sent over the connection.

\+
 Message received from OPES or OPENTF

 Required parameters

\+
 - Station Name
 - Family Name
 - User Name
 - Control Device
\-

 Optional parameters

\+
 - Station Usage
 - Accept Messages
\--
\ n.n.n.n Add User Response
 Response message to the Add User command above.

\+
 Message sent to OPES or OPENTF

 Parameters

\+
 - Station Name
 - Response Code
\--
\ n.n.n.n Change Batch Device Attributes
 Request to change various attributes defined for batch devices or batch
streams.  This message is generated by a change_batch_device_attributes
I/O station operator command or by a change_batch_stream_attributes NTF
operator command.

\+
 Message received from OPES or OPENTF

 Required parameters

\+
 - Station Name
 - Device Name
\-

 Optional parameters

\+
 - Device Alias 1
 - Device Alias 2
 - Device Alias 3
 - Terminal Model
 - File Acknowledgement
 - Transmission Block Size
 - Maximum File Size
 - Page Width
 - Page Length (ignored at NOSVE R1.2.2)
 - Banner Page Count
 - Banner Highlight Field
 - Carriage Control Action
 - Forms Code (1 - 4)
 - External Characteristics (1 - 4)
 - Code Set
 - Vertical Print Density
 - VFU Load Procedure
 - Forms Size
 - Undefined Format Effector Action
 - Unsupported Format Effector Action
 - Skip Punch Count
 - Control Code Replacement
 - Data Parity
 - Site-defined Code Set
\--
\ n.n.n.n Change Batch Device Attributes Response
 Response message to the Change Batch Device Attributes command above.

\+
 Message sent to OPES or OPENTF

 Required parameters

\+
 - Station Name
 - Device Name
 - Response Code
\-

 Optional parameters

\+
 - Device Alias 1
 - Device Alias 2
 - Device Alias 3
 - Terminal Model
 - File Acknowledgement
 - Transmission Block Size
 - Maximum File Size
 - Page Width
 - Page Length (ignored at NOSVE R1.2.2)
 - Banner Page Count
 - Banner Highlight Field
 - Carriage Control Action
 - Forms Code (1 - 4)
 - External Device Characteristics (1 - 4)
 - Code Set
 - Vertical Print Density
 - VFU Load Procedure
 - Forms Size
 - Undefined Format Effector Action
 - Unsupported Format Effector Action
 - Invalid Attribute (parameter # with validation error)
 - Skip Punch Count
 - Control Code Replacement
 - Data Parity
 - Site-defined Code Set
\--
\ n.n.n.n Stop Batch Device
 Request that a batch device or batch stream be suspended from file scheduling.
If any
transfer is active the action required is specified by the File Disposition
parameter.

\+
 Message received from OPES or OPENTF

 Required parameters

\+
 - Station Name
 - Device Name
 - File Disposition
\--
\ n.n.n.n Stop Batch Device Response
 Response to the Stop Batch Device command above.

\+
 Message sent to OPES or OPENTF

 Required parameters

\+
 - Station Name
 - Device Name
 - Response Code
\--
\ n.n.n.n Start Batch Device
 Request that a batch device or batch stream currently "stopped" be enabled
for scheduling.

\+
 Message received from OPES or OPENTF

 Required parameters

\+
 - Station Name
 - Device Name
\--
\ n.n.n.n Start Batch Device Response
 Response to the Start Batch Device command above.

\+
 Message sent to OPES or OPENTF

 Required parameters

\+
 - Station Name
 - Device Name
 - Response Code
\--
\ n.n.n.n Terminate Transfer
 Command to terminate the transfer of a job/file from/to
a batch device or batch stream.  The batch device or batch stream
remains active for the transfer of subsequent jobs/files.
The only permissible file disposition option for an input device
or receive type batch stream
is DROP. The
allowable file disposition options for an output device
or transmit batch stream
are: REQUEUE, DROP,
and HOLD.

\+
 Message received from OPES or OPENTF

 Required parameters

\+
 - Station Name
 - Device Name
 - File Disposition
\--
\ n.n.n.n Terminate Transfer Response
 Response to the Terminate Transfer command above.

\+
 Message sent to OPES or OPENTF

 Required parameters

\+
 - Station Name
 - Device Name
 - Response Code
\--
\ n.n.n.n Select File
 Request that an output file be selected for immediate processing on the I/O
station being operated. In the event of the file being eligible for processing
on multiple I/O stations, the file is removed from selection for all I/O
stations controlled by the same Control Facility. Candidate I/O stations
controlled by another control facility are not affected.
 If the optional device name is included, the file is forced to that device.
 This message is also used to request that a NTF file be selected for
immediate processing.  If the optional batch stream name is included, the file
is forced to that batch stream.

\+
 Message received from OPES or OPENTF

 Required parameters

\+
 - Station Name
 - System File Name or User File Name
\-

 Optional parameters

\+
 - Device Name
\--
\ n.n.n.n Select File Response
 Response to the Select File command above.

\+
 Message sent to OPES or OPENTF

 Required parameters

\+
 - Station Name
 - System File Name or User File Name
 - Response Code
\-

 Optional parameters

\+
 - Device Name
\--
\ n.n.n.n Get Device Status
 Request for detailed status information about a specified batch device
or batch stream.
\+

 Message received from OPES or OPENTF

 Required parameter

\+
 - Station Name
 - Device Name
\--
\ n.n.n.n Device Status Data
 Response to Get Device Status command above. Status information is returned
for the
specified batch device or batch stream.
 If this is a response to a Station Status message that requested an OPTIMIZED
response then the Device Status Data message will contain information about all
the devices on the I/O station.  Information about each device will be separated
from the next by a NULL parameter.
\+

 Message sent to OPES or OPENTF

 Required parameters

\+
 - Station Name
 - Device Name
 - Response Code
 - Device Status
 - Device Type
 - File Transfer Status
 - Terminal Model
 - File Acknowledge
 - Maximum File Size
 - Page Length (ignored at NOSVE R1.2.2)
 - Page Width
 - Banner Page Count
 - Banner Highlight Field
 - Transmission Block Size
 - Carriage Control Action
 - Forms Code 1
 - External Characteristics 1
 - Suppress Carriage Control
 - Last Unsolicited Message
 - Code Set
 - Vertical Print Density
 - Forms Size
 - Undefined Format Effector Action
 - Unsupported Format Effector Action
 - VFU Load Option
 - Control Code Replacement
 - Data Parity
\-

 Optional parameters

\+
 - Device Alias (1 - 3)
 - External Characteristic (2 - 4)
 - Forms Code (2 - 4)
 - VFU Load Procedure
 - Site-defined Code Set
\-

 Optional parameters for output devices

\+
 - System Supplied File Name
 - User Supplied File Name
 - System Supplied Job Name of Originating Job
 - User Supplied Job Name of Originating Job
 - Login User Name of Originating Job
 - Family Name of Originating Job
 - Percent Complete
\-

 Optional parameters for input devices

\+
 - User Job Name
 - Destination Name
 - Input Bytes Transferred
\-

 Optional parameters for NTF

\+
 - Logical Line Number
 - Transparent Mode
 - Skip Punch Count
\--
\ n.n.n.n Get Queue Status
 Request for status information about output queue(s) for an I/O station or
transmit queue(s) for a remote system.  Information is accumulated for all
queues which may be processed by the I/O station or remote system.
\+

 Message received from OPES or OPENTF

 Required parameters

\+
 - Station Name
\--
\ n.n.n.n Queue Status Data
 Response to the Get Queue Status command above.  Information is returned as
specified under the Get Queue Status command above.
 The status data returned comprises:
\item,j1,l.
 . Number of files for selector
 . Total byte length of files for selector
 . Age of oldest file for selector (integer minutes)
 . Average age of files for selector (integer minutes)
\block,j1,i4

\+

 Message sent to OPES or OPENTF

 Required parameters

\+
\nojust
 - Station Name
 - Number of Files in Queue
 - Response Code
 - Count of External Characteristics
 - External Characteristic & Status (repeated Count times)
 - Count of Forms Codes
 - Forms Code & Status (repeated Count times)
 - Count of Device Names
 - Device Name & Status (repeated Count times)
 - Count of Destination Names (Station and Station Alias or Remote System Names)
 - Destination & Status (repeated Count times)
 - Count of Device Types
 - Device Type and Status
\just
\--
\ n.n.n.n Get Queue Entry List
 Request for a list of all system file names and current priorities for files
in a queue.

 If the optional parameter number of entries is supplied only that many
file names will be returned. File names are returned in priority order.

 If optimization is requested then attributes of all queue files will be returned
using the Queue Entry Data message.
\+

 Message received from OPES or OPENTF

 Required parameters

\+
 - Station Name
 - All or Top 10 Files
\-

 Optional parameter

\+
 - Optimize Queue List

\--
\ n.n.n.n Queue Entry List Data
 Response to the Get Queue Entry List command above. Information is returned as
specified under Get Queue Entry List command above.
\+

 Message sent to OPES or OPENTF

 Required parameters

\+
\nojust
 - Station Name
 - Response Code
 - Count of files
 - System File Name & Priority (repeated Count times)
\just
\--
\ n.n.n.n Get Queue Entry
 Request for detailed information about a specified queue file.
\+

 Message received from OPES or OPENTF

 Required parameters

\+
 - Station Name
 - System File Name or User File Name
\--
\ n.n.n.n Queue Entry Data
 Response to the Get Queue Entry command above,
or to the Get Queue Entry List (w/optimize) command.
Detailed information pertaining
to the specified queue file(s) is returned.
 If the number of files is more than can be sent in
one message, multiple messages will be sent, each of
which will end with the continue parameter (except
the last).
\+

 Message sent to OPES or OPENTF

 Required parameters

\+
 - Station Name
 - System File Name
 - Response Code
 - User File Name
 - Time Enqueued by SCFS/VE
 - Position in Queue
 - Priority
 - Copies
 - Creating Job Family Name
 - Creating System Job Name
 - Creating User Job Name
 - Creating User Name
 - Data Mode
 - Destination Name
 - Device Type
 - File Length
 - File Transfer State
\-

 Optional parameters

\+
 - Device name
 - External Characteristics
 - Forms Code
 - Page Format
 - Page Length (ignored at NOSVE R1.2.2)
 - Page Width
 - Vertical Print Density
 - VFU Load Procedure
 - Queue Entry Data Continues
\--
\page
\ n.n Messages between SCFS/VE and OPERATE_STATION utility
\ n.n.n.n Position File
 Request to re-position a device output transfer currently active. The
request is sent in response to a position_device operator command. The
information is forwarded to SCF/DI for processing and the device suspended.

\+
 Message received from OPERATE_STATION utility

 Required parameters

\+
 - I/O Station Name
 - Device Name
 - Location Integer
 - Location String 1
 - Location String 2
 - Units
 - Direction
 - Starting position
\-

 Optional parameters

\+
 - Preview line count
\--
 Note the location specifiers may only occur in the following groups:
\item,j1,n.
 . Location Integer alone
 . Location String 1 alone
 . Location String 1 and Location String 2
\block,j1,i4
 Any other combinations are invalid and should be considered illegal.
\ n.n.n.n Position File Transfer Response
 Response to the Position File Transfer command above.

\+
 Message sent to OPERATE_STATION utility

 Required parameters

\+
 - I/O Station Name
 - Device Name
 - Response Code
\--
\ n.n.n.n Suppress Carriage Control
 Request that carriage control processing be suppressed for a specified device.
Carriage control processing is only suppressed for a single file transfer.

\+
 Message received from OPERATE_STATION utility

 Required parameters

\+
 - I/O Station Name
 - Device Name
\--
\ n.n.n.n Suppress Carriage Control Response
 Response message to Suppress Carriage Control command above.

\+
 Message sent to OPERATE_STATION utility

 Required parameters

\+
 - I/O Station Name
 - Device Name
 - Response Code
\--
\ n.n.n.n Get Station Status
 Request for I/O station status information.
\+

 Message received from OPERATE_STATION utility

 Required parameters

\+
 - I/O Station Name
\-

 Optional parameter

\+
 - Optimized Device List
\--
\ n.n.n.n Station Status Data
 Reply to the "Get Station Status" request. Status information is returned
about the I/O station.
\+

 Message sent to OPERATE_STATION utility

 Required parameters

\+
\nojust
 - I/O Station Name
 - Response Code
 - Control Facility Name
 - Number of Files Queued for Output
 - Station Usage
 - File Acknowledgement
 - Count of Devices
 - Device Name, Device Status, File Transfer Status, & Device Type
(repeated Count times)
 - Default Job Destination
 - Destination Unavailable Action
 - PM Message Action
\-

 Optional parameters

\+
 - Required Console Device Name
 - I/O Station Alias 1
 - I/O Station Alias 2
 - I/O Station Alias 3
\--
\just
 Note the Device Name, Device Status, Device Type, and File Transfer Status are
all returned in one parameter using the "Device Status Name" parameter format.
\ n.n.n.n Terminate Queued Output
 Request to delete a file from the station's output queue before it gets
transferred.

\+
 Message sent by OPERATE_STATION utility to SCFS and by SCFS/VE to SCF/VE

 Required Parameters

\+
 - I/O Station Name
 - System File Name or User File Name
\--
\ n.n.n.n Terminate Queued Output Response
 Response to Terminate Queued Output command above.

\+
 Message sent by SCF/VE to SCFS/VE and by SCFS to OPERATE_STATION utility

 Required Parameters

\+
 - I/O Station Name
 - System File Name or User File Name
 - Response Code (Status of file termination)
\--
\ n.n.n.n Operator Message
 Request to send a message to the I/O station
operator. This message is expected to originate in a print file "PM"
entry, upon detection of an error condition, to contain preview data for
file positioning, upon file assignment to a device, upon completion of a
file transfer to a device, or upon control facility change.

\+
 Message sent to OPERATE_STATION utility

 Required parameters

\+
 - I/O Station Name
 - Device Name
 - text
\--
\page
\ n.n Messages between SCFS/VE and OPERATE_NTF utility
\ n.n.n.n Delete User
 Request to relinquish control of the remote system by the specified NTF
operator.

\+
 Message received from OPENTF

 Required parameters

\+
 - Remote System Name
 - Family Name
 - User Name
\--
\ n.n.n.n Delete User Response
 Response message to the Delete User command above.

\+
 Message sent to OPENTF

 Parameters

\+
 - Remote System Name
 - Response Code
\--
\ n.n.n.n Get Remote System Names
 Request the logical names and kinds of remote systems.

\+
Message received from OPERATE_NTF utility

 Optional parameters

\+item
 - Remote System Name
 - Logical Line Number
 - Remote System Kind
\--
\ n.n.n.n Remote System Names Data
 Response to the Get Remote System Names command above.

\+
 Message sent to OPERATE_NTF utility

 Required parameters

\+item
 - Response Code
 - Count of Remote Systems
 - Remote System Name, Type, Kind, Route Back Position and Authority
Level(repeated count times)
\--
\ n.n.n.n Get Remote System Options
 Request for remote system options information.

\+
 Message received from OPERATE_NTF utility

 Required parameter

\+item
 - Remote System Name
\--
\ n.n.n.n Remote System Options Data
 Response to the Get Remote System Options command above.

\+
 Message sent to OPERATE_NTF utility

 Required parameters

\+item
 - Directly Connected Remote System Name
 - Response Code
 - Control Facility
 - Remote System Protocol
 - Authority Level
 - Wait-a-bit
 - Inactivity Timer
 - Positive Acknowledge
 - Default Job Destination
 - Default File Destination
 - Store and Forward Destination
 - Count of Logical Line Numbers
 - Logical Line Number, Line Name and Terminal User Procedure
(repeated count times)
 - Count of Batch Streams
 - Batch Stream Name (repeated count times)
 - Remote System Type
 - Route Back Position
 - Request Permission Retry
 - Local System Name
\--
\ n.n.n.n Send Remote Command
 Request to transmit a command or message to a remote system.

\+
 Message received from OPERATE_NTF utility

 Required parameters

\+item
 - Remote System Name
 - Logical Line Number
 - Command Type (Command, Message, Signon, Signoff, TDP)
 - Command Text
\--
\ n.n.n.n Send Remote Command Response
 Response to the Send Remote Command command above.

\+
 Message sent to OPERATE_NTF utility

 Required parameters

\+item
 - Remote System Name
 - Command Type
 - Response Code
\--
\ n.n.n.n Get Remote System Status
 Request remote system status information.

\+
 Message received from OPERATE_NTF utility

 Required parameter

\+item
 - Remote System Name
\-

Optional parameters

\+
 - Logical Line Number
 - Signon Status
\--
\ n.n.n.n Remote System Status Data
 Response to the Get Remote System Status command above.

\+
 Message sent to OPERATE_NTF utility

 Required parameters

\+item
 - Remote System Name
 - Response Code
 - Count of Lines to the Remote System
 - Logical Line Number, Line Name, Line Speed, and
Signon Status (repeated count times)
\--
\page
\ n.n Messages between SCFS/VE and multiple partners
\ n.n.n.n Transfer SCFS/VE Control
 Switch between different priority copies of SCFS/VE. This message is
issued by a higher priority copy of SCFS/VE to a lower priority copy
of SCFS/VE. The lower priority copy passes control of all I/O stations
or remote systems
associated with the specified control facility title to the higher
priority copy.

\+
 Message sent to all connections

 Required parameters

\+
 - Connection Identifier
 - SCFS/VE Network Address (higher priority SCFS)
\--
\ n.0 SCFS/VE Connection Establishment
 This section describes what information is sent by the client and SCFS/VE
when a connection is being established.

 SCFS/VE expects to receive a 5 or 6 character client identifier when it
receives a SAP event. The identifiers are as follows:

\+
 - SCFDI   (indicating SCF/DI client)
 - SCFVE   (indicating SCF/VE client)
 - SCFSVE  (indicating a different priority SCFS/VE)
 - OPESVE  (indicating the OPERATE_STATION utility)
 - NTFVE   (indicating NTF/VE client)
 - OPENTF  (indicating the OPERATE_NTF utility)
\-

 When SCFS/VE accepts the connection, it sends its control facility name to the
client.
\ n.0 message protocol definitions
 This section provides detailed definitions of the message protocols
to be followed. The protocol is presented by function (e.g. configure
I/O station etc.) rather than by single message specification. This
presentation allows for a functional representation of the SCFS/VE
message flow data.
\ n.n notes
\item,j1,n.
 . A series of periods have been used to denote the passing of time. During
this time any other operations may have been performed, thus all information
related to a specific message must be assumed to be destroyed. Any "state"
information required to be preserved must be saved in the I/O station
or batch device definition tables within SCFS/VE.
\block,j1,i4
\page
\ n.n i/o station and batch device maintenance

\asis
   Action              SCF/DI              SCFS/VE
   ------              ------              -------

  New I/O station        Add I/O Station
  defined and first      ------------------------>
  batch device is
  connected to the DI.

                         Add I/O Station Response
                        <------------------------

                                .
                                .
                                .
  New batch device       Add Batch Device
  defined (one per       ------------------------->
  device)
                         Add Batch Device Response
                         <-------------------------


              Normal operation of station

                                .
                                .
                                .

  Batch device lost      Delete Batch Device
                         ------------------------->
                         Delete Batch Device Response
                         <-------------------------


                                .
                                .
                                .

  Last batch device      Delete I/O Station
  deleted (disconnected  ------------------------->
  from the network)
                         Delete I/O Station Response
                        <---------------------------
\page
\ n.n output file maintain, assign and transfer

\asis
   Action     SCF/DI      SCFS/VE       SCF/VE        OPES
   ------     ------      -------       ------        ----

  Maintain                   File Available
  file in                   <--------------
  queue                       .
                              .
                              .
  Output                    File Assignment
  device ok                 --------------->
                          File Assignment Response
                            <-----------------

                              .
                              .
                              .
                File Status
                -------------->
                (started)
                              Operator Message
                              --------------------->
                        (file acknowledgement if required)
                              .
                              .

                    file transfer underway

                              .
                              .
                File Status
                -------------->
                (percent complete update)
                              .
                              .
  Transfer      File Status
  complete      -------------->
                (complete)
                              Operator Message
                              --------------------->
                        (file acknowledgement if required)
\page
\ n.n input file transfer

\asis
   Action     SCF/DI         SCFS/VE              OPES
   ------     ------         -------              ----

  Input device  File Status
  started       ---------------->
                (active,busy)
                                .
                                .
                                .
  Transfer      File Status
  complete      ---------------->
                (complete)
                              Operator Message
                              --------------------->
                        (file acknowledgement if required)
\page
\ n.n assign i/o station operator

      Action      SCF/DI       SCFS/VE           OPES
      ------      ------       -------           ----

  New operator                        Add User
  request                         <----------------

  Validate user
                                  Add User Response
                                  ----------------->
                    Start I/O Station
                   <---------------

                                  .
                                  .
                                  .
   Operator         Stop I/O Station
   connection      <---------------
   broken
\page
\ n.n start/stop batch device

      Action      SCF/DI       SCFS/VE           OPES
      ------      ------       -------           ----

                                   Stop Batch device
                                  <----------------
                      Stop Batch Device
                    <--------------

                      Stop Batch Device Response
                    -------------->

                                 Stop Batch Device Response
                                     -------------->

                      File Status
                    -------------->
                 (complete or suspended)

                                 .
                                 .
                                 .
  Device now off
                                   Start Batch Device
                                 <----------------
                      Start Batch Device
                    <-------------
  Device now on       Start Batch Device Response
                    -------------->
                                 Start Batch Device Response
                                     -------------->
                    Batch Device Status
                    -------------->
\page
\ n.n position file

\asis
  Action          SCF/DI         SCFS/VE          OPES
  ------          ------         -------          ----

                                     position file
 Command received                   <---------------
 and forwarded      Position File Transfer
                   <-----------------
                   Position File Transfer Response
                   ----------------->
                               Position File Transfer Response
                                     --------------->

                      File Status
                    ---------------->
                      (suspended)
                                     .
                                     .
                                     .
 Optional preview  Operator Message
 data sent         ----------------->
                    (preview data)   Operator Message
                                     --------------->
                                      (preview data)
                                     .
                                     .
                                     .

 Preview complete                     Start Batch Device
                                     <---------------
                    Start Batch Device
                   <------------------
  Device now on       Start Batch Device Response
                    -------------->
                                 Start Batch Device Response
                                       ------------>
                    Batch Device Status
                    -------------->
\page
\ n.n display station status

\asis
 If OPERATE_STATION requests an OPTIMIZED device list
 the protocol is as follows:

 Action                   SCFS/VE                 OPES
 ------                   -------                 ----

 Get list of files            get station status
 in queue (optimized)        <----------------------

 Send information about       device status data
 all batch devices           ---------------------->


 If OPERATE_STATION does not request an optimized device
 list the protocol is as follows:

    Action               SCFS/VE                  OPES
    ------               -------                  ----

 Get information              get station status
 for station                <-----------------------

                              station status data
                            ----------------------->
\page
\ n.n display queue entry

\asis
 If OPERATE_STATION requests an OPTIMIZED queue entry
 list the protocol is as follows:

 Action                   SCFS/VE                 OPES
 ------                   -------                 ----

 Get list of files            get queue entry list
 in queue (optimized)        <----------------------

 Send information about       queue entry data
 all queue files             ---------------------->
                              .
 Send as many messages as     .
 needed.                      .
                              queue entry data
                             ---------------------->


 If OPERATE_STATION does not request an optimized queue entry
 list the protocol is as follows:

 Action                   SCFS/VE                 OPES
 ------                   -------                 ----

 Get list of files            get queue entry list
 in queue                    <----------------------

                              queue entry list data
                             ---------------------->
                              .
                              .
                              .

 Get information for a          get queue entry
 specific entry in the       <----------------------
 queues
                                queue entry data
                             ---------------------->

                              .
                              .

      get queue entry is repeated as required to get all data
\page
\ n.n remote system and batch stream maintenance

\asis
   Action              SCF/DI              SCFS/VE
   ------              ------              -------

  New remote system      Add Remote System
  defined and first      ------------------------>
  batch stream is
  connected to the DI.

                         Add Remote System Response
                        <------------------------

                                .
                                .
                                .
  New batch stream       Add Batch Device
  defined (one per       ------------------------->
  stream)
                         Add Batch Device Response
                         <-------------------------


                        Normal operation

                                .
                                .
                                .

  Batch stream lost      Delete Batch Device
                         ------------------------->
                         Delete Batch Device Response
                         <-------------------------


                                .
                                .
                                .

  Last batch stream      Delete Remote System
  deleted (disconnected  ------------------------->
  from the network)
                         Delete Remote System Response
                        <---------------------------
\page
\ n.n remote system output file assignment and transfer

\asis
   Action     SCF/DI      SCFS/VE       NTF/VE
   ------     ------      -------       ------

  File in
  queue
                             File Available
                            <--------------
                              .
                              .
                              .
  Output                    File Assignment
  stream ok                 --------------->
                          File Assignment Response
                            <-----------------

                              .
                              .
                              .
                File Status
                -------------->
                (started)
                              .
                              .

                    file transfer underway

                              .
                              .
                File Status
                -------------->
                (percent complete update)
                              .
                              .
  Transfer      File Status
  complete      -------------->
                (complete)
\page
\length+4
\ n.n start/stop batch stream

      SCF/DI       SCFS/VE           OPENTF     Operator
      ------       -------           ------     --------

                                        Stop_Batch_Stream
                                       <----------------
                       Stop Batch Device
                      <----------------
          Stop Batch Device
        <--------------

          Stop Batch Device Response
        -------------->

                     Stop Batch Device Response
                     -------------->

                                        Stop_Batch_Stream Response
                                       ---------------->
          File Status
        -------------->
     (complete or suspended)

                     .
                     .
                     .
  Device now off
                                        Start_Batch_Stream
                                       <----------------
                       Start Batch Device
                     <----------------
          Start Batch Device
        <-------------

  Device now on

          Start Batch Device Response
        -------------->
                     Start Batch Device Response
                         -------------->
                                        Start_Batch_Stream Response
                                       ---------------->
        Batch Device Status
         -------------->
\length
\page
\ n.n display remote system status
\block

\asis
    Action               SCFS/VE                  OPENTF
    ------               -------                  -----

 Get information              Get Remote System Status
 for remote system          <-----------------------

                              Remote System Status Data
                            ----------------------->



\ n.n display remote system queue entry

\asis
 Action                   SCFS/VE                 OPENTF
 ------                   -------                 ------

 Get list of NTF              Get Queue Entry List
 files in queue              <----------------------

                              Queue Entry List Data
                             ---------------------->
                              .
                              .
                              .

 Get information for a          Get Queue Entry
 specific entry in the       <----------------------
 queues
                                Queue Entry Data
                             ---------------------->

                              .
                              .

      Get Queue Entry is repeated as required to get all data
\setsec1
\setapp=A-Appendix A
\page1
\title2=Detailed message descriptions
\ n. introduction
\block,j1,i4
 This appendix presents detailed specifications of the message formats
for SCFS/VE. Each message is presented with all parameters and the binary
representation where applicable.
\ n.n Attribute Number/Attribute Value (AN/AV) Message Format
 AN/AV messages are command messages and are sent as Session Layer data
messages.  The required parameters as designated in
Section 2 of this document must be present in the order shown in this
appendix for all AN/AV formatted messages. Optional parameters may or
may not be present and may occur in any order.
 The An/AV messages are formatted according to the following layout. Each
message starts with a message type indicator byte. This is followed by a
variable number of (attribute/name, attribute/value) pairs. The total
message length is not restricted. The (attribute/name, attribute/value)
pairs are formatted as shown.

\asis
byte 1    <-- additional 8 bit bytes (no max. limit) --->
+----------------------------------------------------------------
|       |
| MTI   | attribute number/attribute value string
|       |
+----------------------------------------------------------------
  ^
  |
  +----- Message Type Indicator

Attribute number/attribute value strings have the following format:

+------------------------\------------\ +-------------------------
|  |         | |          |             |  |
|L |attribute|L|length    | attribute   |L |  next
|I | number  |L|field     |  value      |I |  number
|  |         | |          |             |  |
+------------------------\------------\ +-------------------------
\block,j1,i4
 The fields LI and length fields are to be interpreted in the following
manner  If the LI bit is 0 no length byte is included, and the attribute value
field has a length of one byte. If the LI field is 1 the length field is included
and is interpreted as follows.  If LL = 0, the length field is 1 byte and specifies the
attribute value length up to 127 bytes. If the LL field is set to 1, the length field
is the number of bytes that make up the length of the attribute value.  For
messages sent to and received from the DI, the length field will be 2 and
maximum attribute value length will be 65,535 bytes. For messages between
NOS/VE mainframes, the length field can be larger than 2, meaning the attribute
value length can be greater than 65535 bytes.

Examples:
\asis
+-------------------------------------\ +-------------------------
|  |         |L |         |             |  |
|L |attribute|L |length of| attribute   |L |  next
|I | number  |= | value   |  value      |I |  number
|  |         |O | 1..127  |             |  |
+-------------------------------------\ +-------------------------

 EXAMPLE ATTRIBUTE VALUE LESS THAN OR EQUAL TO 127 BYTES

+---------------------------------\+------------\+----------------
|  |         |L | length  |              |           |  |
|L |attribute|L |   of    | length bytes | attribute |L | next
|I | number  |= | length  |              |  value    |I | number
|  |         |1 | bytes*  |              |           |  |
+---------------------------------\+------------\ +---------------

 EXAMPLE ATTRIBUTE VALUE GREATER THAN 127 BYTES


\block,j1,i4
\ n.n.n Notes
\item,j1,N)
 . The message type is one byte.  The identifier parameters may vary
in length but are fixed in length for each message type.
 . Attribute value fields which represent Cybil ordinal type values are
flagged by an asterisk in the allowed value field.  The description of
these field values for reason codes is presented in appendix A4 and the
description of other field values is presented in appendix A5.
 . Some attributes are of type "Dev^Stat^Data".
The attribute is physically 3 one byte
integer fields followed by an ascii string of up to 31 bytes. It may be
considered to be the following Cybil data structure:

\+asis
  TYPE
    device_status_data = record
      device_status: device status, (1 Byte)
      file_xfer_status: file transfer status, (1 Byte)
      type: device_type, (1 Byte)
      name: string ( * <= 31),
    recend;
\-
 . Some attributes are of the type "q status data".
The attribute consists physically of
four 8 byte integer fields followed by
two fixed ascii strings of 31 bytes followed by
an ascii string of up to 31 bytes.
It may be considered to be the following Cybil data structure:

\+asis
  TYPE
    q_status_data = record
      file_count: integer, (8 Bytes)
      total_size: integer,
      oldest_age: integer,
      average_age: integer,
      operator_name: string (31),
      operator_family: string (31),
      name: string ( * <= 31),
    recend;
\-
 . Some attributes are of the type "file priority".
The attribute consists physically of
a 1 integer field followed by an ascii string of up to 31 bytes. It may be
considered to be the following Cybil data structure:

\+asis
  TYPE
    file_and_priority = record
      priority: integer, (8 Bytes)
      name: string ( * <= 31),
    recend;
\-
 . One attribute is of the type "date and time". The attribute consists
physically of a 6 one byte fields followed by a two byte field. It may be
considered to be the following Cybil data structure:

\+asis
  TYPE
    date and time = record
      year: 0 .. 255, (1 Byte)  {year minus 1900. e.g. 85 = 1985}
      month: 1 .. 12 (1 Byte)
      day: 1 .. 31 (1 Byte)
      hour: 0 .. 24 (1 Byte)
      minute: 0 .. 59 (1 Byte)
      second: 0 .. 59 (1 Byte)
      millisecond: 0 .. 999, (2 Bytes)
    recend;
\-
 . One attribute is of type "rmt^sys^data".  The attribute is physically four
one byte fields followed by an ascii string of up to 31 bytes.  It may be
considered to be the following Cybil data structure:

\+asis
  TYPE
    remote_system_data = record
      remote_system_type: remote system type, (1 Byte)
      remote_system_kind: remote system kind, (1 Byte)
      route_back_position: 0..255, (1 Byte)
      authority_level: authority level, (1 Byte)
      name: string ( * <= 31),
    recend;
\-
 . One attribute is of type "rmt^stat^data".  The attribute is physically
a two byte field followed by 2 one byte fields followed by an ascii string
of up to 31 bytes.  It may be considered to be the following Cybil data
structure:

\+asis
  TYPE
    remote_status_data = record
      logical_line_number: 0..999, (2 Bytes)
      line_speed: line speed, (2 Bytes)
      signon_status: device status, (1 Byte)
      name: string ( * <= 31),
    recend;
\-
 . One attribute is of type "log^line^data".  The attribute is
physically a two byte field followed by a fixed ascii string of 31
bytes followed by an ascii string of up to 31 bytes.  It may be
considered to be the following Cybil data structure:
\+asis
  TYPE
    logical_line_data = record
      logical_line_number: 0..999, (2 Bytes)
      tup: string (31),
      name: string ( * <= 31),
    recend;
\-
 . One attribute is of type "ccr^data".  The attribute can range from 2 to 128
bytes.  Each byte pair is interpreted as follows:  The first character must be
in the range 00..1f(16) or 80..9f(16).  This is a control code character which
is to be replaced or deleted.  The second character can equal the first
character in which case the control code is to be deleted.  If the second
character is not equal to the first then the second character is to replace the
control code.
\+asis
  TYPE
    ccr_data: array (2..128) of char;
\-
\block,j1,i4
\page
\ n.0 detailed message formats
\ n.n Messages between SCFS/VE and SCF/DI
\block
\keep33
\ n.n.n.n Add I/O Station

 Message type = 20

\box,1,12,39,47,62
\+table;2,19,40,50
 ;attribute;description;length;allowed
 ;^number;;;^values
\boxline
\+table;6,14,41,49
 ;01;I/O station name;1..31;ascii string
\boxline
 ;02;I/O station alias 1;1..31;ascii string
\boxline
 ;03;I/O station alias 2;1..31;ascii string
\boxline
 ;04;I/O station alias 3;1..31;ascii string
\boxline
 ;05;required operator device;1..31;ascii string
\boxline
 ;06;station usage;1;*0..2
\boxline
 ;07;file acknowledgement;1;0=no, 1=yes
\boxline
 ;08;check  I/O station unique;1;0=no, 1=yes
\boxline
 ;09;auto operator control;1;*0=no, 1=yes
\boxline
 ;10;default job destination;1..31;ascii string
\boxline
 ;11;dest. unavail. action;1;*0..1
\boxline
 ;12;PM message action;1;*0..2
\nobox
\--
\page
\ n.n.n.n Delete I/O Station

 Message type = 21

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\nobox
\--
\ n.n.n.n Add Batch Device

 Message type = 22

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;device status;1;*0..15
\boxline
 ;04;file transfer status;1;*0..15
\boxline
 ;05;device alias 1;1..31;ascii string
\boxline
 ;06;device alias 2;1..31;ascii string
\boxline
 ;07;device alias 3;1..31;ascii string
\boxline
 ;08;device type;1;*0..10
\boxline
 ;09;tip type;1;*0..15
\boxline
 ;10;terminal model;1..31;ascii string
\boxline
 ;11;file acknowledgement;1;0=no, 1=yes
\boxline
 ;12;transmission block size;2;tip dependant
\boxline
 ;13;maximum file size;4;0..99999999
\boxline
 ;14;page width;1;10..255
\boxline
 ;15;page length;1;0..176
\boxline
 ;16;banner page count;1;0..3
\boxline
 ;17;banner highlight field;1;*0..4
\boxline
 ;18;carriage control action;1;*0..2
\boxline
 ;19;forms code 1;1..6;ascii string
\boxline
 ;20;forms code 2;1..6;ascii string
\boxline
 ;21;forms code 3;1..6;ascii string
\boxline
 ;22;forms code 4;1..6;ascii string
\boxline
 ;23;device ext. chars. 1;1..6;ascii string
\boxline
 ;24;device ext. chars. 2;1..6;ascii string
\boxline
 ;25;device ext. chars. 3;1..6;ascii string
\boxline
 ;26;device ext. chars. 4;1..6;ascii string
\boxline
 ;27;suppress carriage cont.;1;0=off, 1=on
\boxline
 ;28;code set;1;*0..7
\boxline
 ;29;vertical print density;1;*0..3
\boxline
 ;30;VFU Load Procedure;1..31;ascii string
\boxline
 ;31;forms size;1;1..62
\boxline
 ;32;undefined fe action;1;*0..2
\boxline
 ;33;unsupported fe action;1;*0..2
\boxline
 ;34;VFU load option;1;*0..3
\boxline
 ;35;Maximum Page Length;1;0..255
\boxline
 ;36;transparent mode;1;0=off, 1=on
\boxline
 ;37;skip punch count;1;0..9
\boxline
 ;38;logical line number;2;1..999
\boxline
 ;39;Control Code replacement;2..128;ccr_data
\boxline
 ;40;Data Parity;1;*0..4
\boxline
 ;41;Site-defined Code Set;1..31;ascii string
\nobox
\--
\keep17
\ n.n.n.n Batch Device Status

 Message type = 23

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;device status;1;*0..15
\boxline
 ;04;file transfer status;1;*0..15
\nobox
\--
\keep18
\ n.n.n.n File Status

 Message type  = 24

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;device status;1;*0..15
\boxline
 ;04;file transfer status;1;*0..15
\nobox

\keep17
 Optional or Required - depending on device type

\box
 ;05;file position (% done);1;0..100
\boxline
 ;06;system job/file name;1..31;ascii string
\boxline
 ;07;system id (family);1..31;ascii string
\boxline
 ;08;user job/file name;1..31;ascii string
\boxline
 ;09;actual destination;1..31;ascii string
\boxline
 ;10;requested destination;1..31;ascii string
\boxline
 ;11;input bytes transferred;4;integer
\nobox
\--
\keep13
\ n.n.n.n Delete Batch Device

 Message type = 25

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\nobox
\--
\keep19
\ n.n.n.n BTFS/DI Status

 Message type = 26

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;BTFS/DI network address;12;gt_sap
\boxline
 ;02;BTFS/DI status;1;*0..1
\boxline
 ;03;BTFS/DI title;1..255;ascii string
\boxline
 ;04;BTFS/DI advanced features;1;*0..1
\nobox
\--
\keep13
\ n.n.n.n Add I/O Station Response

 Message type = 27

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\boxline
 ;02;response code;1;*0..3
\nobox
\--
\keep13
\ n.n.n.n Delete I/O Station Response

 Message type = 28

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\boxline
 ;02;response code;1;*0..1
\nobox
\--
\keep13
\ n.n.n.n Start I/O Station

 Message type = 29

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\boxline
 ;02;user identity;62;ascii string
\nobox
\--
\keep11
\ n.n.n.n Stop I/O Station

 Message type = 30

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\nobox
\--
\keep17
\ n.n.n.n Switch Control

 Message type = 31

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;control facility;1..31;ascii string
\nobox
\--
\keep17
\ n.n.n.n Position File (to SCF/DI)

 Message type = 32

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;position parameters *;1..32k;as required
\nobox
 ;*  these parameters are transferred to BTF/VE as received
\--
\keep15
\ n.n.n.n Add Batch Device Response

 Message type = 33

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;response code;1;*0..3
\nobox
\--
\keep15
\ n.n.n.n Delete Batch Device Response

 Message type = 34

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;response code;1;*0..2
\nobox
\--
\keep45
\ n.n.n.n Add Remote System

 Message type = 35

\box,1,12,39,47,62
\+table;2,19,40,50
 ;attribute;description;length;allowed
 ;^number;;;^values
\boxline
\+table;6,14,41,49
 ;01;remote system name;1..31;ascii string
\boxline
 ;02;remote system protocol;1;*0..1
\boxline
 ;03;logical line number;2;1..999
\boxline
 ;04;line speed;2;50..64000
\boxline
 ;05;line name;1..31;ascii string
\boxline
 ;06;authority level;1;*0..2
\boxline
 ;07;terminal user procedure;1..31;ascii string
\boxline
 ;08;wait-a-bit;1;*0..1
\boxline
 ;09;inactivity timer;2;0..600
\boxline
 ;10;positive acknowledge;1;*0..1
\boxline
 ;11;default job destination;1..31;ascii string
\boxline
 ;12;default file destination;1..31;ascii string
\boxline
 ;13;store/forward destination;1..31;ascii string
\boxline
 ;14;remote system type;1;*0..5
\boxline
 ;15;route back position;1;0..255
\boxline
 ;16;request permission retry;1;0=no, 1=yes
\boxline
 ;17;local system name;1..31;ascii string
\nobox
\--
\keep27
\ n.n.n.n Add Accessible Remote System

 Message type = 36

\box,1,12,39,47,62
\+table;2,19,40,50
 ;attribute;description;length;allowed
 ;^number;;;^values
\boxline
\+table;6,14,41,49
 ;01;remote system name;1..31;ascii string
\boxline
 ;02;logical line number;2;1..999
\boxline
 ;03;accessible remote system;1..31;ascii string
 ;;name
\boxline
 ;04;authority level;1;*0..2
\boxline
 ;05;remote system type;1;*0..8
\boxline
 ;06;route back position;1;0..255
\nobox
\--
\keep13
\ n.n.n.n Delete Remote System

 Message type = 37

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;remote system name;1..31;ascii string
\boxline
 ;02;logical line number;2;1..999
\nobox
\--
\keep13
\ n.n.n.n Add Remote System Response

 Message type = 38

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;remote system name;1..31;ascii string
\boxline
 ;02;logical line number;2;1..999
\boxline
 ;03;response code;1;*0..4
\nobox
\--
\keep15
\ n.n.n.n Add Accessible Remote System Response

 Message type = 09

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;directly connected system;1..31;ascii string
\boxline
 ;02;logical line number;2;1..999
\boxline
 ;03;accessible remote system;1..31;ascii string
\boxline
 ;04;response code;1;*0..4
\nobox
\--
\keep13
\ n.n.n.n Delete Remote System Response

 Message type = 39

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;remote system name;1..31;ascii string
\boxline
 ;02;logical line number;2;1..999
\boxline
 ;03;response code;1;*0..1
\nobox
\--
\page
\block,j1,i4
\ n.n Messages between SCFS/VE and SCF/VE or SCFS/VE and NTF/VE
 The File Availability message format is used for Add File Availability
(message type 01), Modify File Availability (02), and Delete File Availability
(03). For all the messages the first 10 parameters are required. The rest of the
parameters are required for Add File Availability, optional for Modify File
availability, and not used for Delete File Availability (except "file held by
filter" - which is optional on Delete File Availability).

\keep25
\ n.n.n.n File Availability Messages

 Message types = 01, 02, 03

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;operator name (private);1..31;ascii string
\boxline
 ;03;operator family (private);1..31;ascii string
\boxline
 ;04;station usage;1;*0..2
\boxline
 ;05;system file name;1..31;ascii string
\boxline
 ;06;system job name;1..31;ascii string
\boxline
 ;07;user file name;1..31;ascii string
\boxline
 ;08;user job name;1..31;ascii string
\boxline
 ;09;user name (private);1..31;ascii string
\boxline
 ;10;user family (private);1..31;ascii string
\nobox

\keep21
 required for ADD, optional for MODIFY only when changed

\box
 ;11;copies;8;integer
\boxline
 ;12;device name;1..31;ascii string
\boxline
 ;13;device type;1;*0..10
\boxline
 ;14;ext. device chars.;1..6;ascii string
\boxline
 ;15;file size;4;0..99999999
\boxline
 ;16;forms code;1..6;ascii string
\boxline
 ;17;output data mode;1;*0..1
\boxline
 ;18;output initial priority;8;integer
\boxline
 ;19;output maximum priority;8;integer
\boxline
 ;20;output priority factor;8;integer
\boxline
 ;21;output state;1;*0..4
\boxline
 ;22;page format;1;*0..2
\boxline
 ;23;page length;1;0..176
\boxline
 ;24;page width;1;10..255
\boxline
 ;25;vertical print density;1;*0..7
\boxline
 ;26;VFU Load Procedure;1..31;ascii string
\boxline
 ;27;file requeued;1;0=no, 1=yes
\nobox

 optional for DELETE - sent only by SCF/VE

\box
 ;28;file held by filter;1;0=no, 1=yes
\nobox
\--
\page
\ n.n.n.n File Assignment

 Message type = 04

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;system file name;1..31;ascii string
\boxline
 ;03;device name;1..31;ascii string
\boxline
 ;04;BTFS/DI network address;12;generic_sap
\boxline
 ;05;requested destination;1..31;ascii string
\boxline
 ;06;requested device;1..31;ascii string
\boxline
 ;07;user name;1..31;ascii string
\boxline
 ;08;user family;1..31;ascii string
\boxline
 ;09;station usage;1;*0..2
\boxline
 ;10;copies;8;integer
\boxline
 ;11;ext. device char.;1..6;ascii string
\boxline
 ;12;forms code;1..6;ascii string
\boxline
 ;13;output initial priority;8;integer
\boxline
 ;14;VFU load procedure;1..31;ascii string
\boxline
 ;15;vertical print density;1;*0..7
\boxline
 ;16;remote system protocol;1;*0..1
\boxline
 ;17;device type;1;*0..10
\boxline
 ;18;remote system type;1;*0..8
\boxline
 ;19;route back position;1;0..255
\nobox
\page
\box
 ;20;BTFS/DI title;1..255;ascii string
\boxline
 ;21;banner highlight field;1;*0..4
\boxline
 ;22;banner page count;1;0..3
\boxline
 ;23;carriage control support;1;*0..2
\boxline
 ;24;code set;1;*0..7
\boxline
 ;25;device alias 1;1..31;ascii string
\boxline
 ;26;device alias 2;1..31;ascii string
\boxline
 ;27;device alias 3;1..31;ascii string
\boxline
 ;28;ext. characteristics 1;1..6;ascii string
\boxline
 ;29;ext. characteristics 2;1..6;ascii string
\boxline
 ;30;ext. characteristics 3;1..6;ascii string
\boxline
 ;31;ext. characteristics 4;1..6;ascii string
\boxline
 ;32;file acknowledgement;1;0=no, 1=yes
\boxline
 ;33;forms code 1;1..6;ascii string
\boxline
 ;34;forms code 2;1..6;ascii string
\boxline
 ;35;forms code 3;1..6;ascii string
\boxline
 ;36;forms code 4;1..6;ascii string
\boxline
 ;37;forms size;1;1..62
\boxline
 ;38;maximum file size;4;0..FFFFFFFF
\boxline
 ;39;page width;1;10..255
\boxline
 ;40;terminal model;1..31;ascii string
\boxline
 ;41;tip type;1;*0..15
\boxline
 ;42;transmission block size;2;tip dependant
\boxline
 ;43;undefined fe action;1;*0..2
\boxline
 ;44;unsupported fe action;1;0..2
\boxline
 ;45;vertical print density;1;*0..3
\boxline
 ;46;vfu load option;1;*0..3
\boxline
 ;47;vfu load procedure;1..31;ascii string
\nobox
\--
\keep19
\ n.n.n.n File Assignment Response

 Message type = 05

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;system file name;1..31;ascii string
\boxline
 ;03;device name;1..31;ascii string
\boxline
 ;04;response code;1;*0..2
\nobox
\--
\keep15
\ n.n.n.n Delete Destination

 Message type = 06

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;Destination name;1..31;ascii string
\boxline
 ;02;Control Facility name;1..31;ascii string
\nobox
\--
\keep13
\ n.n.n.n BTF/VE Status

 Message type = 07

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;BTF/VE protocol stacks;1;*0..3
\nobox
\--
\page
\ n.n Messages between SCFS/VE and Operator Utilities
 This section describes common messages between SCFS/VE and the
OPERATE_STATION utility or between SCFS/VE and the OPERATE_NTF utility.
\keep27
\ n.n.n.n Add User

 Message type = 60

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;control device name;1..31;ascii string
\boxline
 ;03;family name;1..31;ascii string
\boxline
 ;04;user name;1..31;ascii string
\boxline
 ;05;station usage;1;*0..2
\boxline
 ;06;accept messages;1;*0..1
\nobox
\--
\keep13
\ n.n.n.n Add User Response

 Message type = 61

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;response code;1;*0..3
\nobox
\--
\keep15
\ n.n.n.n Select File

 Message type = 62

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;system/user file name;1..31;ascii string
\boxline
 ;03;device name;1..31;ascii string
\nobox
\--
\keep17
\ n.n.n.n Select File Response

 Message type = 63

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;system/user file name;1..31;ascii string
\boxline
 ;03;response code;1;*0..6
\boxline
 ;04;device name;1..31;ascii string
\nobox
\--
\keep14
\ n.n.n.n Get Device Status

 Message type = 67

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\nobox
\--
\ n.n.n.n Device Status Data

 Message type = 68

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;00;null (separator);0
\boxline
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;response code;1;*0..3
\boxline
 ;04;device status;1;*0..15
\boxline
 ;05;device type;1;*0..10
\boxline
 ;06;file transfer status;1;*0..15
\boxline
 ;07;terminal model;1..31;ascii string
\boxline
 ;08;file acknowledge;1;boolean
\boxline
 ;09;maximum file size;4;0..99999999
\boxline
 ;10;page width;1;10..255
\boxline
 ;11;page length;1;0..176
\boxline
 ;12;banner page count;1;0..3
\boxline
 ;13;banner highlight field;1;*0..4
\boxline
 ;14;transmission block size;2;tip dependant
\boxline
 ;15;carriage control action;1;*0..2
\boxline
 ;16;forms code 1;1..6;ascii string
\boxline
 ;17;forms code 2;1..6;ascii string
\boxline
 ;18;forms code 3;1..6;ascii string
\boxline
 ;19;forms code 4;1..6;ascii string
\boxline
 ;20;ext. characteristics 1;1..6;ascii string
\boxline
 ;21;ext. characteristics 2;1..6;ascii string
\boxline
 ;22;ext. characteristics 3;1..6;ascii string
\boxline
 ;23;ext. characteristics 4;1..6;ascii string
\boxline
 ;24;suppress carriage cont.;1;0=off, 1=on
\boxline
 ;25;device alias 1;1..31;ascii string
\boxline
 ;26;device alias 2;1..31;ascii string
\boxline
 ;27;device alias 3;1..31;ascii string
\boxline
 ;28;last unsolicited message;0..255;ascii string
\boxline
 ;29;system file name;1..31;ascii string
\boxline
 ;30;user file name;1..31;ascii string
\boxline
 ;31;system job name;1..31;ascii string
\boxline
 ;32;user job name;1..31;ascii string
\boxline
 ;33;user name;1..31;ascii string
\boxline
 ;34;family name;1..31;ascii string
\boxline
 ;35;percent complete;1;0..100
\boxline
 ;36;code set;1;*0..7
\boxline
 ;37;vertical print density;1;*0..3
\boxline
 ;38;VFU Load Procedure;1..31;ascii string
\boxline
 ;39;forms size;1;1..62
\boxline
 ;40;undefined fe action;1;*0..2
\boxline
 ;41;unsupported fe action;1;*0..2
\boxline
 ;42;VFU load option;1;*0..3
\boxline
 ;43;destination name;1..31;ascii string
\boxline
 ;44;input bytes transferred;4;integer
\boxline
 ;45;logical line number;2;1..999
\boxline
 ;46;transparent mode;1;0=off, 1=on
\boxline
 ;47;skip punch count;1;0..9
\boxline
 ;48;Control Code replacement;2..128;ccr_data
\boxline
 ;49;Data Parity;1;*0..4
\boxline
 ;50;Site-defined Code Set;1..31;ascii string
\nobox
\--
\keep13
\ n.n.n.n Get Queue Status

 Message type = 69

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\nobox
\--
\keep27
\ n.n.n.n Queue Status Data

 Message type = 70

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+table;6,14,40,49
 ;01;station name;1..31;ascii string
\boxline
 ;02;no of files;8;integer
\boxline
 ;03;response code;1;*0..3
\boxline
 ;04;count of ext. chars.;8;integer
\boxline
 ;05;ext chars & status;95..100;q status data
\boxline
 ;06;count of forms codes;8;integer
\boxline
 ;07;forms code & status;95..100;q status data
\boxline
 ;08;count of devices;8;integer
\boxline
 ;09;device name & status;95..125;q status data
\boxline
 ;10;count of destinations;8;integer
\boxline
 ;11;destinations & status;95..125;q status data
\boxline
 ;12;count of device types;8;integer
\boxline
 ;13;device type & status;95..125;q status data
\nobox
\--
\keep15
\ n.n.n.n Get Queue Entry List

 Message type = 71

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+table;6,14,41,49
 ;01;station name;1..31;ascii string
\boxline
 ;02;all or top 10;1;*0..1
\boxline
 ;03;optimize queue list;1;*0..1
\nobox
\--
\keep17
\ n.n.n.n Queue Entry List Data

 Message type = 72

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;response code;1;*0..3
\boxline
 ;03;count of files;8;integer
\boxline
 ;04;system file name & prty;9..39;file priority
\nobox
\--
\keep13
\ n.n.n.n Get Queue Entry

 Message type = 73

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;system/user file name;1..31;ascii string
\nobox
\--
\ n.n.n.n Queue Entry Data

 Message type = 74

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;00;null (separator);0
\boxline
 ;01;station name;1..31;ascii string
\boxline
 ;02;system file name;1..31;ascii string
\boxline
 ;03;response code;1;*0..3
\boxline
 ;04;user file name;1..31;ascii string
\boxline
 ;05;time enqueued;8;date and time
\boxline
 ;06;position in queue;8;integer
\boxline
 ;07;priority;8;integer
\boxline
 ;08;copies;8;integer
\boxline
 ;09;creating job family name;1..31;ascii string
\boxline
 ;10;creating system job name;1..31;ascii string
\boxline
 ;11;creating user job name;1..31;ascii string
\boxline
 ;12;destination name;1..31;ascii string
\boxline
 ;13;device type;1;*0..10
\boxline
 ;14;file length;4;0..99999999
\boxline
 ;15;output data mode;1;*0..1
\boxline
 ;16;device name;1..31;ascii string
\boxline
 ;17;ext. characteristics;1..6;ascii string
\boxline
 ;18;forms code;1..6;ascii string
\boxline
 ;19;page format;1;*0..2
\nobox
\page
\box
 ;20;page length;1;0..176
\boxline
 ;21;page width;1;10..255
\boxline
 ;22;vertical print density;1;*0..7
\boxline
 ;23;VFU load procedure;1..31;ascii string
\boxline
 ;24;creating user name;1..31;ascii string
\boxline
 ;25;file transfer state;1;*0..3
\boxline
 ;26;Q entry data continues;0
\nobox
\--
\page
\ n.n Messages between SCFS/VE and the OPERATE_STATION utility
\keep27
\ n.n.n.n Position File

 Message type = 64

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;location integer;2;0..65535
\boxline
 ;04;location string 1;0..255;ascii string
\boxline
 ;05;location string 2;0..255;ascii string
\boxline
 ;06;units;1;*0..1
\boxline
 ;07;direction;1;*0..1
\boxline
 ;08;starting position;1;*0..2
\boxline
 ;09;preview line count;8;integer
\nobox
\--
\keep15
\ n.n.n.n Terminate Queued Output

 Message type = 75

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\boxline
 ;02;system/user file name;1..31;ascii string
\nobox
\--
\keep17
\ n.n.n.n Terminate Queued Output Response

 Message type = 76

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\boxline
 ;02;system/user file name;1..31;ascii string
\boxline
 ;03;response code;1;*0..5
\nobox
\--
\keep11
\ n.n.n.n Get Station Status

 Message type = 65

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\boxline
 ;02;optimize device list;1;*0..1
\nobox
\--
\keep39
\ n.n.n.n Station Status Data

 Message type = 66

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\boxline
 ;02;response code;1;*0..3
\boxline
 ;03;control facility name;1..31;ascii string
\boxline
 ;04;no. of files queued;8;integer
\boxline
 ;05;station usage;1;*0..2
\boxline
 ;06;file acknowledgement;1;0=no, 1=yes
\boxline
 ;07;count of devices;8;integer
\boxline
 ;08;device status data;4..34;dev stat data
\boxline
 ;09;required console device;1..31;ascii string
\boxline
 ;10;I/O station alias 1;1..31;ascii string
\boxline
 ;11;I/O station alias 2;1..31;ascii string
\boxline
 ;12;I/O station alias 3;1..31;ascii string
\boxline
 ;13;default job destination;1..31;ascii string
\boxline
 ;14;dest. unavail. action;1;*0..1
\boxline
 ;15;PM message action;1;*0..2
\nobox
\--
\page
\ n.n Messages between SCFS/VE and OPERATE_NTF utility
\ n.n.n.n Get Remote System Names

 Message type = 10

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;remote system name;1..31;ascii string
\boxline
 ;02;logical line number;2;1..999
\boxline
 ;03;set of remote system kind;1;set of *0..2
\nobox
\--
\keep15
\ n.n.n.n Remote System Names Data

 Message type = 11

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;response code;1;*0..3
\boxline
 ;02;count of remote systems;8;integer
\boxline
 ;03;remote system name & info;5..35;rmt sys data
\nobox
\--
\keep11
\ n.n.n.n Get Remote System Options

 Message type = 12

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;remote system name;1..31;ascii string
\nobox
\--
\keep48
\ n.n.n.n Remote System Options Data

 Message type = 13

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;remote system name;1..31;ascii string
\boxline
 ;02;response code;1;*0..3
\boxline
 ;03;control facility name;1..31;ascii string
\boxline
 ;04;remote system protocol;1;*0..1
\boxline
 ;05;authority level;1;*0..2
\boxline
 ;06;wait-a-bit;1;*0..1
\boxline
 ;07;inactivity timer;2;0..600
\boxline
 ;08;positive acknowledge;1;*0..1
\boxline
 ;09;default job destination;1..31;ascii string
\boxline
 ;10;default file destination;1..31;ascii string
\boxline
 ;11;store/forward destination;1..31;ascii string
\boxline
 ;12;count of logical lines;8;integer
\boxline
 ;13;logical line data;34..64;log line data
\boxline
 ;14;count of batch streams;8;integer
\boxline
 ;15;stream name;1..31;ascii string
\boxline
 ;16;remote system type;1;*0..5
\boxline
 ;17;route back position;1;0..255
\boxline
 ;18;request permission retry;1;0=no, 1=yes
\boxline
 ;19;local system name;1..31;ascii string
\nobox
\--
\keep16
\ n.n.n.n Delete User

 Message type = 14

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;remote system name;1..31;ascii string
\boxline
 ;03;family name;1..31;ascii string
\boxline
 ;04;user name;1..31;ascii string
\nobox
\--
\keep13
\ n.n.n.n Delete User Response

 Message type = 15

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;remote system name;1..31;ascii string
\boxline
 ;02;response code;1;*0..2
\nobox
\--
\keep15
\ n.n.n.n Get Remote System Status

 Message type = 18

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;remote system name;1..31;ascii string
\boxline
 ;02;logical line number;2;1..999
\boxline
 ;03;signon stat (dev stat);1;*7..11
\nobox
\--
\keep18
\ n.n.n.n Remote System Status Data

 Message type = 19

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;remote system name;1..31;ascii string
\boxline
 ;02;response code;1;*0..3
\boxline
 ;03;count of lines;8;integer
\boxline
 ;04;remote system status;6..36;rmt stat data
\nobox
\--
\page
\ n.n messages between SCFS/VE and multiple partners
\keep6
\ n.n.n.n Switch Control Facility

 Message type = 80

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;Connection Identifier;1..31;ascii string
\boxline
 ;02;SCFS/VE network address;12;generic sap
\nobox
\--
\page
\block,j1,i4
\ n.n Common messages between SCFS/VE, SCF/DI, and OPES
  This section describes common messages between SCFS/VE and SCF/DI and between
SCF/VE and the OPERATE_STATION utility (OPES).
\keep15
\ n.n.n.n Suppress Carriage Control Response

 Message type = 40

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;response code;1;*0..13
\nobox
\--
\keep16
\ n.n.n.n Operator Message

 Message type = 51

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;text;1..32k;ascii string
\nobox
\--
\keep15
\ n.n.n.n Suppress Carriage Control

 Message type = 43

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;suppress format control;1;0=off, 1=on
\nobox
\--
\keep17
\ n.n.n.n Position File Transfer Response

 Message type = 50

\box
\+
 ;attribute;description;length;allowed
 ;^name;;;^value
\boxline
\+
 ;01;I/O station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;response code;1;*0..13
\nobox
\--
\page
\block,j1,i4
\ n.n Common messages between SCFS/VE, SCF/DI, and OPES or OPENTF
  This section describes common messages between SCFS/VE and SCF/DI and between
SCFS/VE and the OPERATE_STATION utility (OPES) or between SCFS/VE and the
OPERATE_NTF utility (OPENTF).
\keep19
\ n.n.n.n Change Batch Device Attributes Response

 Message type = 46

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;response code;1;*0..13
\nobox


 optional - included only when changed

\box
 ;04;device alias 1;0..31;ascii string
\boxline
 ;05;device alias 2;0..31;ascii string
\boxline
 ;06;device alias 3;0..31;ascii string
\boxline
 ;07;file acknowledge;1;boolean
\boxline
 ;08;terminal model;1..31;ascii string
\boxline
 ;09;transmission block size;2;tip dependant
\boxline
 ;10;maximum file size;4;0..99999999
\boxline
 ;11;page width;1;10..255
\boxline
 ;12;page length;1;0..176
\boxline
 ;13;banner page count;1;0..3
\boxline
 ;14;banner highlight field;1;*0..4
\boxline
 ;15;carriage control action;1;*0..2
\boxline
 ;16;forms code 1;0..6;ascii string
\boxline
 ;17;forms code 2;0..6;ascii string
\boxline
 ;18;forms code 3;0..6;ascii string
\boxline
 ;19;forms code 4;0..6;ascii string
\boxline
 ;20;external device char. 1;0..6;ascii string
\boxline
 ;21;external device char. 2;0..6;ascii string
\boxline
 ;22;external device char. 3;0..6;ascii string
\boxline
 ;23;external device char. 4;0..6;ascii string
\boxline
 ;24;code set;1;*0..7
\boxline
 ;25;vertical print density;1;*0..3
\boxline
 ;26;VFU Load Procedure;1..31;ascii string
\boxline
 ;27;forms size;1;1..62
\boxline
 ;28;undefined fe action;1;*0..2
\boxline
 ;29;unsupported fe action;1;*0..2
\boxline
 ;30;invalid attribute;1;*0..30
\boxline
 ;31;skip punch count;1;0..9
\boxline
 ;32;Control Code replacement;2..128;ccr_data
\boxline
 ;33;Data Parity;1;*0..4
\boxline
 ;34;Site-defined Code Set;1..31;ascii string
\nobox
\--
\keep13
\ n.n.n.n Start Batch Device

 Message type = 41

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\nobox
\--
\keep13
\ n.n.n.n Stop Batch Device

 Message type = 42

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;file disposition;1;*0..4
\nobox
\--
\keep16
\ n.n.n.n Terminate Transfer

 Message type = 44

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;file disposition;1;*0..2
\nobox
\--
\keep15
\ n.n.n.n Change Batch Device Attributes

 Message type = 45

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\nobox

 optional - included only when changed

\box
 ;03;device alias 1;0..31;ascii string
\boxline
 ;04;device alias 2;0..31;ascii string
\boxline
 ;05;device alias 3;0..31;ascii string
\boxline
 ;06;file acknowledge;1;boolean
\boxline
 ;07;terminal model;1..31;ascii string
\boxline
 ;08;transmission block size;2;tip dependant
\boxline
 ;09;maximum file size;4;0..99999999
\boxline
 ;10;page width;1;10..255
\boxline
 ;11;page length;1;0..176
\boxline
 ;12;banner page count;1;0..3
\boxline
 ;13;banner highlight field;1;*0..4
\boxline
 ;14;carriage control action;1;*0..2
\boxline
 ;15;forms code 1;0..6;ascii string
\boxline
 ;16;forms code 2;0..6;ascii string
\boxline
 ;17;forms code 3;0..6;ascii string
\nobox
\page
\box
 ;18;forms code 4;0..6;ascii string
\boxline
 ;19;external device char. 1;0..6;ascii string
\boxline
 ;20;external device char. 2;0..6;ascii string
\boxline
 ;21;external device char. 3;0..6;ascii string
\boxline
 ;22;external device char. 4;0..6;ascii string
\boxline
 ;23;code set;1;*0..7
\boxline
 ;24;vertical print density;1;*0..3
\boxline
 ;25;VFU Load Procedure;1..31;ascii string
\boxline
 ;26;forms size;1;1..62
\boxline
 ;27;undefined fe action;1;*0..2
\boxline
 ;28;unsupported fe action;1;*0..2
\boxline
 ;29;skip punch count;1;0..9
\boxline
 ;30;Control Code replacement;2..128;ccr_data
\boxline
 ;31;Data Parity;1;*0..4
\boxline
 ;32;Site-defined Code Set;1..31;ascii string
\nobox
\--
\keep17
\ n.n.n.n Start Batch Device Response

 Message type = 47

\box
\+
 ;attribute;description;length;allowed
 ;^name;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;response code;1;*0..13
\nobox
\--
\keep17
\ n.n.n.n Stop Batch Device Response

 Message type = 48

\box
\+
 ;attribute;description;length;allowed
 ;^name;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;response code;1;*0..13
\nobox
\--
\keep17
\ n.n.n.n Terminate Transfer Response

 Message type = 49

\box
\+
 ;attribute;description;length;allowed
 ;^name;;;^value
\boxline
\+
 ;01;station name;1..31;ascii string
\boxline
 ;02;device name;1..31;ascii string
\boxline
 ;03;response code;1;*0..13
\nobox
\--
\page
\block,j1,i4
\ n.n Common messages between SCFS/VE, SCF/DI, and OPENTF
  This section describes common messages between SCFS/VE and SCF/DI and between
SCFS/VE and the OPERATE_NTF utility (OPENTF).
\keep17
\ n.n.n.n Send Remote Command

 Message type = 16

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;remote system name;1..31;ascii string
\boxline
 ;02;stream name;1..31;ascii string
\boxline
 ;03;logical line number;2;1..999
\boxline
 ;04;command type;1;*0..6
\boxline
 ;05;command text;1..255;ascii string
\nobox
\--
\keep15
\ n.n.n.n Send Remote Command Response

 Message type = 17

\box
\+
 ;attribute;description;length;allowed
 ;^number;;;^value
\boxline
\+
 ;01;remote system name;1..31;ascii string
\boxline
 ;02;stream name;1..31;ascii string
\boxline
 ;03;command type;1;*0..6
\boxline
 ;04;device status;1;*0..15
\boxline
 ;05;response code;1;*0..3
\nobox
\--
\page
\block,j1,i4
\ n.0 Position File Parameter Format
 This section describes the format of the parameters for the Position File
message sent to SCF/DI to be eventually passed on to BTF/VE. These
parameters will form a data block that SCF/DI will pass on to BTF/VE. The
format of the data will be the A-A 56 parameter.

 The block passed to SCF/DI is defined as:
\asis
  <CCC AA......AA>

  This is all character data where:

      CCC = 001
      AAA =
          Location Count    = <01 LLL II..II> where:
              LLL           = length of II..II
              II..II        = count

          Location String 1 = <02 LLL SS..SS> where:
              LLL           = length of SS..SS
              SS..SS        = location string

          Location String 2 = <03 LLL SS..SS> where:
              LLL           = length of SS..SS
              SS..SS        = location string

          Units             = <04 LLL X> where:
              LLL           = 001
              X             = L (for lines)
                              P (for pages)

          Direction         = <05 LLL X> where:
              LLL           = 001
              X             = F (for forward)
                              B (for backward)
\page
\asis
          Start position    = <06 LLL X> where:
              LLL           = 001
              X             = E (for end of file)
                              B (for beginning of file)
                              L (for current line)

          Preview           = <07 LLL X> where:
              LLL           = 001
              X             = 0 .. 9
\block,j1,i4
\ n.0 Response codes
 This section details response codes for all response messages.
\ n.n.n.n Add I/O Station Response Codes
\+flowtab;10,17
 ;~Value~;~Meaning~

 ;0;message accepted
 ;1;duplicate definition with Check IOS Unique set to true
 ;2;duplicate definitions do not match
 ;3;duplicate alias names specified in message
 ;4;duplicate station name within domain
\-
\ n.n.n.n Delete I/O Station Response Codes
\+
 ;~Value~;~Meaning~

 ;0;message accepted
 ;1;no io station found with specified name
\-
\ n.n.n.n Add Remote System Response Codes
\+flowtab;10,17
 ;~Value~;~Meaning~

 ;0;message accepted
 ;1;duplicate definitions do not match
 ;2;duplicate logical line number
 ;3;duplicate remote system name within domain
 ;4;remote system name not found in NTF System List
\-
\ n.n.n.n Add Accessible Remote System Response Codes
\+
 ;~Value~;~Meaning~

 ;0;message accepted
 ;1;no remote system found with specified name
 ;2;no remote system found with specified logical line number
 ;3;duplicate definitions do not match
 ;4;remote system name not found in NTF System List
\-
\ n.n.n.n Delete Remote System Response Codes
\+
 ;~Value~;~Meaning~

 ;0;message accepted
 ;1;no remote system found with specified name
\-
\ n.n.n.n Add Batch Device Response Codes
\+
 ;~Value~;~Meaning~

 ;0;message accepted
 ;1;no io station or remote system found with specified name
 ;2;duplicate batch device or batch stream name
 ;3;duplicate alias names specified in message
\-
\ n.n.n.n Delete Batch Device Response Codes
\+
 ;~Value~;~Meaning~

 ;0;message accepted
 ;1;no io station or remote system found with specified name
 ;2;no batch device or batch stream found with specified name
\-
\keep9
\ n.n.n.n Add User Response Codes
\+
 ;~Value~;~Meaning~

 ;0;message accepted
 ;1;no io station or remote system found with specified name
 ;2;operator already assigned to station or remote system
 ;3;operator device does not match required operating device
\-
\ n.n.n.n Send Remote Command Response Codes
\+
 ;~Value~;~Meaning~

 ;0;message accepted
 ;1;incorrect signon status for remote system
 ;2;no remote system found with specified name
 ;3;no batch stream found with specified name
\-
\block,j1,i4
\ n.n.n.n Device Control Response Codes
  Response codes for the Start Batch Device Response, Stop Batch Device
Response, Terminate Transfer Response, Suppress Carriage Control Response,
Position File Transfer Response and Change Batch Device Attributes Response
messages.

\+flowtab;10,17
 ;~Value~;~Meaning~

 ;0;command accepted
 ;1;command rejected, BTFS/DI down
 ;2;command rejected, unknown I/O station or remote system
 ;3;command rejected, unknown device or batch stream
 ;4;command rejected, wrong device or stream type
 ;5;command rejected, wrong data mode
 ;6;message rejected, device cannot support the specified VFU
 ;7;message rejected, VFU load request outstanding
 ;8;message rejected, VFU load procedure could not be found
 ;9;message rejected, syntax error in VFU load procedure
 ;10;message rejected, VFU not changeable by the operator
 ;11;message rejected, terminal model is undefined
 ;12;message rejected, device busy, new VFU is not allowed
 ;13;message rejected, insufficient memory in DI for request
 ;14;message rejected, TIP rejected attribute
 ;15;message rejected, code set load procedure not found
\-
\block,j1,i4
\ n.n.n.n File Assignment Response Codes

\+flowtab;10,17
 ;~Value~;~Meaning~

 ;0;command accepted
 ;1;command rejected
 ;2;command rejected, cannot translate BTFS/DI title
\-
\block,j1,i4
\ n.n.n.n Select File Response Codes

\+flowtab;10,17
 ;~Value~;~Meaning~

 ;0;command accepted
 ;1;command rejected, unknown I/O station or remote system
 ;2;command rejected, unknown device or batch stream
 ;3;command rejected, unknown file
 ;4;command rejected, file already assigned
 ;5;command rejected, wrong device or stream type
 ;6;command rejected, file name not unique
\-
\block,j1,i4
\ n.n.n.n Display Status Response Codes

\+flowtab;10,17
 ;~Value~;~Meaning~

 ;0;command accepted
 ;1;command rejected, unknown I/O station or remote system
 ;2;command rejected, unknown device or batch stream
 ;3;command rejected, unknown file
\-
\block,j1,i4

 These response codes are used for the following messages:  Station
Status Data, Device Status Data, Queue Status Data, Queue Entry List
Data, Queue Entry Data, Remote System Names Data, Remote System Options
Data and Remote System Status Data.
\ n.n.n.n Delete User Response Codes
\+
 ;~Value~;~Meaning~

 ;0;message accepted
 ;1;no remote system found with specified name
 ;2;operator not assigned to remote system
\-
\ n. assorted field codes
 This section details codes for all coded fields in attribute value
descriptors.
\ n.n.n.n Accept Messages
\+
 ;~Value~;~Meaning~

 ;0;Do accept unsolicited messages
 ;1;Do not accept unsolicited messages
\-
\ n.n.n.n Action Required Codes
\+flowtab;10,17
 ;~Value~;~Meaning~

 ;0;add entry
 ;1;modify entry
 ;2;delete entry
\-
\ n.n.n.n BTF/VE Protocol Stacks
\+
 ;~Value~;~Meaning~

 ;1;XNS Protocol Stack
 ;2;OSI Protocol Stack
 ;3;XNS and OSI Protocol Stacks
 ;4-255;Reserved
\-
 NOTE: These values are derived from bit positions, they do not
represent an ordinal list.

\ n.n.n.n BTFS/DI Advanced Features
\+
 ;~Value~;~Meaning~

 ;0;No advanced features
 ;1;Transparent mode allowed for TIP type of URI.
 ;2-255;Reserved
\-
\ n.n.n.n BTFS/DI Status Codes
\+
 ;~Value~;~Meaning~

 ;0;BTFS/DI down
 ;1;BTFS/DI active
\-
\ n.n.n.n Carriage Control Action Codes
\+
 ;~Value~;~Meaning~

 ;0;pre print
 ;1;post print
 ;2;pre and post print
\-
\ n.n.n.n Connection Type Codes
\+
 ;~Value~;~Meaning~

 ;0;Cyber 180 connection
 ;1;Cyber 170 connection
\-
\ n.n.n.n Device Status Codes
\+
 ;~Value~;~Meaning~

 ;0;Active
 ;1;Stopped (disabled)
 ;2;Not ready
 ;3;Down
 ;4;VFU procedure being loaded
 ;5;VFU procedure not loadable
 ;6;Stopped by system
 ;7-10;Reserved
 ;11;Waiting for signon (NTF only)
 ;12;Signon initiated (NTF only)
 ;13;Signed on (NTF only)
 ;14;Signon failed (NTF only)
 ;15;Signed off (NTF only)
\-
\ n.n.n.n Device Type Codes
\+
 ;~Value~;~Meaning~

 ;0;Null Device
 ;1;Console
 ;2;Reader
 ;3;Printer
 ;4;Punch
 ;5;Plotter
 ;6;Remote System Input
 ;7;Job Receiver
 ;8;Sysout Receiver
 ;9;Job Transmitter
 ;10;Sysout Transmitter
\-
\ n.n.n.n File Disposition Codes
\block,j1,i4
 These disposition codes are for the Stop Batch Device, Stop Device, and
Terminate Transfer messages. The Terminate Transfer messages will use only
the first 3 codes.

\+

 ;~Value~;~Meaning~

 ;0;Requeue
 ;1;Drop
 ;2;Hold
 ;3;Finish
 ;4;Suspend
\-
\ n.n.n.n File Transfer State Codes
\+
 ;~Value~;~Meaning~

 ;0;File is eligible to transfer
 ;1;File is on hold
 ;2;File is not eligible to transfer
 ;3;File is selected to transfer
\-
\ n.n.n.n File Transfer Status Codes
\+
 ;~Value~;~Meaning~

 ;0;Idle (file transfer complete)
 ;1;Idle, device disconnected
 ;2;Idle, vfu not loadable
 ;3;Idle, transfer error (DI or HOST)
 ;4;Idle, accounting limit exceeded
 ;5;Idle, operator dropped file
 ;6;Idle, operator requeued file
 ;7;Idle, operator hold file
 ;8;Busy (file transfer started)
 ;9;Suspended, device not ready (file transfer busy)
 ;10;Suspended, PM message (file transfer busy)
 ;11;Suspended, operator command (file transfer busy)
 ;12;Suspended, operator position file (file transfer busy)
 ;13;Suspended, VFU procedure being loaded
 ;14;Reserved for other busy conditions
 ;15;Reserved for other busy conditions
\-
\ n.n.n.n Job Destination Unavailable Action Codes
\+
 ;~Value~;~Meaning~

 ;0;Stop I/O station
 ;1;Drop job
\-
\ n.n.n.n Job State Codes
\+
 ;~Value~;~meaning~

 ;0;input queue
 ;1;executing
 ;2;output queue
\-

\ n.n.n.n Optimization Request Codes
\+
 ;~Value~;~meaning~

 ;0;do not optimize
 ;1;do optimize
\-

\ n.n.n.n Output Data Mode Codes
\+
 ;~Value~;~Meaning~

 ;0;coded mode
 ;1;transparent mode
\-
\ n.n.n.n Output State Codes
\+
 ;~Value~;~Meaning~

 ;0;eligible for selection
 ;1;hold
 ;2;not eligible for selection
 ;3;selected
 ;4;completed
\-
\ n.n.n.n Page Format Codes
\+
 ;~Value~;~Meaning~

 ;0;continuous (not paged)
 ;1;burstable (paged)
 ;2;not burstable (paged)
\-
\ n.n.n.n Position Direction Codes
\+
 ;~Value~;~Meaning~

 ;0;forward
 ;1;backward
\-
\ n.n.n.n Position Units Codes
\+
 ;~Value~;~Meaning~

 ;0;lines
 ;1;pages
\-
\ n.n.n.n Starting Position Codes
\+
 ;~Value~;~Meaning~

 ;0;top of file
 ;1;bottom of file
 ;2;last line printed
\-
\ n.n.n.n Station Usage Codes
\+
 ;~Value~;~Meaning~

 ;0;public
 ;1;private
 ;2;NTF
\-
\ n.n.n.n Banner Highlight Field Codes
\+
 ;~Value~;~Meaning~

 ;0;comment banner
 ;1;routing banner
 ;2;site banner
 ;3;user file name
 ;4;user name
\-
\keep12
\ n.n.n.n Code Set Codes
\+
 ;~Value~;~Meaning~

 ;0;ASCII
 ;1;ASCII 48
 ;2;ASCII 64
 ;3;ASCII 95
 ;4;ASCII 128
 ;5;EBCDIC
 ;6;ASCII 256
 ;7;BCD (Mode 4)
 ;8;Defined by site, indicates use of site-defined code set parameter
\-
\keep8
\ n.n.n.n VFU Load Option Codes
\+
 ;~Value~;~Meaning~

 ;0;NONE - VFU not present or not loadable
 ;1;INIT - VFU loaded during initialization
 ;2;OPER - VFU changeable by operator
 ;3;USER - VFU changeable by operator or user
\-
\keep7
\ n.n.n.n Format Effector Action Codes
\+
 ;~Value~;~Meaning~

 ;0;PAS - print after spacing
 ;1;PBS - print before spacing
 ;2;DIS - discard print line
\-
\keep10
\ n.n.n.n Vertical Print Density Codes (device attribute)
\+
 ;~Value~;~Meaning~

 ;0;six only - device only capable of printing 6 lines/inch
 ;1;eight only - device only capable of printing 8 lines/inch
 ;2;six any - device capable of printing 6 or 8 lines/inch
but defaulting to 6 if user does not care
 ;3;eight any - device capable of printing 6 or 8 lines/inch
but defaulting to 8 if user does not care

\-
\ n.n.n.n Vertical Print Density Codes (output file attribute)
\+
 ;~Value~;~Meaning~

 ;0;none - the device vertical print density will be used
 ;1;6 lines per inch
 ;2;7 lines per inch
 ;3;8 lines per inch
 ;4;9 lines per inch
 ;5;10 lines per inch
 ;6;11 lines per inch
 ;7;12 lines per inch
\-
\keep7
\ n.n.n.n PM Message Action Codes
\+
 ;~Value~;~Meaning~

 ;0;print PM message
 ;1;display PM message to operator
 ;2;discard PM message
\-
\ n.n.n.n Tip Type Codes
\+
 ;~Value~;~Meaning~

 ;0;internal tip
 ;1;auto tip
 ;2;async tip
 ;3;user1 tip
 ;4;user2 tip
 ;5;user3 tip
 ;6;user4 tip
 ;7;hasp tip
 ;8;x25 async tip
 ;9;bisync 3270 tip
 ;10;bisync njef tip
 ;11;remote term emulator tip
 ;12;uri tip
 ;13;xpc tip
 ;14;mode4 tip
 ;15;ntf tip
 ;16;sna 3270 tip
 ;17;telnet tip
\-
\ n.n.n.n Data Parity Codes
\+
 ;~Value~;~Meaning~

 ;0;Zero
 ;1;Mark
 ;2;Even
 ;3;Odd
 ;4;None
\-
\ n.n.n.n Remote System Protocol Codes
\+
 ;~Value~;~Meaning~

 ;0;NJE
 ;1;HASP
\-
\ n.n.n.n Remote System Authority Level Codes
\+
 ;~Value~;~Meaning~

 ;0;NONE
 ;1;NET
 ;2;JOB
\-
\ n.n.n.n Remote System Wait-a-Bit Codes
\+
 ;~Value~;~Meaning~

 ;0;ACK
 ;1;FCS
\-
\ n.n.n.n Remote System Positive Acknowledge Codes
\+
 ;~Value~;~Meaning~

 ;0;ACK
 ;1;NULL
\-
\ n.n.n.n Remote System Kind Codes
\+
 ;~Value~;~Meaning~

 ;0;Not configured
 ;1;Directly Connected
 ;2;Accessible
\-
\ n.n.n.n Remote System Type Codes
\+
 ;~Value~;~Meaning~

 ;0;NOS/VE
 ;1;NOS
 ;2;NOS/BE
 ;3;IBM
 ;4;DEC
 ;5;User
 ;6;CYBER 205
 ;7;ETA
 ;8;Cray
\-
\ n.n.n.n Remote System Command Type Codes
\+
 ;~Value~;~Meaning~

 ;0;Command
 ;1;Message
 ;2;Signon
 ;3;Signoff
 ;4;TDP
 ;5;Broadcast
 ;6;Operator
\-
\ n.n.n.n Terminate Queued Output Response Codes
\+
 ;~Value~;~Meaning~

 ;0;Successful
 ;1;Unknown I/O Station
 ;2;Unknown File Name
 ;3;Duplicate File Names
 ;4;File Being Transferred
 ;5;Message Rejected
\-
\block,j1,i4
\ n.0 command message type tables
 This section presents consolidated lists of message type codes to
message name cross references. One list is presented in message type sequence
and one in message name sequence.
\ n.n message type sequence
\box,1,16,62
\table;3,18
 ;Message type;Message Name
\boxline
\table;8,18
 ;01;Add File Availability
 ;02;Modify File Availability
 ;03;Delete File Availability
 ;04;File Assignment
 ;05;File Assignment Response
 ;06;Delete Destination
 ;07;BTF/VE Status
 ;09;Add Accessible Remote System Response
 ;10;Get Remote System Names
 ;11;Remote System Names Data
 ;12;Get Remote System Options
 ;13;Remote System Options Data
 ;14;Delete User
 ;15;Delete User Response
 ;16;Send Remote Command
 ;17;Send Remote Command Response
 ;18;Get Remote System Status
 ;19;Remote System Status Data
 ;20;Add I/O Station
 ;21;Delete I/O Station
 ;22;Add Batch Device
 ;23;Batch Device Status
 ;24;File Status
 ;25;Delete Batch Device
 ;26;BTFS/DI Status
 ;27;Add I/O Station Response
 ;28;Delete I/O Station Response
 ;29;Start I/O Station
 ;30;Stop I/O Station
 ;31;Switch Control (to SCF/DI)
 ;32;Position File Transfer (to SCF/DI)
 ;33;Add Batch Device Response
 ;34;Delete Batch Device Response
 ;35;Add Remote System
 ;36;Add Accessible Remote System
\nobox
\page
\box
 ;37;Delete Remote System
 ;38;Add Remote System Response
 ;39;Delete Remote System Response
 ;40;Suppress Carriage Control Response
 ;41;Start Batch Device
 ;42;Stop Batch Device
 ;43;Suppress Carriage Control
 ;44;Terminate Transfer
 ;45;Change Batch Device Attribute
 ;46;Change Batch Device Attributes Response
 ;47;Start Batch Device Response
 ;48;Stop Batch Device Response
 ;49;Terminate Transfer Response
 ;50;Position File Transfer Response
 ;51;Operator Message
 ;60;Add User
 ;61;Add User Response
 ;62;Select File
 ;63;Select File Response
 ;64;Position File (from OPES)
 ;65;Get Station Status
 ;66;Station Status Data
 ;67;Get Device Status
 ;68;Device Status Data
 ;69;Get Queue Status
 ;70;Queue Status Data
 ;71;Get Queue Entry List
 ;72;Queue Entry List Data
 ;73;Get Queue Entry
 ;74;Queue Entry Data
 ;75;Terminate Queued Output
 ;76;Terminate Queued Outupt Response
 ;80;Switch Control
\nobox
\page
\ n.n command message name sequence
\box,1,16,62
\table;3,18
 ;Message type;Message Name
\boxline
\table;8,18
 ;36;Add Accessible Remote System
 ;09;Add Accessible Remote System Response
 ;22;Add Batch Device
 ;33;Add Batch Device Response
 ;01;Add File Availability
 ;20;Add I/O Station
 ;27;Add I/O Station Response
 ;35;Add Remote System
 ;38;Add Remote System Response
 ;60;Add User
 ;61;Add User Response
 ;23;Batch Device Status
 ;07;BTF/VE Status
 ;26;BTFS/DI Status
 ;45;Change Batch Device Attribute
 ;46;Change Batch Device Attribute Response
 ;25;Delete Batch Device
 ;34;Delete Batch Device Response
 ;06;Delete Destination
 ;03;Delete File Availability
 ;21;Delete I/O Station
 ;28;Delete I/O Station Response
 ;37;Delete Remote System
 ;39;Delete Remote System Response
 ;14;Delete User
 ;15;Delete User Response
 ;68;Device Status Data
 ;04;File Assignment
 ;05;File Assignment Response
 ;24;File Status
 ;67;Get Device Status
 ;73;Get Queue Entry
 ;71;Get Queue Entry List
 ;69;Get Queue Status
 ;10;Get Remote System Names
 ;12;Get Remote System Options
 ;18;Get Remote System Status
 ;65;Get Station Status
 ;03;Modify File Availability
 ;51;Operator Message
 ;64;Position File (from OPES)
 ;32;Position File Transfer (to SCF/DI)
 ;50;Position File Transfer Response
\nobox
\page
\box
 ;74;Queue Entry Data
 ;72;Queue Entry List Data
 ;70;Queue Status Data
 ;11;Remote System Names Data
 ;13;Remote System Options Data
 ;19;Remote System Status Data
 ;62;Select File
 ;63;Select File Response
 ;16;Send Remote Command
 ;17;Send Remote Command Response
 ;41;Start Batch Device
 ;47;Start Batch Device Response
 ;29;Start I/O Station
 ;66;Station Status Data
 ;42;Stop Batch Device
 ;48;Stop Batch Device Response
 ;30;Stop I/O Station
 ;43;Suppress Carriage Control
 ;40;Suppress Carriage Control Response
 ;80;Switch Control
 ;31;Switch Control (to SCF/DI)
 ;75;Terminate Queued Output
 ;76;Terminate Queued Outupt Response
 ;44;Terminate Transfer
 ;49;Terminate Transfer Response
\nobox
\title2=
