[15335792] runSystemCommand()[794] : RUNNING  COMMAND:/usr/sbin/rsct/bin/mkrpdomain rbRMHA $(/usr/bin/hostname) > /dev/null  2>&1; [15335792] runSystemCommand()[800]: Unaltered return status: 0 [15335792] runSystemCommand()[827]: RC: 0 [15335792] Ksyscluster has been created, please run: "ksysmgr verify ksyscluster  <ksysclustername>" [15335792] time:10/27/2018 13:26:20 ------------- [15335792] runSystemCommand()[794] : RUNNING COMMAND:lssrc -s IBM.VMR | grep  IBM.VMR | awk '{print $3}' >/tmp/ksysmgr.tmp.YQW7ea; [ -s /tmp/ksysmgr.tmp.YQW7ea  ] [15335792] runSystemCommand()[800]: Unaltered return status: 0 [15335792] runSystemCommand()[827]: RC: 0 add_ksyscluster()[478]: EXITING SUCCESSFULLY The  IBM.VMR  resource manager is responsible for its own set of resources and classes, and  has specific attributes and actions. Example 2-14 starts by listing all resource classes that are  defined at the RMC level after the KSYS cluster creation. The second column lists the  associated resource manager of each class in the first column. Filtering by the  IBM.VMR  string  in the second column, we get 11 classes as the final output. They are the RMC classes that  are managed by the  IBM.VMR  resource manager. The RMC resource manager  IBM.VMR  implements its log files by using the common RSCT  trace facility. Example 2-15 shows the default trace setup for the  IBM.VMR  resource manager. Example 2-15 Default tracing setup for the IBM.VMR resource manager Example 2-14 Resource classes of the IBM.VMR resource manager # echo "class_name:mgr_name"; lsrsrc -c|grep -v class_name|while read cl; do echo  "$cl:\c"; lsrsrcdef -c $cl|grep mgr_name|awk '{ print $3}';done|grep IBM.VMR class_name:mgr_name "IBM.VMR_HMC":"IBM.VMR" "IBM.VMR_CEC":"IBM.VMR" "IBM.VMR_LPAR":"IBM.VMR" "IBM.VMR_VIOS":"IBM.VMR" "IBM.VMR_SSP":"IBM.VMR" "IBM.VMR_SITE":"IBM.VMR" "IBM.VMR_SA":"IBM.VMR" "IBM.VMR_DP":"IBM.VMR" "IBM.VMR_DG":"IBM.VMR" "IBM.VMR_HG":"IBM.VMR" "IBM.VMR_APP":"IBM.VMR" # # lssrc -ls IBM.VMR|grep -p trace Information about trace levels: ... _VMR Errors=255 Info=1 LPAR=4 Verify=4 KREST=5 KRI=4  FDE=4 FDELong=4 CONFLICT=4 MSG=4 Debug=0 /var/ct/3EmzyyOpynuvLXYdEkdZSO/log/mc/IBM.VMR/trace.1.sp -> spooling not enabled /var/ct/rbRMHA/log/mc/IBM.VMR/trace.conflict.1.sp -> spooling not enabled /var/ct/rbRMHA/log/mc/IBM.VMR/trace.fde.1.sp -> spooling not enabled /var/ct/rbRMHA/log/mc/IBM.VMR/trace.fdelong.1.sp -> spooling not enabled /var/ct/rbRMHA/log/mc/IBM.VMR/trace.krest.1.sp -> spooling not enabled 58  Implementing IBM VM Recovery Manager for IBM Power Systems IBM.VMR resource manager