Difference: 0LASubrUtilCheckSecurity (1 vs. 3)

Revision 32020-05-12 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPXRuntimeSubroutineAPI"

.UTIL CHECK SECURITY

Line: 29 to 29
  <oper_phase> is the operational phase to be tested (Optional). If not passed, it will default to the operational phase of the current application. If passed, it must be one of Live Operations, Initial Set Up or Recovery Processing.
Changed:
<
<
If you are using Role Based Security, use .UTIL CHECK RBS instead.
>
>
If you are using Role Based Security, use .UTIL CHECK RBS instead.
 

Comments:

Read what other users have said about this page or add your own comments.

Revision 22012-10-30 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPXRuntimeSubroutineAPI"

.UTIL CHECK SECURITY

Line: 28 to 28
 <database_id> is the database to be tested (Required).

<oper_phase> is the operational phase to be tested (Optional). If not passed, it will default to the operational phase of the current application. If passed, it must be one of Live Operations, Initial Set Up or Recovery Processing.

Added:
>
>
If you are using Role Based Security, use .UTIL CHECK RBS instead.
 

Comments:

Read what other users have said about this page or add your own comments.

Revision 12012-01-27 - JeanNeron

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="APPXRuntimeSubroutineAPI"

.UTIL CHECK SECURITY

This subroutine is called to check the security code for the specified user.


Usage:

      PASS         <result>                   FIELD            SHARE? Y
      PASS         <sec_class>                FIELD            SHARE? N
      PASS         <user_id>                  FIELD            SHARE? N
      PASS         <database_id>              FIELD            SHARE? N
      PASS         <oper_phase>               FIELD            SHARE? N
      GOSUB    --- .UTIL CHECK SECURITY
      *        Check for errors
      IF       --- .UTIL CHECK SECURITY       NE

Description:

This subroutine is called to check the security code for the specified user. All parameters are required, except for <oper_phase>. If any required parameters are missing, the subroutine will CANCEL.

<result> will contain Y or N, depending on the setting of the specified security code (Required). This must be PASSed Share "Y" to return the value.

<sec_class> is the security class to be tested, from 1-9999 (Required).

<user_id> is the user to be tested (Required).

<database_id> is the database to be tested (Required).

<oper_phase> is the operational phase to be tested (Optional). If not passed, it will default to the operational phase of the current application. If passed, it must be one of Live Operations, Initial Set Up or Recovery Processing.

Comments:

Read what other users have said about this page or add your own comments.


<--/commentPlugin-->

-- JeanNeron - 2012-01-27

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 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