124 lines
8.1 KiB
HTML
124 lines
8.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="Using XPCML" />
|
||
|
|
<meta name="abstract" content="Using XPCML is similar to using PCML. The following steps serve as a general outline for the actions that you need to perform to use XPCML." />
|
||
|
|
<meta name="description" content="Using XPCML is similar to using PCML. The following steps serve as a general outline for the actions that you need to perform to use XPCML." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahhxpcmlusingregconvert.htm#rzahhxpcmlusingregconvert" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahhxpcmlusingregcreate.htm#rzahhxpcmlusingregcreate" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahhxpcmlusingregobtain.htm#rzahhxpcmlusingregobtain" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahhxpcmlusingregpass.htm#rzahhxpcmlusingregpass" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahhxpcmlusingcon.htm#rzahhxpcmlusingcon" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahhxpcmlusingerrors.htm#rzahhxpcmlusingerrors" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahhxpcmlmain.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahhxpcmlusingregconvert.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahhxpcmlusingregcreate.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahhxpcmlusingregobtain.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahhxpcmlusingregpass.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahhxpcmlusingcon.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahhxpcmlusingerrors.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzahhxpcmlusing" />
|
||
|
|
<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>Using XPCML</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzahhxpcmlusing"><a name="rzahhxpcmlusing"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Using XPCML</h1>
|
||
|
|
<div><p>Using XPCML is similar to using PCML. The following steps serve
|
||
|
|
as a general outline for the actions that you need to perform to use XPCML.</p>
|
||
|
|
<div class="section"><ol><li>Use XPCML to describe the specification for the program call</li>
|
||
|
|
<li>Create a ProgramCallDocument object</li>
|
||
|
|
<li>Use ProgramCallDocument.callProgram() to run the program</li>
|
||
|
|
</ol>
|
||
|
|
<p>Despite the similarities to using PCML, using XPCML offers enhanced
|
||
|
|
functionality:</p>
|
||
|
|
<ul><li>Have the parser automatically validate parameter values</li>
|
||
|
|
<li>Specify and pass values for program parameters</li>
|
||
|
|
<li>Retrieve the results of a program call to your iSeries™ server in XPCML</li>
|
||
|
|
<li>Transform an existing PCML document into the equivalent XPCML document</li>
|
||
|
|
<li>Extend the XPCML schema to define new simple and complex elements and
|
||
|
|
attributes</li>
|
||
|
|
</ul>
|
||
|
|
<p>For example, IBM<sup>®</sup> Toolbox for Java™ enables you to extend the XPCML schema
|
||
|
|
to create new parameter and data types. You can use this XPCML capability
|
||
|
|
to condense your XPCML source files, which makes the files easier to read
|
||
|
|
and code easier to use.</p>
|
||
|
|
<p>For more information about using XPCML, see
|
||
|
|
the following pages:</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahhxpcmlusingregconvert.htm">Converting existing PCML to XPCML</a></strong><br />
|
||
|
|
The ProgramCallDocument class contains the transformPCMLToXPCML method that enables you to transform existing PCML documents to equivalent XPCML documents.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahhxpcmlusingregcreate.htm">Using XPCML to call a program on your iSeries server</a></strong><br />
|
||
|
|
After you create your XPCML file, you need to create a ProgramCallDocument
|
||
|
|
object that can use the XPCML specifications and data values to call a program
|
||
|
|
on your iSeries server.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahhxpcmlusingregobtain.htm">Obtaining program call results as XPCML</a></strong><br />
|
||
|
|
After you call a server program, you can use ProgramCallDocument.getValue
|
||
|
|
methods to retrieve the Java objects that represent program parameter
|
||
|
|
values. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahhxpcmlusingregpass.htm">Passing in parameter values as XPCML</a></strong><br />
|
||
|
|
You can set the values for program parameters in the XPCML source file and pass in the parameter values as XPCML.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahhxpcmlusingcon.htm">Using condensed XPCML</a></strong><br />
|
||
|
|
Because XPCML is extensible, you can define new parameter types that extend those specified by the XPCML schema. Condensing XPCML extends the XPCML schema to create new data type definitions that simplify and improve the readability and usability of your XPCML documents.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahhxpcmlusingerrors.htm">Identifying parse errors in XPCML</a></strong><br />
|
||
|
|
When validating XPCML schema documents, a fully validating XML parser may generate warnings, non-fatal parse errors, and fatal parse errors.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahhxpcmlmain.htm" title="Extensible Program Call Markup Language (XPCML) enhances the functionality and usability of the Program Call Markup Language (PCML) by offering support for XML schemas. XPCML does not support serialization, so unlike PCML, you cannot serialize an XPCML document.">Extensible Program Call Markup Language</a></div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div class="linklistwithchild">
|
||
|
|
<div class="ulchildlink"><strong><a href="rzahhxpcmlusingregconvert.htm#rzahhxpcmlusingregconvert">Converting
|
||
|
|
PCML to XPCML</a></strong><br />
|
||
|
|
Learn how to transform existing PCML documents to equivalent XPCML documents.</div>
|
||
|
|
|
||
|
|
<div class="ulchildlink"><strong><a href="rzahhxpcmlusingregcreate.htm#rzahhxpcmlusingregcreate">Using
|
||
|
|
XPCML to call a program on your iSeries server</a></strong><br />
|
||
|
|
See how to create a ProgramCallDocument object that uses XPCML to call
|
||
|
|
a program on your server.</div>
|
||
|
|
|
||
|
|
<div class="ulchildlink"><strong><a href="rzahhxpcmlusingregobtain.htm#rzahhxpcmlusingregobtain">Obtaining
|
||
|
|
program call results as XPCML</a></strong><br />
|
||
|
|
Find out how to retrieve the results of your call to a server program
|
||
|
|
as XPCML.</div>
|
||
|
|
|
||
|
|
<div class="ulchildlink"><strong><a href="rzahhxpcmlusingregpass.htm#rzahhxpcmlusingregpass">Passing
|
||
|
|
in parameter values as XPCML</a></strong><br />
|
||
|
|
Learn about setting values for program parameters in XPCML and passing
|
||
|
|
in those values. Examine different techniques for defining constant parameter
|
||
|
|
values and data arrays.</div>
|
||
|
|
|
||
|
|
<div class="ulchildlink"><strong><a href="rzahhxpcmlusingcon.htm#rzahhxpcmlusingcon">Using condensed
|
||
|
|
XPCML</a></strong><br />
|
||
|
|
See how condensing an XPCML document makes it easier to read and use.
|
||
|
|
Find out about using condensed XPCML to create a ProgramCallDocument object
|
||
|
|
and obtaining program call results as condensed XPCML.</div>
|
||
|
|
|
||
|
|
<div class="ulchildlink"><strong><a href="rzahhxpcmlusingerrors.htm#rzahhxpcmlusingerrors">Identifying
|
||
|
|
parse errors in XPCML</a></strong><br />
|
||
|
|
Find out how to identify and log useful warnings and non-fatal parser
|
||
|
|
errors that sometimes occur when parsing an XPCML document.</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|