Hi Jeff:
I've gone both up and down in buffer size.
I can send a short command or a short JCL from RSCS to JES. ?No problem there. ?But when I send a larger job, maybe 20 lines, the IO errors start. ?There seems to be something wrong in the way the BSC conversation over TCP is being handled.
Now in the case of the short JCL (an IEFBR14 job, for example), it will run and output will come back to RSCS. ?Since the output is not tagged in any way to go back to my user, it gets printed on PRT1. ?Aside from the IO issues, the next thing I need to figure out is if there is any JCL that could tell RSCS to route the job back to PRT on my userid.
On Sat, 2024-10-12 at 02:21 -0700, Jeff Snyder wrote:
Hi Daniel,
?
Try using the following for your RSCS link start command:
?
START NODEA PARM H02 B999
?
Page 35 in the manual "GC20-1816-3 VM/370 Remote Spooling Communications Subsystem Users Guide, Release 3" documents the parms for the start command and describes the H parm as the line number of the JES2 remote line VM is connecting to.? I'm suggesting B999 to bump the buffer size up to possibly counteract the I/O errors on data flowing from JES2 to VM.? I've used that on other links with success, so it may work here as well.
?
When I use this start command, I am able to start the RSCS link, followed by the JES2 line.? I get one I/O error when I start the JES2 line, but none after that.
?
I am able to use the RSCS CMD command to send commands to JES2 and get the response files back.? I am getting an "invalid destination" when I punch files to RSCS with NODEA in the tag, but I suspect that's because the AXSROUTE COPY file is empty.
?
Eventually, when I want to bring it down, I just $PLINE<n>.? When JES2 shuts down the line, RSCS detects that and deactivates the link.
?
Jeff
?
