OK - thanks. Seems to be nje w/dedicated ctc. I think I found a clue. 09180,07/05/03 16:46:00 RSCS SYS1 : 16:46:00 DMTNTR930E LINK SYS2 STR EAM 2 DENIED -- INSUFFICIENT SPOOL SPACE ,
I assuming this means the remote system (SYS2) has run out of spool space?? Oddly it seemed to recover and send more files until around 8PM when I got involved. I do remember checking spool on both sides at that time and each had plenty. BTW sys1 & sys2 are z/vm 52 - sys2 is second level. So I guess the mystery remains - why did it hang @8PM? - why did the purge of the sending(hung) file not clear things? Why did I have to stop/start the link to free it? Thanks for the help. -James On 5/4/07, Kris Buelens <[EMAIL PROTECTED]> wrote:
RSCS can use SNA, CTC or TCP/IP as transport mechanism for a link to another NJE site, it depends on your setup. Example SM RSCS Q VMKBMB01 Link Name Status Type VMKBMB01 connect TCPNJE which is for TCP/IP, the other linktypes are SNANJE or NJE. If it is a link driving a printer, it probably is SNA or TCP/IP. If your link is SNA, also have a look at the VTAM console; for TCP/IP, maybe the TCPIP console can tell you things too. 2007/5/4, James M <[EMAIL PROTECTED] >: > > backup guy here again in need of assistance... > > Last night one of the rscs links froze. Q F showed one file at the top > in sending mode with many behind in waiting status. > Purged the sending file, stop/start the link and files were again > moving. > Now I've been told to provide an explanation. > question 1 - how to look at rscs log - I think the command would > be..... > smsg rscs cp sp cons close to myid > ....is that correct? > question 2 - if I remember correctly rscs now uses tcpip as transport > mechanism. If this is correct is there anything on that side I should be > looking at? > > If there are any other hints that may be helpful I would appreciate > hearing them. > > Thanks again. > -James -- Kris Buelens, IBM Belgium, VM customer support
