Re: MI solution for displaying another jobs LDA?

[SirJohn <jbuying@xxxxxxxxxx>]

I read a response and a thought fell into my brain.

This might work if you have the job msgq set with a break handing program.   
When
you send the job a message, it will break (suspending the current job) and give
control to the break handing cl program. The cl could now print/change the lda 
or do
just about anything to the job you like. You can add the breakhanding pgm by 
doing a
chgmsgq.

I use this trick to send my compile messages to the status line of my display
instead of having them break on me.

Maybe showing my age here, but I recall not being able to see what was in 
another
jobs qtemp.  I guess that looking at another jobs lda will be available in V9R3.

Hope that this helps


Jeffrey M. Silberberg wrote:

>   Paul,
>
>         Put a break handling routine in the CLP that controls the job,
> then when you have a problem send a msg to the job that triggers a
> routine to print, or dump to a dataq or what ever is needed the contents of
> the LDA with in the job.  You could even use this to instruct the
> executing job to change the LDA, job switches, or other attrib as
> necessary from within the job stream.
>
>         JMS
>
> On Thu, 6 Aug 1998 Qile@aol.com wrote:
>
> > Hello,
> > our business uses the LDA heavily to set up attributes for our many 
>warehouse
> > users scattered across the country.  Sometimes as part of troubleshooting a
> > problem we need to take a look at the contents of a users LDA.  Suffice to 
>say
> > it is not easy.  What normally ends up happening is that we change their
> > profile to LMTCPB(*NO), temporarily change the users password, sign on as 
>them
> > and then get to a command line to dump the lda, sign off and reverse the
> > process.
> >
> > Now it seems that it should be so simple to look at another jobs LDA, but 
>yet
> > it isn't (as far as I know).  I have heard rumors of MI programs that will 
>do
> > this.
> > If so does anyone have some sample code I could get? or at least some
> > guidelines as to how to do it. It would really make our tech support staff
> > happy (myself included).
> >
> > thanks in advance!!!
> >
> > -Paul Jackson
> > Tech Support Programmer
> > Costco Wholesale
> > Issaquah, WA
> > (425) 313-8594   Fax: (425) 313-6800
> > qile@aol.com
> > +---
> > | This is the Midrange System Mailing List!
> > | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> > | To subscribe to this list send email to MIDRANGE-L-SUB@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
> > +---
> >
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@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
> +---



--
John Buying
Strategic Business Systems, Inc.
300 Lake Street, Suite B, Ramsey, NJ 07446  USA
E-mail: mailto:jbuying@sbsusa.com   Phone: (201) EASY400 x145
Web:    http://www.sbsusa.com       Fax:   (201) 327-6984


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---