| Title: | DOCUMENT T1.0 |
| Notice: | **New notesfile (DOCUMENT.NOTE) now available (see note 897)** |
| Moderator: | CLOSET::ADLER |
| Created: | Mon Feb 09 1987 |
| Last Modified: | Thu Oct 31 1991 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 897 |
| Total number of notes: | 4397 |
We run all our DOCUMENT in batch here and it is a constant source
of frustration trying to find out what is queued for a particular
user.
Would it be possible to have the batch job name default to the source
filename ? With the username automatically added on a submit, this
would give us an 'at-a-glance' check of exactly what is queued for
whom.
Currently we have a command procedure that does this for us, but
I don't like this solution and it is definately slower.
Nigel
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 119.1 | See Topic #18 | VAXUUM::DYER | Adventures in Success | Tue Mar 17 1987 09:58 | 0 |
| 119.2 | it bears repeating | CLOSET::ANKLAM | Tue Mar 17 1987 18:08 | 10 | |
#18 discusses workarounds, etc. I prefer a simple DOCU/BATCH=LOG:name
(where SUBMIT is defined in my LOGIN.COM to be SUBMIT/KEEP). This
sends all the LOG files to my top level directory.
In the next version, the LOG will have the same name as the input
file.
patti
| |||||
| 119.3 | I'd like SUBMIT/NAME=filename | CASEE::CLARK | Ward Clark | Tue Jul 14 1987 12:56 | 11 |
.2> In the next version, the LOG will have the same name as the input
.2> file.
I assume (from the date on the note) that "next version" is T1.0-008.
Indeed, the jobname did change from DOC$longstringofnumbers (BL7) to
DOC$filename (BL8).
What is the purpose of the "DOC$" prefix? After all, SUBMIT doesn't
name its batch job SUBMIT$filename.
-- Ward
| |||||