Tags:
view all tags
---+ .UTIL ADD HOOK _This subroutine adds a record to the Hook file._ <br />%TOC% ---++ Usage: <pre> PASS <error_msg> FIELD SHARE? Y PASS --- HOOK RECORD FIELD SHARE? N GOSUB --- .UTIL ADD HOOK * Check for errors IF --- .UTIL ADD HOOK NE </pre> ---++ Description: This subroutine adds a record to 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 added (Required). This must be PASSed Share "Y" to return the value. --- HOOK RECORD is the record structure containing the Hook information (Required). The fields are: HOOK AP<br /> HOOK VER<br /> HOOK PROC TYPE<br /> HOOK PROC NAM The above fields identify the process to be hooked (Application, Version, Process Type, Process Name). This must be a valid process in the specified application/version. HOOK DB:<span style="white-space: pre;"> </span>If the hook is only applicable to certain databases, enter that database here, otherwise leave it blank for all databases. HOOK USER ID:<span style="white-space: pre;"> </span>If the hook is only applicable to a certain user, enter that user id here, otherwise leave it blank for all users. HOOK OV AP<br /> HOOK OV VER<br /> HOOK OV PROC TYPE<br /> 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:<span style="white-space: pre;"> </span>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:<span style="white-space: pre;"> </span>Enter a Y to make this hook active the next time a user logs on. Blank or N means the hook is not active. This subroutine is different from [[0LASubrUtilGetHookRecords][.UTIL GET HOOK RECORDS]] / [[0LASubrUtilPutHookRecords][.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 [[0LASubrUtilGetHookRecords][.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 [[0LASubrUtilPutHookRecords][.UTIL PUT HOOK RECORDS]]. Or you can do nothing, and the changes will take effect the next time users log on. Also see [[0LASubrUtilChgHook][.UTIL CHG HOOK]] and [[0LASubrUtilDelHook][.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._ <br />%COMMENT% -- Main.JeanNeron - 2012-03-12
Edit
|
Attach
|
Watch
|
P
rint version
|
H
istory
:
r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Raw edit
|
More topic actions...
Topic revision: r1 - 2012-03-12
-
JeanNeron
Home
Site map
Main web
MedicaidBilling web
Sandbox web
TWiki web
Main Web
Users
Groups
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
P
P
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
Edit
Attach
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback