Paul [Gilmartin], The anomaly that both &&<dsn value> and &<dsn value> are recognized reflects the historical evolution of JCL. In the beginning was the word, but single JCL parameter values were not replaceable. It was necessary to supply an entire 'overriding' JCL statement. The [only] function of '&' in this context was to identify a temporary DSN value.
Then when the facility for overriding single keyword parameter values was introduced the new convention that && denoted a temporary DSN[ame] was also introduced. Understandably but unfortunately, the context-sensitive recognition of &<dsn> was retained to avoid making much already written JCL obsolete and unusable. The result is not pretty, but it is more 'defensible' than you suggested. We have had enough of the characterization of Paul Gilmartin as an intelligent, recently arrived Martian; but your synchronic view of things does sometimes jar. John Gilmore, Ashland, MA 01721 - USA ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
