93 lines
6.3 KiB
HTML
93 lines
6.3 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="concept" />
|
||
<meta name="DC.Title" content="How workstation devices are allocated" />
|
||
<meta name="abstract" content="Subsystems attempt to allocate all workstation devices in its subsystem description for AT(*SIGNON) workstation entries." />
|
||
<meta name="description" content="Subsystems attempt to allocate all workstation devices in its subsystem description for AT(*SIGNON) workstation entries." />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakswhathappenssbsstarts.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakssbsasignuser.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="../experience/work1abstract.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakssbsasignuser.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="../rzaiw/rzaiwprogramtypes.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="rzakswrkstationallocationa" />
|
||
<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>How workstation devices are allocated</title>
|
||
</head>
|
||
<body id="rzakswrkstationallocationa"><a name="rzakswrkstationallocationa"><!-- --></a>
|
||
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
<h1 class="topictitle1">How workstation devices are allocated</h1>
|
||
<div><p>Subsystems attempt to allocate all workstation devices in its subsystem
|
||
description for AT(*SIGNON) workstation entries.</p>
|
||
<p>The following situations might occur during the time the subsystem starts:</p>
|
||
<ul><li>If the device is not varied on, the subsystem cannot allocate it. The
|
||
system arbiter (QSYSARB) and the QCMNARBxx jobs hold locks on all varied-off
|
||
devices. </li>
|
||
<li>If the device is varied on and has not been allocated by any other subsystem,
|
||
the subsystem can allocate it and display the signon display. </li>
|
||
<li>If the device is varied on and has been allocated by another subsystem
|
||
and is at the signon display (the signon display was displayed before the
|
||
second subsystem was started), a second subsystem can allocate the device
|
||
from the first subsystem and display the signon display.</li>
|
||
</ul>
|
||
<p>If more than one subsystem tries to allocate the same workstation (as specified
|
||
in the workstation entries) and the workstation is varied off, the subsystem
|
||
that gets the workstation when it is varied on cannot be predicted. Similarly,
|
||
if a workstation entry specifies a workstation type instead of a workstation
|
||
name, a subsystem might get all, some, or none of the workstations of that
|
||
type. (This also applies to workstation entries with generic
|
||
names.) To avoid such a situation, you can set up the workstation entries
|
||
for the subsystems so multiple subsystems are not using the same workstations.</p>
|
||
<div class="section"><h4 class="sectiontitle">After a user has signed on</h4><div class="p">When a user signs on
|
||
to a workstation, the job runs in the subsystem that was shown on the signon
|
||
display on the workstation (the subsystem is identified in the IBM-supplied
|
||
signon display). The following situations might occur after the user has signed
|
||
on: <ul><li>If a second subsystem is started and it tries to allocate the workstation
|
||
on which the user signed on, the second subsystem cannot allocate it. The
|
||
user’s job continues to run in the first subsystem. </li>
|
||
<li>If the user selects option 1 (Display signon for alternative job) on the
|
||
System Request menu or issues the Transfer to Secondary Job (<span class="cmdname">TFRSECJOB</span>)
|
||
command, the new job runs in the same subsystem as the original job. </li>
|
||
<li>When the user signs off, the workstation remains allocated to the subsystem
|
||
used when the user signed on, unless the user transferred into the subsystem
|
||
using the Transfer Job (<span class="cmdname">TFRJOB</span>) command, and specified <span class="parmname">AT</span>(*ENTER)
|
||
for the workstation entry for this workstation. A signon display is shown,
|
||
and any subsequent jobs from that workstation continue to run in that subsystem,
|
||
(unless another subsystem is started up that allocates the workstation while
|
||
it is at the signon display). </li>
|
||
<li>If the user signs off and the subsystem in which his job was running is
|
||
ended, the device is deallocated. A second subsystem can then allocate the
|
||
device and display the signon display.</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div>
|
||
<div class="familylinks">
|
||
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakswhathappenssbsstarts.htm" title="When a subsystem starts, the system allocates several items and starts autostart and prestart jobs before the subsystem is ready for work.">How a subsystem starts</a></div>
|
||
</div>
|
||
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
<div><a href="rzakssbsasignuser.htm" title="This topic section discusses several techniques that can be used for assigning device names and then associating those device names with users. After this is accomplished, you can use the workstation entries to get the user to the correct subsystem.">Assigning users to a specific subsystem</a></div>
|
||
</div>
|
||
<div class="relinfo"><strong>Related information</strong><br />
|
||
<div><a href="../experience/work1abstract.htm">Subsystem Configuration experience report</a></div>
|
||
<div><a href="../rzaiw/rzaiwprogramtypes.htm">Use Telnet exit point programs</a></div>
|
||
</div>
|
||
</div>
|
||
</body>
|
||
</html> |