nim Command

Purpose

Performs operations on Network Installation Management (NIM) objects.

Syntax

nim { -o Operation} [ -F ] [ -t Type ] [ -a Attribute=Value... ] {ObjectName}

Description

The nim command performs an operation on a NIM object. The type of operation that is performed depends on the type of object that is specified by the ObjectName parameter. Possible operations include initializing environments and managing resources. You can use the lsnim command to display the list of supported operations.

Flags

Table 1. Flags
Item	Description
-a `Attribute`=`Value` . . .	Assigns the specified value to the specified attribute. Use the `lsnim -q Operation -t Type` command to get a list of valid attributes for a specific operation.
-F	Overrides some safety checks.
-o `Operation`	Specifies an operation to perform on a NIM object. Following are the possible operations: `activate` Starts a managed system. `allocate` Allocates a resource for use. `alt_disk_install` Performs an alternate disk installation. `alt_disk_mig` Creates a copy of rootvg to a free disk (or disks) and simultaneously upgrades it to a new version or release level of AIX. `bos_inst` Performs a BOS installation. `change` Changes an object's attributes. `check` Checks the status of a NIM object. `chwpar` Changes the characteristics of managed workload partitions. `create` Creates an instance of a managed system. `cust` Performs software customization. `deactivate` Stops a managed system. `deallocate` Deallocates a resource. `define` Defines an object. `destroy` Removes an instance of a managed system. `diag` This operation enables a system to boot a diagnostic image. `dkls_init` Initializes a diskless environment of a system. `dtls_init` Initializes a dataless environment of a system. `fix_query` Lists the fix information for an APAR or keyword. `linux_inst` Installs the Linux® operating system on stand-alone clients. `lppchk` Verifies installed filesets on NIM systems and SPOTs. `lppmgr` Eliminates unnecessary software images in an `lpp_source`. `lslpp` Lists licensed program information about an object. `lswpar` This operation shows the characteristics of managed workload partitions. `maint` Performs software maintenance. `maint_boot` Enables a system to boot in maintenance mode. `reboot` Reboots a NIM client system.

Table 2. Flags (continued)
Item	Description
-o `Operation` (Continued)	`remove` Removes an object. `reset` Resets an object's NIM state. `restvg` Performs a `restvg` operation. The `restvg` operation ignores the passphrase or Platform keystore (PKS) encryption authentication method when called from NIM master by using the `nim -o restvg` command. `select` This operation includes and excludes group members from operations that are performed on the group. `showlog` Displays a NIM client's installation, boot or customization log, or a SPOT's installation log from the NIM master. `showres` Displays the contents of a NIM resource. `sync` Synchronizes the NIM database with an alternate master. `sync_roots` Synchronizes root directories for diskless and dataless clients for a specific Shared Product Object Tree (SPOT). `syncwpar` Synchronizes the managed workload partition software with the managing system. `takeover` This operation allows a machine that is configured as an `alternate_master` to take control of the NIM environment. `unconfig` Unconfigures the NIM master fileset. `update` Adds software to an `lpp_source` or removes software from an `lpp_source`. `updateios` Performs software customization and maintenance on a virtual input-output server (VIOS) management server that is of the `vios` or `ivm` type. Use the `lsnim -POt Type` command to get a list of the valid operations for a specific type.

Table 3. Flags (Continued)
Item	Description
-t `Type`	Specifies the type of the NIM object for define operations. Following are the possible NIM object types: `resource` types `adapter_def` Directory containing secondary adapter definition files. `boot` An internally managed NIM resource that is used to indicate that a boot image is allocated to a client. `bosinst_data` Configure the file that is used during base system installation. `devexports` The device exports the files for workload partitions. `dump` Parent directory for client dump files. `exclude_files` Contains files to be excluded from a `mksysb` image. `fb_script` Executable script that is run during the first reboot of a machine. `fix_bundle` Fix (keyword) input file for the `cust` or `fix_query` operation. `home` Parent directory for client /home directories. `image_data` Configure the file that is used during base system installation. `installp_bundle` Installp bundle file. `ios_mksysb` Represents a backup image that is taken from a VIOS management server that is of the `vios` or `ivm` type. `linux_source` Represents the Linux installation media. `log` Captures log data during a network installation. `lpp_source` Source device for optional product images. `mksysb` `mksysb` image. `nas_filer` A network-attached storage (NAS) device. `nim_script` An internally managed NIM resource that is used to indicate that NIM must run a script as a part of a NIM operation. `paging` Parent directory for the paging files of the client. `root` Parent directory for client `/` (root) directories. `resolv_conf` Name server configuration file. `savevg` A `savevg` image. `savewpar` Workload partition backup image. `script` Executable file that is run on a client. `secattrs` Security attributes file for workload partitions. `shared_home` /home directory that is shared by the clients. `shared_root` / (root) directory that is shared by clients `spot` Shared Product Object Tree (SPOT) - equivalent to /usr file system. `tmp` Parent directory for client /tmp directories. `vg_data` Configuration file that is used during volume group restoration. `wpar_spec` Specification file for creating workload partitions.

Item Description

Item	Description
-t `Type` (Continued)	`machine` types `alternate_master` A system that is reserved as a backup in case the primary NIM master ceases to function properly. `diskless` All file systems and resources are remote. `dataless` Local paging, dump, remote /, /usr, others remote or local. `stand-alone` Local file systems and resources. `master` System that controls the NIM environment. `wpar` Workload partition that is hosted by the managing system. `management` types `bcmm` A blade management module hardware. `cec` A central electronic complex hardware. `hmc` A Hardware Management Console system. `ivm` An integrated virtual management system. `vios` A Virtual I/O Server. `network` types `tok` Token-Ring network. `ent` Ethernet network. `fddi` FDDI network. `atm` ATM network. `generic` Other Internet Protocol networks. `hfi` Host Fabric Interface (HFI) network. `group` types `mac_group` A group of machines. `res_group` A group of resources. `customer` types `customer` A combined group of machines and resources.

-t Type (Continued)

machine types

alternate_master: A system that is reserved as a backup in case the primary NIM master ceases to function properly.
diskless: All file systems and resources are remote.
dataless: Local paging, dump, remote /, /usr, others remote or local.
stand-alone: Local file systems and resources.
master: System that controls the NIM environment.
wpar: Workload partition that is hosted by the managing system.

management types

bcmm: A blade management module hardware.
cec: A central electronic complex hardware.
hmc: A Hardware Management Console system.
ivm: An integrated virtual management system.
vios: A Virtual I/O Server.

network types

tok: Token-Ring network.
ent: Ethernet network.
fddi: FDDI network.
atm: ATM network.
generic: Other Internet Protocol networks.
hfi: Host Fabric Interface (HFI) network.

group types

mac_group: A group of machines.
res_group: A group of resources.

customer types

customer: A combined group of machines and resources.

Security

Access Control: You must have root authority to run the nim command.
RBAC users: Attention RBAC users: This command can perform privileged operations. Only privileged users can run privileged operations. For more information about authorizations and privileges, see Privileged Command Database in Security. For a list of privileges and the authorizations that are associated with this command, see the lssecattr command or the getcmdattr subcommand.

Examples

The following examples are grouped by operation.

activate

To start the managed wpar1 workload partition, enter the following command:
```
nim -o activate wpar1
```
To start the managed wpar1 workload partition with more startwpar command flags with verbose output, enter the following command:
```
nim -o activate -a cmd_flags="-v" wpar1
```

allocate

