IBM Support

IC89425: TIVOLI STORAGE MANAGER SERVER SERVICE IS NOT STOPPED WHILE OS RUNLEVEL BEING CHANGED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Tivoli Storage Manager server for Linux Installation Guide
    introduce the steps to register the service on Linux systems.
    However, even when registering service according to the steps,
    the service stop operation is not invoked while OS runlevel
    being changed.
    
    
    Here is the steps to register server service:
    (ref. "Alternative method of automatically starting servers on
    Linux systems")
    ---------------------------
    In this example, the instance owner is tsminst1 and the server
    instance
    directory is /home/tsminst1/tsminst1. Create a copy of the
    dsmserv.rc script
    called /etc/rc.d/init.d/tsminst1. Use the CHKCONFIG utility to
    configure the
    script to start at run level 5.
    cp /opt/tivoli/tsm/server/bin/dsmserv.rc
    /etc/rc.d/init.d/tsminst1
    chkconfig --list tsminst1
    service tsminst1 supports chkconfig, but is not referenced in
    any runlevel
    (run ?chkconfig --add tsminst1?)
    chkconfig --add tsminst1
    chkconfig --list tsminst1
    tsminst1 0:off 1:off 2:off 3:off 4:off 5:off 6:off
    chkconfig --level 5 tsminst1 on
    chkconfig --list tsminst1
    tsminst1 0:off 1:off 2:off 3:off 4:off 5:on 6:off
    
    
    Tivoli Storage Manager Versions Affected: TSM 6.3 for Linux
    platform
    
    
    Customer/L2 Diagnostics (If Applicable)
    The cause of the problem is that dsmserv.rc generate a lock file
    whose name is "dsmserv" though Installation Guide recommends to
    register service as <INSTANCE_NAME>(6.X) or "dsmserv.rc"(5.5).
    As the result of following the steps in manual, there will be a
    K10<SERVICE_NAME> located on "/etc/rc*.d".
    While runlevel being changed, Linux will check if there is lock
    file under "/var/lock/subsys", whose name is <SERVICE_NAME> to
    judge whether the  service is running and it should be stopped.
    When there is a lock file whose name is the same as the one for
    service, Linux OS will run K10<SERVICE_NAME>.
    However, because the name of the lock file is "dsmserv", it is
    not the same as the recommended <SERVICE_NAME> and Linux will
    not run K10<SERVICE_NAME>.
    As the result, server service will not be stopped while OS
    runlevel being changed.
    * <SERVICE_NAME> is the name which was used while issuing
    "chkconfig--add".
    
    
    Initial Impact: Middle
    
    
    Additional Keywords: zz63 dsmserv.rc chkconfig
    K10tsminst1 service
    

Local fix

  • When the name of lock file is the same as the name of service,
    Linux OS will run K10<SERVICE_NAME> as expected while runlevel
    being changed.
    
    To avoid encountering the problem, change the dsmserv.rc script
    at two points as follows:
    old: /var/lock/subsys/dsmserv
    new: /var/lock/subsys/<SERVICE_NAME>
    when there are multiple services:
    new: /var/lock/subsys/${instance}
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Tivoli Storage Manager server users      *
    *                 of the alternative method of automatically   *
    *                 starting servers on Linux systems.           *
    ****************************************************************
    * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in level 6.3.4. Note that this is subject    *
    *                 to change at the discretion of IBM.          *
    ****************************************************************
    *
    

Problem conclusion

  • This problem was fixed.
    Affected platforms:  Linux.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC89425

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-10

  • Closed date

    2013-01-28

  • Last modified date

    2013-03-03

  • 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

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"63L","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
03 March 2013