# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | patch name(+) | 0;1 | FREE TEXT | B | This is the name of the patch as it comes in the mail message. Examples: RMIM*1*1 DG*5.3*211 | |
1 | date of receipt | 0;2 | DATE-TIME | C | This is the date the patch was received in-house. | |
2 | priority | 0;3 | SET OF CODES | m:MANDATORY e:EMERGENCY | The priority assigned to this patch. Typical is "mandatory". | |
3 | parent package | 0;4 | FREE TEXT | This is the package for which the patch was issued. This field must be free text because of the possibility of having a patch issued for a new package without the package having been installed yet. | ||
4 | sequence number | 0;5 | NUMERIC | This is the sequence number assigned to the patch by the National Patch Module. | ||
5 | package version | 0;6 | FREE TEXT | This is the version of the parent package for which a patch is sent. It is determined from the patch information in the message. | ||
6 | patch subject | 0;7 | FREE TEXT | This is the subject of the patch. | ||
7 | install name | 0;8 | FREE TEXT | The installation information may or may not be in the INSTALL file for a patch. This may be because of: a. The package is new and may not yet be loaded but already has patches issued. b. The patch is a non-kids patch for executables, etc. | ||
8 | compliance date | 0;9 | DATE-TIME | D | This is the date by which the patch must be installed. | |
9 | date installed | COMPUTED | This is a computed field, driven by a mumps routine XTPMKPCF. This is a special routine to calculate the date installed from the INSTALL file. It reads the index backwards to find the last installed version by taking the $O(^XPD(9.7,"B",[INSTALL NAME],9999999999),-1). This is done because there may be several test versions on file in INSTALL file which may affect the true installation date determination. | |||
10 | installed by | COMPUTED | This is a computed field driven also by the routine AWBCKPCF at entry point WHO. It tells who installed the patch. | |||
11 | non-kids patch? | 0;10 | BOOLEAN | 1:YES | This field determines what happens in various areas of the package. A patch can be KIDs or non-KIDs. The data on a patch record can be either NULL (KIDs patch) or 1 (Non-KIDs patch). The field can actually be only set to a 1 or the information deleted (NULL). | |
12 | non-kids install date | 0;11 | DATE-TIME | E | Non-KIDs patches are those which do not have an accompanying KIDs install in the Packman message because: o It may have an accompanying host file (too large for a mail message) or o It may be a patch message referring to a .zip, .exe or other file which will not put an entry into the INSTALL file. Because of this, there is no install record to extract the install date and it must be entered (i.e., completed) by filling in this field. | |
13 | non-kids patch completed by | 0;12 | POINTER | 200 | This is a pointer to file 200 to record who completed the non-KIDs patch. |
Not Referenced