Walt, I think the message from the customers is that they would be happy to accept "your gun, your bullet, your foot." Customers want these symbols available. If they have a Sysplex and set the dates very differently, well then, they may see some odd date things happening.
I know also that it's easy for customers to assert the above today, but open a PMR tomorrow when they encounter some anomaly. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Walt Farrell Sent: Wednesday, November 30, 2005 9:21 AM To: [email protected] Subject: Re: Using symbolic in JCL On 11/30/2005 11:24 AM, [EMAIL PROTECTED] wrote: > 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 Unfortunately, since different systems in a sysplex (or sharing the spool) could have very different times and dates, they could get very unexpected results if we let those symbols be used in batch job JCL. Suppose the job converted on a system where the date is today, and ran on a system where the date is several days, or weeks, ago. (The normal ---------------------------------------------------------------------- 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
