topic Re: PAK for TELNET access? in Operating System - OpenVMS

PAK for TELNET access?

Timothy J Stegner — Wed, 14 Feb 2007 14:49:06 GMT

I've upgraded an ALPHA (DS10L) system to VMS V8.2, and now I'm unable to TELNET into the system. When I try, I'm getting a LICENSE error indicating the software is not licensed. Oddly, FTP works OK.

Can anyone tell me which PAK is required to get TELNET to work correctly?

thanks.

Re: PAK for TELNET access?

Andy Bustamante — Wed, 14 Feb 2007 15:02:16 GMT

The PAK for telnet is the same as FTP, you need a UCX or some NAS licenses. If FTP is working, you probably need a user license for login.

Please post the results of

$show license

Is this system in a cluster? Are you running under the OpenVMS Hobbyist program? Check for an expired user license.

Andy

Re: PAK for TELNET access?

Steven Schweda — Wed, 14 Feb 2007 15:03:56 GMT

It depends.

You could have a bad VMS user license, which
would stop (most) interactive logins,
including TELNET, or you could have a bad UCX
license -- you are using TCPIP, right? --
which could take several forms.

SHOW LICENSE might offer a clue or two.

If you changed the node name, that could mess
with a PAK which has the NO_SHARE option.

Re: PAK for TELNET access?

Hoff — Wed, 14 Feb 2007 15:18:44 GMT

This could be the IP license, or any of various other licenses related to an interactive login. There's a logical name described below that will allow you -- from the console or from some session you can get logged in -- to see what license is triggering the error.

regarding the following... I'll fix the stale LURT URL reference for the next edition of the OpenVMS FAQ. The current URL dejour for the LURT and licensing info is http://licensing.hp.com/swl/view.slm?page=index
And I'll add the OpenVMS I64 OE license PAKs to the list. The FAQ home is over at http://www.HoffmanLabs.com/vmsfaq/

...
5.39 Resolving License PAK Problems?

The PAK release date, the PAK termination date, and the PAK version are the usual culprits when a license product authorization key (PAK) check failure occurs.

The PAK termination date is the date when the license PAK will expire.

The PAK release date is the date of the most recent release date of the software package that will be permitted by the particular license PAK. (The release date check is analogous to a product version check.) The PAK version indicates the most recent product version that is permitted by the license.

Having multiple license PAKs registered (and active) can also cause problems if an expired PAK gets loaded. You will want to DISABLE license PAKs you do not wish to have loaded.

Other problems include a failure to register each PAK in all license databases throughout a multiple-system-disk cluster, with a consistent set of /INCLUDE lists specified across each of the duplicated PAKs.

Additionally, you could have an invalid LMF$LICENSE logical name defined. (If no LMF$LICENSE logical name is defined, the standard license database named SYS$SYSTEM:LMF$LICENSE.LDB will be used.)

You can display license failures by defining the following logical name:

$ DEFINE/SYS/EXEC LMF$DISPLAY_OPCOM_MESSAGE TRUE

Enable your terminal as a license operator (REPLY/ENABLE=LICENSE), define the LMF$DISPLAY_OPCOM_MESSAGE logical name, and then try the failing operation again. You should see one or more OPCOM messages displayed.

If you have the LMF$DISPLAY_OPCOM_MESSAGE logical name defined, you can (will?) see spurious license check failures-various products will check for multiple licenses, and a few products will check for PAKs that either have not yet been or will not be issued. Once you figure out which license has failed, you will want to deassign this logical name.

Note

That there are no license check failures does not indicate that the particular product or operation or use is permissible per applicable licensing agreements. Please consult the applicable agreement(s) for licensing-related information and requirements.

To register a license PAK on a DECwindows system when DECwindows cannot start (because of an expired license or other licensing problem), follow the steps outlined in section Section 5.6 up through the use of the AUTHORIZE command. In place of the AUTHORIZE command, use the console to register the license PAKs. Also see Section 12.4 for licensing and troubleshooting information.

For information on licensing and on the numbers of license units required for various products and various platforms, the License Unit Requirements Table (LURT) is available at:

o http://www.compaq.com/products/software/info/
...
--
...
Some of the more common license PAKs:

DECnet Phase IV: DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*
DECnet-Plus: DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*
TCP/IP Services: UCX, or NET-APP-SUP*
OpenVMS Alpha: OPENVMS-ALPHA and OPENVMS-ALPHA-USER
OpenVMS VAX: VAX-VMS
OpenVMS Galaxy: OPENVMS-GALAXY
Cluster (Alpha): VMSCLUSTER, NET-APP-SUP*
Cluster (VAX): VAXCLUSTER, NET-APP-SUP*
...

Re: PAK for TELNET access?

Timothy J Stegner — Wed, 14 Feb 2007 15:39:51 GMT

Thanks for responses.

The system is standalone. I believe I have the licenses set up similar to my other systems. I can log in ok from the console, to a non-system account, but not from another machine nor via a PC access.

As I am using UCX/TCPIP Svs for HP, I thought such access falls under the base license?

SHOW LICENSE Results (apologies for the formatting)

Active licenses on node VMSQA:

------- Product ID -------- ---- Rating ----- -- Version --
Product Producer Units Avail Activ Version Release Termination
AV-DVNETEND DEC 0 0 100 0.0 16-DEC-1993 (none)
C DEC 1100 H 0 0.0 (none) (none)
NET-APP-SUP-250 DEC 2150 H 0 0.0 (none) (none)
OPENVMS-ALPHA-USER DEC 1700 0 100 0.0 (none) (none)
VMS-USER DEC 200 0 100 0.0 (none) (none)

thanks.

Re: PAK for TELNET access?

Hoff — Wed, 14 Feb 2007 16:06:03 GMT

I don't see the base license.

OPENVMS-ALPHA.

You do need that, in addition to the user license you presently have.

TCP/IP Services is not part of the base license on VAX or Alpha -- that's an OpenVMS I64 thing -- and AFAIK never has been. It's always been either a separate product purchase, or part of a licensing package like NAS. NET-APP-SUP includes IP capabilities; check the NAS 250 SPD for full details: http://h18000.www1.hp.com/info/spd/

These don't look like the licenses I'd expect to find on an AlphaServer DS10L, either. AV-DVNETEND? I have no idea what that one is, and have never seen it before. (I know what DVNETEND is; that's DECnet. But AV-DVNETEND is entirely unfamiliar. Apparently ancient, too?)

Re: PAK for TELNET access?

Martin Hughes — Wed, 14 Feb 2007 18:20:17 GMT

It is likely that you have a base license registered, but for some reason it will not load. Can you post the results for;

$ LICE LIST/FUL OPENVMS-ALPHA

Re: PAK for TELNET access?

Timothy J Stegner — Thu, 15 Feb 2007 13:13:57 GMT

It does appear I never loaded the OPENVMS-ALPHA PAK for the node. I'll try that next.

thanks for the help, all.

Re: PAK for TELNET access?

Timothy J Stegner — Thu, 15 Feb 2007 14:52:31 GMT

The suggestions that the base license wasn't loaded were correct. I checked my list of licenses, and noted the base license wasn't included. Upon loading this license PAK, I now enjoy telnet and non-console access, and can proceed with what I'm REALLY trying to test.

thanks, all.