Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields |  ICR |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables  | All
Print Page as PDF
Global: ^XPD(9.6

Package: Kernel

Global: ^XPD(9.6


Information

FileMan FileNo FileMan Filename Package
9.6 BUILD Kernel

Description

Directly Accessed By Routines, Total: 39

Package Total Routines
Kernel 25 BUILD COMPONENTS    DD NUMBER    ENTRIES    EXCLUDE NAMESPACE OR PREFIX    FILE    GLOBAL    INSTALL QUESTIONS    MULTIPLE BUILD
PACKAGE NAMESPACE OR PREFIX    REQUIRED BUILD    XPDB1    XPDDCS    XPDE    XPDER    XPDET    XPDIB
XPDIP    XPDT    XPDTA    XPDTA2    XPDTC    XPDV    ^XPD(9.6    XUMF5AT
ZTP1    
Toolkit 7 XINDX10    XINDX11    XQABLOAD    XTRUTL    XTRUTL1    XTSUMBLD    XTVSRFL1    
VA FileMan 3 DDD    YEAR    ^DIC    
Scheduling 2 SCMCENV    SDECU    
Automated Information Collection System 1 IBD3KENV    
VistA Package Sizing Utility 1 A1VSRFL1    

Accessed By FileMan Db Calls, Total: 7

Package Total Routines
Toolkit 3 XTRUTL1    XTSUMBLD    XTVNUM    
Imaging 2 MAGGTU4    MAGJUTL5    
Nursing Service 1 NURXPRE    
Womens Health 1 WV4PST    

Pointer To FileMan Files, Total: 2

Package Total FileMan Files
Kernel 1 PACKAGE(#9.4)[1]    
VA FileMan 1 FILE(#1)[#9.64(.01)#9.67(.01)#9.68(.02)]

Fields, Total: 35

Field # Name Loc Type Details
.01 NAME 0;1 FREE TEXT

  • INPUT TRANSFORM:  D INPUTB^XPDET(.X)
  • LAST EDITED:  AUG 19, 2021
  • HELP-PROMPT:  Enter Package or Patch Name and version in the format 'PACKAGE nn.n[V|T]n' or 'PATCH*nn.n*nn'.
  • DESCRIPTION:  The name and version number of this Package or Patch.
    i.e. KERNEL 8.0T1 or XU*8.0*1
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • CROSS-REFERENCE:  9.6^B
    1)= S ^XPD(9.6,"B",$E(X,1,50),DA)=""
    2)= K ^XPD(9.6,"B",$E(X,1,50),DA)
  • FIELD INDEX:  D (#471) REGULAR IR LOOKUP & SORTING
    Short Descr: Allows lookup without decimal on Version number
    Description: This cross reference will allow users to lookup entries in the BUILD file without a decimal in the Version number.
    Set Logic: S ^XPD(9.6,"D",$E(X,1,50),DA)=""
    Kill Logic: K ^XPD(9.6,"D",$E(X,1,50),DA)
    Whole Kill: K ^XPD(9.6,"D")
    X(1): NAME (9.6,.01) (Subscr 1) (Len 50) (forwards)
    Transform (Storage): S:$P(X,"*",2)'=+$P(X,"*",2) X=$P(X,"*")_"*"_+$P(X,"*",2)_"*"_$P(X,"*",3)
.02 DATE DISTRIBUTED 0;4 DATE

  • INPUT TRANSFORM:  S %DT="EX" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  JUN 08, 1994
  • DESCRIPTION:  
    The date this Build is distributed to the sites.
1 PACKAGE FILE LINK 0;2 POINTER TO PACKAGE FILE (#9.4) PACKAGE(#9.4)

  • INPUT TRANSFORM:  S DIC("S")="I $$PCK^XPDET(Y)" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  APR 25, 1994
  • DESCRIPTION:  Enter this field only if you want to update the Package file when this package is installed at the recipient's site. You can only reference a Package with the same Name as your Build. If this is a patch, you can only
    reference a Package with the same Namespace as your Build.
  • SCREEN:  S DIC("S")="I $$PCK^XPDET(Y)"
  • EXPLANATION:  Must be the same Package Name or Namespace
  • CROSS-REFERENCE:  9.6^C
    1)= S ^XPD(9.6,"C",$E(X,1,30),DA)=""
    2)= K ^XPD(9.6,"C",$E(X,1,30),DA)
2 TYPE 0;3 SET
  • '0' FOR SINGLE PACKAGE;
  • '1' FOR MULTI-PACKAGE;
  • '2' FOR GLOBAL PACKAGE;

  • LAST EDITED:  JAN 05, 1995
  • DESCRIPTION:  This field controls what can be sent as part of this Build.
    SINGLE PACKAGE can contain all Routines and all Build Components.
    MULTI-PACAGE contains only a list of other Builds.
    GLOBAL PACKAGE can contain Environment Check and Post-Install
    Routines and a list of Globals.
3 DESCRIPTION OF ENHANCEMENTS 1;0 WORD-PROCESSING #9.61

  • LAST EDITED:  JUN 07, 1994
  • DESCRIPTION:  
    A complete and detailed description of the Package's or Patch's enhancements and capabilities.
4 VERSION COMPUTED

  • MUMPS CODE:  S X=$$VER^XPDUTL($P($G(^XPD(9.6,D0,0)),U))
  • ALGORITHM:  S X=$$VER^XPDUTL($P($G(^XPD(9.6,D0,0)),U))
  • DESCRIPTION:  
    This field returns the version number for this package.
5 TRACK PACKAGE NATIONALLY 0;5 SET
  • 'y' FOR YES;
  • 'n' FOR NO;

  • LAST EDITED:  APR 22, 1994
  • DESCRIPTION:  YES means you want to send a message to the National Package File on FORUM to track this package when it is installed at an installing site.
    NO means you don't want to generate a message.
6 FILE 4;0 POINTER Multiple #9.64 9.64

  • DESCRIPTION:  
    Any FileMan files which are part of this Package are documented here. This multiple controls what files (Data Dictionaries and Data) are distributed from this Package entry.
  • INDEXED BY:  DATA COMES WITH FILE (AD)
7 BUILD COMPONENTS KRN;0 POINTER Multiple #9.67 9.67

  • LAST EDITED:  MAY 19, 1994
  • DESCRIPTION:  
    The list of the components that make up a package.
10 MULTIPLE BUILD 10;0 Multiple #9.63 9.63

  • LAST EDITED:  SEP 04, 1996
  • DESCRIPTION:  This multiple contains other Builds that will be sent with this package for a multi-package distribution. It can also contain a list of patches that was rolled up into this Build. The Type field is used to distinguish the
    difference in its use.
11 REQUIRED BUILD REQB;0 Multiple #9.611 9.611
20 ALPHA/BETA TESTING ABPKG;1 SET
  • 'y' FOR YES;
  • 'n' FOR NO;

  • LAST EDITED:  MAR 07, 1994
  • DESCRIPTION:  YES means this package is currently in alpha or beta test and that you want to track option usage and errors relating to this package at the sites.
    NO means that you want to discontinue tracking of alpha or beta testing at sites.
21 INSTALLATION MESSAGE ABPKG;2 SET
  • 'y' FOR YES;
  • 'n' FOR NO;

  • LAST EDITED:  MAR 07, 1994
  • DESCRIPTION:  
    YES means you want a Installation Message sent when this package is installed at a site. The message will be sent to the mailgroup in the 'ADDRESS FOR USAGE REPORTING' field.
22 ADDRESS FOR USAGE REPORTING ABPKG;3 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>60!($L(X)<5)!(X'?1"G."1U.E1"@"1U.E) X I $D(X) N DIC,XPD S DIC=4.2,DIC(0)="QEM",XPD=X,X=$P(X,"@",2) D ^DIC S:Y>0 X=$P(XPD,"@")_"@"_$P(Y,U,2) K:Y<0 X
  • LAST EDITED:  MAR 08, 1994
  • HELP-PROMPT:  Answer should be a group addressee network mail format (e.g., G.PKG-TEST@ISC-ANYWHERE)
  • DESCRIPTION:  
    This field contains a mail group at a domain to which installation, option usage, and error messages are sent. This is usually a mail group containing one or more of the developers of the package at the developing ISC.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
23 PACKAGE NAMESPACE OR PREFIX ABNS;0 Multiple #9.66 9.66

  • DESCRIPTION:  
    This multiple field is used to identify the namespace or prefixes used to identify the options and routines associated with the alpha or beta test package.
30 GLOBAL GLO;0 Multiple #9.65 9.65

  • DESCRIPTION:  
    This multiple contains the globals to transport with KIDS.
50 INSTALL QUESTIONS QUES;0 Multiple #9.62 9.62

  • DESCRIPTION:  These are the Install questions that will be asked at the installing site. All questions will use the VA Fileman Reader (DIR) and all variables need to be defined in this multiple. Only the ENVIROMENT CHECK ROUTINE will
    be loaded at the installing site when these questions are asked.
51.01 XPF1 QDEF;1 SET
  • 'YES' FOR YES;
  • 'NO' FOR NO;

  • LAST EDITED:  JUN 19, 2007
  • DESCRIPTION:  
    Place holder for developer default answer. Not used at this time.
51.03 XPF2 QDEF;3 SET
  • 'YES' FOR YES;
  • 'NO' FOR NO;

  • LAST EDITED:  JUN 21, 2007
  • DESCRIPTION:  
    Place holder for developer default answer. Not used at this time.
  • TECHNICAL DESCR:  
    The order and location of these fields are setup to match the order and index in QUESTION^XPDTC.
51.05 XPI1 QDEF;5 SET
  • 'YES' FOR YES;
  • 'NO' FOR NO;

  • LAST EDITED:  JUN 19, 2007
  • DESCRIPTION:  
    This field holds the developer default for the Install question XPI1.
51.07 XPM1 QDEF;7 SET
  • 'YES' FOR YES;
  • 'NO' FOR NO;

  • LAST EDITED:  JUN 21, 2007
  • DESCRIPTION:  
    Place holder for developer default answer. Not used at this time.
51.09 XPO1 QDEF;9 SET
  • 'YES' FOR YES;
  • 'NO' FOR NO;

  • LAST EDITED:  JUN 19, 2007
  • DESCRIPTION:  
    This field holds the developer default for the Install question XPO1.
51.11 XPZ1 QDEF;11 SET
  • 'YES' FOR YES;
  • 'NO' FOR NO;

  • LAST EDITED:  JUN 19, 2007
  • DESCRIPTION:  
    This field holds the developer default for the Install question XPZ1.
51.13 XPZ2 QDEF;13 SET
  • 'YES' FOR YES;
  • 'NO' FOR NO;

  • LAST EDITED:  JUN 19, 2007
  • DESCRIPTION:  
    Place holder for developer default answer. Not used at this time.
61 BUILD VERSION# 6;1 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  MAR 02, 2021
  • HELP-PROMPT:  Type a Number between 1 and 999, 0 Decimal Digits
  • DESCRIPTION:  
    This is the build version number used in the File Comment field for Host Files or in the Subject for PackMan messages.
62 SEQ# 6;2 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>9999)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  DEC 16, 2019
  • HELP-PROMPT:  Type a number between 1 and 9999, 0 decimal digits.
  • DESCRIPTION:  
    This is just a place holder to reserve the database location in the INSTALL file.
63 TRANSPORT BUILD NUMBER 6.3;1 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999)!(X<0)!(X?.E1"."1.N) X
  • LAST EDITED:  JUN 19, 2006
  • HELP-PROMPT:  Type a number between 0 and 999, 0 Decimal Digits
  • DESCRIPTION:  This field holds the Transport Build Number for this package or patch. It is incremented by one every time there is a KIDS transport done. It should not be edited. During the KIDS transport this build number will be
    inserted into the 7th piece of the second line. During the testing of a package or patch this gives a way for support to know if the most current routines are loaded.
900 PRE-TRANSPORTATION ROUTINE PRET;E1,240 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>66!($L(X)<3)!'(X?.1UP.15UN.1"^"1UP.15UN.1"(".E) X
    MAXIMUM LENGTH: 66
  • LAST EDITED:  OCT 25, 2022
  • HELP-PROMPT:  Enter a routine, [TAG^]ROUTINE[(parameters)], 3 to 66 characters.
  • DESCRIPTION:  The name of the routine which is run before the Transport Global is sent. You can use this routine to add nodes to the Transport Global. The variable XPDGREF will be defined to a closed global root that could be used to
    set the nodes.
    example: S @XPDGREF@("mydata",1,0)="node one of data"
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
913 ENVIRONMENT CHECK ROUTINE PRE;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)<3!(X'?1U.15UN) X
    MAXIMUM LENGTH: 16
  • LAST EDITED:  MAR 07, 2016
  • HELP-PROMPT:  Enter name of developer's environment check routine (3-16 characters) that runs before any user questions are asked. This routine should be used for environment check only and should not alter data.
  • DESCRIPTION:  The name of the developer's routine which is run at the beginning of the install process. This should just check the environment and should not alter any data, since the user has no way to exit out of the install process
    until this program runs to completion. This routine can interact with the user. If the variable XPDQUIT is set, the install process will terminate.
    Note: This routine must be self-contained, since it will be the only routine installed from this package at this time.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
913.1 DELETE ENV ROUTINE INID;1 SET
  • 'y' FOR Yes;
  • 'n' FOR No;

  • LAST EDITED:  MAR 07, 2016
  • HELP-PROMPT:  Enter 'Yes' if you want the Environment Check Routine deleted at the end of the install.
  • DESCRIPTION:  Setting this field to YES will instruct KIDS to delete the Environment Check Routine at the end of the install.
914 POST-INSTALL ROUTINE INIT;E1,240 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>66!($L(X)<3)!(X'?.1UP.15UN.1"^"1UP.15UN.1"(".E) X
    MAXIMUM LENGTH: 66
  • LAST EDITED:  OCT 25, 2022
  • HELP-PROMPT:  Enter the name of the developer's post-initialization [TAG^]ROUTINE[(parameters)], 3 to 66 characters.
  • DESCRIPTION:  
    The name of the developer's routine which is run immediately after the installation of the package. This routine cannot be interactive with the user, it might be queued to run at a later time.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
914.1 DELETE POST-INIT ROUTINE INID;2 SET
  • 'y' FOR Yes;
  • 'n' FOR No;

  • LAST EDITED:  APR 15, 1999
  • DESCRIPTION:  
    Setting this field to YES will instruct KIDS to delete the Post-INIT Routine at the end of the install.
916 PRE-INSTALL ROUTINE INI;E1,240 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>66!($L(X)<3)!(X'?.1UP.15UN.1"^".1UP.15UN.1"(".E) X
    MAXIMUM LENGTH: 66
  • LAST EDITED:  OCT 25, 2022
  • HELP-PROMPT:  Enter name of developer's pre-init [TAG^]ROUTINE[(parameters)], 3 to 66 characters.
  • DESCRIPTION:  Name of the developer's routine that runs after the user has answered all of the questions, but before any data or DD has been installed. All of the routines for this package will already be installed. Used for data
    conversions, etc. that the developer needs to do before bringing in new data. This routine cannot be interactive with the user, it might be queued to run at a later time.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
916.1 DELETE PRE-INIT ROUTINE INID;3 SET
  • 'y' FOR Yes;
  • 'n' FOR No;

  • LAST EDITED:  APR 15, 1999
  • DESCRIPTION:  
    Setting this field to YES will instruct KIDS to delete the Pre-INIT Routine at the end of the install.
917 RESTORE ROUTINE REST;E1,240 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>66!($L(X)<3)!(X'?1UP.15UN.1"^"1UP.15UN.1"(".E) X
    MAXIMUM LENGTH: 66
  • LAST EDITED:  OCT 13, 2022
  • HELP-PROMPT:  Enter the developer's Restore Routine [TAG^]ROUTINE[(parameters)], that will be used if the patch is backed out, 3 to 66 characters.
  • DESCRIPTION:  
    Name of the developer's routine that will become the POST-INSTALL ROUTINE in the Back up Build. This routine should be used to delete any new files, fields, or data. This routine cannot be interactive with the user.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER

ICR, Total: 3

ICR LINK Subscribing Package(s) Fields Referenced Description
ICR #1125
  • Toolkit
  • FILE (4).
    Access: Direct Global Read & w/Fileman

    BUILD COMPONENTS (6).
    Access: Direct Global Read & w/Fileman

    ICR #2626
  • Library
  • NAME (.01).
    Access: Read w/Fileman

    PACKAGE FILE LINK (1).
    Access: Both R/W w/Fileman

    ICR #4897
  • Imaging
  • NAME (.01).
    Access: Read w/Fileman

    ALPHA/BETA TESTING (20).
    Access: Read w/Fileman

    ENTRIES (10).
    Access: Read w/Fileman

    ENTRIES (.01).
    Access: Read w/Fileman

    FILE (.02).
    Access: Read w/Fileman

    ACTION (.03).
    Access: Read w/Fileman

    CHECKSUM (.04).
    Access: Read w/Fileman

    ENTRIES (.01).
    Access: Read w/Fileman

    This access is restricted to the specific fields at thetop level of the BUILD (#9.6) file.ENTRIES is a multiple for each BUILD COMPONENT beingexported in a VI build. There are fields under the ENTRIES multiple that willbe returned by the software approved to use this IA.This ENTRIES (#9.68) multiple is a list of each recordthat is being sent for a build component. This particular IA focuses on theroutine build component. The VI software using this IA will assume a static D1value of 9.8 (ROUTINE file number) to return routine specific data to the VIapplication.This is a list of the routine(s) being sent as a buildcomponent.

    External References

    Name Field # of Occurrence
    ^%DT .02+1
    EN^DDIOL IDW1+1
    ^DIC 1+1, 22+1
    $$EXTERNAL^DILFD IDW1+1
    Y^DIQ ID1+1
    INPUTB^XPDET .01+1
    $$VER^XPDUTL 4+1

    Global Variables Directly Accessed

    Name Line Occurrences  (* Changed,  ! Killed)
    ^DD(9.4 ID1+1
    ^DIC(9.4 - [#9.4] ID1+1
    ^XPD(9.6 - [#9.6] IXDSL+1*, IXDKL+1!, IXDKEIC+1!, .01(XREF 1S), .01(XREF 1K), 1(XREF 1S), 1(XREF 1K), 4+1

    Naked Globals

    Name Field # of Occurrence
    ^(0 ID1+1, IDW1+1

    Local Variables

    Legend:

    >> Not killed explicitly
    * Changed
    ! Killed
    ~ Newed

    Name Field # of Occurrence
    >> %DT .02+1*
    %I ID1+1*!
    >> C ID1+1*
    >> D0 4+1
    >> DA IXDSL+1, IXDKL+1, .01(XREF 1S), .01(XREF 1K), 1(XREF 1S), 1(XREF 1K)
    DIC ID1+1, 1+1!*, 22+1~*
    DIC("S" 1+1*, 1SCR+1*
    DIC(0 22+1*
    >> DIE 1+1
    U ID1+1, IDW1+1, 4+1, 22+1
    X IXDSL+1, IXDKL+1, IXDP1TS+1*, .01+1, .01(XREF 1S), .01(XREF 1K), .02+1*!, 1+1*!, 1(XREF 1S), 1(XREF 1K)
    , 4+1*, 22+1!*, 61+1!, 62+1!, 63+1!, 900+1!, 913+1!, 914+1!, 916+1!, 917+1!
    XPD 22+1~*
    >> Y ID1+1*, .02+1, 1+1, 22+1
    Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields |  ICR |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables  | All