Using the IBM Cross System Product
The following information about the IBM Cross System Product (CSP) 4GL
application generator concentrates on tests carried out running CSP 3.3, but in
general the information also applies to later releases of CSP.
There are two components to CSP:
v CSP/AD (Application Development) is used to develop the applications
v CSP/AE (Application Environment) is the run-time environment for application
execution.
If you use the IBM Cross System Product to develop your applications and, in
particular, use CSP/AE as the run-time environment for the applications, the
Reporter report will contain a large number of transaction groups. These groups are
created because of the way that CSP/AE uses EXEC CICS commands, and in
many cases do not cause real affinities.
Affinity analysis for a CICS region containing CSP 3.3 applications
When CSP 3.3 is used to develop and execute CICS pseudoconversational
applications, the main CSP affinity is LUNAME/PCONV TS queue affinity, which can
be dealt with either by CICSPlex SM or by a queue-owning region (QOR). The only
other real affinity likely to be encountered is the use of non-read-only CSP shared
tables, and the scope of this affinity depends on the tables and applications
involved.
CSP internally uses these CICS resources and commands in the following ways.
They can cause transaction affinities, and these appear in the Transaction Affinities
Utility report.
ENQUEUEs/DEQUEUEs
are used to serialize the loading of CSP tables and applications from VSAM
files called ALFs (application load files). They are also used to serialize writing
messages to TD destination CSMT.
Shared storage
When a CSP application or table or map from an ALF has completed loading, it
is copied to shared storage. Note that some of these tables may be defined by
the application developer as SHARED and made resident by the CSP utility
program ALFUTIL. Such tables may be shared between applications, and may
be updated.
Temporary storage queues
CSP allows division of applications into ’segments’. This is just another name
for a pseudoconversational application. CSP uses TS to save state data
between transactions in the pseudoconversation, building the TS queue name
from the termid to ensure uniqueness.
SPI commands
are used to inquire on system attributes such as the version and release of
CICS in use, to set up and share a user exit global work area (GWA), and to
obtain file characteristics of the ALFs.
50 CICS Transaction Affinities Utility Guide