Using

1
Using IBMs InfoPrint Manager to print ANY
document to ANY printer
2
Have been involved in some aspect of printing
since 1992 Certified as EDP in 1996 Currently
System Analyst with Moore Wallace, a Division of
R. R. Donnelly Personal goal is to print ANYTHING
to ANY PRINTER As the System Analyst, my goal is
to get the jobs our clients send in out the back
door quickly, efficiently, and with NO
ERRORS. I am very proud of what I have
accomplished over the last 5 years, and want to
share with others some of the tricks I used to do
this.
3
The beginning Started with Moore in August,
1999 Was introduced to my first InfoPrint Manager
Server Comment WHAT IS THIS? I had never
seen UNIX before, much less AIX or InfoPrint
Manager It AINT XEROX!!! IBM did not do a good
job of training, so I spent a great deal of time
with an on-site IBM consultant InfoPrint Manager
needed to drive two IBM IP4000 printers By
January, 2000, the associates were comfortable
enough with the system to start using it Most
challenges were my lack of experience
4
Next challenge Now that I know how to install it
and make it usable for AFP printing, whats
next? What about AFP to Xerox printers? What
about DJDE/metacode to IBM printers? What about
PostScript, PCL, and PDF to both Xerox and IBM
Printers? We currently have IBM 4000 lines, Xerox
4890s, Xerox 92Cs, Xerox 4635s, and Xerox
DP180s. Well, we install the IPS front end on
all of the Xerox printers to handle the AFP. We
also have the NPS software loaded on most of the
Xerox printers. IBM printers talk directly to
the InfoPrint Manager Software, and the Xerox IPS
software allows Xerox printers to talk to the
InfoPrint Manager. Very nicely, too
5
First Order of Business AFP!
Running AIX 5.2 and InfoPrint Manager 4.1 on the
servers. The NPS/IPS front end is being migrated
to version 8.1.4. Turns out the Xerox IPS system
will accept highlight color AFP on the 4890s and
92Cs Recent purchases of DP180 printers include
just the NPS/IPS front end, without LCDS This
works great, especially for jobs that pull from
multiple input bins So, when we purchased our EPS
system, I stated we didnt need LCDS, saving the
company money Our only EPS system will run
PostScript Level 3, PDF, and PCL jobs, and has
the IPS extender. InfoPrint Manager will take
in AFP data (line data, MODCA) and convert it to
IPDS the actual AFP language that the printers
speak. That then goes directly to an IBM 4000
printer, or it goes to the Xerox IPS
software. Oh, one other thing, we were heavily
tape based for input. Now we want to be tapeless.
6
Tape versus Tapeless NO CONTEST
Input via tape using IBMs SMIT panels while it
worked, it wouldnt give us a decent job name no
matter what we tried. I realized early on that I
could get job names directly from file names, if
we could convince folks to go this route. Had
some issues convincing folks, so I started to
write Korn Shell Scripts that would allow us to
take a tape and write the contents to a file.
Then I would issue the InfoPrint Manager print
command against that file. This allowed us to
give the job a decent name, and also allowed for
some tracking. FINALLY, folks stepped on board
and a heavy migration to tapeless is now
underway, scheduled to be completed by the end of
this year. I have taught myself many of the
commands, and the IBM InfoPrint Manager Reference
Manual is my best tool right now. Course, there
are only 5 of us writing Korn Shell Scripts to
handle a multitude of clients, and the intent is
to migrate these to PERL scripts in the future.
For now, though, what we have WORKS, and is
really quite good!
7
File name when submitted from a tape -
/var/psf/seglist/tapeFqfyNh.0.N.FCN0753.CRITE04.09
67 File name when submitted from a file
(tapeless) - THUP.SMR.CLIENT6719.STMT.CONFS6X9.C01
CN.CR01 InfoPrint manager uses its own version
of lpr called pdpr to submit jobs to a
logical printer queue. That command gives us a
lot of flexibility for reporting certain
information back to a log file or via email to
specific project managers. Each client has what
we call a configuration file that consists of a
series of attributes for that job. This
information consists of Form Definitions, Page
Definitions (if needed), locations of fonts and
resources, number of copies, and alignment on the
page (X,Y coordinates). Operators want to see the
number of pages in a file when we submit a job.
Well, this was a little tricky, but I discovered
the afpdmp command, which dumps an AFP file and
counts the number of BPG commands it finds.
This information is now shown in the Operator
GUI. The Operators know how much paper they
need, and compare the information to their job
requests.
8
Pagesafpdmp JobName grep BPG wc -l echo
"JobName has Pages" gtgt logFile pdpr -d
Printer-lp -X config -x "job-nameprintName"
-x "notification-profileevent-identifiersjob-co
mpleted job-cancelled-by-operator
past-discard-time job-discarded
delivery-address/thuprod/client/log/clientlog
delivery-methodfile-add-to" -x
"job-page-countPages" -r brief gtgt logFile
runName As you can see, there is a lot of things
indicated in the pdpr command. We are telling it
which logical printer to use, which
configuration file to use, job name, some job
information that we are going to log, and
detailed information on what was actually
submitted to the queue is also placed in the log
file. The last variable - runName is the name
of the file itself. More detailed information on
the pdpr command is included in the handout.
9
What else do we keep track of in the log? Between
the Korn Shell Scripts and the print command, we
have developed a pretty robust tracking system
of the jobs we send out through InfoPrint
Manager. At any given time, someone can give me a
file name and I can determine if the file imaged,
was deleted, etc. I know who submitted jobs, when
they submitted them. How many pages are in the
file (as long as its AFP and not Line Data). I
know if a file printed, or if the operator
cancelled the job. I know if a job was rerun. I
dont track test files, but there is another
trick I used to determine if a test file was
imaged. I know what printer the Operator
submitted the job to. Recently I added a step
that prompts the operator for a reason for
rerunning a file. They are given 6 choices, and
depending on what they respond is what is put
into the log. Oh, the last choice gives them a
space to fill in their own reason. This has
helped cut down on files being imaged, and also
helps us determine what the operator was doing at
the time. An example of our log file is part of
the handout.
10
Recently I discovered a way of reporting back to
everyone just what jobs imaged during a given
shift. This is also an IBM command pdaccount
and we have an automated script that will run at
the beginning of each shift and list the jobs
that imaged during the previous shift. This
information looks like this Report from 214010
7/6/04 through 94010 7/7/04 Printer,UserID,Date
Completed,Time Completed,Pages Completed,File
Name C72,tosms1_at_ipw1,07/07/04,051024,9194,THUP.F
IN.CLIENT3089.NOTI.AFP.CRITE.FI001 C72,tosms1_at_ipw1
,07/07/04,063652,2288,THUP.FIN.CLIENT4089.LTRS.C
RITE01.MA01 C71,tohlb1_at_ipw1,07/07/04,091851,355,
THUP.FIN.CLIENT4135.ANNV.BRKRB912.C01BR.CR02 C71,t
ohlb1_at_ipw1,07/07/04,091205,7392,THUP.FIN.CLIENT4
135.ANNV.PARTA10.C01PA.CR01 C71,tohlb1_at_ipw1,07/07
/04,001541,43,THUP.FIN.CLIENT0765.ADVC.CRITE01.C
01MB.DM2 As you can see, its a comma separated
file and includes the printer ID, the User, the
date and time, the number of pages, and the file
name itself. A GREAT tool and helps determine if
we did image the correct number of pages. The
command looks like this pdaccount -t all -s
Start -e Current gt kathy.one Where I request
all of the jobs starting at a certain time and
ending at the current time. That goes to a file,
which is then sorted by file name and emailed out
to folks that have requested this information.
Its all done with Korn Shell Scripts, and some
PERL scripts as well.
11
Problems? Very few But, if we do have problems,
and receive error messages from the printer, we
lucked out with a tool that comes with InfoPrint
Manager. The printer may have issues with
printing pages of a file. Thats why all of our
configuration files have error reporting set to
all - this requests that all data errors be
reported FROM the printer TO the server. The most
frequent one is printing outside the printable
area and usually causes a black box to be
printed on the page. IBM supplies a tool that
allows us to determine just exactly what a
problem is. That tool is called pdmsg.
(Thank heavens for the IBM (or is it UNIX)
command of man. Now if Xerox could only give
me a tool to make debugging IPS and NPS easier I
have taken one error message and performed the
pdmsg command against it. The result of this
action is part of the handout.
12
man pdmsg pdmsg Utility Displays Information
about a Message Syntax pdmsg -d -t
MessageNumber Description The pdmsg utility
displays the text and description of an Infoprint
message at the command line. The pdmsg utility
extracts the text and description from the
appropriate message catalogs. If you do not
specify the -d or -t flag with the utility,
Infoprint displays both the text and the message
description.
13
As for PostScript, PCL, and PDF? Well, if its
PostScript Level 2 or PCL, and requires highlight
color, then we use the NPS front end thats the
only tool right now that will handle the
highlight color (which has issues in its own
right). If its monochrome, then we can take
any level of PostScript and PCL and convert it to
AFP images using InfoPrint Manager. These then
are sent to IPS or IBM printers, and images just
fine (providing things are set up correctly, that
is). The only way we handle PDF is through
InfoPrint Manager, again ripping the file to AFP
images. Oh, we tried the Xerox EPS system, but
found it difficult to manage and to train the
Operators on its use. Remember, service bureaus
have a lot of temp workers, and we need
something easy to train and use!
14
First up Get a job to Xerox NPS using the IBM
InfoPrint Manager Server
AND do it in such a way that is easy for the
Operators
The Xerox NPS/IPS software comes with a client
for printing from Windows and even from AIX. So,
we grabbed that and installed it on the InfoPrint
Manager server (which IS AIX). That gave us a
command called print, which we then renamed to
xprint. After that it was easy to add Korn
Shell Scripts to make this work just like other
tapeless jobs that our operators are
submitting. The actual printing command
itself is part of the handout for this session.
15
Speaking about COLOR in PostScript and PCL!
Well, you cant run highlight color PostScript,
PCL, or PDF through InfoPrint Manager and expect
color in the NPS front end. So, the ONLY way you
can handle color PostScript and PCL is by sending
the file to the Xerox NPS front end. That gets
tricky in this day and age of desktop publishing.
Folks get nice colors on their screen, and
expect the same things out of their printer.
Thats fine for desktop color printers, but it
doesnt translate well in the world of Xerox
Highlight Color printers. So, while the
technique on the previous page will send a color
file to the NPS printer, it wont necessarily
look the way the client wants it to look. No
matter what you try, you will have to experiment
with a host of options on NPS in order to get
close (emphasis on the word CLOSE) to what they
will accept. The different options you have to
change or play with are part of the handout.
Lets just say that this would be a whole session
by itself. Its not easy, its very time
consuming, but it IS possible!
16
Using IBMs InfoPrint Manager for PostScript,
PCL, and PDF
This works very well for jobs that have no color
in them. And it takes all the PostScript
languages. Its the only way we have of printing
PDF files at this time. We have clients that we
use this technology for today. There is one
InfoPrint Manager gotcha. There is a default
configuration file, located in the
/usr/lpp/psf/ps2afp directory, that looks
something like this
17
ps2afp configuration file KEYWORD
EQUIVALENT ps2afp FLAG
PURPOSE
port 8251
-P which TCP/IP port to
use server 127.0.0.1 -S
which server to connect with ps_max_memory
24000K -M maximum amount of memory
that
PostScript uses the 'K' is ignored ps_job_timeout
9999 -j maximum number of
minutes
to process PostScript job ps_server_timeout
360 -s maximum number of
minutes
server waits between jobs ps_width 8.5i
-w width of generated
image ps_length 11i -l
length of generated image ps_x_offset 0i
-x left and right
margins ps_y_offset 0i -y
top and bottom margins ps_resolution 300
-r resolution of target
printer ps_output_type IO1_G4 -a
type of AFP image to generate See that
highlighted item? You have GOT to watch this.
Trust me, it used to have a default of 240, and
our output looked terrible. Now, you dont want
to have to change this every time, so we build a
file much like the one we use for AFP that has
this entry in it. The handout has some sample
configuration files to handle this issue, among
others.
18
DJDE/Metacode? Another story entirely
InfoPrint Manager Server was originally
purchased with IBMs Xport Product. Worked very
well for monochrome printing, but not at all for
highlight color printing. Facility objective was
for all AFP printing, but not to lose those
applications that were DJDE/metacode. Xport to
AFP works very well for BLACK jobs only. It
cannot convert highlight color commands.
Recently, Moore Wallace acquired a new transform
product from Crawford Technologies. This product
allows our Composition Team to actually set up
jobs to transform. We use it to take
DJDE/Metacode jobs to AFP, and it actually will
handle highlight color calls! Crawford is also
used to transform AFP back to metacode, or to
PostScript, etc.
19
The Process
A job is DJDE/metacode, and in Thurmont we want
to print AFP. The Resource Management folks write
an ini file and test out the transform and the
final printing of the transformed file. The name
and location of the ini file is sent to me. I
take the transform and using Korn Shell Scripts,
automate the transform and send the resulting
output files and log files to different locations
on the network. If the transform is successful,
the output file is placed in a directory where
the operators will later pull it for printing.
If the transform is NOT successful, a report is
printed to the Operator area, and an email is
sent to the Resource Management Team. The output
file is deleted and the original file is moved to
a different location. The process is automated by
using the AIX crontab program. This watches a
directory and when it senses a file it transforms
it and sends the files to the correct
places. Operators then pull the jobs, using the
same menu systems we set up for AFP printing, and
send them to the printer they want to use.
20
The Resource Management team also create the
configuration file for the AFP output so that we
can plug into the pdpr command the correct
information. Oh, once the AFP file is generated,
the job is treated just like any other AFP file
that we may receive from a customer. We
calculate the number of pages, the operator pulls
the file the same way, everything is the
same. Its just that one extra step between
DJDE/metacode and AFP. And that is handled in
the background. We also have set up a process for
the Resource Management team that they can use
for testing ini files if changes need to be
made. To be honest, I really am not involved in
setting up the transform itself. All I do is
write the scripts that automate the process. Good
thing Korn Shell is so easy! Hmm I wonder if
PERL will be as easy, since that is the direction
we are heading!
21
What we affectionately call The Crawford
Transform Process is very easy, painless, and
works just great. Im particularly impressed with
the output for the highlight color jobs. - No,
Im VERY impressed! We have converted about 10
jobs so far, and more are coming. Current testing
is to take the AFP output and use it for a
damaged piece process, convert the DJDE/metacode
to PostScript, convert an AFP file to
DJDE/metacode or PostScript, etc. This is so we
can share the load between facilities that have
different technologies! IT IS WORKING!!! And
thats coming from a rather large skeptic who
started out thinking it was going to be really
hard to do this!
22
I know what you are thinking What DOES the
Operator see?
They open a terminal window on AIX. Then they
key in main After that, its all kinds of
things!
trkmr1_at_ipw1/home/trkmr1gt main
23


MOORE BCS THURMONT
FACILITY COMMERCIAL
JOBS MAIN MENU



1 CLIENT ONE
2 CLIENT TWO
3 CLIENT THREE
4 AND THE
LIST GOES ON! X
Exit This Program


ENTER THE REFERENCE NUMBER OF THE
DESIRED PROCESS
24



PRODUCTION JOBS




1 RUN STATEMENTS
2 RUN DOCS
3 RUN TRUST
4 RUN
JOBS
X Exit This Program




ENTER THE REFERENCE NUMBER OF THE
DESIRED PROCESS
25



SELECT THE ORDER NUMBER FOR THE JOB



1) 0751
2) 0752
3) 0753
4)
0755
5) 0756
6) 0786



