HP3000-L Archives

July 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Johnson, Tracy" <[log in to unmask]>
Reply To:
Johnson, Tracy
Date:
Tue, 13 Jul 1999 21:58:21 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
From:   Cobo, David [SMTP:[log in to unmask]]

tracy,
      try adding the menufile name to streamx.data.vesoft with the appropriate cap for the appropriate user(s). Hope this helps.

example:

?withcaps-permit user.account menufile.group.account "cap"

----
This worked but, it seems to fly in the face of the WITHCAPS part of the manual, which says in two places:

Often you might want to have users execute certain commands in command files, job streams or menus, that require more capabilities than they have.  For ...

* You add lines to the STREAMX.DATA.VESOFT file that indicate which command files/menus/job streams being executed ...

This tells me it can be either a command file OR a menu file OR a job stream.  If it has to be the menu file that has to be authorized, why doesn't it work by just by authorizing just the command file?  Or is it the fact my command file is IN a menu that takes precedence?

In any case, I tried your suggestion, and it worked.

By reading the Manual and FAQ I can't find that a menu file takes precedence.  Although now it seem logical since I was executing the command file WITHIN the menu.  It just isn't obvious.

Seems I had a 50% chance of setting the right file just by reading the manuals.

ATOM RSS1 RSS2