
Defining the BIM-EPIC Resource Dataset (ERD) ADD
Chapter 2. Installing the Basic System 2-29
ADD
An ADD control statement is required for each UCB definition that is added to the ERD.
There must be one ERD ADD for each tape cuu ADD in the VSE $IPL PROC. If multiple
VSE images are using the ERD, then all of the VSE ADD statements must be identical. This
is true even if some the devices are not accessible by one or more of the VSE images. The
VSE ADD statements must be in ascending sequence in the $IPL PROC.
ADD UCB=
cuu
,DEV=
iplcode
[,FEAT=
fcode
][,ACLNAME=
aclname
] [,ACLVEND=x]
[,ACLNUM=aclnum]
The UCB and DEV parameters are always required. All other parameters are optional.
cuu is the actual device address of the tape media. If sharing this tape media, it must be
known to all sharing systems by this same device address.
iplcode can be any valid tape IPL code, such as 3420, 3480, 3490, or TPA. It must be the
same one used on the VSE ADD statement.
fcode is a 1 to 3-character code that specifies any combination of the following features:
Code Feature
A Device has an automatic cartridge loader
D Dual density device
E 3490E device
I IDRC-capable device
L Leveling is used in an IBM ACL
T “Native” 3590 drive
Do not define VTS 3590’s in the ERD.
Define each VTS-owned 3490E drive with
Feature Code E.
U Remove Leveling feature from an IBM
ACL
Feature codes D, E, I, T are self-explanatory.
Feature Code A tells BIM-EPIC that the tape device has an automatic cartridge loader. This is
useful in the following scenario: A multi-cartridge input file is being processed, and all of the
input cartridges are stacked in the same cartridge loader. When a cartridge is “closed” a RUN
is issued and BIM-EPIC scans other drives looking for the next input volser. If the volser is
not found and A is not specified for the cuu, an EP001 MOUNT xxxxx message will be
issued. If A is specified, BIM-EPIC will wait until the RUN has completed and the next
Description
Syntax
Parameters
Comentários a estes Manuais