Management Overview of
ROLO/XPFC V3R1
V3R1 of ROLO/XPFC is functionally identical to the latest ROLO/XPFC
release (V2R3), but there are TWO major changes to the external operational interface and
an important new feature which will provide support for VIPP enabled (DocuPrint) laser
printers.
V3R1 is fully upwards compatible with previous versions of
ROLO/XPFC, no changes are required to existing Configurator Files.
Use of the C Compiler
Previous versions made "secret" use of the C Compiler in the
configurate and make processes ...... V3R1 no longer requires access to the C Compiler at
any time.
This change was partly provoked by IBM's decision to make the C
Compiler a chargeable item from AIX V4 onwards !
If you have integrated ROLO/XPFC with your own printer/server
control system, then you will need to modify the scripts that provide the update service
for adopting updated Configurator Files.
There is now no requirement to run the make process because the
ROLO/XPFC run-time code will use the new format Configurator File created by the new V3R1
configurate utility.
New V3R1 options now also allow you to specify the input and output
Configurator File(s), this is to support the new "Multiple Configurator File"
feature which is described next.
Support for Multiple (Mode) Configurator
Files
New V3R1 options with the configurate utility now allow you to specify
the names for the input and output Configurator Files via command line parameters.
The -f filename parameter specifies the input (source)
Configurator File, whilst the -c filename parameter specifies the output (run-time)
Configurator File.
Similar parameters also allow naming of both the cross reference
listing ( > ?????? ) and the error report ( 2> ?????? ).
From V3R1 onwards the Configurator File to be used at run-time is
specified explicitly on the ROLO/XPFC command line via the -o cfile ??????
parameter.
Although introduced as part of the DJDE/VIPP support feature, the
Multiple Configurator File feature is also eminently suitable for driving mixed printer
types alongside each other, such as 4090 and 4890. Now you can drive each printer
according to your PRECISE needs, without having to compromise on laser controls previously
held in a single Configurator File across the two different printing regimes (such as the
B&W 4090 and the spot color 4890).
And testing becomes easier too, with V3R1 introducing the concept of
Test Configurator File(s) and separate Production Configurator File(s).
Support for VIPP Enabled Printers
VIPP support is provided from V3R1 onwards of ROLO/XPFC. There are also
various enhancements to the syntax/language used in the Configurator File to support use
of VIPP controls/processing in a user-friendly style, these are documented separately.
Both VIPP and DJDE handling capabilities are provided within the
single ROLO/XPFC system for those users requiring both types of laser control.
Installation management must maintain discrete Configurator Files,
one (group ??) specifying DJDE controls, and the other (group ??) specifying VIPP controls.
Perhaps now you can appreciate the case for the other V3R1 enhancement which provides for
multiple/mixed Configurator Files !
Each Configurator File can be created using a site specified name,
and subsequently connected at run-time by supplying the appropriate names on the command
line where ROLO/XPFC is invoked.
For Example .......
A user site has two Xerox printers, one being a regular 4090 and the other a DocuPrint
4890.
Simple ...... create two separate Configurator Files, each
one specifically engineered for the target printer and simply connect the relevant one to
the image of ROLO/XPFC driving each printer.
ROLO/XPFC V3R1 for Windows NT
Remember Partner Briefing No 42 ?
V3R1 of ROLO/XPFC will form the base for the NT version ........ so
all these features are available for the first release of ROLO/XPFC for Windows NT ! |