Allow multiple Jobnames per rule in AT-TLS Policy. Mask won't work for jobs like J363100, J491001. J* will pull in all jobs.

1. A bank has provided 3 different client server
certificates in addition to the usual server
certificates.

2. Different applications FTP to the bank from a
z/OS Lpar using a batch JCL. Mainframe is the
client.

3. For each of the FTP job, we need to be able to
point to the correct keyring if we employ different
keyrings with default client certificates -OR-
use same keyring with different certificate label.

4. No matter which route we choose, we have to
use the Jobname parm to guide the job to use
the right rule.

5. Since the Jobnames are different for different
applications and within applications they are not
in a pattern matching sequence, we cannot use
the mask like (J363*) for the rule. There could
be other J363 pattern jobs that FTP elsewhere.

6. Since the current implementation only allows
the Jobname to be a singlet or a mask, we ended
up defining the same rule but with a different
jobname to make the transition happen.

7. So currently, instead of having just 3 rules for 3
different client certificates with all Jobnames
in one rule, we have 25 rules for the 25 different
Jobs.

8. Cannot ask applications to yank out all FTPs
from different jobs and put in one new JOB for
each application either, because they have
dependencies built in depending on return codes
and changing anything here would imply having
to change the schedule with the IBM Workload
Scheduler as well.