TSYS has QMF applications running in 6 UAT and Production Db2 environments. There are approximately 2,600+ client users running QMF queries and procs for their applications in those Db2 environments. Many of the users are creating temporary tables and what-if-tables using the QMF SAVE DATA command.
Today in the 6 UAT and Production Db2 environments the TSYS Db2 DBAs have created multiple client Db2 databases with one SEGMENTED table space defined to each database. And as new clients come into TSYS, the TSYS Db2 DBAs create the same setup, the new client’s Db2 databases with one SEGMENTED table space.
The client users QMF profiles are setup with the name of the client’s database and SEGMENTED table space. This allows the client users to execute the QMF SAVE DATA command with the table name of their choice on the QMF report from the client user’s QMF query. The client user has no knowledge or understanding of a Db2 database and Db2 table space.
The TSYS QMF application team supporting the client and the TSYS Db2 DBAs are not notified when a client’s user may create a query and use the QMF SAVE DATA command. The client does not want to notify TSYS nor does TSYS want to be notified by the client when their user uses the SAVE DATA command. The client requires the current ability to do whatever QMF work they want to do or need to do without notifying or waiting for some TSYS action.
When the TSYS Db2 DBA creates the client’s Db2 database with the one SEGMENTED table space certain table space parameter have predetermined TSYS values. Of these predetermined TSYS values some are to adhere to contractual agreements with financial obligations between TSYS and the client. These two table space parameter, PRIQTY and SECQTY, are the most critical ones.
In the contractual agreement between TSYS and the client, the client pays for DASD usage for tables created by the client’s user when executing the QMF SAVE DATA command. The agreement states that a certain amount of DASD is available to the client. The adherence of that certain amount of DASD is accomplished by the value of the table space PRIQTY parameter.
If the client needs more DASD than allowed by the contractual agreement, then the client must request more available DASD and agree to the financial responsibility of that additional DASD. When TSYS and the client are in agreement about the additional DASD, then the TSYS Db2 DBAs will alter the table space SECQTY value to accomplish that agreement. Also, since this is a SEGMENTED table space, the maximum DASD available is limited to the 2G X 32 datasets limits of a SEGMENTED table space.
Two other table space parameters are the FREEPAGE and PCTFREE. TSYS defines these parameter’s values as 0 (zero). This is to also accomplish the DASD contractual agreement, giving the client all the DASD as allocated by the PRIQTY parameter value. Also, due to the way the client user’s use the tables they create, a FREEPAGE and PCTFREE of 0 (zero) is the most practical value.
Another table space parameter is the BUFFERPOOL. Today, TSYS uses several BUFFERPOOLs for the client’s QMF applications. This table space parameter does not have a contractual obligation, but it does have a role in the performance of the client user’s QMF queries.
The TSYS Db2 DBAs understand that QMF offers 3 choices for creating the database and / or table space when using the QMF SAVE DATA command. As stated earlier, TSYS uses the choice of providing in the client user’s QMF profile the database name and SEGMENTED table space name.
If TSYS has control over certain implicit table space parameter values, then the TSYS Db2 DBAs can convert these 6 UAT and Production Db2 environments from SEGMENTED table spaces to UTS PBG table spaces. TSYS can use the QMF option to provide a database name in the user’s QMF profile and allow Db2 to create an implicit table space using the TSYS override values for thetable space parameter default values.
Also, TSYS is a sponsor of the IBM development project, E4056 Multi-table table space conversion to UTS PBG. The 6 UAT and Production Db2 environments where client users use QMF and the QMF SAVE DATA command are the remaining Db2 environment at TSYS which have SEGMENTED table space. So for TSYS to continue to contribute to this IBM development project, there must be a solution to the implicit table space parameter values issue for TSYS.
TSYS would like to have control of the implicit table space name. TSYS Db2 DBAs have automated processes which use the table space name as a filter and / or control. However, the TSYS Db2 DBAs believes the automated process can be altered to work around the table space name if it is not possible to give TSYS the control of the implicit table space name.
Here are the implicit table space parameters that the TSYS Db2 DBAs know of today which TSYS needs to control at the individual table space level. To control the parameter values at a higher level like database or ZPARM will not work for TSYS.
These are DASD usage:
- PRIQTY and SECQTY
- MAXPARTITIONS
- DSSIZE
- COMPRESS
- FREEPAGE
- PCTFREE
These are for performance
- BUFFERPOOL
- LOGGED / NOT LOGGED
- SEGSIZE
- LOCKSIZE
Also, TSYS uses the IBM Encryption Services application ported to the mainframe. That application creates XML tables and TSYS also sees the need for control of implicit table space parameter values created for the IBM Encryption Services XML tables.
