Alan, Yes, I know it has been a loooooong time since IBM shipped all the source for a given product. This is when OCO started. So, be it.
The 'inconsistency' is that historically and traditionally anything that IBM provided as a 'SAMPLE' was distributed as source code, be it assembler, rexx or whatever. Hence the implication for SCSIDISC SAMP(ple)EXEC being assumed to be REXX source code and not compiled REXX. Surely the code in SCSIDISC is not proprietary in regards to doing 'I/O' to FCP devices. Linux developers are doing this. Are the QDIO drivers in Linux OCO? HITACHI DATA SYSTEMS Raymond E. Noal Senior Technical Engineer Office: (408) 970 - 7978 -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Thursday, March 19, 2009 5:29 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SCSIDISC SAMPEXEC on z/VM 5.4.0 On Wednesday, 03/18/2009 at 07:15 EDT, Scott Rohling <scott.rohl...@gmail.com> wrote: > That does seem odd.. I would think it would be supplied named as EXEC in that > case.. I agree it implies a 'sample' when named SAMPEXEC .. which is only > useful when the 'sample' is human readable so you can see what a good sample > looks like ;-) > > Inconsistent to say the least, but I'm not aware of the reasons (if any) behind > not releasing the source. Maybe Chuckie knows.. ? We use filetype SAMPxxxx to indicate that the item is not a supported/documented part of the product, but is something we provide for you to use. Sometimes the point is the source, demonstrating how to do something, and other times it is the functionality. SCSIDISC falls into the latter category. It has been a loooong time since we shipped the source to everything in the product, so I'm not sure what is "inconsistent." Alan Altmark z/VM Development IBM Endicott
