Change PTF CRQ Activity (CHGPTFCRQA)

The Change Program Temporary Fix Change Request Activity (CHGPTFCRQA) command changes a PTF distribution activity in a change request description.

Restrictions:

You must have *CHANGE authority to the change request description and *EXECUTE authority to the library.
The PTF must be for an iSeries product package using System Manager licensed program. The PTF must be supported using the Work with Supported Products (WRKSPTPRD) command. Software redesigns can be managed for other types of systems by using globally named objects on the Add Object Change Request Activities (ADDOBJCRQA) command or by using Add Change Management Activity (QNSADDCM) API.
A PTF save file must exist and be released in order to be sent to another system.
A PTF can only be retrieved from a single managed system.
If the destination node does not have the Managed System Services licensed program installed, then only the send action is available. The activity is considered successful when the PTF is sent not when it arrives.
Delayed PTFs are applied only during the next IPL. Apply all other PTFs immediately while the activity runs on the system or during the next IPL.
PTFs marked as delayed can only be applied permanently if they have been previously applied temporarily. Notice that the IPL would have Notice that an IPL would have been required to apply them since they are delayed.
PTFs are always removed temporarily except Vertical Licensed Internal Code (VLIC) PTFs which are removed permanently.
If a node list (NODL) value is specified, the node list can only contain entries that have a value of *SNA for the address type.

The following notes provide information on how the command works.

Notes:

Authorization to the product specified on the activity is not verified until the activity runs.
All conditions must be met before the activity runs.
The start times indicate when the activity can be started. Actual start times can be later due to network and system delays.

Parameters

Keyword	Description	Choices	Notes
CRQD	Change request description	Qualified object name	Required, Key, Positional 1
	Qualifier 1: Change request description	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
ACTIVITY	Activity	Name, *LAST	Required, Key, Positional 2
ACTION	Action	SND, RTV, DLT, APY, SNDAPY, RMV, *SAME	Optional, Positional 3
PTFID	PTF identifier	Element list	Optional
	Element 1: PTF	Character value, ALL, SAME
	Element 2: Product	Character value, ONLY, SAME
	Element 3: Release level	Character value, *SAME
NODL	Managed systems node list	Element list	Optional
	Element 1: Node list	Single values: NONE, SAME Other values: Qualified object name
	Qualifier 1: Node list	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
CPNAME	Managed system node names	Single values: NONE, SAME Other values (up to 50 repetitions): Element list	Optional
	Element 1: Network identifier	Communications name, *NETATR
	Element 2: Control point	Communications name
PTFPART	PTF parts	PTF, CVRLTR, *SAME	Optional
CVRLTRLNG	Cover letter language	2900-2999, SRVRQS, SAME	Optional
APY	Extent of change	TEMP, PERM, LODONLY, SAME	Optional
DLYAPY	Delayed PTF apply	NO, YES, *SAME	Optional
DLYRMV	Delayed PTF remove	NO, YES, *SAME	Optional
RMTSTRTIME	Start time on managed system	Element list	Optional
	Element 1: Time zone	LCLSYS, MGDSYS, *SAME
	Element 2: Start after	Element list
	Element 1: Time	Time, CURRENT, SAME
	Element 2: Date	Date, CURRENT, NEXT, *SAME
TEXT	Text 'description'	Character value, GEN, BLANK, *SAME	Optional
COND	Activity conditions	Single values: NONE, SAME Other values (up to 5 repetitions): Element list	Optional
	Element 1: Activity	Generic name, name, *PRV
	Element 2: Relational operator	EQ, GT, LT, LE, NE, GE
	Element 3: End code	0-99, SUCCESS, FAIL, NOTRUN, ANY
	Element 4: Condition mode	ALLNODES, SAMENODE
STRTIME	Activity start time	Element list	Optional
	Element 1: Start after	Element list
	Element 1: Time	Time, CURRENT, SAME
	Element 2: Date	Date, CURRENT, NEXT, *SAME
	Element 2: Start before	Element list
	Element 1: Time	Time, ANY, CURRENT, *SAME
	Element 2: Date	Date, ANY, CURRENT, NEXT, SAME
HOLD	Hold activity	NO, YES, *SAME	Optional

Top

Action (ACTION)

Specifies the function to be performed on the resource.

The possible values are:

