Skip to content

RLSMAREA SCANALL CMP_RLSE

The RLSMAREA SCANALL CMP_RLSE message scans all versions of components in a release concatenation to find those with contents matching a search string. Release area libraries are searched for the current and prior releases, as well as baseline libraries.

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

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

These tags appear in both requests and replies.

RLSMAREA SCANALL CMP_RLSE — Request

The following example shows how you might code a request to scan all versions of components of library type "SRC" that contain the string "SAMCPY1B". Data structure details for the <request> tag are identical to those for the RLSMAREA SCAN CMP_RLSE message - see RLSMAREA SCAN CMP_RLSE <request> Data Structure.

Example XML — RLSMAREA SCANALL CMP_RLSE Request

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="SCANALL">
        <message name="CMP_RLSE">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <release>S4711010</release>
                <releaseArea>ACCTPAY </releaseArea>
                <libType>SRC</libType>
                <scan1>SAMCPY1B </scan1>
            </request>
        </message>
    </scope>
</service>

...

RLSMAREA SCANALL CMP_RLSE — Reply

The XML reply to a RLSMAREA SCANALL CMP_RLSE request returns zero to many <result> data elements. Each result lists information for a component that matched the search string.

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 are identical to those for the RLSMAREA SCAN CMP_RLSE message - see RLSMAREA SCAN CMP_RLSE <result> Data Structure.

Example XML — RLSMAREA SCANALL CMP_RLSE Reply

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="SCANALL">
        <message name="CMP_RLSE">
            <result>
                <release>BASELINE</release>
                <applName>ACTP</applName>
                <component>SAMSRC1A</component>
                <libType>SRC</libType>
                <matchLine> COPY SAMCPY1B.</matchLine>
                <libName>CMNTP.S4.V711.BASE.ACTP.SRC</libName>
            </result>
            <result>
                <release>BASELINE</release>
                <applName>ACTP</applName>
                <component>SAMSRC1A</component>
                <libType>SRC</libType> <matchLine> CALL \&apos;SAMSRS1B&apos; USING SAMCPY1B. </matchLine>
                <libName>CMNTP.S4.V711.BASE.ACTP.SRC</libName>
            </result>
            <response>
                <statusMessage>CMR9572I - Component scan service completed </statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>9572</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

...