CCCHK initialization parameters

[TERESA JOHNSON]

We recently had an issue with a job completing successfully with a non-zero return code.  This was due to no CCCHK statement in place for that job at any level.  The product behaved as it should.

It is standard practice for us to code a catchall CCCHK statement at APPL level but this wasn't followed.  

I would like to cater for this issue in future and not rely on the CCCHK statement being coded at APPL level or that GLOBALS member is INVOKED.

I found that the Statement Search Order mentioned CCCHK initialization parameters.

CCCHK: Specify Job Processing Based on Condition Codes

A matched statement affects all jobs and applications in the ESP subsystem (including proxies in a master and proxy system).

Has anyone implemented a catchall at parm level?  I couldn't find anything in the installation guide or the samples.

Is it just a case of coding CCCHK RC(1:4095) FAIL CONTINUE in CYBESS03/ESPPARM.

Thanks

Teresa

[Jonas Dusil]

Hi Teresa,

You are correct. Using CCCHK as an initialization parameter should work as a "catchall".  (Unless is overwritten by other CCHK on job or application level)
Coding it in the ESPPARM (cybess03) is the right way.


------------------------------
Jonáš Dusil
Product Owner | ESP Workload Automation | Mainframe Software Division
------------------------------