Difference between revisions of "Patching Instructions"
(→Update Ingredients) |
(→Update Ingredients) |
||
| Line 68: | Line 68: | ||
* Build File -- defines which things are to be transported, but doesn't contain actual data | * Build File -- defines which things are to be transported, but doesn't contain actual data | ||
* Install file -- tracks which patches have been installed. | * Install file -- tracks which patches have been installed. | ||
| − | * Transport global | + | * Transport global -- temporary storage place to see how it will affect system before actually applying changes. So, when you "load" a patch, it has not been applied yet. You can change your mind before commiting to use of it. |
| − | * Distribution file or message | + | * Distribution file or message -- mail message is the primary format (esp in the VA). But there are some things it does not handle. Outside the VA firewall, they use a file format. |
| − | * Patches | + | * Patches -- Patches contain a distribution of a build. User uses patches. |
Revision as of 20:51, 1 July 2006
This will be filled in over time...
Example name: XWB-1p1_SEQ-10_PAT-11.kid
XWB is package name
SEQ-10 means this is the 10th sequence number
Patch-11 means this is patch number 11
Because multiple teams may be working on a project, occasionally patch 4 might come out before patch 3. Thus the sequence numbers were introduced, to ensure proper ordering.
To make a long story short, install the KID patches in numerical SEQUENCE NUMBER ordering.
I think the KIDS menu option is under EVE->Programm->KID
Patches have to be first loaded, then applied Always read the .TXT file that accompanies a patch (.kid). This will tell the special conditions that should be met before applying a patch.
Rick's Talk
These are things that can be included in a KIDS package
Package elements: Primary
- Package (?)
- Build (file 9.6)
- Data Dictionary (0)
- Data (file 1)
- Routine (*)
- Routine (file 9.8) entries <--- possible conflicts with local stuff.
- Option (file 19)
- Protocol (file 101)
- Remote Procedure (file 8994)
Package Elements: Secondary
- Function (.5) -- fileman functions
- Dialog (.84) -- i.e. internationalization text
- Parameter (8989.5) -- i.e. adjustable parameters for CPRS etc.
- Parameter Definition (8989.51)
Below are not included in KIDS, but instructions might specify for user to edit them.
- Device
- Domain
- bulletin
- Mail Group
- Help Frame
- Security Key
- New Person
Package Elements: Templates Print Template sort Template Input Template Form Block Foreign Format ...
Non-KIDS stuff -- not included in KIDS Manuals Script Configuration File Non-MUMPS programs
Instructions will tell you to go get separate programs.
Update Ingredients
- Package File (9.4)
- Package Elements
- Build File -- defines which things are to be transported, but doesn't contain actual data
- Install file -- tracks which patches have been installed.
- Transport global -- temporary storage place to see how it will affect system before actually applying changes. So, when you "load" a patch, it has not been applied yet. You can change your mind before commiting to use of it.
- Distribution file or message -- mail message is the primary format (esp in the VA). But there are some things it does not handle. Outside the VA firewall, they use a file format.
- Patches -- Patches contain a distribution of a build. User uses patches.
