gtps4m2nSystem Generation

CONFIG

The CONFIG macro is used to define some of the hardware and software configuration specifications for the installation.

The CONFIG macro is required.

Format




Notes:

  1. The following parameters are only used by SIP Stage I processing.

  2. The SYSID parameter is used by the offline FACE table generator as well as by SIP Stage I processing.

  3. The PROC parameter is repeated for each processor defined in the loosely coupled complex, where x is 1 - 32.

  4. The only valid values for an SSA range from 0 to 7. Do not code for processors 9 - 32.

APRNT=address
Three-digit physical address, in hexadecimal of a printer device to be used by the IPL program and 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 has been 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.

Note:
If a 3880 storage director is set to answer to address range A0-AF, the DCUSV value will be 16. If it answers to address range A0-BF, then the DCUSV value will be 32. The value 64 is only valid for a 3990 storage director. The current locking architecture may not support 64 DASD behind a storage director.

MAPSP=YES|NO
Specifies the inclusion of 3270 mapping support.

See 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. Note that PTV also uses these options. These options are also set by specifying PTV to SIP.

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.

CIPHR=(NO|AET|DES|BOTH,pdsname)
Specifies whether data encryption support is to be included in the system and the type of encryption technique desired.

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

NO
No data encryption support provided.

AET
Provides support for the original IBM 3614 encryption technique. This technique will now be referred to as the Alternate Encryption Technique (AET). Specify the AET parameter with the name of a partitioned data set (PDS) that contains the BQKCIPH module or SIP processing will not be completed.

DES
Provides support for the data encryption technique that complies with the National Bureau of Standards Proposed U.S. Federal Information Processing Data Encryption Standard (DES) as defined in the Federal Register, Volume 40, Number 149, August 1, 1975, page 32395. Specify the DES parameter with the name of a PDS that contains the BQKDES module or SIP processing will not be completed.

BOTH
Provides support for both the AET and DES encryption techniques. Specify the BOTH parameter with the name of a PDS that contains the BQKCIPH and BQKDES modules or SIP processing will not be completed.

pdsname
Specifies the name of a PDS that contains the encryption modules to be included. Specify pdsname with the AET, DES, or BOTH parameters or SIP processing will not be completed. If you specify a PDS name with the NO parameter, the PDS name is ignored.
Note:
If data encryption support is included for 3614 and/or 3624 type devices, the dummy modules included with the 3600 Independent Release must be replaced by operational modules. IBM distributes object modules for BQKCIPH and BQKDES to 3614 and 3624 customers on special request.

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 TPF system will activate a series of RES programs. A list of these programs can be found in IBMPAL by locating all program invocations where FUNC=&SBRES is specified.

Notes:

  1. It is the obligation of the system programmer to ensure that all of these programs are loaded into the TPF system.

  2. 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 TPF system will activate a series of Fare Quote Ticketing programs. A list of these programs can be found in IBMPAL, by locating all PAL macro invocations where FUNC=&SBNFQTK is specified.
Note:
It is the obligation of the system programmer to ensure that all of these programs are loaded into the TPF system.

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 TPF complexes within an enterprise or operations center. This name is displayed with the 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 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 TPF loosely coupled complex or stand-alone processor that is being generated. Unique names should be used to distinguish multiple 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 TPF (stored as 'TPF   ').

DATEFMT=MDY|DMY|YMD
Specifies the date format the system clocks use where M=month, D=day, and Y=year.

NEF=NO|YES
This parameter should be coded 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. 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 TPF System Installation Support Reference.

TPFAR=NO|YES
Specifies whether the TPF Application Requester (TPFAR) feature is included in the system.

TPFDF=NO|YES
Specifies whether the TPFDF product is included in the system initialization program (SIP).

NO
Specifies that the SIP does not include the TPFDF product in the TPF system.

YES
Specifies that the SIP includes the TPFDF product in the TPF system.

VEQR=NO|YES
Specifies migration mode.

This parameter should be set to YES in a test system when migrating to the TPF 4.1 system (migration mode).

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

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

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

YES
The 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
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 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.

