I suppose the easy way is to rename my ‘dan shelby’ folder to ‘owner’; however, the fact remains that a development programmer should be able to identify the location of ‘my documents’ with readily available information instead of having to do a work-around.
yeah .. you are right tom.. only few are here.. having the authority to do those kind of changes.. many thanks for your help
i’m really ..not getting what to do right now..
If you have system auditing enabled for *DELETE, the system audit journal (QAUDJRN) will have a T/DO entry. You have a basic timeline that begins at the date of your last save and ends at the time you discovered the missing trigger.
.
Use the DSPAUDJRNE ENTTYP(DO) command to list entries in the time range. Search the output report for the physical name of the trigger to find a precise timestamp. Then use DSPJRN to look at actual T/DO entries from QAUDJRN to see details.
.
Without useful database journal receivers (that possibly ought to be saved for the previous month), the system audit journal is your only reasonable chance.
.
Since only a couple people should have authority to delete something like a database trigger, you should only have to ask those few.
.
Tom
yes Tom, we thought of using SQL delete before as to clear the file.. but it cannot be done as the file is added with delete trigger.
I thought of using the DDM and to create a new file by adding trigger in that..
As the data from ATM is copied to the new file using DDM, and to add all three after trigger in the file.. which will call RPG program,,as to compare the new file with the file in banking system.
and if a record is not there the trigger program will delete that record from the banking system.like wise for update and delete…here clearing is not done..
but all the triggers will work ..as correctly.. I hope so
oh no.. we got journals only for three days ..
I restored last months file and found that the trigger was present on the file
There are two files that you have mentioned: file (A) and file (B). The way that you have described the problem, only file (A) is causing a problem.
If file (B) is being locked, then please explain why its lock needs to be *EXCL since that’s the only lock state that could be any problem, and a trigger should not be involved in an *EXCL lock on its own file. Any lock state less than *EXCL won’t stop you from copying from the file.
In any case, it doesn’t matter if it’s one system or two systems. It doesn’t matter if DDM is used. If a lock prevents the copy, it will be prevented no matter what.
.
As far as your description goes, the problem comes from the *REPLACE option. You can’t use that if you have a DELETE trigger on the file even if their is no lock at all. You must either remove the DELETE trigger, disable the DELETE trigger, or use a different method to clear the existing records from the file.
.
To clear the existing records, you can use a SQL DELETE that deletes each record that needs to be removed or you can write a program that reads through the file and deletes the records.
.
Tom
you are right
So instead of doing the clear operation.. as I told these are two different systems..
and is there any other way .. that we can compare both the two files.. and do insert, delete, update accordingly ?
Any way of using DDM ??
Ah, and that assumes that the trigger is enabled. If it’s been disabled, it won’t fire. — Tom
The schema journal will have a D/TD entry for the deleted trigger. — Tom
Why ask? If you issue a SQL DELETE statement against a table that has a DELETE trigger, then the trigger will be activated.
.
That’s pretty much the whole point of a DELETE trigger. It wouldn’t have much value if it didn’t run when you issued a DELETE statement against the table.
.
Tom
Actually, come to think of it, I don’t know you can run a ‘clear’ type of operation against a table that has a DELETE trigger. If you use SQL DELETE statements, it should work.
.
There have been a few oddities related to ‘clear’ operations in different releases. I need to go back and read the Memo to Users documents for a few releases to remember what the details are for each release.
.
A ‘clear’ operation is something that causes all rows to become effectively deleted at once, for example, a CLRPFM or CPYF *REPLACE. If a DELETE statement has no WHERE clause, it can also be run by DB2 as a ‘clear’ operation.
.
Tom
well all i can say is if you feel too much information is shared, then dont use it. I will give an example, my friend whose friend always tag him in fb for pictures decided to remove his fb account as he dont want to be tag or featured so much.
i too for once diactivated my fb account for a month and without it dont really make much difference. so its a choice people will have to make.
awaiting your quick reply…
Guys.. we got a problem here.. our file is associated with Inser and delete trigger.
so will an SQL delete query execution will trigger the job attached ?
In general, the FTP commands are the FTP commands that would be used anywhere. Use GET to receive a file; PUT to send a file; and most others are similar.
Please check this link







