- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Remote procedure on DecNet V
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
тАО09-13-2005 02:29 AM
тАО09-13-2005 02:29 AM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2005 02:40 AM
тАО09-13-2005 02:40 AM
Re: Remote procedure on DecNet V
$ directory NEW"username password"::
Any error message?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2005 02:43 AM
тАО09-13-2005 02:43 AM
Re: Remote procedure on DecNet V
@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
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2005 02:46 AM
тАО09-13-2005 02:46 AM
Re: Remote procedure on DecNet V
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
FILE
OUTGOING CONNECT PRIVILEGES -
USER
You put this in SYS$MANAGER:NET$APPLICATION_STARTUP.NCL
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2005 02:49 AM
тАО09-13-2005 02:49 AM
Re: Remote procedure on DecNet V
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2005 03:06 AM
тАО09-13-2005 03:06 AM
Re: Remote procedure on DecNet V
mc ncl show ses con app xxx [all]
xxx = TASK for T2T
xxx = FAL for remote file access
xxx = * to see them all
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2005 03:24 AM
тАО09-13-2005 03:24 AM
Re: Remote procedure on DecNet V
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2005 03:35 AM
тАО09-13-2005 03:35 AM
Re: Remote procedure on DecNet V
I wanto to simply my trouble.
At moment I want type
$ DIR NEW::*.*
on old alpha and see dir on new alpha
Antonio Vigliotti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2005 03:38 AM
тАО09-13-2005 03:38 AM
Re: Remote procedure on DecNet V
on old alpha and see dir on new alpha"
If the proxies are right on the new alpha then this should work - does it?
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2005 03:40 AM
тАО09-13-2005 03:40 AM
Re: Remote procedure on DecNet V
Again, may I ask if you got any error message?
- anything from OPCOM?
$ reply/enable=network
- something in the ACCOUNTING or AUDIT logs?