|
Publishing Framework
COMPANION_NEXTRetrieves the next companion HTML file in the ODS HTML set. SyntaxCALL COMPANION_NEXT(entryId, path, filename, url, rc <, properties, propValue1, ...propValueN>);
DetailsThe publisher can choose to publish any combination of the HTML files. Included in the set of published files can be any number of additional HTML files or companion files.
The For details about how HTML files are published and how the optional encoding property can be used to provide encoding information to package recipients, see Publish/Retrieve Encoding Behavior. ExamplesExample 1The following example retrieves an HTML file and then retrieves the next companion HTML file in the set.
data _null_;
length contents $64 frame $64 pages $64
body $64 contentsUrl $256 frameUrl $256
PagesUrl $256 bodyUrl $256;
path ='/finance/accounting/doc';
CALL RETRIEVE_HTML(entryId, path, body, bodyUrl, frame,
frameUrl, contents, contentsUrl, pages, pagesUrl,rc);
CALL COMPANION_NEXT(entryId, path, fname, url, rc);
Example 2The following example retrieves an HTML file and then retrieves the next companion HTML file in the set. If the publisher specifies a MIME type when publishing a package, the optional MIMETYPE property is specified in order for its MIME type to be returned. The MIME type will be returned in the mime variable.
data _null_;
length contents $64 frame $64 pages $64 body $64
contentsUrl $256 frameUrl $256 PagesUrl $256
bodyUrl $256 mime $64;
path ='/finance/accounting/doc';
CALL RETRIEVE_HTML(entryId, path, body, bodyUrl, frame,
frameUrl, contents, contentsUrl, pages, pagesUrl,rc);
properties="MIMETYPE";
CALL COMPANION_NEXT(entryId, path, fname,
url, rc, properties, mime);
|