Introduction of Calling Quick Screens as Functions
Jon Hawks
hawksj@yahoo.com
Mon, 24 May 2004 22:35:56 -0700 (PDT)
--0-2111171573-1085463356=:47135
Content-Type: text/plain; charset=us-ascii
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? Apparently 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.
--0-2111171573-1085463356=:47135
Content-Type: text/html; charset=us-ascii
<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? Apparently
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>
--0-2111171573-1085463356=:47135--