Hi Mike,
Thanks for the info.  I would appreciate a sample to give me a quick 
understanding of how it works.  

Thanks to ALL who have responded.

Kind Regards,
Steve



-----Original Message-----
From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf 
Of Mike Walter
Sent: Wednesday, December 08, 2010 4:38 PM
To: [email protected]
Subject: Re: FTP within REXX EXEC

I recommend the very flexible VMFTP shareware.  You write macros as REXX execs, 
giving you complete control of the FTP session.

For example, we sometimes send VMDUMPs to a particular ISV (each ISV has its 
own exec/macro).  Some want the VMDUMP "COPYFILE (PACK"ed before sending (doing 
so preserves record lengths of variable length files when UNPACK'ed at the 
other end).  Rather than documenting all their preferences, and target 
directory naming conventions, I wrote an FTP2isv EXEC and VMFTP macro (where 
"isv" is the ISV's initials).  From FILELIST on the VMDUMP, I enter:
     FTP2isv / outputfn outputft issue_number The FTP2isv process checks to 
ensure that the file is already COPYFILE PACK'ed, or it find free disk space 
and does it, then calls the FTP2isv VMFTP macro (again, all written in REXX), 
establishes the FTP session, issues all the preferred FTP commands (e.g.  'BIN 
FIXED 1024', 'CD dirname', 'PUT  ifn.ift.ifm  ofn.oft', 'QUIT').  That makes 
life a lot easier.

z/VM users can easily FTP files to their z/VM userid from z/OS by running a 
local FTPFMZOS EXEC, which in turns calls a FTPFMZOS VMFTP macro.

We've also used it to write execs/macros that send a batch job via NJE to our 
z/OS systems, which in turn connects back to z/VM to FTP very large (both LRECL 
and number of records) files from a target disk, then runs additional 
application programs on z/OS.  When the job completes, the initial (still 
waiting) exec sees the messages sent via NJE and cleans up work files on the 
user's disk. 

The VMFTP package can be obtained from: 
 
     Fran Hensler's excellent Slippery Rock University FTP site with 
     the most recent updates as of 2009-03-13 at: 
 
         http://zvm.sru.edu/~DOWNLOAD/ 

It's well worth the time you'll spend installing it and becoming familiar with 
it.  I could send a sample of one of our simpler EXEC/VMFTP macros if you'd 
like.

Mike Walter
Aon Corporation
The opinions expressed herein are mine alone, not my employer's.




Steve Perez <[email protected]> 

Sent by: "The IBM z/VM Operating System" <[email protected]> 12/08/2010 
04:05 PM Please respond to "The IBM z/VM Operating System" 
<[email protected]>



To
[email protected]
cc

Subject
FTP within REXX EXEC






Hello Listers,

I have written an REXX exec to file transfer monitor data files from our z/VM 
Lpar to our z/OS Lpar using FTP.  The following is an excerpt from that code:

push 'quit' 
push put TEST.FILE.A 'my.zos.dsn' 
... other ftp commands here ... 
'FTP' ftpaddress

My question is.  What can I do to retrieve the return code if this fails or is 
successful?  Or any other ideas or suggestions I can use to determine if the 
file successfully transferred?

Thanks in advance for any and all replies.

Steve.






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. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by e-mail. 
******************************************************************************************
 
This message may contain confidential or proprietary information intended only 
for the use of the 
addressee(s) named above or may contain information that is legally privileged. 
If you are 
not the intended addressee, or the person responsible for delivering it to the 
intended addressee, 
you are hereby notified that reading, disseminating, distributing or copying 
this message is strictly 
prohibited. If you have received this message by mistake, please immediately 
notify us by  
replying to the message and delete the original message and any copies 
immediately thereafter. 

Thank you. 
******************************************************************************************
 
CLLD

Reply via email to