SETUSRBRM vs adopted authority -- MIDRANGE-L

Subject: SETUSRBRM vs adopted authority
From: Rob Berendt <robertowenberendt@xxxxxxxxx>
Date: Fri, 28 Jun 2024 12:04:02 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Apparently you cannot do a SETUSRBRM from your custom QSTRUPPGM just by
using adopted authority. You either have to change
- QSTRUPJD *JOBD to run under a higher profile,
- submit off a job which runs under a higher profile
- Do profile switching.

BRM4023:
Message . . . . : *SECADM required for SETUSRBRM.

Cause . . . . . : *CURRENT does not have *SECADM authority. *SECADM
authority is required to use SETUSRBRM.
Recovery . . . : Get the necessary authority from your security officer.
Then try the request again.

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.