To allocate resources to a diskless workstation with the name syzygy and SPOT attribute value of spot1, enter the following command:
```
nim -o allocate -a spot=spot1 syzygy
```
To perform a base system installation on the system that is named krakatoa, resources must be allocated initially by entering:
```
nim -o allocate -a spot=myspot -a lpp_source=images krakatoa
```
The NIM environment can be initialized to support the installation by performing the bos_inst operation, enter the following command:
```
nim -o bos_inst krakatoa
```
To install the software product adt, into a stand-alone system stand1, given that the installable option adt, in the lpp_source, images, enter the following commands:
```
nim -o allocate -a lpp_source=images stand1
```
```
nim -o cust -a filesets="adt" stand1
```
To install software products into a stand-alone system stand1, such that the image for the installable option adt, in the lpp_source, images, and the installp_bundle, bundle1 that contains the name of the installable option, enter the following commands:
```
nim -o allocate -a lpp_source=images \
-a installp_bundle=bundle1 stand1
```
```
nim -o cust stand1
```
To automatically configure a machine with name resolution services after a BOS installation, create the /exports/resolv.conf file, with contents similar to the following sample file:
```
nameserver      129.35.143.253
nameserver      9.3.199.2
domain          austin.ibm.com
```
After creating the /exports/resolv.conf file, enter the following command:
```
nim -o define -t resolv_conf -a location=/exports/resolv.conf \
-a server=master rconf1
```
Before issuing the bos_inst operation, allocate this resource with other required and optional resources by entering the following command:
```
nim -o allocate -a spot=spot1 -a lpp_source=images1 \
-a bosinst_data=bid1 -a resolv_conf=rconf1 client1
```
To allocate all resources applicable to stand-alone machines from the NIM resource group res_grp1, to the machine mac1, enter the following command:
```
nim -o allocate -a group=res_grp1 mac1
```
To allocate a stand-alone machine that is named standalone1 to a customer that is named customer1, enter the following command:
```
nim -o allocate -a standalone=standalone1 customer1
```
To allocate a lpp_source that is named lpp_source1 to a customer that is named customer1, enter the following command:
```
nim -o allocate -a lpp_source=lpp_source1 customer1
```

alt_disk_install

To install a mksysb resource all_devices_mysysb to client roundrock, on hdisk4 and hdisk5 by using the image_data resource image_data_shrink, with the debug turned on, enter the following command:
```
nim -o alt_disk_install -a source=mksysb\
-a image_data=image_data_shrink\
-a debug=yes\
-a disk='hdisk4 hdisk5' roundrock
```
To clone a rootvg on client austin to hdisk2, but run phase1 and phase2 only (leaving the /alt_inst file systems mounted), enter the following command:
```
nim -o alt_disk_install -a source=rootvg\
-a disk='hdisk2'\
-a phase=12 austin
```

bos_inst

To install the machine blowfish, by using the resources spot1, images1, bosinst_data1, and rconf1, first allocate the resources by typing:
```
nim -o allocate -a spot=spot1 -a lpp_source=images1 \
-a bosinst_data=bosinst_data1 -a resolv_conf=rconf1 blowfish
```
Then, perform the BOS installation by typing:
```
nim -o bos_inst blowfish
```
To install the machine blowfish while allocating the resources spot1, images1, bosinst_data1, and rconf1 automatically when the bos_inst operation starts, enter the following command:
```
nim -o bos_inst -a spot=spot1 -a lpp_source=images1 \
-a bosinst_data=bosinst_data1 -a resolv_conf=rconf1 blowfish
```
To use the default resources when installing the machine mac1, enter the following command:
```
nim -o bos_inst mac1
```
To install a machine deadfish, with spot1 and lpp_source1 and use an adapter_def resource adapter_def1 to configure secondary adapters, enter the following command:
```
nim -o bos_inst -a spot=spot1 -a lpp_source=lpp_source1 \
  -a adapter_def=adapter_def1 deadfish
```

To install the machine blowfish and accept software license agreements, enter the following command:

nim -o bos_inst -a spot=spot1 -a lpp_source=images1 \
-a accept_licenses=yes -a resolv_conf=rconf1 blowfish

change

Machines on the BLDG905 network use the gateway905 gateway to reach the OZ network. Machines on the OZ network use the gatewayOZ gateway to reach the BLDG905 network. To add a route between two networks that are named BLDG905 and OZ, enter the following command:
```
nim -o change -a routing1="OZ gateway905 gatewayOZ" BLDG905
```
The adapter that is identified by the host name sailfish2.austin.ibm.com is attached to a token ring network. To define a secondary interface for this adapter on the NIM master and instructing NIM to locate the NIM network that represents the attached ethernet network and, if not found, have NIM define a NIM network with subnetmask 255.255.255.128, enter the following command:
```
nim -o change -a if2="find_net sailfish2.austin.ibm.com 0" \
-a net_definition="tok 255.255.255.128" -a ring_speed2=16 master
```
Note: A default name is generated for the network, and no routing information is specified for the new network.
To define default routes for the networks net1 and net2 that use default gateways gw1 and gw2, enter the following commands:
```
nim -o change -a routing1="default gw1" net1
nim -o change -a routing1="default gw2" net2
```
To designate the resources that are defined by the resource group res_grp1 as the set of resources that are always allocated by default during any operation in which these resources are applicable, enter the following command:
```
nim -o change -a default_res=res_grp1 master
```

