II14411: OEM BUGS IN DFSMS DATA MANAGEMENT - OPEN/CLOSE/EOV, ACCESS METHODS, PDSE, HFS, CMM, CVAF, DADSM

APAR status

• Closed as canceled.

Error description

• #1
  IGWMSCST+54E ABEND0F4 RC24 RSN5A070022
    0F4 rsn5A070022 is detected due to an invalid VSB.
  The VSB was overlayed with XPEDTRC from Xpediter.
  The problem is resolved by Xpediter/TSO PTF XTE0075
  ----------------------------------------------------------------
  #2
  IEC999I IFG0TC0A IFG0TC0B DEBADDR=xxxxxx-1,DSN = xxxxxxx
    After new release of Syncsort, IEC999I ABENDC03 and
  ABEND0C4 in IFG0TC0A due to DEB having been freed .
  Prior to the upgrade, previous job executions received
  WER225I E35 RC INVALID, IGNORED, but job ran successfully.
  After the upgrade, the job now fails.
  Syncsort apar for rel 1.3 SY66241 fixed the problem.
  ----------------------------------------------------------------
  #3
  IEC141I 013-60 SECZIP PKWARE PKZIP
    JCL has blksize=80   lrecl=80 and recfm=f but dcb
  shows     blksize=4096 lrecl=80 and recfm=f
  The blocksize value got changed and was no longer equal to
  the lrecl which is required for a FIXED recfm.
  The fix was:
  ACFMGR    Load  Mar12 4541  Abend 013-20 ARCHOUT BLKSIZE < 4096
  PKINIT24  Load  Mar12 4541  Abend 013-20 ARCHOUT BLKSIZE < 4096
  
  The fix was released in Maintenance level 6.  You are currently
  at
  SecureZIP(R) for z/OS, Version 10.0b - 03/28/08 14.27 LVL(5)
  You can download the most current levelset from the following
  link:
  SecureZIP V10 - Non-SMP/E Levelset
  ftp://bigiron.pkware.com/pub/patches/securezip/zSeries/100/szlev
  elset100
  .exe
  
  SecureZIP V10 - SMP/E Levelset
  ftp://bigiron.pkware.com/pub/patches/securezip/zSeries/100/secur
  ezipzoss
  
  mpptf100.exe
  Local circumvention would be to use blksize=0, lrecl=80 and
  recfm=FB .
  ----------------------------------------------------------------
  #4
  ABEND0C4 in IGBDCSDR z/OS 1.10  HDZ1A10 using SYNCSORT
    After upgrading to R10, SYNCSORT jobs using DASDCALC fail with
  ABEND0C4 in IGBDCSDR.  The failing CLI instruction 95F1 202C is
  trying to check for a valid F1 identifier in the DSCB table and
  goes beyond the end of the table because there is no zero entry
  in the DSCB table to signify the end of the list.   The same job
  does not fail prior to R10 because the DIS code did not enforce
  this requirement.  Now at R10, the code is enforcing the need to
  have a zero address at the end of the DSCB table.
  SPZAP from Syncsort resolved the 0C4 .
  ----------------------------------------------------------------
  #5
  Missing Totalblocks in IEC205I using SYNCSORT
    Total blocks weren't being recorded because DCBMRABC was being
    turned off.  Syncsort provided fix EW6720-0
  ----------------------------------------------------------------
  #6
  Hang on SYSVTOC after a Job Abend. The DASDM ESTAE
  routine had been deleted from the STAE chain by CA-ALLOCATE
  STAE. This is resolved by CA Allocate fix - T25D07C
  ----------------------------------------------------------------
  #7
  0C4 abends in IGC0003B per the below:
  
  IEC999I IGC0003B,DBC,CTDBA,225B,TST075
  IGD300I AN ABEND OCCURRED DURING SMS PROCESSING 603
    ABEND SYSTEM CODE=0C4 ASID=00E1
    COMPONENT NAME=SMS  COMPONENT ID=DF101
  DUMP TITLE=COMPON=SMS,COMPID=DF101,ISSUER=IGDERDM2,CSECT=UNKNOWN
             N ,OFFSET=UNKNOWN ,ASMDATE=UNKNOWN,FMID=UNKNOWN
  
  Problem was caused by an invalid FMT9 DSCB address being passed
  to the DADSM Space Allocatin Request Validation routine IGC0003B
  
  Problem was resolved by Innovation ZAP P-54.6759
  ----------------------------------------------------------------
  #8
  Intermittant ABEND0C4 in IGC018+1FA at z/OS 1.8
  .
  PTF(T170ATA6) from Allen Systems Group resolved the issue.
  ----------------------------------------------------------------
  #9
  WAIT in IGG0201Z.
   - RB Chain shows close issued, then SYNCH from BMC code, then
     CLOSE is redriven by DP24W (BMC).
  
  BMC Fixes are:
    Module DAPPOSAM:           BQ44242, I329151 and G154966
    Module DAPPTERM:           BQ44243
  ---------------------------------------------------------------
  #10
  IMWEBSV task abends following S913 abend
  IEC150I 913-38,IFG0194E
  +CEE0374C CONDITION=CEE3250C TOKEN=00040CB2 61C3C5C5
  The ABEND913 was issued from CA-TSS module TSSFFAPP .
  With Racroute Auth call return code = 8 :
  If Racroute Auth RsnCode=65 - Access Denied & the task recovers.
  If Racroute Auth RsnCode=6C - Only FETCH access allowed (i.e.
  execute) but requested to read, the task abends & does not
  recover.  CA provided fix BIT8627.
  With the fix, the task receives a 913-70 abend as expected.
  Please contact CA prior to installing this fix, since it
  addresses a secondary problem where FETCH access can allow READ
  to a dataset under limited circumstances.
  ----------------------------------------------------------------
  #11
  IEC999I IGC0002G IFG0RR0A ABEND0C4
    The 0C4 is occurring in Dadsm's Obtain module IGC0002G, due to
  the required 140-byte return area not being all available.
  The address of this area was provided by Obtain's caller
  XBPAM+02E8 from Xerox software.  Xerox provided the following
  fix for their XPAF product which resolves the problem.
  Fix number:   PA12935
  Log number:  841585203
  Maintenance tape:  WA9078
  Internal number:  12935
  Description:
    When attempting to start XOSF on a z/OS 1.10 system with
    DIAGnostic "NUCLABEL ENABLE(IGVGPVTN)" in effect an ABEND
    0C4 occurs
  ----------------------------------------------------------------
  #12
  IEC145I 413-1C using Smart Restart from RAI
    ABEND413 RC1C received when using Smart/Restart product from
  RELATIONAL ARCHITECTS INTERN with DISP=NEW allocations for
  multivolume data sets and JFCBVLSQ > JFCBNVOL.
  Other messages that may be seen in joblog.
    +srsXEOV - Volume switch in progress
  RAI provided fix P108206A .
  ----------------------------------------------------------------
  #13
  Repetitve ABEND0C1 in SMS during dsn allocation
  
  When starting BMC's Mainview Storage Resource Manager at the
  same time as Unicenter CA-PMO is starting, there is a
  possibility that Mainview SRM will receive one or more S0C1
  abends. The abend occurs in the Mainview SRM module BUD0011
  because the address of IGGPOST0 in the Link Pack Directory
  Entry (LPDE) is zero.
  
  Following messages may be seen in the log :
  
  IGD080I SMS DUMP SUPPRESSED FOR CSECT UNKNOWN COMP CODE S0C1
  IGD306I UNEXPECTED ERROR DURING SVCSDUMP PROCESSING 283
  RETURN CODE 8 REASON CODE 20024
  THE MODULE THAT DETECTED THE ERROR IS IGDERDM2
  SMS MODULE TRACE BACK - ERDM2 SSIP2 SSIPC ERDMP SSIRR ERRTR
  VTSDA VTSCR SSIRT
  SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00000
  
  Solution : CA PMO APAR QO77360 for Release 4.3 will Page-Fix
  the LPDE before updating the address of IGGPOST0 in the LPDE.
  ----------------------------------------------------------------
  #14
  IEC141I 013-4C IGG0191A Z/OS 1.11 using CA's Compress
    ABEND013 RC4C followed by the following message
  DB002255 C-4M352: Function OPEN DDname SYSIPT Open error 103.
  Problem was resolved by CA.  RO15232 is PE.
  Please contact CA for more information
  ----------------------------------------------------------------
  #15
  ABEND0C4 ABEND378 RC14 IFG0RR0A IFG0RR0E
    Various abend0c4s in open/close/eov estae error recovery
  modules can occur running BMC Mainview product.
  The RRPLIST (recovery OPEN/CLOSE/EOV/DADSM parameter list)
  is either invalid or has been freed.  BMC recommendations follow
  
  1.  Apply BPG6020 or BPG6004 (depending on SRM release)
  2.  Do not run SVSGC component
  3.  Back-off BPG5967 or BPG5987 (depending on SRM release) and
      do not perform any dynamic I/O reconfigurations
  ----------------------------------------------------------------
  #16
  IEC512I I/O ERR IEC022I 137-18 TAPE ERRORS FOR DASD DEVICE
    The following errors are received processing a data set
  concatenation that resides on a dasd unit.
  IEC512I I/O ERR dddd,volser,,jobname,stepname,dsname
  IEC502E K dddd,volser,,jobname,stepname,dsname
  IEC022I
  137-18,IFG0554F,jobname,stepname,ddname-0002,dddd,,dsname
  
  The ABEND137 rc18 which is only issued for data sets residing on
  tape media was being issued for a dasd device.
  The problem was caused by a USERMOD in IFG0194E from CA CA-DISK
  not being applied correctly.
  ----------------------------------------------------------------
  #17
  A DB2 bind job with a PDSE in the JCL on ISPLLIB and STEPLIB
  results in an S0F4 RC24 RSN13040405 from IGWLHRLS followed
  by an ABEND614 RC14.
  
  Removal of the PDSE from ISPLLIB allows the job to run OK.
  
  SYSTEM COMPLETION CODE=0F4  REASON CODE=00000024
   GR 0 has the reason code 13040405
  IEC214I 614-14,IGG0201Y,jjj,sss, ddname ,dev ,ser ,dsname
  
  The S0F4 RC24 RSN13040405 indicates a CLM_INVALID_LOCK_TOKEN
  error detected by the PDSE CLM Hierarchical Lock Service .
  
  The S614 RC14 indicates a CLOSE macro instruction detected
  an error return code from an SMS service while processing a
  PDSE data set.
  
  ISV: CA-PMO (Computer Associates Program Managment Optimizer)
  Product: Runtime Performance Optimizer
  Release :  Rel 4.3 SP7
  Fix Identifier: T5QV051
  
  ISV description of the problem
  
  Short description:  MESSAGES - PMO638I KEEPS REPEATING
  Description: "PMO638I - PDSE directory bypassed. DSN=library
  name" followed by message: "PMO615I - UNABLE TO CONSTRUCT
  HASH TABLE FOR DSN=library name" is being displayed
  periodically for a PDSE library, even though no INCLPRVT
  commands are issued to include that library for PMO management.
  The problem is caused by PMO incorrectly identifying a
  PDSE library as being a PDS.
  ----------------------------------------------------------------
  #18
  MSGIOS051i Channel detected errors received on input data sets
  residing on virtual tape (OEM).  The resulting output data set
  contains additional records.
  Observation is that a number of channel detected errors occur,
  and the hardware then sometimes will jump back a few blocks and
  reread the records again, causing incorrect records to be writ-
  ten to the output data set.
  CCW trace shows that the hardware presented us with a block that
  had been previously read (6 READs prior), while the block that
  should have been physically read from the tape was never presen-
  ted to the host.
  Oracle/STK determined this was a microcode problem and is fixed
  with D02.14.xx.00 with a  GA date of 7/26/2011.
  

