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
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.
>
>
to see how your JOBCLASS(STC) is coded.
>>>
>>>
>>>
>>>
>>>
>>> Starting the STC with SPIN= is also helpful to spin all JES2 jcl DDs.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
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
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
arly to see what you
>> want to do.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Lizette
>>
>>
>>
>>
>>
>> *From:* venkat kulkarni [mailto:venkatkulkarn...@gmail.com]
>> *Sent:* Friday, May 12, 2017 12:55 AM
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
> -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
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
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
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
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
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.
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
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
> >
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
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
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
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
&
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
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
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
>
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
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!)
>
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
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
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
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
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
>> &
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
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
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
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
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
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,
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)
> 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
37 matches
Mail list logo