Hey David,
Jeff sends me files from his VM to my VM all the time so I know the
routes are correct for both directions. The problem is that the file
originated on the VSE system before going to my VM reader so VSE is
getting the messages, not my VM id.
Tony Thigpen
-----Original Message -----
From: David Boyes
Sent: 09/15/2006 10:46 AM
You may not have a complete NJE routing table in place at the
intervening or end nodes. Remember that for NJE to work, all nodes have
to know about all the possible destinations and the path to get there.
Does BSIVM43 have route statements via BSIVSE27 for your nodes, or a
default route for everything via BSIVSE27? If it does not, then you
won't get any messages, because it can't figure out how to get them
there.
David Boyes
Sine Nomine Associates
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
Behalf Of Tony Thigpen
Sent: Thursday, September 14, 2006 7:31 AM
To: [email protected]
Subject: Re: "transfer" reader item to another NJE node
I set up a rexx to do the commands. But, I was playing with trying to
get the same notifications that SENDFILE creates. (Like xxx received
at
xxxx). When I add system options to the tag command, my file no longer
goes where I expect it to go. For example:
This works:
CP TAG FILE 0872 BSIVM43 BARNARD
CP TRANSFER 0872 RSCS
I see (on my userid):
RDR FILE 0872 SENT TO RSCS RDR AS 0176 RECS 0036 CPY 001 V
NOHOLD NOKEEP
0000001 FILE TRANSFERRED
I see on the RSCS console:
07:09:27 File 0176 (0176) enqueued on link BSIVSE27
07:09:28 Sending file 0176 (0176) on link BSIVSE27 from
TEIVM43(VSE310),
records
36
07:09:48 Sent file 0176 (0176) on link BSIVSE27 to BSIVM43(BARNARD)
07:09:48 File 0176 purged
This does not:
CP TAG FILE 0878 BSIVM43 BARNARD ( SENTMSG=YES )
CP TRANSFER 0878 RSCS
I see (on my userid):
RDR FILE 0874 SENT TO RSCS RDR AS 0175 RECS 011K CPY 001 V
NOHOLD NOKEEP
0000001 FILE TRANSFERRED
I see nothing on the RSCS console.
The file goes to the reader of one of my local VSE systems and not to
the correct system. It happens that the original source of the print
file was that same local VSE ssytem.
