|
Ken and Simon, thanks for the answers. They cleared the fog in this brain. As you pointed out even if the workstn file is program described the workstn file has to have a display file, and it looks for a file with the program's name + FM on the end. Even though it said SCREEN in the program it wasn't using SCREEN. Simon, why quit? These are the level of problems I can handle. --------------------------------------------------------- Booth Martin http://www.MartinVT.com Booth@xxxxxxxxxxxx --------------------------------------------------------- -------Original Message------- From: RPG programming on the AS400 / iSeries Date: Monday, October 27, 2003 11:44:34 PM To: RPG programming on the AS400 / iSeries Subject: Re: program described workstn file: On Tuesday, October 28, 2003, at 09:58 AM, Booth Martin wrote: > FSCREEN CF F 600 WORKSTN > > This compiles but won't run. At runtime it tells me it can't find > SCREEN. > Well of course it can't. SCREEN is program described. Any idea how > to fix > this problem? This is no different from a program-described printer file. The file layout is described in the program but you still need a printer file object (e.g., QSYSPRT). So too here you still need a display file object. CRTDSPF SCREEN will do it. You can specify whatever device parameters you need. > (I know, I know. Who makes program described screens. Well, in 1983 > that > was the only choice. Now I have to maintain it. :( I reckon I'd quit! Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.