Informing the SUs

It is quite common for SUs to preprocess their titles in some way. This is straight forward enough during initialisation, but what happens if their titles change during execution? When an SU initially requests a titles bank it passes its SU ID. to MTT. When MTT changes the bank it calls the SU's initialisation routine again but uses a different value of the MODE parameter (see section 4.1.2) so that the SU can differentiate between an initialisation and a reinitialisation call. Most SUs can handle a change of titles, but just a few cannot. To differentiate between them, SUs are classed as DYNAMIC (titles can change) or STATIC (titles cannot change). At the time of writing these notes only the following SUs are static:-

ANL

The NTPR banks define what data is to be collected during processing; it would make no sense to change this half way through the job.

HST

The HIST bank defines what data is to be collected during processing; it would make no sense to change this half way through the job.

MCO

This defines the context based on its titles banks. A context change that resulted in them changing could induce another context change!

RAN

Once started the seed sequence should not be reset, so it titles, that define the starting point, are only honoured at the start of processing.

SHL

The JOB and JOBP banks define the overall job; it would make no sense to change this half way through the job.

MTT will not recall static SUs. Instead it generates a ZTELL warning (see section 10) but allows processing to continue.