...nothing.
PAR_CANCL and PAR_UNSET are exceptions to this behaviour. Since they are freeing resources they attempt to work regardless of the inherited status.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...values.
In the ADAM implementation the user can omit the brackets in response to a prompt.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...application.
A parameter file is implementation specific, however it is expected to be part of any implementation. In the ADAM parameter system the parameter file is an HDS file named after the application and located in the ADAM_USER directory. So for an application called STATISTICS, the above parameter value could be `read' by a parameter in a different application by the user giving the HDS object name with an @ prefix, namely @ADAM_USER:STATISTICS.SIGMA for VMS and @$ADAM_USER/statistics.SIGMA for UNIX.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...put.
In the ADAM implementation this is usually a component of the parameter file - in this case an object of the required size will be created. However, if indirection to a named HDS file is used the shape specified in the PAR routine must match the object's shape.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...list.
In the ADAM implementation the dynamic minimum and maximum must lie within the limits set by the range field in the interface file. If not, the get routine returns with an error status. The allowed values reside in the intersection set of the two ranges. Users can also specify MIN or MAX for a parameter value to assign the minimum or maximum value to that parameter.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...exclusive.
In the ADAM implementation users of your application may wish to take advantage of the MAX/MIN facility. If this is so you will need to add calls to PAR_MAXI and PAR_MINI in the previous example.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...disappeared.
This assumes that the ppath in the ADAM interface file starts with 'DYNAMIC'.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...dimensions.
In retrospect the name probably should have been PAR_GDM1x for Get with Defaults and Multiple ranges, but the existing name is already in use in applications.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...prompted.
Remember that in the ADAM implementation the PAR_GET0C call made by PAR_CHOIC will first test the obtained value against the range or in fields in the interface file. If the supplied value is unacceptable, the user will be prompted by PAR_GET0C. Only once these constraints are passed will the value be tested against the menu.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
PAR Interface to the ADAM Parameter System
Starlink User Note 114
Malcolm J. Currie
Alan J. Chipperfield
1999 September 24
E-mail:ussc@star.rl.ac.uk