|
On Jan 12, 2018, at 1:30 PM, McGovern, Sean <sean.mcgovern@xxxxxxxxxxxxx> wrote:
Try...
Create table qtemp/xxx as (select * from xxx) with data
Sent from my iPhone
On 12 Jan 2018, at 18:13, Jay Vaughn <jeffersonvaughn@xxxxxxxxx> wrote:[CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records. To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.com
hi justin
i do identify bad data in the original post (see the low level sql error
message code 6 and its meaning)
On Fri, Jan 12, 2018 at 1:05 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:--
So the "bad data" is already in the table and you're wanting to identify
it? Can you define "bad data"?
-----Original Message-----
From: Jay Vaughn [mailto:jeffersonvaughn@xxxxxxxxx]
Sent: Friday, January 12, 2018 8:02 AM
To: RPG programming on the IBM i (AS/400 and iSeries) <
rpg400-l@xxxxxxxxxxxx>
Subject: detecting "bad data" using an sql statement
So the only way i know to detect bad data using sql is when doing the
actual insert of the data into another file.
Is there "select" way of doing it instead? And ideally report all rows
back that have bad data detected. also when a select is done in STRSQL
over the file, the bad data shows up as "+++++", so just need to know how
STRSQL detects it and shows "+++++" instead of the data.
example...
insert into ls#jhv.srvfm50 (prefix)
(select prefix from ldataicl.srvfm50)
file ls#Jhv.srvfm50 has "bad data" in it and the following sql error
occurs when the statement is run...
Message ID . . . . . . : SQL0406
Message . . . . : Conversion error on assignment to column PREFIX.
Cause . . . . . : During an attempt to assign a value to column PREFIX
with
an INSERT, UPDATE, ALTER TABLE, or REFRESH TABLE statement, conversion
error
type 6 occurred. If precompiling, the error occurred when converting a
numeric constant to the same attributes as column PREFIX. A list of the
error types follows:
-- Error type 1 is overflow.
-- Error type 2 is floating point overflow.
-- Error type 3 is floating point underflow.
-- Error type 4 is a floating point conversion error.
-- Error type 5 is not an exact result.
-- Error type 6 is numeric data that is not valid.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.