Never had a command stack big enough to cause problems. Since it's being called from the Unix command line could you not simply clear the stack prior to running the command? Or you could set the CSTACKSZ environment variable for this user so it won't get so big.
We have a directory under UniData home called cmdstack and it puts all of the stacks in there so they work across all accounts. Not exactly sure how it was setup. Hth Colin Alfke Calgary, Canada >-----Original Message----- >From: Raymond DeGennaro II > >We've got a customer site that is having problems with one >user ID always getting core dumps as soon as they start >UniData. This even happens in a brand new, nothing but what >'newacct' puts in it, account. > >They're pretty convinced that it's due to the contents of the >.Command stack getting too large, because when they delete the >stack, the problem goes away for a while. The problem login >us used non-interactively to call UDT from the Unix command >line, often with @SENTENCE data approaching MAXSENTENCE in length. > >I've never seen another site core dump due to large command >stacks and I've never seen the command stack follow a user ID >from account to account. Needless to say, I'm more than a bit stumped. > >Ray ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
