Conference iosg::all-in-1_v30

    Mike,
    
    Can you post some other bits of the license like its name and type.
    It sounds as if we've had a lot of these sorts of problems internally
    in DEC already but I can't check VTX because it keeps insisting
    i'm not a U.S Employee (Oops must be TFSO in action)
    
    Until an expert stops by make sure that you've unregistered and
    unloaded any old ALL-IN-1 licenses and that you've registered and
    loaded this one.
    
    Not that I know anything about LMF but I don't see how a product could
    have been released in 1993 when it's only 1992!
    
    Regards,
    
    Andrew.D.Wicks

Andrew,

Yeah, the PAK has a Product Release Date of 18-may-1993.  I tried to change this
to 18-may-1992, but then it will not load.

I did remove the old PAK.  I did this because I got the same message when I 
tried to do the upgrade.  This current PAK was taken from VTX.  It shows up as 
the only PAK for ALLIN1 on the system.  Weird, huh?

	Issuer:	digital-im&t
	Name:	ALLIN1
	Producer:	DEC
	Product Release Date:	18-may-1993
	Availability Table Code: F
	Options: mod_units
	
And of course the authorization number and checksum.

Thanks for your response.  Will appreciate any other ideas.

Mike Alley

    Mike,
    
    Strange isn't the word for this. How about setting the system time
    on your VAX to 18-may-1993 and trying the install again?
    
    Hopefully one of the LMF experts in Reading (graham or paul) is in this
    week and can explain this.
    
    P.S On all the systems I can get to our license issuer is listed as
        DEC with no release date but I suspect these are old FT licenses
        
    
    Regards,
    
    Andrew.D.Wicks
        

    Hi &drew,

    Curiously, the PAK for TGWW's sandbox has a /DATE=16-APR-1993 and the
    PAK on our former-F/T-now-production cluster has a /DATE=21-FEB-1993,
    with both PAK's originating where Mike's came from ...

	Ron

    Yes it's strange that licences do have a release date in the future,
    our current DOCUMENT one does.
    
    Anyway, try $ license list/history ALLIN1
    
    This should show you a screen of information. Try next-screen several
    times to see how many versions of ALLIN1 licence are loaded.
    
    
    There should only be one with a status of Active, the rest (if any)
    should be Disabled or Extinct.
    
    If you have multile licences active, use $ license disable
    /AUTHORIZATION=whatever the one is you want to turn off. If you do this
    then $ license unload allin1 and $ license load allin1 to get the good
    one re-loaded.
    
    Post the information you get from the screen in here, it may help
    further diagnose. (you may ommit parts of the Authorisation, but the
    letters usually help identify where it was supplied from and which site
    it was for. It's also useless without the checksum anyway) 
    
    Richard

    Hi guys!
    
    	The product release date on the PAK means that it can be used with
    	any version of the product released BEFORE that date, so it better
    	had be in the future! 1993 is fairly normal too, as our VTXPAK system
    	arbritrarily assigns a release date = current date + 1 year, so
    	you can run any version of ALL-IN-1 released in the next year. The
    	product "knows" when it was released. The current system time is
    	irrelevant.
    
    	*ALL* cases of the problem you have reported (and I've seen LOTS)
    	were caused by the wrong license (or should that be licence?) being
    	loaded.
    
    	My recipe would be to DELETE all your ALLIN1 licenses, UNLOAD the
    	loaded one, REGISTER the new one and LOAD it. ($ LICENSE DELETE is only
    	available with LMF V1.1 which comes as an installable kit, or as
    	standard on VMS V5.5. If you don't have LMF V1.1 on your system,
    	but do have access to a V5.5 system, you can
    	$ LIC DELETE/DATABASE=node"SYSTEM password"::LMF$LICENSE from the
    	V5.5 system to your "old" node).
    
    	You can use the command $ SHOW LICENSE ALLIN1 to see the release
    	date on the one that's loaded.
    
    Regards,
    Paul
    
    PS	I thought this would cause problems! :-)

Sorry I have taken so long to get back.  I've been out.

I tried various things.  I remove all old licenses to no avail.  But I finally 
removed the current license and re-installed it and everything worked.  

I am sure it was a problem with LMF (or pilot error).  

Anyway, thanks for the input.

Mike