Submitting jobs to an LPAR with different password case support

Products

• Top Secret

Issue/Introduction

How are passwords handled when submitting jobs to a different system or LPAR using a different password case.

Example:

LPAR1 with mixed case passwords submits job to LPAR2 with uppercased passwords.

Environment

Release : 16.0

Component : Top Secret for z/OS

Resolution

It depends if the job  inherits the signon or signed on by a USER= or PASSWORD= by the JOB card.

Inheritence is when Top Secret imbeds signon information into the job and  used to signon and the USER= or PASSWORD= on the JOB card.

If a job inherits the signon, there is no password validation. No password validation means it doesnt matter if the system is running UPPER or MIXED case passwords.

If the batch job signs on, look for a USER= and PASSWORD= on the job card. If not there, then the job inherited,

If there is a USER= and PASSWORD= is on the JOB, password validation will occur and the password case will matter inorder for the password to match on the remote node.