121 lines
9.6 KiB
HTML
121 lines
9.6 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Operate remote iSeries servers" />
|
||
|
|
<meta name="abstract" content="As an administrator in a distributed relational database you might have to operate a remote iSeries server." />
|
||
|
|
<meta name="description" content="As an administrator in a distributed relational database you might have to operate a remote iSeries server." />
|
||
|
|
<meta name="DC.subject" content="remote server operation, starting and stopping, administration task, starting and stopping remote servers, database administration, starting and stopping remote servers, operating servers remotely, submitting remote commands, command, SBMRMTCMD (Submit Remote Command), Submit Remote Command (SBMRMTCMD), command, CL, SBMRMTCMD (Submit Remote Command), remote command, submitting, Submit Remote Command (SBMRMTCMD), command, CL, SBMRMTCMD (Submit Remote Command), authority restrictions, Submit Remote Command (SBMRMTCMD), authority restrictions, remote command, application server (AS), submit remote commands" />
|
||
|
|
<meta name="keywords" content="remote server operation, starting and stopping, administration task, starting and stopping remote servers, database administration, starting and stopping remote servers, operating servers remotely, submitting remote commands, command, SBMRMTCMD (Submit Remote Command), Submit Remote Command (SBMRMTCMD), command, CL, SBMRMTCMD (Submit Remote Command), remote command, submitting, Submit Remote Command (SBMRMTCMD), command, CL, SBMRMTCMD (Submit Remote Command), authority restrictions, Submit Remote Command (SBMRMTCMD), authority restrictions, remote command, application server (AS), submit remote commands" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1admin.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1ddmcnv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/dspcmd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/dspfd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/dspffd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../ddm/rbae5kickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzal2/rzal2powersched.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1setddm.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/sbmrmtcmd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzal2/rzal2iplsys.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="rbal1opremote" />
|
||
|
|
<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>Operate remote iSeries servers</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1opremote"><a name="rbal1opremote"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Operate remote <span class="keyword">iSeries server</span>s</h1>
|
||
|
|
<div><p>As an administrator in a distributed relational database you might
|
||
|
|
have to operate a remote <span class="keyword">iSeries™ server</span>.</p>
|
||
|
|
<p>For example, you might have to start or stop a remote server. The <span class="keyword">iSeries server</span> provides options that help
|
||
|
|
you ensure that a remote server is operating when it needs to be. Of course,
|
||
|
|
the simplest way to ensure that a remote server is operating is to allow the
|
||
|
|
remote location to power on their server to meet the distributed relational
|
||
|
|
database requirements. But, this is not always possible. You can set up an
|
||
|
|
automatic power-on and power-off schedule or enable a remote power on to a
|
||
|
|
remote server.</p>
|
||
|
|
<p>The server provides several ways to do this either in real time or at previously
|
||
|
|
scheduled times. More often, you might need to perform certain tasks on a
|
||
|
|
remote server as it is operating. The three primary ways that you can do this
|
||
|
|
is by using display station pass-through, the <span class="cmdname">Submit Remote Command
|
||
|
|
(SBMRMTCMD)</span> command, or stored procedures.</p>
|
||
|
|
<p>The <span class="cmdname">Submit Remote Command (SBMRMTCMD)</span> command submits
|
||
|
|
a CL command using Distributed Data Management (DDM) support to run on the application
|
||
|
|
server (AS). You first need to create a DDM file. The remote location information
|
||
|
|
of the DDM file is used to determine the communications line to be used. Thus,
|
||
|
|
it identifies the AS that is to receive the submitted command. The remote
|
||
|
|
file associated with the DDM file is not involved when the DDM file is used
|
||
|
|
for submitting commands to run on the AS.</p>
|
||
|
|
<p>The <span class="cmdname">Submit Remote Command (SBMRMTCMD)</span> command can submit
|
||
|
|
any CL command that can run in both the batch environment and through the
|
||
|
|
QCAEXEC system program; that is, the command has values of *BPGM <em>and</em> *EXEC
|
||
|
|
specified for the ALLOW attribute. You can display the ALLOW attributes by
|
||
|
|
using the <span class="cmdname">Display Command (DSPCMD)</span> command.</p>
|
||
|
|
<p>The primary purpose of the <span class="cmdname">Submit Remote Command (SBMRMTCMD)</span> command
|
||
|
|
is to allow an application requester (AR) user or program to perform file
|
||
|
|
management operations and file authorization activities on objects located
|
||
|
|
on an AS. A secondary purpose of this command is to allow a user to perform
|
||
|
|
nonfile operations (such as creating a message queue) or to submit user-written
|
||
|
|
commands to run on the AS. The CMD parameter allows you to specify a character
|
||
|
|
string of up to 2000 characters that represents a command to be run on the
|
||
|
|
AS.</p>
|
||
|
|
<p>You must have the proper authority on the AS for the CL command being submitted
|
||
|
|
and for the objects that the command is to operate on. If the AR user has
|
||
|
|
the correct authority to do so (as determined in an AS user profile), the
|
||
|
|
following actions are examples of what can be performed on remote files using
|
||
|
|
the <span class="cmdname">Submit Remote Command (SBMRMTCMD)</span> command:</p>
|
||
|
|
<ul><li>Grant or revoke object authority to remote tables</li>
|
||
|
|
<li>Verify tables or other objects</li>
|
||
|
|
<li>Save or restore tables or other objects</li>
|
||
|
|
</ul>
|
||
|
|
<p>Although the command can be used to do many things with tables or other
|
||
|
|
objects on the remote server, using this command for some tasks is not as
|
||
|
|
efficient as other methods on the <span class="keyword">iSeries server</span>.
|
||
|
|
For example, you can use this command to display the file descriptions or
|
||
|
|
field attributes of remote files, or to dump files or other objects, but the
|
||
|
|
output remains at the AS. To display remote file descriptions and field attributes
|
||
|
|
at the AR, a better method is to use the <span class="cmdname">Display File Description
|
||
|
|
(DSPFD)</span> and <span class="cmdname">Display File Field Description (DSPFFD)</span> commands
|
||
|
|
with SYSTEM(*RMT) specified, and specify the names of the DDM files associated
|
||
|
|
with the remote files.</p>
|
||
|
|
<p>See the Distributed data management topic for lists of CL commands you
|
||
|
|
can submit and restrictions for the use of these commands. In
|
||
|
|
addition, see Control DDM conversations for information about how DDM shares
|
||
|
|
conversations.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1admin.htm" title="As an administrator for a distributed relational database, you are responsible for work being done on several servers.">Administration</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../ddm/rbae5kickoff.htm">Distributed data management</a></div>
|
||
|
|
<div><a href="../rzal2/rzal2powersched.htm">Schedule a system shutdown and restart</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rbal1setddm.htm" title="The implementation of DRDA support on the iSeries server uses Distributed Data Management (DDM) conversations for communications. Because of this, you can use DDM in conjunction with distributed relational database processing.">Set up DDM files</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rbal1ddmcnv.htm" title="The term connection in this topic collection refers to the concept of an SQL connection. An SQL connection lasts from the time an explicit or implicit SQL CONNECT is done until the logical SQL connection is terminated by such means as an SQL DISCONNECT, or a RELEASE followed by a COMMIT.">Control DDM conversations</a></div>
|
||
|
|
<div><a href="../cl/dspcmd.htm">Display Command (DSPCMD) command</a></div>
|
||
|
|
<div><a href="../cl/dspfd.htm">Display File Description (DSPFD) command</a></div>
|
||
|
|
<div><a href="../cl/dspffd.htm">Display File Field Description (DSPFFD) command</a></div>
|
||
|
|
<div><a href="../cl/sbmrmtcmd.htm">Submit Remote Command (SBMRMTCMD) command</a></div>
|
||
|
|
<div><a href="../rzal2/rzal2iplsys.htm">System values that control IPL</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|