MCH3601 – Pointer not set for referenced location during backup
I am runing - SAVLIB LIB(*ALLUSR) SAVACT(*SYNCLIB) This is on my DEV LPAR so i was able to run RCLSTG. It did not solve the problem. Any suggestions? I am receiving it on MANY files.
Software/Hardware used:
Software/Hardware used:
ASKED:
January 6, 2009 3:33 AM
UPDATED:
January 22, 2009 9:16 PM
Answer Wiki:
Hi,
What version OS are you running and are you up to the latest PTF's? Do you get any other messages in your joblog? Is there anything special about the files that you receive the message on? Are all/some of these files journalled?
This may well be caused by using *SYNCLIB with *ALLUSR - this means that the system has to keep track of ALL the objects in *ALLUSR libraries to ensure there is a "checkpoint" where none of the objects are being updated. I would suggest you use *LIB instead of *SYNCLIB - or does that cause the same problem?
Regards,
Martin Gilbert.
To see all answers submitted to the Answer Wiki: View Answer History.
I am on V5R3M0 and should be pretty current with PTFs
the files that I get the errors on are nothing special, small files, some source physical files, I can view them through other means without any issues.
The only other issue i seem to have with this backup with thousands of job locks. Your suggestion of not mixing SYNCLIB and ALLUSR makes sense. I will try tha alternative.
Thanks!
We just upgraded to V5R4M0 last weekend and started seeing this in only one file (which happens to be empty) when backing up a single library to a *SAVF. I also was able to RUNQRY *N & DSPPFM that file without trouble, but what gets real weird is that once I start up a subsystem that places a lock on that file, the SAVLIB operation completes without trouble – which would be exactly opposite of what I’d expect. Don’t think that gives you much help, except perhaps try starting something that locks a few of those files and see if it resolves your issue.