RLSMAPPL SYSLIB LIST

The RLSMAPPL SYSLIB LIST message lists SYSLIB data for release applications.

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

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

These tags appear in both requests and replies.

RLSMAPPL SYSLIB LIST — Request

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

Example XML — RLSMAPPL SYSLIB LIST Request

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

RLSMAPPL SYSLIB LIST <request> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<buildProc>	Optional	0 - 1	String (8), variable	SYSLIB procedure name.
<language>	Optional	0 - 1	String (8), variable	SYSLIB language name.
<libType>	Optional	0 - 1	String (3), variable	SYSLIB release library type.
<release>	Required	1	String (8), variable	Release name.
<releaseApplName>	Optional	0 - 1	String (4), variable	Release application name.

RLSMAPPL SYSLIB LIST — Reply

The XML reply to a RLSMAPPL SYSLIB LIST request returns zero to many <result> data elements. Each <result> contains SYSLIB data for a release application.

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 SYSLIB LIST Reply

<?xml version="1.0"?>
<service name="RLSMAPPL">
    <scope name="SYSLIB">
        <message name="LIST">
            <result>
                <release>S4711010</release>
                <releaseApplName>ACTP</releaseApplName>
                <language>COBOL2</language>
                <buildProc>CMNCOB2</buildProc>
                <libType>LCT</libType>
                <likeType>K</likeType>
                <isHfsLibType>N</isHfsLibType>
                <applLibTypeCount>00002</applLibTypeCount>
                <libTypeList>
                    <relatedLibType>LOD</relatedLibType>
                    <libTypeOrderNumber>00000</libTypeOrderNumber>
                </libTypeList>
                <libTypeList>
                    <relatedLibType>LOS</relatedLibType>
                    <libTypeOrderNumber>00000</libTypeOrderNumber>
                </libTypeList>
            </result>

...

            <result>
                <release>S4711010</release>
                <releaseApplName>ACTP</releaseApplName>
                <language>COBOL2</language>
                <buildProc>CMNCOB2</buildProc>
                <libType>LOD</libType>
                <likeType>L</likeType>
                <isHfsLibType>N</isHfsLibType>
                <applLibTypeCount>00001</applLibTypeCount>
                <libTypeList>
                    <relatedLibType>LOS</relatedLibType>
                    <libTypeOrderNumber>00010</libTypeOrderNumber>
                </libTypeList>
            </result> 
.
.
.
            <response>
                <statusMessage>CMR8700I - Application SYSLIB service completed </statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>8700</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

RLSMAPPL SYSLIB LIST <result> Data Structure

Subtag	Use	Occurs	Data Type & Length	Values & Dependencies
<applLibTYpeCount>	Optional	0 - 1	String (5), variable	Count of related application library types.
<buildProc>	Optional	0 - 1	String (8), variable	SYSLIB procedure name.
<isHfsLibType>	Optional	0 - 1	String (1)	Y = SYSLIB library type is HFS. N = SYSLIB library type is not HFS.
<language>	Optional	0 - 1	String (8), variable	SYSLIB language name.
<libType>	Optional	0 - 1	String (3), variable	SYSLIB library type.
<libTypeList>	Optional	0 - 48	Complex	Related library type information. Each occurrence contains the following subtags: <relatedLibType> <libTypeOrderNumber>
<relatedLibType>	Optional	0 - 1	String (3), variable	Related library type. Subtag of <libTypeList>.
<libTypeOrderNumber>	Optional	0 - 1	Integer	Order number of related library type. Subtag of <libTypeList>.
<likeType>	Optional	0 - 1	String (1)	"Like Type" of SYSLIB library type. Values for all library types: C = Copy K= LCT (link control cards) L= Load N= NCAL O= Object Additional values for HFS library types: P = PDS S = Source X = List blank = other
<release>	Optional	0 - 1	String (8), variable	Release name.
<releaseApplName>	Optional	0 - 1	String (4), variable	Release application name.

...