PK56447: EYUJRNL DOESN'T CONTAIN FILE NAME WHEN USING THE API.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• EYUJRNL doesn't contain file name when using the API.
  There is an error in the code in XLSJ that is getting the key
  field from the namelist as used by the API.
  The problem occurs when performing the action on multiple
  records of a result set at once.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM V3R2M0 Users                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: CICSPlex SM Operations action journal   *
  *                      records may be incomplete or            *
  *                      inaccurate. Errors include:             *
  *                                                              *
  *                      - Incorrect Action Names (CPJR_ACTION)  *
  *                      - Missing primary key name              *
  *                      - Incorrect data values                 *
  *                        (CPJR_OPS_FLDDATA)                    *
  *                      - Incorrect CVDA Values                 *
  ****************************************************************
  * RECOMMENDATION: After applying the PTF that resolves this    *
  *                 APAR, all CMASes must be recycled to pick    *
  *                 up the new code.  Note that the restarts     *
  *                 do not need to be done at the same time.     *
  ****************************************************************
  CICSPlex SM Operations Action journal records may be produced
  when the CMAS EYUPARM JRNLOPACT(YES) is set.
  
  EYU0XLSJ (XLSJ - Create Action/Command journal record) is called
  to produce the journal record. Depending on the request, XLSJ
  will generate a CICSPlex SM parameter list (MAL) and then call
  EYU0XLBJ (XLBJ - Build Operations-Type Journal Record) to build
  the journal record from the MAL.
  
  As part of processing, XLBJ will call EYU0MOPM (MOPM - Extract
  parameter related information from MOS) to obtain an internal
  version of the METAPARM resource table records for the action
  being performed in the MAL.
  
  Based upon the returned METAPARM data and the values set in the
  MAL, XLBJ will build the data to be journaled.
  
  A number of logic errors prevent XLBJ from building the correct
  records. This causes the incorrect CPJR_OPS_DATA records from
  being written to the EYUJRNL journal.
  

Problem conclusion

• A number of changes have been made to correct the logic errors:
  
  METAPARM:
  
  - New internal only attributes have been added to the METAPARM
    resource table. These fields contain:
  
    - MAL flag offset byte and bit values.
    - MAL Structured subfield identifiers.
  
    As these fields are internal, the external CICSPlex SM API
    METAPARM record has not changed.
  
  MOPM:
  
  - The MOPM MAL has been changed:
  
    - A new optional input value allows the MOPM caller to pass
      a MAL that should be analyzed.
    - Two new output values have been added to return the Object
      and Action names associated with the MAL
  
  - Using the new MAL parameter MOPM will now use the existence
    bits and where appropriate data fields within the MAL to
    determine the correct action for the request. Once identified
    MOPM will build the necessary METAPARM records.
  
  - The Level 2 exit trace will now include the contents of the
    METAPARM buffer to be returned to the caller.
  
  XLBJ:
  
  - The MAL received from XLSJ is passed to MOPM
  
  - The new object and action fields returned from MOPM will
    be used to set the EYUBCPJR record.
  
  - The internal METAPARM attributes for the MAL flag byte offset
    and bit values are used to determine if data needs to be
    journaled.
  
  - The internal METAPARM attributes for the Structured Subfield
    identifiers are used to locate the correct data to be copied
    to the journal record.
  
  - The CVDA/EYUDA conversion routine has been updated to allow
    for the input value to originate from a CICSPlex SM Namelist.
  
  - The method will now run in Access Register mode.
  
  XLSJ:
  
  - Will now attempt to use pattern offsets in the MAL if the
    instance offsets are not used.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

  PK40222

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

  UK31441

Modules/Macros

•    DYU0MOPM DYU0XDBX DYU0XLBJ EYUB2633 EYUQMOPM
  EYURMOPM EYUR2633 EYUTRDAT EYUT2633 EYUYMOPM EYUY2633 EYUZMOPM
  EYU0MOPM EYU0XDBX EYU0XDP2 EYU0XLBJ EYU0XLSJ EYU9XDPU EYU9XDP3
  EYU9XDP4 METAPARM
  

Fix information

• Fixed component name

  CICSTS V3 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R50M PSY UK31441

     UP07/11/22 P F711

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.