You don't really want to clear all common variables all the time. Some common variables are actually universal.
Take for example that you store in common the say.... full name of the user who is logged in, and their extension. That doesn't change on a logto. Some people use things like that in a LOCKED clause to say "John Brown has this locked, call him on extension 7204" so the users don't have to call the help desk on locks, they can peer to peer it. Sure you can reread things like that. It's half white half black. Do I clear half the common ? Or reread half the common? -----Original Message----- From: David A. Green <[email protected]> To: 'U2 Users List' <[email protected]> Sent: Thu, Apr 12, 2012 4:44 pm Subject: Re: [U2] COMMON Size MisMatch While this topic is on the table, can we request some kind of COMMON flag or ommand that would tell the DBM to clear commons on a LOGTO? David A. Green 480) 813-1725 AG Consulting -----Original Message----- rom: [email protected] mailto:[email protected]] On Behalf Of Bill Brutzman ent: Thursday, April 12, 2012 2:22 PM o: U2 Users List ubject: Re: [U2] COMMON Size MisMatch Will: Your commentary on this matter is very much appreciated. As long as this new fix works... I expect to defer further investigation. --Bill -----Original Message----- rom: [email protected] mailto:[email protected]] On Behalf Of Wjhonson ent: Thursday, April 12, 2012 4:56 PM o: [email protected] ubject: Re: [U2] COMMON Size MisMatch ook inside those routines, and determine that they are agnostic about you oming from LOGIN vs LOGTO Perhaps I'm the sole person in history to have oded things that are wise about the distinction ----Original Message----- rom: Bill Brutzman <[email protected]> o: U2 Users List <[email protected]> ent: Thu, Apr 12, 2012 12:46 pm ubject: Re: [U2] COMMON Size MisMatch presume that the following is workable... Comments are welcome. o LogTo the SandBox it is now just... ED VOC LLS 01: PA 02: CLEARCOMMON 03: LOGTO SANDBOX 04: WHO ED VOC LOGIN 01: PA 03: PTERM -ECHO DELAY 05: BREAK ON 07: CLEARCOMMON 09: HK.RESET.PRINTER 11: RUN MT.BP GET.STACK.LOGNAME 13: LOGIN.CONTROL 15: PTERM CASE NOINVERT 16: RUN B.USER TERMINAL.SETUP.R0 18: IF @LOGNAME = 'root' THEN GO TCL 19: IF @LOGNAME = 'brutzy' THEN GO TCL 20: IF @LOGNAME = 'raymond' THEN GO TCL 22: MM 24: TCL: ttom at line 24. -Bill ----Original Message----- om: [email protected] mailto:[email protected]] Behalf Of Wjhonson nt: Thursday, April 12, 2012 3:08 PM : [email protected] bject: Re: [U2] COMMON Size MisMatch f you *do* use CLEARCOMMON you have to be alert to gremlins as well. GTO is not expecting to have to reinitialize the system and so probably esn't. u need to review what the Login process is doing as well. u may end up wiping out control information such as the user's port, name, gin time, functions they can and can't do, menu access, default printer, nd o on and so forth. ll depends on how complex the login processor has become at your site. me sites don't do a darn thing. Some have thousands of lines of code at gin. Some of which set common (read "environment") variables, that you don't nt* to clear, or at least that you want to reset if you do clear them. ----Original Message----- om: Bill Brutzman <[email protected]> : U2 Users List <[email protected]> nt: Thu, Apr 12, 2012 11:52 am bject: Re: [U2] COMMON Size MisMatch ating my own dog food... I cranked CLEARCOMMON into the LOGTO SandBox and GTO LIVE paragraph commands. Bill om: u2-users-bounces at listserver.u2ug.org mailto:u2-users-bounces at stserver.u2ug.org] On Behalf Of on_Bausili at hcsc.net t: Thursday, July 16, 2009 10:17 AM u2-users at listserver.u2ug.org ject: [U2] Fw: COMMON misMatch nce all common variables are cleared when you exit UniVerse, and liminates he rror, is it possible your user used a LOGTO command to witch nvironments that ave different versions of the subroutine OP.R87? had both a Test and a Prod environment on the same box, and xperienced oblems when enhanced code in Test was being staged for romotion into Prod. xecuting a program in Test that had changes to ts COMMON, and then logging nto rod resulted in the size mismatch rror when running the unchanged rogram. r solution was to insert "CLEARCOMMON" in the LOGIN paragraphs. n -- Forwarded by Don Bausili/OK/HCSC on 07/16/2009 09:09 AM ----- "Brutzman, ll" <BillB at hkMetalCraft.com> Sent by: users-bounces at listserver.u2ug.org 15/2009 06:55 PM ase respond to Users List" <u2-users at listserver.u2ug.org> o Users List" <u2-users at listserver.u2ug.org> c Subject [U2] COMMON misMatch A user here obtained an error message... "COMMON size mismatch in subroutine "HOP.R87". on logging out and then logging back in again... The HOP program was ble to unch without this error. lp with a diagnosis and more reliable cure would be appreciated. is user is WinXP / Dynamic Connect / UniVerse 10.1 / HP-Ux 11i v2. Bill _____________________________________________ Users mailing list Users at listserver.u2ug.org p://listserver.u2ug.org/mailman/listinfo/u2-users e information contained in this communication is confidential, rivate, prietary, or otherwise privileged and is intended only for the use of he dressee. Unauthorized use, disclosure, distribution or copying is trictly ohibited and may be unlawful. If you have received this ommunication in ror, please notify the sender immediately at (312) -6000 in Illinois; (800)835-8699 in New Mexico; (918)560-3500 in klahoma; r 72)766-6900 in Texas. ____________________________________________ Users mailing list Users at listserver.u2ug.org p://listserver.u2ug.org/mailman/listinfo/u2-users vious message: [U2] Fw: COMMON misMatch ext message: [U2] Universe Retrieve sages sorted by: [ date ] [ thread ] [ subject ] [ author ] ore information out the U2-Users -----Original Message----- m: [email protected] mailto:[email protected]] Behalf Of Bill Brutzman t: Thursday, April 12, 2012 2:40 PM U2 Users List ject: [U2] COMMON Size MisMatch . in subroutine named XYZ.R1. ile I would like to pass parameters back-and-forth invoking bona fide xternal broutines using commands such as... CALL *MY.SUB.R2(param1, param2, orString) .I have a few big old legacy programs with nasty COMMON tentacles. w can I make these pesky COMMON messages go away? Bill ____________________________________________ Users mailing list [email protected] p://listserver.u2ug.org/mailman/listinfo/u2-users ____________________________________________ Users mailing list [email protected] p://listserver.u2ug.org/mailman/listinfo/u2-users ______________________________________________ -Users mailing list [email protected] tp://listserver.u2ug.org/mailman/listinfo/u2-users _____________________________________________ -Users mailing list [email protected] tp://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ 2-Users mailing list [email protected] ttp://listserver.u2ug.org/mailman/listinfo/u2-users ______________________________________________ 2-Users mailing list [email protected] ttp://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ 2-Users mailing list [email protected] ttp://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
