On Wed, 24 May 2017 21:28:26 +0200, Peter Hunkeler wrote:
>> The above is why I really "push" the UNIX fork() alternative.
>[snip]
>
>>If a "steplib" is needed, the initial child program can simply DYNALLOC the
>>DSNs and then use an ATTACHX with a TASKLIB.
>
>Assuming there will be an exec() in the forked process, a steplib can be setup
>simply by setting the STEPLIB environment variable, and passing that to exec().
>
More DDNAMEs that STEPLIB are useful. TSOALLOC addresses this only for
the TMP invoked from UNIX.
There should be a facility (subroutine or task) alin to TSOALLOC that
performs a list of BPXWDYN commands passed to it as an argument.
o It should be safely usable in either an authorized or an unauthorized
address space. What would be the risks if an authorized program
invoked BPXWDYN witn an argument string passed by an unauthorized
program? Clearly, the initiator deals with this: an unprivileged user
can code DD statements with DISP=(OLD,DELETE) and allocation and
SAF prevent any damage.
o It should support mixed concatenation of UNIX and Classic files which
TSOALLOC doesn't support.
( Hmmm. I see:
z/OS TSO/E Command Reference
TSO/E commands and subcommands
ALLOCATE command
ALLOCATE command syntax
Read syntax diagramSkip visual syntax diagram
>>-+-ALLOCATE-+------------------------------------------------->
'-ALLOC----'
>--+-+-+-DATASET-+--(--+-*----------+--)-+--+------------------------+-+-><
| | '-DSNAME--' | .--------. | | '-+-FILE---+--(--name--)-' |
| | | V | | | '-DDNAME-' |
| | '---dsname-+-' | |
| '-DUMMY-----------------------------' |
'-+-FILE---+--(--name--)--+-----------------------------------+-----'
'-DDNAME-' +-+-DATASET-+--(--+-*----------+--)-+
| '-DSNAME--' | .--------. | |
| | V | | |
| '---dsname-+-' |
'-DUMMY-----------------------------'
Why do they tell me this twice? Isn't it just saying that DSNAME and
DDNAME may appear in either order? But isn't that generally true for
keyword command operands? )
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
