Actually, that advise sounds reasonable, although I will confess that I don't always follow it!
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of Charles Mills <charl...@mcn.org> Sent: Wednesday, November 7, 2018 5:58 PM To: IBM-MAIN@listserv.ua.edu Subject: Re: Ask the experts about running things I hired a tech writer once who had been taught in school that you should introduce every acronym the first time you used it: "Whizbang/390 runs on any current release of Multiple Virtual Systems (MVS) ..." And wanted to argue me into the ground on the point. I let him go on the 29th day of his probationary period. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Wednesday, November 7, 2018 2:51 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Ask the experts about running things Let's not pass up the opportunity to observe that TSO is not 'time sharing', nor is it 'optional', yet it's constantly on the lips of every mainframer. I caution newbies (and managers and auditors) not to give much weight to these acronyms. Saying 'multiple virtual storage' more than once in a meeting marks you as a doofus. ;-) . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Wednesday, November 07, 2018 1:41 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Ask the experts about running things Roughly, and in an MVS context: Address space: a context for resolving virtual addresses. There is an address space for each batch job, started task, TSO session and similar units of work. Data space: a specialized address space from which instructions are not executed. Subsystem: a body of code identified to MVS as a subsystem and providing service through the subsystem interface. Stated task: a job initiated by the START operator command rather than through the Initiator. In many cases the START is issued automatically shortly after IPL. Started tasks have identifiers starting with S or STC. Job; a unit or work. Batch jobs have identifiers starting with J or JOB. TSO: Time Sharing Option. Support for interactive units of work. Note that you can do Unix System Services work interactively without a TSO session. TSO sessions have identifiers starting with T or TSU. Process: a unit of scheduling for Unix. Depending on how the system is configured, multiple Unix processes may run in a single address space. There may b multiple threads within a process - in fact, the original name for threads as light-weight process. Enclave is a bit difficult describe; take a look at the Language Environment documentation for a start. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of Peter Ten Eyck <peter.tene...@americannational.com> Sent: Tuesday, November 6, 2018 1:59 PM To: IBM-MAIN@listserv.ua.edu Subject: Ask the experts about running things For an inquisitive programmer... what is a good definition for each of the following? How do they relate to each other? Address space Data space Subsystem Started task Job TSU (TSO) Process Enclave Note: My explanation will fall short of what IBM-Main can come up with. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
