Re: Never ending programs

Heba

I generally use a program that waits on a data queue which either just
controls ending and the loop wait period or actually recieves the data as
well - this depends on the process.

If you were to use your trigger program to place items on a data queue and
then have a background process always running (as I gleaned you might be
considering) this would probably work for you. You may want to consider how
you end the process if you adopt this as if you place an END instruction on
the data queue, there is some potential for the END instruction to be
behind other entries and delay the end operation. There may be some
sequencing or keying of the data queue you can do to get around this.

Although others have mentioned ASJ and PSJ jobs I tend to steer clear of
them as I find it helpful to be able to start subsystems without production
jobs starting by default. I generally start my NEP jobs as part of my
production startup program, although I have some switches and parameters
that allow me to control how far "up" the system comes.

I also generally use and create a subsystem for these jobs as opposed to
using the IBM ones. although this is obviously not mandatory, I just find
it more useful for documentation, management, tuning etc.

An additional technique I have found useful is to use the submitting CL
(Yes it has its place :) ) to check whether it is interactive or batch at
startup and if interactive submit itself: this accounts for those instances
where you want to initiate the job manually.

Hope this helps

Regards
Evan Harris

>I need to write a program to act as a daemon. it should work under a certain
>subsystem (Qbatch for example), wait for the new recoded orders and
>authorize them at a predefined intervals of time.
>
>What are the possible programing techniques that can be used to achieve this
>objective other than writing a DB trigger program calling the authorization
>process.