Installing the Online Interfaces › How to Configure the Online Interfaces Without CA CSM › Install the Cross-Memory Services › Step 1: Add the Start Procedure for the Cross-Memory Online Task › Start Procedure Parameters

Start Procedure Parameters

XMSSYS01 (in the PARM statement) specifies the one- to eight-character REGIONID. The REGIONID is positional—it must be the first value of the PARM= statement.

This value is used to define separate cross-memory regions attached to one MVS subsystem (specified by the SUBSYS parameter).

Note: Each separate SARXMS region has its own REGIONID. We suggest using the PROC name of the cross-memory-started task.

CANCEL=YES|NO

Indicates one of the following:

• CANCEL=YES specifies that a user who is inactive (no commands entered) for the time specified by the LONGWAIT parameter will be canceled, and the session will be terminated. With CANCEL=YES, all users are automatically canceled if the region is shut down by an operator command.
• CANCEL=NO specifies that the connection is not to be canceled, and the user status changes to LONGWAIT.

Default: NO

LGNFMT=n

Specifies the format of the data parameter when logging on to a VTAM region where n is a digit (1 through 3), as follows:

1 database//userid/password/newpass

2 userID/password/newpass/database/mode

3 database/mode

Default: 1.

LGNPROP=YES|NO

Indicates whether the CA View user ID is to be passed to MVS for propagation during submit processing.

This parameter is only valid if LGNSEC=YES is specified.

Default: YES.

LGNSEC=YES|NO|PASSWORD|YESP

Indicates whether there will be RACROUTE security checking.

LGNSEC must be YES or YESP if you are accessing a database that has the CA View initialization parameter SECURITY=EXTERNAL specified.

Modifications to default logon exit (SARUSXUX) is not required to implement external security. This exit is only provided so that you can customize the exit to provide any necessary functionality.

For example, to access external security packages directly, without SAF, you must modify and install the SARUSXUX user exit.

These values for LGNSEC are effective when the default exits are implemented:

Value

Result

YES

External security checking is performed using SAF calls.

External security verifies userid only for all cross-memory interfaces (with no interruption to the user).

A panel is presented to the user to verify userid and password.

Note: This panel is only presented when the user interface does not automatically send the userid to the XMS region.

Because the password is not forwarded, RACF or CA ACF2R Security (eTrust CA-ACF2) requires additional specifications. For RACF or CA ACF2, see Bypassing Password Verification in the chapter "Security" in the Reference Guide for implementation instructions.

NO

No SAF call to external security is performed.

The user ID is checked internally against CA View definitions.

If no match is found, CA View might or might not dynamically create a user ID depending on the value of your DEFMODE initialization parameter.

Review your DEFMODE values to be sure that they are appropriate.

PASSWORD

No call to external security is performed.

Internally, userid and password are verified.

YESP

External security checking is performed using SAF calls.

External security verifies userid and password for all cross-memory interfaces (with no interruption to the user).

A panel is presented to the user to verify the userid and password. This panel is only presented when the user interface does not automatically send the userid and password to the XMS region.

Default: NO.

LONGWAIT=nn

Specifies the number of minutes of inactivity (no commands entered) before a user's session is terminated.

The CANCEL parameter must be YES to terminate the session.

Default: 15.

MSGLVL=CRIT|ACTN|NORM|INFO|TRCE

Indicates the level of message to be written to the started task job log.

Unless they are suppressed, the CRITICAL and ACTION messages are written to the console. These settings cause the following types of messages to be written:

Setting Message

CRIT Only critical messages

ACTN Only critical and action messages

NORM Only critical, action, and normal messages

INFO All but trace messages

TRCE All messages

Default: NORM.

Note: This parameter does not suppress messages from the SYSPRINT log.

SARAPPL=applname

Specifies the SARVTAM APPLID which provides the VTAM user signon capability

Default: SARVTAM.

SARVTDB=high-level.databasename

Specifies that this database high-level qualifier must be used by all SARVTAM interface users

Typically, you would not specify this value and allow the user to specify which database to access when the user logs on. When this parameter is specified, any database specified at logon time with the VTAM logon command is ignored.

SMFSESS=nnn

Specifies whether SMF records are going to be collected for the cross-memory sessions.

The EBCSMFU1 macro documents the records available.

Default: zero—no record collection.

SUBSYS=name

Specifies the four-character MVS subsystem.

This value must match the value in the EC1XMCTR table.

Default: XMC1.

Note: The SUBSYS parameter does not apply to VTAM or IMS interface users.

USERMAX=nn

Specifies the maximum number of sessions to be allowed.

Default: 10.

VGRAPPL=name

Indicates the one- to eight-character generic resource name to be used to log on to VTAM cross memory regions.

VGRAPPL is only valid when specified with the SARAPPL parameter.

Default: None.

For more information, see the Reference Guide.

VTAMPASS=YES|NO

Indicates whether signon requests can be passed to other regions in this subsystem when this region cannot accept the request.

Possible reasons for not being able to accept a signon request are that the USERMAX parameter has been exceeded, or a SUSPEND operator command has been issued.

If VTAMPASS=YES is specified, include PASS in the AUTH value on the APPL statement in the VTAM definition. If you want to run multiple regions, VTAMPASS must be YES.

Default: NO.

VTMQUERY=ALL|NORM|NONE

Indicates whether the VTAM interface will QUERY terminals with dynamic log modes to determine the alternate screen size.

Use this parameter only to query VTAM terminals that support SNA QUERY commands, and do not have an alternate screen size defined in their log mode.

• For VTMQUERY=ALL, the interface will QUERY ALL terminals.
• For VTMQUERY=NORM, the interface will QUERY the terminal if the bind image indicates it is a VTAM QUERY terminal, and there is no alternate screen size defined.
• For VTMQUERY=NONE, the interface will not QUERY any terminals (and color will not be supported).

Default: NORM.

VTMSAA=YES|NO

Indicates whether all terminals are SAA compliant.

If you have the following:

• Older terminals that cannot support SAA (3290 terminals, for example
• These older terminals are going to be connecting with log modes that indicate that CA View should query their alternate screen size

You must specify VTAMSAA=NO or these terminals are not able to log onto the SARVTAM interface.

VTAMSAA=NO causes more overhead in logging on terminals than can be queried, and is only to be used when required.

XMS=YES|NO

Indicates whether cross-memory users are allowed to sign on to the region.

Set XMS=NO if this is a VTAM only region, and cross-memory is not to be supported.

Note: If XMS=NO, be sure that there is a VTAM ACB name coded in the SARAPPL= parameter.

Default: YES.

XMSSUB=YES|NO

XMSSUB=YES is required for ISPF cross-memory, TSO cross-memory, and CA Roscoe cross-memory sessions

All other interface users are to be set XMSSUB=NO.

Default: NO.

SARLOG DD Statement (Optional)

The optional SARLOG DD statement is used to specify where to write the log of user subtask messages.

This output is critical to resolving user subtask ABENDs, and is to be submitted to CA Technical Support along with the region or task dump created with an ABEND.

SYSPRINT DD Statement (Optional)

The optional SYSPRINT DD statement is used to specify where to write the log of cross-memory (SARXMS) messages.

This output is critical to resolving SARXMS ABENDs, and is to be submitted to CA Technical Support with the region or task dump created with an ABEND.

EBCUDUMP DD Statement

The EBCUDUMP DD statement is required, and is used to specify where to write a special dump of CA View control blocks that do not appear in normal MVS dump output.

This output is critical to resolving SARXMS abends and should be submitted to Technical Support with the region or task dump created with an ABEND.

Note:

• On ABEND Output, only regular MVS dump output should be collected. Output from dump compression and analysis programs is not helpful to technical support—you might be required to recreate the dump.
• Acceptable types include SYSUDUMP, SYSMDUMP, or SYSABEND output, in print-record format. IPCS/SVC dumps and CICS transaction or region dumps are also acceptable, but must be formatted for printing before they are placed on the tape.
• The RMOXMS region uses the operator facility to abort a user's task for various problems. These problems might be a LONGWAIT time out, a VTAM I/O error, or a detected internal error, which appear in the log followed by a U0522 ABEND of the user subtask. No dump is generated.

STEPLIB for this Job

The action you take in this step depends on what you did during the base-product installation. Specifically, did you:

• Authorize the program load library

  or

• Copy the modules to a system authorized library

Be aware of the following before you run this job:

• If the CA View load modules were copied to an authorized library other than one of the linklist libraries, you must change the data set name on the STEPLIB DD statement.
• If the load modules were copied to a linklist library, you must remove the STEPLIB DD statement.
• If you have CA Deliver installed, you must consider these possibilities before you run the job listed previously above: If the CA View load modules were copied to an authorized library other than one of the linklist libraries, concatenate the CA Deliver load library as a second STEPLIB after the CA View load library in the STEPLIB DD statement.
• If the load modules were copied to a linklist library, do nothing.
• For the JES3 Environment

  You must add the cross memory task to the JES3 task output table.

  If you do not add this task, the P reprint select code cannot function properly.