----- YEAR2000 CFORUM appended at 13:48:58 on 97/06/02 GMT (by 86696404 at EHONE) Subject: CICS V2 and Year 2000 My Customer is currently using CICS V2.1.2. This supports a key business application which is written in 'macro level code'. My IT contact within the Customer is proposing the current application to be re-written in 'command level' (so we can move to CICS V4), but is getting some 'push back', saying they could (maybe, probably) manage the two digit date issue with CICS V2 at the application level as a stop gap until the new SAP application is ready (post Y2000). However, my IT contact has heard a further rumour concerning CICS V2 post year 2000 along the lines..... '...I have heard a report that CICS 2.1, instead of just not being Y2000 compliant, in fact WILL NOT WORK AT ALL after 31 Dec 1999, because it goes into 'an infinite loop'. Can you establish confirmation of this, please?' I have explained to the IT contact that CICS V2 has not been exhaustively tested as it is (a) out of support now and (b) we KNOW it is not 'year 2000 compliant' due to the two digit date issue, so it is difficult to answer the query. I do understand, however, that if we have any experience of the above 'infinite loop', or other 'catastrophic events' for CICS V2.1 this will be very useful to the IT contact to convince his business units that they have to rework the application and not waste time on investigating work-arounds for the two digit date (a risk I don't believe is acceptable to their business anyway). Has anyone heard, or have any experience of the above 'infinite loop' (under MVS 5.2.2)? Colin Richardson, UK Managed Operations. (RICHARC @ UKSSVM1) (Also appended on CENTURY Forum) ----- YEAR2000 CFORUM appended at 15:38:49 on 97/06/02 GMT (by IL35816 at ELINK) Subject: Year 2000 Windowing Pivot Year Standards Ref: Append at 21:41:18 on 97/05/29 GMT (by LKGOINS at CHGVMIC1) It has often seemed to me that a sliding "pivot" makes more sense, such as "current year - 1912" so that in 1998, your "pivot" will go to 86. Charles Mills Firesign Computer Company, San Francisco charlesm@firesign.com ----- YEAR2000 CFORUM appended at 16:09:16 on 97/06/02 GMT (by 9WARLTK at CROVM4) Subject: Compilers and Year 2000 A major customer has asked IBM to modify the COBOL compiler to add syntax to assist in solving their Year 2000 problem. IMHO simple syntax instead of ugly source code insertions is a brilliant idea although a difficult compiler enhancement to make. Has any of your customers asked for a similar extension in COBOL or PL/I and how do you see the demand for such a facility? This is not a silver bullet but who knows? Regards, Keith Warltier, COBOL Restructuring & Year 2000 Consultant 9WARLTK@CROVM4 or GBIBMTJ2@IBMMAIL or KEITH_WARLTIER@UK.IBM.COM ----- YEAR2000 CFORUM appended at 11:36:08 on 97/06/03 GMT (by BLGIBSON at ATLVMIC1) Subject:UNIX testing strategy? We are in the process of formulating testing strategies for a site with a number of different platforms. I'm interested in hearing some strategies being used / considered for the various UNIX systems (HP/UX Sun Solarix, AIX). We are currently thinking our only alternative will be to build a 'clone' test system of the unix system on which the applications being tested resides. If anyone knows of any tools (especially date simulators) that enable other strategies, could you post here or contact me at bennieg@vnet.ibm.com? Thanks Bennie Gibson - IBM GS IT Architect - Atlanta, Ga. T/237-4576 ----- YEAR2000 CFORUM appended at 14:54:33 on 97/06/03 GMT (by 62409950 at EHONE4) Subject: Compatibility Question 1 What are the potential issues when a customer wants to communicate between NJE's ,one Y2K-ready ,the other one not? Question 2 Similarly what problems are anticipated in an SNA network accessing two hosts ,the first being Y2K-ready ,the second not ? The reason of the question is because the Y2K support will be tested on one MVS first. Thanks for any help. ----- YEAR2000 CFORUM appended at 16:18:11 on 97/06/03 GMT (by BLGIBSON at ATLVMIC1) Subject:Programmers Work Bench We have run across PWB at a year 2000 engagement. Can anyone comment on experiences or plans to deal with PWB and PWB generated applications? Thanks Bennie Gibson - IBM GS IT Architect - Atlanta, Ga. T/237-4576 ----- YEAR2000 CFORUM appended at 23:53:29 on 97/06/03 GMT (by ALHICKS at ISSCAUS) Subject: Scanning Excel spreadsheets I am working on a Year 2000 project where the customer has tens of thousands of Excel spreadsheets. Does any one know of a tool or product that can assist in the automated scannning of these spreadsheets for Year 2000 compliance. What we are looking for is something that would detect all of the date fields/functions used and provide a report on them. The individual spreadsheets would then be manually inspected and corrected if necessary. Thanks, Allan Hicks - ISSC Australia. ----- YEAR2000 CFORUM appended at 10:56:27 on 97/06/04 GMT (by MA00613 at EHONE7) Subject: Scanning Excel spreadsheets Ref: Append at 23:53:29 on 97/06/03 GMT (by ALHICKS at ISSCAUS) At DCI's Year 2000 Issues and Answers Conference last month, there was a fellow by the name of Karl Feilder. He's the CEO of a firm called "Greenwich Mean Time." His firm is involved in the PC-side of the Y2K issue (not very pretty stuff, either). You might want to contact him directly at kwf@gmt-2000.com to see if he has any information for you. Their web address is http://www.gmt-2000.com hth... 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 16:51:24 on 97/06/04 GMT (by YAEGER at SJFEVMX) Subject: New DFSORT Year 2000 Features DFSORT R13 PTF UQ05520, available now, delivers the following additional DFSORT Year 2000 features requested by our customers: o A new Y2S format. Y2S can sort, merge and transform two-digit character or zoned decimal year data according to the century window, while handling binary zeros, blanks and binary ones in the year field as special indicators. o A new Y2B format. Y2B can sort, merge and transform two-digit binary year data according to the century window. o FREE=CLOSE support for DFSPARM. This makes it possible to override SORT statements generated by multiple COBOL SORT verbs in the same COBOL program, using appropriate DFSPARM data sets with FREE=CLOSE. Complete details on all of DFSORT's Year 2000 features, including these new additions, can be found in our SORT2000 paper. You can browse SORT2000 from the DFSORT home page at URL: http://www.storage.ibm.com/dfsort/ or download sort2000.zip which contains postscipt and text versions of the paper, via anonymous FTP from: lscftp.pok.ibm.com/pub/mvs/docs/ or ask your IBM representative to obtain the SORT2000 paper for you from MKTTOOLS. Frank L. Yaeger - DFSORT Team (Specialties: ICETOOL, OUTFIL, Y2K :-) ----- YEAR2000 CFORUM appended at 19:41:53 on 97/06/04 GMT (by BLGIBSON at ATLVMIC1) ..... YEAR2000 CFORUM modified at 20:40:42 on 97/06/04 GMT (by BLGIBSON at ATLVMIC1) Subject: Actual test experiences? IBM 9221/Amdahl 5995 ºfixed incorrect subject line... We are looking for anyone that has performed hardware testing on IBM 9221 and Amdahl 5995. By hardware testing, we mean setting the hardware clock to 12/31/1999 and validating how the hardware, firmware and operating system (MVS and VM) react to the rollover AND the ability to set the hardware clock to 1/1/2000 and beyond and how MVS and VM react. Please post if you know of such tests (or contact me at bennieg@ibmus.ibm.com. Thanks Bennie Gibson - IBM GS IT Architect - Atlanta, Ga. T/237-4576 ----- YEAR2000 CFORUM appended at 13:07:17 on 97/06/06 GMT (by GBCBHG00 at ELINK) <10066> Subject: CICS V2 and Year 2000 Ref: Append at 13:48:58 on 97/06/02 GMT (by 86696404 at EHONE) Colin, Although I can't substantiate it I can perpetuate the rumour from what I have been advised is fact. The information was posted on a YEAR2000 email conference of which I participate. The sender of the origonal message was 'nlabs@digital.net'. > If you're a mainframe shop, consider migrating your old CICS 2.1.2 Macr > Level system down to a P/390 and tossing it in a broom closet for 10 > years. Remember, you can't run CICS 2.1.2 with a system date greater > than 1999-12-31, it goes into an infinite loop. > And the corresponding level of IMS 3.1.X will come up, but it will > reject all transactions. (ref: previous test results reported on this > list) You may want to try nlabs@digital.net to try and find the origonal source This append was created on the External IBMLink system by Peter Gammage Tel 0141-204 2737 SEMA Group Outsourcing Fax 0141-204 2523 1 Atlantic Quay Broomielaw, Glasgow G2-8JE Email: Peter.Gammage@mail.sema.co.uk ----- YEAR2000 CFORUM appended at 16:14:55 on 97/06/06 GMT (by SAKC3II at ELINK) <10067> Subject: Test Tools and date/time references Ref: Append at 15:10:50 on 97/04/04 GMT (by GBCCDB01 at ELINK) Martin, I'm a newcomer to TalkLink and am reviewing a lot of old posts. I'm interested in the process you went through in choosing your date simulation product. Is is someting I could have emailed? What communication method do you prefer? Alan Schwartz ----- YEAR2000 CFORUM appended at 16:22:46 on 97/06/06 GMT (by SAKC3II at ELINK) <10068> Subject: COBOL Migration Experiences Ref: Append at 15:24:07 on 97/05/06 GMT (by MLDUCKWO at STLVM6) Mark, we just started this effort here. Let me know how to contact you o I can get some information on your experience. Alan Schwartz ----- YEAR2000 CFORUM appended at 14:08:59 on 97/06/10 GMT (by 86698663 at EHONE) <10069> Subject: Year 2000 Ready IBM Prog Products Looking through the latest (7th) Version of 'The Year 2000 and 2-Digit Dates: A Guide for Planning and Implementation' I find that some IBM Program Products which previously showed 'X*' against a release ie. Y2K support available through the service stream (PTF etc.) now show 'X' against the same release ie. Y2K ready. Does this indicate that no PTF or whatever has been found to be necessary to achieve Y2K readiness ? An example is 5684-157 HMF 1.1.1 in the VM Platform Products table, Appendix A. Also can you tell me what release of the following products is Y2K ready and when this is available for the VM/ESA platform : 5654-007 Automated Network Operations Code 5785-DJD VMBARS 5668-767 VS Pascal Compiler and Library Thanks. Debbie. BARTODA at UKSSVM1 (GBIBMC75 at IBMMAIL) ----- YEAR2000 CFORUM appended at 12:39:13 on 97/06/11 GMT (by BEGENB09 at ELINK) <10071> Subject: ADF and YEAR 2000 Ref: Append at 23:23:10 on 97/03/26 GMT (by VNDRI236 at SJFEVMX) Hi to all, Since the last message I left on this cforum, some things has changed in our situation. We did some testing with our current (non Y2K compliant) ADF version 1.3. With the Validate simulation tool, as well as on a real Year2000 LPAR, we had the same problem when using the $DATE function in ADF Audit Language. On top of this problem, the planning for some ADF applications has been changed, so that ADF will still be necessary beyond 1999. Our management asked to estimate the cost for converting from ADF V1.3 to ADF V2.x, which is Y2K compliant. So what I'm looking for now, is some information or help to point out what this conversion effort can be. Note that we plan only to convert the run-time environment, and we don't prefer to convert all the sources into the IADF interface. Since ADF has been withdrawn from marketing some years ago, I have not been able to find this information. Any comments or suggestions are welcome. Thank you very much Alex Breesch This append was created on the External IBMLink system by Alex Breesch Generale Bank Belgium Development Support tel. +32.2/565.43.44 fax. +32.2/565.24.20 ----- YEAR2000 CFORUM appended at 16:49:52 on 97/06/11 GMT (by 86679714 at EHONE) <10072> Subject: ADF and YEAR 2000 Ref: Append at 12:39:13 on 97/06/11 GMT (by BEGENB09 at ELINK) Prsumably it could be time to re-examine the tool pack mentioned previously: IMS ADF Tool Pak 5655-A21 Highlights include: Assess Year 2000 Impact on ADF Applications Debug ADF conversational transactions Recreate ADF Static and Dynamic rule source Move, remove, migrate (version to version) & document ADF applications Analyze ADF low-level audits Pete Sadler ----- YEAR2000 CFORUM appended at 19:37:08 on 97/06/11 GMT (by RSBOWERS at WASVMIC1) <10073> Subject: YEAR 2000 Conversion Assistance Are there any groups internal to IBM which can assist with the assessment of existing products and their conversion to be YEAR2000 compliant or safe? The product in question is written in a combination of BAL, PL/I and PL/AS. Please respond directly to me: RSBOWERS @ WASVMIC1 - Bob Bowers ----- YEAR2000 CFORUM appended at 12:58:08 on 97/06/12 GMT (by NL5OTR01 at ELINK2) <10074> Subject: year 2000 problem in mainframe and pc software From John Been Most of the products of IBM are mentioned in the year 2000 guide of IBM, but a couple of products are missing. I like to know if there is a year 2000 problem with respect to these products, what will be the compliant version and if it is already general available. With respect to the mainframe: APPC/MVS 1.0.0; CICS File Transfer; COBOL AD/CYCLE 1.1; COBOL Productivity Suite 1.1; ICKDSF Standalone 1.5.0; Dist. Usage Authorisation; ESCON DIR JES2; 3270/PC FTP for TSO; LANRES MVS HOST 1.4; NCP 7.5; Netview ENT LE/370 3.1; Office Vision Host/Client 1.1; OS DITTO S/360-370; OSA Support Facility 1.1; OV/MVS workgroup pgm 1.1; PI and specials 1.1.1; Right to copy category A; Systemview 1.1; TCP/IP 3.1; VCP Kit; Videotex com monitor prot,frame proc supp;VisGen applgen MVS opt, developer, workgroup serv.; X-25 NPSI And with respect to PC software: Distributed Console Access Facility; Faxserver; Personal Communications 3270 Entry Level Dos mode, 3270 Full function Dos mode, 3270 Windows mode. Thank you for your help John Been This append was created on the External IBMLink system by Cliff Jackson Otra Information Services The Netherlands tel : +31 20 5450825 ----- YEAR2000 CFORUM appended at 18:49:05 on 97/06/13 GMT (by VAIS001 at ELINK) <10075> ..... YEAR2000 CFORUM modified at 13:02:47 on 97/06/18 GMT (by VAIS001 at ELINK) <10084> Subject: y2k vtam Reference: "The Year 2000, Cobol Programs, and You" Guide paper dated April 1997 by Tom Ross. In the Guide session AP152 paper two statements are made on pages 29 & 30 relative to "networks" which we want some detail. 1. "Do not allow future dates to corrupt Networks." a. Is this referring to network software products like VTAM and TCP/IP? b. How can the network be corrupted like a dataset can be corrupted? c. What do we need to look out for? 2 "Disconnect LPAR from production networks." a. Does this mean physically? b. Our testers will be remotely located from the Time Machine LPAR. c. How do we test EP lines in an NCP? d. Can this all be done with a SNI connection via channel attached NCP's to a machine. sam ----- YEAR2000 CFORUM appended at 22:36:13 on 97/06/13 GMT (by SHERRY at SJFEVMX) <10076> Subject: year 2000 problem in mainframe and pc software Ref: Append at 12:58:08 on 97/06/12 GMT (by NL5OTR01 at ELINK2) The Guide indicates that ICKDSF Standalone is year 2000 ready with Release 16 under MVS. Unfortunately the release number is missing in the VM and VSE listings and will be added in the next update. Sherry Goncharsky SSD Year 2000 Software Rep sgoncha@us.ibm.com ----- YEAR2000 CFORUM appended at 07:50:16 on 97/06/16 GMT (by NL5OTR01 at ELINK) <10077> Subject: ICKDSF year 2000 compliancy from: John Been According to internal information here at OTRA Amstelveen, we have Device Support Facility 1.16.0, that is year 2000 compliant. I also found Device Support Facility standalone (ICKDSF) 1.5.0. The IBM Y2000 guide says that we also need 1.16.0. Is it possible that I found an incorrect releasenumber and that it is part of DSF 1.16.0, or do we indeed have an incompliant version of ICKDSF. Thank you for your help, John Been This append was created on the External IBMLink system by Cliff Jackson Otra Information Services The Netherlands tel : +31 20 5450825 ----- YEAR2000 CFORUM appended at 08:49:30 on 97/06/16 GMT (by NL5OTR01 at ELINK) <10078> Subject: SMF record-dumping From: john Been When SMF records are being dumped with program IFASMFDP, the parameter DATE(00000,99366) will be used as input. In what way will this be solved after 01-01-2000. Thank you for your help, John Been This append was created on the External IBMLink system by Cliff Jackson Otra Information Services The Netherlands tel : +31 20 5450825 ----- YEAR2000 CFORUM appended at 10:27:48 on 97/06/16 GMT (by WAWA001 at EHONE7) <10079> Subject: SMF record-dumping Ref: Append at 08:49:30 on 97/06/16 GMT (by NL5OTR01 at ELINK) John, Take a look at any of the latest SMF manuals. The DATE parameter has been changed to allow (yyddd/yyyyddd,yyddd/yyyyddd). The new default is (1900000,2099366). Cheryl Watson, Watson & Walker, cheryl@watsonwalker.com Home page: http://www.watsonwalker.com, 1-800-553-4562 ----- YEAR2000 CFORUM appended at 12:36:11 on 97/06/16 GMT (by BLGIBSON at ATLVMIC1) <10080> Subject: 1972 - data encapsalation Ref: Append at 01:10:12 on 97/02/10 GMT (by HELENE at NYCVMIC1) Has anyone got any information (soft copy or otherwise) on data encapsulation techniques and what (if any) experiences have been seen? Thanks Bennie Gibson - IBM GS IT Architect - Atlanta, Ga. T/237-4576 ----- YEAR2000 CFORUM appended at 08:08:51 on 97/06/17 GMT (by 9WARLTK at CROVM4) <10081> Subject: Customer question re LE/370 1.2 A customer at Lloyds Bank would like to know: Which of the following do NOT have Year 2000 compliance in LE/370 1.2: The CALLable services which process dates The support for the CURRENT-DATE intrinsic function ACCEPT FROM DATE for all COBOLs Regards, Keith Warltier, COBOL Restructuring & Year 2000 Consultant 9WARLTK@CROVM4 or GBIBMTJ2@IBMMAIL or KEITH_WARLTIER@UK.IBM.COM ----- YEAR2000 CFORUM appended at 15:37:04 on 97/06/17 GMT (by Y2KTSC3 at STLVM6) <10082> Subject: Customer question re LE/370 1.2 Ref: Append at 08:08:51 on 97/06/17 GMT (by 9WARLTK at CROVM4) > Which of the following do NOT have Year 2000 compliance in LE/370 1.2: > > The CALLable services which process dates > > The support for the CURRENT-DATE intrinsic function > > ACCEPT FROM DATE for all COBOLs None of these functions are affected by the change from 1999 to 2000. ACCEPT FROM DATE will give correct 2-digit year dates after 1999, so it is not technically Year 2000 ready, but it will be correct. LE 1.2 is not Year 2000 ready because it is not serviced by IBM. LE 1.3 is also not supported, and LE 1.4 goes End Of Service 9/97. Year 2000 Technical Support Center ----- YEAR2000 CFORUM appended at 08:43:01 on 97/06/18 GMT (by GBCADH00 at ELINK) <10083> Subject: year 2000 problem in mainframe and pc software Ref: Append at 12:58:08 on 97/06/12 GMT (by NL5OTR01 at ELINK2) >>COBOL Productivity Suite 1.1; ICKDSF Standalone 1.5.0; Dist. Usage >>Authorisation; ESCON DIR JES2; 3270/PC FTP for TSO; LANRES MVS HOST 1.4; >>NCP 7.5; Netview ENT LE/370 3.1; Office Vision Host/Client 1.1; >>OS DITTO S/360-370; OSA Support Facility 1.1; OV/MVS workgroup pgm 1.1; >>PI and specials 1.1.1; Right to copy category A; Systemview 1.1; Dist. Usage Authorisation (and I guess Right to copy category A) are not products in their own right. They are an authority to make a copy to run on another machine. You need to look at what is being copied and ensure that that product is part of the inventory. Something similar is "Customer Technical Support Location - CTSL". This is a 'first copy' where the underlying product needs to be established. The products in question are likely not be be mainframe products, probably running on PCs. This append was created on the External IBMLink system by Nick Hands-Clarke (GBFPLNHC at IBMMAIL.COM) FPLO (+44-1306 740123 ext 3121) ----- YEAR2000 CFORUM appended at 13:58:33 on 97/06/18 GMT (by NL5OTR01 at ELINK) <10085> Subject: year 2000 problem in mainframe and pc software Ref: Append at 08:43:01 on 97/06/18 GMT (by GBCADH00 at ELINK) Nick, Thank you for your information provided about Dist. Usage Authorisation. But about the other software, are products like NCP 7.5; Netview ENT LE/370 3.1; Office Vision Host/Client 1.1; OS DITTO S/360-370; OSA Support Facility 1.1; OV/MVS workgroup pgm 1.1; LANRes MVS Host 1.4, realy no mainframe products? And are they not in the Y2K guide because there is no support anymore, or have they not been tested yet? Thanks again, John been This append was created on the External IBMLink system by Cliff Jackson Otra Information Services The Netherlands tel : +31 20 5450825 ----- YEAR2000 CFORUM appended at 14:35:40 on 97/06/18 GMT (by NL5OTR01 at ELINK) <10086> Subject: date variables in IBM products from: John been Will there be a change in the names of the variables in for example TSO, ISPF, CLISTS, etc. in relation with the year 2000. I already found out that for example in TSO the name of &SYSDATE has been changed in &SYS4DATE. Please can you help me out, or provide me with a list of such changes in products mentioned above or other products you can think about. Thank you for helping me with this problem, John been This append was created on the External IBMLink system by Cliff Jackson Otra Information Services The Netherlands tel : +31 20 5450825 ----- YEAR2000 CFORUM appended at 11:48:29 on 97/06/19 GMT (by ISOKN at DKIBMVM1) <10087> Subject: date variables in IBM products Ref: Append at 14:35:40 on 97/06/18 GMT (by NL5OTR01 at ELINK) There have been added new variables, like &SYS4DATE, that better support the Year2000 challenge. Existing variables, like &SYSDATE, will continue working the way they work today, i.e. continue with 2-digit Year notation. This allows old applications that can live with 2-digit year to continue working without change. Remember, it might not be a problem for all applications to use only 2 digits for year. It also allows you to develop new applications with full Year2000 awareness. Ole Knudsen - IBM Global Services - MVS Application Development Support ----- YEAR2000 CFORUM appended at 13:25:11 on 97/06/19 GMT (by NL5OTR01 at ELINK2) <10088> Subject: date variables in IBM products part 2 From John Been I found out that for example in TSO the name of &SYSDATE has been changed in &SYS4DATE. Is there a list of such changes in IBM products. Thanks, John been This append was created on the External IBMLink system by Cliff Jackson Otra Information Services The Netherlands tel : +31 20 5450825 ----- YEAR2000 CFORUM appended at 13:47:20 on 97/06/19 GMT (by 78897412 at EHONE) <10089> Subject: date variables in IBM products part 2 Ref: Append at 13:25:11 on 97/06/19 GMT (by NL5OTR01 at ELINK2) John, I can hardly imagine that something like that is available. As far as my knowledge stretches you will definately find Y2000 rela- ted info in the product manuals themselves so the best approach would be to make a product inventory of all your products and obtain Y2000 specific info for each product from the appropriate manuals. Should you come across such a manual as you refer to I am very interes- ted myself so do not hesitate to update the forum. Regards Hans Wijngaard IBM Netherlands ----- YEAR2000 CFORUM appended at 15:14:27 on 97/06/19 GMT (by Y2KTSC3 at STLVM6) <10090> Subject: year 2000 problem in mainframe and pc software Ref: Append at 12:58:08 on 97/06/12 GMT (by NL5OTR01 at ELINK2) > COBOL AD/CYCLE 1.1; This COBOL is in the 2-digit year planning guide, but the name has changed. AD/Cycle COBOL R1 = COBOL/370 R1 = COBOL for MVS & VM R1. The product number is more clear: 5688-197. It IS Year 2000 Ready. Year 2000 Technical Support Center ----- YEAR2000 CFORUM appended at 15:23:09 on 97/06/19 GMT (by Y2KTSC3 at STLVM6) <10091> Subject: y2k vtam Ref: Append at 18:49:05 on 97/06/13 GMT (by VAIS001 at ELINK) >1. "Do not allow future dates to corrupt Networks." >a. Is this referring to network software products like VTAM and TCP/IP? >b. How can the network be corrupted like a dataset can be corrupted? >c. What do we need to look out for? For more details please see the OS/390 Year 2000 testing Web Page. You can in fact connect a 'Time Machine' to current date machines but ONLY if you are very careful to have a one-way flow of files. The 'Time Machine' should be treated as a black hole, anything can go in, nothing should ever come out. Year 2000 Testing by S390 group: http://ppdbooks.pok.ibm.com/cgi-bin/bookmgr/ >2 "Disconnect LPAR from production networks." >a. Does this mean physically? >b. Our testers will be remotely located from the Time Machine LPAR. >c. How do we test EP lines in an NCP? >d. Can this all be done with a SNI connection via channel attached NCP's > to a machine. The safest arrangement is to completely disconnect your Time Machine LPAR from any current date systems. Any other configuration puts your production systems at risk. I understand that LPAR connections can be disconnected logically and still be connected physically. Year 2000 Technical Support Center ----- YEAR2000 CFORUM appended at 19:11:55 on 97/06/19 GMT (by Y2KTSC2 at STLVM6) <10092> Subject: year 2000 problem in mainframe and pc software Ref: Append at 12:58:08 on 97/06/12 GMT (by NL5OTR01 at ELINK2) Below, you will find the Year 2000 status of the products you asked about. In the future, please include the product numbers, product names, version/release information and operating system/platform. This will enable us to quickly provide answers. For those products highlighted with a double asterisk below, we are unable to find the product with the information provided. Please provide additional information, such as product number. Thank you. Product Year 2000 Ready Status (yes/no) ----------------------------------------------- --------------- APPC/MVS 1.0.0 Yes This product was part of VTAM and is ready as long as you have a Year 2000 Ready release of VTAM. CICS File Transfer No. This product, 5798-DHQ, was withdrawn from service in 1992. COBOL AD/CYCLE 1.1 No. COBOL for MVS & VM is the earliest Y2K Ready COBOL compiler COBOL Productivity Suite 1.1 No. This was withdrawn from service April 26, 1997 ICKDSF Standalone 1.5.0 No. I believe you mean 1.15.0. 1.16 is the earliest release that's Ready Dist. Usage Authorisation No. Not a product. (See append 10083) ESCON DIR JES2 ** 3270/PC FTP for TSO ** LANRES MVS HOST 1.4 ** According to the HONE Salesmanual database, there is no Release 1.4 for IBM LAN Resource Extension and Services/MVS (LANRES/MVS), product number 5695-123. It just goes up to 1.3.0. Is this the right product number? NCP 7.5 See note. See Info APAR II09701 which documents all NCP products Netview ENT LE/370 3.1 ** Office Vision Host/Client 1.1 ** OS DITTO S/360-370 ** OSA Support Facility 1.1 ** OV/MVS workgroup pgm 1.1 No. Service withdrawn 6/30/1997 PI and specials 1.1.1 Yes. Right to copy category A No. Not a product. (See append 10083) Systemview 1.1 ** Systemview for AIX R2 is Year 2000 Ready TCP/IP 3.1 Yes. VCP Kit ** Videotex com monitor prot,frame proc supp ** VisGen ** And with respect to PC software: Distributed Console Access Facility No. DCAF 1.1 was withdrawn from service on 11/30/1994. Faxserver No. Service withdrawn 12/29/1992 Personal Comm. 3270 Entry Level Dos mode ** 3270 Full function Dos mode ** 3270 Windows mode ** Year 2000 Technical Support Center (TSC2) ----- YEAR2000 CFORUM appended at 19:16:27 on 97/06/19 GMT (by Y2KTSC2 at STLVM6) <10093> Subject: COBOL Migration Experiences Ref: Append at 16:22:46 on 97/06/06 GMT (by SAKC3II at ELINK) You can contact Mark Duckworth by calling the Year 2000 Technical Support Center at 800-426-4968 (800-IBM-4YOU) and asking to speak to him. Year 2000 Technical Support Center (TSC2) ----- YEAR2000 CFORUM appended at 19:21:41 on 97/06/19 GMT (by Y2KTSC2 at STLVM6) <10094> Subject: CICS V2 and Year 2000 Ref: Append at 13:07:17 on 97/06/06 GMT (by GBCBHG00 at ELINK) This is a question that should probably be asked on the CICS FORUM. Or, call 800-IBM-SERV (800-426-7378) to be placed in contact with a CICS technical support person. Year 2000 Technical Support Center (TSC2) ----- YEAR2000 CFORUM appended at 19:22:59 on 97/06/19 GMT (by Y2KTSC2 at STLVM6) <10095> Subject: Scanning Excel spreadsheets Ref: Append at 23:53:29 on 97/06/03 GMT (by ALHICKS at ISSCAUS) You should probably contact Microsoft, or look on their webpage, for this type of automated assistance. Year 2000 Technical Support Center (TSC2) ----- YEAR2000 CFORUM appended at 19:25:55 on 97/06/19 GMT (by Y2KTSC2 at STLVM6) <10096> Subject: Programmers Work Bench Ref: Append at 16:18:11 on 97/06/03 GMT (by BLGIBSON at ATLVMIC1) Pretty much every software company has a product with the words Programmer's Work Bench in the title. I am unable to find a specific IBM product by that name. Do you have additional information to share that would help us answer your question? Year 2000 Technical Support Center (TSC2) ----- YEAR2000 CFORUM appended at 20:51:57 on 97/06/19 GMT (by Y2KTSC2 at STLVM6) <10097> Subject: Year 2000 Ready IBM Prog Products Ref: Append at 14:08:59 on 97/06/10 GMT (by 86698663 at EHONE) 5654-007 Automated Network Operations Code Not ready. This product will be withdrawn from service 04/24/98 5785-DJD VMBARS No information available 5668-767 VS Pascal Compiler and Library Year 2000 Ready with maintenance applied Year 2000 Technical Support Center (TSC2) ----- YEAR2000 CFORUM appended at 09:28:11 on 97/06/20 GMT (by JGREIG at GNKVM) <10098> I have a question regarding use of a separate LPAR for testing in a Y2K date environment. The HARDWARE clock cannot be changed but the LPAR can be IPL'd with a different system date. Can anyone help me understand the validity of Y2K testing carried out in an environment like this ? What is the risk of further Y2K implications being uncovered when the hardware clock is finally moved forward ? Johan Greig Y2K Project Leader IBM Greenock ----- YEAR2000 CFORUM appended at 11:20:59 on 97/06/20 GMT (by GAD at KGNVMC) <10099> Subject: Testing in an LPAR partition Ref: Append at 09:28:11 on 97/06/20 GMT (by JGREIG at GNKVM) Testing done under LPAR with the TOD properly changed is 100% valid and proper test. As far as MVS or any other operating system, there is *NO* way for them to ever see a TOD value other than the one that was set at IPL time. There has been some rumors to the contrary, but that is all they are...rumors. Greg Dyck MVS BCP Kernel and CURE support ----- YEAR2000 CFORUM appended at 14:38:02 on 97/06/20 GMT (by GBCAMS01 at ELINK) <10100> Subject: Hardware Isolation. My apologies if this question has already been asked. Does anyone know what potential there is for data corruption etc in the following scenario ? Two LPARs, ie Production and Y2K, accessing a DASD string using EMIF and each LPAR being restricted to its own devices using CANDIDATE lists (ie PART=). Obviously this will share channels and control units but I'm not sure what the impact of this is. Thanks in anticipation. This append was created on the External IBMLink system by Iain McArthur ANFIS plc GBVTFDPJ @ IBMMAIL 0141-275 9290 ----- YEAR2000 CFORUM appended at 03:52:14 on 97/06/21 GMT (by BLGIBSON at ATLVMIC1) <10101> ..... YEAR2000 CFORUM modified at 03:58:46 on 97/06/21 GMT (by BLGIBSON at ATLVMIC1) <10103> Subject: Programmers Work Bench Ref: Append at 19:25:55 on 97/06/19 GMT (by Y2KTSC2 at STLVM6) My apologies. This is also known as PWB, it is a tool formerly used by Andersen to create COBOL applications (no longer supported by Andersen... customer supports it themselves). BTW: We also have to deal with TI IEF. So, any input on what is being done with code generation facilities such as these will appreciated. Bennie Gibson - IBM GS IT Architect - Atlanta, Ga. T/237-4576 ----- YEAR2000 CFORUM appended at 03:55:20 on 97/06/21 GMT (by BLGIBSON at ATLVMIC1) <10102> Subject: Testing in an LPAR partition Ref: Append at 11:20:59 on 97/06/20 GMT (by GAD at KGNVMC) Just some input from our experience so far... We have a number of system software components that are not Y2K compliant. We need to start application renovation while we wait for the various system software vendors to get off the dime. As a result, we find date simulation will be required even though we have the capability to run a 'time machine' by setting the LPAR date. Bennie Gibson - IBM GS IT Architect - Atlanta, Ga. T/237-4576 ----- YEAR2000 CFORUM appended at 22:46:39 on 97/06/22 GMT (by BLGIBSON at ATLVMIC1) <10104> Subject:UNISYS testing facilities? Has anyone found any UNISYS Y2K testing facilities? I'd like to hear what anyone with UNISYS is doing about testing. Thanks Bennie Gibson - IBM GS IT Architect - Atlanta, Ga. T/237-4576 ----- YEAR2000 CFORUM appended at 22:35:09 on 97/06/23 GMT (by IL35816 at ELINK) <10105> Subject: Anyone using a P/390 for Y2K testing ... ... might want to read my brief append 97/06/23 22:27:47 IL35816 Setting MVS Clock sets OS/2 Clock! in the PC500390 CFORUM. Charles Mills Firesign Computer Company, San Francisco charlesm@firesign.com ----- YEAR2000 CFORUM appended at 23:38:33 on 97/06/23 GMT (by BEGHTEL at STLVM6) <10106> Subject: ISO date with month as a word European dates are sometimes seen with a month number or with a month name (for example, 23/06/97 or 23 Jun 97). Is there an equivalent form for the ISO date with a month name, or is the ISO format of restricted to YYYY-MM-DD, that is, with only a month number? And where can one find the details of the ISO date format? Thanks, Merle Beghtel ----- YEAR2000 CFORUM appended at 07:58:21 on 97/06/24 GMT (by GBOAMU00 at ELINK) <10107> Subject: ISO date with month as a word Ref: Append at 23:38:33 on 97/06/23 GMT (by BEGHTEL at STLVM6) I believe that formats with a month name as 24 jun 97 were popularised by the software package SAS - I personally always call it the SAS date and use it extensively. I believe SAS is marketed by the SAS Institute and you will probably find it in 30 plus percent of MVS shops. This append was created on the External IBMLink system by David Cartwright Technical Consultant ++44 1827 710618 dc@dcuk.demon.co.uk ----- YEAR2000 CFORUM appended at 08:19:41 on 97/06/24 GMT (by 36601943 at EHONE) <10108> Subject: Anyone using a P/390 for Y2K testing ... Ref: Append at 22:35:09 on 97/06/23 GMT (by IL35816 at ELINK) The same effect is seen if you run VM and set the VM clock at IPL time. Dougie Lawson, IBM Basingstoke, UK. (aka 8LAWSOD at NHBVM2) ----- YEAR2000 CFORUM appended at 13:09:07 on 97/06/25 GMT (by VAIS001 at ELINK) <10109> Subject: Y2K TESTING - Changing the date with 'SET' In the context of Year2000 testing, will using the 'T DATE=,CLOCK=' command give the same results as as an IPL relative to the operating system base (i.e. excluding the OEM products)? By base, I mean: ESA/BCP, SMS/DFP, JES2, VTAM. Thanks in advance. sam ----- YEAR2000 CFORUM appended at 13:31:49 on 97/06/25 GMT (by GAD at KGNVMC) <10110> Subject: Y2K TESTING - Changing the date with 'SET' Ref: Append at 13:09:07 on 97/06/25 GMT (by VAIS001 at ELINK) The set command does not change the GMT time physically set in the hardware time of day (TOD) clock. It only alters the constants that MVS uses to determine local time. It can be used as a starting point for doing Y2K testing, but eventually testing *must* be done with the TOD clock physically set to the test date, as some code does a store clock instruction in itself and does not adjust the value with the local time offsets that MVS provides. Greg Dyck MVS BCP Kernel and CURE support ----- YEAR2000 CFORUM appended at 09:02:37 on 97/06/26 GMT (by NL5OTR01 at ELINK2) <10111> Subject: personal communications 3270 From John Been, Holland I like to know if 'Personal Communications 3270 Windows Mode version 3.1 / 4.0 is year 2000 compliant, and if not, what will be the compliant version. Thanks for helping me, John been This append was created on the External IBMLink system by Cliff Jackson Otra Information Services The Netherlands tel : +31 20 5450825 ----- YEAR2000 CFORUM appended at 09:28:55 on 97/06/26 GMT (by ALANDP at SYDVMXA2) <10112> John Been Personal Communications/3270 V4.0 (product number 85G8697) is the Year 2000 Ready version. Regards Year 2000 Technical Support Center - Asia Pacific Internet: y2ktscap@vnet.ibm.com VNET: Y2KTSCAP at SYDVMXA2 ----- YEAR2000 CFORUM appended at 15:48:48 on 97/06/26 GMT (by VAIS001 at EHONE7) <10113> Subject: Y2K TESTING - Changing the date with 'SET' Ref: Append at 13:31:49 on 97/06/25 GMT (by GAD at KGNVMC) NOTE: We are not SYSPLEX; we have a mainframe that runs in LPAR mode. At the risk of showing my ignorance, I have other questions(eventually). We just IPLed and when the date/time was displayed and we were allowed to change it, we responded with xx,clock=,date=, and the clock we specified was 23:30 and the date was 99365. We DID NOT go the system(hardware) console, go to the SYSDEF frame and change any clock there. Soooo, even though we IPLed, did we change the physical TOD clock or did we just change the MVS constants for that LPAR? There is only 1 TOD clock for the whole mainframe, right? Assuming we did NOT change the TOD, what components of our 'base'(ESA/DFSMS/JES2/VTAM) use the TOD and therefore won't pick up the year 2000 from the MVS constants? How might this affect dataset creation, catalog and VVDS info if we IPL backward from and forward to year 2000. Thank you for your time and all info. sam ----- YEAR2000 CFORUM appended at 16:09:26 on 97/06/26 GMT (by GAD at KGNVMC) <10114> ..... YEAR2000 CFORUM modified at 16:10:48 on 97/06/26 GMT (by GAD at KGNVMC) <10115> Subject: Y2K TESTING - Changing the date with 'SET' Ref: Append at 15:48:48 on 97/06/26 GMT (by VAIS001 at EHONE7) First off, ignore the fact that there is one physical TOD for the CEC. Depending on processor type some may actually have multiple TODs (though software will always synchronize them to each other) so the statement is not true. Second, when running a PR/SM environment every logical partition has it's own logical TOD which *CAN* *NOT* be told from the physical TOD as far as that partition is concerned. For all purposes, each logical partition has it's own physical TOD as far as it is concerned. MVS will only set the TOD clock during IPL if it is not already in a set state (which *never* happens on todays processors) or if the "GMT" operand is given in response to the TOD prompt at IPL. If you specify GMT you will then be prompted again for the local time and date. I don't believe a comprehensive list of products that use a STCK value directly and improperly exists. If the TIME system service is used to obtain local time it will see whatever you set. VSAM and VTOCs contain local time, I believe. JES2 uses a STCK value, but properly corrects it by the time offset. Greg Dyck MVS BCP Kernel and CURE support ----- YEAR2000 CFORUM appended at 10:28:15 on 97/06/27 GMT (by JGREIG at GNKVM) <10116> Subject: DB2/2 1.x DB2/2 1.x is not year 2000 ready. Can anyone explain to me what this will mean - i.e. will it simply cease to function or will problems depend on how it is used. Johan Greig IBM Greenock