Re: WLM Couple dataset?

2023-03-09 Thread Mickey Virdi
On Thu, 9 Mar 2023 14:23:43 -0600, Mike Schwab  wrote:

>https://www.ibm.com/docs/en/zos/2.4.0?topic=command-displaying-workload-manager-information-wlm
>
>D WLM
>
>On Thu, Mar 9, 2023 at 2:19 PM Bill Giannelli  wrote:
>>
>> where can I find what the WLM Couple dataset is?
>> we need a policy updated and then the WLM Couple Dataset mirrored in our DR.
>> thanks
>> Bill
>>
>> --
>> 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




D XCF,CPL,TYPE=WLM  will also show which CDS is in use

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Orphaned SYSDSN Enqueue

2021-11-10 Thread Mickey Virdi
Is the owning ASID an INIT ASID, have you attempted to drain the init if it is?


> We have an orphaned SYSDSN enqueue that's preventing CICS from starting. GRS 
> shows it enqueued by the CICS STC that we're trying to startup. The ASID 
> that's being displayed is currently in use by a a different STC. Outside of 
> an IPL is there anyway to remove the enqueue from the sysplex?

>Mark Jacobs

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Content of the ISGLOCK structure

2021-08-12 Thread Mickey Virdi
Hello Alain,
GRS doesn't support ALLOWAUTOALT (via it's IXLCONN request).  The ISGLOCK 
str is purely a LOCK STR, it does not contain any record elements, so it will 
never fill.  If the structure is undersized, the worse thing that will happen 
is that your FALSE CONTENTION rate will increase. It'll be limited in the 
number of unique lock table entries, and multiple resources will more likely be 
hashed to the same lock table entry, causing XES to drive up signalling to 
determine if the contention on that lock table entry is "real" or "false", and 
it will more likely be "false" since your program is using unique qname/rname  
Hope this helps.
.
Mickey Virdi

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN