Sample DOS/VS Directory Entries
The following directory entries represent some batch type virtual
.achines that can be used to run production jobs under DOS and DOS/VS. The operands specified on the OPTION control statement reflect the
requirements cf the particular syste. being used. Disk space can either te dedicated cr shared with other systems. USER DOSUSER PASSWORD 256K ACCOUNT ACCTNO BIN3 IPL 350 OPTION ACCT CONSOLE 01F 3215 SPOOL OOB 2501 SPOOL OOC 2540 R SPOOL OOD 2540 P SPOOL OOE 1403 KDISK 350 3330 101 30 OSDOSl KDISK 351 3330 1 20 UDISK1 W USER DOSVUSER PASSWORD 512K ACCOUNT ACCTNO BIN4 IPL 350 OPTION ECKODE CONSOLE 01F 3215 SPOOL 012 3505 SPOOL 013 3525 SPOOL 002 3211
LINK VKSYS 190 190 RR W KDISK 191 3330 11 10 UDISKA VR RPASS WPASS KDISK 350 3330 100 50 VOSDOS W KDISK 351 3330 21 30 UDISKl W Accessing DOS/VS This topic assumes that DOS/VS for use under VK/370 has already been
generated and that the system residence volume is available on a real
disk or minidisk in read/write status. A user can make the system residence vclume available in anyone of these ways: • Define the DOS/VS system residence as a read/write disk in the VK/370 directory entry for the userid running DOS/VS. A typical directory
entry might lcok like the following: KDISK 250 3330 101 50 VDOSYS KR RPASS WPASS • Link to the DOS/VS system residence volume using the LINK command.
For example, if the DOS/VS system residence is on the 150 disk in the
directory entry for the userid DOSRES, a user could enter:
link dosres 150 250 w wpass
82 IBM VM/370 Operating Systems in a Virtual Machine

April 1, 1981 • Have the VM/370 system operator attach the DOS/VS system residence
directly to a userid, for that user's exclusive use. When the
operator (or another user with Class B command privileges) attaches
the disk to one user, no one else may access the volume. All of the console logs and command examples in this section
assume that a DOS/VS system residence is attached to the virtual machine
at virtual address 250. SHARING THE DOS/VS SYSTEM RESIDENCE VOLUME If VSAM is used, only one user at a time may access the DOS/VS system
residence volume in read/write status. This requirement is necessary
because only one user can update the VSAM catalog and the label
information cylinder. DOS/VS uses this cylinder to keep a record of
volumes and files needed by programs that are running.
However, if VSAM is not used and a user wants to share the DOS/VS system residence volume, set up a read/write core image library for
link-editing. Then, share the SYSRES libraries in read-only status with
other users. This method is acceptable under one of these two
conditions: • Some action has been taken by the installation to provide individual
standard label cylinders for each userid that accesses DOS/VS. • --or--
Different virtual machines use
one virtual machine uses BG and
F1, F2, and F3.
different partitions. For example,
F4, and another virtual machine uses
Another method for sharing DOS/VS is for a user to have his own
read/write copy of the system residence volume. Then, this user can
share this volume with others in read-only status and share the private
libraries with other users. STANDARD LABEL CYLINDER To share DOS/VS among virtual machines when unique partitions are DQ! assigned to each virtual machine, a user must provide a unique standard
label cylinder for each such virtual DOS/VS user. When using DOS/VSE with the VSE/Advanced Functions Program Product (5746-XE8), a user can separate label information areas and use a name
to access each area. While users must create these areas on the system
residence volume, they don't have to (as in DOS/VS Release 34 and
earlier releases): • Place label information areas at the end of the volume, following the
normal standard label cylinder • Modify the IPL communication routines • Bypass the $JOBCTLA procedure
section 3. DOS/VS in a Virtual Machine 83