TWS and Load JCL

[dick scherrer]

Hello,

Sorry, it's difficult to me to know how you need exactly.

And more difficult for us as you are convinced you must implement an unacceptable (most places) design.

I don't anderstand why you need the jcl ...
It's a simple jcl.

A couple of thought here:
1. Your understanding of why someone "needs it" is not required.
2. Simple to you, but as we had not seen it, there was no way to know just what had been implemented.
3. When someone trying to help asks for more info, just post it. No one will ask for more info just for giggles.

I have no idea how this set of "requirements" came about, but they are not really requirements. The requirement is to get the rignt process run every time. . . The user (the reason there is a process) does not need to be involved with one member name versus another.

[Blackthorn]

Initially I thought that you were just accessing a differwent dataset in your job, hence my earlier suggestion. But it seems that the different members you are referencing are your two different jobs.

Are these procedures? If so, you can still use variable substitution on the jobcard, just include/exclude two different JCLLIB statements based on the application name.