RE: Terrible time with this repeated error!

You would have to change whatever program in RBT_GDBPOS is placing an
exclusive lock on the file.  And yes, I know the lock type says *SHRRD, but
there must be a more restrictive lock to get the error you were.  If the
lock is not being created by a SAVLIB or SAVOBJ command, you need only
locate the ALCOBJ command that is using *EXCL as the lock type.  

Be very careful here.  Even if the lock is not because of SAVLIB or SAVOBJ,
there may be very good reasons why the job is restricting access to the
file.  The job is likely assuming that no updates can happen to the file
while it is running.  Violating such an assumption could have, as IBM
manuals are fond of saying, unpredictable results. 

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx


<clip>
This RBT_GDBPOS( Load Program) should not lock
GMIPOSF1, how can i achieve this???
All my problems will be solved if it doesnt lock
GMIPOSF1. Its surprise to see this *SHRRD to lock the file there by abending
other programs.

My question how do I achieve RBT_GDBPOS should not lock GMIPOSF1?
<clip>