Re: Safe to manually terminate QTESTDBGSVR job?

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

I don't do much development anymore but I'm still not finding that job.
Either the others write flawless code or debug in another fashion.

On Thu, Jun 20, 2024 at 12:32 PM Dan Bale <dan.bale@xxxxxxxxxxxxxxxxxxxxx>
wrote:

> PEBKAC error.  It's actually QTESDBGSVR.
>
> - Dan
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
> Berendt
> Sent: Thursday, June 20, 2024 12:23 PM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: Re: Safe to manually terminate QTESTDBGSVR job?
>
> EXTERNAL: This email originated from outside of the organization. Do not
> click on any links or open any attachments unless you trust the sender and
> know the content is safe.
>
> Just curious, how do you get 11 character job names?  :-) I did try this
> and got no hits:  DSPLOG PERIOD((*AVAIL *BEGIN))
> JOB(QTSTDBGSVR)
>
> *** CONFIDENTIALITY NOTICE: The information contained in this
> communication may be confidential, and is intended only for the use of the
> recipients named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution, or
> copying of this communication, or any of its contents, is strictly
> prohibited. If you have received this communication in error, please return
> it to the sender immediately and delete the original message and any copy
> of it from your computer system. If you have any questions concerning this
> message, please contact the sender. ***
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.