Re: Display file puzzlement

[John McKee <jmmckee@xxxxxxxxxxxxxx>]

Interesting....your example works exactly as you describe.  BUT, when I add
COLOR(YLW) or COLOR(BLU) to the first data field, that field does not dp RI.

We don't use PC5250.  My computer has Reflection 7.0.  Shop standard is that
input fields use COLOR(YLW).  Having only tried two colors on the first field,
it may be inaccurate to make a definitive statement, but it appears that COLOR
messes things up in this case.  But, the application package we use has a
multitude of screens where fields are sent as RI when they were coded 
as YLW. Just scanned the vendor display file sources.  Out of a couple 
of jundred
screens, one once is ERRSFL used.  I am not familiar with the program 
that uses
the screen with ERRSFL.  Possibly, it does not work "properly" either.

At least, I now have a better understanding of why some keywords might not be
used.  No matter how practical and nice the intended results might 
normally be.

I am wondering, however, if this behavior is specific to Reflection 7.0 
or if it
applies to othre versions or emulators.

John McKee

Quoting Simon Coulter <shc@xxxxxxxxxxxxxxxxx>:

> On 22/04/2008, at 4:02 AM, John McKee wrote:
> > I removed PUTOVR, OVRATR, and OVRDTA.  Still no RI capability.  With
> > the ERRSFL,
> > though, I guess I can live with it.
>
> You can have these keywords in the file as long as they are not
> active at the same time as ERRMSG. It appears that ERRMSG takes
> precedence. In all these cases the correct analysis is to create a
> test-case that does what you want to determine exactly where the
> problem lies without all the application rubbish getting in the way.
>
> Try the following:
>
> DSPF TSTERRSFLD
> *************** Beginning of data
> ********************************************
>      A                                      DSPSIZ(24 80 *DS3)
>      A                                      CA03(03 'Exit')
>      A                                      ERRSFL
>      A          R THEFORMAT
>      A                                  1 35'Test ERRSFL'
>      A                                      DSPATR(HI)
>      A                                  3  2'Type bad data, press
> Enter.'
>      A                                      COLOR(BLU)
>      A                                  5  5'Have a go ya
> mug . . . . . . .'
>      A            DATA1         10   B  5 37
>      A  98                                  ERRMSG('Bzzt! Wrong
> answer!' 98)
>      A                                  7  5'Have another
> go  . . . . . . .'
>      A            DATA2         10   B  7 37
>      A  99                                  ERRMSG('Bzzt! Wrong
> again!' 99)
>      A                                 23  2'F3=Exit'
>      A                                      COLOR(BLU)
> ****************** End of data
> ***************************************************
>
> RPGLE TSTERRSFLR
> *************** Beginning of data ***********************************
> FTSTERRSFLDCF   E             WORKSTN
> C                   EXFMT     THEFORMAT
> C                   SETON                                        9899
> C                   DOU       *IN03 = *ON
> C                   EXFMT     THEFORMAT
> C                   ENDDO
> C                   SETON                                        LR
> ****************** End of data **************************************
>
> Compile the display file and the RPG. Call the RPG. Press Enter. You
> should see both input fields reverse-imaged, the cursor should be in
> the first field, both error messages should be displayed in the error
> sub-file at the bottom of the screen.
>
> If this is not happening for you then:
> 	1) Check the settings in your emulator--it is possible that RI is
> mapped to something else
> 	2) If not using PC5250 then start using it
> 	3) Check the parameters on the CRTDSPF command are the IBM-shipped ones
> 	4) Check the device type being emulated--it is possible that you are
> emulating a device without RI capability (though unlikely)
> 	5) Check for PTFs--perhaps the 5250 data stream is wrong (again
> unlikely)
>
> I expect that my example code will work correctly indicating the
> problem is in your application display file or code.
>
> Regards,
> Simon Coulter.
> --------------------------------------------------------------------
>    FlyByNight Software         OS/400, i5/OS Technical Specialists
>
>    http://www.flybynight.com.au/
>    Phone: +61 2 6657 8251   Mobile: +61 0411 091 400        /"\
>    Fax:   +61 2 6657 8251                                   \ /
>                                                              X
>                  ASCII Ribbon campaign against HTML E-Mail  / \
> --------------------------------------------------------------------
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.