CICS ADMINISTRATION

TABLE OF CONTENTS

1. 2.

ABOUT THIS BOOK CICS ADMINISTRATOR TASK 2.1 Monitoring CICS log

2.2 Defining and installing various IDs 2.3 CICS SIT Parameters 2.4 CICS TRANSACTIONS 2.5 CICS Start up and shutdown

3. 4. 5.

CICS UTILITITES CICS INSTALLATION CICS errors

1 ABOUT THIS BOOK

This book will explain the various tasks of CICS administrator and solutions for the problems which we will face commonly and also it explains about the various transaction and parameters which is used in CICS.

2. CICS ADMINISTRATOR TASK

Monitoring CICS log Defining and installing various IDS to user like program-id,Trans-id,file-id,Mapset,Db2 Entries and maintaining those IDS Adding SIT (system initialization parameters) if needed CICS Startup and shut down Knowledge of Various Transaction Knowledge of CICS startup procedure

2.1 MONITORING CICS LOG

The CICS log is monitored by using following command

CEMT INQUIRE TASK

It shows the various tasks that are being executed in CICS along with the priority. Task which is having 001 can be purged if it exists for more time. It shows along with the transaction that is being executed with the CICS. We can purge by using.Priority varies from 001-255 where 255 is the highest priority.

CEMT INQUIRE TASK F

This manual purging can be avoided if we set the ICVR parameter in CICS

2.2 DEFINING AND INSTALLING VARIOUS IDs Mainly in CICS we have to give the user Program-id, Transid, db2Entry, File Entry, Mapset Entry, TDQ entry and we have monitor the CICS jobs .If it is in loop we have to purge the Job.

This can be defined and installed in two ways:

1. 2.

Manually defining thru CICS. Through submitting JCLS present in (sysadm.cics.jcls)

Manually Defining:

1.

Enter into CICS region specify the following command:

CEDA DEF PROG

Specify the program name to be -> user-id P Specify the Group name to be -> DEVP Specify the language which user uses -> COBOL, Assembler etc

After giving all these entries press enter so that you will be getting define successful.

CEDA DEF TRANS -> T o define transaction

Specify Transaction id: First 3 letters of the user-id (e12345): Trans-id: E123 (Maximum of 4 characters) Specify Program name: User-id P Specify Group: DEVP

CEDA DEF DB2 ENTRY:

Specify db2 entry: User-id P Plan Name: User-id p Trans-id: E<last3 characters of user-id>

Like wise look into JCLs present in sysadm.cics.jcls and specify all the other entries. Installation of the entries:

CEDA DIS GROUP (DEVP) Place I to install the entries.

Submitting through JCLS: We can use the JCLS which is present in SYSADM.CICS .JCLS. Install the entries by the above way.

Purge the CICS Task : Whenever CICS seems to be slow, it may be due to CICS jobs in loop

The Priority which is in 255 is completed .The job which is in 001 is in loop .So we can purge that job by specify f near that.

2.3 CICS SIT PARAMETERS:

SIT is the System Initialization Parameters. During the start up of CICS, it reads the dataset CICSTS22.CICS.SYSIN (DFHSIP1).Depending on these parameters only we can able to perform various operations:

The following are the SIT parameters defined in our system.

XRF: (Extended Recovery Feature option)

Options:

XRF=YES/NO

Description: If this parameter is defined as YES then there are two CICS regions and CICS system definition file should be shared with both the regions. However, when you run CICS with XRF, CICS always ensures (except for the CSD) that there is no conflicting concurrent use of data sets by an active CICS region and its alternate CICS region, even though they are running in different MVS images.

Our Current Config: As for as now we are having only one region CICS1.So XRF=NO

EDSALIM: (Extended Dynamic Storage Areas)

Options:

EDSALIM ={20M|number}

Descriptions: Specifies the upper limit of the total amount of storage within which CICS can allocate the individual extended dynamic storage areas (EDSAs) that reside above the 16MB boundary. 20M The default EDSA limit is 20MB (20 971 520 bytes). Number Specify number as a value in the range 10MB to 2047MB, in multiples of 1MB. If the size specified is not a multiple of 1MB, CICS rounds the value up to the next multiple. You can specify number in bytes (for example, 33 554 432), or as a whole number of kilobytes (for example, 32 768K), or a whole number of megabytes (for example, 32M).

Our Current Config: This extended storage is specified as 60M as our configuration.

GMTRAN :( Good Morning Transaction)

Options :

