RE: Regarding Decryption of AES128 encrypted data in RPGLE and query regarding CRC 32 -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: Regarding Decryption of AES128 encrypted data in RPGLE and query regarding CRC 32
From: Rob Berendt <rob@xxxxxxxxx>
Date: Thu, 26 Sep 2019 11:12:43 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

It's a DSPLY limitation. See the following:
DSPMSGD RANGE(RNF7016) MSGF(QDEVTOOLS/QRPGLEMSG)
A workaround is to move the first 52 bytes into another field and display that.
That message file can be a Godsend for compiler messages. Then again, you can get that sort of detail in RDi if you can break away from SEU.

Rob Berendt

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.