IBM Support

IT15469: BFGLGMG JCL script fails with 'BFGCL0048E: an unknown parameter was specified on the command line' error

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You use the BFGCUSTM JCL script to generate a BFGLGMG script in
    order to migrate a database logger. Running the new BFGLGMG
    script results in the following command being executed:
    
    fteMigrateLogger -trace com.ibm.wmqfte=all
        -tracePath <trace path location>
        -p <configuration_options>
        -credentialPath
        -config <configuration_directory>
        -file <properties_file>
        -loggerName <logger_name>
    
    This command then fails with the error shown below:
    
    fteMigrateLogger:  BFGCL0048E: An unknown parameter was
    specified on the command line: <value>
    
    due to missing value for the "credentialPath" parameter.
    
    Additional Symptom(s) Search Keyword(s):
    

Local fix

  • - Edit the custom job BFGCUSTM, and specify a
      value for CREDENTIAL_PATH.
    - Re-run the BFGCUSTM job, to generate a new
      version of the BFGLGMG JCL.
    - Run the new BFGLGMG JCL.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the MQ V8.0 Managed File Transfer
    component on z/OS who want to migrate a WebSphere MQ File
    Transfer Edition for z/OS agent or database logger to the new
    release using the BFGAGMG and BFGLGMG JCL scripts.
    
    
    Platforms affected:
    z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The BFGCUSTM script provided by the MQ V8.0 Managed File
    Transfer component on z/OS is used to generate a number of
    additional JCL scripts which can be used to perform
    administrative tasks. Prior to running BFGCUSTM, the script
    needs to be edited to include values for the parameters and
    environment variables that it will use when generating the new
    JCL scripts.
    
    The BFGCUSTM script contained the following comment for the
    environment variable CREDENTIAL_PATH:
    
    #
    # CREDENTIAL_PATH Optional variable
    # USS path to credential file for migration
    # Set to blank value if not required
    # e.g. CREDENTIAL_PATH=
    #
    
    However, this environment variable was actually required by the
    JCL scripts:
    
    - BFGAGMG (used to migrate an agent)
    - BFGLGMG (used to migrate a database logger)
    
    If the BFGCUSTM script was edited so that the CREDENTIAL_PATH
    environment variable had a blank value and then executed, the
    BFGAGMG and BFGLGMG JCL scripts that it generated were invalid.
    The scripts would contain entries similar to the ones shown
    below:
    
    BFGAGMG
    --------------
    fteMigrateAgent -trace com.ibm.wmqfte=all
        -tracePath <trace path location>
        -p <configuration_options>
        -credentialPath
        -config <configuration_directory>
        -agentName <agent name>
    
    BFGLGMG
    --------------
    fteMigrateLogger -trace com.ibm.wmqfte=all
        -tracePath <trace path location>
        -p <configuration_options>
        -credentialPath
        -config <configuration_directory>
        -file <properties_file>
        -loggerName <logger_name>
    
    Because no value had been specified for the -credentialPath
    parameter, the scripts would report the following error when
    they were invoked:
    
    BFGCL0048E: An unknown parameter was specified on the command
    line: <value>
    

Problem conclusion

  • The comment for the CREDENTIAL_PATH environment variable in the
    BFGCUSTM script has been updated to indicate that it is required
    when migrating either an agent or a database logger from the
    WebSphere MQ File Transfer Edition product to the MQ Managed
    File Transfer component.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.6
    v9.0 CD    9.0.1
    v9.0 LTS   9.0.0.1
    
    The latest available FTE maintenance can be obtained from
    'Fix List for WebSphere MQ File Transfer Edition 7.0'
    http://www-01.ibm.com/support/docview.wss?uid=swg27015313
    
    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

    IT15469

  • Reported component name

    WMQ MFT V8.0

  • Reported component ID

    5724H7252

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-26

  • Closed date

    2016-06-28

  • Last modified date

    2017-06-01

  • 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

    WMQ MFT V8.0

  • Fixed component ID

    5724H7252

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:
01 June 2017