Administration of IMSRon Bisceglia

Rocket Software

November 2020

Session 6AY

1

https://twitter.com/gseukchttps://www.linkedin.com/groups/1741877https://www.facebook.com/pages/Guide-Share-Europe-UK-Region/174907039241415

• Message Queues

• Local and Shared

• IMS Coupling Facility Structures

• Checkpointing

• Considerations for journey to IMS Managed ACBs

Agenda

2

Message Queues

3

Message Queue Issues

• Hitting message queue limitations can cause IMS outages

• Defend the message queues• Runaway/looping ISRTs from application

• High input message arrival rates

• Simplistic ways to implement some protection• SEGNO on TRANSACT definition

• DFSQSPC0/DFSQSSP0 exits

4

Message Queue Issues

• SEGNO• Option on TRANSACT macro

• UPD TRAN ttt SET(SEGNO(x))

• /ASS TRAN ttt SEGNO x

• Default is 0 (No limit)

• ISRT above SEGNO limit receives ‘A7’ status code

• Only applicable for message driven applications

• Recommended to specify for all transactions• A fairly low number should cover most situations

• How to handle exceptions may be application dependent

5

Message Queue Issues• Queue Space Notification Exits

• DFSQSPC0 (non-shared queues)• DFSQSSP0 (shared queues)

• The number of records currently in use exceeds upper threshold percentage value of the maximum number assignable before initiation of automatic shutdown.

• The number of records currently in use falls below the lower threshold percentage value of the same maximum.

• By default IMS sets an upper threshold value of 75 percent, and a lower threshold value of 60 percent. You can modify these values by using the QTU and QTL parameters of the IMS procedure.

• Capability• Warning

• Issue message at threshold utilization• QTL/QTH

• Action• Prevent ISRTs when appropriate

• Samples provided by IMS

6

Non-Shared Queue Overflow ProtectionIMS Queue Control Facility provides three methods for implementing queue overflow protection. They are listed in the order of their development through progressive releases of IMS Queue Control Facility. Each subsequent method was designed to provide more capability and flexibility in configuring queue overflow protection.

Type 1: Queue space notification exit (DFSQSPC0)• What QCF adds with this type of protection is the capability to stop dependent regions (BMPs and transactions) and

have message issued to message sender (terminals, OTMA, APPC, MSC)

Type 2: Queue overflow protection using threshold settings to define queue space partitions• Four analysis boundaries are defined using the IMS threshold template. • Type 2 protection provides analysis to detect excessive queue activity for total and specific IMS entities. (APPL, APPC,

MSC, DC, OTMA) • Actions that can be implemented when these partition boundaries are exceeded include WAIT, WTO, STOP, and

UNLOAD

Type 3: Queue overflow protection using AREA and FAILSAFE settings to define queue space partitions• Type 3 protection provides analysis to detect excessive queue activity for total and specific IMS entities. (same as Type

2 but with more partitions)

• AREA protection analyzes specific queue usage. Analysis is performed on the accumulation of the queue activity due to a specific IMS process. In AREA overflow protection, the queue can be divided into up to ten AREA partitions.

• FAILSAFE protection analyzes total queue utilization. Analysis is performed on the accumulation of the queue activity due to all IMS processes. In FAILSAFE overflow protection, the queue can be divided into up to ten FAILSAFE partitions.

• Actions that can be implemented when these partition boundaries are exceeded include WAIT, WTO, STOP, ABEND and UNLOAD. 7

Working with the Messages on the Queue

/DIS POOL QBUF

/DIS POOL QBUF STAT

8

Working with the Messages on the Queue

9

Status of Local Queues

10

Query Messages on Local Queues

11

Act on Messages on Local Queues

12

After Query panel, user can gather additional information about the messages on the queues such as message destinations, the queue type, the message count, among others.

When a user selects one of the destination names, then a new panel will be appear displaying the source names, the date & time, etc.

Lastly, the user can also gather the prefix data of specific messages.

Shared Queue Buffer Overflow Protection

• What does it do?• Protect IMS control region from x78 abends (out of storage) caused by run-away/looping

