Well, as per my other post, I thought I had the
printers working. In fact they do work when I print
reports from fileman. But they are not working with
the TIU package properly, specifically the option:
TIUP PRINT PROGRESS NOTES, which is an action entry
that goes to MAIN^TIUPRD()
When I trace
I am reviving this thread subject from around Oct 11
2004. The suggestion by Joseph that VistaDemo would be good
for newcomer Rod Roark, motivates me to revisit it because
I want to see its sample clinical data in situ. In October,
I was able to get authenticated using Nancy's instruction
From what I understand of how the demo was put together I would not
have too much faith in doing anything more than playing with CPRS. This
demo is not a properly configured system...so while a lot beyond CPRS
may work or seem to workthe problems you can run into beyond CPRS
may be due to
I am not sure that the demo was GT.Mized, e.g., by running ZTMGRSET.
I didn't do it (at that time, I didn't realize that it was needed), and
I am not sure that it was done before it came to me to package.
-- Bhaskar
On Wed, 2005-01-12 at 16:27, Joseph Dal Molin wrote:
From what I understand
Normally if a device or file isn't open you would expect an error, not an
indefinite hang. From your previous Email, Kevin, the device is defined as
TYPE: TERMINAL. This should be HFS, not TERMINAL. But I doubt this relates
to the problem.
Since TIU prints in the background I would suggest
hmmm should have clarified my messageI meant how the VA put the
demo together...not how Bhaskar packaged it :-), ie. it is my
understanding that the demo was not assembled by the VA with the intent
to show anything more than CPRS so anything else you get out of it
without it
A couple of additional thoughts.. You don't need to open the file. ^%ZIS*
does that. Also, I noticed the DEVICE definition doesn't include open
parameters. For GT.M try (NEWVERSION:VARIABLE:NOREADONLY). Again, these
ideas probably do not directly relate to the problem, but it might be
Kevin,
The experiments I tried with OPEN and USE and CLOSE of a test file all resulted
in errors
(as expected) but no hung jobs. For instance, if the file had not been OPENed
or if it was
CLOSEd before the USE or if the file already existed but there was no new
parameter on
the OPEN.
Is an
I was contacted by Henry Bidwell Ely to ask Hardhats the question in
the text below. If you are aware of information for him, please
contact him with the information provided below.
My question is: Is Hardhats aware of any Wound and Skin Tracking Vista
applications internationally?
Thanks
H.
Confession: I discovered a faulty environmental variable
for $vista_home set to /usr/localOpenVistA missing a /
After correcting this I now have Fileman and XUP login to
Options... but this gives me the opportunity to ask:
How is this $vista_home env.variable functioning for GTM?
At the end of this post are the instructions for getting it going in the
environment I set it up in (with lots of help, of course), but it is
apparently not configured the same way as Bhaskar posted it. I had it
configured with VistA routines and globals in the VADemo off of
the
This is the same demo after porting and tweaking to make it run on GTM. If
you would like the original FOIA version that runs on Cache and the
instructions for getting it to run, send me an email and I will send you
information about how to download it.
On Wednesday 12 January 2005 06:02
12 matches
Mail list logo
