Re: cataloging dataset on 2 lpar's master catalog

[Dennis Leong]

Yes, that is on our "to-do" list when we move to 1.7 later this year.

""Tom Schmidt"" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]
> On Fri, 7 Jul 2006 10:12:14 -0700, Dennis Leong wrote:
>
>>I have a SMS managed dataset that is on master catalog that needs to
be
>>added to linklst and is accessed by 2 lpars.  We are sharing dasd.   I
can
>>only get it to catalog on one master catalog correctly.
> ..
>
> Dennis,
>
> How about sharing the master catalog between the 2 LPARs?  Then you
> wouldn't have this "he said-she said" game between your 2 existing
master
> catalogs and the remainder of your problem would be simple.  (Sysplex
it.)
>
> -- 
> Tom Schmidt
> Madison, WI
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html 

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

Re: cataloging dataset on 2 lpar's master catalog

[Dennis Leong]

After delete noscratch on the 2nd master catalog, I tried the def nvsam
with 
recatalog and received the messages:
DEF NVSAM(NAME(SYS2.CA1.R115.CAILIB ) -

DEVT( 3390 ) -

VOL( SYS243 ) -

RECATALOG )

IDC3014I CATALOG ERROR

IDC3009I ** VSAM CATALOG RETURN CODE IS 86 - REASON CODE IS IGG0CLEJ-22

IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12



As the sms admin, I'm a stickler for keeping the volumes clean of  sms 
ineligible datasets.  In this case,  not having the sms attributes is
not an 
issue but for other datasets it may.  Thank you.

"Bruce Black" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]
>> I have a SMS managed dataset that is on master catalog that needs to
be 
>> added to linklst and is accessed by 2 lpars.  We are sharing dasd.
I 
>> can only get it to catalog on one master catalog correctly.  That is,
on 
>> the 2nd master catalog the dataset does not have its sms storclas and

>> mgmtclas attributes.
> You probably did a DEFINE NONVSAM to put it in the second mastercat.
For 
> SMS datasets, you must include the RECATALOG operand to pick up the
SMS 
> data from the NVR in the VVDS, e.g,
>
> DEFINE NONVSAM(NAME(dsname) VOL(volser) RECATALOG)
>
> Do a DELETE NOSCRATCH to get it out of the second mastercat, then do
the 
> DEFINE as above.
>
> However, not having the SMS info in the catalog is probably not a big 
> issue.   The same info is stored in the NVR and I think the NVR is
used 
> when it is needed.  You probably don't need to fix this
>
> -- 
> Bruce A. Black
> Senior Software Developer for FDR
> Innovation Data Processing 973-890-7300
> personal: [EMAIL PROTECTED]
> sales info: [EMAIL PROTECTED]
> tech support: [EMAIL PROTECTED]
> web: www.innovationdp.fdr.com
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html 

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

Re: cataloging dataset on 2 lpar's master catalog

[Shmuel Metz (Seymour J.)]

In <[EMAIL PROTECTED]>, on
07/07/2006
   at 10:12 AM, Dennis Leong <[EMAIL PROTECTED]> said:

>I have a SMS managed dataset that is on master catalog that needs to
>be added to linklst and is accessed by 2 lpars. 

Why? You're putting things in your master catalog that don't belong
there.

>To get around the problem, I have renamed the dataset so that it  is
>cataloged in usercat.

That's what you should have done in the first place.

>However, this means that I have to code the volser in the linklst 
>entry in PROGxx which I really want to avoid. 

Why? And why is it SMS managed?
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: cataloging dataset on 2 lpar's master catalog

[Bruce Black]

I have a SMS managed dataset that is on master catalog that needs to 
be added to linklst and is accessed by 2 lpars.  We are sharing 
dasd.   I can only get it to catalog on one master catalog correctly.  
That is, on the 2nd master catalog the dataset does not have its sms 
storclas and mgmtclas attributes.
You probably did a DEFINE NONVSAM to put it in the second mastercat.  
For SMS datasets, you must include the RECATALOG operand to pick up the 
SMS data from the NVR in the VVDS, e.g,


DEFINE NONVSAM(NAME(dsname) VOL(volser) RECATALOG)

Do a DELETE NOSCRATCH to get it out of the second mastercat, then do the 
DEFINE as above.


However, not having the SMS info in the catalog is probably not a big 
issue.   The same info is stored in the NVR and I think the NVR is used 
when it is needed.  You probably don't need to fix this


--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com

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

Re: cataloging dataset on 2 lpar's master catalog

[Tom Marchant]

On Fri, 7 Jul 2006 12:27:57 -0500, Tom Schmidt 
<[EMAIL PROTECTED]> wrote:

>On Fri, 7 Jul 2006 10:12:14 -0700, Dennis Leong wrote:
>
>>I have a SMS managed dataset that is on master catalog that needs to be
>>added to linklst and is accessed by 2 lpars.  We are sharing dasd.   I can
>>only get it to catalog on one master catalog correctly.
>...
>
>Dennis,
>
>How about sharing the master catalog between the 2 LPARs?  Then you
>wouldn't have this "he said-she said" game between your 2 existing master
>catalogs and the remainder of your problem would be simple.  (Sysplex it.)
>
I agree that's the best answer.

If the HLQ is SYS1, AMS will allow you to recatalog it in another
catalog.

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

Re: cataloging dataset on 2 lpar's master catalog

[Tom Schmidt]

On Fri, 7 Jul 2006 10:12:14 -0700, Dennis Leong wrote:

>I have a SMS managed dataset that is on master catalog that needs to be
>added to linklst and is accessed by 2 lpars.  We are sharing dasd.   I can
>only get it to catalog on one master catalog correctly.  
...

Dennis, 
 
How about sharing the master catalog between the 2 LPARs?  Then you 
wouldn't have this "he said-she said" game between your 2 existing master 
catalogs and the remainder of your problem would be simple.  (Sysplex it.) 
 
-- 
Tom Schmidt 
Madison, WI 
 

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

cataloging dataset on 2 lpar's master catalog

[Dennis Leong]

I have a SMS managed dataset that is on master catalog that needs to be 
added to linklst and is accessed by 2 lpars.  We are sharing dasd.   I can 
only get it to catalog on one master catalog correctly.  That is, on the 
2nd master catalog the dataset does not have its sms storclas and mgmtclas 
attributes.  When I try to run an idcams alter to define the attributes I 
get the following:


IDC3194I SMS CONSTRUCT STORAGECLASS SPECIFIED FOR NON-SMS MANAGED OBJECT
IDC3194I SMS CONSTRUCT MANAGEMENTCLASS SPECIFIED FOR NON-SMS MANAGED

We are running z/os 1.4.   We have other sms datasets that are cataloged on 
both master catalogs with the correct attributes.   I do not know how these 
entries were created as sysprog who is responsible is on vacation.  My gut 
feeling is that he may have cloned one master catalog to create the other 
at one time.  I believe one of the master catalogs is a connected as a user 
catalog. To get around the problem, I have renamed the dataset so that it 
is cataloged in usercat.  Now both systems can access the dataset and have 
the correct sms attributes.  However, this means that I have to code the 
volser in the linklst entry in PROGxx which I really want to avoid.   Any 
suggestions on how I can get a SMS master cataloged dataset to be cataloged 
on both lpar master catalogs?  Thank you.






- enD sin 


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