I think the problem is the files ORIGINID. I did a SENDFILE of a file to
myself. Then I used the transfer exec. For this I get messages:
jeff 920
15 *-* 'CP TAG FILE' rdrid who '50' tagopts
>>> "CP TAG FILE 920 BSIVM43 BARNARD 50 (ACcmsg=Yes
ENQmsg=Yes FINalm
sg=Yes SEntmsg=Yes)"
16 *-* 'CP TRANSFER' rdrid rscid
>>> "CP TRANSFER 920 RSCS"
RDR FILE 0920 SENT TO RSCS RDR AS 0190 RECS 0013 CPY 001 A
NOHOLD NOKEEP
0000001 FILE TRANSFERRED
File 0190 accepted for transmission to BSIVM43(BARNARD)
File 0190 (0190) enqueued on link BSIVSE27
Ready; T=0.01/0.03 11:14:17
Sent file 0190 (0190) on link BSIVSE27 to BSIVM43(BARNARD)
From BSIVM43: DMTAXM104I File (0190) spooled to BARNARD -- origin
TEIVM43(TTHI
GPEN) 09/14/06 11:13:59 EDT
From BSIVSE27: 1RA0I OUTPUT RSCS0190 00900(00190) TRANSMITTED TO
BSIVM43 FOR
BSIVM43 O-TR1
query rdr * all
ORIGINID FILE CLASS RECORDS CPY HOLD DATE TIME NAME TYPE
TTHIGPEN 0923 A PUN 00000013 001 NONE 09/14/2006 11:18:31 JUNK JUNK
VSE310 0925 V PRT 00000011 001 NONE 09/14/2006 11:18:39 LIBR 10931
Tony Thigpen
-----Original Message -----
From: Tony Thigpen
Sent: 09/14/2006 11:08 AM
The final system is a VM system. The VSE is just a hop. I can't accept
that as the problem because when I do a SENDFILE, I do DO get a message:
sf junk junk a to barnard at bsivm43
File JUNK JUNK A1 sent to BARNARD at BSIVM43 on 09/14/2006 10:52:27
Ready; T=0.03/0.05 10:52:27
From BSIVSE27: 1RA0I OUTPUT RSCS0183 00893(00183) TRANSMITTED TO
BSIVM43 FOR
BSIVM43 O-TR1
I just want this same message when I transfer the file from my RDR. The
following is being performed ("jeff" is the exec name):
jeff 821
15 *-* 'CP TAG FILE' rdrid who '50' tagopts
>>> "CP TAG FILE 821 BSIVM43 BARNARD 50 (ACcmsg=Yes
ENQmsg=Yes FINalm
sg=Yes SEntmsg=Yes)"
16 *-* 'CP TRANSFER' rdrid rscid
>>> "CP TRANSFER 821 RSCS"
RDR FILE 0821 SENT TO RSCS RDR AS 0187 RECS 0446 CPY 001 V
NOHOLD NOKEEP
0000001 FILE TRANSFERRED
Ready; T=0.01/0.03 10:59:21
I just went and changed the RSCS CONFIG file to turn on all message
options. I still do not see what I want, but now the outputs are:
jeff 796
15 *-* 'CP TAG FILE' rdrid who '50' tagopts
>>> "CP TAG FILE 796 BSIVM43 BARNARD 50 (ACcmsg=Yes
ENQmsg=Yes FINalm
sg=Yes SEntmsg=Yes)"
16 *-* 'CP TRANSFER' rdrid rscid
>>> "CP TRANSFER 796 RSCS"
RDR FILE 0796 SENT TO RSCS RDR AS 0188 RECS 0039 CPY 001 V
NOHOLD NOKEEP
0000001 FILE TRANSFERRED
Ready; T=0.01/0.03 11:04:26
sf junk junk a to barnard at bsivm43
File 0189 accepted for transmission to BSIVM43(BARNARD)
File 0189 (0189) enqueued on link BSIVSE27
File JUNK JUNK A1 sent to BARNARD at BSIVM43 on 09/14/2006 11:05:09
Ready; T=0.03/0.05 11:05:09
Sent file 0189 (0189) on link BSIVSE27 to BSIVM43(BARNARD)
From BSIVM43: DMTAXM104I File (0189) spooled to BARNARD -- origin
TEIVM43(TTHI
GPEN) 09/14/06 11:05:08 EDT
From BSIVSE27: 1RA0I OUTPUT RSCS0189 00899(00189) TRANSMITTED TO
BSIVM43 FOR
BSIVM43 O-TR1
Tony Thigpen
-----Original Message -----
From: Les Geer (607-429-3580)
Sent: 09/14/2006 08:48 AM
Adding the priority fixed the initial problem. Kinda different from the
normal way parameters and options are processed.
I am still not getting the transfer messages I expect. I am now using:
CP TAG FILE 0846 BSIVM43 BARNARD 50 (ACcmsg=Yes ENQmsg=Yes FINalmsg=Yes
SEntmsg=Yes)
I am getting no completion messages from RSCS.
The completion message, or final message (this is the message you
are interested in correct?) would come from the destination node,
which in this case is VSE which doesn't understand those TAG
parameters.
Best Regards,
Les Geer
IBM z/VM and Linux Development
