Deferred Batch Process |
DEVELOPER |
 |
|
Deferred Batch Process |
DEVELOPER |
|
This feature has been designed to improve the Lookmode copy and Logic Editor save processes. The cross-reference data used by the PROIV Developer search and dependency process can take some time to generate on larger functions/ slower machines. PROIV Developer has therefore been designed to perform this task as a background process using the PROIV Batch Facility.
When PROIV Developer is first executed in a session a check is made to test that PROIV Batch Mode is functioning correctly. If the test fails, a message appears warning that the PROIV Developer Batch Facility has been disabled. This does not indicate any problems for PROIV Developer, but it may result in slower opening of Lookmode functions and saving of large logics.
The following guidelines may assist in enabling the Batch Facility where it has failed:
Is the correct version of the PRO executable in the user's path (Unix)?
Is the physical file batchque.pro installed by PROIV in the PROPATH directory? If you use separate PROPATH and PRODATA directories, this must be moved to the PRODATA directory.
Does the user have sufficient permissions to create files in the current working directory? The Unix user must be able to read and write to batchque.pro, and also able to create the text files (batch1.lst, batch2.lst, etc) generated by the PROIV Batch Mode process.
Is the administration tool Batch Queue Monitor displaying queued processes? If these do not disappear as they are processed they may be deleted to clear the queues.
Are there are Open Client run-time licences and PROIV run-time licences available? PROIV Batch Mode process requires both sets of licences.
Topic ID: 500072