ISQL runs as a CICS/VSE transaction. A CICS user invokes this transaction just like any other CICS transaction.
After CICS has been activated and the DB2 Server for VSE & VM online support has been started, the CICS user starts ISQL by entering the following four-character CICS transaction identifier from a CICS terminal, and pressing ENTER:
isql
ISQL responds with a display like the one shown in Figure 4.
The screen displays the default application server to which the ORA is connected.
The target application server can be changed by entering the target database information as in the following example:
Enter User ID, Password and Target Database, then press Enter User ID ==========> ________ Password =========> ________ Target Database ==> SQLDB1_TOR_INV
This is also the application server to which ISQL will be connected to subsequently. At this point, because ISQL is not connected to the application server to which the ORA is connected, you can end the ORA and restart to another database. If you log on to ISQL again, the signon screen is redisplayed showing the target application server to which the ORA is now connected.
When not connected to a target application server, the ISQL system displays the line Online Support is not ready. Please exit ISQL. The online resource adapter (ORA) must be enabled before you can start ISQL. For additional information on enabling the ORA, and other requirements before you can start ISQL, refer to Before Starting ISQL and the DB2 Server for VSE System Administration and DB2 Server for VM System Administration manuals.
If you decide to press ENTER instead of specifying your user ID and password when the signon display is displayed, then you must use the explicit database manager CONNECT statement as follows:
CONNECT authorization_name IDENTIFIED BY password TO server_name
An exception to using the CONNECT statement in the above situation is if your installation has defined a default authorization_name for you, in which case, you do not have to specify your authorization_name, password, nor server_name.
If the TO parameter is not specified, then the connection to the previously connected server will be maintained.
An alternate method for invoking ISQL without having to use the ISQL signon display is described in Appendix E, Suppressing the ISQL Sign-On Display for DB2 Server for VSE.
You may run an ISQL routine as part of the ISQL signon procedure. Refer to Using the ISQL Transaction Identifier (DB2 Server for VSE) and Appendix E, Suppressing the ISQL Sign-On Display for DB2 Server for VSE.
The area to the right of Password ==> is a dark field; characters typed in this area remain invisible.
Note: | On some occasions, your display may lock up and you are unable to type data. If this happens, simply press RESET, ensure that the cursor is in the correct position, and retype the information. |
When ISQL recognizes your signon name and password, it responds with the display shown in Figure 5.
Figure 5. Initial ISQL Display
+--------------------------------------------------------------------------------+ |ARI7399I The ISQL default profile values are in effect. | |ARI7079I ISQL initialization complete. | |ARI7080A Please enter an ISQL or SQL command. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |_ | | Enter a command | +--------------------------------------------------------------------------------+
You can exit ISQL from the signon display by typing EXIT in the user ID field, leaving the password field blank, and pressing ENTER. If you enter EXIT in the user ID field, but also enter a password, ISQL will treat it as a user ID and continue processing.
If you enter EXIT to end ISQL, message ARI7601I is displayed as follows:
ARI7601I ISQL ended normally by your request.