The only way that I am aware of (and I had to write this exact function for the
MXI G2 CICS plug-in) is to loop thru the TCBs in the suspect address space
hunting for the AFCX control block which is pointed to by TCBCAUF. To do this
you need to squirt an SRB into the suspect ASID and recover from any 0C4s (and
other nasties) that you are going to get snooping around.
It helps *hugely* if you have some site knowledge that narrows down the list of
possibles by using one or more patterns in the Jobname and/or some of the WLM
classes (service, report or workload).
Also be aware that CICS control blocks sometimes wear their "I LOVE JES2"
t-shirts and enjoy shuffling fields around and changing offsets between
releases - so any code you write in x-memory mode for CICS needs an "offset
table per release" approach.
Rob,
Thanks for that info. I don't think I want to run an SRB into every active
address space, and I don't know how to narrow it down to just suspects. I was
thinking it was probably some control block chain scan, such as I mentioned in
the original post about DB2. I would think there has to be a way.... Again,
thanks for the input.
--Dave
----------------------------------------------------------------------
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
