WSACONNRESET error when I try connecting via CPRS.

[shouvik]

Hi All, 

I am running a new instance of vista on a new server with a fresh install. I have set up everything as before but unlike before my CPRS doesn't work. I keep getting the following error on the WVEHR-gui.log file

vista1@PUNITP213911:~/EHR$ cat WVEHR-gui.log

Tue Jul 17 18:08:04 IST 2012

/home/vista1/EHR/WVEHR-gui: 10: /home/vista1/EHR/WVEHR-gui: /mumps: not found

Tue Jul 17 18:08:08 IST 2012

/home/vista1/EHR/WVEHR-gui: 10: /home/vista1/EHR/WVEHR-gui: /mumps: not found

I tried running the code $gtm_dist/mumps -run  GTMLNX^XWBTCPM

ended up with the following error followed by the GTM command prompt.

$gtm_dist/mumps -run GTMLNX^XWBTCPM 2>>/home/vista1/EHR/WVEHR-gui.log

#

vista1@PUNITP213911:~/EHR$ $gtm_dist/mumps -run  GTMLNX^XWBTCPM

%GTM-E-SETECODE, Non-empty value assigned to $ECODE (user-defined error trap)

                At M source location BREAD+13^XWBRW

followed this thread http://www.osehra.org/discussion/error-while-executing-cprs but I don't really see how it correlated to my situation.

Any help would be graciously appreciated.

Regards

Shouvik

[David Whitten]

Could you give us the result of this command at the GT.M prompt>  ZPRINT ^XWBTCPM

This will tell us if the routine is patched up etc.

Shouvik

--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+u...@googlegroups.com

[Bhaskar, K.S]

Shouvik's problem is most likely that when coming in through inetd/xinetd, the gtm_dist environment variable is not set or nor correctly set.

Regards
-- Bhaskar

-- 
GT.M - Rock solid. Lightning fast. Secure. No compromises.

_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.

[Nancy Anthracite]

The error you got when running GTMLNX from the command line is what you should
get. The other error suggests that the environment variables aren't being
picked up correctly by the script in /home/vista1/EHR/WVEHR-gui.

--
Nancy Anthracite

On Tuesday, July 17, 2012, shouvik wrote:
> Hi All,
>
> I am running a new instance of vista on a new server with a fresh install.
> I have set up everything as before but unlike before my CPRS doesn't work.
> I keep getting the following error on the WVEHR-gui.log file
>

> *vista1@PUNITP213911:~/EHR$ cat WVEHR-gui.log*
> *Tue Jul 17 18:08:04 IST 2012*
> */home/vista1/EHR/WVEHR-gui: 10: /home/vista1/EHR/WVEHR-gui: /mumps: not
> found*
> *Tue Jul 17 18:08:08 IST 2012*
> */home/vista1/EHR/WVEHR-gui: 10: /home/vista1/EHR/WVEHR-gui: /mumps: not
> found*

>
> I tried running the code $gtm_dist/mumps -run GTMLNX^XWBTCPM
>
> ended up with the following error followed by the GTM command prompt.
>

> *$gtm_dist/mumps -run GTMLNX^XWBTCPM 2>>/home/vista1/EHR/WVEHR-gui.log*
> *#*
> *vista1@PUNITP213911:~/EHR$ $gtm_dist/mumps -run GTMLNX^XWBTCPM*
> *%GTM-E-SETECODE, Non-empty value assigned to $ECODE (user-defined error
> trap)*
> * At M source location BREAD+13^XWBRW*
> *
> *

[shouvik]

but isn't sourcing the environment variables in WVEHR-gui by the command

[shouvik]

Sorry, that got submitted by a typo.

I have typed 

source /home/vista1/EHR/env2

in the WVEHR-gui file. This is the same file I am using in the bashrc file and I was able to launch, GTM, GDE etc so I believe that the environment variables are fine. I too assumed that the variables were not getting referenced. Though I will try printing the variables in the log today to see if they are resolved correctly.

Thanks for your replies.

Regards

Shouvik

[Nancy Anthracite]

Instead of using "source", try a period followed by a space before the path to
the environment variables file. I am not smart enough about this to know why
sometimes one works and sometimes the other.

[shouvik]

Hey Nancy,

Thanks for the tip. The "." did the trick! I am pretty confused as to why this worked the way it did, but am glad it did :)

Thanks and regards

Shouvik

[Nancy Anthracite]

Bhaskar or Larry or someone out there will explain it to both of us, I am
sure!

[Bhaskar, K.S]

dot (.) is the POSIX standard (see http://pubs.opengroup.org/onlinepubs/009695399/idx/sbi.html).  "source" is a bash extension that was adopted from ksh or csh; I forget which first implemented source.  Use dot (.) if you want your shell scripts to be executable by POSIX shells.

Regards
-- Bhaskar

On 07/18/2012 12:01 AM (US Eastern Time), Nancy Anthracite wrote:

Bhaskar or Larry or someone out there will explain it to both of us, I am 
sure!

-- 
GT.M - Rock solid. Lightning fast. Secure. No compromises.

[Nancy Anthracite]

Are bash and csh and ksh POSIX compliant, or is that a dumb question?
--
Nancy Anthracite

[Bhaskar, K.S]

bash, dash, ksh, mksh and pdksh are supersets of the POSIX standard (on Ubuntu systems, for example, dash provides /bin/sh).  csh and tcsh are not POSIX compliant as far as I know.  zsh appears to be a superset of every other possible shell.

Regards
-- Bhaskar

On 07/18/2012 10:23 AM (US Eastern Time), Nancy Anthracite wrote:

Are bash and csh and ksh POSIX compliant, or is that a dumb question?

-- 
GT.M - Rock solid. Lightning fast. Secure. No compromises.

[Kevin Toppenberg]

I think the reason for this might have to do with which command line shell this linux distro is using.  It seems that there is a slight difference between bash and the other popular one (that I can't remember right now).

Kevin

[William Brummer]

[Nancy Anthracite]

That was FAST!

Since you have done some programming in the past, look at the chapters for
experienced programmers first.
--
Nancy Anthracite

On Wednesday, July 18, 2012, William Brummer wrote:
>

[Nancy Anthracite]

OOPS. I am not sure either one of us intended to send this to Hardhats. :-)
--
Nancy Anthracite

[William Brummer]

OK Thanks