DSXchange

Perhaps dsadmin is the name given to the admin user id in your site.
Since the jobs getting triggered through the current user id, you can make it for sure that, it is related to previlage issue.

ArndW wrote:This is because the F1 through F9 columns are implicitly defined for hashed files, not for SQL access to hashed tables. a "LIST DS_JOBOBJECTS F3" command will work.

Got it.
But did it worked for UPDATE DS_JOBOBJECTS SET F3 = ........

So try with dsadm user id.

ArndW wrote:Yes, F3 and NAME are synonymous.

But SELECT F3 FROM DS_JOBOBJECTS doesnt work for me...

Welcome Aboard :D
Pls give us more information.
What is the error you are facing? Or what makes you to stop runing the job?
By promoting to new environment, the jobs may be readonly.....

What is the error you get?
And what is the value avaialble in the input file?

So the number of rows passed and processed through each row will in divided form.

Try running the underlying job which give the error directly ( not from sequence). That will show you the state of the job whether it is curropted.
Also let know who many job are getting triggered by the sequene at a time? What is the load of the server during the executin of the sequence?

I guess test -z $filename is again a unix command.

Using the same
DSJ.JOBSTARTTIMESTAMP
DSJ.JOBLASTTIMESTAMP

What is the data type for the field you specified?

Look in to Server Job Developers Guide for DB2 and ODBC.

Before going anywhere...
First BACKUP all your exising project.
Do a full export of your project and also do a unix level back up.
From TCL check the pointer strength with COUNT DS_JOBOBJECTS and make sure you are in safer side.

If by dynamically you mean changeable while the job is running then it cannot, nor should it. The parameter is set once when the job starts and remains a given value for the entire time the job is executing in both your example and the README example. A stage variable with a default value that does...

Also depends on the number of column getting pivoted.