Identifying unused programs and dialogs

book

Article ID: 185892

calendar_today

Updated On:

Products

CA IDMS CA IDMS - Database CA IDMS - ADS

Issue/Introduction

This Knowledge Document describes procedures for identifying unused programs and dialogs in an IDMS environment.

Environment

Release : All supported releases.

Component : CA IDMS

Resolution

It's not a simple matter to identify what programs are NOT running in an IDMS CV.
The best approach is to do some reporting on what is there, and exclude what is being executed.

For ADS dialogs:

To identify what is being executed, use PMARPT04.

Finding a concise report of all of the dialogs in a dictionary is also less than trivial.
The following reports could be used:
ADSORPTS (with DIALOG=ALL,REPORTS=SUMMARY)
AREPORT 001
DREPORT 055 

Unfortunately all of the above reports give more than just a simple list of dialogs, so some massaging/editing of the output might be necessary.

If there is an SQL schema describing the dictionary, the following SELECT will generate a concise list of all dialogs in the dictionary:

SELECT PROG_NAME_051, PROG_VER_051
FROM APPLDICT."PROG-051" WHERE PROG_FLAG1_051=X'10';

For user programs (cobol and assembler):

It's impossible to see from an IDMS perspective exactly what is available because in general these program are maintained outside of the IDMS environment, i.e. in TSO source and load libraries.
However, these program have to be defined to sysgen so there is some level of IDMS control.
SREPORT 013 can be used to identify sysgenned programs that are being executed 0 times.