applications

• Features• Inactive mode – turn off overflow protection feature (default)

• Report mode – help customers study local buffer usage

• Enforce mode – automatic actions against incoming messages to avoid local buffer out of storage condition

• What does it NOT do?• Overflow protection against SQ structure overflow

13

Implementation Details

• Exploit Queue Space Notification Exit DFSQSSP0• Does not interfere with dynamic buffer expansion/compressions by IMS

• Terminates unit of work as follows:• ‘A7’ status code if message is from application

• DFS0777I if message from LU 6.2 conversation

• DFS1289I if message is from OTMA

•Requirements• IMS QBUFMAX parameter must be set for Enforce mode

• Require IMS Tools Generic Exits common code to allow co-existence of multiple DFSQSSP0 exits

14

Sample Messages

• Report Mode (2 minutes interval reporting)• 07.45.10 JOB00123 GJE9010I DFSQSSP0 REPORT MODE: 22 BUF 11 PCT IMS1

• 07.47.10 JOB00123 GJE9010I DFSQSSP0 REPORT MODE: 29 BUF 15 PCT IMS1

• 07.49.10 JOB00123 GJE9010I DFSQSSP0 REPORT MODE: 36 BUF 18 PCT IMS1

• Large buffer users (periodic messages):• 08.22.08 JOB00191 GJE9050I DFSQSSP0 LARGE USER: 17 BUF FOR BMP255 IMS1

• 08.22.08 JOB00191 GJE9050I DFSQSSP0 LARGE USER: 12 BUF FOR BMP255 IMS1

• Warning Level• 08.31.20 JOB00191 GJE9020I DFSQSSP0 WARNING MODE: 26 BUF 13 PCT IMS1

• 08.34.20 JOB00191 GJE9020I DFSQSSP0 WARNING MODE: 27 BUF 14 PCT IMS1

• 08.37.21 JOB00191 GJE9020I DFSQSSP0 WARNING MODE: 28 BUF 14 PCT IMS1

• Action Level• 08.22.48 JOB00191 GJE9030I DFSQSSP0 ACTION MODE: 151 BUF 76 PCT IMS1

• 08.24.48 JOB00191 GJE9030I DFSQSSP0 ACTION MODE: 158 BUF 79 PCT IMS1

• Critical Level• 23.01.19 JOB00173 GJE9040I DFSQSSP0 CRITICAL MODE: 179 BUF 90 PCT IMS1

• 23.02.19 JOB00173 GJE9040I DFSQSSP0 CRITICAL MODE: 180 BUF 90 PCT IMS1

15

Shared Queues - Local Buffer Utilization

16

Destination Queue Depth

• Managing Destination Queue Depth & CQS for Shared Queues

• Limited tools to browse, delete and recover messages on Shared Queues

• Lack of tools to obtain CQS statistical information and manage messages on Shared Queues

• Required to optimize Shared Queues environment

• DQD data & List of Shared Queue Structures in use

• Filter based on Destination name or ID

• High level information, Drill down to levels of detail

• Browse, Delete and Recover messages from Cold queue

• Statistics for: structure, rebuild, checkpoint

• CQS processing counters

17

Destination Queue Depth

18

Destination Queue Depth

19

Destination Queue Depth

20

IMS Coupling Facility Structures

21

IMS Coupling Facility Structures

• Growing use of Coupling Facility Structures • Data Sharing, Shared Message Queues, Resource Manager, CQS logstream

• No single source for list of in use structures and details

• Coupling Facility Structure display • Real-time display of structure list

• Statistics, Connections, Coupling Facility information

22

IMS Coupling Facility Structures

23

IMS Coupling Facility Structures

24

CF Structure Statistics

25

CF Structure Connections

26

CF Structure Data

27

CQS Log Stream info

28

Managing CSL RM Structure

• Common Service Layer RM Structure Content • Holds global status of IMS Resources in IMSPlex• Determines IMSPlex wide status of Trans, LTERMs, Users • No capability to view content• No capability to alter/delete inconsistently defined resources

