× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Saving spool files!
  • From: Eric Sundell PMI <esundell@xxxxxxxxxxxxx>
  • Date: Thu, 18 Mar 1999 11:19:00 -0800

How so, does it mess up some pointers or something?

____________________Reply Separator____________________
Subject:    Re: Saving spool files!
Author: "Pete Massiello" [SMTP:pmassiello@os-solutions.com]
Date:       3/18/99 9:51 AM

Saving and restoring the DB file in QSPL spells DISASTER.

    Dont do it.

    Pete

Eric Sundell PMI wrote:

> I would like the code for this, thanks.
> By the way, I have never tried this but what would be the possibility of
> saving
> and restoring the DB file in QSPL, that's where the spool files and their
> information actually are, but I'm not sure if they would automatically get
> picked up by the system or what.-EDS
>
> ____________________Reply Separator____________________
> Subject:    Re: Saving spool files!
> Author: "Shannon O'Donnell" [SMTP:ORION@auburnctnet.com]
> Date:       3/17/99 12:14 PM
>
> You could use the spool APIs to save and restore your spool files. This
> would
> allow you to capture ALL attributes and restore ALL attributes.
>
> Midrange Computing ran an article with a utility to do this back in 94 or
95
> (can't remember which), but you could log on to that web site
> (www.midrangecomputing.com) and download the code from there for it.
>
> Also, I have a different utility I wrote to save and restore entire output
> queues. I did this when I was doing CISC to RISC conversions and I was
tired
> of
> doing the copy to database file routine.  If you want the code I have,
send
> me a
> private email and I'll send it to you.
>
> Shannon O'Donnell
> orion@auburnctnet.com
>
> Graap, Ken wrote:
>
> > Time to share my frustration...
> >
> > I'm in the process of planning a major configuration change to our
> > production system which will involve backing up the entire system
(twice)
> > scratching all system data, initializing the system, adding 22 new disk
> > drives, reconfiguring RAID sets and ASP's and then reloading the entire
> > system.
> >
> > This is all a pretty straight forward process (even though it will take
32
> > hours!) for everything on the system except spool files.
> >
> > I wish IBM would treat a spool file as a real object.
> >
> > I know I can copy the spool file to a DB file or to a folder, backup up
> the
> > DB file or folder and then restore it later, in fact I do archive spool
> > files regularly via BRMS but only after they have aged about 30 days.
> >
> > The restore process results in the loss of several very important
> > attributes. The most important being the Jobname the file was originally
> > created in and the original creation date. This really makes things
> > difficult when trying to locate a spool file after it has been
restored...
> > and ... we have 1000's of spool files users access on a regular basis.
> >
> > Does anyone else share my frustration?
> >
> > Does anyone have a good reason why IBM couldn't create a "spool object"
> > which could be saved and restored just like any other object on the
> system,
> > without changing original attributes?
> >
> > Doing this would sure make my life easier....
> >
> > Geesh!
> >
> > Kenneth
> >
> > --
> > ********************************
> >        Kenneth  E.  Graap
> >     IBM Certified Specialist
> >           AS/400   Professional
> >           System  Administrator
> >  NW Natural - Information Services
> >            System Services
> >         503 226 4211 X5537
> >           FAX  503 721 2521
> >       keg@nwnatural.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
> > +---
>
> +---
> | 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
> +---

--
Pete Massiello
OS Solutions International
Phone: (203)-744-7854  Ext 11.
http://www.os-solutions.com
mailto:pmassiello@os-solutions.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
+---
+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.