Cut the guy some slack, people... Obviously, he has been thrown into a new job without any kind of training on that job. He is "swimming"...
> >>My fault, I'm referring to our Z/OS consoles, we have four of them, >>each identified by a Tel#. Their different TSO's as I'm told. Is that >>like having 4 different "systems" running? It is one or the other. Either you our looking at the console, or not. If it is a console, then the messages you see are an extract of the (MVS) system log. Depending on how the particular console is configured, some messages will be displayed, others will not. From what I read in the previous posts, it seems to me that you are indeed looking at a console and that the routing codes (RTFM, there is a _lot_ to learn...) are set such that tape-related messages (amongst others) are displayed. If you are a "tape-ape" (no offense), this seams appropriate. You say you have 4 consoles. This does not tell us anything about the system (s) these consoles are connected to. It may be that all 4 are connected to only one system, that some are connected to one system and others to another system, or any combination. There is no way of telling from what you posted. Mind you, when I say system, do not think separate physical boxes... Configuration of LPARs and MVS images running in them varies a _lot_ between installations. No way of telling from what you posted. If there is zVM in the installation, things are even more flexible (and confusing...) You really need to be told what systems you are looking at through those different terminals by someone who knows. I am affraid there is no other way of knowing... > >No, TSO doesn't run on consoles and it's like having 4 different jobs >running, possibly all on the same system. If it's TSO then the If indeed you would look at TSO (which I don't think you do), then this means that your terminal is connected to a particalur address space where the Time Sharing Option is running. TSO is kind of a command processor and nowadays usually comes configured such that it automatically fires up ISPF when you connect to it. ISPF is what makes TSO easy (well, compared to line- mode TSO, anyway...) ISPF dialogs come in a very wide array. It is not impossible that you have a dialog running which is presenting you the relevant messages and enables you to enter the commands. But again, I don't think this is what you have. SDSF is a product that enables console access from a TSO session (amongst many other things). Once more: RTFM (yes, I know, it will take you half a year to read all the stuff...). >>And that's probably why I'm supposed to check >>for outstanding messages on each console. This seems to indicate that you do have several MVS images. >>If Tel1 prompts me for a tape, what message would I >>get if a D U,,, that drive from another console? Depends on what console is connected to what system and how these systems are configured and what (additional) system software is running. It is possible to share units amongst different systems. And it is possible that units are swithched (automatically or manually) from one system to the other. No way from telling what will happen in your particular installation without knowing more about the configuration of that installation. >>(come to think of it, all the messages are tape >>related, aren't there many other things going on in the mainframe?) This makes me think you are indeed looking at a console that is configured for tape-related operations. Really, your system programmer should tell you. >is going on. I suspect that you're running a TSO application specific >to tapes. Again, you haven't told us what it is. IMHO the OP is looking at a console, not a TSO application. It is true that he did not tell us, but it is my understanding that he does not know for complete and utter lack of training... Cheers, Jantje. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