Local fix

• #19
  IGD306I UNEXPECTED ERROR DURING IGDCNS01 PROCESSING
  RETURN CODE 5002 REASON CODE 0
  
  FDR user may experience IGD306I 5002 because of the way ABR
  works.  If the program name is IEFBR14 or IEHPROGM, and the DD
  statement specifies DISP=(OLD,DELETE) or DISP=(OLD,UNCATLG) or
  DISP=(MOD,DELETE) or DISP= (MOD,UNCATLG) or DISP=(SHR,DELETE) or
  DISP=(SHR,UNCATLG), then the ABR CATALOG LOCATE exit FDR026DU
  will not recall the data set, but will just uncatalog it from
  auto recall.  This is inhibited by setting SYSTEM
  IEFBR14_DELMIGDS(NORECALL), this will need to change to LEGACY
  or the ABR exits are not called.
  #20
  abend913 rcFC0004BC issued from ACF9096V after applying
  OA49520. Error occurs when running DFSMSDSS logical full
  volume dump.  Also will receive msgadr724E and msgadr717e.
  CA fixes are:
  TR95459 - R16.0
  TR95466 - R15.0
  ----------------------------------------------------------------
  #21
   The client change from using DTS (ACC,SRS - DIF) to CA Allocate
  and
  now gets the 044E0097 (space exceeds 65535 tracks).
    CA has provided the client the following mod....
  .
  From:
  "ALLOC DSN('"acifile"') DDNAME(SORTOUT) NEW SPACE(12288)"
  .
  To:
  ALLOC DSN('RE9709A.ALLOC4') DDNAME(SORTOUT) NEW SPACE(12288)
  TRACKS
  LRECL(32756) BLOCK(32760) RECFM(V,B)
  .
    The DATACLAS happened to contain...
  Recfm  . . . . . . . . . :
  Lrecl  . . . . . . . . . :
  Override Space . . . . . : NO
  Space Avgrec . . . . . . : M
        Avg Value  . . . . : 1
        Primary  . . . . . : 40
        Secondary  . . . . : 40
        Directory  . . . . :
  .
    I believe the 'M' above is what triggered this.
  .
    That case number from CA is 01005323
  .
  --------------------------------------------------------
  

Problem summary

Problem conclusion

Temporary fix

Comments

• n/a
  

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