In a past life, a group of sysprogs entertained the idea of migrating as a cost savings measure. The JECL and JOB CLASS changes were the least of our worries. Exits could be written to translate and map. As others have pointed out, 8-character JES2 JOB classes may reduce the need for custom code, as can software tools that identify and perform conversion (no pun intended).
The bigger problem was JES3 functionality that systems and applications types alike exploited and the extent to which they did. I don't recall any technical hurdles we couln't clear - between already licensed, or readily available vendor (including IBM) software, plus a little custom code, there wasn't any JES3 function we used that couldn't be "replaced". It was the time to make the conversion and the cost of additional software that put the project on the shelf. YMMV. Migrating from JES3 DASD management to SMS (also mentioned to previously) helped, but, off the cuff, in no particular order, there are other features to consider, such as: - JES3 tape management - DEADLINE scheduling - DJC These have have viable alternatives, if you can spend the time and/or money. I agree a trip through the aforementioned Redbook(s), white papers, and a few SHARE presentations (the "bi-JESual" pitch comes to mind) will be well worth the investment in time. Regards, Art Gutowski General Motors, LLC ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
