.UTIL CHG HOOK
This subroutine changes fields on the Hook file.
Usage:
PASS <error_msg> FIELD SHARE? Y
PASS --- HOOK RECORD FIELD SHARE? N
GOSUB --- .UTIL CHG HOOK
* Check for errors
IF --- .UTIL CHG HOOK NE
Description:
This subroutine changes fields on the Hook file. All parameters are required, if any required parameters are missing, the subroutine will CANCEL.
<error_msg> will contain a detailed error message if the Hook record was not able to be changed (Required). This must be PASSed Share "Y" to return the value.
--- HOOK RECORD is the record structure containing the Hook information (Required).
The mandatory fields are:
HOOK AP:
HOOK VER:
HOOK PROC TYPE:
HOOK PROC NAM:
HOOK DB:
HOOK USER ID:
The above fields identify the hook record to be updated. (Application, Version, Process Type, Process Name, Database and User Id).
Enter values for the following fields, but only for the fields you want to change, all others can be blank.
HOOK OV AP
HOOK OV VER
HOOK OV PROC TYPE
HOOK OV PROC NAM
The above fields identify the hook process (Application, Version, Process Type, Process Name). This must be a valid process in the specified application/version.
HOOK OV DB: If you want the hook to switch the user to another database, enter that database here. Leave blank if you want the user to remain in their original database.
HOOK ACTIVE: Enter a Y to make this hook active the next time a user logs on. N means the hook is not active.
This subroutine is different from
.UTIL GET HOOK RECORDS /
.UTIL PUT HOOK RECORDS in that the the changes are permanent, and they do not take effect immediately. If you want the changes to take effect immediately, use
.UTIL GET HOOK RECORDS to get the current hook records from the engine, make the same changes as you did with this subroutine, then update the engine with
.UTIL PUT HOOK RECORDS. Or you can do nothing, and the changes will take effect the next time users log on.
Also see
.UTIL ADD HOOK and
.UTIL DEL HOOK.
Note that although --- HOOK is an indexed file that can contain more than one record, only the current record buffer will be processed.
Comments:
Read what other users have said about this page or add your own comments.
--
JeanNeron - 2012-03-12