Skip to content

RLSMAPPL PROMOTE LIST

The RLSMAPPL PROMOTE LIST message lists release management promotion data for a named release.

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

<service name="RLSMAPPL">
<scope name="PROMOTE">
<message name="LIST">

These tags appear in both requests and replies.

RLSMAPPL PROMOTE LIST — Request

The following example shows how you might code a request to list promotion data for a release. The only required tag is <release>, however, additional tags may be specified to list specific release areas, promotion sites, and so on. Data structure details for the <\request> tag follow the example.

Example XML — RLSMAPPL PROMOTE LIST Request

<?xml version="1.0"?>
<service name="RLSMAPPL">
    <scope name="PROMOTE">
        <message name="LIST">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <release>S4711010</release>
            </request>
        </message>
    </scope>
</service>

...

RLSMAPPL PROMOTE LIST <request> Data Structure

Subtag Use Occurs Data Type & Length Values & Dependencies
<applName> Optional 0 - 1 String (4), variable Release application name.
<promotionLevel> Optional 0 - 1 Integer (2) Release promotion level.
<promotionName> Optional 0 - 1 String (8), variable Release promotion name.
<promotionSiteName> Optional 0 - 1 String (8), variable Release promotion site name.
<release> Required 1 String (8), variable Release name.
<releaseArea> Optional 0 - 1 String (8), variable Release area name.

...

RLSMAPPL PROMOTE LIST — Reply

The XML reply to a RLSMAPPL PROMOTE LIST request returns zero to many <result> data elements. Each <result> tag contains promotion data and status flags for a release area.

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 — RLSMAPPL PROMOTE LIST Reply

<?xml version="1.0"?>
<service name="RLSMAPPL">
    <scope name="PROMOTE">
        <message name="LIST">
            <result>
                <release>S4711010</release>
                <releaseArea>ACCTPAY</releaseArea>
                <applName>ACTP</applName>
                <promotionSiteName>SERT4P1</promotionSiteName>
                <promotionName>S4P1UT</promotionName>
                <promotionLevel>10</promotionLevel>
                <areaBlockedRequired>N</areaBlockedRequired>
                <areaCheckoffApprovedRequired>N</areaCheckoffApprovedRequired>
                <areaDemoteRequiredOnGet>N</areaDemoteRequiredOnGet>
                <areaCheckinApprovedRequired>N</areaCheckinApprovedRequired>
            </result>
            <result>
                <release>S4711010</release>
                <releaseArea>FINANCE</releaseArea>
                <applName>ACTP</applName>
                <promotionSiteName>SERT4P2</promotionSiteName>
                <promotionName>S4P2AT</promotionName>
                <promotionLevel>30</promotionLevel>
                <areaBlockedRequired>N</areaBlockedRequired>
                <areaCheckoffApprovedRequired>N</areaCheckoffApprovedRequired>
                <areaDemoteRequiredOnGet>N</areaDemoteRequiredOnGet>
                <areaCheckinApprovedRequired>N</areaCheckinApprovedRequired>
            </result> 
            .
            .
            .

...

            <response>
                <statusMessage>CMR8700I - Area Promotion service completed</statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>8700</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

...

RLSMAPPL PROMOTE LIST <result> Data Structure

Subtag Use Occurs Data Type & Length Values & Dependencies
<applName> Optional 0 - 1 String (4), variable Release application name.
<areaBlockedRequired> Optional 0 - 1 String (1) Y = Release area block required.
N = Release area block not required.
<areaCheckinApprovedRequired> Optional 0 - 1 String (1) Y = Release area checkin approval required.
N = Release area checkin approval not required.
<areaCheckoffApprovedRequired> Optional 0 - 1 String (1) Y = Release area checkoff approval required.
N = Release area checkoff approval not required.
<areaDemoteRequiredOnGet> Optional 0 - 1 String (1) Y = Demotion required for release area retrieve.
N = Demotion not required for release area retrieve.
<promotionLevel> Optional 0 - 1 Integer (2) Release promotion level.
<promotionName> Optional 0 - 1 String (8), variable Release promotion name.
<promotionSiteName> Optional 0 - 1 String (8), variable Release promotion site name.
<release> Optional 0 - 1 String (8), variable Release name.
<releaseArea> Optional 0 - 1 String (8), variable Release area name.

