|
I had some problems trying that and am moving on to other stuff. I was
just trying a few quickies for your question.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
"Jim Essinger" <dilbernator@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/27/2007 02:30 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc
Fax to
Subject
Re: Program to read SAV output to IFS or userspace
Rob,
I read the help for the SAV command to mean something like a .txt file,
but
your example helps me remember that qsys.lib is a valid path for a stream
file name. Have you tried that? I will, but had not thought to point it
back to a member in a database file. Other save commands let you put the
output to a data base PF that can be copied, queried and archived. Easily
processed. The SAV command seems to be a little different. Any Idea on
what the record length of the PF should be?
Jim
On 8/27/07, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
for
There are a couple three solutions for that.
1 - On every save do an output(*outfile). Something like
SAV DEV('/qsys.lib/rob.lib/rob.file')
OBJ(('/rob/console.log'))
OUTPUT('/qsys.lib/rob.lib/robout.file')
2 - Start journalling of IFS objects and search the journal receivers
save occasions. Or write a program to process the journal receivers andto
record that information to a file.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
"Jim Essinger" <dilbernator@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/27/2007 12:49 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc
Fax to
Subject
Re: Program to read SAV output to IFS or userspace
Kenneth,
Thanks for the reply. I know that the objects on the i5 keep that "last
saved" information. I am talking about the IFS objects. Files and
folders. Is that information stored in the header? What about tracking
over time. Was the save done on a timely and regular basis, according
our policies? Can I prove that by looking at the header. I already havea
tracking system for the i5 objects (libraries, files, frograms, other)contents
that
are save, and what tape they are on, I need the same thing for the IFS
objects put on tape with the SAV command. I am also using a home grown
save
that I created, and have maintained for 15 years or more. I don't want,
nor
see the need for a backup solution. It's not, or should not be that
complicated.
Thanks!
Jim
On 8/27/07, Graap, Kenneth <keg@xxxxxxxxxxxxx> wrote:
Holy Smokes Jim ... You don't have to look at the insides of the *SAVF
to prove that an object was saved...
This information is stored in the object header:
Display Object Description - Full
Library
1 of 1
Object . . . . . . . : USRPRF Attribute . . . . . : PF
Library . . . . . : KENNETH Owner . . . . . . . :
QSECOFR
Library ASP device . : *SYSBAS Primary group . . . : *NONE
Type . . . . . . . . : *FILE
Save/Restore information:
Save date/time . . . . . . . . . . : 08/27/07 01:11:49
Restore date/time . . . . . . . . :
Save command . . . . . . . . . . . : SAVLIB
Device type . . . . . . . . . . . : Tape
Sequence number . . . . . . . . . : 328
Volumes . . . . . . . . . . . . . : E00098
File label ID . . . . . . . . . . : KENNETH
Save format . . . . . . . . . . . : Serial
Kenneth
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Essinger
Sent: Monday, August 27, 2007 8:49 AM
To: Midrange Systems Technical Discussion
Subject: Program to read SAV output to IFS or userspace
Greetings,
Before I re-invent the wheel, does anyone have a program that they can
and would be willing to share to read and display or print the
fileof a user space or IFS txt file that is the result of a SAV command? I
do a weekly SAV, and want to be able to show auditors that certain
objects were saved, when and what tape volume they are on. I did a
quick search of the archives, but found no reference. Output to a
http://code.midrange.com/would be just as good.
If you would be willing to share, you can send to me personally, but I
believe it would be better to post the code on
aand then post the link to the code you shared. That way it will be
available for more people.
Thanks!
Jim
--
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
http://archive.midrange.com/midrange-l.moment to review the archives at
----
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.