Introduction of Calling Quick Screens as Functions

[Hodson, Paul M EDUC:EX]

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