IT45060: Managed File Transfer (MFT) agents report a BFGIO0076E errorwhen transferring data sets on extended attribute volumes

APAR status

• Closed as program error.

Error description

• An IBM MQ Managed File Transfer (MFT) for z/OS agent is acting
  as the source agent for a managed transfer of a data set stored
  on an extended attribute volume (EAV). Shortly after it starts,
  the managed transfer is marked as "Failed" with the following
  supplementary information:
  
  BFGIO0076E : The specified data set //'<data set name>' exists
  but is not a PDS or PDSE.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of IBM MQ Managed File Transfer (MFT)
  for z/OS who have agents that perform managed transfers of data
  sets stored on extended attribute volumes (EAVs).
  
  
  Platforms affected:
  z/OS
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  z/OS uses a catalog and a volume table of contents (VTOC) to
  manage the storage and placement of data sets. Each data set has
  a data set control block (DSCB) in the VTOC which contains
  information about it location, size and attributes (there is a
  useful introduction to VTOCs in the "What is a VTOC?" topic in
  the "z/OS Basic Skills" section of the IBM Documentation site
  here:
  https://www.ibm.com/docs/en/zos-basic-skills?topic=more-what-is-
  vtoc).
  
  If a data set is stored on an extended attribute volume (EAV),
  it will have a Format-8 DSCB in the VTOC. Otherwise, the VTOC
  will contain a Format-1 DSCB for it. These DSCBs are almost
  identical, with just a few small differences between them.
  
  Now, when an MQ Managed File Transfer (MFT) for z/OS agent
  received a managed transfer request involving a data set, it
  would look up the data set's DSCB in the VTOC and use that to
  get information about it. However, the agent always expected the
  VTOC to contain a Format-1 DSCB. This meant that, if the data
  set was stored on an EAV and it's entry in the VTOC contained a
  Format-8 DSCB, the agent was unable to process the DSCB
  correctly. As a result, the agent would mark any managed
  transfers involving data sets stored on EAVs as "Failed" with
  the following supplementary information:
  
  BFGIO0076E: The specified data set //'<data set>' exists but is
  not a PDS or PDSE data set.
  

Problem conclusion

• To resolve this issue, MQ Managed File Transfer (MFT) for z/OS
  agents have been updated to handle Format-1 and Format-8 data
  set control blocks (DSCBs). This allows agents to perform
  managed transfers for data sets, regardless of whether they are
  stored on an extended attribute volume (EAV) or not..
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.2 LTS   9.2.0.25
  v9.3 LTS   9.3.0.20
  v9.x CD    9.3.5
  
  The latest available maintenance can be obtained from
  'IBM MQ Recommended Fixes'
  https://www.ibm.com/support/pages/recommended-fixes-ibm-mq
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'IBM MQ
  Planned Maintenance Release Dates'
  https://ibm.biz/mqplannedmaintenance
  
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• 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 BASE V9.2

• Fixed component ID

  5724H7281

Applicable component levels