DSXchange

Cool. Then they can be compared with comparison operators, for example The ISO8601 format (which uses a 24 hour clock) for timestamps sorts and compares correctly when the timestamp is represented as a string.

It really doesn't matter whether you use DB2, Oracle or SQL Server for the Repository. The configuration of 7.x and earlier repository is totally different (being based on a proprietary non-first-normal-form database design) - knowing that will not help you to make any decisions about the 8.x reposi...

It does. And the PXEngine too.

Easiest would be a constraint expression based on IsValid() function.

Welcome aboard. The correct spelling of the present tense plural of the verb "to be" is "are". DSXchange is not a mobile telephone; there is no call for SMS-style abbreviations. Rather, we prefer to maintain a professional standard of written English, not least because it makes l...

You can't not give a condition.

Yes, you ARE calling subroutines - look at the job control code in your sequence. DSDetachJob is one of these. For some reason this has been de-cataloged in this project. It would be nice to find out by whom. In the meantime, export the entire project, create a new project, import everything into th...

Your middle paragraph says it all.

751 is the job number, mapped to the job name in the DS_JOBS table. SELECT NAME FROM DS_JOBS WHERE JOBNO = '751'; 5260 is the process ID of the process that ran the job. Output from these processes (not logs) are only stored in &PH&. Logs for job number 751 are stored in table RT_LOG751. RT_...

This isn't an Orchestrate schema, so you should not be using that option. You should be using Import > Table Definition > Sequential File.

When you import the table definition specify &h0110 as the delimiter character.

Export the entire project, edit the DSX file, then import the entire project with "overwriting" set.

It is a documented requirement that, when there are more than one Update inputs, all Update inputs must be de-duplicated. This does not appear to be the case in your example.

Although weekday/weekend can be done using Iconv(TheDate, "DW") function.

Welcome aboard. Look in the "environment variables" event in the job log to ensure that your Oracle environment variables are correctly set for the user running the job.