(COBOL only.) Specifies if an apostrophe (') is the delimiting character for character string literals generated in the SQL Communication Area (SQLCA) and the SQL Work Area (SQLWA). This option is provided for compatibility with COBOL compilers which have a similar option.
This option is mutually exclusive with the QUOTE= option, that is to say, if you specify APOST=, do not specify QUOTE= in the Preprocessor options. If neither APOST= or QUOTE= is specified, the Preprocessor uses the default of APOST=Y.
Y (for yes)
Y for z/OS environment
Specifies the associated authorization ID for the program's plan.
Any SQL objects (tables, views, synonyms) you create in your program are owned by this authorization ID unless you specifically qualify those objects with a different authorization ID within the program.
The authorization ID name must be 1 to 18 characters.
An authorization ID name of from 1 to 18 characters
(No default)
Specifies an I/O limit interrupt value for all SQL commands that create a set. This option allows application environments to establish their own maximums in I/O and set processing relative to their own requirements.
You can use this option to limit the computer resources that can be used for each execution of the following statements in the plan:
For cursors, the limit applies to the total resources used to OPEN and FETCH all rows of the cursor.
A counter is incremented each time a different index or data block is accessed, and each time 100 rows are read. Execution is terminated, and SQL return code -137 is returned when this counter exceeds the limit.
The value of the counter is reported in the Statistics and Diagnostics Area (PXX) at the end of each request to the Multi-User Facility when any SQL traces are in effect.
For cursor, SELECT INTO, INSERT, UPDATE and DELETE, you can use the total estimated cost reported in the SYSADM.SYSMSG table when bind time optimization messages are requested with the MSG= plan option as a guide for setting the limit. For CREATE INDEX, DROP INDEX, and ALTER TABLE, estimate the limit as the number of bytes in the table divided by 2000. You must set the limit for the most expensive statement in the plan.
A value of 0 (zero) means no limit.
Note: Here is how the CBSIO plan option is calculated: to 500,000 is added the amount over 500,000 multiplied by 10,000. For example, given a value of 500,100, the calculation would be 500,000 + (100 * 10,000) = 500,000 + 1,000,000 = 1,500,000.
0—524286
0
This plan option allows the creator of a plan to specify whether that plan is to be secured.
If CHECKPLAN=Y, any accessor ID which attempts to execute the plan must have the PLAN EXECUTE privilege for that plan.
If CHECKPLAN=N, any accessor ID can execute the plan (table-level privileges, however, are still checked).
Note: For additional information about plan security, see GRANT and REVOKE. Also see the information on plan security in the CA Datacom Security Reference Guide.
See the table of valid combinations of CHECKPLAN=, CHECKWHEN=, and CHECKWHO= presented previously.
Y or N
CHECKPLAN=N is the default only if the CHECKPLAN= parameter in the PLANSEC Multi-User startup option was not specifed. If the CHECKPLAN= parameter in PLANSEC was specified, its value is the default here. See the CA Datacom/DB Database and System Administration Guide for more information about Multi-User startup options.
Specifies whether table-level privileges are to be checked at bind or runtime.
If CHECKWHEN=BIND, then CHECKWHO=BINDER must be specified (it is impossible for SQL to know all potential executors). Similarly, if CHECKWHO=ACCESSOR, then CHECKWHEN=EXECUTE must be specified.
Note: For additional information about plan security, see GRANT and REVOKE. Also see the information on plan security in the CA Datacom Security Reference Guide.
See the table of valid combinations of CHECKPLAN=, CHECKWHEN=, and CHECKWHO= presented previously.
BIND or EXECUTE
EXECUTE is the default only if the CHECKWHEN= parameter in the PLANSEC Multi-User startup option was not specifed. If CHECKWHEN= in PLANSEC was specified, its value is the default here. See the CA Datacom/DB Database and System Administration Guide for more information about Multi-User startup options.
Used to specify whether table-level privileges is checked at bind or execute time, and whether the access rights of the binder or the executor are checked. If CHECKWHO=BINDER, the only privilege needed by an accessor ID to run that plan is the PLAN EXECUTE privilege (all table-level privileges required to execute the plan are checked using the binder's accessor-ID). Since the CHECKWHO=BINDER type of plan allows the binder to effectively grant temporary privileges to accessors who use the plan, the ability to create CHECKWHO=BINDER plans must be strictly controlled. To create a CHECKWHO=BINDER plan, you must possess the CHECKBINDER system privilege. See the information about the granting and revoking of the CHECKBINDER system privilege in the CA Datacom Security Reference Guide.
Because it is impossible for SQL to know all potential executors, specify CHECKWHO=BINDER if CHECKWHEN=BIND and CHECKWHEN=EXECUTE if CHECKWHO=ACCESSOR.
Note: For additional information about plan security, see GRANT and REVOKE. Also see the information on plan security in the CA Datacom Security Reference Guide.
See the table of valid combinations of CHECKPLAN=, CHECKWHEN=, and CHECKWHO= on presented previously.
ACCESSOR or BINDER
ACCESSOR is the default only if the CHECKWHO= parameter in the PLANSEC Multi-User startup option was not specified. If the CHECKWHO= parameter in PLANSEC was specified, its value is the default here. See the CA Datacom/DB Database and System Administration Guide for more information about Multi-User startup options.
(COBOL only.) Specifies the host language, either OS/VS COBOL or VS/COBOL II.
COBOL II VS/COBOL II Release 3 or later is supported. The CMP2 option is not supported. When using nested programs all SQL statements and any host variables they reference must be within the first program, and all programs must have a DATA DIVISION, a PROCEDURE DIVISION, and a WORKING STORAGE section.
OSVS, VSCOB2
OSVS
Specifies the DATE output format as follows:
|
Entry |
Format |
Description |
|---|---|---|
|
ISO |
yyyy-mm-dd |
International Standards Organization |
|
USA |
mm/dd/yyyy |
IBM USA standard |
|
EUR |
dd.mm.yyyy |
IBM European standard |
|
JIS |
yyyy-mm-dd |
Japanese Industrial Standard |
ISO, USA, EUR, JIS
The default is the value specified in the Multi-User Facility's DATE startup option.
Note: ISO is the default of the Multi-User Facility's DATE startup option.
(COBOL, PL/I, and C only.) Specify C if you want a comma (,) to be the decimal point indicator in decimal, numeric, and floating-point literals.
Specify P if you want a period (.) to be the decimal point indicator.
If the comma is specified as the decimal point indicator, commas which are used as separators must be followed by a space, as in COBOL. Also, any comma followed by a space is interpreted as a separator, even if the comma is preceded by a numeric digit.
C (for comma)
P (for period)
P
(PL/I only.) Same as DECPOINT= (see above).
(COBOL only.) Specify if you want the Preprocessor to generate COBOL items in the WORKING-STORAGE SECTION or LOCAL-STORAGE SECTION of the program.
If you specify W, the Preprocessor generates the items in the WORKING-STORAGE SECTION of the program.
If you specify O (a letter O, not a zero) for GENSECTN=, data structures (SQLCAs, SQLWAs, SQLDAs), used when SQL statements are executed, are generated in a LOCAL-STORAGE section. Addresses of host variables are stored into these data structures, and VALUE clauses may be used.
Memory for a LOCAL-STORAGE section is allocated and value clauses are executed each time a program is called, as opposed to once per run-unit for WORKING-STORAGE sections. LOCAL-STORAGE therefore provides a way to make programs re-entrant.
When you use a LOCAL-STORAGE section:
W (Preprocessor generates COBOL items in the
WORKING-STORAGE SECTION)
O (Preprocessor generates COBOL items in the
LOCAL-STORAGE SECTION)
W
(PL/I and Assembler only.) Causes the necessary storage for SQL to be generated. GENSTOR= is valid only when specified in the source (the $DBSQLOPT statement).
TOP specifies the top of the source.
BOT specifies the end of the source.
HERE specifies after this point in the source.
If not specified, generated storage is placed before the last END statement.
(PL/I and Assembler only.) Causes the initialization code to be generated after a specified point in the source. GENINIT= is valid only when specified in the source (the $DBSQLOPT statement).
TOP specifies the top of the source.
BOT specifies the end of the source.
HERE specifies after this point in the source.
If not specified, generated is placed before the last END statement.
(For Assembler) Specifies the generation of control structures. That is, SQL Work Areas (SQLWAs) that are to be used in conjunction with SQL statements.
With INLINE=N, one set of SQLWAs is generated for each SQL statement. But with INLINE=Y, the Preprocessor generates one set of SQLWAs to use for all SQL statements. INLINE=Y generates more executed code but much less overall code, avoiding the addressability problems (that is, not enough base registers) that can occur when INLINE=N.
Note: Because the C Preprocessor uses the inline method exclusively, the C Preprocessor does not look at the INLINE= option. For that reason, an error may occur if you code the INLINE= option when using the C language. Therefore, when using C, the INLINE= option should not be coded.
Y or N
N
Specifies the isolation level, or the degree to which a unit of recovery in your application is isolated from the updating operations of other units of recovery.
If you specify U (for uncommitted data), no locks are acquired for any rows accessed. Your application can access rows that have been updated by another unit of recovery, even though those changes may not have been committed. Since no locks are acquired, no updates, deletes, or inserts may be done by a unit of recovery operating in the U isolation level.
If you specify C (for cursor stability), locks are acquired for all rows accessed. Your application therefore only accesses rows that contain committed data. For updateable cursors (those that have associated UPDATE WHERE CURRENT OF or DELETE WHERE CURRENT OF statements), exclusive locks are acquired. For read-only cursors, share locks are acquired. When a row is fetched, the lock on the previous row of the cursor is released unless the row was modified. All locks are released when the unit of recovery ends, at which time changes are either committed (COMMIT WORK) or rolled back (ROLLBACK WORK).
In C isolation level, the current row of a cursor may or may not be locked while your application is accessing it, depending on whether the cursor is updateable. For updateable cursors, the current row of the cursor is always locked with an exclusive lock when your application fetches it. For read-only cursors, the SQL Facility may read ahead and transfer multiple rows from the Multi-User Facility to your application's region. In this case, the current row of the cursor could possibly no longer be locked when your application fetches it. If your application requires the current row of a cursor to be locked, it must use an updateable cursor to fetch the row.
If you specify R for repeatable read, data once seen by a transaction cannot be changed by another task while the first is still active. Also, other records cannot be added or updated if it would cause them to participate in the set of records seen by the first transaction.
If SQL receives a blank or zero in the ISOLEVEL= specification from any of the SQL access methods, the default for the appropriate SQLMODE is automatically set. If an invalid ISOLEVEL= relative to the effective (that is, specified or defaulted) SQLMODE is explicitly set (nonblank and nonzero), an appropriate SQLCODE and error message is produced.
Note: If you specify ANSI or FIPS for the SQLMODE= option, you must also specify ISOLEVEL=C. For more information, see SQLMODE= later in this chapter.
To acquire exclusive control of a table, see LOCK TABLE. Also see SQL Plan Options Special Topics.
U (No locks are acquired, no changes are allowed)
C (Locks are acquired, changes are allowed)
R (Locks are acquired, restricted changes are allowed)
C (For ANSI and FIPS SQLMODEs)
U (For all other SQLMODEs)
Note: The both parameter of the SQLOPTION Multi-User startup option controls whether you are allowed to mix the use of isolation level U and C plans under a single logical unit of work (LUW) for those LUWs not running any SQLMODE ANSI or FIPS plans. YES specified for the both option of SQLOPTION indicates that mixing is allowed.
(z/VSE only) Specifies an optional file type for SQL INCLUDE files in z/VSE. The type is one letter.
Note: In COBOL, the ITYP= specification can be overridden by explicitly coding a file type on the INCLUDE statement.
Any letter (including, although not recommended, the standard default letters listed below)
C for COBOL, P for PL/I and Assembler, H for the C language
(PL/I, C, and Assembler only.) Specifies the source language to be processed. This option overrides the initial values for MARGINS= established at initialization.
Note: Specifying MARGINS= is not allowed if you are using the C language.
PLI for PL/I
C for the C language
ASM or ASSEMBLER for Assembler
PLI for PL/I
No default for the C language
No default for Assembler
(PL/I and Assembler only.) Specifies the valid columns of the source record inclusively.
Do not specify MARGINS= in the $DBSQLOPT statement (source code). Specify MARGINS= in the OPTIONS file or in the PARM= text on the EXEC statement of the JCL.
In PL/I you can specify (start, end) or (left, right). For example: (s) or (s,e) or (,e). In Assembler, you can specify (start, end, continue) or (left, right, continue). For example: (s) or (s,e) or (,e) or (s,e,c).
Values are merged with defaults, that is to say, if only one value is specified, the default is assigned to the nonspecified value.
An example in PL/I: if (,71) is specified after LANGUAGE=, the result is (2,71) because 2 is the default for the start value. Or, if (5) is specified, the result is (5,72) because 72 is the default for the end value.
An example in Assembler: if (,71) is specified, the result is (1,71) because 1 is the default for the start value. Or, if (5) is specified, the result is (5,71) because 71 is the default for the end value. The continuation field is the next column after the end (right) margin.
1—30, s < e, and width >= 70
PL/I defaults are:
1 (start) 72 (end) if specified before LANGUAGE=
2 (start) 72 (end) if specified after LANGUAGE=
Assembler defaults are:
1 (start)
71 (end)
16 (continue)
(COBOL only.) Specifies the level of messages you wish the SQL Optimizer to generate. Specify the optimization message in groups of two letters, for example MSG=xy, where S and D and N replace the x and y, and where:
See SQL Query Optimization Messages for a description of the SYSMSG table.
Note: Messages for a plan are deleted when the plan is deleted. When you re-preprocess a program, the Preprocessor deletes the previous plan and therefore also its diagnostic messages.
Valid combinations of S and D and N are given in Valid Entries below, where:
SS, DD, SD, DS, NS, ND, DN, SN, NN
NN
(PL/I, C, and Assembler only.) Refers to messages generated by the Optimizer when the statement is executed (these messages may be retrieved from the SYSMSG table after the statement has been executed). See SQL Query Optimization Messages for a description of the SYSMSG table.
Note: Messages for a plan are deleted when the plan is deleted. When you re-preprocess a program, the Preprocessor deletes the previous plan and therefore also its diagnostic messages.
S, D, N
N
(PL/I, C, and Assembler only.) Refers to precompile-time messages. These messages are included at the end of the Preprocessor Source Listing.
S, D, N
N
Specifies the join optimization mode. P specifies normal join optimization. Specify M (manual join order) if the normal join optimization is unacceptable and you want tables joined as they are listed in the FROM clause. This results in a nested loop join.
Do not specify E; it is reserved for future use.
P or M
P
Specifies the number of output lines per page on SYSPRINT.
For COBOL: 0—120
For PL/I, C, and Assembler: 10—255
55
This option enables the CA Datacom Datadictionary name of a program to be changed without requiring the program source itself to be altered. The program name of a procedure must match its external (or load module) name.
The syntax is as follows: PGMNAME=name
The name specified must be a CA Datacom Datadictionary entity-occurrence name. It overrides any PROGRAM-ID specified in COBOL. If the program is a procedure, this name must match both the generated load module name and the EXTERNAL NAME specified in the CREATE PROCEDURE statement.
A valid name as described above
(No default)
Specifies the name for your plan, a name that should be unique within your authorization ID. You can use MIXED strings in a plan name, that is, strings in which both Double-Byte Character Set (DBCS) and Single-Byte Character Set (SBCS) characters are used.
The plan name must be 1 to 18 bytes in length. The first character of the plan name must be alphabetic (including Katakana symbols) or a Shift-Out character (when you are using MIXED strings). Shift-Out and Shift-In characters (used to delimit DBCS substrings) count toward the 18-byte length limit. If you specify more than 18 bytes for the name, the Preprocessor truncates your entry to the first 18 bytes.
For more information on MIXED data and MIXED strings, see Character Strings.
If you specify a name you used previously for a plan, you are, in essence, replacing that existing plan with a new plan. For example, you have an existing plan named PAYROLL. If you specify PAYROLL as the name of a new plan, this new plan replaces the previous plan named PAYROLL.
If you do not specify a plan name, the Preprocessor uses the PROGRAM-ID specified in your program.
A name 1 to 18 bytes long, first character alphabetic (including Katakana symbols) or a Shift-Out character (when you are using MIXED strings)
In COBOL and PL/I, there is no default.
(PL/I and Assembler only.) Same as PLANAME= (see previous description).
Specifies when the plan, and any User Requirements Tables automatically opened by the SQL Manager, are closed.
If you specify T, the plan, and any User Requirements Tables automatically opened by the SQL Manager, close when the transaction ends, that is to say, an SQL COMMIT WORK or ROLLBACK WORK statement, a CA Datacom/DB LOGCP, LOGCR or LOGTB command, or a CA Datacom CICS Services DEQUE.
We recommend the T option for a CICS environment. We also recommend PLNCLOSE=T for procedures. We recommend the R option for batch programs.
If you specify R, the plan, and any User Requirements Tables automatically opened by the SQL Manager, close when the run unit ends, or when a CA Datacom/DB CLOSE command is issued. In a CA Datacom CICS Services environment, the run unit ends only when CICS is terminated or when the SQL User Requirements Table (usually URT 20) is closed using the DBOC command. When ISOLEVEL=U is used, because no locks are acquired by the MUF (and therefore no DEQUE commands are issued by CA Datacom CICS Services), the plan and User Requirements Tables are not closed at the end of each CICS transaction, even if PLNCLOSE=T. A PLNCLOSE=R plan can be preprocessed or rebound with DDOL or DBSRFPR before the run unit ends if no current unit of recovery has executed the plan.
User Requirements Tables opened on behalf of a plan with PLNCLOSE=R are not closed until the plan closes when the SQL=YES User Requirements Table (default User Requirements Table 020) is closed. If User Requirements Tables accessing a database need to be closed to perform utility functions, you can close those SQL-generated User Requirements Tables accessing a database by deleting (if you have the delete privilege) those rows in the SQL_STATUS_URT_INACTIVE virtual table (this virtual table is a view on the SQL_STATUS_URT table with the restriction that only User Requirements Tables for the current run unit with zero users are selected). Following is an example query that can be executed from any tool that uses SQL, where nnn is the database-ID to be closed. Any valid WHERE clause can be used, including no WHERE clause to close all User Requirements Tables.
DELETE FROM SYSADM.SQL_STATUS_URT_INACTIVE WHERE DBID = 'nnn';
Closing these User Requirements Tables does not keep them from being reopened. There can also be other User Requirements Tables that are active, meaning they have one or more plans that have accessed the table in their current transaction. In addition, other run units can also have User Requirements Tables open for the database. Use the following query to see which User Requirements Tables are open for a database:
SELECT * FROM SYSADM.SQL_STATUS_URT WHERE DBID = 'nnn';
For information about possible performance enhancement using the Least Recently Used (LRU) statement cache to disconnect the caching of plan statements from the control of the PLNCLOSE= option, see LRU Statement Cache.
T (close when transaction ends)
R (close when run unit ends)
R
Is valid for COBOL, PL/I, Assembler, and C. If this option is specified, SQL prepares the program for execution as a procedure. This option is required for programs intended to run as procedures. It is prohibited for programs not run as procedures.
Note: All procedures must be preprocessed, even if there are no embedded SQL statements in a particular procedure.
Important! Use PROCSQLUSAGE= only as documented. If it is specified or omitted inappropriately, the program can fail in an unpredictable way before SQL has a chance to detect the error.
To support procedure execution, the preprocessors add code to programs that specify PROCSQLUSAGE=, thus making proper use of the option critical. Therefore, make certain you have coded this option accurately. CA Datacom reserves the right to add edits at any time.
Specifying NO means the procedure does not call CA Datacom SQL.
Specifying CONTAINS means that the procedure calls CA Datacom SQL but contains no SELECT, SELECT INTO, preparations of dynamic-select, INSERT, UPDATE, or DELETE statements.
Specifying READS means that the procedure contains a SELECT, SELECT INTO, or preparation of a dynamic-select statement, but does not contain INSERT, UPDATE, or DELETE statements.
Specifying MODIFIES means that the procedure contains at least one INSERT, UPDATE, or DELETE statement.
CA Datacom only checks for the existence of calls to CA Datacom SQL in the procedure at the time of the CREATE PROCEDURE statement. (An error is produced, however, if NO is specified in a program containing SQL, or vice versa.) CA Datacom requires the value specified to match the corresponding specification in the CREATE PROCEDURE statement.
NO, CONTAINS, READS, or MODIFIES
(No default)
Specifying PRTREXIT= allows you to write a printer exit routine to print the output instead of allowing the Preprocessor to write to SYSPRINT. The load-module-name is the name of your printer exit routine. When your printer exit routine is called, the registers are as follows:
Address of parameter list as follows:
Word 1 = x'00000014'
Word 2 = AL1(length of print line)
AL3(address of print line)
Word 3 = Address of a 1-byte top-of-page indicator:
if bit x'20' is on, top-of-page is requested
Address of a register save area which you must use to save and restore the CA Datacom/DB registers according to standard linkage conventions.
Address to return to inside CA Datacom/DB.
Address of the entry point of your printer exit.
On return from your routine, the contents of all registers (except 15) should contain what they contained before the exit was called. Register 15 should contain 0 unless a failure occurred. The Preprocessor aborts processing if a nonzero register 15 is returned.
Remember to concatenate the library containing your printer exit to the end of the Preprocessor load library concatenation in your JCL.
If you do not specify a load-module-name (with PRTREXIT=), processing continues to write to SYSPRINT instead of calling the printer exit.
A load-module-name of up to eight characters
(No default)
Specifies the priority of the SQL requests from the plan within the Multi-User Facility. The lowest priority is 1, while 15 is the highest priority.
If you need more information about specifying a priority, see your Database Administrator.
1—15
7
(COBOL only.) Specifies if a quotation mark (") is the delimiting character for character literals generated in the SQL Communication Area (SQLCA) and the SQL Work Area (SQLWA). This option is provided for compatibility with COBOL compilers which have a similar option.
This option is mutually exclusive with the APOST= option, that is to say, if you specify QUOTE=, do not specify APOST= in the Preprocessor options.
If neither QUOTE= or APOST= is specified, the Preprocessor uses the default of QUOTE=Y for z/VSE environments.
Y (for yes)
Y for z/VSE environments
(Assembler only.) See USRNTRY= later in this chapter.
Use this option to specify whether to drop or not to drop security privileges granted on a PLAN when a program is re-preprocessed.
SAVEPLANSEC=Y means PLAN privileges are not dropped and therefore do not have to be regranted after re-preprocessing a program.
SAVEPLANSEC=N means PLAN privileges are dropped (revoked).
Y or N
N
(PL/I, C, and Assembler only.) Specifies the member name and type for the source residing in a z/VSE library. The value specified must be of the form: name.type (for example, SMBR=ABC.P where ABC is the name and P the type).
If SMBR= is not specified, the source is assumed to be on sequential disk. If you specify SMBR=, you must do so either in the execution parameters or the options file. If you specify SMBR= when the source is on a sequential disk file, an open error results.
A valid member name and a type of length 1
(No default)
Specifies the mode in which to process the program. If you specify SQLMODE=DATACOM, your program is processed in extended mode, which means CA Datacom/DB extensions to the standards are allowed in your SQL statements. Names for tables, columns, views, synonyms and cursors can be 1 to 32 characters in length if SQLMODE=DATACOM. Authorization IDs and plan names must be 1 to 18 characters in extended mode.
Specifying SQLMODE=DB2 allows you to use the CA Datacom/DB DB2 compatibility mode. CA Datacom DB2 Transparency is required to use the CA Datacom/DB DB2 mode. The DB2 compatibility mode allows you to use application programs written for IBM DB2. CA Datacom/DB recompiles and executes DB2 application programs against CA Datacom/DB tables without your having to change the source code of those programs. Plans created by the CA Datacom DB2 Transparency Bind program also execute in DB2 mode.
In COBOL and PL/I you can specify SQLMODE=DB2A86 to use the CA Datacom/DB DB2 compatibility mode while conforming to ANSI 86 standards. In COBOL and PL/I, specify ANSI or FIPS for your program to be processed in ANSI or FIPS mode, which means all your SQL statements must be coded according to ANSI or FIPS standards. When ANSI or FIPS mode is specified, the ISOLEVEL=U option is not allowed. ISOLEVEL=C must be specified when SQLMODE=ANSI or SQLMODE=FIPS. Authorization IDs and plan names must be 1 to 18 characters in ANSI mode. Names for tables, columns, views, synonyms and cursors must be 1 to 18 characters in length if SQLMODE=ANSI or SQLMODE=FIPS.
Note: The SQLMODE Multi-User Facility startup option must be set to DATACOM before this Preprocessor option is effective. If the SQLMODE Multi-User Facility startup option is set to ANSI or FIPS, this Preprocessor option is overridden and all SQL statements must comply with ANSI or FIPS standards. See your Database Administrator for information on the value assigned to the SQLMODE Multi-User Facility startup option.
For COBOL and PL/I:
DATACOM, DB2, DB2A86, ANSI, FIPS
For Assembler: DATACOM, DB2
DATACOM
(COBOL, PL/I, and C only.) Specifies whether you want the string delimiter, used to delimit character string literals in SQL statements, to be an apostrophe (') or a quotation mark (").
The escape character, used to enclose delimited SQL identifiers, is the apostrophe if the string delimiter is the quotation mark, or the quotation mark if the string delimiter is the apostrophe. See Delimited SQL identifiers for more information on delimited SQL identifiers.
Specify A for apostrophe or Q for quotation mark.
A, Q
A
(PL/I only.) Same as STRDELIM= (see previous description).
(PL/I only.) Same as STRDELIM= (see previous description).
Specifies the TIME output format as follows:
|
Entry |
Format |
Description |
|---|---|---|
|
ISO |
hh.mm.ss |
International Standards organization |
|
USA |
hh:mm AM or PM |
IBM USA standard |
|
EUR |
hh.mm.ss |
IBM European standard |
|
JIS |
hh:mm:ss |
Japanese Industrial Standard |
ISO, USA, EUR, JIS
The default is the value specified in the Multi-User Facility's TIME startup option.
Note: ISO is the default of the Multi-User Facility's TIME startup option.
Specifies exclusive control wait time limit in minutes.
This option allows a program to either wait or not wait for an explicit amount of time when another job is holding a requested record under exclusive control. If the specified time is exceeded, the application program receives a -117 value in the SQLCODE of the SQL Communication Area and a CA Datacom/DB 61 return code to inform the user that the record was not available.
Specifying a zero for both TIMEMIN= and TIMESEC= means that there is no time limit, and without a limit on the wait time, a wait forever condition is possible.
TIMEMIN=0 and TIMESEC=1 means do not wait at all. Do not specify nonzero values for both TIMEMIN= and TIMESEC=.
If you are using CA Datacom STAR for distributed processing, see CA Datacom STAR documentation before specifying this option.
0—120
0
Specifies exclusive control wait time limit in seconds.
This option allows a program to either wait or not wait for an explicit amount of time when another job is holding a requested record under exclusive control. If the specified time is exceeded, the application program receives a -117 value in the SQLCODE of the SQL Communication Area and a CA Datacom/DB 61 return code to inform the user that the record was not available.
Specifying a zero for both TIMEMIN= and TIMESEC= means that there is no time limit, and without a limit on the wait time, a wait forever condition is possible.
TIMESEC=1 and TIMEMIN=0 means do not wait at all. Do not specify nonzero values for both TIMEMIN= and TIMESEC=.
If you are using CA Datacom STAR for distributed processing, see CA Datacom STAR documentation before specifying this option.
0—120
0
(PL/I and Assembler only.) Specifies whether report should be uppercase only. The data is not affected.
Do not specify UCRPT= in the $DBSQLOPT statement (source code). Specify UCRPT= in the OPTIONS file or in the PARM= text on the EXEC statement of the JCL. In PL/I, if this is the first option in the execution parameters, the entire report is in uppercase.
In Assembler, if this is the first option in the option file, the report is uppercase, except for the initial title lines. To have everything in uppercase, the option should be coded in the execution parameters.
Y, N
N
(COBOL and Assembler only.) The description of USRNTRY= differs in COBOL and Assembler.
Use USRNTRY= in COBOL to specify the entry point in the COBOL program. The value you assign this option must match the value specified for the USRNTRY= parameter of the User Requirements Table.
The default is DBMSCBL. If you have changed this in the User Requirements Table, you must enter the same entry point name as specified in the User Requirements Table. Specify NONE if no entry point is to be generated (used when an SQL program is called by another program).
Valid Entries: DBMSCBL or
An entry point name consistent with COBOL naming conventions, or
NONE
Default Value: DBMSCBL
USRNTRY= works with the REFNTRY= Preprocessor option to cause generation of an entry point that allows use of a single User Requirements Table with OPEN=DB for many separate programs. USRNTRY= and REFNTRY= are for Assembler batch mode only. Following is shown the generation:
usrntry-name EQU refntry-name
ENTRY usrntry-name
Use USRNTRY= to specify the name of the generated entry point. USRNTRY= may be entered in two ways. If USRNTRY=NONE, no entry point is generated. If any other value is entered, that value is considered a valid name. This name is also the name in the User Requirements Table USRNTRY= operand. If USRNTRY= is not specified, then a default name, SQLEXECE, may be used to generate the entry point.
REFNTRY= is the name of a CSECT or ENTRY in the program being processed. This name represents the point where the program would get control when called.
In DATACOM mode, USRNTRY= and REFNTRY= are not required. If REFNTRY= is coded, the entry point is generated. If USRNTRY= is not coded when REFNTRY= is, the default name is used. Specifying USRNTRY= without REFNTRY= causes an error.
In DB2 mode, the entry point generation must be specified or explicitly suppressed. To specify generation, REFNTRY= must be coded, but in this case USRNTRY= is optional since the default name, SQLEXECE, is taken. To suppress generation, USRNTRY=NONE must be entered.
Valid Entries: A name of up to 8 characters or NONE for USRNTRY=, or for REFNTRY= a name of up to 8 characters
Default Value: SQLEXECE is the default for USRNTRY=, but for REFNTRY= there is no default
Whether view security is used for a particular plan is based on the value of the VIEWSEC= Preprocessor plan option. If VIEWSEC= is not specified, whether a plan uses view security is determined by the value of the view-security specification in the SQLOPTION Multi-User startup option. If neither VIEWSEC= nor the view-security specification in SQLOPTION is used, view security is not used for newly bound or rebound plans.
Specify Y to indicate that view security is to be used during the execution of newly prepared and newly rebound plans.
Specify N to indicate that view security is not to be used during the execution of newly prepared and newly rebound plans.
Note: The default for the VIEWSEC= Preprocessor option is the value of the view-security option in the SQLOPTION Multi-User startup option (see the CA Datacom/DB Database and System Administration Guide for more information on SQLOPTION) or N if no default was specified.
Also note, the choice of security method is made at prepare-time rather than during execution. A choice of Y is rejected if view security has not been activated for the Multi-User Facility using external security. See the CA Datacom Security Reference Guide for more information.
Y or N
Value of the view-security specification in the SQLOPTION Multi-User startup option, which itself defaults to N
Important! Subsequently rebound plans (rebound explicitly or automatically) that do not have an explicit view security specification are caused by the value of the SQLOPTION view-security option to change security methods, if necessary, to match the specification. Be aware, therefore, that the security method used by existing plans can be changed intentionally or inadvertently in this way.
Use WORKSPACE= only at the direction of CA Support.
This option specifies an increase in the amount of workspace used at plan execution time. The default is 0 if not specified or an incorrect value is given.
0 to 128
0
|
Copyright © 2014 CA.
All rights reserved.
|
|