[3 15597926 66519541 01/19/19-09:27:59.577 hs_remove_vm.c vioHsRemoveVm 1.18 140]  skipping 24808803-eb32-4d0a-8aa5-a5b60216f15a: unknown machine # # grep vioHs viohs.log.libhealth.txt|tail -4 [3 20382194 66978263 01/20/19-01:56:41.563 hs_atten.c vioHsQuickQuery 1.107 4669]  End, rc=0 [3 20382198 60817889 01/20/19-01:57:03.553 hs_atten.c vioHsQuickQuery 1.107 4669]  End, rc=0 [3 20382202 66191779 01/20/19-01:57:25.594 hs_atten.c vioHsNeedsAttention 1.107  4587] End, rc=0 [3 17170756 66847175 01/20/19-01:57:49.944 hs_atten.c vioHsQuickQuery 1.107 4669]  End, rc=0 # grep -c vioHs viohs.log.libhealth.txt 4045 # grep -c vioHsQuickQuery viohs.log.libhealth.txt 1747 # grep -c vioHsNeedsAttention viohs.log.libhealth.txt 873 # grep -c vioHsQueryVM viohs.log.libhealth,txt 276 # grep -c vioHsRemoveVm viohs.log.libhealth.txt 1104 # grep vioHs viohs.log.libhealth.txt|egrep -v  "vioHsQuickQuery|vioHsNeedsAttention|vioHsQueryVM|vioHsRemoveVm"|head -4 [3 16056632 65143055 01/19/19-10:32:36.797 hs_ms.c vioHsAddMs 1.83 2254] Begin. [3 16056632 65143055 01/19/19-10:32:36.820 hs_ms.c vioHsAddMs 1.83 2274] Managed  system is already existing. [3 16056632 65143055 01/19/19-10:32:36.820 hs_ms.c vioHsAddMs 1.83 2451] END. [3 17105370 65864085 01/19/19-11:40:46.475 hs_ms.c vioHsAddMs 1.83 2254] Begin. # grep -c vioHsAddMs viohs.log.libhealth.txt 45 # # alog -f /home/ios/logs/viosvc.log -o > viosvc.log.libhealth.txt # more viosvc.log.libhealth.txt ... [START 17170756 66847175 01/20/19-01:57:49.883 vioservice.c 1.18 320]  /usr/ios/sbin/vioservice lib/libviopass/passthru  [0 17170756 66847175 01/20/19-01:57:49.883 viosvc_res.c 1.26 456] stdin pipe  input:[<?xml version="1.0"?> Example 2-79 VIO_HS_QUICK_QUERY request trace in viosvc.log and viohs.log So, any string containing the  vioHs  substring in our log excerpt in Example 2-78 on page 117  is an occurrence of an API call from the  libviohealth.a  library: Another legitimate question about our  viohs.log  file excerpt is which are the processes  writing there. From our presentation so far, the best candidate appears to be the  vioservice command. We choose the last entry of the tail output in Example 2-78 on page 117, which is  a  vioHsQuickQuery  trace that is left by the thread 66847175 of process 17170756. Checking  for this PID-TID combination in  viosvc.log  of the  vioservice  command, we obtain the  request and response details of a related  VIO_HS_QUICK_QUERY  request, as shown in  Example 2-79. 118  Implementing IBM VM Recovery Manager for IBM Power Systems 4045=1747+873+276+1104+45.