× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hmm - I think WRKUSRPRF is a system command, not a TAATOOLS command.

But your point is well taken - WRKUSRPRF will not show when the profile was created. Always good to pick up new tricks.

As to being a *USRPRF object - everything on the system is some kind of object, even things in the non-library side of the IFS. Now the stream objects, I'm pretty sure they can't be processed with DSPOBJD.

Just some thoughts.
Vern

On 3/30/2011 7:26 AM, Bryce Martin wrote:
Man, I surely am spoiled by TAATOOLS. We just do a WRKUSRPRF
YOURPROFILE ---plus it has wildcard support so I can type WRKUSRPRF
MYPRO* and get a listing....

I have never been without TAATOOLS so learning about stuff like this is
good, because it helps me to understand the system better. I never
realized that the user profile was a *USRPRF OBJ. Learn as you go I
guess.


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



David Gibbs<david@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/29/2011 05:09 PM
Please respond to
Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: User profile






John Candidi wrote:
On an old 5.2 version, how do I find out when a user profile was
created?

DSPOBJD OBJ(YOURUSER) OBJTYPE(*USRPRF)

david


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-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.