× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



With all due respect... if the code has been written and tested for a named activation group (it doesn't matter whether it's QILE or anything else... QILE is just a name...)

WHY ON EARTH WOULDN'T YOU RUN IT THERE?

Sure, you could change it to *CALLER, and it might work... but WHY?


David FOXWELL wrote:
Hi all,

Just been given an RPG source called MD5 and told to call it to encrypt all the passwords of our internet users. I don't know exactly where this source comes from but you can find it in the archives and elsewhere on the net.

It says to compile with ACTGRP(QILE) and BNDDIR(QC2LE)

We are a shop where everything is compiled with ACTGRP(*CALLER) and there are as yet no SRVPGM to be found. So, I believe that effectively, everything will run in the DFTACTGRP.

Now as MD5 has a stack of SRVPGM, I understand that strange things might happen between calls if I compile it with ACTGRP(*CALLER).

My program will read a userID file, and for each user call MD5 for the encryption.

If my program starts in DFTACTGRP, how should I handle things between each call to MD5?
Why compile MD5 in QILE ?
Couldn't I create a module from MD5, bind it to my program and compile my program in a named activation group that I would destroy when all my passwords are encypted?


Thanks.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.