MainView for DB2 resources
The following table lists all the security resources that are protected by
MainView for DB2
:
Resource name in SERDEF view | Resource definition and considerations |
|---|---|
AccelStats - Table Data | Can the user access the table data in the AccelStats views? Default Entity Name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity Name after Substitution: BBM.MVDB2. targetid.PAA00.OD |
AccelThreads - Table Data | Can the user access the table data in the AccelThreads views? Default Entity Name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity Name after Substitution: BBM.MVDB2. targetid.PY300.OD |
Any Action - (MainView for DB2) | Can the user enter any command from MainView for DB2 views? Default entity name: BBM.&PRODUCT.&CONTEXT.AA Entity name after substitution: BBM.MVDB2. targetid.AA |
Appl Monitor - Table Data | Can the user access application monitor table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PAA1Q.OD |
Application Workload - Table Data | Can the user access application workload table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PAA1J.OD |
Archive Trace Log DSN | Can the user enter the A (Archive) line command on the history trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ210.ARCHIVE.OA |
ASUTIME - Table Data | Can the user access current ASUTIME table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PCAD0.OD |
Authorization Failures CDC0140 - Table Data | Can the user access DB2 authorization failures table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PC8C0.OD |
BufferPool - Table Data | Can the user access buffer pool table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PBF00.OD |
CDCExplain - Table Data | Can the user access the table data in the EXPLAIN view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PV100.OD |
CDCExplain - Action - WHATIF | Can the user enter the W (WhatIf) line command on the EXPLAIN view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.PV100.WHATIF.OA |
CDCExplain - Action - HIDE | Can the user enter the H (Hide) line command on the EXPLAIN view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.PV100.HIDE.OA |
CDCExplain - Action - SELECT | Can the user enter the S (Select ) line command on the EXPLAIN view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.PV100.SELECT.OA |
CDCExplain - Action - PREDICATES | Can the user enter the P (Predicates) line command on the EXPLAIN view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.PV100.PREDICAT.OA |
CDCExplain - Action - RULES | Can the user enter the R (Rules) line command on the EXPLAIN view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.PV100.RULES.OA |
Current Trace - Action - PMACC# | Can a user other than the original creator of the trace issue the STOP, PURGE, MODIFY, QISLOG, or SWITCH command from the Current Traces view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ220.PMACC#.OA |
Current Trace - Any action | Can the user enter any actions on the current trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.QQ220.AO |
Current Traces Display | Can the user access the current trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.QQ220.OD |
Data Set Opens CDC00107 - Table Data | Can the user access DB2 data set open and close table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PC6B0.OD |
Data Set Opens - Physical CDC37071 - Table Data (with PTFs BPD4806, BQU1805, and BQU1806 applied) | Can the user access DB2 data set physical open and close table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PC700.OD |
DB2 Commands CDC0090 - Table Data | Can the user access DB2 commands table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PC5A0.OD |
DB2 Storage - Table Data | Can the user access DB2 DBM1 storage table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PM010.OD |
DDF Connections - Any Action | Can the user issue commands (actions) in the DDF connection views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.PF100.AO |
DDF - Table Data | Can the user access DDF table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PF100.OD |
Default - Alter Data Set | Can the user alter MainView for DB2 data sets? Class name: DATASET Entity name: &DSN |
Default - Any Table Actions | Can the user enter any view commands from MainView for DB2 views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.tableid.AO |
Default - any table actions for DUSER view | Can the user enter any actions from MainView for DB2 DUSER view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.PU300.AO |
Default - Specific Table Action | Can the user enter specific view commands from MainView for DB2 views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.tableid.actionid.OA |
Default - Table Data | Can the user access MainView for DB2 views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.tableid.OD |
Default - User allowed to see all SQL text in DUSER view | Is the user permitted to see all SQL text in the MainView for DB2 DUSER view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.PU300.DB2SQLAL.OA |
Default - User allowed to see only their own SQL text in DUSER view | Is the user permitted to see only their own SQL text in the MainView for DB2 DUSER view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.PU300.DB2SQLAU.OA |
Delete a Trace Directory Entry | Can the user enter the DELETE command on the history trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ210.DEL1DSN.OA |
Delete Trace Log DSNs | Can the user enter the D (Delete) line command on the history trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ210.DELDSNS.OA |
DUSER - Table Data | Can user access active thread detail data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PU300.OD |
Dynamic SQL Cache - Any Action | Can the user enter any action in the SCSETF view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution:BBM.MVDB2. targetid.TD100.AO |
Dynamic SQL Cache - Table Data | Can the user access dynamic SQL cache table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PD100.OD |
Free TLDS - LCMD Action | Can the user enter the F (Free) line command on the history trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ210.FREE.OA |
History Trace - Any action | Can the user enter any actions on the history trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.QQ210.AO |
History Trace Directory Display | Can the user access the history trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.QQ210.OD |
IoActivity - Table Data | Can the user access I/O activity (page set) table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PI010.OD |
Location Stats – Table Data | Can the user access remote locations table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PS200.OD |
LockOuts - Table Data | Can the user access lockout table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PL020.OD |
Locks - Any Action | Can the user enter actions (cancel commands) for active threads holding locks (in the current lock views)? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.PL100.AO |
Locks - Table Data | Can the user access current locks table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PL100.OD |
Modify Trace Action | Can the user enter the M (Modify) line command on the current trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ220.MODIFY.OA |
Monitor - Exception Messages | Can the user access the monitor exceptions table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PE200.OD |
Monitor - Table Data | Can the user access application monitor table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PAA10.OD |
Monitor Profile - Table Data | Can the user access monitor profile table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PN100.OD |
Monitor Services - Action - LOCK | Can the user enter the L (Lock) line command on the monitor services views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QM100.LOCK.OA |
Monitor Services - Action - SETREQ | Can the user enter the BLK (Requests) line command on the monitor services views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QM100.SETREQ.OA |
Monitor Services - Action - START | Can the user start a monitor by using the Start Workload Monitor dialog? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QM100.START.OA |
Monitor Services - Action - UNLOCK | Can the user enter the U (Unlock) line command on the monitor services views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QM100.UNLOCK.OA |
Monitor Services - Any action | Can the user enter actions on the monitor services views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.QM100.AO |
Monitors - Action - MODIFY | Can the user enter the M (Modify) line command on the monitor administration views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OA Entity name after substitution: BBM.MVDB2. targetid.QAA10.MODIFY.OA |
Monitors - Action - PMACC# | Can a user other than the original creator of the monitor issue the STOP, PURGE, or MODIFY command from the Active Monitors views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QAA10.PMACC#.OA |
Monitors - Action - PURGE | Can the user enter the P (Purge) line command on the monitor administration views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OA Entity name after substitution: BBM.MVDB2. targetid.QAA10.PURGE.OA |
Monitors - Action - REPLICAT | Can the user enter the R (Replicate) line command on the monitor administration views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OA Entity name after substitution: BBM.MVDB2. targetid.QAA10.REPLICAT.OA |
Monitors - Action - SHOW | Can the user enter the W (Show) line command on the monitor administration views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OA Entity name after substitution: BBM.MVDB2. targetid.QAA10.SHOW.OA |
Monitors - Action - STOP | Can the user enter the Z (Stop) line command on the monitor administration views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OA Entity name after substitution: BBM.MVDB2. targetid.QAA10.STOP.OA |
Monitors - Any action | Can the user enter actions on the monitor administration views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.QAA10.AO |
New TLDS - LCMD Action | Can the user enter the N (New) command on the history trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2.targetid.QQ210.NEW1DSN.OA |
New TLDS - Primary Action | Can the user enter the NEW command on the history trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ210.NEWDSNS.OA |
Objects for currently executing statement | Can the user access APPTUNE for DB2 collected object table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OA Entity name after substitution: BBM.MVDB2. targetid.PA080.OD |
PASPARM - Table Data | Can the user access the PASPARM table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.QPA10.OD |
PASPARM - Any Action | Can the user execute any action against the PASPARM table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OA Entity name after substitution: BBM.MVDB2. targetid.QPA10.OA |
PASPARM - Alter Data Set | Can the user alter the data set where the member will be saved? Class name: DATASET Entity name: &DSN |
PASPARM - Action - DEPLOY | Can the user execute the DEPLOY primary command to deploy the member to one or more remote targets.? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2.targetid.QPA10.DEPLOY.OA |
PASPARM - Action - EDIT Member | Can the user issue the EDIT action from the PASPARM view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QPA10.EPARM.OA |
PASPARM - Action - VIEW Member | Can the user issue the VIEW action from the PASPARM view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QPA10.VPARM.OA |
PASPARM - Action - INSTALL Member | Can the user issue the INSTALL action from the PASPARM view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QPA10.INSTALL.OA |
Print Trace Action | Can the user enter the P (Print) line command on the history trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ210.PRINT.OA |
Purge Trace Action | Can the user enter the P (Purge) line command on the current trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ220.PURGE.OA |
Quiesce Trace Logging | Can the user enter the Q (Quiesce Logging) line command on the current trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ220.QISLOG.OA |
Replicate Trace Action | Can the user enter the R (Replicate) line command on the current trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2.targetid.QQ220.REPLICAT.OA |
Reset Trace Log Action | Can the user enter the R (Reset) line command on the history trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ210.RESET.OA |
Restricted/ Advisory Objects - Table Data | Can the user access restricted/advisory object table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PO100.OD |
RIDLIST CDC0125 - Table Data | Can the user access RID list processing table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PC7D0.OD |
Short Term Statistics - Table Data | Can the user access short-term statistics table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PS400.OD |
Show Trace Action | Can the user enter the W (Show) line command on the current trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ220.SHOW.OA |
Show Trace Attributes | Can the user enter the W (Show) line command on the history trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ210.TSHOW.OA |
SQL Cache Statement Data | Can the user access SQL statement table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PD200.OD |
Start Detail Trace Action | Can the user enter the ST (Start) command on the current trace view to start a detail trace? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ220.DTLTRACE.OA |
Start - Pageset Processing | Can the user enter the STARTPS command on any windows mode view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.PA Entity name after substitution: BBM.MVDB2. targetid.STARTPS.PA |
Start Trace Action | Can the user enter the ST (Start) command on the current trace view to start a summary or detail trace? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ220.START.OA |
Start Trace Directory Action | Can the user enter the STARTDIR command on the history trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ210.START.OA |
Static SQL Cache - Action - PTRACE | Can the user stop collection for static SQL statistics? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.PD400.PTRACE.OA |
Static SQL Cache - Action - STRACE | Can the user start collection for static SQL statistics? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.PD400.STRACE.OA |
Static SQL Cache – Any Action | Can the user enter any action in the static SQL cache views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.PD400.AO |
Static SQL Cache – Table Data | Can the user access static SQL cache table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PD400.OD |
Static SQL Cache Stmts – Table Data | Can the user access static SQL cache statement text table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PD500.OD |
Status - Action - SCSTATS | Can the user enter the SQL cache start/stop statistics collection command in the STCACHE status view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PS100.SCSTATS.OA |
Status - Any Action | Can the user enter any action in the DB2 status views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.PS100.AO |
Status - Pageset Processing | Can the user enter the SHOWPS command on any windows mode view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.PA Entity name after substitution: BBM.MVDB2. targetid.SHOWPS.PA |
Status - Table Data | Can the user access DB2 status table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PS100.OD |
STDLOGS - Table Data | Can user access log status data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PD300.OD |
Stop Trace Action | Can the user enter the Z (Stop) line command on the current trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ220.STOP.OA |
Stop Trace Directory Action | Can the user enter the STOPDIR command on the history trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ210.START.OA |
Stop - Pageset Processing | Can the user enter the STOPPS command on any windows mode view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.PA Entity name after substitution: BBM.MVDB2. targetid.STOPPS.PA |
Stored Procedures - Any Action | Can the user enter the Activate, Queue, or Reject action commands on the stored procedures views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.PY200.AO |
Stored Procedures - Table Data | Can the user access stored procedures table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PY200.OD |
Switch Trace Action | Can the user enter the I (Switch) line command on the current trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ220.SWITCH.OA |
Thread Intervals - Table Data | Can the user access thread interval history table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PT200.OD |
TIACNDS - Table Data | Can the user access the TIACNDS view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PCF30.OD |
TLDS and MVDB2/DC Traces - Table Data | Can the user access TLDS and MVDB2/DC trace log table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PA720.OD |
Trace Display - Action - PMACC# | Can a user other than the original creator of the history trace issue the FREE, DELETE, RESET, ARCHIVE, STARTDIR, or STOPDIR command from the History Traces view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ210.PMACC#.OA |
Trace Package - Table Data | Can the user access trace package table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PG100.OD |
TRLTRAC - Table Data | Can the user access thread trace table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PTD30.OD |
TRSTRAC - Table Data | Can the user access thread trace detail data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PS300.OD |
Users - Any Action | Can the user enter actions (cancel commands) for active threads in the thread users views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.PU010.AO |
Users - Table Data | Can the user access users (thread) table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PU010.OD |
Utilities - Action - Objects | Can the user enter the Objects action command on the utilities views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2.targetid.PY100.OBJECTS.OA |
Utilities - Action - Terminate | Can the user enter the Terminate action command on the utilities views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2.targetid.PY100.TERMINAT.OA |
Utilities - Any Action | Can the user enter the Terminate action command on the utilities views? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.PY100.AO |
Utilities - Table Data | Can the user access utilities table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PY100.OD |
Verify Trace Action | Can the user enter the V (Verify) line command on the history trace view? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution: BBM.MVDB2. targetid.QQ210.VERIFY.OA |
Workload Definitions - Action - Edit | Can the user edit MainView for DB2 workload definitions? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution:BBM.MVIMS. targetid.FAB10.EDIT.OA |
Workload Definitions - Action - Install | Can the user install MainView for DB2 workload definitions? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.&INTACTION.OA Entity name after substitution:BBM.MVIMS. targetid.FAB10.INSTALL.OA |
Workload Definitions - Alter Data Set | Can the user alter MainView for DB2 workload definitions? Class name: DATASET Entity name: &DSN |
Workload Definitions - Any Action | Can the user enter any commands from MainView for DB2 workload definitions? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.PAB10.AO |
Workload Definitions - Table Data | Can the user access workload definition table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PAB10.OD |
ZPARM - Any Action | Can the user enter any action in the ZPARM views to change DB2 parameters through OPERTUNE? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.AO Entity name after substitution: BBM.MVDB2. targetid.PZ100.AO |
ZPARM - Table Data | Can the user access ZPARM table data? Default entity name: BBM.&PRODUCT.&CONTEXT.&INTTABLE.OD Entity name after substitution: BBM.MVDB2. targetid.PZ100.OD |
Related topic