|
Reeve said: > I am getting the you-know-what hammered out of > me with service program signature violations. Are you doing UPDSRVPGM EXPORT(*SRCFILE)? I think *CURRENT is the default, and might be giving you trouble. I'd DSPPGM and see what sig it wants. Then DSPSRVPGM DETAIL(*PROCEXP *SIGNATURE) to see what is being exported, and what signatures it supports. That should start you down the yellow brick road... Joel asked: > Why do you have this twice? [the same export block > with different signatures] I know the signature is different, > but the export list is the same. I do this so I can tell what functionality level the service program is at. When I distribute a service program to multiple machines, it is easy to tell what level they are at (and if I missed one.) Various change management issues mean that relying on the creation date can be unreliable. --buck
As an Amazon Associate we earn from qualifying purchases.
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.