Make that RCLRSC.

Thank you, Ringer!

I was dealing with the default activation group, and RCLSRC worked nicely.

When I rebuild the system, I need to delete the logical file (the one "in use") 
before deleting the old file it's associated with. The physical is an OUTFILE from 
a system command, I believe DSPPGMREF.

If RPG, some program is not setting on *INLR. Or a service program is holding
the files open. If they run in a specific activation group, you can do a
RCLACTGRP(NameHere). You can try a RCLRSC too but that's probably won't work.

But why is a member lock *SHRRD bad for you? Do you need exclusive use of the
member?

Chris

I enter a command that calls a CL program which adds a library to the library 
list, then CHGJOB JOBMSGQFL(*WRAP), then calls the RPGIV program (which goes on to 
call other CL and RPGIV programs, depending on the logic). There is no use of 
OPNSCOPE(*JOB). The RPGIV program would have been last compiled with either 
default activation group *YES,  or *NO (*CALLER).

Is it an RPG IV program? Is it running in a named activation group?
Is it called from CL? If so, is the OPNSCOPE(*JOB) parm used? 

I have a continuing problem with member locks. A user runs this particular RPGIV 
program from the command line. When he exits the program and goes back to the 
command line, member locks (*SHRRD) continue on a number of files used by the 
program. I was under the impression that the files would be released when the 
program ends; instead, the only way to remove the lock is to terminate the 
workstation session. This becomes an issue when I attempt to rebuild the files 
in the system that are built for the application, and I get a "file in use" 
message even though no one else is actually running a program that uses the 
file.

Anyone have an idea what might be going on and how I might remedy it?

Thanks.