Re: AW: Re: job output into dataset

z/OS System programmer can be helpful when setting up > new functions. > > > Lizette > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > > Behalf Of venkat kulkarni > > Sent: Sunday, May 14, 2017 9:55

Re: AW: Re: job output into dataset

t; To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: AW: Re: job output into dataset > > Hello Lizette, > > So, After modifying STC job class JES2 Log parameter with spin, i will have > to use $S command to start this process. > > Please suggest, as I have not used this before. > >

Re: AW: Re: job output into dataset

to see how your JOBCLASS(STC) is coded. >>> >>> >>> >>> >>> >>> Starting the STC with SPIN= is also helpful to spin all JES2 jcl DDs. >>> >>> >>> >>> >>> >>> >>> >>>

Re: AW: Re: job output into dataset

Hello Steve, So, After modifying STC job class JES2 Log parameter with spin, i will have to use $S command to start this process. Please suggest, as I have not used this before. Thanks On Sun, May 14, 2017 at 7:17 PM, Steve Horein wrote: > Regarding item #1, absent

Re: AW: Re: job output into dataset

Regarding item #1, absent any "formal" automation solution (CA OPS/MVS, IBM NetView, etc.), review the information found in these topics: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.hasa200/sacp.htm

Re: AW: Re: job output into dataset

arly to see what you >> want to do. >> >> >> >> >> >> >> >> >> >> Lizette >> >> >> >> >> >> *From:* venkat kulkarni [mailto:venkatkulkarn...@gmail.com] >> *Sent:* Friday, May 12, 2017 12:55 AM

Re: AW: Re: job output into dataset

gt; > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > > Behalf Of venkat kulkarni > > Sent: Thursday, May 11, 2017 9:37 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: AW: Re: job output into datas

Re: AW: Re: job output into dataset

> -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of venkat kulkarni > Sent: Thursday, May 11, 2017 9:37 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: AW: Re: job output into dataset > > Hello All, > > Final

Re: AW: Re: job output into dataset

umes, execution and termination of job steps and the job, and > disposition of data sets. > > > > You should talk to your friendly z/OS system programmer for assistance > specific to your shop. > > Lizette > > > -Original Message- > >From: venkat k

Re: AW: Re: job output into dataset

hould talk to your friendly z/OS system programmer for assistance specific to your shop. Lizette -Original Message- >From: venkat kulkarni <venkatkulkarn...@gmail.com> >Sent: May 10, 2017 11:42 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: AW: Re: job output into dataset

Re: JCL null statement (Was: job output into dataset)

On Tue, 9 May 2017 13:38:02 -0500, Tom Marchant wrote: >On Tue, 9 May 2017 13:25:43 -0500, Paul Gilmartin wrote: > >>On Tue, 9 May 2017 18:59:23 +0100, David W Noon wrote: >>> i) the job stream arrives at a null statement; >>>... >>I'm skeptical about that point since I often submit jobs

Re: AW: Re: job output into dataset

t; To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: AW: Re: job output into dataset > > Hello Lizette, > > Couple of important points, > > 1) I am still not clear that, what happens when we run spin command $T > job(ims12RC1),spin,ddname=JESMSGLG . Where messages goes from DD &g

Re: AW: Re: job output into dataset

Hello Lizette, Couple of important points, 1) I am still not clear that, what happens when we run spin command $T job(ims12RC1),spin,ddname=JESMSGLG . Where messages goes from DD JESMSGLG . In my case, when i run this command, it clear all record from DD JESMSGLG but its not storing in output

Re: AW: Re: job output into dataset

On 2017-05-10, at 01:25, Gibney, Dave wrote: > I don't believe attempting to override the three JES files with a > explicit DD definition will work. > I think, but haven't confirmed that you can define the eligibility to spin > those files in the definition of the STC or JOB Class to JES2.

Re: AW: Re: job output into dataset

