Skip to content

RLSMAREA DETAIL CMP_RLSE

The RLSMAREA DETAIL CMP_RLSE message lists all components in a release concatenation and shows all locations where each component resides.

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

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

These tags appear in both requests and replies.

RLSMAREA DETAIL CMP_RLSE — Request

The following example shows how you might code a request to list the LOD library type information for all components in a release area. Data structure details for the <request> tag follow the example.

Example XML — RLSMAREA DETAIL CMP_RLSE Request

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="DETAIL">
        <message name="CMP_RLSE">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <release>S4711010</release>
                <releaseArea>ACCTPAY </releaseArea>
                <applName> </applName>
                <libType>LOD</libType>
                <component> </component>
                <caseMixed> </caseMixed>
            </request>
        </message>
    </scope>
</service>

RLSMAREA DETAIL CMP_RLSE <request> Data Structure

Subtag Use Occurs Data Type & Length Values & Dependencies
<applName> Optional 0 - 1 String (4), variable Release application name.
<caseMixed> Optional 0 - 1 String (1) Y = Case is mixed.
N = Case is not mixed.
<component> Optional 0 - 1 String (256), variable Component name.
NOTE: May be masked using asterisk (*) wildcard.
<libType> Required 1 String (3), variable Release library type.
<listType> Optional 1 String (1) Component list type.
<release> Required 1 String (8), variable Release name.
<releaseArea> Required 1 String (8), variable Release area name.

RLSMAREA DETAIL CMP_RLSE — Reply

The XML reply to a RLSMAREA DETAIL CMP_RLSE request returns zero to many <result> data elements. Each result contains information for a component/library type.

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 CMP_RLSE Reply

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="DETAIL">
        <message name="CMP_RLSE">
            <result>
                <release>BASELINE</release>
                <applName>ACTP</applName>
                <component>ACPSRCCA</component>
                <libType>LOD</libType>
                <likeType>L</likeType>
                <libName>CMNTP.S4.V711.BASE.ACTP.LOD</libName>
            </result>

...

            <result>
                <release>BASELINE</release>
                <applName>ACTP</applName>
                <component>ACPSRCCC</component>
                <libType>LOD</libType>
                <likeType>L</likeType>
                <libName>CMNTP.S4.V711.BASE.ACTP.LOD</libName>
            </result>
            <result>
                <release>BASELINE</release>
                <applName>ACTP</applName>
                <component>ACPSRCCE</component>
                <libType>LOD</libType>
                <likeType>L</likeType>
                <libName>CMNTP.S4.V711.BASE.ACTP.LOD</libName>
            </result>
            .
            .
            .
            <response>
                <statusMessage>CMR9570I - Component list service completed </statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>9570</statusReasonCode>
            </response>
        </message>
    </scope>
</service>
...

RLSMAREA DETAIL CMP_RLSE <result> Data Structure

Subtag Use Occurs Data Type & Length Values & Dependencies
<applName> Optional 0 - 1 String (4), variable Release application name.
<component> Optional 0 - 1 String (256), variable Component name.
<libName> Optional 0 - 1 String (44), variable Library name where component resides.
<libType> Optional 0 - 1 String (3) Component library type.
<likeType> Optional 0 - 1 String (1) Release application library "like type". Values for all library types:
C = Copy
K = LCT (link control cards)
L = Load
N = NCAL
O = Object
Additional values for HFS library types:
P = PDS
S = Source
X = List
blank = other
<release> Optional 0 - 1 String (8), variable Release name.
<releaseArea> Optional 0 - 1 String (8), variable Release area name.
<releaseAreaToCheckinDate> Optional 0 - 1 Date, yyyymmdd Release area component checkin date.
<releaseAreaToCheckinTime> Optional 0 - 1 Time, hhmmss Release area component checkin time.
<sortNumber> Required 1 - 1 Integer, undefined Sort number for sorting list.

...