×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Wed, Oct 4, 2023 at 11:07 AM Rob Berendt <robertowenberendt@xxxxxxxxx> wrote:
I would assume that the A and B are arbitrary in the command DSPWSUSR and
it gets its info much the same as the following. Probably filters it down
by job_name_short matching the current job.
I would assume that the A and B are not arbitrary. The A should be the
initial one.
But thank you for the SQL example; I'm sure it can be tweaked to
identify which job came first, if needed. In OP's case, it's not
needed, since they just wanted to know *whether* there was more than
one instance of a given workstation job. And it sure beats scraping
the printed output of the DSPWSUSR command.
John Y.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
