Y2K Testing and the mssdat.cbl Distribution

[CindyMCC]

I was wondering if we could share briefly the types of Y2K testing we have done with MIMS. At my company we are running MIMS 4.1.1 on AIX with Oracle 7.3.3 and 3.008-2q for the TP. <br><br>We have Y2K tested in three separate sessions. The first time we worked through our internal interfaces (checks and accounting are done outside of MIMS). The second sessions we set the date to 12/31/99 - entered December data in all streams (purchasing, materials, a/p, prod stats, maintenance, costing), allowed the box date and time to rollover during the night to 01/01/00, did the December and year-end closes (our fiscal year ends with the calendar year). We entered January data, tested maintenance scheuling, purchase order due dates, etc. <br><br>One thing we did not test was leap year processing - we had intended to work on it but ran out of time. Has anyone specifically checked leap year with MIMS?<br><br>And then of course we have this new distribution of mssdat.cbl. My intention is to hold it until the end of our application freeze period 3/1/00. What has everyone else done?

 

[Glen]

We did test leap year processing, including discounts(AP) and maint. scheduling across year end and feb 29. Unfortunately, we are using a different Y2K remediation scheme than nost other MIMS users <br>

 

[CCIOHIO]

Cindy,Glenn<br>
<br>
Anyone notice anything in the MST area? We are running MIMS 4.1 on an IBM 9000 series, OS390/MVS, CICS and DB2 5.0.<br>
<br>
We will be testing MSTs at the end of this month

 

[CindyMCC]

We really didn't find anything in our testing. We did install the identified work orders in the standard formal distributions made by Mincom when that information became available. There were none of those work orders in the maintenance area - most of it was in financials and AP.

 

[tbreinholt]

Cindy, <br>
<br>
We tested leap year on 3.013s as a part of our Y2K testing and it worked fine for Kennecott.

 

[Warren]

We did Y2K testing in all area's with transaction that spanded 1999 -2000 and also leap year. We are using 4.1 and found four problems. All were related to review screens when requesting data that included 1999 and 2000 data. Error message was start date after end date. Mincom was able to send fixes for all four.