DSXchange

You can say

If IsNULL(Col) Then 'N' Else 'Y'

You need to provide more information. Currently all you are saying is that you have a job which aborts. So how come you expect anyone to resolve your issue.

Unless and otherwise you have any basic scripts that are not version compatable, I assume you can migrate without difficulty.

Maybe for first week no falling fully on either past or present year.

That is because your DS indexes is corrupted. Do a DS.REINDEX ALL from the project via DS Admin or uvsh.

Did you try re-running the sequence?

Week conversion is done taking partial week into consideration.

You may have included an option in the job runtime config setting to run for 100 rows in Limit.

It is part of the dsjob dlls that comes as online manuals pdf.

You can also load your param file in memory and them use scripts to process them. But ensure that your passwords are properly encrypted or hidden.

The dlls and their usage mechanism are explained clearly in the manual

If both are seq files, try using merge stage. You can otherwise use ODBC and enable multiple rows to be returned.

Were any other person changing - e.g. compiling - the job when you are trying to execute your script?

Did you change the DS configuration for files and locks? - if they run fine for low number and fail at certain level.

No.

JobHandle = IsNull(DSAttachJob(TempJobName, DSJ.ERRFATAL))

If IsNULL(JobHandle) Then
Write message
Error ??
End

SetParam

Include a check of job handle being null.