91 lines
6.2 KiB
HTML
91 lines
6.2 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="task" />
|
||
|
|
<meta name="DC.Title" content="Implementing a power-handling program" />
|
||
|
|
<meta name="abstract" content="This topic highlights what you need to do to use a power-handling program for a system when a full uninterruptible power supply is attached." />
|
||
|
|
<meta name="description" content="This topic highlights what you need to do to use a power-handling program for a system when a full uninterruptible power supply is attached." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahrphpgmco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahrwrtpgmco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahrxmppgmrx.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzahrimpgmpi" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Implementing a power-handling program</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzahrimpgmpi"><a name="rzahrimpgmpi"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Implementing a power-handling program</h1>
|
||
|
|
<div><p><span><img src="./delta.gif" alt="Start of change" />This topic highlights what you need to do to use
|
||
|
|
a power-handling program for a system when a full uninterruptible power supply
|
||
|
|
is attached.<img src="./deltaend.gif" alt="End of change" /></span></p>
|
||
|
|
<div class="section"><div class="note"><span class="notetitle">Note:</span> This example assumes that QCTL is the controlling subsystem. </div>
|
||
|
|
</div>
|
||
|
|
<ol><li class="stepexpand"><span>Because of the critical nature of a power-handling program, you
|
||
|
|
should isolate the objects used by the power-handling program in their own
|
||
|
|
library and secure them from other users, as follows:</span> <pre>CRTLIB LIB(UPSLIB) AUT(*EXCLUDE) CRTAUT(*EXCLUDE)</pre>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>A power-handling program requires exclusive use of a message queue.
|
||
|
|
For this reason, you should create a unique message queue and exclude its
|
||
|
|
use from all other users and general system use, as follows:</span> <pre>CRTMSGQ MSGQ(UPSLIB/UPSMSGQ) AUT(*EXCLUDE)</pre>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Create the CL power-handling program and exclude its use from all
|
||
|
|
other users, as follows:</span> <pre>CRTCLPGM PGM(UPSLIB/UPSPGM) AUT(*EXCLUDE)</pre>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Create the job description for the power-handling program you want
|
||
|
|
started automatically whenever the controlling subsystem is started.</span> <pre>CRTJOBD JOBD(UPSLIB/UPSJOBD) JOBQ(QSYS/QCTL2)
|
||
|
|
JOBPTY(1) RQSDTA('CALL UPSLIB/UPSPGM')
|
||
|
|
AUT(*EXCLUDE) USER(<span class="synph"><span class="var">xxxxx</span></span>)</pre>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> You
|
||
|
|
must provide a user profile to use the job description as an auto-start job.</div>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Create an alternative controlling subsystem description by making
|
||
|
|
a copy of the current controlling subsystem description, as follows:</span> <pre>CRTDUPOBJ OBJ(QCTL) FROMLIB(QSYS)
|
||
|
|
OBJTYPE(*SBSD) TOLIB(QSYS) NEWOBJ(QCTL2)</pre>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Change your startup program to start all subsystems. You will
|
||
|
|
need to include a check to see if system value QCTLSBSD is equal to QCTL2.
|
||
|
|
See system value QSTRUPPGM for the name and library. If you do not change
|
||
|
|
the startup program it will not check for QCTL2 in QSYS or QGPL and the startup
|
||
|
|
program will end without starting the rest of your subsystems. </span></li>
|
||
|
|
<li class="stepexpand"><span>Add the autostart job entry to the alternative controlling subsystem
|
||
|
|
description, as follows:</span> <pre>ADDAJE SBSD(QSYS/QCTL2) JOB(QSYS/QCTL2)
|
||
|
|
JOBD(UPSLIB/UPSJOBD)</pre>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Change the controlling subsystem system value to use the alternative
|
||
|
|
controlling subsystem description, as follows:</span> <pre>CHGSYSVAL SYSVAL(QCTLSBSD) VALUE('QCTL2')</pre>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Change the system values to allow the program to handle a power
|
||
|
|
outage, as follows:</span> <pre>CHGSYSVAL SYSVAL(QUPSMSGQ) VALUE('UPSMSGQ UPSLIB')
|
||
|
|
CHGSYSVAL SYSVAL(QUPSDLYTIM) VALUE(*NOMAX)</pre>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Perform an IPL of the system to have the new controlling subsystem
|
||
|
|
description take effect, as follows:</span> <pre>PWRDWNSYS OPTION(*IMMED) RESTART(*YES)</pre>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahrphpgmco.htm" title="System software support is essentially the same for both the battery feature and the uninterruptible power supply attachment.">Enabling a power-handling program to control system activity during a power interruption</a></div>
|
||
|
|
<div class="nextlink"><strong>Next topic:</strong> <a href="rzahrwrtpgmco.htm" title="A power-handling program should be activated at each IPL and remain active at all times. It should be accounted for in the activity level available in work management subsystem specifications.">Writing a power-handling program</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzahrxmppgmrx.htm" title="You can use the sample program with a full uninterruptible power supply.">Example: Power-handling CL program</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|