./usr/040755 000000 000000 00000000000 10046301501 012335 5ustar00rootsystem000000 000000 ./usr/lib/040755 000000 000000 00000000000 10046301370 013107 5ustar00rootsystem000000 000000 ./usr/lib/boot/040755 000000 000000 00000000000 10046301370 014052 5ustar00rootsystem000000 000000 ./usr/lib/boot/network/040664 000000 000000 00000000000 06674372130 015560 5ustar00rootsystem000000 000000 ./usr/lib/boot/network/rc.dd_boot100555 000000 000000 00000031173 06460446324 017524 0ustar00rootsystem000000 000000 # @(#)18 1.19.1.12 src/bos/usr/lib/boot/network/rc.dd_boot.sh, cmdnim, bos43D, 9803A_43D 1/14/98 11:48:15 # IBM_PROLOG_BEGIN_TAG # This is an automatically generated prolog. # # bos43D src/bos/usr/lib/boot/network/rc.dd_boot.sh 1.19.1.12 # # Licensed Materials - Property of IBM # # (C) COPYRIGHT International Business Machines Corp. 1993,1994 # All Rights Reserved # # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # IBM_PROLOG_END_TAG # # COMPONENT_NAME: CMDNIM # # FUNCTIONS: make_dataless # # ORIGINS: 27 # # # (C) COPYRIGHT International Business Machines Corp. 1993, 1996 # All Rights Reserved # Licensed Materials - Property of IBM # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # # This script is to be run as a "dot" script from within rc.boot only. # Function: diskless/dataless configuration nim_status() { # update the "info" attribute on the NIM master /usr/sbin/nimclient -o change -a force=yes -a ignore_lock=yes -a info="$*" } fatal_error() { typeset led=${1} shift nim_status "${*:-fatal network boot error}" loopled ${led} } config_network() { # # Function: configure network # ${NIM_DEBUG} ifconfig lo0 inet 127.0.0.1 up ifconfig $LDEV inet $CLIENT_IPADDR up $SUBMASK [ "$?" -ne 0 ] && return 1 # set up route tables [ "$BOOT_GATE_IP" ] && route -v add $BOOT_SERV_IP $BOOT_GATE_IP [ -n "${ROUTES}" ] && { for route_args in $ROUTES do OIFS="$IFS"; IFS=':' set -- $route_args IFS="$OIFS" # verify that there are 3 arguments [ $# -ne 3 ] && continue route -v add -net $1 -netmask $2 $3 || return 2 done } return 0 # End of config_network function. } DEFAULT_DISK=hdisk0 # the default physical disk to use for local paging make_dataless() { ${NIM_DEBUG} nim_status "creating a local paging device" ${SHOWLED} 0x616 [ -z "${DTLS_VG_DISK}" ] && DTLS_VG_DISK=${DEFAULT_DISK} # clear the ipl record on this disk mkboot -c -d /dev/${DTLS_VG_DISK} # Determine largest physical partition size required # by the target disks. LRGST_PRTN_SZ=$(bootinfo -P 0 -s ${DTLS_VG_DISK}) VGNAME=$(mkvg -f -d 8 -s ${LRGST_PRTN_SZ} ${DTLS_VG_DISK}) [ $? != 0 ] && fatal_error 0x617 "mkvg failed on ${DTLS_VG_DISK}" varyonvg -n ${VGNAME} [ $? != 0 ] && fatal_error 0x617 "varyonvg failed for ${VGNAME}" syncvg -v ${VGNAME} & syncvg1_pid=$! cp /mnt/etc/swapspaces /etc [ $? != 0 ] && fatal_error 0x617 "copy of swapspaces failed" # Calculate paging space using largest number of partitions required # by target disk and the paging space specified OR the size # of real memory. if [ -n "${DTLS_PAGING_SIZE}" ] then # Use the paging space specified. It was specified, we assume, # in 4Meg partitions so we'll calculate the value in bytes # for subsequent calculations. (( TMP_PGSP_MEG=${DTLS_PAGING_SIZE}*4096 )) else # No paging space specified. # Use size of real memory for page space calculation. (( TMP_PGSP_MEG=$(bootinfo -r) )) fi (( DTLS_PAGING_SIZE=${TMP_PGSP_MEG}/(${LRGST_PRTN_SZ}*1024) )) SWAP_DEV=$(mkps -s${DTLS_PAGING_SIZE} -n -a ${VGNAME}) [ $? != 0 ] && fatal_error 0x617 "mkps failed on ${VGNAME}" cp /etc/swapspaces /mnt/etc/swapspaces [ $? != 0 ] && fatal_error 0x617 "restore copy of swapspaces failed" [ -n "${DTLS_LOCAL_FS}" ] && { # if this variable is not null, then we need to create /home # and/or /tmp. Remember that the NFS /usr filesystem is mounted # over /usr, but that the NFS root filesystem is mounted over /mnt. # That is why we must copy /etc/filesystem to the ram filesystem # and then back. This will only work for filesystems that already # have the mountpoints in the NFS root filesystem. nim_status "creating a local /home and/or /tmp" cp /mnt/etc/filesystems /etc cp /mnt/sbin/helpers/v3fshelper /sbin/helpers for fs in ${DTLS_LOCAL_FS} do case ${fs} in home) FS_SIZE=8192;; tmp) FS_SIZE=16384;; *) continue;; esac crfs -v jfs -m /${fs} -g ${VGNAME} -A yes -p rw \ -a size=${FS_SIZE} if [ ${fs} = tmp ] then mount /tmp chmod a-s /tmp chmod 1777 /tmp chown 2:2 /tmp umount /tmp fi done cp /etc/filesystems /mnt/etc } # Copy LVM information to the hardfile cd / find /etc/vg -print | cpio -updmv /mnt [ $? != 0 ] && fatal_error 0x617 "failed to copy lvm info to hardfile" # Make sure we save base cust info [[ -s /etc/basecust ]] && cp /etc/basecust /mnt/etc/basecust # inform NIM that this has succeeded /usr/sbin/nimclient -R success } # # ----------------------- PHASE ONE # ${NIM_DEBUG} case "$PHASE" in 1) # update the Mstate ln -s /SPOT/usr/sbin/nimclient /usr/sbin/nimclient ln -s /SPOT/usr/bin/chmod /usr/bin/chmod ln -s /SPOT/usr/bin/alog /usr/bin/alog # NIM's shared library is not needed until now so it was not included # in the boot image. Link the library from the SPOT to the RAM # filesystem. ln -s /SPOT/usr/lib/libnim.a /usr/lib/libnim.a /usr/sbin/nimclient -S booting set +x /SPOT/usr/bin/rm /lib /sbin/helpers/v3fshelper /usr/bin/tftp cp /SPOT/usr/sbin/rmdev /usr/sbin cp /SPOT/usr/bin/rm /usr/bin /SPOT/usr/bin/mkdir -p /lib/netsvc # we removed /lib, which was a symlink to /usr/lib, and replaced it # with a real directory. now we populate that real directory with # hard links to the files in /usr/lib. this enables us to access the # libraries in the RAM filesystem when /usr is overmounted. This # is a good thing because we do not want to have multiple copies # of the same library loaded into memory during boot! ln /usr/lib/* /lib ln /usr/lib/netsvc/* /lib/netsvc ${NIM_DEBUG} ${SHOWLED} 0x610 mount -o llock ${ROOT} /mnt [ $? -ne 0 ] && \ fatal_error 0x611 "unable to NFS mount the root directory at ${ROOT}" ${SHOWLED} 0x612 # copy the niminfo file into the root cp /SPOT/niminfo /mnt/etc/niminfo if [ -s /mnt/etc/basecust ] then cp /mnt/etc/basecust /etc cp /SPOT/usr/lib/boot/restbase /usr/sbin cp /SPOT/usr/bin/uncompress /usr/bin fi ln /usr/sbin/mount /usr/sbin/umount ln /usr/sbin/mount /etc/umount nim_status "network boot phase 1" umount allr # unconfigure network services and devices and let cfgmgr do it the # right way. this also resets device information to what it was # before the system was shutdown if /etc/basecust is non-null ifconfig ${LDEV} down ifconfig ${LDEV} detach ifconfig lo0 down route -f # If there was a basecust file, then need to unconfigure all of the # devices in the hardware tree so they can be configured using the # basecust data. if [ -s /etc/basecust ] then rmdev -l sys0 -R restbase -o /etc/basecust rm -f /etc/basecust /usr/bin/restbase /usr/bin/uncompress fi rm -f /usr/sbin/rmdev # run config manager to configure only the network boot devices and # their parents. we are limited to only those devices because the # boot RAM filesystem contains a subset of device configuration files cfgmgr -f -v # check the physical boot device name again, in case the basecust data # added an entry that conflicts with what was there before basecust PHY_BOOT_DEV=`bootinfo -b` pdev_to_ldev ${SHOWLED} 0x606 config_network case $? in 1) fatal_error 0x607 "unable to configure the primary network interface";; 2) fatal_error 0x613 "unable to add routes";; esac rm -fr /usr/lib/drivers /usr/lib/methods/!(showled) /usr/lib/microcode \ /usr/sbin/cfgmgr /usr/sbin/ifconfig /usr/sbin/route ${NIM_DEBUG} LIBPATH=/lib; export LIBPATH ${SHOWLED} 0x610 mount -r ${SPOT} /usr [ $? -ne 0 ] && \ fatal_error 0x611 "unable to NFS mount the SPOT at location ${SPOT}" strload -f /dev/null # run cfgmgr to configure remaining devices now that we have the # device support in /usr from the remotely mounted filesystem cfgmgr -f -v mount -o llock ${ROOT} /mnt [ $? -ne 0 ] && \ fatal_error 0x611 "unable to NFS mount root directory at location ${ROOT}" # configure paging - local or NFS network # the grep searches for lines that do not have an asterisk as the # first character and contain "/dev". the sed deletes the lines that # contain "swapnfs" and strips away all characters preceding the "/dev" local_swap=$(grep "^[^*].*/dev" /mnt/etc/swapspaces | \ sed -e "/.*\/dev\/swapnfs.*/d; s/.*\(\/dev.*\)/\1/") # Start local paging if [ -n "$local_swap" ] then nim_status "configuring local paging device" for paging in $local_swap do ${SHOWLED} 0x614 # get the volume group name name=${paging##*/} vgname=$(odmget -qname=$name CuDv | \ sed -n "s/.*parent *= *\"\(.*\)\"/\1/gp") if [ -z "$vgname" ] then ${SHOWLED} 0x615 continue fi # make the /dev entries which are found # in the client's root dev_vg=$(ls -l /mnt/dev/$vgname 2>/dev/null) if [ -n "$dev_vg" ] then if [ ! -c /dev/$vgname ] then # volume group not present yet # activate it # major number is field 5 # minor is field 6 set -- $dev_vg # remove the "," after # the major number major=$(echo $5 | sed -e "s/,//g") # make the /dev entry mknod /dev/$vgname c $major $6 # varyon the volume group varyonvg -fn $vgname || ${SHOWLED} 0x615 syncvg -v $vgname & syncvg2_pid=$! fi # make the paging device entry dev_ps=$(ls -l /mnt$paging) if [ -n "$dev_ps" ] then # major number is field 5 # minor is field 6 set -- $dev_ps # remove the "," after # the major number major=$(echo $5 | sed -e "s/,//g") # make the /dev entry mknod $paging b $major $6 # check for local dump image # if present, upload it to the server BS=8192 dump_info=/tmp/dump.info dump_mnt=/tmp/dump dump_file=${dump_mnt}/dump # is there a dump image to upload? sysdumpdev -z >${dump_info} 2>&1 if [[ -n "${DUMP}" ]] && [[ -s ${dump_info} ]] then # dump info in this format: # set -- $( cat ${dump_info} ) num_bytes=${1} dump_device=${2} # how many blocks? (( num_blocks=num_bytes/BS )) (( (num_bytes%BS) > 0 )) && (( num_blocks=num_blocks+1 )) # mount the remote dump directory mkdir ${dump_mnt} if mount ${DUMP} ${dump_mnt} then # upload the dump image dd if=${dump_device} of=${dump_file} bs=${BS} \ count=${num_blocks} unmount ${dump_mnt} fi fi # swapon the paging device swapon $paging || ${SHOWLED} 0x615 else ${SHOWLED} 0x615 fi else ${SHOWLED} 0x615 fi done # Copy LVM information to the hardfile cd / find /etc/vg -print | cpio -updmv /mnt fi # local_swap # if the dataless conversion flag is set, call a function to do it [ -n "${NIM_MK_DATALESS}" ] && make_dataless remote_swap=$(grep "^[^*]remdev" /mnt/etc/swapspaces | \ sed -e "s/.*= *\(.*\)/\1/") # Start NFS remote paging # configure the remote paging devices DEFAULT_IFS=$IFS for i in $remote_swap do nim_status "configuring remote paging device" ${SHOWLED} 0x618 IFS=':' set -- $i IFS=$DEFAULT_IFS SWAPHOST=$1 SWAPFILE=$2 SWAPDEV=${SWAPFILE##*/} if [ -z "$(odmget -qname=$SWAPDEV CuDv)" ] then # device doesn't exist - create it cat <<- EOF > /tmp/swapnfs CuDv: name = $SWAPDEV status = 0 chgstatus = 1 PdDvLn = swap/nfs/paging EOF odmadd /tmp/swapnfs # change the paging attributes /usr/lib/methods/chggen -l $SWAPDEV -a \ "swapfilename=$SWAPFILE hostname=$SWAPHOST" || \ ${SHOWLED} 0x619 fi /usr/lib/methods/cfgswpnfs -l $SWAPDEV || ${SHOWLED} 0x619 swapon /dev/$SWAPDEV && RC=0 || ${SHOWLED} 0x619 done # remote_swap ${SHOWLED} 0x620 # Copy special files to the hardfile /usr/lib/boot/mergedev # Copy ram disk repository customized data to disk cp /etc/objrepos/Cu* /mnt/etc/objrepos # copy the client's /etc/filesystems to the RAM filesystem cp /mnt/etc/filesystems /mnt/etc/hosts /etc # unmount all of the remote filesystems nim_status "network boot phase 2" # ensure we can access usr/lib after we mount the root. /usr/bin/ln -fs /../usr/lib /mnt/usr/lib wait $syncvg1_pid $syncvg2_pid /etc/umount -f allr ;; # # ----------------------- PHASE TWO # 2) ${SHOWLED} 0x610 # change SHOWLED just in case the mount of / succeeds and the mount # of /usr fails because /usr will be empty SHOWLED=/../usr/lib/methods/showled; export SHOWLED mount -f -t dd_boot [ $? -ne 0 ] && fatal_error 0x611 "unable to mount -f -t dd_boot" slibclean # clean up unused shared libraries SHOWLED=/usr/lib/methods/showled; export SHOWLED # set the client's hostname. this makes NFS services happy. hostname ${NIM_HOSTNAME} ${SHOWLED} 0x553 nim_status "network boot phase 3" ;; esac r/bin/rm /usr/bin /SPOT/usr/bin/mkdir -p /lib/netsvc # we removed /lib, which was a symlink to /usr/lib, and replaced it # with a real directory. now we populate that real directory with # hard links to the files in /usr/lib. this enables us to access the # libraries in the RAM filesystem when /usr is overmounted. This # is a good thing because we do not want to have multiple c./usr/lib/boot/network/rc.bos_inst100555 000000 000000 00000007402 06470235444 017730 0ustar00rootsystem000000 000000 # @(#)19 1.36 src/bos/usr/lib/boot/network/rc.bos_inst.sh, cmdnim, bos43D, 9806A_43D 2/9/98 12:52:22 # # COMPONENT_NAME: CMDNIM # # FUNCTIONS: # mount_from_list # # ORIGINS: 27, 83 # # # (C) COPYRIGHT International Business Machines Corp. 1993, 1995, 1996 # All Rights Reserved # Licensed Materials - Property of IBM # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # LEVEL 1, 5 Years Bull Confidential Information # # This script is to be run as a "dot" script from within rc.boot only. # Function: BOS installation configuration on network booted machine. # NOTE: Since the rc.diag file is very similar to this file, please check # to see if changes made to either file are appropriate for the other. mount_from_list() { ${NIM_DEBUG} # Mount anything else from the info file # format of each stanza is: # :: if [ -n "${NIM_MOUNTS}" ] then ${SHOWLED} 0x610 OIFS="$IFS" for mount_args in ${NIM_MOUNTS} do IFS=':' set -- ${mount_args} IFS="$OIFS" # make sure local mount point exists if [ ! -d "${3}" ] then /SPOT/usr/bin/mkdir -p ${3} || loopled 0x625 fi # Update the client info field to report that we # are mounting a resource. /SPOT/usr/sbin/nimclient -o change -a force=yes \ -a ignore_lock=yes \ -a info="LED 610: mount $1:$2 $3" mount $1:$2 $3 if [[ "$?" -ne 0 ]] then # Update the client info field to report that # the mount failed. /SPOT/usr/sbin/nimclient -o change \ -a force=yes \ -a ignore_lock=yes \ -a info="LED 611: failure: mount $1:$2 $3" loopled 0x611 fi done # Blank out the client info field so it does not look # like a mount hung. /SPOT/usr/sbin/nimclient -o change -a force=yes \ -a ignore_lock=yes -a info="" fi } ##################### MAIN ######################## # # ----------------------- PHASE ONE # ${NIM_DEBUG} case "$PHASE" in 1) # update the Mstate # We need the NIM library so make it available. /SPOT/usr/sbin/nimclient -S booting mount_from_list ${SHOWLED} 0x622 set +x /SPOT/usr/bin/rm -fr /etc/init /usr/bin /usr/lib/boot /usr/lib/drivers \ /usr/lib/microcode /usr/lib/netsvc /usr/sbin /SPOT/usr/bin/ln -s /SPOT/usr/* /usr ln -fs /SPOT/usr/lib/!(libbind.a|libc.a|libs.a|libnim.a) /usr/lib ln -s /SPOT/usr/lib/boot/ssh /etc/init ${NIM_DEBUG} # link necessary methods from the SPOT /SPOT/usr/lib/boot/network/link_methods strload -f /dev/null cfgmgr -f -v ${SHOWLED} 0x622 set +x # now link to the full databases ln -fs /usr/lib/objrepos/* /etc/objrepos ln -s /SPOT/usr/lib/methods/cfgcon /SPOT/usr/lib/methods/startlft \ /SPOT/usr/lib/methods/starttty /usr/lib/methods ${NIM_DEBUG} /SPOT/usr/lib/boot/network/link_methods export DEV_PKGNAME=ALL cfgmgr -s -v ${SHOWLED} 0x622 ;; # # ----------------------- PHASE TWO # 2) set +x unset fd_invoker loopled shift $# rm -f /sbin/rc.boot ${NIM_DEBUG} # set TCP timeouts to reasonable values (default is 2 hours!!!) /SPOT/usr/sbin/no -o tcp_keepintvl=150 /SPOT/usr/sbin/no -o tcp_keepidle=1200 # the next three lines are only for testing. for actual installs, # these three lines will be replaced by the exec of bi_main # /usr/lib/methods/cfgcon # PS1='RAMFS> '; export PS1 # exec /usr/bin/ksh # Following object classes are required to run the diagnostic pre-test # on disks in rootvg before install begins. # So - Link over the empty object classes for i in CDiagDev TMInput MenuGoal FRUB FRUs DAVars CDiagAtt CDiagAtt.vc do cp /usr/lpp/diagnostics/obj/$i /etc/objrepos/$i done mkdir -p /etc/lpp/diagnostics/data ${SHOWLED} 0xfff exec /usr/lpp/bosinst/bi_main ;; esac F odmadd /tmp/swapnfs # change the paging attributes /usr/lib/methods/chggen -l $SWAPDEV -a \ "swapfilename=$SWAPFILE hostname=$SWAPHOST" || \ ${SHOWLED} 0x619 fi /usr/lib/methods/cfgswpnfs -l $SWAPDEV || ${SHOWLED} 0x619 swapon /./usr/lib/boot/network/rc.diag100555 000000 000000 00000011575 07332125774 017024 0ustar00rootsystem000000 000000 # @(#)78 1.24.1.1 src/bos/usr/lib/boot/network/rc.diag.sh, diagsup, bos43X, x2001_31A7 7/31/01 15:02:38 # IBM_PROLOG_BEGIN_TAG # This is an automatically generated prolog. # # bos43X src/bos/usr/lib/boot/network/rc.diag.sh 1.24.1.1 # # Licensed Materials - Property of IBM # # (C) COPYRIGHT International Business Machines Corp. 1993,2001 # All Rights Reserved # # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # IBM_PROLOG_END_TAG # # COMPONENT_NAME: CMDDIAG # # FUNCTIONS: # mount_from_list # # ORIGINS: 27 # # This script is to be run as a "dot" script from within rc.boot only. # Function: BOS installation configuration on network booted machine. # mount_from_list() { ${NIM_DEBUG} # Mount anything else from the info file # format of each stanza is: # :: if [ -n "${NIM_MOUNTS}" ] then ${SHOWLED} 0x610 OIFS="$IFS" for mount_args in ${NIM_MOUNTS} do IFS=':' set -- ${mount_args} IFS="$OIFS" # make sure local mount point exists if [ ! -d "${3}" ] then /SPOT/usr/bin/mkdir -p ${3} || loopled 0x625 fi mount $1:$2 $3 || loopled 0x611 done fi } ##################### MAIN ######################## # # ----------------------- PHASE ONE # ${NIM_DEBUG} case "$PHASE" in 1) # update the Mstate /SPOT/usr/sbin/nimclient -S booting mount_from_list ${SHOWLED} 0x622 set +x /SPOT/usr/bin/rm -fr /etc/init /usr/bin /usr/lib/boot /usr/lib/drivers \ /usr/lib/microcode /usr/lib/netsvc /usr/sbin /SPOT/usr/bin/ln -s /SPOT/usr/* /usr ln -fs /SPOT/usr/lib/!(libbind.a|libs.a|libnim.a|libdiag.a) /usr/lib ln -fs /SPOT/usr/lpp/diagnostics/lib/libdiagcd.a /usr/lib/libdiag.a ln -s /SPOT/usr/lib/boot/ssh /etc/init ${NIM_DEBUG} strload -f /dev/null cfgmgr -f -v ${SHOWLED} 0x622 set +x # now link to the full databases ln -fs /usr/lib/objrepos/* /etc/objrepos ln -s /SPOT/usr/lib/methods/cfgcon /SPOT/usr/lib/methods/startlft \ /SPOT/usr/lib/methods/starttty /usr/lib/methods ${NIM_DEBUG} # link necessary methods from SPOT /SPOT/usr/lib/boot/network/link_methods cfgmgr -s -v ln -s /SPOT/usr/lib/methods/* /usr/lib/methods ${SHOWLED} 0x622 ;; # # ----------------------- PHASE TWO # 2) set +x unset fd_invoker loopled shift $# rm -f /sbin/rc.boot # configure the console /usr/lib/methods/cfgcon ${SHOWLED} 0xfff # copy the empty diagnostic object classes over to # the RAM filesystem from the remotely mounted system. for i in CDiagDev TMInput MenuGoal FRUB FRUs DAVars CDiagAtt CDiagAtt.vc do cp /usr/lpp/diagnostics/obj/$i /etc/objrepos/$i done mkdir -p /etc/lpp/diagnostics/data # If Graphics console, need rcm started /usr/lib/methods/startrcm >/dev/null 2>&1 if [ -x /usr/lib/methods/cfggxme ] then /usr/lib/methods/cfggxme -l gxme0 >/dev/null 2>&1 fi /usr/lib/methods/cfgrcm -l rcm0 >/dev/null 2>&1 # # RSPC and CHRP architecture only - start errdemon, sleep, then kill it. # This logs any errors that might have occurred since previous boot. # architecture=`bootinfo -a` if [ "$architecture" = "3" -o "$architecture" = "2" ] ; then echo Starting errdemon # Copy over files needed for errdemon. cp /SPOT/usr/lpp/bos/inst_root/etc/objrepos/SWservAt /etc/objrepos cp /SPOT/usr/lpp/bos/inst_root/etc/objrepos/SWservAt.vc /etc/objrepos cp /SPOT/usr/lpp/bos/inst_root/var/adm/ras/errtmplt /var/adm/ras cp /SPOT/usr/lpp/bos/inst_root/var/adm/ras/codepoint.cat /var/adm/ras /SPOT/usr/lib/errdemon -s 16384 -B 8192 >/dev/null 2>&1 /usr/bin/sleep 2 errdemonpid=`/usr/bin/ps -ef -o ruser,pid,ppid=parent,args | cut -c 1-90 | awk '$4~/^.*\/errdemon$/||$4~/errdemon/{print $2}'` if [ -n "$errdemonpid" ] ; then /usr/bin/kill $errdemonpid >/dev/null 2>&1 fi fi # # determine if there are any adapters with multiple # personalities. If so, configure the device to allow # odm to be properly populated. Then unconfigure the # device. Currently this only affects some ethernet # adapters and some token-ring adapters. # > /tmp/diag_cudv > /tmp/diag_devices odmget -q"PdDvLn=adapter/pci/14100401 AND status=0" CuDv>>/tmp/diag_cudv odmget -q"PdDvLn=adapter/pci/23100020 AND status=0" CuDv>>/tmp/diag_cudv odmget -q"PdDvLn=adapter/pci/14103e00 AND status=0" CuDv>>/tmp/diag_cudv cat /tmp/diag_cudv|\ awk '$1 == "name" { gsub("\"","",$3) print $3 >> "/tmp/diag_devices"}' while read dev do if [[ -n $dev ]] ; then mkdev -l $dev > /dev/null 2>&1 rmdev -l $dev > /dev/null 2>&1 fi done /dev/console 2>&1 ;; esac ot" slibclean # clean up unused shared libraries SHOWLED=/usr/lib/methods/showled; export SHOWLED # set the client's hostname../usr/lib/boot/network/link_methods100555 000000 000000 00000006405 07206760145 020166 0ustar00rootsystem000000 000000 # @(#)94 1.7 src/bos/usr/lib/boot/network/link_methods.sh, cmdnim, bos43V, v2000_47B3 11/13/00 14:59:33 # IBM_PROLOG_BEGIN_TAG # This is an automatically generated prolog. # # bos43V src/bos/usr/lib/boot/network/link_methods.sh 1.7 # # Licensed Materials - Property of IBM # # Restricted Materials of IBM # # (C) COPYRIGHT International Business Machines Corp. 1996,2000 # All Rights Reserved # # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # IBM_PROLOG_END_TAG # # COMPONENT_NAME: CMDNIM # # FUNCTIONS: link_methods # # ORIGINS: 27 # # # (C) COPYRIGHT International Business Machines Corp. 1996 # All Rights Reserved # Licensed Materials - Property of IBM # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # ##################### MAIN ######################## set +x # This function is called for both a bos_inst and a diag network boot. # This function creates links for selected device types and classes. # This provides a means to control which devices are configured, which # saves time and system resources. Links are from the remotely mounted # filesystem which is mounted over /SPOT to the /usr/lib/methods directory. if [[ ${RC_CONFIG} = /etc/rc.bos_inst ]] then # get required methods for bos_inst boot # link methods for disks, pdisks, and LVM and their possible parents # link methods for tapes and their possible parents # link methods for diskette and keyboard and their possible parents # link methods for tty and lft and their possible parents # link methods for graphics adapters (Common Character Mode) # and their possible parents # link methods for devices having "link_meth" attributes and their # possible parents (default action - no command flag to get this) # link all methods identified by a "load_module" attribute /SPOT/usr/lib/boot/network/link_meth -c disk -c pdisk -c lvm -c tape -c diskette -c keyboard -c tty -c lft -g -m -r "/SPOT" else # get required methods for diag boot # link methods for disk and pdisk and their possible parents # link methods for tape and possible parents # link methods for cdrom and possible parents # link methods for rwoptical and possible parents # link methods for diskette and keyboard and their possible parents # link methods for tty and lft and their possible parents # link methods for graphics adapters (full function graphics mode) # and their possible parents # link methods for devices having "link_meth_diag" attributes and # their possible parents # link methods for devices having "link_meth" attributes and their # possible parents (default action - no command flag to get this) # link all methods identified by a "load_module" attribute /SPOT/usr/lib/boot/network/link_meth -c disk -c pdisk -c tape -c cdrom -c rwoptical -c diskette -c keyboard -c tty -c lft -G -d -m -r "/SPOT" fi # Now see if there is a platform specific link_methods script to run # get the platform platform=`/SPOT/usr/sbin/bootinfo -p` # call platform specific link_methods if it exists if [[ -s /SPOT/usr/lib/boot/network/link_methods_${platform} ]] then /SPOT/usr/lib/boot/network/link_methods_${platform} fi exit 0 t_root/etc/objrepos/SWservAt /etc/objrepos cp /SPOT/usr/lpp/bos/inst_root/etc/objrepos/SWservAt.vc /etc/objrepos cp /SPOT/usr/lpp/bos/inst_root/var/adm/ras/errtmplt /var/adm/ras cp /SPOT/usr/lpp/bos/inst_root/var/adm/ras/codepoint.cat /var/adm/./usr/lib/boot/network/link_meth100555 000000 000000 00000015752 07255453021 017461 0ustar00rootsystem000000 000000 :fH l1L.text .datal@.bssll.loader<"$|nx|#x|+x|1B(9 e)-*@H`H0HA|nxAA| QN!A89}sx}{x~xH`,Ab H9A| @__startb|,!HAcA}hcCN!Ab ,Ac|CN!Ab,Ac|CN!Ab,Ac|CN!Ab,Ac|CN!AH8!@}N 8!@N A__threads_init,4A L| N |`;,!c88A| H A8c( ,LBAcH ݀A`d8a@H `Dc ,8a@@<|.H `,;;8a@At |@ |.Kc8@H `} 0T:H ـA,} @8`H A} T:0!.X8!P}8`N K A@ save_method0 |P!`e08a@H AbX8@8@H A,,@$8`H 9AD0H8`AD0T(4|T02H ̀A,@8`H ݀A8@T(4|(T02|0`@8H Y`8` 8! }N 8! }N A add_device|}&P;:!`aL;;c::;@b;PcH qA,`tA:`:@"dhl8Tz(|q.,G|| AHN ;W8cH A,p`||.@~.:s:RH<.:s:RH,:H$:bH; HoH;aLP8 H A,`tA8Tz(|q.KLH A.D:@:8a@8H AbX8@8@88H A,aT8`@ H A@,An~`"V`(4|T02H iA,n@8`H yAn@T(4| T02T(4| T02|cTH `naT8@H A:|@8a@8K ,A88a@H`b|8@8@88H A,`v@8`HɀA@:,@(: bK%@:|:xbAb8@H ]A8$8a@H`b|8@8@88H A,`v@8`HAA@:,@(: bK@:|:xbAb8@H ՀA,A888a@Hm`b|8@8@88H yA,`w@8`HA@:,@(: bK @:|:xbAb8@H EA:,@|:,:,:b@H:@,||`HA0||`H`,:s|:RAA8a@|8THAb8@8@88H }A,`s@8`HA@,@br:2 ,:9b#@L|zH!`HA<|zH `,:|9b#AA b#K@:|:R\@:2 ,:Kbc8@HـA:|::@,:bK, @;::c:@D,A |`H9`,Al:|@,K̀|0`Ku|0`Ke|0`KU|0`KE|0`K5;|::@c:KL,A|8`8a@Hm`b|8@8@88HyA,`~@8`HA@;,@(;LcK@;|;xcA,@|8x8a@H`b|8@8@88HA,`~@8`H1A@;,@(;LcK)@;|;xcA;,@؀ ;|..8a@8ceHA8a@A\88@HA;|;8a@8ce@|Hl@0:;@aLP8 H̀AK$ 8|.H}A8a@8@HmA;|;8a@8ce@ |.KLHaA8`HA|} 8!8`N K Cmain0 @N @strcpyb@8qA||+|"*AH|8@@@@|A LHp|+|*A$0|8@@@|+@P@D|*@|, TA|0|0|8@H|8@|0}0@@@ LAA 8`N 8`N 8`N 8c8,|0@A@,|0@KAA8`N 8`N 8`N @strcmpHA L| N LA L| N TA L| N \A L| N |fx|#x|3x`````b@T@q@| @M A|*|@ApiA<88!)})B|(88pT|HpT|88$&BM } 88BN |*|*pA} '&B|(pT|'G&FBM } '&BN ||$*|*N |@@ }D(|P@| 8 |Ta|dA(|$*|%*0 B||$*|%*aN |(0|$*|%*B| ||$*|%*aN @bcopy`A L| N pA L| N tA L| N xA L| N A L| N A L| N A L| N $lt$IBM @(#)61 1.13 src/bos/usr/ccs/lib/libc/__threads_init.c, libcthrd, bos43N 3/25/99 13:50:27Gdgmvc:p:r:Gdgmvc:p:r:class=%sattribute=link_methattribute=link_meth_diagconnkey=%sattribute=load_moduleattribute=cfg_method_load%s/usr/lib/methods/%s%s /usr/lib/methods/%suniquetype=%sattribute=belongs_to AND deflt=graphics@(#)05 1.3 src/bos/usr/lib/boot/network/link_meth.c, cmdnim, bos43V, v2000_47B3 00/11/13 14:33:14l\phP!Oerrno@symlink@  @exit@ realloc@ printf@ sprintf@ getopt@ basename@ 8@ __crt0v@optarg@E@R@_@l@ |@ @ @ @ __start! \`     $(,0 48< @DHLPTX\`dh/usr/lib:/lib:/usr/lpp/xlC/liblibc.ashr.olibcfg.ashr.olibodm.ashr.o@VPDlink_meth/5765c3403/430_system_configuration __mod_init PdAt_CLASS PdDv_CLASS PdCn_CLASSodm_terminateodm_initialize odm_get_listodm_get_firstodm_free_listst data # added an en./usr/ccs/040755 000000 000000 00000000000 10046301370 013111 5ustar00rootsystem000000 000000 ./usr/ccs/lib/040755 000000 000000 00000000000 10046301370 013657 5ustar00rootsystem000000 000000 ./usr/ccs/lib/libnim.a.min100444 000002 000002 00000643124 07246747156 015127 0ustar00binbin000000 000000 214452 0 0 136 136 0 214196 214452 0 983289454 300 300 750 5 shr.o` :nH0 hhRE.texth .datai@.bss.loaderWGl|!8,aHL```;`@;@A(8t0`@H89H A8aH88HA8,@ }8H)`,@c:; 8x8@ 8H8L9DH)A 4T`w;98x8@A  K,@D@y;ZA8x8@ 8HK8\8P8`8H`8`H <8@b088HcA,@,8p8d8`8HY`8`8!H,8|A8888aH8LH-A8aHH'}AH`e,A$( 8aH@c,( @b8HH[1A,@8888`8HU`bHZ݀A8`8!H(88aHcHA8aHH&A8b8HHZA,@d888`8HY`bHZmA8`8!H|.88`8H`bHZ9A8`H,;@@P;=cH&EA8bcHZ%A,;Z|AW[:@cKĀDbLc8HaDHYA8`8!}N A l To_Master0a|}&,! 8```@DA88g@889H uAHHY AaLHXA{cdH`A888,8`8H`HaL@ 8H`A,aHA8 88`8HaD@8H`A,a@80A08`H)`聁|} 8!a8`N H`A||y@8`008H`HH`}A,@Ā8`008H`H@H`%A||y@8`008H}`H48aHH`A,@8`008HI`H,8P8`A{H_A,X8`p@A .@HH``d8`.8H`聁a|} 8!8`N 8a@ALH_eA,8aH80@08`H`聁a|} 8!8`N 聁a|} 8!8`N 聁|} 8!a8`N HVUAaDHVIAaL8H^aA,aHA$8 88`8H`8`HpHVAaLHUA{cdH]A888,8`8H `aDHUAaLHUAa@HcccH]聁|8!} aN a}8!N C client_exec0 |}&`!;!````9;@c#8H]ŀA,@;@.Al|,ALC,@(8`888H`)8)4(|} 8!)0!8`N bC8`H[A`g88aXbcFH1A8aXH]=Ab,A(80`@8X889HyA8aX88HS=A,`z@@848(8`8H`)8)4(|} 8!)08`N 8b8HcH8b8Hcb$88HMA,@aP,AT|,@\|q88HNAHl8l8`88H`8`H8\8`88H`8`H8|TaP3|q88HNIA,A}~1b4,@P,AD@,A HN-A?@,@8`888H`b,A(8|0`@889HAA|HZAb)8)4|8!)0} N W}W::~0b|xb8`HJ``qb08x@HA|c@c1K Cx exec_status0 A L| N A L| N b8qA||+|"*AH|8@@@@|A LHp|+|*A$0|8@@@|+@P@D|*@|, TA|0|0|8@H|8@|0}0@@@ LAA 8`N 8`N 8`N 8c8,|0@A@,|0@KAA8`N 8`N 8`N @strcmpA L| N !|@XDHL8H!`,8`888@ uM{a@DHLHuX8!P}N Ah err_Rresult0 |!0,a$0`@8A889KyAH88a@HـA8e|@ HA08`d8@, 88A HA8`8@88H8!}N Aerrsig_handler|!H<@p,L3A(b,$8c@0A KA488`H8!@}N Aldisplay_errstr|$!@,DaH8A 0`@H@D9KA888a@@HH IA88a@H A|y8`/A8H``dcDKAcHAA8`X8!P}N Anim_mail0 |!xahlpt|!8hAg, A `~HDH@8`888HcHAX8!P}N Anim_error_plus|a!ax|!8axAc H| L^BA ` lT:|d.l`l8|8H`|p0,A,,@cccecHcH `cccecHEHAh8!`}aN Al nim_error0|!ahlptx|!8ahA H!ccccH`d<pcT:Al|e.l| T>@(`A ldT:|c .lH,| @$` AldT:|c .l`lH9cX8!P}N Anene0 |bc$,!80`@88A89KAPT;,3c;@8`X8!PHD,A HՀA;,?cA,Kܓ8`X8!P}N Aenable_err_sig||y!cAEM{~@,A<,| @8`H8!@}H@\H=AT:| .d\T:|d.h8@~DDH8!@}N @H<| 8`0@ H %``d@8~KՀy`$`}@8LHuA@,A H@A<pcT:At|d.c\,ccA`HA`|cHyA|0`H=``|8cecHAccH@AcH@uAc@8`@DHKU<pcT:Al|d.l| T>@(`A lT:|c .lH,| @$` AlT:|c .l`@lK8`x8!p}aN Awarning0 |!8,$aH;@A$80`@H889K5A8`HHA,aD$8aDA@HH A`f88aH8HHA,b88L@8a8HHEA8@8~(88H(9`||y,8~@8AA;HGA,8h8~P@DHqA|}y8lc8ȀHA`KYAcH A,@HH88~tH@!A|}y8c8ȀHAKAcH ŀA,@8~8A H5`ch8!`H;ch8!`}N Anim_log0 ||y4!,@DH8`@0@,cHq`|~y8`@H]``~,,@,H>-AcHAAa@cH AH,@H>AcHAAaHcH A`}|H Aa@H AaDH AaHH uA|0`H9``}c@DHHA|@,A H@N @strcpyA L| N A L| N A L| N A L| N A L| N A L| N A L| N A L| N A L| N A L| N A L| N ĐA L| N ȐA L| N ̐A L| N АA L| N ԐA L| N ؐA L| N A L| N A L| N b8q8A||04@T|+|*@0|||(8|894@|*0K0||*N 0||+|*AN /T,/|M 00AHAA,,N@ A,N@ A$, %N@ A$,,//N@ ALN@ ALN@ AL%N@ AL$,,//KBN BN BN %BN @strncpyA L| N A L| N A L| N A L| N A L| N A L| N A L| N A L| N  A L| N A L| N A L| N A L| N  A L| N $A L| N (A L| N ,A L| N b8 qAH||+A|+0 @|0|8 ||"+|*8 0 @N pk=@!k9J}i8A,AP8B8} P8})P},P@} P8})P},PA})@})PyA}+4Uk|Xp!k}iA ,8M 8B耤0|P8})P},P@4} P8})P},P@,|P8})P},PA})(})PyAH})@})PyA}Cx8tT@>@N @xstrcat0A L| N 4A L| N 8A L| N |"']+.*^if[0123456789]*^([^ ]+) ([^ ]+)$^([^ ]+) ([^ ]+) ([^ ]+)$^.*^([^ ]+) .*^([^ =]+)=(.*)^/dev/([^0123456789].*)^(.*)/([^/]+)^rc=([0-9]+)%s/nx.%d.%ld.XXXX exec_status: opening %s exec_statusopenrrc=Select in exec_statusreading stdoutreading stderr exec_status: Rc=%d; client_exec: Args[0]=%s; client_execpipe stdoutclient_execpipe stdErrclient_execforkclient_execdup stdoutclient_execdup stderrclient_execexecvprootrootTo_MasterrcmdTo_MastersetsockoptNoYes%s %s %s To_Masterwrite pkt%dTo_Masterwrite nargsTo_Master write arg.*[][ `$^&*()=+:,.;?/\<>|"']+.*^([^ ]+) ([^ ]+) ([^ ]+)( [^ ]+)*$^[abcdefABCDEF0123456789]{12}$|^0{1,12}$^([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+)$^[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}$^([^0123456789 ]+)([0123456789]*)^([^0123456789 ]+)([0123456789]+)^([0123456789]+-[0123456789]+)(.*)^([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+) (.*)^[0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}$ To_Master: Target=%s; Args[0]=%s; /usr/lpp/bos.sysmgt/nim/methods/m_chstate @(#)96 1.35 src/bos/usr/lib/nim/lib/nim_exec.c, cmdnim, bos43N, 9914A_43N 4/1/99 14:29:36masterbootnim_scriptfind_netdefault.*[][ `$^&*():,;?\<>|"']+.*^if[0123456789]*^([^ ]+) ([^ ]+)$^([^ ]+) ([^ ]+) ([^ ]+)$^.*^([^ ]+) .*^([^ =]+)=(.*)^/dev/([^0123456789].*)^(.*)/([^/]+)^rc=([0-9]+).*[][ `$^&*()=+:,.;?/\<>|"']+.*^([^ ]+) ([^ ]+) ([^ ]+)( [^ ]+)*$^[abcdefABCDEF0123456789]{12}$|^0{1,12}$^([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+)$^[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}$^([^0123456789 ]+)([0123456789]*)^([^0123456789 ]+)([0123456789]+)^([0123456789]+-[0123456789]+)(.*)^([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+) (.*)^[0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}$ @(#)66 1.1 src/bos/usr/lib/nim/lib/libnim_stubs.c, cmdnim, bos43D, 9806A_43D 2/9/98 13:04:08masterbootnim_scriptfind_netdefault.*[][ `$^&*():,;?\<>|"']+.*^if[0123456789]*^([^ ]+) ([^ ]+)$^([^ ]+) ([^ ]+) ([^ ]+)$^.*^([^ ]+) .*^([^ =]+)=(.*)^/dev/([^0123456789].*)^(.*)/([^/]+)^rc=([0-9]+) nim_log: str=%s; %c<%s> <%s> <%d> </var/adm/nim/errlock/usr/bin/alog/usr/bin/alog -q -t nimw%s%s> /var/adm/nim/nim.errora%s%s> /var/adm/nim/errlock%s: %s%s %s%s -s "%s" %s/usr/bin/mail w%s rc=%d %d enable_err_sig disable_err_sig .*[][ `$^&*()=+:,.;?/\<>|"']+.*^([^ ]+) ([^ ]+) ([^ ]+)( [^ ]+)*$^[abcdefABCDEF0123456789]{12}$|^0{1,12}$^([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+)$^[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}$^([^0123456789 ]+)([0123456789]*)^([^0123456789 ]+)([0123456789]+)^([0123456789]+-[0123456789]+)(.*)^([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+) (.*)^[0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}$ nim_mail: userids=%s; subject=%s; text=%s; errsig_handler: signum=%d; @(#)97 1.26.1.1 src/bos/usr/lib/nim/lib/nim_err.c, cmdnim, bos43S, s2000_22B0 5/30/00 12:06:57masterbootnim_scriptfind_netdefault.*[][ `$^&*():,;?\<>|"']+.*^if[0123456789]*^([^ ]+) ([^ ]+)$^([^ ]+) ([^ ]+) ([^ ]+)$^.*^([^ ]+) .*^([^ =]+)=(.*)^/dev/([^0123456789].*)^(.*)/([^/]+)^rc=([0-9]+)null message0042-006 %s: (%s) %s %s 0042-015 %s: syntax error %s0042-041 %s: %s already exists0042-099 %s: unable to open %s0042-100 %s: unable to close %s0042-121 %s: Specify %s OR %s0042-123 %s: %s is NOT exported0042-2000042-2010042-2020042-203null messageNIM objectNIM object classNIM object subclassNIM object typeNIM operationNIM interface stanzaNIM routing stanzaattribute nameattribute assignmentobject namelocation of resourcenetwork definitionIP addresssubnetmaskhostnamedefineallocationroute to the NIM masterexecutereadwritewarningresource allocationerror getting secondary porterror connecting to portdup2 stderrdup2 stdout# NIM client initialization # change the control state flagsbundlesourceoptionsNIM Error reportinit to masterrcmdsending attr_countsending to masterfopenNew niminfoget_adpt_addrCan not get adapter address.Adapter not found ?Adapter device name not found. Saving machines CPU id.Checking input attributes.Built NIM infomation file. usage: m_rmmac usage: m_rmnet usage: m_rmpdir usage: valid operations: valid types: usage: c_time_stamp [-e] EXCLUDED Allocating resources ... Initializing resources ... ENABLEDNOT ENABLEDINITIATEDNOT INITIATEDEXECUTEDNOT EXECUTEDRESETNOT RESETINITIALIZEDNOT INITIALIZEDSUCCESSFAILURELevel check is successful. Remove the %s %s resource. >>>> Unconfiguring NIM An Error Occurred. %s resource %s Configuration is complete. Creating the %s filesystem. Mounting the %s filesystem. Unmounting the %s filesystem. Creating the %s directory. Generated during definition of usage: gen_nim_name hostname not resolvable: missing: invalid attribute value: attribute mismatch: group type mismatch: duplicate machine definition: primary interface not found: primary interface is bad: error: Summary member_type=undefined Nothing to Process. Installing filesets ... PROCESSINGCOMPLETENOT_STARTEDnull messageanyincompleteshutdownbootingrunningreadyscheduleddd_bootdkls_initdtls_initdiagcustbos_inst_readybos_inst_phase_1bos_inst_phase_2bos_inst_phase_3maintavailableunavailablereadymaint_bootcust_setupmaint_setuplppchklppchk_setupNIM internal use onlynot runningin the process of bootingcurrently runningready for a NIM operationready for useunavailable for useready for usesync_rootssync_rootscheckverification is being performedalt_disk_install_setupalt_disk_installnull messagesuccessfailureresetnull messagemachinesresourcesnetworksflag_attrsstatesresultssubclassclasstypeoperationscontrol_opsinfo_attrsbos_rescust_resiplrom_subclassif_attrsonly_1pdirboot_resdisklessdatalessstandalonemasterspotbootrootpagingdumphomeshared_hometmploglpp_sourcesimagesinstallp_bundlebosinst_dataimage_datartemksysbscriptnim_scripttokentfddiclasstypenameatat_argat_joblockedmodversionreleasetranssizecommentsmissinginforeservedcontrolcontextmservedmusedrusedmresNMEMBERnetnamedefinechangeremoveallocatedeallocatescheduledd_bootdkls_initdtls_initdiagcustbos_instmaintresetlslppcheckMstateCstateprev_stateCstate_resultint_ethmca_tokmca_ethmca_fddipififros_emuservescpuidpushableRstateserverlocationif_supportedalloc_countsourcespot_optionssimages_optionsexportedfirst_dirNstatenet_addrsnmroutingring_speedpif_namemaster_ipmaster_portmaster_uidadpt_addradpt_namemknfsexp_paramswarningbundlehostnameiphahtbfgwsmsacommandpermsboot_infonfs_permsrootaccessrorwsecuregrantrevokedevicecdromtapeno_nim_clientpull_interfacepull_requestdisp_mntpntmount_ctrlasyncignore_stateinstallp_flagsfilesetslslpp_flagsforceverboseallpackagesdebuggroups NIM operationsgroups BOS image types togetherlocal filesystems & resourcesan installp bundle filea BOS rte imagea mksysb imageobsoleteobject is locked for updateOS modification levelOS version levelOS release levelsize informationuser entered commentsflag used internally by NIMresult of control actionlist ofdefine an objectchange an object's attributesremove an objectallocate a resource for usedeallocate a resourceenable a diskless/dataless bootperform software customizationperform a BOS installationperform software maintenancereset an object's NIM stateNIM stateNIM control statemachine CPU idobsoleteNIM statelocation of the resourcetoken ring networkethernet networkFDDI networkNIM statenetwork address for a networksubnetmask for a networkNFS export permissionsboot_envdir_createdpreserve_resignore_lockNIM internal use onlyenter_dbg_upenter_dbg_mpmodevfstypenum_parallel_syncsno_mkbootist_committedst_appliediplrom_emuroot_initializedcable_typedestroyanonNIM interal use onlyattributesthe set of possible NIM statesseqnodkls_resdtls_respull_opsauto_expandstd_resmstr_resunconfigplatformplatform_subclassrs6kRISC System 6000rs6ksmprspcRISC Personal Computer Systementer_dbgrs6k_subclassrs6ksmp_subclassrspc_subclassdefaultother_net_typemk_netbootsync_rootsPowerPC Personal Computerfixesfix_bundlefix_queryfix_query_flagsforce_pushno_client_bootrebootreboot specified machinesset_bootlistinst_warningmaint_bootboot_clientmksysb_flagsmk_imagecreate a mksysb imagerm_imageremove a mksysb imageexclude_filessize_previewregistration_portgroupsgroupa group namememberoperationopargsres_groupa group of resourcesmac_groupa group of machinesdefault_resselectexcludeexclude_allincludeinclude_allexclshowlogfull_loglog_typeadd_memberrm_membererr_infotmp_grp_tgtshow_progressshowresshow contents of a resourcereferenceresourcesm_inst_flagsinstfix_flagsrestrict_nfs_exportsfind_netresolv_confnet_definitionlppchkverify installed filesetslppchk_flagsnetboot_kernelkernel to use for network bootsmit_bundleRISC System/6000 Architecturerspcsmprspcsmp_subclassnew_namegenericdtls_init_resRstate_resultresult of resource operationlatest_infogui_ref_time_stampNIM GUI refresh time stampgui_refresh_macs_countgui_refresh_delayieee_entclient_allocclient_regvalidate_cpuidno_error_msgglobal_exportplat_definedif_definedif_prebuildif_discoverdiskalt_disk_installmksysb_levelshow_detailsglobal_forcewsm_ref_time_stampwsm_refresh_macs_countwsm_refresh_delayatmATM networkexport_bootc_infoboot_filenew_typephaseconcurrenttime_limitcmd_operationactivecompletefailedyesmon_opgrp_status_delaymax_nimesis_threadsclient_state_retryns_alloc_cntdisable_distributinguse_clients_if_hostrep_alloc_cntspup_cronspup_ownnull messageobsolete NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only obsolete obsolete obsolete obsolete obsolete obsolete NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only NIM internal use only D.*[][ `$^&*()=+:,.;?/\<>|"']+.*^([^ ]+) ([^ ]+) ([^ ]+)( [^ ]+)*$^[abcdefABCDEF0123456789]{12}$|^0{1,12}$^([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+)$^[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}$^([^0123456789 ]+)([0123456789]*)^([^0123456789 ]+)([0123456789]+)^([0123456789]+-[0123456789]+)(.*)^([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+) (.*)^[0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}$0042-001 %s: processing error encountered on "%s": %s0042-002 %s: error signal number %s received - processing aborted0042-003 %s: error on system call; info follows: %s 0042-004 %s: error on system call %s 0042-005 %s: ODM error encountered; odmerrno = %d0042-007 %s: internal error (buffer overflow) in function %s0042-008 %s: Request denied - %s0042-009 %s: Insufficient data for requested operation - %s0042-010 %s: the contents of the %s directory are not local to the machine %s and they must be in order for this to succeed0042-011 %s: unable to access the /etc/niminfo file0042-012 %s: this command may only be executed on a NIM master0042-013 %s: unable to obtain the global NIM lock0042-014 %s: an internal error has occurred resulting in an invalid %s object named "%s"0042-016 %s: "-%c" is not a valid option for this operation %s0042-017 %s: invalid option-argument for "-%c" %s0042-018 %s: "-%c" is a required option for this operation %s0042-019 %s: option "-%c" requires an argument %s0042-020 %s: "%s" must be supplied for this operation %s0042-021 %s: the "%s" attribute is required for this operation0042-022 %s: "%s" exceeds the maximum limit of %d0042-023 %s: "%s" is not a valid %s0042-024 %s: "%s" is not a valid type for "%s"0042-025 %s: the "%s" operation cannot be applied to "%s" types0042-026 %s: "%s" is not a "%s" object0042-027 %s: "%s" is required to complete the definition of the "%s" object. This attribute is either currently missing or the current operation would cause it to become missing.0042-028 %s: "%s" cannot be used for this operation0042-029 %s: the "%s" attribute cannot be supplied for this operation0042-030 %s: a sequence number may not be specified with the "%s" attribute0042-031 %s: unable to generate a unique id0042-032 %s: %s must be unique and "%s" already exists0042-033 %s: "%s" attr already exists with seqno of "%d"0042-034 %s: unable to generate a new seqno for "%s"0042-035 %s: unable to find attr which matches this query: "%s"0042-036 %s: "%s" cannot serve a resource because of its type ("%s")0042-037 %s: the state of "%s" prevents this operation from succeeding0042-038 %s: unable to continue because "%s" is locked0042-039 %s: unacceptable release level of %s.%s for "%s"0042-040 %s: unable to remove the "%s" definition because it is currently referenced by other objects0042-042 %s: unable to communicate with %s 0042-043 %s: unable to remove "%s" because one or more NIM resources are still defined as being served by that machine0042-044 %s: missing in attribute assignment for "%s"0042-045 %s: a sequence number must be specified with all "%s" attributes for this operation0042-046 %s: unable to %s the file "%s" 0042-047 %s: unable to allocate the "%s" resource because its type cannot be used by "%s" objects0042-048 %s: "%s" is unable to access the "%s" resource due to network routing0042-049 %s: either "%s" or another resource of this type has already been allocated to "%s"0042-050 %s: operation failed for the following reason: %s %s %s0042-051 %s: unable to resolve "%s" to an %s0042-052 %s: unable to %s "%s" because resources have been allocated to it0042-053 %s: there is no NIM object named "%s"0042-054 %s: unable to remove "%s" because it is part of the "%s" installp_bundle0042-055 %s: "%s" is not a valid "source" for this operation0042-056 %s: duplicate attribute assignment for "%s"0042-057 %s: "%s" is a required attribute0042-058 %s: unable to allocate "%s" to "%s" because it does not support the network interface type of that client0042-059 %s: conflict between the supplied type ("%s") and the real type ("%s") for "%s"0042-060 %s: multiple "%s" attributes were specified and only one is allowed0042-061 %s: the "%s" resource is currently allocated for client use0042-062 %s: "%s" is missing something which is required0042-063 %s: the following resource types are required for this operation but have not yet been allocated to "%s":0042-064 %s: "%s" is currently serving a resource ("%s") that is allocated for use0042-065 %s: "%s" is a reserved word and cannot be used to name objects0042-066 %s: the string "%s" contains one or more characters which are not allowed to be used in strings in the NIM environment0042-067 %s: this operation cannot be applied to "%s" because it is a reserved NIM object0042-068 %s: "%s" is not allocated to "%s"0042-069 %s: the %s operation cannot be performed when the target has a %s of "%s"0042-070 %s: there is no NIM object which has the following characteristics: %s0042-071 %s: an operation has already been scheduled for "%s"0042-072 %s: unable to perform a scheduled operation because the "%s" attribute is missing from the definition of "%s"0042-073 %s: unable to create a customization script for "%s" because it does not have any customization resources allocated to it0042-074 %s: "%s" is not a valid pathname because it has been specified with a relative path and pathnames must be absolute0042-075 %s: error encountered when exporting "%s" on "%s":%s0042-076 %s: port %d is already used by the "%s" service0042-077 %s: unable to add routes from the NIM Master0042-078 %s: unable to change the "%s" NIM route because the destination network specified in the new value does not match the destination network specified in the current value0042-079 %s: unable to deallocate "%s" because "%s" must be deallocated first0042-080 %s: fatal error returned by the "%s" command: %s0042-081 %s: a resource already exists on "%s" at location "%s"; due to NFS export restrictions, the new location "%s" may not be used0042-082 %s: "%s" is not a supported device0042-083 %s: network hardware addresses must be unique and "%s" is already being used by the machine "%s"0042-084 %s: This machine is already configured to be a NIM Master0042-085 %s: unable to continue due to fatal error encountered by the niminit command0042-086 %s: a NIM route already exists between "%s" and "%s" (only 1 is allowed)0042-087 %s: obsolete error message0042-088 %s: obsolete error message0042-089 %s: obsolete error message0042-090 %s: obsolete error message0042-091 %s: error returned from malloc0042-092 %s: SPOT location must be an absolute path name; "%s" is not0042-093 %s: unable to create directory "%s"0042-094 %s: unable to populate SPOT from "%s"0042-095 %s: unable to prepare the source %s0042-096 %s: unable to prepare the source %s, type unknown0042-097 %s: unable to start daemon:%s0042-098 %s: unable to refresh daemon:%s0042-101 %s: unable to rewind %s0042-102 %s: unable to position %s0042-103 %s: unable to restore from %s0042-104 %s: pipe system call failed0042-105 %s: dup system call failed0042-106 %s: unable to execute the "%s" program0042-107 %s: waitpid system call failed0042-108 %s: "%s" is not a valid device name0042-109 %s: unable to get filesystem information about "%s"0042-110 %s: /usr SPOT already exists0042-111 %s: invalid sequence number in "%s"; it must be between 1 and %d0042-112 %s: "%s" does not contain a valid bos.rte image0042-113 %s: unable get size requirements for %s0042-114 %s: unable to expand file system %s by %d0042-115 %s: unable to update %s0042-116 %s: obsolete error message0042-117 %s: operation failed due to error encountered by c_mkbooti0042-118 %s: a NIM operation is currently being performed on the "%s" machine or it has resources allocated to it0042-119 %s: unable to change "%s" because it is currently referenced by other objects0042-120 %s: Usage: c_get_level 0042-122 %s: %s is already exported0042-124 %s: NFS option %s is NOT supported 0042-125 %s: Usage: c_upd_imagedata 0042-126 %s: Could not update %s/image.data0042-127 %s: image.data file %s is invalid0042-128 %s: copy original image.data file is in %s0042-129 %s: "%s" is an invalid resource type for this operation0042-130 %s: "%s" cannot be specified as an attribute for this operation0042-131 %s: the "%s" attribute conflicts with "%s": one or the other may be specified, but not both0042-132 %s: "%s" cannot be specified as a value for "%s" for this operation0042-133 %s: unable to remove the "%s" at location "%s"0042-134 %s: unable to initiate network boot on "%s"0042-135 %s: unable to perform the requested operation because "%s" is currently controlled by the machine "%s". It may be necessary to deallocate resources from the target before performing the intended operation.0042-136 %s: there is no NIM route from the "%s" network to the machine "%s"0042-137 %s: the /etc/niminfo file is missing some required environment varibles0042-138 %s: unable to update the rhost file with %s hostname0042-139 %s: the resource "%s" is served by "%s" and cannot be used to install "%s"0042-140 %s: unable to remove the /etc/niminfo file on "%s"0042-141 %s: unable to remove the "%s" attribute because "%s" does not have one0042-142 %s: unable to add the "%s" attribute because attribute values must be unique and "%s" already exists with the same value0042-143 %s: only one "%s" attribute can be specified for an object and one already exists for "%s"0042-144 %s: sequence numbers must be unique and "%d" is already being used with the "%s" attribute0042-145 %s: "%s" is not a valid attribute name0042-146 %s: "%s" is not a valid type0042-147 %s: this command may not be executed on a NIM master0042-148 %s: invalid information in "%s" for the "%s" object0042-149 %s: unable to deallocate "%s" because it is part of the allocated installp_bundle "%s"0042-150 %s: the file "%s" has a vfstype of %s. This conflicts with the expected vfstype, which is one of the following: %s0042-151 %s: the file "%s" has a file type of %s. This conflicts with the expected type of %s.0042-152 %s: an error occurred while performing root sync operations on the following clients: 0042-153 %s: the file "%s" has file permissions of %s. This conflicts with the expected permissions of %s.0042-154 %s: the file or directory "%s" does not exist0042-155 %s: unable to perform requested operation because the server of the root resource must be the same as the server of the spot resource and your request violates this requirement.0042-156 %s: there is no %s at location "%s"0042-157 %s: unable to access the "%s" file0042-158 %s: unable to modify the "%s" file0042-159 %s: %s is missing one or more of the following options: %s0042-160 %s: unable to create any type of network boot image0042-161 %s: there is insufficient free disk space in "%s" to complete the requested operation; data follows: required = %s available = %s0042-162 %s: an lpp_source which has the "simages" attribute is required for this operation0042-163 %s: machine "%s" serves a resource which is being allocated, however, NIM is unable to determine which interface on this machine should be used by the client because this machine is also functioning as the gateway between the "%s" and "%s" networks.0042-164 %s: "%s" cannot be used as a source for installable images in this context because it is a CDROM.0042-165 %s: "%s" cannot be associated with the type of network referenced by the "%s" attribute0042-166 %s: "%s" requires a corresponding "%s" attribute0042-167 %s: "%s" does not contain a valid IPL ROM emulation image0042-168 %s: the destination network ("%s") specified in "%s" is the same as the originating network0042-169 %s: you have allocated an lpp_source, but have not specified which filesets are to be installed using that lpp_source0042-170 %s: "%s" is not a valid platform type0042-171 %s: the "%s" configuration type is not supported for the "%s" platform type0042-172 %s: This machine's CPU ID does not match the CPU ID stored in the NIM database.0042-173 %s: "X" cannot be specified as a value for installp_flags when the auto_expand attribute has a value of "no". 0042-174 %s: The %s attribute may only be assigned a value of "yes" or "no". 0042-175 %s: An unexpected result was returned by the "%s" command: %s0042-176 %s: The resource located in %s cannot serve as a "support images" (or "simages") lpp_source because one or more of the following filesets are missing: %s0042-177 %s: There is insufficient free disk space in "%s" to complete the requested operation; data follows: (All sizes displayed are in 512-byte blocks.) required = %s available = %s0042-178 %s: the logical device name of the network adapter must be supplied when connecting to the "%s" network because that network is composed of more than one network interface type.0042-179 %s: the network type specified by the "%s" attribute cannot be removed because it is currently being used by one or more clients which are attached to the "%s" network.0042-180 %s: The ip address %s does not belong to the network %s which is represented by the nim object %s. 0042-181 %s: The "fix_query_flags" attribute has an illegal value. Use "lsnim -Pa fix_query_flags" for a list of legal values. 0042-182 %s: A resource of type "%s" cannot be allocated for the current operation at the same time as a resource of type "%s". Allocate one or the other but not both. 0042-183 %s: The "%s" attribute cannot be specified for the current operation when a resource of type "%s" is allocated. Use one or the other but not both. 0042-184 %s: The network address (net_addr) or subnet mask (snm) cannot be changed for network "%s" because NIM clients are currently defined as being connected to that network. Remove the client definitions before changing the network. 0042-185 %s: Failed to link or copy %s to %s Check permissions and filesystem space0042-186 %s: Failed to copy setup programs to %s Either start NFS on %s or free 1000 512-byte blocks in the %s filesystem.0042-187 %s: Failed to expand filesystem %s on %s0042-188 %s: Failed to NFS mount %s on %s0042-189 %s: Failed saving existing boot image. Check space in the %s filesystem.0042-190 %s: The key is NOT in the NORMAL position. Unattended installtion cannot complete unless the key is in the NORMAL position.0042-191 %s: Unable to write the IPLROM emulation to %s0042-192 %s: Unable to find boot logical volume %s0042-193 %s: %s has no entry for %s in .rhosts or cannot resolve host id0042-194 %s: %s does not allow NIM push operations. Remove /etc/nimstop on %s if push operation is necessary.0042-195 %s: Unable to order boot device list on "%s"0042-196 %s: The "set_bootlist" attribute is only valid when used in combination with the "no_client_boot" or "boot_client" attributes.0042-197 %s: The network adapter's logical device name must be specified in the "if1" attribute of the target machine's NIM definition when using the force_push attribute if the target machine has more than one interface for a given network type. Add one of the following to the "if1" attribute of the target's NIM definition: %s0042-198 %s: When converting a machine's /usr filesystem to a SPOT the bos image on the media (lpp_source) being used to create the SPOT must match the bos image that was used to install the machine. The machine was installed with bos.rte %s. The package on the installation media contains bos.rte %s.0042-199 %s: The "no_client_boot" and "boot_client" attributes may not be specified together.0042-204 %s: The "mk_image" and "source" attributes are only valid when specified together.0042-205 %s: The bos.sysmgt.sysbr fileset must be installed on %s to perform the system backup. You may install this fileset with the NIM "cust" operation.0042-206 %s: There is already a %s resource allocated to %s.0042-207 %s: Unable to allocate the %s resource to %s.0042-208 %s: Unable to lock %s. This could mean that the client is already locked, or that the name given does not refer to a valid NIM client. 0042-209 %s: The "mksysb_flags" attribute contains an illegal value. Use "lsnim -Pa mksysb_flags" for a list of legal values. 0042-210 %s: The maximum space required for the backup is greater than the amount of free space in the target filesystem. To ignore space requirements use the "-F" flag when defining the mksysb resource. 0042-211 %s: The member %s already exists in group %s.0042-212 %s: The member named %s was not added to the %s group, because it is not a valid NIM name.0042-213 %s: The group %s was not created because it did not contain any valid members.0042-214 %s: Unable to add "%s" as a member of group "%s0042-215 %s: %s is an invalid log type for the showlog operation. Valid types are: %s0042-216 %s: %s is an invalid log type for SPOTs. Valid types are: %s0042-217 %s: %s is an invalid log type for diskless and dataless machines. Valid types are: %s0042-218 %s: The log file is either empty or does not exist at %s0042-219 %s: The object %s is incompatible with the group %s.0042-220 %s: You cannot have more than one resource of type %s in a resource group.0042-221 %s: The group %s is being removed because its single remaining member was removed during this operation.0042-222 %s: An unknown error occurred allocating resources to the machine %s in the method: %s.0042-223 %s: Invalid input file: %s The file either cannot be read, is empty, or contains no valid entries.0042-224 %s: The limit on the length of a line (%d bytes) in a NFS exports file was exceeded in the file %s The export operation cannot be performed.0042-225 %s: An error occurred while updating the exports file %s. Check for corruption in the file.0042-226 %s: A time-out occurred while attempting to initiate the %s operation on the client. The operation may not have started successfully.0042-227 %s: The state of %s indicates that the machine may not be ready for certain NIM operations: %s0042-228 %s: invalid release level of %s.%s.%s for "%s"0042-229 %s: When installing a system using a mksysb as the source for the installation, the level of the SPOT used for the installation must match the level of the mksysb image that is being installed. The release levels of the SPOT, %s, and the mksysb, %s, do not match. 0042-230 %s: When installing a system using a mksysb as the source for the installation, the level of the SPOT used for the installation should match the level of the mksysb image that is being installed. If this convention is not followed, the installation may not complete successfully. 0042-231 %s: Unable to generate the formatted list of software to install. 0042-232 %s: Unable to create the temporary INSTALLP_BUNDLE resource needed to perform this operation. 0042-233 %s: The NIM Master is already initialized. You must unconfigure the NIM Master before you can perform this operation. 0042-234 %s: You can not restore a NIM database backup onto a machine that has an earlier level of the NIM master fileset installed. 0042-235 %s: You must specify an image source for SPOT creation. 0042-236 %s: A name and/or directory specification is missing for the LPP_SOURCE. 0042-237 %s: A name and/or directory specification is missing for the SPOT. 0042-238 %s: A directory specification is missing for the Diskless/ Dataless machine resources. 0042-239 %s: You must specify both a name and a directory for the %s resource to create it. 0042-240 %s: You must specify a directory for the diskless and dataless machine resources to create them. 0042-241 %s: You must specify both a size and a volume group if you want to create a new filesystem for the %s resource. 0042-242 %s: You must specify both a size and a volume group if you want to create a new filesystem for the diskless and dataless machine resources. 0042-243 %s: **** You can not create the same filesystem for the LPP_SOURCE and the SPOT. Please specify different directory names for these resources. 0042-244 %s: **** You can not create the same filesystem for the LPP_SOURCE and the Diskless/Dataless resources. Please specify different directory names for these resources. 0042-245 %s: **** You can not create the same filesystem for the SPOT and the Diskless/Dataless resources. Please specify different directory names for these resources. 0042-246 %s: Not enough space on %s. Try specifying different volume groups for the filesystems that you are creating. 0042-247 %s: Creation of the %s filesystem failed. 0042-248 %s: An error occurred during filesystem creation. Please correct the problem and try again. 0042-249 %s: NIM Master initialization failed. 0042-250 %s: Unable to continue with the configuration. 0042-251 %s: A route cannot be added to %s because a required default route for %s is missing. Add a default route to %s and try this operation again.0042-252 %s: Unable to locate a matching network for %s 0042-253 %s: You cannot use the "net_definition" attribute when the "find_net" keyword is not specified as the first field of the "if" attribute. You specified "%s" instead of "find_net" 0042-254 %s: Invalid format for the specified value of "net_definition": %s The value of the attribute should be as follows: [] [] [] where: = network type (one of tok, ent, fddi, etc.) = dotted decimal subnet mask for the network = optional default gateway ip address or hostname used by the machine being defined to communicate with the master = optional default gateway ip address or hostname used by the master to communicate with clients on other subnets = optional name to be given to the NIM definition created for the network. (A unique default name is used otherwise.) If you wish to specify and if or are not applicable, specify 0 in their place. If is 0, cannot be non-zero. 0042-255 %s: The master already has a default route and the gateway which you specified as being the default for the master is different from that which is already defined: %s Use the "change" operation if you wish to modify the master's default gateway. 0042-256 %s: A default route already exists for the network "%s" You may modify the default gateway but you cannot define more than one default route. 0042-257 %s: You cannot specify the "net_definition" attribute without specifying the "if" attribute when changing a machine definition. 0042-258 %s: You cannot specify the "net_definition" attribute when creating or modifying more than one "if" attribute in the same "change" operation. Use two separate operations. 0042-259 %s: The value of "default_res", specified as "%s" on the master's database definition, is not a valid NIM resource group. 0042-260 %s: The "default" attribute is only applicable when manipulating a resource group. 0042-261 %s: Illegal use of the "async" attribute. This attribute may only be specified for the lppchk operation when the target is a standalone machine or a group of standalone machines. 0042-262 %s: The filename of the client definition file is missing for this operation. 0042-263 %s: The netboot_kernel attribute may only be assigned a value of "up" or "mp". 0042-264 %s: The image source "%s" that was used to define the lpp_source is missing one or more of the following requested packages: %s0042-265 %s: The image source "%s" that was used to define the lpp_source is missing one or more of the following from the list of default packages: %s0042-266 %s: The following requested packages are missing from the defined lpp_source: %s0042-267 %s: The defined lpp_source does not have the "simages" attribute because one or more of the following packages are missing: %s0042-268 %s: The operation cannot be performed because all members of the target group specified are currently excluded from operations on the group. You must unmark (or include) excluded group members before proceeding. 0042-269 %s: Only one verification mode may be specified for this operation. 0042-270 %s: The %s operation is only supported on SPOTs and NIM clients installed with a version and release level of 4.2 or greater. 0042-271 %s: A resource matching the type of "%s" is already allocated to "%s". You cannot allocate more than one resource of this type to a machine. 0042-272 %s: "%s" cannot be specified as a value for "default_res" because it is not a valid NIM resource group. 0042-273 %s: '%s' cannot be specified as the location for the mksysb image because it is a directory. You must specify the filename where the mksysb image currently resides or will reside after creation. 0042-274 %s: The '-e' flag in the mksysb_flags attribute and the exclude_files attribute cannot be specified together. Specify the '-e' flag with the mksysb_flags attribute to exclude the files in /etc/exclude.rootvg on %s from the backup, or specify an exclude_files attribute. 0042-275 %s: Unable to obtain possession of the lock file %s. If no NIM operations are currently in progress remove the file and repeat the operation. 0042-276 %s: The %s fileset must be installed before this operation can be performed. 0042-277 %s: diskless and dataless machines cannot be defined with a primary network install interface residing on a "generic" NIM network. It is presumed that a network adapter defined on a "generic" NIM network does not support network boot. 0042-278 %s: The interface specified does not correspond to a network adapter that is known to support network boot. As a result, the NIM master has been defined on a "generic" NIM network. Network boot dependent operations, such as base operating system installation, will not be possible on any NIM client whose primary network install interface is defined on the same network as the NIM master. 0042-279 %s: The interface specified maps to a subnet which has been defined as a "generic" NIM network. It will not be possible to perform network boot dependent operations, such as base operating system installation, on the machine definition created by this operation. 0042-280 %s: Specify a complete date and time for the scheduled operation in the form: YYMMDDhhmm. 0042-281 %s: The /usr filesystem on the specified server cannot be converted to a NIM SPOT. Either the RM_INST_ROOTS variable was set to "yes" in a bosinst.data file during initial installation of the machine or "inurid -r" was invoked at some time subsequent. The only way to create a SPOT on this machine is to specify the location to be something other than /usr or re-install the machine and then create a SPOT in /usr. 0042-282 %s: The BOS installation has been enabled but could not be initiated because the following file was not found on the target: %s To start the installation do ONE of the following: 1. initiate a network boot operation from the target 2. correct the state of the target with NIM's "reset" operation and invoke the bos_inst operation again either: a) using the "Force Push" option (-a force_push=yes), or b) after installing and configuring the bos.sysmgt.nim.client fileset on the target. 0042-283 %s: The existence of the file "%s" on the server "%s" indicates that a NIM SPOT may still be mounted in a subdirectory of "%s" which will be removed by this operation. Before attempting this operation again, unmount the SPOT's directory along with any other directories that may be mounted beneath the directory being removed. FAILURE TO DO SO WILL RESULT IN LOSS OF DATA ON THE SPOT SERVER! 0042-284 %s: A NFS limitation prevents mounting a file over a directory when the file resides in the root (/) directory on a server. As a result, you must move the file %s to a different location before defining it as a NIM resource. 0042-285 %s: The client "%s" can not have both a home "%s" and a shared_home "%s" resource allocated for this operation. 0042-286 %s: Client "%s" currently has resources allocated to itself. 0042-287 %s: Client "%s" currently has resource "%s" allocated to itself. 0042-288 %s: Clients cannot allocate resources at this time. 0042-289 %s: Client "%s" cannot allocate resources. 0042-290 %s: Clients cannot allocate resource: "%s". 0042-291 %s: The NIM master is not currently allowing registration of NIM clients. Please seek assistance from your network install administrator. 0042-292 %s: The NIM environment currently has resources allocated. The global exports attribute can not be changed until all resources are deallocated. The operation may be forced with the "force" option but deallocation of resources may give unpredictable results. 0042-293 %1$s: You can not specify the "%2$s" attribute when the source for the "%3$s" operation is "%4$s". 0042-294 %1$s: The "%2$s" resource may not be used when the source for the "%3$s" operation is "%4$s". 0042-295 %s: The NIM environment currently has resources allocated. The global exports attribute can not be changed until all resources are deallocated. 0042-296 %s: Diskless and dataless machines cannot be defined with a network install interface residing on an ATM NIM network. It is presumed that a network adapter defined on an ATM NIM network does not support network boot. 0042-297 %s: Clients on ATM networks must be rebooted immediately in order to successfully install when the bos_inst operation is performed. Do not specify any options that would override the reboot. 0042-298 %s: If a machine is on an ATM network, it must be a configured NIM client to be installed. The "force_push" attribute is not valid for clients on ATM networks. 0042-299 %s: A machine on an ATM network can not be network booted for maintenance. 0042-300 %s: A machine on an ATM network can not be network booted for diagnostics. 0042-301 %s: This operation is only valid for converting "generic" networks into "atm" networks. 0042-302 %s: the state of "%s" prevents this operation from succeeding. Use the "reset" operation to correct its state then retry the intended operation. 0042-303 %s: the %s operation cannot be performed when the target has a %s of "%s". It may be necessary to reset the target before retrying the operation.0042-304 %s: Unable to obtain the space allocation lock for server %s. Only one SPOT, lpp_source, or mksysb resource can be created or modified at any given time on a given NIM server. If other operations involving these resources are not currently in progress, remove file: %s and repeat the operation. 0042-305 %1$s: "%2$s" attribute is only valid when the "%3$s" attribute is also specified. 0042-306 %1$s: "%2$s" attribute is only valid with targets of type "mac_group". 0042-307 %1$s: "%2$s" attribute is only valid with the following operations: bos_inst, cust, and alt_disk_install. 0042-308 %1$s: "%2$s" attribute is not valid for defining objects of type "%3$s". 0042-309 %1$s: The source type "%2$s" is not valid for defining an object of type "%3$s". 0042-310 %1$s: "%2$s" attribute requires the "%3$s" to be a "%4$s" machine type. 0042-311 %1$s: "%2$s" attribute needs to be set or the "%3$s" object needs to be a "%4$s" type. 0042-312 %s: The copy failed. The target file "%s" did not get copied or the size is different than the source file "%s". 0042-313 The "Source for Replication" option and the "NIM CLIENT to backup" option may not be specified together. 0042-314 The "Source for Replication" option and the "CREATE system backup image" option may not be specified together. 0042-315 %s: No authentication methods are configured. 0042-316 %s: No password entry was found for this user. 0042-317 %1$s: Kerberos 4 authentication failed : Kerberos 4 was configured but the %2$s library could not be opened. 0042-318 %1$s: Kerberos 4 authentication failed : The %2$s library did not contain the %3$s function. 0042-319 %1$s: The %2$s attribute may only be assigned a value within a range of %3$d to %4$d. 0042-320 %s: A value must be specified for "Maximum simultaneous requests" when enabling the "Client Request Tuning?" option.an install operation is occurring on the server of this resourcethe following resources are required:the following resources are optional:the following attributes are required:the following attributes are optional:the Cstate has been set based upon the Nstate of "%s"nimesis unable to read from socketnimesis can not create file pointer** Mail message from NIM command %s, process id %d ** Text of message: %s End of Mail: Initialized ODM and mounted NIM classes.Making sure the NIM Master package is OK.Adding NIM masters network to NIM class.Connecting NIM master to master network.Building support images for NIM.Adding NIM deamons to SRC and starting.... usage: nimclient -d nimclient -p | -P nimclient -o [-a ]...] nimclient -l usage: lsnim -p|-P [-S] lsnim -p|-P -c |-s |-t [-l]|[-o]|[-O] [-Z] lsnim -p|-P -a ... lsnim -t -q lsnim [-c ]|[-s ]|[-t ] [-l]|[-o]|[-O] [-Z] [] lsnim [-a ] [-Z] [] lsnim -q lsnim -L [-s ]|[-t ] usage: m_mkmac -t [-a ]... usage: m_mkres -t [-a ]... usage: m_mkbosi -t [-a ]... usage: m_mknet -t [-a ]... usage: niminit -q niminit -a ... usage: nim -o [-t ] [-a ]... usage: m_mkres -t [-a ]... usage: c_ckros_emu -a ros_emu= usage: -t [-a ]... usage: -a ... usage: -a ... usage: -a ... usage: m_schedule <"at" time> [] usage: nimconfig -q nimconfig -a ... nimconfig -r usage: m_chnet -t [-a ]... usage: c_ch_nfsexp -a ... unable to perform %s due to missing resources usage: nimclient -d sets client date and time to that of master. nimclient -l invokes the lsnim command on the master. nimclient -p | -P enables/disables the NIM master's push permissions on client. nimclient -o [-a ]... executes NIM operations on the client. usage: To display predefined and help information about NIM objects, types, classes and subclasses: lsnim -p|-P [-S] lsnim -p|-P -c |-s |-t [-l]|[-o]|[-O] [-Z] lsnim -p|-P -a ... To list required and optional attributes for an operation: lsnim -q lsnim -q -t To list information by class, subclass, type or attribute: lsnim [-c ]|[-s ]|[-t ] [-l]|[-o]|[-O] [-Z] [] lsnim [-a ] [-Z] [] To list information that can be accessed by a client machine: lsnim -L [-s ]|[-t ] Miscellaneous options: -g displays long listing of group object with state information for individual members -l displays detailed information -m applies other flags specified to individual members of groups -O lists operations NIM supports -o used by NIM's SMIT interface -Z produces colon-separated output usage: nimconfig -r [-v] rebuilds /etc/niminfo file (not valid with -a) nimconfig -a ...[-v] specifies attribute assignments for nimconfig operation -v displays detailed output for nimconfig operations. usage: niminit -a ...[-v] -v displays detailed output for the niminit operation. ** Use lsnim -O or lsnim -POt to list valid operations for a particular object or object type. ** Use nimclient -l -O or nimclient -l -POt to list valid operations for a particular object or object type. ** Use lsnim -q or lsnim -q -t to list required and optional resources and attributes for a particular NIM operation. ** Use nimclient -l -q to list required and optional resources and attributes for a particular NIM operation. usage: nim -o [-F] [-t ] [ -S ] [-a ]... ******************************************************************* ******************************************************************* ******************************************************************* NIM has initiated a bos installation operation on this machine. Automatic reboot and reinstallation will follow shortly... ******************************************************************* ******************************************************************* ******************************************************************* +---------------------------------------------------------------------+ System Backup Image Space Information (Sizes are displayed in 1024-byte blocks.) +---------------------------------------------------------------------+ Required = %s (%s MB) Available = %s (%s MB) Data compression will be used by the system backup utilities which create the system backup image. This may reduce the required space by up to 50 percent. usage: m_mkgroup -t [-a ]... usage: m_rmgroup See the log file: %s for details or use the "showlog" operation. # global variable tells scripts to update client's object with error text. **************************************************************** *** The log for the "root" part of this /usr SPOT now follows *** **************************************************************** Setting up access to client code residing on NIM master ... Initiating the %s operation on machine %d of %d: Performing %s operation on machine %d of %d: Unexpected results ... (details will follow). Performing clean up ... Note: Use the lsnim command to monitor progress of "%s" targets by viewing their NIM database definition. Deallocating internal resources ... Enabling "%s" Operation Initiating "%s" Operation Performing "%s" Operation "%s" Operation Summary Errors/Warnings Summary Target Result ------ ------ Note: ENABLED targets must be rebooted to initiate the operation. You can not specify both FIXES and a FIX_BUNDLE for this operation. You must specify either FIXES or a FIX_BUNDLE for this operation. rte - Install from installation images spot - Perform a SPOT copy mksysb - Install from a mksysb The level of the NIM master fileset on this machine is: %s The level of the NIM database backup is: %s >>>> Initializing the NIM Master. >>>> Removing any diskless and dataless machine resources that may have been created. >>>> Removing the %s %s resource. >>>> Removing the %s filesystem. >>>> Undoing the partial configuration because something failed >>>> Checking available space for the new filesystems %s MB required on %s. %s MB available. >>>> Creating the %s filesystem in the %s volume group on the %s machine. The filesystems were created successfully. >>>> Creating the %s LPP_SOURCE resource from %s. (This may take a while.) >>>> Creating the %s LPP_SOURCE resource from the directory: %s (This may take a while.) The %s %s resource was created successfully. >>>> Creating the %s SPOT resource from %s. (This may take a while.) >>>> Creating resources for diskless and dataless machines. ...Create the %s %s resource... ...Creation of the %s %s resource failed... The diskless and dataless machine resources were created successfully. >>>> Creating INSTALLP_BUNDLE resources from the predefined system bundles. No system bundles could be found. The INSTALLP_BUNDLE resources have been created successfully. An error occurred when creating the INSTALLP_BUNDLE resources. The creation of the following resources FAILED: The %s %s resource was not created successfully. The resources for diskless and dataless machines were not all created successfully. The following resources were not created: An INSTALLP_BUNDLE resource was not created successfully. Correct the reported errors. When the errors have been corrected, attempt again to create the resources that were not created successfully. Creation of the %s filesystem failed. Unable to mount the %s filesystem. Removing the %s filesystem and mount point. Removal of the %s filesystem failed. The %s filesystem already exists. It must be removed before a new filesystem can be created with the same mount point. # The following resource groups exist. If you allocate # via a resource group an attempt is made to allocate # all applicable group members. # The following resource groups exist. If you deallocate # via a resource group an attempt is made to deallocate # all applicable group members. usage: m_find_net Warning: A NIM definition is referenced by the reserved word "%s" The definition will be renamed "%s" usage: nimdef [-pcd] -f filename %d machine definition is complete. The following machine will be added to the NIM environment: %d machine definitions are complete. The following machines will be added to the NIM environment: %d additional interface will be defined for a machine: %d additional interfaces will be defined for machines: %d machine will not be added because definitions are incorrect: %d machines will not be added because definitions are incorrect: %d machine group will be created with new members. %d machine groups will be created with new members. %d existing machine group will have new members added. %d existing machine groups will have new members added. %d network definition will be added to the NIM environment automatically. %d network definitions will be added to the NIM environment automatically. %d network in the NIM environment will have new machine interfaces added. %d networks in the NIM environment will have new machine interfaces added. # Commands to define new machines in the NIM environment. # Commands to define new interfaces in the NIM environment. # Commands to define new groups and members in the NIM environment. # Commands to add new members to existing groups in the NIM environment. #!/bin/ksh set -x ############################################################################ # # Summary # %3d Machine will be added to the NIM environment. %3d Machines will be added to the NIM environment. %3d Additional interface will be defined for a machine. %3d Additional interfaces will be defined for machines. %3d Machine will not be added because definitions are incorrect. %3d Machines will not be added because definitions are incorrect. %3d Machine group will be created with new members. %3d Machine groups will be created with new members. %3d Existing machine group will have new members added. %3d Existing machine groups will have new members added. %3d Network will be added to the NIM environment automatically. %3d Networks will be added to the NIM environment automatically. %3d Network will have new NIM machine interfaces added. %3d Networks will have new NIM machine interfaces added. >>>> Creating NIM clients from the client definition file. >>>> Removing any client definitions that may have been created. Client machines were not created successfully. Restoring files from %s to %s ... Creating boot images in %s ... WARNING: There may be other platforms that will be supported in this environment after SPOT resources are defined. The following is a list of defaults: Kernel for Single Processor MachinesKernel for Multiprocessor Machines Creating SPOT in "%s" on machine "%s" from "%s" ... Restoring files from BOS image. This may take several minutes ... This may take several minutes. View the log: %s on machine "%s" for progress ... Checking filesets and network boot images for SPOT "%s". This may take several minutes ... Performing software maintenance in the SPOT's root directory: %s. This may take several minutes ... Installing software in the SPOT's root directory: %s. This may take several minutes ... Performing software maintenance in the root directories of any diskless or dataless clients served by this SPOT. This may take several minutes ... Installing software in the root directories of any diskless or dataless clients served by this SPOT. This may take several minutes ... Performing software maintenance "%s" ... The group "%1$s" contains members of type "%2$s".update_all = update all currently installed filesets Be sure to check the output from the SPOT installation to verify that all the expected software was successfully installed. You can use the NIM "showlog" operation to view the installation log file for the SPOT. Status: Pending: %d Installing: %d Complete: %d Failed: %d Concurrency Control Concurrency Control: "%s" Operation Summary Processing will begin with the first %s machines from the group... The first %s machines have been processed. As machines finish installing processing will resume with the remaining members of the group, one at a time. ***** The time limit of %1$s hours has expired. The "%2$s" ***** operation will not be initiated on any more machines in this group. Fix the problem with any failing targets and retry the operation. Enabling the %1$s operation on machine %2$d of %3$d: information is missing from this object's definitiona NIM operation has been scheduled for this objectdiskless or dataless boot is enableddiskless resources are being initializeddataless install has been enableddiagnostic boot has been enabledcustomization is being performedBOS installation has been enabledBase Operating System installation is being performedcustomization is being performedpost install processing is being performedsoftware maintenance is being performedmaintenance boot has been enabledlppchk operation is being performeda client is being prepared for alt_disk_installalt_disk_install operation is being performedthe NIM operation specified by the p_Cstate attribute was successfulthe NIM operation specified by the p_Cstate attribute encountered a fatal error and did not completea user has aborted a NIM operation by executing the reset operationclass of NIM objects which represent machinesNIM object class which represent install resourcesclass of NIM objects which represent networksused to group NIM predefined object classesused to group NIM predefined object typessubset of operations which effect client Cstategroups info which can be customized for an objectgroups customization resource types togetheridentifies information about ROS supportgroups network interface attributes togetherall filesystems & resources remotelocal paging,dump; remote /,/usr; others remote or localmachine which controls the NIM environmentShared Product Object Tree - equivalent to /usr filesystemrepresents the network boot resourceparent directory for client / (root) directoriesparent directory for client paging filesparent directory for client dump filesparent directory for client /home directories/home directory shared by clientslist of optional packages required by all SPOTslist of optional packages required by NIMlocation of a directory which NIM has exportedpathname of first directory which NIM createdparent directory for client /tmp directoriesparent directory for client /var/adm/ras directoriessource device for optional product imagesdirectory where required optional product images are storedconfig file used during base system installationconfig file used during base system installationan executable file which is executed on a clientdirectory containing customization scripts created by NIMindicates that client initiated the operationflag that causes resource access point to be displayedcauses resource to be mounted at specified locationindicates that operation will update state asynchronouslyused internally by NIM to bypass state checkingidentifies which NIM class an object belongs toidentifies the NIM type for an objectunique object identifier which is specified by the userthe time when a scheduled NIM operation will occurarguments for the command specified in the ATTR_AT attributethe job number associated with the scheduled operationdefines cmd to execute when specific state transition occursflags to use with the installp commandfileset names to use with the installp commandoptions & option arguments to use with lslpp commandflag used to override NIM state checkingflag used to obtain verbose output from NIM operationsflag used to pass optional package namesflag used to indicate that debug output is requestedflag used internally to specify a specific NIM subclassinformation missing from an object's definitionindicates that client will not remain a NIM clientused to relate state specific information to the userindicates that the object is for NIM internal use onlyname of machine which has control over the objectstore the object's previous NIM statemachines which use a resource served by specified machinemachines which serve a resource used by specified machinemachines which use the specified resourceresources which may be used by the specified machineresources used by specified machinemachines attached to specified networkschedule an operation to occur at a specified timeinitialize a diskless machines's environmentinitialize a dataless machines's environmentenable a machine to boot a diagnostic imagelist LPP information about an objectcheck the status of a NIM objectmodels which support booting from integrated ethernetmodels which support booting from MCA token ring adaptersmodels which support booting from MCA ethernet adaptersmodels which support booting from MCA FDDI adaptersprimary network interface (stanza format)network interface (stanza format)identifies the device containing the ROS emulationidentifies a resource which the machine servesname of machine which serves the resourcespecifies network interface types supported by a SPOTnumber of times a specific resource has been allocatedlocation of files needed to create a resourcerouting information for a networkring speed for token-ring networksindicates that command executing in boot environmentpathname of a directory which NIM has createdused to retain NIM resources after installaddress of the enter_dbg symbol within the UP kerneladdress of the enter_dbg symbol within the MP kerneldefines the acceptable mask for the stat.st_mode of a filedefines acceptable values for the stat.st_vfstype of a filenum diskless/dataless roots to sync in parallelbypasses rebuilding of network boot imagesvalue of ST_COMMITTED in /usr/include/swvpd.h filevalud of ST_APPLIED in /usr/include/swvpd.h filedefines the device where the IPL ROM emulation residesindicates that root directory already initializeddefines ethernet cable type for the client's interfaceused to signify that a resource is a CDROMan operation for NIM internal use onlyused to store characteristics of individual objectsattributes only used to pass info to NIM operationsthe set of possible results from NIM operationssubset of attributes which require a sequence numbersubset of resource types which diskless can usesubset of resource types which dataless can usesubclass of operations which may be pulledflag to automatically expand filesystemssubset of resource types which standalone can usesubset of resource types which master can usesubset of resources of which only 1 can be usedsubset of resources that are parent directoriessubset of resources which form network boot supportsubset of attributes which are used as flags onlyunconfigure the NIM master filesetthe port number used for master/client socket communicationspecifies the type of hardware platform a machine usesattributes which define the platform choicesRISC System 6000 Symmetric Multiprocessoraddress of the enter_dbg for the specified platform typemachine configuration types which are supported for rs6kmachine configuration types which are supported for rs6ksmpmachine configuration types which are supported for rspcflag/keyword used to process default routes and resource groupsother network interface types which are represented by the same networkinforms the master that network boot images need to be rebuiltIBM Personal Computer Power Seriesspecifies network adapter hardware addresssynchronize roots for all clients using specified SPOTfix keywords to specify to the cust or fix_query operationfix (keyword) input file for the cust or fix_query operationperform queries on installed fixesoptional flags for modifying output of fix_query operationclient should be modified to accept NIM push installsindicates that client should not be rebootedset normal mode boot list if no_client_boot=yesdisplay re-installation warning to users on target machineenable a machine to boot in maintenance modeindicates if the client should be rebootedoptional flags to be used when creating a mksysb resourcefiles to be excluded when creating a mksysb imageshow space required when creating a mksysb imagethe port number used for client registrationa group of machines or resourcesa name of a machine or resource that belongs to a groupa NIM operation associated with a resource groupoptional arguments associated with resource group and an operationspecifies the name of the current default resource groupselect or deselect group membersexclude group members from operations on the groupexclude all group members from operations on the groupinclude group members in operations on the groupinclude all group members in operations on the grouphidden attribute to mark excluded group membersdisplay a log in the NIM environmentshow the entire log (as opposed to a log of the last session)specifies the type of log to be vieweda new member being added to a groupa member being removed from a groupattribute for saving error informationflag used to indicate target is temp group created by nimflag used to tell NIM to display progressreference machine to use when showing resource informationresource to examine with the showres commandsm_inst flags to use with the showres operationinstfix flags to use with the showres operationcontrols client mount access restrictions when exporting resourcesused in the if attribute to find matching network definitionconfiguration file for name-server informationspecifies info required to create network definition when defining a NIM machinespecifies the lppchk_flags for the lppchk operationfile to use as a temporary bundle resource in SMITPowerPC Symmetric Multiprocessor Computermachine configuration types which are supported for rspcsmpRepresents the new name for a NIM object.generic network (no network boot capability)dataless resources are being initializedcontains up to date info on a machine being BOS installedonly refresh GUI periodically when the count of BOS install machines is greater than this number (default = 4)determines time (in seconds) that should pass between GUI refreshes during BOS install (default = 19)specifies whether the network is an IEEE 802.3 ethernet network.specifies whether a client may allocate resources.specifies whether a machine may register itself as a NIM client.specifies whether nimclient commands have their cpu id validated.specifies whether NIM resources get exported on a global scale.specifies that a platform is defined in a SPOT.specifies whether a network interface/platform combination has been defined for a machine in the environment.specifies whether all possible boot images should be built rather than just those associated with defined machines.specifies whether the set of platform/kernel/network combinations defined for machines in the environment should be regenerated.specifies a target disk or disks for an operationperform an alt_disk_install operation on a clientspecifies the level of a mksysb resourcespecifies that detailed output should be displayedspecifies that a boot image should be NFS exportedspecifies the name of a client niminfo filespecifies the name of a client boot imagespecifies a new type for a NIM objectspecifies the phase of an operation to be performedspecifies the number of clients in a group to be operated on concurrentlyspecifies the amount of time to operate on clients in the groupdetermines time (in seconds) that should pass between status messages for Group Control operations (default = 900)specifies the maximum number of threads to use with the nimesis daemon (default = 20).specifies the maximum number of times that a client machine should retry to issue a state change (default = 0).specifies the number of "nim_script" resources currently allocated from this master.Used by the Service Provider LPPUsed by the Service Provider LPPNIM functions by modeling some aspects of the physical environment in which it is operating. To do this, NIM requires that each physical entity that is going to participate be represented by a unique object in the NIM database. Each NIM object is organized into a specific object class and type, and each is identified by a unique name that is assigned by the user. This attribute defines the class of NIM objects that is used to represent the machines that exist in your NIM environment. Each machine that is going to participate in the NIM environment must be represented by its own, unique machine object. This object can be created in two ways: -> Use the "define" operation on the NIM master. This operation requires you to supply the type of object being defined and, in this case, type refers to the machine's configuration type. Use the lsnim command to display a list of supported machine types: # lsnim -p -c machines -> From a running, standalone machine on which the bos.sysmgt.nim.client package has been installed, you can run the niminit command. This command contacts the NIM master and asks it to create a new machine object for that machine. Once a machine object has been defined to represent a machine, you can perform operations on it. Use the lsnim command to display a list of supported operations: -> To display supported operations based on the object type, enter: # lsnim -p -O -t -> To display supported operations based on the object name, enter: # lsnim -O NIM functions by modeling some aspects of the physical environment in which it is operating. To do this, NIM requires that each physical entity that is going to participate be represented by a unique object in the NIM database. Each NIM object is organized into a specific object class and type, and each is identified by a unique name which is assigned by the user. This attribute defines the class of NIM objects that is used to represent the resources that exist in your NIM environment. Each resource that you want to use in the NIM environment must be represented by a unique resource object: use the "define" operation to do this. Note: This operation requires you to supply the type of resource being defined. You can use the lsnim command to display a list of supported NIM resource types: # lsnim -p -c resources Once this kind of object has been defined, it can be used to support other NIM operations. To use a resource during a NIM operation that is performed on a machine object, NIM requires you to first perform the "allocate" operation, which is a preparatory step that: -> Verifies the machine which is going to use the resource (the client) can access the machine that is serving the resource (the server). NIM uses its connectivity algorithm to determine whether this communication is possible. -> Verifies the client's configuration type is allowed to use a the specified resource type. -> Verifies that the specified resource is available for use. If all of these conditions are met, then NIM grants the client access to the resource by using NFS to export it for the client's use. To indicate that a resource has been allocated to a machine, NIM adds an attribute of the resource's type to the machine's definition. The value of this attribute will be the NIM name of the allocated resource. Once a resource has been allocated to a client, it remains allocated until the deallocate operation is performed. For deallocation, NIM removes the client's export permissions to access the resource and removes the attribute that was added to the client's definition to indicate that the resource was allocated for use. NIM functions by modeling some aspects of the physical environment in which it is operating. To do this, NIM requires that each physical entity that is going to participate be represented by a unique object in the NIM database. Each NIM object is organized into a specific object class and type, and each is identified by a unique name that is assigned by the user. This attribute defines the class of NIM objects that is used to represent the networks that exist in your NIM environment. Each network that is part of your NIM environment must be represented by a NIM network object. Use the "define" operation to create a new network object. Note: This operation requires you to supply the type of network being defined. Use the lsnim command to display a list of supported NIM network types: # lsnim -p -c networks not used - the text for VERBOSE_ATTR_CLASS_ATTRS is used NIM operates in a distributed environment in which NIM operations can occur synchronously or asynchronously. To coordinate these operations, NIM enforces concurrency control among NIM objects by maintaining state information for each NIM object. This information is managed entirely by NIM and is updated in response to the NIM operations that you perform and other conditions that NIM is able to detect. NIM states are stored in attributes that are part of every object's definition. The specific attribute used is dependent upon the object's class: -> "Mstate" and "Cstate" are used for objects in the machines class. -> "Rstate" is used for objects in the resources class. -> "Nstate" is used for objects in the networks class. This attribute is maintained as part of an object's definition, and the attribute is used to indicate the result of the previously executed NIM operation. When the result indicates that a failure has occurred, NIM may have added other attributes to the object's definition that provide you with more information about why the operation failed. NIM classifies its management information into classes and types. Sometimes, NIM also needs to group objects within the same class in different ways. NIM does this using subclasses: Each subclass represents a grouping of object types within that object class. Most NIM subclasses are for internal NIM use only; however, some subclasses may be used by the user. Use the lsnim command to list the subclasses you can specify. NIM functions by modeling some aspects of the physical environment in which it is operating. To do this, NIM requires that each physical entity that is going to participate be represented by a unique object in the NIM database. To organize this information, NIM classifies each object into a specific class and type. You can display the list of object classes which NIM supports using the lsnim command: # lsnim -p To display a list of object types for a specific object class, enter: # lsnim -p -c NIM functions by modeling some aspects of the physical environment in which it is operating. To do this, NIM requires that each physical entity that is going to participate be represented by a unique object in the NIM database. Each object is classified into a specific class and type. Use lsnim to display the list of supported object classes. # lsnim -p To display list of object types for a specific object class, enter: # lsnim -p -c This subclass identifies predefined NIM attributes that are NIM operations. This subclass identifies NIM predefined attributes that are NIM control operations. NIM control operations represent the subset of NIM operations that control processing on a target machine. This subclass identifies NIM predefined attributes that can be added to an object's definition (either internally by NIM or by the user) and relate specific information about the object they are associated with. This subclass identifies NIM objects that represent types of BOS images that can be installed by NIM. This subclass identifies NIM objects that represent types of resources that can be used to perform customization on a target. This subclass identifies NIM attributes that store NIM network interface information for a machine. This subclass identifies NIM resources of which only one of that resource type may be allocated to a specific client. That is, if a NIM client has a resource allocated to it which belongs to this subclass, NIM will not allow any other resources in this subclass to be allocated to the client at this time. This subclass identifies NIM resource types that represent the location of "parent" directories in which NIM creates client subdirectories for each client the resource is allocated to. The network boot resource is a complex resource type consisting of several parts. This subclass groups the parts together. This attribute represents a type of machine configuration in which all of the machine's required resources are accessed remotely. The required resources for any machine are those resources the machine needs to achieve the running execution state and consist of: -> The standard file systems (/, /home, /tmp, and /usr) -> A boot image -> A paging device -> A dump device This attribute represents a type of machine configuration in which some of the machine's required resources are local and some are remote. The required resources for any machine are those resources the machine needs to achieve the running execution state and consist of: -> The standard file systems (/, /home, /tmp, and /usr) -> A boot image -> A paging device -> A dump device For this machine configuration, the following resources are remote: -> /, /usr -> Boot image the following resources are local: -> Paging device -> Dump device and the following resources may be local or remote: -> /home, /tmp This attribute represents a type of machine configuration in which all of the machine's required resources are accessed locally. The required resources for any machine are those resources the machine needs in order to achieve the running execution state and consist of: -> The standard file systems (/, /home, /tmp, and /usr) -> A boot image -> A paging device -> A dump device For this machine configuration, all these resources are accessed locally. This attribute represents a special type of machine configuration within the NIM environment. it is the only machine allowed to push operations on other machines. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a Shared Product Object Tree (SPOT). SPOTs are important resources in the NIM environment because they are used to support all NIM operations that require a machine to boot using a network interface. SPOTs are created and managed by NIM. There are two ways to construct a SPOT: -> A /usr file system on a running NIM standalone client can be converted into a SPOT -> A SPOT may be created from scratch in a parent directory that you specify. In either case, SPOTs are large and occupy approximately 130MB of space in the file system where they are created. Additionally, the network boot images that are created with the SPOT are stored in the /tftpboot directory on the server of the SPOT and occupy approximately 30 megabytes of space. This attribute is the NIM resource type that represents the network boot resource, which is one of resources required to support a network boot operation for a NIM client. NIM automatically defines a resource of this type when the bos.sysmgt.nim.master package is configured for use. NIM also manages the use of this resource in response to those NIM operations you perform that require a network boot; that is, NIM automatically performs allocation and deallocation of this resource in response to other NIM operations that you perform. The network boot resource is composed of the following parts, all of which reside on the server of the SPOT used to support the network boot operation: -> client specific stanza in the /etc/bootptab file -> /tftpboot/ file -> /tftpboot/.info file When NIM allocates this resource to a client in response to a NIM operation you've performed that requires a network boot, NIM adds this attribute to the client's definition to indicate that this resource has been allocated to the client; conversely, NIM removes this attribute from the client's definition when NIM automatically deallocates the network boot resource. Therefore, when you use the lsnim command to display information about a client and this attribute is displayed, it indicates that the NIM environment has been enabled to support a network boot for that client. Note: Having this attribute does not guarantee that the client will actually boot from a network interface: it only means that NIM has set up the environment based on the information you provided. If you experience problems booting a client using a network interface, consult the troubleshooting section in the Network Installation Management Guide and Reference. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a directory in which client root directories are maintained. When this type of resource is allocated to a client, NIM creates a subdirectory for the client's exclusive use. This allocated subdirectory is subsequently initialized when you perform the dkls_init or dtls_init operation. After initialization, anytime the client performs a network boot, the client NFS mounts this subdirectory over / to gain access to the root directory that has been setup for its use. This subdirectory remains mounted over / on the client as long as the client is running. Note: Whenever this resource is deallocated, NIM removes the subdirectory that was created for the client's use. Therefore, any files you want to save in the client's subdirectory should be backed up before you deallocate a resource of this type. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a directory in which client paging files are maintained. When this type of resource is allocated to a client, NIM creates a subdirectory for the client's exclusive use. This allocated subdirectory is initialized by the dkls_init or dtls_init operation, which creates a file in this subdirectory that the client configures as a paging device when it performs a network boot. By default, 32 megabytes is reserved for this file: you may specify a different value using the "size" flag when you perform the dkls_init or dtls_init operation. After this resource has been initialized for a client, it is configured as a paging device by the client each time the client performs a network boot. If you subsequently deallocate this resource, NIM removes the paging file and the subdirectory it created for the client's use. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a directory in which client dump directories are maintained. When this type of resource is allocated to a client, NIM creates a subdirectory for the client's exclusive use. This allocated subdirectory is initialized by the dkls_init or dtls_init operation, which creates an empty file in this subdirectory. After initialization, the client uses this file to store any dump images it creates. Note: If you subsequently deallocate this resource, NIM removes the dump file and the subdirectory NIM created for the client's use. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a directory in which client /home directories are maintained. When this type of resource is allocated to a client, NIM creates a subdirectory for the client's exclusive use. This allocated subdirectory is subsequently initialized when you perform the dkls_init or dtls_init operation. After initialization, anytime the client performs a network boot, the client NFS mounts this subdirectory over /home to gain access to the home directory that has been setup for its use. This subdirectory remains mounted over /home on the client as long as the client is running. Note: Whenever this resource is deallocated, NIM removes the subdirectory that was created for the client's use. Therefore, back up any files you want to save in the client's subdirectory before you deallocate a resource of this type. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a directory which can be used as a common /home directory by one or more clients. When this type of resource is allocated to a client, and when the dkls_init or dtls_init operation is performed, NIM configures the client's configuration to use this common directory. After initialization, anytime the client performs a network boot, the client NFS mounts this common directory over its /home directory. This common directory remains mounted as long as the client is running. Note: Whenever this resource is deallocated, NIM only changes the client's configuration so that this directory is no longer used by the client; NIM does not remove the common directory. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a directory in which client /tmp directories are maintained. When is type of resource is allocated to a client, NIM creates a subdirectory for the client's exclusive use. This allocated subdirectory is subsequently initialized when you perform the dkls_init or dtls_init operation. After initialization, anytime the client performs a network boot, the client NFS mounts this subdirectory over /tmp to gain access to /tmp directory that has been setup for its use. This subdirectory remains mounted over /tmp on the client as long as the client is running. Note: Whenever this resource is deallocated, NIM removes the subdirectory that was created for the client's use. Therefore, back up any files you want to save in the client's subdirectory before you deallocate a resource of this type. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a directory in which client RAS directories are maintained. When this type of resource is allocated to a client and the bos_inst, dkls_init, or dtls_init operation is then performed on the client, NIM initializes the client's configuration so that the client's /var/adm/ras directory is overmounted by this resource when the client performs a network boot. Note: Whenever this resource is deallocated, NIM removes the subdirectory that was created for the client's use. Therefore, back up any files which you wish to save in the client's subdirectory before you deallocate a resource of this type. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a directory in which optional product images are stored. This type of resource can be defined in several ways: -> If you already have a directory that contains optional images, no special attributes need to be supplied. -> If you want to create a directory and have NIM fill it with the set of support images ("simages"), use the "source" attribute. This attribute specifies the name of the device that contains the optional images. NIM copies the "simages" from this device into the specified location of this resource. -> If you want to create a directory, but you want specific options to be copied rather than the default set of "simages", supply the "options" attribute. This attribute tells NIM which packages you want copied. This type of resource is used to support NIM install operations. When you perform a NIM install operation on a client and have previously allocated a resource of this type for the client to use, NIM uses this resource from the client by first NFS mounting the directory where the resource is located, then invoking the installp command with the location of the local mount point where NIM has mounted this resource. When installp finishes, NIM automatically unmounts the resource. To execute successfully, installp requires some information. installp needs the location of the installable images to be installed, and installp needs to know "how" to perform the install; that is, should prereqs be installed automatically?, should file systems be expanded automatically?, and so on. This type of information is passed to installp as flags to the command. By default, NIM uses the "-agX" flags when calling installp. You can override this behavior by supplying the "installp_flags" attribute when you perform the NIM install operation. When you do so, NIM uses those flags when it executes the installp command. installp also needs to know the list of filesets that are to be installed. By default, NIM does not automatically assume that "all" products should be installed. So, in the majority of cases, NIM only installs the filesets it needs to function. You can override this behavior by specifying the filesets you want installed. These filesets can be specified in two ways: -> Supply the "filesets" attribute when performing the NIM install operation. When you do so, NIM uses the filesets you specify when NIM executes installp. -> Use a previously defined installp_bundle resource. When a resource of this type is allocated, and when a NIM install operation is performed on a client, NIM NFS mounts this file and passes the local access point to installp using the installp "-f" option. Note: If you add or remove an installable image from the the lpp_source, perform the check operation on that object so that NIM rebuilds the .toc (table of contents) file, which resides in the lpp_source directory. This is important, as the installp command uses the .toc to determine which images are available. This attribute is used to indicate that an lpp_source type resource contains the set of installable images to which NIM requires access to perform its basic functionality. This basic set of images is referred to as "support images" or "simages". NIM automatically manages the use of this attribute as part of the management of an lpp_source. NIM adds this attribute to the definition of an lpp_source when it provides the required simages, and NIM removes this attribute from the object's definition if a required image becomes unavailable. Some NIM operations require access to an lpp_source that has this attribute as part of its definition, so having this attribute can be important. Perform the check operation on the lpp_source to have NIM to check to see if the simages requirement has been fulfilled. if it has, NIM adds this attribute to the lpp_source definition. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a file that contains the names of optional filesets. Once defined, it can be used in NIM install operations by first allocating it to the target, then performing the desired NIM install operation on the target. When this is done, NIM uses this file when it executes the installp command to: 1) NFS mount this resource so that the client has local access to it 2) Pass the local access point to installp by using the "-f" installp option 3) Unmount this resource when installp finishes Note: To install optional software, the installp command requires access to the installable images for those products. This resource should be used in conjunction with a NIM lpp_source type resource. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a file that contains information which can be used to drive the BOS install program. When a resource of this type is allocated to a client and the bos_inst operation is then performed, NIM causes the BOS install program to use this file during base system installation. You can affect certain aspects of your base system installation by modifying the settings in this file. For example, you can avoid BOS install prompting. However, if you do not use this type of resource for the bos_inst operation, BOS install will use the default data file that resides in the SPOT being used to support the network install operation. The path name of the default data file is /usr/lpp/bosinst/bosinst.template on the server of the SPOT. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a file that contains information which can be used to drive the BOS install program. When a resource of this type is allocated to a client and the bos_inst operation is then performed, NIM causes the BOS install program to use this file during base system installation. You can affect certain aspects of your base system installation by modifying the settings in this file. For example, you can specify the size of the paging device which BOS install creates. However, if you do not use this type of resource for the NIM bos_inst operation, when NIM invokes the BOS install program, BOS install uses the default data file that resides in the SPOT being used to support the network install operation. The path name of the default data file is /usr/lpp/bosinst/image.template on the server of the SPOT. This string is one of the possible values for the "source" flag when this flag is specified for a NIM bos_inst operation. When the string "rte" is used as the value of this flag, NIM uses the BOS run-time image in the lpp_source resource being used to support the install. Other possible values are "spot", indicating that the spot that is supporting the install should be copied into the client's /usr file system, or "mksysb", indicating that an allocated mksysb image should be used. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a file that is a system backup image created using the mksysb command. This type of resource can be used as the source of the BOS run-time files when a base system installation is performed, by first allocating a resource of this type to the target, then performing the bos_inst operation on the target. Note: When you perform the bos_inst operation, the "source" flag should be used with a value of "mksysb". This tells NIM that you want to use the allocated mksysb image. NIM sets up the network boot environment such that BOS install will use this image to populate the client's /usr file system. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a file that is a user-defined shell script. Once defined, this type of resource can be used to perform user-defined processing by first allocating a resource of this type to the target, then performing either the NIM cust or bos_inst operation on the target. When you do this, NIM configures the environment to cause the target to execute the shell script you have defined. Note: When this type of resource is used for a bos_inst operation, your script is executed during the third step in the NIM customization phase. During a bos_inst operation, NIM customization occurs after BOS install performs the base system installation and before BOS install performs post-install processing. During this phase, NIM will enforce the following order: 1) NIM client customization is performed, in which NIM configures the target's primary interface. 2) NIM uses installp to install the optional software you have specified to be installed. 3) NIM executes any user-defined scripts that you have allocated. NIM enforces this order because, by installing optional software first then executing your script, NIM enables you to configure the optional software that NIM installed. This attribute is the NIM resource type that represents executable shell scripts which NIM creates to perform customization operations. NIM automatically defines a resource of this type when you configure the bos.sysmgt.nim.master package. NIM also manages the use of this resource in response to those NIM operations you perform that require customization; that is, NIM automatically performs allocation and deallocation of this resource in response to other NIM operations you perform. NIM performs customization on a target by creating a shell script which NIM then causes the target to execute. NIM constructs this script by examining the types of resources that are already allocated to the target and by using information passed to the NIM operation to perform the customization. You can use the lsnim command to display the attributes that spawn construction of a NIM customization script: # lsnim -p -s cust_subclass This attribute is a NIM network type. When a network of this type is defined, it represents a Token-Ring network. This attribute is a NIM network type. When a network of this type is defined, it represents an Ethernet network. This attribute is a NIM network type. When a network of this type is defined, it represents a FDDI network. This attribute is added to an object's definition to "lock" the object. Because NIM operations can occur synchronously or asynchronously, NIM requires a mechanism to control access to each NIM object. NIM does this in two ways: -> NIM manages persistent states using state attributes. -> NIM provides temporary locks using the "locked" attribute. When a NIM operation begins executing, it accesses information about the object that it is operating on. To prevent this information from being changed when a NIM operation is executing, NIM locks the object it is operating on by adding a "locked" attribute to the object's definition. The value of the "locked" attribute is the process ID of the process that has locked the object. When the operation is done with the object, the "locked" attribute is removed. This attribute is used to store information about the operating system modification number for mksysb and spot resources. This attribute is used to store information about the operating system version number for machines and the spot resource. This attribute stores information about the operating system release number for machines and the spot resource. This attribute passes information to NIM operations and is therefore classified as a "flag". For operations that accept this flag, it specifies how big to make a resource that the operation will create. This attribute specifies user-defined comments to be associated with a NIM object. When specified, this attribute becomes part of the object's definition. NIM manages this attribute in response to NIM operations that you perform. If you perform a NIM operation that causes the definition of an object to become incomplete, NIM adds this attribute to the object's definition to inform you what is missing from that definition. When you correct the error condition NIM removes this attribute from the object's definition. NIM manages this attribute in response to NIM operations that you perform. NIM uses this attribute to relate miscellaneous information about a NIM object by adding this attribute to the object's definition. For example, while a base system installation is occurring on a NIM client, this attribute is updated to reflect the BOS install processing occurring on that client. This enables you to monitor a bos_inst operation as it is being performed. NIM manages this attribute to mark certain objects as reserved for NIM internal use only. NIM manages this attribute, which indicates which machine is currently in control of this object. Because NIM operates in a distributed environment in which multiple NIM operations can be active at any given time, NIM must coordinate access to each NIM object. NIM needs to control operations that are performed on a machine. Because the allocate operation is a preparatory step for NIM install operations, when you allocate a resource, NIM assumes that you are going to perform a NIM install operation soon. Because the allocate operation can be performed from the NIM master or a running NIM client, NIM assumes that the machine requesting the allocation is also going to perform the NIM install operation. To prevent one machine from allocating resources to a specific target while another machine is performs an operation on that same target, NIM adds the "control" attribute to the target's definition when the first resource is allocated to the target. When this attribute is added by NIM, its value is the name of the machine that executed the allocate operation. This is the machine that remains in control of the target until all resources have been deallocated for the target. Having control over a NIM object means that only the machine which is in control of the object may perform operations on it. This attribute is only used to pass information to the nimconfig command and is, therefore, classified as a "flag". It specifies the name of the network that nimconfig will create. This network represents the network that the master's primary interface connects to. This NIM operation creates a new NIM object to represent a physical entity in your environment. Before NIM can be used to perform an operation on a physical entity, the entity must be represented by a NIM object. When you use this operation to create a new object, you must always supply the object's type and the name you want to call the object. Other information may be required depending on the type of object you are creating. Use the following lsnim command to display the attributes that are required to perform this operation on a specific object type: # lsnim -q define -t The name that you give an object will be used in all future operations involving that object. This name must be unique among NIM objects; it must adhere to certain restrictions: -> It must have between 1 and 20 characters. -> It cannot be composed of any shell metacharacters. -> It cannot be composed of any file system metacharacters. -> It cannot be composed of any regular expression metacharacters. Note: A NIM object's name is a "global" name, as each object is only known to NIM by that one name. This is beneficial for multihomed machines. Multihomed machines have more than one network interface. Because a host name must be given to each network interface a machine has, multihomed machines could be known by more than one name. However, in the NIM environment, each machine is identified by its unique NIM object name, so it doesn't matter how many network interfaces the machine has. This NIM operation modifies attribute information for an existing NIM object. NIM objects are composed of a set of attributes that store specific information about that object. Use the following lsnim command to display the attributes that currently make up the object's definition: # lsnim -l Not all of the attributes that comprise an object's definition can be modified. Use the following lsnim command to determine which ones can be modified: # lsnim -q change This NIM operation removes a NIM object from the NIM environment. NIM operations can only be performed on those entities that are represented by a NIM object; therefore, when you remove a NIM object, you remove your ability to perform operations on the entity represented by that object. When this operation is performed on a NIM resource, NIM may actually remove the physical resource which this object represents. This is determined by whether NIM actually created the physical resource when the resource object was defined. If NIM created the resource, then NIM removes the physical resource; if not, NIM does not remove the physical resource. This NIM operation grants a NIM client permission to access a NIM resource. The following factors are used when determining whether a client should be granted permissions: -> The NIM connectivity algorithm is run to verify that the client has the potential to communicate with the server of the resource. This algorithm uses the network interface information you entered for the client and server, and the NIM routing information you entered for the networks that these machines connect to. When this algorithm determines that the client has the potential to communicate with the server, it also determines which network interface on the server should be used by the client. (Note: NIM clients only access NIM resources through one network interface, their primary network interface, which is defined by the if1 attribute.) If the connectivity algorithm determines that the client cannot communicate with the server, permission to access the resource is denied. -> NIM verifies that the client's type is permitted to access a resource of the type being allocated; if not, access permission is denied. -> NIM verifies that the resource being allocated is available for use. This is determined by the resource's state; if it is unavailable for use, access permission is denied. When NIM grants a client permission to access a resource, NIM exports that resource for the client's use and performs the management of the NIM objects to keep track of this allocation. NIM performs this management in two ways. First, a count is kept of how many times a resource has been allocated. This information is stored in the "alloc_count" attribute of the resource, and NIM increments this count each time the resource is allocated. Secondly, NIM adds an attribute to the client to indicate that the resource has been allocated to it. This attribute is added in the form of: = This is the NIM operation that removes a NIM client's permission to access a NIM resource. NIM first verifies that the specified resource has been allocated to the client. If so, NIM removes the client's permission to access the resource by first unexporting the resource, then removing the attribute from the client's definition that NIM added to indicate that the resource was allocated to the client. NIM then decrements the "alloc_count" attribute associated with the resource. This attribute represents the machine state in which the NIM environment has been enabled to support a network boot for a diskless or dataless machine. This NIM operation initializes the resources that have been allocated to a machine with the diskless configuration type. This processing includes: -> Populating the root directory that has been allocated for the client's use with the prototype root files from the client's SPOT -> Configuring the appropriate client root files so that it can achieve the running execution state -> Creating a paging file of the appropriate size for the client to use as its paging device -> Allocating the network boot resource for the client's use When this operation returns successfully, the NIM environment is enabled to support the dataless client. This NIM operation initializes the resources that have been allocated to a machine with the dataless configuration type. This processing includes: -> Populating the root directory that has been allocated for the client's use with the prototype root files from the client's SPOT -> Configuring the appropriate client root files so that it can achieve the running execution state -> Allocating the network boot resource for the client's use When this operation returns successfully, the NIM environment has been enabled to support the dataless client. This NIM operation enables the NIM environment to support a network based, diagnostic boot for a machine. Because this operation only enables the environment, it is up to the user to cause the client to begin the network boot process by issuing a BOOTP request. Refer to the Network Installation Management Guide and Reference for procedures on how to initiate the network boot process. This NIM operation performs software customization on a running NIM client. This NIM operation performs base system installation on a machine. In addition to base system installation, customization may also be performed by allocating the appropriate resources before the bos_inst operation is performed. This NIM operation performs software maintenance operations. This NIM operation resets an object's NIM state by stopping any current NIM operation being performed on it. In some cases, NIM is not be able to stop an active operation. This NIM operation uses the lslpp command to display optional software product information for a NIM object. This NIM operation performs verification on a NIM object. The type of verification performed depends on the object's type. NIM manages this attribute, which stores the execution state for a machine. NIM attempts to keep the value of this attribute synchronized with the machine's execution state, but NIM does not guarantee that its accuracy. Perform the "check" operation on the machine for NIM to attempt to determine the machine's execution state. NIM manages this attribute, which indicates the NIM operation that is being currently being performed on a machine or that no NIM operations are currently being performed. This attribute is managed by NIM and is used to indicate the previous NIM state for a NIM object. This attribute is managed by NIM and is used to indicated the result of the previous NIM operation which was performed on a machine. This attribute stores network interface information for a NIM client and requires a sequence number when specified. This information consists of three required fields and a fourth, optional field: field 1 = Name of the network to which this interface connects field 2 = Host name associated with this interface field 3 = Network adapter hardware address of this interface field 4 = Logical device name of the network adapter used for this interface If the fourth field is not specified, NIM uses a default based on the type of network interface defined. This attribute requires a sequence number for NIM to distinguish between multiple network interfaces. Because machines can be multihomed, NIM allows more than one "if" attribute per machine. NIM manages this attribute, which stores the names of the resources which a machine serves. NIM adds this attribute to the definition of a machine each time a NIM resource is defined using that machine as the server. This attribute stores the CPU ID of a machine. NIM manages this attributes, which indicates that a NIM operation can be pushed onto a client. NIM manages this attribute, which indicates whether a resource is available for clients to use. The following factors are used to determine availability: -> The definition of the resource must be complete. This determination is based upon the resource type. -> The server of the resource must be accessible. NIM considers a a server to be inaccessible if a base system installation is being performed on it. This attribute stores the NIM name of the server that is serving the NIM resource. This attribute stores the path name of a NIM resource. It is required for all NIM resources. NIM manages this attribute, which indicates the type of network interface which is supported by a SPOT. Because SPOTs may support more than one interface type, a SPOT may have more than one of these attributes. Note that this is one piece of information that is used to determine whether a SPOT can be allocated to a machine: the SPOT must support the client's primary interface type for the client to use it. NIM manages this attribute, which keeps track of the number of times a NIM resource is currently allocated to a NIM client. This attribute is only used to pass information to NIM operations and is therefore classified as a "flag". For those operations that accept this flag, its value indicates the NIM resource or device that will supply the images that are required by the NIM operation. NIM manages this attribute, which indicates whether the object definition of the network is complete. NIM requires that all networks be able to communicate with the NIM master, either by the master being directly connected to them or by having a NIM route to a network to which the master connects. This attribute stores the network address that is used by a network. This attribute stores the subnet mask that is used by a network. This attribute stores NIM routing information for a network. The attribute requires a sequence number when specified. When a new NIM route is specified, its value consists of three fields: field 1 = NIM name of the destination network to which the route is being added field 2 = Host name of the gateway to use in order to communicate with the destination network field 3 = Host name of the gateway that the destination network uses to get back to the originating network When NIM adds a "routing" attribute to a network's definition, NIM only includes the first two fields. NIM requires three fields for a new route because NIM automatically adds a "routing" attribute for the destination network; the third field is required to do this. This attribute stores the ring speed that is used for a Token-Ring network interface. The attribute requires a sequence number when specified. A sequence number is used to match this information with a corresponding "if" attribute. This attribute is not allowed without a corresponding "if" attribute. This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, its value specifies the logical interface name of the network interface used as the primary network interface. This attribute stores the port number used for NIM socket communication between the NIM master and NIM clients. This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, it specifies a network adapter hardware address. NIM manages this attribute, which stores information used to enable the NIM environment to support a network boot for a NIM client. Specifically, the string "ip" in the target's /etc/bootptab stanza specifies the IP address that the target should use when configuring its network interface. NIM manages this attribute, which stores information used to enable the NIM environment to support a network boot for a NIM client. Specifically, the string "ha" in the target's /etc/bootptab stanza specifies the target's network adapter hardware address. NIM manages this attribute, which stores information that is used to enable the NIM environment to support a network boot for a NIM client. Specifically, the string "ht" in the target's /etc/bootptab stanza specifies the type of network interface the target will use to boot from. NIM manages this attribute, which stores information used to enable the NIM environment to support a network boot for a NIM client. Specifically, the string "bf" in the target's /etc/bootptab stanza specifies the path name of the target's network boot image. NIM manages this attribute, which stores information used to enable the NIM environment to support a network boot for a NIM client. Specifically, the string "gw" in the target's /etc/bootptab stanza specifies the IP address of the gateway that the target should use in order to tftp its network boot image. NIM manages this attribute, which stores information used to enable the NIM environment to support a network boot for a NIM client. Specifically, the string "sm" in the target's /etc/bootptab stanza specifies the subnet mask that should be used by the target when configuring its network interface. NIM manages this attribute, which stores information used to enable the NIM environment to support a network boot for a NIM client. Specifically, the string "sa" in the target's /etc/bootptab stanza indicates the server IP address that should be used when responding to the target's BOOTP request. NIM manages this attribute, which stores information used to enable the NIM environment to support a network boot for a NIM client. NIM manages this attribute, which indicates when a NIM resource resides on CD-ROM. This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, its presence indicates that the bos.sysmgt.nim.client fileset, which normally would be installed and configured as part of the operation, should not be installed. This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, its presence indicates that the access point on the server should be displayed for each resource being allocated by the operation. This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, its value specifies the directory on the target over which the NIM resource being allocated should be mounted. This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, its value specifies the flags that should be used when NIM invokes the installp command to perform an operation on optional software products. This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, its value specifies names of optional software filesets that should be used in the operation. This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, its value specifies the flags that are to be passed to the lslpp command, which NIM invokes to display information about optional software products. This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, its presence is used to indicate that the normal state checking procedures that NIM uses to synchronize NIM operations should be bypassed. In some cases, NIM is able to bypass the checking and perform the requested operation; in other cases, NIM does not allow the checking to be bypassed. This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, it is used to specify the level of verbose output NIM operations should display. Verbose output contains more information than is normally displayed by NIM operations, which can help diagnose problems encountered during a NIM operation. The value of this attribute is a positive integer between 1 and 5. The larger the value, the greater the amount of output. This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, it specifies the names of optional software products. This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, it indicates that the kernel debugger should be enabled when building network boot images. Having the kernel debugger enabled aids the user in diagnosing network boot failures. Refer to the troubleshooting section of the Network Installation Management Guide and Reference for more information on diagnosing network boot failures. This attribute is only used to pass information to the bos_inst operation and is, therefore, classified as a "flag". The bos_inst operation performs a base system installation on the specified machine, which can destroy the target's current file systems. Therefore, if the target is serving NIM resources, the bos_inst operation could actually remove them. NIM assumes this condition by default and removes the resource definitions corresponding to those resources when the target gets installed. You can override this behavior by providing this attribute when you perform the bos_inst operation. This attribute is used store the address of the "enter_dbg" symbol in the UP version of the kernel. This information is useful when debugging network boot failures. Refer to the troubleshooting section of the Network Installation Management Guide and Reference for further details on how to debug network boot failures. This attribute becomes part of a SPOT's definition when you specify the "debug" attribute when performing an operation on the SPOT. The "debug" attribute tells NIM to enable the kernel debugger when rebuilding the network boot images associated with the SPOT. As part of that processing, NIM determines what the address of the "enter_dbg" symbol is and adds this attribute to the SPOT's definition so that the user has easy access to it. This attribute is subsequently removed anytime a SPOT operation is performed without the "debug" attribute. This attribute is used store the address of the "enter_dbg" symbol in the MP version of the kernel. This information is useful when debugging network boot failures. Refer to the troubleshooting section of the Network Installation Management Guide and Reference for details on how to debug network boot failures. This attribute becomes part of a SPOT's definition when you specify the "debug" attribute when performing an operation on the SPOT. The "debug" attribute tells NIM to enable the kernel debugger when rebuilding the network boot images associated with the SPOT. As part of that processing, NIM determines what the address of the "enter_dbg" symbol is and adds this attribute to the SPOT's definition so that the user has easy access to it. This attribute is subsequently removed anytime a SPOT operation is performed without the "debug" attribute. This attribute is only used to pass information to NIM operations and is therefore classified as a "flag". For those operations that accept this flag, its value specifies the number of diskless and dataless root directories that should be "sync"d in parallel. Diskless and dataless machine configurations use a remote directory (a SPOT) as their /usr file system. Whenever an installp operation is performed on the SPOT, the corresponding operation must be performed on their root directories in order to keep the root and usr parts of their software products in synchronization. That operation is referred to as a "root sync" and NIM automatically performs it whenever the SPOT is operated on. By default, NIM performs five root sync operations at the same time. You can change this behavior by using this attribute to specify the number of root syncs you want to be performed in parallel. This attribute is used to store the name of device that contains the IPL ROM emulation for machines requiring the IPL ROM emulation in to perform a network boot. This attribute stores the type of cable used for an Ethernet network interface. The attribute requires a sequence number when it is specified. A sequence number is used to match this information with a corresponding "if" attribute: this attribute is not allowed without a corresponding "if" attribute. Attributes represent pieces of information that NIM requires. This information is passed to NIM commands using command line syntax in the form of: -a = The attribute name that you supply must be a valid NIM attribute, and it must be one of a list of specific attributes accepted by the NIM operation you are currently performing. Use lsnim to display the attributes which any NIM operation accepts: # lsnim -q -t NIM classifies attributes into two subclasses: -> "info_attrs" are those attributes that provide information about a specific characteristic of a NIM object and, hence, become part of the object's definition. -> "flag_attrs" are only used to pass information to NIM operations and do not become part of an object's definition. Use the lsnim command to display the list of NIM attributes that belong to each of these subclasses: # lsnim -p -s info_attrs # lsnim -p -s flag_attrs This attribute classifies the NIM attributes that require a sequence number. NIM requires that a sequence number be appended to the attributes that can added to an object's definition more than once. For example, many "if" attributes can be added to a machine's definition and, to distinguish between them, NIM requires you to append a sequence number to each one. This attribute classifies NIM resources that may be allocated to machines of the diskless configuration type. This attribute classifies NIM resources that may be allocated to machines of the dataless configuration type. This attribute classifies the NIM operations that may be initiated from NIM clients. This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, its presence indicates that file systems should be automatically expanded if space is needed for a NIM operation. This attribute classifies NIM resources that may be allocated to machines of the standalone configuration type. This attribute classifies NIM resources that may be allocated to machines of the master configuration type. This NIM operation unconfigures the NIM master fileset. Use this operation before you deinstall the NIM master fileset with installp. This attribute is used to specify the type of platform a machine uses. By default, a machine belongs to the rs6k family...... This attribute is used to classify NIM machines by their hardware platform type. This attribute represents the RISC System 6000 machine platform type. This attribute represents the RISC System 6000 Symmetric Multi- processor machine platform type. This attribute represents the RISC Personal Computer System machine platform type. This attribute is used to store the address of the enter_dbg symbol in the kernel used to create the network boot image associated with the specified platform type. This attribute is added to a SPOTs definition when you use NIM to create network boot images which have the kernel debugger enabled, which helps you to diagnose network boot failures. This attribute is used to classify NIM configuration types which are supported for the rs6k platform type. This attribute is used to classify NIM configuration types which are supported for the rs6ksmp platform type. This attribute is used to classify NIM configuration types which are supported for the rspc platform type. This attribute is used as a flag or keyword to indicate that a NIM route or resource group being manipulated is a default. Each NIM network is used to represent one logical network which exists in the NIM environment. When the network is defined, the type of network interface used in the network must be supplied. Usually, a network will be composed of only one type. However, a bridge can be used to connect network types together to form one logical network. In that situation, NIM needs to know that the other network interface types are and this attribute is used to specify that information. This attribute is managed by NIM. The attribute indicates a change occured to the SPOT. NIM uses this attribute to know when to rebuild the network boot images. This attribute represents the IBM Personal Computer Power Series platform type. This attribute is used to store the name of the device that contains the IPL ROM emulation software. IPL ROM emulation is required for machines which do not have BOOTP-enabled IPL ROM. This attribute is used to specify the type of platform a machine uses. By default, a machine belongs to the rs6k (RISC System 6000) family. Other supported families include rspc (IBM Personal Computer Power Series) and rs6ksmp (RISC System 6000 Symmetric Multiprocessor). This attribute is used to pass information to NIM about the hardware address. It is classified as a "flag". It is used both internally and via the command line when the niminit command is unable to automatically ascertain the hardware address of the primary network interface. This NIM operation synchronizes root directories for all diskless anddataless clients which use the specified SPOT. This attribute represents the PowerPC Personal Computer platform type. This attribute is used to specify the type of platform a machine uses. By default, a machine belongs to the rs6k (RISC System 6000) family. Other supported families include rspc (PowerPC Personal Computer) and rs6ksmp (RISC System 6000 Symmetric Multiprocessor). This attribute is used in combination with the cust and fix_query operations. It provides a NIM interface to the instfix command which allows software to be updated and viewed via fix keywords. A fix can be made up of either a single fileset update or multiple fileset updates that are related in some way; fixes are identified by unique keyword. When a fix is identified with an APAR number, it will include all the fileset updates that are necessary to fix the reported software problem that is identified by that number. You may update all the filesets you currently have installed, with applicable software from the source being used for the cust operation, by specifying a value of "update_all" for the fixes attribute: ie. "-afixes=update_all". Note: when doing an "update_all" it is advisable to use options to the installp command which cause updates to be committed without saving temporarily replaced files. This is the -cN flag combination or the following settings from the SMIT interface: "COMMIT software updates?"=yes, "SAVE replaced files?"=no. In doing so, you will not be able to revert to the previous level of files being updated but you will use less space. This attribute is a NIM resource type. When a resource of this type is defined, it represents the location of a file that contains fix keywords to be used by the instfix command which is called by the cust and fix_query operations. Once defined, this resource can be used by first allocating it to the target, then performing the NIM operation on the target. (Note that for SPOT targets you use this resource by specifying fix_bundle as an attribute, ie. you do not allocate the resource first.) When this is done, NIM uses this file when it executes the instfix command to: 1) NFS mount this resource so that the client has local access to it 2) Pass the local access point to instfix by using the "-f" instfix flag 3) Unmount this resource when instfix finishes See the "fixes" attribute for more details on fix keywords. This NIM operation displays whether specified fix keywords are installed on a client or SPOT. The "fixes" or "fix_bundle" attributes are used to specify fix keywords to the operation. If neither "fixes" nor "fix_bundle" are specified, all known fixes are displayed. This operation provides a NIM interface to a subset of the query capabilities of the instfix command. See the "fixes" attribute for more details on fix keywords. This attribute is used to specify optional flags to the fix_query operation. Valid flags are: -a Displays symptom text. -c Displays output in colon separated format. -F Returns failure unless all filesets associated with a fix are installed. -q Quiet option. If -c is specified, no heading is displayed. -v Verbose option. Gives information about each fileset associated with a fix (keyword). This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, its presence indicates that the client should be modified to accept commands from the NIM server, even if the client is not currently configured as a NIM client. This attribute is only used to pass information to NIM operations and is, therefore, classified as a "flag". For those operations that accept this flag, its presence indicates that the client should not be shutdown and rebooted as part of this operation. It is reasonable to set this flag if the server is to perform operations to enable a client operation which is to be initiated at a later time. This NIM operation will cause the targeted machines to be rebooted. This attribute is used to tell the bos_inst operation that an attempt should be made to order the list of boot devices on a target machine so that the primary network interface, as defined to NIM, is first. This attribute is only valid if used in combination with the no_client_boot attribute and is only meaningful if set to "yes" when no_client_boot is set to "yes". In all other cases, the attribute is ignored. This attribute is used in combination with the reboot option to display a message to all users on the target system indicating that re-installation will occur after reboot. This attribute would typically be used with the reboot operation after a bos_inst operation had previously been issued with the no_client_boot attribute set to "yes." This operation enables the NIM environment to support a network based, maintenance boot for a machine. Because this operation only enables the environment, it is up to the user to initiate the BOOTP request from the client to begin the network boot. Refer to the Network Installation Management Guide and Reference for procedures on how to initiate the network boot process. For those operations that accept this flag, its presence indicates whether or not the client should be shutdown and rebooted as part of this operation. It is reasonable to set this flag to "no" if the server is to perform operations to enable a client operation which is to be initiated at a later time. This attribute is used to specify optional flags to the mksysb command when creating the mksysb image during the definition of a mksysb resource. Valid flags are: -e Exclude the files and directories listed in the /etc/exclude.rootvg file from the system image backup. -m Generate a layout mapping of the logical to physical partitions for each logical volume in the rootvg volume group. -b [ block_size ] Specifies the number of 512 bytes to write in a single output operation. This attribute may be used when defining a mksysb resource to specify that the system image backup should be created during the definition of the mksysb resource. If the "mk_image" attribute is specified, the "source" attribute must also be used to specify the NIM client for which the backup image should be created. This attribute may be specified when removing a mksysb resource. It specifies that the system backup image should be removed along with the mksysb resource definition. This attribute may be specified when creating a system image backup during the definition of a mksysb resource. It represents a resource that contains files to be excluded from the system image backup. This attribute may be specified when defining a mksysb resource to display the space requirements for creating a mksysb image. The maximum required space along with the space available in the target filesystem will be shown, and the mksysb definition and creation will not occur. This attribute is used to specify the port number that clients can use to register themselves with the NIM master. This class is used to group machines or resources togetherThis attribute is used to specify a group name to be used in a NIM operation. Currently, a NIM machine group can be specified when defining a machine to indicate to which group a machine belongs. Also, a resource group can be specified to the allocate operation or to other installation operations via this attribute. This attribute is used to specify a machine or resource name that is associated with a group.This is a hidden attribute that may be used to associate an operation with a group of resources. NIM does not currently use the operation but the attribute is provided for applications which may use NIM's resource groups. This is a hidden attribute that may be used to associate optional NIM arguments with a group of resources and an optional argument. NIM does not currently use this attribute or the operation attribute but they are provided for applications which may use NIM's resource groups. A group of machines. Machines can be grouped by type: standalone, diskless, or dataless. The NIM master cannot be a member of a machine group. A group of resources. Any valid NIM resource may be specified as a member of a resource group but only one of each resource type may be a member of a group. An exception to this are the installp_bundle and script resources of which there may be more than one occurrence in a resource group. This optional attribute is a member of the NIM master definition. The attribute specifies the name of a default resource group for the master's NIM environment. When an install operation is performed on a NIM machine, all applicable resources that are members of the specified default resource group which are not currently allocated to the machine will be allocated. All occurences of "installp_bundle" and "script" resources in the resource group will be allocated. Select or deselect group members to include or exclude them from operations on the group. Marks a group to exclude specified group members from operations on the group. Marks a group to exclude all group members from operations on the group. Marks a group to include specified group members in operations on the group. Marks a group to include all group members in operations on the group. This operation displays installation and customization logs on NIM clients and SPOTs. By default, the showlog operation will show the output from the last session in the nim.installp log on the showlog target. This behavior can be modified to show the entire log by setting the "full_log" attribute to "yes" The log being viewed can be specified by using the "log_type" attribute. Current values for the "log_type" attribute are: boot, bosinst, devinst, nimerr, niminst, script, and lppchk which map to the log files bootlog, bosinstlog, devinst.log, nimlog, nim.installp, nim.script, nim.lppchk in the directory /var/adm/ras. The "full_log" attribute is not meaningful when viewing the boot, bosinst, or nimerr logs since the entire log is displayed regardless. Show the entire contents of the specified log (instead of the last entry.) Hidden attribute to mark group members that are excluded from operations on that group. Specifies the type of log to be viewed for the "showlog" operation. This attribute is used to specify a member being added to a NIM group. This attribute is used specify a member being removed from a NIM group. This attribute is used to save cumulative error information for a machine being operated on. err_info is different from other attributes in that modification via the change operation appends the error string to the end of existing data. The attribute is reset by specifying an empty string to the change operation. This attribute is used to tell NIM whether or not to display progress while performing various operations. This operation is used to show the contents of a resource. The behaviour of this operation will depend upon the type of resource being examined. For resources that are simple files, the showres operation will display the character contents of the resource. For more complex resources, the showres operation will display the meaningful contents of the resource. For example, if the showres operation were applied to a SCRIPT, the contents of the SCRIPT would be literally displayed. However, if the operation were applied to an LPP_SOURCE resource, the names of the filesets contained in the LPP_SOURCE would be displayed. To show the contents of an LPP_SOURCE in relation to what is currently installed on a NIM machine or SPOT, the "reference" attribute can be used to specify a machine or SPOT name. This attribute is used to specify the name of a machine or SPOT that should be used for comparison when showing information about a resource. For example, to show the contents of an LPP_SOURCE, in relation to what is already installed on a machine, use the "reference" attribute to specify the machine name. This attribute is used to specify the resource that should be viewed using the "showres" operation. Specifies flags for the "showres" operation to perform an "sm_inst" command on an LPP_SOURCE. Specifies flags for the "showres" operation to perform an "instfix" command on an LPP_SOURCE. This attribute is set on the NIM database definition for the master to indicate whether or not NIM resources should be exported with client mount access. When set to "no" the "access" option will not be added to the entry in the exports file for the resource meaning that the line length for the resource in the exports file is shorter (providing the ability to export to more machines). This also means that mount access is not restricted to just those clients to which the resource is allocated, rather, the resource is exported to all hosts. When set to "yes" or when not set at all, client mount access is added to the exports file when NIM allocates a resource. When this value is used as a network name in the if attribute when defining a machine, NIM will search for a matching network for the hostname specified. This attribute is a NIM resource. When a resource of this type is defined, it represents the location of a file that contains valid /etc/resolv.conf entries which define Domain Name Protocol name-server information for local resolver routines. If a resolv_conf resource is allocated to a standalone machine prior to a bos_inst operation or to a diskless or dataless machine prior to initialization and boot, upon successful installation and reboot, the machine will be configured to use the domain name services defined by the resource. This optional attribute may be specified when defining machines in the NIM environment so that the NIM network with which that machine must be associated can be defined at the time the machine is defined. The format of the value of the net_def attribute is as follows: where: = network type (one of tok, ent, fddi, etc.) = dotted decimal mask for the network = optional default gateway ip address or hostname used by the machine being defined to communicate with the master = optional default gateway ip address or hostname used by the master to communicate with clients on other subnets = optional name to be given to the NIM definition created for the network. (A unique default value is assigned otherwise.) When specifying the net_definition attribute to create or change a machine definition, the "find_net" keyword must be specified as the first component of the "if" attribute for the machine. The net_definition attribute may also be specified when defining additional NIM interfaces ("if" attributes) for machine definitions. This operation executes the lppchk command on SPOT or machine targets to perform file and fileset consistency checks. The default behavior is to perform a fileset version consistency check for all installed filesets. Checks may be performed for an individual fileset by specifying the "filesets" attribute followed by a fileset name. See the "lppchk_flags" attribute for details of other consistency check modes available. Specifies the mode of consistency checking for the lppchk operation. The following flags are currently supported: -f Fast check (file existence, file length) -c Checksum verification -v Fileset version consistency check (default) -l File link verification -u Update inventory (only valid with -c or -l) -mn n=1-3 controls detail of messages, 3 is most verbose This attribute refers to the kernel that will be used to boot the system when a network boot takes place. This attribute must be specified when defining a machine resource. The following values are valid for this attribute: up - Specifies to use the kernel for single processor machines. mp - Specifies to use the kernel for multiprocessor machines. This attribute refers to a file on the NIM master that should be used as a temporary bundle resource for a NIM SMIT operation. The bundle definition will be added automatically in the NIM environment when the operation begins, and it will be removed after the operation completes. This attribute is intended to be used by SMIT, and should not normally be specified by the user.This attribute is used to specify optional flags to the mksysb command when creating a mksysb image during the definition of a mksysb resource. Valid flags are: -e Exclude from the system image backup the files and directories listed in the /etc/exclude.rootvg file on the machine being backed up. -m Generate a layout mapping of the logical to physical partitions for each logical volume in the rootvg volume group. -b [ block_size ] Specifies the number of 512 bytes to write in a single output operation. -X Expand the /tmp filesystem on the machine being backed up if needed. This attribute represents the PowerPC Symmetric Multiprocessor Computer machine platform type. This attribute is used to classify NIM configuration types which are supported for the rspcsmp platform type. When changing the name of a NIM machine, resource, or network, this attribute holds the new name of the object. This attribute is a NIM network type. When a network object of this type is defined, it represents a "generic" network which has limited functionality in the NIM environment. Network boot dependent operations, such as bos installation, are not permitted over machines defined on "generic" NIM networks. This attribute is managed by NIM and is used to indicated the result of the last NIM operation performed on a resource. This is a hidden attribute that is used to hold the most up to date information about a machine on which a BOS installation is taking place. NIM does not currently use this attribute. It is provided for the NIM GUI. This attribute is used to specify that a network is an IEEE 802.3 ethernet network. This attribute is only valid for ethernet networks and networks that have an "other_net_type" attribute set to ethernet. If this attribute is not specified, then it will be assumed that the network is standard ethernet. This attribute is used to specify if a client is allowed to allocate resources. If the attribute is set to "no" on the master then no client is allowed to allocate resources. If this attribute is set to "no" on the client then that client is not allowed to allocate resources. If this attribute is set to "no" on a resource then no client is allowed to allocate that resource. This attribute is used to specify if a machine is allowed to register itself as a NIM client. If the attribute is set to "no" on the master then machines are not allowed to register themselves as clients. This attribute is used to specify if the NIM master should perform cpu id validation for nimclient commands. If this attribute is set to "yes" or is not defined, then the cpu id embedded in the nimclient command must match the cpu id in the NIM database for the client issuing the command. If the cpu ids do not match, then the nimclient command will fail. If this attribute is set to "no", then the client definition in the NIM database will be assigned the new cpu id from the nimclient command and the command will run. This attribute is used to specify if NIM servers export their resources with read permission to all hosts. If this attribute is set to "no" or is not defined, then NIM servers export their resources to specific hosts. If this attribute is set to "yes", then NIM servers will export their resources to all hosts. This attribute is used to specify that a platform is defined in a SPOT for building network boot support. This attribute is used to specify that a machine has been defined with a network interface/platform combination. This attribute is used to specify that all possible boot images should be built rather than just those associated with defined machines. This attribute specifies whether the set of platform/kernel/network combinations defined for machines in the environment should be regenerated. This attribute is used to specify the target disks for an alt_disk_install operation on a client. This NIM operation performs an alt_disk_install on a running NIM client. This attribute is used to specify the level of a mksysb resource. Some NIM operations may require the level of the mksysb to match the level of other NIM resources that are used for the operation. This attribute is used to specify that detailed information should be displayed in the output from an operation. ATM networks have limited support for NIM operations. There is currently no capability to perform a network boot over an ATM adapter. In order to support network installations of the base operating system, a boot image is copied to the hard disk of a running machine to configure the adapter and perform the installation. Diskless and dataless clients are not supported on ATM networks. This attribute is used to specify that a boot image should be NFS exported to a client. This attribute is used to specify the name of client niminfo file. This attribute is used to specify the name of a boot image. This attribute is used to specify a new type for a NIM object. This attribute is valid only in special instances. This attribute is used to specify the phase of an operation that should be performed. This attribute is used to specify the number of clients in a group to be operated on concurrently. This attribute is used to specify the amount of time to operate on clients in the group. This attribute is used to specify the number of times a client should retry a failing state change or result request to the master. This attribute is used to specify that the hostname of a client should be set to match the second argument of it's 'if' attribute, at the completion of a BOS install. This can be utilized to allow client machines to have short hostnames at the completion of an install. + 8(+,,/0x2 446 6\778\+89D:x;4;=0?AB(ELPSV8Y\`Xc orv$yx}p++++,, ,8|HTt,P,\,h,t,, ,$d8 `H\,,,,--(T\üX-@-X-p-XȜ˴--d--...00TXtxԬ.H.`.x.....// /8׌/P/h/ @//Lxpޠ`/d4//0t0(0@40X0p00T00`@TT xXT$<  T$lh T!!"#\#$%<&'4'(*+$+t+,,X/\/00L002 2567T78:;T=pBD8EGHJK\KL@MtM000NPQRPT`UVV|WWXXLYY[[l[[\d\] ]|^ ,8DLT`hp| $,4<HLP\dt$,4@HPX`hpx (4DLT\hlpx  $,8DP\ht (08HXht T @p ,XDt$T@$XXhx,d4\@< t@t ( D@|@ L ` h !!$!D(Pt T!`!l!!!!4l!!!!""("D"\"hT"t""""" "\"""#(#\# #4#@,#H#P#hT#t##$#T####@p#,#h#$ $$($0$8$X$d8$tt$$$,$t$$$<$x$%% %  P%0%8%T %d %t % % H%%%%% % & & & &(&8 @&@ x&L &T&`&x&& & ,& P& & & & (& X& & & ' '0' X','<'D'`'l'x,'\''''@'''( ((<(H(h(p((d((((((()(),)@)LD)\x)h)x))@)p))T)) )@)l***,*D*X*\*h*t*|*,*T*********+++(P+8+P+d+t+ ,@Thp|T  8\,<L`Txp|,<Thx$4<H`hpxDl$,4<DXhpH(tDH`\$p(\X@dDĄ|ǜlɴ h,4t˨$H̼̔ T̈́ʹhp|@Έ0lϜ<,`ФXфD<lҸLӔ LԌXtհl@h֌ּ`؄ب$D`l4ٜDڀ@x۴<܌(dݤ 8,ިTߐ XTDT\4|80\x\H 22303h3 344(4h455\5 56,6`6677P77788D8909x99:,:h::;,;t;;$>t>??H??@@X@@A4AAB(BdBC0C|DD\DDE0EpEFtFG4GpGH`HHItIJ JPJJK KDKhKKKL,L\LLL(HMM@MdMMMNN0N`NNOOPOOOPPHPQhQ<Q`QQQRRHRRS@SSTTU0UUVV\VW4WXX4X\XXY@YZ ZZ[([\\D\p\\]]^_\__`@`a,a\abbbc(cdePfftfghDi8ijjDjpjkLkklltlm8nop pq q`qr,rsst$ttuu\uvv@vw wpwxxxytyz{4|`|}}~(~l~t@TPlxx 4xT|dH$4(,x<8PT< lpHlpXP<masterbootnim_scriptfind_netdefault.*[][ `$^&*():,;?\<>|"']+.*^if[0123456789]*^([^ ]+) ([^ ]+)$^([^ ]+) ([^ ]+) ([^ ]+)$^.*^([^ ]+) .*^([^ =]+)=(.*)^/dev/([^0123456789].*)^(.*)/([^/]+)^rc=([0-9]+) nim_malloc: size = %d a # # # %s # %d/usr/bin/rm-r nim_exit all/var/adm/nim/glock/var/adm/nim/explock/var/adm/nim/errlock nim_signinit SM_CONNECTION_PORTSMITaSMITm/etc/niminfo/etc/niminfor/SPOT/niminforexport NIM_NAMEexport NIM_CONFIGURATIONexport NIM_MASTER_HOSTNAMEmallocexport NIM_MASTER_UIDexport NIM_MASTER_PORTexport NIM_REGISTRATION_PORTexport NIM_COMM_RETRIESexport NIM_COMM_DELAYexport NIM_BOOTP_ENABLEDexport NIM_USR_SPOTnimtcpnimregtcp/%d/var/adm/nim/xop%s%s/var/adm/nim/xop/var/adm/nim%s%s/var/adm/nim nim_init: name = %s; mallocrecompcmdnim.catr/var/adm/nim/glock/var/adm/nim/space_lock/var/adm/nim/space_lock/var/adm/nim/space_lock%d%s%d rm_attr_ass: attr=%d attr_value: attr=%d forceverboseignore_lockshow_progressyesnoshow_progressyes %s -a %s=%s %s -a %s=%s first_field: str=%s two_field: value=%s three_field: value=%s SMIT_NO_EXEC0042%s %s a:pqa:pq.*[][ `$^&*()=+:,.;?/\<>|"']+.*^([^ ]+) ([^ ]+) ([^ ]+)( [^ ]+)*$^[abcdefABCDEF0123456789]{12}$|^0{1,12}$^([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+)$^[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}$^([^0123456789 ]+)([0123456789]*)^([^0123456789 ]+)([0123456789]+)^([0123456789]+-[0123456789]+)(.*)^([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+) ([^ ]+) (.*)^[0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}$ nim_realloc: total size = %d push_xop: xops file = %s; /usr/lpp/bos.sysmgt/nim/methods/c_popxop pop_xop: key = %s; ignore = %d; get_nim_env: reading from %s nim_init_var: cmd_name = %s; pid = %d; pgrp = %d query_glock: lf_name=%s get_glock: retry=%d; delay=%d; rm_glock: force=%d; lock_file=%s; fd=%d get_list_space: listptr=0x%x free_list: listptr=0x%x reset_list: listptr=0x%x add_to_LIST: listptr=0x%x; str=%s; add_attr_ass: pdattr=%d; name=%s; value=%s; seqno=%d; add_attr: tag=%d; tag_t=%s; value=%s; find_attr_ass: attr=%d parse_attr_ass: attr_ass=%s; change_op=%d; @(#)95 1.59 src/bos/usr/lib/nim/lib/nim_gen.c, cmdnim, bos43N, 9914A_43N 4/1/99 14:41:548X,lXPhTThhhhlhh%dhXh hph,h?xhB,hIh80 v(v([rZVVZaccess@ close@ getpgrp@ getpid@ getprocs@ lseek@ mkdir@ open@ pipe@ select@ @ umask@ uname@ unlink@ @ @_iob@_Errno@ exit@ atexit@ free@ malloc@ strlen@ fopen@ realloc@ fprintf@ getenv@ atoi@ catopen@ catgets@ strchr@ printf@ catclose@ write@ fclose@ memset@ usleep@ vfprintf@ sprintf@ read@ strncmp@ strrchr@ fgets@ signal@ strdup@ stat@ rewind@ bzero@ 4@ time@ waitpid@ @@ fork@ dup2@ mktemp@ popen@ fdopen@ wait@ getopt@ execvp@ setbuf@ killpg@ strerror@ strftime@ remove@ regcomp@ regerror@ regexec@ L@ rcmd@ strtol@ optind@optarg@optopt@force\ h y errstr nene  MSG_msg    , 8 D P nim_init\ niminfoerrsig(001111 1___ _$_(_,_0_4_8_<_@_D_H_L_P_T_X_\_`_d_h_l_p_t_x_|________________________________```` ````` `$`(`,`0`4`8`<`@`D`H`L`P`T`X`\```d`h`l`p`t`x`|````````````````````````````````aaaa aaaaa a$a(a,a0a4a8a<a@aDaHaLaPaTaXa\a`adahalapataxa|aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaabbbb bbbbb b$b(b,b0b4b8b<b@bDbHbLbPbTbXb\b`bdbhblbpbtbxb|bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbcccc ccccc c$c(c,c0c4c8c<c@cDcHcLcPcTcXc\c`cdchclcpctcxc|cccccccccccccccccccccccccccccccdddd ddddd d$d(d,d0d4d8d<d@dDdHdLdPdTdXd\d`dddhdldpdtdxd|ddddddddddddddddddddddddddddddddeeee eeeee e$e(e,e0e4e8e<e@eDeHeLePeTeXe\e`edehelepetexe|eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeffff fffff f$f(f,f0f4f8f<f@fDfHfLfPfTfXf\f`fdfhflfpftfxf|ffffffffffffffffffffffffffffffffgggg ggggg g$g(g,g0g4g8g<g@gDgHgLgPgTgXg\g`gdghglgpgtgxg|gggggggggggggggggggggggggggggggghhhh hhhhh h$h(h,h0h4h8h<h@hDhHhLhPhThXh\h`hdhhhlhphthxh|hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhiiii iiiii i$i(i,i0i4i8i<i@iDiHiLiPiTiXi\i`idihilipitixi|iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiijjjj jjjjj j$j(j,j0j4j8j<j@jDjHjLjPjTjXj\j`jdjhjljpjtjxj|jjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjkkkk kkkkk k$k(k,k0k4k8k<k@kDkHkLkPkTkXk\k`kdkhklkpktkxk|kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkllll lllll l$l(l,l0l4l8l<l@lDlHlLlPlTlXl\l`ldlhlllpltlxl|llllllllllllllllllllllllllllllllmmmm mmmmm m$m(m,m0m4m8m<m@mDmHmLmPmTmXm\m`mdmhmlmpmtmxm|mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmnnnn nnnnn n$n(n,n0n4n8n<n@nDnHnLnPnTnXn\n`ndnhnlnpntnxn|nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnoooo ooooo o$o(o,o0o4o8o<o@oDoHoLoPoToXo\o`odoholopotoxo|oooooooooooooooooooooooooooooooopppp ppppp p$p(p,p0p4p8p<p@pDpHpLpPpTpXp\p`pdphplppptpxp|ppppppppppppppppppppppppppppppppqqqq qqqqq q$q(q,q0q4q8q<q@qDqHqLqPqTqXq\q`qdqhqlqpqtqxq|qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqrrrr rrrrr r$r(r,r0r4r8r<r@rDrHrLrPrTrXr\r`rdrhrlrprtrxr|rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrssss sssss s$s(s,s0s4s8s<s@sDsHsLsPsTsXs\s`sdshslspstsxs|sssssssssssssssssssssssssssssssstttt ttttt t$t(t,t0t4t8t<t@tDtHtLtPtTtXt\t`tdthtltptttxt|ttttttttttttttttttttttttttttttttuuuu uuuuu u$u(u,u0u4u8u<u@uDuHuLuPuTuXu\u`uduhuluputuxu|uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuvvvv vvvvv v$v(v,v0v4v8v<v@vDvHvLvPvTvXv\v`vdvhvlvpvtvxv|vvv (08@HPX`hpx  $,08<DHPT\`hlptx&|\H)@: % ]./=LKJ"FIM +  '$*(,0$48-<6@?DHL,PTXA\D`Edhlpt x!|GOC<#(43B>87 029; 51/build/export/power/usr/lib:/build/export/power/usr/ccs/lib:/usr/lib:/liblibc.ashr.o sigcleanup setsockopt_system_configuration localtime setlocalegetservbyname To_Mastererrsig_handler client_exec nim_error nim_mallocnim_error_plusexport_errstr smit_no_exec add_to_LISTget_list_space46 0 136 0 0 0 0 0 ` 1 136 shr.olll l$l(l,l0l4l8l<l@lDlHlLlPlTlXl\l`ldlhlllpltlxl|lllllllll,@8888`8HU`bHZ݀A8`8!H(88aHcHA8aHH&A8b8HHZA,@d888`8HY`bHZmA8`8!H|.88`8H`bHZ9A8`H,;@@P;=cH&EA8bcHZ%A,;Z|AW[:@cKĀDbLc8HaDHYA8`8!}N A l To_Master0a|}&,! 8```@DA88g@889H uAHHY A