Report Control - User Guide

Release - R18AMR
May 2018

©2018 Temenos Headquarters SA - All rights reserved.

Warning: This document is protected by copyright law and international treaties. Unauthorised reproduction of this document, or any portion of it, may result in severe
and criminal penalties, and will be prosecuted to the maximum extent possible under law.
Table of Contents

Introduction 3
Purpose of this Guide 3
Intended Audience 3
Overview 4
Setup 5
Parameter Files 5
Banner Page Addressing 9
Deal Processing 12
Report and P-function routing 12
Monitoring reports produced 12
Viewing/reprinting reports 12
Close of Business Services 14
Users to receive batch reports 14
Deferring all Close of Business (Batch) output 14
Deferring output from individual batch processes 14
Spooling Close of Business output manually 14
Reports listing output to be received 15
Interface to Microfiche System 15

Report Control - R18AMR - Page 2 of 15

 Introduction
Purpose of this Guide
This document provides more details about the report controlling system especially on how to spool a
report, how to hold a report, how to restrict viewing a report and how to purge a report.

Intended Audience
This User Guide is intended for the use of Internal Temenos users and Clients.

Report Control - R18AMR - Page 3 of 15

 Overview
The Report Control System provides the following facilities to T24: 
l Routing of User prints- A user may request that reports or prints, produced either online or dur-
ing the Close of Business process, are routed to a specific printer. This is useful where the user is
located in a different building than the computer room, or simply on a different floor. 
l Banner pages for easy distribution - To ensure that a printout is delivered correctly a banner
page can be added that includes the name and location of the user who requested the printout. 
l Storage of Reports - Reports and printouts are stored on the UNIX computer hard disk, for peri-
ods set by the user, and can be reprinted in case of printer problems. Additionally, the reports
can be reviewed on screen prior to, or instead of, printing them. 
Close of Business reports can be printed as the system runs the COB, or alternatively can be held
on disk until required. The reports can then be printed in their entirety or only the requested
reports. 
l Held Mail - Customer Advices and Statements from the Delivery system can be held at a Cus-
tomer or Account level and spooled at a later date.
l Microfiche - T24 has a built-in interface for the storage of reports on microfiche.

Report Control - R18AMR - Page 4 of 15

 Setup
Parameter Files
Report names
The REPORT.CONTROL file is the main control file in the 'Report Control System'. It contains a record
for each report that can be produced by T24 and stores various details related to the report e.g.
description, form name (printer environment defined on DE.FORM.TYPE) and whether it is to be
microfiche, and so on.
The records on this file are automatically created by the various T24 report applications. 

Report Control Maintenance File

Printing to physical Printers

The file PRINTER.ID defines the valid printers available to T24. The key to the file is a logical printer
name, which can either be the same as the  printer or some other name that the System Administrator

Report Control - R18AMR - Page 5 of 15

chooses. The physical printer name is specified in PRIME.PRINTER.ID field.

Printer Maintenance File

In the above example, the T24 printer name LASER refers to the physical printer PR0. 
A record in PRINTER.ID called SYSTEM must exist and it should refer to the default line printer to be
used when no specific routing of reports is to be done. 

Report Control - R18AMR - Page 6 of 15

Printing to system disk
The HOLD entry is a special printer name that does not refer to any physical printers. This can be used
as a destination when no reports need to be physically printed. Instead the report is disk and can be
viewed on screen.

Printing to files
Instead of sending output to a particular printer, T24 can now execute a command specified on the
PRINTER.ID record in the COMMAND field. Typically this is used to send the report to a file instead of
to a printer. 

Report Control - R18AMR - Page 7 of 15

 Printer Maintenance File: print to a file
It is also possible to copy a report to another area such as ‘SAVED’ which is a subdirectory of
‘FOREX.ARCHIVES’, a command could be entered to copy the specified report from '&HOLD&' to
'FOREX.ARCHIVES/SAVED'.
Since the key to '&HOLD&' is different for each report generated, the key cannot be specified directly
in the command, so an element which can be evaluated to generate the required key can be specified.
This must be defined in the format '&filename>field&'.
In this example the key to the '&HOLD&' record to be copied is the @ID of the file HOLD.CONTROL, so
this should be specified as '&HOLD.CONTROL>@ID&' giving a command from Unix to be defined as:
SH -c “cp ../bnk.data/eb/’&HOLD&’/&HOLD.CONTROL>@ID&
FOREX.ARCHIVES/SAVED”

Special forms/printer environment

The DE.FORM.TYPE file defines the printer environment (page length, width, top margin etc.) to be
used for the report. It can also store spooler options such as a special form name to control the
queuing of reports that require special stationery to be loaded in the printer. Refer the below example
of a form defined for delivery advices. 

DE.FORM.TYPE defines printer environment

