IV27433: ADD ABILITY TO DYNAMICALLY TRACE ITM COMPONENTS.

IBM Tivoli Monitoring 6.2.3 Fix Pack 5 (6.2.3-TIV-ITM-FP0005)
IBM Tivoli Monitoring 6.2.3 Fix Pack 2 (6.2.3-TIV-ITM-FP0002)
IBM Tivoli Monitoring 6.2.3 Fix Pack 4 (6.2.3-TIV-ITM-FP0004)

APAR status

• Closed as new function.

Error description

• Add ability to dynamically trace ITM components.
  

Local fix

• N/A
  

Problem summary

• Need ability to dynamically trace IBM Tivoli Monitoring
  components.
  
  
  RAS1 Dynamic Trace is a feature which provides the ability to
  dynamically trace IBM Tivoli Monitoring (ITM) components.  This
  feature obviates the need to re-cycle an ITM monitoring process
  solely for the purpose of changing RAS1 trace settings for that
  process.
  
  RAS1 Dynamic Trace is implemented via tacmd using new options
  listtrace and settrace.  See the APAR Conclusion for more
  details about this new feature.
  

Problem conclusion

• RAS1 Dynamic Trace is implemented via tacmd using new options
  listtrace and settrace. The "tacmd listrace" and "tacmd
  settrace" commands are made available with application of this
  APAR.  Like most tacmd operations, "tacmd listtrace" and "tacmd
  settrace" require a Managed System Name to identify the target
  of the RAS1 trace command.  This means RAS1 Dynamic Trace is
  available to both local and remote ITM processes with this
  feature support.
  
  Usage:
  ------
  Full details of the usage can be seen by issuing the "tacmd
  settrace" and "tacmd listtrace" when logged in to a management
  server that is running IBM Tivoli Monitoring 623 FP2 or later.
  
  tacmd settrace:
  {-m|--system} SYSTEM
  {-p|--property} PROPERTY
  {-o|--option} OPTION
  [{-d|--description}] DESCRIPTION
  
  
  tacmd listtrace:
  {-m|--system} SYSTEM
  {-p|--property} PROPERTY
  
  
  Examples of use:
  >tacmd listtrace -m  host1:LZ -p KBB_RAS1
  KUILTR000I: The current value of KBB_RAS1 at host1:LZ is:
   ERROR
  
  >tacmd settrace -m  host1:LZ -p KBB_RAS1 -o "ERROR (UNIT:KLZ
  ALL)"
  KUISTR000I: Command was performed successfully.
  
  >tacmd listtrace -m  host1:LZ -p KBB_RAS1
  KUILTR000I: The current value of KBB_RAS1 at itmmtvm08:LZ is:
   ERROR (UNIT:KLZ ALL)
  
  
  Versions supported:
  -------------------
  To list or set the trace for an IBM Tivoli Monitoring (ITM)
  component, the managed system and all the management servers
  must be running version 6.23 FP2 or later. Otherwise you will
  see a message similar to the following:
  
  >tacmd listtrace -m ms1:KUX -p KBB_RAS1
  KUILTR241E: Target system ms1:KUX does not support the listtrace
  command.
  The specified target system is running an earlier software
  version that does not support the listtrace command.
  The target system must be upgraded to version 06.23.02.00 or
  later to successfully run the listtrace command.
  
  >tacmd listtrace -m ms2:machine1:R2 -p KBB_RAS1
  KUILTR251E: A HUB or RTEMS in the path to ms2:machine1:R2 does
  not support the
  listtrace command. At least one TEMS in the path to the
  specified managed system
  is running an earlier software version that does not support the
  listtrace
  command. Each HUB and RTEMS in the path to the target managed
  system must be
  upgraded to version 06.23.02.00 or later to successfully run the
  listtrace
  command
  
  
  Values replaced:
  ----------------
  The RAS1 Dynamic Trace "settrace" command replaces the current
  RAS1 setting for a process; it does not augment (add to) the
  current RAS1 setting. This also means "settrace" now replaces
  the RAS1 settings established in any configuration file. A
  second "settrace" (like all subsequent "settrace" commands)
  completely replaces the previous RAS1 trace settings for a
  process.   Note that the RAS1 settings defined in the
  configuration file are not changed, and when the component is
  restarted, it will use the RAS1 values as defined in the
  configuration file.
  
  
  Service Console Change:
  -----------------------
  The ITM/Service Console "RAS1 SET" command has also been updated
  to replace the current RAS1 setting for a process, like the RAS1
  Dynamic Trace 'settrace' command; it does not augment (add to)
  the current RAS1 setting as the ITM/Service console has done in
  the past. This is a change in behavior introduced with RAS1
  Dynamic Trace.  This was done to provide consistent behavior
  between these two mechanisms used to alter RAS1 trace settings.
  This also means "RAS1 SET" now replaces the RAS1 settings
  established in any configuration file. A second "RAS1 SET" (like
  all subsequent "RAS1 SET" commands) completely replaces the
  previous RAS1 trace setting for a process.
  
  <u>How to set dynamic trace on z/OS:</u>
  In the absence of tacmd functionality, RAS1 Dynamic Trace is
  available to Tivoli monitoring processes on z/OS via Tivoli
  distributed platform agents.  The tacmd is available to Tivoli
  monitoring distributed agents, so any such agent connected to a
  z/OS management server can be used to action RAS1 Dynamic Trace
  on that management server.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | 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:

  OA40444

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R623 PSY

     UP