SV: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)

2012-02-28 Thread Thomas Berg
Thanks!  Interesting variant of SDSF access.  I'm so used with the rexx 
interface that I haven't thought of the more direct way.
(I got the rexx way to work thanks to an example by Miklos Szigetvari.)


 
Regards, 
Thomas Berg 
_ 
Thomas Berg   Specialist   A M   SWEDBANK 

> -Ursprungligt meddelande-
> Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För
> Victor Gil
> Skickat: den 28 februari 2012 20:27
> Till: IBM-MAIN@bama.ua.edu
> Ämne: Re: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)
> 
> Thomas,
> 
> This is what I do to capture *any line range* from a SYSOUT being
> currently populated:
> 
> //SDSFBTCH EXEC PGM=SDSF
> //ISFOUT   DD  SYSOUT=*
> //PRINTFL  DD  SYSOUT=*,DCB=RECFM=VB  [or point to a FILE]
> //ISFINDD  *
> PRE 
> OWNER
> ST
> FIND 
> ++?
> FIND 
> ++S
> PRINT FILE PRINTFL
> PRINT/*
> //
> 
> HTH,
> -Victor-
> 
> =
> Is there any possibility to duplicate the output to SYSOUT to another
> Ddname/DSname in realtime ?
> I want to follow the execution by inspecting the output but at the same
> time save it for processing in a following step.
> Preferably by JCL means.
> 
> 
> 
> Regards,
> Thomas Berg
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN


SV: SV: SV: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)

2012-02-27 Thread Thomas Berg
Well that's what I did (IIRC), but I didn't get the ds, I think I got an "in 
use" msg when doing the SA. 

But if You can get this to work so must I be able to do.  Will maybe try it 
again. 


 
Regards, 
Thomas Berg 
_ 
Thomas Berg   Specialist   A M   SWEDBANK 




> -Ursprungligt meddelande-
> Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För
> Miklos Szigetvari
> Skickat: den 27 februari 2012 16:19
> Till: IBM-MAIN@bama.ua.edu
> Ämne: Re: SV: SV: Duplicating SYSOUT output to another DD/DSN in realtime
> ? (JCL)
> 
> Hi
> 
> This is more or less a sample from the REXX SDSF book .
> 
> 
>   /* REXX
> */   .
>   /* trace ?i
> */   .
>   /* accesses sdsf ST panel, thn list the column variables
> */  .
>   /* This is an example taken from SDSF bookshelf
> */  .
>   arg jobname
> ddname   .
>   Say
> 'jobname:'jobname
> .
>   Say
> 'ddname:'ddname
> .
>   rc=isfcalls('ON')
> .
>   /* access the ST panel
> */.
>   /* Address SDSF "ISFEXEC ST"
> */  .
>   /* access the DA panel
> */.
>   Address SDSF "ISFEXEC INPUT
> ON"  .
>   Say '1.
> rc:'rc  .
>   Address SDSF "ISFEXEC
> DA".
>   Say '2.
> rc:'rc  .
>   lrc=rc
> .
>   if
> lrc<>0
> .
>   then
> do
> .
> call
> msgrtn
> .
> exit
> 20
> .
>   end
> .
>   /* Loop for all running SYSLOG jobs
> */   .
>   do ix=1 to
> JNAME.0   .
> 
> /*
> .
> Say
> 'JNAME.'ix':'JNAME.ix
> .
> Say
> 'TOKEN.'ix':'TOKEN.ix
> .
> 
> */
> .
> found = 1 /* if 1, then found
> */   .
> if JNAME.ix <> jobname
> then.
>   found =
> 0.
> if found >
> 0   .
> then
> do
> .
>   Say
> 'JNAME.'ix':'JNAME.ix.
>   Say
> 'STEPN.'ix':'STEPN.ix.
>   Say
> 'TOKEN.'ix':'TOKEN.ix.
>   /* Issue the ? (JDS) action agains the
> */.
>   /* row to list the data sets in the job
> */   .
>   Address SDSF "ISFACT DA TOKEN('"TOKEN.ix"') PARM(NP ?)"
> ,.
> "( prefix
> jds_".
> 
> lrc=rc
> .
>   Say 'aha
> lrc:'lrc.
>   if
> lrc<>0
> .
>   then
> do  .
> call
> msgrtn.
> exit
> 20.
> 
> end
> .
>   /* Find the JESMSGLG data set and allocate it
> */ .
>   /* using the SA action character
> */  .
>   endindex =
> jds_DDNAME.0  .
> 
> 
> On 2/27/2012 4:03 PM, Thomas Berg wrote:
> > Regarding "even if the job is still running", is that true ?  When I
> tried that last time I couldn't get hold of the output as long as the job
> was running.
> > Exactly how do You do that ?  (E g which ISF-commands etc.)
> >
> >
> >
> > Regards,
> > Thomas Berg
> > _
> > Thomas Berg   Speciali

