RLSMRLSE RLS_LINK LIST

The RLSMRLSE RLS_LINK LIST message lists release management data across a TCP/IP link.

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

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

These tags appear in both requests and replies.

RLSMRLSE RLS_LINK LIST — Request

The following example shows how you might code a request to list release management data across a TCP/IP link. Data structure details for the <request> tag follow the

Example XML — RLSMRLSE RLS_LINK LIST Request

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

RLSMRLSE RLS_LINK LIST <request> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<linkControlItem>	Optional	0 - 1	String (255), variable	Link control item.
<linkRequestor	Optional	0 - 1	String (20), variable	Link requestor.
<release>	Required	1	String (8), variable	Release name.
<sourceLinkIpAddress>	Optional	0 - 1	String (255), variable	Source link IP address.
<sourceLinkPortid>	Optional	0 - 1	String (8), variable	Source link port ID.

...

RLSMRLSE RLS_LINK LIST — Reply

The XML reply to a RLSMRLSE RLS_LINK LIST request returns one <result> data element, which lists information for a linked 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 — RLSMRLSE RLS_LINK LIST Reply

<?xml version="1.0"?>
<service name="RLSMRLSE">
    <scope name="RLS_LINK">
        <message name="LIST">
            <result>
                <release>S4712COM</release>
                <releaseDesc>Financial Accounting Release S4.V712 \#COM</releaseDesc>
                <releaseStatus>BAS</releaseStatus>
                <installFromDate>20120824</installFromDate>
                <installToDate>20121231</installToDate>
            </result>
            <response>
                <statusMessage>CMR8764I - Release S4712COM is not Linked. </statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>8764</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

...

RLSMRLSE RLS_LINK LIST <result> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<approvePermitRequired>	Optional	0 - 1	String (1)	Y = Approve permit is required. N = Approve permit is not required.
<backoutPermitRequired>	Optional	0 - 1	String (1)	Y = Backout permit is required. N = Backout permit is not required.
<blockPermitRequired>	Optional	0 - 1	String (1)	Y = Block permit is required. N = Block permit is not required.
<deletePermitRequired>	Optional	0 - 1	String (1)	Y = Delete permit is required. N = Delete permit is not required.
<demotePermitRequired>	Optional	0 - 1	String (1)	Y = Demote permit is required. N = Demote permit is not required.
<installFromDate>	Optional	0 - 1	Date, yyyymmdd	Install start date.
<installToDate>	Optional	0 - 1	Date, yyyymmdd	Install end date.
<linkControlEventListenerCodePage>	Optional	0 - 1	String (4), variable	Link control event listener code page.
<linkControlItem>	Optional	0 - 1	String (255), variable	Link control item.
<linkDate>	Optional	0 - 1	Date, yyyymmdd	Link date.
<linkRequestor>	Optional	0 - 1	String (20), variable	Link requestor.
<linkTime>	Optional	0 - 1	Time, hhmmss	Link time.
<promotePermitRequired>	Optional	0 - 1	String (1)	Y = Promote permit is required. N = Promote permit is not required.
<rejectPermitRequired>	Optional	0 - 1	String (1)	Y = Reject permit is required. N = Reject permit is not required.
<release>	Optional	0 - 1	String (8), variable	Release name.
<releaseDesc>	Optional	0 - 1	String (72), variable	Release description.
<releaseStatus>	Optional	0 - 1	String (3)	Release status. Values: APR = Approved BAK = Backed out BAS = Baselined BLK = Blocked DEL = Deleted DEV = In development DIS = Distributed INS = Installed REJ = Rejected
<revertPermitRequired>	Optional	0 - 1	String (1)	Y = Revert permit is required. N = Revert permit is not required.
<sourceLinkIpAddress>	Required	1	String (255), variable	Source link IP address.
<sourceLinkPortid>	Required	1	String (8), variable	Source link port ID.
<unblockPermitRequired>	Optional	0 - 1	String (1)	Y = Unblock permit is required. N = Unblock permit is not required.
<undeletePermitRequired>	Optional	0 - 1	String (1)	Y = Undelete permit is required. N = Undelete permit is not required.

...