--- title: "IBM Db2 for i Profiles and Permissions" slug: "ibm-db2-for-i-profiles-and-permissions" updated: 2025-06-30T14:10:55Z published: 2025-06-30T14:10:55Z canonical: "skthelp.syniti.com/ibm-db2-for-i-profiles-and-permissions" --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # IBM Db2 for i Profiles and Permissions This article describes the specific profiles and permissions you will need if performing replications using IBM i, System i5, iSeries or AS/400. In some cases, Syniti Replicate needs to access or run commands requiring elevated permissions. However, the most important thing to remember is that Syniti Replicate runs on **Windows**, not on IBM i systems. It is a client application which uses the Host Database Server to access data. This means that you will see the jobs used by Syniti Replicate as QZDASOINIT jobs and the users as QUSER. There is no job or program that can be run as a standalone i system application. Therefore, the final choice regarding everything Syniti Replicate does on i system is up to you and how you are using and configuring it. **Typical user Profile:** ```plaintext 1.  User class . . . . . .            *SECOFR or *SYSOPR (for QSECURITY=30 or more) 2.  Assistance level . . .            *SYSVAL 3.  Current library  . . .            *CRTDFT 4.  Initial program to call           *NONE    5.  Library  . . . . . .               6.  Initial menu . . . . .            MAIN    7.  Library  . . . . . .              *LIBL   8.  Limit capabilities . .            *NO 9.  Special authority  . . . . . . .  *ALLOBJ   10. Special environment  . . . . . .  *SYSVAL 11. Maximum allowed storage  . . . .  *NOMAX   12. Highest schedule priority  . . .  3 13. Job description  . . . . . . . .  QDFTJOBD   14. Library  . . . . . . . . . . .    QGPL           15. Group profile  . . . . . . . . .  *NONE 16. Owner  . . . . . . . . . . . . .  *USRPRF 17. Group authority  . . . . . . . .  *NONE 18. Group authority type . .          *PRIVATE ``` The group options are generic, on purpose, along with the ALLOBJ special authority. You can of course decide to add the user profile to a group and demand specific authorities from the group for specific objects. In this case, you can remove the SYSOPR and *ALLOBJ authorities and add specific authorities for specific objects. However, this could make Syniti Replicate configuration a bit difficult on your side, since in designing the replications and in testing mirroring features you could clash with specific permissions on system objects which are used to get catalogs or journal contents). Note that Syniti Replicate, during mirroring/synchronization configuration and replication, requires access to [journals and receivers](/v1/docs/ibm-db2-for-i-journal-information) where, ideally, receivers are managed by the system (automatically creating new ones when the active ones are full, unbinding the old ones and binding the new ones.) If you have modified the typical user profile above, you may find a situation where Syniti Replicate attempts to access the next receiver but your profile has no permission to act on the request since the permissions aren't varied dynamically as when receivers are managed by the system. We recommend allowing the Syniti Replicate user profile access to explore the catalog to avoid the need to continuously vary the catalog objects used. **Commands Executed by Replicator Agent and Management Center** Below you can find the commands executed by the Syniti Replication Agent(DR) and Management Center (MC). The commands are all run via QSYS.QCMDEXEC by QZDASOINIT jobs (user QUSER). The values between "<>" are execution-dependent parameters To get journal information (DR + MC): ```plaintext - DSPFD FILE() TYPE(*ATR) OUTPUT(*OUTFILE) FILEATR(*PF) OUTFILE(/DBRSTFIS) - DSPFD FILE(/*ALL) TYPE(*ATR) OUTPUT(*OUTFILE) FILEATR(*PF) OUTFILE(/DBRSTFIS) - Select PHJRNL, PHJRLB, PHJRNM, PHJRIM From .DBRSTFIS where PHJRNL = 'Y' - DSPFFD FILE() OUTPUT(*OUTFILE) OUTFILE(/DBRSTFF) - SELECT WHALIS, WHFLDI, WHFMT FROM .DBRSTFF ``` To read the last journal ID and achieve mirroring (DR): ```plaintext - CALL .JRNSQNM (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) - select count(*) from qsys2.systables where TABLE_SCHEMA =  and TABLE_NAME = - DLTF FILE(/) - DSPJRN JRN() FILE() RCVRNG( ) NBRENT(..) JRNCDE((R) (F) (D) (J *IGNFILSLT)) FROMENT(...) OUTPUT(*OUTFILE) OUTFILFMT(*TYPE3) OUTFILE() ENTDTALEN(...) NULLINDLEN(*CALC) TOENT(...) - select JOSEQN, JOCODE, JOENTT, JOTSTP, JOUSPF, JOOBJ, JOLIB, JOMBR, JOCTRR, JONVI, JOESD from . - DLTF FILE(/) ``` To install the required DBMOTOLIB (MC): This is usually performed by the same user ID that was defined in the System i5/iSeries/AS400 source connection. Installing DBMOTOLIB involves: - upload via ftp of the SAVF file - restore DBMOTOLIB (via HSVR; needs QCMDEXEC) - create stored procedure (via HSVR; needs QCMDEXEC) Journals, source and target: - access to source tables in SELECT mode (for refresh/lookups and mirroring/synchro - DR and MC) - access to source tables journals and receivers with *ALL privileges (for mirroring/synchro - DR and MC) - access to target tables in SELECT/INSERT/UPDATE/DELETE mode (for refresh/lookups and mirroring/synchro - DR and MC) - access the AS400 catalog tables and views in QSYS-QSYS2 (for refresh/lookups and mirroring/synchro - DR and MC) - run stored procedures (for refresh/lookups and mirroring/synchro - DR and MC) **Catalog commands (MC):** These are listed in the Syniti DR/DBMoto file Config/AS400.xml and summarized below. The Config/AS400.xml may be more current than the list below. The commands are used for retrieving catalog info (schemas/libaries, tables, views, indexes and primary keys.) ```plaintext DSPOBJD OBJ(QSYS/@schema) OBJTYPE(*LIB) OUTPUT(*OUTFILE) OUTFILE(QTEMP/DBRSTL) select ODOBNM from QTEMP.DBRSTL order by 1 select ODOBNM from QTEMP.DBRSTL where ODOBNM = '@schema'