I thought I had a cute idea, but trying it, there are 2 problems.
FTP xxxx
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 JOBnnnnn
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 <IBM-MAIN@LISTSERV.UA.EDU> 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 <sdg ><
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 <michael.schm...@dxc.com> 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
