RE: Programmatically locating, and allowing response to message causing job *MSGW

Thanks, Simon.

Although I have read between lines on some older MI message threads and
think I know what to do, I have not made a system state program myself. (My
version of "display/manipulate another job's QTEMP" died a merciless death
because of this.) Anyway, it's almost certainly a problem for this
particular client but I will present it as an option.

Thank you very much for your thorough explanation. I'm OK to finding the
PCS if we go that route, and I think I can discern the rest if the client
has the inclination.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Nature gave man two ends - one to sit on and one to think with. Ever since
then man's success or failure has been dependent on the one he used most."
-- George R. Kirkpatrick


On August 15, 2010 7:49 PM, Simon Coulter wrote:

On 15/08/2010, at 11:03 PM, Dennis Lovelady wrote:

Think WRKSBMJOB or WRKACTJOB. Each of these is able to respond to
such
messages via option 7. That's what I want to emulate.

I see Bruce has pointed you at the necessary API but since you are on
a release without that then the following information may prove helpful.

It does require system-state so if that's a problem stop now.

The information you need (message queue, library, and message key) are
in
a) the WCB for the job
or
b) the WCBTE for the job
or
c) both of the above

I can't remember which one of those is correct and I'm about to leave
for Papua New Guinea so my host systems are unavailable. Anyway, the
location is pretty easy to find in dumps of the PCS or WCBT. You can
isolate the system-state stuff in a single program. You'll still need
to build all the code and panels to fetch the message details, display
the message, accept and send the response. You can get IBM code to do
that for you but you must use UIM for your panels, define some magic
variables, and provide a bit of system-state glue.

For method a)
locate the WCBT00
locate the WCBT index in WCBT00
locate the job in the WCBT index
locate the corresponding entry in WCBTn
locate the PCS for the job
and extract the message details


For method b):
essentially as above but you can omit locating the job PCS


Of course, you could extract this information from spooled file dumps
if your authorised to the DMPSYSOBJ command but that has all the
caveats of spooled file processing and it's slow.