Re: updsrvpgm to re-bind changes

Michael, very simple answer:

Q1). No.

Q2). No - just so long as you use UPDSRVPGM.

However, I have a question or two for you. Do you really _need_ to do this rebinding in the first place? Is a signature violation against *SRVPGM A necessary to the continued operation of your application? Can you not take advantage of the Binder Language to control the signature, in order to provide "backward compatibility" for existing *SRVPGM/*PGM objects. (This is the nub of using *SRVPGM and the Binder Language.)

Brian.

====================================
Michael said:
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 is iOS 7.1

Thanks.
Michael Koester