Files > BUILD

name
BUILD
number
9.6
location
^XPD(9.6,
description
This file identifies the elements of a package that will be transported by the Kernel Installation & Distribution System. All components of the package, i.e. templates, options, Security Keys, etc., must be listed in in this file.
Fields
#NameLocationTypeDetailsIndexDescription
.01name0;1FREE TEXTBThe name and version number of this Package or Patch. i.e. KERNEL 8.0T1 or XU*8.0*1
.02date distributed0;4DATE-TIMEThe date this Build is distributed to the sites.
1package file link0;2POINTER9.4CEnter 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.
2type0;3SET OF CODES0:SINGLE PACKAGE
1:MULTI-PACKAGE
2:GLOBAL PACKAGE
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.
3description of enhancements1;0WORD-PROCESSINGA complete and detailed description of the Package's or Patch's enhancements and capabilities.
4versionCOMPUTEDThis field returns the version number for this package.
5track package nationally0;5BOOLEANy:YES
n:NO
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.
6file4;0MULTIPLE9.64Any 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.
7build componentsKRN;0MULTIPLE9.67The list of the components that make up a package.
10multiple build10;0MULTIPLE9.63This 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.
11required buildREQB;0MULTIPLE9.611
20alpha/beta testingABPKG;1BOOLEANy:YES
n:NO
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.
21installation messageABPKG;2BOOLEANy:YES
n:NO
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.
22address for usage reportingABPKG;3FREE TEXTThis 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.
23package namespace or prefixABNS;0MULTIPLE9.66This 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.
30globalGLO;0MULTIPLE9.65This multiple contains the globals to transport with KIDS.
50install questionsQUES;0MULTIPLE9.62These 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.01xpf1QDEF;1SET OF CODESYES:YES
NO:NO
Place holder for developer default answer. Not used at this time.
51.03xpf2QDEF;3SET OF CODESYES:YES
NO:NO
Place holder for developer default answer. Not used at this time.
51.05xpi1QDEF;5SET OF CODESYES:YES
NO:NO
This field holds the developer default for the Install question XPI1.
51.07xpm1QDEF;7SET OF CODESYES:YES
NO:NO
Place holder for developer default answer. Not used at this time.
51.09xpo1QDEF;9SET OF CODESYES:YES
NO:NO
This field holds the developer default for the Install question XPO1.
51.11xpz1QDEF;11SET OF CODESYES:YES
NO:NO
This field holds the developer default for the Install question XPZ1.
51.13xpz2QDEF;13SET OF CODESYES:YES
NO:NO
Place holder for developer default answer. Not used at this time.
61test#6;1NUMERICThis is just a place holder to reserve the database location in the INSTALL file.
62seq#6;2NUMERICThis is just a place holder to reserve the database location in the INSTALL file.
63transport build number6.3;1NUMERICThis 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.
900pre-transportation routinePRET;E1,240FREE TEXTThe 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. examble: S @XPDGREF@("mydata",1,0)="node one of data"
913environment check routinePRE;1FREE TEXTThe 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.
913.1delete env routineINID;1BOOLEANy:Yes
n:No
Setting this field to YES will instruct KIDS to delete the Enviroment Check Routine at the end of the install.
914post-install routineINIT;E1,240FREE TEXTThe 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.
914.1delete post-init routineINID;2BOOLEANy:Yes
n:No
Setting this field to YES will instruct KIDS to delete the Post-INIT Routine at the end of the install.
916pre-install routineINI;E1,240FREE TEXTName 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.
916.1delete pre-init routineINID;3BOOLEANy:Yes
n:No
Setting this field to YES will instruct KIDS to delete the Pre-INIT Routine at the end of the install.

Not Referenced