RE: OVRDBF not allowed in Secondary Thread

Assuming an RPG IV trigger program, take a look at the EXTFILE keyword of the F-Spec.

You can use a variable name in EXTFILE along with the USROPN keyword to control which file gets
opened.

Assuming the file causing the trigger to be fired is in the same library as the file the trigger
writes to, you can get the library from the trigger buffer.

HTH,

Charles Wilt
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Dave Murvin
Sent: Thursday, April 03, 2008 12:01 PM
To: Midrange Systems Technical Discussion
Subject: OVRDBF not allowed in Secondary Thread

I am trying to get a trigger program to work correctly when the physical
file is changed by a Java program in the JVM. My current problem is
CPF180C Function OVRDBF is not allowed in a secondary thread.



The trigger program will write a record to an audit file if selected
changes occur to the physical file. The initial problem that I found is
that the JVM job only has QGPL and TEMP in the library list no matter
what environment the job runs in (Test, Dev, Production). When the
trigger program tries to write to the file it blows up because it can
not find the file. I am hesitant to go to the stage where I have to
hard code the file libraries for each trigger file and have different
trigger programs depending on the environment.



I tried putting the file the trigger writes to in the same library as
the application uses - No joy. Trigger can not find the file to write
to.



My latest try was to retrieve the library the trigger program was
compiled to, parse that library into the files library for the
environment, override the file, then manually open the file. This
should happen only the first time the trigger was called. This method
would require compiling the trigger program into the various
environments, but it would be the same source and not have any hard
coding of file libraries. Using this method, the trigger program blows
up with CPF180C - Function OVRDBF not allowed in a secondary thread.
As a mater if interest, the program dump only has the indicators and the
1st page program status area info. At the bottom of the dump, it says
"Variable data is not available in a secondary thread".



If I change the physical file with WRKDBF, everything works fine.



Any suggestions besides hard coding the file library in the trigger
program and having different source for the trigger program for each
environment? This method sounds like a screw up just waiting to happen.



Thanks



Dave





--
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 e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.