CONFIG

The CONFIG macro is required.

APRNT=address

Three-digit hexadecimal physical address of a printer device to be used by the in-core dump formatter program for printing dumps. The first digit must be 0.

For a non-basic subsystem, this parameter must be coded the same as it was for the basic subsystem.

CTKI32LC

Specifies whether keypoint I (CTKI) should be in 32-way loosely coupled format.

YES

CTKI is generated with the 32-way loosely coupled processor support flag (IC032LC) set on, indicating that CTKI is in 32-way loosely coupled format. YES must be coded if one of the following is true:

• This is an existing loosely coupled complex and the ZMIGR command with the CTKI and CONVERT parameters specified was completed successfully.
• This is a new complex with 32-way loosely coupled processor support on all processors.

NO

CTKI is generated with the 32-way loosely coupled processor support flag (IC032LC) set off, indicating that CTKI is not in 32-way loosely coupled format. NO must be coded if one of the following is true:

• This is an existing loosely coupled complex and the ZMIGR command with the CTKI and CONVERT parameters specified has not been completed successfully.
• The ZMIGR command with the CTKI and FALLBACK parameters specified has been completed and CTKI is not in 32-way loosely coupled format.

DTAC

This parameter limits the amount of data presented to the dump data user exit.

NO

Detached data blocks will not be included.

YES

The number of data blocks presented to the user exit will be limited by the constant DETDATAX in CZOCP.

DUMPDEV

Specifies the device to which systems error dumps are to go.

TAPE

All system error dumps will go to the real time tape (RTA or RTL).

PRTR

Program ICDF will be loaded as part of the in-core online system and all system error dumps will be printed online, on the printer specified in the APRNT parameter. The PRTR option should only be specified for test systems, because all processing is suspended while the dump is being printed.

It is recommended that you dump to tape on a production system, because it is faster than going to a printer.

DCUSV=32|64|16

Specifies the range of installed addresses on the DASD control unit interface cards. Valid values are 16, 32 or 64.

For a non-basic subsystem, this parameter must be coded the same as it was for the basic subsystem.

MAPSP=YES|NO

Specifies the inclusion of 3270 mapping support.

See z/TPF Data Communications Services Reference for more information about mapping support. If MAPSP=YES is coded, and the system being generated is a base only system or the basic subsystem in an MDBF environment, then 3270 support must also be included by coding the MAXRVT parameter of the SNAKEY macro as non-zero at network definition time.

VM=NO|YES

Two options in keypoint record A (CTKA) are generated. The CP in test mode bit is used by the command editor to allow or disallow the use of the ZTEST command. The tapes in test mode bit is used exclusively to control the use of general tapes.

For a non-basic subsystem, this parameter must be coded the same as it was for the basic subsystem.

Note: Either option can run native, or under VM. A system generated with the VM=NO options, when actually running under VM, is aware that it is running under VM. Conversely, a system generated with the VM=YES option is capable of running native.

Loosely coupled systems may not be run under VM. Specify VM=NO (or allow it to default) for all loosely coupled systems.

RES=NO|YES

This parameter specifies if the PARS/IPARS application 'RES0' is to be included in the system. In defining a subsystem other than the basic subsystem in a multiple database function (MDBF) environment, this parameter is the only way to specify the PARS/IPARS option. If RES=YES is specified, the z/TPF system will activate a series of RES programs. You can specify that a program is a RES program by setting the FUNCTION SWITCH field in the control file record for the program to TPF_SBRES.

Note: This parameter is specific to the PARS/IPARS application and should not be confused with a general reservation type application. If the PARS/IPARS application programs are not needed this parameter should be coded as NO.

FQTK=NO|YES

Specifies Fare Quote Program Product support. If FQTK=YES is specified, the z/TPF system will activate a series of Fare Quote Ticketing programs. You can specify that a program is a Fare Quote Ticketing program by setting the FUNCTION SWITCH field in the control file record for the program to TPF_SBNFQTK.

