Maint Scheduling Perf Problems at Cliffs 3

[GlenCYM]

The users from our stream a experiencing unacceptable system slowdowns, particularly on Thursdays. They need to run the MSB700 and other reports for their weekly planning meetings. It appears that some Labor costing MSBnreports are being run along with some other Financial programs at the same time they are trying to run reports/batches necessary for the planning meetings. Mincom has ncountered this at other sites and to resolve this conflict they have seen where a company has developed a policy that all other streams try to restrict the use of the MSB programs on the time of the day ( one day each week) that Maintenance needs to utilize the system for their planning reports/runs. <br>
<br>
I have seen the same problem at a lot of sites and what we found out was the system was not set up properly by MINCOM. The pick slips, scheduling (msb700 and 740), and work order job cards (msr623) should be threaded differently. They should be the only items on this single thread. The MSB700, MSB740 and MSR141 should be able to be run at any time and should be instant.<br>

 

[Glen]

Brian,<br>
<br>
We tend to run our maintenance scheduling as cyclic jobs in the nightly batch stream. Because of the amount of equipment that we run this against, the work is divied up so that particular pieces of equipment run on specific days of the week.<br>
<br>
The request parameters for the MSB700/740 have a significant impact on run times. I think you might want to start by looking at the request parameters and sanity testing them.<br>
<br>
What kind of hardware are you running on? We don't see any negative performance impact on other systems when running maint programs... You may need some system performance tuning.<br>
<br>
Glen

 

[Glen]

Brian,<br>
<br>
We run Maintenance Scheduling in its own stream. When there are a lot of maintenance programs scheduled, they back up on each other, but other modules (pick slips, etc) are not affected. They have their own streams.<br>
<br>
Glen

 

[dpes1]

Hi Brian:<br>
<br>
At Newmont most MSB700 reports are set up to run cyclically each night by work group. We also have different processors streams set up for certain reports. Financials run in their own as do maintenance update reports. See examples in tpnames.tbl.<br>
<br>
<br>
BATCHMR1:MSR1 0-01 $MIMS_EXE -p BATCHMR1 -e ',*' \<br>
1&gt;&gt; $MIMS_LOG/batchmr1.log 2&gt;&1<br>
BATCHMR2:MSR2,MSR9 0-01 $MIMS_EXE -p BATCHMR2 -e ',*' \<br>
1&gt;&gt; $MIMS_LOG/batchmr2.log 2&gt;&1<br>
BATCHMB1:MSB222,MSB2 0-01 $MIMS_EXE -p BATCHMB1 -e ',*' \<br>
1&gt;&gt; $MIMS_LOG/batchmb1.log 2&gt;&1<br>
BATCHMB7:MSB7 0-01 $MIMS_EXE -p BATCHMB7 -e ',*' \<br>
1&gt;&gt; $MIMS_LOG/batchmb7.log 2&gt;&1<br>
BATCHMB:MSB 0-01 $MIMS_EXE -p BATCHMB -e ',*' \<br>
1&gt;&gt; $MIMS_LOG/batchmb.log 2&gt;&1<br>
BATCHNR4:NGR9,NGR4 0-01 $MIMS_EXE -p BATCHNR4 -e ',*' \<br>
1&gt;&gt; $MIMS_LOG/batchnr4.log 2&gt;&1<br>
BATCH621:MSR621 0-02 $MIMS_EXE -p BATCH621 -e ',*' \<br>
1&gt;&gt; $MIMS_LOG/batch621.log 2&gt;&1<br>
BATCH62A:NGR62 0-02 $MIMS_EXE -p BATCH62A -e ',*' \<br>
<br>
<br>

 

[CCIOHIO]

Part of our problem with the setup of MSB online batch initiated reports on our IBM is that they all run