CA IDMS IUA EIUA

Expand all | Collapse all

CA IDMS & z/OS 1.10

  • 1.  CA IDMS & z/OS 1.10

    Posted 05-27-2009 11:05 AM
    Hi everyone,

    We will be upgrading our opsys this summer from z/OS 1.8 to 1.10. Has
    anyone else gone this route? do you have any suggetions of things to
    look out for?

    Thank you,
    Laura Rochon
    Ajilon Consulting
    "
    IDMS 3rd-party providers forum
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    SMTP
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    Re: CA IDMS & z/OS 1.10
    "QI82743 addresses the change to z/OS 1.9 where AllowUserKeyCSA default
    changed to 'no' where it used to be 'yes'. This is of course also
    applicable to z/OS 1.10.

    In z/OS 1.10, the COBOL LE environment changed. We had a problem with
    excessive calls to module CEEROPT which killed our performance in a high
    rate OLTP CV. This occurs when a COBOL, PL/I or LE-compliant assembler
    program does a dynamic CALL to another program or the CA IDMS system,
    the CA IDMS program may access a dictionary load area to try to find the
    program. We're on 16.0 SP1 and CA provided a ZAP (TB96838) to prevent
    the calls so we wouldn't have to change the SYSGEN for all our programs
    from DYNAMIC to NODYNAMIC. Later we found out a system programmer had
    changed the default for CEEROPT in PARMLIB(CEEPRM00) from 'COMPAT' to
    'ALL'. IBM recommended it be changed back to COMPAT. The zap is still in
    place but I think the change to Parmlib may have caused the problem.

    We were in production one day until the CEEROPT problem forced us to
    drop back. We're waiting for a window to go again.


    Jim Lancelot | VA Corporate Data Center Operations
    Austin ITC
    phone 512.326.6471
    email jim.lancelot@va.gov


  • 2.  Re:CA IDMS & z/OS 1.10

    Posted 05-27-2009 11:05 AM
    Hi everyone,

    We will be upgrading our opsys this summer from z/OS 1.8 to 1.10. Has
    anyone else gone this route? do you have any suggetions of things to
    look out for?

    Thank you,
    Laura Rochon
    Ajilon Consulting
    "
    IDMS Public Discussion Forum
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP
    IDMS-L@LISTSERV.IUASSN.COM
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    Re: CA IDMS & z/OS 1.10
    "Hi Laura,

    We did on April 26, 2009 with IDMS rel. 15. No issues were
    encountered.=20


    _________________________________________________
    John N. Baloga
    IDMS DBA, Global I & O=20
    Volvo Information Technology
    7825 National Service Road, Greensboro, NC 27409
    United States of America

    Telephone: 336-393-3425=20
    Telefax: 336-393-4080=20
    E-mail: john.baloga@volvo.com


  • 3.  Re:CA IDMS & z/OS 1.10

    Posted 05-27-2009 12:05 PM
    Hi everyone,

    We will be upgrading our opsys this summer from z/OS 1.8 to 1.10. Has
    anyone else gone this route? do you have any suggetions of things to
    look out for?

    Thank you,
    Laura Rochon
    Ajilon Consulting
    "
    IDMS 3rd-party providers forum
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    SMTP
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    Re: CA IDMS & z/OS 1.10
    "Hi Laura,

    We did on April 26, 2009 with IDMS rel. 15. No issues were
    encountered.


    _________________________________________________
    John N. Baloga
    IDMS DBA, Global I & O
    Volvo Information Technology
    7825 National Service Road, Greensboro, NC 27409
    United States of America

    Telephone: 336-393-3425
    Telefax: 336-393-4080
    E-mail: john.baloga@volvo.com


  • 4.  Re:CA IDMS & z/OS 1.10

    Posted 05-27-2009 12:05 PM
    Hi everyone,

    We will be upgrading our opsys this summer from z/OS 1.8 to 1.10. Has
    anyone else gone this route? do you have any suggetions of things to
    look out for?

    Thank you,
    Laura Rochon
    Ajilon Consulting
    "
    IDMS Public Discussion Forum
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP
    IDMS-L@LISTSERV.IUASSN.COM
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    Problems with the Archive Log utility.
    "Just a heads up for all you log junkies.

    The archived log may be missing entries when the archive process starts
    up prior to the completion of a task. Level 1 is now looking into it.

    Here's the scenariTo:

    We have a segment with 300+ areas. At about 7:30 PM we make a ""break""
    in our systems and perform backups, statistics gathering etc

    The process goes like: =20
    Vary segment retrieval
    Break connection with shadow disk volumes
    Vary segment update
    Backup shadow drives.

    While this is going on, at about 7:35 PM we have a job that fires off
    the archive log utility.

    The process goes smoothly; however...
    When you look at the archive log files you see the following:
    SEGNAME.AREA#40 VARRIED UPDATE
    SEGNAME.AREA#41 VARRIED UPDATE
    SEGNAME.AREA#42 VARRIED UPDATE
    SEGNAME.AREA#43 VARRIED UPDATE
    END OF LOG TAPE.
    The next day's log tape starts like this:
    SEGNAME.AREA#46 VARRIED UPDATE
    SEGNAME.AREA#47 VARRIED UPDATE
    SEGNAME.AREA#48 VARRIED UPDATE
    SEGNAME.AREA#49 VARRIED UPDATE
    etc.

    Notice that the ""audit trail"" for AREAs 44 and 45 are missing. They
    were varried back on correctly.

    The number of areas ""missed"" ranges from 1 to 5.

    Does this impact anything other than the VARY OFF/RET/ON/UPDATE
    messages? I don't know. But I thought you'd like to know

    Dick

    Richard Pierce
    Massachusetts Executive Office of Transportation - IT Services
    IDMS Database Administrator
    10 Park Plaza, Suite 7110
    Boston, MA 02116
    (617) 973-8911
    richard.pierce@state.ma.us
    "
    IDMS 3rd-party providers forum
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    SMTP
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    Problems with the Archive Log utility.
    "Just a heads up for all you log junkies.

    The archived log may be missing entries when the archive process starts
    up prior to the completion of a task. Level 1 is now looking into it.

    Here's the scenariTo:

    We have a segment with 300+ areas. At about 7:30 PM we make a ""break""
    in our systems and perform backups, statistics gathering etc

    The process goes like:
    Vary segment retrieval
    Break connection with shadow disk volumes
    Vary segment update
    Backup shadow drives.

    While this is going on, at about 7:35 PM we have a job that fires off
    the archive log utility.

    The process goes smoothly; however...
    When you look at the archive log files you see the following:
    SEGNAME.AREA#40 VARRIED UPDATE
    SEGNAME.AREA#41 VARRIED UPDATE
    SEGNAME.AREA#42 VARRIED UPDATE
    SEGNAME.AREA#43 VARRIED UPDATE
    END OF LOG TAPE.
    The next day's log tape starts like this:
    SEGNAME.AREA#46 VARRIED UPDATE
    SEGNAME.AREA#47 VARRIED UPDATE
    SEGNAME.AREA#48 VARRIED UPDATE
    SEGNAME.AREA#49 VARRIED UPDATE
    etc.

    Notice that the ""audit trail"" for AREAs 44 and 45 are missing. They
    were varried back on correctly.

    The number of areas ""missed"" ranges from 1 to 5.

    Does this impact anything other than the VARY OFF/RET/ON/UPDATE
    messages? I don't know. But I thought you'd like to know

    Dick

    Richard Pierce
    Massachusetts Executive Office of Transportation - IT Services
    IDMS Database Administrator
    10 Park Plaza, Suite 7110
    Boston, MA 02116
    (617) 973-8911
    richard.pierce@state.ma.us
    "
    IDMS Public Discussion Forum
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP
    IDMS-L@LISTSERV.IUASSN.COM
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    Direct Data OCA-MQSeries and Rel. 17
    "Hello Everyone,

    I am having difficulty trying to get OCA-MQSeries and IDMS rel. 17
    to work. I have removed the OCA-Commit ""hooks"" from modules IDMSIDMS
    and IDMSDBIO as instructed by Data Direct. Data Direct said to set the
    RRS option =3D YES, which I also did. Has anyone been able to get Rel. =
    16
    or above and Data Direct's OCA MQ-Series to work and what did you have
    to do?=20

    Thanks in Advance.


    _________________________________________________
    John N. Baloga
    IDMS DBA, Global I & O=20
    Volvo Information Technology
    7825 National Service Road, Greensboro, NC 27409
    United States of America

    Telephone: 336-393-3425=20
    Telefax: 336-393-4080=20
    E-mail: john.baloga@volvo.com
    "
    IDMS 3rd-party providers forum
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    SMTP
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    Direct Data OCA-MQSeries and Rel. 17
    "Hello Everyone,

    I am having difficulty trying to get OCA-MQSeries and IDMS rel. 17
    to work. I have removed the OCA-Commit ""hooks"" from modules IDMSIDMS
    and IDMSDBIO as instructed by Data Direct. Data Direct said to set the
    RRS option = YES, which I also did. Has anyone been able to get Rel. 16
    or above and Data Direct's OCA MQ-Series to work and what did you have
    to do?

    Thanks in Advance.


    _________________________________________________
    John N. Baloga
    IDMS DBA, Global I & O
    Volvo Information Technology
    7825 National Service Road, Greensboro, NC 27409
    United States of America

    Telephone: 336-393-3425
    Telefax: 336-393-4080
    E-mail: john.baloga@volvo.com
    "
    IDMS Public Discussion Forum
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP
    IDMS-L@LISTSERV.IUASSN.COM
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    Re: Direct Data OCA-MQSeries and Rel. 17
    "I am running CA-IDMS release 16.0 SP4 for quite some time now in test,
    QA and production regions with OCA-MQSeries V2R3 at maintenance level
    2006/02 z/OS 1.9 MF MQSeries is V6. I am working on installing release
    17.0 now also. Do you get any error messages?

    Steve Harmeson =20