Or nicer to have a different name to COMMON e.g. SESSION /CLEAR_THIS/ SESSION_STUFF(SMALL) COMMON /KEEP_THIS/ COMMON_STUFF(BIG)
Or something along those lines. Brian -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of David A. Green Sent: 13 April 2012 15:56 To: 'U2 Users List' Subject: Re: [U2] COMMON Size MisMatch That's why you would specify. Example: COMMON /SYSSTUFF/ SYSSTUFF(100) COMMON /MYSTUFF/ MYSTUFF.REC(100) -CLEAR.ON.LOGTO Then only the MYSTUFF gets cleared. This is the kind of logic that I have to end up writing over and over again to make sure new files get opened when a person does LOGTO to a different account. Programmers would make all their Account specific data into a single named common that has the flag to initialize on LOGTO. And keep other cross-account data in common that isn't flagged. Easy. David A. Green (480) 813-1725 DAG Consulting -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Wjhonson Sent: Thursday, April 12, 2012 4:56 PM To: [email protected] Subject: Re: [U2] COMMON Size MisMatch Okay that was a bad example..... But I think you get my general drift. There are some common variables that are truly universal and should persist. -----Original Message----- From: Wjhonson <[email protected]> To: u2-users <[email protected]> Sent: Thu, Apr 12, 2012 4:49 pm Subject: Re: [U2] COMMON Size MisMatch ou don't really want to clear all common variables all the time. ome common variables are actually universal. Take for example that you store in common the say.... full name of the user who s logged in, and their extension. hat doesn't change on a logto. Some people use things like that in a LOCKED lause to say "John Brown has this locked, call him on extension 7204" so the sers 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. o I clear half the common ? Or reread half the common? -----Original Message----- rom: David A. Green <[email protected]> o: 'U2 Users List' <[email protected]> ent: Thu, Apr 12, 2012 4:44 pm ubject: Re: [U2] COMMON Size MisMatch hile this topic is on the table, can we request some kind of COMMON flag or mmand that would tell the DBM to clear commons on a LOGTO? avid A. Green 80) 813-1725 G Consulting ----Original Message----- om: [email protected] ailto:[email protected]] On Behalf Of Bill Brutzman nt: Thursday, April 12, 2012 2:22 PM : U2 Users List bject: Re: [U2] COMMON Size MisMatch ill: our commentary on this matter is very much appreciated. s long as this new fix works... I expect to defer further investigation. -Bill ----Original Message----- om: [email protected] ailto:[email protected]] On Behalf Of Wjhonson nt: Thursday, April 12, 2012 4:56 PM : [email protected] bject: Re: [U2] COMMON Size MisMatch ook inside those routines, and determine that they are agnostic about you ming from LOGIN vs LOGTO Perhaps I'm the sole person in history to have ded things that are wise about the distinction ---Original Message----- om: Bill Brutzman <[email protected]> : U2 Users List <[email protected]> nt: Thu, Apr 12, 2012 12:46 pm bject: Re: [U2] COMMON Size MisMatch presume that the following is workable... Comments are welcome. LogTo the SandBox it is now just... D VOC LLS 1: PA 2: CLEARCOMMON 3: LOGTO SANDBOX 4: WHO D VOC LOGIN 1: PA 3: PTERM -ECHO DELAY 5: BREAK ON 7: CLEARCOMMON 9: HK.RESET.PRINTER 1: RUN MT.BP GET.STACK.LOGNAME 3: LOGIN.CONTROL 5: PTERM CASE NOINVERT 6: RUN B.USER TERMINAL.SETUP.R0 8: IF @LOGNAME = 'root' THEN GO TCL 9: IF @LOGNAME = 'brutzy' THEN GO TCL 0: IF @LOGNAME = 'raymond' THEN GO TCL 2: MM 4: TCL: tom at line 24. Bill ---Original Message----- m: [email protected] ailto:[email protected]] Behalf Of Wjhonson t: Thursday, April 12, 2012 3:08 PM [email protected] ject: Re: [U2] COMMON Size MisMatch you *do* use CLEARCOMMON you have to be alert to gremlins as well. TO is not expecting to have to reinitialize the system and so probably sn't. need to review what the Login process is doing as well. may end up wiping out control information such as the user's port, name, in time, functions they can and can't do, menu access, default printer, d o on and so forth. l depends on how complex the login processor has become at your site. e sites don't do a darn thing. Some have thousands of lines of code at in. Some of which set common (read "environment") variables, that you on't t* to clear, or at least that you want to reset if you do clear them. ----Original Message----- m: Bill Brutzman <[email protected]> U2 Users List <[email protected]> t: Thu, Apr 12, 2012 11:52 am ject: Re: [U2] COMMON Size MisMatch ting my own dog food... I cranked CLEARCOMMON into the LOGTO SandBox and TO LIVE paragraph commands. ill m: u2-users-bounces at listserver.u2ug.org mailto:u2-users-bounces at tserver.u2ug.org] On Behalf Of on_Bausili at hcsc.net : Thursday, July 16, 2009 10:17 AM u2-users at listserver.u2ug.org ect: [U2] Fw: COMMON misMatch ce all common variables are cleared when you exit UniVerse, and liminates e rror, is it possible your user used a LOGTO command to witch vironments that ave different versions of the subroutine OP.R87? had both a Test and a Prod environment on the same box, and xperienced blems when enhanced code in Test was being staged for romotion into Prod. ecuting a program in Test that had changes to ts COMMON, and then logging to rod resulted in the size mismatch rror when running the unchanged ogram. solution was to insert "CLEARCOMMON" in the LOGIN paragraphs. - Forwarded by Don Bausili/OK/HCSC on 07/16/2009 09:09 AM ----- "Brutzman, l" <BillB at hkMetalCraft.com> Sent by: sers-bounces at listserver.u2ug.org 5/2009 06:55 PM se respond to Users List" <u2-users at listserver.u2ug.org> o Users List" <u2-users at listserver.u2ug.org> c Subject [U2] COMMON misMatch user here obtained an error message... "COMMON size mismatch in subroutine "HOP.R87". n logging out and then logging back in again... The HOP program was ble to nch without this error. p with a diagnosis and more reliable cure would be appreciated. s user is WinXP / Dynamic Connect / UniVerse 10.1 / HP-Ux 11i v2. ill ____________________________________________ sers mailing list sers at listserver.u2ug.org ://listserver.u2ug.org/mailman/listinfo/u2-users information contained in this communication is confidential, rivate, rietary, or otherwise privileged and is intended only for the use of he ressee. Unauthorized use, disclosure, distribution or copying is trictly hibited and may be unlawful. If you have received this ommunication in or, please notify the sender immediately at (312) 6000 in Illinois; (800)835-8699 in New Mexico; (918)560-3500 in klahoma; 2)766-6900 in Texas. ___________________________________________ sers mailing list sers at listserver.u2ug.org ://listserver.u2ug.org/mailman/listinfo/u2-users ious message: [U2] Fw: COMMON misMatch ext message: [U2] Universe Retrieve ages sorted by: [ date ] [ thread ] [ subject ] [ author ] ore information ut the U2-Users -----Original Message----- : [email protected] ailto:[email protected]] ehalf Of Bill Brutzman : Thursday, April 12, 2012 2:40 PM U2 Users List ect: [U2] COMMON Size MisMatch in subroutine named XYZ.R1. le I would like to pass parameters back-and-forth invoking bona fide ternal broutines using commands such as... CALL *MY.SUB.R2(param1, param2, rString) I have a few big old legacy programs with nasty COMMON tentacles. can I make these pesky COMMON messages go away? ill ___________________________________________ sers mailing list [email protected] ://listserver.u2ug.org/mailman/listinfo/u2-users ___________________________________________ sers mailing list [email protected] ://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] 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 ______________________________________________ -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 _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
