Several supervisory services and monitoring of message exchanges are provided by TBT400 :
The basic operating essentials of a communications platform can be resumed as follows:
- Control the activity in progress
- Be aware of the activity to follow
- Verify the transfers effected
- Look into the errors and incidents
- Explain them and remedy them
The supervisory aspects of TBT400 are based on the above requirements.
Within its supervisory layer, TBT400 allows one to monitor at any given time the state of the communications in progress, to follow or already effected.
There is a permanent display of all the communication elements specified in TBT400.
These various functionalities provide condensed views of the different logical queues, but also exhaustive details of all elements transmitted or to be transmitted, as well as the data-file.
Network envelopes, acknowledgments of receipt, distribution advices, are fully archived and reconciled with the messages transmitted. These various elements are all available for consultation via the supervisory menus.
In addition, so as to optimize the job of the operator, multi-criteria searches on important zones describing the transfers, are possible for current or historical messages.
TBT400 gives immediate access to the list of erroneous transfers. These are signaled in red (or double intensity for monochrome screens) via the supervisory menus.
TBT400 allows an application processing an incoming file, to assign a return code to it. This authorizes, with a little work by the application, the supervision of the processing of the incoming files.
A function key gives access to spools of the job having processed an incoming file. It is therefore almost instantaneous to recover the 'JOBLOG' of a job which processed the files.
A message can be retransmitted from the screen: this allows, for example, the correction of the erroneous application name for an incoming message, for internal recycling and the automatic processing by the application.
The essential network exchanges (e.g. identification) are archived including the translation of known diagnostic codes to accelerate fault finding.
It is even possible to display, even amend, if one is authorized, a file of TBT400 transmitted or received (just as far as a hexadecimal view if necessary), simply by using a function key .Possibility of printing the files received..
Serious errors linked to the network (for example the X25 or BSC line out of order) are signaled in the Operator Message Queue.
Functional errors (for example refusal of a sign-on) are placed in a dedicated Message Queue accessible directly from the TBT400 menus.
An option to trace exchanges can be activated allowing, in complex cases, or for the final application testing, to have the necessary elements to resolve problems.
All OS/400 commands useful for monitoring the functioning of TBT400 are taken out of the hands of the users, so as to provide an easy aid, the user not having to understand anything of the native OS/400 commands.