IBM Support

IT01330: CLARIFICATION NEEDED FOR SCRIPT PROCESSING OF COMMANDS THAT START BACKGROUND PROCESSES BUT DON'T SUPPORT WAIT=YES OPTION

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as documentation error.

Error description

  • When running a script using the SERIAL command and the command
    being scripted starts a background process but doesn't support
    WAIT=YES option (such as the EXPORT NODE command), the commands
    are considered to be complete once the background thread starts.
    
    Example of a Query Script:
    10 SERIAL
    11 export node xxx filed=all tos=bb FSID=1 mergefilespaces=yes
    15 export node zzz filed=all tos=bb FSID=5 mergefilespaces=yes
    
    As the Export Node starts a background process but does not
    support the WAIT=YES option, the background processes will run
    at the same time even though the SERIAL command was used.
    
    What needs to be documented:
    Need to add clarifying statement that commands that start
    background processes but do not support the WAIT=YES option, are
    considered to be complete once the background thread has
    started.  Basically, these commands run in parallel as they are
    background processes that do not support the WAIT=YES option.
    
    Current documentation:
    www.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.sr
    v.doc/t_srv_auto_script_defn_run_parallel_serial.html?lang=en
    "Running commands serially in a script ensures that any
    preceding commands are complete before proceeding and ensures
    that any following commands are run serially. When a script
    starts, all commands are run serially until a PARALLEL command
    is encountered. Multiple commands running in parallel and
    accessing common resources, such as tape drives, can run
    serially.
    
    Script return codes remain the same before and after a PARALLEL
    command is run. When a SERIAL command is encountered, the script
    return code is set to the maximum return code from any previous
    commands run in parallel.
    
    When using server commands that support the WAIT parameter after
    a PARALLEL command, the behavior is as follows:
    - If you specify (or use the default) WAIT=NO, a script does not
    wait for the completion of the command when a subsequent SERIAL
    command is encountered. The return code from that command
    reflects processing only up to the point that the command starts
    a background process. The final return code from the command is
    not available to your script.
    - If you specify WAIT=YES, your script waits for the completion
    of the command when a subsequent SERIAL command is encountered.
    The return code from that command reflects processing for the
    entire command.
    
    In most cases, you can use WAIT=YES on commands that are run in
    parallel."
    
    Tivoli Storage Manager Versions Affected: All
    
    Initial Impact: Low
    Additional Keywords:
    

Local fix

  • In the case, for the Export Node command, add more client names
    and filespaces to the command.  This will allow the Tivoli
    Storage Manager server to optimize the export for you.
    
    Example:
    export node xxxx,yyyy,zzzz filed=all tos=bbbb FSID=1,3,5,7
    mergefilespaces=yes
    
    This command will process the three nodes and the stipulated
    FSID's for each node.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users Affected:                                              *
    * All Tivoli Storage Manager server users.                     *
    *                                                              *
    * Problem Description:                                         *
    * See error description.                                       *
    *                                                              *
    * Problem Summary:                                             *
    * *                                                            *
    *                                                              *
    * Problem Conclusion:                                          *
    * In the Administrator's Guide, the "Running commands in       *
    * parallel or serially" section will be updated to include the *
    * following restriction:                                       *
    * "If the Tivoli Storage Manager command starts a background   *
    * process which does not have the WAIT parameter, the command  *
    * is considered to be complete after the background thread is  *
    * started. Therefore, the command can run only in parallel."   *
    *                                                              *
    * Affected platforms: AIX, HP-UX, Solaris, Linux, and Windows. *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See error description.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * None                                                         *
    ****************************************************************
    

Problem conclusion

  • In the Administrator's Guide, the "Running commands in parallel
    or serially" section will be updated to include the following
    restriction:
    "If the Tivoli Storage Manager command starts a background
    process which does not have the WAIT parameter, the command is
    considered to be complete after the background thread is
    started. Therefore, the command can run only in parallel."
    
    Affected platforms: AIX, HP-UX, Solaris, Linux, and Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT01330

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    71S

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-25

  • Closed date

    2014-05-15

  • Last modified date

    2014-05-15

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels



Document information

More support for: Tivoli Storage Manager

Software version: 71S

Reference #: IT01330

Modified date: 15 May 2014