Re: Statement gives error in RUNSQLSTM

[John Jones <chianime@xxxxxxxxx>]

FYI: GMail classified this as spam.  Maybe since it was a comment about
insertion. :)

On Wed, Oct 6, 2010 at 12:29 PM, Alan Shore <AlanShore@xxxxxxxx> wrote:

> Thanks Dan - that makes more sense where INSERT is concerned
>
> Alan Shore
> Programmer/Analyst, Direct Response
> E:AShore@xxxxxxxx
> P:(631) 200-5019
> C:(631) 880-8640
> "If you're going through Hell, keep going" - Winston Churchill
>
>
>
>             Dan Kimmel
>             <dkimmel@rjssoftw
>             are.com>                                                   To
>             Sent by:                  Midrange Systems Technical
>             midrange-l-bounce         Discussion
>             s@xxxxxxxxxxxx            <midrange-l@xxxxxxxxxxxx>
>                                                                        cc
>
>             10/06/2010 12:45                                      Subject
>             PM                        RE: Statement gives error in
>                                       RUNSQLSTM
>
>             Please respond to
>             Midrange Systems
>                 Technical
>                Discussion
>             <midrange-l@midra
>                 nge.com>
>
>
>
>
>
>
> With an INSERT you're creating new records, not changing. K and V are the
> only fields that will have values in the new records. Any other fields will
> have default values or NULL as defined in the CREATE TABLE. One new record
> will be created for each record from the SELECT that match the WHERE
> clause.
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
> Sent: Wednesday, October 06, 2010 11:22 AM
> To: Midrange Systems Technical Discussion
> Cc: Midrange Systems Technical Discussion; midrange-l-bounces@xxxxxxxxxxxx
> Subject: Re: Statement gives error in RUNSQLSTM
>
>
> Hmmmmm - interesting. I did not know that Todays a good day So in this
> instance, there are 2 fields one named K, the other named V that you can
> change on ALL records that meet the selection criteria?
>
> Alan Shore
> Programmer/Analyst, Direct Response
> E:AShore@xxxxxxxx
> P:(631) 200-5019
> C:(631) 880-8640
> "If you're going through Hell, keep going" - Winston Churchill
>
>
>
>             Tommy.Holden@Thom
>             psonMachinery.com
>             Sent by:                                                   To
>             midrange-l-bounce         Midrange Systems Technical
>             s@xxxxxxxxxxxx            Discussion
>                                       <midrange-l@xxxxxxxxxxxx>
>                                                                        cc
>             10/06/2010 12:08
>             PM                                                    Subject
>                                       Re: Statement gives error in
>                                       RUNSQLSTM
>             Please respond to
>             Midrange Systems
>                 Technical
>                Discussion
>             <midrange-l@midra
>                 nge.com>
>
>
>
>
>
>
> (K,V) is the list of fields being inserted into.
>
> Thanks,
> Tommy Holden
>
>
>
> From:   Alan Shore <AlanShore@xxxxxxxx>
> To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Cc:     "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>,
> midrange-l-bounces@xxxxxxxxxxxx
> Date:   10/06/2010 10:55 AM
> Subject:        Re: Statement gives error in RUNSQLSTM
> Sent by:        midrange-l-bounces@xxxxxxxxxxxx
>
>
>
>
> Hi Bryce
> couple of things
> what does (K, V) mean
> I have never seen that and just wondered what it does in SQL
>
> The other question is
> does the file that you are inserting into contain only 2 fields TRIM
> (CNME)and CCUST
>
> Alan Shore
> Programmer/Analyst, Direct Response
> E:AShore@xxxxxxxx
> P:(631) 200-5019
> C:(631) 880-8640
> "If you're going through Hell, keep going" - Winston Churchill
>
>
>
>             Bryce Martin
>             <BMartin@c-sgroup
>             .com>                                                      To
>
>             Sent by:                  "Midrange Systems Technical
>             midrange-l-bounce         Discussion"
>             s@xxxxxxxxxxxx            <midrange-l@xxxxxxxxxxxx>
>                                                                        cc
>
>
>             10/06/2010 11:51                                      Subject
>
>             AM                        Statement gives error in RUNSQLSTM
>
>
>             Please respond to
>             Midrange Systems
>                 Technical
>                Discussion
>             <midrange-l@midra
>                 nge.com>
>
>
>
>
>
>
> 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 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 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.