Wild stab in the dark - is the window size defined by a variable that's somehow overwritten by another application using the same variable name?
I've see a few applications that appear to use the same-named ISPF variables, and thus clash when they overwrite each other's variable - the solution is of course to use an application specific profile if you want to store variables (I'm not going to mention applications that store the screen in a variable that becomes too big for the code to handle at my 82x160 screen size - actually, I suppose that should be 160x82 given "x by y"..). Andy Styles z/Series Systems Programmer -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Steve Thompson Sent: 23 March 2016 16:05 To: [email protected] Subject: ISPF Anomaly: ISPP352 -- This email has reached the Bank via an external source -- We are having a bit of a problem with a "pop-up" panel in ISPF. It hasn't been modified for many months, and now today I am getting a report from a user that it is causing the following MSG: ISPP352 Panel 'aaaaaaaa' error - Invalid window depth value (must be numeric, > 0, less than screen depth). I have had this user change their TN3270 geometry and it has no effect (from MOD4 to 160 wide by 62 deep). I am unable to recreate their problem, and I've been working on this application for over a year and haven't seen this before. I have found a few APARs for it, but their circumvention has been to use other than MOD2 (these are IBM panel issues). This is ISPF 7.1, z/OS 2.1. I even had them change their 3270 definition in =0 to be the same as mine, and go to TSO ready and back into ISPF, and it had NO effect. All of this ISPF application has been tested with a MOD3 (we specifically check for less than that and refuse to initialize the application in that case). I have tried IBMLINK searches and I just don't find anything. The window is set to (74,30). So that is 74 wide and 30 lines deep. And SPLIT is not in use, so that does not appear to be the problem. I'm open to diagnostic suggestions. I just don't have time to do an SR for this, because I'm at the end of this project and am going over to the dark side (z/VM). Regards, Steve Thompson ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC95000. Telephone: 0131 225 4555. Lloyds Bank plc. Registered Office: 25 Gresham Street, London EC2V 7HN. Registered in England and Wales no. 2065. Telephone 0207626 1500. Bank of Scotland plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC327000. Telephone: 03457 801 801. Cheltenham & Gloucester plc. Registered Office: Barnett Way, Gloucester GL4 3RL. Registered in England and Wales 2299428. Telephone: 0345 603 1637 Lloyds Bank plc, Bank of Scotland plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and Prudential Regulation Authority. Cheltenham & Gloucester plc is authorised and regulated by the Financial Conduct Authority. Halifax is a division of Bank of Scotland plc. Cheltenham & Gloucester Savings is a division of Lloyds Bank plc. HBOS plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC218813. This e-mail (including any attachments) is private and confidential and may contain privileged material. If you have received this e-mail in error, please notify the sender and delete it (including any attachments) immediately. You must not copy, distribute, disclose or use any of the information in it or any attachments. Telephone calls may be monitored or recorded. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
