Global File Structure

Attribute Dictionary: File Characteristics Nodes

Certain file characteristics are kept in the subtree descendent from ^DD(filenumber,0,. These characteristics with their subscripted location and brief explanation are:

Table 112: Attribute Dictionary—Characteristics, Subscripted Location, and Brief Explanation

Post-Action

Figure 364: Attribute Dictionary—File Characteristics Nodes: Post-Action

    ^DD(filenumber,0,"ACT")

After an entry has been selected, some action can be taken to examine or verify the selection. This executable code is stored at this global location. If you decide that the entry should not be selected, set Y=-1.

REF: See the Advanced File Definition section.

Data Dictionary Audit

Figure 365: Attribute Dictionary—File Characteristics Nodes: Data Dictionary Audit

    ^DD(filenumber,0,"DDA")

This node is set to Y if auditing is turned on for the data dictionary. The node is nonexistent, NULL, or set to N if data dictionary auditing is not on.

Special Lookup

Figure 366: Attribute Dictionary—File Characteristics Nodes: Special Lookup

    ^DD(filenumber,0,"DIC")

A special lookup program can be written to facilitate selection from a particular file. If such a program is to be used, its name is stored at this location.

NOTE: The lookup program reference cannot be a labeled entry point to a routine. The routine's name is stored without the caret (^); it cannot begin with DI.

REF: See the Advanced File Definition section.

Field Identifiers

Figure 367: Attribute Dictionary—File Characteristics Nodes: Field Identifiers

    ^DD(filenumber,0,"ID",field)

Field Identifiers are defined using the VA FileMan Identifier [DIIDENT] option. The value at the node is a WRITE statement. If the identifier is to be used only to ask fields when a new entry is added, then the statement only writes NULL; otherwise, it contains the code to write the external value of the field. An I is added to the second piece of the File Header when you add a field identifier, (as described in the File Header section).

NOTE: WRITE statements in the VA FileMan-generated Field Identifier nodes are not executed when VA FileMan is in silent mode. Since FileMan generates the Field Identifier nodes, it knows their format. So, in silent mode, VA FileMan places what would have been written into an array instead for use by DBS calls. So, Field Identifier nodes, although they contain WRITE statements, are compatible with GUI applications (in contrast to Write Identifier nodes).

Write Identifier Nodes

Figure 368: Attribute Dictionary—File Characteristics Nodes: Write Identifiers

    ^DD(filenumber,0,"ID","ASTRING")
    ^DD(filenumber,0,"ID","W1")
    ^DD(filenumber,0,"ID","W2")
    ^DD(filenumber,0,"ID","WRITE1")

You can use M code to define additional custom identifier text to be displayed along with field identifiers. To do this, add "Write Identifier" nodes one level descendent from ^DD(filenumber,0,"ID"). The Write Identifier nodes you add must be subscripted with strings that begin with an uppercase alphabetic character.

Set the value of each Write Identifier node to the M code that produces the desired output. Write out your output using either the EN^DDIOL entry point (preferred) or the M WRITE command (not compatible with access to your file by GUI applications). In your M code for each Write Identifier node, you can refer to the values in Table 113 that are defined at the time the node is executed:

Table 113: Attribute Dictionary—Write Identifier Nodes: M code to Produce Desired Output

Write Identifiers are displayed after any field identifiers are displayed. If there is more than one Write Identifier, they are displayed in the collating order of the Write Identifier subscripts.

Since you must hard-set any "WRITE" nodes, you must also add an I (if one is not already there) to the second piece of the File Header.

Cross-References

Figure 369: Attribute Dictionary—File Characteristics Nodes: Cross-References

    ^DD(filenumber,0,"IX",cross-reference name,(sub)filenumber,field)

For cross-references, this node is set equal to NULL.

The INDEX (#.11) file is an alternate way to define indexes on a file. The information is descendent from ^DD("IX".

REF: See a description in the INDEX File section.

Screens

Figure 370: Attribute Dictionary—File Characteristics Nodes: Screens

    ^DD(filenumber,0,"SCR")

If you want to screen access to entries in a file, set the screen code into this node. The screen should be written like a screen put into the local variable DIC("S") for an ^DIC call. The code in this node is executed for each entry in the screened file. If $T=0 is returned when the node is executed, the entry being screened is unavailable for:

• Lookups
• Prints
• Inquiries
• Searches
• Other actions

For the screen in this global to be used, you must put a lowercase "s" into the second piece of the file's header following the file number (as described in the File Header section).

Version Number

Figure 371: Attribute Dictionary—File Characteristics Nodes: Version Number

    ^DD(filenumber,0,"VR")

This node is created during an INIT built by the VA FileMan package distribution routine (DIFROM) or an installation using the Kernel Installation and Distribution System (KIDS). It contains the current version number for the package that distributes this file. This node and the Distribution Package node are updated for any file sent by a KIDS installation. The only time these nodes are not updated is when a partial DD is sent.

REF: For additional information on KIDS, see the "KIDS" section in the Kernel 8.0 Systems Management: KIDS User Guide and Kernel 8.0 and Kernel Toolkit 7.3 Developer's Guide.

Distribution Package

Figure 372: Attribute Dictionary—File Characteristics Nodes: Distribution Package

    ^DD(filenumber,0,"VRPK")

This node is created during an installation using the Kernel Installation and Distribution System (KIDS). It contains the name of the package that distributes this file. The only time this is not updated is when a partial DD is sent.

REF: For additional information on KIDS, see the "KIDS" section in the Kernel 8.0 Systems Management: KIDS User Guide and Kernel 8.0 and Kernel Toolkit 7.3 Developer's Guide.

Package Revision Data

Figure 373: Attribute Dictionary—File Characteristics Nodes: Package Revision Data

    ^DD(filenumber,0,"VRRV")

This optional node, if present, is created during an installation using the Kernel Installation and Distribution System (KIDS). The node is defined by the developer who distributes the package. It can contain patch or other package revision information used to designate the version of the file that is installed at the site. Updating this node is done in the KIDS Post Install Routine (formerly the POST-INIT with DIFROM/INITS) using PRD^DILFD().

REF: For additional information on KIDS, see the "KIDS" section in the Kernel 8.0 Systems Management: KIDS User Guide and Kernel 8.0 and Kernel Toolkit 7.3 Developer's Guide.

Reviewed/Updated: May 2026