On Mon, 8 Sep 2008 15:54:33 -0500, Kirk Wolf [EMAIL PROTECTED] wrote:
Its wierd. Some GDGs work fine and others fail with this error.
Are you sure that, in the failing cases, that the (0) generation actually
exists? In other words, perhaps no GDS entries exist for that particular
GDG, and in
In other words, perhaps no GDS entries exist for that particular GDG, and in
that case generation 0 would work only with DISP=NEW.
It is my understanding that (0) never works with NEW.
-
Too busy driving to stop for gas!
--
Yes, the generation exists.
(0) should work for an existing dataset with status SHR.
I have found that this error only occurs on *some* GDGs. Others work fine.
I don't think that it is a BPXWDYN problem - its either an SVC99 problem, or
maybe a problem with the catalog entries for the GDG.
Sep 2008 12:46:38 +
From: [EMAIL PROTECTED]
Subject: Re: BPXWDYN relative GDG reference error
To: IBM-MAIN@BAMA.UA.EDU
In other words, perhaps no GDS entries exist for that particular GDG,
and in that case generation 0 would work only with DISP=NEW.
It is my understanding that (0
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: BPXWDYN relative GDG reference error
Again, referencing (0) is *not* the problem. That works fine on most
GDGs. The error seems specific to some GDGs, where *no* relative reference
works, even though there are several G000V00 generations cataloged
)
Date: Tue, 9 Sep 2008 12:46:38 +
From: [EMAIL PROTECTED]
Subject: Re: BPXWDYN relative GDG reference error
To: IBM-MAIN@BAMA.UA.EDU
In other words, perhaps no GDS entries exist for that particular GDG, and in
that case generation 0 would work only with DISP=NEW.
It is my
,DELETE),
// UNIT=3380,VOLUME=SER=334455,SPACE=(CYL,20)
Date: Tue, 9 Sep 2008 12:46:38 +
From: [EMAIL PROTECTED]
Subject: Re: BPXWDYN relative GDG reference error
To: IBM-MAIN@BAMA.UA.EDU
In other words, perhaps no GDS entries exist for that particular GDG,
and in that case
On Tue, 9 Sep 2008 08:26:18 -0500, Kirk Wolf wrote:
Also - I get the same error when I allocate a new dataset using (+1)
using (NEW,CATLG)? If you don't specify catalog, it won't be rolled in, so
it won't be associated with the GDG.
--
Tom Marchant
On Tue, 9 Sep 2008 08:26:18 -0500, Kirk Wolf [EMAIL PROTECTED] wrote:
Ahh! I found the problem.
The GDGs that don't work are definitely screwed up in the catalog.
There are G000V00 entries, but when I do a LISTC ALL on the base, they are
*not* listed as associations.
FWIW - the SVC99 error
Kirk:
A dataset ending with GnnnVnn may be created (and cataloged) without being
associated with a GDG index; it will just *appear* as if it were a member of
that GDG, by one's mental association. Most that I have seen, however,
have
been *old* generations that someobdy recovered from HSM
It is my understanding that (0) never works with NEW.
What you're saying seems reasonable, yet the JCL User's
Guide has an example under Generations of a Generation Data Group to the
contrary:
//NEWGDS DD DSNAME=GDS(0),DISP=(NEW,CATLG,DELETE),
// UNIT=3380,VOLUME=SER=334455,SPACE=(CYL,20)
: Re: BPXWDYN relative GDG reference error
It is my understanding that (0) never works with NEW.
What you're saying seems reasonable, yet the JCL User's
Guide has an example under Generations of a Generation Data Group to
the contrary:
//NEWGDS DD DSNAME=GDS(0),DISP=(NEW,CATLG,DELETE
IEF286I DPC088IF TEST - DISP FIELD INCOMPATIBLE WITH DSNAME
That's what I thought would happen.
The manual is wrong.
(I started as a JCL jockey in 1981)
Reminds me of the old joke:
The example on page 666 is wrong!
So what? It's only an example!
How do I do ...?
See the example on page 666.
I don't understand the error that I'm getting from BPXWDYN when I try to
allocate an existing dataset whic is the current/latest generation of an
existing GDG.
rc = bpxwdyn(alloc fi(SYS00011) reuse msg(2) da(HLQ.MY.GDG(0)) shr)
IKJ56871I DATA SET HLQ.MY.GDG NOT ALLOCATED, RELATIVE GENERATION
Its wierd. Some GDGs work fine and others fail with this error.
On Mon, Sep 8, 2008 at 1:52 PM, Kirk Wolf [EMAIL PROTECTED] wrote:
I don't understand the error that I'm getting from BPXWDYN when I try to
allocate an existing dataset whic is the current/latest generation of an
existing GDG.
15 matches
Mail list logo
