Sorry, I forgot about Eastern Washington, so there are two state hospitals in
Washington using VistA. My point still is we need to be careful about what we
write on this list. This is a wonderful place to get information about VistA,
M, or practically any sort of healthcare IT topic. With
Kevin, In that second block of code, the reject reply is sent when the
attempt to JOB EN^XWBTCPC(parameter_list) fails (timeout=5 sec). Failure is
also recorded under ^TMP(TCP). Thus, zwrite ^TMP(TCP) should confirm
or disconfirm failure at this point. Clearly this is debug code. However,
I have been looking at the code for IP communication
between the windows CPRS client and the M server. I
appears that CPRS calls the RPC server on the
specified port, but that server then calls the client
back an a randomly chosen port.
Seems like an awkward setup. Since I was having
trouble
Lloyd,
Thanks. I saw your name in the code, so I know you
hve knowledge in this area.
Also, I see the command LOG^ZUTIL(...) How do I
read these log files/entries?
I'm hoping you have some input on my other post too.
:-)
Thanks
Kevin
--- Lloyd Milligan [EMAIL PROTECTED] wrote:
Kevin, In
OK, so here is my script after revisions. This won't
run a specified routine on startup. I would need a
script that replaces
$gtm_dist/mumps -dir
with
$gtm_dist/mumps -r MYFUNCT
I'll have to learn a bit more of the scripting
language to do the following pseudocode:
if exists($1)
Let me just add quickly (got to work) that in the code
the local listening port is specified to be 0 before
calling the winsock 'bind' function. Doing a web
search on this issue reveals that if you specify the
port to be 0, then winsock will assign a random port.
So it seems that we just need to
Hmm, I remember looking over Steve Shreeve's shoulder as we tried various
tricks to work around the non-routeable callback problem. As you see the
client can signal that it doesn't want to be called back (requires modifying
the client broker to use ^-piece 5 of the message), or the server can
Title: CPRS Messaging
I have been customizing the CPRS client to fit my organization's needs. So Far, I have been able to add information on the server side and display it on the client by adding to the server-side messages. This is ok for display purposes, however, I would like to add fields
I will put it stronger. I wish we could do more to encourage Intersystem
and Cache users to post on this list. I personally have been taken aback by
the serious animosity toward Intersystems that has been posted on this list.
My guess is that it is only a few people expressing a lot of
If you wish to have voices speak up, so be it. I agree with you. It
appears that hardhats has degenerated into a freebie-linux-gtm forum rather
than its original intent which is exposure to the VA's platform independent
VistA EHR.
- Original Message -
From: James Gray [EMAIL PROTECTED]
i don't think the list can be called a degenerated at all, but could be
interpreted as an example of the popularity of open source solutions and the
viability of oss as a business model. perhaps something intersystems should
take note of...
--- steven mcphelan [EMAIL PROTECTED] wrote:
If
I'm a Cache user and do post here quite a bit but as you can tell most
of the questions are for GT.M as that is the opensource M that is
available. Also, since Vista pretty much works out of the box under
Cache, there aren't too many questions to ask. The install guide on the
hardhats website is
When I looked at the Sept. 24 to 30, 2004 posts with the thread VistA Without
CPRS. Roy Gaber said it is this:
The code is in wsockc.pas, the port for the callback is actually set by
the client. Look for LocalPort in the code and you will see how the RPC
Clientgets this port, it sends the port
I, for one, feel that anyone interested in VistA on any OS is someone I would
like to talk to.
Let's not divide ourselves into camps. We are not such a huge group that we
can afford to do that.
On Monday 20 December 2004 01:51 pm, steven mcphelan wrote:
If you wish to have voices speak up,
Let me state it even more strongly - without Intersystems, MUMPS will truly
be dead. It's imperative that they and their users get more actively
involved in the Open VistA movement - they can bring a great deal of
credibility to the movement. Personally, I use Cache for all my current
development.
Lloyd, it is apparent that you could sure help improve Chapter 2 (getting CPRS
running and connected) on the Hardhats site by either adding or helping me to
add all of this great stuff you are talking about to it.
Now that I have openly twisted your arm, I'll write to you to see if we can
Just a guess, but take a look how vital signs are handled. I believe they are
entered in CPRS and then can be graphed, so they are probably entered into a
field of their own like you must want.
On Monday 20 December 2004 12:48 pm, Boon, Thomas wrote:
I have been customizing the CPRS client to
I'd like to remind everyone of the M21 MUMPS supplier in Rugby UK.Thye too
have been around a while and the hardhats as well as the vista community
should be encouraging these Supplier. Much of the animosity regarding
Intersystems arose when it bcame the (almost) only Supplier until
Greystone
This thread seems to have gained attention. As someone who has flirted with
MUMPS since 1975 and actively tested it since 1985, I don't get a sense of
what I would call animosity. Nor do I get much of a warm fuzzy feeling. This
just seems a fact, as the most active participants are working with
I have written to them but have yet to hear a peep.
On Monday 20 December 2004 06:33 pm, A. Forrey wrote:
I'd like to remind everyone of the M21 MUMPS supplier in Rugby UK.Thye too
have been around a while and the hardhats as well as the vista community
should be encouraging these Supplier.
Hardhats
I am installing VistA on a Windows PC using Cache.
I am following the steps in VistA Install with Cache 5 in Windows, Chapter 1.
At step 91,when I entered D ^ZU the Cache Terminal crashed. I
briefly glimpsed the word trouble on the Terminal window before it
disappeared.
What am I
Obviously, even the open sourcerers benefit from a broader market.
I agree that we'd all benefit from a more visible Cache presence here. There
is a lot of Cache experience, of course. (Tom Ackerman comes to mind... And
the whole VA, come to think of it!)
My own roots are heavy with Micronetics
Hi Kevin,
Just curious ... have you tried this with multiple clients connecting at the
same time?
Steven B. Tomlinson
[EMAIL PROTECTED]
Pacific Telehealth and Technology Hui
www.PacificHui.org
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Behalf Of Kevin
Speaking of Bhaskar, I've been on this list for probably ... has it been
2 years?! He's always responded and helped the list in all things - not
just GTM. My surprise to the continuing threads is the missing link of
a Cache uber-geek. Lots of us use the system and can answer questions
but I do
In the terminal window, try VAHD ^XUS instead of VAHD ^ZU. You should be
thrown back to the programmer's prompt without the Cache window closing if
you have problems.
- Original Message -
From: David Reister [EMAIL PROTECTED]
To: Hardhats Members [EMAIL PROTECTED]
Cc: David Reister
We were trying to work this out the other day. I think the resolution was
instead of doing step 38 the way it is now, comment out this line by putting
a semicolon in front of it. Try that to see if it works and let us know,
please.
JOBCHK I $$AVJ^%ZOSV()3 W $C(7),!!,** TROUBLE ** - ** CALL
See, I knew we had a Cache guru among us. :-)
Kevin
--- Robert M. Witkop [EMAIL PROTECTED] wrote:
David,
If you are running a Cache terminal in Windows, turn
on logging by
clicking on file - logging and create a log file.
If there are any
problems, the error will be written to the log
Think Nancy supplied this reply...
That appears to come from
;The next line keeps sign-on users from taking the last slot ;It can be
commented out if not needed.
JOBCHK I $$AVJ^%ZOSV()3 W $C(7),!!,** TROUBLE ** - ** CALL IRM NOW!
** G HALT
I solved the problem by reducing 3 to 1. Comment out
Proof after hitting SEND. Append to the end of my last email, Varying
levels of expertise across platforms like Bob Witkop.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin
Toppenberg
Sent: Monday, December 20, 2004 10:57 PM
To: [EMAIL PROTECTED]
29 matches
Mail list logo
