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

Conference iosg::all-in-1

Title:ALL-IN-1 (tm) Support Conference
Notice:Please spell ALL-IN-1 correctly - all CAPITALS!
Moderator:IOSG::PYECE
Created:Fri Jul 01 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2716
Total number of notes:12169

2598.0. "House keeping job re-submit when reboot" by HGOVC::CHIKAICHEUNG () Wed Apr 02 1997 12:22

    Our customer encounter a problem that whenever they reboot the system,
    all the housekeeping job resubmit again, even though there is already
    one entry exist. Their system is running VMS V5.5-2 and ALL-IN-1 V3.0A.
    They checked that there was no multiple spaces in the name of the job
    and I also asked them to change their original long names to a much
    shorter one which are around 10 characters long. 
    
    Their systems are clustered and sys$batch are logical names pointing to 
    their specific per system batch queue. Could anyone give me some more
    hints to fix this problem?
    
    thanks in advance,
    ck
T.RTitleUserPersonal
Name		DateLines
2598.1V3.0A - what's that?IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeWed Apr 02 1997 18:357
    I have a vague recollection that there was some problem in the script
    that A1V30START runs to resubmit all the jobs, but V3.0 is a LONG time
    ago and not supported. You might look at the later versions of this
    script in V3.1 or V3.2 and see if there are any differences.
    
    I think it's called SM$BATCH$CLEANUP.SCP. In V3.2 it's in saveset
    A1LUS032.D.
2598.2SNOFS1::JOYCEJENNYStill crazy after all these yearsThu Apr 03 1997 04:4210
    I vaguely remember having this problem myself on v3.0a, but I think
    that came down to long names for the housekeeping jobs forcing the
    entry as seen in a show queue to go over 2 lines.  Have a good look for
    this sort of problem, and also make sure the names of the jobs as they
    sit on the queue are the same as in the list produced by MHP.
    
    Of course, as Graham says, V3.0A is very old and no longer
    supported....
    
    Jenny Joyce
2598.3HGOVC::CHIKAICHEUNGThu Apr 03 1997 13:0714
    re: .1 I compared a v3.2 version with a v3.0 version of
    SM$BATCH$CLEANUP.SCP, but they are exactly the same.
    
    re: .2 I'd already check thru' the notes conference and found out that
    long schedule name may cause problem, so I'd already asked them to
    shorten the name to 10 characters long as I said in .0 and I checked
    that the names are the same both in the queue and in ALL-IN-1.
    
    Are there anymore hints for me to check since I don't know much about
    ALL-IN-1?
    
    regards,
    ck
2598.4wagAIMTEC::ZANIEWSKI_DTaking bids on Andrew's Alphatraz cellThu Apr 03 1997 18:133
        Make sure you have only one queue manager for the entire cluster. 
        
        Dave Zaniewski
2598.5Check the SYS$BATCH logicalCOPCLU::ELINElin Christensen @DMO, DTN 857-2406Fri Apr 04 1997 19:597
    >... sys$batch are logical names pointing to 
    >their specific per system batch queue. 
    
    I think there are some TIMA STARS articles about problems that can
    occur with housekeeping when SYS$BATCH is a logical name.
    
    Elin
2598.6HGOVC::CHIKAICHEUNGMon Apr 07 1997 07:3810
    re: .4 Only one queue manager is running at all time.
    
    The problem is workarounded by not using sys$batch logical name and use
    real execution queue instead. I checked previous notes and logical
    queue name should be ok but I don't know why it didn't. After all,
    thanks for all your help.
    
    regards,
    ck