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.

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.

Notes:

1. 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.
2. A maximum of 300 PTFs can be specified.

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. A PTF save file must exist and be released in order to be sent another system.
3. PTFs that are not marked as delayed are applied immediately. PTFs marked as delayed are scheduled to be applied at the next IPL.
4. 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.
5. If a NODL value is specified, the node list must contain only entries that have address types equal to *SNA.
6. The product, option, and release of the PTF must be supported using the Work with Supported Products (WRKSPTPRD) command.
7. 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.
8. 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.

Parameters

Keyword	Description	Choices	Notes
PTFID	PTF description	Values (up to 300 repetitions): Element list	Required, Positional 1
	Element 1: PTF identifier	Character value
	Element 2: Product	Character value, *SPT
	Element 3: Release level	Character value, *ONLY
DESTSRVRQS	Destination service requester	Single values: *ALL, *SELECT, *NONE Other values (up to 50 repetitions): Element list	Optional
	Element 1: Network identifier	Communications name, *NETATR
	Element 2: Control point	Communications name
MAXDST	Maximum distribution	1-5000, *SRVRQS, *SRVPVDA, *NOMAX	Optional
SNDRQT	Send requisites	*YES, *NO	Optional
CHECK	Check service requesters	*YES, *NO	Optional
PTFPART	PTF parts	*ALL, *PTF, *CVRLTR	Optional
APY	Extent of change	*NONE, *TEMP, *PERM	Optional
DLYAPY	Delayed PTF apply	*NO, *YES	Optional
NODL	Node list name	Qualified object name	Optional
	Qualifier 1: Node list name	Name, *NONE
	Qualifier 2: Library	Name, *LIBL, *CURLIB
RMTAPYTIME	Remote apply time	Element list	Optional
	Element 1: Time zone	*LCLSYS, *MGDSYS
	Element 2: Start after	Element list
	Element 1: Time	Time, *CURRENT
	Element 2: Date	Date, *CURRENT, *NEXT
IPL	IPL remote system	*NO, *YES	Optional
RMTIPLTIME	Remote IPL time	Element list	Optional
	Element 1: Time zone	*LCLSYS, *MGDSYS
	Element 2: Start after	Element list
	Element 1: Time	Time, *CURRENT
	Element 2: Date	Date, *CURRENT, *NEXT
PWRDWNOPT	Power down option	*CNTRLD, *IMMED	Optional
PWRDWNDLY	Power down delay	1-65535, 3600	Optional

Top

PTF description (PTFID)

Specifies the PTF numbers for the PTFs that are to be sent. The following special PTFs can also be distributed:

SF97vrm or nnn

PTF summary package

MF98vrm or nnn

Hardware service planning tips

SF98vrm or nnn

Software service planning tips

   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

The possible PTF identifier values are:

PTF-identifier

Specify the 7-character identifier (ID) of the PTF that is to be sent.

The possible product identifier values are:

*SPT

The PTF identifier is unique to only one supported product.

product-id

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.

The possible release level of product values are:

*ONLY

The PTF identifier is unique to only one release level of the product.

release (VxRxMx)

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.

Destination service requester (DESTSRVRQS)

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

The possible network identifier values are:

*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 network identifier of this system.

remote-network-identifier

Specify the remote network identifier of the service requester.

The possible control point value is:

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.

Maximum distribution (MAXDST)

Specifies the maximum number of kilobytes that can be sent to each service requester.

The possible values are:

*NOMAX

Sends any number of kilobytes.

*SRVRQS

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.

*SRVPVDA

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.

maximum-number-of-kilobytes

Specify the maximum number of kilobytes that can be distributed. Specify a value ranging from 1 through 5000 KB.

Send requisites (SNDRQT)

Specifies if requisite PTFs should be added to the list. Requisites includes prerequisite and corequisite PTFs.

The possible values are:

*YES

The PTF and all of its requisites are sent.

*NO

