II09608: OEM BUGS IN DFP DATA MANAGEMENT - O/C/EOV, ACCESS METHODS, PDSE,LINKEDIT, BINDER (ALSO II07757 II07438 II08212 II08264 II08762)

APAR status

• Closed as canceled.

Error description

• See also II08212 II07438 II07757 II08264 II08762 II09608 II10937
  .
  This info APAR lists known third-party (OEM) problems in DFP
  data management components: non-VSAM o/c/eov, sequential access
  methods, linkage editor, CMM, PDSE and HFS.  Where possible,
  OEM fix numbers are listed.  It is by no means a complete list.
  .
  ABEND413 RC04 on Dasd data set using ProSMS
    Problem occurs for nonspecific allocations w/ a unit coded in
    the format UNIT=(unit,x), where x is equal to the number of
    STORAGE volumes.  Doesn't fail with x-1 units.  Abend is
    caused by JFCBVOLS containing incorrect volsers.  Problem was
    resolved by fix PR351P46 for ProSMS release 3.5.1 and is only
    applicable for DASD allocations.
  .
  IEC026I 637-54,IFG0554J....
  IEE763I NAME= CBRLLACS CODE= 1C01A1
  CBR4000I LACS MOUNT abnormal termination for drive 09D5.
  CBR4161I System completion code 0C8, reason code 0008.
  IEE764I END OF IEC026I    RELATED MESSAGES
  ABEND0C8 actually occurs in CONTROL T tape management code
  after WTO from CBRLLACS.  This only occurs on DFSMS130 during
  EOV. See CONTROL T for the fix number.
  MSGIEC026I ABEND637 RC54 MSGCBR4161I            JBV 96/08/14
  .
  ABEND013 RCA4 opening subsystem concatenated PDS data sets.
  SUBSYS=LAM coded for each DD in the concatenation on DFSMS130.
  CA LAM gave customer fix G097070.  Please contact CA to verify
  fix number and release info.           JBV 96/08/16
  .
  ABEND0C4 ICVDMC02 INVOKING CVAF CVAFDSM
    StorageGuard fix SG231P45 for releases 2.3.1 and 2.3.4
  .
  IEC999I IFG0RR0A ABEND0C1 IFG0194A
    ABEND0C1 occurs in IFG0194A because psw is pointing into the
    middle of a DMABCOND define constant.  The abend occurs after
    a return from an SVC E2 from ACF9E9RA which has a hook in to
    IFG019RA.  Problem is resolved by ACF2 fix G092701 .
  .
  ABEND9C7 IN COMPUTER ASSOCIATES (CA) ACF2 SECURITY PACKAGE IN
  MODULE ACF9C000.
    RACROUTE function detected an incorrect token.  Error fixed
    by CA's apar GO71731.
  .
  IEC026I ABEND637 RC78 WHEN EXPIRED SCRATCH TAPES ARE REJECTED
    IEF233A, MSGIECTMS6, MSGIECTMS3 NOT SCRATCH 32 are received .
    Display of the volume status indicated NOERROR for the tapes
    that were expired, hence OAM continued to select the tapes for
    processing. ABEND637 is received after retry counter has been
    exceeded. CA was detecting they are not scratch and placed
    them in abend status, but did not update the date.  Resolved
    by CA R5.1 usermod T5XD515 which requires prereq GO85435 .
  .
  ABEND0C4 IFG019RA CORRUPTED OVERLAYED VOLSER
    Abend was caused by an overlay of the volser in the UCB.
    In some cases the volser changed on an online active volume.
    STOPX37 ( PROSMS ) fix SX357P07
  .
  ABEND106 RC0F RSN40 MSGIEW4005I RC 0F REASON 40
  This ABEND106 can occur even if the job steplibs to the program
  library. The PDS2TTRT (program directory entry + x'c') does not
  point to the first text record. Use IEHLIST LISTPDS output to
  verify. The REL ADDR-HEX to 1ST TXT should point to first text.
  .
  IGWDBPAR detected  TCB->TCBJSTCB->TCBSTCB->STCBSTCB ﾪ= "STCB"
  acronym and set reason code rsn1DF3F034 to indicate bad STCB ptr
  and IGWDBPAR reset the reason code to rsn1DF34E55 because
  an error was detected during get ARA  IGWFTOKM token extract
  and then parser rtn IGWDBPAR issued ABEND0F4 w/ rsn1DF34E55.
  The secondary TCB (STCB) appears to be overlayed with '20' bytes
  that match the ACF2  Userid, Permission and Groupid assigned
  to the RLOGIN user. (reference pmr# 4415X,660,706)
  Overlay does not occur after increasing real storage from 42 meg
  to 64 meg, therefore, storage constraint triggers overlay.
  **********
  (STCB +0 overlay for '20' bytes)
                        00000000   00000001  | .       ........
  00000002   00000014   000000CD   000000FF  | ................
  000001F4   000003E7                        | ...4...X".......
  (ACF2 starting at '055B6588')
                        47F0F0A4   7FC1C3C6  | .       .00u"ACF
  C3C3C4C9   C5406040   F0F761F2   F261F9F3  | CCDIE - 07/22/93
  40F1F74B   F1F34040   60404040   40C1C3C6  |  17.13  -    ACF
  F2404040   4040D9C5   D340F64B   F1404040  | 2     REL 6.1
  (ACF2 Userid, Permission, Groupid assigned to RLOGIN
   starting at '055B6660')
  C3C1E2C1   C6C7C9C4   055B6678   055B66FC  | CASAFGID.$...$..
  0000000C   055B66FC   00000000   E2E8E2F1  | .....$......SYS1
  40404040   00000001   D6D4E5E2   C7D9D740  |     ....OMVSGRP
  00000002   E3E3E840   40404040   00000014  | ....TTY     ....
  E2E8E2D7   D9D6C740   00000015   C5E7D7D3  | SYSPROG ....EXPL
  D6C9E340   00000016   E2C5C3E4   D9C9E3C5  | OIT ....SECURITE
  00000017   D9C5E2C5   C1E44040   00000018  | ....RESEAU  ....
  D7E4D7C9   E3D9C540   000000CD   C9D4E6C5  | PUPITRE ....IMWE
  C2404040   000000FF   E2D7C5C3   C9C1D340  | B   ....SPECIAL
  000001F4   C5D4D7D3   D6E8C5C5   000003E7  | ...4EMPLOYEE...X
  **********
  OW22529 symptoms also reported by same customer (3054X,660,706):
  When HFS updated via rlogin from single system (HFS not shared),
  get msgBPXF020I FILE SYSTEM MAY BE DAMAGED RCA2 RSN5B1500AD.
  Get multiple 0F4 abends intermittently after msgBPXF020I.
  After reIPL, OMVS initialized ok after 3 trys.
  The 0F4 error occurred when IGWFHENT was called to find an entry
  in the FIB hash table at 7F1C80F0 (hash table body at 7F743B50)
  but IGWFHENT detected an invalid table entry type ( HTB_TYPE )
  of '03' that represents a table entry pointing to a hash table
  extension (HTBX) used when the number of collisions exceeds the
  capacity of the hash table list.  Also  HTB_DELETE_OCCURRED
  indicates a delete has occurred in the FIB hash table.
  Each valid table entry w/ HTB_TYPE = '01' all point
  to allocated IGWFIB control blocks.
  The invalid table entry type ( HTB_TYPE = '03' ) does
  point to a valid HTBX at 7EFB5000 but IGWFHENT does not expect
  this table entry type and results in 0F4 w/ rsn0A02202C.
  This is followed by 0F4 (no dump) in disconnect HFS rtn
  IGWDHDSH +13A0 with rc8 and rsn0a080004 that means hash table
  cleanup rtn IGWFHEN2 could not find block during find/delete.
  Then get 0F4 (no dump) in IGWFHEN2 +163E with rsn0a082024
  because IGWFHEN2 could not latch user block.
  **********
  HFS accessed via RLOGIN from AIX RS/6000 connected
  from OS2 using TELNET and get "GETPWNAM: ROOT: NO SUCH USER"
  and msgBPXF020I FILE SYSTEM MAY BE DAMAGED w/ rcA2 rsn5B1500AD.
  After RLOGIN and entering "password", get
   rlogind: exexlp to rlogind2 error: EDC5162I The Physical File
            encountered a system error. rsn=581500AD
  The problem NEVER occurs if HFS accessed via TSO OMVS.
  After HFS adapter GFUGLOOK lookup error rsn5B1500AD,
  can not do RLOGIN anymore and when taking down OMVS get:
   DUMP TITLE=COMPON=DFP C/A,COMPID=5695DF102,ISSUER= IGWCDEXT ,
              DRTR INVOKE EXIT,RET=00000024, RSN27120406
   CSV031I LIBRARY SEARCH FAILED FOR MODULE ITTCTSER  RC24
   REASON CODE 27120406, DDNAME * LNKLST *
   CSV028I ABEND806 RC2C  JOBNAME=OMVS      STEPNAME=OMVS
   IEF450I OMVS OMVS - ABEND=S806 U0000 REASON=0000002C 882
  (reference pmr# 8188X,170,846)
  **********
  Above problems were resolved after installing ACF2 fixes:
    LO00006 LO03790 LO03889
  **********                             ( MW - 10/24/96 )
  .
  **************************************
  ABEND0F4 CSECT=IGWLHRLS+1926 RC=00000024,RSN=13040405
  OEM product PMO fixes QJ42066 and QJ42068 solves problem.
  *********                 DW  11/12/96
  .
  ABEND0C4 IGWAMES0 PDSMAN intercepts STOW
  IEBCOPY issues STOW. It is intercepted by PDSMAN who
  gets ABEND0C4. RIDS data shows IGWAMES0. Product
  CA-PDSMAN fix ID is: FIX72437.
  .
  iec999i ifg055a ifg0rr0a abend0c4 pic10
    Error occurs on cobol program reading concatenated tapes.
    PSW of 0C4-10 was not in storage. Problem was in TMS product
    ZARA and resolved by X122A051.
  .
  JFCBELNM IS BLANKS INSTEAD OF GENERATION NUMBER FOR GDGs
    Using IEBCOPY PDSFAST to create gdg sms managed tape output
    datasets and redirecting them to disk by TMM results in the
    jfcbelnm field being blanks instead of +n, where n is the
    generation number.  The jfcbelnm field in the SWA JFCB was
    correct, but the jfcbelnm in the user's jfcb was blanks.
    The problem only occurs with PDSFAST, not regular IEBCOPY.
    PDSFAST V4.3 fixes are EWF1710 and EWF1724 .
  **************
  DUMP TITLE=COMPID=DF115,CSECT=IGWBIEX1+09D4,DATE=07/15/95,MAINT
             ID=NONE    ,ABND=0F4,RC=00000018,RSN=150BC008
  These and other broken PDSE Datasets reason codes can result
  using OEM SW product RTD (Real Time Defrag). INTERCHIP RTD is
  a product from Germany and currently (as of 2/9/25) doesn't
  issue IGWNOTIF macro before starting the RTD DEFRAG. Make sure
  IGWNOTIF is incorporated in RTD if you use it.
  .
  Following sequence of messages are received when creating NL
  tape on 3480 drive :
  IEF233A M 0202,IMSCAR,,TSYDSR1A,STEP0700
  IOS000I 0202,0A,NCA,02,0600,,**,,TSYDSR1A
   0049242E000000200200(7161716100000000)0070(00000000)C78F3473004
  IEC512I LBL ERR 0202,      ,NL,IMSCAR,NL,TSYDSR1A,STEP0700
  IOS000I 0202,0A,NCA,37,2600,,**,,TSYDSR1A
   0049242E000000200200(7161716100000000)0070(00000000)C78F3473004
  IEC999I OMODVOCA,TSYDSR1A,STEP0700
  .
  ABEND0C4 was in CA-1 module TMS0MODV which is in the OMODVOCA
  loadmodule.  This was resolved with two usermods supplied by
  CA-1 for release 5.1 : TEBC015 and T5XD619
  .
  Writing to a D/T3590 MAGSTAR tape within a D/T4394 atl using
  CA (CA1 Rel. 5.1) may result in data being overwritten.
  After a tape is labeled and written on, the status in TCDB shows
  'Private' with a correct Storage Group. However, CA TMS still
  thinks that the tape is in 'Scratch' status.  As a result, after
  the tape is ejected out of the library and reinserted , TCDB now
  shows the status as SCRATCH, which can cause data to be
  overwritten. A tape written outside the Library (D/T3480) is
  correctly passed to CA1 with a status of 'Private' known to TMS.
  CA1 Release 5.1 does NOT support D/T3590 in a library.
  CA1 Release 5.2 must be installed for Magstar support.
  The following CA maintenance for Release 5.1 or Release 5.2
  (if D/T3590 Magstar), is required in order to operate a
  3494 ATL in Hard Partioning Mode (two TCDB's) with Tape
  Management System from CA (CA-1) :
  TE9C067 - invalid Return Code in Exit CBRUXENT
  T5XD672 - message IGFTMS1 UCBLOOK FAILED FOR RC=0004 RSN=A610
  L012085 - Abend0C4 in ARCDMSUV
  TEBC015 - message IEC999I  Abend0C4 in OMODVOCA
  TX5D619         "
  ................................................................
  ABEND0C4 in IFG0202I + x'588' on instruction D501 A004 E004
  .
  When testing the TCTTIOT for the correct UCB entry by
  comparing the UCBCHAN fields, an 0C4 can occur in IFG0202I
  if the two UCBCHAN fields are different.  The abend can
  occur after StopX37 or ProSMS performs a volume switch to
  a different device and any of the following PTFs are applied:
       UW24286 - MVS 4.2.0 (PUT 9602)
       UW24287 - MVS 4.3.0 (PUT 9602)
       UW24288 - MVS 5.1.0 (PUT 9602)
       UW24289 - MVS 5.2.0 (PUT 9602)
       UW24291 - MVS 5.2.2 (PUT 9602)
       UW24290 - MVS 6.0.1 (PUT 9602)
  Please contact Boole & Babbage for possible coexistant fixes
  if running StopX37 - Releases 3.5.5, 3.5.6, 3.5.7, or 3.5.8
          or ProSMS  - Release  3.4.2
  Subsequent releases of these products do NOT require the
  application of ANY Boole & Babbage service to coexist with
  the above listed IBM PTFs.
  .
  IEC141I 013-34 ABEND013 RC34 IGG0191I REPRO TAPE GDG DATA SET
    Problem was caused by CA-11 release 2.1
    Please contact CA-11 for fix information.
  .
  ABEND0C4 IGGDAU01
    0C4 is caused by PMO issuing a 2nd STOW in a key different
    than the one that was used by OPEN.  Legent provided fix
    QJ42070 for release 4.2.02.  Contact Legent for fix info.
  .
  IEC999I ABEND0C4 RUNNING GENER JOB FROM TAPE TO TAPE WITH CA-1
    Problem surfaces with CA-1 fix L015867 and is resolved by
    L016451 for release CA-1 release 5.2 .
  .
  ABEND0C4 CA ENDEAVOR
    Intermittent S0C4 occurs when extracting information from a
    history delta file on ISPF 4.3.  The problem does not occur
    w/ ISPF 4.2. The problem is caused when using a VOL(* * * * *)
    parameter in an IDCAMS vsam definition for the Master Control
    File.  Endeavor recommends that an explicit VOL parameter
    be used when reorganizing this file, and will document this
    in their database for SMS Endeavor customers.  Please contact
    CA Endeavor directly for information.
  .
  ABEND0F4 occurs in IGWMDSST +BC6 (uw33201) rtn WRITE_SMF_RECORD
  when looping thru the DSSB chain to build SMF type42 records
  using statistics contained in the DSSBs ( IGWDSSB ) and IGWMDSST
  found an invalid DSSB control block header and set rsn5A010008.
  The storage area where DSSBs reside is within contiguous
  storage pool cells in ELSQA DREF SP215.  Same problem occurs
  on other LPARs and common change was to MIM release 4.2.
  OEM MIM ( from Computer Associates ) report ( LI18938 ) error
  description says "various overlays and abends causing
  unpredictable results" and recommends MIM fix# LO18637.
                                                 ( MW - 6/25/97 )
  .
  Using BATCH LSR, security calls are not made and unauthorized
  access is being granted to production VSAM files.  Two products
  hook svc19 processing and bypass the security call.  The
  products SAR (new name-VIEW) and Express Delivery (new name-
  DELIVER) provided fixes for this problem.  How to find out
  who is hooking open: 1) Go to IPCS ACTIVE storage, 2) execute
  the following command: ip l cvt+c8?+84?+98?  len(256)
  This will display what modules get invoked for SVC 19
  processing and then contact that vendor.
                                           JBO 97/08/28
  .
  NL TAPES FOR NL MOUNT REQUESTS REJECTED WITH INVALID VOLSER
           IECTMS3O 059A, Y    ,IS NOT SCRTCH (08)
           IEC502E RK 59A, Y    ,NL, ...
  Problem resolved by CA1 fixes L017794 and/or L016985.
  Contact vendor for current fix information.
  . ( 10/15/97 - MW )
  During CMM (SMF TYPE42) connect IGWMCNDS, SSF environment setup
  IGWFARN0 gets 0C1 at offset +1076 (uw24999 ) because of a 7-byte
  overlay '00814450280000'x. Some pgm used an invalid ptr & moved
  data from low core PSA+4 IPLPSW into a 7-byte area within read
  only nucleus rtn IGWFARN0 +1076 that was loaded into ESQA sp239.
  After the overlay, start getting thousands of msgIGD306I
  because every data set close goes thru CMM to collect SMF data.
  The 0C1 overlay occurred at 16:44:47 and an 0C4 occurred in RACF
  at 16:44:04.  The RACF ACEE data in the 0C4 dump shows the same
  overlay with low core data moved from PSA +4 (RESTART NEW PSW).
  0C4 Title: ICHRST00-RACF SVCS,ABEND CODE=0C4-004,SVC=IRRRCK00,US
  0C1 Title: COMPID=DF115,CSECT=IGWFARN0+1078,DATE=01/18/96,MAINTI
  Recommend CA Endevor (V3R7M2) PTFs to fix CA overlay of ACEE
  P0000820 P0000829 P0000954 P0000991 P0001054 P0001223 P0001364
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• DM infoapar
  

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