On Tue, 9 May 2017 10:42:48 +0300, venkat kulkarni wrote: >Yes. It's not.so I should code jesmsglg dd stmt as >//JESMSGLG dd sysout=a,free=close,spin=unalloc No, you should not. Doing so would define a DD statement for your step. But the JESYSMSG for the job has already been allocated before

Re: AW: Re: job output into dataset

inframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of venkat kulkarni > > Sent: Wednesday, May 10, 2017 12:46 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: AW: Re: job output into dataset > > > > Below is my stc job class output > >

Re: AW: Re: job output into dataset

Of venkat kulkarni > Sent: Wednesday, May 10, 2017 12:46 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: AW: Re: job output into dataset > > Below is my stc job class output > > RESPONSE=TST4 > > $HASP837 JOBCLASS(STC) > > $HASP837 JOBCLASS(STC) AUTH=(AL

Re: AW: Re: job output into dataset

nt: Tuesday, May 09, 2017 11:25 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: AW: Re: job output into dataset > > > > I feel, whatever DD name I want spin, I should code in proclib for > example > > : If I want to always spin JESMSGLG DD from address space t

Re: AW: Re: job output into dataset

t; To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: AW: Re: job output into dataset > > I feel, whatever DD name I want spin, I should code in proclib for example > : If I want to always spin JESMSGLG DD from address space then I should > code below line in proclib and then > > on

Re: AW: Re: job output into dataset

and what works for one does not always work for another. > > > > Lizette > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > > Behalf Of venkat kulkarni > > Sent: Tuesday, May 09, 2017 12:43 AM &

Re: JCL null statement (Was: job output into dataset

On Tue, 9 May 2017 21:39:52 +0100, David W Noon wrote: >On Tue, 9 May 2017 14:56:33 -0500, Paul Gilmartin >(000433f07816-dmarc-requ...@listserv.ua.edu) wrote about "Re: job >output into dataset" (in ><5975685166305075.wa.paulgboulderaim@listserv.ua.edu>): >

JCL null statement (Was: job output into dataset

On Tue, 9 May 2017 14:56:33 -0500, Paul Gilmartin (000433f07816-dmarc-requ...@listserv.ua.edu) wrote about "Re: job output into dataset" (in <5975685166305075.wa.paulgboulderaim@listserv.ua.edu>): On Tue, 9 May 2017 20:20:10 +0100, David W Noon wrote: [snip] W

Re: job output into dataset

On Tue, 9 May 2017 13:38:02 -0500, Tom Marchant wrote: > >The behavior that David describes is very old. Back in the 70's, >operators would routinely add a null JCL statement to the end of >a tray of JCL to be processed so that the last job would be >processed immediately. I just submitted such

Re: job output into dataset

On Tue, 9 May 2017 20:20:10 +0100, David W Noon wrote: >On Tue, 9 May 2017 13:25:43 -0500, Paul Gilmartin >(000433f07816-dmarc-requ...@listserv.ua.edu) wrote about "Re: job >output into dataset" (in ><679800532864.wa.paulgboulderaim@listserv.ua.edu>): >

Re: job output into dataset

On Tue, 9 May 2017 13:25:43 -0500, Paul Gilmartin (000433f07816-dmarc-requ...@listserv.ua.edu) wrote about "Re: job output into dataset" (in <679800532864.wa.paulgboulderaim@listserv.ua.edu>): On Tue, 9 May 2017 18:59:23 +0100, David W Noon wrote: The INTRDR w

Re: job output into dataset

It also returns the JES JobId of the submitted job which is extremely helpful if the same JobName is submitted multiple times. Sent from my iPhone > On May 9, 2017, at 14:58, John McKown wrote: > > Also, any more, I use the ACB interface instead of the DCB

Re: job output into dataset

On Tue, May 9, 2017 at 1:25 PM, Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 9 May 2017 18:59:23 +0100, David W Noon wrote: > > > >The INTRDR writer will "spin" a job stream to the input spool > >automatically when: > > > > i) the job stream arrives at a

Re: job output into dataset

On Tue, 9 May 2017 13:25:43 -0500, Paul Gilmartin wrote: >On Tue, 9 May 2017 18:59:23 +0100, David W Noon wrote: >> i) the job stream arrives at a null statement; >>... >I'm skeptical about that point since I often submit jobs with noise >such as comments after a null statement and SDSF

Re: job output into dataset

On Tue, 9 May 2017 18:59:23 +0100, David W Noon wrote: > >The INTRDR writer will "spin" a job stream to the input spool >automatically when: > > i) the job stream arrives at a null statement; >... I'm skeptical about that point since I often submit jobs with noise such as comments after a

