Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Infrastructure 7.1 .

CAS START command parameters

The following table describes each parameter that can be used with the START command.

Parameter

Description

procname

Specifies the name of the startup procedure for the CAS (for example, BBMCAS as created by customization)

.id

(Optional) Assigns an arbitrary ID to the CAS started task

The .id parameter can be used to assign a name to the CAS that is shorter or more recognizable than the procedure name. For example, you might enter START BBMCAS.CASA to start a CAS on system A that is called simply CASA.

SSID=ssid

(Required for CAS startup procedure, but optional for START command)

Identifies the CAS subsystem ID to the UAS and PAS

If an SSID is not specified on the START command, the SSID on the PROC statement in the CAS startup procedure is used. The default is BBCS.

Be sure your BMC AMI Ops know the SSID value, as this value is required for the Subsystem ID field in the Session Control Parameters panel.

For a PAS to connect to a CAS, the SSID values in both the CAS and PAS startup procedures must be the same. For more information about creating CAS and PAS startup procedures, see Creating-the-CAS-startup-procedure, Creating-the-z-OS-PAS-startup-procedure, and Creating-a-BBI-SS-PAS-startup-procedure.

REUSASID=YES

(Optional) Assigns the address space to the reusable address space pool

See the START command in z/OS MVS System Commands for details on the usage of this parameter.

CAPS={Y|N}

(Optional) Identifies whether the CAS should provide Katakana terminal support for console and WTO messages that are issued from the CAS

The default is N (No), which means that console messages and WTO messages appear in mixed case. If you initialize the CAS with CAPS=Y, console messages and WTO messages are converted to uppercase for Katakana terminals.

COLD={Y|N}

(Optional) Indicates whether CAS startup should be a cold start

The default is N (No).

When the CAS initializes, several control blocks and load modules are placed in common storage. Most of this storage is freed when the CAS terminates. However, certain blocks are retained to permit the reuse of previously allocated system resources – in particular, system linkage indexes. In addition, two load modules are retained in common storage. COLD=N reuses those control blocks and load modules rather than building new ones.

Specify COLD=Y only when instructed to do so by BMC Customer Support in an effort to clear an error condition. COLD=Y causes the linkage indexes, control blocks, and load modules to be discarded. The linkage indexes and the common storage that is occupied by those resources are lost until the system is IPLed. Inappropriate use of COLD=Y might exhaust available system linkage indexes, at which point an IPL is required to restore normal system operation.

COMMORDR={XTV|xxx}

(Optional) Determines the order in which communication methods (XCF, TCP/IP, and VTAM) will be tried in attempts by the local CAS to communicate with remote CASs

Specify the first letter of one or more communication methods (X, T, or V) in any order. The order that you specify does not guarantee a particular communication method will be used, only that each method will be tried in the order you specify. The first method that successfully establishes communication with a remote CAS will be used.

The default is XTV, which means that the local CAS will first attempt to communicate with remote CASs by using the Cross-System Coupling Facility (XCF). If that method fails, TCP/IP will be tried and, if that fails, VTAM will be tried.

Note

To use XCF for CAS-to-CAS communication, all participating CASs must also include CONVXCF=Y (either explicitly or by default).


CONVXCF={Y|N}

(Optional) Indicates whether a CAS uses the Cross-System Coupling Facility (XCF) to communicate with other CASs in a sysplex environment

The default is Y (Yes). If CONVXCF=N is specified, the CAS cannot participate in XCF communication with other CASs.

To use XCF for CAS-to-CAS communication, all participating CASs must

  • Reside in the same sysplex and XCF group
  • Include X on the COMMORDR parameter (either explicitly or by default)

If all the CASs are in the same sysplex and XCF group, CONVXCF=Y allows the CAS to auto-discover and auto-connect to the other CASs through XCF.

DFLTGRP={BBGROUP|name}

(Optional) Identifies the Cross-system Coupling Facility (XCF) group name that is to be used at CAS startup

The default is BBGROUP.

DUMP={Y|N|ALL|YH|ALLH}

(Optional) Indicates whether system dumps (SDUMPs) are taken when a severe error is detected by a CAS

  • DUMP=Y (the default) allows dumps for errors that occur in privileged code.
  • DUMP=N suppresses all dumps within the CAS.
  • DUMP=ALL allows dumps for all errors, whether the error occurs in privileged code or problem-state code. You should use ALL only as instructed by BMC Customer Support.
  • DUMP=YH allows dumps for errors that occur in privileged code, but limits the dump to the home address space (along with summary information from any primary or secondary address space).
  • DUMP=ALLH allows dumps for all errors, but limits the dump to the home address space (along with summary information from any primary or secondary address space).

Note

YH and ALLH are performance-saving options that can restrict the ability to diagnose problems. These options should be used only if the address space cannot tolerate any delay, and only after consulting with BMC Customer Support.


EMM={Y|N}

(Optional) Indicates whether extended message mode (EMM) is active when starting the CAS

The default is N (No).

EMM messages are a subset of the messages that are controlled by the XDM parameter. You can enable EMM messages by specifying EMM=Y without enabling XDM messages. However, EMM=Y is not recommended for normal CAS operation; use only as instructed by BMC Customer Support.

SUB=MSTR

(Optional) Allows the CAS to start and run independently of JES

Note

SUB=MSTR might not be compatible with some releases of OMVS. Early releases of OMVS would not accept a request until their initialization was completed. This effectively disables all TCP/IP communications for the CAS. OMVS releases that are more current queue the request and process it once OMVS is ready. Since this behavior is undocumented and hence subject to change, consider not using SUB=MSTR if also using TCP/IP for communications.


XDM={Y|N}

(Optional) Indicates whether the CAS should operate in extended diagnostic mode (XDM), which produces additional messages and suspends some CAS error recovery processing

The default is N (No).

Warning

Specify XDM=Y only when instructed to do so by BMC Customer Support. The XDM=Y parameter disables certain error-recovery processes that could severely impact your CAS subsystem.


Note

The SPCF=Y parameter is still accepted in the CAS startup procedure and on the START command, however it is ignored. To use the Cross-System Coupling Facility (XCF) to communicate with other CASs in a sysplex, specify

  • CONVXCF=Y
  • X on the COMMORDR parameter

Related topic

Starting-a-CAS

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*