NFT File Transfers Failing

[Christopher Rogers_2]

I am having an issue using NFT.EXE on a Windows 2003 Server. This computer is running a command line job that we are using to transfer data to our VAX. For a day or 2 the job will go through without incident, then without notice all of the NFT procedures fail. Has anyone seen this before or have any suggestions? The only thing that has worked for us so far is to reboot the Windows 2003 server.

Thanks,

Chris

[Volker Halle]

Chris,

could you provide information about the type of NFT operation you're trying to execute (maybe an example of the excact command) and the associated error message ?

Volker.

[Arch_Muthiah]

Chris,
Using Pathworks NFT or DOS NFT?
There was a infor about NFT command WILL NOT copy the files correctly for use with VMS. Some time hanging or other problems.

Make sure you have installed ncd_serv.com as an NCP in VMS side. You can copy this from PC-Xware installation
directory.
$NFT COPY ncd_serv.com vaxhost"user password":: ncd_serv.com and install it. and try again.

I would suggest to use C-Kermit or some other transfer method.

Archunan

[Andy Bustamante]

What version of Pathworks 32 are you using on the Windows 2003 PC?

Check the Pathworks log, in version 7.4, there is a problem where connectivity will fail after "about a day" in our environment. You'll see a message like "Added 32 packets to the datalink buffer pool, total=xxx", after xxx hits 512, connectivity dies.

There's a new DECDNP.SYS available from HP, you'll need to log a call with the support center, I don't think this is available for download.

Andy

[Christopher Rogers_2]

Here is what I is running:

nft DIR 1.3"userid password"::dsk4:[warehouse.corvision.shipping]orders.dat

NFT COPY 1.3"userid password"::dsk4:[warehouse.corvision.shipping]orders.dat;1 E:\transfer

I am using the NFT.exe from the unsupported folder. This was working fine for several years on our Windows NT 4.0 server, but since we went to Windows 2003, some of these issues have cropped up.

[Christopher Rogers_2]

Also forgot to add we are using Pathworks v 7.4.

[Christopher Rogers_2]

Some more info. I appear to be getting an EventID 8032 from the BROWSER:

The browser service has failed to retrieve the backup list too many times on transport \Device\DECDNP_DECNDIS_{FB5B9C41-B700-474D-8EAE-EEAA56B4A18B}. The backup browser is stopping.

Could this be related?

[Arch_Muthiah]

chris,

Pathworks V6.x onwords supports win2003. So this is not a problem

You mentioned you have VAX system, what is VMS version? if your VAX/OpenVMS Version is less than 6.2, then it won't support the latest pathworks 6.1 and after.


Archunan

[Christopher Rogers_2]

We are running VMS V6.1. So this one won't work?

[Christopher Rogers_2]

I forgot to mention we are only using Pathworks for the DECNET and LAT. Mainly PowerTerm and file transfers. So would the VMS version matter in that context?

[Arch_Muthiah]

Yes Chris, if your VAX/OpenVMS Version is less than 6.2, then it won't support the latest pathworks 6.1 and after.

I remember that prior version of pathworks (prior to V6.1) had no complaints negotiating with domain name server. So I would suggest to either to back to pathworks v6.0 or upgrade your VAX OpenVMS to 7.3.


Archunan

[Volker Halle]

Chris,

what kind of errors are you getting from these NFT commands ? Did you consider Andy's entry and check the Pathworks log ?


Archunan,

Chris is talking about Pathworks 32 V7.4, which is the software running on the Windows PC. If this just means using DECnet, LAT and PowerTerm from the PC, Pathworks on the VAX would not be directly involved.

Volker.

[Arch_Muthiah]

Chris,

Please go thru this two release notes which clearly mentions about the supported VAX OpenVMS Version for your Pathworks 7.4 on Win2003.

Volker,

I am also talking about Pathworks Client s/w only.

Whether it is a PATHWORKS 32 V7.4 client or the pathworks server (PATHWORKS 6.1 or AS 7.3A), the OpenVMS version is also a important matter. As I said earlier, to run Pathworks 32 7.4 client, we need have OpenVMS 6.2 or latest OpenVMS 7.3 on VAX.

The same is applicable for PATHWORKS sever (Advanced Server) too.

Please go thru this release notes I have attached...
http://h18000.www1.hp.com/info/SP5633/SP5633PF.PDF
http://h18000.www1.hp.com/info/SP3050/SP3050pf.pdf


Archunan

[Volker Halle]

re: Archunan,

the Pathworks 32 client functions Chris is using (Powerterm via LAT, NFT via DECnet) do NOT require ANY Pathworks functionality on the OpenVMS VAX host, so the Pathworks version on the OpenVMS host would be irrelevant. You can use Powerterm or NFT to any OpenVMS system, which doesn't even know about Pathworks.

The fact that OpenVMS versions are listed in the Pathworks 32 SPD is ONLY relevant, if you want to run DECnet over TCP/IP, as this is not available in the older OpenVMS versions.

I cannot find any reference in the Pathworks Client V7.4 SPD about Pathworks versions on the OpenVMS host.

Volker.