On 2015-09-15 20:24, Sampsa Laine wrote:
See I learned another thing - if you don't specify
the full path to the log file, it goes into SYS$LOGIN:
You need to remember that batch jobs are pretty much totally unrelated
to your current state at the terminal where you submit the batch job from.
Submitting means you put the job in a queue, from which it is later
picked up.
So as I had no log file (or so I thought) I was a tad
confused as to what was going on.
Learning new things is always good.
Johnny
sampsa
On 15 Sep 2015, at 19:23, Johnny Billquist <bqt at softjar.se> wrote:
On 2015-09-15 19:53, Sampsa Laine wrote:
RHELIST.TXT is where the output of the batch job
should go.
Yes. And I would have expected any errors that happened while the batch job was running
would end up in that log file.
And no, batch jobs don't have to start with
$JOB, any .COM file can theoretically be submitted to a queue.
You fancy VMS people... :-)
Johnny
Sampsa
On 15 Sep 2015, at 17:32, Johnny Billquist <bqt at softjar.se> wrote:
On 2015-09-15 18:25, Sampsa Laine wrote:
> I'm trying to submit the following batch file (
RHELIST.COM):
>
> --- SNIP ---
> $! List contents of RHESUS backup
> $backup/list RHESYS-2013-12-18.BCK/save
>
> --- SNIP ---
>
> When I run it using @RHELIST, everything is fine but when I try this:
>
> submit/log=rhelist.txt
rhelist.com
>
> I get the following error:
>
> Job RHELIST (queue SYS$BATCH, entry 159) started on SYS$BATCH
> CHIMPY$
>
> Job RHELIST (queue SYS$BATCH, entry 159) terminated with error status
>
>
> Any ideas?
What is in RHELIST.TXT?
If I were to make a guess, batch files have to start with a $JOB, don't they?
Johnny
_______________________________________________
Hecnet-list mailing list
Hecnet-list at
lists.sonic.net
https://lists.sonic.net/mailman/listinfo/hecnet-list