I am not sure what version of z/OS You are running.

However, there is no symbol for master cat.

It is in the LOADxx parms. 

So are you saying you switch your LOADXX parm with different MCATs on occasion?

You can always create a symbol in IEASYMxx for your system with your mcat name.

Lizette


> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Andrew Metcalfe
> Sent: Friday, February 10, 2017 7:13 AM
> To: [email protected]
> Subject: System Symbol For Master Catalog
> 
> I've obviously not had need for a symbol for the mastercat in the last 30
> years so when I went looking for it today I was surprised to find that there
> isn't one. Am I missing something?
> 
> Use case:
> 
> Healthchecker to perform checks against a mastercat in a 10-way sysplex.
> Six of the systems have individual mastercats and 4 have a shared
> mastercat/sysres.
> I want to use the symbol to define the name of the check in HZSPRMxx so that I
> don't have the same check executed 4 times for the same mastercat.
> 
> I tried defining the check (called VERIFY_MCAT) as GLOBAL for the 4 systems so
> only one instance would exist. This is managed by ENQ against
> SYSZHZS.ANDREW.VERIFY_MCAT - where ANDREW is the check owner.
> 
> However we switch mastercats at RSU maintenance cycles.
> 
> Assuming that SYSA running maintenance cycle A/mastercat A is the owner of the
> check, then the check is "dormant" on SYSB running maintenance cycle
> A/mastercat A as SYSA holds SYSZHZS.ANDREW.VERIFY_MCAT exclusive.
> 
> When SYSB is IPL'd on maintenance cycle B/mastercat B then the check will not
> run against mastercat B as SYSA holds SYSZHZS.ANDREW.VERIFY_MCAT exclusive.
> 
> If I incorporate the mastercat as part of the check-name I could solve my
> problem.
> 
> I have no problem in creating a RYO solution to define one but a symbol for
> the mastercat would have been nice!
> 
> Andrew Metcalfe
> 

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

Reply via email to