IBM Support

PI17121: BIPEGEN FAILS IF THE HOME DIRECTORY IS NOT IN THE PATH

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If the BIPEGEN JCL member is submitted to create an integration
    server (execution group) specific environment file on z/OS, and
    the UNIX System Services ++HOME++ directory where the
    environment files are to be created is not in the $PATH of the
    administrator who is submitting the job, the CREATENV step
    fails with a file "not found" error.
    
    
    Additional Symptom(s) Search Keyword(s):
    

Local fix

  • In the CREATENV step, change the PARM from
    // PARM='SH cd &H.;. &B..&EG..tmp;&P.>ENVFILE.&EG.'
    to
    // PARM='SH cd &H.;. ./&B..&EG..tmp;&P.>ENVFILE.&EG.'
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Message Broker V7.0 and V8.0 and IBM
    Integration Bus V9.0 configuring integration server (execution
    group) profiles on z/OS.
    
    
    Platforms affected:
    z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If the BIPEGEN JCL member is submitted to create an integration
    server (execution group) specific environment file on z/OS, the
    CREATENV step may fail with a file "not found" error. This can
    occur if the $PATH environment variable set by the UNIX System
    Services profile of the administrator who is submitting the job
    contains neither the 'current directory' denoted by '.' (dot)
    nor the broker's ++HOME++ directory as specified in the BIPEGEN
    JCL.
    
    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
    

Problem conclusion

  • The BIPEGEN JCL now explicitly invokes the integration server
    profile from the correct directory.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.0.8
    v8.0       8.0.0.5
    v9.0       9.0.0.3
    
    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

    PI17121

  • Reported component name

    IB Z/OS

  • Reported component ID

    5655IBB00

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-01

  • Closed date

    2014-05-29

  • Last modified date

    2014-05-29

  • 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

    IB Z/OS

  • Fixed component ID

    5655IBB00

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"9.0","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020