[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

585.0. "OAUSER incorrectly defined for a user..." by TAV02::CHAIM (Semper ubi Sub ubi .....) Tue Apr 28 1992 13:30

I just encountered a very strange problem:

The customer has all the accounts as restricted and these accounts access
ALL-IN-1 from within a menu routine which they wrote. This routine activates a
command procedure which issues a normal ALLIN1 command.

All the users with the exception of one user have no problem accessing
ALL-IN-1. 

This one particular user receives "Error opening file cabinet" when accessing
ALL-IN-1 via the routine. If the user does a $SHO LOG OAUSER at this point it
points to the same directory as sys$login and NOT the user's A1 directory. 

If the RESTRICTED flag is removed and the user accesses ALL-IN-1 from DCL then
everything is fine and OAUSER correctly points to the user's A1 directory.

Does anyone have any idea what might be causing this strange behavior?

Thanks,

Cb.
T.RTitleUserPersonal
Name
DateLines
585.1Insufficient Dynamic Memory ...TAV02::CHAIMSemper ubi Sub ubi .....Wed Apr 29 1992 09:5119
We got to the bottom of this problem after MANY MANY hours (both ours and the
customers) of investigation.

This particular user had an extraordinary large number of process logical names
defined and at some point the dynamic memory was ALMOST exhausted, leaving
enough for image activation, but that's about all. 

At some point during the actual initialization which ALL-IN-1 does, the dynamic
memory DID become exhausted. Unfortunately ALL-IN-1 does NOT give any error
message for this. Obviously, the initialization did not complete successfully
and thus the process is left with either undefined or incorrectly defined
logicals. At this point the error messages that are given are absolutely
meaningless at best and totally misleading at worst.

I believe the customer wants to SPR this.

Thanks,

Cb.