miscellaneous functionalities :
has an integrated scheduler allowing :
transmission of files
emptying out of mail-boxes
eventual submission of jobs.
scheduler has the basic understanding of repetition,
frequency, time span, working days, and the processing
of Bank Holidays, it is in fact far more efficient
(within its own scope of usage) than the OS/400 'job
scheduler'. It can, for example, in a single instruction
process the following case:- empty my ATLAS mailbox
every hour between the hours of seven o’clock and six
o’clock in the evening every working day. It does not
pretend to substitute itself as a operational robot,
but to compensate for its absence.
is available for all protocols supported
archives all files received, as well as, as an option,
all files transmitted.
(transmissions or receptions) are also archived. In supervision
mode, it is possible to display the list, and to directly
access the file objects by function key.
has an automatic purge allowing
clear the history files
remove the archived files
clean up the various OS/400 components (messages queues,
purge, entirely parameterized, is effected as a background
task with a low priority so as not to penalise the system.
There is therefore no need to stop the subsystem, therefore
increasing the system availability.
are managed dynamically according to the user and the different
options used by your company, and therefore some choices
may be blank.
menus, consistent with the different Networks/Protocols functionalities
used by your company and available on your platform TBT/400,
provides the management of your communications and your correspondents
via the directory or without the support of the directory.
menus provide pre-formatted screens to the characteristics
of the network of your choice so as to provide a easy means
of transferring your files or messages.
course, whatever the functionality you use, a contextual
and conceptual on-line help is provided in
order to respond to your different questions.
are available via the menus, or via commands.
Hyper-text type relationships are also defined, providing
easy search and learning facilities.
an integrated editor, similar to PDM, providing for message
input and modification.
a procedure which ensures that the installation is effected
in a minimum amount of time (less than an hour).
a subset of functions directly accessible by the’ end user’:
the various protocols used, certain elements necessary for
the processing of a file are absent (for example record length
for an ATLAS transfer, text mode for an Odette transfer,
etc...). As a standard, TBT/400 searches for these
various elements within its parameters. A capability exists
however, in all protocols, to define a flag contained
in a field of the envelope and defining these unknown elements.
allows, providing the sender collaborates, to introduce the
notion of record length when the network
does not have this notion (in the case of ATLAS for
example), the notion of text mode (in the
case of Odette), the notion of the write mode
for the file received (research CR/LF), or
the notion of file type (source file, physical file....).
equally generate this flag automatically (which pre-supposes
the existence of a TBT/400 on
the other site).
of the application
receive files of any record length, length not stated
by the protocol, without having to classify all cases
in advance .
receive 'Save files' via a 'continuous flow' network
(ATLAS for example).