Which SSCM and DSSM versions are available under the various BS2000 versions?
BS2000/OSD-BC V3.0:
with DSSM V3.6: SSCM V1.0, V2.0, V2.1
with DSSM V3.8: SSCM V1.0, V2.0, V2.1, V2.2
with DSSM V3.9: SSCM V1.0, V2.0, V2.1, V2.2, V 2.3A
with DSSM V4.0: SSCM V1.0, V2.0, V2.1, V2.2, V 2.3A, V 2.3B
BS2000/OSD-BC V3.1 (in OSD-SVP V1.0/V2.0):
with DSSM V3.7: SSCM V1.0, V2.0, V2.1
with DSSM V3.8: SSCM V1.0, V2.0, V2.1, V2.2
with DSSM V3.9: SSCM V1.0, V2.0, V2.1, V2.2, V 2.3A
with DSSM V4.0: SSCM V1.0, V2.0, V2.1, V2.2, V 2.3A, V 2.3B
BS2000/OSD-BC V4.0:
with DSSM V3.8: SSCM V1.0, V2:.0, V2.1, V2.2
with DSSM V3.9: SSCM V1.0, V2.0, V2.1, V2.2, V2.3A
with DSSM V4.0: SSCM V1.0, V2.0, V2.1, V2.2, V 2.3A, V 2.3B
BS2000/OSD-BC V5.0:
with DSSM V4.0: SSCM V1.0, V2.0, V2.1, V2.2, V 2.3A, V 2.3B
BS2000 DX
- with DSSM V21.0: SSCM V21.0
There are one or two particular DSSM version(s) for each BS2000/OSD version. However, higher DSSM versions up to V3.9 can run without problems on lower BS2000/OSD versions. BS2000/OSD V3.0 or higher is required for DSSM V4.0.
However, versions 21.0 are BS2000 DX specific.
Which catalog format of the subsystem catalog (corresponds to the SSCM version) is evaluated by the various DSSM versions?
SSCM V1.0: | as of DSSM V3.0 |
SSCM V2.0: | as of DSSM V3.5 |
SSCM V2.1: | as of DSSM V3.6 |
SSCM V2.2: | as of DSSM V3.8 |
SSCM V2.3: | as of DSSM V3.9 |
The creation or modification of a subsystem catalog is not dependent on the DSSM version that is currently running.
However, each DSSM version is able to evaluate only those catalog formats which have
been created by its “own” SSCM version or a lower SSCM version.
The full functionality of a DSSM version is never exploited unless it is run with the associated SSCM version.
The catalog format of a SSCM version is supported by higher DSSM and SSCM versions for compatibility reasons, and it is converted to the higher format when it is read and written back.
Example
When a catalog generated with SSCM V2.1 is read and written back by DSSM V4.0 or SSCM V2.3, it is given the format of SSCM V2.3.
Under what conditions can SSCM versions V1.0 to V2.3B be loaded at the same time?
Up to DSSM V3.4, the appropriate SYSPRC.SSCM.0xx procedure must be used to load the higher version.
Example
In order to allow SSCM V2.3 to be loaded when SSCM V1.0 is in use as a subsystem, the SYSPRC.SSCM.023 procedure must be used; this loads SSCM V2.3 as a program.
As of DSSM V3.5, the version can be selected with the SELECT-PRODUCT-VERSION command. The START-SSCM command then starts the selected version.
However, as the full functionality of a particular DSSM version can only be exploited with its “own”, specially developed SSCM version, loading older SSCM versions at the same time does not provide any advantages for the current BS2000 session.
On the other hand, parallel loading of different SSCM versions is necessary if a subsystem declaration file SYSSSC or SYSSSD is to be generated for an SSCM/DSSM version that is older than the current version (e.g. for version downgrading).