Sorry just got up that was it 

But I ran I to done other problems 

Can I move the checkpoint file to another pack 
As well 

Do t know why IBM set it up that way 
Putting the spool and check point file on the same pack as the parmlib's


> On Mar 23, 2017, at 2:41 AM, Anthony Thompson <[email protected]> 
> wrote:
> 
> Of course, you know that implementing a change to the SPOOLDEF VOLUME 
> parameter requires a cold start of JES2? And, unless you're not interested in 
> keeping any of the old spool data, a spool offload/reload.
> 
> Ant.
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On 
> Behalf Of Joseph Reichman
> Sent: Thursday, 23 March 2017 8:53 AM
> To: [email protected]
> Subject: Re: Spool file
> 
> My parmlib member points to SPOOL as the volume but everything else shows 
> B2SYS.
> 
>    SDSF SPOOL DISPLAY S0W1       2% ACT  14095 FRE  13683 LINE 1-2 (2)
> 
> COMMAND INPUT ===>                                            SCROLL ===>
> CSR  
> NP   NAME   Status   TGPct TGNum TGUse Command  SAff  Ext LoCyl    LoTrk
> 
>      B2SYS1 ACTIVE       5  3000   164          ANY   00  0000031B
> 000000000000
>      B2SYS2 ACTIVE       2 11095   248          ANY   01  00000006
> 000000000000        
> 
> 3.4 Display
> DSLIST - Data Sets on volume SPOOL*                                 Row 1 of
> 6 
> Command ===>                                                  Scroll ===>
> PAGE 
> 
> 
> Command - Enter "/" to select action                  Message
> Volume
> ----------------------------------------------------------------------------
> ---
>         SYS1.HASPACE
> SPOOL1 
>         SYS1.HASPACE
> SPOOL2 
>         SYS1.HASPACE
> SPOOL3 
>         SYS1.VTOCIX.SPOOL1
> SPOOL1 
>         SYS1.VTOCIX.SPOOL2
> SPOOL2 
>         SYS1.VTOCIX.SPOOL3
> SPOOL3
> ***************************** End of Data Set list
> ****************************
> 
> 
> 
> 
> 
> 
>          $dspool,long                                      
>          $HASP893 VOLUME(B2SYS1)                           
> VOLUME(B2SYS1)  STATUS=ACTIVE,DSNAME=SYS1.HASPACE,          
>                SYSAFF=(ANY),TGNUM=3000,TGINUSE=164,        
>                TRKPERTGB=3,PERCENT=5,RESERVED=NO,          
>                MAPTARGET=NO                                
>          $HASP893 VOLUME(B2SYS2)                           
> VOLUME(B2SYS2)  STATUS=ACTIVE,DSNAME=SYS1DisplKCELL=3,VOLUME=B2SYS
> 
>          $DSPOLLDEF                                           
> 
> JES parmlib member
> 
> SPOOLDEF BUFSIZE=3856,       /* MAXIMUM BUFFER SIZE     &BUFSIZE   c*/
>         DSNAME=SYS1.HASPACE,                                         
>         FENCE=NO,           /* Don't Force to Min.Vol. &FENCE    oc*/
>         SPOOLNUM=32,        /* Max. Num. Spool Vols    ---         c*
>         TGBPERVL=5,         /* Track Groups per volume in BLOB  ownc*
>         TGSIZE=33,          /* 30 BUFFERS/TRACK GROUP  &TGSIZE  wnc*/
>         TGSPACE=(MAX=26288, /* Fits TGMs into 4K Page  &NUMTG=(,  c*/
>                  WARN=80),  /*                       &NUMTG=(,% onc*/
>         TRKCELL=3,          /* 3 Buffers/Track-cell    &TCELSIZ   c*/
>         VOLUME=SPOOL        /* SPOOL VOLUME SERIAL   &SPOOL     c*/
> <-------
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On 
> Behalf Of Lizette Koehler
> Sent: Wednesday, March 22, 2017 12:23 AM
> To: [email protected]
> Subject: Re: Spool file
> 
> Only one HASPACE per JES2 Spool volume
> 
> Lizette
> 
>> -----Original Message-----
>> From: IBM Mainframe Discussion List [mailto:[email protected]] 
>> On Behalf Of Lizette Koehler
>> Sent: Tuesday, March 21, 2017 8:55 PM
>> To: [email protected] <mailto:[email protected]>
>> Subject: Re: Spool file
>> 
>> Issue a $DSPOOL,LONG  and see what it shows
>> 
>> Issue $DSPOOLDEF and see what it shows
>> 
>> Next go to ISPF 3.4
>> 
>> Search
>> 
>> **   in the dataset level
>> SPOOL*  in the VOLSER and see what it shows
>> 
>> I am not clear about your statement:   The spool volumes are still on the
> same
>> pack.  Please provide a display of what you are seeing.
>> 
>> 
>> Lizette
>> 
>> 
>>> -----Original Message-----
>>> From: IBM Mainframe Discussion List 
>>> [mailto:[email protected]] On Behalf Of Joseph Reichman
>>> Sent: Tuesday, March 21, 2017 7:48 PM
>>> To: [email protected] <mailto:[email protected]>
>>> Subject: Re: Spool file
>>> 
>>> I have 3 vols SPOOL1 SPOOL2 and SPOOL3
>>> 
>>> In jes2 parmlib member on the spool def for volume I specify SPOOL 
>>> and yet after ipl'ing
>>> 
>>> And then going back to SDSF to look for the  spool volumes are on 
>>> still on the same pack
>>> 
>>> 
>>> 
>>>> On Mar 21, 2017, at 11:20 AM, Lizette Koehler 
>>>> <[email protected] <mailto:[email protected]> >
>>> wrote:
>>>> 
>>>> The best practice for JES2 Spool file is standalone.  Never put 
>>>> anything on the same volume as either the SPOOL Space or the CKPT
>> datasets.
>>>> 
>>>> That can lead to unintentional issues.
>>>> 
>>>> Many shops in the past have tended towards multi-use volumes with 
>>>> JES2.  This is not recommended.
>>>> 
>>>> With storage arrays, you can code a volume as a MOD9 (9GB, 10,017
>>>> Cylinders) and only place the ckpt or the spool space (not both) 
>>>> on it. The array will typically only hold the amount of storage on 
>>>> the
>>>> mod9 as is allocated.  It does not hold the entire 10,017 
>>>> cylinders when you only have a 60 cylinder dataset on it.  As the 
>>>> volume is grown - the array will allocate more space to that 
>>>> device until it reaches
>>> its maximum size.
>>>> 
>>>> So, in my shop we have the ckpt on MOD3s and the Spool space on 
>>>> MOD54s.  The MOD3s only use a small portion for the ckpt as the 
>>>> ckpt is
>>> under 1000 cylinders.
>>>> The MOD54s are maxed out as I have allocated the entire amount to 
>>>> the Spool space.
>>>> 
>>>> So even though there could be 3339 cylinders allocated for the 
>>>> MOD3, I am using barely 15% of that.  So the volume is not very 
>>>> large even though it
>>> could be.
>>>> 
>>>> Or your shop could elect to create MOD1s - which is any size you 
>>>> wish to define
>>>> - for your ckpt and spool space to be considered stand alone.
>>>> 
>>>> When you start to mix files on volumes that should be dedicated -
>>>> CA1 TMS, JES Spool or JES ckpt - you can enq that volume and cause 
>>>> issues to
>>> those products.
>>>> 
>>>> 
>>>> Worst case scenario you might encounter is the need to cold start
> jes2.
>>>> 
>>>> Lizette
>>>> 
>>>> 
>>>>> -----Original Message-----
>>>>> From: IBM Mainframe Discussion List 
>>>>> [mailto:[email protected]] On Behalf Of Joseph Reichman
>>>>> Sent: Tuesday, March 21, 2017 5:47 AM
>>>>> To: [email protected] <mailto:[email protected]>
>>>>> Subject: Spool file
>>>>> 
>>>>> Hi
>>>>> 
>>>>> I'm having problems with my spool file
>>>>> 
>>>>> SYS1.HASPACE
>>>>> 
>>>>> 
>>>>> It happens to be in the same pack as my parmlib And other 
>>>>> important files
>>>>> 
>>>>> I'm wondering can the spool file be on any pack ?
>>>>> 
>>>>> Thanks
>>>>> 
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
> [email protected] <mailto:[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

Reply via email to