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 for ISPF system-related uses. User written dialogs must avoid creating 
or manipulating variable names that start with Z unless their use has been 
clearly documented.



Groete / Greetings
Elardus Engelbrecht

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


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

2018-04-13 Thread Dyck, Lionel B. (TRA)
That is exactly correct - never use a variable that begins with 'Z' when coding 
an ISPF application.

Something that I forgot :(

--
Lionel B. Dyck (Contractor)  <
Mainframe Systems Programmer – RavenTek Solution 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, 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...

--
Jeremy Nicoll - my opinions are my own.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


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...

-- 
Jeremy Nicoll - my opinions are my own.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


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  and that test was failing. So I made a copy of the 
panel and put  within the panel and noticed that it had a value of z/OS. This 
got me to looking and with PDSEGEN 5.3.0 I had to add code to test for ISPF for 
z/OS 2.1 and I used a parse of the variable ZISPFOS and used "parse value 
ispfzos with x y z v'.'r'.'m" which resulted in variable z having the value of 
z/OS which broke the ISPF Panel test "IF ( NE ) ...".

Thus PDSEGEN 5.3.1 fixes this and I know now never to have a variable within 
any ISPF application of z.

You've been warned.

You can get PDSEGEN 5.3.1 starting after 5pm on 4/12/18 at www.lbdsoftware.com

--
Lionel B. Dyck (Contractor)  <
Mainframe Systems Programmer - RavenTek Solution Partners


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN