II10937: OEM BUGS IN DFP DATA MANAGEMENT - O/C/EOV, ACCESS METHODS, PDSE,LINKEDIT, BINDER

APAR status

• INTRAN

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.
  .
  DUMP TITLE IEC999I IFG0RR0A IGG0553A ABEND0C7
    Abend is OEM module SMM40012 from Boole and Babbage.
    Message IEC614I EXTEND FAILED - RC 000,
    DIAGNOSTIC INFORMATION IS (04034379) also received.
    Problem was resolved by oem fix PR352PB6.
    Please contact vendor for applicable release / fix information
  .
  71E StorageGUARD I/O ERROR DURING LSPACE FOR volume ON dddd
  (RC=40 RSN=00000BAD) - VOLUME SKIPPED  RC40 RSN 00000BAD
  LSPACE only issues return codes 0, 4, 8, C, 10
  Problem is resolved in release 2.5.1 (put lvl 2) of
  vendor pool monitor StorageGuard
  .
  Abends in catalog address space
    ABEND0C4 in IGWMDSST due to invalid DSSB pointer.
    DUMP TITLE=COMPID=DF104,CSECT=IGWMDSST+0C94 ......
               ABND=0F4,RC=00000024,RSN=5A010008 RSN5A010008
    MIM was causing the DSSB cell pool to be overlaid.
    CA provided fix TD42021 for Version 4.2 of MIM.
    Also refer to II10619 for reference on MIM fix.
  .
  IEC028I ABEND837 RC08 EXTEND TO SCRATCH VOL AFTER OPEN INOUT
    IFG0552B should be the module to receive control for output
    tape processing.  However, the dump shows the eov tape
    output module id ( EOVOUTID ) in the workarea was not set
    up with IFG0552B, but instead contained CA module IFG019CA.
    This problem was resolved by CA usermods at relese 5.1
    (See II08762).  The fixes should have been rolled into the
    CA base release 5.2 but only half were included, thus the
    problem existed at CA 5.2.  CA provided APAR fix T5Q4127 .
  (Additional symptom : IEC030I B37-04,IFG0554T on 3590 output)
  .
  ABEND0C4 IFG0202K WITH OEM PRODUCT SYSBII FROM H&W
    ABEND 0C4 occurs in IFG0202K trying to use the AVT (Appendage
    vector table) in the DEBAPPB field at offset x'1D' in the DEB,
    to determine if the DEB is page fixed.  The AVT address is on
    the previous page which results in a PIC 11.  There should not
    be an AVT for a subsystem dataset.
    OEM vendor SYSBII from H&W provided zap 42011 .
  .
  ABEND0C1 IFGDEBCK + X'268' DUE TO STORAGE OVERLAY
    IFGDEBCK + x'268' should point to an LA instruction for the
    GETMAIN subpool and key : 412000FF 41300000 but instead shows
    00000000 C1300000.  The problem affects BMC's product Loadplus
    V4.1.0 and DB2 V5.1 .  It is resolved by BMC fix # 50663 .
  
  ----------------------------------------------------------------
  Incorrect Last Reference Date for Year 2000 ( Y2K )
    A dataset allocated with ispf opt3.2 or IEFBR14, results in
    an incorrect DS1REFD for Y2000.  The creation date is correct,
    but the year for the last reference date is off.
    For example, a last reference date of March 2,2000 ends up
    with a DS1REFD of 00003E instead of 64003E (100 years past
    1900, 62nd day).  This only occurs PRIOR to the dataset being
    opened.  Once the dataset is opened, OPEN processing correctly
    fills in the DS1REFD.  The DS1REFD was coming from a FMT1 DSCB
    that was being provided in the IEXFMT1 model dscb from FDR
    module FDRPRE00.  Problem was resolved by FDR zap 52.1264   .
  .
    If the problem is with the DS1REFD last reference date being
    incorrect AFTER open, and DMS is involved, there is a known
    problem with DMS and one of their apars PI#162841 which can
    cause the incorrect DS1REFD.  The problem is fixed by DMS
    ptf SS02927, which is sup'd by SS03283 & hits ADSMVS60 module.
  **If customer states SS03283 is already applied and still having
    the problem, make sure they check to ensure the SVC244 module
    is loaded correctly per the DMS install instructions. If it
    is not loaded per the instructions, a backlevel copy of the
    module is getting pulled in which is what causes the problem
    to persist.
  .
  TSO 'LISTDS datasetname LABEL' command will show the following
  format of the FMT1 DSCB ( 11 bytes on the right are omitted ) :
  .
  --FORMAT 1 DSCB--
  F1 C8E2D4F9F4F2 0001 64003E 000000 01 00 00 C9C2D4D6E2E5E2F24040
  64003E80801040 4000 90 00 1040 1040 00 0000 80 400022C7 09D702 B
  | ...79900001840000E 00000000000000000000 00000000000000000000 0
  |
  DS1REFD - March 1, 2000 (x'3E' = 62nd day of the year
                           x'64' = 100 years past year 1900 = 2000
  ----------------------------------------------------------------
  ABEND0C4 in IEC0SCR1 + x'3EE'
    The module currently in control is an OEM module SRVFIOS.
    The 0C4 is caused by a branch to IEC0SCR1, with REG1 not
    containing a UCB as expected.  IEC0SCR1 is a TRKCALC routine
    that should only receive control for dasd, but failing job
    was for tape.  Problem was resolved with STK ptf L1L006U for
    EXLM product for release 2.1.0.
  
  ****************************************************************
  IEC614I CREATE FAILED RC16 (x'10'), diag 04250057 or 04250067
          or 04250068 , dsname FDRABR.VvvvvvvZ
  Invalid Free Space or Lost Space following FDR SCRATCH.
  Without the SCRATCH parameter, the program is able to scratch
  a data set which is in use.
       This message is normal (not an error) on FDR/ABR ARCHIVE
  or SUPERSCRATCH when the SCRATCH (SCRATCH=IBM) option is not
  in effect, and on FDR full volume COPY or RESTORE to a
  different density.
       For ARCHIVE or SUPERSCRATCH, specifying SCRATCH or
  SCRATCH=IBM on the DUMP command will avoid the message.
  FDR/ABR ARCHIVE or SUPERSCRATCH is able to scratch a data set
  while it is in use if SCRATCH or SCRATCH=IBM is not specified.
  The best way to prevent this is to specify DSNENQ=USE,
  so the data set does not get selected.
       Also, following an FDR or ABR full-volume RESTORE or COPY
  of a volume with an indexed VTOC to an output device with a
  different density, it is the user's responsibility to rebuild
  the indexed VTOC with ICKDSF BUILDIX.
  .
  x'81' IN IEXDCC from POST processing on VSAM extend
  .
  Using Storage Guard Control from Boole and Babbage to extend
  VSAM files results in an x'81' IEXDCC out of the POST.
  From the DFSMSdfp Diagnosis Reference manual, an x'81' indicates
  a successful secondary allocation on the current volume for a
  VSAM data set, and and x'01' indicates the same for a non-VSAM
  data set.  Problem was solved by Boole and Babbage fix SC311P13
  .
  JOB HUNG IN MODULE IFG019RA + X'168'
    The label editor routines called IFG019RA to issue the WAIT.
  The XCTLTABL (xfer control table) in IFG0194K shows CA's
  OMODVOCA and EMODVOCA routines getting control.
  Upon return to IFG0193D, the WTG table should be set up with
  either IGG0190A if entered from OMOD or IGG0550P if from EMOD.
  Since this ins't what IFG0193D expects, it branches to the wait
  routine.  Problem is resolved by CA fix TF45081 / LO38103 .
  .
  Intermittent ABEND0C4 in module TRXMU using BINDER
    Abend occurs in TRXMU + x'1BA' because the storage key 5 is
    being accessed in key 8.  Abend is also sometimes preceeded
    by msgIEC131I.  Apply OEM fix # ZAP186 was provided from OES
    Inc. for their TRX product release 4.3 or install TRX rel 5.0.
  ****************************************************************
  ' CALL_SWA ENTERED ' MSG ISSUED USING CA-1 TMS
  .
  Messages seen in the joblog :
  TMS001  IEC501A M dddd,PRIVAT,SL,COMP,jobname,stepname,dsn
  IECTMS9 dddd,volser,jobname,stepname .....
  IEC705I TAPE ON dddd,volser,SL,COMP,jobname ....
  CALL_SWA ENTERED
  .
  The fixing PTF from Computer Associates Inc is :
  PRODUCT: CA-1-MVS Tape Management          RELEASE: 5.2
  APAR #: LO15867                            DATE: 11 APR 1997
  PROBLEM DESCRIPTION: S0C4-10 IN TMSTMVHS / WTO SWA CALLED .
  ** There is a follow on fix to LO15867 which is LO20115 and
  LO20126 and then an APAR of T5XD765.
  **comments added 11/09/98 by jbo.
  ________________________________________________________________
  ABEND0C4 in IGX00030+'106C' when MSGDISP issued by IFG0RR0A in
  TSO session using FLASHER by Tone Software.  Problem was caused
  by having UCBs defined as dynamic in Flasher.  Once the dynamic
  parameter was changed to "blank" or NON DYNAMIC, the problem
  did not recur.  A fix may also be available from vendor.
                                              jbo  10/08/98
  .
  ABEND177 WITH IMS RUNNING MVS ON NATIVE VM SYSTEM
    Testauth SVC 77 was issued from csect within loadmod IGC00020
    which according to an amblist, resolved to IFG020Z1 + x'224'.
    IFG020Z1 (alias for EDGXCLOS) is an RMM exit.
    RMM was not active.  Testauth actually was a hook from ACF2.
    ACF2 provided fix LO29827 which resolved the problem.
  .
  IEC999I IFG019CA and ABEND0C4
    ABEND0C4 occurs in CA module IFG019CA at offset x'276'.
    CA provided 3 fixes : T5XD742 T5XD743 T5XD744
  .
  IKJ56882I DATA SET NOT ALLOCATED, TOO MANY VOLUMES
  NUMBER OF VOLUMES SPECIFIED EXCEEDS LIMIT
     After allocation of SMS managed volume fails with IEC030I
     B37-04, attempts to delete the multivolume file fails with
     IKJ56882I.  The data set was allocated on 60 volumes
     eventhough the maximum volume count for a VSAM or SMS
     managed data set is 59.  VOLCNT was not specified in the JCL
     and nor Data Class.  If either had been used, either a JCL
     error would have been issued or via the ACS routines, SMS
     would still only allow the data set to be created on 59
     volumes and then issue message :
     IGD17271I ALLOCATION HAS BEEN ALLOWED TO PROCEED FOR DATA SET
     dsn ALTHOUGH VOLUME COUNT REQUIREMENTS COULD NOT BE MET
  .
     OEM product VAM ( SAMS : ALLOCATE ) was adding the volumes
     and performing incorrectly when he exceeds the SMS volume
     maximum.  VAM recommended that the 'latest version of the
     software be installed'.  This customer was currently at
     version 5.30 put 9826 when the problem was discovered.
  .
  DATA SETS ALLOCATED INCORRECTLY ON 4 DIGIT DEVICES WITH BMC
    The file is allocated via JCL as VB with the system
    determined blocksize, but ends up as VBA with the 1/2 track
    lrecl and blocksize.  Problem occurs when using IEBGENER to
    copy any 'PS' file where the output file name is in the BMC
    'registration table' to be compressed.  Problem occurs on
    BMC release 1.0.06 and was resolved by installing BMC V1.2
  .
  ABEND737 RC04 using PDSE or Compressed Data Sets
    IMS 6.1 users of compressed or striped data sets receive
    IEC027I 737-04 during EOV.  The volume listed in the IEC027I
    message is not the volume where the data set was being written
    to nor is it where the data set truly resides.  The problem is
    not limited to IMS 6.1 and can occur with any users attempting
    to extend a compressed or striped data set.  PROSMS by
    Boole and Babbage had a hook in EOV processing which was
    pointing EOV to the wrong volume.  When EOV attempted to read
    the FMT1 DSCB to determine if there was more space on the
    current volume, the FMT1 DSCB was not available so the 737-04
    occurred.  The fix by PROSMS is PR352PG8 .
  .
  ABEND0C4 WITH DUMP TITLE IEC999I IFG0RR0A RUNNING IMS 6.1
    Abend 0C4 was occurring in Computer Associates ACF2 module
    ACF9153X REL 6.2 .  The failing instruction is a TM 9120 9012
    approximately x'23E' within the module.  The psw at the time
    of error is in 31-bit mode but register 9 contains a valid
    24-bit address pointing to within ACF2, not a 31-bit address.
    CA ACF2 provided fix LO36931 which requires PRE LO36928 .
  .
  OBTAIN errors doing 'I' or 'S' in ISPF against HFS data set
    The HFS data set has unknown attributes and an OBTAIN return
    code of x'12' (rc12 rc12x) is received.  The RC12 is detected
    by Dadsm OBTAIN when a permanent I/O error or an invalid FMT1
    or FMT4 ( format-1 or format-4 ) was encountered when
    processing the volume, or when an unexpected CVAF error return
    error return code was encountered.  Problem was resolved by
    upgrading from FDR 5.2 to FDR 5.3 .
  .
  IEC026I ABEND637 RC08 concatenating extended format data set
     MSGIEC026I 637-08 received when an extended format dataset
     is concatenated behind a regular data set in the sortin.
     Problem is resolved with Syncsort ptf EW5157 ( SY51570 ) .
  .
  Mount for VTS tape called for outside the VTS
     BMC image copy is used to move DB2 logs from SILOs to VTS.
     Some data sets got created outside the VTS hence the mounts
     for them were called for outside the VTS.  The problem was
     with BMC for which fix number 205073 was provided.
  .
  ABEND0C4 PIC11 in IFG0196W at offset +x'220'
      During standard processing of an IMS region, processing
      fails with ABEND0C4.  BMC's DPISTATS module is sending parms
      to OPEN above the 16 MB line.  BMC fix is DataPacker/IMS
      2.4.3 zap/problem# 16623
  .
  IEC614I CREATE FAILED - RC192 DIAGNOSTIC INFORMATION 0403012C
    Using IAM by Innovation Software Products to create VSAM
    data sets results in an IEC614I message RC192 diag 0403012C .
    A dump also shows an ABEND0C4 PIC11 in IGGDAC02 with R9
    containing a truncated 24-bit ucb address.  R5 contains
    the 31-bit ucb address.  The invalid 24-bit ucb address is
    being passed to the DADSM convert routine.
    The problem is resolved by IAM fix # P630318 .
  .
  ABENDA37 rc8 (rc08) IN IMS USING PROSMS STOPX37
    BMC was updating EOV's copy of the user's dcb with the new
    TIOT value.  This value later propagated to the user's DCB,
    which resulted in the A37 abend when IMS subsequently tried
    to obtain another extent.
    Additional symptom : IEC999I (msgIEC999I) IFG0554A ABEND0C4
    BMC fix number is PR352PHY .
  .
  ABEND213-B4 WHEN DISP=MOD FOR MULTIVOLUME STRIPED DATASET
    JFCBVSLQ IS > 1 BECAUSE SMFUTIL SETS MOD DATASET VLSQ TO
    JFCBNVOL ON ASSUMPTION THAT MOD WILL BEGIN ON LAST VOLUME.
    FOR STRIPED DATASETS THIS CAUSES 213-B4 ABEND.
    ADDITIONAL SYMPTOMS: IEC143I msgIEC143I 213-B4 rcB4
    SMFUTIL R7 fix is SMF700069
  .
  IOS000I IOE 3490 FORMAT INCOMPATIBLE followed by ABEND0C4 in
     a CA-1 module.  The required CA-1 PTFs were LO05729 & LO12147
     for release 5.2.
  .
  ABEND16E RC04 DURING DEBCHK DELETE BEING ISSUED FROM STERLING
  SHRINK MODULE ZSURSHRK OFFSET AT +X'7E'. STERLING FIX = SS04731
  .
  TAPES INCORRECTLY ASSIGNED IN PARTITIONED ATL USING CA1 CBRUXENT
     Tapes added to a partitionaed library are not recognized due
  to incorrect return code passed to CA1's CBRUXENT exit from CA1
  module TMSQSTS. CA1 Fix # is LO27547 .
  .
  COBOL PROGRAM ABENDS W/ ABEND0C4-04 IN IFG0194F
    0C4 was actually in CA module TMS00SVC + x'0A50'.
    Computer Associates provided fix LO35403 with PRE of LO35096
    for CA Release 5.2  .  An IPL is required.
  
  abend0c4 in IGG019AL when DCBRECAD is 31-bit address and caller
  is 24-bit mode.  Performance Essential (Rocket) was using
  IFG0EX0B to set RMODE31=BUFF incorrectly.  Talk to Rocket.
  

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