827 lines
30 KiB
HTML
827 lines
30 KiB
HTML
|
|
<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<html>
|
|
<head><META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
|
<title>Add Command CRQ Activity (ADDCMDCRQA)</title>
|
|
</head>
|
|
<body bgcolor="white">
|
|
<a name="ADDCMDCRQA.Top_Of_Page"></a>
|
|
<h2>Add Command CRQ Activity (ADDCMDCRQA)</h2>
|
|
<table width="100%">
|
|
<tr>
|
|
<td valign="top" align="left"><b>Where allowed to run: </b>All environments (*ALL)<br>
|
|
<b>Threadsafe: </b>No
|
|
</td>
|
|
<td valign="top" align="right">
|
|
<a href="#ADDCMDCRQA.PARAMETERS.TABLE">Parameters</a><br>
|
|
<a href="#ADDCMDCRQA.COMMAND.EXAMPLES">Examples</a><br>
|
|
<a href="#ADDCMDCRQA.ERROR.MESSAGES">Error messages</a></td>
|
|
</tr>
|
|
</table>
|
|
|
|
<div> <a name="ADDCMDCRQA"></a>
|
|
<p>The Add Command Change Request Activity (ADDCMDCRQA) command adds an activity to a change request description to run a command on one or more managed systems.
|
|
</p>
|
|
<p>The activity can be conditioned so that it only runs after one or more other activities have completed (successfully or unsuccessfully). The activity can also be scheduled to run at a date and time in the future.
|
|
</p>
|
|
<p><b>Restrictions:</b>
|
|
</p>
|
|
<ol>
|
|
<li>You must have *CHANGE authority to the change request description and *EXECUTE authority to the library.
|
|
</li>
|
|
<li>If a node list (NODL) value is specified, the node list can only contain entries that have a value of *SNA for the address type.
|
|
</li>
|
|
</ol>
|
|
<p><b>Notes:</b>
|
|
</p>
|
|
<p>The following notes provide information on how the command works.
|
|
</p>
|
|
<ol>
|
|
<li>Authorization to the product specified on the activity is not verified until the activity runs.
|
|
</li>
|
|
<li>All conditions must be satisfied before the activity can run.
|
|
</li>
|
|
<li>The start times indicate when the activity can be started. Actual start times can be later due to network and system delays.
|
|
</li>
|
|
</ol>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<hr size="2" width="100%">
|
|
|
|
<div>
|
|
<h3><a name="ADDCMDCRQA.PARAMETERS.TABLE">Parameters</a></h3>
|
|
<table border="1" cellpadding="4" cellspacing="0">
|
|
<!-- col1="10" col2="15" col3="30" col4="10" -->
|
|
<tr>
|
|
<th bgcolor="aqua" valign="bottom" align="left">Keyword</th>
|
|
<th bgcolor="aqua" valign="bottom" align="left">Description</th>
|
|
<th bgcolor="aqua" valign="bottom" align="left">Choices</th>
|
|
<th bgcolor="aqua" valign="bottom" align="left">Notes</th>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="3"><a href="#ADDCMDCRQA.CRQD"><b>CRQD</b></a></td>
|
|
<td valign="top">Change request description</td>
|
|
<td valign="top"><i>Qualified object name</i></td>
|
|
<td valign="top" rowspan="3">Required, Positional 1</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Qualifier 1: Change request description</td>
|
|
<td valign="top"><i>Name</i></td>
|
|
</tr><tr>
|
|
<td valign="top">Qualifier 2: Library</td>
|
|
<td valign="top"><i>Name</i>, <b><u>*LIBL</u></b>, *CURLIB</td>
|
|
</tr><tr>
|
|
<td valign="top"><a href="#ADDCMDCRQA.ACTIVITY"><b>ACTIVITY</b></a></td>
|
|
<td valign="top">Activity</td>
|
|
<td valign="top"><i>Name</i>, <b><u>*GEN</u></b>, *LAST</td>
|
|
<td valign="top">Optional, Positional 2</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDCMDCRQA.CMD"><b>CMD</b></a></td>
|
|
<td valign="top">Command to run</td>
|
|
<td valign="top"><i>Command string</i></td>
|
|
<td valign="top">Optional, Positional 3</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDCMDCRQA.NODL"><b>NODL</b></a></td>
|
|
<td valign="top">Managed systems node list</td>
|
|
<td valign="top"><i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Node list</td>
|
|
<td valign="top">
|
|
Single values: <b><u>*NONE</u></b><br>Other values: <i>Qualified object name</i></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" style="padding-left:10pt">Qualifier 1: Node list</td>
|
|
<td valign="top"><i>Name</i></td>
|
|
</tr><tr>
|
|
<td valign="top" style="padding-left:10pt">Qualifier 2: Library</td>
|
|
<td valign="top"><i>Name</i>, <b><u>*LIBL</u></b>, *CURLIB</td>
|
|
</tr><tr>
|
|
<td valign="top" rowspan="3"><a href="#ADDCMDCRQA.CPNAME"><b>CPNAME</b></a></td>
|
|
<td valign="top">Managed system node names</td>
|
|
<td valign="top">Single values: <b><u>*LOCAL</u></b>, *NONE<br>Other values (up to 50 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="3">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Network identifier</td>
|
|
<td valign="top">
|
|
<i>Communications name</i>, <b><u>*NETATR</u></b></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Control point</td>
|
|
<td valign="top">
|
|
<i>Communications name</i></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="8"><a href="#ADDCMDCRQA.RMTSTRTIME"><b>RMTSTRTIME</b></a></td>
|
|
<td valign="top">Start time on managed system</td>
|
|
<td valign="top"><i>Element list</i></td>
|
|
<td valign="top" rowspan="8">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Time zone</td>
|
|
<td valign="top">
|
|
<b><u>*LCLSYS</u></b>, *MGDSYS</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Start after</td>
|
|
<td valign="top">
|
|
<i>Element list</i></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" style="padding-left:10pt">Element 1: Time</td>
|
|
<td valign="top">
|
|
<i>Time</i>, <b><u>*CURRENT</u></b></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" style="padding-left:10pt">Element 2: Date</td>
|
|
<td valign="top">
|
|
<i>Date</i>, <b><u>*CURRENT</u></b>, *NEXT</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Start before</td>
|
|
<td valign="top">
|
|
<i>Element list</i></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" style="padding-left:10pt">Element 1: Time</td>
|
|
<td valign="top">
|
|
<i>Time</i>, <b><u>*ANY</u></b>, *CURRENT</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" style="padding-left:10pt">Element 2: Date</td>
|
|
<td valign="top">
|
|
<i>Date</i>, <b><u>*ANY</u></b>, *CURRENT, *NEXT</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDCMDCRQA.RTNSPLF"><b>RTNSPLF</b></a></td>
|
|
<td valign="top">Return spooled file</td>
|
|
<td valign="top"><b><u>*YES</u></b>, *NO, *FAIL</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDCMDCRQA.USRPRF"><b>USRPRF</b></a></td>
|
|
<td valign="top">User profile</td>
|
|
<td valign="top"><i>Simple name</i>, <b><u>*NONE</u></b></td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDCMDCRQA.PASSWORD"><b>PASSWORD</b></a></td>
|
|
<td valign="top">Password</td>
|
|
<td valign="top"><i>Character value</i>, *USRPRF, <b><u>*NONE</u></b></td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDCMDCRQA.ENCODE"><b>ENCODE</b></a></td>
|
|
<td valign="top">Encode command</td>
|
|
<td valign="top">*YES, <b><u>*NO</u></b></td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDCMDCRQA.TEXT"><b>TEXT</b></a></td>
|
|
<td valign="top">Text 'description'</td>
|
|
<td valign="top"><i>Character value</i>, <b><u>*GEN</u></b></td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="5"><a href="#ADDCMDCRQA.COND"><b>COND</b></a></td>
|
|
<td valign="top">Activity conditions</td>
|
|
<td valign="top">Single values: *NONE<br>Other values (up to 5 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="5">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Activity</td>
|
|
<td valign="top">
|
|
<i>Generic name, name</i>, <b><u>*PRV</u></b></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Relational operator</td>
|
|
<td valign="top">
|
|
<b><u>*EQ</u></b>, *GT, *LT, *LE, *NE, *GE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: End code</td>
|
|
<td valign="top">
|
|
0-99, <b><u>*SUCCESS</u></b>, *FAIL, *NOTRUN, *ANY</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 4: Condition mode</td>
|
|
<td valign="top">
|
|
<b><u>*ALLNODES</u></b>, *SAMENODE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="7"><a href="#ADDCMDCRQA.STRTIME"><b>STRTIME</b></a></td>
|
|
<td valign="top">Activity start time</td>
|
|
<td valign="top"><i>Element list</i></td>
|
|
<td valign="top" rowspan="7">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Start after</td>
|
|
<td valign="top">
|
|
<i>Element list</i></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" style="padding-left:10pt">Element 1: Time</td>
|
|
<td valign="top">
|
|
<i>Time</i>, <b><u>*CURRENT</u></b></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" style="padding-left:10pt">Element 2: Date</td>
|
|
<td valign="top">
|
|
<i>Date</i>, <b><u>*CURRENT</u></b>, *NEXT</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Start before</td>
|
|
<td valign="top">
|
|
<i>Element list</i></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" style="padding-left:10pt">Element 1: Time</td>
|
|
<td valign="top">
|
|
<i>Time</i>, <b><u>*ANY</u></b>, *CURRENT</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" style="padding-left:10pt">Element 2: Date</td>
|
|
<td valign="top">
|
|
<i>Date</i>, <b><u>*ANY</u></b>, *CURRENT, *NEXT</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDCMDCRQA.HOLD"><b>HOLD</b></a></td>
|
|
<td valign="top">Hold activity</td>
|
|
<td valign="top"><b><u>*NO</u></b>, *YES</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
</table>
|
|
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
</div>
|
|
<div> <a name="ADDCMDCRQA.CRQD"></a>
|
|
<h3>Change request description (CRQD)</h3>
|
|
<p>Specifies the change request description object name.
|
|
</p>
|
|
<p>The possible library values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*LIBL</u></b></dt>
|
|
<dd>All of the libraries in your library list and in the system portions of the job's library list are searched.
|
|
</dd>
|
|
<dt><b>*CURLIB</b></dt>
|
|
<dd>The current library for the job is used to locate the object.
|
|
</dd>
|
|
<dt><b><i>library-name</i></b></dt>
|
|
<dd>Specify that only the library named in this parameter is searched.
|
|
</dd>
|
|
</dl>
|
|
<p>The possible change request description value is:
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>change-request-description</i></b></dt>
|
|
<dd>Specify the name of the change request description object.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDCMDCRQA.ACTIVITY"></a>
|
|
<h3>Activity (ACTIVITY)</h3>
|
|
<p>Specifies the name of the activity to add to the change request description.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*GEN</u></b></dt>
|
|
<dd>An activity name is generated. The activity name is of the form QACTxxxxxx where xxxxxx is the first multiple of ten not already being used.
|
|
</dd>
|
|
<dt><b>*LAST</b></dt>
|
|
<dd>The activity is the last to run in the change request. When *LAST is specified for the activity (ACTIVITY) parameter, the condition (COND) parameter and the start time (STRTIME) parameter cannot be specified. Only one activity named *LAST can exist in the change request description.
|
|
</dd>
|
|
<dt><b><i>activity-name</i></b></dt>
|
|
<dd>Specify a 10-character activity name.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDCMDCRQA.CMD"></a>
|
|
<h3>Command to run (CMD)</h3>
|
|
<p>Specifies the CL command to run. The command can be any command that can be run in batch. The command must follow the i5/OS CL command format of 1 to 10 characters with the first character in alphabetic order and the other nine characters alphanumeric.
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>command-string</i></b></dt>
|
|
<dd>Specify the command to run on the managed system. Command prompting support is available if you press F4.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDCMDCRQA.NODL"></a>
|
|
<h3>Managed systems node list (NODL)</h3>
|
|
<p>Specifies that the node list parameter is the object name that contains a list of systems which are the destinations for the activity. This parameter cannot be specified if the control point name (CPNAME) parameter is specified.
|
|
</p>
|
|
<p>The possible values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>The systems on which this activity is to be performed are not specified by a node list. Individual control point names must be specified.
|
|
</dd>
|
|
</dl>
|
|
<p>The possible values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b>*LIBL</b></dt>
|
|
<dd>All of the libraries in the user and system portions of the job's library list are searched for the node list object.
|
|
</dd>
|
|
<dt><b>*CURLIB</b></dt>
|
|
<dd>The current library for the job is used to locate the node list object.
|
|
</dd>
|
|
<dt><b><i>library-name.</i></b></dt>
|
|
<dd>Specify the name of the library to be searched.
|
|
</dd>
|
|
</dl>
|
|
<p>The possible node list name value is:
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>node-list-name</i></b></dt>
|
|
<dd>Specify the node list object name containing the list of systems on which the activity is to be performed.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDCMDCRQA.CPNAME"></a>
|
|
<h3>Managed system node names (CPNAME)</h3>
|
|
<p>Specifies the APPN control point names of the managed systems on which this activity is to be performed. Control point names cannot be specified if the node list (NODL) parameter is specified.
|
|
</p>
|
|
<p>The possible values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*LOCAL</u></b></dt>
|
|
<dd>The local system is identified as the target system. If *LOCAL is specified, the command is run on the local system. Any spooled files created remain on the system.
|
|
</dd>
|
|
<dt><b>*NONE</b></dt>
|
|
<dd>The systems on which this activity is to be performed are not identified individually. A node list must be specified.
|
|
</dd>
|
|
<dt><b>*NETATR</b></dt>
|
|
<dd>The network ID of the local system is used. This is useful when the node being specified is in the same network as the local system.
|
|
</dd>
|
|
<dt><b><i>network-identifier</i></b></dt>
|
|
<dd>Specify the APPN network identifier of the managed system on which the activity is to be performed.
|
|
</dd>
|
|
</dl>
|
|
<p>The possible control point value is:
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>control-point-name</i></b></dt>
|
|
<dd>Specify the APPN control point name of the managed system on which the activity is to be performed.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDCMDCRQA.RMTSTRTIME"></a>
|
|
<h3>Start time on managed system (RMTSTRTIME)</h3>
|
|
<p>Specifies the date and time when the activity can begin running on the managed system. The current date and time values, and the next date values are determined when the activity begins running at the central site system based on the central site date and time.
|
|
</p>
|
|
<p>The possible time zone values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*LCLSYS</u></b></dt>
|
|
<dd>The remote start time is specified in the time zone of the central site system.
|
|
</dd>
|
|
<dt><b>*MGDSYS</b></dt>
|
|
<dd>The remote start time is specified in the time zone of the managed system.
|
|
</dd>
|
|
</dl>
|
|
<p>The possible start after time values are:
|
|
</p>
|
|
<p>This is the definition of the time after which the activity is to start.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*CURRENT</u></b></dt>
|
|
<dd>This function can start on the managed system at any time on or after the time this activity is started on the date specified in element 3.
|
|
</dd>
|
|
<dt><b><i>start-after-time</i></b></dt>
|
|
<dd>Specify the time after when this function can start on the managed system. The time can be entered as 4 or 6 digits (hhmm or hhmmss) where, hh = hours, mm = minutes, and ss = seconds. Seconds are optional. The time can be specified with or without a time separator. With a time separator, specify a string of 5 or 8 digits (hh:mm or hh:mm:ss).
|
|
</dd>
|
|
</dl>
|
|
<p>The possible start after date values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*CURRENT</u></b></dt>
|
|
<dd>This function starts on the managed system on any date on or after the activity starts on the central site system.
|
|
</dd>
|
|
<dt><b>*NEXT</b></dt>
|
|
<dd>This function starts on the managed system on any date after the activity starts on the central site system.
|
|
</dd>
|
|
<dt><b><i>start-after-date</i></b></dt>
|
|
<dd>Specify the date after the functions start on the managed system. The date must be specified in the job date format.
|
|
</dd>
|
|
</dl>
|
|
<p>The possible start before time values are:
|
|
</p>
|
|
<p>This element is ignored if start before time is *ANY.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*ANY</u></b></dt>
|
|
<dd>The activity can start at any time on or after the start time.
|
|
</dd>
|
|
<dt><b>*CURRENT</b></dt>
|
|
<dd>The activity must start before the time at which the change request was submitted on the date specified on the start before date element.
|
|
</dd>
|
|
<dt><b><i>start-before-time</i></b></dt>
|
|
<dd>Specify the time before which the activity must be started. If the activity cannot be started before this time, it never starts. The time can be entered as 4 or 6 digits (hhmm or hhmmss) where hh = hours, mm = minutes, and ss = seconds. Seconds are optional. The time can be specified with or without a time separator. With a time separator, specify a string of 5 or 8 digits (hh:mm or hh:mm:ss).
|
|
</dd>
|
|
</dl>
|
|
<p>The possible start before date values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*ANY</u></b></dt>
|
|
<dd>The activity can start at any date on or after the start date.
|
|
</dd>
|
|
<dt><b>*CURRENT</b></dt>
|
|
<dd>The activity must start on the date the change request was submitted.
|
|
</dd>
|
|
<dt><b>*NEXT</b></dt>
|
|
<dd>The activity must start by the day after the date the change request was submitted.
|
|
</dd>
|
|
<dt><b><i>start-before-date</i></b></dt>
|
|
<dd>The date before which the activity must be started. If the activity cannot be started by this date, it never starts. The date must be specified in the job date format.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Note:</b>
|
|
</p>
|
|
<p>The special values *CURRENT and *NEXT cannot be specified for the date and the time if the time zone value *MGDSYS is specified.
|
|
</p>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDCMDCRQA.RTNSPLF"></a>
|
|
<h3>Return spooled file (RTNSPLF)</h3>
|
|
<p>Specifies whether the output spooled file from the remote command is returned.
|
|
</p>
|
|
<p>The possible values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*YES</u></b></dt>
|
|
<dd>The spooled files created from the remote command are returned from the managed system. The spooled files from all of the nodes are combined into one spooled file that can be viewed by displaying the command activity details of the change request.
|
|
</dd>
|
|
<dt><b>*NO</b></dt>
|
|
<dd>The output data is not returned from the managed system.
|
|
</dd>
|
|
<dt><b>*FAIL</b></dt>
|
|
<dd>The spooled file job log is returned from the managed system if the command fails when running.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDCMDCRQA.USRPRF"></a>
|
|
<h3>User profile (USRPRF)</h3>
|
|
<p>Specifies the user profile under which the command runs at the remote systems. If the remote system is running the NetView Remote Operations Agent/400 product this parameter is ignored at the remote systems.
|
|
</p>
|
|
<p>The possible values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No user profile is specified. The default user profile is used on each managed system.
|
|
</dd>
|
|
<dt><b><i>user-profile</i></b></dt>
|
|
<dd>Specify the name of the user profile.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDCMDCRQA.PASSWORD"></a>
|
|
<h3>Password (PASSWORD)</h3>
|
|
<p>Specifies the password for the remote user profile.
|
|
</p>
|
|
<ul>
|
|
<li>Managed Systems at releases prior to V5R1M0 only accept uppercased passwords up to 10 characters long. If a longer password is entered, SMU18A2 message with 100B0007 SNA sense code is returned, indicating that the request was rejected.
|
|
</li>
|
|
<li>Managed Systems at release V5R1M0 and above, running with QPWDLVL system value:
|
|
<ul>
|
|
<li>0 or 1 -- truncate the received passwords to 10 characters.
|
|
</li>
|
|
<li>2 or 3 -- accept passwords up to 128 characters.
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
<p>The possible values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No password is specified.
|
|
</dd>
|
|
<dt><b>*USRPRF</b></dt>
|
|
<dd>The password is the same as the user profile.
|
|
</dd>
|
|
<dt><b><i>password</i></b></dt>
|
|
<dd>Specify the password for the user profile.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDCMDCRQA.ENCODE"></a>
|
|
<h3>Encode command (ENCODE)</h3>
|
|
<p>Specifies whether or not the command, user profile, and password are encoded when sent to the managed systems. If the managed system is running the NetView Remote Operations Agent/400 product, this parameter must be to *NO.
|
|
</p>
|
|
<p>The possible values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NO</u></b></dt>
|
|
<dd>The command, user profile, and password are not encoded when the request is sent to the managed systems.
|
|
</dd>
|
|
<dt><b>*YES</b></dt>
|
|
<dd>The command, user profile, and password are encoded when the request is sent to the managed systems. The remote command key, which is a managed system attribute, must be specified on both the central site system and the managed system. This attribute can be changed using the Change Managed System Attributes (CHGMGDSYSA) command. The remote command key must be the same on the central site system and the managed system.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDCMDCRQA.TEXT"></a>
|
|
<h3>Text 'description' (TEXT)</h3>
|
|
<p>Specifies the activity description.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*GEN:</u></b></dt>
|
|
<dd>A description is generated based on the action specified.
|
|
</dd>
|
|
<dt><b><i>text-description</i></b></dt>
|
|
<dd>Specify a 50-character description of the activity.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDCMDCRQA.COND"></a>
|
|
<h3>Activity conditions (COND)</h3>
|
|
<p>Specifies which conditions must be met before this activity can be performed. Each condition identifies an activity which must run before this activity and the value the end code from that activity must have to allow this activity to run. The default condition is that the previous activity (in alphabetical order) must complete successfully before this activity can be run.
|
|
</p>
|
|
<p>The possible conditioning activity values are:
|
|
</p>
|
|
<p>The activity which must be run before this activity.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*PRV</u></b></dt>
|
|
<dd>This activity is conditioned on the previous activity. Activities are ordered alphabetically by activity name. If the activity being added is the first activity, a previous activity does not exist and any condition with *PRV is marked as having been met.
|
|
</dd>
|
|
<dt><b><i>conditioning-activity-name</i></b></dt>
|
|
<dd>Specify the name of this activity which must run before this activity. The activity name specified in the activity (ACTIVITY) parameter cannot be specified in the conditioning activity name. An activity cannot be conditioned on itself.
|
|
</dd>
|
|
<dt><b><i>generic*-conditioning-activity-name</i></b></dt>
|
|
<dd>Specify the generic name of the activities which must run before this activity.
|
|
</dd>
|
|
</dl>
|
|
<p>The possible relational operator value is:
|
|
</p>
|
|
<p>This element is the relational operator to use when comparing the end code from the conditioning activity.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*EQ</u></b></dt>
|
|
<dd>Equal
|
|
</dd>
|
|
<dt><b>*GT</b></dt>
|
|
<dd>Greater than
|
|
</dd>
|
|
<dt><b>*LT</b></dt>
|
|
<dd>Less than
|
|
</dd>
|
|
<dt><b>*NE</b></dt>
|
|
<dd>Not equal
|
|
</dd>
|
|
<dt><b>*GE</b></dt>
|
|
<dd>Greater than or equal
|
|
</dd>
|
|
<dt><b>*LE</b></dt>
|
|
<dd>Less than or equal
|
|
</dd>
|
|
</dl>
|
|
<p>The possible condition code value is:
|
|
</p>
|
|
<p>This element is the value compared to the actual end code of the conditioning activity.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*SUCCESS</u></b></dt>
|
|
<dd>The activity ended successfully (0 <= end code <= 9). This end code can only be specified with relational operator *EQ or *NE.
|
|
</dd>
|
|
<dt><b>*FAIL</b></dt>
|
|
<dd>The activity failed (10 <= end code <= 89). This end code can only be specified with relational operator *EQ or *NE.
|
|
</dd>
|
|
<dt><b>*NOTRUN</b></dt>
|
|
<dd>The activity never started (90 <= end code <= 99). This end code is only specified with relational operator *EQ or *NE.
|
|
</dd>
|
|
<dt><b>*ANY</b></dt>
|
|
<dd>The activity ended with any end code. This end code is only specified with relational operator *EQ.
|
|
</dd>
|
|
<dt><b><i>end-code</i></b></dt>
|
|
<dd>Specify an integer value (0-99) that indicates the result of an activity (success or failure). The end code ranges and descriptions are the following:
|
|
<dl>
|
|
<dt><b>00</b></dt>
|
|
<dd>Activity completed successfully.
|
|
</dd>
|
|
<dt><b>01-09</b></dt>
|
|
<dd>Activity completed with warning messages.
|
|
</dd>
|
|
<dt><b>10-29</b></dt>
|
|
<dd>Activity did not complete successfully.
|
|
</dd>
|
|
<dt><b>30-39</b></dt>
|
|
<dd>Activity was canceled by a user before it completed.
|
|
<ul>
|
|
<li>30 = Activity ended with *CNTRLD option
|
|
</li>
|
|
<li>35 = Activity ended with *IMMED option
|
|
</li>
|
|
<li>39 = Activity ended with *FRCFAIL option
|
|
</li>
|
|
</ul>
|
|
</dd>
|
|
<dt><b>40-49</b></dt>
|
|
<dd>Activity was not run due to errors detected by the application.
|
|
<ul>
|
|
<li>40 = Activity not run for security reasons
|
|
</li>
|
|
</ul>
|
|
</dd>
|
|
<dt><b>90-99</b></dt>
|
|
<dd>Activity was not run because conditions or schedules were not met.
|
|
<ul>
|
|
<li>95 = Scheduled start time expired
|
|
</li>
|
|
<li>99 = Conditions cannot be met
|
|
</li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
</dd>
|
|
</dl>
|
|
<p>The possible condition mode values are:
|
|
</p>
|
|
<p>This element indicates which systems the conditioning activity must have completed on before this activity can be performed.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*ALLNODES</u></b></dt>
|
|
<dd>The conditioning activity specified must complete on all nodes before this activity can run.
|
|
</dd>
|
|
<dt><b>*SAMENODE</b></dt>
|
|
<dd>When the conditioning activity specified completes for a given node, the activity specified on the ACTIVITY parameter may run for that same node even though the conditioning activity specified may not have completed on all other nodes. In the case where this activity lists a node not in the conditioning activity, this activity may run for that node; the condition is ignored.
|
|
</dd>
|
|
</dl>
|
|
<p>The possible value is:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>There are no conditions for this activity.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDCMDCRQA.STRTIME"></a>
|
|
<h3>Activity start time (STRTIME)</h3>
|
|
<p>Specifies the date and time when this activity can be started on the central site system. The current date and time values and next date values are determined when the change request is submitted.
|
|
</p>
|
|
<p>The possible start after time values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*CURRENT</u></b></dt>
|
|
<dd>This activity can start any time on or after the time when the change request is submitted.
|
|
</dd>
|
|
<dt><b><i>start-after-time</i></b></dt>
|
|
<dd>Specify the time when this activity can start. The time can be entered as 4 or 6 digits (hhmm or hhmmss), where hh = hours, mm = minutes, and ss = seconds. Seconds are optional. The time can be specified with or without a time separator such as a colon (:). With a time separator, specify a string of 5 or 8 digits (hh:mm or hh:mm:ss).
|
|
</dd>
|
|
</dl>
|
|
<p>The possible start after date values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*CURRENT</u></b></dt>
|
|
<dd>This activity can start on or after the date on which the change request is submitted.
|
|
</dd>
|
|
<dt><b>*NEXT</b></dt>
|
|
<dd>The activity can start on any date after the date the change request is submitted.
|
|
</dd>
|
|
<dt><b><i>start-after-date</i></b></dt>
|
|
<dd>Specify the date after this activity can start. The date must be specified in the job date format.
|
|
</dd>
|
|
</dl>
|
|
<p>The possible start before time values are:
|
|
</p>
|
|
<p>This element is ignored if the start before date is *ANY.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*ANY</u></b></dt>
|
|
<dd>The activity can start at any time on or before the start before date.
|
|
</dd>
|
|
<dt><b>*CURRENT</b></dt>
|
|
<dd>The activity must start before the time at which the change request was submitted on the date specified on the start before date element.
|
|
</dd>
|
|
<dt><b><i>start-before-time</i></b></dt>
|
|
<dd>Specify the time before which the activity must start. If the activity cannot be started before this time, it never starts. The time can be entered as 4 or 6 digits (hhmm or hhmmss) where hh = hours, mm = minutes, and ss = seconds. Seconds are optional. The time can be specified with or without a time separator such as a colon (:). With a time separator, specify a string of 5 or 8 digits (hh:mm or hh:mm:ss).
|
|
</dd>
|
|
</dl>
|
|
<p>The possible start before date values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*ANY</u></b></dt>
|
|
<dd>The activity can start at any time after the start after time and the start after date.
|
|
</dd>
|
|
<dt><b>*CURRENT</b></dt>
|
|
<dd>The activity must start on the date the change request is submitted.
|
|
</dd>
|
|
<dt><b>*NEXT</b></dt>
|
|
<dd>The activity must start by the day after the date the change request is submitted.
|
|
</dd>
|
|
<dt><b><i>start-before-date</i></b></dt>
|
|
<dd>Specify the date before the activity must start. If the activity is not started by this date, it never starts. The date must be specified in the job date format.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDCMDCRQA.HOLD"></a>
|
|
<h3>Hold activity (HOLD)</h3>
|
|
<p>Specifies that the activity be held when the change request is submitted.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NO</u></b></dt>
|
|
<dd>The activity is not held. It runs when all conditions are met at the start time.
|
|
</dd>
|
|
<dt><b>*YES</b></dt>
|
|
<dd>The activity is held when the change request is submitted. It must be released by you before it runs.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<hr size="2" width="100%">
|
|
<div><h3><a name="ADDCMDCRQA.COMMAND.EXAMPLES">Examples</a> </h3>
|
|
<p><b>Example 1: Adding an Activity</b>
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
ADDCMDCRQA CRQD(MYLIB/CR1) ACTIVITY(ACT01) CMD(STRSBS QCMN)
|
|
</pre>
|
|
</p>
|
|
<p>This example shows how activity ACT01 is added to change request description CR1 in library MYLIB to start the QCMN subsystem on the central site system. The activity runs as soon as the change request is submitted.
|
|
</p>
|
|
<p><b>Example 2: Adding an Activity for a Node list</b>
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
ADDCMDCRQA CRQD(MYLIB/CR2) ACTIVITY(ACT01)
|
|
CMD(STRSBS QSNADS) NODL(MYLIB/STORES)
|
|
CPNAME(*NONE) RTNSPLF(*FAIL)
|
|
</pre>
|
|
</p>
|
|
<p>This example shows how activity ACT01 starts the subsystem QSNADS on the systems identified in the STORES node list in the library MYLIB. The example also asks for the spooled file to be returned to the central site system if the command fails.
|
|
</p>
|
|
<p><b>Example 3: Adding an Activity for Two Systems</b>
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
ADDCMDCRQA CRQD(MYLIB/CR3) ACTIVITY(ACT01)
|
|
CMD(PRODLIB/RUNREPORTS)
|
|
CPNAME((STORENET STOREA) (STORENET STOREB))
|
|
USRPRF(REPORTOPER) PASSWORD(OPERPASS)
|
|
ENCODE(*YES)
|
|
</pre>
|
|
</p>
|
|
<p>This example shows how activity ACT01 runs the detail reports for STOREA and STOREB in the STORENET network. The report runs under the REPORTOPER user profile on the managed systems. Because the user profile and a password are supplied, the request will be encoded when sent to the managed system.
|
|
</p>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<hr size="2" width="100%">
|
|
<div><h3><a name="ADDCMDCRQA.ERROR.MESSAGES">Error messages</a> </h3>
|
|
<p>None
|
|
</p>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDCMDCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
</body>
|
|
</html>
|