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-08-2006 02:44 AM
тАО08-08-2006 02:44 AM
Ex.
New TSTSTG> copy bls_login.com team07::q.q/log
%COPY-E-OPENOUT, error opening TEAM07::Q.Q; as output
-RMS-E-CRE, ACP file create failed
-SYSTEM-F-INVLOGIN, login information invalid at remote node
%COPY-W-NOTCOPIED, $1$DUA21:[BLS]BLS_LOGIN.COM;45 not copie
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2006 02:48 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2006 02:51 AM
тАО08-08-2006 02:51 AM
Re: Help
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2006 02:52 AM
тАО08-08-2006 02:52 AM
Re: Help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2006 03:02 AM
тАО08-08-2006 03:02 AM
Re: Help
Determine a valid account to receive the copy at TEAM07 (mayby your own?)
At TEAM07 issue
UAF> ADD/PROXY TSTSTG::
If you now execute the COPY from your question, BLS_LOGIN.COM will be in SYS$LOGIN for
The remote filespec can include file spec for any other location, and/or filename, just as long as
hth
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2006 03:05 AM
тАО08-08-2006 03:05 AM
Re: Help
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2006 03:29 AM
тАО08-08-2006 03:29 AM
Re: Help
Accounts with DECnet access are added to the system like any other accounts, using the AUTHORIZE utility. One example of all of the procedures that use AUTHORIZE is in SYS$EXAMPLES:ADDUSER.COM.
Remember, you need to allow NETWORK access, and you need AT LEAST the NETMBX and TMPMBX privileges.
You can then use the account for DECnet file accesses, whether ny specifying it explicitly in the file name, or implicitly using the network proxy mechanism.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2006 09:51 AM
тАО08-08-2006 09:51 AM
Re: Help
Could you please use more descriptive titles than "Help"?
In this case the system TEAM07 does not have a default DECnet account for the FAL object. This would have been the choice of the system manager who installed and configured DECnet, and maybe required by site security policies.
If it's acceptable security, you can reconfigure DECnet to add a default FAL account. For phase IV it's @SYS$STARTUP:NETCONFIG, for Phase V it's @SYS$STARTUP:NET$CONFIGURE.
Please read the documentation for configuring DECnet BEFORE starting the procedure, or log a case with your local customer support centre for assistance.
Again, this involves opening holes in your system security, and should NOT be done without reference to security policies, and an understanding of the potential risks.