Using OM Plus Version 1.6.6.

Any suggestions would be appreciated

Forum: OM Plus - Q&A ]]> http://plustechnologies.websitetoolbox.com/post?id=4579923 Wed, 10 Feb 2010 19:55:53 GMT http://plustechnologies.websitetoolbox.com/post?id=3763932

• Lexmark C736 (SPR only)
• Lexmark T654dn
• Lexmark T654dtn
• Lexmark T654n
• Lexmark T656dtn e-Task single function printer
• Lexmark X464de
• Lexmark X466de
• Lexmark X466dte
• Lexmark X466dwe
• Lexmark X632e
• Lexmark X644e
• Lexmark X646dte
• Lexmark X646e
• Lexmark X652de
• Lexmark X654de
• Lexmark X656de
• Lexmark X658de
• Lexmark X734de
• Lexmark X736de
• Lexmark X738de
• Lexmark X750e
• Lexmark X752e
• Lexmark X762e
• Lexmark X772e
• Lexmark X782e
• Lexmark X782e XL
• Lexmark X820e
• Lexmark X832e
• Lexmark X850e
• Lexmark X852e
• Lexmark X854e
• Lexmark X860 - New e-Task Multi-Function Printer
• Lexmark X912e
• Lexmark X940e
• Lexmark X945e

Forum: OM Plus - Q&A ]]> http://plustechnologies.websitetoolbox.com/post?id=3763932 Tue, 27 Oct 2009 22:43:55 GMT http://plustechnologies.websitetoolbox.com/post?id=3687894 The term host-based printer (sometimes referred to as GDI printer) is a printer that relies on the computer's processor to rasterize the print job, rather than their own formatter board and the processor and circuitry on it.

Forum: OM Plus - Q&A ]]> http://plustechnologies.websitetoolbox.com/post?id=3687894 Mon, 28 Sep 2009 20:15:08 GMT http://plustechnologies.websitetoolbox.com/post?id=3553797 Creating a High Availability Print Server Environment with OM Plus and Clusters

In many environments, data printed on a page runs a business process. From picking and shipping an order to distributing medication, it has never been more vital to have a 100% guarantee that a page printed; and in a timely manner.

In looking at the issues associated with guaranteed print, you have to first look at general points of failure. In the centralized print environment, the largest point is the print server itself.

To shore up this point of failure, IT professionals look to the common High Availability (“HA”) environment of “Server Clusters”. This environment is a tried and accepted method of providing uptime in the event of a server going down.

While the exact details of configuring OMP will vary depending on the OS and cluster software, the general method will remain the same.

In general the OM Plus software will be installed on each node of the cluster, but each install will be to the common disk that comprises part of the Cluster; a SAN or NAS disk being the most common. This will set the working environment for each Node, but ensure that all working files, including the spooled print files, are not co-located with the server.

Diagram 1.


With this configuration, in the event that a node goes down for any reason, a secondary node can be brought up. With OM Plus configured for Cluster use and the Queues configured for bi-directional communication, all jobs will then pick up where they left off.

In this environment, end users should only notice a small pause in printing while the failure is detected and the secondary Node picks up.

This method of HA is highly effective with the only possibility of job loss coming from jobs not finished spooling at the time the primary node goes down.

A common variance in the configuration is to add a Load Balance (“LB”) element to the mix. While it would seem logical to simply have both nodes Active and processing, this is not necessarily load balancing. OMP, while being installed on both Nodes, are running out of the same directory, so is, by definition, the same instance. While this is not feasible, this is not to say there is not a configuration that is both HA and LB.

A common configuration is to add an OMP Agent to the Application end that will check “Round Robin” prints to each node; each node being installed into separate directories so they are then two instances. This will insure that jobs are split between nodes and if any node is offline then all jobs will route to the healthy node.

Whether the OS is Windows or a UNIX/LINUX flavor, Plus Technologies can add guidance in choosing and configuring the correct environment to meet the exact needs to keep any business process running smoothly.

Forum: OM Plus - Q&A ]]> http://plustechnologies.websitetoolbox.com/post?id=3553797 Thu, 02 Jul 2009 15:25:17 GMT http://plustechnologies.websitetoolbox.com/post?id=3018939 2.3.5.0519 - February, 2010

Enhancement: A version of OM Plus that runs on 64-bit Windows operating systems is now available. Most OM Plus programs run under the 32-bit “Windows-on-Windows” environment; the port monitor and programs that setup and maintain the port monitor need to run in the 64-bit environment.

OM Plus will now operate correctly on Windows Vista or 2008 server when run under elevated authorization. For command-line programs, this means running at an “elevated” command-prompt; or processes that execute them must be elevated. The Start Menu “OM Plus for Windows” option will be linked to a wrapper program that requires this elevated level to run the main server gui. New documentation under the help directory gives more information.
IIS Note: we have no automated OM Plus web setup for Vista; however, the setup/removal scripts used for Windows 2003 will also work for Windows 2008 (and have been renamed from OMP_W2K3_IIS to OMP_WinServer_IIS) if (1) The IIS 6 Management Capability is installed as part of the IIS installation; and (2) the script is run with elevated authorization.
Enhancement: New SAP Call Back Integration will now display current printer status in SAP Status Screen.
Enhancement: Added  the following command line programs:
dccmount
omqdepth
omresolve
Enhancement: Added ability for user to change log-in password;
Enhancement: System info now reports exact version of Windows operating system;
Enhancement: Added proxy host operation to remote destinations; added checkbox to control ‘proxyMode’ on the Remote Hosts Lists tab of the Settings dialog from the main server gui Environment  tab.
Enhancement: A number of queue item values were not available to spooler.bat as environment variables; this has been corrected;
Behavior Change: Implemented “remote hold” option for OMPLUS and LPPLUS modes;
Behavior Change: The message reporting unsupported –o options is no longer logged.
Behavior Change: In background status, changed which user field was in play for filtering on user names.
Behavior Change: The scheduler code did not account for unexpected error codes (e.g. when a filter crashes). This causes unpredictable downstream effects, as when the exit code is put into a too-small character buffer. The termination logic now adjusts and logs the occurrence of such exit codes.
Behavior Change: If the scheduler detected a data error when loading a job initially from dcclp, it didn't communicate this back, so dcclp would wait until it timed out and would not report the true cause. Now, dcclp is made aware that there is a data error and everything is logged appropriately.
Bug Fix: Corrected incorrect host name in the web interface login.
Bug Fix: Changed socket shutdown sequence to prevent services hanging when stopped.
Bug Fix: Some SNMP status messages were being reported as “??” instead of true message. This has been fixed.

2.2.2.0459 - August, 2009
Enhancement: Compatibility for RightFax versions greater than 8.5. RightFax setup can be found in the OMP for Windows Configuration screen . Environment tab > Settings button and then RightFax setup. (See RightFax setup instructions in the OM Plus HELP directory after install for more details.)
Enhancement: Added functions for new OMP Web Service components.

2.2.2.0455 - June, 2009
Enhancement: New SAP Interface; method used is direct call back to SAP on individual job status and not the current Polling method
Enhancement: Added an SAP  tab to Settings dialog in main OM Plus server GUI to set an SAP-Enabled flag and provide access to GUI to maintain sapconfig file. It is also possible to log the status of all current SAP connections from here.
Enhancement: Added new 'syncu' family of ports that would work with Tricerat-type processing where the user name is dynamically altered before the port monitor spools the job to OM Plus.
Behavior Change: Program that gathers system information will now include a "patchlevel" value if such a file is present under the system directory.
Behavior Change: Added Send-To-Any / Receive-From-Any and Host-Alias to the Remote Destination GUI maintenance dialog. These setting will take place without having to manually restart the RemoteServ service. Also added button to manually request printers from hosts in the “Receive” list.
Enhancement: Added RETRYCOUNTER environment variable passed to a retry script that keeps count of how many times the script has been called for the problem at hand. The counter is not based on a specific problem (e.g. paper jam) but on the fact of a communication failure. If the nature of the problem changes (e.g. from paper jam to offline) within the same failure event, the counter is not reset.
Behavior Change: The standalone dcclp now has the exception dump logic included. This means that all processes that run dcclp in this mode (SAP, the port monitor, any scripting) now provide additional debugging support if there is a program abort.
Enhancement: Added command-line program AddPortMonPorts for creating large numbers of ports to work with our port monitor. This program creates the registry entries so they can be picked up for use the next time the Windows spooler is restarted.
Enhancement: The user can now run a script editor for event scripts directly from the dialog where the event and interface scripts are established. (This is on the Scripts In Use tab of the Settings dialog from the Environment tab of the main server OM Plus GUI.) The user doesn’t have to know where OM Plus stores these scripts in order to edit them.
Bug Fix: In CD Plus, a file handle was not getting reset after an open error causing a program abort then next time through. This has been fixed.
Bug Fix: Previously, if a user tried to change the type of OM Plus port monitor (from Basic to NP or NP to Basic), and the change failed, the original linkages between Windows printers and OM Plus destinations were lost. This has been corrected so that the linkages are retained.
Bug Fix: After changing the type of OM Plus port monitor in use, the “restore previous monitor” feature was occasionally lost. This has been fixed.
Behavior Change: dcclp will now retry up to a minute if the file-to-be-spooled is unavailable for any reason (e.g. external virus checker).
Bug Fix: A couple of different PDF page counting problems were identified and fixed.
Behavior Change: OM Plus mode client and LPPlus mode client will now remove any remote destination coding in the option string (E=<whatever>) before sending options along to OMP server.
Bug Fix: Due to a problem in the status service, if a user tried to Copy a request that had a remote destination using Java user interface, the message “Permission Denied” would appear. This has been fixed and the copy is now performed.
Enhancement: If our port monitor is unable to write to our log, or to the Windows event log, it used to pop-up a dialog reporting that fact. This pop-up has been removed. In those cases, there will be no record of the transaction involved and logging will be lost.
Behavior Change: Added the destination name to the log message recording the end of processing for a request.
Bug Fix: There were cases where the scheduler was not selecting the correct job among those in a given class, causing out-of-order printing. This has been fixed.
Bug Fix: There were times when the scheduler was not including newly spooled jobs in its scheduling process in a timely manner. To fix this, a scheduler tuning parameter was added that forces including new jobs within a given period of time. This value is maintained on the System Tuning tab of the server Settings dialog.
Bug Fix: In the Link Windows Printers and OM Plus Destinations dialog, changing a linked destination from one OM Plus printer to another was not working. This has been fixed.
Bug Fix: If the title field contained a path name with backslashes, the title value appearing in the Web Archive window had odd characters displayed. (The backslashes caused the succeeding character to be taken as a control character.) This has been corrected. However, titles with backslash characters are not currently supported as targets of the web archive search. Searching for titles with backslashes will causes the browser session to become unstable.

