Release of EsiObjects V4.2.0.9_RC3 to SVN...

[Terry]

I put a new release of EsiObjects (eo_server_gtm_4_2_0_9_rc3.tar) up
on the SVN (https://esiobjects.svn.sourceforge.net/svnroot/esiobjects/
EsiObjects/Kits/Ports/GTM).

It contains the following two fixes:

1) Routine VESOIM7 enhanced to include Option block Property_Value.
2) Compiler routines VESOIT1 and VESOIT2 GT.M compile tables enhanced
to include all new GT.M commands, special variables and functions.

I will put up a new Cache release shortly.

If any of you can find the time to test this, I would really
appreciate it.

Terry

[Terry]

A new Cache release of EsiObjects (eo_server_cache_4_2_0_9_rc3.tar) up

on the SVN (https://esiobjects.svn.sourceforge.net/svnroot/esiobjects/

EsiObjects/Kits/Canonical).

Terry

[Terry]

I've moved Alex's comments over from the Slipstream:

Hi Terry,

A couple of differences in the set up documentation (readme_cache.doc)

$ZV = "Cache for Windows (x86-32) 2009.1.1 (Build 504.0_SU) Wed Aug 26
2009 16:57:48 EDT"

On Page 2 the documentation says shut down cache and open the Cache
System Management Portal.
The old windows based management portal is no more. It has been
replaced with a CSP based version which requires Cache to be running
in order to access it.

Continuing with Cache running I access the system management portal to
look for the memory settings specified "RoutineBufSize" and
"MaxMemPerProcess". After a bit of navigating around I gave up trying
to find the links.

I opened up the Cache cpf in notepad and had a hunt around for the
settings and couldn't see any memory settings with the names
specified. At this point I concluded that perhaps these are names or
settings from an earlier version of Cache.

In the default install of cache there has always been a database and
namespace called USER. So I feel it is unfortunate to also call the
default ESI namespace USER. Instead I used "ESIUSER" as both the
namespace and database name. It doesn't seem to be detrimental and
might be less confusing in the instruction.

I don't think the instructions for global and routine mappings are
correct. In both cases the documentation says "Select the database
USER location" - in the user namespace this would just map to itself.
I believe it should say "Global database location : ESI" for global
mapping and "Routine database location: ESI" for routine mapping.

Perhaps a section to verify the mappings are correct would be useful.
A user could use a cache terminal:
Switch to the ESIUSER namespace
>ZN ESIUSER

Use Global Directory to list globals
> D ^%GD

Use Routine Directory to list routines
> D ^%RD

Alternatively this is available via the Management Portal:

Home - DataManagement
"Globals" link ... "ESIUSER" namespace
Should see a list of globals starting with VES
"Routines" link .... "ESIUSER" namespace ... "*.int" link
Should see a list of routines starting with VES

I guess its not possible to include any screen shots in documentation,
even with a cache license installed for demonstration?

I've started up a server listener process on port 9000 as directed.

I ran the "Setup.exe" client installer ran OK. (Version 4.2.0.0 Test
release build 3)

Have a connection to the server OK - took a while "Updating objects?"

I'm not sure whether I have a matched client and server install or
whether I need to patch the server but...
I noticed in the Session Browser that I get a specific error on
certain icons when I click them.
For example:
Base.AsbLocableObject between Primary and Collection there are 2
unlabelled icons. When I select these I get a windows message box
titled: "Call Error"
"<Null> is not a Pointer to an Object"
Class: Session
OID: ?N%obj(1)
This repeats twice when I try to cancel.

Do you have a regression and unit test suite that you normally run to
validate a server installation?

Hope this is useful.

Cheers


Alex

[Terry]

I guess I should upgrade Cache more than every 2 years.

I cleaned up the readme file and changed the USER to ESIUSER as
recommended. Changed instructions to leave journaling on and fixed the
mappings.

I think "RoutineBufSize" is actually 'Memory Allocated for Routine
Cache' - correct me if I'm wrong.

Update at session connect should not happen in full install again -
forgot to set the version number.

Null pointers gone...

You can find an updated kit on the SVN at:
https://esiobjects.svn.sourceforge.net/svnroot/esiobjects/EsiObjects/Kits/Canonical

Please let me know if you find other problems...

Terry