RLSMAREA SUMMARY INTEGRTY

The RLSMAREA SUMMARY INTEGRTY message checks the integrity of the component-inmotion (CIM) table against physical members in the release area libraries. This function is similar to the RLSMAREA DETAIL INTEGRTY service; the only difference is that detail information is not returned for each mismatch, only for the first one. Once a mismatch is found, the process stops and an error message is returned.

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

<service name="RLSMAREA">
<scope name="SUMMARY">
<message name="INTEGRTY">

These tags appear in both requests and replies.

RLSMAREA SUMMARY INTEGRTY — Request

The following example shows how you might code a request to check the integrity of a named release. Data structure details for the <request> tag follow the example.

Example XML — RLSMAREA SUMMARY INTEGRTY Request

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="SUMMARY">
        <message name="INTEGRTY">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <release>S4711010</release>
                <releaseArea> </releaseArea>
                <applName>ACTP </applName>
            </request>
        </message>
    </scope>
</service>

RLSMAREA SUMMARY INTEGRTY <request> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<applName>	Required	1	String (4), variable	Release application name.
<release>	Required	1	String (8), variable	Release name.
<releaseArea>	Optional	0 - 1	String (8), variable	Release area name.

RLSMAREA SUMMARY INTEGRTY — Reply

The XML reply to a RLSMAREA SUMMARY INTEGRTY request returns zero to one <result> data elements. If there are no mismatched components, only a <response> data element is returned with a message indicating that the service completed successfully. If a mismatched component is found, a <result> data element is returned for the first mismatch only, followed by a <response> data element.

The following examples show what the reply message might look if a mismatch is found. Data structure details for the <result> tag follow the example.

Example XML — RLSMAREA SUMMARY INTEGRTY Reply

...

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="SUMMARY">
        <message name="INTEGRTY">
            <result>
                <releaseArea>FINANCE</releaseArea>
                <applName>ACTP</applName>
                <libType>CPY</libType>
                <component>ACPCPYCE</component>
                <isCIMMissing>N</isCIMMissing>
                <isMemberMissing>Y</isMemberMissing>
            </result>
            <response>
                <statusMessage>CMR9569I - CIM records and library/file contents do not match</statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>9569</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

...

RLSMAREA SUMMARY INTEGRTY <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	Mismatched component name.
<isCIMMissing>	Optional	0 - 1	String (1)	Y = component is missing from CIM table. N = component exists in CIM table.
<isMemberMissing>	Optional	0 - 1	String (1)	Y = component is missing from release area library. N = component exists in release area library.
<libType>	Optional	0 - 1	String (3)	Component library type.
<release>	Optional	0 - 1	String (8), variable	Release name.
<releaseArea>	Optional	0 - 1	String (8), variable	Release area name.

...