RLSMAPPR AREA LIST
The RLSMAPPR AREA LIST message lists data for the approval entities in a named release and release area.
The XML service/scope/message tags and attributes for this message are:
<service name="RLSMAPPR">
<scope name="AREA">
<message name="LIST">
These tags appear in both requests and replies.
RLSMAPPR AREA LIST — Request
The following example shows how you might code a request to list the data for all of the approval entities in a release/release area. Data structure details for the <request> tag follow the example.
Example XML — RLSMAPPR AREA LIST Request
<?xml version="1.0"?>
<service name="RLSMAPPR">
    <scope name="AREA">
        <message name="LIST">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <release>S4711010</release>
                <releaseArea>FINANCE </releaseArea>
            </request>
        </message>
    </scope>
</service>
RLSMAPPR AREA 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. | 
| <releaseArea> | Required | 1 | String (8), variable | Release area name. | 
RLSMAPPR AREA LIST — Reply
The XML reply to a RLSMAPPR AREA LIST request returns zero to many <result> data elements. Each <result> contains information for an approval entity in the release/ 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 — RLSMAPPR AREA LIST Reply
<?xml version="1.0"?>
<service name="RLSMAPPR">
    <scope name="AREA">
        <message name="LIST">
            <result>
                <releaseApprovalEntity>ACTPLEAD</releaseApprovalEntity>
                <release>S4711010</release>
                <releaseArea>ACCTPAY</releaseArea>
                <releaseApproverDesc>Financial Accounting Manager</releaseApproverDesc>
                <releaseApprovalOrder>0010</releaseApprovalOrder>
                <isApproverRelatedToLibType>N</isApproverRelatedToLibType>
                <isApproverRelatedToRemoteSite>N</isApproverRelatedToRemoteSite>
                <isApproverRelatedToAppl>N</isApproverRelatedToAppl>
                <isReleaseInstallApprover>N</isReleaseInstallApprover>
                <isReleaseAreaChkInApprover>N</isReleaseAreaChkInApprover>
                <isReleaseAreaChkOffApprover>Y</isReleaseAreaChkOffApprover>
                <isReleaseRelatedApprover>N</isReleaseRelatedApprover>
                <isReleaseApproverNotified>N</isReleaseApproverNotified>
                <releaseApproverListCount>0001</releaseApproverListCount>
                <notificationListLength>00000045</notificationListLength>
                <notification>
                    <notifierType>1</notifierType>
                    <userList>KCAMPBE</userList>
                </notification>
            </result>
            <result>
                <releaseApprovalEntity>ACCTPAY</releaseApprovalEntity>
                <release>S4711010</release>
                <releaseArea>ACCTPAY</releaseArea>
                <releaseApproverDesc>Accounts Payable Manager</releaseApproverDesc>
                <releaseApprovalOrder>0020</releaseApprovalOrder>
                <isApproverRelatedToLibType>N</isApproverRelatedToLibType>
                <isApproverRelatedToRemoteSite>N</isApproverRelatedToRemoteSite>
                <isApproverRelatedToAppl>N</isApproverRelatedToAppl>
                <isReleaseInstallApprover>N</isReleaseInstallApprover>
                <isReleaseAreaChkInApprover>N</isReleaseAreaChkInApprover>
                <isReleaseAreaChkOffApprover>Y</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>
RLSMAPPR AREA LIST <result> Data Structure
| Subtag | Use | Occurs | Data Type & Length | Values & Dependencies | 
|---|---|---|---|---|
| <isApproverRelatedToAppl> | Optional | 0 - 1 | String (1) | Y = Approver is associated with application. N = Approver is not associated with application. | 
| <isApproverRelatedToLibType> | Optional | 0 - 1 | String (1) | Y = Approver is associated with library type. N = Approver is not associated with library type. | 
| <isApproverRelatedToRemoteSite> | Optional | 0 - 1 | String (1) | Y = Approver is associated with remote site. N = Approver is not associated with remote site. | 
| <isReleaseApprovedOrRejected> | Optional | 0 - 1 | String (1) | A = Release area is approved. R = Release area is rejected. | 
| <isReleaseApproverNotified> | Optional | 0 - 1 | String (1) | Y = Approver is notified. N = Approver is not notified. | 
| <isReleaseAreaChkInApprover> | Optional | 0 - 1 | String (1) | Y = Release area checkin approver. N = Not a release area checkin approver. | 
| <isReleaseAreaChkOffApprover> | Optional | 0 - 1 | String (1) | Y = Release area check-off approver. N = Not a release area check-off approver. | 
| <isReleaseInstallApprover> | Optional | 0 - 1 | String (1) | Y = Release install approver. N = Not a release install approver. | 
| <isReleaseRelatedApprover> | Optional | 0 - 1 | String (1) | Y = Approver is associated with release. N = Approver is not associated with release. | 
| <notification> | Optional | 0 - 40 | Complex | Notification vehicle and list of users to receive messages. Each occurrence contains the following subtags: <notifierType> <userList>). | 
| <notifierType> | Optional | 0 - 1 | String (1) | Method used for sending messages. Subtag of <notification>. 1 = MVS/TSO send (MVSSEND) 4 = Email via SMTP (EMAIL) 5 = Email via Sernet and ECP web server (SERNET) 6 = Batch job (BATCH) | 
| <userList> | Optional | 0 - 1 | String (44), variable | List of user IDs to be notified. Subtag of <notification>. | 
| <notificationListLength> | Optional | 0 - 1 | String (8), variable | Length of <notification> tag group. | 
| <reasons> | Optional | 0 - 10 | String (72), variable | Release reject reasons. | 
| <release> | Optional | 0 - 1 | String (8), variable | Release name. | 
| <releaseApprovalEntity> | Optional | 0 - 1 | String (8), variable | Release approval entity. | 
| <releaseApprovalOrder> | Optional | 0 - 1 | String (4), variable | Hierarchical order of approver notifications. | 
| <releaseApproverDesc> | Optional | 0 - 1 | String (44), variable | Release approver description. | 
| <releaseApproverListCount> | Optional | 0 - 1 | String (4), variable | Number of approver notifications. | 
| <releaseApproverUserid> | Optional | 0 - 1 | String (8), variable | User ID of user who approved/rejected release. | 
| <releaseArea> | Optional | 0 - 1 | String (8), variable | Release area name. | 
| <releaseDateApproved> | Optional | 0 - 1 | Date, yyyymmdd | Release approved/rejected date. | 
| <releaseTimeApproved> | Optional | 0 - 1 | Time, hhmmss | Release approved/rejected time. |