T.R | Title | User | Personal Name | Date | Lines |
---|
1293.1 | Architectural Restriction | SCOTTC::MARSHALL | Pearl-white, but slightly shop-soiled | Tue Aug 25 1992 11:33 | 11 |
| Hi,
>> he did express some surprise that the command procedures were not
>> quite "smart" enough to overcome this problem and resubmit themselves
In order to re-submit themselves, the command procedures need to use ALL-IN-1,
to write the housekeeping schedule record. So it's nothing to do with them
being "smart", it's just a consequence of the chosen implementation: if ALL-IN-1
isn't available, the housekeeping jobs can't do *anything*.
Scott
|
1293.2 | OAMTISEND.COM does it... | UTRTSC::SCHOLLAERT | VivaceObjectTeamWorkLinks for IOS | Tue Aug 25 1992 12:08 | 22 |
| Scott,
What about starting SMJACKET.COM with .....
$Wait_loop:
$ !
$ ShutDown = "''F$LOGICAL("OA$IMAGE")'"
$ !
$ ! Wait if system not started yet
$ !
$ IF ShutDown .NES. "" THEN GOTO System_up
$ !
$ Wait 0:5:0 ! Wait for 5 minutes
$ !
$ GOTO Wait_loop ! and try again
$ !
$System_up:
$ !
Regards,
Jan
|
1293.3 | Infinite loop | SCOTTC::MARSHALL | Pearl-white, but slightly shop-soiled | Tue Aug 25 1992 17:49 | 11 |
| Hi,
The problem with .2 is that it assumes ALL-IN-1 is eventually going to start.
If there is a problem which prevents ALL-IN-1 starting, or it is intentionally
shut down, then the job(s) just sit there looping for ever.
However, I agree there are several reasonably simple ways the current behaviour
could be improved; my original reply was just something that could be used as
the basis for an official reply to the customer.
Scott
|