Suggestions for note 624745106 related with RST command

Recently we've tried to use RST command in order to restore an object previously saved in the same system when it was being stored at *SYSBAS, but now the current path of the same object involves a *SYMLNK that redirects to an iASP.

The purpose of that restoration was to check if the object in the system had the same content which was saved on tape.

The source object stored on the tape (recorded at 2011) doesn't have any *SYMLNK in its path (/usr/sap/p01/so on..). The destination folder that should receive the result of the unsuccesful restoration also doesn't have any *SYMLNK in its path (/test).

You can see the details in the PMR history.

By other side, the current version of the object now stored in the system, is still /usr/sap/p01/so on..., but /usr/sap/p01 is now a *SYMLNK to an indepedent ASP because of XSM HA implementation.

The question is that we haven't been able to restore the older version of the object from the tape over the same system because RST command refused to execute the operation with the CPI3728 message. Instead that, we have been able to restore that object into another i5 partition, where doesn't exist any *SYMLNK, without any kind of problem.

We have been confused using RST command, as per your note 624745106 in http://www-01.ibm.com/support/docview.wss?uid=nas8N1011141, where uses the term "absolute path name" to refer the current location of the object in the system, when it is not really which had been involved. We had understood as "absolute path names" those that were involved in the restore operation: the path that stores the object in the source tape, and the path of the destination.

Taking into account that the involved system is a productive one, there is not (easily) applicable option to delete as is suggested in the referred note.