| 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 |
I have a problem very similar to the one mentioned in Note 460.
In my case, I am running DOCUMENT from a command file which is
executing from within ALL-IN-1. (Background information: when
ALL-IN-1 needs to execute a DCL command procedure, it does it from
an associated sub-process. This sub-process, because of how it
is created, is *not* marked as an INTERACTIVE process, but as OTHER.)
Now, when my command procedure does a DOCUMENT/BATCH... I do
*not* get the submission to batch, but the processing takes place
immediately. If I execute the same command from a normal DCL process,
everything works fine.
What appears to be happening is that when DOCUMENT sees the
/BATCH qualifier, it looks at the current process's mode. If it
is INTERACTIVE, it does a regular SUBMIT and everything is fine.
If it is OTHER (or maybe even if it is BATCH -- I haven't tried
that yet), it seems to say "What the heck, I may as well just do
it right here and now."
So to expand on Note 460, how can I run DOCUMENT from a process
(in this case, a sub-process) whose mode is OTHER, but still have
the /BATCH qualifier do a full SUBMIT so that the silly thing will
actually get queued up to SYS$BATCH (or wherever)?
Frank
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 759.1 | re: .0 | VAXUUM::PELTZ | �lvynstar Dun�dain | Wed Aug 05 1987 14:19 | 17 |
> What appears to be happening is that when DOCUMENT sees the
> /BATCH qualifier, it looks at the current process's mode. If it
> is INTERACTIVE, it does a regular SUBMIT and everything is fine.
> If it is OTHER (or maybe even if it is BATCH -- I haven't tried
> that yet), it seems to say "What the heck, I may as well just do
> it right here and now."
Yes, you are close, if /BATCH is specified, we look to see
if the processing mode is batch, if not then we run
interactive. This is a by-product of the origional
implementation of /BATCH, which has other problems as well.
All I can say is that this will be rectified in future
versions.
Chris
| |||||