Re: Allocation mystery

2012-06-01 Thread Shmuel Metz (Seymour J.)
In <4fc7e1b0.6070...@trainersfriend.com>, on 05/31/2012 at 03:25 PM, Steve Comstock said: >I'm finding an unexpected allocation situation >that maybe someone can explain. Are all of your datasets supposed to be SMS managed? If so, there is an ACS issue. If not, it has always worked that way.

Re: Allocation mystery

2012-06-01 Thread Paul Gilmartin
On Thu, 31 May 2012 19:31:04 -0600, Steve Comstock wrote: > >> Something has to specify the UNIT. Does "LIKE" establish the >> UNIT but not the VOL? Strange. > >LIKE establishes neither; UNIT comes from the system default >unit, usually SYSALLDA; VOL is chosen from available storage >volumes.

Re: Allocation mystery

2012-05-31 Thread Steve Comstock
On 5/31/2012 4:13 PM, Thomas Conley wrote: On 5/31/2012 5:26 PM, Steve Comstock wrote: I'm finding an unexpected allocation situation that maybe someone can explain. I run a job that creates a new data set using this DD statement: //NEWMAST DD DISP=(NEW,CATLG),DSN=&SYSUID..WORK.NEW.ZINPUTA, //

Re: Allocation mystery

2012-05-31 Thread Steve Comstock
On 5/31/2012 4:59 PM, Paul Gilmartin wrote: On Thu, 31 May 2012 21:45:54 +, Gibney, Dave wrote: There is a parmlib option to abend NOT CATLG 2. I recommend using it. Would this cause the ABEND at the beginning or at the end of the job step? The latter would be suboptimal. IMO, SMS shoul

Re: Allocation mystery

2012-05-31 Thread Paul Gilmartin
On Thu, 31 May 2012 21:45:54 +, Gibney, Dave wrote: >There is a parmlib option to abend NOT CATLG 2. I recommend using it. > Would this cause the ABEND at the beginning or at the end of the job step? The latter would be suboptimal. >IMO, SMS should be set up for all allocations and the fallb

Re: Allocation mystery

2012-05-31 Thread Thomas Conley
On 5/31/2012 5:26 PM, Steve Comstock wrote: I'm finding an unexpected allocation situation that maybe someone can explain. I run a job that creates a new data set using this DD statement: //NEWMAST DD DISP=(NEW,CATLG),DSN=&SYSUID..WORK.NEW.ZINPUTA, // LIKE=STNT329.TRAIN.ZINPUTA Job runs fine a

Re: Allocation mystery

2012-05-31 Thread Gibney, Dave
nformation Technology Services Washington State University > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On > Behalf Of Tom Marchant > Sent: Thursday, May 31, 2012 2:38 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: Allocation myster

Re: Allocation mystery

2012-05-31 Thread Tom Marchant
On Thu, 31 May 2012 15:25:04 -0600, Steve Comstock wrote: >I run a job that creates a new data set using >this DD statement: > >//NEWMASTDD DISP=(NEW,CATLG),DSN=&SYSUID..WORK.NEW.ZINPUTA, >// LIKE=STNT329.TRAIN.ZINPUTA > >Job runs fine and creates the new file. Is the data set SMS mana

Allocation mystery

2012-05-31 Thread Steve Comstock
I'm finding an unexpected allocation situation that maybe someone can explain. I run a job that creates a new data set using this DD statement: //NEWMASTDD DISP=(NEW,CATLG),DSN=&SYSUID..WORK.NEW.ZINPUTA, // LIKE=STNT329.TRAIN.ZINPUTA Job runs fine and creates the new file. Now I run