DSXchange

Perfect! Thanks Chuck.

Hi,

I'm looking for the DS7.5 new features PDF. I believe it is available from the ADN site but my login has gone haywire for now... If someone is able to email it to me ASAP it would be most appreciated.

chrisk@altis.com.au

Thanks,
Chris.

Thx Ray.

On the suggestion of a colleague I've gone with:

oconv(loMSGPMT_inp.T_TRA, 'MY')

Ta,
C.

Hi, The query below returns the following results when executed against a SQL Server 2000 database via SQL Query Analyzer. select t_tra, t_moypmt FROM mulprk.dbo.MSGPMT 0x0000000000000000 0x0001 0x0000000000000000 0x0001 0x0000000000000000 0x0001 0x0000000000000000 0x0001 0x0000000000000000 0x0001 e...

The response from my support call to Ascential is that there are 3 manual methods to delete invocation entries from the Status View in Director: 1. Manual Delete 2. Clear Status File 3. Re Compile I've logged an enhancement request for an "Auto-delete" dialog similar to the "Auto-purg...

Nice suggestion Ken and one I've considered. My problem is that my control job will usually run the child job 24 times (1 days worth) but there are times when it has to *catch up* and run multiple days worth. At face value this is no big deal, but we have our own custom job restart mechanism (I won'...

Thanks Kim, Ken and Craig.

I've logged a call with Ascential to see if there's an *official* method. I'll post the outcome.

Ta,
C.

Yes Craig, you have understood me correctly. I was starting to feel like I was speaking an alien language for a while there ;-) However, the problem still remains that I still have 24 new entries per day created in my Status view in Director. Big deal? The downside is that is takes 15-30 seconds for...

Ken,

Are you implying that DS does NOT have the smarts inbuilt to remove these multi instance entries from the Status view in Director?

I'd like to use an inbuilt mechanism if possible rather than going down the "roll my own" path.

Ta,
C.

Some additional info from DS Director help: Note that, if you are running multiple invocations of the same job, all invocations share the same job log. This means that if you, for example, choose to purge entries for all but the last four runs, and the job is invoked 6 times, then the entries for on...

Thanks for your response. Yes, I have tried setting the auto purge options for "JobName". The auto purge option for my job is "Up to previous" 5 runs. However, since each instance name is unique, each instance will only ever have 1 runs worth of log info. Even if it did get to 5,...

Try:

viewtopic.php?t=88931&highlight=dsmakejobreport

Hi, I have a multi instance job that is executed from a control job. The multi instance job is executed 24 times and is passed the hour of the day as a parameter. The instance name is the jobname concatenated with the date and hour. A DS log is created for each instance executed. This results in 24 ...

You could but it would be a very convoluted method. You're better off using backup utilities to backup the database and bulk export/import utilities to transfer data between different instances of the same database. Both of these types of utilities are supplied with all the major DBMS's. Check out t...

I was actually agreeing with you I.e. creating the DAT file with the bulk load stage is still slow in DS7.0. Therefore, using the sequential file stage is still better and doing groovy things like multiple instances of the job will only make it better still!

Ta,
C.