--* From SYSTEM@yktvmv.watson.ibm.com  Tue Oct 11 06:04:10 1994
--* Received: from yktvmv-ob.watson.ibm.com by asharp.watson.ibm.com (AIX 3.2/UCB 5.64/930311)
--*           id AA21059; Tue, 11 Oct 1994 06:04:10 -0400
--* Message-Id: <9410111004.AA21059@asharp.watson.ibm.com>
--* Received: from watson.vnet.ibm.com by yktvmv.watson.ibm.com (IBM VM SMTP V2R3)
--*    with BSMTP id 3233; Tue, 11 Oct 94 06:04:15 EDT
--* Received: from YKTVMV by watson.vnet.ibm.com with "VAGENT.V1.0"
--*           id <N.*UNKNOWN.NOTICE.RSCS.9543.Oct.11.06:04:12.-0400>
--*           for asbugs@watson; Tue, 11 Oct 94 06:04:15 -0400
--* From: "Earl Hartley" <whirl@yktvmv.vnet.ibm.com>
--* X-Sender-Data: Network Support
--*                T. J. Watson Research Center
--* To: "Sender of File 4078" <asbugs@watson.vnet.ibm.com>
--* X-Unparsable-Date: 10/11/94,  6:04:12
--* Subject: File 4078(4078), "ASBUGS NOTE", for AXIOM at NAGRS1
--* Date: Tue, 11 Oct 94 06:04:15 EDT  

--@ Fixed  by:  SSD   Tue Nov 8 10:13:14 EST 1994 
--@ Tested by:  none 
--@ Summary:    Not a bug. 

We have received the above referenced file, 4078, from you.  Its
destination was for node NAGRS1.  This is not recognized as a VNET or
BITNET node nor is it known locally here at Watson.  The file is class A,
dist VAGENT2, has 56 records and was sent at  6:04:12 on 10/11/94.

The file has not been purged but is being held for you in the *UNKNOWN
queue.  If you do not wish to pursue the matter any further please PURGE
the file.  Otherwise, you can CHANGE the destination to have it continue
on to a new userid and/or new node.

Based on the origin node of this file, WATSON, find which group of
commands below applies to you and then either purge or transfer the
file.  See below for a helpful hint about issuing these commands while
PEEKing this notice.

Local YKTVMV users:
   To PURGE the file, issue:
      CP SMSG RSCS PURGE 4078
   To CHANGE the destination of the file, issue:
      CP SMSG RSCS TRANSFER 4078 TO newnode newuser

YKTOV users:
   To PURGE the file, issue:
      CP SMSG RSCSOV CMD YKTVMV PURGE 4078
   To CHANGE the destination of the file, issue:
      CP SMSG RSCSOV CMD YKTVMV TRANSFER 4078 TO newnode newuser

WATSON users on Agora:
   To PURGE the file, issue:
      /contrib/bin/tell @YKTVMV purge 4078
   To CHANGE the destination of the file, issue:
      /contrib/bin/tell @YKTVMV transfer 4078 to newnode newuser

WATSON users in general (must log on to YKTVMV first):
   To PURGE the file, issue:
      CP SMSG RSCS FROM WATSON ASBUGS CMD YKTVMV PURGE 4078
   To CHANGE the destination of the file, issue:
      CP SMSG RSCS FROM WATSON ASBUGS CMD YKTVMV TRANSFER 4078 TO newnode newuser

VM VNET users:
   To PURGE the file, issue:
      TELL *UNKNOWN AT YKTVMV PURGE 4078
   To CHANGE the destination of the file, issue:
      TELL *UNKNOWN AT YKTVMV TRANSFER 4078 TO newnode newuser

MVS and other workstation VNET users:
   Correct the userid and/or node and resend the file.

In all cases:
newnode  is the new node to transfer the file to (can be YKTVMV)
newuser  is the new userid to transfer the file to

Helpful Hint: If you use PEEK to view this notice you can simply type
over newnode and newuser above, then make that line the current line and
type "STACK 1 1 100".  This will cause that line to be executed.  The
same concept applies to purging a file.  (Simply saying "STACK" will
usually work but doesn't for issuing commands locally, i.e. CP SMSG RSCS
PURGE|TRANSFER ...)

If nothing is done about this file within 3 days, it will be removed
from the queue automatically -- in less time given system constraints.

Regards, Earl