CA IDMS IUA EIUA

Expand all | Collapse all

QO84982 Broken Chains

  • 1.  QO84982 Broken Chains

    Posted 03-07-2007 11:51 AM
    CA Have issued QI86517 stating that QO84982 can create broken chains
    when using large buffer pools. No being on SP2/3/4 I cannot remember if
    there is an SP0/1 version of QO84982. I could not find one.



    Chris Wood

    Alberta Department of Energy

    CANADA




    "
    IDMS Public Discussion Forum
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP
    IDMS-L@LISTSERV.IUASSN.COM
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    QO84982 Broken Chains
    "CA Have issued QI86517 stating that QO84982 can create broken chains
    when using large buffer pools. No being on SP2/3/4 I cannot remember if
    there is an SP0/1 version of QO84982. I could not find one.



    Chris Wood

    Alberta Department of Energy

    CANADA




    "
    IDMS Public Discussion Forum
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP
    IDMS-L@LISTSERV.IUASSN.COM
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    Re: SQL Option overhead
    "Sam,

    Although my experience is about 10 years old, as far as I remember there
    was no overhead running with the SQL Option, in itself.
    Meaning IDMS with SQL Option performs the same as IDMS without the SQL
    Option.

    Naturally when you start using the SQL Option you will impact the overall
    performance of the CV, just as it is with any additional workload.
    Keep in mind that it is significantly easier to write really bad SQL than
    it is to write really bad DML, so make sure your resource limits are set
    appropriately.

    Tommy Petersen
    110 Cokesbury Rd
    Room 542H
    Lebanon, NJ 08833

    Phone:
    Internal 200 - 3699
    External (908) 236-3699
    Fax: (908) 236-3692




    Sam Mowbray
    <base.data@HOTMAI
    L.COM> To
    Sent by: IDMS IDMS-L@LISTSERV.IUASSN.COM
    Public Discussion cc
    Forum
    <IDMS-L@LISTSERV. Subject
    IUASSN.COM> SQL Option overhead


    03/07/2007 08:04
    PM


    Please respond to
    IDMS Public
    Discussion Forum
    <IDMS-L@LISTSERV.
    IUASSN.COM>






    Hi List,

    I am currently investigating the SQL Option and am interested to find out
    different sites experiences with the option and the overhead in terms of
    CPU
    that you may have experienced.

    Regards

    Sam Mowbray
    Total Data Design Pty Ltd

    _________________________________________________________________
    AdvertisemSent: It's simple! Sell your car for just $20 at carsales.com.au
    http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%2Ecom%2Fcgi%2Dbin%2Fa%2Fci%5F450304%2Fet%5F2%2Fcg%5F801577%2Fpi%5F1005244%2Fai%5F838588&_t=757768878&_r=endtext_simple&_m=EXT
    "
    IDMS Public Discussion Forum
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP
    IDMS-L@LISTSERV.IUASSN.COM
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    Re: SQL Option overhead
    "Sam, can you be more specific with your question?

    Also, do you plan to use the SQL option To: a) access network database
    via SQL, or b) create new relational databases?

    The short answer is that, in my experience, a relational database (of
    any brand) will never perform as well as a network database. But there
    can be valid reasons for going relational in spite of the performance
    cost.


  • 2.  Re: QO84982 Broken Chains

    Posted 03-08-2007 05:07 AM
    Bill,

    I have looked at QO84981 and it applies to all levels of 15.0 yet
    QO84982 only applies to 16.0 SP2 and above. Did something get dropped
    out of 16.0 SP0 and 1 for this problem not to be present in those levels
    too?

    Thanks

    Chris


  • 3.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 05:07 AM
    Bill,

    I have looked at QO84981 and it applies to all levels of 15.0 yet
    QO84982 only applies to 16.0 SP2 and above. Did something get dropped
    out of 16.0 SP0 and 1 for this problem not to be present in those levels
    too?

    Thanks

    Chris


  • 4.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 05:07 AM
    Bill,

    I have looked at QO84981 and it applies to all levels of 15.0 yet
    QO84982 only applies to 16.0 SP2 and above. Did something get dropped
    out of 16.0 SP0 and 1 for this problem not to be present in those levels
    too?

    Thanks

    Chris


  • 5.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 05:07 AM
    Bill,

    I have looked at QO84981 and it applies to all levels of 15.0 yet
    QO84982 only applies to 16.0 SP2 and above. Did something get dropped
    out of 16.0 SP0 and 1 for this problem not to be present in those levels
    too?

    Thanks

    Chris


  • 6.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 05:07 AM
    Bill,

    I have looked at QO84981 and it applies to all levels of 15.0 yet
    QO84982 only applies to 16.0 SP2 and above. Did something get dropped
    out of 16.0 SP0 and 1 for this problem not to be present in those levels
    too?

    Thanks

    Chris


  • 7.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 05:07 AM
    Bill,

    I have looked at QO84981 and it applies to all levels of 15.0 yet
    QO84982 only applies to 16.0 SP2 and above. Did something get dropped
    out of 16.0 SP0 and 1 for this problem not to be present in those levels
    too?

    Thanks

    Chris


  • 8.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 05:07 AM
    Bill,

    I have looked at QO84981 and it applies to all levels of 15.0 yet
    QO84982 only applies to 16.0 SP2 and above. Did something get dropped
    out of 16.0 SP0 and 1 for this problem not to be present in those levels
    too?

    Thanks

    Chris


  • 9.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 05:07 AM
    Bill,

    I have looked at QO84981 and it applies to all levels of 15.0 yet
    QO84982 only applies to 16.0 SP2 and above. Did something get dropped
    out of 16.0 SP0 and 1 for this problem not to be present in those levels
    too?

    Thanks

    Chris


  • 10.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 05:28 AM
    Chris,
    You are correct that the r16 version of the apar only applies to r16 SP2
    and above. We did not publish a version of QO84982 for r16 SP0 & SP1.
    Because of the enhancements added on the r16 Service Packs, sometimes we
    are able to publish apars that apply to all service packs and sometimes
    only to a subset of those Service Packs.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com


  • 11.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 05:28 AM
    Chris,
    You are correct that the r16 version of the apar only applies to r16 SP2
    and above. We did not publish a version of QO84982 for r16 SP0 & SP1.
    Because of the enhancements added on the r16 Service Packs, sometimes we
    are able to publish apars that apply to all service packs and sometimes
    only to a subset of those Service Packs.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com


  • 12.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 05:28 AM
    Chris,
    You are correct that the r16 version of the apar only applies to r16 SP2
    and above. We did not publish a version of QO84982 for r16 SP0 & SP1.
    Because of the enhancements added on the r16 Service Packs, sometimes we
    are able to publish apars that apply to all service packs and sometimes
    only to a subset of those Service Packs.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com


  • 13.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 05:28 AM
    Chris,
    You are correct that the r16 version of the apar only applies to r16 SP2
    and above. We did not publish a version of QO84982 for r16 SP0 & SP1.
    Because of the enhancements added on the r16 Service Packs, sometimes we
    are able to publish apars that apply to all service packs and sometimes
    only to a subset of those Service Packs.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com


  • 14.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 05:28 AM
    Chris,
    You are correct that the r16 version of the apar only applies to r16 SP2
    and above. We did not publish a version of QO84982 for r16 SP0 & SP1.
    Because of the enhancements added on the r16 Service Packs, sometimes we
    are able to publish apars that apply to all service packs and sometimes
    only to a subset of those Service Packs.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com


  • 15.  Re: QO84982 Broken Chains

    Posted 03-08-2007 05:28 AM
    Chris,
    You are correct that the r16 version of the apar only applies to r16 SP2
    and above. We did not publish a version of QO84982 for r16 SP0 & SP1.
    Because of the enhancements added on the r16 Service Packs, sometimes we
    are able to publish apars that apply to all service packs and sometimes
    only to a subset of those Service Packs.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com


  • 16.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 05:28 AM
    Chris,
    You are correct that the r16 version of the apar only applies to r16 SP2
    and above. We did not publish a version of QO84982 for r16 SP0 & SP1.
    Because of the enhancements added on the r16 Service Packs, sometimes we
    are able to publish apars that apply to all service packs and sometimes
    only to a subset of those Service Packs.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com


  • 17.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 06:05 AM
    Hi Chris,
    Sorry I misunderstood your question - the original problem was
    discovered after r16 SP2 went out and existed in both 15.0 and r16, so
    we wrote apars for both releases. Our normal practice is that when we
    publish an apar we source it so that the problem will not reoccur in
    future releases. Since we support multiple releases, regardless of
    which release the problem is first identified in, we will research to
    see if the same problem exists in other supported release and write a
    second apar if appropriate. If this doesn't answer your question - give
    me another try.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com


  • 18.  Re: QO84982 Broken Chains

    Posted 03-08-2007 06:05 AM
    Hi Chris,
    Sorry I misunderstood your question - the original problem was
    discovered after r16 SP2 went out and existed in both 15.0 and r16, so
    we wrote apars for both releases. Our normal practice is that when we
    publish an apar we source it so that the problem will not reoccur in
    future releases. Since we support multiple releases, regardless of
    which release the problem is first identified in, we will research to
    see if the same problem exists in other supported release and write a
    second apar if appropriate. If this doesn't answer your question - give
    me another try.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com


  • 19.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 06:05 AM
    Hi Chris,
    Sorry I misunderstood your question - the original problem was
    discovered after r16 SP2 went out and existed in both 15.0 and r16, so
    we wrote apars for both releases. Our normal practice is that when we
    publish an apar we source it so that the problem will not reoccur in
    future releases. Since we support multiple releases, regardless of
    which release the problem is first identified in, we will research to
    see if the same problem exists in other supported release and write a
    second apar if appropriate. If this doesn't answer your question - give
    me another try.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com


  • 20.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 06:05 AM
    Hi Chris,
    Sorry I misunderstood your question - the original problem was
    discovered after r16 SP2 went out and existed in both 15.0 and r16, so
    we wrote apars for both releases. Our normal practice is that when we
    publish an apar we source it so that the problem will not reoccur in
    future releases. Since we support multiple releases, regardless of
    which release the problem is first identified in, we will research to
    see if the same problem exists in other supported release and write a
    second apar if appropriate. If this doesn't answer your question - give
    me another try.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com


  • 21.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 06:05 AM
    Hi Chris,
    Sorry I misunderstood your question - the original problem was
    discovered after r16 SP2 went out and existed in both 15.0 and r16, so
    we wrote apars for both releases. Our normal practice is that when we
    publish an apar we source it so that the problem will not reoccur in
    future releases. Since we support multiple releases, regardless of
    which release the problem is first identified in, we will research to
    see if the same problem exists in other supported release and write a
    second apar if appropriate. If this doesn't answer your question - give
    me another try.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com


  • 22.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 06:25 AM
    Chris,
    It is possible. In cases where we haven't provided a published apar for
    an r16 service pack (in this case SP0 and SP1) we would provide the
    customer a test apar version. If a customer has that situation, they
    should open an issue and we will take care of it.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com


  • 23.  Re: QO84982 Broken Chains

    Posted 03-08-2007 06:25 AM
    Chris,
    It is possible. In cases where we haven't provided a published apar for
    an r16 service pack (in this case SP0 and SP1) we would provide the
    customer a test apar version. If a customer has that situation, they
    should open an issue and we will take care of it.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com


  • 24.  Re: QO84982 Broken Chains

    Posted 03-08-2007 07:50 AM
    Bill,

    This doesn't answer my question. As it only applies to 16.0 SP2 and it
    applies to all levels in 15.0 then whatever caused the problem in the
    original 15.0 release was not included in the original 16.0 release. You
    must have discovered this later and put it into 16 SP2 rather than fix
    the original 16.0 release.

    That was what I was trying to establish.

    Chris


  • 25.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 07:50 AM
    Bill,

    This doesn't answer my question. As it only applies to 16.0 SP2 and it
    applies to all levels in 15.0 then whatever caused the problem in the
    original 15.0 release was not included in the original 16.0 release. You
    must have discovered this later and put it into 16 SP2 rather than fix
    the original 16.0 release.

    That was what I was trying to establish.

    Chris


  • 26.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 07:50 AM
    Bill,

    This doesn't answer my question. As it only applies to 16.0 SP2 and it
    applies to all levels in 15.0 then whatever caused the problem in the
    original 15.0 release was not included in the original 16.0 release. You
    must have discovered this later and put it into 16 SP2 rather than fix
    the original 16.0 release.

    That was what I was trying to establish.

    Chris


  • 27.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 07:50 AM
    Bill,

    This doesn't answer my question. As it only applies to 16.0 SP2 and it
    applies to all levels in 15.0 then whatever caused the problem in the
    original 15.0 release was not included in the original 16.0 release. You
    must have discovered this later and put it into 16 SP2 rather than fix
    the original 16.0 release.

    That was what I was trying to establish.

    Chris


  • 28.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 07:50 AM
    Bill,

    This doesn't answer my question. As it only applies to 16.0 SP2 and it
    applies to all levels in 15.0 then whatever caused the problem in the
    original 15.0 release was not included in the original 16.0 release. You
    must have discovered this later and put it into 16 SP2 rather than fix
    the original 16.0 release.

    That was what I was trying to establish.

    Chris


  • 29.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 07:50 AM
    Bill,

    This doesn't answer my question. As it only applies to 16.0 SP2 and it
    applies to all levels in 15.0 then whatever caused the problem in the
    original 15.0 release was not included in the original 16.0 release. You
    must have discovered this later and put it into 16 SP2 rather than fix
    the original 16.0 release.

    That was what I was trying to establish.

    Chris


  • 30.  Re: QO84982 Broken Chains

    Posted 03-08-2007 08:17 AM
    Bill,

    It is possible for a 16.0 SP0/1 CV to go into a loop in IDMSDBIO, module
    IDMSDBIB when varying an area according to your last message. This is
    the description for QO84982. If this can happen are you looking at
    fixing SP0/1 with the changes in QO84982 and the resultant fix?

    Thanks

    Chris


  • 31.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 08:17 AM
    Bill,

    It is possible for a 16.0 SP0/1 CV to go into a loop in IDMSDBIO, module
    IDMSDBIB when varying an area according to your last message. This is
    the description for QO84982. If this can happen are you looking at
    fixing SP0/1 with the changes in QO84982 and the resultant fix?

    Thanks

    Chris


  • 32.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 08:17 AM
    Bill,

    It is possible for a 16.0 SP0/1 CV to go into a loop in IDMSDBIO, module
    IDMSDBIB when varying an area according to your last message. This is
    the description for QO84982. If this can happen are you looking at
    fixing SP0/1 with the changes in QO84982 and the resultant fix?

    Thanks

    Chris


  • 33.  Re:Re: QO84982 Broken Chains

    Posted 03-08-2007 08:17 AM
    Bill,

    It is possible for a 16.0 SP0/1 CV to go into a loop in IDMSDBIO, module
    IDMSDBIB when varying an area according to your last message. This is
    the description for QO84982. If this can happen are you looking at
    fixing SP0/1 with the changes in QO84982 and the resultant fix?

    Thanks

    Chris


  • 34.  Re: QO84982 Broken Chains

    Posted 03-08-2007 11:36 AM
    Hi Bill,

    For the sites that are still 14.1 out there was it a problem in that
    release as well - even though it is no longer supported? When I was
    looking at buffer tuning quite a few years ago the advice I had was not
    to go over 2000 pages.

    Regards

    Sam Mowbray


    From: ""Abbott, William F"" <William.Abbott@CA.COM>
    Reply-To: IDMS Public Discussion Forum
    Subject: Re: QO84982 Broken Chains
    Date: Thu, 8 Mar 2007 13:25:14 -0500

    Chris,
    It is possible. In cases where we haven't provided a published apar for
    an r16 service pack (in this case SP0 and SP1) we would provide the
    customer a test apar version. If a customer has that situation, they
    should open an issue and we will take care of it.

    Bill Abbott
    CA
    Vice President, Level 2 Support
    100 Staples Drive
    Framingham, MA 01702
    tel: +1 508 628 8011
    fax: +1 508 820 2934
    william.abbott@ca.com