The SET BANK Command

The method outlined above will work with any bank and indeed is the most suitable way to handle the NTPR bank. For other banks where all you want to do is to change one or two words, it does seem like overkill! For this situation there is the alternative solution of using the SET BANK command which instructs SNOMAN to modify one or more values in a bank. For example, if you issue the following commands:-

set bank JOB 1 word 2 to 200
@run

then you will get a 200 events for the SET BANK has updated word 2 of the JOB 1 bank and word 2 of this bank is the event limit.

An advantage of this method is it highlights all the deviations you have made from the standard run and so reduces the chances of making changes and forgetting about them. The same principle applies for resolving conflicts with SET BANK commands as for titles banks:-

If two or more SET BANKS apply to the same word of the same bank, the first takes priority.

So always put your changes before the standard command files. Further,

SET BANK commands apply to all titles banks, even those read using TITLES commands that appear before them.

The reason for this is that SET BANK operates during execution, not during initialisation. It has to be that way, the SET BANKs have to apply to all data read from the database (see section 3.8) as well as from titles files. Each time SNOMAN finds that a new version of a bank is needed, it searches for it in the titles file cache and then the database, but applies all appropriate SET BANKs before connecting it and making it available.