MONMSG CPF2130 was: CL program

[rob@xxxxxxxxx]

John, 

List etiquette strongly recommends that you do not reply to an existing 
message to start a new thread.  It mucks up the thread in the archive.
Also, if you don't care and continue to do it that way at least have the 
decency to change the subject and do NOT reply "with history".

Back to your problem...
At first I thought that was a totally newbie question and would have 
replied with the obvious
CRTDUPOBJ...
MONMSG CPF2130
However then I thought better and looked to see if CRTDUPOBJ throws a 
different message and you have to monitor for that, and if you get that, 
look further into your joblog with RCVMSG to see what the "real" message 
is.  The answer was no, you can monitor for CPF2130 but you still may have 
to look at the joblog with RCVMSG to see what the "real" message was. Here 
it may be because of any number of reasons.  Sample you have *ALL access 
to some objects but only *USE to others.  For some silly reason CRTDUPOBJ 
doesn't like that.  Which is why I'll often imbed SQL CREATE TABLE... 
statements in my programs to build hollow files in QTEMP instead.  I got 
tired of this horse excrement.

Rob Berendt