As we saw in the recent thread on converting from JES3 to JES2, JES3 from the beginning provided function--especially in the area of data device control--that was never envisioned for JES2. I think that most of the recent convergence of function in the two products mostly involves what we think of as classic 'job control'. And the motivation for much of that convergence is to 'elevate' function from JES to the BCP so that code has to be developed only once. JES3's historic foray into disk and tape control, while useful for shops that make use of it, has little to do with 'controlling jobs' in the original sense.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile [email protected] [email protected] > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Staller, Allan > Sent: Friday, January 22, 2016 09:02 AM > To: [email protected] > Subject: [Bulk] Re: Compile error > > <snip> > Meanwhile there did emerge a 'JES3', but it was not an evolutionary > descendant of JES2. Both products have coexisted, albeit uneasily, for decades. > We used to imagine a JES5 or JES6 (depending on one's arithmetic proclivity) > that would somehow combine the best features of both products, but it's > almost certainly DOA. .... > </snip> > > Actually this seems to be happening. Witness the recent merging of JES3 and > JES2 capabilities. 8 char job classes in JES2, JES2/JES3 using common SAPI. > SDSF (formerly JES only) obtaining JES3 capabilities. > Dependent Job Control language in JES2 (2.2). > > And I am sure there are others. It looks like IBM is attempting to create "THE > JES" from the capabilities of JES2 and JES3. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
