RLSMRLSE SITES LIST
The RLSMRLSE SITES LIST service gathers the remote site list by getting the remote site data from all the packages attached to the release. It then combines those lists and returns the release site list.
The XML service/scope/message tags and attributes for this message are:
<service name="RLSMRLSE">
<scope name="SITES">
<message name="LIST">
These tags appear in both requests and replies.
RLSMRLSE SITES LIST — Request
The following example shows how you might code a request to list all of the release site information for a release. Data structure details for the <request> tag follow the example.
Example XML — RLSMRLSE SITES LIST Request
<?xml version="1.0"?>
<service name="RLSMRLSE">
<scope name="SITES">
<message name="LIST">
<header>
<subsys>4</subsys>
<test> </test>
<product>CMN</product>
</header>
<request>
<release>S4712010</release>
</request>
</message>
</scope>
</service>
...
RLSMRLSE SITES LIST <request>
Data Structure
Subtag | Use | Occurs | Data Type & Length | Values & Dependencies |
---|---|---|---|---|
<release> | Required | 1 | String (8), variable | Release name. |
<siteName> | Optional | 0 - 1 | String (8), variable | Site name. |
...
RLSMRLSE SITES LIST — Reply
The XML reply to a RLSMRLSE SITES LIST request returns zero to many <result> data elements. Each result lists dates and contact information for a release site.
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 SITES LIST Reply
<?xml version="1.0"?>
<service name="RLSMRLSE">
<scope name="SITES">
<message name="LIST">
<result>
<release>S4712010</release>
<siteName>SERT4</siteName>
<installDate>20131231</installDate>
<fromInstallTime>080000</fromInstallTime>
<toInstallTime>235900</toInstallTime>
<contactName>Hung Nguyen</contactName>
<contactPhone>808-555-1214</contactPhone>
<alternateContactName>Wenwei Zheng</alternateContactName>
<alternateContactPhone>808-555-1212</alternateContactPhone>
<siteStatus>DEV</siteStatus>
</result>
<response>
<statusMessage>CMR8700I - LIST Sites service completed</statusMessage>
<statusReturnCode>00</statusReturnCode>
<statusReasonCode>8700</statusReasonCode>
</response>
</message>
</scope>
</service>
...
RLSMRLSE SITES LIST <result>
Data Structure
Subtag | Use | Occurs | Data Type & Length | Values & Dependencies |
---|---|---|---|---|
<alternateContactName> | Optional | 0 - 1 | String (25), variable | Alternate analyst name. |
<alternateContactPhone> | Optional | 0 - 1 | String (15), variable | Alternate analyst phone number. |
<contactName> | Optional | 0 - 1 | String (25), variable | Originating analyst name. |
<contactPhone> | Optional | 0 - 1 | String (15), variable | Originating analyst phone number. |
<fromInstallTime> | Optional | 0 - 1 | Time, hhmmss | Start time for installation time range. |
<installDate> | Optional | 0 - 1 | Date, yyyymmdd | Install date. |
<release> | Optional | 0 - 1 | String (8), variable | Release name. |
<siteName> | Optional | 0 - 1 | String (8), variable | Site name. |
<siteStatus> | Optional | 0 - 1 | String (3) | Determined site status. |
<toInstallTime> | Optional | 0 - 1 | Time, hhmmss | End time for installation time range. |
...