Re: job output into dataset

2017-05-02 Thread Styles, Andy (ITS zPlatform Services)
Classification: Public If it's just the JESLOG you're interested in, take a look at the JESLOG parameter of the JOB card: Syntax: JESLOG= {SPIN} {NOSPIN} {SUPPRESS} Subparameter Definition: SPIN JESLOG is spin-eligible. There is an optional second operand.

Re: job output into dataset

2017-05-02 Thread venkat kulkarni
Hello Andy, Thanks . but after spin, where these messages will go and reside to later review. I want to remove messages from job in timely manner and put it in some dataset to be used further. Please suggest. On 02-May-2017 10:42 AM, "Styles, Andy (ITS zPlatform Services)" < 00d68f765d25-dma

Re: job output into dataset

2017-05-02 Thread Roger Lowe
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 at specified time • ‘+hh:mm’ – Spin data set at interval specified • nnn [K|M] – Spin

Re: job output into dataset

2017-05-02 Thread John McKown
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 way, we will save spool size

Re: job output into dataset

2017-05-02 Thread Edward Gould
> 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 is to cut those messages on regular basis >> and keep append

Re: job output into dataset

2017-05-02 Thread venkat kulkarni
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 red

Re: job output into dataset

2017-05-02 Thread Lizette Koehler
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

2017-05-02 Thread Lizette Koehler
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

2017-05-02 Thread Phil Sidler
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 at specified time >• ‘+hh

Re: job output into dataset

2017-05-02 Thread Lizette Koehler
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 >Sent: May 2, 2017 12:50 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: job output into dataset > >On Tue

Re: job output into dataset

2017-05-02 Thread Phil Sidler
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

2017-05-02 Thread van der Grijn, Bart (B)
--Original 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 wrote: >I have thi

Re: job output into dataset

2017-05-02 Thread Lizette Koehler
>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 of >the outputs with th

Re: job output into dataset

2017-05-03 Thread venkat kulkarni
> > -Original Message- > >From: "van der Grijn, Bart (B)" > >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 D

Re: job output into dataset

2017-05-03 Thread Elardus Engelbrecht
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 t

Re: job output into dataset

2017-05-03 Thread van der Grijn, Bart (B)
te Koehler 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

Re: job output into dataset

2017-05-03 Thread Lizette Koehler
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

2017-05-03 Thread Barkow, Eileen
- 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

2017-05-04 Thread venkat kulkarni
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 > Subject: Re: job output into dat

Re: job output into dataset

2017-05-04 Thread Lizette Koehler
- > From: IBM Mainframe 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 yo

Re: job output into dataset

2017-05-04 Thread Jesse 1 Robinson
-MAIN@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

2017-05-04 Thread John McKown
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 started task. > It had accum

Re: job output into dataset

2017-05-04 Thread Barkow, Eileen
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 to

Re: job output into dataset

2017-05-07 Thread venkat kulkarni
> 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

Re: job output into dataset

2017-05-07 Thread Lizette Koehler
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

2017-05-07 Thread Lizette Koehler
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

2017-05-07 Thread Lizette Koehler
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 tod

Re: job output into dataset

2017-05-07 Thread J R
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 / signoff / archive access instr

Re: job output into dataset

2017-05-07 Thread Paul Gilmartin
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 subm

Re: job output into dataset

2017-05-09 Thread Paul Gilmartin
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 ALGOL

Re: job output into dataset

2017-05-09 Thread Paul Gilmartin
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 J

Re: job output into dataset

2017-05-09 Thread David W Noon
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

2017-05-09 Thread Paul Gilmartin
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. > >If

Re: job output into dataset

2017-05-09 Thread Paul Gilmartin
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 nul

Re: job output into dataset

2017-05-09 Thread Tom Marchant
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 show

Re: job output into dataset

2017-05-09 Thread John McKown
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 null

Re: job output into dataset

2017-05-09 Thread J R
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 interface. This > allows the use of

Re: job output into dataset

2017-05-09 Thread David W Noon
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

2017-05-09 Thread Paul Gilmartin
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

2017-05-09 Thread Paul Gilmartin
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

AW: Re: job output into dataset

2017-05-07 Thread Peter Hunkeler
> 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 lists...@listserv.ua.

Re: [EXTERNAL] Re: job output into dataset

2017-05-04 Thread Dyck, Lionel B. (TRA)
ginal 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 whic

