----- YEAR2000 CFORUM appended at 07:41:47 on 97/08/01 GMT (by BEUMII00 at ELINK) <10172> Subject: Access to Y2K Dasd - How far does one have to go ? Ref: Append at 14:12:16 on 97/07/31 GMT (by GAD at KGNVMC) Thanks Greg for the Info So if we plan to test on a separate LPAR, using DASD isolated from the rest of our Production System it will not cause any damage. We also plan to make regular full volume copies from our production system to that test environment. Each time we do this we have to initialize all target volumes with DSF. Does it matter which DSF (the one from the Non Y2K compliant system or the one of the Y2K compliant system) we use ? As far as we talk about the same device types on both sides. This append was created on the External IBMLink system by Francois Vennekens, Systems Engineer UNION MINIERE A. Greinerstraat 14 - 2660 Hoboken (Belgium) Ph +32-3-8217887 Fax +32-3-8217816 - E-Mail Francois.VennekensėUM.BE ----- YEAR2000 CFORUM appended at 10:48:47 on 97/08/01 GMT (by GAD at KGNVMC) <10173> Subject: Access to Y2K Dasd - How far does one have to go ? Ref: Append at 07:41:47 on 97/08/01 GMT (by BEUMII00 at ELINK) Any version of DSF can be used to reinitialize the volumes. The intent is to destroy any datasets that may have gotten year 2000 dates into them in some way. This includes in the data, PDS directories, and the VTOC. The writing of a new VTOC using DSF is the easiest way to ensure this. Greg Dyck MVS BCP Kernel and CURE Support ----- YEAR2000 CFORUM appended at 13:27:42 on 97/08/01 GMT (by BEUMII00 at ELINK) <10174> Subject: Access to Y2K Dasd - How far does one have to go ? Ref: Append at 10:48:47 on 97/08/01 GMT (by GAD at KGNVMC) Thanks Greg, but there was another question that popped up. Is there a need for separate DASD Control Units, or is a VARY OFFLINE/ONLINE of the affected volumes sufficient to switch them over from environment (old) to environment (new) ? This append was created on the External IBMLink system by Francois Vennekens, Systems Engineer UNION MINIERE A. Greinerstraat 14 - 2660 Hoboken (Belgium) Ph +32-3-8217887 Fax +32-3-8217816 - E-Mail Francois.VennekensėUM.BE ----- YEAR2000 CFORUM appended at 18:40:21 on 97/08/01 GMT (by CROBERTS at BLDVMA) <10175> Subject: sliding window I do not think I fully understand the sliding window methodology on the Y2K functionality within DFSORT, or program century date routine. EXAMPLE: 1997 - 43 = 1954 CONVERTING EVERYTHING >= '54' TO CENTURY '19', AND EVERYTHING < '54' TO CENTURY '20'. RESULTS: JANUARY 1, 1954 THROUGH DECEMBER 31, 1999 JANUARY 1, 2000 THROUGH DECEMBER 31, 2053 EXAMPLE: 2000 - 43 = 1957 '57' EXAMPLE: 2042 - 43 = 1999 '99' EXAMPLE: 2043 - 43 = 2000 '00' <-----(PROBLEM)?? In 2042, data that is 1998 (44 years old) will become 2098. Expiration dates are in the future. You would need to check for something that is too far in the future, if that can be determined. How do you work with rate ranges which extend into the future or are intended to be infinite? Can anyone help me with this? Thanks. carol roberts Dept:f82 SN:216192 Div:10 Ext:5 - 8010 ----- YEAR2000 CFORUM appended at 19:31:16 on 97/08/01 GMT (by YAEGER at SJFEVMX) <10176> Subject: sliding window Ref: Append at 18:40:21 on 97/08/01 GMT (by CROBERTS at BLDVMA) I'm not sure I fully understand what you're asking, but perhaps I can help anyway. The century window concept is based on a window of 100 years. Two-digit year data which fits into a 100-year span can use a century window; two-digit year data which exceeds a 100-year span cannot, and will probably require conversion to four-digit years. DFSORT offers both a fixed and sliding century window. The fixed century window doesn't change. If you specify: Y2PAST=1950 you get a Century Window of 1950-2049 in 1997, 1998, and so on. The sliding century window specifies a century window that advances one year each year. If you specify: Y2PAST=47 you get a century window of 1950-2049 in 1997, 1951-2050 in 1998, and so on. You can set the century window to start at any year you like with either of these options and set different century windows for different DFSORT applications. But with either of these methods for using the century window, if your dates cannot be encompassed by a 100-year span at any point, the century window concept will not work for those dates. Frank L. Yaeger - DFSORT Team (Specialties: ICETOOL, OUTFIL, Y2K :-) => DFSORT/MVS is on the WWW at http://www.storage.ibm.com/dfsort/ ----- YEAR2000 CFORUM appended at 11:39:04 on 97/08/05 GMT (by NL5OTR01 at ELINK) <10177> Subject: OV/MVS workgroup PGM 1.1.0 I just read in the 2 digit guide that OV/MVS workgroup PGM 1.1.0 (5622-053) is not year 2000 compliant and that the service is withdrawn with respect to this product. In our company this is an important product, so the question is if there is another product that offers the same functionality and that is year 2000 compliant. Thanks in advance, 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:41:05 on 97/08/06 GMT (by CBS at SJEVM5) <10178> Subject: Access to Y2K Dasd - How far does one have to go ? Ref: Append at 13:27:42 on 97/08/01 GMT (by BEUMII00 at ELINK) Although technically you could use the same control units, I strongly recommend that you do not. This is for various reasons: * We ordinarily recommend that you define all addresses on a control unit to all systems. This is to ensure that all systems are aware of important status information * Although you *can* vary volumes (or even paths) on and offline from different systems, the risk that you might accidentally enable a volume to the wrond system is quite high. The cost of buying additional storage is really quite minimal when compared with the cost of the damage that might occur from such accidental enabling of incorrect volumes. * You may want to look at the advantages of using SnapShot to improve the productivity of your Y2K testing. Since you probably are not using RVA today, different disks would be needed to use SnapShot. * A customer I spoke with was very attracted by the idea of using XRC from current (3990-attached) disk to copy data into RVAs that would be used for testing. By careful use of the RVA and SnapShot, they will be able to have a test system that can be refreshed automatically with up-to-date apps and that can be isolated from production systems but without any need to keep re-initializing volumes using ICKDSF or re-copying data to repeat test scenarios. Chris Saul, Storage Systems Division, San Jose http://saul.sanjose.ibm.com/ ----- YEAR2000 CFORUM appended at 15:29:16 on 97/08/07 GMT (by Y2KTSC5 at STLVM6) <10179> Subject: OV/MVS workgroup PGM 1.1.0 Ref: Append at 11:39:04 on 97/08/05 GMT (by NL5OTR01 at ELINK) We have updated information since the Customer Guide was published in April, 1997 related to 5622-053. CURRENT OV/MVS is Y2000 ready, but it requires a release of OV/MVS that is year 2000 ready. Display of year is both 2 and 4 digits. Year 2000 Technical Support Center (TSC5) ----- YEAR2000 CFORUM appended at 19:23:04 on 97/08/07 GMT (by PIZZAZZ at STLVM20) <10180> Subject: Re: We IPL'ed with Y2K dates on our OLD hardware. Ref: Append at 22:25:54 on 97/07/28 GMT (by PIZZAZZ at STLVM20) There has been a follow-on append on the discussion list: ------------------------------------------------------------------------ Date: Tue, 29 Jul 1997 15:07:14 +0200 To: y2ksasig@cinderella.co.za, y2k@leba.net, listmanager@zebra.co.uk From: Chris Anderson Subject: Re: Year 2000 testing Sender: owner-listmanager@zebra.co.uk Precedence: bulk At 11:18 1997/07/29 +0000, Mike Bredenkamp w > I read a recent append you made on a Year2000 discussion list (it is >currently making the rounds on the IBM internal discussion lists). >I saw that you have done some extensive testing on VSE and VM systems that are >documented non-compliant. If I understood you correctly, you imply that the >problems found were essentially minor and cosmetic. Shriek. Absolutely not. I was talking in very general terms and was merely discussing the possibility of going into the nitty gritty of what can and cannot be done, including hacking the code. Problems are definitely not minor nor cosmetic. We were discussing whether the thing was worth pursuing at all. Good grief. I am the person that has been screaming since 1986 that the beastly systems are NOT compliant and that we had better do something about it! Please understand that I only mentioned this topic because there are certain applications that can never run under the "new" memory management model that came out to support >16M memory. When locore mapping was changed with VM/SP release 6 a whole class of apps became unmigratable. (Remember - we almost lost EP, and it had to be fiddled into a named space. A cute kludge, but not universally applicable.). Certain "black box" applications are locked into 16M top limit architecture. The ESA CP option solved some of this, but it no longer exists. The CP control blocks are just not there any more. There is just no migration path for this stuff. Unfortunately some of it is mission critical. What I was saying was that it is possible to run applications on VM/SP REL5 at PLC 529 that will survive transition PROVIDED you do certain things and omit others. VM ipls to 2000-01-01 and runs. However VSAM will corrupt or get bad time stamps over time unless you redefine your master catalogs and rebuild your spaces AFTER 2000. I actually said that the display sequence of FLIST (or CMS directory listings) is cosmetic and can be lived with. A very minor aspect. I thought I made it clear THERE ARE SOME REAL LULU BUGS that will come out and bite you. This is a very high risk scenario. It can only be entertained by the absolutely desperate who have no other options. It is Unsupported, Unrecommended and excessively Ugly. But if the alternative is survival, could be hacked around. In a nutshell people should run screaming before contemplating this option. But in an emergency, a plan could be made. > I hope you are right. There >is at least one thing I must warn you about. On MVS systems, VSAM catalogs will >NOT even open on/after year 2000. I know you say that your systems does not use >catalogs, but if you have any VSAM applications, especially under VM, you >should maybe consider testing this as well? Agreed. But we were discussing the /SP series, where system catalogs were not yet integrated with VSAM. Old MVS cannot be made compliant without hacking. VM and VSE did not use the system catalog. There was no tape catalog or GDG support, unless through some third party. VM used directory mapping for disk allocation and VSE used direct extent allocation and partition standard labels. Although there was a minimal facility for creating 'profiles' for sequential datasets and temp files, but handled through the VSE/VSAM catalog and not a system catalog. VM uses VSE/VSAM and this does run. (Given caveat above). Let me not bore you with all the horrors to be found in Fastcopy/Restore, ICCF master file maintenance et al. I had not got round to discussing MVS but made passing comment that it was more problematical than VM or VSE, particularly because of the use of the dreadful yyddd in just about everything. But if you have source and a suicidal personality you could hack it into working. A local guy got public domain MVS to run on 3380. Where there's a will, there's a way. How desperate are these people? > >For myself, I have put in leave for a few months from Oct '99 to Mar'00, I have >already booked a large farmhouse with a vegetable garden and a few cows and >goats. :) Somewhere in a country where the gun ownership laws are relaxed, so >I can have a shotgun and a rifle for hunting. Well, I can dream, can't I? > Sounds wonderful. As long as you don't hunt other peoples cows. B>) >Mike > __________________________________________________ > Mike Bredenkamp - Transaction Systems Centre of Competency >E-mail: Mike_Bredenkamp@uk.ibm.com >Tel: +44 (0)1962 816436 Internal: >(7)246436 >Fax: +44 (0)1962 818191 >Web: http://www.isc.uk.ibm.com/isc/tscoc/tscoc.html > > ------------------------------------------------------------------------ Chris Anderson email: slug@fast.co.za Y2K Cinderella Project webmaster@cinderella.co.za http://www.cinderella.co.za Striving for Year 2000 Compliance ------------------------------------------------------------------------ Karen R. Barney ----- YEAR2000 CFORUM appended at 23:01:44 on 97/08/07 GMT (by PATRICK at ISSCAUS) <10181> Subject: General hardware and system software compliance I have an URGENT need for some information (why is it that you get asked to help on the day the proposal is due??). Does anyone have any documentation on how to test/validate hardware (ibm and other) and system software (ibm and other) for Y2K compliance??Most of the stuff I've seen is for applications. Any help would be greatly appreciated. Patrick O'Donnell ----- YEAR2000 CFORUM appended at 13:53:30 on 97/08/08 GMT (by SAKC3II at ELINK) <10182> Subject: Time Machine Access I am starting to plan the construction of our time machine. Once the LPAR is running with a future date, we believe we will occasionally need access to the volumes from our production systems. This is for backup purposes or to refresh application data. Does anyone forsee a problem with a current system using this dasd? As I see it, as long as the LPAR is shut down this should be doable. While I'm at it, any other pearls of wisdom of the building of this lpar from people who have already done this? Alan Schwartz John Alden Systems Company. ----- YEAR2000 CFORUM appended at 14:12:03 on 97/08/08 GMT (by Y2KTSC5 at STLVM6) <10183> Subject: Year 2000 Support Ref: Append at 17:53:38 on 97/07/28 GMT (by CAMEYERS at CHGVMIC1) PRODUCT DESCRIPTION YEAR 2000 READY 5799-WWL VSMR 1.3.3 No This product has been withdrawn from marketing and will not be year 2000 tested by IBM. 5668-896 APE V1 Yes 5668-808 APE V2 APE does not have any interfaces which return dates directly, however, fields which are dates. These fields which are dates. These applications should be examined for year 5688-082 2.3.0 Common Lib No Version 3.1 is first Year 2000 ready release, or migrate to Language Environment for MVS & VM. 5668-897 Info Center/1 1.1.5 No This product has been withdrawn from marketing & service and will not be year 2000 tested by IBM. 5648-092 AS V4 AS 4.1.0 No AS 4.2.0 Yes GPARS 1.2.1 ?? We need further information. Can you provide us more of a description for GPARS or a product id. You may send your product inquirires directly to us, the Year 2000 Technical Support Center. We can be reached by phone (1-800-426-4968) or via e-mail (Y2KTSC@US.IBM.COM). Year 2000 Technical Support Center ----- YEAR2000 CFORUM appended at 14:29:50 on 97/08/08 GMT (by SORBER at ENDVM5) <10184> Subject: Year 2000 Support Ref: Append at 14:12:03 on 97/08/08 GMT (by Y2KTSC5 at STLVM6) As I understand it, below are the various states of products: ------------------------------------------------------------- Current/Supported - Orderable / Supported Withdrawn from Marketing - Unorderable / Possibly Supported Discontinued (same as Withdrawn from Service) - Unorderable and Unsupported As Is - Orderable but Unsupported ------------------------------------------------------------------------ If we agree, then that begs the following question, prompted by an earlier append. Here's the excerpt: "5799-WWL VSMR 1.3.3 No This product has been withdrawn from marketing and will not be year 2000 tested by IBM." Am I to understand that if a program has been withdrawn from marketing no effort will be made to review/make it for y2k readiness? What if it's still in service, and support is still offered/available? I guess I need a clearer definition of terms/intent here. Thanks Tom Sorber ----- YEAR2000 CFORUM appended at 20:08:41 on 97/08/08 GMT (by WFARRELL at KGNVMC) <10185> Subject: Time Machine Access Ref: Append at 13:53:30 on 97/08/08 GMT (by SAKC3II at ELINK) Reply-To: wfarrell at ibmusm10 As I understand it, you should never allow the system with the future date to access DASD that your production system will use. If the test system needs data from the production DASD you should transfer it via dump/restore to another DASD volume. Walt Farrell Internet: wfarrell@us.ibm.com IBMMAIL: USIB3H89 ----- YEAR2000 CFORUM appended at 20:58:58 on 97/08/08 GMT (by CBS at SJEVM5) <10186> Subject: Time Machine Access Ref: Append at 13:53:30 on 97/08/08 GMT (by SAKC3II at ELINK) As you've seen, I recommend that you use something like remote copy to transfer data from production to test systems, potentially in conjunction with SnapShot if you're using an RVA for testing. As Walt says, the only other sensible way to transfer data is with dump/restore (via tape). You don't want to share disks between those two systems. Even if you take great care, it's just too error prone and the costs of making those errors are very high, much higher than the costs of a less error prone solution. Chris Saul, Storage Systems Division, San Jose http://saul.sanjose.ibm.com/ ----- YEAR2000 CFORUM appended at 00:52:30 on 97/08/11 GMT (by GBCADH00 at ELINK) <10187> Subject: Year 2000 Support Ref: Append at 14:12:03 on 97/08/08 GMT (by Y2KTSC5 at STLVM6) Gpars is product number 5798-CPR. It has been out of support for some time, but is a pre-req to IMSPARS 5798-CQP - which I believe is supported. The IMSPARS people have fixed things iin the past which have needed to be fixed. 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 15:36:10 on 97/08/11 GMT (by 70611526 at EHONE) <10188> Subject: Number of days until 01/01/2000 Ref: None Hello, when controling a Y2K project, or any kind of project, it is sometimes necessary to compute from todays date to target date (01/01/2000) the number of working days, the number of working nights, the number of weekends, etc. in order to end the project at the right date. I have browsed the forum and found some entries and algorithm for leap year and date format conversion. Has someone worked on calendar, that includes Easter and all dependant holidays? All suggestions are welcome. Regards, Jacques L. Bouchard ----- YEAR2000 CFORUM appended at 02:25:25 on 97/08/12 GMT (by Y2KTSC2 at STLVM6) <10189> Subject: Year 2000 Support Ref: Append at 14:29:50 on 97/08/08 GMT (by SORBER at ENDVM5) You write: < "5799-WWL VSMR 1.3.3 No < year 2000 tested by IBM." < < Am I to understand that if a program has been withdrawn from marketing < no effort will be made to review/make it for y2k readiness? What if < it's still in service, and support is still offered/available? < I guess I need a clearer definition of terms/intent here. Thanks There is no universal meaning to "Withdrawn from Marketing" as it relates to Year 2000 Readiness. The same can be said about "Withdrawn from Service". Product developers and managers can identify obsolete products as being Year 2000 Ready or not Ready. It all depends on the available resources available to them to perform testing or analysis. Products which are no longer serviced (or will not be serviced after 12/31/1999) are under no corporate mandate to be made Year 2000 Ready. Year 2000 Technical Support Center (TSC2) ----- YEAR2000 CFORUM appended at 19:38:12 on 97/08/12 GMT (by SORBER at ENDVM5) <10190> Subject: Year 2000 Support Ref: Append at 02:25:25 on 97/08/12 GMT (by Y2KTSC2 at STLVM6) Given that the y2k readiness plans of a particular product come from the developer, based on the final destiny that product, may I suggest that you have (on the web?) a list of products that will officially never be made y2k ready. To me, as a part of a team that is managing the y2k readiness of hundreds of products on our systems, such a list would be just as important to us as (the former) appendix A in the planning guide. Also, the sooner I know what products will never be y2k ready, the sooner I can plan alternatives. I am aware that the planing guide did identify MVS products that had been withdrawn, but now, since your reply to my last append, I can't assume that those entries reflect official posture re y2k readiness intent. Bottomline: I am requesting a list since your last append basically stated that we can't necessarily go by such terms as 'withdrawn from marketing' or 'withdrawn from service' when it comes to determining if a product will be made y2k ready (if it isn't already). Thank you for your attention. Tom Sorber ----- YEAR2000 CFORUM appended at 09:15:56 on 97/08/13 GMT (by NEWSPOST at IPNET) <10191> Subject: Re: Number of days until 01/01/2000 From: Steve Swift Ref: Append at 15:36:10 on 97/08/11 GMT (by 70611526 at EHONE) Working out the number of working days until a certain date gets discussed regularly on various forums, and solutions are offered. Maybe you'd do better to ask in the REXX forum, for example. I run a YR2000 awareness application that I wrote for OS/2 all the time. It is currently telling me that there are 870 days, 13:43:20 hours left until Midnight 31/12/1999. It was chilling when it dropped below 1000 days, and those days *include* weekends and holidays... X-NNTP-Server: news.uk.ibm.com NNTP-Posting-Host: hedgehog.ts.uk.ibm.com ----- YEAR2000 CFORUM appended at 09:28:43 on 97/08/13 GMT (by NEWSPOST at IPNET) <10192> Subject: Re: Number of days until 01/01/2000 From: Steve Swift Ref: Append at 09:15:56 on 97/08/13 GMT (by NEWSPOST at IPNET) I just put up my Year2000 clock at: http://hedgehog.ts.uk.ibm.com X-NNTP-Server: news.uk.ibm.com NNTP-Posting-Host: hedgehog.ts.uk.ibm.com ----- YEAR2000 CFORUM appended at 09:39:38 on 97/08/13 GMT (by 36601943 at EHONE) <10193> Subject: Re: Number of days until 01/01/2000 Ref: Append at 09:15:56 on 97/08/13 GMT (by NEWSPOST at IPNET) Try this in REXX /* REXX */ say 730119 - date('b') 'days til the year 2000' Dougie Lawson, IBM Basingstoke, UK. (aka 8LAWSOD at NHBVM2) ----- YEAR2000 CFORUM appended at 09:58:16 on 97/08/13 GMT (by NEWSPOST at IPNET) <10194> Subject: Re: Number of days until 01/01/2000 From: Steve Swift Ref: Append at 09:28:43 on 97/08/13 GMT (by NEWSPOST at IPNET) It was just pointed out to me that this group is visible outside IBM. Unfortunately, hedgehog.ts.uk.ibm.com is inside our firewall. I'll make it available by other means if there is any interest. X-NNTP-Server: news.uk.ibm.com NNTP-Posting-Host: hedgehog.ts.uk.ibm.com ----- YEAR2000 CFORUM appended at 11:28:17 on 97/08/13 GMT (by BEGENB09 at ELINK) <10195> Subject: Number of days until 01/01/2000 Ref: Append at 15:36:10 on 97/08/11 GMT (by 70611526 at EHONE) Hello Jacques, Some months ago, there was a discussion on the calculation of Easter day and the dependant holidays on the GENTECH forum. You can find it in the pruned information (AR979016) with reference "112 EASTER DAY". Maybe there are some good ideas in it. However be aware that if you want to calculate the number of working days, this wil not be the same in all countries, due to public holidays and bankholidays. Regards, 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 11:51:46 on 97/08/13 GMT (by BEGENB09 at ELINK) <10196> Subject: DB2 and date simulation We are using Viasoft Validate as a date simulation tool. As it intercepts all SVC11, we can use this for most cases (such as COBOL ACCEPT) without any problems. If we want to test programs that use the SQL CURRENT TIMESTAMP or CURRENT DATE special registers, it does not seem to work. Obviously, DB2 uses an other mechanism to obtain the date. Does anyone has any information or experience on how to test SQL or DB2 applications with date simulation techniques ? Any info will be appreciated. Thanks in advance. 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 13:24:12 on 97/08/13 GMT (by RBBISDA at CHGVMIC1) <10197> Subject: DB2 and date simulation Ref: Append at 11:51:46 on 97/08/13 GMT (by BEGENB09 at ELINK) From what I understand, some software (like DB2) uses the STCK instruction as opposed to SVC11 to get the current date. This is where you'll need products like TICTOC (from ISOGON) and Hourglass (from Mainware) to do the job. Since the STCK instruction is not as easily interceptable as an SVC11, the technique used is to "ZAP" the associated language library's object code to replace the regular "get current date" routine with the vendor's own "date simulation" routine. This means that you have to have another set of language/system software COMPLETELY SEPARATE from production as TICTOC and HOURGLASS kinda "corrupts" your object code libraries. ----- YEAR2000 CFORUM appended at 16:37:40 on 97/08/13 GMT (by GBCADH00 at ELINK) <10198> Subject: Number of days until 01/01/2000 Ref: Append at 11:28:17 on 97/08/13 GMT (by BEGENB09 at ELINK) And of course Governments change the rules by declaring extra bank holidays from time to time - for example the 31/12/1999 is now a Bank Holiday in the UK. 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 17:46:36 on 97/08/13 GMT (by MORT at PK705VMA) <10199> Subject: Number of days until 01/01/2000 Ref: Append at 16:37:40 on 97/08/13 GMT (by GBCADH00 at ELINK) >> for example the 31/12/1999 is now a Bank Holiday in the UK. What, were they worried about too many banks having trouble closing their accounts on that day, say around midnight? Eric Morton P/390 microcode ----- YEAR2000 CFORUM appended at 18:43:43 on 97/08/13 GMT (by LESK at SPPVM1) <10200> Subject: Number of days until 01/01/2000 Ref: Append at 17:46:36 on 97/08/13 GMT (by MORT at PK705VMA) That's what I heard! Also, several airlines won't be flying through midnight. Les Koehler Advantis - Config Mgt. Development Tampa, Florida Sent on 13Aug1997 at 14:43:42 EDT ----- YEAR2000 CFORUM appended at 19:00:48 on 97/08/13 GMT (by ACLARK at ELINK) <10201> Subject: Number of days until 01/01/2000 Ref: Append at 15:36:10 on 97/08/11 GMT (by 70611526 at EHONE) I wish I could find the name but there's a company that has a COBOL routine that'll handle all holidays everywhere just about. We don't have much COBOL on VM so we didn't get too involved but it was interesting to play with, you'd tell it to subtract two dates and get the output in days, weekdays, working days etc. If you go to www.year2000.com you'll find a pile of vendors over there. As for free stuff like Easter amd what's a leap year... There's some good explanations on time, calendars etc. over at The Royal Greenwich Observatory http://www.ast.cam.ac.uk/pubinfo/leaflets/ Adrian Clark - Sears Canada Inc. IBMMAIL(CASRSAJC) / aclark@null.net ----- YEAR2000 CFORUM appended at 11:42:12 on 97/08/14 GMT (by BOYDG at BETVMIC1) <10202> Subject: Date Calculation Algorithms Is there a repository of date related algorithms available? I'm not looking for code so much as just the algorithm that could be used to perform various calculations related to dates. At the moment, I'm specifically looking for the logic to calculate the day of the week given the julian or gregorian date. Thanks . . . Greg ----- YEAR2000 CFORUM appended at 14:46:10 on 97/08/14 GMT (by ACLARK at EHONE7) <10203> Subject: Date Calculation Algorithms Ref: Append at 11:42:12 on 97/08/14 GMT (by BOYDG at BETVMIC1) Any specific language? (If you're on VM/ESA 2.2.0 then use the built in CSL routine). For our central date routine we convert everything to a base date and work with them (you can add/subtract find the day of week etc. easily with the base date). Some common manipulations of basedates.... date('B') // 7 /* day of week (0-Mon, 6-Sun) */ date('B') - 1 /* yesterday */ date('B') - right(date('O'),2) + 1 /* first of this month */ date('B') - date('B')//7 - 3 /* last friday */ Here's a REXX routine for converting a date to the day of the week in REXX. It's from a package called "REXXTIPS" from IBM... it should translate into any language easily enough. /* Day of the Week */ Say 'REXX exec to calculate the day of the week for any date' Say 'Please enter MM DD YYYY' Pull m d y Say m'/'d'/'y If m <= 2 Then Do m = m + 12 y = y - 1 End s = d + 2*m + y + 2 , + trunc(.6*(m+1)), + trunc(y/4) - trunc(y/100) + trunc(y/400) day = s//7 s$ = "SatSunMonTueWedThuFri" wd = substr(s$,(day*3)+1,3) Say "weekday = " wd "(day" day")" Exit Adrian Clark - Sears Canada Inc. IBMMAIL(CASRSAJC) / aclark@null.net ----- YEAR2000 CFORUM appended at 15:53:29 on 97/08/18 GMT (by BOYDG at BETVMIC1) <10204> Subject: Date Calculation Algorithms Ref: Append at 14:46:10 on 97/08/14 GMT (by ACLARK at EHONE7) Thanks for the code and pointer to the package. I've printed them but I haven't had a chance to sit down and look at it since I've been on the road since last Friday. Hopefully I will on the flight home later this week. Greg ----- YEAR2000 CFORUM appended at 18:56:24 on 97/08/18 GMT (by Y2KTSC1 at STLVM6) <10205> Subject: Date Calculation Algorithms Ref: Append at 11:42:12 on 97/08/14 GMT (by BOYDG at BETVMIC1) Some date calculation algorithms are available on our web site at URL http://www.software.ibm.com/year2000/tips15.html or choice What's New from the home page at URL http://www.software.ibm.com/year2000 Year 2000 Technical Support Center Web Master ----- YEAR2000 CFORUM appended at 08:34:35 on 97/08/19 GMT (by GBCDLH04 at ELINK) <10206> Subject: TERSEMVS on the MVS TOOLS DISK is it y2k compliant? Hi forumers, The full question is in the subject line. Cheers Charlie. This append was created on the External IBMLink system by Charlie Felton, Sys prog, Express Gifts Ltd. Near Yorkshire, But life aint that bad ! 01254-303022 ----- YEAR2000 CFORUM appended at 10:11:32 on 97/08/19 GMT (by MHSU at TAIVM1) <10207> Hi, I am planning the YR2000 capacity offering for customers. Does anyone have experience for several customers under different LPARs to share one CPU machine. ( Subject CPU are shared within 3 or 4 customers ). In general, there is no interruption for each customer if they are under different LPAR for testing. However, if one LPAR want to turn on machine H/W clock after year 2000 for operational testing, it will definitely impact other LPARs users. Can anyone advise how your country provide such services under one CPU? Best Regards, Michael Hsu ----- YEAR2000 CFORUM appended at 10:53:47 on 97/08/19 GMT (by GAD at KGNVMC) <10208> Subject: Year 2000 and LPAR Ref: Append at 10:11:32 on 97/08/19 GMT (by MHSU at TAIVM1) Append at 11:20:59 on 97/06/20 GMT (by GAD at KGNVMC) Append at 16:09:26 on 97/06/26 GMT (by GAD at KGNVMC) This has been said many times. Each LPAR partition can have it's own time value when the operating system initializes. Doing this has *NO* impact to any other partition on the processor. I've put a couple of references above which discuss this. Greg Dyck MVS BCP Kernel and CURE Support ----- YEAR2000 CFORUM appended at 15:15:49 on 97/08/20 GMT (by HOLLYYAM at SJFEVMX) <10209> Subject: Using DFSORT/VSE's Year 2000 features with LE/VSE COBOL You can now use DFSORT/VSE's Year 2000 features with LE/VSE COBOL (at the LE/VSE 1.4 level). LE/VSE PTF UQ05847 provides this capability. For a detailed example on how to tell DFSORT/VSE to: - Process 2-digit year dates - Set a fixed or sliding century window - Transform a 2-digit year date field in the input file to a 4-digit year date field in the output file from a COBOL program, come visit the DFSORT/VSE home page at: http://www.storage.ibm.com/dfsortvse/ Best Regards, Holly Yamamoto-Smith DFSORT/VSE Team ----- YEAR2000 CFORUM appended at 16:01:09 on 97/08/20 GMT (by CABEG at RALVM17) <10210> Subject: Shared objects Have there been prior discussions in this forum on the subject of objects that are shared across multiple partitions? How has this been addressed at other sites? Our testing environment will be a separate MVS LPAR with up to six partitions running concurrently in various stages of testing. Any thoughts, hints, pointers to other documentation or documents would be greatly appreciated. George Cabe IBM Global Services ----- YEAR2000 CFORUM appended at 17:08:42 on 97/08/20 GMT (by WMORGAN at SFOVMIC1) <10211> Subject: Time Machine Access Ref: Append at 13:53:30 on 97/08/08 GMT (by SAKC3II at ELINK) This may be obvious, but......... I was speaking with the sysprog who set up the LPAR at my customer. He mentioned that he basically established an environment by 'copying' a current environment for a set of TSO accounts. So, people had immediate access to their usual signon allocation data. A minor fly in the ointment...... The LPAR IPLed with little problem on a virtual January 1st, 2000 day. That evening as HSM 'looked around' for migration it said 'Wow! Look at all these datasets that haven't been touched for over 2 1/2 years. I'm not even going to archive them. They get 86ed.' So, other than a few lucky souls who actually logged on and touched their data, everyone's data was deleted. The decision was made to deactivate HSM. Bill Morgan WMORGAN at SFOVMIC1 ----- YEAR2000 CFORUM appended at 22:12:23 on 97/08/21 GMT (by JDARDIFF at ATLVMIC1) <10212> Subject: 9's complement I'm reviewing a document which lists some dates in 9's complement and was hoping someone could verify what dates these are: I'll list the full text of the cobol statements so that I don't say anything wrong. 01 Y2K-BEG-9COMP-DATE PIC X(06) VALUE '498768'. 01 Y2K-END-9COMP-DATE PIC X(06) VALUE '489898'. 01 Y2K-20-CENT-END-9COMP-DATE PIC X(06) VALUE '008768'. 01 Y2K-20-CENT-END-PLUS-1-9COMP PIC X(06) VALUE '008767'. 01 Y2K-20-CENT-BEG-9COMP-DATE PIC X(06) VALUE '999898'. 01 Y2K-20-CENT-BEG-MINUS-1-9COMP PIC X(06) VALUE '999899'. I don't even know what calculator to use to translate these. Thanks, Jeanne Ardiff ----- YEAR2000 CFORUM appended at 22:48:17 on 97/08/21 GMT (by BOBKING at ENDVM5) <10213> Subject: 9's complement Ref: Append at 22:12:23 on 97/08/21 GMT (by JDARDIFF at ATLVMIC1) Use a decimal calculator: 9's comp regular 01 Y2K-BEG-9COMP-DATE PIC X(06) VALUE '498768'. => 501231 01 Y2K-END-9COMP-DATE PIC X(06) VALUE '489898'. => 510101 01 Y2K-20-CENT-END-9COMP-DATE PIC X(06) VALUE '008768'. => 991231 01 Y2K-20-CENT-END-PLUS-1-9COMP PIC X(06) VALUE '008767'. => 991232 01 Y2K-20-CENT-BEG-9COMP-DATE PIC X(06) VALUE '999898'. => 000101 01 Y2K-20-CENT-BEG-MINUS-1-9COMP PIC X(06) VALUE '999899'. => 000100 To convert a regular date to a 9's complement date: COMPUTE DATE-9COMP = 999999 - DATE-REG. To convert a 9's complement date to a regular date: COMPUTE DATE-REG = 999999 - DATE-9COMP. (Of course, the variables used in arithmetic must be numeric.) The sum of a regular date and its 9's complement will always equal all 9s. Bob King ----- YEAR2000 CFORUM appended at 16:11:44 on 97/08/22 GMT (by Y2KTSC2 at STLVM6) <10214> Subject: 9's complement Ref: Append at 22:12:23 on 97/08/21 GMT (by JDARDIFF at ATLVMIC1) Jeanne, Just in case you're wondering, nines-complement dates are most often used to sort or store records in reverse order. For example, a record with a date of 082297 will usually be seen before one with a date of 082397. By subtracting both dates from 999999, they now come up as 917702 and 917701 respectively. When sorted, the 917701 date (08/23/97) now comes before the 917702 date (08/22/97). The theory behind this assumes that most of the processing centers on the most recent records. Had they been sorted normally, each search would have had to physically read through the whole database before finding the right record. Using nines-complemented dates, you should find the right record in the very beginning of the file. For large files, this could be an enormous performance enhancement. Year 2000 Technical Support Center (TSC2) ----- YEAR2000 CFORUM appended at 18:22:39 on 97/08/22 GMT (by MILLER at STLVM14) <10215> Subject: DB2 and date simulation Ref: Append at 11:51:46 on 97/08/13 GMT (by BEGENB09 at ELINK From cross memory mode, SVC is the wrong answer unless you like to abend. Here is how I'd discuss the usage: Be aware that date simulators (as marketed by solution developers) should only be installed on a test version of DB2. These tools corrupt one of the DB2 modules. This may be acceptable for your Year2000 testing purposes, but the product can no longer be warranted by IBM after you install such date simulator products. Therefore, install a separate copy of DB2 for use in date simulation testing than the copy used for production or final 'time machine' testing. We do have soem additional information about DB2 and the year 2000 on the web at http://www.software.ibm.com/year2000/db2.html Roger Miller, DB2 for OS/390 ----- YEAR2000 CFORUM appended at 12:52:24 on 97/08/26 GMT (by LAFITTE at MLVVMA) <10216> Subject: which level of JES2 is Year200 ready? From manual GC28-1251-04 one can understand that the minimum JES2 level ready for next century is 5.1.0, is that a good reading? JES2 5.1 is flagged as being ready 'by year end 1996' we are almost in septemner 1997, is that ready by now? thru a PTF? In advance thanks, Jean-Louis Lafitte ----- YEAR2000 CFORUM appended at 15:58:46 on 97/08/26 GMT (by GBCADH00 at ELINK) <10217> Subject: which level of JES2 is Year200 ready? Ref: Append at 12:52:24 on 97/08/26 GMT (by LAFITTE at MLVVMA) If you have access to Servicelink , please see the following PSP bucket Product Description Upgrade Subset YR2000 MVS/JES2 YR2000MVS MVS/JES2 It refers to a fix for timer support and also in support of SDSF function (which might be relevant in a non SDSF environment). 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 17:43:47 on 97/08/26 GMT (by GAD at KGNVMC) <10218> Subject: which level of JES2 is Year200 ready? Ref: Append at 12:52:24 on 97/08/26 GMT (by LAFITTE at MLVVMA) JES2 5.1 with APARs OW16685 and OW28203 should be year 2000 ready. If it is not, then a problem should be opened with the software support center. Greg Dyck MVS BCP Kernel and CURE Support ----- YEAR2000 CFORUM appended at 17:58:09 on 97/08/26 GMT (by Y2KTSC2 at STLVM6) <10219> Subject: which level of JES2 is Year200 ready? Ref: Append at 12:52:24 on 97/08/26 GMT (by LAFITTE at MLVVMA) Jean-Louis, You write: Subject: VisualAge 2000 Web site The IBM VisualAge 2000: Year 2000 Methodology and Tools Implementation Web site is now up at http://www.software.ibm.com/ad/va2000/y2k This is a new an expanded site from the old, now defunct, http://www.software.ibm.com/ad/cobol/y2k So if you have a bookmark at this url, update it to the new site. Either way, check it out. This now covers the full methodology, inventory and assessment tools, and tools specific to COBOL and High Level Assembler, including a disassembler tool for missing source in any language. More to come in the future. Karen R. Barney ----- YEAR2000 CFORUM appended at 08:42:54 on 97/08/27 GMT (by 72437085 at EHONE) <10221> Subject: System /1 Customer still uses a system /1. Has this system been tested for Year2000 calendar integrity ? Thank you in advance. Horst Winkelmann ----- YEAR2000 CFORUM appended at 13:55:54 on 97/08/27 GMT (by 86623100 at EHONE) <10222> Subject:AWD - Workflow Software, Supplied by DST I am trying to track down any Year 2000 projects where a workflow package called AWD (supplied by a company called DST) is on the list of items to be assessed for Year 2000 readiness. It is most likely that the product will be used by insurance and/or banking organisations. My customer is looking for guidance on the best approach to making their AWD applications Year 2000 ready and how best to test them. If you are able to help, please phone me in the UK on (0)1705 568468 and leave a contact number on my VoiceMail, EMail me at GBIB136L@IBMMAIL.COM. or simply address a reply to this forum. Thanks Gerry Moore IBM (UK) ----- YEAR2000 CFORUM appended at 02:37:43 on 97/08/29 GMT (by AS103767 at ELINK) <10223> Subject: Anyone using XCOM62 between Y2K and development systems? Hi, we are in the process of creatinng a LPAR for Y2K testing. There Would be no DASD sharing but our costumers insist in having XCOM62 to transfer data using Changeman. I know this is not safe and recommanded. Does anyone have any experience in this area? Any comments would be appreciated. Thanks. This append was created on the External IBMLink system by Kamran Sedghi - Coles Myer LTD, Melbourne, Australia Tel: 61 3 9483 7361 Fax: 61 3 9483 7381 email:kamran.sedghi@colesmyer.com.au ----- YEAR2000 CFORUM appended at 06:27:07 on 97/08/29 GMT (by 84828401 at EHONE) <10224> Subject: Testing the Year2000 Enabled VSE/ESA Ref: none My customer runs under the control of VM/ESA V2 a production- and a test-VSE/ESA both at V2.2.1. These two VSE/ESA share a user library (application software) and a lock file. The customer would like to test-run the test-VSE/ESA with the system date set to 1/January/2000 and above (TODENABLE), while the production VSE/ESA is run at the current date. What are the risks involved sharing a user library and the lock file? Thanks for your help, regards Werner Geiser, IBM Switzerland. P.S. I sent this question already by e-mail to y2ktscap@vnet.ibm.com on the 27th of Aug. but didn't get an answer. ----- YEAR2000 CFORUM appended at 08:31:29 on 97/08/29 GMT (by ALANDP at SYDVMXA2) <10225> Subject: VSE/ESA 2.2.1 testing The safest course is to keep the Year 2000 test system isolated completely from the production system. Given the only requirement from the production machine is the user library containing the application code the following might be applicable 1. Place a copy of this user library onto the test system 2. Place this user library on its own mini-disk, this disk could then be R/O to the Test System. This method then no longer requires a LOCK FILE as the R/O is controlled by VM. Prior to the Year 2000 IPL it is also adviseable to FASTCOPY all the test packs. If your customer would like more information please feel free to ask. I would also mention the VSE/ESA and Year 2000 page (http://www.s390.ibm.com/vse/vsehtmls/vse2000.htm) which has a wealth of material. Bob McCormack Year 2000 Technical Support Center - Asia Pacific Internet: y2ktscap@vnet.ibm.com VNET: Y2KTSCAP at SYDVMXA2