• Resource Management Structure display • Real-time display of structure content• Selectable via resource type and name filtering• Global status info to aid delete decision• Capability to delete selected resource definitions (multiple delete, delete by resource type or

by owner)• Eliminates need to scratch and reallocate resource structure

29

IMS Resource Structure Content

30

IMS Resource Structure Content

31

IMS Resource Structure Content

32

Aggregated SCI, RM, OM Statistics

• Managing the well being of Common Service Layer (CSL) address spaces• Lack of tools to obtain CSL statistical information

• Multiple instances to check

• Information gathered from CSL address spaces across Sysplex• Aggregated into single system image

• Drill down for information from individual address space

33

Aggregated RM Statistics

34

Aggregated RM Statistics

35

Local RM Statistics

36

CQS Shared Message Queues

37

CQS Structure Statistics

38

CQS Structure Statistics

39

CQS Processing Counters

40

CQS Structure Rebuild Statistics

41

CQS Structure Checkpoint Statistics

42

CQS Structure Checkpoint Statistics (cont)

43

Checkpointing

44

BMP Checkpoint/Restart

• CHKP – Checkpoint call• Commits updates

• Releases locked database records/segments

• Optionally can save application ‘working storage’ to IMS logs

• XRST – Extended Restart Call• Optional

• Enables BMP to be restartable from a checkpoint versus the beginning of an application

• IMS restart logic will reposition GSAM data sets to position at the time of checkpoint being restarted from

• If working storage was checkpointed, working storage will be restored from IMS logs

• Applications being converted from running as DLI to BMP should implement CHKPs

• Otherwise database records/segments can be locked for long periods

45

Basic versus Symbolic Checkpoints• Checkpoint calls indicate to IMS that the program has reached a commit point.

• They also establish places in the program from which the program can be restarted.

• IMS has symbolic checkpoint calls and basic checkpoint calls. A program might issue only one type of checkpoint call.

• MPPs and IFPs must use basic checkpoint calls.

• BMP, JBP, and batch programs can use either symbolic checkpoint calls or basic checkpoint calls.

• You cannot use the restart (XRST) call with the basic checkpoint call.

• Programs that issue symbolic checkpoint calls can specify as many as seven data areas in the program to be checkpointed. When IMS restarts the program, the XRST call restores these areas to the condition they were in when the program issued the symbolic checkpoint call.

46

Dynamically Implementing CHKP calls

Program Restart Facility (PRF) - Options that control implementing CHKP calls

• ISRTCHKP=YES | NO

Enable this feature though job override options or the IRT$CNTL DD. It is not recommended that you enable this feature in global options.

• PCB=nnnn | name | *

Specifies which PCBs are to be used when determining the trigger for checkpoint call insertion

47

Triggers for Implementing CHKP calls• Triggers for dynamically implementing/pacing CHKPs

• ICPNTVL=hhmmssth

Specifies minimal time interval between checkpoint call insertions

• CALLTYPE=GU | NO

Specifies whether to use GU and GHU calls as trigger for checkpoint insertion.

• POS=ROOT | NO

Specifies whether to use GN and GHN calls, when reaching a root segment, as trigger for checkpoint insertion.

• ICSTCLST=status_codes

Specifies 1 to 5 DL/I status codes which is returned from a DL/I call

• If more than one of these options is specified, a checkpoint call is inserted if any of these conditions is satisfied.

48

BMP Checkpoint Summary Report

49

Bypass Checkpoint Processing• Faster machines can cause older programs to perform

checkpoints at a higher-than necessary rate.

• Checkpoints consume IMS resources.

• Long-running jobs taking many checkpoints can benefit if fewer checkpoints can be taken.

• Allows you to specify how often a job is allowed to take checkpoints.

• Checkpoints attempted faster than a user-specified minimum are discarded.

• You can specify conditions where a checkpoint is allowed that would otherwise be discarded

• You can specify AIB return codes/IOPCB status codes to indicate discarded checkpoints

50

Bypass Checkpoint Processing (cont).• Specify the minimum time between checkpoints.

• Checkpoints attempted at a rate greater than specified are discarded.• Specify DBPCB status codes to check for. If found, checkpoint will be allowed.

