On Mon, 13 Apr 2020 21:50:58 +0000, Seymour J Metz wrote:
>Where does MVS do this? Converter? Interpreter? Initiator? Does SVC 99 also do
>it, and under what TCB?
>Ever notice a typo that you were tempted to leave uncorrected? "Coverter"
>
Yes, it's done pretty covertly.
Authorized Assembler Services Guide for DALPOPT pretty closely
echoes JCL Ref. It doesn't identify TCB.
(More) The description of z/OS UNIX file access attributes - Key = '8019'
doesn't say whether the bits are modified by umask as is the UNIX
convention. Does this go without saying, or should I submit an RCF?
Does the answer apply likewise to BPXWDYN()?
________________________________________
From: Paul Gilmartin
Sent: Monday, April 13, 2020 4:21 PM
On Mon, 13 Apr 2020 19:40:07 +0000, Seymour J Metz wrote:
>Allocation doesn't do an OPEN. But why call an SVC 99 interface to allocate a
>ddname that you plan to never OPEN?
>
Think:
//STEP EXEC PGM=IEFBR14
//DSN DD DISP=(NEW,CATLG),...
//PATH DD PATHOPTS=(OEXCL,OCREAT),...
for why allocate but never OPEN.
From the JCL Ref.:
DD: PATHOPTS
...
And if:
� The file does not exist,
Then MVS performs an open() function. The options from PATHOPTS, the pathname
from the PATH parameter, and the options from PATHMODE (if specified) are used
in the open(). MVS uses the close() function to close the file before the
application program receives control.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
