1748184 Members
3676 Online
108759 Solutions
New Discussion юеВ

Re: T2T timeout

 
SOLVED
Go to solution
Wim Van den Wyngaert
Honored Contributor

T2T timeout

I'm using task-to-task to execute things remotely. Decnet+.

The remote task must however open sys$net within 75 seconds or control returns to the main task. And the task continues (and fails in my case).

Is there a way to change the 75 ?

Wim
Wim
17 REPLIES 17
Ian McKerracher_1
Trusted Contributor

Re: T2T timeout

Wim,

This could be caused by the logical NETSERVER$TIMEOUT on the remote node. This contains a delta time value representing the amount of time that NET$SERVER waits before it reaches timeout. The NET$SERVER image is invoked when a link request is received.

I am not entirely convinced that this is the cause of your problems but it is worth checking.

Hope this helps,

Ian

Volker Halle
Honored Contributor

Re: T2T timeout

Wim,

in DECnet Phase IV there are:

$ mc ncp sho exe char
...
Incoming timer = 45
Outgoing timer = 60
...

The incoming connection must be accepted/rejected within 45 seconds and the outgoing connection accepted/rejected within 60 seconds.

In DECnet Phase V (DECnet/Plus) there are

$ MC NCL SHOW SESSION CONTROL ALL
...
Incoming Timer = 45
Outgoing Timer = 60
...


Please check these values on both of your systems involved in the task-to-task communication and change them, where appropriate.

Volker.

Ian Miller.
Honored Contributor

Re: T2T timeout

this could also be related the the incoming timer characteristic of sesson control

ncl show session control incoming timer

____________________
Purely Personal Opinion
Wim Van den Wyngaert
Honored Contributor

Re: T2T timeout

Volker,

I have the same settings. But I would like to modify them for this task only. Possible via logicals ?

Wim
Wim
Ian Miller.
Honored Contributor

Re: T2T timeout

NETSERVER$TIMEOUT logical is a delta time for how long a idle netserver process waits around for another incoming connection before exiting.
____________________
Purely Personal Opinion
Volker Halle
Honored Contributor

Re: T2T timeout

Wim,

this is an attribute of the session control entity and cannot be specified for individual session control applications.

Why does the remote task take so long to open sys$net ? Maybe you can do the open earlier and then do other initialization tasks later.

Volker.
Wim Van den Wyngaert
Honored Contributor

Re: T2T timeout

Volker,

It is a remote backup procedure. The task mounts the tape and converts sys$net to tape.
However, if the tape needs to be positioned, this can take minutes to complete. I tried to open sys$net shared and to convert/shared but convert didn't work.

Wim
Wim
Volker Halle
Honored Contributor

Re: T2T timeout

Wim,

can't you just do an

$ OPEN/READ/WRITE x SYS$NET
$ MOUNT tape ...
$ CONVERT SYS$NET tape:file
$ CLOSE x

I've tested this with a simple DCL procedure:

SYS$LOGIN:ABC.COM:

$ SHOW LOG SYS$NET
$ OPEN/READ/WRITE x SYS$NET
$ convert sys$net aaa.txt
$ CLOSE x

$ copy x.com 0"user pwd"::"task=abc"

and the aaa.txt file gets created:

$ dir/dat aaa.txt

Directory USERDISK1:[HALLE]

AAA.TXT;1 19-AUG-2005 19:45:07.45

Volker.
Volker Halle
Honored Contributor

Re: T2T timeout

Wim,

it worked ONCE, now it won't work again ?!

%CONV-F-OPENIN, error opening node::"0=HALLE/├Г┬┐├Г┬┐ABC" as input
-RMS-F-DEV, error in device name or inappropriate device type for operation

Sorry,

Volker.