Invalid timeout value in LA7UID2

[jeff.apple]

GTM can not handle very, very large timeout values. Q6249^LA7UID2 has one of these at Q6249+5. The timeout given is 9999999, which causes an immediate fault.

Such a large value is most likely meaningless. It should either be made much smaller, or removed completely.

[Jon Tai (jontai)]

Jeff, since the problem is in a LA routine and not in the kernel, should we fix this in a lab patch for OpenVista Server (and not roll the fix into our KIDS build)? Do you know if we have an OpenVista Server artifact for this open internally already?

[jeff.apple (jeff-apple)]

I did not record this problem anywhere but here. It does seem like it should be fixed as a lab patch.

[Jon Tai (jontai)]

This will be fixed in an update to OpenVista Server, likely 1.5 SP4.

[Jon Tai (jontai)]

For reference, 2147483 is the maximum timeout value for 32-bit GT.M V5.3-004. That's a little over 24 days. Larger timeouts cause the following error:

%GTM-E-TIMEROVFL, Timer overflow; interval probably too large

The upcoming fix in OpenVista Server reduces the timeout to 99999 (approximately 27 hours).

[Jon Tai (jontai)]

OpenVista Server 1.5 Service Pack 4 was released Jun 2, 2010. The build that fixes the issue is MSCLR UNIVERSAL INTERFACE*1.5*1, in MSCLR_UNIVERSAL_INTERFACE_1501.KID