check

To have NIM check on the usability of a SPOT that is named myspot, enter the following command:
```
nim -o check myspot
```
To check the status of an lpp_source named images, enter the following command:
```
nim -o check images
```

chwpar

To add resource set rs/cpus23 to the resource control attributes for the wpar1 workload partition, enter the following command:

nim -o chwpar -a cmd_flags="-R rset=rs/cpu23" wpar1

create

To create the wpar1 workload partition with host name and specification file resource basic_wpar, enter the following command:
```
nim -o create -a wpar_spec=basic_wpar wpar1
```
To create the wpar1 workload partition with the wpar-specification file resource wpar1_spec, enter the following command:
```
nim -o create -a wpar_spec=wpar1_spec wpar1
```
To create the wpar1 workload partition from the savewpar backup image resource wpar1_backup, enter the following command:
```
nim -o create -a savewpar=wpar_backup wpar1
```

cust

To install a software product into a spot that is named spot1, such that the image for the installable option that is named adt, reside in the lpp_source that is named images, enter the following command:
```
nim -o cust -a lpp_source=images -a filesets=adt spot1
```
To install a software product into a spot spot1, such that the image for the installable option adt, reside in the lpp_source, images, and the installp_bundle, bundle1, contains the name of the installable option, enter the following command:
```
nim -o cust -a lpp_source=images -a installp_bundle=bundle1 spot1
```
To install a software product into a spot spot1, such that the image for the installable option adt, reside on a tape that is in the tape drive that is local to the machine where the spot resides, enter the following command:
```
nim -o cust -a lpp_source=/dev/rmt0 -a filesets=adt spot1
```
To install a software product into a spot spot1, such that the image for the installable option adt, reside on a tape that is in the tape drive that is local to the machine where the spot resides, enter the following command:
```
nim -o cust -a lpp_source=/dev/rmt0 -a filesets=adt spot1
```
To install all fileset updates associated with APAR IX12345, residing on the tape /dev/rmt0 into spot1 and any diskless or dataless clients to which spot1 is currently allocated, enter the following command:
```
nim -F -o cust -afixes=IX12345 -a lpp_source=/dev/rmt0 spot1
```
To update all software installed on the client Standalone1, with the latest updates in the lpp_source named updt_images, enter the following command:
```
nim -o allocate -a lpp_source=updt_images Standalone1
nim -o cust -afixes=update_all Standalone1
```
To install the machine catfish with the contents of the installp_bundle bundle1, first allocate the resources by typing:
```
nim -o allocate -a installp_bundle=bundle1 \
-a lpp_source=images1 catfish
```
Then, perform the cust operation by typing:
```
nim -o cust catfish
```
To update all software that is installed on the client Standalone1, with the latest updates in the lpp_source named updt_images, enter the following command:
```
nim -o cust -a lpp_source=updt_images -a fixes=update_all \
Standalone1
```
To install the machine catfish with the contents of the installp_bundle bundle1, while allocating this resource and the lpp_source images1 when the cust operation runs, enter the following command:
```
nim -o cust -a installp_bundle=bundle1 -a lpp_source=images1 \
catfish
```
To configure secondary adapters on a client machine deadfish, by using the secondary adapter configuration file in the adaper_def resource adapter_def1, enter the following command:
```
  nim -o cust -a adapter_def=adapter_def1 deadfish
```

deactivate

To stop the managed wpar1 workload partition, enter the following command:
```
nim -o deactivate wpar1
```
To force the stop of the managed wpar1 workload partition, enter the following command:
```
nim -Fo deactivate wpar1
```
To stop the managed wpar1 workload partition with more stopwpar command flags to halt after 85 seconds, enter the following command:
```
nim -o deactivate -a cmd_flags="-t 85" wpar1
```

deallocate

To deallocate an lpp_source named images from the stand-alone machine client1, enter the following command:
```
nim -o deallocate -a lpp_source=images client1
```
To deallocate a stand-alone machine that is named idevp9-lp10 from a customer that is named customer1, enter the following command:
```
nim -o deallocate -a standalone=idevp9-lp10 customer1
```