2.2.1.0428 - Jan, 2009
Enhancement: OM Plus Browser Interface V3
Enhancement: Cluster Aware port monitor, allowing OMP to take jobs in the Cluster virtual node.
Enhancement: New Port Monitor setting to accept Windows Spooler output and save to file instead of spool to OMP
Enhancement: Added new command line utility to update security parameters (updtsecgrp.exe).
Enhancement: OMPLUS mode destinations can now be configured to be unidirectional. This change will work with 'real' destinations as well as propagated Print Server / Agent installs
Enhancement: New scripts have been added to remove the IIS virtual server directories for uninstalling.
Bug Fix: In some instances the User Filter would close before all of the data was flushed to the output. Thus behaviors has been changed.
Bug Fix: Bi-Directional mode queues could timeout due to the size of the job and the timing of the PJL "Keep Alive". The timing has been altered to fix this. Also that time is now user configurable.
Bug Fix: Problems were found in the accesing of 'Shared Memory'; this process has been corrected.
Bug Fix: LPR automatic detection of when a Form Feed (Hex 0c) should be autpmatically added to a data stream when the file break is active was flawed.
Bug Fix: LPR incomming job titles were malformed.
Behavior Change: DCGRP now has the L command to batch by the spooled job time.

2.2.1.0374 - Sept., 2008
Enhancement: Increased Filter/Interface response time
Bug Fix: Bi-directional confirmation was not always interrupting a job when the write-timeout was exceeded.
Behavior Change:  The bi-directional confirmation logic (PJL and ZPL) was not handling write timeouts of less than one minute.
Bug Fix: ZPL monitored jobs were not always interrupted when an error was discovered while de-spooling.
Enhancement: The ZPL de-spooling logic will now respond to an optional environment variable (PICK_WAIT) to wait indefinitely for a “pick” status bit to be set. This corresponds to a person physically removing a label from a printer.
Bug Fix: The 'Bundler' de-spooling process did not return the correct value internally if there was an error.
Bug Fix: In some isolated cases, jobs printed to a class were despooled out of order. This has been corrected.
Enhancement: Added 'ompdest' console program which verifies whether the supplied command-line queue name is a valid OM Plus destination / class.
Enhancement: Added 'omremsetup' program to help with scripting send/receive file lists; and to set new flags indicating whether hosts can receive or send
from/to any host.
Enhancement: Modified Remote service to implement sending to, or receiving from, any host, as determined by a user setting; also to use ‘pingHost’ to set alias for local host.
Behavior Change: Uninstall will now automatically remove additional components added for partners when “remove all” is selected.

2.2.1.0355 - May, 2008
Enhancement: Changes to destination configurations are stored and can be un-done with the new “-orestore” command line option in lpadmin. This undo feature also works if a destination has been deleted. In the case of restoring a deleted destination, the class and group memberships are also restored.
Enhancement: Added command to allow a bundle to be terminated manually through the client GUI. At present, this “Terminate Bundle” command is not available through the web interface.
Enhancement: dccnetstat will now return the up/down state of the scheduler by transacting with the omplus-mode server (uses new –o<hostname> parameter).
Enhancement: The installation, handling, and management of event scripts and de-spooling scripts has changed to prevent custom user scripts being impacted during an upgrade installation. (a) the OM Plus installation will no longer install operational event scripts in the events directory; only example, ‘batdist’, files are installed; (b) the software no longer expects such events scripts to be present; (c) with this scheme, users can create custom event scripts without worrying about their being overwritten during an upgrade. A new document in the ‘help’ directory, Managing Custom Scripts in OM Plus explains the new process in detail. As part of this change, new event scripts were added to the Windows version of OM Plus to mirror the event scripts available under the Unix version. New event scripts now honored are: accept, arch_err, cancel, demon, lpdfail, and reject. In addition, the purge script now runs out of the bin directory and is not to be modified by the user. There is a new prepurge script that can be created and, if it exists, it will run before the purge script. If users had previously modified the original purge script, they will need to move those modifications into the prepurge script.
During an upgrade installation, installation process attempts to make the environment fit this new scheme by deleting uncustomized scripts or moving others. All installation actions are logged in the omsetup file.
Bug Fix: SNMP queries from the filter had caused aborts in some cases. This has been fixed.
Bug Fix: The Printer-Status feature from the Request Status window was not showing the “circular log” for the printer in some cases. This has been fixed.
Bug Fix: CD Plus logic assumed the only ‘$’ appearing on the command line was as part of its substitution keyword logic, and did not handle the case where the character would appear natively. This resulted in the parameter containing the $ lose characters from that point on. This has been corrected.
Enhancement: If the number file is discovered missing when trying to spool a file, it is re-created starting at RID00001.
Behavior Change: Any permissions problems encountered by the Port Monitor will now be logged to the port monitor log, or to the Windows event log if the port monitor log is unavailable. Previously, a pop-up window reported this problem, causing the port processing to stall until the pop-up window was closed.
Behavior Change: 'lpadmin' command line program was not secured properly. This has been changed so that only OM Plus admin users are able to use the command. Also, the user who creates, deletes, or modifies a destination is now logged.
Behavior Change: If a security model defined restriction based on user, then spooling would sometimes not work depending on how the job arrived in OM Plus. This was due to some security checks being made in dcclp before the security user had been properly determined.
Behavior Change: OMP can now automatically set all omxfer template files to LPPlus mode in addition to netprint and OMPlus mode. This is done through the OM Plus server GUI/Environment Tab/Settings/Remote Host Lists Tab/Settings button.

Forum: OM Plus Version History for Windows ]]> http://plustechnologies.websitetoolbox.com/post?id=3018939 Mon, 06 Oct 2008 17:13:41 GMT http://plustechnologies.websitetoolbox.com/post?id=2979734

In general:

A User Filter in OMP is a process that is called during the output of the job to the end destination.  Its normal function is to make some kind of change to the data stream before the end destination receives the data. A common use is Transformation into PDF or from PDF to Post Script.

Implementing a User Filter:

A User Filter is referenced in Define Destination Screen, Page 3.  The setup will only necessitate the reference to the User Filter logic itself (Program, Script, etc). The program / script must have permissions of 755 or it will cause the job to abort for security reasons.

Creating a User Filter:

To start off, a User Filer ("UF") is a set of logic (program, script, etc) that will take data on the STDIN pipe and then deliver the back to STDOUT.  OMP will deliver STDOUT to the UF STDIN and then listen to the UF STDOUT and take that data and finish the delivery to the end destination.  It is required that you have some knowledge of basic scripting on the system you are working with, including knowledge of system commands.

Since a UF configuration does not take options, all configuration and program setting must be internal. Normally even programs are "wrapped" in scripts so programs can be given their correct options.

User Filter logic will work the same in the Windows and UNIX/LINUX systems, with one difference; a UF written for Windows will have to be a script that starts with our stdintofile.exe (%omhome%\bin\stdintofile.exe <file>). That utility will drain the data from STDIN and write it to a file. The UF script will then have to take the file and deliver it STDOUT.

Since writing a UF will require some knowledge of what is in the system environment at the time it runs, it is recommended that the first UF written simply return the environment.

Windows BAT Example:

@echo off

%omhome%\bin\stdintofile.exe %omhome%\tmp\INFILE

Set C:\UF_ENV.TXT

Type %omhome%\tmp\INFILE

Del %omhome%\tmp\INFILE

UNIX Shell example

cat > $LPHOME/tmp/INFILE

env /UF_ENV.TXT

cat $LPHOME/tmp/INFILE

rm $LPHOME/tmp/INFILE

Both examples will take the data from STDIN, write that data to a file, export the working environment to a file, write the job data back to STDOUT for OMP delivery and then clean up the data file.

Plus Technologies Support ("PT Support") has a number of UF files in our library, so feel free to ask for examples.

PT Support can also provide Professional Services to create User Filter and include that into normal system support.

Note: User Filers not provided by PT Support will not be supported under a normal support contract.

Please contact PT Support with any questions.

support@plustechnologies.com

877-899-7587 Option 6

Forum: OM Plus - Q&A ]]> http://plustechnologies.websitetoolbox.com/post?id=2979734 Thu, 18 Sep 2008 14:36:22 GMT http://plustechnologies.websitetoolbox.com/post?id=2131893
I need to make sure the destination are working in OM Plus before I start testing integration with our other applications.

Thank you,

Matt

Forum: OM Plus - Q&A ]]> http://plustechnologies.websitetoolbox.com/post?id=2131893 Tue, 04 Sep 2007 20:03:09 GMT http://plustechnologies.websitetoolbox.com/post?id=1731014 2.2.1.0330 - Mar., 2008
Enhancement: The maximum size of the Title field for spool jobs has been increased from 20 to 50 characters.
Enhancement: The maximum size of the Form field for spool jobs / destinations has been increased from 15 to 30 characters.
Enhancement: CD Plus now allows matching on ‘originating-host’ or ‘spool-time’ (time is matched based on a time range, or being earlier or later than a given time).
Enhancement: The LPD service has expanded the protocols allowed for designating the data and control header information.
Behavior Change: Previously, when a trial license expired during a time of scheduler inactivity, the next job to spool caused the scheduler to abort in the middle of the spooling process. The spooling process then waited for communication with the scheduler. This caused a delay back up the chain to the port monitor in some cases. Now, when the license period expires, the scheduler will remain active, but will not spool new jobs (it follows the same logic as when Request-Max has been exceeded.). In addition, anytime the Services tab on the server user interface is activated and the license has expired, the “expiration dialog” will display. Previously, this dialog only displayed when the user tried to activate the scheduler service.
Behavior Change: Uninstall did not include stopping the (relatively) new Monitor service. This has been corrected.
Behavior Change: Temserv mode destinations will now report an error and interrupt a job if the closing protocol sequence with the partner device is not successful.
 
