Fw: [U2] [UV] QSELECT in transaction

[Jonathan D Smith]

Hi All,

Just needed to clear up where we are with QSELECT question for everyone on 
the list. We've done some researching on the issue, as it is also a 
currently active support case asked by a customer in South Africa. 
Previous comments about the interaction with the SAVEDLISTS file would be 
incorrect, after all SAVE.LIST is also allowed in a transaction. We are 
unsure at this time if the omission of QSELECT was by design or an 
oversight. We have been able to get QSELECT to work within a transaction 
by a simple change, however we are still looking to see if this change has 
any unwanted interactions or implications in other areas of the 
transaction or UniVerse. The good news is that, if the tests go well then 
you will be able to make the same change for yourselves without having to 
upgrade UniVerse.

Regards,
Jonathan Smith
IBM Certified Solutions Expert
Advanced Support Engineer - U2 Advanced Technical Support
IBM Data Management Solutions
Support Phone 0800 773 771
Support mailto:[EMAIL PROTECTED]
http://www.ibm.com/software/data/u2/support - Open, Query, Update, Search 
- Online!
DISCLAIMER:This email and any files transmitted with it are confidential 
and intended solely for the use of the individual or entity to which they 
are addressed. If you have received this email in error, please delete it 
and notify the sender immediately. 
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

Fw: [U2] [UV] QSELECT in transaction

[Herve Balestrieri]

 QSELECT builds a SELECTed list of values, which operation is also

 possible with the SELECT statement, as noted.

 But the QSELECT statement have some options that implies a Read

 operation from the SAVEDLISTS file. It is assumed that, the

 SAVEDLISTS file being generally a Type 1 or 19 file, a Transaction

 cannot be ensured on this type of file. Subsequently, QSELECT is not

 permitted at all.

 If the equivalent of a QSELECT satement is to be performed in an

 Transactionnal application, the various steps to be executed would have to

 be explicitly programmed within the Transaction. In that sort of

 workaround programming, the programmer and applicative layer instead of

 the database engine are made responsible for application data consistency.


 An enhancement request could be raised toward IBM to allow in transactions
 those of the QSELECT syntaxes which are not involving the SAVEDLIST
file.
 Though, I doubt the UniVerse Basic Run Machine has the ability to
differentiate
 these syntaxes on the fly, so the restriction was made to easily secure

 the transaction in all cases.


Hervi BALESTRIERI

Support Technique Avanci - IBM France
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/