...

RLSMAPPL SERVICE LIST

The RLSMAPPL SERVICE LIST message lists the application release status for a named release.

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

<service name="RLSMAPPL">
<scope name="SERVICE">
<message name="LIST">

These tags appear in both requests and replies.

RLSMAPPL SERVICE LIST — Request

The following example shows how you might code a request to list the release status for all applications in a named release. Data structure details for the <request> tag follow the example.

Example XML — RLSMAPPL SERVICE LIST Request

<?xml version="1.0"
<service name="RLSMAPPL">
    <scope name="SERVICE">
        <message name="LIST">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <release>S4711010</release>
            </request>
        </message>
    </scope>
</service>

...

RLSMAPPL SERVICE LIST <request> Data Structure

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

RLSMAPPL SERVICE LIST — Reply

The XML reply to a RLSMAPPL SERVICE LIST request returns zero to many <result> data elements. Each <result> contains status flags and other information for an application in the release.

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 — RLSMAPPL SERVICE LIST Reply

<?xml version="1.0"?>
<service name="RLSMAPPL">
    <scope name="SERVICE">
        <message name="LIST">
            <result>
                <release>S4711010</release>
                <applName>ACTP</applName>
                <applDesc>ACTP Accounts Payable (Base ZMF)</applDesc>
                <applDateJoined>20111005</applDateJoined>
                <applTimeJoined>173838</applTimeJoined>
                <isApplInstalled>N</isApplInstalled>
                <isApplBackedOut>N</isApplBackedOut>
                <allApplsRelated>N</allApplsRelated>
                <allReleaseApplsRelated>N</allReleaseApplsRelated>
                <allBaselinesShared>N</allBaselinesShared>
                <isApplLibsDefined>Y</isApplLibsDefined>
                <isApplSyslibsDefined>Y</isApplSyslibsDefined>
                <isApplPromotionDefined>Y</isApplPromotionDefined>
                <relatedApplCount>00001</relatedApplCount>
                <relatedApplName>COMM</relatedApplName>
            </result>
            <response>
                <statusMessage>CMR8700I - Release Application service completed </statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>8700</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

...

RLSMAPPL SERVICE LIST <result> Data Structure

Subtag Use Occurs Data Type & Length Values & Dependencies
<allApplsRelated> Optional 0 - 1 String (1) Y = All base applications are related.
N = All base applications are not related.
<allBaselinesShared> Optional 0 - 1 String (1) Y = All applications share baselines.
N = All applications do not share baselines.
<allReleaseApplsRelated> Optional 0 - 1 String (1) Y = All ERO applications are related.
N = All ERO applications are not related.
<applDateJoined> Optional 0 - 1 Date, yyyymmdd The date that the application was joined to the release.
<applDesc> Optional 0 - 1 String (44), variable Application description.
<applName> Optional 0 - 1 String (4), variable Release application name.
<applTimeJoined> Optional 0 - 1 Time, hhmmss The time that the application was joined to the release.
<isApplBackedOut> Optional 0 - 1 String (1) Y = Application is backed out.
N = Application is not backed out.
<isApplInstalled> Optional 0 - 1 String (1) Y = Application is installed.
N = Application is not installed.
<isApplLibsDefined> Optional 0 - 1 String (1) Y = Application libraries are defined.
N = Application libraries are not defined.
<isApplPromotionDefined> Optional 0 - 1 String (1) Y = Application promotion is defined.
N = Application promotion is not defined.
<isApplSyslibsDefined> Optional 0 - 1 String (1) Y = Application SYSLIBS are defined.
N = Application SYSLIBS are not defined.
<relatedApplCount> Optional 0 - 1 Integer (5) Count of related applications.
<relatedApplName> Optional 0 - 487 String (4), variable Related application name.
<release> Optional 0 - 1 String (8), variable Release name.

...