TYPE NODE"user pass"::"TASK=dcl"

[Mario Abruzzi]

What are all of the DECnet prerequisites required to use the TYPE node"user pass"::"TASK=dcl" construct?

I receive the following error when I try the command:
$ type NODEA"username pass"::"task=test"
%TYPE-W-OPENIN, error opening NODEA"username password"::"task=test" as input
-RMS-E-ACC, ACP file access failed
-SYSTEM-F-LINKEXIT, network partner exited

[Steven Schweda]

I get that response when the remote task
exits prematurely (such as because of an
error). For example:

alp $ type task_ok.com
$ open /read /write sysnet sys$net
$ write sysnet f$trnlnm( "sys$net")
$ close sysnet

(I have a DECnet proxy, hence no need for
"user pass".)

alp $ type alp::"task=task_ok"
ALP::"0=SMS/ÿÿTASK_OK"

alp $ type task_e2.com
$ exit
$ open /read /write sysnet sys$net
$ write sysnet f$trnlnm( "sys$net")
$ close sysnet

alp $ type alp::"task=task_e2"
%TYPE-W-OPENIN, error opening ALP::"task=task_e2" as input
-RMS-E-ACC, ACP file access failed
-SYSTEM-F-LINKEXIT, network partner exited

In this case, the behavior appears to depend
on timing, or something, as another example
with an actual error ("$ show junk") failed
once this way, and then started working
better. (Perhaps I need slower hardware.)

You might look for clues in
SYS$LOGIN:NET$SERVER.LOG on the remote
system.

Have you tried a simple task (like mine,
above)?

[Andy Bustamante]

Another option is to use sysman. If you're not in a cluster you'll need to start SMISERVER

$ @SYS$SYSTEM:STARTUP SMISERVER

After this is done, generally in your startup you can manager another node.

$ mc sysman
$ set envi/node=NODE/user=USERID
Remote Password:
SYSMAN> do show systems

Andy

[Wim Van den Wyngaert]

SYSMAN has the disadvantage of not doing a login to the user environment. It justs creates a process with the right uic.

I use T2T in DCL since years and still from time to time (1 in 10000 ?) I get a client and server that got disconnected.

Stop your script with stop/id=0 or otherwise the process and it's context are reused for other T2T jobs.

You get about 75 seconds to open sys$net. Otherwise client and server get disconnected (but continue).

Wim

[Ian Miller.]

look at the log file in the user login directory.
LOGIN.COM or SYLOGIN can do things that cause this - ensure they check for network mode and act appropriately.

[Mike Reznak]

Hi,

I've tried it, have recieved the same message, but on the remote node in sys$login dir I've found in NETSERVER.LOG, that the command had been executed and output written in it. (I used only dir command in remote procedure). So the problem may reside in TASK object definition in NCP/NCL. I take a look at it.

Mike

[Karl Rohwedder]

Be sure, that your remote procedure contains something along the lines:

$ Open/Read/Write/Share=Write/Error=Network$10 Netlun Sys$Net
$ Define/Nolog Sys$Output Netlun:
$ 'your command here'

[Mike Reznak]

I've found this.

http://h71000.www7.hp.com/wizard/wiz_0159.html

But there is no hint for TYPE command. OPEN is used instead.

M

[Mike Reznak]

Karl hits the nail on its head. ;o)

And dont't forget CLOSE command

This works all right.

$ Open/Read/Write/Share=Write/Error=Network$10 Netlun Sys$Net
$ Define/Nolog Sys$Output Netlun:
$ dir
$ close netlun

Mike

[Allan Bowman]

There is a restriction on the length of the filename parameter when using remote task execution. Make sure the DCL file is in the default login directory and the filename is less than 9 characters (plus .COM - I think that's the right number).

Allan

[Steven Schweda]

> There is a restriction on the length of the
> filename [...]

True, but the failure symptom is different
(and more local). Same data, different names:

alp $ type alp::"task=task_long_name16"
ALP::"0=SMS/ÿÿTASK_LONG_NAME16"

alp $ type alp::"task=task_long_name_17"
%TYPE-W-OPENIN, error opening ALP::"task=task_long_name_17" as input
-RMS-F-DEV, error in device name or inappropriate device type for operation

Further conjecture with no new info may be
wasted effort.

[Jan van den Ende]

Allen wrote

Make sure the DCL file is in the default login directory and the filename is less than 9 characters


There is an elegant way around this (which may be preferable even when not needed for the above reasons):

DEFINE a logical name (max 9 chars) to point to the DCL file.

This is especially desirable if several users need the remote task, because defining ONE (system, cluster, group) logical to ONE file accessable to all intended users will do the job, in a maintainable manner.

hth

Proost.

Have one on me.

jpe

[Jan van den Ende]

Mario,

from your Forum Profile:


I have assigned points to 34 of 103 responses to my questions.

Some of those are quite old.

Maybe you can find some time to do some assigning?

http://forums1.itrc.hp.com/service/forums/helptips.do?#33

Mind, I do NOT say you necessarily need to give lots of points. It is fully up to _YOU_ to decide how many. If you consider an answer is not deserving any points, you can also assign 0 ( = zero ) points, and then that answer will no longer be counted as unassigned.
Consider, that every poster took at least the trouble of posting for you!

To easily find your streams with unassigned points, click your own name somewhere.
This will bring up your profile.
Near the bottom of that page, under the caption â My Question(s)â you will find â questions or topics with unassigned points â Clicking that will give all, and only, your questions that still have unassigned postings.

Thanks on behalf of your Forum colleagues.

PS. â nothing personal in this. I try to post it to everyone with this kind of assignment ratio in this forum. If you have received a posting like this before â please do not take offence â none is intended!

Proost.

Have one on me.

jpe

[Robert Gezelter]

Mario,

Also watch the contents of your LOGIN.COM file. I have seen a wide range of possible errors generated when the LOGIN.COM files do erroneous things.

A first test is can you do a DIRECTORY remotely.

- Bob Gezelter, http://www.rlgsc.com