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

Last month, I had a question about a keyed union of enrollment files for
multiple separate environment libraries of an application.

It turned out to be much easier to accomplish the goal by switching to a
single enrollment file in the application library, with the environment
added as a leading key to it and all its logicals.

But that opens another can of worms: now I have programs that need to
know which environment they're running in. Easy enough if the program
opens a file in the environment library, but not so easy if it doesn't.

But for a variety of other reasons, the application already sets the
Print Text of every one of its jobs to the environment library and TCP
port it's using. (Among other things, it makes it easy to find the
server jobs using a particular environment, so they can be held,
serviced, or terminated.)

Obviously, I can get the print text from a call to QUSRJOBI, format
JOBI0400, but is there another way to get it?

--
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.