0% found this document useful (0 votes)
712 views9 pages

Spufi Screen Shots and Faqs

The screenshots show the process of running SQL queries using SPUFI (Structured Query Language Processing Using File Input). The user first selects SPUFI from the DB2I primary menu. They then specify the input and output files, processing options like editing input or executing queries, and defaults. The SQL statements are run and output is browsed, with messages indicating success or errors encountered.

Uploaded by

bsuppal
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
712 views9 pages

Spufi Screen Shots and Faqs

The screenshots show the process of running SQL queries using SPUFI (Structured Query Language Processing Using File Input). The user first selects SPUFI from the DB2I primary menu. They then specify the input and output files, processing options like editing input or executing queries, and defaults. The SQL statements are run and output is browsed, with messages indicating success or errors encountered.

Uploaded by

bsuppal
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 9

SPUFI

SPUFI Screen Shots and FAQs


The below screenshots show how to run a query in SPUFI.

Screen: 1

------------------------- Quest Infotech.


------------------------------------
DB2 Tools Primary Menu
Option ===> D
Userid - MUTHU
Subsystem => SBTG
Date - 07/12/01

Time - 21:50

D - DB2I - 7.1 - Insight for


DB2(TSO INSIGHT on command line)
Q - QMF - 7.2
M - DBMAUI - 1.2.5 W -
Weekly DB2 Performance Data
P - CA Products - R11.5
A - CA Advantage Report Facility C -
Sapiens Object Pool - 30.26
L - Plutonium

Enter END command to terminate DB2 Tools Primary


Menu

Screen: 2

DB2I PRIMARY
OPTION MENU SSID: SBTG
COMMAND ===> 1

Select one of the following DB2 functions and press


ENTER.

1 SPUFI (Process SQL statements)


2 DCLGEN (Generate SQL and source
language declarations)
3 PROGRAM PREPARATION (Prepare a DB2
application program to run)
4 PRECOMPILE (Invoke DB2 precompiler)
5 BIND/REBIND/FREE (BIND, REBIND, or FREE
plans or packages)
6 RUN (RUN an SQL program)
7 DB2 COMMANDS (Issue DB2 commands)
8 UTILITIES (Invoke DB2 utilities)
D DB2I DEFAULTS (Set global parameters)
X EXIT (Leave DB2I)

PRESS: END to exit HELP


for more information

Screen: 3

SPUFI
SSID: SBTG
===>

Enter the input data set name: (Can be


sequential or partitioned)
1 DATA SET NAME ... ===>
'MUTHU.TAG.SOURCE(SQLIN)'
2 VOLUME SERIAL ... ===> (Enter if not
cataloged)
3 DATA SET PASSWORD ===> (Enter if
password protected)

Enter the output data set name: (Must be a


sequential data set)
4 DATA SET NAME ... ===> 'MUTHU.SQLOUT'

Specify processing options:


5 CHANGE DEFAULTS ===> YES (Y/N -
Display SPUFI defaults panel?)
6 EDIT INPUT ...... ===> YES (Y/N - Enter
SQL statements?)
7 EXECUTE ......... ===> YES (Y/N -
Execute SQL statements?)
8 AUTOCOMMIT ...... ===> YES (Y/N - Commit
after successful run?)
9 BROWSE OUTPUT ... ===> YES (Y/N - Browse
output data set?)

For remote SQL processing:


10 CONNECT LOCATION ===>

PRESS: ENTER to process END to exit


HELP for more information
Screen: 4

CURRENT SPUFI DEFAULTS


SSID: SBTG
===>

Enter the following to control your SPUFI session:


1 SQL TERMINATOR .. ===> ; (SQL
Statement Terminator)
2 ISOLATION LEVEL ===> RR
(RR=Repeatable Read, CS=Cursor Stability)
3 MAX SELECT LINES ===> 200000 (Maximum
number of lines to be
returned
from a SELECT)
4 ALLOW SQL WARNINGS===> NO (Continue
fetching after sqlwarning)
5 CHANGE PLAN NAMES ===> NO (Change the
plan names used by SPUFI)

Output data set characteristics:


6 RECORD LENGTH ... ===> 4092
(LRECL=Logical record length)
7 BLOCK SIZE ...... ===> 4096 (Size of one
block)
8 RECORD FORMAT ... ===> VB (RECFM=F, FB,
FBA, V, VB, or VBA)
9 DEVICE TYPE ..... ===> SYSDA (Must be DASD
unit name)

Output format characteristics:


10 MAX NUMERIC FIELD ===> 33 (Maximum
width for numeric fields)
11 MAX CHAR FIELD .. ===> 80 (Maximum
width for character fields)
12 COLUMN HEADING .. ===> NAMES (NAMES,
LABELS, ANY or BOTH)

PRESS: ENTER to process END to exit


HELP for more information

Screen: 5

File Edit Edit_Settings Menu Utilities


