Running drop schema statement hangs

[abmusse]

• Node.js version: v12.18.4
• idb-connector version: 1.2.10
• IBM i version:: 7.2

Describe the bug When trying to drop a schema the program hangs. Looks like the schema get held by a lock.

To Reproduce Steps to reproduce the behavior:

I first created a schema via Run Sql Scripts:

Then using idb-connector attempted attempted to drop the schema

const { dbconn, dbstmt, SQL_TXN_NO_COMMIT, SQL_TXN_ISOLATION,
 } = require('idb-connector');

  const schema = 'IDBTEST';
  const dropSchema = `DROP SCHEMA ${schema}`;
  const findSchema = `SELECT SCHEMA_NAME FROM QSYS2.sysschemas WHERE SCHEMA_NAME = '${schema}'`

  const connection = new dbconn();
  connection.debug(true);
  let isolationLevel = connection.getConnAttr(SQL_TXN_ISOLATION);
  console.log('BEFORE: Isolation level is: ', isolationLevel);
  connection.setConnAttr(SQL_TXN_ISOLATION, SQL_TXN_NO_COMMIT);
  isolationLevel = connection.getConnAttr(SQL_TXN_ISOLATION);
  console.log('AFTER: Isolation level is: ', isolationLevel);

  connection.conn('*LOCAL');
  const statement = new dbstmt(connection);

  console.log('finding schema...');
  statement.exec(findSchema, (r, e) => {
    if (e) { throw e; }
    console.log('find schema result: ', r);
    statement.closeCursor();
    console.log('dropping schema...');
    statement.exec(dropSchema, (r2, e2) => {
      if (e2) { throw e2; }
      statement.close();
      connection.disconn();
      connection.close();
    });
  });

Output:

Trying to drop the schema from Run Sql Scripts:

FYI I needed to set the isolation level to no commit to avoid this error:

@dmabupt Have you run into this before?

Expected behavior Should be able to drop the schema successfully without hanging

[kadler]

When dropping a schema, if there are unsaved journal receivers the job will go in to message wait indefinitely. I suspect that's what's going on here.

You can double check in WRKACTJOB if the status says "MSGW". If so, you can use option 7 on the job to answer the messages. You can also work around this with reply list entries, but they are system-wide and require special authority to set.

[abmusse]

Spot on there was a QSQSRVR job in MSGW Status. I Hit option 7 and replied with I to continue operation then my code terminated successfully.