POSTMAS@CSUGREEN.BITNET (Colorado State University Postmaster) (12/01/87)
During the past 6-8 weeks we have been unable to correctly receive BITNET jobs at Colorado State from sites such as UMass, FSU, TUCC, UNev. The destination ID is being changed from JOB to SYSTEM on its way here, and we are picking the file up on our SYS RECEIVE stream rather than the JOB RECEIVE stream. We then place the file in the PUNCH queue for the (non-existent) user SYSTEM, when it should go into the input queue. I have heard that VM sites must PUNCH a file to the magic user "JOB" in order to go out on the input (ie JOB) stream. Is it possible that a transmitting node is changing the user ID from JOB to SYSTEM, only to go through a VM site that transmits the file on the SYS OUT stream because the user ID is no longer JOB? Who is changing the user ID from JOB to SYSTEM and why? If a file starts out on the input stream (ie it is a job), what could cause it to be changed to the output stream? Any thoughts on this are very much appreciated. Please reply directly to me. Thanks in advance for your help, Scott Baily Colorado State University Computer Center (303) 491-7655