PRINTER SETUP IN jBASE AND T24

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.
Printer Set Up In jBASE And T24

Table of Content
Table of Content ................................................................................................................................... 2
Printer Setup in jBASE.......................................................................................................................... 3
Device Types................................................................................................................................. 3
Creation And Maintenance Of Form Queues ................................................................................. 3
Setting A Printer As Default Printer................................................................................................ 3
SP-NEWTAB ................................................................................................................................. 3
REST-SPOOLER .......................................................................................................................... 3
Obtaining spooler information ........................................................................................................ 3
Display Print Jobs For A Specific Port Number.............................................................................. 3
Display Print Jobs For A Specific Formqueue................................................................................ 3
Display Print Jobs For A Specific Status........................................................................................ 3
Deleting Form Queues................................................................................................................... 3
Form Queue Security..................................................................................................................... 3
Formqueue De-activation and Re-assignment............................................................................... 3
Printer Setup In T24 .......................................................................................................................... 3

TEMENOS Training Publications Page 2 of 13 November 2005

T2MBTT – R05 – 1.0
Printer Set Up In jBASE And T24

Printer Setup in jBASE

It is very vital to understand the fact that, it is only the operating system that can print. An application
(Globus) or a database (uniVerse/jBASE) cannot print. They merely redirect the print jobs to the
operating system.
As you would be aware by now, there is no layer that separates the operating system (Unix) and the
database (jBase). Therefore all the operating system level printers are available in jBase.
In Windows, when we wish to install a printer we would normally choose the ‘Add Printer’ icon and
proceed. Once done, a logical printer would get created which would actually point to a physical
printer that could be connected to that specific machine or it could be a network printer. In jBase, we
create from queues. Form queues are like the logical printers that get created in Windows. They would
point to a physical printer device.
To install a printer in jBase, a printer must be installed at the Unix level. Once installed at the Unix
level, note down the name of the printer and the device file associated with it. Device files will be
located in the /dev directory.

Device Types
Every form queue created n jBase will have a device type associated with t. Following are the various
device types supported by jBase.

LPTR
Logical devices for form queues Specifies a direct UNIX device name. A background despooler
sssdaemon outputs the print jobs directly to the specified device.

For example: LPTR /dev/lptr

will write data from the print jobs directly to file /dev/lptr.

PROG
Logical devices for form queues Specifies an external UNIX program. A background despooler
daemon pipes data from the print jobs to the command line.

For example: PROG rsh HostId -l spooler lp -d devicename

will pipe the print job data to remote connection HostId for user spooler and output to device device
name.

PORT
Logical devices for form queues Specifies a port device.

For example: PORT /dev/tty8b

queues the print jobs for output to port /dev/tty8b. Print jobs are despooled locally with the PORT-
DESPOOL command.

TEMENOS Training Publications Page 3 of 13 November 2005

T2MBTT – R05 – 1.0
Printer Set Up In jBASE And T24

TAPE
Logical devices for formqueues Specifies a tape device configured in the jBASE devices file.

For example: TAPE SCT0

will assign streaming cartridge tape device 0.

Creation And Maintenance Of Form Queues

SP-STATUS
SP-STATUS is a menu driven utility in jBase that helps us to install printers at the jBase level and
also manage them.

Creating A Formqueue (Option 1 CREATE FORMQUEUE)

We could create a form queues in jBase using the ‘Create Formqueue’ option in
the SP-STATUS menu or by using the SP-CREATE command.

Example
SP-CREATE TRG LPTR /dev/lptr

will create the formqueue TRG and assign it to logical device type LPTR. LPTR is associated with
device /dev/lptr which will receive the output print job data.

TEMENOS Training Publications Page 4 of 13 November 2005

T2MBTT – R05 – 1.0
Printer Set Up In jBASE And T24

Changing The Device Type(Option 4 CHANGE DEVICE)

Formqueue TRG could then be reassigned to any alternative logical device type by using the SP-
DEVICE command (or the change device option from the SP-STATUS menu)

Example
SP-DEVICE PAYROLL PORT /dev/tty8b

Setting A Printer As Default Printer

The SP-ASSIGN command is used to a assign a printer as the default printer and also used to set the
spooler options and number of copies. (This is the equivalent of the SETPTR command in uniVerse)

Syntax
SP-ASSIGN {formqueue} {options} {copies}

Syntax Elements
formqueue defines the name of the formqueue to which print jobs are queued. The
default formqueue is STANDARD.

options define the spooler assignment options which will be assigned to the
subsequent print jobs when queued to . ? displays current assignment.

copies defines the number of copies of the print report data are required to be output.

SP-NEWTAB
This is the command that is used to initialise the spooler environment in jBASE. This command can
be executed by root or a root equivalent only. It is normally executed after the jBASE installation. It
creates a new spooler structure. As you would be aware by now the JBCSPOOLERDIR is the
environmental variable in jBase that contains the path of the jspooler directory. This command once
executed, creates the jspooler directory under the path pointed by the JBCSPOOLERDIR variable and
created the following under the jspooler directory

a. A non hashed file named jobs

b. A hashed file name jspool_log

TEMENOS Training Publications Page 5 of 13 November 2005

T2MBTT – R05 – 1.0
Printer Set Up In jBASE And T24

jobs
The jobs directory contains the entries as below.

formqueue_0
formqueue_1

Each of the entries refer to a form queue. Formqueue_0 refers to the standard formqueue.

jspool_log
Prints jobs are identified by number. The jBASE spooler uses a control record in the jspool_log file -
NextJobNumber - to assign print job numbers. The structure of this record is:

<1> Date job number was last reset

<2> Next job number to be assigned

When a job is created, this record is read (and locked) by the spooler. If the date in attribute 1 does
not match the current date (or the control record does not exist) then the counter in attribute 2 is reset
to 1 and the current date is assigned to attribute 1.

The counter is then used to check if a print job with that number already exists. It is incremented and
re-checked until an unused number is determined. In this way, gaps in the job number sequence that
occur because old jobs are deleted, are filled by new jobs generated on subsequent days.

When an unused number is determined, it is assigned to the print job and the counter is incremented
for the next job that is created.

The default directory in which the spooler files are created is called jspooler however SP-NEWTAB
allows a different directory to be specified. Before the spooler can be accessed by a user, it's location
must be specified using the environment variable JBCSPOOLERDIR. SP-NEWTAB allows security
settings for form queues and print jobs. The SP-NEWTAB command does not kill despooling daemons.
If a process was assigned to any formqueue other than STANDARD when the SP-NEWTAB
command was executed, the process will be assigned to NO QUEUE. The default formqueue
STANDARD is re-initialized with a LPTR logical device type.

TEMENOS Training Publications Page 6 of 13 November 2005

T2MBTT – R05 – 1.0
Printer Set Up In jBASE And T24

REST-SPOOLER
When ever a form queue is created in jBase and assigned to a particular device, a background
process by name ‘jspprint’ gets initiated in the background for that form queue. The REST-SPOOLER
command, when executed starts a jspprint process for every form queue which does not have an
already active jspprint process in the background. (In uniVerse, irrespective of the number of
formqueues, there would be only one background process to handle all print requests that come to
uniVerse.)

Obtaining spooler information

jspstatus
The jspstatus command s used to obtain the spooler information.

jspstatus 1 Display device information. Option (R displays real user ids)

jspstatus 2 Display print job information
jspstatus 3 Display assignment information
jspstatus 4 Display open job information

SP-JOBS

The SP-JOBS screen displays a list of print jobs together with their status and formqueue assignment.
Each action code, except code 99, corresponds to a jBASE command that performs the same function.

Note: The SP-JOBS command displays only the print jobs associated with the jBASE spooler. The
command does not display information about the UNIX spooler.
TEMENOS Training Publications Page 7 of 13 November 2005
T2MBTT – R05 – 1.0
Printer Set Up In jBASE And T24

Option 1 : Move print jobs from one form queue to another

Prompt : FROM-FORM-QUEUE TO-FORM-QUEUE:
Enter the form queue to move print jobs from, a space, and the form queue to move the print jobs to.
You will be prompted for any missing parameters.

Display Print Jobs For A Specific Port Number

Print jobs can be filtered to display only those jobs generated from a specific port number. At the
Action Code / Options prompt, enter PT followed by a port number

Example : PT 42

will display the first page of print jobs generated from port 42.

Display Print Jobs For A Specific Formqueue

Print jobs can be filtered to display only those jobs belonging to a specific form queue. Enter Q
followed by a the name of a form queue

Example : Q TRG

will display the first page of print jobs belonging to the TRG form queue.

Display Print Jobs For A Specific Status

Print jobs can be filtered to display only those jobs with a specific STATUS. Enter S followed by a
status of either QUEUED, PRINT, FINISH, OPEN, HOLD, KILLED or EDIT.

Example : S FNSH

will display the first page of print jobs whose current status is FINISH indicating all jobs which have
been completely despooled.

Deleting Form Queues

SP-FQDELETE
This command is used to delete form queues.
SP-FQDELETE formqueue
A formqueue cannot be deleted if the formqueue is not empty or the formqueue is assigned to a
logical device type. The formqueue should be changed to a device type of zero and any print jobs
either deleted or reassigned to another formqueue. Any processes currently assigned to the deleted
formqueue will change to NO QUEUE and any attempt to spool a job will display an error message.

TEMENOS Training Publications Page 8 of 13 November 2005

T2MBTT – R05 – 1.0
Printer Set Up In jBASE And T24

SP-PURGEQ
This command purges a formqueue of a specific print or all print jobs. This command will delete the
print job or jobs irrespective of status. If all jobs are requested the jspprint process for that form queue
wll also be stopped.

SP-PURGEQ FORM-QUEUE PRINT JOB LIST (OR * FOR ALL):

Note : This command can only be run by root (Unix) or an Administrator (NT).

