RLSMRLSE REASONS LIST
The RLSMRLSE REASONS LIST message lists backout and revert reasons for a release.
The XML service/scope/message tags and attributes for this message are:
<service name="RLSMRLSE">
<scope name="REASONS">
<message name="LIST">
These tags appear in both requests and replies.
RLSMRLSE REASONS LIST — Request
The following example shows how you might code a request to list backout and revert reasons for a release. Data structure details for the <request> tag follow the example.
Example XML — RLSMRLSE REASONS LIST Request
<?xml version="1.0"?>
<service name="RLSMRLSE">
<scope name="REASONS">
<message name="LIST">
<header>
<subsys>4</subsys>
<test> </test>
<product>CMN</product>
</header>
<request>
<release>S4712COM</release>
</request>
</message>
</scope>
</service>
...
RLSMRLSE REASONS LIST <request>
Data Structure
Subtag | Use | Occurs | Data Type & Length | Values & Dependencies |
---|---|---|---|---|
<fromDate> | Optional | 0 - 1 | Date, yyyymmdd | Start date in desired range of reason update dates. |
<reasonType> | Optional | 0 - 1 | String (1) | Reason type. Values: B = Backout R = Revert |
<release> | Required | 1 | String (8), variable | Release name. |
<siteName> | Optional | 0 - 1 | String (8), variable | Site name. |
<toDate> | Optional | 0 - 1 | Date, yyyymmdd | End date in desired range of reason update dates. |
<updater> | Optional | 0 - 1 | String (8), variable | TSO user ID of last user to back out or revert the release. |
...
RLSMRLSE REASONS LIST — Reply
The XML reply to a RLSMRLSE REASONS LIST request returns zero to many <result> data elements. Each result lists backout/revert reasons for 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 — RLSMRLSE REASONS LIST Reply
<?xml version="1.0"?>
<service name="RLSMRLSE">
<scope name="REASONS">
<message name="LIST">
<result>
<release>S4712COM</release>
<reasonType>B</reasonType>
<siteName>SERT4</siteName>
<updater>KCAMPBE</updater>
<updateDate>20120827</updateDate>
<updateTime>111831</updateTime>
<reasons>BACKOUT RELEASE TO CHANGE COMCPY00 TO COMCPY10</reasons>
<reason01>BACKOUT RELEASE TO CHANGE COMCPY00 TO COMCPY10</reason01>
</result>
<result>
<release>S4712COM</release>
<reasonType>R</reasonType> <siteName>SERT4</siteName>
<updater>KCAMPBE</updater>
<updateDate>20120827</updateDate>
<updateTime>121011</updateTime>
<reasons>REVERT TO CHANGE COMCPY00 TO COMCPY10</reasons>
<reason01>REVERT TO CHANGE COMCPY00 TO COMCPY10</reason01>
</result>
.
.
.
<response>
<statusMessage>CMR8700I - LIST Reasons service completed </statusMessage>
<statusReturnCode>00</statusReturnCode>
<statusReasonCode>8700</statusReasonCode>
</response>
</message>
</scope>
</service>
...
RLSMRLSE REASONS LIST <result>
Data Structure
Subtag | Use | Occurs | Data Type & Length | Values & Dependencies |
---|---|---|---|---|
<reason01> | Optional | 0 - 1 | String (72), variable | Reason line 1. |
<reason02> | Optional | 0 - 1 | String (72), variable | Reason line 2. |
<reason03> | Optional | 0 - 1 | String (72), variable | Reason line 3. |
<reason04> | Optional | 0 - 1 | String (72), variable | Reason line 4. |
<reason05> | Optional | 0 - 1 | String (72), variable | Reason line 5. |
<reason06> | Optional | 0 - 1 | String (72), variable | Reason line 6. |
<reason07> | Optional | 0 - 1 | String (72), variable | Reason line 7. |
<reason08> | Optional | 0 - 1 | String (72), variable | Reason line 8. |
<reason09> | Optional | 0 - 1 | String (72), variable | Reason line 9. |
<reasonType> | Optional | 0 - 1 | String (1) | Reason type. Values: B = Backout R = Revert |
<reasons> | Optional | 0 - 9 | String (72), variable | Reason lines 1 - 9. NOTE: The <reasons> tag is deprecated and contains the same information as <reason01> -- <reason09>. |
<release> | Optional | 0 - 1 | String (8), variable | Release name. |
<siteName> | Optional | 0 - 1 | String (8), variable | Site name. |
<updateDate> | Optional | 0 - 1 | Date, yyyymmdd | Reason update date. |
<updateTime> | Optional | 0 - 1 | Time, hhmmss | Reason update time. |
<updater> | Optional | 0 - 1 | String (8), variable | TSO user ID of user who last updated the reason. |
...