Stuart Redbook's are Curate's eggs. Fortunately this is still a "Draft" so if I can "stir my stumps", I can get the problem fixed.
The problem is that the TRLE example in Appendix B is *not* the one used for all the command and display examples in the appendix - very poor! You will note that the commands and display examples refer to a TRLE with a PORTNAME operand value OSA2080 while the all the TRLE statement examples have a TRLE statement name OSAE200P and PORTNAME operand value OSAE200 - very poor! Nevertheless the convention adopted by the examples appears to be that the value of the PORTNAME operand is OSAxxxx and the name of the TRLE statement is OSAxxxxP - for whoever knows what weird reason! Thus, as I said in my previous post and you appear not to have noticed, you need to use the value of the PORTNAME operand of the TRLE statement also as the value of the PORTNAME operand of the VARY TCPIP,,OSAENTA command as can be seen from the example in the redbook, namely V TCPIP,TCPIPA,OSAENTA,ON,PORTNAME=OSA2080,IP=10.1.2.11,PORTNUM=2323 You will note that the PORTNAME operand here lacks a final "P". I even made sure that this was the *only* example of the VARY TCPIP,,OSAENTA command in the whole redbook in order to be sure you had not been misled by another example. Thus, for the second time, the answer to your correctly composed question, even following the example in the redbook and according to your names, would appear to be VARY TCPIP,TCPIP,OSAENTA,ON,PORTNAME=OSA408 I've said it before, I'm saying it now and I'll no doubt be obliged to say it again: when you have problems having followed examples in redbooks, you'd better actually read the "official" manuals in order to be sure that what you think you understood from the redbook is correct. The "official" manuals in this case are the ones prefixed with z/OS VxRy Communications Server IP <something>. Redbooks are *not* official manuals. They are written by people like yourself who are drafted in to man - or woman - the redbook projects. They are not written by development shop authors. Incidentally, it would appear that, when a "hardware" address is understood to be a port used for the OSAENTA function, it changes its type from "DATA" to "TRACE" as well as changing status from "RESET" to "ACTIVE". Chris Mason On Wed, 4 Mar 2009 15:48:07 -0000, Stuart Willis <[email protected]> wrote: >Hi Chris > >The Processor was only delivered in January so I assuming it has all the >latest levels of microcode. CODE LEVEL = 0891 > >I'm following the instructions in APENDIX B of the following manual > >http://www.redbooks.ibm.com/redpieces/abstracts/sg245948.html? Open&open& >cm_mmc=4851-_-n-_-vrm_newsletter-_- 10300_105452&cmibm_em=dm:0:7664116 > >Example B-11 shows the TRACE DEV to be in a ACTIVE status where mine is >in RESET ? > >I have enabled the OSA-Express NTA via the HMC as per Figure B-5 in the >manual. > >> Does anyone know how to activate it? Sorry this is a bit misleading > >How Do I get the trace Device to an ACTIVE status as apposed to RESET > > >Hope this make sense > >Regards >Stuart > > > > -Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On >Behalf Of Chris Mason >Sent: 04 March 2009 15:10 >To: [email protected] >Subject: Re: OSAENTA device problem > >Stuart > >Here's what is said about the PORTNAME operand of the VARY >TCPIP,,OSAENTA command in the Communications Server (CS) IP System >Administrator's Commands: > ><quote> > >PORTNAME=osa_port_name > >Specifies the name of the OSA port for which tracing is desired. This is >the >same port name that is defined on the VTAM TRLE statement PORTNAME >keyword. This parameter is required. > >Tip: You are not required to also define OSA-Express to TCP/IP using the > >DEVICE/LINK or INTERFACE statement in order to collect trace data. > >Restriction: Multiple stacks cannot use the tracing function >concurrently for a >given OSA. > ></quote> > >> VARY TCPIP,TCPIP,OSAENTA,ON,PORTNAME=TRL408 > >is your command and > >> TRL408 TRLE LNCTL=MPC, >> MPCLEVEL=QDIO, >> READ=0408, >> WRITE=0409, >> DATAPATH=(040A,40B), >> PORTNAME=OSA408 > >is your TRLE statement. > >You appear to be using the TRLE statement name rather than the name >given >by the PORTNAME operand. It's possible that this has something to do >with >your problem. > >To answer your presumed question - edited into an English sentence: > >> Does anyone know how to activate it? > >but tentatively, try the following: > >VARY TCPIP,TCPIP,OSAENTA,ON,PORTNAME=OSA408 > >Before this post appeared, I had spotted the OSAENTA "thing" only with >peripheral vision while researching other OSA-related topics, so thanks >for the >opportunity to become more closely acquainted with it. > >Incidentally 1: I see from the section on OSAENTA in the CS IP >Configuration >Guide that OSAENTA support depends on the OSA-Express2 feature in some >way. Perhaps it is a matter of a microcode upgrade. Have you checked >that >your OSA feature supports OSAENTA? > >Incidentally 2: From the example of the output from a DISPLAY >NET,TRL,TRLE >command in the CS SNA Operations manual, I see only one DATA DEVice with > >STATUS=ACTIVE and three with STATUS=RESET. Given that this tracing >function is a bit of a fiddle using existing structures, are you sure >that the >status of the DATA DEVice should change from RESET to ACTIVE? Perhaps >someone who has already used the OSAENTA function can clarify this >point. > >Incidentally 3: "BOOK"! There's a bit of a VSE flavour about that isn't >there? > >Chris Mason > >On Wed, 4 Mar 2009 07:35:16 -0600, Stuart Willis ><[email protected]> wrote: > >>I'm trying to run an OSA trace after I issue the Vary command and >display the >>TRLE the device is in REST status when is should be ACTIVE >> >>IST1221I DATA DEV = 040B STATUS = RESET STATE = N/A >> >>The manual tells me "Subchannel path is not ready" but the device is >there >an >>online. >> >>Any one know how to activate it. >> >>Regards >>Stuart >> >> >>VARY TCPIP,TCPIP,OSAENTA,ON,PORTNAME=TRL408 >>EZZ0060I PROCESSING COMMAND: VARY >>TCPIP,TCPIP,OSAENTA,ON,PORTNAME=TRL408 >>EZZ0053I COMMAND VARY OSAENTA COMPLETED >>SUCCESSFULLY >>D NET,TRL,TRLE=TRL408 >>IST097I DISPLAY ACCEPTED >>IST075I NAME = TRL408, TYPE = TRLE 109 >>IST1954I TRL MAJOR NODE = P19TRL2 >>IST486I STATUS= ACTIV, DESIRED STATE= ACTIV >>IST087I TYPE = LEASED , CONTROL = MPC , HPDT = YES >>IST1715I MPCLEVEL = QDIO MPCUSAGE = SHARE >>IST1716I PORTNAME = OSA408 LINKNUM = 0 OSA CODE LEVEL = 0891 >>IST1577I HEADER SIZE = 4096 DATA SIZE = 0 STORAGE = ***NA*** >>IST1221I WRITE DEV = 0409 STATUS = ACTIVE STATE = ONLINE >>IST1577I HEADER SIZE = 4092 DATA SIZE = 0 STORAGE = ***NA*** >>IST1221I READ DEV = 0408 STATUS = ACTIVE STATE = ONLINE >>IST1221I DATA DEV = 040A STATUS = ACTIVE STATE = N/A >>IST1724I I/O TRACE = OFF TRACE LENGTH = *NA* >>IST1717I ULPID = TCPIP2 >>IST1815I IQDIO ROUTING DISABLED >>IST1918I READ STORAGE = 4.0M(64 SBALS) >>IST1757I PRIORITY1: UNCONGESTED PRIORITY2: UNCONGESTED >>IST1757I PRIORITY3: UNCONGESTED PRIORITY4: UNCONGESTED >>IST2190I DEVICEID PARAMETER FOR OSAENTA TRACE COMMAND = 00-01- 00- >>05 >>IST1801I UNITS OF WORK FOR NCB AT ADDRESS X'0F9E4010' >>IST1802I P1 CURRENT = 0 AVERAGE = 0 MAXIMUM = 0 >>IST1802I P2 CURRENT = 0 AVERAGE = 0 MAXIMUM = 0 >>IST1802I P3 CURRENT = 0 AVERAGE = 0 MAXIMUM = 0 >>IST1802I P4 CURRENT = 0 AVERAGE = 0 MAXIMUM = 0 >> >>IST1724I I/O TRACE = OFF TRACE LENGTH = *NA* >>IST314I END >>D U,CTC >>IEE457I 13.30.19 UNIT >>UNIT TYPE STATUS >>0400 OSA A-BSY >>0401 OSA A >>0402 OSA A-BSY >>0403 OSA OFFLINE >>0404 OSA A-BSY >>0405 OSA A >>0406 OSA A-BSY >>0407 OSA O >>0408 OSA A-BSY >>0409 OSA A >>040A OSA A-BSY >>040B OSA O >>040C OSA OFFLINE >>040D OSA OFFLINE >>040E OSA OFFLINE >>040F OSA OFFLINE >> >>VTAM BOOK >> VBUILD TYPE=TRL >>TRL408 TRLE LNCTL=MPC, >+ >> MPCLEVEL=QDIO, >+ >> READ=0408, >+ >> WRITE=0409, >+ >> DATAPATH=(040A,40B), >+ >> PORTNAME=OSA408 ---------------------------------------------------------------------- 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
