D TCPIP,,N,CONN,MAX=10000 gives : "37 of 239 records"
Surely the 'MAX' parameter here is a function of the TCPIP code that responds to the operator command - MXI has no effect on it. I get this problem when issuing commands from SDSF, TSO CONSOLE, the master console or MXI. I really do not think this is an MXI problem. Rob Scott www.rs.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Patrick O'Keefe Sent: 23 September 2005 15:52 To: [email protected] Subject: Re: MXI 4.3 On Fri, 23 Sep 2005 05:07:55 -0400, Rob Scott <[EMAIL PROTECTED]> wrote: >... >I tried adding the "MAX=10000" for good measure - but that did not make >any difference. >... None? When I try it with MAX the numbers still don't agree, but they are much closer. Close enough that I expect a miscount on IBM's part - probably because of a rapidly chaning number of connections. Displays of more static things (like PORTList) have an accurate count. The default MAX for 1.4 & 1.6 is 100 but it sounds like it was 50 back on 2.10. >I don't think this is a problem with MXI as I can re-create this problem >by entering the command at the z/OS master console. >... I'm not so sure. If you're letting MAX default you're defintely going to truncate data. I'd put in a large MAX if I were you.) Is that something we can do in MXI?) The max MAX in 1.4 is 56535. Pat O'Keefe ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
