Hi. Is anyone using QMF and maintaining their QMF Procs, Queries, and Forms using Endevor?
I am not familiar with IBM QMS. What kinds of source at involved ? Does this application run under MVS or is it a distributed product ? How are these source types updated and do they get processed ? If it is JCL or parameter cards, it should be possible to maintain under Endevor. Please describe the code types and any processing that is required.
Hi Craig. In addition to John's description, IBM DB2 Query Management Facility (QMF) for z/OS is a business analytics software solution developed by IBM. It was originally created to be the reporting interface for the IBM DB2 for z/OS database and is used by many customers to generate reports.
We run it under MVS and use three object types: procedure, query and form.
All three QMF objects mentioned above can be created, modified or deleted from the QMF/TSO home panel. The source of these objects is kept in the QMF control tables. The source can be exported from QMF into the MVS dataset which later can be imported back to QMF also.
Any tips or experience from anyone using the CA Endevor to maintain the source for these QMF objects are greatly appreciated.
For Craig: QMF = Query Management Facility. My experience is it's predominantly for doing ad hoc SQL commands/queries against DB2.
It's going to depend how the site uses QMF, I suppose. Craig is right in that if you're doing a lot of batch or canned invocations, you could store the different components in Endevor as types and execute from there.
But as I indicated, my personal experience was using it basically in line command mode in foreground, in which case I would say there's little point in imposing Endevor....
Thanks John. I'll forward your info to our DBAs.
Forgive me if you know this already, but the portability of QMF objects for storage in Endevor or in the ISPF environment, and/or 'productionalizing' their execution within a formal batch job, is facilitated by use of the QMF 'EXPORT' and 'IMPORT' commands.
For example, if from a QMF screen, assuming your TSO-ID is "USER45" and you entered these commands, the following would result
EXPORT QUERY USER45.QUERY001 TO QUERY001 ==> results in the QMF query being saved to an FB, 79 byte TSO/ISPF dataset called: USER45.QUERY001.QUERY.
EXPORT PROC USER45.PROC001 TO PROC001 ==> results in the QMF procedure being saved to an FB, 79 byte TSO/ISPF dataset called: USER45.PROC001.PROC.
EXPORT FORM USER45.FORM001 TO FORM001 ==> results in the QMF form being saved to an V, 161 byte TSO/ISPF dataset called: USER45.FORM001.FORM.
The resulting ISPF/TSO datasets can be added to Endevor, using Endevor element types that were created in the same format as these ISPF/TSO datasets. i.e. Endevor types: QMFQUERY, QMFPROC, QMFFORM
That would at least enable you to use Endevor as a change-management repository to store your QMF objects. If you want to productionalize these QMF objects to be run in batch, then your production release process should respectively have a way to migrate the Endevor items to members in production PDS libraries defined appropriately for the QMF queries, procs, and forms. Your production job that runs QMF in batch, would first execute a QMF proc that executes the QMF IMPORT command to import the desired QMF objects to the DB2 QMF environment, save those objects, and then run the QMF proc that points to these objects.
Yes, we have all three types. They are not utilized much and I am not knowledgeable about QMF. I know that JCL references some of them with a IMPORT command for FORM and QUERY. PROC are FB 79, QUERY are FB 80, FORM are VB 161.