On Tue, 2 Jun 2015 07:49:47 -0500, Joel Ewing wrote:
>
>It doesn't have to be a difference in TCB structure that makes this
>behavior of IKJEFT01 vs. IKJEFT1A/IKJEFT1B different, but if you avoid
>executing the commands directly under the TMP --e.g., by executing them
>from within a REXX EXEC -- you can circumvent that behavioral
>difference. I think one adds a TCB by invoking a REXX EXEC, but
>probably more significantly it's no longer the TMP that sees the TSO
>Command return code for commands within the EXEC. The interpretation of
>whether a non-zero return code is or is not a fatal error is solely at
>the discretion of the calling program, and IKJEFT1A/IKJEFT1B appear to
>be designed to regard any non-zero return code they see as fatal.
>
I consider it a design shortcoming that an EXEC can't set the return code
for the IKJEFT01 step. If it were supported, this could be as simple as:
address TSO 'LOGOFF' code
... causing the job step to complete with "code" in R15.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
