IBM Support

II07766: INFO ITEMS FOR IMS SYSTEMS. PRIOR II02886 NEXT II08109 *CLOSED*FOR FUTURE UPDATES SEE THE "HTTP://WWW.IBM.COM/IMS" SUPPORT PAGE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • ******************** JANUARY 10, 2002 **************************
    RETAIN INFORMATION ITEMS WILL NO LONGER BE USED TO DOCUMENT
    COMMON USER ERROR INFORMATION.  THE NEW PROCESS WILL RELAY THIS
    INFORMATION VIA THE SUPPORT PAGE WITHIN THE IMS HOME WEBSITE AT
            "HTTP://WWW.IBM.COM/IMS"
    CLICK ON THE "SUPPORT" KEYWORD IN THE LEFT MENU AREA.
    ****************************************************************
    568501201 568501201 568501301
    566540802 566540801 566540901 5740XY211 5740XX214 5740I1214
    5740I2214 HMK4102 HMH4102 JMH4112 JMJ4112 HMJ4102 JMJ4122
     HMK3102 HMH3102 HMH2202 HMH2102 HIM1304 JMH3112 JMH2213 JMH2110
     JMH1314 HMJ3102 JMH2223 JIM1324 JMH2273 JMH2233 JMH2130 JIM1334
     JMH2243 JMH2140 JIM1344 JMK3152 JMH2253 JMH2150 JIM1354 JMK3162
     JMH2263 JMH2160 JIM1364 JMK3112 JMK4152 JMK4162 JMK4112
    
    
    
     R102 R202 R304 R112 R213 R110 R314 R223 R120 R324 R273 R233 R13
     R334 R152 R253 R150 R354 R162 R263 R160 R364
     THIS APAR IS BEING CREATED AS AN EXTENTION TO II02886 AND
     II04204 II05221 AND II05470 TO DOCUMENT COMMON PROBLEMS IN THE
     SYSTEMS AREA OF IMS.  DIAGNOSTIC PROCEDURES AND/OR SOLUTIONS
     TO THESE PROBLEMS MAY BE INCLUDED.
       WHEN ADDING NEW ENTRIES, BE SURE TO FIRST ADD AN INDEX ITEM
     THAT BRIEFLY DESCRIBES THE PROBLEM SYMPTOMS AND THE PAGE ON
     WHICH THE FULL DESCRIPTION MAY BE FOUND.  INCLUDE YOUR NAME AND
     DATE AT WHICH TIME THE ENTRY IS MADE OR UPDATED.
     --------------  PROBLEM INDEX  --------------------------------
     1. ABEND0C4 DFSPRE10 CSECT DFSSYNTX                     PG. E 1
     2. MISC ABEND0C4 WITH PSB NAME DUE TO OVERLAY           PG. E2
     3. MNOTE G205 psb operand is omitted or invalid         PG. E3
     4. ABEND0C4 DFSCLM00 IMS 4.1                            PG. E4
     5. Doc update for sysdef messages g008 and g1211        PG. E5
     6. ABEND0C4 DFSCSIF0 on CLC instruction, R10 CSAB bad   PG. E7
     7. Callable Services LOAD Module function CSLDUSE       PG. E8
     8. UN53182 HOLD DOC CONTAIN INCORRECT INFORMATION       PG  E9
     9. DFSLI000 compatability between ims4.1 and ims3.1     PG  E9
    10. Abend0c4 in DFSCLM00 near label CLM00101.            PG E11
    11. ims310 and ims410 t2 svc compatability               PG E11
    12. abendu3058 attempting to install fastpath            PG E12
    13. MSGDFS3588W from dfsss000 during lgen for svcb       PG E13
    14. MSGIEW0241 during LGEN process                       PG E15
    15. Binder compatibility msgiew2652w msgiew2645w         PG E17
    16. Abendu0123 received when abendu0777 expected         PG E18
    17. Orphaned SP241 KEY7 storage for 216 bytes            PG E20
    18. MSGIEW0461 in LGEN caused by sequence numbers        PG E21
    19. ABENDU0581 in DFSIINV0 becaused incorrect JCLIN      PG E22
    20. Abend0c4 S0c4 DFSIDSP0 after label ITASKR90          PG E22
    21. ABENDU0240 when MPP accesses external datasets.      PG E23
    22. MSGIEW2303S and MSGIEW2677S during dbctl batch gen   PG E25
    23. DFSPZPxx assembler error - override value is null    PG E26
    24. Abendu0730 rc14 in IMS410 due to IMS310 of DFSPRRG0  PG E26
    25. MSGGIM24801W No applicable ++VER when receiving PTFS PG E27
    26. ABENDU3042 r15=05060024 in dfsespr0                  PG E28
    XX. FUTURE UPDATES WILL BE MADE WITHIN THE IBM SUPPORT
        WEBSITE AT "WWW.IBM.COM/IMS".  THE SUPPORT OPTION IS ON
        THE LEFT MENU.  (January 10, 2002)
    

