The 80 character focexec line limit in mainframe FOCUS requires that I split my SUBFOOT line specification into two lines of code:

ON MONTH SUBFOOT
"MONTH TOTAL:< ST.FIELD01< ST.FIELD02< ST.FIELD03< ST.FIELD04< FIELD05
< FIELD06< ST.FIELD07< ST.FIELD08< ST.FIELD09< FIELD10< FIELD11"

When I create a FORMAT HTML file, FOCUS sees the spaces following FIELD05 and appears to interpret them as text, resulting in a blank column between FIELD05 and FIELD06. I have tried various combinations of spot markers (<0X, <+0, etc.), and HEADALIGN= parameters [INTERNAL, BODY), but can't hit on one that will tell FOCUS to ignore the blanks following "FIELD05". I even tried the POSITION parameter, though the documentation seems to say that it only applies to PDF files. Someone must have run into this situation before, as it must also apply to SUBHEAD, HEADING, and FOOTING. Any suggestions from the peanut gallery?

This message has been edited. Last edited by: Anonymouse,

Oh crud! The spot markers in my example must have been interpreted as HTML tags!! I'll try to correct....

jeff, put code tags around your code in your post.
just type them in before and after
leftbracket code rightbracket
then
leftracket /code rightbracket

Susannah, I'm not sure about what you mean by "bracket". Tried a few, but settled on inserting some spaces instead.

Everyone, as you look at the SUBFOOT example, keep in mind that the actual code has no spaces after the "<" characters. Thanks.

Jeff,

The bracket to use is the square bracket e.g. [
Use [ code ] and [ /code ] without the spaces or disable HTML in the options list when you construct your post. If you can not see the options list then click on the options hyperlink to display them.

T

Can you try this one:

TABLE FILE CAR
PRINT
     BODYTYPE
     SEATS
     DEALER_COST
     RETAIL_COST
     SALES
BY COUNTRY NOPRINT
BY CAR NOPRINT
BY MODEL
ON MODEL SUBFOOT
"<COUNTRY<CAR<MODEL<0X
<ST.SALES"
...

Piipster,
Sorry for not replying to this sooner, but your suggestion was exactly right. (though I can't believe we hadn't tried it before I posted my question --- we certainly tried everything else!)
Thanks!