I[ve never used this but I think the SPIN parameter on the DD statement would
work for you
SPIN= {NO }
{UNALLOC }
{(UNALLOC,'hh:mm') }
{(UNALLOC,'+hh:mm') }
{(UNALLOC,nnn [K|M])}
{(UNALLOC,NOCMND) }
{(UNALLOC,CMNDONLY) }
(UNALLOC,'hh:mm')
Indicates that the data set is to be spun at time 'hh:mm' each
24 hour period. hh is hours and has a range of 00 through 23.
mm is minutes and has a range of 00 through 59. Note that the
time must be specified within apostrophes.
(UNALLOC,'+hh:mm')
Indicates that the data set is to be spun every hh:mm' time
interval, where hh is hours and has a range of 00-23 and mm is
minutes and has a range of 00-59. The minimum interval that can
be specified is 10 minutes (mm). Hours hh must be specified
even if zero. For example, SPIN=(UNALLOC,'+00:20') specifies
that the data set be spun at 20 minute intervals. Note that the
time interval must be specified within apostrophe characters.
Carmen Vitullo
----- Original Message -----
From: "venkat kulkarni" <[email protected]>
To: [email protected]
Sent: Tuesday, May 8, 2018 1:56:07 PM
Subject: Re: Job submit using REXX
Hello Group,
Is it possible to capture log from any running address space on every
regular interval and keep appending to these logs to output dataset using
REXX.
for example: I run my rexx at 1 AM and it capture logs generated upto 1 AM
and write into output dataset . Then I run this rexx at 2 AM and it capture
logs generated from 1 am till 2 AM and write into output dataset goes
upto 24hr.
On Tue, May 8, 2018 at 5:29 PM, Tony Thigpen <[email protected]> wrote:
> Phil,
>
> Per your link:
>
> The null queue is only needed if using '*' for the count. In the program
> posted, the following was used:
> "EXECIO" QUEUED()" DISKW ISFIN (FINIS"
>
> Since the number of records was specified using QUEUED(), then the null
> record is not needed.
>
> Using the QUEUED() is a good habit to get into since it allows you to
> actually DISKW a null record.
>
> Tony Thigpen
>
>
> Phil Carlyle wrote on 05/08/2018 10:14 AM:
>
>> Okay, when writing records from a stack using the EXECIO statement, this
>> is what I mean by writing from the QUEUE.
>> It requires that the last entry on the stack be null to indicate the end
>> of the stack. Here is a link to help you understand.
>> https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/
>> com.ibm.zos.v2r1.ikja300/dup0037.htm
>>
>>
>> PHIL CARLYLE
>> Information Security | IAM RACF directory services
>> M: 480-235-2837 | [email protected]<mailto:[email protected]>
>> TEKSystems
>>
>> “The Universe is made up of Protons, Neutrons, Electrons & Morons!”
>>
>> From: IBM Mainframe Discussion List [mailto:[email protected]] On
>> Behalf Of Paul Gilmartin
>> Sent: Monday, May 7, 2018 3:43 PM
>> To: [email protected]
>> Subject: Re: Job submit using REXX
>>
>> On Mon, 7 May 2018 20:46:36 +0000, Phil Carlyle wrote:
>>
>> When using QUEUE() for output the last record needs to be NULL in order
>>> to completely flush the buffers.
>>>
>>> I see no such statement in:
>> TSO/E REXX Reference Version 2 Release 3 SA32-0972-30
>>
>> Where do you see it?
>>
>> What do you mean by "using QUEUE() for output"? Example?
>>
>> -- gil
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected]<mailto:[email protected]>
>> with the message: INFO IBM-MAIN
>>
>>
>> American Express made the following annotations
>> ************************************************************
>> ******************
>> "This message and any attachments are solely for the intended recipient
>> and may contain confidential or privileged information. If you are not the
>> intended recipient, any disclosure, copying, use, or distribution of the
>> information included in this message and any attachments is prohibited. If
>> you have received this communication in error, please notify us by reply
>> e-mail and immediately and permanently delete this message and any
>> attachments. Thank you."
>>
>> American Express a ajouté le commentaire suivant le Ce courrier et toute
>> pièce jointe qu'il contient sont réservés au seul destinataire indiqué et
>> peuvent renfermer des
>> renseignements confidentiels et privilégiés. Si vous n'êtes pas le
>> destinataire prévu, toute divulgation, duplication, utilisation ou
>> distribution du courrier ou de toute pièce jointe est interdite. Si vous
>> avez reçu cette communication par erreur, veuillez nous en aviser par
>> courrier et détruire immédiatement le courrier et les pièces jointes. Merci.
>>
>> ************************************************************
>> ******************
>>
>>
>> ----------------------------------------------------------------------
>> 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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
