|
>> The Display file references this field. The dspf won' compile. For reasons that I do not understand Varying fields are not supported on display files (unless there's some secret I don't know). You have two options, use a fixed field and eval the contents of the display field from the varying. On return remember to do varying = %TrimR(fixed). The alternative - which avoids the outbound assignment but not the inbound trim - is to map the fixed portion of the varying field with the name used on the display - like so: D DS D Varying 40a Varying D DispField 40a Overlay(Varying:3) /free ExFmt Whatever; // format Whatever uses "DispField" Varying = %TrimR(DispField); // Trim content on input (use %Trim if reqd) I understand your frustration with InfoCenter on this topic. The only good thing I can say is that at least the DDS reference comes up about number 7 in the list now. When I tried it on V5R1 it came up (I think) number 22 after goodness knows how many references to Tivoli among other nonsense. I finished up in the Rochester Usability Lab after a little tirade on that subject. I think the main problem is that all indexed words keywords have equal weight to the search engine - they are supposed to be looking at it - but it is an IBM standard search engine and it is pretty awful. I now use Google and restrict the search to the ibm.com domain. Most searches produce the right answer in the first few hits. Note to IBM - "Buy Google"! Jon Paris Partner400
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.