Displaying another jobs LDA

[John Carr <74711.77@xxxxxxxxxxxxxx>]

RE:     Displaying another jobs LDA

Paul
A couple of ways.  One way is to create a CL program which just looks like
this;
PGM
DSPDTAARA *LDA (which ever flavor *char or *hex)  *PRINT
ENDPGM
 
Then have a menu option or something to call this when ever you would like.

Or another way envolves REQUEST processing programs and setting the user's
message queue to break mode and then sending a *RQS type message to the 
message queue with RQSDTA(DSPDTAARA *LDA *PRINT) as the message.
This method however is not the most savory from a security standpoint.

John Carr
EdgeTech
-------------------------------------------
Hello,

We frequently find the need to determine what LDA value another job is using
for troubleshooting application problems.  At the moment this entails us
changing the user to LMTCPB(*NO) (to allow a command line), changing their
password, and then signing on as that profiles, then doing a DSPDTAARA *LDA
from a command line.

Does anyone know an easier way of looking at another jobs LDA without having
to change user profiles, passwords etc?

I have experimented with start service job on the job and then doing a DMPJOB
or DMPSYSOBJ, and it seems that within the hundeds of pages generated, the LDA
values are printed. This command takes so long though that it is not a viable
option for us.   

Does anyone know a faster way to get what we are looking for? I have played
around a bit with MI and am curious if there is a way that it can be used to
retrieve the LDA efficiently.

Thanks in advance,
-Paul Jackson
Qile@aol.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---