File-AID for IMS/DC Installation Guide

File-AID for IMS/DC

Installation Guide

Release 7.5

ii

File-AID for IMS/DC Installation Guide

Please direct questions about File-AID for IMS or comments on this document to:

File-AID for IMS Customer Support

Compuware Corporation

One Campus Martius

Detroit, MI 48226-5099

1-800-538-7822

Outside the USA and Canada, please contact your local Compuware office or agent.

This document and the product referenced in it are subject to the following legends:

Copyright 1986-2010 Compuware Corporation. All rights reserved. Unpublished rights reserved under the

Copyright Laws of the United States.

U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Compuware Corporation license agreement and as provided in DFARS

227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995),

FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. Compuware Corporation.

This product contains confidential information and trade secrets of Compuware Corporation. Use, disclosure, or reproduction is prohibited without the prior express written permission of Compuware

Corporation. Access is limited to authorized users. Use of this product is subject to the terms and conditions of the user’s License Agreement with Compuware Corporation.

Abend-AID, Compuware, File-AID, and FrontLine are trademarks or registered trademarks of Compuware

Corporation.

BookManager, CICS, IBM, IMS, and MVS/ESA are trademarks or registered trademarks of International

Business Machines Corporation.

Adobe

®

Reader

®

is a trademark of Adobe Systems Incorporated in the United States and/or other countries.

All other company and product names are trademarks or registered trademarks of their respective owners.

Doc. CWFIID7F

January 21, 2010.

iii

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

What’s New in Release 7.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Browse and Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Extract and Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

New Commands for Release 7.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

What’s New in Release 7.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

Secondary Index Support for Extract and Selection Criteria . . . . . . . . . . .xiii

Unicode UTF-16 Support in Edit and Browse . . . . . . . . . . . . . . . . . . . . . . .xiii

Audit Trail User Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

What’s New in Release 7.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

Expanded Data Privacy Management via File-AID/EPDM . . . . . . . . . . . . .xiii

Product Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

FrontLine Support Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

World Wide Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Chapter 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

License Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Execution Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Installation Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Single Transaction Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Multiple Transaction Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Audit Trail Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

DBD Tailoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

PSB Tailoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

IMS System Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Access Fast Path Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Space Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

CLT Control Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

MFS Tailoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Limiting DL/I Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

IMS Message Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Resource Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Installation Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Chapter 2. Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Step 1. Define Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

iv

Step 2. Access File-AID for IMS/DC INSTALL Panel . . . . . . . . . . . . . . . . . . . . . . 2-1

Step 3. Assemble and Link Installation Parameters . . . . . . . . . . . . . . . . . . . . . . 2-3

Step 4. Assemble and Link MFS Source Code . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Step 5. Modify DBD Source Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

DBD Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

Step 6. Assemble DBD Source Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

Step 7. Modify PSBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Step 8. Assemble PSB Source Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Step 9. Generate ACB Control Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Step 10. Allocate Control Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26

Step 11. Copy Training Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

Step 12. Assemble/Link Sample Security Exit . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

Step 13. Create Aliases to the Main Load Module . . . . . . . . . . . . . . . . . . . . . . 2-43

Step 14. Access Additional Databases and Segment Layouts . . . . . . . . . . . . . 2-46

Chapter 3. Verification of the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Step 1. Verify Primary Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Step 2. Edit DBD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Step 3. Edit Data Base Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Step 4. Select Segment and Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Step 5. Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Potential Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Appendix A. File-AID for IMS Security Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Security Exit Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Call Sequence: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

AMODE 31 and XRMODE ANY Parameters . . . . . . . . . . . . . . . . . . . . . . . A-2

Security Parms Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

INPUT PARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

INPUT/OUTPUT PARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Appendix B. Maintenance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Control Database DBD Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Control Database Segment Size Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Security Exit Added or Changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Installation Parameters Changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2

Control Segment Missing or Invalid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2

Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3

DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3

IXPREBLD Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3

Back up and Restore Control Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-4

New File-AID Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-4

CPU Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-5

Disaster Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-5

Permanent CPU Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-5

Appendix C. Load Module Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Appendix D. Batch DBD and XREF Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

DBD Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

DBD Update JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

DBDUPBMP–IMSBATCH Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

DBDUPDLI–DLIBATCH Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

DBDUPSDB–SDB Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

DBD Update DD Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5

Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5

Program Control Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6

v

DBD Execution Return Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6

Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6

Batch XREF Update Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7

Segment Layout Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7

Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-8

XREF Update JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-8

XRFUPBMP–IMSBATCH Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-9

XRFUPDLI–DLIBATCH Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-10

XRFUPSDB–SDB Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-11

XREF Update DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-11

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12

Option Control Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12

XREF Execution Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-14

Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-14

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

vi


vii

Figures

2-1.

Install Manager Main Menu .....................................................................................2-2

2-2.

Installation Task Table..............................................................................................2-2

2-3.

File-AID for IMS/DC – INSTALL MENU....................................................................2-3

2-4.

File-AID for IMS/DC Audit Trail Feature Screen.......................................................2-3

2-5.

File-AID for IMS/DC Installation Parameters Screen................................................2-4

2-6.

File-AID for IMS/DC Naming Conventions Screen..................................................2-5

2-7.

File-AID for IMS/DC Audit Trail Feature Screen.......................................................2-6

2-8.

File-AID for IMS/DC Audit Trail DBD Exceptions Screen ........................................2-7

2-9.

File-AID for IMS/DC Audit Trail DBD Exception List Screen ...................................2-8

2-10.

File-AID for IMS – Generate Install JCL Screen (@FDIPRM) .....................................2-9

2-11.

File-AID for IMS/DC MFS Screen ............................................................................2-10

2-12.

File-AID for IMS – Generate Install JCL Screen (@FDMFS).....................................2-11

2-13.

Example of JCL to Link-Edit the MFS Modules, Part 1 ..........................................2-12

2-14.

Example of JCL to Link-Edit the MFS Modules, Part 2 ..........................................2-13

2-15.

LTM DBD Example .................................................................................................2-15

2-16.

CLT DBD Example ..................................................................................................2-15

2-17.

AUD DBD Example.................................................................................................2-16

2-18.

File-AID for IMS/DC DBD Generate Screen............................................................2-16

2-19.

File-AID for IMS – Generate Install JCL Screen (@FDDBD) ....................................2-17

2-20.

Example of JCL to Link-Edit the DBD Source Modules, Part 1 ..............................2-18

2-21.

Example of JCL to Link-Edit the DBD Source Modules, Part 2 ..............................2-19

2-22.

Program Specification Block (PSB) Example ..........................................................2-20

2-23.

File-AID for IMS/DC PSB Generate Screen .............................................................2-21

2-24.

File-AID for IMS – Generate Install JCL Screen (@FDPSB)......................................2-21

2-25.

Example of JCL to Assemble and Link-Edit PSB Source Modules, Part 1...............2-22

2-26.

Example of JCL to Assemble and Link-Edit PSB Source Modules, Part 2...............2-23

2-27.

File-AID for IMS/DC ACB Generate Screen ............................................................2-24

2-28.

File-AID for IMS – Generate Install JCL Screen (@FDACB).....................................2-24

2-29.

Example of JCL to Link File-AID for IMS/DC Load Library ...................................2-25

2-30.

File-AID for IMS/DC Allocate Control Database Screen.........................................2-26

2-31.

File-AID for IMS VSAM Control Database Screen ..................................................2-27

2-32.

File-AID for IMS – Generate Install JCL Screen (@FDALOCV) ...............................2-27

2-33.

Example JCL, Allocate File-AID for IMS/DC VSAM Control Databases, Part 1......2-28

2-34.


2-35.


2-36.

Example JCL, Allocate File-AID for IMS/DC OSAM Control Databases, Part 1 .....2-31

2-37.


2-38.


2-39.

File-AID for IMS/DC Training Files Screen .............................................................2-34

2-40.

File-AID for IMS – Generate Install JCL Screen (@FDTRAIN) .................................2-34

2-41.

Example of JCL to Copy Training Files, Part 1.......................................................2-35

2-42.


2-43.


2-44.


2-45.

File-AID for IMS/DC Security Exit Screen...............................................................2-39

2-46.

File-AID for IMS – Generate Install JCL Screen (@FDSCXT)...................................2-39

2-47.

Example JCL, Compile and Link-Edit the Sample Security Exit Program, Part 1 ..2-40

2-48.


2-49.


2-50.


2-51.

File-AID for IMS/DC Aliases Screen ........................................................................2-44

2-52.

File-AID for IMS/DC Aliases List Screen .................................................................2-44

2-53.

File-AID for IMS – Generate Install JCL Screen (@FDALIAS) ..................................2-45

2-54.

Example of JCL to Allocate and Unload File-AID for IMS/DC Libraries ................2-46

3-1.

Primary Option Menu ..............................................................................................3-1

3-2.

DBD Member List Screen..........................................................................................3-2

Figures

viii

3-3.

Data Base Location Screen ........................................................................................3-2

3-4.

Formatted Screen ......................................................................................................3-3

3-5.

Unformatted Screen..................................................................................................3-3

3-6.

Key Specification Screen ...........................................................................................3-4

3-7.

Unformatted/HEX OFF Screen .................................................................................3-4

3-8.

Index Screen .............................................................................................................3-5

B-1.

Online Control Information Update Summary Report ...........................................B-4

D-1.

DBDUPBMP–IMSBATCH JCL Procedure ................................................................. D-2

D-2.

DBDUPDLI–DLIBATCH JCL Procedure ................................................................... D-3

D-3.

DBDUPSDB–SDB JCL Procedure .............................................................................. D-4

D-4.

DBD UPDATE SUMMARY FOR ONLINE ACCESS ................................................... D-7

D-5.

XRFUPBMP–IMSBATCH JCL Procedure .................................................................. D-9

D-6.

XRFUPDLI–DLIBATCH JCL Procedure .................................................................. D-10

D-7.

XRFUPSDB–SDB JCL Procedure ............................................................................. D-11

D-8.

Seg/Layout XREF and COBOL Layout Update Summaries ................................... D-15

ix

Tables

1-1.

Naming Convention Rules .......................................................................................1-3

1-2.

LTM and CLT Databases ...........................................................................................1-5

1-3.

AUD Database ...........................................................................................................1-6

1-4.

Resource Protection Approaches ............................................................................1-11

1-5.

IMS Large Message Queue Requirements ...............................................................1-12

2-1.

Installation Parameters Field Descriptions ...............................................................2-4

2-2.

Naming Conventions Field Descriptions .................................................................2-5

2-3.

Audit Trail Feature Field Descriptions ......................................................................2-6

2-4.

Audit Trail DBD Exceptions Field Descriptions........................................................2-7

2-5.

Audit Trail DBD Exception List Field Descriptions ..................................................2-8

A-1.

Input Parms ............................................................................................................. A-2

A-2.

Input/Output Parms ................................................................................................ A-3

B-1.

JCLSCXT Symbolic Parameters.................................................................................B-2

B-2.

Rebuild Control Segment Program DD Statements .................................................B-3

C-1.

File-AID for IMS/DC Load Modules......................................................................... C-1

D-1.

DBD Update Program DD Statements ..................................................................... D-5

D-2.

Segment Layout Dataset Types................................................................................ D-7

D-3.

XREF Update Program DD Statements .................................................................. D-12

Tables

x

xi

Summary of Changes

Sum_Chgs

Changes to this document for Release 7.5 are indicated with a vertical bar (|) in the left margin.

What’s New in Release 7.5

Compuware is pleased to announce File-AID for IMS Release 7.5. Continuing our commitment in responding to customer requests, we have added the following enhancements:

Parameters

Enhanced and Expanded Parameters Selection Menu

Option 1 System Parameters now allows you to control the checkpoint frequency used

during load processing and the maximum number of database segments to search when using a FIND or CHANGE command. The Print parameter settings are now included within this option.

Option 2 Modify DLI Parameters is a new option that allows you to override DLI

parameters.

Option 3 Modify BMP Parameters is a new option that allows you to override BMP

parameters.

Option 4 IMS DLI Datasets is a new option that allows you to override IMS datasets

used during DLI processing.

Option 5 Temporary Dataset Allocations is a new option that allows you to control the

allocation of the IMS log and File-AID for IMS audit trail.

Each of these options provide a RESTORE command which will reset displayed parameter values to system defaults.

User ID Variable to Define Dataset Concatenations

You may use a User ID variable (

#USERID

) to define dataset names included in dataset concatenations available in a File-AID for IMS environment.

Browse and Edit

Unicode Support for DBCS Character Data

File-AID for IMS Formatted Edit and Browse functions allow you to edit IMS segments containing mixtures of DBCS and Unicode data.

Optional Delete Confirmation in Edit

The user controlled option to display a confirmation pop-up before segments are actually deleted during an edit session has been added. This allows you to confirm whether the delete request should be processed or not. The Delete Confirmation option in the System

Parameters Option 0.1 controls whether to show or hide the confirmation pop-up.

xii


Extract and Load

Extract Using Concatenated Keys

You can use a key file consisting of concatenated keys to drive your extract processing.

Save Selection Criteria with New Name

Temporary or existing selection criteria may be edited and saved to an existing PDS or sequential dataset. Use the SAVEAS (SAVAS) command to save to a different member or dataset.

Rename DBDs During Load Processing

A user controlled option has been added to allow DBD names appearing in an extract file to be changed prior to load processing.

Write Records Discarded During Load to a File

A user controlled option has been added to allow records discarded during load processing to be written to a discard file.

Utilities

Database Hierarchy Displayed from Utilities Menu

A new option in the Utilities menu invokes the database Hierarchy Display panels that previously were only available in Edit and Browse.

Miscellaneous

Restrict Processing to One or More HALDB Partitions

When processing a HALDB, a new panel is displayed listing all of its database partitions.

You may restrict processing to one or more of these partitions or use all of them.

New Commands for Release 7.5

The following primary commands are new for Release 7.5:

BMP : The BMP command displays the “File-AID for IMS – Modify BMP Parameters”

screen, where you can override certain BMP parameters. This command terminates the current screen processing. When you exit the “File-AID for IMS – Modify BMP

Parameters” screen, you return to the File-AID for IMS Primary Option Menu, where you can select the desired option.

DLI : The DLI command displays the “DLI Parameters Screen” screen, where you can

override certain DLI parameters. This command terminates the current screen processing. When you exit the “DLI Parameters Screen” screen, you return to the File-

AID for IMS Primary Option Menu, where you can select the desired option.

SAVEAS : When editing selection criteria, including temporary selection criteria,

SAVEAS, or SAVAS, store the selection criteria data in a different dataset or member.

For an existing partitioned dataset member, the member is rewritten with the same name and the library statistics for the member are updated.

TMP : The TMP command displays the “Temporary Dataset Allocations” screen, where

you can control the allocation of the IMS log and File-AID for IMS audit trail. This command terminates the current screen processing. When you exit the “Temporary

Dataset Allocations” screen, you return to the File-AID for IMS Primary Option Menu, where you can select the desired option.

Summary of Changes

xiii

VHEX : The VHEX command displays the “Edit Unicode Field” screen for the selected

Unicode field. The entire value of the field is displayed vertically with one character per line. There you can edit the field in hexadecimal image. Each character is identified by its Unicode hex value and its description. Valid only for Unicode field values in Formatted Edit and Browse.

The following row command is newly documented for Release 7.5:

H (Hierarchy) : The H (Hierarchy) line command graphically displays the structure of

the the selected DBD during extract and load.


Compuware is pleased to announce File-AID for IMS Release 7.4. Continuing our commitment in responding to customer requests, we have added the following enhancements:

Secondary Index Support for Extract and Selection Criteria

The File-AID for IMS extract has been enhanced to make use of secondary indexes. Using secondary indexes may improve efficiency of extract processing. Data can now be extracted using secondary index key file processing when appropriate. You can use extract selection criteria referencing secondary index search fields for direct access processing where possible.

Unicode UTF-16 Support in Edit and Browse

File-AID for IMS Browse and Edit functions support Unicode (UTF-16) when the data is located on a COBOL usage NATIONAL field. The Browse and Edit functions retrieve the native Unicode data in formatted mode. Then, after converting the data from Unicode to terminal CCSID EBCDIC-based data, File-AID for IMS displays the converted EBCDICbased data on the Browse/Edit formatted data screens.

In an Edit session, you can edit the converted data in the Unicode fields. Characters that can’t be displayed with your current code page are protected. When you enter your edits, the EBCDIC-based data is converted back to Unicode.

A record layout is required to recognize data as Unicode data. Therefore, Compuware recommends to edit Unicode data only in Formatted display mode.

Audit Trail User Exit

A user exit (IXPATXT) may be coded to provide special processing of File-AID for IMS audit trail records. This exit can be used to write the audit trail records to a different location than the two standard options available through File-AID for IMS (Audit trail dataset and SMF).


Expanded Data Privacy Management via File-AID/EPDM

The integration of File-AID/Enterprise Data Privacy Manager (File-AID/EDPM) begins with the centralized storage of Data Privacy specifications in Release 1.0. Future capabilities will allow Security Administrators and other users to control, enforce, and audit the coverage of data privacy techniques for both in-house or out-sourced application development and testing from a centralized workbench.File-AID for IMS 7.3 introduces File-AID/EDPM and is required to support this centralized Privacy Manager

xiv


Repository. If File-AID for IMS is installed with the File-AID/EDPM Repository, you have the option to save all data disguise criteria to the Privacy Manager Repository with an

Owner and Project name or to the Disguise Criteria File.If File-AID for IMS is installed without the File-AID/EDPM Repository, criteria can only be saved to the Disguise Criteria

File.

Product Delivery

File-AID is now delivered on a CD-ROM. Use the File-AID installation media to offload the product files to DASD. Follow the Upload Instructions included with the installation media for details.

xv

Introduction

This guide is intended for use by IMS system programmers and database administrators in the installation of the File-AID for IMS system. It describes how to install the DC component of File-AID for IMS, including customization, verification, and problem determination. Detailed knowledge of your IMS environment is required to correctly complete the installation process.

Related Publications

The following File-AID for IMS documents are available from Compuware. To obtain hardcopies, please call your Compuware sales representative.

• File-AID for IMS/ISPF Reference Manual: This manual details the information necessary to fully use the features of File-AID for IMS/ISPF.

• File-AID for IMS/ISPF Installation Guide: This manual provides a step-by-step description of how to install File-AID for IMS/ISPF on your system. It is intended for database administrators and the systems group responsible for File-AID for IMS at your installation.

• File-AID for IMS/CICS Installation Guide: This guide provides a step-by-step description of how to install File-AID for IMS/CICS on your system. It is intended for database administrators and the systems group responsible for File-AID for IMS at your installation.

• File-AID for IMS/DC Installation Guide: This guide provides a step-by-step description of how to install File-AID for IMS/DC on your system. It is intended for database administrators and the systems group responsible for File-AID for IMS at your installation.

• File-AID for IMS/DC/CICS Reference Manual: This manual details the information necessary to fully use the features of File-AID for IMS/DC/CICS.

• File-AID for IMS/FLEX Reference Manual: This manual details the information necessary to fully use the features of File-AID for IMS/FLEX.

• File-AID for IMS Quick Reference: This reference provides a summary of the File-AID for

IMS options and commands. It is intended for any user of File-AID for IMS.

• File-AID for IMS Messages and Codes Manual: This manual provides information on the error messages that you may encounter within File-AID for IMS.

FrontLine Support Website

Access online customer support for Compuware products via our FrontLine support website. View or download documentation, frequently asked questions, and product fixes, or directly e-mail Compuware with questions or comments. To access FrontLine, you must first register and obtain a password at http://frontline.compuware.com.

Online Documentation

The installation package includes the following File-AID for IMS documentation in these electronic formats:

• Release Notes in HTML format

• The product manuals in PDF format

Intro

xvi


• The Adobe PDF index file (PDX file).

View and print the PDF files with Adobe Reader version 6.0 or more current. Download a free copy of the reader from Adobe’s Web site, http://www.adobe.com.

The File-AID for IMS product manuals are also available in HTML and IBM BookManager formats at the FrontLine Web site.

HTML files can be viewed with any standard web browser.

BookManager softcopy files can be viewed with any version of IBM BookManager READ or the IBM Library Reader. To learn more about BookManager or download the free

Library Reader, go to http://www.ibm.com.

World Wide Web

Compuware’s site on the World Wide Web provides information about Compuware and its products. The address is http://www.compuware.com.

Getting Help

At Compuware, we strive to make our products and documentation the best in the industry. Feedback from our customers helps us to maintain our quality standards.

Questions about File-AID for IMS or comments on this document should be directed to:

File-AID for IMS Customer Support

http://www.compuware.com/support.

If problems arise, consult your manual or the File-AID for IMS customer support representative at your site. If problems persist, please obtain the following information before contacting Compuware. This information helps us to efficiently determine the cause of the problem.

1. Obtain your client number and write it in the space below.

Client No._____________________________________

2. If you are getting an error message from File-AID for IMS, press PF1 for an extended explanation of the error.

3. If you are getting a batch error message from File-AID for IMS, keep the JCL and output.

4. Enter the VIEW command from any COMMAND line within the product and print the configuration report. Refer to the description of the “View” command in the primary commands chapter of the File-AID for IMS/ISPF Reference Manual for more information.

5. Determine the product function being used and the sequence of events leading up to the problem.

6. If files are involved, determine the file characteristics.

7. Record any ISPF/PDF error messages or operating system messages. If an abend occurs, record the abend or screen information.

8. Determine the versions of current operating system components that may have an impact on the problem.

1-1

Chapter 1.

Overview

File-AID for IMS is an interactive, full-screen product designed for use by application programmers, analysts, and database administrators. This product provides the ability to easily access and manipulate data within IMS databases. The databases can be browsed or edited in any of the following modes directly under IMS/DC:

• Formatted using COBOL or PL/I segment layouts

• Unformatted in hexadecimal

• Hierarchical sequence with one segment per screen line

File-AID for IMS executes as a single segment, nonconversational Message Processing

Program (MPP) that requires absolutely no modifications to IMS, DL/I, or any other existing software. An IMS Stage 1 system definition job must be run to define File-AID for

IMS to the IMS system.

The File-AID for IMS system, not including user database DBDs and PSBs, consists of the following:

• Product load modules

• Product MFS modules

• 3 Control Databases

• 3 Control DBDs

• 1 or more Transactions

• 1 or more PSBs/ACBs

File-AID for IMS/ISPF Option 7, Release 3.2 or later must be installed to create and maintain the segment/layout cross-reference data used by File-AID for IMS. Depending on system resource availability and IMS system definition job scheduling, plan to spend from six to twelve hours installing File-AID for IMS.

Read this guide thoroughly, paying particular attention to the sections on “IMS System

Definition” on page 1-7 and “PSB Tailoring” on page 1-6, before beginning the

installation process. It is beneficial to do these steps before beginning the process

outlined in Chapter 2, “Installation Steps”.

License Management System

Compuware provides the License Management System (LMS) to help manage access to

Compuware’s products at your site. The LMS includes several components that together allow you to establish, maintain, diagnose, and upgrade access to the Compuware products licensed by your enterprise.

Install LMS from the Enterprise Common Components (ECC) installation media.

Separately, via e-mail you receive a License Certificate for File-AID for IMS.

IMPORTANT:

File-AID for IMS/DC operation requires these steps:

1-2


1. Ensure that the Compuware License Management System has been installed from the

ECC installation media.

Refer to the Compuware Enterprise Common Components Installation and Customization

Guide for installation procedures. This step is only necessary for a first-time install of

LMS or when upgrading the License Management System itself.

2. Import the License Certificate into your License File.

3. Establish and update the Runtime License Management System by running the program LMSINIT.

Refer to the “License Certificate Import Checklist” section in the Compuware License

Management User/Reference Guide for detailed instructions.

System Requirements

• The operating environment required is IMS release 7 or higher.

• The two datasets created in JCLLINK occupy approximately two 3380 cylinders.

• File-AID for IMS/DC uses approximately 200K of IMS/DC MPP region, with a maximum of approximately 300K.

• File-AID for IMS/ISPF Release 7.5 or greater must be installed prior to installing File-

AID for IMS/DC.

Execution Environment

There are a number of execution environment items that need to be considered during the installation process.

Installation Configuration

The two basic configurations used to run File-AID for IMS are single transaction and multiple transaction. The type of configuration affects the steps taken during installation.

Single Transaction Configuration

Use a single transaction configuration if:

1. Your installation has only one programming group.

2. The number of databases does not exceed the number practical for a single PSB. IMS allows a maximum of 500 PCBs in a PSB.

3. Transaction security will be the same for all users.

4. Including all the databases in one PSB will not exceed your installation’s PSB pool

size (refer to “PSB Tailoring” on page 1-6).

In a single transaction configuration, only one transaction code is used to invoke File-

AID for IMS. Up to 494 user database PCBs can be included in the PSB associated with the transaction (File-AID for IMS uses six PCBs in the PSB), provided that the resulting ACB does not exceed your IMS PSB pool size. Security can be based on the transaction name and can be enhanced by using the File-AID for IMS security exit, other security products

(e.g., SMU, RACF, CA-ACF2, CA-TOP SECRET), or both.

Multiple Transaction Configuration

Use a multiple transaction configuration if:

Overview

1-3

1. Your installation has more than one programming group and each group needs access to different sets of databases.

2. The number of databases exceeds the number practical for a single PSB. IMS allows a maximum of 500 PCBs in a PSB.

3. Transaction security will vary with different programming groups.

4. Including all the database PCBs in one PSB will exceed your installation’s PSB pool

size (refer to “PSB Tailoring” on page 1-6).

In a multiple transaction configuration, two or more transaction codes are used to invoke

File-AID for IMS. Each transaction code is associated with a different PSB. Each PSB contains PCBs for a set of databases. Because the PSB name must be the same as the main load module name, the load module uses alias names to match the names of the PSBs. Up to 494 user database PCBs can be included in each PSB (File-AID for IMS uses six PCBs in the PSB), provided that the resulting ACB does not exceed your IMS PSB pool size. Each transaction can have different security requirements to allow more lenient access to certain databases. Transaction security can be enhanced by using the File-AID for IMS security exit, other security products, or both.

Naming Conventions

File-AID for IMS enables you to customize MFS format, program, DBD, and transaction names to your installation’s naming conventions. However, certain rules must be followed so that File-AID for IMS can find the modules it needs during execution. The following table summarizes these rules.

Table 1-1.

Naming Convention Rules

TRANSACTION

DBD

MFS MOD

MAIN PROGRAM

OTHER PROGRAMS

1 to 8 characters

1 to 8 characters

