RLSMRLSE DETAIL TEST
The RLSMRLSE DETAIL TEST message tests the contents of a release against all of the packages that may place a component in that release. Only the final area of a release is tested.
The XML service/scope/message tags and attributes for this message are:
<service name="RLSMRLSE">
<scope name="DETAIL">
<message name="TEST">
These tags appear in both requests and replies.
RLSMRLSE DETAIL TEST — Request
The following example shows how you might code a request to test the contents of a release. Data structure details for the <request> tag follow the example.
Example XML — RLSMRLSE DETAIL TEST Request
<?xml version="1.0"?>
<service name="RLSMRLSE">
    <scope name="DETAIL">
        <message name="TEST">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <release>S4711010</release>
            </request>
        </message>
    </scope>
</service>
...
RLSMRLSE DETAIL TEST <request> Data Structure
| Subtag | Use | Occurs | Data Type & Length | Values & Dependencies | 
|---|---|---|---|---|
| <cleanupComponentFromDiffPkg> | Optional | 0 - 1 | String (1) | Y = If different versions of a component exist in different packages, the version not checked into the release will be deleted from the package. N = Do not delete components with different versions. | 
| <cleanupEmptyPackage> | Optional | 0 - 1 | String (1) | Y = Automatically cleanup empty packages. N = Do not cleanup empty packages. | 
| <cleanupNotCheckedInComponent> | Optional | 0 - 1 | String (1) | Y = Automatically cleanup components that were not checked into release. N = Do not cleanup components that were not checked into release. | 
| <jobCard01> | Required | 1 | String (72), variable | Job card 1 | 
| <jobCard02> | Required | 1 | String (72), variable | Job card 2 | 
| <jobCard03> | Required | 1 | String (72), variable | Job card 3 | 
| <jobCard04> | Required | 1 | String (72), variable | Job card 4 | 
| <release> | Required | 1 | String (8), variable | Release name. | 
...
RLSMRLSE DETAIL TEST — Reply
The XML reply to a RLSMRLSE 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 — RLSMRLSE DETAIL TEST Reply
<?xml version="1.0"?>
<service name="RLSMRLSE">
    <scope name="DETAIL">
        <message name="TEST">
            <result>
                <release>S4711010</release>
                <releaseArea>FINANCE</releaseArea>
                <package>ACTP000094</package>
                <packageStatus>DEV</packageStatus>
                <reasonCode>E</reasonCode>
                <reasonForFailure>Empty Package</reasonForFailure>
            </result>
            <result>
                <release>S4711010</release>
                <releaseArea>FINANCE</releaseArea>
                <package>ACTP000095</package>
                <packageStatus>DEV</packageStatus>
                <reasonCode>E</reasonCode>
                <reasonForFailure>Empty Package</reasonForFailure>
...
            </result>
            <response>
                <statusMessage>CMR1506I - Release S4711010/FINANCE and package components do not match.</statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>1506</statusReasonCode>
            </response>
        </message>
    </scope>
</service>
...
RLSMRLSE 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. | 
...