Hi Eric, I haven't done 1.9 yet, but at 1.4 to 1.7, I discovered that the size of my checkpoint was too small. One very short green message that went flying by and JES2 would not finish initializing. My symtoms were the same as yours, and I didn't have any WTOR either. Having 2 checkpoints didn't help, they each had to be big enough to do the job.
HTH, Linda Mooney -------------- Original message -------------- From: Eric Bielefeld <[email protected]> > Thanks for all the great replies. I have several things to check when I get > in > Monday morning. > > Ulrich - in reply to your other message, the console is in RD mode. I don't > think that matters though, because when the messages scroll by, that's before > the console is set up in RD mode. There are a bunch of messages for > uninitialized DASD, which we haven't flashed yet. As soon as the console goes > into normal console mode, no more messages come out. MVS Display commands > work > > I should probably mention that we are doing things a little differently now. > We > set up our IODF to put the 2 production Lpars on our original dasd, which is > defined from 8000 to 8700 on our Shark. We defined duplicate DASD from 9000 > to > 9700. We plan to flashcopy everything, and back it all up from a separate > Lpar. > The 2 production Lpars have the 8000 dasd online, and 9000 offline. The 2 > test > Lpars are just the opposite. I don't think that has anything to do with my > situation, but in case it might I thought I better say so. > > In answer to the questions below, there is only one HASPACE on the Catalog > volume. I believe there are 2 checkpoints defined on the same pack. This is > basically the serverpac system. I'll check the JES2 PARM= on Monday. I don't > know what it has. I'll issue display GRS commands on Monday. This is it's own > testplex as a monoplex, and has no connection to our production sysplex. And, > as stated above, the DASD is all copys of production packs, and is all > offline > to the production sysplex. I flashed the 6 volumes that contain the serverpac > volumes just before I IPL'd to the 9000 series DASD. > > > ---- Ulrich Krueger wrote: > > Eric, > > If JES2 is about the last thing to try and come up, but hasn't yet ... > > How many SPOOL volumes do you have defined to JES2? Do they exist? > > Is there a HASPACE dataset on each volume? > > Do you have at least one HASPCKPT dataset pre-allocated and cataloged? > > Please say again: What is the PARM='...' on your JES2 PROC and / or what is > your response to the JES2 - startup message? > > If this is the first time you are starting JES2 on a new system, JES2 has > > to > format the checkpoint and SPOOL datasets. That, depending on the number of > SPOOL > volumes, can take a while, but there should be progress messages. > > > > Oh, one other thing: The names and volumes of the SPOOL and CKPT datasets > > in > use by 1.9 ... are they the same or different from what your current > production > LPAR uses? Is there a chance that your 1.9 system is trying to access the > datasets or volumes used by production JES2? You might want to check GRS for > ENQ > / RESERVE lockouts ... > > > > HTH > > > > Regards, > > Ulrich Krueger > > > > -- > Eric Bielefeld > Systems Programmer > Washington University > St Louis, Missouri > 314-935-3418 > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- 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
