Ladies and gentlemen attempting to follow this thread - except those who don't receive any of my posts, of course!
Sergio - I'll address you more specifically later. >...> We are migrating our environment from Z/VM, and Z/VSE to Z/OS. I'm guessing, with some evidence to hand, that this includes Sergio himself! >...> We have here a lot of EXEC's that is used from VM OPERATOR to display, >activate, deactivate lines from VTAM. >...> What We need, is execute this commands by operators under Master console >of Z/OS. Now that we've seen an example of one of these "commands": > trace r > "set secuser vtam *" > "cp sleep 2 sec" > 'CP SEND VTAM VTAM d net,pending' > "cp sleep 2 sec" > "set secuser vtam off" we can see that - ahem - this is simply a DISPLAY NET,PENDING with some fancy wrapping presumably specific to the VM environment - and dating from a time later than the time I used to teach this stuff - IIRC - since I don't believe I've ever set my eyes on this "SECUSER" concept - and why "sleeping" is required is also a mystery! So, drum roll, top hat held at arm's length, the rabbit which pops out is just to throw away the unnecessary periphery and simply enter the "raw" VTAM command. Of course, this is done "as is" on any z/OS console - in principle, since there may be RACF tricks which influence this and I will leave others to cover that as necessary. If in TSO, the command can typically be entered with a "/" prefix on the command line in the usual TSO "comfort zone", ISPF. - Sergio Well, the above is the answer to your original question which would seem to have been predicated on not appreciating that VTAM commands in a z/OS environment are operating system commands just the same a D A,L, for example. But, you may remember my saying in an earlier post that NetView is the preferred environment for the entry of VTAM commands and it's predecessors started as an environment for the management of VTAM commands before it expanded into a comprehensive automation environment more than 20 years ago. Your DISPLAY NET,PENDING is a superb example with which to illustrate the possibility I mentioned before to pick up the messages provoked by the DISPLAY command and work on them further. What do you do when you find some status code such as those you posted?: > VTAM : IST080I CICSDDS1 PNFY1 CDRKCA PACDR Well, you and all your operators may carry the meaning of all these codes around in your head. I hear that the inhabitants of Brazil have very impressive capabilities! However, if you are like most of the rest of us I expect, you now need to turn to the relevant "z/OS Communications Server IP and SNA Codes" manual in order to decipher the code from Table 12, "Resource state code values". For example: - PNFY1 means the following: <quote> Pending notify(1): A node, such as a logical unit, is being deactivated or disconnected. The request to terminate user sessions has been scheduled, but the notify request indicating that the user sessions have ended has not yet been received. For example, the application program did not issue CLSDST. </quote> - PACDR means the following: <quote> Pending activate CDRM response: A CDRM is being activated and the activate CDRM request has been sent, but the response has not been received. </quote> Actually I didn't need the manual for one of the explanations of those particular codes but that's just because one is self-explanatory and easily recognised - by a very old VTAM hand! I'm a bit puzzled you are still needing to "activate CDRMs" in this day and age. Perhaps as part of the migration from z/VM and z/VSE to z/OS you will migrate from subarea SNA to APPN. Anyhow, if you can pick up the codes within a Clist, you can actually provide typically a short explanation then and there. For example: Enter the command PENDING and receive the output CICSDDS1 - PNFY1 - Waiting for NOTIFY for termination of user sessions. CDRKCA - PACDR - Waiting for response to activate CDRM. Wouldn't it be loverly! The good news is that what I just described I know can be done because it did it[1] about 28 years ago. The bad news is that I did not actually keep that Clist - what a shame! The possibly good news is that, since this is such an obviously useful Clist, there may be a version which is part of the Clists shipped with NetView - and, even better, kept up to date with the latest VTAM. Perhaps any NetView users know or can check. - [1] I can even remember that it was during the customer classes associated with the 3725 ESP when I had to "twiddle my thumbs" between activities with the customer so I found angelic work for otherwise idle hands. - Chris Mason On Mon, 11 Jul 2011 14:03:40 -0300, Sérgio Lima Costa <[email protected]> wrote: >Hello Alan, and all others. > >Thanks very much for your help. > >Run fine, very good. > >But, for give VTAM commands under ZOS, need insert ADDRESS VTAM ? > >Look below please: > >Under Z/VM : > > 3 *-* "set secuser vtam *" > >>> "set secuser vtam *" > 4 *-* "cp sleep 2 sec" > >>> "cp sleep 2 sec" > 5 *-* 'CP SEND VTAM VTAM d net,pending' > >>> "CP SEND VTAM VTAM d net,pending" > 6 *-* "cp sleep 2 sec" > >>> "cp sleep 2 sec" >VTAM : Ready; >VTAM : IST097I DISPLAY ACCEPTED >VTAM : IST350I DISPLAY TYPE = PENDING >VTAM : IST159I THE FOLLOWING NODES ARE IN A PENDING STATE >VTAM : IST080I CICSDDS1 PNFY1 CDRKCA PACDR >VTAM : IST314I END > 7 *-* "set secuser vtam off" > >>> "set secuser vtam off" > > > > > >/**/ >trace r >"set secuser vtam *" >"cp sleep 2 sec" >'CP SEND VTAM VTAM d net,pending' >"cp sleep 2 sec" >"set secuser vtam off" > > > > >And here under ZOS 1.12 > > BROWSE SYS1.SAXREXEC(TESTE) > Command ===> >******************************** >/* rexx */ >trace r >address tso >'d net,pending' > > > > 3 *-* address tso > 4 *-* 'd net,pending' > >>> "d net,pending" > *** > > > >IKJ56500I COMMAND D NOT FOUND > +++ RC(-3) +++ >*** > >Do you know, what We need do for VTAM commands run ok? > >Thanks again, and Best Regards. > >Sergio ---------------------------------------------------------------------- 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
