Re: Creating Custom Printer Banner Page in DCPS?

• Previous message: JF Mezei: "Re: Creating Custom Printer Banner Page in DCPS?"
• In reply to: Paul Anderson: "Re: Creating Custom Printer Banner Page in DCPS?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Mon, 1 Aug 2005 21:50:27 -0500

"Paul Anderson" <paul.anderson@hp.com> wrote in message
news:010820051544499155%paul.anderson@hp.com...
> In article <FEtHe.6$c45.0@fe05.lga>, Christopher Story
> <ke6rwj@spam-eater-remove-me-msn.com> wrote:
>
> > Is there any method to manipulate the sections below. or is this in the
> > symbiont only?
> >
> > (TAZ::AAGAARD) username
> > (JOB 39) jobid
> > (DCPS$IVP_POST) name
> > (Hewlett-Packard Company) companyname
> > (OpenVMS Alpha V7.3-2 ) systemid
> > (DCPS F2.5) symbiontid
>
> I wouldn't think you'd really want to modify most of these, with the
> exception of "companyname". You're suggesting there be a way to
> eliminate the other items entirely, right?
>
> > I would need to add this PS variable:
> >
> > mark
> > (TAZ::AAGAARD) (DCPS$IVP_POST) {setjobinfo} stopped
> > cleartomark
>
> What would this do?

This variable supplies the imaging software with the job title and username
of the person who spooled it. So it can be placed in the proper
repository.(or directory structure, so the user can go see his/her jobs and
the titles)

>
> > I'm not expecting this to be fully supported, we are moving to an
> > imaging system for all output, and we need to provide the system some
> > consistent parameters so the jobs can be properly indexed.
>
> I understand your need to eliminate certain items from the flag page,
> but please explain what you mean by "consistent parameters" and
> "properly indexed".

The software is looking for the same parameters in the job from all the
systems that spool to it. It basically scans the job as it receives it and
looks for the PJL's or grabs the setjobinfo variable from the PS
interpreter. It then places this in a DB table that links it to a web based
viewer that allows users to grab the jobs that are spooled for them.
Without this info the jobs from DCPS are spooled to a "common" area that
requires human intervention to place them in the proper area. (so they don't
use it)

> > The other option is to add PJL commands to the LPS$$ppp_INITPSDEVICE
V2.5-1,
> > but I dont see a way to get the variables to the module.
> >
> > [ESC]%-12345X@PJL
> > @PJL JOB NAME="DCPS$IVP_POST"
> > @PJL SET USERNAME="TAZ::AAGAARD"
> > @PJL ENTER LANGUAGE=POSTSCRIPT
> > %!PS-Adobe
> > % © Copyright 1988-2004 Hewlett-Packard Development Company, L.P.
> > % LPS$$ppp_INITPSDEVICE V2.5-1
>
> DCPS ignores PJL commands. Sometimes, items like Username are put in
> the file as PostScript comments. DCPS does not generate these, but
> since some printers use this information, we've thought of adding such
> comments at the beginning of the file. Not all information about the
> job is available at that time, however, so it could never be a
> substitute mechanism for passing all flag page items.

Exactly my point.. The usernames are not available at the time the INIT is
sent so the comments cannot be added at the beginning, but using a PS
variable "(TAZ::AAGAARD) (DCPS$IVP_POST) {setjobinfo} stopped" they could
be available anywhere after the username for PS to grab.

Many printers also use the same type of variables to add the print jobs to
internal "printed jobs" lists.

adding the variable during the creation of the "(TAZ::AAGAARD) username"
text would allow this to work. If it is at all possible to edit the
generation on the flag page where the varables are passed in would be
excellent.

I appreciate your responses, I know this is outside of the design of the
system....

Chris

• Previous message: JF Mezei: "Re: Creating Custom Printer Banner Page in DCPS?"
• In reply to: Paul Anderson: "Re: Creating Custom Printer Banner Page in DCPS?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]