RE: JAVA400-L Digest, Vol 3, Issue 349

I get the same error when I do and insert/update on a file that is not
journaled. 

 STRJRNPF FILE(MILIB/MYFILE) JRN(MYLIB/MYJOURNAL) OMTJRNE(*OPNCLO)

Tony

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]
On Behalf Of java400-l-request@xxxxxxxxxxxx
Sent: Monday, October 03, 2005 1:01 PM
To: java400-l@xxxxxxxxxxxx
Subject: JAVA400-L Digest, Vol 3, Issue 349

Send JAVA400-L mailing list submissions to
        java400-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.midrange.com/mailman/listinfo/java400-l
or, via email, send a message with subject or body 'help' to
        java400-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
        java400-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of JAVA400-L digest..."


Today's Topics:

   1. SQL exception SQL7008 (rene.loiselle@xxxxxxxxxxxxxxxxxx)
   2. RE: SQL exception SQL7008 (Price, Chris)


----------------------------------------------------------------------

message: 1
date: Mon, 3 Oct 2005 11:55:01 -0400
from: rene.loiselle@xxxxxxxxxxxxxxxxxx
subject: SQL exception SQL7008


I have a application using the JT400 Driver to update a table on the as400.
I got the SQL exception SQL7008.

The user have enought right to the file and the journal.
Here the log.

Any Idia how to fix this error

Reni

java.lang.RuntimeException: Error while invoking proxy :
java.rmi.ServerException: RemoteException occurred in server thread; nested
exception is:
      com.ibm.ejs.container.UncheckedException: ; nested exception is:
      java.lang.RuntimeException: Error while executing insertAssociation()
:
java.sql.SQLException: [SQL7008] FMCOCA00 in VMDPRSQL not valid for
operation. [insert into VMDPRSQL.FMCOCA00
(FCCODE,FCCATEG,FCSEQ,FCSTAT,FCUSAC,FCDATC,FCHRSC,FCUSAM,FCDATM,FCHRSM)
values
('CARO','VB',7,'I','strousse',20050928,142732,'strousse',20050930,93237)]
      at
com.vmd.beh.service.proxy.EjbServiceProxy.invoke(EjbServiceProxy.java:118)
      at $Proxy0.deactivateBkpAssociation(Unknown Source)


Reni Loiselle
514-281-7000 ext: 3959

