CICS behavior in compliance with the Atom format and protocol

CICS handles a number of tasks required for compliance with the Atom format and protocol.

  • CICS validates the format of your Atom configuration files for Atom feed documents, Atom entry documents, and collections to ensure that they comply with the requirements in RFC 4287. Wherever it is viable to do so, CICS checks that you have supplied required elements, and applies defaults where necessary. The CICS documentation for setting up Atom feeds has information about the situations in which CICS is not able to validate your data, where you are responsible for providing correct data.
  • CICS handles Atom service documents and Atom category documents that you create, and delivers these to clients. However, CICS does not validate the format of these documents, whether they are in Atom configuration files or delivered as static documents. You are responsible for compliance with the requirements detailed in RFC 5023 for the format of these Atom document types.
  • CICS provides EXEC CICS API commands that create timestamps in the correct format for Date constructs in Atom documents. If you choose not to use the EXEC CICS API commands to produce your timestamps, you are responsible for compliance with the requirements detailed in RFC 4287 for the content of Date constructs.
  • CICS handles the mapping and comparison tasks for IRIs, which are used in <atom:id> elements and <atom:link> elements.
  • CICS supplies the <atom:generator> element for Atom feed documents, which gives the name of the generating agent, with a URI and version number.
  • CICS can generate an Atom ID for each entry when it serves the Atom feed, in a format that meets the specification in RFC 4287. Under the conditions described in Atom IDs for Atom entries, the Atom ID is unique and remains the same for the lifetime of each Atom entry.
  • CICS carries out the actions required of a server for processing client requests to manipulate ordinary Atom entries in collections, as specified in RFC 5023, except where noted in Atom features not supported by CICS. In particular, CICS does not support media resources and media link entries in collections.
  • CICS enables you to implement security for Atom feeds and resources containing data for Atom feeds, through CICS resource security and CICS web support security. You are responsible for choosing and setting up appropriate security features to protect your Atom feeds. RFC 5023 recommends that you use authentication mechanisms, and discusses a number of threat scenarios.


dfhtl_atom_behavior.html | Timestamp icon Last updated: Monday, 5 June 2017