
Introduction LUB Allocation and the ASSGN Statement
Chapter 7. Running Jobs With BIM-EPIC 7-7
LUB Allocation and the ASSGN Statement
Using LUB allocation and 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.
ASSGN statements must be used whenever LUB allocation is inhibited. When LUB
allocation is inhibited, the drive specified in the ASSGN statement is used.
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
and for the following 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 them in the TSIDMAP macro. See the
BIM-EPIC Installation and System Guide for details.
In addition, you must inhibit LUB allocation for datasets opened by TSIDASS and datasets
which will be processed with PIOCS. This includes datasets processed with many utility
programs and any dataset opened with a DTFPH. 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 to a tape drive address.
You can inhibit LUB allocation for a dataset in several ways:
• the "L" option in the dataset name on a DLBL
•
option "64" in the numeric options on a TLBL
•
OPTION=SYSnnn parameter on a DD statement
•
a default SYS number in the BIM-EPIC dataset definition
When an ASSGN
Statement is Not
Required
When an ASSGN
Statement is
Required
Inhibiting LUB
Allocation
Komentarze do niniejszej Instrukcji