CL Command Reference - CHGPTFCRQA
CL Command List > CHGPTFCRQA Reference
Description:
The Change Program Temporary Fix Change Request Activity (CHGPTFCRQA) command changes a PTF distribution activity in a change request description.
Restrictions:
1. You must have *CHANGE authority to the change request description and *EXECUTE authority to the library.
2. 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.
3. A PTF save file must exist and be released in order to be sent to another system.
4. A PTF can only be retrieved from a single managed system.
5. 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.
6. 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.
7. 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.
8. PTFs are always removed temporarily except Vertical Licensed Internal Code (VLIC) PTFs which are removed permanently.
9. 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:
1. Authorization to the product specified on the activity is not verified until the activity runs.
2. All conditions must be met before the activity runs.
3. The start times indicate when the activity can be started. Actual start times can be later due to network and system delays.
Examples:
None.