TLVPARM

Edit online

TLVPARM contains configuration information for most CL/SuperSession components. Table 17 lists the CL/SuperSession Engine-specific members.

Table 1. CL/SuperSession TLVPARM Members
Member	Component
KLJINVSS	Virtual Session Services
KLKINDM	Dialog Manager
KLKINNAF	Network Accounting Facility
KLKINNAM	Network Access Manager
KLKINPSM	Presentation Space Manager
KLKINRLM	Resource List Manager (invoked as part of NAM initialization)
KLKINSNS	Global Sense Code Processor
KLKINSTG	Storage Isolation
KLKINTB	Tables Manager
KLKINVLG	Viewlog
KLKINVPO	VTAM® Program Operator
KLKINVSM	Virtual Session Manager
KLKINVTM	VTAM Support

Syntax

Observe these syntax rules when coding initialization members:

TLVPARM can be either a fixed- or variable-length file. All libraries concatenated to the DD must have the same RECFM and LRECL.
Note: All CL/SuperSession SMP/E-distributed maintenance assumes a fixed-length file with 80-byte records.
Each CL/SuperSession or product component looks for only a specifically-named member. This is usually the same as the component's initialization module. (That is, the KLKINTB routine reads the KLKINTB member.)
Each initialization member can contain sequence numbers. Sequence numbers are detected according to these rules:

Fixed-length files

The last 8 characters of the first record are examined.
If all 8 characters are numeric, the entire file is assumed to contain sequence numbers and those 8 columns are ignored on every record. Otherwise, they are considered significant.

Variable-length files

The first 8 characters of the first record are examined.
If all 8 characters are numeric, the entire file is assumed to contain sequence numbers and those 8 columns are ignored on every record. Otherwise, they are considered significant.
Keywords and any values specified for them can span multiple physical records. Indicate a continuation by coding one of the following markers as the last nonblank character in a record:
minus (-)
The next line is concatenated to the current line with one blank separating the significant text. For example,
```
   KEYWORD1(VALUE1)   -
     KEYWORD2(VALUE2)
```
is processed as
```
   KEYWORD1(VALUE1)   KEYWORD2(VALUE2)
```
plus (+)
The next line is concatenated to the current line with all blanks retained. For example,
```
   KEYWORD1(VALUE1)     +
     KEYWORD2(VALUE2)
```
is processed as
```
   KEYWORD1(VALUE1)      KEYWORD2(VALUE2)
```
It is recommended that you use the minus/hyphen (-) because it slightly reduces parsing overhead. Use the plus sign (+) only when a specific number of blanks are required as, for example, in message text.
You can specify more than one keyword on a physical record, separated by a comma or blanks. However, it is not recommended because complications for maintenance and debugging result.
An asterisk that is not part of a quoted string causes the remainder of the
logical record to be treated as a comment and ignored. For example,
```
   KEYWORD1(VALUE1)     * changed on 10/12/92 -
   KEYWORD2(VALUE2)
```
is processed as
```
   KEYWORD1(VALUE1)   * changed on 10/12/92 KEYWORD2(VALUE2)
```
and the KEYWORD2 keyword is ignored.
You can enter data in mixed case; it is usually translated to upper case internally before processing. Refer to the description of each initialization member for any exceptions.
Specify keywords once only, except where noted in the description of the initialization member.
Specify keyword values either with an equals sign or a set of parentheses. For example, the following keywords are equivalent:
```
   TIMEOUT=10
   TIMEOUT(10)
```

It is recommended that you use parentheses to delimit the data visually.

Examples

Figure 1 shows an example of an initialization member in TLVPARM.

Figure 1. Typical TLVPARM Member


************************************************************************
*                                                                      *
* MEMBER: KLKINTB   TABLE ACCESS MANAGER DATASET                       *
*                                                                      *
* FUNCTION:                                                            *
*                                                                      *
*   THIS MEMBER IDENTIFIES THE VSAM DATASET USED BY THE TABLE          *
*   MANAGER TO STORE TABLES.                                           *
*                                                                      *
************************************************************************
&rvhilev.RLSTDB -
DISP(SHR)