Storage level S1 can be defined for an SM environment using the CREATE-SM-PUBSET-PARAMETERS or MODIFY-SM-PUBSET-PARAMETERS statement.
In this case, S1-VOLUME-SET=<cat-id> explicitly defines the specified volume set as S1 level. In HSMS V11.0 and higher, S1-VOLUME-SET=*ALL-HSMS-CONTROLLED can be used to define an extended storage level S1. All volume sets of the SM pubset which are under HSMS control are thus available as S1 level.
The following conditions are required for using the extended S1 level:
BS2000 OSD/BC V11.0 and HSMS V11.0 or higher is used on the system. In the case of a shared pubset network, all pubset sharers of the SM pubset must satisfy this requirement.
The value *HSMS-V10-COMPATIBLE must be specified for the SAVE-FILE-PROCESSING HSMS parameter. In case of a shared pubset group, this applies to all systems accessing the pubset.
All volume sets that belong to the S1 level need to be of NK2 format.
The CREATE-SM-PUBSET-PARAMETERS or MODIFY-SM-PUBSET-PARAMETERS statement is rejected in the following cases:
If no volume set of the SM pubset is planned for HSMS usage, the specification is rejected by *ALL-HSMS-CONTROLLED.
On a BS2000 system with BS2000 OSD/BC earlier than V11, the specification of *ALL-HSMS-CONTROLLED is rejected.
As soon as an extended S1 storage level has been set up on an SM pubset, systems with HSMS V10 can no longer take HSMS control over the SM pubset.