Invoked by the ptfpkg command to add fixdata information to the master fixdata database file.
updatefixdata -f InternalTable -a AbstractsFile
The updatefixdata command adds new APAR information to the $TOP/HISTORY/fixdataDB database file for the current PTF. This command uses an internal VRMF table generated by the ptfpkg command and is not intended to be run as a standalone command. This table contains the PTF, fileset, new VRMF level, and a set of APARs for each PTF currently in the ptf_pkg file. The abstracts file contains abstract and symptom information for each APAR. The information from the internal table and the abstracts file is combined into stanza format by the updatefixdata command and added to the $TOP/HISTORY/fixdataDB file.
|-a AbstractsFile||Specifies the location of the abstracts file containing abstract and symptom information for each APAR.|
|-f InternalTable||Specifies the location of the internal table file generated by the ptfpkg command.|
To invoke the updatefixdata command to update the fixdataDB file for the current build cycle,. type:
updatefixdata -f $TOP/HISTORY/internalVRMFTable.$BLDCYCLE \ -a $TOP/HISTORY/abstracts
|internalTable||The internal table file is generated by the ptfpkg
command. The internal table contains an entry for each PTF in the
ptf_pkg file. The entry contains the PTF number, fileset
name, new VRMF level, and a space-separated list of APARs that were fixed by
the PTF. The format is:
ptfid fileset v.r.m.f list of apars
|abstracts||The $TOP/HISTORY/abstracts file is required. It
contains information by APAR number that is included in the fixdata stanza for
the APAR. Its format is:
APARID apar abstract SYMPTOM TEXT @ Example: IX09503 AIXWM, WHEN MOVING A WINDOW THE OUTLINE WRAPS AROUND.
The sample code in /usr/lpp/X11/Xamples/aixclients/aixwm shows a problem in the hiprf3d adapter. When dragging the window around the screen and the window outline is moved beyond the right edge of the screen, it wraps around and shows up in the left edge.
@ IX19441 Virtual Circuits not being freed after child process dies
When an X.25 API user processes several calls with one process (for example, a daemon), the termination of the call does not cause the virtual circuit to be released for reuse causing the process to run out of X.25 resources and hang.
Should the three @ signs be here under abstracts?
|fixdataDB||After successful completion, the updatefixdata command updates
the fixdataDB file with one stanza per APAR. The format of
each stanza is:
fix: name = aparid abstract = apar abstract text type = F filesets = list of filesets:v.r.m.f levels associated with the apar fix symptom = apar symptom text
The ptfpkg command.