--* From SYSTEM@yktvmv.watson.ibm.com  Sat Feb 26 13:54:29 1994
--* Received: from yktvmv.watson.ibm.com by leonardo.watson.ibm.com (AIX 3.2/UCB 5.64/4.03)
--*           id AA26272; Sat, 26 Feb 1994 13:54:29 -0500
--* X-External-Networks: yes
--* Message-Id: <9402261854.AA26272@leonardo.watson.ibm.com>
--* Received: from watson.vnet.ibm.com by yktvmv.watson.ibm.com (IBM VM SMTP V2R3)
--*    with BSMTP id 6941; Sat, 26 Feb 94 13:54:11 EST
--* Received: from YKTVMV by watson.vnet.ibm.com with "VAGENT.V1.0"
--*           id <N.*UNKNOWN.NOTICE.RSCS.6195.Feb.26.13:54:10.-0500>
--*           for asbugs@watson; Sat, 26 Feb 94 13:54:11 -0500
--* From: "Greg Puhak" <puhak@yktvmv.vnet.ibm.com>
--* X-Sender-Data: Network Management and Systems Applications
--*                T. J. Watson Research Center
--* To: "Sender of File 6425" <asbugs@watson.vnet.ibm.com>
--* X-Unparsable-Date: 02/26/94, 13:54:10
--* Subject: File 6425(6425), "ASBUGS NOTE", for PAB at RADICAL
--* Date: Sat, 26 Feb 94 13:54:11 EST  

--@ Fixed  by:  SSD   Fri Jun 3 12:28:01 EDT 1994 
--@ Tested by:  none 
--@ Summary:    Not a bug. 

We have received the above referenced file, 6425, from you.  Its
destination was for node RADICAL.  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 10 records and was sent at 13:54:10 on 02/26/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 6425
   To CHANGE the destination of the file, issue:
      CP SMSG RSCS TRANSFER 6425 TO newnode newuser

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

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

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

VM VNET users:
   To PURGE the file, issue:
      TELL *UNKNOWN AT YKTVMV PURGE 6425
   To CHANGE the destination of the file, issue:
      TELL *UNKNOWN AT YKTVMV TRANSFER 6425 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".  This will cause that line to be executed.  The same
concept applies to purging a file.

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, Greg