RE: QSYS Version Libraries

On our system, we have talked, but not reached concensus, on the notion of using Ops Nav to get all reports associated with end fiscal moved to something that can be saved to a CD or DVD, because 90% of the reason why management wants to keep end fiscal reports from 2 years ago is to be able to show reports to auditors, printing only the reports needed by auditors. When we can come to an agreement on the path to be used, we can test what works, such as being able to reporint in what format.

A couple months ago we had an IRS audit, in which they needed to see everything that got posted to our General Ledger in 2005, and this was after we had closed fiscal years 2005 and 2006, so most BPCS reports no longer able to access dead fiscal years. Fortunately I was not finished purging 2004, and I have a "dump GL" modification which puts the GL data into an Excel friendly format, with reverse engineering on where the GL data came from, although it had to be massaged a bit to get the data into a form that was acceptable to the IRS.

There's also a situation I am not at liberty to discuss, where no one wants to take responsibility for deleting something that has HUGE legal implications. Fortunately I was able to copy the legal hot potato to a separate library, then delete the ancient vintage stuff surrounding it.

For some kinds of reports, we are allowed to use a photocopy machine if another copy is needed, but that only works if you have a printed original convenient.

While various reports are printed at time of each end fiscal, our systems of managing printed reports is such that the odds, of finding stuff 3 years later, are pretty low.

Management knows that at V5R1 we cannot backup spool files, and that systems to do so are available, but they won't spend the $ to get them.

Fortunately I recently got Locksmith ... UPI's archiving system.

It comes with a bunch of cool features to help with data cleanup, many of them superior to what came with BPCS, or my modifications. For example, you can put stuff on JOBQ to not run until no one on system, where you have specified some library ... it will identify all files in that library with deleted records, remove them, and recover their disk space. That sort of thing would be useful to places that are not even on BPCS.

I found RTVDSKINF to be most helpful plus removing 1000's of spool
files. The system has an older version of EZPRINT - the largest library
on the system.

We are talking to the users about how many months/years of checks really
need to be kept for reprint. After 90 days is it really necessary? I am
for void and re-issue.

Bonnie Lokenvitz

-----Original Message-----
From: Al Mac Wheel

You might also review if there are PTF libraries on PTFs that have been
installed.

Perhaps we can trade tips ... I work on an 170 which has hurting disk
space.

It used to be that I could spend much more time managing reources, but
for
many months I have been hammered with new projects, rush projects,
critical
development, so I go longer time between sessions of spending less time
doing disk space management.

We are at about 77% used and climbing. I have a laundry list of things
I
need to do to attack this, but day to day projects get in the way.
Close
to 10% of our disk space is reports ... I have tried many times to get
policies changed on retention.

My main current hope is time to convert some programs that access
historical data vs. an archive collection, then get rid of the data now
being accessed from a non-archive library. Then beyond that, address
some
issues with respect to redundant data.

>I have been asked to clean up disk space on a hurting 170 that is at
>V5R1.
>
>Can I delete libraries QSYSV4R4M0 and QSYSV4R5M0 without any issues?
>
>Thank you,
>Bonnie Lokenvitz
>


--
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.