We've been using the Co:Z Toolkit for a number of years and running SSHD on z/OS per the Toolkit's instructions.
Our Information Security group uses a Linux system to generate certificates. A process was put in place and tested successfully multiple times last year to:
gen a cert
scp the cert to z/OS
sub a job to z/OS to then
oget the cert to a MVS data set using binary
add the cert to RACF
In the last few days we've begun using that process due to some new certificates being needed on z/OS. But the add to RACF is failing with:
IRRD104I The input data set does not contain a valid certificate.
If I have the cert file on Linux copied to a USB stick, place the USB stick in my PC, and then IND$FILE the cert up to a MVS data set, the add to RACF works fine. So I think I'm left with the possibility that either (a) the scp command or (b) the oget command is causing a problem. Any suggestion on how would I go about determining if scp is the culprit ? or oget ?
I may have answered my own question. The Linux staff here is convinced that scp does binary transfers in their world. But according to the Ported Tools documentation (IBM Ported Tools for z/OS: OpenSSH V1.2.0 User's Guide):
By default, scp treats files as text. It assumes that all data going over the network is encoded in ASCII coded character set ISO 8859-1.
? or oget 
?