• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 673
  • Last Modified:

Is it possible to write a SAVF directly onto a WinNT share through QNTC?

We perform a nightly backup to a save file on our AS400, bring the systems back up, then write that save-file to a tape.  Keeping this save-file data in the system adds a significant amount to our overall DASD storage.  My question is:  Is there a method of writing a save file directly to a WinNT file share, through QNTC or otherwise?

Thanks in advance!
0
JUSTICE
Asked:
JUSTICE
  • 3
  • 2
  • 2
  • +1
1 Solution
 
ShadowProgrammerCommented:
I am sure you can FTP a save file onto another platform and FTP it back.

You need to specify the binary option before FTPing between two AS400s - I have never tried it onto a different platform so not sure if you need to specify binary option or not.

Tony.
0
 
ShadowProgrammerCommented:
Just had a quick look on web...

found the following link...

http://www.iseries-user.co.uk/Documents/bravo.htm

Article explains that
(a) it is possible to FTP save file to another platform
(b) sounds like binary option is required
(c) there is a product which allows you some great functionality - I like the thought of restoring indicidual objects from the "save file" without having to pull the whole save file back to the AS400.

Tony.
0
 
Dave FordSoftware Developer / Database AdministratorCommented:
In order to send data from two disparate systems, I do this all the time. It works wonderfully.

Here's an example of FTP'ing to from my iSeries to my local PC:

C:\>ftp mySystem
Connected to mySystem.org.
220-QTCP at MYSYSTEM.ETHERLAN.
220 Connection will close if idle more than 5 minutes.
User (mySystem.org:(none)): dford
331 Enter password.
Password:
230 DFORD logged on.
ftp> bin
200 Representation type is binary IMAGE.
ftp> get dford/daveford c:\daveford.savf
200 PORT subcommand request successful.
150 Retrieving member DAVEFORD in file DAVEFORD in library DFORD.
250 File transfer completed successfully.
ftp: 29568 bytes received in 0.20Seconds 146.38Kbytes/sec.
ftp> bye
221 QUIT subcommand received.

C:\>

I can then FTP the save-file from my PC to the iSeries as needed.

HTH,
DaveSlash
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

 
JUSTICEAuthor Commented:
Sorry to get back to you guys so late.

I know how to FTP a file to a different system, I am wondering if its possible to write it DIRECTLY to the NT system from the AS400.  Wondering if I can somehow point a virtual 'library' to the remote NT file share, etc., so that I dont have to write that temporary .SAVF to the AS400 DASD.  Any other idea's??
0
 
tliottaCommented:
JUSTICE:

You don't tell your OS/400 VRM, but you might want to review the CPYTOSTMF/CPYFRMSTMF commands. Prompt either one and you can see that both support savefiles.

It doesn't take more than a couple minutes practice to catch on, assuming you have a recent enough OS/400 VRM, you have a solid set of PTFs applied, etc., etc.

This is a piece of cake. Ya' got lucky, I think.

Tom
0
 
Dave FordSoftware Developer / Database AdministratorCommented:
To my knowledge, you can only CpyToStmF (or CpyToImpF) to an IFS drive on the '400.  Therefore, it's still going to use AS/400 DASD.  I don't know of any way to send it DIRECTLY to a Windows network drive. I suppose you could set up a program to either:

a) automatically move the exported file from an IFS drive to a Windows network drive nightly

or

b) automatically batch FTP the save-file to a Windows network drive nightly.

HTH,
DaveSlash
0
 
tliottaCommented:
Minor note... If the output path is for example /QNTC/windowsshare/somefile.savf and the job runs under a profile with authority to write to a Windows Network Neighborhood share, and all the stuff that that implies (PTFs, etc.), then the CPYTOSTMF should write (essentially) direct to the Windows PC drive.

Tom
0
 
JUSTICEAuthor Commented:
tliotta:

This does look promising.  We are on release 5.3 of OS/400 with all PTF's, so that shouldnt be an issue.  After some googling I turned up this link also:

http://www.itjungle.com/fhg/fhg032404-story02.html

Thank you everyone who helped!!!
0
 
tliottaCommented:
JUSTICE:

Being current on PTFs generally means a cume level that's no more than one behind current plus a current HI/PER package. DB2 group should also be no more than one behind the current level.

However, neither of those is likely to be sufficient. For NetServer and/or /QNTC, you will need to search out and apply specific individual PTFs. NetServer/QNTC both have enough quirks that cume packages aren't useful.

There are far too many quirks in various configurations of Windows networks. There are unpredictable mixes of servers and fix packs for Windows; there might be domain controllers, logon controllers, Active Directory, DNS, Win2K, WinXP, Win98 clients sending traffic around; netbeui might be directly in use; there might be domain trust issues; Samba might be in your network; etc., etc.

There's no way IBM can create cumulative packages that would cover a major part of Windows network configurations.

Expect to be looking for PTFs that  fit your network.

Tom
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now