March 3, 1980 Planning Considerations for Other Virtual Machines
The RSeS Virtual Machine
The Remote Spooling Communications Subsystem (RSCS), operating in a
virtual machine, handles the transmission of files between VM/370 users
and remote terminals and stations. Figure 4 illustrates a typical RSCS co nfigura tion.
Three lines of the real 3705, operating in 2703 emulation mode, are
shown dedicated to the RSCS virtual machine. The communication lines are
shown attached to a 3780 Data Communication Terminal, a System/3, and an as/HASP processor running in a remote System/360 or System/370. The RSCS machine uses the spooling facilities of VM/370 as the
interface between virtual users and itself. Any user who wishes to have
an output file transmitted to a remote location must associate tag
information (such as destination and priority) with his file via the TAG command and spool the file to the RSCS machine's virtual reader. RSCS analyzes the tag data, enables the appropriate line, and transmits the
data using the line protocol required by the receiving station.
Remote locations can submit card files to the RSCS machine and
address them to either a VK/370 user or to RSCS itself for transmission
to another remote station. RSCS produces a VM/370 spool file by writing
that data to virtual unit record devices and, if the file is destined
for a VM/370 user, sends it to the user's virtual reader via the CP SPOOL command. If the file is addressed to RSCS, it is queued on RSCS's virtual reader and then handled in the same manner as a file spooled to RSCS by a VM/370 user. In this case, it is the responsibility of the
remote station that originated the data to supply the tag information. RSCS can also function as a remote workstation of a HASP/ASP type
batch processor. VM/370 users and remote stations can submit jobs to RSCS for transmission to the HASP system. After processing, HASP can
return printed and/or punched output to RSCS for spooling to the real
system printer or punch. For more information about RSCS, see the RSCS PLANNING CONSIDERATIONS All
tape.
the files you need to generate RSCS are on the RSCS/IPCS Before you perform the RSCS generation procedure, be sure you have a
virtual machine defined for RSCS. The virtual machine you intend to run RSCS should have: 512K of virtual storage A reader A ccnsole A minidisk for the RSCS system residence volume. The RSCS system
disk must have a write password. See the section "Defining Your R SCS Virtual Machine" in Part 3 .• You can define more than one RSCS virtual machine. Also, you can
have more than one RSCS virtual machine running at the same time.
However, when multiple RSCS virtual machines are running at the same
time, each must have a unique user identification (userid) and local
location identification (ID=linkid).
Part 1. Planning for System Generation 41
Page of GC20-1801-10 As Updated March 3, 1980 by TNL GN25-0776
Planning Considerations for Other Virtual Machines
System/370 VMl RSCS I I Control Proqram of VM/370 Virtual Virtual Virtual 2703 2703
2703 I I I Real 3705 (in 2703 EP Mode) I I j Data Data Data
Set Set Set J. .L 1 T T T
Data Data Data
Set Set Set I I I 3780
System/3
as/HASP
Processor
Figure 4. A Remote Spooling Communications Subsystem When you code the GENLINK macros during the RSCS generation
procedure, you must code the local location identification on the first
GENLINK macro.
Information about generating and installing RSCS is in "Part 3.
Generating VM/370 (CP, CMS, RSCS and IPcs).n VM/370 Using Channel Switching
The two-or
environments:
four-channel switch can be used in the following Two processors, one running VM/370 and the other running an operating
system that supports channel switching. I. Two virtual machines running under VM/370; each virtual machine I operating system must support the channel switch feature (eMS does I not).
42 IBM VM/370 Planning and System Generation Guide
Previous Page Next Page