If I understand correctly, there are two master catalogs--one for each 
LPAR--and one shared user catalog pointed to independently by the two mcats. As 
others have said, the catalog configuration for both LPARs must be *exactly* 
the same, including the SYSCAT parameter in LOADxx. It's also possible that one 
of the master cats (but not the other) contains an entry for a SYS7.R30.* 
dataset that was defined *before* the alias was created. Which is to say the 
mcats are not identical. 

I might suggest that out-of-sync conditions in general would be minimized by 
having all sysplex LPARs share the same master catalog unless you have a 
compelling reason not to--like bronze-plex for example.  



.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
[email protected]

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Mike Schwab
Sent: Monday, June 10, 2019 12:54 PM
To: [email protected]
Subject: (External):Re: Alias Listcat discrepancy betweeen sysplex'd LPARs

The ALIAS definition goes into the MASTER CATALOG.
The Alias needs to be defined on every system you want to access it from.
On a system where the alias is defined in the master catalog the datasets will 
be cataloged in the user catalog.
On a system where the alias has not been defined in the master catalog the 
datasets will be cataloged in the master catalog.


On Mon, Jun 10, 2019 at 6:23 PM Elaine Beal <[email protected]> wrote:
>
> I have a 2 LPAR sysplex and a shared user catalog the catalog has only 
> 2 alias entries
>
> when I allocate a new dsn (iefbr14) on one of the LPARs, say LPARA, 
> listcat's look as expected
>
> but on the other LPARB listcat up to some level of qualifiers the 
> dataset is not listed alias sys7.r30
>
> listcat  fqdsn             -  SYS7.R30.V22.RSU.ROOT.HFS           displays as 
> expected
> remove last llq          -  SYS7.R30.V22.RSU.ROOT                 displays as 
> expected
> remove next llq dsn   -  SYS7.R30.V22.RSU                           displays 
> as expected
> remove any more llq and dataset does not list    SYS7.R30.V22
>
>
> Thanks,
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to