RPM Remote Print Manager® 188.8.131.525 was released on July 5, 2023. We consider this an official, supported release and urge users with any issues included in those below to install this on a test system and evaluate it in your environment.
The RPM Roadmap includes a summary of these release notes.
An expanded version of the notes from the Roadmap follows.
Library causes issues
One of the libraries we've used for years has apparently started failing. Users would show error messages, which we ultimately traced to progress on job processing being interrupted at unexpected places.
Control file issues:
Many dialogs include a control called "Name template" where you can use values from the print job to construct a file name, perhaps the job ID or day of the week it's created. There were issues using some control file lines in this template. That is now fixed.
A few of the more obscure, rarely seen, control file lines were not making it into the database. This is now fixed.
Some control file lines contain an integer, and when this integer was extremely long, the operation faulted. This is now fixed.
Filter actions were not behaving consistently when stdin was off.
The Hewlett-Packard PCL manual said that tray identifiers could not be over 39, but apparently, they are. This is now allowed.
The user interface now displays "Unlimited" for "unlimited devices" (this is one of the RPM Elite editions) rather than a huge integer (2**32)
RPM sometimes would not stop processing when instructed to shut down. We removed some unnecessary items from the shutdown logic, and this now
We see occasional critical event reports regarding "Error 0" on file write operations. This is meaningless and baffling, for instance, why signal an error if there is none? We've done some work to correct that using some of the mainstream AI chatbots (they are supposed to be good at programming issues). Time will tell.
The Queue Folders module now ignores zero-length files. The other input protocols already do. The challenging thing with Queue Folders is that it often deals with newly created files. We give files a couple of seconds in the hopes that all the data written to it will actually show up by the time we move that file into our space.