Thanks, Lionel for your comment (year end bonus would be great :) I have also read the announcement from Phoenix software, and the mail from Edward on this list. That is definitely being considered as an option. It would be interesting to see a cost comparison for JES3 being supported from Phoenix - is there any information available in that regard?
But since, I am not involved in the final decision w.r.t. the cost of keeping JES3 (through Phoenix), I am trying to compile this list more from a technical standpoint on the common pitfalls, duration of migration, post migration issues etc for the management to take an informed decision before we get too far down the road. Regards Varun On Tue, Nov 26, 2019 at 8:16 PM Lionel B Dyck <[email protected]> wrote: > Save your company the time and resources and stay with JES3 now that it > will be supported by Phoenix Software > > Check it out at https://phoenixsoftware.com/jes3plus.htm > > This is a very promising development for the JES3 community and will save > those considering the migration the time and expense of the migration, > funds that be better used elsewhere in the company (such as year end > bonuses to the systems staff) while eliminating the risks of a migration. > > Disclaimer: I know several of the team at Phoenix but I do not work for > them or have stock in them. > > > Lionel B. Dyck <sdg>< > Website: http://www.lbdsoftware.com > > "Worry more about your character than your reputation. Character is what > you are, reputation merely what others think you are." - John Wooden > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On Behalf > Of Mainframe Sysprog > Sent: Tuesday, November 26, 2019 8:28 AM > To: [email protected] > Subject: JES3 to JES2 migration experience > > Hi List, > > I know this topic has been discussed multiple times, and with the recent > SOD on JES3, I am looking for some hands-on tips or experiences from anyone > who has had the chance of converting from JES3 to JES2. > > Can anyone share their experience on what are the most troublesome areas > to be considered for such a migration and how were these handled in your > case? > > Any gotchas, or areas that get overlooked? > > I am reviewing the excellent Redbook from IBM, but would want to > supplement that with some real world experiences. > > Thanks > Varun > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
