158 lines
11 KiB
HTML
158 lines
11 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="reference" />
|
||
|
|
<meta name="DC.Title" content="Additional considerations: SBMRMTCMD command" />
|
||
|
|
<meta name="abstract" content="This topic describes additional considerations for the SBMRMTCMD command." />
|
||
|
|
<meta name="description" content="This topic describes additional considerations for the SBMRMTCMD command." />
|
||
|
|
<meta name="DC.subject" content="DDM conversation, SBMRMTCMD command, command, syntax verifying, error message, handling, INQMSGRPY parameter" />
|
||
|
|
<meta name="keywords" content="DDM conversation, SBMRMTCMD command, command, syntax verifying, error message, handling, INQMSGRPY parameter" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5sbmcmd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5jobcnvs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5ddmcnv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5ovrdbf.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbae5addcons" />
|
||
|
|
<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>Additional considerations: SBMRMTCMD command</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5addcons"><a name="rbae5addcons"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Additional considerations: <span class="cmdname">SBMRMTCMD command</span></h1>
|
||
|
|
<div><p>This topic describes additional considerations for the SBMRMTCMD
|
||
|
|
command.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Override use example</h4><div class="p"> The DDMFILE parameter on the <span class="cmdname">SBMRMTCMD</span> command
|
||
|
|
is used to determine which target server the command (CMD parameter) should
|
||
|
|
be sent to. Overrides that apply to the DDM file (not the remote file) are
|
||
|
|
taken into account for this function. For example, if a file override was
|
||
|
|
in effect for a DDM file because of the following commands, which override
|
||
|
|
FILEA with FILEX, then the target server that the <span class="cmdname">Delete File (DLTF)</span> command
|
||
|
|
is sent to is the one associated with the remote location information specified
|
||
|
|
in DDM FILEX (the values point to the DENVER system, in this case). <pre>CRTDDMF FILE(SRCLIB/FILEA) RMTFILE(SALES/CAR)
|
||
|
|
RMTLOCNAME(CHICAGO)
|
||
|
|
CRTDDMF FILE(SRCLIB/FILEX) RMTFILE(SALES/CAR)
|
||
|
|
RMTLOCNAME(DENVER)
|
||
|
|
OVRDBF FILE(FILEA) TOFILE(SRCLIB/FILEX)
|
||
|
|
SBMRMTCMD CMD('DLTF RMTLIB/FRED') DDMFILE(SRCLIB/FILEA)</pre>
|
||
|
|
</div>
|
||
|
|
<p>This <span class="cmdname">SBMRMTCMD</span> command
|
||
|
|
deletes the file named FRED from the DENVER server.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">DDM conversations</h4><p> When a <span class="cmdname">SBMRMTCMD</span> command
|
||
|
|
is run on the target server, it has a target server job associated with it.
|
||
|
|
Successive <span class="cmdname">SBMRMTCMD</span> commands submitted using the same
|
||
|
|
DDM file and DDM conversation might run in the same or different target server
|
||
|
|
jobs, depending on the value of the DDMCNV job attribute. The value of the
|
||
|
|
DDMCNV job attribute determines whether the DDM conversation is dropped or
|
||
|
|
remains active when the submitted function has completed. If the conversation
|
||
|
|
is dropped, the next <span class="cmdname">SBMRMTCMD</span> command runs using a different
|
||
|
|
target job. If several commands are submitted, either DDMCNV(*KEEP) should
|
||
|
|
be in effect, or display station pass-through should be used instead of DDM.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Command syntax verifying</h4><p>The syntax of the command
|
||
|
|
character string being submitted by the CMD parameter is not verified by the
|
||
|
|
source server. In the case of a user-defined command, for example, the command
|
||
|
|
definition object might or might not exist on the source server.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Command running results</h4><p> Because the submitted command
|
||
|
|
runs as part of the target server's job, the attributes of that job (such
|
||
|
|
as the library search list, user profile, wait times, and running priority)
|
||
|
|
might cause a different result than if the command were run locally. If you
|
||
|
|
find that you are having difficulty submitting a command and, for example,
|
||
|
|
the reason is the target server uses a different library list, you can use
|
||
|
|
the <span class="cmdname">SBMRMTCMD</span> command to edit the library list.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Error message handling</h4><p>For errors detected by the
|
||
|
|
target server when processing the submitted command, the source server attempts
|
||
|
|
to send the same error information that was created on the target server to
|
||
|
|
the user. However, if the source server does not have an equivalent message
|
||
|
|
for the one created on the target server, the message sent to the source server
|
||
|
|
user has the message identifier and is of the message type and severity that
|
||
|
|
was created on the target server; the message text sent for the error is default
|
||
|
|
message text.</p>
|
||
|
|
<p>If the target server is a system other than an <span class="keyword">iSeries™ server</span> or <span class="keyword">System/36™</span>,
|
||
|
|
messages sent to the source server have no message identifiers or message
|
||
|
|
types. The only information received from such a target server is the message
|
||
|
|
text and a severity code. When a high severity code is returned from the target
|
||
|
|
server, the source server user receives a message that the <span class="cmdname">SBMRMTCMD</span> command
|
||
|
|
ended abnormally. Other messages sent by the target server are received as
|
||
|
|
informational with no message identifiers.</p>
|
||
|
|
<div class="p">For example,
|
||
|
|
you might see the following statements in your job log when both the source
|
||
|
|
and target are <span class="keyword">iSeries server</span>s: <pre>INFO CPI9155 'Following messages created on target server.'
|
||
|
|
DIAG CPD0028 'Library ZZZZ not found.'
|
||
|
|
ESCP CPF0006 'Errors occurred in command.'</pre>
|
||
|
|
</div>
|
||
|
|
<div class="p">When a target
|
||
|
|
server other than an <span class="keyword">iSeries server</span> returns
|
||
|
|
the same message to an <span class="keyword">iSeries</span> source
|
||
|
|
server, the job log looks like this: <pre>INFO CPI9155 'Following messages created on target server.'
|
||
|
|
INFO nomsgid 'Library ZZZZ not found.'
|
||
|
|
INFO nomsgid 'Errors occurred in command.'
|
||
|
|
ESCP CPF9172 'SBMRMTCMD command ended abnormally.'</pre>
|
||
|
|
</div>
|
||
|
|
<p>The target
|
||
|
|
server messages can be viewed on the source server by using pass-through and
|
||
|
|
either the <span class="cmdname">Work with Job (WRKJOB)</span> or <span class="cmdname">Work with
|
||
|
|
Job Log (WRKJOBLOG)</span> command. If the target job ends, the messages
|
||
|
|
are in the target server's output queue, where they can be displayed by the <span class="cmdname">Work
|
||
|
|
with Output Queue (WRKOUTQ)</span> command.</p>
|
||
|
|
<p>If the <span class="cmdname">SBMRMTCMD</span> command
|
||
|
|
is used to call a CL program on the target server, any escape message that
|
||
|
|
is not monitored and is created by the program is changed into an inquiry
|
||
|
|
message and is sent to the system operator. If you don't want the target system
|
||
|
|
operator to have to respond to this inquiry message before the job can continue,
|
||
|
|
you can refer to the <a href="../rbam6/rbam6clmain.htm">CL</a> topic
|
||
|
|
in the <span class="keyword">iSeries Information Center</span> and do either
|
||
|
|
of the following items on the target server:</p>
|
||
|
|
<ul><li> If you want to specify a default reply for a specific <em>job</em>, you
|
||
|
|
can use the INQMSGRPY parameter on either the <span class="cmdname">Create Job Description
|
||
|
|
(CRTJOBD)</span> or <span class="cmdname">Change Job Description (CHGJOBD)</span> command
|
||
|
|
to specify either *DFT or *SYSRPYL in the job description for the target job.
|
||
|
|
You can also do the same thing if you use the <span class="cmdname">SBMRMTCMD</span> command
|
||
|
|
to submit the <span class="cmdname">Change Job (CHGJOB)</span> command to the target
|
||
|
|
server.</li>
|
||
|
|
<li>If you want to specify a default reply message for a specific <em>inquiry
|
||
|
|
message</em> in the job, you can use the <span class="cmdname">Add Reply List Entry (ADDRPYLE)</span> command
|
||
|
|
(on the target server) to add an entry for that message to the system-wide
|
||
|
|
automatic message reply list (SYSRPYL). Then, if INQMSGRPY(*SYSRPYL) is specified
|
||
|
|
in the job description, this default reply can be sent whenever that inquiry
|
||
|
|
message occurs in the job.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section" id="rbae5addcons__targetjob"><a name="rbae5addcons__targetjob"><!-- --></a><h4 class="sectiontitle">Independent auxiliary storage pools (ASPs)</h4><p>If
|
||
|
|
the target system has online independent ASPs, the independent ASP group of
|
||
|
|
the target job is established when the conversation is started and might not
|
||
|
|
be changed. User-defined or CL commands that attempt to change the independent
|
||
|
|
ASP group of the target job (for example, <span class="cmdname">SETASPGRP</span> or <span class="cmdname">DLTUSRPRF</span>)
|
||
|
|
might fail if submitted to a target system that has online independent ASPs. </p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5sbmcmd.htm" title="The Submit Remote Command (SBMRMTCMD) command submits a command using DDM to run on the target server.">SBMRMTCMD (Submit Remote Command) command</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbae5jobcnvs.htm" title="This topic provides additional information about activation groups, source server jobs, target server jobs, and the DDM conversations used by those jobs.">DDM-related jobs and DDM conversations</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rbae5ddmcnv.htm" title="The DDMCNV parameter is a job-related parameter that controls whether Advanced Program-to-Program Communication (APPC) or iSeries conversations in the job that is allocated for DDM use (that is, DDM conversations) are to be automatically dropped or kept active for the source job.">DDMCNV parameter considerations</a></div>
|
||
|
|
<div><a href="rbae5ovrdbf.htm" title="The Override with Database File (OVRDBF) command can be used with DDM to override (replace) a local database file named in the program with a DDM file; the DDM file causes the associated remote file to be used by the program instead of the local database file.">OVRDBF (Override with Database File) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|