60 lines
5.0 KiB
HTML
60 lines
5.0 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="task" />
|
||
|
|
<meta name="DC.Title" content="Add communications entries" />
|
||
|
|
<meta name="abstract" content="Each communication entry describes one or more communication device, device types, or remote location for which the subsystem will start jobs when program start requests are received. The subsystem can allocate a communication device if the device is not currently allocated to another subsystem or job. A communications device that is currently allocated may eventually be de-allocated, making it available to other subsystems. To add a communications entry to the subsystem description, use the character-based interface." />
|
||
|
|
<meta name="description" content="Each communication entry describes one or more communication device, device types, or remote location for which the subsystem will start jobs when program start requests are received. The subsystem can allocate a communication device if the device is not currently allocated to another subsystem or job. A communications device that is currently allocated may eventually be de-allocated, making it available to other subsystems. To add a communications entry to the subsystem description, use the character-based interface." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakscreatesubsystemdef.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutcommentry.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="rzaksaddcommunentry" />
|
||
|
|
<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>Add communications entries</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksaddcommunentry"><a name="rzaksaddcommunentry"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Add communications entries</h1>
|
||
|
|
<div><p>Each communication entry describes one or more communication device,
|
||
|
|
device types, or remote location for which the subsystem will start jobs when
|
||
|
|
program start requests are received. The subsystem can allocate a communication
|
||
|
|
device if the device is not currently allocated to another subsystem or job.
|
||
|
|
A communications device that is currently allocated may eventually be de-allocated,
|
||
|
|
making it available to other subsystems. To add a communications
|
||
|
|
entry to the subsystem description, use the character-based interface.</p>
|
||
|
|
<div class="section"><strong>Command</strong>: Add Communications Entry (<span class="cmdname">ADDCMNE</span>)</div>
|
||
|
|
<div class="example"><strong>Example</strong>: This example adds a communications entry for the
|
||
|
|
APPC device named COMDEV and mode *ANY to the subsystem description SBS1,
|
||
|
|
which resides in library ALIB. The DFTUSR parameter defaults to *NONE, which
|
||
|
|
means that no jobs may enter the system through this entry unless valid security
|
||
|
|
information is supplied on the program start request. <blockquote><pre>ADDCMNE SBSD(ALIB/SBS1) DEV(COMDEV)</pre>
|
||
|
|
</blockquote>
|
||
|
|
</div>
|
||
|
|
<div class="section"><div class="note"><span class="notetitle">Note:</span> You must specify either the <span class="parmname">DEV</span> parameter
|
||
|
|
or the <span class="parmname">RMTLOCNAME</span> parameter, but not both.</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakscreatesubsystemdef.htm" title="You can create a subsystem description in two ways. You can copy an existing subsystem description and change it, or you can create an entirely new description.">Create a subsystem description</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzaksaboutcommentry.htm" title="The communications work entry identifies to the subsystem the sources for the communications job it will process. The job processing begins when the subsystem receives a communications program start request from a remote system and an appropriate routing entry is found for the request.">Communications entries</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|