- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: debugger motif error codes?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2004 07:02 AM
тАО02-26-2004 07:02 AM
debugger motif error codes?
XIO: fatal IO error 65535 on X server "_WSA17:"
VMS V722, with MUP applied. 'UCX' V5.1
thanks,
Tym
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2004 07:32 AM
тАО02-26-2004 07:32 AM
Re: debugger motif error codes?
ana/sys
tcpip
tcpip sh bug
tcpip sh crash
may help
:-)
(joking)
Gerard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2004 08:17 AM
тАО02-26-2004 08:17 AM
Re: debugger motif error codes?
Unfortunatly I do not think the error code was filled with a reasonable value as it translates to hex FFFF, which just looks like to much of a coincidence. (Somebody in the "know" please correct me if I am wrong!)
Do you have some move information on the circumstances the error occurs in, e.g. is it throwm by your application or the debugger itself etc.
Greetings, Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2004 06:59 PM
тАО02-26-2004 06:59 PM
Re: debugger motif error codes?
Correct.
This is appearently no VMS error code. VMS doesn't have odd fatals.
(For the innocent: for VMS, the last 3 bits deterimine severity: 000 (0) = warning, 001 (1) = success, 010 (2) = error, 011 (3) = Informational, 100 (4) = fatal, rest 'reserved for future use'. So if odd, it's ok, otherwise there's something wrong).
Tym:
I guess it's a unix state, but these won't tell you anything unless you know the source. In this case: the IO-stack of X-Windows...
It might be a conflict between the service you're debugging and decWindows (what actually is an implementation of X_Windows). Try to debug this service using the plain VMS debugger, you'll prevent that problem anyway.
Tell us more, like Martin said. That may shine some light.
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2004 08:48 PM
тАО02-26-2004 08:48 PM
Re: debugger motif error codes?
The text you show isn't that used by the default DECwindows I/O error handler, so I guess Debug must have its own X IO error handler.
Try running DECW$EXAMPLES:ICO to the server. That has a better error handler that can give a more meaningful message.
Martin Kirby
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-27-2004 01:51 AM
тАО02-27-2004 01:51 AM
Re: debugger motif error codes?
(Note that all the following worked FINE last week, when I had Multinet V54 running, instead.)
I can run the debugger fine interactively, but it's not possible to debug the problem that way.
We set up the TCP port command file to invoke our ODBC server, and further modify this command file to define the debug environment, including the necessary SET DISPLAY/CREATE command.
DECW$EXAMPLES:ICO.EXE, as well as another private DecW application run FINE. Due to the query client, MSQUERY, making two connections per request, I have two error files, each showing a slightly different view of the problem. (See attachment for both file extracts.)
I'm willing to apply ECO5, or even upgrade UCX to V5.4, but I'm having trouble locating them in the ITC patch system?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-29-2004 06:21 PM
тАО02-29-2004 06:21 PM
Re: debugger motif error codes?
I would check if there is anything left of Multinet - I think of installed shared images in the first place, but check the process environment of the service as well, there might be references to Multinet routines left (the service will run the login-procedures of the specified user when started).
To locate the ECO (I understand your trouble):
point to http://www5.itrc.hp.com/service/patch/search.do and search for tcpip. you'll find your patch-description at URL:
http://www5.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=VMS731_SYS-V0500&context=openvms:alpha:7.3-1
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2004 04:19 AM
тАО03-01-2004 04:19 AM
Re: debugger motif error codes?
In the log there is:
++++++++
XIO: fatal IO error 65535 on X server "_WSA29:"
after 10607 requests (10605 known processed) with 0 events remaining.
....
%XLIB-F-IOERROR, xlib io error
-SYSTEM-F-CONNECFAIL, connect to network object timed-out or failed
----- end of exception message
++++++++
10605 requests processed means it connected to the display server and did a fair bit of work before it terminated. So it is not a simple case of can't connect or security etc.
However, "CONNECFAIL" isn't the usual message when a server connection is terminated, that is LINKDISCON. Not sure what would cause CONNECFAIL.
Does your DBG$INIT file do anything, such as run your application, that might be interfering with the link? Does EXCEED have a log file that might show why it thinks the connection was closed?
Martin Kirby
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2004 08:52 AM
тАО03-01-2004 08:52 AM
Re: debugger motif error codes?
DEBUG.INI file+does+the+following:
SET LOG SDSK:[xxxxx]debugger.log
SET OUTPUT LOG
SET STEP LINE
set lang C
!SET MODE KEYPAD
!SET MODE SCREEN
set source sdsk:[yyyyy], zz_cmsref:
set image srv
set module mgrmain
... !bunch+of+set+module/set+source+cmds
go
Exceed+trace+file+is+attached.
From+the+client+end, the+steps+are+as+follows:
1. Minimize+all+other+windows+on+the+PC.
2. Ensure+that+Exceed+is+running
3. Start MSQuery
4. Click icon for new query
5. Choose appropriate data source.
6. Debugger window comes up, subwindows, but no focus to that window, nor does any of the debugger displays paint, nor does the prompt come up.
7. After a while, I kill off the MSQuery window by clicking CLOSE in the icon at the bottom of the screen, then agreeing to end the task.
8. Debugger wakes up at that point, and I can EXIT out normally.
I do have Exceed set to give the newly raised window focus, but it doesn't get it.
Running out of ideas-I'm probably gonna call support tomorrow (3/2/04)
thanks for all the help, though.
-Tym
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2004 01:50 PM
тАО03-01-2004 01:50 PM
Re: debugger motif error codes?
did you recompile your application after moving from Multinet to UCX? If yes, did that work
without problems (I seem to remember there are a number of Multinet routines that are not supported with UCX).
Also what do you use as the transport for X? I suppose TCP/IP. If yes, can you test if you get the same problem directly at the console using the local transport?
Greetings, Martin