2.1.1.0321 - Feb., 2008
Bug Fix: Print jobs where OM Plus did not count pages were not being de-spooled under termserv mode. This has been fixed.
Bug Fix: Jobs that had page counts supplied externally (from Windows spooler) would sometimes have their ‘total-pages’ value zeroed out when de-spooling, causing a question-mark to appear as part of the Page information in the Request Status window. This has been fixed.

2.1.1.0316 - Feb., 2008
Enhancement: The omplus-mode service can now receive multiple jobs simultaneously. Previously, this mode only processed one job at a time causing occasional disconnects on pending jobs. The number of allowed jobs is configurable from a new tab in the main server GUI Environment/Settings dialog. By default, up to 10 simultaneous jobs can be processed.
Enhancement: Added implementation of de-spooling communications with Zebra label printers using cpcl. A new model script (omcpclretry.js) is available to be used with this implementation that provides logic for automatic retries under certain conditions. 
Enhancement: Added new ‘virtual’ printer mode and accompanying implementation. This mode is automatically linked to a ‘virtual.bat’ user filter. As delivered, the user filter simply does a pass-through for the general release.
Enhancement: Added new service that can provide remote TCP status information about other OM Plus services. It can also be used to start, stop, restart or kill these services.
Enhancement: Remote printer definitions will now be sent only when a printer is added or deleted, not when maintenance or operational changes are made to the printer. It is now possible to initiate the sending of printer definitions to a remote host through a button on the ‘Remote Hosts Lists’ tab of the ‘Settings’ dialog in the Server user interface.
Enhancement: Added “printer discovery” SNMP status command in background status. Can be used to return more complete information about a printer device.
Bug Fix: Corrected timing problem between the scheduler and dcclp that could cause dcclp to abort under heavy load.
Bug Fix: Fixed problem where a streaming despooling process would abort when internal PJL commands exceeded a certain length.
Bug Fix: Job names with embedded blanks were not properly handled by CD Plus. This has been corrected.
Behavior Change: An error is now returned to the Destination Configuration GUI when trying to add more virtual printers than the system is configured for.
Bug Fix: Previously, the destination creation logic did not prevent a comma from being part of a destination name. This messes up the parsing rules required by the OM Plus GUI. Commas are no longer allowed.
Bug Fix: The OM Plus on-line help could not be properly accessed from the Help button on the web request status window. This has been fixed.

2.1.1.0305 - Nov., 2007
Behavior Change: dcclp now returns an error if the time given on a timed-release is earlier than the current time.
Enhancement: Spooling and de-spooling now handles multiple fax numbers;
Behavior Change: The enable, disable, accept, reject, and form mount commands will now return error messages if a problem is encountered.
Bug Fix: If OM Plus security was set up such that a group had specific printers assigned to it, users in that group would not be able to issue suspend commands successfully. This has been fixed.
Behavior Change: If a modification was made to a printer whose name was the same as an existing printer except for the case of one or more letters, a new printer was created with the case-different name.
Bug Fix: Background status was not correctly checking security when a translation table change request came in. This has been fixed.
Bug Fix: Fixed a bug introduced in prior release that caused the request status screen to not display printer group information properly.

2.1.1.0298 - Oct., 2007
Bug Fix: Background status would abort in some cases when special characters appeared in the title field of a queue entry. This has been fixed.
Behavior Change: If the scheduler is loading corrupted queue files, it will now provide a true RID value and will put the request in interrupted status. Previously, the RID value would be set to RID99999 and the status set to ‘ready’.
Bug Fix: There were cases where internal scheduler commands were not being processed, giving the scheduler the appearance of being hung up. This has been fixed.
Bug Fix:In some cases, the mechanism used by dcclp to track recursive use was not being cleared. This has been fixed.
Behavior Change:When a change is made to the properties of a spool job, the log now reflects both the host/user information as well as the resolved user of the person making the request.
Enhancement: The maximum number of allowed destinations has been increased to 3000.

2.1.1.0295 - Aug., 2007
Behavior Change: Changed logging of request modification in dcclp so that host, user, and resolved user information is included. Previously, only the resolved user was shown, causing confusion in some cases.
Bug Fix: The environment variable that tracked recursive dcclp calls was not being cleared out properly in all cases. This has been fixed.
Behavior Change: Changed background status to incorporate company information as part of web service request filter call.
Enhancement: De-spooling processes now creates an environment variable called OMPWM, setting its value from a new option string parameter(-o  ompwm=<value> ) The intended use is for optionally adding watermarks to the output job stream in a user filter.

2.1.1.0277 - Mar., 2007
Enhancement: The Archive web interface has been updated.
Bug Fix: The web status window did now displays international dates correctly.
Bug Fix: Running the web interface within a Terminal Services environment occasionally would give users the incorrect security status. This has been fixed.
Behavior Change: The Java Client page display for requests being printed using the ‘stream’ protocol was getting page updates from two different sources. The result was confusing. It now reflects the number of pages actually printed on the printer.
Bug Fix: The Java Client page display would not always correctly reflect the number of pages printed when a stream-protocol job was cancelled from the printer console. This has been fixed.
Enhancement: The exit code from the de-spooling process is now available as the environment variable ‘OMEXITCODE’ in the post filter script (postfilt.bat).
Enhancement: Commands related to the new stream protocol have been added to the web interface administration and status windows.
Behavior Change: The operation of the stream-protocol now allows the daemon to time out waiting on the printer based on the destination’s ‘Write Time’ value. The earlier implementation of this did not accurately follow the ‘Write Time’ value.
Bug Fix: The Sort field in the web Preferences window always showed English text regardless of the selected language. This has been fixed.
Bug Fix: The web OM Plus interface did not display RID numbers or printers if the scheduler was down. This has been fixed.
Behavior Change: In the server user interface, the tab panel for ‘Timeouts’ in the Settings dialog did not allow values greater than 10000. This limit has been removed.

2.1.1.0268 - Mar., 2007
Enhancement: Altered the SNMPConf program to allow it to do a shorter MIB query (required by some Sharp printers).

Enhancement: Added stream-confirmation capabilities on de-spooling. The streaming confirmation feature is written to work with printers using standard PJL communication protocol. This feature may not work properly with printers that do not follow this protocol.   

Enhancement: Supporting stream confirmation, a user can change a request in ‘sent’ or ‘unconf’ status to ‘cmplt’. This can be done through the Java GUI or through the console program dccupdtstat.exe.

Enhancement: Added program dccreset.exe to reset different aspects of printer operation. This is the Windows version of the Unix dccreset program.

Enhancement: The LPD process now creates an environment variable called LPDTITLE_<thread#> just prior to calling the dcclp routine. This variable contains the full title as resolved by the LPD process, enclosed in double quotes. The thread number is part of the name to keep the variables unique in a multi-threading environment.

Enhancement: When dcclp is handling the job title, it will now look for a title substitution file (called titeSub) under the constants directory,. If such a file exists, dcclp will match the start of a job title with the file entries and make substitutions if it finds a match. An example file named titleSub.dist is supplied with the release. For present, this file is maintained through a text editor. Each line contains a single substitution candidate and corresponding replacement text separated by the ‘|’ character. The replacement text can contain any valid title character (no double quotes) and may be empty.

NOTE: This build of the server is dependent on build 2.1.1.0046 of the OM Plus Client. Both are required to implement streaming confirmation

2.1.1.0252 - Jan., 2007
Bug Fix: Fixed a token-handle leak in our port monitor.
Behavior Change: dccgrp now uses shared memory if the scheduler is up to retrieve request information, and sort it as the scheduler would, before performing the indicated command.
Enhancement: Changed the internal scheduler thread coordination to ensure that de-spooling activities get their time slice during heavy scheduler command processing.
Bug Fix: Fixed message leak in scheduler when it is shut down.
Bug Fix: Removed PJL ‘heartbeats’ that were being sent at inappropriate times. This caused corruption in interpreting the job stream in some cases.
Lengthened time between end-of-job heartbeats from 10 to 60 seconds. For some printers, too frequent heartbeats adversely impacted processing.

2.1.1.0250 - Nov., 2006
Bug Fix: dcclp command lines constructed by the LPD service sometimes had extra blanks in them. Depending on the context, these extra blanks prevented correct interpretation of the command line, causing some options to be ignored. This has been fixed.
Bug Fix: If a ‘passthru’ option appeared in a dcclp command line, the resulting option string in the queue file did not leave a space between it and options that followed. This has been corrected.
Behavior Change: The port monitor will now replace any double-quote character in the job title with an underscore character.
Bug Fix: In pcl documents where the page orientation changed, this change was not being retained. This caused problems with page calculations. This has been fixed.
Enhancement: Viewing large pcl / pdf / graphics files through the Java client was taking unusually long time. This problem has been fixed
 
