Skip to content

RLSMAREA DETAIL TEST

The RLSMAREA DETAIL TEST message tests the contents of a release area against all of the packages that may place a component in that area.

The XML service/scope/message tags and attributes for this message are:

<service name="RLSMAREA">
<scope name="DETAIL"> 
<message name="TEST">

These tags appear in both requests and replies.

RLSMAREA DETAIL TEST — Request

The following example shows how you might code a request to test the contents of a release area. Data structure details for the <request> tag follow the example.

Example XML — RLSMAREA DETAIL TEST Request

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="DETAIL">
        <message name="TEST">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <release>S4711010</release>
                <releaseArea>ACCTPAY </releaseArea>
            </request>
        </message>
    </scope>
</service>

RLSMAREA DETAIL TEST <request> Data Structure

Subtag Use Occurs Data Type & Length Values & Dependencies
<includeExcludePackage> Optional 1 String (1) Include or Exclude package (I/X).
<Package> Optional 1 String (10) Package name.
<release> Required 1 String (8), variable Release name.
<releaseArea> Required 1 String (8), variable Release area name.

RLSMAREA DETAIL TEST — Reply

The XML reply to a RLSMAREA DETAIL TEST request returns zero to many <result> data elements. Each result contains information for a failing component or package.

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. Because it is the final data element in the XML reply message, the <response> tag serves as an end-of-list marker.

The following example shows what the reply message might look like. Data structure details for the <result> tag follow the example.

Example XML — RLSMAREA DETAIL TEST Reply

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="DETAIL">
        <message name="TEST">
            <result>
                <release>S4711010</release>
                <releaseArea>ACCTPAY</releaseArea>
                <package>ACTP000094</package>
                <packageStatus>DEV</packageStatus>
                <reasonCode>E</reasonCode>
                <reasonForFailure>Empty Package</reasonForFailure>
            </result>
            <result>
                <release>S4711010</release>
                <releaseArea>ACCTPAY</releaseArea>
                <package>ACTP000095</package>
                <packageStatus>DEV</packageStatus>
                <reasonCode>E</reasonCode>
                <reasonForFailure>Empty Package</reasonForFailure>
            </result>
            <response>              <statusMessage>CMR1506I - Release S4711010/ACCTPAY and package components do not match.</statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>1506</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

RLSMAREA DETAIL TEST <result> Data Structure

Subtag Use Occurs Data Type & Length Values & Dependencies
<componentName> Optional 0 - 1 String (256), variable Failing component name.
<componentType> Optional 0 - 1 String (3) Failing component type.
<componentUserid> Optional 0 - 1 String (8), variable Failing component user ID.
<originatingPackage> Optional 0 - 1 String (10) Originating package name.
<originatingUserid> Optional 0 - 1 String (8), variable Originating component user ID.
<package> Optional 0 - 1 String (10) Failing package name.
<packageStatus> Optional 0 - 1 String (3) Package status.
<reasonCode> Optional 0 - 1 String (1) Failure reason code.
<reasonForFailure> Optional 0 - 1 String (20) Reason for failure.
<recordType> Optional 0 - 1 String (1) Component record type.
<release> Optional 0 - 1 String (8), variable Release name.
<releaseArea> Optional 0 - 1 String (8), variable Release area name.
<sourceComponentName> Optional 0 - 1 String (256), variable Failing source component name.
<sourceComponentType> Optional 0 - 1 String (3) Failing source component type.