What you're trying to do is to track every z/OS LOAD of a member from your loadlib. Unfortunately, there's no easy way of doing this.

- You could setup a RACF program access rule, but you'd need a rule for 3500 programs - not a viable option.
- You could write a 'front-end' to the LOAD macro, but that is very difficult, and requires HLASM and z/OS internal knowledge.
- CA-PDSMAN used to have usage statistics for PDSs - but few people now have PDSMAN, and this won't help if your LOADLIB is a PDSE.
- SMF doesn't provide statistics for individual members of a PDS.

The only other thing I could think of is to provide a program that your test scripts would call just before calling a program. This program could output to a dataset, or produce an SMF record.

Unfortunately, I don't think any of this will help you much. Sorry I couldn't help out more

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

Perhaps you could extract the sysin 'key words', then compare that data to your load library members. (either manually, or create one or two short programs to do this). Just a quick thought.

Please complete the following information:

REGISTER / LOG-IN TO DISCUSS

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

Submit your e-mail address below to continue

E-mail: 

E-mail: 

Handle:   

Password: 

Forgot Password?

Create Handle: 

Your handle identifies you in ITKnowledgeExchange. Max 30 char.

Create Password: 

Confirm Password: 

Yes, I agree to the IT Knowledge Exchange  Terms and Conditions.

hidden modal window