>Flash!!! > >After restarting 2 or 3 times without the STREAMS= and getting nowhere >(an immediate DMTNTR930E message and no file transfer activity), with a >rapidly expanding queue, the MVS guy said that JES was configured for 4 >streams. I tried STREAMS=4 and got immediate action. The queue of over >100 jobs was reduced to 1 before another DMTNTR930E struck and, once >again, froze the link. > >Why STREAMS=4 did anything at all to get the link to work is beyond >me. >That may have been happenstance; maybe the link thawed out for some >other reason. According to the documentation, having a number higher >than 1 does not cause files to be transferred concurrently; it merely >affects the order in which files are sent under some circumstances. They >are still sent one at a time. > >The key is the DMTNTR930E. The question is, "What can we do to determine >the cause of the error?" >
Streams indicates to RSCS how many file streams can be in progress simultaneously. How many files can be sent at once. There must be a corresponding stream on the JES side defined or you will receive errors such as this. For example, if RSCS has defined 4 streams but JES only 3 then when RSCS requests to send a file on stream 4 JES will reject the request. This is irregardless of the link type, NJE, SNANJE, or TCPNJE. You also need to setup the TA= and TAPARM= parms accordingly. This tells RSCS what size files to send on each stream Best Regards, Les Geer IBM z/VM and Linux Development
