RLSMAPPR GLOBAL LIST

The RLSMAPPR GLOBAL LIST message lists the global approval data for all approval entities or for a named entity.

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

<service name="RLSMAPPR">
<scope name="GLOBAL"> 
<message name="LIST">

These tags appear in both requests and replies.

RLSMAPPR GLOBAL LIST — Request

There is only one subtag (<releaseApprovalEntity>) for this request and it is optional.

Omitting the subtag returns the global approval data for all approval entities. The <request> tag itself is required even if you are omitting the subtag and it may be coded in either of the following ways:

Note

XML syntax allows both a long form and a short form for empty tags. An empty <request> tag can therefore be coded in one of two ways.

Long form:

<request>
</request>

Equivalent short form:

<request/>

The following example shows how you might code a request to list the global data for a specific approval entity. Data structure details for the <request> tag follow the example.

Example XML — RLSMAPPR GLOBAL LIST Request

<?xml version="1.0"?>
<service name="RLSMAPPR">
    <scope name="GLOBAL">
        <message name="LIST">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <releaseApprovalEntity>FINACCTG</releaseApprovalEntity>
            </request>
        </message>
    </scope>
</service>

...

RLSMAPPR GLOBAL LIST <request> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<releaseApprovalEntity>	Optional	0 - 1	String (8), variable	Release approval entity.

RLSMAPPR GLOBAL LIST — Reply

The XML reply to a RLSMAPPR GLOBAL LIST request returns zero to many <result> data elements. Each <result> contains global information for an 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 follow the example.

Example XML — RLSMAPPR GLOBAL LIST Reply

...

<?xml version="1.0"?>
<service name="RLSMAPPR">
    <scope name="GLOBAL">
        <message name="LIST">
            <result>
                <releaseApprovalEntity>FINACCTG</releaseApprovalEntity>
                <releaseApproverDesc>Financial Accounting Manager</releaseApproverDesc>
                <releaseApprovalOrder>0030</releaseApprovalOrder>
                <isApproverRelatedToLibType>N</isApproverRelatedToLibType>
                <isApproverRelatedToRemoteSite>N</isApproverRelatedToRemoteSite>
                <isApproverRelatedToAppl>N</isApproverRelatedToAppl>
                <isReleaseInstallApprover>Y</isReleaseInstallApprover>
                <isReleaseAreaChkInApprover>N</isReleaseAreaChkInApprover>
                <isReleaseAreaChkOffApprover>Y</isReleaseAreaChkOffApprover>
                <isReleaseRelatedApprover>N</isReleaseRelatedApprover>
                <approverListCount>0001</approverListCount> 
                <notificationListLength>00000045</notificationListLength>
                <notification>
                    <notifierType>1</notifierType>
                    <userList>KCAMPBE</userList>
                </notification>
            </result>
            <response>
                <statusMessage>CMR8700I - Global Approvers service completed </statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>8700</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

...

RLSMAPPR GLOBAL LIST <result> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<approverListCount>	Optional	0 - 1	String (4), variable	Number of approver notifications.
<isApproverRelatedToAppl>	Optional	0 - 1	String (1)	Y = Approver is associated with an application. N = Approver is not associated with an application.
<isApproverRelatedToLibType>	Optional	0 - 1	String (1)	Y = Approver is associated with a library type. N = Approver is not associated with a library type.
<isApproverRelatedToRemoteSite>	Optional	0 - 1	String (1)	Y = Approver is associated with a remote site. N = Approver is not associated with a remote site.
<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 a release. N = Approver is not associated with a 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.
<releaseApprovalEntity>	Optional	0 - 1	String (8), variable	Release approval entity.
<releaseApprovalOrder>	Optional	0 - 1	String (4), variable	Hierarchical order of approval notifications.
<releaseApproverDesc>	Optional	0 - 1	String (44), variable	Release approver description.

...