>As an aside, it is quite normal in the UNIX world to start "long >running" work similar to the following: > >nohup unix-command ..params.. <input.data >standard.output.messages >2>error.messages & > >I've not tried this on z/OS to see if it works. And on most current UNIX >systems, the user is sitting on a X server and running multiple xterms, >so they (like a Windows person) just uses another xterm and leaves the >"long running" command going. I also tend to do this, except that I may >use "screen" to put the command into a "virtual terminal" so that I can >disconnect and reconnect it (like you can a VTAM session manager).
Why should that not work? You may start another shell session or xterm to continue to work but that's not necessary, since you're sending the command to the background (this is what the trailing & does). You can continue to work in the current shell session while the background job is executing. Peter Hunkeler CREDIT SUISSE ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
