In order for openUTM to use the OLTP interface of RSO, RSO and the software products required by RSO must be installed. The RSO subsystem must be active. If you have specific questions, read the RSO manual:
Device definition
With the UTM tool SPSERVE, you open the SPOOL parameter file for the printer definition. The system administrator must configure the printer in RSO for UTM print jobs:
ADD-SPOOL-DEVICE...ADMINISTRATOR=*ADMINISTRATOR(...),
PROCESSING-CONTROL=*PAR(
DISCONNETION=*YES
RESET={*YES | *NO }
CONTROLLER-START=AT-PRINTER-START)
If a new printer is configured, up to 8 RSO device managers can be entered with the parameter ADMINISTRATOR=*ADMINISTRATOR(...). An RSO device manager can modify a device with MODIFY-SPOOL-DEVICE or start a DEVICE with START-PRINTER-OUTPUT.
It is advisable to work with the parameter DISCONNECT=*YES, because with SOCKETS the printer shuts down the connection when the time set on the printer has expired.
The parameter CONTROLLER-START must be set to AT-PRINTER-START.
If RESET=*YES, the settings of the printer menu are used. This also applies regardless of the device entry if openUTM is working with formats. If “logical” formats are used (see note at the end of the section) then openUTM behaves as if no formats are used.
If a format name is transferred by openUTM with an FPUT in the KCMF field, a RESET=*YES is sent by default to the printer by FHS before the message, so that the menu setting of the printer comes into effect before printing. In the printer menu you can set various fonts or CPI values, for example. In this case, RSO processes a message with format names as per the setting CONTROL=TRANSPARENT.
If no format name is transferred by openUTM with an FPUT in the KCMF field, RSO only sends a RESET to the printer before the message if RESET=*YES is entered in the device definition. If no RESET was sent to the printer, the applicable values are the printer menu values currently set on the printer, which may have been changed by a previous print job. RSO handles a printer message without format names as per the setting CONTROL=PHYSICAL.
The commands ADD-SPOOL-FORM for form entries and ADD-SPOOL-CHARACTER for character sets have no effect on UTM print jobs. If both UTM RSO print jobs and RSO SPOOLOUT are processed under the same logical RSO device name, forms and character sets are only relevant for the latter. As the only printer control character, RSO adds the RESET character string for UTM print jobs.
A UTM print job to an RSO printer is not placed in the SPOOL queue.
Sample device entry
Output of a device entry under which the printer is defined for RSO:
/show-spool-dev PGTP0041,inf=*all
DEVICE-NAME : PGTP0041
DEVICE-TYPE : 9021RP
-------------------------------- DEVICE-ACCESS ------------------------------
DEVICE-ACCESS : *TCP-ACCESS
ACCESS-TYPE : *TACLAN
PROCESSOR-NAME : *NONE
STATION-NAME : *NONE
MNEMONIC-NAME : *NONE
PROGRAM-NAME : *NONE
INTERNET-ADDRESS : PGTP0041
PORT-NAME : 9100
LPD-PRINTER-NAME : *NONE
FROM-PORT-NUMBER : 0
TO-PORT-NUMBER : 0
------------------------------- TWIN-DEVICE-DEF -----------------------------
SLAVE-MNEMONIC-NAME : *NONE
ESD-SIZE : 0
----------------------------- DEVICE-INFORMATION ----------------------------
FORMS-OVERLAY-BUFFER: 32767
CHARACTER-SET-NUMBER: 64
ROTATION : NO
DUPLEX-PROCESSING : NO
FORMS-OVERLAY : NO
RASTER-PATTERN-MEM : *NONE
TRANSMISSION : IGN
FONT-TYPE : IGN
FACE-PROCESSING : NO
MAXIMUM-INPUT-TRAY : 1
MONJV : NO
NOTIFICATION : NO
ENCRYPTION : NO
UNICODE : NO
SUPP-FORMAT-NAME :
TEXT
PLAIN-TEXT
-------------------------------- ADMINISTRATOR ------------------------------
USER-IDENTIFICATION : *NONE
IDENTIFICATION : OEC MW 135
TERMINAL : PROCESSOR-NAME :
STATION-NAME :
------------------------------ SPOOLOUT-CONTROL -----------------------------
SHIFT : 0
LINE-FEED-COMPRESS : YES
BLANK-COMPRESSION : YES
START-FORM-FEED : YES
FORM-FEED : *SINGLE-SHEET
DEFAULT-TRAY-NUMBER : 1
OUTPUT-TRAY-NUMBER : 0
SKIP-TO-NEXT-PAGE : BY-FORM-FEED
ESCAPE-VALUE : NONE
----------------------------- PROCESSING-CONTROL ----------------------------
CONTROLLER-RESERVED : NO
FORM-NAME : STD
DISCONNECTION : YES
BUFFER-SIZE : 1024
RESET : YES
REPEAT-MESSAGE : TYPE : SYS
LIMIT : NO
RETRY-TIME : GLB
RESTART-ACTION : LIMIT : NO
RETRY-TIME : GLB
SYNCHRONIZATION : PRINTER
TIMEOUT-MAX : 2
PAGE-EJECT-TIMEOUT : NO
BAND-IDENTIFICATION : *NONE
LOAD : NO
MODULO2 : NO
RECOVERY-RULES : *SYSTEM
POLLING : NO
PRINTER-PARAM-FILE : *SYSTEM
RESOURCE-FILE-PREFIX: *SYSTEM
CONTROLLER-START : AT-PRINTER-START
------------------------------ CHARACTER-SET-POS ----------------------------
POSITION-1 : N-U
POSITION-2 : N-U
POSITION-3 : N-U
POSITION-4 : N-U
POSITION-5 : N-U
POSITION-6 : N-U
POSITION-7 : N-U
POSITION-8 : N-U
POSITION-9 : N-U
POSITION-10 : N-U
POSITION-11 : N-U
POSITION-12 : N-U
POSITION-13 : N-U
POSITION-14 : N-U
POSITION-15 : N-U
POSITION-16 : N-U
-------------------------------- MISCELLANEOUS ------------------------------
REDIRECTION-DEVICE : *NONE
LANGUAGE-EXT-TYPE : *SYSTEM
LINE-SIZE : 150
CHARACTER-IMAGE : *NONE
Defining the RSO buffer size
To be able to print out messages of any length, the RSO buffer must be greater than or equal to the maximum message length in openUTM. Since the maximum value for the UTM buffer size is 32 KB, the RSO buffer size in a session in which openUTM is running, must be adapted to this value:
/MODIFY-SPOOL-PARAMETER...SPOOLOUT-OPTIONS=*PAR(REMOTE-BUFFER-SIZE=32)
Any modification will come into effect in the next SPOOL session.
VTSU codes
When UTM messages containing VTSU codes are output to printers connected directly via BCAM, openUTM calls the VTSU program in order to convert VTSU codes into printer dependent escape sequences. If UTM messages are output to RSO printers, the conversion of the VTSU codes is carried out by RSO. An extensive adaptation to the known VTSU control characters was striven for in this case. Additional information can be found in the RSO manual.