johnny, I'm going on the assumption that PAGE.PLPA.PAGE doesn't exist and copying a non-existent catalog entry isn't going to work. Skip gave sample IDCAMS statement to define a PAGESPACE, so use it to define your PLPA, COMMON, and PAGE datasets - use different names than the system on which you run defines. Then you can copy the entries from existing master to your new master catalog and update IEASYSxx with the names. You will also need other datasets to IPL using your new master catalog (LOGREC,SMF,etc). Do IDCAMS LISTCAT of your new master to look at the contents and compare to existing catalog and parms. Good luck! Cliff McNeill
________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of johnnydeep san <[email protected]> Sent: Saturday, September 15, 2018 6:45 AM To: [email protected] Subject: Re: how to catalog page dataset to new MCAT this is wat i'm getting in my screen while loading IEA247I USING IEASYS21 FOR z/OS 02.01.00 HBB7790 ISG313I SYSTEM IS INITIALIZING IN GRS NONE MODE. RING OR STAR CONFIGURATION KEYWORDS IN GRSCNF00 ARE IGNORED. IEA920I PAGE DATA SET PAGE.PLPA.PAGE NOT LOCATED IEA922D REPLY 'DSN=DSNAME' OR 'IGNORE' 00,IGNORE IEE600I REPLY TO 00 IS;IGNORE IEA935W INSUFFICIENT PAGING RESOURCES, IPL TERMINATED On Sat, Sep 15, 2018 at 7:19 AM johnnydeep san <[email protected]> wrote: > I used todd's jcl and it ran fine but still getting same issue . > > REPRO INDATASET(CATALOG.Z110S.MASTER) - > 00210004 > OUTDATASET(CATALOG.Z210M.MASTER) - > 00220004 > LEVEL(SYS1.PLPA.PAGE) - > 00221004 > MERGECAT > 00222004 > IDC01460I THE NUMBER OF ENTRIES MERGED WAS 0 > > IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0 > > > > Should pagedatast locate in new master catalog(CATALOG.Z210M.MASTER) > volume ? . > I haven't any page datasets in new master catalog volume, it's located > in old master catalog volume . how to make understand this page datasets > to new master catalog ? .guide me. > > > > On Fri, Sep 14, 2018 at 1:37 PM Carmen Vitullo <[email protected]> > wrote: > >> when creating a new master catalog I've always used the repro mergecat >> process to get my system datasets cataloged in the new mater catalog, and >> some catalog utilities will perform the mergecat without removing the >> entries from the original maaster catalog. >> >> >> >> Carmen Vitullo >> >> ----- Original Message ----- >> >> From: "retired mainframer" <[email protected]> >> To: [email protected] >> Sent: Friday, September 14, 2018 11:37:55 AM >> Subject: Re: how to catalog page dataset to new MCAT >> >> > -----Original Message----- >> > From: IBM Mainframe Discussion List <[email protected]> On >> > Behalf Of johnnydeep san >> > Sent: Friday, September 14, 2018 4:05 AM >> > To: [email protected] >> > Subject: how to catalog page dataset to new MCAT >> > >> > Hi All, >> > >> > I have created new master- catalog and load my system from it .While >> IPL'g >> > sys throw below >> > >> > IEA920I PAGE DATA SET SYS1.PLPA.PAGE >> > NOT LOCATED >> > IEA922D REPLY 'DSN=DSNAME' OR 'IGNORE' >> >> If the dataset already exists on your page volume, the advice from Paul >> and Todd should work. If it does not exist, you need to define it with >> IDCAMS. One of the parameters will let you specify the catalog. >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
