IBM Support

PI88184: A problem in BFGCMD (BFGZCMD) parsing of arguments that containa comma.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A batch job of MQ Managed File Transfer (MFT) is used to do a
    fteCreateTransfer.
    
    The following parameter with SPACE(1) works and the file is
    transfered:
    -ds "//'MQMFTE.IVP.MVS.OUT';+
    BLKSIZE(800);UNIT(SYSALLDA);VOL(9COL09);MGMTCLAS(NOMGMTCL);+
    SPACE(1);CYL" +
    -de overwrite                                   +
    "//'MQMFTE.IVP.MVS.IN'"
    
    The following parameter with SPACE(1,2) fails:
    -ds "//'MQMFTE.IVP.MVS.OUT';+
    BLKSIZE(800);UNIT(SYSALLDA);VOL(9COL09);MGMTCLAS(NOMGMTCL);+
    SPACE(1,2);CYL" +
    -de overwrite                                   +
    "//'MQMFTE.IVP.MVS.IN'"
    
    The errors include:
    
    BFGIO0001E: File "/u/user1/1);CYL"" does not exist.
    
    BFGIO0045E: The specified data set name
    /'MQMFTE.IVP.MVS.OUT';BLKSIZE(800);UNIT(SYSALLDA);VOL( is not a
    valid data set name.
    
    BFGRP0034I: The file transfer request has completed with no
    files being transferred.
    
    The script that does the parsing of the arguments does not
    expect a comma within the arguments.
    

Local fix

  • - If possible, do not include comma in the parameter
    
    - Another work-around was the following, which has a comma
    after CMD=fteCreateTransfer:
    
    %BFGCMD +
    CMD=fteCreateTransfer,                          +
    -sa AGENT1                                      +
    -da AGENT1                                      +
    -sm CSQ1                                        +
    -dm CSQ1                                        +
    -ds "//'MQMFTE.IVP.MVS.OUT';                    +
    BLKSIZE(800);UNIT(SYSALLDA);STORCLAS(SC001);    +
    SPACE(1,2);CYL"                                 +
    -de overwrite                                   +
    //'MQMFTE.IVP.MVS.IN'
    
    That comma should not be needed, but it allowed BFGCMD to parse
    the parameters correctly.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    -  IBM MQ Managed File Transfer for z/OS V8.0
    -  IBM MQ Managed File Transfer for z/OS V9.0
    
    who are running a batch job (using JCL) that issues
    "fteCreateTransfer" command.
    
    
    Platforms affected:
    z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The "fteCreateTransfer" command issued by IBM MQ Managed File
    Transfer supplied JCL (Job Control Language) failed if a
    parameter of the command contained a comma in it. This was
    because the BFGCMD (BFGZCMD) script that does the parsing of
    arguments used a comma to extract and process the keyword
    parameters, and then split on equals to get parameter and
    arguments.
    
    Expected arguments were:
    &#09;[STDIN,][TRACE,][TMPDIR=<path>,]CMD=<parameters>|PGM=<param
    eters>
    
    Actual arguments were:
    &#09;[STDIN,][TRACE,][TMPDIR=<path>,]CMD=<parameter with a
    comma>|PGM=<parameter with a comma>
    &#09;
    However the script did not expect a comma within the arguments,
    which resulted in terminating the parameter and treating the
    rest of the string after the comma as a separate parameter.
    

Problem conclusion

  • The BFGCMD (BFGZCMD) script has been changed so that parsing of
    parameters that contain a comma is done correctly.
    
    After a PTF containing this APAR has been applied, any new
    agents or loggers that are created will pick up the updated
    script. For existing agent/logger configuration libraries, the
    updated BFGZCMD member will need to be copied into each library
    and BFGCUSTM re-run to implement the change in the customised
    BFGCMD member for that library.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.9
    v9.0 CD    9.0.5
    v9.0 LTS   9.0.0.4
    
    The latest available MQ maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI88184

  • Reported component name

    IBM MQ MFT Z/OS

  • Reported component ID

    5655MFT00

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-29

  • Closed date

    2017-12-17

  • Last modified date

    2017-12-17

  • 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

    IBM MQ MFT Z/OS

  • Fixed component ID

    5655MFT00

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 December 2017