51

Bypass Checkpoint Processing Considerations• BCSTCLST functionality helps avoid skipping necessary checkpoints.

• Useful for guaranteeing a checkpoint that is taken after certain conditions is not discarded.

• For instance, qualified GU/GN processing resulting in GB status.

• Bypass checkpoint processing is not suggested for Fast Path applications.

• Changes kept in memory until checkpoint taken.

• Discarding checkpoints can result in memory issues.

• Be certain your program can handle discarded checkpoints.

• Does your program do special processing to non-IMS files as part of a checkpoint process?

52

Considerations for Journey toIMS Managed ACBs

53

• IMS 12 added an IMS Catalog

▪ IMS DB meta data − Single source of Trusted repository of meta data− Loaded and updated from IMS ACBLIB− Data about data

▪ HALDB Structure− DBRC registered− Four dataset Groups

▪ IMS Catalog implementation− Infrastructure required• CSL: SCI, OM, RM (for Multiple IMSs)

− Initial Planning – How much space will I need for my production catalog?− Database maintenance procedures apply• Back up• Reorganization• Recovery

> Special Considerations with IMS Managed ACBs

What is the IMS Catalog?

54

• Trusted IMS metadata information stored in the catalog

• Comprehensive view of IMS database, application and program metadata managed by IMS with standard access methods (JDBC/SQL/DLI)

• Facilitates large scale Open Database solutions

• Metadata discovery and exchange possible through the IMS Explorer for Development and IMS Open Database

• Supports IMS integration with IBM and ISV tooling (Data Studio, Cognos, QMF, Optim Development Studio, Rational Asset Analyzer, InfoSphere Data Architect, etc…)

IMS Catalog Benefits

55

• Control block information is stored in the IMS Directory• The Directory has functionality similar to an ACBLIB• Directory records have a format much like the ACBs in an ACBLIB• The directory is kept in sync with the catalog

• IMS maintains a boot strap data set (BSDS) with information about the Directory data sets

• IMS will manage the IMS directory PDSE data sets• Directory data sets are automatically allocated

• An additional data set is allocated when a directory data set becomes full

• When IMS ACB Management is enabled• IMS will reference the directory to get the runtime application control blocks • IMS uses the directory to indicate which members from the IMS catalog are currently

active in the IMS environment

What is IMS Managed ACBs?

56

Physical Catalog Structure

57

HEADER(RESOURCE HEADER)

SS(SENSEG)

PCB

PSB

SF(SENFLD)

PSBVENDPSBRMK(REMARKS)

PCBRMK(REMARKS)

SFRMK(REMARKS)

SSRMK(REMAKRS)

XDFLD

LCHILD

AREA CAPXDBD SEGMDSET(DATASET)

DBD

MAP(DFSMAP)

DBDRMK(REMARKS)

CAPXSEGM

CASE(DFSCASE)

LCHRMK(REMARKS)

SEGMRMK(REMARKS)

CMAR(DFSMARSH)

CPROP(PROPERTIES)

CFLD(FIELD)

DBDVEND

CFLDRMK(REMARKS)

CMARRMK(REMARKS)

DBDXREF

DSETRMK(REMARKS)

AREARMK(REMARKS)

FLD(FIELD)

MAR(DFSMARSH)

FLDRMK(REMARKS)

PROP(PROPERTIES)

MARRMK(REMARKS)

MAPRMK(REMARKS)

CASERMK(REMARKS)

RESERVED RESERVED

LCH2IDX(INDEX NAME)

XDFLDRMK(REMARKS)

…RESERVED

DSG A DSG B DSG DDSG C

DFSCX000

Secondary

Index

Using the IMS Catalog to Provide Open Access to IMS Data Directly Using SQL

58

SQL Calls to IMS Data

59

• IMS 13 added direct SQL access using COBOL 5.1• Builds upon the catalog trusted meta data

• Allows a COBOL application program to make SQL calls to access IMS hierarchical databases• Most SQL calls are supported

• IMS 14 adds IMS managed ACBs• IMS 14 adds more

