DB2 Server for VSE & VM: Operation

Putting Initialization Parameters in VSE Source Members or in VM CMS Files

When starting the application server, you often use the same set of initialization parameters. You can place the initialization parameters in either a VM CMS file or in a VSE A-type source member. You can use the CMS file instead of entering the parameters each time you start the application server, you merely refer to the file. Or, you can place the initialization parameters in a VSE A-type source member. Then, instead of entering the parameters each time you start the application server, you merely refer to the member.

The following is an example of the content of a parameter file in VM.

Figure 3. Example Parameter File

LOGMODE=A,NDIRBUF=20, NPAGBUF=20, DUMPTYPE=F, COMMENT -- FULL VIRTUAL MACHINE DUMP NCSCANS=20

You can have as many of these parameter files as needed.

Notes:

1. In this example, use spaces in the place of commas when only one parameter appears on a line. Any text included on the same line, but following the space, will be interpreted as a comment.

2. When naming a parameter file, use any valid file name.

3. The file type must be SQLPARM and have a fixed record length of 80 bytes.

To refer to a file when running SQLSTART, put PARMID=file name in the PARM parameter. (PARMID is itself an initialization parameter.) For example, if the file name is WARMSTRT, and you want to access the SQLDBA application server, you can enter:

SQLSTART DB(SQLDBA) PARM(PARMID=WARMSTRT)

The application server reads the parameters from WARMSTRT SQLPARM (using * as the CMS file mode).

When placing initialization parameters in a CMS file, follow these rules:

• A blank following a parameter ends the processing of the line; therefore, do not put a blank between parameters. The application server ignores any characters that follow the blank. You can, however, use blanks to put comments in the file, as shown in Figure 3 for the DUMPTYPE parameter.
• The file content must be in UPPERCASE.
• A comma at the end of a line is not needed, but can make the statement easier to read.
• You cannot put user parameters (those for the application program itself) in the file. See Specifying Parameters for User Programs for more information. If the application server detects parameters other than its own initialization parameters, it issues error messages and stops processing.

The following is an example of a job you might use to catalog a source member in VSE.

Figure 4. Example Job to Catalog a Source Member

// JOB CATALPRM // EXEC LIBR ACCESS SUBLIB=PRD2.SQL340 CATALOG PARMXMPL.A,REPLACE=YES DSPLYDEV=B,NDIRBUF=20,SYSMODE=S, PROGNAME=USERPROG,NPAGBUF=20, DUMPTYPE=F, COMMENT - FULL PARTITION DUMP NCSCANS=20 /* /&

You can have as many source members as you need. The member must be an A-type source member. Each member specifies a different set of frequently used parameters.

To refer to the member when starting the application server, specify PARMID=member_name. (PARMID is itself an initialization parameter.) For example, if the name of the member is PARMXMPL, you can use:

// EXEC ARISQLDS,SIZE=AUTO,PARM='PARMID=PARMXMPL'

The application server reads the parameters from the PARMXMPL source member.

Follow these rules when placing initialization parameters in either a CMS file or in a source member:

• A blank following a parameter ends the processing of the line; therefore, do not put a blank between parameters. The application server ignores any characters that follow the blank. You can, however, use blanks to put comments in the file, as shown in Figure 4 for the DUMPTYPE parameter.
• A comma at the end of a line is not needed, but can make the statement easier to read.
• You cannot put user parameters (those for the application program itself) in the file. See Specifying Parameters for User Programs for more information. If the application server detects parameters other than its own initialization parameters, it issues error messages and stops processing.