Let's understand Mainframe
Home Tutorials Interview Q&A Quiz Mainframe Memes Contact us About us

Module 12: CICS Resource Definitions and Administration


Resource Installation

Defining a resource is only half the job. Installation is what makes the definition live in the running CICS system. This page covers how installation works, the alternative ways to define resources, and how to keep definitions healthy.

Installing definitions

  • CEDA INSTALL GROUP(name) copies every definition in the group from the CSD into the running region. From that second, tasks use the new values.
  • CEDA INSTALL LIST(name) installs every group in the list - the fast way to bring up a whole application.
  • At startup, the GRPLIST parameter installs its list automatically, so the region opens with everything it needs.
  • Re-installing a group replaces the active definitions with the current CSD copies - the standard way to activate CSD changes.
  • Some resources need extra steps after install: files may need CEMT SET FILE OPEN, programs may need NEWCOPY.

All the ways to define resources

  • RDO online - CEDA (full), CEDB (no install), CEDC (view only). The normal day-to-day method.
  • EXEC CICS CREATE - system programming commands that build resources in the running system directly, without the CSD.
  • EXEC CICS CSD commands - let a program manage CSD definitions; everything CEDA does except CHECK.
  • DFHCSDUP - offline batch utility to list, add, alter and delete CSD definitions without a running region.
  • Autoinstall - CICS creates definitions automatically from a model when a new terminal, program, mapset or journal appears.
  • Macro definition - the old assembler-macro method; kept for history, RDO replaced it.

Keeping definitions consistent

  • Always CEDA CHECK a group before INSTALL - it is cheaper than debugging a broken live install.
  • LOCK groups while changing them so two people cannot edit at once; UNLOCK when finished.
  • Back up the CSD regularly - it is the master copy of every definition in the shop.
  • Keep test and production CSDs separate; migrate definitions with COPY, never by editing production directly.
  • After any install, verify with CEMT INQUIRE that the live values match what you intended.

Example - list a group offline with DFHCSDUP, then install it:

//CSDUPD EXEC PGM=DFHCSDUP,REGION=0M //STEPLIB DD DSN=CICS.SDFHLOAD,DISP=SHR //DFHCSD DD DSN=CICS.DFHCSD,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSIN DD * LIST GROUP(ORDGRP) OBJECTS /* * then online, in CICS: CEDA CHECK GROUP(ORDGRP) CEDA INSTALL GROUP(ORDGRP) CEMT INQUIRE TRANSACTION(ORD1)





© copyright mainframebug.com
Privacy Policy
MainframeBug Assistant