VMS Server And WindowXP Client..can make a connection using PAthworks

[Jon Pinkley · Accepted solution]

3>Any other things that can help me.

http://catb.org/esr/faqs/smart-questions.html

http://www.gerv.net/hacking/how-to-ask-good-questions/

And if your other problem doesn't get resolved, this might help you

http://blog.penelopetrunk.com/2007/02/01/how-to-ask-good-questions-in-an-interview/

And depending on your situation, this may be helpful, but not here.

http://www.ehow.com/how_4901958_ask-good-questions-dates.html

[Lucky Regent]

i have following doubts. Please help me out.

1>While installing Pathworks ver 7.4 on Window XP Pro, do we also need to install the same version of pathworks on Vax-VMS?

2> Does Pathworks V7.4 work on Vax/vms 5.2?

[Hakan Zanderau ( Anders]

The version of Pathworks for VMS 5.5-2 is 5.0F

http://h71000.www7.hp.com/pathworks/pathv5.html

You haven't answered my question if this is the server with the bootproblem.

Hakan

[Brad McCusker]

>While installing Pathworks ver 7.4 on >Window XP Pro, do we also need to install >the same version of pathworks on Vax-VMS?

No.

In fact, you do NOT need PATHWORKS on your client PC at all to use PATHWORKS on VMS.

Also, there is no such thing as PATHWORKS V7.4 for OpenVMS.

There is NO releationship between PATHWORKS on the PC and PATHWORKS on VMS. You do not need one to use the other - with one exception: DECnet. If you plan to use DECnet to communicate between your VAX and your PC then you need PATHWORKS on the PC to provide the DECnet stack on the PC. Otherwise, you do not need PATHWORKS on the PC.

The last version of PATHWORKS for OpenVMS V5.5-2 was PATHWORKS V5.0F. PATHWORKS V5.0F does not support Windows XP clients. It may work, but I doubt it. I have never tried it.

As others have said, we could help you more if you would let us know what you are trying to do. If you simply want to move files between the PC and the VAX, then use ftp. If ftp will not work for you, please explain why and tell us what you are trying to do.

Brad McCusker
Software Concepts International
www.sciinc.com

[Hoff]

[Reposting this due to the usual ITRC posting-lost glitch. Apologies, etc.]

With the communications gap obviously arising here (and the fear of job loss and the lack of local OpenVMS VAX skills that are mentioned in your other thread), I would doubt that the ITRC forums are going to lead anywhere but frustration for everybody involved here.

On no evidence other than the apparent unfamiliarity with OpenVMS VAX and related products here, I'd recommend replacing the OpenVMS VAX box with a Windows Server box, or one of the various NAS storage boxes running Windows File Services or analogous. Going to a native-Windows solution.

HP offers ProLiant servers and various NAS boxes that will likely better fulfill your (assumed!) requirements and (assumed!) expectations, and would make the best use of your existing Windows experience and skills.

I just don't think OpenVMS VAX is a good fit here, and suspect that there are better solutions for your particular environment.

Some time spent with a specialist here could help tailor a solution (whether that might use PATHWORKS 32 client on Windows XP and PATHWORKS Server on an upgraded OpenVMS VAX box), or the use of ftp or Filezilla on WIndows and TCP/IP Services on OpenVMS VAX, or a Windows-based environment, or something else) to your particular local requirements. Unlike the hardware service and repair matter from the other thread, this configuration matter can likely be discussed via conference call.

For reference, here is the other referenced thread:

http://forums11.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=1338501

[Lucky Regent]

To:- Anderson
Thanks anderson and That system is working fine now?

To:-Brad...thank you brad for ur useful informations. Still i have some doubts:- here they go:-

We used to FTP(TCP/IP) connection between Window XP and VAX/VMS machine to tranfer data.

Now we want to connect Window XP and VAX?VMS machine vie Pathworks. SO make a connection between these two vie PAthworks do we need to install same version of pathworks on the Both machines.

Or if vax machine has other version of Pathworks and XP has another version of pathworks. CAn we make a pathworks connection between these machines?

what other requirement should be met to accomplish this task??

[Jon Pinkley]

RE: what other requirement should be met to accomplish this task??

The ability to read and understand the documentation.

[Hakan Zanderau ( Anders]

>To:- Anderson
>Thanks anderson and That system is working fine now?

Could you share the solution with all of us who tried to help you by updating the thread

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1338501

and maybe close it ?

Pathworks isn't just something you install and then leave..... it needs configuration and maintenance.

Hakan

BTW....have you started to take backups on this machine now ? before doing further installations/changes ?

[Lucky Regent]

To:-Anderson

Ok i will update that thread.. we still did not take any backups of that system.

I know we need some more things despite of just installing pathworks.

But i want to confirm that can it be possible to make a connection using pathworks between vax/vms and Win XP pro having different version of pathworks.

[Hakan Zanderau ( Anders]

The server- and client- application is two different applications.

The server version you need is PW 5.0F

Hakan