PM08656: MSG4191I TAPE FILE PROCESSING FAILURE RC=048 WHEN RUNNING AN AUXTRACE TO TAPE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You receive MSG4191I TAPE FILE PROCESSING FAILURE RC=048 when
  trying to run AUXTRACE to tape (NOT VTAPE) when capturing
  data for problem analysis assistance.
  You also receive MSGDFHTR0116 which points to an ABEND in the
  subroutines module DFHTRSU.
  KIXREVBDB
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Using a tape for CICS auxiliary trace   *
  *                      causes message 4191I TAPE FILE          *
  *                      PROCESSING FAILURE RC=048 and a CICS    *
  *                      2C5/AKEB abend.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The customer attempted to use a tape drive for CICS auxiliary
  trace due to the amount of data that was expected to be
  produced. However, when the trace was started, a VSE message
  was produced, the trace was not started and CICS produced a
  2C5/AKEB reason code 09000000 abend.
  
  4191I TAPE FILE PROCESSING FAILURE RC=048
  
  The reason for the failure is that DFHEVOP module DFHEVOMT
  builds a DTFMT with TYPEFLE=OUTPUT instead of TYPEFLE=WORK,
  which is required to support the WRITE macro used for the
  trace data.
  
  The tape logic module does not support WRITE, and uses SVC 50
  (0A32) to force the abend, which CICS then handles as a
  2C5/AKEB abend.
  
  Additional keywords: DFHAUXT DFHBUXT MSG4191I ABEND2C5 ABENDAKEB
  

Problem conclusion

• DFHEVOP has been changed as follows:
  
  1. When DFHAUXT and DFHBUXT are opened for output, a DTFMT
     TYPEFLE=WORK is built.
  2. A check is made to see if there is a TLBL for DFHAUXT or
     DFHBUXT and the DTFMT is built to handle a labelled tape
     for input or output.
  3. If DFHAUXT or DFHBUXT is not assigned to a disk or tape
     device, error message msgDFHEV9941S is produced.
  4. To allow tape drive switching to occur, DFHAUXT is on
     logical unit SYS009 and DFHBUXT is on logical unit SYS019.
     Tape OPEN/CLOSE/EOV will force the tape to be rewound
     without being unloaded.
  
  DFHTRAO has been changed as follows:
  
  1. EOV on a real tape volume is now correctly handled.
  
     Note that EOV on a z/VSE VTAPE cannot be detected,
     and will result in an I/O error. The auxiliary trace
     will be stopped and data will be lost. This is a
     restriction of the z/VSE VTAPE buffering and cannot
     be changed.
  
  DFHTRSU has been changed as follows:
  
  1. Module DFHTRSU error checking has been changed to match
     the emulation of the asynchronous WRITE requests to the
     auxiliary trace dataset.
  
  The CICS Transaction Server for VSE/ESA V1.1 System Definition
  Guide SC33-1651-05 has been updated to describe the use of
  tapes for Auxiliary Trace in Chapter 17
  
  "Defining auxiliary trace data sets".
  
  The third paragraph has been updated to:
  
  If your auxiliary trace data set is on tape, you must
  specify device SYS009 in the ASSGN job control statement
  for DFHAUXT and SYS019 for DFHBUXT. If a labeled tape
  is used, the TLBL name for the data set must be DFHAUXT
  or DFHBUXT. To avoid problems with tape management
  systems' labeled tape support, IBM recommends that
  unlabeled tapes be used.
  
  A fourth paragraph has been added:
  
  z/VSE VTAPE volumes may be used for Auxiliary Trace.
  However, as z/VSE cannot correctly identify the
  end-of-volume, the CICS trace output may generate
  an I/O error resulting in Auxiliary Trace being
  stopped, with some data loss due to the VTAPE
  buffer not being completely written to disk. For
  VTAPE mapped to VSAM ESDS, the maximum VSAM
  RECORDSIZE parameter value must be 4096 or
  greater.
  
  "Job control statements for CICS execution"
  
  Note 3 has been updated to:
  
  If you place the auxiliary trace data set on tape,
  you must use the following job control statement:
  for DFHAUXT:
  // ASSGN SYS009,cuu
  
  For DFHBUXT use:
  // ASSGN SYS019,cuu1
  
  Where "cuu1" is a different tape drive address to
  the one used for DFHAUXT.
  
  Note: You should be aware that some other products
  may use SYS009 for other functions (for example, ICCF
  uses SYS009 as the default for the system console).
  
  You must mount a tape on each assigned tape drive
  before entering the master terminal command to
  turn on the auxiliary trace.
  
  If you intend using a labeled tape volume, you need
  to add one or more TLBL statements, for example:
  
  // TLBL DFHAUXT,'CICS411.DFHAUXT'
  // TLBL DFHBUXT,'CICS411.DFHBUXT'
  
  IBM recommends that you do not use a TLBL DISP
  parameter other than DISP=NEW, otherwise the
  results will be unpredictable.
  
  As previously stated, IBM recommends that labeled
  tapes are not used so as to avoid problems with
  tape management software products.
  
  CICS rewinds the tape volume to its load point during
  OPEN/CLOSE/EOV. When CICS switches tape drives, any
  previous data on that volume is normally overwritten.
  This provides exactly the same function as Auxiliary
  Trace to disk.
  
  The tape drives remain allocated to the CICS
  partition until CICS is shut down.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK56732

Modules/Macros

•    DFHEVOCM DFHEVOMT DFHEVOP  DFHEVSIO DFHTRAO
  DFHTRSU
  

Fix information

• Fixed component name

  CICSTS FOR VSE

• Fixed component ID

  564805400

Applicable component levels

• RB0P PSY UK56732

     UP10/05/07 P E430

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.