Dynamic Scripting and CICS/TS 4.2

Are you using the new Dynamic Scripting Feature Pack? If so, you must be running CICS/TS 4.1 … There was only a limited SupportPac for CICS/TS V3, and IBM just announced that the Dynamic Scripting Featue Pack is not supported on CICS/TS 4.2.

CICS/TS 4.2 supports only 64-bit JVM’s, and the feature pack has environment variables set for using 31-bit JVM’s. We will be watching for an update from IBM soon, as supporting dynamic scripting was listed on the CICS/TS 4.2 Announcment Letter‘s Statement of Direction.

Follow theCICSguy on twitter here

Advertisements

Accessing “The Good Stuff” With CICS Explorer in CICS/TS 4.1

When I initially installed CICS/TS 4.1 in our Systems test environment, I started looking for what was new and improved in this version over the 3.2 we had been running. One thing I was looking forward to was seeing the “update” options available in CICS Explorer; in version 3 of CICS/TS, there were many options teasingly grayed out. However, when I loaded CICS Explorer and pointed it at my shiny new CICS/TS 4.1 region, those options were still grayed out!

After doing some web searches, I found information that indicated that to access the update functions, I would need to change the CICS Explorer connection type from CICSPlex SM Data Interface to CICS Management Interface. Of course, nothing is ever that easy …

When I changed the CICS Explorer to use  the CICS Management Interface, I got the following error when I tried to connect:

org.xml.sax.SAXParseException: The element type “HR” must be terminated by the matching end-tag “</HR>”

Boy, it is really clear what this means, isn’t it? Translated into English, this is what it is really saying:

“You tried to access a port with the wrong protocol; make sure you are using a CICSPlex SM Data Interface to access a WUI port, or a CICS Management Interface to access a CMCI port.”

Up to this point, I had never heard of a CMCI port. However, it was fairly trivial to define new WUI parm, CMCIPORT, and point CICS Explorer to that port when using the CICS Management Interface. Once that was done, I magically got all the update options.

IBM has a procedure documented for setting up CMCI in stand-alone (non-CICSPlex) CICS regions so that they, too, can be accessed with CICS Explorer. (Thanks go to Chris Hodgins over at The Master Terminal for that link!)

Follow theCICSguy on twitter here

Implementing CICSPlex Part 4 – Connecting “Regular” CICS Regions to the CICSPlex

If you have performed the first 3 parts of this series of blog posts, then you are ready to connect your “regular” CICS regions to the CICSPlex. And that is probably the simplest part of the process!

The “regular” CICS’s are known as LMAS’s, or locally managed address spaces; in the CICS documentation, you may see them referred to as just managed address spaces.

As in the CMAS and the WUI regions, add the SEYUAUTH library to the STEPLIB concatenation, and the SEYULOAD library to the DFHRPL concatenation, and add an EYULOG DD.

In the SIT table, add the CPSMCONN=LMAS parameter, and make sure MN=ON is set.

That’s it! When you start up LMAS’s, you should see messages in the log where they connect to the CICSPlex. If you point a browser at http://hostname:portnumber, you should be able to sign on with your security id/password, and see information for the LMAS’s, such as current tasks active, files, programs, and other resource information – it is amost like CEMT on steroids!

This concludes the series of postings on establishing a CICSPlex, but we surely have not seen the end of this topic! I’m sure in the future I’ll post write-ups about CICS Explorer and other topics related to CICSPlex.

Follow theCICSguy on twitter here

Implementing CICSPlex Part 3 – Convert an Existing CICS into a WUI

The WUI, or Web User Interface, is the “console” for the CICSPlex. Originally a TSO interface was supported, but now there is only the WUI. There are several good sources that show how to create a WUI, including Dave Williams’ excellent article on MainframeZone.com, but some may not wish the overhead of another region and would prefer to use an existing region; a TOR is a good logical choice. However, be aware that the WUI runs auxtrace constantly (regardless of what you may have in the SIT or overrides), so you’ll be adding that activity to a region within which you choose to implement the WUI. To avoid constant changes of auxtrace files, you’ll probably want to reallocate the trace datasets for the WUI to be pretty large. If the tracing activity is a concern, then you’ll want to choose a different region, or create a new region for the WUI.

Start-up JCL

As in the CMAS, you’ll need the SEYUAUTH library in the STEPLIB concatenation and the SEYULOAD library in the DFHRPL concatenation. You’ll want to allocate a SYSOUT DD for EYULOG.

SIT and Overrides

In the DFHSIT table, or its SYSIN overrides, add the CPSMCONN parameter and set it to WUI. Add an INITPARM and set it to (EYU9VKEC=’ENU’,EYU9VWAN=’ENU1′); if you already have an INITPARM, then add the EYU9VKEC and EYU9VWAN parameters. Make sure that TCP is set to YES.

WUI Repository

Allocate a VSAM dataset to serve as the WUI repository:

