In a recent note, "Shmuel Metz (Seymour J.)" said: > Date: Tue, 24 Apr 2007 15:56:06 -0300 > > >channel programs addressed to any member-protected PDS. The change > >would examine all CCWs to make sure the channel program was going to > >process a member the user was allowed to use. > > That would require reading the entire member in order to determine > where to set the limits. > Not if the changes also retained information about where each member ends. After all, we're talking about massive changes to PDS processing. Why stop halfway?
I believe it's agreed that there are ISV products that provide member-level protection. How do they do it? I believe I've heard also of ISV products that track unused space in PDSes. How do they do that? Knowing where each unused area begins would be sufficient information to deduce where any member ends (the upper limit). -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