GMTRAN=( Some transaction Name

Description: This is the transaction which is going to be executed when we SIGNON in CICS region.

Our Current Config : GMTRAN=CESN

GMTEXT: (Good Morning Text)

Options : GMTEXT=ANY TEXT

Descriptions: Text which is going to be executed while signon to the CICS

Our system config: GMTEXT= WELCOME TO IFLEX CICS

APPLID: (Application ID)

Options: APPLID=<cics application-id>

Description: ID for CICS. This ID should match with the VTAM ACBNAME Parameter which is in SYS1.VTAMLIST

Our system config : CICS1

MXT : (Maximum Number of Concurrent Task in CICS)

Option: MXT={5|number}

Description: Maximum number of user task that can be executed at a time .The Number can vary from 1 thru 999.It does not include CICS system Task.

Our system Config: MXT=60

SEC: (Security)

Option : SEC=YES/NO

Description: Specifies what level of external security you want CICS to use. YES You want to use full external security. CICS requires the appropriate level of authorization for the access intent: a minimum of READ permission for read intent, and a minimum of UPDATE permission for update intent. No: Security is not implemented

Our system Config: SEC=YES

GRPLIST: (Group List)

Options : GRPLIST={DFHLIST |name|(name[,name2][,name3][,name4])

Description: specifies the names (each 1 through 8 characters) of up to four lists of resource definition groups on the CICS system definition (CSD) file. The resource definitions in all the groups in the specified lists are loaded during initialization when CICS performs a cold start. If a warm or emergency start is performed, the resource definitions are derived from the global catalog, and the GRPLIST parameter is ignored. Any duplicate resource definitions in later group lists override those in earlier group lists. Do not code GRPLIST=NO unless you have a group list named NO.

Our system Config : GRPLIST=IVPLIST (view the group in the list by CEDA DIS LIST(*))

AUXTR: (Auxiliary Trace)

Options: AUXTR ={OFF|ON}

Descriptions: You may need to use auxiliary trace data sets to avoid the loss of diagnostic information, because internal trace table entries wrap around. When the end of the internal trace table is reached, subsequent entries overwrite those at the start of the table. To get a trace of CICS activity in which trace entries are not overwritten, use the auxiliary trace data sets. This can be particularly useful if you are using CICS trace during startup, because of the high volume of trace entries written when CICS is initializing .

Specifies whether the auxiliary trace destination is to be activated at system initialization. This parameter controls whether any of the three types of CICS trace entry are written to the auxiliary trace data set. The three types are: CICS system trace (see the SYSTR parameter), user trace (see the USERTR parameter), and exception trace entries (that are always made and are not controlled by a system initialization parameter). OFF Do not activate auxiliary trace. ON Activate auxiliary trace.

Our System Config: AUXTR=ON Datasets are: CICSTS22.CICS.CICSHW61.DFHAUXT CICSTS22.CICS.CICSHW61.DFHBUXT

AUXTRSW: (Auxiliary Trace switch)

Options:

AUXTRSW ={NO|ALL|NEXT}

Descriptions: specifies whether you want the auxiliary trace autoswitch facility. NO Disables the autoswitch facility. NEXT Enables the autoswitch facility to switch to the next data set at end of file of the first data set used for auxiliary trace. Coding NEXT permits one switch only, and when the second data set is full, auxiliary trace is switched off.

ALL Enable the autoswitch facility to switch to the inactive data set at every end of file. Coding ALL permits continuous switching between the two auxiliary trace data sets, DFHAUXT and DFHBUXT, and whenever a data set is full, it is closed and the other data set is opened.

Our System Config: AUXTR=NEXT

DB2CONN: (Db2 Connection)

Options: DB2CONN=YES/NO Descriptions: specifies whether you want CICS to start the DB2 connection automatically during initialization. NO Do not automatically invoke DFHD2CM0, the CICS DB2 attach program, during initialization. YES Invoke the CICS DB2 attach program, DFHD2CM0, automatically during CICS initialization .Specifying DB2CONN=YES is the recommended

Our System Config : DB2CONN=YES

MQCONN: (MQ series Connection)

Options: MQCONN=YES/NO

Descriptions: specifies whether you want CICS to start the MQSeries for MVS/ESA connection automatically during initialization. NO Do not automatically invoke CSQCCODF, the MQSeries attach program, during initialization. YES Invoke the MQSeries attach program, CSQCCODF, automatically during CICS initialization.

Our system Config: MQCONN=YES

XCMD: (External command security)

Options: XCMD ={YES|name|NO}

Descriptions: This is the External command security checking. If Yes is specified then if anyone trying to use a CICS resource ,it will check for RACF protection with that user-id and proceed if the user is authorized No: It wont check for security Our System Config: Initially it was set to XCMD=NO, But now it is XCMD=yes

XDB2: (External Db2 security)

Options: {NO|name}

Descriptions: specifies whether you want CICS to perform DB2ENTRY security checking. NO CICS does not perform any DB2 resource security checks. Name CICS calls RACF, using the specified general resource class name, to check whether the userid associated

with the CICS DB2 transaction is authorized to access the DB2ENTRY referenced by the transaction.

Our system Config :XDB2=NO

Like wise we are having some parameters for external security XTRAN (External Transaction security): It is defined as YES in our system. Define whether to use RACF for resource level checking by using the XDCT, XFCT, XJCT, XPCT, XPPT, XPSB, and XTST system initialization parameters. Define whether to use RACF for transaction-attach security checking by using the XTRAN system initialization parameter .XUSER is for surrogate user.

INITPARM: (Initialization Parameter)

Options : INITPARM =(pgmname_1='parmstring_1'[, .... ,pgmname_n='parmstring_n'])

Descriptions: Specifies that parameters are to be passed to application programs that use the ASSIGN INITPARM command.

Our system config: INITPARM=(CSQCPARM='SN=CSQ1,TN=001,IQ=CICS1.INITQ')

SYSIDNT: (System Identification) This for indentification of system subsystem.It is defined as SYSIDNT=1 in our system

Apart from this there are parameters for the BMS (Basic Mapping support) operations 1. PGRET =/P for BMS retrieval command 2 PGPURGE=T/, for BMS purge commands command 3. PGCOPY=C/, for BMS copy 4 PGCHAIN=X/, FOR BMS chaining command

CICS START UP AND SHUT DOWN PROCEDURE:

There are 3 types of start in CICS 1. 2. 3. COLD START EMERGENCY START WARM START

COLD START: /S CICS1 START=COLD

Log records for local resources are purged and resource definitions rebuilt from the CSD or CICS control tables. Units of work on other systems are resynchronized with this system, as described under START=COLD. WARM START: /S CICS1 START=WARM A warm start restores CICS to the state it was in at the previous shutdown. START: /S CICS1 START=INITIAL You should rarely need to specify START=INITIAL; if you simply want to reinstall definitions of local resources from the CSD, use START=COLD instead. Examples of times when an initial start is necessary are: When bringing up a new CICS system for the first time. After a serious software failure, when the system log has been corrupted. If the global catalog is cleared or reinitialized.

When you want to run CICS with a dummy system log. (If the system log is defined as a dummy, it is ignored.) If it is necessary to perform an initial start of CICS, you can do so in two ways: By specifying START=INITIAL. By using the recovery manager utility program, DFHRMUTL, to set the auto start override record to AUTOINIT, and specifying START=AUTO.

CICS UTILITIES: 1. DFHLSCL

DFHLSCU is a migration utility that helps you to define your CICS Transaction Server for OS/390 Release 3 log streams, based on your CICS/ESA 4.1 or CICS/ESA 3.3 journaling activity. It examines one or more CICS/ESA 4.1 or CICS/ESA 3.3 journal data sets, and produces a report Note: As of now it is not needed to use this utility. For further information refer IBM manual CICS operations and utility guide

DFHSTUP

The statistics utility program, DFHSTUP, prepares and prints reports offline, using the CICS statistics data recorded on the MVS system management facilities (SMF) SYS1.MANx data sets. To enable the CICS statistics domain to record interval statistics on these SMF data sets, you must specify the STATRCD=ON system initialization parameter. Refer to the JCL: SYSADM.CICS .SMF.JCL Various steps to be performed 1. 2. RUN THE SMF JCL FROM THE OUTPUT FOR EX: SMFDUMPS.Y04.OCT WE HAVE TO RETREIVE ONLY RECORD TYPE 110 WHICH IS THE CICS RELATED TYPE 3. FOR THE ABOVE OPERATION SUBMIT SYSADM.CICS.SMF.JCL BY MAKING CHANGES IN INPUT 4. WE CAN ABLE TO SEE THE OUTPUT REPORT IN SPOOL

Various Information that is being collected for this report is: AUTOINSTALL CONNECTION DBCTL DB2 DISPATCHER ENQUEUE FEPI FILE JOURNAL

LOGSTREAM LSRPOOL MONITOR PROGAUTO PROGRAM RECOVERY STATS STORAGE SYSDUMP TCPIPSERV TABLEMGR TDQUEUE TERMINAL TRANCLASS or TCLASS TRANDUMP TRANSACTION TSQUEUE USER VTAM > in SYSIN of

You can select the particular type to get the particular information by giving SELECT TYPE=< the JCL and also you can ignore the particular type by giving IGNORE TYPE=< >.

There is another option called COLLECTION TYPE = <ALL/INT/EODREQ/RRT/USS> which you can code to get the information in interval basis or all or End of Day,

or Format requested statistics for all of the selected

APPLIDs, or RRT Format requested reset statistics for all of the selected APPLIDs, or USS Format unsolicited statistics for all of the selected APPLIDs DFHTU530 It is a Trace utility program There are three destinations for CICS region trace data: A table in main storage, when you specify INTTR=ON and SYSTR=ON as system initialization parameters The CICS auxiliary trace data sets, when you specify AUXTR=ON and SYSTR=ON as system initialization parameters The MVS generalized trace facility (GTF) data sets, when you specify GTFTR=ON and SYSTR=ON as system initialization parameters.

In our system we storing in the trace at only AUXULIARY datataset CICSTS22.CICS.CICS1.AUXT and CICSTS22.CICS .CICS1.BUXT since we have specified the auto switching option the trace activities will be automatically switch between these once one of the dataset becomes full The Utility DFHTU530 is not used in this case. Note : In our system since DFHT5U30 is not installed we can use DFHTU620 for taking the trace actibities

There are several other utility program in CICS which is used in multiple regions and During initialization of CICS.

DFHLSCU DFHJUP DFH$STER DFHMNDUP DFH$MOLS DFHCSDUP DFHMSCAN DFHEISUP DFHSNMIG DFH$STED DFHMEU DFHCESD DFHRMUTL DFHRMUTL

Log stream and coupling facility| sizing utility Journal select, print, and copy Recovery Statistics Program Monitoring dictionary record Creation Sample Monitoring Formatting System Definition Dataset Utility Macro-level programs Identification Load Module Scanner SIGN on table to RACF migration Sample stagger end of day Message Editing Sample shutdown assist program Recovery Manager Batch utility BMS Macro Generation Utility program

DFH$OFAR DFHSMUTL

Offsite Automatic Reply program Local catalog storage manager domain subpool record manipulation

Refer to the below website: http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/dfhqat38/CCONTENTS\

More common CICS abends

ASRA
This is the most common abend in CICS. It indicates a Program Check Exception, roughly equivalent to having an S0C7 in a batch program. Check for spaces in a packed decimal numeric field and changes to the file and record layouts.

AEIx and AEYx

There are numerous abends that start with AEI or AEY. They indicate that an exception has occurred, and RESP (or NOHANDLE) is not is use. The last character indicates the exact error.

AEI0 indicates a PGMIDERR. AEI9 is a MAPFAIL condition. AEIO indicates a duplicate key (DUPKEY) condition. AEIN indicates a duplicate record (DUPREC) condition. AEID indicates an End of file condition. AEIS indicates that a file is not open (NOTOPEN)

AEIP indicates an invalid request condition (INVREQ) AEY7 indicates that you are not authorized to use a resource (NOTAUTH)

AICA
This abend usually occurs if your program is looping. There are CICS parameters that determine how long a task can run without giving up control. The ICVR parameter in the CICS SIT table can be used to specify a value for all tasks running in CICS, or you can specify a RUNAWAY value when you define a transaction. If a program is looping then you may not get an AICA abend, because the timer can be reset when certain events occur, e.g. some EXEC CICS commands may reset the timer to zero.

AEY9
With CICS/ESA Version 3, you can use the following CICS command to detect W hether the CICS attachment facility is enabled:

EXEC C IC S EXT R AC T EXIT PROG R AM ( D SN C EXT 1) ENTRY ( DSNCSQL) G ASET (n am e1) G AL EN GT H (n am e2)
If you get the INVEXITREQ condition, then the CICS attachment facility is not Enabled. However, there is a short window between the CICS attachment Facilitys enable and the enable start where the CI CS attachment facility is still not available. During that period, you can get an AEY9 ABEND. INQUIRE EXITPROGRAM is a new command that CICS/ESA Version 4 provides. You can use it in place of the EXTRACT EXIT command to determine whether theCICS attachment facility is enable-started, enabled, or disabled. If the attach is enabled without being enable-started, you can still get an AEY9 abend, and the EXTRACT EXIT command can tell you only if the CICS attachment facility is enabled.

PQ54479: ABEND AEY9 DURING CONCURRENT DL/I ABNORMAL TASK TERMINATION

Message 'DFHTD0001 .... An abend (code ---/AEY9) has occurred at offset X'085E' in module DFHAPTD' is issued, then CICS comes

Shut down cics and restart again.

ATCH and ATCI

These abends indicates that the task was purged. The task may have been purged by someone issuing a CEMT command to purge the task, or by CICS because the Deadlock timeout limit has been exceeded or because there was not enough virtual storage available to run all the tasks in CICS (Short on Storage)

APCT
A program was not found or was disabled. Check the transaction definition to see if the program name was misspelled. Check that the program is enabled. Check that the program is in an appropriate Load Library (i.e. one defined to the current CICS system).

AKCP and AKCT

These abends indicate that a timeout of the task occurred. This may be due to a deadlock.

AFCA
A dataset could not be accessed because it was disabled.

ABM0
The specified map was not found in the specified mapset. Check that you have not misspelled the map name.