[2392] in Enterprise Print Delivery Team
RE: Request for New Web Interface Function Etc.
daemon@ATHENA.MIT.EDU (Rocklyn E. Clarke)
Thu Mar 14 19:06:53 2002
Mime-Version: 1.0
Message-Id: <p05010407b8b6e963b9ef@[18.152.2.129]>
In-Reply-To: <OF0AD31232.A329B1D9-ON87256B66.006882AE@boulder.ibm.com>
Date: Thu, 14 Mar 2002 19:06:48 -0500
To: "Dave Dow" <davedow@us.ibm.com>
From: "Rocklyn E. Clarke" <rclarke@MIT.EDU>
Cc: Enterprise Printing Delivery Team <PRINTDEL@MIT.EDU>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Hi Dave,
I would like to revisit an old topic momentarily. Lynne Durland has
noticed that the pdls command can be made to return a format value
for a print job. She tried out the following variation of one of the
pdls commands from mitjobs.pl:
pdls -cj -F -g -scol -rjob-state,destination-requested,format
pillage:1050600XXX
this gave her the following results:
held central-3hole, pdf
We understand from an earlier conversation with you and Dan that
format is an attribute of an individual print file WITHIN a print job
and not an attribute of the print job itself. It seems that pdls is
returning the format of the first print file within the print job by
default. Since all of our print jobs have only one print file, this
is probably adequate for us.
We still intend to implement the work that you did to display the
formats of multiple potential print files within a print job by
clicking on the print job itself. It would still be nice however to
have the format of the first (and for the forseeable future only)
print file in the job display in the initial listing of print jobs
along with the job name, owner, date, time, and byte count. Can you
add this to the code that you've already produced?
Rocklyn
-------
At 12:31 PM -0700 2/20/02, Dave Dow wrote:
>Hi Rocklyn,
>Sorry I didn't get back to you sooner about this.....
>I just finished your request to determine the format of the document
>on the Job Submission page. It took me a little longer than
>anticipated (6 hours) because I was trying to come up with the
>cleanest way of adding this code so we didn't have any new files to
>maintain and I spent additional time testing jobs with various
>special characters. The best way I came up with is adding a few
>lines in mit_jobs.pl and mit_ping.pl.
>
