RLSMRLSE LIBRARY LIST

The RLSMRLSE LIBRARY LIST message lists allocated release area libraries.

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

<service name="RLSMRLSE">
<scope name="LIBRARY">
<message name="LIST">

...

These tags appear in both requests and replies.

RLSMRLSE LIBRARY LIST — Request

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

Example XML — RLSMRLSE LIBRARY LIST Request

<?xml version="1.0"?>
<service name="RLSMRLSE">
    <scope name="LIBRARY">
        <message name="LIST">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <release>S4712COM</release>
            </request>
        </message>
    </scope>
</service>

...

RLSMRLSE LIBRARY LIST <request> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<applName>	Optional	- 1	String (4), variable	Release application name. NOTE: May be masked using asterisk (*) wildcard.
<libType>	Optional	- 1	String (3)	Release library type. NOTE: May be masked using asterisk (*) wildcard.
<release>	Required	1	String (8), variable	Release name.
<releaseArea>	Optional	- 1	String (8), variable	Release area name. NOTE: May be masked using asterisk (*) wildcard.

...

RLSMRLSE LIBRARY LIST — Reply

The XML reply to a RLSMRLSE LIBRARY LIST request returns zero to many <result> data elements. Each result lists information for an allocated release area library.

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 — RLSMRLSE LIBRARY LIST Reply

<?xml version="1.0"?>
<service name="RLSMRLSE">
    <scope name="LIBRARY">
        <message name="LIST">
            <result>
                <release>S4712COM</release>
                <releaseArea>ACCTPAY</releaseArea>
                <applName>ACTP</applName>
                <libType>CPY</libType>
                <likeType>CPD</likeType>
                <libraryOrg>PDS</libraryOrg>
                <areaLibrary>CMNTP.S4712COM.ACCTPAY.ACTP.CPY</areaLibrary>
            </result>
            <result>
                <release>S4712COM</release>
                <releaseArea>FINANCE</releaseArea>
                <applName>ACTP</applName>
                <libType>CPY</libType>
                <likeType>CPD</likeType>
                <libraryOrg>PDS</libraryOrg>
                <areaLibrary>CMNTP.S4712COM.FINANCE.ACTP.CPY</areaLibrary>
            </result>
            <result>
                <release>S4712COM</release>
                <releaseArea>GENLEDGR</releaseArea>
                <applName>ACTP</applName>
                <libType>CPY</libType>
                <likeType>CPD</likeType>
                <libraryOrg>PDS</libraryOrg>
                <areaLibrary>CMNTP.S4712COM.GENLEDGR.ACTP.CPY</areaLibrary>
            </result>
            .
            .
            .

...

            <response>
                <statusMessage>CMR8700I - Release Library service completed </statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>8700</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

...

RLSMRLSE LIBRARY LIST <result> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<applName>	Optional	0 - 1	String (4), variable	Release application name.
<areaLibrary>	Optional	0 - 1	String (1024), variable	Release area library dataset name.
<libType>	Optional	0 - 1	String (3)	Release library type.
<libraryOrg>	Optional	0 - 1	String (8), variable	Release library dataset organization. Values: LIB = Librarian OTH = Other PAN = Panvalet PDS = Partitioned dataset SEQ = Sequential VSM = VSAM MIG = Migrate PDSE = Partitioned dataset extended
<likeType>	Optional	0 - 1	String (3)	Release library "like" type. Values: C = Copy L = Load P = PDS S = Source N = NCAL O = Object K = LCT (link control cards X = List J = JCL/Proc
<release>	Optional	0 - 1	String (8), variable	Release name.
<releaseArea>	Optional	0 - 1	String (8), variable	Release area name.

...