Add License CRQ Activity (ADDLICCRQA)

The Add License CRQ Activity (ADDLICCRQA) command adds a license key distribution activity to a change request description that performs a license key distribution function.

The activity can be conditioned so that it will only run 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:

This command is shipped with public *EXCLUDE authority.
The user must have *CHANGE authority to the change request description object and *EXECUTE authority to the library.
The user adding the activity does not need to be authorized to any objects that are to be manipulated.
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 license key information does not need to exist in the license repository when a license activity is being added to a change request, but it must exist by the time the activity runs.

Notes:

All conditions must be satisfied before the activity can be performed.
The start times indicate when the activity can be started. Actual start times may be later due to network and system delays.
All the existing records in the central site license repository containing the license key information for the specified product are sent to the specified managed system or systems. Only those ones that match the system serial number are added to the managed system license repository.

Parameters

Keyword	Description	Choices	Notes
CRQD	Change request description	Qualified object name	Required, Positional 1
	Qualifier 1: Change request description	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
ACTIVITY	Activity	Name, GEN, LAST	Optional, Positional 2
ACTION	Action	*SND	Optional, Positional 3
PRDID	Product ID	Character value, *ALL	Optional, Positional 4
LICTRM	License term	Character value, *ALL	Optional, Positional 5
NODL	Managed systems node list	Element list	Optional
	Element 1: Node list	Single values: NONE Other values: Qualified object name*
	Qualifier 1: Node list	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
CPNAME	Managed system node names	Single values: NONE Other values (up to 50 repetitions): Element list*	Optional
	Element 1: Network identifier	Communications name, *NETATR
	Element 2: Control point	Communications name
TEXT	Text 'description'	Character value, GEN, BLANK	Optional
COND	Activity conditions	Single values: NONE 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
	Element 2: Date	Date, CURRENT, NEXT
	Element 2: Start before	Element list
	Element 1: Time	Time, ANY, CURRENT
	Element 2: Date	Date, ANY, CURRENT, *NEXT
HOLD	Hold activity	NO, YES	Optional

Top

License term (LICTRM)

Specifies the license term for which the license keys information will be sent.

*ALL

The license keys for all license term of the specified product existing in the focal point license repository will be distributed.

license-term

Specify the license term in one of the following formats:

Vx: The authorized usage limit is valid for the entire version of the product or feature.
VxRy: The authorized usage limit is valid for the entire release of the product or feature.
VxRyMz: The authorized usage limit is valid only for a modification of the product.

where "x" and "y" can be a number from 0 through 9, and "z" can be a number 0 through 9 or a letter A through Z.

Managed systems node list (NODL)

Specifies that the node list parameter is the object name that contains a list of systems that are the destinations for the activity. This parameter cannot be specified if the control point name (CPNAME) parameter is specified.

The possible value is:

*NONE: The systems on which this activity is to be performed are not identified 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 name value is:

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

Managed system node names (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.

The possible values are:

*NONE: The systems on which this activity is to be 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.

The possible control point value is:

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

Activity conditions (COND)

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

The possible conditioning activity values are:

The activity that 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 this 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.

The possible relational operator value is:

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

The possible condition code value is:

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 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 mode values are:

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 can run.
*SAMENODE: When the conditioning activity specified completes for a given node, the activity specified on the ACTIVITY parameter may run for that same node even though the conditioning activity specified may not have completed on all other nodes. In the case where this activity lists a node not in the conditioning activity, this activity may run for that node; the condition is ignored.

The possible value is:

*NONE: There are no conditions for this activity.

Activity start time (STRTIME)

Specifies the date and time when this activity can be started on the central site system. This is the date and time at which the specified license information will be sent. The current date and time values and next date values are determined when the change request is submitted.

The possible start after time values are:

*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 (:). Without a time separator, specify a string of 4 to 6 digits (hhmm or hhmmss) where hh = hours, mm = minutes, and ss = seconds. With a time separator, specify a string of 5 or 8 digits (hh:mm or hh:mm:ss) where the time separator specified for your job is used to separate the hours, minutes, and seconds.

The possible start after date values are:

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

The possible start before time values are:

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

*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 (:). Without a time separator, specify a string of 4 to 6 digits (hhmm or hhmmss) where hh = hours, mm = minutes, and ss = seconds. With a time separator, specify a string of 5 or 8 digits (hh:mm or hh:mm:ss) where the time separator specified for your job is used to separate the hours, minutes, and seconds.

The possible start before date values are:

*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: Adding an Activity to Send Licenses

ADDLICCRQA   CRQD(MYLIB/CR1)  ACTIVITY(ACT01)  ACTION(*SND)
             PRDID(1ACCOUN)  LICTRM(V5R2M0)
             CPNAME((*NETATR SYS1))

Add an activity to send the licenses for the 1ACCOUN product, with a license term of V5R2M0, to the license repository of the iSeries server SYS1. If 1ACCOUN product is installed on the managed system, the license is also activated.

Example 2: Adding an Activity to Send the License for Product 1CHECKS with License Term V5

ADDLICCRQA   CRQD(MYLIB/CR3)  ACTIVITY(ACT02)  ACTION(*SND)
             PRDID(1CHECKS)  LICTRM(V5)
             STRTIME(('23:00:00' '9/30/02'))
             NODL(NETLIB/ACCTSYS)

This example shows how to add an activity to send the license for product 1CHECKS with license term V5 to the systems identified in the ACCTSYS node list. Only the license keys matching the managed system serial number are added to the license repository. The license activity will be performed at 11 PM on September 30, 2002.