Using the NIM cust operation

Use the cust operation to install software filesets and updates on standalone clients and SPOT resources.

Note: The following operation is not allowed when resources with architectures different from the client are allocated to the client.

See Customizing NIM clients and SPOT resources for information on performing a software customization of standalone NIM clients.

The command line syntax for the cust operation is as follows:

nim -o cust -a Attribute=Value ... TargetName |TargetNames

The target of a cust operation can be a standalone NIM client, a group of standalone NIM clients, or a SPOT resource.

The following are required attributes that can be specified for the cust operation:

Item	Description
-a filesets=Value	Specifies a list of filesets to install on the target. This attribute is required unless an installp_bundle is used for the operation.
-a installp_bundle=Value	Specifies an installp_bundle resource that lists filesets to install on the target. This attribute is required unless the filesets attribute is specified.
-a lpp_source=Value	Identifies the lpp_source resource that will provide the installation images for the cust operation.

The following are optional attributes that can be specified for the cust operation:

Item	Description
-a accept_licenses=Value	Specifies whether software licenses should be automatically accepted during installation. If `accept_licenses=yes`, the `-Y` flag is passed on the installp command and licenses are automatically accepted. If `accept_licenses=no`, license processing is controlled by the installp_flags attribute. The default value is accept_licenses=no.
-a async=Value	Specifies whether NIM should perform operations on group members asynchronously and not wait for the operation to complete on one member before beginning the operation on the next. The default value is async=yes.
-a concurrent=Value	Specifies the maximum number of machines from the selected group that should be installing at any given time. This attribute is only valid when the target of the operation is a machine group. If specified, NIM will monitor the progress of all machines in the group and attempt to keep no more or less than the number specified installing until all machines in the group are installed.
-a fix_bundle=Value	Contains a list of fixes to install on the target. Fixes should be listed in the fix_bundle resource by APAR number with one number per line.
-a fixes=Value	Identifies a list of fixes to install on the target. Fixes should be listed by APAR number. For example, `fixes="IX12345 IX54321"`.
-a group=Value	Specifies the name of a resource group to use for the installation. A resource group can be specified as an alternative to specifying multiple resources as separate attributes. If a resource group is specified, and it contains an lpp_source, the lpp_source attribute is no longer required.
-a installp_flags=Value	Identifies the flags that tell installp how to apply the filesets specified by the filesets, installp_bundle, fixes, and fix_bundle attributes. The default value is installp_flags=agQX.
-a resolv_conf=Value	Specifies a resolv_conf resource for configuring domain and name resolution on a client.
-a script=Value	Specifies a script resource to be run on the target system after all software has been installed.
-a show_progress=Value	Indicates whether status should be displayed while software is installed. The default value is show_progress=yes.
-a time_limit=Value,	Specifies the maximum number of hours that should elapse before ceasing to initiate installation of additional members of the selected group of machines. This value can only be specified when limiting the number of concurrent operations on a group.
-a live_update_data=Value	Identifies the `live_update_data` resource that provides the AIX® Live Update information for the cust operation.
-a live_update=Value	Specifies that a Live Update operation must be executed. If a `live_update_data` resource is specified, the resource is Network File System (NFS)-exported from the NIM resource server and mounted on the client. On the Network Installation Manager (NIM) client, the mounted `live_update_data` resource is copied to the /var/adm/ras/liveupdate/lvupdate.data file. If a `live_update_data` resource is not specified, the file that is located at /var/adm/ras/liveupdate/lvupdate.data on the client is used.