CL Command Reference - CHGOBJCRQA

CL Command List > CHGOBJCRQA Reference

Description:

The Change Object Change Request Activity (CHGOBJCRQA) command changes an object distribution activity in a change request description. The object referred to in the activity can be an i5/OS object identified by an i5/OS object name or a global name, or a non-i5/OS object such as a PS/2 file which is identified by a global name.

The activity can be conditioned so that it only runs after one or more other activities have completed (successfully or unsuccessfully). The activity can also be scheduled to run at a date and time in the future.

Restrictions:

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

2. An object can be specified using an i5/OS object name or a global name but not both.

3. The global name can be a maximum of 65-n characters in length, where n is the number of tokens. A maximum of 10 tokens can be specified.

4. Only i5/OS program objects or file members such as CL and REXX can be run.

5. The object to be distributed cannot reside in the QTEMP library.

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

Notes:

The following notes provide information on how the command works.

1. When you add the activity, you do not need to be authorized to any objects that are to be manipulated. When you submit a change request, you must be authorized to any objects that are manipulated.

2. The save and restore history for the object is not updated when it is sent or retrieved.

3. Active message queues are not saved when libraries (*LIB) are sent or retrieved.

4. All conditions must be satisfied before the activity can be run.

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

6. If a global name is to be used, the Add Distribution Catalog Entry (ADDDSTCLGE) command can be used to indicate where the object is located or is to be stored.

7. Authorization to the object specified on the activity is not verified until the activity runs.


Examples:

None.