DSXchange

Hi,

We have a requirment to move the input file after the job is finished.
I wrote the mv command in after job subroutine and it works fine.

its moving the file if it finished ok or with warning , My query is if the job aborts still it will rename move the file or not.

Thanks

[quote="DSguru2B"]Return code for an aborted job is 3. While running the job, stick in -jobstatus so that the return code of the command will be infact the job status which can be read by [b]$?[/b] Also, search the forum, you will find a variety of shell scripts that does this for you.[/qu...

...by reseting it from unix command dsjob -run -mode RESET <<PROJNAME>> <<SEQName>> thanks...this will reset the sequencer everytime it runs....seems we need to check the return code for abort or failure and then reset if it has aborted .......just wndering what is the return code for job abort...i...

Dont make it restartable. And yes, reset it and then run. It will run from the begining. I think this can not be acheieved if the sequencer fails and its not in restartable mode how the unix script will run it i.e. the sequencer will be aborted state and hence can not be run. We need to reset the s...

Hi, We have sequencer job which is not in restartable mode i.e. if it fails the entire process has to start from begining we do not want it to start from where it fails. Can we reset the sequencer job from unix script we have all server jobs in sequencer been set to reset if required and run. Thanks

Its working as below SELECT CASE_NUMBER FROM "DS_UV_STG_ALIS" GROUP BY CASE_NUMBER HAVING COUNT(*) > 1; Yes you can. What error message do you receive from UniVerse? I just ran a similar query (the only difference being the column names) in UniVerse. SELECT "TYPE","F2" ...

Yes you can. What error message do you receive from UniVerse? I just ran a similar query (the only difference being the column names) in UniVerse. SELECT "TYPE","F2" FROM VOC GROUP BY "TYPE","F2" HAVING COUNT(*) > 1; I also checked with a space between COUNT ...

Thats by default. That number specifies a block of memory to hold the data. One block for writing to and the other is for reading. So if you put 128, that means 256 is specified. So I would say increase that. Let it be a multiple of the complete record size + a few bytes. So I have seventeen fields...

Did you try increasing the buffer size? How huge is your record? Just checked its 512 .....will it make a difference on performance of jobs...as we have nearly 300 job batch cycle and more than 200 jobs might be using IPC stage...... if we make it to 1024 ...changing in env variable for ipc buffer ...

DSguru2B wrote:Did you try increasing the buffer size? How huge is your record?

its 128...how much we can increase is there any formula for it or its an hit and trial methiod.

Regards,

Hi,

I'm trying to use having count(*) = 1 clause in universe table but somehow its failing. Can we use group by , having clause with DS Universe tables

SELECT CASE_NUMBER,LOSS_RPT_NUMBER FROM DS_UV_STG_ALIS
group by
CASE_NUMBER,LOSS_RPT_NUMBER
HAVING
count (*) > 1

Thanks

Hi, We have a job which aborts due to garbage data trailing behind one or 2 columns ..as it appears in director log. But when we reset the job and run it ..it just go fine. The only reason I see is IPC stage , when i remove IPC stage as we done in many other job it runs fine. Is it happening due to ...

Hi, We have requirment: Currently the job has DSJobStartDate defined in transformer for column dervation. We need to make it dynamic i.e. by default it should run for the DSJobStartDate but if user want to change the date he can do it run time by typing values for the param.\ I tried making it the J...

Algorithm design: Find current status. If "Finished OK" then do the remainder. Find start of current run. Find newest "job finished" message prior to that timestamp. Get status from that event. Hi Ray, Tried for 4 hours but seems my skills of playing with DS commands are lil wea...

A job's status is always its current status. That's all you mentioned in your specification. To get previous status requires going to the job log, even assuming that you don't have auto-purge up to previous 1 job run enabled. It would be substantially different code. Hi Ray, Sorry for the confusion...