Missing INI file causes job to hang

Hi
We make extensive use of the Inifilegetkey JAL statement and have discovered what seems to be a bug with it.
If I have a job that references an ini file but that ini file does not exist it does not fail gracefully, in fact it hangs and blocks the queue it is in.

I will submit this issue for further investigation. As a workaround, please replace calls to built-in Inifilegetkey function with calls to user-defined statement. In the user-defined statement make a check for Ini file existence and if it exists, return the value from Inifilegetkey, otherwise return the default value.

Further information; the same statement, inifilegetkey hangs when the section and key you are looking for does not exist which caused us a production incident that became far bigger than it should have been.

Have you got anywhere with the original problem please? It means that a simple typo can stop processing until someone notices a queue is blocked.

So far we are unable to reproduce it. In case the specified INI file, key or value are not available, the statement returns default value for the data type which is in most cases an empty string. The result matches the documented behavior.

Can you provide a job trace file indicating that the job get stuck while executing IniFileGetKey?

I'll try to duplicate the problem in our test env.