Re: [EXTERNAL] Re: ISPF Application - a warning

2018-04-13 Thread Elardus Engelbrecht
Dyck, Lionel B. (TRA) wrote: >That is exactly correct - never use a variable that begins with 'Z' when >coding an ISPF application. This is documented in "z/OS ISPF Dialog Developer's Guide and Reference" Note: ISPF uses variable names that start with Z. Therefore, Z variables are reserved

Re: [EXTERNAL] Re: ISPF Application - a warning

2018-04-13 Thread Dyck, Lionel B. (TRA)
tion Partners -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jeremy Nicoll Sent: Friday, April 13, 2018 4:34 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: ISPF Application - a warning On Thu, 12 Apr 2018, at 19:08, Dyck, L

Re: ISPF Application - a warning

2018-04-13 Thread Jeremy Nicoll
On Thu, 12 Apr 2018, at 19:08, Dyck, Lionel B. (TRA) wrote: > Thus PDSEGEN 5.3.1 fixes this and I know now never to have a variable > within any ISPF application of z. I have a feeling that one is meant to avoid any variable name that starts with Z too... so no "ZERO" or "ZORRO" or... -- Jere

ISPF Application - a warning

2018-04-12 Thread Dyck, Lionel B. (TRA)
I ran across an interesting bug today - found that in PDSEGEN 5.3.0 that edit cancel was failing. I even opened a PMR on it as I couldn't figure it out - complete with ispvcall traces. Then I did some digging and found the edit cancel panel - ISRECFM - and noticed that it was testing for &Z and