- L'intigriti des informations transmises dans ce courriel n?est pas
garantie par Valeurs mobilihres Desjardins qui dicline toute responsabiliti
quant aux dommages causis par leur modification frauduleuse. - Ce courriel
est confidentiel et est ` l?usage exclusif de son destinataire. Toute
personne qui regoit celui-ci par erreur doit en informer immidiatement son
expiditeur et le ditruire sur-le-champ. Toute autre  utilisation des
informations qu?il contient est strictement interdite. - Le prisent
avertissement ne limite aucunement tout autre avertissement plus restrictif
qui vous aurait iti transmis par Valeurs mobilihres Desjardins.
- The integrity of the transmitted information in this E-mail is not
guaranteed by Desjardins Securities which accepts no liability for any
damage caused by its fraudulent alteration.  - This E-mail is confidential
and is intended for the sole use of the recipient or authorized
representative of the recipient. Any person who receives this E-mail by
mistake shall immediately notify the sender and destroy it. Any other use
of the information therein is strictly prohibited. - In no manner does this
notice limit other more restrictive warnings which may have been
transmitted to you by Desjardins Securities.

------------------------------

message: 2
date: Mon, 3 Oct 2005 17:08:48 +0100
from: "Price, Chris" <Chris.Price@xxxxxxxxxxxxx>
subject: RE: SQL exception SQL7008


You really need to find the next level of information for the error.

>From the SQL message finder:

SQL7008 
Message Text: &1 in &2 not valid for operation. 
Cause Text: The reason code is &3. Reason codes are: 1 
1 -- &1 has no members. 
2 -- &1 has been saved with storage free. 
3 -- &1 not journaled, or no authority to the journal. Files with an RI
constraint action of CASCADE, SET NULL, or SET DEFAULT must be journaled to
the same journal. 
4 and 5 -- &1 is in or being created into production library but the user
has debug mode UPDPROD(*NO). 
6 -- Schema being created, but user in debug mode with UPDPROD(*NO). 
7 -- A based-on table used in creation of a view is not valid. Either the
table is program described table or it is in a temporary schema. 
8 -- The based-on table resides in an ASP which is different than the ASP of
the object being created. 
9 -- Index is currently held or is not valid. 
10 -- A constraint or trigger is being added to a table that is not valid.
The table is in QTEMP, has ASP's that are not the same, or is not an
externally described file, or is not write, update, or delete capable. For a
constraint, the table is a source file or the parent does not have a member.
For a trigger, maximum number of triggers reached. 
11 -- Distributed table is being created in schema QTEMP, or a view is being
created over more than one distributed table. 
12 -- Table could not be created in QTEMP, QSYS, QSYS2, or SYSIBM because it
contains a column of type DATALINK having the FILE LINK CONTROL option. 
13 -- The table contains a DATALINK column or a LOB column that conflicts
with the data dictionary. 
14 -- A DATALINK or LOB column cannot be added to a non SQL table. 
15 -- Attempted to create or change an object using a commitment definition
in a different ASP. 
16 -- Sequence &1 in &2 was incorrectly modified with a CL command. 
 
Recovery Text: Do one of the following based on the reason code: 
1 -- Add a member to &1 (ADDPFM). 
2 -- Restore &1 (RSTOBJ). 
3 -- Start journaling on &1 (STRJRNPF), or get access to the journal. 
4, 5, or 6 -- Perform a CHGDBG command with UPDPROD(*YES). 
7 -- Remove table names which identify files in QTEMP or program described
files. 
8 -- Use tables in the same ASP. 
9 -- Use the EDTRBDAP command to change the sequence of the access path from
HELD to 1-99 or *OPN, or rebuild or delete the unique index or constraint.
10 -- Specify tables that are valid for constraints or triggers. 
11 -- Specify a schema other than QTEMP, or create the view over only one
distributed table. 
12 -- Specify a schema other than QTEMP, QSYS, QSYS2, or SYSIBM. 
13 -- Specify a schema that does not contain a data dictionary or remove all
DATALINK and LOB columns. 
14 -- Specify SQL table for adding the DATALINK or LOB column. 
15 -- Specify an object in the same ASP as the current commitment definition
or end the current commitment definition. 
16 -- Specify a different sequence, or delete the data area associated with
sequence &1 in &2 and recreate the sequence. 
 
SQLCODE or SQLCODEs: -7008 
SQLSTATE or SQLSTATEs: 55019


-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]
On Behalf Of rene.loiselle@xxxxxxxxxxxxxxxxxx
Sent: 03 October 2005 16:55
To: java400-l@xxxxxxxxxxxx
Subject: SQL exception SQL7008


I have a application using the JT400 Driver to update a table on the as400.
I got the SQL exception SQL7008.

The user have enought right to the file and the journal.
Here the log.

Any Idia how to fix this error

Reni

java.lang.RuntimeException: Error while invoking proxy :
java.rmi.ServerException: RemoteException occurred in server thread; nested
exception is:
      com.ibm.ejs.container.UncheckedException: ; nested exception is:
      java.lang.RuntimeException: Error while executing insertAssociation()
:
java.sql.SQLException: [SQL7008] FMCOCA00 in VMDPRSQL not valid for
operation. [insert into VMDPRSQL.FMCOCA00
(FCCODE,FCCATEG,FCSEQ,FCSTAT,FCUSAC,FCDATC,FCHRSC,FCUSAM,FCDATM,FCHRSM)
values
('CARO','VB',7,'I','strousse',20050928,142732,'strousse',20050930,93237)]
      at
com.vmd.beh.service.proxy.EjbServiceProxy.invoke(EjbServiceProxy.java:118)
      at $Proxy0.deactivateBkpAssociation(Unknown Source)


Reni Loiselle
514-281-7000 ext: 3959

- L'intigriti des informations transmises dans ce courriel n?est pas
garantie par Valeurs mobilihres Desjardins qui dicline toute responsabiliti
quant aux dommages causis par leur modification frauduleuse. - Ce courriel
est confidentiel et est ` l?usage exclusif de son destinataire. Toute
personne qui regoit celui-ci par erreur doit en informer immidiatement son
expiditeur et le ditruire sur-le-champ. Toute autre  utilisation des
informations qu?il contient est strictement interdite. - Le prisent
avertissement ne limite aucunement tout autre avertissement plus restrictif
qui vous aurait iti transmis par Valeurs mobilihres Desjardins.
- The integrity of the transmitted information in this E-mail is not
guaranteed by Desjardins Securities which accepts no liability for any
damage caused by its fraudulent alteration.  - This E-mail is confidential
and is intended for the sole use of the recipient or authorized
representative of the recipient. Any person who receives this E-mail by
mistake shall immediately notify the sender and destroy it. Any other use
of the information therein is strictly prohibited. - In no manner does this
notice limit other more restrictive warnings which may have been
transmitted to you by Desjardins Securities.-- 
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.


******************************************************
The information in this E-mail and in any attachment is 
confidential and is intended solely for the addressee. 
Access, copying, disclosure or use of such information 
by anyone else is unauthorised. If you are not the 
intended recipient please contact postmaster@xxxxxxxxxxxxxx
While reasonable efforts are made to ensure these files are free 
of virus infection and offensive materials, if something of this 
nature is inadvertently sent to you, please destroy it, accept 
our apologies and contact postmaster@xxxxxxxxxxxxx with 
details of the sender. We will ensure that action is taken 
immediately to prevent any recurrence. Debenhams accept no 
responsibility for any views expressed by the originator of this email. 


Debenhams Retail plc (reg. no. 83395) Registered in England and Wales. 
Registered office: 1 Welbeck Street, London W1G 0AA.

http://www.debenhams.com

******************************************************




------------------------------