On a program object, there are two parameters that affect adopted authority (use the CHGPGM and DSPPGM commands to see, or affect, these parameters). They are the USRPRF and USEADPAUT parameters--and they don't work the way you might think at first.
The USRPRF parameter controls whose authority the program uses when it is executed. It can contain one of two values: *USER or *OWNER. *USER indicates that the program, when executed, will run under the authority of the end user who called it. *USER is the default value for newly created programs and is also the more common usage. *OWNER indicates that the program will adopt the authority of the user profile that owns the program object. If you use *OWNER, when the program executes, it runs with the combined authority of the original end user plus the authority of the program object's owner--sort of a two-fer. In a scenario where program PROGA calls PROGB, and PROGB calls PROGC, and all of these programs are set to USRPRF(*OWNER) and have separate owners, PROGC will run under the combined authority of the original user, plus the individual owners of PROGA, PROGB, and PROGC.
This is what is traditionally known as "adopted authority," and it is very useful for providing users with an elevated level of authority for a short period of time or with a limited amount of function.
The second parameter is more confusing, and the text surrounding this parameter is squarely to blame. The Use Adopted Authority (USEADPAUT) parameter controls not whether a program actually uses adopted authority, but rather whether a program will accept the propagation of adopted authority from a program that was called earlier in the job stack. That is, if PROGA adopts QSECOFR's authority and then calls PROGB, PROGB decides whether or not to accept QSECOFR?s adopted authority when it executes based upon the value specified in the USEADPAUT parameter. If PROGB is set to USEADPAUT(*YES), which is the default value, PROGB will accept and use the adopted authority that a preceding program has acquired. If PROGB is set to USEADPAUT(*NO), PROGB will reject PROGA's adopted authority and run only under the authority of its end user.
When speaking of adopted authority, many OS/400 professionals refer to USEADPAUT as if it controls a program's ability to adopt authority. This is simply not true. For example, if a program is set to the values USRPRF(*OWNER) and USEADPAUT(*NO), the program would adopt the authority of its current owner but refuse to accept the adopted authority of any previously called program. (This is a very handy technique for changing the adopted authority that an end user runs under, while in the middle of a job).
Just to be clear, setting parameter USRPRF(*OWNER) will cause a program to adopt the program owner's authority. Setting parameter USEADPAUT(*YES) causes a program to accept all of the adopted authority set by programs that precede this program in the job stack. And if you get confused, bypass the parameter descriptions on the CHGPGM and consult directly with the help text.
John Earl
PowerTech Group
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online