> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/rt-lab/automation-api-and-scripting/rt-lab-api/c-rt-lab-api-reference/functions-reference/opalloadalias.md).

# OpalLoadAlias

<table data-header-hidden><thead><tr><th width="199.77777099609375"></th><th></th></tr></thead><tbody><tr><td><strong>Group</strong></td><td>Model Interaction, Alias</td></tr><tr><td><strong>Description</strong></td><td><p>Load a list of aliases. The new list isn’t merged to the current list of aliases or doesn’t replace the current list of aliases.</p><p>Specifying a pattern ensures that only matching aliases information is returned. Wildcard characters (?,*) may be used in the pattern.</p><p>Memory for output structure has been allocated by the RT-LAB API. User must free this memory with a call to OpalFreeMemory.</p><p>The existing field of the aliasInfo structure indicates if the loaded alias matches an alias in the current list of alias. When a match exists, the newAlias field of the aliasInfo structure contains a pointer of the matched alias.</p></td></tr><tr><td><strong>Required Control</strong></td><td>None</td></tr><tr><td><strong>Usage</strong></td><td>int <strong>OpalLoadAliasDescription</strong>(const char * fileName,const char * aliasNamePattern, int * numberAlias OP_ALIAS_INFO ** aliasInfo);</td></tr><tr><td><strong>Input</strong></td><td><ul><li><strong>fileName:</strong> Absolute or relative path of the file to load.</li><li><strong>aliasNamePattern:</strong> See <strong>Glossary.</strong></li></ul></td></tr><tr><td><strong>Output</strong></td><td><ul><li><strong>numberAlias:</strong> The number of aliases returned in the structure.</li><li><strong>aliasInfo:</strong> List of aliases' structure returned.</li></ul></td></tr><tr><td><strong>Return value</strong></td><td><ul><li><strong>EOK:</strong> Success.</li><li><strong>ENOENT:</strong> Cannot open parameter file.</li><li><strong>EIO:</strong> Error sending the request or receiving the reply.</li><li><strong>ENOMEM:</strong> Memory allocation error.</li><li><strong>EBADF:</strong> Model not specified by previous OpalConnect or OpalSetCurrentModel.</li></ul></td></tr><tr><td><strong>Examples</strong></td><td>None</td></tr><tr><td><strong>Related items</strong></td><td>OpalCreateAlias, OpalLoadAlias, OpalSaveAlias, OpalGetAliasDescription, OP_ALIAS_INFO.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/rt-lab/automation-api-and-scripting/rt-lab-api/c-rt-lab-api-reference/functions-reference/opalloadalias.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
