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

[Volker Halle · Accepted solution]

Phil,

I think we need some more information.

Could you explain what 'will not give us the same results' refers to ? Any error messages ?

What kind of application is this ?

I don't think this has anything to do with 'I64 OpenVMS disk shadowing'.

Volker.

[Peter Zeiszler]

Is the SANVOL4 disk ODS-5 and the DSA0 system disk also ODS-5?

Is the application accessing the disk via volumen name or device name?

Is the application parsing the disk name and assuming its only 5 characters (this his one of my customers before) DSA0:

[Phillip Tusa]

>Is the SANVOL4 disk ODS-5 and the DSA0 system >disk also ODS-5?

Yes.

>Is the application accessing the disk via >volume name or device name?

We are using a device name with a logical
"MDTSYS" = "DSA400:[MDTSYS.] ..."


Phil

[Volker Halle]

Phil,

so, what IS the problem ???

Volker.

[Brad McCusker]

>We are using a device name with a logical
>"MDTSYS" = "DSA400:[MDTSYS.] ..."

And, what does the logical look like when the application is on the system disk? Please do a show logical /full on both versions of the logical.

Phil - you've got to give us some more information here - give us some sort of description of the different results you see, what you expect to see, etc.

[Guy Peleg]

Phil,

Please post the output of the following:

$ SHOW SHADOW DSA0
$ SHOW SHADOW DSA400
$ SHOW DEVICE/FULL DSA0
$ SHOW DEVICE/FULL DSA400

Differences could potentially rise due
to the following common reasons:higwater
could be turned on on one of the volumes, volumes use different I/O PATH,
cluster size, extent size....

Guy Peleg
BRUDEN-OSSG
http://www.brudenossg.com