define

To define a resource that is a directory that contains installable images and is on the server altoid and has a path name of /usr/sys/inst.images, and name that resource images, enter the following command:
```
nim -o define -t lpp_source -a server=altoid \
-a location=/usr/sys/inst.images images
```
To create a new SPOT resource named myspot on the NIM master in the /export/exec directory, by using an lpp_source named image, enter the following command:
```
nim -o define -t spot -a server=master -a location=/export/exec \
-a source=images myspot
```
To define a network object named BLDG905, with a subnetmask of 255.255.240.0 and an address of 129.35.129.0, enter the following command:
```
nim -o define -t tok -a snm=255.255.240.0 \
-a net_addr=129.35.129.0 BLDG905
```
To define a mksysb resource mksysb1, from an existing mksysb image that is located in /resources/mksysb.image on the master, enter the following command:
```
nim -o define -t mksysb -a server=master \
-a location=/resources/mksysb.image mksysb1
```
To define a NIM network that is named ATMnet with a subnet mask of 255.255.240 and an address of 129.35.101.0 to represent an ATM network, by using the generic network type, enter the following command:
```
nim -o define -t generic -a snm=255.255.240.0 \
-a net.addr=129.35.101.0 ATMnet
```
To define a machine group named DisklsMacs1 with members that are NIM diskless machines that are named diskls1, diskls2, and diskls3, enter the following command:
```
nim -o define -t mac_group -a add_member=diskls1 \
-a add_member=diskls2 -a add_member=diskls3 DisklsMacs1
```

To define a resource group named DisklsRes1 with resources spot1, root1, dump1, paging1, home1, tmp1, enter the following command:

nim -o define -t res_group -a spot=spot1 -a root=root1 \
-a dump=dump1 -a paging=paging1 -a home=home1 -a tmp=tmp1 \
DisklsRes1

