125 lines
8.9 KiB
HTML
125 lines
8.9 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 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-09-13" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 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>Guidelines for submitting remote commands</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="rzahqremotecmdguidelines"></a>
|
||
|
<h3 id="rzahqremotecmdguidelines">Guidelines for submitting remote commands</h3>
|
||
|
<p>To remotely submit integrated Windows server commands, keep these guidelines
|
||
|
in mind:</p>
|
||
|
<p><span class="bold">Note:</span> Many of the SBMNWSCMD parameters discussed
|
||
|
in this section are not available when running Windows commands by using iSeries™ Navigator. If you need to use a parameter that iSeries Navigator
|
||
|
does not support, then you must use Submit Network Server Command (SBMNWSCMD)
|
||
|
directly.</p>
|
||
|
<ul>
|
||
|
<li>The requested command is run under the Windows console command "cmd.exe."
|
||
|
SBMNWSCMD will not return control to its caller until the command has finished
|
||
|
running on Windows and the cmd.exe program terminates.</li>
|
||
|
<li>The authentication domain field of SBMNWSCMD indicates the Windows domain
|
||
|
where your user ID is to be authenticated. The default, *PRIMARY, logs on
|
||
|
to the primary domain of the server, if the server is a domain member. *LOCAL
|
||
|
logs on to the server itself. The name of a trusted domain may also be specified.</li>
|
||
|
<li>The QSECOFR user profile is handled differently than all other user profiles.
|
||
|
User authentication is not performed on Windows when SBMNWSCMD is run by the
|
||
|
QSECOFR profile. The requested Windows command is run under the Windows Local
|
||
|
System Account. The Local System Account is used even if the QSECOFR profile
|
||
|
is enrolled. The Local System Account does not have a password and lacks network
|
||
|
access rights.</li>
|
||
|
<li>Do not use the "/u" parameter with the Windows "cmd" command.</li>
|
||
|
<li>SBMNWSCMD has limited support of Kerberos v5 authentication. Kerberos
|
||
|
will only be used when the LCLPWDMGT user profile attribute is *NO. See <a href="rzahqsbmnwscmdandkerberos.htm#rzahqsbmnwscmdandkerberos">SBMNWSCMD and file level backup support for Kerberos v5 and EIM</a>.</li>
|
||
|
<li>The Remote Command service and SBMNWSCMD are able to distinguish between
|
||
|
ASCII multi-byte and unicode output data and convert them as appropriate.</li>
|
||
|
<li>You can combine integrated Windows server commands into a single command
|
||
|
string by using features of the Windows "cmd.exe" command interpreter. For
|
||
|
example, on the SBMNWSCMD command line, you can enter <tt>net statistics workstation && net statistics server</tt> to collect
|
||
|
statistics. However, commands that you combine in a single SBMNWSCMD request
|
||
|
should not return mixed data (for example, a combination of ASCII and Unicode
|
||
|
data), or data in mixed codesets. If the commands return different types of
|
||
|
data, SBMNWSCMD may end abnormally with a message which indicates "a problem
|
||
|
occurred in the data output conversion." In that case, run the commands separately.</li>
|
||
|
<li>Do not use characters that are not normally available from the integrated
|
||
|
server keyboard. In rare cases, an EBCDIC character in the active jobs coded
|
||
|
character set may not have an equivalent in the active code page on Windows.
|
||
|
Each different Windows application will give different conversion results.</li>
|
||
|
<li>The Submit Network Server Command does not completely initialize your
|
||
|
logon environment. The user's environment variables are set, but may not
|
||
|
be completely equal to those provided by an interactive logon. Thus, environmental
|
||
|
variables that an interactive logon normally sets to user-specific values
|
||
|
may not exist or may be set to system default values. Any scripts or applications
|
||
|
that rely on user-specific environmental variables may not operate correctly.</li>
|
||
|
<li>If the home directory for your user ID on the integrated server is mounted
|
||
|
on the local server, the Submit Network Server Command sets the current directory
|
||
|
to your home directory. Otherwise, it tries to use /home/default or the local
|
||
|
system drive.</li>
|
||
|
<li><img src="delta.gif" alt="Start of change" />If the Load User Profile (LODUSRPRF) keyword is *YES, and if
|
||
|
a user profile exists, SBMNWSCMD will attempt to load your Windows profile.
|
||
|
You can then use commands that use or alter profile dependencies. However,
|
||
|
there is no indication of profile load failures, beyond event log messages
|
||
|
that may be produced by Windows. A windows profile can only be active in one
|
||
|
Windows Logon session.<img src="deltaend.gif" alt="End of change" /></li>
|
||
|
<li>You can use SBMNWSCMD to run integrated server applications as long as
|
||
|
they do not require user intervention. The commands run in a background window,
|
||
|
not on the integrated server console. If an application requests user intervention,
|
||
|
such as popping up a message window, then SBMNWSCMD will hang, waiting for
|
||
|
the command to complete - but no intervention is possible. If you end SBMNWSCMD
|
||
|
on i5/OS™, it will attempt to end the hung Windows command. The background
|
||
|
command stops whether GUI or console based.</li>
|
||
|
<li>You can also run commands that require a <span class="bold">yes</span> or <span class="bold"> no</span> reply to proceed. You do this by using input pipe syntax
|
||
|
to provide the response. For example, <tt>echo y|format
|
||
|
f: /fs:ntfs</tt> will let the format proceed after the <span class="bold">Proceed with Format</span> question raised by the format command. Note that
|
||
|
the "y" and the pipe symbol "|" do not have a space between them. However,
|
||
|
not all Windows batch commands support the piping of input (for example,
|
||
|
the "net" command). Attempts to pass a default response may not be possible.</li>
|
||
|
<li>You can prevent SBMNWSCMD from logging the command. If the command string
|
||
|
contains sensitive data, such as passwords, that you do not want logged in
|
||
|
error messages, do the following steps:
|
||
|
<ol type="1">
|
||
|
<li>Specify <tt>*NOLOGCMD</tt> as the command string.</li>
|
||
|
<li>When the <tt>Command (not logged)</tt> field appears,
|
||
|
enter the command to run in this field.</li></ol> Note, however, that the *NOLOGCMD option does not affect data that the
|
||
|
command returns. If the command returns sensitive data, you can use the command
|
||
|
standard output (CMDSTDOUT) parameter to store the output in a secure location,
|
||
|
such as an integrated file system file.</li>
|
||
|
<li>You can direct standard output from the command to your job log (<tt>*JOBLOG</tt>), to a spool file (<tt>*PRINT</tt>), or to an integrated file system (IFS) object. Standard error
|
||
|
data always goes to the job log.
|
||
|
<p>When you specify *PRINT, the Work with
|
||
|
Spool File (WRKSPLF) display shows SBMNWSCMD in the User Data field for the
|
||
|
spooled file. If you select option 8 to display the attributes, the names
|
||
|
of the specified integrated server and Windows command appear in the user-defined
|
||
|
data field.</p>
|
||
|
<p>When you specify an integrated file system object, the path
|
||
|
name must already exist. If the integrated file system object name does not
|
||
|
exist, SBMNWSCMD creates it.</p></li>
|
||
|
<li>In the <tt>Convert standard output</tt> field, you
|
||
|
can specify (<tt>*YES</tt>) to convert output from the
|
||
|
Windows code set to the coded character set identifier (CCSID) of the i5/OS job.
|
||
|
<p>New IFS files will be created with the job CCSID. Output directed
|
||
|
to an existing IFS object is converted to the IFS object CCSID. Output directed
|
||
|
to a new member of an existing file in the <tt>/QSYS.LIB</tt> file system is converted to the existing file CCSID.</p></li>
|
||
|
<li><img src="delta.gif" alt="Start of change" />If Convert standard output is (*NO), the Windows standard output
|
||
|
will be written to the IFS object, or spool file, with CCSID conversion.<img src="deltaend.gif" alt="End of change" /></li></ul>
|
||
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
</body>
|
||
|
</html>
|