IBM Support

PI85716: MQ MFT z/OS transfer jobs hang if they contain syntax errors

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

  • When the following z/OS JCL:
    
    	 //TSO              EXEC PGM=IKJEFT01,REGION=0M
     	//STDENV       DD
    PATHOPTS=(ORDONLY),PATH='/u/ebarto/mftenv'
     	//STDOUT      DD SYSOUT=*
    	//STDERR       DD SYSOUT=*
    	//SYSTSPRT   DD SYSOUT=*
     	//SYSTSIN      DD *
     	BPXBATSL PGM -
      	/u/ebarto/mft/bin/fteCreateTransfer +
      	-w   +
      	-sm FT8C -sa Z1 +
       	-dm FT8C -da Z2 -jn TESTJOB +
      	-de overwrite -t text +
      	-df /u/ebarto/target/destination.txt +
      	-skeep +
      	//'EBARTO.JOBS.JCL(TEST1)''
    
     was submitted. The JCL contains a syntax error. The z/OS
    dataset name contained an extra character ' at the end. As a
    result of this, the MFT file transfer never completes. If a
    number of transfers with syntax errors are submitted they can
    delay valid transfer request from running.
    

Local fix

  • Issue the fteCleanAgent command (try it with the -transfers
    option) against the affected MFT agent.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects the users of:
    
     - IBM MQ Managed File Transfer for z/OS V9.0
    
    who run the fteCreateTransfer command.
    
    
    Platforms affected:
    z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a user ran the fteCreateTransfer command via JCL or Unix
    System Services (USS),  if the command contained a syntax error
    (for example: the z/OS dataset name contained an extra chracter
    ' at the end) then a transfer ID was returned, but the transfer
    never finished. Below is an example JCL that causes the problem
    to occur:
    
    	 //TSO              EXEC PGM=IKJEFT01,REGION=0M
     	//STDENV       DD
    PATHOPTS=(ORDONLY),PATH='/u/ebarto/mftenv'
     	//STDOUT      DD SYSOUT=*
    	//STDERR       DD SYSOUT=*
    	//SYSTSPRT   DD SYSOUT=*
     	//SYSTSIN      DD *
     	BPXBATSL PGM -
      	/u/ebarto/mft/bin/fteCreateTransfer +
      	-w   +
      	-sm FT8C -sa Z1 +
       	-dm FT8C -da Z2 -jn TESTJOB +
      	-de overwrite -t text +
      	-df /u/ebarto/target/destination.txt +
      	-skeep +
      	//'EBARTO.JOBS.JCL(TEST1)''
    
    
    The issue occurred because an internal thread within the Managed
    File Transfer (MFT) agent identified a syntax error in the
    dataset name of the  transfer request (the additional character
    '), presumed it was a recoverable error and backed out the
    transfer request message to the SYSTEM.FTE.STATE.<agent name>
    queue. After the message was backed out another internal MFT
    thread consumed the same message, tried to process it and backed
    it out again. This caused the file transfer request XML message
    to get stuck between the internal MFT threads and the
    SYSTEM.FTE.STATE.<agent name> queue. Hence the managed file
    transfer never completed.
    
    If a number of transfers with syntax errors are submitted they
    can delay valid transfer request from running. The reason for
    this was because the internal MFT threads that are responsible
    for processing the transfer requests were busy consuming and
    processing the requests with syntax errors.
    

Problem conclusion

  • IBM MQ MFT for z/OS has been updated so that if a file transfer
    request contains a syntax error in the dataset name (such as the
    extra character ' at the end) the file transfer will no be
    allowed to start. The transfer will fail with the following
    error message:
    
    <supplement>BFGIO0045E: The specified data set name <dataset
    name> is not a valid data set name.</supplement>
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 CD    9.0.5
    v9.0 LTS   9.0.0.3
    
    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

    PI85716

  • Reported component name

    MQ MFT Z/OS V9

  • Reported component ID

    5655MF900

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-09

  • Closed date

    2017-11-28

  • Last modified date

    2017-11-28

  • 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

    MQ MFT Z/OS V9

  • Fixed component ID

    5655MF900

Applicable component levels

  • R900 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":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
28 November 2017