In a recent note, Peter Relson said: > Date: Wed, 30 Nov 2005 09:09:16 -0500 > > >What about &SYSUID? > > &SYSUID is not what we refer to as a "system symbol" for the purposes of > the discussion. If it is not in the list of symbols defined for ASASYMBM > (or added by the system when it invokes ASASYMBM), then it is not a "system > symbol" in this regard. > In that case, a multitude of customers would be delighted to see the date and time symbolics moved from the class of "system symbols" to the same class as &SYSUID, whatever you call the class. I understand (but don't necessarily agree with) the concern over the ambiguity over system names. But the difference between Reader time, Converter time, and Interpreter time is different in character, and exists even now, even for STCs. If an STC started just before midnight incorporates the date system symbol in a data set name, that name may disagree with the timestamp stored with the data set.
Most users don't care about such microscopic precision; IBM should relent its intransigence and make at least the date and time symbols available in batch JCL, with the stipulation that the values of such symbols reflect the reader environment, not any other. -- 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