SQL support

• DDL updates to the Catalog & Directory

An IMS DBA or application programmer wants to know what an SQL call will return

• What are the results?

• Are the segment (table) fields defined for an SQL call?

• What DL/I calls will get executed when the SQL call is issued?

Implementing SQL Calls to IMS Data

60

IMS Explorer for Development• Connect … and start querying, updating, deleting IMS data

Using SQL

61

View the

SQL

results

SQL Builder

with content

assistance to

build a SQL

statement

Connection

PSB = Schema

DB PCB = Database

Database Segments

Here you can

create SQL

scripts with

Select,

Update,

Delete, Insert

statements

IMS Explorer for Development

Using SQL

62

Translate SQL

calls to an IMS

database into

DLI

Loading Metadata into an IMS Catalog

63

Initial Load specification • MANAGEDACBs=SETUP

Adding new resources• MANAGEDACBS=STAGE

Staged. Must be activated by Import

• MANAGEDACBS=UPDATEImmediately active

MANAGEDACBS=SETUP

• Directory is created if not available

• Directory is assumed to be new – no members

• Directory is populated from ACBLIB

or

• From DBDLIB / PSBLIB for GSAM & Logical DBDs

How is ACB Info Loaded in the IMS Directory

64

//LOADCAT EXEC PGM=DFS3PU00,

// PARM=(DLI,DFS3PU00,DFSCPL00,,,,,,,,,,,Y,N,,,,,,,,,,,,'DFSDF=001')

//STEPLIB DD DSN=IMS.SDFSRESL,DISP=SHR

//DFSRESLB DD DSN=IMS.SDFSRESL,DISP=SHR

//IMS DD DSN=IMS.PSBLIB,DISP=SHR

// DD DSN=IMS.DBDLIB,DISP=SHR

//PROCLIB DD DSN=IMS.PROCLIB,DISP=SHR

//SYSPRINT DD SYSOUT=* Messages, statistics

//IEFRDER DD ... Log data set

//DFSVSAMP DD ... Buffer pool parameters

//IMSACB01 DD ... First ACBLIB

// DD ... Optional concatenated ACBLIB

//IMSACB02 DD ... Optional additional ACBLIBs

//IMSACB03 DD ... ...

//SYSINP DD * ISRTLIST DUPLIST /*

IMS Catalog Populate Utility – DFS3PU00

• Traditional DBD structures• A Key field

• A sequencing field

• Segment total size with undefined space

• Adding Segment metadata → Fields

What is in the IMS Catalog After a Load?

65

Field 1 UndefinedField 2

Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7

Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7

Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7

→ Additional Instances and Fields equals database (IMS Catalog) growth

...

IMS Explorer for Development

• Import with copybook function• Include and update individual IMS

segments within a (DBD) with schema from:• COBOL copybooks

• PL/1 includes

• Updating DBD schema’s• Accomplished interactively

• Single Segment updates in E4D

• Multiple segment uploads

Importing Metadata

66

IMS Explorer for Development

• With IMS Managed ACBs• DDL is generated as a CREATE

TABLE

• DDL may be rewritten to perform an ALTER TABLE to add fields

• Run as SQL to directly update the IMS Catalog

Importing Metadata

67

IMS Administration Tool – EXPORT function

How is ACB info loaded into the IMS Directory?

68

• Offload PSB and DBD definitions

IMS Administration Tool – IMPORT function

How is ACB Info Loaded into the IMS Directory?

69

• Bulk copy DBD and PSB resource definitions

• From same IMS system or from another IMS system

• Regardless of whether both systems are using the IMS catalog or not.

• Initial Load specification

• Yes - Specify whether to replace or create an IMS directory database

• No – Specify to add records to an existing IMS directory instead.

• Rollback capability

• Backup existing objects in the target data set first before importing.

Validating Contents in the IMS Catalog

70

As IMS DBA’s prepare to migrate from an ACBLIB-managed environment to IMS Catalog-Managed environment, they need to validate consistency of resource objects.

• IMS Administration tool Compare function allows the IMS DBA to compare versions of DBD and PSB resources • Between the IMS catalog (directory) and the IMS ACB library.