Re: SV: SV: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)

2012-02-27 Thread Miklos Szigetvari

Hi

This is more or less a sample from the REXX SDSF book .


 /* REXX 
*/   .
 /* trace ?i 
*/   .
 /* accesses sdsf ST panel, thn list the column variables 
*/  .
 /* This is an example taken from SDSF bookshelf  
*/  .
 arg jobname 
ddname   .
 Say 
'jobname:'jobname
.
 Say 
'ddname:'ddname  
.

 rc=isfcalls('ON')  
  .
 /* access the ST panel 
*/.
 /* Address SDSF "ISFEXEC ST" 
*/  .
 /* access the DA panel 
*/.
 Address SDSF "ISFEXEC INPUT 
ON"  .
 Say '1.  
rc:'rc  .
 Address SDSF "ISFEXEC 
DA".
 Say '2.  
rc:'rc  .

 lrc=rc 
  .
 if 
lrc<>0
.
 then 
do  
.
   call 
msgrtn.
   exit 
20.

 end
  .
 /* Loop for all running SYSLOG jobs 
*/   .
 do ix=1 to 
JNAME.0   .
   
/* 
.
   Say 
'JNAME.'ix':'JNAME.ix  
.
   Say 
'TOKEN.'ix':'TOKEN.ix  
.
   
*/ 
.
   found = 1 /* if 1, then found 
*/   .
   if JNAME.ix <> jobname 
then.
 found = 
0.
   if found > 
0   .
   then 
do.
 Say 
'JNAME.'ix':'JNAME.ix.
 Say 
'STEPN.'ix':'STEPN.ix.
 Say 
'TOKEN.'ix':'TOKEN.ix.
 /* Issue the ? (JDS) action agains the 
*/.
 /* row to list the data sets in the job 
*/   .
 Address SDSF "ISFACT DA TOKEN('"TOKEN.ix"') PARM(NP ?)" 
,.
   "( prefix 
jds_".
 
lrc=rc   
.
 Say 'aha 
lrc:'lrc.
 if 
lrc<>0.
 then 
do  .
   call 
msgrtn.
   exit 
20.
 
end  
.
 /* Find the JESMSGLG data set and allocate it 
*/ .
 /* using the SA action character 
*/  .
 endindex = 
jds_DDNAME.0  .



On 2/27/2012 4:03 PM, Thomas Berg wrote:

Regarding "even if the job is still running", is that true ?  When I tried that 
last time I couldn't get hold of the output as long as the job was running.
Exactly how do You do that ?  (E g which ISF-commands etc.)


  
Regards,

Thomas Berg
_____________
Thomas Berg   Specialist   A M   SWEDBANK



-Ursprungligt meddelande-
Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För
Miklo

Re: SV: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)

2012-02-27 Thread Tom Sipusic

On 2/27/2012 9:01 AM, Thomas Berg wrote:
The output needs to be processed in a later step. But if the output is 
directed to SYSOUT, are there any way for a later step to read that 
output ?   Regards, Thomas Berg
We use IOF, which allows a REXX EXEC in a later step to read the SYSOUT 
sent to a DD card in an earlier step. I would hope that rival products 
can do the same thing.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN


SV: SV: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)

2012-02-27 Thread Thomas Berg
Regarding "even if the job is still running", is that true ?  When I tried that 
last time I couldn't get hold of the output as long as the job was running. 
Exactly how do You do that ?  (E g which ISF-commands etc.) 


 
Regards, 
Thomas Berg 
_ 
Thomas Berg   Specialist   A M   SWEDBANK 


> -Ursprungligt meddelande-
> Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För
> Miklos Szigetvari
> Skickat: den 27 februari 2012 15:52
> Till: IBM-MAIN@bama.ua.edu
> Ämne: Re: SV: Duplicating SYSOUT output to another DD/DSN in realtime ?
> (JCL)
> 
>  Hi
> 
>  I used to say : "With the SDSF REXX interface you can process the
> output in the next STEP", but lately we have tested this again, and got
> some
> error codes during processing the own job. (i.e "sfmsg is:JCT NOT
> AVAILABLE   ")
> Anyhow if you submit a job to process the JES output from the previous
> job, it would work, even if the job is still ruing.
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN


SV: SV: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)

