HELP: IBM z/OS Cloud Data Access object store (store.ibmcda(), z/OS only) TYPE: OBJECT SYNTAX: IBMCDA(PROVIDER='str',BUCKET/CONTAINER='str',PREFIX='str',ALTCRED)
Use the IBM z/OS Cloud Data Access (CDA) object store for archive read.
The archive is read from the given bucket through the DFSMSdfp Cloud Data Access component of z/OS. The parameters are the connection parameters of STORE.IBMCDA and carry the same meaning as for archive write; see the write description for what CDA owns and what this object names.
This store is available on z/OS only, on MVS as well as on z/OS UNIX.
Speed is not what this store is for. Cloud Data Access sits on the same z/OS Client Web Enablement Toolkit as the native cloud stores, so the HTTP/1.1 limitation applies here too. Where the installed level offers GDKINIT and GDKTERM the store holds one session per open, which saves a provider file read, a key file read and a handshake on every object; a level without them answers X'F02' and every operation stands on its own, as before. FL_CDA_SESSION=OFF asks for the standalone form on any level. On MVS the operation goes through the same helper in a second address space; on z/OS UNIX it runs in process in both addressing modes. What this store is for is that the endpoint and the credentials never appear in a FLAM command. The STORE section "Storage Backends and How FLAM Reaches Them" compares the routes.
STRING: PROVIDER='str' - CDA provider name, basename of its json file [required; max 20 chars, case sensitive; env: FL_CDA_PROVIDER]STRING: BUCKET/CONTAINER='str' - Bucket or container name inside the provider [required; env: FL_CDA_BUCKET]STRING: PREFIX='str' - Object key prefix within the bucket [default: none; env: FL_CDA_PREFIX]SWITCH: ALTCRED - Use the alternate credential pair CDA holds for this provider [FALSE; refused at present, see the manual]