topic Re: PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3 in Operating System - OpenVMS

PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3

Dom Searle — Mon, 29 Sep 2003 10:31:42 GMT

We are using VMS 7.3 PATHWORKS V6.1 for OpenVMS (Advanced Server).

Previously we had a license for 25,000 units. We now have a 2,500 unit license which is newly installed. Since this change in license the following occours on a pathworks startup. We have disabled the old license.

---Taken from file pwrk$license_s_nodename.log--

$ run SYS$SYSTEM:PWRK$LICENSE_SERVER /NoDebug
29-SEP-2003 15:12:10.00 2144F636:001D2C00 Using OpenVMS V7 DEC C time logicals
29-SEP-2003 15:12:10.07 2144F636:001D2C00 GMTinit: timezone = 0
29-SEP-2003 15:12:10.07 2144F636:001D2C00 GMTinit: daylight = 0
29-SEP-2003 15:12:10.07 2144F636:001D2C00 GMTinit: Local time = 29 Sep 2003 14:12:10 GMT
29-SEP-2003 15:12:10.11 2144F636:001D2C00 GMTinit: GMT time = 29 Sep 2003 14:12:10 GMT
29-SEP-2003 15:12:11.53 2144F636:001D2C00 PW_init: 451 CCBs out of 758 io channels, 1516 xccb
%SYSTEM-F-ABORT, abort
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC

LOGGING PLog 8586 000002E9 0001663D
STATE_FILE AdjustTotals 18406 00000263 00018B07
PL lmfSynch 32107 000000A9 000085DD
PL AddProd 28179 00000099 00004641
REGISTER LSStartup 29663 00000190 0000D648
PL LsMain 32718 000006F4 000090B0
00125C85 00125C85
MTS$MAIN main 5464 00000029 00002839

------------------------------------------------
We have changed the maximum amount of users that can connect through $admin/config to reflect the change but to no avail.

Anyhelp would be appreciated.

Thanks.

Re: PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3

Antoniov. — Mon, 29 Sep 2003 12:33:43 GMT

Hi Dom,
Admin/License does work?
Can you see license loaded and what type of licensing are you using (server mode or client mode)?
Also what license code (i.e. PWLMXXXCa07.03)?

Bye
Antoniov

Re: PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3

Dom Searle — Tue, 30 Sep 2003 03:13:56 GMT

Admin/License says
"Success"
"Unable to communicate with license server"
"Continue"

$lic list /full
-----------------------------------
Issuer: DEC
Authorization: AMA-IL-2003SEP12-5
Product Name: PWLMXXXCA07.03
Producer: DEC
Units: 2500
Version: 0.0
Release Date: (none)
PAK Termination Date: (none)
Availability: 0
Activity: 000000100
Options:
Hardware ID:

Revision Level: 1
Status: Active
Command: REGISTER
Modified by user: ITAM
Modified on: 17-SEP-2003 14:46:47.95

Currently we are using a server mode licenses.

Thanks again,
Dom

Re: PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3

Antoniov. — Tue, 30 Sep 2003 07:44:18 GMT

Hi Dom,
it's obvious license server cannot start and you cannot manager AS license.
If I understand you had 25,000 units and you added 2,550 unit so you should have 27,500 units of *CA07.03 license. Is it right?
So if you have 27,500 when you type sho lice
you shoul see:
PWLMXXXCA07.03 DEC 27,500 0 100 (none) (none)
Because if you have 27,500 units loaded may be old license wer unloaded and then PWRK license crash (because are allocated more units than licensed).
If you see 2,500 (and not 27,500) you couls unload and then reload license.
ONLY IF YOU HAVE NOT 27,500 UNITS (no execute follow statemente if you see 27,500):
$! Unload license (No PC user cannot log in)
$ LICENSE UNLOAD PWLMXXXCA07.03
$! Immediatly load licende
$ LICENSE LOAD PWLMXXXCA07.03
$! Now show license
$ SHOW LICENSE PWLMXXXCA07.03
PWLMXXXCA07.03 DEC 27,500 0 100 (none) (none)

Bye
Antoniov

Re: PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3

Antoniov. — Tue, 30 Sep 2003 09:23:28 GMT

Hi Dom,
Post info about this check-list.

1) License check
Read prior post.

2) ADMIN/CONFIG
I think you need 2750 client; when you press RETURN (to verify) system tell you "Then number of client specified (nn) CAN be supported. You not need run AUTOGEN ..."?
Also what transport are enabled?

3)You manage license in server mode, so each PC don't query a license. If you would manage license using DecNet, remember you should change links in executor. If you would manage usign TCP/IP, TCPIP have running.

4) Now you can obtain furthermore information reading log event
ADMIN/ANAL/SINCE=time/CLASS=ERROR/SOURCE=LICENSE_MANAGER
to see if find any license manager error.

I can't think any other but your problem sound like a wrong system parameter.
Bye
Antoniov

Re: PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3

Dom Searle — Tue, 30 Sep 2003 09:55:51 GMT

(1) We have disabled the old license 25,000 unit license and got a new 2,500 unit license. Therefore we have a 25 user license. So the show lic is correct.