1 to 4 character prefix

3 to 4 character suffix

1 to 8 characters

1 to 4 character prefix

3 to 4 character suffix

None

None

Same number of characters as MID

Cannot Change

Must Match PSB

None

Cannot Change

Default

FILEAID

See Source Code

IXDO

See Source Code

IXDMAIN

IXD

See Source Code

Transaction and DBD names can be completely modified. However, the MFS MOD names and program names must adhere to the rules listed above.

The first three or four characters of the default program names (other than the main program’s) and MFS MOD names can be partially modified to meet your installation’s requirements. The characters that can be modified are referred to as the prefix. You can use a different prefix for the MFS MODs and program names.

The default prefix for the MOD names is IXDO. If you change the length of the MFS

MOD prefix (that is, from IXDO to IXD) in the MFS source code, you must also change the length of the MFS MID prefix to match that of the MOD prefix (that is, from IXDI to

IXI) in the MFS source code. Do not change the program prefix for IXDHEDX or

IXMHED1.

The default for the program names is IXD. The remaining characters (the suffix) are not modifiable. The main program’s name, IXDMAIN, can be completely changed. The only restriction is that its name, or its alias name, must be the same as the PSB/ACB name (this is an IMS restriction).

After choosing the prefixes appropriate for your installation, change the MFS source code and load module names to reflect your choices. This modification is explained in

Chapter 2, “Installation Steps”.

1-4


Before starting the installation process, determine what names and prefixes your installation will be using.

Audit Trail Feature

The File-AID for IMS Audit Trail feature is an option that captures user updates to a database into the File-AID for IMS’s Audit Trail (AUD) control database. The database update information can then be extracted from the AUD control database with the batch

Audit Trail extract program (IXPATEXT). The extracted information is then sorted and processed by the batch reporting program (IXPATRPD), which generates the Audit Trail

Report.

The end users of File-AID for IMS do not have any control over which databases are protected by the Audit Trail feature. Those decisions are made and administered at the installation level by the individual or group responsible for File-AID for IMS. The user database updates that are to be captured by the Audit Trail feature are specified in the

File-AID for IMS installation parameters described on page 2-3, the File-AID for IMS

Security Exit described in Appendix A, “File-AID for IMS Security Exit”, or both.

The Audit Trail Extract program (IXPATEXT) and the Audit Trail Report program

(IXPATRPD) are actually part of File-AID for IMS/ISPF and are located in that load library.

These programs can be run as DL/I batch or BMP jobs. These programs and the sort of the extracted audit trail information are described in the File-AID for IMS/DC/CICS Reference

Manual.

Compuware recommends that you decide whether you want to use the Audit Trail feature at your installation before you actually begin to install File-AID for IMS. If you don’t want to use the Audit Trail feature immediately but think you may want to in the near future, it is simpler to include the Audit Trail feature in the installation process. You can include the necessary Audit Trail control database information into the installation process and still disable the Audit Trail feature through the File-AID for IMS installation parameters. If you add the Audit Trail feature later, you will be required to execute several of the installation steps again (e.g., regenerate PSBs and ACBs).

Each step of the installation process described in this guide that can be affected by the use of the Audit Trail feature contains an appropriate explanation.

DBD Tailoring

File-AID for IMS uses three databases to store information created or used during execution. These databases are referred to as control databases. Two of the control databases are required and one is optional.

The LTM control database is required and is used to store information between transactions. It is updated as each transaction ends, before the screen is displayed. The other required control database is CLT, which contains static information about the user databases, including segment layouts. The CLT is updated primarily by the DBD Update and XREF Update batch programs. The use of these programs is described in the File-AID

for IMS/DC/CICS Reference Manual.

The third control database is the optional AUD or Audit Trail control database. If you choose to use the Audit Trail feature of File-AID for IMS at your installation, the AUD database is used to capture the update activity processed against the databases you specify. It is not necessary to create the AUD control database if you do not choose to use the Audit Trail feature at your installation.

All three control databases use the HDAM access method and IBM’s randomizing module

DFSHDC40. There are two parameters that are input to this randomizing module that must be altered to your installation’s requirements—the Relative Block Number (RBN) and the Root Addressable Area size (BYTES). These parameters are specified in the

RMNAME= keyword in the DBD statement for each of the three control database DBDs.

Overview

1-5

To calculate the RBN parameter for the LTM control database, multiply the estimated number of users who will be using File-AID for IMS (allow for growth) by 1.20. To calculate the RBN parameter for the CLT database, add the number of user databases to the number of layouts for the segments in those databases (allow for growth), and multiply this number by 1.20.

Calculate the RBN parameter for the AUD database as follows:

• Decide how often you plan to extract and delete the Audit Trail database segments

(by executing the IXPATEXT program as described in the File-AID for IMS/DC/CICS

Reference Manual).

• Estimate the typical total number of segment updates (inserts, repeats, deletes, and replaces of all database segment types) that will take place at your installation (across all the user databases where the Audit Trail feature will be active) between the planned extraction and deletion of the Audit Trail database segments.

• Divide the number of total updates by 16.

The resulting value is the RBN used for the AUD control database. For example, if you plan to extract and delete the segments from the Audit Trail database every two days and the daily segment updates total is estimated at 400, then the RBN is calculated as (2 *

400)/16 = 50.

Refer to the LTM and CLT databases table to determine the BYTES parameter. In the

Maximum User DB Segment Length column, find the row that corresponds to your installation’s maximum user database segment length. Within this row, find the BYTES operand from the RMNAME Bytes column. Because the minimal SEGM bytes for the LTM and CLT databases is 8,158 bytes, use the data from row one if all your user databases have segment lengths less than 8,153 bytes. The same RMNAME bytes parameter must be used for both the CLT and LTM databases. Also, based on the row selected, use the corresponding CI/BLOCK value for the SIZE parameter in the DATASET statement in both control databases.

Table 1-2.

LTM and CLT Databases

DBD Parameters

Maximum User DB

Segment Length

RMNAME

Bytes

SEGM Bytes

Dataset Allocation

CI/BLOCK RECSZ

8,153 or less 8,177 8,158 8,192 8,185

Buffer Used

8,192

12,249 12,273 12,254 12,288 12,281 12,288

16,345 16,369 16,350 16,384 16,377 16,384

20,441 20,465 20,446 20,480 20,473 20,480

24,537 24,561 24,542 24,576 24,569 24,576

28,633 28,657 28,638 28,672 28,665 28,672

30,681 30,705 30,688 30,720 30,713 30,720

To determine the BYTES parameter for the AUD database, you must first perform the following steps:

1. Determine the length of the longest user database segment whose updates will be captured by the Audit Trail feature. This value is specified for the BYTES= keyword in the SEGM statement that defines each user database segment type in the DBD source code for each database.

2. Determine the length of the longest fully concatenated key to a user database segment whose updates will be captured by the Audit Trail feature. One way to determine this value is to look for the largest KEYLEN= parameter value specified on a PCB statement within the PSBs that contain an Audit Trail database PCB.

1-6


Add the longest segment length value to the longest concatenated key value. Then, find the row that corresponds to the result in the Maximum User DB Segment Plus Concat Key

Length column in the AUD database table (Table 1-3). Within this row, find the BYTES

operand from the RMNAME Bytes column. Because the minimal SEGM bytes for the AUD database is 8,102 bytes, use the data from row one if the result you calculated is less than

8054 bytes. Also, based on the row selected, use the corresponding CI/BLOCK value for the size parameter in the DATASET statement in the AUD database.

Table 1-3.

AUD Database

DBD Parameters

Maximum User DB

Segment Plus Concat

Key Length

RMNAME

Bytes

SEGM Bytes

Dataset Allocation

CI/BLOCK RECSZ

8,054 or less 8,117 8,102 8,192 8,185

Buffer Used

8,192

12,150 12,213 12,198 12,288 12,281 12,288

16,246 16,309 16,294 16,384 16,377 16,384

20,342 20,405 20,390 20,480 20,473 20,480

24,438 24,501 24,486 24,576 24,569 24,576

28,534 28,597 28,582 28,672 28,665 28,672

30,582 30,645 30,630 30,720 30,713 30,720

Further modifications to the control database DBDs are explained in Chapter 2,

“Installation Steps”.

PSB Tailoring

All PSBs used by File-AID for IMS must contain five PCBs for the CLT and LTM control databases, as well as PCBs for the user databases. If the Audit Trail feature is going to be activated for any of the user databases accessed through a given PSB, then a sixth PCB must be coded for the AUD control database. In a single transaction configuration there is only one PSB that will contain these PCBs.

However, in a multiple transaction configuration, there are usually multiple PSBs, each with PCBs for the control databases and PCBs for a subset of the user databases. Some thought must be given to grouping the user database PCBs into the PSBs. Following are some suggestions:

1. Provide each programming group with its own PSB, which contains PCBs for the databases that the group uses.

2. Group each set of application related databases into its own PSB.

3. Group databases that have strict access security in a PSB separate from databases that have more lenient access.

4. Group test database PCBs in one PSB, production database PCBs in another.

Remember, a separate transaction code must be created for each PSB defined.

Note: Each PCB within a PSB requires storage in the IMS PSB pool. In some situations,

depending on the number of PCBs in the PSB, the installation limit for the IMS

PSB pool size may be exceeded. If this limit is exceeded, you must either split the

PSB into smaller PSBs and create a separate transaction for each PSB, or increase the IMS PSB pool size.

Overview

1-7

Following are some guidelines for creating PSBs:

1. The first five PCBs in the source code must be exactly as shown in Figure 2-22 on page 2-20, except for the NAME= operand on the first PCB. This name corresponds to

the transaction name and is used for message switching. The sixth PCB, as shown in that chapter, is optional for the AUD control database.

2. The PROCOPT parameter on all user database PCBs should be A and should be specified on the PCB macro and not the SENSEG macro. If you want to enforce security using the PSBs, you can specify a PROCOPT parameter of G, GO, or GOT on the user databases. This action causes File-AID for IMS to display an abend screen with an AM status code and then the Primary Option Menu whenever one of these user databases is edited.

3. To exclude a segment from processing by File-AID for IMS, simply leave the segment out of the PCB. The excluded segment is not displayed nor updated.

4. Do not code more than one PCB per database within a single PSB. File-AID for IMS cannot differentiate between them.

IMS System Definition

File-AID for IMS runs like any other IMS application and, therefore, must be initially defined to the IMS system. Because system definition can be performed only at specific times at your installation, it will speed the installation process if you do the following before starting the detailed installation steps:

1. Code an APPLCTN and TRANSACT macro for each transaction/PSB combination to be used in your installation configuration. These macros are input to the IMS Stage 1 system definition job.

The PSB= operand must be the same as the main program name or an alias’ program name and correspond to the PSBNAME= operand of the PSB used as the transaction.

APPLCTN PSB=IXDMAIN,PGMTYPE=(TP,,,)

For full-featured databases code the following:

TRANSACT CODE=FILEAID,MSGTYPE=(SNGLSEG,RESPONSE),MODE=SNGL,

PROCLIM=(10,2),EDIT=ULC,SCHD=1

For Fast Path databases code the following:

TRANSACT CODE=FILEAID,MSGTYPE=(SNGLSEG,RESPONSE),MODE=SNGL,

PROCLIM=(10,2),EDIT=ULC,SCHD=1,FPATH=YES

The CODE= operand in the TRANSACT macro corresponds to the NAME= operand in

the first PCB in the transaction’s PSB. Refer to “Step 7. Modify PSBs” on page 2-19.

IMPORTANT:

The TRANSACT macro must be coded with the RESPONSE keyword, and the

TERMINAL macro CANNOT be coded with NORESP. Failure to do this will yield unpredictable results.

To browse/edit Fast Path databases with File-AID for IMS you need to define the transaction as an IMS Fast Path potential transaction. File-AID for IMS does not run as a Fast Path exclusive transaction. An IMS Fast Path potential transaction is identified by a TRANSACT macro statement that specifies FPATH=YES following an

APPLCTN statement that does not specify FPATH=YES

2. Code a DATABASE macro to define the required CLT and LTM control database DBDs, the three sample database DBDs, and, optionally, the AUD DBD. These macros are input to the IMS Stage 1 system definition job.

1-8


DATABASE DBD=IXDCLT,ACCESS=EX

DATABASE DBD=IXDLTM,ACCESS=EX

DATABASE DBD=IXDAUD,ACCESS=EX

DATABASE DBD=PCUST,ACCESS=EX

DATABASE DBD=PORDR,ACCESS=EX

DATABASE DBD=PPART,ACCESS=EX

If you want the Data Management Block (DMB) created by the database statement to be made resident in storage during system initialization, include the resident option on the database statement.

3. If you want the control databases and sample databases to participate in IMS dynamic allocation, code a DFSMDA macro for each one. These macros are input to the IMSDALOC procedure during IMS system definition.

DFSMDA TYPE=DATABASE,DBDNAME=IXDCLT

DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.IXDCLT,

DDNAME=IXDCLTDD

DFSMDA TYPE=DATABASE,DBDNAME=IXDLTM

DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.IXDLTM,

DDNAME=IXDLTMDD

DFSMDA TYPE=DATABASE,DBDNAME=IXDAUD

DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.IXDAUD,

DDNAME=IXDAUDDD

DFSMDA TYPE=DATABASE,DBDNAME=PCUST

DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.FIDSAMP.CUSTOMER,

DDNAME=PCUSTDD

DFSMDA TYPE=DATABASE,DBDNAME=PORDR

DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.FIDSAMP.ORDER,

DDNAME=PORDRDD

DFSMDA TYPE=DATABASE,DBDNAME=PPART

DFSMDA TYPE=DATASET,DSNAME=XXXXXXX.FIDSAMP.PART,

DDNAME=PPARTDD

4. If you do not want these databases to be dynamically allocated, add a DD card for each to the IMS startup JCL.

//IXDCLTDD DD DSN=XXXXXXX.IXDCLT,DISP=OLD

//IXDLTMDD DD DSN=XXXXXXX.IXDLTM,DISP=OLD

//IXDAUDDD DD DSN=XXXXXXX.IXDAUD,DISP=OLD

//PCUSTDD DD DSN=XXXXXXX.FIDSAMP.CUSTOMER,DISP=OLD

//PORDRDD DD DSN=XXXXXXX.FIDSAMP.ORDER,DISP=OLD

//PPARTDD DD DSN=XXXXXXX.FIDSAMP.PART,DISP=OLD

5. If you want the control databases and sample databases to be under the control of

DBRC, code an INIT.DB and INIT.DBDS command for each. These commands are input to the Recovery Control Utility of DBRC.

INIT.DB DBD(IXDCLT) SHARELVL(0) TYPEIMS

INIT.DBDS DBD(IXDCLT) DDN(IXDCLTDD)

DSN(XXXXXXX.IXDCLT) GENMAX(2)

INIT.DB DBD(IXDLTM) SHARELVL(0) TYPEIMS

INIT.DBDS DBD(IXDLTM) DDN(IXDLTMDD)

DSN(XXXXXXX.IXDLTM) GENMAX(2)

INIT.DB DBD(IXDAUD) SHARELVL(0) TYPEIMS

INIT.DBDS DBD(IXDAUD) DDN(IXDAUDDD)

DSN(XXXXXXX.IXDAUD) GENMAX(2)

INIT.DB DBD(PCUST) SHARELVL(0) TYPEIMS

INIT.DBDS DBD(PCUST) DDN(PCUSTDD)

DSN(XXXXXXX.FIDSAMP.CUSTOMER) GENMAX(2)

Overview

1-9

INIT.DB DBD(PORDR) SHARELVL(0) TYPEIMS

INIT.DBDS DBD(PORDR) DDN(PORDRDD)

DSN(XXXXXXX.FIDSAMP.ORDER) GENMAX(2)

INIT.DB DBD(PPART) SHARELVL(0) TYPEIMS

INIT.DBDS DBD(PPART) DDN(PPARTDD)

DSN(XXXXXXX.FIDSAMP.PART) GENMAX(2)

Access Fast Path Databases

File-AID for IMS supports browse/edit access to Fast Path databases.

To access Fast Path databases you can create a transaction/PSB combination that is separate from your full feature databases. To do this, create a PSB as described in the

guidelines listed under “PSB Tailoring” on page 1-6.

Next, you must code an APPLCTN and TRANSACT macro for a Fast Path potential

transaction. (Refer to “IMS System Definition” on page 1-7.)

You must have File-AID for IMS/ISPF Release 3.0 or later installed to access DEDB Fast

Path databases. File-AID for IMS/ISPF Release 3.2 or later must be installed to access

MSDB Fast Path databases and SDEP (Sequential Dependent) segment types.

Other than the above there are no other differences between accessing a Fast Path database and a full featured IMS database.

Space Allocation

File-AID for IMS’s control databases require one dataset each. It is recommended that the control databases be allocated as VSAM files because of their segment sizes. However, if your installation does not want to use VSAM, the control databases can be allocated as

OSAM files, but the ACCESS parameter of the DBD macro within the DBD source must be modified to reflect this.

Use the following formulas to calculate the space needed by the control databases:

• LTM dataset size: bytes = RBN calculated earlier * CI size * 14

• CLT dataset size: bytes = RBN calculated earlier * CI size

• AUD dataset size: bytes = RBN calculated earlier * CI size

These formulas assume a stable user base. If you anticipate that the user base will grow, you should factor this growth into the formulas before allocating the datasets.

Convert the number of bytes required to the number of cylinders required.

CLT Control Database

As mentioned earlier, the CLT control database contains information about the user databases. A control segment, also found on this database, stores various counts and control fields used to verify the database’s integrity. Most of this information remains static during on-line File-AID for IMS execution. However, there are three batch programs, herein referred to as DBD Update (IXPDBDUP), XREF Update (IXPXRFUP), and

Rebuild Control Segment (IXPREBLD), that are used to maintain the information on the

CLT database. These programs are actually part of File-AID for IMS/ISPF and are located in that load library. The programs can be run either as DL/I batch or BMP jobs.

The DBD Update program updates the CLT control database with information about the user databases’ hierarchical structure. The DBD Update program uses the DBD control blocks from the DBD load library to obtain this information.

1-10


Note: This job must be run for each database before it can be accessed under File-AID

for IMS

The XREF Update program updates the CLT control database with information about the segment-to-layout cross-reference. The XREF Update program uses the segment/layout

XREF data created in File-AID for IMS/ISPF option 7, along with the DBD information gained by the DBD Update program. This job must be run to allow File-AID for IMS access to your segment layouts. It does not need to be run if segment layouts do not exist.

However, if not run, formatted mode is not available.

These jobs are run during the Detailed Installation Steps for the sample databases. If you want to access additional databases, the DBD Update program must be run again using control cards for your databases. Optionally, the XREF Update job must be run to allow use of your segment layouts. Refer to the File-AID for IMS/DC/CICS Reference Manual for more information.

The Rebuild Control Segment program recreates the control segment. If the control segment was inadvertently updated or deleted, it must be rebuilt to ensure accurate

processing of the databases. Refer to “DD Statements” on page B-3 for more information.

MFS Tailoring

MFS formats for 3270 Model 2 devices and symbolic device types of 3270-A2, 3270-A3,

3270-A4, and 3270-A7 are supplied with File-AID for IMS. The following screen sizes are assumed for these symbolic devices.

3270-A2

3270-A3

3270-A4

3270-A7 *

24 x 80

32 x 80

43 x 80

27 x 132

Note: Display will be 24 x 80

If your installation has defined these symbolic device types differently, you must change the TYPE= operand on the DEV macro in the MFS source code. If you are not sure how your installation has defined the symbolic device types, the MFS Service Utility can produce a report that lists the device characteristics table.

If your installation does not have all the previously mentioned symbolic devices defined to IMS, you must modify the MFS source code before it is assembled. Either comment out or delete the DIF/DOFs for the symbolic terminal types that are not supported.

If you change the length of the MFS MOD prefix (that is, from IXDO to IXD) in the MFS source code, you must also change the length of the MFS MID prefix to match that of the

MOD prefix (that is, from IXDI to IXI) in the MFS source code.

Limiting DL/I Calls

Compuware recommends that a limit be enforced on the number of DL/I database movement calls permitted during one transaction to prevent excessive resource usage when browsing or editing large databases. A database movement call is one that changes your position to another segment. This limit is specified in the Lmtcalls field in the installation parameters updated by JCLIPRMS. When the specified limit is reached, the position is at the last segment retrieved, and a message is displayed on the screen.

Overview

1-11

Security

Access can be controlled with the same security procedures currently in place at your installation because File-AID for IMS runs as an MPP application under IMS. Like any other application, it must be defined to your security package during the installation process.

An exit is provided for your use when additional security checks are wanted. Refer to

Appendix A, “File-AID for IMS Security Exit” for details on how to write the security

routine.

The following table summarizes several alternative security approaches to use with File-

AID for IMS.

Table 1-4.

Resource Protection Approaches

Protected

Resource

Type of Security

Database

PTERM

LTERM

Segment Sensitivity

Field Sensitivity

Sign-on Verification

Terminal-User

Resource Access

PSB

Transaction

Resource Access

LTERM

Password

Resource Access

DBD

Access mode

DBD-User-Password

File-AID for IMS Function

Security Product

IMS

N/A

SMU and IMS user exit

IMS user exit



SMU

SMU


File-AID for IMS exit

File-AID for IMS exit

Notes*

1, 7, 8

2

3,4

4

3,4

3,4

3

3

3,4

5

5,6

Notes:

1. Segment sensitivity is controlled through the PCBs in the PSB.

2. File-AID for IMS does not support field sensitivity.

3. SMU - Security Maintenance Utility.

4. User exit refers to a custom exit routine or a security product.

5. Must be written for your particular installation.

6. Edit/Browse security.

7. The PROCOPT parameter on all user database PCBs should be A and should be specified on the PCB macro and not the SENSEG macro. If you want to enforce security using the PSBs, you can specify a PROCOPT parameter of G, GO, or GOT on the user databases. This action causes File-AID for IMS to display an abend screen with an AM status code and then the Primary Option Menu whenever one of these user databases is edited.

8. To exclude a segment from processing, simply leave the segment out of the PCB. The excluded segment is not displayed nor updated.

In many instances it may be desirable to limit access of certain databases to specific users.

This can be accomplished in the following ways:

1. Code a security exit that checks the DBD name against the User ID entered either during sign-on or on the Primary Option Menu. This is the only way to limit database access in a single transaction configuration.

1-12


2. Create multiple PSBs with different database PCBs within them. Assign each PSB to a separate transaction, and use transaction security to limit their use. With this method, the File-AID for IMS security exit is not required. You can simply use the security procedures currently in place at your installation. This is the method recommended for multi-transaction configurations.

In addition, your normal PTERM, LTERM, and PSB security can be enforced with the use of security packages that may be installed at your installation.

IMS Message Queues

Because IMS does not allow an MFS output message to span logical records, the system large message queue record length must be long enough to contain the messages produced by File-AID for IMS and the system prefix. The following table outlines these requirements.

Table 1-5.

IMS Large Message Queue Requirements

Screen Size Message Length

24 x 80 1764

32 x 80

43 x 80

2404

3353

Note: Add 48 bytes if MSC is installed

LGMSG Queue Size Required*

1852

2492

3441

Large message queue sizes that are less than these will cause unpredictable results. The large message queue size at your installation can be verified with the IMS command

/DISPLAY POOL QBUF. If the queue is not large enough, the value on the IMS system macro MSGQUEUE must be increased. Refer to IMS/ESA Installation Guide for more information.

Resource Usage

The average CPU time for a File-AID for IMS transaction is from 0.5 to 1.5 seconds.

Installation Output

Print and keep the output from the jobs run during the installation process. If there are any problems with the installation or operation of File-AID for IMS, you might need to refer to the output.

2-1

Chapter 2.

Installation Steps

This chapter provides the step-by-step instructions to install File-AID for IMS/DC. Before you can start the installation of File-AID for IMS/DC, you must have successfully completed the installation and verification of File-AID for IMS/ISPF.

Note: Compuware product media can be installed for one year after it is created. Before

installing this release of File-AID for IMS, check the date on the media label. If the media’s date is more that one year old, call File-AID for IMS Customer

Support to have new media sent to you.

Step 1. Define Environment

1. Use the Stage 1 system definition procedures in place at your installation to define

File-AID for IMS’s transactions, applications, and databases to IMS.

a. If you want File-AID for IMS’s control databases or sample databases to participate in IMS dynamic allocation, define them to IMS through the

IMSDALOC procedure in place at your installation.

b. If you do not want the databases dynamically allocated, add a DD card for each database dataset to the IMS startup JCL.

c. If you want File-AID for IMS’s control databases or sample databases under the control of DBRC, use the Recovery Control Utility to define them.

2. If required, define the transactions, applications, and databases to your existing security package.

Refer to “IMS System Definition” on page 1-7 for more information.

Step 2. Access File-AID for IMS/DC INSTALL Panel

When you installed File-AID for IMS/ISPF, you updated the SETUP CLIST in the File-AID for IMS install dataset that was shipped with the product. If you copied this CLIST to a library defined to your SYSPROC concatenation, you will be able to start the File-AID for

IMS/DC installation process in either of the following ways:

• On the command line, type:

TSO SETUP

• From Option 5, COMMAND, of the ISPF/PDF Primary Option Menu, type:

SETUP

If the SETUP CLIST is not defined to your SYSPROC concatenation, you may invoke it using the following command:

TSO EX ‘install.dsn(SETUP)’ where “install.dsn” is the name of your File-AID for IMS installation dataset.

When you execute the SETUP CLIST, the Install Manager main menu is displayed

(Figure 2-1 on page 2-2).

2-2


Figure 2-1. Install Manager Main Menu

Install Manager ------------------ SET UP ----------------------- VER: 04.02.01

OPTION ===>

Product.... FILE-AID FOR IMS

Version.... 07.04.00

OLD Table Dataset ===> 'IX.V7R3M0.ISPTLIB'

NEW Install Dataset ===> 'IX.V7R5M0.INSTALL'

Select option:

1 DATASET NAMES - Specify required datasets

2 INSTALL OPTIONS - Specify installation parameters

3 PRODUCT OPTIONS - Specify product options

4 INSTALL - Execute installation steps

5 START

6 MAINTAIN

- Start the product to verify installation

- Apply or View Maintenance (Optional)

X EXIT - Terminate Install Manager

Note: If this is the first time you are installing File-AID for IMS at your site, the OLD

Table Dataset field displays a “NOT AVAILABLE” value.

