(IBM Mainframe Discussion List) wrote:
It simply caches the new TTR value -- like always.
It would seem that a validation against the maximal TTR would be friendlier
than simply caching the new value and letting program fetch break some
unpredictable time later.
IBM recommends no secondary extent allocation for data sets on LNKLST.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
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
