Datasheet

Release Notes - New Features included in Release 2.4.0
Page 67 of 89
• Add ABORTFLAG value of ‘S’ which (following a failure) will cause all records to be
skipped up to the next record with the same layout code.
• When a called transaction generated a System Error, this was reported, but details of the
failed record were not shown, nor written to the reject file. This has been corrected. The
error count is also now increased.
• The location of the moved file was not being shown on the output report, although it was
shown on the ‘TIRQ’ history. This is now shown in the error file.
4.3.4.4 Report printing from TIGI (SR4095)
TIGI has been enhanced to allow the user to over-ride the database auto-queuing facility.
A new field has been added to the screen that will default to the current database auto-queuing
value. This may then be changed by the user.
4.3.5 Core Environment (AAAA)
4.3.5.1 Authorisation Enhancements (SR4195)
When a user has transactions added to or deleted from their identity and there was the requirement
for them to have a password, they are forced to set a new password. This is a feature that ensures
that they are aware of any changes that have been made.
Some customers have found this undesirable, especially if running SDK applications.
This function may now be controlled by a customer configurable package parameter (PAKCONT-
PASS). If this is set to ‘Y’, then the existing processing will continue. If set to ‘N’, then a message
will be displayed, and there will be no need to set a new password.
On upgrade, the parameter will be set to ‘N’ so changing the existing behaviour.
4.3.5.2 Report Printing (SR3622)
The control of TROPOS printing has been rationalised.
Listings produced by TROPOS have been categorised into two types:
• Reports produced by batch programs and certain online transactions
• Documents produced by online transactions.
Reports have a name of Rxxnnnn.LIS or Rnnnn.LIS and will be printed according to details entered
on the BAPR request or, for regular reports, details as entered on the BAPD transaction for that
particular report. There has been no change in this area other than the increase in size of the ‘Report
Destination’ and ‘Forms’ fields. The exception to this is the FSEL transaction that produces
documents with a name format of RBG710n.LIS.
Documents are now all printed according to the information defined on the DPMT transaction.
Previously this transaction related only to those documents produced by White Paper printing
routines – it now applies to all documents. The printer and form specified on the transaction screen
is now only used if there is a DPMT entry with a blank printer and form.