Re: EGL add creates lock

[Steve Mervosh <spm@xxxxxxxxxx>]

Have you looked into using

sysLib.commit();

I saw this in InfoCenter and have used it in places within my code:
In most cases, EGL performs a single-phase commit that affects each
recoverable manager in turn. In most cases, this releases the read position
and the update locks in any file or databases.

EGL does implicit commits at times, but I was worried about locks myself,
and decided to put in explicit sysLib.commit's after my SQL operations.

In addition, I have used
sqlLib.disconnectAll();
in a situation where the user might wait a long time before responding to a
prompt - so I didn't want any database access methods lingering around when
the user might have went to lunch, etc.

The sqlLib.disconnectAll() system function disconnects EGL from all
databases.


    Before disconnecting, invoke sysLib.commit() or sysLib.rollback().

****************************************************************************************************

I'm trying to create an EGL page that allows users to modify batch
requests and calls the appropriate COBOL batch program.

I have created/tested the page that loads/modifies the user's request
lines.  I added a submit button to call the program and am running into
an issue.

First, when a request is submitted the request lines get written to an
intermediate file to ensure the report is run with the requests at
submission time.
Then the batch program reads the intermediate file and once the requests
are loaded into the program, the records from the intermediate file are
deleted.  My problem lies here.

When I execute the EGL 'add' statement to create the intermediate
records, a lock is created and the batch program cannot access those
records [access is I-O] because of the lock.

How do I get rid of this lock once all of my records are added to the file?


Steve Mervosh
THOR (Total Hardware and Order Repository)
Software Development
IBM Rochester Minnesota
spm@xxxxxxxxxx