I64 OpenVMS Disk Shadowing Question

[Phillip Tusa]

Greetings to all!

We have three rx-2620 clustered together using OpenVMS v8.2-1 and Disk Shadowing.

When we try to run an application on the SANVOL4 disk (designated as DSA400:), the application will not give us the same results when we run the application on the system disk (designated DSA0:). In other word the application runs as it is designed on the system disk DSA0: We are attempting to load
and run the application in a common area so all three I64 boxes can "see" the application results.


Any assistance would be appreciated, thanks!

Phil

[Heinz W Genhart]

Hi Phillip

that means, the application was originaly installed on the systemdisk and then moved?

If so, there could be a problem in the applications startup procedure, or in a procedure called by it. Did you reflect the new environment in the applications startup commandfile?

What you could do is a

$ search disk-whre-application-is:[000000...]*.com dsa0

This way you can find every commandfile where dsa0 is in it.

Or could you give us a more precise informations. What is the error message, what is not running?

Regards

Geni

[Phillip Tusa]

>Did you reflect the new environment in the >applications startup commandfile?

The application is a .exe file. We use a logical to refer to its location.

i.e. "MDTSYS" = "DSA400:[MDTSYS.] ..."


>What is the error message, what is not >running?

When we try to run the application on the SANVOL (DSA400:) The application will not
display the correct information.

It works just fine on the system disk DSA0:


Any suggestions?

Phil

[Heinz W Genhart]

Hi Phil

"The application is a .exe file. We use a logical to refer to its location."

"MDTSYS" = "DSA400:[MDTSYS.]

This logical, should it be a concealed Device? I'm wondering about the .] (the dot)

There are at least two possibilities:

The logical is defined as

$ define/sys/exec mdtsys dsa4:[mdtsys]
Then you may run a program like this

$ r mdtsys:program.exe


or
the logical is defined as a concealed device

$ define/sys/exec/trans=(terminal,conceal) mdtsys dsa4:[mdtsys.]
Then you may run a program like this

$ r mdtsys:[000000]program.exe
or
$ r mdtsys:[bin]progrmm.exe if th program is located at dsa4:[bin]

could this be the problem?

Regards

Geni

[Jan van den Ende]

Phil,

to start with:

Welcome to the VMS forum!

With the info we have now, it is entirely possible that Geni has the solution, but there is too little info to tell.

As always, the real error message, together with the part of the code that generates it, is more likely to lead to the real reason behind the "issue".

One minor remark on Geni's answer:

>>>
$ define/sys/exec/trans=(terminal,conceal) mdtsys dsa4:[mdtsys.]
<<<

Note that the translation attibute "terminal" is no longer needed for concealed devices.

Do the search for "DSA0:" in all code used, it REALLY should be replaced by references of MDTSYS.

Proost.

Have one on me.

jpe

[Robert Gezelter]

Phil,

Let me also welcome you to the OpenVMS Forum.

First, it is highly unlikely that the problem you are experiencing is in any way related to shadowing.

It is extraordinarily difficult to diagnose a problem from the limited information in the posting. At first glance, my personal speculation would likely center on a file reference that IS NOT to the designated logical name (and is thus sometimes pointing to the wrong place). Of course, while that is based on many years experience, it is speculation on thin evidence.

If you can localize the problem, that is an immense help. I am sure that we will be happy to assist you publicly in the forum. If privacy is desired, there are several active members of this forum available on a consulting basis (disclaimer: My firm does provide such services).

- Bob Gezelter, http://www.rlgsc.com