Name: frenkelvlad Date: July 6, 2004 at 16:53:04 Pacific Subject: Weird Motif problem OS: Mandrakw Linux 9.0 CPU/Ram: 700Mhz/256
Comment:
Hi, I was encountered an interesting problem after Motif installation. First, Motif wouldn't start after installation, I've checked autogen parameters and everything was normal. Ok, after that I've restarted Motif manually by doing @SYS$MANAGER:DECW$STARTUP command and logical DECW$DISPLAY was created. Running after installation @SYS$TEST:DECW$IVP also didn't show any errors. Ok, I logged off from the current console session, and immediately saw a Motif login screen. Looks like system was able to confirm my name/password parameters (cause supplying a wrong ones immediately returns an error) display flick for a second (you can see busy mouse pointer) and immediately returns to login screen. OK, I've restarted the box, and investigated a problem, what I've found is that, that a fresh copy of DECW$sm.log file in SYSTEM$MANAGER was created every time I was tried to login with only one entry inside: "No active license". Reinstallation of Motif didn't help either. But this is weird, cause DW-MOTIF license is registered and showing as enabled, by doing sh lic command, also, I believe, a Motif installation also checks for an active DW-MOTIF license, and didn't return any error. (Note) I do not know, if this one is important, but I've an active TCPIP_Services license, and no DECNET license, but sh dis command is showing an active transport as an DECNET transport. Can somebody help me with this one?
Some add-in, forgot to mention. Manually startup of Motif (@SYS$MANAGER:DECW$STARTUP) creates a display with transport as Local - not DECNET, as I mentioned above, only in this case I've a login display enabled. On an other hand, when I've tried to change a display transport (set dis /transport=TCPIP) to TCPIP and log off, I've a gray screen with mouse pointer on it with missing loging screen, but decw$sm.log file with the same entry was created. Any idea guys?
Hi. I'm running Motif 1.28. Problem is not in the Transport type, I can easily change that, what I believe problem is in "no active license" in dew$sm.log file and that I cannot understand.
Hi. Thanks a lot for a response. Here is a detailed output: show lic *motif/full DW-MOTIF Producer:DEC Units:1100 Version:0.0 Release Date:(none) Termination Date:(none) Availability: H (Alpha Layered Products) Activity:0 MOD_UNITS ALPHA
On sh lic /charge command (I believe you interested in H type licenses): Type H, Units Required: 1100
What I've noticed thought, that products type A (ALpha system) which I only running OpenVMS-Alpha product required 400 units, where I've only 100, but it didn't actually reflect on any layered product installation (nor TCPIP services nor DW-MOTIF) (Note: TCPIP services working without any problem) nor any complaints in system_startup.log file . Again here is a decw$sm.log file entry: No license is active for this software product. mcr command didn;t help much, cause if I run it before I start DECW it simply do not display anything, if after - just stalled.
Again, if I start DW-MOTIF throught @SYS$MANAGER$DECW$STARTUP it creates a process and after log command giving me a login screen, but unfortunately I'm not able to login.
Thanks a lot. If you'll have some time, could you dig some more on that.
Hi. Thanks a lot for a response. Just wanted to provide some answers to you're questions: 1)Console is the only X-windows terminal, and I do not use eXcursion or ReflectionX yet (even thought I've used them before) 2) I've used DecWindows (Motif) before, I simply never installed it and configured it from scratch.
3) It is not a very urgent problem, just wanted to get it fixed, cause Operator Console is not the best interface for operations.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE