Bookmark and Share

Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

st: Stata 11 v Stata 12: difference in batch mode behaviour

From   Dave Ewart <>
Subject   st: Stata 11 v Stata 12: difference in batch mode behaviour
Date   Wed, 5 Oct 2011 16:52:57 +0100

In the following, I use 'stata11' as a command to mean Stata 11's
'stata' and 'stata12' for Stata 12's 'stata.  Both are running on Linux.

I noticed when testing Stata 12 that a previously-working batch job was

The old job was launched as follows:

    stata11 -b

and it put correct output into something.log


    stata12 -b

fails and puts output like the following into an output logfile called

       . doedit 
       unrecognized command:  doedit

Very strange?  It's launching 'doedit' against the supplied DO file?

Then I realised that perhaps I've been playing against the rules all
these years and found that I should actually have been using

    stata11 -b do

(that is, include the 'do' command).  However, Stata prior to Stata 12
has previously taken a simple DO file parameter as a file to be executed
with 'do'; Stata 12 appears to be trying to 'doedit' it instead.

Can anyone shed any light on the above?

I have a number of staff around the department who may well be using the
"-b" form rather than "-b do" who will be
nagging me soon, so if there's a way to change the Stata execution mode
from 'doedit' back to 'do', that would be great!



Dave Ewart
Computing Manager, Cancer Epidemiology Unit
University of Oxford / Cancer Research UK
N 51.7516, W 1.2152
*   For searches and help try:

© Copyright 1996–2018 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   Site index