
Introduction Maintaining the DSN Catalog (TSIDUTL)
6-4 BIM-EPIC Installation and System Guide
therefore not allowed by VSE). If the normal termination disposition keyword of DELETE
was specified in place of the default of KEEP, the file would be erased when it was closed for
output and we would fail when we attempted to open the file for input since it would no longer
exist.
There are a couple of solutions to this dichotomy. If unique dataset names without any
partition or partition/processor independence specifications (i.e., dataset name not prefixed by
% or %%) are used, merely supply an IDCAMS step to delete the file from the VSAM catalog
just prior to its use.
If your requirements dictate that partition or partition/processor independence dataset name(s)
be used, insert a job step similar to the following example just prior to the use of the dataset
which will erase any data that may already exist:
// DLBL IJSYSUC,'your.vsam.user.catalog',,VSAM
// DLBL ERASE,'%%your.vsam.esds.sam.file',,VSAM, *
DISP=(OLD,DELETE),RECORDS=(500,250), *
RECSIZE=50
// EXEC IDCAMS,SIZE=AUTO
REPRO IFILE (SYSIPT ENV(BLKSZ(80) RECFM(F))) -
OFILE (ERASE ENV(BLKSZ(50) RECFM(F)))
/*
Note the DISP operand on the DLBL control statement for ERASE. A
DISP=(OLD,DELETE) tells VSAM to allocate space if the file does not already exist and,
most importantly, to delete the file when it is closed. Now, no matter if the file previously
existed or not, it will be erased when the job step completes. (The IDCAMS control
statements accomplish nothing beyond opening and closing the dataset since the '/*' indicates
that no SYSIPT data has been presented.)
TSIDUTL functions are dictated by control statements. You may specify as many functions
per execution as you wish. Individual control statements and TSIDUTL examples are
presented in the following sections.
Control Statements
and Examples
Kommentare zu diesen Handbüchern