ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaig_5.4.0.1/rzaigmanagejobstructure.htm

109 lines
7.2 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="concept" />
<meta name="DC.Title" content="Job structure and user queues" />
<meta name="abstract" content="When managing cluster, you need to know about job structures and user queues." />
<meta name="description" content="When managing cluster, you need to know about job structures and user queues." />
<meta name="DC.Relation" scheme="URI" content="rzaigmanage.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsfailovermessagequeue.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaigmanagemaintainuserprofiles.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaigtroubleshootdetermineproblem.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaigtroubleshootrecoverjobfailure.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="rzaigmanagejobstructure" />
<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>Job structure and user queues</title>
</head>
<body id="rzaigmanagejobstructure"><a name="rzaigmanagejobstructure"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Job structure and user queues</h1>
<div><p>When managing cluster, you need to know about job structures and
user queues.</p>
<div class="section"><h4 class="sectiontitle">Cluster resource services job structure</h4><p>Cluster
resource services consists of a set of multi-threaded jobs. When clustering
is active on a server, the following jobs run in the QSYSWRK subsystem under
the QSYS user profile. The jobs run using the QDFTSVR job description, but
with the logging level set such that a job log will be produced.</p>
<ul><li>Cluster control consists of one job that is named QCSTCTL.</li>
<li>Cluster resource group manager consists of one job that is named QCSTCRGM.</li>
<li><img src="./delta.gif" alt="Start of change" />Cluster resource groups consist of one job per cluster
resource group object. The job name is the same as the cluster resource group
name. This includes the cluster administrative domain.<img src="./deltaend.gif" alt="End of change" /></li>
<li>When one or more device list entries in a resilient device CRG have been
set to be brought online at switchover or failover, additional jobs will be
submitted to perform the vary on function.</li>
</ul>
<p>The QCSTCTL and QCSTCRGM job are cluster critical jobs. That is, the
jobs must be running in order for the node to be active in the cluster.</p>
<p>Most
cluster resource group APIs result in a separate job being submitted that
use the user profile specified when the cluster resource group was created.
The exit program defined in the cluster resource group is called in the submitted
job. By default, the jobs are submitted to the QBATCH job queue. Generally,
this job queue is used for production batch jobs and will delay or prevent
completion of the exit programs. To allow the APIs to run effectively, create
a separate user profile, job description, and job queue for use by cluster
resource groups. Specify the new user profile for all cluster resource groups
that you create. The same program is processed on all nodes within the recovery
domain that is defined for the cluster resource group. </p>
<p><img src="./delta.gif" alt="Start of change" />You
can use the <a href="../cl/chgclurcy.htm">Change
Cluster Recovery (CHGCLURCY) command</a> to restart the cluster resource
group job that ended without ending and restarting clustering on a node. <img src="./deltaend.gif" alt="End of change" /></p>
</div>
<div class="section"><h4 class="sectiontitle">Cluster APIs use of user queues</h4><p><img src="./delta.gif" alt="Start of change" />Functions
performed by an API that has a results information parameter operate asynchronously
and send their results to a user queue once the API is finished processing.
The user queue must be created before calling the API. You can create a user
queue by using the <a href="../apis/quscrtuq.htm"><span class="apiname">Create
User Queue (QUSCRTUQ)</span> API</a>. The queue must be created as a
keyed queue. The key for the user queue is described in the format of the
user queue entry. The user queue name is passed to the API. The Cluster API
documentation contains <a href="../apis/clust1a4.htm">examples</a> on
how to use user queues with Cluster APIs.<img src="./deltaend.gif" alt="End of change" /></p>
<p>When the <a href="../apis/cldistinfo.htm"><span class="apiname">Distribute Information
(QcstDistributeInformation)</span></a> API is used, the information
sent between nodes is deposited on the user queue specified when the CRG was
created. This queue must be created by the user on all active nodes in the
recovery domain before useing the <span class="apiname">Distribute Information</span> API.
See the <a href="../apis/clrgcrtcrg.htm">Create
Cluster Resource Group (QcstCreateClusterResourceGroup) API </a> for details
on when the distribute information queue must exist. </p>
<p>The failover message
queue receives messages regarding failover activity.</p>
</div>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rzaigconceptsfailovermessagequeue.htm">Failover message queue</a></strong><br />
The failover message queue receives messages regarding failover activity.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigmanage.htm" title="This topic contains information that covers some of the tasks that involve managing your clusters.">Manage clusters</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzaigmanagemaintainuserprofiles.htm" title="You can use two mechanisms for maintaining user profiles on all nodes within a cluster.">Maintain user profiles on all nodes</a></div>
<div><a href="rzaigtroubleshootdetermineproblem.htm" title="Start here to diagnose your cluster problems.">Determine if a cluster problem exists</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="rzaigtroubleshootrecoverjobfailure.htm" title="Failure of a cluster resource services job is usually indicative of some other problem.">Recover from cluster job failures</a></div>
</div>
</div>
</body>
</html>