The following examples show how to use WRITE_NOS to create a manifest file.
When Write_NOS is done creating objects on external object store it can create a manifest file with the names of the objects created. If there is a crash, abort, or error while writing objects, the manifest file is not created.
- The first example shows how to create the manifest file if a WRITE_NOS operation aborts before all the objects have been written out.
- The second example shows how to overwrite a manifest file.
- The third example shows how to create a manifest file using READ_NOS with RETURNTYPE('NOSREAD_KEYS') as input to writing the manifest file.
In these examples only the manifest file is written, not the actual objects the manifest file identifies.
- If not already done, set up an authorization to access external object storage. See Setting Up Authorization for WRITE_NOS Examples.
- If not already done, set up a database table to extract data from. You can use one of your existing tables or set up a test table to use with the examples. See Setting Up a Test Table.
- If not already done, set up or obtain access to the external object store where you want to write data. Follow the instructions from your external storage vendor.
-
Create a database table to store the manifest file entries:
CREATE TABLE ManifestTbl ( ObjectName VARCHAR(1024) CHARACTER SET UNICODE NOT CASESPECIFIC, ObjectSize BIGINT );
Prerequisites
Create A Manifest Table in the Database