IT06486: ACTIVITY AND SUMMARY LOG MAY REFLECT PRIOR SCHEDULE WHEN ACTION=COMMAND INVOKING SCRIPT AND ADJACENT MULTIPLE SCHEDULES

6.3.6.000-TIV-TSMRPT-AGENT-Linux
6.3.6.000-TIV-TSMRPT-AGENT-AIX
6.3.6.000-TIV-TSMRPT-AIX
6.3.6.000-TIV-TSMRPT-AGENT-Windows
6.3.6.000-TIV-TSMRPT-Linuxx86
6.3.6.000-TIV-TSMRPT-Linuxx86_64
6.3.6.000-TIV-TSMRPT-WindowsI32
6.3.6.000-TIV-TSMRPT-WindowsX64
6.3.6.000-TIV-TSMAC-WindowsX64
6.3.6.000-TIV-TSMAC-WindowsI32
6.3.6.000-TIV-TSMAC-SolarisSPARC
6.3.6.000-TIV-TSMAC-Linuxx86
6.3.6.000-TIV-TSMAC-Linuxs390x
6.3.6.000-TIV-TSMAC-AIX
6.3.6.000-TIV-TSMALL-SolarisSPARC
6.3.6.000-TIV-TSMALL-WindowsX64
6.3.6.000-TIV-TSMSTA-WindowsI32
6.3.6.000-TIV-TSMALL-HP-UX
6.3.6.000-TIV-TSMALL-Linuxppc64
6.3.6.000-TIV-TSMALL-AIX
6.3.6.000-TIV-TSMALL-Linuxs390x
6.3.6.000-TIV-TSMALL-Linuxx86_64
7.1.3.000-TIV-TSMSRV-WIN
7.1.3.000-TIV-TSMSRV-SolarisSPARC
7.1.3.000-TIV-TSMSRV-Linuxx86_64
7.1.3.000-TIV-TSMSRV-Linuxs390x
7.1.3.000-TIV-TSMSRV-Linuxppc64
7.1.3.000-TIV-TSMSRV-HP-UX
7.1.3.000-TIV-TSMSRV-AIX
IBM Tivoli Storage Manager V6.3 Fix Pack 6 (6.3.6.000) Server Downloads

APAR status

• Closed as program error.

Error description

• This issue occurs when three things are true:
  
  1.  The Tivoli Storage Manager client scheduler process executes
  a schedule with "action=command", and the specified command
  invokes a script which executes an instance of the command line
  client (dsmc). This second instance of dsmc, which is invoked by
  the scheduler, is unable to obtain the schedule name from the
  scheduler.   In this case, the server will copy the schedule
  name from an existing session for the same node.
  2.  There are multiple schedules for the same node started
  relatively close to each other.
  3.  Sessions for a prior schedule are still running when
  sessions for the current schedule start running.
  
  Example:
  
  There is a schedule defined called 2000_xyz that starts around
  20:00 and another schedule named 2100_xyz that starts around
  21:00. Both schedules are for the same node. In some occasions,
  for example when the server or client is under heavy load, the
  2000_xyz schedule runs long and sessions for it are still
  running after 21:00 when sessions start for schedule 2100_xyz.
  These new sessions may get associated with schedule 2000_xyz.
  
  TSM Versions Affected:
  Tivoli Storage Manager server all levels on all platforms
  
  Initial Impact:
  Low
  
  Additional Keywords:
  TSM; schedule; activity log; summary; IC54677
  

Local fix

• Avoid running multiple schedules for the same node close
  together.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager server users.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available.  This problem is          *
  * currently projected to be fixed in levels 6.3.6 and 7.1.3.   *
  * Note that this is subject to change at the discretion of     *
  * IBM.                                                         *
  ****************************************************************
  

Problem conclusion

• The problem was fixed.
  Affected Platforms: AIX, HP-UX, Solaris, Linux, and Windows.
  

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

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP

• R71A PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP