On Friday, October 18, 2024 at 09:57:22 PM PDT, Jim Mulder <[email protected]> wrote:
> A supervisor state or system key program could specify DISP=NO on ATTACH > For a problem program, the only thing that can set something in storage > created by ATTACH before the attached task can run is ATTACH itself. These techniques can be used but why make it complicated. As I said before, ATTACH PARAM= is passed in R1 which doesn't need serialization because it was created before ATTACH but must exist as long as it can be referenced (typically the entire life of task especially if used by EXTR). Most flexible would be a CB that covers all functionality provided by the task because EXTR can cleanup all resources for the task (e.g. DCB's, various status flags, ...). Since you saved regs upon startup, R1 (attach parm) can easily be found in TCBFSA (First Save Area).
