LJ

Correct. There is no concept of 'member locking' like RDi and SEU have. This is due to the way we are connecting to the system. Not sure how to combat...

@szsascha that's how ILEditor 1 used to work, since it only had a single connection (FTP) > Allocate the member to the VS Code job (Or maybe thread? Not pretty...

@ChrisHird The way this is architected isn't the same as RDi or SEU - we don't have a mechanism to lock a member - though we can likely check if...

This is where that error is likely happening: https://github.com/halcyon-tech/vscode-ibmi/blob/master/src/filesystems/qsys/basic.js#L36 Would be interested in your feedback or PR.

I am not sure that will work. When running ILE commands (`CPYTOSTMF`), we use `system`, which is forking the connection job and running in that I believe. I am not...

Further note: your suggestion will only work when source dates are disabled (default). When enabled, we fetch the member with SQL.

We use `db2util` under the covers, which runs in the same ssh connection we get - so no new job for running SQL.

Source dates are disabled when SQL is not enabled.

@ChrisHird We are not using the `system` API, we are using the `system` command from pase. https://www.ibm.com/docs/en/i/7.3?topic=utilities-pase-i-system-utility Read the `-i` parameter.

Sure, feel free to run any tests as you wish. Moral of the store is that running these commands will have no affect on the wait time: ``` system "CHGJOB...