Memorex LOCK - VERSION 2-24 Especificaciones descargar pdf (Pagina 255)

Types of Datasets Physical IOCS Processing

Chapter 7. Running Jobs With BIM-EPIC 7-35

Physical IOCS Processing

VSE system utilities, sort programs, report writers, database utilities, and many other

programs process datasets with physical IOCS (PIOCS).

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 those described below, you can

make any PIOCS program work with BIM-EPIC-controlled datasets. When you are familiar

with these points, please review the sections on program-specific instructions.

1. When a program requires a specific logical unit, LUB allocation must be inhibited for

every dataset processed in that job step. There are some cases in which LUB allocation is

inhibited automatically. See "LUB Allocation and the ASSGN Statement" in this chapter

for details.

2. Satisfy pre-open checking:

a. Make an assignment to a device type, using any of the following techniques:

• 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

If you make a disk assignment using the VSE ASSGN statement, assign the dataset to a

device of the same type to be 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.

b. For other programs like DITTO, some IDCAMS functions, and some SORT products,

include an EXTENT card with the assigned logical unit number.

c. Many programs that use PIOCS do not issue an "open" request that BIM-EPIC can

recognize. In this case, you can satisfy BIM-EPIC's "open" processing requirements by

executing the TSIDASS OPEN function to simulate the opening of both input and

output datasets. This is required only when the program does not issue an open, or

does I/O to the dataset before it is opened. Examples include some DITTO functions,

LIBR stand-alone backups and most FORTRAN compilers.

3. Use caution when using BIM-EPIC's concatenation facility. BIM-EPIC cannot recognize

end-of-file processing for many PIOCS programs, so BIM-EPIC's dataset concatenation

may not work for these programs.

4. Most PIOCS programs do not honor BIM-EPIC's dataset reblocking facility. Alternate

block sizes must usually be specified by submitting control statements to the program. For

sorts, TSIDSRT can be used to automatically update the control statements with the BIM-

EPIC block size.

Introduction

PIOCS Issues

1 2 ... 250 251 252 253 254 255 256 257 258 259 260 ... 488 489

Sin comentarios

Memorex LOCK - VERSION 2-24 Especificaciones Pagina 255