/* with in an editor and use on a z/OS Web server. */
ods html body='odsexb'
contents='odsexc'
page='odsexp'
frame='odsexf'
path='.example.htm'(url=none)
rs=none;
Using a z/OS PDSE for ASCII HTML Output
/* Allocate a PDSE for the HTML Output. */
filename pdsehtml '.example.htm'
dsntype=library dsorg=po
disp=(new, catlg, delete);
/* Specify the files to create for the HTML output. */
/* These files are PDSE members. */
/* The URL= suboption in the HTML-file */
/* specifications provides a URL that will be valid */
/* after the PDSE members have been moved to an */
/* ASCII file system. When the files are */
/* transferred, they must retain their member names */
/* and have the ".htm" extension added in order for */
/* these URLs to be correct. */
/* The PATH= option specifies the location for all */
/* the HTML files. The URL= suboption in the PATH= */
/* option prevents information from PATH= from */
/* appearing in the links and references that ODS */
/* creates because it will not be a valid URL for */
/* the ASCII file system. */
/* The TRANTAB= option creates ASCII HTML that */
/* you can send to an ASCII-based Web server. */
ods html body='odsexb' (url='odsexb.htm')
contents='odsexc' (url='odsexc.htm')
page='odsexp' (url='odsexp.htm')
frame='odsexf'
path='.example.htm'(url=none)
trantab=ascii;
Note: Use a binary transfer to move the files to the Web server.
1102 Appendix 4 ODS HTML Statements for Running Examples in Different Operating Environments

Get SAS 9.4 Output Delivery System, 3rd Edition now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.