About printer emulations for AppSocket

The AppSocket module in RPM Remote Print Manager® ("RPM") provides query/response similar to what a print application could expect from a JetDirect printer.

To do this, the RPM user interface launches a utility that establishes a connection with your JetDirect printer and performs the following queries:

@PJL INFO ID
@PJL INFO CONFIG
@PJL INFO MEMORY
@PJL INFO PAGECOUNT
@PJL INFO STATUS
@PJL INFO VARIABLES
@PJL INFO USTATUS

The purpose of this is so that your JetDirect print client application can query RPM in place of your printer and get realistic results, identical to or very close to what the client expects.

We also found that most status readback results relied on data returned from these queries.

The utility composes the query results from the printer into a file stored in a PRINTERS folder alongside the RPM jobs and other data. RPM can then respond to queries authentically. RPM does not try to control or alter the PJL in the print job, although you can do that with the string translator.

Please note that the AppSocket protocol configuration form includes a field for the serial number, so you can keep the information private if you wish. The value for the ID field is what we use to display printer emulations.