Re: SYSTEM(14) with D3

Luke:

"Luke Webber" <luke@xxxxxxxxxxxxx> wrote in message ...

Bill H wrote:

It seems there's plenty of room for confusion regarding what is the
standard behavior one should expect with "named common" in an MV system.
From just my perspective, I'd have thought named common __SHOULD__ be
retained during a logto. I say this because in a web environment there's
often some program running awaiting INPUT from a web server. When data
comes in, the program will usually logto another account and run some
command passed by the web server. Once complete, the polling program
will return back to the original account and pass the data back. It
seems a much easier architecture if most variables can be passed back and
forth via "named common".

Really? That seems utterly counter-intuitive to me. Logging back and forth
implies that you have to relinquish program control and start again in a
whole new program, which means that you lose the passed parameters. Unless
you store them in a file somewhere and read them in again. Or something
similar. That's, well, kinda nasty.

UniData even has things like STACKCOMMON and DELETECOMMON. These manipulate
the named common under program execution. So, there's even more to this
discussion than either of us realize. :-)

Anyway, just a few thoughts.

Sorry if I've misunderstood. I'm no UDT afficianado. In fact, I've always
loathed UDT above all other implementations. Possibly you know some tricks
that make my points meaningless.

So do most people. However, I doubt I know any tricks, just fishy
"work-arounds". :-)

Bill


.

Relevant Pages

  • Re: SYSTEM(14) with D3
    ... paragraph isn't executed when one logs to another account. ... However, the standard behavior is to execute the "LOGIN" paragraph so one, ... paragraph when doing a "LOGTO". ... behavior one should expect with "named common" in an MV system. ...
    (comp.databases.pick)
  • Re: SYSTEM(14) with D3
    ... Unfortunately, the documentation ... is weak here and should have been explicit regarding LOGTO. ... place today for NAMED COMMON, I doubt few would "re-read" how NAMED ... something and LOGTO back to the original account. ...
    (comp.databases.pick)
  • Re: SYSTEM(14) with D3
    ... If named Common does not clear on LOGTO, ... 2- But if I want to LOGTO an account to perform certain functions, ... If named common clears on LOGTO, you're limited from doing the above. ... Now I am more confused by Chandru's comment as I always use the Login proc ...
    (comp.databases.pick)
  • Re: SYSTEM(14) with D3
    ... I'm betting that 95% of programmers would choose not to have their named common persist across a LOGTO. ... Did you consider that LOGTO doesn't even necessarily appear on the radar when a programmer writes his/her code? ... It DOES NOT logoff. ... everything about your profession, I'll eat this keyboard. ...
    (comp.databases.pick)
  • Re: SYSTEM(14) with D3
    ... Chandru, btw... ... is weak here and should have been explicit regarding LOGTO. ... place today for NAMED COMMON, I doubt few would "re-read" how NAMED ... something and LOGTO back to the original account. ...
    (comp.databases.pick)