CA IDMS IUA EIUA

Expansion of the CALC Key

  • 1.  Expansion of the CALC Key

    Posted 05-24-2006 08:46 AM
    Hi,

    Currently, there is a need for us to expand the length of the CALC key from
    2 bytes to 7 bytes. We are quite new in IDMS and we have not done this
    before. Anyone can advise us on how to carry out this expansion. Is this
    any guide that we can refer to.

    Thks

    Rgds

    Lim


    WARNING: This communication is meant only for the addressee(s) named above and may contain information which is confidential and/or legally privileged. If you are not the named addressee(s), or the agent responsible for receiving and delivering this communication to the named addressee(s), this communication has been sent to you in error. If so, kindly notify the sender and delete the information immediately. Unauthorised dissemination, distribution, copying or reliance on this communication is prohibited and may attract criminal penalties.

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








    Normal

    Normal
    Re: [IDMSVENDOR-L] Expansion of the CALC Key
    "There can't be many records in the DB with only a 2 byte Calc Key. Unless
    of course Duplicates are allowed in which case I bet the Calc chains are
    pretty lengthy.

    If the record has no set connections and is as low a volume as I suspect
    and you have no experience of the utilities then just do it with a couple
    of COBOL programs - one to do an area sweep to a sequential file with the
    old subschema.Then format the area or erase them all and store them again
    with a second program with the new subschema.

    I wouldn't do this with large volumes of data but for little stuff it is
    efficient enough.

    If you do have large volumes of data with only a 2 byte Calc key then I
    think you have bigger problems than this.

    I knew someone once who spent a whole day trying to get a Restructure and
    Unload/reload right and it turned out there were only 3 80 byte records
    in the DB.

    Mit freundlichen Grüssen
    --------------------------------------------------------------------------------------
    Chris Trayler, IXD
    Bank Julius Bär & Co. AG
    Hohlstrasse 602, CH-8010 Zurich, Switzerland
    Telephone +41 (0) 58 887 43 32
    Christopher.Trayler@juliusbaer.com, www.juliusbaer.com
    --------------------------------------------------------------------------------------


    *****Disclaimer*****
    This message is for the addressee only and may contain confidential or privileged information. You must delete and not use it if you are not the intended recipient. It may not be secure or error-free. All e-mail communications to and from the Julius Baer Group may be monitored. Processing of incoming e-mails cannot be guaranteed. Any views expressed in this message are those of the individual sender. This message is for information purposes only. All liability of the Julius Baer Group and its entities for any damages resulting from e-mail use is excluded. US persons are kindly requested to read the important legal information presented at following URL: http://www.juliusbaer.com/maildisclaimer

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








    Normal

    Normal
    Re: [IDMSVENDOR-L] Expansion of the CALC Key
    "Hi,

    Currently, there is a need for us to expand the length of the CALC key
    from
    2 bytes to 7 bytes. We are quite new in IDMS and we have not done this
    before. Anyone can advise us on how to carry out this expansion. Is this
    any guide that we can refer to.


    I believe the correct order of events would be to perform a restructure of
    the changing record(several steps in itself), followed by an unload/reload
    of the database area in which the restructured record resides.

    chris hoelscher


    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.

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








    Normal

    Normal
    Re: Expansion of the CALC Key
    "Look at the Database Administration Guide chapter 32.4.3


    with kindest regards,

    Ulens Ivan, Cegeka NV
    DBA VCST Industrial Products
    Tel. +32 (0)11 670 240
    Fax +32 (0)11 670 553

    Woo Liew <woo_liew.lim@CPF.GOV.SG> 2006-05-24 12:46 >>>
    Hi,

    Currently, there is a need for us to expand the length of the CALC key from
    2 bytes to 7 bytes. We are quite new in IDMS and we have not done this
    before. Anyone can advise us on how to carry out this expansion. Is this
    any guide that we can refer to.

    Thks

    Rgds

    Lim


    WARNING: This communication is meant only for the addressee(s) named above and may contain information which is confidential and/or legally privileged. If you are not the named addressee(s), or the agent responsible for receiving and delivering this communication to the named addressee(s), this communication has been sent to you in error. If so, kindly notify the sender and delete the information immediately. Unauthorised dissemination, distribution, copying or reliance on this communication is prohibited and may attract criminal penalties.

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








    Normal

    Normal
    Expansion of the CALC Key
    "Hi,

    Currently, there is a need for us to expand the length of the CALC key from
    2 bytes to 7 bytes. We are quite new in IDMS and we have not done this
    before. Anyone can advise us on how to carry out this expansion. Is this
    any guide that we can refer to.

    Thks

    Rgds

    Lim


    WARNING: This communication is meant only for the addressee(s) named above and may contain information which is confidential and/or legally privileged. If you are not the named addressee(s), or the agent responsible for receiving and delivering this communication to the named addressee(s), this communication has been sent to you in error. If so, kindly notify the sender and delete the information immediately. Unauthorised dissemination, distribution, copying or reliance on this communication is prohibited and may attract criminal penalties.

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








    Normal

    Normal
    Re: out of the closet: how to capture CPU effectiveness stats
    "I have been running the CPU Effectiveness Culprit program for our MT
    systems under Release 12, 14 and 16. (we skipped 15). If your Culprit
    program no longer works, here are a number of points to check.

    1) sysgen STATISTICS INTERVAL OFF NOLINE TASK COLLECT (no need to
    WRITE)

    2) Change the column start position for ENTC-LIT to reflect the
    following ENTC message prompt (add 1 to column 49)

    3) ENTC-VALUE literal value is case sensitive to perform the
    matching test

    V20 Release 16.0 SP3 >>> JIS Production CV <<< Enter next task:
    ^
    |
    starts in column 49

    REC ENTC-LIT 050 016

    010 ENTC-VALUE 'Enter next task:'

    017010 IF ENTC-LIT NE ENTC-VALUE DROP


    Regards,
    Paul Mak
    Email : mailTo:paul.mak@eds.com
    Phone : +61 2 9012 5434
    Mobile : +61 419 398 116
    Fax : +61 2 9312 6380
    Mail : EDS Australia South Applications Delivery Unit
    Level 3, 36-46, George Street, Burwood, NSW 2134, Australia