Hello JES experts,
My practical experience with JES3 is near zero, or even <below> zero. The software we develop rarely ever has to take into consideration the differences between JES2 and JES3. I can remember only 3 such cases in the past more than 15 years I have been working here. Every now and then, though, it would be nice to be able to perform a quick test on a JES3 system. However, I cannot spare an LPAR, and I do not have the time and the resources to set up and maintain a z/OS JES3 system on a permanent basis. So, not surprisingly, my thoughts wandered off to the possibility of a secondary JES; I had done that before, yet only with all JES2s. Frustration came quick: The JES3 to JES2 Migration Considerations (SG24-8083-00) on page 6 reads: "You can also define a JES3 as the primary and JES2 as a secondary subsystem (however running JES2 and JES3 on the same z/OS image is not currently supported, though there are no known problems). If JES3 is running on a system, it must be the primary job entry subsystem. You cannot run JES2 as the primary subsystem and JES3 as a secondary subsystem.". My question; Does anybody know a - dirty? - trick to still do that, run JES2 as primary with JES3 as a secondary? What/Where is the ruse? I mean, it works the other way around. I'm not afraid of experimenting; I might possibly even find a test LPAR that I can <shred> on a weekend. I'm looking forward to your suggestions. Thanks a lot in advance. Best Regards Karl ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
