ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzau3_5.4.0.1/rzau3rmtjob.htm

101 lines
5.6 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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="dc.language" scheme="rfc1766" 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. -->
<meta name="dc.date" scheme="iso8601" content="2005-10-17" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
<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))' />
<title>Remote job submission</title>
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
<link rel="stylesheet" type="text/css" href="ic.css" />
</head>
<body>
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
<a name="rmtjob"></a>
<h3 id="rmtjob">Remote job submission</h3>
<p>OptiConnect allows jobs to be submitted on the local system and started
as a batch job on the target system transparently. These jobs must be created
using the Submit Job (SBMJOB) or Submit Database Jobs (SBMDBJOB) command.
This transparency is achieved by replacing QCMD routing entry in a subsystem
description (SBSD) with an entry that will route the submitted job to the
remote system. The following is an example of how to configure job submission: </p>
<ol type="1">
<li>Create a routing entry that calls QYYCROUT with two input parameters.
<a name="wq40"></a>
<div class="notetitle" id="wq40">Note:</div>
<div class="notebody">Routing entries do not allow program parameters. You will need to
create a program to call QYYCROUT and pass the parameters. It should look
like the following CL program example 'ROUTEPGM':</div>
<p></p>
<pre class="xmp">PGM
CALL PGM(QSOC/QYYCROUT) PARM(ddmfile libname)
ENDPGM</pre></li>
<li>Add a routing entry to a subsystem description (SBSD) and specify 'ROUTEPGM'
as the 'Program to Call'.</li>
<li>Create or change a job description to specify the routing data that is
to be the compare value for the routing entry just added.
<a name="wq41"></a>
<div class="notetitle" id="wq41">Note:</div>
<div class="notebody">All jobs submitted with this job description will run on the remote system
by the QYYCROUT program.</div></li>
<li>When the job is submitted, QYYCROUT is started. QYYCROUT then extracts
information from the DDM file passed in. This DDM file is not used after
this. The parameter for the DDM file should be:
<ul>
<li>Device = QYCTSOC</li>
<li>Mode = BATCHJOB</li>
<li>LCLLOCNAME = *LOC</li>
<li>REMOTE SYSTEM = target system name</li></ul></li>
<li>QYYCROUT creates a data queue and a DDM file in library QTEMP. It starts
a SOCA<var class="pv">nnnnnn</var> job and creates a data queue on the target system.</li>
<li>QYYCROUT then retrieves job attributes, cancel severity, and local data
area (LDA). The job and local data area information get sent to the remote
data queue on the target system. The target system runs a program to receive
this information and changes the target job's attributes to match the source
job.</li>
<li>QYYCROUT will extract information about inline data files and copy them
to QTEMP in the target job.</li></ol>
<p>The job queue on the source system receives request data one command at
a time and runs each request on the target. After each command is run, the
target job returns an indication of whether or not cancel severity has been
exceeded. This allows QYYCROUT to decide if the job should be terminated.
Since commands are run one at a time, holding the job on the source system
will end command execution on the target system until released.</p>
<p>After all the requests have been received and run, and if message logging
is set to something other than *NOLIST, the target joblog is retrieved and
written to QPJOBLOG. The user data field is set to the target system name.</p>
<p>To route the spooled file back to the source system:</p>
<ol type="1">
<li>Create a Remote Output queue by using the CRTOUTQ command.</li>
<li>Specify the system name that you will be routing files to in the Remote
System parameter. This will allow you to supply information to the remaining
parameters.</li>
<li>For the Remote Print Queue (RMTPRTQ) parameter, specify the output queue
to which the remote writer sends the spooled file.</li>
<li>Issue the Start Remote Writer (STRRMTWTR) command on the target system.
See <a href="rzau3rmtjob.htm#source">Figure 12</a> and <a href="rzau3rmtjob.htm#target">Figure 13</a>.</li></ol>
<a name="source"></a>
<div class="fignone" id="source"><span class="figcap">Figure 12. Remote Job Submission Source System</span>
<div class="mmobj">
<img src="rv4f202.gif" alt="Remote Job Submission Source System" /></div></div>
<a name="target"></a>
<div class="fignone" id="target"><span class="figcap">Figure 13. Remote Job Submission Target System</span>
<div class="mmobj">
<img src="rv4f203.gif" alt="Remote Job Submission Source System" /></div></div>
<p>&nbsp;</p>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>