|
At 01:12 03/04/1999 +1100, Kris Vaidyanathan wrote: > I am trying to create a subsystem that will run to Never ending programs >that will work as trigger programs for some data monitoring >However the techos who are helping on this seem to be puzzled as to how to >get two jobs going, and I also think they have some difficulty >Creating the subsystem. Triggers run in the same job as the application that initiates the trigger event. This is not necessarily bad, since the trigger will remain active as long as the job is active, unless you terminate it with a call to CEETREC or RCLACTGRP. If you need to do some heavy batch processing in your trigger, I would suggest that you validate the data in the trigger and then write a request to a data queue. This request could then be processed by a program in another subsystem that just calls QRCVDTAQ and waits. You could start this job with an auto start job entry so that it runs when the subsystem starts. It will use no CPU cycles as long as there are no requests to process, and can run in its own storage pool. Pete Hall pbhall@execpc.com http://www.execpc.com/~pbhall +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.