To display the space that is required to define a mksysb resource mksysb2, and create an mksysb image of the client client1, during the resource definition where the image is located in /resources/mksysb.image on the master, enter the following command:
Note: This action shows the space that is required for the operation, mksysb, or resource creation does NOT take place.
```
nim -o define -t mksysb -a server=master \
-a location=/resources/mksysb.image -a source=client1 \
-a mk_image=yes -a size_preview=yes mksysb2
```
To define a mksysb resource mksysb2, and create the mksysb image of the client client1, during the resource definition where the image is in /resources/mksysb.image on the master, enter the following command:
```
nim -o define -t mksysb -a server=master \
-a location=/resources/mksysb.image -a source=client1 \
-a mk_image=yes mksysb2 
```
To define a mksysb resource mksysb2, and create an mksysb image of the client client1, during the resource definition where the mksysb flags used to create the image are -em, and the image is in /resources/mksysb.image on the master, enter the following command:
```
nim -o define -t mksysb -a server=master \
-a location=/resources/mksysb.image -a source=client1 \
-a mk_image=yes -a mksysb_flags=em mksysb2
```
To define a exclude_files resource that is named exclude_file1, located in /resources/mksysb.image on the master, enter the following command:
```
nim -o define -t exclude_files -a server=master \
-a location=/resources/exclude_file1 exclude_file1
```
A machine that is called redfish, hostname redfish_t.lab.austin.ibm.com, has its primary interface that is attached to a token-ring network with ring speed of 16 Megabits. To define redfish as a stand-alone machine in the NIM environment and instructing NIM to locate the name of the network that the machine's primary interface is attached, enter the following command:
```
nim -o define -t stand-alone  -a if1="find_net \
redfish_t.lab.austin.ibm.com 0" -a ring_speed1=16 redfish
```
A machine that is called bluefish, hostname is bluefish_e.lab.austin.ibm.com, has its primary interface that is attached to an ethernet network with cable_type of bnc. To define bluefish as a diskless machine in the NIM environment and instructing NIM to locate the name of the network that the machine's primary interface is attached, and if not found, have NIM define a NIM network with the name ent_net, subnetmask of 255.255.255.128 and default route by using the gateway with hostname lab_gate, enter the following command:
```
nim -o define -t diskless -a if1="find_net \
bluefish_e.lab.austin.ibm.com 0" -a net_definition="ent \
255.255.255.128 lab_gate 0 ent_net" -a cable_type=bnc bluefish
```
Note: Specify 0 in place of the master gateway in the net_definition attribute if a default route for the master exists, otherwise you must specify the master gateway.
To define the /export/nim/adapters directory as a adapter_def resource adapter_def1, on the master, enter the following command:
```
nim -o define -t adapter_def -a server=master \
  -a location=/export/nim/adapters adapter_def1
```
To populate the adapter_def resource with secondary adapter configuration files, run the nimadapters command.
To display the space that is required to define a savevg resource savevg2, and create a savevg image of the client client1, during the resource definition where the image is in /export/nim/savevg on the master and the volume_group to backup is myvg, enter the following command:
```
nim -o define -t savevg -a server=master \
  -a location=/export/nim/savevg/savevg2 -a source=client1 \
  -a mk_image=yes -a size_preview=yes -a volume_group=myvg savevg2
```
Note: This action shows the space that is required for the operation. savevg or resource creation does not take place.
To define a savevg resource savevg2, and create the savevg image of the client client1, during the resource definition where the image is in /export/nim/savevg on the master and the volume_group to backup is myvg, enter the following command:
```
nim -o define -t savevg -a server=master \
-a location=/export/nim/savevg -a source=client1 \
-a mk_image=yes -a volume_group=myvg savevg2
```
To define a savevg resource savevg2, and create a savevg image of the client client1, during the resource definition where the savevg flags used to create the image are -em, and the image is in /export/nim/savevg on the master, enter the following command:
```
nim -o define -t savevg -a server=master \
-a location=/export/nim/savevg -a source=client1 \
-a mk_image=yes -a volume_group=myvg -a savevg_flags=em savevg2
```
To define a vg_data resource my_vg_data, on the master at the location /export/nim, enter the following command:
```
nim -o define -t vg_data -a server=master -a location=/export/nim/my_vg_data my_vg_data
```
To define the wpar1 workload partition that is managed by the yogi managing stand-alone machine with wpar1 as both the host name and the name of the workload partition on the managing system, enter the following command:
```
nim -o define -t wpar -a mgmt_profile1="yogi wpar1" -a if1="find_net wpar1 0" wpar1
```
To define a savewpar resource that is named wpar1backup and create the savewpar image of the yogi workload partition on the sterling server, enter the following command:
```
nim -o define -t savewpar \
   -a server=sterling -a location=/resources/wpar1.image \
   -a source=wpar1 -a mk_image=yes wpar1backup
```
To define a savewpar resource that is named wpar1backup and create the savewpar image of the yogi workload partition on the sterling server, excluding file patterns in the exclude_files resource wparexclude, and passing the flag to the savewpar resource to exclude files and creates a image.data file, enter the following command:
```
nim -o define -t savewpar \
   -a server=sterling -a location=/resources/wpar1.image -a source=wpar1 \
   -a exclude_files=wparexclude -a cmd_flags="-ei" mk_image=yes wpar1backup
```
To define a ios_mksysb resource such as ios_mksysb1, and create the ios_mksysb image of the vios client as vios1, during the resource definition where the image is located in /export/nim/ios_mksysb on the master, enter the following command:
```
nim -o define -t ios_mksysb -a server=master \
-a location=/export/nim/ios_mksysb -a source=vios1 \
-a mk_image=yes ios_mksysb1
```
To define a customer object, enter the following command:
```
nim -o define -t customer -a server=master customer1
```

destroy

To remove the managed wpar1 workload partition from its managing system, enter the following command:
```
nim -o destroy wpar1
```
To force the removal of the managed wpar1 workload partition, enter the following command:
```
nim -Fo destroy wpar1
```

dkls_init

