The Herb Garden

This from IBM...

The MVS high performance option (HPO) can be used for processing VTAM requests. The purpose of HPO is to reduce the transaction pathlength through VTAM.

Remember...
- to code an SVCPARM in SYS1.PARMLIB(IEASVCxx)
- to add NUCLST entry to LOAD00 in SYS1.IPLPARM
- to add member NUCLSTxx to SYS1.IPLPARM

The following USERMOD should install the CICS HPO exit in SYS1.NUCLEUS via SMP/E.

This should be two stage process for safety sake but could be completed in one job.

Create and implement new certificate

//*
//* +--------------------------------------------------------------+
//* | NEWCERT1: Rekey certificate and rollover |
//* +--------------------------------------------------------------+
//*
//NEWCERT1 EXEC PGM=IKJEFT01
//SYSTSPRT DD SYSOUT=*
//SYSTERM DD DUMMY
//SYSTSIN DD *
PROF MSGID WTPMSG
/* */
RACDCERT ID(TCPSTC) -
REKEY( -
LABEL('TN3270 SERVER SELF SIGNED CERT')) -

Thresholds can be displayed via the “Problems” screen from the “CICS Region Menu” or the CREGPRB view display.
Each threshold represents the upper limit of a range of measurable values.
The colour of a message indicates whether an informational, a warning, or a severe threshold has been exceeded.
This document explains how to set problem thresholds with the CMRPRBT macro. This macro generates a problem message threshold table.
Each table entry consists of a message number followed by the thresholds that trigger the display of informational, warning, and severe messages.

PCI compliance involves, amongst other things, encrypting PAN information, e.g. credit card numbers, using 'strong encryption', e.g TDES. Coded CICS programs to make ICSF calls (CSFENC and CSFDEC) to encrypt and decrypt data using secure keys. We hit a little bit of a glitch earlier this week (courtesy of IBM) in securing access to the ability to decrypt data.

CICS Transaction Server for z/OS V2.2 - 30th April 2008

CICS Transaction Server for z/OS V2.3 - 30th September 2009

(This from IBM documentation...) 

Containers are named blocks of data designed for passing information between programs. You can think of them as “named communication areas (COMMAREAs)”. Programs can pass any number of containers between each other. Containers are grouped together in sets called channels. A channel is analogous to a parameter list.

LLA and VLF

Modules loaded by CICS from the DFHRPL (or dynamic LIBRARY concatenation) may be managed by the MVS LLA (library lookaside) facility.

LLA is designed to minimize disk I/O by keeping load modules in a VLF (virtual lookaside facility) dataspace and keeping a version of the library directory in its own address space.

LLA manages modules (system or application) whose library names you have put in the appropriate CSVLLA member in SYS1.PARMLIB.

There are two optional parameters in this member that affect the management of specified libraries: