PI39368: EYUVS1058E IN CPSM WUI WHILE IMPORTING VIEWS FROM PDS OR PDSE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You attempt to import WUI views from a PDS or PDSE. You receive
  error message similar to the following:
  .
  EYUVS1058E applid Import failed at record number 2 in data set
       (your.dataset.here), member (membername).
  .
  If it was a PDSE, you try copying the data to a PDS and the
  import may work fine.
  If it was a PDS, you try copying it to a PDSE and again it may
  work fine. So the data itself appears to be fine, but CPSM WUI
  IMPORT processing has an issue at some point.
  .
  If you're capturing trace, you will see trace entries from the
  WUI import process with the following debug texts:
  .
  12345 VVIC VVIE COVC SIM Excp    102 BadObj
  12345 VVIC VVIE COVC SIM Excp     17 NotStart
  .
  .
  Additional Symptom(s) Search Keyword(s): KIXREVSVR
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM V3R2M0 Users                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using the COVC transaction to      *
  *                      import WUI Viewset file, the request    *
  *                      fails with the message:                 *
  *                      - EYUVS0917E Import operation failed    *
  *                                                              *
  *                      The EYULOG of the WUI CICS Region also  *
  *                      reports:                                *
  *                      - EYUVS1058E Import failed at record    *
  *                        number n in data set (datasetname),   *
  *                        member (membername).                  *
  *                                                              *
  *                      In addition to the rejection messages,  *
  *                      the CICS trace dataset in the WUI may   *
  *                      contain CICSplex SM exception trace     *
  *                      entries, issued by modules VVIC & VVIE: *
  *                                                              *
  *                      VVIC - PT-ID:   102   DEBUG: BadOBJ     *
  *                      VVIC - PT-ID:    17   DEBUG: NotStart   *
  *                      VVIE - PT-ID:     2   DEBUG: badVVIC    *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: After applying the PTF that resolves this    *
  *                 APAR, all affected WUIs must be recycled to  *
  *                 pick up the new code.                        *
  *                                                              *
  ****************************************************************
  Before a WUI region can become usable, it has to import a set
  of screen formatting definitions contained within a "Viewset".
  In its original form, viewsets could only be imported from an
  extra-partition CICS Transient Data queue. This function was
  subsequently extended to allow viewsets to be imported
  from an explicitly named Partitioned Dataset (PDS) member
  without passing through an intermediate TD queue.
  
  When a viewset is imported from a PDS (or PDSE) member, the
  file is reblocked into a normalised CICS TS Queue. This
  queue is scanned and its contents are imported to an internal
  control directory, which the WUI uses to build its display
  panels. Within each queue block there can be multiple
  sub-record types. Each MENU or VIEW definition will comprise
  a single "Start of block" record, followed by multiple records
  pertaining to the object being defined, and then a single
  "End of block" record at the end of the logical set.
  There is also provision within the file format for comment
  records and empty null records. These blank/comment
  records may be interspersed anywhere within the
  sub-record stream.
  
  The error being reported has occurred because the
  "Start of block" record was not found where one was expected.
  This is because a logic error in the code meant that if the
  last two subrecords of a physical block were a blank/comment
  followed by a "Start of block", then the "Start of block"
  record was ignored. This caused a process error when the code
  subsequently determined that the expected Start record is
  missing - resulting in the reported error messages and traces.
  

Problem conclusion

• Updates have been made to TS Queue import module EYU0VVIC
  to ensure that if the penultimate sub-record of a block
  is a blank record followed by the "Start of block"
  subrecord for a new MENU or VIEW, then the Start record
  is not skipped.
  

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:

  PI40997 UI29652

Modules/Macros

• EYU0VVIC
  

Fix information

• Fixed component name

  CICSTS V3 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R50M PSY UI29652

     UP15/07/25 P F507

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.