MCH3601 – Pointer not set for referenced location during backup

15 pts.
Tags:
LPAR
MCH3601
RCLSTG
SAVACT
SAVLIB
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.
ASKED: January 6, 2009  3:33 AM
UPDATED: January 22, 2009  9:16 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

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.

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • DoubleL
    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!
    15 pointsBadges:
    report
  • Bobo95201
    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.
    25 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following