Restartabilty issue due to invocations with diff parameters
Posted: Tue Dec 13, 2005 9:08 pm
Hi
We are using the restartability feature in our sequences
However since we fetching the parameters a control table to pass on to subsequent sequence - the values between an abort and rerun dont necessarily match, as a result of which the following warning message crops up
JobControl (@Coordinator): The current job run does not have the same parameters as its checkpoint record.
The checkpointed parameter values were:
LoadId=1 [current run=2]
and causes the sequence to abort.
Ex
Sequence main <checkpointed>
-routine activity<not checkpointed>
-user variable
-Sequence1<checkpointed>
-Sequence2<checkpointed>
-routine activity<not checkpointed>
Can we supress this warning using a message handler/Is there any other method to handle this?
We are using the restartability feature in our sequences
However since we fetching the parameters a control table to pass on to subsequent sequence - the values between an abort and rerun dont necessarily match, as a result of which the following warning message crops up
JobControl (@Coordinator): The current job run does not have the same parameters as its checkpoint record.
The checkpointed parameter values were:
LoadId=1 [current run=2]
and causes the sequence to abort.
Ex
Sequence main <checkpointed>
-routine activity<not checkpointed>
-user variable
-Sequence1<checkpointed>
-Sequence2<checkpointed>
-routine activity<not checkpointed>
Can we supress this warning using a message handler/Is there any other method to handle this?