Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Format of the work block extension z/OS TSO/E REXX Reference SA32-0972-00 |
|||||||||||||||||||||||||||||||||||||||||||||||||
The work block extension contains information about the REXX exec that is currently running. The environment block points to the work block extension. When IRXINIT first initializes a new environment and creates the environment block, the address of the work block extension in the environment block is 0. The address is 0 because a REXX exec is not yet running in the environment. At this point, IRXINIT is only initializing the environment. When an exec starts running in the environment, the environment block is updated to point to the work block extension describing the exec. If an exec is running and invokes another exec, the environment block is updated to point to the work block extension for the second exec. The work block extension for the first exec still exists, but the environment block does not point to it. When the second exec completes and returns control to the first exec, the environment block is changed again to point to the work block extension for the original exec. The work block extension contains the parameters that are passed to the IRXEXEC routine to invoke the exec. You can call IRXEXEC explicitly to invoke an exec and pass the parameters on the call. If you use IRXJCL, implicitly or explicitly invoke an exec in TSO/E, or run an exec in TSO/E background, the IRXEXEC routine always gets control to run the exec. Exec processing routines - IRXJCL and IRXEXEC describes the IRXEXEC routine in detail and each parameter that IRXEXEC receives. Table 1 shows the format of the work block extension. TSO/E provides a mapping macro, IRXWORKB, for the work block extension. The mapping macro is in SYS1.MACLIB.
|
Copyright IBM Corporation 1990, 2014
|