More Problems with Tutorial

[dheller]

Hello

Now I'm having a problem with Chapter 15 Validating the Name property

When I do: If '$Valid(I%Test.Name,"Doe, John L") DO $Env.Assert("Name
Invalid - Try again!")
or If '$Valid(I%Test.Name,"Doe, John L") Write "Name Invalid - Try
again!"

I get the following error message:

Bad Expression: Null expratom
Class: ClassLibrary
OID: (?)N^TUT("Library",2) (?) is some kind of square
<External Call>
Service: System>Xecute
Implemented by class: Object
Called by <External Call>
150373850,TRACE+5^VESOTCSH,%GTM-E-UNDEF, Undefined local variable: %obj
(1,,TCPDevice)

My Validation Code is as follows

Options: (
Inheritable,
Property_Valid,
Type=Boolean,
Public,
Name=Name,
Platform=All
);
Input:( (System,In,Type=String)P%Nam
) Break
;Error if name contains control characters.
Quit:P%Nam?.E1C.E 0
;Error if name is not proper format.
Quit:P%Nam'?1.30A1", "1.30A1" "1A 0
;Passes check
Set $Return=1
Quit.

This compiles without errors or warnings

Thanks,

Dave

[Terry L. Wiechmann]

What versions of the following are you using?
GT.M:
EsiObjects Server:
EsiObjects Client:

Terry L. Wiechmann
978-779-0257
http://www.esitechnology.com

[dheller]

Terry I have the following

GT.M: V5.3003
EsiObjects Server: V4.2.0.8 Candidate 1
EsiObjects Client: V4.2.0.0 (Release Candidate)

On Jul 21, 8:21 am, "Terry L. Wiechmann"

<tlwiechm...@esitechnology.com> wrote:
> What versions of the following are you using?

> GT.M: V5.3003
> EsiObjects Server: V4.2.0.8 Candidate 1
> EsiObjects Client: V4.2.0.0 (Release Candidate)
>
> Terry L. Wiechmann
> 978-779-0257http://www.esitechnology.com

Dave

[Terry L. Wiechmann]

Dave,

Sorry for the delay.

I've tried to reproduce this error here and can't. Based on the error,
it looks like some kind of session connection error. Does it do it every
time you connect and try to execute this and only this code or does it
do it all the time?

I noticed in a previous message that you used the "Inspect" command.
This means that you are coming up with EsiObjects Programmers privileges
which means you have access to all the EsiObjects internals.
Unfortunately, the tutorial does not elaborate on the different levels
of privileges at startup which it shouldn't at that point. However, it
should simply specify what privileges to startup with and doesn't - I'll
change that.

The point is, if you can see the Inspect command means you have probably
checked all the User privileges in the Connections property sheet for
the session - particularly the "Debugging" option. This means you have
"EsiObjects" programmer and debugging privileges. This means that
anytime you bring up the Xecute Shell, it will come up in the object you
have selected (possibly an EsiObjects object), not the $Environment
object. If you simply type int "ZV" (rather than ZV $ENV) to bring up
the Object Browser, you can quit possibly be in an EsiObjects object.
Consequently, if you can inadvertently change EsiObject by executing
commands.

I'm not saying this is what happened. However, to eliminate this
possibility, please do the following:

1. Export your tutorial work.
2. Do an "upgrade" of EsiObjects. Read the readme file for
instructions. This will not destroy your work - but do a backup
anyway
3. Bring the UI up and under File|Connections|Show, bring the
property sheet up for the session. Under the User tab, make sure
the Debugging and Internals check boxes are unchecked. Log off and
back on. Make sure the "Inspect" does not appear.
4. Try Lesson 14 again.

Let me know what happens.

Note: If you want to keep the Inspect menu option, then make sure you
always type "ZV $Env" to bring the Object Browser up in the context of
the $Env object.

Terry L. Wiechmann
978-779-0257
http://www.esitechnology.com



dheller wrote:

[dheller]

Terry

I will try what you suggest. I also get the same error when trying to
write to globals such as when doing the following: Set ^VESCB
("ORB","DEFAULT","ObjectHost")=192.168.1.92
when I was installing the ESIOrb. So either something happened during
the installation or I did something to mess it up.

