17.10 Supported client environment definitions

Table 17-46 lists the client environment definitions that can be specified with the JDBC driver. The numbers in the list correspond to the numbers of the individual environment variables in 6.6.4 Environment definition information.

Table 17-46 Client environment variables that can be specified with the JDBC driver

No.Environment variable nameFunctionEnvironment variable type
1PDHOSTSpecifies the host name of the HiRDB server to be connected.System configuration
2PDNAMEPORTSpecifies the port number of the HiRDB server.
3PDFESHOSTSpecifies the host name of the front-end server.
4PDSERVICEGRPSpecifies the server name of the single server or front-end server.
5PDSRVTYPESpecifies the HiRDB server type.
6PDSERVICEPORTSpecifies the port number for high-speed connection.
8PDCLTRCVPORTSpecifies the client receive port number.
9PDCLTRCVADDRSpecifies the IP address or host name of the client.
19PDUSERSpecifies the authorization identifier and password. In UNIX, this environment variable can be omitted.User execution environment
20PDCLTAPNAMESpecifies UAP identification information (UAP identifier) of the UAP that accesses the HiRDB server.
23PDDBLOGSpecifies whether or not the database update log is to be retrieved when the UAP is executed.
24PDEXWARNSpecifies whether return codes with warnings are to be accepted from the server.
25PDSUBSTRLENSpecifies the maximum number of bytes representing one character.
29PDCLTGRPSpecifies a client group name when the connection frame guarantee facility for client groups is used.
31PDAUTORECONNECTSpecifies whether or not the automatic reconnect facility is to be used.
32PDRCCOUNTSpecifies the number of times the CONNECT statement is retried by the automatic reconnect facility.
33PDRCINTERVALSpecifies the CONNECT retry interval at which the automatic reconnect facility executes reconnect processing.
34PDUAPENVFILESpecifies the UAP environment definition file that defines the execution environment if the UAP is to be executed in a separate environment.
35PDDBBUFLRUSpecifies whether the LRU method is to be applied to processing when a page accessed by the UAP is cached to the global buffer.
36PDHATRNQUEUINGSpecifies that the client does not use the transaction queuing facility.
46PDCWAITTIMESpecifies the maximum time that the HiRDB client waits for a response from the HiRDB server after sending a request to the HiRDB server.System monitoring
47PDSWAITTIMESpecifies the maximum time that the HiRDB server waits for the next request from the HiRDB client to arrive after returning a response to the previous request from the HiRDB client.
This function monitors the time during transaction processing.
48PDSWATCHTIMESpecifies the maximum time that the HiRDB server waits for the next request from the HiRDB server to arrive after returning a response to the previous request from the HiRDB client.
This function monitors the time other than the transaction processing time.
49PDCWAITTIMEWRNPNTSpecifies the output timing of the SQL runtime warning information file when the SQL runtime warning output facility is used. The output timing is specified as a percentage of the maximum time that the HiRDB client waits, or as an amount of time.
54PDCONNECTWAITTIMESpecifies the maximum time that the HiRDB client waits for a response from the HiRDB server when it connects with the HiRDB server.
55PDCLTPATHSpecifies the storage directory for SQL trace files and error log files created by the HiRDB client.Troubleshooting
56PDSQLTRACE#Specifies the size (bytes) of the SQL trace file into which SQL trace information for the UAP is to be output.
59PDPRMTRCSpecifies whether parameter information and retrieval data are to be output in the SQL trace information.
60PDPRMTRCSIZESpecifies the maximum data length of the parameter information and retrieval data to be output in the SQL trace information.
62PDUAPREPLVLSpecifies output information for UAP statistical reports.
63PDREPPATHSpecifies whether UAP statistical report files are to be output to a different directory from the directory specified by PDCLTPATH.
64PDTRCPATHSpecifies the storage directory for dynamic SQL trace files.
66PDSQLTEXTSIZESpecifies the size of the SQL statement to be output to the SQL trace.
68PDRCTRACESpecifies the size of the output file for the UAP reconnect trace information.
69PDWRTLNPATHSpecifies the storage directory for files to which value expression values of WRITE LINE statements are to be output.
70PDWRTLNFILSZSpecifies the maximum size of the files to which value expression values of WRITE LINE statements are to be output.
71PDWRTLNCOMSZSpecifies the total size of the value expression values in WRITE LINE statements.
74PDVWOPTMODESpecifies whether the access path information file is to be retrieved.Access path information file for the access path display utility
78PDSTJTRNOUTSpecifies whether UAP statistical information is to be output to a statistical log file for each transaction.Output unit for UAP statistical information
79PDLOCKLIMITSpecifies the maximum number of lock requests that a UAP can issue to one server.Lock
80PDDLKPRIOSpecifies the deadlock priority value of the UAP.
81PDLOCKSKIPSpecifies whether an unlocked conditional search is to be performed.
82PDFORUPDATEEXLOCKSpecifies whether WITH EXCLUSIVE LOCK is to be applied to the lock option of SQL statements in which the FOR UPDATE clause is specified (or assumed).
83PDISLLVLSpecifies the data guarantee level of an SQL statementSQL-related
84PDSQLOPTLVLSpecifies optimization methods (SQL optimization options) for determining the most efficient access path by taking the database status into consideration.
85PDADDITIONALOPTLVLSpecifies optimization methods (SQL extension optimizing methods) for determining the most efficient access path by taking the database status into consideration.
86PDHASHTBLSIZESpecifies the hash table size when hash join, subquery hash execution is applied in SQL optimization.
88PDAGGRSpecifies the maximum number of groups allowed in each server so that the memory size used in GROUP BY processing can be determined.
89PDCMMTBFDDLWhen a definition SQL is to be executed in a transaction that is executing a data manipulation SQL, specifies whether the transaction is to be committed automatically before the definition SQL is executed.
90PDPRPCRCLSSpecifies whether an open cursor is to be closed automatically if a PREPARE statement reuses the SQL identifier that is using that open cursor.
92PDDDLDEAPRPSpecifies whether definition information of a table being used by a closed holdable cursor can be changed by another UAP between transactions.
94PDDELRSVWDFILESpecifies the name of the SQL reserved word deletion file when the SQL reserved word deletion facility is used.
95PDHJHASHINGMODESpecifies the hashing method when application of hash join, subquery hash execution is selected as the SQL extension optimizing option.
96PDBLKFSpecifies the number of rows to be sent in one transfer when the HiRDB server transfers retrieval results to the HiRDB client.Block transfer facility
97PDBINARYBLKFSpecifies whether the block transfer facility is to be applied when a table with a BINARY-type selection expression with a defined length exceeding 32,00 bytes is searched.
98PDBLKBUFFSIZESpecifies the size of the server-client communication buffer used by the block transfer facility.
100PDDBACCSWhen the inner replica facility is being used and an RDAREA that is not the current RDAREA is to be accessed, specifies that RDAREA's generation number.Inner replica facility
101PDDBORGUAPSpecifies whether to execute a UAP on the original RDAREA that is in online reorganization hold status.Updatable online reorganization
102PDSPACELVLSpecifies the space conversion level for data storage, comparison, and search processing.Data space conversion
106PDCNSTRNTNAMESpecifies the position of the constraint name definition when a referential or check constraint is defined.Referential and check constraints
107PDBESCONHOLDSpecifies whether the BES connection holding facility is to be used.BES connection holding facility
108PDBESCONHTISpecifies the BES connection holding period when the BES connection holding facility is used.
109PDRDABLKFSpecifies the number of rows to be transferred in one transfer operation when retrieval results are transferred from a distributed server to a distributed client.Distributed database
117PDPLGIXMKSpecifies whether delayed batch creation of plug-in indexes is to be used.Plug-ins
118PDPLUGINNSUBFor details, see the manual for the target plug-in.
119PDPLGPFSZSpecifies the initial size of the index information file for delayed batch creation of plug-ins.
120PDPLGPFSZEXPSpecifies the extension size of the index information file for delayed batch creation of plug-ins.
121PDJDBFILEDIRSpecifies the log file output destination for Exception trace logs in the Type4 JDBC driver.JDBC driver
122PDJDBFILEOUTNUMSpecifies the number of Exception trace logs that the Type4 JDBC driver outputs to the log file.
123PDJDBONMEMNUMSpecifies the number of Exception trace logs acquired in memory by the Type4 JDBC driver.
124PDJDBTRACELEVELSpecifies the trace acquisition level for Exception trace logs in the Type4 JDBC driver.
#
The name of the SQL trace file is pdjsqlxxxxxxxx_ppppp_1.trc or pdjsqlxxxxxxxx_ppppp_2.trc.
xxxxxxxx: Name of connected server (up to 8 characters)
ppppp: Receive port number (5 characters) at the client side
This format is used even when the SQL trace file is acquired by the UAP statistical report facility (PDREPPATH specification) or by the SQL trace dynamic acquisition facility (PDTRCPATH specification). However, if the SQL trace file is acquired before connection to the FES or SDS, the file name becomes pdjsql1.trc or pdjsql2.trc.