IDMS

  • 1.  Why is SYSIDMS override ignored ?

    Posted Sep 21, 2017 08:49 AM

    Hello all,

    I'm trying to override the Journal  DMCL date/time via JRNLDTS in DD SYSIDMS in my CV startup proc, and the override is reflected back in WTO, but I still get a mismatch :

     

    IDMS DC016109 XTIOT disabled for dynamic allocation
    SYSIDMS parms --> JRNLDTS=2017-09-21-10.46.32.903427
    IDMS DC390009 V3190 STARTING IDMS-CV/DC INITIALIZATION - R19.0 SP 4
    IDMS DC391511 V3190 Lock Manager for Warmstart initialization Complete
    IDMS DC202001 V3190 Starting WARMSTART
    IDMS DC202027 V3190 Name/Date from DMCL on Journals different from Run Time DMC
    IDMS DC202028 V3190 Run Time DMCL Name: GLBLDMCL , Compile Date/Time: 2017-09-21-10.46.32.903427
    IDMS DC202029 V3190     Journal DMCL Name: GLBLDMCL , Compile Date/Time: 2017-02-10-15.32.27.361250
    IDMS DC391008 V3190 WARMSTART Failure - IOSTATUS=3027

     

    (sorry for the truncation but I think its visible there).

     

    I'm happy to force the later DMCL in there, this is a Test v19 SP0 IDMS which I am playing with, so the data in the journals is not required for my CDC extraction yet.

     

    I couldn't find anything on a search - does anyone have any ideas on why my override isn't used ? I still have the previous DMCL saved but I would like to use the new one I generated (new schema added).

     

    (Apologies in advance, I am a relative newbie to IDMS so it's possible that my use of phrases and general understanding of the concepts is less than perfect !!)

     

    Thanks, Tony



  • 2.  Re: Why is SYSIDMS override ignored ?
    Best Answer

    Broadcom Employee
    Posted Sep 21, 2017 09:21 AM

    Hi Tony,

    You need to specify the Journal Datetime stamp as found in the Disk Journal as shown in the DC202029 message.

    In your case, this is  2017-02-10-15.32.27.361250

     

    So, change your JRNDTDS parameter into JRNLDTS=2017-02-10-15.32.27.361250



  • 3.  Re: Why is SYSIDMS override ignored ?

    Posted Sep 21, 2017 09:25 AM

    Hi Yves,

    Many thanks for replying. So my understanding of the function of JRNLDTS is flawed really - I thought I was forcing the DMCL to match my latest one, but really I am forcing in the earlier DMCL date ?

     

    I'll give that a go.

     

    best regards,

    Tony



  • 4.  Re: Why is SYSIDMS override ignored ?

    Broadcom Employee
    Posted Sep 21, 2017 09:39 AM

    from the SYSIDMS doc:

     

    JRNLDTS=yyyy-mm-dd-hh.mm.ss.nnnnnn

    This parameter provides a way to bypass a date time stamp mismatch problem between the DMCL and the journal files. The yyyy-mm-dd-hh.mm.ss.nnnnnn is the date time stamp on the journal file. This should only be used if you know that the reason for the mismatch will not cause a problem. Inappropriate use of this parameter may cause database corruption.



  • 5.  Re: Why is SYSIDMS override ignored ?

    Posted Sep 21, 2017 09:47 AM

    Thanks Brian and Yves - all up and running now.

    best regards,

    Tony