Re: AW: Re: job output into dataset

2017-05-08 Thread venkat kulkarni
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) But

Re: AW: Re: job output into dataset

2017-05-08 Thread venkat kulkarni
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

2017-05-08 Thread Lizette Koehler
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

2017-05-08 Thread Barkow, Eileen
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

2017-05-08 Thread venkat kulkarni
ine 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@LISTSERV.UA.EDU > Subject: R

Re: AW: Re: job output into dataset

2017-05-08 Thread Gibney, Dave
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

2017-05-09 Thread venkat kulkarni
gt; > 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 > > > > Hello All, >

Re: AW: Re: job output into dataset

2017-05-09 Thread venkat kulkarni
sage- >> > 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 >>

Re: AW: Re: job output into dataset

2017-05-09 Thread Paul Gilmartin
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 sev

Re: AW: Re: job output into dataset

2017-05-09 Thread Tom Marchant
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

2017-05-09 Thread Tom Marchant
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 c

Re: AW: Re: job output into dataset

2017-05-09 Thread John McKown
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 recy

Re: AW: Re: job output into dataset

2017-05-09 Thread Paul Gilmartin
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!) > >It'

Re: AW: Re: job output into dataset

2017-05-09 Thread Tom Marchant
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 e

Re: AW: Re: job output into dataset

2017-05-09 Thread John McKown
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 > >>//*FORMA

Re: AW: Re: job output into dataset

2017-05-09 Thread Farley, Peter x23353
rame 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 know

Re: AW: Re: job output into dataset

2017-05-09 Thread Lizette Koehler
A.EDU] On > 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 > >

Re: AW: Re: job output into dataset

2017-05-09 Thread venkat kulkarni
t 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: AW: Re: job output into dataset

2017-05-10 Thread Gibney, Dave
1: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 then I should > code below line in proclib and then >

Re: AW: Re: job output into dataset

2017-05-10 Thread venkat kulkarni
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 spa

Re: AW: Re: job output into dataset

2017-05-10 Thread Gibney, Dave
> 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 > > RESPONSE=TST4 > > $HASP837 JOBCLASS(STC) > > $HASP837 JOBCLASS(STC)

Re: AW: Re: job output into dataset

2017-05-10 Thread venkat kulkarni
ion 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 > > > > RESPO

Re: AW: Re: job output into dataset

2017-05-10 Thread Tom Marchant
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 you

Re: AW: Re: job output into dataset

2017-05-10 Thread Paul Gilmartin
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

2017-05-10 Thread venkat kulkarni
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

2017-05-10 Thread Gibney, Dave
AM > 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

2017-05-10 Thread Lizette Koehler
ta sets. You should talk to your friendly z/OS system programmer for assistance specific to your shop. Lizette -Original Message- >From: venkat kulkarni >Sent: May 10, 2017 11:42 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: AW: Re: job output into dataset > >Hello

Re: AW: Re: job output into dataset

2017-05-11 Thread venkat kulkarni
d 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 kulkarni > >Sent: M

Re: AW: Re: job output into dataset

2017-05-12 Thread Lizette Koehler
lines. Lizette > -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 A

Re: AW: Re: job output into dataset

2017-05-12 Thread venkat kulkarni
; > > -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 > &g

Re: AW: Re: job output into dataset

2017-05-14 Thread venkat kulkarni
gt;> >> >> >> >> >> >> >> Lizette >> >> >> >> >> >> *From:* venkat kulkarni [mailto:venkatkulkarn...@gmail.com] >> *Sent:* Friday, May 12, 2017 12:55 AM >> *To:* IBM Mainframe Discussion List ; Lizette >>

Re: AW: Re: job output into dataset

2017-05-14 Thread Steve Horein
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 https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos

Re: AW: Re: job output into dataset

2017-05-14 Thread venkat kulkarni
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 any "formal" automation sol

Re: AW: Re: job output into dataset

2017-05-14 Thread venkat kulkarni
gt; >>> Starting the STC with SPIN= is also helpful to spin all JES2 jcl DDs. >>> >>> >>> >>> >>> >>> >>> >>> Either or both can be used. >>> >>> >>> >>> Review the JES2 INIT and TUNING m

Re: AW: Re: job output into dataset

2017-05-15 Thread Lizette Koehler
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

2017-05-20 Thread venkat kulkarni
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 PM > > To: IBM-MAIN@LISTSE