Requirements for users of MIDAS

1. All users working with MIDAS need a rather high page file quota in the authorization file (e.g. 30000) due to the use of the mapping mechanism of MIDAS.

2. Also users of MIDAS should have at least a CPU limit time of 30 minutes.

3. Finally, they need a BYTLIM of 16384 (however, we already had cases where even 16384 was not sufficient and lead to problems when trying to create the foreground subprocess, so it may be set even higher).

4. The following symbol definitions are needed by users to run MIDAS:

   $ SETMIDAS :== @ MID_DISK:['MIDASHOME'.95NOV .MONIT]SETMIDAS.COM
   $ INMIDAS :== @ MID_DISK:['MIDASHOME'.95NOV .MONIT]START.COM

   With INMIDAS you start each session of MIDAS. With SETMIDAS you once set up the symbol MIDOPTION and the logical name MID_WORK which are used in each subsequent INMIDAS.

   • MIDOPTION: may be PARALLEL or NOPARALLEL (the default).

     If MIDOPTION is set to NOPARALLEL, all intermediate MIDAS working files in the MIDAS startup directory are deleted when starting MIDAS via INMIDAS.

     If MIDOPTION is set to PARALLEL, no intermediate files are deleted. So, the PARALLEL option is necessary if you want to run several sessions of MIDAS simultaneously.

   • MID_WORK: specifies the MIDAS startup directory. MIDAS creates all temporary files like FORGRxy.KEY in this directory. Additionally, all the personal procedures may be stored in MID_WORK, in particular the LOGIN.PRG file. It does not matter where you are when you start MIDAS via INMIDAS, the intermediate files will be stored in MID_WORK and the LOGIN.PRG will be searched for in MID_WORK. Furthermore, when executing a "private" MIDAS procedure it may reside in the current default directory or in MID_WORK.
   It may be convenient to put these two definitions into the system LOGIN.COM file - see your system manager for help.