The specific PTF or list of PTFs are sent. No requisites are sent.

Note: 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.

Check service requesters (CHECK)

Specifies that each service requester is checked to determine its unique set of required PTFs.

The possible values are:

*YES

Each service requester is checked to determine the required set of PTFs.

*NO

The service requesters are not checked to determine whether the PTFs are required. All PTFs are sent to all specified service requesters.

PTF parts (PTFPART)

Specifies whether PTFs and cover letters should be sent.

The possible values are:

*ALL

Sends the PTF and its associated cover letter. If a cover letter is not found for a PTF, the cover letter is not sent.

*PTF

Sends only the PTF.

*CVRLTR

Sends only the cover letter.

Extent of change (APY)

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.

The possible values are:

*NONE

Do not apply PTFs on the service requester's system.

*TEMP

Apply the PTFs temporarily on the service requester's system.

*PERM

Apply the PTFs permanently on the service requester's system.

Delayed PTF apply (DLYAPY)

Specifies how PTFs are applied. Apply immediate PTFs at the time the activity runs on a 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 IPL.

Node list name (NODL)

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

The possible values are:

*NONE

The service requesters are identified in the DESTSRVRQS parameter.

The possible 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.

The possible node list name value is:

node-list-name

Specify the node list name which contains the list of systems where the PTF function is to be performed.

Remote apply time (RMTAPYTIME)

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.

The possible time zone values are:

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

The possible start after time values are:

*CURRENT

Starts the apply on the service requester system at any time on or after the apply request is processed on this system.

start-after-time

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.

The possible start after date values are:

*CURRENT

Starts the apply on the service requester system on any date on or after the date the apply request is processed on this system.

*NEXT

Starts the apply on the service requester system on any date after the date the apply request is processed on this system.

start-after-date

Specify the date when the apply 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 if the time zone value *MGDSYS is specified.

IPL remote system (IPL)

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

The possible values are:

*NO

An IPL of the service requester system should not occur.

*YES

An IPL of the service requester system should occur after all the PTFs are successfully applied on the service requesters system.

Remote IPL time (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.

The possible time zone values are:

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

The possible start after time values are:

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

The possible start after date values are:

*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 if the time zone value *MGDSYS is specified.

Power down option (PWRDWNOPT)

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.

*CNTRLD

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.

*IMMED

Jobs end immediately.

Power down delay (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

Example 1: Sending a PTF and Requisites

SNDPTF   PTFID((1234567) (1234600))  DESTSRVRQS(*ALL)
         MAXDST(*SRVRQS)

This command sends a PTF and requisites to one or more selected service requesters.

Example 2: Sending a PTF to a Specific Service Requester

SNDPTF   PTFID(1234567)  DESTSRVRQS(*NETATR CHICAGO1)
         SNDRQT(*NO)

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.

Example 3: Sending a PTF and Its Requisites to Two Service Requesters

SNDPTF   PTFID(1234567)
         DESTSRVRQS((*NETATR CHICAGO1) (*NETATR CHICAGO2))
         CHECK(*NO)

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.

Example 4: Selecting One or More Service Requesters as Destination

SNDPTF   PTFID(1234567)  DESTSRVRQS(*SELECT)

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.

Example 5: Sending and Temporarily Applying One PTF

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'))

This command sends and temporarily applies one PTF on a specific requester, schedules when the PTF is applied, and schedules the IPL.

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.

Example 6: Sending and Applying a Permanent PTF

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'))

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.

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.

Example 7: Doing an IPL after Sending and Applying a PTF

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)

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.

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.

Error messages

*ESCAPE Messages

SMU107F

Error found processing &1 command.

SMU1080

Cannot specify *SELECT for service requester destination.

SMU109C

Errors detected while processing PTFs.

SMU109E

One or more PTFs could not be sent.

SMU109F

No PTFs sent.

*STATUS Messages

SMU109A

Contacting &1.&2 to determine required PTFs.