Logging Process needs another option.

[Bob Hansen]

I have run across an undesirable result when using the logging process while calling a script from a parent script.

I have two separate macro scripts that each have logging turned on, they write to separate log files, and they are both set to log the entry BEFORE running the step.

1. If I run each script independantly, the log files are OK.
2. If I have script1 call script2 then all of the logging for both scripts is in log for script1, that is OK.
3. If I have script1 call script2 and use the /logfile option, then log for script1 is OK, but log for script2 does logging for BOTH BEFORE and AFTER running the step.

Example of line in script1 calling macro script2:

Macro>J:\DATA\MJT\CPU\Script2.scp /logfile=J:\DATA\MJT\CPU\Script2.log

There is no way to get script2 log to use the BEFORE running step mode when called by a parent script.

I know that the default mode is to use BOTH BEFORE and AFTER running step. But I think another option should be added to ID which of the three modes is wanted. It would also be better to just call the other script and let the process use the values already associated with the logging for that macro script.