Re: v6r1 save system endsbs hanging

I've noticed in the Memo To Users, this issue is an update to the original MTU,
so any early adopters may not have seen it.
Also, in one of the links you provided, the ptf si35204 added these steps
to GO Save, Go Restore options, but did not list Go Backup opt 11(which is what
this site used-and it may be exact same call as Go Save-21).
A note in the MTU page 33 also says exit qibm_qwc_prerestrict will run under
the executing user profile (used to be QSYS). I imagine any user who can
endsbs *all should also have proper access for the other end.. but it is noted.
We did resolve the issue with the extra end commands.
Thanks for the comments.
Jim


---- rob@xxxxxxxxx wrote:

I've found with 6.1 and above you can do an ENDSBS *ALL and, eventually
you will get the message that all subsystems were ended. It's a lie.
Because, if you do not ENDTCP first it will still be running - just like
it says in the MTU. It's one of those things that one may pass over in
the MTU thinking they can't really mean that, after all, an ENDSBS *ALL
always brings the system down into restricted state, right? But, yes,
they do mean that. ENDTCP must be run prior to running the ENDSBS *ALL. I
lobbied hard, early on, to get that stressed in the MTU. It's been long
enough that I forget what problem it was causing me. Normally after
ending the system to a restricted state we run a full RCLSTG followed by a
full system save so I am sure it affected one or both of those operations.
The third link below specifically mentions save issues with not ending
tcp/ip first.

http://www-01.ibm.com/support/docview.wss?uid=nas2a68debf42e0d564a862575a2003c97a4
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=%2Frzarm%2Frzarmrsmnopt.htm
http://archive.midrange.com/midrange-l/200912/msg00528.html



Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jim Oberholtzer <midrangel@xxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 02/19/2012 09:02 AM
Subject: Re: v6r1 save system endsbs hanging
Sent by: midrange-l-bounces@xxxxxxxxxxxx



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

--

--