topic Re: Dec term problem in Operating System - OpenVMS

Dec term problem

berlioz — Wed, 04 Aug 2004 04:23:04 GMT

Hello

i'm currently using Dec Windows interface under OpenVMS 7.3-2.

My problem is :
When i invoke script "@orauser.com" in login.com file for user oracle, i can't opened any dec term windows

What's the problem ? there's no "set term" function in that script... what kind of function cause problem ?

(sorry for my poor english)

thanks in advance for all
philippe

Re: Dec term problem

Antoniov. — Wed, 04 Aug 2004 04:51:38 GMT

Hi Philippe,
when you invoce script @orauser?
LOGIN.COM is executed after user is logged into system, so I guess DecWindows is already active.
If script is executed by batch or detached process, I guess you can't open a new windows.

Antonio Vigliotti

Re: Dec term problem

labadie_1 — Wed, 04 Aug 2004 04:53:47 GMT

Can you post this orauser.com file ?

What does it do ?

Does it exit, or wait for something ?

Try a
$ ! 'f$ver(1)
$ set watch file/class=major
before calling orauser

$ set watch file/class=none
to suppress this verbosity

:-)

Re: Dec term problem

Martin Vorlaender — Wed, 04 Aug 2004 05:07:25 GMT

Antoniov,

ORAUSER.COM sets up the environment to work with Oracle. Normally, it just defines a few logicals and symbols.

Philippe,

what do you get when you issue
$ SHOW DISPLAY
and
$ CREATE /TERMINAL

cu,
Martin

Re: Dec term problem

berlioz — Wed, 04 Aug 2004 05:09:36 GMT

orauser.com script is used to set up oracle environnement and is necessary for such an user.

Is there an other way to invoke that script in some login file (login.com or decw$login.com) ?
somethink like : run/detach/output='display' orauser.com ?

what can i do ?

Re: Dec term problem

berlioz — Wed, 04 Aug 2004 05:20:20 GMT

martin,

show display normally print display characteristics (device,node,transport) and create/terminal opened a new dec term windows

Re: Dec term problem

Wim Van den Wyngaert — Wed, 04 Aug 2004 05:28:22 GMT

Try putting "set noon" before the "@".

Wim

Re: Dec term problem

berlioz — Wed, 04 Aug 2004 05:39:46 GMT

wim

sorry but... nothing changes

A question :
what command is invoke when clinking on decterm icon from decw menu task ? what script is invoking ?

Re: Dec term problem

berlioz — Wed, 04 Aug 2004 06:47:08 GMT

labadie,

when trying your solution, logging is impossible.

i've no decw interface... only a gray backgroud... what could i do ?

Re: Dec term problem

labadie_1 — Wed, 04 Aug 2004 07:14:33 GMT

it was not intented to allow logging, but only to see what happens, the last command, and may be understand why it fails.

Re: Dec term problem

Martin Vorlaender — Wed, 04 Aug 2004 07:32:41 GMT

>>>
I've no decw interface... only a gray backgroud... what could i do ?
<<<

Log in by some other means (e.g. SET HOST or TELNET), repair the login file, and issue

@SYS$MANAGER:DECW$STARTUP RESTART

Re: the commands I suggested

I know what they do. What I wanted to know is what their output is when you enter them. If you can't (because you don't have a DECterm), log in by some other means, and enter

$ SET DISPLAY/TRANSPORT=LOCAL
$ CREATE /TERMINAL

cu,
Martin

Re: Dec term problem

berlioz — Wed, 04 Aug 2004 08:04:42 GMT

Sorry martin...

show display : device WSA7:[super], node 0, transport local, server 0, node 0

create/terminal just opened a new decterm

Precision : i'm using the new interface CDE

Re: Dec term problem

Wim Van den Wyngaert — Wed, 04 Aug 2004 09:48:56 GMT

bp,

The command executed when you click the decterm icon is something like
$ create/term/detach with some options.

If you go into the subdirectory dt you find a file "errorlog." created by cde. Anything in it ? (or errorlog.old)

If not, rename dt.dir to tdold.dir and see if it is cde setting related (undo rename afterwards).

How about your quotas ? Since you only have the problem when defining extra logicals and symbols, increase e.g. jtquota.

Wim

Re: Dec term problem

John Gillings — Wed, 04 Aug 2004 17:26:52 GMT

philippe,

It sounds to me like you're executing orauser.com unconditionally in your LOGIN.COM. I suspect you should only execute it for interactive logins. It's extremely unlikely that it needs to be executed for the process running your session & window managers.

