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



From past experience as a first-year operator, the SYSVAL does the
whole system, and yes, it works! =)

Assuming it was its own LPAR, that would be an effective solution.

There's also a PRTTXT parm on *JOBD that works for this. I've used
this on occasion for BRMS recovery reports to direct the printed
output to the correct person/location. Just specify that particular
*JOBD on the scheduled job, and BLAMMO, you've got custom text on each
page.

So - QPRTTXT is global. PRTTXT on a user's *JOBD is more granular.

jch

On Tue, Sep 16, 2008 at 3:07 PM, Steve McKay <steve.mckay@xxxxxxxxxxx> wrote:
You would need to test this but what about setting system value QPRTTXT to
"TEST TEST TEST . . ." ? This (according to 'Help') would print that string
"on the bottom of listings and separator pages" but I've never tried it . .
.

Steve

"Thierry Bernard" <tbernard@xxxxxxxxxxxxx> wrote in message
news:mailman.10984.1221592028.2545.midrange-l@xxxxxxxxxxxxxxx
Hello,

For our test environment, we would like to have a backgroud to every page
we print from there (ideally a big light grey TEST).

If possible, I would like something more visible than PRTTXT. Also we have
a few programs that override the printer file so it is not printed, so
that is only a partial solution.

As most of our printing goes through Host Print Transform (HPT), I was
thinking of using a custom WSCST that would setup a PCL macro overlay in
the :INITPRT section but so far it has not worked. I don't know if it's
my limited PCL knowledge or if I should place the macro elsewhere, or ...

Has anyone made this work or has another solution to identify test
printed output?

Thank you and have a nice day.
Thierry Bernard.
AVERTISSEMENT CONCERNANT LA CONFIDENTIALITE

Ce message, incluant ses pieces jointes, est strictement reserve a l'usage
de l'individu ou de l'entite a qui il est
adresse et contient de l'information privilegiee et confidentielle. La
dissemination, distribution ou copie de cette
communication est strictement prohibee. Si vous n'etes pas le
destinataire projete veuillez retourner
immediatement un courrier electronique a l'expediteur et effacez toutes
les copies.


CONFIDENTIALITY WARNING

This message, including its attachments, is strictly intended for the use
of the individual or the entity to which it is addressed
and contains privileged and confidential information. Disclosure,
distribution or copy of this communication is strictly
prohibited. If you are not the intended recipient please notify us
immediately by returning the e-mail to the originator and
deleting all copies.


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



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.