New to iSeries.
If I drop and recreate a table with two additional fields, will the journalling be cleared out too? Also will the jounalling be enabled when I recreate the table?
I have this brief........
We need to have the old journal entries (relating to the current layout before the changes) removed as the journal extract procedure will crash if we extract journals containing entries
for different layouts.
After this the journaling will have to be re enabled with both images enabled.
Software/Hardware used:
If I drop and recreate a table with two additional fields, will the journalling be cleared out too?
No.
Also will the jounalling be enabled when I recreate the table?
That depends on how journaling was set up previously. If this is a SQL schema, then it will probably be reenabled. Or if not a schema, then if the library was assigned a default journal, it will probably be reenabled. Otherwise, probably not.
...the journal extract procedure will crash if we extract journals containing entries for different layouts.
Can you describe the "journal extract procedure" a little? That may have a significant impact.
Tom
When you do the DROP, you will need to end the jouirnalling since there will no longer be an object to journal.
When you do the CREATE, you will need to start the journalling again..
The old journal receivers can stay on the system if you need them.
You will be starting a new receiver when to do the STRJRN.
I am not sure what journal extract procedures you are asking about.
It this answer did not give you what you need, please give us more information on the extract.
Thank you so much Charlie Brown.
Do I also lose the permissions when I DROP the table?
Yes, you would loose the Object authorities.
Have you thought about ALTER TABLE insetad of drop and create?
Phil
Hi Phil,Charlie and Tom
The reason I did not use ALTER because I was led to believe that a DROP would sort out my journalling delema. Hence me coming to “the people in the know”.
The developers use a home written app to read the journal and did not want the rows with the OLD layout (excluding the two new columns) on the journal that they were reading.
The developers use a home written app to read the journal and did not want the rows with the OLD layout (excluding the two new columns) on the journal that they were reading.
Yes, but can you describe it?
For example, is it expected always to be running? Does it retrieve entries as they are being added to the journal? Or is it started each day (each week? each month?) so that it quickly grabs the latest journal entries and then quits?
Whenever it is started, how does it know which entries to retrieve? Does it always start with the *CURRENT receiver? …*CURCHAIN? …an explicit receiver name?
General info about its behavior could be useful in considering the process you should go through.
Tom
The design of the Journal “reader” missed a critial design issue .
Since it didn’t allow for different versions of the files. That’s little help at the moment but it’s something to put on the list for a future enhancement.
Phil
In fact, if it’s a critical issue. The journal “reader” needs to be fixed first.
Phil
Thank you once again everyone for the input, all is well and I learnt alot. Regards Wendy