http://itknowledgeexchange.techtarget.com/itanswers/mch3601-pointer-not-set-for-location-referenced-during-backup/ Thu, 23 May 2013 01:41:43 +0000 hourly 1 http://itknowledgeexchange.techtarget.com/itanswers/mch3601-pointer-not-set-for-location-referenced-during-backup/#comment-59367 bobo95201 Thu, 22 Jan 2009 21:16:40 +0000 #comment-59367 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.

]]> http://itknowledgeexchange.techtarget.com/itanswers/mch3601-pointer-not-set-for-location-referenced-during-backup/#comment-59024 doublel Tue, 06 Jan 2009 18:50:05 +0000 #comment-59024 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!

]]>