ESDS files with Atom feeds

You may use ESDS (entry-sequenced data set) files to hold Atom entry data for an Atom feed, but there are some restrictions on deleting the Atom entries, which apply if you set up your feed as an editable collection.

Web clients can delete Atom entries in a collection by making HTTP requests with the DELETE method. With an ESDS file, HTTP requests with the DELETE method are only supported if the ESDS has no alternate index defined.

In response to a DELETE request, CICS deletes the relevant record from the ESDS by rewriting it with 'FF'x as the first byte, to represent a logical deletion. If web clients make subsequent HTTP requests with the GET method to retrieve the Atom entry that was in the deleted record, CICS returns a "not found" response to the GET requests.

When you define an ESDS file as an Atom collection, you must use one of the following methods to ensure that other application programs that use the ESDS file handle the deleted records correctly:
  • In the FILE resource definition for the ESDS, set DELETE to NO.
  • Alternatively, code the applications to process a record beginning with 'FF'x as being logically deleted.

To avoid these restrictions, if you are setting up a new resource to store Atom entry data for a collection, choose a VSAM file type other than ESDS.

If the ESDS file is only used for an Atom feed that is not defined as a collection, so web clients cannot make requests with the DELETE method, these restrictions do not apply. However, if you are setting up a new resource to store Atom entry data for an Atom feed, avoid using an ESDS file in case you decide to set up the Atom feed as a collection later on.



dfhtl_atom_esds.html | Timestamp icon Last updated: Sunday, 4 June 2017