We've done the same thing here, and occasionally I've run into a small
problem. Normally, when I sign on I go to QINTER, which I assumed was
because the other subsystem was named QXXISD , which is later in the
alphabet. But sometimes I can't sign on with my regular workstation device
name, and when I change the name and get on I discover that my regular
device has been locked by some job in QXXISD, even though there appears to
be nothing running in QXXISD. If I stop and restart QXXISD, everything is
fine again. This doesn't happen every time, but it tends to average 2-3
times a month.

Does anyone have any ideas on what might be causing this, and whether
there is a fix?

TIA,

Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> writes:
>We made a separate subsystem for the IT department. Our WSID's are
>assigned
>there. Each night before our backup runs, QINTER is ended by the IBM job
>scheduler. The last job on our nightly processing queue is to start
>QINTER.
>This keeps users off the system until everything completes sucessfully. If
>we are planning an upgrade over the weekend, we simply remove the startup
>job from the queue. We can dial or VPN and we still have our subsystem up
>and running. 
>HTH,
>Cyndi B.


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@xxxxxxxxxxxx


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.