ervation in general, would coding the VOLSERS in the VOL field cause
the
> abend because the DATACLASS has the volume count of 20 and there were 56
> volumes in this particular STORAGE GROUP POOL?
>
> --- On Thu, 11/11/10, Darth Keller wrote:
>
>
> From: Darth Keller
> Subj
om.au]
Sent: Thursday, November 11, 2010 12:25 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET
I verified the DATACLAS construct. The volume count is 20. I am unable to
confirm if the LISTCAT has a EXT-ADDR because the dsn has been deleted. Sorr
From: John Dawes
To: IBM-MAIN@bama.ua.edu
Date: 11/11/2010 11:26 AM
Subject:Re: IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET
Sent by:IBM Mainframe Discussion List
Sorry, I'm at DR today - so I don't have the time or the manuals to look,
but my thinki
abend because the
DATACLASS has the volume count of 20 and there were 56 volumes in this
particular STORAGE GROUP POOL?
--- On Thu, 11/11/10, Darth Keller wrote:
From: Darth Keller
Subject: Re: IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET
To: IBM-MAIN@bama.ua.edu
Received: Thursday
R " in the ListCat
dd keller
G'Day,
I encountered the following abend when attempting to define a VSAM
extended dsn. The SMS routines (STORAGE CLASS, STORAGE GROUP &
DATACLASS) have been correctly defined. I verified if the volumes(3390-3)
were empty and all seem okay.
IGD17103I
G'Day,
I encountered the following abend when attempting to define a VSAM extended
dsn. The SMS routines (STORAGE CLASS, STORAGE GROUP & DATACLASS) have been
correctly defined. I verified if the volumes(3390-3) were empty and all seem
okay.
IGD17103I CATALOG ERROR WHILE DEFINING
2I PADD,NVSM,IDVR,CDVR,ACD1
>
> IEC333I
L028(041),08,CATALOG.TEST01.USER,FCIS.ZZZ.ON.CCISCHZZ.P7.D100130
>
>
>
> IGD17102I CATALOG ERROR IN DEFINING NONVSAM DATA SET
> FCIS.ZZZ.ON.DCISMAS1.CCISCHZZ.P7.D100130
> RETURN CODE IS 20 REASON CODE IS 0 IGG0CLEG
> IGD306I UNEXPEC
IGD17102I CATALOG ERROR IN DEFINING NONVSAM DATA SET
FCIS.ZZZ.ON.DCISMAS1.CCISCHZZ.P7.D100130
RETURN CODE IS 20 REASON CODE IS 0 IGG0CLEG
IGD306I UNEXPECTED ERROR DURING IGG0CLEG PROCESSING
RETURN CODE 20 REASON CODE 0
THE MODULE THAT DETECTED THE ERROR IS IGDVTSCU
SMS MODULE TRACE BACK - VTSCU VTSCT
>Why don't you just zap the VTOC entry for this dataset to PS? The catalog
>structure is much simpler then and bypasses VVDS. You should be familiar
>with VTOP dump, zap and format-x DSCBs. Don't try it at home if you are
not
>familiar with it! If you have CA-Disk, you can use a utility to this for
Why don't you just zap the VTOC entry for this dataset to PS? The catalog
structure is much simpler then and bypasses VVDS. You should be familiar
with VTOP dump, zap and format-x DSCBs. Don't try it at home if you are not
familiar with it! If you have CA-Disk, you can use a utility to this for
you
>I've had good luck with IBM's unsupported VVDSFIX tool, to delete an
>otherwise un-delete-able data set. The VVDSFIX tool's DELBCSR command did
>the trick for me.
SHAZAM! It worked. Thanks!
Jeffrey Deaver, Engineer
Systems Engineering
[EMAIL PROTECTED]
651-665-4231(v)
IS - "Creating competit
I've had good luck with IBM's unsupported VVDSFIX tool, to delete an
otherwise un-delete-able data set. The VVDSFIX tool's DELBCSR command did
the trick for me.
//*DELBCSR - DELETE BCS RECORD will erase a BCS record.**
//* The purpose of this command is to erase a catalog
>4. For this one you need to leave the ver… as is.
>
>//SYSINDD *
> ZAP BCS(USERCAT.NAME) -
> DELETE(KEY(DATASET.NAME) -
> VER(04,C'A'))
>
Well, I'd love to try the zap, but I don't have CatalogRecovery +. Bum
rouble cleaning them
up.
This one is being stubborn.
ALTER GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 -
NEWNAME(GROUP.PCLAIMS.LOA.JUNK) -
CAT(ISV.SICF.USERCAT.VSYSP35)
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 94 - REASON CODE IS IGG0CLRN-8
8
Jeffrey, here are a few of the parameters that I have tried and have gotten
the file deleted. Since, you didn’t post the commands that you’ve used. I
figure that I send you what has worked for me in the pass. Hope this helps.
Just review the parms in manual before using to make sure that we’ll w
.
This one is being stubborn.
ALTER GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 -
NEWNAME(GROUP.PCLAIMS.LOA.JUNK) -
CAT(ISV.SICF.USERCAT.VSYSP35)
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 94 - REASON CODE IS IGG0CLRN-8
8 Explanation: OBTAIN
> How can you PURGE a non-existant dataset?
Tried it both ways. I get the same result without the PURGE.
Jeffrey Deaver, Engineer
Systems Engineering
[EMAIL PROTECTED]
651-665-4231(v)
IS - "Creating competitive advantage with technology. Providing service
that excels."
OSS - " Where Innovation
>Had to go to 1.9 manual to find 90-54. Does this make any sense to you?
>
>| 54 Explanation: DELETE failed because the data set is
> being renamed but it has not completed.
>
> | Programmer Response: Rename the data set with the
> |
-Original Message-
> > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
> > Behalf Of Jeffrey Deaver
> > Sent: Friday, August 22, 2008 3:22 PM
> > To: IBM-MAIN@BAMA.UA.EDU
> > Subject: Re: Catalog Error - Can't delete dataset
> &
| IDCAMS ALTER command and then delete it.
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
> Behalf Of Jeffrey Deaver
> Sent: Friday, August 22, 2008 3:22 PM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: Catalog Error - Ca
How can you PURGE a non-existant dataset?
From: Jeffrey Deaver [mailto:[EMAIL PROTECTED]
Sent: Fri 8/22/2008 4:22 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Catalog Error - Can't delete dataset
>Have you tried delete noscratch.
Yep. Got this...
IDCAMS
TCH
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 90 - REASON CODE IS IGG0CLFO-54
IDC0551I ** ENTRY GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 NOT
IDC0551I DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE
Did you try:
Idcams
Delete dataset.name NSCR
From: Jeffrey Deaver [mailto:[EMAIL PROTECTED]
Sent: Fri 8/22/2008 4:05 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Catalog Error - Can't delete dataset
I can't delete a dataset which is cataloged, but no longer
Have you tried delete noscratch.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Jeffrey Deaver
Sent: Friday, August 22, 2008 4:05 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Catalog Error - Can't delete dataset
I can't delete a datase
I can't delete a dataset which is cataloged, but no longer physically
exists. I've tried every trick I can think of to delete the catalog entry,
nothing is working. Ideas? Ran a Diag on the catalog, got this...
IDC21364I ERROR DETECTED BY DIAGNOSE:
ICFCAT ENTRY: GROUP.PCLAIMS.LOA.TJJ49MIG.D2
>The reason I used the LOCK to prevent updates to this CATALOG because it is
>shared.
That's not the purpose of LOCK.
It's for recovery/operational purposes, IIRC.
-
Too busy driving to stop for gas!
--
For IBM-MAIN subscribe /
lto:[EMAIL PROTECTED] On Behalf
Of esmie moo
Sent: Tuesday, December 04, 2007 10:26 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: CATALOG ERROR
Good Day Gentle Readers,
I am trying to define a user catalog and I am unsuccessful. The error
message (please see below) points to a Security problem. I ch
DAL Analysis for Legato in an easy to view format
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of esmie moo
Sent: Tuesday, December 04, 2007 10:26 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: CATALOG ERROR
Good Day Gentle Readers,
I am tryin
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of esmie moo
> Sent: Tuesday, December 04, 2007 9:26 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: CATALOG ERROR
>
> Good Day Gentle Readers,
>
> I am trying
esmie moo
Sent: 04 December 2007 15:26
To: IBM-MAIN@BAMA.UA.EDU
Subject: CATALOG ERROR
Good Day Gentle Readers,
I am trying to define a user catalog and I am unsuccessful. The error
message (please see below) points to a Security problem. I checked with
Security and they say that it is not a
))
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 186 - REASON CODE IS IGG0CLFT-2
IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
John I checked and the dsn is not there. I will check with IBM for assistance.
Thanks for your help. Thanks to all who offered their suggestions and help.
John Kington <[EMAIL PROTECTED]> wrote:
Esmie,
I recommend you check the dasd volume(s) to make sure the dataset
that you deleted usi
Esmie,
I recommend you check the dasd volume(s) to make sure the dataset
that you deleted using noscratch is not still there.
I am out of ideas. If no one else figures it out, you could search ibmlink
or open a problem with IBM for assistance.
Sorry,
John
esmie moo <[EMAIL PROTECTED]> wrote:
> The
Esmie,
If I were you, I would open an ETR with IBM. At this point you are being
pulled in several directions by well meaning persons on this list. The
inability to catalog a new generation of a GDG has nothing to do with whether a
dataset has been migrated or not. Check with IBM. They wrote
Reynalodo,
The management class is NOMIGRATE. The user didn't want the dsns migrated
because he views them daily to compile reports. Also, a new gdg is created
daily.
reynaldo nobre muntoreanu <[EMAIL PROTECTED]> wrote:
Esmie
If the dataset is under control of DFSMSHSM, check the valu
The dsn is created on dasd and SMS managed. I checked the disk status and it
is always online. The job creates the dsn in the SMS pool which has 23 dasds
in that storage pool.
John Kington <[EMAIL PROTECTED]> wrote: Keeping with top posting:
Esmie,
Do you recall whether the oldest generatio
John,
I did a listcat of the GDG base and it has a limit of 40 with SCRATCH and
NOEMPTY parms.
John Kington <[EMAIL PROTECTED]> wrote:
>Do you have noscratch specified in the GDG define? It should be scratch to
have the oldest gdg automatically roll off to allow the next generation to
be
g wrapped around then the dataset would not be able to
roll in.
Esmie, how many catalog entries exist under the base gdg name? Just do a 3.4
display under ispf.
From: John Kington [mailto:[EMAIL PROTECTED]
Sent: Tue 1/16/2007 8:36 AM
To: IBM-MAIN@BAMA.UA.EDU
Tom Marchant wrote:
The oldest GDS will roll off regardless of SCRATCH. If neither
SCRATCH nor EMPTY is specified, the oldest GDS will be in rolled-out
status and will no longer be part of the GDG. In the pre-SMS days
it would have been uncataloged but not scratched. That said, I
agree with Da
/16/2007 8:36 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR
>Do you have noscratch specified in the GDG define? It should be scratch to
have the oldest gdg automatically roll off to allow the next generation to
be catalogued.
The listcat should look as follows:
ATTRIBUTES
LI
>Do you have noscratch specified in the GDG define? It should be scratch to
have the oldest gdg automatically roll off to allow the next generation to
be catalogued.
The listcat should look as follows:
ATTRIBUTES
LIMIT-10 SCRATCH NOEMPTY
David,
He must have had scr
Thanks Tom, I mis-spoke.
Dave
From: Tom Marchant [mailto:[EMAIL PROTECTED]
Sent: Tue 1/16/2007 8:19 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR
On Tue, 16 Jan 2007 07:37:25 -0500, O'Brien, David W. (NIH/CIT) [C] wrote:
>
>Do you hav
Keeping with top posting:
Esmie,
Do you recall whether the oldest generation was on dasd or tape? The
scratch error
indicates that it was dasd and the volume was not online. Maybe you
reclaimed a
dasd volume or have a dasd volume offline?
Regards,
John
>Thanks John. Yes, I noticed that the catalo
On Tue, 16 Jan 2007 07:37:25 -0500, O'Brien, David W. (NIH/CIT) [C] wrote:
>
>Do you have noscratch specified in the GDG define? It should be
>scratch to have the oldest gdg automatically roll off to allow the
>next generation to be catalogued.
>
The oldest GDS will roll off regardless of SCRATC
Esmie
If the dataset is under control of DFSMSHSM, check the values for the
attributes GDS defined in MGMTCLAS.
Verify itself trials involved without the duty permission exist RACF, of
access update upon I cataloguing.
RMUNTOR
2007/1/16, esmie moo <[EMAIL PROTECTED]>:
Thanks John. Yes, I no
[mailto:[EMAIL PROTECTED]
Sent: Tue 1/16/2007 7:11 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR
Thanks John. Yes, I noticed that the catalog entry was present. I then
scratched the entry (del noscr). But I cannot understand why this happened. I
checked the syslog but found nothing
-10 SCRATCH NOEMPTY
From: esmie moo [mailto:[EMAIL PROTECTED]
Sent: Tue 1/16/2007 7:11 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR
Thanks John. Yes, I noticed that the catalog entry was present. I then
scratched the entry (del noscr
Thanks John. Yes, I noticed that the catalog entry was present. I then
scratched the entry (del noscr). But I cannot understand why this happened. I
checked the syslog but found nothing that would indicate any type of a problem.
Any other suggestions?
John Kington <[EMAIL PROTECTED]> wrote
>My job put out the following error:
IEC331I 042-006(04280039),JS3BATCH,SOFVMA05,SCRT,IGG0CLH0
IEC331I VOL,INST49,NAME,DATAALL.REND.PC5.PROD.VMAXTD.G0553V00
IEC331I 050-092(0484,INST49),SOFVMA05,XTRACT,VALO,IGG0CLE3
IGD07001I GDG ROLL IN ERROR - RETURN CODE 50 REASON CODE 0 MODULE
IGD10
My job put out the following error:
IEC331I 042-006(04280039),JS3BATCH,SOFVMA05,SCRT,IGG0CLH0
IEC331I VOL,INST49,NAME,DATAALL.REND.PC5.PROD.VMAXTD.G0553V00
IEC331I 050-092(0484,INST49),SOFVMA05,XTRACT,VALO,IGG0CLE3
IGD07001I GDG ROLL IN ERROR - RETURN CODE 50 REASON
Of Darth Keller
Sent: Monday, September 18, 2006 2:02 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR - Defining VVDS
Now there's a timely question!
>>For the record, I have used CYL(5,1) for the last 15 years. I may need
>>to consider upping that for Mod-27s and -54s
>For the record, I am no spring chicken either. I have hit the 50+ age
>bracket, needless to say not only the gray cells are graying.
The only people in IT, that I work with, that are even close to my age, are the
mainframers.
I'm old enough to be the father of the IT people responsible for th
>I can live with that (vvds in extents). It is a user test volume.
I do not have exclusive ownership of that canine.
But, I would have one canned job that inits all general storage volumes the
same.
Putting all the VTOC, VTOCIX, VVDS (and CATALOGUE if it exists) at the front
with a standard siz
So with the default of TRK(10,10), the VVDS goes into secondary extents
on a volume with a lot of VSAM (the volume size is irrelevant, only the
numer of clusters). The VVDS can go to 123 extents, and there is no
problem if it does so. There is no performance hit or other problems.
So the def
Now there's a timely question!
>>For the record, I have used CYL(5,1) for the last 15 years. I may need
>>to consider upping that for Mod-27s and -54s. What are others using
>>these days on the large volumes?
We're going through a bid process for new DASD right now. We'll be moving
from 3 Sun
hards
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of willie bunter
Sent: Monday, September 18, 2006 11:59 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR - Defining VVDS
David,
I can live with that (vvds in extents). It is a user
And in closing, yes, Willie needs to read more...as we all do.
Bob Richards
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Tom Marchant
Sent: Monday, September 18, 2006 11:57 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR - Defining V
On Mon, 18 Sep 2006 09:04:01 -0700, willie bunter <[EMAIL PROTECTED]>
wrote:
>I am not sure what RTFB. However, how do I go about doing it...
Read the book. Some people use RTFM (Manual).
--
For IBM-MAIN subscribe / signoff
On Mon, 18 Sep 2006 16:01:06 +, Ted MacNEIL <[EMAIL PROTECTED]> wrote:
>>It's been so long since it was (4 4). I don't even remember when the
>>default changed. I want to say that it's about the time SMS first
>>became available.
>
>
>I never saw the update, but even (10 10) is too small on l
archant
Sent: Monday, September 18, 2006 11:43 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR - Defining VVDS
Snippage
Stop thinking only of VSAM!
On an SMS managed volume, ALL data sets have an entry in the VVDS.
The default allocation is 10 tracks primary and 10 tracks secondary
>
>Bob Richards
>
>
>-Original Message-
>From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
>Behalf Of Tom Marchant
>Sent: Monday, September 18, 2006 11:43 AM
>To: IBM-MAIN@BAMA.UA.EDU
>Subject: Re: CATALOG ERROR - Defining VVDS
>
>Snippage
>
>It's been so long since it was (4 4). I don't even remember when the default
>changed. I want to say that it's about the time SMS first became available.
I never saw the update, but even (10 10) is too small on larger volumes.
When in doubt.
PANIC!!
-
David,
I can live with that (vvds in extents). It is a user test volume.
I will have to examine the process of allocating a vvds in the same job as
the initialize of the volume. This would save a lot of headaches.
Thanks for the reassurance and advice from all.
"O'Brien, David
top answering those questions and leave to you young-uns to
>answer!
>
>Bob Richards
>
>
>-Original Message-
>From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
>Behalf Of Tom Marchant
>Sent: Monday, September 18, 2006 11:43 AM
>To: IBM-MAI
Willie,
CI size for the VVDS is 4096. For 10 trks that computes to 120 CIs in the VVDS.
For a SMS managed volume each file will require the following # of bytes:
KSDS 530
ESDS 370
Linear 340
Non-VSAM 100
I suspect you're not going to have a problem. Worst case your
e questions and leave to you young-uns to
answer!
Bob Richards
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Tom Marchant
Sent: Monday, September 18, 2006 11:43 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR - Defining VVDS
Sni
On Mon, 18 Sep 2006 08:13:55 -0700, willie bunter <[EMAIL PROTECTED]>
wrote:
>The user is not sure. I checked and the VVDS is at 10 trks (default?).
How many VSAMS dsns can this accomodate?
>
>"Richards.Bob" <[EMAIL PROTECTED]> wrote: Willie,
>
>DO NOT DELETE THAT VVDS unless you can empty th
asier than a
pound of problem resolution.
Bob Richards
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of willie bunter
Sent: Monday, September 18, 2006 11:34 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR - Defining VVDS
Bad news it is.
IL PROTECTED] On
Behalf Of willie bunter
Sent: Monday, September 18, 2006 11:14 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR - Defining VVDS
The user is not sure. I checked and the VVDS is at 10 trks (default?).
How many VSAMS dsns can this accomodate?
"Richards.Bob" wrote: Willie
@BAMA.UA.EDU
Subject: Re: CATALOG ERROR - Defining VVDS
The user is not sure. I checked and the VVDS is at 10 trks (default?).
How many VSAMS dsns can this accomodate?
"Richards.Bob" <[EMAIL PROTECTED]> wrote: Willie,
DO NOT DELETE THAT VVDS unless you can empty that volume!
B
e there that the
defaults are not enough?
Bob Richards
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of willie bunter
Sent: Monday, September 18, 2006 10:53 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR - Defining VVDS
Since t
bunter
Sent: Monday, September 18, 2006 10:53 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR - Defining VVDS
Since the VVDS entry is there can I expand it? Or do I have to delete
it and retry the allocation?
LEGAL DISCLAIMER
The information transmitted is intended solely for the
Since the VVDS entry is there can I expand it? Or do I have to delete it and
retry the allocation?
Tom Marchant <[EMAIL PROTECTED]> wrote: On Mon, 18 Sep 2006 14:12:15 +,
Ted MacNEIL wrote:
>
>The equivalent of SPACE=(TRK,(4,4)) is used.
Ancient history!
Tracks(10 10)
It's been so long
On Mon, 18 Sep 2006 14:12:15 +, Ted MacNEIL <[EMAIL PROTECTED]> wrote:
>
>The equivalent of SPACE=(TRK,(4,4)) is used.
Ancient history!
Tracks(10 10)
It's been so long since it was (4 4). I don't even remember when the
default changed. I want to say that it's about the time SMS first
became
According to the z/OS V1R7.0 Managing Catalogs manual:
"Explicitly defining a VVDS is usually appropriate when you are initializing
a new volume. If you are not running SMS, and a volume already contains some
non-VSAM data sets, it is appropriate to allow the VVDS to be defined
implicitly with the
>You can change it with F CATALOG,VVDSSPACE(pri,sec). This must be done at
>every IPL of the system. If not, it goes back to the default.
That's why I prefer it to be part of initialising DASD.
When in doubt.
PANIC!!
--
For
18, 2006 10:01 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR - Defining VVDS
Initialize the volume, vary it online, define the VVDS, and then add it
to the SMS configuration. If it has not been added to an SMS storage
group, SMS will not try to allocate a data set on it
>Yes, the first time a data set gets placed on an SMS-managed volume, a VVDS
>will be created if one does not already exist. (This is true whether the
data set is VSAM or not.)
The equivalent of SPACE=(TRK,(4,4)) is used.
This doesn't get you much on large packs.
When in doubt.
PANIC!!
--
Of willie bunter
Sent: Monday, September 18, 2006 7:14 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: CATALOG ERROR - Defining VVDS
Good Day,
I encountered the following error while I was attempting to define the
VVDS on a 3390-9 disk which is SMS managed:
IDC3014I CATALOG ERROR
IDC3009I
On Mon, 18 Sep 2006 09:19:35 -0400, Dave <[EMAIL PROTECTED]> wrote:
>Yes. On an SMS volume if there is no VVDS and SMS wishes to put a dsn on
>the volume (that is empty...) SMS will put a VVDS on the volume for you -
>albeit a tiny VVDS
Tiny? It's been quite a while since I was doing dasd
Yes, the first time a data set gets placed on an SMS-managed volume, a VVDS
will be created if one does not already exist. (This is true whether the
data set is VSAM or not.)
Regards,
Greg Shirey
Ben E. Keith Company
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL
Yes. On an SMS volume if there is no VVDS and SMS wishes to put a dsn on
the volume (that is empty...) SMS will put a VVDS on the volume for you -
albeit a tiny VVDS
--
For IBM-MAIN subscribe / signoff / archive access ins
Could the problem have been caused because a VSAM dsn was allocated on that
volume as soon as I put it ONLINE?
"Richards.Bob" <[EMAIL PROTECTED]> wrote: Oops, I forgot. I do this in REXX
and issue a Vary online from within
that code and then do the define VVDS. You may want to bring the volume
Richards.Bob
Sent: Monday, September 18, 2006 8:43 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: CATALOG ERROR - Defining VVDS
Add the DEFINE of the VVDS as the 2nd step of your INIT jcl.
Bob Richards
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf
Add the DEFINE of the VVDS as the 2nd step of your INIT jcl.
Bob Richards
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of willie bunter
Sent: Monday, September 18, 2006 8:14 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: CATALOG ERROR - Defining
Good Day,
I encountered the following error while I was attempting to define the VVDS
on a 3390-9 disk which is SMS managed:
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 50 - REASON CODE IS IGG0CLE3-8
IDC3003I
86 matches
Mail list logo