Compilers Test Help
¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢
¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢
EDIT MUTHU.TAG.SOURCE(TIME) - 01.95
Columns 00001 00072
Command ===> END
Scroll ===> CSR
****** ***************************** Top of Data
******************************
==MSG> -Warning- The UNDO command is not available
until you change
==MSG> your edit profile using the command
RECOVERY ON.
000010 --
000020 -- DROP TABLE MUTHU.PLAN_TABLE;
000030 -- CREATE TABLE MUTHU.PLAN_TABLE LIKE
TEST.PLAN_TABLE;
000040 --
000050 -- EXPLAIN ALL SET QUERYNO=100 FOR
000060 -- (SELECT HOURS_WORKED
000070 -- FROM TEST.TIME_ENTRY
000071 -- WHERE REQ_NUM = 215);
000080 --
000090 SELECT REQ_NUM,SUM(HOURS_WORKED)
000100 FROM TEST.TIME_ENTRY
000110 WHERE REQ_NUM BETWEEN 215 AND 220
000111 GROUP BY REQ_NUM;
000112 --
000120 --SELECT
TSO_ID,TIME_SHEET_DT,SUM(HOURS_WORKED)
000200 -- FROM TEST.TIME_ENTRY
000300 --WHERE REQ_NUM = 215
000301 --WHERE TIME_SHEET_DT >= '2007-08-10'
000310 -- AND TIME_SHEET_DT <= '2007-08-16'
000320 -- AND REQ_NUM = 215
000400 --GROUP BY TSO_ID,TIME_SHEET_DT;
000500 --
****** **************************** Bottom of Data
****************************

Screen: 6

SPUFI
SSID: SBTG
===>

Enter the input data set name: (Can be


sequential or partitioned)
1 DATA SET NAME ... ===> 'MUTHU.TAG.SOURCE(TIME)'
2 VOLUME SERIAL ... ===> (Enter if not
cataloged)
3 DATA SET PASSWORD ===> (Enter if
password protected)

Enter the output data set name: (Must be a


sequential data set)
4 DATA SET NAME ... ===> 'MUTHU.T1'

Specify processing options:


5 CHANGE DEFAULTS ===> * (Y/N - Display
SPUFI defaults panel?)
6 EDIT INPUT ...... ===> * (Y/N - Enter
SQL statements?)
7 EXECUTE ......... ===> YES (Y/N - Execute
SQL statements?)
8 AUTOCOMMIT ...... ===> YES (Y/N - Commit
after successful run?)
9 BROWSE OUTPUT ... ===> YES (Y/N - Browse
output data set?)

For remote SQL processing:


10 CONNECT LOCATION ===>

PRESS: ENTER to process END to exit


HELP for more information

Å¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢
¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢Õ
… DSNE808A EDIT SESSION HAS COMPLETED. PRESS
ENTER TO CONTINUE …
Ä¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢
¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢Ô

Screen: 7

Menu Utilities Compilers Help


¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢
¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢
BROWSE MUTHU.T1
Line 00000000 Col 001 080
Command ===>
Scroll ===> CSR
********************************* Top of Data
**********************************
---------+---------+---------+---------+---------
+---------+---------+---------+
--
00001000
-- DROP TABLE MUTHU.PLAN_TABLE;
00002093
-- CREATE TABLE MUTHU.PLAN_TABLE LIKE
AI00066.PLAN_TABLE; 00003095
--
00004080
-- EXPLAIN ALL SET QUERYNO=100 FOR
00005095
-- (SELECT HOURS_WORKED
00006095
-- FROM TEST.TIME_ENTRY
00007095
-- WHERE REQ_NUM = 215);
00007195
--
00008061
SELECT REQ_NUM,SUM(HOURS_WORKED)
00009077
FROM TEST.TIME_ENTRY
00010077
WHERE REQ_NUM BETWEEN 215 AND 220
00011096
GROUP BY REQ_NUM;
00011177
---------+---------+---------+---------+---------
+---------+---------+---------+
REQ_NUM
---------+---------+---------+---------+---------
+---------+---------+---------+
215 169.00
216 12.00
217 115.50
218 26.00
219 39.00
DSNE610I NUMBER OF ROWS DISPLAYED IS 5
DSNE616I STATEMENT EXECUTION WAS SUCCESSFUL, SQLCODE
IS 100
--
00011274
--SELECT TSO_ID,TIME_SHEET_DT,SUM(HOURS_WORKED)
00012056
-- FROM TEST.TIME_ENTRY
00020056
--WHERE REQ_NUM = 215
00030056
--WHERE TIME_SHEET_DT >= '2007-08-10'
00030152
-- AND TIME_SHEET_DT <= '2007-08-16'
00031052
-- AND REQ_NUM = 215
00032052
--GROUP BY TSO_ID,TIME_SHEET_DT;
00040056
--
00050000
---------+---------+---------+---------+---------
+---------+---------+---------+
DSNE617I COMMIT PERFORMED, SQLCODE IS 0
DSNE616I STATEMENT EXECUTION WAS SUCCESSFUL, SQLCODE
IS 0
---------+---------+---------+---------+---------
+---------+---------+---------+
DSNE601I SQL STATEMENTS ASSUMED TO BE BETWEEN
COLUMNS 1 AND 72
DSNE620I NUMBER OF SQL STATEMENTS PROCESSED IS 1
DSNE621I NUMBER OF INPUT RECORDS READ IS 22
DSNE622I NUMBER OF OUTPUT RECORDS WRITTEN IS 42

