|
View previous topic :: View next topic
|
| Author |
Message |
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
Dick, the cond code confusion is due to me.
he keeps getting an 806 because the job will always have a step that invokes the old program - which is no longer available.
i suggested the condition code so the original step would not be executed, since he won't change his proc's or jcl.
since he can not change the pgm of a step he needs to skip this step and then allow the new step (with the ikjeft ) to be added to the proc with his overrides.
as far as the op's last question:
| Quote: |
So "Cond" is the only way to not to execute that step. Is there anyother way to not to execute that step?
|
that still is an open question. I don't have (or want to look for) any other suggestions.
why the op does not create a new proc is beyond me. he will need to when he migrates to production. but that is just me being picky. |
|
| Back to top |
|
 |
birdy K
New User
Joined: 05 Mar 2008
Posts: 72
Location: chennai
|
|
|
|
hai d.sch
I have given the entire jcl for that step. My problem also I have specified. Please look at the jesjcl. As it is executing the step s501025 which is not a db2 cobol pgm. I am getting s806 load module not found abend and the message "The module DSNHLI was not found". I have compiled as db2 cobol pgm. But that step is calling simple cobol pgm. Then it added the new step as cobol-db2 pgm. |
|
| Back to top |
|
|
|
|
