Remote procedure on DecNet V

[Antoniov.]

I migrated a decnet IV host to decnet V (VMS V7.3-2). In my network there is a old alpha with V6.2 and DecNet IV.
Before migration, on old alpha I could type
$ TYPE NEW::"0=mycmd"
where mycmd was an object recorded in NCP database of NEW alpha.
Hence new alpha has DecNet V reither this command can't work nor simple remote command like $ DIR NEW::*.*
I checked for proxy database. It's fine.
How can I run a remote procedure or remote command on new DecNet V ?
I'm newbie in DecNet OSI :-(

Antonio Vigliotti

[Uwe Zessin]

Does it work if you put a username/password into the ACS? e.g.:
$ directory NEW"username password"::

Any error message?

[Ian Miller.]

You need to define a session control application

@SYS$STARTUP:NET$CONFIGURE ADVANCED

select option for 'Configure application database'
then select option for ADD
and follow the prompts.

The result of this is a new NET$SESSION_STARTUP.NCL

[Bojan Nemec]

Antonio,

I have no DECNet V installed (I prefer to work with the old good phase IV ;). I find a procedure which I wrote some years ago to create a DECNet V object:

CREATE NODE 0 SESSION CONTROL APPLICATION
SET NODE 0 SESSION CONTROL APPLICATION -
ADDRESSES = {NUMBER = } -
,CLIENT = -
,INCOMING ALIAS = TRUE -
,INCOMING PROXY = FALSE -
,OUTGOING ALIAS = FALSE -
,OUTGOING PROXY = FALSE -
,NODE SYNONYM = TRUE -
,IMAGE NAME = -
,USER NAME = "" -
,INCOMING OSI TSEL =

Which is equivalent to old NCP:

NCP> DEFINE OBJECT NUMBER -
FILE -
OUTGOING CONNECT PRIVILEGES -

USER PASSWORD

You put this in SYS$MANAGER:NET$APPLICATION_STARTUP.NCL

Bojan

[Joseph Huber_1]

Apparently You have no TASK object defined. (don't know if that's omitted by net$configure with a cause).

Define it in net$application_local.ncl like that:

CREATE NODE 0 SESSION CONTROL APPLICATION TASK
SET NODE 0 SESSION CONTROL APPLICATION TASK ADDRESSES = {NAME=TASK} -
,CLIENT = -
,INCOMING ALIAS = TRUE -
,INCOMING PROXY = TRUE -
,OUTGOING ALIAS = FALSE -
,OUTGOING PROXY = TRUE -
,NODE SYNONYM = TRUE -
,INCOMING OSI TSEL = -
,USER NAME = "ILLEGAL"

The user name ILLEGAL makes sure only proxy accounts can use it (assuming You have no legal user named ILLEGAL :-).

For others like FAL , lookin NET$APPLICATION_STARTUP.NCL, I wonder what happened when You NET$COMNFIGUREd.
Eventually copy a sample from my location:

http://wwwvms.mppmu.mpg.de/vms$common/sysmgr/net$application_startup.ncl

[Wim Van den Wyngaert]

Before you create objects, check what you have.

mc ncl show ses con app xxx [all]

xxx = TASK for T2T
xxx = FAL for remote file access
xxx = * to see them all

Wim

[Antoniov.]

Wow,
how many answer!

Uwe,
yes, with direct password it works but I don't want supply username and password.

Ian,
executed procedure but it yet doesn't work. I'm not sure about parameter supplied.

Bojan,
I saw in SYS$STARTUP:NET$APPLICATION_STARTUP.NCL
my definition by above Ian's procedure
!* Session Control Application MYDCL added
!* 13-SEP-2005 17:07:32.11 by SYSTEM
CREATE NODE 0 SESSION CONTROL APPLICATION MYDCL
SET NODE 0 SESSION CONTROL APPLICATION MYDCL ADDRESSES = {NAME=MYDCL} -
,CLIENT = -
,INCOMING ALIAS = TRUE -
,INCOMING PROXY = TRUE -
,OUTGOING ALIAS = FALSE -
,OUTGOING PROXY = TRUE -
,NODE SYNONYM = TRUE -
,IMAGE NAME = USR$BIN:MYDCL.COM -
,INCOMING OSI TSEL =
I deletede USERNAME because I want to use proxy.

Joseph,
I addes USERNAME="ILLEGAL"
It seems doesn't work

Wim
MC NCL SHOW SESS CON APPL MYDCL
show me

Node 0 Session Control Application MYDCL
at 2005-09-13-17:23:23.690+02:00Iinf

Identifiers

Name = MYDCL


Thank to allbodies.

Antonio Vigliotti

[Antoniov.]

Because I can't execute remote command,
I wanto to simply my trouble.
At moment I want type
$ DIR NEW::*.*
on old alpha and see dir on new alpha

Antonio Vigliotti

[Ian Miller.]

"$ DIR NEW::*.*
on old alpha and see dir on new alpha"

If the proxies are right on the new alpha then this should work - does it?

[Uwe Zessin]

If it works with explicit username and password, then you can expect the object to be working and there is something wrong with the proxy processing.

Again, may I ask if you got any error message?

- anything from OPCOM?
$ reply/enable=network

- something in the ACCOUNTING or AUDIT logs?