IC54677: SCHEDULE NAME NOT STORED IN THE SUMMARY TABLE FOR SCHEDULED EVENT

APAR status

• Closed as program error.

Error description

• This issue occurs when the TSM 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.  This results in an event in the summary table
  without a schedule name associated with it.
  .
  q ev show the schedule as finished:
  11/11/2007 12:00:00 11/11/2007 12:05:08  ABC123DOM  DOM_345
  completed.
  
  But select from summary table doesn't show the schedule_name:
   START_TIME: 2007-11-11 12:07:17.000000
          END_TIME: 2007-11-12 06:50:24.000000
          ACTIVITY: BACKUP
            NUMBER: 273
            ENTITY: DOM_345
          COMMMETH: Tcp/Ip
           ADDRESS: 192.168.2.55:46143
     SCHEDULE_NAME:
          EXAMINED: 0
          AFFECTED: 1708
            FAILED: 0
             BYTES: 357097443864
              IDLE: 555
            MEDIAW: 224
         PROCESSES: 1
        SUCCESSFUL: YES
       VOLUME_NAME:
        DRIVE_NAME:
      LIBRARY_NAME:
          LAST_USE:
         COMM_WAIT: 32762
  NUM_OFFSITE_VOLS:
  
  
  TSM Versions Affected:
  All Versions of Tivoli Storage Manager Server on all platforms
  
  Initial Impact: Low
  
  Additional Keywords:
  action=command, event, clientaction, schedule, sql, select
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All TSM Server users of schedules            *
  *                 with "action=command".                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available.           *
  *                 This problem is currently projected          *
  *                 to be fixed in level 5.3.6.3,                *
  *                 5.4.3 and 5.5.1. Note that this is           *
  *                 subject to change at the discretion          *
  *                 of IBM.                                      *
  ****************************************************************
  *
  

Problem conclusion

• The TSM server has been corrected.
  

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:

  PK59993 PK59995 PK65798

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R53A PSY

     UP

• R53H PSY

     UP

• R53L PSY

     UP

• R53S PSY

     UP

• R53W PSY

     UP

• R54A PSY

     UP

• R54H PSY

     UP

• R54L PSY

     UP

• R54S PSY

     UP

• R54W PSY

     UP

• R55A PSY

     UP

• R55H PSY

     UP

• R55L PSY

     UP

• R55S PSY

     UP

• R55W PSY

     UP