I guess I shouldn't use that "Quick Reply" button grrrrrr.....
Anyway here is more detail..
I'm working with JCL that calls a master PROC that calls a series of sub PROCs.
The last PROC step in the master proc, runs a program that we call "Component Response" which basically passes a status through MQ to USS box and picked up by a JAVA component for further processing.
This status is either populated by an exit within the COBOL program or condition codes of the previous PROC steps.
This works very well, until one day DASD resources were low and our primary allocation for an output file could not be accomodated, resulting in a JCL error, which stopped the job right there, which of course is normal.
However the monitoring system never got any feedback from our "Component Response" program so the problem took a long time to track down (so says the user).
Anyway, I've tried using the COND=EVEN construct to alleviate this problem. To do this I moved the "Component Response" statements out of the master PROC into it's own PROC and called it from both the master PROC and the JCL with COND=EVEN while duplicating the space issue and in both cases the "Component Response" steps would not trigger.
I am beginning to think that there is no way around this.
Thanks for listening.