Most likely case is output variables that have not been initialized. It
should be a habit before starting anything that output variables are
initialized/cleared.



"WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx> wrote on 08/30/2019 01:00:22
PM:

From: "Nadir Amra" <amra@xxxxxxxxxx>
To: "Web Enabling the IBM i \(AS/400 and iSeries\)"
<web400@xxxxxxxxxxxxxxxxxx>
Date: 08/30/2019 01:00 PM
Subject: [EXTERNAL] Re: [WEB400] IWS "Low-order nibble of the byte
at array offset 526 is not valid. Byte value: 00."
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>

The data you are trying to insert into a filed is not valid or
compatible
with the field.

What are you sending in and how is the structure defined?



"WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx> wrote on 08/30/2019
12:25:25
PM:

From: Booth Martin <booth@xxxxxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"
<web400@xxxxxxxxxxxxxxxxxx>
Date: 08/30/2019 12:25 PM
Subject: [EXTERNAL] [WEB400] IWS "Low-order nibble of the byte at
array offset 526 is not valid. Byte value: 00."
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>

I can't figure out what is happening/wrong, nor do I know where the
error message is coming from, nor where to look for the answer.

"Low-order nibble of the byte at array offset 526 is not valid. Byte
value: 00."

I have a service program which reads a data record and loads the field

values into a data structure defined like the record. That data
structure is processed by an IWS wizard and the output is supplied as
a
web service. When the web service is accessed from the web I get that

error message.

I am suspicious that the issue revolves about issues with packed
fields
and zoned fields but can't prove it one way or another.






As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.