2.1.1.0248 - Nov., 2006
Bug Fix: The end-to-end service would sometimes abort on systems with tens of thousands of requests and under heavy load. This has been corrected.
Bug Fix: If an OM Plus user is added through the OM Plus security and the length of the user name was at the maximum for the field (30 characters), the security information became corrupted. This has been fixed.
Behavior Change: Changed new HTML user preference logic regarding ascending/descending display order. This was not language sensitive on startup.
Behavior Change: HTML will now report archive retrieval failure problems.
Bug Fix: When dccnetstat is run requesting a queue status, if the queue had a large number of pending requests, the LPD service could get into an error reporting loop. This has been fixed.
Behavior Change: dccnetstat has been fixed so it can correctly receive the status of a large number of pending requests for a queue.
Bug Fix: De-spooling requests using the ombanner.js model would sometimes interrupt with a code 1. This was a scripting problem with the model and has been corrected.
Behavior Change: Interface scripts will now by default write some file access errors to the log.
Behavior Change: The template directory was not being deleted during a complete product uninstall. This has been changed.
 
2.1.1.0240 - Sep., 2006
Bug Fix: If a request with no page counting was archived, it caused the archiving software to abort. This has been corrected.
Bug Fix: Customers with large values for ‘Maximum Requests’, coupled with intense LPD activity, had problems with the LPD process aborting.
Product Enhancment: Customers with extremely heavy LPD activity reported sluggish processing; Enhancements have been made to internal message handling, resulting in increased efficiency and significantly improved processing under load.
Bug Fix: It was possible for an advanced form request copy to be assigned the same RID as another request spooling at the same time. This has been fixed.
Bug Fix: Class name checking was not obeying case-sensitivity requirements, causing some requests to be spooled but never de-spooled. This has been corrected.
Behavior Change: If a bi-directional destination is receiving statuses from a printer, it would not send “keep-alive” transmissions back to the printer. In some cases, this caused the printer to timeout. This has been corrected.
Bug Fix: Corrected a case where, when Java login security is in use, a user who was associated with administrator security access was denied access to the log file.
Bug Fix: When operating in termserv mode, if a printer went into retry status there was a case where it would not be reset to active status until long after the printer had resumed normal operation. This has been corrected.
Bug Fix: The (undocumented) –z option of the lpadmin command was not functioning properly. This has been corrected.
Enhancement: Added event script ‘remotedests.bat’ that is run whenever the Remote Service either receives remote destinations from a remote host or sends its own destinations to a remote host.
Behavior Change: To avoid problems with multi-language definitions in the Web interface, the name of the preferences.png file has been changed to prefsetup.png as have all corresponding references.
Bug Fix: The de-spooling connection retry logic was not retrying failed connections properly. This would lead to the filter waiting on a connection even though the previously unavailable partner is now available. This has been corrected.
 
2.1.1.0224 - Jul., 2006
Note* Includes phase 2 of web changes to OM Plus.
Note* This version is Minimum to interface with Om Stats
Enhancement: Includes latest OM Plus documentation (HTML & pdf);
Behavior Change: If title field contains a comma character, enclose the field in double-quotes when writing to accounting log.
Bug Fix: Fixed adminhtml protocol problem that caused 10053 error in background status.
Bug Bix: Fixed pdf page counting problem (done in Unix in March) that caused some pdf docs to not get a valid page count.
New Feature: Two new batch files (OMP_XP_IIS_Setup.bat and OMP_W2K3_IIS_Setup.bat) are available under our …\httpd\conf directory. Assuming our web stuff is left in place as installed, these scripts will do the IIS configuration needed for either an XP system or a Windows 2003 Server system. In both cases the IIS virtual directories cgi-bin and omplus are created. In the Windows 2003 case, the Web Services Extension setup is also done. The user opens a command prompt and navigates to the %omhome%\httpd\conf directory and runs the appropriate script.
New Feature: There are certain delete-file and rename-file routines that throw program exceptions if they fail rather than simply returning a failure code. In most cases, no exception handling was present. All these routines have been converted to routines that return simple success/failure codes.
Behavior Change: A termserv mode destination using bi-directional confirmation will now receive status updates from the printer while the job is being delivered. Previously, status information was not received until after the whole job was delivered. This caused a delay in getting status information for very large jobs.
New Feature: Added extended identification for ipg-vgl data and extended page counting logic.
New Behavior: Added exception handling to the LPD service, the OMP server service, the End-to-End service, and the main filter de-spooling program. If any of these programs abort, information about the location of the problem is now written to files. These files can be used by developers to diagnose the cause of the problem. The files are written to the bin directory and have the PTDUMP_<prog>_<thread>;
New Behavior: At the end of the filter de-spooling, in termserv if we have been PJL-ing the page count, don’t rectify the count at the end if the ‘total-pages’ is 0.
 
2.1.1.0212 - May, 2006
Enhancement: A new web interface for request status and the structure to allow internationalization of text.
Enhancement: The web administration interface (ompadmin) now allows creation of new destinations. The prior version (adminhtml) still has this limitation.
Enhancement: During installation, the files needed for the web interface will be placed under the appropriate directory for the operating system being used. (This assumes using IIS as the web server.)
Bug Fix: Fixed bug in form matching where un-initialized field and a maximum length form name could cause a field overflow.
Bug Fix: Viewing archive pcl data through the web interface did not work properly through SwiftView. This has been corrected.(PENDING)
Enhancement: Added pdf files to those that can be viewed through the web interface to archive reports.
Enhancement: Documented ALT_DEST environment variable at the top of model interface scripts.
Behavior Change: Previously, performing an update install of OM Plus did not replace existing scripts under the event or interfaces directories. This caused problems when functional changes were made in scripts from one release to another. This has been corrected such that the installation software ensures that the latest scripting is always installed; and any user customized scripts, or obsolete scripts, are saved under a separate directory. This allows the user to re-apply their customization manually after the upgrade. All installation activity is for this is logged to omSetup.
Bug Fix: A destination change would fail to a class if the class definition held a large number of destinations. This has been fixed.
 
2.1.1.0202 - Apr., 2006
Bug Fix: If modification dcclp was run during de-spooling, the code went ahead with the parent/child hook up, even though there was no new request. This created a condition where a child was its own parent. This has been corrected.
Bug Fix: dccreindex was not picking up the setting to turn off looking for pcl-graphics; also it was over counting some files by a page; and was being pre-maturely ended by embedded end-of-file characters.. These issues have been fixed.
Bug Fix: Restored operational feature removed when the wild-card security function was implemented: if a user is working on the box where OM Plus is installed, that user’s Windows login is treated as a resolved local user for OM Plus security.
Behavior Change: The button to create an OM Plus destination on the “Link Windows Printers …” dialog has been hidden.
Bug Fix: Terminal Service status now being logged when the main server gui is started; the log entry for Terminal services associated with the scheduler has been removed because it will always be ‘no’ by the current way it is determined.
Enhancement: %OMHOME% can now be used in the as part of the user filter definition string.
Behavior Change: In the Log Viewer, when lines were marked they were kept in the order marked rather than in sorted order. This has been changed.
Bug Fix: If a destination change was issued inside spooler.bat, the scheduler loaded the changed destination in the main part of memory, but did not change the destination field it used in the de-spooling logic. This has been fixed by altering the add/chg request scheduler routines to be like those of the Unix side.
Behavior Change: Changed pjl confirmation so that (1) it only exits when the right number of end-of-job messages have been received; (2) on successful completion of a job, the total pages printed on the request status will match the number spooled.
Behavior Change: Changed datatype determination logic to expand characteristics for a pcl-2 file.
 
2.1.1.0198 - Mar., 2006
Enhancement: Added dccreindex program, to be used only in the context of spooler.bat for “re-indexing” a job.
Behavior Change: When receiving data in archive html, if the data contained a 0x01 in the first byte, this was interpreted as a NACK and the html receive closed down. This has been fixed to only respond to a NACK if it is the only data transmitted.
Behavior Change: Removed DISPLAY parameter from front of bi-di communication string (Kyocera printers did not handle this parameter).
Behavior Change: If the title field from archived file has embedded commas, these will now be translated to underscores for during retrieval.
Enhancement: Added dccarchive.exe program to perform asynchronous archiving process relative to the scheduler. A new version of purge.bat now runs this program; the script itself is now run asynchronously.
Bug Fix: Fixed bug in lpdserv that could cause a job to be rejected if the destination is remote to the computer receiving the job.
Bug Fix: Fixed bug in lpdserv that could cause the program to abort if the host names in the RemoteDest file exceeded a certain length.
Behavior Change: All PJL communication is now included in a debug trace, not just the PJL from the printer after the job has been sent.
Bug Fix: In RemoteServ, if a receive error occurs, it’s possible for the program to go into an infinite error loop. This has been corrected.
Bug Fix: Customers who set their request max to 99999 had a problem when the RIDs rolled over back to 0. This has been fixed.
Bug Fix: In background status, added checks everywhere a socket receive is done to bail on error. There were a few places where this was not done.
Behavior Change: Changed distributed omxfer1 and omxfer2  so that banner is turned off.
Behavior Change: During installation, the user is now presented with an additional ‘Confirmation’ box to verify that they accept the terms of the license agreement.
 
2.1.1.0191 - Nov., 2005
*Note: (2.1.1.0044 Optio, Client 2.1.1.0036)
*Note: Client 2.1.1.0028 or newer is required
Bug Fix: Some drivers were reporting page counts to the spooler in a way that made our page count received from the spooler incorrect. This has been adjusted.
Bug Fix: Archive HTML interface had old, short values for length of USER field; and was incorrectly labeling a registered system as not registered. Both these have been fixed.
Bug Fix: dcclp was not reporting an error if the destination was omitted on a new request. This has been corrected.
Bug Fix: Some scheduler locking was not “Terminal Services” safe, resulting in, e.g., customers running lpadmin from Remote Desktop not having changes reflected in shared memory. This has been fixed.
Bug Fix: The existing mechanism for determining if the process was being run under terminal services did not work when Remote Desktop’ing into an XP machine. This has been fixed.
Bug Fix: lpadmin was not correctly counting virtual destinations or normal destinations when determining whether to allow a new definition to go forward. This has been corrected.
Enhancement: The maximum number of destinations allowed has been increased from 1000 to 2500.
 
