RE: Program to read SAV output to IFS or userspace

Hi Tom,

There's also a pretty good explanation of how to interpret the SAV
command output to user space and stream file to be found here:
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/rzaiu/rzaiur
zaiu004.htm

Best regards,
Carsten Flensburg

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tom Liotta
Sent: 27. august 2007 22:43
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Program to read SAV output to IFS or userspace

Jim Essinger wrote:

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:

Note that the output can be to a spooled file, a stream file or a user
space. For many purposes, streamfiles and user spaces are nearly
interchangeable. The 16MB *usrspc limit is one potential problem here,
but /might/ be far more than enough. The *usrspc needs to exist before
SAV runs. I'd have to test to see if it auto-extends or if it has to
have its attribute set first.

It takes a few minutes to figure out how to read the resulting *USRSPC
info, but it can be done even in OPM CL. A DMPOBJ of a *USRSPC resulting
from a test run of SAV helps a lot.