APYRMTPTF (Apply Remote Program Temporary Fix)

Note: To use this command, have the 5722-SM1 (System Manager for iSeries) licensed program installed.

APYRMTPTF Command syntax diagram

 

Purpose

The Apply Remote Program Temporary Fix (APYRMTPTF) command allows a service provider to remotely apply PTFs on the service requester's system. When using the APYRMTPTF command, you can request an IPL of the service requester's system. The apply PTF and IPL can be scheduled to occur at a later date and time.

Note: A change request is automatically submitted that can be viewed to determine the status of this command. Use the Work with Submitted Change Request (WRKSBMCRQ) command to monitor the status.

 

Restrictions

  1. The apply and IPL functions of this command are only supported when the service requester has the Managed System Services licensed program installed.

  2. PTFs that are not marked as delayed are applied immediately. PTFs marked as delayed are scheduled to be applied at the next IPL.

  3. 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.

  4. Prerequisite PTFs of the same product must already be loaded on the service requester. However, prerequisite PTFs of another product must already be applied on the service requester. Corequisite PTFs of the same product and same option must already be loaded on the service requester. However, corequisite PTFs of another product or another option must already be applied on the service requester.

  5. If a NODL value is specified, the node list can only contain entries that have a value of *SNA for the address type.

 

Required Parameters

PTFID
Specifies the PTF that is to be applied. A maximum of 300 PTF identifiers can be specified.

Element 1: PTF Identifier

ptf-identifier: Specify a 7-character PTF identifier.

*ALL: Applies all PTFs for the specified product.

Element 2: Product Identifier

*ONLY: Specifies that the PTF identifier is associated with only one product.

product-id: Specify the product of the PTF. The product must be specified when PTF identifiers are not unique across products or the PTF identifier is *ALL.

Element 3: Release Level of Product

release(VxRxMx): Specify the release level of the product. The format is VxRxMx.

DESTSRVRQS
Specifies the service requester where this PTF function is to be performed. A single service requester or a list of service requesters can be specified.

Element 1: Network Identifier

*SELECT: 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.

*ALL: Specifies that this PTF function should occur on all of the service requesters that are defined for this service provider.

*NONE: The service requesters are identified in a node list object.

*NETATR: The remote network identifier of the service requester is the same as the remote network identifier of this system.

remote-network-identifier: Specify the remote network identifier of the service requester.

Element 2: Control Point

This element is not valid when the network identifier is *ALL, *SELECT, or *NONE.

remote-control-point: Specify the remote control point name of the service requester.

 

Optional Parameters

NODL
Specifies the node list object name that contains a list of service requesters where this PTF function is to be performed.

*NONE: The service requesters are identified in the DESTSRVRQS parameter.

The possible library values are:

*LIBL: Searches all of the libraries in the user and system portions of the job's library list for the node list object.

*CURLIB: Searches for the node list object in the library for the current job.

library-name: Specify the name of the library to be searched.

node-list-name: Specify the node list name which contains the list of service requesters where this PTF function is to be performed.

APY
Specifies the extent of the change when the PTFs are applied.

*TEMP: Apply the PTFs temporarily on the service requester.

*PERM: Apply the PTFs permanently on the service requester.

DLYAPY
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.

*NO: 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.

*YES: Applies both immediate or delayed PTFs during the next unattended IPL.

RMTAPYTIME
Specifies the date and time when this PTF function can occur on the service requester. The current date and time values and next date are determined, when this PTF function is processed on this system, based on this system's date and time.

Element 1: Time Zone

*LCLSYS: Specifies the remote start time in the time zone of this system.

*MGDSYS: Specifies the remote start time in the time zone of the service requester.

Element 2: Start After Time

*CURRENT: Starts this PTF function on the service requester system at any time on or after this PTF function request is processed on this system.

start-after-time: Specify the time when this PTF function 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 (hh:mm or hh:mm:ss).

Element 3: Start After Date

*CURRENT: Starts this PTF function on the service requester system on any date on or after the date this PTF function request is processed on this system.

*NEXT: Starts this PTF function on the service requester system on any date after the date this PTF function is processed on this system.

start-after-date: Specify the date when this PTF function can start on the service requester system. The date must be specified in the job date format.

Note: The special values *CURRENT and *NEXT cannot be specified for the date and time when the time zone value *MGDSYS is specified.

IPL
Specifies if an IPL of the service requester's system should occur.

*NO: An IPL of the service requester's system should not occur.

*YES: An IPL of the service requester's system should occur after all of the PTFs listed on the command are successfully applied on the service requester.

RMTIPLTIME
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.

Element 1: Time Zone

*LCLSYS: Specifies the remote start time in the time zone of this system.