The example defines a printer set-up of 80 columns and 66 lines per page and a special form ADVICE
(contents of OPTIONS field set to FORMADVICE). 
Any REPORT.CONTROL records that use this form is spooled with a form name of ADVICE

Report Control - R18AMR - Page 8 of 15

Special print attributes
The file PRINTER.ATTRIBUTES is used to define any special printer attributes, for example compressed
font, landscape, portrait modes and so on; that are required for certain reports. 
The records in this file contain the ASCII <escape> sequences for setting and resetting the desired
attribute. 
For example, to define a report to be printed in landscape mode on a KYOCERA laser printer, follow
the steps below: 
1. Set the PRINTER.TYPE field on the PRINTER.ID record for the laser printer to KYOCERA. This field
allows similar printers that support the same <escape> sequences to be grouped together. 
2. Create the record KYOCERA.LANDSCAPE(‘printer.type’.attribute) on the PRINTER.ATTRIBUTES
file, defining the initialisation and reset <escape> sequences for landscape printing. The
<escape> sequences can be obtained from the Programming manual for the printer. 
3. Set the RPT.ATTRIBUTE field to LANDSCAPE on the DE.FORM.TYPE record used for the report
(refer REPORT.CONTROL record to obtain form name). 

Printer Attributes Maintenance File

Banner Page Addressing

The details that appear on the banner page of each report are specified in the USER and
DEPT.ACCT.OFFICER files. 

Report Control - R18AMR - Page 9 of 15

The department area (AREA field in the DEPT.ACCT.OFFICER record) is printed at the top of the banner
page. The next three lines of the banner page contains the address specified in USER.ADDR field in the
USER record. If no address is specified, then the delivery point (DELIVERY.POINT field in the
DEPT.ACCT.OFFICER record) is used. 
The T24 banner page can be suppressed by specifying 'NHEAD' or 'NOHEAD' in OPTIONS field of the
DE.FORM.TYPE record for the report. 
The format of the block letters that appear on the banner page can be changed using the application
BLOCK.LETTERS. The key to this file is the ASCII number for the character to be defined. 

Create Report Banner Page

The banner page contains information on the user, printer and area printed from. In the example
below, the following information is provided: 
The Department:
DEPARTMENT ONE                     is from the USER record 
The User:
SDONEY is from the USER record
The Area:
USER GUIDE DEPARTMENT
4TH FLOOR

Report Control - R18AMR - Page 10 of 15

MAIN BUILDING                         is from the USER record 
The Report name:
P FUNCTION                             is the id of REPORT.CONTROL
The spool details:
Description: P-FUNCTION SCREEN OUTPUT
from REPORT.CONTROL description
As at: 15-04-1996   13:16          Date/Time print requested

Bank date: 31-01-1994              Date of system

Printed on: 15-04-1996   13:16   Date/Time printed

Form: SYSTEM                         DE.FORM.TYPE record used

Printer: PRINT1 - PR1                PRINTER.ID key and Unix printer name

Hold Id: 103334780200 - dev.run - d05030

Three items; ID of HOLD.CONTROL -
uv.account (area) - UNIX user ID

Attributes: STD BOLD                Settings in RPT.ATTRIBUTES field of the DE.FORM.TYPE record.

Report Control - R18AMR - Page 11 of 15

 Deal Processing
Report and P-function routing
Report and P-function (screen print) output produced online can be routed to specific printers for a
T24 User by specifying the printer names (defined on PRINTER.ID) in PRINTER.FOR.RPTS and
PRINTER.FOR.P.FUNC fields in the USER record.
The online Printer destination is determined as follows: 
l Firstly, if the DE.FORM.TYPE used in the REPORT.CONTROL record for the report has a specific
printer specified in PRINTER.ID field; then this is used. 
l Secondly, if no printer is specified in the relevant DE.FORM.TYPE; then the printer specified in
the USER record (PRINTER.FOR.RPTS field) is used. 
l Finally, if this is not specified the SYSTEM printer (defined on PRINTER.ID file) is used as a
default. 

Monitoring reports produced

A record of all the reports produced by the system is held in the HOLD.CONTROL file. This has an entry
for each report saved to disk and stores various details related to the report; for example, the name of
user who created the report, the date/time produced, whether it is a COB report and so on.
It is purged according to the setting in the SPF and REPORT.CONTROL records. 

Viewing/reprinting reports
Reports can be viewed and reprinted online through the HOLD.CONTROL application.
The ‘List’ function is used to list the contents of the file and the items to be viewed/reprinted are selec-
ted using the ‘V’erify function. 
The entire report can be reprinted or just specified pages. 
Reports can be displayed on 80 or 132 column terminals. 
Refer HELPTEXT for more details of the view function and the Navigation chapter of the User Guide;
for more details on viewing reports with the Graphical User Interface (GUI).

Cancelling spool request

