Skip to main content
Next section

Global

Map globals to namespaces.

Synopsis

[Map.w]    Global_GlobalName(ss)=Database,Collation,LockLocation

Description

Whenever a namespace (w) contains mappings, InterSystems IRIS® data platform creates a section in the configuration parameter (CPF) file called [Map.w] for that namespace. For example, mappings for the USER namespace appear under the section [Map.USER]. The [Map.w] section contains every global mapping, routine mapping, and package mapping for that namespace.

Global mappings take the form Global_GlobalName, where GlobalName is the specific global that is being mapped. Each global entry contains three comma-separated values that map a global to a namespace. Only the first value is required. If the other values are not specified, they are set to the instance default. These values are:

  • Database — Database location of the global.

  • Collation — Collation of the global (Default=5, InterSystems IRIS standard collation).

  • LockLocation — Lock database location for the global (Default=Database location). InterSystems recommends that the lock database be the same as the Database location.

The collation setting is ignored if the global is not mapped at the subscript level. If the actual collation of the global does not match the defined collation in the namespace definition (for subscript level mapped globals), a <COLLATEMISMATCH> error is generated when it is referenced. This is because InterSystems IRIS requires the global to have the same collation across all the databases it lives in, regardless of the default collation for the particular database.

For more information about mappings, see the Add Global, Routine, and Package Mapping to a Namespace section of the “Configuring InterSystems IRIS” section of System Administration Guide.

Subscript Mapping

You may specify subscript mapping as part of the GlobalName (ss). Note that if a subscript mapping is specified, a higher level mapping of the global itself must also exist. So if you want to create a mapping ^X(9), then a mapping for ^X must also exist. Subscript mappings may take the following forms:

(1)

(“A”)

(1):(5) — from 1 up to, but not including, 5

("A"):("Z") — from A up to, but not including, Z

(BEGIN):("X") — from the beginning up to, but not including, X

("Y"):(END) — from Y up to the end

Examples

Map the global ^SALES to the SALES Database:

Global_SALES=SALES
Copy code to clipboard

Subscript map the global ^SALES(“MA”) to the SALESMA database:

Global_SALES(“MA”)=SALESMA
Copy code to clipboard

Map the global ^ACCOUNT to the database ACCOUNTS:

Global_ACCOUNT=ACCOUNTS
Copy code to clipboard

Subscript map the global ^ACCOUNT(1) up to but not including ACCOUNT(5) to database ACCOUNTS1TO4:

Global_ACCOUNT(1):(5)=ACCOUNTS1TO4  
Copy code to clipboard

Map all globals starting with ABC to database ABC:

Global_ABC*=ABC
Copy code to clipboard

Changing This Parameter

On the Namespaces page of the Management Portal (System Administration > Configuration > System Configuration > Namespaces), select Global Mappings for the namespace you want to explore. To add a new entry, click New. To edit an existing entry, select Edit in that entry's row.