RLSMAREA DETAIL INTEGRTY

The RLSMAREA DETAIL INTEGRTY message checks the integrity of the component-inmotion (CIM) table against physical members in the release area libraries. All versions of all components in the release concatenation are checked.

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

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

These tags appear in both requests and replies.

RLSMAREA DETAIL 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 DETAIL INTEGRTY Request

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="DETAIL">
        <message name="INTEGRTY">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <applName>ACTR </applName>
                <release>S4712COM</release>
            </request>
        </message>
    </scope>
</service>

RLSMAREA DETAIL 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 DETAIL INTEGRTY — Reply

The XML reply to a RLSMAREA DETAIL INTEGRTY request returns zero to many <result> data elements. Each result contains information for a mismatched component.

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

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="DETAIL">
        <message name="INTEGRTY">
            <result>
                <release>S4712COM</release>
                <releaseArea>FINANCE</releaseArea>
                <applName>ACTR</applName>
                <libType>CPY</libType>
                <component>ACRCPYCE</component>
                <isCIMMissing>N</isCIMMissing>
                <isMemberMissing>Y</isMemberMissing>
            </result>
            <result>
                <release>S4712COM</release>
                <releaseArea>ACCTPAY</releaseArea>
                <applName>ACTR</applName>
                <libType>CPY</libType>
                <component>ACRCPYCE</component>
                <isCIMMissing>N</isCIMMissing>
                <isMemberMissing>Y</isMemberMissing>
            </result>
            <result>
                <release>S4712COM</release>
                <releaseArea>FINANCE</releaseArea>
                <applName>ACTR</applName>
                <libType>LCS</libType>
                <component>ACRSCSCE</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 DETAIL 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.