Re: DB Recovery after Abnormal outage

That's what we have for our main server too. What happens if the recovery
take longer than that?

Wes

<rob@xxxxxxxxx> wrote in message
news:OF04EDC9FD.6A418E2C-ON05256F46.0079BA3C-05256F46.0079CB6C@xxxxxxxxxx
> On our machines, CHGRCYAP is set to 150.  I wonder how that number was
> picked?
>
> Rob Berendt
> -- 
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> CWilt@xxxxxxxxxxxx
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 11/08/2004 04:58 PM
> Please respond to
> Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
>
>
> To
> midrange-l@xxxxxxxxxxxx
> cc
>
> Fax to
>
> Subject
> RE: DB Recovery after Abnormal outage
>
>
>
>
>
>
> System Managed Access Path Protection (SMAPP)
>
> basically, the system will automatically journal selected access paths so
> that your recovery time is within a specified limit if the system ends
> abnormally.
>
> DSPRCYAP
> CHGRCYAP
> EDTRCYAP
>
>
> HTH,
>
> Charles Wilt
> iSeries Systems Administrator / Developer
> Mitsubishi Electric Automotive America
> ph: 513-573-4343
> fax: 513-398-1121
>
>
> > -----Original Message-----
> > From: ron_adams@xxxxxxxxxxxxxx
[mailto:ron_adams@xxxxxxxxxxxxxx]
> > Sent: Monday, November 08, 2004 4:46 PM
> > To: Midrange Systems Technical Discussion
> > Subject: Re: DB Recovery after Abnormal outage
> >
> >
> > SMAPP?  That's a new one for me.
> >
> > How do we know if it's on, and how do we control it?
> >
> > We've come a LOOOOONG way since S/38 days.
> >
> >
> > Thanks,
> >
> > Ron Adams
> > Information Technology Group
> > Crane Valves
> > 9200 New Trails Dr. Suite 200
> > The Woodlands, TX 77385
> >
> >
> >
> >
> >
> > Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx>
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > 11/08/2004 03:36 PM
> > Please respond to Midrange Systems Technical Discussion
> >
> >
> >         To:     Midrange Systems Technical Discussion
> > <midrange-l@xxxxxxxxxxxx>
> >         cc:
> >         Fax to:
> >         Subject:        Re: DB Recovery after Abnormal outage
> >
> >
> >
> > Do you have SMAPP turned on?  The default is yes.
> >
> > Shipped recovery time limits are:
> >
> > V4R5  90 minutes
> > V5R1  90
> > V5R2  70
> > V5R3  60
> >
> > If you have it turned off, you need to find and maim whoever
> > turned it
> > off.
> >
> > On a System/38, I had a system that took 15 days!
> >
> > DSPRCYAP is the command that will tell you where you are at.
> >
> > Al
> >
> > Al Barsa, Jr.
> > Barsa Consulting Group, LLC
> >
> > 400>390
> >
> > "i" comes before "p", "x" and "z"
> > e gads
> >
> > Our system's had more names than Elizabeth Taylor!
> >
> > 914-251-1234
> > 914-251-9406 fax
> >
> > http://www.barsaconsulting.com
> > http://www.taatool.com
> > http://www.as400connection.com
> >
> >
> >
> >
> >              "Wes"
> >              <small_du@xxxxxxx
> >              om>
> >           To
> >
> >              Sent by:
midrange-l@xxxxxxxxxxxx
> >              midrange-l-bounce
> >           cc
> >
> >              s@xxxxxxxxxxxx
> >
> >      Subject
> >
> >                                        DB Recovery after
> > Abnormal outage
> >              11/08/2004 04:15
> >              PM
> >
> >
> >              Please respond to
> >              Midrange Systems
> >                  Technical
> >                 Discussion
> >              <midrange-l@midra
> >                  nge.com>
> >
> >
> >
> >
> >
> >
> > One of our AS/400 (2way, 820, 900 gid, 8gig mem) went down
> > due to a power
> > supply hardware failure. IBM has replaced the part and
> > performed an IPL.
> > It's been 4hrs since then, and the system is still performing
> > index path
> > recovery. Is there anyway to expedite this process. We have
> > one file about
> > 100Gig, we don't care if the logical files are corrupted or not.
> >
> > Thanks, Wes
> >
> >
> >
> >
> > --
> > This is the Midrange Systems Technical Discussion
> > (MIDRANGE-L) mailing
> > list
> > To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
> >
> > --
> > This is the Midrange Systems Technical Discussion
> > (MIDRANGE-L) mailing
> > list
> > To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
> >
> > --
> > This is the Midrange Systems Technical Discussion
> > (MIDRANGE-L) mailing list
> > To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>