Tony, Perhaps try - COPYFILE SENDFILE SEXEC S SENDFILE EXEC A - Modifying SENDFILE EXEC A to issue a CP TAG QUERY PUN just before the file is punched to RSCS - Issue SET INSTSEG OFF (to bypass the EXECLOADed SENDFILE) - run SENDFILE as usual to see what it is actually using - Try using the same arguments with your TAG command - ERASE SENDFILE EXEC A
Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Tony Thigpen" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <[email protected]> 09/14/2006 10:08 AM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Re: "transfer" reader item to another NJE node 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 > > The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
