![[OpenVMS documentation]](../../images/openvms_doc_banner_top.gif)
|
![[Site home]](../../images/buttons/bn_site_home_off.gif)
![[Send comments]](../../images/buttons/bn_comments_off.gif)
![[Help with this site]](../../images/buttons/bn_site_help_off.gif)
![[How to order documentation]](../../images/buttons/bn_order_docs_off.gif)
![[OpenVMS site]](../../images/buttons/bn_openvms_off.gif)
![[Compaq site]](../../images/buttons/bn_compaq_off.gif)
|
| Updated: 11 December 1998 |
|
|
|
|
| Updated: 11 December 1998 |
OpenVMS System Services Reference Manual
| Previous | Contents | Index |
On Alpha systems, specifies the address of a routine to receive control when a Change Mode to User or Change Mode to Supervisor instruction trap occurs.
On VAX systems, specifies the address of a routine to receive control when a Change Mode to User or Change Mode to Supervisor instruction trap occurs, or when a compatibility mode fault occurs.
SYS$DCLCMH addres ,[prvhnd] ,[type]
int sys$dclcmh (int (*addres)(__unknown_params), void *(*(prvhnd)), char type);
addres
OpenVMS usage: address type: longword (unsigned) access: read only mechanism: by reference
Routine to receive control when a change mode trap or a compatibility mode fault occurs. The addres argument is the exception handling code in the address space of the calling process.If you specify the addres argument as 0, $DCLCMH clears the previously declared handler.
prvhnd
OpenVMS usage: address type: longword (unsigned) access: write only mechanism: by reference
Address of a previously declared handler. The prvhnd argument is the address of a longword containing the address of the previously declared handler.type
OpenVMS usage: longword_unsigned type: longword (unsigned) access: read only mechanism: by value
Handler type indicator. The type argument is a longword value. The value 0 (the default) indicates that a change mode handler is to be declared for the access mode at which the request is issued; the value 1 specifies that a compatibility mode handler is to be declared.
On Alpha systems, the Declare Change Mode or Compatibility Mode Handler service calls the change mode handler as a normal procedure (that is, with a standard procedure call). The change mode handler must exit by performing a standard procedure return to the change mode dispatcher.
Arguments (for example, the change mode code) passed between the routine that issued the change mode instruction and the change mode handler are strictly by agreement between the two procedures.
The following MACRO code example shows a subroutine calling Change Mode to User. The example is written for Alpha users porting from VAX systems.
CHG_MD: .CALL_ENTRY CHMU RETCall this subroutine from any program that requires a Change Mode to User instruction to be invoked.
On VAX systems, the $DCLCMH service specifies the address of a routine to receive control when (1) a Change Mode to User or Change Mode to Supervisor instruction trap occurs, or (2) a compatibility mode fault occurs. A change mode handler provides users with a dispatching mechanism similar to that used for system service calls. It allows a routine that executes in supervisor mode to be called from user mode. You declare the change mode handler from supervisor mode; then when the process executing in user mode issues a Change Mode to Supervisor instruction, the change mode handler receives control and executes in supervisor mode.
The top longword of the stack contains the zero-extended change mode code. The change mode handler must exit by removing the change mode code from the stack and issuing an REI instruction.
The operating system uses compatibility mode handlers to bypass normal condition handling procedures when an image executing in compatibility mode causes a compatibility mode exception. Before transferring control to the compatibility mode handler, the system saves the compatibility exception code, the registers R0 through R6, and the PC and PSL in a 10-longword array starting at the location CTL$AL_CMCNTX. Before the compatibility mode handler exits, it must restore the saved registers R0 through R6, push the saved PC and PSL onto the stack, and exit by issuing an REI instruction.
You can declare a change mode or compatibility mode handler only from user or supervisor mode.
None
$SETEXV, $UNWIND
SS$_NORMAL The service completed successfully. SS$_ACCVIO The longword to receive the address of the previous change mode handler cannot be written by the caller. ++SS$_IVSSRQ The call to the service is invalid because it attempted to declare a compatibility mode handler on Alpha systems.
Declares an exit handling routine that receives control when an image exits.
SYS$DCLEXH desblk
int sys$dclexh (void *desblk);
desblk
OpenVMS usage: exit_handler_block type: longword (unsigned) access: write mechanism: by reference
Exit handler control block. The desblk argument is the address of this control block. This control block, which describes the exit handler, is depicted in the following diagram.
The Declare Exit Handler service declares an exit handling routine that receives control when an image exits. Image exit normally occurs when the image currently executing in a process returns control to the operating system. Image exit might also occur when you call the Exit ($EXIT) or Force Exit ($FORCEX) service.Exit handlers are described by exit control blocks. The operating system maintains a separate list of these control blocks for user, supervisor, and executive modes. The $DCLEXH service adds the description of an exit handler to the front of one of these lists. The actual list to which the exit control block is added is determined by the access mode of the caller.
At image exit, the exit handlers declared from user mode are called first; they are called in the reverse order from which they were declared.
Each exit handler is executed only once; it must be redeclared before it can be executed again. The exit handling routine is called as a normal procedure with the argument list specified in the third through nth longwords of the exit control block. The first argument is the address of a longword to receive a system status code indicating the reason for exit; the system always fills in this longword before calling the exit handler.
You can call this service only from user, supervisor, and executive modes.
None
None
$CANEXH, $CREPRC, $DELPRC, $EXIT, $FORCEX, $GETJPI, $GETJPIW, $HIBER, $PROCESS_SCAN, $RESUME, $SETPRI, $SETPRN, $SETPRV, $SETRWM, $SUSPND, $WAKE
The Cancel Exit Handler ($CANEXH) service removes an exit control block from the list.
SS$_NORMAL The service completed successfully. SS$_ACCVIO The first longword of the exit control block cannot be written by the caller. SS$_IVSSRQ The call to the service is invalid because it was made from kernel mode. SS$_NOHANDLER The exit handler control block address was not specified or was specified as 0.
On Alpha systems, deletes a buffer object previously created by the $CREATE_BUFOBJ_64 system service.This service accepts 64-bit addresses.
SYS$DELETE_BUFOBJ buffer_handle_64
int sys$delete_bufobj (struct _generic_64 *buffer_handle_64);
buffer_handle_64
OpenVMS usage: handle type: quadword (unsigned) access: read only mechanism: by 32- or 64-bit reference
The buffer object to be deleted. The buffer_handle_64 argument is the 32- or 64-bit address of a 2-longword array previously returned by a $CREATE_BUFOBJ_64 call.
The Delete Buffer Object system service deletes the buffer object identified by the buffer_handle_64 argument. The associated memory is made free to be paged, swapped, or deleted.Buffer objects are also automatically deleted at image rundown.
None
None
$CREATE_BUFOBJ_64
SS$_NORMAL The service completed successfully. SS$_ACCVIO The buffer_handle_64 argument cannot be read by the caller. SS$_BADPARAM The buffer_handle_64 argument is not a valid buffer handle. SS$_NOPRIV The buffer object was created by a more privileged access mode than the caller's access mode.
Searches for and deletes all records in the intrusion database matching the caller's specifications.
SYS$DELETE_INTRUSION user_criteria ,[flags]
int sys$delete_intrusion (void *user_criteria, unsigned int flags);
user_criteria
OpenVMS usage: char_string type: character-coded text string access: read only mechanism: by descriptor--fixed-length string descriptor
Description of intruder or suspect. The user_criteria argument is the address of a character-string descriptor pointing to a buffer containing the user criteria to match an intrusion record's user specification in the intrusion database.The user_criteria argument is a character string of 1 to 1058 bytes containing characters to match the user specification on records in the intrusion database.
A user specification is any combination of the suspect's or intruder's source node name, source user name, source DECnet--Plus address, local failed user name, or local terminal. The user specification for an intrusion record is based on the input to the $SCAN_INTRUSION service and the settings of the LGI system parameter. For more information, see the OpenVMS Guide to System Security.
Wildcards are allowed for the user_criteria argument. For example, if you specify an asterisk (*) for the user_criteria argument, the service deletes all records in the intrusion database.
flags
OpenVMS usage: mask_longword type: longword (unsigned) access: read only mechanism: by value
Functional specification for the service. The flags argument is a longword bit mask wherein each bit corresponds to an option.Each flag option has a symbolic name. The $CIADEF macro defines the following valid name for the $DELETE_INTRUSION service.
Symbolic Name Description CIA$M_IGNORE_RETURN The service should not wait for the return status from the security server. No return status from the server's function will be returned to the caller.
The Delete Intrusion service deletes from the intrusion database a set of records matching the criteria you specify in the user_criteria argument. All records matching the criteria you specify are deleted. You do not have to call the service more than once to delete a set of records.For example, if you specify an asterisk (*) for the user_criteria argument, the service deletes all records in the intrusion database with one call.
$DELETE_INTRUSION requires access to the intrusion database. You must have SECURITY privilege to access the database.
None
$SCAN_INTRUSION, $SHOW_INTRUSION
SS$_NORMAL The service completed successfully. SS$_ACCVIO The user_criteria argument cannot be read. SS$_BADBUFLEN The length of the user_criteria argument is out of range. SS$_BADPARAM An invalid flag was specified in the flags argument. SS$_NOSECURITY The caller does not have SECURITY privilege. This service can also return any of the following messages passed from the security server: SECSRV$_CIADBEMPTY No records in the intrusion database. SECSRV$_NOSUCHINTRUDER No records matching the specified criteria were found in the intrusion database. SECSRV$_SERVERNOTACTIVE The security server is not currently active. Try the request again later.
Deletes an existing proxy or removes the default user or a local user from an existing proxy in the proxy database.
SYS$DELETE_PROXY rem_node ,rem_user ,[local_user] ,[flags]
int sys$delete_proxy (void *rem_node, void *rem_user, void *local_user, unsigned int flags);
rem_node
OpenVMS usage: char_string type: character-coded text string access: read only mechanism: by descriptor--fixed-length string descriptor
Remote node name of the proxy to be deleted from or modified in the proxy database. The rem_node argument is the address of a character-string descriptor pointing to the remote node name string.A remote node name consists of 1 to 1024 characters. No specific characters, format, or case are required for a remote node name string. All node names are converted to their DECnet for OpenVMS full name unless the PRX$M_BYPASS_EXPAND flag is set with the flags argument.
Asterisk (*) and percent sign (%) wildcards are allowed for the remote node specification. If you specify wildcards for the rem_node argument, the security server searches for an exact match to the specified remote node first. If it does not find an exact match, the server performs the requested operations on all of the matching proxies in the proxy database.
rem_user
OpenVMS usage: char_string type: character-coded text string access: read only mechanism: by descriptor--fixed-length string descriptor
Remote user name of the proxy to be deleted from or modified in the proxy database. The rem_user argument is the address of a character-string descriptor pointing to the user name string.A remote user name consists of 1 to 32 alphanumeric characters, including dollar signs ($), underscores (_), and brackets ([ ]). Any lowercase characters specified are automatically converted to uppercase.
The rem_user argument can be specified in user identification code (UIC) format ([group, member]). Brackets are allowed only if the remote user name string specifies a UIC. Group and member are character-string representations of octal numbers with no leading zeros.
Asterisk (*) and percent sign (%) wildcards are allowed for the remote user specification. If you specify wildcards for the rem_user argument, the server searches for an exact match to the specified remote user first. If it does not find an exact match, the server performs the requested operations on all of the matching proxies in the proxy database.
local_user
OpenVMS usage: char_string type: character-coded text string access: read only mechanism: by descriptor--fixed-length string descriptor
Local user name to delete from the proxy record specified by the rem_node and rem_user arguments in the proxy database. The local_user argument is the address of a character-string descriptor pointing to the local user name.A local user name consists of 0 to 32 alphanumeric characters, including dollar signs ($) and underscores (_). If the local_user argument is not specified or has a length of 0, the server will delete the entire record or records specified by the rem_node and rem_user arguments from the proxy database.
If the local_user argument is specified, the server will delete only the user name specified by the local_user argument from the record specified by the rem_node and rem_user arguments. The local_user argument can specify either the proxy's default user or a user name in the proxy's local users list.
flags
OpenVMS usage: mask_longword type: longword (unsigned) access: read only mechanism: by value
Functional specification for the service and type of user the local_user argument represents. The flags argument is a longword bit mask wherein each bit corresponds to an option.Each flag option has a symbolic name. The $PRXDEF macro defines the following symbolic names.
Symbolic Name Description PRX$M_BYPASS_EXPAND The service should not convert the node name specified in the rem_node argument to its corresponding DECnet full name. If this flag is set, it is the caller's responsibility to ensure that the fully expanded node name is passed into the service. PRX$M_IGNORE_RETURN The service should not wait for a return status from the security server. No return status from the server's function will be returned to the caller. PRX$M_EXACT The service should match exactly the remote node and remote user and ignore wildcards.
The Delete Proxy service deletes a proxy from, or modifies an existing proxy in, the proxy database.$DELETE_PROXY requires access to the proxy database. To achieve access, the caller must have either SYSPRV privilege or a UIC group less than or equal to the MAXSYSGRP system parameter.
None
$ADD_PROXY, $DISPLAY_PROXY, $VERIFY_PROXY
SS$_NORMAL The service completed successfully. SS$_ACCVIO The rem_node, rem_user, local_user, or flags argument cannot be read by the service. SS$_BADBUFLEN The length of the rem_node, rem_user, or local_user argument was out of range. SS$_BADPARAM An invalid flag was specified in the flags argument. SS$_NOSYSPRV The caller does not have access to the proxy database. This service can also return any of the following messages passed from the security server: SECSRV$_BADNODENAMELEN The node name length is out of range. SECSRV$_BADREMUSERLEN The remote user name length is out of range. SECSRV$_INVALIDDELETE You attempted to remove the last local user with no default user remaining, or you tried to remove the last default user with no local user remaining. You must have at least one local user or one default user. SECSRV$_NOSUCHPROXY The proxy specified by the rem_node and rem_user arguments does not exist in the proxy database. SECSRV$_NOSUCHUSER The specified local user does not exist in the proxy's local user list, or is not the proxy's default user. SECSRV$_PROXYNOTACTIVE Proxy processing is currently stopped. Try the request again later. SECSRV$_SERVERNOTACTIVE The security server is not currently active. Try the request again later.
| Previous | Next | Contents | Index |
|
|
![[OpenVMS documentation]](../../images/openvms_doc_banner_bottom.gif) |
|
Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal |
4527PRO_026.HTML
|