Hey Birgitta,
It is not journaled. And my command statement is as follows...
RUNSQLSTM SRCFILE(BMSRC/QTXTSRC) SRCMBR(RCM#RSQL) COMMIT(*NONE)
I have the table create statements right before this. Then I'm going to
insert my data. Then I'll have some sanitation statements. But I can't
get it to insert the data.
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
"Birgitta Hauser" <Hauser@xxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/06/2010 12:44 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc
Subject
AW: Statement gives error in RUNSQLSTM
Just an idea:
1. Is your file registered in an journal?
2. If not are you executing your SQL-Statement (RUNSQLSTM) with commit
*NONE?
3. If execute your Script with commit *NONE or add with NC (which means
"with no commit") to the end of your insert statement.
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 Bryce Martin
Gesendet: Wednesday, 06. October 2010 17:41
An: Midrange Systems Technical Discussion
Betreff: Statement gives error in RUNSQLSTM
This statement gives an error in RUNSQLSTM but runs fine from an
interactive sql tool.
INSERT INTO BMDATA/RCM#NAME (K, V) SELECT TRIM(CNME), CCUST FROM
BPCSFFG/RCM WHERE CMID = 'CM' AND CNME NOT LIKE '**%';
Here is the error...
SQL0199 30 9 Position 8 Keyword INTO not expected. Valid tokens:
FOR
WITH FETCH ORDER UNION EXCEPT OPTIMIZE.
It has not been a good SQL day so far for me.
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
--- This message (including any attachments) is intended only for the use
of
the individual or entity to which it is addressed and may contain
information that is non-public, proprietary, privileged, confidential, and
exempt from disclosure under applicable law. If you are not the intended
recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited. If
you have received this communication in error, please notify us and
destroy
this message immediately. ---
--
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.
--
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.
--- This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us and destroy this message immediately. ---
midrange.com
