Re: UPDATE: Corrupted object. HELP!!

Sounds like Lawson needs to produce a fix for the problem. I forced the same
issue with another software vendor last year. The package was creating
members named QPADEVnnnn all over the place for lots of interactive jobs,
and even a bunch of batch jobs in the "new and improved" version of the
software, but never removed them when the user signed off or when the batch
job was finished. When it was brought to his attention, the client made them
remove all the "garbage". They got back over 5% of their DASD.

Paul Nelson
Braxton-Reed, Inc.
630-327-8665 Cell
708-923-7354 Home
pnelson@braxton-reed.com
----- Original Message -----
From: "Wills, Mike N. (TC)" <MNWills@taylorcorp.com>
To: <midrange-l@midrange.com>
Sent: Friday, August 16, 2002 11:00 AM
Subject: UPDATE: Corrupted object. HELP!!


> Well, last night we did a rclstg and it fixed it. I am thinking part of
the
> problem is Lawson creates separate members in the working and sometimes
> doesn't remove them properly. Well, 90 jobs per day everyday for over a
year
> can cause problems. After I deleted them it seems to restoring better. I
> have now scheduled a Lawson's cleanup program to run once a week.
>
> -----Original Message-----
> From: Wills, Mike N. (TC) [mailto:MNWills@taylorcorp.com]
> Sent: Wednesday, August 14, 2002 1:31 PM
> To: 'midrange-l@midrange.com'
> Subject: RE: Corrupted object. HELP!!
>
>
> Last RCLSTG took about 1.5 hours. So that shouldn't be bad.
>
> -----Original Message-----
> From: Steve Landess - Hotmail [mailto:steve_landess@hotmail.com]
> Sent: Tuesday, August 13, 2002 9:27 PM
> To: midrange-l@midrange.com
> Subject: Re: Corrupted object. HELP!!
>
>
> I would try deleting the library again after an IPL.  Sometimes an IPL
will
> fix a damaged object, and it's not necessary to run the RCLSTG.
>
> However, I don't give this a high probability of success, either.  In all
> probability, I think that you will have to run RCLSTG.  Hopefully you
don't
> have a huge amount of aux. stg...it could run for a loooooonnnnnnggggg
time!
>
>
> ----- Original Message -----
> From: "Wills, Mike N. (TC)" <MNWills@taylorcorp.com>
> To: <midrange-l@midrange.com>
> Sent: Tuesday, August 13, 2002 4:48 PM
> Subject: Corrupted object. HELP!!
>
>
> This story is almost funny.
>
> I was restoring the test data today from live. So I take last nights
backup
> to restore. I first delete the old library then restore the new one. Okay,
> well, it shouldn't take 3 hours to restore. I starting digging around and
> discovered a Tape drive failure. Great... so I cancel the job and end and
> restart the tape drive. Now I need to delete the library again. No
> problem... well... it was taking 45 mins to delete about 20 objects (size
I
> am not sure but looked to be work files, they should be small). Hmmm...
> great. So I cancel the job and try again... locks up my workstation. After
a
> bit more digging with a co-worker of mine we discover that it is corrupt.
> Just great... We tried to rename the library, but now
>
> So this is where we are at. We have to IPL to complete the library name
> change and need to reclaim storage to recover the file.
>
> Does anyone know how to take care of the file without doing these things?
>
> Any help will be greatly appreciated!!!
>
> Mike
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> 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@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> 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@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> 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@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>