IZ48625: ITM 6.2 FP01 & ITM 6.2.1 TMSDLA.SH FAILS TO RUN ON UNIX/LINUX

APAR status

• Closed as program error.

Error description

• Severity: 3
  Approver:mb
  Compid:  5724C04PS Tivoli Enterprise Portal Server
  Abstract:tmsdla.sh fails to run on Unix/Linux platform
  
  Environment:
    Unix and Linux environments.
    TEPS 6.20 FP1, 621
  Problem Description:
    Documentation is unclear on how to invoke tmsdla.sh.  The
  proper way
    is to use the following syntax:
  
    ./itmcmd execute cq "tmsdla.sh"
  
    Even using the above syntax will fail because the script
  expects that
    it will be run from the cq/bin directory and not the ITM
  install home
    directory.
  
    In addition, for the ITM 6.20 TEPS, the agent xml files are
  installed
    in cq/tmsdla directory, but the java executable expects the
  agent xml
    files to be in cq/bin/tmsdla.
  
    In both cases, the script will fail with the following error:
  
       Starting user script...
       Errors found.  Highest severity:  12
       12:  Problem with output file.
  
  java.io.FileOutputStream.<init>(FileOutputStream.java:205)
  
  java.io.FileOutputStream.<init>(FileOutputStream.java:96)
           java.io.FileWriter.<init>(FileWriter.java:69)
  
       com.ibm.tivoli.monitoring.tmsdla.SingleOutputFile.make(
          SingleOutputFile.java:141)
  
  com.ibm.tivoli.monitoring.tmsdla.TmsDla.main(TmsDla.java:182)
  
    In 621 it fails because the script does not change the
  directory to
    cq/bin and in 620 it fails because because it does not change
  the
    directory to cq/bin AND the tmsdla directory does not exist
  under
    cq/bin.
  Detailed Recreation Procedure:
    1. From the ITM Home install bin directory issue:
        ./itmcmd execute cq "tmsdla.sh"
    2. The following errors will display:
  
       Starting user script...
       Errors found.  Highest severity:  12
       12:  Problem with output file.
  
  java.io.FileOutputStream.<init>(FileOutputStream.java:205)
  
  java.io.FileOutputStream.<init>(FileOutputStream.java:96)
           java.io.FileWriter.<init>(FileWriter.java:69)
  
       com.ibm.tivoli.monitoring.tmsdla.SingleOutputFile.make(
          SingleOutputFile.java:141)
  
  com.ibm.tivoli.monitoring.tmsdla.TmsDla.main(TmsDla.java:182)
  
  Related Files and Output:
    No special logs required, only the console output.
    configuration files, coredumps, etc.
  

Local fix

• Workaround:
    For ITM 620:
    1. Create a tmsdla directory under cq/bin
    2. Copy all files from cq/tmsdla to cq/bin/tmsdla
    3. Continue steps for ITM 621
  
    For ITM 621
    1. Make a copy of the tmsdla.sh in cq/bin as tmsdla_orig.sh
    2. Edit tmsdla.sh and add the following line:
           cd ${KFW_BIN_DIR}
  

Problem summary

• The documentation is unclear on how to invoke tmsdla.sh.  The
  proper way is to use the following syntax:
  
  ./itmcmd execute cq "tmsdla.sh"
  
  However even using the above syntax will fail because the script
  expects that it will be run from the cq/bin directory and not
  the ITM install home directory.
  
  In addition, for the ITM 6.2.0 TEPS, the agent xml files are
  installed in cq/tmsdla directory, but the java executable
  expects the agent xml files to be in cq/bin/tmsdla.
  
  In both cases, the script will fail with the following error:
  
     Starting user script...
     Errors found.  Highest severity:  12
     12:  Problem with output file.
     java.io.FileOutputStream.<init>(FileOutputStream.java:205)
     java.io.FileOutputStream.<init>(FileOutputStream.java:96)
     java.io.FileWriter.<init>(FileWriter.java:69)
  com.ibm.tivoli.monitoring.tmsdla.SingleOutputFile.make(SingleOut
  putFile.java:141)
     com.ibm.tivoli.monitoring.tmsdla.TmsDla.main(TmsDla.java:182)
  
  In 621 it fails because the script does not change the directory
  to cq/bin and in 620 it fails because because it does not change
  the directory to cq/bin and the tmsdla directory does not exist
  under cq/bin.
  

Problem conclusion

• The tmsdla.sh script was modified to work when run by the itmcmd
  execute command.  This will allow for proper setup of the
  environment variables.
  
  Now when you run the script via itmcmd from the $CANDLEHOME/bin
  directory:
  
  ./itmcmd execute cq "tmsdla.sh"
  
  You should see something similar to the following:
  
     Starting user script...
     Starting tmsdla.sh at  Thu Apr 9 21:14:47 CDT 2009
     No errors during run.
     Ending tmsdla.sh at  Thu Apr 9 21:14:56 CDT 2009
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | fix pack | 6.2.0-TIV-ITM-FP0003
  

Temporary fix

• For ITM 620:
     1. Create a tmsdla directory under cq/bin
     2. Copy all files from cq/tmsdla to cq/bin/tmsdla
     3. Continue steps for ITM 621
  
     For ITM 621
     1. Make a copy of the tmsdla.sh in cq/bin as tmsdla_orig.sh
     2. Edit tmsdla.sh and add the following line:
            cd ${KFW_BIN_DIR}
  

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

  TEPS

• Fixed component ID

  5724C04PS

Applicable component levels

• R620 PSY

     UP