Skip to content

RLSMAREA SERVICE TEST

The RLSMAREA SERVICE TEST message tests the contents of a release area against all of the packages that may place a component in that area. The reply message does not return any data, only a response with a message describing the status of packages and components in the release area.

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

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

These tags appear in both requests and replies.

RLSMAREA SERVICE 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.

Note

Job cards are only required if you are using the auto-cleanup subtags: 

<cleanupComponentFromDiffPkg>
<cleanupEmptyPackage>
<cleanupNotCheckedInComponent>
For example, job cards would be required if an auto-cleanup operation needed to demote a component prior to deletion.

Example XML — RLSMAREA SERVICE TEST Request

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

RLSMAREA SERVICE TEST <request> Data Structure

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

RLSMAREA SERVICE TEST — Reply

The XML reply to a RLSMAREA SERVICE TEST request does not return any <result> data elements. The <response> data element 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 examples show what a reply message might look for a successful and unsuccessful request.

Example XML — RLSMAREA SERVICE TEST Replies

Successful Request

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="SERVICE">
        <message name="TEST">
            <response>
                <statusMessage>CMR1507I - Release S4711010/GENLEDGR and package components match.</statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>1507</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

...

Unsuccessful Request

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="SERVICE">
        <message name="TEST">
            <response>
                <statusMessage>CMR1506I - Release S4711010/ACCTPAY and package components do not match.</statusMessage>
                <statusReturnCode>08</statusReturnCode>
                <statusReasonCode>1506</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

...