Business Context
A financial institution runs credit risk simulations daily. To comply with strict regulatory audit trails (Basel III), the system must explicitly log the configuration parameters (interest rate caps, risk thresholds, iteration limits) into the central logs before the actual, computationally expensive simulation starts. This ensures that every run is traceable to its specific input settings.
Data Preparation
Simulation of a configuration dataset containing risk parameters.
Copied!
| 1 | |
| 2 | DATA work.risk_config; |
| 3 | INPUT param_name $20. param_value; |
| 4 | DATALINES; |
| 5 | interest_cap 0.05 max_iterations 1000 risk_weight 1.2 ; |
| 6 | |
| 7 | RUN; |
| 8 |
Étapes de réalisation
1
Read configuration into a CAS dictionary structure.
Copied!
| 1 | PROC CAS; |
| 2 | TABLE.addCaslib / name="casuser" dataSource={srcType="path"} path="/tmp"; |
| 3 | TABLE.loadTable / caslib="casuser" path="risk_config.sas7bdat"; |
| 4 | RUN; |
2
Execute echo to validate the nested configuration object before simulation.
Copied!
| 1 | PROC CAS; |
| 2 | configObject = {scenario="Baseline_2024", settings={cap=0.05, iter=1000, weight=1.2}, timestamp=datetime()}; |
| 3 | BUILTINS.echo / parameters=configObject; |
| 4 | RUN; |
Expected Result
The SAS log displays the structured 'configObject' dictionary, confirming that the CAS session correctly received the complex nested parameters (Scenario name, settings dictionary, and timestamp) prior to execution.