
Using LUB Allocation and the ASSGN Statement
User Reference
Connectivity Systems, Inc.—Copyright © 2006
Use Pursuant to Company Instructions
7-7
Using LUB Allocation and the ASSGN Statement
Using ASSGN
Statements
When using LUB allocation and Automatic Volume Recognition (AVR),
BIM-EPIC does the work of an ASSGN statement. LUB allocation
selects the SYS number and AVR selects the drive. As long as LUB
allocation is active, ASSGN statements are not necessary and should be
removed from your JCL. However, ASSGN statements must be used
whenever LUB allocation is inhibited. When LUB allocation is inhibited,
you should use the drive specified in the ASSGN statement.
LUB allocation is automatically inhibited:
For direct access datasets
If the logical unit number is currently assigned IGNORE
For system logical units
If the logical unit is assigned in the DSN Catalog entry for a
dataset
In addition, LUB allocation is automatically inhibited for DTF names:
UIN
UOUT
IJSYSxx
SYS000
SORTxxx (unless TSIDSRT is executed in place of SORT)
You can add other DTF names to this list by specifying the names in the
BIM-EPIC TSIDMAP macro. See the BIM-EPIC Installation and System
Guide for additional information.
You must inhibit LUB allocation for datasets opened by TSIDASS and
datasets processed by PIOCS. This includes datasets processed with many
utility programs and any dataset opened with a DTFPH. In most data
processing environments, there are not many programs that can perform
these functions. In most circumstances, the TSIDASS utility can replace
the use of a VSE ASSGN statement.
Uncontrolled tape datasets do not need ASSGN statements. BIM-EPIC
will request the operator to specify a tape drive address.
Inhibiting LUB
Allocation
You can inhibit LUB allocation for a dataset using any of the following:
Option L in the dataset name on a DLBL
Comentarios a estos manuales