HI

[ankit]

Hi All,
Does anyone know the purpose of the subroutine BATCH.JOB.CONTROL......

THIS SUBROUTINE IS ATTACHED TO THE JOB BY NAME
PM.ACTIVITY.ONITE

Thanks,
Ankit

[Luis Lascano]

Ankit,

Subject is incorrect. You should put something like:

[T24] BATCH.JOB.CONTROL subroutine.

Regards,

Luis

[Mike Preece]

BATCH.JOB.CONTROL is the subroutine that controls batch jobs. For
example, it essentially runs the CoB. Typically during the CoB, for
"multithreaded" processes, it will call the .LOAD routine, then
the .SELECT routine and, for each record to be processed, will start a
transaction boundary (unless the routine has .NTX set in
ADDITIONAL.INFO in F.PGM.FILE), call the routine to process a record
(commonly called the "record routine") and, on return, commit the
transaction, then, when all records have been processed, call
the .POST routine. It can also do a number of other things, like
logging performance stats etc.. To clarify, in a multithreaded CoB, an
"instance" of BJC will run on each "thread" (or PID), with any one of
the threads performing the .LOAD, .SELECT and .POST routines, and
multiple instances calling the record routine simultaneously. Note
also that the term "multithreaded" has a distinct meaning in the T24
context, meaning that the processing is shared by multiple processes.

Mike.

[John Watson]

Hi,

Please be aware that if you remove transaction boundaries from any
multithreaded T24 job then you risk data integrity issues in the event
of a COB crash - the PGM.FILE should only be modified at the request
of the Help Desk.

If you do remove the transaction boundary and you get a crash then HD
will probably not be able to help you and a restore / COB re-run will
be required.

Also, the .POST functionality appeared briefly in one version of T24
but is no longer supported.

Cheers,

John.