RLSMAPPL SERVICE RELEASE

The RLSMAPPL SERVICE RELEASE message lists release data for each release to which an application is joined.

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

<service name="RLSMAPPL">
<scope name="SERVICE">
<message name="RELEASE">

These tags appear in both requests and replies.

RLSMAPPL SERVICE RELEASE — Request

The following example shows how you might code a request to list release data for an application. Data structure details for the <request> tag follow the example.

Example XML — RLSMAPPL SERVICE RELEASE Request

<?xml version="1.0"?>
<service name="RLSMAPPL">
    <scope name="SERVICE">
        <message name="RELEASE">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <applName>ACTP</applName>
                <release>S4711010</release>
                <releaseParms> </releaseParms>
            </request>
        </message>
    </scope>
</service>

RLSMAPPL SERVICE RELEASE <request> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<applName>	Required	1	String (4), variable	Release application name.
<release>	Required	0 - 1	String (8), variable	Release name.
<releaseParms>	Optional	0 - 1	String (1), variable	Release Parms (A or blank).

...

RLSMAPPL SERVICE RELEASE — Reply

The XML reply to a RLSMAPPL SERVICE RELEASE request returns zero to many <result> data elements. Each <result> contains information for a release to which the application is joined.

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 — RLSMAPPL SERVICE RELEASE Reply

<?xml version="1.0"?>
<service name="RLSMAPPL">
    <scope name="SERVICE">
        <message name="RELEASE">
            <result>
                <release>S4712010</release>
                <applName>ACTP</applName>
                <applDesc>ACTP Accounts Payable (Base ZMF)</applDesc>
                <releaseDesc>Financial Accounting Release S4.V712 \#010</releaseDesc>
                <releaseStatus>DEV</releaseStatus>
                <releaseFromInstallDate>20121005</releaseFromInstallDate>
                <releaseFromInstallTime>000100</releaseFromInstallTime>
                <releaseToInstallDate>20121231</releaseToInstallDate>
                <releaseToInstallTime>235959</releaseToInstallTime>
                <releaseDateCreated>20120312</releaseDateCreated>
                <releaseTimeCreated>123024</releaseTimeCreated>
                <releaseCreator>KCAMPBE</releaseCreator>
                <releaseSchedulerCmn>Y</releaseSchedulerCmn>
                <releaseSchedulerManual>Y</releaseSchedulerManual>
                <releaseSchedulerOther>Y</releaseSchedulerOther>
                <releaseSchedulerType>MANUAL</releaseSchedulerType>
                <applDateJoined>20111005</applDateJoined>
                <applTimeJoined>173838</applTimeJoined>
                <isApplInstalled>N</isApplInstalled>
                <isApplBackedOut>N</isApplBackedOut>
            </result>
            <result>
                <release>S4711010</release>
                <applName>ACTP</applName> <applDesc>ACTP Accounts Payable (Base ZMF)</applDesc>
                <releaseDesc>Financial Accounting Release S4.V711 \#010</releaseDesc>
                <releaseStatus>DEV</releaseStatus>
                <releaseFromInstallDate>20131005</releaseFromInstallDate>
                <releaseFromInstallTime>000100</releaseFromInstallTime>
                <releaseToInstallDate>20131231</releaseToInstallDate>
                <releaseToInstallTime>235959</releaseToInstallTime>
                <releaseDateCreated>20111005</releaseDateCreated>

...

                <releaseTimeCreated>203509</releaseTimeCreated>
                <releaseCreator>KCAMPBE</releaseCreator>
                <releaseSchedulerCmn>Y</releaseSchedulerCmn>
                <releaseSchedulerManual>Y</releaseSchedulerManual>
                <releaseSchedulerOther>Y</releaseSchedulerOther>
                <releaseSchedulerType>MANUAL</releaseSchedulerType>
                <applDateJoined>20111005</applDateJoined>
                <applTimeJoined>173838</applTimeJoined>
                <isApplInstalled>N</isApplInstalled>
                <isApplBackedOut>N</isApplBackedOut> 
            </result> 
.
.
.
            <response>
                <statusMessage>CMR8700I - Appl Release Search service completed </statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>8700</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

RLSMAPPL SERVICE RELEASE <result> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<applDateJoined>	Optional	0 - 1	Date, yyyymmdd	The date that the application was joined to the release.
<applDesc>	Optional	0 - 1	String (72), variable	Application description.
<applName>	Optional	0 - 1	String (4), variable	Application name.
<applTimeJoined>	Optional	0 - 1	Time, hhmmss	The time that the application was joined to the release.
<isApplBackedOut>	Optional	0 - 1	String (1)	Y = Application is backed out. N = Application is not backed out.
<isApplInstalled>	Optional	0 - 1	String (1)	Y = Application is installed. N = Application is not installed.
<release>	Optional	0 - 1	String (8), variable	Release name.
<releaseCreator>	Optional	0 - 1	String (8), variable	The user ID of the person who created the release.
<releaseDateCreated>	Optional	0 - 1	Date, yyyymmdd	The date that the release was created.
<releaseDesc>	Optional	0 - 1	String (72), variable	Release description.
<releaseFromInstallDate>	Optional	0 - 1	Date, yyyymmdd	Start date of the install date range for the release.
<releaseFromInstallTime>	Optional	0 - 1	Time, hhmmss	Start time of the install date/time range for the release.
<ReleaseSchedulerCmn>	Optional	0 - 1	String (1)	Y = Allow CMN internal release scheduler. N = Do not allow CMN internal release scheduler.
<ReleaseSchedulerManual>	Optional	0 - 1	String (1)	Y = Allow manual release scheduler. N = Do not allow manual release scheduler.
<ReleaseSchedulerOther>	Optional	0 - 1	String (1)	Y = Allow other release scheduler. N = Do not allow other release scheduler.
<ReleaseSchedulerType>	Optional	0 - 1	String (8), variable	Scheduler type: CMN = The installation jobs are submitted by the ChangeMan ZMF started task at the scheduled install date and time. Manual = The installation jobs are submitted as soon as the package approvals are complete. Other = The installation jobs are inserted into a third party scheduler via a batch job.
<releaseStatus>	Optional	0 - 1	String (3)	Release status: APR = Approved. BAK = Backed out. BAS = Baselined. BLK = Blocked. DEL = Deleted. DEV = In development. DIS = Distributed. INS = Installed. REJ = Rejected.
<releaseTimeCreated>	Optional	0 - 1	Time, hhmmss	The time that the release was created.
<releaseToInstallDate>	Optional	0 - 1	Date, yyyymmdd	End date of the install date range for the release.
<releaseToInstallTime>	Optional	0 - 1	Time, hhmmss	End time of the install date/time range for the release.