The IMON installation monitor permits parallel administration of different versions of a software product on a single computer system. This means, you can also use multiple SESAM/SQL versions in parallel.
Points to note when starting a SESAM/SQL program
When you start a SESAM/SQL program by means of the start commands, you can specify the correction status with which the program is started by means of the VERSION parameter (see "Operands of the start commands"). If you do not specify this at startup, the most recent version of the LLM in the selected module library is loaded by default.
Points to note about the SESAM DBH in 24-hour operation
If a SESAM DBH is running in 24-hour operation, and if a new correction status is loaded into the SESAM module library during operation, the running DBH continues to work with the old correction status. When the DBH starts a new service task after the new correction delivery status is loaded, this service task is started with the appropriate correction status for the DBH.
If one or more subsystems of SESAM/SQL are loaded when a new correction status is loaded, the SESAM subsystems do not automatically load the new correction status.
You can also use correction statuses of SESAM/SQL in parallel in 24-hour operation and change to the new correction status without interrupting database operation, see the section “Parallel use of multiple correction statuses”.
Points to note when starting the performance monitor
If you want to start the SESAM performance monitor in this situation, note that it has to be started with the correction status of the SESAM DBH. In other words, you have to specify the correction status of the SESAM DBH to be monitored for the VERSION parameter of the start command for the performance monitor (e.g. VERSION=9.1A00).
As a result, some DBHs in a configuration may be working with the new correction status while others are still working with the old one. If you want all the DBHs in a configuration to be monitored by the performance monitor in this situation, you have to start a separate performance monitor for each correction status.