friedkiwi/ibm-information-center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
14ed2849c6
ibm-information-center/dist/eclipse/plugins/i5OS.ic.cl_5.4.0.1/sndptf.htm

744 lines
27 KiB
HTML
Raw Normal View History

Add readme and dist folders
2024-04-02 14:02:31 +00:00
<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head><META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Send Program Temporary Fix (SNDPTF)</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="SNDPTF.Top_Of_Page"></a>
<h2>Send Program Temporary Fix (SNDPTF)</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="#SNDPTF.PARAMETERS.TABLE">Parameters</a><br>
<a href="#SNDPTF.COMMAND.EXAMPLES">Examples</a><br>
<a href="#SNDPTF.ERROR.MESSAGES">Error messages</a></td>
</tr>
</table>
<div> <a name="SNDPTF"></a>
<p>The Send Program Temporary Fix (SNDPTF) command sends a specific Program Temporary Fix (PTF) and accompanying requisites, or a list of PTFs to a specific requester or list of service requesters. Cover letters can also be sent if they are available.
</p>
<p>When using the SNDPTF command, you can request that the PTFs be applied on the service requester when the PTFs arrive on the service requester. When requesting that the PTFs be applied, you can also request an IPL of the service requester's system. The apply PTF and IPL can be scheduled to occur at a later date.
</p>
<p><b>Notes:</b>
</p>
<ol>
<li>A change request is automatically submitted that can be viewed to determine the status of this command. You can use the Work with Submitted Change Request (WRKSBMCRQ) command to monitor the status.
</li>
<li>A maximum of 300 PTFs can be specified.
</li>
</ol>
<p><b>Restrictions:</b>
</p>
<ol>
<li>The apply and IPL functions of this command are only supported when the service requester has the Managed System Services licensed program installed.
</li>
<li>A PTF save file must exist and be released in order to be sent another system.
</li>
<li>PTFs that are not marked as delayed are applied immediately. PTFs marked as delayed are scheduled to be applied at the next IPL.
</li>
<li>PTFs marked as delayed can only be applied permanently if they have been previously applied temporarily. Notice that an IPL would have been required to apply them since they are delayed.
</li>
<li>If a NODL value is specified, the node list must contain only entries that have address types equal to *SNA.
</li>
<li>The product, option, and release of the PTF must be supported using the Work with Supported Products (WRKSPTPRD) command.
</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>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div>
<h3><a name="SNDPTF.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="4"><a href="#SNDPTF.PTFID"><b>PTFID</b></a></td>
<td valign="top">PTF description</td>
<td valign="top">Values (up to 300 repetitions): <i>Element list</i></td>
<td valign="top" rowspan="4">Required, Positional 1</td>
</tr>
<tr>
<td valign="top">Element 1: PTF identifier</td>
<td valign="top">
<i>Character value</i></td>
</tr>
<tr>
<td valign="top">Element 2: Product</td>
<td valign="top">
<i>Character value</i>, <b><u>*SPT</u></b></td>
</tr>
<tr>
<td valign="top">Element 3: Release level</td>
<td valign="top">
<i>Character value</i>, <b><u>*ONLY</u></b></td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#SNDPTF.DESTSRVRQS"><b>DESTSRVRQS</b></a></td>
<td valign="top">Destination service requester</td>
<td valign="top">Single values: *ALL, <b><u>*SELECT</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>, *NETATR</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="#SNDPTF.MAXDST"><b>MAXDST</b></a></td>
<td valign="top">Maximum distribution</td>
<td valign="top">1-5000, *SRVRQS, *SRVPVDA, <b><u>*NOMAX</u></b></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#SNDPTF.SNDRQT"><b>SNDRQT</b></a></td>
<td valign="top">Send requisites</td>
<td valign="top"><b><u>*YES</u></b>, *NO</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#SNDPTF.CHECK"><b>CHECK</b></a></td>
<td valign="top">Check service requesters</td>
<td valign="top"><b><u>*YES</u></b>, *NO</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#SNDPTF.PTFPART"><b>PTFPART</b></a></td>
<td valign="top">PTF parts</td>
<td valign="top"><b><u>*ALL</u></b>, *PTF, *CVRLTR</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#SNDPTF.APY"><b>APY</b></a></td>
<td valign="top">Extent of change</td>
<td valign="top"><b><u>*NONE</u></b>, *TEMP, *PERM</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#SNDPTF.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" rowspan="3"><a href="#SNDPTF.NODL"><b>NODL</b></a></td>
<td valign="top">Node list name</td>
<td valign="top"><i>Qualified object name</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Qualifier 1: Node list name</td>
<td valign="top"><i>Name</i>, <b><u>*NONE</u></b></td>
</tr><tr>
<td valign="top">Qualifier 2: Library</td>
<td valign="top"><i>Name</i>, *LIBL, *CURLIB</td>
</tr><tr>
<td valign="top" rowspan="5"><a href="#SNDPTF.RMTAPYTIME"><b>RMTAPYTIME</b></a></td>
<td valign="top">Remote apply time</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="#SNDPTF.IPL"><b>IPL</b></a></td>
<td valign="top">IPL remote system</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="#SNDPTF.RMTIPLTIME"><b>RMTIPLTIME</b></a></td>
<td valign="top">Remote IPL time</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="#SNDPTF.PWRDWNOPT"><b>PWRDWNOPT</b></a></td>
<td valign="top">Power down option</td>
<td valign="top"><b><u>*CNTRLD</u></b>, *IMMED</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#SNDPTF.PWRDWNDLY"><b>PWRDWNDLY</b></a></td>
<td valign="top">Power down delay</td>
<td valign="top">1-65535, <b><u>3600</u></b></td>
<td valign="top">Optional</td>
</tr>
</table>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
</div>
<div> <a name="SNDPTF.PTFID"></a>
<h3>PTF description (PTFID)</h3>
<p>Specifies the PTF numbers for the PTFs that are to be sent. The following special PTFs can also be distributed:
</p>
<dl>
<dt><b>SF97vrm or nnn</b></dt>
<dd>PTF summary package
</dd>
<dt><b>MF98vrm or nnn</b></dt>
<dd>Hardware service planning tips
</dd>
<dt><b>SF98vrm or nnn</b></dt>
<dd>Software service planning tips
</dd>
</dl>
<p>
<pre>
n is the PTF sequence number
v is the version for the package requested
r is the release for the package requested
m is the modification level
for the package requested
</pre>
</p>
<p>The possible PTF identifier values are:
</p>
<dl>
<dt><b><i>PTF-identifier</i></b></dt>
<dd>Specify the 7-character identifier (ID) of the PTF that is to be sent.
</dd>
</dl>
<p>The possible product identifier values are:
</p>
<dl>
<dt><b><u>*SPT</u></b></dt>
<dd>The PTF identifier is unique to only one supported product.
</dd>
<dt><b><i>product-id</i></b></dt>
<dd>Specify the product ID of the PTF that is to be sent. The product must be specified when PTF identifiers are not unique across products.
</dd>
</dl>
<p>The possible release level of product values are:
</p>
<dl>
<dt><b><u>*ONLY</u></b></dt>
<dd>The PTF identifier is unique to only one release level of the product.
</dd>
<dt><b><i>release (VxRxMx)</i></b></dt>
<dd>Specify the version, release, and modification level of the PTF being sent. The release level must be specified when the PTF identifiers are not unique across products. The format is VxRxMx.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="SNDPTF.DESTSRVRQS"></a>
<h3>Destination service requester (DESTSRVRQS)</h3>
<p>Specifies the service requester system where this PTF function is performed. A single service requester or a list of service requesters can be specified.
</p>
<p>The possible network identifier values are:
</p>
<dl>
<dt><b><u>*SELECT</u></b></dt>
<dd>Shows a list of service requesters. From the list, you can select one or more service requesters. *SELECT is not valid when the command is used in a batch environment.
</dd>
<dt><b>*ALL</b></dt>
<dd>Specifies that this PTF function should occur on all of the service requesters that are defined for this service provider.
</dd>
<dt><b>*NONE</b></dt>
<dd>The service requesters are identified in a node list object.
</dd>
<dt><b>*NETATR</b></dt>
<dd>The remote network identifier of the service requester is the same as the network identifier of this system.
</dd>
<dt><b><i>remote-network-identifier</i></b></dt>
<dd>Specify the remote network identifier of the service requester.
</dd>
</dl>
<p>The possible control point value is:
</p>
<p>This element is not valid when the network identifier is *ALL, *SELECT, or *NONE.
</p>
<dl>
<dt><b><i>remote-control-point</i></b></dt>
<dd>Specify the remote control point name of the service requester.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="SNDPTF.MAXDST"></a>
<h3>Maximum distribution (MAXDST)</h3>
<p>Specifies the maximum number of kilobytes that can be sent to each service requester.
</p>
<p>The possible values are:
</p>
<dl>
<dt><b><u>*NOMAX</u></b></dt>
<dd>Sends any number of kilobytes.
</dd>
<dt><b>*SRVRQS</b></dt>
<dd>The number of kilobytes that are specified for each service requester in the service requester entry information is used. Use the Work with Service Requesters (WRKSRVRQS) command to display the current value.
</dd>
<dt><b>*SRVPVDA</b></dt>
<dd>The number of kilobytes specified on the maximum distribution service provider attribute is used. Use the Display Service Provider Attribute (DSPSRVPVDA) command to determine the current value.
</dd>
<dt><b><i>maximum-number-of-kilobytes</i></b></dt>
<dd>Specify the maximum number of kilobytes that can be distributed. Specify a value ranging from 1 through 5000 KB.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="SNDPTF.SNDRQT"></a>
<h3>Send requisites (SNDRQT)</h3>
<p>Specifies if requisite PTFs should be added to the list. Requisites includes prerequisite and corequisite PTFs.
</p>
<p>The possible values are:
</p>
<dl>
<dt><b><u>*YES</u></b></dt>
<dd>The PTF and all of its requisites are sent.
</dd>
<dt><b>*NO</b></dt>
<dd>The specific PTF or list of PTFs are sent. No requisites are sent.
<p><b>Note:</b> When using SNDRQT(*NO) APY(*TEMP) or SNDRQT(*NO) APY(*PERM) all requisite PTFs must be applied on the service requester. The PTFs are applied in the order listed on this command.
</p>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="SNDPTF.CHECK"></a>
<h3>Check service requesters (CHECK)</h3>
<p>Specifies that each service requester is checked to determine its unique set of required PTFs.
</p>
<p>The possible values are:
</p>
<dl>
<dt><b><u>*YES</u></b></dt>
<dd>Each service requester is checked to determine the required set of PTFs.
</dd>
<dt><b>*NO</b></dt>
<dd>The service requesters are not checked to determine whether the PTFs are required. All PTFs are sent to all specified service requesters.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="SNDPTF.PTFPART"></a>
<h3>PTF parts (PTFPART)</h3>
<p>Specifies whether PTFs and cover letters should be sent.
</p>
<p>The possible values are:
</p>
<dl>
<dt><b><u>*ALL</u></b></dt>
<dd>Sends the PTF and its associated cover letter. If a cover letter is not found for a PTF, the cover letter is not sent.
</dd>
<dt><b>*PTF</b></dt>
<dd>Sends only the PTF.
</dd>
<dt><b>*CVRLTR</b></dt>
<dd>Sends only the cover letter.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="SNDPTF.APY"></a>
<h3>Extent of change (APY)</h3>
<p>Specifies the extent of change when the PTFs are applied. The apply occurs when all the PTFs have been successfully received by the service requester.
</p>
<p>The possible values are:
</p>
<dl>
<dt><b><u>*NONE</u></b></dt>
<dd>Do not apply PTFs on the service requester's system.
</dd>
<dt><b>*TEMP</b></dt>
<dd>Apply the PTFs temporarily on the service requester's system.
</dd>
<dt><b>*PERM</b></dt>
<dd>Apply the PTFs permanently on the service requester's system.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="SNDPTF.DLYAPY"></a>
<h3>Delayed PTF apply (DLYAPY)</h3>
<p>Specifies how PTFs are applied. Apply immediate PTFs at the time the activity runs on a 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 IPL.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="SNDPTF.NODL"></a>
<h3>Node list name (NODL)</h3>
<p>Specifies the node list object name that contains a list of service requesters where this PTF function is to be performed.
</p>
<p>The possible values are:
</p>
<dl>
<dt><b><u>*NONE</u></b></dt>
<dd>The service requesters are identified in the DESTSRVRQS parameter.
</dd>
</dl>
<p>The possible values are:
</p>
<dl>
<dt><b>*LIBL</b></dt>
<dd>Searches all of the libraries in the user and system portions of the job's library list for the node list object.
</dd>
<dt><b>*CURLIB</b></dt>
<dd>Searches for the node list object in the library for the current job.
</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 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="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="SNDPTF.RMTAPYTIME"></a>
<h3>Remote apply time (RMTAPYTIME)</h3>
<p>Specifies the date and time when the apply can occur on the service requester. The current date and time values and next date are determined, when the apply request is processed, based on this system's date and time.
</p>
<p>The possible time zone values are:
</p>
<dl>
<dt><b><u>*LCLSYS</u></b></dt>
<dd>Specifies the remote start time in the time zone of this system.
</dd>
<dt><b>*MGDSYS</b></dt>
<dd>Specifies the remote start time in the time zone of the service requester's system.
</dd>
</dl>
<p>The possible start after time values are:
</p>
<dl>
<dt><b><u>*CURRENT</u></b></dt>
<dd>Starts the apply on the service requester system at any time on or after the apply request is processed on this system.
</dd>
<dt><b><i>start-after-time</i></b></dt>
<dd>Specify the time when the apply can be started on the service requester. The time can be entered as 4 or 6 digits, such as hhmm or hhmmss where hh = hours, mm = minutes, and ss = seconds. Seconds are optional. The time can be specified with or without a separator. With a time separator, specify a string of 5 or 8 digits such as hh:mm:ss.
</dd>
</dl>
<p>The possible start after date values are:
</p>
<dl>
<dt><b><u>*CURRENT</u></b></dt>
<dd>Starts the apply on the service requester system on any date on or after the date the apply request is processed on this system.
</dd>
<dt><b>*NEXT</b></dt>
<dd>Starts the apply on the service requester system on any date after the date the apply request is processed on this system.
</dd>
<dt><b><i>start-after-date</i></b></dt>
<dd>Specify the date when the apply can start on the service requester system. The date must be specified in the job date format.
<p><b>Note:</b>
</p>
<p>The special values *CURRENT and *NEXT cannot be specified for the date and time if the time zone value *MGDSYS is specified.
</p>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="SNDPTF.IPL"></a>
<h3>IPL remote system (IPL)</h3>
<p>Specifies if an IPL of the service requester's system should occur.
</p>
<p>The possible values are:
</p>
<dl>
<dt><b><u>*NO</u></b></dt>
<dd>An IPL of the service requester system should not occur.
</dd>
<dt><b>*YES</b></dt>
<dd>An IPL of the service requester system should occur after all the PTFs are successfully applied on the service requesters system.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="SNDPTF.RMTIPLTIME"></a>
<h3>Remote IPL time (RMTIPLTIME)</h3>
<p>Specifies the date and time when the IPL can occur on the service requester. The current date and time values and next date are determined, when this IPL request is processed on this system, based on this system's date and time.
</p>
<p>The possible time zone values are:
</p>
<dl>
<dt><b><u>*LCLSYS</u></b></dt>
<dd>Specifies the remote start time in the time zone of this system.
</dd>
<dt><b>*MGDSYS</b></dt>
<dd>Specifies the remote start time in the time zone of the service requester's system.
</dd>
</dl>
<p>The possible start after time values are:
</p>
<dl>
<dt><b><u>*CURRENT</u></b></dt>
<dd>Starts the IPL on the service requester system at any time on or after this IPL request is processed on this system.
</dd>
<dt><b><i>start-after-time</i></b></dt>
<dd>Specify the time when this IPL can be started on the service requester. The time can be entered as 4 or 6 digits, such as hhmm or hhmmss where hh = hours, mm = minutes, and ss = seconds. Seconds are optional. The time can be specified with or without a separator. With a time separator, specify a string of 5 or 8 digits such as hh:mm:ss.
</dd>
</dl>
<p>The possible start after date values are:
</p>
<dl>
<dt><b><u>*CURRENT</u></b></dt>
<dd>Starts the IPL on the service requester system on any date on or after the date the IPL request is processed on this system.
</dd>
<dt><b>*NEXT</b></dt>
<dd>Starts the IPL on the service requester system on any date after the date this IPL request is processed on this system.
</dd>
<dt><b><i>start-after-date</i></b></dt>
<dd>Specify the date when the IPL can start on the service requester system. The date must be specified in the job date format.
</dd>
</dl>
<p><b>Note:</b> The special values *CURRENT and *NEXT cannot be specified for the date and time if the time zone value *MGDSYS is specified.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="SNDPTF.PWRDWNOPT"></a>
<h3>Power down option (PWRDWNOPT)</h3>
<p>Specifies how to manage the end of active jobs during the IPL process at the service requester system. This parameter is valid only if IPL(*YES) is specified.
</p>
<dl>
<dt><b><u>*CNTRLD</u></b></dt>
<dd>All jobs end when the specified time in the Power Down Delay (PWRDWDLY) parameter expires. Any current jobs that are running will perform an end of batch processing.
</dd>
<dt><b>*IMMED</b></dt>
<dd>Jobs end immediately.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="SNDPTF.PWRDWNDLY"></a>
<h3>Power down delay (PWRDWNDLY)</h3>
<p>This parameter is valid only if IPL(*YES) and if PWRDWNOPT(*CNTRLD) are specified. Specifies the amount of time in seconds that the system allows a controlled end to be performed. If the end of job routines are not finished in the specified power down delay, any remaining jobs are ended immediately.
</p>
<dl>
<dt><b><u>3600</u></b></dt>
<dd>The amount of time in which to complete a controlled end of processing is limited to 3600 seconds.
</dd>
<dt><b><i>delay-time</i></b></dt>
<dd>Specify the maximum amount of delay time, in seconds, in which a controlled end can be performed. Valid values range from 1 through 65535 (65,535 seconds).
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="SNDPTF.COMMAND.EXAMPLES">Examples</a> </h3>
<p><b>Example 1: Sending a PTF and Requisites</b>
</p>
<p>
<pre>
SNDPTF PTFID((1234567) (1234600)) DESTSRVRQS(*ALL)
MAXDST(*SRVRQS)
</pre>
</p>
<p>This command sends a PTF and requisites to one or more selected service requesters.
</p>
<p><b>Example 2: Sending a PTF to a Specific Service Requester</b>
</p>
<p>
<pre>
SNDPTF PTFID(1234567) DESTSRVRQS(*NETATR CHICAGO1)
SNDRQT(*NO)
</pre>
</p>
<p>This command distributes PTF 1234567 to a service requester with a control point name of CHICAGO1, if the PTF is not already there. The size of the PTF package does not have an effect on the distribution and no requisites are sent with the PTF.
</p>
<p><b>Example 3: Sending a PTF and Its Requisites to Two Service Requesters</b>
</p>
<p>
<pre>
SNDPTF PTFID(1234567)
DESTSRVRQS((*NETATR CHICAGO1) (*NETATR CHICAGO2))
CHECK(*NO)
</pre>
</p>
<p>This command distributes PTF 1234567 and its requisites to two service requesters with control point names of CHICAGO1 and CHICAGO2. The service requesters are not checked before the PTFs are distributed to determine whether PTF 1234567 is already there. If any of the PTFs exist on the service requesters, they are replaced.
</p>
<p><b>Example 4: Selecting One or More Service Requesters as Destination</b>
</p>
<p>
<pre>
SNDPTF PTFID(1234567) DESTSRVRQS(*SELECT)
</pre>
</p>
<p>This command shows a display that allows the user to select one or more service requesters as the destination for PTF 1234567 and its requisites.
</p>
<p><b>Example 5: Sending and Temporarily Applying One PTF</b>
</p>
<p>
<pre>
SNDPTF PTFID(1234567 *SPT *ONLY) DESTSRVRQS(*NETATR CHICAGO1)
SNDRQT(*NO) CHECK(*NO) PTFPART(*PTF) APY(*TEMP)
RMTAPYTIME((*MGDSYS ('10:00:00' '10/31/02'))
IPL(*YES)
RMTIPLTIME((*MGDSYS ('01:00:00' '11/01/02'))
</pre>
</p>
<p>This command sends and temporarily applies one PTF on a specific requester, schedules when the PTF is applied, and schedules the IPL.
</p>
<p>This example loads and applies the specified PTFs at 10:00 a.m. on October 31, 2002 if all the PTFs were received successfully. If the PTFs have been received and applied successfully, the IPL on the remote system starts at 1:00 a.m. on November 1, 2002.
</p>
<p><b>Example 6: Sending and Applying a Permanent PTF</b>
</p>
<p>
<pre>
SNDPTF PTFID(1234567 *SPT *ONLY)
DESTSRVRQS((*NETATR CHICAGO1) (*NETATR CHICAGO2))
PTFPART(*PTF) APY(*PERM)
RMTAPYTIME((*MGDSYS ('10:00:00' '10/31/02'))
IPL(*YES)
RMTIPLTIME((*MGDSYS ('01:00:00' '11/01/02'))
</pre>
</p>
<p>This command sends and permanently applies one PTF to more than one service requester. This schedules the application of the PTF and the IPL of the system. The scheduled time is the time at the location of the service requester or the remote system. The command sends requisites and checks the service requester for the availability of the PTFs.
</p>
<p>This example applies the specified PTFs on the service requester starting at 10:00 a.m. on October 31, 2002, if all the PTFs were received successfully. If the PTFs have been received and applied successfully, the remote system IPL starts at 1:00 a.m. on November 1, 2002.
</p>
<p><b>Example 7: Doing an IPL after Sending and Applying a PTF</b>
</p>
<p>
<pre>
SNDPTF PTFID(1234567 *SPT *ONLY) DESTSRVRQS(*SELECT)
PTFPART(*PTF) APY(*TEMP)
RMTAPYTIME((*MGDSYS (*CURRENT *CURRENT)) IPL(*YES)
RMTIPLTIME((*LCLSYS (*CURENT 12/24/02))
PWRDWNOPT(*CNTRLD) PWRDWNDLY(4800)
</pre>
</p>
<p>This command sends and temporarily applies one PTF to one or more selected service requesters. This command schedules the application of the PTF and the IPL of the system. The scheduled time is the time at the location of the service requester or the remote system. The command sends requisites and checks the service requester or the availability of the PTFs.
</p>
<p>This example applies the specified PTF on the service requester starting at the current time on the current date. If the PTFs were received and applied successfully, the remote system IPL starts at the current time on December 24, 2002. The time specified for the IPL is in the time zone of the local system.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="SNDPTF.ERROR.MESSAGES">Error messages</a> </h3>
<p><b><u>*ESCAPE Messages</u></b>
</p>
<dl>
<dt><b>SMU107F</b></dt>
<dd>Error found processing &amp;1 command.
</dd>
<dt><b>SMU1080</b></dt>
<dd>Cannot specify *SELECT for service requester destination.
</dd>
<dt><b>SMU109C</b></dt>
<dd>Errors detected while processing PTFs.
</dd>
<dt><b>SMU109E</b></dt>
<dd>One or more PTFs could not be sent.
</dd>
<dt><b>SMU109F</b></dt>
<dd>No PTFs sent.
</dd>
</dl>
<p><b><u>*STATUS Messages</u></b>
</p>
<dl>
<dt><b>SMU109A</b></dt>
<dd>Contacting &amp;1.&amp;2 to determine required PTFs.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#SNDPTF.Top_Of_Page">Top</a></td></tr>
</table>
</body>
</html>
Reference in New Issue Copy Permalink