Use the following rules to code the Mainframe Server startup parameters in your job stream:
option-name=option-value
The order in which the parameters are coded is irrelevant.
(Optional) Specifies the type of SQL access available in this Mainframe Server.
Valid Entries: R (read-only) or W (read/write)
Default: W
Note: ACCESS=R tells the Mainframe Server to reject SQL maintenance commands, such as INSERT, DELETE, UPDATE, and CREATE. It does not affect locking mechanisms that the SQL engine uses in the Multi-User Facility to ensure data integrity.
If the CAICCI communication protocol is used, APPLID=specifies the Application Identifier of the Mainframe Server. When an operation group of servers exists, the first four characters of this option must be the same for each member of the group. However, each Mainframe Server must have a unique APPLID.
If the TCP/IP communication protocol (z/OS only) is used, APPLID=, SERVERNAME=, and TCPIP_PORT= are used as tokens to uniquely identify the CA Datacom Server Mainframe Server component.
Valid Entries: 1 to 20 alphabetic characters for APPLID and SERVERNAME, following the rules for the SQL names, TCPIP_PORT must be a numeric value from 1024 through 65534
Default: No default
(Optional) Specifies a valid SQL AUTHID to be used as the default by clients of this Mainframe Server. The AUTHID= parameter value is substituted in any non-qualified table, view, or procedure name in SQL queries that are transmitted through the Mainframe Server. AUTHID must already exist on the attached Multi-User Facility.
Note: For more information about creating the AUTHID, see the CA Datacom/DB SQL User Guide.
Valid Entries: Any valid SQL AUTHID
Default: SYSUSR
(Optional) Specifies a user-coded connection exit to replace the security that CA Datacom Server provides through external security. CONEXIT is called before the call to the external security interface. A sample connection exit, SVCXTPR, is provided.
Valid Entries: A valid connection exit program
Default: No default (spaces)
Specifies the number of CA Datacom/DB threads to be dedicated to this Mainframe Server. The MUF uses this number to reserve threads to service requests from the Server. Any number of non‑update requests can share threads. The number to request is determined mainly by the number of concurrent update requests. When a client workstation issues any request causing an update, the thread being used is held for this task until the task issues a COMIT or ROLBK or requests a disconnect.
In estimating the number of DBUSERS, consider the number of update requests operating concurrently a large percentage of the time and allocate a thread for each of these. Additionally, allocate one thread for each five concurrent read-only type requests.
Valid Entries: A number from 1 to 999
Default: No default
(Optional) Specifies the database ID (BASEID) of the Datadictionary database (DATA‑DICT) for the Datadictionary on the Multi-User Facility accessed through this Mainframe Server.
Valid Entries: A valid CA Datacom/DB database ID
Default: 2
(Optional) Specifies the database ID (BASEID) of the Data Definition Directory database (DDD‑DATABASE) for the Datadictionary on the Multi‑User Facility accessed through this Mainframe Server.
Valid Entries: A valid CA Datacom/DB database ID
Default: 15
(Optional) Specifies that any USERID or PASSWORD is converted to uppercase characters. This is intended to force those two values to upper case for JDBC applications. There is currently no provision to convert userid and password to uppercase in the JDBC client code. This parameter has no effect on ODBC applications since the userid and password are converted to uppercase on the client side code. The only exception for ODBC is when the CA Datacom ODBC Setup dialog "DataSource" dialog has the "Mixed-case Password" checkbox is checked. In that case the checkbox is ignored.
Valid Entries: Y or N
Default: N
(Optional) Specifies whether the Mainframe Server attempts to do an external security logon to validate each user.
If LOGON=YES, each user must be authorized to access data through MUF external security.
If LOGON=NO, user IDs are not validated through external security nor passed to MUF.
Note: If LOGON=YES, the SVDBSPR module must reside in an authorized library.
Valid Entries: NO or YES
Default: YES
Specifies a four-character prefix that is used for all plan names that the Mainframe Server creates. Must be four alphanumeric or @, $, or # characters.
Note: Each Mainframe Server that is attached to a same Multi-User Facility must provide a unique PLANNAME prefix to ensure that conflicting PLANNAMEs are not generated in a MUF.
Valid Entries: 4 alphanumeric characters, @, $, or #.
Default: No default
Specifies the communication protocol that is used to transmit data between workstations or client applications and the Mainframe Server.
If CCI is specified, the native TCP/IP protocol (z/OS only) is not available. All other TCP/IP parameters are ignored.
If BOTH is specified, the native TCP/IP interface is initialized (z/OS only). TCPIP_HOST, TCPIP_PORT and TCPIP_CONNECT_QUEUE must be specified, too.
PROTOCOL=BOTH is required for JDBC Type 4 driver connections.
Valid Entries: CCI or BOTH
Default: CCI
(Optional) Specifies a user-coded security exit that is used to enhance the security that CA Datacom Server provides through external security. SECEXIT is called after the call to external security. A sample security exit, SVCXTPR, is provided.
Valid Entries: A valid security exit program
Default: No default (spaces)
Uniquely identifies the Mainframe Server region. Each Server must have a unique name.
Valid Entries: 1 to 32 alphabetic characters, following the rules for SQL names
Default: No default
Note: For more information on the rules for SQL names, see the CA Datacom/DB SQL User Guide.
(Optional) Specifies the status of SQL statement storage when a cursor is closed. Traditionally, The SQL statement storage is kept in memory for reuse if the statement is re-executed, perhaps with different parameters.
SQLMEM=KEEP specifies that SQL statement storage is kept in memory for reuse. It allows an application to prepare a statement once and execute it multiple times without intervening prepares. JDBC applications that use the PreparedStatement interface require SQLMEM=KEEP.
SQLMEM=FREE specifies that SQL statement storage is released upon cursor close. Prepared statement storage is not saved. Any attempt to re-execute a statement without an intervening prepare results in SQLSTATE 07033 and SQLCODE -134 – Unknown dynamic/cursor statement-id (aaaa). SQLMEM=FREE reduces SQL memory usage in MUF.
Valid Entries: KEEP or FREE
Default: KEEP
(Optional) The CA Datacom Server mainframe component behaves as a dynamic SQL application in MUF. SQL Plan Options specify input parameters for SQL preprocessor options that can be set at startup. In most cases, you do not need to change these parameters. Therefore, we recommend that you accept the defaults.
DATE=, TIME=, and DECPOINT= parameters are probably the only parameters you may want to change. The default values for these parameters are appropriate for most PC applications.
For complete details on the purpose of other plan options, see the CA Datacom/DB SQL User Guide.
SQLMODE= DATACOM
CBSIO= 0
ISOLEVEL= C
OPT= P
PLNCLOSE= T
PRTY= 7
TIMEMIN= 0
TIMESEC= 0
WORKSPACE= 16
MSG= NN
STRDELIM= A
DATE=ISO
TIME=JIS
DECPOINT=P
(Optional) Denotes whether the connect/disconnect messages, DSV00035I and DSV00036I, respectively, are to appear on the console or in the Mainframe Server JESLOG or SYSLOG. A value of NO means that DSV00035I and DSV00036I messages are not suppressed and appear on the console and in the JESLOG (z/OS). A value of YES means that they are suppressed from the console or JESLOG/SYSLOG but are written to the SYSPRINT/ SYSLOG output data set. A value of ALL suppresses ALL messages and nothing is written including any warning or error messages.
Valid Entries: NO, YES, or ALL
Default: NO
(For z/OS only) Specifies the number of threads that the Server Mainframe region spawns to service TCP/IP requests. Requires PROTOCOL=BOTH. Ignored if PROTOCOL=CCI.
Valid Entries: 1 to 150
Default: Up to 150
(For z/OS only) Specifies the host name or IP address that is associated with TCPIP_PORT= for TCP/IP transmissions. If TCPIP_HOST=0.0.0.0, the Mainframe Server listens on all addresses using TCPIP_PORT. Requires PROTOCOL=BOTH. Ignored if PROTOCOL=CCI.
Code the TCPIP_HOST parameter if you are using TCP/IP (z/OS only)..
Valid Entries: Host name,LOCALHOST, or IP address (IPv4 or IPv6)
Default: 0.0.0.0
(For z/OS only) Specifies the port number on which the Mainframe Server listens for incoming TCP/IP data traffic. No other TCP/IP service in your environment must use this port assignment. Required if PROTOCOL=BOTH. Ignored if PROTOCOL=CCI.
If TCPIP_PORT is specified in the mainframe component startup option, verify that the value is from 1024 through 65535. If valid, update the PORT NUMBER field with the specified value.
PROTOCOL=BOTH specified without a port number causes the CA Datacom Server to enable TCP/IP communication (z/OS only) on port 5465 as the default port. Without specifying PROTOCOL=BOTH, TCPIP_PORT=nnnnn does not enable TCP/IP communication. The PROTOCOL=BOTH value must be set to BOTH to enable TCP/IP communication.
Valid Entries: 1024 to 65535
Default: 5465
(Optional) Specifies the time in minutes that a connection from a client application can remain idle before an automatic rollback and disconnect occurs. TIMEOUT=1440 (24 hours) specifies that no connection is ever automatically disconnected.
Valid Entries: A number from 1 to 1440
Default: 120
(Optional) Specifies the time interval in minutes for which the Mainframe Server waits to initiate a timeout task. The timeout task reviews all tasks and will automatically rollback and disconnect those tasks for which the value in the TIMEOUT= parameter has exceeded. This parameter allows a Mainframe Server with little or no activity to time out idle tasks. A value of 0 means that a timeout task is not started at periodic intervals and timeouts only occur when there are other tasks in the Server.
Valid Entries: A number from 0 to 720
Default: 90 minutes
(Optional) Starts the Trace Facility.
Valid Entries: NO or YES
Default: NO
(Optional) Enables a SQL Syntax trace and defines the userids to trace. When enabled, the SQL syntax generated by the user's application is written to SYSPRINT. The output of the SQL syntax trace is typically brief but depends on the length of the SQL statements. For more information, see the SQL Syntax Trace Example Output.
Up to five userids can be traced at one time.
The TRACEON=YES option overrides TRUSERx=. If TRACEON=YES is also specified in the startup JCL, the SQL syntax trace entries do not display.
Valid Entries: A valid userid or TRUSRALL
Default: No default
Specifies the priority that CA Datacom Server uses for dynamically built URTs. This parameter is required if DYNURT=YES.
Valid Entries: A number from 1 to 15
Default: 7
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|