|
View previous topic :: View next topic
|
| Author |
Message |
srinivas_cog
New User
Joined: 05 Jun 2008
Posts: 17
Location: chennai
|
|
|
|
Hi,
I need to ftp my mainframe file as .txt with date and time extension.
ex:
i have file1 as mainframe file, i need to ftp this file like
file1.200806271202 (ccyymmddhhmm).txt
PUT 'Mainframe dataset name' file1.CCYYMMDDHHMM.TXT .
When i searched in forums it is saying that not possible. Is there any way
Thanks |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| file1.200806271202 (ccyymmddhhmm).txt |
This is an invalid mainframe dataset name - dsn nodes must be less than 9 characters and cannot begin with a numeral.
This does not mean that you cannot ftp some file to a remote location and use that name. UNIX and Windows have more flexible file naming rules.
If you create a file named MY.MAINFRM.FILE - you can ftp it and use tHe name you want to use ON THE TARGET SYSTEM. Something like:
| Code: |
PUT MY.MAINFRM.FILE file1.200806271202.txt |
|
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
If your site has CA-7, you can use CARPROC to generate the date for the file name. If your site has a different scheduler, see if it can generate date fields.
Or, write a program to create the FTP commands with the date as part of the file name and run that program before running your FTP step, which would get input from the program's output.
Otherwise, the long way around would be to set up your JCL with step 1 being a Unix System Services shell script that creates the desired FTP commands, step 2 being an OGET to transfer the FTP commands to an MVS file name, and step 3 being the actual FTP execution, using as input the commands generated in step 1.
Since MVS systems do not have intrinsics for the date, these are pretty much your only options. |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| This topic is for almost exactly the same requirement. |
|
| Back to top |
|
|
|
|
