IDMS

 View Only
  • 1.  TF24458

    Posted Sep 23, 2005 12:27 PM
    Hi,



    This 16.0 'needed' test fix has not been upgraded to a full blown QO
    apar yet. We have had it on Production since May this year. Does anybody
    know why that is or has or just been forgotten? Is there a 16.2 version?



    Thanks



    Chris Wood

    Alberta Department of Energy

    CANADA

    This communication is intended for the use of the recipient to which it
    is addressed, and may contain confidential, personal and or privileged
    information. Please contact us immediately if you are not the intended
    recipients of this communication, and do not copy, distribute, or take
    action relying on it. Any communication received in error, or subsequent
    reply, should be deleted or destroyed.

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








    Normal

    Normal
    Re: TF24458
    "Thanks for the update Stan. It would be interesting to know what was
    changed because it appeared to work well for us after they made an
    earlier change from a first attempt. Now we may have to test this again.

    Chris


  • 2.  Re:TF24458

    Posted Sep 23, 2005 12:27 PM
    Hi,



    This 16.0 'needed' test fix has not been upgraded to a full blown QO
    apar yet. We have had it on Production since May this year. Does anybody
    know why that is or has or just been forgotten? Is there a 16.2 version?



    Thanks



    Chris Wood

    Alberta Department of Energy

    CANADA

    This communication is intended for the use of the recipient to which it
    is addressed, and may contain confidential, personal and or privileged
    information. Please contact us immediately if you are not the intended
    recipients of this communication, and do not copy, distribute, or take
    action relying on it. Any communication received in error, or subsequent
    reply, should be deleted or destroyed.
    This communication is intended for the use of the recipient to which it is addressed, and may contain confidential, personal and or privileged information. Please contact us immediately if you are not the intended recipients of this communication, and do not copy, distribute, or take action relying on it. Any communication received in error, or subsequent reply, should be deleted or destroyed.

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








    Normal

    Normal
    Re: Linked-to dialogs in Perfmon reports
    "Kay and others who may be experiencing retrieval locking programs,
    I've attached the COBOL source for a program I wrote to read the dictionary to get information about dialogs. It extracts the information and puts it in a sequential file which you can sort and FTP to an excel spreadsheet, for analysis. The file includes the following elements:
    Dialog Name, Map Name, User ID and Date of last update, an indicator which tells whether the dialog is retrieval only or performs updates, the retrieval lock indicator, the dialog module containing the source code, an indicator which tells whether the dialog is performing a LINK or INVOKE, the Program or Dialog name the dialog is linking or invoking and an indicator to distinguish a called program from a dialog. This indicator will be a 'D' if the called entity is a dialog, otherwise it will be blank.
    Once you have this list, you can start removing all of the retrieval locks on dialogs, which are retrieval only, and don't link to or invoke any update dialogs. After this, you can trace the application thread for those dialogs being linked to and see if they are also performing updates. If there are still retrieval locking problems occurring, then that's when you will have to look at making coding changes, which I outlined to Tim earlier. Anyway, if you get to that point, let me know and I will be happy to walk you through it.
    Good Luck.
    Margaret






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








    Normal

    Normal
    IDMS Tools and COBOL OSVS
    "In looking at our IDMS 15.0 SP6 tools loadlib, it is learned many CA delivered load modules have COBOL OSVS linked in.

    Given, COBOL OSVS runtime support is slowly being eliminated by IBM, this would appear to be a potential problem. Anyone already address this item?

    Example of USJEXT0.

    USJEXT0 0182082C 42E2 022B78 000000 05.007 USJEXT0 RMODE 24 AMODE 24
    CS-USJEXT0 01CD4C NOV 5,1901 9.27.23 NOENDJ NOFLOW OBJ370 COBOPT VS
    NORES NOSTATE NOSYMD SYSOUD NOTEST 0204
    CS-ILBOCOM0 000173 OLDCOB R/T OSVS 0501 83194
    CS-GSSCALL 000D38 569623400 0102 99326 HL ASSEMBLER LANGUAGE CSECT
    CS-ILBOACP 000290 OLDCOB R/T OSVS 0201 86036
    CS-ILBOBEG 0001DC OLDCOB R/T OSVS 0501 83194


    g Corporate - GIS
    _______________________________________
    Rob Klan
    "
    IDMS Public Discussion Forum
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP
    IDMS-L@LISTSERV.IUASSN.COM
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    Re: IDMS Tools and COBOL OSVS
    "Gooooooooooooooood question Rob.


  • 3.  Re: TF24458

    Posted Sep 29, 2005 03:31 AM
    We have upgraded 3 of our 6 production CV's from R14.1 to R16.1 and were
    having
    some isolated currency (0306) problems. We applied TF24458 which did
    not help.
    CA had us apply a completely reworked version of TF24458 which solved
    our currency (0306) problems. I believe CA is still working on the QO
    apar for TF24458.

    Stan Robinson
    American Greetings