RLSMAREA ALL_CHK SYSLIB
The RLSMAREA ALL_CHK SYSLIB message lists the COPYLIB, LOADLIB, and source concatenation lists for libraries that are allocated.
The XML service/scope/message tags and attributes for this message are:
<service name="RLSMAREA">
<scope name="ALL_CHK">
<message name="SYSLIB">
These tags appear in both requests and replies.
RLSMAREA ALL_CHK SYSLIB — Request
The following example shows how you might code a request to list the COPYLIB, LOADLIB, and source concatenation lists for allocated libraries in a release application. Data structure details for the <request> tag follow the example.
Example XML — RLSMAREA ALL_CHK SYSLIB Request
<?xml version="1.0"?>
<service name="RLSMAREA">
<scope name="ALL_CHK">
<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_CHK SYSLIB <request>
Data Structure
Subtag | Use | Occurs | Data Type & Length | Values & Dependencies |
---|---|---|---|---|
<buildProc> | Required | 1 | String (8), variable | Release application procedure name. |
<language> | Required | 1 | String (8), variable | Release application language name. |
<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. |
RLSMAREA ALL_CHK SYSLIB — Reply
The XML reply to a RLSMAREA ALL_CHK SYSLIB request returns zero to many <result> data elements. Each result contains SYSLIB data for each allocated 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 follow the example.
Example XML — RLSMAREA ALL_CHK SYSLIB Reply
<?xml version="1.0"?>
<service name="RLSMAREA">
<scope name="ALL_CHK">
<message name="SYSLIB">
<result>
<release>S4711010</release>
<releaseArea>ACCTPAY</releaseArea>
<releaseApplName>ACTP</releaseApplName>
<libType>LOS</libType>
<likeType>N</likeType>
<concatType>L</concatType>
<libraryFromType>B</libraryFromType>
<library>CMNTP.S4.V711.BASE.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>B</libraryFromType>
<library>CMNTP.S4.V711.BASE.COMM.LOS</library>
<libraryOrg>PDS</libraryOrg>
</result>
<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>
...
RLSMAREA ALL_CHK SYSLIB <result>
Data Structure
Subtag | Use | Occurs | Data Type & Length | Values & Dependencies |
---|---|---|---|---|
<concatType> | Optional | 0 - 1 | String (1) | SYSLIB concatenation type. Values: C = Copy L = Load S = Source |
<libType> | Optional | 0 - 1 | String (3), variable | Release application library type. |
<library> | Optional | 0 - 1 | String (1024), variable | Release dataset name. |
<libraryFromType> | Optional | 0 - 1 | String (1) | SYSLIB from type. Values: B = Baseline C = Current P = Prior release S = Staging |
<libraryOrg> | Optional | 0 - 1 | String (4), variable | Release dataset organization. Values: LIB = Librarian LIBA = Librarian archie PAN = Panvalet PDS = PDS PDSE = PDSE |
<likeType> | Optional | 0 - 1 | String (1) | Release application library "like 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. |
<releaseArea> | Optional | 0 - 1 | String (8), variable | Release area name. |
...