RLSMAREA ALL_NOC SYSLIB

The RLSMAREA ALL_NOC SYSLIB message lists the COPYLIB, LOADLIB, and source concatenation lists for all libraries, including those that are not yet allocated.

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

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

These tags appear in both requests and replies.

RLSMAREA ALL_NOC SYSLIB — Request

The following example shows how you might code a request to list the COPYLIB, LOADLIB, and source concatenation lists for all libraries in a release application. Data structure details for the <request> tag are identical to those for the RLSMAREA ALL_CHK SYSLIB message - see RLSMAREA ALL_CHK SYSLIB <request> Data Structure.

Example XML — RLSMAREA ALL_NOC SYSLIB Request

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

RLSMAREA ALL_NOC SYSLIB — Reply

The XML reply to a RLSMAREA ALL_NOC SYSLIB request returns zero to many <result> data elements. Each result contains SYSLIB data for each library type in 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 are identical to those for the RLSMAREA ALL_CHK SYSLIB message - see RLSMAREA ALL_CHK SYSLIB <result> Data Structure.

Example XML — RLSMAREA ALL_NOC SYSLIB Reply

<?xml version="1.0"?>
<service name="RLSMAREA">
    <scope name="ALL_NOC">
        <message name="SYSLIB">
            <result>
                <release>S4711010</release>
                <releaseArea>ACCTPAY</releaseArea>
                <releaseApplName>ACTP</releaseApplName>
                <libType>LOS</libType>
                <likeType>N</likeType>
                <concatType>L</concatType>
                <libraryFromType>C</libraryFromType>
                <library>CMNTP.S4711010.ACCTPAY.ACTP.LOS</library>
                <libraryOrg>PDS</libraryOrg>
            </result>
            <result>
                <release>S4711010</release>
                <releaseArea>ACCTPAY</releaseArea>
                <releaseApplName>COMM</releaseApplName>
                <libType>LOS</libType>
                <likeType>N</likeType>
                <concatType>L</concatType>
                <libraryFromType>C</libraryFromType>
                <library>CMNTP.S4711010.ACCTPAY.COMM.LOS</library>
                <libraryOrg>PDS</libraryOrg>
            </result>
            <result>
                <release>S4711010</release>
                <releaseArea>FINANCE</releaseArea>
                <releaseApplName>ACTP</releaseApplName>
                <libType>LOS</libType>
                <likeType>N</likeType>
                <concatType>L</concatType>
                <libraryFromType>C</libraryFromType>
                <library>CMNTP.S4711010.FINANCE.ACTP.LOS</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>