CPCINI keywords
This topic lists and describes the supported cpcxINI keywords.
The default cpcxINI sample member contains sufficient keywords for normal operations.
Command | Keyword | Required | Default | Description |
|---|---|---|---|---|
ENV | NAME | Y | None | Specifies the logical name of environmental services to be initialized in the server address space The name must be one to eight characters. |
ENV | PARM | N | None | Eight-byte parameter field to be passed to environment services initialization module |
ENV | PROGRAM | Y | None | Identifies the program module to call to initialize the service The program module is also called for each function connecting to these services. |
ID | DESC | N | None | Up to 50-character description used to identify CPC subsystem for user interface |
LOG | SPILL | N | 0 | Number of lines to write to CPCLOG before automatically closing and reallocating new SYSOUT data set |
LOG | SYSOUT | N | * | SYSOUT class to use for the CPCLOG data set |
MIG | DATACLAS | N | None | Identifies the SMS data class of the unload file being allocated for migration |
MIG | MGMTCLAS | N | None | Identifies the SMS management class of the unload file being allocated for migration |
MIG | STORCLAS | N | None | Identifies the SMS storage class of the unload file being allocated for migration |
MIG | THRESHEXT | N | 200 | Identifies the threshold value for maximum extents that is used during execution of the repository management EXPAND command If you specify a value less than five, the original default value (200) is used. The maximum extents threshold used with the repository management EXPAND command is used exclusively as a repository management threshold. It is not related to the MAXM OSAM/VSAM Extents threshold defined in the console for user databases. |
MIG | UNIT | N | None | Identifies the UNIT name of the unload file being allocated for migration |
MIG | VOLS | N | None | Identifies the volume name of the unload file being allocated for migration |
REP | PREFIX | N | None | 26-byte prefix to use when allocating repository data sets You must change this name to accommodate your environment. |
REP | RECS(p,s) | N | 1000, 500 | Default REC values (primary allocation, secondary allocation) to use when defining new repository data sets |
REP | VOLS(vol,...,vol6) | N | None | Up to six default volumes to use when defining new repository data sets You must change this value to accommodate your environment. |
START | MODE | Y | None | MODE specifies that the server is private. |
START | NAME | Y | None | NAME(ALL) is used for all product functions NAME(CPCSAMP) is used for all CPC sample functions. Any function can be started by operator command. |
START | TYPE | Y | None | TYPE(FUNCTION) is used to specify which functions are started at CPC initialization. TYPE(COM) is used to start the Comm Server in this address space. |
TRACE | ACTIVE | N | N | Identifies whether tracing is to be started when the server address space is initialized |
XSYS | GROUP | Y | None | One to eight-character cross-system group name; must be a unique XCF group within the SYSPLEX All cpcxINI keywords must point to the same XSYS(GROUP) name. |
XSYS | MASTER | N | None | Defines the MVS image on which the IPT server master resides For more information about how the master IPT server works, see Sysplex-implementation. |
TRACE | SPILL | N | 0 | Number of lines to write to CPCTRACE before automatically closing and reallocating new SYSOUT data set |
TRACE | SYSOUT | N | * | SYSOUT class to use for the CPCTRACE data set |
XSYS | THREADS | N | 1 | Number of pipes to use per remote host |
A F Y N | SYSPLEX |
| A | Specify whether to use XIM |
Any valid unit name | XIMDASD |
| SYSDA | Assign a unit name for SYSPLEX DASD |
A F Y N | SYSPLEX |
| A | Specify whether to use XIM |
Any valid unit name | XIMDASD |
| SYSDA | Assign a unit name for SYSPLEX DASD |
You must specify the CPCINI control statement data set in the IPT started task procedure (cpcxIPT). The control statement must contain 80-character fixed-length records. A command can have keywords and comments. Separators and continuation characters are supported. You can enter commands anywhere in positions 1 through 72 of the input statement (positions 73 through 80 are ignored). See the CPCINI sample member in the sample library for your solution or product.
Related topic