[05] 12/22/18 T(9192) _VMR 16:25:28.551833 DEBUG VMR_retry.C[1151]: Doing  operation with opCode: 33(VMDR_QUICK_QUERY) [05] 12/22/18 T(9192) _VMR 16:25:28.551854 DEBUG VMR_retry.C[178]: INFO: Trying  with HMC: rthmc3. [05] 12/22/18 T(9192) _VMR 16:25:28.551863 DEBUG VMR_HMC.C[6905]: getQuickQuery:  Calling kriSubmitQuickQuery!. HMC:9.3.18.159, viosUuid:  315CE56B-9BA0-46A1-B4BC-DA6108574E7E [05] 12/22/18 T(9192) _VMR 16:25:28.678215 DEBUG VMR_HMC.C[6925]: getQuickQuery:  Job submitted. Now doing WaitTillJobCompletion() .. [05] 12/22/18 T(9192) _VMR 16:25:28.678218 DEBUG VMR_HMC.C[3426]: Calling  krigetJobResult(). HMC: 9.3.18.159, jobid: 1543584834864, retCnt = 1 [05] 12/22/18 T(9192) _VMR 16:25:29.771523 DEBUG VMR_HMC.C[3426]: Calling  krigetJobResult(). HMC: 9.3.18.159, jobid: 1543584834864, retCnt = 2 [05] 12/22/18 T(9192) _VMR 16:25:29.863552 DEBUG VMR_HMC.C[6938]: getQuickQuery  [315CE56B-9BA0-46A1-B4BC-DA6108574E7E] JobStatus: COMPLETED_OK, ReturnCode: 0 [05] 12/22/18 T(9192) _VMR 16:25:29.863562 DEBUG VMR_retry.C[345]: In doRetry  function, for opCode = 33(VMDR_QUICK_QUERY), rc = 0, retCode is 0, errstr is:  ,retry flag is 22 [05] 12/22/18 T(9192) _VMR 16:25:29.863572 DEBUG VMR_HG.C[11671]: FDE doQuickQuery  success to 315CE56B-9BA0-46A1-B4BC-DA6108574E7E [05] 12/22/18 T(9192) _VMR 16:25:29.863587 DEBUG VMR_VIOS.C[6134]: setCAAtopology  [05] 12/22/18 T(9192) _VMR 16:25:29.863592 DEBUG needAttn.C[1566]: START  handleVIOResponse scan [ 38 ]. ... Note the entry marking the 20-second sleep interval between the previous request  ( sleepCounter 37 ) and current request ( Current scan [ 38 ] ). By comparison, there is no  sleep interval before the first QQ request ( Current scan [ 1 ] ), as shown in Example 2-38 on  page 76. The same VIOS,  rt13v2 , is used for polling in both cases. A  doQuickQuery  call is  performed for this VIOS, and inside this call is the HMC REST API job request pattern that is  handled at the  krest  library level by the  kriSubmitQuickQuery  and  krigetJobResult()  calls.  This pattern is covered in “QuickQuery asynchronous job example” on page 105. Here, we  focus on the actions at the FDE and VIOS levels and on the content of the request and  response payloads they exchange with each other. A typical QQ request that originated at the FDE level on the KSYS side and delivered to the  vioservice  command at the VIOS level together with its immediate corresponding XML  response that was obtained at the VIOS level from the HSDB are shown in Example 2-210. Example 2-210 QuickQuery request and response in the vioservice log on the VIOS side # alog -f /home/ios/logs/viosvc.log -o > viosvc.log.QQ.txt # more viosvc.log.QQ.txt ... [START 12058936 62259481 12/22/18-15:20:23.789 vioservice.c 1.18 320]  /usr/ios/sbin/vioservice lib/libviopass/passthru  [0 12058936 62259481 12/22/18- 15:20:23.789  viosvc_res.c 1.26 456] stdin pipe  input:[ <?xml version="1.0"?> <VIO xmlns="http://ausgsa.austin.ibm.com/projects/v/vios/schema/vioHADR2.00"  version="2.00" author="LIBKREST" title="Req Quick Query"> <Request action_str="VIO_HS_QUICK_QUERY"/> </VIO> ] [0 12058936 62259481 12/22/18- 15:20:23.862  viosvc_res.c 1.26 464]  vio_response.result=[ <VIO><Response> <quickQuery> Chapter 2. IBM VM Recovery Manager High Availability components  235