zmf Global Component security blocking browse of components Hot

by JOHN BREX on October 18, 2016

Modicication for ZMF Global component secuirty processing to allow users that are blocked from checkout/stage/checking functions to be abled to browse/view the restricted component.

 

  • We have turned on some Global component security to block checkout/stage/checking of selected modules.

    While function does stop users from changing modules, it also disallows them from browsing/view these same modules in Changeman. We are using function to restrict updates of DB2 components to the DBA group.  The developers do need to include the declgen and copbooks that the DBA create in the programs, but function disallows browse/view function also.

     

    We would like to suggest that Serena change the way the function works so to allow browse/view access, or provide ASM exit to allow us to overide restriction to allow browse/vewing of restricted modules.

     

  • Please login to view any attachments.

  • Hi John,

    We have done the same and there is no need to use Component Security
    You can segregate all DBA components into a separate application in which only DBA people have update access
    Any other developer can be given read access to the application giving them the ability to read/view/browse the objects

    The target libraries can be defined in the other applications as ‘hidden’ library types making them available to other applications and/or via the use of participating packages
    This enables the use of the generated copybooks to the other applications

    If you need more info, I can always send you an application report on how such applications are defined and co-op together. If needed just drop me a note

    Cheers

    Johan
    Johan Jacob Commented by Johan Jacob December 22, 2016
    Top 10 Reviewer  -  

    Hi John,

    We have done the same and there is no need to use Component Security
    You can segregate all DBA components into a separate application in which only DBA people have update access
    Any other developer can be given read access to the application giving them the ability to read/view/browse the objects

    The target libraries can be defined in the other applications as ‘hidden’ library types making them available to other applications and/or via the use of participating packages
    This enables the use of the generated copybooks to the other applications

    If you need more info, I can always send you an application report on how such applications are defined and co-op together. If needed just drop me a note

    Cheers

    Johan

     

PrintEmail

Recent Tweets