| 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 |
We have a customer running V2.4 who is unable to edit/delete some of his jobs in housekeeping. The queue_job.com procedure exits with a missing param DCL error. Using set ver we see that the entry_number is empty. Using the SM_GENERIC_UTILITY_SCHEDULE form we see that indeed the entry_number is empty. What could be causing this? Thanks, Cb.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1103.1 | Perhaps when rescheduling... | TAV02::CHAIM | Semper ubi Sub ubi ..... | Sun Jul 26 1992 07:40 | 9 |
The customer has checked, and any newly created procedures do receive an entry_number. Perhaps this is happening when the procedure reschedules itself. The customer will update me. In the meantime, I'd appreciate input from anyone who has any idea. Thanks, Cb. | |||||
| 1103.2 | After reboot, entry numbers gone ... | TAV02::CHAIM | Semper ubi Sub ubi ..... | Tue Jul 28 1992 13:24 | 26 |
The customer just reported that it happened again AFTER his machine was rebooted yesterday. All the jobs that were in MHP before the reboot are now missing entry numbers. Any jobs submitted or automatically rescheduled after the reboot have entry numbers. Out of curiosity, I had the customer do a dir/date on the oa$sm_util_schedule.dat file and it was created on July 25th. The customer verified that on July 25th the RSF (Reorganize System Files) was run. This does indeed reorganize the oa$sm_util_schedule.dat file, and I thought that here might lie the problem. However, I ran this procedure on my test system (running same version as the customer) and the entry numbers for my jobs did not disapper. Besides, looking in the procedure, it appears that the procedure basically does a convert/fdl which would not affect any of the actual data in the file. Are there any procedures which do any type of manipulation to this file that could inadvertantly cause the entry numbers to be blown away. Does anyone see how the rebooting of the machine (and of course having ALL-IN-1 restarted) could be connected? Thanks, Cb. | |||||
| 1103.3 | QUEUE not defined on all nodes... | TAV02::CHAIM | Semper ubi Sub ubi ..... | Thu Jul 30 1992 10:12 | 15 |
I have some more input which may be relavent: The customer runs ALL-IN-1 on a four node cluster with each node maintaining its own JBCSYSQUE.DAT file. The queue upon which the MHP jobs run is defined and exists on ONLY one of these nodes. The customer always receives errors when ALL-IN-1 starts up on any of the nodes which do not have this queue defined at the point where the startup attempts to reschedule any housekeeping procedures. Could this be causing the loss of the entry numbers? Thanks, Cb. | |||||