
Physical IOCS Processing
User Reference
Connectivity Systems, Inc.—Copyright © 2006
Use Pursuant to Company Instructions
7-37
Physical IOCS Processing
Description Some VSE system utilities, sort programs, report writers, database
utilities, and other programs process datasets with Physical IOCS
(PIOCS) instead of Logical IOCS (LIOCS).
Many different issues can come into play when a program uses PIOCS to
process datasets that are under BIM-EPIC control. If you familiarize
yourself with the issues described below, you can make any PIOCS
program work with BIM-EPIC-controlled datasets.
PIOCS Issues PIOCS issues to consider are:
When a program requires a specific logical unit, you must inhibit
LUB allocation for every dataset processed in that job step. There
are some cases in which LUB allocation is inhibited
automatically. See “
Using LUB Allocation and the ASSGN
Statement” for additional information.
Satisfy pre-open checking.
Make an assignment to a device type, using any of the
following methods:
Make a permanent assignment, as for SYS001 through
SYS005 and SYSLNK
Make a temporary assignment
Use the DD OPTION=SYSnnn parameter
Execute TSIDSRT for SORT or TSIDASS ASSGN for
other programs
If you make a disk assignment using the VSE ASSGN
statement, assign the dataset the same type of device as
the device used for the dataset. For example, you can
assign a disk dataset with the following statement:
// ASSGN SYS003,DISK,VOL=SYSWK1,SHR
If SYSWK1 is a 3380, for example, your dataset can be
created on any 3380 volume.
For other programs like DITTO, some IDCAMS commands,
and some SORT products, include an EXTENT card with the
assigned logical unit number. The xxx.SAMPJOB members
in the VSE sub-library containing BIM-EPIC have a large
number of examples for specific programs.
Komentáře k této Příručce