|
I only have one record format to write, that is the MSGSFLCTL. The MSGSFL is the error message subfile. In this record format I don't have a subfile so I don't have separate formats. There is only one and it contains the record for I/O as well as the message subfile. But I don't see any message, though I do see the F-Key Legend on line 23. Marvin -----Original Message----- From: rpg400-l-bounces+mradding=dpi-west.com@xxxxxxxxxxxx [mailto:rpg400-l-bounces+mradding=dpi-west.com@xxxxxxxxxxxx] On Behalf Of Jerry Adams Sent: Thursday, September 29, 2005 8:23 AM To: RPG programming on the AS400 / iSeries Subject: Re: Call RPG Service Program from CLLE Marvin, There are probably a thousand ways to write programs with message subfiles. What I see below is only the definition of the message subfile, not the body of the display. While the OVERLAY in the message subfile control may or may not be necessary, in the body of the display you definitely need the OVERLAY keyword on the displays which follow the WRITE of the message subfile. A big mistake that I'll make (heaven only knows how many times) is putting my function key legend (the main body) on Line 24. Even with OVERLAY this hides the messages. * Jerry C. Adams *iSeries/i5 Programmer/Analyst B&W Wholesale Distributors, Inc.* * voice 615.893.8633x152 fax 615.995.1201 email jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx> Marvin Radding wrote: >Actually, I don't have two record formats here but one. The MSGCTL >record is header which contains all of the input fields and the MSGSFL >is the error message subfile. So I don't need the overlay keyword >because there is only one write required to put on the screen the input >fields and the message subfile. > >Marvin > > >-----Original Message----- >From: rpg400-l-bounces@xxxxxxxxxxxx >[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of RPower@xxxxxxxxxx >Sent: Wednesday, September 28, 2005 10:49 AM >To: RPG programming on the AS400 / iSeries >Subject: Re: Call RPG Service Program from CLLE > >You might be missing the OVERLAY keyword. I couldnt' get error messages > >to show without it. > > >A R HEADER SFLCTL(SFLHDR) >************************************************ >A OVERLAY >************************************************ >A SFLDSP >A SFLDSPCTL >A SFLINZ >A 99 SFLEND >A SFLSIZ(0002) >A SFLPAG(0001) >A PGMQ SFLPGMQ(10) >A #POSITION 4S 0H >A #FIELD 10A H >A #RECORD 10A H >A 1 3DATE > >Ron Power >Programmer >Information Services >City Of St. John's, NL >P.O. Box 908 >St. John's, NL >A1C 5M2 >709-576-8132 >rpower@xxxxxxxxxx >http://www.stjohns.ca/ >_______________________________________________________________________ _ >___ >Success is going from failure to failure without a loss of enthusiasm. - > >Sir Winston Churchill > > > > >"Marvin Radding" <MRadding@xxxxxxxxxxxx> >Sent by: rpg400-l-bounces@xxxxxxxxxxxx >2005/09/28 02:54 PM >Please respond to >RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> > > >To >"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx> >cc > >Subject >Call RPG Service Program from CLLE > > > > > > >I am using the ISTKT and attempt to use the MSGTKT. I want to send >error messages to the display file via the SNDMSG service program. > >I call SETDFTPGMQ: > >CALLPRC PRC(SETDFTPGMQ) PARM('RMR00100C') > >I call SNDMSG: > >CALLPRC PRC(SNDMSG) PARM('CPD006' ' Invalid + > Function Key') RTNVAL(&MSGKEY) > >I have the MSGSFL defined: > >A R SFLHDR SFL >A SFLMSGRCD(24) >A MSGKEY SFLMSGKEY >A PGMQ SFLPGMQ(10) > >I have the MSGSFLCTL defined: > >A R HEADER SFLCTL(SFLHDR) >A SFLDSP >A SFLDSPCTL >A SFLINZ >A 99 SFLEND >A SFLSIZ(0002) >A SFLPAG(0001) >A PGMQ SFLPGMQ(10) >A #POSITION 4S 0H >A #FIELD 10A H >A #RECORD 10A H >A 1 3DATE > >Can anyone see what I am missing. I see no messages at the bottom of >the screen except when the system displays job complete messages. > >Before I lose what little hair I have left, can anyone help? > >Marvin > > > > >
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.