DSXchange

Hmm... where is the corresponding change in the conversion? It looks like OConv is still delivering the time in AM/PM format and it needs it to be in Military / 24 Hour format, hence the HH24 in the picture. So rather than the end result being '2006-08-29 05:00:00pm' it should be '2006-08-29 17:00:0...

Result is 2006-08-29 05:00:00pm But the issue is ,Orcale is not accepting this and throws an error as ORA-01830: date format picture ends before converting entire input string Because, by default, Oracle is not expecting a Timestamp in that format. It wants what you had before you converted the tim...

Director: Tools / Options / Limits - set it there. Keep in mind that this is not a global setting, but is a per user setting.

A script or 'wrapper' process that uses dsjob to run the job rather than using the Director to run it. That script can have the "-warn 1" in its command line to enforce that rule. The only other way would be to change the default in the Director so that it defaults to aborting after 1 warning, but t...

YES, of course. You need to 'nohup' what you are doing.

Now since i am running the job through Sequence, i don't have control to set the job limit. Sure you do... or at least you should. If you run the Sequence job itself with a Warning Limit of 1 it should pass that limit to all child jobs it runs automatically. As noted, it's supposed to be as easy as...

I'd take your situation and messages to whomever is handling your JBoss installation. Where is your repository stored for RTI - the default Derby database or a relational one? Any chance that those connections are being closed by some kind of idle timeout?

No problem other than the fact that it will add that warning to every job, every run that is.

I'll have to check that out as it's been a long time since I've done much of anything with the RA. Unless you've migrated the repository to something else, that would require some knowledge of Access... not all my peoples do. And I don't believe the Reporting Assistant supports Sequence jobs, do it?

Make sure your O/S supports positive offsets with the 'head' function if you are thinking about doing this. HP-UX 11 does not, for example.

It does work and is actually a pretty standard technique for handling static values across a job's run. Custom routines can be leveraged in the Initial Value derivation of a stage variable for consistancy across jobs. And then, as noted, leave the derivation empty in the job so it retains its initia...

Sorry Kim. Take heart, I'll be off on vacation for over three weeks next month - plenty of time to catch up then.

is this correct? That looks just fine. Of course, you could inline the functions like Narasimha has noted if you were doing it in a derivation. For a custom routine I'd probably do them all separately as you've done. Easier to read and easier to maintain. One of the Grognards would have to comment ...

vmcburney wrote:You can export the jobs to dsx files and run diffs against it.

This is what I would recommend you check out. It's easy to do as long as you have a good visual diff tool (like UltraEdit for example) and simple for people to understand what they are seeing. Typically.

Use the DSJobInvocationId macro instead, wrapping it in hash/pound signs if you are using it for part of a filename.