|
Jim, This is a classic PITA with the dual format display files. It's extremely rare that I work on these, but I do have a working app that uses it; since it's been several years since I last worked on it, I won't be able to explain why my code "makes" it work. So experiment at your leisure (like I did <g>). File level: A DSPSIZ(27 132 *DS4 - A 24 80 *DS3) Subfile Control Records: A R SFLCTL27 SFLCTL(SFL27) A *DS4 SFLSIZ(0020) A *DS3 SFLSIZ(0008) A *DS4 SFLPAG(0020) A *DS3 SFLPAG(0008) ... later in this format: A *DS3 5 29 A* A R SFLCTL24 SFLCTL(SFL24) A 69 DSPMOD(*DS3) A *DS4 SFLSIZ(0008) A *DS3 SFLSIZ(0008) A *DS4 SFLPAG(0008) A *DS3 SFLPAG(0008) This seems to be all of the pertinent statements in the display file source. I have no idea why the statement with no field displayed at 5,29 is there, or what it does, or if it even matters. Also, indicator 69 is NOT referenced in the program, so it is always off, so I don't know what it is doing or how it affects the DSPMOD keyword. As you can surmise, I developed separate screens for the 24x80 & 27x132 modes. FYI for others: To determine whether the workstation is *capable* of 27x132, I use the workstation INFDS: d Num_Rows 152 153B 0 d Num_Columns 154 155B 0 d* Num_******* - Returns the size capability of the display d* device; either 24x80 or 27x132 Sorry I can't be of much more help with this. Hopefully, it's enough to get you going. db
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.