Introduction of Calling Quick Screens as Functions

[Chris Sharman]

David Morrison - Corporate wrote:
> <rant on>
> 
> Well, now you see why the cost of running California's prisons has skyrocketed.  Here you have someone working for that department that refuses to use a better tool when it is available.
> 
> </rant off>

On the contrary: maintainability should be a major factor in assessing 
'the best tool available'.
Quick provides a lot of Cobol-like 3GL funtionality.
Luddites don't need to embrace its 4GL nature at all, if they're more 
comfortable with 3GL.
When we moved to Powerhouse, initially all was well, as we progressed up 
the learning curve, until one of our older programmers booked onto the 
advanced course.
Afterwards, he never again wrote a Quick screen without several hundred 
lines of procedural code.
He retired several years ago now, fortunately, but I still come across 
the odd 'dog's breakfast'.
QTP (and/or Quiz) is the right tool for the vast majority of batch 
processes.
I'm aware it's possible to use Quick in batch, but I've never needed to 
do it myself.

Chris

>  -----Original Message-----
> From: 	Penney, John [mailto:John.Penney@corr.ca.gov] 
> Sent:	Tuesday, May 25, 2004 12:14 PM
> To:	'Viet Nguyen'; Hodson, Paul M EDUC:EX; powerh-l@lists.sowder.com
> Subject:	RE: Introduction of Calling Quick Screens as Functions 
> 
> Dear Viet:
> <rant on> or whatever
> The majority, if not the vast majority of batch processing can easily or if
> not easily, with come forethought can indeed be accomplished via QTP. The
> tools, techniques and procedures alluded to in this thread reflect the
> leading edge of the most sophisticated users who have years if not decades
> of Powerhouse experience. I do not think that it would be in your best
> interest to learn how to program Quick to act just like a variant of Cobol-
> or am I missing something? I do realize that the Quick language provides you
> this type of functionality but, IMHO, it is to be used with caution and only
> after long reflection as to the consequences. QTP is a fine tool and looping
> constructs are there in the facility. YMMV IIRC IMHO
> <rant off> or whatever
> 
> JP in Sacto
> -----Original Message-----
> From: Viet Nguyen [mailto:VNguyen@wsboces.org]
> Sent: Tuesday, May 25, 2004 11:44 AM
> To: Hodson, Paul M EDUC:EX; powerh-l@lists.sowder.com
> Subject: RE: Introduction of Calling Quick Screens as Functions 
> 
> 
> Where can I learn more about using quick as batch programs? I am a
> newbie at Cognos QTP - it's very awkward for me without the looping
> constructs.
> Thanks.
> 
> -----Original Message-----
> From: powerh-l-admin@lists.sowder.com
> [mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Hodson, Paul M
> EDUC:EX
> Sent: Tuesday, May 25, 2004 2:37 PM
> To: 'powerh-l@lists.sowder.com'
> Subject: Introduction of Calling Quick Screens as Functions 
> 
> We have a batch quick process(aka ghost screen) that processes a WEB
> calls
> (up to 2500 concurrent clients) from a JAVA app through oracle 8i blob
> data
> type and generates PDF output back to the WEB app(see www.sanface.com).
> All
> run from a batch quick engine running in "persistent" mode using  a
> trigger
> and an openVMS mailbox. This allows our CUI user to the have the same
> processing as the WEB does (sharing the processing) and dressed up the
> powerhouse CUI interface(lipstick on a pig - sorry but the WEB is much
> sexier but why re-write if it ain't broke)
> 
> Also at another client, we have batch quick that is used as an interface
> between Level 4 (business app) and Level 3 (steel mill line ops) that is
> shared. DMQueue is used to pass messages with the same quick engine
> running
> 6 different mill ops interfaces. Again sharing processing.
> 
> There are papers written in the cognos proceedings (user group meeting
> minutes). One comes to mind "Quick:To Batch or not to batch" from the
> 1994
> version.
> 
>  
> 
> 
>>Paul Hodson
>>Senior Systems Consultant
>>
> 
> Tel:     (250) 387-8877
>            (250) 744-2372
> Fax:    (250) 744-2372
> Email: Paul.Hodson@gems7.gov.bc.ca
>           phodson@pacificcoast.net



-----------------------------------------------------------------------

Any views expressed in this message are those of the sender and not
necessarily those of CCA Group.  The unauthorized use, disclosure,
copying or alteration of this message is forbidden.  The contents of
this message may be confidential and/or privileged, copyright CCA Group
and are intended solely for the use of the individual or entity to whom
they are addressed.  Whilst this message has been scanned, CCA Group
cannot guarantee that it is virus free or compatible with your systems
and accepts no responsibility for any loss or damage arising from its
use. The recipient is advised to run their own anti-virus software. If
you receive this message in error please contact
postmaster@ccagroup.co.uk immediately, destroy any copies and delete it
from your computer systems.