15 Sep
2015
15 Sep
'15
6:25 p.m.
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?
15 Sep
15 Sep
6:32 p.m.
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
7:09 p.m.
The job fails I think because it cannot find the saveset. The logfile woul?d tell you
exactly what went wrong. You'll find the logfile in the default directory of the
usercode that submitted the logfile.
A $JOB card is not required, a valid COM file is enough.
? Origineel bericht ?
Van: Johnny Billquist
Verzonden: dinsdag 15 september 2015 18:33
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Weird SUBMIT error
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
7:50 p.m.
That fixed it, thanks.
sampsa
On 15 Sep 2015, at 18:09, Hans Vlems <hvlems at zonnet.nl> wrote:
The job fails I think because it cannot find the
saveset. The logfile woul?d tell you exactly what went wrong. You'll find the logfile
in the default directory of the usercode that submitted the logfile.
A $JOB card is not required, a valid COM file is enough.
Origineel bericht
Van: Johnny Billquist
Verzonden: dinsdag 15 september 2015 18:33
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Weird SUBMIT error
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
7:55 p.m.
To clarify, I specified the full path to the saveset in the batch job:
$backup/list DQB0:[RHEBCK]RHESYS-2013-12-18.BCK/save
On 15 Sep 2015, at 18:50, Sampsa Laine <sampsa at mac.com> wrote:
That fixed it, thanks.
sampsa
On 15 Sep 2015, at 18:09, Hans Vlems <hvlems at zonnet.nl> wrote:
The job fails I think because it cannot find the
saveset. The logfile woul?d tell you exactly what went wrong. You'll find the logfile
in the default directory of the usercode that submitted the logfile.
A $JOB card is not required, a valid COM file is enough.
Origineel bericht
Van: Johnny Billquist
Verzonden: dinsdag 15 september 2015 18:33
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Weird SUBMIT error
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
8:24 p.m.
On 2015-09-15 19:55, Sampsa Laine wrote:
To clarify, I specified the full path to the saveset
in the batch job:
$backup/list DQB0:[RHEBCK]RHESYS-2013-12-18.BCK/save
Oh. Was this a silly mistake of the saveset not being in your home
directory, and running the com file while in the right directory it
worked...?
Batch jobs start with a default directory of your home directory, just
like when you log in interactively.
Johnny
On 15 Sep 2015, at 18:50, Sampsa Laine <sampsa at mac.com> wrote:
That fixed it, thanks.
sampsa
On 15 Sep 2015, at 18:09, Hans Vlems <hvlems at zonnet.nl> wrote:
The job fails I think because it cannot find the
saveset. The logfile woul?d tell you exactly what went wrong. You'll find the logfile
in the default directory of the usercode that submitted the logfile.
A $JOB card is not required, a valid COM file is enough.
Origineel bericht
Van: Johnny Billquist
Verzonden: dinsdag 15 september 2015 18:33
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Weird SUBMIT error
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
8:25 p.m.
On 15 Sep 2015, at 19:24, Johnny Billquist <bqt at softjar.se> wrote:
Oh. Was this a silly mistake of the saveset not being
in your home directory, and running the com file while in the right directory it
worked...?
Batch jobs start with a default directory of your home directory, just like when you log
in interactively.
Effectively, yes. I haven't used SUBMIT much, so I learnt lots of new stuff from
this.
sampsa
7:53 p.m.
RHELIST.TXT is where the output of the batch job should go.
And no, batch jobs don't have to start with $JOB, any .COM file can theoretically be
submitted to a queue.
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
8:23 p.m.
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
8:24 p.m.
See I learned another thing - if you don't specify the full path to the log file, it
goes into SYS$LOGIN:
So as I had no log file (or so I thought) I was a tad confused as to what was going on.
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
8:28 p.m.
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
8:28 p.m.
On Sep 15, 2015, at 2:23 PM, Johnny Billquist <bqt
at softjar.se> wrote:
On 2015-09-15 19:53, Sampsa Laine wrote:
Or RSTS/E people... where it's even neater because you can do stuff like "give me
a log file" interactively -- it was created for the benefit of batch but it is part
of the kernel machinery for talking to a process ("job"), so it isn't only
batch.
paul
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... :-)
8:32 p.m.
On 2015-09-15 20:28, Paul_Koning at Dell.com wrote:
Well, my comment was specifically about the non-need for a $JOB. In RSX,
batch will be very unimpressed if you skip the $JOB.
But now you got me a bit curious. So you can essentially ask for a log
file of whatever terminal that is doing something, at any point in time?
Johnny
On Sep 15, 2015, at 2:23 PM, Johnny Billquist
<bqt at softjar.se> wrote:
On 2015-09-15 19:53, Sampsa Laine wrote:
Or RSTS/E people... where it's even neater because you can do stuff like "give
me a log file" interactively -- it was created for the benefit of batch but it is
part of the kernel machinery for talking to a process ("job"), so it isn't
only batch. 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... :-)
8:50 p.m.
On Sep 15, 2015, at 2:32 PM, Johnny Billquist <bqt
at softjar.se> wrote:
On 2015-09-15 20:28, Paul_Koning at Dell.com wrote:
Yes:
$ open/logfile/time foo.log
$.sys/s
RSTS P10.1-L RSTS/E V10.1 status at 15-Sep-15, 02:46 PM Up: 1:08
Job Who Where What Size State Run-Time Pri/RB RTS
1 1,211 KB0 SYSTAT 17/32K RN Lck 0.0 -8/6 ...RSX
2 1,2 Det PBS... 19/32K SL 0.0 -8/6 ...RSX
3 1,2 Det EVTLOG 18/32K SL 0.0 -8/6 ...RSX
$.close/log
$ type foo.log
15-Sep-15 02:46:03 PM $.sys/s
15-Sep-15 02:46:08 PM RSTS P10.1-L RSTS/E V10.1 status at 15-Sep-15, 02:46 PM Up
: 1:08
15-Sep-15 02:46:08 PM Job Who Where What Size State Run-Time Pri/RB
RTS
15-Sep-15 02:46:08 PM 1 1,211 KB0 SYSTAT 17/32K RN Lck 0.0 -8/6
...RSX
15-Sep-15 02:46:08 PM 2 1,2 Det PBS... 19/32K SL 0.0 -8/6
...RSX
15-Sep-15 02:46:08 PM 3 1,2 Det EVTLOG 18/32K SL 0.0 -8/6
...RSX
15-Sep-15 02:46:08 PM $.close/log
The way this works is that the log file (and current command file level) are owned and
handled by the kernel. The indirect command processor just opens the files and hands them
to the kernel. If a command file is open, the kernel directs terminal reads to that file.
If a log file is open, it sends terminal output to the log. Also, if requested, it
prefixes a timestamp. These are called "permanent files" because they
aren't closed at program exit the way regular file descriptors are.
So most of the work of batch jobs (and command files) is in the kernel. That's about
the only way to make it transparent, since RSTS doesn't have supervisor mode in which
to hide DCL concurrent with the running process, as VMS does.
paul
...
Or RSTS/E people... where it's even neater because you can do stuff like "give
me a log file" interactively -- it was created for the benefit of batch but it is
part of the kernel machinery for talking to a process ("job"), so it isn't
only batch.
Well, my comment was specifically about the non-need for a $JOB. In RSX, batch will be
very unimpressed if you skip the $JOB.
But now you got me a bit curious. So you can essentially ask for a log file of whatever
terminal that is doing something, at any point in time?
8:58 p.m.
On 2015-09-15 20:50, Paul_Koning at Dell.com wrote:
Really nice. But was this something new in V9 or so then? I pretty much
stopped using RSTS/E at V8, and I can't remember anything like this.
The way to accomplish this in RSX would essentially be to run all your
commands in a virtual terminal, and output the results both to the
terminal and a logfile. However, there are some subtly differences that
happens if done that way. So I can't say that you really can accomplish
this in RSX.
Johnny
On Sep 15, 2015, at 2:32 PM, Johnny Billquist
<bqt at softjar.se> wrote:
On 2015-09-15 20:28, Paul_Koning at Dell.com wrote:
Yes:
$ open/logfile/time foo.log
$.sys/s
RSTS P10.1-L RSTS/E V10.1 status at 15-Sep-15, 02:46 PM Up: 1:08
Job Who Where What Size State Run-Time Pri/RB RTS
1 1,211 KB0 SYSTAT 17/32K RN Lck 0.0 -8/6 ...RSX
2 1,2 Det PBS... 19/32K SL 0.0 -8/6 ...RSX
3 1,2 Det EVTLOG 18/32K SL 0.0 -8/6 ...RSX
$.close/log
$ type foo.log
15-Sep-15 02:46:03 PM $.sys/s
15-Sep-15 02:46:08 PM RSTS P10.1-L RSTS/E V10.1 status at 15-Sep-15, 02:46 PM Up
: 1:08
15-Sep-15 02:46:08 PM Job Who Where What Size State Run-Time Pri/RB
RTS
15-Sep-15 02:46:08 PM 1 1,211 KB0 SYSTAT 17/32K RN Lck 0.0 -8/6
...RSX
15-Sep-15 02:46:08 PM 2 1,2 Det PBS... 19/32K SL 0.0 -8/6
...RSX
15-Sep-15 02:46:08 PM 3 1,2 Det EVTLOG 18/32K SL 0.0 -8/6
...RSX
15-Sep-15 02:46:08 PM $.close/log
The way this works is that the log file (and current command file level) are owned and
handled by the kernel. The indirect command processor just opens the files and hands them
to the kernel. If a command file is open, the kernel directs terminal reads to that file.
If a log file is open, it sends terminal output to the log. Also, if requested, it
prefixes a timestamp. These are called "permanent files" because they
aren't closed at program exit the way regular file descriptors are.
So most of the work of batch jobs (and command files) is in the kernel. That's about
the only way to make it transparent, since RSTS doesn't have supervisor mode in which
to hide DCL concurrent with the running process, as VMS does. ...
Or RSTS/E people... where it's even neater because you can do stuff like "give
me a log file" interactively -- it was created for the benefit of batch but it is
part of the kernel machinery for talking to a process ("job"), so it isn't
only batch.
Well, my comment was specifically about the non-need for a $JOB. In RSX, batch will be
very unimpressed if you skip the $JOB.
But now you got me a bit curious. So you can essentially ask for a log file of whatever
terminal that is doing something, at any point in time?
9:20 p.m.
Oh you do need a $JOB card as the first card in a deck submitted through a cardreader. It
identifies the username and the subsequent $PASSWORD card completes the user's
credentials.
When an interactive user submits a job the username is known. Different credentials may be
used as well.
? Origineel bericht ?
Van: Johnny Billquist
Verzonden: dinsdag 15 september 2015 20:58
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Weird SUBMIT error
On 2015-09-15 20:50, Paul_Koning at Dell.com wrote:
Really nice. But was this something new in V9 or so then? I pretty much
stopped using RSTS/E at V8, and I can't remember anything like this.
The way to accomplish this in RSX would essentially be to run all your
commands in a virtual terminal, and output the results both to the
terminal and a logfile. However, there are some subtly differences that
happens if done that way. So I can't say that you really can accomplish
this in RSX.
Johnny
On Sep 15, 2015, at 2:32 PM, Johnny Billquist
<bqt at softjar.se> wrote:
On 2015-09-15 20:28, Paul_Koning at Dell.com wrote:
Yes:
$ open/logfile/time foo.log
$.sys/s
RSTS P10.1-L RSTS/E V10.1 status at 15-Sep-15, 02:46 PM Up: 1:08
Job Who Where What Size State Run-Time Pri/RB RTS
1 1,211 KB0 SYSTAT 17/32K RN Lck 0.0 -8/6 ...RSX
2 1,2 Det PBS... 19/32K SL 0.0 -8/6 ...RSX
3 1,2 Det EVTLOG 18/32K SL 0.0 -8/6 ...RSX
$.close/log
$ type foo.log
15-Sep-15 02:46:03 PM $.sys/s
15-Sep-15 02:46:08 PM RSTS P10.1-L RSTS/E V10.1 status at 15-Sep-15, 02:46 PM Up
: 1:08
15-Sep-15 02:46:08 PM Job Who Where What Size State Run-Time Pri/RB RTS
15-Sep-15 02:46:08 PM 1 1,211 KB0 SYSTAT 17/32K RN Lck 0.0 -8/6 ...RSX
15-Sep-15 02:46:08 PM 2 1,2 Det PBS... 19/32K SL 0.0 -8/6 ...RSX
15-Sep-15 02:46:08 PM 3 1,2 Det EVTLOG 18/32K SL 0.0 -8/6 ...RSX
15-Sep-15 02:46:08 PM $.close/log
The way this works is that the log file (and current command file level) are owned and
handled by the kernel. The indirect command processor just opens the files and hands them
to the kernel. If a command file is open, the kernel directs terminal reads to that file.
If a log file is open, it sends terminal output to the log. Also, if requested, it
prefixes a timestamp. These are called "permanent files" because they aren't
closed at program exit the way regular file descriptors are.
So most of the work of batch jobs (and command files) is in the kernel. That's about
the only way to make it transparent, since RSTS doesn't have supervisor mode in which
to hide DCL concurrent with the running process, as VMS does. ...
Or RSTS/E people... where it's even neater because you can do stuff like "give
me a log file" interactively -- it was created for the benefit of batch but it is
part of the kernel machinery for talking to a process ("job"), so it isn't
only batch.
Well, my comment was specifically about the non-need for a $JOB. In RSX, batch will be
very unimpressed if you skip the $JOB.
But now you got me a bit curious. So you can essentially ask for a log file of whatever
terminal that is doing something, at any point in time?
10:07 p.m.
On Sep 15, 2015, at 2:58 PM, Johnny Billquist <bqt
at softjar.se> wrote:
On 2015-09-15 20:50, Paul_Koning at Dell.com wrote:
Really nice. But was this something new in V9 or so then? I pretty much stopped using
RSTS/E at V8, and I can't remember anything like this.
Yes, I added that in V9.0.
On Sep 15, 2015, at 2:32 PM, Johnny Billquist
<bqt at softjar.se> wrote:
On 2015-09-15 20:28, Paul_Koning at Dell.com wrote:
Yes:
$ open/logfile/time foo.log...
The way this works is that the log file (and current command file level) are owned and
handled by the kernel. The indirect command processor just opens the files and hands them
to the kernel. If a command file is open, the kernel directs terminal reads to that file.
If a log file is open, it sends terminal output to the log. Also, if requested, it
prefixes a timestamp. These are called "permanent files" because they
aren't closed at program exit the way regular file descriptors are.
So most of the work of batch jobs (and command files) is in the kernel. That's about
the only way to make it transparent, since RSTS doesn't have supervisor mode in which
to hide DCL concurrent with the running process, as VMS does. ...
Or RSTS/E people... where it's even neater because you can do stuff like "give
me a log file" interactively -- it was created for the benefit of batch but it is
part of the kernel machinery for talking to a process ("job"), so it isn't
only batch.
Well, my comment was specifically about the non-need for a $JOB. In RSX, batch will be
very unimpressed if you skip the $JOB.
But now you got me a bit curious. So you can essentially ask for a log file of whatever
terminal that is doing something, at any point in time?
The way to accomplish this in RSX would essentially be to run all your commands in a
virtual terminal, and output the results both to the terminal and a logfile. However,
there are some subtly differences that happens if done that way. So I can't say that
you really can accomplish this in RSX.
RSTS used to do it that way. The trouble is that we really wanted to be able to do stuff
based on "exit status". And in RSTS that wasn't always well defined. Yes
for RSX based programs, but not for others. So we did this by watching the output for
error messages. Also, the virtual terminal based approach means you need two job slots:
one for the controller, and one for the controlled. With job slots often being in short
supply, that wasn't desirable. The question became "can the kernel do this so we
don't end up using scarce system resources" and the answer turned out to be yes.
paul
16 Sep
16 Sep
10:47 a.m.
New subject: MONITOR DISK - Meaning of values
I'm running a batch job that is creating a large (82 GB) file and monitoring the
system with MONITOR DISK.
The value I'm getting is 39 - what does this actually mean, what is the unit that is
being monitored?
10:52 a.m.
New subject: MONITOR DISK - Meaning of values
Found the answer - it's disk operations/second.
Is there any way to see how much in bytes/blocks etc is being written to a disk?
sampsa
On 16 Sep 2015, at 09:47, Sampsa Laine <sampsa at mac.com> wrote:
I'm running a batch job that is creating a large
(82 GB) file and monitoring the system with MONITOR DISK.
The value I'm getting is 39 - what does this actually mean, what is the unit that is
being monitored?
11:03 a.m.
New subject: MONITOR DISK - Meaning of values
The only way I know to obtain transfer rates is to run backup and hit ^T... :(
? Origineel bericht ?
Van: Sampsa Laine
Verzonden: woensdag 16 september 2015 10:53
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] MONITOR DISK - Meaning of values
Found the answer - it's disk operations/second.
Is there any way to see how much in bytes/blocks etc is being written to a disk?
sampsa
On 16 Sep 2015, at 09:47, Sampsa Laine <sampsa at mac.com> wrote:
I'm running a batch job that is creating a large
(82 GB) file and monitoring the system with MONITOR DISK.
The value I'm getting is 39 - what does this actually mean, what is the unit that is
being monitored?
11:06 a.m.
New subject: MONITOR DISK - Meaning of values
OK, so I didn't miss anything in the dozen or so HELP pages I read :)
sampsa
On 16 Sep 2015, at 10:03, Hans Vlems <hvlems at zonnet.nl> wrote:
The only way I know to obtain transfer rates is to run
backup and hit ^T... :(
Origineel bericht
Van: Sampsa Laine
Verzonden: woensdag 16 september 2015 10:53
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] MONITOR DISK - Meaning of values
Found the answer - it's disk operations/second.
Is there any way to see how much in bytes/blocks etc is being written to a disk?
sampsa
On 16 Sep 2015, at 09:47, Sampsa Laine <sampsa at mac.com> wrote:
I'm running a batch job that is creating a
large (82 GB) file and monitoring the system with MONITOR DISK.
The value I'm getting is 39 - what does this actually mean, what is the unit that is
being monitored?
11:35 a.m.
New subject: MONITOR DISK - Meaning of values
You'll agree that HELP contains tons of interesting information. To the point of
distracting you from your original problem :-)
? Origineel bericht ?
Van: Sampsa Laine
Verzonden: woensdag 16 september 2015 11:06
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] MONITOR DISK - Meaning of values
OK, so I didn't miss anything in the dozen or so HELP pages I read :)
sampsa
On 16 Sep 2015, at 10:03, Hans Vlems <hvlems at zonnet.nl> wrote:
The only way I know to obtain transfer rates is to run
backup and hit ^T... :(
Origineel bericht
Van: Sampsa Laine
Verzonden: woensdag 16 september 2015 10:53
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] MONITOR DISK - Meaning of values
Found the answer - it's disk operations/second.
Is there any way to see how much in bytes/blocks etc is being written to a disk?
sampsa
On 16 Sep 2015, at 09:47, Sampsa Laine <sampsa at mac.com> wrote:
I'm running a batch job that is creating a
large (82 GB) file and monitoring the system with MONITOR DISK.
The value I'm getting is 39 - what does this actually mean, what is the unit that is
being monitored?
3168
days inactive
3169
days old
21 comments
4 participants
participants (4)
-
bqt＠softjar.se -
hvlems＠zonnet.nl -
Paul_Koning＠Dell.com -
sampsa＠mac.com