I still can't punch jobs to MVS from VM for some reason but, in tests today, output routed from MVS to VM transfers with no I/O errors.? So far, I have routed jobs with various amounts of output, from 153 lines of MVS output (90 records on the VM SPOOL) to 11071 lines (11145 records on VM).
?
In case the issue is not with the RSCS start command, here are my Hercules config statements for the link.? They seem to mirror yours though, so I don't think there's an issue here.
?
Note: Pi4 is the hostname for my Pi host OS.
?
MVS - 670 is JES2 line 1, the one I used for connecting to VM
670 2703 dial=no lport=37908 rhost=Pi4 rport=37913 # RJE to VM/370 (JES line 1)
?
VM - 040 is the CUA defined as NODEA in RSCS
040 2703 dial=no lport=37913 rhost=Pi4 rport=37908 # RJE link to JS08 (NODEA - SML mode to MVS RJE line)
?
As for routing the output to a specific user, the best I've been able to come up with is draining the VM printer or changing the output class or whatever so the output doesn't print by default and using the TRANSFER command to move the output file to the requestor's queue.
?
JES2 thinks it's talking to a dumb RJE workstation, not a smart system with an OS and multiple users.? If you had a level of JES2 that supported NJE, you could use that and Peter Coghlan's updated RSCS to set up an NJE link and get closer to what it sounds like you want.? I've used his modified RSCS to support both NJE and RJE links with good success, though I don't remember specifically testing RJE jobs with massive output for I/O errors.? Typically just IEFBR14s to see the connection works.
?
