* Standard COBOL (file "XTS717.SCO") calling SQL * procedures in file "XTS717.MCO".
*Copyright 1995 National Computing Centre Limited *and Computer Logic R&D S.A *on behalf of the CTS5 SQL2 Project. *All rights reserved. *The CTS5 SQL2 Project is sponsored by the European Community. * *The National Computing Centre Limited and Computer Logic R&D *have given permission to NIST to distribute this program *over the World Wide Web in order to promote SQL standards. *DISCLAIMER: *This program was reviewed by employees of NIST for *conformance to the SQL standards. *NIST assumes no responsibility for any party's use of *this program.
**************************************************************** * * COMMENT SECTION * * SQL VALIDATION TEST SUITE V6.0 * * XTS717.SCO * WRITTEN BY: Manolis Megaloikonomou * TRANSLATED AUTOMATICALLY FROM EMBEDDED COBOL BY CHRIS SCHANZLE * REVIEWED BY: Nickos Backalidis * * SET SESSION AUTHORIZATION to current auth-id inside * transaction. * * REFERENCES * 16.4 -- <set session authorization identifier statement> * 16.4 GR.1 * 16.4 GR.2 * 16.4 LR.2a -- Raised. Entry SQL restriction that * prohibits the use of any <set session * authorization identifier statement>. * 6.2 -- <value specification> and <target specification> * 6.2 SR.3 * 6.2 GR.9 * 6.2 LR.2c -- Raised. Entry SQL restriction which * prohibits the specification of CURRENT_USER, * SYSTEM_USER or SESSION_USER in a * <general value specification>. * F#32 -- User authorization. * * DATE LAST ALTERED 12/12/95 CTS5 Hand-over Test * * Cleanups and fixes by V. Kogakis 01/12/95: * Respect length of strings * * QA Status: QA Check * * Revised by DWF 1/23/96 * Removed status code checks after cursor definition. * Fixed pass criteria (wrong SQLCODE) * Added a subtest * Fixed data clobbering problem ****************************************************************
*Use a host variable xuser explicitly initialised to *the value of the current authorization identifier. MOVE" CTS1 "TO xuser DISPLAY"xuser = '", xuser, "'"
MOVE 99 TO coun DISPLAY"SELECT COUNT(*) INTO :coun FROM CTS1.STAFF;" * EXEC SQL SELECT COUNT(*) INTO :coun FROM CTS1.STAFF * ; CALL"SUB3"USING SQLCODE SQLSTATE coun MOVE SQLCODE TO SQL-COD PERFORM CHCKOK DISPLAY"Coun should be 5; its value is ", coun if ( coun NOT = 5 ) then MOVE 0 TO flag END-IF DISPLAY" "
*This should fail because we're in the middle of a transaction *(16.4 GR.1) *Yes, a SELECT statement begins a transaction 4.22.6 DISPLAY"SET SESSION AUTHORIZATION :xuser;" * EXEC SQL SET SESSION AUTHORIZATION :xuser; CALL"SUB4"USING SQLCODE SQLSTATE xuser MOVE SQLCODE TO SQL-COD DISPLAY"SQLCODE should be < 0; its value is ", SQL-COD DISPLAY"SQLSTATE should be 25000; its value is ", SQLSTATE PERFORM NOSUBCLASS THRU EXIT-NOSUBCLASS if (SQLCODE NOT < 0 OR NORMSQ NOT = "25000") then MOVE 0 TO flag END-IF if (NORMSQ = "25000"AND NORMSQ NOT = SQLSTATE) then DISPLAY"Valid implementation-defined SQLSTATE accepted." END-IF DISPLAY" "
*In order to activate an SQL transaction use a cursor *and retrieve rows from the table STAFF DISPLAY"DECLARE ALPHA CURSOR" DISPLAY"FOR SELECT EMPNAME FROM CTS1.STAFF;" * EXEC SQL DECLARE ALPHA CURSOR * FOR SELECT EMPNAME FROM CTS1.STAFF END-EXEC
DISPLAY"OPEN ALPHA;" * EXEC SQL OPEN ALPHA; CALL"SUB6"USING SQLCODE SQLSTATE MOVE SQLCODE TO SQL-COD PERFORM CHCKOK DISPLAY" "
DISPLAY"FETCH ALPHA INTO :xuser;" * EXEC SQL FETCH ALPHA INTO :xuser; CALL"SUB7"USING SQLCODE SQLSTATE xuser MOVE SQLCODE TO SQL-COD PERFORM CHCKOK DISPLAY" "
*Change the session authorization identifier to the *value of CURRENT_USER DISPLAY"SET SESSION AUTHORIZATION CURRENT_USER;" * EXEC SQL SET SESSION AUTHORIZATION CURRENT_USER; CALL"SUB8"USING SQLCODE SQLSTATE MOVE SQLCODE TO SQL-COD *Check that an exception condition of invalid *transaction state is raised indicated in the value *of SQLSTATE which should be '25000'. DISPLAY"SQLCODE should be < 0; its value is ", SQL-COD DISPLAY"SQLSTATE should be 25000; its value is ", SQLSTATE PERFORM NOSUBCLASS THRU EXIT-NOSUBCLASS if (SQLCODE NOT < 0 OR NORMSQ NOT = "25000") then MOVE 0 TO flag END-IF if (NORMSQ = "25000"AND NORMSQ NOT = SQLSTATE) then DISPLAY"Valid implementation-defined SQLSTATE accepted." END-IF DISPLAY" "
DISPLAY"SET SESSION AUTHORIZATION :xuser;" * EXEC SQL SET SESSION AUTHORIZATION :xuser; CALL"SUB11"USING SQLCODE SQLSTATE xuser MOVE SQLCODE TO SQL-COD *Check that an exception condition of invalid *transaction state is raised indicated in the value *of SQLSTATE which should be '25000'. DISPLAY"SQLCODE should be < 0; its value is ", SQL-COD DISPLAY"SQLSTATE should be 25000; its value is ", SQLSTATE PERFORM NOSUBCLASS THRU EXIT-NOSUBCLASS if (SQLCODE NOT < 0 OR NORMSQ NOT = "25000") then MOVE 0 TO flag END-IF if (NORMSQ = "25000"AND NORMSQ NOT = SQLSTATE) then DISPLAY"Valid implementation-defined SQLSTATE accepted." END-IF DISPLAY" "
if ( flag = 1 ) then DISPLAY" xts717.mco *** pass *** " * EXEC SQL INSERT INTO CTS1.TESTREPORT * VALUES('7017','pass','MCO'); CALL"SUB13"USING SQLCODE SQLSTATE MOVE SQLCODE TO SQL-COD else DISPLAY" xts717.mco *** fail *** " * EXEC SQL INSERT INTO CTS1.TESTREPORT * VALUES('7017','fail','MCO'); CALL"SUB14"USING SQLCODE SQLSTATE MOVE SQLCODE TO SQL-COD COMPUTE errcnt = errcnt + 1 END-IF
DISPLAY"========================================"
* EXEC SQL COMMIT WORK; CALL"SUB15"USING SQLCODE SQLSTATE MOVE SQLCODE TO SQL-COD ******************** END TEST7017 ********************
**** TESTER MAY CHOOSE TO INSERT CODE FOR errcnt > 0 STOPRUN.
* **** Procedures for PERFORM statements
*Test SQLCODE and SQLSTATE for normal completion.
CHCKOK. DISPLAY"SQLCODE should be 0; its value is ", SQL-COD DISPLAY"SQLSTATE should be 00000; its value is ", SQLSTATE PERFORM NOSUBCLASS THRU EXIT-NOSUBCLASS if (SQLCODE NOT = 0 OR NORMSQ NOT = "00000") then MOVE 0 TO flag END-IF if (NORMSQ = "00000"AND NORMSQ NOT = SQLSTATE) then DISPLAY"Valid implementation-defined SQLSTATE accepted." END-IF
.
NOSUBCLASS.
*This routine replaces valid implementation-defined *subclasses with 000. This replacement equates valid *implementation-defined subclasses with the 000 value *expected by the test case; otherwise the test will fail. *After calling NOSUBCLASS, NORMSQ will be tested * SQLSTATE will be printed.
MOVE SQLSTATE TO NORMSQ
MOVE 3 TO norm1 *subclass begins in position 3 of char array NORMSQ *valid subclass begins with 5-9, I-Z, end of ALPNUM table PERFORMVARYING norm2 FROM 14 BY 1 UNTIL norm2 > 36 if (NORMSQX(norm1) = ALPNUM(norm2)) then MOVE"0"TO NORMSQX(norm1) END-IF END-PERFORM
*Quit if NORMSQ is unchanged. Subclass is not impl.-def. *Changed NORMSQ means implementation-defined subclass, *so proceed to zero it out, if valid (0-9,A-Z) if (NORMSQ = SQLSTATE) then GOTO EXIT-NOSUBCLASS END-IF
MOVE 4 TO norm1 *examining position 4 of char array NORMSQ *valid characters are 0-9, A-Z PERFORMVARYING norm2 FROM 1 BY 1 UNTIL norm2 > 36 if (NORMSQX(norm1) = ALPNUM(norm2)) then MOVE"0"TO NORMSQX(norm1) END-IF END-PERFORM
MOVE 5 TO norm1 *valid characters are 0-9, A-Z *examining position 5 of char array NORMSQ PERFORMVARYING norm2 FROM 1 BY 1 UNTIL norm2 > 36 if (NORMSQX(norm1) = ALPNUM(norm2)) then MOVE"0"TO NORMSQX(norm1) END-IF END-PERFORM
*implementation-defined subclasses are allowed for warnings *(class = 01). These equate to successful completion *SQLSTATE values of 00000. *Reference SQL-92 4.28 SQL-transactions, paragraph 2
if (NORMSQX(1) = "0"AND NORMSQX(2) = "1") then MOVE"0"TO NORMSQX(2) END-IF
.
EXIT-NOSUBCLASS. EXIT.
¤ Dauer der Verarbeitung: 0.14 Sekunden
(vorverarbeitet)
¤
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung ist noch experimentell.