Being an IT guy, I think printing out those large reports is a cardinal sin. To get around this, we considered having the documents print out as a PDF. We did not want to spend the money on native AS/400 PDF writers nor did we want the hassle of installing new software on the AS/400.
Our solution was to print to a PDF print driver on the client computer that was printing the report. Using Client Access/400, we set up two PC5250 sessions. The first was a typical display session. The second was a printer session that we arbitrarily named CHRISPDF.
The printer session was set up such that the default printer for any jobs printed was the Adobe Acrobat PDF Writer. When you install Adobe Acrobat 4.0 and later, it installs print drivers for both the Distiller and the PDF Writer. The benefit is that Acrobat does not need to understand each individual application that writes to it. It simply sees the standard Windows print stream and converts it to a PDF--no matter which application is the source of the printout.
When I am ready to print on the AS/400, I direct the spool file to the CHRISPDF output queue. When it hits that queue, the Client Access/400 printer session downloads it from the AS/400 and sends it to the PDF Writer. When the PDF Writer receives it, a window pops up on my computer asking for the file name of the PDF file and where to save it. Once this information is entered, the PDF file is created and saved, and we're all done!
There are a few drawbacks of this solution, as you can probably tell. There is no way to automatically name a file based upon, for example, a title in the AS/400 print out. It is not an automated system, so user intervention is required. Batch printing any more than about five print jobs would be too time-consuming for this process. But it works, and for $200 to $300 and no software installed on the AS/400, you can't complain.
--Chris Green
Print PDFs? Why not print $$?
OK, you can't print money,
but you can get paid for your TechTips!
Send them to
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online