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

It still sounds like a bug waiting to bite you. Like saying if the 7th
digit of a SKU is a '1' then do something (as opposed to having an
attached attribute).

Don't ask how I know that.....

jamesl@xxxxxxxxxxxxxxxxx 10/13/2009 4:10:40 PM >>>

However what I alluded to was the calling of any program which
might have the undesirable effect of changing the print text value
[i.e. with CHGJOB JOB(*)], not for some user invoking the CHGJOB
JOB(named). For instance, a "CALL CJD" coded in the application
might not currently issue a CHGJOB JOB(*) PRTTXT('CJD REPORT'), but
what controls are in place within the application development
environment to ensure that is not done in a future revision?

In this case, it's a "validation server" program, that runs as an
intermediate stage in the spawning off of a "child server" job. And
since neither it nor the server that spawns it prints anything other
than the occasional diagnostic, there's no reason to change the print
text.

--
JHHL