# sed '789,$!d;=' postrestart_ksys.log|sed 'N;s/
/:/'|sed -n '/T(8889)/h;$!b;g;p' 1124:[15] 11/19/18 T(8889) _VMR 13:49:43.5399 DEBUG VMR_CEC.C[9776]: usage_count 2 # sed '789,$!d;=' postrestart_ksys.log|sed 'N;s/
/:/'|sed -n '/T(90a)/h;$!b;g;p' 1084:[15] 11/19/18 T(90a) _VMR 13:49:43.3469 DEBUG VMR_CEC.C[9776]: usage_count 1 # sed '789,$!d;=' postrestart_ksys.log|sed 'N;s/
/:/'|sed -n '/T(3d3e)/h;$!b;g;p' 1097:[15] 11/19/18 T(3d3e) _VMR 13:49:43.3750 DEBUG VMR_CEC.C[9776]: usage_count 0 #  We also must identify the lines that are logged in 789 - 1169 by other threads than those  handling the  resyncAPP  tasks (Example 2-53). Example 2-53 Records in resyncAPP flows not logged by resyncAPP task threads # sed '789,1169!d;=' post-restart_ksys.log|sed 'N;s/
/:/'|egrep -v  "T\(4041\)|T\(8586\)|T\(8687\)|T\(8788\)|T\(8889\)|T\(90a\)|T\(3d3e\)" 803:[15] 11/19/18 T(405) _VMR 13:49:36.238105 DEBUG VMR_LPAR.C[9124]: In  chgResourceCommited for HASTATE of VM rt13007 to 0x20000004. 818:[15] 11/19/18 T(405) _VMR 13:49:36.244447 DEBUG VMR_LPAR.C[9124]: In  chgResourceCommited for HASTATE of VM rt14007 to 0x20000004. 835:[15] 11/19/18 T(405) _VMR 13:49:36.284252 DEBUG VMR_LPAR.C[9124]: In  chgResourceCommited for HASTATE of VM rt14001 to 0x20000004. 852:[15] 11/19/18 T(405) _VMR 13:49:36.313110 DEBUG VMR_LPAR.C[9124]: In  chgResourceCommited for HASTATE of VM rt14002 to 0x20000004. 869:[15] 11/19/18 T(405) _VMR 13:49:36.377773 DEBUG VMR_LPAR.C[9124]: In  chgResourceCommited for HASTATE of VM rt14005 to 0x20000004. 886:[15] 11/19/18 T(405) _VMR 13:49:36.428750 DEBUG VMR_LPAR.C[9124]: In  chgResourceCommited for HASTATE of VM rt13001 to 0x20000004. 902:[15] 11/19/18 T(405) _VMR 13:49:36.455869 DEBUG VMR_LPAR.C[9124]: In  chgResourceCommited for HASTATE of VM rt13002 to 0x20000004. 978:[15] 11/19/18 T(405) _VMR 13:49:42.061246 DEBUG VMR_LPAR.C[9124]: In  chgResourceCommited for HASTATE of VM rt13007 to 0x4. 1082:[15] 11/19/18 T(405) _VMR 13:49:43.346419 DEBUG VMR_LPAR.C[9124]: In  chgResourceCommited for HASTATE of VM rt13001 to 0x4. 1095:[15] 11/19/18 T(809) _VMR 13:49:43.374562 DEBUG VMR_LPAR.C[9124]: In  chgResourceCommited for HASTATE of VM rt13002 to 0x4. 1108:[15] 11/19/18 T(809) _VMR 13:49:43.437520 DEBUG VMR_LPAR.C[9124]: In  chgResourceCommited for HASTATE of VM rt14007 to 0x4. 1122:[15] 11/19/18 T(809) _VMR 13:49:43.539527 DEBUG VMR_LPAR.C[9124]: In  chgResourceCommited for HASTATE of VM rt14005 to 0x4. 1153:[15] 11/19/18 T(405) _VMR 13:49:48.561214 DEBUG VMR_LPAR.C[9124]: In  chgResourceCommited for HASTATE of VM rt14001 to 0x4. 1167:[15] 11/19/18 T(809) _VMR 13:49:48.702620 DEBUG VMR_LPAR.C[9124]: In  chgResourceCommited for HASTATE of VM rt14002 to 0x4. #  So, only  T(405)  and  T(809)  inserted some records in this range (among the bulk  resyncAPP related records). All of the records are about updating the  HASTATE  persistent attribute, as  shown in Example 2-45 on page 83. After  resyncAPP  tasks are complete, the  ksys  daemon goes to a steady state in which periodic  actions are run as follows: GLYPH<SM590000> Two  QuickQuery  + 1x  NeedAttention  actions every 20s, which are performed by FDE.  GLYPH<SM590000> A  QuickDiscovery  every hour and a  DeepDiscovery  once a day. Chapter 2. IBM VM Recovery Manager High Availability components  89 Steady state periodic actions