Hi,
Contrary to DDS SQL always tries to start journaling as soon as a table will
be created.
If there is a journal named QSQJRN in your data library/schema, the newly
created table will automatically be registered in this journal. Also if
there is a data area named QDftJrn were the name of a journal and the
appropriate library is stored, the table (and even a DDS desrcibed physical
file) will be registered at creation time.
This message you get is only a warning, that the table could not get
registered in a journal.
If you want to register the table in a journal, you have to go the same way
as with a DDS described physical file, you have to use the CL command
STRJRNPF to register it.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Brian Piotrowski
Gesendet: Thursday, May 03, 2007 20:00
An: Midrange Systems Technical Discussion
Betreff: CREATE TABLE not Journaled
Hi Group,
Instead of creating physical files and compiling to our data library, I'm
thinking of going directly into the SQL interpreter and performing a "CREATE
TABLE" command. I did a small test using SQL, but when I completed it, I
received a message that said:
Message . . . . : Table WD_CONTROL in SPSL created but could not be
journaled.
Cause . . . . . : The table WD_CONTROL was created in SPSL, but the
table
could not be journaled. The journal QSQJRN in SPSL may be damaged,
removed,
unable to accept journal entries, or may not be created. The SQL name
for
the table is WD_CONTROL and the system name for the table is WD_CONTROL.
For
a distributed table, journaling could not be started on all of the
systems.
The journal QSQJRN in SPSL must exist, and be able to accept journal
entries, on each of the systems in the node group.
Recovery . . . : The table was created, but until the table is
journaled,
COMMIT(*CHG), COMMIT(*CS), and COMMIT(*ALL) will not be allowed for
table
WD_CONTROL.
I'm a bit concerned with this message, as we are moving to a HA solution in
the near future that will use remote journaling as it's method of detecting
changes. Of course, this may be a message that I don't have to worry about,
so I thought I'd throw it out to the group for opinions.
The table's data will be added/modified/deleted through an ASP (windows
web) program (no AS400 programs will be accessing this table). The
remainder of this message goes on to tell me to either create the journal or
fix the journal.
I'm a bit foggy on how this "Create journal" process works when you compile
a PF from a source file vs. creating a table from a CREATE TABLE command. I
don't recall seeing a similar message when I compile a PF from a source
file.
Based on this information, what would the group suggest that I need to do to
ensure that this data will be moved from our production i5 to the backup i5
within the HA system?
Thanks in advance!
Brian.
-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Assistant Mgr. - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x343
Fx: 705-435-6746
-=-=-=-=-=-=-=-=-=-=-=-=-=-
midrange.com