Re: job output into dataset

On Tue, 9 May 2017 18:59:23 +0100, David W Noon wrote: > >The INTRDR writer will "spin" a job stream to the input spool >automatically when: > > i) the job stream arrives at a null statement; > > ii) the job stream arrives at a new JOB statement; > >iii) the SYSOUT DD statement is closed. >

JCL or ...? (was: job output into dataset)

On 2017-05-09, at 10:20, Farley, Peter x23353 wrote: > Burroughs 5500 MCS (and possibly later, I didn't get to see those) had WFL, > Work Flow Language, which was nearly the full Burroughs Algol language, minus > the I/O facilities. > > Very powerful and flexible. Your "JCL" was an actual

Re: job output into dataset

On Tue, 9 May 2017 12:52:19 -0500, Paul Gilmartin (000433f07816-dmarc-requ...@listserv.ua.edu) wrote about "Re: job output into dataset" (in <3155439687677594.wa.paulgboulderaim@listserv.ua.edu>): On Tue, 9 May 2017 10:16:00 -0700, Lizette Koehler wrote: You can S

Re: job output into dataset

On Tue, 9 May 2017 10:16:00 -0700, Lizette Koehler wrote: > >You can SPIN SYSOUT (I do not think you can SPIN INTRDR ) > For INTRDR, the program can close it (and re-open or FREE and re-ALLOCATE.) I don't think I'd want to spin INTRDR by an external command unless I knew that data set was at a

Re: AW: Re: job output into dataset

t; Behalf Of venkat kulkarni > Sent: Tuesday, May 09, 2017 12:43 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: AW: Re: job output into dataset > > Yes. It's not.so I should code jesmsglg dd stmt as //JESMSGLG dd > sysout=a,free=close,spin=unalloc > > in my ims proc and t

Re: AW: Re: job output into dataset

Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday, May 09, 2017 11:31 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: AW: Re: job output into dataset IMO, IBM needs to _replace_ JCL with "something else". But, honestly, I'm not knowledgea

Re: job output into dataset

On Tue, 9 May 2017 10:21:38 -0500, Tom Marchant wrote: > >How many languages had a PRAGMA directive when ASP was written in the 1960's? > I see that as having been an excellent opportunity to innovate. IBM often misses such opportunities. The term "pragma[t]" appears to have originated with

Re: AW: Re: job output into dataset

On Tue, May 9, 2017 at 10:03 AM, Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 9 May 2017 09:54:22 -0500, Tom Marchant wrote: > > >On Tue, 9 May 2017 08:16:48 -0600, Paul Gilmartin wrote: > > > >>The JCL Ref. indicates that they are available to the >

Re: AW: Re: job output into dataset

On Tue, 9 May 2017 10:03:04 -0500, Paul Gilmartin wrote: >On Tue, 9 May 2017 09:54:22 -0500, Tom Marchant wrote: > >>There is a good reason it looks like a comment. >>It allows JCL to be coded that contains Job Entry Control Language statements >>for both JES2 and JES3, so that it can be run in

Re: AW: Re: job output into dataset

On Tue, 9 May 2017 09:54:22 -0500, Tom Marchant wrote: >On Tue, 9 May 2017 08:16:48 -0600, Paul Gilmartin wrote: > >>The JCL Ref. indicates that they are available to the >>//*FORMAT PR statement. >> >>("//*FORMAT PR" looks uncomfortably like a comment. Is >>this a reserved comment? Ugh!) >

Re: AW: Re: job output into dataset

On Tue, May 9, 2017 at 9:16 AM, Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On 2017-05-09, at 01:42, venkat kulkarni wrote: > > > Yes. It's not.so I should code jesmsglg dd stmt as > > //JESMSGLG dd sysout=a,free=close,spin=unalloc > > > > in my ims proc and then

Re: AW: Re: job output into dataset

On Tue, 9 May 2017 08:16:48 -0600, Paul Gilmartin wrote: >The JCL Ref. indicates that they are available to the >//*FORMAT PR statement. > >("//*FORMAT PR" looks uncomfortably like a comment. Is >this a reserved comment? Ugh!) It's a JES3 JECL statement. There is a good reason it looks like a

Re: AW: Re: job output into dataset

On Tue, 9 May 2017 16:01:33 +0300, venkat kulkarni wrote: >and also after spin, all these messages should be no longer exist in this >imsproc. SPIN does not delete messages. It makes them available for print or cancel. -- Tom Marchant

Re: AW: Re: job output into dataset

On 2017-05-09, at 01:42, venkat kulkarni wrote: > Yes. It's not.so I should code jesmsglg dd stmt as > //JESMSGLG dd sysout=a,free=close,spin=unalloc > > in my ims proc and then recycle ims and then issue > $t job,imsproc,spin,ddname=JESMSGLG > Command to spin JESMSGLG. > The JCL Ref. lists

Re: AW: Re: job output into dataset

the JESx) to SPIN. >> Why do you want to spin job? >> >> > -Original Message- >> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> > On Behalf Of venkat kulkarni >> > Sent: Monday, May 08, 2017 10:44 PM >> &