• Active or Staging Directory to Active, Inactive, or Staging ACBLIB or to a specific ACBLIB dataset

• Between IMS Directory datasets (Active to Staging)

• Compare function confirms consistency of resources• Within the same IMS subsystem• Between IMS subsystems

• Any differences detected are highlighted to simplify identification and assist in analysis

Validate Contents of the IMS Catalog

71

IMS Administration Tool – Compare Function

72

IMS Administration Tool – Compare Function

73

Managing Multiple Instances of DBDs and PSBs

74

• As IMS DBA’s or applications programmer add or alter resources, instances become obsolete over time.• Every ‘ACBGEN’ will result in a new version of the DBD or PSB being added to the IMS

Catalog database

• Is a database resource still needed?

• Are there database resources with no corresponding PSB?

• Obsolete resources eventually result in Catalog maintenance• Resource Purge to free space utilization

• Database reorganization to reduce fragmentation

• How does a DBA easily identify obsolete resources in the IMS Catalog?

Managing IMS Catalog Resources

75

• Use the IMS Catalog Purge utility (DFS3PU10) to delete resources

➢ The catalog does not automatically purge DBDs & PSBs

Removing Obsolete Objects

76

//BATCH EXEC PGM=DFSRRC00,

// PARM=(DLI,DFS3PU10,DFSCP001,,,,,,,,,IMB1,,Y,Y,IRLB,,,,,,,,,,,,

// 'DFSDF=0B1')

//STEPLIB DD DSN=IMSCFG.IMB1.SDFSRESL,DISP=SHR

// DD DSN=IMSCFG.IMSB.USERLIB,DISP=SHR

//DFSRESLB DD DSN=IMSCFG.IMB1.SDFSRESL,DISP=SHR

//PROCLIB DD DSN=IMSCFG.IMSB.PROCLIB,DISP=SHR

//IMS DD DSN=IMSCFG.IMSB.PSBLIB,DISP=SHR

// DD DSN=IMSCFG.IMSB.DBDLIB,DISP=SHR

//SYSUT1 DD DSN=IMSCFG.IMSB.CATPURG,DISP=OLD

//IEFRDER DD DSN=&&IMSLOG1,DISP=(NEW,DELETE),

// DCB=(RECFM=VB,LRECL=4092,BLKSIZE=4096,BUFNO=5),

// SPACE=(CYL,(200,75)),UNIT=SYSDA

//IEFRDER2 DD DSN=&&IMSLOG2,DISP=(NEW,DELETE),

// SPACE=(CYL,(200,75)),UNIT=SYSDA

//DFSVSAMP DD DSN=IMSCFG.IMSB.PROCLIB(DFSVSM0B),DISP=SHR

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

MODE BOTH

//*

Example: The value RETENTION=(INSTANCES=3)There are 5 instances of DATADB10

Running the Catalog Purge utility will remove the oldest two instances of DATADB10 from the catalog

IMS Administration Tool

Details on Obsolete Objects – PSBs & DBDs

77

Details on Obsolete Objects – PSBs & DBDs

78

May want to export this list to:• Compare with Obsolete Instances list• Input to IMS Catalog purge utility

IMS Administration Tool

Query and Analysis of IMS Catalog Content

79

Physical Catalog Structure

80

HEADER(RESOURCE HEADER)

SS(SENSEG)

PCB

PSB

SF(SENFLD)

PSBVENDPSBRMK(REMARKS)

PCBRMK(REMARKS)

SFRMK(REMARKS)

SSRMK(REMAKRS)

XDFLD

LCHILD

AREA CAPXDBD SEGMDSET(DATASET)

DBD

MAP(DFSMAP)

DBDRMK(REMARKS)

CAPXSEGM

CASE(DFSCASE)

LCHRMK(REMARKS)

SEGMRMK(REMARKS)

CMAR(DFSMARSH)

CPROP(PROPERTIES)

CFLD(FIELD)

DBDVEND

CFLDRMK(REMARKS)

CMARRMK(REMARKS)

DBDXREF