Enter the reference number of the
Run Order Number.
Or Enter an 'x' to return to the
Main Menu.
26
VVVVVVVVVVVVVVVVVVVVVV
VVVVVVVVVV VVVVVVVVVVVV
VVVVVVVVVVVVVVVVVVVVV
VVV JOBS AVAILABLE FOR PRINT
VVV VVVVVVVVVVVVVV
VVVVVVVVVVVVVVVVVV
VVVVVVVVVVVVVVVVVVVVVVVVV
VVVVVVVV VVV These Files are
Currently Available VVV
VVV 1) THUP.FIN.CLIENT0751.RETS.BLACK.C01FN
.CK01 VVV VVV 2)
THUP.FIN.CLIENT0751.RETS.BLACK.C01MA.CK01
VVV VVV 3) THUP.FIN.CLIENT0751.RET
S.BLACK.C01MO.CK01 VVV VVV

VVV VVVVVVVVVVVVVVVVVVV
VVVVVVVVVVVVVV
VVVVVVVVVVVVVVVVVVVVVVVVV
VVVVVVVV Enter the reference
number of the file to be printed.
Or Enter an
'x' to return to the Main Menu.

27
Please enter the printer you would like to use
C60 C61 C63 C67 C68 C69 C70 C71 C72 C73 C74 C75
COMP IP40 or X to exit this menu ip40
28
This is a warning box. This appears if somehow a
file is still in the main directory and the
operator tries to image it. We check to see if
the file had been imaged before, and throw this
up. The operator cannot go any further, and they
have to check to see if the file should be imaged
again.
WARNING WARNING WARNING WARNING WARNING WARNING
WARNING WARNING WARNING WARNING WARNING WARNING
WARNING WARNING WARNING WARNING WARNING WARNING
WARNING WARNING WARNING

