131 lines
7.1 KiB
HTML
131 lines
7.1 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="reference" />
|
||
|
|
<meta name="DC.Title" content="DDM syntax error code descriptions" />
|
||
|
|
<meta name="abstract" content="If FCT+ (SPACE- 02) contains 124C in bytes 3 and 4, look for one of these codes in byte 6." />
|
||
|
|
<meta name="description" content="If FCT+ (SPACE- 02) contains 124C in bytes 3 and 4, look for one of these codes in byte 6." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1ddmec.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="rbal1syntaxerror" />
|
||
|
|
<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>DDM syntax error code descriptions</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1syntaxerror"><a name="rbal1syntaxerror"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">DDM syntax error code descriptions</h1>
|
||
|
|
<div><p>If FCT+ (SPACE- 02) contains 124C in bytes 3 and 4, look for one
|
||
|
|
of these codes in byte 6.</p>
|
||
|
|
<div class="section"><dl><dt class="dlterm">01</dt>
|
||
|
|
<dd>DSS header length less than 6.</dd>
|
||
|
|
<dt class="dlterm">02</dt>
|
||
|
|
<dd>DSS header length does not match the number of bytes of data found.</dd>
|
||
|
|
<dt class="dlterm">03</dt>
|
||
|
|
<dd>DSS head C-byte not <span>X'D0'</span>.</dd>
|
||
|
|
<dt class="dlterm">04</dt>
|
||
|
|
<dd>DSS header F-bytes either not recognized or not supported.</dd>
|
||
|
|
<dt class="dlterm">05</dt>
|
||
|
|
<dd>DSS continuation specified, but not found. For example, DSS continuation
|
||
|
|
is specified on the last DSS, and the SEND indicator has been returned by
|
||
|
|
the SNA LU 6.2 communications program.</dd>
|
||
|
|
<dt class="dlterm">06</dt>
|
||
|
|
<dd>DSS chaining specified, but no DSS found. For example, DSS chaining is
|
||
|
|
specified on the last DSS, and the SEND indicator has been returned by the
|
||
|
|
SNA LU 6.2 communications program.</dd>
|
||
|
|
<dt class="dlterm">07</dt>
|
||
|
|
<dd>Object length less than 4. For example, a command parameter length is
|
||
|
|
specified as 2, or a command length is specified as 3.</dd>
|
||
|
|
<dt class="dlterm">08</dt>
|
||
|
|
<dd>Object length does not match the number of bytes of data found. For example,
|
||
|
|
an RQSDSS with a length 150 contains a command whose length is 125, or an
|
||
|
|
SRVDGN (server diagnostic information) parameter specifies a length of 200,
|
||
|
|
but there are only 50 bytes left in the DSS.</dd>
|
||
|
|
<dt class="dlterm">09</dt>
|
||
|
|
<dd>Object length greater than maximum allowed. For example, the RECCNT parameter
|
||
|
|
specifies a length of 5, but this indicates that only half of the hours field
|
||
|
|
is present instead of the complete hours field.</dd>
|
||
|
|
<dt class="dlterm">0A</dt>
|
||
|
|
<dd>Object length less than minimum required. For example, the SVRCOD parameter
|
||
|
|
specifies a length of 5, but the parameter is defined to have a fixed length
|
||
|
|
of 6.</dd>
|
||
|
|
<dt class="dlterm">0B</dt>
|
||
|
|
<dd>Object length not allowed. For example, the FILEXPDT parameter is specified
|
||
|
|
with a length of 11, but this indicates that only half of the hours field
|
||
|
|
is present instead of the complete hours field.</dd>
|
||
|
|
<dt class="dlterm">0C</dt>
|
||
|
|
<dd>Incorrect large object extended length field (see the description of DSS).
|
||
|
|
For example, an extended length field is present, but it is only 3 bytes long.
|
||
|
|
It is defined as being a multiple of 2 bytes long.</dd>
|
||
|
|
<dt class="dlterm">0D</dt>
|
||
|
|
<dd>Object code point index not supported. For example, a code point of <span>X'8032'</span> is
|
||
|
|
encountered, but <span>X'8'</span> is a reserved code point index.</dd>
|
||
|
|
<dt class="dlterm">0E</dt>
|
||
|
|
<dd>Required object not found. For example, a CLRFIL command does not have
|
||
|
|
an FILNAM parameter present, or an MODREC command is not followed by a RECORD
|
||
|
|
command data object.</dd>
|
||
|
|
<dt class="dlterm">0F</dt>
|
||
|
|
<dd>Too many command data objects sent. For example, an MODREC command is
|
||
|
|
followed by two RECORD command data objects, or a DELREC command is followed
|
||
|
|
by a RECORD object.</dd>
|
||
|
|
<dt class="dlterm">10</dt>
|
||
|
|
<dd>Mutually exclusive objects present. For example, a CRTDIRF command specifies
|
||
|
|
both a DCLNAM and a FILNAM parameter.</dd>
|
||
|
|
<dt class="dlterm">11</dt>
|
||
|
|
<dd>Too few command data objects sent. For example, an INSRECEF command that
|
||
|
|
specified RECCNT(5) is followed by only four RECORD command data objects.</dd>
|
||
|
|
<dt class="dlterm">12</dt>
|
||
|
|
<dd>Duplicate object present. For example, a LSTFAT command has two FILNAM
|
||
|
|
parameters specified.</dd>
|
||
|
|
<dt class="dlterm">13</dt>
|
||
|
|
<dd>Specified request correlation identifier not valid. Use PRCCNVRM with
|
||
|
|
a PRCCNVCD of <span>X'04'</span> or <span>X'05'</span> instead of this error code.
|
||
|
|
This error code is being maintained for compatibility with Level 1 architecture.</dd>
|
||
|
|
<dt class="dlterm">14</dt>
|
||
|
|
<dd>Required value not found.</dd>
|
||
|
|
<dt class="dlterm">15</dt>
|
||
|
|
<dd>Reserved value not allowed. For example, an INSRECEF command specified
|
||
|
|
an RECCNT(0) parameter.</dd>
|
||
|
|
<dt class="dlterm">16</dt>
|
||
|
|
<dd>DSS continuation less than or equal to 2. For example, the length bytes
|
||
|
|
for the DSS continuation have a value of 1.</dd>
|
||
|
|
<dt class="dlterm">17</dt>
|
||
|
|
<dd>Objects not in required order. For example, a RECAL object contains a
|
||
|
|
RECORD object followed by a RECNBR object that is not in the specified order.</dd>
|
||
|
|
<dt class="dlterm">18</dt>
|
||
|
|
<dd>DSS chaining bit not a binary 1, but DSSFMT bit 3 is set to a binary 1.
|
||
|
|
Next DSS has the same request correlator.</dd>
|
||
|
|
<dt class="dlterm">19</dt>
|
||
|
|
<dd>Previous DSS indicated current DSS has the same request correlation, but
|
||
|
|
the request correlation identifiers are not the same.</dd>
|
||
|
|
<dt class="dlterm">1A</dt>
|
||
|
|
<dd>DSS chaining bit not a binary 1, but error continuation is requested.</dd>
|
||
|
|
<dt class="dlterm">1B</dt>
|
||
|
|
<dd>Mutually exclusive parameter values specified. For example, an OPEN command
|
||
|
|
specified PRPSHD(TRUE) and FILSHR(READER).</dd>
|
||
|
|
<dt class="dlterm">1D</dt>
|
||
|
|
<dd>Code point not a valid command. For example, the first code point in RQSDSS
|
||
|
|
either is not in the dictionary or is not a code point for a command.</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1ddmec.htm" title="These error codes are included in the FFDC dumps (L in the sample dump output) that identify DDM error conditions. These conditions might or might not be defined by the DDM architecture.">DDM error codes</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|