Get documents about "Migration to VSE-ESA 2.4 and CICS Transaction Server for VSE-ESA 1.1
Document Sample
Migration to VSE/ESA 2.4 and
CICS Transaction Server for VSE/ESA 1.1
Annegret Ackel, Susan Davies, Andonela Guadagno
John Lawson, Keith Miller, Cesar Teixeira
International Technical Support Organization
http://www.redbooks.ibm.com
SG24-5595-00
SG24-5595-00
International Technical Support Organization
Migration to VSE/ESA 2.4 and
CICS Transaction Server for VSE/ESA 1.1
August 1999
Take Note!
Before using this information and the product it supports, be sure to read the general information in
Appendix C, “Special Notices” on page 229.
First Edition (August 1999)
This edition applies to Version 1 Release 1 of CICS Transaction Server for VSE/ESA, Program Number 5648-054
for use with the VSE/ESA Version 2 Release 4, Program Number 5690-VSE.
Comments may be addressed to:
IBM Corporation, International Technical Support Organization
Dept. HYJ Mail Station P099
522 South Road
Poughkeepsie, New York 12601-5400
When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any
way it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 1999. All rights reserved.
Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is
subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
The Team That Wrote This Redbook . . . . . . . . . . . . . . . . . . . . . . . . xiii
Comments Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 What is new in VSE/ESA 2.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.1 CICS Transaction Server for VSE/ESA 1.1 . . . . . . . . . . . . . . . . . 2
1.1.2 Migration issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 2. Installation and tailoring . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1.1 Planning steps for installation . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1.2 Hardware considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1.3 Software considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.1.4 Additional considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2 Installing VSE/ESA 2.4 and CICS Transaction Server . . . . . . . . . . . . . 15
2.3 Tailoring the CICS Transaction Server . . . . . . . . . . . . . . . . . . . . . 16
2.3.1 Reviewing virtual storage requirements for CICS TS . . . . . . . . . . 16
2.3.2 CICS system definition (CSD) file . . . . . . . . . . . . . . . . . . . . . . 17
2.3.3 Defining system files for a second CICS TS . . . . . . . . . . . . . . . 19
2.3.4 Customizing the DFHSIT table . . . . . . . . . . . . . . . . . . . . . . . 26
2.3.5 Migrating the DFHPCT and DFHPPT tables . . . . . . . . . . . . . . . . 32
2.3.6 Customizing and migrating the DFHFCT table . . . . . . . . . . . . . . 41
2.3.7 Migrating the DFHTCT table . . . . . . . . . . . . . . . . . . . . . . . . . 48
2.3.8 Customizing the DFHDCT, DFHJCT and DFHPLT tables . . . . . . . . 55
2.3.9 Tailoring the CICS start-up jobstream . . . . . . . . . . . . . . . . . . . 61
2.3.10 Autoinstall of resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.3.11 Additional considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Chapter 3. Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.1 VSE/ESA Version 2 Release 4 security . . . . . . . . . . . . . . . . . . . . . 73
3.1.1 VSE/ESA V2R4 security option changes . . . . . . . . . . . . . . . . . . 73
3.1.2 Basic security manager (BSM) . . . . . . . . . . . . . . . . . . . . . . . 75
3.1.3 Security Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
3.1.4 BSM logging and reporting . . . . . . . . . . . . . . . . . . . . . . . . . 81
3.1.5 System Authorization Facility (SAF) . . . . . . . . . . . . . . . . . . . . 82
3.1.6 External security manager (ESM) installation . . . . . . . . . . . . . . 83
3.2 CICS Transaction Server for VSE/ESA R1 security . . . . . . . . . . . . . . 87
3.2.1 CICS TS Sign-on security provided by the BSM . . . . . . . . . . . . . 87
3.2.2 User sign-on and sign-off . . . . . . . . . . . . . . . . . . . . . . . . . . 93
3.2.3 User password checking . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
3.2.4 CICS TS security parameters . . . . . . . . . . . . . . . . . . . . . . . . 95
3.2.5 CICS TS transaction-attach security . . . . . . . . . . . . . . . . . . . . 95
3.2.6 CICS default user ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.2.7 Security for program list table (PLT) programs at startup . . . . . . 109
3.2.8 Resource security checking (not supported by the BSM) . . . . . . 109
3.2.9 Surrogate user security (not supported by the BSM) . . . . . . . . . 110
© Copyright IBM Corp. 1999 iii
3.2.10 Security on intercommunication . . . . . . . . . . . . . . . . . . . . . 110
3.2.11 CICS Report Controller . . . . . . . . . . . . . . . . . . . . . . . . . . 111
3.2.12 Printer security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
3.2.13 Terminal security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
3.3 Security Migration Aid (SMA) . . . . . . . . . . . . . . . . . . . . . . . . . 112
3.3.1 SMA phase one . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
3.3.2 Installation of the Security Migration Aid (SMA) . . . . . . . . . . . . 112
3.3.3 Use of the Security Migration Aid (SMA) . . . . . . . . . . . . . . . . 113
3.3.4 Using the DTSECTX2 REXX procedure . . . . . . . . . . . . . . . . . . 113
3.3.5 SMA phase two . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
3.4 Summary of security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Chapter 4. CICS coexistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
4.1 CSD considerations in a coexistence environment . . . . . . . . . . . . . 118
4.2 Sharing the CSD between CICS TS and CICS/VSE 2.3 . . . . . . . . . . . 120
4.2.1 Shared access from within the same CICS partition . . . . . . . . . 120
4.2.2 Shared access from several CICS regions (partitions) and batch . 121
4.2.3 Obsolete attributes in the CSD in mixed releases of CICS . . . . . . 124
4.3 Placing CICS/VSE 2.3 definitions in a shared CSD . . . . . . . . . . . . . 127
4.4 Separate CSD files in a coexistence environment . . . . . . . . . . . . . 130
4.5 The Interactive Interface in a coexistence environment . . . . . . . . . . 130
4.6 BTAM terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
4.7 Migration options for coexistence . . . . . . . . . . . . . . . . . . . . . . 132
4.8 Placing CICS phases into the SVA in a coexistence environment . . . . 136
4.9 DL/I considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
4.9.1 DL/I SVA considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 139
4.9.2 DL/I installation considerations . . . . . . . . . . . . . . . . . . . . . . 139
4.9.3 LIBDEF considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
4.9.4 DL/I migration considerations . . . . . . . . . . . . . . . . . . . . . . . 140
4.9.5 Batch applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
4.10 DB2 Server for VSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
4.11 Sharing data in a coexistence environment . . . . . . . . . . . . . . . . 145
4.11.1 Shared data table considerations . . . . . . . . . . . . . . . . . . . . 146
4.12 Application programs in a coexistence environment . . . . . . . . . . . 146
Chapter 5. CICS customization . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5.1 System generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5.2 Initialization and termination processing . . . . . . . . . . . . . . . . . . . 147
5.2.1 System initialization overlays . . . . . . . . . . . . . . . . . . . . . . . 148
5.2.2 Program list table (PLT) programs . . . . . . . . . . . . . . . . . . . . 148
5.3 User exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
5.4 Global user exits (GLUEs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
5.4.1 Task-related user exits (TRUEs) . . . . . . . . . . . . . . . . . . . . . 150
5.5 User-replaceable modules (URMs) . . . . . . . . . . . . . . . . . . . . . . 150
5.5.1 VSE/ESA-supplied URMs . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.6 System programmer interfaces . . . . . . . . . . . . . . . . . . . . . . . . 151
5.6.1 System programming macros . . . . . . . . . . . . . . . . . . . . . . . 151
5.6.2 Programmable interface to CEMT . . . . . . . . . . . . . . . . . . . . 152
5.6.3 The System Programming Interface (SPI) . . . . . . . . . . . . . . . . 155
Chapter 6. Performance and tuning . . . . . . . . . . . . . . . . . . . . . . . . 157
6.1 Virtual storage considerations . . . . . . . . . . . . . . . . . . . . . . . . . 157
6.1.1 VSE startup parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 157
6.1.2 Shared Virtual Area (SVA) . . . . . . . . . . . . . . . . . . . . . . . . . 158
6.1.3 CICS partition layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
iv VSE/ESA V2R4
6.1.4 Storage requirements for MXT . . . . . . . . . . . . . . . . . . . . . . 167
6.2 System resource requirements . . . . . . . . . . . . . . . . . . . . . . . . 168
6.2.1 Processor considerations . . . . . . . . . . . . . . . . . . . . . . . . . 168
6.2.2 Real storage considerations . . . . . . . . . . . . . . . . . . . . . . . . 169
6.3 Statistics and monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
6.3.1 Setting up the Data Management Facility . . . . . . . . . . . . . . . . 169
6.3.2 Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
6.3.3 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Chapter 7. CICS application program considerations . . . . . . . . . . . . . . 183
7.1 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
7.2 Migrating macro-level applications . . . . . . . . . . . . . . . . . . . . . . 184
7.2.1 DFHMSCAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
7.2.2 CICS Application Migration Aid (AMA) . . . . . . . . . . . . . . . . . 186
7.3 VSE/ESA compile dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
7.4 CICS Basic Mapping Support (BMS) . . . . . . . . . . . . . . . . . . . . . 188
Chapter 8. CICS problem determination . . . . . . . . . . . . . . . . . . . . . 191
8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
8.2 CICS tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
8.2.1 Trace levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
8.2.2 Control options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.2.3 Default SIT options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.2.4 CETR overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
8.2.5 Using CETR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
8.2.6 Tracing scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
8.2.7 Trace formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
8.3 CICS dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
8.3.1 Processing the CICS dump from a stand-alone tape . . . . . . . . . 209
8.3.2 Program check and abend information . . . . . . . . . . . . . . . . . 213
8.3.3 Default SIT options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
8.4 The Dump Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
8.4.1 Functional overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
8.4.2 Transaction Dump table . . . . . . . . . . . . . . . . . . . . . . . . . . 215
8.4.3 System Dump table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
8.4.4 Dump suppression for ASRA and ASRB abends . . . . . . . . . . . . 216
8.5 Changes to CSFE and CEDF . . . . . . . . . . . . . . . . . . . . . . . . . . 217
8.5.1 Changes to the CSFE DEBUG transaction . . . . . . . . . . . . . . . . 217
8.5.2 CEDF support for remote transactions . . . . . . . . . . . . . . . . . . 217
Appendix A. IBM-supplied CSD groups . . . . . . . . . . . . . . . . . . . . . . 219
Appendix B. CICS TS Statistics output examples . . . . . . . . . . . . . . . . 221
B.1 Sample Statistics Program output . . . . . . . . . . . . . . . . . . . . . . . 221
B.2 Sample unsolicited statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Appendix C. Special Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Appendix D. Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . 231
D.1 International Technical Support Organization Publications . . . . . . . . 231
D.2 Redbooks on CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
D.3 Other Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
How to Get ITSO Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
IBM Redbook Fax Order Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Contents v
List of Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
ITSO Redbook Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
vi VSE/ESA V2R4
Figures
1. CICS organizations of domains . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. CICS address space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3. Sample CSD repro job from CICS/VSE 2.3 . . . . . . . . . . . . . . . . . . 18
4. Sample CSD define and repro job for VSE/ESA 2.4 . . . . . . . . . . . . . 18
5. Sample CSD upgrade job for CICS Transaction Server . . . . . . . . . . 19
6. Copy of VSE groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7. CICS system file definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8. CICS files initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
9. Create CSD GRPLIST VSELST2 . . . . . . . . . . . . . . . . . . . . . . . . . 22
10. Global variables definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
11. Shareoption change for sharing files with DBDCCICS . . . . . . . . . . . 23
12. CICS journal formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
13. Journal archive data set definition . . . . . . . . . . . . . . . . . . . . . . . 24
14. File labels procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
15. Catalog CICS startup and load into RDR queue . . . . . . . . . . . . . . . 25
16. DFHPPT source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
17. DFHPCT source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
18. MIGRATE command to transfer a PCT and a PPT to the CSD . . . . . . 35
19. Output from PCT and PPT MIGRATE command . . . . . . . . . . . . . . . 36
20. ADD command from DFHCSDUP . . . . . . . . . . . . . . . . . . . . . . . . 37
21. RDO ADD command - CEDA transaction . . . . . . . . . . . . . . . . . . . 37
22. Sample of CICS initialization with GRPLIST in the overrides . . . . . . . 37
23. Sample of DFHSIT with GRPLIST parameter . . . . . . . . . . . . . . . . 38
24. RDO INSTALL command - CEDA transaction . . . . . . . . . . . . . . . . 38
25. RDO VIEW PROGRAM - CEDA transaction . . . . . . . . . . . . . . . . . . 39
26. RDO VIEW TRANSACTION - CEDA transaction . . . . . . . . . . . . . . . 40
27. RDO VIEW PROFILE - CEDA transaction . . . . . . . . . . . . . . . . . . . 41
28. DFHFCT source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
29. MIGRATE command to transfer the FCT to the CSD . . . . . . . . . . . . 44
30. Output from FCT MIGRATE command . . . . . . . . . . . . . . . . . . . . . 44
31. DFHFCT source with MIGRATE=COMPLETE . . . . . . . . . . . . . . . . 45
32. RDO VIEW LSRPOOL - CEDA transaction . . . . . . . . . . . . . . . . . . . 46
33. RDO VIEW FILE - CEDA transaction . . . . . . . . . . . . . . . . . . . . . . 47
34. DFHTCT source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
35. MIGRATE command to transfer the TCT to the CSD . . . . . . . . . . . . 50
36. Output from TCT MIGRATE command . . . . . . . . . . . . . . . . . . . . . 51
37. DFHTCT Source with MIGRATE=COMPLETE . . . . . . . . . . . . . . . . 52
38. RDO VIEW TERMINAL - CEDA transaction . . . . . . . . . . . . . . . . . . 53
39. RDO VIEW TYPETERM (part 1) - CEDA transaction . . . . . . . . . . . . . 54
40. RDO VIEW TYPETERM (part 2) - CEDA transaction . . . . . . . . . . . . . 55
41. DFHDCT source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
42. Sample of LIBDEF parameter in CICS startup . . . . . . . . . . . . . . . . 58
43. DFHJCT source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
44. DFH$ARCH sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
45. DFHPLTP2 Source - initialization . . . . . . . . . . . . . . . . . . . . . . . . 60
46. DFHPLTS2 source - shutdown . . . . . . . . . . . . . . . . . . . . . . . . . 60
47. Output from CICS startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
48. Sample of DFHSIT with program autoinstall parameters . . . . . . . . . . 63
49. CSPL queue in the IESZDCT copybook . . . . . . . . . . . . . . . . . . . . 64
50. RDO VIEW PROGRAM(DFHPGAPG) - CEDA transaction . . . . . . . . . . 64
51. RDO VIEW MAPSET(DFHPGAMP) - CEDA transaction . . . . . . . . . . . 65
© Copyright IBM Corp. 1999 vii
52. RDO VIEW PARTITIONSET(DFHPGAPT) - CEDA transaction . . . . . . . . 65
53. RDO VIEW PROGRAM(DFHZCQ) - CEDA transaction . . . . . . . . . . . . 67
54. CADL queue in the IESZDCT copybook . . . . . . . . . . . . . . . . . . . . 68
55. RDO VIEW TRANCLASS - CEDA transaction . . . . . . . . . . . . . . . . . 70
56. Tailor IPL SYS parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
57. Initial Install option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
58. Install SECSERV startup messages . . . . . . . . . . . . . . . . . . . . . . 76
59. Normal SECSERV startup message . . . . . . . . . . . . . . . . . . . . . . 76
60. Normal SHUTDOWN message . . . . . . . . . . . . . . . . . . . . . . . . . 77
61. Security Server commands available . . . . . . . . . . . . . . . . . . . . . 77
62. Messages after STOP issued to the Security Server . . . . . . . . . . . . 78
63. Stopping/Starting the Security Server . . . . . . . . . . . . . . . . . . . . . 78
64. Cancelling the FB partition . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
65. Starting Security Server database caching . . . . . . . . . . . . . . . . . . 79
66. Stopping Security Server database caching . . . . . . . . . . . . . . . . . 80
67. CICS Message File on Sign-on Failure . . . . . . . . . . . . . . . . . . . . 80
68. Security Server - STATUS=ALL - function . . . . . . . . . . . . . . . . . . 81
69. Security Server - CICS TS message log (security violation messages) . 82
70. Security Server - VSE/ESA console log message . . . . . . . . . . . . . . 82
71. Security Server - DTSECTAB example . . . . . . . . . . . . . . . . . . . . 83
72. Security Server - Maintain User Profiles . . . . . . . . . . . . . . . . . . . 89
73. First dialog in II to add/change the user profile screen . . . . . . . . . . 89
74. Second dialog in II to add/change the user profile screen . . . . . . . . 90
75. Third Dialog in II for defining CICS security information . . . . . . . . . . 90
76. Fourth dialog in II for defining CICS security information . . . . . . . . . 91
77. Sample job IESUPDCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
78. Interactive Interface sign-on dialog . . . . . . . . . . . . . . . . . . . . . . 94
79. CESN sign-on screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
80. Password change dialog when signing onto VSE/ESA Interactive
Interface (II) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
81. Inquire Transaction dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
82. Define Transaction dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
83. Add Transaction dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
84. Job created by PROCESS option . . . . . . . . . . . . . . . . . . . . . . . . 98
85. DTSECTXN assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
86. DTSECTXS REXX procedure description . . . . . . . . . . . . . . . . . . 101
87. Sample JCL to execute DTSECTXN procedure . . . . . . . . . . . . . . . 102
88. Output of sample DTSECTXN procedure job . . . . . . . . . . . . . . . . 103
89. Output in IPF table format required for MERGE function . . . . . . . . . 104
90. IPFTABLE REXX procedure description . . . . . . . . . . . . . . . . . . . 105
91. Sample JCL to execute the IPFTABLE procedure . . . . . . . . . . . . . 105
92. Sample output of executing the IPFTABLE REXX procedure . . . . . . 106
93. Merge table dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
94. Initialization of CICS TS with default user ID of CICSUSER . . . . . . . 108
95. Shutdown of CICS TS with default user ID CICSUSER . . . . . . . . . . 108
96. CICS startup failure when default user ID not defined . . . . . . . . . . 108
97. Definition of the new default user ID . . . . . . . . . . . . . . . . . . . . . 109
98. DTSECTX2 REXX procedure . . . . . . . . . . . . . . . . . . . . . . . . . . 114
99. Sample job for executing DTSECTX2 REXX procedure . . . . . . . . . . 115
100. Sample DTSECTXN macro output of REXX procedure DTSECTX2 . . . 115
101. Sample IPF table output of the REXX procedure DTSECTX2 . . . . . . . 115
102. Screen 1 of CEDA ALTER . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
103. Screen 2 of CEDA ALTER . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
104. Screen 3 of CEDA ALTER . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
105. User application screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
viii VSE/ESA V2R4
106. Single CICS to coexistent VSE/ESA 2.3 and CICS TS - option 1 . . . . . 133
107. Single CICS to coexistent VSE/ESA 2.3 and CICS TS - option 2 . . . . . 134
108. Possible ISC/MRO with VSE/ESA 2.3 and CICS TS . . . . . . . . . . . . 135
109. DL/I 1.10 and DL/I VSE 1.11 coexistence . . . . . . . . . . . . . . . . . . 141
110. Example of the DLZACT macro for CICS/VSE 2.3 . . . . . . . . . . . . . 142
111. Example of DLZACT macro under CICS TS . . . . . . . . . . . . . . . . 144
112. CICS/VSE V2R3 CEMT INQUIRE display . . . . . . . . . . . . . . . . . . . 153
113. CICS TS CEMT INQUIRE display . . . . . . . . . . . . . . . . . . . . . . . 153
114. CICS/VSE V2R3 CECI INQUIRE display . . . . . . . . . . . . . . . . . . . 155
115. CICS TS CECI INQUIRE display . . . . . . . . . . . . . . . . . . . . . . . . 156
116. VSE/ESA V2R3 SVA storage layout . . . . . . . . . . . . . . . . . . . . . 159
117. VSE/ESA V2R4 SVA storage layout . . . . . . . . . . . . . . . . . . . . . 159
118. VSE/ESA V2R3 CICSICCF partition layout . . . . . . . . . . . . . . . . . . 160
119. VSE/ESA V2R4 CICSICCF partition layout . . . . . . . . . . . . . . . . . . 161
120. VSE/ESA V2R3 CICSICCF storage layout . . . . . . . . . . . . . . . . . . 162
121. VSE/ESA V2R4 CICSICCF storage layout . . . . . . . . . . . . . . . . . . 163
122. CEMT INQUIRE DSA display . . . . . . . . . . . . . . . . . . . . . . . . . 165
123. CEMT INQUIRE SYS display . . . . . . . . . . . . . . . . . . . . . . . . . . 167
124. DMF VSAM dataset definition . . . . . . . . . . . . . . . . . . . . . . . . . 170
125. DMF initialization jobstream . . . . . . . . . . . . . . . . . . . . . . . . . 171
126. DMF startup table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
127. DMF startup jobstream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
128. DMF startup console messages . . . . . . . . . . . . . . . . . . . . . . . 174
129. Sample STAT transaction display . . . . . . . . . . . . . . . . . . . . . . 177
130. Sample DMF statistics print job . . . . . . . . . . . . . . . . . . . . . . . 180
131. DFHMSCAN sample summary report job . . . . . . . . . . . . . . . . . . 184
132. Sample DFHMSCAN summary report . . . . . . . . . . . . . . . . . . . . 185
133. DFHMSCAN sample detail report job . . . . . . . . . . . . . . . . . . . . 185
134. Sample DFHMSCAN detailed report . . . . . . . . . . . . . . . . . . . . . 186
135. VSE/ESA V2R3 IUI Compile Screen . . . . . . . . . . . . . . . . . . . . . 187
136. VSE/ESA V2R4 IUI Compile Screen . . . . . . . . . . . . . . . . . . . . . 187
137. IUI Generated BMS mapset compile job . . . . . . . . . . . . . . . . . . 189
138. CETR transaction: initial screen . . . . . . . . . . . . . . . . . . . . . . . 194
139. CETR transaction: component trace options screen . . . . . . . . . . . 195
140. CETR transaction: transaction and terminal trace screen - SU option . 196
141. CETR transaction: transaction and terminal trace screen - ST option . 197
142. CETR transaction: transaction and terminal trace screen - SP option . 198
143. Job to format a CICS dump . . . . . . . . . . . . . . . . . . . . . . . . . . 201
144. Sample of a dump summary . . . . . . . . . . . . . . . . . . . . . . . . . 202
145. Sample job to format the trace table . . . . . . . . . . . . . . . . . . . . 202
146. The SUMMARY trace report . . . . . . . . . . . . . . . . . . . . . . . . . 203
147. The corresponding FULL trace report . . . . . . . . . . . . . . . . . . . . 203
148. Using the TRS parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
149. Printing a transaction dump . . . . . . . . . . . . . . . . . . . . . . . . . . 205
150. Printing the auxiliary trace . . . . . . . . . . . . . . . . . . . . . . . . . . 207
151. Console log output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
152. Executing DOSVSDMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
153. SYSLST output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
154. Onloading the dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
155. Offloading the dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
156. Building the CICS dump file . . . . . . . . . . . . . . . . . . . . . . . . . . 212
157. Reloading the dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
158. The Kernel Error Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
159. STAT transaction output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
160. Unsolicited statistics - Autoinstall terminal . . . . . . . . . . . . . . . . . 228
Figures ix
161. Unsolicited file statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
x VSE/ESA V2R4
Tables
1. Some optional programs for VSE/ESA 2.4 . . . . . . . . . . . . . . . . . . 14
2. IBM predefined environments . . . . . . . . . . . . . . . . . . . . . . . . . 15
3. System files used for second CICS TS . . . . . . . . . . . . . . . . . . . . 19
4. Summary of DFHSIT parameter changes . . . . . . . . . . . . . . . . . . . 26
5. Exceptions for CSD equivalents . . . . . . . . . . . . . . . . . . . . . . . . 35
6. Changes to the DFHFCT macro . . . . . . . . . . . . . . . . . . . . . . . . . 43
7. Changes to the DFHDCT, DFHJCT and DFHPLT macros . . . . . . . . . . 56
8. MRO security options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
9. Methods of Defining Resources . . . . . . . . . . . . . . . . . . . . . . . 118
10. Resource Definition Methods . . . . . . . . . . . . . . . . . . . . . . . . . 119
11. Connection definitions for MRO . . . . . . . . . . . . . . . . . . . . . . . 122
12. Session definitions for MRO . . . . . . . . . . . . . . . . . . . . . . . . . 122
13. Mandatory SVA modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
14. CICS phases in the SVA . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
15. TASKDATAKEY and EXECKEY combinations . . . . . . . . . . . . . . . . 149
16. VSE-supplied CICS URMs . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
17. CICS DSA Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
18. VSE/ESA 2.4 Basic CPU requirements . . . . . . . . . . . . . . . . . . . 169
19. DMF operational commands . . . . . . . . . . . . . . . . . . . . . . . . . 175
20. CICS TS Programming Language Support . . . . . . . . . . . . . . . . . 183
21. Trace-related keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
22. Trace formatting utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
23. SELECTION control options . . . . . . . . . . . . . . . . . . . . . . . . . . 206
24. OUTPUT control options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
25. Dump-related keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
26. IBM-supplied RDO groups . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
© Copyright IBM Corp. 1999 xi
xii VSE/ESA V2R4
Preface
This redbook is intended for VSE customers and IBM technical personnel
responsible for planning and migrating to VSE/ESA 2.4 and the CICS Transaction
Server for VSE/ESA 1.1 (CICS TS 1.1).
CICS has significantly changed in this new release. CICS TS 1.1 provides
functions to improve application programming, system programming, system
management, and data security and availability. CICS internal security has been
removed, thus requiring the use use of an external security manager if security
is needed.
This redbook will help you to understand the impact of migrating to CICS TS 1.1.
It will also help you to install and configure the new CICS TS 1.1 by providing
detailed guidance and samples for the changes that you have to perform.
You will understand the new features and their potential, the impact of the
removal of obsolete functions, and the possibilities of CICS TS 1.1 and CICS for
VSE/ESA 2.3 coexistence. You will learn about security and performance issues,
and samples are provided for first-level problem determination through the use
of dumps or the use of trace tools.
The Team That Wrote This Redbook
This redbook was produced by a team of specialists from around the world
working for the International Technical Support Organization Poughkeepsie
Center in the IBM Germany Development location in Böblingen.
Annegret Ackel, from the IBM Development Laboratory Böblingen, was the
project leader.
Susan Davies, NeoMedia, Toronto, Canada.
Andonela Guadagno, IBM Brazil.
John Lawson, IntelliWare Systems Inc., Arlington, Texas, USA.
Keith Miller, IBM Australia.
Cesar Teixeira, IBM Australia.
Thanks to the following people for their invaluable contributions to this project:
Neville Brailsford
IBM Hursley Development
Hans Joachim Ebert
IBM Germany
David Fitzpatrick
IBM Hursley Development
Dr. Wolfgang Kraemer
IBM Germany Development
© Copyright IBM Corp. 1999 xiii
Richard Steimle
IBM Germany Development
Andy Wharmby
IBM Hursley Development
Bob M. Yelavich
Yelavich Consulting, Sparks, Nevada, USA
xiv VSE/ESA V2R4
Comments Welcome
Your comments are important to us!
We want our redbooks to be as helpful as possible. Please send us your
comments about this or other redbooks in one of the following ways:
Fax the evaluation form found in “ITSO Redbook Evaluation” on page 241 to
the fax number shown on the form.
Use the online evaluation form found at http://www.redbooks.ibm.com/
Send your comments in an Internet note to redbook@us.ibm.com
Preface xv
xvi VSE/ESA V2R4
Chapter 1. Introduction
This release of the VSE/ESA operating system introduces the CICS Transaction
Server for VSE/ESA (CICS TS) as the replacement for CICS/VSE 2.3.
In this chapter we discuss the new functions of CICS TS, as well as other
enhancements and changes included in this release.
1.1 What is new in VSE/ESA 2.4
The CICS TS provides new functions that improve application and system
programming, system management, and the reliability and integrity of your CICS
system. Some highlights of the CICS TS are:
1. It is based on a proven restructured code base from CICS for MVS/ESA 4.1.
2. It exploits ESA/390 subsystem storage protection.
3. It provides extensive virtual storage constraint relief with more space below
the 16 MB line for user applications.
4. It provides extended application programming support, including a new
external CICS interface (EXCI) and front-end programming interface (FEPI).
5. It provides system management enhancements including Resource Definition
Online (RDO) for files and Local Shared Resource pools (LSR).
6. It provides shared data tables for improved performance and availability.
7. It provides new security concepts.
8. It provides the ability for CICS/VSE 2.3 and CICS TS to coexist within a single
or multiple VSE image.
Other VSE/ESA 2.4 enhancements and changes include:
1. The new optional programs DL/I VSE 1.11, IXFP/SnapShot for VSE/ESA, and
MQSeries for VSE/ESA.
2. BTAM-ES is now an optional product.
3. The use of Turbo Dispatcher only.
4. The label area automatically resides on virtual disk (address FDF).
5. Changed VSE/ESA system layout.
6. Changed disk layouts.
7. New Access Control for VSE/POWER Spool Entries.
8. Changes to the VSE/POWER files and VSE dump library.
9. PTF application is possible via disk (PTF.FILE on DOSRES).
10. Changed contents of the Extended Base Tape.
11. Changes to the support of programming languages.
© Copyright IBM Corp. 1999 1
1.1.1 CICS Transaction Server for VSE/ESA 1.1
The CICS Transaction Server (CICS TS) is the main focus of migration for the
following reasons:
1. Some functions that were present in previous releases of VSE/ESA have
been removed, meaning that applications which successfully executed under
CICS/VSE 2.3 may not be supported in this release.
2. New functions have been introduced which require decisions to be made as
to when and if these functions will be implemented within a production
environment.
1.1.1.1 CICS Transaction server code
The CICS TS is a new release of CICS for the VSE platform based on the CICS
for MVS/ESA 4.1 product.
The following functions have been removed from CICS TS:
Support for macro-level programs
It was previously announced that CICS/VSE 2.3 would be the last release of
CICS to support macro-level application programs. Macro-level application
programs are, of course, still supported in CICS/VSE 2.3 as part of a
coexistence environment.
Support for BTAM devices
Support for RPG programs
Support for DOS PL/I or C/370 programs
CICS Internal Security
Support for CICS system generation (SYSGEN)
Note:
There is limited support for DOS/VS COBOL and COBOL II programs, provided
they are link-edited against LE/VSE run-time libraries.
The following new functions have been provided with CICS TS:
New domain architecture
Exploitation of ESA/390 subsystem storage protection
Virtual Storage constraint relief (VSCR)
External CICS Interface and Front End Programming Interface
System management and resource definition online
Shared data tables
New security concepts
CICS coexistence
1.1.1.2 New domain architecture
Selected areas of CICS TS code are structured into domains, which improves
code quality and serviceability and extends 31-bit support for almost all CICS TS
code, allowing for better exploitation of Extended Architecture Support.
This new architecture is shown in Figure 1 on page 3, and is followed by a brief
description of each domain.
2 VSE/ESA V2R4
Application Monitoring
Domain (AP) Domain (MN)
CICS Catalog Parameter Manager
Domain (GC/LC) K Domain (PA)
E
R
N
Directory Manager E Program Manager
Domain (DD) L Domain (PG)
L
Dispatcher I Security Manager
Domain (DS) N Domain (XS)
K
A
G
Domain Manager E Statistics
Domain (DM) Domain (ST)
R
O
Dump U Storage Manager
Domain (DU) T Domain (SM)
I
N
E
Kernel S Timer
Domain (KE) Domain (TI)
Loader Trace
Domain (LD) Domain (TR)
Lock Manager Transaction Mgr.
Domain (LM) Domain (XM)
Message User
Domain (ME) Domain (US)
Figure 1. CICS organizations of domains
Application Domain (AP)
Application programs run in the application domain. The CICS management
programs within the AP domain are not restructured, but nevertheless,
communication between the AP domain and the other domains is also
through the new domain interface. Although the AP domain represents
Chapter 1. Introduction 3
unrestructured CICS, there are still many changes (for example, changes to
control blocks).
Catalog Domains
There are two catalog domains: the local catalog domain (LC), and the global
catalog domain (GC). They are used by the other domains to hold
information relating to an orderly restart. They allow CICS to read, write and
purge records on the local and global catalog data sets so that a record of
the status of CICS can be maintained when CICS is not running. The catalog
domains use a common set of programs to provide a domain interface to
VSAM KSDS data sets, and they conceal the underlying VSAM operations
from the calling domains.
The local catalog holds information relevant to a particular CICS system,
including a list of domains.
The global catalog holds information applicable to the whole CICS system.
Therefore, in an XRF system consisting of one active and one alternative
CICS system, there are two local catalogs and one global catalog.
Conversely, in a non-XRF system, there is one local catalog and one global
catalog.
Directory Manager Domain (DD)
The directory manager domain is a service component, providing resource
table lookup services for the other domains (except the application domain,
which uses the table manager program). The resources include:
− Transaction definitions
− Remote transaction definitions
− Transaction classes
− TP names
− User attributes
− Programs
− BMS map sets and partition sets
The table manager program handles:
− Terminals
− Connections
− Sessions
− Modegroups
− Files
− Profiles
− Autoinstall terminal models
Dispatcher Domain (DS)
The dispatcher domain controls attaching, running, and detaching tasks, and
controls the scheduling of VSE tasks.
Domain Manager Domain (DM)
The domain manager domain maintains (through the use of catalog services)
permanent information about the status of individual domains. The domain
manager domain also attaches initialization and termination tasks for the
other domains.
Dump Domain (DU)
The dump domain produces storage dumps and handles the associated data
sets (transaction and system dump data sets) and status in the CICS system.
4 VSE/ESA V2R4
Kernel Domain (KE)
The kernel domain is the main CICS control structure. The kernel tracks the
existence of domains, and is involved in every call from one domain to
another, thereby providing a consistent linkage and recovery environment for
CICS.
Serious system errors can result in the termination of the kernel domain with
a system dump containing diagnostic and problem determination
information.
Loader Domain (LD)
The loader domain is used by the other domains to gain access to
storage-resident copies of nucleus and application programs, maps, and
tables.
Lock Manager Domain (LM)
The lock manager domain provides both locking and associated queueing
facilities for CICS resources. Each resource is associated with a unique lock
name that is used to access locking facilities.
Message Domain (ME)
The message domain acts as a centralized repository for storing and issuing
CICS messages for all parts of restructured CICS. This ensures consistency
of messages issued by the central controlling structures of CICS.
Monitoring Domain (MN)
The monitoring domain controls all monitoring functions within CICS.
Monitoring data is written to Data Management Facility (DMF) data sets, and
can be used for subsequent processing by the monitoring utility program
DFHMNDUP.
Parameter Manager Domain (PA)
The parameter manager controls the process of applying system
initialization parameters to CICS. Initialization takes place using
standardized interfaces that provide an improved method of communicating
between functional areas of CICS.
Program Manager Domain (PG)
The program manager domain provides support for the following areas of
CICS:
− Program control functions such as EXEC CICS LINK, XCTL, LOAD,
RELEASE and RETURN.
− Transaction abend and condition handling functions such as EXEC CICS
ABEND, HANDLE ABEND, HANDLE CONDITION, and HANDLE AID.
− Related functions such as invoking user-replaceable programs, global
user exits, and task-related user exits.
− Autoinstall for programs, map sets, and partition sets.
Security Manager Domain (XS)
The security function (previously provided by the security identification
program DFHACEE) controls:
− Multiple sign-ons by the same user
− Security messages
Chapter 1. Introduction 5
− Warnings when a password is about to expire
− Idle terminal sign-off time-out
It also provides an optional facility for checking user authority to run
transactions and access resources.
The security function is split into two domains, the user domain and the
security domain. The security domain manages the security capabilities of
users, and handles all the interfaces to the external security manager (ESM).
Statistics Domain (ST)
The statistics domain controls the collection of resource statistics for a CICS
system. The statistics domain collects statistics data at a user-specified
interval, at a system quiesce, or at a logical end-of-day, and when requested
by a user. Statistics data is written to Data Management Facility (DMF) data
sets, and can subsequently be used by the statistics offline utility DFHSTUP
to produce formatted reports.
Storage Manager Domain (SM)
The storage manager domain manages virtual storage requests for the CICS
system.
Timer Domain (TI)
The timer domain provides interval timing and alarm clock services for the
other domains. The timer domain also provides date and time facilities and
conversion functions, including the ability to synchronize the CICS local time
with the operating system clock when the system operator has adjusted the
time zone.
Trace Domain (TR)
The trace domain is used by CICS system code and application programs to
record details of the sequence of events occurring in the CICS system. The
basic unit of information created for this purpose is the trace entry . The
trace domain can write entries to:
− Internal trace, which is a wraparound table in main storage in a CICS
address space.
− Auxiliary trace, which is a pair of CICS-controlled SAM data sets used
alternatively.
Transaction Manager Domain (XM)
The transaction manager domain provides transaction-related services to:
− Create tables
− Terminate, purge and inquire about tasks
− Manage transaction definitions and classes
The transaction manager domain also provides a transaction environment
that allows other CICS components to implement transaction-related
services.
User Domain (US)
The user domain restructures the function previously provided by the sign-on
facility.
6 VSE/ESA V2R4
1.1.1.3 Exploitation of ESA/390 subsystem storage protection
CICS TS Release 1 exploits the ESA/390 subsystem storage protection facility in
a way that enables you to prevent CICS code and control blocks from being
overwritten accidentally by your user application programs.
Note that it does not prevent the following:
Deliberate overwriting of CICS code or control blocks. CICS cannot prevent a
user application from obtaining the necessary access key to modify CICS
storage.
Application programs and data being overwritten by another application
program.
Programs can be protected if they are written to reentrant and AMODE (31),
RMODE(ANY) standards, because CICS loads these programs into read-only
storage, if requested by RENTPGM system initialization parameter.
CICS storage protection is optional. However, if you want to use it, you must
have the hardware facility that supports the ESA/390 subsystem storage
protection facility. See CICS Transaction Server for VSE/ESA Release Guide for a
list of machines that are suitable.
1.1.1.4 Virtual Storage constraint relief (VSCR)
CICS TS continues the process of moving as much CICS code and control blocks
as possible above the 16 MB line, leaving more storage available below 16 MB
for user applications that require it. Only CICS code and data areas that have a
dependency on 24-bit addressing are left below the 16 MB line.
This in turn provides considerable virtual storage constraint relief (VSCR).
1.1.1.5 External CICS interface
The external CICS interface (EXCI) is an application programming interface that
allows a non-CICS program (a client program) running in VSE to call a program
(a server program) running in the CICS TS region. A communication area
enables the exchange of information, with the CICS program being invoked as if
it were linked by another CICS program.
1.1.1.6 Front-end programming interface
The front-end programming interface (FEPI) is used as a front end to existing
application programs, allowing you to extend or use these applications
differently without changing the application programs.
FEPI increases the flexibility of your system by:
Allowing existing CICS application programs to be used in different ways, in
different combinations, in different environments, and on different systems,
without changing them
Enabling a new program to access an existing program by acting as if it
were a terminal accessing the existing program
Letting you write programs in a way that adds new function to old programs
Chapter 1. Introduction 7
1.1.1.7 System management and resource definition online (RDO)
The system management improvements in the CICS TS can be summarized as
follows:
Dynamic transaction routing (DTR) program is provided to maintain better
information about the state of routed transactions. The new dynamic
transaction routing mechanism:
− Enables a DTR program to make more intelligent routing decisions, for
example, based on workload goals.
− Makes it possible to detect inter-transaction affinities as they are
created.
You can dynamically define programs, mapsets, and partition sets on their
first usage.
You can define which CICS journals should be automatically archived by
CICS when they are closed for output.
Improved monitoring and statistics in CICS are provided by writing statistical
and monitoring data to Data Management Facility Data Handler data sets,
rather than to CICS journals. This data can be used for subsequent
processing by the new monitoring utility program DFHMNDUP, or by the
statistical utility program DFHSTUP.
You can use RDO to define resources that are associated with CICS files:
− VSAM files
− Remote VSAM files
− Remote DAM files
− VSAM local shared resource (LSR) pools
− Shared data tables
1.1.1.8 Shared data tables (SDT)
Shared Data Tables (SDT) makes the data tables facility introduced in CICS/VSE
2.2 obsolete. By exploiting ESA/390 data spaces and cross-memory services,
using SDT has several important advantages:
They reduce the cost of file sharing by eliminating the overheads of function
shipping for all read and browse requests. The overhead of function
shipping requests will only apply to remote update requests.
They provide support for browse requests between CICS regions in the same
VSE image with good performance, full integrity, recovery and availability.
1.1.1.9 New security concepts
CICS internal security is withdrawn in the CICS TS. You can secure your system
by the following methods:
1. As in the basic form of an external security manager (BSM) provided with
the VSE/ESA 2.4 system package.
The BSM provides sign-on and transaction-attach security only. User IDs and
operator data previously defined in the CICS sign-on table (DFHSNT) must be
defined to the BSM using the VSE/ESA Interactive Interface.
2. Using an external security manager (ESM) conforming to the VSE/ESA
System Authorization Facility (SAF) interface.
8 VSE/ESA V2R4
To provide the necessary security for CICS regions, CICS issues RACROUTE
calls via the System Authorization Facility (SAF) to route authorization
requests to an ESM at appropriate points within CICS transaction processing.
1.1.1.10 CICS coexistence
If you cannot migrate your CICS production systems to the CICS TS completely,
you may need to maintain a CICS/VSE 2.3 system as well as a CICS TS system
for a period of time.
Because some functions have been removed from the CICS TS, (such as support
for macro-level applications, BTAM terminals, RPG programs and so on) you
may need to implement an MRO environment to enable the running of both
systems in a production environment. The ability to run both the CICS TS and
CICS/VSE 2.3 in a coexistent environment is supported by VSE/ESA 2.4.
1.1.1.11 New optional program DL/I VSE 1.11
This new optional program, which is upwardly compatible with DL/I 1.10,
executes under the control of the CICS TS.
Note: DL/I VSE 1.11 will not execute in a CICS/VSE 2.3 or earlier release of
CICS/VSE.
Because VSE/ESA 2.4 supports the coexistence of CICS/VSE 2.3 and the CICS TS,
it is possible to support both DL/I 1.10 and DL/I VSE 1.11 in the same VSE image.
Some of the enhancements included in DL/I VSE 1.11 are:
More than 4 GB for HD databases
Multiple MPS systems
1.1.1.12 BTAM-ES
VSE/ESA 2.4 with the CICS TS does not support BTAM-ES. BTAM-ES is now
supplied as an optional product which will run with CICS/VSE 2.3 only.
1.1.1.13 Turbo Dispatcher
The Turbo Dispatcher is the only dispatcher supported in VSE/ESA 2.4. You can
no longer IPL your system without the Turbo Dispatcher.
1.1.1.14 Label area on virtual disk
VSE/ESA 2.4 automatically loads the label area onto virtual disk FDF, which is a
directly accessed data space.
1.1.1.15 Changed VSE/ESA system layout
During initial installation, you must choose one of the predefined environments
as the basis for your system. If none of the environments meets your needs,
select the most suitable one and tailor it according to your requirements. See
Table 2 on page 15 for the predefined environments.
1.1.1.16 Changed disk layouts
Because of increased sizes of the page data set, VSE/POWER data file, and VSE
dump libraries, the layouts of DOSRES and SYSWK1 have changed.
Refer to VSE/ESA Planning for disk layouts.
If you have allocated user files onto DOSRES or SYSWK1, you should review the
layouts before allocating your datasets to these volumes.
Chapter 1. Introduction 9
1.1.1.17 Access control for VSE/POWER spool entries
VSE/POWER security has been improved by providing spool access protection
for entries in the RDR, LST, PUN, and XMT queues.
This protection can be activated by setting the IPL SYS statement SEC=YES and
SECAC=SYS in the SET statement in the VSE/POWER startup procedure.
The SECAC operand in JOB, LST and PUN statements can be used to provide
further protection for spool access.
This support is available with the BSM as well as with an ESM.
1.1.1.18 Size increase of VSE/POWER data file/VSE dump library
The number of extents of the VSE/POWER data file has been increased to 16,
and the shipped size of the VSE dump library has more than doubled. The DBLK
default size VSE/POWER files have been optimized according to DASD type.
As soon as the ALLOC specification for the VSE/POWER private partition
stretches beyond the 16 MB line, the storage copy of the VSE/POWER queue file
will reside partly or totally in the 31-bit partition GETVIS area.
This relief is provided for a growing consumption of 24-bit GETVIS space due to:
Expanding queue record size
Controlling an increased number of queue entries
Increased input/output spooling in general
Generating an increased Data Block (DBLK) I/O area size, in case the
shipped DBLK default is insufficient
1.1.1.19 PTF application from disk
With VSE/ESA 2.4, you have the ability to apply service to your system from a
VSAM-managed SAM file on disk. If you use the Service Update Facility, the disk
file can be created from the service downloaded into the VSE library
PRIMARY.SUF.
1.1.1.20 Contents of extended base tape
The extended base tape for VSE/ESA 2.4 includes the following base products:
CICS/VSE 2.3
LANRES/VSE
VSE/ESA Distributed Workstation Feature
VisualLift Run-Time Environment
These programs are shipped on the extended base tape and are therefore not
installed automatically on your system during initial installation.
Although part of the base, you must treat them as optional products and you can
install them using the dialogs of the Interactive Interface.
10 VSE/ESA V2R4
1.1.1.21 Support for programming languages
CICS TS 1.1 supports only those applications that use the CICS command-level
application programming interface, compiled with the following compilers:
COBOL for VSE/ESA
C for VSE/ESA
PL/I for VSE/ESA
High-level assembler
Programs compiled with the VS COBOL II and DOS/VS COBOL compilers are
supported if link-edited against the LE/VSE run-time library. CICS TS 1.1 does
not support C/370 or DOS PL/I compiled programs as well as DOS/VS RPG II.
See Chapter 4, “CICS coexistence” on page 117 for details of executing these
programs in a CICS environment.
VS COBOL II, DOS/VS COBOL, C/370, and DOS PL/I are no longer available as
VSE/ESA optional products.
1.1.2 Migration issues
The main migration item for VSE/ESA 2.4 is the switch from CICS/VSE to the
CICS Transaction Server.
The complexity and variety of possible CICS configurations means that there is
no single list of instructions for migration planning and implementation.
Migration to the CICS TS requires careful planning and change management. To
achieve this, you must:
Understand the practical issues and detailed product changes intrinsic in
migrating to the CICS TS.
Plan a satisfactory conversion strategy.
Plan the required actions to achieve that strategy.
Accurately estimate the resources and time required to achieve that
strategy.
You can adopt good change management practices by:
Making minimum changes simultaneously.
Testing all changes before placing them into production, and having a
fallback plan.
Assessing the impact of the change before introducing it into production.
Scheduling the change so as to have minimal impact on users of the system.
Generally, you should plan a phased conversion and cut-over. For example, you
could have the following phases as part of your strategy:
Plan your migration.
Position your system on CICS/VSE 2.3.
Install, test and run your CICS in a coexistence environment.
Cut over to your new system in stages.
Chapter 1. Introduction 11
1.1.2.1 Migration planning summary
How you migrate your system depends on the current level of your system. The
main points to remember are:
Make sure you have the correct levels of software for the functions you wish
to use.
Make sure you have the required hardware for the functions you wish to use,
If you are migrating from a previous VSE release that does not support
CICS/VSE 2.3, then you should migrate to a VSE/ESA release that includes
CICS/VSE 2.3.
You cannot run an XRF system with an active CICS system and an
alternative CICS system at different release levels of CICS.
Ensure that all third-party products you use are capable of running under
VSE/ESA 2.4 and the CICS TS. If they are not, you must obtain replacement
products.
Detailed information about migration considerations is available in CICS
Transaction Server for VSE/ESA Migration Guide .
12 VSE/ESA V2R4
Chapter 2. Installation and tailoring
In this chapter we describe the necessary steps how to install VSE/ESA 2.4 with
the CICS Transaction Server and how to perform the migration and tailoring of
CICS tables.
2.1 Planning
The planning phase of a system migration from VSE/ESA 2.3.x to VSE/ESA 2.4 is
the most important part of the migration to ensure a successful migration.
The main migration item is switching from CICS/VSE to the CICS Transaction
Server that is shipped as part of the VSE/ESA 2.4.
2.1.1 Planning steps for installation
Define the optional products that you need to install.
Define your hardware configuration.
Determine the predefined environment that best fits your needs.
Determine whether you want to run your system with security active.
2.1.2 Hardware considerations
In this section, we do not cover all hardware items, only the main changes.
2.1.2.1 Processors
All VSE/ESA 2.4 interfaces provided for the CICS Transaction Server are only
available with the Turbo Dispatcher , which runs on uni- or multiprocessors. The
standard dispatcher can no longer be IPLed.
If you currently use the standard dispatcher, there may be additional CPU
requirements when using the Turbo Dispatcher. Make sure, before migration,
that you review your current processor utilization CPU time requirements to run
VSE/ESA 2.4. Only ESA/390 processors are supported.
If you want to use storage protection facilities, you need a processor that
supports the ESA/390 subsystem storage protection override facility.
2.1.2.2 DASD
For initial installation, if you select predefined environment B, the page data set
has expanded to support a VSIZE of 250 MB compared to 180 MB of VSE/ESA
2.3. To avoid overlaps or errors, especially with the last files in disk layouts, you
should review the DASD layouts for DOSRES and SYSWK1.
You will need additional library space in PRD2 if you install CICS/VSE 2.3 and
DL/I DOS/VS 1.10 in a co-existence environment.
© Copyright IBM Corp. 1999 13
2.1.3 Software considerations
Fast Service Upgrade (FSU) to VSE/ESA 2.4 from prior releases is not possible.
A full base and optional product installation is required.
You may have to apply additional program temporary fixes (PTFs) for the system
to run successfully. You should contact your IBM Support Center to obtain
additional Preventive Service Planning (PSP) information that you should know.
The migration path to the new CICS Transaction Server is via CICS/VSE 2.3. You
should be on a release of VSE/ESA that supports CICS/VSE 2.3, prior to
migrating to VSE/ESA 2.4, particularly if you need to support an environment of
both CICS/VSE 2.3, and CICS TS.
The CICS/VSE 2.3 product is shipped on the extended base tape and therefore is
not installed during the initial installation. You must treat CICS/VSE 2.3 as an
optional program and use the Install Optional Programs dialog of the Interactive
Interface for installation.
Note the following:
LE/VSE is shipped as part of the VSE/ESA base.
OSA/SF for VSE/ESA is included in the VSE/ESA base tape.
Online applications written in DOS/VS RPG II are supported in CICS/VSE 2.3,
but are not supported in the CICS TS.
Table 1 lists some changes for the VSE/ESA optional programs. Refer to
VSE/ESA Planning for a complete list of optional products.
Table 1. Some optional programs for VSE/ESA 2.4
Optional Program number Version release Sublibrary
programs
BTAM-ES 1 5746-RC5 1.1.0 PRD1.BASE
DL/I DOS/VS 1 5746-XX1 1.10.0 PRD2.DLI1A0
DL/I VSE 2 5746-XX1 1.11.0 PRD2.DBASE
DB2 Server for 5648-158 6.1.0 PRD2.DB2610
VSE & VM 3 PRD2.RCV610
PRD2.ASN610
PRD2.DB261S02
PRD2.DB261S03
PRD2.DB261S04
MQSeries for 5686-A06 2.1.0 PRD2.PROD
VSE/ESA 3
Notes:
1. Can run only with CICS/VSE 2.3
2. Can run only with CICS Transaction Server for VSE/ESA
3. Enhanced version
VS COBOL II, DOS/VS COBOL, C/370 and DOS PL/I are no longer available as
VSE/ESA optional products:
CICS Transaction Server does not support C application programs compiled
using the C/370 compiler. All such application programs must be recompiled
14 VSE/ESA V2R4
using the C for VSE/ESA compiler, and link-edited using Language
Environment for VSE (LE/VSE).
CICS Transaction Server does not support PL/I application programs
compiled using the DOS PL/I compiler. All such application programs must
be recompiled using the PL/I for VSE/ESA compiler, and link-edited with
LE/VSE.
CICS command-level application programs compiled using the VS/COBOL II
and DOS/VS COBOL compilers should be link-edited with LE/VSE to obtain
limited support.
If you have any CICS applications written in VS/COBOL II, you may need to
review your COBOL run-time options.
2.1.4 Additional considerations
Ensure that all your third-party/vendor software products are supported with
VSE/ESA 2.4 and CICS Transaction Server for VSE/ESA. You should contact your
vendor for information regarding required levels for VSE/ESA 2.4 and CICS TS.
You cannot run an XRF environment with an active CICS system and an alternate
CICS system at different release levels of CICS. Also, all CICS applications with
GDDM must be relinked with GDDM 3.2 stubs to work properly on CICS
Transaction Server for VSE/ESA.
2.2 Installing VSE/ESA 2.4 and CICS Transaction Server
VSE/ESA is a pregenerated system that is easy to install. The CICS Transaction
Server is installed as part of the base installation process. VSE/ESA is shipped
on three base tapes, where the third tape is the extended base tape.
The install process is essentially the same as for VSE/ESA 2.3. The main
difference is the activation of the Basic Security Manager (BSM) during the
install process.
You may choose between an automatic installation and a manual installation. We
recommend the automatic installation of environment B. Refer to Table 2 for a
list of available environments.
Table 2. IBM predefined environments
Environment A B C
Number of address space 24 44 12
VSIZE 100 MB 250 MB 100 MB
Maximum number of dynamic partitions 12 32 -
PASIZE 30 MB 50 MB 30 MB
Maximum size of data space (DSPACE) 8 MB 20 MB 8 MB
Install with the IPL SYS SEC=YES command to set up support for BSM. You will
find details in Chapter 3, “Security” on page 73.
Chapter 2. Installation and tailoring 15
2.3 Tailoring the CICS Transaction Server
In this section we discuss the following main CICS Transaction Server tailoring
tasks:
Reviewing virtual storage requirements to run CICS TS.
Defining the system files for CICS TS.
Customizing the DFHSIT table.
Migrating the DFHPCT and DFHPPT tables.
Customizing and migrating the DFHFCT table.
Migrating the DFHTCT table.
Customizing the DFHDCT, DFHJCT and DFHPLT tables.
Tailoring the CICS start-up jobstream.
Autoinstall of CICS resources.
Additional considerations.
2.3.1 Reviewing virtual storage requirements for CICS TS
The storage allocations defined for the CICS Transaction Server in environment
B are 50 MB for F2 for CICSICCF and 50 MB for F8 for a second CICS. Figure 2
on page 17 illustrates the layout for the CICS Transaction Server address space.
See Chapter 6, “Performance and tuning” on page 157 for additional discussion
on CICS virtual storage requirements.
16 VSE/ESA V2R4
2 GB
maximum
↑
SVA 31-bit
..............................
↑ ////////////////////////
......................
↑ ↑
DFHSIP31
.
.
.....
↑
EDSALIM
= Extended DSAs
25 MB (ECDSA,ERDSA,ESDSA,EUDSA)
GETVIS ↓
= .....
49152K .
ALLOC .
=
50 MB
Partition Getvis 31-bit
PASIZE
= 16 MB
50 MB
Partition Getvis 24-bit
.....
↑
DSALIM CICS DSAs
= (CDSA,RDSA,SDSA,UDSA)
5 MB
↓
.....
.
↓ .
.............
Exec SIZE = DFHSIP (4K)
↓ ↓
..............................
↑
SVA-24-bit
(including CICS code)
Shared Area
24 bits
SUPERVISOR
↓
.........
0
Figure 2. CICS address space
The minimum ALLOC required is 30 MB.
Increasing partition sizes may also mean that you have to increase the VSIZE to
meet your total system requirements.
2.3.2 CICS system definition (CSD) file
CICS Transaction Server is the first version on the VSE/ESA platform where the
use of a CSD file for resource definitions is mandatory . This makes the CSD file a
critical resource of your system. You should ensure that this file is backed up on
a regular basis.
The DFHCSD dataset is defined during the installation of VSE/ESA.
Chapter 2. Installation and tailoring 17
If you use a CSD file with CICS for VSE/ESA 2.3, you do not need to recreate
your CSD file to migrate to CICS Transaction Server. To migrate the CSD, do the
following:
1. Back up the old CSD prior to the migration. The sample JCL is as shown in
Figure 3:
// JOB REPROCSD
// DLBL COPYIN,'CICS.CSD',,VSAM,CAT=VSESPUC
// TLBL COPYOUT,'CSD.REPRO',,123456
// ASSGN SYS005,181
// EXEC IDCAMS,SIZE=AUTO
REPRO INFILE (COPYIN) -
OUTFILE (COPYOUT -
ENVIRONMENT (BLOCKSIZE (508) -
RECORDFORMAT (VARUNB) -
STDLABEL -
PRIMEDATADEVICE (2400) REW)) -
NOREUSE
/*
Figure 3. Sample CSD repro job from CICS/VSE 2.3
2. Restore the old CSD on the new system.
Define the CSD to VSE/ESA 2.4 and restore the backup copy.
You should take the precaution of making a backup copy of the supplied
CSD, created during the VSE/ESA 2.4 install, before you run this job; refer to
Figure 4.
// JOB CSDTS
// TLBL COPYIN,'CSD.REPRO',,123456
// ASSGN SYS004,181
// DLBL COPYOUT,'CICS.USER.CSD',,VSAM,CAT=VSESPUC
// EXEC IDCAMS,SIZE=AUTO
DEFINE CLUSTER(NAME(CICS.USER.CSD) -
INDEXED -
RECORDSIZE (120 500) -
RECORDS (4000 1000) -
KEYS (22 0) -
CISZ(4096) -
FREESPACE (50 10) -
SHR(2) -
VOL(DOSRES)) -
DATA(NAME(CICS.USER.CSD.@D@)) -
INDEX (NAME (CICS.USER.CSD.@I@)) -
CATALOG(VSESP.USER.CATALOG)
REPRO INFILE (COPYIN -
ENVIRONMENT (BLOCKSIZE (508) -
RECORDFORMAT (VARUNB) -
STDLABEL -
PRIMEDATADEVICE (2400) REW)) -
OUTFILE (COPYOUT) -
NOREUSE REPLACE
/*
Figure 4. Sample CSD define and repro job for VSE/ESA 2.4
3. Upgrade your CSD to include CICS resource definitions new in the CICS
Transaction Server.
We used the job stream shown in Figure 5 on page 19:
18 VSE/ESA V2R4
// JOB UPGRADE
// LIBDEF PHASE,SEARCH=PRD1.BASE
// DLBL DFHCSD,'CICS.USER.CSD',,VSAM,CAT=VSESPUC
// EXEC DFHCSDUP,SIZE=DFHCSDUP
UPGRADE
UPGRADE USING(DFHCURCF) . .
LIST ALL OBJECTS
/*
Figure 5. Sample CSD upgrade job for CICS Transaction Server
. .If you have installed the Report Controller optional feature, you must
specify the UPGRADE command shown to include the required Report
Controller resource definitions.
4. Copy the VSE groups from the supplied CSD to your CSD, as shown in
Figure 6:
// JOB COPY
// LIBDEF PHASE,SEARCH=PRD1.BASE
// DLBL FROMCSD,'CICS.CSD',,VSAM,CAT=VSESPUC
// DLBL DFHCSD,'CICS.USER.CSD',,VSAM,CAT=VSESPUC
// EXEC DFHCSDUP,SIZE=DFHCSDUP
COPY GROUP(VSESPG) TO(VSESPG) FROMCSD(FROMCSD) REPLACE
COPY GROUP(VSETYPE) TO(VSETYPE) FROMCSD(FROMCSD) REPLACE
COPY GROUP(VSEAI62) TO(VSEAI62) FROMCSD(FROMCSD) REPLACE
COPY GROUP(VSETERM) TO(VSETERM) FROMCSD(FROMCSD) REPLACE
COPY GROUP(VSETERM1) TO(VSETERM1) FROMCSD(FROMCSD) REPLACE
LIST ALL OBJECTS
/*
Figure 6. Copy of VSE groups
If you are using modified versions of some IBM-supplied resource definitions:
1. Replace your private version of the resource with the original one supplied
by IBM.
2. Modify the IBM-supplied resource to meet your requirements.
You must review all the CSD groups lists that you use for CICS startups and
ensure that obsolete groups are removed, and that groups supporting new
functions are added to your lists.
Using resource definitions that have not been upgraded can have unpredictable
results.
2.3.3 Defining system files for a second CICS TS
The system files we used for our second CICS TS are listed in Table 3.
Table 3 (Page 1 of 2). System files used for second CICS TS
File name File identifier File type
DFHAUXT CICS2.AUXTRACE 1 SAM
DFHCSD CICS.CSD 2 VSAM KSDS
DFHDMFA CICS.DBDCCICS.DFHDMFA 2 . . VSAM ESDS
DFHDMFB CICS.DBDCCICS.DFHDMFB 2 . . VSAM ESDS
DFHDMPA CICS2.DUMPA 1 SAM
DFHDMPB CICS2.DUMPB 1 SAM
Chapter 2. Installation and tailoring 19
Table 3 (Page 2 of 2). System files used for second CICS TS
File name File identifier File type
DFHGCD CICS2.GCD . . VSAM KSDS
DFHLCD CICS2.LCD . . VSAM KSDS
DFHNTRA CICS2.TD.INTRA VSAM ESDS
DFHRSD CICS2.RSD VSAM KSDS
DFHTEMP CICS2.DFHTEMP VSAM ESDS
IESCNTL VSE.CONTROL.FILE 2 VSAM KSDS
IESPRB CICS2.ONLINE.PROB.DET.FILE VSAM KSDS
IESROUT VSE.MESSAGE.ROUTING.FILE 2 VSAM KSDS
IESTRFL VSE.TEXT.REPSTORY.FILE 2 VSAM KSDS
Approx. amount of disk space required 3
Number of FBA blocks Number of tracks (full cylinders) Approx.
number
IBM 3380 IBM 3390 IBM 9345
of
megabytes
(MB)
VSAM space 24.000 390 360 435 12
Journal files 4 12.032 240 240 240 6
Notes:
1. The file is created dynamically when required.
2. The file can be shared with DBDCCICS (the primary CICS TS).
3. Without files shared.
4. The size of a system or user journal file is workload-dependent.
Two separate VSAM data sets are used for cataloging information about the
running CICS system. CICS no longer uses part of the restart data set (DFHRSD)
as in previous versions.
The file names are DFHLCD for the local catalog and DFHGCD for the global
catalog. The catalogs contain system information for use in WARM and
EMERgency restarts, including takeovers by an alternate CICS partition if running
with XRF. The global catalog can also contain information that is used in a
COLD start. If you delete and redefine a catalog for any reason, you must delete
and redefine them both.
DFHRSD now refers to a data set that is used only for system log processing
during EMERgency restart.
The DFHDMF data sets are used for statistics and monitoring data. A minimum
of two data sets should be available for use by DMF. See Chapter 6,
“Performance and tuning” on page 157 for additional information.
2.3.3.1 System file definitions and initialization
We defined the VSAM files for our second CICS partition using the skeleton
SKPREPC2 in ICCF library 59.
The following figures show the jobs we used.
20 VSE/ESA V2R4
// EXEC IDCAMS,SIZE=AUTO
/* define the Global Catalog Data Set
DEFINE CLUSTER(NAME(CICS2.GCD) -
RECORDSIZE (4089 4089) -
RECORDS (2000 200) -
KEYS (28 0) -
REUSE -
INDEXED -
FREESPACE (10 10) -
SHR(2) -
CISZ(8192) -
VOL(SYSWK1 DOSRES)) -
DATA(NAME(CICS2.GCD.@D@)) -
INDEX (NAME (CICS2.GCD.@I@)) -
CATALOG(VSESP.USER.CATALOG)
/* define the Local Catalog Data Set
DEFINE CLUSTER(NAME(CICS2.LCD) -
INDEXED -
RECORDSIZE (45 124) -
RECORDS (3000 200) -
KEYS (28 0) -
REUSE -
FREESPACE (10 10) -
SHR(2) -
CISZ(2048) -
VOL(SYSWK1 DOSRES)) -
DATA(NAME(CICS2.LCD.@D@)) -
INDEX (NAME (CICS2.LCD.@I@)) -
CATALOG(VSESP.USER.CATALOG)
DEF CLUSTER(NAME(CICS2.ONLINE.PROB.DET.FILE) -
FILE(IESPRB) -
VOL(SYSWK1 DOSRES) -
RECORDS (300 100) -
RECORDSIZE (4000 4089) -
INDEXED -
KEYS(2 0) -
SHR(2)) -
DATA (NAME (CICS2.ONLINE.PROB.DET.FILE.@D@) CISZ(4096)) -
INDEX (NAME (CICS2.ONLINE.PROB.DET.FILE.@I@) CISZ(512)) -
CATALOG(VSESP.USER.CATALOG)
/* */
DEF CLUSTER(NAME(CICS2.DFHTEMP) -
VOL(SYSWK1 DOSRES) -
RECORDS (100) -
RECORDSIZE (4089 4089) -
CISZ (4096) -
NONINDEXED -
SHR(2)) -
DATA(NAME(CICS2.DFHTEMP.ESDS)) -
CATALOG(VSESP.USER.CATALOG)
/* */
DEF CLUSTER(NAME(CICS2.TD.INTRA) -
VOL(SYSWK1 DOSRES) -
RECORDS (100) -
RECORDSIZE (4089 4089) -
CISZ (4096) -
NONINDEXED -
SHR(2)) -
DATA(NAME(CICS2.TD.INTRA.ESDS)) -
CATALOG(VSESP.USER.CATALOG)
/* */
DEF CLUSTER(NAME(CICS2.RSD) -
INDEXED -
RECORDSIZE (2000 2000) -
RECORDS (250 100) -
KEYS (22 0) -
FREESPACE (20 20) -
SHR(2) -
VOL(SYSWK1 DOSRES)) -
DATA(NAME(CICS2.RSD.@D@)) -
INDEX (NAME (CICS2.RSD.@I@)) -
CATALOG(VSESP.USER.CATALOG)
/* */
Figure 7. CICS system file definitions
Chapter 2. Installation and tailoring 21
Initialize the Restart Data Set, Global Catalog and Local Catalog files; see
Figure 8:
// DLBL DFHRSD,'CICS2.RSD',0,VSAM,CAT=VSESPUC
// DLBL DFHGCD,'CICS2.GCD',0,VSAM, X
CAT=VSESPUC
// EXEC IDCAMS,SIZE=AUTO
REPRO INFILE -
(SYSIPT -
ENVIRONMENT -
(RECORDFORMAT (FIXUNB) -
BLOCKSIZE(80) -
RECORDSIZE (80))) -
OUTFILE (DFHRSD)
ACTL 0001
/*
// EXEC IDCAMS,SIZE=AUTO INIT GCD FILE
REPRO INFILE -
(SYSIPT -
ENVIRONMENT -
(RECORDFORMAT(FIXUNB) -
BLOCKSIZE(80) -
RECORDSIZE(80))) -
OUTFILE(DFHGCD)
ACTL 0002
/*
// DLBL DFHLCD,'CICS2.LCD',0,VSAM, X
CAT=VSESPUC
// LIBDEF *,SEARCH=(PRD2.CONFIG,PRD2.SCEEBASE,PRD1.BASE)
// EXEC DFHCCUTL,SIZE=300K INITIALIZE CICS CATALOG
/*
Figure 8. CICS files initialization
Create the system list that you name in the GRPLIST parameter by adding all
resource definitions required by CICS; see Figure 9:
// LIBDEF *,SEARCH=(PRD2.CONFIG,PRD1.BASE,PRD2.SCEEBASE)
// EXEC DFHCSDUP,SIZE=DHCSDUP INIT AND LOAD CICS
APPEND LIST(DFHLIST) TO(VSELST2)
ADD GROUP(VSETYPE) LIST(VSELST2)
ADD GROUP(DFHRCF) LIST(VSELST2)
ADD GROUP(VSETERM) LIST(VSELST2)
ADD GROUP(VSETERM1) LIST(VSELST2)
ADD GROUP(VSEAI62) LIST(VSELST2)
ADD GROUP(VSESPG) LIST(VSELST2)
ADD GROUP(CEE) LIST(VSELST2)
LIST ALL
/*
Figure 9. Create CSD GRPLIST VSELST2
Initialize the global variables definition in the CPUVARx procedure; see
Figure 10:
// SETPARM XNCPU=' '
// EXEC PROC=$COMVAR,XNCPU
// EXEC DTRSETP,PARM='CPUVAR&XNCPU'
SET XPARTC2='F8'
SET XUSEF8='CI'
/*
Figure 10. Global variables definition
22 VSE/ESA V2R4
Change the file's shareoption from 2 to 4, so these files can be accessed by
multiple CICS partitions; see Figure 11:
.
* PLEASE CLOSE FILES IESROUT AND INWFILE ON PRODUCTION CICS
* AND ALSO ON ALL OTHER CICS PARTITIONS USING THE FILES.
* A RETURN CODE OF 4 IS OK. IF THE INWFILE DOES NOT EXIST, RETURN
* CODE WILL BE 12.
// PAUSE
// EXEC IDCAMS
ALTER VSE.MESSAGE.ROUTING.FILE.@I@ -
SHAREOPTIONS(4) -
CATALOG(VSESP.USER.CATALOG)
/**/
ALTER VSE.MESSAGE.ROUTING.FILE.@D@ -
SHAREOPTIONS(4) -
CATALOG(VSESP.USER.CATALOG)
/**/
ALTER PC.HOST.TRANSFER.FILE.INDEX -
SHAREOPTIONS(4) -
CATALOG(VSESP.USER.CATALOG)
/**/
ALTER PC.HOST.TRANSFER.FILE.DATA -
SHAREOPTIONS(4) -
CATALOG(VSESP.USER.CATALOG)
/*
Figure 11. Shareoption change for sharing files with DBDCCICS
Format CICS journal data sets (ICCF skeleton SKJOURN in ICCF library 59); see
Figure 12:
/. D3390
* -------------------------------------------------------------------*
* FORMAT SYSTEM JOURNAL: DFHJ01A *
* -------------------------------------------------------------------*
// DLBL JOURNAL,'CICS.SYSTEM.LOG.A',0,SD
// EXTENT SYS019,DOSRES,1,0,5655,60
// ASSGN SYS019,DISK,VOL=DOSRES,SHR
// EXEC DFHJCJFP,SIZE=DFHJCJFP
/*
* -------------------------------------------------------------------*
* FORMAT SYSTEM JOURNAL: DFHJ01B *
* -------------------------------------------------------------------*
// DLBL JOURNAL,'CICS.SYSTEM.LOG.B',0,SD
// EXTENT SYS019,DOSRES,1,0,5715,60
// ASSGN SYS019,DISK,VOL=DOSRES,SHR
// EXEC DFHJCJFP,SIZE=DFHJCJFP
/*
* -------------------------------------------------------------------*
* FORMAT USER JOURNAL: DFHJ02A *
* -------------------------------------------------------------------*
// DLBL JOURNAL,'CICS.USER.JOURNAL.A',0,SD
// EXTENT SYS019,DOSRES,1,0,5775,60
// ASSGN SYS019,DISK,VOL=DOSRES,SHR
// EXEC DFHJCJFP,SIZE=DFHJCJFP
/*
* -------------------------------------------------------------------*
* FORMAT USER JOURNAL: DFHJ02B *
* -------------------------------------------------------------------*
// DLBL JOURNAL,'CICS.USER.JOURNAL.B',0,SD
// EXTENT SYS019,DOSRES,1,0,5835,60
// ASSGN SYS019,DISK,VOL=DOSRES,SHR
// EXEC DFHJCJFP,SIZE=DFHJCJFP
/*
Figure 12. CICS journal formatting
Chapter 2. Installation and tailoring 23
If you decide to use the new CICS automatic journal archiving facility to archive
CICS journals, you need to define the new DFHJACD journal archive control data
set.
You do not have to initialize the JACD because CICS initializes it for you. For
each JCT entry defined with JOUROPT=AUTOARCH, records are added or
updated.
The sample job to define a journal archive data set is shown is Figure 13:
/* DEFINE THE JOURNAL ARCHIVE DATA SET
// EXEC IDCAMS,SIZE=AUTO
DEFINE CLUSTER -
(NAME(CICS2.PRODCICS.DFHJACD) -
NUMBERED -
RECORDS(198) -
RECORDSIZE(505 505) -
CONTROLINTERVALSIZE(512) -
SHAREOPTIONS(4) -
VOLUMES(DOSRES SYSWK1)) -
DATA -
(NAME(CICS2.PRODCICS.DFHJACD.DATA) ) -
CATALOG(VSESP.USER.CATALOG)
/*
Figure 13. Journal archive data set definition
The catalog procedure with all non-shared CICS file labels is shown in Figure 14:
CATALOG DTRCICS2.PROC D=YES R=YES EOD=/+
// ASSGN SYS018,DISK,VOL=SYSWK1,SHR
// DLBL DFHDMPA,'CICS2.DUMPA',0,VSAM, X
CAT=VSESPUC,RECSIZE=7200, X
DISP=(NEW,KEEP),RECORDS=(300,0)
// DLBL DFHDMPB,'CICS2.DUMPB',0,VSAM, X
CAT=VSESPUC,RECSIZE=7200, X
DISP=(NEW,KEEP),RECORDS=(100,0)
// DLBL DFHAUXT,'CICS2.AUXTRACE',0,VSAM, X
CAT=VSESPUC,RECSIZE=4096, X
DISP=(NEW,KEEP),RECORDS=(400,0)
// DLBL DFHTEMP,'CICS2.DFHTEMP',0,VSAM, X
CAT=VSESPUC
// DLBL DFHNTRA,'CICS2.TD.INTRA',0,VSAM, X
CAT=VSESPUC
// DLBL DFHRSD,'CICS2.RSD',0,VSAM, X
CAT=VSESPUC
// DLBL DFHLCD,'CICS2.LCD',0,VSAM, X
CAT=VSESPUC
// DLBL DFHGCD,'CICS2.GCD',0,VSAM, X
CAT=VSESPUC
// DLBL IESPRB,'CICS2.ONLINE.PROB.DET.FILE',,VSAM, X
CAT=VSESPUC
// DLBL DFHJ01A,'CICS.SYSTEM.LOG.A',0,SD
// EXTENT SYS019,DOSRES,1,0,5655,60
// DLBL DFHJ01B,'CICS.SYSTEM.LOG.B',0,SD
// EXTENT SYS019,DOSRES,1,0,5715,60
// DLBL DFHJ02A,'CICS.USER.JOURNAL.A',0,SD
// EXTENT SYS019,DOSRES,1,0,5775,60
// DLBL DFHJ02B,'CICS.USER.JOURNAL.B',0,SD
// EXTENT SYS019,DOSRES,1,0,5835,60
// DLBL DFHJACD,'CICS2.PRODCICS.DFHJACD',,VSAM, X
CAT=VSESPUC
/+
Figure 14. File labels procedure
Modify and catalog the CICS startup job and load it in the POWER reader queue,
as shown in Figure 15 on page 25:
24 VSE/ESA V2R4
* $$ JOB JNM=CATCICS2,DISP=D,CLASS=0
* $$ LST DISP=D,CLASS=Z
// JOB CATCICS2 CATALOG CICS2 AND LDCICS2
// EXEC LIBR,PARM='MSHP'
ACCESS S=IJSYSRS.SYSLIB
CATALOG CICS2.Z REPLACE=YES
$$$$ JOB JNM=CICS2,DISP=L,CLASS=8,EOJMSG=YES
$$$$ LST CLASS=Z,DISP=D
// JOB CICS2 STARTUP OF SECOND CICS WITHOUT ICCF
// OPTION SADUMP=5,SYSDUMPC
// LIBDEF *,SEARCH=(PRD2.CONFIG,PRD2.ARCHJCL,PRD1.BASED,PRD1.BASE, X
PRD2.PROD,PRD2.SCEECICD,PRD2.SCEECICS,PRD2.SCEEBASD, X
PRD2.SCEEBASE,PRD2.DBASE),PERM
// LIBDEF DUMP,CATALOG=SYSDUMP.F8
// SETPARM XNCPU=''
// SETPARM XMODEF8=AUTO
// SETPARM XAPPLF8=''
// EXEC PROC=$COMVAR,XNCPU
// EXEC DTRSETP,PARM='CPUVAR&XNCPU;;SET XSTATF8=ACTIVE' **F8 ASSUMED
$$/*
// EXEC PROC=CPUVAR&XNCPU,XMODEF8,XAPPLF8 **F8 ASSUMED
// SETPFIX LIMIT=256K
LOG
// ID USER=PRODCICS
NOLOG
// ASSGN SYS019,DISK,VOL=DOSRES,SHR JOURNAL FILES
// DLBL DFHCXRF,'CICS2.PRODCICS.DFHCXRF',0,SD XRF TD
// EXTENT SYS020,DOSRES,1,0,14820,5
// ASSGN SYS020,DISK,VOL=DOSRES,SHR
// EXEC PROC=DTRCICS2 LABELS FOR CICS FILES
* WAITING FOR VTAM TO COME UP
// EXEC IESWAITT
$$/*
// IF XMODEF8 = COLD THEN
// GOTO COLDST
// SETPARM XMODEF8=AUTO
// GOTO STARTCIC
/. COLDST
// SETPARM XMODEF8=COLD
/. STARTCIC
// EXEC DFHSIP,SIZE=DFHSIP,PARM='APPLID=&XAPPLF8.,START=&XMODEF8.,SI', * . .
DSPACE=2M,OS390 . .
SIT=C2,STATRCD=OFF,SVA=NO . .
$$/*
// EXEC DTRSETP,PARM='CPUVAR&XNCPU;;SET XSTATF8=INACTIVE'
$$/*
$$/&
$$$$ EOJ
/+
CATALOG LDCICS2.PROC REPLACE=YES DATA=YES
// EXEC DTRIINIT
LOAD CICS2.Z
/*
/+
/*
// EXEC PROC=LDCICS2 LOAD CICS2 INTO RDR QUEUE
/*
/&
* $$ EOJ
Figure 15. Catalog CICS startup and load into RDR queue
. .To override SIT parameters, we used the PARM parameter and also the
SYSIN keyword (SI) to tell CICS to read system initialization parameters from the
SYSIPT data set.
. .The CICS TS must run in OS390 emulation mode. To activate OS390
emulation mode, code the OS390 parameter at the end of the // EXEC statement.
. .The SYSIPT data.
Chapter 2. Installation and tailoring 25
2.3.4 Customizing the DFHSIT table
You must modify the existing system initialization tables, removing all obsolete
parameters, and specifying the required values for new or changed parameters
if you want to run with other than the defaults. After this, reassemble the tables
using CICS Transaction Server macro libraries.
Table 4 summarizes the major changes in system initialization parameters. See
CICS Transaction Server for VSE/ESA System Definition Guide for a complete
description:
Table 4 (Page 1 of 5). Summary of DFHSIT parameter changes
Area Parameter Remarks
CSD definitions CSDACC new
CSDJID new
CSDBUFNI new
CSDLSRNO new
CSDBUFND new
CSDRECOV new
CSDFRLOG new
CSDSTRNO new
DSA definitions DSASLIM new
EDSALIM new
BMS Definitions BMS changed
Autoinstall definitions AIEXIT new
AILDELAY new
AIQMAX new
AIRDELAY new
AUTINST removed
PGAICTLG new
PGAIEXIT new
PGAIPGM new
Monitoring definitions MN new
MNCONV new
MNFREQ new
MNTIME new
MNEXC new
MNPER new
MNSYNC new
MONITOR removed
Dispatcher parameters ICVTSD changed
ICVS removed
MXT changed
AMXT removed
CMXT removed
26 VSE/ESA V2R4
Table 4 (Page 2 of 5). Summary of DFHSIT parameter changes
Area Parameter Remarks
Storage protection CMDPROT new
CWAKEY new
RENTPGM new
STGPROT new
TCTUAKEY new
Storage management CHKSTRM new
CHKSTSK new
CDSASZE new
ECDSASZE new
PGSIZE removed
RDSASZE new
ERDSASZE new
SCS removed
SDSASZE new
ESDSASZE new
STGRCVY new
TCTUALOC new
UDSASZE new
EUDSASZE new
Temporary Storage TSMGSET new
definitions
TS changed
Dump definitions ABDUMP removed
DUMP changed
DUMPDS changed
DUMPSW new
PCDUMP removed
SVD removed
SYDUMAX new
TRDUMAX new
Trace definitions AUXTR new
AUXTRSW new
INTTR new
SPCTR new
SPCTRxx new
STNTR new
STNTRxx new
SYSTR new
TRACE removed
TRTABSZ new
TRTRANSZ new
TRTRANTY new
USERTR new
Chapter 2. Installation and tailoring 27
Table 4 (Page 3 of 5). Summary of DFHSIT parameter changes
Area Parameter Remarks
XRF definitions XRFSOFF new
XRFSTME new
XRFTRSZ removed
Persistent session PSDINT New
SVA Management PRVMOD new
SVA new
Application considerations BFP removed
COBOL2 removed
DISMACP New
EXEC removed
INITPARM new
LESTG removed
PLI removed
RUWAPOOL new
Terminal and LU DSHIPIDL new
management
DSHIPINT new
EODI new
FERS removed
GNTRAN new
OPNDLIM removed
PVDELAY new
PRINT changed
RESP new
TCSACTN new
TCSWAIT new
USRDELAY new
VTPREFIX changed
ISC and MRO operation APPLID changed
DTRTRAN new
FSSTAFF new
MROFSE new
SYSIDNT changed
Transient data TD changed
DTB definitions DBP changed
DTB removed
28 VSE/ESA V2R4
Table 4 (Page 4 of 5). Summary of DFHSIT parameter changes
Area Parameter Remarks
Security definitions CMDSEC new
CONFDATA new
CONFTXT new
DFLTUSER new
ESMEXITS new
EXTSEC removed
PLTPIUSR new
PLPTISEC new
SEC new
SECPRFX new
SNSCOPE new
XCMD new
XUSER new
XDCT changed
XFCT changed
XJCT changed
XPCT changed
XPPT changed
XTST changed
RESSEC new
Exit definitions TBEXITS changed
ALEXIT removed
EXITS removed
Initialization ALT removed
FCT changed
GMTRAN changed
GRPLIST changed
NLT removed
PCT removed
PPT removed
SIMODS removed
START changed
SUFFIX changed
SRT changed
TCP changed
ZCP removed
Chapter 2. Installation and tailoring 29
Table 4 (Page 5 of 5). Summary of DFHSIT parameter changes
Area Parameter Remarks
Miscellaneous DIP removed
FEPI new
MSGCASE new
NEWSIT new
PARMERR new
PRTYAGE new
STATRCD new
JSTATUS changed
DATFORM changed
2.3.4.1 CICS system initialization table generation
The following definition is the source of the DFHSITC2 table. You can use this as
a model to tailor and assemble your own table depending on your requirements.
We used the DFHSIT skeleton from ICCF library 59.
TITLE 'DFHSITC2 -- SIT FOR CICS TS - APPLID PRODCICS'
PUNCH ' CATALOG DFHSITC2.OBJ REP=YES'
DFHSIT TYPE=CSECT, *
AIEXIT=IESZATDX, AUTO INSTALL TERMINALS *
AILDELAY=200, AUTO INSTALL DEL TERM PQ03810*
AIQMAX=100, AUTO INSTALL CONC TERMINALS *
AIRDELAY=700, AUTO INSTALL ELAPS TIME *
AKPFREQ=200, ACTIVITY KEYPOINTING FREQUENCY *
APPLID=PRODCICS, CICS APPLICATION NAME *
AUXTR=OFF, AUXTRACE OFF *
BMS=FULL, FULL BASIC MAPPING SUPPORT *
CMDPROT=YES, VALIDATE START ADDRESSES *
CMDSEC=ASIS, CMDSEC WILL BE HONORED *
CONFDATA=SHOW, SHOW USER DATA IN TRACE *
CONFTXT=NO, VTAM SHOW USER DATA *
CSDACC=READWRITE, CSD MAY BE UPDATED *
CSDLSRNO=1, CSD LOCAL SHARED RESOURCE *
CSDSTRNO=4, CSD SIMULTANEOUS ACCESS *
DATFORM=MMDDYY, EXTERNAL DATE DISPLAY *
DBP=1$, DYN. BACKOUT (NO LOCAL DLI I/F)*
DBUFSZ=2000, DYN. ADJUSTED BY CICS *
DCT=C2, FOR SECOND CICS *
DFLTUSER=CICSUSER, DEFAULT USER *
DISMACP=YES, ASRD ABEND IN CASE MACROS I/F *
DLI=NO, NO DL/I SUPPORT *
DSALIM=5M, UPPER LIMIT OF STORAGE BELOW *
DUMP=YES, IDUMP IN ABEND SITUATIONS *
DUMPDS=AUTO, AUTO SWITCH DUMP DATA SETS *
DUMPSW=NEXT, USERS MAY NOT USE DUMPSW S *
EDSALIM=25M, DSA ABOVE THE LINE ENV. B *
FCT=C2, FOR SECOND CICS *
GMTEXT='VSE/ESA CICS2', GOOD MORNING MESSAGE TEXT *
GMTRAN=IEGM, LOGON TRANSACTION ID *
GNTRAN=IEGT, TIME OUT TRANSACTION *
GRPLIST=VSELST2, AUTOINST. TERMINALS. AND MRO *
ICP=COLD, INTERVAL CONTROL PGM *
ICV=1000, INTERVAL CONTROL EXIT TIME-MS *
ICVR=20000, RUNAWAY TASK TIME *
ICVTSD=200, TERMINAL SCAN DELAY *
INTTR=ON, INTERNAL TRACE *
IRCSTRT=NO, START IRC DURING INITIALIZATION*
ISC=YES, INTERSYSTEM COMMUNICATION *
JCT=C2, NO JOURNALLING *
LGNMSG=YES, VTAM LOGON DATA *
MCT=NO, NO MONITOR CONTROL TABLE *
MN=OFF, MONITORING OFF *
MNCONV=NO, NO MONITORING OF CONVERSATIONAL*
MNEXC=OFF, MONITORING EXCEPTION CLASS *
30 VSE/ESA V2R4
MNFREQ=0, MONITORING FREQUENCY *
MNPER=OFF, MONITORING PERFORMANCE CLASS *
MNSYNC=NO, MONITORING SYNCPOINT *
MNTIME=LOCAL, MONITORING TIME GMT *
MROBTCH=1, MRO BATCHING EVENTS *
MROLRM=YES, MRO LONG RUNNING MIRROR TASK *
MSGLVL=1, MESSAGES ON BOTH SYSLST/SYSLOG *
MXT=50, MAX NO. OF ALL CONCURRENT TASKS*
NATLANG=E, (E,X) X = S,G,... NLS *
PGAICTLG=ALL, UPDATE AUTOINSTALL PGM DEFINING*
PGAIEXIT=DFHPGADX, PGM AUTOINSTALL EXIT *
PGAIPGM=ACTIVE, PGM AUTOINSTALL ACTIVE *
PGCHAIN=X/, BMS CHAINING COMMAND *
PGCOPY=COPY/, BMS COPY COMMAND *
PGPURGE=T/, BMS PURGE COMMAND *
PGRET=P/, BMS RETRIEVAL COMMAND *
PLTPI=P2, POST-INITIALIZATION PLT *
PLTPISEC=CMDSEC, POST-INITIALIZATION PLT SECURE *
PLTPIUSR=CICSUSER, POST-INITIALIZATION PLT USER *
PLTSD=S2, SHUTDOWN PLT *
PRGDLAY=100, ONE HOUR PURGE DELAY *
PRINT=PA1, PRINT WITH PA1 AND TCP PRINT *
PRTYAGE=5000, PRIORITY AGING 5 SECONDS *
RAMAX=256, SIZE OF I/O AREA FOR RA *
RAPOOL=10, NUMBER OF FIXED RPLS *
SEC=YES, FULL SECURITY *
SECPRFX=NO, NO SECURITY PREFIX *
SNSCOPE=NONE, SIGNON MORE THAN ONCE *
SPCTR=1, SPECTRUM OF TRACE *
SPOOL=(YES,B,A), CICS SPOOLER ACTIVE *
SRT=1$, DEFAULT SRT *
START=AUTO, LET CICS DETERMINE STARTUP *
STATRCD=ON, STATISTICS RECORDING *
STGPROT=NO, STORAGE PROTECTION *
STGRCVY=YES, RECOVER FROM STORAGE VIOLATION *
STNTR=1, STANDARD TRACING *
SUFFIX=C2, FOR SECOND CICS *
SVA=NO, NO SVA LOADING FOR COEXISTENCE *
SYSIDNT=CIC2, IDENTIFIER OF THIS CICS *
SYSTR=ON, ALLOW SYSTR CODING *
TCP=YES, TERMINAL CONTROL PROGRAM *
TCSACTN=NONE, TERMINAL CONTROL SHUTDOWN *
TCT=C2, FOR AUTOINSTALLED TERMINALS *
TCTUALOC=BELOW, TCTUA STORAGE BELOW II *
TD=(3,3), THREE BUFFERS & THREE STRINGS *
TRTABSZ=80, SIZE OF INTERNAL TRACE TABLE *
TRTRANSZ=80, TRANSACTION DUMP TRACE SIZE *
TRTRANTY=TRAN, TRANSACTION DUMP TRACE TYPE *
TS=(,8,8), EIGHT BUFFERS & EIGHT STRINGS *
TSMGSET=20, 20 MESSAGE SET ENTRIES *
TST=NO, NO TEMP STORAGE TABLE INCLUDED *
USERTR=ON, ALLOW USER TO SET MASTER TRACE *
VTPREFIX=C, COMMON CLIENT TERM NAME PREFIX *
WRKAREA=512, COMMON WORK AREA OF THE CSA *
XCMD=NO, COMMAND SECURITY *
XDCT=NO, DCT SECURITY *
XFCT=NO, FCT SECURITY *
XJCT=NO, JCT SECURITY *
XLT=SP, SUPPLIED WITH VSE/ESA *
XPCT=NO, PCT SECURITY *
XPPT=NO, PPT SECURITY *
XPSB=NO, PSB SECURITY *
XRF=NO, NO XRF SUPPORT INCLUDED *
XUSER=NO, SURROGATE USER *
XTST=NO, TST SECURITY *
DUMMY=DUMMY TO END MACRO
END DFHSITBA
Chapter 2. Installation and tailoring 31
2.3.5 Migrating the DFHPCT and DFHPPT tables
A number of functions are withdrawn in CICS TS, especially the ability to define
transaction and program resource definitions using suffixed PCTs and PPTs.
You must define in the CSD:
Transactions
Transaction profiles
Programs
Map sets
Partition sets for basic mapping support
2.3.5.1 Migration steps
To perform the migration, you have to do the following:
Edit your existing DFHPCT/DFHPPT source.
Assemble and link-edit the edited source.
Process the link-edited table using the DFHCSDUP utility.
Check the output produced by the DFHCSDUP utility.
Initialize CICS with the migrated definitions.
Editing your existing DFHPCT/DFHPPT source: You must reassemble your
existing DFHPCT/DFHPPT source using CICS Transaction Server macro libraries.
The DFHPCT and DFHPPT macros are available only as input to the migration
utility program in DFHCSDUP. Remove all IBM-supplied CICS and VSE
Interactive Interface entries before assembling.
If your source is large, you might find it most convenient to assemble small
segments of the source individually, because each resource definition on the
CSD must belong to a CSD group. It is better to create many small groups for
your files rather than one large group. Try to limit groups to 100 resource
definitions.
Usually the definitions within a group have something in common. For example,
keep all the resource definitions belonging to one application in one group: one
CSD group for payroll application, one CSD group for inventory application.
You can specify the names to be given to groups of definitions generated from
your DFHPCT macros or DFHPPT macros by adding:
DFHPCT TYPE=GROUP,GROUP=GROUPNAME
or
DFHPPT TYPE=GROUP,GROUP=GROUPNAME
All definitions following a particular TYPE=GROUP macro statement are
migrated into the named group in the CSD file. A new TYPE=GROUP statement
overrides all previous ones.
Figure 16 on page 33 is the DFHPPTC2 source we used:
32 VSE/ESA V2R4
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
TITLE 'DFHPPTC2 -- SUPPLIED WITH VSE/ESA'
PUNCH ' CATALOG DFHPPTC2.OBJ REP=YES'
DFHPPT TYPE=INITIAL,SUFFIX=C2,MIGRATE=YES
*
DFHPPT TYPE=GROUP,GROUP=DB2610
*
DFHPPT TYPE=ENTRY,PROGRAM=ARIRCONT,RES=YES,PGMLANG=ASSEMBLER
DFHPPT TYPE=ENTRY,PROGRAM=ARI0OLRM,PGMLANG=ASSEMBLER
DFHPPT TYPE=ENTRY,PROGRAM=ARICMOD,PGMLANG=ASSEMBLER
DFHPPT TYPE=ENTRY,PROGRAM=ARIMS001,RES=YES,PGMLANG=ASSEMBLER
DFHPPT TYPE=ENTRY,PROGRAM=ARIISQL,RES=YES,PGMLANG=ASSEMBLER
DFHPPT TYPE=ENTRY,PROGRAM=ARIITRM,RES=YES,PGMLANG=ASSEMBLER
DFHPPT TYPE=ENTRY,PROGRAM=ARIITRX,RES=YES,PGMLANG=ASSEMBLER
DFHPPT TYPE=ENTRY,PROGRAM=ARICDIRD,PGMLANG=ASSEMBLER
DFHPPT TYPE=FINAL
END DFHPPTBA
/*
Figure 16. DFHPPT source
The DFHPCTC2 source is shown in Figure 17 on page 34:
Chapter 2. Installation and tailoring 33
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
TITLE 'DFHPCTC2 -- SUPPLIED WITH VSE/ESA'
PUNCH ' CATALOG DFHPCTC2.OBJ REP=YES'
DFHPCT TYPE=INITIAL,SUFFIX=C2,MIGRATE=YES
*
DFHPCT TYPE=GROUP,GROUP=DB2610
*
CIRA DFHPCT TYPE=ENTRY, ADD CONNECTION X
TRANSID=CIRA, X
PROGRAM=ARIRCONT, X
TWASIZE=0, X
DTB=YES, X
SPURGE=YES, X
TPURGE=YES
CIRB DFHPCT TYPE=ENTRY, ESTABLISH CONNECTION X
TRANSID=CIRB, X
PROGRAM=ARIRCONT, X
TWASIZE=0, X
DTB=YES, X
SPURGE=YES, X
TPURGE=YES
CIRC DFHPCT TYPE=ENTRY, CHANGE DEFAULT DB X
TRANSID=CIRC, X
PROGRAM=ARIRCONT, X
TWASIZE=0, X
DTB=YES, X
SPURGE=YES, X
TPURGE=YES
CIRD DFHPCT TYPE=ENTRY, DISPLAY CONNECTION STATUS X
TRANSID=CIRD, X
PROGRAM=ARIRCONT, X
TWASIZE=0, X
DTB=YES, X
SPURGE=YES, X
TPURGE=YES
CIRR DFHPCT TYPE=ENTRY, REMOVE CONNECTION X
TRANSID=CIRR, X
PROGRAM=ARIRCONT, X
TWASIZE=0, X
DTB=YES, X
SPURGE=YES, X
TPURGE=YES
CIRT DFHPCT TYPE=ENTRY, TERMINATE CONNECTION X
TRANSID=CIRT, X
PROGRAM=ARIRCONT, X
TWASIZE=0, X
DTB=YES, X
SPURGE=YES, X
TPURGE=YES
ISQL DFHPCT TYPE=ENTRY, X
TRANSID=ISQL, X
PROGRAM=ARIITRM, X
TWASIZE=300, X
DTB=YES, X
SPURGE=NO, X
TPURGE=YES, X
SCRNSZE=ALTERNATE
CISQ DFHPCT TYPE=ENTRY, X
TRANSID=CISQ, X
PROGRAM=ARIISQL, X
TWASIZE=0, X
DTB=YES, X
SPURGE=NO, X
TPURGE=YES
DFHPCT TYPE=FINAL
END DFHPCTBA
/*
Figure 17. DFHPCT source
34 VSE/ESA V2R4
Most DFHPCT and DFHPPT macros have CSD equivalents. Table 5 shows the
exceptions:
Table 5. Exceptions for CSD equivalents
DFHPCT macro operands without RDO equivalents
ANTICPG
DTB=NO
FDUMP
PRMSIZE
DFHPPT macro operands without RDO equivalents
FN
LENABLE
RES=PGOUT
RES=FIX
RES=ALIGN
RSL
Assemble and link-edit the source: You must assemble your table using the
CICS Transaction Server macro library and link-edit it into your CICS load
library. If you get a return code greater than 4, remove the cause of the error
and reassemble.
Using the DFHCSDUP utility: To convert the table entries into resource
definitions, use the MIGRATE command of the DFHCSDUP offline utility program;
Figure 18 shows an example:
// EXEC DFHCSDUP,SIZE=DFHCSDUP
MIGRATE TABLE(DFHPCTC2) TOGROUP(DB2610)
MIGRATE TABLE(DFHPPTC2) TOGROUP(DB2610)
/*
Figure 18. MIGRATE command to transfer a PCT and a PPT to the CSD
Checking the output from MIGRATE: Migration may have produced some
messages. Read these warning messages carefully.
Figure 19 on page 36 shows the output from the MIGRATE command:
Chapter 2. Installation and tailoring 35
// EXEC DFHCSDUP,SIZE=DFHCSDUP
MIGRATE TABLE(DFHPCTC2) TOGROUP(DB2610)
DFHCA5120 I PRIMARY CSD OPENED; FILENAME: DFHCSD
DFHCA5144 I MIGRATION OF TABLE DFHPCTC2 IN PROGRESS. DEFAULT GROUP IS DB2610
DFHCA5143 I GROUP DB2610 CREATED.
DFHCA5159 I TRANSACTION CIRA DEFINED IN GROUP DB2610
DFHCA5162 I TRANSACTION CIRA USES PROFILE XXXXCIRA
DFHCA5159 I PROFILE XXXXCIRA DEFINED IN GROUP DB2610
DFHCA5159 I TRANSACTION CIRB DEFINED IN GROUP DB2610
DFHCA5162 I TRANSACTION CIRB USES PROFILE XXXXCIRA
DFHCA5159 I TRANSACTION CIRC DEFINED IN GROUP DB2610
DFHCA5162 I TRANSACTION CIRC USES PROFILE XXXXCIRA
DFHCA5159 I TRANSACTION CIRD DEFINED IN GROUP DB2610
DFHCA5162 I TRANSACTION CIRD USES PROFILE XXXXCIRA
DFHCA5159 I TRANSACTION CIRR DEFINED IN GROUP DB2610
DFHCA5162 I TRANSACTION CIRR USES PROFILE XXXXCIRA
DFHCA5159 I TRANSACTION CIRT DEFINED IN GROUP DB2610
DFHCA5162 I TRANSACTION CIRT USES PROFILE XXXXCIRA
DFHCA5159 I TRANSACTION ISQL DEFINED IN GROUP DB2610
DFHCA5162 I TRANSACTION ISQL USES PROFILE XXXXISQL
DFHCA5159 I PROFILE XXXXISQL DEFINED IN GROUP DB2610
DFHCA5159 I TRANSACTION CISQ DEFINED IN GROUP DB2610
DFHCA5162 I TRANSACTION CISQ USES PROFILE XXXXCIRA
DFHCA5156 W PROFILE DFHCICSA DID NOT MIGRATE. ITS PROPERTIES MATCH AN IBM-SUPPLIED DEFINITION IN GROUP DFHSTAND
DFHCA5156 W PROFILE DFHCICST DID NOT MIGRATE. ITS PROPERTIES MATCH AN IBM-SUPPLIED DEFINITION IN GROUP DFHSTAND
DFHCA5156 W PROFILE DFHCICSV DID NOT MIGRATE. ITS PROPERTIES MATCH AN IBM-SUPPLIED DEFINITION IN GROUP DFHSTAND
DFHCA5140 I TOTAL TRANSACTION DEFINITIONS CREATED: 8
DFHCA5140 I TOTAL PROFILE DEFINITIONS CREATED: 2
DFHCA5102 I WARNING MESSAGE(S) ISSUED WHILE PROCESSING MIGRATE COMMAND.
DFHCA5123 I PRIMARY CSD CLOSED; FILENAME: DFHCSD
MIGRATE TABLE(DFHPPTC2) TOGROUP(DB2610)
DFHCA5120 I PRIMARY CSD OPENED; FILENAME: DFHCSD
DFHCA5144 I MIGRATION OF TABLE DFHPPTC2 IN PROGRESS. DEFAULT GROUP IS DB2610
DFHCA5159 I PROGRAM ARIRCONT DEFINED IN GROUP DB2610
DFHCA5159 I PROGRAM ARI0OLRM DEFINED IN GROUP DB2610
DFHCA5159 I PROGRAM ARICMOD DEFINED IN GROUP DB2610
DFHCA5159 I PROGRAM ARIMS001 DEFINED IN GROUP DB2610
DFHCA5159 I PROGRAM ARIISQL DEFINED IN GROUP DB2610
DFHCA5159 I PROGRAM ARIITRM DEFINED IN GROUP DB2610
DFHCA5159 I PROGRAM ARIITRX DEFINED IN GROUP DB2610
DFHCA5159 I PROGRAM ARICDIRD DEFINED IN GROUP DB2610
DFHCA5140 I TOTAL PROGRAM DEFINITIONS CREATED: 8
DFHCA5101 I MIGRATE COMMAND EXECUTED SUCCESSFULLY.
DFHCA5123 I PRIMARY CSD CLOSED; FILENAME: DFHCSD
DFHCA5107 I COMMANDS EXECUTED SUCCESSFULLY: 1 COMMANDS GIVING WARNING(S): 1 COMMANDS IN ERROR: 0
DFHCA5108 I COMMANDS NOT EXECUTED AFTER ERROR(S): 0
DFHCA5109 I END OF DFHCSDUP UTILITY JOB. HIGHEST RETURN CODE WAS: 4
Figure 19. Output from PCT and PPT MIGRATE command
From the output listing you can see the names of groups, transactions, profiles
and programs defined in the CSD.
Initializing CICS after migration: Every resource definition is a member of a
group. To have these groups installed at initialization, you must do the following:
1. Use DFHCSDUP or RDO to ADD each group to a list.
Figure 20 on page 37 shows the sample JCL for the ADD command in the
DFHCSDUP offline utility:
36 VSE/ESA V2R4
// EXEC DFHCSDUP,SIZE=DFHCSDUP
ADD GROUP(DB2610) LIST(VSELST2)
ADD GROUP(PAYROLL) LIST(VSELST2)
ADD GROUP(VSEFILES) LIST(VSELST2)
ADD GROUP(SUPPORT) LIST(VSELST2)
/*
Figure 20. ADD command from DFHCSDUP
Figure 21 shows the sample ADD command in the CEDA transaction:
ADD GROUP(DB2610) LIST(VSELST2)
OVERTYPE TO MODIFY
CEDA ADD
GROUP ==> DB2610
LIST ==> VSELST2
BEFORE ==>
AFTER ==>
SYSID=CIC1 APPLID=DBDCCICS
ADD SUCCESSFUL TIME: 17.31.32 DATE: 99.085
PF 1 HELP 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 21. RDO ADD command - CEDA transaction
2. Use the GRPLIST parameter in the DFHSIT table or in the PARM field in CICS
initialization to tell CICS which groups are to be installed.
Figure 22 shows part of the CICS startup job with the PARM parameter:
.
.
/. STARTCIC
// EXEC DFHSIP,SIZE=DFHSIP,PARM='GRPLIST=VSELST2,FCT=C2,TCT=C2,SI', *
DSPACE=2M,OS390
SIT=C2,STATRCD=OFF,SVA=NO
.
.
Figure 22. Sample of CICS initialization with GRPLIST in the overrides
Figure 23 on page 38 shows part of the DFHSIT table with the GRPLIST
parameter:
Chapter 2. Installation and tailoring 37
.
.
.
DUMPSW=NEXT, USERS MAY NOT USE DUMPSW S *
EDSALIM=25M, DSA ABOVE THE LINE ENV. B *
FCT=C2, FOR SECOND CICS *
GMTEXT='VSE/ESA CICS2', GOOD MORNING MESSAGE TEXT *
GMTRAN=IEGM, LOGON TRANSACTION ID *
GNTRAN=IEGT, TIME OUT TRANSACTION *
GRPLIST=VSELST2, CSD LIST NAME FOR STARTUP *
ICP=COLD, INTERVAL CONTROL PGM *
ICV=1000, INTERVAL CONTROL EXIT TIME-MS *
.
.
SYSTR=ON, ALLOW SYSTR CODING *
TCP=YES, TERMINAL CONTROL PROGRAM *
TCSACTN=NONE, TERMINAL CONTROL SHUTDOWN *
TCT=C2, FOR AUTOINSTALLED TERMINALS *
TCTUALOC=BELOW, TCTUA STORAGE BELOW II *
.
.
.
Figure 23. Sample of DFHSIT with GRPLIST parameter
3. Initialize the CICS partition.
Alternatively, you can wait until CICS has initialized, and then use RDO to
INSTALL the groups that you want CICS to use, as shown in Figure 24:
INSTALL GROUP(DB2610)
OVERTYPE TO MODIFY
CEDA Install
All
Connection ==>
File ==>
Lsrpool ==>
Mapset ==>
PARTItionset ==>
PARTNer ==>
PROFile ==>
PROGram ==>
TErminal ==>
TRANClass ==>
TRANSaction ==>
TYpeterm ==>
Group ==> DB2610
SYSID=CIC2 APPLID=PRODCICS
INSTALL SUCCESSFUL TIME: 12.22.20 DATE: 99.088
PF 1 HELP 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 24. RDO INSTALL command - CEDA transaction
The installed resources are active as long as CICS is WARM or EMERgency
restarted. Add the resources to the GRPLIST to ensure they are activated after a
COLD start.
In CICS/VSE 2.3, the RDO INSTALL command operated only on groups. Now you
can use the INSTALL command for a single resource, rather than having to
INSTALL the whole group.
38 VSE/ESA V2R4
To create a new program definition in the CSD, you use the DEFINE PROGRAM
command in the following:
Resource definition online (RDO): CEDA or CEDB transactions
DFHCSDUP offline utility
Autoinstall (see 2.3.10, “Autoinstall of resources” on page 62)
Figure 25 shows the RDO Program Definition:
V PROGRAM(ARIRCONT) GROUP(DB2610)
OBJECT CHARACTERISTICS CICS RELEASE = 0410
CEDA View PROGram( ARIRCONT )
PROGram : ARIRCONT
Group : DB2610
DEscription : . .
Language : Assembler CObol | Assembler | C | Pli
RELoad : No No | Yes
RESident : Yes No | Yes
USAge : Normal Normal | Transient . .
USEsvacopy : No No | Yes . .
Status : Enabled Enabled | Disabled
RSl : 00 0-24 | Public
Cedf : Yes Yes | No . .
DAtalocation : Below Below | Any . .
EXECKey : User User | Cics . .
REMOTE ATTRIBUTES
REMOTESystem :
REMOTEName :
Transid :
EXECUtionset : Fullapi Fullapi | Dplsubset
SYSID=CIC2 APPLID=PRODCICS
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 25. RDO VIEW PROGRAM - CEDA transaction
. .New parameters, see CICS Transaction Server for VSE/ESA Resource
Definition Guide .
To create a new transaction definition in the CSD, you use the DEFINE
TRANSACTION command in the following:
Resource definition online (RDO): CEDA or CEDB transactions
DFHCSDUP offline utility
Figure 26 on page 40 shows the RDO Transaction Definition:
Chapter 2. Installation and tailoring 39
V TRANS(CIRA) GROUP(DB2610)
OBJECT CHARACTERISTICS CICS RELEASE = 0410
CEDA View TRANSaction( CIRA )
TRANSaction : CIRA
Group : DB2610
DEscription : . .
PROGram : ARIRCONT
TWasize : 00000 0-32767
PROFile : XXXXCIRA
PArtitionset :
STAtus : Enabled Enabled | Disabled
PRIMedsize : 00000 0-65520
TASKDATALoc : Below Below | Any . .
TASKDATAKey : User User | Cics . .
STOrageclear : No No | Yes . .
RUnaway : System System | 0 | 500-2700000 . .
SHutdown : Disabled Disabled | Enabled . .
REMOTE ATTRIBUTES
DYnamic : No No | Yes
REMOTESystem :
REMOTEName :
TRProf :
Localq : No | Yes
SCHEDULING
PRIOrity : 001 0-255
TClass : No No | 1-10 . .
TRANClass : DFHTCL00 . .
ALIASES
Alias :
TASKReq :
XTRanid :
TPName : . .
:
XTPname : . .
:
:
RECOVERY
DTimout : No No | 1-6800
Indoubt : Backout Backout | Commit | Wait
RESTart : No No | Yes
SPurge : Yes No | Yes
TPUrge : Yes No | Yes
DUmp : Yes Yes | No
TRACe : Yes Yes | No
COnfdata : No No | Yes . .
SECURITY
RESSec : No No | Yes . .
CMdsec : No No | Yes . .
Extsec : No No | Yes
TRANSec : 01 1-64
RSl : 00 0-24 | Public
SYSID=CIC2 APPLID=PRODCICS
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 26. RDO VIEW TRANSACTION - CEDA transaction
. .New parameters, see CICS Transaction Server for VSE/ESA Resource
Definition Guide .
. .See 2.3.11.2, “The new TRANCLASS definition” on page 69.
40 VSE/ESA V2R4
To create a new profile definition in the CSD, you use the DEFINE PROFILE
command in:
Resource definition online (RDO): CEDA or CEDB transactions
DFHCSDUP offline utility
Figure 27 shows the RDO Profile Definition:
V PROFILE(XXXXCIRA) GROUP(DB2610)
OBJECT CHARACTERISTICS CICS RELEASE = 0410
CEDA View PROFile( XXXXCIRA )
PROFile : XXXXCIRA
Group : DB2610
DEscription : . .
Scrnsize : Default Default | Alternate
Uctran : No No | Yes
MOdename :
PRIntercomp : No No | Yes
JOURNALLING
Journal : No No | 1-99
MSGJrnl : No No | INPut | Output | INOut
PROTECTION
MSGInteg : No No | Yes
Onewte : No No | Yes
PROtect : No No | Yes
Chaincontrol : No No | Yes . .
PROTOCOLS
DVsuprt : All All | Nonvtam | Vtam
Inbfmh : Eods No | All | Dip | Eods
RAq : No No | Yes
Logrec : No No | Yes
RECOVERY
Nepclass : 000 0-255
RTimout : No No | 1-7000
SYSID=CIC2 APPLID=PRODCICS
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 27. RDO VIEW PROFILE - CEDA transaction
. .New parameters, see CICS Transaction Server for VSE/ESA Resource
Definition Guide .
2.3.6 Customizing and migrating the DFHFCT table
You can define the following data sets using either RDO or file control table
(FCT) macros:
VSAM files
Remote VSAM files
Remote DAM files
VSAM local shared resource (LSR) pools
Shared data tables
We strongly recommend that you migrate these definitions to the CSD in order to
take advantage of the benefits of online definition. Any future releases of CICS
will support online definition only for these resources.
Chapter 2. Installation and tailoring 41
Whatever your choices, the result will be an FCT built from one or both of the
following:
Entries defined using DFHFCT macros
Entries defined and installed using RDO and the GRPLIST parameter
Entries of both kinds can coexist, so that you can keep your existing tables and
try the new function in parallel.
If you continue using your existing DFHFCT macro, you must remove the CSD
entry from the FCT source statements, and then reassemble the table. The CSD
is now defined by system initialization parameters. See CICS Transaction Server
for VSE/ESA System Definition Guide for details.
If you define the same file with both RDO and the macro method, be aware that
the macro definitions are installed during cold start first, and then the
RDO-defined file entry overrides the equivalent macro-defined file entry when
they are installed (using CEDA install or during group list install on a cold start).
If you use data tables, see 2.3.11.3, “Shared data tables” on page 70.
2.3.6.1 Migration steps
To perform the migration of at least some of your table entries to RDO, you have
to do the following:
1. Edit your existing DFHFCT source, removing any definition for the CSD.
2. Assemble and link-edit the edited source.
3. Process the link-edited table using the DFHCSDUP utility.
4. Check the output produced by the DFHCSDUP utility.
5. Use the DFHCSDUP ADD command to add the new groups to a list of groups
on your CSD.
6. Remove from your macro source all the table entries that have been
migrated and reassemble it.
7. Start up your system with the non-VSAM FCT (if any) and the list you have
created.
Editing your existing DFHFCT source: As previously mentioned, you must
reassemble your existing DFHFCT source using the CICS Transaction Server
macro library. If your source is large, you might find it most convenient to
assemble small segments of the source individually, because each resource
definition on the CSD must belong to a CSD group. It is better to create many
small groups for your files rather than one large group. Try to limit groups to 100
resource definitions.
Usually the definitions within a group have something in common. For example,
keep all the resource definitions belonging to one application in one group (one
CSD group for payroll application, one CSD group for inventory application), or
according to the department or function of the people using them.
You can specify the names to be given to groups of definitions generated from
your DFHFCT macros by adding:
DFHFCT TYPE=GROUP,GROUP=GROUPNAME
42 VSE/ESA V2R4
All definitions following a particular TYPE=GROUP macro statement are
migrated into the named group in the CSD file.
A new TYPE=GROUP statement defines a new group; Figure 28 shows an
example:
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
TITLE 'DFHFCTC2 -- SUPPLIED WITH VSE/ESA'
PUNCH ' CATALOG DFHFCTC2.OBJ REP=YES'
DFHFCT TYPE=INITIAL,SUFFIX=C2,MIGRATE=YES
*
DFHFCT TYPE=GROUP,GROUP=VSEFILES
*
COPY IESZFCTO -- DATASET ENTRIES FOR VSE/ESA - OTHER PARTITION
*
DFHFCT TYPE=GROUP,GROUP=PAYROLL
*
FILEA DFHFCT TYPE=FILE, *
FILE=FILEA, *
ACCMETH=VSAM, *
RECFORM=(FIXED,BLOCKED), *
LSRPOOL=01, *
JID=02, *
JREQ=ALL, *
LOG=YES, *
SERVREQ=(UPDATE,ADD,BROWSE,DELETE), *
STRNO=3
*
FILEB DFHFCT TYPE=FILE, *
FILE=FILEB, *
ACCMETH=VSAM, *
RECFORM=(FIXED,BLOCKED), *
LSRPOOL=01, *
JID=02, *
JREQ=ALL, *
LOG=YES, *
SERVREQ=(READ,BROWSE), *
STRNO=2
*
FILEC DFHFCT TYPE=FILE, *
FILE=FILEC, *
ACCMETH=DAM, *
RECFORM=(UNDEFINED), *
BLKSIZE=88, *
LRECL=60, *
EXTENT=01
DFHFCT TYPE=SHRCTL, *
LSRPOOL=01, *
BUFFERS=(512(12),1024(12)), *
KEYLEN=10, *
STRNO=3
SPACE 3
DFHFCT TYPE=FINAL
END DFHFCTBA
/*
Figure 28. DFHFCT source
Table 6 shows changes to the DFHFCT macros:
Table 6. Changes to the DFHFCT macro
removed RSL
SERVREQ=REUSE
new DSNAME
TYPE=GROUP
MIGRATE
changed SRCHM (DAM only)
Chapter 2. Installation and tailoring 43
Assemble and link-edit the source: You must assemble your table using the
CICS Transaction Server macro library and link-edit it into your CICS load
library. If you get a return code greater than 4, remove the cause of the error
and reassemble.
Using the DFHCSDUP utility: To convert the table entries into resource
definitions, use the MIGRATE command of the DFHCSDUP offline utility program.
Figure 29 shows an example:
// EXEC DFHCSDUP,SIZE=DFHCSDUP
MIGRATE TABLE(DFHFCTC2)
/*
Figure 29. MIGRATE command to transfer the FCT to the CSD
Checking the output from MIGRATE: Migration may have produced some
messages. Read these warning messages carefully.
Figure 30 shows part of the MIGRATE output:
// EXEC DFHCSDUP,SIZE=DFHCSDUP
MIGRATE TABLE(DFHFCTC2)
DFHCA5120 I PRIMARY CSD OPENED; FILENAME: DFHCSD
DFHCA5143 I GROUP VSEFILES CREATED.
DFHCA5159 I FILE IESTRFL DEFINED IN GROUP VSEFILES
DFHCA5159 I FILE IESPRB DEFINED IN GROUP VSEFILES
DFHCA5159 I FILE IESCNTL DEFINED IN GROUP VSEFILES
DFHCA5159 I FILE IESROUT DEFINED IN GROUP VSEFILES
DFHCA5143 I GROUP PAYROLL CREATED.
DFHCA5159 I FILE FILEA DEFINED IN GROUP PAYROLL
DFHCA5159 I FILE FILEB DEFINED IN GROUP PAYROLL
DFHCA5172 W NO DEFINITION FOR FILE FILEC CREATED. DAM FILES ARE NOT SUPPORTED BY RDO.
DFHCA5159 I LSRPOOL LSRPOOL1 DEFINED IN GROUP PAYROLL
DFHCA5140 I TOTAL FILE DEFINITIONS CREATED: 6
DFHCA5140 I TOTAL LSRPOOL DEFINITIONS CREATED: 1
DFHCA5102 I WARNING MESSAGE(S) ISSUED WHILE PROCESSING MIGRATE COMMAND.
DFHCA5123 I PRIMARY CSD CLOSED; FILENAME: DFHCSD
DFHCA5107 I COMMANDS EXECUTED SUCCESSFULLY: 0 COMMANDS GIVING WARNING(S): 1 COMMANDS IN ERROR: 0
DFHCA5108 I COMMANDS NOT EXECUTED AFTER ERROR(S): 0
DFHCA5109 I END OF DFHCSDUP UTILITY JOB. HIGHEST RETURN CODE WAS: 4
Figure 30. Output from FCT MIGRATE command
From the output listing you can see the names of groups, files and LSRPOOLs
defined in the CSD.
Reassembling the DFHFCT source with MIGRATE=COMPLETE: If you wish to
load tables from the DFHFCT load library, you must code FCT=YES or FCT=xx
for a suffixed table in your system initialization parameters.
You do not need to edit your macro source to remove all migrated definitions
immediately after migrating. However, you will need to assemble your macro
source with MIGRATE=COMPLETE to retain an FCT to manage resources that
you cannot define using RDO. You should eventually remove from your FCT
source all the definitions that have been successfully migrated to the CSD.
44 VSE/ESA V2R4
The MIGRATE=COMPLETE option will suppress the assembly of RDO-eligible
FCT entries, whether or not they have actually been migrated to the CSD, so be
careful if you are intending to use the resulting FCT table for RDO-eligible
entries.
Figure 31 lists the DFHFCTC2 job with MIGRATE=COMPLETE we used:
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
TITLE 'DFHFCTC2 -- SUPPLIED WITH VSE/ESA'
PUNCH ' CATALOG DFHFCTC2.OBJ REP=YES'
DFHFCT TYPE=INITIAL,SUFFIX=C2,MIGRATE=COMPLETE
*
DFHFCT TYPE=GROUP,GROUP=VSEFILES
*
COPY IESZFCTO -- DATASET ENTRIES FOR VSE/ESA - OTHER PARTITION
*
DFHFCT TYPE=GROUP,GROUP=PAYROLL
*
FILEA DFHFCT TYPE=FILE, *
FILE=FILEA, *
ACCMETH=VSAM, *
.
.
.
*
FILEC DFHFCT TYPE=FILE, *
FILE=FILEC, *
ACCMETH=DAM, *
RECFORM=(UNDEFINED), *
BLKSIZE=88, *
LRECL=60, *
EXTENT=01
DFHFCT TYPE=SHRCTL, *
LSRPOOL=01, *
BUFFERS=(512(12),1024(12)), *
KEYLEN=10, *
STRNO=3
SPACE 3
DFHFCT TYPE=FINAL
END DFHFCTBA
/*
Figure 31. DFHFCT source with MIGRATE=COMPLETE
Initializing CICS after migration:
1. Use DFHCSDUP or RDO to ADD each group to a list (see Figure 20 on
page 37 and Figure 21 on page 37).
2. Use the GRPLIST parameter and the non-VSAM FCT (if any) in the DFHSIT
table or in the PARM field in CICS initialization (see Figure 22 on
page 37and Figure 23 on page 38).
3. Initialize the CICS partition.
Alternatively, you can wait until CICS has initialized, and then use RDO to
INSTALL the groups that you want CICS to use. For an example of the install
command, see Figure 24 on page 38.
A new file definition can be installed only if the existing file is closed and
disabled, or is closed and unenabled.
The RDO LSRPOOL definition is also new in CICS Transaction Server. Each
LSRPOOL is identified by its LSRPOOLid. You can now define separate index
Chapter 2. Installation and tailoring 45
and data buffer pools within a resource pool. Up to 15 LSRPOOLs can be
defined.
Figure 32 shows the RDO LSRPOOL definition:
V LSRPOOL(LSRPOOL1) GROUP(PAYROLL)
OBJECT CHARACTERISTICS CICS RELEASE = 0410
CEDA View Lsrpool( LSRPOOL1 )
Lsrpool : LSRPOOL1
Group : PAYROLL
DEscription :
Lsrpoolid : 01 1-15
Maxkeylength : 010 0-255
SHarelimit : 050 1-100
STrings : 003 1-255
DATA BUFFERS
DATA512 : 00012 3-32767
DATA1K : 00012 3-32767
DATA2K : 3-32767
DATA4k : 3-32767
DATA8k : 3-32767
DATA12k : 3-32767
DATA16k : 3-32767
DATA20k : 3-32767
DATA24k : 3-32767
DATA28k : 3-32767
DATA32k : 3-32767
INDEX BUFFERS
INDEX512 : 3-32767
INDEX1K : 3-32767
INDEX2K : 3-32767
INDEX4k : 3-32767
INDEX8k : 3-32767
INDEX12k : 3-32767
INDEX16k : 3-32767
INDEX20k : 3-32767
INDEX24k : 3-32767
INDEX28k : 3-32767
INDEX32k : 3-32767
SYSID=CIC2 APPLID=PRODCICS
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 32. RDO VIEW LSRPOOL - CEDA transaction
CICS Transaction Server supports the online definition of files.
The FILE definition can be used to describe the physical and operational
characteristics of a file to CICS file control.
The definition includes keywords that provide information about record
characteristics, types of operations allowed on file, recovery attributes and the
operations that are to be journaled.
Figure 33 on page 47 shows the RDO file definition:
46 VSE/ESA V2R4
V FILE(FILEA) GROUP(PAYROLL)
OBJECT CHARACTERISTICS CICS RELEASE = 0410
CEDA View File( FILEA )
File : FILEA
Group : PAYROLL
DEScription :
VSAM PARAMETERS
DSNAme :
Password : PASSWORD NOT SPECIFIED
Lsrpoolid : 01 1-15 | None
Catname :
DSNSharing : Noreqs Noreqs | Allreqs | Modifyreqs
STRings : 003 1-255
Nsrgroup :
SHr4access : Key Key | Rba
REMOTE ATTRIBUTES
REMOTESystem :
REMOTEName :
RECORDSize : 1-32767
Keylength : 1-255
INITIAL STATUS
STAtus : Enabled Enabled | Disabled | Unenabled
Opentime : Firstref Firstref | Startup
BUFFERS
DAtabuffers : 00004 2-32767
Indexbuffers : 00003 1-32767
DATATABLE PARAMETERS
Table : No No | Cics | User
Maxnumrecs : 16-16777215
DATA FORMAT
RECORDFormat : F V | F
OPERATIONS
Add : Yes No | Yes
Browse : Yes No | Yes
DELete : Yes No | Yes
REAd : Yes Yes | No
Update : Yes No | Yes
AUTO JOURNALLING
JOurnal : 02 No | 1-99
JNLRead : All None | Updateonly | Readonly | All
JNLSYNCRead : No No | Yes
JNLUpdate : Yes No | Yes
JNLAdd : Before None | Before | AFter | ALl
JNLSYNCWrite : Yes Yes | No
RECOVERY PARAMETERS
RECOVery : Backoutonly None | Backoutonly | All
Fwdrecovlog : No No | 1-99
SYSID=CIC2 APPLID=PRODCICS
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 33. RDO VIEW FILE - CEDA transaction
See CICS Transaction Server for VSE/ESA Resource Definition Guide for a
description of parameters.
Chapter 2. Installation and tailoring 47
2.3.7 Migrating the DFHTCT table
The DFHTCT macro must be used exclusively to define resources which are not
supported by RDO:
Sequential devices
Remote BTAM terminals for transaction routing
Logical device codes
You must define in the CSD:
VTAM-connected terminals
VSE consoles for use as CICS terminals
Multiregion operation (MRO) connections and sessions
Intersystem communication (ISC) links and sessions using LU6.1 and APPC
(LU6.2) protocols
Indirect connections
There is a special facility called autoinstall that can remove the need to migrate
specific resources. For more information, see 2.3.10, “Autoinstall of resources”
on page 62.
2.3.7.1 Migration steps
To perform the migration of your RDO-eligible table entries to RDO, you have to
do the following:
Edit your existing DFHTCT source.
Assemble and link-edit the edited source.
Process the link-edited table using the DFHCSDUP utility.
Check the output produced by the DFHCSDUP utility.
Use the DFHCSDUP ADD command to create a list of groups on your CSD.
Remove from your source all the table entries that have been migrated and
reassemble it.
Start up your system with the non-VTAM TCT (if any) and the list you have
created.
Editing your existing DFHTCT source: As previously mentioned, you must
reassemble your existing DFHTCT source using CICS Transaction Server macro
libraries. If your source is large, you might find it most convenient to assemble
small segments of the source individually, because each resource definition on
the CSD must belong to a CSD group. It is better to create many small groups
for your files rather than one large group. Try to limit groups to 100 resource
definitions.
Usually the definitions within a group have something in common. For example:
Keep all your TYPETERM definitions in one group.
Keep all your TERMINAL definitions by departmental function or
geographical location.
Keep AUTOINSTMODEL terminal definitions separately in a group.
48 VSE/ESA V2R4
You can specify the names to be given to groups of definitions generated from
your DFHTCT macros by adding:
DFHTCT TYPE=GROUP,GROUP=GROUPNAME
All definitions following a particular TYPE=GROUP macro statement are
migrated into the named group in the CSD file. A new TYPE=GROUP statement
overrides all previous ones; Figure 34 shows an example:
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
TITLE 'DFHTCTC2 VSE/ESA TCT'
PUNCH ' CATALOG DFHTCTC2.OBJ REPLACE=YES'
DFHTCT TYPE=INITIAL,SUFFIX=C2, *
ACCMETH=(VTAM,NONVTAM),MIGRATE=YES
* *********************************************************************
DFHTCT TYPE=SDSCI, *
DEVADDR=SYSIPT, *
DEVICE=2540, *
DSCNAME=READER
DFHTCT TYPE=SDSCI, *
DEVADDR=SYSLST, *
DEVICE=1403, *
DSCNAME=PRINTER
DFHTCT TYPE=LINE, *
ACCMETH=BSAM, *
INAREAL=80, *
TRMTYPE=CRLP, *
ISADSCN=READER, *
OSADSCN=PRINTER
DFHTCT TYPE=TERMINAL, *
TRMIDNT=SAMA, *
TRMTYPE=CRLP, *
TRMSTAT=TRANSCEIVE
* *********************************************************************
* L77A - VTAM TRMTYPE LUTYPE2 NETNAME - D72L301. *
* L77B - VTAM TRMTYPE 3270 NETNAME - D72L302. *
* L86P - VTAM NON-SNA 3270 PRINTER. NETNAME - P42L303. *
* *********************************************************************
*
DFHTCT TYPE=GROUP,GROUP=SUPPORT
*
VTRM1 DFHTCT TYPE=TERMINAL,TRMIDNT=L77A,TRMTYPE=LUTYPE2,TRMMODL=2, *
TIOAL=(1500,1920), *
BUFFER=1536, *
RELREQ=(NO,YES), *
FEATURE=(SELCTPEN,AUDALARM,DCKYBD), *
CHNASSY=YES, *
NETNAME=D72L301, *
PRINTTO=(VTRM3), *
GMMSG=YES, *
ACCMETH=VTAM,TCTUAL=32, *
TRMSTAT=(TRANSCEIVE)
VTRM2 DFHTCT TYPE=TERMINAL,TRMIDNT=L77B,TRMTYPE=3270,TRMMODL=2, *
CLASS=(CONV,VIDEO),TIOAL=1500,RELREQ=(NO,YES), *
FEATURE=(SELCTPEN,AUDALARM,DCKYBD), *
NETNAME=D72L302, *
PRINTTO=(VTRM3), *
GMMSG=YES, *
ACCMETH=VTAM,TCTUAL=32, *
TRMSTAT=(TRANSCEIVE)
VTRM3 DFHTCT TYPE=TERMINAL,TRMIDNT=L86P,TRMTYPE=3270P,TRMMODL=2, *
NETNAME=P42L303, *
RELREQ=(YES,YES), *
CLASS=(CONV,VIDEO),TIOAL=1500,TCTUAL=32, *
ACCMETH=VTAM,TRMSTAT=(TRANSCEIVE)
DFHTCT TYPE=FINAL
END ,
/*
Figure 34. DFHTCT source
For different types of macros, see CICS Transaction Server for VSE/ESA
Resource Definition Guide , Appendix G.
Chapter 2. Installation and tailoring 49
Assemble and link-edit the source: You must assemble your table using the
CICS Transaction Server macro library and link-edit it into your CICS load
library.
If you get a return code greater than 4, remove the cause of the error and
reassemble.
Using the DFHCSDUP utility: To convert the table entries into resource
definitions, use the MIGRATE command of the DFHCSDUP offline utility program;
Figure 35 shows an example:
// EXEC DFHCSDUP,SIZE=DFHCSDUP
MIGRATE TABLE(DFHTCTC2) TYPESGROUP(MYTYPE)
/*
Figure 35. MIGRATE command to transfer the TCT to the CSD
The TYPETERM definitions are put into the CSD group named in the
TYPESGROUP parameter.
The TYPETERM attributes of each DFHTCT TYPE=TERMINAL macro are checked
with existing TYPETERM definitions and if they do not match with any of these, a
new TYPETERM is added to the CSD.
The existing TYPETERMs checked are:
TYPETERMs in the group currently being created.
TYPETERMs in the group specified in the TYPESGROUP parameter of the
MIGRATE command.
Checking the output from MIGRATE: Migration may have produced some
messages. Read these warning messages carefully.
The output is shown in Figure 36 on page 51:
50 VSE/ESA V2R4
// EXEC DFHCSDUP,SIZE=DFHCSDUP
MIGRATE TABLE(DFHTCTC2) TYPESGROUP(MYTYPE)
DFHCA5120 I PRIMARY CSD OPENED; FILENAME: DFHCSD
DFHCA5280 I PROCESSING DEFINITIONS FROM LIBRARY MEMBER DFHRDTC2
DFHCA5143 I GROUP SUPPORT CREATED.
DFHCA5159 I TERMINAL L77A DEFINED IN GROUP SUPPORT
DFHCA5143 I GROUP MYTYPE CREATED.
DFHCA5159 I TYPETERM LU2000 DEFINED IN GROUP MYTYPE
DFHCA5159 I TERMINAL L77B DEFINED IN GROUP SUPPORT
DFHCA5159 I TYPETERM 3270000 DEFINED IN GROUP MYTYPE
DFHCA5159 I TERMINAL L86P DEFINED IN GROUP SUPPORT
DFHCA5159 I TYPETERM 3270P000 DEFINED IN GROUP MYTYPE
DFHCA5140 I TOTAL TERMINAL DEFINITIONS CREATED: 3
DFHCA5140 I TOTAL TYPETERM DEFINITIONS CREATED: 3
DFHCA5101 I MIGRATE COMMAND EXECUTED SUCCESSFULLY.
DFHCA5123 I PRIMARY CSD CLOSED; FILENAME: DFHCSD
DFHCA5107 I COMMANDS EXECUTED SUCCESSFULLY: 1 COMMANDS GIVING WARNING(S): 0 COMMANDS IN ERROR: 0
DFHCA5108 I COMMANDS NOT EXECUTED AFTER ERROR(S): 0
DFHCA5109 I END OF DFHCSDUP UTILITY JOB. HIGHEST RETURN CODE WAS: 0
Figure 36. Output from TCT MIGRATE command
From the output listing, you can see the names of the groups, terminals and
typeterms defined from library member DFHRDTC2 (which contains the
RDO-eligible definitions in command format).
Reassembling the DFHTCT source with MIGRATE=COMPLETE: If you need to
use a TCT, you must code TCT=xx (where xx is the suffix of your table) in the
DFHSIT macro.
You do not need to edit your macro source to remove all migrated definitions
immediately after migrating, but you do need to assemble your macro source
with MIGRATE=COMPLETE to retain a TCT to manage resources that you
cannot define using RDO. You should eventually remove from your TCT all the
definitions that have been successfully migrated to the CSD.
The DFHTCTC2 source with MIGRATE=COMPLETE is shown in Figure 37 on
page 52:
Chapter 2. Installation and tailoring 51
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
TITLE 'DFHTCTC2 VSE/ESA TCT'
PUNCH ' CATALOG DFHTCTC2.OBJ REPLACE=YES'
DFHTCT TYPE=INITIAL,SUFFIX=C2, *
ACCMETH=(VTAM,NONVTAM),MIGRATE=COMPLETE
* *********************************************************************
DFHTCT TYPE=SDSCI, *
DEVADDR=SYSIPT, *
DEVICE=2540, *
DSCNAME=READER
DFHTCT TYPE=SDSCI, *
DEVADDR=SYSLST, *
.
.
.
RELREQ=(YES,YES), *
CLASS=(CONV,VIDEO),TIOAL=1500,TCTUAL=32, *
ACCMETH=VTAM,TRMSTAT=(TRANSCEIVE)
DFHTCT TYPE=FINAL
END ,
/*
Figure 37. DFHTCT Source with MIGRATE=COMPLETE
Initializing CICS after migration:
1. Use DFHCSDUP or RDO to ADD each group to a list, (see Figure 20 on
page 37 and Figure 21 on page 37).
2. Use the GRPLIST parameter and the non-VTAM TCT (if any) in your system
initialization parameters or in the PARM field in CICS initialization (see
Figure 23 on page 38 and Figure 22 on page 37).
3. Initialize the CICS partition.
You must install some migrated definitions in the system when you initialize it.
If you are able to use RDO to manage all the your resources, you can abandon
your DFHTCT macro source and code TCT=NO in your system initialization
parameters.
To create a new VTAM terminal definition in the CSD, you use the DEFINE
TERMINAL command in the following:
Resource definition online (RDO): CEDA or CEDB transactions
DFHCSDUP offline utility
Autoinstall (see 2.3.10, “Autoinstall of resources” on page 62)
After the migration, the RDO Terminal Definition looks as shown in Figure 38 on
page 53:
52 VSE/ESA V2R4
V TE(L77A) GROUP(SUPPORT)
OBJECT CHARACTERISTICS CICS RELEASE = 0410
CEDA View TErminal( L77A )
TErminal : L77A
Group : SUPPORT
Description : . .
AUTINSTModel : No No | Yes | Only
AUTINSTName :
TERMINAL IDENTIFIERS
TYpeterm : LU2000
NEtname : D72L301
Consname : . .
REMOTESYSTem :
REMOTEName :
REMOTESYSNet : . .
Modename :
ASSOCIATED PRINTERS
PRINTER : L86P
PRINTERCopy : No No | Yes
ALTPRINTEr :
ALTPRINTCopy : No No | Yes
SPOOLTo :
PIPELINE PROPERTIES
POol :
TAsklimit : No No | 1-32767
OPERATOR DEFAULTS
OPERId :
OPERPriority : 000 0-255
OPERRsl : 0 0-24,...
OPERSecurity : 1 1-64,...
PRESET SECURITY
USERid :
NAtlang :
TERMINAL USAGES
TRansaction :
TErmpriority : 000 0-255
Inservice : Yes Yes | No
PRINTER DATA
SPOOLDest :
SPOOLPRTRsl : 00 0-24 | Public
SPOOLPRTTo : 00 0-59
SPOOLFcb : . .
PRINTEDmsg : No No | Yes
PRINTImmed : No No | Yes
SESSION SECURITY
SEcurityname :
ATtachsec : Local Local | Identify | Verify | Persistent
| Mixidpe
BINDPassword : PASSWORD NOT SPECIFIED
BINDSecurity : No No | Yes . .
USEDfltuser : No No | Yes . .
SYSID=CIC2 APPLID=PRODCICS
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 38. RDO VIEW TERMINAL - CEDA transaction
. .New parameters, see CICS Transaction Server for VSE/ESA Resource
Definition Guide .
To create a new typeterm definition in the CSD, you use the DEFINE TYPETERM
command in the following:
Chapter 2. Installation and tailoring 53
Resource definition online (RDO): CEDA or CEDB transactions
DFHCSDUP offline utility
Figure 39 and Figure 40 on page 55 show the RDO typeterm definition:
V TY(LU2000) GROUP(MYTYPE)
OBJECT CHARACTERISTICS CICS RELEASE = 0410
CEDA View TYpeterm( LU2000 )
TYpeterm : LU2000
Group : MYTYPE
DEScription : . .
RESOURCE TYPE
DEVice : LUTYPE2
TERmmodel : 2
SESsiontype :
PRINTErtype :
LDclist :
SHippable : No No | Yes
MAPPING PROPERTIES
PAGesize : 024 , 080 0-999
ALTPage : 000 , 000 0-999
ALTSUffix :
FMhparm : No No | Yes
OBOperid : No No | Yes
PAGING PROPERTIES
AUTOPage : No No | Yes
DEVICE PROPERTIES
DEFscreen : 024 , 080 0-999
ALTSCreen : , 0-999
APLKybd : No No | Yes
APLText : No No | Yes
AUDiblealarm : Yes No | Yes
COLor : No No | Yes
COPy : No No | Yes
DUalcasekybd : Yes No | Yes
EXtendedds : No No | Yes
HIlight : No No | Yes
Katakana : No No | Yes
LIghtpen : Yes No | Yes
Msrcontrol : No No | Yes
OBFormat : No No | Yes
PARtitions : No No | Yes
PRINTAdapter : No No | Yes
PROgsymbols : No No | Yes
VAlidation : No No | Yes
FOrmfeed : No No | Yes
HOrizform : No No | Yes
VErticalform : No No | Yes
TEXTKybd : No No | Yes
TEXTPrint : No No | Yes
Query : No No | Cold | All
OUtline : No No | Yes
SOsi : No No | Yes
BAcktrans : No No | Yes
+ CGcsgid : 00000 , 00000 0-65535
SYSID=CIC2 APPLID=PRODCICS
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 39. RDO VIEW TYPETERM (part 1) - CEDA transaction
54 VSE/ESA V2R4
V TY(LU2000) GROUP(MYTYPE)
OBJECT CHARACTERISTICS CICS RELEASE = 0410
CEDA View TYpeterm( LU2000 )
+ SESSION PROPERTIES
AScii : No No | 7 | 8
SENdsize : 01536 0-30720
RECEivesize : 00256 0-30720
BRacket : Yes Yes | No
LOGMODE :
LOGMODECom : No No | Yes . .
DIAGNOSTIC DISPLAY
ERRLastline : No No | Yes
ERRIntensify : No No | Yes
ERRColor : NO NO | Blue | Red | Pink | Green
| Turquoise | Yellow | NEutral
ERRHilight : No No | Blink | Reverse | Underline
OPERATIONAL PROPERTIES
AUTOConnect : No No | Yes | All
ATi : Yes No | Yes
TTi : Yes Yes | No
CReatesess : Yes No | Yes
RELreq : No No | Yes
DIscreq : Yes Yes | No
Nepclass : 000 0-255
SIgnoff : Yes Yes | No | Logoff
Xrfsignoff : Noforce Noforce | Force . .
MESSAGE RECEIVING PROPERTIES
ROutedmsgs : All All | None | Specific
LOGOnmsg : Yes No | Yes
APPLICATION FEATURES
BUildchain : Yes No | Yes
USerarealen : 032 0-255
Ioarealen : 01500 , 01920 0-32767
UCtran : No No | Yes | Tranid
RECOVERY
RECOVOption : Sysdefault Sysdefault | Clearconv | Releasesess
| Uncondrel | None
RECOVNotify : None None | Message | Transaction . .
SYSID=CIC2 APPLID=PRODCICS
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 40. RDO VIEW TYPETERM (part 2) - CEDA transaction
. .New parameters, see CICS Transaction Server for VSE/ESA Resource
Definition Guide .
2.3.8 Customizing the DFHDCT, DFHJCT and DFHPLT tables
You must reassemble all CICS control tables using CICS Transaction Server
macro libraries, including those control tables where there are no changes to the
macro externals in CICS Transaction Server.
You should review your resource definition table macros and make any
necessary changes before reassembling them; refer to the following table for
guidance.
Chapter 2. Installation and tailoring 55
Table 7. Changes to the DFHDCT, DFHJCT and DFHPLT macros
Changes to the DFHDCT macros
removed SEPASMB
TRNSUFX
RSL
RESIDNT
REUSE
new USERID
LENGTH
RMTNAME
SYSIDNT
LENGTH
Changes to the DFHJCT macros
removed BUFSUV
RSL
JOUROPT=INPUT
new ARCHJCL
changed JOUROPT=AUTOARCH
Changes to the DFHPLT macros
changed PROGRAM
new PROGRAM=DFHDELIM
2.3.8.1 Customizing DFHDCT
Modify and assemble your DFHDCT macro, after inserting the required CICS
entries (see the copy members DFH$DCTD and DFH$DCTR in the VSE/ESA
sublibrary PRD1.BASE) in the destination control table.
The following CICS transient data queues are obsolete:
CCSE and CCSO
CPLD and CPLI
CSSN and CSSM
The DFHDCTC2 source we used is shown in Figure 41 on page 57:
56 VSE/ESA V2R4
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
* *
TITLE 'DFHDCTC2 -- SUPPLIED WITH VSE/ESA'
PUNCH ' CATALOG DFHDCTC2.OBJ REP=YES'
DFHDCT TYPE=INITIAL,SUFFIX=C2
EJECT
*---------------------------------------------------------------------*
COPY DFH$DCTD - SDSCI ENTRY @HDC
*---------------------------------------------------------------------*
IESN DFHDCT TYPE=EXTRA, ALL THE MESSAGES COME THROUGH HERE *
DESTID=IESN, 'IESM' POINTS TO HERE *
DSCNAME=MSGUSR POINT TO THE CICS-SUPPLIED DEST
*---------------------------------------------------------------------*
COPY IESZDCT - CICS-REQUIRED AND VSE-ESA REQU. DESTS
*---------------------------------------------------------------------*
CSPW DFHDCT TYPE=INDIRECT, *
DESTID=CSPW, *
INDDEST=IEP1
*---------------------------------------------------------------------*
IEP1 DFHDCT TYPE=INTRA, FORWARD ALL MESSAGES DIRECTLY TO *
DESTID=IEP1, A TERMINAL SO USERS CAN LOOK AT THEM *
DESTFAC=(TERMINAL,CNSL), WRITE TO THE SYSTEM CONSOLE *
TRANSID=IEWR, *
TRIGLEV=1
*---------------------------------------------------------------------*
IEP2 DFHDCT TYPE=INTRA, KEEP ALL MSGS IN A FILE SO ONE *
DESTID=IEP2, CAN PRINT THEM USING CEMS *
DESTFAC=FILE
*---------------------------------------------------------------------*
DFHDCT TYPE=FINAL
END DFHDCTBA
/*
Figure 41. DFHDCT source
2.3.8.2 Customizing DFHJCT
If you want CICS to archive a disk journal data set automatically when it is
closed for output, you need to do the following:
1. Code the AUTOARCH option on the JOUROPT operand (see note . . in
Figure 43 on page 58).
2. With AUTOARCH, you must also code JTYPE=DISK2 (see note . . in
Figure 43 on page 58).
3. Define the journal archive control data set (DFHJACD). (For a sample
definition see Figure 13 on page 24).
4. Define a journal archive JCL sublibrary into which the users will have to
catalog their skeleton archiving jobs.
You can use the CICS-supplied sample JCL DFH$ARCH from the VSE/ESA
sublibrary PRD1.BASE. The following job shows how to do this:
// EXEC LIBR
DEFINE SUBLIB=PRD2.ARCHJCL REUSE=IMM
CONNECT SUBLIB=PRD1.BASE : PRD2.ARCHJCL
COPY DFH$ARCH.J
/*
5. Make sure that the VSE/ESA sublibrary containing skeleton JCL updated with
journal-specific information is in the LIBDEF concatenation chain; see
Figure 42 on page 58:
Chapter 2. Installation and tailoring 57
.
.
// OPTION SYSDUMPC
// LIBDEF *,SEARCH=(PRD2.CONFIG,PRD2.ARCHJCL,PRD1.BASED,PRD1.BASE, X
PRD2.PROD,PRD2.SCEECICD,PRD2.SCEECICS,PRD2.SCEEBASD, X
PRD2.SCEEBASE,PRD2.DBASE),PERM
// LIBDEF DUMP,CATALOG=SYSDUMP.F8
.
.
Figure 42. Sample of LIBDEF parameter in CICS startup
You can tailor the skeleton table DFHJCTSP in ICCF library 59 to meet your
requirements; see Figure 43:
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
TITLE 'DFHJCTC2 -- SUPPLIED WITH VSE/ESA'
PUNCH ' CATALOG DFHJCTC2.OBJ REP=YES'
DFHJCT TYPE=INITIAL,SUFFIX=C2
SPACE 3
*---------------------------------------------------------------------*
* SYSTEM JOURNALS: CICS.SYSTEM.LOG.A AND CICS.SYSTEM.LOG.B *
*---------------------------------------------------------------------*
DFHJCT TYPE=ENTRY, *
JFILEID=SYSTEM, *
BUFSIZE=2040, *
JOUROPT=(CRUCIAL), *
JTYPE=DISK2, *
OPEN=INITIAL, *
DEVADDR=(SYS019,SYS019)
*---------------------------------------------------------------------*
* USER JOURNALS: CICS.USER.JOURNAL.A AND CICS.USER.JOURNAL.B *
* WITH AUTOMATIC JOURNAL ARCHIVING *
*---------------------------------------------------------------------*
DFHJCT TYPE=ENTRY, *
JFILEID=02, *
BUFSIZE=2040, *
JOUROPT=(CRUCIAL,AUTOARCH), . . *
ARCHJCL=DFH$ARCH, *
JTYPE=DISK2, . . *
OPEN=INITIAL, *
DEVADDR=(SYS019,SYS019)
DFHJCT TYPE=FINAL
END
/*
Figure 43. DFHJCT source
You can see from the sample skeleton JCL in DFH$ARCH that the JCL you write
for use by the automatic journal archive submission program (DFHJASP) should
be written using symbolic parameters (those defined with an ampersand symbol,
like &JACDDSN in the sample). These parameters enable you to use a single
skeleton JCL source file to archive all the journals defined to your CICS
partitions. DFHJASP resolves the symbolic parameters into the correct values
for the journal it is archiving at the time it submits the job to POWER.
You must modify the information about catalog name and disk space if you will
use the sample DFH$ARCH, as shown in Figure 44 on page 59:
58 VSE/ESA V2R4
// EXEC LIBR,PARM='MSHP'
A S=PRD2.ARCHJCL
CATALOG DFH$ARCH.J EOD=!! REPLACE=YES
$$$$ JOB JNM=ARCHTEST,CLASS=0
// JOB ARCHTEST Archive PRODCICS Journal Dataset
// ON $RC GT 0 GOTO EOJ
$$/* Step1 : Check journal status
// DLBL DFHJACD,'&JACDDSN',,VSAM,CAT=VSESPUC . .
// EXEC DFHJACDU,PARM='CHECK JOURNAL=&JJ,DATASET=&D,DATE=&ODATE,TIME=&O*
TIME'
$$/*
$$/* Step2 : Copy journal to backup disk extent
$$/*
// DLBL DFHJRNL,'&JOURDSN'
// EXTENT SYS004,DOSRES . .
// ASSGN SYS004,DISK,VOL=DOSRES,SHR . .
// DLBL DFHJOUT,'&JOURDSN..BACKUP',0
// EXTENT SYS005,DOSRES,1,0,15000,150 . .
// ASSGN SYS005,DISK,VOL=DOSRES,SHR . .
// EXEC DFHJUP
* Optimum DFHJOUT Blksize (2 blocks per track):
* 3380 - 23476, 3390 - 27998, 9345 - 22928
* Default is 27998
CONTROL CNTL BLKSIZE=27998
OPTION COPY
END
$$/*
$$/* Step3 : Update journal status
// DLBL DFHJACD,'&JACDDSN',,VSAM,CAT=VSESPUC . .
// EXEC DFHJACDU,PARM='UPDATE JOURNAL=&JJ,DATASET=&D,DATE=&ODATE,TIME=5595c020
OTIME'
$$/*
/. EOJ
$$/&
$$$$ EOJ
!!
/*
Figure 44. DFH$ARCH sample
. .Catalog name of journal archive data set
. .Volume of journal files
. .DASD space to copy the journal files
2.3.8.3 Customizing PLTPI
The sequence of events during initialization has changed. There are three
stages in CICS initialization processing and two phases of program list table
(PLT) execution.
These two phases are separated by the inclusion of the following entry:
DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM
You can write programs to execute during the second and third stages of
initialization, but not during the first.
Programs listed before the PROGRAM=DFHDELIM entry are executed during
the second stage of initialization. The purpose of this stage is to enable user
exit programs needed during recovery. The user exit program should be defined
in an RDO group in the CICS startup GRPLIST.
Programs listed after the PROGRAM=DFHDELIM are executed during the third
stage of initialization. If these programs are used to enable user exits, the user
Chapter 2. Installation and tailoring 59
exit program must also be defined in an RDO group, or it must be capable of
being autoinstalled.
This phase corresponds to the single-phase PLTPI processing of previous
releases and does not require program resource definition.
The following is the DFHPLTP2 source was used:
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
PUNCH ' CATALOG DFHPLTP2.OBJ REP=YES'
DFHPLT TYPE=INITIAL,SUFFIX=P2
DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM
SPACE 3
*---------------------------------------------------------------------*
* COPY IESZPLTI COPY VSE/ESA INCL. VSE/ICCF ENTRIES
*---------------------------------------------------------------------*
SPACE 3
DFHPLT TYPE=FINAL
END
/*
Figure 45. DFHPLTP2 Source - initialization
For additional information see also 5.2.2, “Program list table (PLT) programs” on
page 148.
2.3.8.4 Customizing PLTSD
In shutdown there are also two phases. These phases are separated by the
inclusion of the following entry:
DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM
Programs listed before the PROGRAM=DFHDELIM entry are executed during
the first quiesce stage of shutdown
Programs listed after the PROGRAM=DFHDELIM entry are executed during the
second quiesce stage of shutdown. The second quiesce stage does not require
program resource definitions, because they will be autoinstalled by CICS.
Figure 46 shows the DFHPLTS2 source we used:
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
PUNCH ' CATALOG DFHPLTS2.OBJ REP=YES'
DFHPLT TYPE=INITIAL,SUFFIX=S2
SPACE 3
*---------------------------------------------------------------------*
* COPY IESZPLTS COPY VSE/ESA INCL. VSE/ICCF ENTRIES
*---------------------------------------------------------------------*
* FOLLOWING ENTRY FOR PROGRAM DFH0STAT WILL CAUSE PRINTING *
* OF STATISTICS DURING SHUT DOWN OF CICS TS. PLEASE ACTIVATE *
* THE ENTRY ONLY AFTER HAVING FOLLOWING PROGRAMS AVAILABLE: *
* DFH0STAT, DFH$STAS AND DFH$STCN. *
* YOU HAVE TO COMPILE THEM AND TO DEFINE THEM IN THE CSD FILE. *
* ALL THREE PROGRAMS HAVE TO BE DEFINED WITH EXECKEY=CICS. *
*---------------------------------------------------------------------*
* DFHPLT TYPE=ENTRY,PROGRAM=DFH0STAT
DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM
*---------------------------------------------------------------------*
DFHPLT TYPE=FINAL
END
/*
Figure 46. DFHPLTS2 source - shutdown
60 VSE/ESA V2R4
2.3.9 Tailoring the CICS start-up jobstream
We used the the job SKCICS2 supplied in ICCF library 59 to start our second
CICS system in partition F8.
Figure 47 shows the console log of CICS Transaction Server startup:
F8 0008 // JOB CICS2 STARTUP OF SECOND CICS WITHOUT ICCF
DATE 04/07/1999, CLOCK 18/04/02
F8 0008 LOG
F8 0008 ID (PARAMETERS SUPPRESSED)
F8 0008 NOLOG
F8 0008 * WAITING FOR VTAM TO COME UP
F8 0008 DFHPA1101 PRODCICS DFHSITC2 IS BEING LOADED.
F8 0008 DFHPA1108 PRODCICS DFHSITC2 HAS BEEN LOADED. (GENERATED AT: MM/DD=
03/25 HH:MM= 12:30).
F8 0008 DFHPA1100 PRODCICS OVERRIDE PARAMETERS FROM JCL EXEC STATEMENT:
APPLID=PRODCICS,START=AUTO,SI
F8 0008 DFHPA1102 PRODCICS OVERRIDE PARAMETERS FROM SYSIPT:
F8 0008 DFHPA1927 PRODCICS SIT=C2,STATRCD=OFF,SVA=NO
F8 0008 DFHPA1103 PRODCICS END OF FILE ON SYSIPT.
F8 0008 DFHTR0103 TRACE TABLE SIZE IS 80K
F8 0008 DFHSM0122I PRODCICS LIMIT OF DSA STORAGE BELOW 16 MB IS 5,120 K.
F8 0008 DFHSM0123I PRODCICS LIMIT OF DSA STORAGE ABOVE 16 MB IS 25 M.
F8 0008 DFHSM0113I PRODCICS STORAGE PROTECTION IS NOT ACTIVE.
F8 0102 DFHDM0101I PRODCICS CICS IS INITIALIZING.
F8 0103 DFHXS1100I PRODCICS SECURITY INITIALIZATION HAS STARTED.
F8 0103 DFHSI1500 PRODCICS CICS STARTUP IS IN PROGRESS FOR CICS TRANSACTION
SERVER VERSION 1.1.0
F8 0103 DFHSI1501I PRODCICS LOADING CICS NUCLEUS.
F8 0103 DFHXS1105 PRODCICS RESOURCE PROFILES FOR CLASS TCICSTRN HAVE BEEN
BUILT.
F8 0103 DFHXS1103I PRODCICS DEFAULT SECURITY FOR USERID CICSUSER HAS BEEN
ESTABLISHED.
F8 0103 DFHXS1101I PRODCICS SECURITY INITIALIZATION HAS ENDED.
F8 0103 DFHMN0105I PRODCICS USING DEFAULT MONITORING CONTROL TABLE.
F8 0103 DFHMN0110I PRODCICS CICS MONITORING IS INACTIVE.
F8 0103 DFHSI1502I PRODCICS CICS STARTUP IS WARM.
F8 0103 DFHSI1503I PRODCICS TERMINAL DATA SETS ARE BEING OPENED.
F8 0103 DFHDU0304I PRODCICS TRANSACTION DUMP DATA SET DFHDMPB OPENED.
F8 0103 DFHSI1510I PRODCICS JOURNAL CONTROL SUBTASK IS BEING ATTACHED/ENTERED.
F8 0103 DFHCP0101I PRODCICS CPI INITIALIZATION HAS STARTED.
F8 0103 DFHPR0104I PRODCICS PARTNER RESOURCE MANAGER INITIALIZATION HAS
STARTED.
F8 0103 DFHAI0101I PRODCICS AITM INITIALIZATION HAS STARTED.
F8 0103 DFHTD0100I PRODCICS TRANSIENT DATA INITIALIZATION HAS STARTED.
F8 0103 DFHTS0100I PRODCICS TEMPORARY STORAGE INITIALIZATION HAS STARTED.
F8 0103 DFHSI1516I PRODCICS OPENING JOURNAL DATA SETS.
F8 0103 DFHFC0100I PRODCICS FILE CONTROL INITIALIZATION HAS STARTED.
F8 0103 DFHFC0101I PRODCICS FILE CONTROL INITIALIZATION HAS ENDED.
F8 0103 DFHTS0101I PRODCICS TEMPORARY STORAGE INITIALIZATION HAS ENDED.
F8 0103 DFHTD0101I PRODCICS TRANSIENT DATA INITIALIZATION HAS ENDED.
F8 0104 DFHJC4508 PRODCICS CICS SYSTEM LOG. PRIMARY DATA SET NOW RECEIVING
OUTPUT ON 0150
F8 0104 DFHJC4508 PRODCICS CICS JOURNAL 02. PRIMARY DATA SET NOW RECEIVING
OUTPUT ON 0150
F8 0103 DFHJC4500 PRODCICS 02 OF 02 JOURNALS SUCCESSFULLY OPENED
F8 0103 DFHCP0102I PRODCICS CPI INITIALIZATION HAS ENDED.
F8 0103 DFHPR0105I PRODCICS PARTNER RESOURCE MANAGER INITIALIZATION HAS ENDED.
F8 0103 DFHAI0102I PRODCICS AITM INITIALIZATION HAS ENDED.
F8 0103 DFHAP1203I PRODCICS LANGUAGE ENVIRONMENT FOR VSE/ESA IS BEING
INITIALIZED.
F8 0103 DFHSI1517 PRODCICS CONTROL IS BEING GIVEN TO CICS.
Figure 47. Output from CICS startup
Chapter 2. Installation and tailoring 61
2.3.9.1 System initialization parameter descriptions
There are a number of CICS system initialization parameters that you cannot
define in the DFHSIT macro. These parameters are:
CDSASIZE={0K|number}
CHKSTRM={CURRENT|NONE}
ECDSASZE={0K|number}
ERDSASZE={0K|number}
ESDSASZE={0K|number}
EUDSASZE={0K|number}
JSTATUS=RESET
NEWSIT={YES|NO}
PRVMOD={name|(name,name,...name)}
RDSASZE={0K|number}
SDSASZE={0k|number}
SIT=xx
SPCTRxx={(1[ ,2][,3])|ALL|OFF}
START=LOGTERM
START=(option,ALL)
SNNTRXX={(1[ ,2][,3])|ALL|OFF
UDSASZE={0K|number}
These parameters may only be defined by:
The PARM parameter of the EXEC DFHSIP statement
The SYSIPT data set defined in the startup job stream
Through the system operator's console
For information about coding system initialization parameters in PARM, SYSIPT,
or at the console, see CICS Transaction Server for VSE/ESA System Definition
Guide .
2.3.10 Autoinstall of resources
Autoinstall can be used for the following resources:
VTAM terminals
APPC (LU6.2) connections
Programs
Mapsets
Partitionsets
With autoinstall, you do not need to define and install every resource that you
intend to use. Instead, CICS dynamically creates and installs a definition for you
when a resource is requested. You must provide at least one model resource
definition for each type of resource to be autoinstalled.
62 VSE/ESA V2R4
When a resource is requested which does not have an installed definition, CICS
creates a definition based on what you have specified in the model.
2.3.10.1 Program autoinstall
Autoinstall for programs, mapsets and partitionsets brings several benefits:
Reduced system administration costs
Saving in virtual storage within the CICS address space
Faster COLD restart
Possible improvements on WARM and EMER restart
Program autoinstall steps:
1. Decide whether your programs are eligible for autoinstall.
Programs that cannot be autoinstalled:
The program autoinstall control program
The terminal autoinstall control program
The connection autoinstall control program
2. Decide which programs to autoinstall and what to do with existing program
and mapset definitions in the CSD.
You can use a mixture of RDO and autoinstall.
3. Decide whether you want to use program autoinstall with or without
cataloging.
If you decide to have autoinstalled definitions recorded in the CICS catalog,
specify this by using the PGAICTLG SI, or the SET SYSTEM SPI, or the CEMT
parameter.
4. Enable autoinstall for programs.
The system initialization parameters relating to program autoinstall are:
PGAICTLG Whether an autoinstalled program definition is cataloged or
not
PGAIPGM Whether the program autoinstall function is active or
inactive
PGAIEXIT The name of the program autoinstall exit
You can also enable autoinstall for programs by using the EXEC CICS or
CEMT INQUIRE|SET SYSTEM command.
Figure 48 shows the following is part of the DFHSITC2 table:
.
.
NATLANG=E, (E,X) X = S,G,... NLS *
PGAICTLG=ALL, UPDATE AUTOINSTALL PGM DEFINING*
PGAIEXIT=DFHPGADX, PGM AUTOINSTALL EXIT *
PGAIPGM=ACTIVE, PGM AUTOINSTALL ACTIVE *
PGCHAIN=X/, BMS CHAINING COMMAND *
.
.
Figure 48. Sample of DFHSIT with program autoinstall parameters
5. Define the CSPL transient data queue.
Chapter 2. Installation and tailoring 63
Define the CSPL transient data queue, if you want to log messages
associated with autoinstall for programs.
In copybook IESZDCT, we have the definition shown in Figure 49:
CSPL DFHDCT TYPE=INDIRECT, MESSAGES FROM PROGRAM MANAGER *
DESTID=CSPL, DEFINE THE DESTINATION ID *
INDDEST=IESL SEND IT THROUGH THE VSE/ESA QUEUE
Figure 49. CSPL queue in the IESZDCT copybook
6. Create your model program definitions.
The purpose of a model definition is to provide CICS with one definition that
can be used for all programs with the same properties.
If you do not want to use your own definitions, you can use the
CICS-supplied model definitions in group DFHPGAIP:
DFHPGAPG for programs, shown in Figure 50:
OBJECT CHARACTERISTICS CICS RELEASE = 0410
CEDA View PROGram( DFHPGAPG )
PROGram : DFHPGAPG
Group : DFHPGAIP
DEscription : DEFAULT PROGRAM FOR PROGRAM AUTOINSTALL
Language : CObol | Assembler | C | Pli
RELoad : No No | Yes
RESident : No No | Yes
USAge : Normal Normal | Transient
USEsvacopy : No No | Yes
Status : Enabled Enabled | Disabled
RSl : 00 0-24 | Public
Cedf : Yes Yes | No
DAtalocation : Below Below | Any
EXECKey : User User | Cics
REMOTE ATTRIBUTES
REMOTESystem :
REMOTEName :
Transid :
EXECUtionset : Fullapi Fullapi | Dplsubset
SYSID=CIC1 APPLID=DBDCCICS
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 50. RDO VIEW PROGRAM(DFHPGAPG) - CEDA transaction
DFHPGAMP for mapsets, as shown in Figure 51 on page 65:
64 VSE/ESA V2R4
OBJECT CHARACTERISTICS CICS RELEASE = 0410
CEDA View Mapset( DFHPGAMP )
Mapset : DFHPGAMP
Group : DFHPGAIP
Description : DEFAULT MAPSET FOR PROGRAM AUTOINSTALL
REsident : No No | Yes
USAge : Normal Normal | Transient
USEsvacopy : No No | Yes
Status : Enabled Enabled | Disabled
RSl : 00 0-24 | Public
SYSID=CIC1 APPLID=DBDCCICS
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 51. RDO VIEW MAPSET(DFHPGAMP) - CEDA transaction
DFHPGAPT for partitionsets, as shown in Figure 52:
OBJECT CHARACTERISTICS CICS RELEASE = 0410
CEDA View PARTItionset( DFHPGAPT )
PARTItionset : DFHPGAPT
Group : DFHPGAIP
Description : DEFAULT PARTITIONSET FOR PROGRAM AUTOINSTALL
REsident : No No | Yes
USAge : Normal Normal | Transient
USEsvacopy : No No | Yes
Status : Enabled Enabled | Disabled
RSl : 00 0-24 | Public
SYSID=CIC1 APPLID=DBDCCICS
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 52. RDO VIEW PARTITIONSET(DFHPGAPT) - CEDA transaction
7. Design and write an autoinstall control program.
The purpose of the autoinstall control program is to provide CICS with the
extra information it needs to complete an autoinstall request, such as the
autoinstall model name.
You can write your autoinstall program in any language supported by CICS,
with full access to the CICS application programming interface.
Chapter 2. Installation and tailoring 65
The following sample programs are supplied by CICS:
DFHPGADX, in assembler language
DFHPGAHX, in C language
DFHPGALX, in PL/I language
DFHPGAOX, in COBOL language
The source for these programs and the executable form of the assembler
version are supplied in the VSE/ESA sublibrary PRD1.BASE.
2.3.10.2 VTAM autoinstall
VTAM autoinstall steps:
1. Decide whether your terminals are eligible for autoinstall.
Terminals that cannot be autoinstalled:
Pipeline terminals
Automatic teller machines (3614 and 3624)
Non-VTAM resources
VTAM logical unit type 6.1 ISC and MRO sessions
2. Decide whether to use autoinstall.
You are likely to benefit from autoinstall if any of the following apply to your
system:
A significant number of VTAM terminals
Frequent changes to your network
Many VTAM terminals logged off much of the time
Many VTAM terminals using other applications much of the time
Many VTAM terminals that need access to multiple, but unconnected
CICS systems
3. Decide which devices to autoinstall.
This decision depends on how you use your VTAM terminals. An autoinstall
logon is slower than a logon to a terminal individually defined to CICS, so if
you switch continually between applications and have to log on to CICS
frequently, you may require individual definitions for some terminals.
There are also special issues that you should consider:
Automatic transactions initiation
The TCT user area (TCTUA)
The terminal list table (TLT)
Transaction routing
Autoinstall and output-only devices
For more information, see CICS Transaction Server for VSE/ESA Resource
Definition Guide , Chapter 9.
4. Create your TYPETERM and model TERMINAL definitions.
Define an autoinstall model for each different kind of terminal to be
autoinstalled. Try to keep the number of definitions to a minimum, so that the
autoinstall control program can be as simple as possible.
66 VSE/ESA V2R4
CICS supplies some TERMINAL and TYPETERM definitions in CSD group
DFHTERM and DFHTYPE; for more information see CICS Transaction Server
for VSE/ESA Resource Definition Guide , Appendix B.
The most important parameter in terminal definition is AUTINSTMODEL.
5. Redefine DFHZCQ.
The Terminal control install interface program (DFHZCQ) should be redefined
as RESIDENT(YES). If you use the DFHZCQ from the CICS-supplied group
DFHSPI, it is already defined with RESIDENT(YES) parameter, as shown in
Figure 53:
V PROGRAM(DFHZCQ) GROUP(DFHSPI)
OBJECT CHARACTERISTICS CICS RELEASE = 0410
CEDA View PROGram( DFHZCQ )
PROGram : DFHZCQ
Group : DFHSPI
DEscription :
Language : Assembler CObol | Assembler | C | Pli
RELoad : No No | Yes
RESident : Yes No | Yes
USAge : Normal Normal | Transient
USEsvacopy : No No | Yes
Status : Enabled Enabled | Disabled
RSl : 00 0-24 | Public
Cedf : No Yes | No
DAtalocation : Any Below | Any
EXECKey : Cics User | Cics
REMOTE ATTRIBUTES
REMOTESystem :
REMOTEName :
Transid :
EXECUtionset : Fullapi Fullapi | Dplsubset
SYSID=CIC1 APPLID=DBDCCICS
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 53. RDO VIEW PROGRAM(DFHZCQ) - CEDA transaction
6. Ensure that your VTAM LOGMODE table entries are correct.
When a VTAM terminal logs on to CICS, the VTAM LOGMODE is used by
autoinstall to find matching CICS terminal type definitions. The following
must correspond:
Physical terminal characteristics
VTAM session parameters
CICS terminal type definition
7. Design and write an autoinstall control program.
The autoinstall control program is invoked by CICS every time there is a
valid request for a TCT entry to be autoinstalled, and every time an
autoinstalled TCT entry is deleted.
The following sample programs are supplied:
DFHZATDX, in assembler language
DFHZATDY, in assembler language
Chapter 2. Installation and tailoring 67
IESZATDX, in assembler language
DFHZCTDX, in COBOL language
DFHZDTDX, in C language
DFHZPTDX, in PL/I language
The source for the IESZATDX program is supplied in VSE/ICCF library 59,
and the others programs are supplied in the VSE/ESA sublibrary PRD1.BASE.
You can have only one autoinstall control program active at one time for
terminals and connections. We recommend to use IESZATDX. The
DFHZATDY and IESZATDX programs provide the same function for terminal
autoinstall as DFHZATDX, but also provide functions to autoinstall APPC
connections. In addition IESZATDX provides support for LU6.2 APPC
sessions.
8. Enable terminal autoinstall.
The system initialization parameters relating to terminal autoinstall are:
AIEXIT The name of the autoinstall program exit.
AIQMAX Maximum number of terminals that can be queued
concurrently.
AILDELAY The time interval that will elapse after an autoinstall
terminal logs off before its TCTTE is deleted.
AIRDELAY The time interval that will elapse after emergency restart
before terminal entries will be deleted if they are not in
session.
You can also enable autoinstall for terminals using EXEC CICS or CEMT
INQUIRE|SET AUTOINSTALL commands.
9. Define the CADL transient data queue.
Define the CADL transient data queue, if you want to record each installation
and each deletion of TCT entries. Message DFHZC6987 is useful for
indicating which model came closest to the one being chosen when a null
list of models is passed to the autoinstall control program.
In copybook IESZDCT, we have the definition shown in Figure 54:
CADL DFHDCT TYPE=INDIRECT, CEDA COMMAND LOGGING COMES HERE *
DESTID=CADL, DEFINE THE DESTINATION ID *
INDDEST=IESL SEND IT THROUGH THE VSE/ESA QUEUE
Figure 54. CADL queue in the IESZDCT copybook
2.3.10.3 APPC autoinstall
Autoinstall for APPC connections brings several benefits:
The COLD, WARM and EMER restarts are faster.
These are fewer CSD definitions to manage.
Less storage is taken up by unused definitions.
APPC autoinstall steps:
1. Decide whether to use autoinstall for connections.
Possible restrictions that you should be aware of are as follows:
68 VSE/ESA V2R4
If you use security for connections
If you use persistent sessions support
If you need to recover an autoinstalled connection after WARM or EMER
restarts.
2. Decide which sessions to autoinstall.
You can use autoinstall for CICS-to-CICS connections, but it is intended
primarily for workstations.
3. Create your model connection definitions.
Any installed connection definition can be used as a “template” for an
autoinstalled connection, but you should use an installed connection
definition that is not in use, because the definition is locked while CICS
copies it.
4. Design and write an autoinstall control program.
CICS supplies a sample control program (DFHZATDY) for connections
autoinstall, and VSE/ESA supplies a sample control program (IESZATDX).
5. Enable autoinstall for connections.
Autoinstall for connections are enabled when you enable autoinstall for
terminals; see 2.3.10.2, “VTAM autoinstall” on page 66.
If you want to disable autoinstall for connections, set the model connection
out of service by using the CEMT or EXEC CICS SET CONNECTION
OUTSERVICE command.
2.3.11 Additional considerations
The following discusses additional changes introduced with CICS TS.
2.3.11.1 Obsolete tables
The following tables are obsolete in the CICS Transaction Server:
ALT In the CICS Transaction Server, the program management
component is reengineered to such an extent that the virtual
storage benefits previously offered by the Application Load
Table are superseded.
NLT There is no longer any need to optimize the working set
because of the internal restructuring of CICS.
SNT The Sign-on Table is obsolete because of the removal of CICS
internal security in CICS Transaction Server.
PCT and PPT These resources are installed only by using the CSD. However,
the DFHPCT and DFHPPT table macros are retained for the
purpose of migrating existing PCT and PPT definitions to the
CSD.
2.3.11.2 The new TRANCLASS definition
TRANCLASS is a new resource object which allows you to associate scheduling
and dispatching priorities with TRANSACTION definitions. This replaces and
extends the CMXT parameter.
By putting your transactions into transaction classes, you can control how CICS
dispatches tasks. Transaction classes become RDO-defined resources in CICS
Chapter 2. Installation and tailoring 69
Transaction Server. This allows you to have as many transaction classes as you
need.
Transaction classes are now identified by eight-character names instead of the
numbering scheme used on the now-obsolete CMXT system initialization
parameter.
For compatibility with your old system definition, you can leave your old
transaction definitions as they are, with TCLASS numbers defined, and allow
CICS to assign the transactions to the corresponding TRANCLASS names.
Group DFHTCL contains definitions for the ten CICS-defined TClasses (named
DFHTCL01 through DFHTCL10) provided as replacements for the ten numbered
TClasses that used to be defined on the CMXT parameter.
To ensure that the default TRANCLASS names have the same effect as your
current TCLASS members, you should copy and modify the DFHTCLxx
definitions, specifying values that correspond to your old system values.
Figure 55 shows what all supplied RDO TRANCLASS definitions look like:
OBJECT CHARACTERISTICS CICS RELEASE = 0410
CEDA View TRANClass( DFHTCL01 )
TRANClass : DFHTCL01
Group : DFHTCL
Description : Replacement for CMXT class 1
CLASS LIMITS
Maxactive : 001 0-999
Purgethresh : No No | 1-1000000
SYSID=CIC2 APPLID=PRODCICS
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 55. RDO VIEW TRANCLASS - CEDA transaction
2.3.11.3 Shared data tables
CICS Transaction Server extends CICS file control by introducing shared data
tables.
Shared data tables makes the data tables facility introduced in CICS/VSE 2.2
obsolete and by exploiting ESA/390 data spaces and cross memory services,
brings several advantages.
Regardless of how many partitions will share the data table, CICS stores records
for a data table in a VSE/ESA data space. The data space is created when the
first file to be defined as a data table is opened in the partition. The data space
is used by all CICS data tables that are owned by that partition, and it is retained
until CICS is shut down in that partition.
No changes are required to the file definitions for existing data tables. You may
need to increase the size of the data space available in the VSE system. The
data space for shared data tables is acquired in units of 16 MB. For information
70 VSE/ESA V2R4
about using shared data tables, see CICS Transaction Server for VSE/ESA
Shared Data Tables Guide .
Chapter 2. Installation and tailoring 71
72 VSE/ESA V2R4
Chapter 3. Security
CICS internal security is no longer available in the CICS Transaction Server for
VSE/ESA R1. Security in CICS is now provided through the services of an
external security manager (ESM) that conforms to the VSE/ESA system
authorization facility (SAF) interface. To provide the necessary security for CICS
resources, CICS TS issues RACROUTE calls via the VSE/ESA V2R4 SAF
interface to route authorization requests to an ESM within CICS transaction
processing.
You can choose between two levels of external security manager:
Basic security manager (BSM)
The BSM is provided the with VSE/ESA Version 2 Release 4 system package.
The BSM is a limited-function ESM, and provides only sign-on and
transaction-attach security.
Full-function external security manager (ESM)
A full-function ESM is provided by an independent software vendor (ISV) that
conforms to the SAF interface, and which provides support for all the various
security checks that are necessary to protect your application programs and
CICS system components from misuse. The full-function ESM must be
installed separately.
The following sections describe the security implications of migrating to the CICS
Transaction Server for VSE/ESA R1. They outline the basic security support
provided by the BSM in VSE/ESA Version 2 Release 4 and how the CICS TS
makes use of this support. It only references items of function and support as
they relate to an ESM. Only security changes in the VSE/ESA V2R4 system
relating to the CICS TS are discussed in this document.
3.1 VSE/ESA Version 2 Release 4 security
Security changes made in VSE/ESA Version 2 Release 4 are mainly due to the
replacement of CICS/VSE by the CICS Transaction Server for VSE/ESA R1.
Security must now be implemented with an external security manager, either the
basic security manager (BSM) or a vendor product.
3.1.1 VSE/ESA V2R4 security option changes
3.1.1.1 IPL SYS command
The IPL SYS command has been extended to add the E S M = option,
SERVPART= option and the SEC=RECOVER option. The VSE/ESA Function
Selection dialog for tailoring the IPL procedure has been updated to reflect these
new options. Figure 56 on page 74 shows an example of these options.
© Copyright IBM Corp. 1999 73
TAS$ICM1 TAILOR IPL PROCEDURE: SYS COMMAND
Enter the required data and press PF5=PROCESS
BUFLD........................ 1 Load printer buffers? 1=yes, 2=no
CHANQ........................ _____ Number of channel queue entries
DASDFP....................... 1 DASD file protection? 1=yes, 2=no
JA........................... 1 Job accounting? 1=yes, 2=no
SUBLIB....................... ____ Number of sublibraries
VMCF......................... _ CMS-VSE console interface? 1=yes,
2=no, or blank for system default
SEC.......................... 2 access control security? 1=yes,2=no, . .
3=NOTAPE, 4=RECOVER
ESM.......................... ________ Name of the ESM initialization phase . .
SERVPART..................... FB Security server partition (F1,F2, ...
FB). .
PF1=HELP 2=REDISPLAY 3=END 5=PROCESS
8=FORWARD
Figure 56. Tailor IPL SYS parameter
. . New option SEC=RECOVER switches off all security completely. Use
this option only for problem determination.
. . New option to specify the ESM initialization phase name. This will be
found in the ESM installation documentation. If nothing is specified,
BSM will be activated.
. . New option to specify the partition that the Security Server is running.
If an ESM is specified, this is the partition of the Security Server
required by the ESM. See the ESM installation documentation for
details.
3.1.1.2 DTSECTAB
The DTSECTAB has changed in VSE/ESA Version 2 Release 4. Security-related
user profiles from VSE/ESA Interactive Interface (II) are not stored in DTSECTAB
now, but are in VSE.CONTROL.FILE. You must redefine your current VSE/ESA
Interactive Interface (II) users to the VSE.CONTROL.FILE.
The user IDs FORSEC and DUMMY are the only user IDs stored in both the
DTSECTAB and the VSE.CONTROL.FILE. These IDs are used at system startup
and should never be removed.
To migrate the DTSECTAB user profiles, use either the Maintain User Profiles
dialog as discussed in 3.2.1.2, “Maintaining Users with the Interactive Interface”
on page 88 or the batch utility IESBLDUP. The IESBLDUP utility is discussed in
VSE/ESA System Utilities . It can also be used to create a status report of your
current system's users.
Note: The access control concept for resources defined in the DTSECTAB has
not changed with VSE/ESA V2R4.
74 VSE/ESA V2R4
3.1.1.3 VSE.CONTROL.FILE
All user profiles are stored in the VSE.CONTROL.FILE. User profiles from
VSE/ESA Interactive Interface (II) and from the old CICS SNT table are stored in
the VSE.CONTROL.FILE. The Maintain User Profiles dialogs have been updated
to handle the defining of security-related information in the user profiles.
The user IDs FORSEC and DUMMY are the only user IDs stored in both the
DTSECTAB and the VSE.CONTROL.FILE. These IDs are used at system startup
and should never be removed.
There is a new Security Server to access this file and handle sign-on security.
Refer to 3.2.1.2, “Maintaining Users with the Interactive Interface” on page 88 for
defining users to this file.
Do not copy an old VSE.CONTROL.FILE into a VSE/ESA V2R4 VSE.CONTROL.FILE
as the file has changed. Use the IESBLDUP utility to migrate.
3.1.1.4 DTSECTXN
A new file, DTSECTXN, has been created to handle the CICS TS transaction
security definitions. Refer to 3.2.5, “CICS TS transaction-attach security” on
page 95 for a full description of this file.
3.1.1.5 VSE/POWER
VSE/POWER security has been enhanced, providing spool access protection for
the POWER queues. This support applies to the BSM as well as ESM.
3.1.2 Basic security manager (BSM)
The BSM is part of VSE/ESA V2R4. It provides the minimum sign-on security and
transaction-attach security for CICS TS. The BSM is always active during the
startup of your system. After startup, control may be passed to an ESM for full
security.
The BSM requires the user profiles in the VSE.CONTROL.FILE, the CICS TS
transaction security information in the DTSECTXN table and the resource control
information for files, libraries, sublibraries and members in the DTSECTAB. The
BSM uses a Security Server to do security checking from these files.
3.1.3 Security Server
The Security Server is part of the BSM. It can run in any static partition. The
Security Server controls the access to the VSE.CONTROL.FILE.
3.1.3.1 Initial VSE/ESA V2R4 install and the Security Server
On the initial install of the VSE/ESA V2R4 you are asked if you want to run with
security ON; refer to Figure 57. Reply YES now in the install process as it is
easier to have the system set up the security facilities and turn it off than to
reply NO and set up the security facilities later.
BG 0000 IESI0079D DO YOU WANT TO RUN YOUR SYSTEM WITH SECURITY ON?
YES/NO
0 yes . .
Figure 57. Initial Install option
Chapter 3. Security 75
. . Reply YES for easier install of BSM.
The Security Server runs in FB by default in the installation. Before the startup
of POWER, you will see the SECSERV job startup; refer to Figure 58.
FB 0011 // JOB SECSERV
DATE 03/19/1999, CLOCK 11/55/45
FB 0058 4228I FILE IJSYSCT OPEN ERROR X'B4'(180) CAT=..N/A.. . .
(OPNCT-20) VOLUME 'DOSRES' NOT OWNED BY VSAM
FB 0058 4228I FILE IESCNTL OPEN ERROR X'B4'(180) CAT=VSESPUC (4,AD, 2)
(OPNHC-10) RC X'00000004' FROM CATLG
FB 0058 BST300E THE II CONTROL FILE COULD NOT BE OPENED.
Figure 58. Install SECSERV startup messages
. . You can ignore this message. The install process will continue.
3.1.3.2 Post Install and the Security Server
The BSM is always active during startup independent of the SEC setting on your
IPL SYS command.
After the installation, the IPL SYS parameter may be changed to SYS SEC=NO.
No resource security checking will be done in VSE. This has not changed from
VSE resource checking in the past.
The CICS TS sign-on and transaction-attach security will still be active.
3.1.3.3 Normal Security Server startup
The Security Server must run in a static partition (ALLOC=512K), and it is
started before any other VSE partition, including VSE/POWER. In the initial setup
it runs in FB, but this may be changed to any other static partition. This partition
is specified in the SERVPART parameter option in the IPL SYS command.
If you require FB for production, F4 may be a good candidate for running the
BSM. F4 cannot support a CICS TS system with subsystem storage protection
(STGPROT=YES specified as system initialization parameter).
In the ASI procedure for BG startup, // EXEC BSSINIT initializes the BSM. Then
BG startup continues.
Before VSE/POWER starts up, FB's startup procedure is executed to start the
Security Server with // EXEC BSTPSTS.
If running an ESM, the startup of the ESM replaces the startup of the BSM.
FB 0011 // JOB SECSERV
DATE 03/22/1999, CLOCK 06/56/41
BG 0000 BST001I BASIC SECURITY MANAGER INITIALIZED
BG 0000 STOP
F1 0001 // JOB POWSTART
Figure 59. Normal SECSERV startup message
76 VSE/ESA V2R4
3.1.3.4 Security Server priority
The Security Server partition runs after VSE/POWER and before the CICS
partitions; see the following example:
PRTY BG,FA,F9,F8,F7,F6,F5,F4,F2,FB,F3,F1
3.1.3.5 Security Server shutdown
When you shut down the system and VSE/POWER terminates, the messages
shown in Figure 60 will display:
F1 0001 1Q21I VSE/POWER HAS BEEN TERMINATED
F1 0001 * ------------------------------------------------------------
F1 0001 * SECURITY SERVER PARTITION WILL BE STOPPED
Figure 60. Normal SHUTDOWN message
3.1.3.6 Communicating with the Security Server
There are commands that may be entered on the console using the MSG
command to communicate with the Security Server. The message format is:
MSG FB,DATA=command.
If you issue the MSG command without the data operand, a list of command
options will display; see Figure 61:
MSG FB
AR 0015 1I40I READY
FB 0011 BST221I POSSIBLE SECURITY SERVER COMMANDS ARE:
FB 0011 DBSTARTCACHE........: STARTS DATABASE CACHING
FB 0011 DBSTOPCACHE.........: STOPS DATABASE CACHING
FB 0011 STATUS[=ALL]........: SHOWS TOTAL SERVER STATUS
FB 0011 STATUS=[MAIN|PS|DB].: SHOWS SELECTED STATUS
FB 0011 LOGTIME=N...........: SETS LOGTIME TO N MINUTES (1..9)
FB 0011 RESET...............: CLEANUP EVERYTHING
FB 0011 STOP................: STOPS THE SERVER (USE WITH CAUTION!)
FB 0011 OPENCNTL............: OPENS THE II CONTROL FILE
FB 0011 CLOSECNTL...........: CLOSES THE II CONTROL FILE
Figure 61. Security Server commands available
3.1.3.7 Stopping the Security Server
Note: Use the STOP command carefully.
It will stop the Security Server. Any new user trying to log on will just hang, with
no informational message. Previously logged-on users will continue to work, but
with unpredictable results if using ICCF.
If you issue the STOP command, the following warning message will occur.
Chapter 3. Security 77
FB-0011 BST226W DO YOU REALLY WANT TO STOP THE SECURITY SERVER? (Y/N). .
11 Y
FB 0011 BST212I STOP COMMAND ACCEPTED.
FB-0011 // PAUSE TO RESTART THE SECURITY SERVER ENTER '// EXEC PROC=RESTASEC'
Figure 62. Messages after STOP issued to the Security Server
. . Warning message before stopping the Security Server.
The Security Server can be restarted by issuing // EXEC PROC=RESTASEC.
If you have pressed < e n t e r > to the FB partition, and have the message,
"please assgn sysrdr", execute EXEC PROC=$BJCL or your FB startup
procedure, to start the Security Server again.
On restart of the Security Server, you do not get any confirmation message that
Security Server is initialized.
MSG FB,DATA=STOP
AR 0015 1I40I READY
FB-0011 BST226W DO YOU REALLY WANT TO STOP THE SECURITY SERVER? (Y/
11 Y
FB 0011 BST212I STOP COMMAND ACCEPTED.
FB-0011 // PAUSE TO RESTART THE SECURITY SERVER ENTER '// EXEC PROC=RESTASEC'
11
FB 0011 1N90I EOP WAS FORCED BY EOJ
FB 0011 EOJ SECSERV MAX.RETURN CODE=0099
DATE 03/24/1999, CLOCK 06/48/07, DURATION 18/40/52
FB-0011 1C10D PLEASE ASSIGN SYSRDR.
11 EXEC PROC=$BJCL
FB 0011 // JOB SECSERV
DATE 03/24/1999, CLOCK 06/48/19
MSG FB
AR 0015 1I40I READY
FB 0011 BST221I POSSIBLE SECURITY SERVER COMMANDS ARE:
FB 0011 DBSTARTCACHE........: STARTS DATABASE CACHING
FB 0011 DBSTOPCACHE.........: STOPS DATABASE CACHING
FB 0011 STATUS[=ALL]........: SHOWS TOTAL SERVER STATUS
FB 0011 STATUS=[MAIN|PS|DB].: SHOWS SELECTED STATUS
FB 0011 LOGTIME=N...........: SETS LOGTIME TO N MINUTES (1..9)
FB 0011 RESET...............: CLEANUP EVERYTHING
Figure 63. Stopping/Starting the Security Server
3.1.3.8 Cancelling the Security Server
If FB gets cancelled, a warning message is issued; refer to Figure 64 on
page 79. If the warning message is ignored, and the Security Server is
cancelled, it can be restarted using the FB startup procedure.
78 VSE/ESA V2R4
FB 0011 // JOB SECSERV
REPLID
AR 0015 1I88I NO REPLIES OUTSTANDING
CANCEL FB
AR 0015 1I55D CANCEL SEC.SRVR. ? REPLY YES OR NO . .
AR+0015
15 YES
AR 0015 1I40I READY
FB 0011 BST231I SERVER WAS CANCELLED. CLEANING UP AND EXITING.
FB 0011 1N90I EOP WAS FORCED BY EOJ
FB 0011 EOP $BJCL
FB 0011 1S78I JOB TERMINATED DUE TO CANCEL COMMAND
FB 0011 EOJ SECSERV MAX.RETURN CODE=0099
DATE 03/24/1999, CLOCK 06/53/39, DURATION 00/02/44
FB-0011
11
FB-0011 1C10D PLEASE ASSIGN SYSRDR.
11 EXEC PROC=$BJCL
FB 0011 // JOB SECSERV
DATE 03/24/1999, CLOCK 06/54/26
Figure 64. Cancelling the FB partition
. . Warning message after cancelling the Security Server
Attention
Remember: if you stop or cancel FB, the security on your system is off.
Users cannot log onto the system. Any user currently logged on will continue
working. ICCF users currently signed on may experience unpredictable
results including hanging as the ICCF waits for responses from the Security
Server.
3.1.3.9 Security Server commands
To communicate with the Security Server you have to issue the following MSG
command on the console:
MSG FB,DATA=command.
Figure 61 on page 77 lists the available commands. They are discussed in the
following.
Server database caching: With database caching, recently accessed VSE
Control records are loaded into a data space, thus avoiding VSAM I/O. Use
DBSTARTCACHE and DBSTOPCACHE to control this function; refer to Figure 65
and Figure 66 on page 80. On startup, caching is OFF.
msg fb,data=dbstartcache
AR 0015 1I40I READY
FB 0078 BST310I DATABASE CACHING STARTED.
Figure 65. Starting Security Server database caching
Chapter 3. Security 79
msg fb,data=dbstopcache
AR 0015 1I40I READY
FB 0078 BST309I DATABASE CACHING ENDED.
Figure 66. Stopping Security Server database caching
Server log time: The LOGTIME is the frequency that the server will update its
database with the latest in user profiles. The default is 5 minutes.
Reset: The RESET command will reset the LOGTIME to the default number of
minutes and if the II Control file is closed, it will reopen it. The status of the DB
caching remains the same.
Opening and closing the VSE Control File: The VSE.CONTROL.FILE can be
closed to the Security Server. This does not affect users logging onto the
system, as the cached file is used. However, it does affect any new user added
to the VSE.CONTROL.FILE; they receive the following message:
SIGN-ON FAILED. INFORMATION LOGGED.
The output shown in Figure 67 is logged to the CICS message file.
DFHSN1108 03/25/99 07:13:48 DBDCCICS Signon at netname D08301 by user TESTID
has failed. SAF codes are
(X'00000004',X'00002000'). ESM codes are (X'00000020',X'00000 00000').
IESV0089I FOLLOWING MESSAGE(S) FROM PROGRAM 'IESIES01', OFFSET X'22F6'. 03/25/99
7.13.48
IESA0951I CICS SIGNON FOR USER 'TESTID ' AT TERMINAL 'B003' FAILED.. .
IESA0951I ERROR CONDITION: 'INVREQ ', EIBRESP2: ' 27'.
. . Signon fail message because VSE.CONTROL.FILE closed to the Security Server.
Figure 67. CICS Message File on Sign-on Failure
Status: The status of the Security Server can be displayed; refer to Figure 68 on
page 81.
80 VSE/ESA V2R4
msg fb,data=status=all
AR 0015 1I40I READY
FB 0011 BST223I CURRENT STATUS OF THE SECURITY TRANSACTION SERVER:
FB 0011 SERVER GENERAL STATUS: (06/16/1998)
FB 0011 SERVER WAS STARTED AT .............. : 03/24/1999 07:10:49
FB 0011 TIME ELAPSED (DDDD::HH:MM:SS) ...... : 0000::05:03:26
FB 0011 NO. OF REQUESTS IN XPCC QUEUE ...... : 0
FB 0011 NO. OF REQ. IN INTERNAL REPLY QUEUE : 0
FB 0011 NO. OF FREE (REUSABLE) REQ. BLOCKS . : 9
FB 0011 NO. OF FREE (REUSABLE) REQ. BLOCKS . : 9
FB 0011 NO. OF CURRENTLY ALLOCATED BLOCKS .. : 10
FB 0011 SIZE OF ONE REQUEST BLOCK (BYTES) .. : 740
FB 0011 TOTAL NUMBER OF REQUESTS SO FAR .... : 127
FB 0011 HIGHEST NO. OF PARALLEL REQUESTS ... : 1
FB 0011 SERVER TRACE ....................... : OFF
FB 0011 NUMBER OF SERVER RESETTINGS ........ : 2
FB 0011 PROFILE SERVICE SUBTASK STATUS:
FB 0011 PS SUBTASK STARTED ................. : YES
FB 0011 NO. OF ITEMS IN PS REQUEST QUEUE ... : 0
FB 0011 DATABASE SUBTASK STATUS:
FB 0011 DB SUBTASK STARTED ................. : YES
FB 0011 II CONTROL FILE OPEN ............... : YES
FB 0011 DATABASE CACHE INITIALIZED OK ...... : YES
FB 0011 DATABASE CACHING ................... : OFF
FB 0011 LOGTIME INTERVAL IN MINUTES ........ : 5
FB 0011 NO. OF ITEMS IN DB REQUEST QUEUE ... : 0
Figure 68. Security Server - STATUS=ALL - function
3.1.4 BSM logging and reporting
There is a VSE/ESA optional program, VSE/Access Control-Logging and
Reporting (ACLR), for logging and reporting on the BSM. It logs accesses to the
system and resources defined in the DTSECTAB. It does not log access to CICS
transactions security definitions in the DTSECTXN.
Logging of invalid sign-on attempts or transaction security violations are logged
to the CICS TS message log for the CICS TS being accessed and the VSE/ESA
console. See Figure 69 on page 82 for a sample message log.
Chapter 3. Security 81
DFHSN1200 04/01/99 10:03:03 DBDCCICS Signoff at netname D08001 by user RES3 is complete. 42 transactions entered with
1 errors.
DFHSN1106 04/01/99 10:03:07 DBDCCICS Signon at netname D08001 by user TEST1 requires a new password.
DFHSN1100 04/01/99 10:03:16 DBDCCICS Signon at netname D08001 by user TEST1 in group * is complete.
DFHXS1111 04/01/99 10:03:20 DBDCCICS TST1 Security violation by user TEST1 at netname D08001 for resource TST1 in
class TCICSTRN. SAF codes are (X'00000008',X'00002000'). ESM codes are (X'00000008',X'00000000').
DFHAC2003 04/01/99 10:03:20 DBDCCICS Security violation has been detected term id = A001, trans id = TST1, userid =
TEST1.
DFHSN1200 04/01/99 10:03:52 DBDCCICS Signoff at netname D08001 by user TEST1 is complete. 8 transactions entered with
2 errors.
DFHSN1100 04/01/99 10:03:52 DBDCCICS Signon at netname D08001 by user RES3 in group * is complete.
DFHSN1200 04/01/99 10:04:21 DBDCCICS Signoff at netname D08001 by user RES3 is complete. 8 transactions entered with 1
errors.
DFHSN1100 04/01/99 10:07:37 DBDCCICS Signon at netname D08001 by user RES3 in group * is complete.
DFHSN1200 04/01/99 10:08:04 DBDCCICS Signoff at netname D08001 by user RES3 is complete. 4 transactions entered with 1
errors.
DFHSN1100 04/01/99 10:08:04 DBDCCICS Signon at netname D08001 by user TEST1 in group * is complete.
DFHXS1111 04/01/99 10:08:08 DBDCCICS TST1 Security violation by user TEST1 at netname D08001 for resource TST1 in
class TCICSTRN. SAF codes are (X'00000008',X'00002000'). ESM codes are (X'00000008',X'00000000').
DFHAC2003 04/01/99 10:08:08 DBDCCICS Security violation has been detected term id = A001, trans id = TST1, userid =
TEST1.
DFHSN1200 04/01/99 10:11:38 DBDCCICS Signoff at netname D08001 by user TEST1 is complete. 4 transactions entered with
1 errors.
DFHZC3462 I 04/01/99 10:11:40 DBDCCICS A001 CSNE Node D08001 session terminated. ((2) Module name: DFHZCLS)
DFHZC5966 I 04/01/99 10:13:40 DBDCCICS DELETE started for TERMINAL ( A001 ) SYSID (CIC1) (Module : DFHBSTZ ).
DFHZC6966 I 04/01/99 10:13:40 DBDCCICS Autoinstall delete for terminal A001 with NETNAME D08001 successful.
4A87I AUTOMATIC CLOSE HAS BEEN STARTED
4A88I AUTOMATIC CLOSE FOR 8 FILE(S) COMPLETED
1S55I LAST RETURN CODE WAS 0000
// GOTO STAT
/. STAT
// EXEC DTRSETP,PARM='CPUVAR1;;SET XSTATF2=INACTIVE'
1S55I LAST RETURN CODE WAS 0000
EOJ CICSICCF MAX.RETURN CODE=0000 DATE 04/01/1999, CLOCK 10/14/14, DURATION 21/12/35
Figure 69. Security Server - CICS TS message log (security violation messages)
See Figure 70 for a sample console log.
R1 0095 BST120I USER TEST1
BST120I FORSEC.TST2 CL(TCICSTRN)
BST120I INSUFFICIENT ACCESS AUTHORITY
BST120I FROM TST2
Figure 70. Security Server - VSE/ESA console log message
For a detailed description of this facility, refer to VSE/Access Control-Logging
and Reporting, Program Reference and Operations Guide.
3.1.5 System Authorization Facility (SAF)
The system authorization facility provides centralized control over security
processing by using a system service called the VSE/ESA router. The VSE/ESA
router has a common interface for all products requesting access control
checking for resources or authorization related requests. A resource manager
such as CICS issues a RACROUTE macro call to the VSE/ESA SAF router. The
VSE/ESA router then calls the security manager (either BSM or ESM).
The VSE/ESA router provides an optional installation exit. This exit can be used
to pass control to your own ESM, or to get control before going to a
vendor-supplied ESM.
82 VSE/ESA V2R4
The exit must be named ICHRTX00 and must reside in the shared virtual area
(SVA). This exit also replaces the user MRO security identification program
DFHACEE.
For more information on the VSE/ESA Router exit, see CICS Transaction Server
for VSE/ESA Customization Guide .
3.1.6 External security manager (ESM) installation
CA-Top Secret for VSE/ESA Version 2 Release 4 is the only ESM shipped with
the VSE/ESA Extended Base Products/Components. There are other ESMs
available from other vendors. You find further information on vendor products
on the VSE Web site at http://www.s390.ibm.com/vse/.
ESMs require SEC=YES in your IPL SYS command. With this command, the
DTSECTAB security is activated (as in previous releases of VSE). You may
experience initial problems on installing your ESM if you have never run with
SEC=YES. The DTSECTAB will be controlling your access to VSE files, libraries,
sublibraries and members.
When SEC=YES, the DTSECTAB protects the resources at IPL until the ESM
takes over. If using a BSM, the DTSECTAB stays active. The member
DTSECTRC in ICCF library 59 can be used to add the required VSE security
access for starting up the ESM. See Figure 71 for the entries to access the
CA-Top Secret library that is shipped with VSE/ESA V2R4.
* $$ JOB JNM=DTSECTRC,CLASS=A,DISP=D,NTFY=YES
* $$ LST CLASS=Q,DISP=H
// JOB DTSECTRC ASSEMBLE
// EXEC LIBR PARM='MSHP'
ACCESS S=PRD2.SAVE
DELETE DTSECTAB.PHASE
/*
// LIBDEF *,CATALOG=PRD2.SAVE
* IN CASE GENERATION FEATURE IS INSTALLED ACTIVATE THE FIRST LIBDEF
* // LIBDEF SOURCE,SEARCH=(PRD2.GEN1,PRD1.BASE,PRD1.MACLIB)
// LIBDEF SOURCE,SEARCH=(PRD1.BASE,PRD1.MACLIB)
// OPTION CATAL,LIST
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
*****************************************************
* *
* 5686-066 (C) COPYRIGHT IBM CORP. 1984, 1996 *
* *
*****************************************************
*****************************************************
TITLE 'DTSECTAB - SECURITY TABLE FOR RESOURCES'
********************************************************************
PUNCH ' CATALOG DTSECTRC.OBJ REP=YES'
SPACE 3
Figure 71 (Part 1 of 4). Security Server - DTSECTAB example
Chapter 3. Security 83
*---------------------------------------------------------------------*
* *
* STATIC PART OF DTSECTAB *
* *
*---------------------------------------------------------------------*
* THIS PART IS SHIPPED AS A-BOOK IN IJSYSRS.SYSLIB.DTSECTRC. *
* IF CHANGED, THE USER SHOULD PUT HIS VERSION UNDER THE SAME *
* NAME IN PRD2.SAVE, AS IBM SERVICE IS DONE ON THE MEMBERS *
* CONTAINED IN IJSYSRS.SYSLIB. *
* (THE JOB TO BUILD A DTSECTAB LOOKS FIRST IN PRD2.SAVE FOR *
* DTSECTRC). *
*---------------------------------------------------------------------*
*---------------------------------------------------------------------*
* IBM SUPPLIED USERS *
*---------------------------------------------------------------------*
*** USER DUMMY HAS NO SPECIAL SECURITY RIGHTS.USED TO RESET INHERITANCE
*** IT AVOIDS GETTING TOO MANY RIGHTS WHILE LOADING POWER JOBS DURING
*** ASI.
*** YOU SHOULD NOT DEFINE AN II USER WITH THE NAME 'DUMMY'.
*---------------------------------------------------------------------*
DTSECTAB TYPE=USER, C
NAME=DUMMY, C
PASSWRD=DUMMY, C
AUTH=NO, C
SUBTYPE=INITIAL
SPACE 3
*---------------------------------------------------------------------*
*** USER FORSEC HAS ALL ACCESS RIGHTS. THEREFORE, THE PASSWORD NEEDS
*** TO BE CHANGED AFTER INITIAL INSTALLATION.
*---------------------------------------------------------------------*
DTSECTAB TYPE=USER, C
NAME=FORSEC, C
PASSWRD=FORSEC, C
READDIR=YES, C
MCONS=YES, C
AUTH=YES, C
RIGHT=BTRANS
*---------------------------------------------------------------------*
* END OF IBM SUPPLIED USERS *
*---------------------------------------------------------------------*
*---------------------------------------------------------------------*
*** USER MSCA WAS THE NAME OF THE MASTER CENTRAL SECURITY ADMINISTRATOR
*** ACID (MSCA) USED IN THE INSTALL OF CA-TOP SECRET
*---------------------------------------------------------------------*
DTSECTAB TYPE=USER, . . C
NAME=MSCA, C
PASSWRD=MSCA, C
ACC=(1-32,ALT), C
AUTH=YES, C
RIGHT=BTRANS
Figure 71 (Part 2 of 4). Security Server - DTSECTAB example
84 VSE/ESA V2R4
*---------------------------------------------------------------------*
* *
* FOLLOWING IS THE VSE/ESA 2.4 SUPPLIED PART OF THE DTSECTAB *
* THAT DEFINES A MINIMUM SET OF RESOURCES TO BE PROTECTED. *
* *
*---------------------------------------------------------------------*
****** LIBRARIES*******************************************************
****** IJSYSRS
DTSECTAB TYPE=LIB, C
NAME=DOSRES.VSE.SYSRES.LIBRARY.IJSYSRS, C
UACC=CON
.
.
.
****** IJSYSR2 IS ALIAS NAME OF IJSYSRS, USED BY SERVICE DIALOGS
* WHICH CAN ONLY INVOKED BY SYSTEM ADMINISTRATOR
DTSECTAB TYPE=LIB, C
NAME=DOSRES.VSE.SYSRES.LIBRARY.IJSYSR2, C
UACC=CON
DTSECTAB TYPE=LIB, . . C
NAME=SYSWK1.CA.PRODUCT.LIBRARY.CAIPROD, C
ACC=(1-32), C
UACC=CON
DTSECTAB TYPE=SUBLIB, C
NAME=CAIPROD.PRODUCT, C
ACC=(1-32), C
UACC=CON
DTSECTAB TYPE=MEMBER, C
NAME=CAIPROD.PRODUCT.*, C
ACC=(1-32), C
UACC=READ
.
.
.
DTSECTAB TYPE=MEMBER, C
NAME=PRD2.CONFIG.DTSEC*
DTSECTAB TYPE=SUBLIB, C
NAME=PRD2.BSXCPU*, C
UACC=ALT
Figure 71 (Part 3 of 4). Security Server - DTSECTAB example
Chapter 3. Security 85
* CA TOP SECRET
DTSECTAB TYPE=SUBLIB, . . C
NAME=PRD2.TSSVSE, C
ACC=(1-32), C
UACC=CON
DTSECTAB TYPE=MEMBER, C
NAME=PRD2.TSSVSE.*, C
ACC=(1-32), C
UACC=READ
****** PRIMARY LIBRARY
DTSECTAB TYPE=LIB, C
NAME=*.VSE.PRIMARY.LIBRARY.PRIMARY, C
UACC=CON
****** PRIMARY LIBRARY
DTSECTAB TYPE=LIB, C
NAME=*.VSE.PRIMARY.LIBRARY.PRIMARY, C
UACC=CON
****** THE $$C SUBLIB SHOULD BE USED TO EXCHANGE DATA BETWEEN USERS
DTSECTAB TYPE=SUBLIB, C
NAME=PRIMARY.$$C, C
UACC=UPD
****** FILES *********************************************************
DTSECTAB TYPE=FILE, C
NAME=*.VSE.CONTROL.FILE
DTSECTAB TYPE=FILE, C
NAME=DOSRES.VSE.POWER.QUEUE.FILE
DTSECTAB TYPE=FILE, C
NAME=SYSWK1.VSE.POWER.DATA.FILE, C
SUBTYPE=FINAL
EJECT
EJECT
*---------------------------------------------------------------------*
* END OF VSE/ESA DTSECTAB *
*---------------------------------------------------------------------*
SPACE 3
END
/*
// IF $MRC GT 4 THEN
// GOTO NOLINK
// EXEC LNKEDT
/*
// EXEC LIBR,PARM='MSHP'
CONNECT S=PRD2.SAVE:IJSYSRS.SYSLIB
COPY DTSECTAB.PHASE R=Y
/*
/. NOLINK
/*
/&
Figure 71 (Part 4 of 4). Security Server - DTSECTAB example
. . Master Central Security Administrator ACID(MSCA) from the install of
CA-Top Secret
. . CA90's install library name and sublibrary used for startup of CA90s.
. . VSE library and sublibrary where CA-Top Secret is installed from the
VSE/ESA Extended Base Products/Components tape.
86 VSE/ESA V2R4
Other SYS parameters that are required for the ESM are the SYS E S M = and
SYS SERVPART=. The ESM initialization phase name can be found in the ESM
installation documentation.
Some ESMs require their own partition to run in. If you use the BSM partition, it
will probably have to be increased from the 512 K. CA-Top Secret requires
LE/VSE, so the partition needs to be big enough for LE/VSE to run.
VSE/ESA V2R4 checks for the ESM setting first. If the parameters are set on the
IPL SYS, the ESM is activated; otherwise, the BSM is used. There are also
system initialization parameters which need to be considered when running with
an external security manager (ESM).
Full ESM installation documentation should be acquired from the vendor and
followed closely.
3.2 CICS Transaction Server for VSE/ESA R1 security
With the removal of CICS internal security, you must now decide what level of
security your CICS systems require. You have three levels of security to choose
from.
1. No security
This level will run the CICS system with no security . If you specify SEC=NO
as a system initialization parameter every user will be able to run every
transaction and have access to every resource.
2. Basic security
This level uses the basic security manager (BSM) that is supplied with
VSE/ESA Version 2 Release 4. This provides only sign-on and
transaction-attach security. Users will still have access to resources.
3. Full-function security
This level uses an external security manager (ESM). This provides resource
security, command security, MRO/ISC link security, and report security for
the CICS/VSE Report Control Facility.
3.2.1 CICS TS Sign-on security provided by the BSM
Sign-on security for your CICS regions must now be considered as a
system-wide security issue, not just a CICS region issue. There must be only
one user profile per user ID to be used system wide. The VSE.CONTROL.FILE
contains this profile.
Any use of the DFHSEC macro to interface with CICS security is no longer
available. CICS TS only offers EXEC CICS SIGNON and EXEC CICS QUERY
SECURITY. There are no XPI calls for security-related customization through
global user exits.
Sign-on security is always performed independently of the IPL SYS S E C = setting
with the exception of the RECOVER option. See Figure 56 on page 74.
Chapter 3. Security 87
3.2.1.1 Migrating your System Signon Table (DFHSNT)
The SNT sign-on table macro for defining CICS users and user security is
obsolete. Also, the DFHSNT program definition has been removed from the
group DFHSIGN in DFHLIST.
All security-related information is contained in the VSE.CONTROL.FILE. Users
are now defined via the VSE/ESA Interactive Interface (II). Every user has a user
profile which includes the unique user ID and password.
Users currently using the Operator Name on the CSSN transaction will be
required to change to an 8-character user ID for the CESN transaction.
You define users using the Maintain User Profiles dialog on the II; see 3.2.1.2,
“Maintaining Users with the Interactive Interface.” For a large number of user
updates, a batch utility program IESUPDCF is available, see 3.2.1.3, “Running
batch program IESUPDCF” on page 91.
If you currently have multiple DFHSNT tables for different CICS regions, these
tables must be combined and users defined to the VSE.CONTROL.FILE.
3.2.1.2 Maintaining Users with the Interactive Interface
With the Maintain User Profiles dialog of on the II you define, update, or delete
user profiles. To access the dialog, start with VSE/ESA Function Selection panel
and select:
2 (Resource Definition)
1 (User Interface Tailoring)
1 (Maintain User Profiles)
The Fastpath to the Maintain User Profiles dialog is: 211.
On the MAINTAIN USER PROFILES dialog (see Figure 72 on page 89) type 1 to
add a new user or 2 to change a user in the OPT column to the left of the user
ID. The ADD OR CHANGE USER PROFILES dialog will display; see Figure 73 on
page 89.
88 VSE/ESA V2R4
IESADMUPL2 MAINTAIN USER PROFILES
VSE CONTROL FILE
START.... ________
OPTIONS: 1 = ADD 2 = CHANGE 5 = DELETE
PASSWORD REVOKE USER INITIAL NAME
OPT USERID VALID UNTIL DATE TYPE NAME TYPE
_ $SRV 01/01/97 * 2 IESERSUP 2
_ CICSUSER 01/01/97 * 3 DFLESEL 2
_ CTSRES5 03/21/99 * 1 DUMMY 1
_ DBDCCICS 1 DUMMY 1
_ FORSEC 1 IESEADM 2
1 ITSORES3 03/23/99 * 3 IESEPROG 2
_ KEITH 03/24/99 * 3 IESEADM 2
_ OPER 01/01/97 * 2 IESEOPER 2
_ POST 1 IESA$FST 1
_ PRODCICS 1 DUMMY 1
_ PROG 01/01/97 * 2 IESEPROG 2
_ RES1 1 IESEADM 2
PF1=HELP 3=END
PF7=BACKWARD 8=FORWARD
Figure 72. Security Server - Maintain User Profiles
There are four panels for setting up a user. Panel 1 and panel 2 are used for
defining VSE/ESA profile information. Panel 3 and panel 4 are used for the CICS
TS profile information. Use PF8 to scroll through these panels.
Figure 73 shows panel 1.
IESADMUPBA ADD OR CHANGE USER PROFILE
Base II CICS ResClass ICCF
To ADD, specify information for all of the entries.
USERID............. TESTID 4 - 8 characters (4 characters for ICCF users . .
INITIAL PASSWORD... ________ 3 - 8 characters
DAYS............... 000 0-365 Number of days before password expires . .
REVOKE DATE........ ________ Date when Userid will be revoked (mm/dd/yyyy . .
USER TYPE.......... 3 1=Administrator, 2=Programmer, 3=General
INITIAL NAME....... IESEADM Initial function performed at signon
NAME TYPE.......... 1 1=Application, 2=Selection Panel
SYNONYM MODEL...... Userid to be used as model for synonyms
PF1=HELP 3=END 5=UPDATE
8=FORWARD
Figure 73. First dialog in II to add/change the user profile screen
. . Only 8 characters are available for the USERID no matter which
sign-on procedure is used, II or CESN. ICCF has not changed. An
ICCF user can only have a 4-character USERID.
. . This password entered must be changed by the user at initial sign-on.
Chapter 3. Security 89
. . After this date, a sign-on attempt will be rejected. This can be used
for temporary users. The basic security manager (BSM) will also
revoke a user ID after the number of sign-on attempts exceeds 5.
This value is specified in IESELOGO setup. A sample job is found in
ICCF library 59.
The second panel (see Figure 74) shows the user's authorization to perform
certain tasks.
IESADMUPII USER AUTHORIZATION
Base II CICS ResClass ICCF
Answer yes or no to the following questions for userid TESTID
Enter 1 for yes, 2 for no
NEWS....................... 1 Should user receive news items?
ESCAPE..................... 2 Can user escape to CICS?
CONFIRM DELETE............. 2 Does user want a confirmation message?
VSE PRIMARY SUBLIBRARY..... 1 Does user want a PRIMARY sublibrary?
SUBMIT TO BATCH............ 1 Can user submit to Batch?
PF1=HELP 3=END 5=UPDATE
PF7=BACKWARD 8=FORWARD
Figure 74. Second dialog in II to add/change the user profile screen
The third and forth panels are used for CICS users.
IESADMUPCI ADD OR CHANGE CICS SEGMENT
BASE II CICS RESCLASS ICCF
OPERATOR ID............. TS1 Enter 3 character id for user TESTID1
OPERATOR PRIORITY....... 000 Operator priority between 0-255
XRF SIGNOFF............. 2 Sign off after XRF takeover (1=yes,2=n
TIMEOUT................. 00 Minutes until sign off between 0-60
PRIMARY LANGUAGE........ _ National language for CICS messages
Place an 'X' next to the operator classes for this user . .
01 X 02 _ 03 X 04 05 06 07 _ 08 _
09 _ 10 _ 11 _ 12 _ 13 _ 14 _ 15 _ 16 _
17 _ 18 _ 19 _ 20 _ 21 _ 22 _ 23 _ 24 _
PF1=HELP 3=END 5=UPDATE
PF7=BACKWARD 8=FORWARD
Figure 75. Third Dialog in II for defining CICS security information
. . The operator classes define the user to CICS TS. 1 is the default
class.
90 VSE/ESA V2R4
IESADMUPR1 ADD OR CHANGE RESOURCE ACCESS RIGHTS
Base II CICS ResClass ICCF
Place an 'X' next to the transaction security keys for user TESTID1
01 X 02 03 04 05 06 07 08 09 10 . .
12 13 14 15 16 17 18 19 20 21
23 24 25 26 27 28 29 30 31 32
34 35 36 37 38 39 40 41 42 43
45 46 47 48 49 50 51 52 53 54
56 57 58 59 60 61 X 62 63 64
Specify the access rights for 1-32 DTSECTAB access control classes
( _=No access, 1=Connect, 2=Read, 3=Update, 4=Alter )
01 _ 02 _ 03 _ 04 _ 05 _ 06 _ 07 _ 08 _ 09 _ 10 _ . .
12 _ 13 _ 14 _ 15 _ 16 _ 17 _ 18 _ 19 _ 20 _ 21 _
23 _ 24 _ 25 _ 26 _ 27 _ 28 _ 29 _ 30 _ 31 _ 32 _
READ DIRECTORY..... 1 User can read directory with Connect (1=yes,
B-TRANSIENTS....... 1 User can manipulate B-Transients (1=yes,
PF1=HELP 3=END 5=UPDATE
PF7=BACKWARD 8=FORWARD
Figure 76. Fourth dialog in II for defining CICS security information
. . Each transaction has a security key of 1 to 64 assigned. Transactions
available for all users should have a security key of 1. VSE/ESA
Interactive Interface (II) requires keys 1 and 61. The security keys
here correspond to the transaction security class as shown in
Figure 82 on page 97
. . These have not changed from VSE/ESA 2.3.
When finished, press PF5 to UPDATE. The following message will display,
meaning the profile has been added to the VSE.CONTROL.FILE:
USER PROFILE INFORMATION HAS BEEN UPDATED.
3.2.1.3 Running batch program IESUPDCF
When migrating all your users from the DFHSNT table, a batch program may be
used. A parameter card defines the user ID, password and profile. If you set up
a common profile for a group of users, then the other fields will be copied from
the profile. A sample of this job is provided in Figure 77 on page 92 and also in
ICCF library 59.
Chapter 3. Security 91
* $$ JOB JNM=IESUPDCF,CLASS=0,DISP=D
* $$ PUN DISP=I,CLASS=0,PRI=9
// JOB IESUPDCF
* ADd USERID,PASSWD,PROFILE(,OPTIONAL PARAMETERS)
* ALter USERID(,OPTIONAL PARAMETERS)
* Delete USERID
* EXPLANATION OF PARAMETERS:
* ==========================
* 1. REQUIRED AND POSITIONAL PARAMETERS:
* --------------------------------------
* USERID ... THE ID OF THE USER ( ADD, ALTER, DELETE )
* ( 4-8 CHARACTER / 4 CHARACTER FOR ICCF USER )
* PASSWD ... THE PASSWORD OF THE USER ( ADD )
* ( 3-8 CHARACTERS )
* PROFILE ... THE ID OF THE USER USED AS PROFILE FOR
* THE NEW USER ( ADD )
* ( 4-8 CHARACTER / 4 CHARACTER FOR ICCF USER )
* 2. OPTIONAL PARAMETERS IN ADD/ALTER STATEMENT:
* ----------------------------------------------
* ----------------------------------------------
* Catalog= ... THE DEFAULT CATALOG OF THE USER
* EXAMPLE: CAT=VSESPUC
* Days= ... NUMBER OF DAYS IN EXPIRATION INTERVAL
* EXAMPLE: DAYS=20 ( RANGE: 0-365)
* Library= ... Primary ICCF library ( only ICCF users )
* EXAMPLE: LIB=20
* Initial= ... Initial function at SIGNON
* EXAMPLE: INIT=APPLNAME(A) ... FOR APPLICATION
* INIT=SELNAME(S) ... FOR SELECTION P.
* Natlang= ... NATIONALLANGUAGE_INDICATOR
* EXAMPLE: NAT=E ( for english )
* OID = ... OID CHARACTERS
* EXAMPLE: OID=ABC ( max. 20 characters )
* Operator= OPERATOR ID
* EXAMPLE: OPER=OPE
* PWD= ... USER PASSWORD
* PAssword= EXAMPLE: PWD=PASSWD ( 3-8 Characters )
* PRiority= ... OPERATOR PRIORITY
* EXAMPLE: PRIOR=5 ( RANGE: 0-255 )
* Revoke= ...REVOKE_DATE
* EXAMPLE: R=01/31/97 ( Format mm/dd/yy )
* Synonym= ... SYNONYMS MODEL
* EXAMPLE: SYNONYM=SYNS ( 4-8 Characters )
* Timeout= ... TIMEOUT INTERVAL
* EXAMPLE: TIME=20 ( Values: 0,5,10,...,60 )
Figure 77 (Part 1 of 2). Sample job IESUPDCF
92 VSE/ESA V2R4
* APM=Yes|No ... APPLICATION PROFILE MAINTENANCE
* BQA=Yes|No ... MANAGE ALL BATCH QUEUES
* CMD=Yes|No ... ENTER ALL CONSOLE COMMANDS
* COU=Yes|No ... FULL OUTPUT ON SYSTEM SONSOLE
* COD=Yes|No ... CONFIRM ON DELETE
* DVF=Yes|No ... DEFINE VSAM FILES
* ESC=Yes|No ... ESCAPE TO CICS
* MVC=Yes|No ... MANAGE VSAM CATALOGS
* NEWS=Yes|No ... DISPLAY NEWS TO USER
* OLPD=Yes|No ... DELETE OLPD INCIDENTS
* PSL=Yes|No ... OWNS A PRIVATE SUBLIBRARY
* BAT=Yes|No ... SUBMIT TO BATCH
* SPM=Yes|No ... SELECTION PANEL MAINTENANCE
* UPM=Yes|No ... USER PROFILE MAINTENANCE
* XRF=Yes|No ... XRF SIGNOFF
// EXEC IESUPDCF,SIZE=64K
ICCF=IGNORE
ADD USER1,USR1,PROF1 . .
ADD USER2,USR2,PROF2,OPERATOR=US3 . .
/*
/&
* $$ EOJ
Figure 77 (Part 2 of 2). Sample job IESUPDCF
. . Data to add user1 with password usr1 and profile prof1.
. . Optional parameters such as operator ID, can be entered after the
profile name.
3.2.2 User sign-on and sign-off
Users sign on to CICS TS by either the VSE/ESA Interactive Interface (II) sign-on
dialog (see Figure 78 on page 94) or the CICS CESN sign-on transaction (see
Figure 79 on page 94).
Any user documentation will need to be updated to reflect the new sign-on
procedure and user ID. See 3.2.1.1, “Migrating your System Signon Table
(DFHSNT)” on page 88 for reference.
The VSE.CONTROL.FILE is checked by the Security Server, or the information
passed on to the external security manager (ESM) CSSN and CSSF transactions
are now obsolete. CSSF can still be issued by an application program issuing
EXEC CICS START CSSF .
There is a new system initialization parameter SNSCOPE= to specify whether or
not a user ID can be signed on to CICS more than once within a CICS region or
a VSE system.
Chapter 3. Security 93
IESADMSO1 VSE/ESA ONLINE
5690-VSE and Other Materials (C) Copyright IBM Corp. 1997 and other d
VV VV SSSSS EEEEEEE ++
VV VV SSSSSSS EEEEEEE ++
VV VV SS EE ++ EEEEEEE SSSSS AA
VV VV SSSSSS EEEEEE ++ EEEEEEE SSSSSSS AAAA
VV VV SSSSSS EEEEEE ++ EE SS AA AA
VV VV SS EE ++ EEEEEE SSSSSS AA A
VVVV SSSSSSS EEEEEEE ++ EEEEEE SSSSSS AA A
VV SSSSS EEEEEEE ++ EE SS AAAAAAA
++ EEEEEEE SSSSSSS AA A
++ EEEEEEE SSSSS AA A
Your terminal is B001 and its name in the network is D08101
Today is 03/23/1999 To sign on to DBDCCICS -- enter your:
USER-ID........ ________ The name by which the system knows you.
PASSWORD....... Your personal access code.
PF1=HELP 2=TUTORIAL 3=TO VM 4=REMOTE APPLICATIONS
10=NEW PASSWORD
Figure 78. Interactive Interface sign-on dialog
Figure 79 shows the CICS CESN sign-on transaction.
Signon to CICS APPLID D
VSE/ESA ONLINE
Type your user Id and password, then press ENTER:
Userid . . . . . .
Password . . .
Groupid . . . . .
Language . . .
New Password . . .
DFHCE3520 Please type your user Id.
F3=Exit
Figure 79. CESN sign-on screen
. . Only 8 characters are available for the Userid.
. . Groupid only applies to a full-function ESM, not the VSE BSM.
94 VSE/ESA V2R4
3.2.3 User password checking
The first time users sign onto the system after being defined to the
VSE.CONTROL.FILE ,they are prompted for a new password; see Figure 80.
IESADMSO2 VSE/ESA SIGN-ON WITH NEW PASSWORD
Enter your new password in both places below then enter your current
password for sign-on verification.
Then press the ENTER key.
NEW PASSWORD ==> 3-8 characters
NEW PASSWORD ==> Re-Enter new password for verification
OLD PASSWORD ==> Current password
PF1=HELP 3=END
Figure 80. Password change dialog when signing onto VSE/ESA Interactive Interface (II)
3.2.4 CICS TS security parameters
There are now only three places within CICS where security parameters can be
defined.
1. The system initialization table DFHSIT
For a complete description of the new security system initialization
parameters, see CICS Transaction Server for VSE/ESA System Definition
Guide .
2. Transaction definitions
For a complete description of the new Transaction security definitions, see
CICS Transaction Server for VSE/ESA Resource Definition Guide .
3. Link security
For a complete description of the new Link security options, see CICS
Transaction Server for VSE/ESA Resource Definition Guide .
3.2.5 CICS TS transaction-attach security
Transaction security is part of the basic security manager (BSM). It is always
active regardless of the security setting in the IPL SYS SEC parameter. It is not
active if SEC=NO is specified as a system initialization parameter.
A new security table DTSECTXN is used for transaction definitions. This table
may be updated through an II panel (see 3.2.5.2, “Maintaining Transactions using
the Interactive Interface” on page 96) or manually by an assembler source file
(see 3.2.5.3, “Maintaining transactions using an assembler source file” on
page 99). The DTSECTXN table includes entries for all CICS transactions. You
will see entries for all the IBM-supplied transactions.
In installing new CICS products, their transactions will need to be defined to the
CICS TS CSD file and to the DTSECTXN table. The user's profile must have the
corresponding security key in order to access the transaction. Unauthorized
Chapter 3. Security 95
access attempts are logged to the CICS console file and the VSE console log;
refer to 3.1.4, “BSM logging and reporting” on page 81.
Attention
A transaction not defined in DTSECTXN cannot be accessed. All transactions
must be access protected and in this file.
3.2.5.1 Multiple CICS regions
If more than one CICS TS runs under VSE/ESA V2R4, then a CICS region ID is
used to identify the CICS system to the transaction security definition. This
prefix is the ID statement in the CICS startup JCL.
The new system initialization parameter SECPRFX=YES must be used for the
CICS system to be checked. Also, IPL SYS SEC=YES must be specified. If your
VSE/ESA system has IPL SYS SEC=NO, do not specify a CICS region on your
transaction security definitions. Only transactions with no CICS Region specified
will be checked. See Figure 82 on page 97 for information on setting up
multiple CICS TS systems for transaction security.
3.2.5.2 Maintaining Transactions using the Interactive Interface
From the VSE/ESA Function Selection panel, select:
2 Resource Definition
8 Transaction Security
The Fastpath to the Define Transaction Security panel is 28.
Selecting a transaction: A transaction may be selected individually or by CICS
region; see Figure 81. By pressing Enter, all transactions are listed.
TAS$SECF DEFINE TRANSACTION SECURITY: SPECIFY FILTER
Enter the required data and press ENTER.
Press ENTER to list all security entries.
Specify the prefix of the CICS transaction names or the CICS region you w
be listed and press the ENTER key.
TRANSID...................... TST_ Enter the full transaction name or
1 - 3 prefix characters, e.g. AB for
all transactions starting with AB
CICS REGION.................. ________ Enter the CICS region.
PF1=HELP 2=REDISPLAY 3=END 6=MERGE
Figure 81. Inquire Transaction dialog
96 VSE/ESA V2R4
Defining a transaction On the panel shown in Figure 81 on page 96 we specified
TST as filter. Figure 82 shows the resulting panel. :
TAS$SEC1 DEFINE TRANSACTION SECURITY
Enter the required data and press ENTER.
OPTIONS: 1 = ADD 2 = ALTER 5 = DELETE
OPT TRANSACTION NAME CICS REGION SECURITY CLASS
_ TST1 . . TSRES3. . 10 . .
1 TST1 TSRES3 10
_ TST2 5
_ TST3 TSRES3 14
_ __
_ __
_ __
_ __
_ __
_ __
LOCATE TRANSACTION NAME == > ____
PF1=HELP 2=REDISPLAY 3=END 5=PROCESS
Figure 82. Define Transaction dialog
. . This is the transaction ID.
. . If multiple CICS TS regions exist, this is the region where the security
rule applies. This is only checked if SECPRFX=YES is specified in
the the SIT for the region and the IPL SYS SEC=YES for the VSE.
The CICS region name is the name provided in the ID statement of
the CICS startup deck.
. . This is the security key for the transaction that must match the user's
security key.
Figure 83 shows the ADD transaction screen.
TAS$SEC2 DEFINE TRANSACTION SECURITY: ADD ENTRIES
Enter the required data and press ENTER.
TRANSACTION CICS SECURITY
NAME REGION CLASS
____ ________ 10 . .
____ ________ 10
____ ________ 10
____ ________ 10
____ ________ 10
____ ________ 10
____ ________ 10
____ ________ 10
____ ________ 10
____ ________ 10
PF1=HELP 2=REDISPLAY 3=END
Figure 83. Add Transaction dialog
Chapter 3. Security 97
. . Security Class and CICS Region will be brought forward from the
previous dialog where the ADD was selected.
After adding, changing or deleting transactions, on the Define Transaction
Security screen, press PF5 to PROCESS.
The process first updates the member SECMAC in ICCF library 51. This member
is a table of the assembler DTSECTXN macros for all the transactions. A job is
created to catalog the source file as DTSECTXS in PRD2.CONFIG and assemble
the phase DTSECTXN in IJSYSRS.SYSLIB; see Figure 84.
* $$ JOB JNM=CATSEC,DISP=D,PRI=3, C
* $$ NTFY=YES, C
* $$ LDEST=*, C
* $$ CLASS=0
// JOB CATSEC CATALOG DTSECTXN
// EXEC LIBR,PARM='MSHP'
ACC S=PRD2.CONFIG
CATALOG DTSECTXS.A REPLACE=YES
* $$ SLI ICCF=(SECMAC),LIB=(51) . .
/+
CONN S=IJSYSRS.SYSLIB:PRD2.SAVE
COPY DTSECTXN.PHASE REPLACE=YES . .
/*
// EXEC LIBR
CONN S=IJSYSRS.SYSLIB:PRD2.SAVE
COPY DTRISEC.Z REPLACE=YES . .
/*
// LIBDEF PHASE,CATALOG=IJSYSRS.SYSLIB
// OPTION ERRS,SXREF,SYM,NODECK,CATAL
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)' . .
* $$ SLI ICCF=(SECMAC),LIB=(51)
/*
// IF $MRC GT 4 THEN
// GOTO NOLNK
// EXEC LNKEDT,SIZE=256K,PARM='MSHP'
/*
/. NOLNK
/&
* $$ EOJ
Figure 84. Job created by PROCESS option
. . Catalog the DTSECTXN macro definitions.
. . Back up the old DTSECTXN phase to PRD2.SAVE.
. . Back up the IPF table of the transaction definitions to PDR2.SAVE.
. . Assemble the DTSECTXN definitions and link DTSECTXN phase.
98 VSE/ESA V2R4
3.2.5.3 Maintaining transactions using an assembler source file
The assembler source file of the transaction security definitions can be found in
PRD2.CONFIG as DTSECTXS. You can manually change this file and assemble
DTSECTXN; see Figure 85. Be careful when manually updating this file.
SECMAC will not match.
* $$ JOB JNM=DTSECTXN,DISP=D,CLASS=0
* $$ LST CLASS=R,DEST=(,ITSORES3)
// JOB DTSECTXN ASSEMBLE DTSECTXN TABLE
// LIBDEF PHASE,CATALOG=IJSYSRS.SYSLIB
// OPTION ERRS,SXREF,SYM,NODECK,CATAL
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
DTSECTXN NAME=AADD,TRANSEC=(1), X
SUBTYPE=INITIAL
DTSECTXN NAME=ABRW,TRANSEC=(1)
DTSECTXN NAME=ACCT,TRANSEC=(1)
DTSECTXN NAME=ACEL,TRANSEC=(1)
DTSECTXN NAME=ACLG,TRANSEC=(1)
DTSECTXN NAME=AC01,TRANSEC=(1)
DTSECTXN NAME=AC02,TRANSEC=(1)
DTSECTXN NAME=AC03,TRANSEC=(1)
DTSECTXN NAME=AC05,TRANSEC=(1)
DTSECTXN NAME=AC06,TRANSEC=(1)
DTSECTXN NAME=AC2A,TRANSEC=(1)
.
.
.
.
.
.
DTSECTXN NAME=TELR,TRANSEC=(1)
DTSECTXN NAME=TELW,TRANSEC=(1)
DTSECTXN NAME=TEST,TRANSEC=(10)
DTSECTXN NAME=TSRES2.TST1,TRANSEC=(05) . .
DTSECTXN NAME=TSRES3.TST1,TRANSEC=(10) . .
DTSECTXN NAME=TST2,TRANSEC=(10) . .
DTSECTXN NAME=TST3,TRANSEC=(10)
DTSECTXN NAME=TSRES3.TST4,TRANSEC=(10)
DTSECTXN NAME=UPDT,TRANSEC=(1)
DTSECTXN NAME=USER,TRANSEC=(61)
DTSECTXN NAME=XPKO,TRANSEC=(1)
DTSECTXN NAME=XPLA,TRANSEC=(1)
DTSECTXN NAME=2RPS,TRANSEC=(1)
DTSECTXN NAME=8888,TRANSEC=(1)
DTSECTXN NAME=9999,TRANSEC=(1), X
SUBTYPE=FINAL
END
/*
// IF $MRC GT 4 THEN
// GOTO NOLNK
// EXEC LNKEDT,SIZE=256K,PARM='MSHP'
/*
/. NOLNK
/&
* $$ EOJ
Figure 85. DTSECTXN assembly
Chapter 3. Security 99
. . Macro defining transaction TST1 security for CICS region TSRES2.
. . Macro defining transaction TST1 security for CICS region TSRES3.
. . Macro defining TST2 transaction for all CICS regions.
3.2.5.4 Activating transaction security changes
After changing any security definitions, the CICS region has to reflect the
change. This must be done with the CEMT CICS-supplied transaction in the
following form:
CEMT PERFORM SECURITY or CEMT P SE
The new CICS transaction table will be made available to the CICS region where
the command was entered.
3.2.5.5 Converting the DFHPCT (DTSECTXS REXX Procedure)
There is a REXX procedure DTSECTXS in ICCF library member SKSECTXS which
can be cataloged and run; see Figure 86 on page 101. This REXX procedure
DTSECTXS will read a VSE library member of your current PCT definitions and
create a file either in DTSECTXN macro definitions format or in IPF table format.
The DTSECTXN macro definitions created can be added to your assembly of
DTSECTAB; see 3.2.5.3, “Maintaining transactions using an assembler source
file” on page 99.
The IPF table format is usable by the VSE/ESA Interactive Interface (II) dialog
Define Transaction Security to merge security entries for transactions. This is
the default; see 3.2.5.6, “MERGING transaction definitions to the DTSECTXN
table” on page 104.
100 VSE/ESA V2R4
/***************************************************************/
/* FUNCTION: */
/* This EXEC reads a library file containing CICS/VSE PCT */
/* definitions. The read input is used to create a file */
/* containing the equivalent DTSECTXS-definitions for */
/* CICS TS. */
/* */
/* Parameters are: */
/* INFILE= Librarian name of the file containing PCT */
/* definitions */
/* FORMAT={IPF|MACRO} */
/* defines the format of the output file */
/* IPF is the format usable by the Interactive */
/* Interface dialog "Define Transaction Security", */
/* to merge security entries for transactions. */
/* This is the default. */
/* MACRO is the format consisting of DTSECTXN-macro */
/* definitions. */
/* OUTFILE= Librarian name of the file to be created */
/* containing the DTSECTXN definitions */
/* Default is PRD2.CONFIG.DTRISEC.M for IPF-format */
/* and PRD2.CONFIG.DTSECTXS.A for Macro-format */
/* REGION= Name of the CICS-region to include into the */
/* DTSECTXN definitions */
/* If region name should not be included into */
/* a DTSECTXN definition, omit this parameter or */
/* specify REGION= followed by blank */
/* */
/* Invocation samples: */
/* */
/* // EXEC REXX=DTSECTXS,PARM='INFILE=IJSYSRS.SYSLIB.IESZPCT.A'*/
/* when using PARM-operand to specify parameters */
/* */
/* // EXEC REXX=DTSECTXS */
/* INFILE=IJSYSRS.SYSLIB.IESZPCT.A */
/* FORMAT=MACRO */
/* OUTFILE=LIB.SLIB.DTSECTXS.A */
/* REGION=DBDCCICS */
/* when using SYSIPT to specify parameters */
/* */
/* Return codes: */
/* 0 successful */
/* 4 Unsupported character in transaction name */
/* 8 Output member exists already */
/* 12 Reading of library member with PCT-defs failed */
/* 16 Transaction name longer than 4 characters */
/* 20 TRANSEC definition is not a number */
/* 24 No transaction specifications found */
/* 28 Writing output member failed */
/* */
/***************************************************************/
Figure 86. DTSECTXS REXX procedure description
Chapter 3. Security 101
Figure 87 shows sample JCL to execute this procedure.
* $$ JOB JNM=DTSECTXS,CLASS=0
// JOB DTSECTXS
// EXEC LIBR
ACCESS S=PRD2.SAVE
LIST PCTDEFN.A
/*
// LIBDEF PROC,SEARCH=PRD2.CONFIG
// EXEC REXX=DTSECTXS
INFILE=PRD2.SAVE.PCTDEFN.A
FORMAT=MACRO . .
OUTFILE=PRD2.SAVE.OUTDEFNS.A
/*
// EXEC LIBR
ACCESS S=PRD2.SAVE
LIST OUTDEFNS.A
/&
* $$ EOJ
Figure 87. Sample JCL to execute DTSECTXN procedure
. . Output will be DTSECTXN macro definitions. Specify IPF for IPF table
input.
Figure 88 on page 103 shows the sample job showing the conversion of the
DFHPCT macro instructions converted to DTSECTXN macro instructions.
102 VSE/ESA V2R4
// JOB DTSECTXS DATE
// EXEC LIBR
ACCESS S=PRD2.SAVE
LIST PCTDEFN.A . .
MEMBER=PCTDEFN.A SUBLIBRARY=PRD2.SAVE DATE:1999-04-13
TIME: 07:42
-------------------------------------------------------------------------
* ------------------------------------------------------------- *
* TEST TRANSACTIONS
* ------------------------------------------------------------- *
PDE1 DFHPCT TYPE=ENTRY, ADD CONNECTION X
TRANSID=PDE1, X
PROGRAM=PDE001, X
TWASIZE=0, X
TRANSEC=20, X
DTB=YES, X
SPURGE=YES, X
TPURGE=YES
PDE2 DFHPCT TYPE=ENTRY, ESTABLISH CONNECTION X
TRANSID=PDE2, X
PROGRAM=PDE002, X
TWASIZE=0, X
DTB=YES, X
TRANSEC=20, X
SPURGE=YES, X
TPURGE=YES
PDE3 DFHPCT TYPE=ENTRY, ADD CONNECTION X
TRANSID=PDE3, X
PROGRAM=PDE003, X
TWASIZE=0, X
TRANSEC=20, X
DTB=YES, X
SPURGE=YES, X
TPURGE=YES
PDE4 DFHPCT TYPE=ENTRY, ESTABLISH CONNECTION X
TRANSID=PDE4, X
TRANSEC=20, X
PROGRAM=PDE004, X
TWASIZE=0, X
DTB=YES, X
SPURGE=YES, X
TPURGE=YES
L113I RETURN CODE OF LIST IS 0
1S55I LAST RETURN CODE WAS 0004
// LIBDEF PROC,SEARCH=PRD2.CONFIG
// EXEC REXX=DTSECTXS . .
Created definitions in < PRD2.SAVE.OUTDEFNS.A >:
Figure 88 (Part 1 of 2). Output of sample DTSECTXN procedure job
Chapter 3. Security 103
DTSECTXN NAME=PDE1,TRANSEC=(20),SUBTYPE=INITIAL
DTSECTXN NAME=PDE2,TRANSEC=(20)
DTSECTXN NAME=PDE3,TRANSEC=(20)
DTSECTXN NAME=PDE4,TRANSEC=(20),SUBTYPE=FINAL
END
1S55I LAST RETURN CODE WAS 0000
EOP DTSECTXS
// EXEC LIBR
ACCESS S=PRD2.SAVE
L113I RETURN CODE OF ACCESS IS 0
LIST OUTDEFNS.A . .
MEMBER=OUTDEFNS.A SUBLIBRARY=PRD2.SAVE DATE:1999-04-13
TIME: 07:42
-------------------------------------------------------------------------
DTSECTXN NAME=PDE1,TRANSEC=(20),SUBTYPE=INITIAL
DTSECTXN NAME=PDE2,TRANSEC=(20)
DTSECTXN NAME=PDE3,TRANSEC=(20)
DTSECTXN NAME=PDE4,TRANSEC=(20),SUBTYPE=FINAL
END
L113I RETURN CODE OF LIST IS 0
1S55I LAST RETURN CODE WAS 0000
EOJ DTSECTXS MAX.RETURN CODE=0000
Figure 88 (Part 2 of 2). Output of sample DTSECTXN procedure job
. . Sample input definitions
. . DTSECTXS REXX procedure
. . Sample output macro definitions
By changing the FORMAT command, the output could be in IPF table format. IPF
Table format is required for the MERGE option on the Define Transaction
Security dialog; see 3.2.5.6, “MERGING transaction definitions to the DTSECTXN
table.” Figure 89 shows the output in IPF table format.
MEMBER=OUTDEFNS.A SUBLIBRARY=PRD2.SAVE DATE:1999-04-12
TIME: 13:56
-------------------------------------------------------------------------
$$$005**TRANSID REGION CLASS CHANGED SUBTYPE
$$$005**K K
$$$005**PDE1 20
$$$005**PDE2 20
$$$005**PDE3 20
$$$005**PDE4 20
$$$EOF**
Figure 89. Output in IPF table format required for MERGE function
3.2.5.6 MERGING transaction definitions to the DTSECTXN table
One of the options on the Define Transaction Security dialog is the 6=MERGE;
see Figure 81 on page 96. This option may be used to help migrate your
transactions from your current system. This option may also be used when you
have done a Service upgrade or an Fast Service Upgrade (FSU). The input to
the MERGE function is a library member in IPF table format.
104 VSE/ESA V2R4
If your definitions are in DTSECTXN macro definitions, there is a REXX procedure
called IPFTABLE in IJSYSRS.SYSLIB to convert to IPF table format; see Figure 90
on page 105.
/* *******************************************/
/* FUNCTION: */
/* THIS EXEC TRANSFORMS A MEMBER IN MACRO */
/* FORMAT TO A MEMBER IN IPF TABLE FORMAT. */
/* THE INPUT MEMBER AND OUTPUT MEMBER NAMES */
/* CAN BE GIVEN AS CALL ARGUMENTS. */
/* IF NO ARGUMENTS ARE GIVEN, DEFAULT IS */
/* PRD2.CONFIG.DTSECTXS.A AS INPUT AND */
/* IJSYSRS.SYSLIB.DTRISEC.Z AS OUTPUT. */
/* *******************************************/
Figure 90. IPFTABLE REXX procedure description
Figure 91 shows sample JCL to execute this procedure.
* $$ JOB JNM=IPFTABLE,CLASS=0
// JOB IPFTABLE
// EXEC LIBR
ACC S=PRD2.SAVE
CATALOG INTRANS.A R=Y
DTSECTXN NAME=TRN1,TRANSEC=(10)
DTSECTXN NAME=TSRES2.TRN2,TRANSEC=(05)
DTSECTXN NAME=TSRES3.TRN2,TRANSEC=(10)
/+
/*
// LIBDEF PROC,SEARCH=PRD2.CONFIG
// EXEC REXX=IPFTABLE,PARM='PRD2.SAVE.INTRANS.A PRD2.SAVE.OUTTRANS.Z'
/*
// EXEC LIBR
ACCESS S=PRD2.SAVE
LIST OUTTRANS.Z
/&
* $$ eoj
Figure 91. Sample JCL to execute the IPFTABLE procedure
Figure 92 on page 106 shows sample output after executing the IPFTABLE REXX
procedure.
Chapter 3. Security 105
// JOB IPFTABLE
// EXEC LIBR
ACCESS S=PRD2.SAVE
L113I RETURN CODE OF ACCESS IS 0
LIST INTRANS.A . .
MEMBER=INTRANS.A SUBLIBRARY=PRD2.SAVE DATE:1999-04-08
TIME: 11:12
------------------------------------------------------------------------
DTSECTXN NAME=TRN1,TRANSEC=(05)
DTSECTXN NAME=TSRES2.TRN2,TRANSEC=(05)
DTSECTXN NAME=TSRES3.TRN2,TRANSEC=(10)
DTSECTXN NAME=TRN3,TRANSEC=(10)
DTSECTXN NAME=TRN4,TRANSEC=(10)
L113I RETURN CODE OF LIST IS 0
1S55I LAST RETURN CODE WAS 0004
// LIBDEF PROC,SEARCH=PRD2.CONFIG
1S55I LAST RETURN CODE WAS 0004
// LIBDEF PROC,SEARCH=PRD2.CONFIG
// EXEC REXX=IPFTABLE,PARM='PRD2.SAVE.INTRANS.A PRD2.SAVE.OUTTRANS.Z'. .
1S55I LAST RETURN CODE WAS 0000
EOP IPFTABLE
// EXEC LIBR
ACCESS S=PRD2.SAVE
L113I RETURN CODE OF ACCESS IS 0
LIST OUTTRANS.Z . .
MEMBER=OUTTRANS.Z SUBLIBRARY=PRD2.SAVE DATE:1999-04-08
TIME: 11:12
-------------------------------------------------------------------------
$$$005**TRANSID REGION CLASS CHANGED SUBTYPE
$$$005**K K
$$$005**TRN1 05
$$$005**TRN2 TSRES2 05
$$$005**TRN2 TSRES3 10
$$$005**TRN3 10
$$$005**TRN4 10
$$$EOF**
L113I RETURN CODE OF LIST IS 0
1S55I LAST RETURN CODE WAS 0000
EOJ IPFTABLE MAX.RETURN CODE=0000
Figure 92. Sample output of executing the IPFTABLE REXX procedure
. . INTRANS is in DTSECTXN macro format.
. . This is the IPFTABLE procedure.
. . OUTTRANS is in IPF table format for the MERGE function.
When you have your IPF table file as in Figure 92, use this file as input to the
MERGE option; see Figure 93 on page 107.
106 VSE/ESA V2R4
TAS$SEC3 DEFINE TRANSACTION SECURITY: MERGE TABLES
Enter the required data and press ENTER.
Specify the library member you want to be merged to the
transaction security table.
MEMBER NAME.................. outtrans Enter the member name.. .
MEMBER TYPE.................. z_______ Enter the member type.
LIBRARY...................... prd2___ Enter the library name.
SUBLIBRARY................... save____ Enter the sublibrary name.
PF1=HELP 2=REDISPLAY 3=END
Figure 93. Merge table dialog
. . This is the output file from the IPFTABLE procedure.
Press Enter and the SECMAC member in ICCF library 51 will be updated.
You can now check that your transactions are there by displaying them and then
PROCESS them. PROCESS will submit the batch job to catalog the macro and
assemble the DTSECTXN phase; see Figure 84 on page 98.
3.2.6 CICS default user ID
All CICS TS tasks now have an associated user ID. If a task is started that does
not have an associated user ID, the default user ID from the system initialization
parameter DFLTUSER= is used.
You must define a default CICS user ID to your security manager. If using an
ESM, the system initialization parameters SEC=YES and DFLTUSER=name
must be specified. The default user ID name must also be defined to the ESM. If
no default CICS user ID is specified, CICSUSER is the default ID.
CICS uses the security attributes of the default user ID to perform all security
checks for any terminal users that do not sign-on using the CESN sign-on
transaction.
These security checks using the default user ID apply to transaction-attach
security checking. Resource and command checks are not supported by the
BSM.
Attention
Remember, this default user ID is universally available so limit the resources
you intend to make available to the default ID.
On CICS initialization, the default user ID is signed-on. See Figure 94 on
page 108 for details.
Chapter 3. Security 107
R1 0045 DFHSM0122I TSRES3 Limit of DSA storage below 16MB is 5,120K.
R1 0045 DFHSM0123I TSRES3 Limit of DSA storage above 16MB is 12M.
R1 0045 DFHSM0113I TSRES3 Storage protection is not active.
R1 0087 DFHDM0101I TSRES3 CICS is initializing.
R1 0088 DFHXS1100I TSRES3 Security initialization has started.
R1 0088 DFHSI1500 TSRES3 CICS startup is in progress for CICS Transaction
Server Version 1.1.0
R1 0088 DFHSI1501I TSRES3 Loading CICS nucleus.
R1 0088 DFHXS1105 TSRES3 Resource profiles for class TCICSTRN have been built.
R1 0088 DFHXS1103I TSRES3 Default security for user ID CICSUSER has been
established.. .
R1 0088 DFHXS1101I TSRES3 Security initialization has ended.
R1 0088 DFHMN0105I TSRES3 Using default Monitoring Control Table.
Figure 94. Initialization of CICS TS with default user ID of CICSUSER
. . Default user ID of CICSUSER.
Figure 95 shows the shutdown of CICS TS with the default user ID CICSUSER.
DFHTM1703 TSRES3 CICS is being terminated by user ID CICSUSER in
transaction CEMT at terminal CO01.. .
IST804I CLOSE IN PROGRESS FOR TSRES3 OPENED BY DFHEVID1
Figure 95. Shutdown of CICS TS with default user ID CICSUSER
. . Default user ID of CICSUSER.
If changing the default user ID, remember this default user ID must be defined to
the BSM in the VSE.CONTROL.FILE. If the default user ID is not found,
initialization of CICS will terminate; see Figure 96.
// SETPFIX LIMIT=256K
ID (PARAMETERS SUPPRESSED)
// EXEC PROC=TSRES3
R1 0087 DFHXS1104 TSRES3
Default security could not be established for user Id CICSRES3. The. .
security domain cannot continue, so CICS is terminated. SAF codes
(X'00000004',X'00002000'). ESM codes are (X'00000004',X'00000000
R1 0045 DFHKE1800 TSRES3 ABNORMAL TERMINATION OF CICS IS COMPLETE.
Figure 96. CICS startup failure when default user ID not defined
. . CICSRES3 ID was defined as the default user ID but was not defined
in the VSE.CONTROL.FILE.
To define the default user ID to the BSM, see Figure 97 on page 109 for an
example.
108 VSE/ESA V2R4
IESADMUPBA ADD OR CHANGE USER PROFILE
Base II CICS ResClass ICCF
To CHANGE, alter any of the entries except the user Id.
USERID............. CICSRES3 4 - 8 characters (4 characters for ICCF users)
INITIAL PASSWORD... ________ 3 - 8 characters
There is a new system initialization
DAYS............... 000 0-365 Number of days before password expires
REVOKE DATE........ ________ Date when Userid will be revoked (mm/dd/yy)
USER TYPE.......... 3 1=Administrator, 2=Programmer, 3=General
INITIAL NAME....... DFLESEL Initial function performed at signon
NAME TYPE.......... 2 1=Application, 2=Selection Panel
SYNONYM MODEL...... ________ Userid to be used as model for synonyms
PF1=HELP 3=END 5=UPDATE
8=FORWARD
Figure 97. Definition of the new default user ID
3.2.6.1 Use of the default user ID
Some resources now have additional keywords to specify a user ID. An example
is the DCT. In the DFHDCT TYPE=INITIAL macro you can specify the new
USERID parameter that is for trigger-level transactions not associated with a
terminal. CICS uses this user ID for security checking. If omitted, the CICS
default user ID specified on the system initialization parameter DFLTUSER is
used. If you migrate existing destination control tables that do not specify a user
ID for trigger-level transactions, CICS TS issues the transaction-attach security
check against the CICS default user ID.
The EXEC CICS START command has a new user ID parameter, USERID. This
allows the transaction to run with the authority of the USERID specified.
The default USERID is also specified for multiregion security; see 3.2.10.2,
“Multiregion (MRO) security (not supported by the BSM)” on page 110.
3.2.7 Security for program list table (PLT) programs at startup
There is a new system initialization parameter called PLTPIUSR that specifies
the user ID that CICS is to use for security checking for PLT programs that run
during CICS initialization. With the new system initialization parameter
PLTPISEC you can specify the type of security checking to be performed, (none,
command, resource, or all). The PLT programs run under a new CICS-supplied
transaction, CPLT.
3.2.8 Resource security checking (not supported by the BSM)
A further level of transaction security can be implemented by controlling access
to the resources that the CICS transaction uses. This resource checking can be
specified at the individual transaction level. The system initialization parameter
required for transaction resource level checking is RESSEC=.
Chapter 3. Security 109
The transaction definition requires the RESSEC= parameter set. (The RESSEC
parameter is called RSLC in previous releases of CICS. RSLC(EXTERNAL) can
be specified in compatibility mode only.)
Other system initialization parameters and transaction definition parameters are
required for full CICS transaction resource checking when using an external
security manager (ESM).
3.2.9 Surrogate user security (not supported by the BSM)
Surrogate users allow users to start work on behalf of another user. The system
initialization parameter XUSER=NO|YES specifies whether CICS is to perform
surrogate user checking where such a check is permitted.
CICS uses the ESM to verify the authority of one user (the surrogate user) to
submit a transaction on behalf of another user.
3.2.10 Security on intercommunication
If you have existing intercommunication definitions for MRO, ISC, or APPC under
CICS/VSE 2.3, then you must review the CONNECTION and SESSION parameters
in your CSD, or your SYSTEM definitions in your DFHTCT.
During IPL of VSE/ESA 2.4, the intercommunication program DFHIRP is loaded
into the SVA, and is used for any communication session irrespective of the
CICS level.
3.2.10.1 APPC (LU6.2) session security
If you have an existing APPC connection, and you have defined the connection
with a BINDPASSWORD, you have to decide whether to continue using CICS bind
security.
The method you use for bind security on LU6.2 connections depends on the
capabilities of your ESM:
If your ESM supports bind-time session security, you can use the facilities
provided by the APPCLU general resource class, and specify XAPPC=YES
as a system initialization parameter. Defining BINDSECURITY=YES on your
CONNECTION resource definition indicates that you want bind-time security
checking on your connection.
If your ESM does not support bind-time security (for example, the BSM) you
can continue to use the BINDPASSWORD option on the CONNECTION
resource definition. You have to specify XAPPC=NO as a system
initialization parameter and BINDSECURITY=NO on the CONNECTION
resource definition. CICS then uses the BINDPASSWORD.
3.2.10.2 Multiregion (MRO) security (not supported by the BSM)
If you have existing MRO connections, and you have coded the SECURITYNAME
parameter on the CONNECTION definition in the CSD, or as part of your SYSTEM
definition in a DFHTCT, be aware that this parameter is no longer used for
bind-time security checking, nor is it used for any other security purpose on
MRO links. The internal security check mechanisms that were performed on
previous releases have been replaced by calls to the ESM via the SAF interface.
If you have coded the OPERSECURITY or OPERRSL parameters on the SESSION
definition, these are obsolete under the CICS TS. Under CICS TS, the method of
110 VSE/ESA V2R4
supplying a user ID for link security is the USERID parameter of the SESSIONS
definition. If you do not specify a USERID in the SESSIONS definition, CICS uses
the connecting region's user ID as the default link user ID.
To establish whether you want link security checking, or whether it is to be
bypassed, CICS compares its own region ID with the ID being passed in the
USERID parameter of the SESSION definition, or the user ID of the connecting
region if it was not supplied in the SESSION definition.
If the user IDs are the same, link security checking is bypassed.
If the user IDs are different, then CICS signs-on the link user ID as passed on
the SESSION definition, and uses this ID for all link security checks.
When link security is bypassed, security checking is determined by the
ATTACHSEC parameter on the CONNECTION definition.
See Table 8 for the relationship between ATTACHSEC and link security.
Table 8. MRO security options
Link Security ATTACHSEC (LOCAL) ATTACHSEC (IDENTIFY)
Yes CICS ignores the user ID CICS uses two security
associated with the checks, one against the
transaction, and issues user ID associated with
all security checks the transaction, and one
against the user ID only. against the link user ID,
ensuring that the
transaction cannot
access resources not
authorized for the link.
Bypassed CICS issues all security CICS issues security
checks against the CICS checks against the user
default user id ( the user ID associated with the
ID specified on the transaction.
DFLTUSER system
initialization parameter).
3.2.11 CICS Report Controller
Changes have been made to report security and printer security in CICS TS.
The basic security manager (BSM) does not handle report security requirements.
An external security manager (ESM) is required.
CICS TS will continue to support RSL values for reports. Because there are no
RSL values defined to a user now, security for reports is passed by RACROUTE
calls through the VSE/ESA System Authorization Facility (SAF) to the ESM.
See CICS Transaction Server for VSE/ESA Security Guide and CICS Transaction
Server for VSE/ESA Report Controller Planning Guide for more security
information.
Chapter 3. Security 111
3.2.12 Printer security
Printer security is also handled with RACROUTE calls to an ESM. A user ID is
associated with the printer and used by the ESM.
3.2.13 Terminal security
There are no OPERRSL or OPERSEC parameters in terminal definitions. There
is a preset user ID used by the ESM. Every CICS task has an associated user ID.
3.3 Security Migration Aid (SMA)
To assist in the migration of CICS Transaction Server for VSE/ESA R1 internal
security to either the VSE/ESA V2R4 supplied basic security manager (BSM) or a
fully functional external security manager (ESM), there is a utility called the
Security Migration Aid (SMA).
This utility helps you convert your existing CICS internal security definitions into
a format acceptable to a security manager. It is a two-phase utility. Only a brief
description of the SMA is provided here with a sample REXX exec that has been
written to process CICS transaction information for migrating to the BSM.
Documentation on the SMA is found in CICS Transaction Server for VSE/ESA
Security Guide .
3.3.1 SMA phase one
SMA phase one is a suite of menu-driven online programs designed to extract
security related data from the CICS system upon which it is run. Output of phase
one is a VSAM KSDS file. Run this tool against each existing CICS system that
you want to migrate to CICS TS. Phase one utility is shipped with CICS/VSE 2.3
and CICS TS.
During the extract processing SMA will also analyze the data extracted and
advise of any potential problems which you may need to investigate, such as:
1. Duplicate USERIDs between DFHSNT, DFHTCT and the VSE/ESA II.
2. USER IDs that may have been generated during assembly of the DFHSNT
when USERID has not been specified.
3. When no USERID has been specified on a terminal definition when preset
security (OPERSEC,OPERRSL) has been specified.
3.3.2 Installation of the Security Migration Aid (SMA)
There are various steps required to install and enable the Security Migration Aid
(SMA).
1. Define the SMA programs, mapsets and transactions.
2. Define the VSAM file for the SMA to record its data.
3. Define this VSAM file to the CICS.
4. Add the VSAM file to the CICS startup.
When defining the Security Migration Aid (SMA), you must be aware of the
security options on your system so you can access the resources. The Security
Migration Aid (SMA) uses the system programming commands and system
resources that require the appropriate CICS sign-on security.
112 VSE/ESA V2R4
3.3.3 Use of the Security Migration Aid (SMA)
After installing the SMA, use the CESM transaction to display the SMA main
menu panel XSM01. From this panel you can select options to update/replace
the data for various resource groups and store the information in the DFHXSMA
file.
On panel XSM02, you may select the various resource groups for which security
migration is available.
Transient Data (DCT)
Files (FCT)
Journals (JCT)
Transactions (PCT)
Programs (PPT)
USER Profiles (IUI/SNT/TCT)
RCF authorized printers (TCT)
Temporary Storage (TST)
By selecting the various resource groups, the data is written to the DFHXSMA
file. This file can then be used to provide input for setting up your security on
the BSM or an ESM.
3.3.4 Using the DTSECTX2 REXX procedure
A REXX procedure DTSECTX2 is available that reads the VSAM file created by
running the SMA phase one (DFHXSMA). This REXX procedure is provided in
ICCF library 59 with the name SKSECTX2. It extracts transaction information and
creates either a DTSECTXN macro file or an IPF table file. See Figure 98 on
page 114 for a description of the REXX procedure.
Chapter 3. Security 113
/***************************************************************/
/* FUNCTION: */
/* This EXEC reads a VSAM file created by the CICS Security */
/* Migration Aid - stage one. The read input is used to create */
/* a file containing the equivalent DTSECTXN transaction */
/* definitions for CICS TS. */
/* */
/* Parameters are: */
/* INFILE= VSAM name of the file created by the CICS */
/* Security Migration Aid */
/* FORMAT={IPF|MACRO} */
/* defines the format of the output file */
/* IPF is the format usable by the Interactive */
/* Interface dialog "Define Transaction Security", */
/* to merge security entries for transactions. */
/* This is the default. */
/* MACRO is the format consisting of DTSECTXN-macro */
/* definitions. */
/* definitions. */
/* OUTFILE= Librarian name of the file to be created */
/* containing the DTSECTXN definitions */
/* Default is PRD2.CONFIG.DTRISEC.M for IPF-format */
/* and PRD2.CONFIG.DTSECTXS.A for Macro-format */
/* CATALOG= Catalog name for the VSAM file */
/* Default is IJSYSCT */
/* REGION= Name of the CICS-region to include into the */
/* DTSECTXN definitions */
/* Default is the region name found in the */
/* VSAM file. */
/* If region name should not be included into */
/* a DTSECTXN definition, specify REGION= */
/* followed by blank */
/* */
/* Invocation samples: */
/* */
/* // EXEC REXX=DTSECTX2,PARM='INFILE=CICS.DFHXSMA X*/
/* OUTFILE=LIB.SLIB.DTSECTX2.A REGION=DBDCCICS' */
/* when using PARM-operand to specify parameters */
/* */
/* // EXEC REXX=DTSECTX2 */
/* INFILE=VSEESA.DFHXSMA */
/* CATALOG=IJSYSCT */
/* FORMAT=MACRO */
/* OUTFILE=LIB.SLIB.DTSECTX2.A */
/* REGION= */
/* when using SYSIPT to specify parameters */
/* */
/* Return codes: */
/* 0 successful */
/* 4 Unsupported character in transaction name */
/* 8 Output member exists already */
/* 12 Reading of VSAM file failed */
/* 16 Transaction name longer than 4 characters */
/* 24 No transaction specifications found */
/* 28 Writing output member failed */
/* */
/***************************************************************/
Figure 98. DTSECTX2 REXX procedure
The output of the REXX procedure is a file in either the DTSECTXN macro format
or the IPF table format. The use of the output file is the same as using the
output file of the DTSECTXS REXX procedure discussed in 3.2.5.5, “Converting
the DFHPCT (DTSECTXS REXX Procedure)” on page 100.
114 VSE/ESA V2R4
Figure 99 on page 115 shows a sample job for running this REXX procedure.
* $$ JOB JNM=DTSECTX2,CLASS=0,PRI=8,DISP=D
// JOB DTSECTX2 CREATE DTSECTXN DEFINITIONS FOR TRANSACTIONS
// EXEC LIBR
ACCESS S=PRD2.CONFIG
DELETE DTSECTX2.A
/*
// LIBDEF *,SEARCH=(PRD2.CONFIG,PRD1.BASE)
// EXEC REXX=DTSECTX2
INFILE=VSE23.DFHXSMA . .
OUTFILE=PRD2.CONFIG.DTSECTX2.A . .
FORMAT=MACRO . .
CATALOG=VSESPUC
/*
/&
* $$ EOJ
Figure 99. Sample job for executing DTSECTX2 REXX procedure
. . Input VSAM file created from phase one of the SMA.
. . Output file of REXX procedure DTSECTX2.
. . Output format either DTSECTXN macro definitions or IPF Table.
Figure 100 shows sample macro output for this REXX procedure.
DTSECTXN NAME=OLDCICS .APVU,TRANSEC=(61),SUBTYPE=INITIAL
DTSECTXN NAME=OLDCICS .ARPS,TRANSEC=(1)
DTSECTXN NAME=OLDCICS .CATD,TRANSEC=(1)
DTSECTXN NAME=OLDCICS .CAUT,TRANSEC=(1)
DTSECTXN NAME=OLDCICS .CCMF,TRANSEC=(1)
DTSECTXN NAME=OLDCICS .CDTS,TRANSEC=(1)
Figure 100. Sample DTSECTXN macro output of REXX procedure DTSECTX2
Figure 101 shows sample IPF table output for this REXX procedure.
Created definitions in < PRD2.CONFIG.DTSECTX2.A >:
$$$005**APVU OLDCICS 61
$$$005**ARPS OLDCICS 1
$$$005**CATD OLDCICS 1
$$$005**CAUT OLDCICS 1
$$$005**CCMF OLDCICS 1
$$$005**CDTS OLDCICS 1
$$$005**CEBR OLDCICS 60
Figure 101. Sample IPF table output of the REXX procedure DTSECTX2
Chapter 3. Security 115
3.3.5 SMA phase two
Phase two of the Security Migration Aid will be provided by the ESM vendors.
3.4 Summary of security
Full system security requires a vendor supplied external security manager
(ESM). The basic security manager (BSM) supplied with VSE/ESA Version 2
Release 4 provides only the sign-on and transaction-attach security for your
CICS Transaction Server for VSE/ESA R1.
The following points need to be considered in looking at the security on your
system when migrating to the CICS Transaction Server for VSE/ESA R1 using
only the BSM.
Move your users defined in either the DFHSNT table or the DTSECTAB table
to the VSE.CONTROL.FILE.
Define the users with the transaction security keys they require.
Look at the security information from your DFHPCT or CSD for your
transactions and redefine in the DTSECTXN table.
Define the transaction security classes the transactions require.
Review the security on the CICS-supplied transactions and modify them as
required.
Check any vendor or in-house programs that were using the DFHSEC macro.
Check your use and definition of the DCT for the default user ID checking.
Check your use of the programs in the PLTPI for default user ID checking.
Introduce your users to the new sign-on and sign-off transactions, CESN and
CESF.
Review any intercommunications on your CICS TS system and the security
definitions required or removed. Security of the MRO, APPC and ISC
connections need to be reviewed.
For full documentation on any security issues with the VSE/ESA Version 2
Release 4 and the CICS Transaction Server for VSE/ESA R1, refer to CICS
Transaction Server for VSE/ESA Security Guide .
116 VSE/ESA V2R4
Chapter 4. CICS coexistence
If applications executing within a CICS/VSE 2.3 production system cannot be
migrated to the CICS TS completely, you may have to do the following:
1. Migrate as much as possible first, and
2. Have applications that cannot be migrated because of incompatibilities
executing in CICS/VSE 2.3.
Applications that are written in macro-level assembler, RPG, or DOS PL/I
command level cannot be supported under CICS Transaction Server, but can
continue to run in a CICS/VSE 2.3 system, sharing data owned by the CICS TS.
In the same way, BTAM terminals are not supported by the CICS TS and they
must remain defined to a CICS/VSE 2.3 system.
Coexistence in this chapter refers to the existence of applications executing both
in a CICS TS and CICS/VSE 2.3 environment where incompatibilities force the
coexistence.
With coexistence, you should consider the following points:
How long will coexistence be necessary?
− What plans are in place to redevelop applications written in incompatible
languages, and are these applications in-house, or vendor products?
− Is source code available to make changes, or is a rewrite necessary?
− When will BTAM terminals be replaced?
The period of coexistence will have a bearing on the following:
How users will access their applications
− Perhaps you can implement an MRO environment (if one does not
already exist) to make application execution as transparent as possible
for users, or
− Have other alternatives such as multiple sessions for each user, or
multiple sign-on requirements
How data will be shared between CICS TS and CICS/VSE 2.3
Sharing of data has overhead so you must determine what should be
shared, and what should be non-shared.
What preparation is needed to move CICS/VSE 2.3 system definitions to a
CICS TS environment in the future.
This chapter outlines ways how you can use the coexistence environment.
© Copyright IBM Corp. 1999 117
4.1 CSD considerations in a coexistence environment
The CSD file is a VSAM KSDS dataset with the following characteristics:
It can be shared between CICS systems of the same release level, and
between CICS TS and CICS/VSE 2.3.
Sharing the CSD across multiple CICS partitions within a single or multiple
VSE image enables those partitions to use the same definition of resources,
and means that there is no need for duplication of definitions or datasets.
It can be separately defined for exclusive use by each individual CICS region
or partition.
Using separate CSD files for each CICS region or partition provides a way of
isolating definitions for testing of incompatibilities which may exist between
releases of CICS for resource definitions.
The CSD file contains definitions of resources used within the CICS system. You
supply these definitions by the use of the online transactions CEDA, CEDB and
CEDC. Once defined, resources are installed into an active CICS system from the
CSD file.
The CSD file does not contain resource definitions contained in CICS macro
tables such as DFHPCT, DFHPPT, DFHTCT, DFHFCT and so on which were used
in prior releases to define resource definitions to a CICS system.
Macro tables are still supported under CICS/VSE 2.3, but if you are migrating
your applications to the CICS TS and if you have any of the following definitions,
you must migrate these tables to the CSD:
All of your PCT
All of your PPT
VTAM TCT entries
You should use the CSD utility program DFHCSDUP to migrate your PCT, PPT or
TCT tables to the CSD.
The methods that can be used to define resources to CICS are found in Table 9.
Table 9 (Page 1 of 2). Methods of Defining Resources
Method Description Advantages Disadvantages
RDO This method uses RDO is used while Because RDO
the CEDx CICS is running. operates on an
transaction which This allows easy active system, a
allows definition, access to potential failure
alteration and resource may occur
installation of definitions. because of
resources in a definitions.
running CICS Auditing may be
system. required as a
control
mechanism.
118 VSE/ESA V2R4
Table 9 (Page 2 of 2). Methods of Defining Resources
Method Description Advantages Disadvantages
EXEC CICS Allows definition Allows Definitions are not
CREATE system of resources administration of placed in the CSD
command without CICS systems file and are lost
referencing the under program during a COLD
CSD file. control. start of CICS.
DFHCSDUP Offline utility that You can code You cannot install
allows you to large volumes of resources into an
define and modify definitions in one active CICS
resources using a job system.
batch job.
Autoinstall Applies to VTAM Reduces Time spent
terminals, LU 6.2 overheads of time setting up
sessions, defining static autoinstall.
programs, definitions, and
mapsets, and storage for
partitionsets that definitions.
use a model to
create resources
dynamically based
on the model.
Macro You code and Where possible, CICS must be
assemble use RDO or the stopped and
macroinstructions other methods. restarted to
to define activate any
resources in the alterations to
form of tables. tables, and time is
consumed while
assemblies
generate macro
tables.
Table 10 shows CICS resources, and how they can be defined to a running CICS
system.
For a full description on how to implement your resource definitions, refer to
CICS Transaction Server for VSE/ESA Resource Definition Guide .
Table 10 (Page 1 of 2). Resource Definition Methods
Resource Method CICS TS Method CICS/VSE 2.3
Define connection MUST use RDO. Use RDO. May use
DFHTCT macro.
DL/I VSE databases MUST use DLZACT. MUST use DLZACT.
Data Tables SHOULD use RDO. MUST use DFHFCT
macro.
Files (DAM) MUST use DFHFCT MUST use DFHFCT
macro. macro.
Files (VSAM) SHOULD use RDO. MUST use DFHFCT
macro.
Journals MUST use DFHJCT MUST use DFHJCT
macro. macro.
LSR pools SHOULD use RDO. MUST use DFHFCT.
Chapter 4. CICS coexistence 119
Table 10 (Page 2 of 2). Resource Definition Methods
Resource Method CICS TS Method CICS/VSE 2.3
Mapsets MUST use RDO. Use RDO. May use
DFHPPT macro.
Partitionsets MUST use RDO. May use DFHPPT macro.
Partners MUST use RDO. Not available.
Profiles MUST use RDO. Use RDO. May use
DFHPCT macro.
Programs MUST use RDO. Use RDO. May use
DFHPPT macro.
Queues (destinations) Use DFHDCT macro. Use DFHDCT macro.
Sessions MUST use RDO. Use Rdo. May use
DFHTCT macro.
Temporary storage Use DFHTST macro. Use DFHTST macro.
Terminals( Non VTAM) Use DFHTCT macro. Use DFHTCT macro.
Terminals (VTAM) MUST use RDO. Use RDO. May use
DFHTCT macro.
Transactions MUST use RDO. Use RDO. May use
DFHPCT macro.
Transactions classes MUST use RDO. Not used.
Typeterms MUST use RDO. Use RDO. May use
DFHTCT.
Notes:
If a DFHTCT macro has been coded in CICS/VSE 2.3 to explicitly define
each terminal, then typeterm definition is not required.
Table entries in CICS/VSE 2.3 should be migrated to RDO where
available.
4.2 Sharing the CSD between CICS TS and CICS/VSE 2.3
The sharing of the CSD is not a new function in VSE/ESA 2.4 and the CICS TS.
The CSD file could be shared in previous releases of CICS/VSE. If you are
already sharing the CSD between CICS partitions in a single VSE image, or
between multiple VSE images, then you may continue to do so in a coexistence
environment.
However, in a coexistence environment, certain methods should be employed to
ensure integrity of the CSD, as described in the following sections.
4.2.1 Shared access from within the same CICS partition
Several users within a single CICS partition can access the CSD at the same
time, providing that the CSD has read/write access from within the CICS
partition. CICS file control manages concurrent access for multiple users within a
partition. For information on enabling read/write access to the CSD, refer to the
CSDACC system initialization parameter.
120 VSE/ESA V2R4
As shipped and installed with VSE/ESA 2.4, the DFHSITSP table for the
DBDCCICS system has the CSD file defined as read/write by the parameter
CSDACC=READWRITE.
The VSAM cluster definition for the CSD for DBDCCICS has SHR(2) for share
options.
If you are using the supplied tables of DFHSITC2 and DFHSITC3 (supplied in ICCF
library 59) to build additional CICS partitions or regions, you may need to change
the CSDACC parameter for these partitions to CSDACC=READONLY.
4.2.2 Shared access from several CICS regions (partitions) and batch
Note the following points:
Several users may access the CSD file in different CICS regions at the same
time.
Only one CICS region should be given read/write access to the CSD.
The CICS region that has the read/write access should be at the latest level,
to ensure that obsolete resource attributes from earlier releases can still be
updated safely. Other CICS regions should only be given read access to the
CSD. This ensures that the CSD integrity is preserved for CICS regions in the
same VSE image or different VSE images.
One method of updating the CSD from several regions is to use CICS
transaction routing, and MRO or ISC. Use the following procedure:
− One CICS TS region is to own the CSD (the CSD owning region), and
only in this region specify read/write access for the CSD.
− Define the CSD as read-only to other CICS regions (CICS/VSE 2.3 and
other CICS TS partitions)
− For all regions other than the CSD-owning region:
- Redefine the CEDB transaction as a remote transaction (to be run in
the CSD-owning region).
- Install the definition and add the group to the group list for these
regions.
The CEDB transaction may then be used from any CICS partition to change
the contents of the CSD file.
Use CEDA to install the definitions into the invoking region. (Note that CEDA
is not used to change the CSD in partitions that do not own the CSD).
If the CICS TS CSD-owning region fails, the CSD is not available through the
CEDB transaction until an emergency restart of the CICS TS CSD-owning
partition has been completed ( including any backout processing required for
the CSD). If an attempt is made to install a GROUP or LIST that is the target
of backout processing before an emergency restart has completed, it will fail
because of internal locking.
If the previously described method is not used, and the requirement is for
the CSD to be a recoverable resource, then integrity of the CSD cannot be
guaranteed.
Be aware that read integrity is not guaranteed for a CICS partition that has
read-only access to a CSD. If a CICS TS partition has full read/write access
and updates a shared CSD with new or changed definitions, another CICS
partition with read-only access might not obtain the updated information.
Chapter 4. CICS coexistence 121
This could happen if a control interval (CI) already held by a read-only
partition is updated by a read/write CICS partition.
Also be aware that if you are using the batch utility program DFHCSDUP, the
CSD file defined in the CICS TS partition may have to be closed, depending
on the share options of the VSAM file.
If you do not already have an MRO environment defined, you may use the
following tables to define an MRO environment that ships CEDB transactions
to the CICS TS system that is the CSD-owning region. Table 11 lists the
connection definition for the MRO environment:
Table 11. Connection definitions for MRO
Panel Line CSD-owning CICS/VSE 2.3 Comment
Connection CICA CICB SYSID in DFHSIT.
Group IRCCSD IRCC23 Arbitrary.
Netname CICS23 DBDCCICS Applid Name.
Accessmethod IRc IRc
Protocol Must be blank.
Autoconnect yes yes
Table 12 lists the session definitions for MRO:
Table 12. Session definitions for MRO
Panel Line CSD-owning CICS/VSE 2.3 Comment
Sessions CSDSOWN CICS23 Arbitrary.
Group IRCCSD IRCC23 See connection
group.
Connection CICA CICB SYSID in DFHSIT.
Protocol LU61 LU61
RECEIVEPtx TR PR
RECEIVECount 010 010
SENDPtx TS PS
SENDCount 010 010
SENDSize 4096 4096 Change as
required.
RECEIVESize 4096 4096 Change as
required.
OPERRsl 1 0 0 Default. Check
security.
OPERSecurity 1 1 1 Default. Check
security.
Autoconnect yes yes
INservice yes yes
RELreq yes yes
DIscreq yes yes
122 VSE/ESA V2R4
Notes:
1. Obsolete in CICS TS Release 1, but retained in compatibility mode for
earlier releases only. See also 4.2.3, “Obsolete attributes in the CSD in
mixed releases of CICS” on page 124.
After an MRO environment has been established, you can redefine the CEDB
transaction as being remote in all non CSD-owning CICS partitions.
The CEDA transaction definition is defined in the the GROUP DFHSPI, which
is IBM-protected. To be able to alter this definition for CEDB, you must copy
the definition to a private group. You can do this by entering the following
command from a CICS TS screen:
CEDA COPY TRANSACTION(CEDB) GROUP(DFHSPI) TO(IRCC23)
If the CEDA transaction has been secured, then you may have to sign on
before working with CEDA. There may be an informational message issued
after issuing the CEDA command. Press PF9 to view any messages.
To make the CEDB transaction a remote transaction that executes in the
CSD-owning CICS TS partition from the CICS/VSE 2.3 system, issue the
command:
CEDA ALTER TRANS(CEDB) GROUP(IRCC23) REMOTES(CICA)
When the MRO environment has been activated, the issue of the CEDB
transaction from a CICS/VSE 2.3 will be shipped to the CICS TS CSD-owning
region for execution in read/write mode.
The GROUPs IRCCSD and IRCC23 may be added to a GRPLIST name
specified in the DFHSIT for the CICS TS CSD-owning region and the
CICS/VSE 2.3 system, respectively. You can have up to four lists named on
GRPLIST parameter with CICS TS.
The CEDA transaction may be used in the CICS TS and the CICS/VSE 2.3
region to INSTALL each GROUP to make MRO active without performing a
restart of the CICS regions.
The system initialization parameters must be checked to ensure that the ISC
IRCSTRT parameters have been set to YES. The default parameters are set
to NO.
When using AUTOINSTALL terminals in an MRO environment between
CICS/VSE 2.3 and the CICS TS, a method of not generating the same
terminal ID in both CICS systems should be used.
ICCF library 59 contains members IESZATCO and IESZATDX, which are
sample autoinstall programs which you may alter, assemble and link-edit to
meet your needs. For example, you could use a prefix of A and B on
autoinstall terminals defined in the CICS TS system, and use a prefix of D
and E for autoinstall terminals defined in the CICS/VSE 2.3 system.
This would mean that a terminal autoinstalled in the CICS/VSE 2.3 partition
may have a terminal ID of D002, and when shipped to the CICS TS partition
to perform CEDB transactions, no autoinstalled terminal would be active with
a terminal ID of D002, since terminal IDs in the CICS TS system would all
have a prefix of A or B.
Chapter 4. CICS coexistence 123
4.2.3 Obsolete attributes in the CSD in mixed releases of CICS
Resource attributes become obsolete when they have no relevance for a new
release of CICS. The CICS TS continues to display obsolete attributes on CEDx
panels, but they are displayed as protected fields, indicating that they are not
supported by the CICS TS.
Using the ALTER command on definitions that specify obsolete attributes does
not cause the loss of these attributes when updating resources defined for
earlier releases of CICS from the CICS TS.
These unsupported attributes may be updated from within the CEDx transaction
by the use of the PF2 function key when in ALTER mode. Pressing PF2 converts
protected fields to unprotected fields for modification.
The CSD utility program DFHCSDUP can also be used under VSE/ESA 2.4 to
update resources that specify obsolete attributes. A compatibility option is
available for this purpose, by coding a PARM parameter on the EXEC DFHCSDUP
statement. There are two parameters, COMPAT and NOCOMPAT. COMPAT
means that obsolete attributes may be updated. NOCOMPAT is the default.
Figure 102, Figure 103 on page 125, and Figure 104 on page 125 show the
protected fields on the CEDA ALTER screens.
ALTER TRAN(OLDT) G(CICS23)
OVERTYPE TO MODIFY CICS RELEASE = 0410
CEDA ALter TRANSaction( OLDT )
TRANSaction : OLDT
Group : CICS23
DEscription ==>
PROGram ==> CICS23PG
TWasize ==> 00000 0-32767
PROFile ==> DFHCICST
PArtitionset ==>
STAtus ==> Enabled Enabled | Disabled
PRIMedsize : 00000 0-65520 . .
TASKDATALoc ==> Below Below | Any
TASKDATAKey ==> User User | Cics
STOrageclear ==> No No | Yes
RUnaway ==> System System | 0 | 500-2700000
SHutdown ==> Disabled Disabled | Enabled
REMOTE ATTRIBUTES
DYnamic ==> No No | Yes
+ REMOTESystem ==>
SYSID=CIC1 APPLID=DBDCCICS
. .
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 102. Screen 1 of CEDA ALTER
124 VSE/ESA V2R4
ALTER TRAN(OLDT) G(CICS23)
OVERTYPE TO MODIFY CICS RELEASE = 0410
CEDA ALter TRANSaction( OLDT )
+ REMOTEName ==>
TRProf ==>
Localq ==> No | Yes
SCHEDULING
PRIOrity ==> 000 0-255
TClass : 02 No | 1-10 . .
TRANClass ==> 3FHTCL01
ALIASES
Alias ==>
TASKReq ==>
XTRanid ==>
TPName ==>
==>
XTPname ==>
==>
==>
+ RECOVERY
SYSID=CIC1 APPLID=DBDCCICS
. .
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 103. Screen 2 of CEDA ALTER
ALTER TRAN(OLDT) G(CICS23)
OVERTYPE TO MODIFY CICS RELEASE = 0410
CEDA ALter TRANSaction( OLDT )
+ DTimout ==> No No | 1-6800
Indoubt ==> Backout Backout | Commit | Wait
RESTart ==> No No | Yes
SPurge ==> No No | Yes
TPUrge ==> No No | Yes
DUmp ==> Yes Yes | No
TRACe ==> Yes Yes | No
COnfdata ==> No No | Yes
SECURITY
RESSec ==> No No | Yes
CMdsec ==> No No | Yes
Extsec : No No | Yes . .
TRANSec : 01 1-64 . .
RSl : 00 0-24 | Public . .
SYSID=CIC1 APPLID=DBDCCICS
. ..
PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL
Figure 104. Screen 3 of CEDA ALTER
Notes:
. . The fields shown are protected until PF2 is pressed. They are
protected because they are obsolete under CICS TS.
Chapter 4. CICS coexistence 125
. . The PF2 key acts as a toggle key. Pressing this key alternately
protects and unprotects obsolete fields.
To execute utility program DFHCSDUP, the following JCL could be used to
modify obsolete fields in the DFHCSD file.
* $$ JOB JNM=DFHCSDUP,CLASS=0
// JOB DFHCSDUP
// LIBDEF PHASE,SEARCH=PRD1.BASE
// EXEC DFHCSDUP,SIZE=DFHCSDUP,PARM='COMPAT'
ALTER TRANS(OLDT) GROUP(CICS23) TRANSEC(03)
/*
/&
* $$ EOJ
Following is the printed output from the successful execution of the batch job
submitted.
// JOB DFHCSDUP
// LIBDEF PHASE,SEARCH=PRD1.BASE
// EXEC DFHCSDUP,SIZE=DFHCSDUP,PARM='COMPAT'
ALTER TRANS(OLDT) GROUP(CICS23) TRANSEC(03)
DFHCA5120 I PRIMARY CSD OPENED; FILENAME: DFHCSD
DFHCA5101 I ALTER COMMAND EXECUTED SUCCESSFULLY.
DFHCA5123 I PRIMARY CSD CLOSED; FILENAME: DFHCSD
DFHCA5107 I COMMANDS EXECUTED SUCCESSFULLY: 1 COMMANDS GIVING WARNING(S)
DFHCA5108 I COMMANDS NOT EXECUTED AFTER ERROR(S): 0
DFHCA5109 I END OF DFHCSDUP UTILITY JOB. HIGHEST RETURN CODE WAS: 0
1S55I LAST RETURN CODE WAS 0000
126 VSE/ESA V2R4
If the COMPAT parameter is omitted, the job is executed with warnings as shown
in the following:
// JOB DFHCSDUP
// LIBDEF PHASE,SEARCH=PRD1.BASE
// EXEC DFHCSDUP,SIZE=DFHCSDUP
ALTER TRANS(OLDT) GROUP(CICS23) TRANSEC(03)
DFHCA5214 W TRANSEC IS AN OBSOLETE KEYWORD. IT IS IGNORED.
DFHCA5120 I PRIMARY CSD OPENED; FILENAME: DFHCSD
DFHCA5102 I WARNING MESSAGE(S) ISSUED WHILE PROCESSING ALTER COMMAND.
DFHCA5123 I PRIMARY CSD CLOSED; FILENAME: DFHCSD
DFHCA5107 I COMMANDS EXECUTED SUCCESSFULLY: 0 COMMANDS GIVING WARNING
DFHCA5108 I COMMANDS NOT EXECUTED AFTER ERROR(S): 0
DFHCA5109 I END OF DFHCSDUP UTILITY JOB. HIGHEST RETURN CODE WAS: 4
1S55I LAST RETURN CODE WAS 0004
EOJ DFHCSDUP MAX.RETURN CODE=0004
4.3 Placing CICS/VSE 2.3 definitions in a shared CSD
The shared CSD file has been initialized for use by the CICS TS.
It should not be reinitialized prior to moving your definitions to the shared CSD.
To avoid defining non-compatible definitions in the CSD for your CICS/VSE 2.3
system, you should perform the following prior to adding your definitions in the
shared CSD file.
Chapter 4. CICS coexistence 127
* $$ JOB JNM=DFHCSDUP,CLASS=0,DISP=D
// JOB DFHCSDUP
// LIBDEF *,SEARCH=(PRD2.CONFIG,PRD2.SCEEBASE,PRD1.BASE)
* ******************************************************
* label DFHCSD is assumed to be in standard labels *
* ******************************************************
// EXEC DFHCSDUP,SIZE=DFHCSDUP
APPEND LIST(DFHLIST) to(CICS23L) . .
ADD GROUP(DFHCOMP1) LIST(CICS23L) . .
ADD GROUP(DFHCOMP2) LIST(CICS23L) . .
ADD GROUP(VSETYPE) LIST(CICS23L)
ADD GROUP(VSETERM) LIST(CICS23L)
ADD GROUP(VSETERM1) LIST(CICS23L)
* $$ SLI MEM=CEECCSD.Z S=(PRD2.SCEEBASE) . .
* $$ SLI MEM=IBMCCSD.Z S=(PRD2.SCEEBASE) . .
* $$ SLI MEM=IGZCCSD.Z S=(PRD2.SCEECICS) . .
* $$ SLI MEM=EDCCCSD.Z S=(PRD2.SCEEBASE) . .
ADD GROUP(CEE) LIST(CICS23L) . .
LIST ALL
/*
/&
* $$ EOJ
Notes:
. .Use your name for the GRPLIST name. This will create your group list
name (if it does not already exist) with the base CICS entries required to
initialize a CICS system without ICCF and the Interactive Interface (II).
ICCF and the II cannot be initialized in a CICS/VSE 2.3 system.
. .This is the compatibility group that contains entries for CICS/VSE 2.3
resources changed or made obsolete in CICS TS. This group must only
be added to the CICS/VSE 2.3 group list - do not add to your CICS TS
group list.
. .This is the compatibility group that contains entries for the CICS/VSE
2.3 Report Control Facility. This group must only be added to the
CICS/VSE 2.3 group list - do not add to your CICS TS group list.
. .These are the LE/VSE definitions required to initialize the Language
Environment.
. .These are the PLI/VSE definitions required to initialize support for
PLI/VSE, if needed.
. .These are the COBOL/VSE definitions required to initialize support for
COBOL/VSE, if needed.
. .These are the C/VSE definitions required to initialize support for
C/VSE, if needed.
. .The group CEE was created in steps . . to . . and now is added to
the group list.
During CICS/VSE 2.3 initialization, you may see the following CICS message:
128 VSE/ESA V2R4
DFH4887I I UNRECOGNIZED RESOURCE TYPE FOUND IN THE CSD FILE AND HAS BEEN
IGNORED
If you see this message, it means that CICS TS definitions have been included in
your group list at CICS startup. To avoid this message, remove any group
containing functions only available under the CICS TS, for example:
CEDB REMOVE GROUP(DFHFEPI) LIST(CICS23L)
CEDB REMOVE GROUP(DFHTCL) LIST(CICS23L)
CEDB REMOVE GROUP(DFHCLNT) LIST(CICS23L)
These commands must be issued from the CICS TS CSD-owning region.
After the group list (as defined in the job on page 128) has been defined, groups
containing application-orientated definitions can be merged from your old CSD
file (if available) or defined using the methods described in Table 9 on page 118.
Following is an example of copying your application definitions:
* $$ JOB JNM=CSDCOPY,CLASS=0
// JOB CSDCOPY
// DLBL OLDCSD,'CICS.CSD',,VSAM,CAT=USERCAT . .
* *******************************************************
* THE DLBL FOR THE DFHCSD FILE IS ASSUMED TO BE IN STANDARD LABELS
* *******************************************************
// EXEC DFHCSDUP,SIZE=DFHCSDUP COPY PREVIOUS CSD TO NEW TS CSD
COPY GROUP (PAYROLL) FROMCSD(OLDCSD)
COPY GROUP (INVENT) FROMCSD(OLDCSD)
* 1 copy statement for each of your application
* names - as many as required
*
ADD GROUP(PAYROLL) LIST(CICS23L) . .
ADD GROUP(INVENT) LIST(CICS23L)
* 1 add statement for each group
* copied from the old CSD file
* as above
/*
/&
* $$ EOJ
Notes:
. . Change this statement to agree with the correct name and catalog
where the previous release of VSE/ESA DFHCSD file resides.
. . The group list name is the same as defined in a previous release of
VSE/ESA. The list name agrees with the name described in the job on
page 128.
Previous IBM-protected definitions that you have copied to a private group and
modified, or that exist in your old CSD file should not be copied into the shared
CSD file. Any modifications that you have made should be recoded to suit your
needs.
Chapter 4. CICS coexistence 129
4.4 Separate CSD files in a coexistence environment
The CICS/VSE 2.3 CSD file currently in use in an existing VSE/ESA system can
be used unaltered under VSE/ESA 2.4 in a coexistence environment, provided it
is only accessed by CICS/VSE 2.3.
However, if you have definitions for a CICS/VSE 2.3 system that include ICCF
and/or the Interactive Interface, this environment is not supported in VSE/ESA
2.4, and these systems will not initialize, and must be migrated to CICS TS.
4.5 The Interactive Interface in a coexistence environment
The Interactive Interface (II or IUI) is only available with the CICS Transaction
Server, and cannot be executed under CICS/VSE 2.3.
If you have used the Interactive Interface to provide security for production
applications or defined Selection and Application panels as a front-end to your
CICS/VSE 2.3 system, then care should be taken in a coexistence environment
for applications that still need to execute in the CICS/VSE 2.3 environment.
If you are using the Interactive Interface for security control of applications, then
refer to the new security limitations as described in Chapter 3, “Security” on
page 73.
If you are using the Interactive Interface to front-end your applications, and need
to execute some or all of your applications under CICS/VSE 2.3, then some
redesign of your applications may be required; see Figure 105 on page 131 for
an example.
130 VSE/ESA V2R4
IESADMSL.MENU VSE/ESA FUNCTION SELECTION
APPLID: DB
Enter the number of your selection and press the ENTER key:
1 PAY SYSTEM
2 INVENTORY SYSTEM
3 DEBTORS
4 CREDITORS
PF1=HELP 3=SIGN OFF 6=ESC
9=Escape(m)
==>
Figure 105. User application screen
For example, a user may choose to access the DEBTORS system from the menu.
If this application still required CICS/VSE 2.3 for execution, then it would require
that the TRANSACTION definition be changed for remote execution (to be
executed under CICS/VSE 2.3) using MRO.
If there is a mixture of non-supported and supported programs within an
application suite, then addressability may be an issue. If this is the case, then
all programs within an application suite may be better suited to execute under
CICS/VSE 2.3 prior to removing any incompatibilities with the CICS TS. See
Table 11 on page 122 and Table 12 on page 122 for definitions on establishing
an MRO environment.
4.6 BTAM terminals
As stated earlier, BTAM terminals are not supported under the CICS TS.
Any application that requires access from a BTAM terminal or device will have
to be reviewed. Some options available for BTAM users are covered in 4.7, “
Migration options for coexistence” on page 132. You should consider the
following issues:
If the application has not been migrated to the CICS TS, then the transaction
would be executed within the CICS/VSE 2.3 system in which the terminal is
defined.
If the application has been migrated to the CICS TS, then you must do the
following:
1. Define the BTAM terminals to CICS/VSE 2.3.
Chapter 4. CICS coexistence 131
2. Define the terminals as being remote in the DFHTCT within the CICS TS.
3. Define the transaction as being remote within the CICS/VSE 2.3 system.
4.7 Migration options for coexistence
If you have a single region CICS environment, and there are elements that will
not easily migrate to the CICS TS, you could consider the following options:
Adopt an MRO solution that has two CICS regions, one executing CICS TS,
and one executing CICS/VSE 2.3, with transactions routed or function shipped
between both CICS regions.
For example, your single CICS/VSE 2.3 region may have a mixture of some
or all of the following :
− VTAM Terminals
VTAM terminal definitions present no difficulty for migration. If they are
defined in a DFHTCT table, then they must be migrated to the CSD either
as explicit definitions, or as autoinstall terminals. Refer to CICS
Transaction Server for VSE/ESA Resource Definition Guide for a
description of migrating your TCT definitions.
− BTAM Terminals
As BTAM terminals are not supported under CICS TS except as remote
terminals for ISC/MRO purposes, then you will have to do both of the
following:
- Define the terminals within your CICS/VSE 2.3 system.
- Define the terminals as being remote within your CICS TS system by
coding a DFHTCT TYPE=TERMINAL preceded by a DFHTCT
TYPE=REGION macro instruction. See CICS Transaction Server for
VSE/ESA Resource Definition Guide for information on generating a
TCT for remote terminal definitions.
− Command level applications
Command-level programs can be easily migrated to the CICS TS,
provided that they are written in a Language Environment
(LE)-conforming language. Programs compiled with RPG, C/370 and DOS
PL/I compilers are not supported and cannot be migrated.
If command-level programs access data files that are also accessed from
macro-level applications you will have to leave the data files on the
CICS/VSE 2.3 system, and define them as remote files on the CICS TS
region. The files are accessed by function-shipping the file requests.
− Macro-level applications
These are not supported under the CICS TS, and should be converted to
command-level, if possible. If they cannot be converted, then they must
remain in the CICS/VSE 2.3 environment.
− VSAM and DAM Files, transient data and temporary storage queues
Review the definitions for these files, and define them in either the CICS
TS, or in the CICS/VSE 2.3 region, or both, depending on need.
Figure 106 on page 133 illustrates this first option.
132 VSE/ESA V2R4
CICS/VSE 2.3 CICS TS
Transaction Routing (1)
Terminals: Terminals:
BTAM Transaction Routing (2) VTAM
Applications: Applications:
Macro-level Command-level
only only
Function Shipping (3) (4)
↓ ↓
Resources: Resources:
VSAM & DAM Files VSAM & DAM files
TD & TS queues TD & TS queues
for macro-level for command-level
applications only
Figure 106. Single CICS to coexistent VSE/ESA 2.3 and CICS TS - option 1
Note:
1. Transactions entered at BTAM terminals for applications that have
been migrated to CICS TS are routed to the CICS TS region for
execution.
The transactions must be coded as remote transactions to the
CICS/VSE 2.3 region, and you must include remote BTAM terminal
definitions in the TCT in the CICS TS region.
2. Transactions entered at VTAM terminals for applications that have not
been migrated to the CICS TS system are routed to the CICS/VSE 2.3
region for execution.
You must define the transactions as remote transactions to the CICS
TS region. You must also code the terminals in the CICS/VSE 2.3
system, or define them as being shippable terminals from within the
CICS TS region.
For information on coding remote terminals, or shippable terminals,
refer to CICS Transaction Server for VSE/ESA Resource Definition
Guide .
3. CICS does not support function shipping for macro-level programs.
Any resource that is accessed by macro-level applications must
remain in the CICS/VSE 2.3 region.
The resources owned by the CICS/VSE 2.3 region must be defined to
the CICS TS system as remote resources.
4. CICS TS does not support command-level programs compiled with the
C/370, RPG or DOS PL/I compilers. However, because CICS supports
the function shipping of command-level requests, these resources can
be defined as remote to the CICS/VSE 2.3 region.
Chapter 4. CICS coexistence 133
As an alternative to running two regions with their mixture of transaction routing
and function-shipping between the two regions, you could create a third region.
In this case, you could have the following:
1. A CICS/VSE 2.3 partition which acts as a terminal-owning region (TOR) which
supports BTAM terminals, (BTAM/TOR).
2. A CICS TS region that acts as a terminal-owning region and an
application-owning region (AOR) which supports all VTAM terminals and
migrated command-level applications (VTAM/TOR/AOR).
3. A CICS/VSE 2.3 region that acts as an AOR and a data-owning region (DOR)
which supports all macro-level applications, and all VSAM files that are
accessed by both macro-level and command-level applications (AOR/DOR).
Figure 107 illustrates this alternative option:
CICS/VSE CICS TS
2.3 TOR/AOR
TOR
Terminals Transaction Routing (3)
BTAM Applications
Command
level
CICS/VSE
2.3
AOR/DOR Function
Shipping (4)
Files
VSAM & DAM
Trans. all regions Terminals
Routing Transaction VTAM
(1) Applications Routing (2)
Macro-level
Figure 107. Single CICS to coexistent VSE/ESA 2.3 and CICS TS - option 2
Note:
1. Transactions entered at BTAM terminals for macro-level applications
are routed to the CICS/VSE 2.3 application-owning region (which is
also the data-owning region AOR/DOR).
2. Transactions that are entered at VTAM terminals for macro-level
applications are routed to the CICS/VSE 2.3 region, which is the
application-owning region and data-owning region (AOR/DOR).
3. Transactions entered at BTAM terminals for command-level
applications are routed to the CICS TS region VTAM/TOR/AOR.
4. Transactions entered at any terminal for command-level applications
are processed in the CICS TS VTAM/TOR/AOR, but file requests are
function-shipped to the CICS/VSE 2.3 AOR/DOR.
134 VSE/ESA V2R4
If you are running multi-region CICS systems, using either intercommunication
(ISC) or inter-region communication (IRC) facilities, and you have run in a
coexistence environment because of incompatibilities, you have to introduce a
CICS TS environment in a way that you can still use your CICS/VSE 2.3 regions
as well as the CICS TS. A solution for this type of environment is more complex
than that for a single CICS system.
A possible solution is illustrated in Figure 108
CICS/VSE CICS TS CICS TS
2.3 TOR AOR - 1 DOR
(1) Transaction Command-level Function (4)
Routing Applications Shipping
Terminals
VSAM & DAM
(2) files
VTAM
DL/I
CICS.VSE 2.3 DBs
AOR/DOR
Transaction Funct.
Routing Macro-level Ship
Applications
(3)
BTAM Files :
VSAM & DAM
DL/I DBs (5)
Funct.
Ship
CICS TS
AOR - 2
Transaction
Routing Command-level Function
Applications Shipping
(2)
Figure 108. Possible ISC/MRO with VSE/ESA 2.3 and CICS TS
Chapter 4. CICS coexistence 135
Notes:
a. The CICS/VSE 2.3 terminal-owning region supports both VTAM and BTAM
terminals.
All transactions are routed to application-owning regions.
b. The CICS TS application-owning regions (AOR-1 and AOR-2) are
essentially identical, and provide support for command-level applications
that have been migrated to the CICS TS.
c. The CICS/VSE 2.3 application-owning and data-owning region provides
the support for macro-level applications.
Macro-level applications cannot use function shipping, therefore data
accessed from these applications must reside in the same region.
Command-level applications not yet migrated could also execute in this
region.
d. The CICS TS data-owning region provides the support for the
applications executing in the CICS TS application-owning regions (AOR-1
and AOR-2).
e. The data managed by the CICS/VSE 2.3 application-owning/data-owning
region is not the same data as managed by the CICS TS data-owning
region.
4.8 Placing CICS phases into the SVA in a coexistence environment
The benefits of loading SVA-eligible phases into the SVA are:
Integrity
Phases loaded into the SVA are protected from being overwritten by other
programs as the SVA is key-0 protected.
Performance
If more than one copy of the same program is required in a multiple CICS
environment at the same time, the program can either reside in the SVA and
be accessed from each individual CICS partition, or a copy can be loaded
into each address space. By loading SVA eligible phases into the SVA, they
can be shared, thereby reducing the working set, and consequently the
demand for real storage.
There are certain CICS phases which must be loaded into the SVA; Table 13
shows a summary of the mandatory phases.
Table 13 (Page 1 of 2). Mandatory SVA modules
Module Description
DFHCSVC CICS SVC . .. .
DFHCSEOT CICS EOJ cleanup routine. Performs
cleanup for interregion communication
and shared data tables. CICS invokes
DFHCSEOT during its end-of-job
processing. If it cannot find DFHCSEOT
in the SVA, cleanup does not take place
and the interregion and shared data
table environments become unusable.
136 VSE/ESA V2R4
Table 13 (Page 2 of 2). Mandatory SVA modules
Module Description
DFHCDDAN The CPC dead data anchor block
DFHCSSDAN must be loaded into the
SVA in a dual-CPC XRF environment.
Although DFHCDDAN is not read-only, it
must still reside in the SVA.
DFHIRP Interregion communication program. If
you are using MRO, DFHIRP must be
used from the SVA for integrity reasons.
DFHCSTE and DFHIRW10 Subsystem control table extension. If
you are using MRO, DFHCSTE provides
an anchor for the interregion
communication control block structure.
Although DFHCSTE is not read-only, it
must still be placed in the SVA.
DFHDSPEX The CICS post-exit stub. . .
DFHDTSVC CICS module for data tables.
DFHDTSAN CICS module for data tables.
Notes:
. .Can only be used from the SVA and must be installed into the SVA
before CICS can be started.
. .To communicate using MRO, all CICS regions in the same VSE image
must use the latest levels of the MODULES DFHCSVC and DFHIRP in the
SVA. If, when opening the interregion communication CICS detects that
the level of DFHIRP is at a lower level version, it issues message
DFHIR3799 and interregion communication fails to open.
In a coexistence environment, CICS/VSE 2.3 issues the following
message:
DFH1594 - A 0410 VERSION OF MODULE DFHIRP IS BEING LOADED
during initialization for an MRO environment.
The modules are loaded into the SVA from the load list SVA$CICS from
the CICS TS supplied library.
Chapter 4. CICS coexistence 137
Attention
In a coexistence environment, with both CICS TS and CICS/VSE installed,
care has to be taken when loading the SVA.
You cannot load optional CICS TS SVA-eligible modules into the SVA
where the names of the modules are the same in both CICS systems, as
they would be used by CICS/VSE 2.3, which would fail.
You should code the CICS TS system initialization parameter SVA=NO
(which is the default).
You can load optional CICS/VSE 2.3 modules into the SVA, but you must
ensure that they can only be accessed from CICS/VSE 2.3 and that CICS
TS cannot use them by coding SVA=NO or by using SVA=YES and
specifying on the system initialization parameter PRVMOD the module
names that cannot be shared. The module names that cannot be shared
are listed in the sample source member DFH$SVEX.J contained in
PRD1.BASE. To use this list, you must include the following POWER
source library (SLI) statement in your CICS startup JCL in the system
initialization parameters:
* $$ SLI MEM=DFH$SVEX.J,S=PRD1.BASE
To read the system initialization parameters from the startup job, the
EXEC DFHSIP,... statement must include, PARM='SI'.
Table 14 lists a summary of CICS modules loaded into the SVA.
Table 14. CICS phases in the SVA
Installed environment CICS TS + CICS/VSE CICS TS only
Load optional CICS/VSE Only allowed with ---
modules into SVA SVA=NO
or SVA=YES and use of
DFH$SVEX.
Load optional CICS TS Not allowed. CICS/VSE Yes.
modules into SVA has no SVA=NO . ..
Load Non-CICS modules Yes. Yes.
into SVA (LE etc)
Use of any SVA phase by Yes. ---
CICS/VSE
Use of SVA phases by Not possible . .. Possible - SVA=YES.
CICS TS - DFH* phases
Use of SVA phases by Possible. .. Possible - SVA=YES.
CIC TS - NON DFH*
phases
Note:
. .No optional CICS TS modules are allowed in the SVA, except those
with unique names compared to CICS/VSE 2.3.
. .SVA=YES and inclusion of DFH$SVEX in startup JCL is required in
CICS TS.
138 VSE/ESA V2R4
4.9 DL/I considerations
There are two versions of the DL/I optional program available with VSE/ESA 2.4:
DL/I DOS/VS 1.10 supported under CICS/VSE 2.3
DL/I VSE 1.11 supported under CICS TS
4.9.1 DL/I SVA considerations
For coexistence of DL/I 1.10 (under CICS/VSE 2.3) and DL/I 1.11 (used with the
transaction server), care must be taken with loading DL/I SVA-eligible phases
into the SVA.
If a coexistent environment exists, then do the following:
1. Load DL/I SVA-eligible phases into the SVA from the library which contains
the DL/I 1.10 phases.
DL/I 1.10 checks for phases in the SVA, and will unconditionally use the
phases loaded in the SVA if they are present. You must ensure that the SVA
does not contain SVA-eligible phases loaded from the DL/I VSE 1.11 libraries.
2. Ensure that the DLZACT CONFIG entry for DL/I VSE 1.11 is SVA=NO.
The new parameter of SVA=NO ensures that DL/I VSE 1.11 loads phases
from the library without reference to the SVA.
4.9.2 DL/I installation considerations
When installing both releases of DL/I, you must ensure that different VSE
sublibraries are used for each release.
If you are using the Interactive Interface for installation of optional products, then
by default:
DL/I 1.10 production part is installed into library PRD2.DLI1A0 and the
generation part is installed into library PRD2.DLI1A0G.
DL/I VSE 1.11 production part is installed into library PRD2.DBASE, while the
generation part is installed into PRD2.DLI1B0G.
4.9.3 LIBDEF considerations
You must also ensure that, when executing DL/I applications either under CICS
TS or CICS/VSE 2.3, the correct LIBDEF chains are present.
If you are executing DL/I with CICS/VSE 2.3, then ensure that the LIBDEF chain
places the PRD2.DLI1A0 sublibrary before PRD2.DBASE.
If you are executing DL/I with the CICS TS, then ensure that the PRD2.DBASE
sublibrary is before PRD2.DLI1A0.
If you have existing jobstreams that contain a LIBDEF chain for the PRD2.DBASE
sublibrary and you wish to continue to execute the jobs using DL/I 1.10, you must
amend the LIBDEF statement for the correct library chain.
Chapter 4. CICS coexistence 139
4.9.4 DL/I migration considerations
Current applications which are written in CICS command-level languages are
relatively easily migrated to the CICS TS and DL/I VSE 1.11.
CICS TS supports applications that are LE/VSE conforming languages.
DL/I VSE is upwards compatible from DL/I 1.10.
Applications that are written in CICS macro-level will not execute under the
CICS TS, and must remain and execute under CICS/VSE 2.3.
When considering the migration effort, you should determine:
1. Are there macro-level applications accessing DL/I databases?
If there are macro-level applications accessing DL/I databases, then you
must execute these programs under CICS/VSE 2.3, and the DL/I
databases must remain in DL/I 1.10. Your environment would be as
shown in item (1) in Figure 109 on page 141.
CICS does not support function-shipping of macro-level applications.
2. Are there CICS command-level applications accessing DL/I databases,
but compiled with non-LE/VSE conforming compilers such as RPG, C/370,
or DOS PL/I?
These applications must must still execute under CICS/VSE 2.3.
However, CICS does support function shipping of command-level
applications irrespective of LE/VSE conformity, and the DL/I databases
can be migrated to DL/I VSE 1.11. Your environment would be as shown
in item (2) in Figure 109 on page 141 for those command-level
applications.
A possible solution is illustrated in Figure 109 on page 141.
3. If there are no macro-level applications accessing DL/I databases, then
you should migrate your applications to the CICS TS and DL/I VSE 1.11.
Your applications would execute as shown in item (3) in Figure 109 on
page 141.
140 VSE/ESA V2R4
CICS/VSE 2.3 CICS TS
Applications: (2) Applications:
Function Shipping
Command-level only
Command-level Command-level
Macro-level
(3)
(1)
↓ ↓
DL/I 1.10 DL/I VSE 1.11
Databases Databases
Figure 109. DL/I 1.10 and DL/I VSE 1.11 coexistence
Notes:
a. Macro-level applications use DL/I 1.10 in the CICS/VSE 2.3 region.
b. Command-level applications use function-shipping with remote PSB
to execute under DL/I VSE 1.11.
c. Migrated applications execute under the CICS TS with local DL/I VSE
1.11 databases.
Examples of the DLZACT macros used for function-shipping of remote PSBs
are shown in Figure 110 on page 142.
Chapter 4. CICS coexistence 141
// JOB DLZNUCI1 GENERATE DL/I NUCLEUS FOR CICS 2.3 WITH HSMODE=ANY
// OPTION CATAL,NODECK,NOXREF
// LIBDEF *,SEARCH=(PRD2.DLI1A0,PRD2.DLI1A0G)
// LIBDEF *,CATALOG=PRIVLIB.DLI110
* ************************************************************
* * DLZACT ENTRIES FOR CICS/VSE 1.10 FOR FUNCTION SHIPPING
* * FOR EXECUTION UNDER DL/I VSE UNDER CICS TS
* *
* ************************************************************
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
PRINT GEN
DLZACT TYPE=INITIAL,SUFFIX=I1
DLZACT TYPE=CONFIG,MAXTASK=13,CMAXTSK=13,BFRPOOL=3,PI=YES, *
REMOTE=NO,HSMODE=ANY,PSBLOC=ANY
**********************************************************************
**** DL/I 1.10 PROGRAM ENTRIES ****
**********************************************************************
DLZACT TYPE=PROGRAM,PGMNAME=DFHTDLI, *
PSBNAME=(STBCUSR,STBCUSU,STBICL1)
DLZACT TYPE=PROGRAM,PGMNAME=DLZCBL30, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZCB230, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZCB231, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZCB232, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZPLI30, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZPL230, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZCBL60, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZCB260, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZCB261, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZCB262, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZPLI60, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZPL260, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZSAM60, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZHLA60, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZHLA61, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZHLA62, *
PSBNAME=(STBCUSR,STBCUSU)
DLZACT TYPE=PROGRAM,PGMNAME=DLZRPG60, *
PSBNAME=(STBCUSR,STBCUSU)
Figure 110 (Part 1 of 2). Example of the DLZACT macro for CICS/VSE 2.3
142 VSE/ESA V2R4
DLZACT TYPE=PROGRAM,PGMNAME=ONLCBLCA, *
PSBNAME=(STBICL1)
DLZACT TYPE=PROGRAM,PGMNAME=ONLCB2HL, *
PSBNAME=(STBICL1)
DLZACT TYPE=PROGRAM,PGMNAME=ONLCB2CA, *
PSBNAME=(STBICL1)
DLZACT TYPE=PROGRAM,PGMNAME=ONLCBLHL, *
PSBNAME=(STBICL1)
DLZACT TYPE=PROGRAM,PGMNAME=ONLPLICA, *
PSBNAME=(STBICL1)
DLZACT TYPE=PROGRAM,PGMNAME=ONLPLIHL, *
PSBNAME=(STBICL1)
DLZACT TYPE=PROGRAM,PGMNAME=ONLPL2CA, *
PSBNAME=(STBICL1)
DLZACT TYPE=PROGRAM,PGMNAME=ONLPL2HL, *
PSBNAME=(STBICL1)
**********************************************************************
**** DLZMDLI0 ****
**********************************************************************
DLZACT TYPE=PROGRAM,PGMNAME=DLZMDLI0,PSBNAME=STBCUSU,CONT=YES
DLZACT PSBNAME=STBICL1
**********************************************************************
**** DLZBPC00 ****
**********************************************************************
DLZACT TYPE=PROGRAM,PGMNAME=DLZBPC00, *
PSBNAME=(STBCUSR,STBCUSU,STBICL1,STBICLG)
**********************************************************************
**** REMOTE ENTRIES FOR CICS TS & DLI/VSE 1.11 ****
**********************************************************************
DLZACT TYPE=RPSB,PSB=STBCUSR,SYSID=CIC2
DLZACT TYPE=RPSB,PSB=STBCUSU,SYSID=CIC2
DLZACT TYPE=RPSB,PSB=STBICLG,SYSID=CIC2
DLZACT TYPE=RPSB,PSB=STBICL1,SYSID=CIC2
**********************************************************************
**** EXTENDED REMOTE ENTRIES ****
**********************************************************************
DLZACT TYPE=RPSB,PSB=MXHID,RNAME=MXASM,LNAME=HIDPSBA,SYSID=CIC2
DLZACT TYPE=RPSB,PSB=STBICLX,LNAME=STBICLG,RNAME=STBCUSU,
* SYSID=CIC2
**********************************************************************
**** BUFFERS ****
**********************************************************************
* DLZACT TYPE=BUFFER,HDBFR=(4)
DLZACT TYPE=FINAL
END
/*
ENTRY DLZNUC
INCLUDE DLZFTDP0
// EXEC LNKEDT
/*
/&
* $$ EOJ
Figure 110 (Part 2 of 2). Example of the DLZACT macro for CICS/VSE 2.3
Chapter 4. CICS coexistence 143
// JOB DLZNUCI2 GENERATE DL/I ONLINE NUCLEUS 'I2' WITH HSMODE=ANY
// OPTION CATAL,NODECK,NOXREF
// LIBDEF *,SEARCH=(PRD2.DBASE,PRD2.DLI1B0G)
// LIBDEF *,CATALOG=PRIVLIB.DLI111
* ************************************************************
* * DLZACT ENTRIES FOR CICS/VSE 1.11
* * FOR EXECUTION OF SHIPPED TRANSACTIONS FROM DL/I 1.10
* *
* ************************************************************
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
PRINT GEN
DLZACT TYPE=INITIAL,SUFFIX=I2
DLZACT TYPE=CONFIG,MAXTASK=13,CMAXTSK=13,BFRPOOL=3,PI=YES, *
REMOTE=NO,HSMODE=ANY,PSBLOC=ANY,SVA=NO
**********************************************************************
**** DFHMIRS ONLY ****
**********************************************************************
DLZACT TYPE=PROGRAM,PGMNAME=DFHMIRS, *
PSBNAME=(STBCUSR,STBCUSU,STBICLG,STBICL1)
DLZACT TYPE=PROGRAM,PGMNAME=DFHTDLI, *
PSBNAME=(STBCUSR,STBCUSU,STBICLG,STBICL1)
**********************************************************************
**** BUFFERS ****
**********************************************************************
DLZACT TYPE=BUFFER,HDBFR=(3)
DLZACT TYPE=FINAL
END
/*
ENTRY DLZNUC
INCLUDE DLZFTDP0
// EXEC LNKEDT
/*
/&
* $$ EOJ
Figure 111. Example of DLZACT macro under CICS TS
4.9.5 Batch applications
With the CICS TS and DL/I VSE 1.11, the DL/I Master Partition Controller can be
activated in more than one CICS/DLI partition at the same time. An MPS batch
job can select any active CICS/DLI online system and process any database
defined there. It can only connect to one CICS/DLI online system per job step.
The selection of the CICS/DLI online system is done via a new parameter of the
DLI/DLR statement submitted with a batch job.
Each MPS Master Partition Controller is activated and deactivated using the
CSDA/CSDD transaction as before.
You must consider the following when executing MPS job streams in a
multi-MPS environment:
1. With which CICS/DLI MPS region will the connection be made for execution
of your batch program?
144 VSE/ESA V2R4
2. If you are in a coexistence environment, you must ensure that DLZMPI00 and
DLZMPC00 are at the same release level.
4.10 DB2 Server for VSE
The DB2 Server for VSE 6.1 will support applications executing in CICS TS and
CICS/VSE 2.3 concurrently. If you have applications that cannot be migrated to
the CICS TS and currently execute under CICS/VSE 2.3, they can continue to
execute in this environment unchanged.
Refer to DB2 Server for VSE Administration and the CICS Transaction Server for
VSE/ESA Release Guide for programming language support for each product.
If you have a version or release of DB2 Server for VSE (or SQL/DS) that is not at
the level of 6.1, you should migrate to this level for support under the CICS TS.
The DB2 Server for VSE 6.1 is shipped as an optional product under VSE/ESA
2.3.2 and VSE/ESA 2.4.
If you currently execute SQL/DS applications from a single CICS/VSE 2.3 partition
or region, you will need to define additional resources to your CICS system, and
to your DB2 Server for VSE system. You can do this by:
Defining DB2 to both your CICS systems via CSD resource definitions as
described in DB2 Server for VSE Installation .
Coding the necessary changes to the DFHSIT macro for each CICS system to
support additional active tasks.
Granting SCHEDULE authority for each CICS system to use DB2 resources.
Possibly increasing the NCUSERS parameter to accommodate additional
links when starting your Resource Manager in multi-user mode.
Coding a CIRB transaction for each CICS system attaching to the Resource
Manager.
4.11 Sharing data in a coexistence environment
The sharing of data between partitions in a single VSE or multiple VSE images
remains the same in this release of VSE/ESA and the CICS TS, as in previous
releases.
As described throughout this chapter, the implementation of an MRO
function-shipping environment between regions will be necessary to access data
which is owned by another CICS region. This is necessary because of the
dependency on CICS/VSE 2.3 for macro-level applications, and non-LE/VSE
conforming languages.
For example, a macro-level application requires that the data is accessed within
the same region as the application. For these applications, the data is defined as
being a local resource.
For an application migrated to and executing in the CICS TS, requiring access to
these files in the CICS/VSE 2.3 partition, the request for data will be
function-shipped from the CICS TS region to the CICS/VSE 2.3 region.
Chapter 4. CICS coexistence 145
The same applies to CICS/VSE 2.3 command-level applications which require
data that is owned by a CICS TS region. The request is function-shipped from
CICS/VSE 2.3 to the CICS TS.
4.11.1 Shared data table considerations
If you wish to exploit the new functions of shared data tables in a coexistence
environment, any CICS TS region which requires read access to a data table
defined in another CICS TS file-owning region will use cross memory services.
Any CICS TS partition or region which requires update access to a shared data
table owned by another CICS TS partition or region will use function-shipping to
access the data.
Any CICS/VSE 2.3 partition which requires access to a shared data table from a
command-level program will be function-shipped to the CICS TS file-owning
region.
For more information on CICS TS shared data tables, refer to CICS Transaction
Server for VSE/ESA Shared Data Tables Guide .
4.12 Application programs in a coexistence environment
Application programs that have been translated, compiled, and link-edited using
CICS TS modules may not execute correctly under CICS/VSE 2.3 if you have
exploited new functions that are not supported under CICS/VSE 2.3.
However, command-level application programs that have been translated,
compiled and link-edited under CICS/VSE 2.3 are upwards-compatible providing
they comply with the programming language restrictions as specified in CICS
Transaction Server for VSE/ESA Release Guide .
Macro-level applications will not execute under the CICS TS.
You should have a strategy in place to ensure that applications that have been
migrated to the CICS TS are removed from your CSD file, or from the DFHPCT
and DFHPPT, to avoid invoking the transaction from CICS/VSE 2.3
Refer to Chapter 7, “CICS application program considerations” on page 183 for
further application program considerations.
146 VSE/ESA V2R4
Chapter 5. CICS customization
CICS provides interfaces to allow you to access CICS control blocks, enhance or
modify CICS, and customize the product for special needs and functions. These
interfaces include:
System generation
Initialization and termination processing
User exits
User-replaceable modules
System programmer interfaces
Source and object compatibility is not always guaranteed for most of these
interfaces when you migrate from one CICS release to another. You may have
to recompile and sometimes rework the logic you have implemented.
If you have programs that directly access control blocks, modify CICS code or
use any other undocumented interfaces, you must rewrite these to the supported
interfaces documented in CICS Transaction Server for VSE/ESA Customization
Guide . If you utilize the co-existence environment, you must keep customized
modules and programs for CICS TS and CICS/VSE V2R3 in separate VSE
sublibraries.
In this chapter we look at some of these interfaces. See CICS Transaction
Server for VSE/ESA Migration Guide and CICS Transaction Server for VSE/ESA
Customization Guide for detailed descriptions of new and changed options that
affect customizing CICS TS.
5.1 System generation
You cannot generate CICS management modules in CICS TS. The DFHSG
macros to perform tailoring and system generation of CICS management
modules are no longer provided. The generation sublibrary PRD2.GEN1 only
supports system generation for the VSE/ESA supervisor.
Most of the CICS management modules are pre-generated and distributed as
object code only (OCO). Since most of the CICS nucleus code loads above the
16 MB line, the size of full-function modules does not have the impact on the
amount of available storage below the 16 MB line that it did in prior releases.
You must use either PLT initialization processing or the new exit programming
interface (XPI) to implement any modifications you made to CICS management
modules in prior releases.
5.2 Initialization and termination processing
In this section we describe the changes to the initialization and shutdown
processing.
© Copyright IBM Corp. 1999 147
5.2.1 System initialization overlays
You cannot use system initialization overlays to perform additional processing
during CICS startup. The SIMODS system initialization parameter is no longer
supported.
5.2.2 Program list table (PLT) programs
Programs that are to run during CICS initialization or shutdown must be defined
in a program list table (PLT). The PLT must be named on the program list post
initialization (PLTPI) or the program list shutdown (PLTSD) system initialization
parameter, respectively. The following section describes the changes to PLT
processing.
5.2.2.1 Changes to PLTPI processing
Programs in the initialization program list table (PLTPI) are processed in
separate stages of CICS initialization, similar to the shutdown PLT (PLTSD). The
PLTPI is divided into two parts by the PLT entry:
DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM
Programs listed before the DFHDELIM entry are processed in the second stage
of CICS initialization. These programs can only be used to enable user exits;
they must be written in assembler language, and they must run in AMODE(31).
Programs listed after the DFHDELIM entry are processed in the third stage of
CICS initialization. This is where you include the PLT entries from PLT tables in
previous releases. The VSE-supplied PLT skeletons in ICCF library 59 have all
the PLT entries after the DFHDELIM entry.
5.2.2.2 Changes to PLTSD processing
Shutdown PLT processing is basically the same as in previous releases.
Program entries listed before the DFHDELIM entry in the PLT are processed
during the first quiesce stage of shutdown. Programs entries listed after the
DFHDELIM entry are processed in the second quiesce stage of shutdown.
5.2.2.3 PLT program execution key
You need to be aware of the execution key (EXECKEY) defined for programs
used during PLT processing.
PLTPI programs invoked during initialization and PLTSD programs invoked
by CEMT PERFORM SHUTDOWN run under tasks with TASKDATAKEY(CICS).
Programs must execute in EXECKEY(CICS) if they are invoked by a
transaction defined with TASKDATAKEY(CICS).
CICS passes control to each PLT program in EXECKEY(CICS) even if the
program's RDO definition specifies EXECKEY(USER).
If your PLTPI or PLTSD program links to other programs, those programs
must be defined with EXECKEY(CICS); otherwise, they will abend with an
AEZD abend.
We recommend that you define PLTPI and PLTSD programs with EXECKEY(CICS)
to avoid this problem. This includes any programs your PLT programs link to.
The default is EXECKEY(USER) for RDO and PPT program definitions migrated
from previous releases to CICS TS.
148 VSE/ESA V2R4
Table 15 on page 149 shows the recommended usage for combinations of
TASKDATAKEY on the transaction definition and EXECKEY on the program
definition.
Table 15. TASKDATAKEY and EXECKEY combinations
TASKDATAKEY EXECKEY Recommended usage
USER USER For normal applications using the CICS
API.
CICS USER Not permitted. CICS abends any
program defined with EXECKEY(USER)
invoked under a transaction defined with
TASKDATAKEY(CICS).
USER CICS For programs that need to issue
restricted VSE requests or modify
CICS-key storage.
CICS CICS For transactions (and component
programs) that function as extensions to
CICS, such as the CICS-supplied
transactions, or which require the same
protection.
5.3 User exits
CICS TS continues to provide the same two types of user exit interfaces as in
previous releases.
Global user exit An exit interface invoked at specific processing
points in CICS modules and domains
Task-related user exit An exit interface used primarily for CICS applications
to access external resource managers such as DB2
Server for VSE.
5.4 Global user exits (GLUEs)
The restructuring of CICS has resulted in significant changes to the global user
exit interface.
Standard linkage conventions and interfaces are used for all global user
exits.
A new exit programming interface (XPI) provides a set of calls to selected
CICS domains which service the request.
More exits can use command-level functions.
There are 35 new exit points available.
The following exits have been removed:
− File Control: XFCIN, XFCINC, XFCOUT
− Task Control: XKCDISP, XKCBWT, XKCAWT
− Storage Control: XSCREQ
− Terminal Control: XTCRDAT
The remaining 48 exit points available in previous releases are still
supported. Global user exits implemented on previous versions of CICS are
Chapter 5. CICS customization 149
not source- and object-compatible on CICS TS. If you implemented any of
these, the exit programs need to be reviewed, changed to work on CICS TS,
and recompiled using the CICS TS libraries.
If you have any global user exit interfaces to migrate to CICS TS, you must alter
these to conform to the new exit standards, to be re-entrant, and to run in a
31-bit environment.
Specify EXECKEY(CICS) in your RDO program definitions for your global user exit
programs and any programs to which they pass control. This needs to be done
for the same reasons described in 5.2.2.3, “PLT program execution key” on
page 148. GLUE programs are invoked in CICS key.
See CICS Transaction Server for VSE/ESA Customization Guide for detailed
guidelines on implementing the global user exits and the new XPI.
5.4.1 Task-related user exits (TRUEs)
Task-related user exits are essentially unchanged. The only parameters that
may cause a problem are UEPCSA and UEPTCA, since the CSA and TCA control
blocks are not addressable.
The release of DB2 for VSE shipped with VSE/ESA V2R4 has been updated and
provides the required task-related user exit support. Earlier versions of DB2 for
VSE and SQL/DS will not work with CICS TS.
5.5 User-replaceable modules (URMs)
A user-replaceable module is a CICS-supplied program that is always invoked at
a specific point in CICS processing. You can modify the supplied program with
your own logic or completely replace it with your own version.
The changes in CICS TS have changed the guidelines for writing
user-replaceable programs as follows:
They must be written using command-level interfaces.
They must not access internal CICS control blocks. CICS passes information
required by URMs in a communication area (COMMAREA), rather than in
control block fields as in previous releases.
They can be written in any language supported by CICS. (However, the
journaling URMs, DFHXJCC and DFHXJCO, must be written in assembler
language.)
They must be link-edited as AMODE(31) and support 31-bit addressing. This
includes any programs that the URMs call.
You must review all of your URMs to ensure they conform to the new guidelines.
Some URMs from earlier CICS versions may be source-compatible; however,
they must be re-assembled using the CICS TS libraries.
The following URMs are no longer available with CICS TS:
Security-related: DFHACEE, DFHXSE, DFHXSP are replaced with ESM.
Transaction restart: DFHRTY is replaced with DFHREST.
150 VSE/ESA V2R4
Two new URMs are available:
DFHPGADX: Autoinstall program for programs.
DFHZATDY: Autoinstall program for APPC connections
5.5.1 VSE/ESA-supplied URMs
VSE supplies several URMs that have been updated to conform to the guidelines
for URMs in CICS TS. If you have modified any of these, you must review your
changes and integrate them into the new VSE versions of these programs.
Table 16 lists the VSE ICCF members and the CICS URM functions they perform.
You can find the source code for these in ICCF library 59.
Table 16. VSE-supplied CICS URMs
ICCF Member Function
IESZNEP CICS Node Error Program (DFHZNEP) replacement. Updated to
command level. . .
IESZNEPS Additions to an existing Node Error Program. Updated to
IESZNEPX command level. . . . .
DFHPEP CICS Program Error Program (DFHPEP) replacement. Updated
to command level and AMODE(31).
IESZATDX CICS autoinstall program (DFHZATDX) replacement. Updated
to use URM information passed in the COMMAREA.
. . The DFHSNEP macro generates the AMODE(31) setting for each DSECT in
the node error program. The VSE node error program logic issues an EXEC
CICS START TRANSID('IENP') which invokes the IESCLEAN program to clean up
IUI control information after terminal errors. Prior releases of VSE used a
program control link to IESCLEAN.
. .The CICS EXEC commands are pre-translated in these VSE members.
5.6 System programmer interfaces
In addition to the interfaces described so far, system programmers have used
other interfaces to access CICS information and to perform system-related
functions.
While this is not an all-inclusive list of interfaces that system programmers have
used, following are some of the more common ones.
5.6.1 System programming macros
With the removal of macro-level support and changes in CICS TS, many of the
system programmer macro interfaces have changed or have been removed.
These macros include:
DFHTC CTYPE
This macro provided access to the terminal control table control blocks.
These functions can be replaced with the EXEC CICS INQUIRE and SET
TERMINAL commands.
DFHOC
Chapter 5. CICS customization 151
This macro was used to open and close files, extrapartition transient data
queues and dump datasets. It can be replaced with the EXEC CICS SET FILE
commands.
DFHWTO
This macro performed write-to-console operator functions. Some
applications also used the COBOL and PL/I DISPLAY verbs to write to the
console. These were unsupported in a CICS environment. These methods
can be replaced with the EXEC CICS WRITE OPERATOR command.
DFHSEC
This macro was used to invoke CICS security functions. Another technique
commonly used to front-end CICS sign-on security was to link to the CICS
sign-on program (DFHSNP) and pass a TIOA formatted with the CSSN
transaction and the user sign-on information. These will not work with CICS
TS. The EXEC CICS SIGNON and EXEC CICS SIGNOFF commands can be used to
replace these functions.
If you use any other system macro interfaces, review the system programming
interface (SPI) described in CICS Transaction Server for VSE/ESA System
Programming Reference for commands that can replace these functions.
5.6.2 Programmable interface to CEMT
You can still use this interface in CICS TS to invoke CEMT functions from an
application program; however, we recommend you use the EXEC CICS
INQUIRE|SET SPI commands.
There are several new CEMT commands. Many of the existing commands are
changed with new fields or fields that have been removed. Some commands are
obsolete.
For example, the command CEMT INQUIRE QUEUE on CICS/VSE V2R3 is now CEMT
INQUIRE TDQUEUE on CICS TS. You may also get different results if you use
abbreviations for some of the commands.
You can see some of the differences between the two CICS versions in the CEMT
displays shown in Figure 112 on page 153 and Figure 113 on page 153. If you
use this interface, you may have to change your program because of these
differences. CICS Transaction Server for VSE/ESA Migration Guide lists the
changes to the CEMT commands.
152 VSE/ESA V2R4
inq
STATUS: ENTER ONE OF THE FOLLOWING OR HIT ENTER FOR DEFAULT
AUToinstall TClass
AUXtrace TErminal
CONNection TRACe
CONTrol TRANsaction
DUMP Vtam
DUMPOptions
File
DAtaset
Irc
Journal
Line
Modename
Netname
Program
Queue
System
TAsk
APPLID=OLDCICS
PF 1 HELP 3 END 9 MSG
Figure 112. CICS/VSE V2R3 CEMT INQUIRE display
INQ
STATUS: ENTER ONE OF THE FOLLOWING OR HIT ENTER FOR DEFAULT
AUTInstmodel Journalnum Vtam
AUTOinstall MODename
AUXtrace MONitor
Connection Netname
DEletshipped PArtner
DSAs PROFile
DSName PROGram
DUmpds STatistics
Exci SYDumpcode
FEConnection SYStem
FENode TAsk
FEPOol TClass
FEPRopset TDqueue
FETarget TErminal
FIle TRAnsaction
INttrace TRDumpcode
IRc TSqueue
SYSID=CIC1 APPLID=DBDCCICS
PF 1 HELP 3 END 9 MSG
Figure 113. CICS TS CEMT INQUIRE display
Chapter 5. CICS customization 153
CEMT displays invoked from the VSE console have also changed from CICS/VSE
V2R3 and CICS TS. The following shows the console response from some typical
CEMT commands issued from the console to a CICS/VSE V2R3 partition:
F4-0004
4 cemt in ta
F4 0004
F4 0004 Tas(00016) Tra(CXPB) Act Tas
F4 0004 Tas(00098) Tra(CEMT) Fac(CNSL) Act Ter
F4 0004 Tas(00097) Tra(CEMT) Fac(A001) Sus Ter
F4 0004 RESPONSE: NORMAL TIME: 09.42.38 DATE: 04.14.99
F4 0004 APPLID=OLDCICS
4 cemt in file
F4 0004
F4 0004 Fil(DFHCSD ) Vsa Clo Une Rea Bro
F4 0004 RESPONSE: NORMAL TIME: 09.43.07 DATE: 04.14.99
F4 0004 APPLID=OLDCICS
F4-0004
This is part of the response for the same CEMT commands issued from the VSE
console to a CICS TS partition:
93 cemt in ta
F2-0093
F2 0096 Tas(0011139) Tra(IECM) Sus Tas Pri( 020 )
Hty(EKCWAIT ) Hva(SINGLE ) Hti(000000) Sta(SD)
Use(RES5 ) Rec(X'B2188F1581C64B07')
Tas(0011140) Tra(CEMT) Fac(CO01) Run Ter Pri( 255 )
Sta(TO)
Use(CICSUSER) Rec(X'B2188F15B0EFBB05')
RESPONSE: NORMAL TIME: 16.39.52 DATE: 04.14.99
F2 0096 Tas(0011139) Tra(IECM) Sus Tas Pri( 020 )
Hty(EKCWAIT ) Hva(SINGLE ) Hti(000000) Sta(SD)
Use(RES5 ) Rec(X'B2188F1581C64B07')
Tas(0011140) Tra(CEMT) Fac(CO01) Run Ter Pri( 255 )
Sta(TO)
Use(CICSUSER) Rec(X'B2188F15B0EFBB05')
RESPONSE: NORMAL TIME: 16.39.52 DATE: 04.14.99
SYSID=CIC1 APPLID=DBDCCICS
93 cemt in file
F2-0093
F2 0096
Fil(DFHCSD ) Vsa Clo Une Rea Upd Add Bro Del
Dsn( CICS.CSD )
Max( 00000000 )
Fil(IESCNTL ) Vsa Ope Ena Rea Upd Add Bro Del
Dsn( VSE.CONTROL.FILE )
Fil(IESPRB ) Vsa Ope Ena Rea Upd Add
Dsn( VSE.ONLINE.PROB.DET.FILE )
Fil(IESROUT ) Vsa Ope Ena Rea Upd Add Bro Del
Dsn( VSE.MESSAGE.ROUTING.FILE )
You should include some operator training time in your migration in order to
orient your computer operators to the new information displayed on the console
by the CEMT commands.
154 VSE/ESA V2R4
5.6.3 The System Programming Interface (SPI)
The SPI commands provide a formal programming interface for writing programs
to manage CICS system resources. With these commands you can perform
many of the functions that were done using direct access to control blocks.
CICS TS provides upward source compatibility and object compatibility for
applications that use the SPI commands and which execute correctly on
CICS/VSE V2R3.
There are several new SPI commands. Many of the existing commands have
new options added and have some response values changed. Review CICS
Transaction Server for VSE/ESA Migration Guide for a list of changes to the SPI
interface that may affect applications containing these commands.
If you compile any programs using the SPI commands, you must specify the new
translator option SP, otherwise the translator will not process the command.
If you use the CECI transaction to test SPI commands, note that the
abbreviations for several of the commands that you could enter on the screen
have changed in CICS TS. For example, CECI INQUIRE TRAN(CEMT) that works on
CICS/VSE V2R3 produces an error and defaults to CECI INQUIRE TRANC(CEMT) on
CICS TS. This is not a problem for the SPI commands in an application program,
since abbreviated commands are not allowed by the translator.
You can see some of the differences between the two CICS versions in the CECI
INQ displays shown in Figure 114 and Figure 115.
inq
STATUS: ENTER ONE OF THE FOLLOWING
Autoinstall Vtam
Connection
Dumpds
File
Irc
Journalnum
Modename
Netname
Program
Reqid
System
TAsk
TClass
TDqueue
TErminal
TRACedest
TRANsaction
PF 1 HELP 2 HEX 3 END 4 EIB 5 VAR 6 USER 9 MSG
Figure 114. CICS/VSE V2R3 CECI INQUIRE display
Chapter 5. CICS customization 155
INQ
STATUS: ENTER ONE OF THE FOLLOWING
AUTInstmodel STAtistics
AUTOinstall STOrage
Connection SYSDumpcode
DEletshipped SYSTem
DSname TAsk
DUmpds TClass
Exitprogram TDqueue
File TErminal
Irc TRACEDest
Journalnum TRACEFlag
MODename TRACEType
MONitor TRANClass
Netname TRANDumpcode
PArtner TRANSaction
PROFile TSqueue
PROGram Vtam
Reqid
PF 1 HELP 2 HEX 3 END 4 EIB 5 VAR 6 USER 9 MSG
Figure 115. CICS TS CECI INQUIRE display
156 VSE/ESA V2R4
Chapter 6. Performance and tuning
In this chapter we look at some of the performance and tuning aspects of
VSE/ESA V2R4 and the CICS Transaction Server for VSE/ESA. This material is
intended to give you an introduction to the performance considerations and
related facilities of the new release. For more detailed information on
performance and tuning, you should review:
CICS Transaction Server for VSE/ESA Performance Considerations
This document is available from the VSE Website:
http://www.s390.ibm.com/vse
In addition to CICS performance considerations, it also describes VSE/ESA
V2R4 performance enhancements. Check the Website regularly, since the
document is continuously being updated with performance information.
CICS Transaction Server for VSE/ESA Performance Guide
This publication guides you in monitoring and tuning CICS performance. It
discusses the impact of many of the new parameters supplied with CICS TS.
In planning your migration, you need to answer several questions related to
performance:
How will the new releases affect your virtual storage requirements?
Are your current system resources adequate?
What performance and tuning data do you need?
This chapter discusses each of these areas and helps you answer these
questions.
6.1 Virtual storage considerations
Several changes to VSE and CICS will increase your overall system's virtual
storage requirements.
More CICS storage areas are moved above the line into 31-bit GETVIS.
CICS virtual storage requirements have increased with the restructured
CICS.
New and changed VSE and CICS functions make more use of VSE data
spaces.
You will need to change your VSE startup definitions and your CICS partition
sizes to allow for these changes.
6.1.1 VSE startup parameters
The VSE IPL and JCL startup parameters that you should change are:
ALLOC
Increase the CICS partition allocation sizes. CICS partition sizes for the
environment B system are 50 MB compared to 30 MB on VSE/ESA V2R3.
PASIZE
© Copyright IBM Corp. 1999 157
Increase the maximum private area size to allow for the larger CICS
partitions. The PASIZE for environment B is 50 MB.
SYSDEF
Increase the system limits for the total amount of data space that can be
allocated.
− The supplied SYSDEF statement in the ALLOC procedure specifies a
maximum DSIZE of 20 MB.
− The VSE BSM uses a 960 K data space.
− The CICS Data Management Facility and Shared Data Tables require
data spaces, the sizes of which are user-specified.
VSIZE
Increase the VSE system total virtual size to accommodate the increase in
CICS partition sizes and additional data space requirements.
6.1.2 Shared Virtual Area (SVA)
There is little change in the installed system's SVA storage requirements
between VSE/ESA V2R3 and VSE/ESA V2R4.
The 31-bit program area and the number of SDL entries in the IPL SVA statement
for Environment B are larger. The 31-bit PSIZE value has been increased from 3
MB to 6 MB. The SDL value has changed from 300 entries to 700 entries. The
IUI storage displays in Figure 116 and Figure 117 give you a comparison of the
SVA storage layouts in both releases.
You can load most of the SVA-eligible CICS modules and programs in the
extended SVA in 31-bit storage. This can provide you storage relief for the 24-bit
SVA if you currently load CICS modules in the SVA.
The number and size of CICS SVA-eligible modules has increased. You may
need to increase the 31-bit SVA size to fully utilize the SVA for CICS modules.
158 VSE/ESA V2R4
IESADMDSV1 SHARED VIRTUAL AREA LAYOUT
------------------------------------------------------------------------------
'02CFFFFF'X SYSTEM GETVIS(31) USED: (HWM: 1696K ) | 1132K | |
'025C8000'X FREE: | 6256K | 7388K |
----------------------------------------------------------------------| 11M
PROGRAM AREA(31) USED: | 2908K | |
'02200000'X AVAILABLE: | 964K | 3872K |
==============================================================================
'003FFFFF'X V-POOL | 64K | |
'003D5000'X SYSTEM LABEL AREA (SLA) | 108K | 172K |
----------------------------------------------------------------------|
SYSTEM GETVIS(24) USED: (HWM: 564K ) | 552K | |
'0022A000'X FREE: | 1156K | 1708K |
----------------------------------------------------------------------| 3520K
PROGRAM AREA(24) USED: | 1400K | |
'00098000'X AVAILABLE: | 208K | |
-------------------------------------------------------------| 1640K |
SYSTEM DIRECTORY LIST (SDL) | 32K | |
'00090000'X | | |
------------------------------------------------------------------------------
PF1=HELP 2=REFRESH 3=END 4=RETURN 6=PARTITION
Figure 116. VSE/ESA V2R3 SVA storage layout
IESADMDSV1 SHARED VIRTUAL AREA LAYOUT
------------------------------------------------------------------------------
'043FFFFF'X SYSTEM GETVIS(31) USED: (HWM: 2248K ) | 1324K | |
'03CEE000'X FREE: | 5916K | 7240K |
----------------------------------------------------------------------| 14M
PROGRAM AREA(31) USED: | 3002K | |
'03600000'X AVAILABLE: | 4094K | 7096K |
==============================================================================
'003EFFFF'X V-POOL | 64K | |
'003C5000'X SYSTEM LABEL AREA (SLA) | 108K | 172K |
----------------------------------------------------------------------|
SYSTEM GETVIS(24) USED: (HWM: 916K ) | 848K | |
'00248000'X FREE: | 676K | 1524K |
----------------------------------------------------------------------| 3376K
PROGRAM AREA(24) USED: | 1365K | |
'000B4000'X AVAILABLE: | 251K | |
-------------------------------------------------------------| 1680K |
SYSTEM DIRECTORY LIST (SDL) | 64K | |
'000A4000'X | | |
------------------------------------------------------------------------------
PF1=HELP 2=REFRESH 3=END 4=RETURN 6=PARTITION
Figure 117. VSE/ESA V2R4 SVA storage layout
Chapter 6. Performance and tuning 159
6.1.3 CICS partition layout
Figure 118 shows the IUI storage display for the CICS ICCF partition from our
installed VSE/ESA V2R3 system. Figure 119 shows the same IUI storage display
for our installed VSE/ESA V2R4 system. With these two displays you can see the
differences in GETVIS and program area usage between CICS/VSE V2R3 and
CICS TS.
See 6.1.3.1, “CICS/VSE V2R3 partition content” on page 161 and 6.1.3.2, “CICS
TS partition content” on page 163 for a description of the actual content of these
storage areas.
IESADMDSPL STATIC PARTITION LAYOUT
PARTITION: F2 JOB NAME: CICSICCF
PHASE: DFHSIP
------------------------------------------------------------------------------
'021FFFFF'X | GETVIS ANY |
| USED: 5896K | . .
| FREE: 19M |
- -(16M)- - - - - - - - - - - - - - - - -| HIGH WATER MARK: 5908K |
A GETVIS BELOW | LARGEST FREE BLOCK: 19M |
. . | USED: 3236K | |
| FREE: 3932K | | 25M
| HIGH WATER MARK: 3248K | |
'00900000'X | LARGEST FREE BLOCK: 3928K V |
------------------------------------------------------------------------------
PROGRAM AREA (EXEC SIZE) LOADED PHASE: 5108K |
'00400000'X . . AVAILABLE: 12K | 5120K
------------------------------------------------------------------------------
. . PARTITION: 30M
PF1=HELP 2=REFRESH 3=END 4=RETURN 6=SVA
Figure 118. VSE/ESA V2R3 CICSICCF partition layout
160 VSE/ESA V2R4
IESADMDSPL STATIC PARTITION LAYOUT
PARTITION: F2 JOB NAME: CICSICCF
PHASE: DFHSIP
------------------------------------------------------------------------------
'035FFFFF'X | GETVIS ANY |
| USED: 36M | . .
| FREE: 14M |
- -(16M)- - - - - - - - - - - - - - - - -| HIGH WATER MARK: 40M |
A GETVIS BELOW | LARGEST FREE BLOCK: 14M |
. . | USED: 8744K | |
| FREE: 3540K | | 50M
| HIGH WATER MARK: 12M | |
'00401000'X | LARGEST FREE BLOCK: 3532K V |
------------------------------------------------------------------------------
PROGRAM AREA (EXEC SIZE) LOADED PHASE: 582B |
'00400000'X . . AVAILABLE: 3514B | 4096B
------------------------------------------------------------------------------
. . PARTITION: 50M
PF1=HELP 2=REFRESH 3=END 4=RETURN 6=SVA
Figure 119. VSE/ESA V2R4 CICSICCF partition layout
. . More storage is used in 31-bit GETVIS for CICS storage areas above the
line compared to CICS/VSE V2R3.
. . All of the CICS storage areas below the line are now in 24-bit GETVIS
except for the DFHSIP phase. In CICS/VSE V2R3 these storage areas are in
the program area below the size line.
. . The program area size only needs to be large enough to load the DFHSIP
phase. Change your size parameter on the EXEC statement in your CICS
jobstreams to SIZE=DFHSIP. In CICS/VSE V2R3 you specified a value for
the SIZE parameter.
. . The CICS partition sizes have increased.
6.1.3.1 CICS/VSE V2R3 partition content
The storage layout of a CICS partition has changed significantly in CICS TS
compared to CICS/VSE V2R3. Figure 120 describes what is contained in the
storage layout for the CICSICCF partition on VSE/ESA V2R3. Figure 121 shows
the comparable storage layout for the CICSICCF partition on VSE/ESA V2R4.
Chapter 6. Performance and tuning 161
'021FFFFF'X ------------------------------------------------------------------
A |
| CICS 31-bit GETVIS Storage Areas . . | n.nM
| (31-bit Applications + Working Storage) |
GETVIS 31-Bit (TS MAIN, DTB Buffers, COMMAREAs) |
| (Trace Table, Data Tables) |
| (Table Manager CBs) |
| |
| VSAM Buffers . . | .2M
| USED: 2660K |
V FREE: 15M |
- -(16M)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
A ICCF and Interactive Partitions . . | 3.1M
| |
| VSAM Control Blocks . . | 50K
GETVIS 24-Bit |
| |
| USED: 3236K |
V FREE: 3932K |
'00900000'X ------------------------------------------------------------------
A PROGRAM AREA LOADED PHASE: 5108K |
| (EXEC DFHSIP,SIZE=5M) |
| |
V CICS Nucleus, 24-bit CBs and DSA . . | 5120K
'00400000'X ------------------------------------------------------------------
PARTITION: 30M
Figure 120. VSE/ESA V2R3 CICSICCF storage layout
The CICS/VSE V2R3 partition storage is made up of several key areas.
. . CICS uses 31-bit GETVIS storage for:
CICS and user application programs compiled with RMODE(ANY).
Working storage for COBOL programs compiled with DATA(31)
Selected CICS storage areas including:
− Main temporary storage
− All application program COMMAREAs
− Some table manager control blocks
− Dynamic Transaction Backout buffers
− Trace table and data tables
CICS acquires and releases 31-bit GETVIS. However, CICS does not
manage the 31-bit GETVIS area as it does the Dynamic Storage Area in the
program area below the 16 MB line.
Programs loaded in 31-bit GETVIS are considered resident. The CICS
program compression function is not used to free up storage occupied by
unused 31-bit programs.
. . VSAM buffers for non-shared resource (NSR) files and local shared
resource (LSR) pools are above the line. These include buffers for user
files as well as CICS system files such as temporary storage and transient
data. The amount required depends on your VSAM buffer specifications.
Typical requirements are 2 MB to 4 MB. The files in our installed system
used about 170 K.
162 VSE/ESA V2R4
VSAM control blocks are in 24-bit GETVIS. The files in our installed system
used about 50 K.
. . ICCF control blocks, ICCF program code and interactive partitions are in
24-bit GETVIS. The storage required using the default ICCF generation
options is about 3.1 MB.
. . All of the CICS nucleus, most of the CICS control blocks and the CICS
Dynamic Storage Area are loaded in the program area specified by the
SIZE parameter on the EXEC statement.
6.1.3.2 CICS TS partition content
The organization of the CICS partition in CICS TS is quite different than in
CICS/VSE V2R3; see Figure 121.
'035FFFFF'X ------------------------------------------------------------------
A |
| CICS Extended Dynamic Storage Areas (EDSALIM) . . | 25.0M
| (EUDSA, ERDSA, ESDSA, ECDSA) |
| |
GETVIS 31-Bit Other CICS areas . . | 2.3M
| (DFHSIP31, Kernel storage, Trace table) |
| (Non-nucleus CICS modules and Control Blocks) |
| |
| VSAM Buffers . . | .2M
| USED: 27.5M |
V FREE: 10.5M |
- -(16M)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
A ICCF and Interactive Partitions . . | 3.1M
| |
| VSAM Control Blocks . . | .1M
GETVIS 24-Bit |
| CICS Dynamic Storage Areas (DSALIM) . . | 5.0M
| (UDSA, RDSA, SDSA, CDSA) |
| |
| Other CICS areas . . | .5M
| (Non-nucleus CICS modules and Control Blocks) |
| (24-bit Kernel Storage) |
| USED: 8744K |
V FREE: 3540K |
'00401000'X ------------------------------------------------------------ ------
A PROGRAM AREA LOADED PHASE: 582B |
| |
V (EXEC DFHSIP,SIZE=DFHSIP) . . | 4K
'00400000'X ------------------------------------------------------------------
PARTITION: 50M
Figure 121. VSE/ESA V2R4 CICSICCF storage layout
CICS allocates DSAs both below and above the 16 MB line.
There are eight dynamic storage areas (DSAs) in CICS Transaction Server
for VSE/ESA.
. . Four DSAs are in extended storage above the 16 MB line.
The EDSALIM parameter in your CICS system intialization parameters the
maximum amount of 31-bit GETVIS that can be allocated for extended DSAs.
Chapter 6. Performance and tuning 163
Important
Extended DSA storage is required. You must specify at least 10 MB, or
CICS will not initialize.
Environment B sets the EDSALIM parameter to 25 MB.
. . Four DSAs are in 24-bit GETVIS below the line.
The DSALIM parameter in your CICS system initialization parameters
specifies the maximum amount of 24-bit GETVIS that can be allocated for
DSAs below the 16 MB line.
Important
DSA storage is required. The minimum specification is 2 MB.
Environment B sets the DSALIM parameter to 5 MB.
. . . . In addition to the DSA and EDSA storage, CICS also uses 24-bit and
31-bit GETVIS storage for other CICS components.
. . . . VSAM buffer and control block storage allocation requirements are the
same as CICS/VSE V2R3. There is slight increase for the CICS system files.
. . ICCF and interactive partition storage allocations are the same as CICS/VSE
V2R3.
. . The program area size only needs to be large enough to load the DFHSIP
phase. Change your size parameter on the EXEC statement in your CICS
jobstreams to SIZE=DFHSIP. VSE rounds the SIZE allocation to a 4 K multiple.
You must increase your CICS partition allocations to provide sufficient 31-bit
GETVIS storage for CICS TS. To summarize, your minimum CICS partition
storage above the line must include the sum of . ., . . and . . in Figure 121 on
page 163.
6.1.3.3 CICS dynamic storage areas
Table 17 lists the eight CICS dynamic storage areas and the type of storage they
contain. The extended DSAs in 31-bit GETVIS are prefixed with an uppercase
letter E.
Table 17. CICS DSA Descriptions
DSA Name DSA Type Content
UDSA EUDSA User DSAs User-key task-lifetime storage
SDSA ESDSA Shared DSAs Non-reentrant user-key programs and SHARED
GETMAIN storage
RDSA ERDSA Read-only Key-0 storage for all re-entrant programs and
DSAs tables
CDSA ECDSA CICS DSAs Storage for all non-reentrant CICS-key programs,
CICS-key task storage and all CICS control
blocks.
You can specify a fixed size of each of these areas via system initialization
parameters or let CICS dynamically acquire storage for these as required.
164 VSE/ESA V2R4
You can only change the maximum limits while CICS is running by using either
of the following CEMT commands:
CEMT INQ or SET DSA
CEMT INQ or SET SYSTEM
You can see the results of the CEMT INQ DSA command in Figure 122. An
example of the CEMT INQ SYSTEM command is in Figure 123.
If you increase the DSALIM parameter, you must have enough free 24-bit GETVIS
in the CICS partition to satisfy the additional storage allocated for the DSA. If
you increase the EDSALIM parameter, you must have enough free 31-bit GETVIS
in the CICS partition to satisfy the additional storage allocated for the EDSA.
We recommend you let CICS dynamically allocate the individual DSAs even
though you can fix their sizes with system initialization parameters.
IN DSA
STATUS: RESULTS - OVERTYPE TO MODIFY
SOSStatus( NOTSOS )
Dsalimit( 05242880 )
Cdsasize( 00524288 )
Rdsasize( 00786432 )
SDsasize( 00524288 )
Udsasize( 00262144 )
EDsalimit( 0026214400 )
ECdsasize( 0002097152 )
ERdsasize( 0006291456 )
ESdsasize( 0001048576 )
EUdsasize( 0001048576 )
SYSID=CIC1 APPLID=DBDCCICS
RESPONSE: NORMAL TIME: 08.51.25 DATE: 03.26.99
PF 1 HELP 3 END 7 SBH 8 SFH 9 MSG 10 SB 11 SF
Figure 122. CEMT INQUIRE DSA display
Some characteristics of the DSAs you should be aware of are:
Extended DSAs and the EDSALIM are allocated in multiples of 1 MB.
DSAs below the line and the DSALIM are allocated in multiples of 256 K.
CICS manages storage within each DSA using a 4 K page size. The SIT
PGSIZE parameter is no longer supported.
SVA-eligible programs that are not in the SVA are loaded in the RDSA for
24-bit programs and in the ERDSA for 31-bit programs. This provides
read-only access protection the same as loading programs in the SVA,
provided the system initialization parameter RENTPGM=PROTECT is
specified.
New RDO parameters on the program and transaction definitions control
which DSA is used for program-related and task-related storage.
Chapter 6. Performance and tuning 165
On transaction definitions, the following parameters affect where storage is
allocated:
TASKDATAKEY(USER)
This specifies that all task-lifetime storage is obtained from user-key storage
in the user DSA below the line (UDSA) or the extended user DSA above the
line (EUDSA).
Task-lifetime storage includes the transaction work (TWA), the EXEC
interface block (EIB), copies of working storage, explicit GETMAINs and
implicit GETMAINS resulting from the SET option on other commands.
TASKDATAKEY(CICS)
This specifies that all task-lifetime storage is obtained from CICS-key storage
in the CICS DSA below the line (CDSA) or the extended CICS DSA above the
line (ECDSA).
TASKDATALOC(BELOW|ANY)
This parameter controls which DSA the task-lifetime storage is obtained
from, the DSA below the line (BELOW) or the extended DSA above the line
(ANY).
On program definitions, the following parameters affect where storage is
allocated:
EXECKEY(USER)
Non-reentrant programs defined with this option are loaded in the shared
DSAs. RMODE(24) programs are loaded in the SDSA below the line and
RMODE(31) programs are loaded in the ESDSA above the line.
EXECKEY(CICS)
Non-reentrant programs defined with this option are loaded in the CICS
DSAs. RMODE(24) programs are loaded in the CDSA below the line and
RMODE(31) programs are loaded in the ECDSA above the line.
Reentrant programs (programs compiled with the RENT option and
link-edited SVA-eligible) are loaded in the read only DSAs regardless of the
EXECKEY value. RMODE(24) programs are loaded in the RDSA below the
line and RMODE(31) programs are loaded in the ERDSA above the line. The
system initialization parameter RENTPGM=PROTECT must be specified for
the read-only DSAs to be allocated from key-0 read-only storage.
DATALOCATION(BELOW|ANY)
This parameter affects the addresses passed to the program in the address
field of commands with the SET option. Data is copied below the line if
necessary when DATALOCATION(BELOW) is specified.
The defaults for transaction definitions migrated to CICS TS are:
TASKDATAKEY(USER)
and
TASKDATALOC(BELOW)
The defaults for program definitions migrated to CICS TS are:
EXECKEY(USER)
166 VSE/ESA V2R4
and
DATALOCATION(BELOW)
These defaults provide compatibility for the way transaction and program-related
storage is allocated in CICS/VSE V2R3. Figure 123 shows an example of the
CEMT INQ SYSTEM command.
IN SYS
STATUS: RESULTS - OVERTYPE TO MODIFY
AGing( 05000 ) PROGAUTOCtlg( CTLGALL )
AKp( 00000 ) PROGAUTOExit( DFHPGADX )
CDsasize( 00524288 ) PROGAUTOInst( AUTOINACTIVE )
CIcstslevel( 010100 ) RDsasize( 00786432 )
CMDPROTEct( CMDPROT ) REENTPROTEct( REENTPROT )
DFltuser( CICSUSER ) RELease( 0410 )
DSalimit( 05242880 ) RUnaway( 0020000 )
DTrprogram( DFHDYP ) SCandelay( 0200 )
DUmping( SYSDUMP ) SDsasize( 00524288 )
ECdsasize( 0002097152 ) SOSStatus( NOTSOS )
EDsalimit( 0026214400 ) SToreprotect( INACTIVE )
ERdsasize( 0006291456 ) Time( 0001000 )
ESdsasize( 0001048576 ) Udsasize( 00262144 )
EUdsasize( 0001048576 )
MAxtasks( 020 )
MRobatch( 001 )
OPRel( 64 )
OPSys( E )
SYSID=CIC1 APPLID=DBDCCICS
RESPONSE: NORMAL TIME: 10.43.09 DATE: 03.26.99
PF 1 HELP 3 END 7 SBH 8 SFH 9 MSG 10 SB 11 SF
Figure 123. CEMT INQUIRE SYS display
6.1.4 Storage requirements for MXT
The role of MXT has changed significantly in CICS TS. In previous versions of
CICS, you used the MXT parameter to limit the total number of system and user
tasks that CICS allowed at any one time. In CICS TS, you use the MXT
parameter to limit the total number of user tasks only. CICS TS provides for up
to 15 system tasks.
The setting of MXT can significantly affect the amount of DSA and EDSA storage
required for your CICS partition. Storage to support the maximum number of
user tasks is pre-allocated from the DSAs.
The formulas for calculating the DSA storage requirements are:
DSA MXT storage = 20K + (MXT * 2K) + (MXT/10. . * 4K)
EDSA MXT storage = 120K + (MXT * 12K) + (MXT/10. . * 4K)
. . Rounded down
For example, the supplied DFHSIT skeletons in ICCF library 59 for CICSICCF and
a second CICS partition specify MXT=50. The storage required using this value
is as follows:
Chapter 6. Performance and tuning 167
DSA MXT storage = 20K + (50 * 2K) + (50/10 * 4K) = 140K
EDSA MXT storage = 120K + (50 * 12K) + (50/10 * 4K) = 740K
If you use MXT=999 as coded in the skeleton DFHSIT tables supplied with prior
VSE/ESA releases, the storage required is as follows:
DSA MXT storage = 20K + (999 * 2K) + (999/10 * 4K) = 2414K
EDSA MXT storage = 120K + (999 * 12K) + (999/10 * 4K) = 12504K
Note: This storage requirement is significantly larger, so avoid setting MXT to a
high value.
The supplied skeleton DFHSITCO for the CICS/VSE V2R3 coexistence
environment also specifies MXT=999.
You can use your CICS shutdown statistics from your earlier CICS releases to
help you set MXT. As an initial starting point, set MXT to the value in the “Peak
Number of Tasks” statistic. If the “Number of Times at Max Task” statistic is
high, you may need to increase MXT slightly.
The MXT value can be changed dynamically using the CEMT INQUIRE SYSTEM
command shown in Figure 123 on page 167. If you increase the MXT value, you
must have sufficient storage available in the DSAs below and above the 16 MB
line. CICS will issue error message Short on Storage or Short on Extended
Storage if it cannot allocate the additional storage required for the MXT increase.
6.2 System resource requirements
Measure your current system processor and storage utilization to determine if
you need additional capacity to support the migration to VSE/ESA V2R4.
If you have real storage constraint problems or high processor utilization, then
you should add additional real memory and processor capacity as appropriate.
6.2.1 Processor considerations
You can expect an increase in your processor utilization when you migrate to
VSE/ESA V2R4. The VSE Turbo Dispatcher (TD) is required to run VSE/ESA
V2R4. If you are not running the Turbo Dispatcher on your current VSE system,
you will see more of an increase in processor utilization than users who are
running with the Turbo Dispatcher.
More processor cycles will also be used if you have to implement CICS/VSE
V2R3 and MRO for coexistence and are not using MRO on your current system.
The CICS Transaction Server for VSE/ESA Performance Considerations
document provides CPU measurement numbers to help you assess the CPU
requirements for your migration to VSE/ESA V2R4 and CICS TS.
For example, Table 18 on page 169 shows a summary using average measured
CPU increases when migrating from VSE/ESA V2R3 with and without the Turbo
Dispatcher to VSE/ESA V2R4. The measurements include a batch I/O-intensive
workload (PACEX) and online workload measurements for CICS/VSE V2R3 and
CICS TS using the CICS Data Systems Workload (DSW).
168 VSE/ESA V2R4
Table 18. VSE/ESA 2.4 Basic CPU requirements
VSE/ESA 2.4 Workload Migrating from VSE/ESA Migrating from VSE/ESA
2.3 w/o TD 2.3 with TD
Batch (PACEX) +20% +5%
CICS/VSE (DSW) +10% +6%
CICS TS (DSW) +16% +11%
The measurement results are for specific workloads.
For further information, consult CICS Transaction Server for VSE/ESA
Performance Considerations , which is available at the VSE Website:
http://www.s390.ibm.com/vse
You may experience different results, depending on your own environment and
workload.
6.2.2 Real storage considerations
The increase in virtual storage requirements may cause paging problems if you
are real storage-constrained today. You can use the VSE SIR command from the
console to determine if your VSE system is paging. You can also use the
VSE/ESA IUI system activity dialog to identify paging rates and potential
problems. The ideal paging rate is no paging so you can exploit more
data-in-memory facilities of VSE and CICS.
The real storage usage will depend on your working set of your VSE system.
You can have larger virtual storage allocations without affecting real storage, as
long as the working set does not increase dramatically.
We ran multiple CICS TS partitions in our VSE system with a VSIZE of 400 MB.
The system ran under VM in a 64 MB V = V guest machine. We did not observe
any paging problems. There was some paging during CICS TS startups, as
expected.
6.3 Statistics and monitoring
CICS TS has changed the way it collects statistics and monitoring data. CICS
Statistics and Monitoring domains issue requests to a new facility, the Data
Management Facility (DMF), to record data to VSAM datasets.
You can also implement a CICS-supplied sample program to capture statistics.
The sample program writes statistics to temporary storage or the POWER LST
queue and does not require DMF.
6.3.1 Setting up the Data Management Facility
To implement DMF, you must perform the following tasks:
1. Define the DMF datasets.
2. Initialize the DMF datasets.
3. Generate the DMF startup table.
4. Create a DMF startup job.
5. Learn how to operate DMF.
Chapter 6. Performance and tuning 169
6. Create jobstreams to process the DMF data.
For additional information on the setup and operation of DMF, see CICS
Transaction Server for VSE/ESA Operations and Utilities Guide .
6.3.1.1 Define the DMF Datasets
DMF datasets DFHDMFA and DFHDMFB are defined during the installation of
VSE/ESA V2R4. These are adequate for testing DMF, however, you should delete
and re-define these with new allocations to meet your data collection needs.
Figure 124 shows the jobstream we created to re-define the DMF datasets.
* $$ JOB JNM=DMFDEFS,CLASS=0,DISP=D
* $$ LST CLASS=A,DISP=D
// JOB DMFDEFS DEFINE CICS/TS DMF DATASETS
// EXEC IDCAMS,SIZE=AUTO
DELETE (CICSTS.SYSTEM.DFHDMFA) CL NOERASE PURGE -
CATALOG(VSESP.USER.CATALOG)
DELETE (CICSTS.SYSTEM.DFHDMFB) CL NOERASE PURGE -
CATALOG(VSESP.USER.CATALOG)
DEFINE CLUSTER (NAME(CICSTS.SYSTEM.DFHDMFA) - . .
NONINDEXED -
CYLINDERS(5) - . .
REUSE -
RECORDSIZE (125 32767) -
SPANNED -
VOLUMES (SYSWK1) - . .
NOCOMPRESSED -
SHAREOPTIONS (2) -
TO (99366 )) -
DATA (NAME (CICSTS.SYSTEM.DFHDMFA.@D@) -
CONTROLINTERVALSIZE (4096)) -
CATALOG (VSESP.USER.CATALOG)
DEFINE CLUSTER (NAME(CICSTS.SYSTEM.DFHDMFB) - . .
NONINDEXED -
CYLINDERS(5) - . .
REUSE -
RECORDSIZE (125 32767) -
SPANNED -
VOLUMES (DOSRES) - . .
NOCOMPRESSED -
SHAREOPTIONS (2) -
TO (99366 )) -
DATA (NAME (CICSTS.SYSTEM.DFHDMFB.@D@) -
CONTROLINTERVALSIZE (4096)) -
CATALOG (VSESP.USER.CATALOG)
/*
/&
* $$ EOJ
Figure 124. DMF VSAM dataset definition
. . You can define up to 36 DMF datasets for the VSE system.
The datasets created during VSE installation are:
CICS.DBDCCICS.DFHDMFA
CICS.DBDCCICS.DFHDMFB
170 VSE/ESA V2R4
We changed the names to emphasize that these are system datasets used
for all CICS partitions running in the VSE system, not just the DBDCCICS
CICS.
. . Change the allocation to meet your system requirements.
The VSE installation creates DMF datasets with allocations of six tracks
primary and two tracks secondary for 3390 DASD. These are too small for
normal use. We changed this to five cylinders with no secondary allocation
for our testing. Ten cylinders is probably a better starting point.
CICS will automatically switch DMF datasets when the currently active
dataset becomes full. If secondary allocation is used, switching between
datasets will not occur until the file has extended to the maximum number
of VSAM secondary allocations.
Since these are defined with the REUSE attribute, this will result in 16
VSAM extents per volume for each DMF dataset defined with secondary
allocation.
. . Change the volumes to match your installation.
The VSE installation definitions use secondary allocation across multiple
volumes. Primary allocation only requires one volume.
6.3.1.2 Initialize the DMF datasets
The VSE-supplied DMF datasets are initialized during the VSE installation
process. You must re-initialize these if you re-define the datasets to increase
the allocations, or to clear the data that has been collected.
Figure 125 shows the jobstream we created to initialize the DMF datasets.
* $$ JOB JNM=DMFINIT,DISP=D,CLASS=0
// JOB DMFINIT FORMAT CICS DMF DATASETS
// DLBL DFHDMFA,'CICSTS.SYSTEM.DFHDMFA',,VSAM,CAT=VSESPUC . .
// DLBL DFHDMFB,'CICSTS.SYSTEM.DFHDMFB',,VSAM,CAT=VSESPUC
// LIBDEF *,SEARCH=PRD1.BASE
// EXEC DFHDFOU,SIZE=DFHDFOU . .
INDD(DFHDMFA, OPTIONS (CLEAR)) . .
INDD(DFHDMFB, OPTIONS (CLEAR))
/*
/&
* $$ EOJ
Figure 125. DMF initialization jobstream
. . Add these file labels to standard labels to replace the VSE-supplied
definitions if you change the dataset names.
. . This executes the CICS-supplied DMF dump utility program.
. . One control statement is needed for each DMF dataset that you want to
initialize.
Chapter 6. Performance and tuning 171
6.3.1.3 The DMF startup table
The DMF startup table contains the initialization parameters used by the DMF
startup job when it is activated. This table is only used for DMF startup and is
not referenced by any CICS partitions in your system.
VSE supplies a sample DMF startup table in skeleton member DFHDMFSP in
ICCF library 59. CICS supplies a default DMF startup table DFHDMFSU. The
source is in library PRD1.BASE in member DFHDMFSU.A.
Figure 126 lists a modified copy of the VSE-supplied skeleton that we used for
our implementation.
* $$ JOB JNM=DFHDMFSP,CLASS=A,DISP=D,NTFY=YES
* $$ LST CLASS=Q,DISP=H
// JOB DFHDMFSP ASSEMBLE
// LIBDEF *,CATALOG=PRD2.CONFIG
* IN CASE GENERATION FEATURE IS INSTALLED ACTIVATE THE FIRST LIBDEF
* // LIBDEF SOURCE,SEARCH=(PRD2.GEN1,PRD1.BASE,PRD1.MACLIB)
// LIBDEF SOURCE,SEARCH=(PRD1.BASE,PRD1.MACLIB)
// OPTION CATAL,LIST
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
*****************************************************
* *
* 5686-066 (C) COPYRIGHT IBM CORP. 1996 *
* *
*****************************************************
TITLE 'DFHDMFSP -- SUPPLIED BY VSE/ESA'
PUNCH ' CATALOG DFHDMFSP.OBJ REP=YES'
DFHDMFM TABLE, *
. . CATALOG=VSESP.USER.CATALOG, USE VSESPUC *
. . FILELIST=(CICSTS.SYSTEM.DFHDMFA,CICSTS.SYSTEM.DFHDMFB), *
. . INTERVAL=3000, 30 MINUTES 0 SECONDS *
LISTDSN=YES, SHOW DATASETS WHEN DMF STARTS *
SID=VSE, SYSTEM IDENTIFIER *
. . SIZE=4, USE A 4M DATA SPACE *
STATUS=ACTIVE, DMF IS ACTIVE AT START *
SUFFIX=SP, THIS TABLE IS CALLED DFHDMFSP *
TRACE=NO, NO TRACE ACTIVITY *
. . TRTABSZ=1024, TRACE TABLE SIZE IS 1M *
TYPE=0:255, RECORD ALL DMF DATA RECORD TYPES *
. . USAGE=50 REDUCE SPACE WHEN 50% FULL
END
/*
// IF $MRC GT 4 THEN
// GOTO NOLINK
// EXEC LNKEDT,PARM='MSHP'
/. NOLINK
/*
/&
* $$ EOJ
Figure 126. DMF startup table
. . The name of the VSE catalog in which you defined the DMF datasets.
172 VSE/ESA V2R4
. . The names of the datasets you defined for DMF to use.
If you have multiple DMF datasets, an easier way to code the filename list
is:
GENFILES=4,GENPREFIX=(CICSTS.SYSTEM.DFHDMF), *
This will generate four filenames suffixed with Z, Y, X and W respectively.
. . Defines how often you want DMF to dump the data in its data space to the
currently active DMF dataset.
. . Specify DMF's data space size and include it in your data space
requirements.
. . Size of DMF's internal trace table.
. . How full the data space must be before DMF writes records to the currently
active dataset.
6.3.1.4 Create a DMF startup job
DMF executes in its own partition separate from your CICS partitions. You can
have only one DMF job running in your VSE system at a time. You must start
DMF before CICS partitions can start recording statistics and monitoring data.
VSE supplies a sample DMF startup jobstream in skeleton member SKDMFST in
ICCF library 59. The supplied skeleton job contains a jobstep that re-initializes
the DMF datasets before starting DMF. You should move this jobstep to a
separate job; otherwise, data would be cleared if the VSE system were IPLed
before you processed the DMF datasets.
Figure 127 contains a copy of the VSE-supplied skeleton that we tailored for our
DMF startup job.
* $$ JOB JNM=DMFSTART,CLASS=Z,DISP=L . .
* $$ LST CLASS=Q,DISP=H
// JOB DMFSTART DMF STATISTICS AND MONITORING SERVER
* ------------------------------------------------------------------*
* THIS JOB STARTS THE DMF SERVER PARTITION FOR CICS/TS *
* ------------------------------------------------------------------*
* FOR COMMUNICATION USE 'MSG XX' (PARTITION ID) AND . .
* 'XX SETDMF .' COMMANDS.
* TERMINATING:
* 'XX SETDMF SHUTDOWN'
* ------------------------------------------------------------------*
// EXEC DFHDFSIP,SIZE=DFHDFSIP,OS390 . .
SUFFIX=SP . .
/*
/&
* $$ EOJ
Figure 127. DMF startup jobstream
. . A dedicated partition must be allocated for DMF because it needs to be
active before statistics and monitoring data can be recorded. A 5 MB
partition is sufficient to execute DMF. We used one of the installation
supplied class Z dynamic partitions.
. . Instructions for communicating with DMF. See 6.3.1.5, “Operating DMF” on
page 174 for more details.
Chapter 6. Performance and tuning 173
. . Executes the DMF initialization program. OS390 is required on the EXEC
statement to emulate OS/390 services. The DSPACE parameter is not
required because DMF uses SCOPE=COMMON data space.
. . This is the suffix of your DMF startup table.
6.3.1.5 Operating DMF
Some of the operational aspects you need to consider when using DMF are:
Starting and stopping DMF
Controlling DMF
DMF is started by releasing the job described in Figure 127. Console messages
from the startup of DMF are listed in Figure 128.
Z1 0047 DFHDF0016 Data management facility has loaded program DFHDFRFP, which
has entry point X'8052E1D0'.
Z1 0047 DMF CONSOLE REPORT
DFHDF0007 This startup is using suffix SP. . .
Z1 0047 DMF CONSOLE REPORT
DFHDF0028 Data management facility trace status is set to NOTRACE.
Z1 0047 DMF CONSOLE REPORT
DFHDF0025 Data management facility has created data space named
DFHDF000, which is 4M bytes in size. . .
Z1 0047 DMF CONSOLE REPORT
DFHDF0016 Data management facility has loaded program DFHDFQMX, which
Z1 0047 DMF CONSOLE REPORT
DFHDF0016 Data management facility has loaded program DFHDFFM , which
has entry point X'805450D0'.
Z1 0105 DFHDF3001 Data set status report. . .
Z1 0105 DFHDF3002 Data Set Name Status Avail(%)
Z1 0105 DFHDF3003 CICSTS.SYSTEM.DFHDMFA INIT 100
Z1 0105 DFHDF3003 CICSTS.SYSTEM.DFHDMFB INIT 100
Z1 0105 DFHDF3004 Data set status report is complete.
Z1 0105 DMF CONSOLE REPORT
DFHDF3005 Data Management Facility dataset CICSTS.SYSTEM.DFHDMFA
is open. . .
Z1 0047 DMF CONSOLE REPORT
DFHDF0001 Data management facility is started.
Z1 0047 DMF CONSOLE REPORT
==>
Figure 128. DMF startup console messages
. . The suffix of the DMF startup table specified in the startup job.
. . The name and size of the data space allocated by DMF.
. . Current status of the DMF datasets defined in the DMF startup table. The
status indicates if a dataset is initialized (INIT), partially full (PARTIAL) or
completely full (FULL).
. . The currently active DMF dataset.
174 VSE/ESA V2R4
When the active dataset fills up, DMF switches datasets automatically similiar to
CICS journal switching. The following console messages are issued when the
datasets are switched:
Z1 0085 DMF CONSOLE REPORT
DFHDF3006 Data Management Facility dataset CICSTS.SYSTEM.DFHDMFA
is closed.
Z1 0085 DMF CONSOLE REPORT
DFHDF3005 Data Management Facility dataset CICSTS.SYSTEM.DFHDMFB
is open.
If all the datasets are full, DMF issues the following messages on the console:
Z1 0085 DFHDF3002 Data Set Name Status Avail(%)
Z1 0085 DFHDF3003 CICSTS.SYSTEM.DFHDMFA FULL 0
Z1 0085 DFHDF3003 CICSTS.SYSTEM.DFHDMFB FULL 0
Z1 0085 DFHDF3004 Data set status report is complete.
Z1 0085 DMF CONSOLE REPORT
DFHDF3007 Data Management Facility cannot find a dataset to open.
Reply 'GO' to cause DMF to continue operating but without a data set
(data will still be recorded in the data space), or 'RETRY' to cause
DMF to retry its attempt to open a data set
Z1-0085 DFHDF0000 Please enter reply
You need to run the DMF batch utility to dump and re-initialize the DMF datasets
so that DMF can continue recording to the datasets. DMF continues to collect
data in its dataspace until it fills; subsequent data recording will be lost.
To communicate with the DMF partition, enter the MSG xx command from the
VSE console where xx is the partition in which DMF is running. DMF responds
with:
Z1 0047 DMF CONSOLE REPORT
DFHDF1001 Data management facility is ready for communication. At the
prompt you may enter a DMF command, or request assistance by entering
a '?'
Z1-0047 DFHDF0000 Please enter reply
Table 19 lists some of the DMF commands you can enter.
Table 19 (Page 1 of 2). DMF operational commands
Console Command Function
? Lists general operating instructions for DMF.
?DISPLAY Lists information about the DISPLAY command.
?SETDMF Lists information about the SETDMF command.
Displays the current
active data set
DISPLAY O Displays current settings for DMF.
SETDMF NOACTIVE Suspends data recording.
SETDMF ACTIVE Resumes data recording.
SETDMF SWITCH Closes the active dataset and opens the next one.
SETDMF FLUSH Writes data in the data space to the active dataset.
Chapter 6. Performance and tuning 175
Table 19 (Page 2 of 2). DMF operational commands
Console Command Function
SETDMF SHUTDOWN Terminate DMF after writing to the active dataset and
closing it.
You can also issue DMF commands from the console using the format
MSG XX,DATA=SETDMF SHUTDOWN
6.3.2 Statistics
CICS TS has changed the way it records and reports statistics data. In previous
versions of CICS, statistics were written to transient data and typically printed on
SYSLST for subsequent review. In CICS TS, the CICS Statistics Domain issues
requests to DMF to record statistics data in DMF datasets. You then must run a
CICS batch utility jobstream to select and format the statistics that you require.
As a temporary alternative before setting up DMF for statistics recording, you
can implement a CICS-supplied sample program to record statistics. This
program writes statistics information to the POWER/VSE LST queue or to CICS
transient data. DMF is not required to produce this data.
The changes to statistics recording also affect some CICS resource definitions.
CSSM and CSSN transient data queues are no longer used and can be
removed from the DCT.
The statistics datasets DFHSTM and DFHSTN are also obsolete.
The CICS statistics transaction CSTT is replaced with CEMT commands.
6.3.2.1 Sample statistics program
The CICS sample statistics program produces statistics output similiar to the
shutdown statistics in prior versions of CICS. This program demonstrates the
use of new command level interfaces to collect statistics. The output from the
sample program is written to the POWER LST queue using the EXEC CICS
SPOOL interface.
To install the sample statistics programs, you must perform the following tasks:
1. Compile the sample statistics program mapset.
The source for the mapset is in member DFH0STM.A in VSE sublibrary
PRD1.BASE. You must compile the mapset before compiling the sample
program. The copybook from the mapset generation must be available in a
sublibrary accessible by the sample program compile.
2. Translate and compile the sample statistics program.
The sample program source is in member DFH0STAT.C in PRD1.BASE. The
program is written in COBOL.
3. Add resource definitions to the CSD for the programs, the mapset and the
STAT transaction.
The RDO entries to support the sample statistics program are supplied in the
CSD in RDO group DFH$STAT. If you plan to invoke the sample statistics
program from the shutdown PLT, you must ensure the RDO program entries
in this group specify CICS in the EXECKEY parameter. You must copy
176 VSE/ESA V2R4
DFH$STAT to your own RDO group to change the CICS-supplied definitions.
CICS-supplied group entries cannot be changed.
4. Add support for the system spool interface to your CICS startup.
You must code SPOOL=YES in your system initialization parameters to
support the EXEC SPOOL commands issued by the sample program.
The statistics output will be in a POWER LST queue entry separate from the one
containing the CICS startup JCL and CICS transient data messages. You can
identify the statistics LST queue entry by the user ID name in the FROM field.
For example, in the following LST queue display for CICS startup job CICSTS5,
the user ID that submitted the statistics output is SYSCICS5. This is the internal
name of this CICS used by the spool interface and the default used by the
sample program.
F1 0001 1R46I LIST QUEUE P D C S PAGES CC FORM
F1 0001 1R46I CICSTS5 01052 3 D A 16 1 FROM=(SYSCICS5)
F1 0001 1R46I CICSTS5 01051 3 D A 23 1 TO=(RES5) FROM=(RES5)
6.3.2.2 STAT transaction
You can also invoke the sample statistics program by entering the STAT
transaction from a terminal while CICS is running. Figure 129 shows the BMS
map that is displayed and the options that you can change when you enter the
STAT transaction.
Sample Program - CICS Statistics Print
03/29/99 07:49:56
Type in destination fields if required. Press Enter to print
Jobname . . : CICSTS5
Applid . . . : TSRES5
Sysid . . . : CIC5
Node . . . . . * Type in a valid Node. * is default
Userid . . . . * Type in a valid Userid. * is default
Class . . . . A Type in a valid Class. A is default
TS Queue Name Type in TS Queue name, to send out-
put to this TS queue instead.
Abbreviated Enter x for abbreviated TS report
Statistics print successfully completed
F3=Exit to CICS
Figure 129. Sample STAT transaction display
Chapter 6. Performance and tuning 177
6.3.2.3 Sample statistics program output
Figure 159 in Appendix B, “CICS TS Statistics output examples” on page 221
lists some of the output produced by the sample statistics program from one of
our CICS partitions. A total of sixteen pages of output were generated by the
sample program.
In our test we added an entry for the statistics program to the CICS shutdown
PLT. You can add the sample program to your shutdown PLT to capture
statistics when CICS is shut down. The VSE-supplied shutdown PLT skeletons in
ICCF library 59 contain a commented-out entry for the sample statistics program.
The output of the sample statistics program is very similar to the shutdown
statistics from previous CICS versions. Some of the more familiar statistics
include:
Task activity - total transactions, times at MXT, peak tasks
Storage usage
Transaction and program usage
File control and LSR pool activity
Temporary storage and transient data usage
There are also several new statistics recorded to help tune and monitor CICS
TS. New statistics are available for the areas mentioned, as well as for the new
parts of CICS TS such as the new dynamic storage areas and domains. See
CICS Transaction Server for VSE/ESA Performance Guide for a detailed
description of the statistics that CICS TS collects.
6.3.2.4 Collecting statistics using DMF
The CICS Statistics domain has four ways for collecting statistics and writing
them to DMF.
Interval statistics
The CICS statistics domain will collect statistics at intervals you specify and
write them to DMF. Interval statistics are only recorded if you specify the SIT
option STATRCD=ON at CICS startup or turn on recording with the CEMT
SET STATISTICS ON command. Statistics recording only needs to be turned
on to record interval statistics.
The default interval for statistics recording is every 3 hours. You can only
change this option using the CEMT SET STATISTICS command. Statistics
counters are reset after each interval. Capturing statistics this frequently
can produce a large amount of data. A sample report we created from one
day of interval statistics was several hundred pages.
Requested statistics
Statistics can be requested at any time by issuing the CEMT PERFORM
STATISTICS command. This does not require you to turn on statistics
recording. Statistics counters are also not reset.
End-of-day statistics
CICS collects and writes this set of statistics at logical end-of-day or when
you perform a normal shutdown. The default end-of-day is midnight. You
can change this with the CEMT SET STATISTICS command.
End-of-day statistics are similar to those produced by the sample statistics
program. These can also be used as a replacement for the shutdown
178 VSE/ESA V2R4
statistics produced by previous versions of CICS. Statistics recording does
not need to be turned on to collect these statistics.
Unsolicited Statistics
CICS writes statistics for resources that are dynamically allocated and
deallocated. For example, statistics for autoinstall terminals are now
automatically recorded to DMF before those terminals are deleted after they
are logged off.
Figure 160 on page 228 and Figure 161 on page 228 in Appendix B, “CICS
TS Statistics output examples” show two examples of unsolicited statistics
from one of our CICS TS partitions.
6.3.2.5 Processing DMF statistics data
You can use the VSE-supplied skeleton SKDMFPR in ICCF library 59 to create a
jobstream to process DMF statistics data. Figure 130 on page 180 shows a copy
of the skeleton we tailored to produce statistics reports from the DMF datasets.
Chapter 6. Performance and tuning 179
* $$ JOB JNM=DMFPRINT,CLASS=A,DISP=D,NTFY=YES
* $$ LST CLASS=Q,DISP=H
// JOB DMFPRINT PRINT DMF STATISTICS
* ------------------------------------------------------------------*
* THIS JOB PRINTS OFF STATISTIC DATA GATHERED BY DMF *
* ------------------------------------------------------------------*
* -------------------------------------------------------------------
* FIRST CLOSE THE DMF DATASET AS FOLLOWS:
* MSG XX,DATA=SETDMF FLUSH . .
* MSG XX,DATA=SETDMF SWITCH
* WHERE XX IS THE DMF SERVER PARTITION ID.
* -------------------------------------------------------------------
// PAUSE
* *********************************************************************
* STEP 1: UNLOAD DATA FROM THE DMF DATA SETS
* *********************************************************************
// DLBL INDD1,'CICSTS.SYSTEM.DFHDMFA',,VSAM,CAT=VSESPUC
// DLBL INDD2,'CICSTS.SYSTEM.DFHDMFB',,VSAM,CAT=VSESPUC
// DLBL OUTDD1,'CICSTS.DMF.DATA',0,VSAM,CAT=VSESPUC, X
DISP=(NEW,KEEP),RECORDS=2000,RECSIZE=5750
// EXEC DFHDFOU,SIZE=DFHDFOU
INDD ( INDD1, OPTIONS (DUMP)) . .
OUTDD ( OUTDD1, TYPE( 000:255) )
/* INDD ( INDD2, OPTIONS (DUMP))
/*
* ********************************************************************
* STEP 2: SORT, FORMAT AND PRINT THE STATISTICS RECORDS
*
* THE GENERATED OUTPUT DEPENDS ON THE SELECTION CRITERIA ENTERED
* IN DFHSTUP. YOU MAY SELECT ALL ENTRIES FOR A CERTAIN APPLICATION
* AS SHOWN OR YOU ALSO MAY SELECT ALL ENTRIES BY DATE:
* DATE START=MM/DD/YYYY,STOP=MM/DD/YYYY
* ********************************************************************
// DLBL DFHSTAT,'CICSTS.DMF.DATA',0,VSAM,CAT=VSESPUC, X
DISP=(OLD,DELETE),RECORDS=2000,RECSIZE=5750
// DLBL DFHSTWK,'%DOS.WORKFILE.SYS001.DFHSTWK',0,VSAM, X
CAT=VSESPUC,RECSIZE=4096, X
DISP=(,KEEP),RECORDS=2000
/* DLBL DFHSTWK,'SORT.WORK.FILE.1',0,SD
/* EXTENT SYS011,DOSRES,1,0,14520,300
/* ASSGN SYS011,DISK,VOL=DOSRES,SHR
* SORTWK1 LABEL IN STANDARD LABELS . .
// EXEC DFHSTUP,SIZE=1M,OS390 . .
SORT WORK=1
SELECT APPLID=DBDCCICS . .
DATE START=04/01/1999,STOP=04/08/1999
COLLECTION TYPE=ALL
/*
/&
* $$ EOJ
Figure 130. Sample DMF statistics print job
. . You must first issue these commands to flush data from the DMF data
space and to close the active DMF dataset before processing the DMF
data. You can also accomplish the same by shutting down DMF.
180 VSE/ESA V2R4
. . This job step dumps data from the DMF datasets to a sequential file.
The input can be the last active DMF dataset that was closed or can
be multiple DMF datasets. You need one INDD statement for each
DMF dataset that you want to dump.
. . The CICS statistics utility program DFHSTUP is used to process
statistics data from DMF. DFSORT or an equivalent sort product is
required.
. . OS390 emulation mode is required for execution of DFHSTUP.
. . DMF records statistics to the DMF datasets for all CICS TS partitions.
You can specify parameters to control selection of statistics data by
CICS partition, by date and by type of statistics.
The jobstream in Figure 130 on page 180 produced about 500 pages of printed
output for the eight days that were selected. The DMF statistics data collected
during this time period consisted of end-of-day statistics and unsolicited
statistics.
6.3.3 Monitoring
In addition to CICS statistics, you can also capture monitoring data in CICS TS.
The CICS Monitoring Facility (CMF) was available in prior releases of CICS to
collect monitoring data. CMF recorded monitoring data to CICS journals.
In CICS TS the CICS monitoring domain issues requests to the Data
Management Facility to record monitoring data to DMF datasets.
You must convert any user-written programs that process CMF data to use the
new monitoring record formats stored in the DMF datasets.
The CICSPARS/VSE product that processed CMF data from previous versions of
CICS will not work with monitoring data produced by CICS TS. If you have
vendor products that process CMF data, check with the vendor for updates to
their products.
CICS supplies a sample program, DFH$MOLS, to process monitoring data
produced by CICS TS. You can use the source in member DFH$MOLS.A as an
example to create your own program.
VSE supplies a sample jobstream to dump and process monitoring data from the
DMF datasets. This sample uses DFH$MOLS to process the data. It is in
member DFHMOLS in ICCF library 59.
Chapter 6. Performance and tuning 181
182 VSE/ESA V2R4
Chapter 7. CICS application program considerations
Since CICS TS does not support macro-level applications, you must carefully
check your applications. In this chapter we describe the changes that you have
to apply to your application programs if they use unsupported functions. In
addition we describe the DFHMSCAN and Application Migration Aid utilities that
help you with the migration.
7.1 Compatibility
All applications that use the command-level interface documented in CICS
Transaction Server for VSE/ESA Application Programming Reference are source-
and object-compatible, provided that the function and the programming language
are still supported.
Table 20 summarizes the programming language support for CICS TS.
Table 20. CICS TS Programming Language Support
Language Support
Assembler Assembler and high-level assembler supported.
LE/VSE languages COBOL for VSE/ESA, PL/I for VSE/ESA and C for VSE/ESA
supported.
DOS/VS COBOL Supported if link-edited with LE run-time library . ..
VS COBOL II Supported if link-edited with LE run-time library . ..
DOS PL/I and Not supported. Re-compile with the appropriate LE/VSE
C/370 compiler or run on CICS/VSE V2R3 coexistence release.
RPG II Not supported. Convert to LE/VSE language or run on
CICS/VSE V2R3 coexistence release.
. . May run if link-edited with their respective run-time libraries; however, if they
fail, they are not supported unless link-edited with LE/VSE run-time library.
Review CICS Transaction Server for VSE/ESA Release Guide and CICS
Transaction Server for VSE/ESA Migration Guide for a complete list of application
programming interface changes. If you are migrating from a CICS release prior
to CICS/VSE V2R3, you should also review the release guides from the earlier
Version 2 releases.
Changes in CICS security have impacted some options on the EXEC CICS
ASSIGN and EXEC CICS ADDRESS commands.
EXEC CICS ASSIGN OPERKEYS and OPSECURITY are not supported.
EXEC CICS ASSIGN USERNAME returns all blanks when using the BSM. The
field may be blank or have a value, depending on whether the ESM supports
it.
EXEC CICS ADDRESS ACEE is new and enables an application to obtain
security-related information available on earlier releases through methods
that are now obsolete.
You can re-design applications dependent on these fields to use the USERID field
on the EXEC CICS ASSIGN command.
© Copyright IBM Corp. 1999 183
The EXEC CICS ADDRESS CSA command has been removed because CICS does
not allow direct access to control blocks.
The &DFHEIMX global macro in application programs is no longer supported.
You must remove this macro when you convert mixed-mode programs
containing both macro- and command-level statements to all command levels.
EXEC DLI commands and their options are unchanged. If you have CICS DL/I
programs that use the CALLDLI interface, you must change these to use the UIB
rather than the TCA to check return codes.
The built-in-functions program and the BFP parameter in the SIT are no longer
supported. However, the command level built-in function EXEC CICS BIF DEEDIT
is still supported.
CICS TS does not support macro-level application programs. You can execute
these on VSE/ESA V2R4 using the CICS/VSE V2R3 coexistence environment
described in Chapter 4, “CICS coexistence” on page 117. You must convert
these applications to command level and one of the supported programming
languages to execute them on CICS TS.
7.2 Migrating macro-level applications
There are two utilities available that help you migrating your macro-level
applications:
DFHMSCAN
Application Migration Aid
We discuss these utilities in the following chapters.
7.2.1 DFHMSCAN
The CICS-supplied program DFHMSCAN can help you identify programs
containing CICS macro-level interfaces.
7.2.1.1 Creating a summary report
You can run the jobstream in Figure 131 to analyze programs in your VSE
application libraries for macro-level code and produce a summary listing.
* $$ JOB JNM=DFHMSCAN,CLASS=0,DISP=D,NTFY=YES
* $$ LST CLASS=Q,DISP=H
// JOB DFHMSCAN SCAN FOR MACRO PROGRAMS
// ASSGN SYS001,SYSLST
// ASSGN SYS002,SYSLST
// LIBDEF PHASE,SEARCH=(PRD2.USER,PRD1.BASE) . .
// EXEC DFHMSCAN,PARM='PRD2.USER,$SUMMARY' . .
/*
/&
* $$ EOJ
Figure 131. DFHMSCAN sample summary report job
. . The sublibrary containing DFHMSCAN must be in the LIBDEF search chain.
You must include the sublibrary to be scanned in both the LIBDEF statement and
in the PARM statement.
184 VSE/ESA V2R4
. . All the phases in sublibrary PRD2.USER are scanned for macro-level code.
Only one sublibrary can be scanned in each execution of DFHMSCAN.
A report is produced like the one in Figure 132. The report identifies the
following:
Module name and size
Type of program: CICS module(CICSMOD) or language the program is
written in
Number of macro-level (ML) and command-level (CL) statements
Number of unrecognized BALR statements: UR 14,14 and UR 14,15
DFHMSCAN PROGRAM - SUMMARY LISTING SUBLIBRARY: PRD2.USER
MODULE SIZE TYPE ML STMTS CL STMTS UR 14,14 UR 14,15
---------------------------------------------------------------------------
DFHMSCAN 000028F8 CICSMOD 0 0 3 2
DFHPEP 00000122 ASSEMBLR 0 3 0 2
DFHZNEP 000005CA CICSMOD 0 0 0 11
DFH0STAT 0001854A CICSMOD 0 0 0 85
DFH0STM 000003A8 CICSMOD 0 0 0 0
IESZATCO 000010D2 ASSEMBLR 0 20 0 2
IESZATDX 000010CA ASSEMBLR 0 20 0 2
OLDPEP 00000050 ASSEMBLR 1 0 0 0
OLDZNEP 0000061A ASSEMBLR 1 0 0 4
TOTAL NO. NUMBER ASSEMBLER COBOL PL/I
MODULES OF MACRO MACRO MACRO MACRO
SCANNED PROGRAMS PROGRAMS PROGRAMS PROGRAMS
9 2 2 0 0
Figure 132. Sample DFHMSCAN summary report
7.2.1.2 Creating a detailed report
After you have identified programs with macro-level statements, you can run the
jobstream in Figure 133 to obtain additional details about these programs.
* $$ JOB JNM=DFHMSCAN,CLASS=0,DISP=D,NTFY=YES
* $$ LST CLASS=Q,DISP=H
// JOB DFHMSCAN SCAN PROGRAMS FOR MACROS
// ASSGN SYS001,SYSLST
// ASSGN SYS002,SYSLST
// LIBDEF PHASE,SEARCH=(PRD2.USER,PRD1.BASE)
// EXEC DFHMSCAN,PARM='PRD2.USER,OLDPEP,OLDZNEP' . .
/*
/&
* $$ EOJ
Figure 133. DFHMSCAN sample detail report job
. . Only the phases listed in the PARM statement are scanned for macro-level
code in sublibrary PRD2.USER.
A report is produced like the one in Figure 134 on page 186. For the selected
phases, the report lists:
Chapter 7. CICS application program considerations 185
Each BALR statement found, its offset, and what macro it appears to be
An interpretation of the type of macro statements found
DFHMSCAN PROGRAM - DETAILED LISTING SUBLIBRARY: PRD2.USER
PROGRAM MODULE NAME - OLDPEP / LOAD MODULE SIZE - 00000050 / PROGRAM ENTRY POINT - 005405A0
OFFSET ADDRESS STORAGE CONTENT(HEX) MACRO, COMMAND, KEYWORD AND/OR COMMENT
----------------------------------------------------------------------------------------------------
00000018 005405B8 9288C080D207C084A0269200C08158E0D0E805EE DFHPC XCTL
00000026 005405C6 58E0D0E805EE9210C0809200C08158E0D0E805EE DFHPC XCTL
MODULE SIZE TYPE ML STMTS CL STMTS UR 14,14 UR 14,15
----------------------------------------------------------------------------------------------------
DFHMSCAN PROGRAM - SUMMARY LISTING SUBLIBRARY: PRD2.USER
MODULE SIZE TYPE ML STMTS CL STMTS UR 14,14 UR 14,15
----------------------------------------------------------------------------------------------------
OLDPEP 00000050 ASSEMBLR 1 0 0 0
OLDPEP 00000050 ASSEMBLR 1 0 0 0
Figure 134. Sample DFHMSCAN detailed report
Once you have inventoried your macro-level programs and identified the macro
statements in them, you can either convert them manually or use a conversion
aid like the CICS Application Migration Aid.
7.2.2 CICS Application Migration Aid (AMA)
The Application Migration Aid converts COBOL, PL/I or assembler language
macro-level source programs to command level. Most macro-level code is
converted directly to equivalent command-level statements.
Only macros documented in CICS Transaction Server for VSE/ESA Application
Programming Reference are converted. DFHFC TYPE=DL/I macro statements
are not converted. Diagnostics are provided for this and other statements that
cannot be converted.
AMA is supplied in VSE/ESA sublibrary PRD1.BASE, and is described in CICS
Transaction Server for VSE/ESA Application Migration Aid Guide .
7.3 VSE/ESA compile dialogs
The VSE/ESA V2R4 IUI compile dialogs have changed. You cannot generate
compile jobstreams for DOS/VS COBOL, DOS PL/I and C/370 using the IUI
dialogs. You have to create your own compile procedures for these languages if
you currently use the dialogs for them. Figure 135 on page 187 shows the IUI
compile job dialog screens for VSE/ESA V2R3.
Note that RPG II is still an option on the VSE/ESA V2R4 compile screen even
though it is not supported by CICS TS. The VSE/ESA V2R4 dialog generates an
online compile jobstream with the CICS/VSE V2R3 installation library
PRD2.CICSOLDP in the LIBDEF search chain. You can tailor this jobstream for
the other unsupported languages if you still maintain them for execution on
CICS/VSE V2R3.
FORTRAN language is batch only.
186 VSE/ESA V2R4
IESLIBM COMPILE JOB GENERATION
SOURCE MEMBER: DFHPEP
SOURCE TYPE....... 1 1=Online Program 2=Batch Program
3=Map Definition 4=Batch Subroutine
LANGUAGE.......... 1 1=HLASM 4=DOS COBOL 7=RPG II
2=DOS PL/I 5=COBOL II 8=FORTRAN (batch)
3=PL/I VSE 6=COBOL VSE 9=C/370
A=C VSE
DB2 SERVER....... 2 1=Yes, 2=No
CATALOG........... 2 1=Yes, 2=No
JOBNAME........... COMRES5 Name of the job to generate
OUTPUT MEMBER..... ________ Leave blank to submit the job immediately.
Enter a name and a password (optional) to
PASSWORD.......... save it (existing member is overwritten).
PF1=HELP 3=END 4=RETURN
Figure 135. VSE/ESA V2R3 IUI Compile Screen
Figure 136 shows the IUI Compile job dialog screen for VSE/ESA V2R4; note the
differences.
IESLIBM COMPILE JOB GENERATION
SOURCE MEMBER: DFH0STAT
SOURCE TYPE....... 1 1=Online Program 2=Batch Program
3=Map Definition 4=Batch Subroutine
LANGUAGE.......... 3 1=HLASM 2=PL/I VSE 3=COBOL VSE
4=C VSE 5=RPG II 6=FORTRAN
DB2 SERVER....... 2 1=Yes, 2=No
CATALOG........... 1 1=Yes, 2=No
JOBNAME........... COMRES5 Name of the job to generate
OUTPUT MEMBER..... ________ Leave blank to submit the job immediately.
Enter a name and a password (optional) to
PASSWORD.......... save it (existing member is overwritten).
PF1=HELP 3=END 4=RETURN
Figure 136. VSE/ESA V2R4 IUI Compile Screen
Chapter 7. CICS application program considerations 187
7.4 CICS Basic Mapping Support (BMS)
CICS BMS mapset DSECTs and objects are upward source- and
object-compatible.
BMS mapset objects can now be loaded above or below the 16 MB line.
Figure 137 on page 189 shows the mapset compile jobstream generated by the
IUI compile dialog.
The BMS mapset is catalogued with the RMODE and AMODE options shown in
. .. Both 24-bit and 31-bit application programs can access BMS mapsets
loaded above the line.
188 VSE/ESA V2R4
* $$ JOB JNM=DFH0STM,DISP=D,CLASS=A,NTFY=YES
* $$ LST DISP=D,CLASS=Q,PRI=3
// JOB DFH0STM COMPILE PROGRAM DFH0STM
// SETPARM CATALOG=1
// IF CATALOG = 1 THEN
// GOTO CAT
// OPTION NODECK,ALIGN,LIST,SYSPARM='MAP'
// GOTO GENER
/. CAT
// LIBDEF PHASE,CATALOG=PRD2.USER
// OPTION CATAL,NODECK,ALIGN,LIST,SYSPARM='MAP'
PHASE DFH0STM,*
MODE RMODE(ANY),AMODE(31) . .
/. GENER
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
PRINT NOGEN
* $$ SLI ICCF=(DFH0STM),LIB=(0015)
/*
// IF CATALOG NE 1 OR $MRC GT 4 THEN
// GOTO ENDM
// EXEC LNKEDT,SIZE=256K
/*
* $$ PUN DISP=I,DEST=*,PRI=9,CLASS=A
// ASSGN SYSIPT,SYSRDR
// EXEC IESINSRT
$ $$ LST DISP=D,CLASS=Q,PRI=3
#/ JOB DFH0STM CATALOG MAP DFH0STM
// EXEC LIBR
ACCESS SUBLIB=PRD2.USER
CATALOG DFH0STM.C REPLACE=YES
* $$ END
// ON $CANCEL OR $ABEND GOTO ENDJ2
// OPTION NOLIST,ALIGN,DECK,SYSPARM='DSECT'
// EXEC ASMA90,SIZE=(ASMA90,64K),PARM='EXIT(LIBEXIT(EDECKXIT)),SIZE(MAXC
-200K,ABOVE)'
PRINT NOGEN
* $$ SLI ICCF=(DFH0STM),LIB=(0015)
/*
/. ENDJ2
// EXEC IESINSRT
/*
#&
$ $$ EOJ
* $$ END
/. ENDM
/&
* $$ EOJ
Figure 137. IUI Generated BMS mapset compile job
Chapter 7. CICS application program considerations 189
190 VSE/ESA V2R4
Chapter 8. CICS problem determination
This chapter helps you make a quick start with the tracing and dumping facilities
available with the TS for VSE/ESA R1. It also highlights the differences you will
encounter when migrating from CICS Version 2.3.
It provides the following:
An overview of the new environment
CICS tracing
CICS dumps
Changes to CSFE and CEDF
8.1 Overview
The new environment provides for greater flexibility and control of the tracing
activity.
You can determine the following for each specific case:
The CICS domain or subcomponent you want to trace
The level of detail of the generated trace entries
The scope of the trace for:
− A specific transaction
− A specific terminal
− Both a transaction and a terminal
The most significant changes in the problem determination area under CICS TS
for VSE/ESA R1 are:
1. CICS Traces
New exception trace entries
New trace control keywords in the SIT
New CICS-supplied transaction CETR
Utility program DFHTU410 to format auxiliary traces
INFOANA's DFHPD410 exit to format the CICS Internal Trace table from a
SYSDUMP
2. CICS dumps
New keywords for dump control in the SIT
CEMT and CICS commands to control the DUMP table
Print dump exit for INFOANA: DFHPD410
Dump utility program DFHDU410 to format transaction dumps
3. Changes to CSFE and CEDF
CSFE new syntax for TASK and TERMINAL subpools
CEDF support for remote transactions
© Copyright IBM Corp. 1999 191
8.2 CICS tracing
STANDARD TRACE This is performed by the trace domain, at
predetermined trace points in CICS code during the
regular flow of control.
SPECIAL TRACE This is taken for selected tasks and for selected
terminals at trace points other than the standard trace
point. You can run special tracing even if the flag for
the master (standard) tracing is turned off.
USER TRACE This is requested by the application program (AP
domain). Entries have point IDs in the range AP0000 to
AP00C2, and the numeric part of the entry ID is
specified in the application.
EXCEPTION TRACE Trace entries generated by CICS when
exceptional/abnormal conditions are detected as part
of the first failure data capture mechanism.
This tracing cannot be suppressed: entries are always
written to the internal trace table.
8.2.1 Trace levels
Trace levels can vary in value in the range 1 to 32, but most of the mainline
trace points have a trace level of 1 or 2.
LEVEL-1 trace points They are designed to provide enough information to fix
user errors.
They are located as follows:
At many points where trace calls were made in
CICS/VSE Version 2
On entry to, and return from, every CICS domain
On entry to, and return from, major internal functions
within a CICS domain
Before and after calls to other programs, for
example VTAM
The type of information is the same as provided by
CICS/VSE Version 2.
LEVEL-2 trace points These are situated between LEVEL-1 trace points, and
are designed to assist with determining problems within
the CICS code.
LEVEL-3 and above They are reserved for special cases - and are likely to
be of use for IBM personnel only. Very few components
have trace levels above 2.
192 VSE/ESA V2R4
8.2.2 Control options
The initial settings for tracing are coded via the appropriate keywords in the
system initialization parameters.
The system defaults set by the CICS/TS and VSE/ESA supplied samples for the
system initialization table provide trace settings similar to the CICS/VSE V2
environment:
Standard tracing for all transactions
Level-1 trace points for all CICS components
These settings are generally adequate to deal with user problems in a
development or test CICS region.
For a CICS production region, however, you may chose to suppress all
background tracing activity for performance. See 8.2.6.1, “Production regions” on
page 199 for an example.
With CICS/TS for VSE/ESA R1 you can have tracing at the transaction level
rather than the system level tracing of the previous CICS versions. Refer to
8.2.4, “CETR overview” on page 194 for details.
8.2.3 Default SIT options
Table 21. Trace-related keywords
SIT Keyword USAGE
AUXTR=OFF To disable the auxiliary trace
AUXTRSW=NO To disable auxtrace datasets switching
INTTR=ON Activates the main storage trace
SPCTR=(1,2) Sets levels 1 and 2 for all CICS components used by a
transaction, a terminal (or both) when selected for special
tracing
SPCTRxx To activate the special tracing for CICS component xx (not
set)
STNTR=1 To set the detail level for standard tracing for the whole
CICS
STNTRxx To set the detail level for standard tracing for CICS
component xx (not set)
SYSTR=ON Master system trace flag to obtain standard trace entries
of CICS system activity
TRTABSZ=16 To set size of the internal trace table (in KBytes)
TRTRANSZ=40 To set the size of the transaction dump trace table (in
KBytes)
TRTRANTY=TRAN To specify that only transaction-related entries should be
copied from the internal trace table to the transaction
dump trace table
USERTR=ON Master user trace flag enabling user tracing
Chapter 8. CICS problem determination 193
8.2.4 CETR overview
CETR is a CICS-supplied transaction that allows you to control CICS tracing
activity. The overriding options set via CETR will prevail for the current and
subsequent CICS sessions and will only be reset to the initial SIT values after a
CICS cold start. When invoking CETR from a CICS terminal, the panel shown in
Figure 138 is displayed:
CETR CICS Trace Control Facility CICS IYAHZCCV
Type in your choices.
Item Choice Possible choices
Internal Trace Status ===> STARTED STArted, STOpped
Internal Trace Table Size ===> 100 K 16K - 1048576K
Auxiliary Trace Status ===> PAUSED STArted, STOpped, Paused . .
Auxiliary Trace Dataset ===> B A, B
Auxiliary Switch Status ===> NO NO, NExt, All
Master System Trace Flag ===> ON ON, OFf . .
Master User Trace Flag ===> ON ON, OFf . .
When finished, press ENTER.
PF1=Help 3=Quit 4=Components 5=Ter/Trn 9=Error List
Figure 138. CETR transaction: initial screen
. .Auxiliary trace data set is open, but the trace is not started.
. .CICS Trace and User Trace are enabled.
The panel displays the current state of CICS Internal and Auxiliary trace and the
settings of the master system and user trace flags. The values can be altered by
overtyping the current settings.
Notes:
Online help is invoked by pressing PF1.
PF5 invokes the Transaction and Terminal Trace Panel.
194 VSE/ESA V2R4
PF4 invokes the Component Trace Options Panel, as shown in Figure 139:
CETR Component Trace Options CI41 IYAHZCCV
Over-type where required and press ENTER. PAGE 1 OF 3
Component Standard Special
-------- ------------------------------- -------------------------------
AP 1 1-2
BF 1 1
BM 1 1
CP 1 1-2
DC 1 1
DD 1 1-2
DI 1 1
DM 1 1-2
DS 1 1-2
DU 1 1-2
EI 1 1-2
FC 1 1-2
GC 1 1-2
IC 1 1
IS 1 1-2
JC 1 1
KC 1 1
PF: 1=Help 3=Quit 7=Back 8=Forward 9=Messages ENTER=Change
Figure 139. CETR transaction: component trace options screen
The Component Trace panel is used to inquire about and set the STANDARD and
SPECIAL trace levels for the individual components of the CICS system. To see
the meaning of the components abbreviations, press PF1.
Each CICS task is either a STANDARD tracing task or a SPECIAL tracing task.
This task attribute is analyzed by CICS when the task is attached, depending on
the settings for the task and the settings for the terminal where the task is
initiated.
By default, all tasks and terminals are STANDARD. You can override this task
attribute on the Terminal and Transaction Trace panel of CETR. It is common
practice to set higher trace levels for SPECIAL tracing than for STANDARD (see
Figure 139).
You can disable tracing for components that are not involved with the problem
you are debugging by typing OFF over the trace level for the component. If you
set one terminal for SPECIAL and another terminal for STANDARD, you can
debug the same transaction with different trace options, depending on the
terminal you initiate the transaction from.
Chapter 8. CICS problem determination 195
8.2.5 Using CETR
When you press the PF5 key in the Trace Control Facility panel, the Terminal
Tracing panel is displayed; see Figure 140.
Entering a valid transaction ID or a valid terminal ID and pressing Enter will
display the current tracing option for that transaction (STANDARD, SPECIAL or
SUPPRESSED) or terminal (STANDARD or SPECIAL).
Note: By default, STANDARD tracing is set for all transactions and terminals.
To suppress tracing for transaction TR01:
1. Enter TR01 in the transaction ID field.
2. Overtype the default STANDARD in the transaction status field with the SU
option.
3. Press Enter.
CETR Transaction and Terminal Trace CI41 IYAHZCCV
Type in your choices.
Item Choice Possible choices
Transaction ID ===> TR01 Any valid 4 character ID
Transaction Status ===> SU STandard, SPecial, SUppressed
Terminal ID ===> Any valid Terminal ID
Netname ===> Any valid Netname
Terminal Status ===> STandard, SPecial
Terminal ZCP Trace ===> ON, OFf
When finished, press ENTER.
PF1=Help 3=Quit 9=Error List
Figure 140. CETR transaction: transaction and terminal trace screen - SU option
196 VSE/ESA V2R4
Now we clear the TRANSACTION ID field and set terminal T080 for STANDARD
tracing; see the following figure. .
terminal T081 for SPECIAL.
CETR Transaction and Terminal Trace CI41 IYAHZCCV
Type in your choices.
Item Choice Possible choices
Transaction ID ===> TR01 Any valid 4 character ID
Transaction Status ===> STandard, SPecial, SUppressed
Terminal ID ===> T080 Any valid Terminal ID
Netname ===> Any valid Netname
Terminal Status ===> ST STandard, SPecial
Terminal ZCP Trace ===> ON, OFf
When finished, press ENTER.
PF1=Help 3=Quit 9=Error List
Figure 141. CETR transaction: transaction and terminal trace screen - ST option
We set terminal T081 for SPECIAL; see the following figure.
Chapter 8. CICS problem determination 197
CETR Transaction and Terminal Trace CI41 IYAHZCCV
Type in your choices.
Item Choice Possible choices
Transaction ID ===> Any valid 4 character ID
Transaction Status ===> STandard, SPecial, SUppressed
Terminal ID ===> T081 Any valid Terminal ID
Netname ===> Any valid Netname
Terminal Status ===> SP STandard, SPecial
Terminal ZCP Trace ===> ON, OFf
When finished, press ENTER.
PF1=Help 3=Quit 9=Error List
Figure 142. CETR transaction: transaction and terminal trace screen - SP option
With these settings:
TR01 will generate STANDARD trace entries when initiated from terminal
T080.
TR01 - and any other transaction - initiated from terminal T081 will generate
SPECIAL trace entries.
TR01 will not be traced if initiated from any other (non-SPECIAL) terminal or
if initiated via EXEC CICS START TRANSID.
198 VSE/ESA V2R4
8.2.6 Tracing scenarios
Setting up the traces depends on the activities you perform. The following
describes two different scenarios:
Tracing for production regions
Tracing for development regions.
8.2.6.1 Production regions
To eliminate the overhead of background tracing, do the following:
1. Code the following SIT keywords:
SYSTR=OFF . .
AUXTR=ON . .
AUXTRSW=ALL . .
2. Make sure that no special tracing has been specified for any task or
terminal.
3. Set AUXTRACE to STARTED from the CETR initial screen.
. .This switches the system master trace flag off: all system tracing, except
special and exception traces, will be suppressed.
There is no equivalent master trace flag to turn the special trace on/off.
. .This activates auxiliary tracing. However, SYSTR=OFF will suppress all the
standard tracing in the system: the only entries written to the auxiliary trace data
set (assuming you do not specify special tracing for any task or terminal) are the
exception trace entries. In a long CICS run (typical in production regions) and
given the (default) internal trace table size of 16 KB, it is likely that the internal
trace table will fill up with the exception entries. During the subsequent
wraparound, some of them would be lost. With AUXTR=ON, the internal trace
table is used as a buffer and you have the guarantee that all exception entries
will be captured in the auxiliary trace data sets.
In the case of an unplanned system abend, the exception trace entries will be
available for a first-hand diagnosis. It is unlikely that this information alone will
be enough to fix the problem, but it can lead you to identify a failing module or
transaction.
In this case you can use CETR to set one terminal to SPECIAL; then, start the
transaction you want to debug from the terminal you just set.
Once you finish, do not forget to reset the terminal attribute to STANDARD.
. .This enables continuous switching between the two auxiliary trace data sets,
DFHAUXT and DFHBUXT.
8.2.6.2 Development regions
The default settings are adequate for development or test regions (standard
tracing is generated for all transactions).
Chapter 8. CICS problem determination 199
If you need to generate SPECIAL tracing when debugging a particular
transaction, all you need to do is use CETR to set one terminal to SPECIAL and
start the transaction you want to trace from that terminal.
8.2.7 Trace formatting
Table 22 lists the trace formatting utilities.
Table 22. Trace formatting utilities
To format From Utility
Internal trace table CICS system dump DFHPD410
Internal trace table Transaction dump DFHDU410
Auxiliary trace Aux trace data set DFHTU410
8.2.7.1 INFOANA exit DFHPD410
DFHPD410 is the exit for INFOANA to format and print CICS SDUMPs from the
VSE Dump Library.
The CICS Internal Trace Table is printed when formatting the system dump if the
Trace Domain is selected as follows:
Via the component keyword with a non-zero operand, for example TR=1.
Via the non-zero DEFault, for example DEF=2.
Dumps from previous CICS versions cannot be formatted by this exit.
To collect the CICS dumps, generated via the SDUMP macro, the following
conditions are required:
SYSDUMP option must be active for the partition.
LIBDEF DUMP information
There must be enough space in the VSE dump library.
Note: If a Dump Library Full condition arises when a CICS dump is being
written, an unformatted dump is printed in SYSLST unless the VSE option
SYSDMPC is set for the partition, in which case the dump is suppressed.
8.2.7.2 Formatting an SDUMP
Figure 143 on page 201 shows a job to format a CICS dump.
200 VSE/ESA V2R4
* $$ JOB JNM=PRTDUMP,DISP=D,PRI=8,NTFY=YES,CLASS=0
* $$ LST DISP=H
// JOB PRTDUMP
// EXEC PROC=DTRINFOA
// EXEC INFOANA,SIZE=INFOANA
DUMP NAME SYSDUMP.F2.DF200000
SELECT DUMP VIEWING
CALL DFHPD410 DATA DEF=3,KE=1,SM=1,FCP=2,DS=0 . .
/*
/&
* $$ EOJ
Figure 143. Job to format a CICS dump
. .DFHPD410 is called to format the dump. The dump exit parameters are
coded following the INFOANA DATA keyword.
The syntax of the component parameter is component-keyword=level of detail
where level of detail can be:
0 Suppress output for this component
1 Summary only (1 output line per entry)
2 Full format of control blocks
3 Summary and full format (that is, 1 and 2)
This job will produce:
Summary and full format output for all the components that are not selected
(DEF=3).
Summary output only for the Kernel and Storage domains (KE=1,SM=1)
Full format (but no summary) for the File Control Program (FCP=2)
All output from the Dispatcher Domain will be suppressed (DS=0)
8.2.7.3 Using the IUI dialogs to format the SDUMP
If you use IUI dialogs (fastpath 4.3 from the IESEADM panel, and then select
Analyze CICS Dump option), a INFOANA job stream is generated with the
following options:
KE=3 DS=3 TR=3 LD=3
The job will print abbreviated plus full format trace entries for the Kernel,
Dispatcher, Trace and Loader domains.
You can, of course, store the JECL in your ICCF library and modify the selection
according to your needs before submitting it for execution. Note that INFOANA
will always print the dump summary, even if no valid, or null, selection options
are present; see Figure 144 on page 202 for an example.
Chapter 8. CICS problem determination 201
=== DUMP SUMMARY
DUMPID: 16/0002
. . DUMPCODE: MT0001
. . DATE/TIME: 99/04/06 14:36:20 (LOCAL)
MESSAGE: (None)
. . SYMPTOMS: PIDS/564805400 LVLS/410 MS/NOID RIDS/DFHEDCP
TITLE: (None)
CALLER: (None)
ASID: X'0000'
Figure 144. Sample of a dump summary
. .A dump is requested via the Master Terminal (CEMT PERFORM DUMP).
. .Always check the DATE/TIME to make sure this is the dump you think it is.
. .This shows the CICS component ID, release, error message (if any) and
affected module.
8.2.7.4 Formatting the CICS Internal Trace table
If all you want to format from the SDUMP is the CICS Internal Trace table, then
do the following (see Figure 145).
1. SELECT the TRACE COMPONENT (TR=1 to 3).
2. SUPPRESS the output from all other components (DEF=0).
* $$ JOB JNM=PRTDUMP,DISP=D,PRI=8,NTFY=YES,CLASS=0
* $$ LST DISP=H
// JOB PRTDUMP
// EXEC PROC=DTRINFOA
// EXEC INFOANA,SIZE=INFOANA
DUMP NAME SYSDUMP.F2.DF200000
SELECT DUMP VIEWING
CALL DFHPD410 DATA DEF=0,TR=3
/*
/&
* $$ EOJ
Figure 145. Sample job to format the trace table
The job will produce both a summary and a full formatted record (TR=3) for
every trace entry; see Figure 146 on page 203.
202 VSE/ESA V2R4
===TR: TRACE DOMAIN ABBREVIATED TRACE . .
. . Internal trace is STARTED: Table size is 80K
. . Auxiliary trace is STOPPED: Current extent is DFHAUXT: Autoswitch status is OFF
INTERNAL TRACE TABLE
18201 1 LD 0002 LDLD EXIT ACQUIRE_PROGRAM/OK 004B98D0,004B98D0,1E9A,0,REUSABLE,CDSA,OLD_COPY . .
18201 1 PG 0602 PGLD EXIT LOAD_EXEC/OK 004B98D0,004B98D0,1E9A,00000000 . .
Figure 146. The SUMMARY trace report
. . This is the header of the Trace Domain report.
Note: When browsing the formatted SDUMP, you can locate the header of a
component report by the string of three equal signs followed by the component
ID; for example, = = = S M will mark the beginning of the Storage Management
report.
. .This shows information on the status of the trace environment at the time the
dump was taken.
. .These are abbreviated trace entries.
Figure 147 shows the FULL trace report.
===TR: TRACE DOMAIN FULL
LD 0002 LDLD EXIT - FUNCTION(ACQUIRE_PROGRAM) RESPONSE(OK) ENTRY_POINT(004B98D0) LOAD_POINT(004B98D0) PROGRAM_LENGTH(1E9A)
FETCH_TIME(0) PROGRAM_ATTRIBUTE(REUSABLE) LOCATION(CDSA) COPY_STATUS(OLD_COPY)
. . . . . . . .
TASK-18201 KE_NUM-000F TCB-002D9000 RET-81C1CF06 TIME-10:39:16.6224925000 INTERVAL-00.0000071250 =000002=
1-0000 00880000 0000001C 00000000 00000000 B4680A54 00000000 01000140 C9C5E2C5 *.h......................... IESE
0020 D3C9C240 01F092D0 01F3B738 01F092D0 00700000 004B98D0 004B98D0 00000000 *LIB .0k..3...0k.......q...q.....
. . 0040 00001E9A 00000000 03000100 C4F0F8F5 F0F14040 C2F0F0F7 00000000 00000000 *............D08501 B007........
0060 01F8D01C 00000000 01021F70 01BD0174 02028000 00800200 00000000 00000000 *.8..............................
0080 00000000 00000000 *........
PG 0602 PGLD EXIT - FUNCTION(LOAD_EXEC) RESPONSE(OK) LOAD_POINT(004B98D0) ENTRY_POINT(004B98D0) PROGRAM_LENGTH(1E9A)
LANGUAGE_TOKEN(00000000)
TASK-18201 KE_NUM-000F TCB-002D9000 RET-81C6F09A TIME-10:39:16.6224992500 INTERVAL-00.0000067500 =000003=
1-0000 00400000 00000099 00000000 00000000 BF820000 00000000 01600100 C9C5E2C5 *. .....r.........b.......-..IESE
0020 D3C9C240 004B98D0 004B98D0 00001E9A 01000028 00000000 00000000 A5000000 *LIB ..q...q.................v...
Figure 147. The corresponding FULL trace report
As you can see, the FULL trace entry contains control blocks and Data
information that is not shown in the corresponding abbreviated trace:
. .The task number assigned by the Kernel
. .The TCB address of the VSE subtask
. .The call return address
. .The time stamp
. .The Data area
The detailed description of every trace entry can be found in CICS Transaction
Server for VSE/ESA Trace Entries Handbook .
Chapter 8. CICS problem determination 203
8.2.7.5 Trace entry selection
The DFHPD410 exit does not provide the capability to select trace entries from
the internal trace table; instead, all entries are processed. The only choice
available is the level of detail coded with the T R = component keyword.
If you want to use any valid selection parameters available to the auxiliary trace
print utility DFHTU410 to format the internal trace table of an SDUMP, note the
following:
1. The TRACE domain must be selected: T R = n (where n is not zero).
2. Use the TRace Selection (TRS=) parameter as a component keyword and
code as the second operand on any of the select options supported by
DFHTU410.
For an overview of the selection parameters available for DFHTU410, see 8.2.7.8,
“Formatting the Auxiliary Trace” on page 206.
Figure 148 shows an example of using the TRS parameter.
// JOB PRTDUMP
// EXEC PROC=DTRINFOA
// EXEC INFOANA,SIZE=INFOANA COL. 72
DUMP NAME SYSDUMP.F2.DF200000 ------‘
SELECT DUMP VIEWING
CALL DFHPD410
DATA DEF=0 -. .
DATA TR=2 -. .
DATA TRS=<TERMID=(T080),TRANID=(TR01,TR02)> . .
/*
/&
Figure 148. Using the TRS parameter
. .This suppresses entries from all components.
. .These are full format entries from the Trace Domain only.
. .The TRS selection parameters (similar to the auxiliary trace utility, DFHTU410)
must be enclosed in angled brackets.
Note: For INFOANA, the only valid continuation character in column 72 is the
minus sign.
8.2.7.6 Formatting a transaction dump
The output of the CICS Dump domain is written to DASD or tape (depending on
how you have created and defined the transaction dump data sets to CICS).
The transaction dump utility DFHDU410, which replaces the DFHDUP of CICS 2.3,
does the following:
It writes a summary in the form of an index of all the dumps stored in the
dump data set being processed.
The report is written to a print file assigned by the logical unit SYS009.
It prepares the transaction dump output for printing.
204 VSE/ESA V2R4
It prints the formatted information, or
It scans the dump data set and prints a summary of its contents
The internal trace table entries of a transaction dump are formatted as part of
the dump processing via DFHDU410.
By coding the system initialization parameter TRTRANTY=, you can determine
the contents of the transaction dump trace table. The options are:
TRAN Only transaction-related entries are copied from the internal trace
table into the transaction dump table. (This is the value coded in the
default SIT).
ALL All the entries in the internal trace table are copied.
8.2.7.7 Control options
The control statements for DFHDU410 are submitted via SYSIPT, between a
SELECT and an END statement.
Note the following:
1. If a SCAN statement is present, all other statements are ignored.
2. If no control statements are submitted, all dumps are printed.
3. The SELECT TYPE= statement provides the selection criteria for the dumps
you want to print.
You may select dumps that match one or more of the following arguments:
TRANID
DUMPCODE
DUMPID
TIME
You may use either fully qualified or generic search arguments and a range of
Boolean operands; Figure 149 shows an example.
// JOB DFHDU410
// DLBL DFHDUMP,'CICS410.applid.DFHDMPA',0,SD
// EXTENT SYS001,volser,1,0,nnn,mm
// ASSGN SYS001,DISK,VOL=volser,SHR
// LIBDEF *,SEARCH=(PRD1.BASE)
// EXEC DFHDU410,SIZE=DFHDU410,PARM='TRANSLATE=FOLD'
SELECT TYPE=OR . .
DUMPCODE=(AEY9) . .
TRANID=(PAY*,TR+F) . .
END
/*
/&
Figure 149. Printing a transaction dump
. . This sets the OR Boolean operand for the selection: all dumps that match
any of the DUMPCODE or the TRANID selection criteria will be printed:
. . Dumps with dump code AEY9.
Chapter 8. CICS problem determination 205
. . Dumps of TRANIDs beginning with PAY followed by any characters.
. . Dumps of TRANIDs four characters long, beginning with TR followed by any
non-blank character and ending with character F.
8.2.7.8 Formatting the Auxiliary Trace
The utility program DFHTU410 replaces DFHTUP from CICS 2.3 to extract, format
and print all or selected trace entries from one of the auxiliary trace data sets.
Only the auxiliary trace data sets that were opened for the most recent run of
CICS can be used as input for DFHTU410. You select the trace entries by
submitting the selection parameters via SYSIPT or via PARM parameter of the
EXEC statement.
You can specify that all entries are to be processed (this is the default), or select
specific trace entries with certain attributes, for example, entries that are
associated with:
A specific terminal
A specific trace identifier (component+trace point number)
A specific entry sequence number
A specific transaction identifier
A specific instance of a transaction ID (that is, a task)
A specific kernel task
Exception tracing
8.2.7.9 Control options
Table 23 lists SELECTION control options.
Table 23. SELECTION control options
Option Usage
ALL All entries are to be processed (this is the default)
ENTRY_NUM Sequence number (or range) of entries to be processed
EXCEPTION Exception trace entries ONLY
KE_NUM Kernel task number
TASKID Task identification or task number
TERMID Terminal identification
TIMERG Time period (hhmmss) for which trace entries are to be
printed
TRANID Transaction identification
TYPETR Trace point identification in the format DDnnnn, where DD
is the component ID and nnnn is the trace point
identification
Table 24 lists OUTPUT control options.
Table 24 (Page 1 of 2). OUTPUT control options
Option Usage
ABBREV Abbreviated trace, one line per entry
FULL Fully formatted entries (this is the default)
206 VSE/ESA V2R4
Table 24 (Page 2 of 2). OUTPUT control options
Option Usage
INTERVAL Time interval between entries you want to highlight: each
entry generated in the time interval will be marked with an
asterisk (*) for visual reference
PAGESIZE Number of lines per page (default is 55)
TIMESTAMP To print timestamp instead of sequence number
UPPERCASE Output in uppercase (the default is mixed case)
Figure 150 shows an example of printing the auxiliary trace.
* $$ JOB JNM=PRTAUX,CLASS=x,DISP=D
* $$ LIST CLASS=A
// JOB C410AUXP PRINT AUX TRACE
// DLBL DFHAUXT,'user.label',0,SD
// EXTENT SYS001,volname,1,0,nnnn,nnn
// ASSGN SYS001,DISK,VOL=volname,SHR
// LIBDEF *,SEARCH=PRD1.BASE
// EXEC DFHTU410,SIZE=DFHTU410
ABBREV . .
TASKID=(TCP,J01,02198) . .
TIMERG=(152500-153300) . .
UPPERCASE . .
/*
// EXEC LISTLOG
/*
/&
* $$ EOJ
Figure 150. Printing the auxiliary trace
. . This is the summary trace, one line per entry.
. . These tasks are traced.
. . This shows entries written between 15:25 and 15:33.
. . This means print the report in uppercase.
You would get the same result coding the selection statements this way:
Col. 72
‘
// EXEC DFHTU410,SIZE=DFHTU410,PARM='ABBREV,TASKID=(TCP,J01,02198), C
TIMERG=152500-153320),UPPERCASE'
Chapter 8. CICS problem determination 207
8.3 CICS dumps
The most significant changes in the dump environment under CICS TS for
VSE/ESA R1 are:
CICS dumps via SDUMP macro
New dump-related keywords in the SIT
Dump tables
Extended CEMT commands for dump control
New CICS commands for dump control
Two types of dumps can be produced in the CICS environment:
1. Transaction Dumps
These are written to the CICS transaction data sets DFHDMPA/B.
They are user-requested:
− EXEC CICS DUMP TRANSACTION
− Via a Transaction Dump call from a Global User Exit (GLUE).
− Via the DUMP attribute of the RDO transaction definition.
They are requested or forced by CICS following a transaction abend.
2. CICS Dumps
They are produced via VSE SDUMP/SDUMPX macros.
They are written to the VSE Dump Library (SYSDUMP).
They are user-requested:
− EXEC CICS PERFORM DUMP
− CEMT PERFORM DUMP or SNAP
− SYSTEM_DUMP XPI call from a GLUE
− Requested by global trap or trace exit.
They are requested by NEP.
They are taken by CICS following a system abend.
For both transaction dumps and system dumps, the dumping environment
determines whether the dump is taken or not.
208 VSE/ESA V2R4
The CICS System Dump is produced via VSE SDUMP or SDUMPX macros.
SDUMP is used if the invoking program is running in primary address space
control (ASC) mode. If invoked from a program running in Access Register (AR)
mode, or if data space is to be dumped, then the dump request is issued via
SDUMPX macro.
The output of a CICS system dump comprises:
VSE Supervisor
SVA and other common areas
CICS private storage areas
8.3.1 Processing the CICS dump from a stand-alone tape
The DFHPD410 exit requires some control information from the VSE supervisor
and the system GETVIS to reside in the same dump file as the CICS TS partition.
Important
If the system hangs, you will not be able to run CEMT to take an SDUMP; the
only alternative to get a dump of the CICS region is to take a stand-alone
dump.
On a standalone dump, the VSE supervisor and the SVA are written into a single
file; each active address space eligible for dumping (per force of the
SADUMP=nn option statement) will be written as a separate file into the dump
output device.
If you attempt to process the CICS TS dump file from the standalone output, the
INFOANA job will fail with error messages shown in Figure 151.
SELECT DUMP VIEWING
CALL DFHPD410 DATA DEF=0,KE=1,DS=1,TR=1,FCP=2
-- DFHPD0110 UNABLE TO ACCESS DATA FOR CRADDR
ADDRESS 00000014 -- TESTING FOR DMF DUMP
-- DFHPD0115 CICS/EXCI/DMF JOB NOT FOUND.
** DFHPD0120 CICS DUMP ANALYZER EXIT IS TERMINATING.
Figure 151. Console log output
Chapter 8. CICS problem determination 209
In order to process the CICS dump from a standalone output tape, you must use
the following procedure:
STEP 1: Scan the standalone dump to locate the dump files to be onloaded; see
Figure 152.
r rdr,pausebg
BG 0000 // JOB PAUSEBG
BG 0000 // PAUSE
0 // exec dosvsdmp
BG 0000 4G01D SELECT ONE OF THE FOLLOWING FUNCTIONS:
1 CREATE STAND-ALONE DUMP PROGRAM
2 SCAN DUMP TAPE/DISK
3 PRINT DUMP TAPE/DISK
4 PRINT SDAID TAPE
5 PRINT IPL DIAGNOSTICS
R END DOSVSDMP PROCESSING
0 2
BG 0000 4G04D SPECIFY ADDRESS OF DUMP DEVICE (CUU OR SYSNNN)
BG 0000 0C66D READY
0 00F
Figure 152. Executing DOSVSDMP
Figure 153 shows the resulting output.
PRINTOUT OF VSE DUMP TAPE
DIRECTORY OF VSE DUMP TAPE
DUMP FILE DUMP TYPE NAME DATE DATE DUMPED
--------- --------- -------- -------- --------------------
001 DOES NOT CONTAIN DUMP DATA
002 DOES NOT CONTAIN DUMP DATA
003 SADUMP SUPERVISOR+SVA
004 SADUMP 99/04/20 PMRAS-R
005 SADUMP 99/04/20 PMRAS-00
006 SADUMP CICSTST 99/04/20 F2-PARTITION
007 SADUMP TMONTST 99/04/20 Z1-PARTITION
008 SADUMP VTAM42 99/04/20 F3-PARTITION
009 SADUMP POWSTART 99/04/20 F1-PARTITION
END-OF-DUMP
Figure 153. SYSLST output
210 VSE/ESA V2R4
STEP 2: Onload the supervisor and CICS dumps into SYSDUMP; see Figure 154.
// JOB INFOANAL - ONLOAD TWO DUMP FILES FROM TAPE
// ASSGN SYS009,280
// MTC REW,SYS009
// ASSGN SYS016,DISK,VOL=SYSWK1,SHR . .
// ASSGN SYS017,DISK,VOL=SYSWK1,SHR . .
// EXEC INFOANA,SIZE=300K
* ONLOAD SUPVR+SVA
DUMP NAME SYSDUMP.SUPSVA_DUMP
SELECT DUMP ONLOAD
VOLID TST999 SYS009
FILE 3
RETURN
* ONLOAD CICS DUMP
DUMP NAME SYSDUMP.CICSTS_DUMP
SELECT DUMP ONLOAD
VOLID TST999 SYS009
FILE 6 LAST
RETURN
SELECT END
/*
/&
Figure 154. Onloading the dumps
. .ASSGN for the dump analysis routines data set BLNXTRN
. .ASSGN for the dump management files BLNDMF
Label information for BLNXTRN and BLNDMF is assumed to have been added to
STDLABEL.PROC.
STEP 3: Offload the supervisor and CICS dumps into two different tape volumes;
see Figure 155.
// JOB INFOANAL - OFFLOAD TWO DUMP FILES
// ASSGN SYS009,280 OUTPUT FOR SUPVR+SVA
// MTC REW,SYS009
// MTC WTM,SYS009,10
// MTC REW,SYS009
// ASSGN SYS010,281 OUTPUT FOR CICS DUMP
// MTC REW,SYS010
// MTC WTM,SYS010,10
// MTC REW,SYS010
// ASSGN SYS016,DISK,VOL=SYSWK1,SHR
// ASSGN SYS017,DISK,VOL=SYSWK1,SHR
// EXEC INFOANA,SIZE=300K
DUMP NAME SYSDUMP.SUPSVA_DUMP
SELECT DUMP OFFLOAD
VOLID TST999 SYS009
RETURN
DUMP NAME SYSDUMP.CICSTS_DUMP
SELECT DUMP OFFLOAD
VOLID TST999 SYS010
RETURN
SELECT END
/*
/&
Figure 155. Offloading the dumps
Chapter 8. CICS problem determination 211
STEP 4: Using DFSORT, combine both dumps into a third tape; see Figure 156.
// JOB DFSORT - Merging dumps
// ASSGN SYS001,283 SORT OUTPUT
// MTC REW,SYS001
// MTC WTM,SYS001,10
// MTC REW,SYS001
// ASSGN SYS002,280 SUPERVISOR DUMP
// MTC REW,SYS002
// ASSGN SYS003,281 CICS DUMP
// MTC REW,SYS003
// DLBL SORTWK1,,DA
// EXTENT SYS005,VSEWK2,1,0,22601,800
// ASSGN SYS005,DISK,VOL=SYSWK2,SHR
* COPY FIRST RECORD FROM DUMP TO OUTPUT TAPE
// EXEC SORT,SIZE=64K
OPTION LABEL=(U,U,U),STOPAFT=1 . .
SORT FIELDS=(1,16,BI,A),FILES=1
RECORD TYPE=F,LENGTH=(4112,,4112)
OUTFIL NOTPMK
/*
// MTC REW,SYS001
// MTC FSR,SYS001,1
* SORT BOTH INPUT TAPES
* REPLY "0 DELETE" TO MSG4733D ON SORTWK1
// EXEC SORT,SIZE=64K
OPTION LABEL=(U,U,U)
SORT FIELDS=(1,16,BI,A),FILES=2
RECORD TYPE=F,LENGTH=(4112,,4112)
OMIT COND=(1,4,BI,EQ,X'00000001') . .
OUTFIL OPEN=NORWD,NOTPMK
/*
/&
Figure 156. Building the CICS dump file
. .Copy the first record from the dump file to the output tape.
. .Omit the first record of the input dumps (we only need the one we already
copied in . .).
212 VSE/ESA V2R4
STEP 5: Onload the combined dump into SYSDUMP; see Figure 157.
// JOB INFOANAL - ONLOAD NEW DUMP FROM TAPE
// ASSGN SYS009,283
// MTC REW,SYS009
// ASSGN SYS016,DISK,VOL=SYSWK1,SHR
// ASSGN SYS017,DISK,VOL=SYSWK1,SHR
// EXEC INFOANA,SIZE=300K
DUMP NAME SYSDUMP.CICSTS.NEW_DUMP
SELECT DUMP ONLOAD
VOLID TST999 SYS009
FILE 1
RETURN
SELECT END
/*
/&
Figure 157. Reloading the dump
You can now process CICSTS.NEW_DUMP via DFHPD410.
Note: You should consider increasing the size of your SYSDUMP library to
accommodate the larger dumps of your CICS TS regions; as shipped, it can
barely store more than two consecutive SDUMPs.
8.3.2 Program check and abend information
As part of the first failure data capture mechanism, when a program check or
abend condition is detected in any domain, the following occurs:
An exceptional trace entry is written to the internal trace table.
An error message is issued.
Program check and abend information is generated in the Kernel domain.
1. If you select the output from the Kernel when formatting the dump (KE=n),
the Error Table of the Kernel is printed; see Figure 158.
Each row summarizes and identifies an abend.
.
==KE: KE Domain Error Table Summary
ERR_NUM ERR_TIME KE_NUM ERROR TYPE ERR_CODE MODULE OFFSET
======= ======== ====== ========== ======== ====== ======
0000008F 16:29:25 0021 TRAN_ABEND ---/AEI9 DFHPCP 000004EC
00000090 16:29:25 0021 TRAN_ABEND_PERCOLATE ---/AEI9 DFHEIP 000015D6
00000091 16:33:15 0021 TRAN_ABEND_PERCOLATE ---/AEI9 DFHPCP 000004EC
******************************************************************************
Figure 158. The Kernel Error Table
2. If you select the Kernel output with the the full format option (KE=2 or
KE=3), then the program check and abend information for each of the errors
is also formatted.
This information consists of the following:
Registers and PSW at the time of failure.
A storage report for each task that had a program check or a program
abend during the current CICS session.
Chapter 8. CICS problem determination 213
8.3.3 Default SIT options
The initial dump options are set via SIT keywords described in Table 25.
Table 25. Dump-related keywords
SIT Keyword Usage
DUMP=YES . . Enable the dump domain to take SDUMPs.
DUMPDS=AUTO During CICS initialization, opens the Transaction Dump
data set that was not in use in the previous CICS run.
DUMPSW=NO If the transaction data set is full, operator is notified to
perform the data set switch.
SYDUMAX=999 Sets no limit for system dumps per entry of the system
dump table.
TRDUMAX=999 Sets no limit for transaction dumps per entry of the
transaction dump table.
TRTRANSZ=40 . . Transaction dump trace table size in KB.
TRTRANTY=TRAN Only transaction-related entries should be copied from
the internal trace table to the transaction dump trace
table.
. .The Kernel domain will always take an SDUMP if a fatal failure occurs,
regardless of the DUMP option in the SIT.
. .The storage for the Transaction Dump Trace Table is acquired above the 16
MB line via a VSE GETVIS request issued when the transaction abend is
detected.
8.4 The Dump Table
The DUMP TABLE facility enables the CICS users to control the actions to be
taken when a particular abend code occurs.
There are two dump tables:
TRANSACTION DUMP TABLE Defines the conditions and the options
associated with transaction dump codes.
SYSTEM DUMP TABLE Defines the conditions and the options
associated with CICS system dump codes.
214 VSE/ESA V2R4
8.4.1 Functional overview
If CICS detects a storage violation, the following occurs:
1. An exception trace entry is written.
2. The Message domain issues message DFHSM0102.
3. CICS takes a system dump with a dump code SM0102. (Most of the system
dump codes are the associated message number, once the DFH prefix is
removed.)
4. The Dump Table is searched in order to take the actions prescribed for this
type of abend.
If an entry is not found, CICS generates a temporary entry for this abend
code, assuming default values.
Temporary entries created by CICS are not written to the CICS Global Catalog
and will only remain active for the current CICS run.
You can create a permanent entry in any of the dump tables via a CEMT or EXEC
CICS command. Permanent entries are written to the Global Catalog and are
only reset after a CICS cold start. Each entry defines the actions to be taken by
the Dump domain for a particular dump code.
The dump code for both transaction and system abends can either be
CICS-supplied or user-defined.
To add an entry to the System Dump table, use either of these commands:
CEMT SET SYDUMPCODE
EXEC CICS SET SYSDUMPCODE
For the Transaction Dump table, use either of these commands:
CEMT SET TRDUMPCODE
EXEC CICS SET TRANDUMPCODE
Following are the actions and options you can specify for each of the tables.
8.4.2 Transaction Dump table
Each entry in the Transaction Dump table specifies the following for a transaction
dump code:
1. Whether a transaction dump is to be taken
2. Whether a system dump is to be taken with or without a transaction dump
3. Whether CICS is to be terminated after an occurrence of this dump code
4. The maximum number of times this transaction dump code action should be
taken during the CICS run, or before the counter is reset
Chapter 8. CICS problem determination 215
8.4.3 System Dump table
Each entry in the System Dump table specifies the following for a system dump
code:
1. Whether a system dump is to be taken
2. Whether CICS is to be terminated after an occurrence of this dump code
3. The maximum number of times this system dump code action should be
taken during the CICS run, or before the counter is reset
Note: The CICS Kernel dumps cannot be suppressed.
8.4.4 Dump suppression for ASRA and ASRB abends
With CICS/VSE Version 2, the SIT options PCDUMP= and ABDUMP= (now
obsolete) were used for this purpose. With the TS for VSE/ESA R1, we use the
dump tables and the enhanced CEMT transaction.
When a VSE abend or program check occurs in the AP domain or in a user
application program, CICS issues either message DFHSR0001 or DFHAP0001.
DFHSR0001 is issued (and abend dump code SR0001 is taken) if the failing
application is running in the USER key. However, if the application is running in
the CICS key, then DFHAP0001 is issued and abend dump code AP0001 is taken.
If you want to suppress CICS dumps when provoked by application errors, but
still allow dumps to be taken if the abend is in the CICS code, use CEMT to
suppress system dumps for SR0001 by adding the following entry to the system
dump table:
CEMT SET SYDUMPCODE(SR0001) ADD NOSYSDUMP
If you want to suppress the system dumps for abends and program checks in the
CICS code as well, then also add an entry for AP0001:
CEMT SET SYDUMPCODE(AP0001) ADD NOSYSDUMP
On the other hand, you may wish to take a system dump for the ASRA but not
for the ASRB transaction abends. In that case, use CEMT to create the entries in
the Transaction Dump table:
CEMT SET TRDUMPCODE(ASRA) ADD SYSDUMP MAX(2) . .
CEMT SET TRDUMPCODE(ASRB) ADD NOSYSDUMP
. .CICS will take a system dump for the first two ASRA occurrences only.
To display the options set for all defined dump table entries, use:
CEMT INQ TRDUMPCODE (*) and CEMT INQ SYDUMPCODE (*).
You can modify any of the entries by overtyping the displayed options.
216 VSE/ESA V2R4
8.5 Changes to CSFE and CEDF
The following sections describe changes in CSFE and CEDF.
8.5.1 Changes to the CSFE DEBUG transaction
The syntax of the CSFE DEBUG transaction is changed to match the new SIT
overrides that control storage checking.
With CICS V2, you used the following to specify you wanted storage checking for
the TASK user storage:
CSFE DEBUG,TASKSTG=ON OFF
Now you use:
CSFE DEBUG,CHKSTSK=(ALL CURRENT NONE)
In CICS V2, you specified the following when you wanted storage checking for
the TERMINAL subpool:
CSFE DEBUG,FAQE=...,SUBPOOL=TP
Now you use:
CSFE DEBUG,CHKSTRM=(CURRENT NONE)
8.5.2 CEDF support for remote transactions
The restriction on the use of CEDF for remote transactions has been removed.
In a multiregion operation (MRO) or an intersystem communication (ISC)
environment (APPC only), you can use CEDF (in single session mode only) for
transactions that are defined in the terminal-owning region (TOR) as remote.
CICS automatically notifies the application-owning region (AOR) that the
transaction is to be run in EDF mode.
Note: CICS supports EDF for remote transactions only when all the
communicating regions are using CICS Transaction Server for VSE/ESA Release
1 or later.
Chapter 8. CICS problem determination 217
218 VSE/ESA V2R4
Appendix A. IBM-supplied CSD groups
Table 26 summarizes some CSD groups supplied by IBM.
Table 26 (Page 1 of 2). IBM-supplied RDO groups
Group name To define
CEE Language environment group
DFHAI62 Starter APPC connections group
DFHAKP * Activity keypoint group
DFHAUTO Automatic statistics group
DFHBACK * Dynamic backout group
DFHBMS * Terminal page retrieval group
DFHCLNT CICS client support
DFHCONS * VSE console support group
DFHCOMP1 Compatibility with CICS/VSE 2.3
DFHCOMP2 Required by users of the report controller
DFHEDF * Execution diagnostic group
DFHEXEC Group for general EXEC modules
DFHFE * FE terminal test group
DFHFEPI * Front end programming interface
DFHHARDC * 3270 print support group
DFHINQUI * Group for EXEC CICS special commands
DFHINTER * Command interpreter group
DFHISC * Routing transaction group
DFHISCT Intersystem communication group
DFHJRNL * Journal bootstrap group
DFHMASTT Old master terminal group
DFHMISC * Miscellaneous group
DFHMISC3 Miscellaneous group
DFHMSWIT * Message switching group
DFHNUM Numeric sign off group
DFHOPCLS * Dynamic open and close group
DFHOPER * EXEC master terminal group
DFHPLI PL/I support group
DFHPGAIP * Program manager autoinstall group
DFHRCF Reporter controller group
DFHRMI * Resource manager interface group
DFHRSEND * VTAM resend program group
DFHRSPLG Response logging group
DFHSIGN * CICS sign on group
DFHSPI * Resource definition online group
DFHSTAND * Standard entries group
DFHTCL * IBM-supplied TRANCLASS
DFHTERM * Supplied model TERMINAL definitions
DFHTYPE * Supplied TYPETERM definitions
DFHTIME Time of day adjustment group
© Copyright IBM Corp. 1999 219
Table 26 (Page 2 of 2). IBM-supplied RDO groups
Group name To define
DFHVTAM * VTAM group
DFHVTAMP * VTAM 3270 print group
TCPIP TCP/IP environment group
VSEAI62 Sample DFHZATDY
VSETERM Supplied VSE TERMINAL definitions for
autoinstall
VSETERM1 Supplied VSE TERMINAL definitions during
installation
VSETYPE Supplied VSE TYPETERM definitions for
autoinstall
VSESPG Supplied VSE entries by DFHPPTSP and
DFHPCTSP
Note: * These are DFHLIST resource definitions.
220 VSE/ESA V2R4
Appendix B. CICS TS Statistics output examples
This appendix provides an example of output from a sample statistics program,
as well as examples of unsolicited statistics.
B.1 Sample Statistics Program output
Figure 159 shows some of the output produced by the sample statistics program
from a CICS TS partition.
Applid TSRES5 Sysid CIC5 Jobname CICSTS5 Date 03/29/99 Time 07:49:54 CICS 01.01.00 PAGE 1
____________________________________________________________________________________________________________________________________
System Status
_____________
VSE Release . . . . . . : VSE/AF6.4.0
CICS Startup. . . . . . : COLD
CICS Status . . . . . . : ACTIVE
Storage Protection. . . : INACTIVE
Reentrant Programs. . . : PROTECT
Monitoring
__________
Monitoring . . . . . : OFF
Exception Class. . . : OFF
Performance Class. . : OFF
Exception Class Records . . . . . : 0
Exception Records Suppressed. . . : 0
Performance Class Records . . . . : 0
Performance Records Suppressed. . : 0
DMF Records . . . . . . . . . . . : 0
DMF Errors. . . . . . . . . . . . : 0
Statistics
__________
Statistics End-of-Day Time . . : 00:00:00
Statistics Interval. . . . . . : 03:00:00
Next Statistics Collection . . : 00:00:00
Statistics Recording . . . . . : OFF
Transaction Manager
___________________
Total Accumulated transactions so far. . : 59
Accumulated transactions (since reset) . : 59
Maximum transactions allowed (MXT) . . . : 50
Times at MXT . . . . . . . . . . . . . . : 0
Current Active User transactions . . . . : 3
Peak Active User transactions. . . . . . : 7
Total Active User transactions . . . . . : 39
Current Running transactions . . . . . . : 1
Current Dispatchable transactions. . . . : 0
Current Suspended transactions . . . . . : 2
Current System transactions. . . . . . . : 0
Transactions Delayed by MXT. . . . . . . : 0
Total MXT queueing time. . . . . . . . . : 00:00:00.00000
Average MXT queueing time. . . . . . . . : 00:00:00.00000
Current Queued User transactions . . . . : 0
Total Queueing time for current queued . : 00:00:00.00000
Average Queueing time for current queued : 00:00:00.00000
Dispatcher
__________
Dispatcher start time. . . : 07:33:30.11166
Peak tasks . . . . . . . . : 22
Current tasks. . . . . . . : 11
Current ICV time . . . . . : 1,000ms
Current ICVR time. . . . . : 20,000ms
Current ICVTSD time. . . . : 200ms
Current PRTYAGING time . . : 5,000ms
Number of active CICS TCBs : 2
TCB TCB TCB Op. System Op. System TCB TCB DS TCB
Name Status Start Time Waits Wait Time Dispatch Time CPU Time CPU Time
______________________________________________________________________________________________________________
QR_SUBD Active 07:33:30.11166 2,172 00:16:14.31723 00:00:09.89239 00:00:02.56000 00:00:00.00000
RO_SUBD Active 07:33:30.61046 62 00:16:03.68154 00:00:20.02948 00:00:00.51200 00:00:00.00000
______________________________________________________________________________________________________________
Totals 00:00:29.92188 00:00:03.07200 00:00:00.00000
Figure 159 (Part 1 of 7). STAT transaction output
© Copyright IBM Corp. 1999 221
Applid TSRES5 Sysid CIC5 Jobname CICSTS5 Date 03/29/99 Time 07:49:54 CICS 01.01.00 PAGE 3
____________________________________________________________________________________________________________________________________
Partition size established from ALLOC parameter . . : 30,463K
Storage BELOW 16MB
__________________
Partition GETVIS area size under 16 Mb . . . . . . : 12,028K
Partition GETVIS used area below 16 Mb . . . . . : 5,652K
Partition GETVIS free area below 16 Mb . . . . . : 6,376K
Partition GETVIS maximum used below 16 Mb . . . . : 12,028K
Partition GETVIS largest free area below 16 Mb . : 6,376K
__________________________________________________________________
Current DSA Limit . . . . . . : 5,120K
Current Allocation for DSAs . : 2,048K
Peak Allocation for DSAs. . . : 2,048K
CDSA UDSA SDSA RDSA Totals
___________________________________________________________________________________
Current DSA Size. . . . . . . : 512K 256K 512K 768K 2,048K
Current DSA Used. . . . . . . : 296K 4K 296K 608K 1,204K
Current DSA Used as % of DSA. : 57% 1% 57% 79% 58% of DSA Size
* Peak DSA Used . . . . . . . . : 356K 40K 296K 608K
Peak DSA Size . . . . . . . . : 512K 256K 512K 768K
Cushion Size. . . . . . . . . : 64K 64K 64K 64K
Free Storage (inc. Cushion) . : 216K 252K 216K 160K
* Peak Free Storage . . . . . . : 316K 256K 260K 564K
* Lowest Free Storage . . . . . : 156K 216K 216K 160K
Largest Free Area . . . . . . : 168K 248K 212K 144K
Largest Free Area as % of DSA : 32% 96% 41% 18%
Largest Free/Free Storage . . : 0.77 0.98 0.98 0.90
Current number of extents . . : 2 1 2 2 7
Number of extents added . . . : 2 1 2 2
Number of extents released. . : 0 0 0 0
Getmain Requests. . . . . . . : 426 474 75 17
Freemain Requests . . . . . . : 310 472 3 0
Current number of Subpools. . : 32 9 6 4 51
Add Subpool Requests. . . . . : 84 61 6 4
Delete Subpool Requests . . . : 52 52 0 0
Times no storage returned . . : 0 0 0 0
Times request suspended . . . : 0 0 0 0
Current requests suspended. . : 0 0 0 0
Peak requests suspended . . . : 0 0 0 0
Requests purged while waiting : 0 0 0 0
Times Cushion released. . . . : 0 0 0 0
Times Short-On-Storage. . . . : 0 0 0 0
Total time Short-On-Storage . : 00:00:00.00000 00:00:00.00000 00:00:00.00000 00:00:00.00000
Average Short-On-Storage time : 00:00:00.00000 00:00:00.00000 00:00:00.00000 00:00:00.00000
Storage Violations. . . . . . : 0 0 0 0 0
Access. . . . . . . . . . . . : CICS CICS CICS READONLY
'*' indicates values reset on last DSA Size change
Figure 159 (Part 2 of 7). STAT transaction output
222 VSE/ESA V2R4
Applid TSRES5 Sysid CIC5 Jobname CICSTS5 Date 03/29/99 Time 07:49:54 CICS 01.01.00 PAGE 4
____________________________________________________________________________________________________________________________________
Storage ABOVE 16MB
__________________
Partition GETVIS area size above 16 Mb . . . . . . : 18,428K
Partition GETVIS used area above 16 Mb . . . . . : 16,932K
Partition GETVIS free area above 16Mb . . . . . . : 1,496K
Partition GETVIS maximum used above 16 Mb . . . . : 18,000K
Partition GETVIS largest free area above 16 Mb . : 7,400K
__________________________________________________________________
Current EDSA Limit. . . . . . : 14,336K
CICS Trace table size . . . . . . . . . . . . . . . : 80K
Current Allocation for EDSAs. : 11,264K
Peak Allocation for EDSAs . . : 11,264K
ECDSA EUDSA ESDSA ERDSA Totals
___________________________________________________________________________________
Current DSA Size. . . . . . . : 3,072K 1,024K 1,024K 6,144K 11,264K
Current DSA Used. . . . . . . : 2,284K 64K 100K 4,784K 7,232K
Current DSA Used as % of DSA. : 74% 6% 9% 77% 64% of EDSA Size
* Peak DSA Used . . . . . . . . : 2,308K 64K 100K 5,056K
Peak DSA Size . . . . . . . . : 3,072K 1,024K 1,024K 6,144K
Cushion Size. . . . . . . . . : 128K 0K 128K 256K
Free Storage (inc. Cushion) . : 788K 960K 924K 1,360K
* Peak Free Storage . . . . . . : 1,024K 1,024K 1,024K 3,000K
* Lowest Free Storage . . . . . : 764K 960K 924K 1,088K
Largest Free Area . . . . . . : 784K 960K 924K 872K
Largest Free Area as % of DSA : 25% 93% 90% 14%
Largest Free/Free Storage . . : 0.99 1.00 1.00 0.64
Current number of extents . . : 3 1 1 5 10
Number of extents added . . . : 3 1 1 5
Number of extents released. . : 0 0 0 0
Getmain Requests. . . . . . . : 14,922 33 3 245
Freemain Requests . . . . . . : 9,306 29 0 20
Current number of Subpools. . : 131 9 3 4 147
Add Subpool Requests. . . . . : 183 61 3 4
Delete Subpool Requests . . . : 52 52 0 0
Times no storage returned . . : 0 0 0 0
Times request suspended . . . : 0 0 1 0
Current requests suspended. . : 0 0 0 0
Peak requests suspended . . . : 0 0 1 0
Requests purged while waiting : 0 0 1 0
Times Cushion released. . . . : 0 0 0 0
Times Short-On-Storage. . . . : 0 0 1 0
Total time Short-On-Storage . : 00:00:00.00000 00:00:00.00000 00:00:10.48411 00:00:00.00000
Average Short-On-Storage time : 00:00:00.00000 00:00:00.00000 00:00:10.48411 00:00:00.00000
Storage Violations. . . . . . : 0 0 0 0 0
Access. . . . . . . . . . . . : CICS CICS CICS READONLY
'*' indicates values reset on last DSA Size change
Figure 159 (Part 3 of 7). STAT transaction output
Appendix B. CICS TS Statistics output examples 223
Applid TSRES5 Sysid CIC5 Jobname CICSTS5 Date 03/29/99 Time 07:49:54 CICS 01.01.00 PAGE 5
____________________________________________________________________________________________________________________________________
Loader
______
Library Load requests. . . . . . . . . . . . . : 325 Total Program Uses . . . . . . . . . . . . . . : 3,743
Total Library Load time. . . . . . . . . . . . : 00:00:11.29817 Program Use to Load Ratio. . . . . . . . . . . : 11.51
Average Library Load time. . . . . . . . . . . : 00:00:00.03475
Library Load requests that waited. . . . . . . : 2
Total Library Load request wait time . . . . . : 00:00:00.05811
Average Library Load request wait time . . . . : 00:00:00.02905
Current Waiting Library Load requests. . . . . : 0
Peak Waiting Library Load requests . . . . . . : 1
Times at Peak. . . . . . . . . . . . . . . . . : 2 Average Not-In-Use program size. . . . . . . . : 8K
CDSA ECDSA
____ _____
Programs Removed by compression. . . . . . . . : 0 Programs Removed by compression. . . . . . . . : 0
Time on the Not-In-Use Queue . . . . . . . . . : 00:00:00.00000 Time on the Not-In-Use Queue . . . . . . . . . : 00:00:00.00000
Average Time on the Not-In-Use Queue . . . . . : 00:00:00.00000 Average Time on the Not-In-Use Queue . . . . . : 00:00:00.00000
Programs Reclaimed from the Not-In-Use Queue . : 21 Programs Reclaimed from the Not-In-Use Queue . : 0
Programs Loaded - now on the Not-In-Use Queue. : 7 Programs Loaded - now on the Not-In-Use Queue. : 3
SDSA ESDSA
____ _____
Programs Removed by compression. . . . . . . . : 0 Programs Removed by compression. . . . . . . . : 0
Time on the Not-In-Use Queue . . . . . . . . . : 00:00:00.00000 Time on the Not-In-Use Queue . . . . . . . . . : 00:00:00.00000
Average Time on the Not-In-Use Queue . . . . . : 00:00:00.00000 Average Time on the Not-In-Use Queue . . . . . : 00:00:00.00000
Programs Reclaimed from the Not-In-Use Queue . : 111 Programs Reclaimed from the Not-In-Use Queue . : 33
Programs Loaded - now on the Not-In-Use Queue. : 20 Programs Loaded - now on the Not-In-Use Queue. : 2
RDSA ERDSA
____ _____
Programs Removed by compression. . . . . . . . : 0 Programs Removed by compression. . . . . . . . : 10
Time on the Not-In-Use Queue . . . . . . . . . : 00:00:00.00000 Time on the Not-In-Use Queue . . . . . . . . . : 01:51:28.85590
Average Time on the Not-In-Use Queue . . . . . : 00:00:00.00000 Average Time on the Not-In-Use Queue . . . . . : 00:11:08.88558
Programs Reclaimed from the Not-In-Use Queue . : 0 Programs Reclaimed from the Not-In-Use Queue . : 2,999
Programs Loaded - now on the Not-In-Use Queue. : 3 Programs Loaded - now on the Not-In-Use Queue. : 9
Program Storage
_______________
Nucleus Program Storage (CDSA) . . . . . . . . : 40K Nucleus Program Storage (ECDSA). . . . . . . . : 8K
Program Storage (SDSA) . . . . . . . . . . . . : 196K Program Storage (ESDSA). . . . . . . . . . . . : 100K
Resident Program Storage (SDSA). . . . . . . . : 0K Resident Program Storage (ESDSA) . . . . . . . : 0K
Read-Only Nucleus Program Storage (RDSA) . . . : 16K Read-Only Nucleus Program Storage (ERDSA). . . : 772K
Read-Only Program Storage (RDSA) . . . . . . . : 112K Read-Only Program Storage (ERDSA). . . . . . . : 2,060K
Read-Only Resident Program Storage (RDSA). . . : 292K Read-Only Resident Program Storage (ERDSA) . . : 0K
CDSA used by Not-In-Use programs. : 34K 6.68% of CDSA ECDSA used by Not-In-Use programs : 5K 0.15% of ECDSA
SDSA used by Not-In-Use programs. : 161K 31.35% of SDSA ESDSA used by Not-In-Use programs : 2K 0.15% of ESDSA
RDSA used by Not-In-Use programs. : 8K 1.10% of RDSA ERDSA used by Not-In-Use programs : 171K 2.78% of ERDSA
Transactions
____________
Tran Tran Program Task Data Attach Restart Dynamic - Counts Remote
id Class Name Dynamic Location/Key Count Count Local Remote Starts
___________________________________________________________________________________________________
iccf DTSICCF Static Below/CICS 0 0 0 0 0
.
.
STAT DFH0STAT Static Any/USER 2 0 0 0 0
USER IESDUSR Static Below/USER 0 0 0 0 0
2RPS DFH0CRPS Static Any/USER 0 0 0 0 0
___________________________________________________________________________________________________
Totals 59 0 0 0 0
____________________________________________________________________________________________________________________________________
Transaction Totals
__________________
Task Data Transaction Attach
Location/Key Count Count
______________________________________
Below/CICS 44 23
Any/CICS 43 8
Below/USER 104 26
Any/USER 6 2
______________________________________
Totals 197 59
Figure 159 (Part 4 of 7). STAT transaction output
224 VSE/ESA V2R4
Applid TSRES5 Sysid CIC5 Jobname CICSTS5 Date 03/29/99 Time 07:49:54 CICS 01.01.00 PAGE 11
____________________________________________________________________________________________________________________________________
Programs
________
Program Data Exec Times Total Average Times Times Program Program
Name Loc Key Times Used Fetched Fetch Time Fetch Time Newcopy Removed Size Location
__________________________________________________________________________________________________________________________________
CEECCICS Below USER 1 1 00:00:00.43350 00:00:00.43350 0 0 295,688 RDSA
CEECDATX Below USER 0 0 0 None
.
.
DFH$STED Any CICS 0 0 0 None
DFHACP Any CICS 2 1 00:00:00.02240 00:00:00.02240 0 0 9,578 ECDSA
DFHAKP Below CICS 0 0 0 None
DFHAMP Any CICS 2 2 00:00:00.33883 00:00:00.16940 0 1 121,952 None
DFHAPATT Any CICS 16 1 00:00:00.02067 00:00:00.02067 0 0 722 ERDSA
.
.
IESSCRH Below USER 31 1 00:00:00.02862 00:00:00.02862 0 0 2,258 SDSA
IESSCRIO Below USER 31 1 00:00:00.02963 00:00:00.02963 0 0 11,834 SDSA
IESSMSG Below USER 0 0 0 None
IESSVL Below USER 26 1 00:00:00.01622 00:00:00.01622 0 0 680 SDSA
IESTUP Below USER 0 0 0 None
.
__________________________________________________________________________________________________________________________________
Totals 3,515 97 0 9
Applid TSRES5 Sysid CIC5 Jobname CICSTS5 Date 03/29/99 Time 07:49:54 CICS 01.01.00 PAGE 29
____________________________________________________________________________________________________________________________________
Program Totals
______________
Programs. . . . . . . : 876
Assembler . . . . . : 863
C . . . . . . . . . : 3
COBOL . . . . . . . : 5
LE/VSE. . . . . . . : 0
PL1 . . . . . . . . : 4
Other . . . . . . . : 1
Maps. . . . . . . . . : 68
Partitionsets . . . . : 1
___________________________________
Total . . . . . . . . : 945
CDSA Programs . . . . : 9
SDSA Programs . . . . : 24
RDSA Programs . . . . : 6
ECDSA Programs. . . . : 5
ESDSA Programs. . . . : 3
ERDSA Programs. . . . : 33
SVA Programs. . . . . : 0
ESva Programs . . . . : 0
Unused Programs . . . : 10
Not Located Programs. : 855
___________________________________
Total . . . . . . . . : 945
Figure 159 (Part 5 of 7). STAT transaction output
Appendix B. CICS TS Statistics output examples 225
Applid TSRES5 Sysid CIC5 Jobname CICSTS5 Date 03/29/99 Time 07:49:54 CICS 01.01.00 PAGE 30
____________________________________________________________________________________________________________________________________
Temporary Storage
_________________
Put/Putq main storage requests . . . . . : 3
Get/Getq main storage requests . . . . . : 1
Peak storage used for TS Main. . . . . . : 1K
Current storage used for TS Main . . . . : 0K
Put/Putq auxiliary storage requests. . . : 81
Get/Getq auxiliary storage requests. . . : 87
Times temporary storage queue created. . : 11
Peak temporary storage queues in use . . : 11
Current temporary storage queues in use. : 10
Items in longest queue . . . . . . . . . : 15
Queue extension threshold. . . . . . . . : 20
Queue extensions created . . . . . . . . : 0
Control interval size. . . . . . . . . . : 4,096
Control intervals in the DFHTEMP dataset : 108
Peak control intervals used. . . . . . . : 20
Current control intervals in use . . . . : 17
Available bytes per control interval . . : 4,032
Segments per control interval. . . . . . : 63
Bytes per segment. . . . . . . . . . . . : 64
Writes bigger than control interval size : 0
Largest record length written. . . . . . : 4,008
Times auxiliary storage exhausted. . . . : 0
Number Temporary storage compressions. . : 6
Temporary storage strings. . . . . . . . : 8
Peak Temporary storage strings in use. . : 1
Temporary storage string waits . . . . . : 0
Peak users waiting on string . . . . . . : 0
Current users waiting on string. . . . . : 0
Temporary storage buffers. . . . . . . . : 8
Temporary storage buffer waits . . . . . : 0
Peak users waiting on buffer . . . . . . : 0
Current users waiting on buffer. . . . . : 0
Temporary storage buffer reads . . . . . : 16
Temporary storage buffer writes. . . . . : 27
Forced buffer writes for recovery. . . . : 0
Format writes. . . . . . . . . . . . . . : 0
I/O errors on the DFHTEMP dataset. . . . : 0
Applid TSRES5 Sysid CIC5 Jobname CICSTS5 Date 03/29/99 Time 07:49:54 CICS 01.01.00 PAGE 31
____________________________________________________________________________________________________________________________________
Transient Data
______________
Transient data reads . . . . . . . . . . : 27
Transient data writes. . . . . . . . . . : 27
Transient data formatting writes . . . . : 0
Control interval size. . . . . . . . . . : 4,096
Control intervals in the DFHNTRA dataset : 108
Peak control intervals used. . . . . . . : 31
Times NOSPACE on DFHNTRA occurred. . . . : 0
Transient data strings . . . . . . . . . : 3
Times Transient data string in use . . . : 54
Peak Transient data strings in use . . . : 1
Times string wait occurred . . . . . . . : 0
Peak users waiting on string . . . . . . : 0
Transient data buffers . . . . . . . . . : 3
Times Transient data buffer in use . . . : 2,615
Peak Transient data buffers in use . . . : 1
Peak buffers containing valid data . . . : 3
Times buffer wait occurred . . . . . . . : 0
Peak users waiting on buffer . . . . . . : 0
I/O errors on the DFHNTRA dataset. . . . : 0
Figure 159 (Part 6 of 7). STAT transaction output
226 VSE/ESA V2R4
Applid TSRES5 Sysid CIC5 Jobname CICSTS5 Date 03/29/99 Time 07:49:54 CICS 01.01.00 PAGE 32
____________________________________________________________________________________________________________________________________
LSR Pools
_________
Pool Number : 1 Time Created : 07:33:54.69730
_________________ _______________________________
Maximum key length . . . . . . . : 22
Total number of strings . . . . : 4
Peak concurrently active strings : 1
Total requests waited for string : 0
Peak requests waited for string. : 0
Buffer Totals
_____________
Data Buffers . . . . . . . . . . : 16 Index Buffers. . . . . . . . . . : 0
Successful look asides . . . . : 14 Successful look asides . . . . : 0
Buffer reads . . . . . . . . . : 12 Buffer reads . . . . . . . . . : 0
User initiated writes. . . . . : 0 User initiated writes. . . . . : 0
Non-user initiated writes. . . : 0 Non-user initiated writes. . . : 0
Data and Index Buffer Statistics
________________________________
Look User
Size Buffers Asides Reads Writes Writes
______________________________________________________________
512 8 11 6 0 0
4096 8 3 6 0 0
Files
_____
Access LSR Str Waits Read Get Update Browse Add Update Delete Data Index
Filename Method Type Pool Max Total Requests Requests Requests Requests Requests Requests EXCPs EXCPs
__________________________________________________________________________________________________________________________________
DFHCSD VSAM 1 0 0 0 0 0 0 0 0 0 0
IESCNTL VSAM KSDS 0 0 0 15 0 0 0 0 0 15 16
IESPRB VSAM KSDS 0 0 0 204 6 0 0 4 0 209 4
IESROUT VSAM KSDS 1 0 0 0 0 0 0 0 0 1 1
IESTRFL VSAM KSDS 1 0 0 8 0 0 0 0 0 5 5
__________________________________________________________________________________________________________________________________
Totals 227 6 0 0 4 0 230 26
Applid TSRES5 Sysid CIC5 Jobname CICSTS5 Date 03/29/99 Time 07:49:54 CICS 01.01.00 PAGE 34
____________________________________________________________________________________________________________________________________
Data Tables - Requests
______________________
Data Max Successful Records Adds via Adds via Adds Rewrite Delete Read
Filename Table Type Num recs Reads Not Found Read API Rejected Requests Requests Retries
__________________________________________________________________________________________________________________________________
Data Tables - Storage
_____________________
<------- Total ------> <------ Entries -----> <------- Index ------> <------- Data ------->
Current Peak Storage Storage Storage Storage Storage Storage Storage Storage
Filename Type Records Records Allocated In-Use Allocated In-Use Allocated In-Use Allocated In-Use
__________________________________________________________________________________________________________________________________
Figure 159 (Part 7 of 7). STAT transaction output
B.2 Sample unsolicited statistics
Figure 160 on page 228 and Figure 161 on page 228 show examples of
unsolicited statistics printed from DMF datasets for our CICS TS partition.
Appendix B. CICS TS Statistics output examples 227
Unsolicited Statistics Report Collection Date-Time 03/30/1999-14:51:23 Last Reset 12:00:00 Applid DBDCCICS Jobname CICSICCF
___________________________________________________________________________________________________________________________________
*******************************************
*********************************************
***********************************************
**** ****
**** UNSOLICITED STATISTICS ****
______________________
**** ****
***********************************************
*********************************************
*******************************************
Unsolicited Statistics Report Collection Date-Time 03/30/1999-14:51:23
____________________________________________________________________________
AUTOINSTALLED TERMINALS
_______________________
Terminal identifier : B001
Input messages : 2
Output messages : 3
Transactions : 3
Transmission errors : 0
Transaction errors : 0
Luname : D08201
Logon Time : 14:47:09.7798
Logoff Time : 14:51:23.3347
Logon Duration : 00:04:13.5549
Figure 160. Unsolicited statistics - Autoinstall terminal
Unsolicited Statistics Report Collection Date-Time 03/30/1999-14:58:31 Last Reset 12:00:00 Applid DBDCCICS Jobname CICSICCF
_______________________________________________________________________________________________________________________
FILES - Resource Information
____________________________
File Dataset Name Dataset DT Time Time Remote Remote Lsrpool
Name Base Dataset Name (If Applicable) Type Indicator Opened Closed Name Sysid ID
____________________________________________________________________________________________________________________
DFHCSD CICS.CSD K 14:36:11 14:58:31 01
____________________________________________________________________________________________________________________
Unsolicited Statistics Report Collection Date-Time 03/30/1999-14:58:31 Last Reset 12:00:00
________________________________________________________________________________________________
FILES - Requests Information
____________________________
File Get Get Upd Browse Update Add Delete VSAM EXCP Requests
Name Requests Requests Requests Requests Requests Requests Data Index
_________________________________________________________________________________
DFHCSD 18 11 389 3 7 4 41 8
_________________________________________________________________________________
*TOTALS* 18 11 389 3 7 4 41 8
Figure 161. Unsolicited file statistics
228 VSE/ESA V2R4
Appendix C. Special Notices
This publication is intended to assist customers and IBM technical personnel in
the migration of a VSE system to VSE/ESA V2R4 and CICS TS 1.1. The
information in this publication is not intended as the specification of any
programming interfaces that are provided by VSE/ESA V2R4 and CICS TS 1.1.
See the PUBLICATIONS section of the IBM Programming Announcement for
VSE/ESA V2R4 and CICS TS for more information about what publications are
considered to be product documentation.
References in this publication to IBM products, programs or services do not
imply that IBM intends to make these available in all countries in which IBM
operates. Any reference to an IBM product, program, or service is not intended
to state or imply that only IBM's product, program, or service may be used. Any
functionally equivalent program that does not infringe any of IBM's intellectual
property rights may be used instead of the IBM product, program or service.
Information in this book was developed in conjunction with use of the equipment
specified, and is limited in application to those specific hardware and software
products and levels.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to the IBM Director of
Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact IBM Corporation, Dept.
600A, Mail Drop 1329, Somers, NY 10589 USA.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The information contained in this document has not been submitted to any
formal IBM test and is distributed AS IS. The use of this information or the
implementation of any of these techniques is a customer responsibility and
depends on the customer's ability to evaluate and integrate them into the
customer's operational environment. While each item may have been reviewed
by IBM for accuracy in a specific situation, there is no guarantee that the same
or similar results will be obtained elsewhere. Customers attempting to adapt
these techniques to their own environments do so at their own risk.
Any pointers in this publication to external Web sites are provided for
convenience only and do not in any manner serve as an endorsement of these
Web sites.
© Copyright IBM Corp. 1999 229
The following terms are trademarks of the International Business Machines
Corporation in the United States and/or other countries:
CICS IBM
IMS MQSeries
S/390 System/390
VM/ESA VSE/ESA
VTAM ACF/VTAM
APPN Advanced Peer-to-Peer Networking
DB2 Language Environment
OS/390 RACF
The following terms are trademarks of other companies:
C-bus is a trademark of Corollary, Inc.
Java and HotJava are trademarks of Sun Microsystems, Incorporated.
Microsoft, Windows, Windows NT, and the Windows 95 logo are trademarks
or registered trademarks of Microsoft Corporation.
PC Direct is a trademark of Ziff Communications Company and is used
by IBM Corporation under license.
Pentium, MMX, ProShare, LANDesk, and ActionMedia are trademarks or
registered trademarks of Intel Corporation in the U.S. and other
countries.
UNIX is a registered trademark in the United States and other
countries licensed exclusively through X/Open Company Limited.
SET and the SET logo are trademarks owned by SET Secure Electronic
Transaction LLC.
Other company, product, and service names may be trademarks or
service marks of others.
230 VSE/ESA V2R4
Appendix D. Related Publications
The publications listed in this section are considered particularly suitable for a
more detailed discussion of the topics covered in this redbook.
D.1 International Technical Support Organization Publications
For information on ordering these ITSO publications see “How to Get ITSO
Redbooks” on page 233.
External Presentation Interface (EPI): New VSE/ESA Support for CICS Clients ,
SG24-2038
CICS/VSE in a Networking World: Connecting CICS Servers and Clients ,
SG24-2047
Running CICS Transaction Through the Web: The CICS Internet Gateway to
VSE/ESA, SG24-4799
D.2 Redbooks on CD-ROMs
Redbooks are also available on the following CD-ROMs. Click the CD-ROMs
button at http://www.redbooks.ibm.com/ for information about all the CD-ROMs
offered, updates and formats.
CD-ROM Title Collection Kit
Number
System/390 Redbooks Collection SK2T-2177
Networking and Systems Management Redbooks Collection SK2T-6022
Transaction Processing and Data Management Redbooks Collection SK2T-8038
Lotus Redbooks Collection SK2T-8039
Tivoli Redbooks Collection SK2T-8044
AS/400 Redbooks Collection SK2T-2849
Netfinity Hardware and Software Redbooks Collection SK2T-8046
RS/6000 Redbooks Collection (BkMgr Format) SK2T-8040
RS/6000 Redbooks Collection (PDF Format) SK2T-8043
Application Development Redbooks Collection SK2T-8037
D.3 Other Publications
These publications are also relevant as further information sources:
CICS Transaction Server for VSE/ESA 1.1
Release Guide , GC33-1645
Migration Guide , GC33-1646
System Definition Guide , SC33-1651
Customization Guide , SC33-1652
Resource Definition Guide , SC33-1653
Operations and Utilities Guide , SC33-1654
Application Programming Reference, SC33-1658
Application Migration Aid Guide , SC33-1943
Performance Guide , SC33-1667
© Copyright IBM Corp. 1999 231
Shared Data Tables Guide , SC33-1668
Security Guide , SC33-1942
Report Controller Planning Guide , SC33-1941
Trace Entries Handbook , SX33-6108
VSE/ESA 2.4
Planning , SC33-6703
Installation , SC33-6704
Administration , SC33-6705
Operation , SC33-6706
System Control Statements , SC33-6713
System Utilities , SC33-6717
IBM Data/Language/I DOS/VS and VSE
Release Guide Version 1 Release 10 and 11, SC33-6211
IBM VSE/Access Control-Logging and Reporting 1.2.1
Program Reference and Operation , SH12-5336
DB2 Server for VSE Version 6 Release 1
Installation , GC09-2656
System Administration , SC09-2658
Other related publications:
VSE/ESA Software Newsletter , G225-4508-17
VSE/ESA Software Newsletter , G225-4508-18
VSE/ESA Home Page, on the World Wide Web at
http://www.s390.ibm.com/vse/
CICS Transaction Server for VSE/ESA Performance Considerations on the
VSE Home Page on the World Wide Web at http://www.s390.ibm.com/vse/
VSE/ESA Version 2 Performance Considerations on the VSE Home Page on
the World Wide Web at http://www.s390.ibm.com/vse/
Softcopy Publications
IBM Online Library VSE Collection , SK2T-0060
232 VSE/ESA V2R4
How to Get ITSO Redbooks
This section explains how both customers and IBM employees can find out about ITSO redbooks, redpieces, and
CD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided.
Redbooks Web Site http://www.redbooks.ibm.com/
Search for, view, download, or order hardcopy/CD-ROMs redbooks from the redbooks Web site. Also read
redpieces and download additional materials (code samples or diskette/CD-ROM images) from this redbooks
site.
Redpieces are redbooks in progress; not all redbooks become redpieces and sometimes just a few chapters
will be published this way. The intent is to get the information out much quicker than the formal publishing
process allows.
E-mail Orders
Send orders by e-mail including information from the redbook fax order form to:
In United States: e-mail address: usib6fpl@ibmmail.com
Outside North America: Contact information is in the "How to Order" section at this site:
http://www.elink.ibmlink.ibm.com/pbl/pbl/
Telephone Orders
United States (toll free) 1-800-879-2755
Canada (toll free) 1-800-IBM-4YOU
Outside North America Country coordinator phone number is in the "How to Order" section at this site:
http://www.elink.ibmlink.ibm.com/pbl/pbl/
Fax Orders
United States (toll free) 1-800-445-9269
Canada 1-403-267-4455
Outside North America Fax phone number is in the "How to Order" section at this site:
http://www.elink.ibmlink.ibm.com/pbl/pbl/
This information was current at the time of publication, but is continually subject to change. The latest information
may be found at the redbooks Web site.
IBM Intranet for Employees
IBM employees may register for information on workshops, residencies, and redbooks by accessing the IBM
Intranet Web site at http://w3.itso.ibm.com/ and clicking the ITSO Mailing List button. Look in the Materials
repository for workshops, presentations, papers, and Web pages developed and written by the ITSO technical
professionals; click the Additional Materials button. Employees may access MyNews at http://w3.ibm.com/ for
redbook, residency, and workshop announcements.
© Copyright IBM Corp. 1999 233
IBM Redbook Fax Order Form
Please send me the following:
Title Order Number Quantity
First name Last name
Company
Address
City Postal code Country
Telephone number Telefax number VAT number
Invoice to customer number
Credit card number
Credit card expiration date Card issued to Signature
We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card not
available in all countries. Signature mandatory for credit card payment.
234 VSE/ESA V2R4
List of Abbreviations
ABEND abnormal end CPIC Common Programming
Interface for Communications
ACB access control block
CSA Common Storage Area
ACF/VTAM Advanced Communications
Facility/Virtual CSD CICS System Definition
Telecommunications Access
DASD Direct Access Storage Device
Method
DB2 DataBase 2
ACLR Access Control Logging and
Reporting DCT Destination Control Table
ALT application load table DD Directory Manager Domain
AMA Application Migration Aid DITTO Data Interfile Transfer,
Testing & Operations utility
AMODE addressing mode
DL/I Data Language 1
AOR application-owning region
DLBL Disk LabeL
AP Application Domain
DM Domain Manager Domain
API Application Programming
Interface DMF Data Management Facility
APPC Advanced DNS Domain Name Support
Program-to-Program DOR data-owning region
Communication
DOS Disk Operating System
APPL application
DS Dispatcher Domain
APPN Advanced Peer-to-Peer
Networking DSA Dynamic Storage Area
AR Attention Routine DTR Dynamic Transaction Routing
ASI Automatic System DU Dump Domain
Initialization ECB event control block
BG background EDSA Extended Dynamic Storage
BMS Basic Mapping Support Area
BSM Basic Security Manager EIP EXEC interface program
BTAM Basic Telecommunications EOJ end of job
Access Method EOV end of volume
CDRM Cross-Domain Resource ESA Enterprise Systems
Manager Architecture
CDSA CICS Dynamic Storage Area ESDS Entry Sequenced Data Set
CEMT Master Terminal Transaction ESM External Security Manager
CET Central European Time EXCI external CICS interface
CI control interval EXEC Execute/Execution
CICS Customer Information Control FCT File Control Table
System
FEPI Front-End Programming
CICS TS Customer Information Control Interface
System Transaction Server
FOR file-owning region
CICSVR CICS VSAM Recovery
FORTRAN formula translation
CMF CICS Monitoring Facility
FSU Fast Service Upgrade
COBOL common business-oriented
language FTP File Transfer Program
CPC central computer complex GB Gigabyte
© Copyright IBM Corp. 1999 235
GDDM Graphical Data Display MQSeries Message Queuing Series
Manager
MRO multiregion operation
GID Group Identifier
MVS Multiple Virtual Storage
GL Global Catalog Domain
MVS/ESA Multiple Virtual
GLUE global user exit Storage/Enterprise Systems
Architecture
GTF generalized trace facility
N/A not applicable
HLASM high-level assembler
NLT nucleus load table
HLL high-level language
NSR nonshared resources
I/O input/output
OCO object code only
IBM International Business
Machines OS/390 IBM System/390 Operating
System
ICCF Interactive Computing and
Control Facility PA Parameter Manager Domain
ID identification/identifier PCT Program Control Table
II interactive interface PG Program Manager Domain
IPL initial program load PL/I Programming Language 1
IRC interregion communication PLT Program List Table
ISC intersystem communication PLTPI Program List Table Post
Initialization
IT Information Technology
PLTSD Program List Table Shutdown
ITSO International Technical
Support Organization POR printer-owning region
IUI Interactive User Interface POWER Priority Output Writers,
Execution processor, and
JACD Journal Archive Control Data
input Readers
set
PPT Processing Program Table
JCT journal control table
PSB program specification block
KE Kernel Domain
PSP preventive service planning
KSDS Key Sequenced Data Set
PTF Program Temporary Fix
LC Local Catalog Domain
QOR queue-owning region
LAN local area network
RACF Resource Access Control
LANRES/VSE LAN Resource Extension and
Facility
Services/VSE
RC return code
LD Loader Domain
RCF Report Controller Facility
LE/VSE Language Environment for
VSE/ESA RDSA Read-only Dynamic Storage
Area
LM Lock Manager Domain
REXX Restructured Extended
LPAR Logically Partitioned mode
Executor
LSR Local Shared Resources
RDO Resource Definition Online
LU logical unit
RMODE Residency mode
M Megabyte
RPG Report Program Generator
MB Megabyte
S/390 IBM System/390
ME Message Domain
SAF System Authorization Facility
MN Monitoring Domain
SAM Sequential Access Method
MPS multiple partition support
SDT Shared Data Table
MQ message queue
SIT System Initialization Table
MQI Message Queue Interface
SM Storage Manager Domain
236 VSE/ESA V2R4
SMA Security Migration Aid VM/ESA Virtual Machine/Enterprise
Systems Architecture
SNA Systems Network
Architecture VSAM Virtual Storage Access
Method
SNT System Signon Table
VSCR Virtual Storage Constraint
SPI System Programming
Relief
Interface
VSE Virtual Storage Extended
ST Statistics Domain
VSE/ESA Virtual Storage
STS Security Transaction Server
Extended/Enterprise Systems
SVA Shared Virtual Area Architecture
SYSRES system residence file VSE/POWER Virtual Storage
TCT Terminal Control Table Extended/Priority Output
Writers, Execution processor,
TI Timer Domain and input Readers
TLT Terminal List Table VSE/VSAM Virtual Storage
TOD time of day Extended/Virtual Storage
Access Method
TOR terminal-owning region
VTAM Virtual Telecommunications
TR Trace Domain Access Method
TRUE task-related user exit VTOC Volume Table of Contents
UDSA User Dynamic Storage Area WWW World Wide Web
URM User-Replaceable Module XM Transaction Manager Domain
US User Domain XPI exit programming interface
VM Virtual Machine XRF extended recovery facility
VM/CMS Virtual XS Security Manager Domain
Machine/Conversational
Monitor System
List of Abbreviations 237
238 VSE/ESA V2R4
Index
coexistence (continued)
A shared data tables (SDT) 146
abbreviations 235 sharing data 145
acronyms 235 sharing the CDS 120
APPC autoinstall 68 summary 9
Application Load Table 69 cold start 42
Application Migration Aid (AMA) 186 compile job dialog 186
autoinstall control program 65, 66, 67, 69 conversion tools 184
autoinstall model 66 cross-memory services 70
autoinstall of programs 63 CSD groups 219
autoinstall of resources 48, 62 CSFE DEBUG transaction 217
automatic installation 15 CSPL transient data queue 63
automatic journal archive 24, 58
D
B Data Management Facility (DMF)
Basic Mapping Support (BMS) 188 collecting statistics using DMF 178
basic security manager (BSM) 73 define the DMF datasets 170
bibliography 231 DMF commands 175
BTAM terminal support 9, 131 DMF startup jobstream 173
DMF startup table 172
initialize the DMF datasets 171
C monitoring data to DMF datasets 181
C/370 14, 183 monitoring domain 5
CA-Top Secret 83 operating DMF 174
CADL transient data queue 68 processing DMF statistics 179
CEMT command changes, examples 152 DB2 Server 145
CETR transaction 194 DEFINE PROFILE command 41
CICS Data Systems Workload 168 DEFINE PROGRAM command 39
CICS system definition (CSD) DEFINE TERMINAL command 52
backup old CSD 18 DEFINE TRANSACTION command 39
CSD considerations 118 DEFINE TYPETERM command 53
CSD integrity 121 DFH0STAT, new sample program 176
restore old CSD 18 DFHDCT customization 56
sharing the CDS 120 DFHDCT macro changes 55
upgrade CSD 18 DFHDCT source 57
use of CSD 17 DFHFCT macro changes 43
CICS system dumps 208 DFHFCT migration 41
coexistence DFHFCT source 43
access from BTAM terminals 131 DFHJCT customization 57
application programs 146 DFHJCT macro changes 55
availability of Interactive Interface 130 DFHJCT source 58
avoid non-compatible definitions 127 DFHMSCAN 184
coexistence of DL/I releases 141 DFHPCT migration 32
compatibility option for DFHCSDUP 124 DFHPCTC2 source 34
connection definitions for MRO 122 DFHPLT macro changes 55
CSD considerations 118 DFHPPT migration 32
CSD integrity 121 DFHPPTC2 source 33
introduction 117 DFHSIT generation 30
loading phases into the SVA 136, 138 DFHSIT parameter changes 26
methods to define resources 118 DFHSITC2 source 30
migration options 132 DFHTCT migration 48
sample autoinstall programs 123 DFHTCT source 49
separate CSD files 130 DFHTCTC2 source 52
session definitions for MRO 122
© Copyright IBM Corp. 1999 239
DFHTU410, trace utility program 206
DFHZCQ 67 M
DL/I considerations MIGRATE command 35, 44, 50
coexistence of DL/I releases 141 MIGRATE=COMPLETE option 44, 51
DL/I versions 139 migration planning 11
executing MPS job streams 144 model definition 64
installation 139 monitoring data to DMF datasets 181
LIBDEF chains 139 MXT system initialization parameter 167
migration effort 140
summary 9
SVA considerations 139
N
new with CICS TS 2
domains, CICS restructure 2
non-shared resource (NSR) file 162
DOS PL/I 11, 14, 183
nucleus load table (NLT) 69
DOS/VS COBOL 2, 11, 14, 183
DOS/VS RPG II 11, 183
DSALIM, new system initialization parameter
165
164, O
obsolete CICS transient data queues 56
dump suppression 216 obsolete tables in CICS TS 69, 88
dynamic storage area (DSA) 163, 164 OS390 emulation mode 25
E P
EDSALIM, new system initialization parameter 164, paging rate 169
165 partition content of CICS TS 163
enhancements in VSE/ESA 2.4 1 partition content of CICS/VSE 2.3 162
extended base tape 10, 14 partition layout for CICS in VSE/ESA 2.3 160
external CICS interface (EXCI) 7 partition layout for CICS in VSE/ESA 2.4 161
external security manager (ESM) 73 PLTPI customization 59
external security manager, summary of 8 PLTSD customization 60
predefined environments 15
processor utilization 168
F program list table (PLT) processing changes 148
Fast Service Upgrade (FSU) 14
program list table (PLT) program execution key 148
first failure data capture 213
programming language support 11, 14, 183
front-end programming interface (FEPI) 7
G R
removed from CICS TS 2, 32
global catalog 4, 20, 22
RENTPGM, new system initialization parameter 7,
global user exit (GLUE) interface 149
165
Report Controller 19, 111
H restructured CICS 2
hardware requirements 13
S
I sample autoinstall programs 67, 123
security
INSTALL command 38
IPL SYS command 73 APPC (LU6.2) session security 110
basic security manager 75
default CICS user ID 107
J default link user ID 111
journal data set 23 DFHSNT migration 88, 91
DFLTUSER, new system initialization
parameter 107
L dialog for defining transaction security 91
label area on virtual disk 9 DTSECTAB 74
local catalog 4, 20, 22 DTSECTAB and ESM 83
local shared resource (LSR) pool 45, 162 DTSECTAB example 83
DTSECTXN 75, 95, 98
240 VSE/ESA V2R4
security (continued) statistics (continued)
DTSECTXN assembly 99 statistics domain 6
ESM installation 83 unsolicited statistics 179
IESUPDCF sample job 92 storage protection 7
IPL SYS command 73 system authorization facility (SAF) 73, 82
levels of security 87 system files for second CICS 19
link security 111 system generation 147
MERGE function 104 system initialization overlays 148
Multiregion (MRO) security 110 system management improvements 8
PLT programs startup 109 system programming interface (SPI) 155
PLTPISEC, new system initialization system programming macros 151
parameter 109 system resource requirements 168
PLTPIUSR, new system initialization
parameter 109
printer security 112 T
report security 111 task-related user exit (TRUE) 150
resource security 109 task-related user exit support in DB2 150
REXX procedure for converting DFHPCT 100 terminal autoinstall 68
SECPRFX, new system initialization parameter 96 terminal control install interface program 67
security migration aid (SMA) 112 traces
security parameter specification 95 CETR transaction 194
security server 75 DFHTU410, trace utility program 206
security server commands 77, 79 trace formatting 200
security server priority 77 trace level 192
security server startup 76 trace-related keyword 193
sign-on security 87 tracing for development regions 199
SNSCOPE, new system initialization parameter 93 tracing for production regions 199
surrogate user checking 110 TRANCLASS definition 40, 69
system authorization facility (SAF) 82 transaction class 69
terminal security 112 transaction definition parameter 166
transaction-attach security 95, 109 transaction definition parameter, default 166
trigger-level transaction 109 Turbo Dispatcher 9, 13, 168
user sign-on, sign-off 93 TYPETERM definition 50
VSE.CONTROL.FILE 74, 75
Service Update Facility 10
shared data tables (SDT) 8, 70, 146 U
Shared Virtual Area (SVA) user exit interface 149
IPL SVA statement 158 user-replaceable modules (URM)
SDL value change 158 URMs dropped 150
SVA storage layout for VSE/ESA 2.3 159 URMs new 150
SVA storage layout for VSE/ESA 2.4 159 URMs supplied by VSE/ESA 151
SVA storage requirements 158 user-replaceable modules (URM) 150
shareoption 23
sign-on table (SNT) 69
SIR command 169
V
vendor products 83
SKCICS2 61 vendor software 15
SKPREPC2 20 virtual storage constraint relief (VSCR) 7
software considerations 14 virtual storage requirements 16, 157
SQL/DS applications 145 VS COBOL II 2, 11, 14, 183
statistics VSE startup parameter
changes to statistics 176 ALLOC parameter 157
collecting statistics using DMF 178 PASIZE parameter 157
DFH0STAT, new sample program 176 SYSDEF parameter 158
processing DMF statistics 179 VSIZE parameter 158
sample statistics program 176 VSE/Access Control-Logging and Reporting
sample statistics program output 178 (ACLR) 81
sample statistics program output, examples 221 VSE/POWER enhancements 10, 75
STAT transaction 177
Index 241
VTAM autoinstall 66
VTAM-connected terminal 48
X
XRF environment 15
242 VSE/ESA V2R4
ITSO Redbook Evaluation
Migration to VSE/ESA 2.4 and CICS Transaction Server for VSE/ESA 1.1
SG24-5595-00
Your feedback is very important to help us maintain the quality of ITSO redbooks. Please complete this
questionnaire and return it using one of the following methods:
Use the online evaluation form found at http://www.redbooks.ibm.com/
Fax this form to: USA International Access Code + 1 914 432 8264
Send your comments in an Internet note to redbook@us.ibm.com
Which of the following best describes you?
__Customer __Business Partner __Solution Developer __IBM employee
__None of the above
Please rate your overall satisfaction with this book using the scale:
(1 = very good, 2 = good, 3 = average, 4 = poor, 5 = very poor)
Overall Satisfaction ____________
Please answer the following questions:
Was this redbook published in time for your needs? Yes____ No____
If no, please explain:
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
What other redbooks would you like to see published?
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
Comments/Suggestions: (THANK YOU FOR YOUR FEEDBACK!)
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
© Copyright IBM Corp. 1999 243
Migration to VSE/ESA 2.4 and CICS Transaction Server for VSE/ESA 1.1 SG24-5595-00
Printed in the U.S.A.
SG24-5595-00
Other docs by blacksadow2
Image and Workflow Library- Content Manager for ImagePlus on OS-390 Implementation and EIP
Views: 165 | Downloads: 1
