DSSM supports the management of shared programs. This permits the following during a session:
unloading of shared programs, even from class 4 memory
relocation of shared programs from class 4 memory to class 5 or class 6 memory.
Shared programs can be declared as subsystems and as such administered by DSSM.They can be dynamically activated, deactivated, suspended and resumed, just like any other subsystems.
This requires that the shared programs be declared during generation of the subsystem catalog. Given this definition, a shared program can be activated and deactivated like a normal subsystem after DSSM has been started.
Users can access the program via the BIND macro or by means of the START-PROGRAM and LOAD-PROGRAM commands.
The entry point must always be defined by means of the SSCM statement SET-SUBSYSTEM-ATTRIBUTES,...SUBSYSTEM-ENTRIES=, even if it is identical with the LINK-ENTRY (of the reference address used to load the subsystem).