MSGSW=NO|YES

Specifies the inclusion of the message switching function.

For a non-basic subsystem, this parameter must be coded the same as it was for the basic subsystem.

USER=USA|WTC

Specifies whether the support functions for a WTC (World Trade Corp.) user are to be included or whether support is for a non-WTC (i.e. USA) user.

For a non-basic subsystem, this parameter must be coded the same as it was for the basic subsystem.

ENTERPRISE=IBM|enterprise name

The 1-to-8 alphanumeric character string indicating the name of the enterprise or operations center associated with the system. The same name can be used to identify multiple z/TPF complexes within an enterprise or operations center. This name is displayed with the z/TPF complex name and the CPU ID in an IPL message when the system is IPLed. You can display this information in an online environment using the ZDSID command. See z/TPF Operations for additional information.

For a non-basic subsystem, this parameter must be coded the same as it was for the basic subsystem.

The enterprise name is stored internally and displayed online in a right-justified field.

The default is IBM (stored as '   IBM').

COMPLEX=TPF|complex name

The 1-to-8 alphanumeric character string indicating the name of the z/TPF loosely coupled complex or stand-alone processor that is being generated. Unique names should be used to distinguish multiple z/TPF complexes within an enterprise or operations center.

For a non-basic subsystem, this parameter must be coded the same as it was for the basic subsystem.

The complex name is stored and displayed in a left-justified field.

The default is z/TPF (stored as 'TPF   ').

DATEFMT=MDY|DMY|YMD

Specifies the date format the system clocks use where M is the month, D is the day, and Y is the year.

NEF=NO|YES

Code YES if the user requires ALCI support.

For a non-basic subsystem, this parameter must be coded the same as it was for the basic subsystem.

MPIF=NO|YES

Include the multi-processor interconnect facility (MPIF). Must be coded as YES in a basic subsystem / loosely coupled generation.

Do not code this parameter as YES in a non-basic subsystem generation.

ACF=NO|YES

Controls whether OSTG segments are link-edited.

For a non-basic subsystem, this parameter must be coded the same as it was for the basic subsystem.

SELACT=NO|YES

Enables or disables the E-type loader selective activate function. If SELACT=YES, selected ECBs can enter the programs in a selectively activated loadset. Otherwise, no ECBs can enter the programs in a selectively activated loadset. For more information about the E-type loader selective activate function, see z/TPF and z/TPFDF System Installation Support Reference.

TPFAR=NO|YES

Specifies whether the z/TPF application requester (z/TPFAR) is included in the system.

BPCRLOAD

Controls the method for loading the core resident program area (CRPA).

NO

The CRPA is loaded during restart while the z/TPF system is cycling to 1052 state.

YES

The z/TPF system does not load the CRPA during restart. Rather, it loads core resident programs when they are called for the first time.

This parameter must be the same for all subsystems (BSS and non-BSS).

Note: Programs that are allocated as PRELOAD are always loaded during restart, regardless of the value specified for this parameter.

DBRBUF=NO|YES

Specifies if buffered tape devices are used during the database reorganization (DBR) output phase.

This parameter is ignored when generating a non-basic subsystem.

Attention: Running the DBR output phase with buffered tape devices will improve performance; however, if the z/TPF system IPLs again or tape errors occur while DBR is in progress, you may lose data.

WTOPCUNS

Specify one of the following:

YES

The WTOPC message package sends remote terminals unsolicited messages.

NO

The WTOPC message package sends remote terminals solicited messages.

This parameter must be the same for all subsystems (BSS and non-BSS).

PREMSG=YES|NO

Specifies whether messages generated by the system message processor will be prefixed by the CSMP0097I message.

Note: Do not use the NO value with the PREMSG parameter on a system that has a subsystem defined because messages do not always have a subsystem name.

