Sure they are trivial - until we move into an environment where there are multiple DASD sizes with different optimal BLKSIZE needs. The programmer shouldn't care what disk his files are in - the systems people should have the ability to quickly and easily move the files depending on current needs. When they move them, they should be able to adjust the buffering without recompiling and changing JCL.
I don't understand what you're talking about. In today's world there is no need for an application's programmer to know anything about BLKSIZE beyond what the installation demands. Utilities can certainly move data between different geometries and handle the reblocking without intervention. The JCL and program don't need to specify a blocksize since the DSCB provides such information. Where exactly is all the effort?
Whether the programmer should care or not is irrelevant. In most cases, they actually don't know which means that your point has already been made. The programmer DOESN'T need to know.
Just a question though.. How many different DASD geometries are being encountered today under z/OS? I am curious about the environment you're suggesting.
Adam ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
