Files Produced by the HTML Destination

The HTML destination can produce four kinds of files: body, contents, frame, and page files. You create these files with options in the ODS HTML statement (see 'ODS HTML Statement' on page 95 for details).

The Body File

The body file contains HTML output that is generated from the output objects that your SAS job creates. The style definition and the table definition that the job uses determine the appearance and content of the tables and the cells within them.

Typically, when you route an output object that does not contain graphics to the HTML destination, ODS places the results within TABLE tags, generating them as one or more HTML tables.

Graphics output is produced according to the SAS code that generates it. Instead of using <TABLE> tags, the body file contains an <IMG> (image) tag that references the graphic. When you view the body file in a browser, you cannot tell that the graphic is not part of the body file because the <IMG> tag displays it in the browser.

Note: A very few procedures produce output objects that are neither tabular nor graphics. In these cases, the output is not tagged as an HTML table.

Titles and footnotes in the body file are generated as HTML tables of their own near the top and bottom of each page of HTML output.

Note: For graphics output, titles and footnotes are, by default, part of the graphics file. You can use the NOGTITLE and NOGFOOTNOTE options to place them in the body file instead. See the discussion of GTITLE and GFOOTNOTE in 'ODS HTML Statement' on page 95 for more information.

All <TABLE> tags and all <IMG> tags are potential targets for links or references (see 'How ODS Constructs Links and References' on page 640). Therefore, ODS must provide an <A> tag with a NAME attribute close to each <TABLE> and <IMG> tag for links and references to point to. The NAME attribute on the anchor tag becomes the final part of any reference or link to the table. ODS inserts anchor tags in its HTML output as follows :

• ODS places an anchor tag near the top of each page, before all tables on the page (including the table that holds the titles) and before all images. This anchor is the target for links to the first table (excluding any titles) or to the first image on the page.

  Note: Each procedure or DATA step starts a new page. In addition, ODS produces a new page of output whenever the SAS program explicitly asks for a new page. For example, if you use the page dimension in PROC TABULATE, then you create a page for each value of the variable that defines the pages. In this context, the word page has nothing to do with the PAGESIZE= setting in your SAS session.

• ODS places an anchor tag slightly before each <TABLE> tag, provided that the table contains results (not titles or footnotes) and that it is not the first table or image on the page.

• ODS places an anchor tag slightly before each <IMG> tag, provided that it is not the first table or image on a page.

The following figure illustrates the placement of anchor tags from a SAS job that executes two procedures. The first procedure creates two HTML tables of results on a single page. The page also includes an HTML table for the title and one for the footnote. Solid arrows indicate which <A> tag ODS uses as a target for each table. The second procedure creates a GIF file. The titles for this procedure are part of the GIF file (the default behavior). Again, the solid arrow indicates which anchor tag ODS uses as a target when it creates a link to the image. The dashed arrow points to the file that the <IMG> tag references.

Figure A2.4: Placement of <A> (anchor) Tags in HTML Output

For a view of this same file through a browser, see Browser View of HTML Frame FileDisplay A2.1 on page 647.

The Contents File

The contents file contains a link to the body file for each HTML table that ODS creates from procedure or DATA step results. The targets for these links are the values of the NAME attributes on the anchor tags that are in the body file, see 'The Body File' on page 642. For example, an anchor tag that links to the second HTML table of results in Placement of <A> (anchor) Tags in HTML Output on page 644 looks like this:

 <A href="pop-body.htm#IDX1"> 

In this anchor tag

• pop-body.htm identifies the file that contains the target

• #IDX1 provides the name of the target.

You can view the contents file directly in the browser, or, if you make a frame file, you can see the contents file as part of the frame file (see 'The Frame File' on page 645).

The Page File

The page file contains a link to the body file for each page of HTML output that ODS creates from procedure or DATA step results. The targets for these links are the values of the NAME attributes on the anchor tags that are in the body file (see 'The Body File' on page 642). For example, an anchor tag that links to the second page of results in Placement of <A> (anchor) Tags in HTML Output on page 644 looks like this:

 <A href="pop-body.htm#IDX2"> 

In this anchor tag

• pop-body.htm identifies the file that contains the target.

• #IDX2 provides the name of the target

You can view the page file directly in the browser, or, if you make a frame file, you can see the page file as part of the frame file (see 'The Frame File' on page 645).

The Frame File

The frame file provides a simultaneous view of the body file and the contents file, the page file, or both. The following figure illustrates how a frame that references both the contents and page files looks (in part) to an ASCII editor. The SRC attribute identifies a file to display in the browser. ODS constructs the value for the SRC attribute the same way that it constructs the value for an HREF attribute in a page or contents file (see Schematic of an HTML Frame File on page 646).

Figure A2.5: Schematic of an HTML Frame File

Browser View of HTML Frame FileDisplay A2.1 on page 647 shows the same frame file viewed from a browser.

Display A2.1: Browser View of HTML Frame File