WARNING WARNING RUN.THUP.KMR.CLIENT1.PRIM.
TBA.MISS01V5.DMG.afp WARNING WARNING
WAS PRINTED ON SERVER ipw1
WARNING WARNING BY trkmr1
TO PRINTER IP40
WARNING WARNING DATE - 07/29/04 TIME -
1027 WARNING WARNING

WARNING WARNING TYPE THE ENTER
KEY FOR A NEW JOB NUMBER
WARNING WARNING
WARNING WARNING
WARNING WARNING WARNING WARNING WARNING WARNING
WARNING WARNING WARNING WARNING WARNING WARNING
WARNING WARNING WARNING WARNING WARNING WARNING
WARNING
29
Finally, our two caution boxes. Used when the
operator wants to rerun a file. First box asks
if they want to do it. Second box asks for a
reason, which is logged in the log file.
Caution Caution Caution Caution Caution Caution
Caution Caution Caution Caution Caution Caution
Caution Caution Caution Caution Caution
Caution Caution
Caution Caution
THUP.FIN.SQB0786.STMT.BANKSG.C01CR.CR01
Caution Caution WAS PRINTED ON SERVER
ipw1 Caution Caution
BY trkmr1 TO PRINTER IP40
Caution Caution DATE- 07/29/04 TIME
- 1606 Caution Caution

