Write history information to an NDF NDF_HPUT
’
VERBOSE’
, ’
NORMAL’
or ’
QUIET’
, where ’
VERBOSE’
signifies
the lowest priority and ’
QUIET’
signifies the highest. The value given may be abbreviated, to no less then
three characters. A blank value is accepted as a synonym for ’
NORMAL’
. ’
s text width will simply be broken (at a space if possible) and
continued on a new line. This routine will return without action if (a) there is no history component present in the NDF, (b) the
priority specified via HMODE is lower than the NDF’
s current history update mode setting, or (c) the
NDF’
s history update mode is currently set to ’
DISABLED’
.
It is expected that the APPN argument will usually be left blank. A non-blank value should normally only be given for this argument if a more complete identification of the current application can be given than is supplied by default.
If no previous history information has been written to the NDF by the current application, then this routine will create a new history record whose text width will be determined by the length of the lines of the TEXT array (as returned by the Fortran LEN function). If history information has already been written, then this routine will append to the existing history record. In this case, the text width will already have been defined, so the supplied text will be re-formatted if necessary (by line breaking or paragraph wrapping) to fit into the available width.
Paragraph wrapping is recommended, when appropriate, as a means of saving space while retaining a neat appearance in the resulting history record. It is particularly useful when message tokens are used within normal text, since these make it hard to predict the precise length of history lines in advance. The right justification flag may be used to improve the cosmetic appearance of history text, but it has no effect on the amount of space used.
On exit from this routine, all message tokens in the current message context are left in an undefined state.