DSXchange

Pretty much just like that. Was hoping the OP would take a stab at it on their own first, however.

But don't think you still need to Abort the Sequence to trigger the checkpoint restarting you no longer have. Abort it for other reasons, perhaps, but not that one.

OK, that's what I was afraid of. COMP-3 is packed decimal and packed is packed, not even EBCDIC or ASCII technically, just... packed. It can look like hex data if you look at the raw data, but it isn't. Why are you "not able to read it" using the CFF? What exactly are you doing and what er...

It has everything to do with the Health Monitor's "let me know when utilization goes over 85%" alarm going off now that it's at 91%. Suggest you talk to your DB2 DBA.

Only time for very short answers this morning:

1. Yes.
2. Yes, technically.
3. Backup, backup, backup. Config info comes with the product.

You'll have to declare the output as a string and then trim any trailing zeroes. After that, the comma too if it is now the last character.

sridharvg wrote:Can anyone tell me about the Direct and Conventional paths used in Oracle loader and also how are these related to indexes.

Sure, your DBA.

Then it's time to mark your post as Resolved it seems, using the button at the top of the page.

MT wrote:There are not so many guys having RTI experience anyway

Unfortunately true. Perhaps Ernie will add something once he comes back from his self-imposed exile.

ps. There is a dedicated "RTI" forum here. FYI.

There are 62 matches for that error message. I picked one at random and it seems to have everything you need in it. If it doesn't help, please let us know why, which part isn't making enough sense and we'll see what we can do about that.

Unfortunately, the only place "Unable to get Eobject" has been mentioned is in this thread. You'll need to take this to your official support provider, it seems.

What makes you think you have "hex data" in your COMP-3 field?

Why do you think this needs to be resized? I'm curious what brought you here, asking that. Are you having... issues?

Then it seems you need to look at whatever checks the last character of the Invocation ID and how it goes sideways when it is a 'Y'.

So how to design the sequence as my objective before? As already noted. Your requirements preclude the use of the automatic checkpointing, hence the suggestion to disable those compiler options. You need to control the job flow using triggers, for example if you don't want an aborted job to stop th...