ibm-information-center/dist/eclipse/plugins/i5OS.ic.apis_5.4.0.1/dsm3.htm

89 lines
3.6 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Copyright" content="Copyright (c) 2006 by IBM Corporation">
<title>Session Services APIs</title>
<!-- Begin Header Records ========================================= -->
<!-- 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. -->
<!-- Change History: -->
<!-- YYMMDD USERID Change description -->
<!-- DSMMST1 SCRIPT A converted by B2H R4.1 (346) (CMS) by V2KEA304 -->
<!-- at RCHVMW2 on 29 Jan 1999 at 16:05:09 -->
<!-- File Edited November 2001 -->
<!-- End Header Records -->
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body>
<!-- Java sync-link -->
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript">
</script>
<h2>Session Services APIs</h2>
<p>The session services APIs provide a general scrolling I/O interface. They
can be used to build a standard input-line scrolling interface or an interface
that has an output-only scroll area (called a <strong>scroller</strong>) in a
window. Sessions are special cases of windows as supported by the window
services. A session is defined using a session, a window, and a low-level
environment description. The window and low-level environment descriptions are
the same as those used to define a window directly with the window services
APIs. The session description defines the structure of the session. The
structure includes the coordinates of the scrolling portion, the length of the
input line, the amount to roll by, and so on. A session is implemented as a
window, where the window user data pointer describes the session itself. Thus,
a session can be manipulated through the window and low-level interfaces by
passing the session handler or through the session interfaces. This
implementation is similar to the concept of inheritance in object-oriented
programming languages.</p>
<p>Sessions are similar in concept to subfiles and can be used for any
application that requires a scrolling line interface. The session services APIs
are divided into the following functional groups:</p>
<ul>
<li><a href="dsm3a.htm">Session manipulation and query APIs</a> allow you
to create, query, and manipulate sessions.<br>
<br>
</li>
<li><a href="dsm3b.htm">Session I/O APIs</a> allow you to perform input and
output operations to sessions.</li>
</ul>
<p>For additional information, select one of the following:</p>
<ul>
<li><a href="dsm3c.htm#Header_594">Session Details</a></li>
<li><a href="dsm3c.htm#Header_595">Line Mode and Character Mode I/O</a></li>
<li><a href="dsm3c.htm#HDRCMDKEY">Command Key Action Routines</a></li>
<li><a href="dsm3c.htm#Header_597">Action Routine Parameters</a></li>
<li><a href="dsm3c.htm#HDRACTPOS">Active Position</a></li>
<li><a href="dsm3c.htm#HDREBCDICC">EBCDIC Display Control Characters</a></li>
<li><a href="dsm3c.htm#HDRSSDBCS">DBCS Considerations</a></li>
</ul>
<br>
<hr>
<center>
<table cellpadding="2" cellspacing="2">
<tr align="center">
<td valign="middle" align="center">
<a href="#Top_Of_Page">Top</a> |
<a href="dsm.htm">Dynamic Screen Manager APIs</a> |
<a href="aplist.htm">APIs by category</a></td>
</tr>
</table>
</center>
<br>
</body>
</html>