Solution Option - Content from zFS file determined by URIMap attribute

[ijmitch]

One alternative I don't think is appropriate would be to make some use of the URIMAP - CICS could perform the normal matching on a URIMAP and then have some URI-specific behaviour. But what would this be?

The data to be returned wouldn't really fit into a Resource Definition attribute. Perhaps we could make the attribute a DOCTEMPLATE name... but how would we substitute any symbols in that template? Or a zFS file? Path and name or just name and we assume a path?

[Karagines]

With a URIMAP with DOCTEMPLATE attribute approach is an interesting idea. There is a direct link between the URIMAP and the CORS attributes stored in the document template. As for symbols, I don't believe we need them. A DOCTEMPLATE is very flexible in terms of storage location including a zFS file.
I like the direct link for discovery and the flexibility of locations to store the CORS attributes. The downside is yet another place to configure CICS.