RE: IBM On-Demand -- MIDRANGE-L

We use On-Demand quite a bit, I would like to start using it more.  On thing
we did was to add the monitor start up to a job scheduler to end it
everynight and then re-start it that seemed to clear up any problems with
overloading the monitors or problems storing them.  We also send all the
reports for the stores successful/failed to an output queue that gets
cleared nightly on the job scheduler so that there is not a mess of reports
out there.   I am starting to look into the portion of the On-Demand that
allows the storage of scanned documents.  Hopefully this portion works just
as well!
  

Angie Wawrzaszek
M.I.S. Department


-----Original Message-----
From: Evan Harris [mailto:spanner@ihug.co.nz]
Sent: Thursday, June 29, 2000 2:51 AM
To: MIDRANGE-L@midrange.com
Subject: RE: IBM On-Demand


Bob

>We support a very large installation of OnDemand and have used it
>extensively, averaging archiving about 25,000 reports a day, so I have seen
>most problems.  When a report stops storing and you have verified that the
>report format has not changed and the definition is correct then it could
be
>several issues, first store the report manually using the command
STRCDSRDAR
>and view the joblog for why it failed.  It could be anything from a restart
>indicator flag set to "Y" in the QARLRSRT file, to a STMF file in an IFS
>directory partial stored(a stub), or a user space for that definition is
>pseudo active, etc.  Email me the joblog and maybe I have seen it before.

Wow ! We would be lucky (currently) to be filing 200 reports a day but this 
is growing fast.

The error I saw (repeatedly) was the restart flag being required to save 
the file. Where/when does the flag get set ? Is it set individually for 
each job/report ? It seems that when the monitor jobs starts, it eventually 
falls over because as far as I can tell it does a poor job of cleaning up 
after itself as it goes. It then says it needs a restart flag for each 
subsequent file it tries to process. Restarting the Monitor job seems to 
fix this until the next (inevitable) occurrence.

My experience so far is that stacking up a heap of spool files is almost 
certain to make the job fail after about 20 files, but for some 
inexplicable reason a trickle of spool files seems to work fine. Go figure.

I'll hunt up a job log for the other messages regarding unable to 
complete/find segment failures (can't remember the exact message and I'm at 
home now) and email it to you. Any light you can shed on it would be most 
appreciated.

Thanks again for your help so far

Regards
Evan Harris

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---