ftarcb 30, 1979
122.16 IB! Vft/370 efts User's Guide

Pg. of GC20-1819-2 Rev March 30, 1979 by SUppa SD23-9024-1 for 5748-118 The CMS disk files created are always in unblocked, 80-character for.at. IEHMOYE: OS unloaded partitioned data sets on tapes created by the lEHMOYE utility program can be read either by the TAPPDS command or by
the TAPEMAC command. The TAPPDS command creates an individual CMS file from each member of the PDS. If the PDS is a macro library, you can use the TAPEMAC command to
copy it into a CMS MACLIB. A MACLIB, a macro library, has a special
format and can usually be created only by using the CMS MACLIB command.
If you use the TAPPDS command, you have to use the MACLIB command to
create the macro library from individual files containing macro
definitions. SPECIFYING SPECIAL TAPE HANDLING OPTIONS For most of the tape handling that you do in eMS, you do not have to be
concerned with the density or recording format of the magnetic tapes
that you use. There are, however, some instances when it may be
important and there are command options that you can use with the TAPE command MODESET operand and with ASSGN and FILEDEF command options.
The specific situations and the command options you should use are
listed below. • If you are reading or writing a 7-track tape and the density of the
tape is either 200 or 556 bpi, you must specify DEN 200 or DEN 556. • If you are reading or writing a 7-track tape with a density of 800 bpi, you must specify 7TRACKa • If you are reading or writing a 7-track tape without using the data
convert feature, you must use the TRTCH option. • If you are writing a tape using a 9-track dual density tape drive
with the 9TRACK option specified, and you want the density to be 800 (on an 800/1600 drive) or 6250 (on a 1600/6250 drive), then you must
specify DEN 800 or DEN 6250. I • If you are writing a tape, the default tape block size is 4096 bytes
plus a 5-byte header. This format is not compatible with previous YM/370 systems. Therefore, if you want to write a tape compatible
with previous YM/370 systems, you must use the 'BLK 800' option of
the TAPE command. The TAPE command is described in detail in !ALJIQ Using the Remote Spooling Communications
Subsystem (RSCS) If your VM/370 installation is on a Remote Spooling Communications Subsystem (RSCS) network, you can send printer, punch, or reader spool
files to users at remote locations. To send a spool file, you must know
the userid of the virtual machine at your location that is running RSCS and the location identification (locid) of the remote location. If you
are sending a spool file to a particular user at the remote location,
you should also know that userid of the user.
The CP commands that you can use to transmit files across the network
are TAG and SPOOL. The TAG command allows you to specify the locid and
userid that are to receive a spool file, or, in the case of tagging a
Section 7. Using Real Printers, Punches, Readers, and Tapes 123