try DSPUSRPRF USRPRF(ASSETS) TYPE(*GRPMBR) to make sure that no one is
using the profile as it's group.
Thanks,
Tommy Holden
"Rubino, Jim" <Jim.Rubino@xxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
06/19/2007 12:24 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc
Subject
RE: DLTUSRPRF fails with CPF22BF-User profile not deleted.
Rob,
You are correct this should have. Let me ask a dumb question, is this
user id signed on somewhere? Is there a job on the system that was
started by this user (do a wrkusrjob markp)?
Jim
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, June 19, 2007 12:09
To: Midrange Systems Technical Discussion
Subject: RE: DLTUSRPRF fails with CPF22BF-User profile not deleted.
No, the OWNOBJOPT(*DLT) should have blasted them to kingdom come.
WRKOBJOWN shows nothing.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
"Rubino, Jim" <Jim.Rubino@xxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
06/19/2007 12:45 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc
Fax to
Subject
RE: DLTUSRPRF fails with CPF22BF-User profile not deleted.
The user may have a MSGQ, JOBD and OUTQ that they own, you will have to
remove them as owner/authority or delete these first then try and delete
the user profile.
Jim
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, June 19, 2007 11:00
To: midrange-l@xxxxxxxxxxxx
Subject: DLTUSRPRF fails with CPF22BF-User profile not deleted.
DLTUSRPRF USRPRF(MARKP) OWNOBJOPT(*DLT)
CPF22BF-
Message . . . . : User profile MARKP not deleted.
Cause . . . . . : User profile MARKP cannot be deleted because the
user
profile still owns objects or is the primary group for objects.
Recovery . . . : See the previously listed messages in the job log
using
the Display Job Log (DSPJOBLOG) command or press F10=Display messages
in jo
log. Correct the errors and try the command again.
CPDA0B2
Message . . . . : A request to remove all links for an object failed.
The
object has no name. Condition 1 exists.
Cause . . . . . : An internal function requested that all links for an
object be removed. However, the object has no name. The object was
detected
as being in condition 1. The meaning of this condition code is: 1.
The
object is in use by some job, but the object's name has been removed.
2.
The object exists but it can not be used by any other job because it
has no
name.
Recovery . . . : The user's response depends on the condition code
returned. The responses are: 1. Wait until the job which has the
object in
use releases it. Then, retry your requested function. 2. Run the
RCLSTG
(Reclaim Storage) command to give the object a name in the "QReclaim"
directory. Then, you can retry your requested function.
IBM gave us the Microsoft Answer: IPL and see if it still happens. If
so, there is a new V5R4 command:
RCLOBJOWN USRPRF(MARKP)
Requires dedicated state or you will get:
CPF8208
Message . . . . : System not in proper state to reclaim objects by
owner.
Cause . . . . . : Either all the subsystems were not ended before
running
the RCLOBJOWN command or there is a system job still running.
Recovery . . . : Do one of the following and try the RCLOBJOWN
command
again:
-- End all subsystems by using either the ENDSBS or the ENDSYS
command.
-- If the RCLOBJOWN command is run after an IPL, you may need to
wait
several minutes for the IPL to complete. Use the Work with Active Jobs
(WRKACTJOB) command to verify that no jobs are running and the status
of all
the subsystems is not active.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.