Topic
  • No replies
stan0110
stan0110
3 Posts

Pinned topic How to migrate Cobol compiler option- YEARWINDOW to COBOL V5.1 version?

‏2013-12-02T16:48:10Z |

Dear All,

Our client want to migrate Cobol version from Enterprise Cobol for z/OS V3.2 to COBOL V5.1 version.

and we found the COBOL compiler option - "YEARWINDOW" is Not Support in COBOL V5.1 version.

How could we migrate this Cobol version from V3.2 to V5.1? and for "YEARWINDOW" compiler option?

and for This "YEARWINDOW" compiler option NOT support, How action could we di in migrate?

and Whether for Cobol Application source need to change for Not support "YEARWINDOW" compiler option?

.

Any advice is welcome, Thanks.

.,

Stan Yang 

 

  • BillWoodger
    BillWoodger
    134 Posts

    Re: How to migrate Cobol compiler option- YEARWINDOW to COBOL V5.1 version?

    ‏2013-12-03T13:00:41Z  

    It depends on whether any of the source is making use of YEARWINDOW.

    If you still have dates with two-digit years in, you will need code or data changes.

    So, is any of the code actually using anything which relates to YEARWINDOW. Have you looked at the Migration guide?

  • Tom.Ross
    Tom.Ross
    21 Posts

    Re: How to migrate Cobol compiler option- YEARWINDOW to COBOL V5.1 version?

    ‏2013-12-03T22:54:56Z  

    It depends on whether any of the source is making use of YEARWINDOW.

    If you still have dates with two-digit years in, you will need code or data changes.

    So, is any of the code actually using anything which relates to YEARWINDOW. Have you looked at the Migration guide?

    Actually, the source could have 2-digfit year date logic that is completely unaffected by the YEARWINDOW option. 

    In fact, that is most likely the case, the YEARWINDOW option only affects IBM COBOL language such as:

    §DATE FORMAT   clause on data description entries
    §DATEVAL          intrinsic function
    §UNDATE     intrinsic function
    §YEARWINDOW  intrinsic function
    §

    These were rarely used COBOL features.  If your source does not have any of the above syntax then DATEPROC and YEARWINDOW compiler options will have no affect.