Previous Topic: Updateable User Code CopiesNext Topic: Dynamic Storage Area (DSA)


Temporary Storage Record Naming Conventions

Assuming the following:

tttt-CICS terminal-ID

?-Product generated character

!xx!-Hex characters

uid-CA Ideal short-ID user definition

sys-CA Ideal short-ID system definition

Most of CA Ideal Temporary Storage records are built using the following naming convention:

$t?ttt??

There are two other types of records you find that do not follow this naming convention. These two types of records represent the CA Ideal users and CA Ideal systems.

User Records

Most of these records have a length of 2048 bytes.

When SECRTY=YES: ??????!6200!

When SECRTY=NO: $I?uid!6200!

The records are not deleted even after the user signs off CA Ideal. These records eliminate the need to re-access the dictionary for signon information, thereby improving signon performance for subsequent signons to CA Ideal for manual signon or transactions invoked by $FINAL-ID.

System Records

A temporary storage record is explicitly written to main temporary storage normally consisting of 90 bytes for each CA Ideal system that was accessed in the particular CICS region.

Its naming convention is: $I!00!sys!6100!

These records are not deleted from temporary storage unless the CA Ideal system definition is updated in the CICS region. The presence of these records improves performance by eliminating the need to access the dictionary each time a system is accessed in the region.

VPE writes the following two types of temporary storage records:

A Temporary Storage record for each terminal session called the VPE Session Anchor Block (VSAB). It contains a list of all of the active control blocks, Temporary Storage records, addresses to EDSA for the user's session. Its naming convention is VSABtttt.

A Temporary Storage record with the naming convention:

$VPtttt?.

Datadictionary also builds some temporary storage records to maintain information across transaction boundaries that it needs. These records are named as follows:

#tttt???