symbol.
But doesn't line 2 set MYSYM to 'INITVAL'?
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Bass, Walter W
Sent: Wednesday, July 18, 2012 10:33 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Unsetting a JCL symbol.
Paul,
Note in your
On Wed, Jul 18, 2012 at 5:37 PM, Bass, Walter W bill_b...@uhc.com wrote:
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
Just curious.
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?
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
On 7/17/2012 3:08 PM, Paul Gilmartin wrote:
Just curious.
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?
-- gil
Use nested procs.
--
Kind regards,
-Steve Comstock
The Trainer's Friend, Inc.
] On
Behalf Of Paul Gilmartin
Sent: Tuesday, July 17, 2012 5:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Unsetting a JCL symbol.
Just curious.
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?
-- gil
On Tue, 17 Jul 2012 16:43:32 -0500, Bass, Walter W wrote:
Try this ...
//* SAVE CURRENT VALUE OF MYSYM
// SET SAVESYM=MYSYM
//* SET MYSYM TO A NEW VALUE
// SET MYSYM='NEWVAL'
...
//* RESTORE MYSYM
// SET MYSYM=SAVESYM
Probably not the answer you wanted, but it works.
Actually,
This is one of many such discussions we have had here over the years.
Symbols were a good notion, or wouild have been if they had been
implemented more generously. They were not, and anyone who, seeing
simplistic uses of them, dreams of using them in more interesting,
non-trivial ways is almost
