Hello Lizette,
Sorry for consuming lots of time on this issue. But, I wanted to get
clarity on very basic like,
1) If I see more records in one of the JES* DD statement Ex : JESMSGLG in
my IMS address space and I want to spin this messages from this address
space and put it in one dataset
and also after spin, all these messages should be no longer exist in this
imsproc.
SDSF JOB DATA SET DISPLAY - JOB IMS12IMS (STC01559) LINE 1-5
(5)
COMMAND INPUT ===> SCROLL ===>
CSR
PREFIX=DBC* DEST=(ALL) OWNER=* SYSNAME=
NP DDNAME StepName ProcStep DSID Owner C Dest Rec-Cnt
Page
JESMSGLG JES2 2 STCCICT Z
5
JESJCL JES2 3 STCCICT Z
229
JESYSMSG JES2 4 STCCICT Z
3
JESMSGLG JES2 103 STCCICT Z
869
JESYSMSG JES2 104 STCCICT Z
0
To make this process work, do I need to code DD statement in IMS proc like
below
//JESMSGLG DD SYSOUT=A,FREE=CLOSE,SPIN=UNALLOC
before running spin command ex : $T IMS12IMS,SPIN,DD=JESMSGLG
or there is no need to code this //JESMSGLG DD
SYSOUT=A,FREE=CLOSE,SPIN=UNALLOC
DD statement inside IMS proc.
I am asking this query because, currently in my IMS proc, I have only below
DD statement
//STEPLIB DD DSN=IMS1.V120.&SYS2.SDFSRESL,DISP=SHR
//PROCLIB DD DSN=IMS1.V120.&SYS2.PROCLIB,DISP=SHR
//DFSOLP00 DD DSN=IMS1.V120.&SYS.OLP00,DISP=SHR
//DFSOLP01 DD DSN=IMS1.V120.&SYS.OLP01,DISP=SHR
//DFSOLP99 DD DSN=IMS1.V120.&SYS.OLP99,DISP=SHR
//DFSWADS0 DD DSN=IMS1.V120.&SYS.WADS0,DISP=SHR
//DFSWADS1 DD DSN=IMS1.V120.&SYS.WADS1,DISP=SHR
//IMSACBA DD DSN=IMS1.V120.ACBLIBA,DISP=SHR
//IMSACBB DD DSN=IMS1.V120.ACBLIBB,DISP=SHR
//MODBLKSA DD DSN=IMS1.V120.&SYS2.MODBLKSA,DISP=SHR
//MODBLKSB DD DSN=IMS1.V120.&SYS2.MODBLKSB,DISP=SHR
//MODSTAT DD DSN=IMS1.V120.&SYS.MODSTAT,DISP=SHR
//SYSUDUMP DD SYSOUT=&SOUT,
//IMSRDS DD DSN=IMS1.V120.&SYS.RDS,DISP=SHR
//MATRIXA DD DSN=IMS1.V120.&SYS2.MATRIXA,DISP=SHR
//MATRIXB DD DSN=IMS1.V120.&SYS2.MATRIXB,DISP=SHR
//PRINTDD DD SYSOUT=&SOUT
//IMSMON DD DSN=IMS1.V120.IMSMON,DISP=SHR
//DFSESL DD DSN=IMS1.V120.&SYS2.SDFSRESL,DISP=SHR
and when I run $T IMS12IMS,SPIN,DD=JESMSGLG command, I see all record line
comes to zero in address space or JESMSGLG DD but system create one more DD
with same name JESMSGLG,
but I am not sure how this happens ??
And SPIN command output never complete and i just get below message but
never received message saying " SPIN successfully completed."
$T IMS12IMS,SPIN,DD=JESMSGLG
$HASP890 JOB(DBCY2RC3) 878
$HASP890 JOB(DBCY2RC3) STATUS=(EXECUTING/TST4),CLASS=STC,
$HASP890 PRIORITY=15,SYSAFF=(TST4),HOLD=(NONE)
Now, my another query is , when I run this SPIN command and my DD JESMSGLG
record comes to zero then where all these message gone. Are they purged or
I can view them.
I tried looking at output but I don’t find any print named IMS12IMS .
Can you please guide me with this whole process
On 09-May-2017 10:42 AM, "venkat kulkarni" <[email protected]>
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.
>
> Please correct me, if my understanding is wrong.
> Also, suggest after this spin , how to remove those many record from JESMSGLG
> dd which we just spin .
>
> On 09-May-2017 9:40 AM, "Gibney, Dave" <[email protected]> wrote:
>
>> There is no DD named JCLOUT.
>> There is nothing (aside from the JESxxxxx) to SPIN.
>> Why do you want to spin job?
>>
>> > -----Original Message-----
>> > From: IBM Mainframe Discussion List [mailto:[email protected]]
>> > On Behalf Of venkat kulkarni
>> > Sent: Monday, May 08, 2017 10:44 PM
>> > To: [email protected]
>> > Subject: Re: AW: Re: job output into dataset
>> >
>> > Hello All,
>> >
>> >
>> >
>> > Thanks for reply. I looked at my IMS proc and looks like below.
>> >
>> >
>> >
>> > BROWSE SYS1.DEVL.PROCLIB(IMS12IMS) - 01.05 Line 00000000 Col
>> 001
>> > 080
>> >
>> > Command ===> Scroll
>> ===>
>> > CSR
>> >
>> > ********************************* Top of Data
>> > ******************************
>> > ****
>> >
>> > // PROC RGN=0M,SOUT=A,
>> >
>> > // SYS=,SYS2=,
>> >
>> > // RGSUF=DBC,PARM1='AUTO=N',
>> >
>> > // PARM2=
>> >
>> > //IEFPROC EXEC PGM=DFSMVRC0,REGION=&RGN,
>> >
>> > // PARM='DBC,&RGSUF,&PARM1,&PARM2'
>> >
>> > //*
>> >
>> > //STEPLIB DD DSN=IMS1.V120.&SYS2.SDFSRESL,DISP=SHR
>> >
>> > //PROCLIB DD DSN=IMS1.V120.&SYS2.PROCLIB,DISP=SHR
>> >
>> > //*
>> >
>> > //IMSIRD DD SYSOUT=(A,INTRDR)
>> >
>> > //*
>> >
>> > //*
>> >
>> > //DFSOLP00 DD DSN=IMS1.V120.&SYS.OLP00,DISP=SHR
>> >
>> > //DFSOLP01 DD DSN=IMS1.V120.&SYS.OLP01,DISP=SHR
>> >
>> > //DFSOLP99 DD DSN=IMS1.V120.&SYS.OLP99,DISP=SHR
>> >
>> > //*
>> >
>> > //DFSWADS0 DD DSN=IMS1.V120.&SYS.WADS0,DISP=SHR
>> >
>> > //DFSWADS1 DD DSN=IMS1.V120.&SYS.WADS1,DISP=SHR
>> >
>> > //*
>> >
>> > //IMSACBA DD DSN=IMS1.V120.ACBLIBA,DISP=SHR
>> >
>> > //* DD DSN=DBCR.V120.ACBLIB.FAID,DISP=SHR
>> >
>> > //IMSACBB DD DSN=IMS1.V120.ACBLIBB,DISP=SHR
>> >
>> > //* DD DSN=DBCR.V120.ACBLIB.FAID,DISP=SHR
>> >
>> > //MODBLKSA DD DSN=IMS1.V120.&SYS2.MODBLKSA,DISP=SHR
>> >
>> > //MODBLKSB DD DSN=IMS1.V120.&SYS2.MODBLKSB,DISP=SHR
>> >
>> > //MODSTAT DD DSN=IMS1.V120.&SYS.MODSTAT,DISP=SHR
>> >
>> > //******** SYSTEM REQUIRED DD CARDS **************
>> >
>> > //*
>> >
>> > //SYSUDUMP DD SYSOUT=&SOUT,
>> >
>> > // DCB=(LRECL=125,RECFM=FBA,BLKSIZE=3129),
>> >
>> > // SPACE=(6050,300,,,ROUND)
>> >
>> > //IMSRDS DD DSN=IMS1.V120.&SYS.RDS,DISP=SHR
>> >
>> > //MATRIXA DD DSN=IMS1.V120.&SYS2.MATRIXA,DISP=SHR
>> >
>> > //MATRIXB DD DSN=IMS1.V120.&SYS2.MATRIXB,DISP=SHR
>> >
>> > //PRINTDD DD SYSOUT=&SOUT
>> >
>> > //*
>> >
>> > //IMSMON DD DSN=IMS1.V120.IMSMON,DISP=SHR
>> >
>> >
>> > //****** EXTERNAL SUBSYSTEM DD CARDS ***********
>> >
>> > //*
>> >
>> > //* USER MAY OPTIONALLY ADD THE DFSESL DD CARD
>> >
>> > //* FOR EXTERNAL SUBSYSTEM CONNECTION.
>> >
>> > //*
>> >
>> > //DFSESL DD DSN=IMS1.V120.&SYS2.SDFSRESL,DISP=SHR
>> >
>> > //************ DATA BASE DD CARDS ***************
>> >
>> > ******************************** Bottom of Data
>> > ********************************
>> >
>> >
>> >
>> > And in DA, I see this
>> >
>> >
>> >
>> > COMMAND INPUT ===>
>> >
>> > PREFIX=IMS12IMS DEST=(ALL) OWNER=* SYSNAME=
>> >
>> > NP DDNAME StepName ProcStep DSID Owner C Dest
>> >
>> > JESMSGLG JES2 2 STCBRCR Z
>> >
>> > JESJCL JES2 3 STCBRCR Z
>> >
>> > JESYSMSG JES2 4 STCBRCR Z
>> >
>> > JESMSGLG JES2 104 STCBRCR Z
>> >
>> > JESYSMSG JES2 105 STCBRCR Z
>> >
>> >
>> >
>> > So, I don’t have any other SYSOUT withSYSOUT=* or SYSOUT=A as you can
>> > see
>> > in the above mentioned proc.
>> >
>> >
>> >
>> > So, can you please suggest, what are all change I need to make for spin
>> to
>> > work .
>> >
>> > I think, I will also have to addFREE=CLOSE,SPIN=UNALLOC in this IMS
>> proc DD,
>> > So that spin function can work. Because, currently when I run spin
>> command
>> > like below,
>> >
>> > $T JQ(IMS12RC3),SPIN,DDNAME=JCLOUT
>> >
>> >
>> >
>> > I just get output as below.
>> >
>> >
>> >
>> > and output from this command is
>> >
>> > RESPONSE=TST4
>> >
>> > $HASP890 JOB(IMS12RC3)
>> >
>> > $HASP890 JOB(IMS12RC3) STATUS=(EXECUTING/TST4),CLASS=STC,
>> >
>> > $HASP890 PRIORITY=15,SYSAFF=(TST4),HOLD=(NONE)
>> >
>> >
>> >
>> > But this doesn’t show that spin successfully completed or not.
>> >
>> >
>> >
>> > I tried to provide you as much as detail this time. Can you please
>> suggest,
>> > how spin will work looking at my current proc
>> >
>> >
>> >
>> > On 08-May-2017 6:14 PM, "Barkow, Eileen" <[email protected]> wrote:
>> >
>> > > As I explained to Vekat, he can use the SDSF/REXX clist I gave him
>> > > to extract and archive the SYSOUT queue to a dataset as allocated in
>> the
>> > clist.
>> > > Then the clist can issue a command like:
>> > >
>> > > $TSTC04306,SPIN,DDNAME=DDNTOSPIN
>> > > To drain the queue.
>> > >
>> > > The clist has the started task number to use for the $Tstcno,SPIN
>> > command.
>> > > Code can also be added to extract the number of existing lines 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-
>> > [email protected]]
>> > > On Behalf Of venkat kulkarni
>> > > Sent: Monday, May 08, 2017 3:34 AM
>> > > To: [email protected]
>> > > 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
>> > >
>> > > JESMSGLG JES2
>> > >
>> > > JESJCL JES2
>> > >
>> > > JESYSMSG JES2
>> > >
>> > > JESMSGLG JES2
>> > >
>> > > JESYSMSG JES2
>> > >
>> > > On 08-May-2017 10:25 AM, "venkat kulkarni"
>> > > <[email protected]>
>> > > wrote:
>> > >
>> > > >
>> > > > 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 I am not aware of this process of doing this task. But after
>> > > > all our discussion, I did as below.
>> > > >
>> > > >
>> > > >
>> > > > I looked at IMS12RC3 proc in proclib library and noticed one of
>> > > > SYSOUT DD statement as below
>> > > >
>> > > >
>> > > >
>> > > > //JCLOUT DD SYSOUT=(A,INTRDR)
>> > > >
>> > > >
>> > > >
>> > > > Job IMS12RC3 is,
>> > > >
>> > > >
>> > > >
>> > > > BROWSE SYS1.DEVL.PROCLIB(IMS12RC3) - 01.03 Line 0000000
>> > > >
>> > > >
>> > > >
>> > > > ********************************* Top of Data
>> > ********************
>> > > > Show quoted text
>> > > >
>> > > > and then I used below command to spin IMS12RC3 address space lines
>> > > > and put it in dataset.
>> > > >
>> > > >
>> > > >
>> > > > $T JQ(IMS12RC3),SPIN,DDNAME=JCLOUT
>> > > >
>> > > >
>> > > >
>> > > > and output from this command is
>> > > >
>> > > >
>> > > >
>> > > > RESPONSE=TST4
>> > > >
>> > > > $HASP890 JOB(IMS12RC3)
>> > > >
>> > > > $HASP890 JOB(IMS12RC3) STATUS=(EXECUTING/TST4),CLASS=STC,
>> > > >
>> > > > $HASP890 PRIORITY=15,SYSAFF=(TST4),HOLD=(NONE)
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > But I think my understanding is wrong somehow but not able to point
>> > > > out the issue.
>> > > >
>> > > >
>> > > >
>> > > > I think, the flow of this process will be use SPIN command to cut
>> > > > lines from running address space to spool and then from spool, we
>> > > > should copy
>> > > to
>> > > > dataset.
>> > > >
>> > > >
>> > > >
>> > > > As I am new in this process, please help me with the required steps
>> > > > to
>> > > be
>> > > > performed to achieve this.
>> > > >
>> > > > On 08-May-2017 8:51 AM, "Peter Hunkeler" <[email protected]> wrote:
>> > > >
>> > > >>
>> > > >> > 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 [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
>> > >
>> > > ________________________________
>> > >
>> > > This e-mail, including any attachments, may be confidential,
>> > > privileged or otherwise legally protected. It is intended only for the
>> > > addressee. If you received this e-mail in error or from someone who
>> > > was not authorized to send it to you, do not disseminate, copy or
>> > > otherwise use this e-mail or its attachments. Please notify the sender
>> > > immediately by reply e-mail and delete the e-mail from your system.
>> > >
>> > > ------------------------------------------------------------
>> ----------
>> > > 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
