Introduction of Calling Quick Screens as Functions
Johnson, Harold A EDUC:EX
Harold.A.Johnson@gems1.gov.bc.ca
Tue, 25 May 2004 08:51:57 -0700
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C4426F.DD60ACC0
Content-Type: text/plain;
charset="iso-8859-1"
We use this method extensively in our system for complicated processes that
would be a bear to write in QTP. The only "gotcha" that you need to worry
about is an apparent 32,000 "run screen" limit. That is, if your quick
screen calls other screens, there is a limit as to how many times that other
screen can be called. It seems to depend on how many calls are being done
and the relative complexity of the process that you've written.
cheers
-----Original Message-----
From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com]On Behalf Of Jon Hawks
Sent: 2004 May 24 10:36 PM
To: chuck.reinke; Darren Reely; powerh-l@lists.sowder.com
Subject: Re: Introduction of Calling Quick Screens as Functions
Try this, and for the hard-core's, please excuse the simplicity. I copied it
from one of our regular jobs we run in batch using quick.
quick auto=qk-batch-1 term=vt220 (if you're on an Open/VMS your site might
need this)
Screen qk-batch-1
file customer designer
file invoices designer
file payments designer
Procedure Internal Special-payments
begin
some great stuff here
gets
lets
puts
end
Procedure internal regular-payments
begin
some other great stuff here
get an invoice
get the payment
lets reconcile
puts
end
procedure cust-run
begin
while retrieving customer sequential
begin
if cust-type = "regular joe"
do internal regular-payments
if cust-type = "special"
do internal special-payments
end
procedure initial
begin
do internal cust-run
return
end
build
"chuck.reinke" <chuck.reinke@sbcglobal.net> wrote:
I believe the practice arose many years ago on ancient HP systems where
programmers often ran out of stack space. A GHOST screen, as a sub-process,
was a technique for gaining additional system resources. Eventually some
programming logic supported the technique as well as the idea of shared
subroutines.
Chuck
----- Original Message -----
From: "Darren Reely"
To:
Sent: Monday, May 24, 2004 6:10 PM
Subject: Introduction of Calling Quick Screens as Functions
> We were wondering today when the concept was introduced allowing coders
> to call quick screens as hidden functions. The code I'm maintaining
> seems to have been created as early as April 1992.
>
> While we're on the subject. What is the best way to set up the screen
> statement? A! pparently the GHOST option is not _required_ when calling
> the screen.
>
> Thanks for the interest.
>
> Darren
>
>
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l@lists.sowder.com
> Subscribe: "subscribe" in message body to
powerh-l-request@lists.sowder.com
> Unsubscribe: "unsubscribe " in message body to
powerh-l-request@lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.sowder.com
Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
Unsubscribe: "unsubscribe " in message body to
powerh-l-request@lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
------_=_NextPart_001_01C4426F.DD60ACC0
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=808294915-25052004><FONT face=Arial color=#0000ff size=2>We use
this method extensively in our system for complicated processes that would be a
bear to write in QTP. The only "gotcha" that you need to worry about
is an apparent 32,000 "run screen" limit. That is, if your quick screen
calls other screens, there is a limit as to how many times that other screen can
be called. It seems to depend on how many calls are being done and the
relative complexity of the process that you've written.</FONT></SPAN></DIV>
<DIV><SPAN class=808294915-25052004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808294915-25052004><FONT face=Arial color=#0000ff
size=2>cheers</FONT></SPAN></DIV>
<BLOCKQUOTE>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
powerh-l-admin@lists.sowder.com [mailto:powerh-l-admin@lists.sowder.com]<B>On
Behalf Of </B>Jon Hawks<BR><B>Sent:</B> 2004 May 24 10:36 PM<BR><B>To:</B>
chuck.reinke; Darren Reely; powerh-l@lists.sowder.com<BR><B>Subject:</B> Re:
Introduction of Calling Quick Screens as Functions<BR><BR></FONT></DIV>
<DIV>Try this, and for the hard-core's, please excuse the simplicity. I copied
it from one of our regular jobs we run in batch using quick.</DIV>
<DIV> </DIV>
<DIV>quick auto=qk-batch-1 term=vt220 (if you're on an Open/VMS your
site might need this)</DIV>
<DIV> </DIV>
<DIV>Screen qk-batch-1</DIV>
<DIV>file customer designer</DIV>
<DIV>file invoices designer</DIV>
<DIV>file payments designer </DIV>
<DIV> </DIV>
<DIV>Procedure Internal Special-payments</DIV>
<DIV> begin</DIV>
<DIV> some great stuff here</DIV>
<DIV> gets </DIV>
<DIV> lets</DIV>
<DIV> puts</DIV>
<DIV> end</DIV>
<DIV>Procedure internal regular-payments</DIV>
<DIV> begin</DIV>
<DIV> some other great stuff here</DIV>
<DIV> get an invoice</DIV>
<DIV> get the payment</DIV>
<DIV> lets reconcile</DIV>
<DIV> puts</DIV>
<DIV> end</DIV>
<DIV>procedure cust-run</DIV>
<DIV> begin</DIV>
<DIV> while retrieving customer sequential </DIV>
<DIV> begin</DIV>
<DIV> if cust-type = "regular joe"</DIV>
<DIV> do internal
regular-payments</DIV>
<DIV> if cust-type = "special"</DIV>
<DIV> do internal
special-payments</DIV>
<DIV> end</DIV>
<DIV>procedure initial</DIV>
<DIV> begin</DIV>
<DIV> do internal cust-run</DIV>
<DIV> return</DIV>
<DIV> end</DIV>
<DIV>build<BR><BR><B><I>"chuck.reinke"
<chuck.reinke@sbcglobal.net></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">I
believe the practice arose many years ago on ancient HP systems
where<BR>programmers often ran out of stack space. A GHOST screen, as a
sub-process,<BR>was a technique for gaining additional system resources.
Eventually some<BR>programming logic supported the technique as well as the
idea of shared<BR>subroutines.<BR><BR>Chuck<BR><BR>----- Original Message
----- <BR>From: "Darren Reely" <DARREN.REELY@LATTICESEMI.COM><BR>To:
<POWERH-L@LISTS.SOWDER.COM><BR>Sent: Monday, May 24, 2004 6:10
PM<BR>Subject: Introduction of Calling Quick Screens as
Functions<BR><BR><BR>> We were wondering today when the concept was
introduced allowing coders<BR>> to call quick screens as hidden
functions. The code I'm maintaining<BR>> seems to have been created as
early as April 1992.<BR>><BR>> While we're on the subject. What is the
best way to set up the screen<BR>> statement? A! pparently the GHOST
option is not _required_ when calling<BR>> the screen.<BR>><BR>>
Thanks for the interest.<BR>><BR>> Darren<BR>><BR>><BR>> = =
= = = = = = = = = = = = = = = = = = = = = = = = = =<BR>> Mailing list:
powerh-l@lists.sowder.com<BR>> Subscribe: "subscribe" in message body
to<BR>powerh-l-request@lists.sowder.com<BR>> Unsubscribe: "unsubscribe
<PASSWORD>" in message body to<BR>powerh-l-request@lists.sowder.com<BR>>
http://lists.sowder.com/mailman/listinfo/powerh-l<BR>> This list is
closed, thus to post to the list you must be a subscriber.<BR><BR><BR>= = =
= = = = = = = = = = = = = = = = = = = = = = = = =<BR>Mailing list:
powerh-l@lists.sowder.com<BR>Subscribe: "subscribe" in message body to
powerh-l-request@lists.sowder.com<BR>Unsubscribe: "unsubscribe <PASSWORD>"
in message body to
powerh-l-request@lists.sowder.com<BR>http://lists.sowder.com/mailman/listinfo/powerh-l<BR>This
list is closed, thus to post to the list you must be a
subscriber.</BLOCKQUOTE><BR><BR></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C4426F.DD60ACC0--