ibm-information-center/dist/eclipse/plugins/i5OS.ic.rbam6_5.4.0.1/ccdcp.htm

143 lines
8.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="concept" />
<meta name="DC.Title" content="Effect of changing the command definition of a command in a procedure or program" />
<meta name="abstract" content="Some changes can be made to the command definition of a command with no further action. Other changes may require the program or procedure to be recreated, or may cause the program or procedure to function differently." />
<meta name="description" content="Some changes can be made to the command definition of a command with no further action. Other changes may require the program or procedure to be recreated, or may cause the program or procedure to function differently." />
<meta name="DC.subject" content="command, CL, effect of changing definition, command definition, effect of changing, changing, command definition effect on program, CHGCMD (Change Command) command, Change Command (CHGCMD) command, CHGCMD (Change Command), Change Command (CHGCMD), command" />
<meta name="keywords" content="command, CL, effect of changing definition, command definition, effect of changing, changing, command definition effect on program, CHGCMD (Change Command) command, Change Command (CHGCMD) command, CHGCMD (Change Command), Change Command (CHGCMD), command" />
<meta name="DC.Relation" scheme="URI" content="defcm.htm" />
<meta name="DC.Relation" scheme="URI" content="chgcmddef.htm" />
<meta name="DC.Relation" scheme="URI" content="chgcmddefex.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="ccdcp" />
<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>Effect of changing the command definition of a command in a procedure
or program</title>
</head>
<body id="ccdcp"><a name="ccdcp"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Effect of changing the command definition of a command in a procedure
or program</h1>
<div><p>Some changes can be made to the command definition of a command
with no further action. Other changes may require the program or procedure
to be recreated, or may cause the program or procedure to function differently.</p>
<p>When a CL module or program is created, the command definitions of the
commands in the procedure or program are used to generate the module or program.
When the CL procedure or program is run, the command definitions are also
used. If you specify a library name for the command in the CL procedure or
program, the command must be in the same library at procedure creation time
and at run time. If you specify *LIBL for the command in the CL procedure
or program, the command is found, both at procedure creation and run time,
using the library list (*LIBL).</p>
<div class="p">You can make the following changes to the command definition statements
for a command without recreating the modules and programs that use the command.
Some of these changes are made to the command definition statements source,
which requires the command to be recreated. Other changes can be made with
the Change Command (CHGCMD) command. <ul><li>Add an optional parameter in any position. Adding an optional parameter
before the positional limit may affect any procedures, programs, and batch
input streams that have the parameters specified in positional form.</li>
<li>Change the REL and RANGE checks to be less restrictive.</li>
<li>Add new special values. However, this could change the action of the
procedure or program if the value could be specified before the change.</li>
<li>Change the order of the parameters. However, changing the order of the
parameters that precede the positional limit <em>will</em> affect any procedures,
programs, and batch input streams that have the parameters specified in positional
form.</li>
<li>Increase the number of optional elements in a simple list.</li>
<li>Change default values. However, this may affect the operation of the
procedure or program.</li>
<li>Decrease the number of required list items in a simple list.</li>
<li>Change a parameter from required to optional.</li>
<li>Change RSTD from *YES to *NO.</li>
<li>Increase the length when FULL(*NO) is specified.</li>
<li>Change FULL from *YES to *NO.</li>
<li>Change the PROMPT text.</li>
<li>Change the ALLOW value to be less restrictive.</li>
<li>Change the name of the command processing program if the new command processing
program accepts the correct number and type of parameters.</li>
<li>Change the name of the validity checking program if the new validity checking
program accepts the correct number and type of parameters.</li>
<li>Change the mode in which the command can be run as long as the new mode
does not affect the old mode of the same command that is used in a CL procedure
or program.</li>
<li>Change the TYPE to a compatible and less restrictive value. For example,
change the TYPE from *NAME to *CHAR.</li>
<li>Change the MAX value to greater than 1.</li>
<li>Change the PASSATR and VARY values.</li>
</ul>
</div>
<p>The following changes can be made to the command definition statements
depending on what was specified in the CL procedure or program in which the
command is used: </p>
<ul><li>Remove a parameter.</li>
<li>Change the RANGE and REL values to be more restrictive.</li>
<li>Remove special values.</li>
<li>Decrease the number of elements allowed in a list.</li>
<li>Change the TYPE value to be more restrictive or incompatible with the
original TYPE value. For example, change the TYPE value from *CHAR to *NAME
or change *PNAME to *CHAR.</li>
<li>Add a SNGVAL parameter that was previously a list item.</li>
<li>Change the name of an optional parameter.</li>
<li>Remove a value from a list of values.</li>
<li>Increase the number of required list items.</li>
<li>Change a SNGVAL parameter to a SPCVAL parameter.</li>
<li>Change a simple list to a mixed list of like elements.</li>
<li>Change an optional parameter to a constant.</li>
<li>Change RTNVAL from *YES to *NO, or from *NO to *YES.</li>
<li>Change case value from *MIXED to *MONO.</li>
</ul>
<p>The following changes can be made to the command definition statements,
but may cause the procedure or program that uses the command to function differently:
</p>
<ul><li>Change the meaning of a value.</li>
<li>Change the default value.</li>
<li>Change a SNGVAL parameter to a SPCVAL parameter.</li>
<li>Change a value to a SNGVAL parameter.</li>
<li>Change a list to a list within a list.</li>
<li>Change case value from *MIXED to *MONO.</li>
</ul>
<p>The following changes to the command definition statements require that
the procedures or program using the command be recreated. </p>
<ul><li>Addition of a new required parameter.</li>
<li>Removal of a required parameter.</li>
<li>Changing the name of a required parameter.</li>
<li>Changing a required parameter to a constant.</li>
<li>Changing the command processing program to or from *REXX</li>
</ul>
<p>In addition, if you specify *LIBL as the qualifier on the name of the command
processing program or the validity checking when the command is created or
changed, you can move the command processing program or the validity checking
to another library in the library list without changing the command definition
statements.</p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="chgcmddef.htm">Change command defaults</a></strong><br />
You can change the default value of a command keyword by using
the <span class="cmdname">Change Command Default (CHGCMDDFT)</span> command. </li>
<li class="ulchildlink"><strong><a href="chgcmddefex.htm">Examples: Change command defaults</a></strong><br />
These provide examples of changing default values for commands.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="defcm.htm" title="This describes how you can define and create your own commands.">Define commands</a></div>
</div>
</div>
</body>
</html>