Transaction Contexts and URIs

The METASEC_BEGTRAN function creates a transaction context (TC), and the METASEC_ENDTRAN function ends it. The TC instance is located in the metadata server. The TC instance maintains the state of authorization query results and update requests for a client that is using the security administration interface. The TC accumulates changes that are requested for a single object. Submitting the METASEC_ENDTRAN function commits or discards changes, and then ends the TC.
Here are some usage notes:
  • For the value of the TC, if you specify an empty string, a temporary context is invoked, no server-side state is maintained, and changes to security settings are made immediately. This choice can be efficient if you have only one change to make, and you want to make the change immediately.
  • Specifying the URI is a best practice and is usually required. For DATA step functions that return information, the URI is the key to a cache of information about the object. The information is returned one row at a time in two-dimensional arrays. For more information, see Array Parameters.
If the URI refers to a standard metadata object, but not to an ACT or to a SAS Metadata Repository, you can use a standard URI. For more information, see What Is a URI?.
  • If the URI refers to an ACT, the URI must be in the form omsobj:AccessControlTemplate/my-ACTobj-id. For example:
    omsobj:AccessControlTemplate/A5DRX6L4.AT000005
  • If the URI refers to a repository, the URI must be in the form reposid:my-repos-id. For example:
    reposid:A5DRX6L4