xcall MIAMEX, MX_REGISTRY, opcode, <params depending on opcode>
(Windows only) MX_REGISTRY (MIAMEX 138) provides a range of Registry operations. The symbols and values for opcode are shown in the following table. Parameters, which are dependent on the function being called, are listed and discussed in the topics covering the various functions. See also MX_GETREG (simplified retrieve with ATE support).
Symbol |
Value |
Function |
|---|---|---|
REGOP_OPEN |
1 |
|
REGOP_CREATE |
2 |
|
REGOP_SET |
3 |
|
REGOP_READ |
4 |
|
REGOP_ENUMKEYS |
5 |
|
REGOP_ENUMVALS |
6 |
|
REGOP_CLOSE |
7 |
|
REGOP_DELKEY |
8 |
|
REGOP_DELVALUE |
9 |
|
REGOP_DELIMS |
64 |
|
Definition file: ashell.def |
||
Comments
MX_REGISTRY does not recognize ATE. If executed in a non-Windows environment (whether ATE or not), it will be essentially a null operation. If executed in the ATSD environment, it will return information from the server registry, not the client. If you want to retrieve registry information from the ATE client, either use MX_GETREG for simple retrieval, or package your MX_REGISTRY operations in an SBX which can be executed on the client side via AG_XFUNCS or MX_AGWRAPPER.
Although direct access to the Registry is not available for applications running A-Shell/Unix, Steve Evans of Caliq has developed a pair of routines which allow information to be saved using a similar model but which work on all platforms. See the routines INIX in SOSLIB:[907,26] and SYSREG in SOSLIB:[907,26] for details.
