In these HIPAA days, sooner or later it is going to be not kosher to share userids or have open access systems. But that's a topic for a discussion at another time. I am scrambling this weekend to get something ready for the VistA Community Meeting in Boston.
-- Bhaskar -----Original Message----- From: [EMAIL PROTECTED] on behalf of Greg Woodhouse Sent: Sat 4/2/2005 6:57 PM To: [email protected] Cc: Subject: RE: [Hardhats-members] Need advice re Linux/GT.M login script That's an interesting question. In VHA, things have never been done this way. The MUMPS subsystem (whatever the flavor) has always run under the control of a single (pseudo-)user and then users would sign in using VA Kernel. In fact, it's not unusual to set up an account with no password but with VistA (Kernel) as its "shell". But remember that VistA originated (then called DHCP) at a time when it was not the norm for users to have their own accounts at the OS level. My VA career doesn't go back to the PDP-11 days, but it wasn't that long ago that VistA/DHCP was run on top of DOS. If VistA development were started today, I don't think it's likely that the same architecture would be used -- Or would it? Lately, I've been thinking about ways to optimize access by multiple users to the same tables/file (depending on the underlying DBMS) and it is in many ways attractive to have a single "user" accessing the database with a front-end of some sort handling synchronization and resource sharing. But then, of course, that's just what an application server is for! (Yet another way that VistA has anticipated current technology.)
<<winmail.dat>>
