On Wed, 30 Jun 2010 16:04:24 -0500, Mark Zelden wrote:
>Although Paul may be able to use more chicanery to add an SDSF REXX
>batch step to look at the joblog of the running job, get the tape mount
>message, and create the IDCAMS DEFINE NONVSAM input and then
>run IDCAMS in a subsequent step.
>
In the case where the volume can be allocated, Paul might
be more comfortable chasing the TIOT in Rexx than scraping
the output with SDSF.
>On Wed, 30 Jun 2010 15:56:15 -0500, Field, Alan C. wrote:
>
>>Probably not - this is all SYSIN data so would require manual data entry
>>to plug in the volser
>>
Now I'm confused:
16.0 "z/OS V1R10.0 DFSMS AMS for Catalogs"
16.0 Topic 16. DEFINE NONVSAM
The DEFINE NONVSAM command defines a catalog entry for non-VSAM data
sets or a collection of objects. The syntax of the DEFINE NONVSAM
command is:
DEFINE NONVSAM
(NAME(entryname)
DEVICETYPES(devtype[ devtype...])
VOLUMES(volser[ volser...])
[COLLECTION]
[FILESEQUENCENUMBERS(number[ number...])]
[OWNER(ownerid)]
[RECATALOG|NORECATALOG]
[CATALOG(catname)]
A sequence of commands commonly used in a single job step includes
DELETE--DEFINE--REPRO or DELETE--DEFINE--BLDINDEX. You can specify
either a DD name or a data set name with these commands. ...
But I would expect to see a keyword with which to specify
the DD name. ???
>>The 98000 is a convention used to tell one's tape management system to
>>ignore the volser and not try and manage it.
>>
Yup. Do it all the time.
Thanks,
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