Re: AW: Re: job output into dataset

riginal Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of venkat kulkarni > > Sent: Monday, May 08, 2017 10:44 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: AW: Re: job output into dataset > > > > He

Re: AW: Re: job output into dataset

t; To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: AW: Re: job output into dataset > > Hello All, > > > > Thanks for reply. I looked at my IMS proc and looks like below. > > > > BROWSESYS1.DEVL.PROCLIB(IMS12IMS) - 01.05

Re: AW: Re: job output into dataset

in the > DDNAME to determine whether or not to spin it. > Any DDNAME can be specified. > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of venkat kulkarni > Sent: Monday, May 08, 2017 3:34 AM > To: IBM-MAIN

Re: AW: Re: job output into dataset

Sent: Monday, May 08, 2017 3:34 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: AW: Re: job output into dataset Just to add one more thing . Under ims12rc3 address space , below are dd name available. COMMAND INPUT ===> PREFIX=* DEST=(ALL) OWNER=* NP DDNAME StepName ProcSte JESMS

Re: AW: Re: job output into dataset

t; To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: AW: Re: job output into dataset > > Just to add one more thing . Under ims12rc3 address space , below are dd name > available. > > COMMAND INPUT ===> > > PREFIX=* DEST=(ALL) OWNER=* > > NP DDNAME StepName ProcSte

Re: AW: Re: job output into dataset

Just to add one more thing . Under ims12rc3 address space , below are dd name available. COMMAND INPUT ===> PREFIX=* DEST=(ALL) OWNER=* NP DDNAME StepName ProcSte JESMSGLG JES2 JESJCL JES2 JESYSMSG JES2 JESMSGLG JES2 JESYSMSG JES2 On 08-May-2017 10:25 AM,

Re: AW: Re: job output into dataset

Thanks for all suggestion and sorry for not being more precise. Our requirement is 1) Any address space (STC) running continously and producing more number of linee, we would like to cut lines on regulalr basis and put it in seperate dataset and keep appending data on regulalr basis. 2)

AW: Re: job output into dataset

> Started tasks? TSO sessions? UNIX forked (BPXAS) address spaces? What do you want to say by this?? -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: job output into dataset

