--- Marc Krawitz <[EMAIL PROTECTED]> wrote: > Okay - I re-built the cross-references on the Volume Set file, and I > now > have the following tasks. I'm assuming that I need to delete 1 and > 2? > Unfortunately, I cannot do so - I get an error indicating that I can > only > delete my own tasks. What does user #0 refer to and how can I delete > tasks > 1 and 2? > > Thanks, > > Marc >
It sounds like you haven't signed in. You need to create a user with the appropriate security keys, and sign in as that user before you start. You sign is like this: BAY>D ^XUP Setting up programmer environment This is a TEST account. Access Code: <==== Enter access code here Terminal Type set to: C-VT100 Select OPTION NAME: <==== Just hit <enter> BAY> Once you've signed in as a real user (which, among other things, sets the variable DUZ to the IEN in the NEW PERSON file of that user), you'll be able to delete tasks if you have the ZTMQ key. Otherwise, you'll only be able to delete your own tasks. A lot of users have just been typing gtm (or csession cache) to go directly to the programmer prompt without signing in. This is not a good habit to be in. For one thing, in a production system you do NOT want to allow people to even be able to do this. It's the VistA equivalent of being root. But for what you're doing (set up and configuration), it's also a problem because your environment isn't fully initialized, and the system may not behave properly if it is not. The keys you want to give your adminstrative user include XUPROG - allows you to perform actions limited to programmers XUPROGMODE - allows you to go to programmer mode XUMGR - allows you to manage users ZTMQ - allows you to perform certain actions in Taskman XMMGR - allows you to manage Mailman If you have a fresh database and you have not yet set up a user for yourself, and if your version doesn't come with certain standard users already set up, you can "cheat" by picking a user and getting that user's IEM in file 200, set DUZ to that number and DUZ(0) to "@", then sign in with D ^XUP, and you won't be prompted for an access code. (Note that non-adminstrators should NEVER be allowed to enter MUMPS directly, and this is one reason why!) You need to assign the key XUMGR to your administrative user, if it isn't already there. You can then use the normal menu options. Finally, you should assign EVE as the primary menu for your admistrative user (think of it as the login shell). === Gregory Woodhouse <[EMAIL PROTECTED]> "All truth passes through three stages: First, it is ridiculed. Second, it is violently opposed. Third, it is accepted as being self-evident." --Arthur Schopenhauer ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
