Jim,
Have you thought about using the Catalog Search Interface within a REXX Exec
to retrieve the dataset information you need? Then process the results to
create the necessary JCL or allocation statements.
Please search the IBM-Main Archives for references to "IGGCSI" or "Catalog
Search Interface". Also look at your SYS1.SAMPLIB for IGGCSI.. members.


Regards,
Ulrich Krueger

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of SUBSCRIBE IBM-MAIN Jim
Sent: Wednesday, July 09, 2008 06:03
To: [email protected]
Subject: wildcard utilities

I have been struggling with a way to use wildcards as a means of not having 
to know all dataset names that may be created within a day's time.  I know 
you can use wildcards within a IDCAMS using the LISTCAT ENTRIES 
statement, but what I would really like is to be able to copy all the
wildcard 
datasets to another single dataset for reporting type purposes.  We have 
quite a few products on our mainframe, but I really don't know the best 
approach or software.  Below is a brief example of what I want to
accomplish.

 All the datasets are -  ORG of PS, RECFM = FB, LRECL = 133, BLKSIZE = 5985
 

 DISK.TEST.DATASETA
 DISK.TEST.DATASETB
 DISK.TEST.DATASETC

 Hopefully use wildcard of DISK.TEST.** to pick up ALL datasets and then 
copy to any other name I choose - DISK.BACKUP.DATASETS.  Then using that 
dataset to print out a single report in a viewable format.

Thanks in advance for any and all suggestions.

----------------------------------------------------------------------
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

----------------------------------------------------------------------
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

Reply via email to