1. Select Option 4, INSTALL from the main menu. The Installation Task Table is

displayed (Figure 2-2).

Figure 2-2. Installation Task Table

Install Manager ---------- Installation Task Table --------- Row 1 to 10 of 13

COMMAND ===> SCROLL===> CSR

Select a task to install:

Product.... FILE-AID FOR IMS

Version.... 07.04.00

Table...... IX#EXE

Primary cmds: END/UP/DOWN

Line cmds: S/E/?

Task

Cmd Number Description

--- ----------------------------------------------------------------

01 ALLOCATE AND LOAD DATASETS

02

03

04

05

LINK EDIT FILE-AID FOR IMS

COPY GENERATED OBJECTS

CREATE VB CLIST LIBRARY (OPTIONAL)

GENERATE IXGLOBL LOAD MODULE

06

07

08

09

10

EXECUTE ADMIN OPTION

COPY FILE-AID FOR IMS TRAINING FILES (OPTIONAL)

GENERATE FILE-AID SVC'S (OPTIONAL)

LINK PANVALET ACCESS MODULE(OPTIONAL)

USER EXITS (OPTIONAL)

2. Select Option 11, INSTALL File-AID for IMS DC Option (Optional), from the

Installation Task Table. The File-AID for IMS/DC - INSTALL MENU is displayed

(Figure 2-3 on page 2-3).

Installation Steps

2-3

Figure 2-3. File-AID for IMS/DC – INSTALL MENU

INSTALL ------------- File-AID for IMS/DC - INSTALL MENU ----------------------

OPTION ===>

1 IPRM

2 MFS

3 DBD

4 PSB

- Assemble/Link Installation Parameters

- Assemble/Link MFS modules into IMS format library

- Assemble DBD source code

- Assemble PSB source code

5 ACB

6 CONTROL DB

- Generate ACB control blocks

- Allocate control databases

7 TRAINING - Copy training files

8 SECURITY EXIT - Assemble/Link sample security exit

9 ALIASES - Create Aliases to main load module

Step 3. Assemble and Link Installation Parameters

1. Select option 1, IPRM, from the File-AID for IMS/DC Installation Menu.

The File-AID for IMS/DC Audit Trail Feature screen is displayed (Figure 2-4).

Figure 2-4. File-AID for IMS/DC Audit Trail Feature Screen

INSTALL ---------- File-AID for IMS/DC Audit Trail Feature --------------------

COMMAND ===>

Compuware recommends that you decide whether you want to use the audit trail feature at your installation before you continue the install. If you do not want to use the audit trail feature immediately but think you may want to in the near future, it is simpler to include the audit trail feature in the installation process.

You can include the necessary audit trail control database information into the installation process and still disable the audit trail feature in the following installation parameters. If you add the audit trail feature later you will be required to execute several of the installation steps again

(e.g., regenerate PSBs and ACBs).

INCLUDE AUDIT TRAIL FEATURE IN INSTALL ===> Y (Y = Yes, N = No)

2. Enter Y or N to indicate whether you want to install the audit trail feature.

Refer to “Audit Trail Feature” on page 1-4 for a description of the audit trail feature.

3. Press Enter.

2-4


The File-AID for IMS/DC Installation Parameters screen is displayed (Figure 2-5).

Figure 2-5. File-AID for IMS/DC Installation Parameters Screen

INSTALL --------- File-AID for IMS/DC Installation Parameters -----------------

COMMAND ===>

IMS Version/Release

LIMIT DB CALLS

INTEGRITY CHECK IND

CAPS MODE

CODE PAGE

===> 08100

===> 100

===> Y

===> ON

===> 0697

(e.g. 08100 = version 8.1)

(50 - 32767)

(Y = Yes, N = No)

(ON or OFF)

(0697 - English (default)

0905 - Canadian Bilingual

0277 - Danish/Norwegian

0297 - France

0424 - Hebrew

0500 - Swiss French/Swiss German

0290 - Japanese Katakana

0833 - Korea

0838 - Thailand)

-------------------------------------------------------------------------------

LIMIT DB CALLS limits the number of database movement calls that can be performed in one transaction. INTEGRITY CHECK IND indicates to check segment for a change by a concurrent user prior to an update.

4. Enter the values for each field as they apply to your installation. Refer to Table 2-1

for a description of the fields. Each field’s label name as it appears in the JCL is shown in parentheses.

Table 2-1.

Installation Parameters Field Descriptions

Field / (Label)

(IMSVERSN)

Description

IMS Version/Release

Default: 08100 (IMS 8.1.0)

Version-release of IMS (first two positions are version, last three are release). Use

08100 for IMS 8.1.0.

LIMIT DB CALLS

(LMTCALLS)

Default: 100

Database movement call limit. The maximum number of database movement calls that are permitted during one transaction. Recommended minimum value is

50. Maximum allowable value is 32,767.

INTEGRITY CHECK

IND

(INTEGIND)

CAPS MODE

(CAPSMODE)

Default: Y

Integrity check indicator. Indicates whether the Integrity Check feature is to be active when File-AID for IMS is used to edit databases. Default value Y indicates that the segment is verified for any changes made by a concurrent user prior to an update. N indicates that the Integrity Check feature is not active for any databases edited.

Default: ON

Default caps mode. Indicates the initial caps mode to be set when a user invokes

File-AID for IMS. Controls whether alphabetic data entered is automatically translated to uppercase or left as is.


2-5

Table 2-1.

Installation Parameters Field Descriptions

Field / (Label)

CODE PAGE

(CODEPAGE)

Description

Default: 0697

Code to represent the codepage translation required at your site.

0697 Default (English)

0277 Danish and Norwegian

0290 Japan

0297 France

0424 Hebrew

0500 Swiss-French and Swiss-German

0833 Korean

0838 Thailand

0905 Canadian bilingual

5. Press Enter.

The File-AID for IMS/DC Naming Conventions screen is displayed (Figure 2-6).

Figure 2-6. File-AID for IMS/DC Naming Conventions Screen

INSTALL --------- File-AID for IMS/DC Naming Conventions ----------------------

COMMAND ===>

Program name prefix

MFS MOD name prefix

End MFS MOD name

===> IXD

===> IXDO

===>

(1 to 4 characters or default IXD)

(1 to 4 characters or default IXDO)

(default blanks)

--------------------------------------------------------------------------------

You can use a different prefix for the MFS MOD names and program names other than the default. If you change the length of the MFS MOD prefix

(that is, from IXDO to IXD) you must also change the length of the MFS MID prefix to match that of the MOD prefix. END MFS MOD name is the MFS MOD that you want formatted upon exit from the product.


for a description of the fields:

Table 2-2.

Naming Conventions Field Descriptions

Field / (Label)

Program name prefix

Description

Default: IXD

Program name prefix. Must match the prefix specified for the load module names on the NAME linkage editor control cards in JCLPERML.

(PGMPRFX)

MFS MOD name prefix

Default: IXDO

MFS MOD name prefix. Must match the prefix specified for the MOD names in the MFS source code assembled by JCLMFS.

(MODPRFX)

End MFS MOD name

(ENDMOD)

Default: blanks

End MFS MOD name. The MFS MOD name that you want formatted upon exit from the product (for example, a user menu used to invoke File-AID for IMS).

Leave blank if MOD is not to be formatted upon exit.

2-6


7. Press Enter.

The File-AID for IMS/DC Audit Trail Feature screen is displayed (Figure 2-7) if you

selected to install the Audit Trail Feature.

If you chose not to install the Audit Trail Feature, the File-AID for IMS – Generate

Install JCL screen is displayed (Figure 2-10 on page 2-9).

Figure 2-7. File-AID for IMS/DC Audit Trail Feature Screen

INSTALL --------- File-AID for IMS/DC Audit Trail Feature ---------------------

COMMAND ===>

The name your installation has selected for the audit trail database DBD.

Leave blank if you are not using this feature.

Audit Trail DBD name ===> IXDAUD

The maximum number of dependent segments to be written to the audit trail database when a parent segment is deleted. 0 to 32,767 limits the number of children written to the audit trail database. -1 writes all children to the audit trail database.

Dependent Seg. No.

===> -1 (-1 to 32,767)

The maximum size of an audit trail segment to be written to the audit trail database. This is the MAX BYTES value you specified for the BYTES= keyword on the SEGM statements in the AUD database DBD source code as calculated using the installation guide.

Maximum Seg. Size ===> 0 (0 to 30,630)


for a description of the fields:

Table 2-3.

Audit Trail Feature Field Descriptions

Field / (Label) Description

Audit Trail DBD name

(ATTRLDBD)

Default: blanks

Audit Trail database DBD name. Enter the name your installation chose for the File-

AID for IMS Audit Trail DBD name.

Enter *NOCHK* if you want File-AID for IMS to attempt to use the database to write audit records without validating that the DBD name in the PSB matches the one specified here.

Leave blank if you are not using the Audit Trail feature.

Dependent Seg. No.

Default: -1

(DEPSEGNO)

Maximum Seg. Size

(MAXSEGSZ)

Number of deleted dependent segments to be captured by the Audit Trail feature.

When a segment that has dependent segments under it is deleted, IMS automatically deletes all those dependent segments. Indicate the maximum number of deleted dependent segment images you want written to the Audit Trail database for a given deleted parent. Default value of -1 indicates that images of all deleted dependents are to be captured. Specify zero if deleted dependents are not to be captured. The maximum allowable value is 32,767.

Default: Zero

Audit Trail database maximum segment size. This is the MAX BYTES value you specified for the BYTES= keyword on the SEGM statements in the AUD database

DBD source code. Refer to “DBD Tailoring” on page 1-4 and “Step 6. Assemble

DBD Source Code” on page 2-16 for additional information about the AUD

database segments’ size.

9. Press Enter.


2-7

The File-AID for IMS/DC Audit Trail DBD Exceptions screen is displayed (Figure 2-8).

Figure 2-8. File-AID for IMS/DC Audit Trail DBD Exceptions Screen

INSTALL --------- File-AID for IMS/DC Audit Trail DBD exceptions --------------

COMMAND ===>

The ALL/NONE audit trail indicator indicates whether or not to create an audit trail when databases are edited. 'A' will activate this feature for all databases edited using File-AID for IMS/DC except for those specified in the exception list. 'N' will deactivate this feature for all databases edited except for those specified in the exception list.

ALL/NONE indicator ===> N (A = All, N = None)

The DBD exception list will exclude databases from the audit trail when the

ALL/NONE indicator is 'A'. If no exception DBDs are specified, the audit trail feature will be active for all databases edited through File-AID for

IMS/DC. The DBD exception list will include databases in the audit trail when the ALL/NONE indicator is 'N'. If no exception DBDs are specified, then the audit trail feature will not be active at any time. A wild card may be used to specify DBDs. 'PEMPL

'IXD*

' will include or exclude database PEMPL only.

' will include or exclude all databases beginning with 'IXD'.

The next screen will process the DBD exception list. Press enter to continue.

10. Enter A or N. Table 2-4 describes the ALL/NONE indicator for the Audit Trail feature:

Table 2-4.

Audit Trail DBD Exceptions Field Descriptions


ALL/NONE indicator

(ALLNONE)

Default: N

All/None Audit Trail indicator. Indicates whether you want the Audit Trail feature to be active when File-AID for IMS is used to edit databases. Default value of N indicates that the Audit Trail feature will not be active for any databases that are

edited, except for those specified in the exception list (Figure 2-9 on page 2-8). A

indicates that the Audit Trail feature will be active for all databases that are edited,

except for those specified in the exception list (Figure 2-9 on page 2-8). If the

Audit Trail feature is not going to be used at your installation, leave this indicator set to N.

11. Press Enter.

The File-AID for IMS/DC Audit Trail DBD Exception List screen is displayed (Figure 2-

9 on page 2-8).

2-8


Figure 2-9. File-AID for IMS/DC Audit Trail DBD Exception List Screen

INSTALL --------- File-AID for IMS/DC DBD Exception List --- Row 1 to 11 of 11

COMMAND ===> SCROLL ===> PAGE

_

_

_

_

_

_

I=Insert,D=Delete

Action DBD

------------------------------------------------------------------------------

_

_

_

_

_

******************************* Bottom of data ********************************

12. To add a DBD to the list, enter the action I and the name of the DBD. To remove a

DBD from the list, enter the action D in front of the listed DBD. Refer to Table 2-5 for

a description of the fields:

Table 2-5.

Audit Trail DBD Exception List Field Descriptions


Action I=Insert the DBD.

DBD

D=Delete the DBD from the list.

Name of the DBD in the exception list. Databases for the DBD names specified in the exception list are treated as exceptions to the Audit Trail mode indicated by

the ALL/NONE indicator on the previous panel (Figure 2-8 on page 2-7).

You can explicitly enter each exception DBD name in the exception list, or you can indicate DBD exception groups by entering only the characters that make up the common "prefix" for the DBDs in that group.

To disable the Audit Trail feature at your installation, leave the ALLNONE indicator as N, and do not specify any DBD names in the exception list.

13. Enter the END primary command (PF3).

The File-AID for IMS – Generate Install JCL screen is displayed (Figure 2-10 on page

2-9).

Note: Option 1 (EDIT JCL) or Option 2 (SAVE JCL) saves your installation JCL in

your installation library member @FDIPRM.


2-9

Figure 2-10. File-AID for IMS – Generate Install JCL Screen (@FDIPRM)

INSTALL ------------------ File-AID for IMS - Generate Install JCL ------------

OPTION ===>

1 EDIT JCL - to edit the generated JCL

2 SAVE JCL - to save JCL in ’XXXXXXX.FID.V7R5M0.INSTALL(@FDIPRM)’

3 SUBMIT - to submit batch job without review

Specify batch JCL information:

SYSOUT CLASS ===> *

JOB statement information:

===> //PFHTSO0A JOB (ACCT),'PGMR.NAME',CLASS=A,

===> // MSGCLASS=X,NOTIFY=PFHTSO0,REGION=4M

===> //*

===> //*

Enter END to exit without submitting batch job

14. After reviewing your JCL, save it (Option 2) and then submit it (Option 3).

2-10


Step 4. Assemble and Link MFS Source Code

Use the JCL already in place and link File-AID for IMS’s MFS source code into the IMS format library,

or

1. Select option 2, MFS, from the File-AID for IMS/DC Installation Menu.

The File-AID for IMS/DC MFS screen is displayed (Figure 2-11).

Figure 2-11. File-AID for IMS/DC MFS Screen

INSTALL ------------- File-AID for IMS/DC MFS ---------------------------------

COMMAND ===>

Specify your IMS RESLIB, MFS Referral library, MFS Format library and the option al SYSLIB source dataset to assemble and link the MFS source code into your MF

S Format library.

IMS RESLIB ===> 'IMS810A.SDFSRESL'

MFS REFERRAL LIB ===> 'IMS810A.REFERAL'

MFS FORMAT LIB ===> 'IMS810A.TFOMAT'

SYSLIB (optional) ===> 'IMS810A.SDFSMAC'

2. Enter the fully qualified dataset name for your IMS RESLIB, MFS referral, and MFS format libraries.

Optionally, specify your SYSLIB source dataset.

3. Press Enter.


2-11).


your installation library member @FDMFS.


2-11

Figure 2-12. File-AID for IMS – Generate Install JCL Screen (@FDMFS)


OPTION ===>


2 SAVE JCL - to save JCL in ’XXXXXXX.FID.V7R5M0.INSTALL(@FDMFS)’



SYSOUT CLASS ===> *




===> //*

===> //*



Figure 2-13 on page 2-12 and Figure 2-14 on page 2-13 show an example of the generated

JCL to assemble and link-edit the MFS source modules into your IMS format library.

2-12


Figure 2-13. Example of JCL to Link-Edit the MFS Modules, Part 1 ,JCL to Linkedit the MFS

Modules

//PFHTSO0A JOB (ACCT),'PGMR.NAME',CLASS=A,

// MSGCLASS=X,NOTIFY=PFHTSO0,REGION=4M

//*

//*

//*____________________________________________________________________

//* |

//*

//*

C O M P U W A R E C O R P O R A T I O N |

|

//*

//*

F I L E - A I D F O R I M S / D C |

|

//* S Y S T E M I N S T A L L A T I O N |

//* ------------------------------------------------------------------|

//*

//*

//* STEP

//* ----

//*

//*

1

FUNCTION

ASSEMBLE MFS SOURCE

|

|

|

-----------------------------------------------------------|

|

|

//*

//*

2 LINKEDIT MFS MODULES INTO YOUR IMS FORMAT LIBRARY |

|

//*___________________________________________________________________|

//*

//IXDPROC4 PROC DEV=SYSDA,

// PRINT='*',

//

//*

MBR=,

SYSTEM DISK WORK UNIT

SYSOUT PRINT CLASS

MFS SOURCE CODE MEMBER

//*** FILE-AID FOR IMS/DC SOURCE LIBRARY

// SRCDSN='XXXXXXX.FID.V7R5M0.DCSRCE',

//*** YOUR IMS RESLIB

// RESLIB='IMS810A.SDFSRESL',

//*** YOUR MFS REFERRAL LIBRARY

// REFERAL='IMS810A.REFERAL',

//*** YOUR MFS FORMAT LIBRARY

// FORMAT='IMS810A.FORMAT',

//*

//

//

//

PXREF=XREF,

PCOMP=NOCOMP,

PSUBS=NOSUBS,

PDIAG=NODIAG,

REFER TO THE MFS USER'S

GUIDE FOR THE REMAINING

PARAMETERS

//

//

//

//

COMPR=NOCOMPRESS,

LN='LINECNT=55',

SN='STOPRC=8',

DC='DEVCHAR=A' //

//*

//*--------------------------------------------------------------------

//* STEP1: ASSEMBLE MFS SOURCE MODULE

//*--------------------------------------------------------------------

//*

//STEP1

//

EXEC PGM=DFSUPAA0,

PARM='&PXREF,&PCOMP,&PSUBS,&PDIAG,&COMPR,&LN,&SN,&DC'

//STEPLIB

//SYSIN

//REFIN

//REFOUT

//

//REFRD

//

//SYSTEXT

DD DSN=&RESLIB,DISP=SHR

DD DSN=&SRCDSN(&MBR),DISP=SHR

DD DSN=&REFERAL,DISP=OLD

DD DSN=&&TEMPPDS,

UNIT=&DEV,SPACE=(CYL,(5,1,10))

DD DSN=*.REFOUT,VOL=REF=*.REFOUT,DISP=(OLD,DELETE)

DD DSN=&REFERAL,DISP=OLD

DD DSN=&&TXTPASS,UNIT=&DEV,

//

//SYSUT3

SPACE=(CYL,(1,1)),DCB=BLKSIZE=800

DD UNIT=&DEV,SPACE=(CYL,(1,1))

//SYSUT4 DD UNIT=&DEV,SPACE=(CYL,(1,1))

//SYSPRINT DD SYSOUT=&PRINT,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330)

//SYSUDUMP DD SYSOUT=&PRINT

//SEQBLKS DD DSN=&&BLKS,DISP=(NEW,PASS),

//

//*

UNIT=&DEV,SPACE=(CYL,(1,1))

//*--------------------------------------------------------------------

//* STEP2: LINKEDIT MFS MODULES INTO IMS FORMAT LIBRARY

//*--------------------------------------------------------------------

//*


2-13

Figure 2-14. Example of JCL to Link-Edit the MFS Modules, Part 2

//*

//IXD06

//

//*

//IXD07

//

//*

//IXD08

//

//*

//IXD09

//

//*

//IXD10

//

//*

//IXD11

//

//

//IXD12

//

//*

//IXD13

//

//*

//STEP2

//

//STEPLIB

//SEQBLKS

EXEC PGM=DFSUNUB0,

COND=(8,LT,STEP1)


DD DSN=&&BLKS,DISP=(OLD,DELETE)

//UTPRINT DD SYSOUT=&PRINT,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330)

//SYSUDUMP DD SYSOUT=&PRINT

//FORMAT

//SYSUT3

DD DSN=&FORMAT,DISP=SHR


DD UNIT=&DEV,SPACE=(CYL,(1,1)) //SYSUT4

//*

//

//*

PEND

//*--------------------------------------------------------------------

//* FILE-AID FOR IMS/DC SUPPORTS SEVERAL DEVICE TYPES (REFER TO THE

//*

//*

INSTALLATION GUIDE FOR MORE INFORMATION).

YOU MAY HAVE TO

DELETE OR COMMENT OUT CERTAIN DEVICE TYPES IN THE MFS SOURCE

//*

//*

//*

//*

CODE OF THE MEMBERS BELOW.

IF YOUR INSTALLATION DOES NOT HAVE

ALL OF THE SUPPORTED DEVICE TYPES DEFINED, THE MFS SOURCE CODE

WILL NOT COMPILE CORRECTLY UNTIL YOU DELETE OR COMMENT OUT THE

UNDEFINED DEVICE TYPES.

//*--------------------------------------------------------------------

//*

//IXD01

//

EXEC IXDPROC4,

MBR='IXDABND'

//*

//IXD02

//

//*

EXEC IXDPROC4,

MBR='IXDCHR'

EXEC IXDPROC4,

MBR='IXDDBD'

//IXD03

//

//*

//IXD04

//

//*

//IXD05

//

EXEC IXDPROC4,

MBR='IXDFMT'

EXEC IXDPROC4,

MBR='IXDHEX'

EXEC IXDPROC4,

MBR='IXDINX'

EXEC IXDPROC4,

MBR='IXDKEY'

EXEC IXDPROC4,

MBR='IXDLOC'

EXEC IXDPROC4,

MBR='IXDMENU'

EXEC IXDPROC4,

MBR='IXDCPYRT'

EXEC IXDPROC4,

MBR='IXDLMS'

EXEC IXDPROC4,

MBR='IXDTFMT'

EXEC IXDPROC4,

MBR='IXDVKEY'

Step 5. Modify DBD Source Code

1. Modify the DBD source code for File-AID for IMS’ control databases to conform to your installation’s specifications. Each member—IXDLTM, IXDCLT, and IXDAUD— should be updated identically except where noted.

2-14


DBD NAME=IXDLTM,ACCESS=(HDAM,VSAM),RMNAME=(DFSHDC40,1,30,8177)

DBD NAME=IXDCLT,ACCESS=(HDAM,VSAM),RMNAME=(DFSHDC40,1,50,8177)

DBD NAME=IXDAUD,ACCESS=(HDAM,VSAM),RMNAME=(DFSHDC40,16,250,8117)

NAME=IXDLTM

NAME=IXDCLT

NAME=IXDAUD

(for the LTM database)

(for the CLT database)

(for the AUD database

If necessary, modify these names to meet your installation’s DBD naming conventions.

ACCESS=(HDAM,VSAM) (same for all control databases)

Compuware recommends that the control databases be organized as VSAM datasets because of their large segment sizes. However, if your installation wants to allocate them as OSAM datasets, change the second parameter to OSAM. Do not change the access method (first parameter).

RMNAME=(DFSHDC40,1,30,8177)

RMNAME=(DFSHDC40,1,50,8177)



RMNAME=(DFSHDC40,16,250,8117) (for the AUD database)

Substitute the RBNs calculated in “DBD Tailoring” on page 1-4 for the third

parameters. Substitute the RMNAME BYTES calculated earlier for the fourth parameters. The RMNAME BYTES parameter must be the same for the LTM and CLT databases. Do not change the randomizer name (first parameter) or the RAPs per CI

(second parameter).

2. Modify the following:

DATASET DD1=IXDLTMDD,DEVICE=3380,SIZE=8192 (for the LTM database)

DATASET DD1=IXDCLTDD,DEVICE=3380,SIZE=8192 (for the CLT database)

DATASET DD1=IXDAUDDD,DEVICE=3380,SIZE=8192 (for the AUD database)

DD1=IXDLTMDD

DD1=IXDCLTDD

DD1=IXDAUDDD



(for the AUD database)

If necessary, modify these names to meet your installation’s DDNAME conventions.

DEVICE=3380 (same for all control databases)

Change the device to the type used at your installation.

SIZE=8192 (same for LTM and CLT databases; AUD database can vary)

Find the row that corresponds to your installation’s Maximum User DB Segment

Length (for the LTM and CLT databases) or Maximum User DB Segment Plus Concat

Key Length (for the AUD database) in the tables shown in “DBD Tailoring” on page

1-4. Substitute the appropriate number from the CI/BLOCK column for the SIZE

parameter.

3. Find the row that corresponds to your installation’s Maximum User DB Segment

Length (for the LTM and CLT databases) or Maximum User DB Segment Plus Concat

Key Length (for the AUD database) in the tables shown in “DBD Tailoring” on page

1-4. Substitute the appropriate number from the Segm Bytes column for the

corresponding BYTE operand. Substitute this same number in all the SEGM statements in the appropriate control database DBDs. Each control database DBD must have the same maximum segment size on all its SEGM statements. Do not change the NAME=, PARENT=, PTR=, or the segment minimum size parameters.


2-15

SEGM NAME=GV,PARENT=0,BYTES=(8158,10),PTR=TWIN

BYTES=(8158,10) (same for all LTM and CLT control database segments)

BYTES=(8102,48) (same for all AUD control database segments)

DBD Samples

DBD Samples

Following are samples of the LTM, CLT, and AUD control database DBDs.

Figure 2-15, Figure 2-16, and Figure 2-17 on page 2-16 are examples of an LTM control

database DBD, a CLT control database DBD, and an AUD control database DBD, respectively.

Figure 2-15. LTM DBD Example ff

PRINT

DBD

NOGEN

NAME=IXDLTM,ACCESS=(HDAM,VSAM),RMNAME=(DFSHDC40,1,30,8177)

DATASET DD1=IXDLTMDD,DEVICE=3380,SIZE=8192

SEGM

FIELD

SEGM

FIELD

NAME=GV,PARENT=0,BYTES=(8158,10),PTR=TWIN

NAME=(GVKEY,SEQ,U),BYTES=8,START=3

NAME=PS,PARENT=((GV,SNGL)),BYTES=(8158,7),PTR=TWIN

NAME=(PSKEY,SEQ,U),BYTES=5,START=3

SEGM

FIELD

SEGM

FIELD

DBDGEN

FINISH

END

NAME=WA,PARENT=((GV,SNGL)),BYTES=(8158,5),PTR=TWIN

NAME=(WAKEY,SEQ,U),BYTES=3,START=3

NAME=ST,PARENT=((GV,SNGL)),BYTES=(8158,54),PTR=TWIN

NAME=(STKEY,SEQ,U),BYTES=52,START=3

Figure 2-16. CLT DBD Example

PRINT

DBD

NOGEN

NAME=IXDCLT,ACCESS=(HDAM,VSAM),RMNAME=(DFSHDC40,1,50,8177)

DATASET DD1=IXDCLTDD,DEVICE=3380,SIZE=8192

SEGM

FIELD

FIELD

FIELD

FIELD

NAME=DCLT,PARENT=0,BYTES=(8158,60),PTR=TWIN

NAME=(DCLTKEY,SEQ,U),BYTES=52,START=5

NAME=(CLTSRCH),BYTES=84,START=85

NAME=(PRTKEY11),BYTES=11,START=5

NAME=(PRTKEY19),BYTES=19,START=5

DBDGEN

FINISH

END

2-16


Figure 2-17. AUD DBD Example

PRINT

DBD

NOGEN

NAME=IXDAUD,ACCESS=(HDAM,VSAM),RMNAME=(DFSHDC40,16,250,8117)

DATASET DD1=IXDAUDDD,DEVICE=3380,SIZE=8192

SEGM

FIELD

SEGM

LAST)