2.1.1.0189 - Oct., 2005
Bug Fix: Made additional corrections related to working with files > 2GB (corrected numeric display in port monitor, in dcclp; fixed size allocation in de-spooling process)
Enhancement: Added parameter to command executing js interface script to force interpretation by javascript processor. Customer who had another program associated with .js suffix could only run our bat interface scripts.
Enhancement: Added change to pcl page counting to account for macros in the header (mirrored change to UNIX code).
Bug Fix: Fixed dcclp bug where modifying a non-existent RID caused an empty queue file to be created and did not flag the error.
Bug Fix: Changed dccprint to prevent a request from remaining in active status after it has de-spooled.
Bug Fixed: When class printers had form-mount override in effect, one job was despooled to each printer and then despooling to the class stopped. This has been fixed.
Behavior Change: Corrected template for optio.bat in line with coding changes.
Bug Fixed: In OMFilterLog program, if non-standard directory is used for searches, this value is not retained across runs; and the standard directory was always used to store search results. Also added a line to the results log indicating from which log file a line came.
 
2.1.1.0187 - Aug., 2005
*Note: JAVA Client 2.1.1.0027 required
Enhancement: The OMPlus-mode server can now have up to 50 pending connections.
Behavior Change: The optio.bat template has been updated to use the environment variable FORM_NAME instead of FORM;
Behavior Change: An ecivprinter mode destination will now not go fpend;
Bug Fix: A bug in the RD+ de-spooling process when working with pcl type files has been fixed.
 
2.1.1.0185 - Aug., 2005
Bug Fix: Fixed bug in pcl page counting when input comes from STDIN.
Behavior Change: In dcclppcgi, if the REMOTE_USER has a host name in front of user, strip it off.
Enhancement: InstallShield will now look for a program called ‘iscustom.exe’ under the directory with the installation package. If it exists, it will be run as the final step in the installation.
Enhancement: Added functions for Dynamic Color management.
Bug Fix: CD+ was not setting the user to $ properly; and the substitution of a real value into a $ place was not always correct lengthwise. This has been fixed.
Bug Fix: Corrected the auto-invocation of the editor in the “Active User Filter” dialog so that it would ignore any parameters present when invoking Notepad.
Bug Fix: Previously, when the ‘file=’ option was used, the name could not include a dot and therefore could not include a suffix (specifying, e.g., file=userdata.txt was not allowed). This has been fixed.
Bug Fix: The file= option did not allow a double-quoted string, to allow for blanks in the name. This has been fixed.
Bug Fix: For Optio products, the Fax Setup page did not appear in the Settings dialog; nor would ‘RightFax’ appear as a fax option. These have both been fixed.

2.1.1.0176 - July 2005
*Note:This build contains the following items relative to the prior version (2.0.6.0145):
Enahncement: Added parent/child processing in server.
Enahncement: Added ‘ecivprinter’ mode, allowing destinations to be created that automatically integrate with Optio processing. These are virtual printers and are not counted toward license restrictions.
Enahncement: New ‘Virtmax’ system default value defines how many slots are available for ‘virtual’ destinations (ecivprinter mode destinations and omxfer destinations). This change now allows us to accurately match licensed printers with defined printers (previously we had used two of these slots internally for omxfer).
Enahncement: Added wildcard designations for remote login security settings. Enahncement: The port monitor will now supply the domain of the originating job as the “host” associated with the request. Plus tech ports in the port monitor can be individually configured to supply either the domain or the host to associate with a job. The default is domain.
Enahncement: Added additional wildcard matching in CD+ title: now allows a*, a*b, a*b*,a*b*c, *a, *a*, *a*b matching.
Enahncement: Added ALT_DEST environment variable to de-spooling process. Enahncement: Added support for new syntax for requesting “pjlstart” activity: when restart value ends with ‘p’ the entire job is sent to the printer with pjl instructions to begin printing at a specific page.
Enahncement: When despooling, the user component of the HO field will now be taken as the request user instead of the value in the US field.
Enahncement: New ‘ForwardHost’ field is now stored in the extension file and is used by background status for request trace and SAP trace requests. If the field is not present, Device field (or E= field) will be used, as in prior versions.
Enahncement: New ‘BackwardHost’ field is now stored in the extension file and is used by the end-to-end notify service to locate the originating request to be marked ‘complete’. If the field is not present, the host component of the HO field will be used, as in prior versions.
Enahncement: When de-spooling, if an OMPlus mode client process has the environment variable OMPORIGHOST=y present, the logic will replace HO host field with current host, as it used to do prior to this build. This will allow a 2.1.1 server to act as an omplus-mode client with a 2.0.x server.
Behavior Change: For efficiency reasons, OM Plus no longer writes detailed log info to destination-specific “rolling” log.
Bug Fix: The option string was getting wiped out when dcclp ran within spooler.bat. This has been fixed.
Bug Fix: There were cases in LF counted files where we counted one page too few. This has been corrected.
Bug Fix: dcclp will now correctly give an error message if the destination name provided is incorrect due to upper/lower case differences. Previously dcclp detected the problem and exited with an error but generated no error message.
Bug Fix: Previously, attempting to override the datatype of a pdf job (using –T) was ignored; as was attempting to override the datatype for any job that was piped in to dcclp. This has been fixed.
Bug Fix: dcclp now logs when Advanced Forms creates a copy of a request; and the detail trace will log when the AF is in play for subsetting a request.
Bug Fix: dcclp will now log failures of Advanced Form to successfully copy any of the key files when the ‘all’ option is used.
Bug Fix: The logic looking for a ‘post’ data type signifier should have been looking at only the first 100 bytes of the job, but was instead looking through 8000 bytes. This caused a false positive for some jobs. This has been corrected.
Bug Fix: Fixed bug that treated originating e2e requests as clients when the scheduler was bounced. This has been corrected.
Bug Fix: Bundling on UserId will now reference the user from the HO entry if the US entry is lpplus.
Bug Fix: Corrected situation where despooling job went into retry for a few seconds then came back out again when no remedial action was taken. It would continue to go into retry as the retry timeout elapsed but the display would always revert back to an active status. This has been fixed.
Bug Fix: A number of individual processes that verified destination/class names were not case sensitive (because validation was done via the stat() function). This resulted in disk records being changed but the scheduler not recognizing the name in question. Processes fixed: dcclp , omplus-server, dccenable/disable/accept/reject/etc.
Bug Fix: Now, if the result of postfilt.bat is non-zero, the message will be logged. Currently it is only logged if the detail trace is set.
Bug Fix: If two enable messages received while a job is active, it caused the disable event script to run. This has been fixed.
Bug Fix: Fixed bug in RD+ that caused a NULL host component in the HO field of a newly spawned job.
Bug Fix: Responding to TRACE request in bk status the sockets were not being closed. This was fixed.
Bug Fix: The ‘PJLSTART’ environment variable was not being set in dccprint. This has been fixed.

2.0.6.0144 - Feb., 2005
Bug Fix: Class maintenance only showed one class even if there are more defined. This has been fixed.
Bug Fix: For large numbers of destinations / classes, Request Status incorrectly shows bunches of classes/destinations in light red. Also classes were displayed as normal destinations. This has been corrected


2.0.6.0142 - Feb., 2005
Bug Fix: Corrected bug that caused SAP submitted jobs to not reflect being reported to SAP.
Bug Fix: Included full socket shutdown protocol when getting trace information between background-statuses. Without this the communication appeared to end smoothly, resulting in error messages in the log.
Bug Fix: Retrieving graphics files from archive caused the first two characters to be dropped from the retrieved file.
Enahncement: Ensured that all Java GUI view requests are reflected in the log; and that the proper information is being shown.
Enahncement: OM Plus should now correctly handle reports up to 4.29 GB; the previous limit was 2.15 GB.
Enahncement: The efficiency of the page reporting logic when despooling has been improved.
Bug Fix: Uninstall didn’t complete on Win2003 machine due to change in how a system API worked. This has been fixed: the uninstall process should now work across all platforms.
Bug Fix: OMPlus mode printer wasn’t responding to suspend request. This has been fixed.
Bug Fix: The ompserver program would occasionally hang when a sending job was suspended or cancelled. This has been fixed.
Enahncement: All delivery modes are now enabled for the suspend or cancel commands.
Enahncement: Expanded internal class table from 100 to 500; and reduced the number of dests/class (CEMAX) from 100 to 30.
 
2.0.6.0128 - Jan., 2005
Bug Fix: Correction to new pcl page counting (now handles &pX correctly; and only counts linefeeds for pcl-1 files).
Bug Fix: Fixed problem where jobs printed from archive were only partially retrieved.
Bug Fix: Fixed problem where an extra space being added before the job title when retrieving from archive.
Bug Fix: Corrected memory leak in RightFax monitor code.
Bug Fix: Changed interpretation of RightFax status codes so only error is ‘completed-with-error’. Previously we reported a job as being failed when RightFax may be retrying the job.
 
2.0.6.0120 - Oct., 2004
Bug Fix: Corrected memory leaks in Search function within the GUI View Request command. In the worst case, this leak causes the PC to hang for lack of resources.
Bug Fix: Intermediate correction made to GUI View Request background status code (past-end-of-buffer problem) to prevent program termination.
Bug Fix: Fixed problem in new pcl page counting logic where embedded PJL commands were not always handled properly (as in a bundled file) and thus not setting the new OMCOLOR environment variable and miscounting pages.
Bug Fix: Fixed problem in pdf page counting where a file was being left open. This problem causes, for example, the LPD service to be unable to process new jobs.
Enhancement: Updated code for operation as Optio Print Manager.
Enhancement: OM Plus new Settings tabbed dialog will now generate updates to the rest of the system only when data changes. Previously, update messages had been sent whenever a page was exited, whether or not a change was made.
Enhancement: Added admin service commands for processing Java GUI send/receive host lists and rid spans files.
 
