Found 6 jobs on output queue that are 62000+ pages! Can I use spin now after 
they are already on output q? We r at z/os 1.13

Sent from my iPhone

> On Mar 15, 2014, at 11:31 AM, "Lizette Koehler" <[email protected]> 
> wrote:
> 
> I know if you are at z/OS V1.13 - This is there, check your level of z/OS to
> see if is at your level.
> 
> 
> Usage and invocation - Spin any spin 
> 
> An additional operand on SPIN=(UNALLOC) specification in JCL 
> -  Similar in function to JESLOG= keyword on job card 
> . SPIN=(UNALLOC,value) where value is one of: 
> . hh:mm  - Spin data set at specified time 
> . + hh:mm  - Spin data set at interval specified 
> . nnn  [K|M]  - Spin every nnn records 
> . 
> NOCMD  - Cannot spin data set by command (current processing) 
> . CMDONLY - Spin only when a command is issued (default) 
>  Also supported in dynamic allocation and TSO ALLOC 
>  $T JQ(xxx),SPIN,DDNAME=ddname  -  command can spin data set on demand 
>                    - If you omit DDNAME= all active spin data sets will be
> spun
> 
> Lizette
> 
> 
> 
>> -----Original Message-----
>> From: IBM Mainframe Discussion List [mailto:[email protected]] On
>> Behalf Of Lizette Koehler
>> Sent: Saturday, March 15, 2014 8:23 AM
>> To: [email protected]
>> Subject: Re: JES2 shortage caused by BPXAS - HELP!
>> 
>> What version of z/OS are you running?
>> 
>> Second - add another SPOOL volume to provide some relief while you work on
> this.
>> 
>> 
>> 
>> I might try a JES2 OFFLOAD on the task.  You can set it up for this
> specific ID.
>> 
>> However, if the BPXAS is still active and this is a part of it, then you
> may have to do
>> some cycling or IPLing to free it up.
>> 
>> I have not research BPXAS as to how to make it go away (the output)>
>> 
>> 
>> Lizette
>> 
>> 
>>> -----Original Message-----
>>> From: IBM Mainframe Discussion List [mailto:[email protected]]
>>> On Behalf Of Crabtree, Anne D
>>> Sent: Saturday, March 15, 2014 7:52 AM
>>> To: [email protected]
>>> Subject: JES2 shortage caused by BPXAS - HELP!
>>> 
>>> In SDSF Status queue, I see this:
>>>                                                     tgnum   tgpct
>>> BPXAS          LOCAL                       64431  55.14 LOCAL    LOCAL
>>> 
>>> It is causing JES2 shortage!  I tried to purge protected PP but that
>> didn't work.  Is
>>> there any way to get rid of this???
> 
> ----------------------------------------------------------------------
> 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