Yes. Even after making entry for Netview load library in LPALST00 parmlib member, I am not able to find it in this ISRDDN LPA command.
Not able to determine, where I am missing. On Mon, Jun 9, 2014 at 8:23 AM, Lizette Koehler <stars...@mindspring.com> wrote: > You may need to contact IBM for assistance, > By doing internet searches with IBM CNM598W I came up with the following > > http://www-01.ibm.com/support/docview.wss?uid=swg1OA40138 > > > OA40138: WHEN MATCHING SUBSYSTEM HAS NOT BEEN INITIALIZED, ABEND0E0 OCCURS > DURING NETVIEW INITIALIZATION > > NetView V6R1 code was written expecting that all required procedures are > followed prior to starting the NetView program. However, there are some > situations where an appropriate SUBSYS statement is not specified in the > IEFSSN subsystem name list, but the NetView program needs to be started. > When this is true, ABENDs occur because the Canzlog data space is assumed > to be available, but it is not because proper initialization has not taken > place for the subsystem. > > The Tivoli NetView for z/OS V6R1 Installation: Getting Started manual > (GI11-9443-03) should be changed as follows: > - A new Usage Note should be added to the description of how to update > member IEFSSNxx in subsection "Updating SYS1.PARMLIB Members" in Chapter 2, > "Preparing the MVS System", which should read as follows: > o If you choose not to add the NetView subsystem to the subsystem name > table, you can dynamically add it before starting the NetView subsystem. > For information on dynamically adding the subsystem name to the table, see > Starting the NetView Subsystem Address Space Using Job CNMPSSI. > > The following should be added to section "Starting the NetView Subsystem > Address Space Using Job CNMPSSI" in Chapter 6, "Activating the NetView > Program", just before the paragraph starting with "You can start the > NetView subsystem address space": > If you did not add the NetView subsystem name to the IEFSSN subsystem > name table, you can follow these steps to dynamically add the subsystem > name: > 1. Make sure that the SSI procedure (CNMSJ010 sample) is not active. > 2. Issue the following SETSSI ADD system command to dynamically add > the subsystem name: > > SETSSI ADD,SUBNAME=xxxx,INITRTN=DSI4LSIT > > where xxxx specifies the first four characters of your procedure > name. The NetView instance recognizes the new status within 10 seconds. > This command remains in effect until a system IPL occurs. > 3. To ensure that archiving and automation are properly initialized > with the new status, issue the following commands: > o RESTYLE ARCHIVE > o RESTYLE MVSPARM > > Note that the SETSSI ACTIVATE command is not supported by the > NetView subsystem. > > If a value is specified for SSI.ProcString in the CNMSTYLE member, > your subsystem address space will automatically start after the RESTYLE > MVSPARM command. > > > It sounds like all implementation steps have not be done. > > I would use ISRDDN on the system where Netview is not initializing and > enter LPA on the command line. Then MEMBER DSI4LSIT to make sure it is > actually there. > > Lizette > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > > Behalf Of Mainframe Mainframe > > Sent: Sunday, June 08, 2014 6:41 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: Netview 6.1 install > > > > Hello, > > > > Thanks for reply. Even after making entry in LPALPST for > netview loadlib > > SYS1.SCNMLPA1, I am getting below error, while starting NETVSSI address > > space. > > > > IEF695I START NETVSSI WITH JOBNAME NETVSSI IS ASSIGNED TO USER > > ++++++++ > > $HASP373 NETVSSI STARTED > > IEF403I NETVSSI - STARTED - TIME=18.36.41 CNM598W SSI initialization > > routine missing for NETV. > > - -----TIMINGS (MINS.)------ > > -----PAGING COUNTS---- > > -STEPNAME PROCSTEP RC EXCP CONN TCB SRB CLOCK > > SERV WORKLOAD PAGE SWAP VIO SWAPS > > - NETVIEW 12 11 2 .00 .00 .0 > > 242 SYSTEM 0 0 0 0 > > IEF404I NETVSSI - ENDED - TIME=18.36.41 > > -NETVSSI ENDED. NAME- TOTAL TCB CPU TIME= .00 > > TOTAL ELAPSED TIME= .0 > > $HASP395 NETVSSI ENDED > > $HASP250 NETVSSI PURGED -- (JOB KEY WAS CD46D86F) > > > > > > Do I need to apply OA42162 APAR as well, or some other issues > > > > > > > > > > On Mon, Jun 9, 2014 at 4:41 AM, Lucas Rosalen <rosalen.lu...@gmail.com> > > wrote: > > > > > Yep... check for netview loadlib in lpa. > > > > > > Lucas Rosalen > > > Em 08/06/2014 19:40, "Ed Finnell" < > > > 0000000248cce9f3-dmarc-requ...@listserv.ua.edu> escreveu: > > > > > > > Info APAR OA42162 sums it up pretty well. SMP/E should tell you > > > > where > > > the > > > > modules were installed. This DSN should be in LPALIST. The APAR > > > describes > > > > how to add to running system with LPA ADD. > > > > > > > > > > > > In a message dated 6/8/2014 1:46:44 P.M. Central Daylight Time, > > > > stars...@mindspring.com writes: > > > > > > > > How did you define the entry in SCHEDxx member? Something like the > > > > following? > > > > > > > > > > > > SUBSYS SUBNAME(xxxx) INITRTN(DSI4LSIT) INITPARM('TINYDS') > > > > > > > > > > > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
