The processor with the AVAS job control is called the AVAS master. Any other processors that may become active during the runtime of a job network are called AVAS slaves. The total number of processors and pubsets involved during the runtime of a network form the hardware environment of an AVAS network. It also contains all the pubsets/volumes for AVAS and all the pubsets/volumes for the jobs in the AVAS network. The hardware environment can therefore be different for different networks. In the same way, a different hardware environment may be necessary for a network in different runs or it may even be required intentionally: jobs are started on the processors where the specific catalogs are located at the time of the ENTER calls.
The software environment must be available on every processor involved in the runtime of an AVAS network: FHS, openNet Server, JV, HIPLEX MSCF, TIAM. FHS is not required on the AVAS slaves. For certain AVAS functions, MAREN, SDF-P, IFG can be used as further options.
AVAS accesses its data via the access methods PLAM and UPAM. If external data is read into AVAS or data generated by AVAS is output externally, the user can define the file name with CATID.
The CATID for the AVAS files can be specified by the user in the AVAS configuration file GENPAR. If you intend to relocate AVAS, this metadata must be located as far as possible on relocatable pubsets or a shared pubset.
ENTER files are stored by AVAS on a shared pubset in the MSCF network. The AVAS job control must be informed accordingly of the CATID of the shared pubset via a start parameter.
For more detailed information on AVAS, see the "AVAS" manual [1 (Related publications)].