Have you run thought syslog looking for the RECEIVE messages as well as scanning for the RUNHSTAX?
When I have had issues like that I usually need to know how big is the file, what is the transmitting node. Then I have to follow the messages in SYSLOG/OPERLOG to see what happened. I am always interested in the HASP message that indicates the transmission is completed. I also think there are some SMF records you could pull that will help to see what happened. I think it is SMF 57 for NJE sysout transmission. Then I would need to look at VTAM or TCPIP which ever is the communications for JES2 to these nodes. But I don't think there is ever a quick answer as to "where did it go". HTH. Lizette > >Our JES2 system was receiving a large transmit file but it never got stored >on spool. Any ideas? > > $HASP540 RUNHSTAX ON L50.SR1 FROM AXMO031 AT AVSCOM1 2,354,384 RECORDS > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
