Frequently Asked Questions

RPM (108)

Is it possible to allow RPM to print to more than this number of printers?

RPM Select 4.5 and prior is limited to 24 printers; RPM Select 5.0 is limited to 10 devices. If you have RPM Select and wish to print to additional printers, please contact us about converting your license to RPM Elite. RPM Elite has 3 options for device limits: 99, 249, and Unlimited Devices

Here are the steps to increase the RPM Elite printer limit above 99.

  1. Open the Brooks License Manager in the RPM Program group or choose License from the software's Help menu.
  2. Open the Module Status tab and double-click RPM Printers. Follow the wizard selecting Internet activation option.
  3. Enter your invoice or sales receipt number, the auth code you were provided, and the number of printers you purchased and click Next.
  4. A success dialog will appear if your activation was successful.

Note: If you purchase an unlimited printer license for RPM Elite, enter 0 (zero) for quantity. Zero means "no limit".

RPM 6.0 (4)

Is it possible to allow RPM to print to more than this number of printers?

RPM Select 4.5 and prior is limited to 24 printers; RPM Select 5.0 is limited to 10 devices. If you have RPM Select and wish to print to additional printers, please contact us about converting your license to RPM Elite. RPM Elite has 3 options for device limits: 99, 249, and Unlimited Devices

Here are the steps to increase the RPM Elite printer limit above 99.

  1. Open the Brooks License Manager in the RPM Program group or choose License from the software's Help menu.
  2. Open the Module Status tab and double-click RPM Printers. Follow the wizard selecting Internet activation option.
  3. Enter your invoice or sales receipt number, the auth code you were provided, and the number of printers you purchased and click Next.
  4. A success dialog will appear if your activation was successful.

Note: If you purchase an unlimited printer license for RPM Elite, enter 0 (zero) for quantity. Zero means "no limit".

Will RPM Remote Print Manager® support network printers?

RPM version 6 and beyond have IP Print and LPR Print actions which support network printers directly.

When RPM receives more than one print job at a time, which one will print first? r-11221 Sue

The default for RPM it to process the data on a first in, first out (FIFO) basis. The first print job that RPM completely receives is the first job that will print out.

Let me describe a scenario that will provide a better picture. Let's say you send 2 jobs to RPM, one immediately after another. The first file you send is 60MB, and the second is a 3MB file. It is very possible that even though RPM started receiving the larger file first, it will probably print the small file first because that is the one RPM finishes receiving first.

In RPM Elite Version 6 new scheduling options are available with allow more control on processing order. These include Balanced, By Job ID, FIFO, and Priority Scheduling which allows user controlled priority settings.

Is it possible to allow RPM to print to more than this number of printers?

RPM Select 4.5 and prior is limited to 24 printers; RPM Select 5.0 is limited to 10 devices. If you have RPM Select and wish to print to additional printers, please contact us about converting your license to RPM Elite. RPM Elite has 3 options for device limits: 99, 249, and Unlimited Devices

Here are the steps to increase the RPM Elite printer limit above 99.

  1. Open the Brooks License Manager in the RPM Program group or choose License from the software's Help menu.
  2. Open the Module Status tab and double-click RPM Printers. Follow the wizard selecting Internet activation option.
  3. Enter your invoice or sales receipt number, the auth code you were provided, and the number of printers you purchased and click Next.
  4. A success dialog will appear if your activation was successful.

Note: If you purchase an unlimited printer license for RPM Elite, enter 0 (zero) for quantity. Zero means "no limit".

RPM Elite (1)

Is it possible to allow RPM to print to more than this number of printers?

RPM Select 4.5 and prior is limited to 24 printers; RPM Select 5.0 is limited to 10 devices. If you have RPM Select and wish to print to additional printers, please contact us about converting your license to RPM Elite. RPM Elite has 3 options for device limits: 99, 249, and Unlimited Devices

Here are the steps to increase the RPM Elite printer limit above 99.

  1. Open the Brooks License Manager in the RPM Program group or choose License from the software's Help menu.
  2. Open the Module Status tab and double-click RPM Printers. Follow the wizard selecting Internet activation option.
  3. Enter your invoice or sales receipt number, the auth code you were provided, and the number of printers you purchased and click Next.
  4. A success dialog will appear if your activation was successful.

Note: If you purchase an unlimited printer license for RPM Elite, enter 0 (zero) for quantity. Zero means "no limit".

RPM 4.0 (1)

My RPM Remote Print Manager® does not seem to be getting the data. The RPM log shows the following information:

Error: 0x2740 [10048] Address already in use.

This message is what the Windows operating system returned to RPM when RPM tried to use port 515. The message, in laymens terms, means that RPM is trying to open port 515, but another application is already using it. There are several applications which could use this port and it is difficult to find out which one to close or stop.

A couple of things you can check first: In the 'Services' applet under the control panel, look for TCP/IP Print Server. If it is showing 'Started', you need to first stop it, next press the 'Startup' button and disable this service. If that was running, try RPM again.

Another thing to check: Go into the RPM program, choose 'Protocols' from the 'Options' menu, and see if you have configured RPM to use port 515 twice. In there, you might see "Telnet:515" and "LPD:515". If both are in there using 515, choose the one you do not need, and press 'Delete'.

If you need both, you must use a different port for each. Try 9100 for telnet.

If these steps do not fix the problem, you have another program using this port. Check any terminal emulation software packages that may be starting an LPD automatically. You will need to look in the 'Startup' folders, and also the 'Services' applet in the control panel. Look specifically for something that has "LPD" in the name.

Category: 

RPM 2.1 (2)

After checking my logfile, I see

"Warning: Unrecognized control line."

What does this mean? And, is it going to cause problems in the future?

An unrecognized control line means that your LPR is sending over codes which are "enhancements" to the System V printing system. The System V printing facility supposedly expands the functionality of the BSD spooling facility, however, these enhancements have not been documented.

RPM handles these "enhancements" for the most part by ignoring the option. For example, if you have told your printer to use a form, it will not be used. RPM does not know how to do forms, so this option will be ignored. You should be able to eliminate these "unrecognized control lines" by editing the printcap file on your host system.

Note: RPM attempts to implement some of the "extensions" where we can identify their purpose, and actually do a credible job for the customer.

The answer to the second question, "will it cause problems," is "no". RPM may not do what you originally intended but usually there is a way to get the results you want. Please contact our tech support or tech sales for assistance.

An unrecognized control line means that your LPR is sending over codes which are "enhancements" to the System V printing system. The System V printing facility supposedly expands the functionality of the BSD spooling facility, however, these enhancements have not been documented.

RPM handles these "enhancements" for the most part by ignoring the option. For example, if you have told your printer to use a form, it will not be used. RPM does not know how to do forms, so this option will be ignored. You should be able to eliminate these "unrecognized control lines" by editing the printcap file on your host system.

Note: RPM attempts to implement some of the "extensions" where we can identify their purpose, and actually do a credible job for the customer.

The answer to the second question, "will it cause problems," is "no". RPM may not do what you originally intended but usually there is a way to get the results you want. Please contact our tech support or tech sales for assistance.

Category: 

After checking my logfile, I see

"Warning: Unrecognized control line."

What does this mean? And, is it going to cause problems in the future?

RPM Remote Print Manager® processes LPR/LPD information in accordance with the RFC1179. Some UNIX systems (System V) have tried to enhance the LPR/LPD protocol above the standard RFC specifications. You most likely are using one of these particular commands to try to get the correct output. RPM handles these problems by simply ignoring them. It is a good idea to not allow these printing "enhancements". Usually you can take these extras out of the printcap file.

This issue is currently being researched. We plan to have RPM correctly use these control lines, but we currently have no confirmation as to what they specifically do. We need more information from the developer of these System V enhancements. Contact our support team for further information.

Category: 

RPM 4.5 (11)

Is it possible to allow RPM to print to more than this number of printers?

RPM Select 4.5 and prior is limited to 24 printers; RPM Select 5.0 is limited to 10 devices. If you have RPM Select and wish to print to additional printers, please contact us about converting your license to RPM Elite. RPM Elite has 3 options for device limits: 99, 249, and Unlimited Devices

Here are the steps to increase the RPM Elite printer limit above 99.

  1. Open the Brooks License Manager in the RPM Program group or choose License from the software's Help menu.
  2. Open the Module Status tab and double-click RPM Printers. Follow the wizard selecting Internet activation option.
  3. Enter your invoice or sales receipt number, the auth code you were provided, and the number of printers you purchased and click Next.
  4. A success dialog will appear if your activation was successful.

Note: If you purchase an unlimited printer license for RPM Elite, enter 0 (zero) for quantity. Zero means "no limit".

Is it possible to allow RPM to print to more than this number of printers?

RPM Select 4.5 and prior is limited to 24 printers; RPM Select 5.0 is limited to 10 devices. If you have RPM Select and wish to print to additional printers, please contact us about converting your license to RPM Elite. RPM Elite has 3 options for device limits: 99, 249, and Unlimited Devices

Here are the steps to increase the RPM Elite printer limit above 99.

  1. Open the Brooks License Manager in the RPM Program group or choose License from the software's Help menu.
  2. Open the Module Status tab and double-click RPM Printers. Follow the wizard selecting Internet activation option.
  3. Enter your invoice or sales receipt number, the auth code you were provided, and the number of printers you purchased and click Next.
  4. A success dialog will appear if your activation was successful.

Note: If you purchase an unlimited printer license for RPM Elite, enter 0 (zero) for quantity. Zero means "no limit".

Occationally a warning occurs in my RPM log that states: "Unable to spool file 'C:\Path\To\Filename' 0x7b : The filename, directory name, or volume label syntax is incorrect" and the queue is suspended automatically.

What is causing this? And, can I change the behavior of suspending the queue on errors?

RPM 5.0 no longer suspends Print Queues when a Device is unavailable.  Instead, RPM checks on a regular interval for the Device to recover before attempting to process any jobs received.

Answer for Versions 4.5: The usual cause of this error is when RPM running on Windows NT with a "raw" type queue receives a job and tries printing it to a Windows Shared printer, and the PC hosting the printer is turned off, then RPM will hang for a period of time and wait for the printer. Eventually the connection to the printer "times out" and then the warning is logged in RPM.

This is because Windows NT spools everything to the remote spooler and if it is unavailable, then it cannot spool it at all.

You can configure RPM to hold the incoming job rather than suspending the queue. In this case, when the host PC for the shared printer comes back up, subsequent jobs coming in will be printed. The existing jobs that were held will need to be unheld manually.

To configure RPM for this behavior, here are the instructions:

  1. From the RPM "Queues" menu, choose "Edit Queues..."
  2. Press the "Print Data Options" button.
  3. In the "Other" tab of the "Print Data Options" dialog, uncheck "Suspend queue on printer error".
  4. Press "Apply" and then "OK" and "OK" again to save all changes.

RPM should now hold jobs rather than suspending queues.

You will also have the same problem with a "text" queue type, but in this case the message will state:

"Can't start document printing 0x7b : The filename, directory name, or volume label syntax is incorrect"

When I change my printer properties in RPM, they aren't used. I've tried to select a different tray, and also a different orientation, but neither seems to work properly. Am I doing something wrong?

If you are using a Text Print action in RPM Remote Print Manager®, these settings should all work just fine, as long as you have the correct driver loaded for the printer.

If you are using a Raw Print action, these settings make no difference. RPM's raw print actions send the data straight through to the printer without changing the file at all, including adding appropriate printer codes. This is the desired behavior and there is no way to make these settings work with this action type. If you need to print directly, you will need to configure your sending (LPR) system to format the data accordingly before RPM ever gets the data.

When I print through RPM to an HP LaserJet 5 printer, I get a Spool32.exe error message and I am forced to reboot the computer. After rebooting, I continue to receive the same error. Is there something that can be done?

The HP LaserJet 5 print driver causes this issue, but this can be fixed in RPM. First, verify that you have installed the HP LaserJet 5 print driver from the Windows CD-ROM and not from a CD or diskette that shipped with the printer.

If you are using the driver from HP, delete the printer from the Windows Printers folder. Then, add a new printer using the driver provided on the Windows CD-ROM.

Finally, you must append a form-feed or a line-feed to the end of the data.

  1. Choose "Edit Queues" from the "Queues" menu in RPM.
  2. Press the "Print Data Options" button.
  3. In the "Append" tab, choose "Append Bytes".
  4. Press the "Edit Bytes" button, then the FF or LF buttons.[1]
  5. Press OK on the "Edit Bytes" dialog, then "Apply" and "OK" on the "Print Data Options" dialog, and finally, the "OK" button on the "Edit Queues" dialog.
  6. Test the new configuration to verify that the problem is fixed.

Note: This problem may be evident in other print drivers that use the same PCL language as the HP 5.

[1] The FF button adds a form feed, the LF button adds a line feed. If you add a form feed, a blank page may print out after each document.

Category: 

CL codes are showing in my print job and I am using a "raw" type queue.

This could be caused by any of the following:

  • The printer does not support PCL 

If this is the case, you must either format the data differently on the sending side, or use a "text" type queue when that is not possible.

  • The printer does not support that PCL version 

Format the data using a PCL level that the printer does understand.

  • The Windows driver is using different PCL version than what is in the file 

Change the Windows print driver to one that supports the same PCL version that is in the file or use a "text" type queue in RPM if that is not possible.

Category: 

Print jobs are stuck in RPM Remote Print Manager® and I have looked at the data. The data seems OK, but they still won't print.

There are 2 possible answers to this question.

First, have you appended a LF to the end of the data. For whatever reason, some systems do not add a LF so the program thinks it's not quite done. To append an LF:

  1. Go to RPM\Queues\Edit Queues
  2. Select Print Data Options, then the append tab.
  3. Choose Append Bytes\Edit Bytes\LF
  4. Press OK until you are back to the queue status.

The other solution is the Windows printer Spool Settings or Scheduling (in the case of NT). To fix it, change the Spool Settings to "Spool print jobs so program finishes faster" and then "Start printing after last page has been spooled". Always turn off bi-directional printing because RPM does not support it at this time.

Category: 

How do I copy queue configuration from one computer to another running RPM?

RPM Remote Print Manager® (RPM) Elite and Select offer the functionality to export and import your configuration. This is done using the Export and Import functions from the File menu.

To export your configuration to a file, choose Export from the File menu. The standard Save As dialog will appear where you can choose a location and name your file. A .reg extension will be added to the file.

To import that file, choose Import from the File menu. This will invoke the standard Open dialog. Locate the file you exported previously and click Open.

RPM will reread the configuration and any new configuration will be used immediately, without the need to restart your computer.

RPM version 5.0 can import registry files exported by previous versions of RPM. It also imports and exports XML files.

Note: If you have any problems exporting your configuration through RPM, you can manually backup your queue configuration.

Category: 

We would like to be able to reprint our print jobs, just in case of any problems that may occur while printing. Does RPM have this feature built-in?

Quick answer: RPM 5.0 and newer support this, RPM 4.5 and prior do not. The following directions are for RPM 4.5 users.

No. RPM does not have this feature built in, but it can be done. RPM has three types of queues: text, raw and filter. To use this work-around, you must use the "filter" type queue. Follow these steps: First create the batch file:

  1. Create a batch file using notepad or another text editor program.
  2. The batch file needs to contain the following lines:
    • lpr -Phold -S127.0.0.1 %1
    • lpr -Pprint -S127.0.0.1 %1
  3. Save the file to a directory. In my example, I've named it "reprint.bat".

Now create the appropriate queues and configurations in RPM:

  1. Create a new queue in RPM to receive the initial job
  2. In the edit queues dialog, choose the "Run a local filter program on the file" option.
  3. In the queue setup, click the execute tab.
  4. In the "Program command line, with arguments, input "c:\path\reprint.bat %s". Be sure to put the correct path to the file.
  5. Create another new queue. I call it "print" in my example.
  6. Setup the queue to print the file correctly.
  7. Create another new queue. I call it "hold" in my example.
  8. In the Edit Queues dialog, check "Hold print jobs, operator controlled".

Now, when RPM receives the file in the filter queue, it will resend the file back through RPM in 2 different queues. One queue will hold the print job, the other will print it. If you need to reprint later on, double-click the job in the "hold" queue you wish to reprint. From here, you will be able to move the job to either the "print" queue or the filter queue which will start the process all over again. You can also specify the page range in the Operator Job Control dialog.

Category: 

I have changed my code page to print in a different language, but now when I print to RPM Remote Print Manager®, certain characters are replaced with a question mark (?). Why?

The printed "?" means that the character is not supported by the current code page. You need to change your code page to one that supports the character you're trying to print. The code page is in the Text Setup dialog.

If you've selected the correct code page, try a different script. To do this, follow the steps below.

  1. From the 'Queues' menu, choose 'Edit Queues:'.
  2. In the 'Edit Queues' dialog, make sure the 'Text' queue type is selected. Press the 'Queue Setup' button.
  3. In the 'Text Setup' dialog, you will see the Windows code page you are using. Verify the correct code page is selected. Press the 'Font' button. Note that it may be labeled 'Courier New 12' or similar.
  4. The 'Font' dialog is where you select the proper script. There could be multiple scripts depending on the language. You need to experiment to see which translates your document with the correct characters.

I can't print over 132 columns in my print jobs, although I set 150 characters-per-line.

RPM Remote Print Manager® (RPM) has two ways to set the horizontal size of the font. One is Use characters per inch and the other is Fit columns per line.

  1. From the RPM user interface, choose Edit Queues from the Queues menu.
  2. In the Edit Queues dialog, verify Select a queue lists the queue you wish to modify and that you have select the Print text, allows font selection, page setup queue type. Open the Text Setup dialog by clicking the Queue Setup button.
  3. Do one of the following:
    • Check Use characters per inch and fill in the chars/inch edit box. This page explains how to determine the number of characters per inch
    • Select Fit columns per line and enter the correct number of columns in the columns field.

Note: For best results, we suggest selecting a TrueType font such as Courier New. In the Font dialog, look for a TrueType icon beside the font name. The other type is a bitmapped, or system font, represented by the following icon: .

If your print job is a report or other document that lists data in columns, a fixed-width font should be used. It is important that the white-space (0x20) character is the same width as other printable characters. Courier New and Letter Gothic MT are the most common fixed-width fonts. Both Arial and Times New Roman are variable-width fonts.

Category: 

RPM 5.0 (2)

Is it possible to allow RPM to print to more than this number of printers?

RPM Select 4.5 and prior is limited to 24 printers; RPM Select 5.0 is limited to 10 devices. If you have RPM Select and wish to print to additional printers, please contact us about converting your license to RPM Elite. RPM Elite has 3 options for device limits: 99, 249, and Unlimited Devices

Here are the steps to increase the RPM Elite printer limit above 99.

  1. Open the Brooks License Manager in the RPM Program group or choose License from the software's Help menu.
  2. Open the Module Status tab and double-click RPM Printers. Follow the wizard selecting Internet activation option.
  3. Enter your invoice or sales receipt number, the auth code you were provided, and the number of printers you purchased and click Next.
  4. A success dialog will appear if your activation was successful.

Note: If you purchase an unlimited printer license for RPM Elite, enter 0 (zero) for quantity. Zero means "no limit".

Is it possible to allow RPM to print to more than this number of printers?

RPM Select 4.5 and prior is limited to 24 printers; RPM Select 5.0 is limited to 10 devices. If you have RPM Select and wish to print to additional printers, please contact us about converting your license to RPM Elite. RPM Elite has 3 options for device limits: 99, 249, and Unlimited Devices

Here are the steps to increase the RPM Elite printer limit above 99.

  1. Open the Brooks License Manager in the RPM Program group or choose License from the software's Help menu.
  2. Open the Module Status tab and double-click RPM Printers. Follow the wizard selecting Internet activation option.
  3. Enter your invoice or sales receipt number, the auth code you were provided, and the number of printers you purchased and click Next.
  4. A success dialog will appear if your activation was successful.

Note: If you purchase an unlimited printer license for RPM Elite, enter 0 (zero) for quantity. Zero means "no limit".

My RPM Remote Print Manager® data base has grown in size, or my RPM system sees to operate much slower, what should I do?

RPM Remote Print Manager (RPM) uses Firebird SQL for its database implementation. Even well-implemented databases require maintenance after heavy use. Database maintenance is one important practice which should improve system performance.

For RPM 5.1.1.99 database maintenance was a separate process. The in-depth discussion is in this FAQ.

Starting with RPM 6.0, database maintenance is available directly in the RPM user interface. From the File menu, choose Repair Database.

Database Maintenance

Let's review the "Database Maintenance" dialog. The tools shown here will locate issues within the database and correct them if possible.

Repair Options

First, we have the Repair Options. Of the four available choices: Validate, Full Validate, Mend and Sweep, we most often recommend all except Mend. Though this option is occassionally necessary to repair a database, it works by marking identified corruptions to be ignored making it the only option of those available with the potential of causing data loss.  As a result, it should be used as a last resort only if the other options fail to repair your corrupt database.

More detailed information about these functions is available on the Firebird website.

Rebuild Options

Next, we have the Rebuild Options. Both will create a new database, but exactly how they accomplish that task should play a role in determining which option you use.

There are two functions in this section. Of the two, we most often recommend Create a new database and migrate settings. This option renames the existing database file, creates a new blank database, and then migrates the settings from the old to the new.  This has the benefit of leaving the original database file intact.  Backup and restore database first backs up the database, but then restores it overwriting the original database file.  This option is not used during an upgrade because it may leave partially empty pages and non-conforming rows in the database. We include it as it may prove necessary or useful from time to time.

Our recommended database maintenance plan

We recommend you create a new database periodically. Exactly how often varies widely depending on the volume of traffic and activity in your environment.

We recommend running:

  1. "Validate", "Full Validate", and "Sweep"
  2. Create a new database and migrate settings.

It is often useful to first purge the RPM log which allows for the smallest size database while retaining your settings. If you choose to leave the log intact, the migration may take significantly longer to complete.

Category: 

Will RPM Remote Print Manager® work on an OS/2 system?

RPM is compatible with Windows running under OS/2, but not with OS/2 itself.

Will RPM Remote Print Manager® support network printers?

RPM version 6 and beyond have IP Print and LPR Print actions which support network printers directly.

Will RPM run in a cluster environment and is it a cluster-aware application?

RPM runs fine in a cluster environment, but it is not cluster aware. Because RPM is licensed per computer, a separate license is required for each redundant server.

Will RPM Remote Print Manager® receive jobs from an HP3000 running the MPE/iX operating system (OS)?

The MPE/iX OS does not natively support the LPR/LPD protocol. If you have a 3rd party LPR client for MPE/iX, we recommend you use it; however, we do not provide instructions for configuring 3rd-party clients.

Before getting started, note that TCP/IP printing on the HP3000 is supported on MPE release 5.5 or greater. The first step is to add the printer LDEV. You can add it using SYSGEN, which requires a system reboot, or it can be added dynamically with the IOCONFIG utility.

Creating the LDEV for RPM is exactly the same as any other JetDirect printer.

  1. Log on as Manager.SYS and run IOCONFIG.PUB.SYS.
  2. At the IOCONFIG prompt, type: AD LDEV=nnn PATH=NONE ID=HPTCPJD. Substitute nnn with a unique number.
  3. Exit IOCONFIG by typing EXIT.

Next, an entry in the NPCONFIG file must be created or added. The following configuration should be added to the "NPCONFIG.PUB.SYS" file. If this file does not exist, it must be created.

nnn (network_address = x.x.x.x
  tcp_port_number = 9100
  jam_recovery = false
  pjl_supported = false
  snmp_enabled = false
  setup_file = null.hpenv.sys
)

Replace nnn with the same number as the LDEV. The "network_address" should reflect the IP address of the PC where RPM is installed.

Note: null.hpenv.sys may not exist.  If not, create it first.  The setup_file should be an empty file.

Note: The "tcp_port_number" setting can be any number you choose. You must configure RPM to receive jobs on this port. Also, you must make sure that you are not using a reserved number such as 23 for telnet. Usually, if you use ports in the 9100 range, it will work.

To configure RPM to receive jobs on different ports:

  1. In RPM, choose "Port Settings" from the "Configure" menu.
  2. Choose "Telnet" from the "Select Port Type to Add" list and click Add Port.
  3. Enter 9100 in the Port list, or the number you configured in the "npconfig.pub.sys" file on the HP3000.
  4. From the "Queue" list, choose which RPM queue will receive jobs sent on this port number. We recommend accepting all other default values initially.  Press OK.
  5. The changes should take effect once you press OK on the "Port Settings" dialog.

RPM should now be configured properly for receiving jobs from the MPE/iX OS running on the HP3000 box.

RPM does not receive print jobs from the Windows Standard TCP/IP Port unless the LPR Byte Counting Enabled option is selected. What is "LPR byte counting" and why must it be selected?

The simple answer is this: if Microsoft implemented their LPR to send zero as the number of bytes, then RPM would be able to handle that correctly. As it is Microsoft sends an impossibly huge number, instead of the actual size of the file in bytes.

The LPR/LPD protocol allows for zero as the file size though sending the actual size is typical. There are a few LPR clients in the world which handle this correctly, and RPM works as you would expect in either case.

The longer answer follows.

"LPR byte counting" forces Windows to count the number of bytes in the file and send this value in the Receive data file subcommand. To understand why this does not work, you must first understand the steps in sending a print job using the LPR/LPD protocol.

  1. The LPR client sends the Receive a printer job command.
  2. RPM replies with an acknowledgement (ACK).
  3. When the LPR client receives the ACK, it can proceed. The client then sends the Receive control file subcommand.
  4. When the LPR client receives an ACK from RPM, the control file is sent. RPM will then respond with another ACK.
  5. The LPR client now sends the Receive data file subcommand. The size must either be set to the actual size of the data file, or set to 0. This is one area where Microsoft does not follow the protocol specifications.
  6. When the client receives the ACK, it will send the data file. Once the data file has completed, the connection is closed by both parties.

When LPR byte counting enabled is turned off, Microsoft sets the <file size> to a size much larger than the actual size. It is set neither to 0 nor the actual file size. When RPM receives a file much smaller than the specified file size, RPM believes that the entire file was not sent, deletes the "incomplete" file, and waits for the file to be sent again.

RFC1179 states that you may set the size of the data file to 0, however, it does not discuss how the LPD Server should handle this "unknown length file". RPM handles the "unknown length file" situation by receiving all data from the request to send the data file until the connection is closed by the LPR client.

RPM can also handle the opposite situation, in which the file is actually 0 bytes. You tell RPM to close the connection after a specified amount of time.

To do this, follow these instructions.

  1. Choose LPD Options from the Options menu.
  2. Select Enable zero length file transfers. 600 seconds is the default amount of time to wait, however, you may raise or lower this value to meet your needs.

When printing through RPM, the Euro currency symbol does not print, but is translated into a space character. How can this be resolved?

RPM handles the Euro symbol just fine, however, you must use a font that defines the euro symbol, such as Courier New. Here are some steps to help you determine where the problem lies.

First, determine if the Euro symbol is received by RPM. If it was sent, it will be in the data.

  1. Suspend the RPM queue, so it is displayed like "Queue xxx: Enabled, Suspended, Not holding" in the RPM Queue Status window.
  2. Send a print job to RPM just as if the file would be printed through RPM. Since the queue is suspended, the file will not print. Open the RPM\Spool folder. In it should be the data file, beginning with "dfA" followed by a sequence number, followed by the host system that sent the job to RPM. Example: dfA1tempest.
  3. View the contents of this file with a hex editor. A good one is UltraEdit32. Search for the hex character 0x80 or 80. This is the hex equivalent of the Euro symbol.

If the character is in the file, then your problem might simply be a font that does not support the symbol. If it is not in the file, then your efforts should be concentrated on the sending side host, as it is not sending the currency symbol to RPM.

Category: 

When RPM receives more than one print job at a time, which one will print first? r-11221 Sue

The default for RPM it to process the data on a first in, first out (FIFO) basis. The first print job that RPM completely receives is the first job that will print out.

Let me describe a scenario that will provide a better picture. Let's say you send 2 jobs to RPM, one immediately after another. The first file you send is 60MB, and the second is a 3MB file. It is very possible that even though RPM started receiving the larger file first, it will probably print the small file first because that is the one RPM finishes receiving first.

In RPM Elite Version 6 new scheduling options are available with allow more control on processing order. These include Balanced, By Job ID, FIFO, and Priority Scheduling which allows user controlled priority settings.

When I print, I get a stair step effect.

The reason for this is your Host (e.g. a UNIX system) uses LF as the end of line character and the printer is expecting CR/LF.

For RPM 6.0: add the "Unix to DOS" transform to the setup for this queue.

For RPM 5.0: add the "LF to CRLF" transform to the setup for this queue. Typically it would go at the beginning of the transform list, or just following a code page (data format translation) step.

For RPM 4.5 and prior: this is generally associated with a "RAW" type Queue. To Translate the LF to CR/LF do the following:

  1. Verify the Queue type is RAW
  2. Select the Queue Setup in the Edit Queues Window.
  3. Select Translate LF to CR/LF.

What types of printers does RPM Remote Print Manager® support?

RPM supports all printers that Microsoft Windows supports. If your printer has a Windows "print driver", then RPM can print to the printer.

Note: Some older dot matrix printers may be supported with the "Generic/Text only" driver.

Category: 

Your AS/400 setup instructions show to place "XAIX XAUTOQ" into the "Desination Options" parameter in the AS/400 OUTQ.  What do these options do, and what other options can I use?

You can find a description of the XAUTOQ parameter here.

The "Destination Options" parameter specifies the destination-dependent options. These options may be specific to a particular implementation of an LPD print server. When this parameter is not specified, the SNDTCPSPLF command sends default options that are common to most LPD print servers. The options specified by this parameter are inserted into the LPR/LPD control file generated by the SNDTCPSPLF command, one option per line, and sent to RPM.

The options specified by this parameter must have the following format:
"option1 option2 option3...optionN"
Each option is separated from the next by one or more spaces.

Options typically have a format of <control character><value>. An example is
"JJob_name"
J specifies the job name for the banner page and "Job_name" is what RPM would print on the banner page. SNDTCPSPLF examines the first character of each option to determine if it is a reserved control character. If any of the following control characters are specified, the option is ignored and a warning message is generated.

C T H U I W L 1 M 2 N 3 P 4 S k

For example "Class=ASCII" is not allowed because the "C" control character is reserved for use by the SNDTCPSPLF command. However, "-Class=ASCII" is permitted. The control character "X" is allowed, but the value of "AS/400" used with it is not permitted. For example, "XRPM" can be specified, but "XAS/400" cannot be.

The option "XAS/400" is reserved for use by the SNDTCPSPLF command as are the letters listed above. XAS/400 is used to indicate to another AS/400 that the request is coming from an AS/400.

The option "XAIX" controls how multiple copies are sent to the printer. This option is not the default, but should always be used when printing to RPM. XAIX specifies that the data and control files are to be sent multiple times, once for each copy. The default is to send the data and control files once, with multiple print commands in the control file.

c n d p f r g t l v

If one of these characters is specified as the first character in a destination option, the character is used on the "print file" command in the control file. Only the first occurrence of one of these characters in this position is used in the control file. Subsequent use of these characters in this position is ignored. If none of these options is specified, the default character "l" is used on the "print file" command, which prints the file "as is" without filtering out any control characters.

What is LPR/LPD?

LPR/LPD is the printing method most commonly used in TCP/IP networks. It is in use on university and business campuses where UNIX, AS/400 and mainframe systems have been in place for a while; the new generation of operating systems, for both mainframe and desktop, now support TCP/IP and LPD as well. It is a computer-to-computer printing method, rather than PC-to-PC.

The LPR/LPD protocol is broken into two parts, LPR and LPD. The standard LPD port is 515.

LPR is an acronym for Line Printer Request; this is the part that submits the print request. LPR is the client part of the protocol and is sometimes confused when used on a mainframe. Any system submitting requests via an "LPR client" is a client. INTELLIscribe is an LPR client.

LPD stands for Line Printer Daemon; this is the piece that receives and processes the request. A "daemon" is a server or agent. RPM is a LPR/LPD server. This component is often refered to as the "LPD service".

The phrase "LPD printing" refers to the setup or process required to print to an LPD server, like RPM. Often what people have in mind is system of organizing their print requirements into LPD print queues. For instance a queue named "printronix132" might be setup to print 132 column text to a printronix printer. It's easier to keep your work organized if you are systematic and print queue names certainly give you that opportunity.

The phrase "LPR printing" is very closely related, and often refers to using an LPR capable program on your system to send print jobs to an LPD server.

The LPD Protocol Specification is documented in RFC 1179, Line Printer Daemon Protocol, dated August 1990, edited by L. McLaughlin III.

RFC stands for Request for Comments. The RFCs document Internet protocols, practices and proposed standards. They are available via anonymous FTP at http://www.ietf.org/rfc/.

Try our LPD print server, RPM Remote Print Manager®, download the 21 day trial with pre-sales technical support. Contact us or download it today.

What happens to AS/400 spool files if they are sent to an RPM host where the RPM service has not yet been started or is not running?

The spool file will first go into a SND state on the AS/400, and will eventually be placed in a HLD state.
If the job is in a HLD state when RPM is restarted, the spool files will need to be manually released again. Here are instructions for releasing AS/400 spool files:

  1. From an AS/400 command prompt, issue the following command, WRKOUTQ outq name, and press Enter.
  2. Place a 6 next to each job you wish to print and press Enter.

If you continue having trouble printing, check the following related article: AS/400 print job goes into a HLD state.

What information is passed to RPM from the sending side?

RPM receives data via the LPR/LPD or Telnet printing protocols. When using Telnet printing, the only information RPM receives from the sending side is the data itself.

When using the LPR/LPD protocol, RPM receives a control and one or more data files. The control file contains detailed information on the print job such as the name of the print job and the host system sending the data. It also contains information how RPM should print the job such as what type of file it is, etc.

To see this information, do the following:

  1. First, enable the save control file option by performing the following steps:
    Windows Server 2003 or later:

    1. Open the Registry Editor (regedit.exe) to...
      HKEY_LOCAL_MACHINE\SOFTWARE\Brooks Internet Software\RPMPRO
    2. Edit SaveControlFile changing the value to 1. If it does not exist, add it as a new DWORD value.

    Windows 2000 or XP

    1. From the Options menu, choose Log.
    2. Check Save control file from host checkbox.
  2. Next, suspend the RPM Queue.
    1. From the Queues menu, choose Edit Queues.
    2. Check the Suspend printing on queue checkbox.
  3. Now, send a print job to RPM. With the queue in a suspended state, the job will be retained in RPM without printing.
  4. In the RPM Spool folder, two files will be created. One starts with "dfA", has a sequence number, and finally the hostname of the sending side. This is the data file. By default, the spool folder for RPM Elite is:
            C:\Program Files\Brooks Internet Software\RPMElite\Spool
    
  5. The other is named exactly identical except it starts with "cfA" and ends with a .txt extension. This is the control file. This file contains a LPR/LPD specific entry on each line. Each line begins with a letter, which corresponds to a control file line in the RFC1179 specifications. All information in this file was received from the sending side.

I need to allow only certain people to print to this RPM Remote Print Manager® queue. Does RPM include these security features?

RPM implements 2 types of security. You can restrict access based on hostname or IP address. If you want to restrict access based on hostname, you specify the hostname and whether or not you want them to have access, 'allow' or 'deny'. IP Address security works basically the same way only you enter the IP address instead of the hostname.

To get the host access, choose "Host Access:" from the "Options" menu in RPM.

This is quite an involved process, so we suggest that you obtain more documentation. You can press F1 for the help files or download the manual.

Category: 

Printer limit exceeded for queue xxxx, printer 'yyyy' (in the RPM Remote Print Manager® Log).

You will see this message when you have exceeded the number of allowed printers that your copy of RPM supports. The Trial version of RPM supports printing to any two printers connections in a single session. The Select version of RPM supports up to 10 printers connections in a single session. Unlimited printer connections may be purchased by contacting Brooks Internet Software.

I have configured a new OUTQ on my AS/400 to print data through RPM.  For some reason, print jobs go into a SND or HLD state and do not print. No new messages appear in the RPM log file.

To make a TCP/IP connection to RPM, the TELNET command may be used.  To verify a connection, perform the following telnet test.

  1. At the AS/400 command prompt, type TELNET and press F4
  2. In the Start TCP/IP TELNET (TELNET) screen, press F9 to view "all parameters."
  3. In the Remote System field, type *INTNETADR.  Enter the IP address of the RPM host in the Internet Address field.
  4. Locate the Port parameter and enter 515, then press Enter.

If RPM is configured to relax the 'port in range' requirement, this will input-inhibit the session if a connection is made. Close RPM (Windows 9x) or restart the RPM service (RPM Elite/Select) to release the AS/400 session. Then restart RPM and check the RPM log for new message.

If RPM is not configured this way, a new message should be displayed in the RPM log stating:
Client port xxxx out of range

Although this message is a warning, it verifies that a connection was made to RPM at port 515.

Can I use Ghostscript with RPM Remote Print Manager® (RPM)?

Ghostscript is a PostScript interpreter. PostScript is the most common printer language and is supported by most laser printers from nearly every printer manufacturer. However, there are a number of printers, laser and inkjet both, that do not support PostScript; this is where Ghostscript becomes useful.

The most common reason to use Ghostscript is to convert a PostScript file to PDF. Ghostscript can also output other formats including graphics formats (PNG, JPEG, TIFF, etc.) and printer formats (PCL5, PXL, epson). The second most common reason to use Ghostscript is to print PostScript files to a printer that does not support it.

How to download Ghostscript

You'll need to do a web search such as:

You should be able to find instructions to download and install the software.

You will also need to review the license information which comes with Ghostscript to verify that your use will be in compliance with the copyright holder's terms. This is not something Brooks can help you with.

However, the rest of our instructions will assume you can use GhostScript with permission as intended.

Convert Postscript to PDF

  1. In Queue Settings, create a new Filter action.
  2. Next to Command, click Browse and locate gswin32.exe. For instance, at this writing it was located in C:\Program Files\gs\gs8.64\bin\.
  3. If you are using a filter action, the Arguments should be:
    -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=%n.pdf %s

    If you are using a filter transform, the Arguments would be slightly different:
    -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=%o %s

  4. Set the Working directory to the folder in which you want the PDF file to be saved. To eliminate many issues, this folder should be local.

Note that the %s, %o, and %n are variables (placeholders).  RPM will substitute those values with the appropriate values.  A complete list of available variables is found in the RPM manual under both Filter transforms (page 13) and Filter actions (page17).

Print Postscript to a non-Postscript printer

  1. In Queue Settings, create a new Filter action.
  2. Next to Command, click Browse and locate gswin32.exe. It may be located in C:\Program Files\gs\gs8.64\bin\.
  3. The arguments should be:
    -dNOPAUSE -dBATCH -sDEVICE=mswinpr2 -sOutputFile="\\spool\<Printer Name>" "%s"

Substitute the name of the printer to which you want to print in place of <Printer Name>. This is the name found in the Printers folder.

Note: Certain situations may prevent gswin32 from completing successfully.  Each of the following methods have proven useful to resolve the problem at one time or another.  We suggest trying each method in the order it appears and testing each change until you find the first method that works.

  • The option -dBATCH tells gswin32 it is running as a batch and should exit when finished.  It has been added to these instructions.
  • Try adding the word 'quit' as the last argument to the command line.
  • Add an Append bytes transform to append the word quit to the end of the data file.  One customer reported this method corrupted PDF Documents when attempting to convert Color PostScript files.
  • Configure your Filter action or transform to terminate idle process after a few seconds.  This option will cause gswin32 to close, but it may not be finished with the conversion.

If you encounter any problems, enter the login credentials of the user you are logged on as and select Interact with Desktop. The next time a job is received, the Ghostscript window will be displayed where you can troubleshoot errors. Once resolved, remove the credentials.

There is no page between jobs.

This is a factor for raw printing. Text printing separates documents courtesy the Windows print drivers.

RPM offers several banner types as well as a PCL page seperator. It also supports insert and append byte strings as described below. These would be configured as transforms in the queue setup.

I have just installed RPM Remote Print Manager®. When I try to restart the computer or start the "RPM Remote Print Manager" service, I get "Error 1058: The service is disabled and cannot be started." When I go to the services utility and look at the RPM service, it shows "Automatic", not "Disabled".

This issue is caused when the service your are trying to start has been disabled for the current hardware profile. Consulting the Microsoft KB articles yield the following resolution:

  1. From Administrative Tools, open the Services utility.
  2. Right-click the RPM Remote Print Manager service and choose Properties.
  3. In the Log On tab, near the bottom is a list of hardware profiles and whether or not the service is enabled for that profile.
  4. Highlight your current hardware profile, then click Enable.
  5. Click OK

Note: If the Enable button is grayed out or otherwise unavailable, you may be logged in as a user that does not have the appropriate permissions to modify a service's settings. Log in as the Administrator and try again.

Otherwise, visit the Microsoft support page The Specified Service is Disabled and Cannot Be Started.

When I set up an RPM Remote Print Manager® queue to receive text, I can send a PostScript file but of course it prints with all its programming language text. Are you aware of any software that can allow my PC to become a PostScript or Encapsulated PostScript server to my Unix workstation?

The Ghostscript application is a postscript translation application. You can use a Filter type queue in RPM, call the Ghostscript application from the command line, pass the file to Ghostscript. Ghostscript will translate the file and send it to the printer. Ghostscript is shareware and can be downloaded from the Internet.

If you would like more information about Ghostscript, what it can do, or how to implement it using RPM, click on this FAQ. You can also get more information about it by going directly to the website.

We are using DHCP and DNS or a dialup connection and would like to print data from an AS/400 to a PC. How can I configure the AS/400 so I can print to a computer with a dynamic IP address?

One of our clients provided the following CL program. We are providing it for your consideration. As you can see, this program does the following:

  1. Prompts the user for the name of the OUTQ (printer) they want to use
  2. Automatically obtains their IP Address.
  3. Notifies the user that the OUTQ's IP address is being updated.
  4. Updates the OUTQ they provided with their IP address.
  5. Prompts them to update another OUTQ.

The CL program may be used and modified for your needs. It is possible to modify the program to eliminate all user interaction and automatically update the proper OUTQ on the AS/400. This program should be placed in the user's profile and run when the user logs in.

Download the CL program in a PDF document

This document is our best approximation of the correct tab and structure. We are currently unable to provide anything more accurate than this but no doubt an RPG programmer can make sense of it.

I want to receive a print job in RPM from an AS/400 without any printer control characters. Is this possible?

The AS/400 setup instructions show how to receive data into RPM from the AS/400 with Host Print Transform disabled. In this case, RPM will receive SCS data. You can then use the SCS to Text Markup and Remove text markup transforms in RPM to get plain text. Some users have mentioned they get an extra blank line on the first page of the resulting document.

To prevent the random blank line and instead use the AS/400 to perform the EBCDIC conversion leaving plain text, use all settings specified in the AS/400 setup instructions except the following.

  • Host Print Transform: *YES
  • Manufacturer type and model: *WSCST
  • Workstation customizing object: QWPDEFAULT
  • Library: QSYS

You will now get the data without specific printer codes embedded in the document.

I need RPM Remote Print Manager® to be able to retain each print job for a specified amount of time in order to reprint later if necessary. Does RPM currently have this ability?

Yes! In the Job panel in the GUI, you can set the Job Archive settings and specify how long jobs are retained for reprint. You can specify a time limit or number of jobs to retain.

Category: 

RPM Remote Print Manager® is taking a long time to print.

RPM receives and passes the file to your printer quickly. The time frame from the print job being sent to RPM from the host system (e.g. AS/400, Unix, etc.) until the print job is printed can be evaluated with the following steps to determine where the bottleneck is:

Problem 1: Evaluating time to send to RPM

First, suspend the RPM queue (at the menu select Queues, Resume/Suspend). Then send the file from the host (e.g. AS/400, Unix, etc.). Note the time from release at the host until the RPM queue status states "DONE". If it takes a long period of time for RPM to receive the job, the problem is probably associated with processing on the host system.

Resolution 1: Time to send Resolution 

RPM has been used to improve print job performance significantly by performing EBCDIC or SCS transforms rather than have the host do the transformation. To use RPM to transform, set the Print Data Options in RPM to do this transform and set the host to not transform. Now, re-send the print job from the host and note the reduction in the time for RPM to receive the print job.

If your host is not performing a translation, the bottleneck is with your network architecture. You should contact your network administrator for a resolution.

Problem 2: Evaluating time to print from RPM

If the above evaluation did not identify the problem, release the RPM queue (at the menu select Queues, Resume/Suspend) and note the time from release until the job completes printing. If it seems to take a long time for the job to begin printing, the problem could be the spool settings on your PC.

Resolution 2: Time to print from RPM resolution 

Set your spool settings (Start/Setting/Printer - right click on the printer you are sending to, and select Properties/Details/Spool Settings) to "Print directly to printer" and "disable bi-directional support." Now suspend the RPM queue, re-send the print job from the host, release the RPM queue and note the reduction in time to send the print job to the printer.

If this did not reduce the time for the print job to begin printing, here are other considerations:

  • The problem could be with the type of print driver you are using. If you are using a print driver from the manufacturer versus the Windows "box" driver (the driver that ships with Windows), try setting up the printer with the Windows box driver.
  • If RPM is performing formatting, you may change the queue type from TEXT to RAW and perform the "time to print from RPM evaluation" again. If this results in a significantly lower time for the print job to begin printing, you may choose to have your host system do the formatting and send the print job to a RAW type queue. Retry the steps above until you get the combination that works best for you.
  • If this does not improve your time to print, you should consider upgrading the PC that RPM is running on. Because the print job you are formatting will be processed faster on a more powerful PC.

RPM Remote Print Manager® shows fonts for one printer that it doesn't show for another. How do we copy fonts from one printer to another?

The Windows font dialog is displaying fonts. RPM tells it to use a particular printer, either the printer you selected in Edit Queues/Printer Setup, or the Windows default printer.

The fonts you see are the fonts supported by the print driver for that particular printer. We are not aware of a way to add fonts to a print driver.

RPM Remote Print Manager® (RPM) "Queue Status" shows Xfer next to the file name and the job never shows completely received (Done).

The above status indicates that RPM is receiving. Therefore, this is not an RPM problem. The problem is on the "Sending or LPR" side. Should you experience this issue, we suggest that you contact your network administrator (feel free to e-mail support). There are a variety of setup problems that can cause this symptom as shown below by the following *real* examples:

  1. Firewall issues - The control file could be sent just fine and a firewall could stop the data from sending. The resolution to this issue is to review the firewall log to see if the firewall is blocking the data transfer.
  2. Network issue - When many routers are on a network providing many paths to all of the networks. One of the routers could be performing nat translations of the address of the lpd server to allow for a second path to the machine if the primary was down. The problem develops when the nat translation is only being performed on the path to the server and not from the server. So the initial connection will be made and when the server sends back the ack packet, it will be sent from a different ip address which would cause the sender to fail to reply (expecting a reply from the address it was sent to). The resolution to this issue was to verify that the nat ip address to LPD server is same as ack ip from LPD server.
  3. Sending Host Setup issue - An incorrect print queue configuration on the Sending Host may also cause this to occur. To resolve this situation, verify the correct print queue setup.

RPM prints differently than another printer that is receiving print jobs directly from the AS/400.

Here are the most likely causes of this problem.

  1. If RPM is configured using a text type queue, any AS/400 formatting will be stripped and the file reformatted using the Windows print driver, as well as the settings configured in RPM. Change the queue type to Pass data directly to the printer (raw) and try again. If the printers are identical, this will resolve the issue.
  2. The AS/400 OUTQ directed to RPM may be configured differently than the OUTQ going directly to the printer. Verify they are identically configured. You can also use CRTDUPOBJ command to copy one OUTQ to another identical OUTQ, changing only the name.
  3. Users may have an override print file (OVRPRTF) associated with their user profile. Override print files can change the file printing attributes. Try logging in as a different user, or removing any override print file associated with the current user, to determine whether or not this is the problem.

My RPM Remote Print Manager® job has been placed in a "Wait" Status

Please check the Log and you will probably see "Printer limit exceeded for queue 'queue name', printer 'xxxxx.'

This message appears when you have exceeded the number of allowed printers that your copy of RPM supports. The Trial version of RPM supports printing to any two printers in a single session. The Select version of RPM supports up to 10 device connections in a single session and the Elite version supports 99 devices and can be increased to support unlimited printer connections by contacting Brooks Internet Software.

RPM Remote Print Manager® is receiving; however, nothing was printed. There are not any errors in the RPM Log and the log reads as follows:

    Information: Accepted client from x.x.x.x, port 148
    Information: Remote closed 148
    Information: Close on socket 148
    Information: Closing transaction for 148  

This issue is caused by a router or routers not being configured properly. Network Address Translation (NAT) is probably the cause. If you have more than one router, verify that either:

  1. All routers are configured to perform NAT translations, or
  2. No routers are configured for NAT translations

Also, a single router can be configured to perform the translation on outgoing data and not to perform the tranlation on incoming data. Verify that the router will do the translation on both incoming and outgoing data.

Suppose that the router was configured for NAT translation to the RPM host server, but data coming from the server did not get translated. The translation would occur before RPM received the data, then RPM would send an acknowledgement back. Since the translation is not performed on data coming from the RPM host server, the LPR client would never recieve this acknowledgment. Therefore, the LPR (in most cases) will close the connection and try again, over and over. Eventually it will give up.

Note: Verify that the NAT IP address to the RPM server is the same as the acknowledgment IP address from the RPM server.

Category: 

 I am printing from a SCO UNIX to RPM Remote Print Manager®. When I attempt to sent multiple files, a few print out, but it eventually hangs on about the 3rd or 4th print job.

This problem has been reported only with SCO UNIX, although it's possible if you're sending print jobs from systems with enhanced options. You will probably get a couple of messages in RPM that state:

  Error writing data to port 236 (0x2745):[10053] Software caused connection abort.
  Warning : Unrecognized control line -Onobanner.

In most cases, this problem will not occur if sending only one datafile over a connection. To fix the problem, you need to change your printer configuration on your SCO box to not use the option -o when sending to RPM.

The following message pops up when I try to start RPM Remote Print Manager®:

	RPM has detected that another program is using this network port: 515.
	Please check your configuration and try again.

RPM Version 2.2 and later checks to see if another program is using port 515. If you receive this message, exit the program that is using port 515 and restart RPM.

If you setup a queue with LPD protocol and another queue with Telnet protocol, do *NOT* use the port 515 on each. If you do, RPM version 2.2 will not launch and will report the port conflict. If this occurs, one of the queue setups must be deleted from the registry. Contact Brooks Internet Software, Inc. for assistance to proceed.

I already have a queue created in RPM, but when I sent a print job, RPM creates a new queue automatically. Why does this happen and can this behavior be changed?

The LPR/LPD protocol requires that the LPR client must specify the name of the queue when it sends a print job. By default, if this queue does not exist, RPM will create the queue automatically instead of denying the print request.

You can turn off the auto-create queue functionality. If this setting is turned off and RPM receives a request to print a job to a queue that does not exist, RPM rejects the print request instead.

To fix this issue, you can do either of the following.

  1. Modify the configuration on the sending side to use the queue name already created.
  2. Delete the queue you created and use the one which is auto-created by RPM.

RPM prints differently in RAW queue than directly from the AS/400.

One reason that we have seen is that the AS/400 OUTQ going to the RPM may be set up different than the OUTQ going directly to the printer. The AS/400 OUTQ parameters must be identical other than the IP address. All processing must be identical.

To test this, change the OUTQ going directly to the printer to use the IP address of the system running RPM and select a raw print action. Your print jobs should be the same now.

If they are still not the same, verify that you do not have an override print file command associated with your "user profile." This will change the file printing attributes.

Category: 

I have upgraded to OS400 V4R5. Now, reports are not printing out properly. Is the problem related to RPM or to the upgraded OS?

The upgrade to V4R5 introduced problems in areas of the AS/400 such as printing. Other problems not even related to printing can also occur, corrupted host table and printer emulation issues included.

To fix this problem, IBM advises applying the following PTFs:

  • 5769TC1, SF63410
  • 5769SS1, SF63267

These PTFs are available from IBM.

I am trying print through RPM from my host system to an HP Laserjet 1000 printer. Both the text and raw type queues show that RPM successfully printed to the printer, the printer light blinks as though it is attempting to print, but nothing is printed. How can I print from RPM to the HP Laserjet 1000 printer?

The HP Laserjet 1000 series printers are host-based printers and do not support the PCL printer language typically supported by other HP Laserjet printers.

Other users have reported that RPM can successfully print to this printer using the HP Laserjet 1000 DOS driver. To locate this driver:

  1. Open your browser to the Hewlett Packard website
  2. Search the "download drivers and software" section for "laserjet 1000."
  3. From the list of available downloads, choose the HP LaserJet 1000 Printing Software Solution. Download and run the installation program, following the directions.
  4. Once the printer is installed, open the Printers and Faxes folder, right-click the HP Laserjet 1000 DOS printer and choose Properties. Open the Advanced tab, click the Print Processor button and verify that the Print Processor is set to ZPPPCL and the Default Data Type is RAW.
  5. Click OK on the Print Processor dialog to accept the changes and dismiss the dialog.
  6. On the HP Laserjet 1000 DOS Properties dialog, open the General tab and click the Print Test Page button. Verify that a Windows test page prints successfully to the printer. If not, contact your system administrator for assistance. Press Ok to save the changes and exit.
  7. Open RPM, double-click the queue that is printing to the HP Laserjet 1000 printer, press the Printer Setup button, and select the new printer you installed. Repeat this step for each queue that is printing to the printer.

How do I set up the LPR/LPD service in OpenVMS to print through RPM?

OpenVMS stores printer configuration in the SYS$SPECIFIC[TCPIP$LPD]:TCPIP$PRINTCAP.DAT. This file is similar in syntax to a UNIX /etc/printcap file. You also need to add the hostname of the computer to the UCX$HOST.DAT file.

First, the LPD services must be enabled using the UCX utility. To do this, follow these steps.

  1. From the system account, start the configuration utility for UCX using the @ucx$config command.
  2. Select Client Components and verify whether or not LPD is enabled. If not, enable it now.
  3. Exit back to the main menu and select Server Components. Once again, if LPD is disabled, enable it now.
  4. Restart UCX by rebooting or restarting it from the main menu.

Next, the RPM host's DNS name must be entered in the UCX$HOST.DAT file. This tells OpenVMS that the RPM host is a valid printer on the network.

  1. Start the UCX utility using the UCX command.
  2. Add the DNS name of the RPM host in the UCX host database using the following command: set host "print1" /address=192.168.1.1 /alias="PRINT1"
    • print1: The DNS name of the RPM host
    • 192.168.1.1: The IP address of the RPM host
    • PRINT1: An alternate DNS name of the RPM host

    Note that VMS is not case sensitive, but UCX is. In UCX, PRINT1 and print1 are different.

Finally, create a printer.

  1. Start the LPR utility using the following command: run SYS$SYSTEM:UCX$LPRSETUP.EXE
  2. When LPRSETUP starts, select Add to add a print queue. The utility will prompt you for the following information.
    • Printer name to add: The name of the print queue in VMS.
    • Printer Type (remote / local): Choose remote for an RPM printer.
    • Printer Synonym: Synonyms are alternate names for the printer. When finished entering synonyms, press return on a blank line to continue.
    • Spool Directory: We suggest accepting the default directory.
    • Remote System Name: The hostname entered in the ucx database
    • Remote Printer Name: The name of the RPM queue.
    • Log File: The location where log files will be stored.
  3. You are next prompted to modify any symbol. Review to determine if any errors were made during LPRSETUP. If not, select q to quit.
  4. When prompted to start the print queue. Select yes.

If the lpd_startup.com file is included with your version of UCX, include it in the sys$manager:ucx$lpd_startup.com file. This allows the print queues to start automatically when restarting the OpenVMS system.

We have recently upgraded to SunOS 2.6 (or later) from a previous version. RPM Remote Print Manager® (RPM) is no longer receiving print jobs from the Solaris box. How can we configure the new operating system version to print through RPM?

There have been significant modifications to the printing system between Solaris 2.5 and 2.6. You may need to remove all old printers and add a new printer to allow RPM to receive print jobs from Solaris 2.6. RPM supports all relevant BSD print protocol options, such as those described in the RFC 1179 specifications.

If you have the graphical desktop CDE, these instructions may be more helpful.

If the above is not helpful, or you want a simpler way to create printers in Solaris, the following command can be used to create a printer that will print to remote print servers such as RPM.

# lpadmin -p name -s host!remote-queue
# enable name
# accept name

Be sure to replace the italicized words above with the correct information in your situation. Below is information if you have any questions as to what each of the italicized words represent.

  • name: The name of the print queue as it will be known in Solaris
  • host: The DNS hostname or IP address of the RPM host
  • remote-queue: The name of the queue in RPM. This name can be identical to name above.
Category: 

How can I create a printer on the Solaris server to print to my queue in RPM?

The steps below will help you configure a printer on Solaris version 2.51 to print through RPM.

  1. At the console, open Admintool.
  2. Open the Printers utility.
  3. From the Edit menu, point to Add and choose Access to Printer.
  4. The following options should be configured.
  • Client: Enter the IP address or hostname of the Solaris server.
  • Printer name: Enter the RPM queue name here.
  • Print Server: Enter the RPM host computer's IP address (or hostname if using DHCP).

When pressing the "Printer Setup" button to select a printer on a newly created queue, an hourglass cursor appears for a second then goes away. The Print Setup dialog never appears.

The reason that new queues cannot access the Print Setup dialog is that the operating system is blocking it due to a connection problem with the default printer.

Try changing the default printer to be a local printer. This is done from the Windows Printers folder.

  1. Open Start->Settings->Printers.
  2. Right-click on a printer and choose "Set as default".
  3. Now try accessing the Print Setup dialog from RPM.

If the Print Setup dialog still does not appear, repeat the above process until it does. This problem is caused by the operating system and not by RPM. Typically, your default printer should be a "local" printer, meaning one connected to LPTx or COMx ports, or other ports such as the LPR port, JetDirect port, etc. A shared printer, such as \\Server\Printer, can cause problems with other applications as well as RPM.

I send PostScript files and they print as PostScript code.

Use a Raw Print action instead of a Text Print action in order to pass the PostScript to printer.

If your printer does not support PostScript please see our instructions for using Ghostscript.

I am using SCO TermVision and I want to use RPM because of the features offered. When I try starting RPM, an error message stating 'RPM has detected another program is using port 515...'. How can I eliminate this message?

SCO TermVision contains a fairly simple LPD package. It will pass raw data to the printer. Since you wish to use RPM for more complicated tasks or features, this LPD should be disabled. To disable it:

  1. Open the Windows "Control Panel". Double-click "Vision Services".
  2. Click the "Printing" tab. Choose "None", meaning TermVision will not have any printers configured.

Now, you should be able to start RPM without the error message. This message is there to warn users or administrators that there is a problem, rather than determining the problem later on.

I am using Chameleon NetManage and I want to use RPM because of the extended features offered. When I try starting RPM, an error message stating 'RPM has detected another program is using port 515...'. How can I eliminate this message?

Chameleon HostLink contains a very simple LPD package. It will pass raw data to the printer. Since you wish to use RPM for more complicated tasks or features, this LPD should be disabled. To disable it:

  1. Open the Windows "Control Panel". Double-click "Network".
  2. Locate the NetManage LPD service. Highlight it, then press "Properties".
  3. Select the setting to disable this service. RPM will be replacing it, along with adding features which are not available in the NetManage LPD.

Now, you should be able to start RPM without the error message. This message is there to warn users or administrators that there is a problem, rather than determining the problem later on. Note: In old versions of Chameleon, the LPD did not run as a service. To disable the LPD in old versions, simply close the application. You should also remove it from the "Startup" group if you will be using RPM.

When printing from the AS/400 to RPM and specifying a range of pages to print, it seems this instruction is ignored as the entire spool file is printed. Can RPM be configured to honor the page range setting?

RPM does not impose this limitation, it is caused by the AS/400. With a Remote OUTQ, even if you specify a page range, the entire spool file is sent to RPM and printed. The LPR/LPD protocol does not allow for page range printing, so RPM will print everything that is received.

IBM provides a way for page ranges to be set in remote OUTQs. Click here for more information. RPM also supports page ranges. To control the starting and ending page, the job must be held or the queue suspended. When a print job arrives in RPM, double-click the job, and enter the starting and ending pages. If the specified ending page is less than the starting page, the job will start at the starting page and end when there is no more data to print. Release the job or unsuspend the queue to start printing the job.

On which versions of Windows does RPM run?

RPM 6.1 supports these versions of Windows: Vista, 7, Server 2008 (including R2), Windows 8 and 8.1, Server 2012 (including R2), and Windows 10.

RPM does not run on Windows 95, 98, Millennium Edition, or Windows NT and 2000 as these platforms have not been support by Microsoft for a number of years.

Category: 

How can I manage the jobs with different forms? Using RPM Remote Print Manager®, the AS/400 doesn't send any warning about the change of form.

Even working with different vendors, we have not yet established whether or not the AS/400 LPR can send form information. We are exploring ways to get this information from the '400 directly.

Until then, you might investigate using "styles" with RPM Remote Print Manager®. This would make it easier to manage a number of different layouts, even though it would not be automatic.

I try to send a print job to RPM, and nothing is recorded in the log. I do not exactly know if the problem is in my network or just that RPM is not receiving.

To perform a local telnet test, you need to first have network logging turned on in RPM. Follow these steps:

  1. In RPM, choose "Log" from the "Options" menu.
  2. If they are not already checked, put a check in the first 6 boxes: 'Enable network logging', 'High detail', 'Enable print logging', 'High detail', 'Enable queue logging', and 'High detail'.
  3. Press OK

Now that you have the logging set to high detail, you need to perform a local telnet test. Use the following steps.

  1. Choose Run from the Windows Start menu.
  2. If your computer operating system is Windows 95, 98, or Millennium Edition, type "COMMAND" in the Run dialog. Otherwise, type "CMD". Press OK.
  3. In the command prompt, type telnet 127.0.0.1 515 and press Enter. If you know the IP address of the RPM host, substitute it instead of 127.0.0.1.
  4. Depending on your RPM settings and your operating system, different results can occur. For instance, on Windows 2000 or XP:
    • If a telnet window pops up, or the command prompt goes to a plain black screen with only a blinking cursor, but nothing else happens, press Enter again.
    • A dialog should pop up stating: 'Connection to host lost' and in the Telnet window, another message appears: 'Socket xxxx received unknown command 0xd with arguments."
  5. On Windows 9x or NT, with older versions of RPM, this may happen:
    • You may see a message in the DOS prompt that says 'Client port xxxx out of range'.
  6. In either case, check the RPM log for the same message.
    • In RPM, press the "Log" tab at the bottom of the RPM window.
    • Look for the same message you received above: 'Client port xxxx out of range'.

If the RPM log has the same error, that means RPM is working fine. If not, that means something else got the connection and is not allowing RPM to do its job. You need to look for another LPD that might be starting before RPM. Some terminal emulators such as "Exceed" install an LPD server software that cannot on the same computer at the same time with RPM.

We have RPM running on a dedicated print server machine. We have more than 50 queues. If this machine were to have any problems, these queues would be lost. Is there any way to backup this information just in case our computer crashes?

Go to the "File" menu in the GUI, select "Export" and enter a file name. The RPM GUI will back up the current configuration of queues, actions, transforms, jobs and settings into an XML file. You can later "Import" this from the "File" menu.

This is a good thing to do for backup purposes and for copying the information to a different computer as well.

Category: 

I can ping the PC, but can't connect.

First, make sure your remote computer can see RPM. Attempt to connect to RPM using the telnet program. Most Unix telnet programs can take an optional port argument. The following command will attempt to connect to the host rpm.somewhere.com on TCP port 515, which is the port RPM listens on for incoming print jobs.

  telnet rpm.somewhere.com 515

If you can connect to RPM, you will probably see the following text (or equivalent).

  Trying rpm.somewhere.com...
  Connected to rpm.somewhere.com
  Escape character is '^]'.

Pressing the Enter key at this point should close the connection and display the following message.

  Socket xxx received unknown command 0xd with arguments  Connection closed by foreign host.

The first part of the above message is RPM's response to an unknown command. Check the RPM log for the same message as it should be logged as a warning. If the message shows up in the RPM log, you have made a successful connection to RPM.

If you get "Connection refused" or "Connection timed out", check and relax port 515 for any firewalls (software or hardware based) that may be blocking the connection.

If you see a message such as "Unknown host", check your server's DNS configuration (on some machines this is in /ect/hosts) and make sure there is an entry for your PCs hostname, or that your server has the appropriate DNS servers configured.

Open the LPD Options dialog by choosing LPD Options from the Options menu in RPM. If you have turned off "relax the 'port in range' requirement", after initiating the above telnet command, you will see the following message. You will also see it in the RPM log as well.

   Client port xxxx is out of range

Even though these are warnings in the RPM, they merely show that a connection has been made to RPM. You can safely ignore the warnings.

We need RPM Remote Print Manager® to translate EBCDIC to ASCII.

RPM has a native EBCDIC translator, which can handle not only US EBCDIC but European language extensions from a variety of countries.

Follow these steps to use the EBCDIC translator:

For RPM 5.0 and newer:

The SCS to Text Markup transform natively supports this translation. You can also change codepages on the various Text to Text Markup transforms.

For RPM 4.5:

  1. Select "Edit Queues" from the "Queues" menu in RPM.
  2. Choose which queue you want to translate from the drop-down queue list.
  3. Press the "Print Data Options" button.
  4. In the "Transform" tab, check "EBCDIC". Also, you can choose (from the drop-down list) to have RPM use a different language for translation. By default, RPM will pick the language closest to your computer's locale setting.

I have installed RPM Remote Print Manager®, but now I do not know how to setup my AS/400 to print to it. Do you have steps for setting up a remote OUTQ in the AS/400?

  1. From the AS/400 command line, issue the command CRTOUTQ.
  2. The first parameter is Output queue. This is the name of the local queue on your AS/400.
  3. The Library parameter should be QUSRSYS.
  4. The Remote system is the host name of your PC, AS/400 host table entry. We recommend that you use the fully qualified name in both the host table and in this file and screen or you can use *INTNETADR and enter the IP address in the IP Address key later on.
  5. The Remote printer queue is the name of a queue defined on your PC in RPM.
  6. Press F24, F9 now. This should display all parameters.

 

Use the following table to enter values as shown.

Writers to autostart: 1

Connection type: *IP

Destination type: *OTHER

Transform SCS to ASCII: *YES

Go to the Manufacturer type and model parameter. Press F4 to see a list of printers that IBM supports. Pick HP4 for the best RPM features; or pick the printer you will be printing to, if you are using features that RPM does not currently support. Use the following table to enter the values as shown.

Destination options: XAIX XAUTOQ

Operator controlled: *YES

Data queue: *NONE

Library:

Authority to check: *DTAAUT

Authority: *USE

If you want to suppress banner pages, set Print separator page to *NO and Job Separators to 0.

Category: 

How do I setup a queue in AIX version 4.x to print to RPM Remote Print Manager®?

Setting up queues in version 4.x is slightly different than 3.x. Follow these steps:

  1. smit
  2. Print spooling
  3. Add a print queue with the following options:

    Attachment type: REMOTE

    Type of remote printing STANDARD PROCESSING

    Name of queue <PICK_A_NAME>

    Hostname of remote server <REMOTE_SYSTEM_NAME>

    Name of queue on remote server <RPM_QUEUE_NAME>

    Type of print spooler on remote server BSD

  4. Enter to accept, exit from smit and test.

How do I set up my AIX version 3.x queue to print to RPM Remote Print Manager® (RPM)?

  • On the Unix Host, add a line to the /etc/hosts file at the end that lists the IP address of the PC where RPM is installed, then a tab, then a hostname to be referenced, such as:
    192.168.1.100      rprinter
  • Now ensure the LPD subsystem is activated:
    1. smit
    2. Spooler
    3. Manage Remote Printer Subsystem
    4. Server Services
    5. lpd Remote Printer Subsystem
    6. Start Using the lpd Subsystem
    7. Start BOTH now and at System Restart
  • Now configure the Remote Printer Queue:
    1. smit
    2. Spooler
    3. Manage Remote Printer Subsystem
    4. Client Services
    5. Remote Printer Queues
    6. Add a Remote Queue
  • Fill in the fields as follows:
    *NAME of queue to add <AIX printer name>
    ACTIVATE the queue? yes
    Will this become the DEFAULT queue? no
    Queuing DISCIPLINE first come first serve
    ACCOUNTING FILE pathname [  ]
    DESTINATION HOST for remote jobs <RPM hostname> or <IP Address>
    *Pathname of the SHORT FORM FILTER
    for queue status output
    [/usr/lpd/bsdshort]
    *Pathname of the LONG FORM FILTER
    for queue status output
    [/usr/lpd/bsdlong]
    *Name of QUEUE on remote printer <RPM_Queue>
    *NAME of device to add <eg. HP5>
    *BACKEND PROGRAM pathname [/usr/lpd/rembak]

Note: Replace bold items with information specific to your situation. If you are unclear on any of these items, contact your system administrator.

Note: The instructions to setup AIX version 4.x are slightly different. Click here for the 4.x setup instructions.

How do I setup SCO UNIX to print to RPM Remote Print Manager®?

Make sure you have a line in your /etc/hosts file that has the IP address of the PC you have installed RPM on, and a hostname for that PC.

At the shell prompt type "telnet <hostname> 515". <hostname> should be the name of the PC running RPM.

If you get the following response (or similar), your setup is correct:

	Trying <xxx.xxx.xxx.xxx>:
	Connected to <hostname>.
	Escape character is '^]'.
	Client port 1107 out of range
	Connection closed by foreign host.

Now run scoadmin and choose "Printers".

Choose "Printer Manager".

Choose Printer/Add Remote/UNIX

Now, put your host name and printer name in. (Make sure to deselect the box that says: "Use extended remote printer")

If you forget this, you can later remove the ":ex" from the /etc/printcap file using vi or another text editor.

For a more detailed set of instructions, click here.

How do I set up RPM Remote Print Manager® (RPM) with Lapres?

Please contact us if you are using Lapres with RPM. We have not encountered this software in a very long time.

  1. In Queue Settings, create a new Filter action.
  2. Next to Command, click Browse and locate laprun.exe.
  3. Arguments:
    /P /O /R /D=%s /P=<lapres_destination> J=<lapres_environment> /X

The following process is performed:

  1. RPM receives print job.
  2. RPM runs the command above.
  3. Lapres outputs to the local or network printer.
  4. Lapres shuts down with the /X option after file has been printed.

I am trying to print from a Dec VAX. The problem is that the OCX software does not support LPR printing! However, it will use Telnet. Can I set up RPM Remote Print Manager this way?

Set the DEC VAX to send to port 9100 and the printer queue name to the RPM queue name.

You also need to configure RPM to receive on Telnet 9100. Follow these steps:

  1. In the RPM UI, select Options/Protocols:
  2. In the Protocol type, use "Telnet".
  3. In the TCP/IP port, type "9100", and click Add.
  4. Choose the queue that will receive jobs from the Dec VAX.
  5. Click OK, Then OK again on the Server Protocols dialog.
  6. Choose Yes to restart server protocols.

How do I setup Linux to print to RPM Remote Print Manager® (RPM)?

Make sure you have a line in your /etc/hosts file that has the IP address of the PC you have installed RPM on, and a hostname for that PC.

At the shell prompt type "telnet <hostname> 515". <hostname> should be the name of the PC running RPM.

If you get the following response (or similar), RPM is listening correctly:

	Trying <xxx.xxx.xxx.xxx>:
	Connected to <hostname>.
	Escape character is '^]'.
	Client port 1107 out of range
	Connection closed by foreign host.

Now run printtool and press "Add".

Choose "Remote Unix (lpd) Queue".

By default, the spool directory, file size limit, and name are automatically entered. You may change this information, or add another name by typing a pipe (|) character and another name.

Now, add your remote host destination ip address or hostname (RPM PC) and the remote queue name which will be the queue name in RPM.

For a more detailed set of instructions, click here.

Question: I want RPM Remote Print Manager® (RPM) to copy the data file in a directory I specify, without printing it or running a program. How do I accomplish this?

Answer: you can accomplish this easily using the Archive action in RPM. The Archive action is extremely flexible and is used in a number of situations. In this FAQ we'll focus on simply writing to disk. At the end we'll reference other articles which reference expanded features.

How to save the file without the printer

Saving your print jobs without actually printing them is surprisingly common. There are lots of reasons for doing this, including migrating your library of company data to a new server or document storage system.

Step 1: determine which print queue you are using

There are two ways you could do this. The first is to look at the setup on your sending system. The second is probably the easiest; start the RPM service and run the RPM user interface from the Windows programs menu. Send print jobs and see what queue is created in RPM containing your print jobs.

Step 2: add an archive action to this queue

First, double click on the queue name in the RPM user interface.

You don't need to worry about adding a transform for this example.

Let's add an Archive action. Look for the button that says "Add Action". To the left of that is a drop list of actions. Select "Archive" then click the "Add Action" button.

This is the Action dialog:

Action setup dialog
Archive Setup

In this example, you won't be archiving to a shared folder so you won't need Credentials. If you need to use shared folders please see this page.

Click the Browse button, use the Windows dialog to select the folder you want to archive to, and click OK.

The default file name is probably OK. You can certainly try it, then change the file name if you prefer.

You can experiment with the File Creation options although "Create New File" is probably a good one to start with.

Category: 

How do I print to RPM Remote Print Manager® (RPM) from an IBM/VSE mainframe running a VTAM-based application?

You can use the General Print Server Daemon to spool jobs to RPM. Here is how to do that:

Use the DEFINE GPSD command to initiate an instance of a GPS Daemon (server). You must define one Daemon for each VTAM logical unit you wish to emulate.

Define GPSD

name:

  • A 1- to 16-character alphanumeric name used to identify this definition. The first character must be alphabetic.

pubname:

  • The public name (enclosed in single quotes) of a library and sublibrary to be used by the GPS Daemon. This library will be used as a staging dataset for LPR data and to contain the optional logging file. It must be available to the TCP/IP filesystem e.g. through using a DEFINE FILE statement.

dest:

  • The IP address (numeric or symbolic) of the remote host where the Line Printer Daemon resides. The port number is determined by the protocol.

pname:

  • The name of a print queue. This name will be sent to the Line Printer Daemon on the remote host to identify the target printer. You must know this name and specify it here. Otherwise, the LPD will reject our attempts to send data. Note that the printer name can be supplied and/or overwritten in a SCRIPT. pname is case sensitive.

lu:

  • The VTAM LUname with which GPS will be known to VTAM applications. This value must be defined to VTAM as an application ID. If omitted, the default is GPSDTERM.

LOG:

  • If 'YES’, the GPS Daemon will create a log file. This file will have a name equal to the value specified for TERMNAME and an extension of 'LOG’. This file is overwritten each time the Daemon is started. The file is a simple text file and can be viewed or printed using standard VSE facilities. The default value is 'NO’.

This information was originally found on the IBM website, however, it is no longer available.

I need to modify the line spacing. Can I do this with RPM Remote Print Manager®?

In RPM 5.0 and newer you can change the line height in the Text Markup transforms.

Prior versions of RPM have several ways to modify the line spacing, none of which are actual line-spacing features, rather page formatting features. Go to the Text Setup dialog. You can now specify a font size and lines per inch or fit lines per page. The last option will fit the given number of lines between the top and bottom margins on a page, scaling the font as needed.

We also provide instructions on setting the "lines-per-inch" in RPM.

Category: 

How do I configure my SGI IRIX lpr to print through RPM Remote Print Manager®?

To print through RPM from SGI IRIX, the following instructions will help you configure the remote printer definition.

The daemon /usr/etc/lpd should already be running by default if the proper software has been installed. This software is installed from the eoe2.sw.bsdlpr subsystem on 3.3.1 or later versions of IRIX.

  1. Edit the /etc/printcap file and add your printer information. If you need help here, see the man pages for printcap. If you want to make a printer the default printer for the lpr command, add lp to the list of printer name aliases. A typical printer entry looks like:

    hp4|rpmqueue|lp:\
    :sd=/usr/spool/print/hp4:\
    :rm=rpm.brooksnet.com:\
    :rp=rpmqueuename:\
    :lf=/var/adm/lpd-errs:

  2. Create the general spool directory and set the correct ownership and permissions. This step should only be done if this is the first printer created. You cannot perform this step more than a single time.

    cd /usr/spool
    mkdir print
    chown lp print
    chgrp lp print
    chmod 755 print

  3. Create the spool directory for the new printer and set the correct ownership and permissions. The name of the directory is specified in the /etc/printcap entry on the sd= line.

    cd /usr/spool/print
    mkdir hp4
    chown lp hp4
    chgrp lp hp4
    chmod 755 hp4

  4. At this point, the system should be restarted or you may restart the /usr/etc/lpd to allow the changes to take effect.

Note: To print, enter the following command at the shell prompt:

lpr -Php4 path/to/file

I have upgraded to a new computer. Now, when I try to print from the AS/400, the job never makes it to my RPM queue. Is there something I need to do when upgrading PCs or changing the IP addressing scheme?

There are two common causes to this problem.

  1. The new computer typically has a different IP address than the previous RPM host computer. To resolve this, you must configure the AS/400 OUTQ with the IP address of your new RPM computer.
    1. From an AS/400 command prompt, issue this command, substituting your OUTQ name where appropriate: ENDWTR outq name *IMMED.
    2. Wait 15 seconds, then issue this command, again substituting your OUTQ name where appropriate: CHGOUTQ outq name. Press F4 to prompt, as opposed to the Enter key. If you press the Enter key, start again from the beginning.
    3. In the Change Output Queue screen, press F9. Verify the Remote system parameter is set to *INTNETADR (or to the DNS hostname of your new RPM host).
    4. Locate the Internet Address parameter. Enter the IP address of the new computer. Do not use single quotes or an asterisk (*).
    5. Now, press Enter. If the Writers to autostart parameter is greater than zero, the writer for this OUTQ will start automatically and printing will begin. If not, you must enter the following command to start the writer: STRRMTWTR outq_name. Press Enter.
  2. The other most common problem is that the computer has a firewall installed. Printing from the AS/400 to RPM requires the firewall to allow incoming data on port 515. This page has instructions on configuring the Windows XP Service Pack 2 firewall.

How can RPM be used in a fail-safe way with the licensing model?

The Brooks License Manager generates a serial number during installation based on the MAC address of the first network device. The MAC address is obtained using the SNMP protocol. This method ensures that the serial number is unique because MAC addresses are also unique.

Each time the RPM Remote Print Manager® (RPM) service is started, the serial number is verified against the MAC address of the current network device. If there is any discrepancy, the license expires (is set to a trial with 0 days remaining). In order for the new serial number to function, it must be reactivated.

If a hardware failure causes the license to expire, an uninstall and reinstall must be performed to allow the trial license to be used in production within the printer limit of the trial. Contact us to reset your license so it can be activated again.

Solution: We advise exporting the current RPM configuration to a safe place and keeping a copy of the latest install as backup procedure. If there is a failure, a new system or the repaired system, can be placed into production quickly. The license will need to be activated to have the full printer limit supported.

When a fail-safe backup plan is required, we recommend an extra license be purchased. If your server is down, and you cannot contact us, then you can license your backup RPM until we can be reached. Once we are reached, we can deactivate your backup license and it is available next time you need it. This is a low-cost way of ASSURING your RPM production license will always be up and running.

Category: 

How do I disable banner pages?

RFC 1179 says that the client passes information to the server (e.g. RPM Remote Print Manager®) that specifies the name that is to appear on the banner page. You are *supposed* to treat this as a command to create a banner page.

Note that the Unix client does this unless you tell it not to, with the "-h" switch.

When RPM is printing text, it will make a banner page using the normal convention as explained above. You can tell RPM not to print a banner page by going to Queue Setup and setting "Never print the banner page".

When RPM is printing raw or pass-through, RPM will print a banner page only when the control file designates.

Sometimes when we're asked about not printing the banner page, they are referring to a banner page created by an application on the remote system. The way around that is this:

  1. Hold the queue.
  2. When the job is received, double click on the job. This opens the "Operator Job Control" dialog. The field "Start print on page" contains the value "1". Change this to "2".
  3. The setting "Hold (set ON to print later)" will be selected. Click this setting to release the job.

For RPM 5.0 and newer you can use the "Remove Until" transform to remove up to the first line of text, beyond the banner page, or the "Remove Lines" transform to remove a specific number of lines from the front of your file.

How do I set an RPM Remote Print Manager® queue to print to a specific Windows Printer?

For RPM 5.0 and later:

  1. Open the Queue Setup panel
  2. Select the queue in the queue list
  3. Select the action with the printer you want to change (Text print and Raw print actions work the same way in this regard)
  4. Click the Modify button to the right of the actions list
  5. Select a new printer. For Text print actions you can select printer settings in this dialog.
  6. Click Save when done.

For RPM 4.5 and prior:

  1. From the "Queues" menu, choose "Edit Queues".
  2. From the "Queue" drop-down list, choose the queue you want to select a printer for.
  3. Now, if the queue type is Text print, press the "Printer Setup" button.
  4. In the "Printer Setup" dialog, choose the printer you want this queue to print to from the "Printers" drop-down list.

Note: From this same dialog, you may also identify the page orientation and paper size by pressing the "Properties" button.

How can I release a job in "wait" status?

Jobs can be in a wait status if the queue is suspended. If this is the case, simply unsuspend the queue. If the queue immediately goes back into a wait status, check the Log window for any new warning messages for the cause. Typically, there is a problem with the printer.

Another reason for jobs being in a wait status is if another job is printing in another queue. RPM is a single threaded application, so one job must finish before others can be printed. If you are using a filter queue and jobs are not completing properly, open the Execute tab in the Queue Setup and deselect run one filter program at a time.

Note: RPM 5.0 and newer do not have the "single threaded" bottleneck but jobs may still error, so checking the log is still the good option.

Category: 

How do I grant the Logon as a batch job privilege to my user account?

Setting up 'Logon as Batch Job'

Answer: On Windows, this privilege is granted through the Local or Domain Security Policy. To do this using the Local Security Policy, follow these steps.

  1. In the Control Panel, open Administrative Tools, then Local Security Policy.
  2. Beneath Security Settings, open Local Policies and highlight User Rights Assignment.
  3. Locate Log on as a batch job. Open the properties and add any users that need this right.
  4. When finished, save your changes and close the Local Security Settings window.

Your changes should take effect immediately. To make changes to the Domain Security Policy, on a domain controller, use the Domain Security Policy utility in the Control Panel.

Why RPM Remote Print Manager needs 'Logon as Batch Job'

RPM Remote Print Manager uses Logon as Batch Job

Our RPM product has the ability to process print jobs as a specific Windows user. As you well know, sometimes the permissions make this necessary; for instance, if you want to

  • write to a shared folder
  • print a shared printer
  • run a program interactively.

This is the reason we researched this topic in the first place, and we are pleased to make this page available to you. Obviously, helping our users is what makes us all successful, and we're happy to share the information with the community.

If you need a great print server or virtual printer, please download the free trial today! And best of luck with your "logon as batch" issues from here on out.

In RPM Remote Print Manager®, I get an "Error: Failed subcommand 4" when printing from my AS/400. What can I do to fix it?

This error is caused by an incorrect setting in the OUTQ on the AS/400. To fix it, follow these steps:

  1. First you must end the writer. From a command prompt on the AS/400, issue the command (without quotes) 'ENDWTR writer_name *IMMED'.
  2. Now from the command prompt, issue the command 'CHGOUTQ queue_name'. Press the F4 key
  3. Now you must get to the "All Parameters". Press F24 (shift-F12) then F9.
  4. Press "Page Down" until you get to the parameter "Destination Type".
  5. Change this to *OTHER.
  6. Finally, save the changes and start the writer again.

I have reinstalled RPM on a different computer as the one originally had RPM crashed. When I attempt activation, it states "all available licenses are already unlocked."

For customers who have current Software Upgrade & Maintenance (SUM), an After Hours Licensing solution is available in emergency or disaster recovery situations when the regular trial version is not sufficient to meet your needs. This solution is available for RPM Elite and Select only and provides a five day trial version allowing the same number of printers as if the activation has been completed. The software can then be activated at your convenience when our normal business hours resume.

Click here to access the 5-day trial version. Please note that this service is no longer available. The possibility for abuse from certain users ended up being a large enough problem that we decided to discontinue this option.

Category: 

Does RPM support printing to a USB connected printer?

USB printing is supported as RPM does not make any distinction between USB, parallel, and serial connected printers.

Note: Some manufacturers create print drivers that do not support remote or network printing. These are typically low-end, low-cost printers and the print driver will work only when in constant communication with the printer. If this is the case, try changing the Spool settings and other Advanced features to disable bi-directional support and advanced printing capabilities.

Does RPM Remote Print Manager® support Intelligent Printer Data Stream (IPDS) files from the AS/400 or IBM mainframe systems?

RPM cannot support IPDS. Our newest product, ExcelliPrint®, is currently available and supports IPDS extensively. To learn more about Excelliprint, please visit our IPDS site.

Is there any way for RPM to print a document correctly with mixed font styles such as bold, italics, or both?

The answer depends on data in the incoming print job.

  1. If you are printing SCS from an iSeries computer, RPM can handle most font styles and changes automatically. The Remote OUTQ may need to be configured differently than normal. Setting the Host Print Transform parameter to *NO will cause RPM to receive raw SCS data. In the Print Data Options for your RPM queue, turn on Convert SCS to ASCII. RPM supports and interprets most, but not all, SCS commands.
  2. RPM understands two other ways to print bold: using backspace (0x08) or a carriage return (0x0C) without a line feed. We suggest opening the data file in a hexadecimal editor looking for these two characters. RPM also supports strikethrough and underlined text using this method as well.
  3. At this time, RPM does not interpret bold printing with any other format. RPM removes the PCL formatting instructions and, since bold printing is performed by a PCL sequence, no font change instructions remain. Future versions of RPM may support bold printing when the incoming data is PCL.

Does RPM Remote Print Manager® support printing AFPDS files generated from an AS/400 or System 390?

The AS/400 will convert AFPDS data streams via Host Print Transform for AS/400 printer emulations. An RPM raw type queue will pass the converted data directly to the printer bypassing the Windows print driver.

ExcelliPrint does handle AFPDS files, please visit ExcelliPrint's IPDS Printing home page. ExcelliPrint gives you the power to print IPDS to any Windows-based printer.

System 390 supports the AFPDS conversion via the Infoprint system. RPM can then pass the converted data directly to the Windows printer through an RPM raw type queue.

How do I determine the characters-per-inch and lines-per-inch settings to use in a "Text" type queue?

Characters-per-inch may be calculated using the following formula(s):

  • CPI = Number of Characters in a line to be printed / Printable Width, or
  • CPI = Characters / Paper Width - (left margin + right margin)

Lines-per-inch may be calculated using the following formula(s):

  • LPI = Number of Lines to be printed on a page / Printable Width, or
  • LPI = Lines per page / Paper height - (top margin + bottom margin)

Examples:

  1. I am printing on letter size paper, landscape. I want 60 lines on each page, and there are 132 characters on each line. I've set the margins to 1/2 inch on all: top, bottom, left, and right.
    • CPI = 132 / (11 - (0.5 + 0.5)) = 13.20
    • LPI = 60 / (8.5 - (0.5 + 0.5)) = 8
  2. Printing again on letter size paper, portrait this time. I want 80 lines on each page, and there are 92 characters on each line. I've set the margins to .75 inches on top and bottom margins, 0.5 inches on the left and right margins.
    • CPI = 92 / (8.5 - (0.5 + 0.5)) = 12.2
    • LPI = 80 / (11 - (0.75 + 0.75)) = 7.6

Error: Unable to find data queue in library (AS/400 V3R6).

If you have made all the entries identified in the "AS/400 Setup Instructions" (CRTOUTQ) screen, and get the error message above, then leave the "Library" field blank.

I have a host system running that does not support the LPR/LPD protocol, however, it does support the Telnet protocol for printing. Can I configure RPM to receive jobs using the Telnet protocol?

RPM Remote Print Manager® provides the ability to receive print jobs via a direct socket connection on any port. This is also known as stream printing or reverse telnet. Ports used for this purpose typically start at 9100 similar to the Jetdirect protocol. Follow the steps below to configure RPM for direct socket printing.

In the RPM GUI:

  1. Go to the View menu and select General Settings.
  2. Click the Ports icon.
  3. Click Add Port.
  4. Select "Telnet" from the list, and enter a port number.
  5. Select a queue to send telnet jobs to. The defaults for the other settings are usually good enough.
  6. Click the Save button.

My RPM Remote Print Manager® will not receive jobs from the Tandem operating system on the mainframe. Can I configure RPM to receive jobs from a Tandem OS?

We have researched the Tandem operating system and found that the old OS versions do not support the LPR/LPD protocol natively.

There are 3rd-party LPR spoolers available, and RPM can receive jobs fine using their "raw" printing. Configure the Tandem systems as follows:

Create a file in $SYSTEM.SYSTEM called FASTCNFG with the following information.

  !****** CONFIGURE TCP/IP DIRECT FOR RPM Software ******
  Device $LPRT1
  CONTYPE	=TCP/IP
  ADDRESS	=192.168.1.50 (RPM host IP Address)
  PROTOCOL	=NONE
  PORT	=9100 (Telnet port setup in RPM)

Now, configure RPM to receive jobs using the Telnet protocol on port 9100. Note that this port number can be any TCP/IP port number you choose. Some port numbers are reserved for other protocol such as 21 for FTP and 23 for regular Telnet.

  1. In the RPM UI, select "Options/Protocols:".
  2. In the Protocol type drop-down list, select "Telnet".
  3. In the TCP/IP port, type "9100", and click Add. Make sure that you do not add telnet using port 515 or this will cause a problem with RPM.
  4. Choose the queue that will receive jobs from the Tandem.
  5. Click OK, then OK again on the Server Protocols dialog.
  6. Choose Yes to restart server protocols.

We have learned that new OS versions support the LPR/LPD protocol natively. To do this:

  1. Create a device name in Tandem using "SPOOLCOM".
  2. In your "FASTCNFG" file, create an entry similar to the above entry, using "LPD1179" in "PROTOCOL" in place of "NONE".
  3. Do not enter "PORT", or configure it to port 515, since this is the proper LPR/LPD port number.

I am trying to print jobs to a low-cost inkjet printer. Using a Raw printer action, the RPM Remote Print Manager® (RPM) log indicates the job has been printed, but nothing is printed to the physical printer. What can I do to resolve this problem?

To save on cost, most inkjet printers do not have any internal processing power, but instead rely on Windows and the driver for all processing. These printers cannot print even a plain text document unless the application uses the Windows print driver.

The purpose of the Raw print action is to bypass the print driver altogether. This requires the printer be supported by the sending system. Low-cost inkjet printers rarely, if ever, support any operating system other than Windows.

Luckily, RPM's text printing functionality can resolve this problem. If the incoming data is plain text, use a Text markup transform and a Text print action to print these jobs to any printer with a supported Windows driver.

If the incoming data is PostScript, see the section titled Print Postscript to a non-Postscript printer in this FAQ.

I have files with ASA carriage control, also known as FORTRAN control characters, that I need to print. Can RPM convert ASA carriage control properly?

RPM Remote Print Manager® supports ASA characters where appropriate using a transform specific to this data format, which also known as Fortran formatted data.

The following list shows the ASA carriage control characters and how they are interpreted by RPM. For each character the action follows:

0 Insert a blank line before the current line
1 Draw the current line at the top of the next page
+ Return to the beginning of the current line; used to overwrite
- Insert two blank lines before the current line

All other characters residing on the first column of each line are ignored and the remainder of the line is printed single-spaced.

Category: 

Is it possible to allow RPM to print to more than this number of printers?

RPM Select 4.5 and prior is limited to 24 printers; RPM Select 5.0 is limited to 10 devices. If you have RPM Select and wish to print to additional printers, please contact us about converting your license to RPM Elite. RPM Elite has 3 options for device limits: 99, 249, and Unlimited Devices

Here are the steps to increase the RPM Elite printer limit above 99.

  1. Open the Brooks License Manager in the RPM Program group or choose License from the software's Help menu.
  2. Open the Module Status tab and double-click RPM Printers. Follow the wizard selecting Internet activation option.
  3. Enter your invoice or sales receipt number, the auth code you were provided, and the number of printers you purchased and click Next.
  4. A success dialog will appear if your activation was successful.

Note: If you purchase an unlimited printer license for RPM Elite, enter 0 (zero) for quantity. Zero means "no limit".

When sending a job from the AS/400, that job immediately goes into a ready (*RDY) status. The job is never sent to RPM and no messages are logged in RPM related to this print job. In the AS/400, the *RDY status never changes to *SND.

This is a result of the AS/400 remote writer not running. To start the remote writer, issue the command STRRMTWTR outq_name. The remote writer can also be configured to start automatically after making any changes to the OUTQ configuration using the Change Output Queue (CHGOUTQ) command. To do so, follow these instructions.

  1. From an AS/400 command prompt, issue this command, substituting your OUTQ name where appropriate: ENDWTR outq name *IMMED.
  2. Wait 15 seconds, then issue this command, again substituting your OUTQ name where appropriate: CHGOUTQ outq name. Press F4 to prompt. If you press Enter, start again from step 1.
  3. Press F9 to view all parameters, then locate the Writers to autostart parameter. Set this value to 1.
  4. Press Enter to accept the changes. In the future, any changes to the OUTQ will also restart the remote writer; there is no need to issue the STRRMTWTR command.

When sending a print job from the AS/400, it goes into a holding (*HLD) status, and does not print. There are no messages logged to the RPM log whent his happens.

This is caused when a connection cannot be made from the AS/400 to the RPM host. To resolve the issue, verify the settings in the OUTQ match the recommended settings on our AS/400 setup instructions. To begin modifying the OUTQ, follow these instructions.

  1. From an AS/400 command prompt, issue this command, substituting your OUTQ name where appropriate: ENDWTR outq name *IMMED.
  2. Wait 15 seconds, then issue this command, again substituting your OUTQ name where appropriate: CHGOUTQ outq name. Press F4 to prompt, rather than the Enter key. If you press the Enter key, start again from the beginning.
  3. Press F9 to view all parameters, then compare your settings with our AS/400 setup instructions.

Verify the RPM host's IP address or DNS hostname are configured properly, and that there are no firewalls between the AS/400 and RPM that may be blocking the connection, including the Windows XP Service Pack 2 firewall. If the Windows Firewall is the cause, we show you how to add a firewall exception.

When attempting to print from the AS/400, the spool file immediately goes into a sending (*SND) status but does not print.
No messages are logged in the RPM Remote Print Manager® (RPM) log when this happens.

There are a number of settings on the remote AS/400 OUTQ that can result in this issue. To resolve, verify the OUTQ settings match the recommended settings on our AS/400 setup instructions. To begin modifying the OUTQ, follow these instructions.

  1. From an AS/400 command prompt, issue this command, substituting your OUTQ name where appropriate: ENDWTR outq_name *IMMED. Press Enter.
  2. Wait 15 seconds, then issue this command, again substituting your OUTQ name where appropriate: CHGOUTQ outq_name. Press F4 to prompt. If you press the Enter key, start again from step 1.
  3. Press F9 to view all parameters, then compare your settings with our AS/400 setup instructions.

Also, verify the RPM host's IP address or DNS hostname are configured properly, and that there are no firewalls between the AS/400 and RPM that can be blocking the connection, including the Windows Firewall. If the Windows Firewall is the cause, click here for assistance.

I am printing to RPM from an AS/400. When I specify a page range on the spool file, the entire document prints anyway. Is there any way for RPM to honor the page range setting on the AS/400?

The problem is not with RPM, but with the AS/400. Specifically, remote OUTQs do not limit the pages to the specified page range, only standard OUTQs and devices.

Basically, the AS/400 knows what you want but is not telling RPM (or any other 3rd party LPD product).

IBM provides a program with source that will allow a user to specify a page range printed or sent via RMTOUTQs that are configured with a connection type of *IP or using the LPR or SNDTCPSPLF commands. The program is called TSPRWPR and details can be found on the IBM website. Or, perform a web search for the program name "TSPRWPR" which should locate the IBM document.

After the OS/400 version has been upgraded, all spool files go to a SND state, but will not print. What did the upgrade do to stop printing?

After an OS/400 operating system upgrade, check the AS/400 host table and TCP/IP configuration. Restore or replace any missing entries in the host table.

Also, verify that the writer is started for each OUTQ. To do so, from the AS/400 command prompt, issue the following command: WRKOUTQ outq name. If the status of each Output Queue is RLS/WTR, then a Writer is running and this is not the cause of the issue.

There are a number of settings in the AS/400 OUTQ configuration that can result in this symptom. To resolve the issue, verify the settings in the OUTQ match the recommended settings on our AS/400 setup instructions. To begin modifying the OUTQ, follow these instructions.

  1. From an AS/400 command prompt, issue this command, substituting your OUTQ name where appropriate: ENDWTR outq name *IMMED.
  2. Wait 15 seconds, then issue this command, again substituting your OUTQ name where appropriate: CHGOUTQ outq name. Press F4 to prompt, rather than the Enter key. If you press the Enter key, start again from the beginning.
  3. Press F9 to view all parameters, then compare your settings with our AS/400 setup instructions.

We have installed RPM on a Windows Server 2003 operating system. When printing to a locally attached printer, everything is fine. When the printer is shared from another Windows PC, a message is logged that reads, in part, access is denied.

Microsoft recommends that vendors support login credentials as the preferred way to get access to a shared resource, from a Windows service. This is why RPM Remote Print Manager® offers optional credentials for any action that uses a printer, folder or file path.

To assign user credentials to a device, in the action settings dialog (for whatever action you are using) locate the Credentials field in the dialog and click the Update button, then enter your domain, user and password where indicated.

We have an extensive discussion on printing to shared printers on this page.

I have a software firewall such as Zone Alarm or the Windows Firewall installed on my computer. What ports need to be opened in order to use ExcelliPrint?

At the minimum, you must relax your firewall to allow allow IPDS traffic.  The default IPDS port is 5001 (though this is configurable on the AS/400).

To determine which port numbers your AS/400 is using, use the CHGDEVPRT. Issue the command for each printer pointed to ExcelliPrint. For the OS/390, look at the PRINTDEV macro defined in the PSF Startup Job. The PORTNO parameter is the port number setting. Again, do this for each printer pointed to the computer where ExcelliPrint is installed.

If you wish to administer ExcelliPrint from another computer, you also need to relax the ports configured for HTTP and, if used, HTTPS. To see which ports are used for administration, use the ExcelliPrint control panel utility. Open Control Panel and double-click the ExcelliPrint icon. If you are using Category View on Windows XP, the ExcelliPrint utility is found in Other Control Panel Options under the See Also collapsible window on the left.

IPDS print jobs are not being separated properly when printing through ExcelliPrint.

IPDS is a page-based protocol. ExcelliPrint never receives any information about when a print job starts or ends as it is not supplied by the host system.

The Print Services Facility (PSF) provides a method to separate the print job into separate files. On IBM mainframes, the JES parameter is CKPTPAGE. On the iSeries, the PSFCFG option is Acknowledgment frequency (ACKFRQ).

ExcelliPrint will create a new job or file if the number of pages in the spool file exceeds this setting. PSF supports a maximum of 32767 in this parameter.

For example, if you set this parameter to 100 and the print job is only 25 pages, the job will be split at page 25 successfully. If the number of pages in the next print job is 120, ExcelliPrint will separate the first 100 pages into one print job and the last 20 pages in a new print job.

The host system also uses this setting when handling problems.

  • If you have a 60,000 page print job, and you set this parameter to 32767, ExcelliPrint will create only two separate print jobs. If an error occurs on page 60,000, the host system must resend all pages from 32,768 through 60,000 again.
  • If 10 was configured in the CKPTPAGE parameter, ExcelliPrint would separate the job into 6,000 smaller print jobs. If an error occured on page 60,000, the host system would need to resend only pages 59,991 through 60,000, significantly reducing the amount of recovery time and host system processor utilization.

Setting this parameter to a low value will cause slower printing.

We suggest testing this to find the value that works best in your environment.

I need to send IPDS print jobs to a specific source drawer (paper input tray) on my printer. How do I know on which tray the job will be printed?

You need to know the following three things.

  1. Which tray you want to print to
  2. What PCL command your printer uses for that tray
  3. The source drawer specified in the IPDS file on your host system

ExcelliPrint takes the source drawer specified by the host system and converts it to a PCL escape sequence.

  • If source = 1 use PCL command <Esc>&l1H
  • source = 2 PCL command = <Esc>&l4H
  • source = 3 PCL command = <Esc>&l5H
  • source = 4 PCL command = <Esc>&l8H
  • source = 5 PCL command = <Esc>&l9H
  • source = 6 PCL command = <Esc>&l10H
  • source = Envelope (65) PCL command = <Esc>&l6H
  • source = Manual (33) PCL command = <Esc>&l2H
  • source = Manual Envelope (96) PCL command = <Esc>&l3H

Note: To print to a different tray, you must change the IPDS print job on the host system. Changing ExcelliPrint settings will not change the tray from which the job is printed.

We are using ExcelliPrint to print IPDS to our printer. Each time a job is printed, there are a number of font substitution messages found in the message log (DSPMSGLOG). Can these messages be suppressed?

You can suppress messages regarding successful font substitutions only. Messages indicating that a font substitution attempt failed are always issued.

To suppress messages regarding successful font substitution, set Font substitution messages (FNTSUBMSG) to *NO on the PSF configuration object (PSFCFG) used by the device to which you are printing.

For these detailed instructions, substitute the name of your device description and PSF configuration object where appropriate.

  1. Open Client Access or your preferred emulator.
  2. At a command line, enter: ENDWTR [DEVD] *IMMED and press Enter. This will end the writer quickly.
  3. After the writer is ended, you must vary-off the device. To do this, enter VRYCFG CFGOBJ([DEVD]) CFGTYPE(*DEV) STATUS(*OFF) and press Enter.
  4. Repeat the above two steps for each device using the PSF configuration object.
  5. Now you need to change the PSF configuration object. This is done by issuing the following command: CHGPSFCFG PSFCFG([PSFCFG]) FNTSUBMSG(*NO).
  6. Finally, vary-on the device and start the writer again using the following commands:
    • VRYCFG CFGOBJ([DEVD]) CFGTYPE(*DEV) STATUS(*ON)
    • STRPRTWTR [DEVD]

Alternatively, you can change it using the AFP Manager component of iSeries Navigator by de-selecting Notify after successful font substitution on the PSF Configuration Resources page.

How do I create a device on my host system (mainframe or AS/400) that prints to ExcelliPrint using IPDS?

Detailed information about printing to ExcelliPrint from mainframes and AS/400 systems can be found in the ExcelliPrint manual.

Information in the manual covers both ExcelliPrint Premium and ExcelliPrint Standard.

I need tech support with ExcelliPrint. What information should I have available when contacting technical support?

You should be ready to provide your serial number. The serial number can be found in the Brooks License Manager or the Home link on the ExcelliPrint administration.

Also, you may be asked to provide a capture file. Follow these instructions to obtain a capture file.

  1. Open the ExcelliPrint Administration and login as an admin account.
  2. Click Printers, then click the ExcelliPrint printer name.
  3. In the Input tab, for each port, there is a Capture column. If the capture is off, click Turn On. If it is currently on, skip this step.
  4. Now, print a job from your host system.
  5. When the job has finished printing (or failed), look in the ExcelliPrint capture folder. If installed to the default location, the capture folder is C:\Program Files\Brooks Internet Software\ExcelliPrint\capture.
  6. Any files with a .ebc extension are capture files and can be emailed to technical support.
Category: 

The printer to which I would like to print does not appear as a selection at the printer list.

The printers listed are those the run-as user has installed. If "ExcelliPrint User" is the run-as user, only the local printers are shown in the list.

Windows printers which are shared from another computer are considered network printers. All other printers are local printers. Once installed, network printers are user specific. For example, if you log in as Administrator and install a network printer, it will not be visible by any other user even when logged on to the same computer. On the other hand, local printers are system wide and, once installed, can be printed to by any interactive user, including the "ExcelliPrint User."

To get different printers listed, change the run-as user. Any run-as user needs the "logon as a batch job" user right. Instructions for adding this user rights assignment are found here.

Writer abnormally ended (abended).

Your AS/400 is not configured correctly.

Please refer to the AS/400 Setup instructions. The most common settings to check are:

  • REMOTE SYS name and/or the RPM host system's IP address is correct in the remote outq definition or HOST TABLE
  • Verify that the AUTCHK is set to *DTAAUT

Does RPM Remote Print Manager® support Intelligent Printer Data Stream (IPDS) files from the AS/400 or IBM mainframe systems?

RPM cannot support IPDS. Our newest product, ExcelliPrint®, is currently available and supports IPDS extensively. To learn more about Excelliprint, please visit our IPDS site.

Does RPM Remote Print Manager® support printing AFPDS files generated from an AS/400 or System 390?

The AS/400 will convert AFPDS data streams via Host Print Transform for AS/400 printer emulations. An RPM raw type queue will pass the converted data directly to the printer bypassing the Windows print driver.

ExcelliPrint does handle AFPDS files, please visit ExcelliPrint's IPDS Printing home page. ExcelliPrint gives you the power to print IPDS to any Windows-based printer.

System 390 supports the AFPDS conversion via the Infoprint system. RPM can then pass the converted data directly to the Windows printer through an RPM raw type queue.

How do I create a PSFCFG to use with ExcelliPrint?

Your AS/400 operating system and release version may vary. For more detailed information on different OS/400 versions, please review appendix II in the manual.

Once created, you must change your device description to reference the PSFCFG. See the steps below for instructions.

Creating the PSFCFG for V4R5 and Later

  1. From an AS/400 command prompt, enter CRTPSFCFG and press F4.
  2. Press F24, then F9 to view all parameters.
  3. The following table shows the configuration needed for use with ExcelliPrint.
  PSF configuration . . . . . . . . . . . : EXCELLPSF
  Library . . . . . . . . . . . . . . . . : QUSRSYS
  User resource library . . . . . . . . . : *JOBLIBL
  IPDS pass through . . . . . . . . . . . : *YES
  Activate release timer. . . . . . . . . : *NORDYF
  Release timer . . . . . . . . . . . . . : *SEC15
  Restart timer . . . . . . . . . . . . . : *IMMED
  SNA retry count . . . . . . . . . . . . : 2
  Delay time between retries. . . . . . . : 0
  Blank page. . . . . . . . . . . . . . . : *YES
  Page size control . . . . . . . . . . . : *YES
  Resident fonts. . . . . . . . . . . . . : *YES
  Resource retention. . . . . . . . . . . : *YES
  Edge orient . . . . . . . . . . . . . . : *NO
  Remote location . . . . . . . . . . . . :
  Name or address . . . . . . . . . . . . : *NONE
  TCP/IP port . . . . . . . . . . . . . . : *NONE
  TCP/IP activation timer . . . . . . . . : 170
  PSF defined options . . . . . . . . . . : *NONE
  Text description. . . . . . . . . . . . : EXCELLIPRINT [ADDRESS]:[PORT]
  Device resource library list. . . . . . : *DFT

Changing the Device Description

  1. Make sure the writer is ended by issuing the following command: ENDWTR writer *IMMED.
  2. Now, vary off the device: VRYCFG device *PRT *OFF.
  3. Issue the Change Device Description command, CHGDEVD device, and press F4. Press F9 to view all parameters.
  4. Locate the User Defined Object parameter and enter the name of your PSFCFG (i.e. EXCELLPSF) which you created above, the Library where the PSFCFG is located, and the object type is *PSFCFG.
  5. Vary on the device and start the print writer (STRPRTWTR).

Can ExcelliPrint receive SCS files and create a PDF file from them?

Yes, the PSF can convert SCS to IPDS. To do so, simply place the SCS spool file in the IPDS device. The converted file is then sent to ExcelliPrint and a PDF file is created. Using the same method, ExcelliPrint can also create images files such as JPEG, TIFF, and PNG.

ExcelliPrint can also print SCS files the same way by converting the IPDS data into PCL or Windows EMF.

Every time a print job is released from the AS/400, I get the following message:

Load form type <TYPE> device <DEVICE> writer <WRITER>.

This message (CPA3394) is a safety mechanism to prompt you to load paper that has a form type matching the spool file output that is being sent to that printer. So, for instance, you do not print reports on expensive check paper. To answer this message automatically, configure the message in the Work with System Reply List command.

  1. To begin, enter the following from the command prompt: WRKRPYLE. This displays a screen showing all automatic system reply entries that are already configured on your AS/400.
  2. To add a new entry, press F6. This opens the Add Reply List Entry (ADDRPYLE) command.
  3. On this screen, enter the following fields:
    • Sequence Number -- Any unique number between 1 and 9999.
    • Message Identifier -- The load form type message ID, CPA3394 in this case.
    • Comparison Data -- The name of the device or *NONE (not recommended) for all devices.
    • Message Data Start Position -- Take the default *NONE.
    • Message Reply -- The automatic response value, G to start printing now (go).

ExcelliPrint main page

We are having a problem with INTELLIscribe. I think we need to upgrade to a newer version, but I'm not sure. What are some main reasons why people upgrade to newer versions of INTELLIscribe?

Each new release has either new features, resolved issues, or both. We have put together a "What's New" that shows the improvements made in each version. To find out your version of the program, choose About INTELLIscribe from the Help menu.

Category: 

Error: Unable to create MsgBoxer CoClass

The issue of the "unable to create MsgBoxer CoClass" should be resolved by installing the latest release of INTELLIscribe and rebooting the PC.
If this does not resolve the issue please contact Technical Support and we will resolve the issue.

When trying to print from INTELLIscribe to Linux, the Linux LPD rejects the request and logs an error stating:

	/usr/sbin/lpd: Malformed from address  

The message also appears in the Properties dialog in INTELLIscribe.

The new version of INTELLIscribe sends data on source ports greater than 1024. This is to circumvent a problem with Windows and port timeout periods. Some flavors of Unix and Linux, by default, will only accept data on source ports less than 1024. This is due to a security hole present in systems providing both FTP and LPR/LPD functionality.

INTELLIscribe may be modified to send data on ports less than 1024 in the virtual printer port wizard.

  1. From the Printers menu, choose Add or update virtual printer port.
  2. Click "Next" until the final step.
  3. Modify the "Relax port restr" parameter to display "no" by choosing this from the drop-down list.

When trying to print from INTELLIscribe to Linux, the Linux LPD accepts the entire print job, but does not print it. The job then disappears from the spooler. Unix logs the following errors:

	lp: illegal format character 'o'
	lp: job could not be printed

INTELLIscribe's Properties dialog states that the print job was successful.

INTELLIscribe, by default, specifies to the LPD print server that the data is in "postscript" format. If no Unix PostScript printers are available, or the queue receiving the print jobs is not configured for a PostScript printer, the job will not be printed by Unix.

The default works properly in most cases, however, some Unix LPD servers try to modify the data before printing it when following strict RFC1179 compliance.

You can configure INTELLIscribe to resolve this issue:

  1. From the Printers menu, choose Add or update virtual printer port.
  2. Click "Next" until the final step.
  3. Modify the "Print format" parameter to display "preformatted" by choosing this selection from the drop-down list.

Can INTELLIscribe be used to print from a Windows computer to a Unix computer running IBM AIX?

Yes, INTELLIscribe can print to IBM running AIX. Please check the following settings:

  1. The INTELLIscribe host must be listed in /etc/hosts.lpd file.
  2. A plus sign (+) must also be added to the /etc/hosts.lpd file at the end.
  3. The virtual printer port must be configured correctly:

LPD Queue Name: <same as AIX queue name>

Relax Port Restr: no

Note: The "print format" parameter should be "postscript" if the printer supports it or "preformatted" if not.

How do I print to a Tektronix Phaser 560 using INTELLIscribe?

First, the installation instructions for the network card on this printer state that the LPD queue name of "AUTO" or "PS" must be used, all upper case. Quoting from the TEK web site:

  • [For the Name or address of host providing LPD: enter the printer IP Address. For the name of printer on the machine: type AUTO or PS in all UPPERCASE letters (lowercase letters will not work).]

Second, the "Tektronics Phaser 560 Extended," should use the PSCRIPT.DRV "box" driver, which comes with Windows95/98 rather than a driver (e.g. "ADOBEPS4.DRV") from some vendor-supplied media.

Our recommendation to resolve this would be to first delete the Tektronics printer from the Settings/Printers window, and then to reinstall the same printer using the box driver (i.e. just the dialog that pops up when you click Add printer). This should reinstall the driver so that it does not use a language monitor. Should the problem still appear, then you need to edit the registry. Follow these steps to edit the registry:

  1. Choose Start\Run. In the text box, type "Regedit". Then press OK.
  2. Open the "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Environments\Windows 4.0\Drivers\Tektronix Phaser 560 Extended" key
  3. Determine what print driver is being used (e.g. "ADOBEPS4.DRV" or "PSCRIPT.DRV)
  4. Finally, change all the entries which read "ADOBEPS4.DRV" to "PSCRIPT.DRV".

Note: This assumes you have previously installed a PostScript printer, which you can check for by searching in that vicinity of the registry for the "PSCRIPT.DRV" string. If you cannot find it, then just install any PostScript   printer (e.g. Lexmark Optra S PS, HP LaserJet 4  PostScript , etc.) and then delete the printer, selecting "no" at the prompt to delete driver files.

How do I print to my Apple LaserWriter 16/600 using INTELLIscribe?

Set up the virtual printer:

  1. Choose a name
  2. Enter the IP address
  3. Select LPR/LPD
  4. Select Port 515
  5. Select "Add Destination"
  6. Select "Next."

The "LPD Queue Name" entry is specific to the LaserWriter 16/600, which uses the queue name to determine how to handle the end-of-line character. Normally, "raw" is the correct queue name to use. Using "raw" as the queue name in INTELLIscribe should not add any special control characters to the document, as is appropriate for PostScript and PCL5 print jobs.

However, if each new line of text starts where the previous one left off, creating a stairstep effect, then use "text" as the queue name. The reason for this is normally that your host (e.g. UNIX a system) uses LF as the end of line character and the LaserWriter is expecting CRLF. Selecting "text" as the queue name will append a carriage return to the end of each line in the document as it is printed.

I'm having trouble printing through INTELLIscribe to an Epilog Legend Engraver. Some problems are as folows:

  • The status window shows "submitted" or "started", but the job never prints
  • A message stating "List index out of bounds(0)" is received
  • The job prints but says "Failed" in the status window
  • A job prints over and over again 

These steps should resolve most issues when spooling print jobs to Epilog Legend Engravers:

  1. Upgrade to the latest version of INTELLIscribe. This can be downloaded here.
  2. In the virtual printer port wizard, configure the "Relax port restr" parameter to "no".
  3. In the virtual printer port wizard, configure the "Data File Ack" parameter to "no".
  4. In the virtual printer port wizard, configure the "LPD queue name" parameter to "Legend".

If the problems are still not solved, verify that your TCP/IP network configuration is correct. If you already have a network at your location, contact your system administrator for help on configuring your engraver and PC correctly.

If you are in an environment with only a single PC and an engraver, verify the following:

Your engraver and PC must have a different IP address

The default IP address for Epilog Engravers is 192.168.98.1 and the subnet mask is 255.255.255.0. You must configure the computer's IP address to be similar (on the same network of 192.168.98), but not identical. We suggest setting it to 192.168.98.2 and subnet mask the same 255.255.255.0. Once this is accomplished and the computer is restarted, try pinging the engraver with the command

	ping 192.168.98.1

If you receive 4 replies to your ping, then your configuration is correct.

If you are connecting through a network hub

Verify that your network cables are "straight through" cables. Straight through cables should be used in this instance because cross-over is accomplished by the hub.

If you are connecting directly to the Engraver from the PC

Verify that your network cable is a "cross-over" cable. Cross over cables are used in this instance to provide the network proper "listening" and "talking" wires.

I am using INTELLIscribe to print to my network printer. When I print a job, I sometimes get a page printed with the error:

Error defined Offending command.

This error is caused by a PostScript printer driver supplied by Adobe or the printer manufacturer. This problem can be resolved by installing a PostScript driver from the Windows CD-ROM. Any of the Windows PostScript drivers would be adequate, such as HP LaserJet 4V/4MV PostScript.

Do you have a list of LPD queue names that we can browse to find out our configuration for INTELLIscribe?

Here is a list of LPD queue names which we have collected. If you have documentation for your queue names, please look there before trying these queue names. Some of the queue names in this list may not work because they are specific to the type of LPD server installed in the printer.

Manufacturer Model Queue Name
Apple LaserWriter 16/600 raw
text
LaserWriter Pro 810 TEXT
PASSTHRU
LaserWriter 12/640PS raw
text
LaserWriter 8500 RAW
Axis 560 / 570 / 660 / 670 Externals PRn
Barr Systems Print Servers BARRTCP1
Canon 460 PS (no hard drive) xjprint
xjdirect
460 PS (with hard drive) xjprint
xjhold
GP Series Copier/Printer print
ImageRunner Printers (Fiery LAN adapter) print
Castelle LANpress L1
L2
LANpress 3 P1
P2
P3
D-Link DP-300
DP-301
LPT1_TEXT
LPT1
Decision Data Print Server d1prn
Digi Portserver Does not support LPD
Portserver II raw_n
Digital Products, Inc. NETPrint Print Server PORTn
EFI Canon CLC 300 / 320 / 350 Ext. PRn
Canon CLC 500 / 550 print_500-550
Canon CLC 700 / 800 print_700-800
Canon CLC 1000 print_1000
HP DeskJet 750C print_DJ750C
Kodak ColorEdge 1525 / 1525+ print_1525/25+
Kodak ColorEdge 1550 / 1550+ print_1550/50+
Kodak ColorEdge 1560 / 65 print_1560/65
Lanier 5506 DC print_r
Minolta CF80 print_CF80
Minolta CF900 print_Copier-M
NovaJet Pro print_NJPro
Oce 3107C / 3108C print_3107C/8C
Ricoh NC 5206 print_r
Ricoh 5206 print_r2
Ricoh 5006 print_r
Sharp AR-C860 print_r
Fiery XJ 5760 / 5765 print_5760/65
print_5760/65_1
Fiery XJ 5790 print_5790
Docucolor 4040 print_DocuColor
Emulex Corp. NETJex/NETQue print server TEXT
PASSTHRU
PASS
Epilog Legend Laser Engraver Legend
Epson Interface Card LPB
LPBF
Extended Systems ExtendNet Print Printern
GCC Technologies Elite XL EliteXL
HP JetDirect Internals raw
text
JetDirect Externals raw1 / text1
raw2 / text2
raw3 / text3
Intermec 4400 series PR1
I-Data Easycom 10 Printserver par1
Easycom 100 Printserver LPDPRT1
IBM Network Printer 12,17,24,14PS PASS
NP & Infoprint Printers (4300) series PASS
3130 afccu2
Intel NetPort Express 10/100 and Pro LPT1_PASSTHRU
LPT2_PASSTHRU
COM1_PASSTHRU
Lantronics EPS1, EPS2 (serial) EPS_nnnn_S1
(parallel) EPS_nnnn_P1
Lexmark RN+ printer
printer_cr
MarkNet XLe Adapter Parallel 1 printer
printer_cr
Parallel port 2 printer2
printer2_cr
Serial port printer9
printer9_cr
Optra S 1855 PASS
Linksys Print server box L1
L2
L3
Minolta QMS Magicolor 330 same as IP address
raw
OCE 3165 oce3165
9400 oce9400
Rose Electronics Microserve Print Servers lp
Tektronics Phaser 560(per language) PS
AUTO
HPGL
PCL
Xerox DocuPrint DP65 dp65
dt65
user-configurable
DocuCentre

DC265

lp

 

Models 4505, 4510, 4517, 4520 PASSTHRU
Model 4512 PORT1
Model N17, N24, N32 RAW
Models 4900, 4915, 4925, C55 PS
DocuCentre DC220/DC230 lp

Note: These names are all case-sensative. This means that you have to type the names exactly as you see them, uppercase letter, lowercase letter, forward slashes(/), dashes(-), and underscores(_). There are no spaces in any of the names. 

If you would like to help us accumulate and maintain this list, please give us feedback on this article. We are always open to feedback. If you submit an LPD queue name, be sure to include the printer model and hardware print server. Thank you!

I have configured INTELLIscribe to send to my network printer. After a few minutes, the job fails due to a "timeout" problem. On certain printers, the job may even print, but  INTELLIscribe e shows a status of "Failed" in the "Print Job Information" window. When I ping the printer, it replies quickly. In the print job "Properties" dialog, you may see a message stating a "timeout" or "List index out of bounds" message.

Some network print servers may not send an acknowledgement (ACK) back to INTELLIscribe after the last part of the print job is received. INTELLIscribe follows the LPR/LPD specifications exactly which state that the LPD should reply with an ACK after the control file and the data file(s). If  INTELLIscribe e does not get an ACK after the last part, the datafile by default, it will not close the connection, nor does the network printer close the connection. With the connection still open, the printer does not think the file has been completely received, and eventually the connection will timeout and the printer does not print the job.

The fix to this problem is rather simple. In step 4 of the "Add or Update Virtual Printer Port" wizard, set the following parameters:

  • Reverse Order: No
  • Control File ACK: Yes
  • Data File ACK: No

All other parameters should be left at the defaults. This should allow INTELLIscribe to close the connection, and the printer to think it has accepted the job. Your print jobs should be fine now.

Note: This problem has been reported in some, but not all, Xerox printers and with an Epilog Legend Engraver.

I'm trying to print to a  Lexmark printer. When I specify yes to print a banner page, the printer still does not print one. Is there a way to print a banner page to a Lexmark printer?

The Lexmark Marknet print server does not handle the banner page issue as the RFC1179 specifications say. You can tell the printer to print a banner page for all LPD print jobs by doing the following:

  1. Telnet to the printer. Select Start\Run... and type: telnet ipaddress 9000.
  2. At the menu, press 5 (Set LPD options) and press enter.
  3. Press 3 (Enable/Disable banner page on all lpr jobs) and press enter. Verify that this option shows ( Enabled )
  4. Enter 'X' to return to the main menu. Enter 'S' to save changes.
  5. Once the changes are saved, test the banner page by printing through INTELLIscribe.

The Lexmark printer should now print a banner page for all jobs printed using the LPR/LPD protocol. You do not need to specify 'yes' in the banner page option in INTELLIscribe since now the printer will print the banner whether you request it or not.

I have installed INTELLIscribe and set up a virtual printer port. If I install a printer and assign it to the INTELLIscribe port and finish it, then try to add another new printer, Windows tells me that I haven't finished installing the first printer.

This problem, though annoying, is not a fatal error. It has been encountered only if certain print drivers are used in conjunction with INTELLIscribe. The problem is resolved when the system is restarted.

The error is present due to interaction between the print driver and the spooler at the point of printer install only. The spooler tries to gather some driver/vendor specific information from the printer, which is not supported by INTELLIscribe

For more information on this problem go to this Microsoft KB article.

Category: 

I want to utilize the broadcast printing feature in INTELLIscribe®. What are the requirements and how do you configure the Virtual Printer Port?

The requirements are simple:

  • Install the software on a Windows-based system.
  • Your printers must be attached directly to the network and have TCP/IP support. Or, if you have a software LPD print server such as our RPM Remote Print Manager®, the printer can be attached to the computer where the software is installed.
  • Each printer needs to be the same model, or understand a common printer language such as PCL or PostScript.

Then, you need to create a virtual printer port following these instructions.

  1. In the INTELLIscribe window, choose Add from the Port menu. The Virtual Printer Port Wizard begins. Review the introduction page and click Next to begin
  2. This step requires you to enter a name to associate with the port, the name can contain spaces. Also, you are required to choose how the destinations will be used; Choose broadcast and click Next.
  3. Enter each destination that you need to print to, providing the TCP/IP Address or hostname of the printer, the protocol, and a port number. Once all the destinations are entered, click Next to continue.
  4. Customize protocol specific attributes. When using the LPR/LPD protocol, the Queue Name is a required parameter. Some printers require specific queue names. Consult your documentation, or check our website for the correct LPD queue name.
  5. Finally, open the Windows Printers folder and install a new printer. When you are prompted to select a port where the printer is attached, select the port you named in step 2.

I'm trying to uninstall INTELLIscribe from my computer to be placed on a new computer. There is no shortcut in the INTELLIscribe program group that allows me to uninstall the application.

There are a number of ways to remove the application from your computer. Microsoft recommends each Windows user know the existence of and use the Add or Remove Programs utility found in the Control Panel. To do this:

  1. From the Start menu, point to Settings, then select Control Panel. On the Windows XP, the Control Panel is found in the redesigned Start menu, not Settings.
  2. Click Add or Remove Programs. Find and highlight INTELLIscribe and click Change/Remove.
  3. The InstallShield Wizard for INTELLIscribe will guide you through the process of removing INTELLIscribe from your computer.

You can also execute the installation executable file again which will initiate uninstallation of INTELLIscribe if it is already installed.

The uninstall process involves a large number of steps including removing the program files from the target and Windows System folders, removing the port monitor from the Windows Print Manager, and the registry entries used by INTELLIscribe to store configuration and other settings. We do not recommend removing the application manually.

I have a Xerox DocuTech/Print 65. I need to print to it directly from a Windows 95 or 98 PC. How do I configure INTELLIscribe to print to this type of printer?

First provide INTELLIscribe with the IP Address or Hostname of the printer and the "LPD Queue Name". On the Xerox DP65 printer, the default LPD queue name is 'dp65', but that is entirely configurable. To find the LPD queue names available on your printer, type "list virtual printers" on the printer console. You can also find the IP address from the console.

Note: You must use a print driver that is compatible with the printer, but also one that does not use the PostScript driver provided by Adobe. This driver invokes a dialog each time the system is booted and cannot be suppressed.

I recently installed INTELLIscribe on my PC, created a "virtual printer port" and associated my print driver with it. Now, when I reboot my computer, I get the following warning message:

This warning occurs during system startup or login because of print drivers that use language monitors. Unfortunately, most of these print drivers do not provide a mechanism to easily disable the download of fonts on system startup.

Most printers that cause this problem are PostScript printers using the 'ADOBEPS4.DRV'. There are several ways to fix this.

  • The best way: First, delete the printer from the Windows Printers folder. Then, add a new printer using the driver provided on the Windows CD-ROM. Non of these box drivers cause this issue. Usually, a compatible driver can be found even if your specific printer is not on the CD.
  • May cause problems, so do not attempt this unless you cannot find another compatible driver. From the Windows "Start" button, choose "Run". Type 'msconfig' and press OK. In the "Startup" tab, unselect "BRI Fixup Ports". This will ensure that INTELLIscribe will not check the printers at startup, thereby eliminating the warning. Keep in mind that INTELLIscribe may not function properly with this not selected.
  • Could be dangerous: Another way to eliminate this issue is to edit the registry. Changing any reference showing 'ADOBEPS4.DRV' to 'PSCRIPT.DRV'. The registry key you need to modify is HKey_Local_Machine\System\CurrentControlSet\Control\Print\Environments\Windows 4.0\(Printer). Note that you must have another PostScript driver added for 'PSCRIPT.DRV' to be installed.

Note: Editing the registry should only be done in extreme cases. Editing the registry can seriously damage your system or make it unbootable. Only edit the registry after you have backed up the system so you can restore later if problems appear. If you do not feel comfortable editing the registry, contact your system administrator.

I am trying to print to a Fiery XJ network printer from INTELLIscribe. The problem is, I don't know what the queue name is for this printer.

There seem to be as many queue names for these printers as there are printers. Sometimes the queue names resemble the printer model. For instance, for the Fiery XJ 5790 model the queue name in lowercase letters (uppercase letter will not work) is "print_5790". If you have a different model, try print_ and the model number of your printer.

Consult your documentation if this does not work.

I installed INTELLIscribe on my computer and it has been working well. After performing some maintenance and cleanup on my computer, now INTELLIscribe will not start. I receive the following error message when I attempt to open INTELLIscribe:

This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.

INTELLIscribe 4.0 requires the latest version of the Microsoft Visual C++ Runtime, which is installed during INTELLIscribe setup. If you uninstall the Microsoft Visual C++ Runtime manually, INTELLIscribe will fail to work and report this error.

To resolve this issue, perform an upgrade by running the setup program again.

If Microsoft Visual C++ Runtime causes issues with other applications requiring the Visual C++ 8 Runtime, upgrade those applications to a version supporting the Windows side-by-side assemblies (WinSxS). To learn more about WinSxS, search the Microsoft MSDN website or look at this Microsoft KB article.

Category: 

After installing INTELLIscribe, I create a new port with the appropriate settings. Then, I open the Windows Print Manager and try to associate that port with an existing printer. The following error message appears:

Printer settings could not be saved. The specified port is unknown.

The Print Manager on Windows NT 4.0 does not query the INTELLIscribe port monitor every time it is needed. There are 2 ways around this issue.

  1. Restart the Windows Spooler service. To do this, open the command prompt and type net stop spooler and wait for the service to stop. Then type net start spooler and wait for the service to start. Once started again, you should now be able to select the INTELLIscribe port from the printer properties dialog..
  2. Instead of using the INTELLIscribe user interface to create the port, use the Windows Print Manager. To do this, open the Properties for the printer, then in the Ports tab, choose to create a new port.

I am trying to print to a Apple LaserWriter 16/600 PostScript printer using INTELLIscribe. I've used the queue name of "raw" in the LPD Queue Name parameter in the Virtual Printer Port wizard. Now, when I send a job to the printer, I get the following message:

This job cannot print because its header is not in the printer.
Please return to the driver's dialog box, mark the header as not
in the printer, and then print again. 

This is a setting in the print driver properties for the Apple LaserWriter PostScript printer. Other printers may also have this problem.

  1. Press Start-->Settings. Click Printers.
  2. Right-click on the printer and choose "Properties" from the pop-up menu.
  3. In the "PostScript" tab, choose "Download header with each print job".
  4. Press OK.

This should correct this problem.

My printer is an Apple LaserWriter Pro 810 and it has a built in print server. I cannot configure my print server to work with INTELLIscribe.

The LaserWriter Pro 810 does not support the JetDirect protocol. You must select the LPD:515 protocol in INTELLIscribe and assign it a queue name. The built-in queue names for this print server are "TEXT" and "PASSTHRU" (remember that the queue names are case-sensitive).

"PASSTHRU" should be used as the data will already be formatted for the printer.

Can INTELLIscribe print through a firewall?

There are many ways to print from INTELLIscribe through a firewall. Just like all network questions, it depends on how the firewall is configured and what functions it is performing.

If your firewall is performing Network Address Translation (NAT), you will configure port forwarding on your firewall. The virtual printer port will be configured to use the external IP address of your firewall.

  • If you are using the LPR/LPD protocol, you will forward traffic coming in on the port configured in INTELLIscribe to the internal IP address of the printer or print server. The internal port number should always be 515.
  • If you are using Jetdirect, you will forward traffic coming in on the port configured in the INTELLIscribe virtual printer port to the internal IP address of the Jetdirect printer or print server, using whichever port your server is listening on, typically 9100, 9101, or 9102. Check your Jetdirect print server documentation for the correct port number.

If your firewall is not performing NAT, you will simply allow data to go through your firewall. This is called relaxing a port. In this case, you will configure the destination in INTELLIscribe to use the printer or print server's IP address.

Note: Your firewall may require you to supply the type of connection; both LPR/LPD and streams printing are TCP connections, not UDP.

Also remember that some low-end, low-cost firewalls do not support port forwarding.

During the INTELLIscribe setup, I got an error that states "BISILOCK.DLL uses function #6883 in MFC42.dll."

This error is caused by an outdated version of the MFC42.dll file. The fix could be either of the following:

  1. First try rebooting your machine. This file may be in use and cannot be updated by the INTELLIscribe setup program until you reboot your PC.
  2. INTELLIscribe may be using a file that is located in a different directory. You may have more than one file on your system, even if one of them is the newest version (6.00.8447.0) but one is older, this might be causing your problem. You should delete all occurrences of this file on your hard disk except for the newest version in your C:\Windows\System directory. Follow these steps:
    1. Choose Start\Find\Files or Folders.
    2. Find "MFC42.DLL" (without quotes) on all local harddrives
    3. Delete all MFC42.DLL files except in the Windows\System directory.

Note: When you are having problems, you need to reboot often. For instance, if you uninstall INTELLIscribe, reboot even if it says that it was removed completely. Similarly, reboot after installing, even if the install program doesn't ask you to.

Category: 

When printing from INTELLIscribe to IBM AIX, the status information contains the following warning:

  Host does not have access to line printers

Ensure that a plus sign (+) appears at the end of the /etc/hosts.lpd file. The problem should then be resolved.

AFP (1)

Does RPM Remote Print Manager® support printing AFPDS files generated from an AS/400 or System 390?

The AS/400 will convert AFPDS data streams via Host Print Transform for AS/400 printer emulations. An RPM raw type queue will pass the converted data directly to the printer bypassing the Windows print driver.

ExcelliPrint does handle AFPDS files, please visit ExcelliPrint's IPDS Printing home page. ExcelliPrint gives you the power to print IPDS to any Windows-based printer.

System 390 supports the AFPDS conversion via the Infoprint system. RPM can then pass the converted data directly to the Windows printer through an RPM raw type queue.

ASA (1)

I have files with ASA carriage control, also known as FORTRAN control characters, that I need to print. Can RPM convert ASA carriage control properly?

RPM Remote Print Manager® supports ASA characters where appropriate using a transform specific to this data format, which also known as Fortran formatted data.

The following list shows the ASA carriage control characters and how they are interpreted by RPM. For each character the action follows:

0 Insert a blank line before the current line
1 Draw the current line at the top of the next page
+ Return to the beginning of the current line; used to overwrite
- Insert two blank lines before the current line

All other characters residing on the first column of each line are ignored and the remainder of the line is printed single-spaced.

Category: 

ASCII (6)

Your AS/400 setup instructions show to place "XAIX XAUTOQ" into the "Desination Options" parameter in the AS/400 OUTQ.  What do these options do, and what other options can I use?

You can find a description of the XAUTOQ parameter here.

The "Destination Options" parameter specifies the destination-dependent options. These options may be specific to a particular implementation of an LPD print server. When this parameter is not specified, the SNDTCPSPLF command sends default options that are common to most LPD print servers. The options specified by this parameter are inserted into the LPR/LPD control file generated by the SNDTCPSPLF command, one option per line, and sent to RPM.

The options specified by this parameter must have the following format:
"option1 option2 option3...optionN"
Each option is separated from the next by one or more spaces.

Options typically have a format of <control character><value>. An example is
"JJob_name"
J specifies the job name for the banner page and "Job_name" is what RPM would print on the banner page. SNDTCPSPLF examines the first character of each option to determine if it is a reserved control character. If any of the following control characters are specified, the option is ignored and a warning message is generated.

C T H U I W L 1 M 2 N 3 P 4 S k

For example "Class=ASCII" is not allowed because the "C" control character is reserved for use by the SNDTCPSPLF command. However, "-Class=ASCII" is permitted. The control character "X" is allowed, but the value of "AS/400" used with it is not permitted. For example, "XRPM" can be specified, but "XAS/400" cannot be.

The option "XAS/400" is reserved for use by the SNDTCPSPLF command as are the letters listed above. XAS/400 is used to indicate to another AS/400 that the request is coming from an AS/400.

The option "XAIX" controls how multiple copies are sent to the printer. This option is not the default, but should always be used when printing to RPM. XAIX specifies that the data and control files are to be sent multiple times, once for each copy. The default is to send the data and control files once, with multiple print commands in the control file.

c n d p f r g t l v

If one of these characters is specified as the first character in a destination option, the character is used on the "print file" command in the control file. Only the first occurrence of one of these characters in this position is used in the control file. Subsequent use of these characters in this position is ignored. If none of these options is specified, the default character "l" is used on the "print file" command, which prints the file "as is" without filtering out any control characters.

There is no page between jobs.

This is a factor for raw printing. Text printing separates documents courtesy the Windows print drivers.

RPM offers several banner types as well as a PCL page seperator. It also supports insert and append byte strings as described below. These would be configured as transforms in the queue setup.

I want to receive a print job in RPM from an AS/400 without any printer control characters. Is this possible?

The AS/400 setup instructions show how to receive data into RPM from the AS/400 with Host Print Transform disabled. In this case, RPM will receive SCS data. You can then use the SCS to Text Markup and Remove text markup transforms in RPM to get plain text. Some users have mentioned they get an extra blank line on the first page of the resulting document.

To prevent the random blank line and instead use the AS/400 to perform the EBCDIC conversion leaving plain text, use all settings specified in the AS/400 setup instructions except the following.

  • Host Print Transform: *YES
  • Manufacturer type and model: *WSCST
  • Workstation customizing object: QWPDEFAULT
  • Library: QSYS

You will now get the data without specific printer codes embedded in the document.

We need RPM Remote Print Manager® to translate EBCDIC to ASCII.

RPM has a native EBCDIC translator, which can handle not only US EBCDIC but European language extensions from a variety of countries.

Follow these steps to use the EBCDIC translator:

For RPM 5.0 and newer:

The SCS to Text Markup transform natively supports this translation. You can also change codepages on the various Text to Text Markup transforms.

For RPM 4.5:

  1. Select "Edit Queues" from the "Queues" menu in RPM.
  2. Choose which queue you want to translate from the drop-down queue list.
  3. Press the "Print Data Options" button.
  4. In the "Transform" tab, check "EBCDIC". Also, you can choose (from the drop-down list) to have RPM use a different language for translation. By default, RPM will pick the language closest to your computer's locale setting.

How do I get RPM Remote Print Manager® to print both text and PostScript correctly?

This is why the LPD protocol supports multiple queues. Set up one queue to print text, with the characteristics you want; set up another queue to pass the PostScript data directly to the printer.

We are sometimes asked whether RPM will automatically switch from text to pass-through when it looks at the data. This is not as simple as it may seem. RPM may support this in the future but for now we recommend multiple queues.

Category: 

Is there any way for RPM to print a document correctly with mixed font styles such as bold, italics, or both?

The answer depends on data in the incoming print job.

  1. If you are printing SCS from an iSeries computer, RPM can handle most font styles and changes automatically. The Remote OUTQ may need to be configured differently than normal. Setting the Host Print Transform parameter to *NO will cause RPM to receive raw SCS data. In the Print Data Options for your RPM queue, turn on Convert SCS to ASCII. RPM supports and interprets most, but not all, SCS commands.
  2. RPM understands two other ways to print bold: using backspace (0x08) or a carriage return (0x0C) without a line feed. We suggest opening the data file in a hexadecimal editor looking for these two characters. RPM also supports strikethrough and underlined text using this method as well.
  3. At this time, RPM does not interpret bold printing with any other format. RPM removes the PCL formatting instructions and, since bold printing is performed by a PCL sequence, no font change instructions remain. Future versions of RPM may support bold printing when the incoming data is PCL.

Binary (1)

When I print, I get a stair step effect.

The reason for this is your Host (e.g. a UNIX system) uses LF as the end of line character and the printer is expecting CR/LF.

For RPM 6.0: add the "Unix to DOS" transform to the setup for this queue.

For RPM 5.0: add the "LF to CRLF" transform to the setup for this queue. Typically it would go at the beginning of the transform list, or just following a code page (data format translation) step.

For RPM 4.5 and prior: this is generally associated with a "RAW" type Queue. To Translate the LF to CR/LF do the following:

  1. Verify the Queue type is RAW
  2. Select the Queue Setup in the Edit Queues Window.
  3. Select Translate LF to CR/LF.

Code page (1)

I have changed my code page to print in a different language, but now when I print to RPM Remote Print Manager®, certain characters are replaced with a question mark (?). Why?

The printed "?" means that the character is not supported by the current code page. You need to change your code page to one that supports the character you're trying to print. The code page is in the Text Setup dialog.

If you've selected the correct code page, try a different script. To do this, follow the steps below.

  1. From the 'Queues' menu, choose 'Edit Queues:'.
  2. In the 'Edit Queues' dialog, make sure the 'Text' queue type is selected. Press the 'Queue Setup' button.
  3. In the 'Text Setup' dialog, you will see the Windows code page you are using. Verify the correct code page is selected. Press the 'Font' button. Note that it may be labeled 'Courier New 12' or similar.
  4. The 'Font' dialog is where you select the proper script. There could be multiple scripts depending on the language. You need to experiment to see which translates your document with the correct characters.

EBCDIC (1)

We need RPM Remote Print Manager® to translate EBCDIC to ASCII.

RPM has a native EBCDIC translator, which can handle not only US EBCDIC but European language extensions from a variety of countries.

Follow these steps to use the EBCDIC translator:

For RPM 5.0 and newer:

The SCS to Text Markup transform natively supports this translation. You can also change codepages on the various Text to Text Markup transforms.

For RPM 4.5:

  1. Select "Edit Queues" from the "Queues" menu in RPM.
  2. Choose which queue you want to translate from the drop-down queue list.
  3. Press the "Print Data Options" button.
  4. In the "Transform" tab, check "EBCDIC". Also, you can choose (from the drop-down list) to have RPM use a different language for translation. By default, RPM will pick the language closest to your computer's locale setting.

PCL (5)

I want to receive a print job in RPM from an AS/400 without any printer control characters. Is this possible?

The AS/400 setup instructions show how to receive data into RPM from the AS/400 with Host Print Transform disabled. In this case, RPM will receive SCS data. You can then use the SCS to Text Markup and Remove text markup transforms in RPM to get plain text. Some users have mentioned they get an extra blank line on the first page of the resulting document.

To prevent the random blank line and instead use the AS/400 to perform the EBCDIC conversion leaving plain text, use all settings specified in the AS/400 setup instructions except the following.

  • Host Print Transform: *YES
  • Manufacturer type and model: *WSCST
  • Workstation customizing object: QWPDEFAULT
  • Library: QSYS

You will now get the data without specific printer codes embedded in the document.

CL codes are showing in my print job and I am using a "raw" type queue.

This could be caused by any of the following:

  • The printer does not support PCL 

If this is the case, you must either format the data differently on the sending side, or use a "text" type queue when that is not possible.

  • The printer does not support that PCL version 

Format the data using a PCL level that the printer does understand.

  • The Windows driver is using different PCL version than what is in the file 

Change the Windows print driver to one that supports the same PCL version that is in the file or use a "text" type queue in RPM if that is not possible.

Category: 

My new HP printer has many internal fonts. The problem is, in the RPM Remote Print Manager® "TEXT" queue setup, these fonts cannot be selected. What can I do if I want to use internal fonts with my printer?

HP printers that use PCL 6 such as the 4050 and 8100 models show they have internal fonts, however, when you try to use the internal fonts, they are not accessible. I believe this is a driver issue and not a printer issue. It is definitely caused by the printer and not the RPM program.

Have you tried using these fonts with any other program?

You can get access to these fonts by using an older driver such as the HP 4000 or the HP 8000 driver or another compatible driver.

Category: 

I want to utilize the broadcast printing feature in INTELLIscribe®. What are the requirements and how do you configure the Virtual Printer Port?

The requirements are simple:

  • Install the software on a Windows-based system.
  • Your printers must be attached directly to the network and have TCP/IP support. Or, if you have a software LPD print server such as our RPM Remote Print Manager®, the printer can be attached to the computer where the software is installed.
  • Each printer needs to be the same model, or understand a common printer language such as PCL or PostScript.

Then, you need to create a virtual printer port following these instructions.

  1. In the INTELLIscribe window, choose Add from the Port menu. The Virtual Printer Port Wizard begins. Review the introduction page and click Next to begin
  2. This step requires you to enter a name to associate with the port, the name can contain spaces. Also, you are required to choose how the destinations will be used; Choose broadcast and click Next.
  3. Enter each destination that you need to print to, providing the TCP/IP Address or hostname of the printer, the protocol, and a port number. Once all the destinations are entered, click Next to continue.
  4. Customize protocol specific attributes. When using the LPR/LPD protocol, the Queue Name is a required parameter. Some printers require specific queue names. Consult your documentation, or check our website for the correct LPD queue name.
  5. Finally, open the Windows Printers folder and install a new printer. When you are prompted to select a port where the printer is attached, select the port you named in step 2.

Can ExcelliPrint receive SCS files and create a PDF file from them?

Yes, the PSF can convert SCS to IPDS. To do so, simply place the SCS spool file in the IPDS device. The converted file is then sent to ExcelliPrint and a PDF file is created. Using the same method, ExcelliPrint can also create images files such as JPEG, TIFF, and PNG.

ExcelliPrint can also print SCS files the same way by converting the IPDS data into PCL or Windows EMF.

PDF (2)

Can I use Ghostscript with RPM Remote Print Manager® (RPM)?

Ghostscript is a PostScript interpreter. PostScript is the most common printer language and is supported by most laser printers from nearly every printer manufacturer. However, there are a number of printers, laser and inkjet both, that do not support PostScript; this is where Ghostscript becomes useful.

The most common reason to use Ghostscript is to convert a PostScript file to PDF. Ghostscript can also output other formats including graphics formats (PNG, JPEG, TIFF, etc.) and printer formats (PCL5, PXL, epson). The second most common reason to use Ghostscript is to print PostScript files to a printer that does not support it.

How to download Ghostscript

You'll need to do a web search such as:

You should be able to find instructions to download and install the software.

You will also need to review the license information which comes with Ghostscript to verify that your use will be in compliance with the copyright holder's terms. This is not something Brooks can help you with.

However, the rest of our instructions will assume you can use GhostScript with permission as intended.

Convert Postscript to PDF

  1. In Queue Settings, create a new Filter action.
  2. Next to Command, click Browse and locate gswin32.exe. For instance, at this writing it was located in C:\Program Files\gs\gs8.64\bin\.
  3. If you are using a filter action, the Arguments should be:
    -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=%n.pdf %s

    If you are using a filter transform, the Arguments would be slightly different:
    -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=%o %s

  4. Set the Working directory to the folder in which you want the PDF file to be saved. To eliminate many issues, this folder should be local.

Note that the %s, %o, and %n are variables (placeholders).  RPM will substitute those values with the appropriate values.  A complete list of available variables is found in the RPM manual under both Filter transforms (page 13) and Filter actions (page17).

Print Postscript to a non-Postscript printer

  1. In Queue Settings, create a new Filter action.
  2. Next to Command, click Browse and locate gswin32.exe. It may be located in C:\Program Files\gs\gs8.64\bin\.
  3. The arguments should be:
    -dNOPAUSE -dBATCH -sDEVICE=mswinpr2 -sOutputFile="\\spool\<Printer Name>" "%s"

Substitute the name of the printer to which you want to print in place of <Printer Name>. This is the name found in the Printers folder.

Note: Certain situations may prevent gswin32 from completing successfully.  Each of the following methods have proven useful to resolve the problem at one time or another.  We suggest trying each method in the order it appears and testing each change until you find the first method that works.

  • The option -dBATCH tells gswin32 it is running as a batch and should exit when finished.  It has been added to these instructions.
  • Try adding the word 'quit' as the last argument to the command line.
  • Add an Append bytes transform to append the word quit to the end of the data file.  One customer reported this method corrupted PDF Documents when attempting to convert Color PostScript files.
  • Configure your Filter action or transform to terminate idle process after a few seconds.  This option will cause gswin32 to close, but it may not be finished with the conversion.

If you encounter any problems, enter the login credentials of the user you are logged on as and select Interact with Desktop. The next time a job is received, the Ghostscript window will be displayed where you can troubleshoot errors. Once resolved, remove the credentials.

Can ExcelliPrint receive SCS files and create a PDF file from them?

Yes, the PSF can convert SCS to IPDS. To do so, simply place the SCS spool file in the IPDS device. The converted file is then sent to ExcelliPrint and a PDF file is created. Using the same method, ExcelliPrint can also create images files such as JPEG, TIFF, and PNG.

ExcelliPrint can also print SCS files the same way by converting the IPDS data into PCL or Windows EMF.

PostScript (12)

Can I use Ghostscript with RPM Remote Print Manager® (RPM)?

Ghostscript is a PostScript interpreter. PostScript is the most common printer language and is supported by most laser printers from nearly every printer manufacturer. However, there are a number of printers, laser and inkjet both, that do not support PostScript; this is where Ghostscript becomes useful.

The most common reason to use Ghostscript is to convert a PostScript file to PDF. Ghostscript can also output other formats including graphics formats (PNG, JPEG, TIFF, etc.) and printer formats (PCL5, PXL, epson). The second most common reason to use Ghostscript is to print PostScript files to a printer that does not support it.

How to download Ghostscript

You'll need to do a web search such as:

You should be able to find instructions to download and install the software.

You will also need to review the license information which comes with Ghostscript to verify that your use will be in compliance with the copyright holder's terms. This is not something Brooks can help you with.

However, the rest of our instructions will assume you can use GhostScript with permission as intended.

Convert Postscript to PDF

  1. In Queue Settings, create a new Filter action.
  2. Next to Command, click Browse and locate gswin32.exe. For instance, at this writing it was located in C:\Program Files\gs\gs8.64\bin\.
  3. If you are using a filter action, the Arguments should be:
    -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=%n.pdf %s

    If you are using a filter transform, the Arguments would be slightly different:
    -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=%o %s

  4. Set the Working directory to the folder in which you want the PDF file to be saved. To eliminate many issues, this folder should be local.

Note that the %s, %o, and %n are variables (placeholders).  RPM will substitute those values with the appropriate values.  A complete list of available variables is found in the RPM manual under both Filter transforms (page 13) and Filter actions (page17).

Print Postscript to a non-Postscript printer

  1. In Queue Settings, create a new Filter action.
  2. Next to Command, click Browse and locate gswin32.exe. It may be located in C:\Program Files\gs\gs8.64\bin\.
  3. The arguments should be:
    -dNOPAUSE -dBATCH -sDEVICE=mswinpr2 -sOutputFile="\\spool\<Printer Name>" "%s"

Substitute the name of the printer to which you want to print in place of <Printer Name>. This is the name found in the Printers folder.

Note: Certain situations may prevent gswin32 from completing successfully.  Each of the following methods have proven useful to resolve the problem at one time or another.  We suggest trying each method in the order it appears and testing each change until you find the first method that works.

  • The option -dBATCH tells gswin32 it is running as a batch and should exit when finished.  It has been added to these instructions.
  • Try adding the word 'quit' as the last argument to the command line.
  • Add an Append bytes transform to append the word quit to the end of the data file.  One customer reported this method corrupted PDF Documents when attempting to convert Color PostScript files.
  • Configure your Filter action or transform to terminate idle process after a few seconds.  This option will cause gswin32 to close, but it may not be finished with the conversion.

If you encounter any problems, enter the login credentials of the user you are logged on as and select Interact with Desktop. The next time a job is received, the Ghostscript window will be displayed where you can troubleshoot errors. Once resolved, remove the credentials.

When I set up an RPM Remote Print Manager® queue to receive text, I can send a PostScript file but of course it prints with all its programming language text. Are you aware of any software that can allow my PC to become a PostScript or Encapsulated PostScript server to my Unix workstation?

The Ghostscript application is a postscript translation application. You can use a Filter type queue in RPM, call the Ghostscript application from the command line, pass the file to Ghostscript. Ghostscript will translate the file and send it to the printer. Ghostscript is shareware and can be downloaded from the Internet.

If you would like more information about Ghostscript, what it can do, or how to implement it using RPM, click on this FAQ. You can also get more information about it by going directly to the website.

When trying to print from INTELLIscribe to Linux, the Linux LPD accepts the entire print job, but does not print it. The job then disappears from the spooler. Unix logs the following errors:

	lp: illegal format character 'o'
	lp: job could not be printed

INTELLIscribe's Properties dialog states that the print job was successful.

INTELLIscribe, by default, specifies to the LPD print server that the data is in "postscript" format. If no Unix PostScript printers are available, or the queue receiving the print jobs is not configured for a PostScript printer, the job will not be printed by Unix.

The default works properly in most cases, however, some Unix LPD servers try to modify the data before printing it when following strict RFC1179 compliance.

You can configure INTELLIscribe to resolve this issue:

  1. From the Printers menu, choose Add or update virtual printer port.
  2. Click "Next" until the final step.
  3. Modify the "Print format" parameter to display "preformatted" by choosing this selection from the drop-down list.

Can INTELLIscribe be used to print from a Windows computer to a Unix computer running IBM AIX?

Yes, INTELLIscribe can print to IBM running AIX. Please check the following settings:

  1. The INTELLIscribe host must be listed in /etc/hosts.lpd file.
  2. A plus sign (+) must also be added to the /etc/hosts.lpd file at the end.
  3. The virtual printer port must be configured correctly:

LPD Queue Name: <same as AIX queue name>

Relax Port Restr: no

Note: The "print format" parameter should be "postscript" if the printer supports it or "preformatted" if not.

How do I print to a Tektronix Phaser 560 using INTELLIscribe?

First, the installation instructions for the network card on this printer state that the LPD queue name of "AUTO" or "PS" must be used, all upper case. Quoting from the TEK web site:

  • [For the Name or address of host providing LPD: enter the printer IP Address. For the name of printer on the machine: type AUTO or PS in all UPPERCASE letters (lowercase letters will not work).]

Second, the "Tektronics Phaser 560 Extended," should use the PSCRIPT.DRV "box" driver, which comes with Windows95/98 rather than a driver (e.g. "ADOBEPS4.DRV") from some vendor-supplied media.

Our recommendation to resolve this would be to first delete the Tektronics printer from the Settings/Printers window, and then to reinstall the same printer using the box driver (i.e. just the dialog that pops up when you click Add printer). This should reinstall the driver so that it does not use a language monitor. Should the problem still appear, then you need to edit the registry. Follow these steps to edit the registry:

  1. Choose Start\Run. In the text box, type "Regedit". Then press OK.
  2. Open the "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Environments\Windows 4.0\Drivers\Tektronix Phaser 560 Extended" key
  3. Determine what print driver is being used (e.g. "ADOBEPS4.DRV" or "PSCRIPT.DRV)
  4. Finally, change all the entries which read "ADOBEPS4.DRV" to "PSCRIPT.DRV".

Note: This assumes you have previously installed a PostScript printer, which you can check for by searching in that vicinity of the registry for the "PSCRIPT.DRV" string. If you cannot find it, then just install any PostScript   printer (e.g. Lexmark Optra S PS, HP LaserJet 4  PostScript , etc.) and then delete the printer, selecting "no" at the prompt to delete driver files.

I send PostScript files and they print as PostScript code.

Use a Raw Print action instead of a Text Print action in order to pass the PostScript to printer.

If your printer does not support PostScript please see our instructions for using Ghostscript.

I am using INTELLIscribe to print to my network printer. When I print a job, I sometimes get a page printed with the error:

Error defined Offending command.

This error is caused by a PostScript printer driver supplied by Adobe or the printer manufacturer. This problem can be resolved by installing a PostScript driver from the Windows CD-ROM. Any of the Windows PostScript drivers would be adequate, such as HP LaserJet 4V/4MV PostScript.

How do I get RPM Remote Print Manager® to print both text and PostScript correctly?

This is why the LPD protocol supports multiple queues. Set up one queue to print text, with the characteristics you want; set up another queue to pass the PostScript data directly to the printer.

We are sometimes asked whether RPM will automatically switch from text to pass-through when it looks at the data. This is not as simple as it may seem. RPM may support this in the future but for now we recommend multiple queues.

Category: 

I want to utilize the broadcast printing feature in INTELLIscribe®. What are the requirements and how do you configure the Virtual Printer Port?

The requirements are simple:

  • Install the software on a Windows-based system.
  • Your printers must be attached directly to the network and have TCP/IP support. Or, if you have a software LPD print server such as our RPM Remote Print Manager®, the printer can be attached to the computer where the software is installed.
  • Each printer needs to be the same model, or understand a common printer language such as PCL or PostScript.

Then, you need to create a virtual printer port following these instructions.

  1. In the INTELLIscribe window, choose Add from the Port menu. The Virtual Printer Port Wizard begins. Review the introduction page and click Next to begin
  2. This step requires you to enter a name to associate with the port, the name can contain spaces. Also, you are required to choose how the destinations will be used; Choose broadcast and click Next.
  3. Enter each destination that you need to print to, providing the TCP/IP Address or hostname of the printer, the protocol, and a port number. Once all the destinations are entered, click Next to continue.
  4. Customize protocol specific attributes. When using the LPR/LPD protocol, the Queue Name is a required parameter. Some printers require specific queue names. Consult your documentation, or check our website for the correct LPD queue name.
  5. Finally, open the Windows Printers folder and install a new printer. When you are prompted to select a port where the printer is attached, select the port you named in step 2.

I recently installed INTELLIscribe on my PC, created a "virtual printer port" and associated my print driver with it. Now, when I reboot my computer, I get the following warning message:

This warning occurs during system startup or login because of print drivers that use language monitors. Unfortunately, most of these print drivers do not provide a mechanism to easily disable the download of fonts on system startup.

Most printers that cause this problem are PostScript printers using the 'ADOBEPS4.DRV'. There are several ways to fix this.

  • The best way: First, delete the printer from the Windows Printers folder. Then, add a new printer using the driver provided on the Windows CD-ROM. Non of these box drivers cause this issue. Usually, a compatible driver can be found even if your specific printer is not on the CD.
  • May cause problems, so do not attempt this unless you cannot find another compatible driver. From the Windows "Start" button, choose "Run". Type 'msconfig' and press OK. In the "Startup" tab, unselect "BRI Fixup Ports". This will ensure that INTELLIscribe will not check the printers at startup, thereby eliminating the warning. Keep in mind that INTELLIscribe may not function properly with this not selected.
  • Could be dangerous: Another way to eliminate this issue is to edit the registry. Changing any reference showing 'ADOBEPS4.DRV' to 'PSCRIPT.DRV'. The registry key you need to modify is HKey_Local_Machine\System\CurrentControlSet\Control\Print\Environments\Windows 4.0\(Printer). Note that you must have another PostScript driver added for 'PSCRIPT.DRV' to be installed.

Note: Editing the registry should only be done in extreme cases. Editing the registry can seriously damage your system or make it unbootable. Only edit the registry after you have backed up the system so you can restore later if problems appear. If you do not feel comfortable editing the registry, contact your system administrator.

I am trying to print to a Apple LaserWriter 16/600 PostScript printer using INTELLIscribe. I've used the queue name of "raw" in the LPD Queue Name parameter in the Virtual Printer Port wizard. Now, when I send a job to the printer, I get the following message:

This job cannot print because its header is not in the printer.
Please return to the driver's dialog box, mark the header as not
in the printer, and then print again. 

This is a setting in the print driver properties for the Apple LaserWriter PostScript printer. Other printers may also have this problem.

  1. Press Start-->Settings. Click Printers.
  2. Right-click on the printer and choose "Properties" from the pop-up menu.
  3. In the "PostScript" tab, choose "Download header with each print job".
  4. Press OK.

This should correct this problem.

I am trying to print jobs to a low-cost inkjet printer. Using a Raw printer action, the RPM Remote Print Manager® (RPM) log indicates the job has been printed, but nothing is printed to the physical printer. What can I do to resolve this problem?

To save on cost, most inkjet printers do not have any internal processing power, but instead rely on Windows and the driver for all processing. These printers cannot print even a plain text document unless the application uses the Windows print driver.

The purpose of the Raw print action is to bypass the print driver altogether. This requires the printer be supported by the sending system. Low-cost inkjet printers rarely, if ever, support any operating system other than Windows.

Luckily, RPM's text printing functionality can resolve this problem. If the incoming data is plain text, use a Text markup transform and a Text print action to print these jobs to any printer with a supported Windows driver.

If the incoming data is PostScript, see the section titled Print Postscript to a non-Postscript printer in this FAQ.

SCS (3)

I want to receive a print job in RPM from an AS/400 without any printer control characters. Is this possible?

The AS/400 setup instructions show how to receive data into RPM from the AS/400 with Host Print Transform disabled. In this case, RPM will receive SCS data. You can then use the SCS to Text Markup and Remove text markup transforms in RPM to get plain text. Some users have mentioned they get an extra blank line on the first page of the resulting document.

To prevent the random blank line and instead use the AS/400 to perform the EBCDIC conversion leaving plain text, use all settings specified in the AS/400 setup instructions except the following.

  • Host Print Transform: *YES
  • Manufacturer type and model: *WSCST
  • Workstation customizing object: QWPDEFAULT
  • Library: QSYS

You will now get the data without specific printer codes embedded in the document.

Is there any way for RPM to print a document correctly with mixed font styles such as bold, italics, or both?

The answer depends on data in the incoming print job.

  1. If you are printing SCS from an iSeries computer, RPM can handle most font styles and changes automatically. The Remote OUTQ may need to be configured differently than normal. Setting the Host Print Transform parameter to *NO will cause RPM to receive raw SCS data. In the Print Data Options for your RPM queue, turn on Convert SCS to ASCII. RPM supports and interprets most, but not all, SCS commands.
  2. RPM understands two other ways to print bold: using backspace (0x08) or a carriage return (0x0C) without a line feed. We suggest opening the data file in a hexadecimal editor looking for these two characters. RPM also supports strikethrough and underlined text using this method as well.
  3. At this time, RPM does not interpret bold printing with any other format. RPM removes the PCL formatting instructions and, since bold printing is performed by a PCL sequence, no font change instructions remain. Future versions of RPM may support bold printing when the incoming data is PCL.

Can ExcelliPrint receive SCS files and create a PDF file from them?

Yes, the PSF can convert SCS to IPDS. To do so, simply place the SCS spool file in the IPDS device. The converted file is then sent to ExcelliPrint and a PDF file is created. Using the same method, ExcelliPrint can also create images files such as JPEG, TIFF, and PNG.

ExcelliPrint can also print SCS files the same way by converting the IPDS data into PCL or Windows EMF.

Issues (208)

Will RPM run in a cluster environment and is it a cluster-aware application?

RPM runs fine in a cluster environment, but it is not cluster aware. Because RPM is licensed per computer, a separate license is required for each redundant server.

I have a software firewall such as Zone Alarm or the Windows Firewall installed on my computer. What ports need to be opened in order to use ExcelliPrint?

At the minimum, you must relax your firewall to allow allow IPDS traffic.  The default IPDS port is 5001 (though this is configurable on the AS/400).

To determine which port numbers your AS/400 is using, use the CHGDEVPRT. Issue the command for each printer pointed to ExcelliPrint. For the OS/390, look at the PRINTDEV macro defined in the PSF Startup Job. The PORTNO parameter is the port number setting. Again, do this for each printer pointed to the computer where ExcelliPrint is installed.

If you wish to administer ExcelliPrint from another computer, you also need to relax the ports configured for HTTP and, if used, HTTPS. To see which ports are used for administration, use the ExcelliPrint control panel utility. Open Control Panel and double-click the ExcelliPrint icon. If you are using Category View on Windows XP, the ExcelliPrint utility is found in Other Control Panel Options under the See Also collapsible window on the left.

I am trying to find the queue names for my Linksys print server. Do you have any documentation on this print server?

We found information on the queue names in the section on setting up UNIX to print to this print server. 

The queue names are

  • L1 for lpt1
  • L2 for lpt2
  • L3 for lpt3

I need to allow only certain people to print to this RPM Remote Print Manager® queue. Does RPM include these security features?

RPM implements 2 types of security. You can restrict access based on hostname or IP address. If you want to restrict access based on hostname, you specify the hostname and whether or not you want them to have access, 'allow' or 'deny'. IP Address security works basically the same way only you enter the IP address instead of the hostname.

To get the host access, choose "Host Access:" from the "Options" menu in RPM.

This is quite an involved process, so we suggest that you obtain more documentation. You can press F1 for the help files or download the manual.

Category: 

How do I set up a remote printer on an HP9000 UNIX system or an HP-UX System V 10.x system?

We strongly recommend that you configure your remote printer using the System Administration Manager (SAM). Configuring printers manually on an HP9000 is difficult to do correctly. To install a printer using SAM, follow these steps:

  1. Log in as superuser/root, and launch SAM.
  2. Open LP Spooler, then Printers and Plotters.
  3. From the pulldown menus, choose Actions.
  4. Choose Add Remote Printer/Plotter from the Actions menu. Do not choose Add Network-Based Printer/Plotter. There are several fields for adding information about the printer:
    • Printer Name -- is the name you give to the printer queue on the HP 9000 running SAM.
    • Remote System Name -- is the name or IP address of the remote PC that is running the RPM Remote Print Manager® software. If you use the PC's name, it must be in the HP 9000's hosts file or configured on the Domain Name Server (DNS).
    • Remote Printer Name -- This name should match the Queue Name already setup in the RPM software.
    • Check the Remote Printer is on a BSD System checkbox.
    • Fill in the optional fields as desired.
  5. Click OK to finish the configuration.
  6. Exit SAM.

Permissions Note: Make sure that you have the correct permissions to print from the UNIX host. Check to see that the username is added to the UNIX host file that lists its users (for example, hosts.equiv or hosts.lpd).

How do I setup the AS/400 for A4 paper size?

If you have not changed the page size of the PRTF, it is still 132 66. The Host Print Transform looks at this value and translates it into the escape sequence requesting that the paper at the printer be 13.2"x 11." Paper. It is not possible with some printers so they are not including in the transform - normally you would default to PPRSRC1 parameter; but, if you are using RMTOUTQ there is no DEVD. It must send something so it requests LETTER rather than A4.

To fix you can change the PRTF so that it has a PAGESIZE that reflects A4 or you can edit the transform. We suggest you look at the Rebook IV if you have it. The basic principle is to RTVWSCST *TRANSFORM *HP4 <specify a PF to retrieve into>. Then use SEU to edit this file and either create another PAGESIZE tag for 13.2" x 11" or change the one for letter.

To change the entry for letter:..

  • PAGSIZE
  • PAGWTH=12240
  • PAGLEN=15840 (these are the size of the page in 1/1440ths of an inch)
  • Data='1B266C303241'X

Change this to

  • Data='1B266C323641'X

What you are doing is sending the escape sequence for A4 rather than letter sized paper. Save this and then CRTWSCST. Add this into the RMTOUTQ under WSCST.

When I change my printer properties in RPM, they aren't used. I've tried to select a different tray, and also a different orientation, but neither seems to work properly. Am I doing something wrong?

If you are using a Text Print action in RPM Remote Print Manager®, these settings should all work just fine, as long as you have the correct driver loaded for the printer.

If you are using a Raw Print action, these settings make no difference. RPM's raw print actions send the data straight through to the printer without changing the file at all, including adding appropriate printer codes. This is the desired behavior and there is no way to make these settings work with this action type. If you need to print directly, you will need to configure your sending (LPR) system to format the data accordingly before RPM ever gets the data.

I already have a queue created in RPM, but when I sent a print job, RPM creates a new queue automatically. Why does this happen and can this behavior be changed?

The LPR/LPD protocol requires that the LPR client must specify the name of the queue when it sends a print job. By default, if this queue does not exist, RPM will create the queue automatically instead of denying the print request.

You can turn off the auto-create queue functionality. If this setting is turned off and RPM receives a request to print a job to a queue that does not exist, RPM rejects the print request instead.

To fix this issue, you can do either of the following.

  1. Modify the configuration on the sending side to use the queue name already created.
  2. Delete the queue you created and use the one which is auto-created by RPM.

When trying to print from INTELLIscribe to Linux, the Linux LPD accepts the entire print job, but does not print it. The job then disappears from the spooler. Unix logs the following errors:

	lp: illegal format character 'o'
	lp: job could not be printed

INTELLIscribe's Properties dialog states that the print job was successful.

INTELLIscribe, by default, specifies to the LPD print server that the data is in "postscript" format. If no Unix PostScript printers are available, or the queue receiving the print jobs is not configured for a PostScript printer, the job will not be printed by Unix.

The default works properly in most cases, however, some Unix LPD servers try to modify the data before printing it when following strict RFC1179 compliance.

You can configure INTELLIscribe to resolve this issue:

  1. From the Printers menu, choose Add or update virtual printer port.
  2. Click "Next" until the final step.
  3. Modify the "Print format" parameter to display "preformatted" by choosing this selection from the drop-down list.

Can INTELLIscribe be used to print from a Windows computer to a Unix computer running IBM AIX?

Yes, INTELLIscribe can print to IBM running AIX. Please check the following settings:

  1. The INTELLIscribe host must be listed in /etc/hosts.lpd file.
  2. A plus sign (+) must also be added to the /etc/hosts.lpd file at the end.
  3. The virtual printer port must be configured correctly:

LPD Queue Name: <same as AIX queue name>

Relax Port Restr: no

Note: The "print format" parameter should be "postscript" if the printer supports it or "preformatted" if not.

How do I set up the LPR/LPD service in OpenVMS to print through RPM?

OpenVMS stores printer configuration in the SYS$SPECIFIC[TCPIP$LPD]:TCPIP$PRINTCAP.DAT. This file is similar in syntax to a UNIX /etc/printcap file. You also need to add the hostname of the computer to the UCX$HOST.DAT file.

First, the LPD services must be enabled using the UCX utility. To do this, follow these steps.

  1. From the system account, start the configuration utility for UCX using the @ucx$config command.
  2. Select Client Components and verify whether or not LPD is enabled. If not, enable it now.
  3. Exit back to the main menu and select Server Components. Once again, if LPD is disabled, enable it now.
  4. Restart UCX by rebooting or restarting it from the main menu.

Next, the RPM host's DNS name must be entered in the UCX$HOST.DAT file. This tells OpenVMS that the RPM host is a valid printer on the network.

  1. Start the UCX utility using the UCX command.
  2. Add the DNS name of the RPM host in the UCX host database using the following command: set host "print1" /address=192.168.1.1 /alias="PRINT1"
    • print1: The DNS name of the RPM host
    • 192.168.1.1: The IP address of the RPM host
    • PRINT1: An alternate DNS name of the RPM host

    Note that VMS is not case sensitive, but UCX is. In UCX, PRINT1 and print1 are different.

Finally, create a printer.

  1. Start the LPR utility using the following command: run SYS$SYSTEM:UCX$LPRSETUP.EXE
  2. When LPRSETUP starts, select Add to add a print queue. The utility will prompt you for the following information.
    • Printer name to add: The name of the print queue in VMS.
    • Printer Type (remote / local): Choose remote for an RPM printer.
    • Printer Synonym: Synonyms are alternate names for the printer. When finished entering synonyms, press return on a blank line to continue.
    • Spool Directory: We suggest accepting the default directory.
    • Remote System Name: The hostname entered in the ucx database
    • Remote Printer Name: The name of the RPM queue.
    • Log File: The location where log files will be stored.
  3. You are next prompted to modify any symbol. Review to determine if any errors were made during LPRSETUP. If not, select q to quit.
  4. When prompted to start the print queue. Select yes.

If the lpd_startup.com file is included with your version of UCX, include it in the sys$manager:ucx$lpd_startup.com file. This allows the print queues to start automatically when restarting the OpenVMS system.

I'm having trouble printing through INTELLIscribe to an Epilog Legend Engraver. Some problems are as folows:

  • The status window shows "submitted" or "started", but the job never prints
  • A message stating "List index out of bounds(0)" is received
  • The job prints but says "Failed" in the status window
  • A job prints over and over again 

These steps should resolve most issues when spooling print jobs to Epilog Legend Engravers:

  1. Upgrade to the latest version of INTELLIscribe. This can be downloaded here.
  2. In the virtual printer port wizard, configure the "Relax port restr" parameter to "no".
  3. In the virtual printer port wizard, configure the "Data File Ack" parameter to "no".
  4. In the virtual printer port wizard, configure the "LPD queue name" parameter to "Legend".

If the problems are still not solved, verify that your TCP/IP network configuration is correct. If you already have a network at your location, contact your system administrator for help on configuring your engraver and PC correctly.

If you are in an environment with only a single PC and an engraver, verify the following:

Your engraver and PC must have a different IP address

The default IP address for Epilog Engravers is 192.168.98.1 and the subnet mask is 255.255.255.0. You must configure the computer's IP address to be similar (on the same network of 192.168.98), but not identical. We suggest setting it to 192.168.98.2 and subnet mask the same 255.255.255.0. Once this is accomplished and the computer is restarted, try pinging the engraver with the command

	ping 192.168.98.1

If you receive 4 replies to your ping, then your configuration is correct.

If you are connecting through a network hub

Verify that your network cables are "straight through" cables. Straight through cables should be used in this instance because cross-over is accomplished by the hub.

If you are connecting directly to the Engraver from the PC

Verify that your network cable is a "cross-over" cable. Cross over cables are used in this instance to provide the network proper "listening" and "talking" wires.

The AS/400 application asks for a device to print to rather than a remote OUTQ.

Some applications on the AS/400 require a printer device to send the spool file to instead of a queue. To accomplish this IBM recommends the followings steps:

  1. At the AS/400 command prompt, issue the command CRTDEVPRT, then press F4.
  2. In the Description parameter, name the device.
  3. In the Class parameter use *VRT.
  4. If you have a laser printer, use *IBM3812 for the "Manufacturer" parameter and 1 for the "Model" parameter; for dot matrix printers use either *IBM4214 Model 2 or *IBM5219 model D1.
  5. In the Font Identification parameter use 11 for all printers.
  6. Use the defaults on the rest of the keywords.

Now, modify the OUTQ, which was automatically created by CRTDEVPRT. It should be the same name as the device.

  1. End the writer. Issue the command 'ENDWTR name *IMMED', without the quotes. Wait 15 seconds for the writer to end.
  2. At the AS/400 command prompt, issue the command CHGOUTQ "device_name". "device_name" should be the Description parameter you entered in step 2 above.
  3. Input the appropriate parameters for the remote OUTQ. The following table lists the important parameters.
  • Writers to autostart: 1
  • Connection type: *IP
  • Destination type: *OTHER
  • Transform SCS to ASCII: *YES
  • Destination options: 'XAIX XAUTOQ'
  • Operator controlled: *YES
  • Data queue: *NONE
  • Authority to check: *DTAAUT

Your AS/400 application can send print files to the device, and RPM Remote Print Manager® should get them shortly after that.

Note: Create the device before the OUTQ, because the AS/400 will automatically create an OUTQ with the appropriate links from the device to the OUTQ.

My AIX system queue is disabled after a while and I have to restart it again.  Is there any way to keep the AIX queue from being disabled automatically?

When the "Receive a <Printer> Job" command is sent by rembak to a remote server, a positive acknowledgment should be received by rembak before proceeding with sending datafiles. If rembak does not receive a positive acknowledgement within its timeout period, the print request will fail and the queue will be taken down. Datafiles will not be sent across to the lpd server.

With AIX 4.2 and later, set the backend <timeout> period to 120.  To do this, add a printer with the following parameters.

Description

Lexmark Printer (Room 330)

* Name of new PRINT QUEUE to add [aix_queue]
* HOSTNAME of Remote Server 192.168.1.1
* Name of QUEUE on remote server [rpm_queue]
TYPE of print spooler on remote server BSD
Send PASS-THROUGH FLAG to queue
on remote server?
yes
Backend TIME OUT period (minutes) [120]
 Send control file first?  no

For prior versions of AIX edit the /etc/qconfig file as follows:

  Parts:device = @TES_Server1
          up = TRUE
          host = TES_Server1
          s_statfilter = /usr/lib/lpd/bsdshort
          l_statfilter = /usr/lib/lpd/bsdlong
          rq = Parts@TES_Server1:
          backend = /usr/lib/lpd/rembak -T120

We have RPM running on a dedicated print server machine. We have more than 50 queues. If this machine were to have any problems, these queues would be lost. Is there any way to backup this information just in case our computer crashes?

Go to the "File" menu in the GUI, select "Export" and enter a file name. The RPM GUI will back up the current configuration of queues, actions, transforms, jobs and settings into an XML file. You can later "Import" this from the "File" menu.

This is a good thing to do for backup purposes and for copying the information to a different computer as well.

Category: 

How do I verify that my workstation object is properly imported and registered in the Novell NDS tree?

Right click the Novell Desktop Management icon in the system try and select "Display NDS Information". Now, verify the "Workstation Object" is correct. If you see "N/A", the workstation object is not logged into the NDS and a problem exists.

How do I setup a queue in AIX version 4.x to print to RPM Remote Print Manager®?

Setting up queues in version 4.x is slightly different than 3.x. Follow these steps:

  1. smit
  2. Print spooling
  3. Add a print queue with the following options:

    Attachment type: REMOTE

    Type of remote printing STANDARD PROCESSING

    Name of queue <PICK_A_NAME>

    Hostname of remote server <REMOTE_SYSTEM_NAME>

    Name of queue on remote server <RPM_QUEUE_NAME>

    Type of print spooler on remote server BSD

  4. Enter to accept, exit from smit and test.

How do I set up my AIX version 3.x queue to print to RPM Remote Print Manager® (RPM)?

  • On the Unix Host, add a line to the /etc/hosts file at the end that lists the IP address of the PC where RPM is installed, then a tab, then a hostname to be referenced, such as:
    192.168.1.100      rprinter
  • Now ensure the LPD subsystem is activated:
    1. smit
    2. Spooler
    3. Manage Remote Printer Subsystem
    4. Server Services
    5. lpd Remote Printer Subsystem
    6. Start Using the lpd Subsystem
    7. Start BOTH now and at System Restart
  • Now configure the Remote Printer Queue:
    1. smit
    2. Spooler
    3. Manage Remote Printer Subsystem
    4. Client Services
    5. Remote Printer Queues
    6. Add a Remote Queue
  • Fill in the fields as follows:
    *NAME of queue to add <AIX printer name>
    ACTIVATE the queue? yes
    Will this become the DEFAULT queue? no
    Queuing DISCIPLINE first come first serve
    ACCOUNTING FILE pathname [  ]
    DESTINATION HOST for remote jobs <RPM hostname> or <IP Address>
    *Pathname of the SHORT FORM FILTER
    for queue status output
    [/usr/lpd/bsdshort]
    *Pathname of the LONG FORM FILTER
    for queue status output
    [/usr/lpd/bsdlong]
    *Name of QUEUE on remote printer <RPM_Queue>
    *NAME of device to add <eg. HP5>
    *BACKEND PROGRAM pathname [/usr/lpd/rembak]

Note: Replace bold items with information specific to your situation. If you are unclear on any of these items, contact your system administrator.

Note: The instructions to setup AIX version 4.x are slightly different. Click here for the 4.x setup instructions.

How do I configure my SGI IRIX lpr to print through RPM Remote Print Manager®?

To print through RPM from SGI IRIX, the following instructions will help you configure the remote printer definition.

The daemon /usr/etc/lpd should already be running by default if the proper software has been installed. This software is installed from the eoe2.sw.bsdlpr subsystem on 3.3.1 or later versions of IRIX.

  1. Edit the /etc/printcap file and add your printer information. If you need help here, see the man pages for printcap. If you want to make a printer the default printer for the lpr command, add lp to the list of printer name aliases. A typical printer entry looks like:

    hp4|rpmqueue|lp:\
    :sd=/usr/spool/print/hp4:\
    :rm=rpm.brooksnet.com:\
    :rp=rpmqueuename:\
    :lf=/var/adm/lpd-errs:

  2. Create the general spool directory and set the correct ownership and permissions. This step should only be done if this is the first printer created. You cannot perform this step more than a single time.

    cd /usr/spool
    mkdir print
    chown lp print
    chgrp lp print
    chmod 755 print

  3. Create the spool directory for the new printer and set the correct ownership and permissions. The name of the directory is specified in the /etc/printcap entry on the sd= line.

    cd /usr/spool/print
    mkdir hp4
    chown lp hp4
    chgrp lp hp4
    chmod 755 hp4

  4. At this point, the system should be restarted or you may restart the /usr/etc/lpd to allow the changes to take effect.

Note: To print, enter the following command at the shell prompt:

lpr -Php4 path/to/file

What steps should I perform on my firewall to enable RPM to receive print jobs from a system that is outside the firewall, perhaps from the Internet or WAN connection?

To answer this question you will need to know how your firewall is configured, and which protocol you will be using to print.

Firewall: NAT

If your firewall is performing Network Address Translation (NAT), you will configure port forwarding on your firewall.

  • If you are using the LPR/LPD protocol, and your firewall is performing NAT, you will forward traffic coming in on port 515 to the internal IP address of the RPM host.
  • If you are using streams and your firewall is performing NAT you will forward traffic on whichever port you configured on the sending side (e.g. 9100) to the internal IP address of the RPM host.

Firewall: not NAT

If your firewall is not performing NAT, you will simply allow data to go through your firewall. This is called relaxing a port.

  • If you are using the LPR/LPD protocol, you will relax port 515 on your firewall.
  • If you are using streams printing, you will relax the appropriate port number. The port number you relax will depend on how your printer is configured on the sending side; typically, it will be in the range of 9100-9200, but could be any port number between 1 and 65535.

Note: Streams printing may be referred to as any of the following: Socket Printing, Reverse Telnet, or Telnet Printing.

Note: Your firewall may require you to supply the type of connection; both LPR/LPD and streams printing are TCP connections, not UDP.

How do I set an RPM Remote Print Manager® queue to print to a specific Windows Printer?

For RPM 5.0 and later:

  1. Open the Queue Setup panel
  2. Select the queue in the queue list
  3. Select the action with the printer you want to change (Text print and Raw print actions work the same way in this regard)
  4. Click the Modify button to the right of the actions list
  5. Select a new printer. For Text print actions you can select printer settings in this dialog.
  6. Click Save when done.

For RPM 4.5 and prior:

  1. From the "Queues" menu, choose "Edit Queues".
  2. From the "Queue" drop-down list, choose the queue you want to select a printer for.
  3. Now, if the queue type is Text print, press the "Printer Setup" button.
  4. In the "Printer Setup" dialog, choose the printer you want this queue to print to from the "Printers" drop-down list.

Note: From this same dialog, you may also identify the page orientation and paper size by pressing the "Properties" button.

How do I grant the Logon as a batch job privilege to my user account?

Setting up 'Logon as Batch Job'

Answer: On Windows, this privilege is granted through the Local or Domain Security Policy. To do this using the Local Security Policy, follow these steps.

  1. In the Control Panel, open Administrative Tools, then Local Security Policy.
  2. Beneath Security Settings, open Local Policies and highlight User Rights Assignment.
  3. Locate Log on as a batch job. Open the properties and add any users that need this right.
  4. When finished, save your changes and close the Local Security Settings window.

Your changes should take effect immediately. To make changes to the Domain Security Policy, on a domain controller, use the Domain Security Policy utility in the Control Panel.

Why RPM Remote Print Manager needs 'Logon as Batch Job'

RPM Remote Print Manager uses Logon as Batch Job

Our RPM product has the ability to process print jobs as a specific Windows user. As you well know, sometimes the permissions make this necessary; for instance, if you want to

  • write to a shared folder
  • print a shared printer
  • run a program interactively.

This is the reason we researched this topic in the first place, and we are pleased to make this page available to you. Obviously, helping our users is what makes us all successful, and we're happy to share the information with the community.

If you need a great print server or virtual printer, please download the free trial today! And best of luck with your "logon as batch" issues from here on out.

I am trying to print to a Fiery XJ network printer from INTELLIscribe. The problem is, I don't know what the queue name is for this printer.

There seem to be as many queue names for these printers as there are printers. Sometimes the queue names resemble the printer model. For instance, for the Fiery XJ 5790 model the queue name in lowercase letters (uppercase letter will not work) is "print_5790". If you have a different model, try print_ and the model number of your printer.

Consult your documentation if this does not work.

Writer abnormally ended (abended).

Your AS/400 is not configured correctly.

Please refer to the AS/400 Setup instructions. The most common settings to check are:

  • REMOTE SYS name and/or the RPM host system's IP address is correct in the remote outq definition or HOST TABLE
  • Verify that the AUTCHK is set to *DTAAUT

Printer Device needed, AS/400. Application requires print job to be sent to a printer rather than a queue.

Some applications on the AS/400 require a printer device to send the spool file to instead of a queue. To accomplish this IBM recommends the followings steps and parameters for the remote outq keywords. When a printer device is created an outq is also created with the same name as the device.

  1. Use the CRTDEVPRT command and prompt the command.
  2. In the Description parameter give the device the same name as the remote outq.
  3. In the Class parameter use *VRT
  4. In the Type parameter use *IBM3812 if this is a laser printer.
  5. In the Model parameter use 1 if this is a laser printer.
  6. In the Font Identification parameter use 011 on all printers.
  7. Use the defaults on the rest of the keywords.
  8. Set the Destination options to XAIX and XAUTOQ in the outq and change the other keywords to represent a remote outq.

If you are using a dot matrix printer the Type parameter can be *IBM4214 with a Model 2 or *IBM5219 with a model D1.

In RPM Remote Print Manager®, I get an "Error: Failed subcommand 4" when printing from my AS/400. What can I do to fix it?

This error is caused by an incorrect setting in the OUTQ on the AS/400. To fix it, follow these steps:

  1. First you must end the writer. From a command prompt on the AS/400, issue the command (without quotes) 'ENDWTR writer_name *IMMED'.
  2. Now from the command prompt, issue the command 'CHGOUTQ queue_name'. Press the F4 key
  3. Now you must get to the "All Parameters". Press F24 (shift-F12) then F9.
  4. Press "Page Down" until you get to the parameter "Destination Type".
  5. Change this to *OTHER.
  6. Finally, save the changes and start the writer again.

How do I determine the characters-per-inch and lines-per-inch settings to use in a "Text" type queue?

Characters-per-inch may be calculated using the following formula(s):

  • CPI = Number of Characters in a line to be printed / Printable Width, or
  • CPI = Characters / Paper Width - (left margin + right margin)

Lines-per-inch may be calculated using the following formula(s):

  • LPI = Number of Lines to be printed on a page / Printable Width, or
  • LPI = Lines per page / Paper height - (top margin + bottom margin)

Examples:

  1. I am printing on letter size paper, landscape. I want 60 lines on each page, and there are 132 characters on each line. I've set the margins to 1/2 inch on all: top, bottom, left, and right.
    • CPI = 132 / (11 - (0.5 + 0.5)) = 13.20
    • LPI = 60 / (8.5 - (0.5 + 0.5)) = 8
  2. Printing again on letter size paper, portrait this time. I want 80 lines on each page, and there are 92 characters on each line. I've set the margins to .75 inches on top and bottom margins, 0.5 inches on the left and right margins.
    • CPI = 92 / (8.5 - (0.5 + 0.5)) = 12.2
    • LPI = 80 / (11 - (0.75 + 0.75)) = 7.6

How do I create a PSFCFG to use with ExcelliPrint?

Your AS/400 operating system and release version may vary. For more detailed information on different OS/400 versions, please review appendix II in the manual.

Once created, you must change your device description to reference the PSFCFG. See the steps below for instructions.

Creating the PSFCFG for V4R5 and Later

  1. From an AS/400 command prompt, enter CRTPSFCFG and press F4.
  2. Press F24, then F9 to view all parameters.
  3. The following table shows the configuration needed for use with ExcelliPrint.
  PSF configuration . . . . . . . . . . . : EXCELLPSF
  Library . . . . . . . . . . . . . . . . : QUSRSYS
  User resource library . . . . . . . . . : *JOBLIBL
  IPDS pass through . . . . . . . . . . . : *YES
  Activate release timer. . . . . . . . . : *NORDYF
  Release timer . . . . . . . . . . . . . : *SEC15
  Restart timer . . . . . . . . . . . . . : *IMMED
  SNA retry count . . . . . . . . . . . . : 2
  Delay time between retries. . . . . . . : 0
  Blank page. . . . . . . . . . . . . . . : *YES
  Page size control . . . . . . . . . . . : *YES
  Resident fonts. . . . . . . . . . . . . : *YES
  Resource retention. . . . . . . . . . . : *YES
  Edge orient . . . . . . . . . . . . . . : *NO
  Remote location . . . . . . . . . . . . :
  Name or address . . . . . . . . . . . . : *NONE
  TCP/IP port . . . . . . . . . . . . . . : *NONE
  TCP/IP activation timer . . . . . . . . : 170
  PSF defined options . . . . . . . . . . : *NONE
  Text description. . . . . . . . . . . . : EXCELLIPRINT [ADDRESS]:[PORT]
  Device resource library list. . . . . . : *DFT

Changing the Device Description

  1. Make sure the writer is ended by issuing the following command: ENDWTR writer *IMMED.
  2. Now, vary off the device: VRYCFG device *PRT *OFF.
  3. Issue the Change Device Description command, CHGDEVD device, and press F4. Press F9 to view all parameters.
  4. Locate the User Defined Object parameter and enter the name of your PSFCFG (i.e. EXCELLPSF) which you created above, the Library where the PSFCFG is located, and the object type is *PSFCFG.
  5. Vary on the device and start the print writer (STRPRTWTR).

I have a host system running that does not support the LPR/LPD protocol, however, it does support the Telnet protocol for printing. Can I configure RPM to receive jobs using the Telnet protocol?

RPM Remote Print Manager® provides the ability to receive print jobs via a direct socket connection on any port. This is also known as stream printing or reverse telnet. Ports used for this purpose typically start at 9100 similar to the Jetdirect protocol. Follow the steps below to configure RPM for direct socket printing.

In the RPM GUI:

  1. Go to the View menu and select General Settings.
  2. Click the Ports icon.
  3. Click Add Port.
  4. Select "Telnet" from the list, and enter a port number.
  5. Select a queue to send telnet jobs to. The defaults for the other settings are usually good enough.
  6. Click the Save button.

My RPM Remote Print Manager® will not receive jobs from the Tandem operating system on the mainframe. Can I configure RPM to receive jobs from a Tandem OS?

We have researched the Tandem operating system and found that the old OS versions do not support the LPR/LPD protocol natively.

There are 3rd-party LPR spoolers available, and RPM can receive jobs fine using their "raw" printing. Configure the Tandem systems as follows:

Create a file in $SYSTEM.SYSTEM called FASTCNFG with the following information.

  !****** CONFIGURE TCP/IP DIRECT FOR RPM Software ******
  Device $LPRT1
  CONTYPE	=TCP/IP
  ADDRESS	=192.168.1.50 (RPM host IP Address)
  PROTOCOL	=NONE
  PORT	=9100 (Telnet port setup in RPM)

Now, configure RPM to receive jobs using the Telnet protocol on port 9100. Note that this port number can be any TCP/IP port number you choose. Some port numbers are reserved for other protocol such as 21 for FTP and 23 for regular Telnet.

  1. In the RPM UI, select "Options/Protocols:".
  2. In the Protocol type drop-down list, select "Telnet".
  3. In the TCP/IP port, type "9100", and click Add. Make sure that you do not add telnet using port 515 or this will cause a problem with RPM.
  4. Choose the queue that will receive jobs from the Tandem.
  5. Click OK, then OK again on the Server Protocols dialog.
  6. Choose Yes to restart server protocols.

We have learned that new OS versions support the LPR/LPD protocol natively. To do this:

  1. Create a device name in Tandem using "SPOOLCOM".
  2. In your "FASTCNFG" file, create an entry similar to the above entry, using "LPD1179" in "PROTOCOL" in place of "NONE".
  3. Do not enter "PORT", or configure it to port 515, since this is the proper LPR/LPD port number.

Is it possible to allow RPM to print to more than this number of printers?

RPM Select 4.5 and prior is limited to 24 printers; RPM Select 5.0 is limited to 10 devices. If you have RPM Select and wish to print to additional printers, please contact us about converting your license to RPM Elite. RPM Elite has 3 options for device limits: 99, 249, and Unlimited Devices

Here are the steps to increase the RPM Elite printer limit above 99.

  1. Open the Brooks License Manager in the RPM Program group or choose License from the software's Help menu.
  2. Open the Module Status tab and double-click RPM Printers. Follow the wizard selecting Internet activation option.
  3. Enter your invoice or sales receipt number, the auth code you were provided, and the number of printers you purchased and click Next.
  4. A success dialog will appear if your activation was successful.

Note: If you purchase an unlimited printer license for RPM Elite, enter 0 (zero) for quantity. Zero means "no limit".

When sending a job from the AS/400, that job immediately goes into a ready (*RDY) status. The job is never sent to RPM and no messages are logged in RPM related to this print job. In the AS/400, the *RDY status never changes to *SND.

This is a result of the AS/400 remote writer not running. To start the remote writer, issue the command STRRMTWTR outq_name. The remote writer can also be configured to start automatically after making any changes to the OUTQ configuration using the Change Output Queue (CHGOUTQ) command. To do so, follow these instructions.

  1. From an AS/400 command prompt, issue this command, substituting your OUTQ name where appropriate: ENDWTR outq name *IMMED.
  2. Wait 15 seconds, then issue this command, again substituting your OUTQ name where appropriate: CHGOUTQ outq name. Press F4 to prompt. If you press Enter, start again from step 1.
  3. Press F9 to view all parameters, then locate the Writers to autostart parameter. Set this value to 1.
  4. Press Enter to accept the changes. In the future, any changes to the OUTQ will also restart the remote writer; there is no need to issue the STRRMTWTR command.

When sending a print job from the AS/400, it goes into a holding (*HLD) status, and does not print. There are no messages logged to the RPM log whent his happens.

This is caused when a connection cannot be made from the AS/400 to the RPM host. To resolve the issue, verify the settings in the OUTQ match the recommended settings on our AS/400 setup instructions. To begin modifying the OUTQ, follow these instructions.

  1. From an AS/400 command prompt, issue this command, substituting your OUTQ name where appropriate: ENDWTR outq name *IMMED.
  2. Wait 15 seconds, then issue this command, again substituting your OUTQ name where appropriate: CHGOUTQ outq name. Press F4 to prompt, rather than the Enter key. If you press the Enter key, start again from the beginning.
  3. Press F9 to view all parameters, then compare your settings with our AS/400 setup instructions.

Verify the RPM host's IP address or DNS hostname are configured properly, and that there are no firewalls between the AS/400 and RPM that may be blocking the connection, including the Windows XP Service Pack 2 firewall. If the Windows Firewall is the cause, we show you how to add a firewall exception.

When attempting to print from the AS/400, the spool file immediately goes into a sending (*SND) status but does not print.
No messages are logged in the RPM Remote Print Manager® (RPM) log when this happens.

There are a number of settings on the remote AS/400 OUTQ that can result in this issue. To resolve, verify the OUTQ settings match the recommended settings on our AS/400 setup instructions. To begin modifying the OUTQ, follow these instructions.

  1. From an AS/400 command prompt, issue this command, substituting your OUTQ name where appropriate: ENDWTR outq_name *IMMED. Press Enter.
  2. Wait 15 seconds, then issue this command, again substituting your OUTQ name where appropriate: CHGOUTQ outq_name. Press F4 to prompt. If you press the Enter key, start again from step 1.
  3. Press F9 to view all parameters, then compare your settings with our AS/400 setup instructions.

Also, verify the RPM host's IP address or DNS hostname are configured properly, and that there are no firewalls between the AS/400 and RPM that can be blocking the connection, including the Windows Firewall. If the Windows Firewall is the cause, click here for assistance.

After the OS/400 version has been upgraded, all spool files go to a SND state, but will not print. What did the upgrade do to stop printing?

After an OS/400 operating system upgrade, check the AS/400 host table and TCP/IP configuration. Restore or replace any missing entries in the host table.

Also, verify that the writer is started for each OUTQ. To do so, from the AS/400 command prompt, issue the following command: WRKOUTQ outq name. If the status of each Output Queue is RLS/WTR, then a Writer is running and this is not the cause of the issue.

There are a number of settings in the AS/400 OUTQ configuration that can result in this symptom. To resolve the issue, verify the settings in the OUTQ match the recommended settings on our AS/400 setup instructions. To begin modifying the OUTQ, follow these instructions.

  1. From an AS/400 command prompt, issue this command, substituting your OUTQ name where appropriate: ENDWTR outq name *IMMED.
  2. Wait 15 seconds, then issue this command, again substituting your OUTQ name where appropriate: CHGOUTQ outq name. Press F4 to prompt, rather than the Enter key. If you press the Enter key, start again from the beginning.
  3. Press F9 to view all parameters, then compare your settings with our AS/400 setup instructions.

I was not able to disable the option "use extended remote printing protocol" option in the SCO configuration. Now when I print, I receive warning messages in the log stating "unrecognized control line".

You can now modify the /etc/printcap file manually. Open this file in an editor such as 'vi' or 'edit'.

Locate the printer entry for this printer, it should look something like this:

  hp4:\
    :lp=:rm=192.168.1.53:ex:rp=hp4:sd=/usr/spool/lpd/hp4:

Remove 'ex:' from the line. It should now read similar to this:

  hp4:\
    :lp=:rm=192.168.1.53:rp=hp4:sd=/usr/spool/lpd/hp4:

Be sure to leave a colon (:) separator between each entry. Now you can save the file and try printing again. This disables the extended options that are not included in the original RFC 1179 specifications.

Will RPM Remote Print Manager® receive jobs from an HP3000 running the MPE/iX operating system (OS)?

The MPE/iX OS does not natively support the LPR/LPD protocol. If you have a 3rd party LPR client for MPE/iX, we recommend you use it; however, we do not provide instructions for configuring 3rd-party clients.

Before getting started, note that TCP/IP printing on the HP3000 is supported on MPE release 5.5 or greater. The first step is to add the printer LDEV. You can add it using SYSGEN, which requires a system reboot, or it can be added dynamically with the IOCONFIG utility.

Creating the LDEV for RPM is exactly the same as any other JetDirect printer.

  1. Log on as Manager.SYS and run IOCONFIG.PUB.SYS.
  2. At the IOCONFIG prompt, type: AD LDEV=nnn PATH=NONE ID=HPTCPJD. Substitute nnn with a unique number.
  3. Exit IOCONFIG by typing EXIT.

Next, an entry in the NPCONFIG file must be created or added. The following configuration should be added to the "NPCONFIG.PUB.SYS" file. If this file does not exist, it must be created.

nnn (network_address = x.x.x.x
  tcp_port_number = 9100
  jam_recovery = false
  pjl_supported = false
  snmp_enabled = false
  setup_file = null.hpenv.sys
)

Replace nnn with the same number as the LDEV. The "network_address" should reflect the IP address of the PC where RPM is installed.

Note: null.hpenv.sys may not exist.  If not, create it first.  The setup_file should be an empty file.

Note: The "tcp_port_number" setting can be any number you choose. You must configure RPM to receive jobs on this port. Also, you must make sure that you are not using a reserved number such as 23 for telnet. Usually, if you use ports in the 9100 range, it will work.

To configure RPM to receive jobs on different ports:

  1. In RPM, choose "Port Settings" from the "Configure" menu.
  2. Choose "Telnet" from the "Select Port Type to Add" list and click Add Port.
  3. Enter 9100 in the Port list, or the number you configured in the "npconfig.pub.sys" file on the HP3000.
  4. From the "Queue" list, choose which RPM queue will receive jobs sent on this port number. We recommend accepting all other default values initially.  Press OK.
  5. The changes should take effect once you press OK on the "Port Settings" dialog.

RPM should now be configured properly for receiving jobs from the MPE/iX OS running on the HP3000 box.

I have configured a new OUTQ on my AS/400 to print data through RPM.  For some reason, print jobs go into a SND or HLD state and do not print. No new messages appear in the RPM log file.

To make a TCP/IP connection to RPM, the TELNET command may be used.  To verify a connection, perform the following telnet test.

  1. At the AS/400 command prompt, type TELNET and press F4
  2. In the Start TCP/IP TELNET (TELNET) screen, press F9 to view "all parameters."
  3. In the Remote System field, type *INTNETADR.  Enter the IP address of the RPM host in the Internet Address field.
  4. Locate the Port parameter and enter 515, then press Enter.

If RPM is configured to relax the 'port in range' requirement, this will input-inhibit the session if a connection is made. Close RPM (Windows 9x) or restart the RPM service (RPM Elite/Select) to release the AS/400 session. Then restart RPM and check the RPM log for new message.

If RPM is not configured this way, a new message should be displayed in the RPM log stating:
Client port xxxx out of range

Although this message is a warning, it verifies that a connection was made to RPM at port 515.

How do I setup an MVS mainframe to print to RPM Remote Print Manager®?

There are several potential sources of print data on an MVS mainframe, and several possible methods for LPRing that data to an LPD server. Perhaps the simplest case is where the LPR command is used to print a copy of a disk file. This can be done interactively (under TSO) or in a batch job. The LPR command is a part of IBM's TCP/IP for MVS product, and it works very much like the LPR command you would find on a workstation.

On most MVS systems, though, the majority of print data will be generated by three other sources:

Batch jobs (sometimes very long reports) On-line systems running under CICS. Batch jobs normally produce printouts that go into the JES spool for printing. Output from CICS applications is designed to be sent directly to a 3270-family printer device.

There are a couple of options for intercepting both of these types of print data and sending them to a print server. One method is to use IBM's Network Print Facility, a product that comes as an optional feature of TCP/IP for MVS version 3.1. NPF includes software that can take printouts from the JES spool and LPR them off to a print server. It also has software that "pretends" to be a 3270-style printer and intercepts printouts coming from CICS; these printouts are then sent via LPR to a print server.

The other option for printing JES and CICS data at an LPD server is a combination of products from Levi, Ray and Shoup. A product called VPS/TCPIP will take printouts from the JES spool and use LPR to send them to a server. Another product called DRS emulates 3270-style printers so that it can intercept CICS printouts and then send them to an LPD server. Both IBM's NPF and Levi, Ray and Shoup's products require that the MVS system administrators define CICS printers and JES destinations to the software, and associate LPD hostnames/IP addresses with each "virtual" printer.

There is now a third, and probably best way to send jobs to RPM from an MVS system. IBM now packages IP Printway with the IBM/MVS operating system. We do not know much about it other than it works. Configuration is a little difficult, but can definately be done.

MVS/JES provided by Bill Kelly, Auburn University

How do I set up a remote printer on an HP9000 UNIX system or an HP-UX System V 10.x system?

We strongly recommend that you configure your remote printer using the System Administration Manager (SAM). Configuring printers manually on an HP9000 is difficult to do correctly. To install a printer using SAM, follow these steps:

  1. Log in as superuser/root, and launch SAM.
  2. Open LP Spooler, then Printers and Plotters.
  3. From the pulldown menus, choose Actions.
  4. Choose Add Remote Printer/Plotter from the Actions menu. Do not choose Add Network-Based Printer/Plotter. There are several fields for adding information about the printer:
    • Printer Name -- is the name you give to the printer queue on the HP 9000 running SAM.
    • Remote System Name -- is the name or IP address of the remote PC that is running the RPM Remote Print Manager® software. If you use the PC's name, it must be in the HP 9000's hosts file or configured on the Domain Name Server (DNS).
    • Remote Printer Name -- This name should match the Queue Name already setup in the RPM software.
    • Check the Remote Printer is on a BSD System checkbox.
    • Fill in the optional fields as desired.
  5. Click OK to finish the configuration.
  6. Exit SAM.

Permissions Note: Make sure that you have the correct permissions to print from the UNIX host. Check to see that the username is added to the UNIX host file that lists its users (for example, hosts.equiv or hosts.lpd).

RPM Remote Print Manager® (RPM) "Queue Status" shows Xfer next to the file name and the job never shows completely received (Done).

The above status indicates that RPM is receiving. Therefore, this is not an RPM problem. The problem is on the "Sending or LPR" side. Should you experience this issue, we suggest that you contact your network administrator (feel free to e-mail support). There are a variety of setup problems that can cause this symptom as shown below by the following *real* examples:

  1. Firewall issues - The control file could be sent just fine and a firewall could stop the data from sending. The resolution to this issue is to review the firewall log to see if the firewall is blocking the data transfer.
  2. Network issue - When many routers are on a network providing many paths to all of the networks. One of the routers could be performing nat translations of the address of the lpd server to allow for a second path to the machine if the primary was down. The problem develops when the nat translation is only being performed on the path to the server and not from the server. So the initial connection will be made and when the server sends back the ack packet, it will be sent from a different ip address which would cause the sender to fail to reply (expecting a reply from the address it was sent to). The resolution to this issue was to verify that the nat ip address to LPD server is same as ack ip from LPD server.
  3. Sending Host Setup issue - An incorrect print queue configuration on the Sending Host may also cause this to occur. To resolve this situation, verify the correct print queue setup.

RPM Remote Print Manager® is receiving; however, nothing was printed. There are not any errors in the RPM Log and the log reads as follows:

    Information: Accepted client from x.x.x.x, port 148
    Information: Remote closed 148
    Information: Close on socket 148
    Information: Closing transaction for 148  

This issue is caused by a router or routers not being configured properly. Network Address Translation (NAT) is probably the cause. If you have more than one router, verify that either:

  1. All routers are configured to perform NAT translations, or
  2. No routers are configured for NAT translations

Also, a single router can be configured to perform the translation on outgoing data and not to perform the tranlation on incoming data. Verify that the router will do the translation on both incoming and outgoing data.

Suppose that the router was configured for NAT translation to the RPM host server, but data coming from the server did not get translated. The translation would occur before RPM received the data, then RPM would send an acknowledgement back. Since the translation is not performed on data coming from the RPM host server, the LPR client would never recieve this acknowledgment. Therefore, the LPR (in most cases) will close the connection and try again, over and over. Eventually it will give up.

Note: Verify that the NAT IP address to the RPM server is the same as the acknowledgment IP address from the RPM server.

Category: 

When trying to print from INTELLIscribe to Linux, the Linux LPD rejects the request and logs an error stating:

	/usr/sbin/lpd: Malformed from address  

The message also appears in the Properties dialog in INTELLIscribe.

The new version of INTELLIscribe sends data on source ports greater than 1024. This is to circumvent a problem with Windows and port timeout periods. Some flavors of Unix and Linux, by default, will only accept data on source ports less than 1024. This is due to a security hole present in systems providing both FTP and LPR/LPD functionality.

INTELLIscribe may be modified to send data on ports less than 1024 in the virtual printer port wizard.

  1. From the Printers menu, choose Add or update virtual printer port.
  2. Click "Next" until the final step.
  3. Modify the "Relax port restr" parameter to display "no" by choosing this from the drop-down list.

When pressing the "Printer Setup" button to select a printer on a newly created queue, an hourglass cursor appears for a second then goes away. The Print Setup dialog never appears.

The reason that new queues cannot access the Print Setup dialog is that the operating system is blocking it due to a connection problem with the default printer.

Try changing the default printer to be a local printer. This is done from the Windows Printers folder.

  1. Open Start->Settings->Printers.
  2. Right-click on a printer and choose "Set as default".
  3. Now try accessing the Print Setup dialog from RPM.

If the Print Setup dialog still does not appear, repeat the above process until it does. This problem is caused by the operating system and not by RPM. Typically, your default printer should be a "local" printer, meaning one connected to LPTx or COMx ports, or other ports such as the LPR port, JetDirect port, etc. A shared printer, such as \\Server\Printer, can cause problems with other applications as well as RPM.

Do you have a list of LPD queue names that we can browse to find out our configuration for INTELLIscribe?

Here is a list of LPD queue names which we have collected. If you have documentation for your queue names, please look there before trying these queue names. Some of the queue names in this list may not work because they are specific to the type of LPD server installed in the printer.

Manufacturer Model Queue Name
Apple LaserWriter 16/600 raw
text
LaserWriter Pro 810 TEXT
PASSTHRU
LaserWriter 12/640PS raw
text
LaserWriter 8500 RAW
Axis 560 / 570 / 660 / 670 Externals PRn
Barr Systems Print Servers BARRTCP1
Canon 460 PS (no hard drive) xjprint
xjdirect
460 PS (with hard drive) xjprint
xjhold
GP Series Copier/Printer print
ImageRunner Printers (Fiery LAN adapter) print
Castelle LANpress L1
L2
LANpress 3 P1
P2
P3
D-Link DP-300
DP-301
LPT1_TEXT
LPT1
Decision Data Print Server d1prn
Digi Portserver Does not support LPD
Portserver II raw_n
Digital Products, Inc. NETPrint Print Server PORTn
EFI Canon CLC 300 / 320 / 350 Ext. PRn
Canon CLC 500 / 550 print_500-550
Canon CLC 700 / 800 print_700-800
Canon CLC 1000 print_1000
HP DeskJet 750C print_DJ750C
Kodak ColorEdge 1525 / 1525+ print_1525/25+
Kodak ColorEdge 1550 / 1550+ print_1550/50+
Kodak ColorEdge 1560 / 65 print_1560/65
Lanier 5506 DC print_r
Minolta CF80 print_CF80
Minolta CF900 print_Copier-M
NovaJet Pro print_NJPro
Oce 3107C / 3108C print_3107C/8C
Ricoh NC 5206 print_r
Ricoh 5206 print_r2
Ricoh 5006 print_r
Sharp AR-C860 print_r
Fiery XJ 5760 / 5765 print_5760/65
print_5760/65_1
Fiery XJ 5790 print_5790
Docucolor 4040 print_DocuColor
Emulex Corp. NETJex/NETQue print server TEXT
PASSTHRU
PASS
Epilog Legend Laser Engraver Legend
Epson Interface Card LPB
LPBF
Extended Systems ExtendNet Print Printern
GCC Technologies Elite XL EliteXL
HP JetDirect Internals raw
text
JetDirect Externals raw1 / text1
raw2 / text2
raw3 / text3
Intermec 4400 series PR1
I-Data Easycom 10 Printserver par1
Easycom 100 Printserver LPDPRT1
IBM Network Printer 12,17,24,14PS PASS
NP & Infoprint Printers (4300) series PASS
3130 afccu2
Intel NetPort Express 10/100 and Pro LPT1_PASSTHRU
LPT2_PASSTHRU
COM1_PASSTHRU
Lantronics EPS1, EPS2 (serial) EPS_nnnn_S1
(parallel) EPS_nnnn_P1
Lexmark RN+ printer
printer_cr
MarkNet XLe Adapter Parallel 1 printer
printer_cr
Parallel port 2 printer2
printer2_cr
Serial port printer9
printer9_cr
Optra S 1855 PASS
Linksys Print server box L1
L2
L3
Minolta QMS Magicolor 330 same as IP address
raw
OCE 3165 oce3165
9400 oce9400
Rose Electronics Microserve Print Servers lp
Tektronics Phaser 560(per language) PS
AUTO
HPGL
PCL
Xerox DocuPrint DP65 dp65
dt65
user-configurable
DocuCentre

DC265

lp

 

Models 4505, 4510, 4517, 4520 PASSTHRU
Model 4512 PORT1
Model N17, N24, N32 RAW
Models 4900, 4915, 4925, C55 PS
DocuCentre DC220/DC230 lp

Note: These names are all case-sensative. This means that you have to type the names exactly as you see them, uppercase letter, lowercase letter, forward slashes(/), dashes(-), and underscores(_). There are no spaces in any of the names. 

If you would like to help us accumulate and maintain this list, please give us feedback on this article. We are always open to feedback. If you submit an LPD queue name, be sure to include the printer model and hardware print server. Thank you!

I try to send a print job to RPM, and nothing is recorded in the log. I do not exactly know if the problem is in my network or just that RPM is not receiving.

To perform a local telnet test, you need to first have network logging turned on in RPM. Follow these steps:

  1. In RPM, choose "Log" from the "Options" menu.
  2. If they are not already checked, put a check in the first 6 boxes: 'Enable network logging', 'High detail', 'Enable print logging', 'High detail', 'Enable queue logging', and 'High detail'.
  3. Press OK

Now that you have the logging set to high detail, you need to perform a local telnet test. Use the following steps.

  1. Choose Run from the Windows Start menu.
  2. If your computer operating system is Windows 95, 98, or Millennium Edition, type "COMMAND" in the Run dialog. Otherwise, type "CMD". Press OK.
  3. In the command prompt, type telnet 127.0.0.1 515 and press Enter. If you know the IP address of the RPM host, substitute it instead of 127.0.0.1.
  4. Depending on your RPM settings and your operating system, different results can occur. For instance, on Windows 2000 or XP:
    • If a telnet window pops up, or the command prompt goes to a plain black screen with only a blinking cursor, but nothing else happens, press Enter again.
    • A dialog should pop up stating: 'Connection to host lost' and in the Telnet window, another message appears: 'Socket xxxx received unknown command 0xd with arguments."
  5. On Windows 9x or NT, with older versions of RPM, this may happen:
    • You may see a message in the DOS prompt that says 'Client port xxxx out of range'.
  6. In either case, check the RPM log for the same message.
    • In RPM, press the "Log" tab at the bottom of the RPM window.
    • Look for the same message you received above: 'Client port xxxx out of range'.

If the RPM log has the same error, that means RPM is working fine. If not, that means something else got the connection and is not allowing RPM to do its job. You need to look for another LPD that might be starting before RPM. Some terminal emulators such as "Exceed" install an LPD server software that cannot on the same computer at the same time with RPM.

I can ping the PC, but can't connect.

First, make sure your remote computer can see RPM. Attempt to connect to RPM using the telnet program. Most Unix telnet programs can take an optional port argument. The following command will attempt to connect to the host rpm.somewhere.com on TCP port 515, which is the port RPM listens on for incoming print jobs.

  telnet rpm.somewhere.com 515

If you can connect to RPM, you will probably see the following text (or equivalent).

  Trying rpm.somewhere.com...
  Connected to rpm.somewhere.com
  Escape character is '^]'.

Pressing the Enter key at this point should close the connection and display the following message.

  Socket xxx received unknown command 0xd with arguments  Connection closed by foreign host.

The first part of the above message is RPM's response to an unknown command. Check the RPM log for the same message as it should be logged as a warning. If the message shows up in the RPM log, you have made a successful connection to RPM.

If you get "Connection refused" or "Connection timed out", check and relax port 515 for any firewalls (software or hardware based) that may be blocking the connection.

If you see a message such as "Unknown host", check your server's DNS configuration (on some machines this is in /ect/hosts) and make sure there is an entry for your PCs hostname, or that your server has the appropriate DNS servers configured.

Open the LPD Options dialog by choosing LPD Options from the Options menu in RPM. If you have turned off "relax the 'port in range' requirement", after initiating the above telnet command, you will see the following message. You will also see it in the RPM log as well.

   Client port xxxx is out of range

Even though these are warnings in the RPM, they merely show that a connection has been made to RPM. You can safely ignore the warnings.

How do I setup SCO UNIX to print to RPM Remote Print Manager®?

Make sure you have a line in your /etc/hosts file that has the IP address of the PC you have installed RPM on, and a hostname for that PC.

At the shell prompt type "telnet <hostname> 515". <hostname> should be the name of the PC running RPM.

If you get the following response (or similar), your setup is correct:

	Trying <xxx.xxx.xxx.xxx>:
	Connected to <hostname>.
	Escape character is '^]'.
	Client port 1107 out of range
	Connection closed by foreign host.

Now run scoadmin and choose "Printers".

Choose "Printer Manager".

Choose Printer/Add Remote/UNIX

Now, put your host name and printer name in. (Make sure to deselect the box that says: "Use extended remote printer")

If you forget this, you can later remove the ":ex" from the /etc/printcap file using vi or another text editor.

For a more detailed set of instructions, click here.

I am trying to print from a Dec VAX. The problem is that the OCX software does not support LPR printing! However, it will use Telnet. Can I set up RPM Remote Print Manager this way?

Set the DEC VAX to send to port 9100 and the printer queue name to the RPM queue name.

You also need to configure RPM to receive on Telnet 9100. Follow these steps:

  1. In the RPM UI, select Options/Protocols:
  2. In the Protocol type, use "Telnet".
  3. In the TCP/IP port, type "9100", and click Add.
  4. Choose the queue that will receive jobs from the Dec VAX.
  5. Click OK, Then OK again on the Server Protocols dialog.
  6. Choose Yes to restart server protocols.

How do I setup Linux to print to RPM Remote Print Manager® (RPM)?

Make sure you have a line in your /etc/hosts file that has the IP address of the PC you have installed RPM on, and a hostname for that PC.

At the shell prompt type "telnet <hostname> 515". <hostname> should be the name of the PC running RPM.

If you get the following response (or similar), RPM is listening correctly:

	Trying <xxx.xxx.xxx.xxx>:
	Connected to <hostname>.
	Escape character is '^]'.
	Client port 1107 out of range
	Connection closed by foreign host.

Now run printtool and press "Add".

Choose "Remote Unix (lpd) Queue".

By default, the spool directory, file size limit, and name are automatically entered. You may change this information, or add another name by typing a pipe (|) character and another name.

Now, add your remote host destination ip address or hostname (RPM PC) and the remote queue name which will be the queue name in RPM.

For a more detailed set of instructions, click here.

What are some ways of determine the IP Address of my computer?

There is no standard way to determine the IP address of a computer that works for all operating systems and versions. However, you can usually view all information about your TCP/IP configuration by running some sort of configuration program. Here are some of the most common ways for the most common operating systems.

Windows 7

  1. Go to Start\Programs\Command Prompt. This will bring you to the MS-DOS window.
  2. At the prompt, type "ipconfig". You will see your IP address and other TCP/IP configuration information.

Windows 8 / Windows 10

  1. Go to Cortana, type in "cmd", then when Cortana shows you "Command Prompt" click on that.
  2. Type in "ipconfig" and hit the Enter key.
  3. Look for a line that says "IPv4 Address". The 4 part number at the end is what you are looking for. 

UNIX/Linux

From a command line, enter "ifconfig". This stands for interface configuration. This works on most UNIX or Linux systems.

Other Systems 

Consult your documentation, or contact your system administrator.

How do I configure my SGI IRIX lpr to print through RPM Remote Print Manager®?

To print through RPM from SGI IRIX, the following instructions will help you configure the remote printer definition.

The daemon /usr/etc/lpd should already be running by default if the proper software has been installed. This software is installed from the eoe2.sw.bsdlpr subsystem on 3.3.1 or later versions of IRIX.

  1. Edit the /etc/printcap file and add your printer information. If you need help here, see the man pages for printcap. If you want to make a printer the default printer for the lpr command, add lp to the list of printer name aliases. A typical printer entry looks like:

    hp4|rpmqueue|lp:\
    :sd=/usr/spool/print/hp4:\
    :rm=rpm.brooksnet.com:\
    :rp=rpmqueuename:\
    :lf=/var/adm/lpd-errs:

  2. Create the general spool directory and set the correct ownership and permissions. This step should only be done if this is the first printer created. You cannot perform this step more than a single time.

    cd /usr/spool
    mkdir print
    chown lp print
    chgrp lp print
    chmod 755 print

  3. Create the spool directory for the new printer and set the correct ownership and permissions. The name of the directory is specified in the /etc/printcap entry on the sd= line.

    cd /usr/spool/print
    mkdir hp4
    chown lp hp4
    chgrp lp hp4
    chmod 755 hp4

  4. At this point, the system should be restarted or you may restart the /usr/etc/lpd to allow the changes to take effect.

Note: To print, enter the following command at the shell prompt:

lpr -Php4 path/to/file

What steps should I perform on my firewall to enable RPM to receive print jobs from a system that is outside the firewall, perhaps from the Internet or WAN connection?

To answer this question you will need to know how your firewall is configured, and which protocol you will be using to print.

Firewall: NAT

If your firewall is performing Network Address Translation (NAT), you will configure port forwarding on your firewall.

  • If you are using the LPR/LPD protocol, and your firewall is performing NAT, you will forward traffic coming in on port 515 to the internal IP address of the RPM host.
  • If you are using streams and your firewall is performing NAT you will forward traffic on whichever port you configured on the sending side (e.g. 9100) to the internal IP address of the RPM host.

Firewall: not NAT

If your firewall is not performing NAT, you will simply allow data to go through your firewall. This is called relaxing a port.

  • If you are using the LPR/LPD protocol, you will relax port 515 on your firewall.
  • If you are using streams printing, you will relax the appropriate port number. The port number you relax will depend on how your printer is configured on the sending side; typically, it will be in the range of 9100-9200, but could be any port number between 1 and 65535.

Note: Streams printing may be referred to as any of the following: Socket Printing, Reverse Telnet, or Telnet Printing.

Note: Your firewall may require you to supply the type of connection; both LPR/LPD and streams printing are TCP connections, not UDP.

I have a host system running that does not support the LPR/LPD protocol, however, it does support the Telnet protocol for printing. Can I configure RPM to receive jobs using the Telnet protocol?

RPM Remote Print Manager® provides the ability to receive print jobs via a direct socket connection on any port. This is also known as stream printing or reverse telnet. Ports used for this purpose typically start at 9100 similar to the Jetdirect protocol. Follow the steps below to configure RPM for direct socket printing.

In the RPM GUI:

  1. Go to the View menu and select General Settings.
  2. Click the Ports icon.
  3. Click Add Port.
  4. Select "Telnet" from the list, and enter a port number.
  5. Select a queue to send telnet jobs to. The defaults for the other settings are usually good enough.
  6. Click the Save button.

My printer is an Apple LaserWriter Pro 810 and it has a built in print server. I cannot configure my print server to work with INTELLIscribe.

The LaserWriter Pro 810 does not support the JetDirect protocol. You must select the LPD:515 protocol in INTELLIscribe and assign it a queue name. The built-in queue names for this print server are "TEXT" and "PASSTHRU" (remember that the queue names are case-sensitive).

"PASSTHRU" should be used as the data will already be formatted for the printer.

My RPM Remote Print Manager® will not receive jobs from the Tandem operating system on the mainframe. Can I configure RPM to receive jobs from a Tandem OS?

We have researched the Tandem operating system and found that the old OS versions do not support the LPR/LPD protocol natively.

There are 3rd-party LPR spoolers available, and RPM can receive jobs fine using their "raw" printing. Configure the Tandem systems as follows:

Create a file in $SYSTEM.SYSTEM called FASTCNFG with the following information.

  !****** CONFIGURE TCP/IP DIRECT FOR RPM Software ******
  Device $LPRT1
  CONTYPE	=TCP/IP
  ADDRESS	=192.168.1.50 (RPM host IP Address)
  PROTOCOL	=NONE
  PORT	=9100 (Telnet port setup in RPM)

Now, configure RPM to receive jobs using the Telnet protocol on port 9100. Note that this port number can be any TCP/IP port number you choose. Some port numbers are reserved for other protocol such as 21 for FTP and 23 for regular Telnet.

  1. In the RPM UI, select "Options/Protocols:".
  2. In the Protocol type drop-down list, select "Telnet".
  3. In the TCP/IP port, type "9100", and click Add. Make sure that you do not add telnet using port 515 or this will cause a problem with RPM.
  4. Choose the queue that will receive jobs from the Tandem.
  5. Click OK, then OK again on the Server Protocols dialog.
  6. Choose Yes to restart server protocols.

We have learned that new OS versions support the LPR/LPD protocol natively. To do this:

  1. Create a device name in Tandem using "SPOOLCOM".
  2. In your "FASTCNFG" file, create an entry similar to the above entry, using "LPD1179" in "PROTOCOL" in place of "NONE".
  3. Do not enter "PORT", or configure it to port 515, since this is the proper LPR/LPD port number.

Data (6)

When printing through RPM, the Euro currency symbol does not print, but is translated into a space character. How can this be resolved?

RPM handles the Euro symbol just fine, however, you must use a font that defines the euro symbol, such as Courier New. Here are some steps to help you determine where the problem lies.

First, determine if the Euro symbol is received by RPM. If it was sent, it will be in the data.

  1. Suspend the RPM queue, so it is displayed like "Queue xxx: Enabled, Suspended, Not holding" in the RPM Queue Status window.
  2. Send a print job to RPM just as if the file would be printed through RPM. Since the queue is suspended, the file will not print. Open the RPM\Spool folder. In it should be the data file, beginning with "dfA" followed by a sequence number, followed by the host system that sent the job to RPM. Example: dfA1tempest.
  3. View the contents of this file with a hex editor. A good one is UltraEdit32. Search for the hex character 0x80 or 80. This is the hex equivalent of the Euro symbol.

If the character is in the file, then your problem might simply be a font that does not support the symbol. If it is not in the file, then your efforts should be concentrated on the sending side host, as it is not sending the currency symbol to RPM.

Category: 

CL codes are showing in my print job and I am using a "raw" type queue.

This could be caused by any of the following:

  • The printer does not support PCL 

If this is the case, you must either format the data differently on the sending side, or use a "text" type queue when that is not possible.

  • The printer does not support that PCL version 

Format the data using a PCL level that the printer does understand.

  • The Windows driver is using different PCL version than what is in the file 

Change the Windows print driver to one that supports the same PCL version that is in the file or use a "text" type queue in RPM if that is not possible.

Category: 

We need RPM Remote Print Manager® to translate EBCDIC to ASCII.

RPM has a native EBCDIC translator, which can handle not only US EBCDIC but European language extensions from a variety of countries.

Follow these steps to use the EBCDIC translator:

For RPM 5.0 and newer:

The SCS to Text Markup transform natively supports this translation. You can also change codepages on the various Text to Text Markup transforms.

For RPM 4.5:

  1. Select "Edit Queues" from the "Queues" menu in RPM.
  2. Choose which queue you want to translate from the drop-down queue list.
  3. Press the "Print Data Options" button.
  4. In the "Transform" tab, check "EBCDIC". Also, you can choose (from the drop-down list) to have RPM use a different language for translation. By default, RPM will pick the language closest to your computer's locale setting.

Does RPM Remote Print Manager® support Intelligent Printer Data Stream (IPDS) files from the AS/400 or IBM mainframe systems?

RPM cannot support IPDS. Our newest product, ExcelliPrint®, is currently available and supports IPDS extensively. To learn more about Excelliprint, please visit our IPDS site.

Does RPM Remote Print Manager® support printing AFPDS files generated from an AS/400 or System 390?

The AS/400 will convert AFPDS data streams via Host Print Transform for AS/400 printer emulations. An RPM raw type queue will pass the converted data directly to the printer bypassing the Windows print driver.

ExcelliPrint does handle AFPDS files, please visit ExcelliPrint's IPDS Printing home page. ExcelliPrint gives you the power to print IPDS to any Windows-based printer.

System 390 supports the AFPDS conversion via the Infoprint system. RPM can then pass the converted data directly to the Windows printer through an RPM raw type queue.

I have changed my code page to print in a different language, but now when I print to RPM Remote Print Manager®, certain characters are replaced with a question mark (?). Why?

The printed "?" means that the character is not supported by the current code page. You need to change your code page to one that supports the character you're trying to print. The code page is in the Text Setup dialog.

If you've selected the correct code page, try a different script. To do this, follow the steps below.

  1. From the 'Queues' menu, choose 'Edit Queues:'.
  2. In the 'Edit Queues' dialog, make sure the 'Text' queue type is selected. Press the 'Queue Setup' button.
  3. In the 'Text Setup' dialog, you will see the Windows code page you are using. Verify the correct code page is selected. Press the 'Font' button. Note that it may be labeled 'Courier New 12' or similar.
  4. The 'Font' dialog is where you select the proper script. There could be multiple scripts depending on the language. You need to experiment to see which translates your document with the correct characters.

I am printing from IBM's AIX (Unix System V) to RPM Remote Print Manager®, and the following appears in the RPM log:

Warning: Unrecognized control line: -N1
Warning: Unrecognized control line: -Zmblack@host2
Warning: Unrecognized control line: -tmblack@host2
Warning: Unrecognized control line: -TSTDIN.34509

Furthermore, if I specify the number of copies, RPM ignores it.

The format of the control lines sent by LPR is documented in RFC 1179. IBM, SCO, and other vendors have chosen to add their own "extended" options. RPM understands the standard BSD control lines.

New versions of RPM should properly handle the "number of copies" feature. These extended options are not documented thoroughly like the RFC 1179 specification.

RPM will ignore all control lines that it does not recognize. You will see simple information messages in the log because they are not detrimental to the way RPM processes the rest of the data. They are simply ignored.

Printer limit exceeded for queue xxxx, printer 'yyyy' (in the RPM Remote Print Manager® Log).

You will see this message when you have exceeded the number of allowed printers that your copy of RPM supports. The Trial version of RPM supports printing to any two printers connections in a single session. The Select version of RPM supports up to 10 printers connections in a single session. Unlimited printer connections may be purchased by contacting Brooks Internet Software.

Error: Unable to create MsgBoxer CoClass

The issue of the "unable to create MsgBoxer CoClass" should be resolved by installing the latest release of INTELLIscribe and rebooting the PC.
If this does not resolve the issue please contact Technical Support and we will resolve the issue.

I have just installed RPM Remote Print Manager®. When I try to restart the computer or start the "RPM Remote Print Manager" service, I get "Error 1058: The service is disabled and cannot be started." When I go to the services utility and look at the RPM service, it shows "Automatic", not "Disabled".

This issue is caused when the service your are trying to start has been disabled for the current hardware profile. Consulting the Microsoft KB articles yield the following resolution:

  1. From Administrative Tools, open the Services utility.
  2. Right-click the RPM Remote Print Manager service and choose Properties.
  3. In the Log On tab, near the bottom is a list of hardware profiles and whether or not the service is enabled for that profile.
  4. Highlight your current hardware profile, then click Enable.
  5. Click OK

Note: If the Enable button is grayed out or otherwise unavailable, you may be logged in as a user that does not have the appropriate permissions to modify a service's settings. Log in as the Administrator and try again.

Otherwise, visit the Microsoft support page The Specified Service is Disabled and Cannot Be Started.

My RPM Remote Print Manager® job has been placed in a "Wait" Status

Please check the Log and you will probably see "Printer limit exceeded for queue 'queue name', printer 'xxxxx.'

This message appears when you have exceeded the number of allowed printers that your copy of RPM supports. The Trial version of RPM supports printing to any two printers in a single session. The Select version of RPM supports up to 10 device connections in a single session and the Elite version supports 99 devices and can be increased to support unlimited printer connections by contacting Brooks Internet Software.

The following message pops up when I try to start RPM Remote Print Manager®:

	RPM has detected that another program is using this network port: 515.
	Please check your configuration and try again.

RPM Version 2.2 and later checks to see if another program is using port 515. If you receive this message, exit the program that is using port 515 and restart RPM.

If you setup a queue with LPD protocol and another queue with Telnet protocol, do *NOT* use the port 515 on each. If you do, RPM version 2.2 will not launch and will report the port conflict. If this occurs, one of the queue setups must be deleted from the registry. Contact Brooks Internet Software, Inc. for assistance to proceed.

When trying to print from INTELLIscribe to Linux, the Linux LPD rejects the request and logs an error stating:

	/usr/sbin/lpd: Malformed from address  

The message also appears in the Properties dialog in INTELLIscribe.

The new version of INTELLIscribe sends data on source ports greater than 1024. This is to circumvent a problem with Windows and port timeout periods. Some flavors of Unix and Linux, by default, will only accept data on source ports less than 1024. This is due to a security hole present in systems providing both FTP and LPR/LPD functionality.

INTELLIscribe may be modified to send data on ports less than 1024 in the virtual printer port wizard.

  1. From the Printers menu, choose Add or update virtual printer port.
  2. Click "Next" until the final step.
  3. Modify the "Relax port restr" parameter to display "no" by choosing this from the drop-down list.

When trying to print from INTELLIscribe to Linux, the Linux LPD accepts the entire print job, but does not print it. The job then disappears from the spooler. Unix logs the following errors:

	lp: illegal format character 'o'
	lp: job could not be printed

INTELLIscribe's Properties dialog states that the print job was successful.

INTELLIscribe, by default, specifies to the LPD print server that the data is in "postscript" format. If no Unix PostScript printers are available, or the queue receiving the print jobs is not configured for a PostScript printer, the job will not be printed by Unix.

The default works properly in most cases, however, some Unix LPD servers try to modify the data before printing it when following strict RFC1179 compliance.

You can configure INTELLIscribe to resolve this issue:

  1. From the Printers menu, choose Add or update virtual printer port.
  2. Click "Next" until the final step.
  3. Modify the "Print format" parameter to display "preformatted" by choosing this selection from the drop-down list.

I am using SCO TermVision and I want to use RPM because of the features offered. When I try starting RPM, an error message stating 'RPM has detected another program is using port 515...'. How can I eliminate this message?

SCO TermVision contains a fairly simple LPD package. It will pass raw data to the printer. Since you wish to use RPM for more complicated tasks or features, this LPD should be disabled. To disable it:

  1. Open the Windows "Control Panel". Double-click "Vision Services".
  2. Click the "Printing" tab. Choose "None", meaning TermVision will not have any printers configured.

Now, you should be able to start RPM without the error message. This message is there to warn users or administrators that there is a problem, rather than determining the problem later on.

I am using Chameleon NetManage and I want to use RPM because of the extended features offered. When I try starting RPM, an error message stating 'RPM has detected another program is using port 515...'. How can I eliminate this message?

Chameleon HostLink contains a very simple LPD package. It will pass raw data to the printer. Since you wish to use RPM for more complicated tasks or features, this LPD should be disabled. To disable it:

  1. Open the Windows "Control Panel". Double-click "Network".
  2. Locate the NetManage LPD service. Highlight it, then press "Properties".
  3. Select the setting to disable this service. RPM will be replacing it, along with adding features which are not available in the NetManage LPD.

Now, you should be able to start RPM without the error message. This message is there to warn users or administrators that there is a problem, rather than determining the problem later on. Note: In old versions of Chameleon, the LPD did not run as a service. To disable the LPD in old versions, simply close the application. You should also remove it from the "Startup" group if you will be using RPM.

I recently installed INTELLIscribe on my PC, created a "virtual printer port" and associated my print driver with it. Now, when I reboot my computer, I get the following warning message:

This warning occurs during system startup or login because of print drivers that use language monitors. Unfortunately, most of these print drivers do not provide a mechanism to easily disable the download of fonts on system startup.

Most printers that cause this problem are PostScript printers using the 'ADOBEPS4.DRV'. There are several ways to fix this.

  • The best way: First, delete the printer from the Windows Printers folder. Then, add a new printer using the driver provided on the Windows CD-ROM. Non of these box drivers cause this issue. Usually, a compatible driver can be found even if your specific printer is not on the CD.
  • May cause problems, so do not attempt this unless you cannot find another compatible driver. From the Windows "Start" button, choose "Run". Type 'msconfig' and press OK. In the "Startup" tab, unselect "BRI Fixup Ports". This will ensure that INTELLIscribe will not check the printers at startup, thereby eliminating the warning. Keep in mind that INTELLIscribe may not function properly with this not selected.
  • Could be dangerous: Another way to eliminate this issue is to edit the registry. Changing any reference showing 'ADOBEPS4.DRV' to 'PSCRIPT.DRV'. The registry key you need to modify is HKey_Local_Machine\System\CurrentControlSet\Control\Print\Environments\Windows 4.0\(Printer). Note that you must have another PostScript driver added for 'PSCRIPT.DRV' to be installed.

Note: Editing the registry should only be done in extreme cases. Editing the registry can seriously damage your system or make it unbootable. Only edit the registry after you have backed up the system so you can restore later if problems appear. If you do not feel comfortable editing the registry, contact your system administrator.

Writer abnormally ended (abended).

Your AS/400 is not configured correctly.

Please refer to the AS/400 Setup instructions. The most common settings to check are:

  • REMOTE SYS name and/or the RPM host system's IP address is correct in the remote outq definition or HOST TABLE
  • Verify that the AUTCHK is set to *DTAAUT

After installing INTELLIscribe, I create a new port with the appropriate settings. Then, I open the Windows Print Manager and try to associate that port with an existing printer. The following error message appears:

Printer settings could not be saved. The specified port is unknown.

The Print Manager on Windows NT 4.0 does not query the INTELLIscribe port monitor every time it is needed. There are 2 ways around this issue.

  1. Restart the Windows Spooler service. To do this, open the command prompt and type net stop spooler and wait for the service to stop. Then type net start spooler and wait for the service to start. Once started again, you should now be able to select the INTELLIscribe port from the printer properties dialog..
  2. Instead of using the INTELLIscribe user interface to create the port, use the Windows Print Manager. To do this, open the Properties for the printer, then in the Ports tab, choose to create a new port.

In RPM Remote Print Manager®, I get an "Error: Failed subcommand 4" when printing from my AS/400. What can I do to fix it?

This error is caused by an incorrect setting in the OUTQ on the AS/400. To fix it, follow these steps:

  1. First you must end the writer. From a command prompt on the AS/400, issue the command (without quotes) 'ENDWTR writer_name *IMMED'.
  2. Now from the command prompt, issue the command 'CHGOUTQ queue_name'. Press the F4 key
  3. Now you must get to the "All Parameters". Press F24 (shift-F12) then F9.
  4. Press "Page Down" until you get to the parameter "Destination Type".
  5. Change this to *OTHER.
  6. Finally, save the changes and start the writer again.

I get "Cannot find data queue in library" on my AS/400 when I try to print.

You must leave the library name blank after the Data queue field entry of *NONE. Please refer to AS/400 Setup page for additional instructions.

During installation on Windows XP or Windows Server 2003, you may receive an error stating:

An error (-5006 : 0x80004005) has occurred while running the setup.
Please make sure you have finished any previous setup and closed other applications. If the error still occurs, please contact your vendor: Brooks Internet Software (https://www.brooksnet.com).

This error message can be resolved by running setup from within the Add/Remove Programs utility in the Control Panel. To do this on Windows 2000, XP, or Server 2003, perform the following steps.

  1. From the Start menu, choose Control Panel. Now, open the Add or Remove Programs utility.
  2. On the left side of the Add or Remove Programs utility, click Add New Programs.
  3. Click the CD or Floppy button. When the wizard appears, click Next. After searching your Floppy and CD drives, a page will appear asking you for the program you wish to run. Click Browse and locate the RPM setup program. Click Next and the installation will begin.

You should now be able to install RPM on your computer.

Error: Unable to find data queue in library (AS/400 V3R6).

If you have made all the entries identified in the "AS/400 Setup Instructions" (CRTOUTQ) screen, and get the error message above, then leave the "Library" field blank.

I was not able to disable the option "use extended remote printing protocol" option in the SCO configuration. Now when I print, I receive warning messages in the log stating "unrecognized control line".

You can now modify the /etc/printcap file manually. Open this file in an editor such as 'vi' or 'edit'.

Locate the printer entry for this printer, it should look something like this:

  hp4:\
    :lp=:rm=192.168.1.53:ex:rp=hp4:sd=/usr/spool/lpd/hp4:

Remove 'ex:' from the line. It should now read similar to this:

  hp4:\
    :lp=:rm=192.168.1.53:rp=hp4:sd=/usr/spool/lpd/hp4:

Be sure to leave a colon (:) separator between each entry. Now you can save the file and try printing again. This disables the extended options that are not included in the original RFC 1179 specifications.

When printing from INTELLIscribe to IBM AIX, the status information contains the following warning:

  Host does not have access to line printers

Ensure that a plus sign (+) appears at the end of the /etc/hosts.lpd file. The problem should then be resolved.

Firewall (9)

Will RPM Remote Print Manager® receive jobs from an HP3000 running the MPE/iX operating system (OS)?

The MPE/iX OS does not natively support the LPR/LPD protocol. If you have a 3rd party LPR client for MPE/iX, we recommend you use it; however, we do not provide instructions for configuring 3rd-party clients.

Before getting started, note that TCP/IP printing on the HP3000 is supported on MPE release 5.5 or greater. The first step is to add the printer LDEV. You can add it using SYSGEN, which requires a system reboot, or it can be added dynamically with the IOCONFIG utility.

Creating the LDEV for RPM is exactly the same as any other JetDirect printer.

  1. Log on as Manager.SYS and run IOCONFIG.PUB.SYS.
  2. At the IOCONFIG prompt, type: AD LDEV=nnn PATH=NONE ID=HPTCPJD. Substitute nnn with a unique number.
  3. Exit IOCONFIG by typing EXIT.

Next, an entry in the NPCONFIG file must be created or added. The following configuration should be added to the "NPCONFIG.PUB.SYS" file. If this file does not exist, it must be created.

nnn (network_address = x.x.x.x
  tcp_port_number = 9100
  jam_recovery = false
  pjl_supported = false
  snmp_enabled = false
  setup_file = null.hpenv.sys
)

Replace nnn with the same number as the LDEV. The "network_address" should reflect the IP address of the PC where RPM is installed.

Note: null.hpenv.sys may not exist.  If not, create it first.  The setup_file should be an empty file.

Note: The "tcp_port_number" setting can be any number you choose. You must configure RPM to receive jobs on this port. Also, you must make sure that you are not using a reserved number such as 23 for telnet. Usually, if you use ports in the 9100 range, it will work.

To configure RPM to receive jobs on different ports:

  1. In RPM, choose "Port Settings" from the "Configure" menu.
  2. Choose "Telnet" from the "Select Port Type to Add" list and click Add Port.
  3. Enter 9100 in the Port list, or the number you configured in the "npconfig.pub.sys" file on the HP3000.
  4. From the "Queue" list, choose which RPM queue will receive jobs sent on this port number. We recommend accepting all other default values initially.  Press OK.
  5. The changes should take effect once you press OK on the "Port Settings" dialog.

RPM should now be configured properly for receiving jobs from the MPE/iX OS running on the HP3000 box.

I have a software firewall such as Zone Alarm or the Windows Firewall installed on my computer. What ports need to be opened in order to use ExcelliPrint?

At the minimum, you must relax your firewall to allow allow IPDS traffic.  The default IPDS port is 5001 (though this is configurable on the AS/400).

To determine which port numbers your AS/400 is using, use the CHGDEVPRT. Issue the command for each printer pointed to ExcelliPrint. For the OS/390, look at the PRINTDEV macro defined in the PSF Startup Job. The PORTNO parameter is the port number setting. Again, do this for each printer pointed to the computer where ExcelliPrint is installed.

If you wish to administer ExcelliPrint from another computer, you also need to relax the ports configured for HTTP and, if used, HTTPS. To see which ports are used for administration, use the ExcelliPrint control panel utility. Open Control Panel and double-click the ExcelliPrint icon. If you are using Category View on Windows XP, the ExcelliPrint utility is found in Other Control Panel Options under the See Also collapsible window on the left.

We are using DHCP and DNS or a dialup connection and would like to print data from an AS/400 to a PC. How can I configure the AS/400 so I can print to a computer with a dynamic IP address?

One of our clients provided the following CL program. We are providing it for your consideration. As you can see, this program does the following:

  1. Prompts the user for the name of the OUTQ (printer) they want to use
  2. Automatically obtains their IP Address.
  3. Notifies the user that the OUTQ's IP address is being updated.
  4. Updates the OUTQ they provided with their IP address.
  5. Prompts them to update another OUTQ.

The CL program may be used and modified for your needs. It is possible to modify the program to eliminate all user interaction and automatically update the proper OUTQ on the AS/400. This program should be placed in the user's profile and run when the user logs in.

Download the CL program in a PDF document

This document is our best approximation of the correct tab and structure. We are currently unable to provide anything more accurate than this but no doubt an RPG programmer can make sense of it.

RPM Remote Print Manager® (RPM) "Queue Status" shows Xfer next to the file name and the job never shows completely received (Done).

The above status indicates that RPM is receiving. Therefore, this is not an RPM problem. The problem is on the "Sending or LPR" side. Should you experience this issue, we suggest that you contact your network administrator (feel free to e-mail support). There are a variety of setup problems that can cause this symptom as shown below by the following *real* examples:

  1. Firewall issues - The control file could be sent just fine and a firewall could stop the data from sending. The resolution to this issue is to review the firewall log to see if the firewall is blocking the data transfer.
  2. Network issue - When many routers are on a network providing many paths to all of the networks. One of the routers could be performing nat translations of the address of the lpd server to allow for a second path to the machine if the primary was down. The problem develops when the nat translation is only being performed on the path to the server and not from the server. So the initial connection will be made and when the server sends back the ack packet, it will be sent from a different ip address which would cause the sender to fail to reply (expecting a reply from the address it was sent to). The resolution to this issue was to verify that the nat ip address to LPD server is same as ack ip from LPD server.
  3. Sending Host Setup issue - An incorrect print queue configuration on the Sending Host may also cause this to occur. To resolve this situation, verify the correct print queue setup.

I have upgraded to a new computer. Now, when I try to print from the AS/400, the job never makes it to my RPM queue. Is there something I need to do when upgrading PCs or changing the IP addressing scheme?

There are two common causes to this problem.

  1. The new computer typically has a different IP address than the previous RPM host computer. To resolve this, you must configure the AS/400 OUTQ with the IP address of your new RPM computer.
    1. From an AS/400 command prompt, issue this command, substituting your OUTQ name where appropriate: ENDWTR outq name *IMMED.
    2. Wait 15 seconds, then issue this command, again substituting your OUTQ name where appropriate: CHGOUTQ outq name. Press F4 to prompt, as opposed to the Enter key. If you press the Enter key, start again from the beginning.
    3. In the Change Output Queue screen, press F9. Verify the Remote system parameter is set to *INTNETADR (or to the DNS hostname of your new RPM host).
    4. Locate the Internet Address parameter. Enter the IP address of the new computer. Do not use single quotes or an asterisk (*).
    5. Now, press Enter. If the Writers to autostart parameter is greater than zero, the writer for this OUTQ will start automatically and printing will begin. If not, you must enter the following command to start the writer: STRRMTWTR outq_name. Press Enter.
  2. The other most common problem is that the computer has a firewall installed. Printing from the AS/400 to RPM requires the firewall to allow incoming data on port 515. This page has instructions on configuring the Windows XP Service Pack 2 firewall.

What steps should I perform on my firewall to enable RPM to receive print jobs from a system that is outside the firewall, perhaps from the Internet or WAN connection?

To answer this question you will need to know how your firewall is configured, and which protocol you will be using to print.

Firewall: NAT

If your firewall is performing Network Address Translation (NAT), you will configure port forwarding on your firewall.

  • If you are using the LPR/LPD protocol, and your firewall is performing NAT, you will forward traffic coming in on port 515 to the internal IP address of the RPM host.
  • If you are using streams and your firewall is performing NAT you will forward traffic on whichever port you configured on the sending side (e.g. 9100) to the internal IP address of the RPM host.

Firewall: not NAT

If your firewall is not performing NAT, you will simply allow data to go through your firewall. This is called relaxing a port.

  • If you are using the LPR/LPD protocol, you will relax port 515 on your firewall.
  • If you are using streams printing, you will relax the appropriate port number. The port number you relax will depend on how your printer is configured on the sending side; typically, it will be in the range of 9100-9200, but could be any port number between 1 and 65535.

Note: Streams printing may be referred to as any of the following: Socket Printing, Reverse Telnet, or Telnet Printing.

Note: Your firewall may require you to supply the type of connection; both LPR/LPD and streams printing are TCP connections, not UDP.

Can INTELLIscribe print through a firewall?

There are many ways to print from INTELLIscribe through a firewall. Just like all network questions, it depends on how the firewall is configured and what functions it is performing.

If your firewall is performing Network Address Translation (NAT), you will configure port forwarding on your firewall. The virtual printer port will be configured to use the external IP address of your firewall.

  • If you are using the LPR/LPD protocol, you will forward traffic coming in on the port configured in INTELLIscribe to the internal IP address of the printer or print server. The internal port number should always be 515.
  • If you are using Jetdirect, you will forward traffic coming in on the port configured in the INTELLIscribe virtual printer port to the internal IP address of the Jetdirect printer or print server, using whichever port your server is listening on, typically 9100, 9101, or 9102. Check your Jetdirect print server documentation for the correct port number.

If your firewall is not performing NAT, you will simply allow data to go through your firewall. This is called relaxing a port. In this case, you will configure the destination in INTELLIscribe to use the printer or print server's IP address.

Note: Your firewall may require you to supply the type of connection; both LPR/LPD and streams printing are TCP connections, not UDP.

Also remember that some low-end, low-cost firewalls do not support port forwarding.

When sending a print job from the AS/400, it goes into a holding (*HLD) status, and does not print. There are no messages logged to the RPM log whent his happens.

This is caused when a connection cannot be made from the AS/400 to the RPM host. To resolve the issue, verify the settings in the OUTQ match the recommended settings on our AS/400 setup instructions. To begin modifying the OUTQ, follow these instructions.

  1. From an AS/400 command prompt, issue this command, substituting your OUTQ name where appropriate: ENDWTR outq name *IMMED.
  2. Wait 15 seconds, then issue this command, again substituting your OUTQ name where appropriate: CHGOUTQ outq name. Press F4 to prompt, rather than the Enter key. If you press the Enter key, start again from the beginning.
  3. Press F9 to view all parameters, then compare your settings with our AS/400 setup instructions.

Verify the RPM host's IP address or DNS hostname are configured properly, and that there are no firewalls between the AS/400 and RPM that may be blocking the connection, including the Windows XP Service Pack 2 firewall. If the Windows Firewall is the cause, we show you how to add a firewall exception.

When attempting to print from the AS/400, the spool file immediately goes into a sending (*SND) status but does not print.
No messages are logged in the RPM Remote Print Manager® (RPM) log when this happens.

There are a number of settings on the remote AS/400 OUTQ that can result in this issue. To resolve, verify the OUTQ settings match the recommended settings on our AS/400 setup instructions. To begin modifying the OUTQ, follow these instructions.

  1. From an AS/400 command prompt, issue this command, substituting your OUTQ name where appropriate: ENDWTR outq_name *IMMED. Press Enter.
  2. Wait 15 seconds, then issue this command, again substituting your OUTQ name where appropriate: CHGOUTQ outq_name. Press F4 to prompt. If you press the Enter key, start again from step 1.
  3. Press F9 to view all parameters, then compare your settings with our AS/400 setup instructions.

Also, verify the RPM host's IP address or DNS hostname are configured properly, and that there are no firewalls between the AS/400 and RPM that can be blocking the connection, including the Windows Firewall. If the Windows Firewall is the cause, click here for assistance.

How to (45)

Will RPM Remote Print Manager® receive jobs from an HP3000 running the MPE/iX operating system (OS)?

The MPE/iX OS does not natively support the LPR/LPD protocol. If you have a 3rd party LPR client for MPE/iX, we recommend you use it; however, we do not provide instructions for configuring 3rd-party clients.

Before getting started, note that TCP/IP printing on the HP3000 is supported on MPE release 5.5 or greater. The first step is to add the printer LDEV. You can add it using SYSGEN, which requires a system reboot, or it can be added dynamically with the IOCONFIG utility.

Creating the LDEV for RPM is exactly the same as any other JetDirect printer.

  1. Log on as Manager.SYS and run IOCONFIG.PUB.SYS.
  2. At the IOCONFIG prompt, type: AD LDEV=nnn PATH=NONE ID=HPTCPJD. Substitute nnn with a unique number.
  3. Exit IOCONFIG by typing EXIT.

Next, an entry in the NPCONFIG file must be created or added. The following configuration should be added to the "NPCONFIG.PUB.SYS" file. If this file does not exist, it must be created.

nnn (network_address = x.x.x.x
  tcp_port_number = 9100
  jam_recovery = false
  pjl_supported = false
  snmp_enabled = false
  setup_file = null.hpenv.sys
)

Replace nnn with the same number as the LDEV. The "network_address" should reflect the IP address of the PC where RPM is installed.

Note: null.hpenv.sys may not exist.  If not, create it first.  The setup_file should be an empty file.

Note: The "tcp_port_number" setting can be any number you choose. You must configure RPM to receive jobs on this port. Also, you must make sure that you are not using a reserved number such as 23 for telnet. Usually, if you use ports in the 9100 range, it will work.

To configure RPM to receive jobs on different ports:

  1. In RPM, choose "Port Settings" from the "Configure" menu.
  2. Choose "Telnet" from the "Select Port Type to Add" list and click Add Port.
  3. Enter 9100 in the Port list, or the number you configured in the "npconfig.pub.sys" file on the HP3000.
  4. From the "Queue" list, choose which RPM queue will receive jobs sent on this port number. We recommend accepting all other default values initially.  Press OK.
  5. The changes should take effect once you press OK on the "Port Settings" dialog.

RPM should now be configured properly for receiving jobs from the MPE/iX OS running on the HP3000 box.

When printing through RPM, the Euro currency symbol does not print, but is translated into a space character. How can this be resolved?

RPM handles the Euro symbol just fine, however, you must use a font that defines the euro symbol, such as Courier New. Here are some steps to help you determine where the problem lies.

First, determine if the Euro symbol is received by RPM. If it was sent, it will be in the data.

  1. Suspend the RPM queue, so it is displayed like "Queue xxx: Enabled, Suspended, Not holding" in the RPM Queue Status window.
  2. Send a print job to RPM just as if the file would be printed through RPM. Since the queue is suspended, the file will not print. Open the RPM\Spool folder. In it should be the data file, beginning with "dfA" followed by a sequence number, followed by the host system that sent the job to RPM. Example: dfA1tempest.
  3. View the contents of this file with a hex editor. A good one is UltraEdit32. Search for the hex character 0x80 or 80. This is the hex equivalent of the Euro symbol.

If the character is in the file, then your problem might simply be a font that does not support the symbol. If it is not in the file, then your efforts should be concentrated on the sending side host, as it is not sending the currency symbol to RPM.

Category: 

When I print, I get a stair step effect.

The reason for this is your Host (e.g. a UNIX system) uses LF as the end of line character and the printer is expecting CR/LF.

For RPM 6.0: add the "Unix to DOS" transform to the setup for this queue.

For RPM 5.0: add the "LF to CRLF" transform to the setup for this queue. Typically it would go at the beginning of the transform list, or just following a code page (data format translation) step.

For RPM 4.5 and prior: this is generally associated with a "RAW" type Queue. To Translate the LF to CR/LF do the following:

  1. Verify the Queue type is RAW
  2. Select the Queue Setup in the Edit Queues Window.
  3. Select Translate LF to CR/LF.

Can I use Ghostscript with RPM Remote Print Manager® (RPM)?

Ghostscript is a PostScript interpreter. PostScript is the most common printer language and is supported by most laser printers from nearly every printer manufacturer. However, there are a number of printers, laser and inkjet both, that do not support PostScript; this is where Ghostscript becomes useful.

The most common reason to use Ghostscript is to convert a PostScript file to PDF. Ghostscript can also output other formats including graphics formats (PNG, JPEG, TIFF, etc.) and printer formats (PCL5, PXL, epson). The second most common reason to use Ghostscript is to print PostScript files to a printer that does not support it.

How to download Ghostscript

You'll need to do a web search such as:

You should be able to find instructions to download and install the software.

You will also need to review the license information which comes with Ghostscript to verify that your use will be in compliance with the copyright holder's terms. This is not something Brooks can help you with.

However, the rest of our instructions will assume you can use GhostScript with permission as intended.

Convert Postscript to PDF

  1. In Queue Settings, create a new Filter action.
  2. Next to Command, click Browse and locate gswin32.exe. For instance, at this writing it was located in C:\Program Files\gs\gs8.64\bin\.
  3. If you are using a filter action, the Arguments should be:
    -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=%n.pdf %s

    If you are using a filter transform, the Arguments would be slightly different:
    -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=%o %s

  4. Set the Working directory to the folder in which you want the PDF file to be saved. To eliminate many issues, this folder should be local.

Note that the %s, %o, and %n are variables (placeholders).  RPM will substitute those values with the appropriate values.  A complete list of available variables is found in the RPM manual under both Filter transforms (page 13) and Filter actions (page17).

Print Postscript to a non-Postscript printer

  1. In Queue Settings, create a new Filter action.
  2. Next to Command, click Browse and locate gswin32.exe. It may be located in C:\Program Files\gs\gs8.64\bin\.
  3. The arguments should be:
    -dNOPAUSE -dBATCH -sDEVICE=mswinpr2 -sOutputFile="\\spool\<Printer Name>" "%s"

Substitute the name of the printer to which you want to print in place of <Printer Name>. This is the name found in the Printers folder.

Note: Certain situations may prevent gswin32 from completing successfully.  Each of the following methods have proven useful to resolve the problem at one time or another.  We suggest trying each method in the order it appears and testing each change until you find the first method that works.

  • The option -dBATCH tells gswin32 it is running as a batch and should exit when finished.  It has been added to these instructions.
  • Try adding the word 'quit' as the last argument to the command line.
  • Add an Append bytes transform to append the word quit to the end of the data file.  One customer reported this method corrupted PDF Documents when attempting to convert Color PostScript files.
  • Configure your Filter action or transform to terminate idle process after a few seconds.  This option will cause gswin32 to close, but it may not be finished with the conversion.

If you encounter any problems, enter the login credentials of the user you are logged on as and select Interact with Desktop. The next time a job is received, the Ghostscript window will be displayed where you can troubleshoot errors. Once resolved, remove the credentials.

There is no page between jobs.

This is a factor for raw printing. Text printing separates documents courtesy the Windows print drivers.

RPM offers several banner types as well as a PCL page seperator. It also supports insert and append byte strings as described below. These would be configured as transforms in the queue setup.

Do you have any documentation on how to print to RPM Remote Print Manager® under Solaris 7/Sparc.

  1. Start the admintool.
  2. Go to Browse..Printers.
  3. Now go to Edit..Add..Access to Printer.
  4. In the "Printer Name" field, type the name of the queue name set up in RPM. (ex. RPM_Queue)
  5. In the "Print Server" field, type the name of the host running RPM. (ex. RPM_PC:IP Address may work here also)
  6. Click OK until you have exited the admintool.

You have now created a virtual printer on your Solaris box. When you want to print, simply issue this command:

	lp -d RPM_PC:RPM_Queue /path/to/filename
Category: 

How do I set up a remote printer on an HP9000 UNIX system or an HP-UX System V 10.x system?

We strongly recommend that you configure your remote printer using the System Administration Manager (SAM). Configuring printers manually on an HP9000 is difficult to do correctly. To install a printer using SAM, follow these steps:

  1. Log in as superuser/root, and launch SAM.
  2. Open LP Spooler, then Printers and Plotters.
  3. From the pulldown menus, choose Actions.
  4. Choose Add Remote Printer/Plotter from the Actions menu. Do not choose Add Network-Based Printer/Plotter. There are several fields for adding information about the printer:
    • Printer Name -- is the name you give to the printer queue on the HP 9000 running SAM.
    • Remote System Name -- is the name or IP address of the remote PC that is running the RPM Remote Print Manager® software. If you use the PC's name, it must be in the HP 9000's hosts file or configured on the Domain Name Server (DNS).
    • Remote Printer Name -- This name should match the Queue Name already setup in the RPM software.
    • Check the Remote Printer is on a BSD System checkbox.
    • Fill in the optional fields as desired.
  5. Click OK to finish the configuration.
  6. Exit SAM.

Permissions Note: Make sure that you have the correct permissions to print from the UNIX host. Check to see that the username is added to the UNIX host file that lists its users (for example, hosts.equiv or hosts.lpd).

We are using DHCP and DNS or a dialup connection and would like to print data from an AS/400 to a PC. How can I configure the AS/400 so I can print to a computer with a dynamic IP address?

One of our clients provided the following CL program. We are providing it for your consideration. As you can see, this program does the following:

  1. Prompts the user for the name of the OUTQ (printer) they want to use
  2. Automatically obtains their IP Address.
  3. Notifies the user that the OUTQ's IP address is being updated.
  4. Updates the OUTQ they provided with their IP address.
  5. Prompts them to update another OUTQ.

The CL program may be used and modified for your needs. It is possible to modify the program to eliminate all user interaction and automatically update the proper OUTQ on the AS/400. This program should be placed in the user's profile and run when the user logs in.

Download the CL program in a PDF document

This document is our best approximation of the correct tab and structure. We are currently unable to provide anything more accurate than this but no doubt an RPG programmer can make sense of it.

I want to receive a print job in RPM from an AS/400 without any printer control characters. Is this possible?

The AS/400 setup instructions show how to receive data into RPM from the AS/400 with Host Print Transform disabled. In this case, RPM will receive SCS data. You can then use the SCS to Text Markup and Remove text markup transforms in RPM to get plain text. Some users have mentioned they get an extra blank line on the first page of the resulting document.

To prevent the random blank line and instead use the AS/400 to perform the EBCDIC conversion leaving plain text, use all settings specified in the AS/400 setup instructions except the following.

  • Host Print Transform: *YES
  • Manufacturer type and model: *WSCST
  • Workstation customizing object: QWPDEFAULT
  • Library: QSYS

You will now get the data without specific printer codes embedded in the document.

RPM Remote Print Manager® is taking a long time to print.

RPM receives and passes the file to your printer quickly. The time frame from the print job being sent to RPM from the host system (e.g. AS/400, Unix, etc.) until the print job is printed can be evaluated with the following steps to determine where the bottleneck is:

Problem 1: Evaluating time to send to RPM

First, suspend the RPM queue (at the menu select Queues, Resume/Suspend). Then send the file from the host (e.g. AS/400, Unix, etc.). Note the time from release at the host until the RPM queue status states "DONE". If it takes a long period of time for RPM to receive the job, the problem is probably associated with processing on the host system.

Resolution 1: Time to send Resolution 

RPM has been used to improve print job performance significantly by performing EBCDIC or SCS transforms rather than have the host do the transformation. To use RPM to transform, set the Print Data Options in RPM to do this transform and set the host to not transform. Now, re-send the print job from the host and note the reduction in the time for RPM to receive the print job.

If your host is not performing a translation, the bottleneck is with your network architecture. You should contact your network administrator for a resolution.

Problem 2: Evaluating time to print from RPM

If the above evaluation did not identify the problem, release the RPM queue (at the menu select Queues, Resume/Suspend) and note the time from release until the job completes printing. If it seems to take a long time for the job to begin printing, the problem could be the spool settings on your PC.

Resolution 2: Time to print from RPM resolution 

Set your spool settings (Start/Setting/Printer - right click on the printer you are sending to, and select Properties/Details/Spool Settings) to "Print directly to printer" and "disable bi-directional support." Now suspend the RPM queue, re-send the print job from the host, release the RPM queue and note the reduction in time to send the print job to the printer.

If this did not reduce the time for the print job to begin printing, here are other considerations:

  • The problem could be with the type of print driver you are using. If you are using a print driver from the manufacturer versus the Windows "box" driver (the driver that ships with Windows), try setting up the printer with the Windows box driver.
  • If RPM is performing formatting, you may change the queue type from TEXT to RAW and perform the "time to print from RPM evaluation" again. If this results in a significantly lower time for the print job to begin printing, you may choose to have your host system do the formatting and send the print job to a RAW type queue. Retry the steps above until you get the combination that works best for you.
  • If this does not improve your time to print, you should consider upgrading the PC that RPM is running on. Because the print job you are formatting will be processed faster on a more powerful PC.

I already have a queue created in RPM, but when I sent a print job, RPM creates a new queue automatically. Why does this happen and can this behavior be changed?

The LPR/LPD protocol requires that the LPR client must specify the name of the queue when it sends a print job. By default, if this queue does not exist, RPM will create the queue automatically instead of denying the print request.

You can turn off the auto-create queue functionality. If this setting is turned off and RPM receives a request to print a job to a queue that does not exist, RPM rejects the print request instead.

To fix this issue, you can do either of the following.

  1. Modify the configuration on the sending side to use the queue name already created.
  2. Delete the queue you created and use the one which is auto-created by RPM.

How do I print to a Tektronix Phaser 560 using INTELLIscribe?

First, the installation instructions for the network card on this printer state that the LPD queue name of "AUTO" or "PS" must be used, all upper case. Quoting from the TEK web site:

  • [For the Name or address of host providing LPD: enter the printer IP Address. For the name of printer on the machine: type AUTO or PS in all UPPERCASE letters (lowercase letters will not work).]

Second, the "Tektronics Phaser 560 Extended," should use the PSCRIPT.DRV "box" driver, which comes with Windows95/98 rather than a driver (e.g. "ADOBEPS4.DRV") from some vendor-supplied media.

Our recommendation to resolve this would be to first delete the Tektronics printer from the Settings/Printers window, and then to reinstall the same printer using the box driver (i.e. just the dialog that pops up when you click Add printer). This should reinstall the driver so that it does not use a language monitor. Should the problem still appear, then you need to edit the registry. Follow these steps to edit the registry:

  1. Choose Start\Run. In the text box, type "Regedit". Then press OK.
  2. Open the "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Environments\Windows 4.0\Drivers\Tektronix Phaser 560 Extended" key
  3. Determine what print driver is being used (e.g. "ADOBEPS4.DRV" or "PSCRIPT.DRV)
  4. Finally, change all the entries which read "ADOBEPS4.DRV" to "PSCRIPT.DRV".

Note: This assumes you have previously installed a PostScript printer, which you can check for by searching in that vicinity of the registry for the "PSCRIPT.DRV" string. If you cannot find it, then just install any PostScript   printer (e.g. Lexmark Optra S PS, HP LaserJet 4  PostScript , etc.) and then delete the printer, selecting "no" at the prompt to delete driver files.

We have recently upgraded to SunOS 2.6 (or later) from a previous version. RPM Remote Print Manager® (RPM) is no longer receiving print jobs from the Solaris box. How can we configure the new operating system version to print through RPM?

There have been significant modifications to the printing system between Solaris 2.5 and 2.6. You may need to remove all old printers and add a new printer to allow RPM to receive print jobs from Solaris 2.6. RPM supports all relevant BSD print protocol options, such as those described in the RFC 1179 specifications.

If you have the graphical desktop CDE, these instructions may be more helpful.

If the above is not helpful, or you want a simpler way to create printers in Solaris, the following command can be used to create a printer that will print to remote print servers such as RPM.

# lpadmin -p name -s host!remote-queue
# enable name
# accept name

Be sure to replace the italicized words above with the correct information in your situation. Below is information if you have any questions as to what each of the italicized words represent.

  • name: The name of the print queue as it will be known in Solaris
  • host: The DNS hostname or IP address of the RPM host
  • remote-queue: The name of the queue in RPM. This name can be identical to name above.
Category: 

How can I create a printer on the Solaris server to print to my queue in RPM?

The steps below will help you configure a printer on Solaris version 2.51 to print through RPM.

  1. At the console, open Admintool.
  2. Open the Printers utility.
  3. From the Edit menu, point to Add and choose Access to Printer.
  4. The following options should be configured.
  • Client: Enter the IP address or hostname of the Solaris server.
  • Printer name: Enter the RPM queue name here.
  • Print Server: Enter the RPM host computer's IP address (or hostname if using DHCP).

I need to send IPDS print jobs to a specific source drawer (paper input tray) on my printer. How do I know on which tray the job will be printed?

You need to know the following three things.

  1. Which tray you want to print to
  2. What PCL command your printer uses for that tray
  3. The source drawer specified in the IPDS file on your host system

ExcelliPrint takes the source drawer specified by the host system and converts it to a PCL escape sequence.

  • If source = 1 use PCL command <Esc>&l1H
  • source = 2 PCL command = <Esc>&l4H
  • source = 3 PCL command = <Esc>&l5H
  • source = 4 PCL command = <Esc>&l8H
  • source = 5 PCL command = <Esc>&l9H
  • source = 6 PCL command = <Esc>&l10H
  • source = Envelope (65) PCL command = <Esc>&l6H
  • source = Manual (33) PCL command = <Esc>&l2H
  • source = Manual Envelope (96) PCL command = <Esc>&l3H

Note: To print to a different tray, you must change the IPDS print job on the host system. Changing ExcelliPrint settings will not change the tray from which the job is printed.

When printing from the AS/400 to RPM and specifying a range of pages to print, it seems this instruction is ignored as the entire spool file is printed. Can RPM be configured to honor the page range setting?

RPM does not impose this limitation, it is caused by the AS/400. With a Remote OUTQ, even if you specify a page range, the entire spool file is sent to RPM and printed. The LPR/LPD protocol does not allow for page range printing, so RPM will print everything that is received.

IBM provides a way for page ranges to be set in remote OUTQs. Click here for more information. RPM also supports page ranges. To control the starting and ending page, the job must be held or the queue suspended. When a print job arrives in RPM, double-click the job, and enter the starting and ending pages. If the specified ending page is less than the starting page, the job will start at the starting page and end when there is no more data to print. Release the job or unsuspend the queue to start printing the job.

My AIX system queue is disabled after a while and I have to restart it again.  Is there any way to keep the AIX queue from being disabled automatically?

When the "Receive a <Printer> Job" command is sent by rembak to a remote server, a positive acknowledgment should be received by rembak before proceeding with sending datafiles. If rembak does not receive a positive acknowledgement within its timeout period, the print request will fail and the queue will be taken down. Datafiles will not be sent across to the lpd server.

With AIX 4.2 and later, set the backend <timeout> period to 120.  To do this, add a printer with the following parameters.

Description

Lexmark Printer (Room 330)

* Name of new PRINT QUEUE to add [aix_queue]
* HOSTNAME of Remote Server 192.168.1.1
* Name of QUEUE on remote server [rpm_queue]
TYPE of print spooler on remote server BSD
Send PASS-THROUGH FLAG to queue
on remote server?
yes
Backend TIME OUT period (minutes) [120]
 Send control file first?  no

For prior versions of AIX edit the /etc/qconfig file as follows:

  Parts:device = @TES_Server1
          up = TRUE
          host = TES_Server1
          s_statfilter = /usr/lib/lpd/bsdshort
          l_statfilter = /usr/lib/lpd/bsdlong
          rq = Parts@TES_Server1:
          backend = /usr/lib/lpd/rembak -T120

How can I manage the jobs with different forms? Using RPM Remote Print Manager®, the AS/400 doesn't send any warning about the change of form.

Even working with different vendors, we have not yet established whether or not the AS/400 LPR can send form information. We are exploring ways to get this information from the '400 directly.

Until then, you might investigate using "styles" with RPM Remote Print Manager®. This would make it easier to manage a number of different layouts, even though it would not be automatic.

Do you have a list of LPD queue names that we can browse to find out our configuration for INTELLIscribe?

Here is a list of LPD queue names which we have collected. If you have documentation for your queue names, please look there before trying these queue names. Some of the queue names in this list may not work because they are specific to the type of LPD server installed in the printer.

Manufacturer Model Queue Name
Apple LaserWriter 16/600 raw
text
LaserWriter Pro 810 TEXT
PASSTHRU
LaserWriter 12/640PS raw
text
LaserWriter 8500 RAW
Axis 560 / 570 / 660 / 670 Externals PRn
Barr Systems Print Servers BARRTCP1
Canon 460 PS (no hard drive) xjprint
xjdirect
460 PS (with hard drive) xjprint
xjhold
GP Series Copier/Printer print
ImageRunner Printers (Fiery LAN adapter) print
Castelle LANpress L1
L2
LANpress 3 P1
P2
P3
D-Link DP-300
DP-301
LPT1_TEXT
LPT1
Decision Data Print Server d1prn
Digi Portserver Does not support LPD
Portserver II raw_n
Digital Products, Inc. NETPrint Print Server PORTn
EFI Canon CLC 300 / 320 / 350 Ext. PRn
Canon CLC 500 / 550 print_500-550
Canon CLC 700 / 800 print_700-800
Canon CLC 1000 print_1000
HP DeskJet 750C print_DJ750C
Kodak ColorEdge 1525 / 1525+ print_1525/25+
Kodak ColorEdge 1550 / 1550+ print_1550/50+
Kodak ColorEdge 1560 / 65 print_1560/65
Lanier 5506 DC print_r
Minolta CF80 print_CF80
Minolta CF900 print_Copier-M
NovaJet Pro print_NJPro
Oce 3107C / 3108C print_3107C/8C
Ricoh NC 5206 print_r
Ricoh 5206 print_r2
Ricoh 5006 print_r
Sharp AR-C860 print_r
Fiery XJ 5760 / 5765 print_5760/65
print_5760/65_1
Fiery XJ 5790 print_5790
Docucolor 4040 print_DocuColor
Emulex Corp. NETJex/NETQue print server TEXT
PASSTHRU
PASS
Epilog Legend Laser Engraver Legend
Epson Interface Card LPB
LPBF
Extended Systems ExtendNet Print Printern
GCC Technologies Elite XL EliteXL
HP JetDirect Internals raw
text
JetDirect Externals raw1 / text1
raw2 / text2
raw3 / text3
Intermec 4400 series PR1
I-Data Easycom 10 Printserver par1
Easycom 100 Printserver LPDPRT1
IBM Network Printer 12,17,24,14PS PASS
NP & Infoprint Printers (4300) series PASS
3130 afccu2
Intel NetPort Express 10/100 and Pro LPT1_PASSTHRU
LPT2_PASSTHRU
COM1_PASSTHRU
Lantronics EPS1, EPS2 (serial) EPS_nnnn_S1
(parallel) EPS_nnnn_P1
Lexmark RN+ printer
printer_cr
MarkNet XLe Adapter Parallel 1 printer
printer_cr
Parallel port 2 printer2
printer2_cr
Serial port printer9
printer9_cr
Optra S 1855 PASS
Linksys Print server box L1
L2
L3
Minolta QMS Magicolor 330 same as IP address
raw
OCE 3165 oce3165
9400 oce9400
Rose Electronics Microserve Print Servers lp
Tektronics Phaser 560(per language) PS
AUTO
HPGL
PCL
Xerox DocuPrint DP65 dp65
dt65
user-configurable
DocuCentre

DC265

lp

 

Models 4505, 4510, 4517, 4520 PASSTHRU
Model 4512 PORT1
Model N17, N24, N32 RAW
Models 4900, 4915, 4925, C55 PS
DocuCentre DC220/DC230 lp

Note: These names are all case-sensative. This means that you have to type the names exactly as you see them, uppercase letter, lowercase letter, forward slashes(/), dashes(-), and underscores(_). There are no spaces in any of the names. 

If you would like to help us accumulate and maintain this list, please give us feedback on this article. We are always open to feedback. If you submit an LPD queue name, be sure to include the printer model and hardware print server. Thank you!

I try to send a print job to RPM, and nothing is recorded in the log. I do not exactly know if the problem is in my network or just that RPM is not receiving.

To perform a local telnet test, you need to first have network logging turned on in RPM. Follow these steps:

  1. In RPM, choose "Log" from the "Options" menu.
  2. If they are not already checked, put a check in the first 6 boxes: 'Enable network logging', 'High detail', 'Enable print logging', 'High detail', 'Enable queue logging', and 'High detail'.
  3. Press OK

Now that you have the logging set to high detail, you need to perform a local telnet test. Use the following steps.

  1. Choose Run from the Windows Start menu.
  2. If your computer operating system is Windows 95, 98, or Millennium Edition, type "COMMAND" in the Run dialog. Otherwise, type "CMD". Press OK.
  3. In the command prompt, type telnet 127.0.0.1 515 and press Enter. If you know the IP address of the RPM host, substitute it instead of 127.0.0.1.
  4. Depending on your RPM settings and your operating system, different results can occur. For instance, on Windows 2000 or XP:
    • If a telnet window pops up, or the command prompt goes to a plain black screen with only a blinking cursor, but nothing else happens, press Enter again.
    • A dialog should pop up stating: 'Connection to host lost' and in the Telnet window, another message appears: 'Socket xxxx received unknown command 0xd with arguments."
  5. On Windows 9x or NT, with older versions of RPM, this may happen:
    • You may see a message in the DOS prompt that says 'Client port xxxx out of range'.
  6. In either case, check the RPM log for the same message.
    • In RPM, press the "Log" tab at the bottom of the RPM window.
    • Look for the same message you received above: 'Client port xxxx out of range'.

If the RPM log has the same error, that means RPM is working fine. If not, that means something else got the connection and is not allowing RPM to do its job. You need to look for another LPD that might be starting before RPM. Some terminal emulators such as "Exceed" install an LPD server software that cannot on the same computer at the same time with RPM.

I'm trying to print to a  Lexmark printer. When I specify yes to print a banner page, the printer still does not print one. Is there a way to print a banner page to a Lexmark printer?

The Lexmark Marknet print server does not handle the banner page issue as the RFC1179 specifications say. You can tell the printer to print a banner page for all LPD print jobs by doing the following:

  1. Telnet to the printer. Select Start\Run... and type: telnet ipaddress 9000.
  2. At the menu, press 5 (Set LPD options) and press enter.
  3. Press 3 (Enable/Disable banner page on all lpr jobs) and press enter. Verify that this option shows ( Enabled )
  4. Enter 'X' to return to the main menu. Enter 'S' to save changes.
  5. Once the changes are saved, test the banner page by printing through INTELLIscribe.

The Lexmark printer should now print a banner page for all jobs printed using the LPR/LPD protocol. You do not need to specify 'yes' in the banner page option in INTELLIscribe since now the printer will print the banner whether you request it or not.

I can ping the PC, but can't connect.

First, make sure your remote computer can see RPM. Attempt to connect to RPM using the telnet program. Most Unix telnet programs can take an optional port argument. The following command will attempt to connect to the host rpm.somewhere.com on TCP port 515, which is the port RPM listens on for incoming print jobs.

  telnet rpm.somewhere.com 515

If you can connect to RPM, you will probably see the following text (or equivalent).

  Trying rpm.somewhere.com...
  Connected to rpm.somewhere.com
  Escape character is '^]'.

Pressing the Enter key at this point should close the connection and display the following message.

  Socket xxx received unknown command 0xd with arguments  Connection closed by foreign host.

The first part of the above message is RPM's response to an unknown command. Check the RPM log for the same message as it should be logged as a warning. If the message shows up in the RPM log, you have made a successful connection to RPM.

If you get "Connection refused" or "Connection timed out", check and relax port 515 for any firewalls (software or hardware based) that may be blocking the connection.

If you see a message such as "Unknown host", check your server's DNS configuration (on some machines this is in /ect/hosts) and make sure there is an entry for your PCs hostname, or that your server has the appropriate DNS servers configured.

Open the LPD Options dialog by choosing LPD Options from the Options menu in RPM. If you have turned off "relax the 'port in range' requirement", after initiating the above telnet command, you will see the following message. You will also see it in the RPM log as well.

   Client port xxxx is out of range

Even though these are warnings in the RPM, they merely show that a connection has been made to RPM. You can safely ignore the warnings.

I have installed RPM Remote Print Manager®, but now I do not know how to setup my AS/400 to print to it. Do you have steps for setting up a remote OUTQ in the AS/400?

  1. From the AS/400 command line, issue the command CRTOUTQ.
  2. The first parameter is Output queue. This is the name of the local queue on your AS/400.
  3. The Library parameter should be QUSRSYS.
  4. The Remote system is the host name of your PC, AS/400 host table entry. We recommend that you use the fully qualified name in both the host table and in this file and screen or you can use *INTNETADR and enter the IP address in the IP Address key later on.
  5. The Remote printer queue is the name of a queue defined on your PC in RPM.
  6. Press F24, F9 now. This should display all parameters.

 

Use the following table to enter values as shown.

Writers to autostart: 1

Connection type: *IP

Destination type: *OTHER

Transform SCS to ASCII: *YES

Go to the Manufacturer type and model parameter. Press F4 to see a list of printers that IBM supports. Pick HP4 for the best RPM features; or pick the printer you will be printing to, if you are using features that RPM does not currently support. Use the following table to enter the values as shown.

Destination options: XAIX XAUTOQ

Operator controlled: *YES

Data queue: *NONE

Library:

Authority to check: *DTAAUT

Authority: *USE

If you want to suppress banner pages, set Print separator page to *NO and Job Separators to 0.

Category: 

How do I setup a queue in AIX version 4.x to print to RPM Remote Print Manager®?

Setting up queues in version 4.x is slightly different than 3.x. Follow these steps:

  1. smit
  2. Print spooling
  3. Add a print queue with the following options:

    Attachment type: REMOTE

    Type of remote printing STANDARD PROCESSING

    Name of queue <PICK_A_NAME>

    Hostname of remote server <REMOTE_SYSTEM_NAME>

    Name of queue on remote server <RPM_QUEUE_NAME>

    Type of print spooler on remote server BSD

  4. Enter to accept, exit from smit and test.

How do I set up my AIX version 3.x queue to print to RPM Remote Print Manager® (RPM)?

  • On the Unix Host, add a line to the /etc/hosts file at the end that lists the IP address of the PC where RPM is installed, then a tab, then a hostname to be referenced, such as:
    192.168.1.100      rprinter
  • Now ensure the LPD subsystem is activated:
    1. smit
    2. Spooler
    3. Manage Remote Printer Subsystem
    4. Server Services
    5. lpd Remote Printer Subsystem
    6. Start Using the lpd Subsystem
    7. Start BOTH now and at System Restart
  • Now configure the Remote Printer Queue:
    1. smit
    2. Spooler
    3. Manage Remote Printer Subsystem
    4. Client Services
    5. Remote Printer Queues
    6. Add a Remote Queue
  • Fill in the fields as follows:
    *NAME of queue to add <AIX printer name>
    ACTIVATE the queue? yes
    Will this become the DEFAULT queue? no
    Queuing DISCIPLINE first come first serve
    ACCOUNTING FILE pathname [  ]
    DESTINATION HOST for remote jobs <RPM hostname> or <IP Address>
    *Pathname of the SHORT FORM FILTER
    for queue status output
    [/usr/lpd/bsdshort]
    *Pathname of the LONG FORM FILTER
    for queue status output
    [/usr/lpd/bsdlong]
    *Name of QUEUE on remote printer <RPM_Queue>
    *NAME of device to add <eg. HP5>
    *BACKEND PROGRAM pathname [/usr/lpd/rembak]

Note: Replace bold items with information specific to your situation. If you are unclear on any of these items, contact your system administrator.

Note: The instructions to setup AIX version 4.x are slightly different. Click here for the 4.x setup instructions.

How do I setup SCO UNIX to print to RPM Remote Print Manager®?

Make sure you have a line in your /etc/hosts file that has the IP address of the PC you have installed RPM on, and a hostname for that PC.

At the shell prompt type "telnet <hostname> 515". <hostname> should be the name of the PC running RPM.

If you get the following response (or similar), your setup is correct:

	Trying <xxx.xxx.xxx.xxx>:
	Connected to <hostname>.
	Escape character is '^]'.
	Client port 1107 out of range
	Connection closed by foreign host.

Now run scoadmin and choose "Printers".

Choose "Printer Manager".

Choose Printer/Add Remote/UNIX

Now, put your host name and printer name in. (Make sure to deselect the box that says: "Use extended remote printer")

If you forget this, you can later remove the ":ex" from the /etc/printcap file using vi or another text editor.

For a more detailed set of instructions, click here.

How do I setup Linux to print to RPM Remote Print Manager® (RPM)?

Make sure you have a line in your /etc/hosts file that has the IP address of the PC you have installed RPM on, and a hostname for that PC.

At the shell prompt type "telnet <hostname> 515". <hostname> should be the name of the PC running RPM.

If you get the following response (or similar), RPM is listening correctly:

	Trying <xxx.xxx.xxx.xxx>:
	Connected to <hostname>.
	Escape character is '^]'.
	Client port 1107 out of range
	Connection closed by foreign host.

Now run printtool and press "Add".

Choose "Remote Unix (lpd) Queue".

By default, the spool directory, file size limit, and name are automatically entered. You may change this information, or add another name by typing a pipe (|) character and another name.

Now, add your remote host destination ip address or hostname (RPM PC) and the remote queue name which will be the queue name in RPM.

For a more detailed set of instructions, click here.

How do I print to RPM Remote Print Manager® (RPM) from an IBM/VSE mainframe running a VTAM-based application?

You can use the General Print Server Daemon to spool jobs to RPM. Here is how to do that:

Use the DEFINE GPSD command to initiate an instance of a GPS Daemon (server). You must define one Daemon for each VTAM logical unit you wish to emulate.

Define GPSD

name:

  • A 1- to 16-character alphanumeric name used to identify this definition. The first character must be alphabetic.

pubname:

  • The public name (enclosed in single quotes) of a library and sublibrary to be used by the GPS Daemon. This library will be used as a staging dataset for LPR data and to contain the optional logging file. It must be available to the TCP/IP filesystem e.g. through using a DEFINE FILE statement.

dest:

  • The IP address (numeric or symbolic) of the remote host where the Line Printer Daemon resides. The port number is determined by the protocol.

pname:

  • The name of a print queue. This name will be sent to the Line Printer Daemon on the remote host to identify the target printer. You must know this name and specify it here. Otherwise, the LPD will reject our attempts to send data. Note that the printer name can be supplied and/or overwritten in a SCRIPT. pname is case sensitive.

lu:

  • The VTAM LUname with which GPS will be known to VTAM applications. This value must be defined to VTAM as an application ID. If omitted, the default is GPSDTERM.

LOG:

  • If 'YES’, the GPS Daemon will create a log file. This file will have a name equal to the value specified for TERMNAME and an extension of 'LOG’. This file is overwritten each time the Daemon is started. The file is a simple text file and can be viewed or printed using standard VSE facilities. The default value is 'NO’.

This information was originally found on the IBM website, however, it is no longer available.

How do I create a device on my host system (mainframe or AS/400) that prints to ExcelliPrint using IPDS?

Detailed information about printing to ExcelliPrint from mainframes and AS/400 systems can be found in the ExcelliPrint manual.

Information in the manual covers both ExcelliPrint Premium and ExcelliPrint Standard.

What are some ways of determine the IP Address of my computer?

There is no standard way to determine the IP address of a computer that works for all operating systems and versions. However, you can usually view all information about your TCP/IP configuration by running some sort of configuration program. Here are some of the most common ways for the most common operating systems.

Windows 7

  1. Go to Start\Programs\Command Prompt. This will bring you to the MS-DOS window.
  2. At the prompt, type "ipconfig". You will see your IP address and other TCP/IP configuration information.

Windows 8 / Windows 10

  1. Go to Cortana, type in "cmd", then when Cortana shows you "Command Prompt" click on that.
  2. Type in "ipconfig" and hit the Enter key.
  3. Look for a line that says "IPv4 Address". The 4 part number at the end is what you are looking for. 

UNIX/Linux

From a command line, enter "ifconfig". This stands for interface configuration. This works on most UNIX or Linux systems.

Other Systems 

Consult your documentation, or contact your system administrator.

How do I configure my SGI IRIX lpr to print through RPM Remote Print Manager®?

To print through RPM from SGI IRIX, the following instructions will help you configure the remote printer definition.

The daemon /usr/etc/lpd should already be running by default if the proper software has been installed. This software is installed from the eoe2.sw.bsdlpr subsystem on 3.3.1 or later versions of IRIX.

  1. Edit the /etc/printcap file and add your printer information. If you need help here, see the man pages for printcap. If you want to make a printer the default printer for the lpr command, add lp to the list of printer name aliases. A typical printer entry looks like:

    hp4|rpmqueue|lp:\
    :sd=/usr/spool/print/hp4:\
    :rm=rpm.brooksnet.com:\
    :rp=rpmqueuename:\
    :lf=/var/adm/lpd-errs:

  2. Create the general spool directory and set the correct ownership and permissions. This step should only be done if this is the first printer created. You cannot perform this step more than a single time.

    cd /usr/spool
    mkdir print
    chown lp print
    chgrp lp print
    chmod 755 print

  3. Create the spool directory for the new printer and set the correct ownership and permissions. The name of the directory is specified in the /etc/printcap entry on the sd= line.

    cd /usr/spool/print
    mkdir hp4
    chown lp hp4
    chgrp lp hp4
    chmod 755 hp4

  4. At this point, the system should be restarted or you may restart the /usr/etc/lpd to allow the changes to take effect.

Note: To print, enter the following command at the shell prompt:

lpr -Php4 path/to/file

I want to utilize the broadcast printing feature in INTELLIscribe®. What are the requirements and how do you configure the Virtual Printer Port?

The requirements are simple:

  • Install the software on a Windows-based system.
  • Your printers must be attached directly to the network and have TCP/IP support. Or, if you have a software LPD print server such as our RPM Remote Print Manager®, the printer can be attached to the computer where the software is installed.
  • Each printer needs to be the same model, or understand a common printer language such as PCL or PostScript.

Then, you need to create a virtual printer port following these instructions.

  1. In the INTELLIscribe window, choose Add from the Port menu. The Virtual Printer Port Wizard begins. Review the introduction page and click Next to begin
  2. This step requires you to enter a name to associate with the port, the name can contain spaces. Also, you are required to choose how the destinations will be used; Choose broadcast and click Next.
  3. Enter each destination that you need to print to, providing the TCP/IP Address or hostname of the printer, the protocol, and a port number. Once all the destinations are entered, click Next to continue.
  4. Customize protocol specific attributes. When using the LPR/LPD protocol, the Queue Name is a required parameter. Some printers require specific queue names. Consult your documentation, or check our website for the correct LPD queue name.
  5. Finally, open the Windows Printers folder and install a new printer. When you are prompted to select a port where the printer is attached, select the port you named in step 2.

I have a Xerox DocuTech/Print 65. I need to print to it directly from a Windows 95 or 98 PC. How do I configure INTELLIscribe to print to this type of printer?

First provide INTELLIscribe with the IP Address or Hostname of the printer and the "LPD Queue Name". On the Xerox DP65 printer, the default LPD queue name is 'dp65', but that is entirely configurable. To find the LPD queue names available on your printer, type "list virtual printers" on the printer console. You can also find the IP address from the console.

Note: You must use a print driver that is compatible with the printer, but also one that does not use the PostScript driver provided by Adobe. This driver invokes a dialog each time the system is booted and cannot be suppressed.

How do I print labels to a label printer, aka a thermal printer, from the AS/400?

There are two main keys to printing through RPM to a label printer from the AS/400. First, you must have a Windows print driver, and secondly, some specific settings need to be configured in the AS/400 OUTQ.

  1. First, download and install the print driver specific for your label printer. You may download many types of label printer drivers from Seagullscientific.com. Some drivers are available for a free download, and others may need to be purchased.  Add a new printer to Windows using the downloaded print driver. Assign it to the proper (COM or LPT) port. 
  2. Now modify the OUTQ on the AS/400.
    • End the writer by issuing the following command: ENDWTR outq_name *IMMED. Then press ENTER. Wait for the writer to end. This should take less than 15 seconds.
    • Now, edit the OUTQ by issuing the following command: CHGOUTQ outq_name. Press F4 to prompt, do not press ENTER. Then press F24, F9 to display all parameters.
    • Page down until you find the "Host Print Transform" parameter. Verify that it is set to: *YES. If not, please change it now. Do not press ENTER yet!
    • Find the "Manufacturer type and model" parameter. Enter the following for this parameter: *WSCST.
    • Now find the "Workstation customizing object" parameter. Enter the following option: QWPDEFAULT. Do not enter an asterisk (*) before the option. Do not press ENTER yet!
    • Finally set the "Library" parameter under the "Workstation customizing object" to the following: *LIBL.
    • Now you may press ENTER. If the "Writers to autostart" parameter is set to greater than zero, the writer for this OUTQ will start automatically. If not, you must enter the following command to start the writer: STRRMTWTR outq_name. Press ENTER again.

Note that QWPDEFAULT will not be available until you have set your Manufacturer type and model to *WSCST.

Your OUTQ should now be configured properly to print to your thermal label printer.

Provided by Tom Prosser with SpecTran.

How do I disable banner pages?

RFC 1179 says that the client passes information to the server (e.g. RPM Remote Print Manager®) that specifies the name that is to appear on the banner page. You are *supposed* to treat this as a command to create a banner page.

Note that the Unix client does this unless you tell it not to, with the "-h" switch.

When RPM is printing text, it will make a banner page using the normal convention as explained above. You can tell RPM not to print a banner page by going to Queue Setup and setting "Never print the banner page".

When RPM is printing raw or pass-through, RPM will print a banner page only when the control file designates.

Sometimes when we're asked about not printing the banner page, they are referring to a banner page created by an application on the remote system. The way around that is this:

  1. Hold the queue.
  2. When the job is received, double click on the job. This opens the "Operator Job Control" dialog. The field "Start print on page" contains the value "1". Change this to "2".
  3. The setting "Hold (set ON to print later)" will be selected. Click this setting to release the job.

For RPM 5.0 and newer you can use the "Remove Until" transform to remove up to the first line of text, beyond the banner page, or the "Remove Lines" transform to remove a specific number of lines from the front of your file.

What steps should I perform on my firewall to enable RPM to receive print jobs from a system that is outside the firewall, perhaps from the Internet or WAN connection?

To answer this question you will need to know how your firewall is configured, and which protocol you will be using to print.

Firewall: NAT

If your firewall is performing Network Address Translation (NAT), you will configure port forwarding on your firewall.

  • If you are using the LPR/LPD protocol, and your firewall is performing NAT, you will forward traffic coming in on port 515 to the internal IP address of the RPM host.
  • If you are using streams and your firewall is performing NAT you will forward traffic on whichever port you configured on the sending side (e.g. 9100) to the internal IP address of the RPM host.

Firewall: not NAT

If your firewall is not performing NAT, you will simply allow data to go through your firewall. This is called relaxing a port.

  • If you are using the LPR/LPD protocol, you will relax port 515 on your firewall.
  • If you are using streams printing, you will relax the appropriate port number. The port number you relax will depend on how your printer is configured on the sending side; typically, it will be in the range of 9100-9200, but could be any port number between 1 and 65535.

Note: Streams printing may be referred to as any of the following: Socket Printing, Reverse Telnet, or Telnet Printing.

Note: Your firewall may require you to supply the type of connection; both LPR/LPD and streams printing are TCP connections, not UDP.

How do I set an RPM Remote Print Manager® queue to print to a specific Windows Printer?

For RPM 5.0 and later:

  1. Open the Queue Setup panel
  2. Select the queue in the queue list
  3. Select the action with the printer you want to change (Text print and Raw print actions work the same way in this regard)
  4. Click the Modify button to the right of the actions list
  5. Select a new printer. For Text print actions you can select printer settings in this dialog.
  6. Click Save when done.

For RPM 4.5 and prior:

  1. From the "Queues" menu, choose "Edit Queues".
  2. From the "Queue" drop-down list, choose the queue you want to select a printer for.
  3. Now, if the queue type is Text print, press the "Printer Setup" button.
  4. In the "Printer Setup" dialog, choose the printer you want this queue to print to from the "Printers" drop-down list.

Note: From this same dialog, you may also identify the page orientation and paper size by pressing the "Properties" button.

How do I grant the Logon as a batch job privilege to my user account?

Setting up 'Logon as Batch Job'

Answer: On Windows, this privilege is granted through the Local or Domain Security Policy. To do this using the Local Security Policy, follow these steps.

  1. In the Control Panel, open Administrative Tools, then Local Security Policy.
  2. Beneath Security Settings, open Local Policies and highlight User Rights Assignment.
  3. Locate Log on as a batch job. Open the properties and add any users that need this right.
  4. When finished, save your changes and close the Local Security Settings window.

Your changes should take effect immediately. To make changes to the Domain Security Policy, on a domain controller, use the Domain Security Policy utility in the Control Panel.

Why RPM Remote Print Manager needs 'Logon as Batch Job'

RPM Remote Print Manager uses Logon as Batch Job

Our RPM product has the ability to process print jobs as a specific Windows user. As you well know, sometimes the permissions make this necessary; for instance, if you want to

  • write to a shared folder
  • print a shared printer
  • run a program interactively.

This is the reason we researched this topic in the first place, and we are pleased to make this page available to you. Obviously, helping our users is what makes us all successful, and we're happy to share the information with the community.

If you need a great print server or virtual printer, please download the free trial today! And best of luck with your "logon as batch" issues from here on out.

How do I determine the characters-per-inch and lines-per-inch settings to use in a "Text" type queue?

Characters-per-inch may be calculated using the following formula(s):

  • CPI = Number of Characters in a line to be printed / Printable Width, or
  • CPI = Characters / Paper Width - (left margin + right margin)

Lines-per-inch may be calculated using the following formula(s):

  • LPI = Number of Lines to be printed on a page / Printable Width, or
  • LPI = Lines per page / Paper height - (top margin + bottom margin)

Examples:

  1. I am printing on letter size paper, landscape. I want 60 lines on each page, and there are 132 characters on each line. I've set the margins to 1/2 inch on all: top, bottom, left, and right.
    • CPI = 132 / (11 - (0.5 + 0.5)) = 13.20
    • LPI = 60 / (8.5 - (0.5 + 0.5)) = 8
  2. Printing again on letter size paper, portrait this time. I want 80 lines on each page, and there are 92 characters on each line. I've set the margins to .75 inches on top and bottom margins, 0.5 inches on the left and right margins.
    • CPI = 92 / (8.5 - (0.5 + 0.5)) = 12.2
    • LPI = 80 / (11 - (0.75 + 0.75)) = 7.6

I am trying to print jobs to a low-cost inkjet printer. Using a Raw printer action, the RPM Remote Print Manager® (RPM) log indicates the job has been printed, but nothing is printed to the physical printer. What can I do to resolve this problem?

To save on cost, most inkjet printers do not have any internal processing power, but instead rely on Windows and the driver for all processing. These printers cannot print even a plain text document unless the application uses the Windows print driver.

The purpose of the Raw print action is to bypass the print driver altogether. This requires the printer be supported by the sending system. Low-cost inkjet printers rarely, if ever, support any operating system other than Windows.

Luckily, RPM's text printing functionality can resolve this problem. If the incoming data is plain text, use a Text markup transform and a Text print action to print these jobs to any printer with a supported Windows driver.

If the incoming data is PostScript, see the section titled Print Postscript to a non-Postscript printer in this FAQ.

I can't print over 132 columns in my print jobs, although I set 150 characters-per-line.

RPM Remote Print Manager® (RPM) has two ways to set the horizontal size of the font. One is Use characters per inch and the other is Fit columns per line.

  1. From the RPM user interface, choose Edit Queues from the Queues menu.
  2. In the Edit Queues dialog, verify Select a queue lists the queue you wish to modify and that you have select the Print text, allows font selection, page setup queue type. Open the Text Setup dialog by clicking the Queue Setup button.
  3. Do one of the following:
    • Check Use characters per inch and fill in the chars/inch edit box. This page explains how to determine the number of characters per inch
    • Select Fit columns per line and enter the correct number of columns in the columns field.

Note: For best results, we suggest selecting a TrueType font such as Courier New. In the Font dialog, look for a TrueType icon beside the font name. The other type is a bitmapped, or system font, represented by the following icon: .

If your print job is a report or other document that lists data in columns, a fixed-width font should be used. It is important that the white-space (0x20) character is the same width as other printable characters. Courier New and Letter Gothic MT are the most common fixed-width fonts. Both Arial and Times New Roman are variable-width fonts.

Category: 

Is it possible to allow RPM to print to more than this number of printers?

RPM Select 4.5 and prior is limited to 24 printers; RPM Select 5.0 is limited to 10 devices. If you have RPM Select and wish to print to additional printers, please contact us about converting your license to RPM Elite. RPM Elite has 3 options for device limits: 99, 249, and Unlimited Devices

Here are the steps to increase the RPM Elite printer limit above 99.

  1. Open the Brooks License Manager in the RPM Program group or choose License from the software's Help menu.
  2. Open the Module Status tab and double-click RPM Printers. Follow the wizard selecting Internet activation option.
  3. Enter your invoice or sales receipt number, the auth code you were provided, and the number of printers you purchased and click Next.
  4. A success dialog will appear if your activation was successful.

Note: If you purchase an unlimited printer license for RPM Elite, enter 0 (zero) for quantity. Zero means "no limit".

I am printing to RPM from an AS/400. When I specify a page range on the spool file, the entire document prints anyway. Is there any way for RPM to honor the page range setting on the AS/400?

The problem is not with RPM, but with the AS/400. Specifically, remote OUTQs do not limit the pages to the specified page range, only standard OUTQs and devices.

Basically, the AS/400 knows what you want but is not telling RPM (or any other 3rd party LPD product).

IBM provides a program with source that will allow a user to specify a page range printed or sent via RMTOUTQs that are configured with a connection type of *IP or using the LPR or SNDTCPSPLF commands. The program is called TSPRWPR and details can be found on the IBM website. Or, perform a web search for the program name "TSPRWPR" which should locate the IBM document.

When using a filter queue to call Acrobat Distiller, the first job is distilled properly. Subsequent jobs fail to be opened in Distiller and stay in RPM in a Wait state.

A new feature introduced in version 5.0, and has been available in all versions since, has an option to forcibly close a filter program launched by RPM after a configurable idle timeout period. By default, the program will be closed if it has been idle for ten seconds. Because RPM ensures the program must be idle for that amount of time before closing it, the value can be set to a much lower threshold safely.  We had an Adobe program in mind when we added this.

Acrobat Distiller has some command line switches that were either not available or not required in previous Distiller versions. Distiller should be called similar to the following example:

	x:\path\to\acrodist.exe /N /Q filename
  • The /N option tells Distiller to start a new instance which assures that it will be started fresh and will not try to wait for previous Distiller instances to finish processing.
  • The /Q option is supposed to cause Distiller to quit when it is finished processing a file, though it will not close if it is the only remaining instance of Distiller.

For more command line switches in Distiller, refer to www.adobe.com.

We have installed RPM on a Windows Server 2003 operating system. When printing to a locally attached printer, everything is fine. When the printer is shared from another Windows PC, a message is logged that reads, in part, access is denied.

Microsoft recommends that vendors support login credentials as the preferred way to get access to a shared resource, from a Windows service. This is why RPM Remote Print Manager® offers optional credentials for any action that uses a printer, folder or file path.

To assign user credentials to a device, in the action settings dialog (for whatever action you are using) locate the Credentials field in the dialog and click the Update button, then enter your domain, user and password where indicated.

We have an extensive discussion on printing to shared printers on this page.

Licensing (3)

Will RPM run in a cluster environment and is it a cluster-aware application?

RPM runs fine in a cluster environment, but it is not cluster aware. Because RPM is licensed per computer, a separate license is required for each redundant server.

How can RPM be used in a fail-safe way with the licensing model?

The Brooks License Manager generates a serial number during installation based on the MAC address of the first network device. The MAC address is obtained using the SNMP protocol. This method ensures that the serial number is unique because MAC addresses are also unique.

Each time the RPM Remote Print Manager® (RPM) service is started, the serial number is verified against the MAC address of the current network device. If there is any discrepancy, the license expires (is set to a trial with 0 days remaining). In order for the new serial number to function, it must be reactivated.

If a hardware failure causes the license to expire, an uninstall and reinstall must be performed to allow the trial license to be used in production within the printer limit of the trial. Contact us to reset your license so it can be activated again.

Solution: We advise exporting the current RPM configuration to a safe place and keeping a copy of the latest install as backup procedure. If there is a failure, a new system or the repaired system, can be placed into production quickly. The license will need to be activated to have the full printer limit supported.

When a fail-safe backup plan is required, we recommend an extra license be purchased. If your server is down, and you cannot contact us, then you can license your backup RPM until we can be reached. Once we are reached, we can deactivate your backup license and it is available next time you need it. This is a low-cost way of ASSURING your RPM production license will always be up and running.

Category: 

I have reinstalled RPM on a different computer as the one originally had RPM crashed. When I attempt activation, it states "all available licenses are already unlocked."

For customers who have current Software Upgrade & Maintenance (SUM), an After Hours Licensing solution is available in emergency or disaster recovery situations when the regular trial version is not sufficient to meet your needs. This solution is available for RPM Elite and Select only and provides a five day trial version allowing the same number of printers as if the activation has been completed. The software can then be activated at your convenience when our normal business hours resume.

Click here to access the 5-day trial version. Please note that this service is no longer available. The possibility for abuse from certain users ended up being a large enough problem that we decided to discontinue this option.

Category: 

Printing (48)

Will RPM Remote Print Manager® support network printers?

RPM version 6 and beyond have IP Print and LPR Print actions which support network printers directly.

When RPM receives more than one print job at a time, which one will print first? r-11221 Sue

The default for RPM it to process the data on a first in, first out (FIFO) basis. The first print job that RPM completely receives is the first job that will print out.

Let me describe a scenario that will provide a better picture. Let's say you send 2 jobs to RPM, one immediately after another. The first file you send is 60MB, and the second is a 3MB file. It is very possible that even though RPM started receiving the larger file first, it will probably print the small file first because that is the one RPM finishes receiving first.

In RPM Elite Version 6 new scheduling options are available with allow more control on processing order. These include Balanced, By Job ID, FIFO, and Priority Scheduling which allows user controlled priority settings.

When I print, I get a stair step effect.

The reason for this is your Host (e.g. a UNIX system) uses LF as the end of line character and the printer is expecting CR/LF.

For RPM 6.0: add the "Unix to DOS" transform to the setup for this queue.

For RPM 5.0: add the "LF to CRLF" transform to the setup for this queue. Typically it would go at the beginning of the transform list, or just following a code page (data format translation) step.

For RPM 4.5 and prior: this is generally associated with a "RAW" type Queue. To Translate the LF to CR/LF do the following:

  1. Verify the Queue type is RAW
  2. Select the Queue Setup in the Edit Queues Window.
  3. Select Translate LF to CR/LF.

What types of printers does RPM Remote Print Manager® support?

RPM supports all printers that Microsoft Windows supports. If your printer has a Windows "print driver", then RPM can print to the printer.

Note: Some older dot matrix printers may be supported with the "Generic/Text only" driver.

Category: 

Printer limit exceeded for queue xxxx, printer 'yyyy' (in the RPM Remote Print Manager® Log).

You will see this message when you have exceeded the number of allowed printers that your copy of RPM supports. The Trial version of RPM supports printing to any two printers connections in a single session. The Select version of RPM supports up to 10 printers connections in a single session. Unlimited printer connections may be purchased by contacting Brooks Internet Software.

IPDS print jobs are not being separated properly when printing through ExcelliPrint.

IPDS is a page-based protocol. ExcelliPrint never receives any information about when a print job starts or ends as it is not supplied by the host system.

The Print Services Facility (PSF) provides a method to separate the print job into separate files. On IBM mainframes, the JES parameter is CKPTPAGE. On the iSeries, the PSFCFG option is Acknowledgment frequency (ACKFRQ).

ExcelliPrint will create a new job or file if the number of pages in the spool file exceeds this setting. PSF supports a maximum of 32767 in this parameter.

For example, if you set this parameter to 100 and the print job is only 25 pages, the job will be split at page 25 successfully. If the number of pages in the next print job is 120, ExcelliPrint will separate the first 100 pages into one print job and the last 20 pages in a new print job.

The host system also uses this setting when handling problems.

  • If you have a 60,000 page print job, and you set this parameter to 32767, ExcelliPrint will create only two separate print jobs. If an error occurs on page 60,000, the host system must resend all pages from 32,768 through 60,000 again.
  • If 10 was configured in the CKPTPAGE parameter, ExcelliPrint would separate the job into 6,000 smaller print jobs. If an error occured on page 60,000, the host system would need to resend only pages 59,991 through 60,000, significantly reducing the amount of recovery time and host system processor utilization.

Setting this parameter to a low value will cause slower printing.

We suggest testing this to find the value that works best in your environment.

There is no page between jobs.

This is a factor for raw printing. Text printing separates documents courtesy the Windows print drivers.

RPM offers several banner types as well as a PCL page seperator. It also supports insert and append byte strings as described below. These would be configured as transforms in the queue setup.

We are using DHCP and DNS or a dialup connection and would like to print data from an AS/400 to a PC. How can I configure the AS/400 so I can print to a computer with a dynamic IP address?

One of our clients provided the following CL program. We are providing it for your consideration. As you can see, this program does the following:

  1. Prompts the user for the name of the OUTQ (printer) they want to use
  2. Automatically obtains their IP Address.
  3. Notifies the user that the OUTQ's IP address is being updated.
  4. Updates the OUTQ they provided with their IP address.
  5. Prompts them to update another OUTQ.

The CL program may be used and modified for your needs. It is possible to modify the program to eliminate all user interaction and automatically update the proper OUTQ on the AS/400. This program should be placed in the user's profile and run when the user logs in.

Download the CL program in a PDF document

This document is our best approximation of the correct tab and structure. We are currently unable to provide anything more accurate than this but no doubt an RPG programmer can make sense of it.

How do I setup the AS/400 for A4 paper size?

If you have not changed the page size of the PRTF, it is still 132 66. The Host Print Transform looks at this value and translates it into the escape sequence requesting that the paper at the printer be 13.2"x 11." Paper. It is not possible with some printers so they are not including in the transform - normally you would default to PPRSRC1 parameter; but, if you are using RMTOUTQ there is no DEVD. It must send something so it requests LETTER rather than A4.

To fix you can change the PRTF so that it has a PAGESIZE that reflects A4 or you can edit the transform. We suggest you look at the Rebook IV if you have it. The basic principle is to RTVWSCST *TRANSFORM *HP4 <specify a PF to retrieve into>. Then use SEU to edit this file and either create another PAGESIZE tag for 13.2" x 11" or change the one for letter.

To change the entry for letter:..

  • PAGSIZE
  • PAGWTH=12240
  • PAGLEN=15840 (these are the size of the page in 1/1440ths of an inch)
  • Data='1B266C303241'X

Change this to

  • Data='1B266C323641'X

What you are doing is sending the escape sequence for A4 rather than letter sized paper. Save this and then CRTWSCST. Add this into the RMTOUTQ under WSCST.

I need RPM Remote Print Manager® to be able to retain each print job for a specified amount of time in order to reprint later if necessary. Does RPM currently have this ability?

Yes! In the Job panel in the GUI, you can set the Job Archive settings and specify how long jobs are retained for reprint. You can specify a time limit or number of jobs to retain.

Category: 

RPM Remote Print Manager® is taking a long time to print.

RPM receives and passes the file to your printer quickly. The time frame from the print job being sent to RPM from the host system (e.g. AS/400, Unix, etc.) until the print job is printed can be evaluated with the following steps to determine where the bottleneck is:

Problem 1: Evaluating time to send to RPM

First, suspend the RPM queue (at the menu select Queues, Resume/Suspend). Then send the file from the host (e.g. AS/400, Unix, etc.). Note the time from release at the host until the RPM queue status states "DONE". If it takes a long period of time for RPM to receive the job, the problem is probably associated with processing on the host system.

Resolution 1: Time to send Resolution 

RPM has been used to improve print job performance significantly by performing EBCDIC or SCS transforms rather than have the host do the transformation. To use RPM to transform, set the Print Data Options in RPM to do this transform and set the host to not transform. Now, re-send the print job from the host and note the reduction in the time for RPM to receive the print job.

If your host is not performing a translation, the bottleneck is with your network architecture. You should contact your network administrator for a resolution.

Problem 2: Evaluating time to print from RPM

If the above evaluation did not identify the problem, release the RPM queue (at the menu select Queues, Resume/Suspend) and note the time from release until the job completes printing. If it seems to take a long time for the job to begin printing, the problem could be the spool settings on your PC.

Resolution 2: Time to print from RPM resolution 

Set your spool settings (Start/Setting/Printer - right click on the printer you are sending to, and select Properties/Details/Spool Settings) to "Print directly to printer" and "disable bi-directional support." Now suspend the RPM queue, re-send the print job from the host, release the RPM queue and note the reduction in time to send the print job to the printer.

If this did not reduce the time for the print job to begin printing, here are other considerations:

  • The problem could be with the type of print driver you are using. If you are using a print driver from the manufacturer versus the Windows "box" driver (the driver that ships with Windows), try setting up the printer with the Windows box driver.
  • If RPM is performing formatting, you may change the queue type from TEXT to RAW and perform the "time to print from RPM evaluation" again. If this results in a significantly lower time for the print job to begin printing, you may choose to have your host system do the formatting and send the print job to a RAW type queue. Retry the steps above until you get the combination that works best for you.
  • If this does not improve your time to print, you should consider upgrading the PC that RPM is running on. Because the print job you are formatting will be processed faster on a more powerful PC.

RPM prints differently than another printer that is receiving print jobs directly from the AS/400.

Here are the most likely causes of this problem.

  1. If RPM is configured using a text type queue, any AS/400 formatting will be stripped and the file reformatted using the Windows print driver, as well as the settings configured in RPM. Change the queue type to Pass data directly to the printer (raw) and try again. If the printers are identical, this will resolve the issue.
  2. The AS/400 OUTQ directed to RPM may be configured differently than the OUTQ going directly to the printer. Verify they are identically configured. You can also use CRTDUPOBJ command to copy one OUTQ to another identical OUTQ, changing only the name.
  3. Users may have an override print file (OVRPRTF) associated with their user profile. Override print files can change the file printing attributes. Try logging in as a different user, or removing any override print file associated with the current user, to determine whether or not this is the problem.

When I change my printer properties in RPM, they aren't used. I've tried to select a different tray, and also a different orientation, but neither seems to work properly. Am I doing something wrong?

If you are using a Text Print action in RPM Remote Print Manager®, these settings should all work just fine, as long as you have the correct driver loaded for the printer.

If you are using a Raw Print action, these settings make no difference. RPM's raw print actions send the data straight through to the printer without changing the file at all, including adding appropriate printer codes. This is the desired behavior and there is no way to make these settings work with this action type. If you need to print directly, you will need to configure your sending (LPR) system to format the data accordingly before RPM ever gets the data.

 I am printing from a SCO UNIX to RPM Remote Print Manager®. When I attempt to sent multiple files, a few print out, but it eventually hangs on about the 3rd or 4th print job.

This problem has been reported only with SCO UNIX, although it's possible if you're sending print jobs from systems with enhanced options. You will probably get a couple of messages in RPM that state:

  Error writing data to port 236 (0x2745):[10053] Software caused connection abort.
  Warning : Unrecognized control line -Onobanner.

In most cases, this problem will not occur if sending only one datafile over a connection. To fix the problem, you need to change your printer configuration on your SCO box to not use the option -o when sending to RPM.

When trying to print from INTELLIscribe to Linux, the Linux LPD accepts the entire print job, but does not print it. The job then disappears from the spooler. Unix logs the following errors:

	lp: illegal format character 'o'
	lp: job could not be printed

INTELLIscribe's Properties dialog states that the print job was successful.

INTELLIscribe, by default, specifies to the LPD print server that the data is in "postscript" format. If no Unix PostScript printers are available, or the queue receiving the print jobs is not configured for a PostScript printer, the job will not be printed by Unix.

The default works properly in most cases, however, some Unix LPD servers try to modify the data before printing it when following strict RFC1179 compliance.

You can configure INTELLIscribe to resolve this issue:

  1. From the Printers menu, choose Add or update virtual printer port.
  2. Click "Next" until the final step.
  3. Modify the "Print format" parameter to display "preformatted" by choosing this selection from the drop-down list.

I am trying print through RPM from my host system to an HP Laserjet 1000 printer. Both the text and raw type queues show that RPM successfully printed to the printer, the printer light blinks as though it is attempting to print, but nothing is printed. How can I print from RPM to the HP Laserjet 1000 printer?

The HP Laserjet 1000 series printers are host-based printers and do not support the PCL printer language typically supported by other HP Laserjet printers.

Other users have reported that RPM can successfully print to this printer using the HP Laserjet 1000 DOS driver. To locate this driver:

  1. Open your browser to the Hewlett Packard website
  2. Search the "download drivers and software" section for "laserjet 1000."
  3. From the list of available downloads, choose the HP LaserJet 1000 Printing Software Solution. Download and run the installation program, following the directions.
  4. Once the printer is installed, open the Printers and Faxes folder, right-click the HP Laserjet 1000 DOS printer and choose Properties. Open the Advanced tab, click the Print Processor button and verify that the Print Processor is set to ZPPPCL and the Default Data Type is RAW.
  5. Click OK on the Print Processor dialog to accept the changes and dismiss the dialog.
  6. On the HP Laserjet 1000 DOS Properties dialog, open the General tab and click the Print Test Page button. Verify that a Windows test page prints successfully to the printer. If not, contact your system administrator for assistance. Press Ok to save the changes and exit.
  7. Open RPM, double-click the queue that is printing to the HP Laserjet 1000 printer, press the Printer Setup button, and select the new printer you installed. Repeat this step for each queue that is printing to the printer.

Can INTELLIscribe be used to print from a Windows computer to a Unix computer running IBM AIX?

Yes, INTELLIscribe can print to IBM running AIX. Please check the following settings:

  1. The INTELLIscribe host must be listed in /etc/hosts.lpd file.
  2. A plus sign (+) must also be added to the /etc/hosts.lpd file at the end.
  3. The virtual printer port must be configured correctly:

LPD Queue Name: <same as AIX queue name>

Relax Port Restr: no

Note: The "print format" parameter should be "postscript" if the printer supports it or "preformatted" if not.

How do I print to a Tektronix Phaser 560 using INTELLIscribe?

First, the installation instructions for the network card on this printer state that the LPD queue name of "AUTO" or "PS" must be used, all upper case. Quoting from the TEK web site:

  • [For the Name or address of host providing LPD: enter the printer IP Address. For the name of printer on the machine: type AUTO or PS in all UPPERCASE letters (lowercase letters will not work).]

Second, the "Tektronics Phaser 560 Extended," should use the PSCRIPT.DRV "box" driver, which comes with Windows95/98 rather than a driver (e.g. "ADOBEPS4.DRV") from some vendor-supplied media.

Our recommendation to resolve this would be to first delete the Tektronics printer from the Settings/Printers window, and then to reinstall the same printer using the box driver (i.e. just the dialog that pops up when you click Add printer). This should reinstall the driver so that it does not use a language monitor. Should the problem still appear, then you need to edit the registry. Follow these steps to edit the registry:

  1. Choose Start\Run. In the text box, type "Regedit". Then press OK.
  2. Open the "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Environments\Windows 4.0\Drivers\Tektronix Phaser 560 Extended" key
  3. Determine what print driver is being used (e.g. "ADOBEPS4.DRV" or "PSCRIPT.DRV)
  4. Finally, change all the entries which read "ADOBEPS4.DRV" to "PSCRIPT.DRV".

Note: This assumes you have previously installed a PostScript printer, which you can check for by searching in that vicinity of the registry for the "PSCRIPT.DRV" string. If you cannot find it, then just install any PostScript   printer (e.g. Lexmark Optra S PS, HP LaserJet 4  PostScript , etc.) and then delete the printer, selecting "no" at the prompt to delete driver files.

How do I print to my Apple LaserWriter 16/600 using INTELLIscribe?

Set up the virtual printer:

  1. Choose a name
  2. Enter the IP address
  3. Select LPR/LPD
  4. Select Port 515
  5. Select "Add Destination"
  6. Select "Next."

The "LPD Queue Name" entry is specific to the LaserWriter 16/600, which uses the queue name to determine how to handle the end-of-line character. Normally, "raw" is the correct queue name to use. Using "raw" as the queue name in INTELLIscribe should not add any special control characters to the document, as is appropriate for PostScript and PCL5 print jobs.

However, if each new line of text starts where the previous one left off, creating a stairstep effect, then use "text" as the queue name. The reason for this is normally that your host (e.g. UNIX a system) uses LF as the end of line character and the LaserWriter is expecting CRLF. Selecting "text" as the queue name will append a carriage return to the end of each line in the document as it is printed.

I'm having trouble printing through INTELLIscribe to an Epilog Legend Engraver. Some problems are as folows:

  • The status window shows "submitted" or "started", but the job never prints
  • A message stating "List index out of bounds(0)" is received
  • The job prints but says "Failed" in the status window
  • A job prints over and over again 

These steps should resolve most issues when spooling print jobs to Epilog Legend Engravers:

  1. Upgrade to the latest version of INTELLIscribe. This can be downloaded here.
  2. In the virtual printer port wizard, configure the "Relax port restr" parameter to "no".
  3. In the virtual printer port wizard, configure the "Data File Ack" parameter to "no".
  4. In the virtual printer port wizard, configure the "LPD queue name" parameter to "Legend".

If the problems are still not solved, verify that your TCP/IP network configuration is correct. If you already have a network at your location, contact your system administrator for help on configuring your engraver and PC correctly.

If you are in an environment with only a single PC and an engraver, verify the following:

Your engraver and PC must have a different IP address

The default IP address for Epilog Engravers is 192.168.98.1 and the subnet mask is 255.255.255.0. You must configure the computer's IP address to be similar (on the same network of 192.168.98), but not identical. We suggest setting it to 192.168.98.2 and subnet mask the same 255.255.255.0. Once this is accomplished and the computer is restarted, try pinging the engraver with the command

	ping 192.168.98.1

If you receive 4 replies to your ping, then your configuration is correct.

If you are connecting through a network hub

Verify that your network cables are "straight through" cables. Straight through cables should be used in this instance because cross-over is accomplished by the hub.

If you are connecting directly to the Engraver from the PC

Verify that your network cable is a "cross-over" cable. Cross over cables are used in this instance to provide the network proper "listening" and "talking" wires.

How can I create a printer on the Solaris server to print to my queue in RPM?

The steps below will help you configure a printer on Solaris version 2.51 to print through RPM.

  1. At the console, open Admintool.
  2. Open the Printers utility.
  3. From the Edit menu, point to Add and choose Access to Printer.
  4. The following options should be configured.
  • Client: Enter the IP address or hostname of the Solaris server.
  • Printer name: Enter the RPM queue name here.
  • Print Server: Enter the RPM host computer's IP address (or hostname if using DHCP).

I need to send IPDS print jobs to a specific source drawer (paper input tray) on my printer. How do I know on which tray the job will be printed?

You need to know the following three things.

  1. Which tray you want to print to
  2. What PCL command your printer uses for that tray
  3. The source drawer specified in the IPDS file on your host system

ExcelliPrint takes the source drawer specified by the host system and converts it to a PCL escape sequence.

  • If source = 1 use PCL command <Esc>&l1H
  • source = 2 PCL command = <Esc>&l4H
  • source = 3 PCL command = <Esc>&l5H
  • source = 4 PCL command = <Esc>&l8H
  • source = 5 PCL command = <Esc>&l9H
  • source = 6 PCL command = <Esc>&l10H
  • source = Envelope (65) PCL command = <Esc>&l6H
  • source = Manual (33) PCL command = <Esc>&l2H
  • source = Manual Envelope (96) PCL command = <Esc>&l3H

Note: To print to a different tray, you must change the IPDS print job on the host system. Changing ExcelliPrint settings will not change the tray from which the job is printed.

When pressing the "Printer Setup" button to select a printer on a newly created queue, an hourglass cursor appears for a second then goes away. The Print Setup dialog never appears.

The reason that new queues cannot access the Print Setup dialog is that the operating system is blocking it due to a connection problem with the default printer.

Try changing the default printer to be a local printer. This is done from the Windows Printers folder.

  1. Open Start->Settings->Printers.
  2. Right-click on a printer and choose "Set as default".
  3. Now try accessing the Print Setup dialog from RPM.

If the Print Setup dialog still does not appear, repeat the above process until it does. This problem is caused by the operating system and not by RPM. Typically, your default printer should be a "local" printer, meaning one connected to LPTx or COMx ports, or other ports such as the LPR port, JetDirect port, etc. A shared printer, such as \\Server\Printer, can cause problems with other applicat