You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The intent is to kill the job unless the DEBUG flag is set (to a negative value). So if DEBUG is 0, we invoke .LOGOUT, which is supposed to kill the job if it is top-level. However, .logout with no AC specified, or an AC of 0 specified, will only kill top-level jobs. The job won't exit if it is an inferior job. For that, the code should be:
.LOGOUT 1,
I'm not sure if it really matters, since it only impacts people running it as an inferior job (e.g. for debugging), and when they do, they would normally set DEBUG to -1. However, I was trying to figure out why the job was not working reliably, and happened to notice that when DEBUG was 0, the job didn't terminate.
The text was updated successfully, but these errors were encountered:
Has the following subroutine (accessed via JSR):
The intent is to kill the job unless the DEBUG flag is set (to a negative value). So if DEBUG is 0, we invoke .LOGOUT, which is supposed to kill the job if it is top-level. However, .logout with no AC specified, or an AC of 0 specified, will only kill top-level jobs. The job won't exit if it is an inferior job. For that, the code should be:
I'm not sure if it really matters, since it only impacts people running it as an inferior job (e.g. for debugging), and when they do, they would normally set DEBUG to -1. However, I was trying to figure out why the job was not working reliably, and happened to notice that when DEBUG was 0, the job didn't terminate.
The text was updated successfully, but these errors were encountered: