Clean up XWB

Bug #404640 reported by jeff.apple
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenVista/GT.M Integration
Fix Released
Medium
jeff.apple

Bug Description

XWB has a few rough spots:

1) Apply the hotfix to BREAD^XWBRW that detects if a network error occurs. The unmodified code only works well under Cache, which seems to set $T=0 on error (which is not standard).
2) While at it, clean adjacent code as well. The timeout value supplied is not actually used as the number of second. It works out that the timeout value will be twice what is supplied.
3) CONNTYPE^XWBTCPM uses a hard-coded timeout of 5. Could this be made a system parameter?
4) On a new log-in, a local variable is set to "XUS SIGNON", but the context is never actually set. If there is junk in ^TMP from a previous connection it will interfere and prevent XUS SIGNON SETUP from running.
5) Should setting the context to "" clear ^TMP? Seems like it should.

Jon Tai (jontai)
Changed in openvista-gtm-integration:
assignee: nobody → jeff.apple (jeff-apple)
importance: Undecided → Medium
milestone: none → 0.8.5
Revision history for this message
jeff.apple (jeff-apple) wrote :

To the points above:
1) Done.
2) It's messy but works, so I'm going to leave it. The code does cut the timout value by half, so the wait time is right after all.
3) I looked at this wrong. It's OK as it stands.
4) Done.
5) Done.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.