Re: Problem with JES2 proclibs

Article View: comp.protocols.ibm

Article #134

Back to comp.protocols.ibm Previous Next

#134

From: Butch Kemper
Date: Fri, 28 Jul 1989 23:00

21 lines
1130 bytes

I had some problems sending my original reply and I don't know if it
made it through.  So here it is again:




The problem is caused by the dataset going into a new extent that wasn't
present when the datasets were opened.  The circumvention is to:

      1.  Allocate the datasets so there are only primary allocations
          and no secondary allocations.

      2.  When the dataset get full, quiesce JES2 so that no jobs are
          going through JCL conversion and then compress the proclib.

Butch

   Computing Services Center           X040BK@TAMVM1.BITNET
   Texas A&M University                X040BK@TAMVM1.TAMU.EDU
   College Station, Tx 77843-3142      409/845-4215

Technical Details

Message-ID: <8907290743.AA13909@jade.berkeley.edu>

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!cs.utexas.edu!sun-barr!decwrl!ucbvax!TAMVM1.BITNET!X040BK

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!cs.utexas.edu!sun-barr!decwrl!ucbvax!TAMVM1.BITNET!X040BK
From: X040BK@TAMVM1.BITNET (Butch Kemper)
Newsgroups: comp.protocols.ibm
Subject: Re: Problem with JES2 proclibs
Message-ID: <8907290743.AA13909@jade.berkeley.edu>
Date: 28 Jul 89 23:00:02 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: Butch Kemper <X040BK%TAMVM1.bitnet@jade.berkeley.edu>
Organization: The Internet
Lines: 21