(2) Admin/config is set correctly to 25 users

(3) TCPIP is running.

(4) Output to the anal command is as follows

admin/anal/since=yesterday/class=error/source=license_manager

:::::::::: PATHWORKS Error Log Report ::::::::::
DATE: 30-SEP-2003 15:53:30.92

As you can see, no errors ??

Thanks again for all your help,

Dom

Re: PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3

Antoniov. — Wed, 01 Oct 2003 02:40:16 GMT

Hi Dom,
I think your problem was born when you have updated license; perhaps were allocated more then 2500 units when new license was loaded and so license manager crash.
The best way to work should be:
1) Enable old license again so you have 27500 units temporarly active.
2) Start license manager: now it should not go in crash.
3) Activate license manager ADMIN/LICENSE; becuase you are using server license model, you must remove 25000 units from group server and assign it to client group; after this operation, no any PC can allocate client license.
4) Now you can disable old license
5) Shutdown and startup license server process.

I haven't post detail of every operation; if you need I can write more detail.

H.T.H.
Antoniov

Re: PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3

Dom Searle — Wed, 01 Oct 2003 04:42:20 GMT

Thanks again for all you suggestions. Unfortunately the previous license has expired so I cannot re-load it and try your suggestion.

If there are parameter held in admin/license that I cannot get to but need to edit, is it ok to manually edit the configuration files if I can find the file the parameter is set in ?

Thanks

Re: PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3

Antoniov. — Wed, 01 Oct 2003 08:09:38 GMT

Yes, it's possibile manage manually license file using LICENSE command instead VMSLICENSE.COM; but this is difficult to make and may be dangerous; I think your license is expired so to recall it you should update system date and then make a new license file.
You should copy manually all license (one for time) then restarting with new; theese operation (change date e change file) could are not executing while system working.

Reading my documentation in SYS$HELP:ASOVMSV72A072.RELEASE_NOTES (your shoul be ..v73...) I read xccb error is due to exceeded session allocated. So the unique way to solve your problem is free allocated sessions but there is not any command can make it.

Now I'm walking in the dark (I don't know exactly english terms) how disable allocated.
Perhaps you can do follow:
Shutdown license using @SYS$STARTUP:PWRK$LICENSE_SHUTDOWN
set 1 minimun expiration time
$ DEF/SYSTEM PWRK$LS_IDLE_EXPIRATION 1
so license manager free allocated after 1
day.

Sorry but now I have no idea best way
Bye
antoniov@shs-av.it

Re: PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3

Rob Buxton — Sun, 05 Oct 2003 18:26:46 GMT

I don't run the license server, so just guessing a bit here.
Try looking for any .INI Files in the PWRK$Root: structure.
In our Setup there's pwrk.ini which has an entry for starting the License Server or Not and then there's the lanman.ini.

There may be an entry stored in one of these that can be manually edited.

As I've said I don't run the License Server and have not tried this.

Re: PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3

Brad McCusker — Fri, 10 Oct 2003 16:44:14 GMT

Dom,

First, the ACCVIO/crash you see has not been seen before. Feel free to contact the CSC and escalate to engineering to expediate recieving a fix, if you want one.

But, I can probably get you a workaround. I don't think the code expects the license
counts to ever go down, and, this is exactly what you have done.

Rebuilding the license database after installing the new license should solve the problem.

Try deleting the licenses database files:

1. Shutdown PATHWORKS, cluster wide
2. $ DELETE PWRK$LICENSE:PWRK$LICENSE*.DAT
3. Restart PATHWORKS
4. Let us know how it worked out!

I'm going to enter an Internal Problem report on this.

Regards,

Brad McCusker
OpenVMS Engineering

Re: PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3

Dom Searle — Mon, 13 Oct 2003 04:33:25 GMT

Removed the files after a shutdown. On a restart I received the following two errors

1. "Semaphore Password Expired"
2. "Could not allocate license for Computer Name"

Had to shut pathworks down and restore the files.

Thanks,
Dom

Re: PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3

Antoniov. — Mon, 13 Oct 2003 07:33:50 GMT

Hi Dom,
Brad has released a good clue.
You could remove license file and then reinstall Adv.Server; in this mode, installation will create new empy license files while configurations files still unchanged.
Perhaps you can solve your problem.

Bye
Antoniov

Re: PATHWORK ADVANCED SERVER 6.1 For OpenVMS 7.3

Brad McCusker — Mon, 13 Oct 2003 07:48:20 GMT

Well, the re-install Advanced Server is a big hammer, but, I suspect it would get the job done - maybe. When you start PW/AS, if the license database files aren't there, they get created.

Are you in a cluster? Did you do the PW shutdown across the cluster?

Did you look to see if new license database files got created (those are the ones I told you to delete)?

The errors you report - Where did you see them, during startup of AS? Did you still get the ACCVIO?

What I told you should work. Can you give me more detail on the exact steps you took, and the exact errors you saw and when/where? (Maybe I was vague in my direction to you? If you saw thsoe erros from a client, is it possible the client already had a license? Can you try it from a client that doesn't have a license already?