CA IDMS IUA EIUA

Expand all | Collapse all

I think this RSTT will work

  • 1.  I think this RSTT will work

    Posted 08-28-2009 11:02 AM
    We need a restructure before doing an unload/reload to enlarge a Calc Key. =
    The key fields are getting a 2 digit year inserted in front of them that w=
    ill become part of the new Calc key. The restructure will insert a new fie=
    ld with a value of 00 but it would be nice to copy a year-field found in ea=
    ch of the record instances instead.

    *
    * The generated RSTT;
    *
    IDMSRSTT BUFSIZE=3D(1500,1500) OLD WRFOTO
    IDMSRSTT RECNAME=3DWRHEDR
    IDMSRSTT SETPTR=3DALL
    IDMSRSTT FIELD=3D(2CL1'0',1,2,NEW) INIT WRHEDR-WARRANT-YR <- the new field,=
    initialized to 00
    IDMSRSTT FIELD=3D(1,3,8) COPY WRHEDR-WARRANT-NO
    IDMSRSTT FIELD=3D(9,11,9) COPY WRHEDR-EIEMPL-SSAN
    IDMSRSTT FIELD=3D(18,20,9) COPY WRHEDR-HRCSTC-CODE
    IDMSRSTT FIELD=3D(27,29,15) COPY WRHEDR-LNAME
    IDMSRSTT FIELD=3D(42,44,15) COPY WRHEDR-FNAME
    IDMSRSTT FIELD=3D(57,59,1) COPY WRHEDR-MNAME
    IDMSRSTT FIELD=3D(58,60,5) COPY WRHEDR-NAME-SFX
    IDMSRSTT FIELD=3D(63,65,24) COPY WRHEDR-PAYNAME
    IDMSRSTT FIELD=3D(87,89,3) COPY WRHEDR-HRPSTN-AGENCY
    IDMSRSTT FIELD=3D(90,92,3) COPY WRHEDR-HRPSTN-APPROP
    IDMSRSTT FIELD=3D(93,95,4) COPY WRHEDR-HRPSTN-ORG
    IDMSRSTT FIELD=3D(97,99,5) COPY WRHEDR-HRPSTN-HRCLSC
    IDMSRSTT FIELD=3D(102,104,3) COPY WRHEDR-HRPSTN-NUMBER
    IDMSRSTT FIELD=3D(105,107,1) COPY WRHEDR-HRPSTN-REPLACE
    IDMSRSTT FIELD=3D(106,108,2) COPY WRHEDR-WARR-CC
    IDMSRSTT FIELD=3D(108,110,2) COPY WRHEDR-WARR-YY
    ...

    *
    * The possibly clever RSTT
    *
    IDMSRSTT BUFSIZE=3D(1500,1500) OLD WRFOTO
    IDMSRSTT RECNAME=3DWRHEDR
    IDMSRSTT SETPTR=3DALL
    IDMSRSTT FIELD=3D(108,1,2) COPY WRHEDR-WARR-YY <- the new field, po=
    pulated with WRHEDR-WARR-YY
    IDMSRSTT FIELD=3D(1,3,8) COPY WRHEDR-WARRANT-NO
    IDMSRSTT FIELD=3D(9,11,9) COPY WRHEDR-EIEMPL-SSAN
    IDMSRSTT FIELD=3D(18,20,9) COPY WRHEDR-HRCSTC-CODE
    IDMSRSTT FIELD=3D(27,29,15) COPY WRHEDR-LNAME
    IDMSRSTT FIELD=3D(42,44,15) COPY WRHEDR-FNAME
    IDMSRSTT FIELD=3D(57,59,1) COPY WRHEDR-MNAME
    IDMSRSTT FIELD=3D(58,60,5) COPY WRHEDR-NAME-SFX
    IDMSRSTT FIELD=3D(63,65,24) COPY WRHEDR-PAYNAME
    IDMSRSTT FIELD=3D(87,89,3) COPY WRHEDR-HRPSTN-AGENCY
    IDMSRSTT FIELD=3D(90,92,3) COPY WRHEDR-HRPSTN-APPROP
    IDMSRSTT FIELD=3D(93,95,4) COPY WRHEDR-HRPSTN-ORG
    IDMSRSTT FIELD=3D(97,99,5) COPY WRHEDR-HRPSTN-HRCLSC
    IDMSRSTT FIELD=3D(102,104,3) COPY WRHEDR-HRPSTN-NUMBER
    IDMSRSTT FIELD=3D(105,107,1) COPY WRHEDR-HRPSTN-REPLACE
    IDMSRSTT FIELD=3D(106,108,2) COPY WRHEDR-WARR-CC
    IDMSRSTT FIELD=3D(108,110,2) COPY WRHEDR-WARR-YY
    ...
    "
    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: I think this RSTT will work
    "
    I have done this in the past and in my experience, the best approach would be a combination:

    IDMSRSTT BUFSIZE=(1500,1500) OLD WRFOTO
    IDMSRSTT RECNAME=WRHEDR
    IDMSRSTT SETPTR=ALL
    IDMSRSTT FIELD=(2CL1'0',1,2,NEW) INIT WRHEDR-WARRANT-YR <- create the new fld & init to 00
    IDMSRSTT FIELD=(108,1,2) COPY WRHEDR-WARR-YY <- populate the new fld WRHEDR-WARR-YY
    IDMSRSTT FIELD=(1,3,8) COPY WRHEDR-WARRANT-NO
    IDMSRSTT FIELD=(9,11,9) COPY WRHEDR-EIEMPL-SSAN
    IDMSRSTT FIELD=(18,20,9) COPY WRHEDR-HRCSTC-CODE
    IDMSRSTT FIELD=(27,29,15) COPY WRHEDR-LNAME
    IDMSRSTT FIELD=(42,44,15) COPY WRHEDR-FNAME
    IDMSRSTT FIELD=(57,59,1) COPY WRHEDR-MNAME
    IDMSRSTT FIELD=(58,60,5) COPY WRHEDR-NAME-SFX
    IDMSRSTT FIELD=(63,65,24) COPY WRHEDR-PAYNAME
    IDMSRSTT FIELD=(87,89,3) COPY WRHEDR-HRPSTN-AGENCY
    IDMSRSTT FIELD=(90,92,3) COPY WRHEDR-HRPSTN-APPROP
    IDMSRSTT FIELD=(93,95,4) COPY WRHEDR-HRPSTN-ORG
    IDMSRSTT FIELD=(97,99,5) COPY WRHEDR-HRPSTN-HRCLSC
    IDMSRSTT FIELD=(102,104,3) COPY WRHEDR-HRPSTN-NUMBER
    IDMSRSTT FIELD=(105,107,1) COPY WRHEDR-HRPSTN-REPLACE
    IDMSRSTT FIELD=(106,108,2) COPY WRHEDR-WARR-CC
    IDMSRSTT FIELD=(108,110,2) COPY WRHEDR-WARR-YY
    ...

    Regards,
    ...................Al

    Alan R. Dicken
    Citigroup Enterprise Systems -
    Data Base Administration
    (718) 248-3458


  • 2.  Re:I think this RSTT will work

    Posted 08-28-2009 11:02 AM
    We need a restructure before doing an unload/reload to enlarge a Calc Key. The key fields are getting a 2 digit year inserted in front of them that will become part of the new Calc key. The restructure will insert a new field with a value of 00 but it would be nice to copy a year-field found in each of the record instances instead.

    *
    * The generated RSTT;
    *
    IDMSRSTT BUFSIZE=(1500,1500) OLD WRFOTO
    IDMSRSTT RECNAME=WRHEDR
    IDMSRSTT SETPTR=ALL
    IDMSRSTT FIELD=(2CL1'0',1,2,NEW) INIT WRHEDR-WARRANT-YR <- the new field, initialized to 00
    IDMSRSTT FIELD=(1,3,8) COPY WRHEDR-WARRANT-NO
    IDMSRSTT FIELD=(9,11,9) COPY WRHEDR-EIEMPL-SSAN
    IDMSRSTT FIELD=(18,20,9) COPY WRHEDR-HRCSTC-CODE
    IDMSRSTT FIELD=(27,29,15) COPY WRHEDR-LNAME
    IDMSRSTT FIELD=(42,44,15) COPY WRHEDR-FNAME
    IDMSRSTT FIELD=(57,59,1) COPY WRHEDR-MNAME
    IDMSRSTT FIELD=(58,60,5) COPY WRHEDR-NAME-SFX
    IDMSRSTT FIELD=(63,65,24) COPY WRHEDR-PAYNAME
    IDMSRSTT FIELD=(87,89,3) COPY WRHEDR-HRPSTN-AGENCY
    IDMSRSTT FIELD=(90,92,3) COPY WRHEDR-HRPSTN-APPROP
    IDMSRSTT FIELD=(93,95,4) COPY WRHEDR-HRPSTN-ORG
    IDMSRSTT FIELD=(97,99,5) COPY WRHEDR-HRPSTN-HRCLSC
    IDMSRSTT FIELD=(102,104,3) COPY WRHEDR-HRPSTN-NUMBER
    IDMSRSTT FIELD=(105,107,1) COPY WRHEDR-HRPSTN-REPLACE
    IDMSRSTT FIELD=(106,108,2) COPY WRHEDR-WARR-CC
    IDMSRSTT FIELD=(108,110,2) COPY WRHEDR-WARR-YY
    ...

    *
    * The possibly clever RSTT
    *
    IDMSRSTT BUFSIZE=(1500,1500) OLD WRFOTO
    IDMSRSTT RECNAME=WRHEDR
    IDMSRSTT SETPTR=ALL
    IDMSRSTT FIELD=(108,1,2) COPY WRHEDR-WARR-YY <- the new field, populated with WRHEDR-WARR-YY
    IDMSRSTT FIELD=(1,3,8) COPY WRHEDR-WARRANT-NO
    IDMSRSTT FIELD=(9,11,9) COPY WRHEDR-EIEMPL-SSAN
    IDMSRSTT FIELD=(18,20,9) COPY WRHEDR-HRCSTC-CODE
    IDMSRSTT FIELD=(27,29,15) COPY WRHEDR-LNAME
    IDMSRSTT FIELD=(42,44,15) COPY WRHEDR-FNAME
    IDMSRSTT FIELD=(57,59,1) COPY WRHEDR-MNAME
    IDMSRSTT FIELD=(58,60,5) COPY WRHEDR-NAME-SFX
    IDMSRSTT FIELD=(63,65,24) COPY WRHEDR-PAYNAME
    IDMSRSTT FIELD=(87,89,3) COPY WRHEDR-HRPSTN-AGENCY
    IDMSRSTT FIELD=(90,92,3) COPY WRHEDR-HRPSTN-APPROP
    IDMSRSTT FIELD=(93,95,4) COPY WRHEDR-HRPSTN-ORG
    IDMSRSTT FIELD=(97,99,5) COPY WRHEDR-HRPSTN-HRCLSC
    IDMSRSTT FIELD=(102,104,3) COPY WRHEDR-HRPSTN-NUMBER
    IDMSRSTT FIELD=(105,107,1) COPY WRHEDR-HRPSTN-REPLACE
    IDMSRSTT FIELD=(106,108,2) COPY WRHEDR-WARR-CC
    IDMSRSTT FIELD=(108,110,2) COPY WRHEDR-WARR-YY
    ...
    "
    IDMS Public Discussion Forum
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP
    IDMS-L@LISTSERV.IUASSN.COM
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    finding all OBTAINING USING .....
    "when migrating from 15 to 17 (might have also happened had me migrated to
    16) - we noted that all subsequent of cobol code ""OBTAIN .... USING"" now
    requires a terminating period or semicolon (to enforce only one character
    string to be interpreted as the sort-key element name. we have addressed
    this as each program was compiled when a change is made.

    we recently picked up a 3rd party productivity tool (i am really not sure
    which one) - and our developers want to compile EVERY program abd are
    complaining about the number of precompiles failing due to this issue -
    and want all such programs pre-identified

    has anyone written a program/script to examine program source repositories
    looking for OBTAIN...USING .... DML? (and more importantly, willing to
    share?)

    thanks,
    Chris Hoelscher
    Senior IDMS & DB2 Database Administrator
    Humana Inc
    502-476-2538
    choelscher@humana.com

    you only need to test the programs that you want to work correctly




    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 3rd-party providers forum
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    SMTP
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    IDMSVENDOR-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    finding all OBTAINING USING .....
    "when migrating from 15 to 17 (might have also happened had me migrated to
    16) - we noted that all subsequent of cobol code ""OBTAIN .... USING"" now
    requires a terminating period or semicolon (to enforce only one character
    string to be interpreted as the sort-key element name. we have addressed
    this as each program was compiled when a change is made.

    we recently picked up a 3rd party productivity tool (i am really not sure
    which one) - and our developers want to compile EVERY program abd are
    complaining about the number of precompiles failing due to this issue -
    and want all such programs pre-identified

    has anyone written a program/script to examine program source repositories
    looking for OBTAIN...USING .... DML? (and more importantly, willing to
    share?)

    thanks,
    Chris Hoelscher
    Senior IDMS & DB2 Database Administrator
    Humana Inc
    502-476-2538
    choelscher@humana.com

    you only need to test the programs that you want to work correctly




    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: finding all OBTAINING USING .....
    "Not sure why you would need anything special to do the search. If you program source is in PANVALET, why couldn't you do a search for the string you want using a PANVALET utility? Same thing if the source libraries are in PDS format, simply use the IBM standard program ISRSUPC.

    Now, if you want to also append the semicolon, then you could use File Aid or Macro 4 utilities if you have them.

    Dan Miley
    Lockheed Martin