This isn't true. I just successfully "got" a VSAM file from VSE
using the CMS FTP client. VSE of course must have an FTP daemon
running. In this case the FTP daemon is the CSI TCP/IP for VSE
product (the one that IBM distributes with VSE). I used standard
ftp commands: open, dir, cd, etc. When I had navigated to the
directory which represented the VSAM catalog, I issued the get
command. The VSAM file name in this case was SAFEPR.UPLD. Here's the
console showing the "get" command:
get safepr.upld this.file
>>>PORT 10,10,1,228,9,66
200 Command okay.
>>>RETR safepr.upld
150-About to open data connection
File: VSAM/SAFEPR.UPLD
Type: ASCII Recfm: FB Lrecl: 80 Blksize: 80
CC=ON UNIX=ON RECLF=OFF TRCC=OFF CRLF=ON
Translate with US_ENG_03
150 File status okay; about to open data connection
226-Bytes sent: 41,814
Records sent: 606
Transfer Seconds: 1.47 ( 40K/Sec)
File I/O Seconds: 1.46 ( 40K/Sec)
226 Closing data connection.
41814 bytes transferred in 1.486 seconds. Transfer rate 28.14 Kbytes/sec.
- Tom.
At 01:38 PM 1/13/2006, you wrote:
> I am trying to "get" a VSE VSAM file and looked up
> instructions on how to specify VSE file names and "trees",
> but could not find them. Any notes or links will be greatly
> appreciated.
You can't do it with the VM FTP server or client. DOS simulation I/O
and/or VSAM are not supported by these tools.
You need a VSE-based FTP server which understands VSAM files to do this.
Tom Cluster
County of Sonoma
Santa Rosa, CA
(707) 565-3384 (Tuesdays and Wednesdays only)
