SOLVE:Operations Automation - Want to automate the startup/shutdown of JVM inside CICS

Products

• SOLVE:Operations Automation
• SOLVE:Access Session Management
• SOLVE:FTS
• SOLVE

Issue/Introduction

Want to automate the startup/shutdown of JVM inside CICS.

when we issue F CICS,CEMT SET JVM(DFHWLP) EN / DIS to enable or disable JVM, below is the log, we define a LOGICAL resource in monitoring, with status message "BEING ENABLED" as "STARTING", but it never show status as STARTING.

Once we activate the resource, it immediately turns to ACTIVE even actual state is still enabling.

Do you have a new template for CICS JVM kind of resource or how can we fix this?

Jvmserver(DFHWLP)              

Enablestatus( Disabled )  

...      

BEING ENABLED 

Environment

Release :

Component : CA SOLVE:Operations Automation for z/OS

Resolution

After reviewing your messages I think a USRCLS resource set up as follows should do the job. 

I called the resource CICSJVM for the purposes of this exercise. 

NOTE: you will need a couple of processes as well, that I have called JVMSTART and JVMSTOP, which I will also cover here. 

 

Firstly, the Display and Heartbeat screen:

NOTE: I have used a 1 minute heartbeat. You can set whatever value works for you. 

 

Next the Activation screen: 

This uses a PROCESS called JVMSTART. 

 

The PROCESS looks like this: 

 

The PARAMETERS for S1 look like this:

It will return RC=0 if it sees "BEING ENABLED" otherwise it will timeout after 5 seconds and return RC=69

 

The PARAMETERS for S2 look like this:

It is run if S1 returns RC=0 and sets the state of the resource to STARTING

 

The PARAMETERS for S3 look like this:

 

Next the Inactivation screen:

 

JVMSTOP looks just like JVMSTART except: 

 

S1 issues F CICSDEBK,CEMT S JVM(CPFWLPO) DI and looks for BEING DISABLED. 

S2 sets the state to STOPPING. 

 

Once these processes run, the next heartbeat should set the state to ACTIVE or INACTIVE.