Re: Alias Listcat discrepancy betweeen sysplex'd LPARs
Good point but I checked and Include Additional Qualifiers is selected. Also, in addition to my ne wdataset, there is one older one that has the same issue. Thanks, Elaine -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Alias Listcat discrepancy betweeen sysplex'd LPARs
Thanks Lizette. I have verified with 3.4 and listcat - same results there are other datasets in the catalog that list on both LPARs and F CATALOG confirms it's allocated on bot LPARs Elaine -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Alias Listcat discrepancy betweeen sysplex'd LPARs
I can say I've done this also, removed the include additional qualifiers, not good timing, right after I created a new master catalog for my 2.1 or 2.2 systems YIKES! Carmen Vitullo - Original Message - From: "Dana Mitchell" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Tuesday, June 11, 2019 1:02:40 PM Subject: Re: Alias Listcat discrepancy betweeen sysplex'd LPARs On Tue, 11 Jun 2019 17:28:44 +, Jesse 1 Robinson wrote: >We had a 'catalog anomaly' recently were one person got a different list of >data sets under 3.4 than I did, both of us using the same search criterion. >Turns out we had different selections set In the options list: > I experienced this just last week. The user inadvertently un-slahsed the 'Include Additional Qualifiers ' option. Produced very different results than expected. Dana -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Alias Listcat discrepancy betweeen sysplex'd LPARs
On Tue, 11 Jun 2019 17:28:44 +, Jesse 1 Robinson wrote: >We had a 'catalog anomaly' recently were one person got a different list of >data sets under 3.4 than I did, both of us using the same search criterion. >Turns out we had different selections set In the options list: > I experienced this just last week. The user inadvertently un-slahsed the 'Include Additional Qualifiers ' option. Produced very different results than expected. Dana -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Alias Listcat discrepancy betweeen sysplex'd LPARs
We had a 'catalog anomaly' recently were one person got a different list of data sets under 3.4 than I did, both of us using the same search criterion. Turns out we had different selections set In the options list: Confirm Data Set Delete Confirm Member Delete Include Additional Qualifiers Display Catalog Name Display Total Tracks Prefix Dsname Level It's not about right or wrong choices, simply that unless the choices are identical, results can differ for the *same* person on the *same* system, in particular 'Include Additional Qualifiers'. Having these choices is great, but the consequences of selecting one--or not--can be surprising. . . 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 robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Lizette Koehler Sent: Tuesday, June 11, 2019 7:15 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Alias Listcat discrepancy betweeen sysplex'd LPARs What are you using to list the Datasets? IDCAMS? 3.4? Other tool? Just verifying apples to apples Also, list the catalog - From both LPARs - MVS Console Command F CATALOG,REPORT Provides general information on the status of the catalog address space. Current settings for CAS parameters and features are listed as well as CAS specialty tasks addresses and any CAS entry points that have been intercepted. There are other forms of the REPORT command that provide information on other aspects of the catalog address space. Maybe also from both LPARs F CATALOG,ALLOCATED - ensure the ucat is there on both systems. Then provide the entire output back to the list Lizette > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Elaine Beal > Sent: Tuesday, June 11, 2019 6:36 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Alias Listcat discrepancy betweeen sysplex'd LPARs > > LPARA SYSCAT SCS001123CCATALOG.ICF.VSCS001 > VCATICF > > LPARB SYSCAT SCS001123CCATALOG.ICF.VSCS001 > VCATICF > > Thanks, > Elaine -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Alias Listcat discrepancy betweeen sysplex'd LPARs
What are you using to list the Datasets? IDCAMS? 3.4? Other tool? Just verifying apples to apples Also, list the catalog - From both LPARs - MVS Console Command F CATALOG,REPORT Provides general information on the status of the catalog address space. Current settings for CAS parameters and features are listed as well as CAS specialty tasks addresses and any CAS entry points that have been intercepted. There are other forms of the REPORT command that provide information on other aspects of the catalog address space. Maybe also from both LPARs F CATALOG,ALLOCATED - ensure the ucat is there on both systems. Then provide the entire output back to the list Lizette > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Elaine Beal > Sent: Tuesday, June 11, 2019 6:36 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Alias Listcat discrepancy betweeen sysplex'd LPARs > > LPARA SYSCAT SCS001123CCATALOG.ICF.VSCS001 > VCATICF > > LPARB SYSCAT SCS001123CCATALOG.ICF.VSCS001 > VCATICF > > Thanks, > Elaine -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Alias Listcat discrepancy betweeen sysplex'd LPARs
LPARA SYSCAT SCS001123CCATALOG.ICF.VSCS001 VCATICF LPARB SYSCAT SCS001123CCATALOG.ICF.VSCS001 VCATICF Thanks, Elaine -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Alias Listcat discrepancy betweeen sysplex'd LPARs
On Mon, 10 Jun 2019 23:32:21 -0500, Elaine Beal wrote: >These LPARs do share a master catalog. >LOADxx syscat has the same parm on both LPARs > >A listcat of the master shows the alias entry > >ALIAS -,SYS7.R30 > >Thanks, >Elaine > Can you please show us the complete LOADxx member each LPAR is using? I'm specifically interested in the SYSCATs' multilevel alias value (at pos. 17), but prefer to see the entire LOADxxs, if no "trade secrets" involved. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Alias Listcat discrepancy betweeen sysplex'd LPARs
These LPARs do share a master catalog. LOADxx syscat has the same parm on both LPARs A listcat of the master shows the alias entry ALIAS -,SYS7.R30 Thanks, Elaine -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Alias Listcat discrepancy betweeen sysplex'd LPARs
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 robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mike Schwab Sent: Monday, June 10, 2019 12:54 PM To: IBM-MAIN@LISTSERV.UA.EDU 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 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 listSYS7.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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 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 listSYS7.R30.V22 > > > Thanks, > Elaine > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Alias Listcat discrepancy betweeen sysplex'd LPARs
Have you ever checked multi level alias definitions in the LOADxx members of both LPARs. There must be a difrence. If so you have to modify wrong one. Best Regards. Bülent Dülger Mainframe IT Specialist ServiZ Information Technologies Inc. > On 10 Jun 2019, at 21:23, Elaine Beal 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 listSYS7.R30.V22 > > > Thanks, > Elaine > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Alias Listcat discrepancy betweeen sysplex'd LPARs
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 listSYS7.R30.V22 Thanks, Elaine -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
