On 7/17/2012 3:47 PM, Tom Marchant wrote: > > >The > >reason your example does not work is because when lines 3 and 4 are > >evaluated, &MYSYM has not yet been assigned any value, > therefore the JCL > >processor does not yet consider it to be a symbol. > > Right. Paul provided that to show that your "solution" did not > solve the problem that he wanted to solve, as follows: > > On 7/17/2012 3:08 PM, Paul Gilmartin wrote: > >> > >> Once a JCL symbol has been set, is there any way subsequently > >> to restore it to exactly the state and behavior it had before it > >> was set? >
Aha. I get it now. I failed to consider that the initial state of "not defined" was the desired condition to revert to. In fact, I had fully expected that a reference to an uninitialized symbol on the right side of the SET statement would cause a JCL error. That it was instead treated as a literal could perhaps be considered a violation of the "principle of least astonishment". Thanks for setting me straight. Bill This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
