IV06856: CLEARDEPLOYSTATUS KUICDS010E: NO ENTRY FOUND

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)

APAR status

• Closed as program error.

Error description

• tacmd cleardeploystatus appears to fail due to the process
  trying to query the zOS TEMS associated with the ITM
  Enterprise without success.
  
  Remote Deploy is not supported on zOS systems, yet the query
  to remove entries from these systems is executed which
  results in a query failure.
  
  
  RECREATE INSTRUCTIONS:
  
  Problem description
  6.2.2 Fix Pack 4
  
  Using to clear completed deployments via the tacmd - when
  using the clearDeployStatus the command reports it fails
  despite working.  This is repeatable.
  
  - run tacmd getDeployStatus -t LZ -s (before)
  - - examine the "before" file to see that there are
      deployments that match these settings of "-t" and "-s"
  
  - tacmd clearDeployStatus -t LZ -s (during)
  - - examine the "during" file and it claims that the command
      did not delete entries because there are none, and that
      the command should be executed again.
  
  - tacmd getDeployStatus -t LZ -s (after)
  - - examine the "after" file and indeed there is nothing
      matching this.  This shows that the clearDeployStatus
      command did actually run despite reporting it doing
      nothing.
  
  Enterprise has zOS HOST running. The following appears in
  the TEMS log when an attempt to issue the SQL1 Query
  (cleardeploystatus) is made to the zOS RTEMS.
  
  
  (4E4AB195.000A-2FA0:kdyctrl.cpp,8248,
  "forwardClearDeployStatusSQL1Deploy ") An error occurred,
  rc=[2], while attempting to forward the cleardeploystatus
  sql=[SELECT RETVAL,TRANSID,TASK,RETMSGID,RETMSGPARM,CONTEXT
  FROM KDY.KDYDPLY AT('ZOSAQ:CMS')  WHERE
  COMMAND='CLEARDPLOYSTATUS' AND OPTIONAL='HUB01' AND
  CMDOPTIONS='GETCONFIG' AND STATUS=0;] to TEMS=[ZOSAQ:CMS]
  (4E4AB195.000B-2FA0:kdyctrl.cpp,8132,"forwardClearRequest")
  An error occurred, rc=[2], while attempting to forward the
  cleardeploystatus command to TEMS=[ZOSAQ:CMS]
  

Local fix

Problem summary

• When the z/OS remote monitoring server is present, and a
  cleardeploystatus -s request is issued, the command may return
  the message that there are no entries matching the criteria.
  However, there are entries that are present, and those entries
  that match are indeed cleared.
  
  The message is: CLEARDEPLOYSTATUS KUICDS010E: NO ENTRY FOUND
  when the z/OS remote monitoring server is present
  
  The cleardeploystatus command is issued to all remote monitoring
  servers, including ones that are on z/OS. However, because z/OS
  does not support remote reploy, the command request received by
  the z/OS remote monitoring server is rejected. The rejected
  command causes the hub monitoring server to interpret the remote
  monitoring server response as failure to locate matching entries
  rather than a connection failure.
  

Problem conclusion

• The hub monitoring server now determines if the remote
  monitoring server is running z/OS, and if true, does not attempt
  to send the cleardeploystatus command to that remote monitoring
  server.
  
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.2.2-TIV-ITM-FP0007
    | fix pack | 6.2.3-TIV-ITM-FP0002
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R622 PSY

     UP