RE: [Hardhats-members] flag error and detective methods
I think I resolved this issue as follows: Go to the User Management Menu - Edit An Existing User On the 4th screen of the User Management set of screens, near the top is the RESTRICT PATIENT SELECTION item. I set this to NO. Don't forget to Save =) Steven B. Tomlinson [EMAIL PROTECTED] Pacific Telehealth and Technology Hui www.PacificHui.org -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tyrus Maynard Sent: Friday, June 17, 2005 10:33 AM To: hardhats-members@lists.sourceforge.net Subject: [Hardhats-members] flag error and detective methods I have also encountered the Patient Flagnot Set error. I found Kevin's fairly recent post by searching the archives (the list archive doesnt offer a thread of discussion)and another post mentioned by Thurman, but no continued thread giving the fix. My context is with Semiviva.4 and CPRS ver*.40 which connects OK to the GUI but then dies after the error message. Besides seeking guidance,I want to take this opportunity to ask about skills for searching error messages within the vista globals. When you have a specific error message, with no clue as to where the flag resides among in the many Vista menus, is there any strategy of deduction to locate the text in a global and then map it back to a menu name??? IF anyone does this style of sleuthing, what are your tools or mumps commands, working backwards from an obscure error text? Thanks Rusty earlier post From: Kevin Toppenberg [EMAIL PROTECTED] CPRS Error: Patient Selection Flag not Set 2005-01-27 09:51 I am having a problem with CPRS. My username works fine, but when I tried to add another user, I am getting an error from CPRS that says something like: Patient Selection List Flag Not Set. Then CPRS quits. How do I fix this? thanks Kevin --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
RE: [Hardhats-members] Trying to get some debugging info with - D O DEBUG^XWBTCPM
Agreed. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Greg Woodhouse Sent: Friday, April 08, 2005 10:46 AM To: hardhats-members@lists.sourceforge.net Subject: RE: [Hardhats-members] Trying to get some debugging info with - D O DEBUG^XWBTCPM The Broker is an application layer protocol. On the other hand BSD sockets are used to implement network interfaces at the TCP or UDP level, so this is kind of apples and oranges. But, to be sure, the Broker uses a connection handling model significantly different from most TCP/IP based protocols. On the Windows end, the Broker components use plain old Windows sockets, but there still has to be an API on the MUMPS end. It would br great if MUMPS vendors would implement something like BSD sockets in a uniform way instead of forcing people to use system dependent code to accomplish the same thing. --- [EMAIL PROTECTED] wrote: I don't think the problem is so much with MUMPS, as with CPRS and the RPC Broker attempting to implement it's own protocol instead of being written to use the BSD Sockets API which has been around much longer than VistA. Steven B. Tomlinson [EMAIL PROTECTED] Pacific Telehealth and Technology Hui www.PacificHui.org -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Greg Woodhouse Sent: Friday, April 08, 2005 9:48 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Trying to get some debugging info with - DO DEBUG^XWBTCPM What is the value of ^%ZOSF(OS) on your system? It looks like the Broker is trying to use the open parameters specific to DSM. Incidntally, if I may be allowed a small soapbox here, I find it very annonying that something so basic as TCP/IP should require a syntax that is completely system dependent. MUMPS badly needs a standard sockets API. --- Mark Street [EMAIL PROTECTED] wrote: I am still attempting to connect with CPRS and I am getting this error with SemiViva FOIA Gold. Any clues? GTMDO DEBUG^XWBTCPM S XWBTDEV=% O XWBTDEV:(TCPDEV):60 ;Special UCX/DSM open ^- At column 25, line 9, source module /home/vista/r/XWBTCPM.m %GTM-E-DEVPARUNK, Deviceparameter unknown S XWBTDEV=$P U XWBTDEV:(NOWRAP:RECORDSIZE=512) ^- At column 33, line 40, source module /home/vista/r/XWBTCPM.m %GTM-E-DEVPARINAP, Device parameter inappropriate to this command Before running this entry point set your debugger to stop at the place you want to debug. Some spots to use: 'SERV+1^XWBTCPM', 'MAIN+1^XWBTCPM' or 'CAPI+1^XWBPRS.' or location of your choice. IP Socket to Listen on: -- Mark Street, RHCE http://www.oswizards.com -- Key fingerprint = 3949 39E4 6317 7C3C 023E 2B1F 6FB3 06E7 D109 56C0 GPG key http://www.oswizards.com/pubkey.asc --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members A practical man is a man who practices the errors of his forefathers. --Benjamin Disraeli Greg Woodhouse [EMAIL PROTECTED] [EMAIL PROTECTED] --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members A practical man is a man who practices the errors of his
RE: [Hardhats-members] Install problems with GDE and aliases?
You may want to try putting the aliases in your .bashrc file. Steven B. Tomlinson [EMAIL PROTECTED] Pacific Telehealth and Technology Hui www.PacificHui.org -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Peter Charbonnier Sent: Sunday, February 06, 2005 2:38 PM To: hardhats-members@lists.sourceforge.net Subject: [Hardhats-members] Install problems with GDE and aliases? Hello, This weekend I went out and picked up a new HD and installed Fedora Core 3 in the hopes of getting OpenVistA up and running on my computer at home. Things went well making the dual boot comp, but when I went to install VistA I hit a snag. Everything was fine until the very end of the Quick Start Installation Guide: 5.Create the globals file: First logout and login as the vista user, then enter the following commands: gde At the GDE prompt type: When I open a Terminal window and type gde I get - bash: gde: command not found The other aliases I set in the .bash_profile also look like they are bombing out. I either get the command not found error or Cannot access global directory. I think that I've set-up something wrong in the .bash_profile, although that's just a guess. As I said, I've only just installed Linux this weekend. I really hope it doesn't have anything to do with the big use core 1 only warning on the pacific telehealth website. Any help would be appreciated. Thanks, Peter Charbonnier Overlake Hospital Bellevue WA --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
RE: [Hardhats-members] RPC communication with random callback por t -- SOLVED.
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 Toppenberg Sent: Monday, December 20, 2004 1:05 PM To: [EMAIL PROTECTED] Subject: [Hardhats-members] RPC communication with random callback port -- SOLVED. Hey all, After finding the info below, and reading other's confirmation that the problem was in WSockc.pas, it wasn't too hard to fix this 'bug'. Here is the fix: on line 700 OF WSockc.pas, change the following line: LocalHost.sin_port := 0; { -- local listening port} to this: LocalHost.sin_port := htons(ListnerPort); { -- local listening port} So here is the surrounding code to help locating it: LocalHost.sin_family := PF_INET;{ -- internet address type} LocalHost.sin_port := htons(ListnerPort); //kt added { -- local listening port} SocketError := bind(hSocketListen, LocalHost, SizeOf(LocalHost));{ -- bind socket to address} If SocketError = SOCKET_ERROR Then NetError( 'bind',0); The project file for CPRS did not initially include WSockc.pas in the project list. Thus I couldn't trace to the exact point of the error and make the change. So, go to the menu [Project], then [Add To Project]. The file should be in the ...\Broker\Source\ directory. But do a file search for wsockc.pas if you can find it. I will add, incidentaly, that the reject message that I was getting stopped as soon as I made this fix. It's nice when a difficult problem is quickly found once in awhile. :-) Kevin --- Kevin Toppenberg [EMAIL PROTECTED] wrote: 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 change RPCBroker to use the user-requested port number. Kevin --- Kevin Toppenberg [EMAIL PROTECTED] wrote: 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 along these lines, I have been tracing through the code. I don't have any experience with winsock communications, so I wonder if someone could explain how this is working, and if there is a way to avoid the random callback port. CPRS sends a message to the RPC server that includes the port to call back on. This port seems to be assigned by a call to the windows code getsockname. The structure of the message is: TCPconnect^local ip address^callback port^workstation name^(no call-back--[not used in RPCBroker]) Furthermore, looking on the server-side code, there appears to be an option for the client CPRS to send a signal that it does NOT want a callback. Yet in the CPRS RPCBroker code, there is no variable for signaling this option. So in summary, would there be an easy way to tell the RPC server not to use the random port? And does communication require separate ports for outgoing and incoming signals?? I wouldn't think so, as telnet, ssh etc. all use just one port number. So why is winsock doing this screwy random port assignment?? Thanks Kevin __ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ Hardhats-members mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hardhats-members __ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ Hardhats-members mailing list
RE: [Hardhats-members] Krung Thai Bank goes live on GT.M
Just curious, was this deployment based on the Open Source release of GT.M? Steven B. Tomlinson [EMAIL PROTECTED] Pacific Telehealth and Technology Hui www.PacificHui.org -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of K.S. Bhaskar Sent: Friday, December 03, 2004 4:23 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [Hardhats-members] Krung Thai Bank goes live on GT.M http://www.fidelityinfoservices.com/FNFIS/CompanyLevel/NewsEve nts/20041108.htm Krung Thai Bank is the second largest bank in Thailand. To the best of my knowledge, at over 14 million accounts, this is the largest single real-time core processing system in production at any commercial bank anywhere in the world. -- Bhaskar ** * This electronic mail transmission contains confidential and/or privileged information intended only for the person(s) named. Any use, distribution, copying or disclosure by another person is strictly prohibited. ** * NOTE: Ce courriel est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus et peut contenir de l'information privilegiee, confidentielle et/ou dispensee de divulgation aux termes des lois applicables. Si vous avez recu ce message par erreur, ou s'il ne vous est pas destine, veuillez le mentionner immediatement a l'expediteur et effacer ce courriel. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ Hardhats-members mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ Hardhats-members mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hardhats-members
RE: [Hardhats-members] Cutting to the chase regarding licenses
This is why I pushed for the development of the Hui Openvista Free Software License. It is an attempt to satisfy the Socialist and Capitalist communities. It allows organizations to do the distribute free software, share the source code, hope someone else is vetting/testing, without taking responsibility, thing, while at the same time allowing others to do the let's keep our changes/fixes to ourselves, sell software, and assume some liability types, to do their thing. My interest is simply to see quality Electronic Health Record Software adopted by as many health care professionals as possible, in whatever form, by any means possible. I believe the Hui Openvista Free Software License helps in this regard by not enforcing any particular business model on an organization that may wish to provide the software. DISCLAIMER: I do not speak for the Hui, U.S. Government, or any other organization, simply my thoughts and opinions on this particular issue. Steven B. Tomlinson -Original Message- From: K. S. Bhaskar [mailto:[EMAIL PROTECTED] Sent: Monday, November 22, 2004 4:07 AM To: [EMAIL PROTECTED] Subject: [Hardhats-members] Cutting to the chase regarding licenses Cutting to the chase, is the fundamental issue that of Medsphere, and perhaps others in the VistA Software Alliance, prefer licenses that do not require downstream disclosure of source code, whereas WorldVistA, and some members of the VistA community (including me), prefer licenses that do. The only compromise would appear to be to eliminate licensing altogether - i.e., public domain. Is this a fair summary? -- Bhaskar --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ Hardhats-members mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ Hardhats-members mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hardhats-members
RE: [Hardhats-members] Visa Installers
Interesting ... this appears to be from a 9 location medical center ... www.grovehill.com Steven B. Tomlinson[EMAIL PROTECTED]Pacific Telehealth and Technology Huiwww.PacificHui.org -Original Message-From: Labbadia, Carl [mailto:[EMAIL PROTECTED]Sent: Wednesday, October 27, 2004 10:16 AMTo: '[EMAIL PROTECTED]'Subject: [Hardhats-members] Visa Installers Is anyone looking to work with a clinic and move forward on an installation process? Drop me an email if you care to discuss this further. DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you. Tomlinson, Steven B.vcf Description: Binary data