PROCx=(serial#, model#,SSA0,SSA1,SSA2,SSA3,SSA4,SSA5,SSA6,SSA7)
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.

The time-of-day (TOD) Synchronization Selection Address (SSA) is the port that other processors receive signals on when this processor is the master. The SSA is specified on the 3rd through the 10th subparameters of a PROCx statement and is only required if the TOD Clock Synchronization RPQ is installed or if an STR is using a TSC for TOD clock synchronization. The position of the third through tenth subparameters corresponds to the addresses of the CPU(s) within a processor (where processor refers to either a real processor or one side of a partitioned processor). See Processor Definition for a discussion on partitionable processors.) Within an LC complex each TPF image must possess a unique SSA. If the TOD Clock Synchronization RPQ is installed, at least one of the SSA subparameters must be coded for each PROCx parameter that is coded. The only valid values for an SSA range from 0 to 7. Do not code the SAA subparameter for PROC9-PROC32.

For uniprocessors, only one of the eight SSAs will be coded. For multiprocessors, all CPUs in the same partition must possess the same SSA. If the SSA for a CPU is omitted, then that CPU cannot be IPLed.

For partitioned processors, the side that will be included in the LC complex must have its CPU(s) coded. If both sides of a partitioned processor are used within the same LC complex, then each partition must have a unique SSA, and each CPU within the partition must have the same SSA value.

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

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

The first TPF processor ID takes on additional significance -- this processor will contain the EP and BSC communication functions. Also, the system communications keypoint (SCK) generation must use the first 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.

Note:
When a loosely-coupled environment exists:
  1. The MPIF feature is also required to permit IPC communications among the processors. This is accomplished by coding MPIF=YES on the CONFIG macro.
  2. Multiple Systems Network Facility (MSNF) support must be included in the system.
  3. 4KB blocks must be increased to account for SIPC requirements. See CORREQ.

Examples

Example 1: The following specifies a processor with a printer address of X'00E', and the TPF processor ID is A.

CONFIG APRNT=00E,SYSID=A

Example 2: The following example (illustrated in Figure 29) specifies a loosely coupled complex. Each processor in the complex has a printer address of X'00D'. Since PROC3 defines a partitioned processor, it receives two of the four processor IDs that were specified on the SYSID parameter. The other two processors receive only one processor ID each. The actual assignment of a processor ID to a processor is done at IPL.

CONFIG APRNT=00D,SYSID=(A,B,C,D),
      PROC1=(10000,9021,,,1),
      PROC3=(20000,3090,,3,3,4,4),
      PROC4=(30000,9121,,2,2),

A 9021 has a single CPU at address 2. For the example above, this implies that an SSA should be coded on the fifth subparameter of PROC1. Subparameters three and four are left undefined. A 9121 has two CPUs, one at address 1 and one at address 2. For the example above, this implies that an SSA should be coded on the fourth and fifth subparameters of PROC4. Subparameter three is left undefined.

The physical connection of the TOD Synchronization RPQ cables must follow the SSA number as shown in Figure 29. PROC1 has an SSA number of 01. Notice that the lines connecting PROC1 with PROC3 and PROC4 use SSR 01 whereas PROC3 Side A has an SSA number of 03 so the connections to all other CPUs use SSR 03.

Note:
The Synchronization Selection Register (SSR) is the port that this processor receives signals on when it is the slave. When the high-order bit is on this processor is the slave (synchronized remotely). When the high-order bit is off, either the processor is the master for the complex or it is running in local mode. By convention the master has its SSR set equal to its SSA.

Example 3: The following example specifies a loosely-coupled complex that is using a Sysplex Timer (STR) as the synchronization source.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection Architecture.

There are no processors with the TOD Clock Synchronization RPQ; therefore no SSA subparameters are required.

CONFIG APRNT=00D,SYSID=(A,B),                                X
      PROC1=(12345,3090),                                    X
      PROC2=(67890,3090)

Example 4: The following example specifies a loosely-coupled complex that is using an STR as the synchronization source. Processor 1 is directly connected to the STR and therefore does not require any SSA subparameters. Processors 2 and 3 both have the TOD Clock Synchronization RPQ and are connected to the STR through the TOD Synchronization Compatibility RPQ. Processors 2 and 3 require SSA subparameters due to the presence of the TOD Clock Synchronization RPQ. In addition, Processor 3 defines a partitioned processor.

CONFIG APRNT=00E,SYSID=(A,B,C,D),                            X
      PROC1=(10000,3090),                                    X
      PROC2=(20000,3083,,,0),                                X
      PROC3=(30000,3090,,1,1,2,2)

Figure 29. Sample Configuration


References

Mapping support in the TPF Data Communications Services Reference.