2012-02-27 Thread Thomas Berg
> -Ursprungligt meddelande-
> Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För
> Steve Comstock
> Skickat: den 27 februari 2012 15:13
> Till: IBM-MAIN@bama.ua.edu
> Ämne: Re: SV: Duplicating SYSOUT output to another DD/DSN in realtime ?
> (JCL)
> 
> On 2/27/2012 7:01 AM, Thomas Berg wrote:
> >> -Ursprungligt meddelande-
> >> Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För
> >> Steve Comstock
> >> Skickat: den 27 februari 2012 14:58
> >> Till: IBM-MAIN@bama.ua.edu
> >> Ämne: Re: Duplicating SYSOUT output to another DD/DSN in realtime ?
> (JCL)
> >>
> >> On 2/27/2012 4:18 AM, Thomas Berg wrote:
> >>> Is there any possibility to duplicate the output to SYSOUT to another
> >> Ddname/DSname in realtime ?
> >>> I want to follow the execution by inspecting the output but at the
> same
> >> time save it for processing in a following step.
> >>> Preferably by JCL means.
> >>>
> >>>
> >>>
> >>> Regards,
> >>> Thomas Berg
> >>> _
> >>> Thomas Berg   Specialist   A M   SWEDBANK
> >>>
> >>
> >> If you want to 'follow the execution by inspecting the output'
> >> and 'in realtime', I gather you don't want an automated
> >> process.
> >>
> >> Why not just go to SDSF (or (E)JES or IOF or Flasher or ... )
> >> and select the sysout file? It will show you what's been
> >> output so far, but does not disturb the final distribution.
> >>
> >> You can set up an automated, timed refresh of the screen
> >> (say, every 5 seconds) to watch the SYSOUT data grow, or
> >> just hit enter to see the latest entries.
> >>
> >> Or maybe I'm not clear on what you are after.
> >
> > The output needs to be processed in a later step. But if the output is
> directed to SYSOUT, are there any way for a later step to read that output
> ?
> >
> >
> > Regards,
> > Thomas Berg
> > _
> > Thomas Berg   Specialist   A M   SWEDBANK
> >
> 
> Ah! So the output is not originally SYSOUT? Can you direct
> the output to a z/OS UNIX file? Then from a UNIX session
> (omvs or telnet) you could use 'tail' commands to watch
> the file grow.
> 
> If things are not going well, cancel the job. If all goes
> well, copy the UNIX file back to an MVS file (or just
> process the UNIX file if that would be supported).

Well, I suppose that's a good idea. But here I'm out on unchartered 
territories. :)  Although *NIX land is not totally unknown for me I haven't 
used the z/OS variant much. 
Maybe it's a time for me to explore it...

But as this routine will go into automated production in future I prefer MVS 
proper (as I don't want to change the job to much between the "manual" period 
and the automated production. 


 
Regards, 
Thomas Berg 
_ 
Thomas Berg   Specialist   A M   SWEDBANK 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN


Re: SV: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)

2012-02-27 Thread Miklos Szigetvari

Hi

I used to say : "With the SDSF REXX interface you can process the 
output in the next STEP", but lately we have tested this again, and got 
some
error codes during processing the own job. (i.e "sfmsg is:JCT NOT 
AVAILABLE   ")
Anyhow if you submit a job to process the JES output from the previous 
job, it would work, even if the job is still ruing.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN


SV: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)

2012-02-27 Thread Thomas Berg
> -Ursprungligt meddelande-
> Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För
> Lizette Koehler
> Skickat: den 27 februari 2012 15:06
> Till: IBM-MAIN@bama.ua.edu
> Ämne: Re: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)
> 
> That's right.  I'm about to process DB2 REBIND en masse and need to see in
> realtime that it executes ok (if in error it needs to be stopped) and at
> the
> same time save it for processing in a later step.
> As the execution can take >30 minutes I don't want to wait until end.
> (Using the DSN command under IKJEFT01.)
> 
> 
> 
> Then why not put a REXX around it and then inspect the SQL as it is
> produced?  You can use a REXX to invoke the DSNREXX or use DSN natively.
> 

I'm worried about performance.  As it is now I'm feeding one invocation of DSN 
with >25000 REBIND's.  If I do a new invoke of DSN for every (or every 10:th) 
REBIND it will prolong the execution (I think, haven't tested). 
My experience of DSNREXX is that performance is not one of its points... 

What I'm doing is to manually run a "package cleaning" routine for future 
automatic execution. So I want to have a close control of what's happening now 
in the beginning. 

Maybe I should go back to the drawing board... 


 
Regards, 
Thomas Berg 
_ 
Thomas Berg   Specialist   A M   SWEDBANK 


 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN


Re: SV: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)

2012-02-27 Thread Steve Comstock

On 2/27/2012 7:01 AM, Thomas Berg wrote:

-Ursprungligt meddelande-
Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För
Steve Comstock
Skickat: den 27 februari 2012 14:58
Till: IBM-MAIN@bama.ua.edu
Ämne: Re: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)