Try modifying your LOGIN.COM to have multiple branches for different mode processes and place orauser.com only in the INTERACTIVE branch:

template LOGIN.COM

$! Stuff for all modes goes here
$
$ GOTO DO_'F$MODE()
$! shouldn't get here
$ EXIT
$
$ DO_NETWORK:
$! stuff for network jobs
$ EXIT
$
$ DO_BATCH:
$! stuff got batch jobs
$ EXIT
$
$ DO_OTHER:
$! stuff for other jobs
$ EXIT
$
$ DO_INTERACTIVE:
$! stuff for interactive jobs
$ EXIT

Re: Dec term problem

Martin Vorlaender — Thu, 05 Aug 2004 01:41:11 GMT

John's reply reminded me of something:
For some time now, we have the following snippet of code in all our SYLOGIN files:

$ mode = f$mode()
$ tt_devname = f$trnlnm("TT")
$ session_mgr_login = (mode .eqs. "INTERACTIVE") .and. -
(f$locate("WSA",tt_devname) .ne. f$len(tt_devname))
$ session_detached_process = (mode .eqs. "INTERACTIVE") .and. -
(f$locate("MBA",tt_devname) .ne. f$len(tt_devname))
$!
$ if (mode .eqs. "INTERACTIVE") .and. .not. -
(session_mgr_login .or. session_detached_process)
$ then
$ ! ...REAL interactive stuff, e.g.
$ SET TERMINAL /INQUIRE /INSERT
$ endif

HTH,
Martin

Re: Dec term problem

Wim Van den Wyngaert — Thu, 05 Aug 2004 02:01:49 GMT

Martin,

We find our real interactive processes with
$ if f$getdvi("TT","TRM") .and. f$mode() .eqs. "INTERACTIVE"
$ then
$! real interactive
$ endif

Is your version better ?

Wim

Re: Dec term problem

Bojan Nemec — Thu, 05 Aug 2004 02:26:46 GMT

John,

You are rigth that some commands must be executed only for interactive (or some other) mode. But orauser.com defines the logical names and symbols needed to interact with Oracle database and you need to interact with the database in all modes. So I think that must be executed unconditionally.

Philippe,

I sugest you that you try to see which symbols and logical names are different after executing the orauser.com. You can do that with a set of commands like this:

$ DEFINE SYS$OUTPUT BEFORE.TXT
$ SHOW SYMBOL/GLOBAL/ALL
$ SHOW LOGICAL
$ DEASSIGN SYS$OUTPUT
$ @ORAUSER.COM
$ DEFINE SYS$OUTPUT AFTER.TXT
$ SHOW SYMBOL/GLOBAL/ALL
$ SHOW LOGICAL
$ DEASSIGN SYS$OUTPUT
$ DIFFERENCES BEFORE.TXT AFTER.TXT

Now you can see which symmbols and logicals are defined or changed.

Bojan

Re: Dec term problem

Martin Vorlaender — Thu, 05 Aug 2004 03:11:25 GMT

Wim,

I think I got the code from some DECwindows cookbook (which explains the restriction to WS and MB devices).

I didn't know about the TRM item (as I always look at $GETDVI straight ahead ;-)

It seems that your code is more general. Thanks for the pointer.

cu,
Martin

Re: Dec term problem

Martin Kirby — Thu, 05 Aug 2004 04:03:12 GMT

We have noticed a bug in the New Desktop login that if the login.com exits the login can fail and the login box not be restarted.

If that is what you are seeing you should see the errors from running the login.com in your DECW$SM.LOG file. If you have no access after the login then to access the file, reboot, login with the /NOCOMM qualifier, and look at DECW$SM.LOG;-1.

You may want to add a SET VERIFY to the login.com

The two cases we have had reported of problems were:

1. Where the LOGIN.COM exitted with a severe error state.
2. Where the LOGIN.COM included a SET DISPLAY command.

Another thing to try is to select on the login box to login as a DECwindows session rather than a New Desktop session.

If I am misunderstanding your problem and the issue is that you have been able to login and obtain a front panel but can't start a DECterm then start the Application Manager and from the New Desktop Tools start Watch Errors. Then try and start a DECterm and see if any errors are reported.

Martin Kirby
Sometims DECwindows maintainer

Re: Dec term problem

Wim Van den Wyngaert — Thu, 05 Aug 2004 04:16:40 GMT

Martin,

This is a feature, not a bug. And create/term worked.

Wim