<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Help in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839405#M78232</link>
    <description>oh eh, sorry, I forgot:&lt;BR /&gt;&lt;BR /&gt;&lt;USERNAEM_AT_TEAM07&gt; should of course be allowed NETWORK login in SYSUAF.&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe&lt;/USERNAEM_AT_TEAM07&gt;</description>
    <pubDate>Tue, 08 Aug 2006 10:05:01 GMT</pubDate>
    <dc:creator>Jan van den Ende</dc:creator>
    <dc:date>2006-08-08T10:05:01Z</dc:date>
    <item>
      <title>Help</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839400#M78227</link>
      <description>How do you set up a DECnet username and password for a system. ?&lt;BR /&gt;&lt;BR /&gt;Ex. &lt;BR /&gt;   New TSTSTG&amp;gt; copy bls_login.com team07::q.q/log&lt;BR /&gt;&lt;BR /&gt;%COPY-E-OPENOUT, error opening TEAM07::Q.Q; as output&lt;BR /&gt;&lt;BR /&gt;-RMS-E-CRE, ACP file create failed&lt;BR /&gt;&lt;BR /&gt;-SYSTEM-F-INVLOGIN, login information invalid at remote node&lt;BR /&gt;&lt;BR /&gt;%COPY-W-NOTCOPIED, $1$DUA21:[BLS]BLS_LOGIN.COM;45 not copie&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Aug 2006 09:44:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839400#M78227</guid>
      <dc:creator>vmsserbo</dc:creator>
      <dc:date>2006-08-08T09:44:06Z</dc:date>
    </item>
    <item>
      <title>Re: Help</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839401#M78228</link>
      <description>You can put a valid username and password in the command:&lt;BR /&gt;&lt;BR /&gt;copy bls_login.com team07"username password"::q.q/log&lt;BR /&gt;&lt;BR /&gt;There are other ways to get by having to specify the username and password, like using DECnet proxies.</description>
      <pubDate>Tue, 08 Aug 2006 09:48:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839401#M78228</guid>
      <dc:creator>Eric Dittman</dc:creator>
      <dc:date>2006-08-08T09:48:00Z</dc:date>
    </item>
    <item>
      <title>Re: Help</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839402#M78229</link>
      <description>If security is not an issue you can even use a user without password. But limit access to "network" in authorize (optional since security is not an issue).&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 08 Aug 2006 09:51:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839402#M78229</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2006-08-08T09:51:21Z</dc:date>
    </item>
    <item>
      <title>Re: Help</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839403#M78230</link>
      <description>How can I set this up usinf decnet? &lt;BR /&gt;</description>
      <pubDate>Tue, 08 Aug 2006 09:52:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839403#M78230</guid>
      <dc:creator>vmsserbo</dc:creator>
      <dc:date>2006-08-08T09:52:31Z</dc:date>
    </item>
    <item>
      <title>Re: Help</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839404#M78231</link>
      <description>Miles,&lt;BR /&gt;&lt;BR /&gt;Determine a valid account to receive the copy at TEAM07 (mayby your own?)&lt;BR /&gt;&lt;BR /&gt;At TEAM07 issue &lt;BR /&gt;UAF&amp;gt; ADD/PROXY TSTSTG::&lt;USERNAME_AT_TSTSTG&gt; &lt;USERNAME_AT_TEAM07&gt;/default&lt;BR /&gt;&lt;BR /&gt;If you now execute the COPY from your question, BLS_LOGIN.COM will be in SYS$LOGIN for &lt;USERNAEM_AT_TEAM07&gt;, and renamed to Q.Q&lt;BR /&gt;&lt;BR /&gt;The remote filespec can include file spec for any other location, and/or filename, just as long as &lt;USERNAEM_AT_TEAM07&gt; has write permission.&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe&lt;/USERNAEM_AT_TEAM07&gt;&lt;/USERNAEM_AT_TEAM07&gt;&lt;/USERNAME_AT_TEAM07&gt;&lt;/USERNAME_AT_TSTSTG&gt;</description>
      <pubDate>Tue, 08 Aug 2006 10:02:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839404#M78231</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2006-08-08T10:02:32Z</dc:date>
    </item>
    <item>
      <title>Re: Help</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839405#M78232</link>
      <description>oh eh, sorry, I forgot:&lt;BR /&gt;&lt;BR /&gt;&lt;USERNAEM_AT_TEAM07&gt; should of course be allowed NETWORK login in SYSUAF.&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe&lt;/USERNAEM_AT_TEAM07&gt;</description>
      <pubDate>Tue, 08 Aug 2006 10:05:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839405#M78232</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2006-08-08T10:05:01Z</dc:date>
    </item>
    <item>
      <title>Re: Help</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839406#M78233</link>
      <description>Miles,&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;Remember, you need to allow NETWORK access, and you need AT LEAST the NETMBX and TMPMBX privileges.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Tue, 08 Aug 2006 10:29:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839406#M78233</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2006-08-08T10:29:46Z</dc:date>
    </item>
    <item>
      <title>Re: Help</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839407#M78234</link>
      <description>Miles,&lt;BR /&gt;&lt;BR /&gt;  Could you please use more descriptive titles than "Help"? &lt;BR /&gt;&lt;BR /&gt;  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.&lt;BR /&gt;&lt;BR /&gt;  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.&lt;BR /&gt;&lt;BR /&gt;  Please read the documentation for configuring DECnet BEFORE starting the procedure, or log a case with your local customer support centre for assistance.&lt;BR /&gt;&lt;BR /&gt;  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.</description>
      <pubDate>Tue, 08 Aug 2006 16:51:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help/m-p/3839407#M78234</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2006-08-08T16:51:39Z</dc:date>
    </item>
  </channel>
</rss>

