Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Scoping Rules - Subprocess/Related/Detached | ||||||||
Line: 11 to 11 | ||||||||
| ||||||||
Changed: | ||||||||
< < | DETACHED workfields/tempfiles survive DETACHED process invocations. RELATED and SUBPROCESS level files/fields don't. DETACHED workfields/tempfiles only reinitialize when the user exits APPX. | |||||||
> > | DETACHED workfields/tempfiles survive DETACHED process invocations. RELATED and SUBPROCESS level files/fields don't. DETACHED workfields/tempfiles initialize on the next invocation of a DETACHED proces. | |||||||
DETACHED and RELATED workfields/tempfiles survive RELATED invocations. SUBPROCESS level files/fields don't. | ||||||||
Line: 29 to 29 | ||||||||
Query(Runtime) inherits inbound workfields/tempfiles only from its associated Query(Setup). It can pass nothing to any subsequent JOB step. The exception to this is that --- PROCESS CODE can be used to pass limited information into and out of Query processes. But --- PROCESS CODE should only be used for SPEED II compatibility issues. See ECR #2805 for further explanation.
Exception #2: | ||||||||
Changed: | ||||||||
< < | No workfield or tempfile information can 'come back' from a JOB step whose 'Sep Tsk?' (Separate Task) flag is set to 'Y'. This is because a JOB step process that could be spawned into an independent thread has no facility for communicating back to the original parent process, save by means of a disk/permanent file. See How APPX spawns Background processes for further discussion. | |||||||
> > | No workfield or tempfile information can 'come back' from a JOB step whose 'Sep Tsk?' (Separate Task) flag is set to 'Y'. This is because a JOB step process that could be spawned into an independent thread has no facility for communicating back to the original parent process, save by means of a disk/permanent file. See APPX Background Processing for further discussion. | |||||||
Comments: |