Since no one else is answering this, I'll make a really wild guess without any real substance. I can't believe that IBM would default to SMF Signature Validation enabled. Are there supposed to be SMF parm changes? Did you meet the software and hardware requirements for this feature?
Jon. On Friday, October 4, 2019, 05:40:11 AM PDT, Mark Jacobs <00000224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote: What's the magic spell(s) to get SMF Signature Validation to work? I've been trying for a couple of days and it's failed every time. Latest failure is this; IFA741I UNABLE TO PERFORM SMF SIGNATURE VALIDATION IFA742I SMF SIGNATURE VALIDATION FAILED DUE TO INCONSISTENT RECORDS - FIRST FLAG DOES NOT MATCH The previous days SMF data is archived using these parameters; LSNAME(IFASMF.DEVL52.DEFAULT,OPTIONS(ARCHIVE)) OUTDD(OUTDD1,TYPE(0:255)) RELATIVEDATE (BYDAY,1,1) NOSIGSTRIP And my validation job reads in that archived data using these parameters INDD (IN,OPTIONS(DUMP)) OUTDD(DUMPOUT,TYPE(0:255)) NOSIGSTRIP SID(PROD) SIGVALIDATE(HASH(SHA512), TOKENNAME(SMF#SIGNING#TAMPER#RESISTANT#TOK)) Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
