search cancel

Call to EARLVSM always made instead of EARLR900, why?

book

Article ID: 189010

calendar_today

Updated On:

Products

Earl

Issue/Introduction

We are working on cleaning up our LNKLST and APF entries. As part of it we have generated a report to see what user jobs are using an old EARL module called EARLVSM. We looked at those jcls,procs of the jobs and don't see a steplib coded to access this module in the old CCS loadlib. In fact, we have this load module placed at the bottom of our LNKLST. How come EARLVSM is still being picked up when the loadlib it resides is placed at the bottom of the LNKLST entries? We are expecting the EARLR900 module to be called.

We are only using the standard canned reports from products like CA 1.


 

Environment

Release : 6.1

Component : EARL-MVS COMMON COMPONENT

Resolution

When using PGM=EARL the program calls a program called EARLOPI. This module automatically calls EARLVSM. If it finds it then it uses EARLVSM rather than EARLR900.

If there is no EARLVSM available then the call will go to EARLR900.

That is why you see the call for EARLVSM all the time. You have it in the LNKLST.

You can remove the module EARLVSM from the LNKLST and the call will go to the EARLR900.