Re: Really dumb CLIST question

2010-10-08 Thread Shmuel Metz (Seymour J.)
In listserv%201010042257331476.0...@bama.ua.edu, on 10/04/2010 at 10:57 PM, Paul Gilmartin paulgboul...@aim.com said: CLIST makes it real hard to even know what the value in a variable is. CLIST makes a lot of things real hard; Rexx is a much better language. -- Shmuel (Seymour J.)

Re: Answered: Really dumb CLIST question

2010-10-06 Thread Shmuel Metz (Seymour J.)
In listserv%201010042237560303.0...@bama.ua.edu, on 10/04/2010 at 10:37 PM, Paul Gilmartin paulgboul...@aim.com said: And this is to be further tailored by customers. Here, the significant advantage of CLIST over Rexx is in avoiding the apostrophe catastrophe. As opposed to the Ampersand

Re: Answered: Really dumb CLIST question

2010-10-06 Thread Ricc Harding
in generated JCL use ...NOTIFY=STR(amp;)STR(SYSUID) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at

Re: Answered: Really dumb CLIST question

2010-10-05 Thread Donald Johnson
Code it as SYSUID? *don* On Mon, Oct 4, 2010 at 11:37 PM, Paul Gilmartin paulgboul...@aim.comwrote: On Mon, 4 Oct 2010 20:16:06 -0500, Paul Gilmartin wrote: How can I set a symbolic variable to the null string? Thanks to Dave Salt: SET X = Z /* Works as long as Z is undefined. */

Re: Answered: Really dumb CLIST question

2010-10-05 Thread Mark Zelden
On Mon, 4 Oct 2010 22:37:56 -0500, Paul Gilmartin paulgboul...@aim.com wrote: Now I need to figure out how to get SYSUID into tailored JCL without CLIST evaluating it. Not sure if this will come out correctly since I am posting from the web interface, but here is an example from an edit macro

Re: Answered: Really dumb CLIST question

2010-10-05 Thread Mark Zelden
On Tue, 5 Oct 2010 07:56:36 -0500, Mark Zelden mzel...@flash.net wrote: Not sure if this will come out correctly since I am posting from the web interface, but here is an example from an edit macro that creates a job card: ISREDIT LINE_AFTER 1 = STR('// NOTIFY=amp;amp;SYSUID,REGION=7M') In

Re: Really dumb CLIST question

2010-10-05 Thread Lizette Koehler
I like languages that report error on reference to undefined variables. Now I'll see whether I can figure out STR() and get PERPETRATOR = amp;SYSUID ISREDIT LINE BEFORE = STR(// NOTIFY=PERPETRATOR,) or some such to work. CLIST makes it real hard to even know what the value in a

Re: Really dumb CLIST question

2010-10-05 Thread Steve Comstock
On 10/5/2010 7:08 AM, Lizette Koehler wrote: I like languages that report error on reference to undefined variables. Now I'll see whether I can figure outSTR() and get PERPETRATOR =amp;SYSUID ISREDIT LINE BEFORE =STR(// NOTIFY=PERPETRATOR,) or some such to work. CLIST makes it real

Re: Really dumb CLIST question

2010-10-05 Thread Mark Zelden
On Tue, 5 Oct 2010 07:25:58 -0600, Steve Comstock st...@trainersfriend.com wrote: ITYM NRSTR so: ISREDIT LINE BEFORE = NRSTR(// NOTIFY=SYSUID) might do the trick without even needing the intermediate 'PERPETRATOR' variable. That won't work with ISREDIT. The userid will still get

Re: Really dumb CLIST question

2010-10-05 Thread Paul Gilmartin
On Tue, 5 Oct 2010 08:51:27 -0500, Mark Zelden wrote: ITYM NRSTR so: ISREDIT LINE BEFORE = NRSTR(// NOTIFY=SYSUID) might do the trick without even needing the intermediate 'PERPETRATOR' variable. The structure my co-worker bestowed on me is something like: /* Modify the following

Re: Really dumb CLIST question

2010-10-05 Thread Ricc Harding
Is there some reason why you don't initialize it to nulls? SET X = STR() Always set to a known value of nulls... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the

Re: Really dumb CLIST question

2010-10-05 Thread Paul Gilmartin
On Tue, 5 Oct 2010 10:38:51 -0500, Ricc Harding wrote: Is there some reason why you don't initialize it to nulls? SET X = STR() Always set to a known value of nulls... Ignorance. I tried the first thing that occurred to me: SET X = SUBSTR(1:0,junk) ... (why not?) and it failed. I

Really dumb CLIST question

2010-10-04 Thread Paul Gilmartin
Answer offline; don't flood the list. How can I set a symbolic variable to the null string? SET X = '' /* Sets X to two apostrophes. */ SET X = /* Syntax error. */ SET X = SUBSTR(1:0,FOO) /* Syntax error. */ Isn't there a way? Thanks, gil

Re: Really dumb CLIST question

2010-10-04 Thread Chris Mason
Paul What value does a variable have if you don't try to initialise it? This vital information appears to be missing from the obvious place to mention it in the manual and I expect the old TSO CLIST language doesn't use the quixotic REXX rule that you find variables initialised to whatever

Re: Answered: Really dumb CLIST question

2010-10-04 Thread Paul Gilmartin
On Mon, 4 Oct 2010 20:16:06 -0500, Paul Gilmartin wrote: How can I set a symbolic variable to the null string? Thanks to Dave Salt: SET X = Z /* Works as long as Z is undefined. */ Why am I writing CLIST? Well I need to modify a CLIST ISPF EDIT macro. I don't quite own it, so I can't

Re: Really dumb CLIST question

2010-10-04 Thread Steve Comstock
On 10/4/2010 8:14 PM, Chris Mason wrote: Paul What value does a variable have if you don't try to initialise it? This vital information appears to be missing from the obvious place to mention it in the manual and I expect the old TSO CLIST language doesn't use the quixotic REXX rule that you

Re: Really dumb CLIST question

2010-10-04 Thread Paul Gilmartin
On Mon, 4 Oct 2010 21:14:01 -0500, Chris Mason wrote: What value does a variable have if you don't try to initialise it? I found it. It's easy when you know where to look (and the vital line isn't scrolled just off the screen.): z/OS V1R8.0 TSO/E CLISTs