On Sun, 7 May 2017 17:27:51 +, J R wrote: >Huh? REPORTS? Someone's confused. > Perhaps, "jobs generating reports." But that's redundant. Started tasks? TSO sessions? UNIX forked (BPXAS) address spaces? >> On May 7, 2017, at 12:34, Lizette Koehler wrote: >> >> INTRDR is used to

Re: job output into dataset

Huh? REPORTS? Someone's confused. Sent from my iPhone > On May 7, 2017, at 12:34, Lizette Koehler wrote: > > INTRDR is used to submit REPORTS or JCL into SPOOL. -- For IBM-MAIN subscribe /

Re: job output into dataset

f Lizette Koehler > Sent: Sunday, May 07, 2017 9:42 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: job output into dataset > > So I guess now I am curious as to what you are trying to capture from your DD > Statement that uses the INTRDR? > > Are you capturing anything

Re: job output into dataset

Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Lizette Koehler > Sent: Sunday, May 07, 2017 9:34 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: job output into dataset > > A DD Statement that use

Re: job output into dataset

LISTSERV.UA.EDU > Subject: Re: job output into dataset > > Hello, > > > > Thanks for helping so far. I used below command > > > > $T JQ(IMS12RC3),SPIN,DDNAME=JCLOUT > > > > and output from this command is > > > > RESPONSE=TST4 >

Re: job output into dataset

.UA.EDU] On > Behalf Of venkat kulkarni > Sent: Thursday, May 04, 2017 8:58 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: job output into dataset > > Hello, > > Thanks for reply. As you mentioned that you have program which can be used > to extract data from various jobs.

Re: job output into dataset

Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of venkat kulkarni Sent: Thursday, May 04, 2017 8:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: job output into dataset Hello, Thanks for reply. As you mentioned that you have program which can be used

Re: job output into dataset

On Thu, May 4, 2017 at 11:27 AM, Jesse 1 Robinson wrote: > In some cases, sysout--or job messages--can become a space problem. I > mentioned recently a system that we failed to IPL for over a year. At some > point we hit a spool track group shortage because of the PFA

Re: job output into dataset

@LISTSERV.UA.EDU Subject: (External):Re: job output into dataset Just to clarify. You will not run out of space on an active job. You can run into a S722 abend which is lines exceeded in JES which means the configuration in JES2 has a maximum limit for lines written to SPOOL. And the task exceeded

Re: job output into dataset

nframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of venkat kulkarni > Sent: Thursday, May 04, 2017 5:58 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: job output into dataset > > Hello, > > Thanks for reply. As you mentioned that you have program which

Re: [EXTERNAL] Re: job output into dataset

Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of venkat kulkarni Sent: Thursday, May 04, 2017 7:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: job output into dataset Hello, Thanks for reply. As you mentioned that you have program which can

Re: job output into dataset

to datasets. > I can send you the routine if that would help. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of venkat kulkarni > Sent: Wednesday, May 03, 2017 7:14 AM > To: IBM-MAIN@LISTSERV.UA.EDU >

Re: job output into dataset

- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of venkat kulkarni Sent: Wednesday, May 03, 2017 7:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: job output into dataset Thanks for all suggestion. Currently, we don’t have any third party product for doing this task

Re: job output into dataset

kat kulkarni > Sent: Wednesday, May 03, 2017 4:14 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: job output into dataset > > Thanks for all suggestion. Currently, we don’t have any third party product > for doing this task. So, my idea is to create rexx program, which keep > ch

Re: job output into dataset

Sent: Tuesday, May 02, 2017 5:40 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: job output into dataset So it might be possible that you are seeing data that JES2 has buffered. That is why you can see all of the data on a job in the ST panel even if all that is left in O or H panels is the output

Re: job output into dataset

venkat kulkarni wrote: >... So, my idea is to create rexx program, which keep checking ( once in day) >particular address spaces like IMS, CICS, or any other which are continuously >running in system and find that if the lines are exceed in the job with the >limit we set in rexx program then

Re: job output into dataset

