Re: TCP/IP to JES3
All the links from our main NJE/IP Bridge site should be accessible once again. https://www.sinenomine.net/offerings/zVM/Products/NJE They were still behind our private network after our website upgrade, making this a pretty quick fix. Looking forward to hearing about your thoughts on the product. Thanks and Best Regards, Kurt Acker On Thu, Sep 28, 2023 at 10:18 AM Bfishing wrote: > I've sent the team notice of this. > Found all the links from that page are in the same state. Thanks for > bringing this to our attention, > > Kurt Acker > > On Thu, Sep 28, 2023 at 10:11 AM Schmitt, Michael > wrote: > >> Thank you. >> >> The links on your website are broken, e.g. publications such as >> http://download.sinenomine.net/publications/njebridge/SNA-NJE-Bridge.pdf >> >> -Original Message- >> From: IBM Mainframe Discussion List On Behalf >> Of Neale Ferguson >> Sent: Thursday, September 28, 2023 2:30 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: TCP/IP to JES3 >> >> We produce an NJE implementation running on Linux (and other platforms) >> that speaks the NJE protocol - both SSL and non-SSL. We have customers >> using it to receive job output from JES2/JES3/POWER/RSCS as well as >> submitting jobs and sending files the other way. >> >> Further details: >> https://www.sinenomine.net/index.php/offerings/zVM%26VSE/Products/NJE >> >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > > > -- > > ><º>`·.¸¸´¯`·.¸.·´¯`·...¸>(((º> > .·´¯`·.><º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><º> > > <>< Go fishing ><> > -- ><º>`·.¸¸´¯`·.¸.·´¯`·...¸>(((º> .·´¯`·.><º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><º> <>< Go fishing ><> -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
I've sent the team notice of this. Found all the links from that page are in the same state. Thanks for bringing this to our attention, Kurt Acker On Thu, Sep 28, 2023 at 10:11 AM Schmitt, Michael wrote: > Thank you. > > The links on your website are broken, e.g. publications such as > http://download.sinenomine.net/publications/njebridge/SNA-NJE-Bridge.pdf > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Neale Ferguson > Sent: Thursday, September 28, 2023 2:30 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: TCP/IP to JES3 > > We produce an NJE implementation running on Linux (and other platforms) > that speaks the NJE protocol - both SSL and non-SSL. We have customers > using it to receive job output from JES2/JES3/POWER/RSCS as well as > submitting jobs and sending files the other way. > > Further details: > https://www.sinenomine.net/index.php/offerings/zVM%26VSE/Products/NJE > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- ><º>`·.¸¸´¯`·.¸.·´¯`·...¸>(((º> .·´¯`·.><º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><º> <>< Go fishing ><> -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
Thank you. The links on your website are broken, e.g. publications such as http://download.sinenomine.net/publications/njebridge/SNA-NJE-Bridge.pdf -Original Message- From: IBM Mainframe Discussion List On Behalf Of Neale Ferguson Sent: Thursday, September 28, 2023 2:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: TCP/IP to JES3 We produce an NJE implementation running on Linux (and other platforms) that speaks the NJE protocol - both SSL and non-SSL. We have customers using it to receive job output from JES2/JES3/POWER/RSCS as well as submitting jobs and sending files the other way. Further details: https://www.sinenomine.net/index.php/offerings/zVM%26VSE/Products/NJE -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
We produce an NJE implementation running on Linux (and other platforms) that speaks the NJE protocol – both SSL and non-SSL. We have customers using it to receive job output from JES2/JES3/POWER/RSCS as well as submitting jobs and sending files the other way. Further details: https://www.sinenomine.net/index.php/offerings/zVM%26VSE/Products/NJE -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
On Fri, 22 Sep 2023 20:25:58 +, Schmitt, Michael wrote: >Is there a way to transfer sysout type data from a remote, non-mainframe >system, into a JES3 spool? I think INFOPRINT has this capability. Another possibility is to use Unix LPR command to a z/OS UNIX LPR daemon. Another possibility is to send the file to z/OS and use your job schedular or automation to submit a job to print it. For security purposes, FTP is not recommended because userids/passwords get embedded in scripts. You gotta love developers who are proud of their code and distribute it as open source thru github. I saw a NASA script recently that had userid/password. Several possible solutions like setting up NFS daemon on z/OS UNIX avoid this situation for FTP. > From which already existing tasks will grab the output according to > destination, class, writer, etc. If you are going to process the data, then put it to a dataset and let your job scheduler process it as it is created. If you decide to go with USERID / PASSWORD, then think about security because this is an easy exposure. I would suggest use of secondary users with very restricted access. Remember most resources are readable. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
On Sun, 24 Sep 2023 21:37:18 -0500, Steve Horein wrote: >To me, the simplest way would be to ftp the desired data to an >appropriately allocated dataset, and then change to filetype=jes to put jcl >to copy the newly created dataset to sysout, and perform housekeeping >if/when the copy was complete. I do not believe filetype=jes was meant to >be exclusive. > Why the intermediate data set? Just put it instream. >On Fri, Sep 22, 2023 at 3:26 PM Schmitt, Michael wrote: > >> Is there a way to transfer sysout type data from a remote, non-mainframe >> system, into a JES3 spool? From which already existing tasks will grab the >> output according to destination, class, writer, etc. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
To me, the simplest way would be to ftp the desired data to an appropriately allocated dataset, and then change to filetype=jes to put jcl to copy the newly created dataset to sysout, and perform housekeeping if/when the copy was complete. I do not believe filetype=jes was meant to be exclusive. On Fri, Sep 22, 2023 at 3:26 PM Schmitt, Michael wrote: > Is there a way to transfer sysout type data from a remote, non-mainframe > system, into a JES3 spool? From which already existing tasks will grab the > output according to destination, class, writer, etc. > > Such as, use some product or capability to connect and transfer to a > TCP/IP port. > > Most of what I see is going the other direction, answering the question of > "how do I get this report from the JES spool to my printer/pc/file > server/etc?" But I need to get it into JES3, because the existing report > distribution software wants to grab it from there. > > I thought I remembered being able to inject jobs into the IEFRDER via FTP, > and thought perhaps could also transfer to sysout, but don't see it in the > Communications Server manual. > > Bonus points for a solution that will also work with JES2, after the > inevitable end-of-support for JES3. > > __ > Michael Schmitt | DXC Apps Development | MassMutual > (737) 910-8248 | michael.schm...@dxc.com > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
On Sat, 23 Sep 2023 23:23:32 -0700, Leonard D Woren wrote: >I thought I had a cute idea, but trying it, there are 2 problems. >FTP >SITE FILETYPE=JES >200 SITE command was accepted >SITE LRECL=133 >200 SITE command was accepted >PUT test.ds(member) >EXA1701I >>> SITE FIXrecfm 133 LRECL=133 RECFM=FBA BLKSIZE=32718 >200 SITE command was accepted >EXA1701I >>> STOR test.ds(member) >125 Sending Job to JES internal reader FIXrecfm 80 >250-It is known to JES as JOBn >250 Transfer completed (data was truncated) > >I edit out some ftp messages regarding passive mode, etc. > >Well, that's annoying. >1. I can't figure out how to get an LRECL other than 80. > It *used*to* work with up nto 254. Did IBM break it? Are you sure of the syntax? SITE never reports an error. >2. Probably can't suppress the JOB statement. > Make lemonade. Make your payload SYSUT1 to an IEBGENER step. You can put all desired delivery attributes on //SYSUT2 DD SYSOUT My empirical observations for instream data submitted via FTP or INTRDR: o If no record exceeds 80 bytes: RECFM=FB,LRECL=80 o Otherwise, if JES3 or all records are of equal length: RECFM=FB,LRECL=length of longest record o Otherwise: RECFM=VB,LRECL=length of longest record LRECL is allowed on instream data sets, but may not have the intended effect with SYMBOLS=. RECFM is not allowed on in stream data sets . >But here's the trick to go directly to SYSOUT, if you're satisfied >with LRECL=80 and the JOB statement printing: >//jobname JOB TYPRUN=COPY >[data to print] >[...] -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
I thought I had a cute idea, but trying it, there are 2 problems. FTP SITE FILETYPE=JES 200 SITE command was accepted SITE LRECL=133 200 SITE command was accepted PUT test.ds(member) EXA1701I >>> SITE FIXrecfm 133 LRECL=133 RECFM=FBA BLKSIZE=32718 200 SITE command was accepted EXA1701I >>> STOR test.ds(member) 125 Sending Job to JES internal reader FIXrecfm 80 250-It is known to JES as JOBn 250 Transfer completed (data was truncated) I edit out some ftp messages regarding passive mode, etc. Well, that's annoying. 1. I can't figure out how to get an LRECL other than 80. 2. Probably can't suppress the JOB statement. But here's the trick to go directly to SYSOUT, if you're satisfied with LRECL=80 and the JOB statement printing: //jobname JOB TYPRUN=COPY [data to print] [...] TYPRUN=COPY is probably a holdover from punch cards, where you could duplicate a card deck that way. /Leonard Schmitt, Michael wrote on 9/22/2023 1:59 PM: Thanks, I overlooked the "interacting with JES topic". Looks like you can GET (receive) sysout but not PUT. I suppose a worst case solution would be to wrap the output in JCL, where the JCL executes code to build LRECL=133 lines from instream data and then copy that to SYSOUT. We used to transfer files this way: run a job on system A, where the job takes the file and converts it into instream data, embeds it in a job it constructs, submits that job that routes to system B, where it executes and unloads the instream data back into a file. In fact, I still have the JCL for that trick using TSO XMIT as the conversion program, for sending data between systems that are only connected by JES (and you don't want to go to the remote system to receive the file.) To top that, I think I have a job that finds and collects a file and all of its dependencies, converts that all into instream data, builds and routes a job to a remote system, where it runs a program, takes the output files from that program, converts all of that, puts it into a job, routes it back to the original system, where the jobs runs and converts the files back and saves them! -Original Message- From: IBM Mainframe Discussion List On Behalf Of Lionel B Dyck Sent: Friday, September 22, 2023 3:32 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: TCP/IP to JES3 Try FTP with filetype=jes Lionel B. Dyck < Website: http://www.lbdsoftware.com/ Sent from my iPhone 15 Pro Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden On Sep 22, 2023, at 3:26 PM, Schmitt, Michael wrote: Is there a way to transfer sysout type data from a remote, non-mainframe system, into a JES3 spool? From which already existing tasks will grab the output according to destination, class, writer, etc. Such as, use some product or capability to connect and transfer to a TCP/IP port. Most of what I see is going the other direction, answering the question of "how do I get this report from the JES spool to my printer/pc/file server/etc?" But I need to get it into JES3, because the existing report distribution software wants to grab it from there. I thought I remembered being able to inject jobs into the IEFRDER via FTP, and thought perhaps could also transfer to sysout, but don't see it in the Communications Server manual. Bonus points for a solution that will also work with JES2, after the inevitable end-of-support for JES3. __ Michael Schmitt | DXC Apps Development | MassMutual (737) 910-8248 | michael.schm...@dxc.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
On Fri, Sep 22, 2023 at 05:28:00PM -0400, Steve Thompson wrote: > I'm going for the bonus points: NJE/RJE. I was just reading on this by > accident while working on a tool to do a JES3 to JES2 migration (JOBs, not > the sysprog work, not that far into AI yet ;-) ). UCLA/Mail (in it's day) sent and received mail from JES2 via SNA/NJE. The code is available, I don't know if it would still work. During development I had the NJE protocol book and, of course, the source to JES2. There was a "problem" with JES2 not accepting data I sent formated as the book said. I looked at the JES2 source and it was clearly not in agreement with the book. I called IBM with the disagreement between their protocol book and the JES2 code. This went nowhere as about expected. After going around a bit, my final question was (thinking that SNA/NJE was IBM's main path, and not being a JES3 shop): Well then how does JES3 do it? The answer was JES3 didn't (at that time) do SNA/NJE. I changed my code to produce something JES2 would accept... PS: Another site at UCLA was JES3. The JES3 lack of NJE was circumvented by having their UCLA/Mail connect to our JES2 via SNA. This got them both local email and email to Bitnet and the Internet. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
On Fri, 22 Sep 2023 20:59:11 +, Schmitt, Michael wrote: >Thanks, I overlooked the "interacting with JES topic". > >Looks like you can GET (receive) sysout but not PUT. > >I suppose a worst case solution would be to wrap the output in JCL, where the >JCL executes code to build LRECL=133 lines from instream data and then copy >that to SYSOUT. > FTP limits JESLRECL to 254 which may be sufficient to avoid the "JCL executes code to build." (I assume IEBGENER step with instream SYSUT1.) 254!? Antique JES3 limit. Both JES2 and JES3 allow far more nowadays. Time for an RFE^H^H^HIdea? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
I'm going for the bonus points: NJE/RJE. I was just reading on this by accident while working on a tool to do a JES3 to JES2 migration (JOBs, not the sysprog work, not that far into AI yet ;-) ). So there is a way to do that between those nodes. Steve Thompson On 9/22/2023 4:25 PM, Schmitt, Michael wrote: Is there a way to transfer sysout type data from a remote, non-mainframe system, into a JES3 spool? From which already existing tasks will grab the output according to destination, class, writer, etc. Such as, use some product or capability to connect and transfer to a TCP/IP port. Most of what I see is going the other direction, answering the question of "how do I get this report from the JES spool to my printer/pc/file server/etc?" But I need to get it into JES3, because the existing report distribution software wants to grab it from there. I thought I remembered being able to inject jobs into the IEFRDER via FTP, and thought perhaps could also transfer to sysout, but don't see it in the Communications Server manual. Bonus points for a solution that will also work with JES2, after the inevitable end-of-support for JES3. __ Michael Schmitt | DXC Apps Development | MassMutual (737) 910-8248 | michael.schm...@dxc.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
NJE over TCP/IP. From: IBM Mainframe Discussion List on behalf of Schmitt, Michael Sent: Friday, September 22, 2023 4:25 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: TCP/IP to JES3 Is there a way to transfer sysout type data from a remote, non-mainframe system, into a JES3 spool? From which already existing tasks will grab the output according to destination, class, writer, etc. Such as, use some product or capability to connect and transfer to a TCP/IP port. Most of what I see is going the other direction, answering the question of "how do I get this report from the JES spool to my printer/pc/file server/etc?" But I need to get it into JES3, because the existing report distribution software wants to grab it from there. I thought I remembered being able to inject jobs into the IEFRDER via FTP, and thought perhaps could also transfer to sysout, but don't see it in the Communications Server manual. Bonus points for a solution that will also work with JES2, after the inevitable end-of-support for JES3. __ Michael Schmitt | DXC Apps Development | MassMutual (737) 910-8248 | michael.schm...@dxc.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
Thanks, I overlooked the "interacting with JES topic". Looks like you can GET (receive) sysout but not PUT. I suppose a worst case solution would be to wrap the output in JCL, where the JCL executes code to build LRECL=133 lines from instream data and then copy that to SYSOUT. We used to transfer files this way: run a job on system A, where the job takes the file and converts it into instream data, embeds it in a job it constructs, submits that job that routes to system B, where it executes and unloads the instream data back into a file. In fact, I still have the JCL for that trick using TSO XMIT as the conversion program, for sending data between systems that are only connected by JES (and you don't want to go to the remote system to receive the file.) To top that, I think I have a job that finds and collects a file and all of its dependencies, converts that all into instream data, builds and routes a job to a remote system, where it runs a program, takes the output files from that program, converts all of that, puts it into a job, routes it back to the original system, where the jobs runs and converts the files back and saves them! -Original Message- From: IBM Mainframe Discussion List On Behalf Of Lionel B Dyck Sent: Friday, September 22, 2023 3:32 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: TCP/IP to JES3 Try FTP with filetype=jes Lionel B. Dyck < Website: http://www.lbdsoftware.com/ Sent from my iPhone 15 Pro Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden > On Sep 22, 2023, at 3:26 PM, Schmitt, Michael wrote: > > Is there a way to transfer sysout type data from a remote, non-mainframe > system, into a JES3 spool? From which already existing tasks will grab the > output according to destination, class, writer, etc. > > Such as, use some product or capability to connect and transfer to a TCP/IP > port. > > Most of what I see is going the other direction, answering the question of > "how do I get this report from the JES spool to my printer/pc/file > server/etc?" But I need to get it into JES3, because the existing report > distribution software wants to grab it from there. > > I thought I remembered being able to inject jobs into the IEFRDER via FTP, > and thought perhaps could also transfer to sysout, but don't see it in the > Communications Server manual. > > Bonus points for a solution that will also work with JES2, after the > inevitable end-of-support for JES3. > > __ > Michael Schmitt | DXC Apps Development | MassMutual > (737) 910-8248 | michael.schm...@dxc.com > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
Try FTP with filetype=jes Lionel B. Dyck < Website: www.lbdsoftware.com Sent from my iPhone 15 Pro Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden > On Sep 22, 2023, at 3:26 PM, Schmitt, Michael wrote: > > Is there a way to transfer sysout type data from a remote, non-mainframe > system, into a JES3 spool? From which already existing tasks will grab the > output according to destination, class, writer, etc. > > Such as, use some product or capability to connect and transfer to a TCP/IP > port. > > Most of what I see is going the other direction, answering the question of > "how do I get this report from the JES spool to my printer/pc/file > server/etc?" But I need to get it into JES3, because the existing report > distribution software wants to grab it from there. > > I thought I remembered being able to inject jobs into the IEFRDER via FTP, > and thought perhaps could also transfer to sysout, but don't see it in the > Communications Server manual. > > Bonus points for a solution that will also work with JES2, after the > inevitable end-of-support for JES3. > > __ > Michael Schmitt | DXC Apps Development | MassMutual > (737) 910-8248 | michael.schm...@dxc.com > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TCP/IP to JES3
RJE3780? https://github.com/wa6our/RJE3780 https://www.cq-comm.com/3780.htm On Fri, Sep 22, 2023 at 3:26 PM Schmitt, Michael wrote: > > Is there a way to transfer sysout type data from a remote, non-mainframe > system, into a JES3 spool? From which already existing tasks will grab the > output according to destination, class, writer, etc. > > Such as, use some product or capability to connect and transfer to a TCP/IP > port. > > Most of what I see is going the other direction, answering the question of > "how do I get this report from the JES spool to my printer/pc/file > server/etc?" But I need to get it into JES3, because the existing report > distribution software wants to grab it from there. > > I thought I remembered being able to inject jobs into the IEFRDER via FTP, > and thought perhaps could also transfer to sysout, but don't see it in the > Communications Server manual. > > Bonus points for a solution that will also work with JES2, after the > inevitable end-of-support for JES3. > > __ > Michael Schmitt | DXC Apps Development | MassMutual > (737) 910-8248 | michael.schm...@dxc.com > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
TCP/IP to JES3
Is there a way to transfer sysout type data from a remote, non-mainframe system, into a JES3 spool? From which already existing tasks will grab the output according to destination, class, writer, etc. Such as, use some product or capability to connect and transfer to a TCP/IP port. Most of what I see is going the other direction, answering the question of "how do I get this report from the JES spool to my printer/pc/file server/etc?" But I need to get it into JES3, because the existing report distribution software wants to grab it from there. I thought I remembered being able to inject jobs into the IEFRDER via FTP, and thought perhaps could also transfer to sysout, but don't see it in the Communications Server manual. Bonus points for a solution that will also work with JES2, after the inevitable end-of-support for JES3. __ Michael Schmitt | DXC Apps Development | MassMutual (737) 910-8248 | michael.schm...@dxc.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
