Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Dataset in Catalog but not on Volume

239 views
Skip to first unread message

Werner Nussbaumer

unread,
Mar 3, 2003, 9:03:48 AM3/3/03
to
Hi all

In a REXX procedure I first delete and then allocate a dataset:

/*REXX*/
ADDRESS TSO
"DEL 'T096058.LIB.TEST'"
"ALLOC F(CPMUNITS) DSN('T096058.LIB.TEST') CATALOG LRECL(80)",
"RECFM(F B) TRACKS SPACE(1,1) DIR(0) DSORG(PS) NEW REUSE"
ADDRESS MVS
"EXECIO * DISKW CPMUNITS (STEM DATA. FINIS"

This works dozens of time, but randomly the dataset can't be deleted with the normal DEL command because it is in the catalog but not on the indicated volume. The REXX is called under BBI and the TSO delete command shows the following error message:

del 'T096058.LIB.TEST'
DATA SET T096058.LIB.TEST NOT ON VOLUME AS INDICATED IN THE CATALOG OR VOL PARAMETER
** T096058.LIB.TEST NOT DELETED
LASTCC=8

Does anyone know how this can happen?

Thanks for any help,
Regards
Werner Nussbaumer

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LIST...@VM.MARIST.EDU with the message: INFO TSO-REXX

Doug Nadel

unread,
Mar 3, 2003, 9:31:21 AM3/3/03
to
Try DEL dsname NOSCRATCH


Doug Nadel
----------------------------------------
ISPF and OS/390 Tools & Toys page:
http://www.sillysot.com/mvs
Mail containing HTML or any attachments, including vcf files, is
automatically discarded. If you need to send me an attachment,
please let me know so that I can change my email filters.

Werner Nussbaumer

unread,
Mar 3, 2003, 10:03:28 AM3/3/03
to
Yes, that works, but how can a dataset be in the catalog and not on the specified volume?

Regards
Werner Nussbaumer

Binyamin Dissen

unread,
Mar 3, 2003, 10:03:26 AM3/3/03
to
On Mon, 3 Mar 2003 14:31:21 GMT Doug Nadel <some...@MINDSPRING.COM> wrote:

:>Try DEL dsname NOSCRATCH

I would try to figure out why the problem is occurring. It cannot occur if the
allocation is always under TSO unless either NEW KEEP is sometimes specified
or if the catalog is messed up.

It can occur in batch if the system fails while the step with DISP=(,CATLG)
fails.

:>On 3 Mar 2003 06:03:48 -0800, werner.n...@UBS.COM (Werner Nussbaumer) wrote:

:>>In a REXX procedure I first delete and then allocate a dataset:

:>>/*REXX*/
:>>ADDRESS TSO
:>>"DEL 'T096058.LIB.TEST'"
:>>"ALLOC F(CPMUNITS) DSN('T096058.LIB.TEST') CATALOG LRECL(80)",
:>> "RECFM(F B) TRACKS SPACE(1,1) DIR(0) DSORG(PS) NEW REUSE"
:>>ADDRESS MVS
:>>"EXECIO * DISKW CPMUNITS (STEM DATA. FINIS"

:>>This works dozens of time, but randomly the dataset can't be deleted with the normal DEL command because it is in the catalog but not on the indicated volume. The REXX is called under BBI and the TSO delete command shows the following error message:

:>>del 'T096058.LIB.TEST'
:>>DATA SET T096058.LIB.TEST NOT ON VOLUME AS INDICATED IN THE CATALOG OR VOL PARAMETER
:>>** T096058.LIB.TEST NOT DELETED
:>>LASTCC=8

--
Binyamin Dissen <bdi...@dissensoftware.com>
http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel

Phil Clowes

unread,
Mar 4, 2003, 10:28:54 AM3/4/03
to
Any number of reasons (some given in previous posts)

Often it is as a result of a manual process where a person has removed the
dataset without going through the catalog.

Or it is due to a step failure when the dataset is being created.


"Werner Nussbaumer" <werner.n...@UBS.COM> wrote in message
news:D035A59D220A5743B57...@s01b1f4d.flur.zuerich.ubs.ch...

0 new messages