Screen: 8

BROWSE MUTHU.T1
Line 00000000 Col 001 080
Command ===>
Scroll ===> CSR
********************************* Top of Data
**********************************
---------+---------+---------+---------+---------
+---------+---------+---------+
--
00001000
-- DROP TABLE MUTHU.PLAN_TABLE;
00002093
-- CREATE TABLE MUTHU.PLAN_TABLE LIKE
AI00066.PLAN_TABLE; 00003095
--
00004080
-- EXPLAIN ALL SET QUERYNO=100 FOR
00005095
-- (SELECT HOURS_WORKED
00006095
-- FROM TEST.TIME_ENTRY
00007095
-- WHERE REQ_NUM = 215);
00007195
--
00008061
SELECT REQ_NUM,SUM(HOURS_WORKED)
00009077
FROM TEST.TIME_ENTRY
00010077
WHERE REQ_NUM BETWEEN 215 AND 220
00011096
GROUP BY REQ_NUM;
00011177
---------+---------+---------+---------+---------
+---------+---------+---------+
REQ_NUM
---------+---------+---------+---------+---------
+---------+---------+---------+
215 169.00
DSNE626I MAXIMUM OUTPUT LINES FOR SELECT STATEMENT
REACHED (1), PROCESSING FOR C
DSNE610I NUMBER OF ROWS DISPLAYED IS 1
DSNE616I STATEMENT EXECUTION WAS SUCCESSFUL, SQLCODE
IS 0
---------+---------+---------+---------+---------
+---------+---------+---------+

When query has problems, the result may look like below:

Screen: 9

BROWSE MUTHU.T1
Line 00000000 Col 001 080
Command ===>
Scroll ===> CSR
********************************* Top of Data
**********************************
---------+---------+---------+---------+---------
+---------+---------+---------+
--
00001000
-- DROP TABLE MUTHU.PLAN_TABLE;
00002093
-- CREATE TABLE MUTHU.PLAN_TABLE LIKE
AI00066.PLAN_TABLE; 00003095
--
00004080
-- EXPLAIN ALL SET QUERYNO=100 FOR
00005095
-- (SELECT HOURS_WORKED
00006095
-- FROM TEST.TIME_ENTRY
00007095
-- WHERE REQ_NUM = 215);
00007195
--
00008061
SELECT REQ_NUM,SUM(HOURS_WORKED) AS TOTAL-HOURS
00009099
FROM TEST.TIME_ENTRY
00010077
WHERE REQ_NUM BETWEEN 215AND 220
00011096
GROUP BY REQ_NUM;
00011177
---------+---------+---------+---------+---------
+---------+---------+---------+
DSNT408I SQLCODE = -104, ERROR: ILLEGAL SYMBOL "-".
SOME SYMBOLS THAT MIGHT BE
LEGAL ARE: , FROM INTO
DSNT418I SQLSTATE = 42601 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNHPARS SQL PROCEDURE
DETECTING ERROR
DSNT416I SQLERRD = 502 0 0 -1 43 0 SQL
DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'000001F6' X'00000000'
X'00000000' X'FFFFFFFF'
X'0000002B' X'00000000' SQL DIAGNOSTIC
INFORMATION
---------+---------+---------+---------+---------
+---------+---------+---------+
DSNE618I ROLLBACK PERFORMED, SQLCODE IS 0
DSNE616I STATEMENT EXECUTION WAS SUCCESSFUL, SQLCODE
IS 0

 Look at screen 7. Even though the records are fetched by SPUFI for the query,
the SQLCODE is shown as 100. Why?
Look at screen 4. We mentioned MAX SELECT LINES ===> 200000.
As only 5 rows returned SPUFI returned SQLCODE 100.
If we change this MAX SELECT LINES to 1, the last screen may look like
screen 8

 How do you comment the SQL in the SPUFI input dataset?


By prefixing – -

 When you run a Update Query in SPUFI, the changes will be made permanent
automatically?
It depends on the AUTOCOMMIT option mentioned in the screen 6.

 I ran a query to fetch remarks which is of 250 VARCHAR item of an employee.

But SPUFI shows only 80 characters. There is truncation. What could be the
possible reason?
That could be the limit you set up for CHAR item in Screen 6.

You might also like