Version backup in shared environment

In an inhomogeneous BS2000/HSMS environment a //BACKUP-FILE-VERSIONS will not be transferred to a master (backup server) running BS2000 OSD/BC < V11.0B or HSMS < V12.0A. In this case, the statement //BACKUP-FILE-VERSIONS is aborted with a corresponding message on the host that starts the request.

Notes:

• It is strongly recommended to set the same value of the system parameter NUMBACK on all sharers with BS2000 OSD/BC version as of V11.0B. Otherwise newly created files will have different NUMBER-OF-BACKUP-VERSIONS depending on the system, where they were created.
• //BACKUP-FILE-VERSIONS is only possible in *HSMS-V10-COMPATIBLE mode. 
• Restoring from version backup archives is possible only by HSMS V12.0A or higher. In case slave/master or backup server, the processing system must have HSMS V12.0A or higher installed.
• Restoring from version backup archives is only possible with BS2000 OSD/BC V11.0B or higher.
• //CHECK-CATALOG-FILES is only possible on systems with BS2000 OSD/BC V11.0B or higher.
• //REORGANIZE-VERSION-BACKUP requires BS2000 OSD/BC V11.0B or higher and is only possible in *HSMS-V10-COMPATIBLE mode.

Compatibility in a shared SM environment.

As soon as a system archive for version backup (SYSVERSION) is defined for an SM-pubset on a sharer with HSMS V12.0A or higher, modifying the SM-pubset parameters via MODIFY-SM-PUBSET-PARAMETERS is no longer possible on other sharers with lower HSMS versions. The function is again available when the sysversion backup archive is again set to *UNDEFINED.