Jetform Documents not Printing

[Morgan Buschlen]

Hi All, I have configure a printer (using lpadmin on HPUX), the printer the printer prints fine from SAP except jetform documents.

Here it the print flow:
User printer in SAP, which is sent to a remote queue on the HPUXServer1, then sent to a remote queue to HPUXServer2, then a remote queue HPUXServer3, then a remote queue NT or W2K server then to the printer.

SAP -> HPUX1 -> HPUX2 -> HPUX3 -> WINDOWS -> Printer

The jetform (jfserver.jmd) is configured on HPUX1

Normal printing works, and when a jetform document is printed the printer does print a page of what looks like commands from the jetform document but not the actual document.

My thoughts are the Windows Print server needs a jetform service or jetform drivers installed, but I donâ t know that much about jeform.

Please let me know what might resolve this issue?

Thanks, Morg

[Bryan D. Quinn]

Hello Morg,

In SAP you should have a corresponding 'Jetform' que for the printer you are trying to print to that has a device type of 'ZJ ASCII:some generic ASCII printer'. That que should be pointing to the host where the jetform process is running and to the jetform que that you have setup on that host. In our system it is jf01.

For instance, we have a printer in SAP and on HPUX named ah05. If we want to set it up to print Jetform, we create an SAP que called ah65 and point it to the HPUX server running the jetform process. We also point it to jf01 on the host where jetform is running. The device type for ah65 is set to 'ZJ ASCII:some generic ASCII printer'. Then we would put the following line in jfserver.jmd:

!p ah65 * "lp -dah05 -or,p" * 50 *

Now, when you want to print Jetform to printer ah05, you actually choose ah65 in SAP and it sends the print to jf01 on the host running jetform. The jetform process monitors jf01, sees that something is there. Processes the file and prints it to ah05 on the host where jetform is runnning.

I hope this helps!

-Bryan

[Morgan Buschlen]

Thanks for the help, we do have other clients that are configured with the ASCII drivers, Adobe is currently working on the issues there was a larger jetform problem.