Skip to content

RLSMRLSE SERVICE TEST

The RLSMRLSE SERVICE TEST message tests the contents of a release against all of the packages that may place a component in that release. The reply message does not return any data, only a response indicating success or failure.

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

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

These tags appear in both requests and replies.

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

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 — RLSMRLSE SERVICE TEST Request

<?xml version="1.0"?>
<service name="RLSMRLSE">
    <scope name="SERVICE">
        <message name="TEST">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <release>S4712COM</release>
            </request>
        </message>
    </scope>
</service>

...

RLSMRLSE SERVICE TEST <request> Data Structure

Subtag Use Occurs Data Type & Length Values & Dependencies
<cleanupComponentFromDiffPkg> Optional - 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 - 1 String (1) Y = Automatically cleanup empty packages.
N = Do not cleanup empty packages.
<cleanupNotCheckedInComponent> Optional - 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> Optional - 1 String (72), variable Job card 1.
<jobCard02> Optional - 1 String (72), variable Job card 2.
<jobCard03> Optional - 1 String (72), variable Job card 3.
<jobCard04> Optional 0 - 1 String (72), variable Job card 4.
<jobCards> Optional 0 - 4 String (72), variable Deprecated. Use tags <jobCard01> through <jobCard04> instead.
<release> Required 1 String (8), variable Release name.

...

RLSMRLSE SERVICE TEST — Reply

The XML reply to a RLSMRLSE 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 — RLSMRLSE SERVICE TEST Replies

Successful Request

<?xml version="1.0"?>
<service name="RLSMRLSE">
    <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="RLSMRLSE">
    <scope name="SERVICE">
        <message name="TEST">
            <response>
                <statusMessage>CMR0001A - Invalid Release status BAS, S4712COM must be in DEV,BLK,APR,REJ status.</statusMessage>
                <statusReturnCode>08</statusReturnCode>
                <statusReasonCode>0001</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

...