On 2/27/2012 4:18 AM, Thomas Berg wrote:

Is there any possibility to duplicate the output to SYSOUT to another

Ddname/DSname in realtime ?

I want to follow the execution by inspecting the output but at the same

time save it for processing in a following step.

Preferably by JCL means.



Regards,
Thomas Berg
_
Thomas Berg   Specialist   A M   SWEDBANK



If you want to 'follow the execution by inspecting the output'
and 'in realtime', I gather you don't want an automated
process.

Why not just go to SDSF (or (E)JES or IOF or Flasher or ... )
and select the sysout file? It will show you what's been
output so far, but does not disturb the final distribution.

You can set up an automated, timed refresh of the screen
(say, every 5 seconds) to watch the SYSOUT data grow, or
just hit enter to see the latest entries.

Or maybe I'm not clear on what you are after.


The output needs to be processed in a later step. But if the output is directed 
to SYSOUT, are there any way for a later step to read that output ?


Regards,
Thomas Berg
_
Thomas Berg   Specialist   A M   SWEDBANK



Ah! So the output is not originally SYSOUT? Can you direct
the output to a z/OS UNIX file? Then from a UNIX session
(omvs or telnet) you could use 'tail' commands to watch
the file grow.

If things are not going well, cancel the job. If all goes
well, copy the UNIX file back to an MVS file (or just
process the UNIX file if that would be supported).



--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN


SV: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)

2012-02-27 Thread Thomas Berg
> -Ursprungligt meddelande-
> Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För
> Steve Comstock
> Skickat: den 27 februari 2012 14:58
> Till: IBM-MAIN@bama.ua.edu
> Ämne: Re: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)
> 
> On 2/27/2012 4:18 AM, Thomas Berg wrote:
> > Is there any possibility to duplicate the output to SYSOUT to another
> Ddname/DSname in realtime ?
> > I want to follow the execution by inspecting the output but at the same
> time save it for processing in a following step.
> > Preferably by JCL means.
> >
> >
> >
> > Regards,
> > Thomas Berg
> > _
> > Thomas Berg   Specialist   A M   SWEDBANK
> >
> 
> If you want to 'follow the execution by inspecting the output'
> and 'in realtime', I gather you don't want an automated
> process.
> 
> Why not just go to SDSF (or (E)JES or IOF or Flasher or ... )
> and select the sysout file? It will show you what's been
> output so far, but does not disturb the final distribution.
> 
> You can set up an automated, timed refresh of the screen
> (say, every 5 seconds) to watch the SYSOUT data grow, or
> just hit enter to see the latest entries.
> 
> Or maybe I'm not clear on what you are after.

The output needs to be processed in a later step. But if the output is directed 
to SYSOUT, are there any way for a later step to read that output ?   

 
Regards, 
Thomas Berg 
_ 
Thomas Berg   Specialist   A M   SWEDBANK 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN


SV: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)

2012-02-27 Thread Thomas Berg
That's right.  I'm about to process DB2 REBIND en masse and need to see in 
realtime that it executes ok (if in error it needs to be stopped) and at the 
same time save it for processing in a later step.
As the execution can take >30 minutes I don't want to wait until end. 
(Using the DSN command under IKJEFT01.)


 
Regards, 
Thomas Berg 
_ 
Thomas Berg   Specialist   A M   SWEDBANK 





> -Ursprungligt meddelande-
> Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För
> Vernooij, CP - SPLXM
> Skickat: den 27 februari 2012 14:44
> Till: IBM-MAIN@bama.ua.edu
> Ämne: Re: Duplicating SYSOUT output to another DD/DSN in realtime ? (JCL)
> 
> "Staller, Allan"  wrote in message
> news:<45e5f2f45d7878458ee5ca679697335502e25...@usdaexch01.kbm1.loc>...
> > YES!.
> >
> > Define multiple output statements
> > //out1 output.
> > //out2 output...
> >
> > And refer to them
> >
> > //sysprint  dd output=(*.out1,*.out2)
> >
> > HTH,
> >
> 
> That is what I thought first, but I think he wants it to both sysout and
> a dataset.
> 
> Kees.
> 
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee only. If
> you are not the addressee, you are notified that no part of the e-mail or
> any attachment may be disclosed, copied or distributed, and that any other
> action related to this e-mail or attachment is strictly prohibited, and
> may be unlawful. If you have received this e-mail by error, please notify
> the sender immediately by return e-mail, and delete this message.
> 
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
> employees shall not be liable for the incorrect or incomplete transmission
> of this e-mail or any attachments, nor responsible for any delay in
> receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with registered
> number 33014286
> 
> 
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN