A fix is available
APAR status
Closed as program error.
Error description
If DFHLOG log is defined as dummy in the CMAS then the EYUDREP file can not be a recoverable file. If DFHLOG log is set up as a real log in the CMAS then EYUDREP file can be a recoverable file.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V3R2M0 Users * **************************************************************** * PROBLEM DESCRIPTION: You observe resources missing from * * the CMAS's data repository, and incon- * * sistent BAS definitions stored in the * * repository while DFHLOG in the CMAS * * is defined as TYPE=DUMMY. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all CMASes and MASes must be recycled * * to pick up the new code. Note that the * * restarts do not need to be done at the same * * time. * * Before starting a CICSPlex SM CMAS with * * libraries containing the fix for this APAR, * * you must insure that the DFHLOG JOURNALMODEL * * for the CMAS specifies TYPE(MVS). If the * * DFHLOG JOURNALMODEL used by a CMAS does not * * specify TYPE(MVS), the CMAS will terminate * * after issuing message * * . * * EYUXD0113E Data Repository initialization * * failed. * * . * * Either Coupling Facility or DASD-Only log * * streams may be specified. * * Refer to CICS Transaction Server for z/OS * * Installation Guide, Version 3 Release 1 * * (GC34-6426-05), Chapter 25 "Defining the * * logger environment for CICS journaling" for * * information on how to define logstreams for * * the CICS System Log. * **************************************************************** CPSM requires that the EYUDREP file be recoverable, so that incomplete changes can be backed out if a repository update fails or an exception occurs during processing associated with a repository update (for example, BAS Inconsistent Set or Inconsistent Scope checking). Otherwise, the repository may be updated with invalid resources, or resources may be deleted without any audit trail. At one time module EYU0XDIN (XDIN - Data Repository Initialization) checked to insure that DFHLOG was not associated with a dummy logstream, but this check was bypassed during development of a prior release of CPSM so that CMASes could run on processors which did not support the MVS logger.
Problem conclusion
The check to insure that DFHLOG is not associated with a dummy logstream is restored. In addition, termination methods for several CPSM subcomponents were updated to avoid abends due to unavailable structures when a CMAS terminates because of an exception during initialization.
Temporary fix
********* * HIPER * ********* FIX AVAILABLE BY PTF ONLY
Comments
You observe resources missing from the CMAS's data repository, and incon- sistent BAS definitions stored in the repository while DFHLOG in the CMAS is defined as TYPE=DUMMY. CPSM requires that the EYUDREP file be recoverable, so that incomplete changes can be backed out if a repository update fails or an exception occurs during processing associated with a repository update (for example, BAS Inconsistent Set or Inconsistent Scope checking). Otherwise, the repository may be updated with invalid resources, or resources may be deleted without any audit trail. At one time module EYU0XDIN (XDIN - Data Repository Initialization) checked to insure that DFHLOG was not associated with a dummy logstream, but this check was bypassed during development of a prior release of CPSM so that CMASes could run on processors which did not support the MVS logger. The check to insure that DFHLOG is not associated with a dummy logstream is restored. In addition, termination methods for several CPSM subcomponents were updated to avoid abends due to unavailable structures when a CMAS terminates because of an exception during initialization.
APAR Information
APAR number
PK61294
Reported component name
CICSTS V3 Z/OS
Reported component ID
5655M1500
Reported release
50M
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2008-02-20
Closed date
2008-04-29
Last modified date
2008-05-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK35928
Modules/Macros
DYU0MOXT EYU0CITM EYU0MOXT EYU0PTRM EYU0TSTM EYU0WTRM EYU0XDIN EYU0XLBV EYU9XLEV
Fix information
Fixed component name
CICSTS V3 Z/OS
Fixed component ID
5655M1500
Applicable component levels
R50M PSY UK35928
UP08/05/01 P F804
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.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 May 2008