Re: Device Independence

2018-01-31 Thread Seymour J Metz
SEMBLER-LIST@listserv.uga.edu Subject: Re: Device Independence On 2018-01-30, at 21:30:33, Jon Perryman wrote: >> Steve Thompson wrote:> It causes me to wonder, why DSORG causes a problem >> with a path or > >> a file. After all, unless you know something special about the >> f

Re: Device Independence

2018-01-31 Thread Seymour J Metz
: IBM Mainframe Assembler List <ASSEMBLER-LIST@listserv.uga.edu> on behalf of Steve Smith <sasd...@gmail.com> Sent: Wednesday, January 31, 2018 9:42 AM To: ASSEMBLER-LIST@listserv.uga.edu Subject: Re: Device Independence I suppose you might be kidding, but outside evidence is inconclu

Re: Device Independence

2018-01-31 Thread Steve Smith
I suppose you might be kidding, but outside evidence is inconclusive. Gil's point was clear: IBM is inconsistent with their "rules" about REXX OPEN, and he demonstrated they are also obtuse. btw, I can easily imagine a KSDS being used as a PDS; for a large number of smallish members, it's

Re: Device Independence

2018-01-30 Thread Jon Perryman
>> Jon wrote: >> Programs do not access Unix files. Specifying path >> causes a Unix address space to handle the file. >> It communicates with the program thru the subsystem file> Paul wrote: > Isn't the same true for JES files? Yes > Paul wrote: > Spitefully, I tried a concatenation of a

Re: Device Independence

2018-01-30 Thread Paul Gilmartin
On 2018-01-30, at 21:30:33, Jon Perryman wrote: >> Steve Thompson wrote:> It causes me to wonder, why DSORG causes a problem >> with a path or > >> a file. After all, unless you know something special about the >> file, aren't all files DSORG=PS -- Physical Sequential in EXT, >> I believe

Re: Device Independence

2018-01-30 Thread Jon Perryman
> Steve Thompson wrote:> It causes me to wonder, why DSORG causes a problem > with a path or  > a file. After all, unless you know something special about the > file, aren't all files DSORG=PS -- Physical Sequential in EXT, > EXT2, btrfs, hfs, zfs, etc.?  Ok, in hfs and zfs they are >

Re: Device Independence

2018-01-30 Thread Steve Thompson
On 01/30/2018 03:43 PM, Paul Gilmartin wrote: On 2018-01-30, at 13:33:24, Jon Perryman wrote: Jon wrote: If you specified the attributes needed, then you would not need concatenated datasets. > Paul wrote: No, I have tried TRSMAIN UNPACK with a single UNIX file as archive. FILEDATA, RECFM,

Re: Device Independence (was: Fair ... C vs HLASM)

2018-01-30 Thread Paul Gilmartin
On 2018-01-30, at 13:33:24, Jon Perryman wrote: >>> Jon wrote: >>> If you specified the attributes needed, >>> then you would not need concatenated datasets. > Paul wrote: > >> No, I have tried TRSMAIN UNPACK with a single >> UNIX file as archive. FILEDATA, RECFM, LRECL, BLKSIZE >> all

Re: Device Independence (was: Fair ... C vs HLASM)

2018-01-30 Thread Paul Gilmartin
On 2018-01-30, at 11:20:10, Jon Perryman wrote: > >> Paul wrote: >> I can fool it by prefixing an empty temp Classic PDS. > Open uses the first dataset in concatenated datasets to fill in the DCB. The > second DD must be able to tolerate the DCB attributes from the first dataset. > The classic

Re: Device Independence (was: Fair ... C vs HLASM)

2018-01-29 Thread Paul Gilmartin
On 2018-01-29, at 23:00:25, Jon Perryman wrote: >> Paul Gilmartin wrote: > >> The design integrity of OS/360's I/O architecture has been much >> compromised with the advent of utilities which gratuitously >> (sometimes with a goal of performance) enforce device dependence. >> Such utilities

Re: Device Independence (was: Fair ... C vs HLASM)

2018-01-29 Thread Jon Perryman
> Paul Gilmartin wrote: > The design integrity of OS/360's I/O architecture has been much > compromised with the advent of utilities which gratuitously > (sometimes with a goal of performance) enforce device dependence. > Such utilities should at least support, if possible, a fallback > to