DATA SET RESERVATION UNSUCCESSFUL

[Donnelly, John P]

We have a job that executes PGM=IEFBR14 with 40 DD cards specifying DISP=(OLD,DELETE,DELETE).
From time to time we will get a JCL error because dataset reservation failed.
Any other way we might accomplish the same event?

John Donnelly
Texas Instruments SVA
2900 Semiconductor Drive
Santa Clara, CA 95051
408-721-5640
408-470-8364 Cell
John.P....@ti.com




----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

[Lloyd Fuller]

Add SPACE and VOLUME parameters, and change OLD to MOD. That way if it does
exist, it will be deleted, and if it does not, it will be created and deleted in
the same step.

Use it all of the time. You can also use UNIT=SYSDA (or some such) instead of
VOLUME.


Lloyd

[Lizette Koehler]

>
>We have a job that executes PGM=IEFBR14 with 40 DD cards specifying DISP=(OLD,DELETE,DELETE).
>From time to time we will get a JCL error because dataset reservation failed.
>Any other way we might accomplish the same event?
>

what version of z/OS?

It depends on if the job is currently setup by a person or a process. How is the IEFBR14 job created?

Lizette

[Schwarz, Barry A]

Does the dataset exist but the enqueue fails or do you fail due to dataset not found? If the latter, use DISP=(MOD,DELETE,DELETE). If the former, there is a JES2 parameter that will change the behavior from fail to wait but you really need a process to insure no one else is using the datasets in question.

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-...@bama.ua.edu] On
> Behalf Of Donnelly, John P
> Sent: Thursday, November 03, 2011 12:38 PM
> To: IBM-...@bama.ua.edu
> Subject: DATA SET RESERVATION UNSUCCESSFUL
>

> We have a job that executes PGM=IEFBR14 with 40 DD cards specifying
> DISP=(OLD,DELETE,DELETE).
> From time to time we will get a JCL error because dataset reservation
> failed.
> Any other way we might accomplish the same event?

[Starr, Alan]

John,

There are many ways of accomplishing this, assuming that you wish to delete those datasets that are NOT in use.

One possibility: run IKJEFT01 in batch and, for each of the DDs in the IEFBR14 step, issue a DELETE command. Datasets that are ENQueued upon (EXCL or SHR) will not be deleted.

Cheers,
Alan

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@bama.ua.edu] On Behalf Of Donnelly, John P
Sent: Thursday, November 03, 2011 12:38 PM
To: IBM-...@bama.ua.edu
Subject: DATA SET RESERVATION UNSUCCESSFUL

[Staller, Allan]

There are several different conditions that can generate similar
issues, each of which, generally requires an operator (human or
electronic) to reply to a WTOR.

Without the message id from the WTOR, any response from this list would
be pure speculation.

Please check you system log and post the message ID of the WTOR.

HTH,

<snip>

We have a job that executes PGM=IEFBR14 with 40 DD cards specifying
DISP=(OLD,DELETE,DELETE).
From time to time we will get a JCL error because dataset reservation
failed.
Any other way we might accomplish the same event?

</snip>

[Gibney, Dave]

This suggestion will not change the ' DATA SET RESERVATION UNSUCCESSFUL' situation. The answer to Lizette's question is a factor in what might be the correct or "better" solution.

In my experience, this message occurs when deleting a GDS (specific generation dataset) and something else is adding, deleting or otherwise preventing the required update to the GDG base entry.

Dave Gibney
Information Technology Services
Washington State University

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-...@bama.ua.edu] On

[Eric Bielefeld]

Another way to do it is to set up an IDCAMS job to delete all of the datasets. I don't think you will get dataset reservation failed errors. If for whatever reason 1 or 2 datasets don't get deleted, you will get a non zero return code instead of a JCL error.

--
Eric Bielefeld
Systems Programmer

[Mark Zelden]

On Thu, 3 Nov 2011 12:37:51 -0700, Donnelly, John P <John.P....@TI.COM> wrote:

>We have a job that executes PGM=IEFBR14 with 40 DD cards specifying DISP=(OLD,DELETE,DELETE).
>From time to time we will get a JCL error because dataset reservation failed.
>Any other way we might accomplish the same event?
>

Details, details, details... Without them I can't say for sure. Are you getting
message IEF211I? I think you may be describing a situation rectified by specifying
the following in your ALLOCxx parmlib member:

SDSN_WAIT WAITALLOC(YES)

See the init and tuning guide for details. Also, these days you can make the change
dynamically with the SETALLOC command.

I've needed to use this at shops since MVS/XA. However, you used to have
have to zap the allocation default table (IEFAB445) to get this option by
turning on the DEFSDSWT flag.

Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
mailto:ma...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://expertanswercenter.techtarget.com/

[Ted MacNEIL]

>Another way to do it is to set up an IDCAMS job to delete all of the datasets. I don't think you will get dataset reservation failed errors. If for whatever reason 1 or 2 datasets don't get deleted, you will get a non zero return code instead of a JCL error.

And, if you want, you can make the RC 0.
Just code:

IF MAXCC < 9 THEN SET MAXCC = 0

I always want delete steps to complete successfully.
Deleting a nonexistent dsn is not an error.

-
Ted MacNEIL
eama...@yahoo.ca
Twitter: @TedMacNEIL

[McKown, John]

We just use CA-11. But I have used IDCAMS.

//DELEM EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEL some.dsn1
DEL some.dsn2
...
DEL some.dsn3
SET MAXCC=0
/*
//*

--
John McKown
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone *
john....@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

> -----Original Message-----
> From: IBM Mainframe Discussion List
> [mailto:IBM-...@bama.ua.edu] On Behalf Of Donnelly, John P
> Sent: Thursday, November 03, 2011 2:38 PM
> To: IBM-...@bama.ua.edu
> Subject: DATA SET RESERVATION UNSUCCESSFUL
>

[Shmuel Metz , Seymour J.]

In <995242624F0873419E71E...@EXMAIL01.scwf.nsc.com>,
on 11/03/2011

at 12:37 PM, "Donnelly, John P" <John.P....@TI.COM> said:

>Any other way we might accomplish the same event?

Yes, but if another job is using the data set you will cause problems
by deleting it. I advise that you use AMS to delete the data sets and
deal with the ones in use after the job using them has finished and
you have verified that it really is safe to delete them.

--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)