|
I noticed something interesting the last night... I was executing a BRMS backup process using a System Operator user profile called BACKUP. User profile BACKUP is a member of the QSYSOPR group, which has *SAVSYS and *JOBCTL authority. What was interesting was I submitted the BRMS backup from user BACKUP and it began executing under that profile. When I tried to take a look at the active jobs job log I received a "Not Authorized" message. In other words I was unable to look at the job log of my own job... When I looked into this further I found that the first thing the BRMS backup process did was a SWAP to user profile QSECOFR. This explained why I couldn't view the active job's job log even though I had *JOBCTL authority... What I'm trying to understand is why the BRMS backup process needs to SWAP to QSECOFR in order to backup the IFS, even though the BACKUP user profile has *SAVSYS special authority. Is *SAVSYS special authority ignored in the IFS just like program adoption authority is??????????? Kenneth **************************************** Kenneth E. Graap IBM Certified Specialist AS/400e Professional System Administrator NW Natural (Gas Services) keg@xxxxxxxxxxxxx Phone: 503-226-4211 x5537 FAX: 603-849-0591 ****************************************
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.