2.0.6.0116 - Dec., 2004
Bug Fix: Changed background status so it no longer “passes along” the sap marker in the transaction request when we need to hop to another server for request status updates (we still send it for printer status updates). This was causing the remote request to be marked as ‘SAPReported’ and was getting deleted early.
Enhancement: Added option for defining a “default” line for a bundled printer definition to provide a destination and options for any request not matching other explicitly defined keys.
Enahncement: Incorporated new pcl page counting logic to improve our page counting.
Enhancement: LPD service can now be set to accept unknown queues. It operates like the Unix version: an unknown queue will be given the name “UNKNOWN” and will remained spooled until disposed of by an operator. There is a new LPD settings dialog (see below) for controlling this option.
Enhancement: LPD service can now automatically discard jobs that have errors of one kind or another, while reporting back success to the partner process. This is controlled in new LPD settings dialog (see below).
Behavior Change: If job is not in ‘sent’ status, E2E server will now send “retry” back to partner in all cases except where we can’t find the request in shared memory. In this case it still sends back the ‘xxxxxxx’ value. The notify part will not quit on that request if it receives a ‘retry’.
Enhancement: Added snmp program and accompanying script (snmpObj.dll / checkSNMP.js) that can be used by scripts to get a printer’s snmp status in an ad-hoc way inside or outside of the context of OM Plus. This program is written as a COM object to provide flexibility in retrieving the different statuses available.
Enhancement: dcclp now sets an environment variable (OMCOLOR) if page counting a pcl file detects color commands. This should only be used in non-threaded contexts.
Behavior Change: Spooling to a bundle printer with type ‘form’ would fpend if a form was not mounted. Now a form difference will not cause a bundle printer request to fpend.
Bug Fix: Fixed problem that didn’t supply the correct user to a spooled bundle.
Enhancement: A number of individual OM Plus setting dialogs have been moved to a single, tabbed dialog box. This allows for more flexibility as additional parameters are added. A number of buttons on the right side of the Environment tab have been replaced by a single Settings button.
Bug Fix: Changed socket shutdown call so it doesn’t block receiving the last message from the printer.
Behavior Change: InstallShield now displays a box after the main system has been installed, but before the final box is displayed, indicating that processing is continuing. This is to address cases where conversion of existing systems takes a long time.
Enhancement: To view a subset in a log file, you can now highlight data to be viewed and right-click for a one-step operation.
Enhancement: Added a minimize button to the Link Windows Printers and OM Plus Destinations dialog; and a warning if the Link Windows … dialog is open when the user tries to close the main server GUI.

2.0.6.0102 - Oct., 2004
Bug Fix: This build fixes a problem with virtual printer processing that was present in build 2.0.6.0100.

2.0.6.0100 - Oct., 2004
Bug Fix: Reject destination did not work this has been fixed.
Behavior Change: The user is now prohibited from setting ‘Maximum Dests’ in the System Defaults GUI to a value greater than PMAX, where PMAX is an internal program constant used for sizing arrays.
Enhancement: Through a new OM Plus Tuning dialog the user can set how many de-spooling jobs can be active at one time. The minimum is 0 (which effectively stops the scheduling process) and the maximum is 60.
Enhancement: Through a new OM Plus Tuning dialog the user can set how many simultaneous jobs the LPD service will receive. The minimum is 0 (which prevents any new jobs from being received); there is no maximum; the default value is 30.
Enhancement: Added new OM Plus Tuning dialog accessed from the Internals dialog off the Environment tab.
Behavior Change: Fixed both dccgenable and dccgdisable so they will run successfully if the scheduler is not up.
Bug Fix: Changed close-down logic of end-to-end service to prevent occasional hang-ups.

 
2.0.6.0090 - Oct., 2004
*Note: This release should be made available in conjunction with release
 2.0.1.0017 of the OM Plus Client.
Enhancement: The de-spooling process now includes the use of interface scripts. The Word document InterfaceScripts.doc describes the background and technical aspects of this.
Enhancement: There is now an “Advanced Scripting” dialog that can be displayed from the main server gui. This dialog can be used to see the current state of the scripting setup and to facilitate an update of the OM Plus setup when the Windows Scripting Host is upgraded to a newer version.
Bug Fix: The number of characters written to acct log did not accurately reflect the total number of characters sent to the device. This has been fixed.
Bug Fix: Fixed problem where if user filter was not successfully started, the de-spooling could hang even through attempts to suspend or cancel the job.
Behavior Change: dcclp will now report an error if you try to modify an RID that is in ‘spool’ status. Previously, it reported no error and updated the queue entry (file only) but this would later be overwritten by internal dcclp values.
Bug Fix: Fixed situation where spooler.bat was not getting the correct exit code from the dcclp process.
Bug Fix: Fixed problem where, when SAP asks for status, background status tried to trace the status out to a non-OM Plus device.
Bug Fix: When a trace-connect failed in background status, the socket was not closed, resulting in system resource issues when this occurred consistently. This has been fixed.
Bug Fix: When called through SAP, file handles to RemoteDests not being closed. This has been fixed.
Bug Fix: Code will now correctly handle option strings surrounded by double-quotes (e.g. –o”one two three”).
Bug Fix: Retrieving requests from archive also handles embedded blank field (title / options) correctly.
Bug Fix: All parameters passed to spooler.bat used to be enclosed in double-quotes. This meant that environment variables created in spooler.bat included double-quotes around the value. Now, only the title field is enclosed in double quotes.
Bug Fix: Correction to e2e logic that could cause it to go into a processing loop (code assumed that result of a recv was either -1 or > 0; looping was controlled by positive value of this result; when result was 0, looped forever).
Bug Fix: Corrected one reference to ‘list’ directory in the code which should have been ‘lists’.
Behavior Change: Now allows file= to reference a remote system (scheduler must be running under account that has access)
Bug Fix: Fixed logic maintaining group file that could allow group file to be deleted and not re-created.
Enhancement: Added “Record System Info” button to Environment tab that echoes system information to the log (to get a snapshot of user system for debugging).
Behavior Change: Changed names of environment variables created in spooler.bat (and .batdist) to make unique to spooler context.
Enhancement: Now distributing datatypeOptions in constants files with default values.
 
2.0.6.0062 - Sept., 2004
Bug Fix: Repaired duplicate checking logic when archiving files with ‘archive-keep’ option set. Bug caused some archive data corruption (queue / reports entries out-of-synch) and repeated failure to archive certain requests.
Behavior Change: If SNMP is unavailable for a device, the SNMP polling will now be disabled in all circumstances.
Bug Fix: Fixed OMFilterLog so that is now accepted as the new-line character when entering multiple text lines on the Define Lists page.

2.0.5.0060 - Sept., 2004
Enhancement: Scheduler now writes a log entry that includes the OM Plus version number.
Enhancement: Dcclp now creates WINTITLE environment variable when called from port monitor that has full title of job as we get it from Windows.
New Feature: Port monitor now passes to dcclp the name of the Windows printer as an undocumented –k option. Dcclp makes this available as environment variable WINDEST for spooler.bat.
Enhancement: Increased maximum length allowed for a log record from 200 to 300 characters.
Bug Fix: Despooling job will no longer interrupt during bidirectional printing if the PJL page count differs from our page count (except for PJL page count of 0). The ‘postpjl.bat’ script is responsible for any interrupt processing. The default action of the script is to do nothing (except for the page-count-0 case).
Enhancement: Added distribution versions of all scripts (*.batdist extensions) that will always replace existing versions. Previously we had no way to deliver a changed script during an update install.
Bug Fix: Fixed bug that caused rolling log to blow up when trying to record stuff for omxfer.
Behavior Change: Previously, any request that underwent a destination change would be put on hold. Now, only already “resolved” jobs will be put on hold.
Bug Fix: If a job with a ‘cmplt’ status underwent a destination change, the status remained ‘cmplt’. This has been corrected so it now goes to ‘held’.
Bug Fix: Corrected condition where processing did not recognize that an existing option parameter was already existing, and so would verify with security that the current user had the authority to remove the parameter. A restricted user would therefore be dinged for trying to remove something that was not being removed. This has been corrected.
Enhancement: LPR client now has the same formatting options for the job title as the Unix version. In addition, it not only responds to an environment variable (now called ‘LPRTITLEORDER’), but also to a constants file (or printer-specific file) named ‘lprTitleOrder’. The formatting options and values of these variables/files are given below:

