Re: Year 2000

[ConnectY2K@xxxxxxx]

James:
you recommend Logical file views haveyou thought of the performance hits
 here?
Is this better worse or equal to the alterate soultion(s)?

Yes this is at least wqual to a dual project or system overhaul

In a message dated 97-06-07 07:43:14 EDT, you write:

<< DAsmussen@aol.com wrote:
 > 
 > Doing a Y2K conversion AND converting to ILE is a bit ambitious, don't you
 > think?  It was my understanding that there were some performance problems
 > with the date data types at one point, is this still the case?
 
 I agree.  One major overhaul at a time. please.......
 
 The performance problems may be addressed in the next version, who
 knows.
 Think about it though, to support date date types, IBM was faced with
 either handling the conversion within each program product or at the
 data base level.  (the products always gets the result)
 
 The only way we can think of to get around it is to create new logicals
 which do not include the date fields if they are not being used in a
 particular program.  Sort of like pulling the input specs for unused
 fields on a S/3 when you were stuck with a machine which only had 16k to
 work with and the program went into overlays.
 
 Because of backlog and time contraints, we bit the bullet and stuck with
 7,0 packed dates for everthing except birthdates.  We are at 3.1 and the
 *date command processor variable returns a 7,0 cyymmdd variable so we
 decided to stick with that.  This got us y2k "compliant".  We're not
 real happy with the decision. Technically speaking, date data types are
 not that hard to work around in RPG/400, but all the files were already
 7,0 packed date formated.
 
 We have reworked our date routines so that when a 7,0 cyymmd date comes
 in it is Z-ADDed to a 8,0 field then we add/subtract 1900 from the year
 giving us yyyymmdd.  Since we use standard /COPY routines for all date
 manipulation, we used the QUSRTOOL SCNALLSRC (Scan all source) to get a
 hit list of the programs using the routines.
 
 For those shops not getting the benefits of ILE reusable code, /COPY is
 the next best thing going.
 If you are a RPG/400 shop and not using /COPY, you might want to give it
 some thought.  These routines could make the starting point for service
 programs in the future.
 
 Just my .02
 -- 
 ===================================================
 James W. Kilgore >>

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *