Cross-Memory Services Regions

Installing Online Interfaces › How to Configure the Online Interfaces Without CA MSM › Install Cross-Memory Services › Cross-Memory Services Regions

Cross-Memory Services Regions

The VTAM and XMS (cross-memory services) interfaces operate in one or more cross-memory online regions.

A cross-memory region can be configured as:

An XMS only region
A VTAM only region
A combination of XMS and VTAM users

Be aware of the following:

Each cross-memory region is configured with the start-up parameters provided on the PARM= of the execute statement, and with an optional SYSIN DD statement.
The REGION= specification determines the maximum number of users supported.
Allow 20 MB (megabytes) for the XMS region plus 1 MB of storage for every two users.

For example, if you specified a REGION of 120 MB, you could specify:

USERMAX=200

If more users are needed, multiple regions can be started under the same SUBSYS= value and will be chained together.

Note: The REGION ID specified in the parameters must be different for each region, and if VTAM interface is used, a different RMOAPPL= name will be needed for each region.

Interface Parameter Requirements

This table lists the optional and required parameters for each interface.

Note: The numbers next to the interface values refer to note references.

Parameter	VTAM	TSO	TSO/ISPF	CA Roscoe	CICS	IMS/DC
CANCEL	Opt. (1)	Opt. (1)	Opt. (1)	Opt. (1)	Opt. (1)	Opt. (1)
LGNFMT	Opt. (2)
LGNSEC	Opt. (3)	Opt. (3)	Opt. (3)	Opt. (3)	Opt. (3)	Opt. (3)
LGNPROP	Opt. (3)	Opt. (3)	Opt. (3)	Opt. (3)	Opt. (3)	Opt. (3)
LONGWAIT	Opt. (1)	Opt. (1)	Opt. (1)	Opt. (1)	Opt. (1)	Opt. (1)
MSGLVL	Opt.	Opt.	Opt.	Opt.	Opt.	Opt.
RMOAPPL	Req.
RMOVTDB	Opt. (4)
SMFSESS	Opt. (5)	Opt. (5)	Opt. (5)	Opt. (5)	Opt. (5)	Opt. (5)
SUBSYS	Opt. (6)	Opt. (6)	Opt. (6)	Opt. (6)	Opt. (6)	Opt. (6)
USERMAX	Req.	Req.	Req.	Req.	Req.	Req.
VTAMPASS	Opt. (7)
VTAMSAA	Opt. (8)
VTMQUERY	Opt. (9)
XMS	Opt. (10)	Opt. (10)	Opt. (10)	Opt. (10)	Opt. (10)	Opt. (10)
XMSSUB		Req. (11)	Req. (11)	Req. (11)		Req. (11)

Notes for the Interface Parameter Requirements Table

The CANCEL= and LONGWAIT= values work together.
We recommend that you set CANCEL=YES and set LONGWAIT to a value appropriate for your site.
LGNFMT= should either not be specified, or it is to be specified as the default (LGNFMT=1), unless your session manager cannot provide logon data in the normal format.
If RMOVTDB= is specified, LGNFMT=1 must be specified; any VTAM logon data will be ignored.
The LGNSEC= and LGNPROP= work together, and require the default RMOUSxUX exit.
If LGNSEC=YES or LGNSEC=YESP is used (to indicate external security signon), the LGNPROP=YES/NO will be used to control whether security violations, database opens and jobs submitted will use the user ID (LGNPROP=YES which is the default) or will use the XMS region's user ID.

It works as follows:
- In the online region, the CA Deliver database is opened before logon, and uses the XMS region's user ID.
The RMOVTDB= only affects VTAM access, and is only to be used when the session manager cannot produce valid LOGON DATA.
For the valid formats supported by CA Deliver, see the LGNFMT= parameter.
The SMFSESS= is to be specified when the user needs to collect user session statistics (CPU, logon/LOGOFF times, storage used, and so on).
The SUBSYS= is only to be specified when you are using a non-default subsystem ID under MVS.
The default is release specific; it does not require JCL/PARM changes when you are converting to a new software release.
VTAMPASS= is only to be specified if you are going to be running a multi-region VTAM interface.
The other VTAM regions must specify the same parameters (LGNFMT= RMOVDTB=, VTMQUERY=, VTAMSAA=), or the interface might react in unpredictable ways.
VTMQUERY= is to be specified either as NORM (normal) or allowed to default to that value.
VTMQUERY=NONE works, but CA Deliver cannot detect color/high-light terminal attributes so color/high-light support will be shut off.

VTAMSAA=NO is to be used if terminals cannot support the SNA QUERY LIST command, such as the older 3270/3290 devices and some older PC/3270 emulators.
XMS=NO is to be used when you are going to be using only the VTAM interface.
XMS=YES (the default) must be used to provide support for these interfaces.
XMSSUB=YES must be specified to provide support for these interfaces.
The XMSSUB=YES must reside in an XMS region with a default SUBSYS= value. If multiple XMS regions are started, only one region can have XMSSUB=YES. The other regions will still be available for user sessions, but their traffic will be routed through the region specifying XMSSUB=YES.

If you terminate the region with XMSSUB=YES, all sessions using the subtask are goint to fail (that is, all TSO/XMS, ISPF/XMS, CA Roscoe/XMS, IMS/DC regions). CICS has router SUBTASK in its region, and does not use the XMSSUB=YES function.
The OVERRIDE parameter is valid for all interfaces and is optional. It might be specified only in the execute statement PARM field and it cannot be coded in the SYSIN data set.
If the parameter is not coded, the default duplicate parameter substitution hierarchy is SYSIN then the EXEC PARM.
- The OVERRIDE parameter determines whether parameters in the execute statement PARM field have precedence over parameters in the SYSIN data set.
- If OVERRIDE is coded in the execute statement PARM field, parameters specified in the execute statement PARM field will override duplicate specifications in the SYSIN data set.
- If OVERRIDE is not coded, parameters specified in the SYSIN data set are used and corresponding parameter specifications in the execute statement PARM field are ignored.
- The OVERRIDE parameter does not have any sub-parameters and it is coded as is in the execute statement PARM field.
- If this parameter is coded in the SYSIN data set, error message "EBCDRV99 OVERRIDE KEYWORD NOT ALLOWED IN SYSIN STATEMENTS - RUN ENDED U0016" is going to be displayed in the XMS job log and XMS will terminate with a return code of 16.