Formatting Option|  LPRTITLEORDER env. var.| lprTitleOrder File Value  
(rid)-(title)                            1                                  back    
(title>-(rid)                           0                                  front             
(title>                                   2                                  only               

2.0.5.0052 - Aug, 2004
New Feature: Added test early in dcclp to warn if user doesn’t have rights to run dcclp in a Terminal Services environment.
Enhancement: Added destination “rolling log” for information generated during de-spooling. Applies to all destination modes.
Enhancement: CD Plus will now match on the ‘basename’ of input file if no explicit –t parameter is found to provide a title for title matching.
Enhancement: You now must have OM Plus admin rights to start/stop our services from our GUI.

2.0.5.0047 - Aug, 2004
Bug Fix: Data in View Request caused nulls to be included in data stream.
Bug Fix: Most OM Plus programs not running if the system PATH exceeded 276 characters.
Bug Fix: Removed deadlock situation that could prevent the scheduler from coming down.
Enhancement: Terminal Services clients now have full access to all OM Plus features (e.g. dcclp / stopping services).
Enhancement: Port Monitor will now log problems to the Application event log if it is unable to write to ptmonlog.
Enhancement: You must now have OM Plus administrator access to uninstall OM Plus.
New Feature: Added script ptTestlpd.js to provide an easy way to test and get message back on lpd status. It runs dccnetstat –h and provides text output based on the return code.
Enhancement: Now resolves a destination name on the dcclp command line to a remote destination. If no local destinations by that name are found, it will hit on the first matching remote destination in the RemoteDests file.

2.0.5
Bug Fix: Page count not being passed from CD Plus to OM Plus
Bug Fix: Jobs with a ‘E=’ in the –o options were not processed properly
Bug Fix: Background Status crashed when a group lookup was specified in the Java GUI

2.0.4
Bug Fix: HTML Interface was allowing all users to see all requests despite proper security settings
Bug Fix: Changed SAP/R3 interface so that it would properly purge jobs that had been transferred to another host
Bug Fix: New context file for CD Plus not being saved properly
Bug Fix: When purging, report file being deleted even if queue file is not successfully deleted

2.0.3
Bug Fix: RID Spans file not formatting correctly

2.0.2
Bug Fix: Log file would not display on HTML interface
New Feature: Background Status made multi-threaded to increase performance

2.0.1
Bug Fix: When datatype is pcl-1 spooling takes a long time
Bug Fix: Spooling would hang when a job had no title using Port Monitor
Bug Fix: FFE File not being set properly in Advanced Forms
Enhancement: HTML interface for Windows can now run on a different machine than the OM Plus Server
New Feature: Multiple OM Plus servers can now ‘advertise’ their defined destinations to each for enterprise wide print management (Replaces QA Plus)

1.6.9
Bug Fix: When ftp to a Windows NT machine, it would only support PASV  mode
Bug Fix: When re-starting active or retry status jobs, the status service crashes.

1.6.8
Enhancement: Changed copied requests. Copies of requests that are on hold are now also held instead of de-spooled immediately

1.6.7
Bug fix: Receiving wrong PJL return information due to Windows driver nesting PJL
Bug Fix: Fixed page counting for Postscript documents

1.6.6
Bug Fix: Corrected page count of PCL jobs

1.6.5
Bug Fix: Printer was timing out OM Plus’ connection while OM Plus was waiting on PJL confirmation
Added: MPCL to support Paxar label printers

1.6.4
Bug Fix: Archive program not returning correct results when searching by date
Bug Fix: Added support for the return code that an AS400 used when receiving FTP
Bug Fix: HTML interface caused a core dump when using the auto update  feature

1.6.2
Bug Fix: HTML interface showing only 4 digit RID number on Archive  screen

1.6.0
New Feature: Context Delivery Plus (CD Plus) and Report Bundler Plus (RB  Plus) now available
New Feature: Changed maximum number of characters in a destination’s name from 14 to 50
New Feature: Added Paxar mode so OM Plus could support bi-directional communication with Paxar printers

1.5.2
New Features: Can now do accurate page counting of PDF documents. No partial document restarting possible due to interpage dependencies
Changed advanced forms:  When printing to multiple destinations, command line options only affect the first destination, not all of them

1.5.1
Bug Fix: PJL confirmation page count was being incorrectly written to the accounting log
Bug Fix: lpadmin was updating the ‘form mounted’ field of the destination’s  configuration and not the ‘default form’

1.5.0
New Features: PJL Confirmation to Printer Now Available, QA Plus Available

1.4.4
Bug Fix: Filter crashed when used with FlexForm
Bug Fix: Data type set incorrectly when data was piped to dcclp
Bug Fix: Defining user to remote security did not work correctly

1.4.3
Enhancement: Java GUI Changed to display only 200 jobs at a time.

1.4.1
First Major OM Plus Release
Options Available:
HTML Interface, Java GUI Interface, Report Distributor Plus (RD Plus) and Archive.

Forum: OM Plus Version History for Windows ]]> http://plustechnologies.websitetoolbox.com/post?id=1731014 Tue, 27 Feb 2007 19:10:21 GMT http://plustechnologies.websitetoolbox.com/post?id=1720368 The change in date for the switchover to Daylight Savings Time will not affect OM Plus Server on any of the Operating System platforms it is currently installed on.

However, it will effect our Java based Client utility.

While the time for the server is correct, the Client utility may report it incorrectly.

Plus Technologies has made available a patch to the Java Run Time environment used to drive the Client utility.

It is recommended that this patch is used, as the Client utility uses a copy of the JRE installed into a specific directory and called by the Client from there. Upgrading the JRE on a specific system may not upgrade those files.

If you would like this patch, please send an email to support@plustechnologies.com and we will forward the patch to you.

After this has been completed, you may notice a slight difference in check boxes in the Status Screen.  The checks in the check boxes will only be visible if you mouse over them.

Forum: OM Plus - Q&A ]]> http://plustechnologies.websitetoolbox.com/post?id=1720368 Thu, 22 Feb 2007 19:30:40 GMT http://plustechnologies.websitetoolbox.com/post?id=1490682 After many years of ignoring the HTML interface  I noticed in the change logs that it has undergone a revamp lately. So, I have installed it here on my test system.

It does look a lot nicer!

I am wondering how to go about selecting a particular destination for viewing a smaller list of requests. I notice at the top the the page says "Lookup: All" but can't actually find a way of changing it! Any clues please?

Also, the Admin icon takes me to Destination Configuration only, and doesn't allow me to reach the URL page - I had one of my destinations URL configured just as the IP address without the http:// bit at the beginning which failed when clicking from the HTML interface, but I can't change it from within the HTML interface admin bit!

PS the forum is a great idea! Thanks.

Forum: OM Plus - User Interfaces ]]> http://plustechnologies.websitetoolbox.com/post?id=1490682 Fri, 03 Nov 2006 11:19:53 GMT http://plustechnologies.websitetoolbox.com/post?id=1489166

UNIX:

On UNIX/Linux systems the native LPD service is most likely already running as this is default on most systems.

As this service is not necessary to run OMP then you can feel free to edit the $LPHOME/shells/rc.omplus and edit out the lines that start our LPD service.  You should only need this service if you are going to use the LPD protocol to send data to OMP from another system.

If you do need to use the OMP LPD listener, then the following should help:

1). Do a ps –ef | grep lpd and that will be the process that is on port 515. This is your native LPD listener. Kill hat process and the OMP LPD should start.

2). Then you can vi the /etc/services file and search for and comment out what is on port 515, it should be the daemon 'printer'.

Windows:

A Windows system doesn't have any listener on port 515 by default, but if you install the TCP/IP Print Services for UNIX, then you may have issues as that service uses port 515.

Also, as the Windows system doesn't use port 515 normally this is usually a port blocked by firewalls and Anti-virus utilities.  This will not stop the OMP LPD service from listening on that port, but those utilities may stop the data stream from getting to the OMP LPD service.

Forum: OM Plus - Q&A ]]> http://plustechnologies.websitetoolbox.com/post?id=1489166 Thu, 02 Nov 2006 18:48:22 GMT http://plustechnologies.websitetoolbox.com/post?id=1488691 While it is always recommended that you have an up to date Anti-Virus utility installed on your production systems, that utility can sometimes effect the operation of OM Plus.

The first problem you might encounter connectivity issues with your OMP Interface.  This could be caused by the AV program blocking ports or slowing down response and causing timeout.

Also, some AV programs will monitor all disk access and all scripts when they execute.  As OMP is a spooler, it is constantly performing disk read/write actions. Also, many parts of the OMP process uses scripting to accomplish printer interface and behavioral actions and an AV program can slow the system down by stopping and scanning each action of each print.

This can cause system slowdown, out of order printing and general strange behavior.

Your AV program should be configured to ignore all file access and script execution without the OMP Home directory.

Forum: OM Plus - Q&A ]]> http://plustechnologies.websitetoolbox.com/post?id=1488691 Thu, 02 Nov 2006 15:43:51 GMT http://plustechnologies.websitetoolbox.com/post?id=1488496 Both the Client and Browser interface communicate with OM Plus via an IP connection to two status services/daemons.

An inability to connect, more often than not, is caused by the status components not being started or something interfering with the communication between the status components and OMP.

List of things to check:

1). Make sure Background Status and Admin Service has been started on OMP.

2). On the Client side, first make sure the IP or DNS to the OMP server has been addded in client configuration and that it is correct.

if you are using the Browser, cheek the omphtmlenv file.  This will be in the /cgi-bin/omplus directory if using IIS or in the /etc directory using a UNIX web server (Apache). If the host name of the OMP server is not in that file, then it will look locally. Make sure this information is correct.

3). Check on Firewalls and Anti-Virus utilities.  Both of these systems can block communication between OMP and the Interfaces. The default ports used are 53971 and 53974 if you need to configure your system to ignore OMP communication. if you would like, the Clients can be configured to use other ports.

It should be quite easy to test communication between OMP and the machine the Client is running on. First ping that machine. If that works, then try doing a telnet to the machine and the port that OMP is using. The telnet should connect, although you should not get a prompt.

Forum: OM Plus - User Interfaces ]]> http://plustechnologies.websitetoolbox.com/post?id=1488496 Thu, 02 Nov 2006 14:18:10 GMT http://plustechnologies.websitetoolbox.com/post?id=1437819 Every time a print job finishes, it deposits a file called exit????? in my tmp directory.  Is there any way to stop this?  Are they necessary?

Forum: OM Plus - Q&A ]]> http://plustechnologies.websitetoolbox.com/post?id=1437819 Wed, 11 Oct 2006 01:20:28 GMT http://plustechnologies.websitetoolbox.com/post?id=1327333 2.3.5 - 10/6/2009
JAVA Interface - 2.1.1.0059
Bug Fix: Jobs transferred to OMP via LPD where the control file and data file were not the same name generated NAK; LPD thought someone was sending more than one file. LPD listerner now accounts for it.
Bug Fix: Lock file created by 'dccbkst' has read-only permissions; this caused the lock file to not remove; the system would then not be able to start the service a second time. Logic has been fixed.
Bug Fix: HP UX on Itanium systems run 64-bit; OMP is a 32 bit program running compiled for that system. There were some shared memory issues that were cleaned up.
Bug Fix: JAVA GUI; when a copy Request was done to a block of Requests, they would all be copied to the Destination on the first Request.
Bug Fix: Timing problem between when Destinations are loaded into shared memory and the status service gets the list. This has been accounted for and corrected.
Bug Fix: The 'dcce2eser' service was staring 'zombie' processes, causing the service to not shut down correctly. This has been corrected.
Enhancement: Web Services programming interface is now available for the UNIX platform.
Enhancement: Customer 'status id's' are available using the Web Services interface for users to get status form their own job identifiers.
Enhancement: Page counting for PCL6/PCLXL data types.
Enhancement: New utility 'ompdest' to verify the existence of an OMP Destination from a script.
Enhancement: New utility 'ompqdepth' to return the number of jobs queued and ready on a specific Destination.
Enhancement: New utility 'ompresolve' will return the HOST/IP resolution of an OMP Server.
Enhancement: new utility 'omremsetup'; used to setup printer advertising via the command line / console.
Enhancement: Unidirectional OMPLUS mode to allow upstream jobs to purge without confirmation.
Enhancement: The 'dccpingrem' service will now operate in a 'proxy' mode; advertising both remote and local Destinations to OMP Agents.
Behavior Change: Destinations in 'bidirectional' mode will now remove multiple conflicting PJL statements that may exist in the job stream.

