|
Hi all, I am a bit confused by some service program behaviour. I have a program PGMA which calls a service program SPPARTS containing one module PARTS. This module contains a number of procedures, the most recently added is called "updateMinMax". I found a problem in the updateMinMax procedure in which it was returning an error when it should not have been, due a condition that needed to be more granular. So, I opened the source for the PARTS module, split up the condition and compiled, overwriting the existing PARTS module. Then I issued the command "UPDSRVPGM MYLIB/SPPARTS MODULE(MYLIB/PARTS)". Note that no procedures were added or removed and no parameters were changed. I got the message that the service program was updated. The service program is ACTGRP(*CALLER). When I called the program, the error was still showing up when it should not have been. The call order is like this, starting by issuing the command to start the main menu application: main menu ----> vehicle maintenance menu ---> work order menu (this menu has a named activation group VMACTGRP) ---> PGMA ---> SPPARTS So, since I had done an UPDSRVPGM, and the activation group was not in use by my job, I thought I should see the changes. When this didn't work I tried recreating the service program. This didn't work either and I had to sign out and sign back in to see the changes. I've skimmed the ILE Concepts Reference to see if I can check my assumptions about how UPDSRVPGM works, but didn't find anything to explain this behaviour. Can someone shed a bit of light on why the program saw the old version of the service program until the job ended? Thanks in advance, Adam ##################################################################################### Attention: The above message and/or attachment(s) is private and confidential and is intended only for the people for which it is addressed. If you are not named in the address fields, ignore the contents and delete all the material. Thank you. Have a nice day. For more information on email virus scanning, security and content management, please contact administrator@xxxxxxxxxxxx #####################################################################################
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.