Migration Monitor question

Question

Suppose there are 50 dedicated packages for top 50 table and 25 SAPXXXX package in total. I want to:
Load them order by size (seems this is the default setting in migtion monitor)
For those 50 tables, I need specify both DDL file and loadArgs
8 parallel processor used.
My questions:
1) ddlFile & ddlMap parameters can be used to specify the non standard DDL control file. I must set both those 50 & 25 packages into 2 group sections in ddlmap file? Or I can simply set 25 of them into ddlMap.txt and let sapinst use default value (set in import property file) for other 50 packages?
2) ddlMap file can be used to specify the additional loadArgs, such as "-loadprocedure fast LOAD" etc...?
3) If loadArgs must be used in orderby.txt (this is suggested in migration monitor guide), sapinst will not use order by size option, instead, it uses the line order, right?
4) Same as question 1, I must set both those 50 & 25 package into 2 group sections in orderby.txt?
5) If I need set those 50 & 25 packages. I want to know how to defined "package". Every file with STR extension in <exportdir>/DATA stands for a package, am i right? How about SAPVIEW.STR, it can be loaded before all packages are loaded completely?
The migration monitor guidd is really hard to fully understand. I can not find answer for about questions.
Thanks for you comment,
James

Answer 1

Neel,
Yes, you are right.
My test shows:
ddlMap control file just read group and  ddlFile parameter information.
orderby control file does NOT recogonize ddlFile parameter, but loadArgs , no. of jobs  are OK.
So you recommend to use same orderby.lst as both ddlMap & orderby control file, and put all parameters into the same orderby.lst. That is a good idea.
My test also shows:
We do NOT have to list all packages in orderby.lst. Packaged are not listed in orderby.lst will be assinged to a "default group" and use the default ddlFile, loadArgs parameters in property file. SAPNTAB will be checked at the first to identify the codepage. SAPVIEW will be loaded after all other packages are loaded successfully.
*Below is suitable for Ver640:
If we use group concept in orderby.lst, than each group (include "default group") get its own no. of jobs and orderby property. I do NOT find a way to specify individual  loadArgs to each group but use a system wide orderby (order by size of all packages is a good suggestion during import) and no. of jobs parameter.  In traditionaly sapinst mode, if we do not select "Use Migration Monitor" and  select "Individual Configuration for Data Load" option, then we can specify ddlFile & loadArgs, and use a system wide orderby and no. of jobs parameter. So if there is loading conflict (example, you do not want to load 2 big packages at the same time), use Migration Monitor. If there is no loading conflict and more than 1 loadArgs, use "Individual Configuration for Data Load" option.
As for 700, I do not test this point. It works as ver640, I think.
James