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 |
Yes, Andrew I have read previous notes...... Since upgrading to VMS 5.5-2 when rebooting system 5 (PT,RSF, TRM,UA,DA) out of his 7 housekeeping jobs get scheduled twice. EW and ROA do not. This did not happen before upgrading VMS. We checked the known problems with ALL-IN-1 (i.e., hypens, apostrophes, underscores, spaces) and this does not apply to his problem. Customer is running V2.4 fully patched. Any ideas? Jean
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1967.2 | SWAG... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Wed Dec 16 1992 09:39 | 11 |
Does this keep happening? There's some problem areas in the code in A1V30START that reschedules all the jobs. It gets confused about the version numbers of command files or something like that... I don't knowif that was a problem in V2.4 too. Have you tried emptying all the HK jobs off the queues and then using the startup procedure to put them back? Graham | |||||
1967.3 | Found Problem | AIMTEC::GRENIER_J | Thu Dec 17 1992 19:26 | 36 | |
Turned out the customer was running V2.3, non-cluster environment, had patches K501,502,503,505. Problem did start happening after he upgraded from VMS 5.4 to VMS 5.5-2. In VMS V5.4 when doing a show/queue you saw: Jobname Submittor Job # In VMS V5.5 you see: Job # Jobname Submittor Problem only happens when the job name is greater than 15 characters. FIX: Edit OA$LIB:SM$ON$QUEUE.COM Change NEXT_LINE: as follows: $ READ/END=SUBMITAGAIN QUEUE LINE $ IF 'F$LOCATE(P2,LINE) .EQ. 'F$LENGTH(LINE) THEN GOTO NEXT_LINE $ IF 'F$LOCATE(P3,LINE) .EQ. 'F$LENGTH(LINE) THEN GOTO NEXT_LINE $ READ/END=SUBMITAGAIN QUEUE LINE $ IF 'F$LOCATE(P4,LINE) .EQ. 'F$LENGTH(LINE) THEN GOTO NEXT_LINE $ GOTO FOUND_IT This is because the JOB # is now the first entry in the queue for the job and would not be on the second line of the queue entry if the job had a long name. |