Configuration Restrictions

This topic outlines the configuration restrictions when using a Performance and Availability Cluster (PAC) with Redis as its Scale-Out Repository (SOR).

CICS Support

CICS is supported in a PAC with the following CICS resources restrictions:

CSA
The CSA trace flags are shared between regions in a PAC. csa-TCS-unique-generator and csa-ICE-unique-generator are also shared in a PAC.
DCT
Although the DCT resources themselves are stored in the PSOR, the actual queue must be one of the following DCT types in order for it to be stored in a SOR by a SOR Model:
  • Non-recoverable
  • Intra-partition - which includes triggers
  • Indirect - model prefixes work only on the target DCT
Note: Recoverable, internal reader, and extra-partition types cannot be stored in a SOR.

When viewing information about TD queues in ESMAC, the following apply:

  • Information regarding SOR stored queues, such as number of items and depth, can be viewed by any enterprise server instance.
  • Information regarding queues stored on disk is only available to the local enterprise server instance.
FCT
The VSAM file referred to by the resource of this type can be stored in an RDBMS. See the MFDBFH configuration for requirements. Whether or not in MFDBFH, issuing a file close command in any enterprise server instance results in the file being closed by all instances in the PAC.
PCT
Active PCTs in a PAC will have two different count values:
  • A count of the number of times the transaction has been executed across the PAC.
  • A local count for each enterprise server instance of the number of executions in that instance.
PPT
Each enterprise server instance will load user applications from the location specified in its configured transaction path.

If you need to modify a program while a PAC is active, you need to uploaded the new binary file to the PSOR and then issue a New Copy command.

TST
Only non-recoverable queues can be stored in a SOR.

Temporary Storage and Transient Data Queues

Only non-recoverable queues are supported in Redis.

Temporary Storage (TS) and Transient Data (TD) queues can be directed to any SOR; they do not need to be directed to the same SOR that holds the TMP.

Indirect Queues
Model prefixes work on the target queue only:

Model prefix = MYQ

TDQ Name Indirect Name Storage location
MYQ1 TDQ1 Disk
TDQ1 MYQ1 SOR
Triggering
This is supported.
Extra-partition Queues
PAC usage unsupported.
Internal Reader
This is supported.

CICS applications can direct a JCL jobstream to these queues (which are a special type of extra-partition queue) for execution by the JCL engine.

Temporary Storage Queue (TSQ)
This is supported.
Browsing
TSQ browsing supported.

EXEC CICS START @ TERMID

Exec CICS START with a Termid specified is supported in a PAC.

Note: START CHANNEL is currently unsupported.

VSAM Share Options

These are supported.

JCL Support

JCL is supported in a PAC, without restrictions.

IMS Support

IMS is not supported in a PAC.