Re: v6r1 save system endsbs hanging

[Jim Oberholtzer <midrangel@xxxxxxxxxx>]

Was the *IMMED option used on the ENDSBS, or at least a time limit set?  
If not there is almost no chance the system will ever get to a 
restricted state.  I also like Bryan's idea with the exit program.  I 
have not done that before but I am going to look into it.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 2/18/2012 7:51 PM, Bdietz400 wrote:
> Its even more important to end tcpip if you are using nfs.   We ended up putting an exit program in place to end everything before the endsbs happened.
>
> QIBM_QWC_PRERESTRICT - ENDSYS ENDSBS *ALL pre restricted state processing (called when ENDSBS *ALL is issued).
>
> --
> Bryan
>
>
> On Feb 18, 2012, at 2:23 PM,<franz400@xxxxxxxxxxxx>  wrote:
>
> > >  Doing save system before applying cume to v6r1.
> > >  The endsbs in the save system never completed.
> > >  Cancelled from console, ipled, and started save system again.
> > >  It's going.
> > >  I see notes that memo to users changed to
> > >  endtcpsvr
> > >  endhostsvr
> > >  endtcp
> > >  before an endsbs *all.
> > >  Is this the fix to this issue?
> > >  Anything in latest cume to resolve this?
> > >  ps... we have had many issues lately w/win 7 mapping drive over ifs /home/user directories and breaks in connection-wondering if this is why endsbs not completing.
> > >  Jim
> > >  
> > >  --