Form Queue Security

SP-SECURITY
This is a menu driven interface to the previously mentioned SPSECURITY- xx commands. It is also
available from option 11 of SPSTATUS. When run, it presents the user with a screen that looks like
this:

The above screen will show up to 10 form queues at a time. The 4 fields shown for each form queue
are as follows:

QUEUE NAME This is the name of the form queue.

Queue This is the security for the form queue, and can be one of three

TEMENOS Training Publications Page 9 of 13 November 2005

T2MBTT – R05 – 1.0
Printer Set Up In jBASE And T24

possibilities.
-none- There is no security and any user can modify the definition of the
form queue.
-q.owners- The security state is such that all the form queue owners
shown in the field "Queue Owners" have permissions to modify
the form queue.
accname -This is the account name of the creator of the form queue, and
only this user has permission to modify the form queue.
Job This is the security for the print jobs , and can be one of three
possibilities:
-none- There is no security and any user can modify or view print jobs
placed on this form queue.
-q.owners- The security state is such that all the form queue owners
shown in the field "Queue Owners" have permissions to modify
or view any jobs placed on this form queue.
-j.creator- The security state is such that only the print job creator has
permissions to modify or view the print job.
Queue Owners This is a list of the owners of the form queue. The first name in the list is
the creator of the form queue and cannot be modified. The other names
in the queue and cannot be modified. The other names in the list are the
alternate form queue owners.

Menu Options

Option 1 QUEUE SECURITY

Use this option to modify the security state of the form queue. The syntax of the remainder of the
command is similar to the SP-SECURITY-QUEUE command.

Option 2 JOB SECURITY

Use this option to modify the security state of print jobs placed on the form queue. The syntax of the
remainder of the command is similar to the SP-SECURITYJOBS command.

Option 3 QUEUE OWNERS

Use this option to modify the list of alternative owners of a form queue. This list of owners is used
when the form queue security is set to QUEUE or the print job security is set to QUEUE. The syntax of
the remainder of the command is similar to the SP-SECURITY-OWNER command.

TEMENOS Training Publications Page 10 of 13 November 2005

T2MBTT – R05 – 1.0
Printer Set Up In jBASE And T24

Option 4 RETURN TO SP-JOBS

Returns to the SP-JOBS menu

Option 5 RETURN TO SP-STATUS

Returns to the SP-STATUS menu.

Option 99 EXIT
Exits the SP-SECURITY menu back to the shell

Formqueue De-activation and Re-assignment

A formqueue can be de-activated and re-assigned to another available logical device without having to
be stopped and restarted. After reassignment the next print job to be despoiled will be directed to the
new logical device type. For example, if formqueue REPORTS is despooling to logical device type
PROG lp -d lptr and you issue the command:

SP-DEVICE REPORTS PROG lp -d laser

the next and all subsequent print jobs will be output to the logical device PROG lp -d laser. In other
words, the command will redirect REPORTS to the UNIX spooler lp for device name laser.

TEMENOS Training Publications Page 11 of 13 November 2005

T2MBTT – R05 – 1.0
Printer Set Up In jBASE And T24

Printer Setup In T24

Now to the final step is to configure printer in Globus. Following are the key printer related files in T24
PRINTER.ID
DE.FORM.TYPE

PRINTER.ID
This file is used to define the valid printers on the system. It used both to validate the entry of a printer
id and to determine the physical destination of the output. A 'SYSTEM' entry must exist on this file.
This is used as the default for all output. An entry of HOLD can be set up. This special entry will hold
all output in the &HOLD& file and not spool the output.

Name of the physical

Unix level printer

DE.FORM.TYPE
The Form Type Table defines the width and depth of each printed form, and states which printer it is
produced on. It is also used to specify output format for tabular FILE output from ENQUIRY.REPORT.
A separate record on this table is required for each type of stationery on each printer. Whenever a
new Form Type is used two new files will automatically be created for processing the Formatted
Message Queue for that Form Type.
Example

Note the link between the

PRINTER.ID application
and the DE.FORM.TYPE
application

TEMENOS Training Publications Page 12 of 13 November 2005

T2MBTT – R05 – 1.0
Printer Set Up In jBASE And T24

When a print command is invoked in Globus from a DEAL SLIP/BATCH application etc, depending on
the application that it is being invoked from, the REPORT.CONTROL file or the User profile is read
and the DE.FORM.TYPE id is obtained and the corresponding record is read. From the
DE.FORM.TYPE record, the id of the PRINTER.ID application is obtained and the attributes of the
form are loaded. Then the PRINTER.ID application is read to determine the physical Unix level printer
name. Once the Unix printer name is obtained, the control goes to jBase where a formqueue with the
same name as that of the value in the PRIME.PRINTER.ID in the PRINTER.ID application. Once the
form queue is obtained, depending on the device type, the printing to the physical Unix level printer
happens.

TEMENOS Training Publications Page 13 of 13 November 2005

T2MBTT – R05 – 1.0