Skip to main content

Hi All

Perhaps a short one, but can someone please confirm that the super Q pointers ONLY work across D3 installations with THE SAME rev version?

Assuming the hosts file has been setup correctly for this exercise .


IOW, I should NOT expect to communicate (as via a LIST verb) to D3 machine A (where A is D3 version 10.x) and an older D3 version (say 7.x).

I am able to do same 7.x to 7.x - that's OK BUT NOT 10.x to 7.x

Just require confirmation. Or is there a solution which I don't know of?

Thanks

Hi All

Perhaps a short one, but can someone please confirm that the super Q pointers ONLY work across D3 installations with THE SAME rev version?

Assuming the hosts file has been setup correctly for this exercise .


IOW, I should NOT expect to communicate (as via a LIST verb) to D3 machine A (where A is D3 version 10.x) and an older D3 version (say 7.x).

I am able to do same 7.x to 7.x - that's OK BUT NOT 10.x to 7.x

Just require confirmation. Or is there a solution which I don't know of?

Thanks

I assume, since you're D3-Linux-centric, that you're talking about using network-setup to define OSFI servers, the use Q-pointers using this form:

otherserver:account,file,

If so, I just successfully tested that in both directions from a D3 9.0 machine (CentOS 6.4) and a D3 10.3.4 machine (RedHat 9.0).

If you're talking about FSI: connections from D3 Windows to D3 Windows, that depends on RPC, and I'm pretty sure that D3 versions 9 and 10 cannot FSI to each other.

Hi All

Perhaps a short one, but can someone please confirm that the super Q pointers ONLY work across D3 installations with THE SAME rev version?

Assuming the hosts file has been setup correctly for this exercise .


IOW, I should NOT expect to communicate (as via a LIST verb) to D3 machine A (where A is D3 version 10.x) and an older D3 version (say 7.x).

I am able to do same 7.x to 7.x - that's OK BUT NOT 10.x to 7.x

Just require confirmation. Or is there a solution which I don't know of?

Thanks

Yes you can use to list data, BUT
if you have CALL in the DICT somethngs may fail due the break of the backword compatibles, but if its only pure text (raw data) it works just fine, another thing you can't run basic programs in different envs because of the same reason ( only tested with linux )

Hi All

Perhaps a short one, but can someone please confirm that the super Q pointers ONLY work across D3 installations with THE SAME rev version?

Assuming the hosts file has been setup correctly for this exercise .


IOW, I should NOT expect to communicate (as via a LIST verb) to D3 machine A (where A is D3 version 10.x) and an older D3 version (say 7.x).

I am able to do same 7.x to 7.x - that's OK BUT NOT 10.x to 7.x

Just require confirmation. Or is there a solution which I don't know of?

Thanks

Thanks @Brian Cram, I'll check the network-setup but I know I have an entry in the HOSTS file

BTW - restarting hosts worked - thanks

Hi All

Perhaps a short one, but can someone please confirm that the super Q pointers ONLY work across D3 installations with THE SAME rev version?

Assuming the hosts file has been setup correctly for this exercise .


IOW, I should NOT expect to communicate (as via a LIST verb) to D3 machine A (where A is D3 version 10.x) and an older D3 version (say 7.x).

I am able to do same 7.x to 7.x - that's OK BUT NOT 10.x to 7.x

Just require confirmation. Or is there a solution which I don't know of?

Thanks

You may have the host defined, but you also have to start the servers in network-setup. Do a lu or list-jobs to see if they're running.

Terms & ConditionsAccessibility statement