Re: do the QANESAVA and QANERSTA APIs use save files?

I can confirm that. I am running my code to save a very large library using
the QANESAVA api. The program takes the QANESAVA exit program data and
streams it to a remote sock on a network PC. The PC started to receive the
save data almost immediately after I started the save code on the 400. So
far the PC says it has received 8GB with no change in WRKSYSSTS dasd usage.
The transfer rate is about 400MB per minute. ( a POWER 5 570 )

BTW, network switches must be a ton faster than SOHO phone company supplied
routers. When I run my code on the receiving end, streaming the save file
data from a PC to JS12, the transfer rate is much slower. At least I think
that is where the bottleneck is.


On Tue, Apr 14, 2009 at 5:37 PM, Vern Hamberg <vhamberg@xxxxxxxxxxx> wrote:

Gents and ladies

I just talked today with an IBMer who says that these APIs do not use
save files. But I'd not seen this post before talking to him. I
specifically asked him whether disk is being used - said no, as I
understood it. Said that if we choose to write out to something, yes,
then there's double storage usage. But it's a buffer that the exit
program receives, right? So it's minimal impact on storage, AFAIK.

Now being the machine it is, there is always stuff being done on DASD
for temporary actions.

Regards
Vern

Flensburg, Carsten wrote:

Steve,

Sorry, I had no intention of replying since I don't know the answer - I
must have hit the wrong button when browsing through my inbox. Anyway,
I've noticed the same behavior as you have, when working with the two
APIs in question. You'll also see evidence of the save file in the QTEMP
library of the QANEAGNT prestart job performing the actual save record
buffering. I don't however know exactly how this implementation affects
the storage requirement during the save/restore process, and nothing
seems to be documented in the manual as far as this issue is concerned.

Best regards,
Carsten Flensburg

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve Richter
Sent: 13. april 2009 23:23
To: Midrange Systems Technical Discussion
Subject: Re: do the QANESAVA and QANERSTA APIs use save files?

Carsten,

Did you have a reply? I dont see it.

thanks,




On Mon, Apr 13, 2009 at 2:35 PM, Flensburg, Carsten
<Flensburg@xxxxxxxxxx>wrote:

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve Richter
Sent: 13. april 2009 14:12
To: Midrange Systems Technical Discussion
Subject: do the QANESAVA and QANERSTA APIs use save files?

I am working with the QANESAVA and QANERSTA APIs to save and restore
direct to a network socket. The idea being to pass the data streamed
by the QANESAVA API direct to a .NET program running on a PC.

I am seeing mention of temporary save files in the low level messages

of the save/restore agent job:

Message . . . . : 4 objects restored. 1 not restored to SRICHTER3.

Cause . . . . . : 4 objects were restored from SRICHTER2 to

SRICHTER3

at

04/13/09 07:52:01. 1 objects were not restored to SRICHTER3. Objects

were restored from save file QANE262913 in library QTEMP.

Is the internal functioning of QANESAVA to first save to a save file,
and then stream the save file data to the exit program? If so, does
that mean that to use QANESAVA you need enough free space on the
system to hold that temporary save file?

thanks,
--
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 communication is intended only for use by the addressee.It may
contain confidential or privilegedinformation.
If you receive this communication unintentionally, please inform us
immediately and delete this e-mail and any attachments.
Warning: Although we have taken reasonable precautions to ensure no
viruses are present in this email, we cannot accept responsibility for

any loss or damage arising from the use of this email orattachments.

--
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 communication is intended only for use by the addressee.It may

contain confidential or privilegedinformation.

If you receive this communication unintentionally, please inform us

immediately and delete this e-mail and any attachments.

Warning: Although we have taken reasonable precautions to ensure no

viruses are present in this email, we cannot accept

responsibility for any loss or damage arising from the use of this email

orattachments.

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