Re: Easiest way for a program to find out the PRTTXT ("print text") of the job it's running in?

In the pas when I have run into this I used the external indicators U1-U8. They can be accessed in any language and can be set on the job description (job switches).

Albert

----- Original Message -----
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Subject: Re: Easiest way for a program to find out the PRTTXT ("print text") of the job it's running in?
Date: Tue, 13 Oct 2009 13:34:31 -0700


rob@xxxxxxxxx wrote:

I don't suppose a File Information Data Structure is a
possibility to get the library name versus PRTTXT, is it?

No, because this particular program doesn't open any other files. But
retrieving an object description on something known to be in the
environment library is (and that's exactly what happens in another
program in the same application).

I think, since I'm already getting a JOBI0100 for another purpose, I may
as well bump it up to a JOBI0400, since both have the fields I'm already
getting. I was merely hoping that there was someplace I was overlooking,
where I already had that information.

And Chuck, if somebody is really enough of a doofus to go into a server
job and change the PRTTXT, then they deserve whatever malfunction they
might cause. After all, nothing is ever completely foolproof, because
complete fools are so ingenious.

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.