Comments on: Change Text Description of All the AS/400 User Profiles (roughly around 1000) in the system.

By: tomliotta

tomliotta — Tue, 01 Dec 2009 19:41:13 +0000

(QSYS qualification isn’t actually needed for CHGOBJD when object type is *USRPRF.)

Tom

By: tomliotta

tomliotta — Tue, 01 Dec 2009 19:39:37 +0000

I say keep it simple. Good point. If that's the primary criteria:

CHGUSRPRF USRPRF(TOML)
          TEXT(&ODOBTX)

...or:

CHGOBJD OBJ(QSYS/TOML)
        OBJTYPE(*USRPRF)
        TEXT(&ODOBTX)

CHGUSRPRF is only slightly more simple. But if simplicity is paramount...? Tom

By: splat

splat — Tue, 01 Dec 2009 15:39:34 +0000

Why use a CHGUSRPRF when a CHGOBJD is specific to the job at hand? If there were changes being made to attributes of the profile object beyond just text I’d agree – as the changes are only being made to profile object’s text, I say keep it simple.

By: tomliotta

tomliotta — Sun, 29 Nov 2009 21:35:04 +0000

Why use a generic CHGOBJD when a specific CHGUSRPRF is available? If maintenance is against a specific object type and an interface is supplied for it, I’d go with the supplied interface. Many other attributes are available with CHGUSRPRF. And the same &ODOBTX would be just as available.

Tom

By: splat

splat — Fri, 27 Nov 2009 16:07:34 +0000

I wouldn't bother with CHGUSRPRF. Running under a profile with the necessary authorities, I'd write a CL to do a DSPOBJD OBJ(*ALL) OBJTYPE(*USRPRF) OUTPUT(*OUTFILE) OUTFILE(library/file), then read through the outfile and execute a CHGOBJD OBJ(&ODLBNM/&ODOBNM) OBJTYPE(*USRPRF) TEXT('New text') on the user profile object. The original text (&ODOBTX) will be available if you're looking to modify existing text.