RE: Power Handling program?

How do I communicate with other partitions? Remote data queue.

Remember the OP was to shut down other partitions on the box that are not
set up with the power handling from the UPS. The remote data queue was my
choice for a method to do that.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Friday, April 10, 2015 10:04 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Power Handling program?

Jim,

Understood.

But why a remote q and not just q on the local LPAR?

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer
Sent: Friday, April 10, 2015 11:01 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Power Handling program?

Paul:

You can accomplish this task many ways; the data queue example is one that
tends to be more tolerant of OS changes which is why I like it, as I said
it's an example. As Rob pointed out with newer hardware it might not even
be needed in a completely virtualized environment, but Rob's set up is the
exception not the rule. (After all Decko is a member of the LUG)

The message queue is the one defined in the QUPSMSGQ system value and the
program attached to that message queue actually sends out the remote data
queue entry. That program can, if needed, interrogate the messages and be
smart about what to do etc. if you wish. Since it's a program it can do
anything you want it to.

Once the remote data queue base set up is done, then you can expand the
technique to many different needs based on the situation and imagination of
the admin. Extending it is easy.

Is it the best way, maybe not. The only way, certainly not.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Friday, April 10, 2015 9:40 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Power Handling program?

Jim,

Are you keying off of a specific message?
Why are you utilizing a remote data q?
Could you accomplish this with a WRKWCH?

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer
Sent: Friday, April 10, 2015 8:30 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Power Handling program?

That I am aware of no, I've not seen examples of that type.

However it's fairly easy to do. I like remote data queues. Set up a remote
data queue on each partition. The program that listens for that data
queue entry would be able to perform an orderly shutdown. When it receives
the queue entry from the partition connected to the UPS (the program setup
to watch QUPSMSGQ), it does its thing. This program would start with the
start up program and I usually use QUSRNOMAX job queue.

When you think about it this can be used for many types of interpartition
communications limited only by your need and imagination. The program can
be written in any language (I use CL) so use your favorite.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Thomas Garvey
Sent: Thursday, April 09, 2015 11:44 PM
To: Midrange Systems Technical Discussion
Subject: Power Handling program?

I've seen the suggested code IBM published for a Power Outage Handling
program when the message queue defined by the QUPSMSGQ system value is
allocated.
But what can be done when a UPS is supporting a server on which multiple
partitions are defined?
What is the connection actually made between the RS232 cable from the UPS
and the IBM i? It must be simply an IBM i port monitored by some process in
a single partition, right?
In this case, how would all the partitions be notified so they can be shut
down? And, if they could all be shut down, how would the server itself be
powered off, since PWRDWNSYS doesn't actually power the server down (we do
it through the HMC, which also manages another server).

Is there an IBM document describing this circumstance?