Dave

On Jul 26, 8:34 am, "Terry L. Wiechmann"

> 978-779-0257http://www.esitechnology.com

[dheller]

Terry

I think I know what happened, the startup script /etc/init.d/
esiobjects
needs the following line added if OS is Ubuntu 9.04: . /lib/lsb/init-
functions
Otherwise esiobjects will not shutdown because
killproc is not found. I did not realize this until I tried to
shutdown esiobjects to
perform a upgrade. This also may effect other debian based systems.
There are reports
of this happening with other startup scripts also.


Dave

[dheller]

Terry

Still won't go! I got another server I can try that is Red Hat Based
I'll let you know in the next couple of days.

Dave

[Terry L. Wiechmann]

Yes, that release and all previous releases are tuned to RH. The next
release has been built to install generically (if there is such a thing
in the Linux world). Sorry about that. I've almost got the new install done.

Terry L. Wiechmann
978-779-0257
http://www.esitechnology.com



dheller wrote:

[dheller]

Terry

I finally got it to work on Ubuntu 9.04

Here is what I did:

Modified /etc/init.d/esiobjects as such:

#!/bin/sh
#
# chkconfig: - 91 35
# description: Starts and stops the esiobjects connect service
# pidfile: /var/run/esiobjects.pid
# config: /etc/sysconfig/esiobjects


# Source function library.
if [ -f /etc/init.d/functions ] ; then
. /etc/init.d/functions
elif [ -f /etc/rc.d/init.d/functions ] ; then
. /etc/rc.d/init.d/functions
elif [ -f /lib/lsb/init-functions ] ; then <-This line added
. /lib/lsb/init-functions <- and this line
else
exit 0
fi

# Avoid using root's TMPDIR
unset TMPDIR

# Source networking configuration.
. /etc/sysconfig/network


# Get GTM setup
if [ -f /etc/profile.d/gtm.sh ] ; then
. /etc/profile.d/gtm.sh
else
gtm_dist="/usr/local/gtm"
export gtm_dist
fi

if [ -f /etc/sysconfig/esiobjects ]; then
. /etc/sysconfig/esiobjects
fi

# Check that networking is up.
# [ ${NETWORKING} = "no" ] && exit 0 <- commented out

#Pretend we are a VT100 so GTM does not Quit
TERM="vt100"
export TERM

gtmroutines=". /usr/local/esiobjects/source /usr/local/esiobjects/user
$gtm_dist"
export gtmroutines

EsiObjects_Source="/usr/local/esiobjects/user"
export EsiObjects_Source

gtmgbldir=/usr/local/esiobjects/data/esiobjects.gld
export gtmgbldir

esiobjectsdir=/usr/local/esiobjects
export esiobjectsdir

esiobjects_config="/etc/sysconfig/esiobjects"
export esiobjects_config

RETVAL=0


start() {
KIND="EsiObjects"
echo -n $"Starting $KIND services: "
$gtm_dist/mumps -r ^VESOGTCM <-This line modified there is no
"daemon" in Ubuntu
RETVAL=1
echo
return $RETVAL
}

<snipped> (no changes)

And added /etc/sysconfig/networks as follows:

NETWORKING=yes
HOSTNAME=daveh-desktop
GATEWAY=192.168.1.1


Dave

On Jul 27, 9:37 pm, "Terry L. Wiechmann"

<tlwiechm...@esitechnology.com> wrote:
> Yes, that release and all previous releases are tuned to RH. The next
> release has been built to install generically (if there is such a thing
> in the Linux world). Sorry about that. I've almost got the new install done.
>
> Terry L. Wiechmann

> 978-779-0257http://www.esitechnology.com

[Terry L. Wiechmann]

Thanks Dave,

We've tentatively decided to use xinetd instead of the EO redirector in
the future - but nothing is certain at this point... :-\

When it comes to Linux level stuff, I'm not much help unfortunately. So
it's good to see someone who can deal with that level.

Let me know how it goes...

Terry L. Wiechmann
978-779-0257
http://www.esitechnology.com



dheller wrote: