When Top Secret starts, the following errors occur:
TSS9020W INVALID PARAMETER FILE OPTION errors.
For example:
07JUN 14:12:53 TSS ssss TSS9020W INVALID PARAMETER FILE OPTION
07JUN 14:12:55 TSS ssss TSS9079E INVALID DATA
07JUN 14:12:55 TSS ssss TSS9076I CURRENT OPTION IS <FAC(USER38=NAME=XXX)>
07JUN 14:12:55 TSS ssss TSS9020W INVALID PARAMETER FILE OPTION
07JUN 14:12:55 TSS ssss TSS9079E INVALID DATA
07JUN 14:12:55 TSS ssss TSS9076I CURRENT OPTION IS <FAC(USER41=NAME=YYYY)>
07JUN 14:12:55 TSS ssss TSS9020W INVALID PARAMETER FILE OPTION
07JUN 14:12:55 TSS ssss TSS9079E INVALID DATA
07JUN 14:12:55 TSS ssss TSS9076I CURRENT OPTION IS <FAC(USER45=NAME=ZZZZ)>
07JUN 14:12:55 TSS ssss TSS9020W INVALID PARAMETER FILE OPTION
07JUN 14:12:55 TSS ssss TSS9079E INVALID DATA
07JUN 14:12:55 TSS ssss TSS9076I CURRENT OPTION IS <FAC(USER46=NAME=AAAAA)>
07JUN 14:12:55 TSS ssss TSS9020W INVALID PARAMETER FILE OPTION
07JUN 14:12:55 TSS ssss TSS9079E INVALID DATA
07JUN 14:12:55 TSS ssss TSS9076I CURRENT OPTION IS <FAC(USER39=NAME=BBBBB)>
07JUN 14:12:55 TSS ssss TSS9020W INVALID PARAMETER FILE OPTION
Release : 16.0
Component : Top Secret for z/OS
The problem is the following statements:
FAC(USER38=NAME=XXX)
FAC(USER39=NAME=BBBBB)
FAC(USER41=NAME=YYYY)
FAC(USER45=NAME=ZZZZ)
FAC(USER46=NAME=AAAAA)
are in multiple parmfile members in the PARMFILE concatenation. What is happening is facility USERnn is getting renamed to 'facname' (XXX, BBBBB, etc) in the first member. Any subsequent FAC statements must start with FAC(facname=...) instead of FAC(USERnn=...).