For UV, LOGTO seems to work like this:
If you don't specify the full path and the account exists in UV.ACCOUNT
it will go there; otherwise it looks for the account in your current
directory (at the same level and below) and will go there. If it
doesn't exist in your current directory and it doesn't exist in
UV.ACCOUNT, you can only LOGTO it if you specify the full path. Of
course, we always put a security subroutine in the LOGTO command that
does other checks too!
-Dianne
Tony Gravagno wrote:
I'd like to piggyback on this question with another related:
What is the exact set of rules for determining whether an account
can/should be referenced via a full path vs just the name? It seems it's
not as simple as just having an entry in UV.ACCOUNT or UD.ACCOUNT. Is this
flavor-dependent? It seems every time I'm working with a new client and in
different accounts we go through this ritual: if you can't logto some
account, try the full path. Same goes for cataloging code in one account
where the object is in another: can't run the code - oops, the account name
needs to be the full path.
It would be nice to have some rules of thumb like : all accounts created
through UniAdmin can be referenced via account name only, or all Pick
flavor accounts created from the command prompt don't have a Ux.ACCOUNT
entry but creating one will always work...
Humble ignorance and gratitude,
Tony
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
