80 lines
5.2 KiB
HTML
80 lines
5.2 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="reference" />
|
||
|
|
<meta name="DC.Title" content="Managing iSeries communications sessions for application programs" />
|
||
|
|
<meta name="abstract" content="System Object Access APIs for iSeries Access for Windows communicate with the iSeries server through the use of one or more client/server conversations." />
|
||
|
|
<meta name="description" content="System Object Access APIs for iSeries Access for Windows communicate with the iSeries server through the use of one or more client/server conversations." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiksoaprogconsiderations.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="soamanagecommsessions" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Managing iSeries communications
|
||
|
|
sessions for application programs</title>
|
||
|
|
</head>
|
||
|
|
<body id="soamanagecommsessions"><a name="soamanagecommsessions"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Managing iSeries communications
|
||
|
|
sessions for application programs</h1>
|
||
|
|
<div><p>System Object Access APIs for <span class="keyword">iSeries™ Access for Windows<sup>®</sup></span> communicate
|
||
|
|
with the iSeries server
|
||
|
|
through the use of one or more client/server conversations.</p>
|
||
|
|
<div class="section"><p>Because it often takes several seconds to establish a conversation,
|
||
|
|
your application may experience delays when a list first is opened. This topic
|
||
|
|
explains how to control and manage the initiation of conversations so that
|
||
|
|
the performance impact on application programs is minimized.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>The default behavior of System Object Access may be summarized
|
||
|
|
as follows: </p>
|
||
|
|
<ul><li>If no conversation has been established with the iSeries system object that is identified
|
||
|
|
on the <span class="apiname">CWBSO_CreateListHandleEx</span> API, a conversation automatically
|
||
|
|
will be started when the list is opened or displayed. If <span class="keyword">iSeries Access for Windows</span> has
|
||
|
|
not yet established a connection to the specified system, a dialog box will
|
||
|
|
appear prompting the user for the appropriate UserID and password.</li>
|
||
|
|
<li>If another instance of the application program starts, the above process
|
||
|
|
repeats itself. No conversation sharing occurs between application programs
|
||
|
|
that run in different processes (that is, with different instance handles).</li>
|
||
|
|
<li>When the application program deletes the last System Object Access list,
|
||
|
|
the conversation with the iSeries server is automatically ended (Note that <span class="apiname">CWBSO_CloseList</span> does
|
||
|
|
not end the conversation with the iSeries server).</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>A System Object Access conversation may be started using the <span class="apiname">cwbRC_StartSysEx</span> API.
|
||
|
|
This API accepts an iSeries system object as a parameter, and returns
|
||
|
|
a system handle. Save this handle for later use on the <span class="apiname">cwbRC_StopSys</span> API,
|
||
|
|
when the application is terminating and it is time to end the conversation
|
||
|
|
with the iSeries server.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>When the <span class="apiname">cwbRC_StartSysEx</span> API is called, the
|
||
|
|
application is blocked until the conversation is established. Therefore, it
|
||
|
|
is good practice to inform the user that a connection is about to be attempted
|
||
|
|
immediately before the call. On return, the conversation will have been initiated,
|
||
|
|
and System Object Access list processing will use this conversation instead
|
||
|
|
of starting a new one.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>When <span class="apiname">cwbRC_StartSysEx</span> is used in this way,
|
||
|
|
the last list to be deleted will not end the conversation. You must call <span class="apiname">cwbRC_StopSys</span> explicitly
|
||
|
|
before you exit the application.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiksoaprogconsiderations.htm" title="See the following topics for important SOA programming considerations.">iSeries Access for Windows System Object Access programming considerations</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|