Local fix

Problem summary

  • 1. ABEND0C4 DFSPRE10 csect DFSSYNTX after label ADDNAME2 on
    EX instruction.  Reg4 is bad, and we get it from reg6 which
    should be the address of PARSVAL.  R6 points to instructions
    within another module.  This problem was caused by a user who
    entered blanks after the TRANSACTION CODE= parm on the TRANSACT
    macro - i.e. TRANSACTION CODE=(    ,followed by valid parms).
    ************************************PILETIC 4/11/94************
    2.  Misc. random 2 word overlay with data containing psb
    names.  ABEND0C4 ABEND0C1 ABEND0CX received because of
    the overlays.  UCB and CNT control blocks hit as well
    as module overlays.  Abending pgms include dfsrcp30, dfsrlp00
    and dfsicl70.  This is caused by boole and babbage db2
    manager monitor package.
    Additional symptoms include abendu0168 during restart
    because of the bad cnt blocks checkpointed.  This caused
    a coldcom restart to be done.
    ***********************************BUTTERWECK 4/14/94*******
    

Problem conclusion

  • 3.  MNOTE g205 psb operand is omitted of invalid, received
    when specifying a psb name beginning with dfs or dbcdm
    (excluding DFSSAM and dfsivp) for ims4.1  This is an
    ims4.1 restriction on psb name.  Updates to the manuals
    have been requested. ims410
    ***********************************BUTTERWECK 4/15/94*******
     4. ABEND0C4 in DFSCLM00 after label CLM00400 on CDS
        instruction. REG4 is bad = x'00000010'. This problem
        is caused by OEM BMC's Database Itegrity Plus (DI+).
        Their tracking # is 204095 and the PTF's are: BP43670,
        BP43671, BP43672, BP46611, BP46612 and BP46613.
    ***********************************JENNINGS 4/19/94*********
    5.  The following pub updates have been requested to the
    ims4.1  Messages and Codes Manual sc26-3071 chapter 8:
    Change g008 to the following:
    G008   LGEN ASSEMBLE EXECUTION NOT FROM THE PREPROCESSOR.
      Explanation:  One of the following occurred:
       .  A LGEN/MODBLKS or LGEN/MSVERIFY sysgen assembly was
          attempted without using the preprocessor.  The
          preprocessor must be invoked to build the assembly input
          and to call the assembler.
       .  Assembler listing control instructions (such as PRINT OFF)
          imbedded in the stage 1 source.
      System Action:  The assembly fails.
    Programmer Response:  Change the job step JCL to execute the
    preprocessor rather than the assembler or modify the stage 1
    source removing the assembler listing control instructions (i.e
    PRINT OFF) and rerun the stage 1.
    
    Severity:  4
    
    *
    Add the following message:
    G1211 ETO DESCRIPTORS ARE NOT BUILT IN A LGEN SYSGEN.
    
    Explanation: ETO descriptors are not built in a LGEN sysgen.
    - A severity 2 warning message is issued when ETO descriptors
      are requested along with the sysgen, i.e.
      ETOFEAT=(YES,YES,ALL). A severity 4 error message is issued
      when only ETO  descriptors are requested in a LGEN sysgen,
      i.e. ETOFEAT=(YES,YES,ONLY)
    
    System Action: For the warning message, processing continues.
    For the error message, the stage 1 will not complete
    successfully.
    Programmer Action: Change the ETOFEAT keyword of the IMSCTRL
     macro to not request the building of the ETO descriptors.
    
    Severity: 2 or 4
    ****************************** Butterweck 4/28/94 ********
    6. ABEND0C4 in callable services module DFSCSIF0 on CLC
       instruction when referencing R10 ( CSAB ).  The error
       occurs on the second consecutive callable services request.
       On the second call, the token (first word of CS PARM LIST)
       has been destroyed.  There are two ways to code the second
       call to fix this.
       a. When intializing the parm list for the second (and
          subsequent calls under the same initilization), save
          the token ( CSPTOKN ) somewhere and then put it back
          prior to the call to DFSCSIF0.
       b. Don't clear the first word (token) from the parm list
          when initializing it for the second call.
    **********************************PILETIC 05/04/94**********
    7. When using Callable Services LOAD Module function and you
    want to load the existing copy of a module, CSLDUSE = CSLDUOLD
    and the module must be either reentrant or reusable.  If it
    is not linkedited with RENT or REUS attributes, you will get
    a new copy of the module even if CSLDUOLD is requested.
    **********************************PILETIC 05/04/94**********
    8. PTF UN53182'S HOLD DOC Refered to IMS 3.1 UTILITIES
    REFERENCE Manual SC26-4284-01 Page 628 was incorrect.  It
    should be either Page 618 for SC26-4284-01 or Page 628 for
    SC26-4284-00.
    *****************************Alan K. Ho 05/04/94************
    9.  The IMS/ESA 4.1 Migration Guide ( GG24-4150-00 )
    under Fallback Considerations states 'That the ims4.1
    language interface (dfsli000) module cannot be executed on the
    previous releases of IMS.  Any application programs that are
    link-edited with the ims 4.1 Language Interface Module cannot
    be executed on the old IMS release'.
    *
    This is true if new functions introduced in ims 4.1 are being
    used by the application program (i.e. cee or ess
    interface).  If these new functions are NOT being used then
    the ims 4.1 language interface module is compatible with ims
    3.1.
    ***************************** Butterweck 5/5/94 **********
    10. An abend0c4 occurs in DFSCLM00 +x'6c' near label CLM00101
    when R8 is zero. This happens when DFSCLM00 is called by
    DeltaIMS (VTF prefix) and the parmlist +x'c' is zero. Prob
    is fixed in V5.02.3
    +++++++++++++++++++++++++++++ Compton 5/16/94 +++++++++++++
    11.  The ims t2 svc dfsvc200 is downward compatible between
    ims410 and ims310 (i.e. you can use the ims410 t2 svc on
    an ims310 system).  The reverse is not true however, you
    cannot use the ims310 t2 svc with an ims410 system. If you
    do so the results are unpredictible (apar pn28971 introduced
    changes that will cause an abend0c4 in module dfsvci00
    in this situation). One 0c4 occurred at x'2ea' on MVC.
    *********** Butterweck 5/18/94 - mod. Bullinger 3/13/95 *******
    12. abendu3058 can occur when some modules are assembled
    with fastpath and some modules are assembled without
    fastpath.  Adding fastpath to a system not only adds
    additional modules it also modifies some common modules
    such as dfsask00.  If modules genned without fastpath are
    used (i.e. the non fastpath modules are in lpalib and lpalib
    is accessed before steplib) this abend can occur.
    ***************************** Butterweck 5/18/94 **********
    13.  The following is received running the lgen sort split
    program dfsss000 :
    DFS3588W- EXPECTED END RECORD NOT FOUND AT  INPUT RECORD
    location 000     0056 RESOURCE TYPE = SCVB RETURN CODE = 4
    This may be caused when using acf ( acf2 ) security.  This
    is a know acf2 problem - contact the vendor for the fix.
    ts94039 - acf fix number
    Additional keywords:  msgdfs3588W rc(04) rc04 stage2 sysgen
    ****************************** Butterweck 5/20/94 ********
    14. MSGIEW0241 received during an IMS 3.1 LGEN might cause
    by pointing to an IMS 4.1 reslib.  Since there are a big
    difference between IMS 3.1 and 4.1 LGEN process.  The way to
    identify this possibility of error is to compare OCNTX01x in
    LGENOUT between a good lgen and a bad one.  The following are
    the first few lines of good OCNTX011 and bad OCNTX012 :
    
    BROWSE -- IMSVS.LGENOUT(OCNTX011) ----
             GBLB  &GBASLAST
    &GAMSTR  SETA  025893
    &GASMSTR SETA  030109
    &GAWTOR  SETA  041228
    &GBASLAST SETB 1
    &GALCNT   SETA 046202
    &GATCNT   SETA 046202
    OCNTX011 CSECT                     RECORD GENERATED BY DFSSS040
    
     BROWSE -- IMSVS.LGENOUT(OCNTX012) --------
             GBLA  &GATCNT,&GARTOT
             LCLC  &LCMODC
    &LCMODC  SETC  '0'
    &GATCNT  SETA  046474
    &GARTOT  SETA  000000
             DFSCNT GEN,MASTER,SLAVE,LGEN,4,01
    
    You will notice OCNTX011 had a Csect statement but not in
    OCNTX012 (IMS4.1 does not generate the Csect in this step) which
    caused linkage editor add $PRIVATE csect and instead of replace
    the csects in OCNTX012, the linkage editor just add the csects
    and result of msgiew0241.
    Keywords : iew0241, rc04, rc=04linkage editor
    ******************************** ALAN K. HO  06/06/94 ********
    15.  msgiew2652w and msgiew2645w resulting in rc04
    from stage2 sysgen during linked processing ( iewl ).
    These messages will be received after the binder compatability
    service is on the sms binder but the corresponding ims service
    is not on.  This will occur when compat=pm1 is specified or
    defaulted to without the corresponding ims service.  This
    item will be updated to include apar numbers when they
    are available.  rc(04) rc=04 iew2652 iew2645
    ******************************** J. Butterweck 06/07/94 ******
    16. Abendu0123 received when abendu0777 expected when APPC
    is not active.  This only happens when APPC=YES on startup
    26. MSGGIM44402W indicating dfsixv79 not assembled when
    processing un22414.  This message can be ignored and will
    allow smpe processing to continue.  DFSIXV79 contains help
    text and does not get assembled.  This message is expected.
    It will be received whenever a members in the ivp libraries
    are processed.
    *************************** Butterweck 08/08/94 **********
    27. MSGIEW2454W (for binder) and/or MSGIEW0461I (linkage
    editor) indicating unresolved external references cause rc(04)
    during accept processing.  This is expected for accept
    processing and should be ignored.  These messages are NOT
    ok when processing via apply or stage 2 ( stage2 ) of
    sysgen.
    ************************** Butterweck 08/08/94 ***********
    parameter.  This may occur when module ATBEXAI does not
    exist in SYS1.CSSLIB library.  This extract exit must reside
    in this library to determine whether a CPI-C CPIC conversation
    was allocated.  The missing module may also cause other
    unwanted abends as follows:
      Abendu2478 expected, but abendu0124 received.
      Abendu3303 expected, but abendu0125 received.
      Abendu2479 expected, but abendu0126 received.
    ================================ A. Bullinger 6-21-94 =========
    SP241 KEY7 storage may be orphaned in 216 byte chunks and have
    an eyecatcher of an IMS DB name (in one case it was a FP DB
    name).  There were no other eyecatchers.  Problem occurred
    using BMC's Secondary Index Trace facility and they have a fix
    for it.  BMC module DSIXPST3 was involved.
    ***********************************Piletic 06/24/94************
    18. IEW0461 can be iussed during LGEN stage 2 if the input to
    SORT/SPLITTER contain sequence numbers. The sequence numbers
    caused the sort/splitter to output invalid statement to
    LGENOUT.  It resulted the module/macro assemble incorrectly and
    might missing some entries.  Referred to SDR manaul under LGEN
    process stage 2 input for restriction of Sort-Splitter.
    ********************************* Alan k. Ho 06/30/94 *********
    19. ABENDU0581 might occurred, if an incorrect version of JCLIN
    or no JCLIN being run again the target csi after a sysgen.
    The NCNT field of DFSISCD0 in the dump and the value of CNT=
    of DFSISCD0 in stage 2 should be equal if the JCLIN is in
    synch.  Otherwise, a JCLIN need to be run again target csi
    before apply any maintenances to the target zone.
    ********************************** Alan K, Ho  06/30/94********
    20.  Abends0c4 received after label ITASKR90 pic4 on an OI
    instruction within the LEAVE macro.  The address pointed to
    by r13 contains a word of zeroes.  This is a known Sterling
    Software, IMSHRINK problem.  The problem appears to occur after
    an ISWITCH and after IMSHRINK goes into a wait.  The problem
    is fixed by upgrading the OEM product to 5.2.4 from 5.2.3 or
    lower.  The fix is also reported to fix abend0c1.  Reported
    under IMS310 release.
    Additional symptoms:  Also showed up as an abendu0780 rc03 rc3
    in an IMS410 release with a prior abend0c4.
    ================================== A. Bullinger 7-5-94 ========
    21.  ABENDU0240 when external MVS datasets / files are accessed
    by a MPP.  "External" in this case means external to the DL/1
    environment.  Message Processing Programs(MPPs) accessing
    external MVS datasets / files is not supported.  The
    IMS/ESA V3 Programming Design Guide, SC26-4279, chapter 3a,
    provides the types of data, input/output, a MPP can access.
    MVS datasets / files are not included.
    Additional considerations:
    a: MPP access to MVS datasets / files does work but is
       suseptable to abendu0240 if the STIMER option on the MPR
       EXEC statement parameter is set to 1 or 2.
    b: ABENDU0240 can be prevented by disabling timing by
       specifing STIMER=0.
    c: Usually, the root cause of the ABENDU0240 is that MVS
       dataset / file services such as dynamic allocate (SVC99)
       and CLOSE also issue a STIMER and only one STIMER should
       be issued for a task.  Additional detail can be found
       in PP23968 and 0E816,PK5,000.
    ================================== Earl Hale 07/13/94 =========
    22.  MSGIEW2303S AND MSGIEW2677S received for dfsatch0,
    dfssdlc0, dfskldli, and dfsirac0 causing rc(12) during
    linkedit ( lked ) when running a sysgen specifying
    'batch,dbctl' on the imsctrl macro for ims410.  This problem
    can be circumvented by specifying 'batch,db/dc'.  This problem
    has been corrected in ims510
    ================================= Butterweck 07/15/94 =======
    23. The DRA startup parameter table module DFSPZPxx pick up
    all the default valules from DFSPRP macro.  No override parm
    keywords were shipped with DFSPZPxx.  If any default value
    need to be overrided, user must specify a value in parameter
    keyword in DFSPZPxx.  A null value in the parameter will cause
    an assembler error.
    For example :   CNBA=0 - is a valid keyword
                    CNBA=, - will cause assembler error IEV074
    ============================ Alan K. Ho  7/18/94 ============
    24. Customer running IMS410 and getting abendu0730 subcode 14
    due to an improper library concatenation causing an IMS310
    version of DFSPRRG0 to be picked up.  Customer has SPM
    parameter in start up proc specified as ( SPM=, ) and does
    not want to use the DFSSPMxx member.
    Additional symptom: Abend878 abends878 rc14 - For a complete
    description see PDDB entry CXJSK via ASKQ.
    +++++++++++++++++++++++++++++++++ A. Bullinger 7-18-94 +++++++
    25. MSGGIM24801W and " NO APPLICABLE ++VER " is received
    while attempting to perform SMP RECEIVE for IMS PTFs.
    This can occur if the SREL P115 is not present in the GLOBAL
    ZONE or the IMS FMIDs have been wiped out of the GLOBAL ZONE.
    Simply add the correct IMS FMIDs and SRELs to the GLOBAL
    ZONE to fix the problem using the SMP dialog.
    ********************************* Jeff Maddix 08/02/94 ********
    26. Abendu3042 r15(05060024) in dfsespr0 can be caused by
    db2 library dsnload not being authorized.
    ********************************** J Butterweck 12/06/94 ****
    

Temporary fix

Comments

  • Information APAR II07766
    

APAR Information

  • APAR number

    II07766

  • Reported component name

    PB LIB INFO ITE

  • Reported component ID

    INFOPBLIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1994-04-08

  • Closed date

    1994-04-08

  • Last modified date

    2002-01-11

  • 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":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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
14 December 2020