Skip to content

RLSMAREA SOURCE SYSLIB

The RLSMAREA SOURCE SYSLIB message lists the source SYSLIB information for a library type in a release application.

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

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

These tags appear in both requests and replies.

RLSMAREA SOURCE SYSLIB — Request

The following example shows how you might code a request to list the source SYSLIB information for a library type in a release application. Data structure details for the <request> tag follow the example.

Example XML — RLSMAREA SOURCE SYSLIB Request

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

RLSMAREA SOURCE SYSLIB <request> Data Structure

Subtag Use Occurs Data Type & Length Values & Dependencies
<libType> Required 1 String (3), variable Release application library type.
<package> Optional 0 - 1 String (10), variable Release application package name.
<release> Required 1 String (8), variable Release name.
<releaseApplName> Required 1 String (4), variable Release application name.
<releaseArea> Required 1 String (8), variable Release area name.
<releaseParms> Optional 1 String (1), variable Release parms C or blank.

RLSMAREA SOURCE SYSLIB — Reply

The XML reply to a RLSMAREA SOURCE SYSLIB request returns one <result> data element, which lists the SYSLIB data for the requested library type 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.

The following example shows what the reply message might look like. Data structure details for the <result> tag are identical to those for the RLSMAREA ALL_CHK SYSLIB message - see RLSMAREA ALL_CHK SYSLIB <result> Data Structure.

Example XML — RLSMAREA SOURCE SYSLIB Reply

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="SOURCE">
        <message name="SYSLIB">
            <result>
                <release>S4711010</release>
                <releaseArea>ACCTPAY</releaseArea>
                <releaseApplName>ACTP</releaseApplName>
                <libType>LOD</libType>
                <likeType>L</likeType>
                <concatType>S</concatType>
                <libraryFromType>B</libraryFromType>
                <library>CMNTP.S4.V711.BASE.ACTP.LOD</library>
                <libraryOrg>PDS</libraryOrg>
            </result>

...

            <response>
                <statusMessage>SER8209I Logon accepted for user MTULLY; Local CCSID=00037 </statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>8700</statusReasonCode>
            </response>
        </message>
    </scope>
</service>