Home > IT Answers > AS/400 > making CHGOBJOWN faster
Brami06
0 pts.
 making CHGOBJOWN faster
AS/400, DB2 Universal Database
Is there a way to make a command like CHGOBJOWN run faster. Rather than waiting to get an exclusive lock on the object I would rather see the command try once and move on. I still need to capture the fact that the change failed, I just want it to fail quicker if it is going to fail.

Software/Hardware used:
ASKED: November 8, 2005  2:33 PM
UPDATED: November 10, 2005  11:08 AM
RELATED QUESTIONS
Answer Wiki:
add an ALCOBJ before your CHGOBJOWN, this will trap the object lock immediatly.
Last Wiki Answer Submitted:  November 9, 2005  1:28 am  by  JPLamontre   0 pts.
All Answer Wiki Contributors:  JPLamontre   0 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

You could also try using a CHGJOB DFTWAIT(1) command. I believe this should change the default wait time to acquire a lock to 1 second. I believe the default is 30 seconds, but this can be altered depending on how your system is set up.

TheQuigs
 0 pts.
 

about a half hour after I posted the question, I figured it out. I went with the change job option.

Thanks for your responses.

This site is a great tool when you are stuck. Just about everything that can be done on 400 has been done by someone, somewhere at sometime.

Brami06
 0 pts.