This is the right answer, sort of. The behavior is a bug in V3R1M2. It's fixed in V3R1M3, but I didn't see it mentioned in any of the APARs. I was able to isolate the bug. When you first start using a display file, Client Access will not display _any_ attributes (only plain green text) until you display a record with either an input or input/output field. In addition, any records without input or input/output fields may redraw incorrectly whenever the display is restored. You can workaround the bug by adding protected input fields to output-only records. You can't workaround it by adding hidden or program-to-system fields. If you have menu screens where the attributes/colors don't always display correctly, this is why. Get V3R1M3. (Real terminals and Rumba don't have this problem.) Like I said, I'm new to the AS/400. This was a rude awakening. I would have thought IBM would catch a bug like that before they shipped a product.

---

check yout PTF's on Client Access.

---

Check to see what the AS/400 thinks your device is. It may have been told that you are running a one-color terminal.

---

Normally you shouldn't do anything special. The problem is probably caused by a wrong device type (left behind from previous setups). I would suggest to check which device you're using (try DSPJOB and look at the jobname), and delete this (from another screen) so that it will be recreated when CA is started again. If this doesn't help, specify the connection method and versions used.

---