IBM Support

PI86198: Inconsistent aliasing between --jobParameterFile and --jobPropertiesFile in the batchManager and batchManagerZos CLI.

Fixes are available

17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
21.0.0.3: WebSphere Application Server Liberty 21.0.0.3
21.0.0.4: WebSphere Application Server Liberty 21.0.0.4
21.0.0.5: WebSphere Application Server Liberty 21.0.0.5
21.0.0.6: WebSphere Application Server Liberty 21.0.0.6
21.0.0.7: WebSphere Application Server Liberty 21.0.0.7
21.0.0.8: WebSphere Application Server Liberty 21.0.0.8
21.0.0.9: WebSphere Application Server Liberty 21.0.0.9
21.0.0.1: WebSphere Application Server Liberty 21.0.0.1
21.0.0.2: WebSphere Application Server Liberty 21.0.0.2
21.0.0.10: WebSphere Application Server Liberty 21.0.0.10
21.0.0.11: WebSphere Application Server Liberty 21.0.0.11
21.0.0.12: WebSphere Application Server Liberty 21.0.0.12
22.0.0.1: WebSphere Application Server Liberty 22.0.0.1
22.0.0.2: WebSphere Application Server Liberty 22.0.0.2
22.0.0.3: WebSphere Application Server Liberty 22.0.0.3
22.0.0.4: WebSphere Application Server Liberty 22.0.0.4

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The batch management feature's two command line interfaces
    (CLIs) accept a comma-separated list of control properties
    files, to be used to submit and restart jobs.  \n\nAlso,
    though the \"--jobParametersFile\" and
    \"--jobPropertiesFile\" parameters are supposed to be
    aliases of each other in the two CLIs, the aliases were not
    applied consistently in cases in which a sequence of control
    properties is used.   In the case of more than one
    (comma-separated) value, each value's contents are supposed
    to override the last.   But the aliasing wasn't performed
    correctly throughout the override.  E.g.
    --jobParametersFile=A1  in control property file cp1 was not
    correctly overridden by --jobPropertiesFile=A2 in  control
    property file cp2,  in the case that the control properties
    file parameter was set to --controlPropertiesFile=cp1,cp2.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty- Batch                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Inconsistent aliasing between --        *
    *                      jobParameterFile and --                 *
    *                      jobPropertiesFile in the batchManager   *
    *                      and batchManagerZos CLI.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The batch management feature's two command line interfaces
    (CLIs) accept a comma-separated list of control properties
    files, to be used to submit and restart jobs. Also, though the "
    -jobParametersFile" and "--jobPropertiesFile" parameters are
    supposed to be aliases of each other in the two CLIs, the
    aliases were not applied consistently in cases in which a
    sequence of control properties is used.   In the case of more
    than one (comma-separated) value, each value's contents are
    supposed to override the last.   But the aliasing wasn't
    performed correctly throughout the override.  E.g. --
    jobParametersFile=A1  in control property file cp1 was not
    correctly overridden by --jobPropertiesFile=A2 in  control
    property file cp2,  in the case that the control properties file
    parameter was set to --controlPropertiesFile=cp1,cp2.
    

Problem conclusion

  • The --jobParametersFile and --jobPropertiesFile properties found
    are collapsed into a single property with --jobParametersFile
    taking precedence, since each is an alias of the other.   This
    happens within each control properties file. In this way, for
    example, a command line argument or a control properties
    override using one of these aliases, say, "--jobParametersFile"
    will always override an instance of either of the two appearing
    in an earlier (overridden) control properties file.  This was
    not the case in the separate cli's batchManagerZos and
    batchManager.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 17.0.0.3.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI86198

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-21

  • Closed date

    2017-09-25

  • Last modified date

    2017-09-25

  • 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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • RCD0 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022