RLSMLTYP BUN LIST

The RLSMLTYP BUN LIST message lists information from the release BUN library-type table.

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

<service name="RLSMLTYP">
<scope name="BUN">
<message name="LIST">

These tags appear in both requests and replies.

RLSMLTYP BUN LIST — Request

The following example shows how you might code a request to list information from the BUN library-type table for a named application. Data structure details for the <request> tag follow the example.

Example XML — RLSMLTYP BUN LIST Request

<?xml version="1.0"?>
<service name="RLSMLTYP">
    <scope name="BUN">
        <message name="LIST">
            <header>
                <subsys>4</subsys>
                <test> </test>
                <product>CMN</product>
            </header>
            <request>
                <applName>ACTP</applName>
            </request>
        </message>
    </scope>
</service>

RLSMLTYP BUN LIST <request> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<applName>	Optional	0 - 1	String (4), variable	Application name in BUN table.
<baseLib>	Optional	0 - 1	String (44), variable	Baseline library dataset name.
<bunNumber>	Optional	0 - 1	Integer (10)	Baseline unique number.
<libType>	Optional	0 - 1	String (3)	Library type in BUN table.
<libTypeLike>	Optional	0 - 1	String (3)	Library "like" type (for example CPY).
<likeType>	Optional	0 - 1	String (1)	Component type attribute which determines how a component is processed. C = Copy L = Load P = PDS S = Source N = NCAL O = Object K = LCT (link control cards X = List J = JCL/Proc

RLSMLTYP BUN LIST — Reply

The XML reply to a RLSMLTYP BUN LIST request returns zero to many <result> data elements. Each result lists information about a library type.

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 examples show what the reply message might look like. Data structure details for the <result> tag follow the example.

Example XML — RLSMLTYP BUN LIST Reply

<?xml version="1.0"?>
<service name="RLSMLTYP">
    <scope name="BUN">
        <message name="LIST">
            <result>
                <applName>ACTP</applName>
                <libType>CPY</libType>
                <likeType>C</likeType>
                <libTypeLike>CPY</libTypeLike>
                <bunNumber>0000000001</bunNumber>
                <baseLib>CMNTP.S4.V711.BASE.ACTP.CPY</baseLib>
            </result>
            <result>
                <applName>ACTP</applName>
                <libType>CTC</libType>
                <likeType>P</likeType>
                <libTypeLike>PDS</libTypeLike>
                <bunNumber>0000000002</bunNumber>
                <baseLib>CMNTP.S4.V711.BASE.CTC</baseLib>
            </result>
            <result>
                <applName>ACTP</applName>
                <libType>DOC</libType>
                <likeType>P</likeType>
                <libTypeLike>PDS</libTypeLike>
                <bunNumber>0000000003</bunNumber>
                <baseLib>CMNTP.S4.V711.BASE.ACTP.DOC</baseLib>
            </result> 
.
.
.
            <response>
                <statusMessage>CMR8700I - Release BUN Table service completed </statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>8700</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

RLSMLTYP BUN LIST <result> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<applName>	Optional	0 - 1	String (4), variable	Application name in BUN table.
<baseLib>	Optional	0 - 1	String (44), variable	Baseline library dataset name.
<bunNumber>	Optional	0 - 1	Integer (10)	Baseline unique number.
<libType>	Optional	0 - 1	String (3)	Library type in BUN table.
<libTypeLike>	Optional	0 - 1	String (3)	Library "like" type (for example CPY).
<likeType>	Optional	0 - 1	String (1)	Component type attribute which determines how a component is processed. C = Copy L = Load P = PDS S = Source N = NCAL O = Object K = LCT (link control cards X = List J = JCL/Proc