W dniu 18.10.2024 o 20:03, Steve Estle pisze:
Radoslaw,
Not something I've tried - my SMS guy is out right now but can talk to him when
he gets back. Not sure we have any EAV volumes yet, although we've discussed.
I have few thoughts:
1. If the DSS doc. does not offer any restrictions on restoring as you indicate
(were the backups done as logical or physical?), I'd recommend reporting this
as a potential defect to IBM support.
2. Have you tried logical disk to disk DSS copy - does it give same error?
If this being restored from a physical backup, might try backing up / restoring
from logical backup and see if any difference.
Hope that helps.
Steve,
Thank you for your valuable advices, however the problem seems to be
solved by Ernesto's hint.
I simply checked RESTORE syntax, but forgot about "patch features" of dss.
While haven't tested it I strongly believe the patch is the answer.
Thank you Ernesto!
BTW: I don't understand patch concept. It could be good solution for
beta products or early features. However nowadays I would expect simple
switch. It need not to be a keyword of (many) dss commands, it would be
enough to have some SETTINGS paragraph with some KEY=value entries.
Provided as a part of SYSIN of another DSSPARM file. Yes, SET PATCH does
similar job, but "5B FF" is much less intuitive than KEY=value.
Regards
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
