----- YEAR2000 CFORUM appended at 02:48:43 on 97/04/01 GMT (by AS106968 at ELINK) Subject: Date Conversion Ref: Append at 21:37:43 on 97/03/27 GMT (by V$N8KG5 at CLTVM1) Leap Year Test : I believe the following logic applies to leap year determination. If year divisible by 4 then Leap=Yes, but if also divisible by 100 then Leap=No, but if also divisible by 400 then Leap=Yes. Thats a bit scratchy. In PL/I you could code : SELECT(MOD(YEAR,100)); WHEN (0) SELECT(MOD(YEAR,400)); WHEN (0) LEAP_YEAR='1'B; OTHERWISE LEAP_YEAR='0'B; END; OTHERWISE SELECT(MOD(YEAR,0)); WHEN (0) LEAP_YEAR='1'B; OTHERWISE LEAP_YEAR='0'B; END; END; No doubt this forum will receive either corrections or better ways !! This append was created on the External IBMLink system by Richard Barrow, J B Were & Son, Systems Programmer, Ph : +61 3 9679 1284 Fax : +61 3 9679 1067 E-mail : rbarrow@jbwere.com.au ----- YEAR2000 CFORUM appended at 13:36:27 on 97/04/02 GMT (by 70607825 at EHONE) Subject: LPAR and YEAR2000 hello, My customer has built an LPAR partition for Y2K tests. No DASD, no Control Unit , no physical paths are shared but we would like to use VTAM cross domain to logon | Is it a safe way ? Does VTAM propagate date between networks ? Thanks for help Andre ----- YEAR2000 CFORUM appended at 15:23:33 on 97/04/02 GMT (by GAD at KGNVMC) - Subject: LPAR and YEAR2000 Ref: Append at 13:36:27 on 97/04/02 GMT (by 70607825 at EHONE) This has already been asked in this forum. There is no problem doing this. If you search backwards for "VTAM" you will find the other appends on this. Greg Dyck MVS BCP Kernel and CURE support ----- YEAR2000 CFORUM appended at 18:36:14 on 97/04/02 GMT (by 485756 at STFVM4) Subject: Date Conversion Ref: Append at 02:48:43 on 97/04/01 GMT (by AS106968 at ELINK) Nicely done, except: Change OTHERWISE SELECT(MOD(YEAR,0)); To OTHERWISE SELECT(MOD(YEAR,4)); Tom Sowers IBM Global Systems Gaithersburg MD ----- YEAR2000 CFORUM appended at 10:10:34 on 97/04/03 GMT (by GBCFCP00 at ELINK) Subject: Test Tools and date/time references We are evaluating Y2K test tools and one claims to test all date/time references including SVC, PC call , STCK and CVT . I understand SVC is SVC11 but can anyone explain the others ? This append was created on the External IBMLink system by Bristol & West ----- YEAR2000 CFORUM appended at 12:12:49 on 97/04/03 GMT (by GAD at KGNVMC) - Subject: Test Tools and date/time references Ref: Append at 10:10:34 on 97/04/03 GMT (by GBCFCP00 at ELINK) The reference to PC is the TIME LINKAGE=SYSTEM processing. As to handling STCK, I don't see how unless they are referring to some specific set of STCK users such as the LE time service. The reference to CVT is too vague to guess. Note: The LE group has stated that modifications made by products like this to LE modules are not supported by them. The same holds true for the SVC and PC alterations. If a system problem occurs, including performance degradation, you may be asked to reproduce the problem without the simulation hooks in place. Greg Dyck MVS BCP Kernel and CURE support ----- YEAR2000 CFORUM appended at 15:56:24 on 97/04/03 GMT (by NEWSPOST at WATSON) Subject: Re: Date Conversion Ref: Append at 02:48:43 on 97/04/01 GMT (by AS106968 at ELINK) Append at 21:37:43 on 97/03/27 GMT (by V$N8KG5 at CLTVM1) X-rnews-From: geoff_moore@uk.ibm.com In <970401024843.year2000.cforum.ibmmvs.as106968@elink.vnet.ibm.com>, as106968@elink.vnet.ibm.com writes: >Leap Year Test : > > Thats a bit scratchy. In PL/I you could code : > > ..or save fingers and phosphor : mod(year,4)=0 & (*(mod(year,100)=0) | mod(year,400)=0) is true for leaps. Nntp-Posting-Host: mooreg.portsmouth.uk.ibm.com ----- YEAR2000 CFORUM appended at 18:25:05 on 97/04/03 GMT (by BARD018 at ELINK) ..... YEAR2000 CFORUM modified at 18:49:31 on 97/04/03 GMT (by BARD018 at ELINK) Subject: Test Tools and date/time references Ref: Append at 12:12:49 on 97/04/03 GMT (by GAD at KGNVMC) Could the reference to CVT mean the field CVTDATE? It contains the current julian date in packed format. Are you talking about test tools to provide fake date-time to applications? I don't know how can they handle the case that a program gets date from CVTDATE, or uses STCK as Greg pointed out, unless they change the application codes. Chen-yu Hu C. R. Bard, Inc. Murray Hill, NJ, USA chen-yu.hu@ccmail.crbard.com (908) 277-8512 ----- YEAR2000 CFORUM appended at 19:07:50 on 97/04/03 GMT (by KAREN at STLVM20) Subject: VisualAge 2000 Ref: Append at 22:06:38 on 97/03/27 GMT (by CREMA at STLVM1) There is accompanying information at http://www.software.ibm.com/ad/cobol/y2k Karen R. Barney ----- YEAR2000 CFORUM appended at 19:30:21 on 97/04/03 GMT (by IL68778 at ELINK) ..... YEAR2000 CFORUM modified at 19:57:53 on 97/04/03 GMT (by IL68778 at ELINK) Subject: Test Tools and date/time references Ref: Append at 18:25:05 on 97/04/03 GMT (by BARD018 at ELINK) >Appended at 18:25:05 on 97/04/03 GMT (by BARD018 at ELINK) >Are you talking about test tools to provide fake date-time to >applications? I don't know how can they handle the case that a program >gets date from CVTDATE, or uses STCK as Greg pointed out, unless they >change the application codes. Chen-yu, some of these products come with a utility that scans object code in loadlibs, looking for STCK, PC, SVC 11, etc. I guess they also could look at CVTPTR references, then check for references to CVTDATE, although the tool would have to be pretty smart to do a good job with that. BTW, couldn't they use the equivalent of a SLIP trap to detect references to CVTDATE? Gilbert Saint-flour Automated Migration Services IBMMAIL(USS24LG4) IBMLINK(IL68778) ----- YEAR2000 CFORUM appended at 19:33:14 on 97/04/03 GMT (by LESENDEL at LASVM1) Subject: RE: PC/DOS 7 & Lan requester are y2k ready ? As you said, PC DOS 7 is not Y2K Ready unless the required service or PTF is applied. Customers can check to see which Service Level the product is at. If the product is already at the required level or above, then no further action is required to make it Year 2000 Ready. However, if the product is below the required Service Level then the required PTF's must be applied to the product to make it Year 2000 Ready. Customers can contact their local IBM services representative to order the required PTF's. But, you will need the product number (info not given in your request, specially for Lan Requester) to identify the PTF which needs to be applied to the product. We hope this may help you understand Service Stream, and feel free to ask us further questions. Regards, YEAR 2000 TECHNICAL SUPPORT CENTER LATIN AMERICA T/L: 8-840-7347 // Y2KTSCLA AT ARG ----- YEAR2000 CFORUM appended at 21:25:22 on 97/04/03 GMT (by LESENDEL at LASVM1) Subject: RE: IMS Workload Router Version 2 (5697-B87) Jim, Sorry it took us so long to find the information you needed but finally it's here!. IMS WR v2 is Y2000 ready. This was confirmed by the IMS lab. If you need further information or assistance feel free to contact us. Regards, YEAR 2000 TECHNICAL SUPPORT CENTER LATIN AMERICA T/L: 8-840-7347 // Y2KTSCLA AT ARG WEB SITE: http//www.ibm.com.ar/argweb/anio2000.htm ----- YEAR2000 CFORUM appended at 05:32:44 on 97/04/04 GMT (by AS103033 at ELINK) Subject: Test Tools and date/time references Ref: Append at 19:30:21 on 97/04/03 GMT (by IL68778 at ELINK) >BTW, couldn't they use the equivalent of a SLIP trap to detect >references to CVTDATE? That would need a PER event for storage read. Is there such a thing? Has PER 3 been invented while I wasn't looking? Andy Wood. This append was created on the External IBMLink system by Westpac Banking Corp ----- YEAR2000 CFORUM appended at 15:10:50 on 97/04/04 GMT (by GBCCDB01 at ELINK) Subject: Test Tools and date/time references Ref: Append at 05:32:44 on 97/04/04 GMT (by AS103033 at ELINK) We looked a few of the Y2K date simulation tools. While they all handled SVC11 and the PC route to access the date, the best any could offer was to "guess" what were STCK's and references to CVTDATE. I am not aware of any method of directly intercepting either STCK's or references to the CVTDATE field. The most common method is to zap the STCK instructions to use a vendor supplied SVC. Even then you have to know or guess where the STCK codes are. As for using CVTDATE - one of our ISV's actually issued a fix to change the product to use SVC 11 instead of using CVTDATE !. We have now made our choice and purchased the product we intend to use. If you wish for further details from me please contact me direct. This append was created on the External IBMLink system by Martin Leist Senior Technical Analyst Itex, Norfolk County Council +44 1603 222788 (Martinl.itex@norfolk.gov.uk) ----- YEAR2000 CFORUM appended at 16:55:15 on 97/04/04 GMT (by AMPOP01 at ELINK) ..... YEAR2000 CFORUM modified at 18:20:50 on 97/04/10 GMT (by AMPOP01 at ELINK) Subject: Problem Passing julian date in RC starting year2000. Over the past 15 years, we built many system date utilities that have made life much easier for our user community. One date utility that will cause us major problems is called "JULIAN" that will pass the current, or gregoran(if passed as arg1) as the RC. The problem we are running into starting day 1 year 2000 is all return codes coming back via exit look like (1) instead of (00001). Today, the rc would look like (97001) but starting year 2000 the 0's are dropped. This is easy to fix via a simple statement of VAR=RIGHT(RC,5,'0') however we have thousands of programs using this code, and this will be very time consuming to correct. Is anyone else doing something like the above? If so, what are your plans to fix the problem? By the way, we have approached IBM, and they said everything is working as designed. John D'Adamo (AMP Inc., Harrisburg PA.) ----- YEAR2000 CFORUM appended at 15:04:46 on 97/04/07 GMT (by TMCDONAL at WASVMIC1) Subject: S/36 I do not think that System/36 hardware nor software is Year2000 compliant. Can the S/36 software be moved to an AS/400 and run on the S/36 emulation software? Will it be Y2K compliant then? ----- YEAR2000 CFORUM appended at 17:18:46 on 97/04/07 GMT (by JLJAY at RHQVM09) SUBJECT: On the Road to Year 2000 with VM and VSE: VM and VSE Roadshows - USA - 2nd and 3rd Quarter 1997 On the Road to the Year 2000 - with VM and VSE - Seminars With the Year 2000 less than 1,000 days, its likely that you've already begun thinking seriously about getting your systems ready to handle all the challenges that lie ahead -- especially if you're running older versions of VM, VSE or VM/VSE, such as VM/SP or VSE/SP. To help you put your organization on the right path, IBM is offering a series of no-charge, one-day seminars in cities across the U.S.. These seminars are specifically designed to offer you valuable information and solutions for taking your business into the 21st century and beyond. What makes VM/ESA and VSE/ESA the vehicles of choice Here's an opportunity for you to discover why the current versions of VM/ESA and VSE/ESA provide the ideal platform for launching some of the newest, most productive technologies available -- while they continue to support the applications critical to running your business. How hardware can help You'll learn how IBM's newest hardware, including CMOS servers, PC Server S/390 and RS/6000 with S/390 Server-on-Board, can provide the cost-effective platform you need for your VM/ESA or VSE/ESA system. Plus, you'll see how IBM's newest storage systems solutions can meet your data storage and retrieval needs. You may even discover that the IBM's newer hardware offers you considerable cost savings over the older hardware you're currently running and maintaining. Where networking pays off You'll also find out how VM/ESA and VSE/ESA can help you: * Create a business presence on the Internet * Administer your LANs and WANs * Make better use of the data distributed across your network And as a result, you'll discover the benefits of making VM/ESA and VSE/ESA the platforms of choice in your client/server environment. Who should attend Systems managers and others in decision-making roles with organizations running older versions of VM, VSE or VM/VSE. When and where Choose the date and location that best meet your needs: Date City Course Code ---------------------------------------- 4/29/97 St Louis, MO 310276 4/30/97 Minneapolis, MN 310278 5/01/97 Omaha, NE 310279 5/28/97 Columbus, OH 310280 5/29/97 Detroit, MI 310283 6/03/97 Chicago, IL 310287 6/04/97 Milwaukee, WI 310288 6/05/97 Indianapolis, IN 310290 6/10/97 Seattle, WA 310294 6/11/97 +Los Angeles, CA 310297 6/12/97 San Francisco, CA 310298 6/24/97 Harrisburg, PA 310299 6/25/97 +Wayne, PA 310300 + These sites changed city locations (were Costa Mesa and Philadelphia) Cities currently planned for 3Q and NOT YET OPEN for enrollment: (please note that the list is not yet complete) Albany, NY Atlanta, GA Burlington, NC Columbia, SC Fort Lauderdale, FL Jacksonville, FL Tampa, FL For enrollment and further information regarding the 2Q agendas and exact locations, call 1-800-289-0583. Please be ready to provide the appropriate course code, date and location. There are more seminars planned for other cities across the US in the third quarter of 1997. We will update the following INTERNET Sites with that information it becomes available: VM http://www.vm.ibm.com VSE http://www.ibm.de/go/d00000166 fyIT http://www.ihost.com/fyit Get a copy of the flyer/general Agenda by calling 1-800-IBM-4FAX and requesting document 7566. (1-800-426-4329) Or for more information contact: Judith Jay (914) 642-5568 T/L 224-5568 RHQVM09(JLJAY) or Internet EMAIL: JJAY@VNET.IBM.COM ----- YEAR2000 CFORUM appended at 17:39:30 on 97/04/07 GMT (by LESENDEL at LASVM1) Subject: RE: S/36 About your question, you can move your S/36 software to an AS400 and run it on the S/36 emulation software, but you need to convert your applications to be Year2000-Ready. This includes the modification of files and programs using analisys and conversion tools. If you need further information or assistance feel free to contact us. Regards, YEAR 2000 TECHNICAL SUPPORT CENTER LATIN AMERICA T/L: 8-840-7347 // Y2KTSCLA AT ARG WEB SITE: http//www.ibm.com.ar/argweb/anio2000.htm ----- YEAR2000 CFORUM appended at 19:09:34 on 97/04/07 GMT (by VINING at RCHVMX2) Subject: S/36 Ref: Append at 15:04:46 on 97/04/07 GMT (by TMCDONAL at WASVMIC1) Selected software products of S/36 were made Year 2000 tolerant by way of the S/36 Value-Added Software Package (VASP) introduced back in 1992. VASP implemented a fixed window support for treating 2-digit years with values of '00' to '39' as being logically greater than 2-digit years of '40' to '99' so as to simulate the years 2000 to 2039. Though VASP is no longer available (it's been withdrawn) for S/36, it did provide for limited support for Year 2000 for the S/36. Limitations in VASP are documented with one reference being SC21-8368 (Using Value-Added Software Package -- 9402 Model 236) chapter 15 Year 2000 Support. While VASP provides for S/36s to operate in years greater than 1999, VASP does NOT provide application enablers to assist in developing Year 2000 ready applications. By this I mean SSP PCE, COBOL, RPG, and Assembler do not provide 4-digit years as a standard part of the language. Customer application programs could be written in a manner to work properly in the year 2000 by implementing designs such as VASP does (that is, years '00' - '39' are logically greater than years '40' - '99') but there is nothing provided in the system to aid the developer. On the other hand for the AS/400 236 and 436 application programming enablers such as PCE ?LONGDATE? 4-digit year support and callable subroutines for S/36 RPG and COBOL applications are available to retrieve the current 4-digit year for the system or job. Bruce Vining ----- YEAR2000 CFORUM appended at 19:21:27 on 97/04/07 GMT (by JCRANDL at ATLVMIC1) Subject: RE: IMS Workload Router Version 2 (5697-B87) Ref: Append at 21:25:22 on 97/04/03 GMT (by LESENDEL at LASVM1) Thanks! Jim Randle, Memphis ISAM ----- YEAR2000 CFORUM appended at 20:04:16 on 97/04/07 GMT (by Y2KTSC5 at STLVM6) Subject: VisualAge 2000 Ref: Append at 16:54:50 on 97/03/27 GMT (by JGREIG at GNKVM) Year 2000 Technical Support Center (TSC5) General information on VisualAge 2000 can be found in INEWS category Year 2000: 03/26/97 YEAR2000 IBM Delivers Tools to Tackle Year 2000 Let us know if we can further assist you. ----- YEAR2000 CFORUM appended at 12:11:54 on 97/04/08 GMT (by LESK at SPPVM1) Subject: Passed return codes that represent julian dates, and year 2000. Ref: Append at 16:55:15 on 97/04/04 GMT (by AMPOP01 at ELINK) Ouch! Even if the leading zeroes were preserved, you would STILL have a Y2K problem in that all the *calling* code would have to recognize '00' as being the year 2000 and you are going to have to change all that calling code! Although you didn't tell us what the platform and language are, I see REXX in there so the first thing you might consider doing is change JULIAN so it does: parse source . how . : : if how^='COMMAND' then RETURN yyddd century else EXIT yyddd instead of: EXIT yyddd Then the code that (presumably) does something like: 'EXEC JULIAN' parm date=rc could be changed to something like this: Parse value julian(parm) with date century . Of course, if the caller can't execute a REXX function, then this won't work! The overall idea is to provide a 'migratable' way of handling the Y2K problem. Les Koehler Advantis - Config Mgt. Development Tampa, Florida Sent on 8Apr1997 at 08:11:53 EDT ----- YEAR2000 CFORUM appended at 23:12:40 on 97/04/08 GMT (by IL35816 at ELINK) Subject: Test Tools and date/time references Ref: Append at 18:25:05 on 97/04/03 GMT (by BARD018 at ELINK) > I don't know how can they handle the case that a program > gets date from CVTDATE, or uses STCK I am in contact with a developer whose product tags onto the end of MVS LOAD and searches the machine code for STCKs and so forth and replaces them with invalid op codes, then traps the invalid op codes with SPIE. (No prizes will be awarded for suggesting coding techniques that this would NOT catch, nor for pointing out that this is probably not supported by IBM.) Charles Mills Firesign Computer Company, San Francisco charlesm@firesign.com ----- YEAR2000 CFORUM appended at 14:31:50 on 97/04/09 GMT (by IL68778 at ELINK) Subject: Test Tools and date/time references Ref: Append at 23:12:40 on 97/04/08 GMT (by IL35816 at ELINK) > I am in contact with a developer whose product tags onto the end of > MVS LOAD and searches the machine code for STCKs and so forth and > replaces them with invalid op codes, then traps the invalid op codes > with SPIE. > > (No prizes will be awarded for suggesting coding techniques that this > would NOT catch, nor for pointing out that this is probably not > supported by IBM.) Do I receive a prize for suggesting that they should be *very* careful that their (E)SPIE doesn't interfere with the application's own recovery mechanisms? I had an interesting experience in that type of situation once, and I must say that I never quite got over it. Gilbert Saint-flour Automated Migration Services IBMMAIL(USS24LG4) IBMLINK(IL68778) ----- YEAR2000 CFORUM appended at 16:11:04 on 97/04/09 GMT (by GBCCDB01 at ELINK) Subject: Test Tools and date/time references Ref: Append at 23:12:40 on 97/04/08 GMT (by IL35816 at ELINK) > I am in contact with a developer whose product tags onto the end of > MVS LOAD and searches the machine code for STCKs and so forth and > replaces them with invalid op codes, then traps the invalid op codes > with SPIE. What about non-code that contains x'B205....' - will these get changed as well - thats what I meant about "guessing" what is a STCK !. How would you separate an EXecuted STCK against a constant of x'B205'. This append was created on the External IBMLink system by Martin Leist Senior Technical Analyst Itex, Norfolk County Council +44 1603 222788 (Martinl.itex@norfolk.gov.uk) ----- YEAR2000 CFORUM appended at 16:43:20 on 97/04/09 GMT (by IL35816 at ELINK) Subject: Test Tools and date/time references Ref: Append at 16:11:04 on 97/04/09 GMT (by GBCCDB01 at ELINK) Void where prohibited. What can I say? Trust me, I am NOT the developer. Sounded risky to me when he approached me. He was having a problem with some sort of task (I am betraying my woeful MVS internals non-guruness here) that did not honor an ESPIE at all. Also no prizes for guessing the name of the vendor. Charles Mills Firesign Computer Company, San Francisco charlesm@firesign.com ----- YEAR2000 CFORUM appended at 13:39:48 on 97/04/10 GMT (by 36601943 at EHONE) ..... YEAR2000 CFORUM modified at 16:03:12 on 97/04/17 GMT (by 36601943 at EHONE) Subject: IMS Database Analyser (DSFEVAL etc.) My customer is running the IMS Database Analyser product (DFSEVAL, DSFSCAN, DSFDBD and DSFHASH). Which versions are year 2000 compliant and ready? Which versions are still supported? Is there a replacement product? Dougie Lawson, IBM Basingstoke, UK. (aka 8LAWSOD at NHBVM2) | Full answer not received yet. ----- YEAR2000 CFORUM appended at 14:07:00 on 97/04/10 GMT (by HENRYF at RIOSYS1) Subject: Bypass2000 (Hal) Please, I like to know if Bypass2000 (Hal-Italy) support PL/I conversion in a MVS/ESA environment. Many tks, Henry de Ferran hferran@vnet.ibm.com ----- YEAR2000 CFORUM appended at 14:16:58 on 97/04/10 GMT (by LESENDEL at LASVM1) Subject: RE: IMS Database Analyser (DSFEVAL etc.) About your question, all that I've found is on the guide *The Year 2000 and 2-Digit Dates...*, that states in the OS/390 and MVS section (appendix A - MVS Platform Products: Operating Systems and Middleware) that the product 5740-XXR: IMS DB Analyser V1 R1 is Year2000-Ready If we find extra info, we'll contact you a.s.a.p. Regards, YEAR 2000 TECHNICAL SUPPORT CENTER LATIN AMERICA T/L: 8-840-7347 // Y2KTSCLA AT ARG WEB SITE: http//www.ibm.com.ar/argweb/anio2000.htm ----- YEAR2000 CFORUM appended at 18:24:11 on 97/04/10 GMT (by ZIELENSK at GDLVM7) Subject: Passed return codes that represent julian dates, and year 2000. Ref: Append at 12:11:54 on 97/04/08 GMT (by LESK at SPPVM1) Since the question of "what platform" was raised, I thought I should comment. (I'm the CMS support rep who made the statement that everything is working as designed.) The platform is VM, and the REXX Exit function strips the leading zeros off the 'rc' variable when the routine is invoked by the CMS EXEC command, which behavior is a requirement of CMS command processing. If the routine is invoked by the REXX CALL function, the Exit function does NOT strip the leading zeros off the 'result' variable (in this case the 'rc' variable is not set). In other words, the EXEC command and the 'rc' variable are CMS things, whereas the REXX CALL function and the 'result' variable are REXX things. Mark Zielenski ----- YEAR2000 CFORUM appended at 18:27:35 on 97/04/10 GMT (by AMPOP01 at ELINK) Subject: Passed return codes that represent julian dates, and year 2000. Ref: Append at 12:11:54 on 97/04/08 GMT (by LESK at SPPVM1) Thanks for the input. I agree that your way would work however we still need to change all applications that call julian. John D'Adamo (AMP Inc., Harrisburg PA.) ----- YEAR2000 CFORUM appended at 20:04:00 on 97/04/10 GMT (by WAWA001 at EHONE7) Subject: Is Julian Date fading? Has there been talk on this forum about how IBM views Julian Date? I heard a rumor that it's not a strategic direction for IBM and that they hope to reduce it's use. Is there any fact to the rumor? If so, could you point me to a reference? Many thanks, Cheryl Watson, Watson & Walker, cheryl@watsonwalker.com Home page: http://www.watsonwalker.com, 800-553-4562 ----- YEAR2000 CFORUM appended at 11:16:53 on 97/04/11 GMT (by 86617495 at EHONE) Subject: Bypass2000 (Hal) Ref: Append at 14:07:00 on 97/04/10 GMT (by HENRYF at RIOSYS1) Hello Henry, The latest information that I have is that Bypass2000 DOES handle PL/1 in an MVS environment (JCL is also handled). For experience, a contact that I have been given is Oliver Schoisswohl (vievma(61821364). For general information a contact is Alberto Gracchi (ithvm05(75805219)) Regards, Ian Junor ----- YEAR2000 CFORUM appended at 12:29:40 on 97/04/11 GMT (by LESK at SPPVM1) Subject: Passed return codes that represent julian dates, and year 2000. Ref: Append at 18:27:35 on 97/04/10 GMT (by AMPOP01 at ELINK) You're going to have to change them anyway, since they can't currently handle the Y2K transition. Even if you *could* get back '00001' as the RC, you would have to add code to treat 00001 as greater than 99365. Since you have to open the code up anyway, might as well do it right. Given the 'problem' you've posed, the best way to approach it would be as I suggested. Les Koehler Advantis - Config Mgt. Development Tampa, Florida Sent on 11Apr1997 at 08:29:39 EDT ----- YEAR2000 CFORUM appended at 15:27:19 on 97/04/14 GMT (by HENRYF at RIOSYS1) Subject: Tool for PC (Inventory) Hi, Does anyone know about a tool that analyze (Inventory-Phase I) a PC environment ? (Clipper, VB ...) Many Tks, Henry de Ferran (hferran@vnet.ibm.com) ----- YEAR2000 CFORUM appended at 18:07:36 on 97/04/14 GMT (by ZIEMBA at BCRVM1) Subject: Is Julian Date fading? Ref: Append at 20:04:00 on 97/04/10 GMT (by WAWA001 at EHONE7) The Language Environment (LE) product has date and time routines that are usable by any of the mainframe languages (COBOL, PL/I, C, Assembler, FORTRAN). The calls use/return Lilian dates (named for the creator of the Gregorian calendar, Luigi Lilio) which are based on the start of the Gregorian calendar (October 15, 1582 is Day 1 for this calendar.) The calls can convert between Gregorian, Julian, Asian and Lilian formats. These calls are good until 9999 (a time when these programs will have been replaced or I won't be around to care anymore.) C. A. Ziemba Austin Y2K Conversion Center ----- YEAR2000 CFORUM appended at 19:53:12 on 97/04/14 GMT (by ACLARK at EHONE7) Subject: Is Julian Date fading? Ref: Append at 20:04:00 on 97/04/10 GMT (by WAWA001 at EHONE7) > If so could you point me to a reference? "HELP REXX DATE". The updated BIF under VM/ESA 2.2.0 can convert from any date format to another but it can only _display_ the current Julian date. We still need to do Julian date math (esp. when working with our TMC). It would have been nice if IBM had included the Julian conversions so we could get rid of some home grown stuff. Adrian Clark - Sears Canada Inc. IBMMAIL(CASRSAJC) / Adrian Clark@e-Mail.com ----- YEAR2000 CFORUM appended at 12:59:16 on 97/04/15 GMT (by SHEL at KGNVMC) Subject: Year 2000 online article Today's Wall Street Journal has an article by the Gartner Group on the Year 2000 problem. See... http://www.wsj.com/public/current/summaries/y2k.htm to read and access other related articles. Sheldon Potolsky ----- YEAR2000 CFORUM appended at 22:18:06 on 97/04/15 GMT (by JFRANCIS at GDLVM7) Subject: Is Julian Date fading? Ref: Append at 19:53:12 on 97/04/14 GMT (by ACLARK at EHONE7) The VM/ESA 2.2.0 REXX Date() implementation for Julian and Century dates has been changed with APAR VM60860. These are now accepted as *input* conversion formats, but not *output* conversion formats. Julian and Century may be specified as output formats when no input date and format is specified. John Franciscovich VM/ESA Development ----- YEAR2000 CFORUM appended at 16:31:51 on 97/04/17 GMT (by ACLARK at EHONE7) Subject: Is Julian Date fading? Ref: Append at 22:18:06 on 97/04/15 GMT (by JFRANCIS at GDLVM7) Thanks for the APAR John. It'll be a big help to us. We're trying to get our central date routine to use all IBM Date functions to save us having to make changes for Y2K. This extra APAR will be a big help towards that. Now.... we just need the REXX compiler to accept the new BIF syntax in the base 2.2.0 code (and this APAR). But I assume that'll be coming in time. Adrian Clark - Sears Canada Inc. IBMMAIL(CASRSAJC) / aclark@null.net ----- YEAR2000 CFORUM appended at 09:56:07 on 97/04/18 GMT (by AWHAKIM at EOSVM) ..... YEAR2000 CFORUM modified at 09:58:49 on 97/04/18 GMT (by AWHAKIM at EOSVM) Subject: GC28-1251-06 The April 1997 edition of the Year 2000 Guide has just reached me in LIST3820 format. The file includes half a page of error messages indicating that Page Segments "front811" and "back811" were not found. Does this make a significant difference to the body of the document? Alan Hakim, IBM Global Services, VM Support, Portsmouth, UK. ----- YEAR2000 CFORUM appended at 10:17:51 on 97/04/18 GMT (by ZOOT at KGNVMC) Subject: GC28-1251-06 Alan, et al., With apologies, when I created the LIST3820 file, I forgot to delete the error messages. These two messages (FRONT811 and BACK811 not found) simply refer to the placement of the graphic that is printed on the "orderable" hardcopy. In a LIST3820, the graphic is unprintable and hence the error messages. The content is exactly the same. Don B. Pizzuto Y2K Information Development IBM Poughkeepsie ----- YEAR2000 CFORUM appended at 09:03:30 on 97/04/22 GMT (by GBOAKR00 at ELINK) Subject: IMS V5 Somewhere its documented that to be Y2000 compliant you need to be at service level PUT9612 or greater. My Y2000 project manager wants this in black and white but I can't find where I originally read it. Can anyone help? This append was created on the External IBMLink system by Shawn Grinter Millenium Systems, UK Tel: +44 171 821 6346 Fax: +44 171 976 5769 ----- YEAR2000 CFORUM appended at 10:43:24 on 97/04/23 GMT (by 73850840 at EHONE) Subject: Y2000 compliant DOS / Windows product lists Hello, couldn't find the list for DOS / Windows products in the "Year 2000 4-digit year - Planning & Implementation" I'm particularly interested in the following DB2 SDK/DOS V1.2 DB2 CAE/DOS V1.2 DB2 SDK/WIN V2.1.1 DB2 CAE/WIN V2.1.1 IBM TCP/IP for DOS V2.1.1 IBM TCP/IP for DOS Programming ToolKits V2.1.1 IBM TCP/IP for DOS NFS Kit V2.1.1 (In Appendix A, a footnote mentioned TCP/IP V2.1 is withdrawn from service, and the replacement product is INTERNET CONNECTION SECURED SERVER!!!???) Are they Y2000 ready? Thanks! Teresa Lam HKGVM8(LAMTBS) teresal@vnet.ibm.com ----- YEAR2000 CFORUM appended at 20:40:17 on 97/04/23 GMT (by Y2KTSC3 at STLVM6) Subject: IMS V5 Ref: Append at 09:03:30 on 97/04/22 GMT (by GBOAKR00 at ELINK) >Somewhere its documented that to be Y2000 compliant you need to >be at service level PUT9612 or greater. >My Y2000 project manager wants this in black and white but I can't find >where I originally read it. Can anyone help? Please check the PSP bucket YR2000MVS in ServiceLink of IBMLINK. Year 2000 Technical Support Center ----- YEAR2000 CFORUM appended at 14:08:17 on 97/04/24 GMT (by GBOAKR00 at ELINK) Subject: IMS V5 Ref: Append at 20:40:17 on 97/04/23 GMT (by Y2KTSC3 at STLVM6) Sorry the PSP bucket gives me information about some fixes to apply, my project managers wants a statement that IMS V5 at maint Level YYMM is Y2000 compliant. As I said before I seem to recall some such statement refering to maint level 9612, but I don't really care what the specific level is just the statement. IMS V5 stated initially that Y2000 compliance would be deliverey via the service process - has that process finished? This append was created on the External IBMLink system by Shawn Grinter Millenium Systems, UK Tel: +44 171 821 6346 Fax: +44 171 976 5769 ----- YEAR2000 CFORUM appended at 12:00:42 on 97/04/25 GMT (by SEICAE00 at ELINK) Subject: OS/390 and YEAR2000 Hello | This might be a stupid & unnecessary question, but: I'm involved in a Year2000-project at our company (as MVS Systemsprogrammer), and a couple of days ago I ordered OS/390 Release 3. According to IBM's "S390-Site" on Internet OS/390 Release 2 is "YEAR2000 READY" (http://www.s390.ibm.com/stories/year2000/mvs.html) That makes me believe that OS/390 Release 3 MUST be ready for YEAR2000. But how true is it ? Is there any "breakdown" of the various components in OS/390 R2 & R3 listed somewhere ? Or is PSP the only place ? As I run (a lot of) SMP/E in my profession I think it would be a good suggestion to IBM to create a new SOURCEID named YR2000 (or something like it) and add that to all the PTF's involved in getting products ready for Year2000 (?). Maybe it's already done, but I haven't seen any. Sorry for placing this question here but IBM reorganised again so now we have no SW/SE. All SW-related questions etc. should go through our HW/CE. That's all Thanks & Take care This append was created on the External IBMLink system by Bo Stamhagen SystemsProgrammer MVS ICA Handlarnas AB (Stockholm, Sweden) Tel: 46-8-7221174 E-Mail: bo.stamhagenŽica.se ----- YEAR2000 CFORUM appended at 23:40:22 on 97/04/28 GMT (by Y2KTSC3 at STLVM6) Subject: IMS V5 Ref: Append at 14:08:17 on 97/04/24 GMT (by GBOAKR00 at ELINK) >IMS V5 stated initially that Y2000 compliance would be deliverey via >the service process - has that process finished? Yes, that process has finished. The official statement of the Year 2000 readiness (there is no Year 2000 Standard to be 'compliant' to) is the manual GC26-1251, which is available on the Y2KTSC Web Site or in hard copy from IBM. Year 2000 Technical Support Center ----- YEAR2000 CFORUM appended at 00:59:53 on 97/04/29 GMT (by CHRISTIN at GDLVM7) Subject: IBM ITSO Residency Opportunity - Year 2000 Migration (This is cross posted on VMSHARE, VMESA-L, VMARENA, YEAR2000 & sent to the VM interested parties distribution list). We're are passing along this special invitation from our colleagues in the IBM International Support Organization who have a "Year 2000 migration" opportunity. Perhaps you can be a participant in the next Redbook. ------------------ITSO Residency ----------------------------- Date: 04/29/97 Stephen E. Record +49-7031-16-1204 SRECORD at BOEVM3 ITSO Boeblingen ITSO RESIDENCY ANNOUNCEMENT --------------------------- Residency 97-MR-1105-R: VM/ESA Year 2000 Migration Leader: Stephen Record (SRECORD at BOEVM3), Boeblingen ITSO Center Residency Residency Duration Number of Nominations Candidate start end in weeks residents close selection --------- --------- -------- --------- ----------- --------- 06/09/97 07/18/97 6 3 05/09/97 05/12/97 For especially well-qualified candidates, the above dates and duration are negotiable. Also, ITSO will favorably consider the nomination of customers, Business Partners, and Independent Software Vendors (ISVs). DESCRIPTION: ------------ The purpose of this residency is to provide guidance to IBM customers and field specialists on how to migrate a real (not hypothetical) VM system and its applications to a Year 2000 Ready state. There already exists a wealth of information, available at the IBM Year2000 World Wide Web site among other places, on the problems posed by the imminent approach of the year 2000. What there is relatively little of so far, however, is documented experience of assessing and resolving Year 2000 problems in a real setting. This residency will help to address that deficit. The residents will migrate an existing VM/ESA system to VM/ESA V2.2.0, the Year 2000 Ready release of VM/ESA, and then will work on migrating a set of application programs on that system, assessing their Year 2000 vulnerabilities and formulating a plan to correct any problems and test the results. OBJECTIVES ---------- The output of this residency will be a Redbook that will document in considerable detail the experience of migrating a VM/ESA system with applications to a fully Year 2000 Ready state. The Redbook material will also be published incrementally on the World Wide Web as Redpieces while the residency is progressing, thus making the experiences of the residents available to others both inside and outside IBM as rapidly as possible. Information from the Redbook will also be distilled into teaching material for a workshop on VM and VSE Year 2000 Migration to be offered later in 1997. BENEFITS TO RESIDENT -------------------- The residents will acquire knowledge and practical understanding of the process of migrating a VM system to a Year 2000 Ready condition, and in addition will gain hands-on experience in assessing and correcting Year 2000 exposures in real application programs. The residents should find it straightforward to interpret this experience for the further benefit of their customers or colleagues back home who are themselves becoming engaged in Year 2000 migrations. The ITSO is seeking an IBM customer with a VM/ESA system that could serve as the case study for this Year 2000 Migration residency. The system and a subset of its applications would be cloned on a test system in Boeblingen, where a representative from the customer site would work with the other residents to perform the migration. The additional benefit to this customer would, of course, be substantial assistance in achieving Year 2000 readiness of its production VM/ESA environment. RESIDENT PREREQUISITES: ----------------------- Solid knowledge of VM/ESA and an understanding of the Year 2000 support in VM/ESA V2.2.0 is required. Both systems and application programming skills will be important in performing the migration. Expertise in one or more common programming languages (Rexx, C, PL/I, Fortran, Cobol, or Assembler) and application-enabling products will be extremely helpful. Language skills: Fluency in writing and speaking English is required. Suitable for customers: Yes Costs: ITSO will pay travel (according to IBM Travel Policy) and living expenses for residency participants. ITSO manager: Herbert Kratzer (KRATZER at BOEVM4) FOR MORE INFORMATION -------------------- For further information about this residency, please contact the VM residency leader, Stephen Record, either by Internet: srecord@vnet.ibm.com r Vnet: SRECORD at BOEVM3 telephone: (+49-7031-16-1204). ----------End of ITSO note --------------------------- ------------VM & VSE Technical Conferences ------------- A reminder about the upcoming VM and VSE Technical conferences. Seats are still available for both Kansas City (May 13-16) and Mainz, Germany (16-18 June). Registration information is available on the web sites for VM and VSE. VM: http://www.vm.ibm.com VSE: http://www.ibm.de/go/d00000166 Or, contact Pam Christina at vmesa@vnet.ibm.com. Regards, PLC Pamela Christina Visit VM's home page at url: http://www.vm.ibm.com IBM S/390 Development- VM/ESA Endicott 607-752-6125 (t/l 852) .PC @ VMSHARE | christin@gdlvm7.vnet.ibm.com | USIBMWKS @ IBMMAIL ----- YEAR2000 CFORUM appended at 02:40:42 on 97/04/29 GMT (by LEESOHN at SULVM1) Hello, I'm a member of Y2k Team from IBM Korea. I am looking for sample cases in which the efficiency of tools can be explained. My client, the biggest steel manufacturer in Korea, are going to start Year2000 project. But they are not going to understand the necessity of using tools without some real case of telling about the productivity. I need any kind of cases or information sources to be referenced which I can persuade my client ASAP. The confidentiality of client to be referenced will be guaranteed. Any kind of your information would be highly appreciated. Thank you. Sean Lee. ----- YEAR2000 CFORUM appended at 14:58:26 on 97/04/29 GMT (by DTERECK at TORVM3) One of our customers is trying to make a decision regarding a conversion from VS Cobol II to COBOL for MVS, as part of their Year 2000 project. They are (obviously and rightly) worried about adding to the complexity and risk of performing the conversion at this time. They asked us if we knew of anyone else who has done this conversion. I am looking for a reference account of someonene who has gone through this conversion. Someone who would be willing to tell me (us) their experiences (both good and bad) with such a conversion. This customer has (relatively) recently gone through the major conversion from OS/VS Cobol to VS Cobol II (completed within the last year). If anyone has any such contact, please respond here, or call me. Thnx...Dan Tereck ISM Manitoba - Part of the IBM Global Services Team (204)946-6854 ----- YEAR2000 CFORUM appended at 16:25:29 on 97/04/29 GMT (by DTERECK at TORVM3) Hi... One of our major customers, for whom we provide and manage a large MVS environment for their processing requirements, are well underway on a Year 2000 project. Our strategy for providing a Year2000 test environ- ment for them, is to utilize their existing "normal development environ- ment" (test program libraries, test data, etc.) for their unit/regression and for their initial year 2000 testing (using a date simulation tool... and of course a test copy of LE). Then our strategy includes the use of a separate LPAR that the customer can use for "Year 2000 confirmation testing". It will have a complete portfolio of the system software they use, all at Year 2000 ready levels. That's the background. Our customer has inquired as to the use of a P/390 box to use for all of their Year 2000 application mtce and testing - whether or not we would be interested in supplying, configuring, and supporting this for them. This goes against our strategy, but we must consider this alternative. We did consider it last fall, but the software licensing costs made it impractical financially. We are currently investigating this further to see if anything has changed, but are interested to know if anyone else in our family has chosen this route...or considered it. I'd be interested in hearing any comments on this. Thnx...Dan Tereck ISM Manitoba - Part of the IBM Global Services Team (204)946-6854 ----- YEAR2000 CFORUM appended at 19:10:42 on 97/04/29 GMT (by JCRANDL at ATLVMIC1) Subject: Y2K testing methodology My customer has asked if there are any documents available that give examples of specific testing methodologies and techniques for Y2K compliance. With the understanding that many IBM product groups have certified their products as Y2K compliant, there must be a lot of experience on deciding what to test, how to test, developing test cases, evaluating results, etc. Are you aware of any of this that we could provide to customers? Thanks. Jim Randle, Memphis ISAM ----- YEAR2000 CFORUM appended at 13:17:13 on 97/04/30 GMT (by JFRANCIS at GDLVM7) Subject: Y2K testing methodology Ref: Append at 19:10:42 on 97/04/29 GMT (by JCRANDL at ATLVMIC1) If you go to the Year 2000 Technical Support Center Home Page (http://www.software.ibm.com/year2000), and click on methodology, you'll find information on general Year 2000 testing methodologies and considerations. IMHO, this is also a great site to find some of the general Year 2000 information (conversion, COBOL, testing, etc.) that has been requested recently in this forum. John Franciscovich VM Development ----- YEAR2000 CFORUM appended at 13:42:02 on 97/04/30 GMT (by 9WARLTK at CROVM4) Subject: VisualAge 2000 for MVS, VM, AS/400 & OS/2 Ref: IBM Press Announcement 26 March, 1997 The COBOL Newsletter Issue # 6 has a lot of information about VisualAge 2000 and the Year 2000 challenge. This is a glossy newsletter containing illustrations and photographs. To obtain your copy, please send a fax to USA 408-463-2425 stating: Name Company Address Country Postal Code Telephone number Fax number Email Address and say if you would like a free copy of the IBM COBOL CDs for: VisualAge for COBOL for OS/2 IBM COBOL Set for AIX Regards, Keith Warltier, COBOL Restructuring & Year 2000 Consultant 9WARLTK@CROVM4 or GBIBMTJ2@IBMMAIL or KEITH_WARLTIER@UK.IBM.COM ----- YEAR2000 CFORUM appended at 13:51:08 on 97/04/30 GMT (by DKSOD01 at ELINK) Subject: Y2K testing methodology Ref: Append at 19:10:42 on 97/04/29 GMT (by JCRANDL at ATLVMIC1) Hi, IBM offers a document called The year 2000 and 2 digit dates: A Guide for Planning and Implementation Document number: GC28-1251-00 It contains very much information on this issue and it also has references to non-IBM publications and Internet WEB pages. Best regards from KIMI This append was created on the External IBMLink system by Kim V. Iversen SOS Data ApS - Homepage: HTTP://INET.UNI-C.DK/õSOSDATA Gl. Kongevej 123, 1 tv. - E-mail : SOSDATA.øINET.UNI-C.DK DK-1850 Frederiksberg C - Phone : +45 31 23 34 91 - Fax: +45 31 23 22 66 ----- YEAR2000 CFORUM appended at 14:34:17 on 97/04/30 GMT (by JCRANDL at ATLVMIC1) Subject: Y2K testing methodology Ref: Append at 13:17:13 on 97/04/30 GMT (by JFRANCIS at GDLVM7) Thanks, John for the pointer to the home page. I'd forgotten that it was useful for info other than getting the planning guide. I did follow the two links Testing Considerations - a few general tips Testing Stages - three stages for Year 2000 testing I also viewed the white papers referenced in the Customer Guidance Paper link. The customer was hoping to find something with more detail, with the understanding that it might be very specific to a product or system. Jim Randle, Memphis ISAM ----- YEAR2000 CFORUM appended at 15:26:20 on 97/04/30 GMT (by JCRANDL at ATLVMIC1) Subject: Y2K testing methodology Ref: Append at 13:51:08 on 97/04/30 GMT (by DKSOD01 at ELINK) Thanks, KIMI, We'll re-read the planning guide and see if anything was slipped into it. Jim Randle, Memphis ISAM ----- YEAR2000 CFORUM appended at 16:40:59 on 97/04/30 GMT (by TMALLARD at STLVM27) Subject: Y2K testing methodology Ref: Append at 13:17:13 on 97/04/30 GMT (by JFRANCIS at GDLVM7) You can also find detailed testing information on the VisualAge 2000 Web page. From the http://www.software.ibm.com/ad/cobol, select "Meeting the COBOL Year 2000 Challenge" at to top of the page or go to: http://www.software.ibm.com/ad/cobol/y2k/ In either case, select "Test and Integration" on the VisualAge 2000 page. Terry Allard