On Wed, 26 Apr 2017 20:53:14 -0400, Tony Harminc wrote:
>
>> Is that intended to exclude NFS files (and possibly others) which
>> don't support zFS extended attributes? (Don't know about TFS.)
>
>Not explicitly. But I can't imagine a product the customer knows is going
>to run as a z/OS started task with significant performance requirements is
>going to decide to put a transaction-containing file on an NFS server on a
>Linux box across the country. Nor, for that matter, are they going to make
>it a temporary file.
>
All true predicated on the assumption of "started task with significant
performance requirements" or transaction processing.
>>What about sockets? Can SVC 99 allocate a DDNAME to a socket?
>
>I'm willing to bet not. Can JCL?
>
JCL, I'd bet not because the socket would have to be opened before
step initiation. SVC 99, I'd be less certain:
o A socket can have a descriptor.
o DYNALLOC can allocate to PATH('/dev/fd/'descriptor). I've done this
with unnamed pipes created after step initiation; never tried with sockets.
Are you suggesting that SVC 99 can allocate only objects that could as
well have been allocated with JCL?
(Things that can be allocated with JCL but not with DYNALLOC include
passed data sets. Probably.)
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