2.3.2 - 4/20/2009
JAVA Interface - 2.1.1.0058
Enhancement - New environment 'PICK_WAIT=y|Y' will signal the filter to wait until a label has been picked. NOTE: Zebra Printers, Termserv Mode, ZPL Bi-Directional setting.
Bug Fix: Fixed two issues where a job coming in LPD would spool only a 0 length file or the job plus a 0 length file.
Bug Fix: When 'Write Time' set to '0', job would end immediately instead of going on infinitely.
Behavior Change: Now ignore the 'DMINFO' PJL string.
Behavior Change: the 'e2e'servcies have been added to the 'dccshut' routine. ex. dccshut een, dccshut ees, dccshut e2e
Behavior Change: dcclpdci print messages added to printer trace log.
Behavior Change: SNMP Messages added to printer trace log even if community not set.
Enhancement: Lock files aded to $LPHOME/system for e2e services with an automatic restart if e2e crashes.
Enhancement: New SAP Interface; Direct Callback from SAp host(2).
Behavior Change: Environment added 'PJL_NEUTRALIZE' to remove PJL BOJ and EOJ from job in favor of the OMP version.

2.1.8 - 6/15/2006
Bug Fix: Now when the host is removed from the remotehost list, those printers are removed from the master destination list.

2.1.7 - 6/9/2006
Feature Added: HTML Updated - New graphics
Feature Added: When file named nographics in constants directory, graphics will type as simple.
Bug Fix: Email list was being replaced and not added to.

2.1.6 - 6/5/2006
Feature Added: New HTML Interface
Behavior Change: ECIV printer now not counted in total license.
Bug Fix: CD Plus STDIN bug fixed.
Bug Fix: dccshed form not initializing due to case matching.
Behavior Change: Added code to support OM Stats.

2.1.5 - 5/18/2006
Behavior Change: new page break logic for PCL data type
Feature Added: CD Plus now takes input from STDIN file.
Bug Fix: Page count with PDF data type.
Bug Fix: dccompser crashing
Feature Added: Minor code enhancements in dccompser
Behavior Change: permission set after the chown now during install

2.1.4 - 5/9/2006
Behavior Change: dccadmin system level file delete changed.
Feature Added: background status, added support for gzip compression.
Bug Fix: Fixed copy bug in dcccancel on parent / Child jobs
Bug Fix: dcclpdcli now adds quotes around title for so the Archive will be able to access data later.
Feature Added: user field added.
Feature Added: Added dccreindex utility.
Behavior Change: dccshed no longer logs error 859 when legacy QA Plus files not found.
Bug Fix: dccverify - fixed casing bug with UID's.

2.1.3 - 3/5/2006
Bug Fix: dcchealth now fixes permissions of scripts.

2.1.2 - 1/5/2006
Fixed Bug: If two jobs archives at the same second, one could try to save over the other causing error.
Feature Change: added TCP shutdown functions to background status
Behavior Change: Changes Parent / Child default flag
Bug Fix: Restart of Parent / Child would create new children. Now restarts old children.
Behavior Change: LP admin change. Change how it deletes files.
Bug Fix: Page counting issue with PCL
Feature Added: CD Plus regex support
Feature Added: CD Plus Context file now memory mapped.
Bug Fixed: Changed dcccancel to cancel whole family in Parent Child job.
Behavior Change: Changed the way dccadmin does a file open.
Behavior Change: ECIV printers now do not disable on error.
Bug Fix: Admin flag not set for admin button in HTML interface. Button was not grayed out (still not accessible)
Behavior Change: Native lpr is renamed lpr.old and now also lpr.lpp.
Behavior Change: dccnetstat no longer needs tcp bind
Behavior Change: dccpingrem now loads printers from disk.
Feature Added: CD Plus now can now look up HOST.

2.1.1 - 10/5/2005
New Feature: Print job Parent / Child system.
New Feature: Single sign security system for OMP / JAVA GUI
New Feature: ECIV mode printer.

2.0.5 - 7/20/2004
Bug Fix: File permissions on enable and disable were not properly set
Bug Fix: Translating ‘h’ to ‘H’ in vertical cursor position PCL sequence when receiving data on standard in
Bug Fix: $LPHOME/bundle directory not being created by default
Bug Fix: Character based view program not authenticating user properly
Bug Fix: Advanced form error when sending entire copy of a request to 2 destinations on Linux
Bug Fix: Jobs set for future printing cause dcclp to accept 0 length requests
Bug Fix: Destination changes issued from within the spooler event script are displayed, but job goes to original destination
Bug Fix: Jobs with a ‘E=’ in the –o options were not processed properly
Bug Fix: Background Status crashed when a group lookup was specified in the Java GUI
Enhancement: Background Status now has separate buffers for send and receive to reduce chance of corruption

2.0.4 - 3/32/2004
Bug Fix: HTML Interface was allowing all users to see all requests despite proper security settings
Bug Fix: Deleting a printer using the character based interface could cause the terminal to lock up
Bug Fix: Changed SAP/R3 interface so that it would properly purge jobs that had been transferred to another host
Bug Fix: Lines per page defaulting wrong on a undefined form
Bug Fix: When purging, report file being deleted even if queue file is not successfully deleted

2.0.3 - 2/23/2004
Bug Fix: Getting permission denied when adding a new printer
Bug Fix: Servers whose names end in ‘sap’ report the scheduler as being down
Bug Fix: dccpingrem is leaving zombie processes in the process queue
Bug Fix: Jobs to default printer do not display properly in dccstat
Bug Fix: When HTML interface is sorted by user, it splits the requests across multiple pages
Bug Fix: Cannot print to locally attached devices

2.0.2 - 1/29/2004
Bug Fix: When viewing a job on a SCO system every other line is not displayed. Set VIEWLTR environment variable
Bug Fix: Changes to RD Plus to properly handle no-match jobs
Bug Fix: Jobs with selected Translation Tables were not having all copies of the job translated
Bug Fix: Slow printer was timing out and going interrupted
Bug Fix: Printers screen in dccstat causes dccstat to exit

2.0.1 - 12/30/2003
Bug Fix: When datatype is pcl-1 spooling takes a long time
Bug Fix: Email address getting dropped from email requests
Bug Fix: Page count displaying wrong in dccstat
Bug Fix: Request -o options are being truncated when spooled from archive system
Bug Fix: Copy request from GUI not function on UNIX servers
Bug Fix: Users cannot update email addresses in dccstat
Bug Fix: Install script for HP/UX now functions properly
Enhancement: Time stamp added to the Archive screen in the OM Plus Java GUI
Enhancement: Majority of OM Plus on UNIX files are now owned by a user other than root
New Feature: Multiple OM Plus servers can now ‘advertise’ their defined destinations to each for for enterprise wide print management
New Feature: Customizable logging of OM Plus system messages
New Feature: Lookup of OM Plus System message numbers and OS specific error numbers

1.6.8
Enhancement: Changed copied requests. Copies of requests that are on hold are now also  held instead of de-spooled immediately

1.6.7
Bug Fix: Fixed page counting for Postscript documents
Bug Fix: Fixed broken link and job title on HTML interface

1.6.6
Bug Fix: Corrected page count of PCL jobs

1.6.5
Bug Fix: Printer was timing out OM Plus’ connection while OM Plus was waiting  on PJL confirmation
New feature: Added MPCL to support Paxar label printers
Behavior Change: Separated error coded for gethostbyname and Config

1.6.4
Bug Fix: Archive program not returning correct results when searching by date
Bug Fix: Added support for the return code that an AS400 used when receiving FTP
Bug Fix: HTML interface caused a core dump when using the auto update feature

1.6.2
Bug Fix: HTML interface showing only 4 digit RID number on Archive screen.

1.6.0
New Features: Context Delivery Plus (CD Plus) and Report Bundler Plus (RB  Plus) now availableChanged maximum number of characters in a destination’s name from 14 to 50 Added Paxar mode so OM Plus could support bi-directional communication with Paxar printers

1.5.2
New Features: Can now do accurate page counting of PDF documents. No partial document restarting possible due to interpage dependencies.
Changed advanced forms.  When printing to multiple destinations, command line options only affect the first destination, not all destinations.

1.5.1
Bug Fix: PJL confirmation page count was being incorrectly written to the accounting log
Bug Fix: After issuing the SU command, the wrong user is assigned to spooled jobs
Bug Fix: lpadmin was updating the ‘form mounted’ field of the destinations configuration and not the ‘default form’

1.5.0
New Features, PJL Confirmation to Printer Now Available, QA Plus Now Available
Bug Fix: File permission set improperly causing remote installations to fail

1.4.5
Bug Fix: Possible memory leak in dccprint when using OM Plus mode destinations.

1.4.4
Bug Fix: Filter crashed when used with FlexForm
Bug Fix: Data type set incorrectly when data was piped to dcclp
Bug Fix: LPHOME variable improperly loaded when modifying a translation table
Bug Fix: Defining user to remote security did not work correctly

Forum: OM Plus Version History for UNIX/LINUX ]]> http://plustechnologies.websitetoolbox.com/post?id=1327333 Mon, 21 Aug 2006 18:52:41 GMT