Controlling the asynchronous behavior of NIM operations

Certain NIM operations are asynchronous, meaning that NIM master might initiate the operation on the client, but does not wait for the operation to finish. The reason for this asynchronous behavior is because the NIM operation running on the client is typically time-consuming.

An example of an asynchronous operation is the bos_inst operation. Examples of synchronous operations are the cust, maint, and lppchk operations on a single machine target. However, these operations, when applied to members of a machine group, are asynchronous. The nim command initiates these operations on each member of the group without waiting for the operation to finish.

If desired, the asynchronous behavior of the cust, maint, and lppchk operations can be controlled by setting the async attribute on the command line. For example, to ensure that the execution of a customization script identified by the NIM resource script1 is executed completely on a given member of the group MacGrp1 before initiating execution of the script on the next member of the group, enter the following:
nim -o cust -a script=script1 -a async=no MacGrp1
To force the master to not wait for the customization operation to finish when running the script on machine Standalone1 that is not part of a machine group, enter:
nim -o cust -a script=script1 -a async=yes Standalone1