Skip to content

RLSMRLSE IMP LIST

The RLSMRLSE IMP LIST message lists the impact data stored in the ERO Db2 impact table.

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

<service name="RLSMRLSE">
<scope name="IMP">
<message name="LIST">

These tags appear in both requests and replies.

RLSMRLSE IMP LIST — Request

There are no required subtags for this request; however, the subtags allow you to request specific releases and component relationships.

The 'source' tags refer to the top level of the relationship and the 'target' tags refer to the bottom level. For example, in a source-to-copybook relationship, the 'source' tags pertain to where the source component was generated; the 'target' fields pertain to where the copybook was pulled from. Similarly, for a composite load-to-subroutine relationship, the 'source' is for the composite and the 'target' is for the subroutine. The <toWhat> tag value is the name of the subcomponent (bottom level component, i.e. copybook or subroutine).

The following example shows how you might code a request to list the impact data for all releases. Data structure details for the <request> tag are identical to those for the RLSMAREA IMP LIST message except that the <sourceRelease> subtag is optional - see RLSMAREA IMP LIST <request> Data Structure.

Example XML — RLSMRLSE IMP LIST Request

<?xml version="1.0"?>
<service name="RLSMRLSE">
    <scope name="IMP">
        <message name="LIST">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
            </request>
        </message>
    </scope>
</service>

RLSMRLSE IMP LIST — Reply

The XML reply to a RLSMRLSE IMP LIST request returns zero to many <result> data elements. Each result lists impact data for a component relationship.

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 IMP LIST message - see RLSMAREA IMP LIST <result> Data Structure.

Example XML — RLSMRLSE IMP LIST Reply

<?xml version="1.0"?>
<service name="RLSMRLSE">
    <scope name="IMP">
        <message name="LIST">
            <result>
                <sourceRelease>S4712COM</sourceRelease>
                <sourceReleaseArea>ACCTPAY</sourceReleaseArea>
                <sourceApplName>COMM</sourceApplName>
                <sourceLibraryType>SRS</sourceLibraryType>
                <sourceLibraryBun>0000000032</sourceLibraryBun>
                <sourceComponent>COMSRS10</sourceComponent>
                <relation>CPY</relation>
                <targetApplName>COMM</targetApplName>
                <targetLibraryType>CPY</targetLibraryType>
                <targetLibraryBun>0000000028</targetLibraryBun>
                <toWhat>COMCPY10</toWhat>
                <hashToken>8C2DCBB800000080</hashToken>
            </result>

...

            <result>
                <sourceRelease>S4712COM</sourceRelease>
                <sourceReleaseArea>ACCTPAY</sourceReleaseArea>
                <sourceApplName>ACTR</sourceApplName>
                <sourceLibraryType>SCS</sourceLibraryType>
                <sourceLibraryBun>0000000024</sourceLibraryBun>
                <sourceComponent>ACRSCSCE</sourceComponent>
                <relation>CPY</relation>
                <targetRelease>S4712COM</targetRelease>
                <targetReleaseArea>ACCTPAY</targetReleaseArea>
                <targetApplName>ACTR</targetApplName>
                <targetLibraryType>CPY</targetLibraryType>
                <targetLibraryBun>0000000017</targetLibraryBun>
                <toWhat>ACRCPYCE</toWhat>
                <hashToken>8FA76F0000000079</hashToken>
            </result>
.
.
.
            <response> 
                <statusMessage>CMR8700I - Release IMP Table service completed </statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>8700</statusReasonCode>
            </response>
        </message>
    </scope>
</service>