× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.