-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Assign Certificate to DCM Application #22
Comments
According to IBM Support this is the result of using more than 7 parameters in ServiceProgramCall. // 1 Application ID Output Char(*) to // 1 Application ID Output Char(*) and so on, it should work. |
Thanks for the insight, @DeltaE0 ! |
* start rework to use IBMi5OSKeyStore * fixup * optimize `dcmexportcert` if format is pkcs12 * fix `dcmrenew` * fixup * code fix per comment in issue #22 Co-authored-by: Jesse Gorzinski <[email protected]>
I tried to assign a certificate to an application.
This i the qshell output:
dcmassign
shortname for 'QIBM_QTV_TELNET_SERVER' is 'TELNET'
shortname for 'QIBM_GLD_DIRSRV_SERVER' is 'DIRSRV'
shortname for 'QIBM_QTMS_SMTP_SERVER' is 'SMTP'
shortname for 'QIBM_QTMF_FTP_SERVER' is 'FTP'
shortname for 'QIBM_QTMM_POP_SERVER' is 'POP'
shortname for 'QIBM_QSVR_OBJC_SERVER' is 'OBJC'
Enter application ID:
FTP
Assigning to QIBM_QTMF_FTP_SERVER...
Enter certificate ID:
2022-02
The parameter [0]: Parameter value is not valid.
$
The text was updated successfully, but these errors were encountered: