× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I added a field to a file that uses an I/O module (service program) for
all access to this particular file. I have re-compiled the file.

I went to the following link to see exactly what I need to do next.
http://archive.midrange.com/midrange-l/200210/msg00025.html

Then re-read Joel Cochran's article: "Service Programs with a Smile"
particularly this paragraph: "With service programs, you only have to
issue one command, UPDSRVPGM, like so: 
UPDSRVPGM SRVPGM(MYLIB/MYSRVPGM)   MODULE(MYLIB/PROC2)
Doing so updates not only the service program itself but also all of
the programs that have bound PROC2."

Like many shops, we have  dev and prod boxes. If I use the UPDSRVPGM
command to get everything back in sync on development, does that mean I
only have to send the re-created file to production then run the
UPDSRVPGM there, as well? 

Or, could I, to be on the safe side (read: sissy) just recreate
everything - add *prv to binder source, etc - and promote to production?
This is one file, one service program,  and three programs that access
the I/O service program.  The last time I worked on any service programs
was when I built this automatic job submitter system last July. We have
since decided to go in another direction - dot net on our intranet for
all applications.  Scary *ain't*  it?

Thanks,


Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404

Receipt of this message does not grant you permission to send me 
Unsolicited Commercial Email


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.