*SAME: The value does not change.
*SND: Send the specified PTF to the specified managed system. The PTF is not loaded as part of this activity.
*RTV: Retrieve the specified PTF from the specified managed system.
*DLT: Deletes the PTF save file and cover letter on the specified managed system.
*APY: Apply the PTF on the specified system. All requisite PTFs must be applied. A PTF may set in loaded status ("Not applied"). 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" ("Not applied") status. Request to apply one PTF and all corresponding corequisite PTFs are applied.
*SNDAPY: Send, load, and apply the PTF on the specified system. All requisite PTFs must have already been applied. If the PTF has corresponding corequisite PTFs, set all PTFs to "loaded" ("Not applied") status to apply all of them.
*RMV: Temporarily, remove the PTF on the specified systems.

PTF (PTFID)

Specifies the PTF that is to be distributed.

The possible values are:

*SAME: The value does not change.
PTF-identifier: Specify a 7-character PTF identifier.
*ALL: All PTFs for the specified product. It can only be specified when applying, deleting, or removing PTFs. A product must be specified.

The product identifier values are:

This is the product identifier of the product to which the PTF is associated.

*SAME: The value does not change.
*ONLY: The PTF identifier specified is associated with only one supported product.
product-ID: Specify the product to which the PTF is associated. The product must be specified when PTF identifiers are not unique across products.

The release level of product values are:

This element shows the release level of the product.

*SAME: The value does not change.
release(VxRxMx): 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.

Node list name (NODL)

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

The possible values are:

*SAME: The value does not change.
*NONE: The systems on which this activity is to be performed are not specified by a node list. Individual control point names must be specified.

The possible library values are:

*LIBL: All of the libraries in the user and system portions of the job's library list are searched for the node list object.
*CURLIB: The current library for the job is used to locate the node list object.
library-name: Specify the name of the library to be searched

The possible node list value is:

node-list-name: Specify the node list object name containing the list of systems on which the activity is to be performed.

Change Product CRQ Activity (CPNAME)

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 is specified.

*SAME: The value does not change.
*NONE: The systems on which this activity is performed are not identified individually. A node list must be specified.

The possible values are:

*NETATR: 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.
network-identifier: Specify the APPN network identifier of the managed system on which the activity is to be performed.

The possible control point name value is:

control-point-name: Specify the APPN control point name of the managed system on which the activity is to be performed.

Start time on managed system (RMTSTRTIME)

Specifies the date and time when the activity can begin running on the managed system. The current date and time values, and next date values are determined when the activity begins running at the central site system based on the central site date and time.

The possible time zone of the remote start time values are:

*SAME: The value does not change.
LCLSYS: The remote start time is specified in the time zone of the central site system.
*MGDSYS: The remote start time is specified in the time zone of the managed system.

The possible start after time values are:

This is the definition of the time after which the activity is to start.

*SAME: The value does not change.
*CURRENT: 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 3.
start-after-time: 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.

The possible start after date values are:

*SAME: The value does not change.
*CURRENT: This function starts on the managed system on any date on or after the date this activity starts on the central site system.
*NEXT: This function starts on the managed system on any date after the date this activity starts on the central site system.
start-after-date: Specify the date after the functions start on the managed system. The date must be specified in the job date format.

Notes:

The special values *CURRENT and *NEXT are specified for the date and the time if the time zone value *MGDSYS is specified.
This parameter can only be specified if *APY, *RMV, or *SNDAPY actions are specified.

Activity conditions (COND)

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.

The possible single values are:

*SAME: The value does not change.
*NONE: There are no conditions for this activity.

The conditioning activity values are:

The activity which must be run before this activity.

*PRV: 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.
conditioning-activity-name: Specify the name of the activity which must be 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.
generic*-activity-name: Specify the generic name of the activities which must be run before this activity.

The relational operator values are:

This element is the relational operator to use when comparing the end code from an activity.

*EQ: Equal
*GT: Greater than
*LT: Less than
*NE: Not equal
*GE: Greater than or equal
*LE: Less than or equal

The condition code values are:

*SUCCESS

The activity ended successfully (0 <= end code <= 9). This end code can only be specified with relational operator *EQ or *NE.

*FAIL

The activity failed (10 <= end code <= 89). This end code can only be specified with relational operator *EQ or *NE.

*NOTRUN

The activity never started (90 <= end code <= 99). This end code is only specified with relational operator *EQ or *NE.

*ANY

The activity ended with any end code. This end code is only specified with relational operator *EQ.

end-code

Specify an integer value (0-99) that indicates the result of an activity (success or failure). The end code ranges and descriptions are:

00

Activity completed successfully.

01-09

Activity completed with warning messages.

10-29

Activity did not complete successfully.

30-39