an IEBGENER. > > Lizette > > -Original Message- > >From: "van der Grijn, Bart (B)" <bvandergr...@dow.com> > >Sent: May 2, 2017 2:26 PM > >To: IBM-MAIN@LISTSERV.UA.EDU > >Subject: Re: job output into dataset > > > >It works pretty wel

Re: job output into dataset

t; <bvandergr...@dow.com> >Sent: May 2, 2017 2:26 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: job output into dataset > >It works pretty well except for one (minor) issue. When you do SE against a >DDNAME in SDSF it doesn't work as expected. It seem to display the first

Re: job output into dataset

Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Phil Sidler Sent: Tuesday, May 02, 2017 4:16 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: job output into dataset On Tue, 2 May 2017 12:54:35 -0700, Lizette Koehler <stars...@mindspring.com> wrot

Re: job output into dataset

On Tue, 2 May 2017 12:54:35 -0700, Lizette Koehler wrote: >I have this in place on several Products I support. The JES Messages all go to >our output repository. No issues. Oh, I see it now, $HASP138 and a new DD with the same name shows up. Cool.

Re: job output into dataset

I have this in place on several Products I support. The JES Messages all go to our output repository. No issues. Lizette -Original Message- >From: Phil Sidler <phil_sid...@hotmail.com> >Sent: May 2, 2017 12:50 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: job o

Re: job output into dataset

On Tue, 2 May 2017 05:33:18 -0500, Roger Lowe wrote: >As of zOS 1.13 and later, JES2 provides the ability to 'spin' any SPIN spool >datasets based on command, size or time (interval or absolute). > >SPIN=(UNALLOC,value) where value is one of: >• ‘hh:mm’ – Spin data set

Re: job output into dataset

When you SPIN a job it goes to JES Spool. After that you need a process to pick it up. As others have stated: Homegrown REXX using ISFEXEC (SDSF REXX) to write to dataset External Writer to pick up the spooled output $AVERS VIEW Direct SAR Others. Lizette

Re: job output into dataset

A.EDU > Subject: Re: job output into dataset > > Thanks for sharing.. actually we have is , cics etc running from last 6 month > or 1 yrs without recycle and I saw 1 million record in that address spaces and > I would like to cut these record from these address space and keep appending

Re: job output into dataset

Thanks for sharing.. actually we have is , cics etc running from last 6 month or 1 yrs without recycle and I saw 1 million record in that address spaces and I would like to cut these record from these address space and keep appending in dataset , so that I dont have to recycle ims, cics etc to

Re: job output into dataset

> On May 2, 2017, at 8:02 AM, John McKown wrote: > > On Tue, May 2, 2017 at 2:35 AM, venkat kulkarni > wrote: > >> Hello, >> >> We have some address spaces running from long time and produce messages >> regularly. Now, my requirement

Re: job output into dataset

On Tue, May 2, 2017 at 2:35 AM, venkat kulkarni wrote: > Hello, > > We have some address spaces running from long time and produce messages > regularly. Now, my requirement is to cut those messages on regular basis > and keep appending into seperate dataset. > > This

Re: job output into dataset

imum of 500 lines must be specified. "K" is thousands and >"M" is millions. > > >Andy Styles >z/Series Systems Programmer > >-Original Message- >From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >Behalf Of venkat kulk

Re: job output into dataset

e- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of venkat kulkarni Sent: 02 May 2017 08:35 To: IBM-MAIN@LISTSERV.UA.EDU Subject: job output into dataset -- This email has reached the Bank via an external source -- Hello, We have some address spaces run

Re: job output into dataset

:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of venkat kulkarni Sent: 02 May 2017 08:35 To: IBM-MAIN@LISTSERV.UA.EDU Subject: job output into dataset -- This email has reached the Bank via an external source -- Hello, We have some address spaces running from long time and produce messages regularly. N

job output into dataset

Hello, We have some address spaces running from long time and produce messages regularly. Now, my requirement is to cut those messages on regular basis and keep appending into seperate dataset. This way, we will save spool size and no need to recycle the address space to remove old message. Can