Re: IFS error on V5R4M0

[Pete Helgren <Pete@xxxxxxxxxx>]

To my knowledge there wasn't any journaling in place although a couple 
of the APAR's I read mentioned journaling.

We are running RCLSTG right now.  With the system is a restricted state, 
we are going to try to delete the folder after the RCLSTG.  I'll post 
whatever we come up with.

Thanks,

Pete


Scott Klement wrote:

> I've seen this error when restoring a section of the IFS that was 
> journalled on the original system, but the journal receiver wasn't 
> backed up at the same time as the directories.
>
> Do you have journalling enabled?  If so, you might want to turn 
> journalling off, back up the directories again, and then re-restore 
> without the journalling.
>
> It could also be a problem with authority to the journal or journal 
> receiver.
>
> It could also be corruption in the filesystem...  if you havent' already, 
> a RCLSTG might help.
>
> ---
> Scott Klement  http://www.scottklement.com
>
>
>
> On Wed, 26 Jul 2006, Pete Helgren wrote:
>
>  
>
> > Anybody seen something similar to this: "File system error occurred.
> > Error number 3474"  This particular folder in the IFS isn't accessible.
> > Can't access it with WRKLNK. Can't get to it through QSH.  All attempts
> > to access the folder generate the error above, sometimes in conjunction
> > with an MCH3601 "Pointer not set for location referenced." error.
> >
> > The objects and folders were restored from a model 800 at V5R2M0 using
> > SAVRST.
> >
> > We've opened a PMR with IBM but I wonder if someone else has seen/solved
> > this issue?
> >
> > Pete Helgren
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >