×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




You may have more than one PWRDWNSYS command existing on your system, with one of them a user-created command. Issue the command as QSYS/PWRDWNSYS and see what happens.

Pat Barber wrote:
I just tried a small test.

I created a brand new profile called "sample" with the class being
*sysopr. The system also added *jobctl and *savsys for some reason.

I signed on with the new "sample" profile.

Exact same result as prior message.


Message ID . . . . . . : CPD0032 Date sent . . . . . . : 12/31/07 Time sent . . . . . . : 16:16:04
Message . . . . : Not authorized to command PWRDWNSYS in library *LIBL.
Cause . . . . . : An attempt was made to access a command without adequate authority.
Recovery . . . : Obtain authority from the security officer or the command owner, and then try the command again.


rob@xxxxxxxxx wrote:

From the help on PWRDWNSYS:
Restrictions: 1. To run this command, the user must have job control (*JOBCTL) authority.
Now, QSYSOPR on our machines has *JOBCTL. Does yours?

Rob Berendt


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.