The ATTACH command lets you start CA‑L‑Serv servers on a system and set operating values for them.
ATTach COMMSERVER [[LOGID(name)] [XMVS(YES|NO) [[ACBNAME(name|NONE)]
[CONTYPE(luvalue)] [HOLDBUF(nnnn)] [MAXSENDSIZE(kilobytes)
[MAXSESSIONS(nnnn)] [RECBUFFSIZE(nK)] [RETRMAX(nn)]
[RETRY(seconds)] [SENDLIMIT(nnn)] [XCF(YES|NO)]]]
ATTach FILESERVER [[BUFFERSIZE(bytes)] [COMMSERVERSSN(ssname)]
[SERVERTYPE(type)]]
ATTach SQLSERVER [[AUDIT(msgtype)] [HOSTVARPFX(char)] [LOGID(name)]
[MATCHLIMIT(nnnn)] [OPERATORPFX(char)] [SCANLIMIT(nnnn)]]
|
Operand |
Explanation |
|---|---|
|
ACBNAME |
Identifies the CA-L‑Serv ACB name on this system. This value must be provided if you are using VTAM communication. The value corresponds to the application ID that identifies CA‑L‑Serv to VTAM on the current system. This ID must be unique within your network. Specify NONE if you do not want to use VTAM. Default Value: NONE |
|
AUDIT |
Determines which SQL messages are logged. Specify one of these values: To log only error messages, specify ERROR. To log all messages, specify STATEMENTS. Default Value: ERROR |
|
BUFFERSIZE |
Sets the size (in bytes) of the data buffer that the file server uses to receive data from the communications server. Specify a value from 1024 to 32768. Default Value: 4096 |
|
COMMSERVER |
Activates the CA-L‑Serv communications server. |
|
COMMSERVERSSN |
Tells the file server what copy of the communications server to use. Specify one of these values: To use the communications server running in the same address space as the file server, specify *. To use a different communications server, specify the subsystem name for the appropriate CA‑L‑Serv started‑task. Default Value: * |
|
CONTYPE |
Identifies the protocol when using VTAM communication. Specify one of these values: To use VTAM LU 0, specify LU0. To use VTAM LU 6.2, specify LU62. Default Value: LU0 |
|
FILESERVER |
Activates the CA‑L‑Serv file server. |
|
HOLDBUF |
Indicates the maximum number of data buffers that CA‑L‑Serv should use per client for incoming data. Once this maximum is reached, incoming data is rejected until the client receives the data buffers' contents. Specify a value from 0 to 999. Default Value: 10 |
|
HOSTVARPFX |
Assigns a prefix character that the SQL server uses to identify host variables. Default Value: (colon) |
|
LOGID |
Identifies an auxiliary log for certain messages issued by the communications server or the SQL server: For the communications server, the auxiliary log collects messages about session initiations and terminations, as well as cross‑system transactions. For the SQL server, the auxiliary log collects messages about SQL statements. Default Value: MSGLOG |
|
MATCHLIMIT |
Sets the maximum number of rows that the SQL server can return per SQL statement. Specify one of these values: If you do not want to set a maximum, specify 0. Otherwise, specify a value from 1 to 999999999. Default Value: 0 |
|
MAXSENDSIZE |
Sets the maximum number of kilobytes for data transmission when using XMVS communication. Specify a value from 4 to 64. Default Value: 32 |
|
MAXSESSIONS |
Indicates the maximum number of clients that can be in session with the communications server. Specify a value from 1 to 100. Default Value: 32 |
|
OPERATORPFX |
Assigns a prefix character that identifies special operators to the SQL server. Default Value: . (period) |
|
RECBUFFSIZE |
Sets the size of the transmission buffer for the communications server. This value applies only to VTAM communication and it must be set to the same value on all systems. Specify 1K, 2K, 4K, 8K, or 16K. Default Value: 4K |
|
RETRMAX |
When you tell CA‑L‑Serv to reactivate VTAM communication routes (through the RETRY parameter), this parameter sets the maximum number of retries: To retry indefinitely, specify 0. To retry a designated number of times, specify a value from 1 to 100. Default Value: 0 |
|
RETRY |
Indicates whether CA‑L‑Serv should try to reactivate inactive VTAM communication routes: If you do not want to reactivate routes, specify 0. Otherwise, set the retry interval (in seconds) by specifying a value from 1 to 86400. Default Value: 0 |
|
SCANLIMIT |
Determines the maximum number of rows that the SQL server can search per SQL statement: If you do not want to set a maximum, specify 0. Otherwise, set a maximum by specifying a value from 1 to 999999999. Default Value: 0 |
|
SENDLIMIT |
Sets the maximum number of outstanding send requests per client. Once this limit has been reached, the client must wait for the next data transmission to occur. Specify a value from 1 to 999. Default Value: 32 |
|
SERVERTYPE |
Indicates how requests to access CA‑L‑Serv files should be handled by the file server. Specify one of these values: HOST - Identifies a server as the host server. This server handles all requests for access to files that CA‑L‑Serv is managing. Requests from remote servers are forwarded through the communications server. LOCAL - Handles access requests from the local system only. REMOTE - Forwards access requests for files to your host server. Requests are forwarded through the communications server. Default Value: LOCAL |
|
SQLSERVER |
Activates the CA-L‑Serv SQL server. |
|
XCF |
Indicates whether you want to use XCF communication. Specify YES or NO. By default, CA‑L‑Serv does not use XCF. Specifying YES directs CA‑L‑Serv to automatically determine which systems are in the associated sysplex and dynamically initialize the corresponding XCF group and its members. Default Value: NO |
|
XMVS |
Indicates whether CA‑L‑Serv will be used to communicate between MVS systems. Unless directed to do so by the documentation for the application, specify YES. Default Value: YES |
Notes:
If you shutdown a server (with the DETACH command) and restart it using ATTACH server, the parameter values default to the values in effect at the time of the DETACH (whether set by the ATTACH command or modified by the OPTIONS command).
Examples
ATTACH FILESERVER SERVERTYPE(REMOTE)
ATTACH COMMSERVER ACBNAME(SYS01) XCF(YES)
Note: Since LU 0 is used by default, it is not necessary to specify the associated parameter.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |