924 lines
34 KiB
HTML
924 lines
34 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 PTF CRQ Activity (ADDPTFCRQA)</title>
|
|
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
|
|
</head>
|
|
<body bgcolor="white">
|
|
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<a name="ADDPTFCRQA.Top_Of_Page"></a>
|
|
<h2>Add PTF CRQ Activity (ADDPTFCRQA)</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="#ADDPTFCRQA.PARAMETERS.TABLE">Parameters</a><br>
|
|
<a href="#ADDPTFCRQA.COMMAND.EXAMPLES">Examples</a><br>
|
|
<a href="#ADDPTFCRQA.ERROR.MESSAGES">Error messages</a></td>
|
|
</tr>
|
|
</table>
|
|
|
|
<div> <a name="ADDPTFCRQA"></a>
|
|
<p>The Add Program Temporary Fix Change Request Activity (ADDPTFCRQA) command adds an activity to a change request description which performs a PTF distribution function.
|
|
</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>The PTF must be for an iSeries product package using the System Manager licensed program. The PTF must be supported using the Work with Supported Product (WRKSPTPRD) command. Software redesigns can be managed for other types of systems by using globally named objects on the Add Object Change Request Activity (ADDOBJCRQA) command or by using Add Change Management Activity (QNSADDCM) API.
|
|
</li>
|
|
<li>A PTF save file must exist and be released in order to be sent to another system.
|
|
</li>
|
|
<li>A PTF can only be retrieved from a single managed system.
|
|
</li>
|
|
<li>If a NODL value is specified, the node list can only contain entries that have a value of *SNA for the address type.
|
|
</li>
|
|
<li>If the destination node does not have IBM SystemView Managed System Services installed, only the send action is available. The activity is considered successful when the PTF is sent, not when it arrives.
|
|
</li>
|
|
<li>If you are distributing a PTF and the distribution queue is set to *SNADS in the Work with Service Requesters (WRKSRVRQS) command, you must have *USE authority to the Send PTF (SNDPTF) command.
|
|
</li>
|
|
<li>If you are distributing a PTF and the distribution queue is set to *SVDS in the Work with Service Requesters (WRKSRVRQS) command, you must have *USE authority to the Copy PTF (CPYPTF) command.
|
|
</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 met before the activity runs.
|
|
</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>
|
|
<li>PTFs that are not marked as delayed are applied immediately or during the next IPL. PTFs marked as delayed are applied during the next IPL.
|
|
</li>
|
|
<li>PTFs marked as delayed can only be applied permanently if they have been previously applied temporarily. Because they are delayed, these PTFs would be applied during the next scheduled IPL.
|
|
</li>
|
|
<li>PTFs are always removed temporarily except Vertical Licensed Internal Code (VLIC) PTFs which are removed permanently.
|
|
</li>
|
|
</ol>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<hr size="2" width="100%">
|
|
|
|
<div>
|
|
<h3><a name="ADDPTFCRQA.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="#ADDPTFCRQA.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="#ADDPTFCRQA.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="#ADDPTFCRQA.ACTION"><b>ACTION</b></a></td>
|
|
<td valign="top">Action</td>
|
|
<td valign="top">*SND, *RTV, *DLT, *APY, *SNDAPY, *RMV</td>
|
|
<td valign="top">Optional, Positional 3</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPTFCRQA.PTFID"><b>PTFID</b></a></td>
|
|
<td valign="top">PTF identifier</td>
|
|
<td valign="top"><i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: PTF</td>
|
|
<td valign="top">
|
|
<i>Character value</i>, *ALL</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Product</td>
|
|
<td valign="top">
|
|
<i>Character value</i>, <b><u>*ONLY</u></b></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Release level</td>
|
|
<td valign="top">
|
|
<i>Character value</i></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPTFCRQA.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="#ADDPTFCRQA.CPNAME"><b>CPNAME</b></a></td>
|
|
<td valign="top">Managed system node names</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><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"><a href="#ADDPTFCRQA.PTFPART"><b>PTFPART</b></a></td>
|
|
<td valign="top">PTF parts</td>
|
|
<td valign="top"><b><u>*PTF</u></b>, *CVRLTR</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPTFCRQA.CVRLTRLNG"><b>CVRLTRLNG</b></a></td>
|
|
<td valign="top">Cover letter language</td>
|
|
<td valign="top">2900-2999, <b><u>*SRVRQS</u></b></td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPTFCRQA.APY"><b>APY</b></a></td>
|
|
<td valign="top">Extent of change</td>
|
|
<td valign="top"><b><u>*TEMP</u></b>, *PERM, *LODONLY</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPTFCRQA.DLYAPY"><b>DLYAPY</b></a></td>
|
|
<td valign="top">Delayed PTF apply</td>
|
|
<td valign="top"><b><u>*NO</u></b>, *YES</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPTFCRQA.DLYRMV"><b>DLYRMV</b></a></td>
|
|
<td valign="top">Delayed PTF remove</td>
|
|
<td valign="top"><b><u>*NO</u></b>, *YES</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="5"><a href="#ADDPTFCRQA.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="5">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"><a href="#ADDPTFCRQA.TEXT"><b>TEXT</b></a></td>
|
|
<td valign="top">Text 'description'</td>
|
|
<td valign="top"><i>Character value</i>, <b><u>*GEN</u></b>, *BLANK</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="5"><a href="#ADDPTFCRQA.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="#ADDPTFCRQA.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="#ADDPTFCRQA.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="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
</div>
|
|
<div> <a name="ADDPTFCRQA.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 the user and 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="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.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 identifier.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.ACTION"></a>
|
|
<h3>Action (ACTION)</h3>
|
|
<p>Specifies the function to be performed on the PTF.
|
|
</p>
|
|
<p>The possible values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b>*SND</b></dt>
|
|
<dd>Send the PTF to the specified managed system. The PTF is not loaded as part of this activity.
|
|
</dd>
|
|
<dt><b>*RTV</b></dt>
|
|
<dd>Retrieve the specified PTF from the specified managed system.
|
|
</dd>
|
|
<dt><b>*DLT</b></dt>
|
|
<dd>Deletes the PTF save file and cover letter on the specified managed system.
|
|
</dd>
|
|
<dt><b>*APY</b></dt>
|
|
<dd>Apply the PTF on the specified system. All requisite PTFs must be applied. A PTF may set in loaded ("Not applied") status. If the PTF is not previously loaded, then the PTF must be loaded before it is applied. To apply all corequisite PTFs, set the status to "loaded". Request to apply one PTF and all corresponding corequisites will be applied.
|
|
</dd>
|
|
<dt><b>*SNDAPY</b></dt>
|
|
<dd>Send, load, and apply the PTF on the specified system. All requisite PTFs must have already been applied. To apply the current PTF and corresponding corequisite PTFs, set the status to "loaded" ("Not applied"). When applying one PTF, that PTF and all corresponding corequisite PTFs are applied.
|
|
</dd>
|
|
<dt><b>*RMV</b></dt>
|
|
<dd>Temporarily remove the PTF on the specified system.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.PTFID"></a>
|
|
<h3>PTF (PTFID)</h3>
|
|
<p>Specifies the PTF that is to be distributed.
|
|
</p>
|
|
<p>The possible values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>PTF-identifier</i></b></dt>
|
|
<dd>Specify a 7-character PTF identifier.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All PTFs for the specified product. It can only be specified when applying or removing PTFs. A product must be specified.
|
|
</dd>
|
|
</dl>
|
|
<p>The possible product identifier values are:
|
|
</p>
|
|
<p>This is the product identifier of the product to which the PTF is associated.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*ONLY</u></b></dt>
|
|
<dd>The PTF identifier specified is associated with only one supported product.
|
|
</dd>
|
|
<dt><b><i>product-ID</i></b></dt>
|
|
<dd>Specify the product to which the PTF is associated. The product must be specified when PTF identifiers are not unique across products.
|
|
</dd>
|
|
</dl>
|
|
<p>The possible release level of the product value is:
|
|
</p>
|
|
<p>This element shows the release level of the product.
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>release(VxRxMx)</i></b></dt>
|
|
<dd>Specify the release level of the product to which the PTF is associated. The format is VxRxMx. The release must be specified when PTF identifiers are not unique across product releases.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.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 also specified.
|
|
</p>
|
|
<p>The possible value is:
|
|
</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 library values are:
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*LIBL</u></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 value is:
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>node-list-name</i></b></dt>
|
|
<dd>Specify the node list object name which contains the list of systems where the PTF function is to be performed.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.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 a node list (NODL) parameter is specified.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>The systems on which this activity is performed are not identified individually. A node list must be specified.
|
|
</dd>
|
|
</dl>
|
|
<p>The possible values are:
|
|
</p>
|
|
<dl>
|
|
<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 name 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="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.PTFPART"></a>
|
|
<h3>PTF parts (PTFPART)</h3>
|
|
<p>Specifies whether the PTFs or cover letters should be sent, retrieved, or deleted.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*PTF</u></b></dt>
|
|
<dd>Only the PTF should be handled.
|
|
</dd>
|
|
<dt><b>*CVRLTR</b></dt>
|
|
<dd>Only the PTF cover letter is handled. *CVRLTR can only be used with the *RTV and *SND actions.
|
|
</dd>
|
|
</dl>
|
|
<p>If the delete action is specified, then both the PTF and the cover letter are always deleted.
|
|
</p>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.CVRLTRLNG"></a>
|
|
<h3>Cover letter language (CVRLTRLNG)</h3>
|
|
<p>Specifies the language of the cover letter to be sent with the PTF.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*SRVRQS</u></b></dt>
|
|
<dd>The cover letter language specified in the service requester entry for each node determines which cover letter that particular node is sent. If a service requester entry is not present or a language is not specified, the default language 2924 is used. If the language specified is not found, then 2924 is sent except when 2926 is requested in which case 2950 is sent.
|
|
</dd>
|
|
<dt><b><i>cover-letter-language-ID</i></b></dt>
|
|
<dd>Specify the 4-character language identifier of the cover letter to be sent or retrieved.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.APY"></a>
|
|
<h3>Extent of change (APY)</h3>
|
|
<p>Specifies the extent of change when the PTF is applied.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*TEMP</u></b></dt>
|
|
<dd>The PTF is applied temporarily.
|
|
</dd>
|
|
<dt><b>*PERM</b></dt>
|
|
<dd>The PTF is applied permanently.
|
|
</dd>
|
|
<dt><b>*LODONLY</b></dt>
|
|
<dd>The PTF is only loaded. This is useful for PTFs which are part of a corequisite group where all PTFs are applied, removed, or permanently applied as a group and the "loaded" ("Not applied") status is the requisite to perform those functions.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.DLYAPY"></a>
|
|
<h3>Delayed PTF apply (DLYAPY)</h3>
|
|
<p>Specifies how PTFs are applied. Apply immediate PTFs one at a time while the activity runs on the specified system or later during the next IPL.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NO</u></b></dt>
|
|
<dd>Applies an immediate PTF at the time the activity runs. If the PTF is marked delayed, it is not applied until the next unattended IPL.
|
|
</dd>
|
|
<dt><b>*YES</b></dt>
|
|
<dd>Applies both immediate or delayed PTFs during the next unattended IPL.
|
|
</dd>
|
|
<dt><b></b></dt>
|
|
<dd>
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.DLYRMV"></a>
|
|
<h3>Delayed PTF remove (DLYRMV)</h3>
|
|
<p>Specifies how a PTF is removed. Remove a PTF at the time the activity is specified on the system or later during the next IPL.
|
|
</p>
|
|
<p>The possible single value is:
|
|
</p>
|
|
<dl>
|
|
<dt><b>*NO</b></dt>
|
|
<dd>Removes a PTF at the time an activity runs.
|
|
</dd>
|
|
<dt><b>*Yes</b></dt>
|
|
<dd>Removes during the next time the unattended IPL.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.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 central site system on the date specified in element 2.
|
|
</dd>
|
|
<dt><b><i>start-after-time</i></b></dt>
|
|
<dd>Specify the time 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><b>Notes</b>
|
|
</p>
|
|
<ol>
|
|
<li>The special values *CURRENT and *NEXT are specified for the date and the time if the time zone value *MGDSYS is specified.
|
|
</li>
|
|
<li>This parameter can only be specified if *APY, *RMV, or *SNDAPY actions are specified.
|
|
</li>
|
|
</ol>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.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 activity selected.
|
|
</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="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.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 which 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 single value is:
|
|
</p>
|
|
<dl>
|
|
<dt><b>*NONE</b></dt>
|
|
<dd>There are no conditions for this activity.
|
|
</dd>
|
|
</dl>
|
|
<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 the 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*-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 values are:
|
|
</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 values are:
|
|
</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 is 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:
|
|
<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 runs.
|
|
</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 for all other nodes. In the case where this activity lists a node not in the conditioning activity, this activity can run for that node; the condition is ignored.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.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 (:). Without a time separator, specify a string of 4 or 6 digits (hhmm or hhmmss). 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 when the change request is submitted.
|
|
</dd>
|
|
<dt><b>*NEXT</b></dt>
|
|
<dd>The activity can start on any date after the date when 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 when the change request was submitted on the date specified on the start before date element. This value cannot be specified if the start before date is *CURRENT.
|
|
</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 cannot be 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="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPTFCRQA.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 and the start time are met.
|
|
</dd>
|
|
<dt><b>*YES</b></dt>
|
|
<dd>The activity is held for all nodes 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="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<hr size="2" width="100%">
|
|
<div><h3><a name="ADDPTFCRQA.COMMAND.EXAMPLES">Examples</a> </h3>
|
|
<p><b>Example 1: Adding an Activity to Permanently Apply a PTF</b>
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
ADDPTFCRQA CRQD(MYLIB/CR1) ACTIVITY(ACT01) ACTION(*APY)
|
|
APY(*PERM) PTFID(SF12345)
|
|
CPNAME((*NETATR SYS1))
|
|
</pre>
|
|
</p>
|
|
<p>This command adds an activity to permanently apply PTF SF12345 on system SYS1.
|
|
</p>
|
|
<p><b>Example 2: Add an Activity to Send a PTF Cover Letter</b>
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
ADDPTFCRQA CRQD(MYLIB/CR2) ACTIVITY(ACT03) ACTION(*SND)
|
|
PTFID(SF89345) PTFPART(*CVRLTR) CVRLTRLNG(2950)
|
|
NODL(NETLIB/EUROPESYS)
|
|
</pre>
|
|
</p>
|
|
<p>This command adds an activity to send a PTF cover letter to all systems in Europe that are identified in the EUROPESYS node list.
|
|
</p>
|
|
<p><b>Example 3: Adding an Activity to Temporarily Apply a PTF</b>
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
ADDPTFCRQA CRQD(MYLIB/CR3) ACTIVITY(ACT01) ACTION(*SND)
|
|
PTFID(SF99911) CPNAME((NET1 SYSX))
|
|
ADDPTFCRQA CRQD(MYLIB/CR3) ACTIVITY(ACT02) ACTION(*APY)
|
|
APY(*TEMP) PTFID(SF99911)
|
|
RMTSTRTIME(*MGDSYS ('02:00:00' '12/12/02'))
|
|
CPNAME((NET1 SYSX))
|
|
</pre>
|
|
</p>
|
|
<p>This command adds activities to send a PTF and apply it temporarily at 2:00 a.m. on December 12th, 2002, on a system encountering a problem.
|
|
</p>
|
|
<p><b>Example 4: Adding an Activity to Load a PTF</b>
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
ADDPTFCRQA CRQD(MYLIB/CR4) ACTIVITY(ACT01) ACTION(*APY)
|
|
PTFID(SF89555) CPNAME(*NETATR SYS4) APY(*LODONLY)
|
|
</pre>
|
|
</p>
|
|
<p>This command adds an activity to only load the PTF SF89555, which is part of a corequisite PTF group, on system SYS4.
|
|
</p>
|
|
<p><b>Example 5: Adding an Activity to Send and Permanently apply a PTF in Delayed Mode</b>
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
ADDPTFCRQA CRQD(MYLIB/CR5) ACTIVITY(ACT01) ACTION(*SNDAPY)
|
|
PTFID(SF91388) CPNAME(*NETATR SYS5)
|
|
APY(*PERM) DLYAPY(*YES)
|
|
</pre>
|
|
</p>
|
|
<p>This command adds an activity to send and permanently apply PTF SF91388 during the next unattended IPL.
|
|
</p>
|
|
<p><b>Example 6: Adding an Activity to Load and Apply an Individual PTF and the Corequisite Group</b>
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
ADDPTFCRQA CRQD(MYLIB/CR6) ACTIVITY(ACT01) ACTION(*SNDAPY)
|
|
PTFID(SF97001) CPNAME(*NETATR SYS6)
|
|
APY(*LODONLY)
|
|
ADDPTFCRQA CRQD(MYLIB/CR6) ACTIVITY(ACT02) ACTION(*SNDAPY)
|
|
PTFID(SF97002) CPNAME(*NETATR SYS6)
|
|
APY(*LODONLY)
|
|
ADDPTFCRQA CRQD(MYLIB/CR6) ACTIVITY(ACT03) ACTION(*SNDAPY)
|
|
PTFID(SF97003) CPNAME(*NETATR SYS6)
|
|
APY(*TEMP)
|
|
</pre>
|
|
</p>
|
|
<p>In this example, there are three PTFs: SF97001, SF97002, and SF97003. SF97001 has corequisite SF97002, and SF97002 has corequisite SF97003. To apply one of them, you must apply all of them as a group to have the product function correctly. Therefore, you need to load the PTFs first, then when you request to apply only one of them, that PTF and its associated corequisites will all be applied.
|
|
</p>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<hr size="2" width="100%">
|
|
<div><h3><a name="ADDPTFCRQA.ERROR.MESSAGES">Error messages</a> </h3>
|
|
<p>None
|
|
</p>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPTFCRQA.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
</body>
|
|
</html>
|