Maximum number of files on submit

Is there a maximum number of files allowed for a single submit?

Or is it driven by the total amount of data possibly?

thanks!

Find more posts tagged with

Comments

tgerber

Not sure but it always fails for us if we try to submit 100's of files.

jed

Is there a maximum number of files allowed for a single submit?

Or is it driven by the total amount of data possibly?

thanks!

There should be no limit (from the command line). We routinely do a submit of an entire branch which consists of 140,000+ files. It may take awhile at times, but it always finishes.

If you try this from the GUI, you may experience timeout issues which can be alleviated by increasing the timeout threshold of iw-webd.

~jed

Ambuj

Is there a maximum number of files allowed for a single submit?

Or is it driven by the total amount of data possibly?

thanks!

There's no such limit but you should manage your deployment as per the size and number... some threads here provide details on this... search devnet forums..

Frederik

I've noticed that on our implementation (Solaris 9, TS 6.5 sp2) submits via GUI / workflow of several hundreds of files fail. I found that this is caused by the external task in the job.

The iwtrace.log says for instance:

Too many arguments for command /path-to-script/external-task-script.ipl (args: 756, max: 510)

My interpretation is that the workflow adds all the files (and comments?) in the workflow as arguments to the command, and hits an upper limit on UNIX command line arguments.

Things are different probably if one does a submit of one explicit directory, thereby submitting possibly thousands of modified files therein.

ISCBorisB

I've noticed that on our implementation (Solaris 9, TS 6.5 sp2) submits via GUI / workflow of several hundreds of files fail. I found that this is caused by the external task in the job.

The iwtrace.log says for instance:
Too many arguments for command /path-to-script/external-task-script.ipl (args: 756, max: 510)
My interpretation is that the workflow adds all the files (and comments?) in the workflow as arguments to the command, and hits an upper limit on UNIX command line arguments.

Things are different probably if one does a submit of one explicit directory, thereby submitting possibly thousands of modified files therein.

It's been recommended few times on this Forum that iw.cfg should be configured to suppress WF File List parameters
to external Tasks and that TeamSite::WFtask::GetFiles() method used instead

[workflow]
external_task_add_filelist=false