[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
Moderator: | STAR::VATNE |
|
Created: | Mon Oct 30 1989 |
Last Modified: | Mon Dec 31 1990 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3726 |
Total number of notes: | 19516 |
3557.0. "What is 12DB821C (vs. 02DB821C)?" by AKOV12::NISHINAGA (Joyce Nishinaga) Wed Oct 31 1990 10:54
The attached accounting log shows a final status code of 12DB821C for
the detached process which was running DECW$TERMINAL.EXE. This code
looks suspiciously close to the 02DB821C code mentioned in Note 684.*
but, it appears to be different.
In any event, does anyone have any clue as to what the code 12DB821C
means? The problem we are getting is the user's window disappears,
along with all the work that was being performed on it. In the
attached example, the user is running CHILD.EXE and ALL-IN-1 as
a subprocess to the CHILD process on the window supported by the detached
process running DECW$TERMINAL.EXE.
Nothing is showing up in the log files; the attached accounting records are
our only clues. The second record shows that the ALL-IN-1 subprocess
gets a "%SYSTEM-F-DEVOFFLINE, device is not in configuration or not
available" (%X00000084) error, presumably because the DECterm croaked
with the 12DB821C error. The owner process running CHILD, however,
exits successfully.
We are completely baffled by this, and the problem is sporadic.
Any ideas would be appreciated. I couldn't find anything similar
in this conference, except for Note 684, which really didn't provide
a solution.
Regards,
Joyce
DETACHED Process Termination
----------------------------
Username: NISHINAGA UIC: [GI1RAGT,NISHINAGA]
Account: GI1RAGT Finish time: 30-OCT-1990 08:58:02.97
Process ID: 20209AFD Start time: 30-OCT-1990 08:36:55.92
Owner ID: Elapsed time: 0 00:21:07.05
Terminal name: Processor time: 0 00:00:06.12
Remote node addr: Priority: 4
Remote node name: Privilege <31-00>: 00108000
Remote ID: Privilege <63-32>: 00000000
Queue entry: Final status code: 12DB821C
Queue name:
Job name:
Final status text: <no text>
Page faults: 1780 Direct IO: 52
Page fault reads: 42 Buffered IO: 808
Peak working set: 2013 Volumes mounted: 0
Peak page file: 5233 Images executed: 1
SUBPROCESS Process Termination
------------------------------
Username: NISHINAGA UIC: [GI1RAGT,NISHINAGA]
Account: GI1RAGT Finish time: 30-OCT-1990 08:58:05.78
Process ID: 20208507 Start time: 30-OCT-1990 08:37:18.85
Owner ID: 202088FB Elapsed time: 0 00:20:46.93
Terminal name: Processor time: 0 00:00:06.62
Remote node addr: Priority: 4
Remote node name: Privilege <31-00>: 00108000
Remote ID: Privilege <63-32>: 00000000
Queue entry: Final status code: 10000084
Queue name:
Job name:
Final status text: %SYSTEM-F-DEVOFFLINE, device is not in configuration or not
Page faults: 3400 Direct IO: 208
Page fault reads: 35 Buffered IO: 263
Peak working set: 3759 Volumes mounted: 0
Peak page file: 18982 Images executed: 3
DETACHED Process Termination
----------------------------
Username: NISHINAGA UIC: [GI1RAGT,NISHINAGA]
Account: GI1RAGT Finish time: 30-OCT-1990 08:58:06.28
Process ID: 202088FB Start time: 30-OCT-1990 08:36:52.10
Owner ID: Elapsed time: 0 00:21:14.18
Terminal name: Processor time: 0 00:00:01.51
Remote node addr: Priority: 4
Remote node name: Privilege <31-00>: 00108000
Remote ID: Privilege <63-32>: 00000000
Queue entry: Final status code: 10000001
Queue name:
Job name:
Final status text: %SYSTEM-S-NORMAL, normal successful completion
Page faults: 1051 Direct IO: 46
Page fault reads: 45 Buffered IO: 95
Peak working set: 458 Volumes mounted: 0
Peak page file: 3734 Images executed: 8
T.R | Title | User | Personal Name | Date | Lines |
---|
3557.1 | same code | VINO::MCARLETON | Reality; what a concept! | Wed Oct 31 1990 11:40 | 8 |
|
The difference between the code 02DB821C and 12DB821C is just one of
the condition code bits. The meaning of the signal is the same.
You may want to look in the DECTERM notes file on HANNAH:: for a
solution to this problem.
MJC
|
3557.2 | | QUARK::LIONEL | Free advice is worth every cent | Wed Oct 31 1990 13:13 | 3 |
| The bit is STS$V_INHIB_MSG, which tells $PUTMSG not to display it.
Steve
|
3557.3 | | DECWIN::MESSENGER | Bob Messenger | Thu Nov 01 1990 11:08 | 7 |
| Re:.0
Error 12db821c is an XLIB I/O error, and it means that the server dropped
the connection. This could be a network problem. Was there really nothing
in the server log file?
-- Bob
|
3557.4 | Looks like a network problem | AKOV12::NISHINAGA | Joyce Nishinaga | Fri Nov 02 1990 09:43 | 17 |
| Thank you all for your pointers. I did suspect a hardware/network problem,
but we had no hard evidence until yesterday when the "Device offline" error
showed up in several other places, which definitely pointed to a network
problem. It was also discovered that a DELNI was swapped last week by
Field Service, so there's probably a connection. It is being investigated.
Is the appropriate server log the one pointed to by DECW$DECTERM_OUTPUT?
We weren't defining this logical, so the only log I could locate was
the DECW$SM.LOG file. I have just defined the DECW$DECTERM_OUTPUT and
will watch.
Thanks again. I expect a network fix will make our disappearing window
problem go away, too (you'll hear more from us on this if it doesn't!).
Joyce
|
3557.5 | | DECWIN::MESSENGER | Bob Messenger | Fri Nov 02 1990 10:17 | 3 |
| The server log file is SYS$MANAGER:DECW$SERVER_0_ERROR.LOG.
-- Bob
|