- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: T2T timeout
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2005 02:13 AM
тАО08-19-2005 02:13 AM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2005 03:47 AM
тАО08-19-2005 03:47 AM
Re: T2T timeout
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2005 03:52 AM
тАО08-19-2005 03:52 AM
Re: T2T timeout
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2005 03:54 AM
тАО08-19-2005 03:54 AM
Re: T2T timeout
ncl show session control incoming timer
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2005 03:55 AM
тАО08-19-2005 03:55 AM
Re: T2T timeout
I have the same settings. But I would like to modify them for this task only. Possible via logicals ?
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2005 03:58 AM
тАО08-19-2005 03:58 AM
Re: T2T timeout
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2005 04:02 AM
тАО08-19-2005 04:02 AM
Re: T2T timeout
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2005 05:26 AM
тАО08-19-2005 05:26 AM
Re: T2T timeout
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2005 05:49 AM
тАО08-19-2005 05:49 AM
Re: T2T timeout
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2005 05:57 AM
тАО08-19-2005 05:57 AM
Re: T2T timeout
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.