|
View previous topic :: View next topic
|
| Author |
Message |
Willem Vermeer
New User
Joined: 31 Oct 2007
Posts: 38
Location: Amsterdam, the Netherlands
|
|
|
|
Greetings.
a customer of ours ran into the issue above when restoring from a logical dump. The cluster was pre-allocated, but DFSMSdss deleted/reallocated it. An ADR788I seems to suggest that processing went ok -number of records processed corresponds to records dumped- but statistics shown with a LISTCAT suggest that something went wrong when the cluster was closed.
I'm trying to get a grip on that ADR417W RSNC 05 message. On the IBM Support Portal the only items mentioning this message, were for older versions of DFSMSdss (2010). We're running z/OS 1.12 and this is really the very first time I've ever seen it.
Anybody any ideas? |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Nope, this is not familiar to me.
What does IBM have to say? |
|
| Back to top |
|
|
Willem Vermeer
New User
Joined: 31 Oct 2007
Posts: 38
Location: Amsterdam, the Netherlands
|
|
|
|
Dick,
I haven't contacted IBM yet. Perhaps it's about time that I did. I had the customer do an EXAMINE on the cluster and everything came out just fine. No errors at all. |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 580
Location: London
|
|
|
|
ADR417W RC=5 - Message action is:
5 Use AMASPZAP to reset the RACF indicator, and rerun the job.
Alternative might be to just delete the target file (if you can) before rerunning the restore.
You could first do some IDCAMS DIAGNOSE of the volume and catalog entry which might highlight any issue.
Also, out of curiosity is the source file that was dumped showing valid statistics? |
|
| Back to top |
|
|
Willem Vermeer
New User
Joined: 31 Oct 2007
Posts: 38
Location: Amsterdam, the Netherlands
|
|
|
|
Pete,
we could try deleteing the target file, but to be honest, I'm not sure whether that would make any difference. After all, isn't that what DFdss is doing? It finds the target already present and deletes it first before proceeding with the reallocation and restore. But I guess we could give it a try.
I haven't done any IDCAMS Diagnose on volume or catalog entry yet. Will try that.
As to those statistics, difficult to say. You see, they're Dumping / Restoring the same files on what looks like a periodic basis. Why? I don't know. Must admit I haven't asked them. Yet.
Anyway, if the original file ever had correct statistics, I cannot see them anymore since the file has been dumped/restored a number of times. |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 580
Location: London
|
|
|
|
I have had experiences where deleting the target file up front has a different effect to DFDSS doing it itself. Sometimes I think you can get a mismatch in some attributes of the DUMP'd version and the online version. You could just rename the target file which would have a similar effect, at least its there for later analysis then.
Certainly appears to be something to with the VTOC entry otherwise the message wouldn't recommend using ZAP.
Is the file QSAm or VSAM? |
|
| Back to top |
|
|
|
|
