To supply individual optional parameters to
h02cbf.
h02cdf may be used to supply values for optional parameters to
h02cbf. It is only necessary to call
h02cdf for those arguments whose values are to be different from their default values. One call to
h02cdf sets one argument value.
Each optional parameter is defined by a single character string of up to
characters, consisting of one or more items. The items associated with a given option must be separated by spaces, or equal signs
. Alphabetic characters may be upper or lower case. The string
Print level = 1
is an example of a string used to set an optional parameter. For each option the string contains one or more of the following items:
– |
a mandatory keyword; |
– |
a phrase that qualifies the keyword; |
– |
a number that specifies an integer or real value. Such numbers may be up to contiguous characters in Fortran 77's I, F, E or D formats, terminated by a space if this is not the last item on the line. |
Blank strings and comments are ignored. A comment begins with an asterisk (*) and all subsequent characters in the string are regarded as part of the comment.
Normally, each user-specified option is printed as it is defined, on the current advisory message unit (see
x04abf), but this printing may be suppressed using the keyword
Nolist. Thus the statement
Call h02cdf ('Nolist')
suppresses printing of this and subsequent options. Printing will automatically be turned on again after a call to
h02cbf, and may be turned on again at any time by you, by using the keyword
List.
Optional parameter settings are preserved following a call to
h02cbf, and so the keyword
Defaults is provided to allow you to reset all the optional parameters to their default values by the statement,
Call h02cdf ('Defaults')
prior to a subsequent call to
h02cbf.
A complete list of optional parameters, their abbreviations, synonyms and default values is given in
Section 12 in
h02cbf.
None.
If a line is not recognized as a valid option, then a warning message is output on the current advisory message unit (see
x04abf).
Not applicable.
h02cdf is not thread safe and should not be called from a multithreaded user program. Please see
Section 3.12.1 in How to Use the NAG Library and its Documentation for more information on thread safety.
h02ccf may also be used to supply optional parameters to
h02cbf. Note that if
e04nff/e04nfa is used in the same program as
h02cbf, then in general
h02ccf will also affect the options used by
e04nff/e04nfa.