STL Time Machine Report #8 - 1998-02-18 Here's a time machine tip, although it may be more appropriate for IBM Mainframe applications that for other platforms. There are several different application areas testing in the Time Machine in the current phase. I was not following their efforts because I was preoccupied with my own application. My project leader described an interesting difference in the approaches. One other group built their job schedules and managed all their testing with JCL overrides. They were ready before we were, but many of their tests didn't work because JCL overrides were not entered properly, or weren't changed for each test date. In other words, their testing required constant manual intervention, and a few tests didn't work and had to be repeated. In contrast, we built special jobs into our schedule to initialize the environment for each test, build required test data, et cetera. This included special programs, and was partially required for the various tools we used to create realtime CICS data. We had more startup problems, but our tests run pretty much automated, with very little manual intervention. A good test suite should be repeatable, and should be run several times. Once we got into the groove we simply monitor the test schedule to see that everything is happening on time (and there is some spare time to correct problems if they occur). Then run the batch schedule automatically. We print out the test results and start reviewing them. It may be helpful to automate as much of the test execution as possible. OS/VS COBOL I already posted this in c.s.y2k, but someone asked if the OS/VS COBOL compiler would still work after rollover. I spent about a half-hour playing with this, and basically the compiler doesn't break and the compiled programs still return correct dates with 2-digit years, at least for 01/01/2000. I haven't tried any other dates yet in the Time Machine. But it prints "JAN 1, 1900" on the compile listing, and it returns the bad date for DATE-COMPILED. This is a 1982 compiler, PP 5740-CB1 Release 2.4 of IBM OS/VS COBOL. Don't let your maintenance fall that far behind. IBM says it's only Y2K-OK if you run it with Language Environment for MVS. Year 2000 in the News Y2K was mentioned again in the Kiplinger Washington Letter, dated Feb 13, 1998. It's $76 for one year (52 issues). Call 800-544-0155 or sub.services@kiplinger.com. They have a rather stern copyright notice: "Quotation for political or commercial use is not permitted. Duplicating an entire issue for sharing with others, by any means, is illegal". Goody, I think I can legally quote a portion of their comments on Y2K. Remember that their terse style is intended for non-technical business managers. Here are some Y2K quotes: "Check your building and equipment, not just computer networks. There are computerized maintenance schedules embedded in machinery. No telling how many are in your office or plant. "Among things to look into: Heating & cooling systems. Boilers. Electronic locks. Elevators. Fax and copy machines. Alarm systems. Automatic lighting. Postal machines & scales. Assembly-line equipment. Ask manufacturers if their stuff is 'Y2K-compliant.' Get it in writing. "Also make sure your bank is fixing its year-2000 computer kinks and will be ready on time. If not, may affect records of loan payments, the posting of interest income to your account and even the use of ATMs. "Don't be afraid to ask...request that the bank reply in writing. If it won't answer or offers only a tepid response, find another bank." End of quote. They also mention the Federal Reserve fining the Georgia bank. There's nothing in here you don't already know, but this is going out to businessmen, not technical types. It may do some good. On Monday, 16 Feb. 1998, the St. Louis Post-Dispatch published a business article titled "Utilities zero in on Year 2000 Problems" by Virginia Baldwin Hick. It tends to put a happy face on the problem, but there are quotes from several electric utility people (the Electric Power Research Institute), and it seems that the local utility, AmerenUE (formerly Union Electric) is working on the problem and inventorying their embedded systems. I don't know if this story is available on their webpage yet (it's too long for me to quote), but there is a URL and a discussion forum, so I'll post it here: http://www.stlnet.com/postnet/forums/year2000.nsf This website includes previous Y2K articles published by the St. Louis Post-Dispatch. Miscellaneous I had lunch with my friend who works for a Cleopatra award winner. His PHM is still ordering the programming department not to fix their Mainframe systems, because they're going to be replaced by Unix applications before 12/31/1999. Their current success with Unix is not very reassuring. The auditor's report is still a more closely guarded secret than the Iraqi bombing plans. My geek friend suspects his bosses have been reamed for their lack of Y2K preparedness. They're still ignoring IBM's warning that their release of IBM AIX is non-compliant. My geek friend is starting to wonder if he should move to the country and stock up on supplies. -- Arnold Trembley http://home.att.net/~arnold.trembley/ "Y2K? Because Centuries Happen!"