Chris, I don't see that your posting made it to IBM-Main (where the original thread was) so John, Sam, and Craig may not have seen your kudos. I'll double-post this response to get it back there.
Yes, I know poor, benighted Bruce is beyond hope - trying to get rid of NetView and all (Are my prejudices showing again?) - but I thought others still using NetView might have misunderstood the comments about getting rid of BNJMTERM. Pat O'Keefe -----Original Message----- From: [EMAIL PROTECTED] on behalf of Chris Mason Sent: Tue 01/17/2006 4:24 PM To: [EMAIL PROTECTED] Subject: [NetView] Re: What starts Netview? Another side issue is that this whole thread would have been better spun in the NetView newsgroup: http://groups.yahoo.com/group/NetView/ However here's my two eurocents. Unfortunately I'm having to do this from manuals from which I hope to get reminders of when I was intimately involved with these things. The program that starts NetView is in the sample procedure CNMSJ009, changed to the name CNMPROC for production use, and, as Pat has indicated, the program has the name BNJLINTX. I found a set of startup messages which contained the message BNJ080I BNJLINTB - BUFFER SIZE=24K,SLOT SIZE=200. From the message description I see that BNJLINTB is the Hardware Monitor "initializer" module which I expect gets control from BNJLINTX at a very early stage. The purpose of the message is to show the values given to the "buffer size" and "slot size" in the PARM field of the EXEC statement calling the NetView program. All modules beginning with the three characters BNJ belong to the NetView Hardware Monitor component of NetView (which originally had the name Network Problem Determination Application, NPDA). For reasons to do with the way the Network Logical Data Manager (NLDM), the Session Monitor component of NetView, and NPDA programs were packaged within the tasking structure of Network Communication Control Facility (NCCF), the base function of NetView also simply called the Command Facility component, an NPDA module needs to get control first. Expanding on what Pat said, CNMNDEF is a way of creating a member of VTAMLST entity names and types - I'm relying on memory here but it's in line with a manual reference I found. An accurate, up-to-date version of this member is needed by the "Status Monitor" component of NetView and so needs to be available when the Status Monitor component is initialised at some point during NetView start-up. I guess there's probably also a way of reloading the Status Monitor member while NetView is active after having again run this "preprocessor" program. The manuals I am trying to use are for NetView 5.2 so nothing would appear "radically" to have "changed". I'm happy - in retrospect - as are others not in retrospect - that the rather messy BNJMTERM requirement is now handled better and with less transparency. Let me congratulate John Eells, Sam Knutson and Craig Gordon for having comprehensively and neatly dealt with the CSECT IEAVTRML issue. Will I be booed off the court if I mention I vaguely remember a third name I had to worry about in that CSECT? Bruce, just make sure that your NetView and IMS are at the appropriate levels not to need the "zap" and then reverse the "zap". Document your research and copy any interested parties so that your posterior will be safe when the "why did we crash" meeting is held :-) Pat, if Bruce is trying to get rid of NetView - sacrilege I know - there will not be any need for any BNJ modules anywhere. Incidentally, the original poster is this heretic Bruce :-) I hope that's cleared everything up ... Chris Mason ---------------------------------------------------------------------- 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