To initialize the environment for a diskless workstation with the name of syzygy, by using the resources spot1, root1, dump1, and paging1, you must allocate the resources by typing:
```
nim -o allocate -a spot=spot1 -a root=root1 -a dump=dump1 \
-a paging=paging1 syzygy
```
Then initialize the resources for the client machine by typing:
```
nim -o dkls_init syzygy
```
To initialize the environment for a diskless workstation with the name of syzygy, enter the following command:
```
nim -o dkls_init syzygy
```
To exclude the member named diskls2 from operations on the machine group DisklsMacs1, and then initialize the remaining members while allocating the diskless resources defined by the resource group named DisklsRes1, enter the following command the following two commands:
```
nim -o select -a exclude=diskls2 DisklsMacs1
nim -o dkls_init -a group=DisklsRes1 DisklsMacs1
```
To initialize the group of diskless machines that are defined by the machine group dtgrp1, while allocating the required and optional resources defined by the resource group dk_resgrp1, when the dkls_init operation runs, enter the following command:
```
nim -o dkls_init -a group=dtgrp1 dk_resgrp1
```

dtls_init

To initialize the environment for a dataless workstation with the name of syzygy, by using the resources spot1, root1, and dump1, first allocate the resources by typing:
```
nim -o allocate -a spot=spot1 -a root=root1 -a dump=dump1 syzygy
```
Then initialize the resources for the client machine by entering the following command:
```
nim -o dtls_init syzygy
```
To initialize the environment for a dataless workstation with the name of syzygy, enter the following command:
```
nim -o dtls_init syzygy
```
To exclude the member named dataless1 from operations on the machine group DatalsMacs1, and then initialize the remaining members while allocating the dataless resources defined by the resource group named DatalsRes1, enter the following command the following two commands:
```
nim -o select -a exclude=datals2 DatalsMacs1
nim -o dtls_init -a group=DatalsMacs1 DatalsRes1
```
To initialize the group of dataless machines defined by the machine group DatalsMacs1, while allocating the required and optional resources defined by the resource group DatalsRes1, when the dtls_init operation runs, enter the following command:
```
nim -o dtls_init -a group=DatalsMacs1 DatalsRes1
```

fix_query

To list information about fixes installed on the client Standalone1 for 20 APAR numbers, create the file /tmp/apar.list with one APAR number per line, as shown:

IX123435
IX54321
IX99999
...

After creating the /tmp/apar.list file, enter the following command:

nim -o define -t fix_bundle -alocation=/tmp/apar.list \
                 -aserver=master fix_bun
nim -o allocate -a fix_bundle=fix_bun Standalone1
nim -o fix_query Standalone1

lppchk

To check fileset version and requisite consistency on the SPOT spot1, enter the following command:
```
nim -o lppchk spot1
```
To verify the file checksums for all packages that begins with the name bos on NIM targets in the group of stand-alone machines macgrp1, and displaying detailed error information and updating the software database to match the actual file checksum when inconsistencies are found, enter the following command:
```
nim -o lppchk -a lppchk_flags='-c -m3 -u' \
-a filesets='bos*' macgrp1
```
Because the lppchk operation runs in the background on group members by default, to view the output from the lppchk operation type:
```
nim -o showlog -a log_type=lppchk macgrp1
```

lppmgr

To list the names of duplicate base level filesets that must be removed from lpp_source1 with space usage information, enter the following command:
```
nim -o lppmgr -a lppmgr_flags="-lsb" lpp_source1
```
To remove duplicate base and update filesets and superseded updates from lpp_source1, enter the following command:
```
nim -o lppmgr -a lppmgr_flags="-rbux" lpp_source1
```
To remove all non-SIMAGES (filesets that are not required for a bos install) from lpp_source1, enter the following command:
```
nim -o lppmgr -a lppmgr_flags="-rX" lpp_source1
```
To remove all language support except C from lpp_source1, enter the following command:
```
nim -o lppmgr -a lppmgr_flags="-r -k C" lpp_source1
```

lswpar

To list the characteristics of the managed wpar1 workload partition, enter the following command:
```
nim -o lswpar wpar1
```
To list the network characteristics of the managed wpar1 workload partition, enter the following command:
```
nim -o lswpar -a cmd_flags="-N" wpar1
```
To list the general characteristics of the workload partitions managed by the global1 stand-alone system, enter the following command:
```
nim -o lswpar -a cmd_flags="-G" global1
```

maint

To cleanup from an interrupted software installation on a spot spot1, enter the following command:
```
nim -o maint -a installp_flags="-C" spot1
```
From the master, to clean up from an interrupted software installation on a stand-alone machine stand1, enter the following command:
```
nim -o maint -a installp_flags="-C" stand1
```

