RE: Updated service program, but not seeing changes

Correct,

If the 'In Use' is No, then the group can be reclaimed using RCLACTGRP.

Have a good weekend!

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx 
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of 
AGlauser@xxxxxxxxxxxx
Sent: Friday, July 21, 2006 3:31 PM
To: Midrange Systems Technical Discussion
Subject: RE: Updated service program, but not seeing changes

Ah, I see ... so when I do a WRKJOB option 18 to show 
activation groups, 
'In Use' <> 'Active'.  That explains a lot of confusing 
situations I've 
come across.  Thanks Wilt.

Adam

midrange-l-bounces@xxxxxxxxxxxx wrote on 21/07/2006 03:01:04 PM:

Adam,

When using named activation groups, the activation group 

remains active

until the job ends or the activation group is reclaimed.

You need to sign off and sign back on.

Or 

RCLACTGRP MAIN

HTH,


Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx 
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of 
AGlauser@xxxxxxxxxxxx
Sent: Friday, July 21, 2006 2:35 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Updated service program, but not seeing changes

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
##############################################################
#######################
-- 
This is the Midrange Systems Technical Discussion 
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

-- 
This is the Midrange Systems Technical Discussion 

(MIDRANGE-L) mailing 
list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

##############################################################
#######################
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
##############################################################
#######################
-- 
This is the Midrange Systems Technical Discussion 
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.