RE: More Service Program Issues

["Chris Wolcott" <CWolcott@xxxxxxxxxxxxxxxxxxxxxx>]

UPDSRVPGM only allows you to change the current modules.  Adding or,
Heaven Forbid, removing a module from a *SRVPGM requires it to be
re-created.  I am not familiar with the mentioned article, but you need
to be aware of the service program signature and how to work-around
them.  I will take it on faith that the article went into those areas.

I've never had to remove a *SRVPGM from a *BNDDIR.  How (why) are you
using a *BNDDIR when creating your *SRVPGM?  Unless they have changed
*SRVPGMs, you can not use a *BNDDIR to let the CRTSRVPGM command look
for the *SRVPGM's component modules, they have to be specified on the
command.  

If you do not have a change management system (ALDON, MKS, etc) then
write a little CL for each CRTSRVPGM command you need.  It surly beats
trying to remember and retype all the module names every time you need
to recreate a *SRVPGM.


> -----Original Message-----
>    2. More Service Program Issues (T.Bryant@xxxxxxxxxxxxxx)
> message: 2
> date: Thu, 9 Dec 2004 11:44:55 +1100
> from: T.Bryant@xxxxxxxxxxxxxx
> subject: More Service Program Issues
> 
> G'day, 
>         was just referring to Joel Cochran's article, Binder 
> Source: The 
> Little Language That Could.
> 
> 
> Now you have to create the service program again. There is no 
> way around 
> this step. You must run the CRTSRVPGM command over the new 
> binder source 
> and include PROC4 in the module list. 
> 
> 
> 
> I thought the UPDSRVPGM command was the 'way around this step'.
> Is it?
> 
> Also, I can't seem to recreate the service program without 
> first removing 
> the entry from the Binding Directory.
> Is this normal? 
> 
> I am using THENON and have experienced infinite annoyances.
> Does anyone else experience problems with THENON and service programs?