You cannot do LISTCAT without some extra software support, but you can issue MODIFY CATALOG commands from the console. I would focus on two. Issue these commands on both a working system and on the problem system.
First verify that you indeed have two-level alias specified. That is not the default. MODIFY CATALOG,REPORT Look for the alias level setting. If the alias level is not right, you can change it dynamically. Then verify that after trying to use the catalog, it's really open. MODIFY CATALOG,OPEN If the catalog does not show up in the open list, you need to explore why. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Thursday, August 27, 2015 7:39 AM To: [email protected] Subject: Re: Catalog entry not visible Also, if you are not aware, there is an ACF2 list on CA Communities that might be better able to help go to support.ca.com and select the COMMUNITY menu option. or you could also join the ACF2 list on Yahoogroups https://groups.yahoo.com/neo/groups/ACF2-L/info Lizette -----Original Message----- >From: Lizette Koehler <[email protected]> >Sent: Aug 27, 2015 7:17 AM >To: [email protected] >Subject: Re: Catalog entry not visible > >Information I would need at this point is > >1) Did you contact CA ACF2 for assistance? They are very helpful and can >probably resolve this issue more quickly. >2) The output of the following IDCAMS lists > LISTC ENT('QWS.SEC.RULES') all >3) Provide the section of SYSLOG where your IKJ message occurs, 10 lines above >and below the message. I am looking for additional IDC, IGD, IEC, etc type >messages. >4) Show us the manual section in the ACF2 manual that states you use a >SHAREOPT(1,3) >5) Did you contact CA ACF2 for assistance. >5) Have you searched the CA Support website to see if there is already a >suggestion for this issue? > >You can code a proc in proclib to do step 2. Then issue a S xxxxx and get the >listing. If security is not available, you may not be able to run the job. > >The list is great, but if there is this much difficulty, then contacting the >vendor could resolve this issue more quickly. > >Lizette > > > >-----Original Message----- >>From: "Steely, Mark" <[email protected]> >>Sent: Aug 27, 2015 6:30 AM >>To: [email protected] >>Subject: Re: Catalog entry not visible >> >>I think the VVDS needs to be dump and look at the entry and see if the VVDS >>has the correct catalog listed. >> >>Thanks >> >>-----Original Message----- >>From: IBM Mainframe Discussion List [mailto:[email protected]] >>On Behalf Of Nathan Astle >>Sent: Thursday, August 27, 2015 7:49 AM >>To: [email protected] >>Subject: Re: Catalog entry not visible >> >>Hi John, >> >>The System is not yet fully up and it is failing at the Security product >>start up. I can see the Catalog services are available. >> >>Nathan >> >>On Thu, Aug 27, 2015 at 6:15 PM, John McKown >><[email protected]> >>wrote: >> >>> On Thu, Aug 27, 2015 at 7:36 AM, Andrew Rowley < >>> [email protected] >>> > wrote: >>> >>> > Stretching my memory, isn't there something about VSAM files can >>> > only be cataloged in 1 catalog, unless they are SYS1.* datasets? I >>> > think there is some information in the VVDS? >>> > >>> >>> This is correct. There are "special dispensations" for VSAM data >>> sets which start with SYS1. _or_ are PAGESPACE data sets. But, in >>> this case, the VSAM data set in question is said to be in a _shared_ >>> catalog. Which is certainly allowed. The OP can "see" it in a 3.4 >>> listing on both systems. I don't remember reading what else has been >>> tried. Personally, on the new system, I think that I'd try a simple >>> TSO ALLOCATE of the DSN in my TSO session. I don't recall if the OP >>> has done this or not. >>> >>> >>> >>> > >>> > Regards >>> > >>> > Andrew Rowley >>> > >>> > >>> >>> -- >>> >>> Schrodinger's backup: The condition of any backup is unknown until a >>> restore is attempted. >>> >>> Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be. >>> >>> He's about as useful as a wax frying pan. >>> >>> 10 to the 12th power microphones = 1 Megaphone >>> >>> Maranatha! <>< >>> John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
