Re: SQL Collection Question -- MIDRANGE-L

You did not mention the version and release or cume level....

but... Yes, there have been problems like that in other cume packages.
As of V5R2 and Cume 3161 *and* HIPER level 72  *and* DB groups for level
8... even the 'invalid date in a null field' problem went away.

Note that the HIPER group in particular was not the HIPER group shipped with
the original cume package. If your PTF 'guy' ordered the cume before and
applied it recently, he should have updated the HIPER and DB groups at least
just before applying the package. HIPER groups can change quickly and
recently, they have.


===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - iSeries Administrator
 -- IBM Certified Specialist - RPG IV Developer

"When I die, I want to die like my grandmother who died peacefully
  in her sleep. Not screaming like all the passengers in her car."

    - Author Unknown

----- Original Message ----- 
From: "Dave Boettcher" <DBoettch@xxxxxxxxxxxxxxxx>
To: "'Midrange-L'" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, September 09, 2003 11:43 AM
Subject: SQL Collection Question


> We have a Visual Basic program that runs on a PC and copies an Oracle
> database to an SQL collection on the iSeries using an ODBC connection.
This
> program has worked fairly well for some time now.
>
> On Monday, the VB program received an error for every one of the 92 tables
> we are duplicating.  Most of the errors we are getting on the download
> involve two messages.  For one example we are moving a "Y" to a 1 char
alpha
> field and the message is "Application uses a value of the wrong type for
the
> current operation".  A second example is putting a 7 digit number in a 15
> digit packed numeric field and message is "Out of range".
>
> The only thing we know of that has changed is that a cumulative PTF
package
> was installed on the iSeries over the weekend.  The person who knows the
> most about the PTFs is out sick.
>
> We did try to recreate one of the tables in the SQL collection and
received
> the same error as before.
> Before we do something rash, does anyone know of any explanations for our
> problems?
>
> Thanks in advance for any insights.
>
> Dave  Boettcher
> David P. Boettcher CCP
> Senior Systems Analyst and Coordinator
> IBM Certified Specialist - RPG IV Developer
> Kenosha County Information Services
> County Courthouse, Kenosha WI
> * e-mail: dboettch@xxxxxxxxxxxxxxxx
> %  Voice: 262.653.2520
>
> All wiyht. Rho sritched mg kegtops awound?
>
> _______________________________________________
> 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.
>