If you encounter this, it is probably a Prime INFORMATION (PI) legacy code. As
this was a commonly used convention in natively developed PI applications
(rather than PICK-ported apps).
As globally catalog'd object was a typical naming convention for production
object in PI. Plus as mentioned
to allow less-privileged users access to
kernal functions.
- Original Message -
From: Wjhonson
Sent: 12/05/12 11:09 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Advantage of indirect call in BASIC
Why do you call it ring jump in particular? What's the ring
In DataStage I have used the indirect all method to implement late binding
(referred to in the OOP post) to create a rules engine. The actual rules to
be applied/tested could not be known until the data actually arrived. So the
test routine itself was effectively little more than a dispatcher,
antli...@youngman.org.uk
To: u2-users u2-users@listserver.u2ug.org
Sent: Tue, Dec 4, 2012 4:07 pm
Subject: Re: [U2] Advantage of indirect call in BASIC
On 04/12/12 17:03, Wjhonson wrote:
Ring-jump ?
Vas is das
It's when the processor jumps between restricted user mode, and kernel
can
On 04/12/12 04:57, Israel, John R. wrote:
As far as the number of arguments changing, I will often write a subroutine
with a few extra variables (FUTURE1, FUTURE2, FUTURE3) so that I do not need
to find all the existing programs that call it and recompile them. It makes
this sort of thing
On 04/12/12 00:38, Wjhonson wrote:
I've not encountered this is my career previously, but now I'm seeing a
system written almost entirely with the use of indirect calls in Universe
BASIC.
That is
SOURCE = *SOME.PROGRAM
...
CALL @SOURCE(INPUTS)
Is there some advantage to the use of
hi,
These method is very usefull when you build software like a lego, some pieces
are polymorphic, the assignment of source depens of environment, params at
runtime not only at compile time... the value of soure can be assigned from
litteral, but also read from file or be the result of a text
On 12/03/2012 10:11 PM, Ed Clark wrote:
I could see a 4gl writing out this kind of code, or a menu system.
When you use indirect calling, the name of the subroutine can contain odd
characters that wouldn't normally be allowed--though on some platforms you can
also quote the call, e.g.:
CALL
Does anyone have any current benchmarks on this type of call? Several years
ago when I tested it in UniData it was very slow call compared to using the
name.
David A. Green
(480) 813-1725
DAG Consulting
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
List'
Subject: Re: [U2] Advantage of indirect call in BASIC
Does anyone have any current benchmarks on this type of call? Several years
ago when I tested it in UniData it was very slow call compared to using the
name.
David A. Green
(480) 813-1725
DAG Consulting
-Original Message-
From: u2
...@listserver.u2ug.org] On Behalf Of Martin Phillips
Sent: December-04-12 6:13 AM
To: 'U2 Users List'
Subject: Re: [U2] Advantage of indirect call in BASIC
Hi,
A direct call has to be looked up once in the catalogue system when it is first
used. Subsequent calls will be fast because the link has been created
I'll second Allen Egerton's left over from Prime Information theory. I
distinctly remember being told that indirect subroutine calls were
measurably faster way back in my days at Prime.
Wjhonson wrote:
I've not encountered this is my career previously, but now I'm seeing a system
written
On 04/12/12 16:06, Jeff Schasny wrote:
I'll second Allen Egerton's left over from Prime Information theory. I
distinctly remember being told that indirect subroutine calls were
measurably faster way back in my days at Prime.
From my knowledge of Pr1me architecture (which isn't great) this was
Of course blindingly fast on a 4 MIPS 9955 is what we might now call
quaintly tortoise like and that's why we still find things like the
all indirect subroutine calls in an attempt to squeeze any available
drop of performance out of applications.
Wols Lists wrote:
From my knowledge of Pr1me
Ring-jump ?
Vas is das
-Original Message-
From: Wols Lists antli...@youngman.org.uk
To: u2-users u2-users@listserver.u2ug.org
Sent: Tue, Dec 4, 2012 8:37 am
Subject: Re: [U2] Advantage of indirect call in BASIC
On 04/12/12 16:06, Jeff Schasny wrote:
I'll second Allen Egerton's
On 04/12/12 17:03, Wjhonson wrote:
Ring-jump ?
Vas is das
It's when the processor jumps between restricted user mode, and kernel
can do anything mode.
Cheers,
Wol
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
Why do you call it ring jump in particular?
What's the ring ?
-Original Message-
From: Wols Lists antli...@youngman.org.uk
To: u2-users u2-users@listserver.u2ug.org
Sent: Tue, Dec 4, 2012 4:07 pm
Subject: Re: [U2] Advantage of indirect call in BASIC
On 04/12/12 17:03, Wjhonson
Maybe some plan to change SOUREC at some key point w/o having to change it in
multiple places?
Looks like an idea that wasn't fully thought out, but that is just my 2 cents
worth. Maybe someone has some pearls of wisdom on this.
JRI
-Original Message-
From:
I've worked on a system that uses this approach. A bunch of variables are
defined in the startup program called by the LOGIN paragraph, and stored
in named common. The idea behind it was to centralize in the event that
the called program ever needed to be changed.
Larry Hiscock
Western Computer
On 12/3/2012 7:38 PM, Wjhonson wrote:
I've not encountered this is my career previously, but now I'm seeing a
system written almost entirely with the use of indirect calls in Universe
BASIC.
That is
SOURCE = *SOME.PROGRAM
...
CALL @SOURCE(INPUTS)
Is there some advantage to the use of
I've used it to dynamically create the subroutine name to call, based on
criteria, also you pass a name
from one program to another, then call that subroutine from that program.
George
George Gallen
Senior Programmer/Analyst
Accounting/Data Division
ggal...@wyanokegroup.com
ph:856.848.9005
I would hate to see that in our software, as it would be so hard to find
where a subroutine is used.
On the odd occasion we use this form (eg call depends on transaction type),
we do the definition just above, so it can be found.
In my experience, the number of parameters is more likely to
I could see a 4gl writing out this kind of code, or a menu system.
When you use indirect calling, the name of the subroutine can contain odd
characters that wouldn't normally be allowed--though on some platforms you can
also quote the call, e.g.:
CALL my-sub**(parms)
On Dec 3, 2012, at 7:38
As far as the number of arguments changing, I will often write a subroutine
with a few extra variables (FUTURE1, FUTURE2, FUTURE3) so that I do not need to
find all the existing programs that call it and recompile them. It makes this
sort of thing a piece of cake. The existing programs will
24 matches
Mail list logo