*MGDSYS: Specifies the remote start time in the time zone of the service requester's system.

Element 2: Start After Time

*CURRENT: Starts the IPL on the service requester system at any time on or after this IPL request is processed on this system.

start-after-time: Specify the time when the 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 (hh:mm or hh:mm:ss).

Element 3: Start After Date

*CURRENT: Starts the IPL on the service requester system on any date on or after the date the IPL request is processed on this system.

*NEXT: Starts the IPL on the service requester system on any date after the date this IPL request is processed on this system.

start-after-date: Specify the date when the IPL can start on the service requester system. The date must be specified in the job date format.

Note: The special values *CURRENT and *NEXT cannot be specified for the date and time when the time zone value *MGDSYS is specified.

PWRDWNOPT
Specifies how to manage the end of active jobs during IPL process at the service requester system. This parameter is valid only if IPL(*YES) is specified.

*CNTRLD: All jobs end when the specified time in the Power down delay (PWRDWNDLY) parameter expires. Any current jobs that are running will perform an end of batch processing.

*IMMED: Jobs end immediately.

PWRDWNDLY
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.

3600: The amount of time in which to complete a controlled end of processing is limited to 3600 seconds.

delay-time: 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).

Examples for APYRMTPTF

Example 1: Applying a Temporary PTF 

APYRMTPTF PTFID((123456 *ONLY V3R1M0)) DESTSRVRQS(*SELECT)
  NODL(SRVPVDLIB/SRVRQSLIST)

Apply a PTF temporarily on the selected service requesters system.

Example 2: Applying Permanent PTFs 

APYRMTPTF PTFID((*ALL PRODUCT1 V5R2M0))  DESTSRVRQS(*NONE)
  NODL(SRVPVDLIB/SRVRQSLIST)
  APY(*PERM) RMTAPYTIME((*MGDSYS (10:00:00 10/31/02))
  IPL(*YES)
  RMTIPLTIME((*MGDSYS (01:00:00 11/01/02))

Apply all PTFs permanently for a specified product, and schedule when the apply and IPL should occur for all of the service requesters in the node list object.

This example applies the PTFs on the service requesters starting at 10:00 a.m. on October 31, 2002. If the PTFs applied successfully, the IPL on the remote system starts at 1:00 a.m. on November 1, 2002. The times specified are in the time zone of the remote system.

Example 3: Applying a Delayed PTF 

APYRMTPTF PTFID((987654 *ONLY V5R2M0))  DESTSRVRQS(*SELECT)
  NODL(SRVPVDLIB/SRVRQSLIST)
  DLYAPY(*YES) RMTAPYTIME((*MGDSYS (8:00:00 *CURRENT))

Apply a delayed PTF temporarily on the selected service requesters system, and schedule when the apply should occur for all of the service requesters in the node list object.

This example applies the PTFs on the service requester systems starting at 8:00 am on the current date. The time specified is in the time zone of the remote system.

Example 4: Doing an IPL after Applying a PTF 

APYRMTPTF PTFID((*ALL *ONLY V5R2M0))  DESTSRVRQS(*SELECT)
  NODL(SRVPVDLIB/SRVRQSLIST)  IPL(*YES)
  RMTIPLTIME((*LCLSYS (*CURRENT 12/24/02))
  PWRDWNOPT(*CNTRLD) PWRDWNDLY(1800)

Apply all PTFs temporarily for a specified product, and schedule when the IPL should occur for all of the service requesters in the node list object.

This example applies the PTFs on the service requester systems. If the PTFs are applied successfully, the IPL on the remote system starts at the current time on December 24, 2002. The times specified are in the time zone of the locl system.

Example 5: Applying a PTF with two Corequisite PTFs and one Prerequisite PTF 

APYRMTPTF PTFID((SF00001 *ONLY V5R2M0))  DESTSRVRQS(*SELECT)
   RMTAPYTIME(*LCLSYS (*CURRENT *CURRENT)) IPL(*NO)

Apply PTF SF00001. This PTF has two corequisite PTFs and one prerequisite PTF. PTFs SF00002 and SF00003 are corequisite PTFs for PTF SF00001. PTF SF00004 is a prerequisite for PTF SF00001. The system will remove PTFs SF00001, SF00002, SF00003, and SF00004. The system will determine all corequisite PTFs if they were not specified. No IPL will be performed, and this action applies the PTFs on the service requesters. The times specified are in the time zone of the local system.

This example applies the PTFs on the service requesters system starting at 8:00 am on the current date. The time specified is in the time zone of the remote system.

Error messages for APYRMTPTF

*ESCAPE Messages

CPF358A
PTF &1-&2 cannot be applied or removed.