when I wars responsible for application software 10 and/or 20 years ago, I did my usual low tech, basic utilities solution. I'd do a 'listd hist' on the member names and store the results. programs were compiled when they went from dev to test, and copied from test to prod/staging. yes I wrote a lot of rexx code and used 'listd members' to process a pds in a loop thru the names. didn't use a lot of pdse since I maintained the libraries and didn't have any issues, but those hist stamps were reliable. I could check the history stamps anytime, but always when software was promoted. then me and my software got replaced by cots...
--- On Mon, 3/26/12, Josef Boeck <[email protected]> wrote: From: Josef Boeck <[email protected]> Subject: Certificates and signed programs To: [email protected] Date: Monday, March 26, 2012, 6:31 AM Hi, It's possible to sign a program with a certificate. If you enable the certification this program is verified during LOAD for integrity and you can be sure as program author that the program ist the one you created and is not modified. If you copy the program from a PDSE to a normal PDS no verification can take place cause the information nessesary to verify is not kept the PDS. As far everithing works as documented. My question: Am I able to verify if the program runs as "signed program" and is verified or if the program runs without verification. I didn't find any hint in documentation. Thanks, Josef ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
