A service program (we'll call it "A") has been changed such that other programs and other service programs to which "A" is bound will throw a signature violation.
I've located the programs and other service programs that would have that issue -- those HawkEye identified as BIND in the How Used column, and plan to use UPD[SRV]PGM BOUNDTOA BNDSRVPGM(A) to rebind to the new copy to each of those.
Not being well-versed in this (yet), I have a couple quick questions:
Question 1: After *srvpgm "BOUNDTOA" has been so updated, do the *PGMS & *SRVPGMs to which BOUNDTOA is bound also need rebinding?
To draw a picture:
Srvpgm "BOUNDTOA" was created with BNDSRVPGM(A *IMMED).
Srvpgm "A" has a new signature that would cause "BOUNDTOA" to fail.
BOUNDTOA needs UPDSRVPGM BOUNDTOA BNDSRVPGM(A *IMMED).
Srvpgm "C" was created with BNDSRVPGM(BOUNDTOA *IMMED).
Is "UPDSRVPGM C BNDSRVPGM(BOUNDTOA *IMMED)" also necessary, or should I only be concerned with those immediately bound to "A"?
Question 2: In at least one case, a service program like BOUNDTOA was created with binding to other service programs besides A, as in BNDSRVPGM((A *IMMED) (X *IMMED)). Do I need to list X in the UPDSRVPGM for its unchanged binding to be retained, or will its binding still be in place after the update?
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.