Hello GCox,
Did you find anything better than strqsh ... openssl md5?
I followed the iProDeveloper SHA1 article you suggested. Good stuff but not quite right. The listing below uses the same concepts but calculates an MD5 hash that agrees with hash produced by a MD5sum Windows port and by the PASE shell openssl md5 < path to file:
PGM PARM(&DATA)
DCL VAR(&DATA) TYPE(*CHAR) LEN(60)
CHKOBJ OBJ(MD5OUT) OBJTYPE(*DTAARA)
MONMSG CPF9801 EXEC(DO)
CRTDTAARA DTAARA(md5out) TYPE(*CHAR) LEN(32)
ENDDO
ADDENVVAR ENVVAR(MD5_INPUT) VALUE(&DATA) REPLACE(*YES)
ADDENVVAR ENVVAR(QIBM_PASE_DESCRIPTOR_STDIO) VALUE(B) REPLACE(*YES)
STRQSH CMD('export PATH=$PATH:/qopensys/usr/bin && openssl md5 < +
$MD5_INPUT | iconv -f 819 -t 37 | sed "s/(stdin)=\ //" | datarea +
-wl md5out')
ENDPGM
Leaves just the 32 byte hash in a current library/MD5OUT data area which can be accessed after the call to this CLP or CLLE.
I'm running way behind schedule. Do you have any pointers for accessing the IRS ACA 1094/1095 software test system? At first glance their testing guide seems fairly obtuse.
Best to you, ~ j