|
|
|
A user session can concurrently execute any number of REXX processes. Any number of these REXX processes can request that external programs be called.
To provide isolation between REXX processes, each REXX process that requests external programs has a private task attached. This task is used to call external programs, including interfaces to CA Technologies products.
The task stays running until the REXX process is terminated, or an ABEND occurs in an external program.
The external program can use REXX services (such as IRXUID) to obtain the user ID of the owning user (for example, to issue RACROUTE requests).
Note: The task has not had an ACEE representing the user anchored.
By using a separate task, any waits, delays, loops, and so on, in the external program do not affect other users.
Note: If the REXX process terminates, the subtask is detached. Any resources allocated by the external program are cleaned up. For example, storage obtained through GETMAIN in a non-shared subpool is released. If the external program has attached further tasks, these tasks are force-terminated (A03 ABENDs). Resources not associated with tasks stay allocated (for example, dynamically allocated data sets).
| Copyright © 2009 CA. All rights reserved. |
|