BOX:VOLUME pair should not contain hostname

Bug #422885 reported by Jon Tai on 2009-09-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenVista/GT.M Integration

Bug Description

In GETENV^ZOSVGUX (which is saved as GETENV^%ZOSV on GT.M/Unix systems), the the third piece and the second part of the fourth piece of the return value is determined by executing "hostname -s". For example, if the machine's hostname was "localhost", GETENV might return "OPEN^OPEN^localhost^OPEN:localhost".

The fourth piece, the BOX:VOLUME pair, is used by Taskman to determine the current BOX:VOLUME pair. There are two disadvantages to having the hostname of the machine included in the BOX:VOLUME pair. First, every time you move an OpenVista instance to a system with a different hostname, you must update the TASKMAN SITE PARAMETERS file. Second, in a failover cluster environment, you have to either: arrange for this configuration to be updated when failing over, have two sets of Taskman/RPC broker configuration, or name your cluster nodes with the same hostname.

On Cache systems, the second part of the BOX:VOLUME pair is determined by a call to $ZU(86), which returns (in the second *-separated piece) the name of the current Cache configuration. Since we do not have an equivalent configuration on GT.M systems, the next best thing is to hard-code it to a known value such as "GTM".

This change would mean that there is now effectively only one set of TASKMAN SITE PARAMETERS. The same set of parameters would take effect regardless of what host OpenVista is running on. This works well for us in practice, since we don't run more than one instance of Taskman at a time (in fact, we don't run any OpenVista processes on more than one machine at a time). However, the change may break backward compatibility.

Related branches

Jon Tai (jontai) on 2009-09-01
Changed in openvista-gtm-integration:
status: New → Fix Committed
Jon Tai (jontai) on 2009-10-19
tags: added: cluster
Changed in openvista-gtm-integration:
importance: Undecided → High
Jon Tai (jontai) wrote :

After discussing this with Rick Marshall, I've updated the patch to return the value of ^%ZOSF("CLUSTER") if it exists instead of hard-coding a string. This has a number of advantages -- it's backwards compatible for folks who are upgrading, it preserves the flexibility to have TaskMan configured differently on different machines, and it still allows cluster users to have a host-independent value if they need it.

Future releases of OpenVista Server are likely to have ^%ZOSF("CLUSTER") set to "GTM" so that new users will not have to set their hostname before running TaskMan. Advanced users who require multiple TaskMan setups can simply K ^%ZOSF("CLUSTER") to restore the old functionality.

Jon Tai (jontai) on 2009-11-24
Changed in openvista-gtm-integration:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers