Endevor

Is there a way to SET STOPRC 12 for all DELETE packages and allow the default 16 for MOVE packages?   We cannot rely on the developers to change the value on the package screen.

An SE37 will flag Endevor to set RC=12 and not abend.  We had two object libraries SE37 when doing a massive delete.  Endevor should have simply stopped and asked for help.  Instead, the job ran hours and was finally cancelled because it was hogging too much CPU.

We do not, however, want a move package to stop after every RC=12 - it is better to show all the failures at once rather than piecemeal stops. 
Please advise.

Thanks.

We have no logic for that, but you can use a package exit at the before-cast or mid-cast point.

The exit can use the 'request for data' mechanism to retrieve the package SCL statements, parse them to identify the SET STOPRC statement, and abort the CAST if it is not correct.

Not sure how your site determines whether a package is a MOVE or a DELETE one. Hopefully you use something that is present in the package header, like the package ID or description. If so. the exit could make its decision when finding the SET STOPRC statement.

However, if a package is a MOVE or DELETE one depending on the actions it contains, your exit needs to examine all the SCL statements (or maybe request for the package action records) and keep information between exit calls.

Best rrgards

Eduard Penafiel

CA-Endevor support

Thank you.