The getting-started workflow is sequential and dependency-driven: table design choices (key size/location, organization) directly shape what the API can retrieve and how, the data must be opened into a TSR before it’s API-accessible, and the copybook is the single artifact that ties the API request/response shape to the underlying table — with no other code changes required to deploy or update an API.
