ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Administering Security in SYSVIEW for Command Level Access


Article ID: 195021


Updated On:




Customer with minimal SYSVIEW security experience requested help with basic security command setup in SYSVIEW.   The information in this document is provided to enable ease of setup for command authority access.  More detail of how Security works in SYSVIEW is provided via the product doc link that is included in the Resolution section of this Knowledge Doc. 


Release : 14.2

Component : SYSVIEW


The fastest way to grant a user access to execute specific commands like CICS commands in SYSVIEW is to add that user’s id to a user group that has already been granted the ability to perform those commands.  (Please refer to the attachment to this knowledge doc, 1594673655236__Administering Security in SYSVIEW for Command Access.docx,  for screen examples)

  • Issue the  SECURITY command in SYSVIEW if you have admin authority
  • Select User Groups to see what access groups have been set up already
  • Note that you can issue the WHERE <TSO ID> command which will display what group if any that the specified TSO ID is defined in so that it is clear as to which group a user may already be assigned to.    If a group was displayed, you can select that group so that any specific Security changes can be made within that group.  
  • Select the new User Group that you may want to assign a user to so that they will have the ability to issue the commands that are authorized for that group.  Let’s use  CICSPGMR as an example.
  • Select the User IDs Section.   The User IDs Section display lists the user IDs that belong to the security group. Use the display to add user IDs to the group, alter user IDs in the group, and delete user IDs from the group. The user IDs are sorted in ascending order.
  • Logout of SYSVIEW to insure that the changes are put into effect for that SYSVIEW instance.

Please refer to the SYSVIEW Product Doc for the release that you are using at the following link  for more detail on how the command and user groups work together.  Please note that this is the link for SYSVIEW 16.0:




1594673655236__Administering Security in SYSVIEW for Command Access.docx get_app