NAME=AT,PARENT=0,BYTES=(8102,48),PTR=TWIN

NAME=(ATKEY,SEQ,U),BYTES=37,START=3

NAME=ATDEP,PARENT=((AT,DBLE)),BYTES=(8102,8),PTR=TWIN,RULES=(,

DBDGEN

FINISH

END

Step 6. Assemble DBD Source Code

Submit DBDGENs for the databases using JCL already in place at your installation,

or

1. Select option 3, DBD, from the File-AID for IMS/DC Installation Menu.

The File-AID for IMS/DC DBD Generate screen is displayed (Figure 2-18).

Figure 2-18. File-AID for IMS/DC DBD Generate Screen

INSTALL ------------- File-AID for IMS/DC DBD Generate ------------------------

COMMAND ===>

Specify your Macro library, IMS RESLIB and DBD library to assemble and link DBDs required for the two control databases and the sample databases.

The audit trail database DBD will be included if you are using this feature.

MACRO LIBRARY

IMS RESLIB

IMS DBD LIBRARY

===> 'IMS810A.SDFSMAC'

===>

===>

If you modified the DBD names to satisfy your installation standards, enter the new DBD member names otherwise leave blank.

DBD MEMBER NAME

IXDCLT

IXDLTM

IXDAUD

PCUST

PORDR

PPART

LCUST

LORDR

===>

===>

===>

===>

===>

===>

===>

===>

NEW DBD MEMBER NAME

2. Enter the fully qualified dataset name for your Macro library, IMS RESLIB, and IMS

DBD library.

Only if you modified the DBD names to satisfy your installation standards, enter the new DBD member names; otherwise, leave blank.


2-17

3. Press Enter.

The File-AID for IMS – Generate Install JCL screen is displayed (Figure 2-19).


your installation library member @FDDBD.

Figure 2-19. File-AID for IMS – Generate Install JCL Screen (@FDDBD)


OPTION ===>


2 SAVE JCL - to save JCL in ’XXXXXXX.FID.V7R5M0.INSTALL(@FDDBD)’



SYSOUT CLASS ===> *




===> //*

===> //*



Figure 2-20 on page 2-18 and Figure 2-21 on page 2-19 show an example of the generated

JCL to assemble and link-edit the DBD source modules into the DBD library.

2-18


Figure 2-20. Example of JCL to Link-Edit the DBD Source Modules, Part 1



//*

//*

//*____________________________________________________________________

//* |

//*

//*


|

//*

//*


|


//* ------------------------------------------------------------------|

//*

//*

//* STEP

//* ----

//*

//*

1

FUNCTION

ASSEMBLE DBD SOURCE MODULE

|

|

|

-----------------------------------------------------------|

|

|

//*

//*

2 LINKEDIT MODULE TO DBD LIBRARY |

|

//*___________________________________________________________________|

//*


// PRINT='*',

//

//*


SYSOUT PRINT CLASS

//*


SRCDSN='XXXXXXX.FID.V7R5M0.DCSRCE',

//*** YOUR MACRO LIBRARY

// SYSLIB='IMS810A.SDFSMAC',



//*** YOUR IMS DBD LIBRARY

// DBDLIB='IMS810A.DBDLIB',

//

//

SRCMBR=,

MBR=

SOURCE MEMBER NAME

DBD MEMBER NAME

//*

//*--------------------------------------------------------------------

//* STEP1: ASSEMBLE DBD SOURCE MODULE

//*--------------------------------------------------------------------

//*

//STEP1

//

//SYSLIB

//SYSUT1

//

//

//SYSLIN

//

//

//

EXEC PGM=IEV90,

PARM='NODECK,LOAD'

DD DSN=&SYSLIB,DISP=SHR

DD DSN=&&SYSUT1,

UNIT=(&DEV,SEP=SYSLIB),

SPACE=(CYL,(10,5))

DD DSN=&&OBJMOD,

DISP=(NEW,PASS),

UNIT=&DEV,SPACE=(80,(100,100,0)),

DCB=(BLKSIZE=0,LRECL=80,RECFM=FB)

//SYSPRINT DD SYSOUT=&PRINT

//SYSPUNCH DD DUMMY

//SYSIN DD DSN=&SRCDSN(&SRCMBR),

//

//*

DISP=SHR

//*--------------------------------------------------------------------

//* STEP2: LINKEDIT DBD TO YOUR DBD LIBRARY

//*--------------------------------------------------------------------

//*

//STEP2 EXEC PGM=DFSILNK0,PARM='XREF,LIST',COND=(4,LT,STEP1)

//STEPLIB DD DSN=&RESLIB,

//

//SYSLIN DD

DISP=SHR

DSN=&&OBJMOD,DISP=(OLD,DELETE)


//SYSLMOD DD DSN=&DBDLIB(&MBR),

//

//SYSUT1 DD

DISP=SHR

UNIT=&DEV,

//

//

//*

//

//*

PEND

SPACE=(1024,(100,10),RLSE),

DISP=(,DELETE)


2-19

Figure 2-21. Example of JCL to Link-Edit the DBD Source Modules, Part 2

//PPART

//

//

//*

//LCUST

//

//

//*

//LORDR

//

//

//*

//IXDAUD

//

//

//*

//

//IXDCLT

//

//

//*

//IXDLTM

//

//

//*

//PCUST

//

//

//*

//PORDR

//

//

//*

EXEC IXDPROC5,

SRCMBR=IXDCLT,

MBR=IXDCLT

EXEC IXDPROC5,

SRCMBR=IXDLTM,

MBR=IXDLTM

EXEC IXDPROC5,

SRCMBR=PCUST,

MBR=PCUST

EXEC IXDPROC5,

SRCMBR=PORDR,

MBR=PORDR

EXEC IXDPROC5,

SRCMBR=PPART,

MBR=PPART

EXEC IXDPROC5,

SRCMBR=LCUST,

MBR=LCUST

EXEC IXDPROC5,

SRCMBR=LORDR,

MBR=LORDR

EXEC IXDPROC5,

SRCMBR=IXDAUD,

MBR=IXDAUD

Step 7. Modify PSBs

Modify the Program Specification Blocks (PSBs) as required by your installation’s configuration. The first six PCBs in the PSB (including the optional Audit Trail PCB) are for File-AID for IMS’s use. PCBs 7 through 500 are for your user databases. Compuware recommends that you include the four sample database PCBs in your PSB for the initial installation. Source library member IXDMAIN contains these sample databases PCBs.

PCB number one is used for message switching between functions. The transaction name in the PCB must be the same as the transaction name that uses this PSB. Change the

NAME= operand of the PCB macro accordingly. Refer to “PSB Tailoring” on page 1-6 for

more information.

Note: If the Audit Trail feature is to be activated, you must uncomment the IXDAUD

PCB.

Figure 2-22 on page 2-20 shows a PSB example.

2-20


Figure 2-22. Program Specification Block (PSB) Example

PRINT NOGEN

PCB TYPE=TP,NAME=FILEAID

PCB TYPE=DB,DBDNAME=IXDCLT,KEYLEN=52,PROCOPT=A,POS=S

SENSEG NAME=DCLT,PARENT=0

PCB TYPE=DB,DBDNAME=IXDLTM,KEYLEN=60,PROCOPT=A,POS=S

SENSEG NAME=GV,PARENT=0

SENSEG NAME=PS,PARENT=GV

SENSEG NAME=WA,PARENT=GV

SENSEG NAME=ST,PARENT=GV

PCB TYPE=DB,DBDNAME=IXDLTM,KEYLEN=60,PROCOPT=A,POS=S





PCB TYPE=DB,DBNAME=IXDLTM,KEYLEN=60,PROCOPT=A,POS=S





PCB TYPE=DB,DBDNAME=IXDAUD,KEYLEN=37,PROCOPT=A,POS=S

SENSEG NAME=AT,PARENT=0

SENSEG NAME=ATDEP,PARENT=AT add user database PCBs here

PCB TYPE=DB,...

.

.

.

PSBGEN LANG=PL/I,COMPAT=YES,PSBNAME=IXDMAIN

END

Step 8. Assemble PSB Source Code

In this step, PSB control blocks are generated for the PSBs needed for your installation configuration and the PSBs in the source dataset members IXDDLET, IXDLOAD, and

IXDUPLD.

Submit PSBGENs for these PSBs using JCL already in place at your installation,

or

1. Select option 4, PSB, from the File-AID for IMS/DC Installation Menu.

The File-AID for IMS/DC PSB Generate screen is displayed (Figure 2-23 on page 2-21).


2-21

Figure 2-23. File-AID for IMS/DC PSB Generate Screen

INSTALL ------------- File-AID for IMS/DC PSB Generate ------------------------

COMMAND ===>

Specify your Macro library, IMS RESLIB and PSB library to assemble and link

PSBs needed for your installation configuration.

If you are using the audit trail feature, then modify the four PSB members

IXDDLET, IXDMAIN, IXDLOAD and IXDUPLD and uncomment the IXDAUD PCB.

MACRO LIBRARY

IMS RESLIB

PSB LIBRARY

===> 'IMS810A.SDFSMAC'

===> 'IMS810A.SDFSRESL'

===>

If you modified the PSB names to satisfy your installation standards, enter the new PSB member names otherwise leave blank.

PSB MEMBER NAME

IXDDLET

IXDLOAD

IXDMAIN

IXDUPLD

===>

===>

===>

===>

NEW PSB MEMBER NAME

2. Enter the fully qualified dataset name for your Macro library, IMS RESLIB, and PSB library.

3. Press Enter.



your installation library member @FDPSB.

Figure 2-24. File-AID for IMS – Generate Install JCL Screen (@FDPSB)


OPTION ===>


2 SAVE JCL - to save JCL in ’XXXXXXX.FID.V7R5M0.INSTALL(@FDPSB)’



SYSOUT CLASS ===> *




===> //*

===> //*



Figure 2-25 on page 2-22 and Figure 2-26 on page 2-23 show an example of the

generated JCL to assemble and link-edit the PSB source modules into the PSB library.

2-22


Figure 2-25. Example of JCL to Assemble and Link-Edit PSB Source Modules, Part 1



//*

//*

//*____________________________________________________________________

//* |

//*

//*


|

//*

//*


|


//* ------------------------------------------------------------------|

//*

//*

//* STEP

//* ----

//*

//*

1

FUNCTION

ASSEMBLE PSB SOURCE MODULE

|

|

|

-----------------------------------------------------------|

|

|

//*

//*

2 LINKEDIT MODULE TO YOUR PSB LIBRARY |

|

//*___________________________________________________________________|

//*


// PRINT='*',

//

//*


SYSOUT PRINT CLASS

//*


SRCDSN='XXXXXXX.FID.V7R5M0.DCSRCE',

//*** YOUR MACRO LIBRARY

// SYSLIB='IMS810A.SDFSMAC',



//*** YOUR IMS PSB LIBRARY

// PSBLIB='IMS810A.PSBLIB',

//

//

SRCMBR=,

MBR=

SOURCE MEMBER NAME

PSB MEMBER NAME

//*

//*--------------------------------------------------------------------

//* STEP1: ASSEMBLE PSB SOURCE MODULE

//*--------------------------------------------------------------------

//*

//STEP1

//

//SYSLIB

//SYSUT1

//

//

//SYSLIN

//

//

//

EXEC PGM=IEV90,

PARM='NODECK,LOAD'

DD DSN=&SYSLIB,DISP=SHR

DD DSN=&&SYSUT1,

UNIT=(&DEV,SEP=SYSLIB),

SPACE=(CYL,(10,5))

DD DSN=&&OBJMOD,

DISP=(NEW,PASS),

UNIT=&DEV,SPACE=(80,(100,100,0)),

DCB=(BLKSIZE=0,LRECL=80,RECFM=FB)


//SYSPUNCH DD DUMMY

//SYSIN DD DSN=&SRCDSN(&SRCMBR),

//

//*

DISP=SHR

//*--------------------------------------------------------------------

//* STEP2: LINKEDIT PSB TO YOUR PSB LIBRARY

//*--------------------------------------------------------------------

//*

//STEP2 EXEC PGM=DFSILNK0,PARM='XREF,LIST',COND=(4,LT,STEP1)


//

//SYSLIN DD

DISP=SHR

DSN=&&OBJMOD,DISP=(OLD,DELETE)


//SYSLMOD DD DSN=&PSBLIB(&MBR),

// DISP=SHR


2-23

Figure 2-26. Example of JCL to Assemble and Link-Edit PSB Source Modules, Part 2

//SYSUT1

//

//

//*

DD UNIT=&DEV,

SPACE=(1024,(100,10),RLSE),

DISP=(,DELETE)

//

//*

//IXDIXD

//

PEND

EXEC IXDPROC6,

SRCMBR=IXDIXD,

MBR=IXDIXD //

//*

//IXDDLET EXEC IXDPROC6,

// SRCMBR=IXDDLET,

//

//STEP2

MBR=IXDDLET

EXEC PGM=DFSILNK0,PARM='XREF,LIST',COND=(4,LT,STEP1)


// DISP=SHR

//SYSLIN DD DSN=&&OBJMOD,DISP=(OLD,DELETE)


//SYSLMOD DD DSN=&PSBLIB(&MBR),

// DISP=SHR

//SYSUT1

//

//

//*

DD UNIT=&DEV,

SPACE=(1024,(100,10),RLSE),

DISP=(,DELETE)

//

//*

//IXDIXD

//

PEND

EXEC IXDPROC6,

SRCMBR=IXDIXD,

MBR=IXDIXD //

//*

//IXDDLET EXEC IXDPROC6,

// SRCMBR=IXDDLET,

// MBR=IXDDLET //*

//IXDLOAD EXEC IXDPROC6,

//

//

SRCMBR=IXDLOAD,

MBR=IXDLOAD

//*

//IXDUPLD EXEC IXDPROC6,

//

//

SRCMBR=IXDUPLD,

MBR=IXDUPLD

//*

//

Step 9. Generate ACB Control Blocks

1. Select option 5, ACB, from the File-AID for IMS/DC Installation Menu.

The File-AID for IMS/DC ACB Generate screen is displayed (Figure 2-27 on page

2-24).

2-24


Figure 2-27. File-AID for IMS/DC ACB Generate Screen

INSTALL ------------- File-AID for IMS/DC ACB Generate ------------------------

COMMAND ===>

Specify your IMS RESLIB, DBD library, PSB library and ACB library to generate

ACB control blocks for your installation configuration and for File-AID for

IMS/DC BMP upload programs IXPXRFUP and IXPDBDDUP.

IMS RESLIB

DBD LIBRARY

PSB LIBRARY

ACB LIBRARY


===>

===>

===>

2. Enter the fully qualified dataset name for your IMS RESLIB and DBD, PSB, and ACB libraries.

3. Press Enter.



your installation library member @FDACB.

Figure 2-28. File-AID for IMS – Generate Install JCL Screen (@FDACB)


OPTION ===>


2 SAVE JCL - to save JCL in ’XXXXXXX.FID.V7R5M0.INSTALL(@FDACB)’



SYSOUT CLASS ===> *




===> //*

===> //*



Figure 2-29 on page 2-25 shows an example of the generated JCL to generate the

access control block.


2-25

Figure 2-29. Example of JCL to Link File-AID for IMS/DC Load Library



//*

//*

//*____________________________________________________________________

//* |

//*

//*


|

//*

//*


|


//* ------------------------------------------------------------------|

//*

//*

//* STEP

//* ----

//*

//*

1

FUNCTION

GENERATE ACCESS CONTROL BLOCK

|

|

|

-----------------------------------------------------------|

|

|

//*___________________________________________________________________|

//*

//IXDPROC7 PROC PRINT='*',

//*

SYSOUT PRINT CLASS



//*** YOUR DC DBD LIBRARY


//*** YOUR DC PSB LIBRARY


//*** YOUR DC ACB LIBRARY

// ACBLIB='IMS810A.ACBLIB'

//*

//*--------------------------------------------------------------------

//* STEP1: GENERATE ACCESS CONTROL BLOCK

//*--------------------------------------------------------------------

//*

//STEP1 EXEC PGM=DFSRRC00,PARM='UPB'


// DISP=SHR

//DFSRESLB DD DSN=&RESLIB,

// DISP=SHR


//IMS

//

DD DSN=&DBDLIB,

DISP=SHR

//

//

//IMSACB

//

DD DSN=&PSBLIB,

DISP=SHR

DD DSN=&ACBLIB,

DISP=SHR

//*

// PEND

//*

//IXDIXD EXEC IXDPROC7

//STEP1.SYSIN

DD *

BUILD PSB=IXDIXD

/*

//*

//IXDUPLD EXEC IXDPROC7

//STEP1.SYSIN

DD *

BUILD PSB=IXDUPLD

/*

//*

//

2-26


Step 10. Allocate Control Databases

1. Select option 6, CONTROL DB, from the File-AID for IMS/DC Installation Menu.

The File-AID for IMS/DC Allocate Control Database screen is displayed (Figure 2-30).

Figure 2-30. File-AID for IMS/DC Allocate Control Database Screen

INSTALL ------------- File-AID for IMS/DC Allocate control database------------

COMMAND ===>

Specify information to allocate the two control databases and the audit trail database datasets. You can choose to allocate these datasets as VSAM or OSAM.

ALLOCATION TYPE

IMS RESLIB

DBD LIBRARY

PSB LIBRARY

IMS PROC LIBRARY

MEMBER NAME

===> V (V = VSAM, O = OSAM)


===>

===>

===>

===> DFSVSAMP (Member containing buffer pool data)

If you modified the CLT, LTM or AUD database DBD member names or DD names, enter the new DBD member names and DD names otherwise leave blank.

CONTROL DATABASE DBD

IXDCLT

NEW DBD MEMBER NAME NEW DD NAME

IXDLTM

IXDAUD

Specify control database dataset names and audit trail dataset name:

CLT Database ===> IXCCLT

LTM Database

AUD Database

===> IXCLTM

===> IXCAUD

2. Specify to allocate the control database datasets either as VSAM (V) or OSAM (O).

3. Enter the fully qualified dataset name for your IMS RESLIB and DBD, PSB, and PROC libraries.

4. Enter the fully qualified dataset name for your CLT, LTM, and AUD databases.

5. Press Enter.

For VSAM allocation type, the File-AID for IMS VSAM Control Database screen is

displayed (Figure 2-31 on page 2-27). For OSAM allocation type, the File-AID for IMS

– Generate Install JCL screen is displayed (Figure 2-32 on page 2-27).


2-27

Figure 2-31. File-AID for IMS VSAM Control Database Screen

INSTALL ------------- File-AID for IMS/DC VSAM control database ---------------

COMMAND ===>

Specify IDCAMS information to allocate the control databases as VSAM:

RECORD SIZE

CI SIZE

LTM VOLUME

CLT VOLUME

AUD VOLUME

===> 8185

===> 8192

===>

===>

===>

Refer to the tables in chapter 1 DBD Tailoring in the installation guide for

RECORD SIZE and CI SIZE values. The VOLSER of the LTM, CLT and AUD databases can be different.

6. Enter and verify the requested record and CI sizes as well as the Volume serial numbers for LTM, CLT, and AUD datasets.

Note: The volume serial numbers can be different for the LTM, CLT, and AUD

datasets.

7. Press Enter.



your installation library member @FDALOCV for VSAM or @FDALOCO for

OSAM dataset types.

Figure 2-32. File-AID for IMS – Generate Install JCL Screen (@FDALOCV)


OPTION ===>


2 SAVE JCL - to save JCL in ’XXXXXXX.FID.V7R5M0.INSTALL(@FDALOCV)’



SYSOUT CLASS ===> *




===> //*

===> //*


2-28



Figure 2-33 through Figure 2-35 on page 2-30 show an example of the generated JCL to

Allocate File-AID for IMS/DC VSAM control databases.

Figure 2-33. Example JCL, Allocate File-AID for IMS/DC VSAM Control Databases, Part 1



//*

//*

//*____________________________________________________________________

//* |

//*

//*


|

//*

//*


|


//* ------------------------------------------------------------------|

//*

//*

//* STEP

//* ----

//*

//*

1

2

FUNCTION

ALLOCATE CONTROL DATA BASES VSAM

INITIALIZE CONTROL DATA BASES

|

|

|

-----------------------------------------------------------|

|

|

//*

//*

//*

//*

3 DELETE SEGMENTS INSERTED IN STEP 2

|

|

|

|

//*___________________________________________________________________|

//*


//*

SYSOUT PRINT CLASS







//*** YOUR DC PROC LIBRARY

// PROCLIB='IMS810A.PROCLIB',

//

//*

DFSVSAM='DFSVSAMP',

//*

MEMBER IN PROCLIB CONTAINING

BUFFER POOL DATA


2-29


//

//

//

//

//*** FILE-AID FOR IMS/DC CLT DATA BASE

// CLTDB='XXXXXXX.CLTDBD',

//*** FILE-AID FOR IMS/DC LTM DATA BASE

// LTMDB='XXXXXXX.LTMDBD',

//*

//

//*

//

LOADPSB='IXDLOAD',

DELPSB='IXDDLET',

INITIAL LOAD

PSB CREATED BY JCLPSB

INITIAL DELETE

PSB CREATED BY JCLPSB //*

//***

//

//

DFSRRC00 PARAMETERS ****

BUF=,SPIE=,TEST=,

EXCPVR=,RST=,PRLD=,

SRCH=,CKPTID=,MON=,

LOGA=,FMTO=,IMSID=,

SWAP=,DBRC=,IRLM=,

IRLMNM=

IMS REGION CONTROLLER PGM

PARAMETERS - FOR MORE INFO

ON THESE PARMS SEE THE

IMS/VS SYSTEM PROGRAMMING

REFERENCE MANUAL

//*

//*--------------------------------------------------------------------

//* STEP1: ALLOCATE FILE-AID FOR IMS/DC CONTROL DATA BASES VSAM

//*--------------------------------------------------------------------

//*

//STEP1 EXEC PGM=IDCAMS


//SYSIN

//*

DD DUMMY

//*--------------------------------------------------------------------

//* STEP2: INITIALIZE FILE-AID FOR IMS/DC CONTROL DATA BASES

//*--------------------------------------------------------------------

//*

//STEP2

//

//

//

EXEC PGM=DFSRRC00,

PARM=(DLI,DFSDDLT0,&LOADPSB,&BUF,

&SPIE&TEST&EXCPVR&RST,&PRLD,

&SRCH,&CKPTID,&MON,&LOGA,&FMTO,

// &IMSID,&SWAP,&DBRC,&IRLM,&IRLMNM),COND=(8,LT)

//STEPLIB DD DSN=&RESLIB,DISP=SHR

//DFSRESLB DD DSN=&RESLIB,DISP=SHR

//IMS DD DSN=&DBDLIB,DISP=SHR

// DD DSN=&PSBLIB,DISP=SHR

//DFSVSAMP DD DSN=&PROCLIB(&DFSVSAM),DISP=SHR

//IEFRDER DD DUMMY

//IXDCLTDD DD DSN=&CLTDB,DISP=OLD

//IXDLTMDD DD DSN=&LTMDB,DISP=OLD

//IXDAUDDD DD DSN=&AUDDB,DISP=OLD

//PRINTDD DD SYSOUT=&PRINT,DCB=BLKSIZE=121

//SYSIN DD DUMMY

//*

//*--------------------------------------------------------------------

//* STEP3: DELETE THE SEGMENTS INSERTED IN STEP 2

//*--------------------------------------------------------------------

//*

//STEP3

//

//

//

//

EXEC PGM=DFSRRC00,

PARM=(DLI,DFSDDLT0,&DELPSB,&BUF,



&IMSID,&SWAP,&DBRC,&IRLM,&IRLMNM),COND=(8,LT)






//IEFRDER DD DUMMY





//SYSIN DD DUMMY

//*

// PEND

//*

//IXDPROC8 EXEC IXDPROC8

//*

2-30



//*--------------------------------------------------------------------

//* FOLLOWING ARE THE IDCAMS CONTROL CARDS WHICH DELETE/DEFINE THE

//* FILE-AID FOR IMS/DC CONTROL DATA BASES. THE CLUSTER NAMES SHOULD

//* BE THE SAME AS THE DATASET NAMES SPECIFIED IN THE STARTUP JCL OR

//* DYNAMIC ALLOCATION MACROS.

//*--------------------------------------------------------------------

//*

//STEP1.SYSIN DD *

DELETE (XXXXXXX.CLTDBD)

IF MAXCC LE 8 +

PURGE CLUSTER

THEN SET MAXCC = 0

DEFINE CLUSTER (NAME(XXXXXXX.CLTDBD) +

CYL(1 1) VOL(898989) RECSZ(8185 8185) NONINDEXED SPEED +

CONTROLINTERVALSIZE(8192) UNIQUE) +

DATA (NAME(XXXXXXX.CLTDBD.DATA))

DELETE (XXXXXXX.LTMDBD) PURGE CLUSTER

IF MAXCC LE 8 +

THEN SET MAXCC = 0

DEFINE CLUSTER (NAME(XXXXXXX.LTMDBD) +



DATA (NAME(XXXXXXX.LTMDBD.DATA))

DELETE (XXXXXXX.AUDDBD)

IF MAXCC LE 8 +

PURGE CLUSTER

THEN SET MAXCC = 0

DEFINE CLUSTER (NAME(XXXXXXX.AUDDBD) +



DATA (NAME(XXXXXXX.AUDDBD.DATA))

/*

//*

//*--------------------------------------------------------------------

//* FOLLOWING ARE THE DFSDDLT0 CONTROL CARDS WHICH INITIALIZE THE

//* CONTROL DATA BASES.

//*--------------------------------------------------------------------

//*

//STEP2.SYSIN DD *

S 1 1 1 1 1 IXDCLT

L U0001 ISRT DCLT

L V0060 DATA

S 1 1 1 1 1 IXDLTM

L U0001 ISRT GV

L V0060 DATA

S 1 1 1 1 1 IXDAUD

L U0001 ISRT AT

L V0060 DATA

/*

//*

//*--------------------------------------------------------------------

//* FOLLOWING ARE THE DFSDDLT0 CONTROL CARDS WHICH DELETE SEGMENTS

//* INSERTED IN STEP2 FROM THE CONTROL DATA BASES.

//*--------------------------------------------------------------------

//*

//STEP3.SYSIN DD *

S 1 1 1 1 1 IXDCLT

L U

L U

GHU

DLET

DCLT

S 1 1 1 1 1

L

L

L

/*

//

U

U

U

GHU

L U DLET

S 1 1 1 1 1

GHU

DLET

IXDLTM

GV

IXDAUD

AT

Figure 2-36 on page 2-31 through Figure 2-38 on page 2-33 show an example of the JCL

when the dataset type is OSAM.


2-31

Figure 2-36. Example JCL, Allocate File-AID for IMS/DC OSAM Control Databases, Part 1



//*

//*

//*____________________________________________________________________

//* |

//*

//*


|

//*

//*


|


//* ------------------------------------------------------------------|

//*

//*

//* STEP

//* ----

//*

//*

1

2

FUNCTION

DELETE CONTROL DATA BASES OSAM

ALLOCATE CONTROL DATA BASES OSAM

|

|

|

-----------------------------------------------------------|

|

|

//*

//*

//*

//*

3 INITIALIZE CONTROL DATA BASES |

|

|

|

//*

//*

4 DELETE SEGMENTS INSERTED IN STEP 3 |

|

//*___________________________________________________________________|

//*


// DEV2='DISK',

//*


SYSOUT PRINT CLASS

PERMANENT FILE DEVICE






//*** YOUR DC PROC LIBRARY

//

//

PROCLIB='IMS810A.PROCLIB',

DFSVSAM='DFSVSAMP',

//*

//*


// CLTDB='XXXXXXX.CLTDBD',

MEMBER IN PROCLIB CONTAINING

BUFFER POOL DATA

//

//

//

//

//*** FILE-AID FOR IMS/DC LTM DATA BASE

// LTMDB='XXXXXXX.LTMDBD',

//*** FILE-AID FOR IMS/DC AUD DATA BASE

// AUDDB='XXXXXXX.AUDDBD',

//*

//

//*

//

LOADPSB='IXDLOAD',

DELPSB='IXDDLET',

INITIAL LOAD

PSB CREATED BY JCLPSB

INITIAL DELETE

PSB CREATED BY JCLPSB //*

//***

//

//

DFSRRC00 PARAMETERS ****

BUF=,SPIE=,TEST=,

EXCPVR=,RST=,PRLD=,

SRCH=,CKPTID=,MON=,

LOGA=,FMTO=,IMSID=,

SWAP=,DBRC=,IRLM=,

IRLMNM=





REFERENCE MANUAL

//*

//*

//*--------------------------------------------------------------------

//* STEP1: DELETE FILE-AID FOR IMS/DC CONTROL DATA BASES

//*--------------------------------------------------------------------

//*

//STEP1 EXEC PGM=IEFBR14

//IXDCLTDD DD DSN=&CLTDB,

//

//

//

//*

DISP=(MOD,DELETE),

UNIT=&DEV2,

SPACE=(TRK,(1))

2-32



//IXDLTMDD DD DSN=&LTMDB,

// DISP=(MOD,DELETE),

//

//

UNIT=&DEV2,

SPACE=(TRK,(1))

//*

//IXDAUDDD DD DSN=&AUDDB,

//

//

DISP=(MOD,DELETE),

UNIT=&DEV2,

// SPACE=(TRK,(1))

//*--------------------------------------------------------------------

//* STEP2: ALLOCATE FILE-AID FOR IMS/DC CONTROL DATA BASES OSAM

//*--------------------------------------------------------------------

//*


//IXDCLTDD DD DSN=&CLTDB,

//

//

DISP=(NEW,CATLG,DELETE),

UNIT=&DEV2,

//

//*

SPACE=(CYL,(1,1))

//IXDLTMDD DD DSN=&LTMDB,

// DISP=(NEW,CATLG,DELETE),

//

//

UNIT=&DEV2,

SPACE=(CYL,(6,1))

//IXDAUDDD DD DSN=&AUDDB,

// DISP=(NEW,CATLG,DELETE),

//

//

UNIT=&DEV2,

SPACE=(CYL,(6,1))

//*

//*--------------------------------------------------------------------

//* STEP3: INITIALIZE FILE-AID FOR IMS/DC CONTROL DATA BASES

//*--------------------------------------------------------------------

//*

//STEP3

//

//

//

//

EXEC PGM=DFSRRC00,

PARM=(DLI,DFSDDLT0,&LOADPSB,&BUF,









//IEFRDER DD DUMMY





//SYSIN DD DUMMY

//*

//*--------------------------------------------------------------------

//* STEP4: DELETE THE SEGMENTS INSERTED IN STEP 3

//*--------------------------------------------------------------------

//*

//STEP4

//

//

//

//

EXEC PGM=DFSRRC00,

PARM=(DLI,DFSDDLT0,&DELPSB,&BUF,









//IEFRDER DD DUMMY





//SYSIN DD DUMMY

//*

//

//*

PEND


2-33



//*

//*--------------------------------------------------------------------

//* FOLLOWING ARE THE DFSDDLT0 CONTROL CARDS WHICH INITIALIZE THE

//* CONTROL DATA BASES.

//*--------------------------------------------------------------------

//*

//STEP3.SYSIN DD *

S 1 1 1 1 1 IXDCLT

L U0001 ISRT DCLT

L V0060 DATA

S 1 1 1 1 1 IXDLTM

L U0001 ISRT GV

L V0060 DATA

S 1 1 1 1 1 IXDAUD

L U0001 ISRT AT

L V0060 DATA

/*

//*

//*--------------------------------------------------------------------

//* FOLLOWING ARE THE DFSDDLT0 CONTROL CARDS WHICH DELETE SEGMENTS

//* INSERTED IN STEP3 FROM THE CONTROL DATA BASES.

//*--------------------------------------------------------------------

//*

//STEP4.SYSIN DD *

S 1 1 1 1 1

L U

L U

GHU

DLET

IXDCLT

DCLT

IXDLTM

GV

S 1 1 1 1 1

L U

L U

GHU

DLET

S 1 1 1 1 1

L U

L U

GHU

DLET

/*

//

IXDAUD

AT

Step 11. Copy Training Files

1. Select option 7, TRAINING, from the File-AID for IMS/DC Installation Menu.

The File-AID for IMS/DC Training Files screen is displayed (Figure 2-39 on page 2-34).

2-34


Figure 2-39. File-AID for IMS/DC Training Files Screen

INSTALL ------------- File-AID for IMS/DC Training Files ----------------------

COMMAND ===>

Specify information for downloading new DC training files:

HIGH LEVEL NODE ===> PFHTSO0

UNIT FOR TRAINING FILES ===> SYSDA

Specify language preferred for updating the CLT control database:

LANGUAGE PREFERRED ===> COBOL (COBOL or PLI)

--------------------------------------------------------------------------------

The installation media contains three sample databases used for training and verification of proper installation.

The File-AID for IMS/DC CLT control database will be updated with DBD and

XREF information to allow access to the sample databases. LANGUAGE PREFERRED will use either the COBOL or PLI, XREF and layout sample libraries copied from the File-AID for IMS/ISPF install.

Warning: Libraries that exist will be replaced.

2. Specify the high-level qualifier and the unit where the training files should be copied to from the product media.

3. Enter either COBOL or PLI for the preferred language for the training files.

4. Press Enter.


Notes:

1. Option 1 (EDIT JCL) or Option 2 (SAVE JCL) saves your installation JCL in your installation library member @FDTRAIN.

2. The JCL generated will run using the default environment that was defined during the ISPF product installation.

Figure 2-40. File-AID for IMS – Generate Install JCL Screen (@FDTRAIN)


OPTION ===>


2 SAVE JCL - to save JCL in ’XXXXXXX.FID.V7R5M0.INSTALL(@FDTRAIN)’



SYSOUT CLASS ===> *




===> //*

===> //*




2-35

Figure 2-41 through Figure 2-44 on page 2-38 show an example of the generated JCL

to copy the training files.

Figure 2-41. Example of JCL to Copy Training Files, Part 1

//TSOUSERA JOB ('JOB ACCOUNT INFORMATION,262),'TSO USER ',

// CLASS=A,MSGCLASS=R,NOTIFY=TSOUSER

/*JOBPARM S=CW01

//*

//*____________________________________________________________________

//* |

//* C O M P U W A R E C O R P O R A T I O N |

//* |

//* F I L E - A I D F O R I M S / D C |

//* |


//* ------------------------------------------------------------------|

//* |

//* |

//* STEP FUNCTION |

//* ---- -----------------------------------------------------------|

//* 1 ALLOCATE TRAINING DATASETS |

//* 2-4 COPY TRAINING FILES FROM MEDIA |

//* 5 UPDATE CLT DATABASE WITH DBD INFORMATION |

//* 6 UPDATE CLT DATABASE WITH XREF INFORMATION |

//* |

//*___________________________________________________________________|

//*

//*------------------------------------------------------------

//IXDPROC9 PROC PRINT='*', SYSOUT PRINT CLASS

//*

//*** TRAINING CUSTOMER DATABASE

// DB1DSN='XXXXXXX.FIDSAMP.CUSTOMER',

//*** TRAINING ORDER DATABASE

// DB2DSN='XXXXXXX.FIDSAMP.ORDER',

//*** TRAINING PART DATABASE

// DB3DSN='XXXXXXX.FIDSAMP.PART',

//*

//*** PARAMETERS FOR STEP5 - DBDUPDLI AND STEP6 - XRFUPDLI

//*//*** YOUR IMS RESLIB


//*** YOUR IMS DBD LIBRARY

// DBDLIB='XXXXXXX.FIDSAMP.DBDLIB',

//*** YOUR IMS PSB LIBRARY

// PSBLIB='XXXXXXX.FIDSAMP.PSBLIB',

//*** YOUR IMS PROC LIBRARY

// PROCLIB='IMS810A.PROCLIB',

// DFSVSAM='DFSVSAMP', MEMBER IN PROCLIB CONTAINING

//* BUFFER POOL DATA

//*


// IXPDB='XXXXXXX.IXCCLT',

//*** FILE-AID FOR IMS/ISPF MESSAGE LIBRARY

// MLIBDSN='XXXXXXX.V7R5M0.ISPMLIB',

//*** File-AID for IMS/ISPF LOAD LIBRARY

// IXPLOAD='XXXXXXX.V7R5M0.LOAD',

//*** File-AID for IMS/ISPF COBOL XREFS

// XRFCDSN='XXXXXXX.FIDSAMP.XREFC',

//*** File-AID for IMS/ISPF COBOL LAYOUTS

// CBLDSN='XXXXXXX.FIDSAMP.COBOLLIB',

//*

//* **** DFSRRC00 PARAMETERS ****

//*

// PSB='IXDUPLD', PSB NAME

// BUF=,SPIE=,TEST=, IMS REGION CONTROLLER PGM

// EXCPVR=,RST=,PRLD=, PARAMETERS - FOR MORE INFO

// SRCH=,CKPTID=,MON=, ON THESE PARMS SEE THE

// LOGA=,FMTO=,IMSID=, IMS/VS SYSTEM PROGRAMMING

// SWAP=,DBRC=,IRLM=, REFERENCE MANUAL

// IRLMNM=

//*

2-36



//*-----------------------------------------------------------------

//* STEP1: ALLOCATE FILE-AID FOR IMS/DC TRAINING DATASETS

//*-----------------------------------------------------------------

//*


//CUSTOMER DD DSN=&DB1DSN,

// DISP=(,CATLG,DELETE),

// UNIT=&DEV2,

// SPACE=(TRK,(2,2)),

// DCB=(RECFM=FBS,LRECL=4096,BLKSIZE=4096)

//*

//ORDER DD DSN=&DB2DSN,


// UNIT=&DEV2,

// SPACE=(TRK,(2,2)),


//*

//PART DD DSN=&DB3DSN,


// UNIT=&DEV2,

// SPACE=(TRK,(2,2)),


//*

//* ----------------------------------------------------------------

//* - COPY FILE 3 FROM INSTALL MEDIA TO TEMPORARY FILE

//* ----------------------------------------------------------------

//STEP2 EXEC PGM=SQUEEZE,PARM='STRETCH'

//*------------------------------------------------------------------

//* STRETCH SQUEEZED FILE3 TO CREATE A STANDARD IEBCOPY UNLOAD DSN

//*------------------------------------------------------------------

//STEPLIB DD DSN=&IXPLOAD,DISP=SHR

//SYSUT2 DD DSN=&BASESEQ,DISP=(NEW,PASS),

// UNIT=SYSDA,SPACE=(CYL,(100,20))

// DCB=(DSORG=PS,RECFM=VS,LRECL=6160,BLKSIZE=6164)

//SYSPRINT DD SYSOUT=*

//*

//SYSUT1 DD DSN=CW.FI.FILE3,

// LABEL=(3,SL),

// UNIT=CART,

// VOL=(,RETAIN,SER=C00009),

// DISP=OLD

//*

//*------------------------------------------------------------------

//STEP3 EXEC PGM=IEBCOPY

//*------------------------------------------------------------------

//* LOAD BASE FROM STRETCHED FILE3

//*------------------------------------------------------------------

//SYSPRINT DD SYSOUT=*

//SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(10,10))

//SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(10,10))

//INDD DD DSN=&BASESEQ,DISP=(OLD,DELETE)

//OUTDD DD DSN=&BASE,DISP=(NEW,PASS),

// UNIT=SYSDA,SPACE=(CYL,(100,20,10))

//SYSIN DD DISP=SHR,

// DSN=XXXXXXX.V7R5M0.INSTALL(COPYUNLD)

//*------------------------------------------------------------------

//*------------------------------------------------------------------

//*

//* LOAD TARGET DATASETS FROM &BASE PDS.

//*

//*------------------------------------------------------------------

//* STRETCH A MEMBER OF A PDS TO A SEQUENTIAL DATASET

//* PARMS

//* PDS1 - THE SOURCE PDS

//* MEM - THE SOURCE MEMBER (OF PDS1 - TO BE STRETCHED AND LOADED)

//* SEQ - THE TARGET SEQUENTIAL DATASET

//*------------------------------------------------------------------



//SYSUT1 DD DSN=&BASE(CUSTOMER),DISP=(OLD,PASS)

//SYSUT2 DD DSN=XXXXXXX.FIDSAMP.CUSTOMER,DISP=OLD


//*------------------------------------------------------------------


2-37




//SYSUT1 DD DSN=&BASE(PART),DISP=(OLD,PASS)

//SYSUT2 DD DSN=XXXXXXX.FIDSAMP.PART,DISP=OLD

//SYSPRINT DD SYSOUT=

//*------------------------------------------------------------------



//SYSUT1 DD DSN=&BASE(ORDER),DISP=(OLD,PASS)

//SYSUT2 DD DSN=XXXXXXX.FIDSAMP.ORDER,DISP=OLD

//SYSPRINT DD SYSOUT=

//*--------------------------------------------------------------------

//* STEP7: UPDATE FILE-AID FOR IMS/DC CLT DATA BASE WITH DBD INFO

//*--------------------------------------------------------------------\

//*

//STEP7 EXEC PGM=DFSRRC00,COND=(0,NE),

// PARM=(DLI,IXPDBDUP,&PSB,&BUF,

// &SPIE&TEST&EXCPVR&RST,&PRLD,

// &SRCH,&CKPTID,&MON,&LOGA,&FMTO,

// &IMSID,&SWAP,&DBRC,&IRLM,&IRLMNM)

//*


// DD DSN=&IXPLOAD,DISP=SHR

// DD DSN=CEE.SCEERUN,DISP=SHR





//SYSABEND DD SYSOUT=&PRINT,

// DCB=(LRECL=121,RECFM=VBA,BLKSIZE=3129),

// SPACE=(125,(2500,100),RLSE,,ROUND)

//ABNLDUMP DD DUMMY

//IEFRDER DD DUMMY,DCB=BLKSIZE=100

//IXDCLTDD DD DSN=&IXPDB,DISP=OLD

//IXPFD DD DSN=&XRFCDSN,DISP=SHR

//IXPC1 DD DSN=&CBLDSN,DISP=SHR

//IXPD1 DD DSN=&DBDLIB,DISP=SHR

//IXPMLIB DD DSN=&MLIBDSN,DISP=SHR

//SYSOUT DD SYSOUT=&PRINT

//*

//*--------------------------------------------------------------------

//* STEP8: UPDATE FILE-AID FOR IMS/DC CLT DATA BASE WITH XREF INFO

//*--------------------------------------------------------------------

//*

//STEP8 EXEC PGM=DFSRRC00,COND=(0,NE),

// PARM=(DLI,IXPXRFUP,&PSB,&BUF,

// &SPIE&TEST&EXCPVR&RST,&PRLD,

// &SRCH,&CKPTID,&MON,&LOGA,&FMTO,

// &IMSID,&SWAP,&DBRC,&IRLM,&IRLMNM)

//*








//SYSABEND DD SYSOUT=&PRINT,

// DCB=(LRECL=121,RECFM=VBA,BLKSIZE=3129),

// SPACE=(125,(2500,100),RLSE,,ROUND)

//ABNLDUMP DD DUMMY

2-38





//IXPFD DD DSN=&XRFCDSN,DISP=SHR

//IXPC1 DD DSN=&CBLDSN,DISP=SHR




//*

// PEND

//*


//*

//*--------------------------------------------------------------------

//* FOLLOWING ARE THE IXPDBDUP PROGRAM CONTROL CARDS FOR THE

//* PROVIDED SAMPLE DATA BASES. THE PROGRAM CONTROL CARDS ADD

//* DBD INFORMATION TO THE FILE-AID FOR IMS/DC CLT DATA BASE.

//*--------------------------------------------------------------------

//*

//STEP7.SYSIN DD *

UPD PCUST PHYSICAL CUSTOMER DATA BASE

UPD LCUST LOGICAL CUSTOMER DATA BASE

UPD PORDR PHYSICAL ORDER DATA BASE

UPD LORDR LOGICAL ORDER DATA BASE

UPD PPART PHYSICAL PART DATA BASE

/*

//*

//*--------------------------------------------------------------------

//* FOLLOWING ARE THE IXPXRFUP PROGRAM CONTROL CARDS FOR THE

//* PROVIDED SAMPLE XREF. THE PROGRAM CONTROL CARDS ADD XREF

//* INFORMATION TO THE FILE-AID FOR IMS/DC CLT DATA BASE.

//*--------------------------------------------------------------------

//*

//STEP8.SYSIN DD *

OPT COBOL

UPD PCUST *

UPD PORDR *

UPD LORDR *

UPD PPART *

/*

//

Step 12. Assemble/Link Sample Security Exit

This step compiles and links the sample security exit program into the main load module. Skip this step unless you are writing your own security exit routine. For further

details refer to Appendix A, “File-AID for IMS Security Exit”.

1. Select option 8, SECURITY EXIT, from the File-AID for IMS/DC Installation Menu.

The File-AID for IMS/DC Security Exit screen is displayed (Figure 2-45).


2-39

Figure 2-45. File-AID for IMS/DC Security Exit Screen

INSTALL ------------- File-AID for IMS/DC Security Exit ---------------------

COMMAND ===>

Specify your IMS load library to linkedit the security exit into.

LOAD LIBRARY ===> 'XXXXXXX.FID.V7R5M0.LOAD'

Specify if you want to dynamically load the security exit during execution or statically link the security exit into the main load module.

STATIC or DYNAMIC ===> (S = Static, D = Dynamic)

Specify compile and linkedit information:

COMPILER LIBRARY

LINKAGE LIBRARY

===>

===>

2. Specify your DC load library to link-edit the security exit into.

3. Specify if you want to dynamically load the security exit during execution or statically link the security exit into the main load module.

4. Specify the compile and link-edit libraries.

5. Press Enter.



your installation library member @FDSCXT.

Figure 2-46. File-AID for IMS

–

Generate Install JCL Screen (@FDSCXT)


OPTION ===>


2 SAVE JCL - to save JCL in ’XXXXXXX.FID.V7R5M0.INSTALL(@FDSCXT)’



SYSOUT CLASS ===> *




===> //*

===> //*



2-40


Figure 2-47 on page 2-40 through Figure 2-50 on page 2-43 show an example of the

generated JCL to compile and link the sample security exit program into the main load module.

Figure 2-47. Example JCL, Compile and Link-Edit the Sample Security Exit Program, Part 1



//*

//*

//*____________________________________________________________________

//* |

//*

//*


|

//*

//*


|


//* ------------------------------------------------------------------|

//*

//*

//* STEP

//* ----

//* 1

//*

//*

//*

2

FUNCTION |

-----------------------------------------------------------|

COMPILE SAMPLE SECURITY EXIT - IXDSCXT

LINK EDIT SAMPLE SECURITY EXIT - IXDSCXT

|

|

|

|

//* 3

//*

//*

//*

REMOVE DUMMY IXDSCXT FROM IXD'S MAIN LOAD MODULE

(FORCES DYNAMIC LOAD OF SECURITY EXIT)

|

|

//*___________________________________________________________________|

//*

|

|

|

|


// PRINT='*',

//*

//*** YOUR IMS PROGRAM LIBRARY

//

//*

PGMLIB='IMS810A.PGMLIB'


SYSOUT PRINT CLASS

//*--------------------------------------------------------------------

//* STEP1 COMPILE FILE-AID FOR IMS/DC

//* SAMPLE SECURITY EXIT - IXDSCXT

//*--------------------------------------------------------------------

//*

//STEP1 EXEC PGM=IGYCRCTL

//STEPLIB DD DSN=SYS2.COBOL.LOADLIB,

//

//SYSLIN DD

DISP=SHR

DSN=&&OBJMOD,DISP=(MOD,PASS),UNIT=&DEV,

// SPACE=(80,(250,100))


//SYSUT1

//SYSUT2

DD

DD



//SYSUT3

//SYSUT4

//SYSUT5

//SYSUT6

DD

DD

DD

DD





//SYSUT7

//SYSIN


DD DUMMY

//*

//*--------------------------------------------------------------------

//* STEP2 LINK IXDSCXT INTO LOAD LIBRARY

//*--------------------------------------------------------------------

//*

//STEP2 EXEC PGM=IEWL,PARM='LIST,MAP,RENT',COND=(7,LT)

//SYSLMOD DD DSN=&PGMLIB,DISP=SHR

//SYSLIB

//

//

//SYSUT1

DD DSN=&PGMLIB,DISP=SHR

DD DSN=CEE.SCEERUN,

DISP=SHR

DD DSN=&&SYSUT1,UNIT=&DEV,

// SPACE=(1024,(200,50),,CONTIG,ROUND),DCB=BLKSIZE=1024


//SYSLIN

//*

DD DUMMY

//*--------------------------------------------------------------------

//* STEP3 REMOVE DUMMY SECURITY EXIT FROM MAIN LOAD MODULE

//*--------------------------------------------------------------------

//*

//STEP3

//

//SYSLIB

EXEC PGM=IEWL,PARM='LIST,MAP,RENT,LET,NCAL',

DD

REGION=512K,COND=(7,LT)

DSN=&PGMLIB,DISP=SHR


2-41


//SYSLMOD DD DSN=&PGMLIB,DISP=SHR

//SYSUT1 DD DSN=&&SYSUT1,UNIT=&DEV,

// SPACE=(1024,(200,50),,CONTIG,ROUND),DCB=BLKSIZE=1024


//SYSLIN DD DUMMY

//*

//

//*

PEND

//IXDPRC10 EXEC IXDPRC10

//*

//STEP1.SYSIN DD *

00001 IDENTIFICATION DIVISION.

00002 PROGRAM-ID. IXDSCXT.

00003 AUTHOR. COMPUWARE CORPORATION.

00004 ENVIRONMENT DIVISION.

00005 INPUT-OUTPUT SECTION.

00006 EJECT

00007 DATA DIVISION.

00008 WORKING-STORAGE SECTION.

00009 ***********************************************************

00010 *

00011 * WORKING STORAGE SHOULD ONLY BE USED FOR NON CHANGING

*

*

00012 * FIELDS TO ENSURE REENTRANCY.

*

00013 * *

00014 ***********************************************************

00015 01 STATIC-STORAGE.

00016

00017

05

10

STATIC-USERIDS.

EMPLOYEE-USERID

00018

00019

00020

10 SALARY-USERID

05 STATIC-PASSWORDS.

10 EMPLOYEE-PASSWORD

PIC X(8)

PIC X(1) VALUE '0'.

PIC X(8)

VALUE 'XAS001 '.

VALUE 'PERSONNL'.

00021

00022

00023

00024

00025

00026

05 STATIC-DBD-NAMES.

10 EMPLOYEE-DBD-NAME

10 SALARY-DBD-NAME

10 PROJECT-DBD-NAME

05 STATIC-FUNCTION-NUMBERS.

10 BROWSE-FUNCTION

PIC X(8)

PIC X(8)

PIC X(4)

PIC X(1)

VALUE 'EMPLDBD '.

VALUE 'SALRYDBD'.

VALUE 'PROJ'.

VALUE '1'.

PIC X(1) VALUE '2'.

00027

00028

00029

10 EDIT-FUNCTION

05 STATIC-LTERMS.

10 PROJECT-LTERM

00030

00031

05 STATIC-TRANSACTIONS.

10 SALARY-TRANSACTION

00032 EJECT

PIC X(3)

PIC X(8)

VALUE 'XAS'.

VALUE 'XASALARY'.

00033 LINKAGE SECTION.

00034 SKIP2

00035 ***************************************************************

00036 * INPUT/OUTPUT PARAMETER INFORMATION USED IN ALL SECURITY *

00037 * EXIT ROUTINES.

*

00038 ***************************************************************

00039 SKIP2

00040 01 SECURITY-EXIT-PARMS.

00041 ***************************************************************

00042 * FUNCTION NUMBER VALUES --1 - BROWSE MODE *

00043 * 2 - EDIT MODE *

00044 ***************************************************************

00045

00046

00047

00048

00049

00050

05 PRMSECXT-INPUT-PARAMTERS.

10 PRMSECXT-EXIT-TYPE

10 PRMSECXT-SIGNON-USER-ID

10 PRMSECXT-MAIN-MENU-USER-ID

10 PRMSECXT-PASSWORD

10 PRMSECXT-DBD-NAME

00051

00052

00053

00054

00055

00056

00057

00058

00059

00060 SKIP2

10 PRMSECXT-FUNCTION-NUMBER

10 PRMSECXT-LTERM

10 PRMSECXT-TRANSACTION

10 PRMSECXT-FILLER1

05 PRMSECXT-OUTPUT-PARAMTERS.

10 PRMSECXT-AUDIT-TRAIL-IND

10 PRMSECXT-DBD-PASSED-IND

10 PRMSECXT-FILLER2

PIC X(1).

PIC X(8).

PIC X(8).

PIC X(8).

PIC X(8).

PIC X(1).

PIC X(8).

PIC X(8).

PIC X(30).

PIC X(1).

PIC X(1).

PIC X(30).

2-42



00061 **********************************************************

00062 * THIS AREA SHOULD BE USED FOR NONSTATIC WORKING STORAGE *

00063 * 256 BYTES ARE AVAILABLE FOR USE *

00064 **********************************************************

00065 01 SECURITY-EXIT-WORK-AREA.

00066

00067

00068

00069

00070

00071

05 WS-USERID.

10 WS-USERID-1ST-7-CHARS

10 WS-USERID-LAST-CHAR

10 WS-DBD-NAME.

15 WS-DBD-1ST-4-CHARS

15 WS-DBD-LAST-4-CHARS

PIC X(7).

PIC X(1).

PIC X(4).

PIC X(4).

00072

00073

00074

00075

00076

00077

00083

00084

00085

00086

00087

00088

00089

00090

00091

00092

00093

00094

10 WS-LTERM.

15 WS-LTERM-1ST-3-CHARS

15 WS-LTERM-LAST-5-CHARS

05 FILLER

ELSE

GOBACK.

PERFORM P2000-SALARY-DBD-VALIDATION

MOVE PRMSECXT-DBD-NAME TO WS-DBD-NAME

IF WS-DBD-1ST-4-CHARS = PROJECT-DBD-NAME

ELSE

PERFORM P3000-PROJECT-DBD-VALIDATION

NEXT SENTENCE.

PIC X(3).

PIC X(5).

PIC X(232).

00078 EJECT

00079 PROCEDURE DIVISION USING SECURITY-EXIT-PARMS

00080 SECURITY-EXIT-WORK-AREA.

00081

00082 IF PRMSECXT-DBD-NAME = EMPLOYEE-DBD-NAME

PERFORM P1000-EMPLOYEE-DBD-VALIDATION

ELSE

IF PRMSECXT-DBD-NAME = SALARY-DBD-NAME

00095 EJECT

00096

00097 P1000-EMPLOYEE-DBD-VALIDATION.

00098 SKIP1

00099 ***************************************************************

00100 * THIS PROCEDURE PREVENTS BROWSING OR EDITING OF THE EMPLOYEE*

00101 * DATA BASE UNLESS THE USERID IS 'XAS001' AND THE PASSWORD IS*

00102 * 'PERSONNL'.

*

00103 ***************************************************************

00104

00105 SKIP2

00106 IF PRMSECXT-MAIN-MENU-USER-ID = EMPLOYEE-USERID AND

00107

00108

00109

00110

00111

00112 EJECT

PRMSECXT-PASSWORD = EMPLOYEE-PASSWORD

MOVE 'Y' TO PRMSECXT-DBD-PASSED-IND

ELSE

MOVE 'N' TO PRMSECXT-DBD-PASSED-IND.

00113

00114 P2000-SALARY-DBD-VALIDATION.

00115 SKIP2

00116 ***************************************************************

00117 * THIS PROCEDURE PREVENTS BROWSING OR EDITING OF THE SALARY *

00118 * DATA BASE UNLESS THE USERID ENDS WITH '0' AND THE *

00119 * TRANSACTION ENTERED WAS 'XASALARY'.

*

00120 *****************************************************************

00121 SKIP1

00122

00123

00124

MOVE PRMSECXT-MAIN-MENU-USER-ID TO WS-USERID.

IF WS-USERID-LAST-CHAR = SALARY-USERID AND

PRMSECXT-TRANSACTION = SALARY-TRANSACTION

00125

00126

00127

ELSE

00128

00129 EJECT

00130


MOVE 'N' TO PRMSECXT-DBD-PASSED-IND.

00131 P3000-PROJECT-DBD-VALIDATION.

00132 SKIP2


2-43


00133 ***************************************************************

00134 * THIS PROCEDURE PREVENTS EDITING OF THE PROJECT DATA BASES *

00135 * UNLESS THE LTERM BEGINS WITH 'XAS'.

THE PROJECT DATA BASES*

00136 * MAY BE BROWSED BY ALL USERS.

*

00137 *****************************************************************

00138 SKIP1

00139 IF PRMSECXT-FUNCTION-NUMBER = EDIT-FUNCTION

00140 MOVE PRMSECXT-LTERM TO WS-LTERM

00141

00142

00143

IF WS-LTERM-1ST-3-CHARS = PROJECT-LTERM

ELSE


00144

00145

00146

00147

/*

//*

MOVE 'N' TO PRMSECXT-DBD-PASSED-IND

ELSE

MOVE 'Y' TO PRMSECXT-DBD-PASSED-IND.

//STEP2.SYSLIN DD DSN=&&OBJMOD,DISP=(OLD,DELETE)

// DD *

ENTRY IXDSCXT

MODE AMODE(24),RMODE(24)

NAME IXDSCXT(R)

/*

//*

//STEP3.SYSLIN DD *

ORDER DFHPL1OI

INCLUDE SYSLIB(IXDSCXT)

INCLUDE SYSLIB(IXDMAIN)

ENTRY PLICALLA


NAME IXDMAIN(R)

/*

//*

//

Step 13. Create Aliases to the Main Load Module

This step creates aliases to the main load module. This step is required only when you install a multiple transaction configuration. If you install a single transaction configuration of File-AID for IMS, skip this step.

1. Select option 9, ALIASES, from the File-AID for IMS/DC Installation Menu.

The File-AID for IMS/DC Aliases

screen is displayed (Figure 2-51 on page 2-44).

2-44


Figure 2-51. File-AID for IMS/DC Aliases Screen

INSTALL ------------- File-AID for IMS/DC Aliases -----------------------------

COMMAND ===>

Creating aliases to the main load module is only required when you install a multiple transaction configuration. If you install a single transaction configuration you can skip this process. The alias names should correspond with the PSB names associated with the transactions in the multiple transaction configuration. The linkage editor allows a maximum of 64 aliases for one load module. If you have more than 65 PSBs you must create additional copies of the main load module (IXDMAIN) and then assign the PSB alias names to that copy of IXDMAIN.

Specify your IMS program library to linkedit IXDMAIN into.

IMS PGMLIB ===> 'IMS810A.PGMLIB'

The next screen will table your aliases. Press enter to continue.

When you are finished entering your aliases, Press PF3 to end.

2. Specify your IMS program library to link-edit IXDMAIN into.

3. Press Enter.

The File-AID for IMS/DC Aliases List screen is displayed (Figure 2-52).

Figure 2-52. File-AID for IMS/DC Aliases List Screen

INSTALL --------- File-AID for IMS/DC Aliases List --------- Row 1 to 11 of 11


_

_

_

_

I=Insert,D=Delete

Action Alias

------------------------------------------------------------------------------

_

_

_

_

_

_

_

******************************* Bottom of data ********************************

4. To add an alias to the list, enter the action I and the name of the alias. To remove an alias from the list, enter the action D in front of the listed alias.

5. Enter the END primary command (PF3).


2-45).


2-45


your installation library member @FDALIAS.

Figure 2-53. File-AID for IMS – Generate Install JCL Screen (@FDALIAS)


OPTION ===>


2 SAVE JCL - to save JCL in ’XXXXXXX.FID.V7R5M0.INSTALL(@FDALIAS)’



SYSOUT CLASS ===> *




===> //*

===> //*



Figure 2-54 on page 2-46 shows an example of the generated JCL to create aliases for the

IXDMAIN load module.

2-46


Figure 2-54. Example of JCL to Allocate and Unload File-AID for IMS/DC Libraries



//*

//*

//*____________________________________________________________________

//* |

//*

//*


|

//*

//*

F I L E - A I D F O R I M S / D C


//* ------------------------------------------------------------------|

|

|

//*

//*

//* STEP

//* ----

FUNCTION

|

|

|

-----------------------------------------------------------|

//* 1 CREATE ALIASES FOR IXDMAIN LOAD MODULE |

//*___________________________________________________________________|

//*

//IXDPRC11 PROC DEV=SYSDA,

//

//*

PRINT='*',


SYSOUT PRINT CLASS

//*** YOUR IMS PROGRAM LIBRARY

// PGMLIB='IMS810A.PGMLIB'

//*

//*--------------------------------------------------------------------

//* STEP1: CREATE ALIASES FOR LOAD MODULE

//*--------------------------------------------------------------------

//*

//STEP1

//

//SYSLIB

//

EXEC PGM=IEWL,PARM='LIST,MAP,XREF,RENT,SIZE=(256K,96K)',

REGION=2048K

DD DSN=&PGMLIB,

DISP=SHR

//SYSLMOD DD DSN=&PGMLIB,

//

//SYSUT1

//

//

DD

DISP=SHR

DSN=&&SYSUT1,

UNIT=&DEV,

SPACE=(1024,(200,50),,CONTIG,ROUND),DCB=BLKSIZE=0


//SYSLIN DD DUMMY

//*

// PEND

//*

//IXDPRC11 EXEC IXDPRC11

//*

//STEP1.SYSLIN DD *

INCLUDE SYSLIB(IXDMAIN)

ALIAS alias2

ALIAS ALIAS

ENTRY PLICALLA


NAME IXDMAIN(R)

/*

//

Step 14. Access Additional Databases and Segment

Layouts

1. If you have additional user databases that you want to access, enter a job card in member DBDUPBMP if you want to run this job as a BMP program. Use member

DBDUPDLI if you want to run it as a DL/I batch program.

Note: This job must be run whenever databases are added, changed, deleted from

access by File-AID for IMS or if the product is being installed for the first time.


2-47

2. If you have additional segment layouts that you want to use with File-AID for IMS, enter a job card in installation JCL member XRFUPBMP or XRFUPDLI. Use

XRFUPBMP if you want to run this job as a BMP program. Use XRFUPDLI if you want to run it as a DL/I batch program.

Note: This job must be run whenever segment layouts are added, changed, deleted

from the File-AID for IMS system or if the product is being installed for the first time.

Refer to the File-AID for IMS/DC/CICS Reference Manual for an explanation of the JCL required.

2-48


3-1

Chapter 3.

Verification of the Installation

A short test that uses File-AID for IMS and the datasets on your installation media completes the installation process. Running the test verifies that all components of File-

AID for IMS are loaded properly and that executing File-AID for IMS produces the expected results.

This chapter provides step-by-step procedures along with screen illustrations and explanations of common variances to assist you with the verification of the installation of File-AID for IMS. If you encounter any problems during the verification procedure,

refer to “Potential Problems” on page 3-5. Call a Compuware customer support

representative if you are still unable to solve the problem.

Step 1. Verify Primary Options

1. Log on to IMS to invoke File-AID for IMS.

2. If you installed the MFS formats into the test format library, enter /TEST MFS to allocate the correct format library.

3. Enter one of the transaction codes installed, preferably one that can access the sample databases shipped with File-AID for IMS. The File-AID for IMS Primary Option

Menu is displayed (Figure 3-1).

Figure 3-1. Primary Option Menu

-----------------File-AID for IMS/DC PRIMARY OPTION MENU -----------------

OPTION ===>

1 BROWSE - Display data base contents

2 EDIT - Create or change data base contents

L LEGAL - Copyright and Trade Secret Information

X EXIT - Terminate File-AID for IMS/DC session

RELEASE

CPU ID

- 7.5

- 323697

TERMINAL - XAS78A01

TIME

DATE

- 08:38:01

- 01/06/10

DBD TO BE USED ===> (Blank for member list)

-------------------------------------------------------------------------------

Enter your USERID and PASSWORD:

USERID ===>

PASSWORD ===>

Copyright (c) 1986, 2010, an unpublished work by Compuware Corporation.

All Rights Reserved.

Step 2. Edit DBD

1. Type 2 in the Option field.

3-2


2. Press Enter. The DBD Member List screen is displayed (Figure 3-2). The DBDs listed

are the same as those in the PSB associated with the transaction entered in “Step 1.

Define Environment” on page 2-1.

Figure 3-2. DBD Member List Screen

-------------------------EDIT - DBD MEMBER LIST ---------------------------

COMMAND ===> SCROLL ===> CUR

--DBD---

_ LCUST

_ LORDR

_ PCUST

_ PORDR

_ PPART

----DATA BASE DESCRIPTION-----

LOGICAL CUSTOMER DATA BASE

LOGICAL ORDER DATA BASE

PHYSICAL CUSTOMER DATA BASE

PHYSICAL ORDER DATA BASE

PHYSICAL PART DATA BASE

*** END OF DBD MEMBER LIST ***

PF1-MENU 3-END 7-UP 8-DOWN

Step 3. Edit Data Base Location

1. Type S next to the PORDR database name that you want to select.

2. Press Enter. The Data Base Location screen is displayed (Figure 3-3).

Figure 3-3. Data Base Location Screen

--------------------EDIT - DATA BASE LOCATION ----------------- LINE 00001

COMMAND ---> SCROLL ---> CUR

LINE KEY KEY

CMD -----LEVEL----- --SEG--- --DESCRIPTION-- LTH -------------VALUE------------

SI* 1 DBD-PORDR

__ 2

ORDR010

ORDR020

ORDER ROOT

ORDER LINE

006 AA2222

002

__

__

__

2

2

3 ORDR030

ORDR040

ORDR050

ORDER STATUS

ORDER SCRAP

002

008

ORDR-CUST LCHLD 002

*** END OF SEGMENT LIST ***

S -- Select Formatted

SU -- Select Unformatted

SI -- Select Index of Segments

PF1-MENU 2-DBD 3-END 7-UP 8-DOWN

K -- Key Spec, then Select Formatted

KU -- Key Spec, then Select Unformatted

KI -- Key Spec, then Select Indexed

Verification of the Installation

3-3

Step 4. Select Segment and Format

1. Select the first segment on the Data Base Location screen to retrieve the first segment

in the database, and press Enter. The Formatted screen is displayed (Figure 3-4).

Figure 3-4. Formatted Screen

EDIT --- (PORDR - PHYSICAL ORDER DATA BASE) ------------------------ LINE 00001


PAR

SEG ORDR010 ORDER ROOT CONCAT KEY: AA2222

--------LEVEL NUMBER/DATA-NAME--------- -FORMAT- ---------FIELD VALUE----------

01 ORDER-ROOT-DATA

05 ORDER-ROOT-KEY

07 ORDER-NUMBER-PREFIX

07 ORDER-NUMBER

C

Z

2

4

C 40

K AA

K 2222

INDUSTRIAL GRADE COAXIAL CABLE 05 ORDER-DESCRIPTION

(POS 31-40)

05 CUSTOMER-NUMBER

05 PLANNED-ORDER-QUANTITY

05

05

PLANNED-ORDER-AMOUNT

ORDER-TYPE

05 ACTUAL-ORDER-QUANTITY

05 TOTAL-SCRAP-QUANTITY

05 TOTAL-SCRAP-REDEFINES

P

C

C 6

PS 5

PS

PS

CN0001

500

5 2 3567.50

2 WS

RDEFINES TOTAL-SCRAP-QUANTITY

C

5

5

3

INVALD X’404040’

10

INVALD X’00010C’

05 ORDER-STATUS

05 FILLER

05 FIRST-ACTIVITY-DATE

Z

C

2

1

01

<

PF1-MENU 2-DBD 3-END 4-NEXT 5-CHILD 6-TWIN 7-UP 8-DOWN 9-PAR 12-ROOT

2. Type UNFMT to display the segment in the unformatted mode, and press Enter. The

Unformatted screen is displayed (Figure 3-5).

Figure 3-5. Unformatted Screen

EDIT --- (LORDR - ORDER DB - LOGICAL VIEW) -----------------------------------


PAR ORDR010 ORDER ROOT

SEG ORDR020 ORDER LINE

RCD TYP1: PO

CONCAT KEY: AA2222,01

SEG LENGTH ===> 178 MIN:50 MAX:200

----+----1----+----2----+----3----+----4----+----5----+----6----+----7

1 ..01POOPEN

C7477ABLACK COAXIAL CABLE EAWXWWAA2222-22 ZEN

0BFFDDDDCD444CFFFFCCDCCD4CDCECCD4CCCDC44444444444CCEEEECCFFFF6FF444ECD

0201766755000374771231320361791303123500000000000516766112222022000955

----+----*----+----*----+----*----+----*----+----*----+----*----+----*

71 ITH WIRE 2224 34552 ...

CEC4ECDC4444444444444444444FFFF4FFFFF444444444444444444444444444444002

938069950000000000000000000222403455200000000000000000000000000000001C

----+----*----+----*----+----*----+----*----+----*----+----*----+----*

141 ..................ASTC1988090119880904

001000000800000008CEECFFFFFFFFFFFFFFFF

00C01C009C000C009C12331988090119880904


3. Type KEY, and press Enter. The Key Specification screen is displayed (Figure 3-6).

3-4


Figure 3-6. Key Specification Screen

KEY SPEC --- (LORDR - ORDER DB - LOGICAL VIEW) -------- SPECIFY KEY TO RETRIEVE


SEGMENT TO RETRIEVE: ORDR040 ORDER SCRAP

-------LEVEL NUMBER/DATA-NAME------- -FORMAT- RO ---------FIELD VALUE----------

LVL 1 ORDR010

05 ORDER-ROOT-KEY

07 ORDER-NUMBER-PREFIX C 2 K

EQ

AA

07 ORDER-NUMBER Z 4 K 2222

------------------------------------ -------- -- ------------------------------

LVL 2 ORDR040 EQ

05 SCRAP-KEY

07 PROCESS-INDICATOR

07 PART-NUMBER

******** END OF KEY ********

C

C

2

6

K

K

01

C7477A

Enter END command when the key value has been fully specified

Enter CANCEL command to terminate Key Specification without processing the key

PF3-END 7-UP 8-DOWN

4. Type CANCEL, and press Enter. The Unformatted screen is displayed again.

5. Type HEX OFF, and press Enter. The Unformatted/HEX Off screen is displayed (Figure

3-7).

Figure 3-7. Unformatted/HEX OFF Screen

EDIT --- (PORDR - ORDER

COMMAND ===>

PAR

SEG ORDR010 ORDER ROOT

DATA BASE) -----------------------------------------

SCROLL ===> CUR

CONCAT KEY: AA2222

SEG LENGTH ===> 167

----+----1----+----2----+----3----+----4----+----5----+----6----+----7

1 AA2222INDUSTRIAL GRADE COAXIAL CORD CN0001.-.....WS......01<

----+----*----+----*----+----*----+----*----+----*----+----*----+----*

71 1988083019880914.........P....P...................!..!................

----+----*----+----*----+----*----+----*----+----*----+----*----+----*

141 ..........................B


6. Type INDEX, and press Enter. The Index screen is displayed (Figure 3-8).

Verification of the Installation

3-5

Figure 3-8. Index Screen

EDIT --- (PORDR - PHYSICAL ORDER DATA BASE) ------------------ COLS 00001 00060


LEVEL --SEG-----+----1----+----2----+----3----+----4----+----5----+----6

__ 1 ORDR010 AA4444HIGH PERFORMANCE COAX CN0033.....n.H

__

__

__

2

3

3

ORDR020 ..01POOPEN

C12223GREY COAX

ORDR030 01QA.. ... .OKGRINDING

ORDR030 04WA........BDFINISHING

1988021419880306

19880902

EAQQRRAA444

__

__ 2

__ 2

3

__ 2

__ 2

__ 2

ORDR030 05WD........OKTESTING

ORDR020 ..02WOOPEN

ORDR020 .>04WOOPEN

ORDR020 01C12223RM....BSSCRAP

1988090519880912

C44567CEMENTING PROCEDURE

U224AB2400 BAUD MODEM KIT

ORDR020 CN00330101............19881012

ORDR020 CN00330202............19881012

Y19880912

INSFAA4-01D

OVEA10098SY

RD8... ..

OVEA02033BE

RD8... ..

__ 1

__ 2

__ 3

__ 3

__

__ 2

3

__

__

__

3

3

3

ORDR010 AA8888TERMINAL ACCESORIES

ORDR020 ..01POOPEN

U248AB4800 BAUD MODEM KIT

ORDR030 01QA........OKMILLING CMPLTE 1988021419880306

ORDR030 04ER........OKPOLISHING

ORDR030 05GG........OKPAINTING

ORDR020 ..02POCLOSED C12222BLUE COAX

19880902

1988090819880902

ORDR030 01WZ........OKPRIMING

1988031419880306

ORDR030 05RZ........OKFIRMING CMPLTE 1988061219880706

ORDR030 12QA........OKPOLISHING

1988071219880706

CN0055.... n.W

EAWXWXAA222

EATITTAA666

PF1-MENU 2-DBD 3-END 7-UP MAX 8-DOWN 9-PAR 10-LEFT 11-RIGHT 12-ROOT

Step 5. Exit

Type =X in the Command field and press Enter to exit File-AID for IMS. A blank screen is displayed.

Potential Problems

• If, after “Step 1. Verify Primary Options”, the message NO SUCH TRANSACTION

CODE appears:

– Verify that the Stage 1 system definition was done for the transaction code entered.

– Verify that a space was entered after the transaction code.

• If, after any step, the message REQUESTED BLOCK NOT AVAILABLE appears:

– Verify that /TEST MFS was entered prior to the transaction code if the MFS modules were linked into the test format libraries.

– Verify that the block name displayed in the message is the same as the MOD name of the corresponding MFS source member.

– Verify that the logical terminal type is one of those supported by File-AID for IMS

(Refer to “MFS Tailoring” on page 1-10).

• If, after “Step 1. Verify Primary Options”, there is no response from the terminal:

– Verify that the IMS transaction queue is not backed up.

– Verify that all the databases within the PSB are online to IMS and not stopped.

– Verify that the class specified on the APPLCTN or TRANSACT macros is proper for your installation.

– Verify that the PSB size shown on the ACB generation report is within your installation’s PSB pool size limits.

– Verify that the VSAM buffer subpool has buffers large enough to contain the control intervals of the control database datasets.

• If File-AID for IMS abends with an AI status code:

3-6


– Verify that the control databases are correctly allocated.

– Verify that the control databases were properly initialized with job JCLALOC.

– Verify that the control databases’ dataset names are not restricted from read/write access by an existing security package.

• If File-AID for IMS abends with message "D204":

– Verify that job JCLCLTUP was run correctly.

– The control segment may have been deleted by an external job. Run program

IXPREBLD to reestablish this segment. Refer to “Control Segment Missing or

Invalid” on page B-2.

• If, upon entering the Edit Formatted mode, no segment layout is displayed:

– Verify that job JCLCLTUP was correctly run.

– If the database selected was not one of the sample databases, verify that job

XRFUPDLI or XRFUPBMP was correctly run for that database.

• If, after any step, the message TRAN/LTERM STOPPED appears:

– Verify that File-AID for IMS did not previously abend.

– Verify that the transaction was not stopped by the MTO.

• If, after entering the KEY or INDEX command, data is missing or truncated or there is no response from the terminal:

Verify that the IMS large message queue is long enough. Refer to “IMS Message

Queues” on page 1-12 for the required size.

A-1

Appendix A.

File-AID for IMS Security Exit

Appendix A.

File-AID for IMS provides one exit type to the security exit. Its primary intent is to limit database access and to control whether a user’s database updates are captured by the

Audit Trail feature. The default security exit routine provided with File-AID for IMS does no processing and returns control immediately to File-AID for IMS.

The security exit receives control from the following locations:

1. From the Primary Option Menu when a DBD name is entered. Here, the security exit may grant or deny access to the database. The message "ACCESS TO SPECIFIED DBD

IS PROHIBITED BY INSTALLATION SECURITY EXIT" is displayed if access was denied.

2. From the DBD Member List screen when DBD names are selected for display. If access is granted to a particular database, its name is displayed on the member list.

Otherwise, access is denied and the DBD name does not appear on the member list.

In both these situations, when the user invokes the edit option, the security exit may also force the Audit Trail feature to be activated or disabled for the database that is being updated.

You may want to use the security exit to implement the following:

• User ID - DBD security

• User ID/Password - DBD security

• LTERM - DBD security

• User ID - transaction security

• User ID - function security

• The Audit Trail feature

• Any combination of the above

The sample security exit provided in JCLSCXT implements some of these functions. It restricts access to the employee database (DBD name = EMPLDBD) to user XAS001 whose password is PERSONNL. DBDs that begin with PROJ can only be edited by users at

LTERMs that begin with XAS. Users with a userid ending in O who enter transaction

XASALARY have access to DBD SALRYDBD.

Security Exit Installation

The sample security exit is written in COBOL, although PL/I or assembler can be used.

However, unless you are using VS COBOL II, a COBOL security exit is not reentrant. If this nonreentrant security exit is statically linked into module IXDMAIN, the module is not eligible for PLPA residence.

You have the following options when installing a security exit:

1. Run Step 3 in JCLSCXT and bypass Step 4 to force File-AID for IMS to dynamically load the IXDSCXT module during initialization. When you use this technique, even if the security exit is non-reentrant, module IXDMAIN remains reentrant.

2. Run Step 4 and bypass Step 3 of JCLSCXT. This option link edits the IXDSCXT routine into IXDMAIN.

A-2


Note: If you previously created aliases to the main load module, you must repeat “Step

13. Create Aliases to the Main Load Module” on page 2-43.

The following information describes the call interface and parameters used to pass control to the security exit.

Call Sequence:

CALL IXDSCXT (SECURITY-PARMS, USER-WORK-AREA)

USER-WORK-AREA is a 256 byte work area initialized to spaces. It is unchanged by File-

AID for IMS during the entire user session and can be used to retain information across multiple calls to the security exit.

AMODE 31 and XRMODE ANY Parameters

File-AID for IMS has implemented the use of AMODE 31, which is 31-bit addressing, wherever possible. Use of AMODE 31 enables File-AID for IMS to access a greatly expanded range of addresses, up to the 31-bit limit of 2 G of memory.

Most of File-AID for IMS modules use RMODE (Residency Mode) ANY, which is loading modules into either 24-bit or 31-bit memory at run time. This frees much of the memory in the lower 16 MB range for use by other applications. However, some programs implement functions that are still required to reside in the lower 16 MB. Some input/output operations use DCBs and DCB exit lists that must reside below the 16 MB line. As a result, some of the File-AID modules must be loaded into memory addresses below 16 MB, that is 24-bit addresses, called RMODE 24.

If you have written a Security Exit for use with File-AID for IMS, the security exit may not be capable of residing in 24-bit memory, depending on what functions it performs. To allow you the option of specifying the residency mode appropriate to your situation, File-

AID for IMS provides the XRMODE parameter. Specify a value of 24 for XRMODE if you have a security exit that requires residency below 16 MB. Otherwise, accept the default value of XRMODE ANY.

Security Parms Layout

The following describes the input and output parameters.

INPUT PARMS

Table A-1 describes the input parms.

Table A-1.

Input Parms

EXIT-TYPE

SIGNON-USER-ID

1

2-9

1

8

CHAR 1 (other types may be added in the future).

CHAR Entered during IMS sign-on procedure. Blank if sign-on not used.

File-AID for IMS Security Exit

A-3

Table A-1.

Input Parms (Continued)

LTERM 35-42

2

Edit

8 CHAR Logical Terminal ID.

8 Transaction used to invoke File-AID for IMS.

INPUT/OUTPUT PARMS

Table A-2 describes the input/output parms.

Table A-2.

Input/Output Parms

N

Audit Trail feature to be disabled for this DBD.

N

Access to this DBD denied.

A-4


B-1

Appendix B.

Maintenance Considerations

Appendix A.

Control Database DBD Changes

A database reorganization must be done whenever the DBDs used by the control databases change after the initial installation. This need can be caused by space requirement, randomizer, maximum segment size, dataset organization, device type, or

IMS version changes. The following steps must be taken to reorganize the changed database:

1. Unload the database that uses the existing DBD. Use JCL available at your installation or the JCL in member UNLOAD.

2. Incorporate the changes into the DBD.

3. Regenerate the DBD control block (“Step 6. Assemble DBD Source Code” on page

2-16)

4. Regenerate the ACB (“Step 9. Generate ACB Control Blocks” on page 2-23).

5. Delete and reallocate the dataset, if necessary, by using the JCL in member DELDEFO

(for OSAM databases) or DELDEFV (for VSAM databases).

6. Reload the database with the new DBD. Use JCL available at your installation or the

JCL in member RELOAD.

Control Database Segment Size Changes

If the segment size requirements of a control database need to be changed to support your database, it is indicated by message D609. Within this message is a value that is the minimum required control database segment size needed to support the DBD in question.

When changing the DBD to reflect this new control database segment length, use the

appropriate table provided in “DBD Tailoring” on page 1-4. In that table, the Segm Bytes

column displays the recommended values for the segment length. Choose the next highest value greater than the size displayed in the message to ensure that your DBD or segment layout will be supported by File-AID for IMS. Use the other values in that row in the table for the remaining control database DBD values. Remember that the LTM and

CLT control databases must use the same maximum segment length (SEGM BYTES) and root addressable area size (RMNAME BYTES).

Aside from the above mentioned requirements, the procedure to change the size of the

control data base segments is the same as described in “Control Database DBD Changes”

above.

Security Exit Added or Changed

If your installation is adding a new security exit program or changing an existing one, it must be linked again into File-AID for IMS’s main load module.

1. Enter a job card in member JCLSCXT. This job requires 512K and no tape drives.

B-2


2. Modify the default symbolic parameters (see Table B-1).

3. Modify the default PL/I Link Edit libraries from PLI.V2R3M0.PLIBASE and

PLI.V2R3M0.SIBMBASE to your PL/I or LE370 Link Edit libraries.

4. Override the SYSIN DD card to point to your security exit program,

5. Submit the job.

Note: If you created aliases to the main load module, you must update and run job

JCLALIAS as described in “Step 13. Create Aliases to the Main Load Module” on page 2-43.

Table B-1.

JCLSCXT Symbolic Parameters

Symbolic Parameter Default

PRINT *

DEV

PGMLIB

SYSDA

XXXXXXX.PGMLIB

Description

Print output SYSOUT class.

Temporary work file device.

IMS Program Library.

Installation Parameters Changed

If your installation parameters change (e.g., your call limit changes or your IMS release number changes), the installation parameter module must be linked again into the main

load module (IXDMAIN). This is done by updating and running job DCP02 in “Step 3.

Assemble and Link Installation Parameters” on page 2-3.

Note: If you created aliases to the main load module, you must update and run job

JCLALIAS as described in “Step 13. Create Aliases to the Main Load Module” on page 2-43.

Control Segment Missing or Invalid

A segment on the CLT control database stores various counts and fields used to verify the database’s integrity. If this segment is inadvertently updated or deleted, it must be rebuilt to ensure accurate processing of your databases. The Rebuild Control Segment program

(IXPREBLD) reads the File-AID for IMS database, calculates and accumulates control field information for each segment, and inserts or replaces the new control segment.

You need to run IXPREBLD when any of the following conditions occur:

• An abend screen is displayed with message number D204:

File-AID for IMS IS MISSING ITS CONTROL SEGMENT

• An abend screen is displayed with message number D205:

File-AID for IMS’s CONTROL SEGMENT CONTAINS INVALID DBD DATA

• The Batch XREF Update program terminates with a return code of 8. The summary report prints the message:

ONLINE CONTROL INFORMATION SEGMENT NOT FOUND. IF DBD UPDATE

FACILITY HAS NEVER BEEN RUN, RUN IT FIRST. OTHERWISE, RUN MAINTENANCE

UTILITY TO REBUILD CONTROL INFORMATION SEGMENT

The Rebuild Control Segment program can be run as a batch or BMP program.

Maintenance Considerations

B-3

Parameters

The parameters on the PROC statement assign default values to symbolic parameters on the procedure statement. To override a default parameter value on the PROC statement, code the same parameter on the EXEC statement that calls the procedure.

The REBLDDLI and REBLDBMP parameters specify the SYSOUT class, load libraries, and

dataset names used when the program executes. These parameters are described in “DD

Statements”.

Change the default LE Runtime library from CEE.SCEERUN to your LE370 Runtime library.

The DFSRRC00 parameters are the IMS execution time parameters.

DD Statements

Table B-2 contains the DD statements that define the primary processing files required to

run the Rebuild Control Segment program.

Table B-2.

Rebuild Control Segment Program DD Statements

DD Statement Description

STEPLIB

DFSRESLB

Designates the IMS system dataset that contains the IMS nucleus, required action modules (&RESLIB), and the library where File-AID for IMS/ISPF load modules are stored (&IXPLOAD).

Designates the IMS system dataset that contains the IMS nucleus and required action modules (&RESLIB).

IMS

DFSVSAMP

REBLDDLI PROC only. Designates the IMS system datasets that contain the database description blocks (&DBDLIB) and the program specification blocks

(&PSBLIB).

REBLDDLI PROC only. Designates the dataset (&PROCLIB) and member

(&DFVSAM) that contains the control statements that describe the size and structure of the VSAM shared resource pool for File-AID for IMS’s CLT database.

The buffers must be large enough to accept the largest segment size in the CLT database.

SYSUDUMP

IEFRDER

IXDCLTDD

IXPD1

IXPMLIB

SYSOUT

A dump of user areas if the program abends. The dump is formatted so that it can be printed directly.

REBLDDLI PROC only. Designates the log dataset when update intent is declared.

REBLDDLI PROC only. Designates the File-AID for IMS’s control database (&IXPDB) that is updated with DBD information.

Designates the DBD load library that contains the DBD load modules that define the databases used to update the CLT database. Multiple DBD load libraries may be concatenated.

Designates the library that contains File-AID for IMS/ISPF messages.

Designates the output class for the Online Control Information Update Summary

Report.

IXPREBLD Return Codes

An IXPREBLD execution return code (RC) appears in the output listing. A message appears on the Online Control Information Update Summary Report for return code 16

(system error).

B-4


The message listed on the Online Control Information Update Summary Report (Figure

B-1) indicates the program’s execution status.

Figure B-1. Online Control Information Update Summary Report

File-AID for IMS PAGE 1

DATE 03/15/07

TIME 14:54:01

ONLINE CONTROL INFORMATION UPDATE SUMMARY

D729 THE ONLINE CONTROL INFORMATION SEGMENT HAS BEEN SUCCESSFULLY REBUILT

****E N D O F R E P O R T****

Back up and Restore Control Databases

A backup and recovery plan should be developed at your installation to allow recovery from physical damage to the control databases. The CLT control database contains a large amount of information that is difficult to recreate in the event the database becomes unusable. The LTM control database, which contains temporary data used only for the duration of a terminal session, is easier to reestablish. The AUD control database may contain Audit Trail activity that has not yet been extracted by running the IXPATEXT program; therefore your installation could lose valuable Audit Trail information.

A job is provided in installation JCL member IMAGECPY to create image copies of the

CLT and AUD databases. You can use it or other JCL available at your installation for periodic backups. To restore the CLT and AUD databases from the image copies, use the job in installation JCL member RESTORE or other JCL available at your installation.

If your CLT and AUD control databases are VSAM files, they must be deleted and redefined before beginning the restore process. Use the job in installation JCL member

DELDEFV for this purpose.

No backup or restore JCL is provided for the LTM database. To repair a damaged LTM control database that is a VSAM file, delete and redefine it using the job in installation

JCL member DELDEFV. For OSAM files this step may be skipped. Then, initialize the database using the job in JCL member LTMINIT.

See Appendix D, “Batch DBD and XREF Update” for more information.

New File-AID Releases

As part of your maintenance agreement with Compuware, periodic upgrades with additional capabilities will be made available.

When installing a new release of File-AID for IMS, we recommend that you create new libraries to verify the installation.

Maintenance Considerations

B-5

CPU Changes

Disaster Recovery

Although Compuware’s products are CPU dependent, each product provides a 45-day window of use for disaster recovery.

To make File-AID for IMS available to users on a disaster recovery CPU, simply copy the

IMS PGMLIB and the control databases (CLT, LTM, AUD) to the new CPU.

Permanent CPU Changes

As documented in your File-AID for IMS license agreement, you must notify Compuware in writing of any CPU changes. A new password will be issued.

Please note that Compuware’s software is priced using IBM’s CPU Categories. This transfer request may result in additional license fee charges. Refer to your license agreement or contact your account manager.

B-6


C-1

Appendix C.

Load Module Summary

Appendix A.

Table C-1 lists the File-AID for IMS/DC load modules, along with their entry names,

attributes, and sizes.

Table C-1.

File-AID for IMS/DC Load Modules

IXDMAIN

IXDEDTS

IXDEDTL

IXDEDTF

IXDEDTU

IXDEDTI

PLICALLA RENT, 230K

IXDKEY

Note: IXDMAIN loads other modules as needed.

C-2


D-1

Appendix D.

Batch DBD and XREF Update

Appendix A.

To browse or edit your databases in the IMS/DC or CICS environment, the databases’

Data Base Definition (DBD) information must be made available to File-AID for IMS. File-

AID for IMS maintains an online CLT control database to store information about your databases’ segment definition and hierarchy.

The Batch DBD Update Facility retrieves the DBDs you specify from your DBD load library, extracts and formats relevant information, and updates this information to the

CLT control database for use by online File-AID for IMS programs.

You need to run the DBD Update Facility when:

• A database needs to be accessed in File-AID for IMS. The database’s DBD information must be added to the CLT control database.

• A DBD has changed. For example, segments are added to or deleted from a DBD.

These changes must be reflected on the CLT control database.

• A DBD no longer exists. This reference must be deleted from the CLT control database.

In addition to storing DBD information, the DBD Update Facility enables you to specify a

30-character DBD description. The description is also stored in the CLT control database and displayed on the DBD Member List screen in File-AID for IMS to make it easier for you to determine the appropriate database to process.

To browse or edit databases in Formatted mode using your existing segment layouts as templates over the segment’s data, the Cross-Reference Update program must be run to

allow File-AID for IMS access to these layouts. Refer to “Batch XREF Update Facility” on page D-7 for more information.

DBD Support

DBD load libraries must conform to the characteristics of a valid DBD load library, a partitioned dataset (DSORG=PO) with an undefined record format (RECFM=U).

Validation of the dataset’s logical record length or blocksize is not done.

Checkpoints

The DBD Update Facility can be run as either a batch DL/I, an IMS BMP, or a CICS shared database (SDB) program. In all three types of processing, a checkpoint call (CHKP) is issued after each control card is read. This process indicates to IMS that the program has reached a commit point. For BMP or SDB processing, the checkpoint also releases the resources that IMS has enqueued for the program. In the event of an abend, IMS backs out the database updates to the most recent checkpoint. The DBD Update Facility, however, does not have restart capability.

D-2


DBD Update JCL

The following JCL streams are copies of procedures (PROCs) supplied with File-AID for

IMS. Your installation may have modified these PROCs to meet installation standards.

DBDUPBMP–IMSBATCH Procedure

Figure D-1. DBDUPBMP–IMSBATCH JCL Procedure

//DBDUPBMP PROC RGN=2048K

//*

REGION SIZE

//* ****DBDUPBMP PARAMETERS****

//

//

//

//

PRINT='*',

RESLIB='XXXXXXX.RESLIB',

DBDLIB='XXXXXXX.DBDLIB',

PRINT OUTPUT SYSOUT CLASS

IMS RESLIB

IMS DBD LIBRARY

MLIBDSN='XXXXXXX.IXP.MLIB', File-AID for IMS/ISPF MLIB DSNAME

// IXPLOAD='XXXXXXX.IXP.LOAD', File-AID for IMS/ISPF LOAD LIBRARY

//* ****DFSRRC00 PARAMETERS

//

//

MBR=IXPDBDUP,

PSB=IXDUPLD,

PROGRAM NAME IN IXPLOAD

PSB NAME

//

//

//

//

IN=,OUT=,OPT=,

SPIE=,TEST=,DIRCA=,

PRLD=,STIMER=,CKPTID=,

PARDLI=,CPUTIME=,NBA=,

OBA=,IMSID=,AGN=





REFERENCE MANUAL //

//*

//*----------------------------------------------------------------

//* STEP1: BMP TO UPDATE File-AID for IMS/DC's CLT DATA BASE

//* WITH DBD INFORMATION

//*----------------------------------------------------------------

//STEP1 EXEC PGM=DFSRRC00,REGION=&RGN,

// PARM=(BMP,&MBR,&PSB,&IN,&OUT,

//

//

&OPT&SPIE&TEST&DIRCA,&PRLD,&STIMER,&CKPTID,

&PARDLI,&CPUTIME,&NBA,&OBA,&IMSID,&AGN)



// DD

//DFSRESLB DD

//SYSUDUMP DD

//

DSN=CEE.SCEERUN,DISP=SHR

DSN=&RESLIB,DISP=SHR

SYSOUT=&PRINT,DCB=(LRECL=121,RECFM=VBA,BLKSIZE=3129),

SPACE=(125,(2500,100),RLSE,,ROUND)

//IXPD1

//IXPMLIB

//SYSOUT

//

DSN=&DBDLIB,DISP=SHR

DSN=&MLIBDSN,DISP=SHR

SYSOUT=&PRINT

//*

//BMP EXEC DBDUPBMP

//*----------------------------------------------------------------

//*INSERT PROGRAM CONTROL CARDS AFTER THE SYSIN DD STATEMENT

//*----------------------------------------------------------------

//SYSIN

/*

DD *

//

DD

DD

DD

PEND

Batch DBD and XREF Update

D-3

DBDUPDLI–DLIBATCH Procedure

Figure D-2. DBDUPDLI–DLIBATCH JCL Procedure

//DBDUPDLI PROC RGN=2048K,

//*

//* **** DBDUPDLI PARAMETERS****

// PRINT='*',

//

//

//

//



PSBLIB='XXXXXXX.PSBLIB',

PROCLIB='XXXXXXX.PROCLIB',

DFSVSAM='DFSVSAMP', //

//*

//

//

IXPDB='XXXXXXX.IXDCLT',

MLIBDSN='XXXXXXX.IXP.MLIB',

// IXPLOAD='XXXXXXX.IXP.LOAD',


REGION SIZE


IMS RESLIB

IMS DBD LIBRARY

IMS PSB LIBRARY

IMS PROCEDURE LIBRARY

MEMBER IN PROCLIB

CONTAINING BUFFER POOL DATA

File-AID for IMS CLT DATA BASE

File-AID for IMS/ISPF MLIB DSNAME

File-AID for IMS/ISPF LOAD LIBRARY

//

//

//*

//

MBR=IXPDBDUP,

PSB=IXDUPLD,

PSB=IXCUPLD,

BUF=,SPIE=,TEST=,


DC PSB NAME

CICS PSB NAME


//

//

//

//

EXCPVR=,RST=,PRLD=,

SRCH=,CKPTID=,MON=,

LOGA=,FMTO=,IMSID=,

SWAP=,DBRC=,IRLM=,

IRLMNM=

PARAMETERS FOR MORE INFO



REFERENCE MANUAL

//

//*

//*----------------------------------------------------------------

//* STEP1: DLI JOB TO UPDATE File-AID for IMS/DC's CLT DATA BASE

//* WITH DBD INFORMATION

//*----------------------------------------------------------------


// PARM=(DLI,&MBR,&PSB,&BUF,

//

//

//

//STEPLIB DD



&IMSID,&SWAP,&DBRC,&IRLM,&IRLMNM)

DSN=&RESLIB,DISP=SHR

//

//

DD DSN=CEE.SCEERUN,DISP=SHR

DD DSN=&IXPLOAD,DISP=SHR





//SYSUDUMP DD SYSOUT=&PRINT,DCB=(LRECL=121,RECFM=VBA,BLKSIZE=3129),

// SPACE=(125,(2500,100),RLSE,,ROUND)



//*IXCCLTDD DD DSN=&IXPDB,DISP=OLD


//IXPMLIB

//SYSOUT

//

/DLI

DD

DD

PEND

DSN=&MLIBDSN,DISP=SHR

SYSOUT=&PRINT

EXEC DBDUPDLI

//*----------------------------------------------------------------

//* INSERT PROGRAM CONTROL CARDS AFTER THE SYSIN DD STATEMENT

//*----------------------------------------------------------------

//SYSIN DD *

/*

//

D-4


DBDUPSDB–SDB Procedure

Figure D-3. DBDUPSDB–SDB JCL Procedure

//DBDUPSDB PROC RGN=2048K,

//* **** DBDUPSDB PARAMETERS ****

//

//

//

//

PRINT='*',


REGION SIZE


IMS RESLIB

DBDLIB='XXXXXXX.DBDLIB', CICS DBD LIBRARY


//

//

//*

//*

IXPLOAD='XXXXXXX.IXP.LOAD',

DFHLIB='XXXXXXX.LOADLIB',


CICS LOAD LIBRARY

CONTAINING BATCH REGION

CONTROLLER MODULES

//* **** DFHDRP PARAMETERS ****

//

//

//

MBR=IXPDBDUP,

PSB=IXCUPLD,

CICS=


PSB NAME

CICS SYSTEM NAME

//*----------------------------------------------------------------

//*

//*

STEP1: SDB JOB TO UPDATE File-AID for IMS/CICS'

CLT DATA BASE WITH DBD INFORMATION

//*----------------------------------------------------------------

//STEP1 EXEC PGM=DFHDRP,REGION=&RGN,

//

//

PARM=('SSA=200,PGM=&MBR,PSB=&PSB,',

'CICS=&CICS,LANG=PLI,CWTO=Y,CMPAT=Y')



//DFHLIB DD DSN=&DFHLIB,DISP=SHR


//

//IXPD1


DD DSN=&DBDLIB,DISP=SHR



//

//SDB

PEND

EXEC DBDUPSDB

//*----------------------------------------------------------------

//* INSERT PROGRAM CONTROL CARDS AFTER THE SYSIN DD STATEMENT.

//*----------------------------------------------------------------

//SYSIN DD *

/*

//


D-5

DBD Update DD Statements

The following DD statements define the primary processing files required to run the DBD

Update program:

Table D-1.

DBD Update Program DD Statements


STEPLIB

DFSRESLB


Designates the IMS system dataset that contains the IMS nucleus and required action modules (&RESLIB). In DBDUPDLI and DBDUPBMP only.

DFHLIB

IMS

DFSVSAMP

SYSUDUMP

Designates the CICS system dataset that contains the batch region controller modules. In DBDUPSDB only.

Designates the IMS system datasets that contain the database description blocks

(&DBDLIB) and the program specification blocks (&PSBLIB). In DBDUPCLI PROC only.

Designates the dataset (&PROCLIB) and member (&DFSVSAM) that contain the control statements that describe the size and structure of the VSAM shared resource pool for File-AID for IMS’ CLT control database. The buffers must be large enough to accept the largest segment size in the CLT control database. In

DBDUPDLI PROC only.

Produces a dump of user areas. The dump is formatted so that it can be printed directly.

IEFRDER

IXDCLTDD,

IXCCLTDD

IXPD1

IXPMLIB

SYSOUT

SYSIN

Designates the log dataset when update intent is declared. In DBDUPDLI PROC only.

Designates File-AID for IMS’ CLT control database (&IXPDB) that is updated with

DBD information. In DBDUPDLI PROC only.

Designates the DBD load library that contains DBD load module(s) that define the database(s) specified on the program control cards. Multiple DBD load libraries may be concatenated.


Designates the output class for the DBD update summary report.

The program control cards follow this DD statement. Refer to page D-6.

Parameters


The DBDUPDLI, DBDUPBMP, and DBDUPSDB parameters specify the sysout class, load libraries, and dataset names used when the program executes. These are described in more detail in the preceding DD Statements section.


The DFSRRC00 parameters are the IMS execution time parameters. For more information on these parameters, refer to the IMS/ESA System Programming Reference Manual.

The DFHDRP parameters are the CICS shared database execution time parameters. For more information on these parameters, refer to the CICS/ESA Installation Guide.

D-6


Program Control Cards

The program control cards you specify trigger DBD Update processing. They are entered after the SYSIN DD statement in a free form, positional format. Control Card fields can be coded anywhere in columns 1 through 72 of your control card, separated by at least one space.

Action

DBD Name

Description

This field must be specified first.

UPDATE, UPD, U Add or change DBD information to the CLT control database.

DELETE, DEL, D Delete DBD information from the CLT control database.

The name of the DBD whose information is to be updated in or deleted from the CLT control database. This field must follow the Action field for both UPDATE and DELETE.

A 30-byte field that can be used to describe each DBD. This field is optional for an

UPDATE action. If entered, it must follow the DBD Name field. It is not applicable to a

DELETE action.

The following example illustrates how program control cards can be entered.

//SYSIN DD *

UPDATE PORDR PHYSICAL ORDER DATA BASE

UPDATE LORDR LOGICAL ORDER DATA BASE

DELETE PCUST

DBD Execution Return Codes

A DBD update execution return code (RC) appears in the output listing. For return codes

4, 8, and 16, a message appears on the DBD Update Summary Report under the column heading Message. In general, the return codes can be summarized as follows:

RC Explanation

0

Job ran to completion


4

Job may have ended prematurely

8

16

Severe error occurred

Error Description

None

• Segment to delete not found

• Segment/DBD size error

• Control card related error

• DBD size error

System error

Summary Report

The DBD Summary Report is printed by the DBD Update job. The ACTION, DBD NAME, and DESCRIPTION shown on the report correspond to the control cards that you specified in your JCL. The rightmost column is for informational messages that describe the status of the update and/or delete processing.


D-7

Figure D-4. DBD UPDATE SUMMARY FOR ONLINE ACCESS

File-AID for IMS BD UPDATE SUMMARY FOR ONLINE ACCESS PAGE 1

DATE 03/16/07

TIME 16:37:13

ACTION DBD NAME DESCRIPTION MESSAGE

----------------------------------------------------------------------------------------------

UPDATE PORDR PHYSICAL ORDER DATA BASE D721 DBD "PORDR" UPDATED;TO INCLUDE LAYOUT CHANGES-RUN XREF UPDATE

UPDATE LORDR LOGICAL ORDER DATA BASE D724 DBD "LORDR" ADDED; TO USE LAYOUTS ONLINE - RUN XREF UPDATE

DELETE PPART PHYSICAL PART DATA BASE D726 DBD "PPART" DELETED

**** E N D O F R E P O R T ****

Batch XREF Update Facility

To edit or browse a database using Formatted mode in the IMS/DC or CICS environment, segment layout information must be made available to File-AID for IMS. File-AID for IMS maintains an online CLT control database to store information pertaining to DBD segments and the segment layout(s) that defines each segment’s data.

The segment/layout cross reference (XREF) that you create in File-AID for IMS/ISPF

Option 7 associates segment layouts with segment types defined in a DBD. The Batch

XREF Update program uses this XREF to update the CLT control database. For more information, refer to the Segment/Layout/Cross Reference chapter in the File-AID for

IMS/DC/CICS Reference Manual.

Segment names defined in a DBD can have corresponding segment layouts that define the segment data. The XREF Update program retrieves the segment layout from your segment layout library and updates the CLT control database with this information for use by File-AID for IMS online programs.

You need to run the Batch XREF Update program when:

• A new XREF member has been created. Segment layout and segment information must be added to the CLT control database.

• An existing XREF member has been changed. For example, segments are added to or deleted from a DBD. The corresponding segment layout information must be added to/deleted from the CLT control database.

• A segment layout changes. These changes must be reflected on the CLT control database.

• A DBD has been deleted from an XREF member. Segment layout and segment information must be deleted from the CLT control database.

If your databases’ DBD information has not been added to the CLT control database, the

DBD Update Facility, described earlier in this chapter, must be run before a segment’s layout information can be added by the XREF Update Facility.

Segment Layout Datasets

The segment layout dataset contains the COBOL or PL/I segment layouts used in many

File-AID for IMS functions. The segment layout dataset can be one of three types:

Table D-2.

Segment Layout Dataset Types

Partitioned dataset PO F, FB 80

D-8


Table D-2.

Segment Layout Dataset Types

Note: Must conform to the requirements for a valid CA-PANVALET/LIBRARIAN file.

The segment layout can be a separate COPYLIB member or can be hard-coded in a

COBOL or PL/I program. If the layout is in a program or if a COPYLIB member contains multiple segment layouts, you can isolate the specific layout, or portion of a layout, that

File-AID for IMS should use by specifying a starting data-name. In these two cases, if you do not specify a starting data-name, File-AID for IMS will use every layout found in the program or COPYLIB member to format the data, treating the second through last layouts as redefinitions of the first.

When you create a segment/layout XREF in File-AID for IMS/ISPF Option 7, you associate existing segment layouts with the segment types in your database. File-AID for IMS requires that your segment layouts follow certain coding rules. Refer to the appropriate

COBOL Language Support or PL/I Language Support topic later in this chapter.

Checkpoints

The XREF Update Facility can be run as either a batch DL/I, IMS BMP, or CICS shared database (SDB) program. In all three types of processing, a checkpoint (CHKP) call is issued after each control card is read. This indicates to IMS that the program has reached a commit point. For BMP or SDB processing, the checkpoint also releases the resources that IMS has enqueued for the program. In the event of an abend, IMS backs out the database updates to the most recent checkpoint. The XREF Update Facility, however, does not have restart capability.

XREF Update JCL

The following JCL streams are copies of the procedures (PROCs) supplied with File-AID for IMS. Your installation might have modified these PROCs to meet installation standards.


D-9

XRFUPBMP–IMSBATCH Procedure

Figure D-5. XRFUPBMP–IMSBATCH JCL Procedure

//XRFUPBMP PROC RGN=2048K,

//*

REGION SIZE

//* **** XRFUPBMP PARAMETERS ****

//

//

//

PRINT='*',



IMS RESLIB

XRFDSN='XXXXXXX.IXP.XREF', File-AID for IMS/ISPF XREF DSNAME

//

//

//

//*


IXPLOAD='XXXXXXX.IXP.LOAD', File-AID for IMS/ISPF LOAD LIBRARY

CBLDSN1='XXXXXXX.COBOL1',


COBOL LAYOUT LIBRARY

ADDITIONAL COBOL LAYOUT

//*

//*

//*

//*

PLIDSN1='XXXXXXX.PLI1',


LIBRARY (OPTIONAL)

PL/I LAYOUT LIBRARY

ADDITIONAL PL/I LAYOUT

LIBRARY (OPTIONAL)


//

//

//

//

//

//

//

MBR=IXPXRFUP,

PSB=IXDUPLD,

IN=,OUT=,OPT=,

SPIE=,TEST=,DIRCA=,

PRLD=,STIMER=,CKPTID=,

PARDLI=,CPUTIME=,NBA=,

OBA=,IMSID=,AGN=


PSB NAME


PARAMTERS FOR MORE INFO



REFERENCE MANUAL

//*----------------------------------------------------------------

//*STEP1: BMP JOB TO UPDATE File-AID for IMS/DC's CLT DATA BASE

//* WITH XREF INFORMATION

//*----------------------------------------------------------------


//

//

PARM=(BMP,&MBR,&PSB,&IN,&OUT,

&OPT&SPIE&TEST&DIRCA,&PRLD,&STIMER,&CKPTID,

// &PARDLI,&CPUTIME,&NBA,&OBA,&IMSID,&AGN)






//

//IXPFD DD


DSN=&XRFDSN,DISP=SHR

//IXPC1

//*IXPC2

//*IXPC1

//*IXPC2

DD

DD

DD

DD

DSN=&CBLDSN1,DISP=SHR


DSN=&PLIDSN1,DISP=SHR




//

//*

PEND

//BMP EXEC XRFUPBMP

//*----------------------------------------------------------------

//* INSERT CONTROL CARDS AFTER THE SYSIN DD STATEMENT.

//*----------------------------------------------------------------

//SYSIN

/*

DD *

//

D-10


XRFUPDLI–DLIBATCH Procedure

Figure D-6. XRFUPDLI–DLIBATCH JCL Procedure

//

//

//

//

//XRFUPDLI PROC RGN=2048K,

//* **** XRFUPDLI PARAMETERS****

//

//

PRINT='*',



PSBLIB='XXXXXXX.PSBLIB',

REGION SIZE


IMS RESLIB

IMS DBD LIBRARY

IMS PSB LIBRARY

PROCLIB='XXXXXXX.PROCLIB', IMS PROCEDURE LIBRARY

DFSVSAM='DFSVSAMP', PROCLIB MEMBER CONTAINING

//*

//

//

//

IXPDB='XXXXXXX.IXDCLT',

BUFFER POOL DATA

File-AID for IMS/DC CLT DB

XRFDSN='XXXXXXX.IXP.XREF', File-AID for IMS/ISPF XREF DSNAME


IXPLOAD='XXXXXXX.IXP.LOAD', File-AID for IMS/ISPF LOAD LIBRARY //

//

//*

//*


CBLDSN2='XXXXXXX.COBOL2'



LIBRARY (OPTIONAL)

PL/I LAYOUT LIBRARY //*

//*



//*

//*DFSRRC00 PARAMETERS


LIBRARY (OPTIONAL)

//

//

//

//

MBR=IXPXRFUP,

PSB=IXDUPLD,

BUF=,SPIE=,TEST=,

EXCPVR=,RST=,PRLD=,


PSB NAME


PARAMETERS FOR MORE INFO

//

//

SRCH=,CKPTID=,MON=,

LOGA=,FMTO=,IMSID=,



// SWAP=,DBRC=,IRLM=,IRLMNM= REFERENCE MANUAL

//*----------------------------------------------------------------

//

//

//

//

//*

//*

STEP1: DLI JOB TO UPDATE File-AID for IMS'S CLT DATA

BASE WITH XREF INFORMATION

//*----------------------------------------------------------------


PARM=(DLI,&MBR,&PSB,&BUF,



&IMSID,&SWAP,&DBRC,&IRLM,&IRLMNM)

//STEPLIB

//


DD DSN=CEE.SCEERUN,DISP=SHR



//IMS

//

DD DSN=&DBDLIB,DISP=SHR

DD DSN=&PSBLIB,DISP=SHR



//

//IEFRDER


DD DUMMY,DCB=BLKSIZE=100


//*IXCCLTDD DD DSN=&IXPDB,DISP=OLD

//IXPFD

//IXPC1

//*IXPC2

//*IXPC1

DD

DD

DD

DD





//*IXPC2

//IXPMLIB

//SYSOUT

//

//DLI EXEC XRFUPDLI

//*----------------------------------------------------------------


//*----------------------------------------------------------------

//SYSIN

/*

DD *

//

DD DSN=&PLIDSN2,DISP=SHR

DD DSN=&MLIBDSN,DISP=SHR

DD SYSOUT=&PRINT

PEND


D-11

XRFUPSDB–SDB Procedure

Figure D-7. XRFUPSDB–SDB JCL Procedure

//XRFUPSDB PROC RGN=2048K,

//*

REGION SIZE

//* **** XRFUPSDB PARAMETERS ****

//

//

//

//

PRINT='*',


XRFDSN='XXXXXXX.IXP.XREF',


IMS RESLIB

File-AID for IMS/ISPF XREF DSNAME


//

//

//*

//*

IXPLOAD='XXXXXXX.IXP.LOAD',

DFHLIB='XXXXXXX.LOADLIB',


CICS LOAD LIBRARY

CONTAINING BATCH REGION

CONTROLLER MODULES

//

//*

//*

//*



LIBRARY (OPTIONAL)




//*

//*


LIBRARY (OPTIONAL)

PL/I LAYOUT LIBRARY


//* **** DFHDRP PARAMETERS ****

//

//

//

MBR=IXPXRFUP,

PSB=IXCUPLD,

CICS=


PSB NAME

CICS SYSTEM NAME

//*----------------------------------------------------------------

//*

//*

STEP1: SDB JOB TO UPDATE File-AID for IMS/CICS'

CLT DATA BASE WITH XREF INFORMATION

//*----------------------------------------------------------------

//STEP1 EXEC PGM=DFHDRP,REGION=&RGN,

//

//

PARM=('SSA=200,PGM=&MBR,PSB=&PSB,',

'CICS=&CICS,LANG=PLI,CWTO=Y,CMPAT=Y')



//DFHLIB DD DSN=&DFHLIB,DISP=SHR

//SYSUDUMP DD SYSOUT=&PRINT,DCB=(LRECL=121,RCFM=VBA,BLKSIZE=3129),

//

//IXPFD DD



//IXPC1

//*IXPC2

//*IXPC1

//*IXPC2

DD DSN=&CBLDSN1,DISP=SHR

DD DSN=&CBLDSN2,DISP=SHR





//

//SDB

PEND

EXEC XRFUPSDB

//*

//*----------------------------------------------------------------


//*----------------------------------------------------------------

//SYSIN

/*

DDT*

//

XREF Update DD Statements

The following DD statements define the primary processing files required to run the

XREF Update program.

D-12


Table D-3.

XREF Update Program DD Statements


STEPLIB

DFSRESLB


Designates the IMS system dataset that contains the IMS nucleus and required action modules (&RESLIB). In XRFUPDLI and XRFUPBMP PROCs only.

DFHLIB

IMS

DFSVSAMP

SYSUDUMP

Designates the CICS system dataset that contains the batch region controller modules. In XRFUPSDB only.

Designates the IMS system datasets that contain the database description blocks

(&DBDLIB) and the program specification blocks (&PSBLIB). In XRFUPDLI PROC only.

Designates the dataset (&PROCLIB) and member (&DFSVSAM) that contain the control statements that describe the size and structure of the VSAM shared resource pool for File-AID for IMS’ CLT control database. The buffers must be large enough to accept the largest segment size in the CLT control database. In

XRFUPDLI PROC only.

Produces a dump of user areas. The dump is formatted so that it can be printed directly.

IEFRDER

IXDCLTDD,

IXCCLTDD

IXPFD

IXPC1

IXPC2

IXPMLIB

SYSOUT

SYSIN

Designates the log dataset when update intent is declared. In DBDUPDLI PROC only.

Designates File-AID for IMS’ CLT control database (&IXPDB) that is updated with

XREF information. In XRFUPDLI PROC only.

DesignatesFile-AID for IMS/ISPF’s segment/layout cross reference dataset

(&XRFDSN).

Designates the segment layout dataset (&CBLDSN1 or &PLIDSN1).

Designates an additional segment layout dataset (&CBLDSN2 or &PLIDSN2), if needed.


Designates the output class for the XREF Update Summary Report.

The program control cards follow this DD statement. Refer to the topic Program

Control Cards later in this section.

Parameters


The XRFUPDLI, XRFUPBMP, and XRFUPSDB parameters specify the sysout class, load

libraries, and dataset names needed to run the XREF Update program. Refer to “DBD

Update DD Statements” on page D-5.


The DFSRRC00 parameters are the IMS execution time parameters. For more information on these parameters, refer to IBM’s IMS System Programming Reference Manual.

The DFHDRP parameters are the CICS shared database execution time parameters. For more information on these parameters, refer to IBM’s CICS Installation Guide.

Option Control Card

The option control card, if specified, must be the first control card entered after the

SYSIN DD statement. The option control card designates program language (for multilanguage sites), layout library organization (PANVALET and/or LIBRARIAN), and update.


D-13

The option limit control card is not required if your installation is a single language site, layouts are not stored in PANVALET or LIBRARIAN. Use the update limit default value of

NOLIMIT.

Options can be coded anywhere in columns 1 through 72 of your control card, separated by at least one space. The Action field is required and must be specified first. All other sfields are optional and can be entered in any order.

Action

Language

OPTION, OPT, O

Only ONE language can be specified:

COBOL, COB

PLI, PL1, PL/I, PL/1

Layout Organization Both CA-PANVALET and CA-LIBRARIAN can be specified:

Update Limit

PANVALET, PAN

LIBRARIAN, LIB

Limits the update of the segment layout references in the CLT control database.

Refer to the Segment/Layout/Cross Reference chapter in the

File-AID for

IMS/DC/CICS Reference Manual

.

NOLIMIT, NOLMT

LIMIT, LMT.

Updates all segment layout references in the CLT control database that uses the same layout in the XREF member and DBD name defined in the program control card (default)

Updates only segment layout references in the CLT control database for the DBD and XREF member specified on the program control card.

A significant decrease in run time will occur when using the LIMIT option but only the DBDs specified will be updated.

The program control cards you specify trigger XREF update processing. They are coded after the SYSIN DD statement or the OPTION card, if specified, in a free form, positional format. Program Control Card fields can be coded anywhere in columns 1 through 72 of your control card, separated by at least one space.

Action

XREF MBR

DBD Name

This field must be specified first.

UPDATE, UPD, U

Add or change segment layout information for use in the

IMS/DC or CICS environment .

DELETE, DEL, D

Delete segment layout references no longer needed in the

IMS/DC or CICS environment.

The name of the File-AID for IMS/ISPF segment/layout cross reference PDS member that contains the references to new or changed segment layouts. For an UPDATE action, this field must follow the Action field. This field is not applicable to a DELETE action.

The name of the DBD in the File-AID for IMS/ISPF XREF member. For an UPDATE action, this field must follow the XREF MBR field. The DBD NAME can be entered as an asterisk to update segment layout references for all DBDs within an XREF member. For a DELETE action, this field must follow the Action field. Specify the DBD whose segment layout references are to be deleted from the CLT control database

In the following example, the OPTION control card is entered for segment layouts in a

PANVALET library. The second card specifies that segment layouts for DBD LORDR in the segment/layout cross reference (XREF) member ORDRCUST are to be used to update the

File-AID for IMS CLT control database. The third card specifies that references to segment layouts for DBD PCUST are to be deleted from the File-AID for IMS CLT control database.

//SYSIN DD *

OPTION PANVALET COBOL

UPD ORDRCUST LORDR

DELETE PCUST

D-14


XREF Execution Return Codes

An XREF update execution return code (RC) appears in the output listing. For return codes 4, 8, and 16, a message appears on the XREF Update Summary Report under the column heading Message. In general, the return codes can be summarized as follows:

RC Explanation

0



4

Job may have ended prematurely

8

16

Severe error occurred

Error Description

None

• Segment to delete not found

• Segment/DBD size error

• Control card related error

• DBD size error

System error

Summary Report

The XREF Summary Report shown in Figure D-8 on page D-15 is printed by the XREF

Update job.

The first section of the report lists the segment/layout cross reference dataset and the segment layout dataset that you specified in your JCL.

The second section details all database update activity. The ACTION, XREF MEMBER (for an UPDATE action), and DBD NAME shown on the report correspond to the control cards that you specified in your JCL. Also shown are the segment names and their corresponding source library members associated with the specified DBD name (and

XREF member for UPDATE). The rightmost column on the report is for informational messages that describe the status of the update and/or delete processing.

When a segment’s data is defined by more than one segment layout, *MULT-RTV* is shown in the MBR column. The individual segment layout members and the record type values that define the segment’s format are shown in the Message column. Refer to the

Segment/Layout/Cross Reference chapter in the File-AID for IMS/DC/CICS Reference Manual for more information on multiple record type values.

One segment layout is often used to describe a segment that is defined in multiple DBDs.

If this segment layout changes, the changes will be updated for all DBDs with segments that reference the changed layout, unless the LIMIT option is used on the option card.

For example, in the sample report in Figure D-8 on page D-15, DBD PORDR defines the

segment ORDR010 in the physical view of the database. DBD LORDR defines the same segment ORDR010 in its logical view of the database. The identical COBOL layout describes the ORDR010 segment in both DBDs. On the report you can see the request to update DBD LORDR within the ORDRCUST XREF member. Notice that COBOL member

ORDR010 was updated on File-AID for IMS’ CLT control database for segment ORDR010 within the LORDR DBD. In addition, the ORDR010 COBOL information was also updated for segment ORDR010 within the PORDR DBD. File-AID for IMS automatically updates all segment layout information on the CLT control database that is generated from the same segment layout dataset and member, unless the default is overridden by using the LIMIT option.


D-15

Figure D-8. Seg/Layout XREF and COBOL Layout Update Summaries

File-AID for IMS SEG/LAYOUT XREF AND COBOL LAYOUT UPDATE SUMMARY PAGE 1

DATE 2007-07-07

TIME 16:59:45

SEG/LAYOUT XREF DSN:

COBOL LAYOUT DSN:

CW.FISAMP.XREF

CW.FISAMP.COBOLLIB

ACTION XREF MBR DBD NAME SEG NAME COBOL MBR MESSAGE

------------- -------- -----------------------------------------------------------------------

UPDATE LORDR LORDR ORDR010

ORDR020

ORDR010

*MULT-RTV*

D714 COBOL MBR "ORDR010" UPDATED

D715 COBOL MBR "ORDR020" UPDATED;RTV1=PO

ORDR030

ORDR040

ORDR030

ORDR040

ORDRCUST ORDR051

D715 COBOL MBR "ORDR021" UPDATED;RTV1=SC

D715 COBOL MBR "ORDR022" UPDATED;RTV1=WO;RTV2=IN

D715 COBOL MBR "ORDR022" UPDATED;RTV1=WO;RTV2=OV




DELETE

THE FOLLOWING DBD(S) AND SEGMENT(S) REFERENCE THE SAME COBOL MEMBER(S):

PORDR ORDR010 ORDR010 D716 MATCHING COBOL MBR "ORDR010" WAS ALSO UPDATED

ORDR020 *MULT-RTV* D728 MATCHING COBOL MBR "ORDR020" UPD;RTV1=WO

D728 MATCHING COBOL MBR "ORDR021" UPD;RTV1=WO

ORDR030

ORDR040

ORDR030

ORDR040

D728 MATCHING COBOL MBR "ORDR022" UPD;RTV1=WO;RTV2=IN

D728 MATCHING COBOL MBR "ORDR022" UPD;RTV1=WO;RTV2=OV

D716 MATCHING COBOL MBR "ORDR030" WAS ALSO UPDATED

D716 MATCHING COBOL MBR "ORDR040" WAS ALSO UPDATED

PCUST CUST020

CUST010

CUST020

CUST010

VORDR050 ORDR050

D714 COBOL MBR "CUST020" DELETED

D714 COBOL MBR "CUST010" DELETED

D714 COBOL MBR "ORDR050" DELETED

**** E N D O F R E P O R T ****

D-16


Index

A

ACB control blocks, 2-23

access additional databases and layouts, 2-46

Acrobat PDF online documentation, xv

aliases list, 2-44

allocate

control databases, 2-26

assemble

ACB control blocks, 2-23

DBD source code, 2-16

PSB source code, 2-20

sample security exit, 2-38

assemble and link source code, 2-10

assemble installation parameters, 2-3

AUD control data base

DBD tailoring, 1-4

PSB tailoring, 1-6

sample, 2-15

AUD control database

back up and restore, B-4

AUD data base, 1-6

audit trail, 1-4

DBD exception list, 2-8

audit trail installation option, 2-3

B

batch DBD update facility

about, D-1 checkpoints, D-1

checkpoints (XREF), D-8

JCL

about, D-8

DBDUPBMP, D-2

DBDUPDLI, D-3

DBDUPSDB, D-4

BookManager softcopy documentation, xvi

C

CLT control data base

about, 1-9


DBD update (IXPDBDUP), 1-9

missing or invalid control segment, B-2

PSB tailoring, 1-6

rebuild control segment (IXPREBLD), 1-9, B-2

sample, 2-15

XREF update (IXPXRFUP), 1-9

control data base

DBD changes, B-1 segment size changes, B-1

control database


COPYLIB, D-8

create aliases, 2-43

customer support, xvi

customer support web site, xv

D

DBD (data base description)

JCL, D-2

member list screen

summary report, D-6

support, D-1

update facility, D-2


DBD tailoring

about, 1-4

AUD control data base, 1-4

AUD control database, B-4

BYTE operand, 2-14

CLT control data base, 1-4, 1-9, B-4

for MAXSEGSZ, 2-6

LTM control data base, 1-4, B-4

samples, 2-15

SIZE parameter, 2-14 third and fourth parameters, 2-14

DBDUPBMP

See batch DBD update facility

DBDUPDLI


DBDUPSDB


ddnames


define environment, 2-1

DL/I calls

limiting DL/I calls, 1-10

LMTCALLS, 1-10

F

Fast Path data base, 1-9

File-AID for IMS/ISPF, 1-9

File-AID releases, B-4

FrontLine support web site, xv

G

generate

PSB control blocks, 2-19

H

HTML documentation, xvi

I-1

I-2


I

IMS message queues, 1-12

IMS system definition

about, 1-7

APPLCTN macro, 1-7, 1-9

defining environment, 2-1

INIT.DB command, 1-8

INIT.DBDS command, 1-8

TRANSACT macro, 1-7, 1-9

installation

change installation parameters, B-2

jobs

@FDACB, 2-24

@FDALOCO, 2-27

@FDALOCV, 2-27

@FDDBD, 2-17

@FDPRM, 2-3, 2-9

@FDPSB, 2-21

@FDSCXT, 2-39

@FDTRAIN, 2-34

DCP02, B-2

JCLALIAS, 2-43, B-2

JCLMFS, 2-10

JCLPERML, 2-5

JCLSCXT, A-1, B-1

steps

access additional databases and segment layouts,

2-46

access installation panel, 2-1

allocate control databases, 2-26

assemble and link installation parameters, 2-3

assemble and link MFS source code, 2-10

assemble DBD source code, 2-16

assemble PSB, 2-20

assemble/link sample security exit, 2-38

copy installation CLIST, 2-1

copy training files, 2-33

create aliases to the main load module, 2-43

define environment, 2-1

generate ACB control blocks, 2-23

modify DBD source code, 2-13

modify PSBs, 2-19

verify installation, 3-1

installation jobs

@FDACB, 2-24

@FDALIAS, 2-45

@FDALOCO, 2-27

@FDALOCV, 2-27

@FDDBD, 2-17

@FDIPRM, 2-9

@FDPSB, 2-21

@FDSCXT, 2-39

@FDTRAIN, 2-34

DCP02, B-2

JCLALIAS, 2-43, B-2

JCLIPRMS, 1-10

JCLMFS, 2-10

JCLPERML, 2-5

JCLSCXT, A-1, B-1

installation output, 1-12

installation parameter

aliases list, 2-44

ALL/NONE indicator, 2-7

audit trail DBD name, 2-6

audit trail feature, 2-3

audit trail indicator, 2-7

caps mode, 2-4 code page, 2-4


dependent segments, 2-6

end MFS MOD name, 2-5

IMS version, 2-4 integrity check, 2-4 limit DB calls, 2-4

maximum segment size, 2-6

MFS MOD name prefix, 2-5 program name prefix, 2-5

Internet, Compuware WWW address, xvi

L

load modules, C-1

LTM control data base


DBD tailoring, 1-4

PSB tailoring, 1-6

sample, 2-15

M

MFS tailoring, 1-10

modify

DBD source code, 2-13

N

naming conventions

about, 1-3

MFS format names, 1-3 program names, 1-3 transaction names, 1-3

new releases, B-4

O

option control card, D-12

P

PDF documentation, xv

product support, xvi

program control cards, D-6, D-13

PSB tailoring

about, 1-6

CLT data base, 1-6

for Fast Path databases, 1-9

LTM data base, 1-6

R

rebuild control segment (IXPREBLD)

DD statements, B-3 return codes, B-3

resource usage, 1-12

S

sample security exit, 2-38

security

resource access, 1-11 resource protection approaches, 1-11

security exit

add or change, B-1

segment

multiple record type

about, D-14

segment layout support, D-7

softcopy documentation, xv

space allocation, 1-9

summary of changes, xi

summary report, D-14

T

training files, 2-33

V

verify installation, 3-1

W

World Wide Web, Compuware address, xvi

I-3

I-4


File-AID for IMS/DC Installation Guide

File-AID for IMS/DC

Installation Guide

ii

File-AID for IMS Customer Support

1-800-538-7822

iii

Contents

vi

vii

ix

xi

Summary of Changes

What’s New in Release 7.5

Parameters

Enhanced and Expanded Parameters Selection Menu

Option 1 System Parameters now allows you to control the checkpoint frequency used

Option 2 Modify DLI Parameters is a new option that allows you to override DLI

Option 3 Modify BMP Parameters is a new option that allows you to override BMP

Option 4 IMS DLI Datasets is a new option that allows you to override IMS datasets

Option 5 Temporary Dataset Allocations is a new option that allows you to control the

User ID Variable to Define Dataset Concatenations

Browse and Edit

Unicode Support for DBCS Character Data

Optional Delete Confirmation in Edit

xii

Extract and Load

Extract Using Concatenated Keys

Save Selection Criteria with New Name

Rename DBDs During Load Processing

Write Records Discarded During Load to a File

Utilities

Database Hierarchy Displayed from Utilities Menu

Miscellaneous

Restrict Processing to One or More HALDB Partitions

New Commands for Release 7.5

BMP : The BMP command displays the “File-AID for IMS – Modify BMP Parameters”

DLI : The DLI command displays the “DLI Parameters Screen” screen, where you can

SAVEAS : When editing selection criteria, including temporary selection criteria,

TMP : The TMP command displays the “Temporary Dataset Allocations” screen, where

xiii

VHEX : The VHEX command displays the “Edit Unicode Field” screen for the selected

H (Hierarchy) : The H (Hierarchy) line command graphically displays the structure of

What’s New in Release 7.4

Secondary Index Support for Extract and Selection Criteria

Unicode UTF-16 Support in Edit and Browse

A record layout is required to recognize data as Unicode data. Therefore, Compuware recommends to edit Unicode data only in Formatted display mode.

Audit Trail User Exit

What’s New in Release 7.3

Expanded Data Privacy Management via File-AID/EPDM

xiv

Product Delivery

xv

Introduction

Related Publications

FrontLine Support Website

Online Documentation

xvi

World Wide Web

Getting Help

File-AID for IMS Customer Support

http://www.compuware.com/support.

Client No._____________________________________

1-1

Chapter 1.

Overview

License Management System

IMPORTANT:

1-2

System Requirements

Execution Environment

Installation Configuration

Single Transaction Configuration

Multiple Transaction Configuration

1-3

Naming Conventions

1-4

Audit Trail Feature

DBD Tailoring

1-5