CHGPRDCRQA (Change Product Change Request Activity) Command Description

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

CHGPRDCRQA Command syntax diagram

 

Purpose

The Change Product Change Request Activity (CHGPRDCRQA) command changes a product distribution activity in a change request description.

 

Restrictions

  1. This command is shipped with public *EXCLUDE authority.

  2. You must have *CHANGE authority to the change request description object and *EXECUTE authority to the library.

  3. If you change the activity, you do not need to be authorized to any objects that are to be manipulated. If you submit the change request, be authorized to the change request description.

  4. The product must be packaged in a save file and cataloged at the time it runs. Use the Package Product for Distribution (PKGPRDDST) command to package the product.

  5. If a 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 satisfied before the activity can be performed.

  3. The start times indicate when the activity can be started. Actual start times can be later due to network and system delays.

  4. Action *DLTCLGE only deletes the save file containing the licensed program and deletes the distribution catalog entry that maps this save file. It does not delete the product.

  5. The save file containing the product is not deleted after an installation. This should be done using a *DLTCLGE action.

  6. If TGTRLS(*ONLY) is specified, the action parameter must be a value other than *INS.

  7. When it is requested to send the license key of the product, a record with the license key information must exist in the central site license repository by the time this activity runs.

  8. All the existing records in the central site license repository containing the license key information for the specified product will be sent to the specified managed system or systems, but only those that match the system serial number are added to the managed system license repository.

 

Required Parameters

CRQD
Specifies the change request description object name.

The possible library values are:

*LIBL: All of the libraries in the user and system portions of the job's library list are searched.

*CURLIB: The current library for the job is used to locate the object.

library-name: Specify that only the library named in this parameter is searched.

change-request-description: Specify the name of the change request description object.

ACTIVITY
Specifies the name of the activity to change in the change request description.

*LAST: The activity is the last to run in the change request. When *LAST is specified for the activity (ACTIVITY) parameter, the condition (COND) parameter and the start time (STRTIME) parameter cannot be specified. Only one activity named *LAST can exist in the change request description.

activity-name: Specify a 10-character activity name.

ACTION
Specifies the product distribution function that is to be performed.

*SAME: The value does not change.

*SND: Send the product to the specified managed systems.

*RTV: Retrieve the product from the specified managed systems.

*DLTCLGE: Delete the catalog entry and associated save file for the product from the specified managed systems.

*INS: Install the product on the specified managed systems.

*SNDINS: Send and install the specified product on the specified managed systems.

PRDID
Specifies the 7-character identifier of the product for which the action is performed.

*SAME: The value does not change.

product-ID: Specify the 7-character product ID that is used in the activity.

 

Optional Parameters

RLS
Specifies which version, release, and modification level of the product is used.

*SAME: The release does not change.

*ONLY: The release level of the product that is installed on your system.

release-level: Specify the release level in the format VxRxMy, where Vx is the version number, where Rx is the release number, and My is the modification number. Valid values for x range from numbers 0 through 9. Valid values for y range from numbers 0 through 9 and the letters A through Z.

OPTION
Specifies which of the optional parts of the product given in the PRDID parameter are used.

*SAME: The value does not change.

*BASE: Only the base part of the product is used. This is only valid when ACTION is *SND, *RTV, *INS, and *SNDINS.

product-option-number: Specify the option number for the product load being used. Valid values range from 1 through 99.

LODTYPE
Specifies the product load objects being used.

*SAME: The value does not change.

*ALL: Code and language objects specified on the LODID parameter are used.

*CODE: The object associated with this product load are used.

*LNG: The objects associated with the NLV identified on the LODID parameter are used.

LODID
Specifies the load identifier used.

*SAME: The value does not change.

*ALL: All languages for this product option are used.

*CODE: The code load is used.

product-load-ID: Specify the load ID of the product when LODTYPE(*LNG) or LODTYPE(*ALL) is used. The load ID must be one of the valid IBM national language versions and be specified in the form 29xx. The value of x can be 0 through 9.

TGTRLS
Specifies the release of the operating system on which you intend to use the product.

*SAME: The value does not change.

*ONLY: The release is determined by the release of the existing product. This value is not valid if more than one release exists for the same product.

*CURRENT: The product is to be used on the release of the operating system currently running on your system.

*PRV: The product is to be used on the previous release with modification level 0 of the operating system.

