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: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson Sent: Thursday, April 12, 2012 4:56 PM To: u2-users@listserver.u2ug.org 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 wjhon...@aol.com To: u2-users u2-users@listserver.u2ug.org 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 dgr...@dagconsulting.com o: 'U2 Users List' u2-users@listserver.u2ug.org 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: u2-users-boun...@listserver.u2ug.org ailto:u2-users-boun...@listserver.u2ug.org] 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: u2-users-boun...@listserver.u2ug.org ailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson nt: Thursday, April 12, 2012 4:56 PM : u2-users@listserver.u2ug.org 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 bi...@hkmetalcraft.com : U2 Users List u2-users@listserver.u2ug.org 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: u2-users-boun...@listserver.u2ug.org ailto:u2-users-boun...@listserver.u2ug.org] Behalf Of Wjhonson t: Thursday, April 12, 2012 3:08 PM u2-users@listserver.u2ug.org 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 bi...@hkmetalcraft.com U2 Users List u2-users@listserver.u2ug.org 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
Re: [U2] COMMON Size MisMatch
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: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] 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: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson Sent: Thursday, April 12, 2012 4:56 PM To: u2-users@listserver.u2ug.org 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 wjhon...@aol.com To: u2-users u2-users@listserver.u2ug.org 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 dgr...@dagconsulting.com o: 'U2 Users List' u2-users@listserver.u2ug.org 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: u2-users-boun...@listserver.u2ug.org ailto:u2-users-boun...@listserver.u2ug.org] 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: u2-users-boun...@listserver.u2ug.org ailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson nt: Thursday, April 12, 2012 4:56 PM : u2-users@listserver.u2ug.org 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 bi...@hkmetalcraft.com : U2 Users List u2-users@listserver.u2ug.org 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: u2-users-boun...@listserver.u2ug.org ailto:u2-users-boun...@listserver.u2ug.org] Behalf Of Wjhonson t: Thursday, April 12, 2012 3:08 PM u2-users@listserver.u2ug.org 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 bi...@hkmetalcraft.com U2 Users List u2-users@listserver.u2ug.org t: Thu, Apr 12, 2012 11:52 am ject: Re: [U2
Re: [U2] COMMON Size MisMatch
Brian: The syntax described here must be UniVerse specific. I don't see anything like this in UniData. :-( Bill - Original Message - *From:* br...@brianleach.co.uk *To:* 'U2 Users List' u2-users@listserver.u2ug.org *Date:* 4/13/2012 8:34 AM *Subject:* Re: [U2] COMMON Size MisMatch 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: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] 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: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson Sent: Thursday, April 12, 2012 4:56 PM To: u2-users@listserver.u2ug.org 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: Wjhonsonwjhon...@aol.com To: u2-usersu2-users@listserver.u2ug.org 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. Greendgr...@dagconsulting.com o: 'U2 Users List'u2-users@listserver.u2ug.org 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: u2-users-boun...@listserver.u2ug.org ailto:u2-users-boun...@listserver.u2ug.org] 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: u2-users-boun...@listserver.u2ug.org ailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson nt: Thursday, April 12, 2012 4:56 PM : u2-users@listserver.u2ug.org 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 Brutzmanbi...@hkmetalcraft.com : U2 Users Listu2-users@listserver.u2ug.org 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: u2-users-boun...@listserver.u2ug.org ailto:u2-users-boun...@listserver.u2ug.org] Behalf Of Wjhonson t: Thursday, April 12, 2012 3:08 PM u2-users@listserver.u2ug.org 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
Re: [U2] COMMON Size MisMatch
I can't anything called CLEAR.ON.LOGTO which it seems you are implying is some kind of option. I do agree with Brian that it would be nice, for just this issue if we could have UCOMMON /STUFF1/ USER.NAME, USER.PHONE, LOGIN.DATE, UPARAMETERS(100) ... COMMON /FILES/ FILE.NAMES, FILE.POINTERS(100), OTHER.STUFF(200) COMMON /STUFF2/ MORE.OTHER.STUFF(200) And then have UCOMMON persists across LOGTOs while COMMON does not UCLEARCOMMON will clear both universal, and local common, while CLEARCOMMON will only clear COMMON Rocket won't hire me as a systems programmer because I keep finding things to fix. Will Johnson -Original Message- From: David A. Green dgr...@dagconsulting.com To: 'U2 Users List' u2-users@listserver.u2ug.org Sent: Fri, Apr 13, 2012 7:56 am 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 o end up writing over and over again to make sure new files get opened when person does LOGTO to a different account. Programmers would make all their Account specific data into a single named ommon that has the flag to initialize on LOGTO. And keep other ross-account data in common that isn't flagged. Easy. David A. Green 480) 813-1725 AG Consulting -Original Message- rom: u2-users-boun...@listserver.u2ug.org mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson ent: Thursday, April 12, 2012 4:56 PM o: u2-users@listserver.u2ug.org ubject: Re: [U2] COMMON Size MisMatch kay that was a bad example. ut I think you get my general drift. here are some common variables that are truly universal and should persist. -Original Message- rom: Wjhonson wjhon...@aol.com o: u2-users u2-users@listserver.u2ug.org ent: Thu, Apr 12, 2012 4:49 pm ubject: Re: [U2] COMMON Size MisMatch ou don't really want to clear all common variables all the time. me common variables are actually universal. ake for example that you store in common the say full name of the user ho s logged in, and their extension. at doesn't change on a logto. Some people use things like that in a LOCKED ause to say John Brown has this locked, call him on extension 7204 so he sers don't have to call the help desk on locks, they can peer to peer t. ure you can reread things like that. It's half white half black. I clear half the common ? Or reread half the common? -Original Message- om: David A. Green dgr...@dagconsulting.com : 'U2 Users List' u2-users@listserver.u2ug.org nt: Thu, Apr 12, 2012 4:44 pm bject: Re: [U2] COMMON Size MisMatch hile this topic is on the table, can we request some kind of COMMON flag or mand that would tell the DBM to clear commons on a LOGTO? vid A. Green 0) 813-1725 Consulting ---Original Message- m: u2-users-boun...@listserver.u2ug.org ilto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Brutzman t: Thursday, April 12, 2012 2:22 PM U2 Users List ject: Re: [U2] COMMON Size MisMatch ll: ur commentary on this matter is very much appreciated. long as this new fix works... I expect to defer further investigation. Bill ---Original Message- m: u2-users-boun...@listserver.u2ug.org ilto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson t: Thursday, April 12, 2012 4:56 PM u2-users@listserver.u2ug.org ject: Re: [U2] COMMON Size MisMatch ok inside those routines, and determine that they are agnostic about you ing from LOGIN vs LOGTO Perhaps I'm the sole person in history to have ded hings that are wise about the distinction ---Original Message- m: Bill Brutzman bi...@hkmetalcraft.com U2 Users List u2-users@listserver.u2ug.org t: Thu, Apr 12, 2012 12:46 pm ject: Re: [U2] COMMON Size MisMatch presume that the following is workable... Comments are welcome. LogTo the SandBox it is now just... VOC LLS : PA : CLEARCOMMON : LOGTO SANDBOX : WHO VOC LOGIN : PA : PTERM -ECHO DELAY : BREAK ON : CLEARCOMMON : HK.RESET.PRINTER : RUN MT.BP GET.STACK.LOGNAME : LOGIN.CONTROL : PTERM CASE NOINVERT : RUN B.USER TERMINAL.SETUP.R0 : IF @LOGNAME = 'root'THEN GO TCL : IF @LOGNAME = 'brutzy' THEN GO TCL : IF @LOGNAME = 'raymond' THEN GO TCL : MM : TCL: om at line 24. ill --Original Message- : u2-users-boun...@listserver.u2ug.org ilto:u2-users-boun...@listserver.u2ug.org] ehalf Of Wjhonson : Thursday, April 12, 2012 3:08 PM u2-users@listserver.u2ug.org ect: Re: [U2] COMMON Size MisMatch you *do* use CLEARCOMMON you have to be alert to gremlins as well. O 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 ime, functions they can and can't do, menu access, default printer, d o on nd so forth. depends on how complex the login processor has become at your site. sites don't do a darn thing. Some have thousands
Re: [U2] COMMON Size MisMatch
On 13/04/12 15:56, David A. Green wrote: 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. Actually, that IS easy. TODAY. Let's say you want to store a filepointer to VOC in common, you create the following INCLUDE file... COMMON /VOC/ F.VOC, D.VOC, VOC.OPEN IF VOC.OPEN NE @WHO THEN VOC.OPEN = @WHO OPEN , VOC TO F.VOC ... OPEN DICT, VOC TO D.VOC ... END I hope I've got the right @variable, but as soon as you LOGTO, the IF goes false, and next to you try access it, it will re-initialise itself. Cheers, Wol (Moderator moan - I've just snipped an AWFUL lot of text ...) ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] COMMON Size MisMatch
Include file? You mean in every program? Or you mean modify the LOGIN process to add this I would suggest that you do something like IF VOC.OPEN NE @WHO THEN CALL RESET.ALL.OPEN.FILE.POINTERS since you may have pointers to lots of files, not just VOC -Original Message- From: Wols Lists antli...@youngman.org.uk To: u2-users u2-users@listserver.u2ug.org Sent: Fri, Apr 13, 2012 11:05 am Subject: Re: [U2] COMMON Size MisMatch On 13/04/12 15:56, David A. Green wrote: 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. Actually, that IS easy. TODAY. Let's say you want to store a filepointer o VOC in common, you create the following INCLUDE file... COMMON /VOC/ F.VOC, D.VOC, VOC.OPEN F VOC.OPEN NE @WHO THEN VOC.OPEN = @WHO OPEN , VOC TO F.VOC ... OPEN DICT, VOC TO D.VOC ... ND I hope I've got the right @variable, but as soon as you LOGTO, the IF oes false, and next to you try access it, it will re-initialise itself. Cheers, ol (Moderator moan - I've just snipped an AWFUL lot of text ...) __ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] COMMON Size MisMatch
Yes, but why make all the programmers in the world repeat this same code over and over? It could easily be accomplished by the database engine. It could be a new keyword across MV database systems. And another step in bring the MV worlds closer together. David A. Green (480) 813-1725 DAG Consulting -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wols Lists Sent: Friday, April 13, 2012 11:00 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] COMMON Size MisMatch On 13/04/12 15:56, David A. Green wrote: 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. Actually, that IS easy. TODAY. Let's say you want to store a filepointer to VOC in common, you create the following INCLUDE file... COMMON /VOC/ F.VOC, D.VOC, VOC.OPEN IF VOC.OPEN NE @WHO THEN VOC.OPEN = @WHO OPEN , VOC TO F.VOC ... OPEN DICT, VOC TO D.VOC ... END I hope I've got the right @variable, but as soon as you LOGTO, the IF goes false, and next to you try access it, it will re-initialise itself. Cheers, Wol (Moderator moan - I've just snipped an AWFUL lot of text ...) ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] COMMON Size MisMatch
Hi all, As a possible suggestion for how this could be implemented, we have a couple of features in QM that together do the job. 1. The ON.LOGTO paragraph. If present, this runs as part of a LOGTO command, before leaving the old account. 2. The DELETE.COMMON command. This deletes the specified named common. Called from ON.LOGTO, the task becomes trivial. Perhaps U2 could do the same? Martin Phillips Ladybridge Systems Ltd 17b Coldstream Lane, Hardingstone, Northampton NN4 6DB, England +44 (0)1604-709200 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] COMMON Size MisMatch
Sounds good Martin. Maybe someone named Will could code this up in Universe BASIC and post it to the PickWiki. Oops... why did I say that. -Original Message- From: Martin Phillips martinphill...@ladybridge.com To: 'U2 Users List' u2-users@listserver.u2ug.org Sent: Fri, Apr 13, 2012 11:50 am Subject: Re: [U2] COMMON Size MisMatch Hi all, As a possible suggestion for how this could be implemented, we have a couple of eatures in QM that together do the job. 1. The ON.LOGTO paragraph. f present, this runs as part of a LOGTO command, before leaving the old ccount. 2. The DELETE.COMMON command. his deletes the specified named common. Called from ON.LOGTO, the task becomes rivial. Perhaps U2 could do the same? artin Phillips adybridge Systems Ltd 7b Coldstream Lane, Hardingstone, Northampton NN4 6DB, England 44 (0)1604-709200 __ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
[U2] COMMON Size MisMatch
... in subroutine named XYZ.R1. While I would like to pass parameters back-and-forth invoking bona fide external subroutines using commands such as... CALL *MY.SUB.R2(param1, param2, errorString) ...I have a few big old legacy programs with nasty COMMON tentacles. How can I make these pesky COMMON messages go away? --Bill ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] COMMON Size MisMatch
Eating my own dog food... I cranked CLEARCOMMON into the LOGTO SandBox and LOGTO LIVE paragraph commands. --Bill From: u2-users-bounces at listserver.u2ug.org [mailto:u2-users-bounces at listserver.u2ug.org] On Behalf Of Don_Bausili at hcsc.net Sent: Thursday, July 16, 2009 10:17 AM To: u2-users at listserver.u2ug.org Subject: [U2] Fw: COMMON misMatch Since all common variables are cleared when you exit UniVerse, and eliminates the error, is it possible your user used a LOGTO command to switch environments that have different versions of the subroutine HOP.R87? We had both a Test and a Prod environment on the same box, and experienced problems when enhanced code in Test was being staged for promotion into Prod. Executing a program in Test that had changes to its COMMON, and then logging into Prod resulted in the size mismatch error when running the unchanged program. Our solution was to insert CLEARCOMMON in the LOGIN paragraphs. Don - Forwarded by Don Bausili/OK/HCSC on 07/16/2009 09:09 AM - Brutzman, Bill BillB at hkMetalCraft.com Sent by: u2-users-bounces at listserver.u2ug.org 07/15/2009 06:55 PM Please respond to U2 Users List u2-users at listserver.u2ug.org To U2 Users List u2-users at listserver.u2ug.org cc Subject Re: [U2] COMMON misMatch A user here obtained an error message... COMMON size mismatch in subroutine HOP.R87. Upon logging out and then logging back in again... The HOP program was able to launch without this error. Help with a diagnosis and more reliable cure would be appreciated. This user is WinXP / Dynamic Connect / UniVerse 10.1 / HP-Ux 11i v2. --Bill ___ U2-Users mailing list U2-Users at listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users The information contained in this communication is confidential, private, proprietary, or otherwise privileged and is intended only for the use of the addressee. Unauthorized use, disclosure, distribution or copying is strictly prohibited and may be unlawful. If you have received this communication in error, please notify the sender immediately at (312) 653-6000 in Illinois; (800)835-8699 in New Mexico; (918)560-3500 in Oklahoma; or (972)766-6900 in Texas. ___ U2-Users mailing list U2-Users at listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users Previous message: [U2] Fw: COMMON misMatch Next message: [U2] Universe Retrieve Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the U2-Users -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Brutzman Sent: Thursday, April 12, 2012 2:40 PM To: U2 Users List Subject: [U2] COMMON Size MisMatch ... in subroutine named XYZ.R1. While I would like to pass parameters back-and-forth invoking bona fide external subroutines using commands such as... CALL *MY.SUB.R2(param1, param2, errorString) ...I have a few big old legacy programs with nasty COMMON tentacles. How can I make these pesky COMMON messages go away? --Bill ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] COMMON Size MisMatch
If you *do* use CLEARCOMMON you have to be alert to gremlins as well. LOGTO is not expecting to have to reinitialize the system and so probably doesn't. You need to review what the Login process is doing as well. You may end up wiping out control information such as the user's port, name, login time, functions they can and can't do, menu access, default printer, and so on and so forth. All depends on how complex the login processor has become at your site. Some sites don't do a darn thing. Some have thousands of lines of code at Login. Some of which set common (read environment) variables, that you *don't want* to clear, or at least that you want to reset if you do clear them. -Original Message- From: Bill Brutzman bi...@hkmetalcraft.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Thu, Apr 12, 2012 11:52 am Subject: Re: [U2] COMMON Size MisMatch Eating my own dog food... I cranked CLEARCOMMON into the LOGTO SandBox and OGTO LIVE paragraph commands. --Bill From: u2-users-bounces at listserver.u2ug.org mailto:u2-users-bounces at listserver.u2ug.org] On Behalf Of on_Bausili at hcsc.net ent: Thursday, July 16, 2009 10:17 AM o: u2-users at listserver.u2ug.org ubject: [U2] Fw: COMMON misMatch Since all common variables are cleared when you exit UniVerse, and liminates the error, is it possible your user used a LOGTO command to witch environments that have different versions of the subroutine OP.R87? We had both a Test and a Prod environment on the same box, and xperienced problems when enhanced code in Test was being staged for romotion into Prod. Executing a program in Test that had changes to ts COMMON, and then logging into Prod resulted in the size mismatch rror when running the unchanged program. Our solution was to insert CLEARCOMMON in the LOGIN paragraphs. Don Forwarded by Don Bausili/OK/HCSC on 07/16/2009 09:09 AM - Brutzman, Bill BillB at hkMetalCraft.com Sent by: 2-users-bounces at listserver.u2ug.org 7/15/2009 06:55 PM lease respond to U2 Users List u2-users at listserver.u2ug.org o U2 Users List u2-users at listserver.u2ug.org c Subject e: [U2] COMMON misMatch A user here obtained an error message... COMMON size mismatch in subroutine HOP.R87. Upon logging out and then logging back in again... The HOP program was ble to launch without this error. Help with a diagnosis and more reliable cure would be appreciated. This user is WinXP / Dynamic Connect / UniVerse 10.1 / HP-Ux 11i v2. --Bill ___ 2-Users mailing list 2-Users at listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users The information contained in this communication is confidential, rivate, roprietary, or otherwise privileged and is intended only for the use of he addressee. Unauthorized use, disclosure, distribution or copying is trictly prohibited and may be unlawful. If you have received this ommunication in error, please notify the sender immediately at (312) 53-6000 in Illinois; (800)835-8699 in New Mexico; (918)560-3500 in klahoma; or (972)766-6900 in Texas. __ 2-Users mailing list 2-Users at listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users revious message: [U2] Fw: COMMON misMatch ext message: [U2] Universe Retrieve essages sorted by: [ date ] [ thread ] [ subject ] [ author ] ore information about the U2-Users -Original Message- rom: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] n Behalf Of Bill Brutzman ent: Thursday, April 12, 2012 2:40 PM o: U2 Users List ubject: [U2] COMMON Size MisMatch ... in subroutine named XYZ.R1. While I would like to pass parameters back-and-forth invoking bona fide external ubroutines using commands such as... CALL *MY.SUB.R2(param1, param2, rrorString) ...I have a few big old legacy programs with nasty COMMON tentacles. How can I make these pesky COMMON messages go away? --Bill __ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users __ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] COMMON Size MisMatch
Do you need to use LOGTO.ABORT perhaps instead of LOGTO? -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson Sent: Thursday, April 12, 2012 1:08 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] COMMON Size MisMatch If you *do* use CLEARCOMMON you have to be alert to gremlins as well. LOGTO is not expecting to have to reinitialize the system and so probably doesn't. You need to review what the Login process is doing as well. You may end up wiping out control information such as the user's port, name, login time, functions they can and can't do, menu access, default printer, and so on and so forth. All depends on how complex the login processor has become at your site. Some sites don't do a darn thing. Some have thousands of lines of code at Login. Some of which set common (read environment) variables, that you *don't want* to clear, or at least that you want to reset if you do clear them. -Original Message- From: Bill Brutzman bi...@hkmetalcraft.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Thu, Apr 12, 2012 11:52 am Subject: Re: [U2] COMMON Size MisMatch Eating my own dog food... I cranked CLEARCOMMON into the LOGTO SandBox and OGTO LIVE paragraph commands. --Bill From: u2-users-bounces at listserver.u2ug.org mailto:u2-users-bounces at listserver.u2ug.org] On Behalf Of on_Bausili at hcsc.net ent: Thursday, July 16, 2009 10:17 AM o: u2-users at listserver.u2ug.org ubject: [U2] Fw: COMMON misMatch Since all common variables are cleared when you exit UniVerse, and liminates the error, is it possible your user used a LOGTO command to witch environments that have different versions of the subroutine OP.R87? We had both a Test and a Prod environment on the same box, and xperienced problems when enhanced code in Test was being staged for romotion into Prod. Executing a program in Test that had changes to ts COMMON, and then logging into Prod resulted in the size mismatch rror when running the unchanged program. Our solution was to insert CLEARCOMMON in the LOGIN paragraphs. Don Forwarded by Don Bausili/OK/HCSC on 07/16/2009 09:09 AM - Brutzman, Bill BillB at hkMetalCraft.com Sent by: 2-users-bounces at listserver.u2ug.org 7/15/2009 06:55 PM lease respond to U2 Users List u2-users at listserver.u2ug.org o U2 Users List u2-users at listserver.u2ug.org c Subject e: [U2] COMMON misMatch A user here obtained an error message... COMMON size mismatch in subroutine HOP.R87. Upon logging out and then logging back in again... The HOP program was ble to launch without this error. Help with a diagnosis and more reliable cure would be appreciated. This user is WinXP / Dynamic Connect / UniVerse 10.1 / HP-Ux 11i v2. --Bill ___ 2-Users mailing list 2-Users at listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users The information contained in this communication is confidential, rivate, roprietary, or otherwise privileged and is intended only for the use of he addressee. Unauthorized use, disclosure, distribution or copying is trictly prohibited and may be unlawful. If you have received this ommunication in error, please notify the sender immediately at (312) 53-6000 in Illinois; (800)835-8699 in New Mexico; (918)560-3500 in klahoma; or (972)766-6900 in Texas. __ 2-Users mailing list 2-Users at listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users revious message: [U2] Fw: COMMON misMatch ext message: [U2] Universe Retrieve essages sorted by: [ date ] [ thread ] [ subject ] [ author ] ore information about the U2-Users -Original Message- rom: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] n Behalf Of Bill Brutzman ent: Thursday, April 12, 2012 2:40 PM o: U2 Users List ubject: [U2] COMMON Size MisMatch ... in subroutine named XYZ.R1. While I would like to pass parameters back-and-forth invoking bona fide external ubroutines using commands such as... CALL *MY.SUB.R2(param1, param2, rrorString) ...I have a few big old legacy programs with nasty COMMON tentacles. How can I make these pesky COMMON messages go away? --Bill __ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users __ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution
Re: [U2] COMMON Size MisMatch
That doesn't help in the situation I described, where you really want just *part* of your environment variables retained, and part cleared. Like I said simple sites, don't have this problem, but some sites have this kind of complexity, and those have or should have by now, seperated their universal common variables, from their local common variables. -Original Message- From: Perry Taylor perry.tay...@zirmed.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Thu, Apr 12, 2012 12:23 pm Subject: Re: [U2] COMMON Size MisMatch Do you need to use LOGTO.ABORT perhaps instead of LOGTO? -Original Message- rom: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] n Behalf Of Wjhonson ent: Thursday, April 12, 2012 1:08 PM o: u2-users@listserver.u2ug.org ubject: Re: [U2] COMMON Size MisMatch f you *do* use CLEARCOMMON you have to be alert to gremlins as well. OGTO is not expecting to have to reinitialize the system and so probably oesn't. ou need to review what the Login process is doing as well. ou may end up wiping out control information such as the user's port, name, ogin time, functions they can and can't do, menu access, default printer, and o on and so forth. All depends on how complex the login processor has become at your site. ome sites don't do a darn thing. Some have thousands of lines of code at ogin. Some of which set common (read environment) variables, that you *don't ant* to clear, or at least that you want to reset if you do clear them. -Original Message- rom: Bill Brutzman bi...@hkmetalcraft.com o: U2 Users List u2-users@listserver.u2ug.org ent: Thu, Apr 12, 2012 11:52 am ubject: Re: [U2] COMMON Size MisMatch ating my own dog food... I cranked CLEARCOMMON into the LOGTO SandBox and GTO LIVE paragraph commands. -Bill rom: u2-users-bounces at listserver.u2ug.org ailto:u2-users-bounces at listserver.u2ug.org] On Behalf Of n_Bausili at hcsc.net nt: Thursday, July 16, 2009 10:17 AM : u2-users at listserver.u2ug.org bject: [U2] Fw: COMMON misMatch ince all common variables are cleared when you exit UniVerse, and iminates the error, is it possible your user used a LOGTO command to itch environments that have different versions of the subroutine P.R87? e had both a Test and a Prod environment on the same box, and perienced problems when enhanced code in Test was being staged for omotion into Prod. Executing a program in Test that had changes to s COMMON, and then logging into Prod resulted in the size mismatch ror when running the unchanged program. ur solution was to insert CLEARCOMMON in the LOGIN paragraphs. on --- Forwarded by Don Bausili/OK/HCSC on 07/16/2009 09:09 AM - Brutzman, Bill BillB at hkMetalCraft.com Sent by: -users-bounces at listserver.u2ug.org /15/2009 06:55 PM ease respond to 2 Users List u2-users at listserver.u2ug.org o 2 Users List u2-users at listserver.u2ug.org ubject : [U2] COMMON misMatch A user here obtained an error message... COMMON size mismatch in subroutine HOP.R87. pon logging out and then logging back in again... The HOP program was le to launch without this error. elp with a diagnosis and more reliable cure would be appreciated. his user is WinXP / Dynamic Connect / UniVerse 10.1 / HP-Ux 11i v2. -Bill __ -Users mailing list -Users at listserver.u2ug.org tp://listserver.u2ug.org/mailman/listinfo/u2-users he information contained in this communication is confidential, ivate, oprietary, or otherwise privileged and is intended only for the use of e addressee. Unauthorized use, disclosure, distribution or copying is rictly prohibited and may be unlawful. If you have received this mmunication in error, please notify the sender immediately at (312) 3-6000 in Illinois; (800)835-8699 in New Mexico; (918)560-3500 in lahoma; or (972)766-6900 in Texas. _ -Users mailing list -Users at listserver.u2ug.org tp://listserver.u2ug.org/mailman/listinfo/u2-users evious message: [U2] Fw: COMMON misMatch xt message: [U2] Universe Retrieve ssages sorted by: [ date ] [ thread ] [ subject ] [ author ] re information about the U2-Users Original Message- om: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] n Behalf Of Bill Brutzman nt: Thursday, April 12, 2012 2:40 PM : U2 Users List bject: [U2] COMMON Size MisMatch .. in subroutine named XYZ.R1. hile I would like to pass parameters back-and-forth invoking bona fide external ubroutines using commands such as... CALL *MY.SUB.R2(param1, param2, rorString) ..I have a few big old legacy programs with nasty COMMON tentacles. ow can I make these pesky COMMON messages go away? -Bill _ -Users mailing list -us...@listserver.u2ug.org tp://listserver.u2ug.org/mailman/listinfo/u2-users _ -Users mailing list -us
Re: [U2] COMMON Size MisMatch
I presume that the following is workable... Comments are welcome. To LogTo the SandBox it is now just... ED VOC LLS 0001: PA 0002: CLEARCOMMON 0003: LOGTO SANDBOX 0004: WHO ED VOC LOGIN 0001: PA 0003: PTERM -ECHO DELAY 0005: BREAK ON 0007: CLEARCOMMON 0009: HK.RESET.PRINTER 0011: RUN MT.BP GET.STACK.LOGNAME 0013: LOGIN.CONTROL 0015: PTERM CASE NOINVERT 0016: RUN B.USER TERMINAL.SETUP.R0 0018: IF @LOGNAME = 'root'THEN GO TCL 0019: IF @LOGNAME = 'brutzy' THEN GO TCL 0020: IF @LOGNAME = 'raymond' THEN GO TCL 0022: MM 0024: TCL: Bottom at line 24. --Bill -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson Sent: Thursday, April 12, 2012 3:08 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] COMMON Size MisMatch If you *do* use CLEARCOMMON you have to be alert to gremlins as well. LOGTO is not expecting to have to reinitialize the system and so probably doesn't. You need to review what the Login process is doing as well. You may end up wiping out control information such as the user's port, name, login time, functions they can and can't do, menu access, default printer, and so on and so forth. All depends on how complex the login processor has become at your site. Some sites don't do a darn thing. Some have thousands of lines of code at Login. Some of which set common (read environment) variables, that you *don't want* to clear, or at least that you want to reset if you do clear them. -Original Message- From: Bill Brutzman bi...@hkmetalcraft.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Thu, Apr 12, 2012 11:52 am Subject: Re: [U2] COMMON Size MisMatch Eating my own dog food... I cranked CLEARCOMMON into the LOGTO SandBox and OGTO LIVE paragraph commands. --Bill From: u2-users-bounces at listserver.u2ug.org mailto:u2-users-bounces at listserver.u2ug.org] On Behalf Of on_Bausili at hcsc.net ent: Thursday, July 16, 2009 10:17 AM o: u2-users at listserver.u2ug.org ubject: [U2] Fw: COMMON misMatch Since all common variables are cleared when you exit UniVerse, and liminates the error, is it possible your user used a LOGTO command to witch environments that have different versions of the subroutine OP.R87? We had both a Test and a Prod environment on the same box, and xperienced problems when enhanced code in Test was being staged for romotion into Prod. Executing a program in Test that had changes to ts COMMON, and then logging into Prod resulted in the size mismatch rror when running the unchanged program. Our solution was to insert CLEARCOMMON in the LOGIN paragraphs. Don Forwarded by Don Bausili/OK/HCSC on 07/16/2009 09:09 AM - Brutzman, Bill BillB at hkMetalCraft.com Sent by: 2-users-bounces at listserver.u2ug.org 7/15/2009 06:55 PM lease respond to U2 Users List u2-users at listserver.u2ug.org o U2 Users List u2-users at listserver.u2ug.org c Subject e: [U2] COMMON misMatch A user here obtained an error message... COMMON size mismatch in subroutine HOP.R87. Upon logging out and then logging back in again... The HOP program was ble to launch without this error. Help with a diagnosis and more reliable cure would be appreciated. This user is WinXP / Dynamic Connect / UniVerse 10.1 / HP-Ux 11i v2. --Bill ___ 2-Users mailing list 2-Users at listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users The information contained in this communication is confidential, rivate, roprietary, or otherwise privileged and is intended only for the use of he addressee. Unauthorized use, disclosure, distribution or copying is trictly prohibited and may be unlawful. If you have received this ommunication in error, please notify the sender immediately at (312) 53-6000 in Illinois; (800)835-8699 in New Mexico; (918)560-3500 in klahoma; or (972)766-6900 in Texas. __ 2-Users mailing list 2-Users at listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users revious message: [U2] Fw: COMMON misMatch ext message: [U2] Universe Retrieve essages sorted by: [ date ] [ thread ] [ subject ] [ author ] ore information about the U2-Users -Original Message- rom: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] n Behalf Of Bill Brutzman ent: Thursday, April 12, 2012 2:40 PM o: U2 Users List ubject: [U2] COMMON Size MisMatch ... in subroutine named XYZ.R1. While I would like to pass parameters back-and-forth invoking bona fide external ubroutines using commands such as... CALL *MY.SUB.R2(param1, param2, rrorString) ...I have a few big old legacy programs with nasty COMMON tentacles. How can I make these pesky COMMON messages go away? --Bill __ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] COMMON Size MisMatch
Look inside those routines, and determine that they are agnostic about you coming from LOGIN vs LOGTO Perhaps I'm the sole person in history to have coded things that are wise about the distinction -Original Message- From: Bill Brutzman bi...@hkmetalcraft.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Thu, Apr 12, 2012 12:46 pm Subject: Re: [U2] COMMON Size MisMatch I presume that the following is workable... Comments are welcome. To LogTo the SandBox it is now just... ED VOC LLS 001: PA 002: CLEARCOMMON 003: LOGTO SANDBOX 004: WHO ED VOC LOGIN 001: PA 003: PTERM -ECHO DELAY 005: BREAK ON 007: CLEARCOMMON 009: HK.RESET.PRINTER 011: RUN MT.BP GET.STACK.LOGNAME 013: LOGIN.CONTROL 015: PTERM CASE NOINVERT 016: RUN B.USER TERMINAL.SETUP.R0 018: IF @LOGNAME = 'root'THEN GO TCL 019: IF @LOGNAME = 'brutzy' THEN GO TCL 020: IF @LOGNAME = 'raymond' THEN GO TCL 022: MM 024: TCL: ottom at line 24. --Bill -Original Message- rom: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] n Behalf Of Wjhonson ent: Thursday, April 12, 2012 3:08 PM o: u2-users@listserver.u2ug.org ubject: Re: [U2] COMMON Size MisMatch f you *do* use CLEARCOMMON you have to be alert to gremlins as well. OGTO is not expecting to have to reinitialize the system and so probably oesn't. ou need to review what the Login process is doing as well. ou may end up wiping out control information such as the user's port, name, ogin time, functions they can and can't do, menu access, default printer, and o on and so forth. All depends on how complex the login processor has become at your site. ome sites don't do a darn thing. Some have thousands of lines of code at ogin. Some of which set common (read environment) variables, that you *don't ant* to clear, or at least that you want to reset if you do clear them. -Original Message- rom: Bill Brutzman bi...@hkmetalcraft.com o: U2 Users List u2-users@listserver.u2ug.org ent: Thu, Apr 12, 2012 11:52 am ubject: Re: [U2] COMMON Size MisMatch ating my own dog food... I cranked CLEARCOMMON into the LOGTO SandBox and GTO LIVE paragraph commands. -Bill rom: u2-users-bounces at listserver.u2ug.org mailto:u2-users-bounces at istserver.u2ug.org] On Behalf Of on_Bausili at hcsc.net nt: Thursday, July 16, 2009 10:17 AM : u2-users at listserver.u2ug.org bject: [U2] Fw: COMMON misMatch ince all common variables are cleared when you exit UniVerse, and liminates the rror, is it possible your user used a LOGTO command to witch environments that ave different versions of the subroutine OP.R87? e had both a Test and a Prod environment on the same box, and xperienced roblems 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 into rod resulted in the size mismatch rror when running the unchanged program. ur solution was to insert CLEARCOMMON in the LOGIN paragraphs. on --- Forwarded by Don Bausili/OK/HCSC on 07/16/2009 09:09 AM - Brutzman, ill BillB at hkMetalCraft.com Sent by: -users-bounces at listserver.u2ug.org /15/2009 06:55 PM ease respond to 2 Users List u2-users at listserver.u2ug.org o 2 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. pon logging out and then logging back in again... The HOP program was ble to aunch without this error. elp with a diagnosis and more reliable cure would be appreciated. his user is WinXP / Dynamic Connect / UniVerse 10.1 / HP-Ux 11i v2. -Bill __ -Users mailing list -Users at listserver.u2ug.org tp://listserver.u2ug.org/mailman/listinfo/u2-users he information contained in this communication is confidential, rivate, oprietary, or otherwise privileged and is intended only for the use of he ddressee. Unauthorized use, disclosure, distribution or copying is trictly rohibited and may be unlawful. If you have received this ommunication in rror, please notify the sender immediately at (312) 3-6000 in Illinois; (800)835-8699 in New Mexico; (918)560-3500 in klahoma; or 972)766-6900 in Texas. _ -Users mailing list -Users at listserver.u2ug.org tp://listserver.u2ug.org/mailman/listinfo/u2-users evious message: [U2] Fw: COMMON misMatch ext message: [U2] Universe Retrieve ssages sorted by: [ date ] [ thread ] [ subject ] [ author ] ore information bout the U2-Users -Original Message- om: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] Behalf Of Bill Brutzman nt: Thursday, April 12, 2012 2:40 PM : U2 Users List bject: [U2] COMMON Size MisMatch .. in subroutine named XYZ.R1. hile I would like to pass parameters back-and-forth invoking bona fide external broutines using commands such as... CALL *MY.SUB.R2(param1, param2, rorString) ..I have
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- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson Sent: Thursday, April 12, 2012 4:56 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] COMMON Size MisMatch Look inside those routines, and determine that they are agnostic about you coming from LOGIN vs LOGTO Perhaps I'm the sole person in history to have coded things that are wise about the distinction -Original Message- From: Bill Brutzman bi...@hkmetalcraft.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Thu, Apr 12, 2012 12:46 pm Subject: Re: [U2] COMMON Size MisMatch I presume that the following is workable... Comments are welcome. To LogTo the SandBox it is now just... ED VOC LLS 001: PA 002: CLEARCOMMON 003: LOGTO SANDBOX 004: WHO ED VOC LOGIN 001: PA 003: PTERM -ECHO DELAY 005: BREAK ON 007: CLEARCOMMON 009: HK.RESET.PRINTER 011: RUN MT.BP GET.STACK.LOGNAME 013: LOGIN.CONTROL 015: PTERM CASE NOINVERT 016: RUN B.USER TERMINAL.SETUP.R0 018: IF @LOGNAME = 'root'THEN GO TCL 019: IF @LOGNAME = 'brutzy' THEN GO TCL 020: IF @LOGNAME = 'raymond' THEN GO TCL 022: MM 024: TCL: ottom at line 24. --Bill -Original Message- rom: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] n Behalf Of Wjhonson ent: Thursday, April 12, 2012 3:08 PM o: u2-users@listserver.u2ug.org ubject: Re: [U2] COMMON Size MisMatch f you *do* use CLEARCOMMON you have to be alert to gremlins as well. OGTO is not expecting to have to reinitialize the system and so probably oesn't. ou need to review what the Login process is doing as well. ou may end up wiping out control information such as the user's port, name, ogin time, functions they can and can't do, menu access, default printer, and o on and so forth. All depends on how complex the login processor has become at your site. ome sites don't do a darn thing. Some have thousands of lines of code at ogin. Some of which set common (read environment) variables, that you *don't ant* to clear, or at least that you want to reset if you do clear them. -Original Message- rom: Bill Brutzman bi...@hkmetalcraft.com o: U2 Users List u2-users@listserver.u2ug.org ent: Thu, Apr 12, 2012 11:52 am ubject: Re: [U2] COMMON Size MisMatch ating my own dog food... I cranked CLEARCOMMON into the LOGTO SandBox and GTO LIVE paragraph commands. -Bill rom: u2-users-bounces at listserver.u2ug.org mailto:u2-users-bounces at istserver.u2ug.org] On Behalf Of on_Bausili at hcsc.net nt: Thursday, July 16, 2009 10:17 AM : u2-users at listserver.u2ug.org bject: [U2] Fw: COMMON misMatch ince all common variables are cleared when you exit UniVerse, and liminates the rror, is it possible your user used a LOGTO command to witch environments that ave different versions of the subroutine OP.R87? e had both a Test and a Prod environment on the same box, and xperienced roblems 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 into rod resulted in the size mismatch rror when running the unchanged program. ur solution was to insert CLEARCOMMON in the LOGIN paragraphs. on --- Forwarded by Don Bausili/OK/HCSC on 07/16/2009 09:09 AM - Brutzman, ill BillB at hkMetalCraft.com Sent by: -users-bounces at listserver.u2ug.org /15/2009 06:55 PM ease respond to 2 Users List u2-users at listserver.u2ug.org o 2 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. pon logging out and then logging back in again... The HOP program was ble to aunch without this error. elp with a diagnosis and more reliable cure would be appreciated. his user is WinXP / Dynamic Connect / UniVerse 10.1 / HP-Ux 11i v2. -Bill __ -Users mailing list -Users at listserver.u2ug.org tp://listserver.u2ug.org/mailman/listinfo/u2-users he information contained in this communication is confidential, rivate, oprietary, or otherwise privileged and is intended only for the use of he ddressee. Unauthorized use, disclosure, distribution or copying is trictly rohibited and may be unlawful. If you have received this ommunication in rror, please notify the sender immediately at (312) 3-6000 in Illinois; (800)835-8699 in New Mexico; (918)560-3500 in klahoma; or 972)766-6900 in Texas. _ -Users mailing list -Users at listserver.u2ug.org tp://listserver.u2ug.org/mailman/listinfo/u2-users evious message: [U2] Fw: COMMON misMatch ext message: [U2] Universe Retrieve ssages sorted by: [ date ] [ thread ] [ subject ] [ author ] ore information bout the U2-Users -Original Message- om
Re: [U2] COMMON Size MisMatch
From: Wjhonson Look inside those routines, and determine that they are agnostic about you coming from LOGIN vs LOGTO Perhaps I'm the sole person in history to have coded things that are wise about the distinction (Not following this thread, sorry if I'm being redundant here) Will, there have been extensive discussions on this topic in D3 and QM forums. Some platforms carry Common across Logto, others not. Migrations have been complicated by this. Some apps getting a GUI refit prefer to have all users come through a common gateway account, and then have them forwarded to other accounts - the question of how Common is carried across Logto versus Login is quite important here. So no, you're not alone by a long shot. T ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] COMMON Size MisMatch
I was pointing out Tony, that some systems programmers like myself, have written BASIC code which acts differently if it sense you are doing a Login, versus a Logto. So the quick solution of simply doing a ClearCommon may not be what's wanted in this case (the OP's original case). I was issuing a warning that just doing ClearCommon may solve one problem, while createing two others :) -Original Message- From: Tony Gravagno 3xk547...@sneakemail.com To: u2-users u2-users@listserver.u2ug.org Sent: Thu, Apr 12, 2012 3:23 pm Subject: Re: [U2] COMMON Size MisMatch From: Wjhonson Look inside those routines, and determine that they are agnostic bout you coming from LOGIN vs LOGTO Perhaps I'm the sole person in history to have coded things that are wise about the distinction (Not following this thread, sorry if I'm being redundant here) Will, there have been extensive discussions on this topic in D3 and QM orums. Some platforms carry Common across Logto, others not. igrations have been complicated by this. Some apps getting a GUI efit prefer to have all users come through a common gateway account, nd then have them forwarded to other accounts - the question of how ommon is carried across Logto versus Login is quite important here. o no, you're not alone by a long shot. T __ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] COMMON Size MisMatch
While this topic is on the table, can we request some kind of COMMON flag or command that would tell the DBM to clear commons on a LOGTO? David A. Green (480) 813-1725 DAG Consulting -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Brutzman Sent: Thursday, April 12, 2012 2:22 PM To: U2 Users List Subject: 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- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson Sent: Thursday, April 12, 2012 4:56 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] COMMON Size MisMatch Look inside those routines, and determine that they are agnostic about you coming from LOGIN vs LOGTO Perhaps I'm the sole person in history to have coded things that are wise about the distinction -Original Message- From: Bill Brutzman bi...@hkmetalcraft.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Thu, Apr 12, 2012 12:46 pm Subject: Re: [U2] COMMON Size MisMatch I presume that the following is workable... Comments are welcome. To LogTo the SandBox it is now just... ED VOC LLS 001: PA 002: CLEARCOMMON 003: LOGTO SANDBOX 004: WHO ED VOC LOGIN 001: PA 003: PTERM -ECHO DELAY 005: BREAK ON 007: CLEARCOMMON 009: HK.RESET.PRINTER 011: RUN MT.BP GET.STACK.LOGNAME 013: LOGIN.CONTROL 015: PTERM CASE NOINVERT 016: RUN B.USER TERMINAL.SETUP.R0 018: IF @LOGNAME = 'root'THEN GO TCL 019: IF @LOGNAME = 'brutzy' THEN GO TCL 020: IF @LOGNAME = 'raymond' THEN GO TCL 022: MM 024: TCL: ottom at line 24. --Bill -Original Message- rom: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] n Behalf Of Wjhonson ent: Thursday, April 12, 2012 3:08 PM o: u2-users@listserver.u2ug.org ubject: Re: [U2] COMMON Size MisMatch f you *do* use CLEARCOMMON you have to be alert to gremlins as well. OGTO is not expecting to have to reinitialize the system and so probably oesn't. ou need to review what the Login process is doing as well. ou may end up wiping out control information such as the user's port, name, ogin time, functions they can and can't do, menu access, default printer, and o on and so forth. All depends on how complex the login processor has become at your site. ome sites don't do a darn thing. Some have thousands of lines of code at ogin. Some of which set common (read environment) variables, that you *don't ant* to clear, or at least that you want to reset if you do clear them. -Original Message- rom: Bill Brutzman bi...@hkmetalcraft.com o: U2 Users List u2-users@listserver.u2ug.org ent: Thu, Apr 12, 2012 11:52 am ubject: Re: [U2] COMMON Size MisMatch ating my own dog food... I cranked CLEARCOMMON into the LOGTO SandBox and GTO LIVE paragraph commands. -Bill rom: u2-users-bounces at listserver.u2ug.org mailto:u2-users-bounces at istserver.u2ug.org] On Behalf Of on_Bausili at hcsc.net nt: Thursday, July 16, 2009 10:17 AM : u2-users at listserver.u2ug.org bject: [U2] Fw: COMMON misMatch ince all common variables are cleared when you exit UniVerse, and liminates the rror, is it possible your user used a LOGTO command to witch environments that ave different versions of the subroutine OP.R87? e had both a Test and a Prod environment on the same box, and xperienced roblems 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 into rod resulted in the size mismatch rror when running the unchanged program. ur solution was to insert CLEARCOMMON in the LOGIN paragraphs. on --- Forwarded by Don Bausili/OK/HCSC on 07/16/2009 09:09 AM - Brutzman, ill BillB at hkMetalCraft.com Sent by: -users-bounces at listserver.u2ug.org /15/2009 06:55 PM ease respond to 2 Users List u2-users at listserver.u2ug.org o 2 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. pon logging out and then logging back in again... The HOP program was ble to aunch without this error. elp with a diagnosis and more reliable cure would be appreciated. his user is WinXP / Dynamic Connect / UniVerse 10.1 / HP-Ux 11i v2. -Bill __ -Users mailing list -Users at listserver.u2ug.org tp://listserver.u2ug.org/mailman/listinfo/u2-users he information contained in this communication is confidential, rivate, oprietary, or otherwise privileged and is intended only for the use of he ddressee. Unauthorized use, disclosure, distribution or copying is trictly rohibited and may be unlawful. If you have received this ommunication in rror, please notify the sender immediately at (312) 3-6000 in Illinois; (800)835-8699 in New Mexico
Re: [U2] COMMON Size MisMatch
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 dgr...@dagconsulting.com To: 'U2 Users List' u2-users@listserver.u2ug.org 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: u2-users-boun...@listserver.u2ug.org mailto:u2-users-boun...@listserver.u2ug.org] 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: u2-users-boun...@listserver.u2ug.org mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson ent: Thursday, April 12, 2012 4:56 PM o: u2-users@listserver.u2ug.org 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 bi...@hkmetalcraft.com o: U2 Users List u2-users@listserver.u2ug.org 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: u2-users-boun...@listserver.u2ug.org mailto:u2-users-boun...@listserver.u2ug.org] Behalf Of Wjhonson nt: Thursday, April 12, 2012 3:08 PM : u2-users@listserver.u2ug.org 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 bi...@hkmetalcraft.com : U2 Users List u2-users@listserver.u2ug.org 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
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 wjhon...@aol.com To: u2-users u2-users@listserver.u2ug.org 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 dgr...@dagconsulting.com o: 'U2 Users List' u2-users@listserver.u2ug.org 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: u2-users-boun...@listserver.u2ug.org ailto:u2-users-boun...@listserver.u2ug.org] 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: u2-users-boun...@listserver.u2ug.org ailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson nt: Thursday, April 12, 2012 4:56 PM : u2-users@listserver.u2ug.org 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 bi...@hkmetalcraft.com : U2 Users List u2-users@listserver.u2ug.org 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: u2-users-boun...@listserver.u2ug.org ailto:u2-users-boun...@listserver.u2ug.org] Behalf Of Wjhonson t: Thursday, April 12, 2012 3:08 PM u2-users@listserver.u2ug.org 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 bi...@hkmetalcraft.com U2 Users List u2-users@listserver.u2ug.org 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
Re: [U2] Common Table Expressions
It could be; although by-exp is not recursive. Probably with a set of WITHIN claused statements it may do the trick - I haven't given it much thought. But it's only one of the things that CTE would give you access to. The point though was not 'how would you do this with the current set of U2 tools'. The provision of CTEs in SQL didn't give SQL the ability to do things you couldn't do before - it just made it a whole lot simpler and more efficient. The point is what advantages would the provision of CTEs give to U2. If the idea is good in SQL - and it is - it's probably worthy of consideration by the folks who can appropriately assess each technology and see how it might be applied to advantage within the U2 environment. Cheers, Stuart Boydell -Original Message- I'd have to think about it a bit, but wouldn't your scenario be a good case for a BY-EXP clause? I haven't used a BY-EXP in years! :o -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Boydell, Stuart Sent: Thursday, April 08, 2010 5:27 PM To: U2 Users List Subject: Re: [U2] Common Table Expressions One scenario off the top of my head would be to allow recursive selects. This would be similar to a qselect, where you select a list of MVs from a record, but would also allow you to include the parent id and any child ids and grandchild ids, etc as a result of the CTE select. Eg. A master customer AC has child accounts which may also have child ACs - you would use a CTE to select the customer and return the parent and list of children and grandchildren etc in a single optimised select. To do this in U2 now probably requires a recursive basic program. Stuart Boydell -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of phil walker Sent: Friday, 9 April 2010 06:30 To: U2 Users List Subject: Re: [U2] Common Table Expressions Hi Symeon, I have been trying to think how you would use CTE (or equivalents) in u2 SQL. Are you willing to enlighten us? Regards Phil -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of Symeon Breen Sent: Thursday, 8 April 2010 8:16 p.m. To: 'U2 Users List' Subject: Re: [U2] Common Table Expressions It could certainly work in u2 SQL - not sure how you would do this in English (MVQuery or whatever) tho -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Boydell, Stuart Sent: 08 April 2010 06:55 To: U2 Users List Subject: [U2] Common Table Expressions Just working on a SQL project which uses lots of CTEs (Common Table Expressions) for in-memory caching of table data. Really useful things in terms of speed and not having to create temporary tables for manipulating data. Wondering if anyone has thought about if or how they might work in U2... Just a thought for better and better (which is down at the moment.) Cheers, Stuart Boydell ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Common Table Expressions
It could certainly work in u2 SQL - not sure how you would do this in English (MVQuery or whatever) tho -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Boydell, Stuart Sent: 08 April 2010 06:55 To: U2 Users List Subject: [U2] Common Table Expressions Just working on a SQL project which uses lots of CTEs (Common Table Expressions) for in-memory caching of table data. Really useful things in terms of speed and not having to create temporary tables for manipulating data. Wondering if anyone has thought about if or how they might work in U2... Just a thought for better and better (which is down at the moment.) Cheers, Stuart Boydell ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Common Table Expressions
Hi Symeon, I have been trying to think how you would use CTE (or equivalents) in u2 SQL. Are you willing to enlighten us? Regards Phil -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of Symeon Breen Sent: Thursday, 8 April 2010 8:16 p.m. To: 'U2 Users List' Subject: Re: [U2] Common Table Expressions It could certainly work in u2 SQL - not sure how you would do this in English (MVQuery or whatever) tho -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Boydell, Stuart Sent: 08 April 2010 06:55 To: U2 Users List Subject: [U2] Common Table Expressions Just working on a SQL project which uses lots of CTEs (Common Table Expressions) for in-memory caching of table data. Really useful things in terms of speed and not having to create temporary tables for manipulating data. Wondering if anyone has thought about if or how they might work in U2... Just a thought for better and better (which is down at the moment.) Cheers, Stuart Boydell ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Common Table Expressions
One scenario off the top of my head would be to allow recursive selects. This would be similar to a qselect, where you select a list of MVs from a record, but would also allow you to include the parent id and any child ids and grandchild ids, etc as a result of the CTE select. Eg. A master customer AC has child accounts which may also have child ACs - you would use a CTE to select the customer and return the parent and list of children and grandchildren etc in a single optimised select. To do this in U2 now probably requires a recursive basic program. Stuart Boydell -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of phil walker Sent: Friday, 9 April 2010 06:30 To: U2 Users List Subject: Re: [U2] Common Table Expressions Hi Symeon, I have been trying to think how you would use CTE (or equivalents) in u2 SQL. Are you willing to enlighten us? Regards Phil -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of Symeon Breen Sent: Thursday, 8 April 2010 8:16 p.m. To: 'U2 Users List' Subject: Re: [U2] Common Table Expressions It could certainly work in u2 SQL - not sure how you would do this in English (MVQuery or whatever) tho -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Boydell, Stuart Sent: 08 April 2010 06:55 To: U2 Users List Subject: [U2] Common Table Expressions Just working on a SQL project which uses lots of CTEs (Common Table Expressions) for in-memory caching of table data. Really useful things in terms of speed and not having to create temporary tables for manipulating data. Wondering if anyone has thought about if or how they might work in U2... Just a thought for better and better (which is down at the moment.) Cheers, Stuart Boydell ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Common Table Expressions
There is *NO* CTE functionality in U2 at all as far as I'm aware. However, I think it would be a worthwhile addition if it could be implemented both for Retrieve (mvquery) and U2 SQL. CTEs are now supported in the major SQL DBs... Stuart Boydell -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of phil walker Sent: Friday, 9 April 2010 10:36 To: U2 Users List Subject: Re: [U2] Common Table Expressions Precisely, I am pretty sure U2 Sql does not support ALL the capabilities of a MS Sql CTE... But I would be interested in being shown otherwise -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of Boydell, Stuart Sent: Friday, 9 April 2010 12:31 p.m. To: U2 Users List Subject: Re: [U2] Common Table Expressions One scenario off the top of my head would be to allow recursive selects. This would be similar to a qselect, where you select a list of MVs from a record, but would also allow you to include the parent id and any child ids and grandchild ids, etc as a result of the CTE select. Eg. A master customer AC has child accounts which may also have child ACs - you would use a CTE to select the customer and return the parent and list of children and grandchildren etc in a single optimised select. To do this in U2 now probably requires a recursive basic program. Stuart Boydell -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of phil walker Sent: Friday, 9 April 2010 06:30 To: U2 Users List Subject: Re: [U2] Common Table Expressions Hi Symeon, I have been trying to think how you would use CTE (or equivalents) in u2 SQL. Are you willing to enlighten us? Regards Phil -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of Symeon Breen Sent: Thursday, 8 April 2010 8:16 p.m. To: 'U2 Users List' Subject: Re: [U2] Common Table Expressions It could certainly work in u2 SQL - not sure how you would do this in English (MVQuery or whatever) tho -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Boydell, Stuart Sent: 08 April 2010 06:55 To: U2 Users List Subject: [U2] Common Table Expressions Just working on a SQL project which uses lots of CTEs (Common Table Expressions) for in-memory caching of table data. Really useful things in terms of speed and not having to create temporary tables for manipulating data. Wondering if anyone has thought about if or how they might work in U2... Just a thought for better and better (which is down at the moment.) Cheers, Stuart Boydell ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Common Table Expressions
I'd have to think about it a bit, but wouldn't your scenario be a good case for a BY-EXP clause? I haven't used a BY-EXP in years! :o -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Boydell, Stuart Sent: Thursday, April 08, 2010 5:27 PM To: U2 Users List Subject: Re: [U2] Common Table Expressions One scenario off the top of my head would be to allow recursive selects. This would be similar to a qselect, where you select a list of MVs from a record, but would also allow you to include the parent id and any child ids and grandchild ids, etc as a result of the CTE select. Eg. A master customer AC has child accounts which may also have child ACs - you would use a CTE to select the customer and return the parent and list of children and grandchildren etc in a single optimised select. To do this in U2 now probably requires a recursive basic program. Stuart Boydell -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of phil walker Sent: Friday, 9 April 2010 06:30 To: U2 Users List Subject: Re: [U2] Common Table Expressions Hi Symeon, I have been trying to think how you would use CTE (or equivalents) in u2 SQL. Are you willing to enlighten us? Regards Phil -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of Symeon Breen Sent: Thursday, 8 April 2010 8:16 p.m. To: 'U2 Users List' Subject: Re: [U2] Common Table Expressions It could certainly work in u2 SQL - not sure how you would do this in English (MVQuery or whatever) tho -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Boydell, Stuart Sent: 08 April 2010 06:55 To: U2 Users List Subject: [U2] Common Table Expressions Just working on a SQL project which uses lots of CTEs (Common Table Expressions) for in-memory caching of table data. Really useful things in terms of speed and not having to create temporary tables for manipulating data. Wondering if anyone has thought about if or how they might work in U2... Just a thought for better and better (which is down at the moment.) Cheers, Stuart Boydell ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] COMMON misMatch
In message 2b1985075953c947a7a53a53987adab22b5...@arnold.hkmetalcraft.lan, Brutzman, Bill bi...@hkmetalcraft.com writes A user here obtained an error message... COMMON size mismatch in subroutine HOP.R87. Upon logging out and then logging back in again... The HOP program was able to launch without this error. Help with a diagnosis and more reliable cure would be appreciated. This user is WinXP / Dynamic Connect / UniVerse 10.1 / HP-Ux 11i v2. Has this program been created by an auto-generator program? Did the user go into the program by the *same* *route* both times after logging in? If you've got a program generator auto-generating named common names you have to be very careful - I fell foul of that a couple of times with PACE. Cheers, Wol -- Anthony W. Youngman pi...@thewolery.demon.co.uk 'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998 Visit the MaVerick web-site - http://www.maverick-dbms.org Open Source Pick ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] COMMON misMatch
1. The program was not created by an auto-generator. 2. The user only has one way to go in. 3. Others here may have been in the program when he went in. Also, others here have access to an older version of the program that may have been active when this user went in... likely having the same COMMON definition. 4. I am glad to be reminded of MaVerick. --Bill -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Anthony W. Youngman Sent: Thursday, July 16, 2009 7:24 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] COMMON misMatch In message 2b1985075953c947a7a53a53987adab22b5...@arnold.hkmetalcraft.lan, Brutzman, Bill bi...@hkmetalcraft.com writes A user here obtained an error message... COMMON size mismatch in subroutine HOP.R87. Upon logging out and then logging back in again... The HOP program was able to launch without this error. Help with a diagnosis and more reliable cure would be appreciated. This user is WinXP / Dynamic Connect / UniVerse 10.1 / HP-Ux 11i v2. Has this program been created by an auto-generator program? Did the user go into the program by the *same* *route* both times after logging in? If you've got a program generator auto-generating named common names you have to be very careful - I fell foul of that a couple of times with PACE. Cheers, Wol -- Anthony W. Youngman pi...@thewolery.demon.co.uk 'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998 Visit the MaVerick web-site - http://www.maverick-dbms.org Open Source Pick ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] COMMON misMatch
A user here obtained an error message... COMMON size mismatch in subroutine HOP.R87. Upon logging out and then logging back in again... The HOP program was able to launch without this error. Help with a diagnosis and more reliable cure would be appreciated. This user is WinXP / Dynamic Connect / UniVerse 10.1 / HP-Ux 11i v2. --Bill ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] COMMON misMatch
Someone probably compiled the program you were in while you were in it. When you went back, you got the new version when you executed it again. - Original Message From: Brutzman, Bill bi...@hkmetalcraft.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Wednesday, July 15, 2009 7:54:47 PM Subject: Re: [U2] COMMON misMatch A user here obtained an error message... COMMON size mismatch in subroutine HOP.R87. Upon logging out and then logging back in again... The HOP program was able to launch without this error. Help with a diagnosis and more reliable cure would be appreciated. This user is WinXP / Dynamic Connect / UniVerse 10.1 / HP-Ux 11i v2. --Bill ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Common UNIX Printing System
Yes, we're using CUPS on Universe on RHEL 5.x. Dave Taylor Sysmark Information Systems, Inc. Authorized IBM Business Partner 49 Aspen Way Rolling Hills Estates, CA 90274 (O) 800-SYSMARK (800-797-6275) (F) 310-377-3550 (C) 310-561-5200 www.sysmarkinfo.com - Original Message - From: Bertrand, Ron bertran...@ghc.org To: u2-users@listserver.u2ug.org Sent: Thursday, February 26, 2009 3:12 PM Subject: [U2] Common UNIX Printing System Hey all - is anybody using CUPS with universe? Ron Bertrand Analyst,AP SYS 3 ISD/LIS/AMS Group Health Coop 206-901-4519 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
[U2] Common UNIX Printing System
Hey all - is anybody using CUPS with universe? Ron Bertrand Analyst,AP SYS 3 ISD/LIS/AMS Group Health Coop 206-901-4519 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Common UNIX Printing System
-Original Message- From: owner-u2-us...@listserver.u2ug.org [mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Bertrand, Ron Sent: Thursday, February 26, 2009 3:13 PM To: u2-users@listserver.u2ug.org Subject: [U2] Common UNIX Printing System Hey all - is anybody using CUPS with universe? Yes, have been for years, and it works just fine. One odd problem I ran into after migrating from RH AS 3 to RH ES 5 was that the default error policy for newly created printers is stop-printer rather than retry-job. If we have a blip on a WAN link, I'd rather not have to manually restart all the printer queues for that site. I have to remember to change that setting anytime I add a new printer. -John --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Common UNIX Printing System
Yes on RHEL 4.0 -Original Message- From: owner-u2-us...@listserver.u2ug.org [mailto:owner-u2- us...@listserver.u2ug.org] On Behalf Of Bertrand, Ron Sent: Friday, 27 February 2009 12:46 p.m. To: u2-users@listserver.u2ug.org Subject: [U2] Common UNIX Printing System Hey all - is anybody using CUPS with universe? Ron Bertrand Analyst,AP SYS 3 ISD/LIS/AMS Group Health Coop 206-901-4519 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] COMMON
Following up on the common thread, can one OPENSEQ to a COMMON variable? -Original Message- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] COMMON
quote who='Dennis Bartlett' date='Friday 04 April 2008' Following up on the common thread, can one OPENSEQ to a COMMON variable? Sure - same approach. OPENSEQ FILE,RECORD TO F.HANDLE THEN * add F.HANDLE to the common array and list of open files... END -- Jeff Butera, Ph.D. Administrative Systems Hampshire College [EMAIL PROTECTED] 413-559-5556 Where I'm from, we believe all sorts of things that aren't true. We call it history. The Wizard, Wicked --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] COMMON
Dennis Bartlett wrote: Following up on the common thread, can one OPENSEQ to a COMMON variable? Absolutely. COMMON is merely a method of sharing data between programs without argument passing as is commonly done with subroutines. Note that common in this fashion is accessible among programs for the individual user, not to be confused with shared common, (such as the catalog uses, which allows users to access the same info). So, any variable can be stuffed into a common block, and it's best to use what's called NAMED COMMON so that you don't collide with anyone else's definitions, (particularly if you're running vendor code which you can't read the source code to). And then any program or routine that has that COMMON block defined within it has acccess to the variables within it. With file pointers, the trick is to set flags so that you know that they're open or closed. Which can be followed through to other variables, set flags to show that they've been initialized or not. Always set them to show non-initialized first, set them, set the flags, then in any routine that uses them, check the flags before you use them, and if the flags aren't set, you can't use the values. One very common way of dealing with this is to call a program from the VOC LOGIN PA which sets common. As has been mentioned previously, watch out for accounts, as showing that your PAYMASTER file is open, and having your user log from TEST to LIVE will give you some very real problems... -- Allen Egerton aegerton at pobox dot com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] COMMON
Yes, but be sure to re-initialize to '' AFTER closing, if you close it, at least in UniData. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Bartlett Sent: Friday, April 04, 2008 8:07 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] COMMON Following up on the common thread, can one OPENSEQ to a COMMON variable? -Original Message- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] COMMON
And be very careful with 4GLs using named common, as I found out many years ago with PACE. It stored filepointers in named common, generating the common name from the file name. Fortunately we found the problem when the runtime complained of a redefinition of common (one routine had the same name declared twice), and not by two programs confusing one declaration and thereby writing to the wrong file! Cheers, Wol -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Allen Egerton Sent: 04 April 2008 14:00 To: u2-users@listserver.u2ug.org Subject: Re: [U2] COMMON Dennis Bartlett wrote: Following up on the common thread, can one OPENSEQ to a COMMON variable? Absolutely. COMMON is merely a method of sharing data between programs without argument passing as is commonly done with subroutines. Note that common in this fashion is accessible among programs for the individual user, not to be confused with shared common, (such as the catalog uses, which allows users to access the same info). So, any variable can be stuffed into a common block, and it's best to use what's called NAMED COMMON so that you don't collide with anyone else's definitions, (particularly if you're running vendor code which you can't read the source code to). And then any program or routine that has that COMMON block defined within it has acccess to the variables within it. With file pointers, the trick is to set flags so that you know that they're open or closed. Which can be followed through to other variables, set flags to show that they've been initialized or not. Always set them to show non-initialized first, set them, set the flags, then in any routine that uses them, check the flags before you use them, and if the flags aren't set, you can't use the values. One very common way of dealing with this is to call a program from the VOC LOGIN PA which sets common. As has been mentioned previously, watch out for accounts, as showing that your PAYMASTER file is open, and having your user log from TEST to LIVE will give you some very real problems... -- Allen Egerton aegerton at pobox dot com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] COMMON
Yes, but On thing to remember - OpenSeq sets a record lock. That will remain until you CloseSeq the record. If the file is unique to your user number, for example, you might want to release it rather than have a load of these clogging up your lock table. One of the few occasions when locking could become a hindrance rather than a help. Brian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Bartlett Sent: 04 April 2008 13:07 To: u2-users@listserver.u2ug.org Subject: RE: [U2] COMMON Following up on the common thread, can one OPENSEQ to a COMMON variable? -Original Message- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] COMMON
With file pointers, the trick is to set flags so that you know that they're open or closed. Actually there is a way to test if a variable is an open file-handle or not ( at least in uv): I have the following code in som subroutines that you can feed with a open file handle or a file name in FN: IF FILEINFO( FN,0) THEN ;* He gave us an open file-handle. FP.FN = FN FNAM = FILEINFO(FN,1) END ELSE OPEN FN TO FP.FN ELSE ERR.M = Me:: Can't open :FN RETURN END FNAM = FN END Every other test I've tried results in error messages. This may be universe only - don't know. -- mats --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] COMMON
quote who='Mats Carlid' date='Friday 04 April 2008' With file pointers, the trick is to set flags so that you know that they're open or closed. Actually there is a way to test if a variable is an open file-handle or not ( at least in uv): I have the following code in som subroutines that you can feed with a open file handle or a file name in FN. This may be universe only - don't know. Works on Unidata as well. -- Jeff Butera, Ph.D. Administrative Systems Hampshire College [EMAIL PROTECTED] 413-559-5556 Where I'm from, we believe all sorts of things that aren't true. We call it history. The Wizard, Wicked --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
[U2] COMMON
Hi I have a subroutine that WRITESEQ to a record in a type 1 file called INTEGRITY. Is there anyway I can open the file once (in the subroutine) and thereafter use the same file handle (to avoid opening the file each time the subroutine is called) ? All the code on this site opens the file in the calling routine and passes the handle to the subroutine. I want to rather make the subroutine a stand-alone, not requiring more than the subroutine call added to the calling programs. I have a suspicion I can use named common - if so, does this have to be declared in the calling routine (which would negate my purpose!). Any advice? --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] COMMON
Sure You can and You don't have to have the named common in any other routine. The only gotcha I'm aware of is that the file stays open until you exit universe or explicitely closes it i.e. even if you LOGTO another acoount. It's quite confusing and potentially dangerous that the open file still points to the old account. -- mats Dennis Bartlett skrev: Hi I have a subroutine that WRITESEQ to a record in a type 1 file called INTEGRITY. Is there anyway I can open the file once (in the subroutine) and thereafter use the same file handle (to avoid opening the file each time the subroutine is called) ? All the code on this site opens the file in the calling routine and passes the handle to the subroutine. I want to rather make the subroutine a stand-alone, not requiring more than the subroutine call added to the calling programs. I have a suspicion I can use named common - if so, does this have to be declared in the calling routine (which would negate my purpose!). Any advice? --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] COMMON
quote who='Dennis Bartlett' date='Thursday 03 April 2008' Hi I have a subroutine that WRITESEQ to a record in a type 1 file called INTEGRITY. Is there anyway I can open the file once (in the subroutine) and thereafter use the same file handle (to avoid opening the file each time the subroutine is called) ? All the code on this site opens the file in the calling routine and passes the handle to the subroutine. I want to rather make the subroutine a stand-alone, not requiring more than the subroutine call added to the calling programs. I have a suspicion I can use named common - if so, does this have to be declared in the calling routine (which would negate my purpose!). Yes - I use this approach and it works fine. In short, I build a COMMON array with file handles and a dynamic array with the names of the open files. At first invocation, you need to check to see if the COMMON vars are initialized or not - if not, you initialize them. Once this is done I merely look for a filename in the dynamic array, if found it returns the file handle for I/O. If it's not present it opens the file, adds the filename to the list and you go on. At the end of the process, it loops over all open file handles and closes them. Depending on your application, you can figure out optimal places to open/close the file handles. -- Jeff Butera, Ph.D. Administrative Systems Hampshire College [EMAIL PROTECTED] 413-559-5556 Where I'm from, we believe all sorts of things that aren't true. We call it history. The Wizard, Wicked --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] COMMON
And - as a suggestion - as mentioned earlier - the array of file names should contain ACCOUNT-FileName to ensure MainAcct-CustFile # TestAcct-CustFile -- it's happened more than once the DIM'd array of file handles survived a LOGTO and suddenly that person is trashing the MAIN account data thinking they are in the TEST account. We have a DIM(50) of file handles we carry around - I'm sure we could do 200 -- you're limited by the OS open files, but at the point you approach that, U2 usually 'soft closes' the file (closes at OS level, but remembers your handle and reopens on demand). Is there anyway I can open the file once (in the subroutine) and thereafter use the same file handle (to avoid opening the file each time the subroutine is called) ? All the code on this site opens the file in the calling routine and passes the handle to the subroutine. I want to rather make the subroutine a stand-alone, not requiring more than the subroutine call added to the calling programs. I have a suspicion I can use named common - if so, does this have to be declared in the calling routine (which would negate my purpose!). Yes - I use this approach and it works fine. In short, I build a COMMON array with file handles and a dynamic array with the names of the open files. At first invocation, you need to check to see if the COMMON vars are initialized or not - if not, you initialize them. Once this is done I merely look for a filename in the dynamic array, if found it returns the file handle for I/O. If it's not present it opens the file, adds the filename to the list and you go on. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] COMMON
Here is a simple but effect way to handle this scenario: COMMON /NAMED_COM/ NAMED_COM.REC(10) EQUATE NAMED_COM.FLAG TO NAMED_COM.REC(1) EQUATE F.OPEN.FILETO NAMED_COM.REC(2) Etc. IF NAMED_COM.FLAG NE @WHO:@DATE THEN ;* Open Files, Set Variables and NAMED_COM.FLAG if everything is OK. GOSUB INIT.NAMED.COM END --- If you are concerned about closing files or deleting a temp file or record then you can call your subroutine with a Final call via a Call Type argument. Normally this Call Type would be I for Initializing, N for Normal, F for Final. Thanks, David A. Green www.dagconsulting.com (480) 813-1725 -Original Message- I have a subroutine that WRITESEQ to a record in a type 1 file called INTEGRITY. Is there anyway I can open the file once (in the subroutine) and thereafter use the same file handle (to avoid opening the file each time the subroutine is called) ? --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
[U2] Common Memory Space Size
Is there a maximum size to the global commons memory space? We've run into an issue where we appear to be getting corruption on the global commons memory space causing our program to die. The program is about 40k of source and uses 5560 unamed globals. Any input would be appreciated, Thanks! Sean Ferguson --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
