Datasheet

Release Notes - New Features included in Release 2.4.0
Page 70 of 89
WARNING
The records are inserted at the end of the background queue, so there may be some delay before
these records are processed. If this is likely to be a problem, it may be avoided by using the existing
Background Process configuration facilities (XSPA etc).
The ability to specify the user name is also useful in controlling the scheduling of transactions. If no
username is specified, the records will always be available to be run. If a username is specified, then
generally records for that user will be processed singly and in sequence.
If a large number of records are un-expectedly inserted into the background queue, this may have an
adverse effect on other users of the background queue. This type of event should be planned and co-
ordinated.
Manual Set-Up Procedures
In order to provide access from a remote server, some set-up steps are required. The remote node
needs to be authorised to access the TROPOS username. This is done by adding the remote node
name to $HOME/.rhosts for the TROPOS username on the TROPOS server.
It is necessary to execute the command from the same username on the remote machine (i.e. the
TROPOS username).
The command entered on the remote machine is then :
rsh tropos_server ". .profile;ith2remote [Fred Bloggs]01IADDFRED"
These tasks should be performed by someone having knowledge of the two operating systems, and
the requirements for specific combinations may be different to the above.
4.3.5.5 Enhance System Error Dumps (SR4308)
The TRAC transaction has been enhanced to allow system error dumps to be produced when there
has not necessarily been a program failure.
This will aid diagnosis of alleged problems occurring within successful transactions. Full details are
contained within the TRAC help information.
4.3.5.6 Complex Updates (SR4001)
References to 'Complex Updates' in TROPOS batch programs have been removed. This message
applies to the OpenVMS version of TROPOS and has no meaning in TROPOS 2.4.0.
Other messages have also been reviewed.
This System request was raised to aid the running of batches from the online transaction OPEB.
These messages were causing excessive message windows to be created, and were adding no value
to the running of the batch run.
4.3.5.7 TECH - New text transaction (SR4005)
TECH is a new transaction that will ease the entry and maintenance of text.
This is an alternative to the existing TEDY / TERP / TEAD transaction set.