maint_boot

To enable the NIM stand-alone client stand1 to boot in maintenance mode, enter the following command:

nim -o maint_boot stand1

This command sets up the maintenance boot operation, but you must initiate the network boot locally from stand1.

remove

To remove a resource that is named dump_files, enter the following command:

nim -o remove dump_files

showlog

To view the boot logs of the machines that are defined by the group DisklsMacs1, enter the following command:

nim -o showlog -a log_type=boot DisklsMacs1

showres

To show the contents of the configure script that is named script1, enter the following command:
```
nim -o showres script1
```
To show the contents of the bosinst.data resource bosinst_data1, enter the following command:
```
nim -o showres bosinst_data1
```
To list all the filesets in the lpp_source lpp_source1, enter the following command:
```
nim -o showres lpp_source1
```
To list all the filesets in the lpp_source lpp_source1 relative to what is installed on the machine machine1, enter the following command:
```
nim -o showres -a reference=machine1 lpp_source1
```
To list all the problems that are fixed by software on the lpp_source lpp_source1, use:
```
nim -o showres -a instfix_flags="T" lpp_source1
```
To show the contents of the secondary adapter configuration file in the adapter_def resource adapter_def1, for client deadfish, enter the following command:
```
nim -o showres -a client=deadfish adapter_def1
```
To show the contents of every secondary adapter configuration file in the adapter_def resource that is named adapter_def1, enter the following command:
```
nim -o showres adapter_def1
```
To show the contents of the savevg resource savevg1, enter the following command:
```
nim -o showres savevg1
```

syncwpar

To synchronize the software of the managed wpar1 workload partition with its managing system, enter the following command:
```
nim -o syncwpar wpar1
```
To synchronize the software of all the workload partitions managed by the global1 stand-alone system, enter the following command:
```
nim -o syncwpar -a cmd_flags="-A" global1
```

update

To add all the filesets on /dev/cd0 to lpp_source1, enter the following command:
```
nim -o update -a packages=all -a source=/dev/cd0 lpp_source1
```

To add the bos.games 7.1.0.0 and bos.terminfo filesets to lpp_source1, enter the following command:

nim -o update -a packages="bos.games 7.1.0.0 bos.terminfo" \
  -a source=/dev/cd0 lpp_source1

To remove bos.games from lpp_source1, enter the following command:

nim -o update -a rm_images=yes -a packages="bos.games" lpp_source1

To recover the missing SIMAGES for lpp_source1 from the AIX Installation CD, enter the following command:
```
nim -o update -a recover=yes -a source=/dev/cd0 lpp_source1
```

updatios

To install fixes or to update VIOS with the vioserver1 NIM object name to the latest maintenance level, enter the following command:
```
nim -o updateios -a lpp_source=lpp_source1 -a preview=no vioserver1
```
The updates are stored in lpp_source and lpp_source1 files.

Note: The updateios operation runs a preview during installation. Running the updateios operation from NIM runs a preview unless the preview flag is set to no. During the installation, you must run a preview when you use the updateios operation with updatios_flags=-install. With the preview, you can check whether the preview installation is running accurately before you proceed with the VIOS update.
To reject fixes for a VIOS with the vioserver1 NIM object name, enter the following command:
```
nim -o updateios -a updateios_flags=-reject vioserver1
```
To clean up partially installed updates for a VIOS with the vioserver1 NIM object name, enter the following command:
```
nim -o updateios -a updateios_flags=-cleanup vioserver1
```
To commit updates for a VIOS with the vioserver1 NIM object name, enter the following command:
```
nim -o updateios -a updateios_flags=-commit vioserver1
```
To remove a specific update such as update1 for a VIOS with the vioserver1 NIM object name, enter the following command:
```
nim -o updateios -a updateios_flags=-remove-a filesets="update1" vioserver1
```
To remove updates for a VIOS with the vioserver1 NIM object name by using an installp_bundle bundle1, where bundle1 contains the updates to be removed, enter the following command:
```
nim -o updateios -a updateios_flags=remove -a installp_bundle=bundle1 vioserver1
```

Files

Table 4. Files
Item	Description
/etc/niminfo	Contains variables that are used by NIM.