DSXchange

True - I just made a quickie change to the date mask, didn't really look at anything else.

Ah... nothing like a little revisionist history.

You cannot selectively disable links and stages, other than sending nothing down a stream, using @FALSE constraint. Sure you can! Think job parameters. One per link or situation, setting it to true or false, yes or no - whatever makes sense to you. Then add it to your constraint - blab blah blah AN...

Just the year, not the entire date: CASE WHEN MOD(TO_CHAR(RENEWAL_DBG_DTL.X_EXP_DT, 'YYYY'),400)=0 or (MOD(TO_CHAR(RENEWAL_DBG_DTL.X_EXP_DT, 'YYYY'),4)=0 AND MOD(TO_CHAR(RENEWAL_DBG_DTL.X_EXP_DT, 'YYYY'),100)!=0) THEN '1' ELSE '0' END

That helps explain what's going on, but that being said I don't have that issue with multi-instances jobs - they still show the 'Clear status' option as enabled for me. If you do the 'Clear' from the main job itself, all of the 'instance' information will be removed. If nothing is actually running, ...

You might need to contact Support on that one. It's not a phenomena that I recall every seeing.

Unless someone else has and knows the reason why?

You might want to explain how you are doing a 'bulk load' from an OCI stage. I also don't understand why the true Bulk Loader stage wouldn't "serve your purpose"?

What exactly about it "didn't work"? It would still be a single parameter, so you should be able to replace one value with the other and be fine - assuming your routine is expecting a full path.

Might be helpful to post your routine code.

sheema wrote:Now it is working thanks.

Excellent - please mark your post as Resolved.

Start a new thread. We're two pages down a rather twisty path, best to start over. That way we'll know your particulars and you can do a better job of explaining your issue - rather than saying it's 'the same'. We've seen too many shades of 'same' here.

Not positive this will work with fixed-width files, but the 'missing' columns must be from the end of the record and not somewhere in the 'middle'. If that's the case, try enabling the 'Suppress row truncation warnings' option on the Format tab. Assuming this is a Server job as you've marked the post.

Specifically, you've posted in the wrong forum. If you have any further questions on this subject, please create a new post in the linked to EE/PX forum.

ponzio wrote:The sequence parameters are linked properly to the job parameters.

No, they're not or you wouldn't be having this issue. Double-check. Heck, triple-check. Both the 'linkage' and the values being passed.

While you could write specific 'is this a leap year' code, you might also want to consider the following. For your year in question, get the number of days between '01/01/xxxx' and '12/31/xxxx' and use that number for the multiplier. IConv and subtract. Note I haven't actually tried it, just one of ...

Not time right now to do more than say - you should have a BASIC.pdf manual in your Docs directory. That's about all there is on the subject, so assuming that was what was meant.

trobinson wrote:Just an idle thought unhampered by any actual knowledge or experience in the matter.

Need more of that.