Caution Caution Caution Caution Caution Caution
Caution Caution Caution Caution Caution Caution
Caution Caution Caution Caution Caution Caution
Caution DO YOU REALLY WANT TO DO
THIS (Y/N)
30
Caution Caution Caution Caution Caution Caution
Caution Caution Caution Caution Caution Caution
Caution Caution Caution Caution Caution

Caution Caution WHAT IS THE REASON FOR
THIS RERUN? Caution Caution
Caution Caution
1) REQUESTED BY PROJECT MANAGER
Caution Caution 2) SETUPS FOR INSERTING
Caution Caution 3) PRINTER
ISSUES Caution Caution
4) JOB CANNOT BE FOUND IN THE FACILITY
Caution Caution 5) COMPONENT ISSUES (wrong
drawer/mixed) Caution Caution 6) ANOTHER
REASON NOT LISTED HERE Caution Caution

Caution Caution Caution Caution Caution Caution
Caution Caution Caution Caution Caution Caution
Caution Caution Caution Caution Caution
ENTER THE REFERENCE NUMBER OF THE REASON
31
Benefits? Can send jobs to every printer we have
in house, no matter what the language If a server
goes down, the printers can be defined to another
server and back up and running in a matter of
minutes If a printer has a problem, jobs can be
easily sent to other printers Necessary in
todays environment to be able to move things
around on an as-need basis Use of NPS for
PostScript Level 2 working very well. Use of
InfoPrint Manager for monochrome PostScript (no
matter what the level), PCL, and PDF is
fantastic. And allows me to use the same menu
system that we use for AFP jobs, which makes
Operator Training much easier. Ability to report
each step of a script to a log file has proven to
be invaluable!
32
Challenges? Besides the constant YOU CANT DO
THAT, and me proving them wrong Actually,
everything works pretty smooth Always able to
work out the problems in a timely manner Course,
neither IBM nor Xerox gets away with telling ME
that it cant be done Well, the biggest one was
figuring out why the quality of the image from
InfoPrint Manager was so bad for PostScript, PCL,
and PDF. Use of EPS for PostScript Level 3
becoming a bit of a challenge Xerox sometimes has
issues with their IPS software New tapeless
initiative has turned me back into a Programmer.
33
The future Full migration of tape input jobs to
tapeless Continue writing the scripts that make
the Operators jobs so easy. And the
documentation that goes along with those
scripts. Learn DB2 and InfoPrint Workflow to see
if I can make certain reporting requirements work
correctly. We have the products, but are not
using them at this time. I know they would be
helpful, but I have to train myself on them in
order to do what we need to do. Learn PERL
programming so that we can fine tune things after
the initial tapeless push is complete. And to
handle any and all problems that may come up Not
to mention, to hold on to my title of InfoPrint
Manager Goddess!
34
Kathy Rixham, EDP Systems Analyst -
Production Moore Wallace a Division of RR
Donnelly 1 Poplar Street Thurmont MD
21788 301-271-5719 kathy.rixham_at_rrd.com
35
Using IBMs InfoPrint Manager to print ANY
document to ANY printer SPECIAL HANDOUTS
36
The pdpr command
37
pdpr -d Printer-lp -X config -x
"job-nameprintName" -x "notification-profileev
ent-identifiersjob-completed job-cancelled-by-ope
rator past-discard-time job-discarded
delivery-address/thuprod/client/log/clientlog
delivery-methodfile-add-to" -x
"job-page-countPages" -r brief gtgt logFile
runName -d Printer-lp. Our Korn Shell Scripts
are quite detailed, and as the Operator pulls the
job they are quizzed about different things. One
of these items is the printer name. They are
asked, and they enter. That information is
plugged in here. The lp means we want the
script to pick up the defaults from the logical
printer. -X config This is a separate file
that contains information that will be applied to
every job for this client. It contains such
things as a Form Definition and how to report
errors. The capital X indicates its a file.
The lower case x in the next few lines indicate
its a command. -x job-nameJobName This is
how we actually give the job a decent name. And
we are using the file name itself, since thats
how we are going to reconcile the fact that we
actually imaged the job, and didnt just delete
it!
38
pdpr -d Printer-lp -X config -x
"job-nameprintName" -x "notification-profileev
ent-identifiersjob-completed job-cancelled-by-ope
rator past-discard-time job-discarded
delivery-address/thuprod/client/log/clientlog
delivery-methodfile-add-to" -x
"job-page-countPages" -r brief gtgt logFile
runName -x notification-profile We are
looking for certain things to be captured in a
log file for each job. This is such things as if
the job completed, was cancelled, when it was
discarded. The delivery address indicates the
name of the log file this information is sent to
for this job. We went over the job page
count. The r brief to the same logfile will give
us certain information in the log. That
information looks kind of like this
Current Destination Destinations Job ID
Name State
Requested Assigned ---
------------------- -----------------------------
------- ----------- ------------ 31
infoprt26527500142 THUP.FIN.CLIENT9007.CONT.CRIT
E01 held IP40-lp Because InfoPrint Manager
uses the Job and the ID more then the job name,
and since we want to know if a job completed or
was cancelled, I discovered that this little tool
will give me information that I can cross
reference. Hey, its great and it
works! runName is the name of the file that we
are submitting to the printer.
39
Sample Configuration File (or as IBM calls it
- the Attributes File)
40
results-profile1
Number of
copies1 form-definitionF19000
Form
Definition to use resource-context-form-definition
/resource01/Prod/AFP/103290003 Location of
the Form Definition resource-context-font/resourc
e01/Prod/AFP/103290003
Location of the Fonts resource-context-overlay/re
source01/Prod/AFP/103290003
Location of the Overlays resource-context-page-seg
ment/resource01/Prod/AFP/103290003 Location
of the Page Segments maximum-messages-printed9999

