Optimizing Storage Management › Session Storage Cleanup › PURGE term-id › Format

Format

PURGE termid

termid-The four-character terminal ID. You must type this value exactly as generated by the AUTOINSTALL routine since term-ID is case sensitive.

When the session is purged, the following message displays:

Terminal 'termid' purge complete

If the value supplied for termid is not a defined terminal ID, the following message displays:

Terminal 'termid' not found

Check to be sure you entered the terminal ID in the correct case, exactly as the AUTOINSTALL routine generated it.

VSE GETVIS Considerations

When you run applications in a VSE environment, having enough space is critical. CA Ideal under VSE is no exception.

Try some of the following suggestions if you encounter space issues:

• You might want to try decreasing the BUFSPACE parameter on your VSAM files. This degrades performance but it frees up GETVIS. It also requires that you redefine the file (you cannot change it dynamically).
• If you have several regions accessing CA Ideal, you might consider putting heavily used CA Ideal modules in the SVA. The module @IAETINT is a good candidate for moving to the SVA. It is frequently used and is approximately 100 KB in size.

  If you allow both on-line and batch compiles, the compiler modules are also a good choice. Moving those modules can save you GETVIS and free up DSA in CICS if the space in SVA is available.

  To determine which CA Ideal modules are used for compiles, compile a program using the CA Ideal Trace facility:

  @I$TRACE TRACE ON LOCAL
  COMPILE pgmname
  @I$TRACE PRINT FUNC VPE STATISTICS
  

• In batch, you might consider decreasing the size of your VPE file table (@IIDSYSF).

  One way to do this is to eliminate old and unused ROSFD entries for your VLS libraries. Another thing to look at is your ROSFD entries for sequential files. The blocksize parameter on those entries represents a maximum blocksize. The macro is expanded to include the space needed for that blocksize. For example, if you change the blocksize parameter on the ISLTAPE1 ROSFD entry from 4 KB to 10 KB, the size of @IIDSYSF increases by 6 KB. If you know that the largest blocksize you ever need is 4 KB, you have 6 KB of wasted space.

• Another thing to look at is your partition size. There are instances where your partition simply is not large enough.

  For batch, make sure that your SIZE= parameter is correct for the type of function you are trying to perform. If you are trying to compile a program and you are getting insufficient GETVIS messages, check if you are producing a cross-reference. If you really do not need one, SET COM XREF=NO. This frees up more GETVIS for the compile.