ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaks_5.4.0.1/rzakssbsintactconfig7.htm

72 lines
5.6 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<?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="task" />
<meta name="DC.Title" content="Configure an interactive subsystem: Customize QINTER" />
<meta name="abstract" content="When you begin using your own set of subsystems, you might not need to use QINTER. However, if you have a reason to continue to use QINTER, you need to ensure that QINTER is set up NOT to allocate the workstations that you want to run under your other subsystems. There are two possible ways to do this." />
<meta name="description" content="When you begin using your own set of subsystems, you might not need to use QINTER. However, if you have a reason to continue to use QINTER, you need to ensure that QINTER is set up NOT to allocate the workstations that you want to run under your other subsystems. There are two possible ways to do this." />
<meta name="DC.Relation" scheme="URI" content="rzakssbsintactconfig.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakssbsintactconfig6.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaksbsintactconfi8.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2004-2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004-2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzakssbsintactconfig7" />
<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>Configure an interactive subsystem: Customize QINTER</title>
</head>
<body id="rzakssbsintactconfig7"><a name="rzakssbsintactconfig7"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Configure an interactive subsystem: Customize QINTER</h1>
<div><p>When you begin using your own set of subsystems, you might not
need to use QINTER. However, if you have a reason to continue to use QINTER,
you need to ensure that QINTER is set up NOT to allocate the workstations
that you want to run under your other subsystems. There are two possible ways
to do this.</p>
<div class="section">Remove the *ALL workstation entry from QINTER:</div>
<ol><li class="stepexpand"><span>Remove the *ALL workstation entry from QINTER, and then add specific
workstation entries that indicate which devices you want QINTER to allocate.</span> Removing the workstation type entry of *ALL is to prevent QINTER from
attempting to allocate all workstations.</li>
<li class="stepexpand"><span>Add a workstation entry for devices named DSP* to allow all twinax-attached
display devices to continue to be allocated to QINTER. </span></li>
</ol>
<div class="example">In this example, the twinax-attached display devices will continue
to run in QINTER; QINTER will not attempt to allocate any other devices. <blockquote><pre>RMVWSE SBSD(QGPL/QINTER) WRKSTNTYPE(*ALL)
ADDWSE SBSD(QGPL/QINTER) WRKSTN(DSP*)</pre>
</blockquote>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakssbsintactconfig.htm" title="The information in this section explains how to set up a new interactive subsystem.">Configure an interactive subsystem</a></div>
<div class="previouslink"><strong>Previous topic:</strong> <a href="rzakssbsintactconfig6.htm" title="Add workstation entries to the subsystem description. This is the key step for assigning which devices are allocated to which subsystem.">Configure an interactive subsystem: Add workstation entries</a></div>
<div class="nextlink"><strong>Next topic:</strong> <a href="rzaksbsintactconfi8.htm" title="A final, but VERY important consideration regarding QINTER is the workstation type entry of *CONS for the console. Make sure that you do not accidentally prevent someone from signing on at the console. You prevent this from happening by not adding any workstation entries for the console to your custom interactive subsystems.">Configure an interactive subsystem: Configure the console</a></div>
</div>
</div><div class="nested1" xml:lang="en-us" id="rzaksbsintactconfig7a"><a name="rzaksbsintactconfig7a"><!-- --></a><h2 class="topictitle2">Second method</h2>
<div><div class="section">Add a workstation entry to tell QINTER not to allocate the devices
that are assigned to other subsystems. However, allow QINTER to continue to
allocate any other device that is not allocated to a subsystem. This keeps
the workstation type entry of *ALL in the QINTER subsystem and adds workstation
name entries with the <span class="parmname">AT</span> parameter for those devices
that are allocated to different subsystems.</div>
<div class="example"><blockquote><pre>ADDWSE SBSD(QGPL/QINTER) WRKSTN(PGMR*) AT(*ENTER)
ADDWSE SBSD(QGPL/QINTER) WRKSTN(ORDERENT*) AT(*ENTER)</pre>
</blockquote>
</div>
</div>
</div>
</body>
</html>