Not sure why, but we have had problems ftp'ing certificates to import.
What we end up doing is cut'ing from the PC and pasting into the TSO.
I was just recenlty made aware of this, the security people new but did
not tell any of the networking people. Here the mainframe network
sysprogs do all truly network functions (firewalls, switches, routers).
I was told that it has something to do with trailing blanks on the end
of the lines. That ftp was adding them, and something did not like
them. I want to do some testing, I think that using recfm VB should
work but I have not tried it yet.
Ward, Mike S wrote:
It doesn't matter whether I ftp it in ascii or binary I still get the
same error.
Here are the racf statements I use.
RACDCERT ID(KEYMSTR) GENCERT('CERT.GENREQ') +
SIGNWITH(CERTAUTH LABEL('My CA Authority 2005')) +
WITHLABEL('WebReports Server') +
NOTAFTER(DATE(2008-06-01))
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Behalf Of TISLER Zaromil
Sent: Monday, March 20, 2006 9:11 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SSL Certificate Signing
<----- snip ----->
So I had them redo the request and I made sure to FTP it back to z/OS in
ascii mode. I still get the same error.
<----- snip ----->
Why ascii?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
