IBM Support

IT12220: ALLOW IIB.CMD COMMAND ON WINDOWS TO USE SETLOCAL FOR ENVS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • On windows, the iib command sets environment variables globally.
    If you want to run against different levels of broker
    then it fails because the environment is already populated.
    This APAR allows you to set an environment variable which
    makes the environment setting only local to the iib command
    being run.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus Version 10 using the iib
    command on Windows.
    
    
    Platforms affected:
    Windows on x86-64 platform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    On Windows, the 'iib' command sets the product environment
    variables globally based on the installation that the command is
    first run from. If you switch to a different installation
    directory, for example at a different fix pack level, and runs
    the iib command again, it will still use the environment from
    the original iib run and therefore the results may not be as
    expected.
    
    This APAR allows the user to set an environment variable which
    makes the environment setting local to the iib command being
    run.
    
    
    <i>There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0.  For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm</i>
    

Problem conclusion

  • The product now allows a user to stop the environment variables
    from being set as global when using the 'iib' command on
    Windows.
    
    To achieve this, set the environment variable IIB_SETLOCAL
    before running the command.
    
    For example:
    set IIB_SETLOCAL=yes
    C:\Program Files\IBM\IIB\10.0.0.1\iib mqsiservice -v
    C:\Program Files\IBM\IIB\10.0.0.2\iib mqsiservice -v
    
    This will run the mqsiservice command from the different fix
    pack installations.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.4
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT12220

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-11-24

  • Closed date

    2016-03-07

  • Last modified date

    2016-03-07

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

  • RA00 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020