______________________________________________________________________________
--- Host Variable Definition --- Command ===> Scroll ===> HALF PSQ195 - Specify host variable data type attributes and press ENTER
Host Variable Profile
UPDATE RLXNUM SET INTEGER = :DV1:IV1 + 10 , SMALLINT = :DV2:IV2 - 56 , DEC150
= :DV3:IV3 , DEC55 = :DV4:IV4 , CHAR5 = :DV5:IV5 , VARCHAR10 = :DV6:IV6 WHERE INTEGER BETWEEN :LOW_LONG_NAME AND :HIGH_LONG_NAME
______________________________________________________________________________
Figure 4.5
Figure 4.5 illustrates the form style panel on which a single host variable definition is displayed for review and/or modification. The description and purpose of the form style panel fields are the same as for the Host Variable Definition summary panel -- with the exception of the fields described in this section. Proceeding from top to bottom, the fields unique to the form style Host Variable Definition panel are as follows:
The Data Type Code field accepts a single alphabetic character selected from the list of datatype codes A through M enumerated on the panel. RLX trans-lates this code into the appropriate SQL datatype. These codes and their corres-ponding SQL datatypes are listed in ascending order by their SQLTYPE values.
The Datatype Origin field identifies the means by which the host variable's datatype was determined.
When the host variable datatype is derived via SQL DESCRIBE, the Datatype Origin field contains the name of the describing SQL column as in:
COLUMN_NAME Host variable datatype = datatype of SQL column
Host variables whose datatype is assigned by RLX appear with the RLX origin literal bounded on the left and right by an asterisk as in the following examples:
Datatype origin Significance
--- ---
* GLOBAL VDEFINE * Explicitly VDEFINEd host variables
* LOCAL VDEFINE * Explicitly VDEFINEd host variables
* FORCED BY USAGE * Host variables whose datatype is forced by usage. For example, RLX sets the
datatypes of host variables appearing in
a LIKE predicate to VARCHAR(255)
* ---> FLOAT * Datatype escalated to double precision
floating point
* UNKNOWN * Host variable whose datatype is
ambiguous or unknown
The RLX SQL statement containing the host variable appears for reference at the bottom of the panel as illustrated below.
_____________________________________________________________________________
UPDATE RLXNUM SET INTEGER = :DV1:IV1 + 10 , SMALLINT = :DV2:IV2 - 56 , DEC150
= :DV3:IV3 , DEC55 = :DV4:IV4 , CHAR5 = :DV5:IV5 , VARCHAR10 = :DV6:IV6 WHERE INTEGER BETWEEN :LOW_LONG_NAME AND :HIGH_LONG_NAME
_____________________________________________________________________________
4.12 RLX/ISPF Control variables
The third RLX User Profile Panel is illustrated in Figure 4.6. The parameters are discussed in the order in which they appear. Possible settings of these options are listed in the display, to the right of the input field following their respective prompts. You can review and revise these values as appropriate.
_______________________________________________________________________________
The group of profile attributes labeled Default RLX/ISPF CONTROL Settings govern various aspects of RLX/ISPF operation. These RLX/ISPF profile attributes can also be set dynamically (via the RLX CONTROL service as described in Chapter 6) during execution of your RLX applications.
The Maximum Rows option places a limit on the number of SQL query result rows that the RLX DECLARE ISPFTABLE and DECLARE REXXSTEM services will attempt to load. Maximum Rows specifies an integer value from 0 through 2,147,483,647. RLX does not attempt to limit the number of rows it loads when Maximum Rows specifies a value less than one. See the CONTROL LIMIT service described in Chapter 6 for additional information.
The Replace _ Char option designates a replacement character for the underscore '_'. A replacement character for the underscore may be needed for the following reason. Although the underscore is a valid character in forming the names of DB2 entities such as column names, the underscore is illegal as a character in the name of an ISPF dialog variable. Thus a name like COL_NAME can create severe errors in ISPF dialog services or the RLX DECLARE ISPFTABLE service.
Although any alphabetic or national character is allowable, we recommend you choose an underscore replacement character from among the national characters
#, @, and $. The RLX CONTROL URC service enables you to dynamically change the underscore replacement character during execution of your RLX applications. See Chapter 6 for additional information.
Defaults for SQL query results previously loaded into ISPF temporary or permanent tables provides three modes with which to govern RLX/ISPF operation.
• The extend option causes RLX to add rows to SQL answer sets previously loaded into ISPF tables. The delete option causes RLX to remove the rows of the previous query result and load the current answer set into a cleared table. In addition, the delete option makes it unnecessary for your dialog to issue explicit ISPEXEC TBEND statements.
• The test option applies to both the ISPF table loaded with SQL query results as well as the dynamic table display panel processed by the RLX TBDISPL service. When the test option is in effect, the DECLARE ISPFTABLE request is reprocessed each time the statement is executed.
Further, any referencing RLX TBDISPL request will be reprocessed whenever the corresponding DECLARE ISPFTABLE is re-executed. As a consequence, the column composition of the ISPF table and TBDISPL panel can change from one execution to the next. This is appropriate when the column selection list of a DECLARE ISPFTABLE request is itself subject to change.
4.13 Maximum Attentions
The attribute labeled Max Attentions appears under the heading Additional RLX Session variables. This value governs how many attention interrupts the RLX attention exit will accept before forcing session cancellation. The default value is 3.
Additional RLX Session variables Max Attentions ===> 3 (before forcing session cancellation) Maximum tokens ===> 15000 (comprising an RLX SQL statement)
4.14 Maximum Tokens
The attribute labeled Maximum Tokens also appears under the heading Additional RLX Session variables. This value specifies a limit for the number of tokens that can comprise RLX SQL statements. The default value is 1500 but can be set higher for applications which issue extremely long SQL statements.
Additional RLX Session variables Max Attentions ===> 3 (before forcing session cancellation) Maximum tokens ===> 15000 (comprising an RLX SQL statement)
4.15 Specify Color Attributes of the RLX panels
The bottom set of options allows you to Specify Color Attributes for the panels supplied with and displayed by RLX.
Specify Color Attributes W - White Input - Normal ===> G R - Red Input - High ===> R B - Blue Output - Normal ===> B G - Green Output - High ===> B P - Pink Text - Normal ===> B Y - Yellow Text - High ===> W T - Turquoise
The Specify Color Attributes options permit you to designate colors associated with various field types for the panels displayed from the RLX panel library.