Well the strange part was the RC=0 was returned. If it had been an 8 I probably would have been much happier with the message.
But 0 and an error? Very strange. Lizette > > I'm guessing that since you mentioned JES2 region size the reason code > on the $HASP473 message was 8? > > From looking in SHASSRC, B32K cell pool appears to be a general purpose > pool of 32K buffers, used for a variety of purposes: JES2 internally, > Spool API, NJE... > > I imagine you'd need to talk to Computer Associates to find out what CA > Dispatcher wants it for. > > If it happens again, you might try using $TBUFDEF,EXTBUF=(LIMIT=...) to > bump up the limit and restart CA Dispatcher and see if it makes much > difference. > > Cheers, Ant. > Northern Territory Government, Australia > > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On > Behalf Of Lizette Koehler > Sent: Friday, 30 April 2010 9:34 AM > To: IBM-MAIN@bama.ua.edu > Subject: JES2 msg $HASP473 for CELL Pool and B32K > > I had an interesting message come out of JES2 to night when CA Dispatch > was > starting up. > > > The HASP473 with TYPE=B32K > > I am not finding much in the JES2 Books on this issue. I am guessing > that > since there was only one occurrence we are okay. > > However, where would I find more information on the B32K or how CA > Dispatch > might require a JES2 Cell. > > Our JES2 proc does not have a REGION coded, so I am thinking I may need > to > add one. > > > > Lizette > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
