TAPPOS TAPPDS Use the TAPPDS command to create eMS disk files from tapes that are used
as in pat to or outpat from the following as utility programs: • IEBPTPCH tape files must be the
operation from either a
set in as. The default
have been issued:
result of an IEBPTPCH punch
sequential or partitioned data
attributes (IEBPTPCH DCB) must
DCB=(RECFM=FA,LRECL=81,BLKSIZE=81) I • IEBUPOTE -- tape files may be blocked or unblocked and must be in the
format accepted by IEBUPDTE as "control data set" (SYSIN) input with a control statement
./ ADD ••• preceding the records to be placed in each partitioned
data set member (OS) or separate CMS file • IEHMOVE unloaded partitioned data sets are read. Tne tape can contain as standard labels or be unlabeled. The format
of the TAPPDS command is:
r I r r r ", I TAPPOS I fn I ft I fm II I [(opt ions ••• [) ]]
1 I I I I I I I I I I I L- I * I * 111111 , I 1* II I L L L .J.J.J
r , QBi!2n2= IPDS I INOPDS I IUPDATEI L .J
r , ,END I I NOENDI L .J
r , ,COL1 I L J
r , IMAXTEN I IJ!Q!1!KIE!!1 L J
r , I TAPnl IIAPll L J
fn is the filename of the disk file to be created from the sequential
tape file. If the tape contains members of a partitioned data set (POS), fn must be specified as an asterisk (*); one file is created foe each member with a filename the same as the member name. If NOPDS or UPDATE is specified and you do not specify fn or specify
it as an asterisk (*), the default filename is TAPPDS. ft is the filetype of the newly created files. The default filetypes ar-e CMSUT1 (for PDS or NOPDS) and ASSEMBLE (for UPDATE). The
defaults are used if ft is omitted or specified as *.
fm is the mode of the disk to contain the new files. If this field is
omitted or specified as an asterisk (*), A1 is assumed. 1QU IBM VM/37Q CMS Command and Macro Reference

TAPPDS If conflicting options are specified, the last one entered
is the one that is used. All options, except TAPn, are ignored when
unloaded (IEHMOVE) PDS tapes are read. indicates that the tape contains members of an OS partitioned
data set, each preceded by a MEMBER NAME=name statement5 The
tape must have been created by the OS IEBPTPCH service
program if this option is specified. NOPDS indicates that the contents of the tape will be placed in one eMS file. indicates that the tape file is in IEBUPDTE control file
format. The filename of each file is taken from the NAKE= parameter in the ".1 ADD" record that precedes each member. (See Usage Note 2.) COLl reads data from columns 1-80. You should specify this option
when you use the UPDATE option. reads data from columns 2-81; column 1 contains control
character information. This is the format produced by the OS IEBPTPCH service program. TAPn END
is the tape
representing
respectively.
unit number. n can be 1, 2,
virtual units 181, 182, 183,
If not specified, TAPl is assumed.
3,
and
or 4,
184,
considers an END statement (characters 'END' in columns 2-5)
a delimiter for the current member.
specifies that END statements are not to be treated as member
delimiters, but are to be processed as text. MAXTEN reads up to ten members.
option is selected.
This is valid only if the PDS reads any number of members.
1. You can use the TAPE command to position a tape at a particular
tape file before reading it with the TAPPDS command. If the tape
has as standard labels, TAPDDS will read and display the "VOL1" and
"HDR" records at the terminal. If the file you want to process is
not at the beginning of the tape, the TAPE command must be used to
position the tape at a particular tape file before reading it with
the command. Be aware that each file on an OS standard
label tape is actually three physical files (HDR, DATA, TRAILER).
If positioning to other than the first file, the user must skip physical tape files (3n-3 if positioning to the header labels,
3n-2 if positioning to the data file, where n is the number of the
file on the tape).
2. If you use the UPDATE option, you must also specify the COLl option. Each tape record is scanned for a "./ ADD" record in column 1. When a "./ ADD" record is found, subsequent reGords are read onto disk until the next ".1 ADD" record is
encountered or until a ".1 ENDUP" record is encountered.
Section 2. CMS Commands 195