IBM Mainframe Discussion List <[email protected]> wrote on 06/27/2005 11:26:49 AM:
> Things to check: > > When you use IPCS, the dialog components are located in data sets > SYS1.SBLS* which are located on your sysres volume. Make sure you're using > the version of IPCS which came with z/OS 1.6. An easy way to do this is to > go into IPCS, and type command ISRDDN on the command line. Scroll down the > list of data sets and make sure that all SYS1.SBLS... data sets are coming > from the volser which is your sysres for z/OS 1.6. > > Also, IPCS must have the correct IPCSPARM data in order to operate > correctly. On your z/OS 1.6 sysres volume, you should find a data set > named SYS1.IBM.PARMLIB (or whatever your sysprog decided to call it) which > contains all the IPCS formatters for that version of the operating system. > If you try to use IPCS and it's picking up formatters from an older > operating system, you will find that some functions might possibly work > (representing functions which didn't change) but many won't. Here's a > quote from the z/OS Init and Tuning Reference manual which describes this > in more detail: > > 7.0 Chapter 7. BLSCECT (Formatting exits for dump and trace analysis) > > The BLSCECT member specifies, through embedded parmlib members, the names > of IBM-supplied exit routines. The routines analyze and format dump and > trace data. While analyzing a dump or trace, you can enter interactive > problem control system (IPCS) subcommands to run the routines. > > IPCS accesses the BLSCECT parmlib member through the IPCSPARM DD > statement. If you allocate FILE(IPCSPARM), IPCS uses this data set for > BLSCECT and the embedded parmlib members. If IPCSPARM is not allocated and > IPCS is running on a level of OS/390 [z/OS] that supports parmlib > concatenation OS/390 R2 or later), the current concatenation is allocated, > used, and then freed. If IPCS is running on a level of OS/390 [z/OS] that > does not support parmlib concatenation (pre-OS/390 R2), SYS1.PARMLIB > contains BLSCECT and all parmlib members embedded in BLSCECT. > > See PARMLIB in topic 58.9 for information on parmlib concatenation. > > On Mon, 27 Jun 2005 09:41:45 -0500, Mark <[EMAIL PROTECTED]> wrote: > > >We've installed z/OS 1.6. We are moving from OS/390 V2R9. > > > >In the new Z/OS IPCS system (under TSO) I seem to be missing a module. > > > >When selecting an option under analyze, I get the > > > >CSV003I REQUESTED MODULE IARZINIT NOT FOUND > > > >message. Most of the rest of IPCS works fine as far as I can tell. > >We've only had the system up for about a week or so. > > > >I do not have this problem with my old OS390 system suggesting that the > >basic installation took care of this for me, or perhaps it was not part > >of the OS390 system. Or perhaps the 0S390 installer fixed this problem > >without noting it. > > > >Can anyone point me in the right direction to look for the source of my > >problem? For instance, what library is this supposed to be in? And > >what standard delivered proc was this library supposed to be included? > > > >Hopefully I can determine if the program is in the proper library and > >the library included the the proper proc for starters. > > > >Please be easy on me. I do not have system admin experience. They guy > >who normally does this, will be out for the next couple of weeks and I'd > >like to see if its possible to get this fixed sooner rather than later. > >I have dumps to review. IARZINIT was the RSMDATA subcommand and the RSM Analyze exits for dumps of systems running ARCHLVL 1 (ESA/390 architecture). Since z/OS 1.6 does not support ARCHLVL 1, this code was deleted in z/OS 1.6. The fact that your IPCS is looking for it is likely due to the IPCSPARM issue explained above by Brian Peterson. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- 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
