RLSMAPPR RELEASE LIST
The RLSMAPPR RELEASE LIST message lists the data for install approval entities for a named release.
The XML service/scope/message tags and attributes for this message are:
<service name="RLSMAPPR">
<scope name="RELEASE">
<message name="LIST">
These tags appear in both requests and replies.
RLSMAPPR RELEASE LIST — Request
The following example shows how you might code a request to list the data for all of the install approvers for a release. Data structure details for the <request> tag follow the example.
Example XML — RLSMAPPR RELEASE LIST Request
<?xml version="1.0"?>
<service name="RLSMAPPR">
<scope name="RELEASE">
<message name="LIST">
<header>
<subsys>4</subsys>
<test> </test>
<product>CMN</product>
</header>
<request>
<release>S4711010</release>
</request>
</message>
</scope>
</service>
RLSMAPPR RELEASE LIST <request>
Data Structure
Subtag | Use | Occurs | Data Type & Length | Values & Dependencies |
---|---|---|---|---|
<release> | Required | 1 | String (8), variable | Release name. |
<releaseApprovalEntity> | Optional | 0 - 1 | String (8), variable | Release approval entity. |
RLSMAPPR RELEASE LIST — Reply
The XML reply to a RLSMAPPR RELEASE LIST request returns zero to many <result> data elements. Each <result> contains information for an install approval entity.
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 RLSMAPPR AREA LIST message except that there is no <releaseArea> tag - see RLSMAPPR AREA LIST <request> Data Structure.
Example XML — RLSMAPPR RELEASE LIST Reply
<?xml version="1.0"?>
<service name="RLSMAPPR">
<scope name="RELEASE">
<message name="LIST">
<result>
<releaseApprovalEntity>FINACCTG</releaseApprovalEntity>
<release>S4711010</release>
<releaseApproverDesc>Financial Accounting Manager</releaseApproverDesc>
<releaseApprovalOrder>0030</releaseApprovalOrder>
<isApproverRelatedToLibType>N</isApproverRelatedToLibType>
<isApproverRelatedToRemoteSite>N</isApproverRelatedToRemoteSite>
<isApproverRelatedToAppl>N</isApproverRelatedToAppl>
<isReleaseInstallApprover>Y</isReleaseInstallApprover>
<isReleaseAreaChkInApprover>N</isReleaseAreaChkInApprover>
<isReleaseAreaChkOffApprover>N</isReleaseAreaChkOffApprover>
<isReleaseRelatedApprover>N</isReleaseRelatedApprover>
<isReleaseApproverNotified>N</isReleaseApproverNotified>
<releaseApproverListCount>0001</releaseApproverListCount>
<notificationListLength>00000045</notificationListLength>
<notification>
<notifierType>1</notifierType>
<userList>KCAMPBE</userList>
</notification>
</result>
<result>
<releaseApprovalEntity>RLSEMNGR</releaseApprovalEntity>
<release>S4711010</release>
<releaseApproverDesc>Release Manager</releaseApproverDesc>
<releaseApprovalOrder>0030</releaseApprovalOrder>
<isApproverRelatedToLibType>N</isApproverRelatedToLibType>
<isApproverRelatedToRemoteSite>N</isApproverRelatedToRemoteSite>
<isApproverRelatedToAppl>N</isApproverRelatedToAppl>
<isReleaseInstallApprover>Y</isReleaseInstallApprover>
<isReleaseAreaChkInApprover>N</isReleaseAreaChkInApprover>
<isReleaseAreaChkOffApprover>N</isReleaseAreaChkOffApprover>
<isReleaseRelatedApprover>N</isReleaseRelatedApprover>
<isReleaseApproverNotified>N</isReleaseApproverNotified>
<releaseApproverListCount>0001</releaseApproverListCount>
<notificationListLength>00000045</notificationListLength>
<notification>
<notifierType>1</notifierType>
<userList>KCAMPBE</userList>
</notification>
</result>
.
.
.
<response>
<statusMessage>CMR8700I - LIST Approver service completed</statusMessage>
<statusReturnCode>00</statusReturnCode>
<statusReasonCode>8700</statusReasonCode>
</response>
</message>
</scope>
</service>
...