PROCx=(serial#,model#)

The PROCx parameter (where x is 1–32) defines a physical processor (CPC) in a loosely coupled (LC) processor complex. In a non-LC environment, the PROCx parameters are ignored and a warning message is issued if they are coded.

In an LC processor complex, at least one PROCx parameter must be coded and, for each PROCx that is coded, at least 2 but no more than 10 subparameters are required. The first subparameter is the processor serial number and the second subparameter is the processor model number. The encoding of the processor serial number corresponds to bits 12–31 of the doubleword addressed by the STIDP instruction, while the encoding of the model number corresponds to bits 32–48 of the doubleword addressed by the STIDP instruction. Both the serial and model number subparameters are required. The serial number is specified by a 1 to 5 character hexadecimal number, while the model number is specified by the 4 character name.

For a non-basic subsystem, this parameter must be coded the same as it was for the basic subsystem.

SYSID=A|v1|(v1[,…,v32])

One or more characters ranging from A through Z or 0 through 9 that will be used to assign the z/TPF processor ID(s). A system being defined as a loosely-coupled system will define more than one and up to 32 z/TPF processor IDs (see Example 2). Specifying more than one z/TPF processor ID will inform SIP that this is a loosely-coupled generation. The order in which each z/TPF processor ID is presented to SIP through this parameter becomes the ordinal number that z/TPF will use to refer to each processor.

The first z/TPF processor ID takes on additional significance — this processor will contain the 3270 local communication functions. Also, the system communications keypoint (SCK) generation must use the first z/TPF processor ID as its pilot processor ID. Finally, the name of the Application Name Table (ANT) deck produced by SIP is derived from the first parameter value. If the first processor ID listed is A, the name of the ANT deck will be ANTA. If it is B, the name of the ANT deck will be ANTB, and so on.

For a non-basic subsystem, this parameter must be coded the same as it was for the basic subsystem.

TRACE=YES|NO

Specifies whether to start ECB trace (macro and function trace). The macros traced are the SVC macros associated with an active ECB. The functions that are traced are in programs compiled using the -mtpf-trace option of the compilers supported by the z/TPF system. TRACE also starts extended function trace when the FUNCEXT=YES parameter is specified.

Note:

1. If you specify TRACE=YES and FUNCEXT=YES, extended function trace starts.
2. If you specify TRACE=NO, extended function trace does not start.
3. If you specify TRACE=NO, enter/back is not traced.
4. If you specify TRACE=YES, enter/back is traced because SIP sets enter/back trace on.

FUNCEXT=NO|YES

Specifies whether to start ECB trace with extended function trace when ECB trace is active (TRACE=YES). Extended function trace includes tracing function returns and tracing the caller information for called functions. The function returns that are traced are in programs that are compiled using the -mtpf-trace option of the compilers supported by the z/TPF system.

Note: If you specify TRACE=NO and FUNCEXT=YES, the extended function trace options are not traced until you enter the ZSTRC ALTER TRACE command. See z/TPF Operations for more information about the ZSTRC command.

APACHE=NO|YES

Specifies whether to include APACHE HTTP Server Version 1.3 code in the z/TPF system. For information about using the Apache HTTP Server Version 1.3, see the Apache Software Foundation website. To access the Apache HTTP Server Version 1.3 for the z/TPF system, go to the TPF Family Products: Product Software web page.

APACHEV2=NO|YES

Specifies whether to include Apache HTTP Server Version 2.2 code in the z/TPF system. For information about using the Apache HTTP Server Version 2.2, see the Apache HTTP Server Project website. To access Apache HTTP Server Version 2.2 for the z/TPF system, go to the TPF Family Products: Product Software web page.

LIBCURL=NO|YES

Specifies whether to include the LIBCURL library code in the z/TPF system. To access the LIBCURL library for the z/TPF system, go to the TPF Family Products: Product Software web page.

Note: Some functions in the z/TPF system will not work if the LIBCURL library is not included. For example, the LIBCURL library must be included to enable FTP client support.

TAR=NO|YES

Specifies whether to include Tar support code in the z/TPF system. To access Tar support for the z/TPF system, go to the TPF Family Products: Product Software web page.

NDSP=ENABLE|DISABLE

Enables or disables the suppression of nondisplayable storage areas for operator commands, debugger displays, or dumps. When the contents of nondisplayable storage areas are suppressed, these functions display asterisks in place of the storage contents. For example, you can set this indicator to enable suppression of these storage areas on a production system to protect sensitive data or you can set this indicator to disable the suppression of these storage areas on a test system to facilitate debugging.

USERSW=0000|userswvalue

Sets the 2-byte user system switch field in keypoint A (CTKA), where userswvalue is a 4-character hexadecimal value. This value represents system shared indicators and can be changed only from the basic subsystem.

The 2-byte field provides you with as many as 16 bit switches. Specify this parameter to set the full 2-byte value. Use the CTKA user switch user exit (ULH4) and the ZCTKA ALTER command with the userkeyword parameter specified to change an individual bit switch in this field.

ZLIB=NO|YES

Specifies whether to include the zlib compression library code in the z/TPF system. Download the zlib compression library from the TPF Family Products: Product Software web page.

OPENLDAP=NO|YES

Specifies whether to include z/TPF support for OpenLDAP in the z/TPF system. Specify YES for this parameter when you specify BDB=YES. For more information about using the OpenLDAP directory server and client library, see http://www.openldap.org. To access the OpenLDAP directory server and client library for the z/TPF system, go to the TPF Family Products: Product Software web page.

BDB=NO|YES

Specifies whether to include z/TPF support for Berkeley DB in the z/TPF system. Specify YES for this parameter when you have also specified OPENLDAP=YES; BDB is intended for use only with OpenLDAP support. For more information about using the Berkeley DB embedded database, see http://www.oracle.com. To access the Berkeley DB embedded database for the z/TPF system, go to the TPF Family Products: Product Software web page.

RESTARTSE

Specifies the target of the system error dump that is issued when the Restart key on the system console is pressed. Specify one of the following values:

DBA

Writes the system error dump to the dump buffer area (DBA).

TAPE

Bypasses the DBA and writes the system error dump directly to the dump tape.

Note: When the target is set to TAPE, if a restart dump is issued while the system is writing another dump from the DBA to the dump tape, the dump that is being written to tape is ended. The remainder of the dump that was being written to tape no longer can be post-processed.

ASYNCTAPE

Specifies one of the following values:

NO

The system restart scheduler waits for tape restart to complete and then continues with the remainder of the restart schedule.

YES

The system restart scheduler allows tape restart to run asynchronously with the remainder of the restart schedule. The z/TPF system waits until tape restart completes before entering 1052 state.

ISBOOST

Specifies one of the following values:

YES

Enables I-stream boost. If you specify this value, SIP creates a keypoint A (CTKA) with I-stream boost shown as enabled. After this CTKA is loaded to the z/TPF system, I-stream boost is started during the next IPL if the following conditions are satisfied:

• The z/TPF system is running on a IBM z15 or later.
• The I-stream cap is less than the number of active I-streams or I-streams that are defined for the z/TPF system.

NO

Specifies that you do not want to enable I-stream boost.

SPBOOST

Specifies one of the following values:

YES

Enables speed boost. If you specify this value, SIP creates a keypoint A (CTKA) with speed boost shown as enabled. After this CTKA is loaded to the z/TPF system, speed boost is started during the next IPL if the following conditions are satisfied:

• The z/TPF system is running on a IBM z15 or later.
• The IBM z15 is a subcapacity machine. A subcapacity machine is an IBM Z machine where the processors are running below their full capacity.

NO

Specifies that you do not want to enable speed boost.

EOWNRSTR

Specifies whether automatic ECB owner name restore support is enabled.

NO

Automatic ECB owner name restore support is disabled.

YES

Automatic ECB owner name restore support is enabled.