DSXchange

Did you look up what that -16 means?

$DSHOME/include/dsapi.h

Do the MERGE 'After SQL' once the work table has been loaded.

I'm unclear why you would get all of the others correct and yet those first two wrong. :? You have to count the number of digits plus the explicit decimal plus the sign. You seem to have missed the last two elements making your 'field width' off by 2: the first should be 11 and the second 13. X56216...

Your first two field sizes are incorrect.

Of course. Show us how you defined them as that is where your problem lies.

hargun wrote:This job has been ran fine previously except the last 10 fields i have added.

OK, that's an important bit of news that should have been in your first post. That means the problem is confined to the definition of the last 10 fields. How have you defined those fields?

Probably best to use the CFF stage to read this as you can import the copybook directly... are you? It's important to understand that you must define each and every field size correctly in order to read any fixed-width record without error since there are no delimiters involved, it is (in essence) r...

As noted, once again... depends.

From what I recall, only istool runs on the server and that doesn't handle dsx files. That doesn't mean you can't use it however. The client side is the expected side for imports and exports and where command line functions like dsexport and dscmdexport live. let me know if there is any way to add o...

OK. Where's the rest of your copybook?

Bottom line is your metadata in the stage is not correct. That and the copybook and data example don't really seem to match.

Your LOAN NUMBER is "20005199394" and the STATUS is "C-O"? Doesn't seem correct.

Parameters are bound in when the service is deployed, from what I recall. Of perhaps for one that is not 'always one' it could be when the service is spooled up. For the latter, you could look at building a values file and leveraging that. However, let's discuss the exact nature of this 'dynamic whe...

Aha! Good catch.

That's a bit... odd. Have you contacted your official support provider?