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
?
