Before switching to the extended S1 level, ensure that all BS2000 systems accessing the SM run BS2000 OSD/BC V11.0 or higher and HSMS V11.0 or higher.
As soon as the extended S1 level for an SM pubset has been set up on a pubset sharer with HSMS V11.0A or higher, all pubset sharers running HSMS V10.0A or lower can no longer take HSMS control over the pubset – neither with IMPORT-PUBSET nor CREATE-SM-PUBSET-PARAMETERS.
In case an SM pubset was used on a pubset sharer with HSMS V10.0 before the extended S1 level for this pubset has been set up on a different sharer, this pubset remains under HSMS V10 control. However, the following functions are no longer available: backup, copying and migrating to S1 and changing pubset parameters. Write access to the save files on S1 level is still possible: recovery of saved files, restoring of migrated files, copying of save files to S2 level, migrating files from S1 to S2, changing files in the S1 level and deleting files from the S1 level.
Systems with HSMS V9.0 or lower can under no circumstances access the files in the extended S1 level.
Information output with SHOW-SM-PUBSET-PARAMETERS
On a pubset sharer with HSMS earlier than V11.0, with the extended S1 level the SHOW-SM-PUBSET-PARAMETERS displays the value NOT-DEFINED instead of ALL-HSMS-CONTROLLED. The HSMS VERSION field has the value 110.
Information output with SHOW-PUBSET-USAGE
If an extended S1 level for the pubset has been set up on a pubset sharer (with HSMS V11.0 or higher), on a sharer of the same pubset with HSMS prior to V11.0 the statement SHOW-PUBSET-USAGE acts as if no S1 level is defined:
with INFORMATION=*REUSABLE-S1-SPACE the statement is rejected with the HSM0213 message.
with INFORMATION=*MIGRATION-EVALUATION, files that have been migrated to S1 level are marked with 'S1-NOT-DEF'.