IBM Support

IV87239: UNIX OS AGENT DOES NOT COMPUTE CORRECTLY THE QUEUE DEPTH AND SIZE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Permanent restriction.

Error description

  • Unix OS Agent - UX - does not compute correctly the queue depth
    and size metrics for UNXPRINTQ attribute group.
    Affected Platforms / Versions: All platforms and all releases
    Diagnostics:
    The UX agent issues the following command to gather print queue
    data:
    LANG=C /bin/enq -isAW 2>/dev/null
    .
    To debug issues with what appear to be invalid metrics for
    UNIXPRINTQ
    attributes when comparing to external "enq" or "lpstat"
    commands, gather
    following RAS1 tracing and refresh workspace to drive data
    collection:
    .
    In the "ux.ini" file set:
    KBB_RAS1=ERROR (UNIT: KRA ALL) (UNIT: KUX12 ALL) (UNIT: lpstat
    ALL)
    .
    Get export of the TEP workspace showing invalid data, as well as
    gathering
    "enq" command from same timeframe as UX agent tracing
    externally:
    LANG=C /bin/enq -isAW 2>/tmp/printqueue.out
    .
    Identify the printer / queue that appears to have invalid data
    by comparing the
    external "enq" command output vs. what is displayed in TEP
    workspace.
    .
    In the RAS1 logging for the UX agent, review the tracing for
    this printer / queue:
    For the sample displayed in the TEP that showed
    ***
    Print Queue Name: cd02
    Device Name: hp@cd02
    Number of Jobs: 30
    Print Queue Status: Ready
    Timestamp: 07/20/16 09:03:35
    Total Size of Jobs in Queue: 362
    ***
    lpstat_parser.cpp,204,"collect") Queue: cd02
    lpstat_parser.cpp,210,"collect") Dev: hp@cd02
    lpstat_parser.cpp,248,"collect") Line ends on queue: cd02
    , Status: READY
    lpstat_parser.cpp,294,"enQueue") Entry
    lpstat_parser.cpp,350,"enQueue") New queue cd02
    lpstat_parser.cpp,380,"enQueue") Realloc 174 >= 174
    lpstat_parser.cpp,424,"enQueue") fileNameBuf:
    lpstat_parser.cpp,425,"enQueue") pre prntqdepth: 0
    lpstat_parser.cpp,426,"enQueue") pre printqsize: 0
    lpstat_parser.cpp,434,"enQueue") post prntqdepth: 0
    lpstat_parser.cpp,435,"enQueue") post printqsize: 0
    The tracing above shows 0 depth on the queue both "pre" and
    "post",
    and the size is also 0 "pre" and "post".
    lpstat_parser.cpp,506,"report") REPORT: cd02
    hp@cd02
    kraux12b.cpp,275,"PrintSelf")               {
    kraux12b.cpp,276,"PrintSelf")
    originnode="zhnpdpt1:KUX
    "
    kraux12b.cpp,277,"PrintSelf")               sampleno=3
    kraux12b.cpp,278,"PrintSelf")               rowno=175
    kraux12b.cpp,279,"PrintSelf")
    timestamp="1160720090335000"
    kraux12b.cpp,280,"PrintSelf")               prt="cd02
    "
    kraux12b.cpp,281,"PrintSelf")               devicenm="hp@cd02
    "
    kraux12b.cpp,282,"PrintSelf")               prntqstate="READY
    "
    kraux12b.cpp,283,"PrintSelf")               prntqdepth=30
    kraux12b.cpp,284,"PrintSelf")               printqsize=362
    kraux12b.cpp,285,"PrintSelf")
    .
    Notice that the data in the "lpstat_parser" tracepoints does not
    match the data in the "PrintSelf" tracepoints
    for the prntqdepth / printqsize values.
    .
    Initial Impact: Medium
    Additional Keywords:
    Print_Queue_Depth
    Print_Queue_Job_Size
    

Local fix

Problem summary

  • Unix OS Agent - UX - does not compute correctly the queue depth
    and size metrics for UNXPRINTQ attribute group.
    

Problem conclusion

  • Considering the low impact of this issue across our customer
    base, there are no plans to address this issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV87239

  • Reported component name

    ITM AGENT UNIX

  • Reported component ID

    5724C040U

  • Reported release

    630

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-25

  • Closed date

    2018-07-12

  • Last modified date

    2018-07-12

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"630","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
08 March 2023