Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
RMODE: Residence mode option z/OS MVS Program Management: User's Guide and Reference SA23-1393-00 |
|
To assign the residence mode for all the entry points into a program
module, you can code the RMODE parameter as follows:
RMODE=({MIN | 24 | ANY | 31 [, INITIAL | COMPAT]}) RMODE(SPLIT) The residence mode assigned in the PARM field is overridden by a residence mode assigned in the MODE control statement, but overrides the accumulated residence mode found in the ESD data for the control sections or private code in the input. AMODE and RMODE values are specified independently, but checked for conflicts before output processing occurs. See AMODE and RMODE combinations for information on AMODE and RMODE compatibility and the setting of default values. In addition to the residence mode value, you may optionally specify
a scope. The scope determines
how the residence mode value is applied. The allowable scope values
are:
Note: The scope may not be specified
with RMODE(SPLIT).
RMODE(SPLIT) specifies the program text (class B_TEXT) can be split
into two class segments according to the RMODE of each section. Rules
for splitting the text are:
When an RMODE(SPLIT) module is loaded, the LOAD service returns a length of zero. For additional information on multiple segment modules, see Creating a program object. When you use LOAD, the CSVQUERY service should be used with the OUTXTLST parameter to obtain information about the address (load point) and length of each program segment. See CSVQUERY in z/OS MVS Programming: Assembler Services Guide for more information. The keyword RMODE can be specified as RMOD for options strings (such as IEWL PARM or options files). |
Copyright IBM Corporation 1990, 2014
|