This code defines and
registers a new standard. The code can also be used to register a
new version of an existing standard.
/*
Step 1. Ensure that the macro variable pointing to the global standards
library exists.
*/
%cstutil_setcstgroot;
/*
Step 2. Register the standard with the Toolkit global standards
library
*/
%cst_registerstandard(
_cstRootPath=%nrstr(&_cstGRoot./standards/myStandard),
_cstControlSubPath=control,
_cstStdDSName=standards,
_cstStdSASRefsDSName=StandardSASReferences),
_cstStdLookupDSName=standardlookup;
Step 1 ensures that
the macro variable that contains the global standards library path
is set. Step 2 registers the standard by passing this information:
-
The main path to the directory
that contains the standard version's files.
-
The path to the registration data
sets that are used to populate the global standards library metadata
data sets. This is the name of the subfolder in the
_cstRootPath
parameter
value.
Note: This subfolder must exist
before registering the standard.
-
The names of the Standards and
StandardSASReferences data sets. These data sets have the same structure
as the data sets in the global standards library metadata directory.
Both of these data sets are required to define a new standard or a
new version of a standard.
-
The name of the Standardlookup
data set. This data set has the same structure as the data set in
the
global standards library directory/metadata
directory.
This data set is optional.
The
_cstRootPath
parameter
uses
%nrstr(&_cstGroot)
so that the
&_cstGroot
is
registered as a macro variable. This specification allows the global
standards library to be moved or copied without reregistering the
full path of the new standard.
When defining
and registering a new standard, you should evaluate which of the metadata
files described in Common Framework Metadata should be provided to support new standard functionality.
For example:
-
Should a sample SASReferences file
be created to perform some task?
-
Should a Messages data set be added
to provide standard-specific informational messages?
-
Should properties files be provided
to set standard-specific global macro variables?
For more information
about the metadata files that support the SAS Clinical Standards Toolkit,
see Metadata File Descriptions. You can define new metadata types. These new metadata types
should be documented in the standard-specific StandardSASReferences
and Standardlookup data sets, and in the SAS Clinical Standards Toolkit
framework Standardlookup data set.