Print ALL error messages data-fidelity-problem-rep
ortedall Report all
print-positioning or invalid-character errors Or
like this results-profile 1
Number of copies
1 document-formatline-data carriage-control-type
none new-line-optionrecord,4200 form-definitionF
15000
Form definition page-definitionP15000
Page
definition resource-context-form-definition/resou
rce01/Prod/AFP/893350004 Location -
formdef resource-context-page-definition/resource
01/Prod/AFP/893350004 Location -
pdef resource-context-font/resource01/Prod/AFP/89
3350004 Location -fonts resource-cont
ext-page-segment/resource01/Prod/AFP/893350004
Location - psegs resource-context-overlay/resour
ce01/Prod/AFP/893350004 Location -
overlay maximum-messages-printed9999
Print ALL
messages data-fidelity-problem-reportedall
Report ALL data problems
41
Sample of Moore Wallace Job Log File
42
What else do we keep track of in the
log? 05/26/04 1336PMgt trkmr1 on ipw1 starting
the Imaging Process 05/26/04 1337PMgt trkmr1 has
selected THUP.KMR.TEST122.CSFS.CRITE01.C0101.CR01
for ipw1.
Current Destination
Destinations Job ID Name
State Requested
Assigned --- ---------------
---------------------------------------- -------
----------- ------------ 22 ipw10277400178
THUP.KMR.TEST122.CSFS.CRITE01.C0101.CR01 held
IP40-lp 05/26/04 1337PM gt
RUN.THUP.KMR.TEST122.CSFS.CRITE01.C0101.CR01 was
copied to /thuprod/client/backup
successfully. 05/26/04 1341PMgt trkmr1 on ipw1
starting the Imaging Process 05/26/04 1341PMgt
trkmr1 has selected THUP.KMR.TEST999.CSFS.CRITE01.
C0101.CR01 for ipw1.
Current
Destination Destinations Job ID
Name State
Requested Assigned --- ---------------
----------------------------------------
------- ----------- ------------ 23
ipw10277400179 THUP.KMR.TEST999.CSFS.CRITE01.C01
01.CR01 held IP40-lp
05/26/04 1358PMgt trkmr1 on ipw1 beginning the
Rerun Process Job THUP.KMR.TEST122.CSFS.CRITE01.C0
101.CR01 is being rerun for this reason question
pm about problems, job was deleted by prior
shift 05/26/04 1359PM gt trkmr1 has decided to
rerun (t122.csfs.crite01.c0101.cr01).

