Hello everyone,
Im designing a job control process based on the following example:
I have a seq:
Job1 -> Job2 -> Job3
and a table on database
REQ DEP
Job1 - Job2
Job2 - Job3
If Job1 aborts, it will prevent Job2 and Job3 to execute and so on.
To check jobs, i use a before and after subroutine to call jobs which read control tables.
But when i tested, control jobs started to abort, because when routine calls them, they were executing by other calls.
So i tried to make multi instance calls, concatenating JOBNAME with the JOBPID, but the process is still unstable somehow.
I think it aborts when it call an aborted instance of the control job (control job may abort when JOBNAME is not on the tables, or when his requisites havent executed to signal job controller to not execute).
There is a way to delete all invocation id jobs before my sequence starts?
How to enqueue or delete all multi instance jobs?
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 44
- Joined: Wed Sep 02, 2015 7:19 am
- Location: Brasilia, Brazil
How to enqueue or delete all multi instance jobs?
Leandro Vieira
Data Expert - Brasilia, Brazil
Data Expert - Brasilia, Brazil
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Delete from where?
Probably the easiest to implement would be to delete the invocationID-stamped records from the RT_STATUSnnn hashed file for the particular job (job number nnn).
Probably the easiest to implement would be to delete the invocationID-stamped records from the RT_STATUSnnn hashed file for the particular job (job number nnn).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.