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



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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.