Skip to main content

Problem:

Is there a way to direct the Addfiles to a certain workgroup level from the MFECL utility ?

for example currently we use something like :

mfecl /addfile %V1-PROJECT% %2 %1\\COPY\\MFE\\*.*

Resolution:

  This can be done, but it depends on how you have built your

Workgroup levels. And it has changed for MFE30 with our Workgroup

modifications, let me give you both scenarios.

If you use a command line such as:

    mfecl /addfile c:\\mydir\\mfeprj.mvp c:\\appsdir\\test2\\*.cbl

and 'c:\\apps\\test2' is listed as a Source Folder in a particular

Workgroup level, then files are added there. If the directory is

not listed in any Workgroup level, then the default for MFE25 is

the bottom level, but with MFE30's changes to the Workgrouping,

the default will be the first enabled (check marked) Workgroup level

if no level has a definition pointing to 'c:\\apps\\test2'.

So you could have commands like these:

    mfecl /addfile c:\\mydir\\mfeprj.mvp c:\\appsdir\\test2\\*.cbl

    mfecl /addfile c:\\mydir\\mfeprj.mvp c:\\appsdir\\test1\\*.cbl

and a Workgroup level such as:

     Test1

     Test2

     Prod

and the .CBL files from test1 will go into Test1 and the files from

test2 will go into Test2. But if you have:

    mfecl /addfile c:\\mydir\\mfeprj.mvp h:\\acc16\\ndr2\\*.cbl

    mfecl /addfile c:\\mydir\\mfeprj.mvp c:\\appsdir\\test1\\*.cbl

then the test1 files will go into Test1 and the ndr2 files will go into

Prod. With MFE30, the files from ndr2 would go into Test1 if it were

enabled. If not, then they would go into Test2 if it were enabled.

And if neither were enabled, they would go into Prod.

I am assuming here that if the MFECL command has a 'test1' or

'test2' or 'prod' definition, that they match the names of the

Workgroup levels.

Old KB# 6709

#MFDS
#EnterpriseDeveloper