IBM Support

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

Subscribe

You can track all active APARs for this component.

 

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, and PDSE.  Where possible, OEM fix
    numbers are listed.  It is by no means a complete list.
    .
    DADSM OBTAIN FAIL WITH RC08 WHEN RUNNING SYNCSORT JOBS
      FDR's FASTCPK product is moving the data set and changing the
      data set name in the DSCB resulting in RC8 from DADSM OBTAIN
      indicating the data set can't be found. FDR fix is P-52.0589.
      In addition, OY59989 and OY62287 should also be on.
                                              QP 10/14/94
    .
    SMF Type 14 record field SMFIOREQ incorrect.
     Processing SMF type 14 records (SMF14 type14 SMFtype14) to
     report on hiperbatch activity resulted in invalid data
     recorded in the SMFIOREQ field.  Problem was with MSX code
     (MXG).  Official fix # was not available when problem record
     closed.  Please contact MSX directly for fix.
    .
    ACL (automatic cart loader) wasn't working after upgrade from
    1.1 to 1.2.  CA-1 TMS allows the ACL to be disabled if scratch
    pools are used.
                                   DES 11/08/94  (updated 11/11/94)
    .
    Various abends during execution when module copied using SAS
    The blocksize is also changed during the copy.  If an AMBLIST
    is run against the module message AMB103I RLD POINTER INVALID
    is issued.  An ADCON has been corrupted during the copy.
    SAS
    RE-LINK OBJECT MODULE - MSA 11/09/94
    .
    ABEND837 RC08 reading an NL tape.  The abend occurs because
    EOV is attempting to find a volser of zeroes in the JFCBVOLS
    and then the JFCBX and there is no JFCB extention.  This occurs
    because CA hooks in OPEN (specifically IFG0194K) bypass the
    initialization of the volsers that are eventually used during
    EOV. This only occurs on DFSMS 120 when IFG0194K is at UW11124.
    The revised CA TLMS zap for IFG0194K is H94A8B2.
                                              JBV 11/02/94
    .
    ABEND0C4 RC10 in IFG0202J at +'568' when running ICEGENER
    job. Failing instruction is 'D703F008F008'.  Reg 15 should
    contain the address of the DCBE and it does not.  It is
    overlaid by PDSMPSR (PDSMAN) software.  The fix number
    is '71268' from Legent. Customer is running DFSMS 1.2.0.
    If the customer is running DFSMS 1.2.0. and PDSMAN 7.2.,
    the fix number is 72137. (added 5/30/95 BR)
                                             JBV 11/04/94
    .
    Abend0f4 occurred in IGWFVSBK +'566' (HDZ11B0) with rsn25110023
    because the pool token passed to IGWFVSBK does not point to the
    start of the IGWFVPH pool header.  The pool token contains an
    FVPH address of 7FFCF000 but the FVPH begins at 7FFCEFFC.  An
    FVPH should start on a page boundary so the FVPH address in the
    pool token is correct.  The problem is the FVPH at 7FFCF000 for
    '18' bytes was moved to 7FFCF000 minus 4 or 7FFCEFFC.  The
    error was detected when VSM end-of-job cleanup rtn IGWFVEOJ
    called IGWFVCOM for the terminating batch initiator job to
    compress all local FVPH pools and IGWFVCOM called rtn IGWFVSBK
    to get the next FVPH pool ptr.
    *  Problem resolved by Thruput Manager apar TR41027
       from MVS Solutions.
                                                  ( MW - 11/14/94 )
    .
    IEC331I 042-006(04180040) IEC999I IFG0TC0A,IFG0TC0B
      User job abended after apparently failing to scratch a dataset
      This is followed by an ABENDC03.  The problem was with HPS
      systems and SEER Technologies fix number is 38244.
    .
    An uninitialized MEDIA2 cartridge mounted on a D/T3490E in an
    ATL is rejected during OPEN for output to FILE1 instead of
    being relabeled.  Messages are:
    65E,08,NCA,02,0600,,,**,,JOBNAME,
    .0049242E000000200000(30CE000000000000)00E9
    IEC512I I/O ERROR
    IEC502E R
    (MSGIOS000I, MSGIEC512I, MSGIEC502E) This is the same problem
    as OW04762 but is also fixed by CA1's zap H9408H2 which is for
    TLMS Vers 5.3.
                                      JBV 94/11/14
    VTOC OVERLAY
     Job that last ran prior to the vtoc getting overlayed was using
     oem product VSAM ASSIST 6.3, which did not have support for the
     3390-9 dasd.  The problem did not reoccur after going to
     VSAM ASSIST version 6 release 4.
    .
    ABEND637-7C - CA1 TMS replied 'M' to WTOR IEC507D
    for a private volume in an automatic tape library
    dataserver.  This is resolved by applying CA1 fix
    number 609.
                                        SH   01/10/95
    .
    ABEND0C4 IN IGC0006D
    During SVC64 (RDJFCB) processing, an ABEND0C4
    in IGC0006D can occur because an invalid exit
    parameter list was passed.  The last entry
    indicator in the JFCB exit list was not on.
    SYNCSORT Early Warning fix number 45790 may
    resolve this problem.
                            SH  01/16/94
    ABEND0C4 PIC4 IFG019RA during OEM SYNCSORT MAXSORT
      Problem was caused by an apply error of fix F170407 from
      Legent's ASTEX (MVS Dasd monitoring product).  The problem
      was resolved when the fix was re-applied correctly.
                                                      QP 1/17/95
    .
    AUTORECALL failing w/ MSGARC1181I but may complete
    successfully later on. MIGRATE was running while data set
    was being RECALLed.  SYSZVOLS was not being deq'd at demount
    on the MIGRATE, (EVR=Early volume release)
    This problem occurs running CA1 TMS Version 5.1 and DFSMS 1.2.
    IFG0194F sets up the UCBDSDSP (dequeue at demount bit @ +2B)
    based on the JFCDQDSP bit being on (C0).  CA1 gets control
    from IFG0194F and the comparison of these bits does not occur
    correctly in CA1.  The UCBDQDSP bit gets zeroed out and the
    volume is not dequeued at EOV time but is dequeue when the
    data set is closed.  This problem can also occur for other jobs
    that use EVR and CA1 TMS Version 5.1  Fix number is T5XD479.
    
    Additional symptoms to this:
    MIM1038 OED092   CONTENTION WITH DBD1MSTR OWNS EXCL  ON SYSX
    MIM1039 OED092   NEEDS EXCL SYSZVOLS VOLSER NUMBER
    IEF690I FOLLOWING VOLUMES UNAVAILABLE TO JOBNAME
    IEF690I VOLSER NUMBER
    The volser in question was previously demounted during a DB2
    job. Please contact CA for current fix number. (db2info MSTR)
                                 JBV 1/15/95  (updated 5/3/95)
    .
    ABEND282-20 in IFG0194F.  Problem occurs when operator fails
    to enter a comma in response to TLMS message CAT9702P.
    This causes UCBVOLI to contain a blank + the text entered by
    the operator, which in turn causes the ABEND282-20 if TAPEVOL
    is active.  Although this appears to be similar to OY63583,
    CA has closed the item as a user error.
                                               RL 95/01/31
    .
    ABEND0C4 in IFG0202I + x'4F0' when running FAVER (Legent)
    and POOLDASD (Empact). Problem corrected with Empact
    fix # X3735P71.
                                               RL 95/01/27
    .
    blocksize.  After exec is run, blocksize is larger than what
    was specified on the ALLOCATE command.  Customer was using
    ULTIMIZER which dynamically changes the blocksize specified
    on DD statements to achieve the optimal blocksize for the
    device. ULTIMIZER was being invoked and not logging a message
    that the blocksize had been changed when the exec was run.
                                              JBV 85/02/02
    .
    ABEND0C1 IN IFG0RR0A WHEN MOD'ING RMF DATA ONTO EREP
    HISTORY FILE.  ABEND WAS IN OEM CODE, CA TLMS PROVIDED
    FIX #H94A2G2.  PLEASE CONTACT CA FOR MOST CURRENT FIX
    NUMBER.                          95/02/07 BR
    .
    ABEND0C4 IFG0200V
      0C4-10 in IFG0200V + x'260' on load instr 58F0 F034 when
      accessing AMB pointer but reg15 storage was not available.
      IFG0TC0A attempted to close the remaining data set, but the
      ACB storage had been freed or reused.  Legent Endeavor
      fix # C9225001 resolved problem for release 3.6.
      (Fix is in the base of release 3.7)
    .
    Customer using TOP SECRET, brings up an image without the
    product and gets ABEND913 RC3C on NON-RACF defined data set.
    For TOPSECRET, customer still needed to have 2 modules in the
    LPALIB (ICHSEC00 & ICHSEC05) and also needed to include the
    TOP SECRET LOADLIB in the LNKLST concatenation.  After these
    things were done, problem resolved.
                                                JBV 95/02/13
    .
     OVERLAPPING EXTENTS
       OEM product System Recovery System from vendor ORWI caused
       overlapping extent condition.  Fix is available.
       msgIEC604I DIRF msgIEC602I msgIGD17040I RC148 D=043D0000
                                              MHM 03/02/95
    MSGIEC151I ABENDA13-10 copying multiple files to tape
       The ABENDA13 RC10 occurred when copying multiple files to
    tape using UNIT=AFF=DDNAME and VOL=REF=*.DDNAME.  The problem
    started occurring after upgrading from CA TLMS 5.3 to
    CA TLMS 5.4.  The problem was caused by a bad TLMS 'L2' hook
    in IFG0196N.
                                      QP 03/13/95
    .
    NO SMF15 TYPE15 RECORDS PRODUCED FOR OUTPUT
      SMF type 15 records were not being written out for data sets
      closed for output.  A job scheduling system ZEKE from ALTAI
      was dymanically adding its own copy of the IEFU83 exit at
      start up.  The exit contained an option to allow the SMF type
      15 records to be written out but U83SUPP=N was not being
      specified, causing the records to be be suppressed.
                                      QP 03/27/95
    .
    ABEND878 RC08 in COMMTASK rtn because SQA (below the line)
    SP245 overflowed into CSA (below) and forced customer to IPL.
    This was added to DFP OEM BUGS because the 878 can occur
    anywhere & PDSEs use Media Manager that also uses SP245 storage.
    Most of the storage contained DSNAMEs and some areas contained
    DSNAMEs with CATALOG names immediately following the DSNAME.
    RMF report showed the size of available SQA below the line
    was 61K FREE at 8:00AM, 47K FREE at 8:45AM, 0K FREE 9:00AM.
    The syslog indicated msgMIM0350 "SYSTEM SY1 HAS NOT RESPONDED
    TO CTC COMMUNICATIONS" occurred 82 times between 8:58am
    and 9:31am and the 878 dump occurred at 9:36am.
    At 9:03 get msgMIM0331 "SYSTEM SY2 -CTC INITIALIZATION PENDING".
    The storage area looks like catalog info returned to the user &
    it is not storage for VSAM catalog data because format is wrong.
    OEM Legent said this is a MIM problem of not freeing storage
    allocating DQ processing and the circumvention is to issue
    the free command.  Legent incident number is FDN001.
                                      MW  4/3/95
    DIRF bit turned on.
      OEM product INFOPAC - RDS by MOBIUS MANAGEMENT may turn on
    the DIRF bit and  not turn it off on Indexed VTOC.
    PTF is ERSRDIRF. MHM 04/24/95  (QP updated 04/28/95)
    .
    Unable to allocate hfs data set using IEFBR14.  This results in
    the following abend and messages:
    ABEND0F4 RC24 RSN010257DC during IEFBR14 for HFS data set and
    IGD17040I ERROR IN DADSM PROCESSING FOR DATA SET XXX.XXX
    HISTORIC RETURN CODE IS 200 DIAGNOSTIC INFORMATION IS 044D57DCn
    IGD306I UNEXPECTED ERROR DURING IGGDAC02 PROCESSING
    RETURN CODE 4 REASON CODE 220
      ( msgIGD17040I rc220 rsn044D57DC rc044D57DC msgIGD306I rc4 )
       This can be caused by the security product not running, not
    installed, or the product's version does not yet support HFS.
    RACF V2R1 or an equivalent, must be used.  If using ACF2,
    please contact them for assistance.  The required use of such a
    product is documented in OS/390 OpenEdition:  Planning, under
    PREFACE, and several chapters, including chapter 4. that
    discusses HFS access.
    Please contact correct product owner for assist.   LAP 98/06/02
    .
    ABEND0C1 ABEND0C4 ABEND0C6 IFG0196X IGC0001I
      Branch to middle of instruction 41DD 0002 caused an 0C1
      abend when attempting to execute invalid opcode 0002.
      Prior to the abend, there was a RACINIT issued with an
      invalid parmlist.  The problem was caused by ORACLE.
      Fix is G4DB2245.                                  QP 04/14/95
    .
    ABEND0C4 PIC11 IFG0194E STRIPED DATASETS
      Abend 0C4 was actually in a DMS SVC 244 usermod IGC0024D
      during the open of a striped data set.  Customer was running
      with DMS Release 8.1 which does not support striped data sets.
                                      MHM/QP 04/25/95
    .
    IEC507D ISSUED FOR SCRATCH TAPES DURING DFHSM MIGRATION
      The scratch tapes had expiration dates > than the current
      date so the IEC507D messages are being issued validly.
      However, in CA-1 5.0 the tape processing hooks were hard coded
      so the MSGIEC507D messages were handled "under the covers" and
      never displayed.  In CA-1 5.1, the dynamic hooks are not hard
      coded so the messages are displayed which is WAD per CA.
      This also applies to non-scratch tapes.
    .
    IFG0194A TMAPI0100 OSIB DCB OR DCB WORKAREA WAS NOT FOUND
      DFSORT job receives MSGTMAPI0100 followed by an ABENDU0888
      (user abend 888) in CA1 TMS module.  Contact OEM vendor
      Computer Associate for current fixes  GO43967 and GO43990.
      Also refer to ASKQ item CZJXH
                                      QP 05/22/95
    .
    WAIT OUT OF IFG019RA
      Following IECTMS60 message TAPE APPROVED FOR DENSITY CHANGE
      for an output tape, there is a wait out of IFG019RA for WTOR
      tape processing.  The problem is caused by CA.  The HIPER
      fixes are T5XD479 (apar GO67173) and T5XD494 (apar GO67179).
                                      QP 05/24/95
    .
    Occasionally IEC704A WTOR message is not issued when relabeling
    a 36trk tape on an 18trk device.  The problem was in
    AF/Operator V225, fix number QAB0453.
                                       JBV 05/25/95
    .
    IEW2711S D80A UNABLE TO POSITION TO MEMBER mmm FOR DDNAME ddn
    CONCATENATION NUMBER 1.  FIND MACRO ISSUED RETURN CODE 70064.
    was issued when using ISPF 4.1 Option 3.3 to copy a PDS member
    to a PDSE. Third party product, TRX, front ended NOTE/POINT
    (FIND) macro.  MSGIEW2711S MSGIGW01207E     LJY 5/30/95
    .
    ABEND0C4 PIC10 ABENDC03 IDA0192A
      0C4 was in oem VIOPLUS module V$RCROUT and occurred when
      starting up an oem subsystem.  Fix # is SWAG017.200 for
      PERFORMANCE SOLUTION (VIOPLUS component) release 1.1.6.
                                      QP 06/20/95
    .
    MSGIOS000I CMD 63 DEFINE EXTENT ABEND314 RC04 IEC211I
      Backup jobs receive IOS000I CMD reject on a define extent
      followed by 314-04.  The problem was resolved by upgrading
      the microcode level from 3711k6 to 3714c3 providing the EMC
      4800 devices w/ the DPR Dynamic Path Reconnect feature.
                                      QP 10/31/95
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • close for Internet viewing
    

APAR Information

  • APAR number

    II08264

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1994-10-14

  • Closed date

    1997-11-07

  • Last modified date

    2003-06-13

  • 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

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
13 June 2003