× 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.


  • Subject: Re[2]:Changing subsystem sign-on
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Wed, 22 Oct 1997 14:57:20 -0400

>At 10:18 AM 10/22/97 -0400, you wrote:
>>If it's by user, you can have their initial program do a TFRJOB QCTL..
>>To see if they've already transferred, RTVJOBA RUNPTY - if it's 20
>>they're in QINTER, if it's 10 they're in QCTL..
>
>Do you mean to tell me that there is no other way to determine what
>subsystem you are in currently?????

Once upon a time, I had an MI program for the /38 that found the
name of the JOBQ that your job was submitted into.  I have no idea
if it still works, or if there's an API that does it nowadays...

I can find the source if you're interested, but I'm pretty sure it
had a hard-coded entry into the job table...

I used to use it for just this reason: our system was taken down for
backups at 19.00, and I wanted to easily see if I remembered to 
transfer into QCTL or not.  I put the "subsystem" name on my
menu.

Buck Calabro
Commsoft, Rensselaer, NY

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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.