Name | Value | ||||
---|---|---|---|---|---|
NUMBER | 316 | ||||
IA # | 316 | ||||
GLOBAL ROOT | DD( | ||||
DATE CREATED | 1993/11/01 | ||||
CUSTODIAL PACKAGE | VA FILEMAN | ||||
CUSTODIAL ISC | San Francisco | ||||
USAGE | Private | ||||
TYPE | File | ||||
DBIC APPROVAL STATUS | APPROVED | ||||
NAME | DBIA316-A | ||||
ORIGINAL NUMBER | 316 | ||||
GENERAL DESCRIPTION | 1. When a new file is configured for use with MTLU, the variable-pointer 'ENTRY' field is automatically updated in the LOCAL KEYWORD and LOCAL SHORTCUT files to reflect the new file. This must be handled via DIC/DIE calls with DIC/DIE being set to ^DD(file,.02,"V", It is fully compatible with the interactive way of creating variable pointer type fields. 2. MTLU uses the string maintained in ^DD("KWIC"). There is currently no way of retrieving this information without directly referencing this node. As stated there is currently no way of extracting data stored in the node except by direct global hit. *Amendment 5/11/94* Toolkit DBIA 316 has been amended to include the $order of ^DD in line QU+5^XTLKEFOP. This code identifies the variable pointer prefix associated with the selected lookup file and was inadvertently ommitted. S XTLKY=Y,XTLKPF=+$O(^DD(8984.2,.02,"V","B",+Y,"")) G:'XTLKPF KL S XTLKPF=$P(^DD(8984.2,.02,"V",XTLKPF,0),U,4),XTLKUT=1 |
||||
GLOBAL REFERENCE |
|
||||
STATUS | Active | ||||
DURATION | Till Otherwise Agreed | ||||
ID | DD( | ||||
SUBSCRIBING PACKAGE |
|