I'm working with a client to move a DECnet Phase IV task on an old VAX that is being shutdown to an Alpha running Phase V.

In Phase IV I would create the user, then define/set the object like this;
define object xyz file sys$sysdevice:[abc]xyz.com user abc password z
set object xyz file sys$sysdevice:[abc]xyz.com user abc password z

In Phase V I seem to be missing something.

The target Alpha has the client VAX defined in DECNET_REGISTER as a Phase IV address. The VAX has the Alpha defined in NCP.

From the VAX I do
$ Open/read netchan alpha””::”TASK=xyz”
I get;
%DLC-E-OPENIN, error opening alpha””::”TASK=xyz” as input
-RMS-E-ACC, ACP file access failed
-SYSTEM-F-INVLOGIN, login information invalid at remote node

When that happens I see “Event: Access Control Violation from: Node LOCAL:.alpha Session Control” in OPERATOR.lOG.

In SYS$MANAGER:NET$APPLICATION_STARTUP.NCL there is a line “SET NODE 0 SESSION CONTROL APPLICATION TASK ADDRESSES = {NAME=TASK}” that was put in when Phase V was installed 20 years ago.

I'm not sure if I have to add something to a .NCL file somewhere to get the task to work in Phase V.

Does anyone know if there are any other steps to add a Phase IV task to Phase V?

Peter

> In SYS$MANAGER:NET$APPLICATION_STARTUP.NCL there is a line “SET NODE 0 SESSION CONTROL APPLICATION TASK ADDRESSES = {NAME=TASK}” that was put in when Phase V was installed 20 years ago.

Just modify the SESSION CONTROL APPLICATION TASK by adding a User Name, e.g..

$ mc ncl set sess con app task user name = "abc"

Or add a network proxy like this:

$ MC AUTHORIZE ADD/PROXY LOCAL:.vax abc /DEFAULT

Volker.

On Wednesday, June 21, 2023 at 2:03:08 PM UTC-4, Volker Halle wrote:
>...
> $ mc ncl set sess con app task user name = "abc"
>...

Thanks Volker, I appreciate it.

On 2023-06-21 19:51, Peter Weaver wrote:
> I'm working with a client to move a DECnet Phase IV task on an old VAX that is being shutdown to an Alpha running Phase V.
>
> In Phase IV I would create the user, then define/set the object like this;
> define object xyz file sys$sysdevice:[abc]xyz.com user abc password z
> set object xyz file sys$sysdevice:[abc]xyz.com user abc password z
>
> In Phase V I seem to be missing something.
>
> The target Alpha has the client VAX defined in DECNET_REGISTER as a Phase IV address. The VAX has the Alpha defined in NCP.
>
> From the VAX I do
> $ Open/read netchan alpha””::”TASK=xyz”
> I get;
> %DLC-E-OPENIN, error opening alpha””::”TASK=xyz” as input
> -RMS-E-ACC, ACP file access failed
> -SYSTEM-F-INVLOGIN, login information invalid at remote node
>
> When that happens I see “Event: Access Control Violation from: Node LOCAL:.alpha Session Control” in OPERATOR.lOG.
>
> In SYS$MANAGER:NET$APPLICATION_STARTUP.NCL there is a line “SET NODE 0 SESSION CONTROL APPLICATION TASK ADDRESSES = {NAME=TASK}” that was put in when Phase V was installed 20 years ago.
>
> I'm not sure if I have to add something to a .NCL file somewhere to get the task to work in Phase V.
>
> Does anyone know if there are any other steps to add a Phase IV task to Phase V?

Why changing to Phase V at this point? You can run Phase IV on your
Alpha as well... Seems like this only adds complications.

Johnny

On 2023-06-22, Johnny Billquist <bqt@softjar.se> wrote:
>
> Why changing to Phase V at this point? You can run Phase IV on your
> Alpha as well... Seems like this only adds complications.
>

It sounds to me like Peter is a consultant/contractor to a client that
is already running DECnet Phase V for some reason, so he has no choice
but to come up with a solution for that environment.

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.

On 2023-06-22 14:05, Simon Clubley wrote:
> On 2023-06-22, Johnny Billquist <bqt@softjar.se> wrote:
>>
>> Why changing to Phase V at this point? You can run Phase IV on your
>> Alpha as well... Seems like this only adds complications.
>>
>
> It sounds to me like Peter is a consultant/contractor to a client that
> is already running DECnet Phase V for some reason, so he has no choice
> but to come up with a solution for that environment.

Well. They are also clearly already running Phase IV. But yes, it might
be that the Alphas are on Phase V, and not willing/wanting to change.
But in that case, why didn't they update the VAXen?

Oh well. I've mostly just seen and heard misery when people use Phase V.

Johnny