[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

1293.0. "A1 startup in batch causes MHP to abort" by TAV02::CHAIM (Semper ubi Sub ubi .....) Sun Aug 23 1992 09:13

A customer running V2.4 has complained that his housekeeping procedures which
had been scheduled to run over the weekend did not resubmit themselves.

At the time that these procedures were scheduled to run the computer was down.
We took a look at any log files, and these showed that the procedures did start
running as soon as the computer came up, but they immediately aborted because
OA$IMAGE couldn't be found. It turns out that in order to save time during
reboot, the system manager has most of his layered products, including
ALL-IN-1, startup in batch. Hence, the housekeeping procedures appear to have
begun before ALL-IN-1 actually was started up.

I explained what happened to the system manager, and although he accepted my
explanation, he did express some surprise that the command procedures were not
quite "smart" enough to overcome this problem and resubmit themselves.

Will this possible scenario be addressed in any future version.

Thanks,

Cb.

T.RTitleUserPersonal
Name
DateLines
1293.1Architectural RestrictionSCOTTC::MARSHALLPearl-white, but slightly shop-soiledTue Aug 25 1992 11:3311
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.2OAMTISEND.COM does it...UTRTSC::SCHOLLAERTVivaceObjectTeamWorkLinks for IOSTue Aug 25 1992 12:0822
    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.3Infinite loopSCOTTC::MARSHALLPearl-white, but slightly shop-soiledTue Aug 25 1992 17:4911
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