HI well my main problem was number one sending them some Numeric fields. Funny that he never mentioned this before. One of them had trouble with leading zeros (funny the other did not but its len is 3 not seven. )
So never do that with UPS worldship.
For now its working but I have to make a field len change so maybe I can do that myself.
Thank you to all who responded,
Adam
--- On Mon, 8/18/08, Adam West <adamster@xxxxxxxxx> wrote:
From: Adam West <adamster@xxxxxxxxx>
Subject: Re: UPS WorldShip issue
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Date: Monday, August 18, 2008, 3:38 PM
Dave, the problems is not the segregation of types of records but that they have
only one format in use, and it is expecting new fields for all types. I have
been initialzing but I think that the fact that it is done via PC transfer ..CSV
files is the problem.
--- On Mon, 8/18/08, Dave Boettcher <DBoettch@xxxxxxxxxxxxxxxx> wrote:
From: Dave Boettcher <DBoettch@xxxxxxxxxxxxxxxx>
Subject: Re: UPS WorldShip issue
To: RPG400-l@xxxxxxxxxxxx
Date: Monday, August 18, 2008, 3:10 PM
No experience with Worldship, but a suggestion may be to use a logical file
with only the records I and N instead of sending them the Physical file. I have
used this trick several times when sending files.
hth,
Dave B
Adam West adamster@xxxxxxxxx> 08/18/08 8:56 AM >>
UPS package shipping uses an application written in VB called Worldship. We are
having some issues with their system. They say they cannot differentiate
between
our record types.
We have recently added some fields that they need anyway for example the weight
of the item we know from our AS/400 files and don't need to have the user
weight and key we can download this and a couple of others. However, what
happens is their application wants thes new fields on all types of orders. We
have orders from the web, and also other orders such as repairs or regular
orders to small stores, these have more complicated weights and cannot be
automated.
The internet orders are coded in the first position of the Invoice Number
field, and can be differentiated from other types of orders that are not part
of
the new fields process.
We have asked UPS to allow their applcation some logic conditions to only worry
as it were about the I and N orders in terms of the new fields, but they cannot
make this happen.
I was wondering if anyone had expereinced this problem and came up with some
kind of 'work around' or method of coding the fields sent to their Flat
file that would help us. Or possibly, what defaults should I be using say for
our numeric fields. It seems like it crashes even when I default to zero. The
UPS fellow I am working with said he had Null fields, if so, what should I be
using when I initialize my fields?
midrange.com
