×
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.
On 23/11/2007, at 10:48 PM, David FOXWELL wrote:
Anyone tried this ? And what about QWSSPRST ?
http://search400.techtarget.com/tip/0,289483,sid3_gci1027630,00.html
Both techniques work but are really for different, although related,
purposes.
The DSM APIs QsnSavScr and QsnRstScr are used to allow an application
to save a copy of the screen before replacing it with something else
and then restore it afterwards. These APIs are a direct interface to
the 5250 Save Screen and Restore Screen commands. These are commonly
used when windows are displayed on the screen.
The QWSSPRST API is used to suspend a display file to allow an
application to write something else to the device. There are
situations where the device is not in the proper state to have data
sent to it such as when the device is waiting for user input. This
API allows the application to overcome that.
I've wasted a lot of time on it this morning without understanding
anything.
Exactly what are you trying to accomplish or understand? You haven't
explained what you're trying to do very well.
Has anyone a clear, simple example ?
Of what?
The referenced URL shows how to use QsnSavScr--although prototyping
the APIs and using EVAL or CALLP would be better. The article text
says QsnRstScr cannot be used to reinstate the save screen but that's
just because the author CHOSE to perform a direct save. If he had
done an indirect save then QsnRstScr would work.
The QWSSPRST API has a very simple interface: 4 parameters; CHAR(1),
BIN(4), CHAR(1), plus error code DS. Why would you need an example of
its use? Just call it before whatever you want to do, do your stuff,
then call it again after your stuff to restore the previous state.
What are you trying to accomplish that specifying RSTDSP(*YES) on the
display file won't accomplish?
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
midrange.com