release-level: Specify the release level in the format VxRxMx. The product can be used on a system with the specified release or with any later release of the operating system installed. Valid values depend on the current version, release, and modification level, and can change with each new release.

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

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

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

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 the node list (NODL) parameter 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.

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

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

KEEPCLGE
Specifies if the distribution catalog entry and its associated save file corresponding to the product is kept on the specified systems. This is only valid if ACTION(*INS) or ACTION(*SNDINS) is specified.

*SAME: The value does not change.

*NO: The catalog entry and associated save file are not kept.

*YES: The catalog entry and associated save file are kept.

SNDLICKEY
Specifies if the license key is to be sent with the product.

*SAME: The value does not change.

*YES: The license key is sent with the product.

*NO: The license key is not sent with the product.

TEXT
Specifies the activity description.

*SAME: The value does not change.

*GEN: A text description is generated based on the action chosen.

text-description: Specify a 50-character description of the activity.

COND
Specifies which conditions must be met before this activity can be performed. Each condition identifies the activity that must run before this activity and the value the end codes from that activity 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.

*SAME: The value does not change.

*NONE: There are no conditions for this activity.

Element 1: Conditioning Activity

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

Element 2: Relational Operator

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

*EQ: Equal

*GT: Greater than

*LT: Less than

*NE: Not equal

*GE: Greater than or equal

*LE: Less than or equal

Element 3: Condition Code

This element is the value compared to the actual end code of the conditioning activity.

*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 can only be specified with relational operator *EQ or *NE.

*ANY: The activity ended with any end code. This end code is only be 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

Element 4: Condition Mode

This element 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.

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

Element 1: Start After Time

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

Element 2: Start After Date:

*SAME: The value does not change.

*CURRENT: This activity can start on or after the date on which the change request is submitted.

*NEXT: The activity can start on any date after the date 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.

Element 3: Start Before Time

This element is ignored if 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 at which 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).

Element 4: Start Before Date

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

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.

Element 1: Time Zone

The time zone of the remote start time.

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

Element 2: Start After Time

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 be started 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).

Element 3: Start After Date

*SAME: The value does not change.

*CURRENT: This function can start on the managed system on any date on or after the date the activity starts on the central site system.

*NEXT: This function can start 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

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

  2. This parameter can only be specified if *INS or *SNDINS actions are specified.


HOLD
Specifies that the activity be held when the change request is submitted.

*SAME: The value does not change.

*NO: The activity is not held. It runs when all conditions and the start time are met.

*YES: The activity is held for all nodes when the change request is submitted. It must be released by you before it runs.

Examples for CHGPRDCRQA

Example 1: Change an Activity to Send a Product 

CHGPRDCRQA CRQD(MYLIB/CRQ1) ACTIVITY(ACT01) ACTION(*SND)
  PRDID(1ACCPAY) RLS(V5R2M0) OPTION(1) LODTYPE(*CODE)
  LODID(*CODE)  SNDLICKEY(*YES)  CPNAME((*NETATR SYS2))

Change an activity to send the accounts payable product to the SYS1 system. Option one with the code parts of the product and its license key will be sent.

Example 2: Change an Activity to Install an Application 

CHGPRDCRQA CRQD(MYLIB/CRQ2) ACTIVITY(*LAST) ACTION(*INS)
  PRDID(1SCHEDU) RLS(V5R2M0) OPTION(*BASE) LODTYPE(*ALL)
  LODID(*ALL) NODL(MYLIB/ALLSYS) RMTSTRTIME(*MGDSYS ('23:00:00' *SAME))

Change the last activity of the change request CRQ2, so it installs the scheduler application on all the systems specified in the ALLSYS node list. Both the code and the languages for the application will be installed at 11:00 p.m. in the time zone where the managed systems are located.

Example 3: Change the Last Activity of the Change Request 

CHGPRDCRQA CRQD(MYLIB/CRQ3) ACTIVITY(*LAST)
  ACTION(*DLTCLGE) PRDID(1HUMRES) RLS(V5R2M0)
  OPTION(*BASE) LODTYPE(*ALL) LODID(2924)
  CPNAME((*NETATR SYS3))

Change the last activity of the change request CRQ3, so it deletes the product packaged for distribution for the human resources application on the SYS3 system.

Error messages for CHGPRDCRQA

*ESCAPE Messages

None