Because CA Ideal executes in pseudo-conversational mode, there is significant use of CICS auxiliary temporary storage. You can define CICS auxiliary temporary storage to reside on a VSAM data set or be diverted to CICS main temporary storage. See IBM documentation for more information regarding CICS temporary storage use and its location.
Consider a user session to be the processing that occurs from the time signon to an SCF-based transaction occurs until signoff is complete. A series of control blocks keep track of each user's session.
Many of these control blocks are written to CICS temporary storage at transaction termination and retrieved into temporary storage buffers that reside in DSA at transaction initiation. In an attempt to minimize the number of writes to temporary storage, these control blocks comprise a single temporary storage record that can be as large as 32 KB.
The most significant of these control blocks include:
Important! Never modify or delete any CA temporary storage queues. This would very likely cause storage violations in CICS. See Session Storage Cleanup in this chapter for information regarding the PURGE termid command and VPE code invoked through NEP.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|