CA IDMS IUA EIUA

Expand all | Collapse all

CA Tuesday Tip: (CA IDMS) DB347015 on DMCL NEW COPY

  • 1.  CA Tuesday Tip: (CA IDMS) DB347015 on DMCL NEW COPY

    Posted 12-04-2012 03:42 AM
    CA IDMS Tuesday Tip by Brian Brendlinger, Principal Support Engineer for December 4, 2012.

    A DCMT VARY DMCL NEW COPY may result in this error message:

    DB347015 V56 T1 Error detected in DMCL AUDIT routine

    The most likely cause of this messages is that the old and new DMCLs were not compiled with the same release of CA-IDMS.

    Note that this has nothing to do with the release under which CA-IDMS is running. In theory, you could vary a DMCL compiled under r17.0 to another DMCL compiled under r17.0 even if the CV is running under r18.0. What's important is that the releases under which the two DMCLs were compiled are the same.

    The DB347015 message itself indicates only that there was an error. Further information in the form of a hard-coded message text is returned to the LTERM on which the DCMT command was issued. For example:

    Error Auditing/Building the new DMCL. BLDR returned a status of 04. See Log.
    Release Number or OPSYS ID. changed between current DMCL and New DMCL.


  • 2.  RE: [Tuesday Tips] CA Tuesday Tip: (CA IDMS) DB347015 on DMCL NEW COPY

    Posted 12-04-2012 10:24 AM
    I have suggested previously (and will do so again) is that as part of your upgrade to a new release, after you bring up the CV under the new release cleanly for the first time then shutdown the CV, generate the DMCL in local mode – then bring up the CV again with the DMCL now generated under the current release – you certainly DON’T want to be in the position of having to shut down the CV in the middle of the day so that a critical change to the DMCL can be made ….. (wouldn’t hurt to hang on to the old DMCL load module just in case you have to revert …)

    Chris hoelscher
    Technology Architect | Database Infrastructure Services
    Technology Solution Services
    [Description: Description: cid:image001.png@01CD13D7.1A57CAF0]
    123 East Main Street |Louisville, KY 40202
    choelscher@humana.com
    Humana.com
    Keeping CAS and Metavance safe for all HUMANAty

    From: CA IDMS (IUA EIUA) Global User Community [mailto:CommunityAdmin@communities-mail.ca.com]
    Sent: Tuesday, December 04, 2012 3:42 AM
    To: mb.98922805.99779556@myca-email.ca.com
    Subject: [Tuesday Tips] CA Tuesday Tip: (CA IDMS) DB347015 on DMCL NEW COPY

    CA IDMS Tuesday Tip by Brian Brendlinger, Principal Support Engineer for December 4, 2012.

    A DCMT VARY DMCL NEW COPY may result in this error message:

    DB347015 V56 T1 Error detected in DMCL AUDIT routine

    The most likely cause of this messages is that the old and new DMCLs were not compiled with the same release of CA-IDMS.

    Note that this has nothing to do with the release under which CA-IDMS is running. In theory, you could vary a DMCL compiled under r17.0 to another DMCL compiled under r17.0 even if the CV is running under r18.0. What's important is that the releases under which the two DMCLs were compiled are the same.

    The DB347015 message itself indicates only that there was an error. Further information in the form of a hard-coded message text is returned to the LTERM on which the DCMT command was issued. For example:

    Error Auditing/Building the new DMCL. BLDR returned a status of 04. See Log.
    Release Number or OPSYS ID. changed between current DMCL and New DMCL.
    Posted by:ian_hill
    --
    CA Communities Message Boards
    99782096
    mb.98922805.99779556@myca-email.ca.com<mailto:mb.98922805.99779556@myca-email.ca.com>
    https://communities.ca.com


    The information transmitted is intended only for the person or entity to which it is addressed
    and may contain CONFIDENTIAL material. If you receive this material/information in error,
    please contact the sender and delete or destroy the material/information.