Daily maintenance cycles:
(Agenda Item #2.)
- CICS request/memo processing overview:
- We re-IPL our prod. z/OS LPAR every other (non-payroll) week, currently.
- We have processes and procedures in place to handle
CICS 24x7 operation. Currently, only CICSPRD4 and CICSPRD5
run in "near 24x7" mode. We would like to discontinue the
daily reload of CICSPRD1.
- We make application changes to CICS almost daily.
- We make system changes to CICS "as needed" (infrequently).
We typically do internal testing, then dev./test region
testing, then test/QA testing, and finally, prod. install.
- We handle emergency requests on a case by case basis.
- Please send CICS request email to the entire CICS Systems Group:
cicsgrp@cns.ufl.edu
- Prod. and dev./test requests must be separate.
- See 'CICS.USER.SAMPLIB(CICSMEMO)' for a prod. skeleton
request.
- See 'CICS.USER.SAMPLIB(DELTMEMO)' for a skeleton
delete/clean-up request.
- See 'CICS.USER.SAMPLIB(HELPMEMO)' for help with the
memo/request processing.
- See 'CICS.USER.SAMPLIB(TESTMEMO)' for a test skeleton
request.
- Prod. requests have priority, then dev./test requests,
then delete/clean-up requests. Requests submitted
correctly on the first attempt get highest priority ;-).
- Request processing is automated, with some basic validation
and sanity checking.
- CNS maintains repositories of all prod. source and copy code.
- CNS maintains repositories of all prod. compilation/assembly listings.
- Prod. regions only have prod. loadlib.
- Test/QA regions have prod. staging loadlib (CICS.TEST.DGLIB),
then development group test loadlibs, then the prod. loadlib.
- Dev./test regions do not have the prod. staging loadlib.
- We have a prod. and a test DBRMLIB for CICS DB2 programs.
CICS tools:
(Agenda Item #3.)
Last updated: 11-30-2005, by Steve Ware.