DSETRMK(REMARKS)

AREARMK(REMARKS)

FLD(FIELD)

MAR(DFSMARSH)

FLDRMK(REMARKS)

PROP(PROPERTIES)

MARRMK(REMARKS)

MAPRMK(REMARKS)

CASERMK(REMARKS)

RESERVED RESERVED

LCH2IDX(INDEX NAME)

XDFLDRMK(REMARKS)

…RESERVED

DSG A DSG B DSG DDSG C

DFSCX000

Secondary

Index

Key value: DBDbbbbbdbdname1 Key value: PSBbbbbbpsbname1

• IMS Administration Tool –> ISPUFI function• Allows you to directly interact with an

IMS database using interactive SQL

• Expand the PSB information to view associated PCBs and detail for each • Table (segment name)

• Columns (field names)

• Authority Information

• The PCB authority information shows the types of operations - such as Select,Update, Insert, and Delete - that IMS SPUFI can perform on the fields in the database.

Querying the IMS Catalog

81

IMS Administration Tool (ISPUFI) - displays all the columns in that Table (Fields in that segment)

SQL Editor – Program View

82

IMS Administration Tool (ISPUFI)

SQL Editor – History

83

• ISPUFI function –> History• Retains the current and previous

SQL statement sessions

• Allows easy access to regularly used statements during future use

• SQL statements instream or saved in an INPUT file• Using data sets allows complicated sets of SQL statements to remain as input for future

executions interactively in ISPF or scheduled in a Batch job

• Output file retains generated output• Result set can be sequential file or CSV

• Can be used to feed other processes

• Sample JCL provided• YOURHLQ.SATYSAMP(ATYSPUFI)

• Many IMS Catalog QUERY examples

SQL - Batch Interface

84

IMS Administration Tool (ISPUFI)

Query Result Set

85

IMS Administration Tool

• Application programmers - IMS Explorer for Development fits program development

• Eclipsed based

• Access to many other PD Tools

• Add metadata to a segment/database

• DBD to PSB cross reference

• SQL by application

• DLI to SQL & SQL to DLI translations

• Database Administrators – IMS Administration Tool

• Web browser, ISPF UI or batch

• Space utilization for impact analysis when planning for initial IMS Catalog implementation or when adding objects to an existingcatalog

• Easily view the number of objects & instances in an IMS Catalog

• Compare versions of DBD & PSB resources, highlighting differences to validate IMS catalog contents

• Adding or updating individual or bulk IMS database definition schemas from COBOL & PL/I copybooks interactively or through a batch job to assist in loading metadata into the IMS Catalog

• ISPUFI feature to develop interactive SQL statements without requiring knowledge of the exact syntax. SQL against IMS Catalog or any IMS database can be done interactively or scheduled in a batch job.

IMS Explorer for Development and IMS Administration Tool

86

• There are many components to administer for an IMS environment

• Understanding how the components work, how they can fail, and the solutions that are available to help you maintain a healthy IMS

• Getting to IMS Managed ACBs:• Will bring change as to how these resources are managed

• Will enable openness into your IMS data

Session Summary

87

Please submit your session feedback!

• Do it online at http://conferences.gse.org.uk/2020/feedback/6AY

• This session is 6AY

88

http://conferences.gse.org.uk/2020/feedback/nn

GSE UK Conference 2020 Charity

• The GSE UK Region team hope that you find this presentation and others that follow useful and help to expand your knowledge of z Systems.

• Please consider showing your appreciation by kindly donating a small sum to our charity this year, NHS Charities Together. Follow the link below or scan the QR Code:

http://uk.virginmoneygiving.com/GuideShareEuropeUKRegion

89

http://uk.virginmoneygiving.com/GuideShareEuropeUKRegion

Thank You

Merci

Grazie

Gracias

Obrigado

Danke

Japanese

English

French

Russian

GermanItalian

Spanish

Brazilian Portuguese

Arabic

Traditional Chinese

Simplified Chinese

Tamil

Thai

KoreanHindi

Ndzi khense ngopfuTsonga

Ke a lebohaTswana

90