On Feb 18,  4:12am, [log in to unmask] wrote:
> I am looking for an answer to a question; it is simply:  'when is it
> appropriate for a jcw to be reset?'  We recently found out by accident that
> some 3rd party software companies reset the jcw, while some do not. Does
> anyone know what HP thinks should happen?

I can comment about two JCWs: CIERROR and JCW.

The CI initializes CIERROR and JCW to zero.  It only sets CIERROR
when an error occurs, and thus CIERROR tracks the most recent CI error,
not the status of the most recently executed command.

The CI clears the most significant 2 bits of JCW when creating a process,
and examines these 2 bits after the process terminates.  If these 2 bits
are set then you'll see "Program aborted per user request".  If just the sign
bit is set you'll see "Program aborted in an error state" message.  The
remaining lower 14 bits are user defined.

regards,
Jeff Vance, CSY

--