QMF storage requirements

Before you start using QMF, you need to make sure that each CICS partition that runs QMF has enough storage to accommodate QMF programs and the QMF reports users create.

The partition must be large enough to accommodate:

You can allocate storage for both purposes above 16 MB.

For a QMF system with up to 20 users, allocate at least 24 MB virtual storage for your CICS partition. The minimum acceptable partition size for any QMF system is 18 MB, regardless of the number of users.

To specify your partition size, use the VSE ALLOC statement in the ALLOC.PROC data set of the IPL procedures, as shown in the following example. For systems with more than 20 QMF users, increase the ALLOC 0.5 MB to 1 MB for each additional user.

Also allow 9 MB, within the 24 MB, for your programs. Specify this space with the SIZE value in the IPL allocation data set:

// JOB ALLOC
// EXEC LIBR,PARM='MSHP'
ACC S=IJSYSRS.SYSLIB
CATALOG ALLOC.PROC    DATA=YES    RELPLACE=YES
ALLOC S,F1=24M
SIZE F1=9m

·
·
·

Some users might require more than 1 MB of GETVIS storage if they use complex formatting options for a report, or if a large amount of data is returned from a query.

If a QMF transaction runs out of storage in the CICS partition, it might time out waiting for storage to become available. Therefore, when you adjust the GETVIS values for each user, make sure you increase the ALLOC to accommodate that additional storage.

You might also consider allocating a spill file for certain users, by defining CICS auxiliary temporary storage in DFHTEMP. The spill file is used for extra storage for data and reports.

The installation procedure in this book installs QMF to an individual CICS partition. If you have several users using QMF in different CCS partitions, you might consider lading QMF into the 31-bit shared virtual area. Or, if the QMF users you support routinely use more than 1 MB of GETVIS storage for queries and reports, you might also consider using CICS multiregion operators or intersystem communications to provide more efficient use of CICS resources at your site.

[ Previous Page | Next Page | Contents | Index ]