Re: file definition

2009-12-07 Thread Elardus Engelbrecht
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

Re: file definition

2009-12-07 Thread Thompson, Steve
-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

Re: file definition

2009-12-07 Thread Donald Imbriale
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

Re: file definition

2009-12-07 Thread John Kelly
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

Re: file definition

2009-12-07 Thread Paul Gilmartin
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

Re: file definition

2009-12-07 Thread McKown, John
-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

Re: file definition

2009-12-07 Thread John Kelly
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

Re: file definition

2009-12-07 Thread Ted MacNEIL
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

Re: file definition

2009-12-07 Thread Paul Gilmartin
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

file definition

2009-12-04 Thread Frank Swarbrick
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,