HP Archive Backup System for OpenVMS Guide to Operations

Solution –
Follow these steps:
Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X
B.2 SLS/MDMS V2.x to ABS/MDMS V4.x Migration
1. Rename the existing *.Dat_old files to *.Dat in the SLS$ROOT:[PRIMAST] directory.
2. Purge the *.Dat files.
3. Execute the conversion again.
PoolAuth.Dat File Locked During the Conversion –
Following is a snap shot of the SLS/MDMS V2.x to ABS/MDMS V4.x conversion process
Renaming the following files:
SLS$MASTER:POOLAUTH.DAT;* to SLS$MASTER:POOLAUTH.DAT_OLD;*
Opening file $2$DKA0:[SLS$FILES.PRIMAST]POOLAUTH.DAT; failed with:
%RMS-E-FLK, file currently locked by another user
Reason –
The above-mentioned error is seen if SLS is still active on other Client nodes and the conversion
is executed on the Database server node. The Client nodes will still be accessing the DAT files
(in the PRIMAST directory) on the Database server node.
Solution –
Shutdown SLS on all the other nodes connected to the server and execute the conversion again.
SLS SBK Symbols to ABS Policy Objects Conversion Fails –
$ @ABS$SYSTEM:SLS_CONVERT SLS_ABS_SIMPLE
No SBK files match the specification: SLS$SYSBAK:SLS_Example_SBK.COM;0
Enter wildcard SBK specification: :
Reason –
The above-mentioned error is seen if you try to convert SLS SBK symbols to ABS Policy
objects without starting SLS. The logical SLS$SYSBAK is set only when SLS is started.
Solution –
Start SLS and do the conversion again.
Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B–51