CA-L-Serv Configuration Tasks › Tailor Startup Parameters

Tailor Startup Parameters

The installation of CA‑L‑Serv places the sample startup command member LSVPARM into the target CCCSOPTN data set. A sample CA‑L‑Serv startup parameter member follows, with an explanation for each line of the parameter.

OPTION SVCDUMP(YES)                               (1)
ADDLOG  MSGLOG  SYSOUT(X)                         (2)
ADDLOG  SQLLOG  SYSOUT(X)
*
IFSYS SYSA                                        (3)
    ATTACH COMMSERVER ACBNAME=COMMSYSA,           (4)
                      CONTYPE=LU0,
                      LOG=MSGLOG
    ACTIVATE COMMSYSB                             (5)
    ACTIVATE COMMSYSC
    ATTACH   FILESERVER SERVERTYPE=HOST           (6)
    ADDPOOL  01 (4096,32) (8192,16)               (7)
    ADDFILE  FILE1 XXXXXXX.FILE1.VSAM,POOL(1)     (8)
    ADDFILE  FILE2 XXXXXXX.FILE2.VSAM,POOL(1)
    ADDFILE  LDMSQL XXXXXXX.LSERV.SQLDICT,        (9)
                      BUFND=5 BUFNI=5
    ATTACH  SQLSERVER LOGID=SQLLOG AUDIT=ALL      (9)
ENDIF                                             (3)
*IFSYS SYSB                                        (3)
    ATTACH COMMSERVER ACBNAME=COMMSYSB,
                      CONTYPE=LU0,
                      LOG=MSGLOG
    ACTIVATE COMMSYSA CONTYPE=LU0
    ATTACH FILESERVER SERVERTYPE=REMOTE           (*)
ENDIF                                             (3)
*IFSYS SYSC                                        (3)
    ATTACH COMMSERVER ACBNAME=COMMSYSC etc.
(...)
    ATTACH FILESERVER SERVERTYPE=REMOTE           (*)
ENDIF                                             (3)

Footnotes:

(1)	This command enables the CA‑L‑Serv recovery code to schedule dumps when exception conditions are encountered.
	Since CA‑L‑Serv does not take duplicate dumps when identical ABENDs recur, this option should not be altered.
(2)	The ADDLOG command defines message logs for the various components of CA‑L‑Serv.
(3)	The IFSYS/ENDIF statements cause CA‑L‑Serv to skip all embedded commands until a match is found on the system sysid. This provides a convenient means of maintaining startup parameters for related CA‑L‑Serv regions executing on different z/OS images within a single LDMPARM member.
(4)	The various services are attached as z/OS subtasks using the ATTACH command. Consult the documentation for your client application to determine which services are necessary to its successful execution.
	Delete statements that are not relevant to your environment. For instance, all communications server commands are not necessary if you run on a single system.
(5)	The ACTIVATE command enables communication between CA‑L‑Serv regions sharing the same subsystem name executing on different systems.
	Note: This command is valid only for VTAM communication. Comment it out or delete it for any systems that use XCF communication.
(6)	This File Server is identified as the HOST. It has physical access to the data sets and will service requests from both local regions executing on SYSA and remote callers executing on SYSB and SYSC.
	Note: All other File Servers in the complex have a SERVERTYPE of REMOTE (*). In a single CPU context, specify SERVERTYPE=LOCAL.
(7)	The ADDPOOL command causes CA‑L‑Serv to invoke VSAM in order to create a pool of shared buffers.
(8)	The ADDFILE command causes CA‑L‑Serv to dynamically allocate a data set, enabling CA‑L‑Serv to process I/O requests.
(9)	If you plan to use the SQL Server, you need to allocate the SQL dictionary (DDname=SQLDICT) before activating this component.

Note: A functionally equivalent setup in three separate members (LSVPARM1, LSVPARM2, and LSVPARM3) is also provided in the YourdeployHLQ.CCCSOPTN data set.