Re: file definition
Frank Swarbrick wrote:
This may or may not be a weird question, but...
No. Actually a good question.
Is there a utility where I can give it a list of dataset names and it can give
back some JCL that could have been used to define that file? Simply an
IEFBR14 with a DD for each file where the DD has the DISP=(NEW,CATLG), the
DSN, the full DCB, the SPACE parm and whatever else could be used to
recreate the dataset if it were deleted.
See this free REXX program. (You can add the full DCB etc, by inserting lines
to trap the LISTDS output. Or you can parse out the result of a Catalog
Search Interface run.)
/* REXX */
ALLOC DA('...in..') F(INVOER) SHR REUSE
EXECIO * DISKR INVOER (STEM LYS. FINIS
FREE F(INVOER)
ALLOC DA('..out..') F(AFVOER) OLD REUSE
AF.1 = //JOB12345 JOB ( ...),CLASS=A
AF.2 = //STEP EXEC PGM=IEFBR14
AANTALLYNE = 2 /* SAME # AS ABOVE */
FIRSTIME = 'YES'
DO J = 1 TO LYS.0
DSN = SUBSTR(LYS.J,1,44)
IF FIRSTIME = 'YES' THEN
DO
JCL = //DATA DD DISP=(NEW,CATLG),DSN=DSN
FIRSTIME = 'NO'
END
ELSE
JCL = // DD DISP=(NEW,CATLG),DSN=DSN
AANTALLYNE = AANTALLYNE + 1
AF.AANTALLYNE = JCL
END
AF.0 = AANTALLYNE
EXECIO * DISKW AFVOER (STEM AF. FINIS
FREE F(AFVOER)
RETURN
Input for REXX:
X.X
SYS1.PEST.RODENT
SYS1.PEST.MICE
SYS1.PEST.HUNGRY
SYS1.PEST.EAT
Output from it:
//JOB12345 JOB ( ...),CLASS=A
// EXEC PGM=IEFBR14
//DATA DD DISP=(NEW,CATLG),DSN=X.X
// DD DISP=(NEW,CATLG),DSN=SYS1.PEST.RODENT
// DD DISP=(NEW,CATLG),DSN=SYS1.PEST.MICE
// DD DISP=(NEW,CATLG),DSN=SYS1.PEST.HUNGRY
// DD DISP=(NEW,CATLG),DSN=SYS1.PEST.EAT
HTH!
Groete / Greetings
Elardus Engelbrecht
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: file definition
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Frank Swarbrick Sent: Friday, December 04, 2009 5:46 PM To: IBM-MAIN@bama.ua.edu Subject: file definition This may or may not be a weird question, but... Is there a utility where I can give it a list of dataset names and it can give back some JCL that could have been used to define that file? Simply an IEFBR14 with a DD for each file where the DD has the DISP=(NEW,CATLG), the DSN, the full DCB, the SPACE parm and whatever else could be used to recreate the dataset if it were deleted. Thanks, Frank SNIPPAGE No such utility for z/OS that I know of per se. However, you may be able to convince IDCAMS to provide you with some of the information. Regards, Steve Thompson -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: file definition
PDS command (from CBT tape) with subcommand DSNAME JCL may provide what you are looking for - at least for non-VSAM data sets. Don Imbriale -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Frank Swarbrick Sent: Friday, December 04, 2009 6:46 PM To: IBM-MAIN@bama.ua.edu Subject: file definition This may or may not be a weird question, but... Is there a utility where I can give it a list of dataset names and it can give back some JCL that could have been used to define that file? Simply an IEFBR14 with a DD for each file where the DD has the DISP=(NEW,CATLG), the DSN, the full DCB, the SPACE parm and whatever else could be used to recreate the dataset if it were deleted. Thanks, Frank -- Frank Swarbrick Applications Architect - Mainframe Applications Development FirstBank Data Corporation - Lakewood, CO USA P: 303-235-1403 This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: file definition
snip Is there a utility where I can give it a list of dataset names and it can give back some JCL that could have been used to define that file? /snip The REXX suggested is probably the easiest way, especially if you put in a LISTDSI. That will give you most of the parameters that you need to allocate a nonVSAM, catalogued DSN. If the DSN isn't around any more you could do something similar if you have DCOLLECT output. HTH Jack Kelly 202-502-2390 (Office) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: file definition
On Mon, 7 Dec 2009 12:38:55 -0500, John Kelly wrote: snip Is there a utility where I can give it a list of dataset names and it can give back some JCL that could have been used to define that file? /snip The REXX suggested is probably the easiest way, especially if you put in a LISTDSI. That will give you most of the parameters that you need to allocate a nonVSAM, catalogued DSN. If the DSN isn't around any more you could do something similar if you have DCOLLECT output. There's one fly in this ointment. Our DASD are all (mostly?) 3390. But when I request a particular number of cylinders, some busybody component (sometimes?) adjusts the requested number downward by the ratio of 3380 cylinder size to 3390 cylinder size. But reporting functions report the actual number of 3390 cylinders. So, if I use ISPF Data Set utility to get info for a data set, then Allocate another with the values on the screen, it's smaller. Every time. The functions to create a data set and to report its characteristics should obey the same conventions. I'm progressively converting all my SPACE requests to bytes. Beware. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: file definition
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Paul Gilmartin Sent: Monday, December 07, 2009 11:52 AM To: IBM-MAIN@bama.ua.edu Subject: Re: file definition snip There's one fly in this ointment. Our DASD are all (mostly?) 3390. But when I request a particular number of cylinders, some busybody component (sometimes?) adjusts the requested number downward by the ratio of 3380 cylinder size to 3390 cylinder size. But reporting functions report the actual number of 3390 cylinders. So, if I use ISPF Data Set utility to get info for a data set, then Allocate another with the values on the screen, it's smaller. Every time. The functions to create a data set and to report its characteristics should obey the same conventions. I'm progressively converting all my SPACE requests to bytes. Beware. -- gil Your DFSMS is messed up. There is a parameter in the Base Configuration where the number of bytes per track is set. For a 3390, it should be set to 56664. Sounds like yours is set to a 3380 value of 47476. Time to wack the sysprog/storage admin. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: file definition
snip But when I request a particular number of cylinders, some busybody component (sometimes?) adjusts the requested number downward by the ratio of 3380 cylinder size to 3390 cylinder size. /snip That certainly sounds like the Default Device Geometry in the SMS Base Configuration. Jack Kelly 202-502-2390 (Office) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: file definition
There's one fly in this ointment. Our DASD are all (mostly?) 3390. But when I request a particular number of cylinders, some busybody component (sometimes?) adjusts the requested number downward by the ratio of 3380 cylinder size to 3390 cylinder size. But reporting functions report the actual number of 3390 cylinders. That busybody is SMS. There is a panel withing the ISPF application where you specify the 'logical' track size. This is an artifact leftover when SMS was first introduced and 3380's still existed with 3390's. It was intended to 'save space'. I have had the parameter changed to 56664 in every shop I've worked at since SMS came out. It seems everybody started with 47476. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: file definition
On Mon, 7 Dec 2009 18:26:56 +, Ted MacNEIL wrote: There's one fly in this ointment. Our DASD are all (mostly?) 3390. But when I request a particular number of cylinders, some busybody component (sometimes?) adjusts the requested number downward by the ratio of 3380 cylinder size to 3390 cylinder size. But reporting functions report the actual number of 3390 cylinders. That busybody is SMS. There is a panel withing the ISPF application where you specify the 'logical' track size. This is an artifact leftover when SMS was first introduced and 3380's still existed with 3390's. It was intended to 'save space'. I have had the parameter changed to 56664 in every shop I've worked at since SMS came out. It seems everybody started with 47476. I was reporting from memory. The problem appears to have vanished, perhaps with a recent upgrade from 1.7 to 1.10. Would IBM have changed a default? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
file definition
This may or may not be a weird question, but... Is there a utility where I can give it a list of dataset names and it can give back some JCL that could have been used to define that file? Simply an IEFBR14 with a DD for each file where the DD has the DISP=(NEW,CATLG), the DSN, the full DCB, the SPACE parm and whatever else could be used to recreate the dataset if it were deleted. Thanks, Frank -- Frank Swarbrick Applications Architect - Mainframe Applications Development FirstBank Data Corporation - Lakewood, CO USA P: 303-235-1403 The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