//DELWREP  EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
DELETE YOUR.EYUWREP
SET MAXCC=0
/*
//DEFWREP  EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
DEFINE CLUSTER(NAME(YOUR.EYUWREP)-
INDEXED -
CYL(5 1) -
SHR(2)-
CISZ(8192) -
SPANNED -
VOLUME(your-volume)) -
DATA(NAME(YOUR.EYUWREP.DATA)-
RECORDSIZE(8192 32000) -
KEYS(20 20)) -
INDEX(NAME(YOUR.EYUWREP.INDEX))
/*

Add a EYUWREP DD to the start-up JCL, with DISP=SHR.

CICSPlex Parms

You’ll need a dataset to contain the CICSPlex-specific parms for the WUI:

NAME(wui-name),
CICSPLEX(CICSPlex-name),
CMASSYSID(CMAS-id)

Set NAME to match what you put in for WUINAME in the CMAS repository, and CICSPLEX must be set to the same value as that in your CMAS’ CICSPlex parms, and CMASSYSID must be set to the SYSIDNT of the CMAS. You’ll probably want to add  a SEC parameter and set it to NO initially, and set security after you have basic functionality.

Add a EYUPARM DD to the start-up JCL pointing to your parm file and member, with DISP=SHR.

WUI Parms

The WUI will need a WUI parm dataset defined, with the following parameters:

TCPIPHOSTNAME(tcpip-host-name)
TCPIPPORT(port-number)
DEFAULTCMASCTXT(cmas-name)
DEFAULTCONTEXT(CICSPlex-name)
DEFAULTSCOPE(scope)
AUTOIMPORTDSN(YOUR.SEYUVIEW)
AUTOIMPORTMEM(EYUEA*)

Set TCPIPHOSTNAME to the host name for your MVS image, and TCPIPPORT to the port number you wish for the WUI to use. Once this region is up, you can access the WUI by pointing a browser to http://tcpip-host-name:port-number .

Set DEFAULTCMASCTXT to the the CMAS name (same value as the CMAS name in your CMAS parms), and set DEFAULTCONTEXT to the CICSPlex name to the Plex name (same value as WUIPLEX in your CMAS repository). You will probably want to set DEFAULTSCOPE to the CICSPlex name, as you’ll probably prefer the scope of the WUI views to default to the entire CICSPlex than a specific CICS or group of CICS systems.

The last two entries can be removed after the initial successful start-up of the region. They specify to load the English “views” from the SEYUVIEW dataset. You can modify these or code your own views and load them later.

Add a EYUWUI DD to the start-up JCL pointing to this dataset, with DISP=SHR.

That’s it for the WUI. Start it up, and it should connect to your CMAS. Load your browser and point it to the host name and port number, and you should see the shell of a CICSPlex. Next time we’ll look at adding CICS regions to the new CICSPlex.

Follow theCICSguy on twitter here

Implementing CICSPlex Part 2 – Defining the CMAS

The CMAS, the primary CICSPlex region, is pretty much the same as any other CICS region with a few exceptions. In this posting, we’ll review the special parameters and data sets necessary for the CMAS CICS to perform CICSPlex functions. Continue reading

Implementing CICSPlex Part 1 – Planning the Environment

It will take more information than I can provide here to fully plan out a new CICSPlex environment, but I will hit on some of the primary things that should be considered, and how I decided to lay out the CICSPlexes in our shop. Continue reading

Implementing CICSPlex – Overview

It’s been a while since I’ve last posted, but now I have some time and an interesting topic, one that will span several postings. I have had it on my to-do list for some time to implement CICSPlex; it is obvious that IBM views this as a central component to managing CICS regions. It is now part of the CICS/TS installation (no need to download or install any additional components to implement); a lot of great documentation is available (a whole series of manuals dedicated to it); and CICS Explorer, touted as the “new face of CICS”, requires it as a prerequisite (or at least CICSPlex is a prerequsite for CICS Explorer in V3 of CICS/TS, but not in V4). Chris Hodgins over at The Master Terminal posted 6 reasons you should implement CICSPlex. However, I just could not find the time to put all the pieces together to get it set up in our shop. Recently I was able to dedicate a few days to it, and with the assistance of a colleague who had already been through it, I was able to get the ball rolling. In this series of postings, I hope to make clear some of the concepts and steps that had me stopped until I had the time and assistance to set it up.

Below is an overview of what is to come in future postings:

  1. Plan the environment
  2. Define the CMAS
  3. Convert an existing CICS into a WUI
  4. Set up other CICS’s as LMAS’s

So that’s four more postings that should be coming in the near future. If you have not implemented CICSPlex yet, perhaps this will help you get the ball rolling, as my colleague helped me. If your shop is like ours, you are up to your eyeballs just keeping things going and don’t have a lot of time for basic research; a little assistance can go a long ways.

Follow theCICSguy on twitter here