52 lines
3.9 KiB
HTML
52 lines
3.9 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="Remove communication entries" />
|
|
<meta name="abstract" content="You can remove communication entries from the subsystem description by using the character-based interface. All jobs that are active through the communications entry being removed must be ended before this command can be run." />
|
|
<meta name="description" content="You can remove communication entries from the subsystem description by using the character-based interface. All jobs that are active through the communications entry being removed must be ended before this command can be run." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksdltsubsystem.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="rzaksrmvcommunentry" />
|
|
<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>Remove communication entries</title>
|
|
</head>
|
|
<body id="rzaksrmvcommunentry"><a name="rzaksrmvcommunentry"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Remove communication entries</h1>
|
|
<div><p>You can remove communication entries from the subsystem description
|
|
by using the character-based interface. All jobs that are active through the
|
|
communications entry being removed must be ended before this command can be
|
|
run. </p>
|
|
<div class="section"><strong>Command</strong>: Remove Communications Entry (<span class="cmdname">RMVCMNE</span>)</div>
|
|
<div class="example"><strong>Example</strong>: This command removes the communications device entry
|
|
for the device COMDEV from the subsystem description SBS1 in library LIB2.
|
|
<blockquote><pre>RMVCMNE SBSD(LIB2/SBS1) DEV(COMDEV)</pre>
|
|
</blockquote>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksdltsubsystem.htm" title="The Delete Subsystem Description (DLTSBSD) command deletes the specified subsystem descriptions (including any work entries or routing entries added to them) from the system. Job queues assigned to this subsystem by the Add Job Queue Entry (ADDJOBQE) command are not deleted. In fact, when you delete a subsystem description (SBSD), none of the objects that are referenced by the SBSD are deleted.">Delete 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> |