IGD17045I SPACE NOT SPECIFIED for allocation of dataset

jalcantara · Posted: Mon May 07, 2007 9:14 pm

hi,

got a CL error below every week. iv been restoring PI08.LPA2A.CTLF.ALLOW.DTFILE and then resubmit the job. does anyone knows why is this happening? is there a way to keep it from happening every week?

IEF344I I2B7246A CC0311 CC0311 DTFILE - ALLOCATION FAILED DUE TO DATA FACILITY SYSTEM ERROR
IGD17045I SPACE NOT SPECIFIED FOR ALLOCATION OF DATA SET
PI08.LPA2A.CTLF.ALLOW.DTFILE

here's the proc:

//DTFILE DD DSN=&MODE&OWNER..L&STATUS.A2A.CTLF.ALLOW.DTFILE,
// DISP=(MOD,CATLG,CATLG),UNIT=&MODE.STOR,
// RECFM=FB,LRECL=41,BLKSIZE=23452

thanks,
june

William Thompson · Posted: Mon May 07, 2007 9:29 pm

I think it is trying to tell you the file does not exist, have you checked?
The simplest way to avoid it is to code the space in the DD.

mkk157 · Active User Joined: 17 May 2006 Posts: 310

Hi jalcantara,

Use this SPACE=(CYL,(10,5),RLSE) in DD statement.

superk · Posted: Mon May 07, 2007 10:49 pm

OK, this has been nagging at me for a long time, so I have to ask:

Why would space ever need to be specified? Shouldn't SMS have taken care of the space allocation, as well as possibly overriding the coded BLKSIZE parameter if needed?

Sometimes, from a lot of the questions, it seems as if these folks don't have or don't use SMS at their sites? Why would SMS NOT be used? Is there some overhead involved that uses up system resources?

dick scherrer · Posted: Mon May 07, 2007 11:45 pm

Hello,

From what i've seen, when people get "mainframe training" at some education facility, SMS is not included - i suppose it is not in the scope of cobol, jcl, vsam, database, utilities, etc. When they go to work and are not told how to allocate SMS-managed datasets at their employment site, the datasets follow all of the old rules. I've been to a few sites where people who had been developers there for several years, did not that the reason they "lost" datasets sometimes because they were allocated on transient volumes rather than SMS-managed volumes. When the "scratch & clean" was run over the weekend or whenever, their test files went away. . .

The biggest reason that i've seen for not using SMS is fear of change and ignorance of what SMS is and what it does. It has been a while since i've gone into a place that did not use SMS at all. For my $.02, not going to SMS is a management problem - individual projects should not determine whether to use SMS or not (again IMHO).

expat · Posted: Tue May 08, 2007 12:37 pm

SMS is no great user of resource. I've never seen a system grind to a halt because SMS had grabbed all of the CPU.

SMS may be used to allocate default space parameters but only if it is set up to. This is obviously a site specific thing, where they have chosen not to. This assumes that this is an SMS managed allocation.

Unfortunately SMS will accept a BLKSIZE from the JCL if coded, so the JCL would win that one. I do try and post rewrites of OP JCL to remove BLKSIZE and let the operating system define it.

As to why your dataset needs to be restored every week, well, one suggestion has already been put forward by Dick. If the dataset is SMS managed then go talk to your storage group and tell them that it can not be deleted so quickly. Of course there's always the possibility that somewhere in the scheme of the application path that someone has coded DISP=(xxx,DELETE)