Re: Using CSNBRNGL

2025-03-12 Thread Andrew Mattingly
Here's some COBOL which calls CSNBRNGL. I have included calls to STCKF to get timings (see: https://github.com/admattingly/Macho/ ) but you can comment this out if you wish. Hopefully this logic is self-explanatory: identification division. program-id. wrangle. environment

Re: Using CSNBRNGL

2025-03-11 Thread Billy Ashton
gt; To IBM-MAIN@listserv.ua.edu Date 3/11/2025 11:18:27 AM Subject Re: Using CSNBRNGL Billy, On this page IBM tells you how to set up the C language parameters. Wherever this page says a parameter is “integer” it means “PIC S9(9) BINARY”, where it says “string” it is any “PIC X” of at least the len

Re: Using CSNBRNGL

2025-03-11 Thread Paul Gilmartin
On Tue, 11 Mar 2025 14:29:16 +, Billy Ashton wrote: >Hey all! It's been a while since I bothered y'all, and I hate to do this >again, but my manager wants me to do some research on using the Crypto >feature to generate "true" random numbers - CSNBRNGL. > Would /dev/random do that for you? <

Re: Using CSNBRNGL

2025-03-11 Thread Farley, Peter
Billy, On this page IBM tells you how to set up the C language parameters. Wherever this page says a parameter is “integer” it means “PIC S9(9) BINARY”, where it says “string” it is any “PIC X” of at least the length specified by the matching integer length parameter area. The integer random

Re: Using CSNBRNGL

2025-03-11 Thread Colin Paice
Check in Cryptographic Services Integrated Cryptographic Service FacilityApplication Programmer's Guide SC14-7508-09. Ive put icsf C code in https://github.com/colinpaicemq/EasyICSF, so you can get to see what coding "rules" etc looks like It looks pretty easy if you can define character strings

Re: Using CSNBRNGL

2025-03-11 Thread Tom Harper
Billy, Why not use the PRNO/PPNO hardware instruction on your CPU if it is new enough? Just write a small assembler program. Tom Harper Phoenix Software International Sent from my iPhone > On Mar 11, 2025, at 10:29 AM, Billy Ashton > <0665bda14df5-dmarc-requ...@listserv.ua.edu> wrote: