Delete USRPRF in AS/400

2445 pts.
Tags:
AS/400
AS/400 user profiles
USRPRF
Hi all! What are the condition or things should be notified or should be made when deleting a user profile from AS/400? Our application using the USERNAME in master. But i think only its saving the USERNAME in the MASTER PF. If I delete a user profile will it affect somewhere? How can I check these things? Surey

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    First thing to do is change the *USRPRF to PASSWORD(*NONE) STATUS(*DISABLED). That handles the usability of the profile for many things. You can take a little time to investigate other problem areas. Meanwhile, the profile still exists so few problems should result. . We have no way of knowing how any of your applications would be affected. Only your developers or vendors can tell you that. This is your main research area. . As far as the system is concerned, there are three fundamental areas: spooled files, ownership and scheduling. For spooled files, you can run WRKUSRJOB over the user you will delete. Other jobs might show up, but you're first interested if any show up on *OUTQs. (You can use WRKSPLF once you know jobs exist.) You'll need to decide what to do for each spooled file that exists. And any other jobs that are not on an *OUTQ need to be closely examined. I don't know what you'll do about those because each one might have some unusual reason for existing. Generally there should be none. . Run DSPSVRAUTE for the user you want to delete. If any entries are listed, you should determine why the entry was created. You might need to create an entry for a different user who will take over those tasks. . For ownership, you should create a work profile that you can use while deleting other profiles. Run DLTUSRPRF for the one you need to delete, and specify OWNOBJOPT( *CHGOWN yourworkprf ) and PGPOPT(*CHGPGP yourworkprf *OLDPGP). The ownership of any objects will be transferred to the work profile you created. You can later list objects owned by 'yourworkprf' and decide if they should be deleted or they should be preserved and transferred to some actual user. The same kind of thing should be done for any Primary Group associations. For scheduling, you'll mostly want to review all job scheduler entries (both standard and 'Advanced' if you use it, as well as any 3rd-party products you might have). . Technically, you should also review all job descriptions to ensure that none of them have the profile named in the USER() attribute. However, that's something that should be controlled anyway. No one should be putting profile names in job descriptions without a documented reason. . Similarly, subsystem communications entries, remote location name entries and prestart job entries should all be reviewed. Any profiles named on those should be controlled and documented. You can use WRKSBS and then display each subsystem to look at those entries. . There are possibly things I've missed, but those will cover most of it. Other members might have ideas. You might create a basic CL 'script' that runs the above commands one after the other. If you run them once manually, you'll know what to put into your CL. You can use it each time you delete another profile, and you can add to it if new elements are decided. . Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following