II13210: THIS APAR WAS CREATED TO DOCUMENT KNOWN PROBLEMS THAT RESULT IN THE OVERLAY OF UCB FIELDS. UCBOVERLAY

APAR status

• INTRAN

Error description

• The following problems have been known to cause UCB overlays:
  (1) OW49989 - DFSMS LOADER
  (2) OW49980 - RSM overlay of words of blanks x'40404040' R703
  (3) OW49890 - RMM overlay storage following tape UCB UCBT
  (4) OW49444 - IOS overlay of 2 words of zeroes at OS/390 R703
  (5) OW46693 - SMF - DCE overlay of 2 words of zeroes (on page
                      boundary
  (6) Vendor product TRX - fix is RX ZAP205
  (7) Vendor product TRX - UCB overlaid for a length of x'9E'
             bytes of zeroes starting on a page boundary.
             TRX fix number is TX ZAP050.
  (8) Vendor product Jobtrac - At OS/390 2.10 overlay of x'AC'
             bytes on a page boundary
  (9) Vendor Product TPM - UCB overlays with eyecatchers of CCB
             and/or MQB, and a TSSxxxxx message. Fix TR51062
  (10) OW38552 - IXFP snapshot overlays UCBFL1 field UCBSTRT
             causing abendC0D in IOSVIRBA
  (11) Vendor Product CA Allocate at os/390 R10 does not
       tolerate changes to TCTIOT structure. The initial overlay
       can eventually propagate into UCB's because the data
       consists of ucb addresses.  The complexity  of this
       scenario is that other components get overlaid with UCB
       addresses they in turn use ucb address as work areas and
       parameter lists on various system services.
       CA APAR LO92617    (aka SAMS ALLOCATE)
       previously known temporary fixes T25A013 and T25A014)
  (12) OW49245 - RSM - Access to UCBs prevented since shared
       pages are marked unusable by RSM.
  (13) Vendor product HSC - STK provided information on HSC fix
       number L1H088M after UCB overlay. In this specific case,
       the UCB IOS extension pointer UCBIEXT was overlaid after an
       abend878 and dump titled:
       COMPON=SLS-JOB PROCESSING,ISSUER=JMESIEST,COMPID=SLS - JOB
          PROCESSING
  (14) OW40764 - DFSMS
       UCBFL1 , UCBWGT , or UCBCHAN overlaid with some kind of
       COMPLETION CODE like 7F 3F or 41 (x'7F' x'3F' or x'41')
  (15) Vendor product TRX - TRX Version 5.0, the fix is ZAP208
       UCBs overlaid on page boundary
  (16) OW55469 DFSMS VSAM incorrect savearea serialization
  (17) UCB Fields which align at offset F14 into a page of UCBs
    have been overlaid with values of an ECB completion code.
    40000000 , 40800000 and other combinations
    BMC Mainview FIXES:
  BPY5733 (or equivalent)
  BPY5774 (or equivalent) (BAY5871)
    These Mainview fixes correct storage usage problems
    which allowed an ECB storage area to FREEMAIN and then
    GETMAIN again by the system as a CAPTURED UCB. Use of the
    old ECB address by BMC resulted in overlays
    UCBEIDAW UCBSNSCT DCEVIB UCBFLP1 are all fields which
   have been overlaid.  xxxxxf14 can result in ABENDB00.
  IECVTCCW can take a PIC13 when running on a 64BIT REAL
  system because UCBEIDAW bit is turned off.
  A normal pattern of the bytes at +f14 is 202A0008
  (18)
  See related CPSM CICSPLEX Session Manager APARs
   PQ67921 ---> PE ---> PQ69785 fix
   PQ67940 ---> PE ---> PQ69745 fix
  UCB Overlay may cause abendSB00 SB00.
  This overlay always occurs at +F14 into the page, and the
  content of the overlay is either '40000000' or '40800000'.
  Since UCBs and their extensions are of fixed size, the
  overlay damages either the DCEVIB pointer or the second
  word in the UCB common extension.
  (19) OA01712 describes an overlay of the UCBVOLI field.
  (20) Overlay on page boundary of captured UCB in below-the-line
       private for x'30' bytes with module name followed by blanks
       For example, DFSRRA00
       The UCB pointer was passed as a plist to CSVQUERY.
       Problem caused by TRX patch TRXV5283 but should not be
       pervasive, since this patch was not widely issued.
  (21) IMS V8 DL/I batch job ABEND formatting causes overlay
       of high private storage.
       ABENDS00DB, UCB overlaid, CDE overlaid.
       This storage overlay typically has a pattern of 5 low
       private addresses and 4 high private address followed
       by x'000000A0'.  These addresses might vary by 4 bytes.
       These symptoms can vary.  PQ73599 should be applied to
       IMS version 8 systems.
  (22) OA03295 - IEAVADMN overlays storage during TCB termination
       ABDUMP processing. In one case, there was a 1 bit overlay
       of the UCBUNTYP field of a captured UCB during processing
       of an abend.
  (23) OA03207 Massive UCB overlay with several pages corrupted.
       The overlaying data includes characters such as
       14SRM SP7.0.4  Logrec has an abend0c4 in IRAPASS2 just
       before the start of the overlay.
  (24) UCB VOLSER volume serial UCBVOLI overlay of the low order
       two bytes. Two different addresses can have the same VOLSER
       APAR OA06604
  (25) BMC data collector running 4.1 Apptune and Pool Advisor
  crashed and in the process of coming down managed to overlay
  low core and damage a page of UCBs. Prior to the IOS abend
  entries in logrec, there are several ABEND0C4 entries made
  by BMC module, CSECT NAME: IODX0064.  Also prior to the
  UCB overlay, PSA is overlaid beginning at +2CC.  Logrec
  contains entries for the PSA overlay made by IEAVESAR for
  abend0c4, IARFPAGD for ABEND0C4 and IARFSEG for ABEND0C4.
  The overlay text at PSA contains the ebcdic for module
  IRXEMSG.  The overlay text on the UCB page points to an
  offset in module IRXEMSG.  BMC calls IRXEMSG in Key 0 and
  causes the overlay.
  BMC APPTUNE FIX# R175537 addresses this problem.
  (26) CA product TSSUTIL: Fix BEA6598 has been written to keep
  TSSUTIL from causing storage overlays if used with a large
  security file (one with more than 256,000 asids). The utility
  can alter data beyond the bounds of its getmained area, which
  in one case caused UCB overlays. The overlaying data pattern
  included individual bit alteration as well as an overlay with
  several words of x'FFFFFFFF'.
  (27) UCB Overlay consistes of data which looks like a register
  save area.  Register 8 in the overlay "savearea" contains the
  address of a control block with eye catcher SMUV or SMUV1. In
  LOGREC, it was found that earlier in the day, an abend0c4
  occurred in a module named PRS40020 which had a BMC copywright
  statement.  Later it was determined that this is part of the
  PROSMS or STOPX37 product. When the abend0c4 occurs, the code
  is running in amode24 and register 13, at the time of error is
  some amode31 bit address... of the form 7Fxxxxxx where xxxxxx is
  the address of a UCB page. Upon further investigation, there was
  not a defect in the PROSMS/STOPX37 product, however it was an
  instalation problem such that a downlevel product was running on
  a later version of zos1.4  Look for the abend0c4 in logrec and
  the low 3 bytes of reg13 will point to the UCB overlay data.
  (28) Mainview PTF BPZ0421 addresses a overlay described by BMC:
  Users of MAINVIEW for CICS may encounter a CSA storage overlay
  with the message "FT462W CICS TERMINATING" when CMRFACT attempts
  to recover from an ABEND in a monitor or other fullscreen
  request running as an SRB in CICS during CICS shutdown.
  The UCB was overlaid with message 'FT462W CICS TERMINATING'.
  (29) Computer Associates ASTEX fix QO53162 corrects a
  problem where ASTEX occasionally re-uses an internal control
  block when it should not. This invalid re-use of the control
  blocks leads to an abend in Auxilliary Storge Manager (ASM)
  code, which can then lead to a spin loop and IPL. This problem
  has only been noticed when ASTEX parameter PAGING=YES was
  specified in the ASTEX start-up parameters. ASTEX code replaces
  the IOSB DIE routine pointer (IOSDIE) - normally this points to
  the DIE routine of the I/O driver, but is replaced to point to
  ASXIOHK ASXDIEE. The resulting symptoms can be varied, and
  different control blocks can be overlaid, depending on what
  driver routine was replaced.
  (30) APARs OA09729 and OA10318 (sysroute for OS/390 R10)
  describe a problem where the UCB can be overlaid after an
  ABENDC03
  The sequence of events leading to the overlay is: An ABEND0C4
  occurs in IFG0TC0A which results in ABENDC03. The ABENDC03
  is retryable but a second ABEND0C4 occurred in IFG0TC0A. The
  overlaying of the UCB is caused by incorrectly saving registers
  during the retry process. Instead of pointing at a CVPL parm in
  IFG0RR0E, the code is pointing at a UCB.
  The nature of the overlay can be varied but UCB NXUCB field has
  been overlaid with zeroes or part of an instruction, UCB CHAN
  and WGT fields have been corrupted, EXTP has also been overlaid
  with all zeroes.
  (31) Entry added 03/31/05
  TRX overlays captured UCBs with a MVCL instruction with length
  x'AC' in module TRXBM, part of the TRX CLIST tracking feature.
  TRX fix ZAP138 corrects the problem. TRX advises that TRX 5.2 is
  the only version supported currently and service level ZAP138
  available March 2005 should be applied.
  The symptoms seen included multiple abends in IOSVPIN and
  IOSVUSER with UCBs overlaid by x'AC' of zeroes.
  (32) APAR OA11495
  IFG0RR0E may overlay captured UCBs with zeroes or data from
  private area as a result of a bad target address and length
  for a MVCL. The symptoms are an AbendE37-08,  followed by a
  subsequent abend0C4.  Abend0DC was also seen because a TCB
  was also overlaid by the bad MVCL.
  (33) APAR PK10591
  When the OMVS segment has not been set-up,
  TCP/IP resolver module EZBRESRV at zOS 1.6 causes random UCB
  overlays of the UCBNXUCB field with 00100000 when incorrectly
  continuing to process a failed call to provide linkage into USS.
  This problem appears to only affect Innovation's FDR products
  which use the NXUCB field.
  (34) PRODUCT: CAIRIM-MVS  RELEASE: 1.0
       APAR #:  QO75220     DATE:  20 DEC 2005
       PROBLEM DESCRIPTION:
        LMP - SQA Storage overlay with no valid LMP keys
        This PTF corrects PE PTF QO66300
        A SQA storage overlay will occur if APAR QO66300
        or CA Common Services for z/OS r11 SP6 is running
        and no valid LMP keys are read in and more then
        40 LMP violation messages are susequently issued.
  
        This APAR also corrects an ASRA storage violation
        in a CICS region when an LMP check is done
        by a CA solution under CICS.
        HYPER: YES
        The overlay in this instance contained the message
         CAS9013A Product DS about to expire or is
          expired and is in use
  (35)
  ISV product DIF from DTS software invalidly issues an SVC 38
  while in cross memory mode.  Its recovery routine receives
  control and stores into a UCB captured page which results in a
  UCB overlay.  The overlay will have the eyecatcher 'DIF'.
  
  TITLE -Abend 0C4 with Simulate 2000 under DB2
  ABSTRACT -When Simulate 2000 was upgraded to rel 4.1, the INIT
  code did not pass the ALET value correctly for cross memory
  mode.
  
  Article ID: DTS41214
  Create Date: 9/11/2006 9:26:00 AM
  Last Modified: 10/2/2006 6:03:00 PM
  Product: DIF
  Type: Service
  Keywords: ABEND0C4, ABENDS0C4, DB2, Y2K, CROSS, MEMORY
  Symptom: Abend 0C4 using Simulate 2000 using DB2 in cross memory
  mode.
  
  Problem: PTL0011 and two DIF modules did not keeping CSRALET.
  This was introduced during the upgrade of Simulate 2000 to 4.1
  (36)
  PRODUCT: CA ENF         RELEASE: 11 SP07
  APAR #:  none planned   DATE:    26 Mar 2007
  PROBLEM DESCRIPTION:
  CA ENF (Event Notification Facility), part of CA Common
  Services, caused actual UCB overlay when an ENF database was
  corrupted.
  SA slip trap taken showed that the overlay was caused by
  CAE$LXQO+0434. Review of the registers at time of overlay showed
  that register 10 had the address of the UCB that was overlaid
  and register 13 had the value that was overlaid.
  -
  Local Fix:
  The CA suggested workaround/cleanup process is to rebuild all
  ENF databases from scratch on all LPARs.
  -
  CA does not plan to fix in the current release.
  ENF DB corruption can have unpredictable results, as in this
  case, and therefore a fix is almost impossible to code.
  However, CA believes that the chances of hitting the overlay
  conditionis very slim.
  (37)
        INTUNE MQ DATA Collector TriLog Service AG
  ABEND0C4 in IOSCDCDR due to UCB OVERLAY
  overlay contains XMQ  "XMQ "  E7D4D840
  Solution:  Apply PTF TPN0123
  (38) OA23299 - ucb overlays with a value of x'00000001'
  at x'50' byte intervals in consecutive ucbxpx ucbioqf, ucbioql,
  ucbchps, ucbxpqh. Abend0C4 in various modules due to the
  overlays.
  (39) OA23230 causes overlay of common storage including IOS
  control blocks. In one case NDCB overlay caused abend0c4 in
  IOSCSSCB after dynamic activate to add a new LPAR
  Item added November 2007
  (40) CA's JCL-CHECK running under ROSCOE may cause UCB overlays
  if recovery is entered. There will be evidence that module
  CAZ2RCVR gets control with bad data in it's registers. The UCB
  will be overlaid with data that appears to be from an SDWA, in
  the customer's case it was the following:
  
  4EE25800 00000000 84106000 81438558 005CC4B0 0000
  
  This problem is being address by CA via PTF TEBE744. CA also
  updated  informational APAR QI92519 which talks about
  properly coding ROSCOE Monitor command.
  
  A work around is to code a NOSPIE parm in the JCL-CHECK options
  list.
  Item added November 2007
  .
  (41) Media Manager UCB one word overlay fixed by OA30083.
  Symptoms seen include overlay of word UCBIEXT but at different
  releases, different words can be overlaid as a result of MM
  inadvertently storing into different offsets from register
  pointing to UCBLOCK UCB lockword.
  Item added October 2009
  .
  (42) IRLM APAR PK99365 fixes a problem where UCBs are overlaid
  during recovery from a previous abend. In one case, after an
  abend878 approx x'48' bytes of UCBOB and extension were overlaid
  LOGREC for the previous abend shows registers pointing into UCB
  storage.
  Item added October 2009
  .
  (43) UCB overlay after SRM abend15F and abend in
       IRARMINT .  UCB overlayed with SRM Regs.
       Abend due to omegamon apars (depending upon
       what release of omegamon)
       OA19529 and OA25566
  (44) Item added Aug 21, 2010 - JES2 APAR OA32551
  The code runs off the end of the getmained area with SDSF
  browse data, so the overlay would be EBCDIC readable job
  data. It is unlikely that OA32551 would cause just some bits
  here and there to be overlaid.
  ***** LATEST ENTRIES IN CONTINUATION INFO APAR II14605 ******
  

Local fix

Problem summary

Problem conclusion

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

Applicable component levels