The command logs in viosvc.log  and viosvc.log.err  in the /home/ios/logs  directory. Example 2-67 shows a vioservice  log excerpt with an entry that is determined by a QuickQuery request ( VIO_HS_QUICK_QUERY ) that came from the KSYS side. 

# alog -f /home/ios/logs/viosvc.log -o | more ... [START 27066876 65733113 12/09/18-19:05:24.752 vioservice.c 1.18 320] /usr/ios/sbin/vioservice lib/libviopass/passthru [0 27066876 65733113 12/09/18-19:05:24.753 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 27066876 65733113 12/09/18-19:05:24.806 viosvc_res.c 1.26 464] vio_response.result=[<VIO><Response> <quickQuery> <viosStatList><viosStatus machine_type="8286" model="42A" serial="21E0B2V"> <viosStat uuid="315ce56b-9ba0-46a1-b4bc-da6108574e7e" state="UP" hmResponsive="1" hmResponseSec='1' hasData='0' reason='0x00000000' syncMsg="0" /> <viosStat uuid="5ac3e0dc-13fc-4221-9617-8ef61c4cdd83" state="UP" hmResponsive="1" hmResponseSec='1' hasData='0' reason='0x00000000' syncMsg="0" /> </viosStatus></viosStatList> </quickQuery> <quickQuery> <viosStatList><viosStatus machine_type="8286" model="42A" serial="2100DEW"> <viosStat uuid="166c89ef-57d8-4e75-815c-aa5b885560b1" state="UP" hmResponsive="1" hmResponseSec='1' hasData='0' reason='0x00000000' syncMsg="0" /> <viosStat uuid="4e0f6f60-214b-4d2c-a436-0eac46f7f71f" state="UP" hmResponsive="1" hmResponseSec='1' hasData='0' reason='0x00000001' syncMsg="0" /> </viosStatus></viosStatList> </quickQuery> </Response></VIO> ] [END 27066876 65733113 12/09/18-19:05:24.806 vioservice.c 1.18 323] exited with rc=0 [START 27066624 62783899 12/09/18-19:05:46.528 vioservice.c 1.18 320] /usr/ios/sbin/vioservice lib/libviopass/passthru viosvc.log (99%) 

We first see the inputXML  content as extracted by the HMC REST server from the HTTP request payload and passed through RMC as input to the vioservice  command. Then, the vioservice  command runs, generates its result on standard output, and exits with a return code. Standard output content and the return code value are passed back through RMC to the HMC REST server to be encoded and sent back to libkrest  and KSYS as parameter values for the stdOut  and CMDReturnCode  parameters in the response XML payload. 

## QuickQuery asynchronous job example 

Now, we look at our KSYS daemon and at the first 10 records that are logged in the krest trace files after the KSYS daemon restart (Example 2-68). 

# sed '1,10!d;=' post-restart_krest.log|sed 'N;s/
/:/' 1:[00] 11/19/18 T( 1) ____ 13:48:35.136313 ******************* Trace Started - Pid = 16646518 ********************** 