Print requests that have been submitted to the spool queue and which are waiting to be printed can be
cancelled by using application SPOOL.CANCEL. This lists the current spool entries and prompts for the
entry number of the item you wish to cancel. 

Report Control - R18AMR - Page 12 of 15

Restricting viewing of reports
In addition to any Security Management System (SMS) controls applied to the HOLD.CONTROL applic-
ation, the viewing and reprinting of reports can be restricted further to only those reports (specified in
field RPT.TO.RECEIVE of USER record) which are received from the COB process by setting the
RESTRICT.RPT.VIEW field to ‘Y’ in the SYSTEM record on the SPF file. 

Holding delivery advices/statements

The Delivery system advices (confirmations and so on) and statements can be held in the system and
spooled at a later date. This is often used to suppress printing until the customer next visits the bank or
where mailing is batched. 
To specify that output from the delivery system should be held, the HOLD.OUTPUT field in the
DE.ADDRESS record for the customer should be set to ‘’Y’. 
This holds any output, which is destined for this address. 

Printing held advices/statements

There is an application called PRINT.CUST.OUTPUT, which enables the user to select any held mail for
a client and to print it. The selection can be by any field on the HOLD.CONTROL file so groups of output
can be printed at the same time. 
The below example illustrates the application in brief.

Print.Cust.Output screen

Report Control - R18AMR - Page 13 of 15

 Close of Business Services
Users to receive batch reports
Reports produced by the COB (Batch) run can be addressed to certain users by specifying the report
names and number of copies requested in RPT.TO.RECEIVE fields and RPT.COPIES of the USER records. 
When the COB output is spooled the USER file is scanned for users who have requested reports and
their address details are extracted and printed on the banner page of each report requested. 

Deferring all Close of Business (Batch) output

The output produced by an EOD (Batch) run, can be held by setting the HOLD.BATCH.OUTPUT field on
the SYSTEM record in the SPF file to ‘Y’. 
When the COB batch is being run all the output is written to the '&HOLD&' file on disk and not sent for
spooling. 

Note: When a process/job in the batch is rerun for any reason then the previous job (log)
file for the process is spooled out to the printer. 

Deferring output from individual batch processes

When the output from the COB (Batch) run is not being held but being spooled immediately, the out-
put from the individual batch processes/jobs can be held by specifying a destination printer of 'HOLD'
in DEFAULT.PRINTER fields and/or PRINTER.NAME of the BATCH record for the process. 
When the COB is being run, the output from the batch processes/jobs with a destination printer of
'HOLD' is not printed. 

Spooling Close of Business output manually

The output from a previous batch run can be spooled by using the application SPOOL.BATCH.OUTPUT
in ‘V’erify mode. 
This maintains a history of '5' batch run start date and times, the most recent one is held in record '1'. 
The output is spooled to a single printer (defined in DEST.PRINTER field of the SPOOL.BATCH.OUTPUT
record) in a sorted order (by department/user/report name) with a covering dispatch list. 
The banner on the reports is addressed to those users defined in the USER file who have requested to
receive the COB output. If any reports are found to have no destination user then they are addressed
to the current user requesting the re-spool. 
Unrequested reports can be suppressed (that is, not spooled) by setting SPOOL.ALL.OUTPUT field of the
SPOOL.BATCH.OUTPUT record to ‘N’. 

Report Control - R18AMR - Page 14 of 15

 Note: The actual number of batch reports held on disk, depends on the report purge cycle. 

Reports listing output to be received

Two online reports are provided which list the batch output to be received. 
These applications can be run online or as part of the batch. 

Two online reports can be run online or as part of batch

Report Purging
Defining report retention period
The number of working days for which the report output is held on disk (&HOLD&) is specified in field
REPORT.RETENTION on the SYSTEM record in the SPF file. 
When the reports have been in the HOLD.CONTROL file for more than this period they are deleted. 
The retention period for reports that need to be retained for a time other than the system wide reten-
tion period specified in the SPF file, should be specified in REPORT.RETENTION field of the individual
REPORT.CONTROL records. 

Purging reports
Purging of reports is carried out by the COB (Batch) process PURGE.HOLD.RPTS which is run in the
‘Start of Day’ batch stage. This batch process is run daily and deletes any reports that have been in the
HOLD.CONTROL file for more than the retention period specified in the SPF and REPORT.CONTROL
files. 

Interface to Microfiche System

Reports that are to be microfiched must be specified in the REPORT.CONTROL file. The
MICROFICHE.OUTPUT field on the REPORT.CONTROL record must be set to ‘Y’. 
If the microfiche system is enabled (refer SYSTEM record on SPF), then every time the reports are pro-
duced they are copied to the microfiche files. These files are then used to create output media (nor-
mally tapes) that can be sent to the microfiche producers.

Report Control - R18AMR - Page 15 of 15