Current Destination Destinations Job
ID Name
State Requested Assigned
--- --------------- --------------------------
-------------------- ------- -----------
------------ 25 ipw10277400184
RERUN.THUP.KMR.TEST555.CSFS.CRITE01.C0101.CR01
held IP40-lp 05/26/04
1401PMgt trkmr1 decided to exit the
clientrerun.menu with no processing. From ipw1
05/26/04 141609 5010-196 Job 26
(ipw10277400187) was cancelled by the operator
or administrator. From ipw1 05/26/04 141610
5010-196 Job 23 (ipw10277400179) was cancelled
by the operator or administrator. From ipw1
05/26/04 141750 5010-071 Job name
THUP.KMR.TEST555.CSFS.CRITE01.C0101.CR01 with ID
24 (ipw10277400182) completed successfully on
IP40. 06/04/04 1426PM gt RERUN.THUP.FIN.client0696
.CSFS.CRITE03.C0303.CR03 has 1088 pages in
the file.
43
Using the Xerox Print Command (or, as we call it
- Moore Wallaces xprint command)
44
xprint -p client600 -server Printer -title
printName runName - (This actually sends the
job to the NPS printer) sleep 10 (Waits
for 10 seconds) listjob -server Printer
-l -n 10 -p client600 gtgt /thuprod/one_off/log/NPSj
obs.Printerdate "HM" - (ListJob is another
command that installed with the Xerox Client
Software. It will give us a list of the last 10
jobs submitted to this printer. It then places
that information in a log file on the server
where we keep a running tab of information on the
client.)
What we are doing is issuing the print (xprint)
command. The p client600 is the virtual printer
name on the NPS printer. The server Printer is
the actual physical name of the printer we are
using. Then we give the job a title of the job
name, which shows up in NPS when we issue a list
documents command. The runName is the name of
the file we are sending to NPS. The listjob
command goes against the actual physical printer
(-server printer). The l command is for the
long format option. It will display the job
name, sender name, number of copies, file size,
submission time, job id and status. The n 10
command will list only the last 10 jobs. And the
p client600 will list only those jobs for that
particular virtual printer. The redirection (gtgt)
of the output just sends the information to a log
file which we name with the physical printer name
and the date. All very easy, once you have
figured it out! Works great for PostScript Level
2 jobs and PCL jobs, with or without color in
them.
45
Sample InfoPrint Manager Configuration Files for
PostScript, PCL, and PDF
46
This is the PostScript configuration file for
Client123. results-profile1
For Multiple Copies, change the 1 to the number
desired plexsimplex sides1
Indicates this is a simplex job image-width9.5i
Image Width - 9.5 inches
image-length11.00i Image
Length - 11 inches x-image-shift0
Image Shift on x axis if needed - NO
SHIFT on this job y-image-shift0
Image Shift on y axis if needed - NO SHIFT
on this job job-rip-actionrip-and-hold Rip
the job for errors, but dont start
printing job-holdfalse Dont hold the
job in the queue because we want it to
RIP. job-retention-period0100 Hold job
in retained jobs for 1 hour after it
print default-printer-resolution300 Default
Printer Resolution for the printer In this file
we can define the size of the paper and the
resolution. Which sometimes will be 600 dpi or
even 1200 dpi. It does work, and the output
looks really good. Oh, the PostScript
configurations are the same no matter what level
of PostScript, and they are also used for PDF.
47
There is a similar configuration file for PCL in
the /usr/lpp/psf/pcl2afp directory. And you can
create similar attributes files like we have for
PostScript pcl2afp configuration file
KEYWORD EQUIVALENT pcl2afp FLAG
PURPOSE
port
8253 -P which
TCP/IP port to use server 127.0.0.1
-S which server to connect
with pcl_max_memory 6000K -M
maximum amount of memory that
PCL uses the 'K' is
ignored pcl_job_timeout 20 -j
maximum number of minutes
to process a PCL
job pcl_width 8.5i -w
width of generated image pcl_length 11i
-l length of generated
image pcl_x_offset 0i -x
left and right margins pcl_y_offset 0i
-y top and bottom
margins pcl_resolution 300 -r
resolution of target printer pcl_output_type
IO1_G4 -a type of AFP image to
generate Its unfortunate that we cant take in
color files for this process, but its one we
have learned to live with. We have also found
that files created on desktops dont always come
out looking like they would on an HP printer when
color is involved. Maybe with full color
printers it would be better, but we dont have
full color printers at this time.
48
Oh, the setup of the Xerox NPS Virtual
Printers Dont be scared - it IS as bad as it
looks!
49
PS-opgt List Virtual Printers Kathy Kathy
Status started Attribute
HighlightColorMismatchAction, useLoadedColor
Attribute Resolution, 600 Attribute Plex,
duplex Attribute HighlightColor, Blue
Attribute Staple, noStapling Attribute
HighlightColorRendering, colorToHighlight
Attribute Media, UsLetterwhite20
Attribute PrinterName, Kathy PS-opgt Change
Virtual Printer Kathy Enter the attribute name
Enter the attribute name (ASCIIFontName,
ASCIIFontSize, AccountInfo, AutoTabShift,
BackgroundForm, Category, ColorCalibration,
CopyCount, CycleExceptions, CycleForms,
DFADivertStackerGroup, DFAMaxSetPolicy,
DFAMaxSetSize, Disposition, DocumentEndMessage,
DocumentFormat, ElideHeader, ExceptionPages,
FlipSide, Halftone, HighlightColor,
HighlightColorMismatchAction, HighlightColorRender
ing, Hold, HorizontalImageShift,
HorizontalImageShiftForBack, IPDSContinuousEmulati
on, IPDSGOCAImageResolution, IPDSResolution,
ImpositionScheme, MICRMode, MapColor, Media,
OffsetPerCopy, OffsetPerJob, Orientation,
OutputBin, PageOrder, PageRange, Plex,
PlexChangesDynamic, PreferredTray, Priority,
QuotaPages, QuotaSeconds, RecipientName,
RenderingIntent, ReprocessForCopies, Resolution,
SkipJTPrescan, SkipXIPP, SkipXPIF, Staple,
Thicken, Uncollated, UndefCMYK, UndefGray,
UndefRGB, UserTRC, VPComment, VerticalImageShift,
VerticalImageShiftForBack)
50
PS-opgt Change Virtual Printer Kathy Enter the
attribute name HighlightColor Enter the
attribute value (Black, Red, Green, Blue, Cyan,
Magenta, Yellow, Cardinal, RoyalBlue, Ruby,
Violet, Brown, DontCare, Other) Cyan Attribute
HighlightColor (old value Blue) has been set to
Cyan for VP Kathy Enter the attribute name
HighlightColorMismatchAction Enter the attribute
value (abortPrint, useLoadedColor,
requestOperatorIntervention) useLoadedColor
Attribute HighlightColorMismatchAction (old
value useLoadedColor) has been set to
useLoadedColor for VP Kathy Enter the attribute
name HighlightColorRendering Enter the attribute
value (pictorial, presentation, colorToHighlight,
colorTables, automatic, defaultRendering)
colorToHighlight Attribute HighlightColorRenderin
g (old value colorToHighlight) has been set to
colorToHighlight for VP Kathy Enter the attribute
name MapColor Enter the attribute value (Black,
Red, Green, Blue, Cyan, Magenta, Yellow,
Cardinal, RoyalBlue, Ruby, Violet, Brown,
DontCare, Other) blue Attribute MapColor has
been set to Blue for VP Kathy So, you can see
there are lots of options, lots of decisions, and
lots of configurations to try before you will get
it right. Best thing is to get the client to
agree to ONE color, which you can map to the
highlight color. Other then that, you will spend
plenty of time trying to get this to work
correctly. I havent found an easier way Have
YOU?
51
Thank Heavens for the IBM pdmsg command
52
pdmsg 0420-485 0420-485 The actual destination
reported that an attempt was made to print
outside of the valid printable area. 0420-485 EXPL
ANATION An attempt was made to print outside of
the valid printable area. This area is the
intersection (common space) of the physical page
with the logical page or of the physical page
with an overlay. One or more characters, rules,
or images fall at least partially outside of the
valid printable area. When the print job
containing this error was sent, either the Type
of PRINT DATA ERRORS to report option on the
Infoprint SMIT Start a Infoprint Print Job panel
was set to All or Positioning, or the DATACK
keyword value entered with the enq -o command was
set to UNBLOCK or BLKCHAR. SYSTEM_ACTION First,
Infoprint prints a print-error marker at the
location on the page where the error was
detected. Then Infoprint stops processing the
page containing the error. Printing continues
with the next page in the print
job. USER_RESPONSE Check that the correct form
was loaded in the actual destination. If it was
and if the printed output would be acceptable
without the printer-error markers, send the print
job again and specify that positioning errors are
not to be reported. To suppress these types of
errors, either set the Type of PRINT DATA ERRORS
to report option on the Infoprint SMIT Start a
Infoprint Print Job panel to None or Invalid
character, or specify DATACKBLOCK or
DATACKBLKPOS at the command line with the enq -o
command. NOTE To correct the source of the
problem, check for other error messages, and see
their system actions and responses.