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
To: 'U2 Users List'
Sent: Fri, Apr 13, 2012 11:50 am
Subject: Re: [U2] COMMON Size Mis
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
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
: Wols Lists
To: u2-users
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
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
ire me as a systems programmer because I keep finding things to
fix.
Will Johnson
-Original Message-
From: David A. Green
To: 'U2 Users List'
Sent: Fri, Apr 13, 2012 7:56 am
Subject: Re: [U2] COMMON Size MisMatch
That's why you would specify.
Example:
COMMON /S
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
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
-
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.
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
To: u2-users
Sent: Thu, Apr 12, 2012 4:49 pm
Subject: Re: [U2] COMMON Size MisMatch
ou don't r
on ? Or reread half the common?
-Original Message-
From: David A. Green
To: 'U2 Users List'
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 com
...@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
e).
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
Sent: Thu, Apr 12, 2012 3:23 pm
Subject: Re: [U2] COMMON Size MisMatch
From: Wjhonson
L
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 h
: 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 abou
12 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: CLEARCO
e 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
ated their
universal common variables, from their local common variables.
-Original Message-
From: Perry Taylor
To: U2 Users List
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
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
n (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
To: U2 Users List
Sent: Thu, Apr 12, 2012 11:52 am
Subject: Re: [U2] COMMON Size MisMatch
Eating my own dog
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" Sent by:
u2-users-bounces at listserver.u2ug.org
07/15/2009 06:55 PM
Please respond to
"U2 Users List"
To
"
: Thursday, April 08, 2010 11:44 PM
To: U2 Users List
Subject: 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
nario 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: [
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 pa
-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 wou
f 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 recor
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
en
> 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-
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
Subje
: Re: [U2] COMMON misMatch
In message
<2b1985075953c947a7a53a53987adab22b5...@arnold.hkmetalcraft.lan>,
"Brutzman, Bill" writes
>
>A user here obtained an error message...
>
> "COMMON size mismatch in subroutine "HOP.R87".
>
>Upon logging out
In message
<2b1985075953c947a7a53a53987adab22b5...@arnold.hkmetalcraft.lan>,
"Brutzman, Bill" 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 thi
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"
To: U2 Users List
Sent: Wednesday, July 15, 2009 7:54:47 PM
Subject: Re: [U2] COMMO
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 / Dyna
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: "Bertr
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
> -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 usin
> >> 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 han
>> 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
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 u
: 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 acc
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: [
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
> 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-55
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/
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.
GO
Dennis,
There are already routines within uniVerse to do this. See my notes:
http://u2blog.org/2007/11/05/appprogs-open-tools/ for more details.
Cheers,
David Murray
*
Learn and do
* Excel and share
http://u2blog.org
-Original Message-
From: [EMAIL PROTECTED]
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
> 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 op
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
49 matches
Mail list logo