Activity was canceled by a user before it completed.

30 = Activity ended with *CNTRLD option
35 = Activity ended with *IMMED option
39 = Activity ended with *FRCFAIL option

40-49

Activity was not run due to errors detected by the application.

40 = Activity not run for security reasons

90-99

Activity was not run because conditions or schedules were not met.

95 = Scheduled start time expired
99 = Conditions cannot be met

The possible condition modes are:

The condition mode indicates which systems the conditioning activity must have completed on before this activity can be performed.

*ALLNODES: The conditioning activity specified must complete on all nodes before this activity runs.
*SAMENODE: When the conditioning activity specified completes for a given node, the activity specified on the ACTIVITY parameter can run for that same node even though the conditioning activity specified cannot have completed for all other nodes. In the case where this activity can run for that node, the condition is ignored.

Activity start time (STRTIME)

Specifies the date and time when this activity can be started on the central site system. The current date and time values and the next date values are determined when the change request is submitted.

The possible start after time values are:

*SAME: The value does not change.
*CURRENT: This activity can start any time on or after the time when the change request is submitted.
start-after-time: Specify the time when this activity can start. The time can be entered as 4 or 6 digits (hhmm or hhmmss) where hh = hours, mm = minutes, and ss = seconds. Seconds are optional. The time can be specified with or without a time separator such as a colon (:). With a time separator, specify a string of 5 or 8 digits (hh:mm or hh:mm:ss).

The possible start after date values are:

*SAME: The value does not change.
*CURRENT: This activity can start on or after the date the change request is submitted.
*NEXT: The activity can start on any date after the date when the change request is submitted.
start-after-date: Specify the date after this activity can start. The date must be specified in the job date format.

The possible start before time values are:

This element is ignored if the start before date is *ANY.

*SAME: The value does not change.
*ANY: The activity can start at any time on or before the start before date.
*CURRENT: The activity must start before the time when the change request was submitted on the date specified on the start before date element.
start-before-time: 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).

The possible start before date values are:

*SAME: The value does not change.
*ANY: The activity can start at any time after the start after time and the start after date.
*CURRENT: The activity must start on the date the change request is submitted.
*NEXT: The activity must start by the day after the date the change request is submitted.
start-before-date: 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.

Examples

Example 1: Applying a Permanent Change to a PTF

CHGPTFCRQA   CRQD(MYLIB/CR1)  ACTIVITY(ACT01)
             ACTION(*APY)  APY(*PERM)
             PTFID(SF12345)  CPNAME((*NETATR SYS1))

This command changes an activity to permanently apply PTF SF12345 on system SYS1.

Example 2: Sending a Change to a PTF

CHGPTFCRQA   CRQD(MYLIB/CR2)  ACTIVITY(ACT03)
             ACTION(*SND)  PTFID(SF89345)
             PTFPART(*CVRLTR)  CVRLTRLNG(2950)
             NODL(MYLIB/EUROPESYS)

This command changes an activity to send the PTF cover letter to all systems in Europe that are identified in the EUROPESYS node list.

Example 3: Changing Activities to Apply a PTF

CHGPTFCRQA   CRQD(MYLIB/CR3)  ACTIVITY(ACT01)
             ACTION(*SND)
             PTFID(SF99911)  CPNAME((NET1 SYSX))

CHGPTFCRQA   CRQD(MYLIB/CR3)  ACTIVITY(ACT02)
             ACTION(*APY)  APY(*TEMP)  PTFID(SF99911)
             RMTSTRTIME((*MGDSYS (02:00:00) (03/30/02))
             CPNAME((NET1 SYSX))

This command changes activities to send a PTF and apply it temporarily at 2:00 a.m. on a system encountering a problem.

Example 4: Changing an Activity to Load a PTF

CHGPTFCRQA   CRQD(MYLIB/CR4)  ACTIVITY(ACT01)  ACTION(*APY)
             PTFID(SF89555)  CPNAME(*NETATR SYS4)  APY(*LODONLY)

This command changes an activity to load only the PTF SF89555, which is part of a corequisite PTF group, on system SYS4.

Example 5: Changing an Activity to Send and Permanently Apply a PTF in Delayed Mode

CHGPTFCRQA   CRQD(MYLIB/CR5)  ACTIVITY(ACT01)  ACTION(*SNDAPY)
             PTFID(SF91388)
             CPNAME(*NETATR SYS5)  DLYAPY(*YES)

This command changes an activity to send and permanently apply PTF SF91388 during the next unattended IPL.