• Subject: Re: MIDRANGE-L Digest V1 #720
  • From: John Carr <74711.77@xxxxxxxxxxxxxx>
  • Date: Fri, 31 Oct 1997 20:40:27 -0500


Date:   10/31/97 10:08 AM
RE:     Re: MIDRANGE-L Digest V1 #720


>Lessee.. the IBM/1130 had 'data switches,' that did much the same thing as
>job switches.  These were a row of 16 switches that you turned on/off.
>The IBM/360/20/5 had job switches.  You had to translate the switch
>combination into Hex and set 4 dials on the front of the console.
>And, of course, the S/3, S/38, and AS/400 still have them.
>--Paul E Musselman
>PaulMmn@ix.netcom.com


The 370 had them too.   I used to write RPG 1 1/2 on the 370.
The other name for job switches was ????..................

............... Thats right,   UPSI

John Carr 



>Al wrote (in part):

>Job switches aren't used very much today.  They came from the System/3 (or
>possibly before, but that's where I started).  When you submit a job, they
>can be specified specifically, or the default is to take them from the
>*JOBD.  When CL was upgraded from the System/38 to the AS/400, many
>parameters of the SBMJOB command were upgraded from *JOBD to *CURRENT, but
>the SWS parameter was not changed (as they are not used heavily).  The
>upgrading of the default parameters from *JOBD to *CURRENT simplified
>coding, but broke many programs when they were converted from S/38 mode to
>native.
>
>Al

+---
| 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
+---


This thread ...


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

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