Re: TCP/IP to JES3

2023-09-29 Thread Bfishing
ame 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

Re: TCP/IP to JES3

2023-09-28 Thread Bfishing
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

Re: TCP/IP to JES3

2023-09-28 Thread Schmitt, Michael
-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

Re: TCP/IP to JES3

2023-09-28 Thread Neale Ferguson
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:

Re: TCP/IP to JES3

2023-09-27 Thread Jon Perryman
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

Re: TCP/IP to JES3

2023-09-24 Thread Paul Gilmartin
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

Re: TCP/IP to JES3

2023-09-24 Thread Steve Horein
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.

Re: TCP/IP to JES3

2023-09-24 Thread Paul Gilmartin
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

Re: TCP/IP to JES3

2023-09-24 Thread Leonard D Woren
e 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 Li

Re: TCP/IP to JES3

2023-09-23 Thread Michael Stein
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

Re: TCP/IP to JES3

2023-09-22 Thread Paul Gilmartin
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

Re: TCP/IP to JES3

2023-09-22 Thread Steve Thompson
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,

Re: TCP/IP to JES3

2023-09-22 Thread Seymour J Metz
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

Re: TCP/IP to JES3

2023-09-22 Thread Schmitt, Michael
al 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 mo

Re: TCP/IP to JES3

2023-09-22 Thread Lionel B Dyck
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

Re: TCP/IP to JES3

2023-09-22 Thread Mike Schwab
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

TCP/IP to JES3

2023-09-22 Thread Schmitt, Michael
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