Configure printer as server printer in jBASE and T24

5/22/2020 How to configure the printer as server printer at both jBASE level and T24 level?
How to conﬁgure the printer as server printer at both jBASE

level and T24 level?
Introduction
This document describes the procedure to setup printer at both jBASE level and T24 level.
Procedure
At Jbase level:
Check if the server printer has been installed by trying to print a file from the shell prompt level
Check the printer spooler list and this indicates the availability of the printer for the particular server. Type 'lpstat'
Now create 'Form Queue' at jbase level

In the jsh prompt type SP-STATUS
The queues will be displayed as below:
Type option 1
Type the Form Queue name in DEVICE NAME
In DEV Type input the appropriate device type along with the printer name
https://tcsp.temenos.com/HowTo/SetupPrinter.aspx 1/9
The queues list will now include the new form queue created as seen above.
Now the STATUS is as KILLED and in order to start the same, exit the SP-STATUS window using option 99 and then
enter the SP-STATUS command at jsh prompt
At T24 level:
Log into T24 and create a record in the application PRINTER.ID (also you may try using an existing one rather than
creating)
Now update the PRINTER.ID (record ID) in the USER profile. This is to set-up printing options at the user profile
level (specific to user, which will ensure that the reports that are assigned to be printed will always be spooled to
the server printer)
In order to ensure that the reports / records printer using print function are spooled to the server printer, the field
PRINTER.ID in the record "SYSTEM" belonging to the file DE.FORM.TYPE should be made null. I.e. the value that
exists in the field PRINTER.ID as in the screenshot below, should be removed.
Since the printer set-up test is being carried out, check the spooler queue prior to printing new reports. It may be
observed in the screenshot below that there are two reports awaiting to be printed
Now log into T24 using the sign on of the user in whose profile the printer id is set-up and print the SPF record
using P function>
It may be observed in the screenshot below that the record is printed
Now check the printer spooler list using the 'lpstat' command and you may get to observe that one more report
has got added to the already existing spooler list
Printing from the ENQUIRY.REPORT record: The MB.ACCOUNT.STATEMENT is printed from the ENQUIRY.REPORT
file using the VERIFY function
Prior to verifying the ENQUIRY.REPORT record 'MB.ACCOUNT.STATEMENT', kindly ensure that the PRINTER.ID field
in the DE.FORM.TYPE record STMT is made null.
NOTE: The link from the ENQUIRY.REPORT to the DE.FORM.TYPE can be established using the link
ENQUIRY.REPORT>REPORT.CONTROL>FORM.NAME>PRINTER.ID
Now check the 'lpstat' to observe that the printer request from the ENQUIRY.REPORT has got updated to the server
printer spooler list
Redirecting an enquiry output to the printer:

In the enquiry selection criteria page update the field PRINT as 'Y'. Refer screenshot below:
Now check the 'lpstat' to view the spooler list and you can get to observe that the request redirected from the
enquiry has got updated in the list
Printing set-up at Batch level:

During "COB process" / "execution of Services", if all the reports pertaining to any particular BATCH process needs
to be printed then the field DEFAULT.PRINTER in the particular BATCH record will have to assigned the PRINTER.ID.
(Care to be taken to ensure that the field PRINTER.ID in the corresponding DE.FORM.TYPE record is null)
During "COB process" / "execution of Services", if a report pertaining to any particular job associated with the
BATCH process needs to be printed then the field PRINTER.NAME (this will be part of the associated multi-value set
relating to JOB.NAME) in the particular BATCH record will have to be assigned the PRINTER.ID. (Care to be taken to
ensure that the field PRINTER.ID in the corresponding DE.FORM.TYPE record is null)
Routing the report:

If a particular report needs to be redirected to a specific directory, then the essential set-up will have to done at the
PRINTER.ID file level.
In the example quoted here, the report is to be redirected to a sub-directory BMI.BP within the T24 home path
(bnk.run). The field COMMAND in the PRINTER.ID file will have to be used for the same. If multiple commands are
to be executed, then the field will have to be multi-valued. If any one particular command is big in length then the
field can be sub-valued to accommodate the same. Refer screenshot below:
In the first command, the file is redirected to the directory BMI.BP with a new name which is formatted as follows:
@ID&-&HOLD.CONTROL>REPORT.NAME&-&HOLD.CONTROL>COMPANY.ID& refers to &HOLD& record ID-
REPORT.NAME-COMPANY.ID (the REPORT.NAME / COMPANY.ID are fetched from within the HOLD.CONTROL
record)
In the second command, the file is redirected to the sub-directory "ACCT/REPORT" within the T24 home path
(bnk.run)
Other associated jbase form queue commands:

SP-ASSIGN
The above command will assign any particular form queue (in this case UAT5PRINT) to the particular unix session.
However this is not applicable to be assigned in case anything needs to be printer from within T24.
Now that we have assigned the form queue to the session, if any print at the jbase level needs to be redirected to the
printer spooler, the same can be achieved. For example refer below:

Post the execution of the CP command at the jsh prompt level, we can get to observe that the request has been updated
to the spooler list.
The above can also be achieved using the SPOOL command. Refer below:
SP-SUSPEND
Any form queue can be suspended using the SP-SUSPEND command. When a form queue is suspended, any report
printed will be move to the form queue at the jbase level, but will not be spooled to server printer
The above command is generally used to check if the settings are done as required at the T24 level prior to printing the
reports. This can be checked by printing and observing by executing the SP-STATUS command to check if the report
printed is actually assigned to form queue.
Now execute the SP-STATUS command.

In the screenshot below, it may be observed that the column "Q" associated with the form queue UAT5PRINT is
incremented by 1.

In may be observed that the server printer spool list has not been updated in the above case.
Now if the particular form queue is moved to the ASSIGNED STATUS then the particular report will be redirected to the
server printer for printing.
REST-SPOOLER
The form queues can be moved to the ASSIGNED status by executing the REST-SPOOLER command. This may also be
executed when the servers are restarted.

Now execute the SP-STATUS command and check the "STATUS" & "Q" associated with the form queue UAT5PRINT
It can be observed that the report from the form queue at the jbase level has been spooled to server printer.

Configure printer as server printer in jBASE and T24

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configure printer as server printer in jBASE and T24

Uploaded by

Copyright:

Available Formats

5/22/2020 How to configure the printer as server printer at both jBASE level and T24 level?

How to conﬁgure the printer as server printer at both jBASE

Now create 'Form Queue' at jbase level

The queues will be displayed as below:

It may be observed in the screenshot below that the record is printed

Redirecting an enquiry output to the printer:

Printing set-up at Batch level:

Routing the report:

Other associated jbase form queue commands:

Now execute the SP-STATUS command.

You might also like