SAS INSTALL

[Clayton_12]

Looking really good . Getting very close to a final solution.

When I apply the SECURITY setting for the DECwindows server SAS will run. What a sight to behold!

However, on reboot the Security settings for TCPIP transport are not retained.
How do I retain them?

Thx
Clayton

[Jan van den Ende]

Clayton,

just like any TCPIP setting:

$ TCPIP SET xxx

does your current setting, and

$ TCPIP CONFIG SET xxx

modifies your configuration, ie, changes the way it will be upon reboot.

hth

Proost.

Have one on me.

jpe

[Volker Halle]

Clayton,

just logout once after you've set the security attributes. This should save your session configuration to disk.

Volker.

[Clayton_12]

Hi Still struglling with making SAS work.
Fun and GAmes. My previous success were actually under the System account.

When I log on as other users the decw$window security settings are not retained.

How do I retain across all USers?

The set display works great as well.
Set display/create/node=XX.XX>XX>XX/trans=tcpip.

How would I be able to automate this to pick up the node the user terminals in from?

THX
Clayton

[Volker Halle]

Clayton,

you don't need to set the display, if you're logged in on the graphic monitor on your local node and want to display your Xapplication on that monitor ($ SHOW DISPLAY already points to your node).

If you've logged in to your node via TELNET from your PC and want to display X-applications on your PC (remember: you must be running a Xserver on your PC), then you can find out the IP address where the TELNET connection comes from with:

$ write sys$output f$getdvi("tt","tt_accpornam")

The security settings are stored in

[.DT.SESSIONS.*]DT.RESOURCES

under the user's default login directory. Don't know, whether there are system-wide defaults for this. Could be SYS.RESOURCES ?

Volker.

[Steven Schweda]

DECWindows security settings should be
retained for each user when he logs out.
There may be a way to spread the joy in a
more automatic way, but I've never had enough
users to care.

There should be a bunch of automatic SET
DISPLAY procedures floating around. The key
is this guy:

f$getdvi( "tt", "tt_accpornam")

For example:

(DECnet. Look for "name::".)
ALP::SYSTEM

(RSH. Look for "Host: name ".)
Host: alp User: SMS

(Telnet. Look for "Host: name ".)
Host: alp Locn: _RTA2:/SMS

For local access, it's empty. Different
TCP/IP products offer similar data, but
possibly in a different format.

Different people attack the resulting
string in different ways, using f$element,
f$locate, f$extract, and so on. It's more
fun to write your own than to steal a good
one from somewhere. Mine works, but it's
probably embarassing. Send me e-mail if you
get desperate.

[Steven Schweda]

Oh, yeah. I forget LAT:

(LAT. Look for "name/".)
ALP/UIC_000001000004

Are there still LAT X terminals?

I'm afraid to investigate
SYS$LIBRARY:DECW$TRANSPORT_ADSP.EXE.

[Volker Halle]

Clayton,

there is a file called:

cde$system_defaults:[config.c]sys.resources

You may be able to define system-wide defaults in that file, but if you really need this, have a look in the DECwindows documentation first.

Volker.

[Clayton_12]

tHX aLOT FOR THE QUICK AND IN DEPTH RESPONSES.

yOU GUYS ARE RIGHT. i PROBABLY DON'T NEED THe settings system wide.
In all likelihood I'll be using command line settings for the SAS routines and commands from DECterms and telenet sessions to maintain existing legacy look and feel. AS pointed out Xwindows on workstaion should resolve any users wishing to try out the graphics interface.

LAT X's AHH! we still use it here for line printers. I'll be looking to switch over to IP printers . One battle at a time:-)


THx
Clayton