RLSMAREA START LIST
The RLSMAREA START LIST message lists the release area definitions for a named release and starting area.
The XML service/scope/message tags and attributes for this message are:
<service name="RLSMAREA">
<scope name="START">
<message name="LIST">
These tags appear in both requests and replies.
RLSMAREA START LIST — Request
The following example shows how you might code a request to list the definitions for a starting release area in a release. Data structure details for the <request> tag follow the example.
Example XML — RLSMAREA START LIST Request
...
<?xml version="1.0"?>
<service name="RLSMAREA">
<scope name="START">
<message name="LIST">
<header>
<subsys>4</subsys>
<test> </test>
<product>CMN</product>
</header>
<request>
<release>S4711010</release>
<releaseArea>ACCTPAY</releaseArea>
</request>
</message>
</scope>
</service>
...
RLSMAREA START LIST <request>
Data Structure
Subtag | Use | Occurs | Data Type & Length | Values & Dependencies |
---|---|---|---|---|
<release> | Required | 1 | String (8), variable | Release name. |
<releaseArea> | Required | 1 | String (8), variable | Release starting area name. |
RLSMAREA START LIST — Reply
The XML reply to a RLSMAREA START LIST request returns one <result> data element, which contains information for a starting area of a release. The standard <response> data element follows any <result> tags in the reply and indicates the success or failure of the request. Successful requests have a return code of 00. Unsuccessful requests have a return code of 04 or higher.
The following example shows what the reply message might look like. Data structure details for the <result> tag are identical to those for the RLSMAREA SERVICE LIST message - see RLSMAREA SERVICE LIST <result> Data Structure.
Example XML — RLSMAREA START LIST Reply
<?xml version="1.0"?>
<service name="RLSMAREA">
<scope name="START">
<message name="LIST">
<result>
<release>S4711010</release>
<releaseArea>ACCTPAY</releaseArea>
<releaseAreaDesc>Starting area for Accounts Payable components </releaseAreaDesc>
<releaseAreaType>0</releaseAreaType>
<releaseAreaStepNumber>0001</releaseAreaStepNumber>
<releaseNextReleaseArea>FINANCE</releaseNextReleaseArea>
<isReleaseAreaBlocked>N</isReleaseAreaBlocked>
<isReleaseAreaApprovedForCheckin>Y</isReleaseAreaApprovedForCheckin>
<isReleaseAreaApprovedForCheckoff>N</isReleaseAreaApprovedForCheckoff> <isReleaseAreaRejectedForCheckin>N</isReleaseAreaRejectedForCheckin>
<isReleaseAreaRejectedForCheckoff>N</isReleaseAreaRejectedForCheckoff>
<releaseAreaAuditRule>0</releaseAreaAuditRule>
<releaseAreaBlockingRule>0</releaseAreaBlockingRule>
<releaseAreaCheckinRule>0</releaseAreaCheckinRule>
<releaseAreaRetrieveRule>0</releaseAreaRetrieveRule>
<releaseAreaApproveRule>0</releaseAreaApproveRule>
<isReleaseAreaAuditPending>N</isReleaseAreaAuditPending>
<isReleaseAreaCheckinPending>N</isReleaseAreaCheckinPending>
<isReleaseAreaApprovalPending>N</isReleaseAreaApprovalPending>
<isReleaseAreaBlockPending>N</isReleaseAreaBlockPending>
...
<addRelatedApprovers>Y</addRelatedApprovers>
<allowComponentCheckout>Y</allowComponentCheckout>
<excludeAreaFromConcatenation>N</excludeAreaFromConcatenation>
<overrideOverlaidComponent>N</overrideOverlaidComponent>
<bypassAreaTestDevPkg>N</bypassAreaTestDevPkg>
<bypassAreaTestFrzPkg>N</bypassAreaTestFrzPkg>
<bypassAreaTestAprPkg>N</bypassAreaTestAprPkg>
<bypassAreaTestEmptyPkg>N</bypassAreaTestEmptyPkg>
<bypassAreaTestPkgIntg>N</bypassAreaTestPkgIntg>
</result>
<response>
<statusMessage>CMR8700I - Area Information service completed </statusMessage>
<statusReturnCode>00</statusReturnCode>
<statusReasonCode>8700</statusReasonCode>
</response>
</message>
</scope>
</service>
...