----- YEAR2000 CFORUM appended at 12:58:59 on 98/06/01 GMT (by 83464129 at EHONE Subject: Does COBOL for MVS V1.2 on MVS/ESA V4.3 return 4-digit year? Hello, A customer is running MVS/ESA V4.3 (not year-2000 ready). If he installs COBOL for MVS V1.2 (year-2000 ready) on his system and uses intrinsic functions, will he be able to obtain 4-digit year? He is asking this question because he wants to start the COBOL application migration without waiting for the MVS to OS/390 migration to complete. MVS/ESA V4.3 meets the target system requirement for COBOL for MVS V1.2, according to the installation manual. There is no mention that running COBOL for MVS V1.2 on a non year-2000 ready MVS system will result in any restricted functionality. So, my answer to the customer would likely be 'yes' but I just don't have a MVS/ESA V4.3 with COBOL for MVS V1.2 environment for me to verify (unless I convince my customer to install and test it out). Can anyone share your experience/knowledge? Thank you in advance! regards, Wee Heong (IBM Singapore) ----- YEAR2000 CFORUM appended at 16:39:01 on 98/06/02 GMT (by 83814093 at EHONE Subject: Isogon TICTOC Can anybody tell me where can I find technical information about ISOGON TICTOC (5620-BFV) (Redbooks, installation guide, user guide, etc). I need to know how the program work and any source of information will be very helpful. Thanks in advance, Rafael Echarren ----- YEAR2000 CFORUM appended at 17:18:31 on 98/06/02 GMT (by DHONDY at PK705VM Subject: Isogon TICTOC Ref: Append at 16:39:01 on 98/06/02 GMT (by 83814093 at EHONE) Have you tried their website at http://www.isogon.com NOSHIR DHONDY ----- YEAR2000 CFORUM appended at 11:23:18 on 98/06/04 GMT (by NL5AAB09 at ELINK Subject: DCAF >< Year2000 Ref: Append at 09:00:26 on 98/05/26 GMT (by 62479255 at EHONE) Hello, We have the same question, please give some clarification, because we need to solve the Y2000 problem with DCAF. regards, Peter Smit This append was created on the External IBMLink system by Peter Smit, Project Manager OS/390 and Systems Management ABN AMRO Bank Netherlands ----- YEAR2000 CFORUM appended at 19:12:55 on 98/06/04 GMT (by SAKC3II at ELINK) Subject: Year2000 abd Back Again We built our lpar and were ready for THE TEST! The lpar was shut down totally (through $PJES2 and Z EOD). All volumes were then placed online to my production system and full volume backups were run. The volumes were then varied offline and the lpar was reipled with a system date of 2000.155. The ipl went successfully but of course we had a few problems with some of our ISV products. When the test was done we shut down again, ran quick inits on the volumes (so they could be varied online to production) and did full volume restores. Now, when I ipled the lpar with the current date (using SIMETR in the CLOCK member) some interesting things happened. First I had 001 $HASP483 JES2 JOB QUEUE ERROR -- REPLY 'Y' TO REBUILD OR 'N' TO TERMINATE JES2 which I allowed to rebuild. Had a number of $DIST catastrophic errors - I can maybe understand. The odd thing, and the reason for this post, is that I can still see all the jobs that we ran while on the year2000 date. SDSF still shows the year 2000. I can think of three datasets that could be involved: HASPACE, Checkpoint, and SDSF HASPINDX. Reviewing the backup and restore jobs, all the volumes these are on were successfully restored. Any ideas why I'm Back to the Future? Alan Schwartz John Alden Systems Company. ----- YEAR2000 CFORUM appended at 23:55:20 on 98/06/04 GMT (by Y2KTSC3 at SJEVM5 Subject: Does COBOL for MVS V1.2 on MVS/ESA V4.3 return 4-digit year? Ref: Append at 12:58:59 on 98/06/01 GMT (by 83464129 at EHONE) >A customer is running MVS/ESA V4.3 (not year-2000 ready). If he installs >COBOL for MVS V1.2 (year-2000 ready) on his system and uses intrinsic >functions, will he be able to obtain 4-digit year? Yes! The century has been available on MVS since XA days. COBOL for MVS & VM programs had full functionality even on MVS 3.1.3! Year 2000 Technical Support Center ----- YEAR2000 CFORUM appended at 00:31:29 on 98/06/05 GMT (by Y2KTSC3 at SJEVM5 Subject: Trying MLE Ref: Append at 08:11:57 on 98/05/14 GMT (by 83816326 at EHONE) > It means you need to have VA COBOL MLE and VA PLI MLE products > installed in order to try MLE advantages, but it is difficult to > say that they must have the products before see some testing. > Please, do you Know if there is a posibility to simulate > the use of this products before to buy them? I know that it is > imposible to get them in demo. You cannot test MLE functionality without the VA MLE product installed on 390 platforms. You can buy it and return it in 60 days if you don't like it. You can buy the workstation compilers and try it out for a lot less money. Both VisualAge PL/I and VisualAge COBOL come with MLE in the base product for Windows and OS/2. Year 2000 Technical Support Center ----- YEAR2000 CFORUM appended at 10:28:40 on 98/06/05 GMT (by GBCAGE94 at ELINK Subject: Year2000 abd Back Again Ref: Append at 19:12:55 on 98/06/04 GMT (by SAKC3II at ELINK) Alan, What products did you use to perform your restore and what options did you use? Some products default restore options (DFDSS and DFSMSdss are examples) will restore a dataset to its existing allocation (size, DCB, CCHH etc) but will only restore physical data in the dataset that it considers to be used space (based upon VTOC information) For some datasets (and the JES HASPCKPT and HASPACE are examples), they have a used space value of 0. As such, the restore will pre-allocate them in the location they should be, but not restore the actuall data. The result is what you have seen. The quick initialize destroys the VTOC but not the actual data. Your restore restores the VTOC and reallocates the datasets but not the data. The result is an "empty" HASPCKPT is allocated over the data from the old HASPCKPT, the same for HASPACE. et viola - back to the future even though you have "wipped" the data This append was created on the External IBMLink system by Peter Gammage Email: peter_gammage@standardlife.com Standard Life Phone: (UK) 0131-245-7024 ----- YEAR2000 CFORUM appended at 12:45:32 on 98/06/05 GMT (by SAKC3II at ELINK) Subject: Year2000 abd Back Again Ref: Append at 10:28:40 on 98/06/05 GMT (by GBCAGE94 at ELINK) We used FDR for backup and restore functions. I have the person that built the jobs review FDR's options. Thanks. Alan Schwartz John Alden Systems Company. ----- YEAR2000 CFORUM appended at 15:56:54 on 98/06/05 GMT (by IL35816 at ELINK) Subject: Tool to get software and hardware inventory of PC's Ref: Append at 17:26:15 on 98/05/28 GMT (by JJACOB at TOROVM1) > One of the things I am involved in my customer is year2000. We nee > an inventory of the PC's. Is there a tool, preferible unser DOS > boot diskettes that will give me hardware and software inventory? I knew of such a product but now I cannot find the name. If you (or anyone else) are still interested please send me a note -- I know where I could track down the name and phone number. They MAY be out of business, however. Charles Mills Firesign Computer Company, San Francisco charlesm@firesign.com ----- YEAR2000 CFORUM appended at 11:56:36 on 98/06/08 GMT (by 83816326 at EHONE Subject: Trying MLE Hello, We are going to get the VA MLE product 60 days in order to try. Thank you very much ----- YEAR2000 CFORUM appended at 04:12:05 on 98/06/09 GMT (by AS106661 at ELINK Subject: EREP MVS V3 R5, problems with 'period from to' dates Ref: Append at 03:14:56 on 98/05/14 GMT (by MSHEWELL at SYDVMXA2) We have also noticed strange behaviour about the 1999/2000 boundary. When EREP is run on our system on 01/01/2000, with LOGREC data including both 99365 and 00001 items, the report period is printed out as FROM 001 00 TO 365 99 - i.e. EREP regards the period as being a whole century not just a day or so. Why is it not possible to make EREP work more sensibly? I understand that it is important to retain compatibility with existing use of EREP, but there are several ways in which the capabilities of EREP could be extended without introducing any unacceptable incompatibility, eg: (1) Introduce a new entry point name which accepts fully-qualified dates as input parameters, and calls the 'real' EREP one or more times to achieve the required effect. (2) Allow fully-qualified date parameters as an option. (3) Recognise the case START-DATE > END-DATE as a period crossing the millennium boundary, and process it as two date ranges. This append was created on the External IBMLink system by Centrelink ----- YEAR2000 CFORUM appended at 11:02:35 on 98/06/09 GMT (by GAD at KGNVMC) <1 Subject: EREP MVS V3 R5, problems with 'period from to' dates Ref: Append at 04:12:05 on 98/06/09 GMT (by AS106661 at ELINK2) >Why is it not possible to make EREP work more sensibly? A financial decision was made that the cost to make changes such as you suggest were not justified for a *free* service tool across a one-time window, when it could be "managed" by using appropriate control statements across the window. Greg Dyck MVS BCP Kernel and CURE Support ----- YEAR2000 CFORUM appended at 13:10:51 on 98/06/09 GMT (by AS103187 at ELINK ..... YEAR2000 CFORUM modified at 13:25:57 on 98/06/09 GMT (by AS103187 at ELINK Subject: EREP MVS V3 R5, problems with 'period from to' dates Ref: Append at 11:02:35 on 98/06/09 GMT (by GAD at KGNVMC) > A financial decision was made that the cost to make changes such as you > suggest were not justified for a *free* service tool across a one-time > window, when it could be "managed" by using appropriate control > statements across the window. Greg, this statement is probably fair enough, but, is this behaviour and ³ "management" documented? Also, Why do you think EREP is *free*? I believe ³ we (Customers) pay for it as part of our MVS ( or VM or VSE) licence. This append was created on the External IBMLink system by John Johnston phone +61 2 9902 5910 Technical Consultant (VTAM and NCP Sysprog) fax +61 2 9902 5111 Westpac Banking Corporation______________internet jjohnston@westpac.com.au Sydney, Australia ----- YEAR2000 CFORUM appended at 06:58:11 on 98/06/10 GMT (by SGONCHA at IBMUSM Subject: EREP MVS V3 R5, problems with 'period from to' dates Ref: Append at 13:10:51 on 98/06/09 GMT (by AS103187 at ELINK) The limitation for EREP is documented in a documentation APAR and is reference as part of the comments for the various EREP products in the IBM Year 2000 Readiness database. "Please see IR34644 information needed to produce EREP reports containing dates which include both December 31, 1999 and January 1, 2000." Sherry Goncharsky IBM Storage Systems Division, Tucson Year 2000 Representative From: Sherry Goncharsky ----- YEAR2000 CFORUM appended at 14:19:06 on 98/06/10 GMT (by MA00613 at EHONE7 Subject: Help with "clean management"... Scenario: the mainframe code was baselined, sent out, and returned remediated. It has been tested and has been put back into production. Now the question is: How can we keep the code Y2K-compliant? I'm hoping for any suggestions, sites, tips, and so on, that will help with the "clean management" effort. tia... Larry Kahm Heliotropic Systems, Inc. e-mail: kahml@ibm.net "to boldly break software that no one had thought to before..." ----- YEAR2000 CFORUM appended at 15:43:16 on 98/06/10 GMT (by Y2KTSC5 at SJEVM5 Subject: Trying MLE Ref: Append at 11:56:36 on 98/06/08 GMT (by 83816326 at EHONE) To order VA MLE, call 1-800-426-2255. You will automatically get 60 days free when you order the product. If you are interested in LE consulting services related to VisualAge 2000, the following can be provided: 1/2 or full day presentations that cover: Language Environment (LE) Overview Year 2000 Issues Migration Strategies Tools (Edge Portfolio Analyzer, ISOGON, CCCA, etc.) Compilers (PL/I and COBOL) Assembler Considerations For more detailed information on this service, please call 1-800-426-4968 and ask for the Year 2000 Technical Support Center and ask to speak to a representation in North America. Thank you. Year 2000 Technical Support Center (TSC5) ----- YEAR2000 CFORUM appended at 12:52:17 on 98/06/15 GMT (by 10008460 at ELINK Subject: S/390 9672 Processor Y2K presentation Ref: Append at 08:07:30 on 98/03/06 GMT (by TROWELL at WTSCPOK) Would you please send a copy to our IBM SE, Yoni Meron, email: jmeron@vnet.ibm.com or to my email: zion@ndsoft.com Thanks, Zion New Dimension Software ----- YEAR2000 CFORUM appended at 11:00:53 on 98/06/17 GMT (by STEVE at UKFSC) < Subject: GC28-1251 The most recent copy of GC28-1251 that I have was sent to me last September (the -07 level). Since then nothing has arrived. Before then they appeared at about 2 month intervals. Has this manual been superceded, or has my subscription expired, or what? Steve Swift ----- YEAR2000 CFORUM appended at 11:58:38 on 98/06/17 GMT (by ZOOT at KGNVMC) < Subject: Availability of IBM Y2K Guide (GC28-1251) Re: Steve Swift The latest edition of this manual was issued in 1998-February at the dash 08 level. If you have a subscription through SLSS, I believe you should have received a copy at that time. Updates have been less frequent simply because there has been less interest from other organizations to provide input. When I began this venture, this Guide was the only information IBM was providing on the subject. Needless to say, all platforms/products now provide more specific information on their own web sites. I have included some of this in the Guide, but most is beyond this book's scope. Hence we're unofficially on a twice-a-year update schedule. Steve: Please contact me at: zoot@us.ibm.com Don B. Pizzuto Y2K Information Development IBM Poughkeepsie, NY ----- YEAR2000 CFORUM appended at 09:45:41 on 98/06/18 GMT (by WONGCC at KULVM) Subject: Data Set Expiry for Non-Leap Year My customer has tested on their OS/390 R3 system and found out that it's possible to have an expiry of Julian date 366 for non-Leap Years. His question is when will the data set expire, if at all? Thanks. From: WongCC (IBM Malaysia) ----- YEAR2000 CFORUM appended at 20:04:06 on 98/06/18 GMT (by SGONCHA at IBMUSM Subject: Data Set Expiry for Non-Leap Year Ref: Append at 09:45:41 on 98/06/18 GMT (by WONGCC at KULVM) An expiration date of 99366 or 1999366 always means that this is a "never expire" dataset. There is a section with more details in the Year 2000 Planning Guide as well as in the different manuals explaining the expiration date parameters. Sherry Goncharsky SSD Year 2000 Representative sgoncha@us.ibm.com From: Sherry Goncharsky ----- YEAR2000 CFORUM appended at 20:08:48 on 98/06/18 GMT (by 62479255 at EHONE Subject: ??? Anything wrong with the JAVA Year2000 readiness application EXPANDED DELIMITED report? COLUMNAR & EXPANDED (regular) are OK. EXPANDED DELIMITED doesn't deliver me anything. I do get back an e-mail, but it's empty. Jan Vanbrabant, VANBRABJ at BRUVMIS1 ----- YEAR2000 CFORUM appended at 06:45:34 on 98/06/19 GMT (by WONGCC at KULVM) Subject: Data Set Expiry for Non-Leap Year Ref: Append at 20:04:06 on 98/06/18 GMT (by SGONCHA at IBMUSM51) 1999366 is a 'never expire' date, but what about after the millenium, ie 2001366, 2002366 etc? Are they also 'never expire' dates? If they aren't when exactly do they expire? Thanks. From: WongCC (IBM Malaysia) ----- YEAR2000 CFORUM appended at 09:59:11 on 98/06/19 GMT (by GBCAVZ15 at ELINK Subject: Guide to setting up a Y2K LPAR Ref: Append at 08:22:58 on 98/05/12 GMT (by SIANNYG at SYDVM1) Please send me a copy of your presentation . Thanks keith.ralph@sts.co.uk This append was created on the External IBMLink system by Keith Ralph - Severn Trent Systems ----- YEAR2000 CFORUM appended at 11:22:53 on 98/06/19 GMT (by WFARRELL at KGNVM Subject: Data Set Expiry for Non-Leap Year Ref: Append at 06:45:34 on 98/06/19 GMT (by WONGCC at KULVM) Reply-To: wfarrell at ibmusm10 Since you don't really have a Y2K question but a regular JCL or data set expiration question, you might get better answers in a different forum. Perhaps MVSESA FORUM or DFP FORUM on the internal conferences or MVSESA CFORUM on the external conferences. Walt Farrell Internet: wfarrell@us.ibm.com IBMMAIL: USIB3H89 ----- YEAR2000 CFORUM appended at 12:33:34 on 98/06/19 GMT (by Y2KTSC5 at SJEVM5 Subject: ??? Anything wrong with Ref: Append at 20:08:48 on 98/06/18 GMT (by 62479255 at EHONE) To report problems experienced with the Year 2000 Readiness Application, please contact the help desk in the United States at (919) 254-2100 or send e-mail to RTPAIX@us.ibm.com and mention "Year 2000 application" in the subject line. lnternal NOTES users can send notes to: RTP.AIXHELP@VM) When reporting a problem by phone or e-mail, please provide the following information: Your name and telephone number Your e-mail address Location (URL) the problem is occurring on Make of web browser (i.e. Netscape, IE) and browser version number Description of the problem by trying to answer the following questions: 1.What is the problem? 2.Is any message being displayed? 3.What message is appearing in the status line of the browser? 4.Does the problem occur EVERY time the application is accessed? 5.How long does it take before the error appears? 6.Have you been able to successfully use other Java applets? Year 2000 Technical Support Center (TSC5) ----- YEAR2000 CFORUM appended at 12:53:44 on 98/06/19 GMT (by E085209 at EHONE) Subject: Data Set Expiry for Non-Leap Year Ref: Append at 06:45:34 on 98/06/19 GMT (by WONGCC at KULVM) Hello, after the apar OY35005/OY56969 to MVS/ESA SP422, or MVS/ESA SP430 later, we cannot specify EXPDT=yy366 or yyyy366 if the year is really a non-leap year. (Of course, 99366 and 1999366 is an exeption.) (1)JCL allocation: IEF638I SPECIFIED NUMERIC EXCEEDS MAXIMUM ALLOWED IN THE parameter FIELD (2)Dynalloc: R15=x'000C' S99ERROR=x'035C' invalid parm specified in text unit Here is my understanding. Best regards, Shigeki Kimura, IBM Japan, Ltd. ----- YEAR2000 CFORUM appended at 20:56:25 on 98/06/19 GMT (by IL61424 at ELINK) Subject: acf/ncp 5.4 ep 1.9 acf/ssp 3.7 are y2k ready Just want to get this resolved once and for all: DOES ANY BODY KNOW IF ACF/NCP 5.4 AND EP 1.9 ARE CONSIDER FULL Y2K READY. IF NOT, WHAT LEVEL OF EACH IS. ALSO, i DO BELIVE THAT ACF/SSP 3.7 IS NOT Y2K READY AND YOU WILL HAVE TO MIGRATE TO 4.X. TRUE OR FALSE ? NOTE: THESE QUESTION WILL ALSO BE ASK IN THE NCP FORUM Next step to TalkLink Access ----- YEAR2000 CFORUM appended at 22:47:47 on 98/06/19 GMT (by 62457058 at EHONE Subject: acf/ncp 5.4 ep 1.9 acf/ssp 3.7 are y2k ready Ref: Append at 20:56:25 on 98/06/19 GMT (by IL61424 at ELINK) Have you tried the URL which, fortunately - although there may be other appends - appears in the first append in this CFORUM file - that is is just escaped the last "prune" - just a few days ago actually ? http://www.ibm.com/ibm/year2000/ I thought I'd try to get your answer from the database, but it seems the application is "under maintenance" right now :-( Chris Mason ----- YEAR2000 CFORUM appended at 10:39:59 on 98/06/22 GMT (by 72452115 at EHONE Subject: Guide to setting up a y2k LPAR Please be so kind and also send me a copy of your presentation if this is a vm file to heimann at franvm2 " PC file to heimann at ibmde ----- YEAR2000 CFORUM appended at 17:35:18 on 98/06/22 GMT (by KMPATTER at DETVM Subject: Y2K LPAR w no printer We are in the process of bulding a Y2K LPAR. It will not have a high speed printer associated with it. We plan to build a special JES2 sysout class for anything that is to be printed on a high speed printer and then offload it to tape. Our concern is reloading this data on our production JES2 spool. We don't want to do this because of the date. Any recommendations on how we can get JES2 to print this? ----- YEAR2000 CFORUM appended at 20:32:53 on 98/06/22 GMT (by MPERRY at PKMFGVM Subject: Y2K LPAR w no printer Ref: Append at 17:35:18 on 98/06/22 GMT (by KMPATTER at DETVMIC1) Is the Production LPAR on the same CPU as the Y2K LPAR? If so you can GEN the CHIPID as reconfigurable and switch the printer(s) between the two LPARs. We scheduled it so the the printer got switched to the Y2K LPAR during lunch time and off shift when the production LPAR was not using it heavily. Mike ----- YEAR2000 CFORUM appended at 07:56:17 on 98/06/23 GMT (by GBOAMU00 at ELINK Subject: Y2K LPAR w no printer Ref: Append at 17:35:18 on 98/06/22 GMT (by KMPATTER at DETVMIC1) Use an external writer to put it on tape - could be non-labelled. I put a sort of external writer on the CBT tape, but that won't do what you want without modification. In this case vanilla is best. This append was created on the External IBMLink system by David Cartwright Technical Consultant ++44 171 860 4438 dc@dcuk.demon.co.uk ----- YEAR2000 CFORUM appended at 08:30:20 on 98/06/23 GMT (by BENNG at EOSVM) < Subject: Guide to setting up a y2k LPAR Ref: Append at 10:39:59 on 98/06/22 GMT (by 72452115 at EHONE) Can you please send a copy of the above to BENNG @ NHBVM2 or BENNG @ IBMGB as appropriate. Thanks. Gordon Benn Global Services. ----- YEAR2000 CFORUM appended at 12:53:17 on 98/06/23 GMT (by KMPATTER at DETVM Subject: Y2K LPAR w no printer Ref: Append at 20:32:53 on 98/06/22 GMT (by MPERRY at PKMFGVM3) I tried this approach, but there are multiple printers on this chipid which are always busy. I'll try making this request again though. Thanks ----- YEAR2000 CFORUM appended at 23:13:03 on 98/06/23 GMT (by DKPEL10 at ELINK) Subject: Guide to setting up a y2k LPAR Ref: Append at 08:30:20 on 98/06/23 GMT (by BENNG at EOSVM) I would be grateful to receive a copy of your LPAR presentation, would you please mail it to me on jogvanbÃelektron.fo (JOGVANB (at) ELEKTRON.FO) Thanks Jogvan Baerentsen, P/F Elektron This append was created on the External IBMLink system by P/F Elektron ----- YEAR2000 CFORUM appended at 06:22:43 on 98/06/24 GMT (by 84867245 at EHONE Subject: Y2000 Database not working? Try to generate a software readiness report at wwwyr2k.raleigh.ibm.com for 5665-349, but this service seems to have a little problem? Does somebody know when this report capability will be again available??. Many thanks in advance Best regards Peter Ramisberger ----- YEAR2000 CFORUM appended at 13:11:41 on 98/06/25 GMT (by NIEDER at IBMDE) Subject: ctime and year2000 Hi, How can I write an ANSI C program, that can handle year2000 (and more) ? As far as I know ctime uses a long int starting from 1.1.1970. This will end in about year 2037/2038 ? Matthias nieder@de.ibm.com IBMDE(NIEDER) From: Matthias Nieder ----- YEAR2000 CFORUM appended at 18:24:56 on 98/06/25 GMT (by ZIEMBA at AUSVMR) Subject: ctime and year2000 Ref: Append at 13:11:41 on 98/06/25 GMT (by NIEDER at IBMDE) You can use C to write year 2000 compliant code. The structure known as tm has a field called tm_year which is defined as the number of years since 1900. When 2000 rolls around, it will return 100. So you can add 1900 to it and use 4 digit years in your code. Where people have gotten into trouble is when they use tm_year as a two-digit year (which works through 1999). And what you do with that value in subsequent data manipulation (like strcopy) can also get you into trouble. You are correct that current C compilers will "break" in January 2038. (That's when the long integer overflows). Hopefully, by that time either the compilers will have changed or most machines will have moved to a 64 or 128 bit architecture and that problem will be resolved. (I expect to retire long before then.) ----- YEAR2000 CFORUM appended at 20:35:31 on 98/06/26 GMT (by SAKC3II at ELINK) Subject: Coming Back Our lpar is built and we're planning the application testing. I asked if the group coordinating the testing thought they might, at some point, want to change the system date backwards. They're not sure; some say yes and some say no. I've got to plan for the no's. My initial thought is that, if the system date is set backwards, I would need to initialize and restore all my system volumes and then the apps people would need to recreate their files. But we ran a test and the thing that complained a little was CA1 and that only needed a not commonly used reply to a wto. I thought DB2 would have a problem with its' timestamps but it started without a hitch. What's the consenus? Does EVERTHING need to be disinfected or will OS390 take a licking and keep on ticking? Alan Schwartz John Alden Systems Company. ----- YEAR2000 CFORUM appended at 09:36:07 on 98/06/29 GMT (by 36601943 at EHONE Subject: Coming Back Ref: Append at 20:35:31 on 98/06/26 GMT (by SAKC3II at ELINK) Its not supported. There have been a number of appends in that past about winding the clock back. But think about it, MVS was never designed for it, it doesn't make sense with normal day to day running. In my universe the clock keeps going forward (and the entropy keeps increasing) and MVS follows that model. Try it with IMS and watch DBRC break, big time. Dougie Lawson, IBM Basingstoke, UK. http://gremlin.ts.uk.ibm.com ----- YEAR2000 CFORUM appended at 12:10:29 on 98/06/29 GMT (by GBCAGE94 at ELINK Subject: Coming Back Ref: Append at 09:36:07 on 98/06/29 GMT (by 36601943 at EHONE) Alan, I agree with Dougie. In all my planning for LPAR time machines, I have worked on the premise that: i) Prior to going into the future backup you DASD ii) When coming back from the future initialize all DASD and restore from your pre-time travel backup. We have done this a number of times. This append was created on the External IBMLink system by Peter Gammage Email: peter_gammage@standardlife.com Standard Life Phone: (UK) 0131-245-7024 ----- YEAR2000 CFORUM appended at 12:43:58 on 98/06/29 GMT (by SAKC3II at ELINK) Subject: Coming Back Ref: Append at 12:10:29 on 98/06/29 GMT (by GBCAGE94 at ELINK) I agree with you all. But I was asked, "What will happen if you don't restore your volumes?" I said this could happen or that could happen and when I tried it everything started beautifully. I guess I'll go with the "It's the clean way to start over". Alan Schwartz John Alden Systems Company. ----- YEAR2000 CFORUM appended at 20:33:45 on 98/06/29 GMT (by SGONCHA at IBMUSM Subject: Coming Back Ref: Append at 12:43:58 on 98/06/29 GMT (by SAKC3II at ELINK) Alan, The real comment is that it's not clear what might happen. It goes all the way from "nothing visible" to system crashes and wrong information. Many people have been moving dates around before the discussion and have never seen any problems. But the big caution is that you are on your own if something does happen. If the worse that could happen is you have lost some time and will have to restore the system and try again, you still need to decide if you can afford for the worst case to happen in terms of time and resources. Sherry Goncharsky IBM Tucson - Storage Systems Division Year 2000 Representative