IBM i Global

IBM i 

A space for professionals working with IBM’s integrated OS for Power systems to exchange ideas, ask questions, and share expertise on topics like RPG and COBOL development, application modernization, open source integration, system administration, and business continuity.


#Power


#IBMi
#Power
#Operatingsystems
#Servers
 View Only

  • 1.  Trace connection

    Posted 03/07/24 03:01 PM

    Hi, 

    I've been trying to trace a QZRCSRVS job that shows wrapping with the following command: 

    QSYS/TRCCNN SET(*ON) TRCTYPE(*IP) SIZE(160 *MB) WCHMSG((*ALL)) WCHMSGQ((*J
    OBLOG)) WCHJOB((192987/QUSER/QZRCSRVS))                                   
    Watch session QSCCNN0050 successfully started.                            
    Trace records will be stored in trace table QTRCCNN193339  

    but when I issue a TRCCNN SET(*OFF) and can't find the trace table and that QSCCNN0050 watch session does not show up under WRKWCH. 

    Where does this log go and how do I view it? 

    Thanks. 



    ------------------------------
    Michael Cramer
    ------------------------------


  • 2.  RE: Trace connection

    Posted 03/08/24 11:16 AM

    Hello Michael,

    The watch that you have set up stops the trace as soon as any message is logged in the job log.  The trace will stop automatically and print the trace when that happens.  The output is a pair of spool files, QPCSMPRT (unformatted raw LIC trace) and QSYSPRT formatted trace.  The trace table name (QSCCNN0050 in your case) is a LIC table that is used to buffer the data when the trace is running.  When the trace ends, the table is deleted.  If you start a trace like this and want to know if it is still running, run the command WRKTRC *ALL and you can see the status of the trace (ACT-ENB when it is running).  It will not be listed once the watch ends the trace.



    ------------------------------
    Michael Swenson
    Software Engineer
    IBM
    ------------------------------



  • 3.  RE: Trace connection

    Posted 03/08/24 04:18 PM

    Hi Michael, 

    Thanks for your answer. I did find both of the spool files but nothing relevant in there. What's the best way to see what these QZRCSRVS jobs are doing on the system? 



    ------------------------------
    Michael Cramer
    ------------------------------

    Original Message


  • 4.  RE: Trace connection

    Posted 03/08/24 04:37 PM

    I'm a huge fan of using TRCCNN or a client side-trace (varies by client) to get answers like that.  But I have the advantage that I'm an IBMer that makes a living supporting that server...so I have access to the information to break out that proprietary data stream and make sense of it.  Outside of opening a support case about all that you can do is look at the job log or create a user exit program for the QIBM_QZRC_RMT exit point that logs the command, programs and parameters that are being sent by the client program.

    Here is where you can find the details of what data are provided to an exit program on this exit point:  https://www.ibm.com/docs/en/i/7.5?topic=parameters-remote-command-distributed-program-call-server



    ------------------------------
    Michael Swenson
    Software Engineer
    IBM
    ------------------------------

    Original Message


  • 5.  RE: Trace connection

    Posted 03/08/24 04:39 PM

    I should also point out that the watch you set up would stop the trace before it captured much of anything that would have been going on in that job.  We usually only use the watch option to stop a trace when some error message we are waiting for happens.  



    ------------------------------
    Michael Swenson
    Software Engineer
    IBM
    ------------------------------

    Original Message


  • 6.  RE: Trace connection

    Posted 03/13/24 07:54 PM

    Hi Michael, 

    would another tool help in finding out what's happening behind those jobs? I don't really want to open up a ticket every time this happens. 



    ------------------------------
    Michael Cramer
    ------------------------------

    Original Message


  • 7.  RE: Trace connection

    Posted 03/14/24 02:33 PM

    Tracing and writing a logging exit program are really your only options.  When this job is used for remote commands, they are all logged in the job log.  But the QZRCSRVS job does double-duty, it also services remote program calls and those calls don't leave much in the job log.

    Client-side traces tend to be more readable but you have to know what the client is, be on the client machine and be able to invoke the right sort of trace (java toolbox, cwbcotrc, etc.) before the client application starts.  



    ------------------------------
    Michael Swenson
    Software Engineer
    IBM
    ------------------------------

    Original Message


  • 8.  RE: Trace connection

    Posted 03/08/24 10:56 PM

    Dear Micahel

    Perhaps, you need a PTF as specified in this IBM i Technote:  Tracking Source of Host Server Connections (QZRCSRVS, QZDASOINIT...) at  https://www.ibm.com/support/pages/tracking-source-host-server-connections-qzrcsrvs-qzdasoinit

    Satid S.



    ------------------------------
    Satid S
    ------------------------------



  • 9.  RE: Trace connection

    Posted 03/13/24 07:52 PM

    Hi Satid, 

    we have that PTF already on. 



    ------------------------------
    Michael Cramer
    ------------------------------

    Original Message


Related Content