RLSMAREA SYSLIB LIST

The RLSMAREA SYSLIB LIST message lists the data that defines a SYSLIB for an application.

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

<service name="RLSMAREA">
<scope name="SYSLIB">
<message name="LIST">

These tags appear in both requests and replies.

RLSMAREA SYSLIB LIST — Request

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

Example XML — RLSMAREA SYSLIB LIST Request

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="SYSLIB">
        <message name="LIST">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <release>S4711010</release>
                <releaseArea>ACCTPAY </releaseArea>
                <releaseApplName> </releaseApplName>
            </request>
        </message>
    </scope>
</service>

RLSMAREA SYSLIB LIST <request> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<release>	Required	1	String (8), variable	Release name.
<releaseApplName>	Optional	0 - 1	String (4), variable	Release application name.
<releaseArea>	Required	1	String (8), variable	Release area name.

RLSMAREA SYSLIB LIST — Reply

The XML reply to a RLSMAREA SYSLIB LIST request returns zero to many <result> data elements. Each result contains SYSLIB information for a 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. The requested release area, ACCTPAY, is a starting area. The reply message lists the ACCTPAY area as well as the system area, FINANCE.

Data structure details for the <result> tag follow the example.

Example XML — RLSMAREA SYSLIB LIST Reply

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="SYSLIB">
        <message name="LIST">
            <result>
                <release>S4711010</release>
                <releaseInstallDate>20131005</releaseInstallDate>
                <releaseInstallTime>000100</releaseInstallTime>
                <releaseHighLevelName>CMNTP</releaseHighLevelName>
                <releaseDsnPattern>HRAPL</releaseDsnPattern>
                <releaseHighLevelPath>/cmntp</releaseHighLevelPath>
                <releaseArea>ACCTPAY</releaseArea>
                <releaseAreaType>0</releaseAreaType>
                <releaseAreaStepNumber>00001</releaseAreaStepNumber>
                <releaseAreaFromType>C</releaseAreaFromType>
                <releaseNextReleaseArea>FINANCE</releaseNextReleaseArea>
            </result>
            <result>
                <release>S4711010</release>
                <releaseInstallDate>20131005</releaseInstallDate>
                <releaseInstallTime>000100</releaseInstallTime>
                <releaseHighLevelName>CMNTP</releaseHighLevelName>
                <releaseDsnPattern>HRAPL</releaseDsnPattern>
                <releaseHighLevelPath>/cmntp</releaseHighLevelPath>
                <releaseArea>FINANCE</releaseArea>
                <releaseAreaType>1</releaseAreaType>
                <releaseAreaStepNumber>00003</releaseAreaStepNumber>
                <releaseAreaFromType>C</releaseAreaFromType>
                <releasePriorReleaseArea>ACCTPAY</releasePriorReleaseArea>
            </result>
            <response>
                <statusMessage>CMR8700I - Application SYSLIB service completed </statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>8700</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

RLSMAREA SYSLIB LIST <result> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<release>	Optional	0 - 1	String (8), variable	Release name.
<releaseApplName>	Optional	0 - 1	String (4), variable	Release application name.
<releaseArea>	Optional	0 - 1	String (8), variable	Release area name.
<releaseAreaFromType>	Optional	0 - 1	String (1)	Release area "from" type. Values: C = Current release area "from" type. P = Prior release area "from" type.
<releaseAreaStepNumber>	Optional	0 - 1	String (5)	Release area step number.
<releaseAreaType>	Optional	0 - 1	String (1)	Release area type. Values: 0 = Subsystem 1 = System
<releaseDsnPattern>	Optional	0 - 1	String (5), variable	Release DSN pattern.
<releaseHighLevelName>	Optional	0 - 1	String (8), variable	Release high-level qualifier.
<releaseHighLevelPath>	Optional	0 - 1	String (40), variable	Release high-level path name.
<releaseInstallDate>	Optional	0 - 1	Date, yyyymmdd	Release install date.
<releaseInstallTime>	Optional	0 - 1	Time, hhmmss	Release install time.
<releaseNextReleaseArea>	Optional	0 - 1	String (8), variable	Next release area name in this release.
<releasePriorReleaseArea>	Optional	0 - 1	String (8), variable	Prior release area name in this release.