16 Getting Started
This section provides users with detailed information on program setup and configuration of the Sentinel Common Components master program parameters as a standalone program. For more information on the technical requirements for running Common Components, please refer to section 1.2: Technical Requirements.
16.1 Set-up and Requirements
16.1.1 Master Program Parameters
The master SAS Program found in sasprograms/00.0_soc_qa_cc_master_file.sas contains several parameters that must be specified by the user. These include the directory containing the QA MIL Package, project, work plan, Data Partner identifiers, and a version identifier. Table 16.1 contains detailed specifications for master program parameters.
| Parameter | Details |
|---|---|
| CCpackage_root | Description: Location of the QA CC package request folder, up to, but excluding the Request ID |
| Format: Alphanumeric | |
Example: CC_Package_Root = //sentinel/requests/etl_22/PhaseB/
|
|
| Evaluate_SCDM | Description: Local path(s) to the DMQA-approved SCDM tables associated with the QA CC request |
|
Note 1: Mulitple paths are allowed, but must be separated by a single space. Therefore, individual paths must not contain embedded spaces. Note 2: Any leading or trailing spaces will be removed programmatically |
|
| Format: Alphanumeric | |
Example: Evaluate_SCDM = //sentinel/etl22/PhaseA/ //sentinel/etl22/PhaseB/
|
|
| PTSTOEXCLUDE | Description: Name of file, including library reference, that lists patients to be excluded from snapshot-specific output files |
| Format: Alphanumeric | |
Example: PTSTOEXCLUDE = infolder.PtsToExclude
|
|
| _ROOT_DPLOCAL | Description: Local ETL and Phase-specific (NOT request specific) request folder root for DPLOCAL subfolder. When combined with parameters from the master program file for a specific production request, the full path(s) specific to that request are dynamically generated. |
|
Note 1: For most Data Partners, all root-path parameters will point to the same directory. |
|
| Format: Alphanumeric | |
Example: _ROOT_DPLOCAL = /sentinel/etl22/PhaseA/requests/
|
|
| _ROOT_INPUTFILES | Description: Local ETL and Phase-specific (NOT request specific) request folder root for INPUTFILES subfolder. When combined with parameters from the master program file for a specific production request, the full path(s) specific to that request are dynamically generated. |
|
Note 1: For most Data Partners, all root-path parameters will point to the same directory. |
|
| Format: Alphanumeric | |
Example: _ROOT_INPUTFILES = &_ROOT_DPLOCAL
|
|
| _ROOT_MSOC | Description: Local ETL and Phase-specific (NOT request specific) request folder root for MSOC subfolder. When combined with parameters from the master program file for a specific production request, the full path(s) specific to that request are dynamically generated. |
|
Note 1: For most Data Partners, all root-path parameters will point to the same directory. |
|
| Format: Alphanumeric | |
Example: _ROOT_MSOC = &_ROOT_DPLOCAL
|
|
| _ROOT_SASPROGRAMS | Description: Local ETL and Phase-specific (NOT request specific) request folder root for SASPROGRAMS subfolder. When combined with parameters from the master program file for a specific production request, the full path(s) specific to that request are dynamically generated. |
|
Note 1: For most Data Partners, all root-path parameters will point to the same directory. |
|
| Format: Alphanumeric | |
Example: _ROOT_SASPROGRAMS = &_ROOT_DPLOCAL
|
|
| PROJID | Description: Project identifier for internal SOC identification and tracking. |
| Format: Alphanumeric | |
Example: PROJID = to16_cap
|
|
| WPTYPE | Description: Work plan type for internal SOC identification and tracking. |
| Format: Alphanumeric | |
Example: WPTYPE = cca
|
|
| WPID | Description: Work plan identifier for internal SOC identification and tracking. |
|
Note 1: Should follow the format [wp###]. |
|
| Format: Alphanumeric | |
Example: MSWPID = wp001
|
|
| DPID | Description: Data Partner identifier for internal SOC identification and tracking. |
| Format: Alphanumeric | |
Example: msoc
|
|
| VERID | Description: Version identifier for internal SOC identification and tracking. Should track each re-distribution of the package (if multiple distributions are required). |
|
Note 1: Should follow the format [v##]. |
|
| Format: Alphanumeric | |
Example: VERID = v01
|