Re: IPL Processing Sequence

:-)
The HMC still relies on TCP and password communications with the FSP. By adding a couple of layers of "stuff" by definition the HMC is not quite as reliable. If it fails it's usually because a human did something stupid, but still...

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 2/8/2012 3:21 PM, rob@xxxxxxxxx wrote:

How dare you put down the HMC and say it is nearly as reliable. Some
might say that twinax would have liked to have been that reliable.


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/08/2012 04:11 PM Subject: Re: IPL Processing Sequence Sent by: midrange-l-bounces@xxxxxxxxxxxx If your doing maintenance and want to start into a restricted state, just change the IPL attributes to start that way. (You have to change it each and every time you IPL when you want restricted state) That way you don't mess with the start up program system value. Also the HMC does not rely on any of those processes running so and HMC console should not have issues. Aside from some small issues with connectivity to the FSP the HMC is nearly as reliable as the twinax console was (I did say /nearly/ before the howls start) While LAN console can be a bit more temperamental ordinarily it's quite reliable as well. Jim Oberholtzer Chief Technical Architect Agile Technology Architects On 2/8/2012 3:03 PM, Evan Harris wrote:

> I used to do this by habit in order to control everything via the
> QSTRUPPGM but am currently re-thinking this approach.
>
> My old approach has an inbuilt assumption that there will be access
> available that does not rely on TCP, but I have been caught a couple
> of times where this assumption has been faulty and QSTRUPPGM has been
> changed to *NONE - thereby making access to the system problematic
> where there is a console issue.
>
> I often change QTSRUPPGM to *NONE when doing maintenance and this can
> cause access issues if the console is compromised.
>
> On Thu, Feb 9, 2012 at 9:43 AM, Jim Oberholtzer<midrangel@xxxxxxxxxx>

wrote:

>> > Rich,
>> >
>> > It sounds a bit like your asking about the TCP/IP servers. If you

need

>> > to control that use CHGIPLA to stop TCP from starting with
>> > QSYSWRK/QUSRWRK start and then start TCP/IP and the balance of the

TCP

>> > servers manually in the start up program per your needs.
>> >
>> > A discussion of the IPL steps from LIC to OS can be found at the

Info

>> > center under Systems Management, Work Management, Reference, IPL

System

>> > reference codes. Until the system is at a point where the the start

up

>> > program runs there's not much you can do with it unless you manually
>> > IPL, then you have a small amount more control... but I sense the

start

>> > up program is what your looking for.
>> >
>> > Jim Oberholtzer
>> > Chief Technical Architect
>> > Agile Technology Architects
>> >
>> >
>> > On 2/8/2012 2:31 PM, Rich Loeber wrote:

>>> >> Does anyone know where I can find a description of the

sequence of steps

>>> >> and when they get processed during an IPL? I have some OS

maintenance I

>>> >> want to do during the QSTRUP program, some of which affects

exit point

>>> >> registration. I'm finding that some server functions are

getting started

>>> >> before I can complete what I need to do in the QSTRUP and the

results are

>>> >> not always pretty. It would help to know what is happening

during the IPL

>>> >> at each stage and what triggers each event to happen.
>>> >>
>>> >> Rich Loeber - @richloeber
>>> >> Kisco Information Systems
>>> >> [1]http://www.kisco.com
>>> >> SDG
>>> >>
>>> >> References
>>> >>
>>> >> Visible links
>>> >> 1.http://www.kisco.com/
>>> >> --

>> > --
>> > This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing list

>> > To post a messageemail:MIDRANGE-L@xxxxxxxxxxxx
>> > To subscribe, unsubscribe, or change list options,
>> > visit:http://lists.midrange.com/mailman/listinfo/midrange-l
>> > oremail:MIDRANGE-L-request@xxxxxxxxxxxx
>> > Before posting, please take a moment to review the archives
>> > athttp://archive.midrange.com/midrange-l.
>> >

>
> -- Regards Evan Harrishttp://www.auctionitis.co.nz
> --

--