MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2014

Re: Trigger setup not working



fixed

Good info here, man

It is a good reminder to all of us, to remember how to do good, old-fashioned job log analysis. The message we see is almost NEVER the real problem, it is usually reporting there WAS a problem, now go look at the stuff that created it.

One thing to add is to remember to use F9 when a message is displayed - this will show the from and to programs and can be very helpful with our own programs - not so much, I find, with IBM stuff, especially SQL.

I think this is similar to Java stacks, as well - those long interminable lists of messages - the one at the top is not really what is the cause, it seems - we have to burrow down the stack to see the issue.

Glad you found the problem - this kind of thing is why Alan Campin wrote his trigger mediator - that app helps avoid problems with locks on files when adding/changing/removing triggers. Worth checking out!!

Vern

On 7/17/2014 8:39 AM, Hoteltravelfundotcom wrote:
according to the message i see now that there is a logical on the PF in
question, in fact there are 15 people with locks on this! thank you kindly
for your help.

OS is 5770SS1 V7R1M0 5050 IBM i
Release of base option . . . . . . . : V7R1M0 L00
TL13037 Temporarily applied
TL12279 Superseded
CPF3203 Diagnostic 40 07/17/14 08:44:24.029714 QDBTRIG2
QSYS *STMT QDBTRIGG QSYS
From module . . . . . . . . :
QDBTRIG2
From procedure . . . . . . :
QDBGEN_SEND_PGM_MSG
Statement . . . . . . . . . : 1604

Message . . . . : Cannot allocate
object for file TRNSTATPF in ASTCCDTA.
Cause . . . . . : The requested
operation was not performed for member *N
file TRNSTATPF in library ISTDTA,
because member *N file TRNSTAT1 in
library ISTDTA type *FILE was not
available. Recovery . . . : Ensure
the object is not locked in another
process or in another thread within this
process. Also, ensure the object, or
a logical file based on the object, is
not open in this process. Try the
request again when the object is
available.



On Thu, Jul 17, 2014 at 9:28 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 7/17/2014 8:50 AM, Hoteltravelfundotcom wrote:
I get this message: but the object has no lock on it.
I have security officer User level. What else can it be? i am able to add
triggers in other libraries on this file.

ADDPFTRG FILE(ISTDTA/TRNSTATPF) TRGTIME(*AFTER) TRGEVENT(*UPDATE)
PGM(PRJLIB78/CRREPCL)
Trigger operation not successful.

>From program . . . . . . . . . : QDBTRIGG
From library . . . . . . . . : QSYS
Instruction . . . . . . . . : 0370
Is this intended to be a general discussion of the myriad ways ADDPFTRG
can be 'not successful'? The reason I ask is that there are very few
details with which the list can work. This will result in time
consuming back and forth messages as individual list members ask for
clarification on one point or another.

Please help us to help you. With every question, please include:

1) The operating system version and Technology Refresh level. This is
important because different capabilities are available with more recent
operating system versions. DSPPTF and WRKPTFGRP will find these.

2) The full first and second level message text. This reveals the error
message ID (in this case, CPF32C6) as well as any reason codes and
recovery operations (in this case, 'See the error messages previously
listed.').

3) The full first and second level text of the previous messages in the
job log. The architecture of IBM i is that a given process will issue
informational and diagnostic messages before failing with an escape
message. Those diagnostics are the actual reason the process failed.

4) The command that caused the failure (supplied here, thank you). This
is important because seeing the exact parameters can reveal the root
cause. Often, the simplest way to provide all of this information is to
DSPJOBLOG OUTPUT(*PRINT) and copy/paste the result in the initial question.

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








Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact