Thanks for all the replies with references and examples.
A plus point for QSH/DB2 utility is the ability to view a SQL statement
directly in CL source as opposed to a "hidden" SQL statement accessed
via RUNSQLSTM. Also it's possible to build the CMD string on the fly.
Having said that, it's clear that usage is restricted owing to its
limitations e.g. no cursor but, in certain cases, QSH/DB2 could be a
useful approach.
Cheers,
Keith
The Royal Bank of Scotland plc, Registered in Scotland No. 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB
Authorised and regulated by the Financial Services Authority.
This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent.
Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by The Royal Bank of Scotland plc in this regard and the recipient should carry out such virus and other checks as it considers appropriate.
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Calling SQL from QSH was: CPYTOSTMF, (continued)
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.